Cip within the application scan cycle -11, About the rslogix 5000 configuration -11, Rules for counting connections – Rockwell Automation AADvance Controller Configuration Guide User Manual
Page 181
Document: 553633
ICSTT-RM405f-EN-P
Issue 07
8-11
You can now examine the structure of 'T' within the Dictionary:
The AADvance controller sets the values of the elements
T.ConnectionState.RunMode and T.ConnectionState. ConnectionFaulted
based upon the run mode of the remote Logix controller and the presence of a
communications fault.
CIP within the Application Scan Cycle
The AADvance controller updates variables configured for CIP production with new
values at the end of each application scan cycle, after the logic has been executed.
Variables configured for CIP production honour the Requested Packet Interval (RPI)
expected by the Logix controller by providing the most recent value of the variable
each time a packet is sent. Variables configured for CIP consumption are updated with
the last received value at the beginning of each application cycle, before the logic is
executed.
About the RSLogix 5000 Configuration
Within the RSLogix configuration it is necessary to configure the AADvance
controller as a CIP provider. Presently this is done in the I/O configuration Tree, by
expanding the CLX Ethernet I/P Module to display the Ethernet Network tree, then
insert a new module.
You can then proceed to configure production and consumption (‘produce’ and
‘consume’) variables normally. When you configure a variable for consumption, select
the producing AADvance controller by name as defined in the I/O Config Tree.
Rules for Counting Connections
These rules are for counting connections for produced and consumed tags in a
ControlLogix system, but are useful to know when using production and consumption
variables to exchange data with an AADvance controller using CIP over Ethernet/IP.
Note: The AADvance Controller will support a maximum of 255 Connections.
Use the following rules to calculate how many connections are required in the
controller for a produced or consumed tag:
Each produced tag reserves (1 + the defined number of consumers) connections in
the controller.