MCU 'mcu' shutdown: Timer too close when homing

[nefelim4ag]

Timer too close

Background A “Timer too close” error occurs when the MCU attempts to schedule a timer for a target time that is in the past. It almost always occurs as a result of a message from the host requesting an action at a time that is now in the past. It is important to understand that Klipper essentially knows which command was scheduled in the past, but not why it happened. For example, a message is delayed because the webcam is blocking the USB port: The message contains a command whose target time …

Latency/bandwidth issue.

Also, there are system load:

also, there are mysterious temperature_logger.py

BTW, this is not a good idea to modify files and add random code commands.