Corrected from:
Library: L_MC4P_RoboticHandling (FAST Motion) V03.17.00.54
(update via package manager)
Response of the new version:
The 'xCommandAborted' and 'xBusy' status outputs will be processed as expected now.
What happens?
After aborting a command via the 'xAbort' input of the 'MC_TrackConveyorBelt' FB, the 'xCommandAborted' and 'xBusy' status outputs do not display the correct status.
Expected behaviour: xCommandAborted = TRUE, xBusy = FALSE
Actual behaviour: xCommandAborted = TRUE, xBusy = TRUE
When does this behaviour occur?
The behaviour occurs if 'MC_TrackConveyorBelt' FB processing is aborted via the 'xAbort' input.
Which products are affected?
Library: L_MC4P_RoboticHandling (FAST Motion)
Short-term measures:
None.
Evaluation/recommendations:
