Use of the common industrial protocol (cip), Understand the producer/consumer model – Rockwell Automation 1732E-IB16M12SOEDR EtherNet/IP ArmorBlock supporting Sequence of Events User Manual

Page 10

Advertising
background image

Publication 1732E-UM002A-EN-P - March 2010

2 About 1732E ArmorBlock Modules

Contact Rockwell Automation if you need software or firmware upgrades to
use this equipment.

For a complete ControlLogix compatibility matrix, see publication

IA-AT003

.

Use of the Common
Industrial Protocol (CIP)

The 1732E-IB16M12SOEDR uses the Common Industrial Protocol (CIP).
CIP is the application layer protocol specified for EtherNet/IP, the Ethernet
Industrial Protocol, as well as for ControlNet and DeviceNet. It is a
message-based protocol that implements a relative path to send a message
from the “producing” device in a system to the “consuming” devices.

The producing device contains the path information that steers the message
along the proper route to reach its consumers. Because the producing device
holds this information, other devices along the path simply pass this
information; they do not need to store it.

This has two significant benefits:

You do not need to configure routing tables in the bridging modules,
which greatly simplifies maintenance and module replacement.

You maintain full control over the route taken by each message, which
enables you to select alternative paths for the same end device.

Understand the
Producer/Consumer Model

The CIP “producer/consumer” networking model replaces the old
source/destination (“master/slave”) model. The producer/consumer model
reduces network traffic and increases speed of transmission. In traditional I/O
systems, controllers poll input modules to obtain their input status. In the CIP
system, input modules are not polled by a controller. Instead, they produce
their data either upon a change of state (COS) or periodically. The frequency
of update depends upon the options chosen during configuration and where
on the network the input module resides. The input module, therefore, is a
producer of input data and the controller is a consumer of the data.

The controller can also produce data for other controllers to consume. The
produced and consumed data is accessible by multiple controllers and other
devices over the EtherNet/IP network. This data exchange conforms to the
producer/consumer model.

Product

Firmware Version / Software Release

1732E-IB16M12SOEDR

Firmware rev. 1.6 or later

1756-EN2T or 1756-EN2TR module

2.3 (or later version of major revision 2) when
using RSLogix 5000 v17
3.x version when using RSLogix 5000 v18 or later

RSLogix 5000 software

17 or later

RSLinx software

2.56 or later

Advertising