Modbus/Tcp Master Settings; Diagnosis And Troubleshooting - Schenck process Intecont Satus Operating Manual

Ethernet
Subscriber addresses
All stations in the ethernet network are explicitly identified by their IP addresses, so the
Modbus-slave address can always be set to 1.
Function codes (FC)
Identical to Modbus RTU
Securing transmission
The TCP layer safety measures guarantee transmission reliability for the Modbus/TCP.
Error codes
Identical to Modbus RTU
Data formats
Identical to Modbus RTU
Process values
Identical to Modbus RTU
Example telegrams
Example telegrams are described in the section: Examples of telegrams for MODBUS and
MODBUS/TCP.

17.3.3 Modbus/TCP master settings

If data from several segments is used (see Fieldbus Data), each segment requires at
n
least one telegram.
Setting the correct byte sequence with values in IEEE and LONG format.
n
The maximum permissible telegram length is 256 bytes, including header and trailer by-
n
tes.

17.3.4 Diagnosis and Troubleshooting

If one of the Fieldbusses has been activated (selected), every fault will be registered by the
''Communication Host' (S9) event message if this message has not been assigned the event
class IG(NORE). The message is visible in the display and in EasyServe. If you only have a
display available, please read the following section. The EasyServe tool can assist in
providing more information for error diagnosis.
Network Block LEDs
The network LEDs are described in the chapter 'Connecting the Device'.
INTECONT® Satus Operating Manual
© Schenck Process
BV-H2346GB / 0833
17.3 Modbus/TCP
85