A suggestion, could we get an estimated run time? once the g code is generated, it should be possible to use the feed rate and path length to display how long the code would take to run. I know it can’t be 100% accurate, but it would be nice to know if i have time to run a job before bed time.
thanks
Code estimate can be precise if it models your system accurately. The problem is different machines have different max speeds and accelerations. Motion controller may change from machine to machine too.
Having said that, Camotics software can give you a rough estimate of gcode file.
Sort of my fault, the fork I maintain does have estimations displayed (they are generated by upstream, but not displayed).
Look at the info panel below the simulation slider bar..
This isnt /terribly/ helpful if you are using upstream, but it is a feature that can be delivered/ Maybe try my fork:
The estimator in laserWeb attempts to do this; using the configured values for the attached machine, It basically ‘runs’ the gcode (in a subprocess after generation) and calculated the cumulative (estimated) time in a table that is then used by the ‘simulate’ slider to show progress accurately; and summarised in the info box on my fork.