Energy meters with a Modbus RTU port are the easiest way to see where a plant’s power goes. They are also where a lot of first IoT projects lose a week, because “it speaks Modbus” says very little about what the numbers mean.
Every meter has its own register map
Modbus defines how to ask for registers, not what is in them. One meter keeps voltage at one address, the next model from the same brand moves it. Some use holding registers (function code 03), others input registers (04). Some documents number registers from 0, others from 1, and some write them as 40001-style addresses. An off-by-one here gives you plausible-looking wrong data, which is worse than an error.
We keep one register-map file per meter model, checked against a reading on the meter’s own display before anything goes to the cloud.
32-bit values and word order
Most values are 32-bit floats or integers spread across two 16-bit registers. The order of those two registers is not fixed: some meters send the high word first, others the low word. Read with the wrong order and 230.1 V turns into a huge number or a tiny one. The fix is one setting per meter model, once you know to look for it.
Scaling and CT ratios
Some meters report primary values, already multiplied by the current transformer ratio. Others report the secondary side and expect you to apply the ratio. The register map does not always say which. We confirm against the display with a known load.
How fast can you poll?
At 9600 baud with 8N1 framing, one character takes about a millisecond. A request for a few registers and its reply come to about 20 characters, plus the silent gaps Modbus RTU needs between frames, plus the meter’s own response delay, which is often tens of milliseconds. So a single read takes somewhere between about 50 and 150 ms. Read 15 values from each of 20 meters on one bus and a full cycle takes many seconds.
Group consecutive registers into one request, read fast-changing values more often than cumulative ones, and raise the baud rate if every meter on the bus supports it.
Read the counters as well
For energy use, read the cumulative kWh register and compute the difference between readings in the cloud, instead of adding up instantaneous power. A missed poll then costs no energy data. Handle meter resets and counter rollover explicitly, and store the raw counter as well as the calculated value.
If you are connecting energy meters across a plant, book a discovery call and tell us which meters you have.
