Product manual

B Protocols TAC Xenta Server – Gateway, Technical Manual
138 (184) Schneider Electric Buildings AB, June 2011
04-00124-06-en
B.3.2 Modbus TCP Interface
The Modbus TCP interface is added into the network pane of XBuilder,
as shown for an IPSim example network in the following screenshot.
Interface Properties
• Server IP Address – Numeric IP address of the applicable Mod-
bus TCP server. The IP address must uniquely identify the server
on the network, and be directly accessible to any Xenta 913 clients
through their 10Base-T Ethernet connections.
• Server TCP Port# – The default port number of 502 is the value
specified in the Modbus TCP protocol standard. In very rare cases
the Modbus TCP port number may be reassigned on the server, in
which case the new TCP Port# must be entered in place of the
default.
Interface Status Signals
The Modbus TCP interface driver generates several network specific
communication status signals, as described below.
• ComsFail – Flags a complete communications failure. Activated
only if the connection to the Modbus TCP server has failed. Nor-
mally caused by an incorrect IP address or port number being
entered for the server, but may be caused by incorrect LAN
cabling or security settings.
• OutsFail – Flags if writing to one or more output values has failed
on the Modbus network. Normally a write fails because an incor-
rect register address has been entered.
• InsFail – Flags if reading of one or more input values has failed
on the Modbus network. Normally a read fails because an incor-
rect register address has been entered.
• online – Flags ONLINE during normal network communications,
and will change to OFFLINE only if communication has failed to
all slaves on the Modbus network. An OFFLINE condition nor-
mally indicates incorrect communication property settings, or
faulty wiring of the network between the Xenta 913 and the Mod-
bus TCP server.