Configuration Signature and Ownership
Every safety module in a system has a configuration signature and configuration
ownership.
Configuration Signature
Each safety device has a unique configuration signature that defines the module
configuration. The configuration signature includes the following:
- ID number
- Date
- Time
The configuration signature is used to verify a module’s configuration.
If you choose to configure safety connections with a Safety Configuration Identifier,
SCID = 0, you are responsible for ensuring that originators and targets have the
correct configurations.
IMPORTANT:
The signature can only be considered “verified” (and configuration locked)
after user testing.
Configuration Ownership
The connection between the owner-controller and the safety module is based on the
following:
- Safety module node number
- Safety module safety network number
- Controller node or slot numberIMPORTANT:If the owner-controller is a Compact GuardLogix 5380 controller, the controller has a node number.If the owner-controller is a GuardLogix 5580 controller, the controller has a slot number.
- Controller safety network number
- Path from the controller to the safety module
- Configuration signature
If any differences are detected, the connection between the owner-controller and the
safety module is lost, the yellow yield icon appears in the controller project
tree.
Different Configuration Owner
When a controller owns the I/O module configuration, other controllers can listen to
the input. In this case, the module configuration signature in the Logix Designer
project for any listening controller must match the one in the owner-controller
project.
TIP:
If the safety module is configured for inputs only, you can copy and paste
the configuration signature from one project to the other.
If the safety module has safety outputs, the configuration signature
parameter is disabled.
Provide Feedback