SV06 - MCU Shutdown - Can Someone Please Look At This Log?

General Discussion
1

Basic Information:

Printer Model: Sovol SV06
MCU / Printerboard: Stock
Host / SBC- Raspberry Pi
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

Again, I’ve had a sudden MCU Shutdown and there’s no other explanation on the dashboard or notifications in Klipper.

Can someone take a look at the log file attached and see if you can see something? I’ve tried looking but don’t have any experience with the log files and haven’t been able to find a guide or tutorial.

thanks

logs-20241021-kLIPPY.zip (525.4 KB)

2

The last Gcode command was this:

G1 Z2.7 F21000

Quite fast for a Z-axes.

1 Like
3

Yeah, would have have come from the slicer or the system settings?

4

Hard to say.

Maybe from the slicer. The wipe settings?

5

I just checked the gcode file for the model I printed right before this and it’s got that all through it since I’m printing PTEG:

;WIPE_END
G1 Z.65 F21000

that one printed fine, actually it’s printed beautifully and the settings were all the same in the slicer

6

The error Lost communication with MCU 'mcu' is typically not caused by odd gcode commands. See Timeout with MCU / Lost communication with MCU

Apart from this, Klipper luckily limits your z-movement velocity to max_z_velocity

1 Like
7

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.