
Installation and User Guide
DS6x00 EtherNet/IP Scanner
Rev 1.02
ETHERNET/IP IS A CERTIFIABLE STANDARD
The groups supporting EIP plan to ensure a comprehensive, consistent standard by careful,
multi-vendor attention to the specification and through certified test labs as has been done with
DeviceNet and ControlNet. Certification programs modeled after the programs for DeviceNet
and ControlNet will ensure the consistency and quality of field devices.
EIP is built on a widely accepted protocol layer
EIP is constructed from a very widely implemented standard used in DeviceNet and ControlNet
called the Control and Information Protocol (CIP) and is illustrated on the attached drawing. This
standard organizes networked devices as a collection of objects. It defines the access, object
behavior and extensions which allow widely disparate devices to be accessed using a common
mechanism. Over 300 vendors now support the CIP protocol in present day products. Using this
technology in EIP means that EIP is based on a widely understood, widely implemented standard
that does not require a new technology shakedown period.
CIP OVERVIEW
The Communications and Information Protocol (CIP) is a communications protocol for
transferring automation data between two devices. In the CIP Protocol, every network device
represents itself as a series of objects. Each object is simply a grouping of the related data values
in a device. For example, every CIP device is required to make an Identity object available to the
network. The identity object contains related identity data values called attributes. Attributes for
the identity object include the vendor ID, date of manufacture, device serial number and other
identity data. CIP does not specify at all how this object data is implemented, only what data
values or attributes must be supported and that these attributes must be available to other CIP
devices.
The Identity object is an example of a required object. There are three types of objects defined by
the CIP protocol:
REQUIRED OBJECTS
Required objects are required by the specification to be included in every CIP device. These
objects include the Identity object, a Message Router object and a Network object.
The identity object contains related identity data values called attributes. Attributes for the
identity object include the vendor ID, date of manufacturer, device serial number and other
identity data.
A Network object contains the physical connection data for the object. For a CIP device on
DeviceNet the network object contains the MacID and other data describing the interface to the
CAN network. For EIP devices, the network object contains the IP address and other data
describing the interface to the Ethernet port on the device.
© 2004 Datalogic S.p.A. – All Right Reserved
Page 7 of 54