A few questions on updates of Klipper, Moonraker, Mainsail etc

I’m mostly on the software side as well, and have relatively extensive experience with debian. I don’t know how far we can get without the source for stuff like mksclient, but i’m fine losing all of the touchscreen functionality.

@sovol3d I don’t know if you’re noticing, but this all doesn’t reflect well on your business practices. I suggest you take another look at open sourcing the code for this printer. People are asking the same for other models, and this will not be a sustainable business model for you.

They at least REALLY need to stop claiming to be “Fully Open Source” if that is a bold face lie.

I have my SV06 totally Klipperized on an SKR 3 EZ, I don’t even like the touchscreen, I made my own and use Klipperscreen in its place which works SO much better… if it is possible to get the printer functionality working on a new board and ditch everything and just run Mainline Klipper, I’m in.

Does anyone have an Ace and a computer capable of running Linux + klipper? I wonder if the “OTG” connector would allow an external host to connect with the MCU.

The toolhead is in fact a “normal” MCU and should happily connect to any Klipper host over USB. You’d need to make a cable to convert the host end to a “normal” USB plug.

Would this be required if the main board was replaced with an SKR 3ez or similar?

Depending on how the OTG port is configured it MAY be possible to connect an external host to the existing MCU.

I’m liking the design of the Ace less and less. I’m not sure I fully understand so far, but it seems like I need to have two instances of Klipper for one printer?

Klipper is several* parts. Klipper runs on one or more mcu(s). Klippy runs under Linux on a general purpose computer.

The ACE mainboard has the MCU and the PC both on one circuit board.

*Other components on the Linux side:

  • Moonraker - Web API
  • Crowsnest - Camera
  • Klipperscreen (Optional GUI for hosts with attached monitors)
  • Mainsail (Optional web interface)
  • Fluidd (Optional web interface)
  • etc
1 Like

Sorry, it’s just the printer side I don’t get, I should have clarified. I do get how Klipper/the components, just not sure how the separate MCU and Mainboard (if the mainboard of the ACE were to be replaced) would function with Klipper.

I’m generally a linux guy and run Klipper on my other printer without issue.

No, you would pull the old MCU & install it on the new board.

But isn’t the MCU on the Toolhead? So remove it from the toolhead and install it on the new board? Would I then need and EBB36/42 on the toolhead? Sorry for the dumb questions.

Klipper is on the MCU, you just remove the 2 screws & move the MCU to the new board & nothing will change.
I had the same thoughts until I replaced the board on my Zero…it’s basically Plug & Play.

However if you replace the MCU with a bigger 32GB unit, you will have to clone the old MCU onto the new one.

Klipper supports multiple MCUs. The Ace has 2. One in the toolhead, one on the mainboard.

Look at the printer.cfg file. Notice the pin addresses;

[stepper_z1]
step_pin: PB14
dir_pin: !PB15
enable_pin: !PB10
microsteps: 16
rotation_distance: 4
endstop_pin: probe:z_virtual_endstop

[tmc2209 stepper_z1]
uart_pin: PB13
run_current: 0.7
interpolate: True
stealthchop_threshold: 999999

[extruder]
step_pin: extra_mcu:PA8
dir_pin: !extra_mcu:PA9
enable_pin: !extra_mcu:PB11
microsteps: 16

See how the extruder step_pin includes “extra_mcu” while the Z step_pin defaults to the “primary” mcu.

Does the MCU need to be swapped to the new board if I want to do a fresh install of Klipper Mainline on it? I didn’t have to do that with the SV06 that I recall?

The MCU (MicroController Unit) is soldered to the mainboard

Some of the printers (SV08, Zero, Max) have a EMMC board that plugs into the mainboard. This board is the storage for the Linux OS and programs/data for the HOST computer. The EMMC is faster than a SD card but slower than a SSD.

As far as I know the ACE has flash (or EMMC) memory soldered to the main board.

As far as I know no one has put an Ace on mainline. I can’t even verify it uses the RockChip H616 CPU as the SV08, Zero and Max.

I think I’m getting more confused by a few different replies from people. I have no intention of trying to put mainline on the existing board. I want to swap it entirely like I did with the SV06 and then flash the new board (probably another SKR 3 ez since I have had no issues with the one I use now on the SV06); another reply mentioned having to swap the MCU to that board.

I agree no one has done it, just trying to see if there is a path forward TO do it and still retain all the functionality of the printer (nozzle probing/etc).

Yep, I made a mistake about swapping the MCU…
The Zero & the SV08’s can do it, the other’s can’t.

Yes if you change the mainboard (and connect a linux host) you can do whatever you want.

The toolhead MCU would need to also be connected to the host and printer.cfg would need to be overhauled to remove Sovol proprietary stuff.

The Ace uses a loadcell on the hotend attached to a HX711 AD converter. The HX711 is supported by klipper BUT not in the same way as Sovol handles it.

Sovol’s [kx711] function outputs a true/false signal then passed to [smart_effector] and is NOT supported by mainline.

Klipper’s [load_cell] function requires user calibration and outputs a force value in grams.

Kalico WOULD allow you to “splice” Sovol’s [hx711] module into it but that may not be a path you want to take.

Plan C:

Don’t reference the HX711 at all in printer.cfg and install a 3rd party eddy or probe. That gives you mainline without having to configure/calibrate the load cell.

This is the part I’ve been worrying about and hoping there was a solution for.

I posted 3 solutions:

  1. Implement Klippers load cell functions
  2. Switch to Kalico fork of Klipper
  3. Install 3rd party eddy or probe

#1 is well supported at General Discussion - Klipper

Sorry, yeah, I missed the 3 things you posted scrolling on mobile and was heavily medicated and not making much sense on a re-read (was stuck in the ER for an unrelated to attempting this accident, ha). I appreciate the help and #1 seems to be the way to go. I have a board coming so we’ll see how it goes.