Klipper: "MCU 'mcu' shutdown: Timer too close"

General Discussion
1

Basic Information:

Printer Model: Voron 2.4
MCU / Printerboard: BTT Octopus v1.1
Host / SBC: RPi4
klippy.log

Describe your issue:

I sporadically get a Timer too close error. I this time I was observing the error where the filament just changed, the Blobifier made its filament poop and the toolhead was moving from the corner of the machine to the printed object when this happened.

So when this triggered, there was no complex movement going on as far as I can determine.

I’ll attach the log and the plots, but it looks like there was a sudden lag spike on the host - although I am not sure why or how to debug that.

Any suggestions?
klippy.log (5.4 MB)

2

System graph
timer_too_close_systemgraph

3

Load graph
timer_too_close_statsgraph

4

Generally, the reasons as listed in Timer too close do apply.
For heavily modified Klipper versions no further guidance can be offered.

5

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