MCU 'mcu' shutdown:

[mykepredko]

@engineer-50

@mykepredko

I’m suggesting that you lower the number of microsteps to 16 because it’s easy to do and often fixes the problem.

Already set the microstepping to 16 and tested. It has just now failed - around 30 minutes into the print. This time with a different error though:

Lost communication with MCU 'mcu'

Attaching the log:
klippy0312_A.log (2.4 MB)

Sorry, then I suggest you start going through the suggestions here:

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 …