Random Resets - Gcode Spin Loop
-
Lately when printing from my external SD card (in a 12864 display) the printer resets at random times during the print. It seems to stop in it's current position, and stay there while it resets itself. This shuts off my power supply relay, shutting down the machine. All is good when I put power to the Duet again.
Here's a M122 dump just after restarting it, and the SD card logging shows nothing relevant. It seems to only have this issue when printing from the external SD card.
=== Diagnostics === RepRapFirmware for Duet 2 Maestro version 3.01-RC3 running on Duet Maestro 1.0 Board ID: 08DJM-956DU-LLMS4-7JKD2-3S07J-1VPQJ Used output buffers: 7 of 24 (7 max) === RTOS === Static ram: 21876 Dynamic ram: 95172 of which 44 recycled Exception stack ram used: 368 Never used ram: 13612 Tasks: NETWORK(ready,856) HEAT(blocked,1340) MAIN(running,1964) IDLE(ready,84) Owned mutexes: === Platform === Last reset 00:12:09 ago, cause: power up Last software reset at 2020-05-19 10:48, reason: Stuck in spin loop, spinning module GCodes, available RAM 12596 bytes (slot 3) Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f80f BFAR 0xe000ed38 SP 0x20001ffc Task 0x5754454e Stack: 00454477 00457e36 21000000 00000000 00000004 0045802d 200049b0 00000001 00000000 20001204 00000004 Error status: 0 Free file entries: 9 SD card 0 detected, interface speed: 15.0MBytes/sec SD card longest block write time: 4.6ms, max retries 0 MCU temperature: min 14.5, current 23.5, max 23.9 Supply voltage: min 0.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: standstill, read errors 0, write errors 0, ifcount 9, reads 29130, timeouts 0 Driver 1: standstill, read errors 0, write errors 0, ifcount 9, reads 29130, timeouts 0 Driver 2: standstill, read errors 0, write errors 0, ifcount 9, reads 29130, timeouts 0 Driver 3: standstill, read errors 0, write errors 0, ifcount 7, reads 29132, timeouts 0 Driver 4: standstill, read errors 0, write errors 0, ifcount 6, reads 29133, timeouts 0 Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 29138 Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 29138 Date/time: 2020-05-19 13:16:15 Slowest loop: 202.61ms; fastest: 0.13ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 167, MaxWait: 707543ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 12, completed moves: 12, 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, chamberHeaters = -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 serial 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. === Network === Slowest loop: 220.04ms; fastest: 0.02ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 Interface state 5, link 100Mbps full duplexIt's not a big deal, as I don't print from the external SD card often, but it did waste about 1-1/2 days of print time (and filament
) and I thought you might be interested in a bug report.I know the firmware isn't the latest, but it's been working well for me.
Thanks!
-
@JadonM said in Random Resets - Gcode Spin Loop:
I know the firmware isn't the latest, but it's been working well for me.
Except for the random crashes you mean.
Please update to the 3.1.1 release that's out now. Far too much has changed with fixes and such to be able to support such an old release.
-
@Phaedrux said in Random Resets - Gcode Spin Loop:
Except for the random crashes you mean.
Yeah!
I'll upgrade. I thought you might be interested in the bug report, even though it is an older version.
