CONTROL SOLUTIONS BB2-7030 User manual









User Guide

Babel Buster 2
Model BB2-7030
BACnet Gateway and Router
Rev. 1.0 – September 2010

BB2-7030 User Guide – Rev. 1.0 Page ii









User Guide

Babel Buster 2
Model BB2-7030
BACnet Gateway and Router
Rev. 1.0 – September 2010
IMPORTANT SAFETY CONSIDERATIONS:
Proper system design is required for reliable and safe operation of distributed control systems incorporating Babel Buster
series gateways and other such devices. It is extremely important for the user and system designer to consider the effects
of loss of power, loss of communications, and failure of components in the design of any monitoring or control
application. This is especially important where the potential for property damage, personal injury, or loss of life may
exist. By using the Babel Buster series gateway or any other Control Solutions, Inc., product, the user has agreed to
assume all risk and responsibility for proper system design as well as any consequence for improper system design.
© 2010 Control Solutions, Inc.
BACnet® is a registered trademark of American Society of Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE). Babel Buster® is a
registered trademark of Control Solutions, Inc., Minnesota, USA. All other trademarks mentioned in this document are the property of their respective
owners. Information in this document is subject to change without notice and does not represent a commitment on the part of Control Solutions, Inc.
This document is provided “as is,” without warranty of any kind, either expressed or implied, including, but not limited to, the implied warranties of
fitness or merchantability for a particular purpose. Control Solutions may make improvements and/or changes in this manual or in the product(s) and/or
the program(s) described in this manual at any time. This product could include technical inaccuracies or typographical errors. Changes are
periodically made to the information herein; these changes may be incorporated in new editions of the publication.

BB2-7030 User Guide – Rev. 1.0 Page iii
Contents
1. Introduction ..................................................................................................................................................... 1
2. Connecting the BB2-7030 for the First Time.................................................................................................. 3
3. Minimum BB2-7030 Gateway/Router Setup .................................................................................................. 6
4. Using the BB2-7030 as a BACnet Router....................................................................................................... 9
5. Using the BB2-7030 as a BACnet Server ..................................................................................................... 12
6. Using the BB2-7030 as a BACnet Client ...................................................................................................... 16
7. Using the BB2-7030 as an MS/TP to BACnet IP gateway ........................................................................... 25
8. Configuring the BB2-7030-01 as a Modbus TCP Server.............................................................................. 26
9. Configuring the BB2-7030-01 as a Modbus TCP Client............................................................................... 30
10. Using the BB2-7030-01 as a BACnet to Modbus TCP Gateway................................................................ 39
11. Using the BB2-7030-02 as an SNMP Server (Agent)................................................................................. 40
12. Using the BB2-7030-02 as an SNMP Client (Manager) ............................................................................. 44
13. Using the BB2-7030-02 as a BACnet to SNMP Gateway .......................................................................... 52
14. Using the BB2-7030 Proxy Support............................................................................................................ 53
15. Using the BB2-7030 BBMD Support and WAN Routing...........................................................................55
16. Miscellaneous System Setup ....................................................................................................................... 60
17. Hardware Guide........................................................................................................................................... 62
18. Trouble Shooting......................................................................................................................................... 64
19. BACnet Object Properties ........................................................................................................................... 65
19.1Data Object Properties (Analog, Binary, Multi-state)....................................................................... 65
19.2Device Object Properties................................................................................................................... 66
20. Modbus Slave Register Mapping ................................................................................................................ 68
20.1Using the BB2-7030 as a Modbus TCP Slave................................................................................... 68
20.2Modbus Registers Accessible with BB2-7030 as a Slave ................................................................. 68
20.3Modbus Function Codes Recognized by BB2-7030 .........................................................................69


History:
Rev 1.0 – Initial release

BB2-7030 User Guide – Rev. 1.0 Page 1
1.Introduction
The Babel Buster BB2-7030 is a BACnet gateway and router. It may be used as either or both, in
various ways for different applications. In its simplest form as a router, it will route a single
MS/TP network to a single BACnet IP network. It may be used as a router to interconnect
multiple BACnet MS/TP via IP networks. It may even be used to traverse NAT routers on a
WAN connection to connect distant buildings via Internet.
The BB2-7030 includes proxy support such that devices that do not support dynamic binding
(Who-Is, I-Am) can be represented by proxy by the BB2-7030. The BB2-7030 will act as proxy
for both MS/TP and BACnet IP devices.
The BB2-7030 may be used as a transparent MS/TP to BACnet IP router, or as an object server
gateway where the BB2-7030 autonomously polls devices, stores the present value of a given set
of objects, and allows other BACnet devices to query the BB2-7030 to obtain that data. Going
the other direction, the BB2-7030 will act as a store and forward device for writing to BACnet
devices.
Here is an example of the gateway functionality solving a problem: A BACnet IP front end
periodically writes values to objects in MS/TP devices. The front end will periodically write
regardless of whether data values have changed. The MS/TP device, on the other hand, does not
want to receive updates unless the data value has changed. A transparent BACnet IP to MS/TP
router will not solve this problem. But a properly configured BB2-7030 gateway will solve this
problem by receiving all writes from the front end, and only forwarding them via MS/TP when
the data value has changed at all or by a user-specified margin. The BACnet Client portion of the
BB2-7030 is used to accomplish this.

BB2-7030 User Guide – Rev. 1.0 Page 2
The BB2-7030 may also be used as a gateway to connect BACnet MS/TP or BACnet IP to either
Modbus TCP or SNMP. There are two variations of the BB2-7030.
The BB2-7030-01 may be used as a gateway to connect BACnet MS/TP or BACnet IP to
Modbus TCP. The connection of BACnet IP to Modbus TCP is also accomplished by the BB2-
7010-01, but only the BB2-7030-01 can connect BACnet MS/TP to Modbus TCP.
The BB2-7030-02 may be used as a gateway to connect BACnet MS/TP or BACnet IP to SNMP.
The SNMP side may be an SNMP Agent (server) or SNMP Client. The connection of BACnet IP
to SNMP is also accomplished by the BB2-7010-02, but only the BB2-7030-02 can connect
BACnet MS/TP to SNMP. The BB2-7030-02 supports generation of traps based on present value
of local objects in the BB2-7030. The data found in the local objects is placed there by the
BACnet client, or written by other BACnet devices.

BB2-7030 User Guide – Rev. 1.0 Page 3
2.ConnectingtheBB27030fortheFirstTime
(a) Connect power. Apply +12 to +24VDC or 24VAC to the terminal marked “POWER”, and
common or ground the the terminal marked “GND”.
(b) Connect a CAT5 cable between the RJ-45 jack on the top and your network switch or hub.
You cannot connect directly to your PC unless you use a “crossover” cable.
(c) Apply power. A blue LED inside the case should light indicating power is present. If the
yellow LED on the RJ45 jack is not on, check your Ethernet cable connections. Both green and
yellow LEDs on the RJ45 jack will be on solid for a time during boot-up. The entire bootup
process will take 1-2 minutes, during which time you will not be able to connect with a browser.
(d) The default IP address as shipped is 10.0.0.101. If your PC is not already on the 10.0.0.0
domain, you will need to add a route on your PC. Do this by opening a command prompt. First
type “ipconfig” and note the IP address listed. This is your PC’s IP address. Now type the
command
route add 10.0.0.0 mask 255.255.255.0 1.2.3.4
but substitute your PC’s IP address for 1.2.3.4.
This generally works, but if this fails, you will need to temporarily change your computer’s IP
address to a fixed address that starts with 10.0.0. and ends with anything but 101.

BB2-7030 User Guide – Rev. 1.0 Page 4
(e) Open your browser, and enter “http://10.0.0.101/” in the address window. You should see a
page with the “Babel Buster BB2-7030” header shown above. From this point, you will find help
on each page in the web site contained within the product.
(f) When you click on any of the page tabs such as System Setup, you will be asked for a user
name and password. The default login is user name “system” with password “admin”. You can
also log in as “root” using password “buster”. You should log in as “root” if you will be
changing the IP address.
(g) To can change the IP address of the BB2-7030, go to the Local Host page under System ::
Setup. The following page should appear. Change the IP address, and subnet mask and gateway
if applicable. Click Change IP to save the changes. The process of programming this into Flash
takes around half a minute. The new IP address only takes effect following the next system
restart or power cycle.

BB2-7030 User Guide – Rev. 1.0 Page 5
(h) Most changes are stored in an XML configuration file in the device’s Flash file system. Only
a few are stored differently, and the IP address is one of those. Normally, clicking Update on any
configuration page only stores that configuration information to a temporary RAM copy of the
configuration file. To make your changes other than IP address permanent, you must click Save
on the Config File page (System :: Setup :: Config File).

BB2-7030 User Guide – Rev. 1.0 Page 6
3.MinimumBB27030Gateway/RouterSetup
The BB2-7030 requires only minimal configuration to be useful in its simplest form. First, you
must assign a device instance to the BB2-7030, and you do this via the BACnet IP Port page.
You may leave all other settings at their default. You could leave the device instance at its
default as well. The only real requirement is that you do not duplicate device instances.
The hardware will effectively prevent you from duplicating the MAC address on the IP side, but
you do need to select a MAC address for the MS/TP side of the router. Enter that MAC address
at the bottom of this page. The MAC addresses must not be duplicated on the network. Enter
your MS/TP baud rate and Max Master setting as well.
The second page that contains a minimum requirement is the Network Info page, under the
BACnet Router tab. The network info strings are just that, information only, and are optional.
The network numbers, however, are mandatory.

BB2-7030 User Guide – Rev. 1.0 Page 7
●Network numbers MUST NOT be duplicated anywhere else on the network. Duplicated
network numbers on two or more routers will result in erratic operation of the network that can
be difficult to diagnose. Duplicated network numbers means two physically disconnected
networks have been assigned the same network number.
●The IP and MS/TP network numbers MUST be different.
●Two routers connected to the same physical network segment or link MUST use exactly the
same network numbers to refer to that segment of the network. Using two different network
numbers to refer to the same physical network will result in erratic behavior that is difficult to
diagnose. Using the same network number in two routers does not constitute a duplicated
network number, provided those identically numbered ports are physically electrically connected
to each other if MS/TP, or physically connected via a local switch or hub if IP.
●IP networks connected by BB2-7030’s that are connected to each other via a WAN router
MUST be given different network numbers – they are considered physically independent
networks.
If your requirement is simply connecting MS/TP devices to a BACnet IP network, the only
configuration you need to do is contained within the two screens shown above. If there are no
other networks and no other routers involved, you may pick any two arbitrary numbers you like
for network numbers.
The last item that should be configured on the above page is Hop Count. If you are only
connecting MS/TP to BACnet IP locally, set that count to at most 2 since you will not need to
make any additional router hops. If there are additional routers in your system, the hop count
needs to be the maximum number of routers that a message must hop to reach the final
destination. The hop count is decremented once each time it is forwarded.

BB2-7030 User Guide – Rev. 1.0 Page 8
The primary use of hop count is to force packets on the network to be discarded faster,
particularly in the event of router misconfiguration that results in a continuous loop.

BB2-7030 User Guide – Rev. 1.0 Page 9
4.UsingtheBB27030asaBACnetRouter
You do not actually need to do more than the minimum configuration mentioned above. If the
BACnet Router :: Remote Networks :: Configured page is left blank, the BB2-7030 will use
Who-Is-Router messages to “learn” the network. You have the option of pre-configuring the
router. This will save a little bit of time when the router first boots up, but will normally not
impact performance overall.
Enter the known remote network numbers and the ports via which they may be reached. The Info
strings are strictly informational and have no bearing on functionality.
The router's address is optional. If not given here, it will be searched for on the network using
Who-Is-Router. You may enter the remote router's address as an MS/TP MAC address, or an
IP address optionally with port number. If no port number is given, the BB2-7030's own local
port number will be used. IP should be given in the form of 192.168.1.199:47808 (for example)
or just 192.168.1.199.
It should be noted that even if you do enter the router's address here, it will be replaced in the
event an I-Am-Router message is received for the given network number but having a different
router address.

BB2-7030 User Guide – Rev. 1.0 Page 10
It should also be noted that if some external BACnet network management tool sends a router
table initialize message to this device, the entire page shown here will be replaced. After a delay
of a few minutes, the new contents of this page will be auto-saved to the XML configuration file
for subsequent reload. Thus, the router portion of this BB2-7030 may be remotely managed.
If you leave this page completely empty, all routers needed for routing of traffic will be located
using the Who-Is-Router broadcast to the network. Routers that are found this way, in addition to
any listed here, will be listed on the Discovered page illustrated below.
Use the Prev/Next buttons to scroll through the list of known networks. This list is a combination
of configured networks and those discovered via the Who-Is-Router and I-Am-Router message
exchange.
An example of a string of routers is illustrated below. This configuration is one of numerous test
scenarios that the BB2-7030 has been tested on. It represents a possible application, but would
represent a poorly configured network. There would normally be no reason to route alternately
between MS/TP and IP numerous times. The IP should be connected in a star configuration for
better performance. However, traffic does reach one end point from the other.

BB2-7030 User Guide – Rev. 1.0 Page 11
The networks listed as “Connected” in the diagram are the locally connected network numbers.
The remaining networks are router table entries. Each entry tells the local router which network
the given net number will be found on.

BB2-7030 User Guide – Rev. 1.0 Page 12
5.UsingtheBB27030asaBACnetServer
The BB2-7030 contains a set of BACnet objects whose only purpose is to store copies of data
obtained from other devices. This copy of data may then be queried by different devices, or
written to different devices by the BB2-7030 client functions.
The collection of objects includes Analog, Binary, and Multi-State types of objects, and includes
Input, (commandable) Output, and (writeable) Value types of each of those objects. The BB2-
7030 also contains a Device object which is shared with router functions. All of the remaining
objects noted here are not used by routing functions.
The BB2-7030 is a BACnet router, and routes packets as defined for routing by the BACnet
protocol specification. The BB2-7030 is also a gateway and can perform certain gateway
functions regardless of whether being used for routing purposes. The gateway functions all rely
upon the input, output, and value objects that store copies of data from devices.
Data may be placed in the local objects by other devices writing to the BB2-7030, or by the
BB2-7030 querying other devices. When the BB2-7030 is configured to query other devices,
these operations are defined by “read maps” and “write maps” associated with the respective
client function (e.g. BACnet client, Modbus TCP client, SNMP client).
The following pages illustrate the Analog Input object page and the Analog Output object page.
The remaining object pages found in the BB2-7030 are virtually identical, and are not replicated
here.

BB2-7030 User Guide – Rev. 1.0 Page 13
The source of data for an Analog Input object will be reading an object in another BACnet
device, or receiving of data from a Modbus (or SNMP) device. The device link will point to a
BACnet client read map or a Modbus (or SNMP) client read map.
Out of Service means any polling of the slave device will stop. While out of service, the present
value may be written by the BACnet client. Data may be forced via this web page at any time,
but will be overwritten by the next poll unless the object is out of service.
Reliability codes may be any of the following (7030-01):
64: Modbus client, no response
65: Modbus client, crc error
66: Modbus exception, illegal function code
67: Modbus exception, illegal data address
68: Modbus exception, illegal data value
69-79: Modbus exception, code+65, rarely used
80: Local device, configuration property fault
81: Faulty Modbus packet
82: BACnet IP client, device timeout
83: BACnet IP client, error returned by server
Reliability codes may be any of the following (7030-02):
80: Local device, configuration property fault

BB2-7030 User Guide – Rev. 1.0 Page 14
81: Faulty packet
82: BACnet IP client, device timeout
83: BACnet IP client, error returned by server
84: SNMP client, no response from agent
85: SNMP client, unable to parse data
86: SNMP client, reply does not match request
Status flags A,B,C,D indicate the following, 0 meaning not true, 1 meaning true:
A = in alarm
B = fault
C = overridden
D = out of service
Device link will indicate BAC or TCP, followed by R for read or W for write, and a number
which is the rule number in the table of read or write rules for mapping external devices or
objects to this BACnet object. The designation R means read from external device, and W means
write to external device.
The destination of data for an Analog Output object will be writing to another BACnet device, or
to a Modbus device. The external device will be updated upon change of source data and/or
periodically as defined by the Write Map.

BB2-7030 User Guide – Rev. 1.0 Page 15
The Analog Output object is commandable, meaning the BACnet client must write both a value
and a priority level for that value. The highest level value will be the one written to the external
device. If all values are relinquished, the relinquish default value will be written to the external
device.
To set an output object manually from this page, check the Force box, enter a value in the
Present Value window, and select a priority level to assign to your forced value. Then click
Update. To return a given priority level to NULL, simply type the word NULL in the Present
Value window, check Force, and click Update.
Out of service means the external device will not be written. Values written by the BACnet client
will be retained, but only applied when this object is placed back in service. At that time, the
highest priority value will be written to the external device.
Reliability codes may be any of the following (7030-01):
64: Modbus client, no response
65: Modbus client, crc error
66: Modbus exception, illegal function code
67: Modbus exception, illegal data address
68: Modbus exception, illegal data value
69-79: Modbus exception, code+65, rarely used
80: Local device, configuration property fault
81: Faulty Modbus packet
82: BACnet IP client, device timeout
83: BACnet IP client, error returned by server
Reliability codes may be any of the following (7030-02):
80: Local device, configuration property fault
81: Faulty packet
82: BACnet IP client, device timeout
83: BACnet IP client, error returned by server
84: SNMP client, no response from agent
85: SNMP client, unable to parse data
86: SNMP client, reply does not match request
Status flags A,B,C,D indicate the following, 0 meaning not true, 1 meaning true:
A = in alarm
B = fault
C = overridden
D = out of service
Device link will indicate BAC or TCP (or SNMP), followed by R for read or W for write, and a
number which is the rule number in the table of read or write rules for mapping external devices
or objects to this BACnet object. The designation R means read from external device, and W
means write to external device.

BB2-7030 User Guide – Rev. 1.0 Page 16
6.UsingtheBB27030asaBACnetClient
The BACnet client is used to query other BACnet devices, obtain their Present Value data, and
store a copy of that data in the BB2-7030’s own local objects. From there, the data may be
accessed by Modbus TCP or SNMP devices, or other BACnet devices when application specific
reasons make this approach more preferred than direct routing.
Setting up the BACnet client consists of identifying one or more BACnet devices, then listing the
objects that should be queried (whether read or written). The client configuration pages are
illustrated below.
Device number simply shows you where you are on the device list. Click "next" and "prev" to
scroll through the list.
Remote BACnet devices to be accessed by this device are specified here. Enter the
Device Instance of the remote device, a name to reference in other pages, a poll rate, default
reply timeout, and default write priority. Enter static address if applicable. Then click "update".
The gateway broadcasts a "who-is" looking for this device when a read or write map wants to use
this device. When (if) it responds, its IP address or MS/TP mac address is listed here simply as a
diagnostic. Timeouts resulting from inability to reach this device are tabulated on this page as
well, and may be cleared by clicking the Clear button. To cause the who-is process to be
repeated, click Clear Cache.
BACnet IP or MS/TP slave devices that to not support Who-Is/I-Am can still be supported here.
When this is the case, enter the slave device's Mac address in the Static Mac window and check

BB2-7030 User Guide – Rev. 1.0 Page 17
the 'No Who-Is' box. If located on a remote network via a router, enter the network number as
DNet. This static entry effectively replies to the implied Who-Is.
To use a fixed static address, enter a single number for MS/TP MAC address. or an IP address
optionally including port number. An example of IP address with port number would be
192.168.1.99:47808. The 47808 is the port number, and is separated from the IP address by a
colon. Note that 47808 is the default 0xBAC0 port number. If no port number is given, the port
configured on the BACnet IP Port page will be used (the BB2-7030's own port).
Map number simply tells you where you're at on the list of register maps. Click "next" and
"prev" to scroll through the list. To advance directly to a specific map, enter the desired number
in the "Showing" box, then click Update.
Maps entered on this page only read data from remote devices. Go to the Client Write Map to
write data to those devices. The full parameter set is different for read versus write.
An abbreviated version of a list of maps is shown on this page. Any of the parameters shown
may be changed here and registered by clicking the Update button. To view and/or modify the
complete set of parameters, click on the map number in the left most column.
For each remote object to be read, enter the object instance and type, and location (device). The
names in the device list are defined in the Devices page.
When the remote object is read, data may be manipulated before being written to the local object.
The value will be multiplied by the scale factor. The final result is written to the local object
number given. The name is optional and used only for display purposes.
Selecting "none" for remote type effectively deletes the map even though it will still appear in
the list until deleted. Unused maps at the end of the list will always show none as the type.