L_MC2P MC_CombineAxes: Modulo overflow not intercepted, setpoint jumps occur in sequence (corrected from V01.23.00)
Corrected from: Library: L_MC2P_MotionControlCam (FAST Motion) from V03.23.00.08
Response of new version:
The position will be calculated correctly now, so that the wrong behaviourwill not occur anymore.
What happens?
With FB 'L_MC2P MC_CombineAxes' the movements of two axes (Master1 and Master2) can be combined via addition or subtraction, resulting in a resulting third axis (slave). The sum of the two positions is incorrectly calculated and a position jump occurs if the two master axes are operated in different axis modes. The position jump always occurs at zero crossing with a new modulo clock. Wrongly, the absolute position of the modulo clock is added instead of the difference.
When does the behaviour occur?
Operation of the two master axes in different axis modes. One master axis in 'limited travel' mode and the second in 'modulo' mode.
Which products are affected? Library: L_MC2P_MotionControlCam (FAST Motion)
Short-term measures, Evaluation/Recommendations:
Run both master axes in the same axis mode, either both in modulo or both limited.
