Allen-Bradley Studio 5000 Logix Emulate Owner's manual

Programming Manual
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

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 for successful application and understanding of the product.
Labels may also be on or inside the equipment to provide specific precautions.
SHOCK HAZARD: Labels may 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).
Allen-Bradley, Rockwell Software, Rockwell Automation, and TechConnect are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.

Rockwell Automation Publication 1756-PM011J-EN-P - February 2018 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.
Subject Reason
Updated screen shots
throughout.
The graphical user interface has been updated in
release 31 of the Logix Designer application.
Updated supported controllers. Logix Designer supports new 5069 Compact
GuardLogix controllers.
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
Additional Resources on page 7 Added controller user manuals as additional
resources
Controllers and networks that support
produced/consumed tags on page 12 Updated information on networks that support
produced and consumed tags
Considerations when migrating projects that contain
multicast produce tags on page 13 Added safety consumed tags on Compact
GuardLogix 5380 and GuardLogix 5580 controllers
considerations
Considerations when migrating projects that contain
multicast produce tags on page 13 Updated the versions of software for multicast
consumers running releases v18 and later
Organize tags for produced or consumed data on
page 14 Updated the controller projects to be verified to
include Compact GuardLogix 5380 and GuardLogix
5580 controllers
Create a produced tag on page 16 Renamed Produce a tag to Create a produce tag
Minor changes to the Create a produced tag
procedure
Create a consumed tag on page 18 Minor changes to the Create a consumed tag
procedure
Set RPI limits, default for producer tag on page 25 Updated the RPI limits and default procedure

Summary of Changes
4Rockwell Automation Publication 1756-PM011J-EN-P - February 2018
Consideration when migrating projects that contain
multicast produce tags on page 13
Organize tags for produced or consumed data on
page 14
RPI limitations and negotiated default on page 23
Set RPI limits, default for producer tag on page 25
RPI I/O faults on page 37
Renamed Allow Consumed Tags to Use RPI
Provided by Consumer to Allow Consumed Tags to
Use RPI Provided by Producer parameter
Set up the consuming controller on page 28 Renamed Set up the consumer tag to Set up the
consuming controller and updated the procedure

Rockwell Automation Publication 1756-PM011J-EN-P - February 2018 5
Table of contents
Additional Resources...................................................................................... 7
Legal notices................................................................................................... 8
Chapter 1
Introduction................................................................................................... 11
Controllers and networks that support produced/consumed tags.................. 12
Connection requirements of a produced or consumed tag............................ 12
Considerations when migrating projects that contain multicast produce tags
...................................................................................................................... 13
Organize tags for produced or consumed data.............................................. 14
Adjust for bandwidth limitations............................................................ 15
Create a produced tag ................................................................................... 16
Create a consumed tag.................................................................................. 18
Additional steps for a PLC-5C controller............................................... 22
RPI limitations and negotiated default.......................................................... 23
Set RPI limits, default for producer tag........................................................ 25
Unicast connection option...................................................................... 27
Set up the consuming controller ................................................................... 28
Verify consumed tag acceptance .................................................................. 29
Produced and consumed RPI scenarios........................................................ 32
Scenario 1............................................................................................... 32
Scenario 2............................................................................................... 33
Scenario 3............................................................................................... 34
Scenario 4............................................................................................... 35
1769-L2x and 1769-L3x RPI limits.............................................................. 35
RPI I/O faults................................................................................................ 37
Chapter 2
Introduction................................................................................................... 39
Produce a large array.................................................................................... 40
Preface
Produce and
Consume a Tag
Produce a Large
Array
Index

Rockwell Automation Publication 1756-PM011J-EN-P - February 2018 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/consumed safety tags, refer to the documentation specific to your
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 that is based on the
Logix 5000 operating system.
These documents contain additional information concerning related
Rockwell Automation products.
Resource Description
Replacement Guidelines: Logix5000
Controllers Reference Manual ,
publication 1756-RM100
Provides guidelines for migrating
projects from ControlLogix 5560/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 your 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.
You can view or download publications at
http://www.rockwellautomation.com/literature . To order paper copies of
technical documentation, contact your local Rockwell Automation distributor
or sales representative.
Additional
Resources

Preface
8Rockwell Automation Publication 1756-PM011J-EN-P - February 2018
Copyright notice
Copyright © 2018 Rockwell Automation Technologies, Inc. All Rights
Reserved. Printed in USA.
This document and any accompanying Rockwell Software products are
copyrighted by Rockwell Automation Technologies, Inc. Any reproduction
and/or distribution without prior written consent from Rockwell Automation
Technologies, Inc. is strictly prohibited. Please refer to the license agreement
for details.
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.
Other 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 can be located at their respective web
site(s).
You may alternately obtain complete Corresponding Source code by
contacting Rockwell Automation via our 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.
The following open source software is used in this product:
Software Copyright License Name License Text
AngularJS Copyright 2010-2017 Google, Inc. MIT License AngularJS 1.5.9 License
Bootstrap Copyright 2011-2017 Twitter, Inc.
Copyright 2011-2017 The Bootstrap Authors MIT License Bootstrap 3.3.7 License
jQuery Copyright 2005, 2014 JS Foundation and
other contributors MIT License jQuery 2.1.1 License
OpenSans Copyright 2017 Google, Inc. Apache License,
Version 2.0 OpenSans License
Trademark Notices
Allen-Bradley, ControlBus, ControlFLASH, Compact GuardLogix, Compact
I/O, ControlLogix, CompactLogix, DCM, DH+, Data Highway Plus,
DriveLogix, DPI, DriveTools, Explorer, FactoryTalk, FactoryTalk
Administration Console, FactoryTalk Alarms and Events, FactoryTalk Batch,
FactoryTalk Directory, FactoryTalk Security, FactoryTalk Services Platform,
FactoryTalk View, FactoryTalk View SE, FLEX Ex, FlexLogix, FLEX I/O,
Legal notices

Preface
Rockwell Automation Publication 1756-PM011J-EN-P - February 2018 9
Guard I/O, High Performance Drive, Integrated Architecture, Kinetix,
Logix5000, Logix 5000, Logix5550, MicroLogix, DeviceNet, EtherNet/IP,
PLC-2, PLC-3, PLC-5, PanelBuilder, PowerFlex, PhaseManager, POINT
I/O, PowerFlex, Rockwell Automation, RSBizWare, Rockwell Software,
RSEmulate, Historian, RSFieldbus, RSLinx, RSLogix, RSNetWorx for
DeviceNet, RSNetWorx for EtherNet/IP, RSMACC, RSView, RSView32,
Rockwell Software Studio 5000 Automation Engineering & Design
Environment, Studio 5000 View Designer, SCANport, SLC, SoftLogix,
SMC Flex, Studio 5000, Ultra 100, Ultra 200, VersaView, WINtelligent,
XM, SequenceManager are trademarks of Rockwell Automation, Inc.
Any Rockwell Automation logo, software or hardware product not
mentioned herein is also a trademark, registered or otherwise, of Rockwell
Automation, Inc.
Other Trademarks
CmFAS Assistant, CmDongle, CodeMeter, CodeMeter Control Center, and
WIBU are trademarks of WIBU-SYSTEMS AG in the United States and/or
other countries. Microsoft is a registered trademark of Microsoft Corporation
in the United States and/or other countries. ControlNet is a trademark of
ControlNet International. DeviceNet is a trademark of the Open DeviceNet
Vendors Association (ODVA). Ethernet/IP is a trademark of ControlNet
International under license by ODVA.
All other trademarks are the property of their respective holders and are
hereby acknowledged.
Warranty
This product is warranted in accordance with the product license. The
product’s performance may be affected by system configuration, the
application being performed, operator control, maintenance, and other related
factors. Rockwell Automation is not responsible for these intervening factors.
The instructions in this document do not cover all the details or variations in
the equipment, procedure, or process described, nor do they provide
directions for meeting every possible contingency during installation,
operation, or maintenance. This product’s implementation may vary among
users.
This document is current as of the time of release of the product; however,
the accompanying software may have changed since the release. Rockwell
Automation, Inc. reserves the right to change any information contained in
this document or the software at any time without prior notice. It is your
responsibility to obtain the most current information available from Rockwell
when installing or using this product.
Environmental compliance
Rockwell Automation maintains current product environmental information
on its website at

Preface
10 Rockwell Automation Publication 1756-PM011J-EN-P - February 2018
http://www.rockwellautomation.com/rockwellautomation/about-
us/sustainability-ethics/product-environmental-compliance.page
Contact Rockwell Automation
Customer Support Telephone — 1.440.646.3434
Online Support — http://www.rockwellautomation.com/support/

Rockwell Automation Publication 1756-PM011J-EN-P - February 2018 11
Chapter 1
Produce and Consume a Tag
A Logix 5000™ controller lets you produce (broadcast) and consume
(receive) system-shared tags.
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.
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.
Introduction

Chapter 1
Produce and Consume a Tag
12 Rockwell Automation Publication 1756-PM011J-EN-P - February 2018
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.
Produced and consumed tags each require connections. As the number of
controllers that can consume a produced tag increases, the number of
connections the controller has available for other operations, like
communication and I/O, is reduced.
Important: If a consumed-tag connection fails, all of the other tags being consumed
from that remote controller stop receiving new data.
Each produced or consumed tag uses the following connections.
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 v24 or earlier is to consume tag data from
Compact GuardLogix 5380, CompactLogix 5380, CompactLogix 5480,
ControlLogix 5580, or GuardLogix 5580 controller, it must have a target
device in its I/O configuration for the connection. However, releases v24 and
earlier do not have profiles for Compact GuardLogix 5380, CompactLogix
5380, CompactLogix 5480, ControlLogix 5580, and GuardLogix 5580
controllers, so a substitute must be used.
Rockwell 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 CompactLogix 5370 Controller, such as the 1769-
Controllers and
networks that
support
produced/consumed
tags
Connection
requirements of a
produced or
consumed tag

Produce and Consume a Tag
Chapter 1
Rockwell Automation Publication 1756-PM011J-EN-P - February 2018 13
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.
When you migrate projects from an earlier controller model to Compact
GuardLogix 5380, CompactLogix 5380, CompactLogix 5480, ControlLogix
5580, or GuardLogix 5580 controller, you need to verify that projects
containing multicast produce tags are configured correctly.
Compact GuardLogix 5380 and GuardLogix 5580 controllers in v31
only produce safety tags as unicast
Compact GuardLogix 5380 and GuardLogix 5580 controllers only produce
safety tags as unicast. They can 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, and you are
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 or GuardLogix 5570 or 5560 controller, the safety
consumed tag can be configured as wither unicast or multicast.
RPI limitations
In releases before v28, produced tags produce data at the requested packet
interval (RPI) of the fastest requesting consumer. This behavior allows
multiple consumers, with different RPI settings, to successfully connect to a
producer. In releases v28 and later, the first consumer of a produced tag
determines the RPI at which data is produced. All subsequent consumers
must request the same RPI value as the first consumer or they fail to connect
and display error code 0112.
The first consumer of a produced tag is the device that sends the first
consumer connection to the producing controller. The first consumer request
is based on the order in which the producer and consumer control system
powers up, so the first consumer can change if power is cycled to the system.
You cannot configure a device to be the first consumer. It can be difficult to
tell which consumer will send the first request to the producing controller, so
you should plan accordingly when configuring multicast produced tags.
Considerations
when migrating
projects that
contain multicast
produce tags

Chapter 1
Produce and Consume a Tag
14 Rockwell Automation Publication 1756-PM011J-EN-P - February 2018
To make sure consumers of produced tags can connect to Compact
GuardLogix 5380, CompactLogix 5380, CompactLogix 5480, ControlLogix
5580, and GuardLogix 5580 controllers, take the following steps:
•For consumers running releases v17 and earlier that are consumers of a
produced tag from Compact GuardLogix 5380, CompactLogix 5380,
CompactLogix 5480, ControlLogix 5580, and GuardLogix 5580
controllers:
•Verify that all multicast consumed tags of a produced tag are
configured with the same RPI. If they are not, some consumers will
fail to connect.
•For multicast consumers running 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.
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 the following publication in the
Rockwell Literature Library :
Replacement Guidelines: Logix5000 Controllers Reference Manual (1756-
RM100).
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, you must 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.
Organize tags for
produced or
consumed data

Produce and Consume a Tag
Chapter 1
Rockwell Automation Publication 1756-PM011J-EN-P - February 2018 15
Guideline Details
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.
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 Logix Designer 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.
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.
Adjust for bandwidth
limitations

Chapter 1
Produce and Consume a Tag
16 Rockwell Automation Publication 1756-PM011J-EN-P - February 2018
Adjustment Description
Reduce your NUT. At a faster NUT, less connections have to share an update slot.
Increase the requested packet interval
(RPI) of your 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.
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.
The produced tag sends its data to one or more consumed tags without using
logic, and can be used simultaneously by multiple controllers.
To create a produced tag:
1. Open the Logix Designer application and choose a controller.
Important: A controller can have both producing and consuming tags, but a
producer cannot consume its own data. The local controller is the
consumer, and the remote controller is the producer.
2. In the Controller Organizer, right-click Controller Tags and click Edit
Tags.
Only controller-scoped tags can be shared.
3. In the Tag Editor, right-click the tag that you want to be a producer,
and click Edit (name of tag) Properties.
Create a produced
tag

Produce and Consume a Tag
Chapter 1
Rockwell Automation Publication 1756-PM011J-EN-P - February 2018 17
4. In the Type box, click Produced.
The Connection button becomes available when Type is either
Produced or Consumed.
5. Click Connection to define the produced tag. The Produced Tag
Connection dialog box opens.
6. In the Max Consumers box, type the number of controllers to
consume (receive) this tag.
7. (optional) Click Advanced to open the Advanced Options dialog box
to change the RPI range limitation, negotiated default, or unicast
connection.

Chapter 1
Produce and Consume a Tag
18 Rockwell Automation Publication 1756-PM011J-EN-P - February 2018
Tip: The Advanced button is available for controllers using version 18
and later of the application.
8. Click OK to close the Produced Tag Connection dialog box.
9. Click OK to close the Tag Properties dialog box.
The consumed tag receives 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.
Before you begin:
•Add the controller that is producing the data to the Controller
Organizer I/O Configuration folder.
To create a consumed tag:
1. Open the Logix Designer application and choose a controller.
Important:
A controller can have both producing and consuming tags, but a
producer cannot consume its own data. The local controller is the
consumer, and the remote controller is the producer.
2. In the Controller Organizer, right-click Controller Tags and click
Edit Tags.
You can consume only controller-scoped tags.
Create a consumed
tag

Produce and Consume a Tag
Chapter 1
Rockwell Automation Publication 1756-PM011J-EN-P - February 2018 19
3. In the Tag Editor, right-click the tag that will consume the data, and
then click Edit (name of tag) Properties.
4. In the Type box, click Consumed.
The Connection button becomes available when Type is either
Produced or Consumed.
5. In the Data Type box, select the data type.
If the producing
controller is Then the data type should be
Logix5000 controller Same data type as the produced tag.
PLC-5C controller User-defined data type with these members.
Data type Description

Chapter 1
Produce and Consume a Tag
20 Rockwell Automation Publication 1756-PM011J-EN-P - February 2018
If the producing
controller is Then the data type should be
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
6. Click Connection to define the consumed tag.
7. In the Producer box, select the controller that produces the data.
If the list is empty, add a remote controller to the Controller Organizer
I/O Configuration folder.
8. In the Remote Data box, type the name or the instance number of the
produced tag.
If the producing controller is Then type or choose
Logix5000 controller Tag name of the produced tag
PLC-5C controller Message number from the
ControlNet configuration of the
PLC-5C controller
9. In the RPI box, enter the requested packet interval (RPI) for the
connection.