
BACnet Server
– Modbus Client
User Manual r1.10 eng
© HMS Industrial Networks S.L.U - All rights reserved
This information is subject to change without notice
URL
http
s
://www.intesis.com
8 / 41
Functionality
From the Modbus system point of view, after the start up process, Intesis reads continuously the points configured
to be read in the Modbus TCP Server and/or Modbus RTU Slave devices and updates in its memory all the values
received from the Modbus system.
There are 2 available ports for Modbus RTU integration. When enabling this functionality in Intesis MAPS, each RS-
485 port (Port A and Port B) integrates up to 32 Modbus RTU devices (up to 64 devices in total) without the need of
additional repeaters to the network.
This functionality is disabled when BACnet MSTP is selected in Intesis MAPS, leaving only port A available for
Modbus RTU connectivity and port B for BACnet MSTP devices.
For more information about product ports and connections please see Section 6. Connections.
The default configuration is Port A: Modbus RTU and Port B: BACnet MSTP.
From the BACnet system point of view, after the start up process, the gateway listens for any subscription (COV)
request, serves any polling request, or performs any writing request of its internal points received from the BACnet
system. The values received from BACnet are immediately written in the associated register of the corresponding
Modbus TCP Server or Modbus RTU Slave device.
All the Modbus registers in the slave devices is associated to a
BACnet
object
, with this, all the Modbus system (all
the slave devices) is seen as
a single
BACnet
device with many objects
from the BACnet system point of view, each
object corresponding to a Modbus slave/register address.
When a new value is read from Modbus for a given register, the new value is updated in the gateway's memory and,
if this signal is associated to a BACnet active subscription then the new value will be sent to the subscripted BACnet
device(s).
In the continuous polling of the Modbus devices, if a non-response of the BACnet device is detected, the
corresponding virtual signal inside Intesis will be activated indicating communication error with the Modbus device.
These virtual signals indicating communication status in real time with the Modbus devices are also accessible from
BACnet, like the rest of the points of the gateway.
Gateway’s capacity
Intesis capacity is listed below:
Element
100
version
250
version
600
version
1200
version
3000
version
Notes
Type of BACnet
devices
IP / MSTP
Communication with BACnet IP
and MSTP
Number of BACnet
Objecs
100
250
600
1200
3000
Maximum number of points that
can be defined in the virtual
BACnet
device
inside
the
gateway
Number of BACnet
Subscriptions (COV)
requests
200
500
1200
2400
6000
Maximum number of BACnet
subscriptions (COV) requests
accepted by the gateway
Type of Modbus
slave devices
Modbus RTU (EIA485)
Modbus TCP
Those supporting Modbus
protocol
. Communication over
TCP/IP and RTU
Number of Modbus
Slave devices
Up to 5 Modbus TCP nodes/devices
Up to 255 Modbus RTU devices per TCP/RTU
node
Number of Modbus Slave
devices supported by the device