11. Modbus Interface
11.1. General Description
The Modbus protocol is an application-layer messaging protocol developed by Modicon in 1979. It is used to
establish master-slave/client-server communication between intelligent devices over different types of buses or
networks. The Intesis gateway supports Modbus TCP and RTU.
Modbus is a request/reply protocol and offers services specified by function codes. Modbus function codes are
elements of Modbus request/reply PDUs (Protocol Data Unit).
11.2. Modbus Server Interface
11.3. Description
The gateway acts as a server device in its Modbus interface, which can be:
• The Ethernet port for Modbus TCP.
• The EIA-485/EIA.232 ports for Modbus RTU.
NOTICE
Modbus RTU and TCP modes can be active in the gateway one at a time or both simultaneously.
To access the gateway's points and resources from a Modbus client device, you must specify as Modbus register
addresses those configured inside the gateway corresponding to the signals on the field device protocol.
11.4. Functions Supported
NOTICE
This part is common for both Modbus TCP and Modbus RTU.
Table 6. Modbus functions
#
Function
Read/Write
01
Read Coils
R
02
Read Discrete Inputs
R
03
Read Holding Registers
R
04
Read Input Registers
R
05
Write Single Coil
W
06
Write Single Register
W
15
Write Multiple Coils
W
16
Write Multiple Registers
W
If poll records are used to read or write more than one register, the range of addresses requested must contain
valid addresses; if not, the Intesis gateway will return the corresponding Modbus error code.
All registers are of 2 bytes, even if they are associated with signals of bit type on theKNX side. Its content is
expressed in MSB .. LSB.
1
Modbus error codes are fully supported. They are sent whenever a non-valid Modbus action or address is
required.
1
MSB: most significant bit; LSB: less significant bit
Modbus Interface
IN701-KNX Series
USER MANUAL Version 1.0
Page 15 of 44
