wispy tulip
The time estimations for duration and ETA (I see on KlipperScreen) is horribly off at the beginning of the print. (9h for a 2h print)
Now I am wondering how this could be improved.
One idea was to just use the times provided by the slicer.
But checking the mainsail config "Slicer" is only available for
"Print progress calculation" and "ETA calculation".
Is this more a question of what to show on KlipperScreen?
Or what are the options?
abstract shell
Thats my setup
So I do not show ETA as also for my the slicer is the most acurate
wispy tulip
Hm. But isn't ETA just = start_time + estimated_time?
abstract shell
I would need to start a print now to show you how that looks, but no ETA = (estimated time + slicer time)/2
Slicer is always shown and the estimated time could run other variables. Any of the times could fit your print best depending how well your slicer is tuned
Estimated time is only a other visible time that you can choose from the possible options
And honestly I never looked what Klipperscreen uses, there is no common agreement between the different moonraker based UIs
wispy tulip
In my mind estimated time is made up of e.g. slicer and file progress etc. (similar to the (estimated time + slicer time)/2)
But the ETA would be a fix start_time + estimated_time.
Apparently that is not how it works.
But to me it would make more sense.
I'll give your setup a go and report back if that improves things for me.
inland notch
Is it possible to make a macro that would output similar time estimate as the one calculated by Mainsail without having access to the gcode metadata to the display? (not klipperscreen)
Does mainsail access such information (ex current_file.gcode_start_byte) from moonraker? Haven't seen documents that explain how to access Moonraker info with gcode. (without using annex engineer klipper_estimate)