- Posts: 175
- Thank you received: 0
Where the stepgen getting it's input from ?
2 years 1 month ago #309878
by PhilipME
Where the stepgen getting it's input from ? was created by PhilipME
Is the stepgen getting its input from the g-code from the ngc file/mdi commands?
and where does that take place?
Thanks
and where does that take place?
Thanks
Please Log in to join the conversation.
- Todd Zuercher
- Offline
- Platinum Member
-
Less
More
- Posts: 4739
- Thank you received: 2
2 years 1 month ago #309928
by Todd Zuercher
Replied by Todd Zuercher on topic Where the stepgen getting it's input from ?
it is somewhat complicated. The stepgens do not get their position commands directly from the g-code. There are a few layers in between.
One of the motion planners (there is more than one) sends the commands for movement to the kinematics model, that then sends the joint position commands either directly to or via a PID loop to the stepgen. (I understand that the motion planner used for jogging isn't the same as the one used for program execution.)
The motion planner reads the G-code, calculates what the current commanded position should be and adds required offsets, before sending the axis positio commands to the Kinematics program.
After the Kinematics program translates the axis positions to joint positions, then any additional joint offsets will be added (such as home offsets.
One of the motion planners (there is more than one) sends the commands for movement to the kinematics model, that then sends the joint position commands either directly to or via a PID loop to the stepgen. (I understand that the motion planner used for jogging isn't the same as the one used for program execution.)
The motion planner reads the G-code, calculates what the current commanded position should be and adds required offsets, before sending the axis positio commands to the Kinematics program.
After the Kinematics program translates the axis positions to joint positions, then any additional joint offsets will be added (such as home offsets.
Please Log in to join the conversation.
Time to create page: 0.073 seconds
