The offset for the torque via the attack points AP_lrSetTorqueOffest > 0 and AP_xSetTorqueOffset = TRUE is taken over as soon as the axis is released and a function such as winding is activated.
What happens?
The offset for the torque is not taken over via the attack points AP_lrSetTorqueOffest > 0 and AP_xSetTorqueOffset = TRUE.
When does the behaviour occur?
An offset to the torque from the application is requested via the attack points. For this the attack points are used: - AP_xSetTorqueOffset = TRUE - AP_lrSetTorqueOffest > 0
Which products are affected?
Library: L_TW2P_TechModulesWindingTraversingV03.21.00 Function bloc: L_TW2P_WinderDancerCtrlState (TM Winder Dancer-controlled)
Short-term measures:
The function block L_MC1P_SetTorqueOffset can be used for switching on the torque offset. This FB can be used to specify an additional pilot torque cyclically.
Evaluation / Recommendations:
With the L_TW2P_WinderDancerCtrlState technology module, it is not possible to pre-control the torque via the attack points. Taking the short-term measure into account, the torque can be pre-controlled in the application via an additional function module.
