Printer keeps rebooting
-
RailCore II - Duet2Eth + Duex5 3.1.1 firmware.
Used the printer on Tuesday IIRC.
Have just left it powererd. Used my macro to turn the enclosure lights off and left it.
Came in next day, lights were on. My last line in my Config.g is to turn the enclosure lights on.
Did not really think about it and printed.
Halfway through a layer test it stopped and rebooted.
Had to go to work, again left it and got back in the evening and the lights were on.
No power cuts.I have ordered another ethernet module anyway.
Please could someone have a look at the log to see what could be causing the reboots.
TIA, Paul.
Here is the logfile.
13/12/2020, 07:25:20 m122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet Ethernet 1.02 or later + DueX5 Board ID: 08DGM-917DA-G4MS8-6JKDL-3SN6N-TVVB9 Used output buffers: 1 of 24 (11 max) === RTOS === Static ram: 27980 Dynamic ram: 94580 of which 84 recycled Exception stack ram used: 256 Never used ram: 8172 Tasks: NETWORK(ready,368) HEAT(blocked,1224) DUEX(suspended,160) MAIN(running,1816) IDLE(ready,80) Owned mutexes: === Platform === Last reset 08:16:45 ago, cause: software Last software reset at 2020-12-12 23:08, reason: Watchdog timeout, spinning module none, available RAM 7772 bytes (slot 2) Software reset code 0x40b1 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f014 BFAR 0xe000ed38 SP 0x2001ffbc Task NETW Stack: 20003cdc 0040f548 2101001f 20018200 20009178 20003108 a5a5a5a5 a5a5a5a5 ffffffed 00000000 00f00000 Error status: 0 MCU temperature: min 17.3, current 18.0, max 19.1 Supply voltage: min 24.0, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: standstill, SG min/max not available Driver 1: standstill, SG min/max not available Driver 2: standstill, SG min/max not available Driver 3: standstill, SG min/max not available Driver 4: standstill, SG min/max not available Driver 5: standstill, SG min/max not available Driver 6: standstill, SG min/max not available Driver 7: standstill, SG min/max not available Driver 8: standstill, SG min/max not available Driver 9: standstill, SG min/max not available Date/time: 2020-12-13 07:25:15 Cache data hit count 4294967295 Slowest loop: 12.32ms; fastest: 0.13ms 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 7.7ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 Heater 1 is on, I-accum = 0.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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 14.65ms; fastest: 0.02ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 Interface state active, link 100Mbps full duplex === DueX === Read count 1, 0.00 reads/min PRINTER WAS NOT BEING USED SO DO NOT UNDERSTAND WHY IT REPORTED AN OVERTEMP @ 10:43 ON 23/23/3030 12/12/2020, 23:08:44 Connection established 12/12/2020, 23:08:41 Connection interrupted, attempting to reconnect... HTTP request timed out 12/12/2020, 18:09:57 Connection established 12/12/2020, 18:09:38 Connection interrupted, attempting to reconnect... HTTP request timed out 12/12/2020, 15:09:06 Connection established 12/12/2020, 15:09:05 Connection interrupted, attempting to reconnect... HTTP request timed out 12/12/2020, 13:55:20 Connection established 12/12/2020, 13:55:20 Connection interrupted, attempting to reconnect... HTTP request timed out 12/12/2020, 10:43:00 Error: over temperature shutdown reported by driver(s) 3 12/12/2020, 10:34:09 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet Ethernet 1.02 or later + DueX5 Board ID: 08DGM-917DA-G4MS8-6JKDL-3SN6N-TVVB9 Used output buffers: 1 of 24 (22 max) === RTOS === Static ram: 27980 Dynamic ram: 94580 of which 84 recycled Exception stack ram used: 256 Never used ram: 8172 Tasks: NETWORK(ready,368) HEAT(blocked,1224) DUEX(suspended,160) MAIN(running,1848) IDLE(ready,80) Owned mutexes: === Platform === Last reset 00:57:20 ago, cause: watchdog Last software reset at 2020-12-12 09:33, reason: Assertion failed, spinning module none, available RAM 7624 bytes (slot 2) Software reset code 0x4131 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f81f BFAR 0xe000ed38 SP 0x2001ffdc Task MAIN Stack: 000000e4 00477b38 00454cf5 00f00000 00000000 c0000000 00454f5d 00454cc0 61030000 ffffffff ffffffff Error status: 0 MCU temperature: min 21.9, current 22.2, max 25.1 Supply voltage: min 24.1, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: standstill, SG min/max not available Driver 1: standstill, SG min/max not available Driver 2: standstill, SG min/max not available Driver 3: standstill, SG min/max not available Driver 4: standstill, SG min/max not available Driver 5: standstill, SG min/max not available Driver 6: standstill, SG min/max not available Driver 7: standstill, SG min/max not available Driver 8: standstill, SG min/max not available Driver 9: standstill, SG min/max not available Date/time: 2020-12-12 10:34:06 Cache data hit count 4294967295 Slowest loop: 11.07ms; fastest: 0.10ms 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 4.3ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 Heater 1 is on, I-accum = 0.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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 17.08ms; fastest: 0.03ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 2 of 8 Interface state active, link 100Mbps full duplex === DueX === Read count 0, 0.00 reads/min 12/12/2020, 09:44:09 m122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet Ethernet 1.02 or later + DueX5 Board ID: 08DGM-917DA-G4MS8-6JKDL-3SN6N-TVVB9 Used output buffers: 3 of 24 (11 max) === RTOS === Static ram: 27980 Dynamic ram: 94580 of which 84 recycled Exception stack ram used: 248 Never used ram: 8180 Tasks: NETWORK(ready,368) HEAT(blocked,1224) DUEX(suspended,160) MAIN(running,1848) IDLE(ready,80) Owned mutexes: === Platform === Last reset 00:07:21 ago, cause: watchdog Last software reset at 2020-12-12 09:33, reason: Assertion failed, spinning module none, available RAM 7624 bytes (slot 2) Software reset code 0x4131 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f81f BFAR 0xe000ed38 SP 0x2001ffdc Task MAIN Stack: 000000e4 00477b38 00454cf5 00f00000 00000000 c0000000 00454f5d 00454cc0 61030000 ffffffff ffffffff Error status: 0 MCU temperature: min 22.4, current 23.5, max 24.0 Supply voltage: min 24.1, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: standstill, SG min/max not available Driver 1: standstill, SG min/max not available Driver 2: standstill, SG min/max not available Driver 3: standstill, SG min/max not available Driver 4: standstill, SG min/max not available Driver 5: standstill, SG min/max not available Driver 6: standstill, SG min/max not available Driver 7: standstill, SG min/max not available Driver 8: standstill, SG min/max not available Driver 9: standstill, SG min/max not available Date/time: 2020-12-12 09:44:07 Cache data hit count 860344785 Slowest loop: 12.33ms; fastest: 0.13ms 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 3.8ms, write time 0.0ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === AuxDDARing === Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 Heater 1 is on, I-accum = 0.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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 14.94ms; fastest: 0.02ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 Interface state active, link 100Mbps full duplex === DueX === Read count 1, 0.14 reads/min 12/12/2020, 09:42:00 m121 Error: Pop(): stack underflow``` -
The nature of the M122 reports suggests a semi-random hardware issue. Here are some possible causes:
- Noise on the ground line between the Duet and DueX5. Please confirm that you have a short thick ground wire between the Duet and DueX5 as described at https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_Wiring. Check that the VIN terminal block screws are still tight.
- Electrostatic discharge. This can be caused by static charge building up on the stepper motors. The remedy is to ground the bodies of the stepper motors. For stepper motors bolted to a metal frame, it is sufficient to ground the frame and then check that there is continuity between the stepper motor bodies and ground.
HTH David
-
Morning David, thanks for replying.
Yes, still have a thick ground wire between the 2 boards,Screws are tight, have 1 grounding wire to a stepper motor on the RC, but will test the ground at various points.
P.
