Corrected from:
Library L_TF2P_TechModulesFollowingPositioning (from V3.23.0.38)
Update via Easy Package Manager
Response of the new version:
The requested movement (MoveAbsolute, MoveRelative, MoveVelocity) is continued on a falling edge.
What happens?
MoveAbsolute:
- Input scCtrlBasicMotion.xMoveAbsExecute reacts to level change and triggers an error in the MOVEABS state on a falling edge (ErrorID = "NoValidVelocity_MoveAbsolute").
MoveRelative:
- Input scCtrlBasicMotion.xMoveRelExecute reacts to level change and triggers an error in the MOVEREL state on a falling edge (ErrorID = "NoValidVelocity_MoveRelative").
MoveVelocity:
- Input scCtrlBasicMotion.xMoveVelExecute reacts to level change and executes a stop in the MOVEVEL state on a falling edge.
When does the behaviour occur?
After requesting a movement via scCtrlBasicMotion (movement orders MoveAbs, MoveRel and MoveVel), the set input is reset during the movement.
Which products are affected?
Function module L_TF2P_SpeedControlBase from library L_TF2P_TechModulesFollowingPositioning (all versions)
Short-term measures:
Do not reset input until scStatusBasicMotion.xFunDone = TRUE has been set.
Evaluation / recommendations:
-
Automatic Translation
