hoax portrayed in the current track axis
22 Mar 2011 19:59 #8005
by PCW
Replied by PCW on topic Re:hoax portrayed in the current track axis
I was just suggesting looking a a worrking configuration as you had a
incorrect 0 FF1 term (which is required for correct velocity mode response)
incorrect 0 FF1 term (which is required for correct velocity mode response)
Please Log in or Create an account to join the conversation.
22 Mar 2011 20:15 #8006
by andypugh
Replied by andypugh on topic Re:hoax portrayed in the current track axis
Are you talking about this (fixed) problem?
sourceforge.net/tracker/?func=detail&ati...018318&group_id=6744
git.linuxcnc.org/gitweb?p=emc2.git;a=com...68f66ee857324a43634c
sourceforge.net/tracker/?func=detail&ati...018318&group_id=6744
git.linuxcnc.org/gitweb?p=emc2.git;a=com...68f66ee857324a43634c
Please Log in or Create an account to join the conversation.
22 Mar 2011 20:26 #8007
by andypugh
Replied by andypugh on topic Re:hoax portrayed in the current track axis
Are you saying that the problem is that the backplot shows commanded position, not actual position?
I think that was a design choice.
The way to tune PID is with HALscope. Axis Preview is only intended to show the program, and the progress through the program.
I think that was a design choice.
The way to tune PID is with HALscope. Axis Preview is only intended to show the program, and the progress through the program.
Please Log in or Create an account to join the conversation.
22 Mar 2011 20:42 #8008
by radekB
Replied by radekB on topic Re:hoax portrayed in the current track axis
andypugh wrote:
Why? The servo and generally everywhere, everyone can see the real tool path. Why watch it on the theoretical calculation?? When do I have a real feedback from the physical components?
Radek
Axis Preview is only intended to show the program, and the progress through the program.
Why? The servo and generally everywhere, everyone can see the real tool path. Why watch it on the theoretical calculation?? When do I have a real feedback from the physical components?
Radek
Please Log in or Create an account to join the conversation.
22 Mar 2011 21:05 #8009
by andypugh
Replied by andypugh on topic Re:hoax portrayed in the current track axis
I didn't make the decision, so I don't know.
It might be so that servo-jitter does not mean that the backplot is constantly replotting, and making the lines fuzzy.
It probably isn't meant as a diagnostic tool, more a progress-indicator. Some of the GUIs have no preview at all.
It might be so that servo-jitter does not mean that the backplot is constantly replotting, and making the lines fuzzy.
It probably isn't meant as a diagnostic tool, more a progress-indicator. Some of the GUIs have no preview at all.
Please Log in or Create an account to join the conversation.
22 Mar 2011 21:13 - 22 Mar 2011 21:55 #8010
by mduzi
Replied by mduzi on topic Re:hoax portrayed in the current track axis
I think that is correct solution when drawing-tool-position same like position on the text display...
...and then command act / comm is switch for monitoring between joint-cmd-pos and joint-fb values.
is it true?
...and then command act / comm is switch for monitoring between joint-cmd-pos and joint-fb values.
is it true?

Last edit: 22 Mar 2011 21:55 by mduzi.
Please Log in or Create an account to join the conversation.
22 Mar 2011 23:18 #8013
by BigJohnT
Replied by BigJohnT on topic Re:hoax portrayed in the current track axis
The Axis backplot is not real time so it will not show the exact position of each path. CPU's that are heavily loaded will be father off than others. Generally everywhere the backplot is not drawn in real time and may not follow the programmed path exactly.
John
John
Please Log in or Create an account to join the conversation.
23 Mar 2011 08:54 - 23 Mar 2011 10:02 #8023
by mduzi
Replied by mduzi on topic Re:hoax portrayed in the current track axis
I disagree with BigJohn 
Logger object in emc.lib recorded by a separate timer coordinates. Although not in real time but the period can be very small 0.01 can be smaller
So the recording time is not an expensive time for display CYCLE_TIME! and therefore it is ok

Logger object in emc.lib recorded by a separate timer coordinates. Although not in real time but the period can be very small 0.01 can be smaller
So the recording time is not an expensive time for display CYCLE_TIME! and therefore it is ok

Last edit: 23 Mar 2011 10:02 by mduzi.
Please Log in or Create an account to join the conversation.
Time to create page: 0.094 seconds