Description
The motion monitoring of mechanical unit arg has been triggered. The reason is arg .
- The motion monitoring of the axis has been triggered.
- Prevent SafeMove force limit violation.
- Prevent axis SafeMove torque limit violation.
Consequences
mechanical unit arg stops motion immediately. It then returns to a location on the path where it was run. If collision error handling is not configured, execution will stop and remain in the motor power-on state, waiting for a start request. If collision error handling has been configured, execution continues into the error handler.
Possible causes
Collisions, incorrect load definitions or external forces may cause motion monitoring to be triggered. This problem can also be caused by old and worn brakes, where when motion begins, the brakes do not release in the expected time.
Recommended actions
- If execution stops, acknowledge the fault and resume operation by pressing the "Start" button on the FlexPendant.
- Make sure all loads are correctly defined and measured.
- If the mechanical unit is exposed to forces from external processes, use the RAPID command or system parameter to increase the monitoring level.
- Consider configuring collision error handling in the theme controller, type " General Rapid ", and add an error handler for collision errors.