Xxxx - ABB IRC5 Operating Manual

Troubleshooting
Hide thumbs Also See for IRC5:
Table of Contents

Advertisement

5 Troubleshooting by event log

5.4 2 xxxx

5.4 2 xxxx
20010, Emergency stop state
Description
The emergency stop circuit has previously been broken, and
while broken, an attempt was made to operate the robot.
Consequences
The system remains in state "Waiting for Motors ON after
emergency stop".
Probable causes
An attempt has been made to maneuver a control, before
switching the system back to status Motors ON.
Recommended actions
To resume operation, switch the system back to state Motors
ON by pressing the Motors ON button on the Control Module.
20011, Emergency stop state.
Description
Emergency stop reset is required.
Recommended actions
First release the Emergency stop button and then press the
panel button.
20012, System failure state active
Description
Fatal non-recoverable system error. Controller restart is
required.
Recommended actions
Turn the mains switch off and on again if the soft restart
command is ignored or not possible to reach.
20025, Stop order timeout
Description
The stop order was carried out as a forced guard stop when no
acknowledgement was received within the expected time.
Recommended actions
20030, Axis not commutated
Description
One or several internal drive unit axes are not commutated.
Recommended actions
Continues on next page
120
20031, Axis not calibrated.
Description
One or several absolute/relative measurement axes are not
calibrated.
Recommended actions
Check what axis that are not calibrated and calibrate them.
20032, Rev. counter not updated
Description
Revolution counter is not updated. One or several absolute
measurement axes are not synchronized.
Recommended actions
Move the axes to the sync position and update the revolution
counters.
20033, Axis not synchronized.
Description
One or several relative measurement axes are not synchronized.
Recommended actions
Order Motors On and synchronize all mechanical units in the
list.
20034, Robot memory is not OK
Description
This action or state is not allowed since data in the robot
memory is not OK.
Consequences
All data must be OK before automatic operation is possible.
Manually jogging the robot is possible.
Probable causes
There are differences between the data stored in the robot and
the controller. This may be due to replacement of SMB-board,
controller or both, or manually cleared robot memory.
Recommended actions
Update the robot memory as detailed in Operator's Manual,
IRC5.
© Copyright 2005-2018 ABB. All rights reserved.
Operating manual - Troubleshooting IRC5
3HAC020738-001 Revision: AA

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents