Originally shared by John Lauer
How good is ChiliPeppr’s time estimator? Just ran a job that was over an hour. CP over-estimated by 8 minutes. Not bad for an hour long job. BTW, this is a new feature released today in the Gcode widget.
Originally shared by John Lauer
How good is ChiliPeppr’s time estimator? Just ran a job that was over an hour. CP over-estimated by 8 minutes. Not bad for an hour long job. BTW, this is a new feature released today in the Gcode widget.
Super sweet. I need to try this out asap. Most of my job is 12 hours plus. This would let me know if I should go to sleep or not.
that estimated remaining will be super useful
For some nerd details, the time estimate is created by the 3D viewer, not the Gcode widget. That’s because the 3D viewer knows the length of each line because it has to calculate it for the 3D view. It measures the distance of each line as it renders and it calculates that against the feedrate for that line. It then adds 25% to that line’s time calculation as a guess based on acceleration and deceleration adding seconds/milliseconds. That’s why it overestimates, but it gets it really close. Closer than I’ve seen anywhere else. To make it exact would require applying the planner buffer algorithm the CNC controller uses, which is a lot of work and probably not worth it.
I’ve never had any estimated time to completion given by man or machine come out precisely 