My printer has been running great, and then yesterday, the printer canceled the print, and then it went into emergency stop (it was printing for about 2hr. I tried simulating the GCODE and that was fine, so i printed the file and now after 15hr it stoped again. Since I'm running 3.5.3, I am going to update it to 3.5.4, although it doesn't appear that there is anything in the changelog about this. I am wondering why this would happen and how to fix it.
Since it halted after it did so the second time, i went over and looked at the console and then ran an M122 the console read this:
Canceled Printing file "file name here", print time was 15hr 36m
Emergency Stop! Reset the controller to continue
Info: status changed from Printing to Halted
And M122 red this
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.3 (2024-09-18 11:25:32) running on Duet WiFi 1.02 or later + DueX5v0.11
Board ID: 0JD2M-9F8TA-GJ4TJ-6J1FJ-3SJ6L-KNSL5
Used output buffers: 3 of 26 (26 max)
=== RTOS ===
Static ram: 23376
Dynamic ram: 75532 of which 12 recycled
Never used RAM 10672, free system stack 104 words
Tasks: NETWORK(2,nWait 6,16.6%,195) HEAT(3,suspended,0.1%,307) DUEX(5,nWait 5,0.0%,17) MAIN(1,running,80.5%,615) IDLE(0,ready,0.1%,29), total 97.2%
Owned mutexes:
=== Platform ===
Last reset 16:30:45 ago, cause: software
Last software reset at 2025-02-21 23:06, reason: User, Gcodes spinning, available RAM 7352, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x0c
Aux0 errors 0,0,0
MCU temperature: min 38.3, current 44.7, max 46.6
Supply voltage: min 23.5, current 24.0, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/14, heap memory allocated/used/recyclable 2048/356/136, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min 0
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min 0
Driver 6: standstill, SG min 0
Driver 7: standstill, SG min 0
Driver 8: standstill, SG min 0
Driver 9: standstill, SG min 0
Driver 10:
Driver 11:
Date/time: 2025-02-22 15:37:14
Cache data hit count 4294967295
Slowest loop: 341.02ms; fastest: 0.14ms
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 14.1ms, write time 30.8ms, max retries 0
=== Move ===
DMs created 83, segments created 43, maxWait 519354ms, bed compensation in use: mesh, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin -0.00, ebfmax 1.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 448761, completed 448746, hiccups 0, stepErrors 0, LaErrors 0, Underruns [7, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks 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
Q0 segments left 0
Code queue 0 is empty
=== Filament sensors ===
check 334755368 clear 14601704
Extruder 0 sensor: ok
Extruder 1 sensor: ok
=== DueX ===
Read count 35, 0.04 reads/min
=== Network ===
Slowest loop: 220.57ms; fastest: 0.00ms
Responder states: 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.1.0
MAC address e8:68:e7:e1:4c:35
Module reset reason: Power up, Vcc 3.43, flash size 2097152, free heap 41372
WiFi IP address 192.168.0.237
Signal strength -30dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
Now, looking at the timing of it all. The software reset was 7min's before the printer halted; it says user; however, I didn't do anything and was not at the printer.
I would love any suggestion or help. I would love to know what happened so I can prevent this in the future.
