Printjob unexpectantly halted during night

General Discussion
1

klippy.log file available here: klippy.zip (1.6 MB)

I am using a SK-Tank with a Raspberry Pi 2B+ and BigTreeTech GTR board

Last night a set a print going only to discover in the morning that the print had halted at some stage during the night:

20240117_125906
20240117_1259061920×1919 370 KB

The “Terminal” window in OctpPrint doesn’t show anything relevant but the “Klipper” window shows this:

00:04:58 probe at 344.000,0.000 is z=1.008500
00:05:04 probe at 175.000,300.000 is z=1.020500
00:05:10 probe at 40.000,0.000 is z=1.009500
00:05:11 Making the following Z adjustments:
stepper_z = -0.190745
stepper_z1 = -0.191872
stepper_z2 = -0.178213
00:05:11 Unknown command:"T0"
00:05:22 Unknown command:"G1 1000"
03:14:25 Klipper: Standby
05:14:57 Klipper: Standby

I set the print going at about midnight so I believe those 00:05:XX logs are of the print starting, then the 03:14:25 Klipper: Standby message is from when the print halted.

I still find the klippy.log file a little hard to parse but it does contain these interesting lines:

Transition to shutdown state: MCU 'mcu' shutdown: Timer too close
This often indicates the host computer is overloaded. Check
for other processes consuming excessive CPU time, high swap
usage, disk errors, overheating, unstable voltage, or
similar system problems on the host computer.
Dumping gcode input 50 blocks

though I have no idea what time it occurred.

I have actually had something similar to this happen before but had no idea what it was so just rebooted and started again, and it worked fine.

I have no reason to think the MCU is overloaded, or if it were why it would happen at this stage of a print.

Clicking “Analize Log” in the “Klipper” tab of Octoprint shows this interesting graph:

LogAnalisis
LogAnalisis2398×1198 236 KB

I have little understanding of what it is showing but there is a clear spike in the “Host Buffer” about one third the way through that “Bandwidth” block however the “MCU Load” seems low the whole time. Also the time scale’s odd, showing all the activity happening the previous evening, ceasing at around 8:30pm.

If anyone can help me understand what’s going on I’ll be most grateful!
Thanks.

2

Hmm, I tried restarting the print and after a little less than an hour when I checked on it I discovered that on layer 51 of 358 (earlier than before) it had paused. The “Klipper” tab in Octoprint just shows: Klipper: standby

I’ve tried typing RESUME at the terminal but it says:

Send: resume
Recv: !! Unknown g-code state: PAUSE_state
Recv: !! Unknown g-code state: PAUSE_state
Recv: ok

Which is no doubt because it was paused without running the code I have in my [gcode_macro PAUSE].

However, clicking the play button (also labelled “Resume”) in the “Control” tab of Octosprint has set it going again.

Any idea what’s going on?

Note, when I got to it this time it was only 6 minutes after after the print had stopped.
While the hotend had cooled some the bed was still set to 60°C (which was not the case this morning), so I just manually reset the hotend to the the regular printing temp and set it going again.

3

Please always post a klippy.log when new issues occurs. From

nobody can derive any further insights.

Generally the Timer too close often is a spurious thing but relates to issues on your host side.

4

The klippy.log file is attached in the first post is it not?

I definitely meant to include it, please do let me know if it hasn’t worked.

5

Yes it is there. At the very end.

It’s preferred to keep the template in place and put the klippy.log there where it is requested. It makes things more easy for supporters.

6

No problem.
I’ll just move it to the top of the message for now: :+1:

1 Like
7

Well, according to the provided, only a Timer too close error is recorded and there is no indication that the error condition has been cleared by restarting the firmware.

8

Well, it just happened again. No idea why but I was sure not to reset and I have attached a new Klippy.log file.

Any insight you can give will be much appreciated.
klippy.zip (1.1 MB)

9

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.