Corrected from:
Library: L_TW2P_TechModulesWindingTraversing (from V.25.0)
(Update via Easy Package Manager)
Response of the new version:
The identification is started with the order from the STANDBY state, regardless of previous events.
What happens?
The identification cannot be started from the STANDBY state.
Affected
- Diameter identificaiton
- Mesh Inertia Identifier
- Frictional identificaiton.
When does the behaviour occur?
If the same identification was previously interrupted via the controller lock and change to the error state.
Which products are affected?
Function module L_TW2P_WinderDancerCtrlState and L_TW2P_WinderTensionCtrlState from library L_TW2P_TechModulesWindingTraversing
Short-term measures:
After restarting the identification after acknowledging the error state, the TM switches to the error case again. With the second acknowledgement of the error state, the identification is initialised again. Now the identification can be started from the STANDBY state and acknowledging the error twice.
Evaluation / recommendations:
The identification should be started immediately with the first job. However, the identification is not initialised cleanly if it is interrupted by an error condition of the TM. Taking the short-term measure into account, the described behaviour can be avoided.
Automatic Translation
