ABB IRC5 Operating Manual page 443

Consequences
The Robot Controller is not able to properly clean the safety
connection. The external CIP Safety Scanner may not be able
to reestablish the connection.
Probable causes
The CIP Safety Adapter may be in a state where the closing of
a safe connection is not allowed.
Recommended actions
Restart the robot controller.
90775, Selected RPI below recommended value
Description
Selected RPI for arg is below recommended value of 20ms.
Consequences
The jitter in the observed packet interval and the worst case
packet interval has increased causing unstable communication.
Probable causes
RPI below the recommended value.
Recommended actions
Set the Timeout Multiplier of the connection to a value greater
than 3.
90776, Configuration Signature Mismatch
Description
The Configuration Signature parameter received from an
external CIP Safety Scanner in the Forward Open request does
not match value in the CIP Safety Adapter of this robot
controller. The signature is created in the ABB Safety
Configuration Report and consist of ID, Date and Time.
Consequences
CIP Safety Communication with the external Scanner is not
possible.
Probable causes
The external Safety Scanner has a signature configured but
it did not match the value in the ABB Safety Configuration
Report of the CIP Safety Adapter or the Adapter configured the
signature to "Not Used".
Recommended actions
Verify that the external Scanner has all parts of the
Configuration Signature (ID, date and time) according to the
ABB Safety Configuration Report of the Adapter. If you wish to
disable the signature matching while opening a safety
connection, then set the Configuration Signature parameter to
Operating manual - Troubleshooting IRC5
3HAC020738-001 Revision: AA
"Not Used" in the Adapter and disable it in the external Scanner
as well.
90777, CIP Safety Configuration Mismatch - Size
Mismatch
Description
The configuration of EterNet/IP Device arg (or its EterNet/IP IO
connections) in I/O System Configuration does not match the
corresponding configuration in Visual SafeMove.
Consequences
CIP Safety Communication with arg may not work properly. The
CIP Safety Configuration Signature (SCID) generated in the
ABB Safety Configuration Report is invalid.
Probable causes
The parameter arg in I/O System Configuration is set to arg.
The corresponding parameter in Visual SafeMove is set to arg.
Recommended actions
Verify that the paramter arg has the same value in both: I/O
System Configuration and in Visual SafeMove. Verify that the
device arg configured in I/O System Configuration has all its
EtherNet/IP IO Connections attached as intended.
90778, CIP Safety Configuration Mismatch - Name
Mismatch
Description
The EtherNet/IP Device arg defined in the I/O System
Configuration does not exist in CIP Safety Scanner configuration
in Visual SafeMove.
Consequences
CIP Safety Communication with arg will not be possible. The
CIP Safety Configuration Signature (SCID) generated in the
ABB Safety Configuration Report is invalid.
Probable causes
The arg device does not exist in CIP Safety Scanner
configuration in Visual SafeMove.
Recommended actions
Verify that the device arg is added in Visual SafeMove
configuration. Verify that the device arg has the same name in
I/O System Configuration and in Visual SafeMove.
90779, CIP Safety Ownership Conflict
Description
An external CIP Safety Scanner tries to connect and write to
inputs of the CIP Safety Adapter. However, another Scanner
© Copyright 2005-2018 ABB. All rights reserved.
5 Troubleshooting by event log
Continues on next page
5.9 9 xxxx
Continued
443