IntesisBox
®
BACnet/IP Server - Modbus RTU Master
User’s Manual r14 eng
© Intesis Software S.L. - All rights reserved
This information is subject to change without notice
IntesisBox
®
is a registered trademark of Intesis Software SL
URL
Email
tel
http://www.intesis.com
[email protected]
+34 938047134
9 / 27
RS232 (for single slave integration).
Modbus slave devices are normally characterised by their communication parameters (baud
rate, data bits, parity), some of them sometimes configurable depending on the device, and
their predefined
registers address map
, this address map specifies the address, type and
characteristics of every internal point (commonly called
register
) of the Modbus slave
device, these registers being accessible using Modbus RTU protocol.
Communication parameters of IntesisBox's Modbus interface (baud rate, data bits, stop bits,
parity) are fully configurable to adapt to any slave device. Of course IntesisBox and all the
slave devices connected to the Modbus network must use the same communication
parameters.
Modbus RTU protocol defines different types of function codes to use to read/write different
type of registers that can be found in Modbus devices, and also different data formats to
encode values. All these are explained in section 5.1.2
Also the data encoding used for 16 bits registers (big-endian or little-endian) can be
configured in IntesisBox's Modbus interface. This is the byte order for data encoding
(MSB..LSB or LSB..MSB). This data encoding, although is specified as big-endian in Modbus
protocol specification, it varies depending on manufacturer/type of slave device.
All this gives great flexibility to integrate a wide range of Modbus slave devices that can be
found in the market.
