User manual

38 Publication 1756-RM093F-EN-P - January 2010
Chapter 4 CIP Safety and the Safety Network Number
Considerations for
Assigning the Safety
Network Number (SNN)
The assignment of the SNN is dependent upon factors including the
configuration of the controller or CIP Safety I/O module.
Safety Network Number (SNN) for Safety Consumed Tags
When a safety controller that contains produced safety tags is added
to the I/O Configuration tree, the SNN of the producing controller
must be entered. The SNN may be copied from the producing
controller’s project and pasted into the new controller being added to
the I/O Configuration tree.
Refer to the GuardLogix Controllers User Manual, publication
1756-UM020
, or the 1768 Compact GuardLogix Controllers User
Manual, publication 1768-UM002
, for information on how to copy and
paste an SNN.
Safety Network Number (SNN) for Out-of-box Modules
Out-of-box CIP Safety I/O modules do not have an SNN. The SNN is
set when a configuration is sent to the module by the GuardLogix
controller that owns the module.
Safety Network Number (SNN) for Safety Module with a Different
Configuration Owner
When a CIP Safety I/O module is owned by a different GuardLogix
controller (controller B), and then is added to another GuardLogix
project (controller A project), RSLogix 5000 software assigns the SNN
based on the current project. Since the current project (controller A
project) is not the true configuration owner, you need to copy the
original SNN (controller B project) into the configuration in controller
A’s project. This is easy to do with standard copy and paste
commands. The result is that the CIP Safety I/O module produces data
to two GuardLogix controllers at the same time. You can do this for a
maximum of 16 controllers.
IMPORTANT
To add a CIP Safety I/O module to a configured GuardLogix
system (the SNN is present in the GuardLogix controller), the
replacement CIP Safety module should have the correct SNN
applied before it is added to the CIP Safety network.