+$/067$'&+,&$*2.$5/658+(72.<2%(,-,1*0,/$1208/+286(&29(175<381(&23(1+$*(1
HMS Industrial Networks
Mailing address: Box 4126, 300 04 Halmstad, Sweden
Visiting address: Stationsgatan 37, Halmstad, Sweden
User Manual
Anybus® X-gateway Modbus-TCP
Modbus-TCP
Doc.Id. HMSI-168-45
Rev. 1.10
Important User Information
This document is intended to provide a good understanding of the functionality offered by the Anybus X-gateway
Modbus-TCP - Modbus-TCP. The reader of this document is expected to be familiar with high level software de-
sign, and communication systems in general.
Liability
Every care has been taken in the preparation of this manual. Please inform HMS Industrial Networks AB of any
inaccuracies or omissions. The data and illustrations found in this document are not binding. We, HMS Industrial
Networks AB, reserve the right to modify our products in line with our policy of continuous product development.
The information in this document is subject to change without notice and should not be considered as a commit-
ment by HMS Industrial Networks AB. HMS Industrial Networks AB assumes no responsibility for any errors that
may appear in this document.
There are many applications of this product. Those responsible for the use of this device must ensure that all the
necessary steps have been taken to verify that the applications meet all performance and safety requirements in-
cluding any applicable laws, regulations, codes, and standards.
HMS Industrial Networks AB will under no circumstances assume liability or responsibility for any problems that
may arise as a result from the use of undocumented features, timing, or functional side effects found outside the
documented scope of this product. The effects caused by any direct or indirect use of such aspects of the product
are undefined, and may include e.g. compatibility issues and stability issues.
The examples and illustrations in this document are included solely for illustrative purposes. Because of the many
variables and requirements associated with any particular implementation, HMS Industrial Networks AB cannot
assume responsibility for actual use based on these examples and illustrations.
Intellectual Property Rights
HMS Industrial Networks AB has intellectual property rights relating to technology embodied in the product de-
scribed in this document. These intellectual property rights may include patents and pending patent applications
in the US and other countries.
Trademark Acknowledgements
Anybus ® is a registered trademark of HMS Industrial Networks AB. All other trademarks are the property of their
respective holders.
Warning: This is a class A product. in a domestic environment this product may cause radio interference in
which case the user may be required to take adequate measures.
ESD Note: This product contains ESD (Electrostatic Discharge) sensitive parts that may be damaged if ESD
control procedures are not followed. Static control precautions are required when handling the prod-
uct. Failure to observe this may cause damage to the product.
Warning: DO NOT USE SD CARD OR USB CONNECTOR WHILE CIRCUIT IS LIVE UNLESS THE AREA IS
KNOWN TO BE FREE OF IGNITABLE CONCENTRATIONS OF FLAMMABLE GAS OR VAPORS.
Anybus X-gateway Modbus-TCP - Modbus-TCP User Manual
Rev 1.10
Copyright© HMS Industrial Networks AB
Nov 2012 Doc Id HMSI-168-45
Doc.Id. HMSI-168-45
Anybus X-gateway Modbus-TCP - Modbus-TCP
Doc.Rev. 1.10
Table of Contents
Table of Contents
Preface About This Document ..................................................................... 5
Related Documents..................................................................................................................... 5
Document History ...................................................................................................................... 5
Conventions & Terminology..................................................................................................... 6
Sales and Support ........................................................................................................................ 7
Chapter 1 Getting Started ................................................................................. 8
Chapter 2 Anybus X-gateway Modbus-TCP .................................................... 9
Introduction ................................................................................................................................. 9
Features....................................................................................................................................... 10
Configuring the Modbus-TCP Network ............................................................................... 10
Functional Overview ................................................................................................................ 11
Data Exchange........................................................................................................................... 12
I/O Mapped Data..................................................................................................................... 13
Parameter Data .......................................................................................................................... 13
Control/Status Word................................................................................................................ 13
Live List ...................................................................................................................................... 14
Transaction Status List ............................................................................................................. 15
Exception Code List ................................................................................................................. 16
Chapter 3 About the Anybus X-gateway Modbus-TCP ..................................17
External View ............................................................................................................................ 17
Mounting the X-gateway..........................................................................................................18
DIN-rail Mounting.......................................................................................................... 18
Wall Mounting................................................................................................................. 19
Status LEDs ............................................................................................................................... 20
USB Connector.......................................................................................................................... 21
Modbus-TCP Connectors (Network 1)................................................................................. 21
Modbus-TCP Connectors (Network 2)................................................................................. 21
Power Connector ...................................................................................................................... 22
Doc.Id. HMSI-168-45
Anybus X-gateway Modbus-TCP - Modbus-TCP
Doc.Rev. 1.10
Chapter 4 SD Card Functionality.................................................................... 23
General Advice and Guidelines............................................................................................... 23
Starting Up.................................................................................................................................. 23
Easy Backup ............................................................................................................................... 24
Simple Configuration Copy ..................................................................................................... 24
Easy Replacement...................................................................................................................... 24
SD Card Synchronization Failure ........................................................................................... 25
Chapter 5 Modbus-TCP Functions for Network 2 ......................................... 26
Chapter 6 Modbus-TCP Functions for Network 1 ......................................... 27
Chapter 7 Network Configuration .................................................................. 28
General Information ................................................................................................................. 28
Introduction ............................................................................................................................... 29
Overview..................................................................................................................................... 30
Home................................................................................................................................31
Configuration ............................................................................................................................. 32
Authentication .................................................................................................................. 32
Modbus Client (Network 2) ............................................................................................. 33
Modbus Servers................................................................................................................. 34
Modbus-TCP (Network 1 Server Interface)....................................................................... 37
Tools........................................................................................................................................... 39
X-gateway Management .................................................................................................... 39
Backup and Restore .......................................................................................................... 39
Mapping Overview ............................................................................................................ 40
Mapping Overview Example............................................................................................. 40
Transaction Monitor ......................................................................................................... 42
Appendix A Technical Specification .................................................................. 43
Protective Earth (PE) Requirements...................................................................................... 43
Power Supply ............................................................................................................................. 43
Environmental Specification ................................................................................................... 43
Temperature...................................................................................................................... 43
Relative Humidity............................................................................................................. 43
EMC (CE) Compliance ............................................................................................................ 44
Appendix B Anybus IPconfig Tool .................................................................... 45
Appendix C Copyright Notices .......................................................................... 46
Doc.Id. HMSI-168-45
Anybus X-gateway Modbus-TCP
Doc.Rev. 1.10
Preface
P. About This Document
For more information, documentation etc., please visit the HMS website, www.anybus.com.
P.1 Related Documents
P.2 Document History
Summary of Recent Changes (1.00... 1.10)
Revision List
Document Author
Modbus Application Protocol Specification V1.1B Modbus Organization
Change Page(s)
Updated information about data exchange to reflect the parameter data features 12
Added information about I/O mapped data and parameter data 13
Added information about the transaction status list 15
Added information about the exception code list 16
Added information about the identification LED sequence 20
Added available Modbus functions 26
Updated the configuration web pages to reflect new and revised functionality 28
Updated information about the Anybus IPconfig tool 45
Revision Date Author(s) Chapter(s) Description
1.00 2011-06-28 KaD - First official release
1.10 2012-11-21 KaD 2, 3, 5, 6, B Major update
About This Document P-6
Doc.Id. HMSI-168-45
Anybus X-gateway Modbus-TCP
Doc.Rev. 1.10
P.3 Conventions & Terminology
The following conventions are used throughout this manual:
• Numbered lists provide sequential steps
• Bulleted lists provide information, not procedural steps
• The terms ‘Anybus’, ‘X-gateway’ or ‘module’ refers to the Anybus X-gateway module
• Hexadecimal values are written in the format NNNNh, where NNNN is the hexadecimal value
• A byte always consists of 8 bits
• The terms ‘master’, ‘scanner’, ‘client’ and ‘controller’ will be used interchangeably to describe a
controlling unit on the network
• The terms ‘slave’, ‘adapter’, ‘server’ and ‘device’ will be used interchangeably to describe units
that are controlled by controlling units on the network
About This Document P-7
Doc.Id. HMSI-168-45
Anybus X-gateway Modbus-TCP
Doc.Rev. 1.10
P.4 Sales and Support
Sales Support
HMS Sweden (Head Office)
E-mail: sales@hms.se E-mail: support@hms-networks.com
Phone: +46 (0) 35 - 17 29 56 Phone: +46 (0) 35 - 17 29 20
Fax: +46 (0) 35 - 17 29 09 Fax: +46 (0) 35 - 17 29 09
Online: Online: www.anybus.com
HMS North America
E-mail: us-sales@hms-networks.com E-mail: us-support@hms-networks.com
Phone: +1-312 - 829 - 0601 Phone: +1-312-829-0601
Toll Free: +1-888-8-Anybus Toll Free: +1-888-8-Anybus
Fax: +1-312-629-2869 Fax: +1-312-629-2869
Online: Online: www.anybus.com
HMS Germany
E-mail: ge-sales@hms-networks.com E-mail: ge-support@hms-networks.com
Phone: +49 (0) 721-96472-0 Phone: +49 (0) 721-96472-0
Fax: +49 (0) 721-96472-10 Fax: +49 (0) 721-96472-10
Online: www.anybus.de Online: www.anybus.de
HMS Japan
E-mail: jp-sales@hms-networks.com E-mail: jp-support@hms-networks.com
Phone: +81 (0) 45-478-5340 Phone: +81 (0) 45-478-5340
Fax: +81 (0) 45-476-0315 Fax: +81 (0) 45-476-0315
Online: www.anybus.jp Online: www.anybus.jp
HMS China
E-mail: cn-sales@hms-networks.com E-mail: cn-support@hms-networks.com
Phone: +86 (0) 10-8532-3183 Phone: +86 (0) 10-8532-3023
Fax: +86 (0) 10-8532-3209 Fax: +86 (0) 10-8532-3209
Online: www.anybus.cn Online: www.anybus.cn
HMS Italy
E-mail: it-sales@hms-networks.com E-mail: it-support@hms-networks.com
Phone: +39 039 59662 27 Phone: +39 039 59662 27
Fax: +39 039 59662 31 Fax: +39 039 59662 31
Online: www.anybus.it Online: www.anybus.it
HMS France
E-mail: fr-sales@hms-networks.com E-mail: fr-support@hms-networks.com
Phone: +33 (0) 3 68 368 034 Phone: +33 (0) 3 68 368 033
Fax: +33 (0) 3 68 368 031 Fax: +33 (0) 3 68 368 031
Online: www.anybus.fr Online: www.anybus.fr
HMS UK & Eire
E-mail: uk-sales@anybus.co.uk E-mail: support@hms-networks.com
Phone: +44 (0) 1926 405599 Phone: +46 (0) 35 - 17 29 20
Fax: +44 (0) 1926 405522 Fax: +46 (0) 35 - 17 29 09
Online: www.anybus.co.uk Online: www.anybus.com
HMS Denmark
E-mail: info@anybus.dk E-mail: support@hms-networks.com
Phone: +45 (0) 22 30 08 01 Phone: +46 (0) 35 - 17 29 20
Fax: +46 (0) 35 17 29 09 Fax: +46 (0) 35 - 17 29 09
Online: www.anybus.com Online: www.anybus.com
HMS India
E-mail: in-sales@anybus.com E-mail: in-support@hms-networks.com
Phone: +91 (0) 20 40111201 Phone: +46 (0) 35 - 17 29 20
Fax: +91 (0) 20 40111105 Fax: +46 (0) 35 - 17 29 09
Online: www.anybus.com Online: www.anybus.com
Doc.Id. HMSI-168-45
Anybus X-gateway Modbus-TCP
Doc.Rev. 1.10
Chapter 1
1. Getting Started
The purpose of this chapter is to give a short description on how to install the X-gateway and get it up
and running, transferring I/O data between Network 1 (the controlling network, where the X-gateway
acts as a server) and Network 2 (the controlled network, where the X-gateway acts as a client).
Perform the following steps when installing the module:
1. Mount the module. See “Mounting the X-gateway” on page 18 for details.
2. Connect the X-gateway to the Network 2. See “External View” on page 17.
3. Connect the power cable and apply power.
4. Access the configuration web pages.
• Connect a PC to the Network 2 (see “External View” on page 17) and open a web browser.
Enter the IP address of the X-gateway and access the configuration web pages. If the IP ad-
dress of the X-gateway is unknown, use the Anybus IPconfig tool to find it. See “Anybus IP-
config Tool” on page 45.
• Configure the Network 2 client interface. See “Modbus Client (Network 2)” on page 33.
• Set up all Modbus servers and transactions using the configuration web pages. See “Modbus
Servers” on page 34 and “Network Configuration” on page 28.
• Configure the Network 1 server interface. See “Modbus-TCP (Network 1 Server Interface)”
on page 37.
5. Configure the Modbus-TCP client (PLC) on Network 1. See “Configuring the Modbus-TCP
Network” on page 10.
6. Connect the X-gateway to the Modbus-TCP (slave) network. See “External View” on page 17.
Doc.Id. HMSI-168-45
Anybus X-gateway Modbus-TCP
Doc.Rev. 1.10
Chapter 2
2. Anybus X-gateway Modbus-TCP
2.1 Introduction
The Anybus X-gateway Modbus-TCP is a series of network gateways, used to provide a seamless con-
nection between a Modbus-TCP network and a controlling network. This particular product connects a
Modbus-TCP network to another Modbus-TCP network. In order to avoid confusion, the controlling
network will be called Network 1, and the network that is controlled will be called Network 2.
The X-gateway enables the master of Network 1 to control Network 2. These X-gateways makes it pos-
sible to integrate Modbus-TCP devices into almost any other PLC system and their supported networks.
The X-gateway is based on patented Anybus
technology, a proven industrial communica-
tion solution used all over the world by lead-
ing manufacturers of industrial automation
products. Each module offers Modbus-TCP
master connectivity to one of these industrial
networks: EtherNet/IP, Modbus-TCP,
PROFINET, Modbus RTU, EtherCAT, CC-
Link, ControlNet, CANopen, DeviceNet
and PROFIBUS DP-V1.
No proprietary configuration software is
needed. All necessary configuration is made
via the built-in web interface.
The Modbus-TCP server interface (the Net-
work 1 interface) is configured with a stand-
ard engineering tool of the PLC. No programming is required.
The X-gateway transmits I/O data transparently between the two networks.
Device Level with Modbus-TCP Slaves
Control Network
Master
(e.g. PLC) Slave Slave Slave Slave
Slave Slave Slave Slave
Anybus X-gateway
Modbus-TCP
Modbus-TCP
Master
Control
Network
Slave
Anybus X-gateway Modbus-TCP 10
Doc.Id. HMSI-168-45
Anybus X-gateway Modbus-TCP
Doc.Rev. 1.10
2.2 Features
Anybus X-gateways for Modbus-TCP act as intelligent links between two industrial networks. On Net-
work 2, they function as clients (masters) while they function as servers (slaves) on Network 1. The im-
plementation is based on the Anybus NP30 ASIC technology.
2.3 Configuring the Modbus-TCP Network
The Anybus X-gateway is a Modbus-TCP server (slave) on Network 1. The general settings for the serv-
er interface are configured using the configuration web pages (see “Modbus-TCP (Network 1 Server In-
terface)” on page 37). All data transfers must be configured using the Modbus-TCP configuration tool.
Please note that the size of the I/O data that can be read from and written to the module is defined when
configuring the X-gateway using the configuration web pages.
There are a number of different configuration tools for Modbus-TCP available on the market. The
choice of tool depends on the application and the Modbus-TCP client of Network 1.
An application note, describing how to configure an Anybus Modbus-TCP server interface with RS
Logix and RS Networx, is available on the support pages for the Anybus X-gateway Modbus-TCP -
Modbus-TCP module at ‘www.anybus.com’.
Anybus X-gateway Modbus-TCP 11
Doc.Id. HMSI-168-45
Anybus X-gateway Modbus-TCP
Doc.Rev. 1.10
2.4 Functional Overview
Internally, the X-gateway consists of an intelligent gateway platform: an Anybus Modbus-TCP client in-
terface for Network 2 and an Anybus Modbus-TCP server interface for Network 1. The two interfaces
are interconnected through the intelligent gateway platform, which basically forwards data from one net-
work to the other and vice versa as shown below. This design allows almost any other industrial network
to be connected to a Modbus-TCP master on a separate Modbus-TCP network.
Industrial network
Modbus-TCP network
Anybus Modbus-TCP
Master Interface
Anybus network
slave interface
Anybus X-gateway Modbus-TCP 12
Doc.Id. HMSI-168-45
Anybus X-gateway Modbus-TCP
Doc.Rev. 1.10
2.5 Data Exchange
Each of the two network interfaces exchanges data on its network through two buffers. The X-gateway
forwards the data between these buffers as shown below. Note that this process is separated from the
network data exchange. While the X-gateway ensures data consistency (where applicable), it does not
feature any built-in mechanisms for synchronization between the two Modbus-TCP networks.
Each buffer holds a maximum of 256 bytes of data. The first two I/O mapped bytes in either direction
can be dedicated for control/status information, and another eight bytes of data coming from Network
2 can feature a live list.
Through the dedicated control word, the client on Network 1 starts/stops the exchange of data on Net-
work 2, and also resets the X-gateway if needed. The client on Network 1 can see the status of Network
2 in the corresponding status word. The live list feature gives the client on Network 1 the opportunity
to continuously see and monitor the status of each individual transaction on Network 2.
Two additional lists, transaction status and exception codes, retrievable from the module by the master
on Network 1, provides detailed error information about all transactions.
The amount of data that shall be exchanged, and the use of the control/status word and the live list, is
specified separately for each application. This means that even though up to 256 bytes of data can be
potentially forwarded to an interface, the amount of data that will actually be exchanged on that network
is determined by the settings in the configuration web pages.
The available control/status functionality is described below, as well as the live list and the transaction
status and exception codes lists. Also note that the terminology and definitions used for different types
of data vary greatly between different networking systems.
Industrial Network InterfaceModbus-TCP Network Interface
Industrial network
Modbus-TCP network
Data To
the Modbus-TCP
Network
Data From
the Modbus-TCP
Network
Data From
the Modbus-TCP
Network
Data to
the Modbus-TCP
Network
Status Word
Control Word
Anybus X-gateway Modbus-TCP 13
Doc.Id. HMSI-168-45
Anybus X-gateway Modbus-TCP
Doc.Rev. 1.10
2.6 I/O Mapped Data
I/O mapped data is cyclic data, exchanged between the networks and/or devices at a high transfer rate.
It is associated with data that is continuously sent on the network.
2.7 Parameter Data
Parameter data is usually exchanged acyclically, to set or change parameters in devices before or during
normal process. Typical parameter data that can be retrieved from the module by the master of
Network 1 includes the transaction status list and the exception code list.
2.8 Control/Status Word
The Control/Status word is always retrievable using acyclical access. Optionally, the Control/Status
word can also be I/O mapped. The I/O mapping can be enabled/disabled when configuring
Network 1 via the configuration web pages. See “Modbus-TCP (Network 1 Server Interface)” on page
37.
For information about how to access the Control/Status word, either I/O mapped or using parameter
access, see “Mapping Overview” on page 40.
The Control word is a 16-bit word (uint16) used by Network 1 to control the Anybus X-gateway and
subsequently also Network 2.
The Status word is a 16-bit word used by the X-gateway to report its current actual status to Network 1.
Bit Value Description
0 (Least signifi-
cant bit)
0 Puts the X-gateway in idle state
1 Puts the X-gateway in run state
1 - A reboot of the X-gateway is triggered by a rising edge, i.e. a transition from 0 to 1
2-7 Set to zero Unused
8-15 Set to zero Unused
Bit Value Description
0 (Least signifi-
cant bit)
0 The X-gateway is in idle state
1 The X-gateway is in run state
1 - This bit is reflecting the state of bit 1 in the control word
Either 0 or 1
2-7 (reserved) Unused
8-15 (reserved) Unused
Anybus X-gateway Modbus-TCP 14
Doc.Id. HMSI-168-45
Anybus X-gateway Modbus-TCP
Doc.Rev. 1.10
2.9 Live List
The live list features the possibility for Network 1 to continuously receive an I/O mapped list containing
the status of every transaction on Network 2.
It is accessible using parameter access, and also I/O mapped by default. The I/O mapped live list can
be enabled/disabled when configuring the Network 1 settings. See “Modbus-TCP (Network 1 Server
Interface)” on page 37. If the I/O mapped live list is enabled, it will occupy either byte 0-7 (control/
status word not enabled) or byte 2-9 (control/status word enabled and mapped to the first two bytes) in
the input data area.
All transactions and their places in the live list are also visible in the Transaction Monitor on the config-
uration web pages.
The live list consists of a bit array with 64 elements, where each bit corresponds to a transaction on Net-
work 2 as in the table below.
• Bit set to 1
Transaction successful.
• Bit set to 0
Transaction not successful.
Note: the reason for the unsuccessful transaction can be found on the corresponding index in
the transaction status list.
The order of the transactions in the live list conforms to the order in which they are stored in the Mod-
bus Server list.
Example
Consider the following configuration:
• Server 1 : a total of 2 transactions
• Server 2 : a total of 3 transactions
• Server 3 : a total of 1 transaction
This scenario will produce a live list as follows (assuming that the transactions are successful):
Note: Use the Modbus function “Read Discrete Inputs” to access the live list as a bit array.
Byte 7 Byte 6-1 Byte 0
Bit 63 Bit 62-56 Bit 55-8 Bit 7 Bit 6 - 2 Bit 1 Bit 0
Status of trans-
action no 63
Status of trans-
action no 62-56
... Status of trans-
action no 7
Status of trans-
action no 6 - 2
Status of trans-
action no 1
Status of trans-
action no 0
Bit 63 Bit 62 - 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
--Server 3,
transaction 1
Server 2,
transaction 3
Server 2,
transaction 2
Server 2,
transaction 1
Server 1,
transaction 2
Server 1,
transaction 1
00111111
Anybus X-gateway Modbus-TCP 15
Doc.Id. HMSI-168-45
Anybus X-gateway Modbus-TCP
Doc.Rev. 1.10
2.10 Transaction Status List
This list holds information about the transactions between Network 2 and the module, from the per-
spective of the module.
It is a list available from the module, which is possible to be retrieved acyclically (using parameter access)
by the Modbus-TCP network. It contains a byte array with 64 elements, where each byte contains a
transaction status code as in the table below.
The indexes in the transaction status list correspond completely to the indexes in the transaction live list.
Transaction status codes
Byte 0 Byte 1 Byte 2-6 Byte 7 Byte 8 - 55 Byte 56-62 Byte 63
Status of trans-
action no 0
Status of trans-
action no 1
Status of trans-
action no 2-6
Status of trans-
action no 7
... Status of trans-
action no 56-62
Status of trans-
action no 63
Transaction Status
Code Description
0 Running ok
1 Gateway idle
2 No link
3 Modbus exception
4 Timeout
5 Gateway disconnect
6 Server disconnect
7 Cannot connect
8 Modbus header error
9 Internal gateway error
10 No valid data
11 Stop sending data to Modbus server
12 Unconfigured transaction
Anybus X-gateway Modbus-TCP 16
Doc.Id. HMSI-168-45
Anybus X-gateway Modbus-TCP
Doc.Rev. 1.10
2.11 Exception Code List
If Modbus transactions fail, the slaves can respond with an exception code. These can be found in the
exception code list available from the module, possible to be retrieved acyclically (using parameter ac-
cess) by the Modbus-TCP network. It contains a byte array with 64 elements, where each byte contains
an transaction exception code as in the table below. The indexes in the exception code list correspond
completely to the indexes in the transaction live list.
Standard Modbus exception codes
Note: The exception codes found in the exception code list are only relevant if the corresponding trans-
action status codes equals 3: “Modbus exception”. See “Transaction Status List” on page 15 for more
information.
Note: If the slave responds with an exception code not in the list, refer to the documentation of the
slave for details.
Byte 0 Byte 1 Byte 2-6 Byte 7 Byte 8-55 Byte 56-62 Byte 63
Exception code
for transaction
no 0
Exception code
for transaction
no 1
Exception code
for transaction
no 2 - 6
Exception code
for transaction
no 7
Exception code
for transaction
no 8 - 55
Exception code
for transaction
no 56 - 62
Exception code
for transaction
no 63
Exception Code Description
00 No error
01 Illegal function
02 Illegal data address
03 Illegal data value
04 Slave device failure
05 Acknowledge
06 Slave device busy
08 Memory parity error
0A Gateway path unavailable
0B Gateway target device failed to respond
Doc.Id. HMSI-168-45
Anybus X-gateway Modbus-TCP
Doc.Rev. 1.10
Chapter 3
3. About the Anybus X-gateway Modbus-TCP
3.1 External View
•A: Power Connector
This connector is used to apply power to the X-
gateway. It is also possible to connect protective
earth (PE) to the power connector. See “Power
Connector” on page 22.
• B: SD Card Slot
This slot adds the possibility to store and load con-
figurations from an SD card. See “SD Card Func-
tionality” on page 23.
•C: USB Port
This port adds the possibility to connect a PC to the
X-gateway to perform firmware upgrades. See
“USB Connector” on page 21.
•D: Status LEDs
See “Status LEDs” on page 20.
•E: DIN-rail Connector
The DIN-rail mechanism fastens the X-gateway to
a DIN-rail and connects the module to protective
earth (PE). See “Mounting the X-gateway” on page
18.
• F: Modbus-TCP Connector (Network 1)
See “Modbus-TCP Connectors (Network 1)” on
page 21.
• G: Modbus-TCP Connectors (Network 2)
2-port switch with daisy-chain functionality. See
“Modbus-TCP Connectors (Network 2)” on page
21.
A
C
DE
B
F
G
About the Anybus X-gateway Modbus-TCP 18
Doc.Id. HMSI-168-45
Anybus X-gateway Modbus-TCP
Doc.Rev. 1.10
3.2 Mounting the X-gateway
The Anybus X-gateway can be physically installed either by mounting it onto a DIN-rail or, if installed
in areas exposed to vibration, by mounting it on a wall for more stability.
3.2.1 DIN-rail Mounting
Make sure the DIN-rail fastening mechanism on the back of
the module is in a fixed and closed position, i. e. pushed all the
way up.
To mount the module, first hook it on to the DIN-rail (1),
then push it against the DIN-rail to make it snap on (2).
To unmount the module, a screwdriver is needed. Use the
screwdriver to push the DIN-rail fastening mechanism on the
back of the module down until it locks in a fixed and open po-
sition (1). Then unhook the module from the DIN-rail (2).
Note: Do not leave the module with the DIN-rail fastening
mechanism in a fixed and open position. This may eventually
wear the fastening mechanism out so it cannot be used effi-
ciently. Be sure to push the DIN-rail fastening mechanism
back into the fixed and closed position after unmounting the
module.
About the Anybus X-gateway Modbus-TCP 19
Doc.Id. HMSI-168-45
Anybus X-gateway Modbus-TCP
Doc.Rev. 1.10
3.2.2 Wall Mounting
Use the wall mounting option if there is a need to place the X-gateway in an environment exposed to
vibration. This way of mounting the module offers more stability than the traditional DIN-rail mount-
ing.
Note: The X-gateway should be fastened in a standing-up position, to ensure a constant air flow.
Note: When mounting the X-gateway to a wall using the wall mount option, do not forget to connect
the module to protective earth (PE) via the power connector. See “Power Connector” on page 22.
Mounting Instructions
Step Description Visual description
Open up the package containing the wall
mounting accessories.
- One metal frame
- Industrial velcro
- Four plastic vibration dampers
Remove the plastic protection from one
side of the velcro.
Attach the velcro to the metal frame.
Attach the four plastic vibration dampers
to the X-gateway, on the side that will face
the wall.
Remove the plastic protection from the
other side of the velcro.
Turn the X-gateway around, so that the
plastic vibration dampers face down-
wards.
Fasten the metal frame to the X-gateway
by pressing the frame firmly against the X-
gateway, making the two velcro parts
attach to each other.
Attach the metal frame and the X-gateway
to a wall using screws and washers (not
enclosed).
1
2
3
4
5
About the Anybus X-gateway Modbus-TCP 20
Doc.Id. HMSI-168-45
Anybus X-gateway Modbus-TCP
Doc.Rev. 1.10
3.3 Status LEDs
Note: A test sequence is performed on all LEDs during startup.
Note: An identification LED sequence can be performed on LEDs 1, 5 and 6 by clicking the “Wink
device” button in the X-gateway Management section in the web configuration interface.
X-gateway and Network 2 LEDs
Network 1 LEDs
LED no State Status
1 - Gateway Status
(GW)
Off Power off
Alternating red/green Missing configuration
Flashing green Idle
Green Running
Flashing red Invalid configuration
Red Fatal error
5 - SD card
(SD)
Green Accessing SD card
Flashing red Failure
6 - Modbus-TCP Status
(MTCP)
Off Power off
Green Communicating with Modbus-TCP net-
work
Flashing red Transaction error or timeout
Red Fatal error
7, 8 - Ethernet Link 1
(LA1), Ethernet Link 2
(LA2)
Off No link
Flashing green Receiving/transmitting Ethernet packets
at 10/100 Mbit
LED no State Status
2 Not used -
3 - Network Status Off Power off, or no IP address
Green I/O data exchanged, normal operation
Flashing green Waiting for connections
Red Duplicate IP address, or fatal event
(restart X-gateway)
Flashing red Process active timeouta
a. For more information, see “Available settings for the Modbus-TCP network” on page
38.
4- Module Status Off Power off
Green Normal operation
Red Major fault (the X-gateway needs a
restart)
Flashing red IP address conflict
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
/