Corrected from:
Library: L_TT1P_TechnologyModules_LM (from V3.23.0)
Update via Easy Package Manager.
Behaviour of new version:
The function xHalt can be assigned together with the active function of the vibration compensation (xOscComp = TRUE).
What happens?The TM L_TT1P_StackerCraneAxisControl reports the error eErrorID = 19810 (ChangeOfOscCompModeLocked).
When does the behaviour occur?
If the xHalt function is activated during a movement and the vibration compensation function is switched to active (xOscComp = TRUE)
Which products are affected?
Function block L_TT1P_StackerCraneAxisControlbase from library L_TT1P_TechnologyModules_LM (from V3.20.0)
Short-term measures:
During execution of the xHalt function, the AP3 and AP4 points of attack should be activated:
- AP03_xOscCompPosScaled = TRUE with AP03_lrOscCompPosScaled := scSignalFlow.MP02_lrOscCompPosScaled
- AP04_xOscCompLoadScaled = TRUE with AP04_lrOscCompLoadScaled := scSignalFlow.MP01_lrOscCompLoadScaled
In the READY state the attack points can be deactivated again:
- AP03_xOscCompPosScaled = FALSE
- AP04_xOscCompLoadScaled = FALSE
Evaluation/Recommendations:
Taking into account the short-term measure, the error state is no longer switched under the given condition. Thus, the function "stop" in combination with the function of vibration compensation is given.
Automatic Translation