Babel Buster BB2-7010 Modbus to BACnet IP Gateway
$749.00
The Babel Buster BB2-7010 Modbus to BACnet IP gateway allows Modbus devices to communicate with BACnet IP devices. (This model is now out of production.)
Out of stock
Overview
The Babel Buster BB2-7010 Modbus to BACnet IP gateway allows Modbus devices to communicate with BACnet IP devices. BACnet objects may be read as Modbus registers, and Modbus registers may be read as BACnet objects. The Modbus to BACnet IP gateway acts as a translator between the two protocols.
The Modbus to BACnet IP gateway may be both Modbus TCP client and server at the same time, and can be configured to also be a Modbus RTU master or slave that runs independently of Modbus TCP. The BB2-7010 will continuously poll Modbus registers in TCP or RTU devices and make that data accessible as BACnet objects. Configured to go the other way, the BB2-7010 will continuously poll objects in other BACnet devices and make that data accessible as Modbus registers for other Modbus masters polling the BB2-7010.
An available variation of the BB2-7010 also includes an SNMP client and server that translates and shares data between BACnet IP and SNMP devices. The SNMP agent (server) also has the ability to send traps on threshold rules set by the user.
Feature Highlights
• Connect BACnet IP Devices to a Modbus RTU or TCP Network
• Subscribe to COV on Changes from Modbus or BACnet
• Up to 1000 BACnet Objects and 1000 Modbus Holding Registers
• BACnet Input, Value, Output objects for Analog, Binary, Multistate
• Optional mapping of Modbus Registers as Coil, Discrete, Input, Holding
• Optional SNMP client and server, includes trap send on threshold
• FCC, CE Mark, UL 916 Listed
• Software Included, No Drivers to Buy
Description
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.
Specifications
• 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
• Standard hardened EIA-485 transceiver for Modbus RTU
• Optional isolated 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% non-condensing
• 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
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