Babel Buster MX-71-SP Proprietary Serial to BACnet IP Gateway

        Babel Buster MX-71-SP Proprietary Serial to BACnet IP Gateway

        Control Solutions’ Babel Buster® MX-71-SP is a specialized BACnet IP Gateway used to connect devices with proprietary serial communication protocols to your BACnet network. 

        • $549.00

        Control Solutions’ Babel Buster MX-71-SP is a specialized BACnet IP Gateway used to connect devices with proprietary serial communication protocols to your BACnet network. The Script Basic programming environment lets you write your own custom protocol interpreter to interact with your serial device, and share data with BACnet objects in the gateway.

        The MX-71-SP also includes a Modbus TCP client and server. Therefore, this gateway can also be used to connect devices with proprietary serial protocols to Modbus TCP, or use it as a gateway to connect Modbus TCP devices to BACnet IP while also connecting the proprietary serial devices.

        Feature Highlights
        • Connect Proprietary Serial Protocol Devices to BACnet IP
        • Script Basic programming for custom serial protocols
        • User HTML support for adding custom web pages
        • Subscribe to COV on Changes to BACnet Objects
        • At least 1,000 BACnet Objects Typical
        • BACnet Input, Value, Output objects for Analog, Binary, Multistate
        • Optional mapping of Modbus Registers as Coil, Discrete, Input, Holding
        • FCC, CE Mark
        • Software Included, No Drivers to Buy

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

        Babel Buster MX-71-SP 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 MX-71-SP 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 MX-71-SP 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 MX-71-SP 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 MX-71-SP’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.

        The MX-71-SP is a special version of the MX-71-RTU that allows one to repurpose the serial communication port to be used for a proprietary serial protocol instead of Modbus RTU. When used for interpreting a proprietary protocol, a Script Basic program would be written to send and receive via the serial port as applicable, and interact with the local BACnet objects under user program control.

        The MX-71-SP allows you to BACnet enable enable serial devices that otherwise have no network connection. Combined with rule templates, Script Basic can generate BACnet COV notifications. Script Basic also has access to TCP and UDP connections, and can potentially interpret proprietary IP protocols as well.

        Script Basic can program your MX-71-SP to be a passive listener capturing data from something like a data logger. Script Basic can also program your MX-71-SP to be an active polling device to query your serial device and interpret the response to provide data to BACnet (or Modbus TCP).

        Configuration of theMX-71-SP gateway is done via the web pages served by the internal web server. You simply fill in templates. The entire configuration is saved in the internal Flash file system in XML format. This file may be exported to replicate additional copies of the configured device, or for backup.

        • Connect Proprietary Serial Protocol Devices to BACnet IP
        • Script Basic programming for custom serial protocols
        • BACnet IP includes BBMD
        • Read/Write any standard Modbus register via BACnet objects
        • Typically at least 1,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/Serial Comm
        • 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
        • Panel mount, 70mm H x 131mm W x 38mm D
        • Pluggable screw terminal block for power & RTU network
        • Operating temperature -20°C to +75°C
        • Humidity 5% to 90% non-condensing
        • FCC Class A, CE Mark

        Maximum Object Counts and System Capacities for MX-71-SP

        • The standard MX-71 Object Pool allows up to 5,000 BACnet objects. The MX-71-SP gives up some of this capacity to support Script Basic, but you can anticipate typically at least 1,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.

        • MX-71-SP 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.

        • 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