Rockwell Automation Allen-Bradley 1756 ControlLogix Owner's manual

Programming Manual
Original Instructions
Logix 5000 Controllers
Produced and Consumed
Tags
1756 ControlLogix, 1756 GuardLogix, 1769 CompactLogix,
1769 Compact GuardLogix, 1789 SoftLogix, 5069
CompactLogix, 5069 Compact GuardLogix, Studio 5000
Logix Emulate

Logix 5000 Controllers Produced and Consumed Tags
2 Rockwell Automation Publication 1756-PM011K-EN-P - September 2020
Important User Information
Read this document and the documents listed in the additional resources section about installation, configuration, and
operation of this equipment before you install, configure, operate, or maintain this product. Users are required to familiarize
themselves with installation and wiring instructions in addition to requirements of all applicable codes, laws, and standards.
Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required to
be carried out by suitably trained personnel in accordance with applicable code of practice.
If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be
impaired.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use
or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and
requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for
actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software
described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is
prohibited.
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to
personal injury or death, property damage, or economic loss.
ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss.
Attentions help you identify a hazard, avoid a hazard, and recognize the consequence.
IMPORTANT
Identifies information that is critical forsuccessful application and understanding of the product.
Labels may also be on or inside the equipment to provide specific precautions.
SHOCK HAZARD: Labelsmay be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be present.
BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous
temperatures.
ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to potential Arc Flash. Arc Flash
will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL Regulatory requirements for safe work practices and
for Personal Protective Equipment (PPE).

Rockwell Automation Publication 1756-PM011K-EN-P - September 2020 3
Summary of Changes
This manual includes new and updated information. Use these reference
tables to locate changed information.
Grammatical and editorial style changes are not included in this summary.
Global changes
This table identifies changes that apply to all information about a subject in
the manual and the reason for the change. For example, the addition of new
supported hardware, a software design change, or additional reference
material would result in changes to all of the topics that deal with that subject.
Change
Topic
Updated branding.
Throughout
New or enhanced features
This table contains a list of topics changed in this version, the reason for the
change, and a link to the topic that contains the changed information.
Topic Name
Reason
Legal Notices on page 7 Updated Legal Notices
Produced/consumed tags on page 9 Changed title from Introduction to Produce and
Consumed tags.
Considerations for produced and consumed tags
on page 10
Added new topic.
Organize tags for produced or consumed data
on page 14
Changed topic title.
Set up produced and consumed axes on page 16
New feature
Create a produced tag on page 20 Added prerequisite to create user-defined data
type. Updated step 2 to add new tag. Updates
steps to included text only.
Create a consumed tag on page 22 Added prerequisite to create user-defined data
type. Updated step 2 to add new tag. Updates
steps to included text only.
Consumed Tag Connection dialog box - Connection
tab on page 25
Added tip under the third bullet
Consumed Tag Connection dialog box - Status tab
on page 26
Added new topic.
Consumed Tag Connection dialog box - Safety tab
on page 27
Added new topic.
Set Advanced Options dialog box parameters
on page 27
Added tips to the steps
Set an RPI Range for Produced Tags on page 29 Added new topic.
Produce and Consume ControlNet Safety Tags
on page 33
Added new topic
Edit Connection Information on page 34
Added new topic

Summary of Changes
4 Rockwell Automation Publication 1756-PM011K-EN-P - September 2020
Topic Name
Reason
Advanced Connection Reaction Time Limit
Configuration Dialog Box Overview on page 38
Added new topic
Produce and consume array types on page 47
Added new topic
Work with large arrays on page 47
Added new topic

Rockwell Automation Publication 1756-PM011K-EN-P - September 2020 5
Table of Contents
Additional resources................................................................................... 7
Legal Notices ............................................................................................... 7
Chapter 1
Produced/consumed tags........................................................................... 9
Considerations for produced and consumed tags..................................10
Controllers and networks that support produced/consumed tags..10
Two controllers in same chassis.......................................................... 11
Two controllers in separate chassis using SynchLink....................... 11
Connection requirements of a produced or consumed tag.............. 11
Considerations when migrating projects that contain multicast
produce tags................................................................................................13
Organize tags for produced or consumed data .......................................14
Bandwidth limitations adjustments...................................................15
Set up produced and consumed axes........................................................16
Produced and consumed axis example.....................................................17
Produced and consumed axis configuration example............................18
Produce and consume program example................................................20
Create a produced tag...............................................................................20
Configure connection properties for produced tags.........................21
Configure status properties for produced tags ................................ 22
Create a consumed tag.............................................................................. 22
Additional steps for a PLC-5C controller........................................... 24
Consumed Tag Connection dialog box - Connection tab ...................... 25
Consumed Tag Connection dialog box - Status tab ............................... 26
Consumed Tag Connection dialog box - Safety tab................................ 27
Set Advanced Options dialog box parameters ........................................ 27
Set an RPI Range for Produced Tags ....................................................... 29
Unicast connection option ..................................................................31
RPI limitations and negotiated default..............................................31
Produce and Consume ControlNet Safety Tags ......................................33
Edit Connection Information ...................................................................34
Set up the consuming controller...............................................................35
Verify consumed tag acceptance...............................................................37
Advanced Connection Reaction Time Limit Configuration Dialog Box
Overview .................................................................................................... 38
Produced and consumed RPI scenarios ...................................................39
Scenario 1..............................................................................................39
Scenario 2 ............................................................................................40
Scenario 3..............................................................................................41
Scenario 4..............................................................................................43
Summary of Changes
Preface
Produce and consume a tag

Table of Contents
6 Rockwell Automation Publication 1756-PM011K-EN-P - September 2020
1769-L2x and 1769-L3x RPI limits...............................................................44
RPI I/O faults ..............................................................................................45
Chapter 2
Produce and consume array types............................................................47
Work with large arrays..............................................................................47
Produce a large array................................................................................. 48
Produce a Large Array
Index

Rockwell Automation Publication 1756-PM011K-EN-P - September 2020 7
Preface
This manual details how, with a Logix 5000™ controller, to produce and
consume standard tags and produce a large array. For information on
produced and consumed safety tags, refer to the documentation specific to
the controller.
This manual is one of a set of related manuals that show common procedures
for programming and operating Logix 5000 controllers.
For a complete list of common procedures manuals, refer to the Logix 5000
Controllers Common Procedures Programming Manual, publication 1756-
PM001.
The term Logix 5000 controller refers to any controller based on the Logix
5000 operating system.
These documents contain additional information concerning related
Rockwell Automation products.
Resource
Description
Replacement Guidelines: Logix 5000 Controllers
Reference Manual, publication 1756-RM100
Provides guidelines for migrating projects from
ControlLogix 5560 and 5570 controllers to
ControlLogix 5580 controllers, and from
CompactLogix 5370 controllers to CompactLogix
5380 controllers.
ControlLogix 5580 and GuardLogix 5580 Controllers
User Manual, publication 1756-UM543
Provides information about designing a system,
operating a ControlLogix or GuardLogix-based 5580
controllers system, and developing applications.
CompactLogix 5380 and Compact GuardLogix 5380
Controllers User Manual, publication 5069-UM001
Explains how to use the CompactLogix and Compact
GuardLogix 5380 Controllers.
GuardLogix 5570 Controllers User Manual,
publication 1756-UM022
Describes the GuardLogix-specific procedures to
configure, operate, and troubleshoot the controller.
Compact GuardLogix 5370 Controllers User Manual,
publication 1769-UM022
Describes the necessary tasks to install, configure,
program, and operate a Compact GuardLogix 5370
controller.
Industrial Automation Wiring and Grounding
Guidelines, publication 1770-4.1
Provides general guidelines for installing a Rockwell
Automation industrial system.
Product Certifications webpage, available
at http://ab.rockwellautomation.com
Provides declarations of conformity, certificates,
and other certification details.
View or download publications
at http://www.rockwellautomation.com/literature. To order paper copies of
technical documentation, contact a local Rockwell Automation distributor or
sales representative.
Rockwell Automation publishes legal notices, such as privacy policies, license
agreements, trademark disclosures, and other terms and conditions on
the Legal Notices page of the Rockwell Automation website.
Additional resources
Legal Notices

Preface
8 Rockwell Automation Publication 1756-PM011K-EN-P - September 2020
End User License Agreement (EULA)
You can view the Rockwell Automation End-User License Agreement ("EULA")
by opening the License.rtf file located in your product's install folder on your
hard drive.
Open Source Licenses
The software included in this product contains copyrighted software that is
licensed under one or more open source licenses. Copies of those licenses are
included with the software. Corresponding Source code for open source
packages included in this product are located at their respective web site(s).
Alternately, obtain complete Corresponding Source code by contacting
Rockwell Automation via the Contact form on the Rockwell Automation
website: http://www.rockwellautomation.com/global/about-
us/contact/contact.page
Please include "Open Source" as part of the request text.
A full list of all open source software used in this product and their
corresponding licenses can be found in the OPENSOURCE folder. The default
installed location of these licenses is C:\Program Files (x86)\Common
Files\Rockwell\Help\FactoryTalk Services Platform\Release
Notes\OPENSOURCE\index.htm.

Rockwell Automation Publication 1756-PM011K-EN-P - September 2020 9
Chapter 1
Produce and consume a tag
A Logix 5000 controller produces (broadcast) and consumes (receive) system-
shared tags.
Number
Description
Controller_1
Produced tag
Controller_2
Consumed tag
Controller_3
Consumed tag
Controller_4
Consumed tag
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.
Produced/consumed tags

Chapter 1 Produce and consume a tag
10 Rockwell Automation Publication 1756-PM011K-EN-P - September 2020
Term
Definition
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.
Keep the following 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.
See also
Organize tags for produced or consumed data on page 14
Create a produced tag on page 20
Create a consumed tag on page 22
For two controllers to share produced or consumed tags, both controllers
must be in the same backplane or attached to the same control network, such
as ControlNet or EtherNet/IP network. Although produced and consumed
tags can be bridged over two networks, Rockwell Automation® does not
support this configuration. Check the documentation specific to your
controller to determine which network connections it supports.
Considerations for
produced and
consumed tags
Controllers and networks
that support
produced/consumed tags

Chapter 1 Produce and consume a tag
Rockwell Automation Publication 1756-PM011K-EN-P - September 2020 11
See also
Two controllers in same chassis on page 11
Two controllers in separate chassis using SynchLink on page 11
Connection requirements of a produced or consumed tag on page 11
If the controller firmware revision is earlier than revision 9.00, axes in pre-
revision 9.00 cannot be consumed in a revision 9.00 or later controller
because the axis structure changed in revision 9.00. For example, an axis
produced in revision 7.00 cannot be consumed in revision 11.00.
If the firmware revision is version 9.00 or earlier, the revision of the controller
for the consuming axis must be the same revision or earlier. For example, a
revision 11.00 controller can consume an axis from revision 11.00 or revision
10.00, but it is not possible for a revision 10.00 controller to consume an axis
from revision 11.00 or revision 12.00. It is not possible in Studio 5000 Logix
Designer® to add a new controller under the I/O configuration with a revision
later then the revision that is currently in use.
See also
Controllers and networks that support produced/consumed tags
on page 10
When using SynchLink to connect two ControlLogix racks, the produced and
consumed axis revision is no longer important, if SynchLink is supported. For
example, a revision 11.00 controller produces an axis transmitted from a 1756-
SYNCH module. In a different rack, another 1756-SYNCH module receives the
axis data. A controller running revision 10.00can then consume this data. In
this case, the revision of the consuming end is later then the revision of the
producing end. This case is not possible when the controllers are in the same
rack. This caseis possible when the controllers are in separate racks using
SynchLink to connect the racks.
See also
Controllers and networks that support produced/consumed tags
on page 10
Produced and consumed tags each require connections. As the number of
controllers that consume a produced tag increases, the number of
connections the controller has available for other operations, such as
communication and I/O, decreases.
IMPORTANT
If a consumed-tag connection fails, all other tags being consumed from that remote
controller stop receiving new data.
Each produced or consumed tag uses these connections.
Two controllers
in same chassis
Two controllers in separate
chassis using SynchLink
Connection requirements of
a produced or
consumed tag

Chapter 1 Produce and consume a tag
12 Rockwell Automation Publication 1756-PM011K-EN-P - September 2020
This type of tag
Uses this many connections
Produced tag number_of_consumers + 1
Consumed tag 1
Example:
Connection requirements of a Produced or Consumed Tag
•A ControlLogix controller producing 4 tags for 1 controller uses 8 connections:
•Each tag uses 2 connections (1 consumer + 1 = 2).
•2 connections per tag x 4 tags = 8 connections.
•Consuming 4 tags from a controller uses 4 connections (1 connection per tag x 4 tags
= 4 connections).
Communication Paths to Compact GuardLogix 5380, CompactLogix
5380, CompactLogix 5480, ControlLogix 5580, and GuardLogix 5580
controllers
If a controller running release version 24.00 or earlier intends to consume tag
data from Compact GuardLogix 5380, CompactLogix 5380, CompactLogix
5480, ControlLogix 5580, or GuardLogix 5580 controller, the controller must
have a target device in its I/O configuration for the connection. However,
releases version 24.00 and earlier do not have profiles for Compact
GuardLogix 5380, CompactLogix 5380, CompactLogix 5480, ControlLogix
5580, and GuardLogix 5580 controllers and requires a substitute profile.
Rockwell Automation recommends the following substitutes:
•To consume tags through the embedded Ethernet port on Compact
GuardLogix 5380, CompactLogix 5380, CompactLogix 5480,
ControlLogix 5580, or GuardLogix 5580 controller, represent the
controller as a Compact 5370 controller, such as the 1769-L36ERM, in
the consuming controller’s I/O configuration. These controllers have a
built-in Ethernet port and therefore can be addressed using an
EtherNet/IP Address.
•To consume tags through the backplane port on a GuardLogix 5580 or
ControlLogix 5580 controller, represent the controller as a
ControlLogix 5570, such as the 1756-L75, in the consuming controller’s
I/O configuration. This process allows connection using the backplane.
See also
Controllers and networks that support produced/consumed tags
on page 10

Chapter 1 Produce and consume a tag
Rockwell Automation Publication 1756-PM011K-EN-P - September 2020 13
When migrating projects from an earlier controller model to Compact
GuardLogix 5380, CompactLogix 5380, CompactLogix 5480, ControlLogix
5580, or GuardLogix 5580 controller, verify that the configuration of projects
containing multicast produce tags is correct.
Compact GuardLogix 5380 and GuardLogix 5580 controllers in
version 31.00 only produce safety tags as unicast
Compact GuardLogix 5380 and GuardLogix 5580 controllers only produce
safety tags as unicast. The controllers consume safety tags as either unicast or
multicast. When configuring a consumed safety tag, consider the capabilities
of the producer.
•If the producer in the I/O configuration of this controller is a Compact
GuardLogix 5380 or GuardLogix 5580 controller consuming a safety
tag, configure the consumed tag to use unicast.
•If the producer in the I/O configuration of this controller is a Compact
GuardLogix 5370, GuardLogix 5570, or GuardLogix 5560 controller,
configure the safety consumed tag as either unicast or multicast.
RPI limitations
In releases before version 28.00, produced tags produce data at the requested
packet interval (RPI) of the fastest requesting consumer. This RPI allows
multiple consumers, with different RPI settings, to connect successfully to a
producer. In releases version 28.00 and later, the first consumer of a produced
tag determines the RPI of produced data. All subsequent consumers must
request the same RPI value as the first consumer or they fail to connect and
display error code 0112.
The device that sends the first consumer connection to the producing
controller is the first consumer of a produced tag. The first consumer makes a
request based on the order in which the producer and consumer control
system powers up. Therefore, cycling power to the system can change the first
consumer. A device cannot be configured to be the first consumer. It is
difficult to identify which consumer sends the first request to the producing
controller, so plan accordingly when configuring multicast produced tags.
To make sure consumers of produced tags connect to Compact GuardLogix
5380, CompactLogix 5380, CompactLogix 5480, ControlLogix 5580, and
GuardLogix 5580 controllers:
•For consumers running releases version 17.00 and earlier that are
consumers of a produced tag from Compact GuardLogix 5380,
CompactLogix 5380, CompactLogix 5480, ControlLogix 5580, and
GuardLogix 5580 controllers:
Considerations when
migrating projects that
contain multicast
produce tags

Chapter 1 Produce and consume a tag
14 Rockwell Automation Publication 1756-PM011K-EN-P - September 2020
•Verify that all multicast consumed tags of a produced tag have the
same RPI. If they do not, some consumers fail to connect.
•For multicast consumers running releases version 18.00 and later:
•Verify that all multicast consumed tags of a produce tag have the
same RPI, or
•Verify that all multicast consumers are configured to Allow
Consumed Tags To Use RPI Provided By Producer.
For more information on replacing a ControlLogix 5560/5570 controller with a
ControlLogix 5580 controller or a CompactLogix 5370 controller with a
CompactLogix 5380 controller, refer to Replacement Guidelines: Logix5000
Controllers Reference Manual (1756-RM100) in the Rockwell Automation
Literature Library.
See also
Controllers and networks that support produced/consumed tags
on page 10
Follow these guidelines when organizing tags for produced or consumed data
(shared data).
Guideline
Details
Create the tags at the controller scope. Only controller-scoped tags can be shared.
Use one of these data types:
•DINT
•REAL
•Array of DINTs or REALs
•User-defined
To share other data types, create a user-defined data type that contains the required data.
Use the same data type for the produced tag and corresponding consumed tag or tags.
To share tags with a PLC-5C controller, use
a user-defined data type.
To
This
Then
Produce Integers Create a user-defined data type that contains an array of INTs with an even
number of elements, such as INT[2]. (When you produce INTs, youmust produce
two or more.)
Only one REAL
value
Use the REAL data type.
More than one
REAL value
Create a user-defined data type that contains an array of REALs.
Consume Integers Create a user-defined data type that contains these members.
Data Type
Description
DINT Status
INT[ x ], where x is the output size of the data from the
PLC-5C controller. (If you are consuming only one INT,
omit
x .)
Data produced by a
PLC-5C controller
Limit the size of the standard tag to 500
bytes.
If you must transfer more than 500 bytes, create logic to transfer the data in packets.
If the produced tag is over a ControlNet network, the tag may need to be less than 500 bytes.
Important: Produced and consumed safety tags are limited to 128 bytes.
Organize tags for produced
or consumed data

Chapter 1 Produce and consume a tag
Rockwell Automation Publication 1756-PM011K-EN-P - September 2020 15
Guideline
Details
Use the highest permissible RPI for your
application.
If the controller consumes the tag over a ControlNet network, use a binary multiple of the ControlNet network update
time (NUT). For example, if the NUT is 5 ms, use an RPI of 5, 10, 20, 40 ms, and so forth.
Verify that Compact GuardLogix 5380,
CompactLogix 5380, CompactLogix 5480,
ControlLogix 5580, or GuardLogix 5580
controller projects containing multicast
produce tags are configured correctly.
Take the following steps to make sure consumers of produce tags can connect:
•For consumers running Logix Designer releases v17 and earlier that are consumers of a producer from a Compact
GuardLogix 5380, CompactLogix 5380, CompactLogix 5480, ControlLogix 5580, or GuardLogix 5580 controller:
•Verify that all multicast consumed tags of a produce tag are configured with the same RPI. If they are not, some
consumers will fail to connect.
•For multicast consumers running LogixDesigner releases v18 and later, take one of these steps:
•Verify that all multicast consumed tags of a produce tag are configured with the same RPI, or
•Verify that all multicast consumers are configured to Allow Consumed Tags To Use RPI Provided By
Producer.
Combine data that goes to the same
controller.
If you are producing several tags for the same controller, group the data:
•Into one or more user-defined data types. (This uses fewer connections than producing each tag separately.)
•According to similar update intervals. (To conserve network bandwidth, use a greater RPI for less critical data.)
For example, you could create one tag for data that is critical and another tag for data that is not as critical.
See also
Create a produced tag on page 20
Create a consumed tag on page 22
Considerations for produced and consumed tags on page 10
When a tag is shared over a ControlNet network, the tag must fit within the
bandwidth of the network.
•As the number of connections over a ControlNet network increases,
several connections, including produced or consumed tags, may need
to share a network update time (NUT).
•Since a ControlNet network can pass only 500 bytes in one NUT, the
data of each connection must be less than 500 bytes to fit into the NUT.
Depending on the size of the system, there may not be enough bandwidth on
the ControlNet network for a tag of 500 bytes. If a tag is too large for the
ControlNet network, make one or more of these adjustments.
Adjustment
Description
Reduce NUT. At a faster NUT, fewer connections need to share an update slot.
Increase the requested packetinterval (RPI) of the
connections.
At higher RPIs, connections can take turns sending data during an update slot.
For a ControlNet bridge module (CNB) in a remote
chassis, choose the most efficient communication
format for that chassis:
Are most of the modules in the chassis non-
diagnostic, digital I/O modules?
Then choose this communication format for the
remote CNB module.
Yes Rack Optimization
No
None
The Rack Optimization format uses an additional 8 bytes for each slot in its chassis. Analog modules or
modules that are sending or getting diagnostic, fuse, timestamp, or schedule data require direct
connections and cannot take advantage of the rack optimized form. Choosing None frees up the 8 bytes
per slot for other uses, such as produced or consumed tags.
Bandwidth limitations
adjustments

Chapter 1 Produce and consume a tag
16 Rockwell Automation Publication 1756-PM011K-EN-P - September 2020
Adjustment
Description
Separate the tag into two or more smaller tags. 1. Group the data according to similar update rates. For example, create one tag for data that is critical and
another tag for data that is not as critical.
2. Assign a different RPI to each tag.
Create logic to transfer the data in smaller sections
(packets).
See Produce a Large Array .
See also
Produce a large array on page 48
Organize tags for produced or consumed data on page 14
Set up axes to produce and consume axis data in the same chassis or between
different chassis.
Prerequisite
•Configure produced and consumer controllers.
To set up produced and consumed axes:
1. In the Controller Organizer, right-click the motion group and
select New Axis and select the data tape for the drive.
2. If creating a new axis, in the New Tag dialog box, enter a name for the
axis.
3. Set the Type to Produced.
•If editing an existing tag, in the Tag Editor, right-click the tag and
click Edit <name of tag> Properties and change
the Type to Produced.
4. Make sure the axis Data Type to the corresponding data type of the
produced axis.
5. Select Connection to open the Produced Tag Connection dialog box.
•Change the Max Consumers value to limit or expand the number of
consumers.
•Select Send DataState Change Event to Consumer to use an IOT
Instruction to send event trigger information to the consumers of
this tag.
•Click the Advanced tab and to open the Advanced Options dialog
box and configure the behavior of the multicast and unicast
connections to the produced tag, for example, limiting the intervals
at which data is produced over a multicast connection.
Set up produced and
consumed axes

Chapter 1 Produce and consume a tag
Rockwell Automation Publication 1756-PM011K-EN-P - September 2020 17
IMPORTANT
The minimum and maximum RPI is disabled for axis types. The produced
axis produced data at the axis rate. The minimum and maximum RPI is
equal to the axis update.
6. Add the producer controller to the I/O configuration of the consumer
controller.
7. Create a new consumed axis
•In the Controller Organizer, right-click the motion group and
select New Axis and select the data tape for the drive.
•If updating an existing axis, right-click Controller Tags and
click New Tag.
8. If creating a new axis, enter a name for the axis.
9. Set the type to Consumed to open the Consumed Tag Connection
dialog box.
•On the Connection tab, in the Producer list, select the controller
that has the Produced Axis.
•In Remote Data, enter the name of the produced axis.
•Specify unicast/multicast connection over Ethernet/IP.
10. In the Controller Organizer, expand the Motion Groups folder and
double click the axis. Adjust axis properties for the application.
•In the Units tab to adjust the Position Units value.
•In the Conversion tab, update the Conversation Constant value.
See also
Create a produced tag on page 20
Create a consumed tag on page 22
Configure connection properties for produced tags on page 21
This example requires these prerequisites:
•ControlLogix® and CompactLogix™ controllers must be from the 5380,
5480, or 5580 family of controllers
•Studio 5000 Logix Designer® v32 or higher
•The Logix controls must be on the same Ethernet/IP.
Assume a machine builder delivered a new filler machine to a customer. The
machine builder is also upgrading the capper machine on the same
manufacturing line.
The filler machine is the lead machine on the line:
•Bottles flow from the filler into the capper machine
•The filler machine uses a ControlLogix controller and Kinetix servo
drives
Produced and consumed
axis example

Chapter 1 Produce and consume a tag
18 Rockwell Automation Publication 1756-PM011K-EN-P - September 2020
The capper machine must follow the output of the filler machine:
•Once synchronized to the filler, the capper must stay in sync
•This machine will use a CompactLogix controller and Kinetix® servo
drives
The filler machine produces an axis of motion for the capper motion to
consume. This enables the capper and filler machine to maintain
coordination.
Item
Description
ControlLogix 5580
Kinetix 5700
CompactLogix 5380
Kinetix 5500
Produced axis
Consumed axis
See also
Produced and consumed axis configuration example on page 18
Produce and consume program example on page 20

Chapter 1 Produce and consume a tag
Rockwell Automation Publication 1756-PM011K-EN-P - September 2020 19
This example illustrates how to configure a produced and consumed axis.
Produced and consumed
axis configuration example

Chapter 1 Produce and consume a tag
20 Rockwell Automation Publication 1756-PM011K-EN-P - September 2020
See also
Produce and consume program example on page 20
This programming example shows syncing the filler (produced) to the capper
(consumed) axis.
See also
Produced and consumed axis example on page 17
The produced tag sends its data to one or more consumed tags without using
logic. Multiple controllers are capable of using the produced tags
simultaneously.
Prerequisite:
•Create a user-defined data type defining the structure of the produced
data. The first data member must be the predefined
CONNECTION_STATUS data type.
To create a produced tag:
1. Open the Logix Designer application and select a controller.
IMPORTANT
A controller is capable of having producing and consuming tags. A produced
cannot consume its own data. The local controller is the consumer. The
remote controller is the producer.
Produce and consume
program example
Create a produced tag