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