Errors after updating Klipper and moonraker

Sovol Klipperized SV07
1

Hello,

The situation is that after updating Klipper and Moonraker via the frontend, thinking nothing would break, it ended up breaking.

Right now I have the versions

2026-03-02 07_58_14-fruit+bowl - OrcaSlicer
2026-03-02 07_58_14-fruit+bowl - OrcaSlicer832×737 58.1 KB

And I have identified that there is a problem requiring me to set the z_offset value in the printer.cfg file. The issue is that whenever I level the Z axis from the frontend or the printer’s screen, that line gets commented out and the following error reappears:

“Option ‘z_offset’ in section ‘probe’ must be specified

Once the underlyung issue is corrected, use the RESTART command to reload the config an restar the host software

Printer is halted”

I have also noticed that the system is adding a SAVE_CONFIG comment to the printer.cfg file.

At this point, does anyone know of a solution, or would it be better to try downgrading Klipper and Moonraker?

Thank you very much.

2

@cardoc

3

My guess is that a macro written by Sovol is your issue.

Unfortunately my SV07 is running mainline klipper and I’ve replaced the Klipad50 with a Intel based tablet computer. I also have replaced all the Sovol macros with this package:

I highly recommend the printer extensions BUT I’d recommend you debug your current problem before jumping into a major upgrade.

Try this:

  1. Power cycle your printer.
  2. Open printer.cfg using the web UI from your PC to add the Option ‘z_offset’ in section ‘probe’
  3. Save and restart
  4. Run the “paper test”.
  5. Save and restart.
  6. From your PC use a browser (not Orca*) to download klippy.log to your PC
  7. Zip klippy.log and upload here.
  • Fluidd/Mainsail inside Orca can not download files. You have to open a browser and connect using the printers IP address.
    The reason for klippy.log is that klipper copies the printer.cfg AND any [include]ed files to the log every time the printer starts or restarts
4

Hi, first of all, thank you so much for your message. Checking the Klippy log file as you suggested, I found an error.

Starting Klippy…
Args: [‘/home/mks/klipper/klippy/klippy.py’, ‘/home/mks/printer_data/config/printer.cfg’, ‘-I’, ‘/home/mks/printer_data/comms/klippy.serial’, ‘-l’, ‘/home/mks/printer_data/logs/klippy.log’, ‘-a’, ‘/home/mks/printer_data/comms/klippy.sock’]
Git version: ‘v0.12.0-0-g0d67d9c45-dirty’
Untracked files: klippy/extras/gcode_shell_command.py
Branch: (HEAD detached at v0.12.0)
Remote: ?
Tracked URL: ?
CPU: 4 core ?
Python: ‘3.7.3 (default, Oct 31 2022, 14:04:00) \n[GCC 8.3.0]’
Start printer at Mon Mar 2 00:09:40 2026 (1772406580.9 26.7)
Can’t read autosave from config file - modifications after header

So I deleted everything after the header, and after restarting, everything is fixed. Thank you very much.

5

Glad you got it sorted out.