Corrected from:
Library L_TW2P_WindingTraversing (from V03.25.00)
(Update via Easy Package Manager)
Response of the new version:
The status eTMState is plausibly displayed.
What happens?
Although the status with eTMState = DANCERCTROL or also LINEJOGGING signals an operation, the axis remains at standstill. No setpoints are generated.
When does the behaviour occur?
Initial situation: eTMState = DANCERCTROL; 'normal operation'.
With an interruption due to an error, the change to the error state occurs as expected: eTMState = ERROR.
After removing the cause of the error and xResetError = TRUE, eTMState changes back to DANCERCTROL, but no setpoints are generated.
The status display therefore does not reflect the operating status.
If the LINEJOGGING is interrupted, the same thing happens.
Which products are affected?
Function module L_TW2P_WinderDancerCtrlState from library L_TW2P_TechModulesWindingTraversing
Short-term measures:
In the error state eTMState = ERROR, all requirements of an operating mode such as DancerControl, Jogging,... should first be reset (xDancerCtrl = FALSE).
After the error reset, any mode can then be started again.
Evaluation / recommendations:
This is only a diagnostic limitation. A practicable applicative remedy is available.
Automatic Translation
