Deployment
Wieland Electric GmbH | BA001269 | 09/2021 (Rev. A)
50
6.7
ricos FLEX BC MODBUS: Replacing an old device with a new device
The Modbus/TCP Ethernet coupler
ricos
FLEX BC MODBUS 83.036.1040.0 is compatible with the
83.036.1040.1 if the configuration of the 83.036.1040.0 is not imported.
Since the product name is evaluated within the configuration file during import, inappropriate con-
figurations are rejected and not adopted. For the import of a configuration file this can be adapted
accordingly:
Open the configuration file to be imported in a text editor.
Search for the entry
product='Wieland BC Modbus'
.
Change the entry to
product='Wieland BC Modbus'
.
Save the configuration file and load it into your
ricos
FLEX BC MODBUS by means of the web
page.
The configuration is applied and the
ricos
FLEX BC MODBUS is restarted.
6.8
Modbus/TCP
General data
Modbus/TCP is a Modbus protocol put upon TCP/IP, where the IP address serves the addressing.
Modbus/TCP allows a client-server-communication, several clients may be provided from one
server.
Telegram structure incl. TCP/IP
The request telegrams sent by a master and the respond telegrams of the slave have the same struc-
ture:
Modbus/TCP
Slave
address
Function code
Data
6 byte header with number of following bytes 1 byte data 1 byte data
max. 254 byte
Modbus/TCP header (6 byte)
For send and receive telegrams, Modbus/TCP uses a header of 6 byte with the following structure:
Byte
Name
Description
0
Transaction identifier (High-Byte) Is sent back by the server (user-defined)
1
Transaction identifier (Low-Byte) Is sent back by the server (user-defined)
2
Protocol identifier (High-Byte)
Always 0
3
Protocol identifier (Low-Byte)
Always 0
4
Length field (High-Byte)
Always 0 because messages < 256 byte
5
Length field (Low-Byte)
Number of following bytes
Normally, byte 0 ... 4 have the value 0. You may also increase byte 0 and 1 in the slave and thus es-
tablish an additional control.
NOTICE
