AXL E EIP DI16 M12 6M
Axioline E EtherNet/IP™ device,
metal housing, 16 inputs, 24 V DC,
M12 fast connection technology
Data sheet
8421_en_01
1
© PHOENIX CONTACT 2015-09-24
Description
The Axioline E device is designed for use within an
EtherNet/IP™ network.
EtherNet/IP™ features
The device is designed for use in systems manufacturing.
–
–
–
It is suitable for use without a control cabinet under harsh industrial conditions.
–
It is used to acquire digital signals.
The Axioline E device can be used on tool platforms, directly
on welding robots or in conveying technology, for example.
–
–
–
2 Ethernet ports (with integrated switch)
Minimum cycle time of 1 ms (RPI)
Supported protocols: ACD, DLR, IGMP v2
SNMP v1, HTTP, TFTP, FTP, BootP, DHCP
Specification: CIP Edition 3.11;
EIP adaptation of CIP 1.12
Device description using EDS file
Firmware can be updated
Integrated web server for web-based management
Axioline E features
–
–
–
–
–
–
Connection to EtherNet/IP™ network
using M12 connectors (D-coded)
Transmission speed of 10 Mbps and 100 Mbps
Connection of digital sensors
to M12 connectors (A-coded)
Diagnostic and status indicators
Short-circuit and overload protection
of the sensor supply
IP65/67 degree of protection
This data sheet is only valid in association with the associated user manual.
Make sure you always use the latest documentation.
It can be downloaded from the product at phoenixcontact.net/products.
AXL E EIP DI16 M12 6M
2
Table of contents
1
Description .............................................................................................................................. 1
2
Table of contents ..................................................................................................................... 2
3
Ordering data .......................................................................................................................... 3
4
Technical data ......................................................................................................................... 4
5
Internal circuit diagram ............................................................................................................ 7
6
Pin assignment ........................................................................................................................ 8
7
Connection example.............................................................................................................. 10
8
Connection notes .................................................................................................................. 10
9
Configuration via rotary encoding switch ............................................................................... 11
10
Local status and diagnostic indicators ................................................................................... 13
11
EtherNet/IP™ object classes, messages, and services......................................................... 15
12
EtherNet/IP™Assembly instances......................................................................................... 24
13
Startup................................................................................................................................... 25
14
SNMP - Simple Network Management Protocol .................................................................... 26
15
DLR - Device Level Ring........................................................................................................ 26
16
WBM - Web-based management .......................................................................................... 26
17
Firmware update.................................................................................................................... 26
18
Quick Connect....................................................................................................................... 26
19
Connection types................................................................................................................... 26
20
Device description (EDS) ...................................................................................................... 26
8421_en_02
PHOENIX CONTACT
2
AXL E EIP DI16 M12 6M
3
Ordering data
Description
Type
Order No.
Pcs. / Pkt.
Axioline E EtherNet/IP™ device in a metal housing with 16 digital inputs,
24 V DC, M12 fast connection technology
AXL E EIP DI16 M12 6M
2701488
1
Accessories
Type
Order No.
Pcs./Pkt.
An M12 screw plug for the unoccupied M12 sockets of the sensor/actuator PROT-M12
cable, boxes and flush-type connectors (Protection and sealing elements)
1680539
5
Mounting plate for Axioline E metal devices (Assembly)
AXL E MP 60
2701761
1
Snap-in markers, Sheet, white, unlabeled, can be labeled with:
THERMOMARK CARD, BLUEMARK CLED, BLUEMARK LED,
TOPMARK LASER, Mounting type: snapped into marker carrier,
Lettering field: 7 x 10 mm (Marking)
UCT-EM (7X10)
0830765
10
Documentation
Type
Order No.
Pcs. / Pkt.
User manual, English, Axioline E: system and installation
UM EN AXL E SYS INST
-
-
Application note, English:
Updating the firmware of AXL E devices using the Windows Explorer
AH EN FIRMWARE UPDATE AXL E
-
-
Additional ordering data
For additional accessories, visit phoenixcontact.net/products.
8421_en_02
PHOENIX CONTACT
3
AXL E EIP DI16 M12 6M
4
Technical data
Dimensions (nominal sizes in mm)
194,5
60
38
185
Width
60 mm
Height
185 mm
Depth
38 mm
Note on dimensions
The height is 194.5 mm including the mounting plate. With fixing clips pulled out,
the height is 212 mm. The depth is 38 mm including the mounting plate (30.5 mm
without the mounting plate).
General data
Housing material
Zinc die-cast
Weight
750 g
Ambient temperature (operation)
-25 °C ... 60 °C
CAUTION: Risk of burns
If the device is used at an ambient temperature above 50°C, the contact temperature of metal surfaces may exceed 70°C.
Ambient temperature (storage/transport)
-25 °C ... 85 °C
Permissible humidity (operation)
5 % ... 95 %
Permissible humidity (storage/transport)
5 % ... 95 %
Air pressure (operation)
80 kPa ... 108 kPa (up to 3000 m above sea level)
Air pressure (storage/transport)
70 kPa ... 106 kPa (up to 3000 m above sea level)
Degree of protection
IP65/67
Protection class
III, IEC 61140, EN 61140, VDE 0140-1
Connection data
Connection method
M12 connector
Interface EtherNet/IP™
Number
2
Connection method
M12 connectors, D-coded
Designation connection point
Copper cable
Number of positions
4
Transmission speed
10/100 MBit/s (with auto negotiation)
Cycle Time
min. 1 ms (RPI)
8421_en_02
PHOENIX CONTACT
4
AXL E EIP DI16 M12 6M
EtherNet/IP™
Equipment type
EtherNet/IP™ slave
EtherNet/IP™ protocols
ACD, DLR, IGMP v2
Additional protocols
SNMP v1, HTTP, TFTP, FTP, BootP, DHCP
Specification
CIP Edition 3.11
EIP adaptation of CIP 1.12
Supply: Module electronics and sensors (US)
Connection method
M12 connector (T-coded)
Number of positions
4
Supply voltage
24 V DC
Nominal supply voltage range
18 V DC ... 31.2 V DC (including all tolerances, including ripple)
Typical current consumption
190 mA ±15 % (at 24 V DC)
Current consumption
max. 12 A
Supply: Actuators (UA) for additional devices
Connection method
M12 connector (T-coded)
Number of positions
4
Supply voltage
24 V DC
Nominal supply voltage range
18 V DC ... 31.2 V DC (including all tolerances, including ripple)
Typical current consumption
3 mA ±15 % (at 24 V DC)
Current consumption
max. 12 A
Digital inputs
Number of inputs
16 (EN 61131-2 types 1 and 3)
Connection method
M12 connector, double occupancy
Connection method
2, 3, 4-wire
Nominal input voltage
24 V DC
Nominal input current
typ. 3 mA
Sensor current per channel
typ. 0.75 mA (from US)
Total sensor current
max. 1.2 A (per device)
Input voltage range "0" signal
-30 V DC ... 5 V DC
Input voltage range "1" signal
11 V DC ... 30 V DC
Input filter time
< 1000 µs
Permissible conductor length to the sensor
30 m
Overload protection, short-circuit protection of sensor supply
Yes
8421_en_02
PHOENIX CONTACT
5
AXL E EIP DI16 M12 6M
Electrical isolation/isolation of the voltage areas
Test section
Test voltage
24 V supply (communications power and sensor supply, digital inputs)/
bus connection (Ethernet 1)
500 V AC, 50 Hz, 1 min
24 V supply (communications power and sensor supply, digital inputs)/
bus connection (Ethernet 2)
500 V AC, 50 Hz, 1 min
24 V supply (communications power and sensor supply, digital inputs)/FE 500 V AC, 50 Hz, 1 min
Bus connection (Ethernet 1)/FE
500 V AC, 50 Hz, 1 min
Bus connection (Ethernet 2)/FE
500 V AC, 50 Hz, 1 min
Bus connection (Ethernet 1)/bus connection (Ethernet 2)
500 V AC, 50 Hz, 1 min
24 V supply (actuator supply)/
24 V supply (communications power and sensor supply, digital inputs)
500 V AC, 50 Hz, 1 min
24 V supply (actuator supply)/bus connection (Ethernet 1)
500 V AC, 50 Hz, 1 min
24 V supply (actuator supply)/bus connection (Ethernet 2)
500 V AC, 50 Hz, 1 min
24 V supply (actuator supply)/FE
500 V AC, 50 Hz, 1 min
Mechanical tests
Vibration resistance in acc. with EN 60068-2-6/IEC 60068-2-6
5g
Shock in acc. with EN 60068-2-27/IEC 60068-2-27
30 g, 11 ms period, half-sine shock pulse
Continuous shock according to EN 60068-2-27/IEC 60068-2-27
10 g
Conformance with EMC Directive 2004/108/EC
Noise immunity test in accordance with EN 61000-6-2
Electrostatic discharge (ESD) EN 61000-4-2/IEC 61000-4-2
Criterion B; 6 kV contact discharge, 8 kV air discharge
Electromagnetic fields EN 61000-4-3/IEC 61000-4-3
Criterion A; Field intensity: 10 V/m
Fast transients (burst) EN 61000-4-4/IEC 61000-4-4
Criterion B, 2 kV
Transient surge voltage (surge) EN 61000-4-5/IEC 61000-4-5
Criterion B; DC supply lines: ±0.5 kV/±0.5 kV (symmetrical/asymmetrical)
Conducted interference EN 61000-4-6/IEC 61000-4-6
Criterion A; Test voltage 10 V
Noise emission test as per EN 61000-6-4
Radio interference properties EN 55022
Class A
Approvals
For the latest approvals, please visit phoenixcontact.net/products.
8421_en_02
PHOENIX CONTACT
6
AXL E EIP DI16 M12 6M
5
Internal circuit diagram
Key:
ETH1
ETH2
Transmitter with electrical isolation
X22
X21
Power supply unit with electrical isolation
US IN
US OUT
UA IN
µC
X31
X32
24 V
3.3 V
UA OUT
µC
Microcontroller
Digital input
16
2 2
X01
#
#
X02
LED
2 2
X03
#
#
X04
2 2
X05
X07
Figure 1
#
#
2 2
#
#
X06
X08
Internal wiring of connections
Key:
Green area:
Blue area:
Yellow area:
8421_en_02
Network
US
UA
PHOENIX CONTACT
7
AXL E EIP DI16 M12 6M
6
Pin assignment
6.1
EtherNet/IP™ and power supply connection
Port 1
6.2
EtherNet/IP™ pin assignment
1
2
2
3
4
3
1
4
Port 2
X21
Figure 3
Pin
Figure 2
Connections for EtherNet/IP™ and voltage
supply
Designation
Port 1 (X21)
Port 2 (X22)
US IN (X31)
UA IN (X31)
US OUT (X32)
UA OUT (X32)
Meaning
Ethernet port 1
Ethernet port 2
Power supply IN (logic and sensors)
Power Supply IN (actuators) for additional devices
Power supply OUT for additional devices
Power supply OUT for additional devices
X22
Ethernet pin assignment, D-coded
Ethernet port 1
(X21)
TX+
RX+
TXRX-
1
2
3
4
Ethernet port 2
(X22)
TX+
RX+
TXRX-
The shield is connected to FE in the device.
The thread is used for additional shielding.
6.3
Ground the device by means of the mounting
screws.
Pin assignment of the power supply US/UA
1
2
4
4
3
3
X31
Figure 4
8421_en_02
1
2
X32
Pin assignment of the power supply, T-coded
Pin
IN
OUT
1
2
3
4
+24 V DC (US)
GND (UA)
GND (US)
+24 V DC (UA)
+24 V DC (US)
GND (UA)
GND (US)
+24 V DC (UA)
Conductor
colors
Brown
White
Blue
Black
PHOENIX CONTACT
8
AXL E EIP DI16 M12 6M
6.4
Input connection
6.5
Pin assignment of the inputs
1
2
2
5
4
5
3
X01, X03, X05, X07
Figure 6
Figure 5
Input connections
Designation
DI1 ... DI16 (X01 ... X08)
8421_en_02
Pin
1
2
3
4
5
3
1
4
X02, X04, X06, X08
Pin assignment of the inputs, A-coded
Input socket
+24 V DC (US)
Input 2, 4, 6, ... 16
GND
Input 1, 3, 5, ... 15
FE
Meaning
Inputs 1 ... 16
PHOENIX CONTACT
9
AXL E EIP DI16 M12 6M
7
Connection example
8
Connection notes
Note: data corruption or loss
IN 6
+24 V
Implement the FE connection using mounting
screws, in order to ensure immunity to interference.
IN 5
IN 12
NOTE: device damage
IN 11
+24 V
To ensure IP65/IP67 protection, cover unused
sockets with protective caps.
NOTE: Damage to the electronics
Figure 7
Typical connection of sensors
Only supply the sensors with the voltage US
provided at the terminal points.
NOTE: Damage to the electronics
Observe the correct polarity of the supply voltages US and UA in order to prevent damage to
the device.
NOTE: Malfunction
When connecting the sensors, observe the
assignment of the connections to the
EtherNet/IP™ input data.
Secure the device to a level surface or to a
profile. Do not use this device to bridge gaps,
in order to prevent forces being transmitted
via the device.
Use standard M5 screws with toothed lock
washer and self-locking nuts. Observe the
maximum torque of the screws.
8421_en_02
PHOENIX CONTACT
10
AXL E EIP DI16 M12 6M
9
Configuration via rotary encoding switch
You can configure the address assignment and other functions using rotary encoding switches.
After modifying the switch position, restart the device, as the
modification to the switch position does not take effect during operation.
14
0
2
4
12
10
x10
8
6
E
D
C
B
A
S1
Figure 8
F 0
2
x1
4
9 8
6
S2
Rotary encoding switch
The code results from the sum of S1 x 10 plus S2 x 1. The
image shows code 77 (7 x 10 + 7).
S1
0
0 ... 5
5 ... 15
0
0
0
9.1
S2
Code
Function
0
00
Remote access (default)
1 ... 0 01 ... 50 Manual address assignment
0 ... 9 51 ... 159
DHCP name assignment
A
0A
Fixed address
E
0E
Resetting IP parameters
F
0F
Resetting to the default settings
Other
Reserved
Remote access
Switch position 00
At this switch position, it is possible to remotely configure the
device using corresponding tools (e.g., Startup+, webbased management (WBM)).
Behavior during initial startup, after resetting the IP
parameters or after resetting to default settings
A valid IP address is not assigned (0.0.0.0) and communication is therefore not possible.
The device transmits continuous BootP requests (2 s, 4 s,
8 s, 2 s ...), until a valid IP address has been received.
Valid IP parameters are then automatically saved as configuration data on the device.
Each additional startup
If BootP is not explicitly deactivated, the device transmits
continuous BootP requests (2 s, 4 s, 8 s, 2 s, etc.), until a
valid IP address has been received.
Valid IP parameters are then automatically saved as configuration data on the device.
9.2
Manual address assignment
Switch position 01 ... 50
Default: BootP deactivated, DHCP activated
The first three octets in the IP address are preset as
192.168.0.x.
The subnet mask is 255.255.255.0.
Specify the last byte with the switch position.
As such, you can select IP addresses between 192.168.0.1
and 192.168.0.50.
Prior to transferring the IP address, a test is performed to
check for any potential IP address conflicts. If a conflict is
detected, the device temporarily switches the IP address to
0.0.0.0 (no IP communication). In this case, the NET LED
flashes red. Eliminate the conflict and restart the device.
9.3
DHCP name assignment
Switch position 51 ... 159
This switch position is used to easily specify the DHCP host
name for the device.
The host name is provided to the DHCP server via DHCP
options. This is therefore able to send a DNS update to the
DNS server.
The DNS name consists of one set part, which is based on
the order designation, and a variable part, which is determined by the switch position.
The first part of the station name is AXL-E-EIP-.
The set number is added.
This results in the following station names: AXL-E-EIP-051
... AXL-E-EIP-159.
Behavior during initial startup, after resetting the IP
parameters or after resetting to default settings
A valid IP address is not assigned (0.0.0.0) and communication is therefore not possible.
The device transmits continuous DHCP discover messages
until a valid IP address has been received.
8421_en_02
PHOENIX CONTACT
11
AXL E EIP DI16 M12 6M
Each additional startup
The device transmits continuous DHCP requests.
There are two possible scenarios:
1. The DHCP server assigns a new IP address.
The device applies the new IP parameters.
2. The DHCP server does not respond.
The device transmits continuous DHCP Discover
messages until new IP parameters have been received.
9.4
9.6
Switch position 0F
All settings are reset to default settings, including IP parameters.
The device is ready for operation after powering up, as soon as the RDY LED lights up
green.
A connection to the device however cannot be
established in this switch position.
As soon as the RDY LED lights up green, a
new switch position can be selected on the rotary encoding switch and the device can be
restarted.
Fixed address
Switch position 0A
Behavior during initial startup, after resetting the IP
parameters or after resetting to default settings
A valid IP address is not assigned (0.0.0.0) and communication is therefore not possible.
Assign an address initially with another switch position.
Resetting to the default settings
9.7
Reserved/invalid switch position
The device starts with the previous settings, e.g., with the
settings that were valid before the device was restarted.
Each additional startup
After a voltage reset, the device maintains the IP address
which was assigned last.
An invalid switch position is indicated by the RDY LED (red
on).
With this switch position, modifying the IP address via tools or web-based management is
not possible.
9.5
Resetting IP parameters
Switch position 0E
The IP parameters stored on the device are reset.
All other settings made on the device are retained.
– BootP is activated for switch position 00.
– IP address, subnet mask: 0.0.0.0
As long as the switch position 0E remains selected, no connection to the device can be established.
IP communication is deactivated (LED NET static yellow).
8421_en_02
PHOENIX CONTACT
12
AXL E EIP DI16 M12 6M
10
Local status and diagnostic indicators
10.1
Indicators for Ethernet ports and power supply
Figure 9
Indicators for Ethernet ports and power supply
Designation
LNK 1/2
Color Meaning
Green Link
ACT 1/2
Yellow Activity
RDY
Green/ Ready
yellow/
red
NET
8421_en_02
State
Green
ON
OFF
Yellow
ON
OFF
Green
ON
Yellow
flashing
Flashing
green/
yellow
Red ON
OFF
Green/ Network status Green
red
ON
Green
flashing
Red ON
Red
flashing
Flashing
green/
red
OFF
Description
Connection present at port 1/2.
Connection not present at port 1/2.
Data transmission present at port 1/2.
Data transmission not present at port 1/2.
Device is ready for operation.
Firmware update is being performed.
Over- or undervoltage at US
Temperature of the device is in the critical area.
Failure of the actuator supply UA
And red US LED: sensor supply overload
Rotary encoding switches are set to an invalid/reserved position.
Device is not ready for operation.
At least one CIP connection is in place and the exclusive owner connection has no timeout.
An IP address is configured, no CIP connection is yet in place, and the
exclusive owner connection has no timeout.
Duplicate IP. ACD has determined an IP address conflict.
Connection timeout. A timeout of an exclusive owner connection has
occurred.
Self test
Device is not ready for operation.
PHOENIX CONTACT
13
AXL E EIP DI16 M12 6M
Designation
MOD
US
Green/ USensorik
red
UA
10.2
Color Meaning
Green/ Module status
red
Green UAktorik
State
Green
ON
Green
flashing
Red ON
Red
flashing
Flashing
green/
red
OFF
Green
ON
OFF
Red ON
ON
OFF
Description
Normal operation
The device is not configured.
A recoverable error has occurred.
A unrecoverable error has occurred.
Self test
Device is not ready for operation.
Communications power/sensor voltage present
Communications power/sensor voltage not present or too low.
Sensor voltage overload
Actuator voltage present.
Actuator voltage not present.
Input indicators
Figure 10
LEDs of the inputs
Designation
00 ... 07,
10 ... 17
Color
Yellow
Meaning
Status of the inputs
State
ON
OFF
Description
Input is set.
Input is not set.
The numbering of the LEDs is as follows: the first number specifies the byte, the second number specifies the
bit.
8421_en_02
PHOENIX CONTACT
14
AXL E EIP DI16 M12 6M
11
EtherNet/IP™ object classes, messages, and services
The device supports the Common Industrial Protocol (CIP) by using digital input points (DIPs) and digital output points
(DOPs) 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.
Connection type
Explicit messaging
Implicit messaging
11.1
Description
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 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).
CIP class services
The device supports the following class services and instance services:
Service code
dec
hex
01
01
02
02
05
05
09
09
14
0E
16
10
11.2
Service name
Get_Attribute_All
Set_Attribute_All
Reset
Delete
Get_Attribute_Single
Set_Attribute_Single
CIP object classes
The device supports the following CIP object classes:
Class code
dec
hex
01
01
04
04
06
06
08
08
71
47
72
48
245
F5
246
F6
8421_en_02
Object type
Identity object
Assembly object
Connection manager object
Digital input point object
Device level ring object
Quality of Service object
TCP/IP interface object
Ethernet link object
PHOENIX CONTACT
15
AXL E EIP DI16 M12 6M
11.3
Identity object (class code 01hex)
The Identity object is required by all devices and provides the device ID and general information about the device.
Class attributes
Attribute
1
2
6
7
Name
Version
Max instance
Max class attribute
Max instance attribute
Access
Get
Get
Get
Get
Data type
UINT
UINT
UINT
UINT
Value
1
1
7
10
Instance attributes
Attribute
1
2
3
4
5
Name
Vendor ID
Device type
Product code
Revision
Major revision
Minor revision
Status
Access
Get
Get
Get
Get
Get
Data type
UINT
UINT
UINT
STRUC of:
USINT
USINT
WORD
6
7
8
Serial number
Product name
State
Get
Get
Get
UDINT
STRING
USINT
9
Configuration consistency value Get
USINT
Value
562
General purpose discrete I/O
8174
1
1
1
Bit 0
Owned
Bit 1
Reserved
Bit 2
Configured
Bit 3
Reserved
Bit 4 ... Bit 7
Extended device status
Bit 8
Minor recoverable fault
Bit 9
Minor unrecoverable fault
Bit 10
Major recoverable fault
Bit 11
Major unrecoverable fault
Bit 12 ... Bit 15 Extended device status 2
Is fixed in production process
AXL E EIP DI16 M12 6M
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
CRC checksum
Common services
Service code
dec
hex
01
01
05
05
14
0E
16
10
8421_en_02
Class
Instance
Service name
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Get_Attribute_All
Reset
Get_Attribute_Single
Set_Attribute_Single
PHOENIX CONTACT
16
AXL E EIP DI16 M12 6M
11.4
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
Attribute
1
2
Name
Version
Max instance
Access
Get
Get
Data type Value
UINT
2
UINT
102
Description
Current Process data of the correspondent
Assembly instance
Number of bytes in attribute 3
Instance attributes
Attribute
3
Name
Data
Access
Get, Set
4
Size
Get
Data type
ARRAY of
Byte
UINT
Class
Instance
Service name
Yes
No
Yes
Yes
Get_Attribute_Single
Set_Attribute_Single
Common services
Service code
dec
hex
14
0E
16
10
11.5
Connection manager object (class code 06hex)
Class attributes
Attribute
1
2
8421_en_02
Name
Version
Max instance
Access
Get
Get
Data type Value
UINT
1
UINT
1
PHOENIX CONTACT
17
AXL E EIP DI16 M12 6M
11.6
Discrete Input Point object (class code 08hex)
The Digital input point (DIP) object mirrors the digital inputs. This object can be used in simple toggle switches as well as in
complex I/O control modules. Each device has a separate instance for each digital input.
Class attributes
Attribute
1
Name
Version
Access
Get
Data type Value
UINT
2
Access
Get
Get
Data type Value
BOOL
0 = off; 1 = on
BOOL
0 = OK; 1 = Fault
Class
Instance
Service name
Yes
No
Yes
Yes
Get_Attribute_Single
Set_Attribute_Single
Instance attributes
Attribute
3
4
Name
Value
Status
Common services
Service code
dec
hex
14
0E
16
10
8421_en_02
PHOENIX CONTACT
18
AXL E EIP DI16 M12 6M
11.7
Device level ring object (class code 47hex)
Class attributes
Attribute
1
Name
Version
Access
Get
Data type Value
UINT
2
Instance attributes
Attribute
1
Name
Network topology
Access Datentyp
Get
USINT
2
Network status
Get
USINT
10
Active supervisor
address
Get
12
Capability flags
Get
STRUCT of:
UDINT
ARRAY of 6
USINTs
DWORD
Wert/ Beschreibung
0 = Linear
1 = Ring
0 = Normal
1 = Ring fault
2 = Unexpected loop detected
3 = Partial network fault
4 = Rapid fault/Restore cycle
IP and/or MAC adress of the active ring supervisor
Supervisor IP address
Supervisor MAC adress
Bit 0
Bit 1
Bit 2 ... Bit 4
Bit 5
Bit 6 ... Bit 31
Announced-based ring node
Beacon-based ring note
Reserved
Supervisor capable
Reserved
Common services
Service code
dec
hex
1
01
14
0E
8421_en_02
Class
Instance
Service name
Yes
Yes
Yes
Yes
Get_Attribute_Single
Set_Attribute_Single
PHOENIX CONTACT
19
AXL E EIP DI16 M12 6M
11.8
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
Attribute
1
2
Name
Version
Max instance
Access
Get
Get
Data type Value
UINT
1
UINT
1
Instance attributes
Attribute
1
4
Name
Access
802.1Q tag enable Get, Set
DSCP urgent
Get, Set
5
DSCP scheduled
Get, Set
6
DSCP high
Get, Set
7
DSCP low
Get, Set
8
DSCP explicit
Get, Set
Data type Value/Description
UINT
0 = off (default); 1 = on
USINT
DSCP value for CIP transport class 0/1 Urgent priority message
(default 55)
USINT
DSCP value for CIP transport class 0/1 Scheduled priority message (default 47)
USINT
DSCP value for CIP transport class 0/1 High priority message
(default 43)
USINT
DSCP value for CIP transport class 0/1 Low priority message (
default 31)
USINT
DSCP value for CIP explicit messages (transport class 2/3 and
UCMM) and all other EtherNet/IP encapsulation messages
(default 27)
Common services
Service code
dec
hex
14
0E
16
10
8421_en_02
Class
Instance
Service name
Yes
No
Yes
Yes
Get_Attribute_Single
Set_Attribute_Single
PHOENIX CONTACT
20
AXL E EIP DI16 M12 6M
11.9
TCP/IP object (class code F5hex)
Class attributes
Attribute
1
2
Name
Version
Max instance
Access
Get
Get
Data type Value
UINT
3
UINT
1
Instance attributes
Attribute
1
Name
Status
2
Configuration capability
3
Configuration control
4
Physical link object
Path size
Path
8421_en_02
Acess
Get
Data type
DWORD
Description
Bit 0 ... Bit 3
Bit 4
Bit 5
Bit 6
Bit 7
Bit 8 ... Bit 31
Bit 0
Bit 1
Bit 2
Bit 3
Bit 4
Bit 5
Bit 6
Bit 7
Bit 8 ... Bit 31
Bit 0 ... Bit 3
Interface configuration status
Mcast pending (always 0)
Interface configuration pending
AcdStatus
AcdFault
Reserved
Get
DWORD
BOOTP client
Not supported
DHCP client
Not supported
TCP/IP config setable via ETH/IP
Not supported
Not supported
AcdCapable
Reserved
Get, Set DWORD
0 = The device use static IP configuration
1 = The device use BOOTP
2 = The device use DHCP
Bit 4
Not supported
Bit 5 ... Bit 31 Reserved
Get
STRUCT of:
Path to Physical link object
UINT
4
Padded EPATH 0x20, 0xF6, 0x25, 0x01
PHOENIX CONTACT
21
AXL E EIP DI16 M12 6M
Attribute
5
6
10
11
Name
Interface configuration
IP address
Network mask
Gateway address
Name server
Name server 2
Domain name
Host name
SelectAcd
Last conflict detected
Acess
Data type
Get, Set STRUCT of:
UDINT
UDINT
UDINT
UDINT
UDINT
STRING
Get, Set STRING
Get, Set BOOL
Set
STRUCT of:
AcdActivity
USINT
Remote MAC
12
ARRAY of
6 USINTs
ArpPdu
Array of
28 USINTs
Ethernet/IP quick connect Get, Set BOOL
Description
TCP/IP network interface configuration
The device’s IP address
The device’s network mask
Default gateway address
Primary name server (always 0.0.0.0)
Secondary name server (always 0.0.0.0)
Default domain name (always empty)
The device’s host name
0 = disable; 1 = enable (default)
Structure containing information related to the last conflict detected
State of ACD activity when last conflict detected
0 = Noconflictdetected (default)
1 = ProbeIpv4Address
2 = OngoingDetection
3 = SemiActiveProbe
MAC address of remote node from the ARP PDU in
which a conflict was detected
Copy of the raw ARP PDU in which a conflict was detected.
0 = disable (default); 1 = enable
Common services
Service code
dec
hex
1
01
14
0E
16
10
8421_en_02
Class
Instance
Service name
Yes
Yes
No
Yes
Yes
Yes
Get_Attribute_All
Get_Attribute_Single
Set_Attribute_Single
PHOENIX CONTACT
22
AXL E EIP DI16 M12 6M
11.10 Ethernet link object (class code F6hex)
Class attributes
Attribute
1
2
3
Name
Version
Max instance
Number of instances
Access
Get
Get
Get
Data type
UINT
UINT
UINT
Description
3
10
2
Instance attributes
Attribute
Name
Access
Data type
Description
1
Interface speed
Get
UDINT
Interface speed currently in use. Speed in bps (e.g. 10, 100)
2
Interface flags
Get
DWORD
Bit 0
Link status
Bit 1
Half/Full duplex status
0 = Half duplex; 1 = Full duplex
Bit 2 ... Bit 4
Auto negotiation status
0 = Auto negotiation in progress
1 = Auto negotiation and speed detection failed
2 = Auto negotiation failed but detected speed
3 = Successfully negotiated
4 = Auto negotiation not attempted
Bit 5
Not supported
Bit 6
Not supported
3
Physical address Get
ARRAY of
6 USINTs
MAC layer adress
6
Interface control
STRUC of:
Configuration for physical interface
WORD
Interface control bits
Set
Control bits
Bit 0
Auto-negotiate (set)
0 = Auto negotiation disabled
1 = Auto negotiation enabled
Bit 1
Forced duplex mode (set)
0 = Half duplex ;1 = Full duplex
Set only if auto negotiation is disabled
Bit 2 ... Bit 15 Reserved, shall be set to 0
Forced interface
speed
10
Interface lable
Get
UINT
The Forced interface speed bits indicate the speed at which the interface shall operate.
10 = 10 Mbps
100 = 100 Mbps
Set only if auto negotiation is disabled
STRING
Interface name
Common services
Service code
dec
1
14
8421_en_02
hex
01
0E
Class
Instance
Service name
Yes
Yes
No
Yes
Get_Attribute_All
Get_Attribute_Single
PHOENIX CONTACT
23
AXL E EIP DI16 M12 6M
12
EtherNet/IP™Assembly instances
Input data length in bytes
Assembly instance
Output data length in bytes
Assembly instance
Configuration data length in bytes
Assembly instance
12.1
Exclusive owner
-
Input only
6
101
0
193
-
Listen only
6
101
0
192
-
Assembly instance 101 (IN process data)
Byte
0 ... 3
4
5
Function
Status byte
Input data
Input data
Description
Status information
Input data channel 1 ... 8
Input data channel 9 ... 16
The first four bytes of the input data have the same format for all Axioline E versions.
Bit 31 ... bit 6
Reserved
Reserved
Bit 5
Bit 4
Supply of the module electronics and sensors (US)
Undervoltage
Overload
Bit 3
Bit 2
Bit 1
Reserved
Reserved
Bit 0
Input process data
Byte
Bit
IN
Connection
Pin
DI
7
6
07
06
X04
2
4
8
7
Byte 0
5
4
3
2
05
04
03
02
X03
X02
2
4
2
4
6
5
4
3
1
0
01
00
X01
2
4
2
1
7
6
17
16
X08
2
4
16
15
Byte 1
5
4
3
2
15
14
13
12
X07
X06
2
4
2
4
14
13
12
11
1
0
11
10
X05
2
4
10
9
Key:
Bit:
IN:
DI:
8421_en_02
Process data assignment
LED marking
Input of the device
PHOENIX CONTACT
24
AXL E EIP DI16 M12 6M
13
Startup
13.1
Delivery state/default settings
By default upon delivery, the following functions and features are available:
IP settings
IP parameters:
Subnet mask:
Default Gateway:
BootP:
0.0.0.0
0.0.0.0
0.0.0.0
activated
13.2
Restoring the default settings
There are two options for resetting the default settings:
– Via web-based management, go to the Administration
web page > default settings and follow the instructions.
– Via the rotary coding switch, switch position 0F
13.3
Starting the firmware
Once you have connected the power, the firmware is
started.
After completion of the firmware boot process, the NET LED
either lights up or flashes green.
Firmware update
Firmware update on next restart:
deactivated
TFTP server IP address:
192.168.210.211
Firmware file name:
FIRMWARE.NXF
System identification
Device name:
Description:
Device location:
Contact:
No name assigned
No description assigned
No location assigned
No contact assigned
Web-based Management (WBM)
User name:
Password:
8421_en_02
admin
private
PHOENIX CONTACT
25
AXL E EIP DI16 M12 6M
14
SNMP - Simple Network Management Protocol
The device supports SNMP v1.
Management Information Base - MIB
The corresponding latest MIBs are available
on the Internet at phoenixcontact.net/products.
Calling web-based management
The device web server can be addressed using the IP address if configured accordingly. The homepage (web page)
of the device is accessed by entering the URL “http://ip-address”.
Example: http://172.16.113.38
The default user name is “admin”, the default password is
“private”.
If you cannot access the WBM pages, check
the connection settings in your browser and
deactivate the proxy, if set.
For the object descriptions, please refer to the ASN1 descriptions for this product.
The password for read access is “public” and cannot be
changed.
By default upon delivery, the password for write/read access
is “private” and can be modified at any time.
15
DLR - Device Level Ring
The device supports DLR.
DLR is a protocol that works on Layer 2 for multi-port-EtherNet/IP™ devices.
The use of DLR is transparent for the protocols which work
on higher levels such as TCP/IP.
DLR increases the network availability, thanks to a redundant ring topology with a switch-over time of less than 3 ms
for error detection and reconfiguration.
The DLR protocol supports the 1-ring topology; multiple
rings or overlapping rings are not possible.
16
WBM - Web-based management
The device has a web server, which generates the required
pages for web-based management and, depending on the
requirements of the user, sends them to a standard web
browser. Web-based management can be used to access
static information (e.g., technical data, MAC address) or dynamic information (e.g., IP address, status information).
17
Firmware update
In order to update the firmware of the device, the device
must be provided with a firmware container via a TFTP
server or it must be loaded onto the device via FTP. Any FTP
client or TFTP server can be used for this. The update must
always be initiated by the web-based management. When
carrying out the firmware update, the RDY LED flashes yellow.
18
Quick Connect
The device supports Quick Connect Class A.
After switching on the mains voltage, it is ready to operate in
under 350 ms in order to process a connection request.
A cyclic process data connection can be established in
under 500 ms.
19
Connection types
The device supports the connection types Exclusive Owner,
Input Only, and Listen Only.
– Exclusive Owner and Input Only can be configured by
the scanner as a Multicast or Point to Point connection
in the Target to Originator direction.
– Listen Only connections can only be used as Multicast.
In the case of the AXL E Ethernet/IP™ device, the data is
transmitted to the scanner with a connection.
20
Device description (EDS)
In the case of EtherNet/IP™, a device description file (EDS)
is required for various configuration tools.
For each Axioline E EtherNet/IP™ device, an individual specific EDS file is provided.
8421_en_02
PHOENIX CONTACT GmbH & Co. KG • 32823 Blomberg • Germany
phoenixcontact.com
26
