On 10/8/14 9:01 AM, Schooner wrote: > First Q > > From Axis > > File > Properties > > Brings up the properties of the currently loaded gcode including > estimated run time > > Always underestimates as it takes no account of time used in > acceleration and deceleration to/from the required Feed speed
Yep, the estimate is off. It's based on the gcode only, and does not take into account important things like machine acceleration and spindle acceleration as you say, as well as things like tolerance (G64 P) and probing. The only way I can think of to improve the estimate would be to run the motion controller, disconnected from actual motion, and see how long the motion actually takes. That's probably possible, but it's not a small change to design & implement. -- Sebastian Kuzminsky ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
