I know that the time remaining function has been raised before, and I have raised it within the context of the Vortex. I don’t see a thread in gSender 1.6.4 though.
I ran the first job on my Mk3 today - a surfacing job using the gSender surfacing module. The count down timer hit 0% when the job had something less than half to run. The clock stalled at 95% with 0 time remaining. The job ran for another 10 minutes by the Windows clock.
I did not use the feed rate slider or change the feed rate in any way.
It’s a factor of smaller files that get entirely sent+planned early on but take some time to run (the long movements in surfacing)
We have some improvements for this and general time estimation coming in the next Edge release - we have some changes for incredibly accurate estimation (within a few seconds between estimate and actual cut time) and fixes for how we show remaining estimates on shorter files with long movements like a surfacing file.
Some sample data as we run test files - a few data points with the new algorithm:
