Considerations for produced and consumed tags

Keep these considerations in mind for produced and consumed tags.
  • The tags must be controller-scoped tags.
  • The data types must match, including user-defined data type layout.
  • The size of the produced and consumed standard tag is limited to less than or equal to 500 bytes.
  • A produced/consumed tag can only be created when the controller is offline.
  • Connection status information can be included with the produced tag in a standard controller. In order to do this, create a user defined type whose first member is a CONNECTION_STATUS type. Then, the remaining members in the user-defined data type contain the data to be produced.
For produced and consumed safety tags, these requirements are mandatory:
  • The size of the produced and consumed safety tags are limited to 128 bytes.
  • Connection status information must be included with produced and consumed safety tags. Create a user-defined data type whose first member is a CONNECTION_STATUS type. The remaining members in the user-defined data type contain the data to be produced.
  • The Class field must be set to Safety.
  • Safety tags can only be modified when the safety application is not in a safety secured state.
  • Compact GuardLogix
     5380 and
    GuardLogix
     5580 Safety controllers can only produce safety tags as unicast. These controllers can consume safety tags as either unicast or multicast.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal