
What is M-Bus? A practical guide to meter reading and integration
M-Bus, short for Meter-Bus, is a communication system for reading utility meters remotely. Water, gas, electricity and heat meters can report their data to a central reading system instead of requiring an operator to visit each display. Its European standards sit within the EN 13757 family. In building automation, the purpose is to collect meter information; the bus does not perform the meter’s measurement for it. [1], [2]
A meter appearing in a scan is only the beginning. Before a reading reaches an energy report, the system must identify the right meter, select the right record, apply its unit correctly and show whether the value is still current. This guide concentrates on wired M-Bus, with a separate explanation of the wireless variant.
On this page: Connecting the meter to a controller · Reading the data correctly · Worked decoding example · What the two wires carry · Capacity and cable layout · Wireless M-Bus · Commissioning checks · Standards and references
Start with the complete data path
A useful way to plan an installation is to write down the path from meter → M-Bus reader or gateway → controller or head-end → report. A PLC with Modbus RTU support does not automatically speak M-Bus. These are different protocols, even when both systems happen to use two-wire connections. A gateway must perform the required conversion rather than merely change a connector. [14]
For example, SENECA’s Z-KEY-MBUS reads M-Bus meters and makes selected data available through Modbus RTU/TCP. The controller-side address and the meter’s M-Bus address belong to different interfaces. The relevant Modbus register mapping comes from the gateway configuration, not from a universal register list shared by all M-Bus meters. [14], [13]
A BACnet building system needs a gateway that explicitly implements the appropriate conversion; HMS documents such an M-Bus-to-BACnet gateway. When choosing this type of interface, identify both ends of the connection. An Ethernet socket on its own does not tell you what application protocol, device role or data mapping the unit provides. The distinction is also important when comparing other industrial communication systems. [17]
A valid number can still be the wrong reading
M-Bus records carry information about the data as well as the data itself. DIF and DIFE describe the data format and record context; VIF and VIFE identify the measured quantity, unit and further qualifiers. A meter may expose a current total, stored readings and tariff-specific records. Selecting a value because it is the first number returned is not a reliable mapping method. [11], [13]
For each reportable point, keep a mapping entry containing the meter identity, record meaning, unit and any applied conversion. Consider two tags labelled “energy”: one might be the current total and the other a stored period-end value. Both may be legitimate, but substituting one for the other changes what the report says. This is a data-selection problem, not necessarily a communication fault.
When setting up SCADA, compare the selected value with the meter display under matching conditions. Put a last-successful-read timestamp and a communication-quality indicator beside the value. On an HMI, a retained number without an age or fault indication can look like a live reading after the meter has stopped responding. Treat that display behaviour as part of the acceptance test.
Worked example: six bytes are not a complete telegram
The following illustrative record fragment uses the classic variable-data layout and assumes least-significant byte first. It is not a captured meter response or a request to send to a device. Framing, address, security and checksum processing are outside this small exercise. [11]
Record fragment: 04 13 40 E2 01 00
DIF: 04h
VIF: 13h
Integer bytes: 40 E2 01 00
Decoded integer: 0x0001E240 = 123456
Volume: 123456 × 0.001 m³ = 123.456 m³
Here, 04h specifies a 32-bit integer and 13h selects a volume unit of 10⁻³ m³. The result is therefore 123.456 m³, or 123456 litres. The suffix “h” denotes hexadecimal notation. This example shows why a raw integer cannot be labelled with an engineering unit until the record has been interpreted. [12]
Now suppose the same counter previously read 122.900 m³. With no reset, rollover or meter replacement between the readings, the interval difference is 0.556 m³, or 556 litres. The cumulative total is not the interval consumption. Likewise, a gateway that already outputs cubic metres must not have the litre-to-cubic-metre factor applied again in the controller. These results are calculations for the stated example, not observed site data.
What actually travels over the two wires?
In a wired network, the reader acts as the master and requests a response from an addressed meter. This is a master/slave exchange, rather than independent simultaneous transmissions from every meter. The electrical directions differ: the master transmits by changing the bus voltage; a meter replies by modulating its current draw. Communication is half-duplex. [18]
The pair can also supply a compatible meter interface. There is no dedicated “data wire” alongside a separate “power wire”; the same circuit carries both functions. Bus-powered interface electronics do not necessarily mean that the entire meter has no battery. Hardware can combine bus and battery supply arrangements, depending on what the meter has to keep operating. [5]
Do not connect an ordinary RS-485 adapter to M-Bus terminals. M-Bus needs its own electrical interface. Nor does current-modulated data make the bus a 4–20 mA analogue input. A computer may expose a reader through a serial communication port, but that host-side port name does not define the electrical signals at the meter-side terminals. [18], [8]
Size the bus by load, not by the number printed in a headline
Three limits should be listed separately in a design: the available addresses, the electrical capacity of the master and the reader software’s supported devices or data points. Primary addresses 1–250 provide an address range; they do not promise that every master can power 250 meters. A secondary-address search does not create additional electrical capacity either. [9], [10], [7], [13]
Electrical loading is expressed in unit loads (UL). One standard load represents up to 1.5 mA of quiescent bus current, and an individual meter may account for more than one UL. Add the declared loads before choosing the master. Reply-current modulation is a separate part of bus operation, so a quiescent-current sum is not a specification for a generic DC supply. [8], [18]
Example load schedule: thirty 1 UL meters plus ten 2 UL meters make 40 physical meters but 50 UL. The corresponding upper-bound quiescent budget is 50 × 1.5 mA = 75 mA. This is a hypothetical schedule used to explain the calculation.
Elvaco specifies its CMeX11S at 64 UL / 96 mA. Against that rating, the example leaves 14 UL unallocated. That arithmetic is only a first check: conductor resistance, capacitance, voltage at the remote devices and the intended baud rate still have to satisfy the installation requirements. [7], [16]
A different implementation illustrates the point. Beckhoff’s KL6781 specifies up to 40 standard loads and 300 m of total cable; the protocol is handled by the TwinCAT M-Bus library. Its rating cannot be replaced with a generic “250-device” claim. The CMeX11S also specifies a nominal 42 V DC master port, so a fixed voltage copied from an unrelated design is not a universal M-Bus specification. [8], [7]
Cable layout: distinguish the longest run from the whole network
Wired meters connect in parallel to the pair. Line, star and tree arrangements can be used with suitable cabling. Polarity-independent interfaces simplify connection, but the meter’s terminal diagram must still be checked: pulse outputs, supply terminals and M-Bus connections are not interchangeable. The total length of every branch is a different quantity from the distance to the furthest meter. [16], [6]
Do not import RS-485 termination rules. OMS Annex P prohibits ring topology and termination resistors on wired M-Bus. It also keeps the bus conductors isolated from earth or other voltage potentials and places a cable-screen earth connection at the master only. Those bus rules do not remove any protective-earth connection required for the equipment itself. [6]
There is no single cable-distance promise that covers every master, cable and meter count. Use the selected equipment’s limits and the cable’s resistance and capacitance. A design record should distinguish maximum run, total length, wire size and baud rate, rather than reducing the whole installation to one distance. This makes later extensions easier to assess against the original assumptions. [16], [7], [8]
Keep device identity separate from a station address
The primary address is a short bus address. Secondary addressing uses a fuller identity comprising an identification number, manufacturer code, version and device/medium type. After selection, the special address 253 is used for the selected device. Selection is not the same as permanently assigning a new primary address. [10]
For maintenance, record the physical location and the complete returned identity alongside the meter label. Where primary addresses are used, resolve duplicates before relying on a full-network poll. 254 can trigger multiple replies and collisions; 255 is a no-reply broadcast. Neither should be treated as an ordinary spare meter address. [9], [16]
Wireless M-Bus is a separate interface choice
Wireless M-Bus uses radio communication covered by EN 13757-4:2025. Walk-by or drive-by collection and fixed receivers are different deployment arrangements. For a wireless project, match the meter’s radio mode and configuration to the receiver; do not transfer a wired bus’s power budget or termination rules to the radio side. [3]
The practical distinction is not “wired equals mains power, wireless equals battery”. Check how the actual meter and its communication interface are powered. For battery-supported devices, the permitted communication workload may matter as much as the baud rate or transmission interval. OMS Annex P explicitly addresses declared communication budgets for relevant wired devices, too. [5], [6]
Choose an acquisition interval, not just a baud rate
The classic serial character format is 8 data bits, even parity and one stop bit (8E1). Support for a particular baud rate remains a device question: CMeX11S lists 300 and 2400 bit/s, while KL6781 lists 300–9600 baud. Configure an option supported by both ends rather than assuming that a familiar rate is universal. [9], [7], [8]
A useful datalogger design keeps the time a response was received separate from any timestamp belonging to the stored meter record. Polling the same stored reading again does not make the measurement newer. Set the acquisition interval to suit the reporting task and the meter’s documented update and communication restrictions. Repeated requests should not be used as a substitute for understanding why a value has not changed. [6], [13]
Security depends on the implemented profile
The label M-Bus does not establish that readings are encrypted. In OMS Volume 2, issue 5.0.1, wired communication can operate without a security profile or with one of the specified profiles. Encryption and message authentication are different properties, and not all profiles provide them in the same combination. Check the meter, gateway, active configuration and key handling together. [15]
The classic telegram checksum detects transmission errors; it does not provide confidentiality or cryptographic source authentication. EN 13757-7 covers transport and security services, but referencing the family does not prove that a particular legacy meter implements them. Apply industrial cybersecurity controls at the gateway and management network as well: limit access and protect configuration accounts and keys. [9], [4], [15]
Commission the installation in stages
Document the intended result. Before connecting the network, list each meter’s wired-interface option, declared load, supported speed and required readings. Add power or communication-budget restrictions where the manual specifies them. The following workflow is a practical checking method, not a replacement for a product’s installation instructions.
Establish a small known-good setup. Have qualified personnel read one known meter using the correct master and a short connection. Compare identity, unit and displayed value. Save the working configuration before adding the building cabling, so later changes can be compared with a reproducible starting point.
Expand one branch at a time. Check the device list and error state after each addition. Follow the manufacturer’s isolation procedure for wiring changes. Resistance or continuity testing requires an appropriately de-energised, isolated circuit with electronic devices disconnected as necessary; do not test resistance on an operating bus. [16]
Test a failure, not just a successful read. Under controlled conditions, interrupt access to a meter and check what the gateway, controller and display do. An unreadable meter must not silently become zero consumption. Nor should an old value acquire a new timestamp that makes it appear freshly measured. Preserve the approved device inventory and point mapping with the project backup.
Troubleshooting by symptom
Nothing responds: start with shared causes—the master supply and fault indication, the correct output terminals, common baud settings and the actual M-Bus reading software. Compare the complete installation with the small known-good setup before changing several software parameters at once.
One added branch stops the bus: isolate that change in a controlled way. Investigate a short circuit, wrong terminal connection or excess load before redesigning the whole network. Change one condition at a time so that a recovery can be linked to a specific intervention.
A subset of meters is missing: compare the missing devices’ locations, connections, supported speeds and identities. Look for duplicate addresses. A similarly named entry from another meter is not proof that the intended device has been found.
Values are present but implausible: check volume against flow, energy against power, current against historical data and one tariff against another. A clean factor-of-1000 error suggests a unit-conversion check; a frozen number calls for an age and communication-status check. These are diagnostic starting points, not unique explanations for every fault.
Which standards and documents belong in the project file?
Within the European standards framework, EN 13757-2:2018+A1:2023 addresses wired communication at the physical and data-link layers, while EN 13757-3:2025 addresses application protocols. EN 13757-4:2025 covers Wireless M-Bus and EN 13757-7:2025 covers transport and security services. Record the relevant edition and the actual product documentation rather than treating the family number as a complete design specification. [1], [2], [3], [4]
OMS provides implementation specifications intended to support interoperable metering. Keep the physical interface, protocol support, data profile and security configuration visible as separate project requirements. The historic M-Bus Usergroup pages below are useful for understanding the classic coding examples, but explicitly warn against using the late-1990s text as a current engineering specification. [19], [9], [11]
Finally, communication acceptance is not measurement calibration or accuracy assurance. A report also needs a defensible meter reading, time period and interpretation. When energy data feeds a carbon-footprint calculation, define the reporting boundary and emission factor separately. A successfully transferred counter value is an input to that assessment, not proof of savings or of the final result.