IntesisBox
®
BACnet/IP Server - Modbus TCP Master
User’s Manual r1 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
5 / 27
1. Description
1.1 Introduction
This document describes the integration of Modbus TCP systems with BACnet ASHRAE 135 –
2001 Annex J - BACnet protocol compatible devices or systems using the gateway
IntesisBox BACnet/IP Server - Modbus TCP Master.
This document assumes that the user is familiar with Modbus TCP and BACnet/IP technology
and technical terms.
From now on, and with the aim of easy the read of this document, the words "gateway" or
“IntesisBox” are used instead of IntesisBox BACnet/IP Server - Modbus TCP Master. Any
other use of the word "gateway" not meaning IntesisBox BACnet/IP Server - Modbus TCP
Master will be specifically indicated.
The aim of this integration is to make accessible Modbus TCP system signals and resources
from a BACnet/IP based control system or device, as if it was a part of the own BACnet
system and vice-versa. For this, the gateway acts as a BACnet/IP Server device in its
BACnet interface, allowing other BACnet/IP devices to perform subscription (COV) requests,
and also read and write its internal points. From the Modbus TCP system point of view,
IntesisBox simulates a Modbus master device, the readings of the Modbus TCP slave
device(s) is performed by IntesisBox by automatic continuous polling.
BACnet IP
client
Ethernet
IntesisBox
LinkBoxBacnet
configuration
software
Only needed for configuration
RS232
LAN
TCP/IP
BACnet IP
BACnet IP
client
Modbus
slave
Modbus
TCP
Modbus
slave
Figure 1.1
Integration of Modbus TCP and BACnet/IP using
IntesisBox BACnet/IP
Server - Modbus TCP Master
gateway
