Rockwell Automation 1734-AENTR EtherNet/IP Network Configuration User Manual - Manual (Page 64)

64 Rockwell Automation Publication ENET-UM001L-EN-P - March 2014
Chapter 6 Interlocking and Data Transfer between Controllers
Terminology
A Logix5000 controller can produce (broadcast) and consume (receive) system-
shared tags.
To share produced or consumed tags, two controllers must be attached to the
same EtherNet/IP subnet. Two controllers cannot bridge produced or consumed
tags over two subnets.
Connections for Produced
and Consumed Tags Logix controllers can produce (broadcast) and consume (receive) system-shared
tags that are sent and received via the EtherNet/IP communication module.
Produced and consumed tags each require connections.
Table 11 - Tag Definitions
Term Definition
Produced tag A tag that a controller makes available for use by other controllers. Multiple
controllers can simultaneously consume (receive) the data. A produced tag
sends its data to one or more consumed tags (consumers) without using logic.
The produced tag sends its data at the RPI of the consuming tag.
Consumed tag A tag that receives the data of a produced tag. The data type of the consumed
tag must match the data type (including any array dimensions) of the produced
tag. The RPI of the consumed tag determines the period at which the data
updates.
Table 12 - Required Connections for Produced and Consumed Tags
Tag Type Required Connections
Produced The local controller (producing) must have one connection for the produced tag
and the first consumer and one more connection for each additional consumer
(heartbeat). The produced tag requires two connections.
As you increase the number of controllers that can consume a produced tag, you
also reduce the number of connections the controller has available for other
operations, such as communication and I/O.
Consumed Each consumed tag requires one connection for the controller that is consuming
the tag.
IMPORTANT: When you configure a consumed tag, you must add a remote
module to the producing controller’s Studio 5000 environment project to
configure the consuming controller. The default Comm Format when adding a
remote module to the project is Rack Optimized.
Change the Comm Format to None when adding the remote communication
module.