17.3 Modbus/TCP
The following chapter describes the functionality of the INTECONT® Satus as a
Modbus/TCP server in the Ethernet.
The following are described in detail:
n
The configuration of the Ethernet connection (subscriber address allocation),
n
The ‘FIELDBUS’ mode of operation between an ethernet client and the INTECONT®
Satus vie Modbus/TCP,
n
Notes for troubleshooting and diagnosis
17.3.1 Guidelines for commissioning
n
Activating the Modbus/TCP protocol type in the INTECONT® Satus
n
Parameterization of the Ethernet address
n
Start communication by the master
17.3.2 Ethernet functionality
n
The connection is an RJ45 plug.
n
The server can exchange data with up to 3 clients simultaneously. If the EasyServe tool
is used, it can occupy one of the three channels if the coupling is performed over the net-
work. The data are either sent as Modbus (RTU)/TCP packets or are expected as such
from external. The functional range is described in more detail below.
n
Monitoring the bus interface
n
The Ethernet interface is easily parametrized using the basic model’s operating station
or the EasyServe diagnostic tool.
The INTECONT® Satus behaves as a Modbus/TCP server, after the ‘OPEN MODBUS/TCP
SPECIFICATION, Release 1.0,’ 29th March 1999 standard. It can handle all class 1 and
class 2 function codes (except for FC7) and the most important class 2 codes (FC15 and
FC23).
This data representation is based entirely on the Modbus standard. The role of the mobus
telegram check sum (CRC16) is assumed by the TCP safety layer. The INTECONT® Satus
only uses the sixth byte of the 6-byte telegram header defined in the OPEN MODBUS
standard to transmit the data length. All other bytes are sent back 1:1 in the reply.
These header bytes (1-5) should not be used to enable subsequent expansion, they should
be set to ZERO!
17.3 Modbus/TCP Ethernet
84 BV-H2346GB / 0833 Operating Manual INTECONT® Satus
© Schenck Process
To Next Page
Loading...
Need help?
General
