Omron DEVICENET SAFETY - SYSTEM CONFIGURATION 07-2009 System Configuration Manual page 154

Table of Contents

Advertisement

Safety Connection Settings
Note
Open Type
Open Type
Configure the Safety Slave
Check the safety signature
Open only
IMPORTANT Check that the Safety Master and the Safety Slave are configured correctly
Note
Configuration Owner
120
3. Refer to 7-1-2 Monitoring Safety Connections for information on status
codes.
• Reset the Safety Slave to default settings before opening an output con-
nection from another Safety Master.
• The error referred to earlier will occur if the Safety Master TUNID changes
as a result of node address or network number changes and the output
connection owner no longer matches.
Select the type of open processing to be performed when the NE1A-series
Controller establishes a connection with the Safety Slave.
The Safety Slave is configured when the connection is established. The parame-
ters that can be set are limited to the parameters relevant to the safety application.
Do not use this open type under normal conditions.
The NE1A-series Controller sends the safety signature of the slave when the con-
nection is established. The safety signature is checked in the Safety Slave that
receives a connection is established. Specify this open type when establishing a
connection with DST1-series Safety I/O Terminals.
The NE1A-series Controller does not send the safety signature of the slave when a
connection is established. The Safety Slave establishes the connection without
checking the safety signature. To use the slave function of the NE1A-series Con-
troller, it is necessary to configure the Safety Slave correctly from the Network
Configurator. If it is not correctly configured, a connection will not be established,
so there is no need to send the safety signature from the Safety Master for check-
ing.
when selecting Open only as the safety connection open type.
If the Safety Slave is not configured when Configure the Safety Slave is spec-
ified, the NE1A-series Controller configures the Safety Slave and then estab-
lishes a connection. Therefore, the communications can be started again just
by connecting the slave to the network without the Network Configurator when
the Safety Slave is replaced. In the current version, however, the parameters
to be set are only those related to the safety application. When standard
parameters do not need to be set, this open type can be specified. The ability
to set standard parameters is planned for future development.
To prevent configuration from an unintended source, Safety Slaves store data
in non-volatile memory to show that the node that performed configuration last
time is the configuration owner. The Safety Slave stores data in memory to
show if the configuration was performed by the Network Configurator or a sim-
ilar software tool (see note 1) and, if the configuration was performed by a
Safety Master, the Safety Slave stores the TUNID (see note 2). The Safety
Slave cannot be configured from another source while it has data on the con-
figuration owner.
If the configuration owner does not match, the following will occur.
A) If a download is attempted using the Network Configurator, an error
message will be displayed to indicate that configuration is not possible
until the Safety Slave is reset because the Safety Slave has been con-
figured by another device.
Description
Section 5-1

Advertisement

Table of Contents
loading

This manual is also suitable for:

Devicenet safety

Table of Contents