Duet 3 mini5+ nightly restarts 3.5.2
-
@jay_s_uk
I will upgrade as soon as the printing is finished on Duet Printer 2 -
Another occurrence overnight last night.
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: 65LYX-8Q6KL-K65J0-409N0-NP02Z-ZFK3T Used output buffers: 1 of 40 (26 max) === RTOS === Static ram: 103232 Dynamic ram: 119916 of which 24 recycled Never used RAM 15388, free system stack 150 words Tasks: NETWORK(1,ready,209.7%,196) HEAT(3,nWait 6,0.4%,372) Move(4,nWait 6,0.1%,355) CanReceiv(6,nWait 1,0.5%,808) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.3%,348) TMC(4,nWait 6,29.5%,102) MAIN(1,running,411.0%,677) IDLE(0,ready,0.3%,30) AIN(4,delaying,31.0%,260), total 682.9% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 09:48:56 ago, cause: software Last software reset at 2024-06-19 22:49, reason: HardFault bfarValid precise, Gcodes spinning, available RAM 15364, slot 2 Software reset code 0x0063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00000803 BFAR 0x00000004 SP 0x20011ff0 Task NETW Freestk 483 ok Stack: 00000160 00000002 200014e8 0000015f ffffffff 000a07ef 0002ff8e 810f0000 0002ff85 00000000 00000000 00000000 20030dfc 00000800 2002c5c8 2002c5c8 00000004 2002c41e 200187fc 2001e9f8 0003011f 00000000 00000000 00000000 200120a0 00000014 00000000 Error status: 0x00 MCU revision 3, ADC conversions started 35336574, completed 35336574, timed out 0, errs 0 MCU temperature: min 38.1, current 39.8, max 40.4 Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/12/12, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 32, reads 24771, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 32, reads 24771, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 32, reads 24770, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 32, reads 24770, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 32, reads 24771, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2024-06-20 08:38:41 Cache data hit count 4294967295 Slowest loop: 606.35ms; fastest: 0.16ms === Storage === Free file entries: 19 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 2.1ms, write time 110.2ms, 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 -1 -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 === CAN === Messages queued 176682, received 282694, lost 0, errs 1, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 296, free buffers 26 (min 26), ts 176682/176681/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 302.72ms; 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 41307, noresp 247 Firmware version 2.1.0 MAC address e8:68:e7:e1:4e:d0 Module reset reason: Power up, Vcc 3.42, flash size 2097152, free heap 42228 WiFi IP address 10.1.10.46 Signal strength -57dBm, channel 11, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 4 0 4 4 0 0 0 0Log data from all of yesterday and up till the above M122 query.
2024-06-19 09:01:12 [warn] HTTP client 10.1.10.9 login succeeded (session key 1729998681) 2024-06-19 09:01:38 [warn] HTTP client 10.1.10.9 login succeeded (session key 3562654751) 2024-06-19 09:01:54 [warn] HTTP client 10.1.10.9 login succeeded (session key 224611796) 2024-06-19 09:02:33 [warn] HTTP client 10.1.10.9 login succeeded (session key 4179562653) 2024-06-19 09:03:20 [warn] HTTP client 10.1.10.9 login succeeded (session key 2552758708) 2024-06-19 09:03:41 [warn] HTTP client 10.1.10.9 login succeeded (session key 2600420170) 2024-06-19 09:03:56 [warn] HTTP client 10.1.10.9 login succeeded (session key 1537291509) 2024-06-19 09:05:53 [warn] HTTP client 10.1.10.9 login succeeded (session key 2699331822) 2024-06-19 09:06:03 [warn] HTTP client 10.1.10.9 login succeeded (session key 2564007033) 2024-06-19 09:07:55 [warn] HTTP client 10.1.10.9 login succeeded (session key 3369922870) 2024-06-19 09:08:26 [warn] HTTP client 10.1.10.9 login succeeded (session key 1329585505) 2024-06-19 09:11:00 [warn] HTTP client 10.1.10.9 login succeeded (session key 3908567028) 2024-06-19 09:11:44 [warn] HTTP client 10.1.10.9 login succeeded (session key 3973151085) 2024-06-19 09:13:07 [warn] HTTP client 10.1.10.9 login succeeded (session key 3663609420) 2024-06-19 09:13:36 [warn] HTTP client 10.1.10.9 login succeeded (session key 3203760620) 2024-06-19 10:06:54 [warn] HTTP client 10.1.10.9 login succeeded (session key 3770264939) 2024-06-19 10:08:04 [warn] HTTP client 10.1.10.9 login succeeded (session key 864774496) 2024-06-19 10:08:42 [warn] HTTP client 10.1.10.9 login succeeded (session key 3541419882) power up + 00:00:00 [info] Event logging started at level debug power up + 00:00:00 [info] Running: Duet 3 Mini5plus WiFi: 3.5.1 (2024-04-19 14:41:25) power up + 00:00:00 [debug] Done! power up + 00:00:00 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running. power up + 00:00:00 [warn] WiFi module started power up + 00:00:08 [warn] WiFi module is connected to access point SD3D-24, IP address 10.1.10.46 power up + 00:00:11 [warn] HTTP client 10.1.10.9 login succeeded (session key 2501685194) 2024-06-19 22:49:56 [warn] Date and time set at power up + 00:00:11 2024-06-19 23:05:56 [warn] HTTP client 10.1.10.9 login succeeded (session key 3338192771) 2024-06-19 23:19:44 [warn] HTTP client 10.1.10.9 login succeeded (session key 995382963) 2024-06-19 23:23:41 [warn] HTTP client 10.1.10.9 login succeeded (session key 577045155) 2024-06-20 00:02:51 [warn] HTTP client 10.1.10.9 login succeeded (session key 2819024432) 2024-06-20 00:03:35 [warn] HTTP client 10.1.10.9 login succeeded (session key 1555340288) 2024-06-20 00:03:36 [warn] HTTP client 10.1.10.9 login succeeded (session key 1829290603) 2024-06-20 00:32:14 [warn] HTTP client 10.1.10.9 login succeeded (session key 135584297) 2024-06-20 00:32:16 [warn] HTTP client 10.1.10.9 login succeeded (session key 3569997682) 2024-06-20 00:32:36 [warn] HTTP client 10.1.10.9 login succeeded (session key 2193291301) 2024-06-20 00:32:57 [warn] HTTP client 10.1.10.9 login succeeded (session key 1877243154) 2024-06-20 00:33:18 [warn] HTTP client 10.1.10.9 login succeeded (session key 3649632143) 2024-06-20 00:33:29 [warn] HTTP client 10.1.10.9 login succeeded (session key 3785599525) 2024-06-20 00:33:41 [warn] HTTP client 10.1.10.9 login succeeded (session key 2111682295) 2024-06-20 00:34:03 [warn] HTTP client 10.1.10.9 login succeeded (session key 2523734364) 2024-06-20 00:34:26 [warn] HTTP client 10.1.10.9 login succeeded (session key 514956231) 2024-06-20 00:34:46 [warn] HTTP client 10.1.10.9 login succeeded (session key 1775476910) 2024-06-20 00:35:09 [warn] HTTP client 10.1.10.9 login succeeded (session key 3441070004) 2024-06-20 00:35:45 [warn] HTTP client 10.1.10.9 login succeeded (session key 1713792156) 2024-06-20 00:35:57 [warn] HTTP client 10.1.10.9 login succeeded (session key 500570079) 2024-06-20 00:36:02 [warn] HTTP client 10.1.10.9 login succeeded (session key 2568201165) 2024-06-20 00:36:26 [warn] HTTP client 10.1.10.9 login succeeded (session key 1106806294) 2024-06-20 00:36:54 [warn] HTTP client 10.1.10.9 login succeeded (session key 3038400876) 2024-06-20 00:37:20 [warn] HTTP client 10.1.10.9 login succeeded (session key 3915957228) 2024-06-20 00:37:47 [warn] HTTP client 10.1.10.9 login succeeded (session key 633926971) 2024-06-20 00:38:13 [warn] HTTP client 10.1.10.9 login succeeded (session key 356966781) 2024-06-20 00:38:42 [warn] HTTP client 10.1.10.9 login succeeded (session key 495343722) 2024-06-20 00:39:14 [warn] HTTP client 10.1.10.9 login succeeded (session key 3960934741) 2024-06-20 00:39:40 [warn] HTTP client 10.1.10.9 login succeeded (session key 3167420754) 2024-06-20 00:40:07 [warn] HTTP client 10.1.10.9 login succeeded (session key 849883161) 2024-06-20 00:40:35 [warn] HTTP client 10.1.10.9 login succeeded (session key 637706513) 2024-06-20 00:40:45 [warn] HTTP client 10.1.10.9 login succeeded (session key 942590317) 2024-06-20 01:12:43 [warn] HTTP client 10.1.10.9 login succeeded (session key 2862368256) 2024-06-20 01:40:58 [warn] HTTP client 10.1.10.9 login succeeded (session key 384322062) 2024-06-20 01:41:27 [warn] HTTP client 10.1.10.9 login succeeded (session key 1801224662) 2024-06-20 01:55:05 [warn] HTTP client 10.1.10.9 login succeeded (session key 2018069423) 2024-06-20 02:04:58 [warn] HTTP client 10.1.10.9 login succeeded (session key 800357292) 2024-06-20 02:05:23 [warn] HTTP client 10.1.10.9 login succeeded (session key 3587811362) 2024-06-20 02:05:53 [warn] HTTP client 10.1.10.9 login succeeded (session key 1966587174) 2024-06-20 02:06:02 [warn] HTTP client 10.1.10.9 login succeeded (session key 975835003) 2024-06-20 02:06:14 [warn] HTTP client 10.1.10.9 login succeeded (session key 2429128476) 2024-06-20 02:11:39 [warn] HTTP client 10.1.10.9 login succeeded (session key 817814135) 2024-06-20 02:12:04 [warn] HTTP client 10.1.10.9 login succeeded (session key 2812448363) 2024-06-20 02:15:51 [warn] HTTP client 10.1.10.9 login succeeded (session key 149586810) 2024-06-20 02:16:17 [warn] HTTP client 10.1.10.9 login succeeded (session key 2141131527) 2024-06-20 02:16:39 [warn] HTTP client 10.1.10.9 login succeeded (session key 3682049859) 2024-06-20 02:17:01 [warn] HTTP client 10.1.10.9 login succeeded (session key 2619402717) 2024-06-20 02:17:11 [warn] HTTP client 10.1.10.9 login succeeded (session key 2985926046) 2024-06-20 02:17:27 [warn] HTTP client 10.1.10.9 login succeeded (session key 803132847) 2024-06-20 02:17:53 [warn] HTTP client 10.1.10.9 login succeeded (session key 3323915025) 2024-06-20 02:18:21 [warn] HTTP client 10.1.10.9 login succeeded (session key 2247458471) 2024-06-20 02:18:45 [warn] HTTP client 10.1.10.9 login succeeded (session key 2536628431) 2024-06-20 02:19:10 [warn] HTTP client 10.1.10.9 login succeeded (session key 3060954282) 2024-06-20 02:19:37 [warn] HTTP client 10.1.10.9 login succeeded (session key 1737042006) 2024-06-20 02:20:08 [warn] HTTP client 10.1.10.9 login succeeded (session key 612654718) 2024-06-20 02:20:37 [warn] HTTP client 10.1.10.9 login succeeded (session key 1068865091) 2024-06-20 02:21:01 [warn] HTTP client 10.1.10.9 login succeeded (session key 771435670) 2024-06-20 02:21:24 [warn] HTTP client 10.1.10.9 login succeeded (session key 3928580257) 2024-06-20 02:24:50 [warn] HTTP client 10.1.10.9 login succeeded (session key 2386749170) 2024-06-20 02:25:14 [warn] HTTP client 10.1.10.9 login succeeded (session key 251546035) 2024-06-20 02:25:41 [warn] HTTP client 10.1.10.9 login succeeded (session key 3523239507) 2024-06-20 02:26:07 [warn] HTTP client 10.1.10.9 login succeeded (session key 3218200729) 2024-06-20 02:26:35 [warn] HTTP client 10.1.10.9 login succeeded (session key 3720041818) 2024-06-20 02:27:01 [warn] HTTP client 10.1.10.9 login succeeded (session key 3716254985) 2024-06-20 02:27:32 [warn] HTTP client 10.1.10.9 login succeeded (session key 3899442431) 2024-06-20 02:27:35 [warn] HTTP client 10.1.10.9 login succeeded (session key 2116079794) 2024-06-20 02:27:53 [warn] HTTP client 10.1.10.9 login succeeded (session key 894565428) 2024-06-20 02:28:27 [warn] HTTP client 10.1.10.9 login succeeded (session key 1305853595) 2024-06-20 02:28:54 [warn] HTTP client 10.1.10.9 login succeeded (session key 2151292634) 2024-06-20 02:29:19 [warn] HTTP client 10.1.10.9 login succeeded (session key 3350555338) 2024-06-20 02:29:45 [warn] HTTP client 10.1.10.9 login succeeded (session key 3462100455) 2024-06-20 02:30:03 [warn] HTTP client 10.1.10.9 login succeeded (session key 4071707954) 2024-06-20 02:30:29 [warn] HTTP client 10.1.10.9 login succeeded (session key 50000306) 2024-06-20 02:30:56 [warn] HTTP client 10.1.10.9 login succeeded (session key 1667854501) 2024-06-20 02:31:27 [warn] HTTP client 10.1.10.9 login succeeded (session key 2048630315) 2024-06-20 02:55:55 [warn] HTTP client 10.1.10.9 login succeeded (session key 2439682909) 2024-06-20 03:02:04 [warn] HTTP client 10.1.10.9 login succeeded (session key 2978987675) 2024-06-20 03:04:28 [warn] HTTP client 10.1.10.9 login succeeded (session key 2758490383) 2024-06-20 03:04:50 [warn] HTTP client 10.1.10.9 login succeeded (session key 2437031831) 2024-06-20 03:05:20 [warn] HTTP client 10.1.10.9 login succeeded (session key 3913432380) 2024-06-20 03:05:47 [warn] HTTP client 10.1.10.9 login succeeded (session key 1213636342) 2024-06-20 03:56:53 [warn] HTTP client 10.1.10.9 login succeeded (session key 4277151167) 2024-06-20 03:57:24 [warn] HTTP client 10.1.10.9 login succeeded (session key 1982808784) 2024-06-20 04:40:40 [warn] HTTP client 10.1.10.9 login succeeded (session key 128428737) 2024-06-20 04:42:53 [warn] HTTP client 10.1.10.9 login succeeded (session key 3218278673) 2024-06-20 04:43:05 [warn] HTTP client 10.1.10.9 login succeeded (session key 3065571460) 2024-06-20 04:43:35 [warn] HTTP client 10.1.10.9 login succeeded (session key 1165941569) 2024-06-20 04:43:52 [warn] HTTP client 10.1.10.9 login succeeded (session key 3591443734) 2024-06-20 04:44:06 [warn] HTTP client 10.1.10.9 login succeeded (session key 1605038994) 2024-06-20 04:47:55 [warn] HTTP client 10.1.10.9 login succeeded (session key 978053962) 2024-06-20 04:48:24 [warn] HTTP client 10.1.10.9 login succeeded (session key 3811958236) 2024-06-20 04:48:51 [warn] HTTP client 10.1.10.9 login succeeded (session key 3390835297) 2024-06-20 04:49:21 [warn] HTTP client 10.1.10.9 login succeeded (session key 2588243843) 2024-06-20 04:49:51 [warn] HTTP client 10.1.10.9 login succeeded (session key 4267056045) 2024-06-20 04:50:18 [warn] HTTP client 10.1.10.9 login succeeded (session key 923226743) 2024-06-20 04:50:31 [warn] HTTP client 10.1.10.9 login succeeded (session key 2771938442) 2024-06-20 04:50:59 [warn] HTTP client 10.1.10.9 login succeeded (session key 3787427531) 2024-06-20 04:51:25 [warn] HTTP client 10.1.10.9 login succeeded (session key 1763409621) 2024-06-20 04:51:51 [warn] HTTP client 10.1.10.9 login succeeded (session key 1054323863) 2024-06-20 04:52:20 [warn] HTTP client 10.1.10.9 login succeeded (session key 2793445079) 2024-06-20 04:52:58 [warn] HTTP client 10.1.10.9 login succeeded (session key 449632642) 2024-06-20 04:53:26 [warn] HTTP client 10.1.10.9 login succeeded (session key 1251356753) 2024-06-20 04:53:56 [warn] HTTP client 10.1.10.9 login succeeded (session key 3408456684) 2024-06-20 04:54:27 [warn] HTTP client 10.1.10.9 login succeeded (session key 479221908) 2024-06-20 04:54:48 [warn] HTTP client 10.1.10.9 login succeeded (session key 1290029679) 2024-06-20 04:55:01 [warn] HTTP client 10.1.10.9 login succeeded (session key 1074154654) 2024-06-20 04:55:11 [warn] HTTP client 10.1.10.9 login succeeded (session key 3453020502) 2024-06-20 04:55:25 [warn] HTTP client 10.1.10.9 login succeeded (session key 991458339) 2024-06-20 04:57:22 [warn] HTTP client 10.1.10.9 login succeeded (session key 3754189644) 2024-06-20 04:59:10 [warn] HTTP client 10.1.10.9 login succeeded (session key 680735117) 2024-06-20 06:56:55 [warn] HTTP client 10.1.10.9 login succeeded (session key 3924206460) 2024-06-20 08:25:24 [warn] HTTP client 10.1.10.9 login succeeded (session key 3691413688) 2024-06-20 08:26:23 [warn] HTTP client 10.1.10.9 login succeeded (session key 3147903152) 2024-06-20 08:26:50 [warn] HTTP client 10.1.10.9 login succeeded (session key 944295359) 2024-06-20 08:38:41 [debug] === Diagnostics === 2024-06-20 08:38:41 [debug] RepRapFirmware for Duet 3 Mini 5+ version 3.5.1 (2024-04-19 14:41:25) running on Duet 3 Mini5plus WiFi (standalone mode) 2024-06-20 08:38:41 [debug] Board ID: 65LYX-8Q6KL-K65J0-409N0-NP02Z-ZFK3T 2024-06-20 08:38:41 [debug] Used output buffers: 1 of 40 (26 max) -
@ProteanReverie @Chriss
@dc42 is away this week and next week, but I'll remind him of this issue when he's back. Please keep posting M122 and logging reports, I'm sure that the 'HardFault bfarValid precise' errors will help him track this painful bug down.Ian
Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard
-
@droftarts For sure... you will be the first who will get an update if that happens again. Btw: I did not changed my setting last weekend, I was to short in time. So my printer is still printing the same gcode over and over without any filament, nopt bed heater and a hotend at 80°C. I hope that I can change that this weekend.
Cheers, Chriss
-
Hi @droftarts
My printer is out of the printing pool for a while.... I have some mechanical issues with my belt.
And I do not have replacements on stock. I will be back at this topic if my bench board hast it and when my playground printer is fixed.Cheers, Chriss
-
Another occurance over the weekend.
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: 65LYX-8Q6KL-K65J0-409N0-NP02Z-ZFK3T Used output buffers: 14 of 40 (18 max) === RTOS === Static ram: 103232 Dynamic ram: 119916 of which 24 recycled Never used RAM 15388, free system stack 150 words Tasks: NETWORK(2,nWait 7,580.1%,218) HEAT(3,nWait 6,0.4%,372) Move(4,nWait 6,0.1%,355) CanReceiv(6,nWait 1,0.6%,808) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.3%,348) TMC(4,nWait 6,34.6%,102) MAIN(1,running,35.1%,677) IDLE(0,ready,0.3%,30) AIN(4,delaying,36.4%,260), total 688.1% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 11:24:14 ago, cause: software Last software reset at 2024-06-23 21:22, reason: HardFault bfarValid precise, Gcodes spinning, available RAM 15364, slot 0 Software reset code 0x0063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00000803 BFAR 0x00000004 SP 0x20011ff0 Task NETW Freestk 483 ok Stack: 00000160 00000002 200014e8 0000015f ffffffff 000a07ef 0002ff8e 810f0000 0002ff85 00000000 00000000 00000000 2002fdcc 00000800 20035308 2002c5f8 200187fc 2002c41e 200187fc 2001e9f8 0003011f 00000000 00000000 00000000 200120a0 00000014 ffffffff Error status: 0x00 MCU revision 3, ADC conversions started 41054418, completed 41054418, timed out 0, errs 0 MCU temperature: min 38.2, current 39.6, max 41.0 Supply voltage: min 24.1, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/12/12, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 43, reads 63568, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 43, reads 63568, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 43, reads 63568, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 43, reads 63568, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 43, reads 63568, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2024-06-24 08:46:40 Cache data hit count 4294967295 Slowest loop: 7.67ms; fastest: 0.16ms === Storage === Free file entries: 19 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 3.2ms, write time 3.8ms, 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 -1 -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 === CAN === Messages queued 205271, received 328436, lost 0, errs 1, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 390, free buffers 26 (min 26), ts 205271/205270/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 7.95ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(1) 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 e8:68:e7:e1:4e:d0 Module reset reason: Power up, Vcc 3.42, flash size 2097152, free heap 29568 WiFi IP address 10.1.10.46 Signal strength -59dBm, channel 11, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 3 0 0 0 0 0 0 0Relevant log file section
2024-06-21 20:23:42 [warn] HTTP client 10.1.10.9 login succeeded (session key 2318516549) 2024-06-22 12:46:56 [warn] HTTP client 10.1.10.9 login succeeded (session key 2498040479) 2024-06-22 12:51:11 [warn] HTTP client 10.1.10.9 login succeeded (session key 2882910232) 2024-06-23 12:58:37 [warn] HTTP client 10.1.10.9 login succeeded (session key 2274061159) 2024-06-23 13:14:38 [warn] HTTP client 10.1.10.9 login succeeded (session key 4219374896) 2024-06-23 13:14:58 [warn] HTTP client 10.1.10.9 login succeeded (session key 1587684493) 2024-06-23 13:15:18 [warn] HTTP client 10.1.10.9 login succeeded (session key 871240276) 2024-06-23 18:32:45 [warn] HTTP client 10.1.10.9 login succeeded (session key 640519980) 2024-06-23 20:18:14 [warn] HTTP client 10.1.10.9 login succeeded (session key 1301043269) 2024-06-23 20:19:52 [warn] HTTP client 10.1.10.9 login succeeded (session key 3916440988) 2024-06-23 20:20:20 [warn] HTTP client 10.1.10.9 login succeeded (session key 3232781641) 2024-06-23 20:20:40 [warn] HTTP client 10.1.10.9 login succeeded (session key 1725357550) 2024-06-23 20:20:56 [warn] HTTP client 10.1.10.9 login succeeded (session key 2497689280) power up + 00:00:00 [info] Event logging started at level debug power up + 00:00:00 [info] Running: Duet 3 Mini5plus WiFi: 3.5.1 (2024-04-19 14:41:25) power up + 00:00:00 [debug] Done! power up + 00:00:00 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running. power up + 00:00:00 [warn] WiFi module started power up + 00:00:08 [warn] WiFi module is connected to access point SD3D-24, IP address 10.1.10.46 power up + 00:00:08 [warn] HTTP client 10.1.10.9 login succeeded (session key 3424165787) 2024-06-23 21:22:35 [warn] Date and time set at power up + 00:00:08 2024-06-23 21:54:45 [warn] HTTP client 10.1.10.9 login succeeded (session key 835669197) 2024-06-23 21:54:54 [warn] HTTP client 10.1.10.9 login succeeded (session key 1712060142) 2024-06-23 21:55:04 [warn] HTTP client 10.1.10.9 login succeeded (session key 2620441938) 2024-06-23 21:55:12 [warn] HTTP client 10.1.10.9 login succeeded (session key 2547895376) 2024-06-23 21:55:35 [warn] HTTP client 10.1.10.9 login succeeded (session key 519733317) 2024-06-24 00:17:19 [warn] HTTP client 10.1.10.9 login succeeded (session key 1091016330) 2024-06-24 00:17:48 [warn] HTTP client 10.1.10.9 login succeeded (session key 598095062) 2024-06-24 00:18:08 [warn] HTTP client 10.1.10.9 login succeeded (session key 994352261) 2024-06-24 00:57:15 [warn] HTTP client 10.1.10.9 login succeeded (session key 852304322) 2024-06-24 04:59:31 [warn] HTTP client 10.1.10.9 login succeeded (session key 713145612) 2024-06-24 08:46:40 [debug] === Diagnostics === -
undefined ProteanReverie referenced this topic
-
No occurrences through the week last week, but did have another over the weekend.
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: 65LYX-8Q6KL-K65J0-409N0-NP02Z-ZFK3T Used output buffers: 1 of 40 (18 max) === RTOS === Static ram: 103232 Dynamic ram: 119940 of which 24 recycled Never used RAM 15364, free system stack 156 words Tasks: NETWORK(1,ready,419.7%,218) HEAT(3,nWait 6,0.7%,356) Move(4,nWait 6,0.2%,341) CanReceiv(6,nWait 1,1.0%,808) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.6%,348) TMC(4,nWait 6,57.1%,102) MAIN(1,running,87.1%,677) IDLE(0,ready,0.5%,30) AIN(4,delaying,60.0%,260), total 627.0% Owned mutexes: === Platform === Last reset 20:58:29 ago, cause: software Last software reset at 2024-06-30 11:35, reason: HardFault bfarValid precise, Platform spinning, available RAM 15364, slot 1 Software reset code 0x0060 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00000803 BFAR 0x00000004 SP 0x20011ff0 Task NETW Freestk 483 ok Stack: 00000160 00000002 200014e8 0000015f ffffffff 000a07ef 0002ff8e 810f0000 0002ff85 00000000 00000000 00000000 200305e4 00000800 2002c5f8 2002c5f8 00000001 2002c41e 200187fc 2001e9f8 0003011f 00000000 00000000 00000000 200120a0 00000014 20468121 Error status: 0x00 MCU revision 3, ADC conversions started 75510090, completed 75510090, timed out 0, errs 0 MCU temperature: min 38.7, current 39.8, max 41.4 Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/12/12, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 54, reads 42014, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 54, reads 42014, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 54, reads 42014, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 54, reads 42014, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 54, reads 42015, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2024-07-01 08:34:24 Cache data hit count 4294967295 Slowest loop: 7.01ms; fastest: 0.16ms === Storage === Free file entries: 19 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 0.7ms, write time 2.6ms, 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 -1 -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 === CAN === Messages queued 377549, received 604082, lost 0, errs 1, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 297, free buffers 26 (min 26), ts 377549/377548/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 7.38ms; 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 e8:68:e7:e1:4e:d0 Module reset reason: Power up, Vcc 3.39, flash size 2097152, free heap 42784 WiFi IP address 10.1.10.46 Signal strength -60dBm, channel 11, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0Log.txt
2024-06-26 13:58:26 [warn] HTTP client 10.1.10.9 login succeeded (session key 3446445976) 2024-06-27 07:44:43 [warn] HTTP client 10.1.10.9 login succeeded (session key 2598975707) 2024-06-27 11:34:42 [warn] HTTP client 10.1.10.9 login succeeded (session key 3419397635) 2024-06-27 12:00:55 [warn] HTTP client 10.1.10.9 login succeeded (session key 3802106080) 2024-06-27 14:17:11 [warn] HTTP client 10.1.10.9 login succeeded (session key 3855690080) power up + 00:00:00 [info] Event logging started at level debug power up + 00:00:00 [info] Running: Duet 3 Mini5plus WiFi: 3.5.1 (2024-04-19 14:41:25) power up + 00:00:00 [debug] Done! power up + 00:00:00 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running. power up + 00:00:00 [warn] WiFi module started power up + 00:00:07 [warn] WiFi module is connected to access point SD3D-24, IP address 10.1.10.46 power up + 00:00:08 [warn] HTTP client 10.1.10.9 login succeeded (session key 526990551) 2024-06-30 11:36:03 [warn] Date and time set at power up + 00:00:08 2024-06-30 13:26:46 [warn] HTTP client 10.1.10.9 login succeeded (session key 2188381128) 2024-06-30 13:26:51 [warn] HTTP client 10.1.10.9 login succeeded (session key 1375067276) 2024-06-30 13:26:54 [warn] HTTP client 10.1.10.9 login succeeded (session key 587158328) 2024-06-30 13:27:19 [warn] HTTP client 10.1.10.9 login succeeded (session key 3511153781) 2024-06-30 14:25:24 [warn] HTTP client 10.1.10.9 login succeeded (session key 2762896906) 2024-07-01 01:18:55 [warn] HTTP client 10.1.10.9 login succeeded (session key 96132253) 2024-07-01 01:20:58 [warn] HTTP client 10.1.10.9 login succeeded (session key 1951105233) 2024-07-01 08:34:24 [debug] === Diagnostics === -
Were you able to test with 3.5.2?
-
@Phaedrux said in Duet 3 mini5+ nightly restarts:
Were you able to test with 3.5.2?
I had missed the release of 3.5.2. I will get that updated now and continue to observe.
I was out of the office last week, and there appear to have been a couple of occurrences that I missed thus do not have M122 reports for. Latest M122 and log from while I was out are below.
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: 65LYX-8Q6KL-K65J0-409N0-NP02Z-ZFK3T Used output buffers: 1 of 40 (26 max) === RTOS === Static ram: 103232 Dynamic ram: 119940 of which 24 recycled Never used RAM 15364, free system stack 150 words Tasks: NETWORK(1,ready,22.3%,218) HEAT(3,nWait 6,0.0%,356) Move(4,nWait 6,0.0%,341) CanReceiv(6,nWait 1,0.0%,808) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,348) TMC(4,nWait 6,0.8%,102) MAIN(1,running,75.9%,569) IDLE(0,ready,0.1%,30) AIN(4,delaying,0.9%,260), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 136:15:22 ago, cause: software Last software reset at 2024-07-09 18:41, reason: HardFault bfarValid precise, Gcodes spinning, available RAM 15388, slot 1 Software reset code 0x0063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00000803 BFAR 0x00000004 SP 0x20011ff0 Task NETW Freestk 483 ok Stack: 00000160 00000002 200014e8 0000015f ffffffff 000a07ef 0002ff8e 810f0000 0002ff85 00000000 00000000 00000000 20031614 00000800 2002c5c8 2002c5c8 00000001 2002c41e 200187fc 2001e9f8 0003011f 00000000 00000000 00000000 200120a0 00000014 ffffffff Error status: 0x00 MCU revision 3, ADC conversions started 490523144, completed 490523144, timed out 0, errs 0 MCU temperature: min 40.2, current 40.8, max 41.2 Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/12/12, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 87, reads 6413, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 87, reads 6413, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 87, reads 6413, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 87, reads 6412, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 87, reads 6413, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2024-07-15 10:56:39 Cache data hit count 4294967295 Slowest loop: 706.08ms; fastest: 0.16ms === Storage === Free file entries: 19 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 0.6ms, write time 1.7ms, 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 -1 -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 === CAN === Messages queued 609, received 976, lost 0, errs 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 7, free buffers 26 (min 26), ts 609/609/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 201.48ms; fastest: 0.07ms 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 8, noresp 1 Firmware version 2.1.0 MAC address e8:68:e7:e1:4e:d0 Module reset reason: Power up, Vcc 3.39, flash size 2097152, free heap 42776 WiFi IP address 10.1.10.46 Signal strength -57dBm, channel 11, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0Log:
2024-07-04 02:48:55 [warn] HTTP client 10.1.10.9 login succeeded (session key 9483890) 2024-07-04 02:49:06 [warn] HTTP client 10.1.10.9 login succeeded (session key 930818349) 2024-07-05 02:52:38 [warn] HTTP client 10.1.10.9 login succeeded (session key 4040799154) 2024-07-05 02:52:47 [warn] HTTP client 10.1.10.9 login succeeded (session key 2855566171) 2024-07-05 02:52:58 [warn] HTTP client 10.1.10.9 login succeeded (session key 2244811411) 2024-07-05 15:41:41 [warn] HTTP client 10.1.10.9 login succeeded (session key 1092597384) 2024-07-05 15:41:59 [warn] HTTP client 10.1.10.9 login succeeded (session key 792491443) 2024-07-06 02:19:54 [warn] HTTP client 10.1.10.9 login succeeded (session key 1617452959) 2024-07-06 02:20:05 [warn] HTTP client 10.1.10.9 login succeeded (session key 3536857478) 2024-07-06 02:20:19 [warn] HTTP client 10.1.10.9 login succeeded (session key 3441961249) 2024-07-06 02:20:30 [warn] HTTP client 10.1.10.9 login succeeded (session key 3419764404) 2024-07-06 03:38:37 [warn] HTTP client 10.1.10.9 login succeeded (session key 3275204183) 2024-07-06 03:38:54 [warn] HTTP client 10.1.10.9 login succeeded (session key 1076010950) 2024-07-06 06:38:04 [warn] HTTP client 10.1.10.9 login succeeded (session key 99326213) 2024-07-06 09:37:53 [warn] HTTP client 10.1.10.9 login succeeded (session key 4281600970) 2024-07-06 17:14:58 [warn] HTTP client 10.1.10.9 login succeeded (session key 244420871) 2024-07-07 03:57:29 [warn] HTTP client 10.1.10.9 login succeeded (session key 1942473528) 2024-07-07 03:57:51 [warn] HTTP client 10.1.10.9 login succeeded (session key 902420159) 2024-07-07 21:37:54 [warn] HTTP client 10.1.10.9 login succeeded (session key 3336424230) power up + 00:00:00 [info] Event logging started at level debug power up + 00:00:00 [info] Running: Duet 3 Mini5plus WiFi: 3.5.1 (2024-04-19 14:41:25) power up + 00:00:00 [debug] Done! power up + 00:00:00 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running. power up + 00:00:01 [warn] WiFi module started power up + 00:00:07 [warn] WiFi module is connected to access point SD3D-24, IP address 10.1.10.46 power up + 00:00:08 [warn] HTTP client 10.1.10.9 login succeeded (session key 1810534383) 2024-07-08 01:43:36 [warn] Date and time set at power up + 00:00:08 2024-07-08 04:01:44 [warn] HTTP client 10.1.10.9 login succeeded (session key 2605107193) 2024-07-08 04:01:54 [warn] HTTP client 10.1.10.9 login succeeded (session key 1991834332) power up + 00:00:00 [info] Event logging started at level debug power up + 00:00:00 [info] Running: Duet 3 Mini5plus WiFi: 3.5.1 (2024-04-19 14:41:25) power up + 00:00:00 [debug] Done! power up + 00:00:00 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running. power up + 00:00:00 [warn] WiFi module started power up + 00:00:07 [warn] WiFi module is connected to access point SD3D-24, IP address 10.1.10.46 power up + 00:00:08 [warn] HTTP client 10.1.10.9 login succeeded (session key 592097959) 2024-07-09 04:20:33 [warn] Date and time set at power up + 00:00:08 2024-07-09 07:25:16 [warn] HTTP client 10.1.10.9 login succeeded (session key 4205354191) power up + 00:00:00 [info] Event logging started at level debug power up + 00:00:00 [info] Running: Duet 3 Mini5plus WiFi: 3.5.1 (2024-04-19 14:41:25) power up + 00:00:00 [debug] Done! power up + 00:00:00 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running. power up + 00:00:01 [warn] WiFi module started power up + 00:00:07 [warn] WiFi module is connected to access point SD3D-24, IP address 10.1.10.46 power up + 00:00:08 [warn] HTTP client 10.1.10.9 login succeeded (session key 3903592583) 2024-07-09 18:41:26 [warn] Date and time set at power up + 00:00:08 2024-07-15 09:14:13 [warn] HTTP client 10.1.10.9 login succeeded (session key 1545598652) 2024-07-15 10:54:38 [debug] === Diagnostics === -
I have begun testing with 3.5.2. I also have now assembled this setup into a machine, moving it from the previous setup of just boards on my desk.
I had a crash occur this morning while I was watching the interface, which happened just after I got an M122 response as I was checking to see if it had any issues overnight. This setup has completed a couple of prints, but nothing had been run since last power-up yesterday afternoon. Interestingly, that M122 response does not appear in the log file, though I did get the response in DWC. I have also included that M122 report below as the last item on this post, just in-case it is useful.
Additionally, I noticed that on startup I got an error (which can also be seen in the M122) stating that none of the motor drivers on the CAN connected board exist. The axis assigned to these drivers are shown and can be interacted with, but they do not respond to commands. Other items on that CAN board, such as the toolhead heaters and thermistors do work. I am guessing this is just due to CAN timing being off from the restart and reconnecting part-way through the config.g, as the motor driver commands are some of the first things in config.g, but wanted to provide this additional information. I can confirm that power cycling the boards/machine resolves this issue.
M122 post-crash:
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.2 (2024-06-11 17:14:16) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: T69HG-KN6KL-K65J0-409NJ-JYW1Z-RZQJW Used output buffers: 17 of 40 (18 max) Error in macro line 17 while starting up: Driver 1.0 does not exist Driver 1.1 does not exist Driver 1.3 does not exist Driver 1.4 does not exist Driver 1.2 does not exist === RTOS === Static ram: 103368 Dynamic ram: 122124 of which 0 recycled Never used RAM 13068, free system stack 198 words Tasks: NETWORK(2,nWait 7,14.1%,217) HEAT(3,nWait 6,0.0%,350) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.1%,796) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,348) TMC(4,nWait 6,0.8%,101) MAIN(1,running,83.9%,665) IDLE(0,ready,0.1%,29) AIN(4,delaying,0.9%,259), total 100.0% Owned mutexes: === Platform === Last reset 00:04:32 ago, cause: software Last software reset at 2024-07-26 08:21, reason: StuckInSpinLoop, none spinning, available RAM 15700, slot 0 Software reset code 0x4093 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000080f BFAR 0xe000ed38 SP 0x200043f0 Task NETW Freestk 4294953692 ok Stack: 00000000 2000305c 10000000 e000e000 200043fd 000a1821 000a0efa 61010000 000a0ee3 20003058 ffffffff 00000000 035a4c16 20002878 2002c424 ffffffff 20011800 00000009 000a0f97 20004498 2002c420 200114f8 0009e1df 2002c420 0002dfab 2002c424 a5a5a5a5 Error status: 0x00 MCU revision 3, ADC conversions started 273048, completed 273048, timed out 0, errs 0 MCU temperature: min 36.5, current 37.3, max 37.6 Supply voltage: min 23.9, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/140/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 21, reads 14333, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 21, reads 14333, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 21, reads 14333, 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 14333, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 21, reads 14333, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2024-07-26 08:26:41 Cache data hit count 522766768 Slowest loop: 6.01ms; fastest: 0.16ms === Storage === Free file entries: 19 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 0.6ms, write time 2.4ms, 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 Heater 2 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 0x0000803 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === Filament sensors === check 0 clear 2577952 Extruder 0 sensor: ok Extruder 1 sensor: no filament === CAN === Messages queued 2473, received 5486, lost 0, errs 1, boc 0 Longest wait 1ms for reply type 6018, peak Tx sync delay 210, free buffers 26 (min 25), ts 1364/1363/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 10.96ms; 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 e8:68:e7:e1:4e:b7 Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 42940 WiFi IP address 10.1.10.21 Signal strength -55dBm, channel 11, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0Log:
power up + 00:00:00 [info] Event logging started at level debug power up + 00:00:00 [info] Running: Duet 3 Mini5plus WiFi: 3.5.2 (2024-06-11 17:14:16) power up + 00:00:00 [debug] Done! power up + 00:00:00 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running. power up + 00:00:01 [warn] WiFi module started power up + 00:00:08 [warn] WiFi module is connected to access point SD3D-24, IP address 10.1.10.21 power up + 00:00:10 [warn] HTTP client 10.1.10.9 login succeeded (session key 2372260450) 2024-07-25 16:44:19 [warn] Date and time set at power up + 00:00:10 2024-07-26 02:59:08 [warn] Error: WiFi module reported: Lost connection, auto reconnecting 2024-07-26 02:59:12 [warn] Error: WiFi module reported: Auto reconnect succeeded 2024-07-26 04:50:09 [warn] Error: WiFi module reported: Lost connection, auto reconnecting 2024-07-26 04:50:12 [warn] Error: WiFi module reported: Auto reconnect succeeded power up + 00:00:00 [info] Event logging started at level debug power up + 00:00:00 [info] Running: Duet 3 Mini5plus WiFi: 3.5.2 (2024-06-11 17:14:16) power up + 00:00:00 [debug] Done! power up + 00:00:00 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running. power up + 00:00:01 [warn] WiFi module started power up + 00:00:08 [warn] WiFi module is connected to access point SD3D-24, IP address 10.1.10.21 power up + 00:00:09 [warn] HTTP client 10.1.10.9 login succeeded (session key 199109116) 2024-07-26 08:22:09 [warn] Date and time set at power up + 00:00:09 2024-07-26 08:26:41 [debug] === Diagnostics === 2024-07-26 08:26:41 [debug] RepRapFirmware for Duet 3 Mini 5+ version 3.5.2 (2024-06-11 17:14:16) running on Duet 3 Mini5plus WiFi (standalone mode) 2024-07-26 08:26:41 [debug] Board ID: T69HG-KN6KL-K65J0-409NJ-JYW1Z-RZQJW 2024-07-26 08:26:41 [debug] Used output buffers: 17 of 40 (18 max) 2024-07-26 08:26:41 [debug] Error in macro line 17 while starting up: Driver 1.0 does not exist Driver 1.1 does not exist Driver 1.3 does not exist Driver 1.4 does not exist Driver 1.2 does not exist 2024-07-26 08:26:41 [debug] === RTOS ===M122 just prior to crash, not appearing in log file:
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.2 (2024-06-11 17:14:16) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: T69HG-KN6KL-K65J0-409NJ-JYW1Z-RZQJW Used output buffers: 1 of 40 (18 max) === RTOS === Static ram: 103368 Dynamic ram: 122348 of which 0 recycled Never used RAM 15700, free system stack 186 words Tasks: NETWORK(1,ready,13.3%,217) HEAT(3,nWait 6,0.0%,325) Move(4,nWait 6,0.0%,341) 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(1,running,84.8%,665) IDLE(0,ready,0.0%,29) AIN(4,delaying,0.9%,259), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 15:37:29 ago, cause: power up Last software reset at 2024-07-24 10:53, reason: User, Gcodes spinning, available RAM 11900, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 MCU revision 3, ADC conversions started 56249400, completed 56249399, timed out 0, errs 0 MCU temperature: min 24.9, current 37.1, max 37.8 Supply voltage: min 23.9, current 23.9, max 24.0, 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 0, read errors 0, write errors 0, ifcnt 10, reads 11346, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 11346, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 11344, writes 10, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x01 Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 11345, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 11346, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2024-07-26 08:21:37 Cache data hit count 4294967295 Slowest loop: 115.60ms; fastest: 0.16ms === Storage === Free file entries: 19 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 10.2ms, write time 111.6ms, 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 Heater 2 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 0x0000803 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === Filament sensors === check 0 clear 536792218 Extruder 0 sensor: ok Extruder 1 sensor: no filament === CAN === Messages queued 506267, received 1125011, lost 0, errs 14, boc 0 Longest wait 1ms for reply type 6018, peak Tx sync delay 2156, free buffers 26 (min 25), ts 281247/281246/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 112.10ms; 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 -
Unsure of the relevancy to this thread, but I had another strange occurrence with this board just now that could potentially be related and provide more info as it related to a network action apparently disconnecting the SD card.
Following the power cycling in my last post to get all the motor drivers working again, I went to upload a print. This failed a little bit into the progress, which is not too uncommon in my experience here on this network when working with Duet 2 boards. See https://forum.duet3d.com/topic/35979/duet-2-wifi-network-slowdowns-and-board-restarts for more info on that. However, this time it came with a new message
"Error: Failed to create folder 0:/gcodes in path 0:/gcodes/PETG-0.8-0.5layers-adaptive0.2-adaptvar0.02_benderHead_fix3.gcode.part"
on top of the usual
"Failed to upload PETG-0.8-0.5layers-adaptive0.2-adaptvar0.02_benderHead_fix3.gcode
Network error"It appears the SD card became unmounted or unresponsive at this time. Following that attempt to upload, I could still see the contents of directories such as Macros and Gcodes, but I would get errors about the directory not being present. Attempting to run a macro would ask if I wanted to run it, but then nothing would happen. I used a USB attached serial console to change over to host mode, which worked. However, trying to connect to DWC would result in the page stating that the page could not be loaded, and to check that the SD card was inserted and the www files were present. I was able to use the USB serial console to switch the board back over to client mode, and both of my already open DWC instances were able to reconnect but still not interact with files. However, new attempts to connect to DWC would result in the page stating to check the SD card.
Power cycling was able to clear this condition. The log file does not show any of this, which makes sense since the SD card appeared to be disconnected. Screenshot of the DWC console provided due to this. Unfortunately I did not get an M122 before power cycling, but I will try to if this occurs again. I am continuing with the print for now but intend to remove the SD card and check it for issues in windows later today.
-
@ProteanReverie said in Duet 3 mini5+ nightly restarts:
intend to remove the SD card and check it for issues in windows later today.
I pulled the SD card and tested with H2testw per https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#troubleshooting-sd-card-issues
This found no issuesI then re-installed the SD card to the board and the board to the machine and ran M122 P104 S10.
Following this, the board appeared to be back in the state of not recognizing the SD card - unable to locate directories, check SD page when trying to load a new DWC session.
M122 output following this occurring:
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.2 (2024-06-11 17:14:16) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: T69HG-KN6KL-K65J0-409NJ-JYW1Z-RZQJW Used output buffers: 1 of 40 (36 max) === RTOS === Static ram: 103368 Dynamic ram: 122324 of which 0 recycled Never used RAM 15724, free system stack 202 words Tasks: NETWORK(1,ready,15.7%,203) HEAT(3,nWait 6,0.0%,371) 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,79.8%,665) IDLE(0,ready,2.6%,29) AIN(4,delaying,0.9%,259), total 100.0% Owned mutexes: === Platform === Last reset 00:01:44 ago, cause: power up Last software reset at 2024-07-26 08:21, reason: StuckInSpinLoop, none spinning, available RAM 15700, slot 0 Software reset code 0x4093 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000080f BFAR 0xe000ed38 SP 0x200043f0 Task NETW Freestk 4294953692 ok Stack: 00000000 2000305c 10000000 e000e000 200043fd 000a1821 000a0efa 61010000 000a0ee3 20003058 ffffffff 00000000 035a4c16 20002878 2002c424 ffffffff 20011800 00000009 000a0f97 20004498 2002c420 200114f8 0009e1df 2002c420 0002dfab 2002c424 a5a5a5a5 Error status: 0x00 MCU revision 3, ADC conversions started 105047, completed 105047, timed out 0, errs 0 MCU temperature: min 28.9, current 30.2, max 30.4 Supply voltage: min 23.9, current 24.0, max 24.0, 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 0, read errors 0, write errors 0, ifcnt 10, reads 3591, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 3591, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 3591, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 3591, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 3591, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2024-07-26 14:56:49 Cache data hit count 219758010 Slowest loop: 4080.50ms; fastest: 0.16ms === Storage === Free file entries: 20 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 101.1ms, write time 116.9ms, 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 Heater 2 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 0x0000803 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === Filament sensors === check 0 clear 893256 Extruder 0 sensor: ok Extruder 1 sensor: no filament === CAN === Messages queued 613, received 1360, lost 0, errs 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 6, free buffers 26 (min 26), ts 341/341/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 2271.55ms; fastest: 0.06ms 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 e8:68:e7:e1:4e:b7 Module reset reason: Power up, Vcc 3.39, flash size 2097152, free heap 42784 WiFi IP address 10.1.10.21 Signal strength -56dBm, channel 11, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0Here are some additional tests I ran while it was in that state:
I power cycled the machine after this, and re-ran M39 which gave the same response, and M20 which did properly list gcode files this time. However, trying to run M122 P104 S10 resulted in the same condition occurring.
After power cycling again, I was able to get results for M122 P104 S10, which I was able to successfully run 10 times consecutively. First run results:
SD write speed for 10.0MByte file was 1.36MBytes/sec
SD read speed for 10.0MByte file was 1.28MBytes/secAcross the first 8 tests I got values in the ranges of:
write = 1.36-1.37MB/s
read = 1.26-1.3MB/sHowever, read speed for attempt 9 fell down to 0.94, and was 0.95 for test 10. The write speeds stayed within previous range on those tests. I ran a couple more tests after waiting 5, and then 15 minutes, and then tried M122, M39, M20, and then repeated the speed test again. Speeds on those tests remained the same as in tests 9&10, and the condition was not incurred again.
-
Had another incident just now where I sent an M122 to see if a restart had happened while I was out of the office, which resulted in DWC reporting the M122 info and then the board crashing and restarting, while failing to recognize the divers on the CAN connected board upon restart. Below is the output from M122 before, and after, as well as a section of the log file. Once again, the log file does not contain any of the M122 reported prior to the restart. I am going to swap out the main board with an unused spare I have on hand and try testing with that. I will then be able to do any tests on the current board from a benchtop setup.
M122 before restart:
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.2 (2024-06-11 17:14:16) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: T69HG-KN6KL-K65J0-409NJ-JYW1Z-RZQJW Used output buffers: 1 of 40 (37 max) === RTOS === Static ram: 103368 Dynamic ram: 122436 of which 0 recycled Never used RAM 12396, free system stack 132 words Tasks: NETWORK(2,nWait 7,12.9%,195) HEAT(3,nWait 6,0.0%,325) Move(4,nWait 6,0.0%,238) CanReceiv(6,nWait 1,0.1%,773) CanSender(5,nWait 7,0.0%,323) CanClock(7,delaying,0.0%,348) TMC(4,nWait 6,0.9%,67) MAIN(1,running,85.2%,665) IDLE(0,ready,0.0%,29) AIN(4,delaying,0.9%,259), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 64:52:05 ago, cause: power up Last software reset at 2024-07-26 08:21, reason: StuckInSpinLoop, none spinning, available RAM 15700, slot 0 Software reset code 0x4093 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0000080f BFAR 0xe000ed38 SP 0x200043f0 Task NETW Freestk 4294953692 ok Stack: 00000000 2000305c 10000000 e000e000 200043fd 000a1821 000a0efa 61010000 000a0ee3 20003058 ffffffff 00000000 035a4c16 20002878 2002c424 ffffffff 20011800 00000009 000a0f97 20004498 2002c420 200114f8 0009e1df 2002c420 0002dfab 2002c424 a5a5a5a5 Error status: 0x00 MCU revision 3, ADC conversions started 233525360, completed 233525360, timed out 0, errs 0 MCU temperature: min 36.2, current 38.4, max 43.8 Supply voltage: min 23.7, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/120/120, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 19, reads 54184, writes 9, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 19, reads 54184, writes 9, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 54193, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 54192, writes 0, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x41 Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 54194, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2024-07-29 08:04:42 Cache data hit count 4294967295 Slowest loop: 241.79ms; fastest: 0.16ms === Storage === Free file entries: 19 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 5.4ms, write time 121.6ms, max retries 0 === Move === DMs created 83, segments created 15, maxWait 2466643ms, 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 18, on retry 0, too short 0, wrong shape 6, maybepossible 0 === DDARing 0 === Scheduled moves 80, completed 80, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 21], 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 0 is on, I-accum = 0.2 Heater 1 is on, I-accum = 0.2 Heater 2 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 0x000080f Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === Filament sensors === check 0 clear 2233026076 Extruder 0 sensor: ok Extruder 1 sensor: no filament === CAN === Messages queued 2082665, received 4627819, lost 0, errs 0, boc 0 Longest wait 1ms for reply type 6013, peak Tx sync delay 296, free buffers 26 (min 24), ts 1156944/1156944/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 95.60ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(2) 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 0M122 after restart:
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.2 (2024-06-11 17:14:16) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: T69HG-KN6KL-K65J0-409NJ-JYW1Z-RZQJW Used output buffers: 1 of 40 (18 max) Error in macro line 17 while starting up: Driver 1.0 does not exist Driver 1.1 does not exist Driver 1.3 does not exist Driver 1.4 does not exist Driver 1.2 does not exist === RTOS === Static ram: 103368 Dynamic ram: 122124 of which 0 recycled Never used RAM 13068, free system stack 202 words Tasks: NETWORK(1,ready,12.5%,217) HEAT(3,nWait 6,0.0%,362) 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,delaying,0.8%,101) MAIN(1,running,84.9%,651) IDLE(0,ready,0.9%,29) AIN(4,delaying,0.9%,268), total 100.0% Owned mutexes: === Platform === Last reset 00:00:33 ago, cause: software Last software reset at 2024-07-29 08:04, reason: StuckInSpinLoop, none spinning, available RAM 12396, slot 1 Software reset code 0x4093 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044f80f BFAR 0xe000ed38 SP 0x200043f0 Task NETW Freestk 4294953692 ok Stack: 00000000 2000305c 10000000 e000e000 200043fd 000a1821 000a0efa 61010000 000a0ee3 20003058 ffffffff 00000000 0deb5022 20002878 2002c424 ffffffff 20011800 00000009 000a0f97 20004498 2002c420 200114f8 0009e1df 2002c420 0002dfab 2002c424 a5a5a5a5 Error status: 0x00 MCU revision 3, ADC conversions started 33534, completed 33534, timed out 0, errs 0 MCU temperature: min 37.3, current 38.4, max 38.4 Supply voltage: min 23.9, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/140/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 2, read errors 0, write errors 1, ifcnt 30, reads 1738, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 30, reads 1738, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 21, reads 1738, 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 1737, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 21, reads 1738, writes 10, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2024-07-29 08:05:40 Cache data hit count 64135214 Slowest loop: 6.20ms; fastest: 0.16ms === Storage === Free file entries: 19 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 1.5ms, write time 4.8ms, 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 Heater 2 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 0x0000803 Code queue 0 is empty Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === Filament sensors === check 0 clear 319150 Extruder 0 sensor: ok Extruder 1 sensor: no filament === CAN === Messages queued 319, received 696, lost 0, errs 1, boc 0 Longest wait 1ms for reply type 6018, peak Tx sync delay 288, free buffers 26 (min 25), ts 168/167/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 10.93ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(2) 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 e8:68:e7:e1:4e:b7 Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 36232 WiFi IP address 10.1.10.21 Signal strength -67dBm, channel 11, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0Log:
2024-07-28 13:21:39 [warn] Error: WiFi module reported: Auto reconnect succeeded power up + 00:00:00 [info] Event logging started at level debug power up + 00:00:00 [info] Running: Duet 3 Mini5plus WiFi: 3.5.2 (2024-06-11 17:14:16) power up + 00:00:00 [debug] Done! power up + 00:00:00 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running. power up + 00:00:01 [warn] WiFi module started power up + 00:00:07 [warn] WiFi module is connected to access point SD3D-24, IP address 10.1.10.21 power up + 00:00:08 [warn] HTTP client 10.1.10.9 login succeeded (session key 3150589034) 2024-07-29 08:05:15 [warn] Date and time set at power up + 00:00:08 2024-07-29 08:05:40 [debug] === Diagnostics === 2024-07-29 08:05:40 [debug] RepRapFirmware for Duet 3 Mini 5+ version 3.5.2 (2024-06-11 17:14:16) running on Duet 3 Mini5plus WiFi (standalone mode) 2024-07-29 08:05:40 [debug] Board ID: T69HG-KN6KL-K65J0-409NJ-JYW1Z-RZQJW 2024-07-29 08:05:40 [debug] Used output buffers: 1 of 40 (18 max) 2024-07-29 08:05:40 [debug] Error in macro line 17 while starting up: Driver 1.0 does not exist Driver 1.1 does not exist Driver 1.3 does not exist Driver 1.4 does not exist Driver 1.2 does not exist 2024-07-29 08:05:40 [debug] === RTOS === -
undefined Phaedrux marked this topic as a question
-
undefined Phaedrux moved this topic from General Discussion
-
@ProteanReverie said in Duet 3 mini5+ nightly restarts:
I am going to swap out the main board with an unused spare I have on hand and try testing with that. I will then be able to do any tests on the current board from a benchtop setup.
I did not make it this far. I did some pre-install setup tasks and testing on the spare unused board, and wound up finding the fresh board and SD card seem to have the same SD disconnecting issue. Not always, but usually if I send an M122 P104 S10, the SD card will become unavailable. I had copied the files from the SD card of the board I originally found the issue on to the fresh board's fresh SD card via windows prior to this testing.
I have additionally tested older firmware versions on this fresh board I opened this morning. I have tried 3.5.1 and 3.4.6, both still having the SD card usually become unresponsive after the command is sent.
I have found that if it does not fail the first time I run the command after a power-up, it will likely not fail on subsequent tests during that power-cycling. However, power-cycling it and testing again can result in the failure. Worth noting perhaps that I had run the test over 10 times on a single power-up on Friday which then crashed this morning in my last post.
Additionally, in regards to a simple M122 for the general diagnostics causing crashes/restarts, that could maybe be related as I do have logging enabled and thus M122 would also be writing to the SD card for the log file.
This is now 2 of my 3 boards this SD issue is confirmed occurring on, and I see there are other posts on this forum indicating that at some point there were hardware/soldering issues with the SD slots on the Duet 3 Mini 5+, though that seems to have been resolved a couple of years ago. For reference the three boards I am working on are all v1.02 purchased from Filastruder on 5/10/24. The serial numbers of the two confirmed to have the SD issue are WD11865 and WD11866. My remaining board that is not yet tested for this issue is WD11864.
-
I spent some time today testing some things related to the SD card dismounting issue
This appears it may be related to the SD cards themselves, though not certain. I ran a series of tests of power cycling the board, running M122 P104 S10, noting result, and then starting that process over. If I encountered the issue where the SD card becomes unavailable at the start of writing, I stopped testing that setup. Otherwise, I initially considered a 10-success streak as passing. Until the last test, these were all using the SD cards provided with the boards. Here are my results:
Expansion board (previously untested), expansion card (previously untested) - passed 10 tests (may be invalid pass, see next section)
Bench board (new board from last post, tested bad before), expansion card - passed 10 tests (may be invalid pass, see next section)
Bench board, bench card (previously tested bad) - failed on test 3
Bench board, bench card, no wifi or logging - failed on test 5
Bench board, bench card, no logging and no debugging - failed on test 2
bench board, bench card, files from expansion board - failed test 3
bench board, bench card, reformatted with smallest allocation size - passed 10 tests, though very slow speeds
bench board, bench card, reformatted with largest allocation size - failed on test 8At this point, I wanted to sanity check my first two tests and got these results:
bench board, expansion card - failed on test 6
expansion board, expansion card - failed on test 4so, either something happened to that card after the initial tests, or the initial tests may be invalid...
Following that I tested with a new 16GB Sandisk micoSDHC UHS-I card I had which was removed from the package just before testing. I did not format, load files onto, or do anything with it between opening the package and inserting it into the Duet:
Bench board, new 16GB card - passed 20 tests in a row -
Interesting. Are you able to do a surface format of one of the potentially bad cards and try the test again?
-
@Phaedrux said in Duet 3 mini5+ nightly restarts 3.5.2:
Interesting. Are you able to do a surface format of one of the potentially bad cards and try the test again?
I am unfamiliar with the terminology "surface format", and a quick google isn't clearing that up. What I have done is used the official SD card formatting tool linked to here https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card . I used the option of "Overwrite format" without "CHS format size adjustment" checked. This did merge everything into one partition thus resulting in one partition of ~8GB as opposed to how it arrived or how windows formatting left it, which had 2 partitions and a large chunk of unallocated space, with only a 2GB partition visible. This appears to have produced a promising result as it has survived 20 consecutive trials without error. I will proceed with adding files and testing, then trying with the other SD cards and boards and testing those, should no issues arise.
-
I have completed some additional testing. Following an official SD tool formatting, both the main board and the bench board SD cards worked just fine and were able to pass 20 tests without issue. However, the expansion board card still has an issue even after the official SD tool formatting, and initially failed on the second test. I also tested that card in a Duet 2 Wi-Fi running 3.5.1, which passed 20 tests without issue. I then tested it in the bench board where it failed on the first test.
I have replaced the faulty card with the new 16GB card from yesterday and re-built those boards into my machine to resume my testing. The bench board is also set up to idle away to see if it randomly restarts again but could also be used for other testing if any more data would be of use.
-
@ProteanReverie said in Duet 3 mini5+ nightly restarts 3.5.2:
surface format
The opposite of a "quick" format. It zeros the entire drive area rather than just the file table. If there are bad cells they would get written to and potentially corrected or remapped.
@ProteanReverie said in Duet 3 mini5+ nightly restarts 3.5.2:
I used the option of "Overwrite format" without "CHS format size adjustment" checked.
This is what I war referring to.
@ProteanReverie said in Duet 3 mini5+ nightly restarts 3.5.2:
which had 2 partitions and a large chunk of unallocated space
that's the way the card comes imaged from the factory. One partition for standalone mode and another for the SBC.
-
@Phaedrux said in Duet 3 mini5+ nightly restarts 3.5.2:
The opposite of a "quick" format. It zeros the entire drive area rather than just the file table. If there are bad cells they would get written to and potentially corrected or remapped.
Ok, that is what I had assumed, just never heard it with that term. Thank you for clarifying.
Just for clarity of data, when I formatted yesterday using windows format I did not have "quick format" selected.
