Remedied from:
ECS Posi&Shaft V2.0 onwards
Behaviour of the new version ?
After ProfEnable=0 aborts a profile with TP positioning, the TP input no longer responds nor stops correctly during the deceleration ramp.
What happens?
After ProfEnable=0 aborts a profile with TP positioning, upon detection of a TP signal, TP positioning continues and the residual path is executed.
When does the problem occur?
If a TP signal continues during the stop ramp after ProfEnable=0 has aborted a profile with TP positioning.
Which products/versions are affected ?
ECS Posi&Shaft <= V1.3
Possible diagnostics?
None..
Short-term measures/recommendations?
Ensure that a TP signal does not occur during the stop ramp. If necessary, activate quick stop (QSP) as a precaution.
In certain circumstances, the impact can be reduced by dividing the residual path of the TP positioning to be executed into a short residual path of the TP positioning and a subsequent relative positioning.
Evaluation:
In application cases where an unexpectedly longer braking distance could pose a risk, QSP must also be activated.
Published with service message No. 2009/13
