L_MC1P_PolePositionIdentification: Drive does not move, depending on call sequence (fixed 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:
The execution of Motion FBs is now possible independently of the xEnable of the FB L_MC1P_PolePositionIdentification and independently of the processing sequence.
What happens?
L_MC1P_PolePositionIdentification: Ist der Funktionsbaustein freigegeben, kann keine Motion-Funktion ausgeführt werden.
When does the behaviour occur?
- Execution of the FB 'L_MC1P_PolePositionIdentification' ist released (xEnable = True).
- FB L_MC1P_PolePositionIdentification is in the call sequence before the motion function.
Which products are affected?
Library: L_MC1P_MotionControlBasic (FAST Motion)
Short-term measures, Evaluation/Recommendations:
Motion functions can be executed if the L_MC1P_PolePositionIdentification is placed at the end of the call sequence of the FBs. Alternatively the motion functions can also be executed if the FB L_MC1P_PolePositionIdentification is deactivated after the execution of the polling identification (xEnable = False).
