ABB IRC5 Operating Manual page 132

Troubleshooting
Hide thumbs Also See for IRC5:
Table of Contents

Advertisement

5 Troubleshooting by event log
5.4 2 xxxx
Continued
Consequences
The system will react to the error causing the stop as specified
in its own event log text.
Probable causes
A number of errors may cause this. Faults causing the system
to go to system failure state will generally also create a
diagnostics record file.
Recommended actions
If required, the file may be appended to an error report sent to
your local ABB representative.
20188, System data is not valid
Description
The contents of the file, arg, containing system persistent data
is invalid. Internal error code: arg. The system has been started
using last good system data saved earlier at arg.
Consequences
Any changes made in the system configuration or RAPID
programs since arg will be rejected.
Recommended actions
Check other event messages occurring at the same time to
determine the actual cause. If acceptable, revert to the last auto
saved system data. Reinstall the system. Check the available
disk storage capacity. If required, erase data to increase free
storage capacity.
20189, Robot data not valid
Description
Could not load the system independent robot data from file arg.
The file exists but the content is not valid. Internal code: arg.
Recommended actions
Check other logged messages for needed actions. Make sure
there is free memory left on the device.
20192, Disk memory low
Description
The amount of free storage capacity on the disk is less than 25
MB. When reaching 10 MB, execution of RAPID programs will
be stopped.
Consequences
The disk memory is close to being completely full. When this
happens the system will not be able to function.
Probable causes
Too much data on the disk.
Continues on next page
132
Recommended actions
Save the files on some other disk connected to the network.
Erase data from disk.
20193, Robot data update warning
Description
Axis sync values and service information data (SIS) was
restored from backup.
The system independent robot data was not saved during
system shutdown. The data was restored from latest backup.
Recommended actions
Make sure there is free memory left on the device.
The backup battery may be drained. Check the hardware log.
20194, System data backup could not be created
Description
The system was restored successfully but a backup of the
current system data could not be created.
Recommended actions
Make sure there is free memory left on the device arg.
20195, System data from last shutdown is lost
Description
Normally, all system data is saved on shutdown. During the
last shutdown saving data has failed. The system has been
started using last good system data saved earlier at arg.
Consequences
Any changes made in system configuration or RAPID programs
since arg will NOT be available after restart. Any such changes
will have to be re-implemented.
Probable causes
The backup energy bank may have been drained at the time of
the shutdown. The storage disk may be full.
Recommended actions
Check other event messages occurring at the same time to
determine the actual cause. If acceptable, restart using revert
to last auto saved to accept the last good system data. Reinstall
the system. Check the available disk storage capacity. If
required, erase data to increase free storage capacity.
20196, Module saved
Description
During reconfiguration of the system a changed and not saved
module was found.
© 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