Control Solutions’ Babel Buster® BB2-7010 is a BACnet IP to Modbus gateway that functions as a BACnet IP client or server, and Modbus master or slave. The purpose of the BB2-7010 is to connect Modbus devices to a BACnet IP network.
• Connect Modbus to BACnet IP
• BACnet IP client or server
• Modbus RTU master or slave
• Modbus TCP client and server
• SNMP v2c client and server
• Universal, fully configurable
• No extra software or drivers to buy
• Configured via internal web server
Babel Buster 2 Network Gateways
More Power. More Capacity.
More Features. Less Expensive.
No Drivers to Buy.
Easy to Configure Yourself.
Babel Buster BB2-7010 BACnet to Modbus Gateway
Order code: BB2-7010
List price: $699.00
Your price: $559.00
Log in for Wholesale
Modbus RTU is RS-485 on standard model. RS-232 is also available. Select the transceiver option when you place your order; price is the same.
BB2-7010 Base Model with Modbus Support
Babel Buster BB2-7010 BACnet IP to Modbus Gateway provides a BACnet IP client and server, Modbus TCP client and server, and Modbus RTU port configurable to be master or slave. Most often used to connect Modbus devices to a BACnet IP network, the BB2-7010 is configured via simple web page templates to read and write Modbus registers in one or more Modbus slaves, making that data accessible as BACnet objects on the BACnet IP network.
The BB2-7010 includes a BACnet IP client which allows BACnet IP devices to be accessible from Modbus TCP or RTU. You configure the device instance, object type and instance, and poll interval for reading or writing BACnet objects. The object data is stored in the BB2-7010 server for subsequent retrieval by any supported remote client (or master). The same polling schemes that apply to Modbus also apply to remote BACnet IP slaves polled by the BB2-7010's BACnet IP client.
A large number of BACnet objects gives you flexibility in mapping Modbus registers to any combination of BACnet objects. Packed Modbus registers may be parsed to multiple BACnet objects when reading. Multiple BACnet objects may be packed into a single Modbus register when writing. All standard Modbus register types are supported.
Value objects will poll their assigned Modbus register at the interval you specify. The content of the Modbus register will be given as the Present Value of the BACnet object when read. The Modbus register is written each time the BACnet Value object is written. The Value object corresponds well with the Modbus Holding register.
Input objects will poll their assigned Modbus register at the interval you specify, and provide the Modbus data as the Present Value when read. Commandable Output objects are used to write Modbus registers, and will update the Modbus device each time BACnet is updated.
BB2-7010 with SNMP Support
The standard model BB2-7010-01 provides Modbus and BACnet IP clients and servers. The BB2-7010-02 adds an SNMP client and server. The combination of SNMP agent (server) and BACnet IP client makes BACnet IP devices accessible from SNMP. The SNMP client allows SNMP devices to be accessible from BACnet IP or Modbus. You configure the remote SNMP agent's IP address, the OID of the MIB variable you wish to poll, and set a polling interval. The object data is stored in the BB2-7010 server for subsequent retrieval by any supported remote client.
The BB2-7010 includes its own internal web server that provides a web based user interface for configuring the BB2-7010. Configuration is done using simple templates, and each web page has an online help section at the bottom.
Click on any of the links below to view a demo copy of the entire Web UI in the BB2-7010.
BB2-7010 Models with WiFi Sensor Support
Babel Buster BB2-7010 models for WiFi sensors are extensions of the BB2-7010 family that add support for third party WiFi products. These versions of the BB2-7010 receive UDP and/or TCP data packets from sensors via a generic off-the-shelf WiFi access point, parse the data packet, and place the sensor data in one or more BACnet objects. The sensor data objects may be accessed via BACnet IP, Modbus TCP, Modbus RTU, or SNMP. All of the standard features found in the BB2-7010-02 are available in the WiFi support versions of BB2-7010. In most cases, the spontaneous transmit rate of the sensor is set in the configuring of the sensor, and the gateway will operate in "listen mode". Where applicable, the poll rate is configured via templates in the BB2-7010, and the gateway will poll the sensor at that rate.
The WiFi sensor server is easily configured by simply entering information about the sensor's identity, and assigning BACnet objects that are to receive the sensor data. Data received from sensors is automatically scaled by the gateway so that standard engineering units are presented on the BACnet or Modbus networks. When using BACnet, COV subscriptions may also be used to send changes in data values.
Babel Buster BB2-7010-06 is an extension of the BB2-7010 family that adds support for PointSix and AirTest Technologies WiFi sensors. The sensor types available include temperature with various sensor technologies, humidity, CO2, pressure, pulse count, generic voltage (0-10V) and current (0-20mA).
The BB2-7010-06 also includes support for the alarm capabilities of the PointSix sensors. High and low alarm thresholds, alarm time, and hysteresis may all be entered via the gateway. Alarm thresholds may be a fixed configuration setting, or may be provided by additional BACnet Analog Value objects (also accessible as Modbus registers). Alarm states may be assigned to BACnet Binary Value objects with COV subscriptions providing notice of alarm state changes. The alarm states may also be configured to generate SNMP traps, or may be read as Modbus registers.
Babel Buster BB2-7010-07 is an extension of the BB2-7010 family that adds support for Veris Industries WiFi sensors. The BB2-7010-07 accepts either UDP or TCP data from the Veris sensors. The sensor types available include temperature with various sensor technologies, humidity, CO2. Refer to the Veris Industries web site for the most recent sensor listing.
Babel Buster BB2-7010-08 is an extension of the BB2-7010 family that adds support for Functional Devices WiFi RIB relays/sensors. The RIB universal inputs support 0-5V, 0-10V, 4-20mA, and thermistor. Additional user configured scaling is provided (optionally) by the gateway. The universal inputs can also be configured as state (on/off) inputs. The universal inputs, in addition to fixed discrete input, can be assigned to any of the gateway’s BACnet objects.
The relay in the RIB can be controlled by a BACnet Binary Output object in the gateway. The gateway also provides binding between a discrete input on one RIB to the relay output on a different RIB if configured by the user.
The BB2-7010-08 will query WiFi sensor data and command the relay output at whatever poll rate is configured by the user via the web pages available in the BB2-7010-08. The BB2-7010-08 can also be configured to send the sensor data to other Modbus slaves or BACnet IP servers, or retrieve relay output state from another device.
• Read/Write any standard Modbus register via BACnet
• Read/Write any standard BACnet object via Modbus
• Support for up to 200 WiFi Sensors (specific models)
• Bidirectional communication between BACnet and Modbus
• Supports Modbus coils, input registers, holding registers
• Single or double Modbus registers
• Signed, unsigned, IEEE 754 Modbus registers
• Supports Mod-10 format (2, 3, 4-register)
• Modbus register mapping configured via web interface
• Modbus registers may be scaled (x10, x0.1, etc.)
• Modbus (master) polling interval configurable per point
• Commandable BACnet objects implement priority array
• Hardened EIA-485 transceiver for Modbus RTU
• Optional RS-232 transceiver (in place of RS-485)
• 10/100BaseT Ethernet for BACnet IP and Modbus TCP
• Powered by 10-30VDC or 12-24VAC 50/60 Hz
• Power Consumption: 0.3A @ 24VDC
• DIN rail mounting, 100mm H x 70mm W x 60mm D
• Pluggable screw terminal block for power & RTU network
• Operating temperature -40°C to +85°C
• Humidity 5% to 90%
• FCC Class A, CE Mark
• Listed to UL 916 and (Canadian) C22.2 No. 205-M1983
Maximum Object Counts and System Capacities for BB2-7010
BB2-7010-01: Pool of 1000 objects
BB2-7010-02: Pool of 500 objects
BB2-7010-06: Pool of 500 objects
BB2-7010-07: Pool of 500 objects
BB2-7010-08: Pool of 500 objects
The object pool may be allocated among the following object types, with a minimum of 1 per object type: Analog Input, Analog Output, Analog Value, Binary Input, Binary Output, Binary Value, Multi-state Input, Multi-state Output, Multi-state Value.
• Maximum 250 Binary objects with state text
• Maximum 1024 states for Multi-state objects with state text, actual number of objects/states supported varies by resource usage per object.
Useful object counts may be further limited by configuration file size which varies with use of character strings for object names, descriptions, and state text. MIB walk is limited to approximately 300 to 400 objects.
Additional maximum counts:
• Maximum BACnet IP device count 50
• BACnet IP Client read rule count 1000
• BACnet IP Client write rule count 1000
• COV Subscription capacity 1000
• Maximum Modbus RTU device count 240
• Modbus RTU read rule count 1000
• Modbus RTU write rule count 1000
• Maximum Modbus TCP device count 50
• Modbus TCP Client read rule count 1000
• Modbus TCP Client write rule count 1000
• WiFi Sensor count: 200
BB2-7010 Video Library
Watch these videos for an introduction to configuring the gateway. It's easier than reading!
Our most extensive technical support is provided by the same engineering staff that developed the products. Your personal attention from this staff is available via the support ticket system.
No user/password is required to open a new ticket. Once you open a ticket, you will immediately receive an email with your ticket number. Your ticket number becomes your login to review your ticket(s) later. Click the Support Ticket icon anywhere you see it. (If you do not get an email with your ticket number, within minutes, check your junk folder, spam settings, etc, and try again if necessary.)Open a Ticket