M-Bus to Modbus gateway

Need to connect M-Bus and Modbus? The Weble WBox routes M-Bus → Modbus natively: one gateway speaks both protocols and maps data points in real time — no PC, no middleware, no cloud dependency.

The protocols

Further reading: Wired vs wireless M-Bus: what is the difference? →

Typical use case

Industrial energy monitoring often means wired M-Bus heat and water meters that a Modbus SCADA or PLC cannot read. The WBox reads the M-Bus meters and presents their values as Modbus registers, so the PLC or SCADA polls consumption exactly like any other Modbus slave. One device replaces an M-Bus level converter plus custom integration, and the meter data lands in the same Modbus map as the rest of the plant.

In the field

Weble customers run this routing in production:

How the WBox bridges M-Bus and Modbus

Activate the M-Bus and Modbus drivers. The WBox polls each M-Bus meter on a cycle, reads the records you need (energy, volume, flow, power) and writes them into its own Modbus slave register map, with units and scaling defined per point. The PLC or SCADA reads those input registers directly over RTU or TCP. A Blockly or JavaScript step can convert units or derive instantaneous power before the value is exposed.

Example mapping

Capacity & limits

• M-Bus — M-Bus drives up to 190 metering slaves through a Weble level converter (250 per the standard).
• Modbus — Modbus addresses up to 247 slaves per line (RTU or TCP) — about 32 RTU devices per RS-485 segment before a repeater.

On the WBox, a driver licence enables the whole protocol — there is no artificial per-point tier to unlock. Capacity scales with the gateway model, from the compact S103 to the E413: you are bounded by the field bus, not by your licence.

Frequently asked questions

What you need

One WBox gateway with these two driver licences:

← All routes