Produced/Consumed Safety Tags

To transfer safety data between controllers, you use produced and consumed safety tags.
Tags that are associated with safety I/O and produced or consumed safety data must be controller-scoped safety tags. For produced/consumed safety tags, you must create a user-defined data type with the first member of the tag structure that is reserved for the status of the connection. This member is a predefined data type called CONNECTION_STATUS.
Produced and Consumed Connections
Tag
Connection Description
Produced
Controllers can produce (send) safety tags to other controllers:
  • Controllers only support unicast produced tags.
  • Controllers do support producing a tag to up to 15 consumers if all consumers are configured to consume the tag unicast.
  • The producing controller uses one connection for each consumer.
  • The consuming controller must be at firmware revision 19 or later. Unicast was not added to safety produced/consumed tags until firmware revision 19.
Consumed
Controllers can consume (receive) safety tags from other controllers in these configurations:
  • If you have a
    ControlLogix®
     5590 controller (the producer) in the I/O tree of another
    ControlLogix®
     5590 controller (the consumer), then the consumer can only consume a tag from the producer if the tag is unicast.
  • If you have a
    GuardLogix®
     5580 controller (the producer) in the I/O tree of another
    GuardLogix®
     5580 controller (the consumer), then the consumer can only consume a tag from the producer if the tag is unicast.
  • If the producer controller is a
    GuardLogix®
     5570 controller, then a consumer controller can consume multicast or unicast tags.
  • Each consumed tag consumes one connection.
Produced and consumed safety tags are subject to the following restrictions:
  • Only controller-scoped safety tags can be shared.
  • Produced and consumed safety tags are limited to 128 bytes.
  • Produced/consumed tag pairs must be of the same user-defined data type.
  • The first member of that user-defined data type must be the predefined CONNECTION_STATUS data type.
  • The requested packet interval (RPI) of the consumed safety tag must match the safety task period of the producing
    GuardLogix®
     controller.
To configure produced and consumed safety tags to share data between peer safety controllers, you must properly configure the peer safety controllers, produce a safety tag, and consume a safety tag. See Configure the SNN for a Peer Safety Controller Connection.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal