Does someone got it done ?
What function/feature do you want/need to make mainline worth the risk?
As far as I can tell, with the pressure sensor no longer used in recent firmware the only thing not compatible with mainline is the display. Upgrade to a HDMI screen and use KIAUH to change repositories and you should be golden.
And, in case not, you can rollback to the previous firmware.
i just want it to work, printer.cfg be visible, moonraker does not crash, remove obico junk etc
printer.cfg is right where it belongs. You have to follow the [include] statements to get everything.
Pro tip: The klippy.log has the ENTIRE configuration written to is every time there is a firmware restart. Use Klipper Advanced Log Inspector if you don’t want to scroll the whole log.
You should be able to uninstall Obico with KIAUH. Uninstall everything in KIAUH of you want. Change repositories and reinstall only the pieces you want.
If uninstall/reinstall doesn’t satisfy you get a spare EMMC module and experiment.
I don’t have a Zero board to test with but the images below will likely boot on the board.
I’d recommend you have the USB <> EMMC dongle. On the Klipad (SV07) the bootloader is configured to boot EMMC first not the SD card. I assume the Zero is similar. You have to update the bootloader if you want to run off a SD card.
OR
One of the SV08 methods has a hack to modify the EMMC image and boot from SD. Might work on the Zero. The SV08 is also based on the same H616 chip.
I have upgraded the eMMC to a 32GB version by downloading the image from the sovol wiki and flashing it to the new eMMC board using the usb to eMMC adapter and it worked flawlessly, I first backed up all my configs too to make sure any modifications I had could be copied over. So far the only thing I kept was the webcam config changes suggested in another thread.
You could also take the eMMC out and use the adapter to clone the data for back-up and then do the klipper main line upgrades.
One thing to note is that you most likely would want to find a way to preserve the eddy sensor code, since that looks like it’s a Sovol specific bit of code that is required for optimal use.
I’ve seen posts at https://klipper.discourse.group claiming they are running a Zero toolhead on different printers with mainline klipper AND Kalico + eddyNG.
I don’t have personal experience so proceed at your own risk.
Just trying this out now. It does seem that the default sovol zero config uses the normal probe_eddy_current implementation and that in order to use eddy-ng the toolhead needs a firmware update.
I’m going to try that out now on the toolhead I’ve got installed on my ender 3 v2.
following this guide to flash the toolhead with mainline (or kalico or klippain) worked for me.
For the record, to get eddy-ng working:
[probe_eddy_ng eddy]
sensor_type = ldc1612
i2c_mcu = toolhead
x_offset = -19.8
y_offset = -0.75
i2c_software_scl_pin = PB10
i2c_software_sda_pin = PB11
that’s assuming the mcu for the toolhead is called toolhead otherwise change to the appropriate value.
I’m not sure why it needs those pin values like that, the STM32F103 that’s on the toolhead board should be able to use i2c_bus: i2c2 but it doesn’t work with eddy-ng. At least not on my setup.
The above does work, however, and I’m able to home the printer now.
Edit to add (6 October 2025):
So I’ve been looking to re-create some of the START_PRINT macro on my ender 3 and I now know that if you need to run the eddy probe with mainline klipper and not eddy-ng, then you’ll need to copy the ~/klipper/klippy/extras/probe_eddy_current.py file as it is not the standard version that comes with klipper. It defines a few extra gcode commands including RUN_PROBE_VIR_CONTACT which I believe is responsible for Z_OFFSET.
I’ve not tried to use this version yet