AXL E EIP DI16 M12 6P
8426_en_04 PHOENIX CONTACT 15 / 26
11 EtherNet/IP™ object classes, messages, and services
The device supports the Common Industrial Protocol (CIP) by using digital input points (DIPs) according to the ODVA
specification. EtherNet/IP™ uses the Common Industrial Protocol (CIP) as the application layer. IP and TCP or UDP are used
for the network and transport layers. CIP and EtherNet/IP™ are standardized by the ODVA on a manufacturer-neutral basis.
The Common Industrial Protocol is an object-oriented protocol with two different types of communication between a controller
and termination devices.
The following table describes the two communication types.
11.1 CIP class and instance services
The device supports the following class services and instance services:
11.2 CIP object classes
The device supports the following CIP object classes:
Connection type Description
Explicit messaging Explicit messaging is based on the request / response principle. This means that a controller or an
engineering system sends a request and the termination device responds.
For example, explicit messaging can be used for configuration and/or diagnostics.
Implicit messaging Implicit messaging is used for the cyclic transmission of I/O data.
That means, for example, that a termination device sends an analog value which is present at a
termination device input. The time for a transmission cycle can be set via the requested packet
interval (RPI).
Service code Service name
dec hex
01 01 Get_Attribute_All
02 02 Set_Attribute_All
05 05 Reset
09 09 Delete
14 0E Get_Attribute_Single
16 10 Set_Attribute_Single
Class code Object type
dec hex
01 01 Identity object
04 04 Assembly object
06 06 Connection manager object
08 08 Digital input point object
71 47 Device level ring object
72 48 Quality of Service object
245 F5 TCP/IP interface object
246 F6 Ethernet link object
