Error: Expansion board 119 stopped sending status (3.6.0-rc.2)
-
Morning I've just had a print fail with a comm issue, as I'm running RC2 I figured I'd best post the results of M122
B119 (Boxturtle) failed first taken whilst print paused -
M122 B119 Diagnostics for board 119: === Diagnostics === RepRapFirmware for STM32H7 based Boards (afclite1_h723) version 3.6.0-rc.2 (2025-04-01 15:28:48) running on STM32H723 (expansion mode) Board ID: 310L0-0N1KU-D4MUS-6M9D8-GDUYW-70000 Bootloader: afclite1_h723 Boot loader IOMode:255 S:0 C:1 version 1.1.0 Used output buffers: 0 of 40 (1 max) === RTOS === Static ram: 43728 Dynamic ram: 114512 of which 488 recycled Never used RAM 89016, free system stack 118 words Tasks: NETWORK(1,ready,4.6%,513) HEAT(3,nWait 6,0.0%,331) Move(4,nWait 6,0.0%,337) TMC22xx(4,delaying,0.6%,41) CanReceiv(6,running,0.0%,86) CanSender(5,nWait 7,0.0%,336) FSWRITE(2,nWait 4,0.0%,161) MAIN(1,ready,94.8%,500) IDLE(0,ready,0.0%,29), total 100.0% Owned mutexes: === Platform === Last reset 07:57:28 ago, cause: software Last software reset at 2025-05-13 21:03, reason: StuckInSpinLoop, FilamentSensors spinning, available RAM 89016, slot 0 Software reset code 0x088d HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0440f80f BFAR 0x00000000 SP 0x2400511c Task NETW Freestk 1073739571 ok Stack: ffffffed 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 40533333 3ea32ff0 3b800000 484e1e51 442a8000 80000010 080ac4cb 00000010 080a867f === Storage === Free file entries: 20 SD card 0 detected SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === Segments created 14, maxWait 0ms, bed comp in use: none, height map offset 0.000, hiccups added 0/3 (58.23/69.95ms), max steps late 0, ebfmin 0.00, ebfmax 0.00 Pos req/act/dcf: 0.00/0/0.00 0.00/0/0.00 26880408.00/26884293/-0.20 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 Peak sync jitter 2/39, peak Rx sync delay 199, resyncs 14/6 No step interrupt scheduled Driver 0: standstill 2209, SG min 0, reads 27966, writes 9, error r/w 0/1, ifcnt 21, timeout 0 Driver 1: standstill 2209, SG min 0, reads 27966, writes 9, error r/w 0/1, ifcnt 19, timeout 0 Driver 2: standstill 2209, SG min 0, reads 27963, writes 11, error r/w 0/1, ifcnt 31, timeout 0 Driver 3: standstill 2209, SG min 0, reads 27965, writes 9, error r/w 0/1, ifcnt 19, timeout 0 Driver 4: Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Phase step loop runtime (us): min=5726621, max=1, frequency (Hz): min=750000, max=0 === DDARing 0 === Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0] Segments left 0, axes/extruders owned 0x00000000, drives owned 0x00000000 Code queue is empty === DDARing 1 === Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0] Segments left 0, axes/extruders owned 0x00000000, drives owned 0x00000000 Code queue is empty === Heat === Bed heaters -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1 -1 -1 -1 -1, ordering errs 0 === CAN === Messages queued 229366, received 278758, lost 0, ignored 221, errs 0, boc 2 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 1/0/0 Tx timeouts 0,0,0,0,0,76658 last cancelled message type 0 dest 1 Motion dup 0, oos 6/4/0/21B1 (3HC) failed next - unable to receive log
M122 B1
CAN response timeout: board 1, req type 6024, RID 111pressed emergency stop - board still not responding
power off and on -
M122 B1 Diagnostics for board 1: Duet EXP3HC rev 1.02 or later firmware version 3.6.0-rc.2 (2025-03-31 12:21:29) Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10) All averaging filters OK Never used RAM 169932, free system stack 202 words Tasks: Move(3,nWait 7,0.0%,181) TMC(2,nWait 6,7.1%,95) HEAT(2,nWait 6,0.0%,132) CanAsync(5,nWait 4,0.0%,70) CanRecv(3,nWait 1,0.0%,74) CanClock(5,nWait 1,0.0%,64) MAIN(1,running,91.6%,413) IDLE(0,ready,0.0%,39) AIN(2,delaying,1.2%,265), total 100.0% Owned mutexes: Last reset 00:00:24 ago, cause: power up Last software reset data not available Moves scheduled 0, hiccups 0 (0.00/0.00ms), segs 0, step errors 0 (types 0x0), maxLate 0 maxPrep 0, ebfmin 0.00 max 0.00 Peak sync jitter 1/9, peak Rx sync delay 181, resyncs 0/0, no timer interrupt scheduled, next step interrupt due in 4276399523 ticks, disabled VIN voltage: min 24.3, current 24.3, max 24.3 V12 voltage: min 12.2, current 12.2, max 12.2 MCU temperature: min 36.2C, current 36.8C, max 36.8C Driver 0: pos 0, 800.0 steps/mm, standstill, SG min 0, mspos 8, reads 30007, writes 19 timeouts 0 Driver 1: pos 0, 800.0 steps/mm, standstill, SG min 0, mspos 8, reads 30008, writes 19 timeouts 0 Driver 2: pos 0, 800.0 steps/mm, standstill, SG min 0, mspos 8, reads 30008, writes 19 timeouts 0 Last sensors broadcast 0x00003000 found 2 15 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 414, send timeouts 0, received 318, lost 0, ignored 0, errs 0, boc 0, free buffers 38, min 38, error reg 0 dup 0, oos 0/0/0/0, rxMotionDelay 0B124 (SHT36) failed last - M122 B124
CAN response timeout: board 124, req type 6024, RID 113after power off and on -
M122 B124 Diagnostics for board 124: Duet SHT36MAX3 firmware version 3.6.0-rc.2 (2025-04-01 15:34:20) Bootloader ID: All averaging filters OK Never used RAM 222576, free system stack 434 words Tasks: Move(3,nWait 7,0.0%,140) TMC(2,delaying,1.9%,52) HEAT(2,nWait 6,0.1%,128) CanAsync(5,nWait 4,0.0%,56) CanRecv(3,nWait 1,0.0%,356) CanClock(5,nWait 1,0.0%,334) ACCEL(3,nWait 6,0.0%,72) MAIN(1,running,95.6%,441) IDLE(0,ready,0.1%,26) USBD(2,blocked,0.0%,150) AIN(2,delaying,2.1%,248), total 100.0% Owned mutexes: Last reset 00:03:31 ago, cause: power up or brownout Last software reset data not available Moves scheduled 0, hiccups 0 (0.00/0.00ms), segs 0, step errors 0 (types 0x0), maxLate 0 maxPrep 0, ebfmin 0.00 max 0.00 Peak sync jitter 1/12, peak Rx sync delay 333, resyncs 0/0, no timer interrupt scheduled MCU temperature: min 61.3C, current 61.3C, max 63.2C Driver 0: pos 0, 885.1 steps/mm, standstill, SG min 0, read errors 0, write errors 0, ifcnt 16, reads 39953, writes 16, timeouts 0, DMA errors 0, CC errors 0 Last sensors broadcast 0x00000002 found 1 28 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 6794, send timeouts 0, received 2698, lost 0, ignored 0, errs 0, boc 0, free buffers 38, min 38, error reg 0 dup 0, oos 0/0/0/0, rxMotionDelay 0 Accelerometer: LIS2DW, status: 00 Inductive sensor: never activated I2C bus errors 0, naks 0, contentions 0, other errors 0Any help or direction would be appreciated
6HC Voron Trident based, 6XD CNC, Mini 5 polar printer
-
@jumpedwithbothfeet Generally, I'd suspect a CAN wiring issue. What order are the boards wired in? Ideally, please provide an M122 report from the mainboard, and your config.g.
Ian
Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth
-
@jumpedwithbothfeet Was the M122 report from board 119 taken without needing to do any sort of reset? The M122 for board 119 is showing a possible crash at 2025-05-13 21:03 how does that date/time relate to when you had the stopped sending status message? As mentioned above I'd suspect some sort of wiring problem (which may have possibly caused the previously reported crash?), but it is hard to be sure. Has the printer been working ok previously?
-
@droftarts I will recheck my wiring, the order of things go 6HC > 3HC > tool distribution board and the boxturtle, SHT36 run of stubs from that.
M122 B0 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.6.0-rc.2 (2025-03-31 12:17:13) running on Duet 3 MB6HC v1.0 or earlier (standalone mode) Board ID: 08DJM-956L2-G43S8-6JKDG-3SS6L-KB12H Used output buffers: 1 of 40 (23 max) === RTOS === Static ram: 137420 Dynamic ram: 134012 of which 84 recycled Never used RAM 66828, free system stack 186 words Tasks: NETWORK(1,ready,24.6%,180) ETHERNET(5,nWait 7,0.1%,316) HEAT(3,nWait 6,0.0%,362) Move(4,nWait 6,0.0%,333) TMC(4,nWait 6,3.2%,377) CanReceiv(6,nWait 1,0.1%,796) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,350) MAIN(1,running,71.8%,103) IDLE(0,ready,0.2%,29) USBD(3,blocked,0.0%,149), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:01:16 ago, cause: power up Last software reset at 2025-05-14 05:22, reason: User, Gcodes spinning, available RAM 67624, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0043c000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a === Storage === Free file entries: 20 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 5.4ms, write time 4.2ms, max retries 0 === Move === Segments created 0, maxWait 0ms, bed comp in use: none, height map offset 0.000, hiccups added 0/0 (0.00/0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00 Pos req/act/dcf: 0.00/0/0.00 0.00/0/0.00 0.00/0/0.00 Next step interrupt due in 248 ticks, disabled Driver 0: standstill, SG min n/a, mspos 8, reads 20472, writes 19 timeouts 0 Driver 1: standstill, SG min n/a, mspos 8, reads 20472, writes 19 timeouts 0 Driver 2: standstill, SG min n/a, mspos 8, reads 20472, writes 19 timeouts 0 Driver 3: standstill, SG min n/a, mspos 8, reads 20472, writes 19 timeouts 0 Driver 4: standstill, SG min n/a, mspos 8, reads 20480, writes 11 timeouts 0 Driver 5: standstill, SG min n/a, mspos 8, reads 20480, writes 11 timeouts 0 Phase step loop runtime (us): min=0, max=64, frequency (Hz): min=1503, max=2964 === DDARing 0 === Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0] Segments left 0, axes/extruders owned 0x00000000, drives owned 0x00000000 Code queue is empty === DDARing 1 === Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0] Segments left 0, axes/extruders owned 0x00000000, drives owned 0x00000000 Code queue is empty === Heat === Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1 -1 -1 -1 -1, ordering errs 0 === GCodes === Movement locks held by null, null HTTP is ready with "M122 B0" 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 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 === Filament sensors === Driver 31: no filament === CAN === Messages queued 706, received 3037, lost 0, ignored 0, errs 0, boc 0 Longest wait 2ms for reply type 6053, peak Tx sync delay 186, free buffers 50 (min 49), ts 361/360/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 5.87ms; fastest: 0.03ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 === Multicast handler === Responder is inactive, messages received 0, responses 0 = Ethernet = Interface state: active Error counts: 0 0 0 1 0 0 Socket states: 6 2 2 2 2 0 0 0 0@gloomyandy yes the M122 report was from the boxturtle without anything but a pause print, unfortunately I didn't take note of the time the fault was reported on DWC, I know the boxturtle can have issues with static discharge could this be part of the problem? I had already purchased the parts to ground the motors etc and they arrived to day so I'll install them as a matter of course, along with rechecking my wiring.
-
@jumpedwithbothfeet If this happened today (the 14th) then the crash in your board 119 log is probably nothing to do with it (as that happened yesterday the 13th). That may have been caused by a static problem, but it is hard to be sure. The board 119 log seems to show that it had been running for almost eight hours when you produced the m122 log. I guess the question is did this happen today or yesterday (which it may not now be possible to establish)? If it happens again make a note of the times. Do you know when you started the print? If that was before 21:00 on the 13th, then it may well be that the crash then caused the CAN-FD problems.
-
@gloomyandy I started the print way before 18:00 yesterday so I imagine its about right and it failed on the 13th and it only failed because it stopped extruding, the printhead was still happily moving around this morning when I found it.
The printer worked without any major issues just new build teething problems prior to installing the boxturtle, I did have CAN issues with the turtle but Jay kindly helped me sort out the stubs and soft/firmware issues I had, I guess I just check the CAN wiring and fit the ground harness to the boxturtle and try again! I'll report back if it happens again
-
@droftarts @gloomyandy, as a follow up, I think I've found the culprit, I disconnected the boxturtle and booted the printer up all remaining boards connect without issue, with it connected I had a cascade failure of all boards but the mainboard, I belled the boxturtle cable out and it was fine, I did however find the positive and both CAN wires retracted in the plug, I've made good and now the printer is up and running the same print now, fingers crossed it completes with no issue!
