TC_J_02_CS — Clock-aligned Meter Values - Transaction ongoing
TC_J_02_CS — Clock-aligned Meter Values - Transaction ongoing
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block J. MeterValues, page 221.
Identification
| Field | Value |
|---|---|
| Test case name | Clock-aligned Meter Values - Transaction ongoing |
| Test case Id | TC_J_02_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 test | Charging Station |
| Functional block | J. 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, while a transaction is ongoing, 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> AlignedDataSendDuringIdle is false (If implemented)
Memory State:
- N/a
Reusable State(s):
- State is EnergyTransferStarted
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| Note(s):; - The Charging Station can follow Steps 1 and 2 or Steps 3 and 4 | |
| 1. The Charging Station notifies the CSMS about its measured Meter Values.; Note(s):; - During a transaction the MeterValueRequest or NotifyEventRequest can still be used to report meter values for the main power meter (evseId=0) and idle EVSEs; - 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, in case the amount of measured data is too much for one message. | 2. The OCTT responds accordingly. |
| 3. The Charging Station sends a TransactionEventRequest; Note(s):; - During a transaction the meter values for the configured EVSE with the ongoing transaction should be transmitted using the TransactionEventRequest. _- The TransactionEventRequest messages do NOT need to be send/received at the exact specified interval. The configured measurands must be measured at the configured interval.; - Multiple TransactionEventRequest messages may be sent per configured interval, in case the amount of measured data is too much for one message. _- The OCTT will end the testcase after it has the <Configured transaction duration> is reached. | 4. The OCTT responds with a TransactionEventResponse |
Tool validations
Note: The following steps do not need to be sent in a specific order.
Step 1:
Message: MeterValuesRequest
- meterValue[0].sampledValue[0].context must be Sample.Clock
- meterValue[0].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">
Step 3:
Message: TransactionEventRequest
- triggerReason must be MeterValueClock
- metervalue[0].sampledValue[0].context must be Sample.Clock
- metervalue[0].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">
Post scenario validations
Message: TransactionEventRequest
- timestamp <The intervals between the timestamps of the received TransactionEventRequest messages must equal the configured value at AlignedDataInterval. However it is allowed to send multiple Meter Value messages per configured interval, in case the amount of measured data is too much for one message. But the timestamp of these messages must all be the same.> 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, in case the amount of measured data is too much for one message. 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, in case the amount of measured data is too much for one message. But the timestamp of these messages must all be the same.>