Supports signed, unsigned 16-bit, 32-bit, 64-bit integer Modbus registers.Supports Modbus coils, discrete inputs, input registers, holding registers.Bidirectional communication between BACnet and Modbus.Read/Write any standard BACnet object via Modbus.Analog, Binary, Multi-State object types.
Read/Write any standard Modbus register via BACnet objects.
Commandable Output objects are used to write Modbus registers, and will update the Modbus device each time BACnet is updated.
Input objects will poll their assigned Modbus register at the interval you specify, and provide the Modbus data as the Present Value when read. The Value object corresponds well with the Modbus Holding register. The Modbus register is written each time the BACnet Value object is written. The content of the Modbus register will be given as the Present Value of the BACnet object when read. Value objects will poll their assigned Modbus register at the interval you specify.
All standard Modbus register types are supported. Multiple BACnet objects may be packed into a single Modbus register when writing. Packed Modbus registers may be parsed to multiple BACnet objects when reading. The same polling schemes that apply to Modbus also apply to remote BACnet IP slaves polled by the MX-71-RTU's BACnet IP client.Ī large number of BACnet objects gives you flexibility in mapping Modbus registers to any combination of BACnet objects. The object data is stored in the MX-71-RTU server for subsequent retrieval by the remote Modbus client (or master). You configure the device instance, object type and instance, and poll interval for reading or writing BACnet objects. The MX-71-RTU includes a BACnet IP client which allows BACnet IP devices to be accessible from Modbus TCP or RTU. Most often used to connect Modbus devices to a BACnet IP network, the MX-71-RTU 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.
Up to 5,000 BACnet Objects and 5,000 Modbus Holding Registers.Subscribe to COV on Changes from Modbus or BACnet.Connect BACnet IP Devices to a Modbus RTU or TCP Network.Connect Modbus RTU or TCP Devices to a BACnet IP Network.Configured to go the other way, the MX-71-RTU will continuously poll objects in other BACnet devices and make that data accessible as Modbus registers for other Modbus masters polling the MX-71-RTU. The MX-71-RTU will continuously poll Modbus registers in TCP or RTU devices and make that data accessible as BACnet objects. 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 Modbus to BACnet IP gateway acts as a translator between the two protocols. BACnet objects may be read as Modbus registers, and Modbus registers may be read as BACnet objects. The Babel Buster MX-71-RTU Modbus to BACnet IP gateway allows Modbus devices to communicate with BACnet IP devices.