I’m playing around with my ACE a little bit more, and enjoying it a lot
A question: I find that sovol used mostly stock moonraker and mainsail components. Moonraker is version 0.9.0 from the standard repo, mainsail is 2.12.0 and also from the standard repo. Both installs are slightly behind the publicly available version. For mainsail, the timelapse module (from the public / standard moonraker-timelapse repo) has been, oddly, included in the mainsail directory tree (and this is a difference with the standard install, I think).
I like playing around with my tech, and want to update moonraker, mainsail, and possibly included/related components as well. I will not touch klipper-mcu, but would love to be able to update klipper as well.
Is it safe to use kiauh (already on the printer) to update the publicly available components? What can I safely update, and what should I not touch?
I haven’t looked at moonraker or mainsail. But I can tell you that you cannot just upgrade klipper itself. Sovol has added a module for the weight sensor that isn’t in klipper mainline.
I noticed that as well. There has been some conversations about that sensor (hx711 if i recall correctly, which is a pretty standard ADC for load cells) on the klipper github. I even seem to remember there was some support built. I’m not comfortable enough yet with the SV06 ACE to try that out, but I would like to be able to run stock klipper at some point.
In the mean time @sovol3d can maybe comment on upgrading mainsail and moonraker etcetera? Is it safe?
In the mean time @sovol3d can maybe comment on upgrading mainsail and moonraker etcetera? Is it safe?
@sovol3d would you please be so kind to respond to this? You are selling the printer as an open source printer, but the open source parts are not available.
FWIW, I am a total Klipper newbie, but I’ve been following this thread on the Klipper forum with great interest. It seems like there is slow-but-steady development going on for “proper” loadcell support (including calibration of the loadcell, which might help with the repeatability issues some folks have noticed?). Of course it’d be awesome if Sovol could contribute towards those efforts, but if not, I’m hopeful that a swap to mainline Klipper will be practical down the road…
Granted, Sovol’s default, slightly customized Klipper setup has worked well for me so far, but there are still reasons it’d be nice to upgrade. For example, I’ve been wanting to try OrcaSlicer’s adaptive pressure advance, but there was a Klipper bug fixed middle of last year that conflicts with it. IIRC, the timing of the fix seemed pretty close to when it looks like Sovol last synced started their fork for the ACE. I keep meaning to check more specifically if the bugfix is there or not… but it’d awesome in the future to be able to just upgrade Klipper “normally” instead.
I was not aware of that klipper effort, thanks! For me it also has been working OK, but there is desync happening between the Sovol klipper and the open source one (you highlighted two things that would really contribute to the functionality of the printer!).
Next to that one of the main selling points to not get a bambu was the ‘open’ nature. It’s quite a dissapointment that this seems to be incorrect. I hope @sovol3d corrects this situation (most probably in discussion with MKS) so we can see similar success and community compared to the ‘old’ SV06.
@sovol3d another reminder. Can you please update us on the status of the open source code for the SV06 ACE ? Just for clarity, this is what you state on the product page:
At the moment this is not the case. For me as well for others, this is one of the main reasons to not get a bambu printer. Please give this some priority.
In my opinion, using the HX711 sensor for ABL is not viable, it’s not reliable enough to use it for bed leveling… Since it is normally used for filament matters. That’s why if you look at @sovol3d official profiles the first layer (for 0.4 nozzle) with a height of 0.25mm, I guess to compensate the load cell errors.
I have been talking to them directly and they are already working on “fixing” the current implementation, I am also trying to get a load sensor to “help” the development and calibration of it.
Meanwhile I am adjusting the current model of the printer to use Klicky, combining it with the load sensor for the z-offset calculation.
