Hello, I’ve owned a Sovol SV08 for a few months, and recently I’ve been getting a lot of Error 14 messages, but I can’t figure out the cause. I replaced the entire extrusion head, but I still get the same error.
It doesn’t happen every time, but it occurs occasionally and I have no way of knowing where it might be coming from.
Could you help me?
Thank you.
What is the actual Klipper error shown in the web UI?
Zip and upload your klippy.log and I’ll look it over.
Thank you for your reply. I’ve done several prints since the error occurred and I’ve rebooted the printer. Should I wait for the error to happen again, or can I send the file anyway?
I don’t know how to reproduce the error again. It happened once with an STL file, another time during an Orca temperature test print, and in other situations as well. But sometimes the prints finish without any problem.
Wait for it to crash again and grab klippy log as soon after as you can after.
Flag me when you upload in this thread.
Hello, after a long period, the error has recurred. I have sent klippy.log.
Thank you very much for your help and explanations.
logs-20260122-025352.zip (372,1 Ko)
Unfortunately the log you sent contains no print activity and no errors. Look in the log folder and send the all the klippy{date code}.log ones in 1 zip file.
=============== Log rollover at Thu Jan 22 00:00:00 2026 ===============
I think sovol uses UTC so you must have only missed it by a tiny bit.
logs-20260122-120448.zip (8,7 Mo)
I was having this problem when print complex geometries, tight circles, and/or Fuzzy skin. I found my solution in this thread… Read imagio’s comments to find the underlying cause: MCU ‘mcu’ shutdown: Move queue overflow - Sovol SV08 - Sovol3d forum.
My code is different than what was displayed in imagio**’s comment (probably due to an update). Commenting 20 lines in the** ~/klipper/klippy/extras/gcode_move.py file fixed the issue, as follows:
SSH into your printer with u:sovol p:sovol
Run: sudo nano ~/klipper/klippy/extras/gcode_move.py
Comment these 20 lines:
> # if 'G' in params and 'X' in params and 'Y' in params and 'Z' in params:
> # if self.v_sd.cmd_from_sd:
> # #commandline = gcmd.get_commandline()
> # cfg_file_path = '/home/sovol/printer_data/config/saved_variables.cfg'
> # _config = configparser.ConfigParser()
> # _config.read(cfg_file_path)
> # was_inter = _config.get('Variables', 'was_interrupted')
> # last_file = _config.get('Variables', 'last_file')
> # if 'Z' in params and float(params['Z']) > 0.2 and was_inter == 'False' and 'zoffset_test.gcode' not in l>
> # self.modify_cfg_value('was_interrupted', "True")
# if 'Z' in params: #for test
# self.z_positon = params['Z']
# if self.z_positon != "": #for test
> # content = {
> # 'commandline': gcmd.get_commandline(),
> # 'Z': params['Z'], #self.z_positon,
> # 'extrude_type': 'M82' if self.absolute_extrude else 'M83',
> # 'e_extrude_abs': 0 #self.Coord(*self.move_position)[3]
> # }
> # with open("/home/sovol/sovol_plr_height", 'w') as height:
> # json.dump(content, height)
> # height.flush()
> # os.fsync(height.fileno())
Thank you very much, I will try
Your log for the 21st contains
Traceback (most recent call last):
File "/home/sovol/klipper/klippy/gcode.py", line 459, in _respond_raw
os.write(self.fd, (msg+"\n").encode())
BlockingIOError: [Errno 11] Resource temporarily unavailable
It looks like @JohnnyBOOM is on the right track.
I created a version of gcode.py using an AI python tool (I’m not a programmer) and it flagged/fixed a second bug.
Look here if interested MCU 'mcu' shutdown: Move queue overflow
Thank you so much, I made the changes to the 20 lines of the gcode_move.py file and started a large print that lasted over 30 hours.
So far, 54% of the print has completed and there are no problems.
I also added a ferrite bead to the power cable, as well as to the hotend cable at the chassis behind the print bed.
I’ll keep you updated in a few days.
Thank you very much, it seems to be working. I have a strong impression that everything is going smoothly. But I have one last question. If I do a reset, will I lose the changes I made via SSH?
Define “reset”
Sovol’s “factory reset” (as far as I know) only deal with .cfg files to your changes would survive.
Firmware upgrades are case by case. That process can overwrite the .py files but only if they are included by Sovol.
Re flashing from the recovery image WILL revert the changes.
Thank you so much for your help. Every printing job had become a source of anxiety.
hey i’m having same problem
i get ssh
what is sudo nano and how do i run it?
by comment do you mean add?
i’m not very literate in coding
TIA
sudo is short for super user do (the config files can’t be opened by a “regular” user)
nano is a small text editor that runs in the terminal.
If you’d rather, I uploaded a pre-edited file to this thread.
My post is toward the bottom with instructions on how to get the file from your PC to your printer. Process is not “super easy” but is simper than editing a configuration file in the terminal.
PROTIP: if you have a windows11 PC Google WSL2 for dummies. Once enabled WSL2 lets you “play” with ubuntu to learn skills that will help you make future changes to your printer.
thanks for prompt answer
ill check it out
