Klipper Connecting... (forever)

This morning I woke up to a myriad of tech issues, Ive had to reinstall Orca multiple times. But the main issue that seems to more or less soft lock me from any more trouble shooting is the fact my printer has been stuck on “Klipper Connecting…” permanently. Its driving me mad and I cant find any answers or similar issues (that I can comprehend at least)

In case it may be related,

Orca is also refusing to connect to my printer IP, and is spouting a bunch of error unauthorized notices for moonraker; as well as the not OctoPrint version 1.1.0 or higher is required

Im also unfortunately on a Mac (x86_64)

Any help would be majorly appreciated, Im at my wits end with this thing.

Do I understand correctly?
The built in touch screen says “klipper connecting”
and
You cannot reach the printer from within Orca

First thing, reset your router.
Next google how to access your router’s internal web control panel and how to view the “client list”. Is your printer connected? Is it on the IP address you have entered in Orca?

Its not a wifi Issue, I know that, Ive restarted it multiple times, and I know the IP I put in is correct, it just gives me back unauthorized errors and the Octoprint version requirement note.

What trips me up is when I first got the printer, before I had even connected it to Orca, Klipper worked just fine on the machine itself (You cant run the start up calibration withought it) So the fact it refuses to connect even just on the local end is confusing.

If your printer was working properly after unpacking, have you tried resetting it to factory settings?

Perhaps a change in your settings is the cause?

unfortunately that was one of the first thing I tried, and have since tried like well over a dozen times both on machine and on orca, so no :frowning:

If you’re under warranty, email to info@sovol3d.com with your order number and an explanation.

Their support team will help you quickly.

How do you “know”?

Have you tried connecting with Safari?

I was trying to figure out if Linux is booting far enough that you can use SSH to remote in and fix Klipper. If not the only way to proceed is to re-flash the entire OS. I don’t even know if that is possible using a Mac.

There is a Mac version of the RKDevTool but I’ve no idea if it is compatible with the Sovol image and the SV06 hardware.

Link to Mac package is near the bottom of the page.

I know its not wifi since the issue has nothing to do with my wifi, Klipper is built into the machine and should be able to work from usb files alone even if I didn’t connect my computer, every possible wifi issue has been reset and reinstalled multiple times over. As for the other stuff, I have absolutely no idea what any of that means.

I did the same day it broke, so far nothing has helped, or been applicable for mac computers.

Yes your printer is broken. Send an email to info@sovol3d.com and include your order number.

As for the “other stuff”
The mainboard in your Ace is essentially 2 separate components. One half is a “computer” equivalent to a Raspberry Pi. It boots to Linux (Armbian). Linux then connects to WiFi and loads Klipper. Once loaded Klipper, connects to the other half (the MCU).

If Linux is broken you’ll have to reflash your board.

If Klipper is broken there are easier ways to fix it. I was trying to help you figure out if you could avoid the complicated reflash process.

Part of that process is verifying what (if any) IP address your router has assigned to the printer. Your router CAN (for various reasons) move your printer to a different IP address. If that has happened it should not stop your printer from booting BUT it is possible that whatever is broken in your printer triggered the router to assign a different IP

BUT the reflash process will fix both Linux and Klipper.

IF you want/need to reflash you’ll need to install rockchip-flash-tools on your Mac

alright ill give it a whirl, thank you for the explanation its incredibly helpful, if it wasn’t obvious tech isn’t my strong suit lol. Sovol sent me the same tutorial but didn’t share mac specific files so I was worried I was more or less doomed.

In my opinion combining the “host” computer and the MCU board is a horrible design choice. It hugely complicates recovering from errors.

BTW the “loading Klipper” screen is a lie. It is a static image the MCU Shows on powerup and just sits there. The MCU has no idea what is happening on the “host” side of the board.

2 Likes

Great news, after many hours of ripping my hair out, I got it to work. The true solution for Mac users with this issue is unfortunately biting the bullet and just downloading windows through bootcamp and running the fix that way. Unless you speak the IOS terminal system fluently, you wont get it to work.

But in the end a win is a win, just sacrifice a bit of storage while fixing it and revert it back over once you finish. Now i’m getting a replacement cable sent to me by support that I don’t need for free as well so thats a nice bonus.

But yeah, again, thank you so much for your help, your explanation and solution managed what I and the support couldn’t.

1 Like