Modbus ⇄ BACnet gateway

Expose your Modbus equipment in a BACnet BMS — with no intermediate PLC and no proprietary hardware.

The problem

A large share of technical equipment — energy meters, inverters, drives, PLCs, measurement units — only speaks Modbus (RTU over RS485 or TCP/IP). But modern supervision systems and BMS expect BACnet. The result: a perfectly working Modbus device stays invisible to the BMS. The usual fix — a vendor-specific gateway or an intermediate PLC — is costly and rigid.

How the WBox does it

The WBox reads Modbus RTU and TCP/IP registers and exposes them as BACnet/IP objects in the BMS

The WBox gateway reads Modbus registers (RTU over RS485 or TCP/IP, as master or slave) and exposes them as native BACnet/IP objects — analog input/value, binary input/value. The BMS discovers and reads them like any other BACnet device, with no awareness that the source is Modbus.

Mapping is done by drag & drop in the routing table, with an optional value transformation (scaling, unit change, type conversion) in Blockly or JavaScript. The bridge is bidirectional: the BMS can also write a BACnet setpoint that is pushed back into a Modbus register. A hysteresis and a consistency check limit traffic and protect the equipment.

What you need

Both drivers are licence-activated on the same gateway — no extra hardware. The same principle applies to other protocols: you can route KNX, M-Bus or MQTT to BACnet the same way, or the other way around.

Try the live demo → See inter-protocol routing → Documentation (wiki) →