Posts made by leobg

Did you get anywhere with this? I am in exact same boat (1LC+6HC on latest stable RRF 3.4.0)

@jay_s_uk upvoting this - having SBC temperature displayed in DWC along with MCU would be very useful.

Anyone has instructions how to wire up the TFT display to a Duet board (Mini 5+ in particular)?

@jay_s_uk said in Monitoring Duet 6HC drivers:

@leobg no, they only provide 0 (cold), 100 (hot) and 130 (very hot)

Thanks for the clarification!

I am trying to monitor drivers temperature on my 6HC as per https://duet3d.dozuki.com/Wiki/Mounting_and_cooling_the_board with

M308 S3 Y"drivers" A"DRIVERS"

but I get a reading of 0.0 degrees for the "drivers" sensor. Am I doing something wrong?

@dc42 said in [3.4.0b7] Firmware update changes 1LC temp:

@alex-cr and anyone else getting incorrect readings using 3.4.0beta7+2, please post a M122 B# report where # is the tool board number.

Latest I found reference is 7+1, where is 7+2 linked? Another threat? What changed between +1 and +2 btw?

I have upgraded back to b7, (sbc mode), but apt spit an error:

Setting up reprapfirmware (3.4-b7-1) ...
Unhandled exception. System.Collections.Generic.KeyNotFoundException: The given key '' was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at DuetControlServer.Utility.Firmware.UpdateFirmwareRemotely() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/Utility/Firmware.cs:line 425
   at DuetControlServer.Program.CheckForAnotherInstance() in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/Program.cs:line 349
   at DuetControlServer.Program.Main(String[] args) in /home/christian/Duet3D/DuetSoftwareFramework/src/DuetControlServer/Program.cs:line 100
   at DuetControlServer.Program.<Main>(String[] args)
Aborted

I'll appreciate if someone can throw some insight on what might be wrong with the SBC upgrade mode..

Meanwhile I have manually updated the 6HC and 1LC firmwares (B7-1) from the thread here. Temperature reads normal for me again now. Will give the new firmware a try to see if anything else pops up

edit: here is M121 B121 output:

M122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.0beta7+1 (2021-12-22 18:45:45)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2152, free system stack 2762 words
Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,115) CanAsync(notifyWait,0.0%,61) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,27) TMC(delaying,3.0%,57) MAIN(running,91.8%,351) IDLE(ready,0.0%,26) AIN(delaying,5.0%,142), total 100.0%
Last reset 00:06:32 ago, cause: software
Last software reset time unknown, reason: AssertionFailed, available RAM 3392, slot 1
Software reset code 0x0120 ICSR 0x00000000 SP 0x2000415c Task  Freestk 129 bad marker
Stack: 00000544 00022ffc 00019b65 20003134 00016cff 20003134 000163d1 20000ed0 00000000 00000001 00008275 200071c8 200071c8 200071e0 00000000 20000f50 00011647 000223b8 00022474 00021ac8 00019b05 200071c8 200071c8 20000f50 000083ed 200071d8 000009c7
Driver 0: pos 0, 414.0 steps/mm,standstill, SG min 2, read errors 0, write errors 1, ifcnt 177, reads 64992, writes 13, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 1/6, peak Rx sync delay 599, resyncs 0/1, no step interrupt scheduled
VIN voltage: min 24.7, current 24.8, max 24.8
MCU temperature: min 37.8C, current 37.9C, max 38.4C
Last sensors broadcast 0x00000002 found 1 205 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 8154, send timeouts 0, received 3564, lost 0, free buffers 37, min 37, error reg 110000
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 3, other errors 0
=== Filament sensors ===
Interrupt 4 to 12us, poll 6 to 572us
Driver 0: pos 36.21, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0

I can confirm the erratic temperature reading after upgrading to B7 with 1LC v1.1. SBC + 6HC + 1LC. Flashing back to B6 returns thermistor readings to normal. Slice Engineering Hight Temp thermistor (450C).

@martin7404 How did you wire up the super pinda to your toolboard? Are you happy with it? I am considering switching from BL-Touch to superpinda as the BLTouch is often acting up on me and feels not as reliable as magnetic probes

I am running similar (just regular Mosquito), I put together a design (https://www.thingiverse.com/thing:4925085) toolboard attaches between the cooling fan and the extruder, right where EVA cable relief arm mounts. Keeps the toolhead setup as compact and as tucked together as possible. The arm is relocated to the side - original cable relief bracket from EVA can be reused, or the one I added which is smaller since toolboard only requires 4 wires. The bracket has provisioning for a lid, but it felt as unnecessary weight (and would restrict board cooling) and I never ended up finishing it.

I can confirm similar behavior (6HC with 1LC in SBC mode on latest 3.4 beta5 firmware) on another RatRig printer - V-Core3 (CoreXY). Running left and right motors in StealthChop-to-SpreadCycle mode causes same "clacking" sound as shown by OP.

Not sure if default behavior from Stable and previous betas has changed, but since switching to 3.4.0 beta4, emergency stop initiated from PanelDue halts the printer and requires power cycle. Is this a bug or there is setting that can restore previous functionality (stop whatever is going on and soft reset the board)?

Running 3.4.0 beta4 in SBC mode. Duet 3 6HC board. Resume after pause seems broken. Instead of resuming the print, it positions right where it should resume, then print restarts from the beginning, including homing (which is fairly problematic if you have something already printed..) This behavior wasn't present in 3.4.0 beta3

Apology for the double post - another member reported same behavior - https://forum.duet3d.com/topic/25362/3-4-0-beta4-troubles

@nightlonk42 This is how mine is wired:
. Note the stepper is just for illustration of the port.