background image

Produce and Consume a Tag 

Chapter 1 

 

 

Rockwell Automation Publication 1756-PM011J-EN-P - February 2018 

37

 

The following table provides a description of error messages for situations 
where an RPI is not accepted. 

Scenario Description 

Software 
Version 

I/O Fault Message 

RPI of consumed tag is not within the range of the 
producer. Producer does not support RPI 
negotiation or is not configured to provide a default 
RPI to the consumer. 

Any 

(Code 0111) Requested Packet Interval 
(RPI) out of range. 

RPI of consumed tag is not within the range of the 
producer. Producer is returning default RPI. 
Consumer does not support negotiation or is not 
configured to accept RPI from producer. 

18 and later 

(Code 0112) Requested Packet Interval 
(RPI) out of range. 

17 and earlier 

(Code 0112) Unknown Error. 

RPI of consumer is out of range, but producer 
provides a default RPI and consumer can accept 
default RPI. Network path contains bridge that does 
not support extended error information. For I/O 
connectivity between two controllers, such as 
consuming a tag from a producing controller, both   
controllers must be attached to the same 
EtherNet/IP subnet. Two controllers cannot bridge 
produced or consumed tags over two subnets. For 
more information on setting up your network, refer to 
the following publication in the 

Rockwell Literature 

Library

 

EtherNet/IP Network Configuration User Manual 

(ENET-UM001)

 

18 and later 

(Code 0112) Requested Packet Interval 
(RPI) out of range. Producer provided 
RPI blocked by the network path. 

RPI of consumer is out of range, but producer 
provides a default RPI and consumer can accept 
RPI provided by producer. Network path contains 
scheduled network update time (NUT). 

18 and later 

(Code 0112) Requested Packet Interval 
(RPI) out of range. Cannot use producer 
provided RPI over a path containing a 
scheduled network. 

Prevent connection failures with Compact GuardLogix 5380, 
CompactLogix 5380, CompactLogix 5480, ControlLogix 5580, and 
GuardLogix 5580 controllers 

If a consumer displays error code 0112 and fails to connect to a Compact 
GuardLogix 5380, CompactLogix 5380, CompactLogix 5480, ControlLogix 
5580, or GuardLogix 5580 controller that provides produce tags, 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:   

RPI I/O faults 

Summary of Contents for 1769 CompactLogix

Page 1: ...anual 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 ...

Page 2: ...hole 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 inform...

Page 3: ...o 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 cons...

Page 4: ...ed 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 pro...

Page 5: ...ed 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 ...

Page 6: ......

Page 7: ...ix 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 5...

Page 8: ...b 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 C...

Page 9: ...ional 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 applica...

Page 10: ...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 ...

Page 11: ... 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 determin...

Page 12: ...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 Gua...

Page 13: ...ardLogix 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 reques...

Page 14: ...ontrolLogix 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 ta...

Page 15: ...Logix 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 cons...

Page 16: ...d 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 S...

Page 17: ...vailable 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 ...

Page 18: ...ch 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...

Page 19: ... 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 ...

Page 20: ... 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 Messag...

Page 21: ...the default unless you are configuring a standard consumed tag and the communication path between the producer and consumer does not cross EtherNet IP or is across the backplane Then the check box is cleared and unavailable 11 Click the Status tab to configure the status properties for the consumed tags 12 In the Data Type box select the data type that allows for connection status 13 Click OK to c...

Page 22: ...For example if the produced tag contains 10 REALs enter 20 for the Message size If the PLC 5C controller consumes REALs reconstruct the values When you produce REALs 32 bit floating point values for a PLC 5C controller the PLC 5C controller stores the data in consecutive 16 bit integers The first integer contains the upper leftmost bits of the value The second integer contains the lower rightmost ...

Page 23: ... produce 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 produce 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 ...

Page 24: ...t 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 on page 35 for details If you have multicast consumers running Logix Designer releases v18 and later take the following steps to make sure cons...

Page 25: ...n which is disabled when online must be within Minimum RPI 0 2 ms for ControlLogix controllers and for CompactLogix 5380 controllers and 1 0 ms for all other CompactLogix controllers Maximum RPI 536870 911 ms Default RPI configurable within the minimum maximum range 1769 L2x and 1769 L3x controllers refer to 1769 L2x and 1769 L3x RPI Limits for additional instructions The RPI limits apply only to ...

Page 26: ...ation recommends using the default value of 536870 9 ms 5 Select the Provide Default RPI to Consumer for Out of Range Requests check box to enable the producing tag to provide an RPI to a consuming tag whenever a consuming tag has an RPI outside the range of the producer s Minimum and Maximum RPI and then in the Default RPI box enter the value that the producer provides to the consumer Important S...

Page 27: ... RPI range or default RPI value The Allow Unicast Consumer Connections check box at the bottom of the Advanced Options dialog box is selected by default to allow multiple unicast consumers to consume from the produced tag Clear the Allow Unicast Consumer Connections check box if you are not using Unicast and the controller is running low on controller memory Additional producer resources are alloc...

Page 28: ... consumers of a producer from 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 See RPI limitations and negotiated default on page 23 for more information To set up the consuming controller 1 In the C...

Page 29: ... consuming controller requests an RPI that is out of the producer s configured RPI range As a result an out of range RPI request results in a failed connection 4 Click OK When a consuming controller accepts a default RPI by a producing controller you can verify the acceptance and the RPI value on the Consumed Tag Connection dialog box Before you begin The controller must be online and the consumed...

Page 30: ...e a Tag 30 Rockwell Automation Publication 1756 PM011J EN P February 2018 2 In the Tag Editor right click a consuming tag and click Edit name of tag Properties The Tag Properties dialog box opens 3 In the Type box click Connection ...

Page 31: ...11J EN P February 2018 31 The Consumed Tag Connection dialog box opens On the Connection tab a flag to the right of the RPI box indicates the consuming controller has accepted an RPI provided by the producer The time interval of the RPI also is indicated 4 Click Cancel to exit ...

Page 32: ...the RPI requested by the consuming tag All controllers on the multicast connection will be increased to 3 ms for the API which is the interval the data is actually being produced Version 18 and later The consuming controller is brought online with an RPI configured at 3 ms The producing controller verifies the requested RPI by the consumer is within the RPI limits set up for the producer Since the...

Page 33: ...figured 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 and there is no default set up a 0111 error reports the connection failed Tip See RPI I O Faults on page 37 for an explanation of the error messages Version 18 and later The RPI requested by the consumed tag is not within the RPI limitation range of ...

Page 34: ...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 Tip See RPI I O Faults on page 37 for an explanation of the error messages Version 18 and later The RPI requested by the consumed tag is not within the RPI limitation range of the producer The p...

Page 35: ...nge 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 L2x and 1769 L3x controllers produce data in packet intervals ra...

Page 36: ...consumed tags to use an RPI provided by the producer See RPI Limitations and Negotiated Default on page 23 and Set up the consuming controller on page 28 for procedures to set up the producer and consumer tags to accept a negotiated default RPI For the 1769 L2x and 1769 L3x controllers the Effective Minimum RPI when present is used to determine the fastest packet interval allowed by the tag When t...

Page 37: ... controllers cannot bridge produced or consumed tags over two subnets For more information on setting up your network refer to the following publication in the Rockwell Literature Library EtherNet IP Network Configuration User Manual ENET UM001 18 and later Code 0112 Requested Packet Interval RPI out of range Producer provided RPI blocked by the network path RPI of consumer is out of range but pro...

Page 38: ...igured 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 ...

Page 39: ...e array of data in smaller packets you must be sure that the transmission of a packet is complete before the data is moved into the destination array Produced data over the ControlLogix backplane is sent in 50 byte segments Data transmission occurs asynchronous to a program scan The logic that this section includes uses an acknowledge word to make sure that each packet contains new data before the...

Page 40: ...at produces the array create these tags P Tag Name Type array_ack DINT 2 X array_packet DINT 125 2 Convert array_ack to a consumed tag For Specify Controller Name of the controller that is receiving the packet Remote Tag Name array_ack Both controllers use the same name for this data 3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transf...

Page 41: ... value in array_ack 0 is not equal to the current offset value but array_ack 1 equals 999 the consumer has begun to receive a new packet so the rung moves 999 into the last element of the packet The consumer waits until it receives the value 999 before it copies the packet to the array This guarantees that the consumer has new data ...

Page 42: ...is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet packet 124 If the current transfer tim...

Page 43: ...troller Name of the controller that is sending the packet Remote tag name array_packet Both controllers use the same name for this data 9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags Tag Name Type array DINT x where x equals the number of elements to transfer plus 122 elements array_offset DINT 10 Create or op...

Page 44: ...to array_ack 0 which signals that the copy is complete Array_ack 1 resets to zero and waits to signal the arrival of a new packet If the last element of the packet is not equal to 999 the transfer of the packet to the controller may not be complete so 999 moves to array_ack 1 This signals the producer to return the value of 999 in the last element of the packet to verify the transmission of the pa...

Page 45: ... unscheduled and are executed only during the system overhead portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer You can improve the transfer time by increasing the system overhead time slice but this diminishes the performance of the continuous task ...

Page 46: ......

Page 47: ...rifying RPI 29 ControlNet bandwidth limits 15 create produced tag 16 D default RPI 23 E error messages RPI 36 I I O faults 36 L L2x controller RPI limits 34 L3x controller RPI limits 34 limitations bandwidth 15 RPI 23 P PLC 5C share data 22 produced tag connection requirements 12 create 16 producer creating tag 16 RPI scenarios 31 R RPI I O faults 36 limitations setting default 23 S scenarios RPI ...

Page 48: ...xperience a problem within the first 24 hours of installation review the information that is contained in this manual You can contact Customer Support for initial help in getting your product up and running United States or Canada 1 440 646 3434 Outside United States or Canada Use the Worldwide Locator available at http www rockwellautomation com locations or contact your local Rockwell Automation...

Reviews: