External Modbus Meter Integration
Chargers have internal metering. External meters get added for two different reasons that are worth keeping apart: billing that has to stand up legally, and load control that has to see more than the charger. Those need different meters in different places, and confusing them produces an installation that does neither job properly.
Connecting a charger to an external meter over Modbus: when you actually need one, the difference between billing grade and control grade measurement, how register mapping works in practice, and what the charger must do when the meter stops answering.
Discuss a meter integrationFor An integrator, manufacturer or operator who needs the charger to read a meter it does not contain, usually for billing or for load control.
Two reasons to add an external meter
Both are legitimate. Deciding which one you are installing, before ordering anything, avoids the installation that half serves both purposes.
Swipe to compare
| Billing grade | Control grade | |
|---|---|---|
| Purpose | Charging money against measured energy | Deciding how much current the charger may offer |
| Where it sits | In the charging circuit, per charge point | On the incoming supply, or on the circuit being protected |
| Certification | MID or the local equivalent, sealed and traceable | None required. Accuracy matters, legal standing does not |
| Update rate | Slow is fine. Energy accumulates | Fast enough for the control loop, typically seconds |
| Failure impact | Billing disputes | The site trips, or capacity sits unused |
A single meter rarely does both well. Billing meters are placed and sealed for legal traceability, which is usually the wrong position for seeing what the rest of the building is doing.
Why MID certification comes up
If you are selling energy rather than selling access, the measurement usually has to be legally defensible. That is what a MID certified meter provides, or its equivalent under whichever national scheme applies.
- The meter is type approved, and the approval covers the measurement, not the charger around it
- It is sealed, so the measuring path cannot be altered after installation without evidence
- Readings are traceable, which is what makes a disputed invoice resolvable
- The charger reads it rather than replacing it, so the legal chain stays with the certified device
Where a project needs this, the practical requirement on the charger is simple: it must be able to read an external meter and use those readings as the transaction record, rather than its own internal measurement. That is the integration this page is about.
Modbus RTU and Modbus TCP
- 1
Modbus RTU
Serial, usually RS-485, multi-drop so several meters share one pair. Cheap, robust over distance, and the common choice inside a panel or across a small site. Termination and biasing matter and are frequently got wrong.
- 2
Modbus TCP
Over Ethernet. Easier to route across a large site and easier to debug, at the cost of needing network infrastructure in places where there may be none.
- 3
Gateways
RTU to TCP converters are common where a serial meter has to be reached across a site network. They add a component that can fail silently, so their failure behaviour has to be part of the design rather than an afterthought.
Register mapping, which is where the time goes
Modbus defines how to ask for a register. It does not define what is in it. Every meter vendor lays out their registers differently, and this is the single largest source of integration effort.
- Register addresses differ per model, and often per firmware revision within a model
- Data types vary: 16 bit, 32 bit, float, and word order that is not consistent between vendors
- Scaling factors are sometimes in a separate register and sometimes implicit in the datasheet
- Energy registers may be cumulative or per period, and mistaking one for the other produces bills that are wrong in an interesting way
- Some meters expose the same value in several places with different accuracy
So the integration is per meter model, not per protocol. A charger that supports Modbus supports the protocol; whether it supports your meter is a separate question and the honest answer is that it needs a profile written and tested against that model.
Polling rate against what the control loop needs
For billing, polling can be slow. Energy accumulates and a reading every few seconds is more than enough.
For load control the rate has to match the loop. Poll too slowly and the system reacts after the supply has already been exceeded. Poll too fast on a serial bus with several devices and responses start arriving late, which the controller then interprets as failures. The sizing question is bus bandwidth against device count against required loop period, and it should be settled before the meters are ordered rather than discovered on site.
What happens when the meter stops answering
This is the part most often left undefined, and it is the part that takes a building off supply.
- A load controller that loses its measurement must fall back to a safe fixed allocation, not hold its last known value and not assume full capacity
- A billing integration that loses its meter must stop or flag the transaction rather than silently reverting to internal measurement, because the two will not agree and the difference will surface as a dispute
- Loss must be detected by timeout rather than by error response, since a dead bus produces silence rather than an error
- Recovery must be tested. A system that fails safe and never comes back is a different outage
Want this applied to your own site?
Discuss a meter integrationTechnically reviewed by Deepu Joy, Director of Products and Delivery. Last reviewed 2026-09-10.
Frequently asked questions
Do I need an external meter at all?
Only if you are selling energy and need legally defensible measurement, or if you need to see load the charger cannot see. For access-based charging on a dedicated supply, the internal meter is usually enough.
Does supporting Modbus mean supporting my meter?
No. Modbus defines how to ask for a register, not what is in it. Every vendor maps registers differently, so integration is per meter model and needs a profile written and tested against that model.
RTU or TCP?
RTU over RS-485 inside a panel or across a small site, TCP where the meter has to be reached across an existing network. Gateways bridge the two and add a component whose failure behaviour has to be designed for.
What does the charger do if the meter goes offline?
For load control it must fall back to a safe fixed allocation. For billing it must stop or flag the transaction rather than quietly switching to internal measurement.
Can one meter do billing and load control?
Rarely well. A billing meter is placed and sealed for legal traceability, which is usually the wrong position for observing total site load.
Need a charger to read your meter?
Send the meter make, model and firmware revision, and whether this is for billing or for load control. Those decide the work.
Discuss a meter integration