1lc board stopped working, but still responsive to m122
-
Printing all week with no issues. Woke up this morning to a completed print, but hotend temp at 2000c and printer not letting me start another print. I hit Emergency Stop and once the printer came back it had an error for the hotend, and current temp (of said hotend). Powered the printer off, waited, and back on didn't change anything.
I noticed the hotend cooling fan was on.... At this point it looked like the 1lc board had died.
I checked the board m122 B10 and there it was, so CAN was working!
But its sensors/hotend/fan didn't work. Powered it down/up a few more times without fix. Finally powered off and gave up. A few hours later knowing I needed to finish printing something for a kids school project powered it back on and works! Like it never stopped and has been printing for about 8 hours.Copied M122 and M122 B10 below. The bottom most are from when the 1lc board wasn't working, and the top most are when it was again. I didn't close the browser inbetween it not working and when it was working and was able to complete a single copy/paste, and includes a few messages about heater and etc not being found after a power cycle.
Any ideas would be helpful. My main concern is that the board is going bad, and fails again mid print.
5/3/2022, 12:18:32 PM M122 B10 Diagnostics for board 10: Duet TOOL1LC rev 1.0 or earlier firmware version 3.4.0 (2022-03-15 09:00:04) Bootloader ID: SAMC21 bootloader version 2.2 (2021-01-16b1) All averaging filters OK Never used RAM 3608, free system stack 88 words Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,115) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) TMC(delaying,3.0%,57) MAIN(running,91.9%,341) IDLE(ready,0.0%,40) AIN(delaying,4.9%,142), total 100.0% Last reset 00:02:41 ago, cause: power up Last software reset at 2021-04-17 12:15, reason: HardFault, available RAM 13692, slot 0 Software reset code 0x0060 ICSR 0x0400f003 SP 0x200019a0 Task CanR Freestk 95 ok Stack: 20008000 0000ffff 002d007f 200020bc 20000018 00006a4b 00005eec 21000000 200047d8 20001c58 20001c54 0000fd85 a5a5a5a5 200047d8 20001c58 200047d8 20001c58 0000ff35 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 00016c25 a5a5a5a5 00000000 00000000 Driver 0: pos 0, 829.8 steps/mm,standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 15177, 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 5/8, peak Rx sync delay 212, resyncs 0/0, no step interrupt scheduled VIN voltage: min 23.7, current 23.8, max 23.9 MCU temperature: min 20.3C, current 30.0C, max 30.0C Last sensors broadcast 0x00000001 found 1 238 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 2914, send timeouts 0, received 1359, lost 0, free buffers 37, min 37, error reg 110000 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0 Accelerometer: none I2C bus errors 4481, naks 4481, other errors 4481 5/3/2022, 12:18:22 PM m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (SBC mode) Board ID: 08DJM-956L2-G43S4-6JTDJ-3SD6S-9S5YD Used output buffers: 1 of 40 (20 max) === RTOS === Static ram: 151000 Dynamic ram: 65844 of which 0 recycled Never used RAM 133828, free system stack 200 words Tasks: SBC(ready,0.5%,436) HEAT(notifyWait,0.0%,321) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.8%,92) MAIN(running,88.2%,1231) IDLE(ready,3.5%,30), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:02:30 ago, cause: power up Last software reset at 2022-05-03 08:36, reason: MemoryProtectionFault mmarValid daccViol, GCodes spinning, available RAM 129940, slot 2 Software reset code 0x4163 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x00400804 BFAR 0x079a070f SP 0x20419a60 Task IDLE Freestk 4290773031 ok Stack: 079a06ff a5a5a5a5 20418198 20424d9c a5a5a5a5 00484b33 00485c9c 01000000 a5a5a5a5 00484171 a5a5a5a5 2041b27c 079a12a3 204337ac 204203fc 20419a8c 20424d34 00000003 20429b1c 20429b1c 20419a8c 20429b14 00000002 20419ae8 4e49414d 00000000 00000000 Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 136 MCU temperature: min 9.9, current 24.3, max 24.4 Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0 Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, mspos 8, reads 54418, writes 14 timeouts 0 Driver 1: standstill, SG min 0, mspos 8, reads 54418, writes 14 timeouts 0 Driver 2: standstill, SG min 0, mspos 8, reads 54421, writes 11 timeouts 0 Driver 3: standstill, SG min 0, mspos 8, reads 54421, writes 11 timeouts 0 Driver 4: standstill, SG min 0, mspos 8, reads 54418, writes 14 timeouts 0 Driver 5: standstill, SG min 0, mspos 8, reads 54419, writes 14 timeouts 0 Date/time: 2022-05-03 12:18:22 Slowest loop: 1.39ms; fastest: 0.04ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 2 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Segments left: 0 Movement lock held by null HTTP* is doing "M122" in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger* is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === CAN === Messages queued 1266, received 2687, lost 0, boc 0 Longest wait 2ms for reply type 6026, peak Tx sync delay 252, free buffers 50 (min 49), ts 752/751/0 Tx timeouts 0,0,0,0,0,0 === SBC interface === Transfer state: 4, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 5779/5779 SPI underruns 0, overruns 0 State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x2b858 Buffer RX/TX: 0/0-0, open files: 0 === Duet Control Server === Duet Control Server v3.4.0 Code buffer space: 4096 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 0.47, max time between full transfers: 90.9ms, max pin wait times: 65.5ms/9.4ms Codes per second: 0.01 Maximum length of RX/TX data transfers: 3488/936 5/3/2022, 12:16:55 PM Connection established 5/3/2022, 8:54:08 AM Connection interrupted, attempting to reconnect... Network error 5/3/2022, 8:53:04 AM M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (SBC mode) Board ID: 08DJM-956L2-G43S4-6JTDJ-3SD6S-9S5YD Used output buffers: 1 of 40 (20 max) === RTOS === Static ram: 151000 Dynamic ram: 65488 of which 0 recycled Never used RAM 134184, free system stack 200 words Tasks: SBC(ready,0.5%,476) HEAT(notifyWait,0.0%,321) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.8%,92) MAIN(running,89.6%,1217) IDLE(ready,2.1%,30), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:16:18 ago, cause: power up Last software reset at 2022-05-03 08:36, reason: MemoryProtectionFault mmarValid daccViol, GCodes spinning, available RAM 129940, slot 2 Software reset code 0x4163 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x00400804 BFAR 0x079a070f SP 0x20419a60 Task IDLE Freestk 4290773031 ok Stack: 079a06ff a5a5a5a5 20418198 20424d9c a5a5a5a5 00484b33 00485c9c 01000000 a5a5a5a5 00484171 a5a5a5a5 2041b27c 079a12a3 204337ac 204203fc 20419a8c 20424d34 00000003 20429b1c 20429b1c 20419a8c 20429b14 00000002 20419ae8 4e49414d 00000000 00000000 Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 133 MCU temperature: min 28.3, current 34.5, max 35.5 Supply voltage: min 24.0, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0 Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, mspos 8, reads 37845, writes 14 timeouts 0 Driver 1: standstill, SG min 0, mspos 8, reads 37845, writes 14 timeouts 0 Driver 2: standstill, SG min 0, mspos 8, reads 37849, writes 11 timeouts 0 Driver 3: standstill, SG min 0, mspos 8, reads 37849, writes 11 timeouts 0 Driver 4: standstill, SG min 0, mspos 8, reads 37846, writes 14 timeouts 0 Driver 5: standstill, SG min 0, mspos 8, reads 37846, writes 14 timeouts 0 Date/time: 2022-05-03 08:53:04 Slowest loop: 41.78ms; fastest: 0.04ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 2 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Segments left: 0 Movement lock held by null HTTP* is doing "M122" in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger* is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === CAN === Messages queued 8681, received 7402, lost 0, boc 842 Longest wait 4ms for reply type 6024, peak Tx sync delay 41283, free buffers 50 (min 49), ts 4893/4422/0 Tx timeouts 0,0,112,0,0,61 last cancelled message type 30 dest 127 === SBC interface === Transfer state: 4, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 20251/20251 SPI underruns 0, overruns 0 State: 5, disconnects: 1, timeouts: 1, IAP RAM available 0x2b880 Buffer RX/TX: 0/0-0, open files: 0 === Duet Control Server === Duet Control Server v3.4.0 Code buffer space: 4096 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 38.85, max time between full transfers: 164.1ms, max pin wait times: 78.2ms/7.4ms Codes per second: 0.03 Maximum length of RX/TX data transfers: 3488/216 5/3/2022, 8:52:30 AM Error: Heater 0 not found 5/3/2022, 8:52:27 AM Error: G0/G1: insufficient axes homed 5/3/2022, 8:52:27 AM Error: Heater 0 not found 5/3/2022, 8:52:22 AM Error: Heater 0 not found 5/3/2022, 8:45:17 AM Connection established 5/3/2022, 8:44:13 AM Connection interrupted, attempting to reconnect... Network error 5/3/2022, 8:41:00 AM M122 B10 Diagnostics for board 10: Duet TOOL1LC rev 1.0 or earlier firmware version 3.4.0 (2022-03-15 09:00:04) Bootloader ID: SAMC21 bootloader version 2.2 (2021-01-16b1) All averaging filters OK Never used RAM 4064, free system stack 88 words Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.1%,99) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) TMC(delaying,3.0%,57) MAIN(running,92.0%,427) IDLE(ready,0.0%,40) AIN(delaying,4.9%,142), total 100.0% Last reset 00:04:13 ago, cause: VDD brownout Last software reset at 2021-04-17 12:15, reason: HardFault, available RAM 13692, slot 0 Software reset code 0x0060 ICSR 0x0400f003 SP 0x200019a0 Task CanR Freestk 95 ok Stack: 20008000 0000ffff 002d007f 200020bc 20000018 00006a4b 00005eec 21000000 200047d8 20001c58 20001c54 0000fd85 a5a5a5a5 200047d8 20001c58 200047d8 20001c58 0000ff35 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 00016c25 a5a5a5a5 00000000 00000000 Driver 0: pos 0, 80.0 steps/mm,standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 61390, writes 9, 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 5/13, peak Rx sync delay 213, resyncs 1/0, no step interrupt scheduled VIN voltage: min 23.6, current 23.8, max 23.8 MCU temperature: min 37.3C, current 37.6C, max 38.5C Last sensors broadcast 0x00000000 found 0 172 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 2057, send timeouts 4, received 1451, lost 0, free buffers 37, min 37, error reg ff0000 Last cancelled message type 4519 dest 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0 Accelerometer: none I2C bus errors 4481, naks 4481, other errors 4481 5/3/2022, 8:40:39 AM Connected to 10.1.10.142 -
Another M122 while the printer is currently running (after about 8 hours)
5/3/2022, 8:37:20 PM M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (SBC mode) Board ID: 08DJM-956L2-G43S4-6JTDJ-3SD6S-9S5YD Used output buffers: 1 of 40 (29 max) === RTOS === Static ram: 151000 Dynamic ram: 66060 of which 0 recycled Never used RAM 130180, free system stack 116 words Tasks: SBC(resourceWait:,14.8%,436) HEAT(notifyWait,0.3%,321) Move(notifyWait,23.1%,248) CanReceiv(notifyWait,0.5%,772) CanSender(notifyWait,0.4%,346) CanClock(delaying,0.1%,339) TMC(notifyWait,192.3%,58) MAIN(running,307.5%,1120) IDLE(ready,0.2%,30), total 539.3% Owned mutexes: HTTP(MAIN) === Platform === Last reset 08:21:26 ago, cause: power up Last software reset at 2022-05-03 08:36, reason: MemoryProtectionFault mmarValid daccViol, GCodes spinning, available RAM 129940, slot 2 Software reset code 0x4163 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x00400804 BFAR 0x079a070f SP 0x20419a60 Task IDLE Freestk 4290773031 ok Stack: 079a06ff a5a5a5a5 20418198 20424d9c a5a5a5a5 00484b33 00485c9c 01000000 a5a5a5a5 00484171 a5a5a5a5 2041b27c 079a12a3 204337ac 204203fc 20419a8c 20424d34 00000003 20429b1c 20429b1c 20419a8c 20429b14 00000002 20419ae8 4e49414d 00000000 00000000 Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 135 MCU temperature: min 24.3, current 44.6, max 44.9 Supply voltage: min 23.9, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0 Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/44/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: ok, SG min 0, mspos 635, reads 19126, writes 7 timeouts 0 Driver 1: standstill, SG min 0, mspos 168, reads 19115, writes 19 timeouts 0 Driver 2: standstill, SG min n/a, mspos 8, reads 19134, writes 0 timeouts 0 Driver 3: standstill, SG min n/a, mspos 8, reads 19134, writes 0 timeouts 0 Driver 4: standstill, SG min 0, mspos 456, reads 19117, writes 17 timeouts 0 Driver 5: standstill, SG min 0, mspos 504, reads 19114, writes 19 timeouts 0 Date/time: 2022-05-03 20:37:19 Slowest loop: 65.11ms; fastest: 0.03ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, segments created 24, maxWait 10085088ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 397023, completed 397011, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], CDDA state 3 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 2 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.0 Heater 2 is on, I-accum = 0.0 === GCodes === Segments left: 1 Movement lock held by null HTTP* is doing "M122" in state(s) 0 Telnet is idle in state(s) 0 File* is doing "G0 F9000 X158.378006 Y141.287003" in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger* is idle in state(s) 0 Queue* is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === CAN === Messages queued 636691, received 601401, lost 0, boc 0 Longest wait 5ms for reply type 6024, peak Tx sync delay 364, free buffers 50 (min 43), ts 149683/149683/0 Tx timeouts 0,0,0,0,0,0 === SBC interface === Transfer state: 4, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 59666/59666 SPI underruns 0, overruns 0 State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x2b858 Buffer RX/TX: 3336/720-4080, open files: 0 === Duet Control Server === Duet Control Server v3.4.0 File /opt/dsf/sd/gcodes/Tree_for_Gloomhaven_V2_-_HollowCanopy BIGGER.gcode is selected, processing File: Buffered code: G0 F9000 X158.378 Y141.287 Buffered code: G1 F960 Z30.800 Buffered code: G1 F30000 E0.4000 Buffered code: G1 F6000 X158.378 Y117.887 E0.8406 Buffered code: G1 F2400 E-0.4000 Buffered code: G1 F960 Z31.000 Buffered code: G0 F9000 X156.995 Y116.847 Buffered code: G1 F960 Z30.800 Buffered code: G1 F30000 E0.4000 Buffered code: G1 F6000 X134.305 Y129.947 E0.9411 Buffered code: G1 F2400 E-0.4000 Buffered code: G1 F960 Z31.000 Buffered code: G0 F9000 X132.712 Y126.789 Buffered code: G1 F960 Z30.800 Buffered code: G1 F30000 E0.4000 Buffered code: G1 F6000 X146.160 Y134.554 E0.5578 Buffered code: G0 F9000 X145.642 Y134.487 Buffered code: G1 F6000 X164.805 Y123.423 E0.7948 Buffered code: G0 F9000 X164.859 Y123.179 Buffered code: G1 F6000 X149.637 Y114.391 E0.6314 Buffered code: G1 F2400 E-0.4000 Buffered code: G1 F960 Z31.000 Buffered code: G0 F9000 X148.778 Y114.847 Buffered code: G1 F960 Z30.800 Buffered code: G1 F30000 E0.4000 Buffered code: G1 F6000 X148.778 Y135.311 E0.7351 Buffered code: G0 F9000 X148.778 Y135.693 Buffered code: G1 F6000 X148.778 Y135.821 E0.0046 Buffered code: G1 F2400 E-0.4000 Buffered code: G1 F960 Z31.000 Buffered code: G0 F9000 X156.317 Y139.409 Buffered code: G1 F960 Z30.800 ==> 1456 bytes Code buffer space: 2616 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 39.01, max time between full transfers: 72.1ms, max pin wait times: 66.7ms/9.0ms Codes per second: 13.40 Maximum length of RX/TX data transfers: 3712/1688 5/3/2022, 8:37:14 PM M122 B10 Diagnostics for board 10: Duet TOOL1LC rev 1.0 or earlier firmware version 3.4.0 (2022-03-15 09:00:04) Bootloader ID: SAMC21 bootloader version 2.2 (2021-01-16b1) All averaging filters OK Never used RAM 3608, free system stack 45 words Tasks: Move(notifyWait,12.8%,99) HEAT(notifyWait,6.4%,95) CanAsync(notifyWait,0.0%,61) CanRecv(notifyWait,2.0%,74) CanClock(notifyWait,0.4%,65) TMC(notifyWait,69.9%,57) MAIN(running,337.6%,341) IDLE(ready,0.0%,40) AIN(delaying,115.0%,142), total 544.2% Last reset 08:21:23 ago, cause: power up Last software reset at 2021-04-17 12:15, reason: HardFault, available RAM 13692, slot 0 Software reset code 0x0060 ICSR 0x0400f003 SP 0x200019a0 Task CanR Freestk 95 ok Stack: 20008000 0000ffff 002d007f 200020bc 20000018 00006a4b 00005eec 21000000 200047d8 20001c58 20001c54 0000fd85 a5a5a5a5 200047d8 20001c58 200047d8 20001c58 0000ff35 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 00016c25 a5a5a5a5 00000000 00000000 Driver 0: pos 8962581, 829.8 steps/mm,ok, SG min 0, read errors 0, write errors 0, ifcnt 14, reads 10414, writes 1, timeouts 0, DMA errors 0, CC errors 0, steps req 19118397 done 19118305 Moves scheduled 364680, completed 364679, in progress 1, hiccups 91, step errors 0, maxPrep 705, maxOverdue 563, maxInc 563, mcErrs 0, gcmErrs 0 Peak sync jitter 4/13, peak Rx sync delay 316, resyncs 0/0, next step interrupt due in 808 ticks, enabled VIN voltage: min 23.3, current 23.6, max 23.9 MCU temperature: min 20.3C, current 52.1C, max 54.1C Last sensors broadcast 0x00000001 found 1 215 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 601052, send timeouts 0, received 636524, lost 0, free buffers 37, min 35, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 723, adv 35205/111234 Accelerometer: none I2C bus errors 4481, naks 4481, other errors 4481 -
undefined BlueDust marked this topic as a question
-
It sounds like another case of ESD buildup causing the fault. How well is the print head grounded?
-
@phaedrux
Sorry for the delay in my response. I was somewhat confused by what you said and with other problems I have been having with the my printers just stopped printing for awhile.When you say grounded, are you referring to the black wire, already apart of the wiring diagram or an additional grounding of the printer and/or 1lc board?
Everything on the 1lc board looks tight, but want to confirm what I am looking for before I start chasing my tail.Thanks!
-
See the wiring notes here on grounding: https://docs.duet3d.com/en/Duet3D_hardware/Duet_3_family/Duet_3_Toolboard_1LC#wiring-notes
In general though it is recommended that your metal frame, stepper motors, hotend metal, etc be grounded to prevent the build up of ESD.
-
Is there a picture of how this ground is wired? Unless I am mis understanding what is being grounded, I can't picture where or how the ground wire would be appropriately attached.
Thanks!
-
@bluedust the metal part of the hotend. So somewhere on there you should attach the ground to
-
@jay_s_uk
I guess that is part of my question.
Am I just wrapping wire around the top of the heat sink? Do I need to attach it using solder? Possibly thread a small hole into the top heat sink fin and screw a ground wire to it? Is this ground then being connected to to a screw hole on the 1lc, to the frame, and then to the black wire on the 24 volt side of the power supply or the ground/frame of the power supply? I don't quickly see a ground on the output side of my power supply (was looking for a screw on the chassis).Sorry for my ignorance here, but it has never been super clear to me how people are grounding their printers, to the power supply, or a separate ground to the wall. Most of my printer are plastic parts, and if I was going to ground it, it would have 100 wires all around to bypass all of the plastic, and have never seen anyone actually do it before to take note of (as this would make me ask, how are full 3d printed printers grounded?).
I am really looking to understand to do it right the first time and not just hot glue a wire on to give my self a warm and fuzzy feeling.Thanks for the help!
-
@bluedust from dc42
One option is to connect it to one of the ground pins on the tool board through a 100K resistor.to the hotend. so that should probably be to somewhere on the heatsink. Solder should work fine.Generally, if you have any metal parts on the printer, such as motors, frame etc, they should all be grounded. In the UK, we have a separate ground connection so I use that for grounding the frame etc.
-
@jay_s_uk
Do you ground your printer/frame directly to the wall or do you ground it to the 24v power supply chassis (I currently don't see a way to do this)?Fun, that 3 letter word with "u" in the middle.
-
@bluedust i ground my frame to the incoming ground pin on the IEC C14 socket on my printer. That then goes directly to the wall.
I think the voron wiring instructions are very good. they can be found on page 236 of this https://github.com/VoronDesign/Voron-Trident/blob/main/Manual/Assembly_Manual_Trident.pdfOwns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
@bluedust to clarify: we have strong evidence that extruding plastic through a nozzle builds up static charge on the nozzle and connected metalwork. If this charge has nowhere to go then it tends to arc over to a heater, thermistor or stepper motor connection. That can damage the tool board, or just cause it to lock up until powered down.
If the tool board is mounted directly on a Hemara or similar extruder (such that the stepper motor body is in electrical contact with the hot end), then one option is to put a solder tag or wire under one of the tool board mounting screws and connect that to a ground pin on the tool board, preferably through a resistor of about 100K. The new tool board we have made to fit the Hemera XS has these resistors built in.
Many other schemes are possible. For example if the hot end is electrically isolated from the stepper motor, then you could use a spring to contact the heatsink; or wrap a piece of solid core wire around the heatsink between a pair of fins and twist the ends together to secure it.
It's possible to use a direct connection instead of a 100K resistor, however we suggest using a 100K resistor to prevent excessive current flowing in the event that the hot end gets a short to something else, for example a short between the heater cartridge element and its case.
-
undefined Leonard03 referenced this topic
-
-
@dc42
Looking at getting a 100K resister...
(Please help correct my ignorance as I am new to the electrical engineering side)
It seems there are wattage requirements in picking the correct resister.
Looking at kits on Amazon, I was able to quickly find 1/8 to 2 watt range.
For this requirement, I am assume wattage (dissipating heat?) doesn't really matter and the smaller the physical size of the resister the better, but didn't want to assume and asking for confirmation.Thanks!
-
@bluedust said in 1lc board stopped working, but still responsive to m122:
For this requirement, I am assume wattage (dissipating heat?) doesn't really matter and the smaller the physical size of the resister the better, but didn't want to assume and asking for confirmation.
I think that's a safe assumption.
