BB2-7030 User Guide – Rev. 1.0
Page 39
10.
Using
the
BB2
7030
01
as
a
BACnet
to
Modbus
TCP
Gateway
The possible reasons for using the BB2-7030 as a BACnet to Modbus TCP gateway are fairly
obvious: Either you want to access BACnet devices from Modbus TCP, or you want to access
Modbus TCP devices from BACnet. The BB2-7030 allows you to access Modbus TCP from
either MS/TP or BACnet IP, and vice versa.
Configuration begins with determining what the source of data is. If the source of data is BACnet
devices, then start by configuring the BACnet client. If the source of data is Modbus TCP
devices, then start by configuring the Modbus client.
The BB2-7030 can be a “slave” on either the BACnet or Modbus network. If the application
wants to view BACnet data as if it was a Modbus slave, configure the BACnet client and then
review the Modbus register map for accessing the data objects in the BB2-7030. If the
application wants to view Modbus TCP data as if it was a BACnet slave, configure the Modbus
client and then address the BB2-7030’s internal data objects from BACnet.
The BB2-7030 can be “slave” on both BACnet and Modbus sides at the same time. The BB2-
7030 can also be “master” on both BACnet and Modbus sides at the same time. To be a slave on
both sides, no client functions need to be configured (no read/write maps entered). To be a
master on both sides, both the BACnet client and Modbus client need to be configured. When
both clients are configured and both sides are acting as master, you are now actively transferring
data from BACnet slaves to Modbus slaves or vice versa.