×
Forum Header
MAX_LINEAR_VELOCITY in [TRAJ]
30 Mar 2014 21:47 - 30 Mar 2014 21:49 #45418
by newbynobi
MAX_LINEAR_VELOCITY in [TRAJ] was created by newbynobi
Hallo,
stepconf does create a entry MAX_LINEAR_VELOCITY in [TRAJ], this should not be there!
It causes problems with gmoccapy glade file and according to the documents:
TRAJ Section
There shouldn't exist this entry, but a MAX_Velocity instead.
Norbert
stepconf does create a entry MAX_LINEAR_VELOCITY in [TRAJ], this should not be there!
It causes problems with gmoccapy glade file and according to the documents:
TRAJ Section
There shouldn't exist this entry, but a MAX_Velocity instead.
Norbert
Last edit: 30 Mar 2014 21:49 by newbynobi.
Please Log in or Create an account to join the conversation.
30 Mar 2014 22:33 #45420
by mariusl
Regards
Marius
www.bluearccnc.com
Replied by mariusl on topic MAX_LINEAR_VELOCITY in [TRAJ]
I concur with Norbert who just beat me to reporting it 
Regards
Marius
www.bluearccnc.com
Please Log in or Create an account to join the conversation.
31 Mar 2014 01:50 #45426
by cmorley
Replied by cmorley on topic MAX_LINEAR_VELOCITY in [TRAJ]
Yes looks like they should be in the [DISPLAY] section instead.
Chris M
Chris M
Please Log in or Create an account to join the conversation.
31 Mar 2014 02:33 #45427
by cmorley
Replied by cmorley on topic MAX_LINEAR_VELOCITY in [TRAJ]
In a little close inspection it seems some of our sample configs are mixed up too.
I'm working on a patch for stepconf in master.
Chris M
I'm working on a patch for stepconf in master.
Chris M
Please Log in or Create an account to join the conversation.
31 Mar 2014 05:47 #45436
by andypugh
Unfortunately is is hard to be sure that no config or file or component anywhere isn't relying on any particular INI entry.
Though searching the entire code tree for [TRAJ] and MAX_LINEAR_VELOCITY in all the possible formats (such as the Python INI file format would be a good start to seeing if it is as truly redundant as we think.
Alternatively one could just take the view that if it isn't in the docs then it can be freely changed
Replied by andypugh on topic MAX_LINEAR_VELOCITY in [TRAJ]
In a little close inspection it seems some of our sample configs are mixed up too.
Unfortunately is is hard to be sure that no config or file or component anywhere isn't relying on any particular INI entry.
Though searching the entire code tree for [TRAJ] and MAX_LINEAR_VELOCITY in all the possible formats (such as the Python INI file format would be a good start to seeing if it is as truly redundant as we think.
Alternatively one could just take the view that if it isn't in the docs then it can be freely changed
Please Log in or Create an account to join the conversation.
31 Mar 2014 09:55 #45448
by cmorley
Replied by cmorley on topic MAX_LINEAR_VELOCITY in [TRAJ]
putting our docs and samples in line and correct seems a good thing to do.
We need to audit the docs and the configs - I made a bug report.
For instance axis.ini sets MAX_VELOCITY in the [AXIS] sections to 5 but sets MAX_LINEAR_VELOCITY in the [DISPLAY] section to 1.2
which limits the axes to 1.2 IPS. The docs imply the setting is for max jog velocity which is apparently wrong.
It's been mixed up for a long time and should be fixed.
Breaking things on a major update is acceptable - but I bet it wouldn't break much at all.
Chris M
We need to audit the docs and the configs - I made a bug report.
For instance axis.ini sets MAX_VELOCITY in the [AXIS] sections to 5 but sets MAX_LINEAR_VELOCITY in the [DISPLAY] section to 1.2
which limits the axes to 1.2 IPS. The docs imply the setting is for max jog velocity which is apparently wrong.
It's been mixed up for a long time and should be fixed.
Breaking things on a major update is acceptable - but I bet it wouldn't break much at all.
Chris M
Please Log in or Create an account to join the conversation.
Time to create page: 0.094 seconds