So I've been referencing a lot of code in RSLogix and have noticed something that I would like to have cleaned up.
The implementation of a virtual axis essentially allows you to send motion instructions to a virtual axis that responds exactly how you want it to. However, I've noticed that a lot of other physical axes reference this virtual axes.
Now I'm working on a design that featuring two axes: one that winds and one the rewinds. I was intending to gear the two axes together to control a specific winding tension, but I'm curious as to whether or not it is better to gear both axes to a virtual master, because that is what I've seen done before.
So my question is, is gearing an axis to a virtual master generally better practice? Is there any reason to not gear together two physical axes? What is the general advantage of have a master virtual axis instead of simply defining a physical axis as the master axis for a machine?
The implementation of a virtual axis essentially allows you to send motion instructions to a virtual axis that responds exactly how you want it to. However, I've noticed that a lot of other physical axes reference this virtual axes.
Now I'm working on a design that featuring two axes: one that winds and one the rewinds. I was intending to gear the two axes together to control a specific winding tension, but I'm curious as to whether or not it is better to gear both axes to a virtual master, because that is what I've seen done before.
So my question is, is gearing an axis to a virtual master generally better practice? Is there any reason to not gear together two physical axes? What is the general advantage of have a master virtual axis instead of simply defining a physical axis as the master axis for a machine?