Use
CIP
 over
EtherNet/IP

The Common Industrial Protocol
CIP™
over
EtherNet/IP™
protocol enables AADvance controllers to exchange data with controllers supporting the
CIP
 protocol, such as
ControlLogix®
controllers. The
CIP
 network exchanges data using producers and consumers; this network cannot download to a target or monitor a target. The
CIP
 data sharing mechanism is similar to the variable bindings mechanism used in AADvance. For each controller,
CIP
 communication enables defining a produce link and multiple consume links.
WARNING:
CIP
 should only be used to share non-safety data with other controllers. To share safety-related data between AADvance controllers, use SNCP bindings.
The controller supports produce and consume communications to redundancy systems. The support for produce/consume variables is non-interfering; a failure of the
EtherNet/IP
 stack does not interfere with the safe operation of the system.
To use
CIP
 over
EtherNet/IP
, define the required consume and produce links, specify an Ethernet port to connect to the
CIP
 network having the remote controller, then define producer and consumer variables (or structures) for the exchange of data. For
CIP
 consume links, also specify the producer and the
CIP
 path to the producer. At runtime, the controller having producer variables sends values to the remote controller, whereas, the controller having consumer variables pulls values from the remote controller having producer variables.
IMPORTANT: When connecting a controller not supporting
CIP
 to a
CIP
 network, a warning occurs and the connection is not implemented. The default IP address for a connection between a controller and a CIP network is blank. When a valid IP address is not specified, an error when building occurs: 'Network
CIP
: invalid connection properties for (the particular configuration).'
Communications Cycle
Before executing the logic at the start of an application scan, the AADvance controller sets the consumer variables to the most recently received values. The controller updates the producer variables after executing the logic at the end of the application scan. When sending a packet, the AADvance controller uses the most recent value of a producer variable, ensuring the variable uses the expected Requested Packet Interval (RPI).
A consumer variable retains the most recently received value; a default value cannot be set.
To use
CIP
 over
EtherNet/IP
, configure controllers to use the
Unicast
mode since AADvance controllers use unicast for
CIP
.
To configure an AADvance controller to communicate with another controller
  1. Set the first AADvance controller as a
    CIP
     provider.
  2. Set the second controller as a
    CIP
     consumer.
    TIP: After building the project, if the
    Output
     window displays a message indicating
    Multiple CIP network instances found
    , see
    Update Ethernet ports of CIP produce and CIP consume links
    .
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal