Library: L_MC1P_MotionControlBasic (FAST Motion) V03.18.00.252
(update via Package Manager)
Response of the new version:
Executing the MC_SetPosition FB no longer changes the target position.
What happens?
If the MC_SetPosition FB is used to change the setpoint and the actual position in an active positioning process, the target position of an absolute positioning process is changed by mistake.
When does this behaviour occur?
The behaviour occurs when using the MC_SetPosition FB in an active absolute positioning process.
Example:
- Absolute positioning is started with target position = 1000 units.
- When the position of 400 units is reached, the MC_SetPosition FB is used to set the position to 0.
Expected behaviour: Setpoint and actual position are set to"0" and the target position remains 1000. Positioning is completed as soon as the target position of 1000 units has been reached.
Actual behaviour: Setpoint and actual position are set to "0". The target position is, however, changed by 400 units to 600 units. For this reason, the drive is not at 1000, but at 600 units after completion of positioning.
Which products are affected?
Library: L_MC1P_MotionControlBasic (FAST Motion)
Short-term measures, Evaluation/recommendations:
Restart absolute positioning, after executing the MC_SetPosition FB.
Automatic translation
