Babel Buster BB3-7101 Modbus to BACnet IP Gateway

        Babel Buster BB3-7101 Modbus to BACnet IP Gateway

        Control Solutions’  Babel Buster® BB3-7101 Modbus to BACnet IP gateway allows Modbus devices to communicate with BACnet IP devices. 

        • $739.00

        The Babel Buster BB3-7101 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 BB3-7101 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 BB3-7101 will continuously poll objects in other BACnet devices and make that data accessible as Modbus registers for other Modbus masters polling the BB3-7101.

        Feature Highlights
        • Connect Modbus RTU or TCP Devices to a BACnet IP Network
        • Connect BACnet IP Devices to a Modbus RTU or TCP Network
        • Subscribe to COV on Changes from Modbus or BACnet
        • Up to 5,000 BACnet Objects and 5,000 Modbus Holding Registers
        • BACnet Input, Value, Output objects for Analog, Binary, Multistate
        • Optional mapping of Modbus Registers as Coil, Discrete, Input, Holding
        • FCC, CE Mark, UL 916 Listed, BTL Certified
        • Software Included, No Drivers to Buy

        Full product information, data sheet, online user guide, tutorial videos, and more available by clicking here.

        Babel Buster BB3-7101 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 BB3-7101 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 BB3-7101 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 BB3-7101 server for subsequent retrieval by the remote Modbus client (or master). The same polling schemes that apply to Modbus also apply to remote BACnet IP slaves polled by the BB3-7101’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.

        • BACnet IP includes BBMD
        • Read/Write any standard Modbus register via BACnet objects
        • Up to 5,000 objects
        • Analog, Binary, Multi-State object types
        • Input, Output, Value objects
        • Read/Write any standard BACnet object via Modbus
        • Bidirectional communication between BACnet and Modbus
        • Supports Modbus coils, discrete inputs, input registers, holding registers
        • Supports signed, unsigned 16-bit, 32-bit, 64-bit integer Modbus registers
        • Supports IEEE 754 floating point (32-bit and 64-bit) Modbus registers
        • Supports Mod-10 format (2, 3, 4-register)
        • Modbus register mapping configured via secure 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
        • Configure via secure web pages with password protection
        • TLS 1.2
        • RSA-1024/SHA-256 self-generated certificates
        • Supports externally generated certificates
        • Flash file system with XML configuration files
        • Includes “10X” configuration file capacity
        • Powered by 10-30VDC or 24VAC 50/60 Hz
        • Power Consumption: 0.1A @ 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, BTL Certified
        • Listed to UL 916 and (Canadian) C22.2 No. 205-M1983

        Maximum Object Counts and System Capacities for BB3-7101

        • BB3-7101 Object Pool allows up to 5,000 BACnet 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 1024 states for Multi-state objects with state text, actual number of objects/states supported varies by resource usage per object.

        • BB3-7101 allows user allocation of memory resources. Memory capacity will not support maximum counts of everything possible, but maximum count limits are set high so that you can allocate resources where you need them. For example, you can have 5,000 BACnet objects and 5,000 read maps – but not 5,000 of each type of read map. Most applications will only use one type of read map anyway.

        • Maximum BACnet object count 5000
        • Maximum BACnet IP device count 200
        • BACnet IP Client read map count 5000
        • BACnet IP Client write map count 5000

        • Maximum Modbus RTU device count 240
        • Modbus RTU read map count 5000
        • Modbus RTU write map count 5000

        • Maximum Modbus TCP device count 200
        • Modbus TCP Client read mapcount 5000
        • Modbus TCP Client write map count 5000

        Footer navigation