Klipper, Sovol and Cura

Basic Information:

Printer Model: Sovol SV06+
MCU / Printerboard: ?
Host / SBC Windows 11
klippy.log what?

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

…I have a Klipper screen to replace the stock one of my Sovol SV06+ printer which was working fine with the old GUI and latest Cura. I was provided with a file to tie them all together but when the install gets to 1/3 of the way through it reports a corrupt executable and quits. The file was supposed to be Cura, with Klipper addi-in with Sovol configuration. I can’t find the file at Sovol (they are not helpful). The Klipper works at the printer end but I can’t connect with USB so I can print something. I am not using Octoprint or an PI device, just the GUI. Any ideas? I found a Klipper cfg file (for Sovol SV06+) at Github, but have no idea how to use it.

It’s almost impossible to offer any useful feedback with this information. We don’t know what this “file” is or where you got it. You say your host is an SBC with Windows 11 but Klipper requires Linux. Cura has absolutely nothing whatsoever to do with installing Klipper.

2 Likes

Well, I got a thumb drive (USB) that came with my Klipper device that I bought off the Sovol website. The file was a Microsoft (not Linus) self-extracting executable. The file was the Cura profile so I could use it with my Sovol. (I had a Sovol profile before but no Klipper…now the USB port has to be recognized for Klipper instead of the Sovol. The problem is that the executable failed at 30% with a corrupt file warning. I’m trying to get that file from Sovol but having difficulty. Thought maybe the Klipper guys would know. Everything I’ve said here I put in my first post. Sovol, Windows, Cura, Klipper…all SUPPOSED to work together. No RPI, No octoprint, no Linux.

Where did you get this idea that these different pieces would work together (I presume you mean seamlessly and through one interface)?

Nothing you’ve described sounds like it has anything to do with Klipper.

2 Likes

From Sovol. I bought the Klipper screen from their website where they said it was compatible with their printer. I made the mods required to make it work on the Sovol but I can’t run Cura and have it talk to the Klipper via USB. (I did have a wifi connection at one time, but I’m already wired for USB).

Can you provide a link to where Sovol states/indicates that (their) Cura can “talk to the Klipper via USB”?

That’s definitely incorrect and misleading in the extreme.

Sovol sent me an email address to someone who supposedly can help, so I’ll wait until then before commenting further. Like I said, the ONLY issue is the corrupt file in the self-extracting executable. If I get that solved, and THEN it doesn’t communicate, THEN I have problem. I attached the last page of the User manual, where I’m currently stuck installing the Cura file.

One thing at a time here, all the things you’re describing are different things.

Cura is a slicer for taking 3D models and making them work with a 3d printer. That’s it’s own software that runs on your computer. Totally separate from the actual printer.

Klipperscreen is just an addon device that works with Klipper to give you a nice little UI interface.

I think Sovol just has really crappy documentation (not surprising).

Looking at the Sovol site the link to the file for the klipperscreen firmware is here…

https://drive.google.com/drive/folders/1vpKWQXOMGV58dYcx2wK9wJC0HJNqU8tg

with instructions that are different than the ones you show.

I’ll be honest, I don’t use Klipperscreen so not sure why it needs it’s own debian file. That sounds kind of weird but I won’t speculate.

If that doesn’t work, come back and we’ll do it the normal way.

I think you will find Sovols Klipper Screen is a all in one jobbie akin to SonicPad with the same issues I suspect

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.