L_MC4P: After aborting a jogging request of the axis group via PathStop, travel requests can no longer be started (corrected from V3.15.0)
Corrected from: Library: L_MC4P_RoboticHandling (FAST Motion) V03.15.00.200 (update via PackageManager)
Response of the new version:
The reason for the malfunction has been remedied.
After a stop accurate to the path via 'AGBC.xGroupStopExecute' further travel requests can be started now.
What happens?
Further travel requests can no longer be started.
When does this behaviour occur?
- The axis group is operated with manual jog (jogging) via 'L_MC4P_AxesGroupBasicControl' and
- the travel request is aborted with a stop accurate to the path (AGBC.xGroupStopExecute).
The corresponding behaviour occurs if jogging is executed via the 'L_TT1P_(Track)PickAndPlace' technology module (TM) and the stop is carried out via TM.xPathStop.
The TM internally uses the AGBC FB.
Which products are affected? Library: L_MC4P_RoboticHandling (FAST Motion) (L_TT1P_TechnologyModules_LM due to internal use of L_MC4P)
Short-term measures:
Only abort manual jog (jogging) requests with the axis-based 'xStopALL' stop.
