Run time calculation in g-code program properties
15 Oct 2011 13:11 #13934
by kostas
Run time calculation in g-code program properties was created 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.
Seems that it's usually half the actual time, but I can't figure this out exactly.
Please Log in or Create an account to join the conversation.
16 Oct 2011 14:23 #13948
by BigJohnT
Replied by BigJohnT on topic Re: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
John
Please Log in or Create an account to join the conversation.
16 Oct 2011 15:48 #13951
by kostas
Replied by kostas on topic Re:Run time calculation in g-code program properties
This explains it. You know if there are any plans on making this calculation less fictional?
Please Log in or Create an account to join the conversation.
16 Oct 2011 17:24 #13953
by BigJohnT
Replied by BigJohnT on topic Re:Run time calculation in g-code program properties
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
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 or Create an account to join the conversation.
16 Oct 2011 18:40 #13954
by kostas
Replied by kostas on topic Re:Run time calculation in g-code program properties
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.
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 or Create an account to join the conversation.
16 Oct 2011 18:48 - 16 Oct 2011 18:50 #13955
by BigJohnT
Replied by BigJohnT on topic Re:Run time calculation in g-code program properties
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
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
Last edit: 16 Oct 2011 18:50 by BigJohnT.
Please Log in or Create an account to join the conversation.
01 Jan 2015 00:48 #54452
by Tomasz_K
HI
Is there any progress in the development of a more accurate time calculation?
Tom
Replied by Tomasz_K on topic Re:Run time calculation in g-code program properties
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 or Create an account to join the conversation.
01 Jan 2015 22:57 - 01 Jan 2015 23:19 #54463
by BigJohnT
Replied by BigJohnT on topic Re:Run time calculation in g-code program properties
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
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
Last edit: 01 Jan 2015 23:19 by BigJohnT.
Please Log in or Create an account to join the conversation.
04 Feb 2018 12:29 #105395
by kibo
Replied by kibo on topic Run time calculation in g-code program properties
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.
If not, is it possible to create Python Virtual Control Panel widget to show this value?
Thanks.
Please Log in or Create an account to join the conversation.
- Todd Zuercher
-
- Offline
- Platinum Member
-
Less
More
- Posts: 4965
- Thank you received: 1370
04 Feb 2018 14:45 #105403
by Todd Zuercher
Replied by Todd Zuercher on topic Run time calculation in g-code program properties
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
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
The following user(s) said Thank You: kibo
Please Log in or Create an account to join the conversation.
Time to create page: 0.215 seconds