Is anyone running mainline klipper on their Ace?
I’m considering adapting an Ace toolhead to another Klipper printer specifically for the “touch to Zero” Z offset function.
As far as I can tell [kx711] is a custom function. Mainline has support for the hx711 but only INSIDE the [loadcell] function.
Indeed, Sovol seems to have some custom code for this. As far as I can tell, it’s open-sourced on their GitHub, but not upstreamed to mainline unfortunately. 
Separately, there seem to have been various investigations into loadcell probing for Klipper over the past few years. Last I checked, someone has been making good progress (slow, but that’s understandable)… but actually looks like you found that thread too. 
Yah spent 4 hours yesterday reviewing a 3 year thread at klipper/discussions.
At this point it seems the only way to make this work is to manually copy the entire printer_data folder from the SV06Ace repo then copy all the [extra_mcu] stuff into my printer.cfg and hope it gets loaded far enough to give me enough error messages to debug the whole mess.
THEN Sovol will do an OTA update but “forget” to update the repo leaving me to beg a copy of [printer_data] on here.
Ah yup. I’d love to get the ACE onto mainline Klipper, but I’m not very knowledgeable about Klipper yet, and anyway I wouldn’t want to give up the loadcell probe (which, though not as repeatable as I’d like, is good enough, and extremely convenient).
Speaking of OTA updates, do you know if anyone ever figured out where they’re fetched from and what files they update? I feel like I saw someone say they just download and install a deb package that overwrites the Klipper config files, but I can’t find that post (or maybe it was on Discord).
This is probably a “me problem”, but it really bugs me that reverting to stock config is so difficult on the ACE. Theoretically these instructions should put it back to a like-new software configuration, but I really wish they’d gone with a mainboard with an SD slot, or at least a socketed EMMC. (I like to mess around with my devices, and being able to blow away my mistakes and go back to a known-good config is really nice.)
SSH into the Ace. What version of Armbian is it running? The mainboard is actually 2 devices from a software point of view, the SPC (Pi) and the MCU board.
There IS a testing branch of Klipper available at Github. Will enable using the loadcell as a probe during bed mesh measurement. Warning these features are still in ALPHA testing
If I understand correctly you should be able to SSH into your Ace and use kiauh to uninstall klipper then change the repo in kiauh and reinstall Klipper. You’ll have to manually install numpy and scipy. The base OS on the SBC remains intact.
Many changes to printer.cfg
Indeed, KIAUH is present. If I were brave enough, I’d be tempted to try it, but I’m not that brave at this time. I am, overall, enjoying the ACE as a printer, and I don’t want to mess it up in a way that might take me some time to get out of. It’s not so much the base OS I’m worried about, but that Sovol seems to have deployed from a “dirty” Klipper repo, and while I appreciate them having their modified code on GitHub, I am not 100% confident that it’s the same as what they shipped.
I’d feel way more comfortable if they had some kind of swappable storage, or else if the process to completely reflash the Linux EMMC was a bit clearer.
If the ACE was a “project printer” for me instead of my main printer, I’d probably be looking into a mainboard swap instead. More of a traditional setup with a a “dumb” Klipper MCU and a Pi (or similar) SBC with its own power supply for the Linux side.
