Lost communication with MCU and MCU 'mcu' shutdown: Timer too close

[EddyMI3D]

Hello @MikiFX !

You may have a look on these:

Timer too close

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 delayed communication between the host and the MCU - for instance, if the host was busy or the message was blocked en route. Important: Klipper can identify what command was too late, but cannot determine why the delay occurred. The root cause is often external - such as USB congestion from a webcam or high system …

Timeout with MCU / Lost communication with MCU

Timeout with MCU / Lost Communication with MCU Background This error occurs when the Klipper host receives no response from a connected MCU to its regular “heartbeat” or other command messages for several seconds. It often appears in conjunction with the Got EOF when reading from device error. Important: Klipper only detects the symptom - a communication loss. It is not capable of determining the root cause, which may lie outside of Klipper’s control (e.g., hardware faults, power i…