Skip to content
Documentation Menu

TC_J_01_CS — Clock-aligned Meter Values - No transaction ongoing

TC_J_01_CS — Clock-aligned Meter Values - No transaction ongoing

Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block J. MeterValues, page 219.

Identification

FieldValue
Test case nameClock-aligned Meter Values - No transaction ongoing
Test case IdTC_J_01_CS
Use case Id(s)J01
Requirement(s)J01.FR.01,J01.FR.02,J01.FR.03,J01.FR.06,J01.FR.07,J01.FR.08,J01.FR.14,J01.FR.15
System under testCharging Station
Functional blockJ. MeterValues

Description

The Charging Station samples the electrical meter or other sensor/transducer hardware to provide information about its Meter Values. Depending on configuration settings, the Charging Station will send Meter Values.

Purpose

To verify if the Charging Station is able to send clock-aligned Meter Values, when it is configured to do so.

Prerequisite(s)

The Charging Station has an energy meter.

Before (Preparations)

Configuration State:

  • AlignedDataInterval is <Configured clock-aligned Meter Values interval>

Memory State:

  • N/a

Reusable State(s):

  • N/a

Main (Test scenario)

Charging StationCSMS
1. The Charging Station notifies the CSMS about its measured Meter Values.; Note(s):; - The Meter Value messages do NOT need to be send/received at the exact specified interval. The configured measurands must be measured at the configured interval.; - Multiple Meter Value messages may be sent per configured interval. One (or more in case the amount of measured data is too much for one message) for each EVSE and one (or more) for the main power meter (connectorId=0); - The OCTT will end the testcase after it has received three Meter Value messages.2. The OCTT responds accordingly.

Tool validations

Step 1:

Message: MeterValuesRequest

  • sampledValue[0].context must be Sample.Clock
  • sampledValue must contain <An element per configured measurand at the AlignedDataMeasurands. The measurand field may be omitted when the measurand is "Energy.Active.Import.Register"> Message: NotifyEventRequest
  • eventData must contain <An element per configured measurand at the AlignedDataMeasurands.>
  • trigger must be Periodic
  • component.name must be "FiscalMetering" Note: The following tool validation will NOT be validated by the OCTT:
  • variable.name must <Refer to the configured measurand in PascalCase without a "." in between. For example; "EnergyActiveImportRegister">

Post scenario validations

Message: MeterValuesRequest

  • timestamp <The intervals between the timestamps of the received Meter Value messages must equal the configured value at AlignedDataInterval. However it is allowed to send multiple Meter Value messages per configured interval. One (or more in case the amount of measured data is too much for one message) for each EVSE and one (or more) for the main power meter (evseId=0). But the timestamp of these messages must all be the same.> Message: NotifyEventRequest
  • timestamp <The intervals between the timestamps of the received Meter Value messages must equal the configured value at AlignedDataInterval. However it is allowed to send multiple Meter Value messages per configured interval. One (or more in case the amount of measured data is too much for one message) for each EVSE and one (or more) for the main power meter (evseId=0). But the timestamp of these messages must all be the same.>