MCU 'mcu' shutdown:

[mykepredko]

Thank you for starting a new thread here.

Going over your klippy.log, the first order of business is that your version of Klipper is “dirty”:

Starting Klippy...
Args: ['/home/mks/klipper/klippy/klippy.py', '/home/mks/printer_data/config/printer.cfg', '-I', '/home/mks/printer_data/comms/klippy.serial', '-l', '/home/mks/printer_data/logs/klippy.log', '-a', '/home/mks/printer_data/comms/klippy.sock']
Git version: 'v0.12.0-379-gf2e69a370-dirty'

The first order of business is to go to the “MACHINE” page in your Mainsail web page and do updates to get rid of the “dirty” status.

Then run again and see if the problem persists.

I should point out that this is a “Timer Too Close” error. If, after getting rid of the “dirty” status problems persist, then read through and look for situations that affect your printer:

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 …