Run time calculation in g-code program properties

More
15 years 2 weeks ago #13934 by kostas
I wonder how EMC calculates the run time shown in g-code program properties. It's always far less than the actual run time required.
Seems that it's usually half the actual time, but I can't figure this out exactly.

Please Log in to join the conversation.

More
15 years 2 weeks ago #13948 by BigJohnT
It only sums the time to make the moves and does not take acceleration/deceleration into account which would make the actual timelonger.

John

Please Log in to join the conversation.

More
15 years 2 weeks ago #13951 by kostas
This explains it. You know if there are any plans on making this calculation less fictional?

Please Log in to join the conversation.

More
15 years 2 weeks ago #13953 by BigJohnT
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

Please Log in to join the conversation.

More
15 years 2 weeks ago #13954 by kostas
I understand. I think that at least taking into account the acceleration / deceleration would be something good.
I don't think I'm up to it with the development skills I have, but I'll take a look at the source code anyway and see if I could make any improvements.

Please Log in to join the conversation.

More
15 years 2 weeks ago #13955 by BigJohnT
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

Please Log in to join the conversation.

More
11 years 9 months ago #54452 by Tomasz_K

BigJohnT wrote: 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


HI
Is there any progress in the development of a more accurate time calculation?

Tom

Please Log in to join the conversation.

More
11 years 9 months ago #54463 by BigJohnT
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

Please Log in to join the conversation.

More
8 years 8 months ago #105395 by kibo
Can I see run time calculation value in the Axis GUI?
If not, is it possible to create Python Virtual Control Panel widget to show this value?
Thanks.

Please Log in to join the conversation.

More
8 years 8 months ago #105403 by Todd Zuercher
If you want a run timer that is easily done with a VCP. A run time estimator would be difficult and there is already one built into Axis.

There are example configurations look up the man for time.9 it has example pyvcp code.
linuxcnc.org/docs/html/man/man9/time.9.html

Please Log in to join the conversation.

Time to create page: 0.097 seconds
Powered by Kunena Forum