EasyManua.ls Logo

Omron NX-SL3500

Omron NX-SL3500
626 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Event code Event name Meaning Assumed cause
Level
Reference
M
a
j
P
rt
M
i
n
O
b
s
I
n
f
o
80300000 hex
[NX-SL3£££]
Safety Proc-
ess Data
Communica-
tions Time-
out
A communications
timeout occurred in
safety process data
communications with
the Safety Control
Unit.
A setting is not correct. The
setting of the safety task peri-
od is too short.
There is excessive noise.
The Safety CPU Unit or safety
slave entered a status where it
could not continue safety proc-
ess data communications.
The process data communica-
tions were not performed cor-
rectly because an error or sta-
tus change occurred in the NX
bus master to which the Unit is
connected.
¡
page
12 - 37
80300001 hex
[NX-SL5
£££]
FSoE Mas-
ter Connec-
tion Timeout
A communication
timeout occurred in
FSoE communica-
tions with the FSoE
slave.
A setting is not correct. The
setting of the safety task peri-
od is too short.
There is excessive noise.
The Safety CPU Unit or FSoE
slave entered a state where it
could not continue FSoE com-
munications.
The process data communica-
tions were not performed cor-
rectly because an error or sta-
tus change occurred in the NX
bus master to which the Unit is
connected.
¡
page
12 - 38
80310000 hex
[NX-SL5
£££]
CIP Safety
Originator
Connection
Not Estab-
lished Error
CIP safety originator
connection was not
established.
The target node is different.
The target node is not config-
ured.
The target node status is inva-
lid.
¡
page
12 - 39
80320000 hex
[NX-SL5
£££]
CIP Safety
Originator
Connection
Timeout
A timeout occurred in
CIP safety originator
connection.
The communications cable is
disconnected or broken.
The target node entered a
state where it could not accept
the connection.
The timeout value in the com-
munications setup is too small.
There is excessive noise.
¡
page
12 - 40
80330000 hex
[NX-SL5
£££]
CIP Safety
Target Does
Not Exist
The target node does
not exist.
The communications cable is
disconnected or broken.
The target node entered a
state where it could not accept
the connection.
The timeout value in the com-
munications setup is too small.
There is excessive noise.
¡
page
12 - 41
12 Troubleshooting
12 - 20
NX-series Safety Control Unit User's Manual (Z930)

Table of Contents

Related product manuals