What about iteration averaging? I am not suggesting this for one off gcodes, but rather production run gcode.
First run, populate a statistics file with estimated run time. This time would be used for total time on status bar versus current run time. After the first run, the actual time would replace the estimated time in the file. On each successive run, the actual time for the given run would be added to the statistics file. Then you could develop more realtime run times for the given part. You could then run all the statistics of the successive runs (SD, Var, Covar,....). Over time, you should then be able to use these files to monitor the performance of the machine tool and its components. Just a thought.... Brian ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
