AXL F BK EIP EF

Axioline F bus coupler for EtherNet/IP™,

extended function

Data sheet
107469_en_03 © PHOENIX CONTACT 2020-04-27

1 Description
The bus coupler is intended for use within an EtherNet/IP™
network. It is the link to the Axioline F I/O system.
Up to 63 Axioline F devices can be connected to the bus
coupler.
A corresponding EDS file is available for integrating the
Axioline F station into the programming system.
It can be downloaded at: phoenixcontact.net/product/
2702782
Features
– 2 Ethernet ports (with integrated switch)
– Transmission speed of 10 Mbps and 100 Mbps
– Rotary coding switches for setting the IP address
assignment and other functions
– Supported protocols: EtherNet/IP, DLR, SNMP,
HTTP, TFTP, FTP, BootP, DHCP, DCP
– Firmware can be updated
– Typical cycle time of the Axioline F local bus is around
10 μs

This data sheet is only valid in association with the UM EN AXL F SYS INST user manual.

Make sure you always use the latest documentation.

It can be downloaded at: phoenixcontact.net/product/2702782
 AXL F BK EIP EF

2 Table of contents
1 Description .............................................................................................................................. 1
2 Table of contents ..................................................................................................................... 2
3 Ordering data .......................................................................................................................... 3
4 Technical data ......................................................................................................................... 5
5 Internal circuit diagram ............................................................................................................ 8
6 Security in the network ............................................................................................................ 8
7 Connecting EtherNet/IP™ and the supply ............................................................................... 9
8 Connection example................................................................................................................ 9
9 Configuration via rotary encoding switch ............................................................................... 10
10 Local diagnostic and status indicators ................................................................................... 13
11 EtherNet/IP™: Object classes, messages, and services ....................................................... 15
12 Reset button .......................................................................................................................... 17
13 Service interface.................................................................................................................... 18
14 Startup behavior of the bus coupler ....................................................................................... 19
15 Mapping process data to the Assembly object ...................................................................... 20
16 SNMP: Simple Network Management Protocol ..................................................................... 21
17 DLR - Device Level Ring........................................................................................................ 21
18 WBM: Web-based management ........................................................................................... 21
19 Firmware update.................................................................................................................... 21
20 Connection types................................................................................................................... 21
21 Device description (EDS) ...................................................................................................... 21

107469_en_03 PHOENIX CONTACT 2 / 21

 AXL F BK EIP EF

3 Ordering data

Description Type Order No. Pcs./Pkt.

Axioline F, Bus coupler, EtherNet/IP™, RJ45 jack, AXL F BK EIP EF 2702782 1
extended function, transmission speed in the local
bus: 100 Mbps, degree of protection: IP20, including bus
base module and Axioline F connector

Accessories Type Order No. Pcs./Pkt.

Axioline  F bus base module for housing type BK AXL BS BK 2701422 5
(Replacement item)
RJ45 connector, shielded, with bend protection sleeve, FL PLUG RJ45 GR/2 2744856 1
2 pieces, gray for straight cables, for assembly on site. For
connections that are not crossed, it is recommended that
you use the connector set with gray bend protection
sleeve. (Connector/Adapter)
RJ45 connector, shielded, with bend protection sleeve, FL PLUG RJ45 GN/2 2744571 1
2 pieces, green for crossed cables, for assembly on site.
For connections that are crossed, it is recommended that
the connector set with green bend protection sleeves is
used. (Connector/Adapter)
CAT5-SF/UTP cable (J-02YS(ST)C HP 2 x 2 x 24 AWG), FL CAT5 HEAVY 2744814 1
heavy-duty installation cable, 2 x 2 x 0.22 mm², solid
conductor, shielded, outer sheath: 7.8 mm diameter, inner
sheath: 5.75 mm ± 0.15 mm diameter (Cable/conductor)
CAT5-SF/UTP cable (J-LI02YS(ST)C H 2 x 2 x 26 AWG), FL CAT5 FLEX 2744830 1
light-duty, flexible installation cable 2 x 2 x 0.14 mm²,
stranded, shielded, outer sheath: 5.75 mm ± 0.15 mm
diameter (Cable/conductor)
Crimping pliers, for assembling the RJ45 plugs FL PLUG FL CRIMPTOOL 2744869 1
RJ45..., for assembly on site (Tools)
Zack marker strip for Axioline F (device labeling), in 2 x ZB 20,3 AXL UNPRINTED 0829579 25
20.3 mm pitch, unprinted, 25-section, for individual
labeling with B-STIFT 0.8, X-PEN, or CMS-P1-PLOTTER
(Marking)

107469_en_03 PHOENIX CONTACT 3 / 21

 AXL F BK EIP EF

Accessories Type Order No. Pcs./Pkt.

Zack Marker strip, flat, Strip, white, unlabeled, can be ZBF 10/5,8 AXL UNPRINTED 0829580 50
labeled with: PLOTMARK, CMS-P1-PLOTTER, mounting
type: snap into flat marker groove, for terminal block width:
10.15 mm, lettering field size: 4 of 10.15 x 5 mm and 1 of
5.8 x 5 mm, Number of individual labels: 50 (Marking)
Insert label, Roll, white, unlabeled, can be labeled with: EMT (35X18,7)R 0801831 1
THERMOMARK ROLLMASTER 300/600,
THERMOMARK X1.2, THERMOMARK ROLL X1,
THERMOMARK ROLL 2.0, THERMOMARK ROLL,
mounting type: snapped into marker carrier, lettering field
size: 35 x 18.7 mm, Number of individual labels: 500
(Marking)
Connecting cable, for connecting the controller to a PC for CAB-USB A/MICRO USB B/ 2701626 1
PC Worx and LOGIC+, USB A to micro USB B, 2 m in 2,0M
length. (Cable/conductor)

Documentation Type Order No. Pcs./Pkt.

User manual, English, UM EN AXL F BK EIP (EF) - - -
Axioline F bus coupler for EtherNet/IP™: object classes, OBJECTS
messages, and services
User manual, English, Axioline F: System and installation UM EN AXL F SYS INST - -
User manual, English, Axioline F: Diagnostic registers, UM EN AXL F SYS DIAG - -
and error messages
Quick start guide, English, Handling an Axioline F station UM QS EN STARTUP+ - -
under Startup+
Application note, English, AH EN TFTP FIRMWARE - -
Updating the firmware of an Axioline F bus coupler UPDATE AXL F BK
Application note, English, Measures to protect network- AH EN INDUSTRIAL SECURI - -
capable devices with Ethernet connection against TY
unauthorized access

107469_en_03 PHOENIX CONTACT 4 / 21

 AXL F BK EIP EF

4 Technical data

Dimensions (nominal sizes in mm)

45 74

122,4
126,1

Width 45 mm
Height 126.1 mm
Depth 74 mm
Note on dimensions The depth is valid when a TH 35-7,5 DIN rail is used (according
to EN 60715).

General data
Color traffic grey A RAL 7042
Weight 177 g (with connector and bus base module)
Ambient temperature (operation) -25 °C ... 60 °C (Mounting position: wall mounting on horizontal
DIN rail)
-25 °C ... 55 °C (Mounting position: any)
Ambient temperature (storage/transport) -40 °C ... 85 °C
Permissible humidity (operation) 5 % ... 95 % (non-condensing)
Permissible humidity (storage/transport) 5 % ... 95 % (non-condensing)
Air pressure (operation) 70 kPa ... 106 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 IP20
Protection class III (IEC 61140, EN 61140, VDE 0140-1)
Mounting position any (observe temperature derating)

Connection data: Axioline F connector

Connection method Push-in connection
Conductor cross section solid / stranded 0.2 mm² ... 1.5 mm² / 0.2 mm² ... 1.5 mm²
Conductor cross section [AWG] 24 ... 16
Stripping length 8 mm
Please observe the information provided on conductor cross sections in the “Axioline F: system and
installation” user manual.

107469_en_03 PHOENIX CONTACT 5 / 21

 AXL F BK EIP EF

Interface: EtherNet/IP™
Number 2
Connection method RJ45 jack
Transmission speed 10/100 Mbps (Half or full duplex mode (automatic detection,
can be adjusted manually))
Transmission physics Ethernet in RJ45 twisted pair
Transmission length max. 100 m

Interface: Axioline F local bus

Number 1
Connection method Bus base module
Transmission speed 100 Mbps

Interface: Service
Number 1
Connection method USB type C (as of HW 01)
Micro USB type B (HW 00)

System limits
Number of local bus devices that can be connected max. 63
NOTE: Electronics may be damaged when overloaded
Observe the logic current consumption of each device when configuring an Axioline F station. It is specified in
every module-specific data sheet. The current consumption can differ depending on the individual module.
The permissible number of devices that can be connected therefore depends on the specific station structure.

Protocols supported
Protocols supported EtherNet/IP™, DLR, SNMP, HTTP, TFTP, FTP, BootP, DHCP,
DCP

Communications power UL feed-in (the supply of the Axioline F local bus UBus is generated from UL)
Supply voltage 24 V DC
Supply voltage range 19.2 V DC ... 30 V DC (including all tolerances, including ripple)
Current consumption typ. 105 mA (without I/O modules, UL = 24 V, HW 00)
typ. 85 mA (without I/O modules, UL = 24 V, as of HW 01)
max. 583 mA (2 A at UBus, UL = 24 V, HW 00)
max. 670 mA (2.5 A at UBus, UL = 24 V, HW 01 or later)
Power consumption typ. 2.5 W (without I/O modules, UL = 24 V, HW 00)
typ. 2 W (without I/O modules, UL = 24 V, as of HW 01)
max. 14 W (2 A at UBus, UL = 24 V, HW 00)
max. 16 W (2.5 A at UBus, UL = 24 V, HW 01 or later)
Surge protection of the supply voltage electronic
Polarity reversal protection of the supply voltage electronic
NOTE: Electronics may be damaged when overloaded
Provide external fuses for the 24 V UL area. If you are using an external fuse, the power supply unit must be
able to supply four times the nominal current of the fuse. This ensures that it trips in the event of an error.

107469_en_03 PHOENIX CONTACT 6 / 21

 AXL F BK EIP EF

Axioline F local bus supply (UBus)

Supply voltage 5 V DC (via bus base module)
Power supply unit max. 2 A (HW 00)
max. 2.5 A (as of HW 01)

Mechanical tests
Vibration resistance in acc. with EN 60068-2-6/ 5g
IEC 60068-2-6
Shock in acc. with EN 60068-2-27/IEC 60068-2-27 30g
Continuous shock according to EN 60068-2-27/ 10g
IEC 60068-2-27

Conformance with EMC Directive 2014/30/EU

Noise immunity test in accordance with EN 61000-6-2
Electrostatic discharge (ESD) EN 61000-4-2/
IEC 61000-4-2
Electromagnetic fields EN 61000-4-3/IEC 61000-4-3
Fast transients (burst) EN 61000-4-4/IEC 61000-4-4
Transient overvoltage (surge) EN 61000-4-5/
IEC 61000-4-5
Conducted interference EN 61000-4-6/IEC 61000-4-6
Noise emission test according to EN 61000-6-3
Criterion B, 6 kV contact discharge, 8 kV air discharge
Criterion A, Field intensity: 10 V/m
Criterion B, 2 kV
Criterion B, DC supply lines: ±0.5 kV/±0.5 kV (symmetrical/
asymmetrical), fieldbus cable shield: ±1 kV
Criterion A, Test voltage 10 V
Class B

Approvals
For the latest approvals, please visit phoenixcontact.net/products.

107469_en_03 PHOENIX CONTACT 7 / 21

 AXL F BK EIP EF

5 Internal circuit diagram 6 Security in the network

Service NOTE: Risk of unauthorized network

TM
EtherNet/IP access
Reset
Connecting devices to a network via Ethernet
NET RDY entails the danger of unauthorized access to
the network.
RJ45 MOD
To prevent unauthorized network access,
CO please read the following notes.
RJ45
PP D
If possible, deactivate unused communication channels.
E
Assign passwords such that third-parties cannot access the
C
bus coupler and make changes without authorization.
Due to its communication interfaces, the bus coupler should
Local bus not be used in safety-critical applications without additional
security appliances.
UBus
Therefore, please take additional protective measures in
UL accordance with the IT security requirements and the
3.3 V standards applicable to your application (e.g. virtual
UBus networks (VPN) for remote maintenance access, firewalls,
24 V
etc.) for protection against unauthorized network access.
On first request, you shall release Phoenix Contact and the
companies associated with
UL Phoenix Contact GmbH & Co. KG, Flachsmarktstrasse 8,
24 V
32825 Blomberg in accordance with §§ 15 ff. AktG (German
Figure 1 Internal wiring of the terminal points Stock Corporation Act), hereinafter collectively referred to
as "Phoenix Contact",
Key: from all third-party claims made due to improper use.
For the protection of networks for remote maintenance via
Service Service interface VPN, Phoenix Contact offers the mGuard product series as
Reset Reset button security appliances; these are described in the latest
Local bus Axioline F local bus Phoenix Contact catalog (phoenixcontact.net/products).
(hereinafter referred to as local bus) Additional measures for protection against unauthorized
RJ45 interface network access can be found in the
RJ45
AH EN INDUSTRIAL SECURITY application note. The
application note can be downloaded at phoenixcontact.net/
Power supply unit with electrical isolation products.

Microcontroller
µC

XXX Power supply unit

XXX

LED

Electrically isolated areas

107469_en_03 PHOENIX CONTACT 8 / 21

 AXL F BK EIP EF

7 Connecting EtherNet/IP™ and the 7.2 Connecting the supply voltage - terminal point
assignment
supply
7.1 Connecting EtherNet/IP™
a1 b1
a1 b1

Connecting EtherNet/IP™ to the bus coupler via an 8-pos.

a2 b2
a2 b2

RJ45 connector.
The EtherNet/IP™ connections are set to autocrossing
(Autocrossover).
Figure 2 Terminal point assignment
Auto crossover is only supported in auto
negotiation mode.
Without auto negotiation, you can activate Terminal Color Assignment
crossover manually in the web-based point
management, if necessary, using the “Manual Supply voltage input
crossover” checkbox. a1, a2 Red 24 V DC Communications power
(UL) feed-in (bridged internally)
Shielding b1, b2 Blue GND Reference potential of the
The shielding ground of the connected supply voltage (bridged in-
twisted pair cables is electrically connected ternally)
with the socket. When connecting network
segments, avoid ground loops, potential
transfers, and voltage equalization currents
via the braided shield.
8 Connection example

Observe bending radii

The housing dimensions specified under
EtherNet/IP
TM

"Dimensions" refer to the bus coupler with I/O

connectors without Ethernet connection.
When installing the bus coupler in a control
NET RDY
MOD
box, observe the bending radii of the Ethernet CO
PP D
E

cables and the connectors used (e.g.,

0 2

12 14
FL CAT5 FLEX: 30 mm for fixed installation S1

4 6
8 10
X10

UL EF
0 2

and FL CAT5 HEAVY: 30 mm without outer S2

CD

24 V DC +
4 6
AB

-
89
X1

sheath and 45 mm with outer sheath). If (UL) TM

required, use angled RJ45 connectors to

maintain these bending radii. Figure 3 Connection of the cables

107469_en_03 PHOENIX CONTACT 9 / 21

 AXL F BK EIP EF

9 Configuration via rotary encoding 9.1 Remote access

switch Switch position 00
You can configure the address assignment and other At this switch position, it is possible to remotely configure the
functions using rotary encoding switches. device using corresponding tools (e.g.,  Startup+, web-
Every time you change the switch position, restart the bus based management (WBM)).
coupler. A change of the switch position during operation
has no effect. Behavior during initial startup, after resetting the IP
parameters or after resetting to default settings
0
14 2
Default: BootP activated, DHCP deactivated
S1 12 4
A valid IP address is not assigned (0.0.0.0) and
10 6
8 communication is therefore not possible.
x10
The device transmits continuous BootP requests (2 s, 4 s,
F 0
E 2 8 s, 2 s ...), until a valid IP address has been received.
D
S2 C
B
4
Valid IP parameters are then automatically saved as
A 6
9 8 configuration data on the device.
x1
Each additional startup
Figure 4 Rotary encoding switch
BootP activated
The code results from the sum of S1 x 10 plus S2 x 1. The Three BootP requests are transmitted even in the case of a
image shows code 77 (7 x 10 + 7). valid configuration. If the device receives a BootP reply, the
new IP parameters are applied.
S1 S2 Code Function
DHCP activated
0 0 00 Remote access (default) For behavior, see switch position 51  159. The station
0 ... 5 0 ... 9 01 ... 50 Manual address assignment name can be selected in WBM. The default station name is
5 ... 15 0 ... 9 51 ... 159 DHCP name assignment the MAC address with “-” used as the separator.
0 A 0A Static address Static (BootP and DHCP deactivated)
0 E 0E Resetting IP parameters The device starts with the last valid assigned IP
1 A 1A Activate Plug and Play mode configuration.
1 B 1B Deactivate Plug and Play
9.2 Manual address assignment
mode
12 C 12C Resetting to the default set- Switch position 01 ... 50
tings
BootP deactivated, DHCP deactivated
Other Reserved
The first three octets in the IP address are preset as
192.168.1.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.1.1
and 192.168.1.50.

107469_en_03 PHOENIX CONTACT 10 / 21

 AXL F BK EIP EF

9.3 DHCP name assignment 9.4 Static address

Switch position 51 ... 159 Switch position 0A

This switch position is used to easily specify the DHCP host
Behavior during initial startup, after resetting the IP
name for the device.
parameters or after resetting to default settings
The host name is provided to the DHCP server via DHCP
options. This is therefore able to send a DNS update to the A valid IP address is not assigned (0.0.0.0) and
DNS server. communication is therefore not possible.

The DNS name consists of a set part and a variable part. Assign an address initially with another switch position.
The set part is based on the order designation. You specify
Each additional startup
the variable part via the switch position.
The first part of the station name is AXL-F-BK-EIP-. After a voltage reset, the device maintains the IP address
which was assigned last.
The set number is added.
This results in the following station names: AXL-F-BK-EIP-
With this switch position, modifying the IP
051 ... AXL-F-BK-EIP-159.
address via tools or web-based management
Behavior during initial startup, after resetting the IP is not possible.
parameters or after resetting to default settings
A valid IP address is not assigned (0.0.0.0) and 9.5 Resetting IP parameters
communication is therefore not possible.
Switch position 0E
The device transmits continuous DHCP discover messages
until a valid IP address has been received. The IP parameters stored on the device are reset.
All other settings made on the device are retained.
Each additional startup
– BootP is activated for switch position 00.
Within the first minute, DHCP requests are transmitted with – IP address, subnet mask: 0.0.0.0
the last valid IP address.
As long as the switch position 0E remains selected, no
Three cases are possible: connection to the device can be established.
1. The DHCP server accepts the desired address. IP communication is deactivated.
 The device starts with this IP address.
2. The DHCP server assigns a new IP address.
 The device applies the new IP parameters.
3. The DHCP server does not respond.
 The device transmits continuous DHCP Discover
messages until new IP parameters have been received.

107469_en_03 PHOENIX CONTACT 11 / 21


9.6 Plug and Play mode
Switch position 1A: activate Plug and Play mode
Switch position 1B: deactivate Plug and Play mode
Plug and Play mode enables local bus modules connected
in the field to be started up using the bus coupler without a
higher-level computer (engineering system).
If plug and play mode is enabled, then the writing of process
data is rejected. Read access to the process data is
possible.
If Plug and Play mode is disabled, then the bus will only be
commissioned if the configuration of the connected bus
matches the saved configuration.
See also section “Startup behavior of the bus coupler”.
107469_en_03
AXL F BK EIP EF
9.7 Resetting to the default settings
Switch position 12C
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.
Alternatively, the default setting can also be
restored via the reset button (see “Reset
button”).
9.8 Reserved/invalid switch position
The device starts with the previous settings, e.g.,  with the
settings that were valid before the device was restarted.
An invalid switch position is indicated by the RDY LED (red
on).
PHOENIX CONTACT 12 / 21
 AXL F BK EIP EF

10 Local diagnostic and status indicators

LNK ACT

NET RDY
MOD
CO
UL PP D
E

LNK ACT

Figure 5 Local diagnostic and status indicators

Designation Color Meaning State Description

UL Green ULogic On Communications power supply present.
Off Communications power supply not present.
NET Green/ Network status Green on At least one CIP connection is in place and the exclusive
red owner connection has no time-out.
Green flashing An IP address is configured, no CIP connection is yet in
place, and the exclusive owner connection has no time-
out.
Red flashing Connection time-out. A time-out of an exclusive owner
connection has occurred.
Red on An IP address conflict has been determined.
Flashing green/red Self test
Off Device is not ready for operation.
MOD Green/ Module status Green on Normal operation
red Green flashing The device is not configured.
Red on A unrecoverable error has occurred.
Red flashing A recoverable error has occurred.
Flashing green/red Self test
Off Device is not ready for operation.
CO Yellow/ Configuration Yellow on Parameterization of the I/O modules failed.
red Red on The active configuration of the local bus differs from the
saved configuration.
Off The active configuration of the local bus matches the
saved configuration.
PP Yellow Plug and Play On Plug and Play mode is activated.
mode Off Plug and Play mode is deactivated.

107469_en_03 PHOENIX CONTACT 13 / 21

 AXL F BK EIP EF

Designation Color Meaning State Description

RDY Green/ Ready Green on Device is ready for operation.
yellow/ Green/ Communications power undervoltage or surge voltage
red yellow flashing Overtemperature
Yellow on Firmware/bus coupler is booting
Yellow flashing Firmware update is being performed.
Flashing yellow/red Firmware update has failed.
Red flashing Faulty firmware
Red on Rotary encoding switches are set to an invalid/reserved
position.
Off Device is not ready for operation.
D Red/ Diagnostics of local bus communication
yellow/ Run Green on The station is ready to operate; communication within the
green station is OK.
All data is valid. An error has not occurred.
Active Green flashing The station is ready to operate. Communication within the
station is ok.
The data are not valid. The controller or higher-level net-
work is not providing valid data.
The module is not malfunctioning.
Ready Yellow on The station is ready to operate. No data are being ex-
changed.
Yellow flashing Access from Startup+ in I/O check mode
Flashing yellow/red Local bus error during active I/O check (with connected
Startup+)
Red flashing Local bus error on startup
Possible causes:
The configuration cannot be generated. Information from
one device is missing.
Chip version of a device is <V1.1
The desired and actual configuration are different
No local bus device connected
The maximum number of local bus devices is exceeded.
Red on The station is ready for operation but has lost connection
to at least one device.
Possible causes:
Communication error
Local bus device has been removed or configured device
is missing.
Reset at a local bus device
Serious device error at a local bus device (local bus device
can no longer be reached)
Power down Off Device is in (power) reset.
E Yellow/ Error Yellow on I/O warning at a local bus device
red Red on I/O error at a local bus device
Off No I/O messages present.

107469_en_03 PHOENIX CONTACT 14 / 21

 AXL F BK EIP EF

Designation Color Meaning State Description

LNK 1/2 Green Link port 1/2 On Connection via Ethernet to a module via port 1/2 estab-
lished
Off No connection established via port 1/2
ACT 1/2 Yellow Activity port 1/2 Flashing Transmission or reception of Ethernet telegrams at
port 1/2
Off No transmission or reception of Ethernet telegrams at
port 1/2

11 EtherNet/IP™: Object classes, messages, and services

The bus coupler maps the I/O device connected to the standard or user-defined CIP objects via the local bus.
The bus coupler supports the Common Industrial Protocol (CIP) according to the ODVA specification. For the objects that are
supported, please refer to the “CIP object classes” table.
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 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).

11.1 CIP class and instance services

The device supports the following class services and instance services:

Service code Service name

dec hex
01 01 Get_Attribute_All
02 02 Set_Attribute_All
05 05 Reset
14 0E Get_Attribute_Single
16 10 Set_Attribute_Single

107469_en_03 PHOENIX CONTACT 15 / 21

 AXL F BK EIP EF

11.2 CIP object classes

The device supports the following CIP object classes:

Class code Object type

dec hex
01 01 Identity object
02 02 Router object
04 04 Assembly object
06 06 Connection manager object
55 37 File object
71 47 Device level ring object
72 48 Quality of Service object
100 64 Configuration object
102 66 Axioline F module object
103 67 Axioline F diagnostics object
105 69 PDI object
244 F4 Port object class definition
245 F5 TCP/IP interface object
246 F6 Ethernet link object

For more detailed information, please refer to

the UM EN AXL F BK EIP - OBJECTS user
manual.

107469_en_03 PHOENIX CONTACT 16 / 21

 AXL F BK EIP EF

12 Reset button 12.2 Restoring the default settings

The bus coupler is supplied with the following default
The reset button is located beneath the top marking label on
settings:
the bus coupler.
Password private
IP settings
  IP address 0.0.0.0
1
  Subnet mask 0.0.0.0
2   Default gateway 0.0.0.0
  BootP activated
Firmware update
  Firmware update on next deactivated
restart
  TFTP server IP address 172.16.40.201
Figure 6 Reset button   Name of firmware update c2688394.fw
file
1 Labeling field System identification
2 Reset button   Name of device AXL F BK EIP
The reset button has two functions:   Description EtherNet/IP bus terminal
– Restarting the bus coupler   Location unknown
– Resetting of the default settings   Contact unknown
Plug and Play mode activated
12.1 Restarting the bus coupler Behavior in case of a fault in the Output substitute values
Restart the bus coupler by pressing the reset button during local bus
ongoing operation. (firmware version 1.30 or later)
The outputs of the station are set to the parameterized Access right IOL-CONF Full access
substitute values. (firmware version 1.30 or later)
The process image of the inputs is not re-read. If you wish to restore the default settings, proceed as
follows:
• Disconnect the power to the module.
• Press and hold the reset button.
• Switch on the power.
The LEDs indicate the initialization phase:

LED State Meaning

RDY Off Starting firmware
RDY Yellow on Initializing firmware
RDY Green Initialization complete

• When the RDY LED lights up green, release the button.

The default settings are restored.

107469_en_03 PHOENIX CONTACT 17 / 21

 AXL F BK EIP EF

13 Service interface
The service interface is located beneath the top marking
field on the bus coupler.

Figure 7 Service interface

1 Labeling field
2 Service interface
Using the service interface via USB, you can connect the
bus coupler to a PC on which Startup+, the startup and
diagnostic tool, is running.
Startup+ offers the following functions:
– Parameterization of the station I/O modules
– I/O check
– Diagnostics

For detailed information on Startup+, please

refer to the UM QS EN STARTUP+ user
manual.

107469_en_03 PHOENIX CONTACT 18 / 21


14 Startup behavior of the bus coupler
14.1 Plug and Play mode
Plug and Play mode active
The bus coupler supports Plug and Play mode.
Plug and Play mode enables local bus modules connected
in the field to be started up using the bus coupler without a
higher-level computer (engineering system).
The Plug and Play mode status (active or inactive) is stored
retentively on the bus coupler. The current mode is
displayed via the PP LED.
In Plug and Play mode, the connected local bus modules are
detected and their function checked.
If this physical configuration is ready to operate, it is started;
however, writing outputs is not enabled.
To enable writing outputs, Plug and Play mode must be
deactivated. The deactivation is to be saved at the same
time as saving the signal, active configuration, and
reference configuration.
Plug and Play mode inactive
When plug and play mode is deactivated, the reference
configuration is compared to the physical configuration. If
the configurations are identical, the bus coupler is set to the
RUN state on the first write access.
If the reference configuration and the physical configuration
differ, the LED CO lights up red. In this case, process data
exchange is not possible for safety reasons.
In order to operate the bus despite this, you have the
following two options:
1. Restore the original configuration so that the reference
configuration and the physical configuration are the
same again.
2. Activate plug-and-play mode and restart the bus
coupler so that the active physical configuration is
accepted as the reference configuration.
107469_en_03
AXL F BK EIP EF
14.2 Behavior in case of a fault in the local bus
Firmware version 1.30 or later.
In case a fault occurs in the local bus, you can parameterize
the behavior of the outputs of the I/O modules that can be
reached. You have the following options:
– The outputs remain in operation.
– The outputs output the parameterized substitute values.
A fault in the local bus can be caused by a bus interruption
or a missing I/O module.
The inputs of all I/O modules that can be reached can
always be read in.
Parameterize the behavior via web-based management or
“Configuration object” (class code 64hex, attribute 28).
14.3 Startup parameterization
There are Axioline F modules that can be parameterized (for
example, measuring ranges or substitute value behavior in
the event of a bus error).
You can parameterize these modules via Startup+ or the
PDI channel. See UM QS DE STARTUP+ and section
“Access to PDI objects”.
The parameterization is stored retentively on the I/O
modules, which is why this information only has to be written
once upon system startup.
When Plug and Play mode is deactivated, the bus coupler
checks the parameterization of the I/O modules as well as
the bus configuration. After the bus configuration has been
changed (e.g., module replacement), the bus coupler
prevents process data from being written, bit 3 is set in the
Axioline F diagnostics object (class code 67hex), and the
CO LED lights up yellow. If necessary, adjust the
parameterization and confirm this with attribute 7 (“Confirm
startup parametrization”) of the Configuration object (class
code 64hex). The bus coupler will then enable the output of
process data.
14.4 Configuration file (config.svc)
The bus coupler supports the administration of startup
parameterization for local bus modules in a configuration
file.
You can generate the file with Startup+ and store it on the
bus coupler via EtherNet/IP or FTP. See
UM QS DE STARTUP+.
The bus coupler transmits the parameters from the
configuration file to the connected local bus modules during
startup.
This makes replacing the device simple.
PHOENIX CONTACT 19 / 21
 AXL F BK EIP EF

15 Mapping process data to the Assembly object

The process data of the modules connected to the bus
coupler are mapped to the Assembly object. Approximately 1400 bytes are available in the
The following instances of the object are implemented: Ethernet frame for process data.

Instance Description
(dec) The current mapping of process data to the
100 Output data of digital, analog, and function process data words for the I/O modules
modules connected to the bus coupler can be viewed
The object contains all the input data for the via the web-based management for the bus
station. coupler under “EtherNet/IP™, I/O Assembly
table”.
110 Input data of digital, analog, and function
modules
The object contains all the output data for
the station.

Example: mapping of the process data

Example of a station
AXL F BK EIP AXL F AXL F AO8 1F AXL F AXL F  AXL F AI8 1F AXL F 
DI16/1 1H DI32/1 2H DO8/2-2A 2H CNT2 INC2 1F

  Input process data Output process data

AXL F Word 0 Byte 0 Byte 1 Word 0 - -
DI16/1 1H Channel 8 ... 1 Channel 16 ... 9
AXL F AO8 1F Word 1 IN1 Word 1 OUT1
Word 2 IN2 Word 2 OUT2
... ... ... ...
Word 8 IN8 Word 8 OUT8
AXL F Word 9 Byte 0 Byte 1 Word 9 - -
DI32/1 2H Channel 8 ... 1 Channel 16 ... 9
Word 10 Byte 2 Byte 3 Word 10 - -
Channel 24 ... 17 Channel 32 ... 25
AXL F  Word 11 - - Word 11 - Byte 0
DO8/2-2A 2H Channel 8 ... 1
AXL F AI8 1F Word 12 IN1 Word 12 - -
... ... ... ...
Word 19 IN8 Word 19 - -
AXL F  Word 20 Word 0 Word 20 Word 0
CNT2 INC2 1F ... ... ... ...
Word 33 Word 13 Word 33 Word 13

For further information on the assignment of
bytes and words, please refer to the module-
specific documentation (data sheet, user
manual).
Unused process data words, such
as dedicated input or output modules, are
marked with “-” in the table. Write access to
these process data words has no effect. Read
access always returns the value 0.

107469_en_03 PHOENIX CONTACT 20 / 21


16 SNMP: Simple Network
Management Protocol
The bus coupler supports SNMP v1 and v2c.
Management Information Base (MIB)
The corresponding latest MIBs are available
on the Internet at phoenixcontact.net/
products.
For the object descriptions, please refer to the ASN1
descriptions for this product.
The password for read access is “public”. This password
cannot be changed.
By default, the password for write and read access is
“private” in the delivery state. This password can be
changed at any time.
17 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.
There are three different types of DLR devices:
– Ring supervisor
– Ring node, Beacon-based
– Ring node, Announce-based
The bus coupler supports “Ring node, Beacon based”
mode.
The bus coupler does not support “Ring supervisor” or “Ring
node, Announce-based” mode.
18 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.
You can use web-based management to access static or
dynamic information. Examples of static information include
technical data or the MAC address. Examples of dynamic
information include IP addresses, status information, local
bus structure and diagnostics.
107469_en_03 PHOENIX CONTACT GmbH & Co. KG • 32823 Blomberg • Germany
phoenixcontact.com
AXL F BK EIP EF
Calling web-based management
You can address the device’s web server using the IP
address if it is configured accordingly. The device’s
homepage (web page) is accessed by entering the URL
“http://ip-address”.
Example: http://172.16.113.38
The default password is “private”.
If you cannot access the WBM pages, check
the connection settings in your browser.
Deactivate the proxy if set.
19 Firmware update
To update the bus coupler firmware, provide the bus coupler
with a firmware container via a TFTP server or load it onto
the bus coupler via FTP. You can use any FTP client or
TFTP server for this, such as the PC Worx Firmware
Updater.
If you do not use the PC Worx Firmware Updater, start the
firmware update using the web-based management. When
the firmware is being updated, the RDY LED flashes yellow.
For detailed information on firmware update
via TFTP, please refer to application note
TFTP FIRMWARE UPDATE AXL F BK.
20 Connection types
The device supports the connection types Exclusive Owner,
Input Only, and Listen Only.
All connection types can be configured by the scanner as a
Multicast or Point to Point connection in the Target to
Originator direction.
21 Device description (EDS)
In the case of EtherNet/IP™, a device description file (EDS)
is required for various configuration tools.
This EDS file can be downloaded via the product at
phoenixcontact.net/products.
The EDS file, which is on the bus coupler by default upon
delivery, can be accessed on the bus coupler via the “File
object” class code 37hex.
21 / 21