Figure out the printers IP and type that into a web browser but if you’ve connected via another router that’s probably not going to work, you need it to be on the same network and same subnet as your PC otherwise you have to get tricky with routing to make it work.
Can you just temporarily move it near your main router just to do some diagnostics?
I’m in. i’m still a bit lost. i glanced over the log file and i cant see anything jumping out at me other than its the same error repeating.
Click on the [machine} button next to the wrench. Then far top right corner click
A sub screen will open and allow you to see everything Linux has connected to.
I don’t see a way to flash the MCU’s from inside Mainsail.
If you SSH in and navigate to home\sovol\printer_data\build\
You should find
Precompiled firmware for the extruder_MCU and a script to flash it. I’m not sure if that script will run run from the command line without some parameters included in the call. Hell I’m not even sure it would’t burn down your printer.
@Vergo help
Plan B go to the machine tab and download printer.cfg
Put it someplace safe. Click on the filename to open it in Mainsail’s editor. CTL+F and search for
extruder_mcu. Put a # at the beginning of EVERY line that references extruder_mcu.
Save and restart
That might get the touchscreen to come online
I think that variable is set BY the reset routine to trigger additional housekeeping routines on the next boot.
If you open macros.cfg you will see the FACTORY_RESET macro right at the top
AND FACTORY_RESET just loads backup copies of all the config files. Does nothing to the OS or MCU firmware
Keep commenting lines till no more errors… or the coffee runs out
that sounds like im only going to possibly break something more.
Sovol tests the zero before shipping AND they install the OS by imaging the EMMC with an exact copy of the EMMC from a “reference machine”. If they neglect to clear the history prior to making the image file then your machine will remember things that happened before it was born.
Editing printer.cfg is pretty safe. Klipper is very heavy with safeguards. As you have seen it is quick to shut down if there is any danger.
I’m just wondering how that’s going to fix anything.
My hope is that if you can get the knob screen running you can go through the menus and tell us what process you aborted that left your machine borked.
IF that process was “flash extruder_mcu” like I think it was then restart that process and let it finish. Then a “factory reset” will load all the default configuration.
That is the safe route.
Quick and dirty is SSH in and from the home folder run
.\sovol\printer_data\build\extruder_mcu_update_fw.sh
Long method executes the process in the way Sovol intended. Short method could skip a vital step. 98% sure the short is safe BUT not my machine so I’m being super cautious.
cardoc is going through a process of elimination to at least get Klipper to start, I would personally be doing much the same thing on my own printer.
At this point I’d be starting with fresh config, you can try my config from my Zero if you like, it has a minor tweak to the resonance tester section which I believe has improved print quality, scp the tar.gz file to /home/sovol/printer_data/ (use WinSCP if you need a GUI tool).
Make a note of these 2 lines in your printer.cfg, save them somewhere for quick reference:
[mcu]
canbus_uuid: 0d1445047cdd
[mcu extruder_mcu]
canbus_uuid: 61755fe321ac
cd ~/printer_data/
Backup original config:
tar -czvf original_config.tar.gz config/
Remove old config
rm -rf config/
Extract my config:
tar -xzvf config.tar.gz
Replace the canbus uuid’s with the ones you saved earlier, then save and restart.
If you want to revert back to your config:
rm -rf config/
tar -xzvf original_config.tar.gz
config.tar.gz (12.1 KB)
Roger.
I’ll get playing with it when I get home from work. I did manage to score a free piece of marble to act as a paver under it. So at least my bricked printer is heavier now. 
I tested what that stop button does and it appears to be a surprisingly hard reset considering that the button only says stop.
@KeiffTi - since you now have SSH access, let’s start by figuring out which firmware the printer thinks is currently installed. For that’s you’ll want to copypaste the following command and hit enter:
grep -A2 __version /home/sovol/klipper/klippy/extras/display/menu.cfg
That should produce three lines that you should reply here. In case there’s a No such file or directory error, that also will tell us something. Assuming it was the firmware upgrade which you interrupted, the reply will most likely contain name: 1.4.7. If not then I’d assume it would be name: 1.3.7.
Since the screenshots suggest the firmware is out of sync between components, the fix should be to flash it again and this time not interrupt anything. This too can be forced from the command line and due to how the firmware packages have been structure, that will also overwrite any possibly corrupted files without touching the operating system. The necessary commands are the following:
cd /tmpwget https://www.comgrow.com/files/printer/SV08mini_Update_Package-03-29-1.3.8.debsudo dpkg -i SV08mini_Update_Package-03-29-1.3.8.debsudo syncsudo rebootThat intentionally uses the older firmware package since it doesn’t care of what the currently installed firmware is and will always overwrite the flashed binaries + all configuration files + klipper + mainsail. That should restore the printer’s functionality and then allow running the OTA from the menu to upgrade to the latest firmware (if you want to do that). The last command forces a reboot that will disconnect the SSH connect so run it only if the previous commands didn’t produce any surprising errors.
@vergo Off topic as the issue at hand does seem to only involve the extruder_mcu BUT if someone needed to flash the main or extra are there precompiled versions someplace? If not what are the parameters to put into “makemenu” to compile them? I don’t see any “use” of the extra_mcu in the Zero printer.cfg. On my Klipad the “extra” is the GPIO pins of the Raspberry Pi clone used only for the accelerometer.
Sovol gave us scripts but nothing to send.
Use the ssh connection to the printer, not the web interface and its gcode input.
