TC_070_CS — Sampled Meter Values

Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 34.

Identification

Field	Value
Test case name	Sampled Meter Values
Test case Id	TC_070_CS
System under test	Charge Point

Description

The Charge Point is able to send different kinds of Sampled MeterValues with a certain interval. What MeterValues are to be sent and at what time(intervals) is configurable.

Purpose

Check whether the Charge Point is able to send MeterValues as configured.

Prerequisite(s)

Before (Preparations)

Configuration State(s):

MeterValueSampleInterval is <Configured Meter Value Sample interval>.
ClockAlignedDataInterval is 0.

Memory State(s):

Reusable State(s):

GetConfiguration for key MeterValuesSampledData
Charging

Scenario Detail(s)

Charge Point (SUT)	Central System (Tool)
[Every x seconds after starting the transaction as configured by the Configuration Key MeterValueSampleInterval.]; 1. The Charge Point sends a MeterValues.req to the Central System.	2. The Central System responds with a MeterValues.conf to the Charge Point.
[Three times the configured MeterValueSampleInterval (in seconds) after starting the transaction.]	n/a

Tool validation(s)

Charge Point side:

Step 3:

(Message: MeterValues.req)

Between the MeterValue.timestamp fields of the sent MeterValues.req should be an interval of x seconds.
The sampledValue.context should be TSample.Periodic
The sampledValue list should contain an sampledValue for each sampledValue.measurand configured in the MeterValuesSampledData Configuration Key (the measurands returned in step 2).
When the value for MeterValuesSampledData is empty the measurand Energy.Active.Import.Register is assumed as default.
None of the provided sampledValues shall have location = EV, except when measurand = SoC.
The sampledValue.format should be Raw or omitted.

Central System side:

Expected result(s) / behaviour

Charge Point side:

Central System side: