Run time calculation in g-code program properties

It only sums the time to make the moves and does not take acceleration/deceleration into account which would make the actual timelonger.

John

I don't know of anything in the works, the number is an exact time for each move less the things listed below.

Short of running the g code on a sim with my timer component to get exact time you would pretty much have to duplicate the trajectory planner and a whole bunch of other code I assume to get exact times due to the many factors involved which include the naive cam detector which may combine short lines and arcs into one and the G61/64 setting among others as well as the acceleration and max velocity of each axis.

John

It starts on line 1693 of / src/emc/usr_intf/axis/scripts/axis.py

LOL, at least I can find it...

Dunno if this line is a clue to getting the acceleration values

mf = vars.max_speed.get()

But if they are different... that would get complicated pretty fast.

John

To my knowledge no one is working on this as accurate time calculations can be arrived at by running a sim with the exact same configuration as the machine. Of course your welcome to work on it.

The time component will give you the run time when you run a file.

www.linuxcnc.org/docs/html/man/man9/time.9.html

JT