Omron DeviceNet Safety, System Configuration Manual

Page: 255 / 376

221
Connection Status Tables Section 8-1
01:0117 Connection Path Error 1. Two or more output safety I/O connections have been set for the Safety Slave.
• Change the Safety Connection setting for the Safety Master so there is only
one connection. Then reset the Safety Slave to default settings and download
the device parameters to the Safety Slave again.
2. The same output assembly number for a Safety Slave has been used for both
a Safety Master and a Standard Master.
• Input assembly numbers can be duplicated but output assembly numbers
cannot. Check the Safety Connection setting for both the Safety Master and
the Standard Master then return the Safety Slave to default settings and
download the device parameters to the Safety Slave again.
• If the error remains even after the above countermeasure has been per-
formed, delete and re-register the connections registered to the Safety Mas-
ter.
01:0119 Unable to communicate
with Safety I/O The DST1-XD @@ Safety Slave is set to Auto Execution Mode. In this mode, the
Controller cannot establish Safety I/O communications with the Safety Slave.
Change the mode to After Establishing Safety I/O Connection.
01:0204 Communications with
Safety Slave timed out It may not be possible to communicate with the Safety Slave.
Check the status of the Safety Slave to see if it is online (the NS indicator
should be flashing or lit green). If the Safety Slave is online, check the following
items.
• Make sure that the Safety Slave's node address is correct.
• Make sure that all nodes are set to the same baud rate.
• Make sure that all cable lengths (main and branch lines) are suitable.
• Make sure that the cable is not broken or loose between the Safety Master
and Safety Slave.
• Make sure that terminating resistance has been connected only at the ends of
the main line.
• Make sure that there is not excessive noise affecting communications.
01:031E No. of Connections Error The setting for the number of safety I/O connections exceeds the upper limit
supported by the Safety Slave. Adjust the Safety Connection setting for the rel-
evant Safety Master. In particular, check that no more than 15 Safety Masters
are set for each Multi-cast connection, with a maximum total of 30.
01:031F Connection ID Resource
Error The maximum number of connection IDs for one Safety Master (12) has been
exceeded.
Change the ID allocation under Edit Safety Connection – Expansion Con-
nection Setting to “Check Produced IDs in the Safety Slave” in the corre-
sponding Safety I/O Connection (Safety Input Assembly) setting, then
download the device parameters to the Safety Master again.
01:07FF Non-existent Safety Slave The Safety Slave may not have been added to the network correctly. Check
that the corresponding Safety Slave is online (i.e., the NS indicator is flashing
green or lit green.) If the Safety Slave is not online, check the following items.
• Is the node address for the Safety Slave correct?
• Do all nodes have the same baud rate?
• Is the cable length correct (trunk lines and branch lines)?
• Is the cable disconnected or slack?
• Is the terminating resistance only on both ends of the main line?
• Is there a lot of noise?
01:080C Safety Signature Mismatch The safety signature for the Safety Slave monitored by the Safety Master does
not match the safety signature of the Safety Slave itself.
• Reset the Safety Slave to default settings then download the device parame-
ters again.
• If the above remedy does not work, delete then re-register the connections
registered to the Safety Master.
Status Countermeasure