ABB IRC5 Operating Manual page 365

max allowed position error at pick/place position. System
parameter 'Max tracking error at pick pos'.
50497, Maximum number of axes in drive module
reached
Description
Joint arg is configured so that the total number of axes in the
drive module becomes larger than maximum allowed (14).
Recommended actions
Check the configuration file.
Use correct parameters and reset the system.
50498, Motion configuration
Description
Failed to read configuration type in topic Motion from the
controller.
Probable causes
This is often a result of syntax error or similar in a loaded
configuration file.
Recommended actions
Check for earlier Configuration errors in the start up. Check
configuration file in previous step. Use correct parameters and
Reset the system.
50499, Exceeded maximum allowed path
correction
Description
The correction needed for arg to follow the actual path is larger
than the allowed maximum correction. The current correction
is arg mm while maximum allowed path correction is arg mm.
Consequences
Program execution is stopped.
Probable causes
Too large path correction, sensor fault or improper placement
of the work object.
Recommended actions
If this behaviour is expected and wanted, change the 'Maximum
allowed path correction' parameter in topic Motion Planner and
topic Motion.
50500, Functionality has Beta status
Description
The system has been configured with a non-default value for
the system parameter 'dyn_ipol_type'. This functionality has
Operating manual - Troubleshooting IRC5
3HAC020738-001 Revision: AA
currently beta status and shall only be used for testing and
evaluation.
Recommended actions
Unless you are doing tests in cooperation with ABB we
recommend that you change the value back to the previous
value.
50501, Short movements
Description
One or more consecutive move instructions resulted in
movements close to zero length.
Task: arg.
Program ref. arg.
Consequences
Programming with multiple close to zero length movements in
a robot program can lead to high CPU load which can make
zones to be converted into finepoints (event message 50024).
Very close programmed points can also lead to non-smooth
robot motion.
Probable causes
Multiple move instructions with the same programmed position
or subsequent move instructions with short distance between
programmed positions.
Recommended actions
Increase the distance between the programmed positions.
Remove redundant intermediate programmed positions.
If the behavior of the robot and the system is ok, the sensitivity
of this event message can be adjusted by using the system
parameter 'Max allowed short segments' in topic Motion and
type Motion Planner.
50502, Collision Avoidance load error
Description
Failed to load the configuration files for Collision Avoidance.
Consequences
No collision checks will be made.
Probable causes
Incorrect configuration files for Collision Avoidance. Check the
internal event log for a more specific error description.
Recommended actions
Correct the configuration files.
© Copyright 2005-2018 ABB. All rights reserved.
5 Troubleshooting by event log
5.7 5 xxxx
Continued
365