L_MC1P: BufferMode does not work as documented (corrected from V03.21.00)
Corrected from: Library: L_MC1P_MotionControlBasic (FAST Motion) from V03.21.00.102 (Update via Package-Manager)
Response of the new version:
L_MC1P: The BufferMode works now, as like described in the documentation.
What happens?
L_MC1P: BufferMode does not work as documented. A first instance of FB MoveAbsolute incorrectly positions e.g. not to a negative end speed of -20, but to the positive end speed of 20. The speed changes briefly from -20 to 20 and back to -20 before continuing.
When does the behaviour occur? With a first instance of FB MoveAbsolute, for example, the positioning is changed from 200 to 100 units. Meanwhile the second instance of FB MoveAbsolute is started via the Execute input, in buffer mode mcBlendingLow with the target position zero. The first instance must end the movement at position 100 from a negative speed. The second instance should take over the motion control starting at 100 units with a constant velocity, which is present at input Velocity (e.g. 20) of the second instance.
Which products are affected? Library: L_MC1P_MotionControlBasic (FAST Motion)
