Tool failed during print

oliof

@jumpedwithbothfeet no need to do a factory reset, the configuration is applied from the main board after bootup. So just reboot. Just make sure the board really is up to date running M115 B121 after running the update procedure.

You can try to see if you can reproduce the issue running a simulation of a print after updating everything to 3.5.1.

jumpedwithbothfeet

@oliof thanks, I have updated to 3.5.1 and confirmed the board is also up to date, I even updated the boot loader from 2.3 to 2.8, also cleaned out any Neo pixel reference from my config and am now running a print (2hr) and all is well so far, but again this has happened before and I thought it was the thermistor playing up.

@dc42 is there anything else that will cause it to use its memory up?

#I was running the failed print at 120% speed factor would that cause an issue?

dc42

@jumpedwithbothfeet please run M122 B121 after the print has been running for some time, or after it has finished, to see how much memory it had left after printing and whether there was anything else unusual..

jumpedwithbothfeet

@dc42 Print has been running over an hour and is currently still printing without issue with about 40 minutes left I guesstimate!

M122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.5.1 (2024-04-19 14:42:41)
Bootloader ID: SAMC21 bootloader version 2.8 (2023-07-25)
All averaging filters OK
Never used RAM 3000, free system stack 71 words
Tasks: Move(3,nWait 7,0.4%,85) HEAT(2,nWait 6,0.4%,91) CanAsync(5,nWait 4,0.0%,49) CanRecv(3,nWait 1,0.1%,71) CanClock(5,nWait 1,0.0%,59) ACCEL(3,nWait 6,0.0%,53) TMC(2,nWait 6,3.6%,53) MAIN(1,running,90.7%,315) IDLE(0,ready,0.0%,27) AIN(2,delaying,4.8%,112), total 100.0%
Owned mutexes:
Last reset 02:16:14 ago, cause: software
Last software reset at 2024-04-21 11:59, reason: OutOfMemory, available RAM 0, slot 0
Software reset code 0x01c0 ICSR 0x00000000 SP 0x20004c68 Task Move Freestk 115 ok
Stack: 20004ee0 000063e3 20004f40 20005fa8 20004f40 0000a51d 20004ccc 00008faf c5784ca0 2e89a8bb 2e89a8bb 47a79800 be3335d3 ce2ae763 41661135 00014f30 00000001 0001f46a 200026cc 20005fa8 200076b0 000492ca 20004ccc 00009629 000007d0 3e5c209d 3f4c1414
Driver 0: pos 0, 860.0 steps/mm, ok, SG min 0, read errors 1, write errors 0, ifcnt 49, reads 43947, writes 0, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 3022477
Moves scheduled 94598, completed 94596, in progress 1, hiccups 240, segs 47, step errors 0, maxLate 1 maxPrep 757, maxOverdue 98, maxInc 64, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 1.00
Peak sync jitter 6/10, peak Rx sync delay 261, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 24.1, current 24.3, max 24.6
MCU temperature: min 37.5C, current 87.2C, max 87.4C
Last sensors broadcast 0x00000002 found 1 177 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 46577, send timeouts 0, received 54900, lost 0, errs 0, boc 0, free buffers 18, min 17, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 399, adv 36241/74663
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 0, contentions 0, other errors 0

is that MCU temp alittle to much?!!

jumpedwithbothfeet

@dc42 Print finished M122 results

M122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.5.1 (2024-04-19 14:42:41)
Bootloader ID: SAMC21 bootloader version 2.8 (2023-07-25)
All averaging filters OK
Never used RAM 3000, free system stack 71 words
Tasks: Move(3,nWait 7,0.7%,85) HEAT(2,nWait 6,0.4%,91) CanAsync(5,nWait 4,0.0%,49) CanRecv(3,nWait 1,0.2%,71) CanClock(5,nWait 1,0.0%,59) ACCEL(3,nWait 6,0.0%,53) TMC(2,nWait 6,3.6%,53) MAIN(1,running,90.3%,315) IDLE(0,ready,0.0%,27) AIN(2,delaying,4.9%,112), total 100.0%
Owned mutexes:
Last reset 02:47:04 ago, cause: software
Last software reset at 2024-04-21 11:59, reason: OutOfMemory, available RAM 0, slot 0
Software reset code 0x01c0 ICSR 0x00000000 SP 0x20004c68 Task Move Freestk 115 ok
Stack: 20004ee0 000063e3 20004f40 20005fa8 20004f40 0000a51d 20004ccc 00008faf c5784ca0 2e89a8bb 2e89a8bb 47a79800 be3335d3 ce2ae763 41661135 00014f30 00000001 0001f46a 200026cc 20005fa8 200076b0 000492ca 20004ccc 00009629 000007d0 3e5c209d 3f4c1414
Driver 0: pos 0, 860.0 steps/mm, standstill, SG min 0, read errors 1, write errors 0, ifcnt 49, reads 39052, writes 0, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x72, steps req 0 done 1524175
Moves scheduled 140397, completed 140397, in progress 0, hiccups 255, segs 47, step errors 0, maxLate 0 maxPrep 706, maxOverdue 79, maxInc 64, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 1.00
Peak sync jitter 6/10, peak Rx sync delay 228, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 24.2, current 24.5, max 24.6
MCU temperature: min 37.5C, current 86.9C, max 87.4C
Last sensors broadcast 0x00000002 found 1 171 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 17411, send timeouts 0, received 35298, lost 0, errs 0, boc 0, free buffers 18, min 18, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 414, adv 36289/74656
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 0, contentions 0, other errors 0

Phaedrux

@jumpedwithbothfeet said in Tool failed during print:

MCU temperature: min 37.5C, current 87.2C, max 87.4C

That is pretty toasty. Is this an enclosed printer?

jumpedwithbothfeet

@Phaedrux yes it is but only passively heated, water cooled hot end, Im trying to figure out a way of water cooling the board as a fan won’t cut it! And I’m guessing the board rear side is where the heat gets transferred like the main board?

jumpedwithbothfeet

Update, found a crimp that had gone bad on the part cooling fan (ground side) this maybe partly to blame, but doesn’t solve the hot cpu issue, could it cause the memory issue?

Phaedrux

does it still get hot like that without the bed heater and extruder heater going and the enclosure open?

jumpedwithbothfeet

@Phaedrux so essentially the printer turned on but not running a print? I’ve not tried it, I’ll turn it on and report back

jumpedwithbothfeet

@Phaedrux the temperature increased from 23.3 degrees to 31.4 over an hour.


M122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.5.1 (2024-04-19 14:42:41)
Bootloader ID: SAMC21 bootloader version 2.8 (2023-07-25)
All averaging filters OK
Never used RAM 4128, free system stack 132 words
Tasks: Move(3,nWait 7,0.0%,135) HEAT(2,nWait 6,0.3%,107) CanAsync(5,nWait 4,0.0%,55) CanRecv(3,nWait 1,0.0%,71) CanClock(5,nWait 1,0.0%,59) ACCEL(3,nWait 6,0.0%,53) TMC(2,delaying,3.4%,53) MAIN(1,running,91.6%,315) IDLE(0,ready,0.0%,27) AIN(2,delaying,4.6%,112), total 100.0%
Owned mutexes:
Last reset 01:07:56 ago, cause: power up
Last software reset at 2024-04-21 11:59, reason: OutOfMemory, available RAM 0, slot 0
Software reset code 0x01c0 ICSR 0x00000000 SP 0x20004c68 Task Move Freestk 115 ok
Stack: 20004ee0 000063e3 20004f40 20005fa8 20004f40 0000a51d 20004ccc 00008faf c5784ca0 2e89a8bb 2e89a8bb 47a79800 be3335d3 ce2ae763 41661135 00014f30 00000001 0001f46a 200026cc 20005fa8 200076b0 000492ca 20004ccc 00009629 000007d0 3e5c209d 3f4c1414
Driver 0: pos 0, 860.0 steps/mm, standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 44134, writes 0, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, segs 0, step errors 0, maxLate 0 maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 0.00
Peak sync jitter 5/8, peak Rx sync delay 204, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 24.4, current 24.4, max 24.4
MCU temperature: min 15.5C, current 31.2C, max 31.4C
Last sensors broadcast 0x00000002 found 1 23 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 1799, send timeouts 0, received 802, lost 0, errs 0, boc 0, free buffers 18, min 18, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 0, contentions 0, other errors 0

Phaedrux

I guess that eliminates a failed component getting hot and cooking the rest of it. The driver chip and it's supporting electronics would be the main source of heat on the board.

Can you try running a print without the enclosure sealed to see if it stays cooler/lasts longer?

jumpedwithbothfeet

@Phaedrux I’ve just run a 1hr print door wide open the MCU crept up consistently during the print it was 25 degrees at the start, 68.5 just before finishing so it’s getting warm, I’ll sort out a 2 hour print tomorrow to see if it continues to climb or plateaus again with the door open.


M122 b121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.5.1 (2024-04-19 14:42:41)
Bootloader ID: SAMC21 bootloader version 2.8 (2023-07-25)
All averaging filters OK
Never used RAM 3096, free system stack 71 words
Tasks: Move(3,nWait 7,0.3%,89) HEAT(2,nWait 6,0.4%,91) CanAsync(5,nWait 4,0.0%,49) CanRecv(3,nWait 1,0.1%,71) CanClock(5,nWait 1,0.0%,59) ACCEL(3,nWait 6,0.0%,53) TMC(2,nWait 6,3.5%,53) MAIN(1,running,91.1%,315) IDLE(0,ready,0.0%,27) AIN(2,delaying,4.7%,112), total 100.0%
Owned mutexes:
Last reset 01:22:03 ago, cause: power up
Last software reset at 2024-04-21 11:59, reason: OutOfMemory, available RAM 0, slot 0
Software reset code 0x01c0 ICSR 0x00000000 SP 0x20004c68 Task Move Freestk 115 ok
Stack: 20004ee0 000063e3 20004f40 20005fa8 20004f40 0000a51d 20004ccc 00008faf c5784ca0 2e89a8bb 2e89a8bb 47a79800 be3335d3 ce2ae763 41661135 00014f30 00000001 0001f46a 200026cc 20005fa8 200076b0 000492ca 20004ccc 00009629 000007d0 3e5c209d 3f4c1414
Driver 0: pos 0, 860.0 steps/mm, ok, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 35276, writes 0, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 46438
Moves scheduled 59221, completed 59218, in progress 1, hiccups 57, segs 43, step errors 0, maxLate 0 maxPrep 504, maxOverdue 65, maxInc 64, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 1.00
Peak sync jitter 4/9, peak Rx sync delay 204, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 24.3, current 24.4, max 24.6
MCU temperature: min 15.8C, current 68.3C, max 68.5C
Last sensors broadcast 0x00000002 found 1 157 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 1450, send timeouts 0, received 1488, lost 0, errs 0, boc 0, free buffers 18, min 17, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 363, adv 36385/74657
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 0, contentions 0, other errors 0
I

jumpedwithbothfeet

@Phaedrux just about to finish a 3 hour print, the temp with the door open reached 73.1 so still fairly toasty! I’m gonna try it again with the cable cover off see if it makes a difference….


M122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.5.1 (2024-04-19 14:42:41)
Bootloader ID: SAMC21 bootloader version 2.8 (2023-07-25)
All averaging filters OK
Never used RAM 3144, free system stack 71 words
Tasks: Move(3,nWait 7,0.3%,85) HEAT(2,nWait 6,0.4%,91) CanAsync(5,nWait 4,0.0%,49) CanRecv(3,nWait 1,0.1%,71) CanClock(5,nWait 1,0.0%,59) ACCEL(3,nWait 6,0.0%,53) TMC(2,delaying,3.5%,53) MAIN(1,running,91.0%,315) IDLE(0,ready,0.0%,27) AIN(2,delaying,4.7%,112), total 100.0%
Owned mutexes:
Last reset 03:45:34 ago, cause: power up
Last software reset at 2024-04-21 11:59, reason: OutOfMemory, available RAM 0, slot 0
Software reset code 0x01c0 ICSR 0x00000000 SP 0x20004c68 Task Move Freestk 115 ok
Stack: 20004ee0 000063e3 20004f40 20005fa8 20004f40 0000a51d 20004ccc 00008faf c5784ca0 2e89a8bb 2e89a8bb 47a79800 be3335d3 ce2ae763 41661135 00014f30 00000001 0001f46a 200026cc 20005fa8 200076b0 000492ca 20004ccc 00009629 000007d0 3e5c209d 3f4c1414
Driver 0: pos 0, 860.0 steps/mm, ok, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 36389, writes 0, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 698704
Moves scheduled 203158, completed 203157, in progress 1, hiccups 853, segs 41, step errors 0, maxLate 0 maxPrep 567, maxOverdue 92, maxInc 64, mcErrs 0, gcmErrs 0, ebfmin 0.00 max 1.00
Peak sync jitter 5/9, peak Rx sync delay 236, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 24.1, current 24.3, max 24.6
MCU temperature: min 16.1C, current 71.9C, max 73.1C
Last sensors broadcast 0x00000002 found 1 117 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 19890, send timeouts 0, received 21397, lost 0, errs 0, boc 0, free buffers 18, min 18, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 369, adv 36230/74658
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 0, contentions 0, other errors 0

jumpedwithbothfeet

No difference with the cover off!