Reboots/crashes - RRF ≤3.5.0-rc1
-
@Exerqtor Noticed the multiple disconnect reconnects. I was running into those this summer. To the point was not able to do anything on the paneldues as was clicking the acknowledgment trying to get past them. At times they were rapidly filling the screen. DWC was also knocked out by them.
Mine seemed to be caused by having a fancy mesh network for WiFi and a wireless Vtech landline phone sitting on the same workbench. Traded phones with the one in the back bedroom which was a different brand. That helped some. Then removed the mesh node in the workshop and installed a Ubiquiti Nanostation . The constant disconnect/reconnects stopped after that. The workshop is about 80 feet behind the room the router is in so I had mesh nodes in the storage building and the workshop to supply WiFi.
What was weird was it did not happen constantly but seemed to be worse in the afternoon. I thought heat in the workshop was the problem since it became worse in late June and started running the air conditioning when printing. ( which caused another whole set of issues. ) but that did not help.
Now things seem stable out there. 2 are on 3.4.6 and one is on 3.5.0-rc.1. All were affected by the WiFi problem. When it was dropping and reconnecting never checked if it was also resetting or rebooting.
Meanwells can fail. I had a SE-600-24 in a Ender 5 plus that would cause reboots when the heated bed was first started in cool weather. Removed it when I went to a line powered heated bed and installed a smaller ( and quieter ) RSP-150-24 meanwell. That power supply was larger than the original 500 watt that had failed so it should have been fine.
-
@Exerqtor said in Reboots/crashes - RRF 3.5.0-rc1:
@deckingman
I have no idea to be honest, but at least it's a genuine Meanwell UHP-200-24 for the 24v rail, the bed is mains powered through a SSR, and the Duet 5v rail is running of a genuine Meanwell RS-25-5.The mains voltage are on the higher side here, BUT it's stable @ 245v, and both the PSU's are rated to handle everything between 88 - 264v.
So it SHOULD be enough power on hand unless the 24v is wonky.
Yes I wasn't thinking about the capability of the PSU, just the fact that the M122 shows Vin varying from 22.9 to 26.1 when the machine is idle. Maybe there are some fast transient excursions that ought not to be there. Given everything else that you've tried, it might be worth looking into further.....
-
@KenW
I hear you, but if it turns out being the disconnects/connects causing the crashing issues, this is a issue that needs solving on the Duet side. NOT by changing out any of the other WiFi equipment (Ubiquity Unifi network, with a dedicated 2.5Ghz SSID).
The Duet is leaving the house before any of the AP's if we put it that way
😂😂😂😂Regarding the voltage issues, I haven't got the feeling that's the cause since the voltages are still WAY within the Duets operating specs after all.
@deckingman
Yeah that's true, I just have a sneaking feeling this all mess has the route in something related to the WiFi module at this point.
Other than that it had another crash a coupe hours ago that I just saw.
I've been connecting to the printer with both my phone and laptop intermittently do check if anythings happening (hence the two other IP's)
debug log:2023-10-29 12:40:42 [warn] HTTP client 192.168.10.x login succeeded (session key 451652038) 2023-10-29 12:59:12 [warn] HTTP client 192.168.10.2xx login succeeded (session key 947195611) 2023-10-29 13:47:02 [warn] HTTP client 192.168.10.xxx login succeeded (session key 834710639) 2023-10-29 13:51:46 [warn] HTTP client 192.168.10.xxx disconnected 2023-10-29 14:00:05 [warn] HTTP client 192.168.10.xxx login succeeded (session key 2059405738) 2023-10-29 14:00:55 [warn] HTTP client 192.168.10.xxx disconnected 2023-10-29 16:39:10 [warn] HTTP client 192.168.10.xxx login succeeded (session key 3826474446) 2023-10-29 17:28:47 [warn] HTTP client 192.168.10.xxx login succeeded (session key 2170746625) 2023-10-29 18:20:29 [warn] HTTP client 192.168.10.xxx login succeeded (session key 3718996851) power up + 00:00:03 [info] Event logging started at level debug power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-rc.1 (2023-08-31 16:16:56) power up + 00:00:03 [info] Event logging stopped power up + 00:00:03 [info] Event logging started at level debug power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-rc.1 (2023-08-31 16:16:56) power up + 00:00:03 [debug] Done! power up + 00:00:03 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running. power up + 00:00:04 [warn] WiFi module started power up + 00:00:08 [warn] WiFi module is connected to access point RV32-IOT2G, IP address 192.168.10.xxxx power up + 00:00:08 [warn] HTTP client 192.168.10.xxx login succeeded (session key 3944043149) 2023-10-29 18:28:38 [warn] Date and time set at power up + 00:00:08x = desktop
xx = phone
xxx = laptop
xxxx = printers IP.
M122:=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.1 (2023-08-31 16:16:56) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ Used output buffers: 1 of 40 (29 max) === RTOS === Static ram: 102836 Dynamic ram: 124036 of which 0 recycled Never used RAM 11688, free system stack 182 words Tasks: NETWORK(1,nWait,16.3%,211) HEAT(3,nWait,0.0%,352) Move(4,nWait,0.0%,358) CanReceiv(6,nWait,0.0%,773) CanSender(5,nWait,0.0%,337) CanClock(7,delaying,0.0%,351) TMC(4,nWait,0.7%,108) MAIN(1,running,81.9%,704) IDLE(0,ready,0.3%,29) AIN(4,delaying,0.8%,264), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 01:24:28 ago, cause: software Last software reset at 2023-10-29 18:28, reason: HardFault invState, Gcodes spinning, available RAM 5200, slot 0 Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00020000 ICSR 0x00000803 BFAR 0xe000ed38 SP 0x20011fa8 Task NETW Freestk 482 ok Stack: 000001b0 00000002 200014ec 00000000 ffffffff 0009df2d 00000000 600f0000 00000000 00000000 00000000 00000000 200301d4 00000800 20035710 2002bf00 20018668 2002bd9d 20018668 2001e880 0002fedf 00000000 00000000 00000000 20012058 00000014 00000000 Error status: 0x00 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 5068453, completed 5068451, timed out 0, errs 0 MCU temperature: min 34.4, current 35.1, max 37.8 Supply voltage: min 23.1, current 24.1, max 26.0, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/33, heap memory allocated/used/recyclable 2048/564/128, gc cycles 236 Events: 0 queued, 0 completed Driver 0: standstill, SG min 68, read errors 0, write errors 1, ifcnt 235, reads 4587, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 68, read errors 0, write errors 1, ifcnt 231, reads 4587, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 115, reads 4586, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 116, reads 4586, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 117, reads 4587, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-10-29 19:52:58 Cache data hit count 4294967295 Slowest loop: 12.68ms; fastest: 0.13ms === Storage === Free file entries: 18 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 6.4ms, write time 7.1ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, 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 1 is on, I-accum = 0.0 === GCodes === Movement locks held by null, null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is doing "G4 S1" in state(s) 0 0, running macro 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 === Extruder 0 sensor: no filament === CAN === Messages queued 45625, received 103943, lost 0, boc 0 Longest wait 2ms for reply type 6031, peak Tx sync delay 336, free buffers 26 (min 25), ts 25342/25341/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 24.73ms; 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.1beta4 MAC address c4:5b:be:ce:91:93 Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 42972 WiFi IP address 192.168.10.xxxx Signal strength -49dBm, channel 6, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0 -
@Exerqtor If the problem is some sort of short transient from the power supply that could easily not be captured by the voltage monitor.
It might be better to test using the same setup you had when things crashed, so Orca Slicer plus Chrome? Especially if Orca slicer is doing something that is different to the normal connection pattern generated by DWC.
-
Dumb question but where is this debug.log that you are referring to?
-
@DaveA said in Reboots/crashes - RRF 3.5.0-rc1:
Dumb question but where is this debug.log that you are referring to?
It has to be configured through M929.
-
@Exerqtor thanks for creating this new thread, it makes this issue easier to track.
Please continue to post M122 reports whenever this happens, in case I can establish some common data in the stack trace.
Please install the firmware at https://www.dropbox.com/scl/fo/tjznycpk7bv7sj71p0ssl/h?rlkey=096p4nvgmigyrb20jj8olg3wu&dl=0. The only issue it fixes that might cause this type of crash is related to filament monitors and (I think) tool changes, so I doubt that it will fix the issue you are experiencing.
Re DWC disconnects/reconnects, do you have a PanelDue connected? See https://forum.duet3d.com/topic/33538/duet-2-ethernet-disconnect-when-printing-and-paneldue-connected.
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 -
@Exerqtor out of curiosity since you did not mention it (I have to admit I did not read through that huge other thread): The fact that - if I understand you correctly - you say the Mini worked first but started to show issues after a while makes me wonder a bit.
Therefore, just to have asked and based on my rusty electronics knowledge - did you check the following two things:
- a faulty power supply might produce spikes that will probably never pop up on the voltage display of the duet but might cause issues or even slowly kill your controller (evil to find out and as far as I can tell the Duet is well hardened against such things, but there is always a limit for that). I would not know how to find this that except with an oscilloscope however, or by blindly replacing the power supply with another one that is known to work.
- obscure emf / crosstalk issues (which I would not rule out on a new printer) might be found or at least narrowed down if you run the Duet with literally everything unplugged. Do these reboots happen even then? If yes, replace the power supply next. If not, start to plug in things back in one item at a time, wait for the issue to (not) happen, turn off the Duet, plug the next in (or unplug and note the possible culprit if it happens - but do not stop there), boot the Duet etc. If you have located all connectors that seem to cause the issue, remove all the others, plug the first of those in and repeat the process. If you are lucky, the issue happens at once, if not, you need go on until you found its counterpart(s)... and so on.
It is an unnervingly lengthy process since you will need to wait for an extended period of time between each attempt, but since you had to fight with that issue for so long now... maybe that process helps. Well, unless you already tried that...
-
@dc42 said in Reboots/crashes - RRF 3.5.0-rc1:
@Exerqtor thanks for creating this new thread, it makes this issue easier to track.
Please continue to post M122 reports whenever this happens, in case I can establish some common data in the stack trace.
Will do, haven't been another reboot since the last one i posted. But the desktop has been in hibernation without any connections to DWC. But i will continue posting reports until a solution is found
🤣Please install the firmware at https://www.dropbox.com/scl/fo/tjznycpk7bv7sj71p0ssl/h?rlkey=096p4nvgmigyrb20jj8olg3wu&dl=0. The only issue it fixes that might cause this type of crash is related to filament monitors and (I think) tool changes, so I doubt that it will fix the issue you are experiencing.
Installing that now, thanks!
Re DWC disconnects/reconnects, do you have a PanelDue connected? See https://forum.duet3d.com/topic/33538/duet-2-ethernet-disconnect-when-printing-and-paneldue-connected.
Yup i have a PanelDue connected as well, i'll update the system description to inlcude that as i completely forgot to mention it.
@NeoDue said in Reboots/crashes - RRF 3.5.0-rc1:
@Exerqtor out of curiosity since you did not mention it (I have to admit I did not read through that huge other thread): The fact that - if I understand you correctly - you say the Mini worked first but started to show issues after a while makes me wonder a bit.
Therefore, just to have asked and based on my rusty electronics knowledge - did you check the following two things:
- a faulty power supply might produce spikes that will probably never pop up on the voltage display of the duet but might cause issues or even slowly kill your controller (evil to find out and as far as I can tell the Duet is well hardened against such things, but there is always a limit for that). I would not know how to find this that except with an oscilloscope however, or by blindly replacing the power supply with another one that is known to work.
To emboss that statement i made about the Mini seeming to be working a little bit:
- When i hooked it up and did the initial tests i didn't have the desktop computer or any other clients connected through DWC either. I just did the PID tuning etc. from the PanelDue and ran a quick test cube to see that all actually worked. Then the printer stood idle witout no use or anything until I had time to work on it in early october, when i quickly
- obscure emf / crosstalk issues (which I would not rule out on a new printer) might be found or at least narrowed down if you run the Duet with literally everything unplugged. Do these reboots happen even then? If yes, replace the power supply next. If not, start to plug in things back in one item at a time, wait for the issue to (not) happen, turn off the Duet, plug the next in (or unplug and note the possible culprit if it happens - but do not stop there), boot the Duet etc. If you have located all connectors that seem to cause the issue, remove all the others, plug the first of those in and repeat the process. If you are lucky, the issue happens at once, if not, you need go on until you found its counterpart(s)... and so on.
It is an unnervingly lengthy process since you will need to wait for an extended period of time between each attempt, but since you had to fight with that issue for so long now... maybe that process helps. Well, unless you already tried that...
saw that the issues wasn't solved at all.
I'll try to see how it behaves over the weekend, and if it's still acting up (which i assume it will) I'll try running it "barebones" for a day or two and see if anything happens.
Not saying a faulty PSU or EMF ain't the issue, it's just not what my gut is telling me at this point.
-
And a new crash, also while idle, but being active on the desktop with an instance of DWC open through OrcaSlicer.
This is the first crash in 4 days, and the only difference (other than FW updates that shouldn't effect this anyways), is that I've been active on the desktop with an DWC instance connected.
Don't know if this is just me seeing paterns in the clouds lol, but i'm sure starting to see a clear pattern in when it crash or not.
This is with RRF 3.5.0rc1+ on the Mini / 1LC, and 3.5.0rc7 on the panel due.degbug:
power up + 00:00:03 [info] Event logging started at level debug power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-rc.1+ (2023-11-01 10:29:03) power up + 00:00:03 [info] Event logging stopped power up + 00:00:03 [info] Event logging started at level debug power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-rc.1+ (2023-11-01 10:29:03) power up + 00:00:03 [debug] Done! power up + 00:00:03 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running. power up + 00:00:04 [warn] Error: Heater 1 fault: failed to read sensor: notReady power up + 00:00:04 [info] M291: - Event notification - Heater 1 fault: failed to read sensor: notReady power up + 00:00:04 [debug] - Event notification - power up + 00:00:04 [debug] Heater 1 fault: failed to read sensor: notReady power up + 00:00:08 [warn] WiFi module is connected to access point RV32-IOT2G, IP address 192.168.10.x power up + 00:00:08 [warn] HTTP client 192.168.10.xx login succeeded (session key 1133366275) 2023-11-03 23:29:57 [warn] Date and time set at power up + 00:00:08M122:
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.1+ (2023-11-01 10:29:03) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ Used output buffers: 9 of 40 (40 max) === RTOS === Static ram: 102812 Dynamic ram: 123924 of which 0 recycled Never used RAM 11824, free system stack 186 words Tasks: NETWORK(2,nWait,18.3%,209) HEAT(3,nWait,0.0%,354) Move(4,nWait,0.0%,358) CanReceiv(6,nWait,0.0%,797) CanSender(5,nWait,0.0%,336) CanClock(7,delaying,0.0%,350) TMC(4,nWait,0.7%,108) MAIN(1,running,79.8%,670) IDLE(0,ready,0.3%,29) AIN(4,delaying,0.8%,264), total 100.0% Owned mutexes: === Platform === Last reset 00:13:05 ago, cause: software Last software reset at 2023-11-03 23:29, reason: HardFault invState, Gcodes spinning, available RAM 10940, slot 2 Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00020000 ICSR 0x00000803 BFAR 0xe000ed38 SP 0x20011f88 Task NETW Freestk 482 ok Stack: 000001b0 00000002 200014e8 00000000 ffffffff 0009e9cd 00000000 600f0000 00000000 00000000 00000000 00000000 20031c4c 00000800 2002c0e0 2002c0e0 00000001 2002bf7d 20018658 2001e868 0002ff97 00000000 00000000 00000000 20012038 00000014 b5dd8a35 Error status: 0x04 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 785822, completed 785822, timed out 0, errs 0 MCU temperature: min 37.0, current 37.4, max 40.1 Supply voltage: min 22.5, current 24.1, max 26.5, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/33, heap memory allocated/used/recyclable 2048/1856/1420, gc cycles 36 Events: 1 queued, 1 completed Driver 0: standstill, SG min 16, read errors 0, write errors 1, ifcnt 31, reads 41299, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 246, read errors 0, write errors 1, ifcnt 27, reads 41299, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 2, read errors 0, write errors 1, ifcnt 161, reads 41299, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 2, read errors 0, write errors 1, ifcnt 162, reads 41298, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 2, read errors 0, write errors 1, ifcnt 164, reads 41299, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-11-03 23:42:53 Cache data hit count 1378843841 Slowest loop: 13.16ms; fastest: 0.13ms === Storage === Free file entries: 18 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 6.9ms, write time 4.6ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, 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 doing "G4 S1" in state(s) 0 0, running macro 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 0 Extruder 0 sensor: no filament === CAN === Messages queued 7076, received 16136, lost 0, errs 1, boc 0 Longest wait 2ms for reply type 6031, peak Tx sync delay 231, free buffers 26 (min 25), ts 3926/3925/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 8.42ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 3 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 2.1beta4 MAC address c4:5b:be:ce:91:93 Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 39880 WiFi IP address 192.168.10.x Signal strength -50dBm, channel 6, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0A new development this time is that the hotend heater reports fault and reads 2000C after the crash.
After when restarting it manually (with
M999) it reports back as usual (active / 25C). -
Another crash about 4 hours and 30minutes ago, one instance of DWC open on the desktop but with orcaslicer/other instances closed (printer idle).
This time it also reports a heater fault and 2000c on the hotend, so it seems like the toolboard don't get recognized after the crashes now.
debug:
2023-11-05 00:02:51 [warn] HTTP client 192.168.10.100 login succeeded (session key 328058056) power up + 00:00:03 [info] Event logging started at level debug power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-rc.1+ (2023-11-01 10:29:03) power up + 00:00:03 [info] Event logging stopped power up + 00:00:03 [info] Event logging started at level debug power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-rc.1+ (2023-11-01 10:29:03) power up + 00:00:03 [debug] Done! power up + 00:00:03 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running. power up + 00:00:04 [warn] Error: Heater 1 fault: failed to read sensor: notReady power up + 00:00:04 [info] M291: - Event notification - Heater 1 fault: failed to read sensor: notReady power up + 00:00:04 [debug] - Event notification - power up + 00:00:04 [debug] Heater 1 fault: failed to read sensor: notReady power up + 00:00:04 [warn] WiFi module started power up + 00:00:08 [warn] WiFi module is connected to access point RV32-IOT2G, IP address 192.168.10.x power up + 00:00:10 [warn] HTTP client 192.168.10.xx login succeeded (session key 987728275) 2023-11-05 06:19:22 [warn] Date and time set at power up + 00:00:10M122 after crash:
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.1+ (2023-11-01 10:29:03) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ Used output buffers: 1 of 40 (34 max) === RTOS === Static ram: 102812 Dynamic ram: 123924 of which 0 recycled Never used RAM 11824, free system stack 182 words Tasks: NETWORK(1,ready,58.6%,203) HEAT(3,nWait,0.1%,331) Move(4,nWait,0.0%,356) CanReceiv(6,nWait,0.2%,774) CanSender(5,nWait,0.0%,336) CanClock(7,delaying,0.0%,350) TMC(4,nWait,2.3%,108) MAIN(1,running,35.2%,670) IDLE(0,ready,0.9%,29) AIN(4,delaying,2.7%,264), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 04:30:58 ago, cause: software Last software reset at 2023-11-05 06:19, reason: HardFault invState, Gcodes spinning, available RAM 11236, slot 1 Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00020000 ICSR 0x00000803 BFAR 0xe000ed38 SP 0x20011f88 Task NETW Freestk 482 ok Stack: 000001ae 00000002 200014e8 00000000 20032e1a 0009e9cd 00000000 600f0000 00000000 00000000 00000000 00000000 200303ec 00000800 20035928 2002c0e0 20018658 2002bf7d 20018658 2001e868 0002ff97 00000000 00000000 00000000 20012038 00000014 904c0824 Error status: 0x00 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 16258966, completed 16258966, timed out 0, errs 0 MCU temperature: min 36.2, current 37.2, max 39.2 Supply voltage: min 22.5, current 24.1, max 26.5, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/33, heap memory allocated/used/recyclable 2048/716/280, gc cycles 756 Events: 1 queued, 1 completed Driver 0: standstill, SG min 16, read errors 0, write errors 1, ifcnt 69, reads 3742, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 236, read errors 0, write errors 1, ifcnt 64, reads 3742, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 193, reads 3742, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 194, reads 3741, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 196, reads 3742, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-11-05 10:50:10 Cache data hit count 4294967295 Slowest loop: 13.22ms; fastest: 0.13ms === Storage === Free file entries: 18 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 7.2ms, write time 4.4ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, 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 doing "G4 S1" in state(s) 0 0, running macro 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 0 Extruder 0 sensor: no filament === CAN === Messages queued 146340, received 333359, lost 0, errs 0, boc 0 Longest wait 2ms for reply type 6053, peak Tx sync delay 270, free buffers 26 (min 25), ts 81295/81294/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 8.43ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 2 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 2.1beta4 MAC address c4:5b:be:ce:91:93 Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 42960 WiFi IP address 192.168.10.x Signal strength -49dBm, channel 6, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0And here is a M122 report from after restarting the board(s) with M999:
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.1+ (2023-11-01 10:29:03) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ Used output buffers: 4 of 40 (29 max) === RTOS === Static ram: 102812 Dynamic ram: 122012 of which 12 recycled Never used RAM 13724, free system stack 198 words Tasks: NETWORK(1,ready,11.8%,228) HEAT(3,nWait,0.0%,356) Move(4,nWait,0.0%,358) CanReceiv(6,nWait,0.0%,797) CanSender(5,nWait,0.0%,336) CanClock(7,delaying,0.0%,352) TMC(4,nWait,0.7%,116) MAIN(1,running,85.2%,670) IDLE(0,ready,1.4%,29) AIN(4,delaying,0.8%,272), total 100.0% Owned mutexes: === Platform === Last reset 00:00:21 ago, cause: software Last software reset at 2023-11-05 10:51, reason: User, Gcodes spinning, available RAM 11824, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 21884, completed 21884, timed out 0, errs 0 MCU temperature: min 37.0, current 37.2, max 40.1 Supply voltage: min 8.3, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/29, heap memory allocated/used/recyclable 2048/1692/1296, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 16, read errors 0, write errors 1, ifcnt 83, reads 1121, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 236, read errors 0, write errors 1, ifcnt 78, reads 1121, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 207, reads 1121, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 208, reads 1120, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 210, reads 1121, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-11-05 10:52:03 Cache data hit count 36913447 Slowest loop: 5.73ms; fastest: 0.14ms === Storage === Free file entries: 18 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 3.8ms, write time 6.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, 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 1 is on, I-accum = 0.0 === GCodes === Movement locks held by null, null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is doing "G4 S1" in state(s) 0 0, running macro 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 0 Extruder 0 sensor: no filament === CAN === Messages queued 208, received 436, lost 0, errs 0, boc 0 Longest wait 2ms for reply type 6031, peak Tx sync delay 3, free buffers 26 (min 25), ts 109/108/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 8.47ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 2 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 2.1beta4 MAC address c4:5b:be:ce:91:93 Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 39880 WiFi IP address 192.168.10.x Signal strength -50dBm, channel 6, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0
It should be noted that it's no recent wifi connections/disconnections leading up to any of the recent crashes in the logs, however it's been one or more connected session on each of them.
-
@Exerqtor said in Reboots/crashes - RRF 3.5.0-rc1:
Supply voltage: min 8.3, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
I still maintain that swapping out your PSU might be a good. Early on you were showing min 22.9, max 26.1 when idle - that ain't normal. Now you have a minimum of 8.3V - that definitely ain't normal.
-
@Exerqtor thanks. Those last 2 M122 reports have some common features.
-
@deckingman said in Reboots/crashes - RRF 3.5.0-rc1:
@Exerqtor said in Reboots/crashes - RRF 3.5.0-rc1:
Supply voltage: min 8.3, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
I still maintain that swapping out your PSU might be a good. Early on you were showing min 22.9, max 26.1 when idle - that ain't normal. Now you have a minimum of 8.3V - that definitely ain't normal.
Yeah i don't know if those readings can maybe (thinking out loud here now) off since i run the Duet3 of a 5v PSU? And the 24v PSU is switched off/on with relays each time the board reboots.
🤷♂️Just to be clear that's more of a question than a statement from my end.
@dc42 said in Reboots/crashes - RRF 3.5.0-rc1:
@Exerqtor thanks. Those last 2 M122 reports have some common features.
I just got home, and it litterlarly crashed a minute or two after i came home, this time it's also showing heaterfault & 2000c on the hotend
debug:
power up + 00:00:03 [info] Event logging started at level debug power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-rc.1+ (2023-11-01 10:29:03) power up + 00:00:03 [info] Event logging stopped power up + 00:00:03 [info] Event logging started at level debug power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-rc.1+ (2023-11-01 10:29:03) power up + 00:00:03 [debug] Done! power up + 00:00:03 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running. power up + 00:00:04 [warn] WiFi module started power up + 00:00:04 [warn] Error: Heater 1 fault: failed to read sensor: notReady power up + 00:00:04 [info] M291: - Event notification - Heater 1 fault: failed to read sensor: notReady power up + 00:00:04 [debug] - Event notification - power up + 00:00:04 [debug] Heater 1 fault: failed to read sensor: notReady power up + 00:00:08 [warn] WiFi module is connected to access point RV32-IOT2G, IP address 192.168.10.x power up + 00:00:08 [warn] HTTP client 192.168.10.xx login succeeded (session key 2917043153) 2023-11-06 15:53:21 [warn] Date and time set at power up + 00:00:08M122 after crash:
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.1+ (2023-11-01 10:29:03) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ Used output buffers: 1 of 40 (40 max) === RTOS === Static ram: 102812 Dynamic ram: 123924 of which 0 recycled Never used RAM 11824, free system stack 186 words Tasks: NETWORK(1,ready,17.5%,234) HEAT(3,nWait,0.0%,352) Move(4,nWait,0.0%,358) CanReceiv(6,nWait,0.0%,797) CanSender(5,nWait,0.0%,336) CanClock(7,delaying,0.0%,350) TMC(4,nWait,0.7%,108) MAIN(1,running,80.7%,670) IDLE(0,ready,0.3%,29) AIN(4,delaying,0.8%,264), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:13:58 ago, cause: software Last software reset at 2023-11-06 15:53, reason: HardFault invState, Platform spinning, available RAM 10940, slot 0 Software reset code 0x4060 HFSR 0x40000000 CFSR 0x00020000 ICSR 0x00000803 BFAR 0xe000ed38 SP 0x20011f88 Task NETW Freestk 482 ok Stack: 000001af 00000002 200014e8 00000000 20032e1b 0009e9cd 00000000 600f0000 00000000 00000000 00000000 00000000 200303ec 00000800 20035928 2002c0e0 20018658 2002bf7d 20018658 2001e868 0002ff97 00000000 00000000 00000000 20012038 00000014 b5dd8a35 Error status: 0x04 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 838810, completed 838810, timed out 0, errs 0 MCU temperature: min 36.2, current 36.6, max 39.2 Supply voltage: min 23.3, current 24.1, max 25.9, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/33, heap memory allocated/used/recyclable 2048/1096/660, gc cycles 39 Events: 1 queued, 1 completed Driver 0: standstill, SG min 16, read errors 0, write errors 1, ifcnt 107, reads 44114, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 244, read errors 0, write errors 1, ifcnt 102, reads 44114, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 2, read errors 0, write errors 1, ifcnt 225, reads 44114, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 2, read errors 0, write errors 1, ifcnt 226, reads 44113, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 2, read errors 0, write errors 1, ifcnt 228, reads 44114, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-11-06 16:07:29 Cache data hit count 1443468903 Slowest loop: 12.56ms; fastest: 0.13ms === Storage === Free file entries: 18 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 6.9ms, write time 4.4ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, 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 doing "G4 S1" in state(s) 0 0, running macro 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 0 Extruder 0 sensor: no filament === CAN === Messages queued 7558, received 17228, lost 0, errs 1, boc 0 Longest wait 3ms for reply type 6053, peak Tx sync delay 327, free buffers 26 (min 25), ts 4194/4193/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 6.64ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 2 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 2.1beta4 MAC address c4:5b:be:ce:91:93 Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 42952 WiFi IP address 192.168.10.x Signal strength -47dBm, channel 6, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0M122 after manual reboot with M999:
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.1+ (2023-11-01 10:29:03) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ Used output buffers: 1 of 40 (32 max) === RTOS === Static ram: 102812 Dynamic ram: 122024 of which 0 recycled Never used RAM 13724, free system stack 198 words Tasks: NETWORK(1,ready,13.4%,238) HEAT(3,nWait,0.0%,360) Move(4,nWait,0.0%,358) CanReceiv(6,nWait,0.0%,797) CanSender(5,nWait,0.0%,336) CanClock(7,delaying,0.0%,352) TMC(4,nWait,0.7%,116) MAIN(1,running,84.0%,670) IDLE(0,ready,1.0%,29) AIN(4,delaying,0.8%,272), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:00:32 ago, cause: software Last software reset at 2023-11-06 16:08, reason: User, Gcodes spinning, available RAM 11824, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 32518, completed 32518, timed out 0, errs 0 MCU temperature: min 36.3, current 36.8, max 39.2 Supply voltage: min 8.3, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/29, heap memory allocated/used/recyclable 2048/904/508, gc cycles 1 Events: 0 queued, 0 completed Driver 0: standstill, SG min 16, read errors 0, write errors 1, ifcnt 121, reads 1681, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 244, read errors 0, write errors 1, ifcnt 116, reads 1681, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 2, read errors 0, write errors 1, ifcnt 239, reads 1680, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 2, read errors 0, write errors 1, ifcnt 240, reads 1680, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 2, read errors 0, write errors 1, ifcnt 242, reads 1681, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-11-06 16:08:19 Cache data hit count 54882292 Slowest loop: 8.47ms; fastest: 0.13ms === Storage === Free file entries: 18 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 3.6ms, write time 4.1ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, 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 1 is on, I-accum = 0.0 === GCodes === Movement locks held by null, null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is doing "G4 S1" in state(s) 0 0, running macro 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 0 Extruder 0 sensor: no filament === CAN === Messages queued 304, received 651, lost 0, errs 1, boc 0 Longest wait 3ms for reply type 6013, peak Tx sync delay 189, free buffers 26 (min 25), ts 163/162/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 8.45ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 2 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 2.1beta4 MAC address c4:5b:be:ce:91:93 Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 42944 WiFi IP address 192.168.10.x Signal strength -49dBm, channel 6, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0 -
Haven't had much time to derp with the printer this week/weekend, plus my damn desktop computer is starting to slowly bite the dust (rejecting RAM, wohoo).
Anywho, had a couple minutes to check the loggs now while doing som other stuff, and the wifi controller ain't happy.
debug:
power up + 00:00:03 [info] Event logging started at level debug power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-rc.1+ (2023-11-01 10:29:03) power up + 00:00:03 [info] Event logging stopped power up + 00:00:03 [info] Event logging started at level debug power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-rc.1+ (2023-11-01 10:29:03) power up + 00:00:03 [debug] Done! power up + 00:00:03 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running. power up + 00:00:04 [warn] WiFi module started power up + 00:00:06 [warn] Error: WiFi module reported: no known networks found power up + 00:00:06 [warn] WiFi module is idle power up + 00:00:08 [warn] Error: WiFi module reported: no known networks found power up + 00:00:08 [warn] WiFi module is idle power up + 00:00:10 [warn] Error: WiFi module reported: no known networks found power up + 00:00:10 [warn] WiFi module is idle power up + 00:00:12 [warn] Error: WiFi module reported: no known networks found power up + 00:00:12 [warn] WiFi module is idle power up + 00:00:14 [warn] Error: WiFi module reported: no known networks found power up + 00:00:14 [warn] WiFi module is idle power up + 00:00:17 [warn] Error: WiFi module reported: no known networks found power up + 00:00:17 [warn] WiFi module is idle power up + 00:00:19 [warn] Error: WiFi module reported: no known networks found power up + 00:00:19 [warn] WiFi module is idle power up + 00:00:21 [warn] Error: WiFi module reported: no known networks found power up + 00:00:21 [warn] WiFi module is idle power up + 00:00:23 [warn] Error: WiFi module reported: no known networks found power up + 00:00:23 [warn] WiFi module is idle power up + 00:00:25 [warn] Error: WiFi module reported: no known networks found power up + 00:00:25 [warn] WiFi module is idle power up + 00:00:28 [warn] Error: WiFi module reported: no known networks found power up + 00:00:28 [warn] WiFi module is idle power up + 00:00:30 [warn] Error: WiFi module reported: no known networks found power up + 00:00:30 [warn] WiFi module is idle power up + 00:00:32 [warn] Error: WiFi module reported: no known networks found power up + 00:00:32 [warn] WiFi module is idle power up + 00:00:34 [warn] Error: WiFi module reported: no known networks found power up + 00:00:34 [warn] WiFi module is idle power up + 00:00:36 [warn] Error: WiFi module reported: no known networks found power up + 00:00:36 [warn] WiFi module is idle power up + 00:00:39 [warn] Error: WiFi module reported: Failed to load credentials power up + 00:00:39 [warn] WiFi module is idle power up + 00:00:41 [warn] Error: WiFi module reported: no known networks found power up + 00:00:41 [warn] WiFi module is idle power up + 00:00:43 [warn] Error: WiFi module reported: no known networks found power up + 00:00:43 [warn] WiFi module is idle power up + 00:00:45 [warn] Error: WiFi module reported: no known networks found power up + 00:00:45 [warn] WiFi module is idle power up + 00:00:47 [warn] Error: WiFi module reported: no known networks found power up + 00:00:47 [warn] WiFi module is idle power up + 00:00:50 [warn] Error: WiFi module reported: no known networks found power up + 00:00:50 [warn] WiFi module is idle power up + 00:00:52 [warn] Error: WiFi module reported: no known networks found power up + 00:00:52 [warn] WiFi module is idle power up + 00:00:54 [warn] Error: WiFi module reported: no known networks found power up + 00:00:54 [warn] WiFi module is idle power up + 00:00:56 [warn] Error: WiFi module reported: no known networks found power up + 00:00:56 [warn] WiFi module is idle power up + 00:00:58 [warn] Error: WiFi module reported: no known networks found power up + 00:00:58 [warn] WiFi module is idle power up + 00:01:01 [warn] Error: WiFi module reported: no known networks found power up + 00:01:01 [warn] WiFi module is idle power up + 00:01:03 [warn] Error: WiFi module reported: no known networks found power up + 00:01:03 [warn] WiFi module is idle power up + 00:01:05 [warn] Error: WiFi module reported: no known networks found power up + 00:01:05 [warn] WiFi module is idle power up + 00:01:07 [warn] Error: WiFi module reported: no known networks found power up + 00:01:07 [warn] WiFi module is idle power up + 00:01:09 [warn] Error: WiFi module reported: no known networks found power up + 00:01:09 [warn] WiFi module is idle power up + 00:01:12 [warn] Error: WiFi module reported: no known networks found power up + 00:01:12 [warn] WiFi module is idle power up + 00:01:14 [warn] Error: WiFi module reported: no known networks found power up + 00:01:14 [warn] WiFi module is idle power up + 00:01:16 [warn] Error: WiFi module reported: no known networks found power up + 00:01:16 [warn] WiFi module is idle power up + 00:01:18 [warn] Error: WiFi module reported: no known networks found power up + 00:01:18 [warn] WiFi module is idle power up + 00:01:20 [warn] Error: WiFi module reported: no known networks found power up + 00:01:20 [warn] WiFi module is idle power up + 00:01:23 [warn] Error: WiFi module reported: no known networks found power up + 00:01:23 [warn] WiFi module is idle power up + 00:01:25 [warn] Error: WiFi module reported: no known networks found power up + 00:01:25 [warn] WiFi module is idle power up + 00:01:27 [warn] Error: WiFi module reported: no known networks found power up + 00:01:27 [warn] WiFi module is idle power up + 00:01:29 [warn] Error: WiFi module reported: no known networks found power up + 00:01:29 [warn] WiFi module is idle power up + 00:01:32 [warn] Error: WiFi module reported: no known networks found power up + 00:01:32 [warn] WiFi module is idle power up + 00:01:34 [warn] Error: WiFi module reported: no known networks found power up + 00:01:34 [warn] WiFi module is idle power up + 00:01:36 [warn] Error: WiFi module reported: no known networks found power up + 00:01:36 [warn] WiFi module is idle power up + 00:01:38 [warn] Error: WiFi module reported: no known networks found power up + 00:01:38 [warn] WiFi module is idle power up + 00:01:40 [warn] Error: WiFi module reported: no known networks found power up + 00:01:40 [warn] WiFi module is idle power up + 00:01:43 [warn] Error: WiFi module reported: no known networks found power up + 00:01:43 [warn] WiFi module is idle power up + 00:01:45 [warn] Error: WiFi module reported: no known networks found power up + 00:01:45 [warn] WiFi module is idle power up + 00:01:47 [warn] Error: WiFi module reported: no known networks found power up + 00:01:47 [warn] WiFi module is idle power up + 00:01:49 [warn] Error: WiFi module reported: no known networks found power up + 00:01:49 [warn] WiFi module is idle power up + 00:01:51 [warn] Error: WiFi module reported: no known networks found power up + 00:01:51 [warn] WiFi module is idle power up + 00:01:54 [warn] Error: WiFi module reported: no known networks found power up + 00:01:54 [warn] WiFi module is idle power up + 00:01:56 [warn] Error: WiFi module reported: no known networks found power up + 00:01:56 [warn] WiFi module is idle power up + 00:01:58 [warn] Error: WiFi module reported: no known networks found power up + 00:01:58 [warn] WiFi module is idle power up + 00:02:00 [warn] Error: WiFi module reported: no known networks found power up + 00:02:00 [warn] WiFi module is idle power up + 00:02:02 [warn] Error: WiFi module reported: no known networks found power up + 00:02:02 [warn] WiFi module is idle power up + 00:02:05 [warn] Error: WiFi module reported: no known networks found power up + 00:02:05 [warn] WiFi module is idle power up + 00:02:07 [warn] Error: WiFi module reported: no known networks found power up + 00:02:07 [warn] WiFi module is idle power up + 00:02:09 [warn] Error: WiFi module reported: no known networks found power up + 00:02:09 [warn] WiFi module is idle power up + 00:02:11 [warn] Error: WiFi module reported: no known networks found power up + 00:02:11 [warn] WiFi module is idle power up + 00:02:15 [warn] WiFi module is connected to access point RV32-IOT2G, IP address 192.168.10.x power up + 00:03:04 [warn] Error: WiFi module reported: Lost connection, auto reconnecting power up + 00:03:04 [warn] Error: WiFi module reported: Auto reconnect succeeded power up + 00:00:03 [info] Event logging started at level debug power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-rc.1+ (2023-11-01 10:29:03) power up + 00:00:03 [info] Event logging stopped power up + 00:00:03 [info] Event logging started at level debug power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-rc.1+ (2023-11-01 10:29:03) power up + 00:00:03 [debug] Done! power up + 00:00:03 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running. power up + 00:00:04 [warn] WiFi module started power up + 00:00:06 [warn] Error: WiFi module reported: Failed to load credentials power up + 00:00:06 [warn] WiFi module is idle power up + 00:00:08 [warn] Error: WiFi module reported: Failed to load credentials power up + 00:00:08 [warn] WiFi module is idle power up + 00:00:10 [warn] Error: WiFi module reported: no known networks found power up + 00:00:10 [warn] WiFi module is idle power up + 00:00:13 [warn] Error: WiFi module reported: no known networks found power up + 00:00:13 [warn] WiFi module is idle power up + 00:00:15 [warn] Error: WiFi module reported: no known networks found power up + 00:00:15 [warn] WiFi module is idle power up + 00:00:17 [warn] Error: WiFi module reported: no known networks found power up + 00:00:17 [warn] WiFi module is idle power up + 00:00:19 [warn] Error: WiFi module reported: no known networks found power up + 00:00:19 [warn] WiFi module is idle power up + 00:00:21 [warn] Error: WiFi module reported: no known networks found power up + 00:00:21 [warn] WiFi module is idle power up + 00:00:24 [warn] Error: WiFi module reported: no known networks found power up + 00:00:24 [warn] WiFi module is idle power up + 00:00:26 [warn] Error: WiFi module reported: no known networks found power up + 00:00:26 [warn] WiFi module is idle power up + 00:00:28 [warn] Error: WiFi module reported: no known networks found power up + 00:00:28 [warn] WiFi module is idle power up + 00:00:30 [warn] Error: WiFi module reported: no known networks found power up + 00:00:30 [warn] WiFi module is idle power up + 00:00:32 [warn] Error: WiFi module reported: no known networks found power up + 00:00:32 [warn] WiFi module is idle power up + 00:00:35 [warn] Error: WiFi module reported: no known networks found power up + 00:00:35 [warn] WiFi module is idle power up + 00:00:37 [warn] Error: WiFi module reported: no known networks found power up + 00:00:37 [warn] WiFi module is idle power up + 00:00:39 [warn] Error: WiFi module reported: no known networks found power up + 00:00:39 [warn] WiFi module is idle power up + 00:00:41 [warn] Error: WiFi module reported: no known networks found power up + 00:00:41 [warn] WiFi module is idle power up + 00:00:43 [warn] Error: WiFi module reported: no known networks found power up + 00:00:43 [warn] WiFi module is idle power up + 00:00:46 [warn] Error: WiFi module reported: no known networks found power up + 00:00:46 [warn] WiFi module is idle power up + 00:00:48 [warn] Error: WiFi module reported: no known networks found power up + 00:00:48 [warn] WiFi module is idle power up + 00:00:50 [warn] Error: WiFi module reported: no known networks found power up + 00:00:50 [warn] WiFi module is idle power up + 00:00:52 [warn] Error: WiFi module reported: no known networks found power up + 00:00:52 [warn] WiFi module is idle power up + 00:00:55 [warn] Error: WiFi module reported: no known networks found power up + 00:00:55 [warn] WiFi module is idle power up + 00:00:57 [warn] Error: WiFi module reported: no known networks found power up + 00:00:57 [warn] WiFi module is idle power up + 00:00:59 [warn] Error: WiFi module reported: no known networks found power up + 00:00:59 [warn] WiFi module is idle power up + 00:01:01 [warn] Error: WiFi module reported: no known networks found power up + 00:01:01 [warn] WiFi module is idle power up + 00:01:03 [warn] Error: WiFi module reported: no known networks found power up + 00:01:03 [warn] WiFi module is idle power up + 00:01:06 [warn] Error: WiFi module reported: no known networks found power up + 00:01:06 [warn] WiFi module is idle power up + 00:01:08 [warn] Error: WiFi module reported: no known networks found power up + 00:01:08 [warn] WiFi module is idle power up + 00:01:10 [warn] Error: WiFi module reported: no known networks found power up + 00:01:10 [warn] WiFi module is idle power up + 00:01:12 [warn] Error: WiFi module reported: no known networks found power up + 00:01:12 [warn] WiFi module is idle power up + 00:01:15 [warn] Error: WiFi module reported: no known networks found power up + 00:01:15 [warn] WiFi module is idle power up + 00:01:17 [warn] Error: WiFi module reported: no known networks found power up + 00:01:17 [warn] WiFi module is idle power up + 00:01:19 [warn] Error: WiFi module reported: no known networks found power up + 00:01:19 [warn] WiFi module is idle power up + 00:01:21 [warn] Error: WiFi module reported: no known networks found power up + 00:01:21 [warn] WiFi module is idle power up + 00:01:24 [warn] Error: WiFi module reported: no known networks found power up + 00:01:24 [warn] WiFi module is idle power up + 00:01:26 [warn] Error: WiFi module reported: no known networks found power up + 00:01:26 [warn] WiFi module is idle power up + 00:01:28 [warn] Error: WiFi module reported: no known networks found power up + 00:01:28 [warn] WiFi module is idle power up + 00:01:30 [warn] Error: WiFi module reported: no known networks found power up + 00:01:30 [warn] WiFi module is idle power up + 00:01:32 [warn] Error: WiFi module reported: no known networks found power up + 00:01:32 [warn] WiFi module is idle power up + 00:01:35 [warn] Error: WiFi module reported: no known networks found power up + 00:01:35 [warn] WiFi module is idle power up + 00:01:37 [warn] Error: WiFi module reported: no known networks found power up + 00:01:37 [warn] WiFi module is idle power up + 00:01:39 [warn] Error: WiFi module reported: no known networks found power up + 00:01:39 [warn] WiFi module is idle power up + 00:01:41 [warn] Error: WiFi module reported: no known networks found power up + 00:01:41 [warn] WiFi module is idle power up + 00:01:44 [warn] Error: WiFi module reported: no known networks found power up + 00:01:44 [warn] WiFi module is idle power up + 00:01:46 [warn] Error: WiFi module reported: no known networks found power up + 00:01:46 [warn] WiFi module is idle power up + 00:01:48 [warn] Error: WiFi module reported: no known networks found power up + 00:01:48 [warn] WiFi module is idle power up + 00:01:50 [warn] Error: WiFi module reported: no known networks found power up + 00:01:50 [warn] WiFi module is idle power up + 00:01:53 [warn] Error: WiFi module reported: no known networks found power up + 00:01:53 [warn] WiFi module is idle power up + 00:01:55 [warn] Error: WiFi module reported: no known networks found power up + 00:01:55 [warn] WiFi module is idle power up + 00:01:57 [warn] Error: WiFi module reported: Failed to load credentials power up + 00:01:57 [warn] WiFi module is idle power up + 00:01:59 [warn] Error: WiFi module reported: no known networks found power up + 00:01:59 [warn] WiFi module is idle power up + 00:02:01 [warn] Error: WiFi module reported: no known networks found power up + 00:02:01 [warn] WiFi module is idle power up + 00:02:04 [warn] Error: WiFi module reported: no known networks found power up + 00:02:06 [warn] Error: WiFi module reported: no known networks found power up + 00:02:06 [warn] WiFi module is idle power up + 00:02:08 [warn] Error: WiFi module reported: no known networks found power up + 00:02:08 [warn] WiFi module is idle power up + 00:02:10 [warn] Error: WiFi module reported: no known networks found power up + 00:02:10 [warn] WiFi module is idle power up + 00:02:13 [warn] Error: WiFi module reported: no known networks found power up + 00:02:13 [warn] WiFi module is idle power up + 00:02:15 [warn] Error: WiFi module reported: Failed to load credentials power up + 00:02:15 [warn] WiFi module is idle power up + 00:02:18 [warn] WiFi module is connected to access point RV32-IOT2G, IP address 192.168.10.x power up + 00:02:48 [warn] Error: WiFi module reported: Lost connection, auto reconnecting power up + 00:02:49 [warn] Error: WiFi module reported: Auto reconnect succeeded power up + 69:32:47 [warn] HTTP client 192.168.10.xx login succeeded (session key 1481405628) 2023-11-10 15:27:24 [warn] Date and time set at power up + 69:32:47Continued on the next reply -
M122;
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.1+ (2023-11-01 10:29:03) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ Used output buffers: 22 of 40 (40 max) === RTOS === Static ram: 102812 Dynamic ram: 122036 of which 12 recycled Never used RAM 13700, free system stack 180 words Tasks: NETWORK(2,nWait,53.7%,213) HEAT(3,nWait,2.2%,327) Move(4,nWait,0.2%,344) CanReceiv(6,nWait,4.3%,772) CanSender(5,nWait,0.0%,336) CanClock(7,delaying,0.7%,341) TMC(4,nWait,61.6%,108) MAIN(1,running,111.9%,670) IDLE(0,ready,22.0%,29) AIN(4,delaying,71.9%,264), total 328.3% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 123:52:45 ago, cause: power up Last software reset at 2023-11-06 16:08, reason: User, Gcodes spinning, available RAM 11824, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 445965944, completed 445965943, timed out 0, errs 0 MCU temperature: min 24.4, current 36.2, max 36.6 Supply voltage: min 0.2, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/29, heap memory allocated/used/recyclable 2048/980/584, gc cycles 20101 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 9948, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 9948, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 9947, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 9947, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 9948, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-11-12 21:47:22 Cache data hit count 4294967295 Slowest loop: 11.70ms; fastest: 0.13ms === Storage === Free file entries: 18 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 7.0ms, write time 4.5ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, 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 1 is on, I-accum = 0.0 === GCodes === Movement locks held by null, null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is doing "G4 S1" in state(s) 0 0, running macro 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 0 Extruder 0 sensor: no filament === CAN === Messages queued 4013705, received 9142508, lost 0, errs 3539, boc 0 Longest wait 3ms for reply type 6053, peak Tx sync delay 11386, free buffers 26 (min 25), ts 2229830/2229826/0 Tx timeouts 0,0,3,0,0,0 last cancelled message type 30 dest 127 === Network === Slowest loop: 19.15ms; fastest: 0.00ms Responder states: MQTT(0) HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 2 of 8 === WiFi === Interface state: active Module is connected to access point Failed messages: pending 0, notrdy 0, noresp 0 Firmware version 2.1beta4 MAC address c4:5b:be:ce:91:93 Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 39508 WiFi IP address 192.168.10.x Signal strength -53dBm, channel 6, mode 802.11n, reconnections 1 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0Should be noted that on this crash it didn't fail to connect to the toolboard, so it wasn't any heater faults etc.
-
@Exerqtor please remind me: did this issue also occur when using firmware 3.4.x, or is it specific to 3.5.x?
I've created https://github.com/Duet3D/RepRapFirmware/issues/935 t track and summarise this, but please continue to post M122 reports in this thread.
open Regular crashes on Duet 3 Mini WiFi #935
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 -
@Exerqtor please install the firmware at https://www.dropbox.com/scl/fo/nta4k70rxl6n0bsv8q4q0/h?rlkey=1oq6j3jrvoxa6uaofyn9re3nn&dl=0 and post the M122 report when it next crashes. I have added some extra debug in the area where I think it is crashing.
-
@dc42 said in Reboots/crashes - RRF 3.5.0-rc1:
@Exerqtor please remind me: did this issue also occur when using firmware 3.4.x, or is it specific to 3.5.x?
IF it happened in 3.4.5 it must have been so Intermittent that i didn't catch it happening. If we put it that way.
@dc42 said in Reboots/crashes - RRF 3.5.0-rc1:
@Exerqtor please install the firmware at https://www.dropbox.com/scl/fo/nta4k70rxl6n0bsv8q4q0/h?rlkey=1oq6j3jrvoxa6uaofyn9re3nn&dl=0 and post the M122 report when it next crashes. I have added some extra debug in the area where I think it is crashing.
Okok i will do it later today
👌☺️ -
The printer has been sitting idle since i updated to the "special" firmware you compiled, and it's been running for about 24hr with one instance of DWC open but the PC not being used (used stood there ).
Now i've been sitting on the PC working for 10min, with the printer idle and in that time the printer has crashed. This time again it's not connecting to the 1LC after the crash and it's throwing a heater fault & 2000C.
debuglog:
2023-11-15 20:35:24 [warn] HTTP client 192.168.10.xx disconnected 2023-11-15 20:35:27 [warn] HTTP client 192.168.10.xx login succeeded (session key 55059692) 2023-11-15 20:35:31 [warn] HTTP client 192.168.10.xx disconnected 2023-11-15 20:35:36 [warn] HTTP client 192.168.10.xx login succeeded (session key 1424224561) power up + 00:00:03 [info] Event logging started at level debug power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-rc.1+ (2023-11-14 10:45:05) power up + 00:00:03 [info] Event logging stopped power up + 00:00:03 [info] Event logging started at level debug power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-rc.1+ (2023-11-14 10:45:05) power up + 00:00:03 [debug] Done! power up + 00:00:03 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running. power up + 00:00:04 [warn] Error: Heater 1 fault: failed to read sensor: notReady power up + 00:00:04 [info] M291: - Event notification - Heater 1 fault: failed to read sensor: notReady power up + 00:00:04 [debug] - Event notification - power up + 00:00:04 [debug] Heater 1 fault: failed to read sensor: notReady power up + 00:00:04 [warn] WiFi module started power up + 00:00:08 [warn] WiFi module is connected to access point RV32-IOT2G, IP address 192.168.10.x power up + 00:00:08 [warn] HTTP client 192.168.10.xx login succeeded (session key 740842430) 2023-11-15 20:37:48 [warn] Date and time set at power up + 00:00:08M122:
=== Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.1+ (2023-11-14 10:45:05) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: XNHXF-HR6KL-K65J0-409N2-K9W1Z-RV2MZ Used output buffers: 1 of 40 (30 max) === RTOS === Static ram: 102812 Dynamic ram: 123820 of which 0 recycled Never used RAM 11928, free system stack 188 words Tasks: NETWORK(1,ready,17.6%,209) HEAT(3,nWait,0.0%,352) Move(4,nWait,0.0%,358) CanReceiv(6,nWait,0.0%,797) CanSender(5,nWait,0.0%,336) CanClock(7,delaying,0.0%,350) TMC(4,nWait,0.7%,108) MAIN(1,running,80.6%,670) IDLE(0,ready,0.3%,29) AIN(4,delaying,0.8%,264), total 100.0% Owned mutexes: === Platform === Last reset 00:15:57 ago, cause: software Last software reset at 2023-11-15 20:37, reason: AssertionFailed, Gcodes spinning, available RAM 6020, slot 0 Software reset code 0x4123 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x20011fbc Task NETW Freestk 495 ok Stack: 000008fe 000af1c8 0002dd83 2002beb4 2002be01 000001a8 2002c0e0 20030b90 2002c0f8 2001e868 a5a5a5a5 a5a5a5a5 00000000 00000000 00000000 00000000 20030b9c 00000800 200358c0 2002c0e0 20018658 2002bf7d 20018658 2001e868 00030023 00000000 00000000 Error status: 0x00 Aux0 errors 0,0,0 MCU revision 3, ADC conversions started 958328, completed 958328, timed out 0, errs 0 MCU temperature: min 35.1, current 35.5, max 38.2 Supply voltage: min 22.7, current 24.1, max 26.3, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/33, heap memory allocated/used/recyclable 2048/1932/1496, gc cycles 44 Events: 1 queued, 1 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 118, reads 50392, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 2, read errors 0, write errors 1, ifcnt 118, reads 50392, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 81, reads 50391, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 79, reads 50391, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 80, reads 50392, writes 13, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2023-11-15 20:53:37 Cache data hit count 1623656227 Slowest loop: 12.73ms; fastest: 0.13ms === Storage === Free file entries: 18 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 6.5ms, write time 4.6ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, 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 doing "G4 S1" in state(s) 0 0, running macro 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 === in 0 notIn 0 Extruder 0 sensor: no filament === CAN === Messages queued 8631, received 19678, lost 0, errs 1, boc 0 Longest wait 2ms for reply type 6053, peak Tx sync delay 299, free buffers 26 (min 25), ts 4790/4789/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 9.16ms; 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.1beta4 MAC address c4:5b:be:ce:91:93 Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 43136 WiFi IP address 192.168.10.x Signal strength -52dBm, channel 6, mode 802.11n, reconnections 0 Clock register 00002001 Socket states: 0 0 0 0 0 0 0 0
