Printer stopping mid print

[pilot375]

Short-duration prints (up to about 6 hours seem to go fine; however, longer prints stop mid-print. Print head stops heaters off right in the middle of the print.

Simplify 3d is the slicer

Any thoughts?

2/9/2024, 7:29:53 AM m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.5.0-rc.2 (2023-12-14 10:32:22) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-956BA-NA3TN-6JKD8-3S46Q-1AAGS
Used output buffers: 1 of 40 (18 max)
=== RTOS ===
Static ram: 154844
Dynamic ram: 87976 of which 0 recycled
Never used RAM 99932, free system stack 132 words
Tasks: SBC(2,ready,14.6%,384) HEAT(3,nWait,0.5%,324) Move(4,nWait,19.7%,217) CanReceiv(6,nWait,0.0%,942) CanSender(5,nWait,0.0%,334) CanClock(7,delaying,0.2%,342) TMC(4,nWait,124.5%,61) MAIN(2,running,84.1%,103) IDLE(0,ready,0.4%,30), total 244.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 17:00:43 ago, cause: reset button
Last software reset details not available
Error status: 0x00
MCU temperature: min 40.5, current 42.1, max 45.2
Supply voltage: min 23.5, current 23.9, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.9, current 12.0, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/468/468, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 568, reads 26981, writes 56 timeouts 0
Driver 1: standstill, SG min 0, mspos 856, reads 26981, writes 56 timeouts 0
Driver 2: standstill, SG min 0, mspos 872, reads 26981, writes 56 timeouts 0
Driver 3: standstill, SG min 0, mspos 424, reads 26982, writes 56 timeouts 0
Driver 4: standstill, SG min 0, mspos 840, reads 26998, writes 40 timeouts 0
Driver 5: standstill, SG min n/a, mspos 8, reads 27017, writes 21 timeouts 0
Date/time: 2024-02-09 07:29:51
Slowest loop: 411.47ms; fastest: 0.05ms
=== Storage ===
Free file entries: 20
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 16, maxWait 244066ms, bed compensation in use: mesh, height map offset 0.000, max steps late 1, 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 472816, completed 472816, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 5], CDDA state -1
=== DDARing 1 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null, null
HTTP* is doing "M122" 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2* is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000000
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 551184, received 0, lost 0, errs 290853814, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 306216/0/0
Tx timeouts 0,0,306215,0,0,244967 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 25326/2417
SPI underruns 0, overruns 0
State: 5, disconnects: 2, timeouts: 2 total, 2 by SBC, IAP RAM available 0x258a4
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server version 3.5.0-rc.2 (2023-12-18 12:39:35)
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 44.50, max time between full transfers: 12949.4ms, max pin wait times: 136.0ms/14.9ms
Codes per second: 30.68
Maximum length of RX/TX data transfers: 6592/2760

Thanks!

[pilot375]

Oddly enough it says print 100% complete but it is only about 1/2 complete!

[dc42]

@pilot375 said in Printer stopping mid print:

Last reset 17:00:43 ago, cause: reset button

Does this reset correspond to when you started the printer, or did you start the print more than 17 hours before running M122?

[pilot375]

@dc42 The reset more than 17 hours prior was before starting the print. I generally always do a restart, then bed level etc before a large print.