fluidd
fluidd copied to clipboard
fluidd-core
Feature Request: ADXL Support in Fluidd
Copy of issue #190 at Moonraker since both Moonraker and interface need to support it.
Since Klipper introduced input shaper we're all using adxl's to calibrate this function and our printers rigidity.
But the proces to do so is really tedious.
- Calibrate
- ssh in
- use script to create images
- SFTP in
- Copy image to pc
- open image
- Repeat steps 1-6 until you're happy with the result
- Save wanted values in klipper.cfg
Would be an awesome QOL improvement if we could do this through Fluidd/Moonraker just like the height map.
Hey, this is a decent idea - and is on the list, but is behind some other priorities for the moment. Thanks!
Though I do like this idea, Klipper now provides the SHAPER_CALIBRATE command that will run the auto-tuning for the input shaper directly from Klipper and suggest some parameters from the measurements. After that, all the use needs to do is SAVE_CONFIG to get it applied.
So yes, this is a good idea for QoL improvement, but in reality Klipper now has a better solution for that!
Closing this because of staleness, feel free to re-open if this is still an ongoing issue.
@matmen Sorry for not responding sooner.
Pedro his comment actually had not much influence on the topic, SHAPER_CALIBRATE already existed when I first opened this feature request but only comes after what I described
SHAPER_CALIBRATE doesn't show anything about the printer, so when actually tuning it you want to use the manual process, because then you can see the result of your tuning and if more tuning is needed. (Things like belt tension have a lot of influence on input shaper.)
SHAPER_CALIBRATE Just uses the settings it thinks is best but doesn't do anything about potential hardware issues.
Considering this requires installing packages as well as running shell scripts, I don't think this is feasible at this point. Fluidd has no means of running any shell commands, so support in Moonraker is needed for this (as you already stated in your issue description). I'll move this to the backlog and I'll let you know if something changes (i.e. Moonraker adds this as a feature). Thanks for your FR!