I got my printer a couple of weeks ago and upgraded it to an enclosure. I also installed a new EMMC (32GB) with mainline klipper. Printer seems to work correctly and it does really nice prints when it’s working. Yesterday for example I ran 4 print jobs (short ones at ~30-40mins each) without any issues.
Today it crashed during bed leveling procedure of the first print. I turned it off and on again and gave it another go. It printed the first 2 layers and crashed again. When it crashes the case fan goes out (I think the one on the hotend keeps on running) and the light turns off as well. There’s no text on the display, but its light is still on as well). If I only use WiFi that stops working as well. Machine doesn’t react to pings anymore. HOWEVER, when I am connected through the LAN port, the connection remains active. The linux system seems to be working still.
The journal looks like this:
Sep 01 20:00:01 sovol-sv08 CRON[6523]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Sep 01 20:00:01 sovol-sv08 CRON[6524]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) Sep 01 20:00:01 sovol-sv08 CRON[6523]: pam_unix(cron:session): session closed for user root -- Here the crash happens -- Sep 01 20:07:48 sovol-sv08 python[686]: [klippy_connection.py:_on_connection_closed()] - Klippy Connection Removed Sep 01 20:07:48 sovol-sv08 systemd[1]: klipper.service: Main process exited, code=killed, status=11/SEGV Sep 01 20:07:48 sovol-sv08 systemd[1]: klipper.service: Failed with result 'signal'. Sep 01 20:07:48 sovol-sv08 systemd[1]: klipper.service: Consumed 3min 24.771s CPU time. Sep 01 20:07:58 sovol-sv08 systemd[1]: klipper.service: Scheduled restart job, restart counter is at 1. Sep 01 20:07:58 sovol-sv08 systemd[1]: Stopped Klipper 3D Printer Firmware SV1. Sep 01 20:07:58 sovol-sv08 systemd[1]: klipper.service: Consumed 3min 24.771s CPU time. Sep 01 20:07:58 sovol-sv08 systemd[1]: Started Klipper 3D Printer Firmware SV1. Sep 01 20:08:05 sovol-sv08 python[686]: [klippy_connection.py:_do_connect()] - Klippy Connection Established Sep 01 20:08:11 sovol-sv08 python[686]: [klippy_connection.py:_request_initial_subscriptions()] - Webhooks Subscribed Sep 01 20:08:11 sovol-sv08 python[686]: [klippy_connection.py:_request_initial_subscriptions()] - GCode Output Subscribed Sep 01 20:08:11 sovol-sv08 python[686]: [klippy_connection.py:_check_ready()] - Sep 01 20:08:11 sovol-sv08 python[686]: Can not update MCU 'mcu' config as it is shutdown Sep 01 20:08:11 sovol-sv08 python[686]: Once the underlying issue is corrected, use the Sep 01 20:08:11 sovol-sv08 python[686]: "FIRMWARE_RESTART" command to reset the firmware, reload the Sep 01 20:08:11 sovol-sv08 python[686]: config, and restart the host software. Sep 01 20:08:11 sovol-sv08 python[686]: Error configuring printer
So no idea what’s happening. There’s no way to turn it back on from the shell, I have to turn the machine off and on again. So no idea what to do here. Could it be the power supply? Or the mainboard?
WiFi isn’t far away, it’s in the next room. I don’t think it should cause the printer to crash even if it would lose the WiFi connection. I will try running it without WiFi though to see if it changes anything.
Hi, are you getting warnings, or on your PC? To me it looks s like toolhead board has lost communication with the motherboard. It could be a simple loose wire on tour toolhead or the main board. Check these out first, also check the earth cable on the toolhead, they have a habit of coming loose. If all those things are OK it could be a brake in the cable from the toolhead to the board. Use a multimeter and check out each individual cable, turn the metre to containuty and check the cable from each end
No warnings, no. I just saw something in the log, but I don’t know whether this message came because of the crash or if it was the reason.
Aug 27 21:54:22 sovol-sv08 python[7688]: [klippy_connection.py:_on_connection_closed()] - Klippy Connection Removed Aug 27 21:54:22 sovol-sv08 systemd[1]: klipper.service: Main process exited, code=killed, status=11/SEGV Aug 27 21:54:22 sovol-sv08 systemd[1]: klipper.service: Failed with result ‘signal’. Aug 27 21:54:22 sovol-sv08 systemd[1]: klipper.service: Consumed 36min 29.142s CPU time. Aug 27 21:54:32 sovol-sv08 systemd[1]: klipper.service: Scheduled restart job, restart counter is at 1. Aug 27 21:54:32 sovol-sv08 systemd[1]: Stopped Klipper 3D Printer Firmware SV1. Aug 27 21:54:32 sovol-sv08 systemd[1]: klipper.service: Consumed 36min 29.142s CPU time. Aug 27 21:54:32 sovol-sv08 systemd[1]: Started Klipper 3D Printer Firmware SV1. Aug 27 21:54:33 sovol-sv08 python[7688]: [klippy_connection.py:_do_connect()] - Klippy Connection Established Aug 27 21:54:40 sovol-sv08 python[7688]: [klippy_connection.py:_request_initial_subscriptions()] - Webhooks Subscribed Aug 27 21:54:40 sovol-sv08 python[7688]: [klippy_connection.py:_request_initial_subscriptions()] - GCode Output Subscribed Aug 27 21:54:40 sovol-sv08 python[7688]: [klippy_connection.py:_check_ready()] - Aug 27 21:54:40 sovol-sv08 python[7688]: Can not update MCU ‘extra_mcu’ config as it is shutdown Aug 27 21:54:40 sovol-sv08 python[7688]: Once the underlying issue is corrected, use the Aug 27 21:54:40 sovol-sv08 python[7688]: “FIRMWARE_RESTART” command to reset the firmware, reload the Aug 27 21:54:40 sovol-sv08 python[7688]: config, and restart the host software. Aug 27 21:54:40 sovol-sv08 python[7688]: Error configuring printer
Would the missing toolhead connection cause it to turn off the lights and other systems? I don’t know how this is all connected. A lose cable could explain the randomness of it all. Sometimes it prints a long time without any issues.
An “extra_mcu” com error should trigger a klipper error but NOT lock up the OS.
What led you to feel the need to go to “mainline”? It seems to me your issues are 2 fold. 1) Intermittent toolhead com issues (VERY common on the SV08). 2) An unstable Armbian install from wherever you got your “mainline” image.
Sovol will support the com issues with parts under warranty but you’ll need to revert to stock OS. Does the original EMMC still have the original installation on it?
Yeah, I put the original EMMC aside without touching it. I like my devices open and moddable, that’s why I didn’t buy a Bambu Lab.
There’s a tutorial for the mainline klipper installation:
Yeah, the OS still seems to be working (at least when LAN is connected), but it doesn’t look like it’s able to communicate with the printer anymore until I do a full power cycle.
I wouldn’t even know what to tell Sovol. I would have to know what’s wrong with the device first. I don’t think they will be able to figure that out remotely given the randomness of the crashes.
This is now the 2nd day I can print without issues. Yesterday I shut down the WiFi module, today I did as well.
I am not sure if those errors are the cause or an effect of my issue.
Yes, I was following the instructions so I also installed the “katapult bootloader” on both MCUs. I wasn’t sure if the old EMMC would still boot after that change. Where does the bootloader go?
I’m tech savvy, but I know nothing about klipper and the hardware components involved. The klipper installation guide I linked didn’t really explain things and it’s not beginner-friendly.
Looks like I will have to do some hardware probing then.
On a Microcontroller the bootloader is roughly equal to the BIOS on a PC.
It manages the low level interface tasks, including how it announces itself on the USB. Klipper doesn’t care about which bootloader is used but it needs to know how Linux configured the connection. If you use the same configuration files that work on mainline you should be golden.
If you just swap the EMMC klipper MAY come back with “unable to connect” using the stock configuration files.