AXL F BK EIP EF
107469_en_01 PHOENIX CONTACT 19 / 20
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.
The following instances of the object are implemented:
Example: mapping of the process data
Instance
(dec)
Description
100 Output data of digital, analog, and function
modules
The object contains all the input data for the
station.
110 Input data of digital, analog, and function
modules
The object contains all the output data for
the station.
Approximately 1400bytes are available in the
Ethernet frame for process data.
The current mapping of process data to the
process data words for the I/O modules
connected to the bus coupler can be viewed
via the web-based management for the bus
coupler under “EtherNet/IP™, I/O Assembly
table”.
Example of a station
AXLFBKEIP AXL F DI16/1
1H
AXLAO8 AXL F DI32/1
2H
AXLFDO8/
2-2A2H
AXLAI8AXLCNT2/
INC2
Input process data Output process data
AXL F DI16/1
1H
Word 0 Byte 0 Byte 1 Word 0 - -
Channel 8 ... 1 Channel 16 ... 9
AXLAO8 Word 1 IN1 Word 1 OUT1
Word 2 IN2 Word 2 OUT2
... ... ... ...
Word 8 IN8 Word 8 OUT8
AXL F DI32/1
2H
Word 9 Byte 0 Byte 1 Word 9 - -
Channel 8 ... 1 Channel 16 ... 9
Word 10 Byte 2 Byte 3 Word 10 - -
Channel 24 ...
17
Channel 32 ...
25
AXLFDO8/
2-2A2H
Word 11 - - Word 11 - Byte 0
Channel 8 ... 1
AXLAI8 Word 12 IN1 Word 12 - -
... ... ... ...
Word 19 IN8 Word 19 - -
AXLCNT2/
INC2
Word 20 Word 0 Word 20 Word 0
... ... ... ...
Word 33 Word13 Word 33 Word13
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, e.g.,in the case
of dedicated input or output modules, are
marked with “-” in the table. There is no write
access to these process data words, read
access always returns the value 0.
AXL F BK EIP EF
107469_en_01 20 / 20
PHOENIX CONTACT GmbH & Co. KG • 32823 Blomberg • Germany
phoenixcontact.com
16 Simple Network Management
Protocol - SNMP
The bus coupler supports SNMP v1 and v2c.
Management Information Base - MIB
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.
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.
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, local bus
structure, and local bus diagnostics).
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 password is “private”.
19 Firmware update
In order to update the firmware of the bus coupler, provide
the bus coupler with a firmware container via a TFTP server
or load it onto the bus coupler via FTP. Any FTP client or
TFTP server can be used for this, e.g.,the FactoryManager.
If the FactoryManager is not used, initialize the firmware
update via web-based management. When carrying out the
firmware update, the RDY LED flashes yellow.
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 37
hex
.
The corresponding latest MIBs are available
on the Internet at phoenixcontact.net/
products.
If you cannot access the WBM pages, check
the connection settings in your browser and
deactivate the proxy, if set.
For detailed information on firmware update
via TFTP, please refer to application note
TFTPFIRMWAREUPDATEAXLFBK.

2702782

Mfr. #:
Manufacturer:
Phoenix Contact
Description:
I/O Modules AXL F BK EIP EF
Lifecycle:
New from this manufacturer.
Delivery:
DHL FedEx Ups TNT EMS
Payment:
T/T Paypal Visa MoneyGram Western Union

Products related to this Datasheet