Wipe the rootfs and debootstrap debian onto it, while keeping kernel, boot loader etc. untouched
Copy over some sovol specific files from the official image.
Repackage the image
The method should work for both SV06 Plus ACE and SV06 ACE but I have only tested it on the SV06 Plus ACE.
In theory I think it should be possible to also use this method to get other Linux-flavored operating systems on the printer such as arch by replacing debootstrap with pacstrap. But I have not tested this.
This is not meant to give you a fully-featured printer OS, but rather only the bare minimum to get a working printer. Hope you find this useful, and let me know what you think.
Lastly, be careful when flashing custom images, as Sovol will void you of your warranty if the printer is broken as a result!!!
Klipper now supports the loadcell probe method. There is NOTHING on the ace that can’t be made to function under 100% mainline.
Download/flash Armbian minimal for BigTree’s CB1 (best H616 distro I know of)
SSH in and install git
Use git to install KIAUH
Use KIAUH to install Klipper, Monraker, Crowsnest, Mainsail and/or Fluidd, and KlipperScreen
Use KIAUH to build and flash firmware to both MCU’s
Rework printer.cfg (and includes) to eliminate Sovol additions and configure loadcell touch functions.
AND there you have it a future proof printer using the NEW (and much improved) input shaper as well as the other Klipper upgrades.
FWIW - Sovol’s GitHub repository of Klipper has not been updated since before the release of the SV07 and is VERY out of date. PLR (power loss recovery) never worked and causes system instability yet the SV08 Max is shipping with the same fork as 2022 era SV07’s.
@sovol3d Your company advertises as “open source”. Why don’t you hire a freelance developer for a couple weeks and release mainline images for ALL your klipper printers? Be less work than fixing your github.
No one is stopping you from developing your own version.
I suppose they can’t do what you suggest because they don’t have enough staff to validate all developments related to their printers and they can’t commit their company to unvalidated software.
Except I don’t have an Ace printer to test with.
I did the process with my SV07. It has a funky display that needed a specific kernel driver (now included in the MKS Armbian source), It was easier due to the removable EMMC module as opposed to the Ace’s soldered down EMMC.
I would really like to try this out, but haven’t dared to flash the MCUs. Is it that simple, you just build the firmware for the two MCUs and flash them using KIAUH?
In theory yes. I can’t say for certain as I don’t have hardware to test.
New mainboard is $69, worst case you have to buy one (and wait on shipping) or you could buy a spare and mod it on the bench. Have to wait to flash the toolhead until new board was installed.
The thing that is most worrisome is there any oddball hardware attached to the H616 that requires a custom kernel. You could use KIAUH’s “change klipper branch” function to get to mainline stock OS.
Right, that’s definitely a worst case scenario I could survive. I just have a couple of prints I need to finish. Maybe I’ll try once I’m done with them. I’ve also contacted support to see if they can provide me with some guidance. I’m not too optimistic about that though, but we’ll see.
Here is a first approximation configuration files for the Ace on mainline.
Generated with the help of AI. I’m POSITITIVE you will have to debug. They are for the ACE not the Plus. They would load/run on the plus but will only allow printing 300x300mm. For the Plus the position_max: would need to be changed for X, Y, and Z steppers.
Just got a reply from support stating that you must use J-link to flash the MCU. This is outside my comfort zone, and I’ll leave this to someone more experienced. But thanks for the support!