My SV08 is on mainline klipper using a beacon probe and was running pretty good. Reliable prints, good z etc.
Today in my infinite wisdom, I used the mainsail interface to do some software updates including the system OS-Packages, Klipper, moonraker and moonraker-obico.
After doing that I got the message:
Internal error during connect: ‘MCU’ object has no attribute ‘register_response’ along with the usual once this is fixed restart.
Problem is I don’t know where to start. I can rollback klipper and moonraker but at least with klipper, I went from …513 to …572, moonraker went to …0-9.
Questions:
Is the OS on the host a standard version of linux or did Sovol “customize” it as well as klipper?
Can I re-install the OS without reverting to Sovol klipper? If so, a hint on how to do that would be helpful.
Thx for any help
UPDATE: I believe this is solved at least temporarily. I used KIAUH to rollback the versions / commits of klipper and moonraker to where I was before I updated. The printer started just fine. I haven’t had time to try and print yet.
Yes the OS is tweaked, but not in a way that should effect klipper.
First use WinSCP and download the entire ~/sovol folder to your PC
Then ssh in and use KIAUH to uninstall everything in the uninstall menu
drop to bash and sudo apt update and sudo apt upgrade
Optional sudo apt autoremove and sudo apt satisfy
Then use KIAUH to reinstall Klipper and the modules you use.
Use WinSCP to restore printer.cfg and any other cfg files you want to preserve, especially those called by [includes] in printer.cfg
restore any custom .py and .cfg files for your beacon (or reinstall it once klipper boots.
Optional - restore the /gcodes folder.
Burn some sage and reboot. Unless you’ve updated the MCU’s Klipper will complain about the V.0.11 firmware. Be ready for that.
Could the package updates done using mainsail/moonraker have affected the Sovol “tweeks”?
I am back up and running, using v0.13.0-513, rather than the -572 commit. Interesting fact, the mainsail interface still shows I’m on -572 even though I told KIAUH to go back to 513, but KIAUH shows I’m at -513.
I will probably do as you suggest, but not for a while.
As far as I know the tweaks are for hardware specific to the mainboard. There are also a few custom scripts inserted here and there but should be benign unless called. Mainline klipper won’t execute thosse.
The OS image is based on an Armbian build originally for the BTT CB1. I don’t have a SV08 to tinker with so I can’t really drill into the specifics.
You are correct as far as the Ambian image goes. It even calls itself a BTT-CB1 when you first login to a ssh session.
Welcome to BTT-CB1 2.3.4 Bullseye with Linux 5.16.17-sun50iw9
I did the backup you recommended with WinSCP. There were a couple of files the system could not or would not copy, I did not write down the names, sorry.