Phoenix Contact AXL E EIP IOL8 DI4 M12 6P User manual

User manual
Network-specific properties of the
AxiolineE EtherNet/IPTM IO-Link devices
UM EN AXL E EIP IOL

2020-12-08
PHOENIX CONTACT GmbH & Co. KG • Flachsmarktstraße 8 • 32825 Blomberg • Germany
phoenixcontact.com
108007_en_02
Network-specific properties
of the AxiolineE EtherNet/IPTM IO-Link devices
This user manual is valid for Axioline E EtherNet/IPTM IO-Link devices.
AXL E EIP IOL8 DI4 M12 6M, Order No. 2701491
AXL E EIP IOL8 DI4 M12 6P, Order No. 2701496
User manual
Revision 02

108007_en_00 PHOENIX CONTACT 3 / 42
Table of contents
1 For your safety ...........................................................................................................................5
1.1 Labeling of warning notes...................................................................................... 5
1.2 Qualification of users ............................................................................................. 5
1.3 Product changes ................................................................................................... 6
1.4 Security in the network .......................................................................................... 6
2 EtherNet/IP™ object classes, messages, and services .............................................................7
2.1 CIP class services ................................................................................................. 7
2.2 CIP object classes ................................................................................................. 8
2.3 Identity object (class code 01hex) .......................................................................... 9
2.4 Instance attributes ................................................................................................. 9
2.5 Message router object (class code 02hex) ........................................................... 10
2.6 Assembly object (class code 4hex) ...................................................................... 10
2.7 Connection manager object (class code 06hex)................................................... 11
2.8 Device level ring object (class code 47hex).......................................................... 12
2.9 Quality of service object (class code 48hex)......................................................... 13
2.10 IO-Link parameter object (class code 80hex) ....................................................... 14
2.11 TCP/IP object (Class code F5hex)........................................................................ 19
3 EtherNet/IP™ Assembly instances ..........................................................................................23
3.1 Input process data ............................................................................................... 24
3.2 Output process data ............................................................................................ 28
4 Startup .....................................................................................................................................35
4.1 Delivery state/default settings.............................................................................. 35
4.2 Starting the firmware............................................................................................ 35

UM EN AXL E EIP IOL
4 / 42 PHOENIX CONTACT 108007_en_02
5 IO-Link master .........................................................................................................................36
6 Connection monitoring/Substitute behavior .............................................................................36
7 Diagnostic messages ...............................................................................................................36
8 Firmware update ......................................................................................................................37
9 Restarting the device (Reboot) ................................................................................................37
10 Restoring the device (Factory default setting) ..........................................................................38
11 WBM - Web-based management .............................................................................................38
12 SNMP - Simple Network Management Protocol ......................................................................39
13 DLR - Device Level Ring ..........................................................................................................39
14 Quick Connect .........................................................................................................................39
15 Connection types .....................................................................................................................40
16 Device Description File (EDS) ..................................................................................................40
17 Data format ..............................................................................................................................40

For your safety
107945_en_02 PHOENIX CONTACT 5 / 42
1Foryoursafety
Read this user manual carefully and keep it for future reference.
1.1 Labeling of warning notes
1.2 Qualification of users
The use of products described in this user manual is oriented exclusively to:
– Qualified electricians or persons instructed by them. The users must be familiar with the
relevant safety concepts of automation technology as well as applicable standards and
other regulations.
– Qualified application programmers and software engineers. The users must be familiar
with the relevant safety concepts of automation technology as well as applicable stan-
dards and other regulations.
This symbol indicates hazards that could lead to personal injury.
There are three signal words indicating the severity of a potential injury.
DANGER
Indicates a hazard with a high risk level. If this hazardous situation is not
avoided, it will result in death or serious injury.
WARNING
Indicates a hazard with a medium risk level. If this hazardous situation is not
avoided, it could result in death or serious injury.
CAUTION
Indicates a hazard with a low risk level. If this hazardous situation is not avoided,
it could result in minor or moderate injury.
This symbol together with the NOTE signal word alerts the reader to a situation
which may cause damage or malfunction to the device, hardware/software, or
surrounding property.
Here you will find additional information or detailed sources of information.

UM EN AXL E EIP IOL
6 / 42 PHOENIX CONTACT 107945_en_02
1.3 Product changes
Changes or modifications to hardware and software of the device are not permitted.
Incorrect operation or modifications to the device can endanger your safety or damage the
device. Do not repair the device yourself. If the device is defective, please contact
Phoenix Contact.
1.4 Security in the network
NOTE: : Risk of unauthorized network access
Connecting devices to a network via Ethernet always entails the risk of unauthorized ac-
cess to the network.
Therefore, please check your application for any option of deactivating active communi-
cation channels . Setting passwords to prevent third parties from accessing the controller
without authorization and modifying the system.
Because of the controller's communication interfaces, we advise against using the con-
troller in safety-critical applications without additional security appliances.
Please take additional protective measures according to the IT security requirements and
the standards applicable to your application (for instance virtual networks (VPN) for re-
mote maintenance access, firewalls, etc.) for protection against unauthorized network ac-
cess.
On first request, you shall release Phoenix Contact and the companies associated with
Phoenix Contact GmbH & Co. KG, Flachsmarktstraße 8, 32825 Blomberg in accordance
with §§ 15 ff. AktG or German Stock Corporation Act (hereinafter collectively referred to
as "Phoenix Contact") from all third-party claims that are made due to improper use.
For the protection of networks for remote maintenance via VPN, Phoenix Contact offers
the mGuard product series security appliances which you can find described in the latest
Phoenix Contact catalog (phoenixcontact.net/products).
Additional measures for protection from unauthorized network access can be found in the
AH EN INDUSTRIAL SECURITY application note. The application note can be download-
ed at phoenixcontact.net/products.

108007_en_02 PHOENIX CONTACT 7 / 42
2 EtherNet/IP™ object classes, messages, and services
The device supports the Common Industrial Protocol (CIP) according to the ODVA secifica-
tion. EtherNet/IP™ uses the Common Industrial Protocol as the application layer. IP and
TCP or UDP are used for the network and transport layers. CIP and EtherNet/IP™ are stan-
dardized 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.
2.1 CIP class services
The device supports the following class services and instance services:
Connection type Description
Explicit messaging 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 in-
terval (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
75 4B Read_ISDU
78 4C Write_ISDU

UM EN AXL E EC IOL
8 / 42 PHOENIX CONTACT 108007_en_02
2.2 CIP object classes
The device supports the following CIP object classes:
Class code Object type
dec hex
01 01 Identity object
02 02 Message router object
04 04 Assembly object
06 06 Connection manager object
09 09 Digital output point object
71 47 Device level ring object
72 48 Quality of service object
128 80 IO-Link device parameter (Vendor specific)
245 F5 TCP/IP interface object
246 F6 Ethernet link object

108007_en_02 PHOENIX CONTACT 9 / 42
2.3 Identity object (class code 01hex)
The Identity object is required by all devices and provides the device ID and general infor-
mation about the device.
Class attributes
Attribute Name Access Data type Value
1Version GetUINT1
2 Max instance Get UINT 1
6 Max class attribute Get UINT 7
7 Max instance attribute Get UINT 9

UM EN AXL E EC IOL
10 / 42 PHOENIX CONTACT 108007_en_02
2.4 Instance attributes
Common services
Attribute Name Access Data type Value
1 Vendor ID Get UINT 562 ("Phoenix Contact")
2 Product type Get UINT 12 ("Communications adapter")
3 Product code Get UINT 8179
4 Version Get STRUCT
of:
1
Major revision USINT 1
Minor revision USINT 1
5 Status Get WORD Bit 0 Self-Testing or unknown
Bit 1 Reserved
Bit 2 At least one fault I/O connection
Bit 3 No I/O connections established
Bit 4 Reserved
Bit 5 Major Fault
Bit 6 At least one I/O connection
in run mode.
Bit 7 At least one I/O connection
established, all in idle mode.
Bit 8 Reserved
Bit 9 Reserved
Bit 10 ... bit 15 Vendor specific
6 Serial number Get UDINT Is fixed in production process
7 Product name Get STRING AXL E EIP IOL8 DI4 M12 6M/AXL E EIP IOL8 DI4 M12 6P
8 State Get USINT 0 = Nonexistent
1 = Device self testing
2 = Standby
3 = Operational
4 = Major recoverable fault
5 = Major unrecoverable fault
6 ... 254 = Reserved
255 = Default for Get_ Attribute_All service
9 Configuration consistency
value
Get UINT CRC checksum
Service code Class Instance Service name
dec hex
01 01 Yes Yes Get_Attribute_All
05 05 No Yes Reset
14 0E Yes Yes Get_Attribute_Single
16 10 No Yes Set_Attribute_Single

108007_en_02 PHOENIX CONTACT 11 / 42
2.5 Message router object (class code 02hex)
The Message router object provides a messaging connection point through which a client
may address a service to any object class or instance residing in the physical device.
The device does not support any object attributes.
2.6 Assembly object (class code 4hex)
The Assembly object combines attributes of multiple objects to allow data to or from each
object to be sent or received via a single connection.
Class attributes
Instance attributes
Common services
Attribute Name Access Data type Value
1Version GetUINT2
Attribute Name Access Data type Value
3 Data Get, Set ARRAY of
Byte
Current Process data of the correspondent Assembly
instance
4 Size Get UINT Number of bytes in attribute 3
Service code Class Instance Service name
dec hex
14 0E Yes Yes Get_Attribute_Single
16 10 No Yes Set_Attribute_Single

UM EN AXL E EC IOL
12 / 42 PHOENIX CONTACT 108007_en_02
2.7 Connection manager object (class code 06hex)
The Connection manager object allocates and manages the internal resources that are
used for I/O and Explicit messaging connections.
Class attributes
Class attributes
The device does not support any instance attributes.
Common services
Attribute Name Access Data type Value
1Version GetUINT1
2 Max instance Get UINT 1
Service code Class Instance Service name
dec hex
14 0E Yes Yes Get_Attribute_Single

108007_en_02 PHOENIX CONTACT 13 / 42
2.8 Device level ring object (class code 47hex)
The Device level ring object (DLR) is the interface for configuration and status information
for the DLR protocol.
Class attributes
Instance attributes
Common services
Attribute Name Access Data type Value
1Version GetUINT3
Attribute Name Access Data type Value/description
1 Network topology Get USINT 0 = Linear
1 = Ring
2 Network status Get USINT 0 = Normal
1 = Ring fault
2 = Unexpected loop detected
3 = Partial network fault
4 = Rapid fault/Restore cycle
10 Active supervisor address Get STRUCT
of:
IP and/or MAC address of the active ring supervisor
UDINT Supervisor IP address
ARRAY of
6 USINTs
Supervisor MAC address
12 Capability flags Get DWORD Bit 0 Announced-based ring node
Bit 1 Beacon-based ring note
Bit 2 ... bit 4 Reserved
Bit 5 Supervisor capable
Bit 6 ... bit 31 Reserved
Service code Class Instance Service name
dec hex
1 01 Yes Yes Get_Attribute_All
14 0E Yes Yes Get_Attribute_Single

UM EN AXL E EC IOL
14 / 42 PHOENIX CONTACT 108007_en_02
2.9 Quality of service object (class code 48hex)
Quality of service (QoS) affects the forwarding and handling of data streams and results in
individual data streams being given differential treatment (usually preferential). QoS can be
used, e.g., to guarantee a transmission bandwidth for individual data streams. The device
uses QoS in connection with prioritization.
Class attributes
Instance attributes
Common services
Attribute Name Access Data type Value
1Version GetUINT1
2 Max instance Get UINT 1
Attribute Name Access Data type Value/description
1 802.1Q tag enable Get, Set USINT 0 = off; 1 = on
4 DSCP urgent Get, Set USINT DSCP value for CIP transport class 0/1 Urgent priority
message (default 55)
5 DSCP scheduled Get, Set USINT DSCP value for CIP transport class 0/1 Scheduled pri-
ority message (default 47)
6 DSCP high Get, Set USINT DSCP value for CIP transport class 0/1 High priority
message (default 43)
7 DSCP low Get, Set USINT DSCP value for CIP transport class 0/1 Low priority
message (default 31)
8 DSCP explicit Get, Set USINT DSCP value for CIP explicit messages (transport class
2/3 and UCMM) and all other EtherNet/IP™ encapsu-
lation messages (default 27)
Service code Class Instance Service name
dec hex
14 0E Yes Yes Get_Attribute_Single
16 10 No Yes Set_Attribute_Single

108007_en_02 PHOENIX CONTACT 15 / 42
2.10 IO-Link parameter object (class code 80hex)
The IO-Link parameter object is a vendor-specific implementation to access IO-Link device
parameters. The object has the class instance 0 and the instance 1. The class instance 1
addresses the IO-Link master.
Class attributes
Instance attributes
The IO-Link ports are addressed via the corresponding instance attributes number, see
section "Read_ ISDU" or "Write_ISDU".
Common services
Attribute Name Access Data type Value
1Version GetUINT1
2 Max instance Get UINT 1
3 Max class attribute Get UINT 8 (Number of the IO-Link ports)
Service code Class Instance Service name
dec hex
14 0E Yes No Get_Attribute_Single
75 4B No Yes Read_ISDU
78 4C No Yes Write_ISDU

UM EN AXL E EC IOL
16 / 42 PHOENIX CONTACT 108007_en_02
Read_ISDU
This service is used to read IO-Link device parameters.
Request
Response
The response to the request can either be positive or negative.
- Positive Response
If the request service was successful ("General Status" of the CIP service response is = 0),
the response has the following structure:
MSG Config Description
Class 80hex IO-Link parameter object
Instance 1 Addressing of the IO-Link masters
Instance attributes 1 ... 8 IO-Link port number
Service code 4Bhex Read_ISDU
Data Read ISDU Service request parameter
Name Data type Description
Index UINT IO-Link ISDU object index
Sub-Index USINT IO-Link ISDU object Sub-Index
EtherNet/IP™ uses the little endian format (Intel), IO-Link the big endian format (Motorola).
For the IO-Link process data, no byte swapping is performed.
Name Data type Description
ISDU Data ARRAY of Byte Maximal 232 bytes

108007_en_02 PHOENIX CONTACT 17 / 42
- Negative Response
If the request service was not successful ("General Status" of the CIP Service Response un-
equal 0), the response has the following structure:
Example: Reading an IO-Link device object
The following table shows the examplary structure of a message (MSG) for reading the Ven-
dorName of an IO-Link device, which is connected to port 7.
Request
Response
Depending on wheter the response is positive or negative, the data structure contains either
the VendorName or additional error codes.
Name Data type Value/Description
IO-Link master Error UINT 1 Service not available
2 Port blocked
3Timeout
4 Invalid index
5 Invalid sub index
6 Wrong port
7 Wrong port function
8 Invalid length
9 ISDU not supported
IO-Link Device Error USINT Please refer to the specific IO-Link device data sheet
IO-Link Device Additional Error USINT Please refer to the specific IO-Link device data sheet
MSG Config Description
Class 80hex IO-Link parameter object
Instance 1 Addressing of the IO-Link master
Instance attributes 7IO-Linkport7
Service code 4Bhex Read ISDU
Data 0010hex IO-Link ISDU object index: 0010hex (VendorName)
00hex IO-Link ISDU objekt Sub-Index: 00hex (no Sub-Index)

UM EN AXL E EC IOL
18 / 42 PHOENIX CONTACT 108007_en_02
Write_ISDU
This service is used to write IO-Link device parameters.
Request
Response
The response to the request can either be positive or negative.
- Positive Response
If the request service was successful ("General Status" of the CIP service response is = 0),
the response does not contain any further data.
- Negative Response
If the request service was not successful ("General Status" of the CIP service response un-
equal 0), the response has the following structure:
MSG Config Description
Class 80hex IO-Link parameter object
Instance 1 Addressing of the IO-Link masters
Instance attributes 1 ... 8 IO-Link port number
Service codes 4Chex Write ISDU
Data Write ISDU Service request parameter
Name Data type Description
Index UINT IO-Link ISDU object index
Sub-Index USINT IO-Link ISDU object Sub-Index
Data ARRAY of Byte IO-Link ISDU data
(max. 232 bytes)
EtherNet/IP™ uses the little endian format (Intel), IO-Link the big endian format (Motorola).
For the IO-Link process data, no byte swapping is performed.
Name Data type Value/Description
IO-Link Master Error UINT 1 Service not available
2 Port blocked
3Timeout
4 Invalid index
5 Invalid sub index
6 Wrong port
7 Wrong port function
8 Invalid length
9 ISDU not supported
IO-Link Device Error USINT Please refer to the specific IO-Link device data sheet
IO-Link Device Additional Error USINT Please refer to the specific IO-Link device data sheet

108007_en_02 PHOENIX CONTACT 19 / 42
Example: Writing to an IO-Link device object
The following table shows the exemplary structure of a message (MSG) for writing the Ap-
plication Specific Name Object (18hex) of the Phoenix Contact Device PSK AFS5000IOL
(Order No 2700705), which is connected to port 5.
Request
Response
If the request service was successful, the general status of the CIP service response is = 0.
In the event of an error the general status is unequal 0.
MSG Config Description
Class 80hex IO-Link parameter object
Instance 1 Addressing of the IO-Link master
Instance attributes 5IO-Linkport7
Service code 4Chex Write ISDU
Data 0018hex IO-Link ISDU objekt index: 0018hex
(Application specific name)
00hex IO-Link ISDU object Sub-Index: 00hex (no Sub-Index)
[0] 4F
[1] 75
...
[13] 5F
[14] 31
[15] 00
IO-Link ISDU data: The object has 16 bytesof data.
- ASCII: Outside_Meter_1 (= 15 byte)
- Hex: 4f 75 74 73 69 64 65 5f 4d 65 74 65 72 5f 31
- The last byte is filled with zeros.

UM EN AXL E EC IOL
20 / 42 PHOENIX CONTACT 108007_en_02
2.11 TCP/IP object (Class code F5hex)
The TCP/IP interface object makes it is possible to configure the physical network interface.
These include setting for example the IP address, subnet mask and gateway address.
Class attributes
Instance attributess
Attribute Name Access Data type Value
1 Revision Get UINT 3
2Maxinstance Get UINT 1
Attribute Name Access Data type Description
1 Status Get DWORD Bit 0 ... bit 3 Interface configuration status
Bit 4 Mcast pending (always 0)
Bit 5 Interface configuration pending
Bit 6 AcdStatus
Bit 7 AcdFault
Bit 8 ... bit 31 Reserved
2 Configuration capability Get DWORD Bit 0 BOOTP client
Bit 1 Not supported
Bit 2 DHCP client
Bit 3 Not supported
Bit 4 TCP/IP config setable via ETH/IP
Bit 5 Not supported
Bit 6 Not supported
Bit 7 AcdCapable
Bit 8 ... bit 31 Reserved
3 Configuration control Get, Set DWORD Bit 0 ... bit 3 0 = The device use static IP configura-
tion.
1 = The device use BOOTP.
2 = The device use DHCP.
Bit 4 Not supported
Bit 5 ... bit 31 Reserved
4 Physical link object Get STRUCT of: Path to Physical link object
Path size UINT 4
Path Padded EPATH 20hex, F6hex, 25hex, 01hex