MCU ‘mcu’ shutdown: Timer too close This often indicates the host computer is overloaded . Basic Information: Printer Model: voron 2.4 350 MCU / Printerboard: HOST : old laptop linux mint 4gb ram Intel Core 2 Solo SU3500, Intel Pentium Dual Core SU4100 MCU: Spider v2.4 klippy.log Describe …

Some background jobs saturated CPUs to > 200% just before the shutdown happened: [sysstats] You can list scheduled tasks with sudo systemctl list-timers and sudo crontab -l and see if the culprit can be found by its execution schedule. You can also look at the system logs around the shutdown time…

Hello @shoxz ! You may have a look on this: [image] Timer too close Knowledge Base Timer too close Background A “Timer too close” error occurs when the MCU is asked to schedule an action at a time that is already in the past. This typically results from delay…

Timer too close e that is in the past. Reasons High system load of the host High disk activity Hi Eddy thanks for reply. i ve already read those, going by step high load: not the case im running 10 to 20% low free memory: host is clean only linux and klip ram is using only 800mb of 4gigs ,…

Could it be the high host buffer utilization? [image] Good luck, hcet14

sorry i tried to google it but didn’t get it, could you please explain whats host buffer and what may be the cause? thanks

hey Piezo, thanks also for your answer, background process or mainly update was a thing that came in mind also to me, thanks for the command line. Today im printing again the same gcode, i ve closed all linux process that can make update or background activity. Lets see.

Got the same error again after 10H, btw @Piezo im not able to save the klipper.service even if im logged as root, is that normal? Im almost sure that i will buy an overpriced RPi cause i really need to have this printer stable for long jobs becouse is going to print pricy filaments. Do you think t…

[image] shoxz: Core 2 Solo SU3500 is quite old Intel® Core™2 Solo Processor ULV SU3500 You might compare the RPi benchmarks against your 4gb ram Intel Core 2 Solo SU3500. Did you start installing Klipper with a fresh (deleted everything on the HDD) linux mint install? Good luck, hcet14

Can you post the klippy.log? This will allow checking if it’s the same issue and CPU load pattern. I think your problem is caused by the distribution. An old SU4100 laptop should not have any issues with Klipper if you dedicate it entirely to this task with a lightweight distribution like Debian. Y…

i know its old, but is empty and clean installed linux mint lite , there is nothing except klipper and some script for input shaper, no webcam also

@Piezo i ve just pulled it, i dont know if the issue is still showing cause i started another 2 “short prints” after that scenario. i was thinking about the pi cause u said that vm are not good for the task :+1: Klippy.log

MCU 'mcu' shutdown: Timer too close on voron 2.4

General Discussion

EddyMI3D June 3, 2023, 10:43am 2

Hello @shoxz !

You may have a look on this:

Also try with 16 microsteps.

Topic		Replies	Views
Error MCU 'mcu' shutdown: Timer too close General Discussion	1	519	June 15, 2024
Interpretation Help needed: MCU 'mcu' shutdown: Timer too close General Discussion	4	696	May 18, 2024
Problem with finding cause MCU shutdown Timer too close General Discussion	2	302	February 25, 2024
"MCU 'mcu' shutdown: Timer too close" error General Discussion	2	2567	December 27, 2022
Help needed with "MCU 'mcu' shutdown: Timer too close" :-( General Discussion	2	1856	May 30, 2023

MCU 'mcu' shutdown: Timer too close on voron 2.4

Related topics