Duet 2 Wifi reboot while printing
-
Hello all,
Recently set up a Modix Big-60 IDEX machine that is run off a Duet 2. This problem has plagued this machine since we started running it. Randomly in the middle of prints (never in the same spot) the machine will stop and then fully reboot.
I have placed the M122 output below and attached the config.g file, but this machine is stock and running firmware 3.4.6.
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.6 (2023-07-21 14:08:28) running on Duet WiFi 1.02 or later + DueX5v0.11 Board ID: 0JD0M-9P6M2-NW4SN-6JKFG-3SJ6L-TAU3K Used output buffers: 1 of 26 (26 max) === RTOS === Static ram: 23896 Dynamic ram: 77276 of which 0 recycled Never used RAM 8052, free system stack 184 words Tasks: NETWORK(notifyWait,13.9%,237) HEAT(notifyWait,0.0%,317) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,82.9%,438) IDLE(ready,3.2%,30), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:00:24 ago, cause: software Last software reset at 2023-11-07 10:55, reason: StuckInSpinLoop, Platform spinning, available RAM 7548, slot 2 Software reset code 0x4080 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200027b0 Task NETW Freestk 4294966998 ok Stack: 20008aa4 00000001 00000000 00000a61 00000001 0040b3e3 0040b44a 210d0000 0040b3d7 3331bb4c 40000000 b5ddea01 388ab355 bb360b61 3e2aaaab 3f800000 20004c64 00000000 a5a5a5a5 d3acb671 a5a5a5a5 a5a5a5a5 0040c903 20004c64 00000001 10000000 20004c64 Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 23.1, current 23.8, max 23.9 Supply voltage: min 24.0, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/14, heap memory allocated/used/recyclable 2048/212/8, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: standstill, SG min n/a Driver 6: standstill, SG min n/a Driver 7: standstill, SG min n/a Driver 8: standstill, SG min n/a Driver 9: standstill, SG min n/a Driver 10: Driver 11: Date/time: 2023-11-07 10:56:20 Cache data hit count 913480765 Slowest loop: 12.06ms; fastest: 0.20ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 0.5ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === 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 === Segments left: 0 Movement lock held by 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === Filament sensors === Extruder 0 sensor: no data received Extruder 1 sensor: no data received === DueX === Read count 1, 2.42 reads/min === Network === Slowest loop: 12.47ms; fastest: 0.00ms Responder states: 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, notready 0, noresp 0 WiFi firmware version 1.27 WiFi MAC address c8:c9:a3:40:09:5d WiFi Vcc 3.36, reset reason Power up WiFi flash size 2097152, free heap 25952 WiFi IP address 192.168.1.203 WiFi signal strength -64dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
is that m122 immediately after it's reset itself?
Have you been in contact with Modix support?
-
@Phaedrux, yes that is after the reset. I did also contact Modix, but they are at FORMNEXT, so their support is not as responsive as usual.
-
Well it just happened again after running all night here is the M122
11/8/2023, 6:58:27 AM: M122: === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.6 (2023-07-21 14:08:28) running on Duet WiFi 1.02 or later + DueX5v0.11 Board ID: 0JD0M-9P6M2-NW4SN-6JKFG-3SJ6L-TAU3K Used output buffers: 1 of 26 (26 max) === RTOS === Static ram: 23896 Dynamic ram: 77276 of which 0 recycled Never used RAM 8052, free system stack 184 words Tasks: NETWORK(ready,15.3%,237) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,84.6%,436) IDLE(ready,0.0%,30), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:01:37 ago, cause: software Last software reset at 2023-11-08 06:56, reason: StuckInSpinLoop, GCodes spinning, available RAM 7212, slot 0 Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x20002570 Task NETW Freestk 4294966854 ok Stack: 00000001 200038d0 20000154 e000e000 00000004 0045e8c3 0045d106 6103f000 00000001 e000e000 0045e8c3 200099d0 00000001 3f800000 20008e00 200099d0 00000000 20009bb0 0043f3cf 0000000f 00000001 00000001 200099d0 20000154 00000000 200026b4 20008edc Error status: 0x04 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 21.0, current 21.1, max 22.2 Supply voltage: min 24.1, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/14, heap memory allocated/used/recyclable 2048/212/8, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: standstill, SG min n/a Driver 6: standstill, SG min n/a Driver 7: standstill, SG min n/a Driver 8: standstill, SG min n/a Driver 9: standstill, SG min n/a Driver 10: Driver 11: Date/time: 2023-11-08 06:58:26 Cache data hit count 3538706965 Slowest loop: 7.58ms; fastest: 0.20ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 0.4ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === 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 === Segments left: 0 Movement lock held by 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === Filament sensors === Extruder 0 sensor: no data received Extruder 1 sensor: no data received === DueX === Read count 0, 0.00 reads/min === Network === Slowest loop: 101.78ms; fastest: 0.07ms Responder states: 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, notready 0, noresp 2 WiFi firmware version 1.27 WiFi MAC address c8:c9:a3:40:09:5d WiFi Vcc 3.36, reset reason Power up WiFi flash size 2097152, free heap 25536 WiFi IP address 192.168.1.203 WiFi signal strength -59dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
So far it has now happened 4 more times today, sadly this part is so close to being done I cannot try any different G-Code, but each time I run the M122 after the reboot it has the StuckInSpinLoop as the reason for the reset with 0x4083 as the reset code. I reached out to Modix and was asked to unplug the E-Stops and the crash detection switch, which I have done, but I am still getting the stops. I will try another SD card tomorrow as I don't have one on me today. Short of that I am not sure how to go forward with this one.
The latest M122 for good measure:
11/8/2023, 1:40:42 PM M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.6 (2023-07-21 14:08:28) running on Duet WiFi 1.02 or later + DueX5v0.11 Board ID: 0JD0M-9P6M2-NW4SN-6JKFG-3SJ6L-TAU3K Used output buffers: 6 of 26 (22 max) === RTOS === Static ram: 23896 Dynamic ram: 77276 of which 0 recycled Never used RAM 8052, free system stack 174 words Tasks: NETWORK(notifyWait,11.8%,237) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,87.4%,436) IDLE(ready,0.8%,30), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:01:45 ago, cause: software Last software reset at 2023-11-08 13:38, reason: StuckInSpinLoop, GCodes spinning, available RAM 7596, slot 2 Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x20002690 Task NETW Freestk 4294966926 ok Stack: 00000001 00000001 20000154 00000000 00000001 0045d6ad 0045d7a6 210d0000 0045d7a7 00000001 20002714 20009de8 0045b07d 00000000 0043ecf1 00000001 20009dec 0045d101 20002724 00000101 610d0c00 00000000 45091000 41bbc1a6 3edb9b38 3331bb4c 40000000 Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 22.0, current 22.5, max 23.4 Supply voltage: min 24.1, current 24.2, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/14, heap memory allocated/used/recyclable 2048/212/8, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: standstill, SG min n/a Driver 6: standstill, SG min n/a Driver 7: standstill, SG min n/a Driver 8: standstill, SG min n/a Driver 9: standstill, SG min n/a Driver 10: Driver 11: Date/time: 2023-11-08 13:40:39 Cache data hit count 3757630694 Slowest loop: 14.92ms; fastest: 0.20ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 0.6ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === 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 === Segments left: 0 Movement lock held by 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === Filament sensors === Extruder 0 sensor: no data received Extruder 1 sensor: no data received === DueX === Read count 1, 0.57 reads/min === Network === Slowest loop: 13.58ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(1) 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, notready 0, noresp 0 WiFi firmware version 1.27 WiFi MAC address c8:c9:a3:40:09:5d WiFi Vcc 3.36, reset reason Power up WiFi flash size 2097152, free heap 25424 WiFi IP address 192.168.1.203 WiFi signal strength -58dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 2 0 0 0 0 0 0 -
@bieringm Did changing the SD card resolve the problems?
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@droftarts sadly no.
-
-
@bieringm @dc42 has had a look at the M122 reports. He says:
The stack is inconsistent because the network task was running at the time but SP is on the MAIN task stack pointer, hence the network free stack report is incorrect. This is probably just a data recording error. I'll look at it. I don't know what is causing the stuck-in-spin-loop errors, we don't often see those.
Yes, it's just a data logging thing. My best guess is that the fault is with the network interface. They could try reinstalling the wifi firmware. If that doesn't work then I suggest replace the Duet.
So first try reinstalling the WiFi firmware that comes with RRF 3.4.6; download a fresh copy of 'Duet2and3Firmware-3.4.6.zip' from https://github.com/Duet3D/RepRapFirmware/releases/tag/3.4.6, extract the zip file, then upload "DuetWiFiServer.bin" to the Duet via DWC and let it install the firmware.
If that doesn't help, could you then try updating the WiFi firmware to the latest version that is in the 3.5.0 release candidate; download the "DuetWiFiServer.bin" from https://github.com/Duet3D/RepRapFirmware/releases/tag/3.5.0-rc.1 and upload that to the Duet. Note that if you do this, you will have to connect to the Duet via USB and put in your WiFi details and password, as it overwrites the old settings. Follow the instructions here to do that: https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet#h-2-connect-your-duet-via-usb
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@droftarts I will give that a shot and see what happens.
Thanks for the help Ian!
-
@droftarts I just had another reset running after reinstalling 3.4.6 wifi server firmware. I just installed 3.5.0RC1 and will see how the preforms.
-
@bieringm Did you install the board firmware, or just the WiFi firmware, of 3.5.0-rc1? It's the Wifi firmware that we want to test on your board.
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@droftarts I just installed the wifi server firmware.
-
@bieringm okay, let’s see if that helps.
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@droftarts, so the change works, but that is only when I can get the printer to boot correctly. I have been struggling more as of recent where the "wifi module disabled - start timed out" and whenever I try to make a change to my wireless settings I get "Error: Failed to reset the Wifi module to factory settings: another SPI transfer is pending".
-
I think we should replace the board under warranty. The wifi module seems to be having issues.
Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
