Chapter 1
Produce and Consume a Tag
24
Rockwell Automation Publication 1756-PM011J-EN-P - February 2018
Tip:
The controller’s backplane and Ethernet ports can support different RPIs. If
multiple consumers need to connect to the controller at different RPIs, you
can configure them to connect through the backplane or the Ethernet port.
See
Connection requirements of a produced or consumed tag
for
more information.
Behavior in releases v18 to v27
In versions 18 and earlier, controllers can be programmed to enhance the
requested packet interval (RPI) acceptance between producing and
consuming tags within specified limitations for multicast connections. A
producing controller verifies that the RPI of incoming connections are within
the produced tag settings. If the consuming tag’s RPI falls outside the
configured range, a producing controller will reject the incoming RPI and
may provide an RPI (default) to the consuming controller.
This optional default RPI applies only if the consuming controller is set up to
allow its consumed tags to use an RPI provided by the producer. You can
choose to not use the default value. However, you will have to manually
change a rejected RPI to make the value within the limitation settings for the
produced tag.
Tip:
1769-L2x and 1769-L3x controllers have additional RPI information. See
1769-L2x and 1769-L3x RPI Limits
for details.
If you have multicast consumers running Logix Designer releases v18 and
later, take the following steps to make sure consumers of produce tags can
connect:
•
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
.
Behavior in releases v17 and earlier
When using releases v17 and earlier of the application, an incoming RPI of a
consuming controller will be accepted by the producer. No default RPI is
offered by the producing controller. The packet intervals of existing
connections from other consumers could be sped up on multicast
connections.
The RPI limitations (the range set on the produced tag) and the default
process applies only to multicast connections on unscheduled networks. This
feature is unavailable for controllers on the ControlNet network or unicast
connections. Scheduled bandwidths on the ControlNet network transmit
critical data at pre-determined intervals of time.