Open sumguysr opened 2 years ago
While the Klipper print time estimator could be integrated directly into Fluidd (using WASM), I think it makes much more sense to have a Moonraker plugin pre-process the files (it makes sense to offload this to the printer host so the browser doesn't get overloaded). I think it would be a great addition, but it needs upstream support first then.
Upstream issue: https://github.com/Arksine/moonraker/issues/481
There's a bunch of useful static GCode analysis that can also be done in the same Moonraker plugin. I'll report back in a couple of weeks.
are there any updates?
@Dreistein75 as far as I'm aware, there has been no changes in Moonraker that would allow this feature.
I'm attempting the plugin route, but with a Python implementation of the estimator. The goal is to also offer more functionality (essentially static analysis tools)
Is your feature request related to a problem? Please describe
Currently Fluidd seems to estimate print times in a very naive and inaccurate way based on percentage printed and the print times estimated by a slicer. It would be great if Klipper Estimator was integrated to evaluate gcode on the current configuration and klipper's kinematics.
Describe the solution you'd like
Add the ability to call Klipper Estimator on any file in the files interface, and add the option to call it it automatically on any file either when it's uploaded or when it's printed.
https://github.com/Annex-Engineering/klipper_estimator
Describe alternatives you've considered
No response
Additional information
Klipper estimator is here, https://github.com/Annex-Engineering/klipper_estimator