EV Charging Meter Values: From Hardware Energy Meter to OCPP Charging Platform

EV charging projects are not only about power output, connector type or charger appearance. For charge point operators, EVSE manufacturers, charging platform providers and project integrators, reliable metering data is one of the foundations for billing, monitoring, load management and smart charging.

In an EV charging station, meter values may come from a hardware energy meter or an embedded metering circuit. These values are read by the charger controller, mapped into the required data structure and transmitted to the Charging Station Management System (CSMS) through protocols such as OCPP.

If metering data is inaccurate, delayed, incomplete or incorrectly mapped, the charging platform may face problems with billing records, energy reports, load control, maintenance analysis or customer dispute handling.

The Open Charge Alliance describes OCPP as the communication protocol between charging stations and charging management systems. OCA lists OCPP 1.6, OCPP 2.0.1 and OCPP 2.1 as currently supported versions. OCPP 2.0.1 Ed.3 was approved as IEC 63584 in 2024, and OCPP 2.1 was released in 2025.

For EV charging project buyers, the key question is:

How does hardware metering data become reliable OCPP metering data for the charging platform?

What Are Meter Values in EV Charging?

In EV charging, meter values are measurement data used to describe the electrical status or energy consumption of a charging session. Depending on charger design and OCPP implementation, these values may include energy, power, voltage, current, frequency, state of charge, timestamps or other electrical data.

In this article, meter values refer to the metering data used in EV charging to describe kWh, power, voltage, current, time-based consumption and other measurement information. These values may come from a physical energy meter or an embedded metering circuit, and they may later be transmitted to the CSMS through OCPP after charger controller processing.

In OCPP 1.6, MeterValues.req can be used to send measurands such as power, energy, voltage and EV battery state of charge. In OCPP 2.x implementations, transaction-related metering data may be handled differently. For example, OCA materials note that transaction-related meter values can be sent via TransactionEvent, while MeterValues may still be used in other contexts.

Buyers should confirm the OCPP version, platform requirements and charger controller implementation before integration. Meter values should not be treated as a simple number. They are part of a complete data chain involving the physical meter, charger controller, communication mapping, OCPP data structure, backend processing and billing logic.

Which Data Does an EV Charging Meter Provide?

An EV charging meter may provide different electrical data depending on whether it is installed on the AC side, DC side, cabinet branch circuit or charger output path.

Common metering data may include:

• kWh energy:charging session records, billing reference and energy reports
• Active power:load monitoring, power limitation and smart charging
• Voltage:electrical status and abnormal condition detection
• Current:cable, phase or output current monitoring
• Frequency:grid-side monitoring in AC systems
• Power factor:AC-side power quality review
• Import / export energy:selected bidirectional or energy-flow analysis projects
• Load profile data:energy analysis and demand management
• Event or alarm data:maintenance and troubleshooting, depending on system design

Not every EV charging meter provides all of these values. Available data depends on the meter type, measurement point, accuracy class, communication interface, firmware and charger controller integration.

How Hardware Meter Data Reaches the OCPP Platform

A simplified EV charging metering data chain may look like this:

Hardware Energy Meter / Metering Circuit
→ Charger Controller
→ OCPP Data
→ Charging Station Management System (CSMS)
→ Billing / Monitoring / Load Management Platform

The hardware energy meter measures electrical values. The charger controller reads these values through an interface such as RS485, Modbus, CAN, pulse output or an internal connection. The controller then maps the metering data according to charger software and platform requirements before sending it to the CSMS.

Many integration problems happen at this stage. For example:

• The controller cannot read the required register from the meter
• The data unit is mapped incorrectly
• Energy values are cumulative in one system but session-based in another
• The reporting interval does not match platform logic
• Phase-level data is required but not provided
• Signed meter values may be required in selected billing markets but are not supported by the charger, meter or platform design
• Billing software interprets meter data differently from the charger controller

For this reason, meter data integration should be verified through communication mapping, charger controller testing, platform testing and target-market billing review.

OCPP, Modbus and Charger Controller Integration

OCPP and Modbus are often discussed together in EV charging projects, but they serve different roles.

Modbus is commonly used between the energy meter and the charger controller. For example, a DIN rail energy meter or DC energy meter may send kWh, voltage, current or power values to the controller through RS485 / Modbus.

OCPP is used between the charging station and the CSMS. The charger controller sends charging status, transaction data, meter values and other information to the platform through OCPP.

A simplified relationship is:

Meter to Controller: RS485 / Modbus / Pulse / CAN / Internal Interface
Controller to Platform: OCPP

OCPP does not automatically guarantee billing accuracy. It provides a communication framework for exchanging data between the charger and the platform. Billing accuracy depends on the meter, measurement point, accuracy class, calibration, data mapping, platform logic and local compliance requirements.

Metering Data for Billing, Load Management and Maintenance

Reliable metering data supports several EV charging use cases.

For billing, the system needs correct energy values, timestamps, session start and stop data, and billing logic. In some markets or applications, billing-related metering may involve MID, Eichrecht, OCMF, signed meter values or other local requirements. These requirements should be confirmed according to country, charger type, billing model, meter model and certificate scope.

OCA’s signed meter values material describes a standardized method for sharing signed meter values between a charging station and a charging station management system, including use cases related to legal metrology requirements such as German Eichrecht. This should be treated as a target-market requirement, not a universal requirement for all EV charging projects.

For load management, the charging platform may need real-time or near-real-time power, current and energy data. This helps operators control total site load, avoid overload, allocate power among chargers and support smart charging strategies.

For maintenance, voltage, current, phase imbalance, abnormal power changes or communication loss can help identify potential issues. Metering data can also support energy reports, charger utilization analysis and operation performance review.

AC-side and DC-side Metering Points

EV charging stations may use different metering points depending on charger type and project requirement.

AC-side metering may be used for AC chargers, distribution circuits, feeder monitoring or site-level energy management. Typical products may include:

• Single-phase AC meters
• Three-phase AC meters
• DIN rail energy meters
• RS485 / Modbus communication-enabled meters

DC-side metering may be used in DC charging systems where output-side DC energy measurement is required. DC energy meters can help measure DC voltage, current, power and energy depending on model and system design.

Project buyers should not assume that an AC-side meter and a DC-side meter serve the same purpose. The correct metering point should be defined according to charger architecture, billing requirement, platform logic, certification requirement and target market.

Meter Selection Checklist for EVSE Manufacturers and CPOs

Before selecting an EV charging meter, EVSE manufacturers, charge point operators and system integrators should confirm:

A better project question is not only “Which meter should we use for EV charging?” but:

Which measurement point, data values, communication interface, refresh rate and billing requirements must this EV charging meter support for our charger and platform?

How YTL Can Support EV Charging Metering Projects

Zhejiang Yongtailong Electronic Co., Ltd. (YTL) manufactures energy metering and power measurement products for commercial, industrial, EV charging, smart building, PV/ESS, data center and power distribution applications.

For EV charging metering projects, relevant YTL product categories may include:

• Single-phase AC meters
• Three-phase AC meters
• DIN rail energy meters
• DC energy meters
• Fast data refresh energy meters for load management applications
• RS485 / Modbus communication-enabled meters
• Multi-function power meters by application
• OEM/ODM metering support by project

YTL can support EVSE manufacturers, CPOs and system integrators in evaluating meter type, metering point, communication interface, Modbus register map requirements, OCPP measurand mapping discussion, data refresh requirements, certification documents and sample testing requirements.

EV charging billing compliance should always be confirmed according to selected meter model, certificate scope, charger controller design and target-market rules. MID, Eichrecht, OCMF, signed meter values or other billing-related requirements must be reviewed by model, certificate and project application.

Selected YTL models may support AC or DC metering, RS485 / Modbus communication, fast data refresh or DIN rail installation depending on product design and project requirements. Exact capability should always be confirmed before procurement.

FAQ

What are meter values in EV charging?

Meter values are electrical measurement data used in EV charging, such as kWh, power, voltage, current, timestamps or other values depending on charger design and OCPP implementation.

How do EV chargers use OCPP metering data?

EV chargers can send metering data to a CSMS through OCPP. The platform may use the data for session records, billing, monitoring, load management and reporting.

Does OCPP guarantee billing accuracy?

No. OCPP provides a communication framework. Billing accuracy depends on the hardware meter, measurement point, accuracy class, data mapping, platform logic and local billing requirements.

What is the difference between OCPP MeterValues and hardware meter readings?

Hardware meter readings come from the physical meter or metering circuit. OCPP metering data is the data transmitted from the charging station to the management platform after controller reading, mapping and processing.

Is MID required for EV charging billing?

It depends on the target market and project requirement. Some markets or applications may require MID, Eichrecht, OCMF, signed meter values or other compliance conditions. Buyers should confirm requirements by country, charger type and billing model.

What is the difference between Modbus and OCPP in EV charging?

Modbus is often used between the energy meter and charger controller. OCPP is used between the charger and the CSMS.

Where should the energy meter be installed in an EV charging station?

The metering point depends on charger architecture and project requirements. It may be installed on the AC input, AC branch circuit, DC output path, cabinet level or site level. Buyers should define the metering point according to billing, monitoring, load management and compliance requirements.

Can one meter support all EV charging platforms?

Not automatically. Meter integration should be verified through communication mapping, charger controller testing and platform requirements.

What should EVSE manufacturers check before selecting a meter?

They should confirm the metering point, AC or DC measurement, required data values, communication interface, refresh rate, accuracy class, certification documents and controller integration requirements.

Conclusion

EV charging meter values connect the physical electrical measurement layer with the digital charging platform. Hardware meters provide kWh, power, voltage, current and other data. Charger controllers read and map these values. OCPP then helps transmit the metering data to the CSMS for billing, monitoring, load management and maintenance.

For EVSE manufacturers, CPOs and project integrators, successful EV charging metering depends on more than selecting a meter. It requires correct measurement point definition, communication mapping, OCPP data configuration, platform testing and target-market billing review.

Planning an EV charging metering project? Share your charger architecture, AC or DC metering point, required measurands, communication interface, OCPP version, billing market and estimated quantity with YTL. Our team can support meter selection, technical confirmation and project-specific metering evaluation.