Getting MCU 'mcu' shutdown: Timer too close starting print

[Terramoto]

Basic Information:

Printer Model: Ender 3
MCU / Printerboard: BIGTREETECH-SKR-mini-E3-V3 + klackender probe
Host: Proxmox VM running prind stack

klippy.log (582.8 KB)

Describe your issue:

It’s my first time trying out Klipper, i was printing with Marlin before. I managed to configure the printer to the point where i can home all axis along with the probe but as soon as i try to start a print, the printer initiates all motors but after raising z axis for a moment it stop everything and comes up with the error MCU ‘mcu’ shutdown: Timer too close.

I’ve tried checking the VM resources which seem to have enough available both CPU & RAM wise.

[EddyMI3D]

Hello @Terramoto !

Please have a look on this:

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 …

[Terramoto]

Sorted, gcode file was causing it. Generated another using Cura instead of OrcaSlicer and that worked, will need to check what’s different between them.