Produce and Consume a Tag
Chapter 1
Rockwell Automation Publication 1756-PM011J-EN-P - February 2018
35
The RPI is outside the range of the producing controller’s RPI Limits. A
default RPI is set up for the producing controller. The consumer is set up to
accept the RPI provided by the producer.
Version 17 and earlier:
The RPI requested by the consumed tag is not
within the range of the producer. The connection is rejected and a 0112 error
is reported that the connection failed. You must re-enter an RPI that is within
the range configured on the produced tag. If a version 17 consumer is trying
to connect with a version 18 producer and the RPI is outside the range of the
producer, a 0112 error reports the connection failed.
Version 18 and later:
The RPI requested by the consumed tag is not within
the RPI limitation range of the producer. The producer is configured to
provide an RPI default. The producer sends the default RPI to the consumer.
The consumer is set up to accept the RPI provided by the producer. The
connection is successful and the multicast connection accepts the new RPI of
5 ms.
All controllers, with the exception of the CompactLogix 1769-L2
x
and 1769-
L3
x
controllers, produce data in packet intervals ranging from
0.196…536870.911 ms. The 1769-L2
x
and 1769-L3
x
controllers produce
only in packet intervals of 2, 4, 8, 16, 32, 64, 128, 256, 512, or 1024 ms.
You are not confined to entering these exact values when configuring an RPI
limitation range and default RPI for the 1769-L2
x
and 1769-L3
x
controllers.
However, if an unsupported packet interval is entered, then the Logix
Designer application may override the unsupported packet interval with a
supported packet interval. When this occurs, the new ‘effective’ value is
displayed separately next to the unsupported value that was entered.
Scenario 4
1769-L2x and 1769-
L3x RPI limits
