Duet 3 mini5+ randomly resets during printing
-
@wschadow thanks for your report. Please also post the address of the network receive buffer, which you can obtain like this:
- Send M122 P106. Example response:
m122p106 Platform 2001d138-2001e737 SbcInterface 2001e740-2001ea70 Network 2001ea80-2001eb67 <--------------- GCodes 2001eb70-2001ff6f Move 20023ff8-20024d33 Heat 20025110-20025237 PrintMonitor 20025240-2002544f FansManager 20025458-200254d7 PortControl 200254e0-2002550f Display 20025518-20025533 ExpansionManager 20025540-200282f7- Send M122 P1007 A{0x########+8} where ######## is the first hex value in the Network line of the previous response. Example response:
m122p1007 a{0x2001ea80+8} 2001ea88: 2002c420- Send M122 P1007 A{0x########+136} where ######## is the second number in that response. Example response:
m122p1007 a{0x2002c420+136} 2002c4a8: 20032dd0The second number (0x20032dd0 in this example) is the value I need.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 here is another one
9/20/2024, 8:02:10 PM M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.3 (2024-09-18 11:25:48) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: UF2UK-QQ6KL-K65J0-409NA-L7X1Z-Z1P2J
Used output buffers: 11 of 40 (32 max)
=== RTOS ===
Static ram: 103368
Dynamic ram: 124088 of which 0 recycled
Never used RAM 11440, free system stack 190 words
Tasks: NETWORK(2,nWait 7,14.9%,228) HEAT(3,nWait 6,0.0%,350) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.1%,798) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,348) TMC(4,nWait 6,0.8%,101) MAIN(1,running,83.3%,665) IDLE(0,ready,0.0%,29) AIN(4,delaying,0.8%,259), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:16:54 ago, cause: software
Last software reset at 2024-09-20 19:45, reason: HardFault imprec, Platform spinning, available RAM 9808, slot 1
Software reset code 0x4060 HFSR 0x40000000 CFSR 0x00000400 ICSR 0x00000803 BFAR 0xe000ed38 SP 0x20012008 Task NETW Freestk 482 ok
Stack: 2002c658 00000000 200014e4 00000165 20033872 0003039d 00034ddc 810f0000 00030389 00000000 00000000 00000000 200326dc 00000800 200363f0 2002c640 2001882c 2002c496 2001882c 2001ea80 00030523 00000000 00000000 00000000 200120b8 00000014 b5ddb6d6
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 761086, completed 761085, timed out 0, errs 0
MCU temperature: min 41.8, current 41.8, max 57.1
Supply voltage: min 23.8, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/43, heap memory allocated/used/recyclable 2048/1844/1020, gc cycles 16
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 30, reads 53382, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 14, read errors 0, write errors 1, ifcnt 35, reads 53382, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 266, read errors 0, write errors 1, ifcnt 42, reads 53381, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 310, read errors 0, write errors 1, ifcnt 41, reads 53382, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 2, read errors 0, write errors 1, ifcnt 30, reads 53382, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2024-09-20 20:02:09
Cache data hit count 1957929928
Slowest loop: 9.15ms; fastest: 0.16ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, 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 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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
=== 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 0x0000000
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== Filament sensors ===
check 0 clear 0
Extruder 1: no data received, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
=== CAN ===
Messages queued 9165, received 41127, lost 0, errs 0, boc 0
Longest wait 2ms for reply type 6053, peak Tx sync delay 161, free buffers 26 (min 25), ts 5074/5073/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 8.81ms; 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 c4:5b:be:46:4f:6c
Module reset reason: Power up, Vcc 3.43, flash size 2097152, free heap 39348
WiFi IP address 192.168.3.139
Signal strength -57dBm, channel 1, mode 802.11n, reconnections 0
Clock register 00002001
Socket states: 0 0 0 0 0 0 0 0 -
@dc42 and the output from 122 p106
9/20/2024, 8:04:08 PM M122 p106
Platform 2001d138-2001e737
SbcInterface 2001e740-2001ea70
Network 2001ea80-2001eb67
GCodes 2001eb70-2001ff6f
Move 20023ff8-20024d33
Heat 20025110-20025237
PrintMonitor 20025240-2002544f
FansManager 20025458-200254d7
PortControl 200254e0-2002550f
Display 20025518-20025533
ExpansionManager 20025540-200282f7 -
9/20/2024, 8:07:48 PM
m122p1007 a{0x2001ea80+8}
2001ea88: 2002c4209/20/2024, 8:09:10 PM
m122p1007 a{0x2001eb67+136}
2001ebef: 00000000 -
@dc42 I upgraded to RRF 3.5.3 today. During the 2nd print I experienced a hard reset. Please see the M122 report underneath:
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.3 (2024-09-18 11:25:48) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: 7MPG2-K396U-D65J0-40KMQ-JQ03Z-Z0D1Q Used output buffers: 3 of 40 (18 max) === RTOS === Static ram: 103368 Dynamic ram: 121604 of which 0 recycled Never used RAM 16776, free system stack 198 words Tasks: NETWORK(2,nWait 7,13.5%,217) HEAT(3,nWait 6,0.0%,350) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.0%,939) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,334) TMC(4,nWait 6,0.8%,110) MAIN(1,running,84.6%,665) IDLE(0,ready,0.2%,29) AIN(4,delaying,0.8%,268), total 100.0% Owned mutexes: === Platform === Last reset 00:05:29 ago, cause: reset button Last software reset time unknown, reason: HardFault invState, Gcodes spinning, available RAM 27292, slot 2 Software reset code 0x4863 HFSR 0x40000000 CFSR 0x00020000 ICSR 0x00000803 BFAR 0xe000ed38 SP 0x20012580 Task TMC Freestk 125 ok Stack: 2001948c 20012334 200014e8 e000e000 00000060 00091d55 00000000 6100f000 00000000 00000000 00000000 cf410005 0041ff05 d7000000 0002ff05 3a130000 00000000 00000000 00000000 00000000 00000053 2003b5d0 20012c24 00000dae 20019494 20012e5c 2001261c Error status: 0x00 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 247196, completed 247196, timed out 0, errs 0 MCU temperature: min 31.8, current 31.8, max 34.9 Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes 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 2, read errors 0, write errors 1, ifcnt 27, reads 17320, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 27, reads 17320, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 4, read errors 0, write errors 1, ifcnt 23, reads 17319, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 21, reads 17319, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 27, reads 17320, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2024-09-21 16:43:50 Cache data hit count 603090100 Slowest loop: 25.74ms; fastest: 0.16ms === Storage === Free file entries: 20 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 1.3ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, 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 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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 === 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 0x0000000 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === Filament sensors === check 0 clear 1548989 Extruder 0: no data received, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0 === CAN === Messages queued 2965, received 0, lost 0, errs 1595525, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 26 (min 26), ts 1648/0/0 Tx timeouts 0,0,1647,0,0,1316 last cancelled message type 4514 dest 127 === Network === Slowest loop: 28.03ms; 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 d8:bf:c0:15:0a:5c Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 42652 WiFi IP address 172.16.0.142 Signal strength -47dBm, channel 5, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0 -
@Maurits Thanks for the report, sorry this is continuing to be a problem. Can you post the same debug info as the post above? See @dc42's post above, here https://forum.duet3d.com/post/345163, for what is needed.
You asked if this could be a hardware fault. Yes, it's possible; I'm not currently sure if the bug we're trying to chase down here is the same one. I'm not aware of other people having the same 'HardFault' reset in 3.4.5. In the past, this fault has usually been to do with static electricity (created by the filament rubbing on the extruder) discharging causing memory corruption. Our general advice to avoid that is here: https://docs.duet3d.com/en/User_manual/Connecting_hardware/Power_wiring#grounding
Ian
-
@dc42 Today I tried to tun in SBC mode, this is not stable as well. Here is the output of m122, m122 p106
9/23/2024, 1:44:01 PM M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.3 (2024-09-18 11:25:48) running on Duet 3 Mini5plus WiFi (SBC mode) Board ID: UF2UK-QQ6KL-K65J0-409NA-L7X1Z-Z1P2J Used output buffers: 1 of 40 (40 max) === RTOS === Static ram: 103368 Dynamic ram: 111484 of which 0 recycled Never used RAM 23684, free system stack 134 words Tasks: SBC(2,ready,1.8%,813) HEAT(3,nWait 6,0.0%,350) Move(4,nWait 6,0.8%,241) CanReceiv(6,nWait 1,0.1%,773) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,348) TMC(4,nWait 6,0.8%,101) MAIN(2,running,95.2%,753) IDLE(0,ready,0.4%,29) AIN(4,delaying,0.8%,259), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:27:46 ago, cause: software Last software reset time unknown, reason: User, Gcodes spinning, available RAM 27616, slot 0 Software reset code 0x6003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 1250473, completed 1250473, timed out 0, errs 0 MCU temperature: min 34.9, current 46.1, max 55.8 Supply voltage: min 23.4, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/43, heap memory allocated/used/recyclable 2048/1448/624, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 44, reads 22122, writes 26, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 2, read errors 0, write errors 1, ifcnt 56, reads 22111, writes 37, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 63, reads 22099, writes 48, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 60, reads 22099, writes 48, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 37, reads 22122, writes 26, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2024-09-23 12:44:01 Cache data hit count 2957030106 Slowest loop: 433.46ms; fastest: 0.09ms === Storage === Free file entries: 20 SD card 0 not detected, interface speed: 0.0MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 15, maxWait 132891ms, bed compensation in use: mesh, 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 2524, completed 2524, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 2], 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 === GCodes === Movement locks held by null, null HTTP* is doing "M122" in state(s) 0 Telnet is idle in state(s) 0 File* is idle in state(s) 3 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 0 Extruder 1: no data received, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0 === CAN === Messages queued 19356, received 68219, lost 0, errs 0, boc 0 Longest wait 4ms for reply type 6013, peak Tx sync delay 272, free buffers 26 (min 24), ts 8333/8332/0 Tx timeouts 0,0,0,0,0,0 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 52443/3526 SPI underruns 0, overruns 0 State: 5, disconnects: 1, timeouts: 1 total, 1 by SBC, IAP RAM available 0x0cd38 Buffer RX/TX: 0/0-0, open files: 0 === Duet Control Server === Duet Control Server version 3.5.3 (2024-09-19 12:12:39, 32-bit) HTTP+Executed: > Executing M122 Code buffer space: 4096 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 31.60, max time between full transfers: 278.9ms, max pin wait times: 77.0ms/12.3ms Codes per second: 2.90 Maximum length of RX/TX data transfers: 4476/1220 9/23/2024, 1:45:38 PM PrintMonitor 20025240-2002544f FansManager 20025458-200254d7 PortControl 200254e0-2002550f Display 20025518-20025533 ExpansionManager 20025540-200282f7 9/23/2024, 1:45:38 PM M122 p106 9/23/2024, 1:45:38 PM Platform 2001d138-2001e737 SbcInterface 2001e740-2001ea70 Network 2001ea80-2001eb67 GCodes 2001eb70-2001ff6f Move 20023ff8-20024d33 Heat 20025110-20025237 9/23/2024, 1:51:17 PM m122p1007 a{0x2001ea80+8} 2001ea88: 2002c420 9/23/2024, 1:52:08 PM m122p1007 a{0x2001eb67+136} 2001ebef: 00000000 -
@dc42 and a second one
9/23/2024, 12:43:41 PM M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.3 (2024-09-18 11:25:48) running on Duet 3 Mini5plus WiFi (SBC mode) Board ID: UF2UK-QQ6KL-K65J0-409NA-L7X1Z-Z1P2J Used output buffers: 10 of 40 (40 max) === RTOS === Static ram: 103368 Dynamic ram: 111484 of which 0 recycled Never used RAM 23900, free system stack 140 words Tasks: SBC(2,rWait:,1.8%,805) HEAT(3,nWait 6,0.0%,350) Move(4,nWait 6,0.1%,241) CanReceiv(6,nWait 1,0.1%,794) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,348) TMC(4,nWait 6,0.8%,101) MAIN(2,running,95.1%,753) IDLE(0,ready,1.2%,29) AIN(4,delaying,0.8%,259), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:10:31 ago, cause: power up Last software reset at 2024-09-20 19:45, reason: HardFault imprec, Platform spinning, available RAM 9808, slot 1 Software reset code 0x4060 HFSR 0x40000000 CFSR 0x00000400 ICSR 0x00000803 BFAR 0xe000ed38 SP 0x20012008 Task NETW Freestk 482 ok Stack: 2002c658 00000000 200014e4 00000165 20033872 0003039d 00034ddc 810f0000 00030389 00000000 00000000 00000000 200326dc 00000800 200363f0 2002c640 2001882c 2002c496 2001882c 2001ea80 00030523 00000000 00000000 00000000 200120b8 00000014 b5ddb6d6 Error status: 0x04 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 474054, completed 474052, timed out 0, errs 0 MCU temperature: min 36.2, current 47.6, max 47.6 Supply voltage: min 23.4, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/43, heap memory allocated/used/recyclable 2048/1136/312, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 23, reads 33185, writes 23, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 28, reads 33180, writes 28, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 37, reads 33171, writes 37, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 35, reads 33172, writes 35, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 23, reads 33185, writes 23, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2024-09-23 11:41:50 Cache data hit count 1238108594 Slowest loop: 471.26ms; fastest: 0.09ms === Storage === Free file entries: 20 SD card 0 not detected, interface speed: 0.0MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 6, maxWait 197430ms, bed compensation in use: mesh, 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 363, completed 363, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 2], 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 === GCodes === Movement locks held by null, 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 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 0 Extruder 1: no data received, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0 === CAN === Messages queued 6076, received 25517, lost 0, errs 0, boc 0 Longest wait 2ms for reply type 6031, peak Tx sync delay 153, free buffers 26 (min 24), ts 3157/3156/0 Tx timeouts 0,0,0,0,0,0 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 22250/968 SPI underruns 0, overruns 0 State: 5, disconnects: 2, timeouts: 2 total, 2 by SBC, IAP RAM available 0x0cd38 Buffer RX/TX: 0/0-0, open files: 0 === Duet Control Server === Duet Control Server version 3.5.3 (2024-09-19 12:12:39, 32-bit) HTTP+Executed: > Executing M122 Code buffer space: 4096 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 30.79, max time between full transfers: 22239.4ms, max pin wait times: 1223.9ms/72.1ms Codes per second: 1.04 Maximum length of RX/TX data transfers: 4408/888 Send M122 P106 9/23/2024, 12:49:37 PM PrintMonitor 20025240-2002544f FansManager 20025458-200254d7 PortControl 200254e0-2002550f Display 20025518-20025533 ExpansionManager 20025540-200282f7 9/23/2024, 12:49:37 PM Platform 2001d138-2001e737 SbcInterface 2001e740-2001ea70 Network 2001ea80-2001eb67 GCodes 2001eb70-2001ff6f Move 20023ff8-20024d33 Heat 20025110-20025237 9/23/2024, 12:51:08 PM m122p1007 a{0x2001ea80+8} 2001ea88: 2002c420 9/23/2024, 12:52:12 PM m122p1007 a{0x2001eb67+136} 2001ebef: 00000000 -
@wschadow whatever issue you are having in SBC mode is not the same problem. Please start a separate thread for it, and include in it description of the problem symptoms.
-
@wschadow said in Duet 3 mini5+ randomly resets during printing:
9/20/2024, 8:07:48 PM
m122p1007 a{0x2001ea80+8}
2001ea88: 2002c4209/20/2024, 8:09:10 PM
m122p1007 a{0x2001eb67+136}
2001ebef: 00000000Unfortunately that's not the info I need. The value reported by the first M122 P1007 commandsneed to be fed into the second one; so the second command should have been:
m122p1007 a{0x2002c420+136}
Note, in SBC mode all the values will be different and so not relevant to this issue.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
undefined dc42 referenced this topic
-
All, please see https://forum.duet3d.com/topic/36689/random-hard-fault-resets-on-duet-3-mini-wifi and provide any additional reports there. I am locking this thread.
-
undefined dc42 locked this topic
