HardFault causing failed prints 3.5.1
-
Not sure why, but since upgrading to 3.5.x I've had 3 times where the Duet3 Mini board just stops motion and reboots. Any clue as to the cause from the diagnostics? Most of the time my prints complete just fine, so I'm puzzled as to why this has started happening. Here's my M122:
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.1 (2024-04-19 14:41:25) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: AATGZ-U396U-D65J0-40KM4-NM03Z-HUQXW Used output buffers: 8 of 40 (21 max) === RTOS === Static ram: 103232 Dynamic ram: 121388 of which 0 recycled Never used RAM 13868, free system stack 160 words Tasks: NETWORK(2,nWait 7,13.9%,234) HEAT(3,nWait 6,0.0%,351) Move(4,nWait 6,0.0%,294) CanReceiv(6,nWait 1,0.0%,940) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,334) TMC(4,nWait 6,0.8%,111) MAIN(1,running,84.3%,665) IDLE(0,ready,0.1%,30) AIN(4,delaying,0.9%,269), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:03:24 ago, cause: software Last software reset at 2024-05-05 19:22, reason: HardFault imprec, Gcodes spinning, available RAM 12748, slot 0 Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00000400 ICSR 0x0047d803 BFAR 0xe000ed38 SP 0x20012050 Task NETW Freestk 507 ok Stack: 2002c5e0 20031398 200014e8 00000000 ffffffff 0002ff99 00030058 610ff200 000347e1 2002c3a8 2002c3a8 00000003 0002f715 00000020 20034ee0 00000000 0ded7a33 e000e000 2001e9f8 a5a5a5a5 20034ee0 00000000 0dee8d89 e000e000 2001e9f8 a5a5a5a5 a5a5a5a5 Error status: 0x00 MCU revision 3, ADC conversions started 205089, completed 205088, timed out 0, errs 0 MCU temperature: min 34.3, current 34.3, max 42.0 Supply voltage: min 24.1, current 24.3, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/336/336, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 174, read errors 0, write errors 1, ifcnt 77, reads 10768, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 188, read errors 0, write errors 1, ifcnt 74, reads 10768, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 110, read errors 0, write errors 1, ifcnt 52, reads 10765, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 2, read errors 0, write errors 1, ifcnt 226, reads 10768, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 2, read errors 0, write errors 1, ifcnt 53, reads 10765, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2024-05-05 19:25:35 Cache data hit count 378313878 Slowest loop: 4.71ms; fastest: 0.16ms === Storage === Free file entries: 20 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 2.1ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 3, maxWait 40727ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === Scheduled moves 1, completed 1, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], CDDA state -1 === DDARing 1 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 1 is on, I-accum = 0.0 === GCodes === Movement locks held by null, null HTTP is idle 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 Q0 segments left 0, axes/extruders owned 0x0000807 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === Filament sensors === check 0 clear 980104 Extruder 0 sensor: ok === CAN === Messages queued 1844, received 0, lost 0, errs 965983, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 26 (min 26), ts 1025/0/0 Tx timeouts 0,0,1024,0,0,818 last cancelled message type 4514 dest 127 === Network === Slowest loop: 10.47ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 2.1.0 MAC address f4:cf:a2:6f:9a:ba Module reset reason: Power up, Vcc 3.36, flash size 2097152, free heap 43052 WiFi IP address 192.168.1.12 Signal strength -56dBm, channel 9, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0
-
-
@Nate-Nygren please see my response to this thread which I see you have also contributed to https://forum.duet3d.com/topic/35611/my-printer-reboots-alone/14.
-