Meters and Modbus
Multifunction meter monitoring software. Read every panel meter over Modbus, any brand.
Most panels in Indian factories already have a multifunction meter on the door. If it has an RS-485 port, software can read it over Modbus RTU and turn its numbers into history, alerts and bill figures. Here is how that works, what usually goes wrong, and what to check before you buy.
What a multifunction meter measures
A multifunction meter, also called a digital panel meter or power meter, measures many electrical quantities on one feeder. Most panel meters read:
- Voltage and current on each phase, and frequency.
- kW, kVA and kVAr, and power factor.
- Energy: kWh, kVAh and kVArh, as running totals.
- On many models, demand, harmonics (THD) and minimum and maximum values.
On the panel door, it shows one reading at a time, and nothing is kept once the display moves on. Monitoring software reads all of them every few seconds, keeps them, and compares them across panels and days.
The meter already measures everything. Software adds memory, comparison and rupees.
How the software reads a meter
Two things link the software to the meter. RS-485 is the cable: one twisted pair that runs from meter to meter. Modbus RTU is the language spoken on it: one master asks, and each meter answers only when asked.
- Each meter has an address. It is called the slave ID, from 1 to 247, and no two meters on one cable may share it.
- The software asks one meter for a block of registers, such as voltage through power factor.
- The meter answers with raw numbers and a checksum, so a damaged reply is thrown away rather than stored.
- The software scales each number into volts, amps or kWh, using that model’s register map.
- It moves to the next meter, then starts again. Every reading is stored with the time.
Every meter on one cable must use the same baud rate, parity and stop bits, for example 9600 baud, 8 data bits, even parity and 1 stop bit. One meter set differently will not answer, and can disturb the others.
Register maps: why every meter model is different
Every make and model keeps its readings at its own addresses, in its own format. One stores voltage as a 32-bit floating-point number. Another stores it as a whole number to be divided by 10. Some manuals count addresses from 0 and others from 1. Some send the high word first, others the low word.
| What differs | Example | If it is missed |
|---|---|---|
| Register address | Voltage at 3000 on one model and 100 on another | The software reads the wrong quantity |
| Number format | 32-bit float, or a scaled whole number | Readings 10 or 1,000 times off, or nonsense |
| Word order | High word first, or low word first | Huge or tiny values that look random |
| Address offset | The manual counts from 1, the protocol from 0 | Every reading shifted by one register |
| Energy unit | Wh, kWh or MWh, with or without the CT ratio applied | Monthly totals off by a factor |
Register numbers are illustrative. Use the map in your meter model’s own manual.
This is why monitoring software lists the meters it supports. “Modbus compatible” is only the start. Each model’s map has to be loaded and checked against the meter’s own display.
Wiring the RS-485 network
- Daisy-chain from meter to meter, A to A and B to B. Avoid long branches off the main line.
- Use shielded twisted-pair cable, with the shield earthed at one end only.
- Fit a 120 Ω termination resistor at the two far ends of the line, not at every meter.
- Keep it away from power cables and drive output cables where you can, and cross them at right angles.
- Give every meter its own slave ID. Two meters with the same ID answer together and garble each other.
- Check the A and B labels. Some makes label them the other way round. If one meter will not answer, swapping its A and B is a common fix.
RS-485 can run up to about 1,200 metres at lower baud rates. Long runs, many meters and electrical noise each need more care.
Common problems, and what causes them
| What you see | The usual cause |
|---|---|
| One meter never answers | Wrong slave ID, baud rate or parity, or A and B swapped |
| Several meters drop out at random | Missing or extra termination, a loose joint, or noise from a drive |
| Readings 10 or 1,000 times too big | Wrong scaling or energy unit in the register map |
| Voltage right, but current and power wrong | Wrong CT ratio set in the meter |
| Power negative on one phase | A CT fitted the wrong way round, or on the wrong phase |
| Energy suddenly drops to zero | The meter was reset, or its counter rolled over |
A good system shows a meter that has stopped answering as missing, not as a flat line that looks like zero load.
What the software should do with the readings
- Keep full-detail history for months, and summaries for years.
- Build 15- or 30-minute demand intervals like the DISCOM meter, in kVA where you are billed in kVA.
- Arrange the meters as a panel tree, so the incomer can be checked against the sum of its feeders. See sub-metering.
- Price the units on your tariff: demand, TOD zones and power factor.
- Raise alerts at limits you set, to a named person.
- Export to Excel and CSV.
Mixing brands on one network
Plants rarely have one brand. Panels from different years and different panel builders carry different meters. Good software reads them all on one cable, as long as they share the cable settings, each has its own slave ID, and each model’s register map is loaded. Single-phase and three-phase meters can share the same line.
Common makes on Indian panels include Schneider, Secure, Lauritz Knudsen (formerly L&T), Rishabh, Selec, Chint, HPL, Elmeasure, Siemens and ABB.
Meter setup tools, data loggers and monitoring software
| Tool | What it does | What it does not do |
|---|---|---|
| Meter maker’s setup tool | Sets up one meter: CT ratio, slave ID, baud rate | Long history, many brands, bill figures, alerts |
| Energy meter data logger | Records readings to a file for later | Live view, alerts, panel tree, tariffs |
| SCADA or PLC | Runs and controls the process, shows live values | Bill-ready demand intervals and tariffs, often an add-on |
| Energy monitoring software | Reads every meter, keeps history, prices it, alerts | Replace protection relays or the DISCOM meter |
A maker’s setup tool is useful at commissioning. It is not monitoring: it does not keep months of history, compare panels, price units or raise alerts.
Where the software runs
Monitoring software can run on a PC in the plant, on a cloud server, or inside a gateway in the panel.
- A PC has to stay on, and updates and restarts interrupt it.
- A cloud server needs the Internet for every reading to reach it.
- A gateway that reads, stores and serves the dashboard itself needs neither.
See cloud vs on-premises energy monitoring for the trade-offs.
Before you buy: a checklist
- List every meter: make, model, slave ID, and whether it has an RS-485 port.
- Ask the vendor to confirm each model, and who maps the registers.
- Check that kVA demand and kVAh are read where your bill uses them.
- Ask how many meters each gateway reads, and how the network is split.
- Check the history, the export, and what happens with no Internet.
- Ask how a meter that stops answering is shown and alerted.
For the wider checks on data, control and support, see the buying guide.
How KONDUKTOR® EMS reads your meters
KONDUKTOR® EMS gateways read multifunction meters over RS-485 Modbus RTU: any brand, single- or three-phase, up to 10 meters per gateway, mixed on one network. Your meter make and model are mapped before installation. More gateways are added as the plant grows, and all of them appear in one dashboard and one panel tree.
- Live readings on every meter, with the running Maximum Demand interval against Contract Demand.
- Power factor, the TOD split, idle detection and an estimated bill on your tariff.
- History kept on the gateway in your plant, with an encrypted backup on a plant computer. Nothing is sent to KONDUKTOR or to any cloud.
- Excel and CSV export of every meter’s history.
- After a power cut, logging restarts on its own and the gap is filled with estimated energy, so totals still match the meter.
See which meters connect.
Common questions
What is multifunction meter monitoring software?+
Software that reads the multifunction meters on your panels over RS-485 Modbus RTU, keeps every reading as history, and turns the readings into demand, power factor, energy and bill figures, with alerts.
What does MFM mean on a panel?+
MFM is short for multifunction meter: a panel meter that measures voltage, current, power, power factor and energy on one feeder. Most come with an RS-485 port, so software can read them.
How do I read an energy meter over RS-485?+
Connect the meter’s RS-485 A and B terminals to a gateway or converter with twisted-pair cable. Give each meter its own slave ID, set the same baud rate and parity on every meter, and load each model’s register map in the software.
What is a Modbus register map?+
A table from the meter maker that lists where each reading is stored, its number format, its scaling and its unit. Software needs the right map for each model to turn raw numbers into volts, amps and kWh.
Can different meter brands share one RS-485 network?+
Yes, if every meter uses the same baud rate, parity and stop bits, each has its own slave ID, and the software has each model’s register map.
How many meters can one RS-485 line take?+
The RS-485 standard allows 32 unit loads on one line, and many meters draw less than one unit load. In practice, polling time sets the limit: the more meters on a line, the longer each round of readings takes.
What is the difference between an energy meter data logger and monitoring software?+
A data logger records readings to a file for later. Monitoring software also shows live values, builds demand intervals the way the DISCOM does, prices them on your tariff, compares panels and raises alerts.
Your meters are already measuring. Start keeping the readings.
Book a live demo and see live readings, Maximum Demand and bill figures from meters like yours.