Corrected from:
Library: L_MC4P_RoboticHandling from V03.15.00.200
(update via package manager)
Response of the new version:
The stop function of the AxesGroup will be maintained until standstill now, as expected.
The AxesGroup unexpectedly executes an error stop instead of the triggered stop function.
Thus, all axes are brought to standstill via xStopAll and the individual stop ramps.
Expected behaviour would be that the stop function of the AxesGroup would be maintained until standstill and that it would not be influenced by other FBs.
When does this behaviour occur?
The behaviour occurs if a movement of the AxesGroup is aborted with 'AGBC.xGroupStopExecute'=TRUE and a new travel request is triggered via MC_MoveLinearAbsolute during the stop ramp.
Which products are affected?
Library: L_MC4P_RoboticHandling
Short-term measures:
Evaluation/recommendations:
