Paused a print, Cannot resume. Duet Crashed
-
Seems like my day for faults!
Kicked a print off this evening, made sure first layers went down well. 2 ObjectsPopped back after 2 hours and one had come unstuck.
Hit the pause buuton on the Panel Due and it paused.Noticed on the Panel Due it did not come back with 'print paused' OR give me the option to resume the print.
Thought I could use M496 to cancel the failed part.Opened DWC on a computer.
This is the M122m122 === 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 (14 max) === RTOS === Static ram: 27980 Dynamic ram: 94860 of which 52 recycled Exception stack ram used: 552 Never used ram: 7628 Tasks: NETWORK(ready,324) HEAT(blocked,1224) DUEX(suspended,160) MAIN(running,1640) IDLE(ready,80) Owned mutexes: === Platform === Last reset 02:24:14 ago, cause: software Last software reset at 2020-06-15 21:45, reason: User, spinning module GCodes, available RAM 8124 bytes (slot 0) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN Error status: 8 MCU temperature: min 34.7, current 38.4, max 39.7 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 0/1023 Driver 1: standstill, SG min/max 0/1023 Driver 2: standstill, SG min/max not available Driver 3: standstill, SG min/max 0/1023 Driver 4: standstill, SG min/max not available Driver 5: standstill, SG min/max 0/1023 Driver 6: standstill, SG min/max 0/1023 Driver 7: standstill, SG min/max 0/1023 Driver 8: standstill, SG min/max not available Driver 9: standstill, SG min/max not available Date/time: 2020-06-16 00:09:52 Cache data hit count 4294967295 Slowest loop: 141.16ms; fastest: 0.14ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 9 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 3.0ms, write time 11.8ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 107, MaxWait: 228721ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 177637, completed moves: 177637, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: 0 === 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 0 is on, I-accum = 0.1 Heater 1 is on, I-accum = 0.5 === GCodes === Segments left: 0 Movement lock held by Aux HTTP is doing "M24" 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) 20 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: 110.89ms; 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.01 reads/min 16/06/2020, 00:09:52 M24 === 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 (14 max) === RTOS === Static ram: 27980 Dynamic ram: 94860 of which 52 recycled Exception stack ram used: 552 Never used ram: 7628 Tasks: NETWORK(ready,324) HEAT(blocked,1224) DUEX(suspended,160) MAIN(running,1640) IDLE(ready,80) Owned mutexes: === Platform === Last reset 02:24:14 ago, cause: software Last software reset at 2020-06-15 21:45, reason: User, spinning module GCodes, available RAM 8124 bytes (slot 0) Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN Error status: 8 MCU temperature: min 34.7, current 38.4, max 39.7 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 0/1023 Driver 1: standstill, SG min/max 0/1023 Driver 2: standstill, SG min/max not available Driver 3: standstill, SG min/max 0/1023 Driver 4: standstill, SG min/max not available Driver 5: standstill, SG min/max 0/1023 Driver 6: standstill, SG min/max 0/1023 Driver 7: standstill, SG min/max 0/1023 Driver 8: standstill, SG min/max not available Driver 9: standstill, SG min/max not available Date/time: 2020-06-16 00:09:52 Cache data hit count 4294967295 Slowest loop: 141.16ms; fastest: 0.14ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 9 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 3.0ms, write time 11.8ms, max retries 0 === Move === Hiccups: 0(0), FreeDm: 169, MinFreeDm: 107, MaxWait: 228721ms Bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves: 177637, completed moves: 177637, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: 0 === 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 0 is on, I-accum = 0.1 Heater 1 is on, I-accum = 0.5 === GCodes === Segments left: 0 Movement lock held by Aux HTTP is doing "M24" 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) 20 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: 110.89ms; 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.01 reads/min
Looked at Job Status, had the Pause only available.
Clicked and then no more functions possible from DWCPressed 'Stop' on Panel Due and board rebooted.
Not sure what is going on here.
Hope someone can shed light on it.
Regards
Paul -
Not sure what it could be but if it does happen again please share another M122 report for @dc42 to see.