Documentation Menu

TC_G_11_CSMS — Change Availability EVSE - With ongoing transaction

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

Identification

Field	Value
Test case name	Change Availability EVSE - With ongoing transaction
Test case Id	TC_G_11_CSMS
Use case Id(s)	G03
Requirement(s)	N/a
System under test	CSMS
Functional block	G. Availability

Description

This test case covers how the CSMS requests the Charging Station to change the availability of one of the EVSEs from Operative to Inoperative. An EVSE is considered Operative in any status other than Faulted and Unavailable.

Purpose

To verify if the CSMS is able to send a change availability request during a transaction according to the mechanism as described at the OCPP specification.

Prerequisite(s)

n/a

Before (Preparations)

Configuration State:

Memory State:

Reusable State(s):

Main (Test scenario)

Charging Station	CSMS
Note(s): Request the CSMS to change the availablitiy to inoperative
2. The OCTT responds with a ChangeAvailabilityResponse with status Scheduled	1. The CSMS sends a ChangeAvailabilityRequest
Note(s): Wait for <Configured Transaction Duration>
3. Execute Reusable State StopAuthorized
4. Execute Reusable State EVConnectedPostSession
5. Execute Reusable State EVDisconnected
6. The OCTT notifies the CSMS about the current state of all connectors with; Message: StatusNotificationRequest; - connectorStatus Unavailable; - evseId <Configured evseId> OR; Message: NotifyEventRequest; - trigger Delta; - actualValue "Unavailable"; - component.name "Connector"; - component.evse.id <Configured evseId>; - variable.name "AvailabilityState"	7. The CSMS responds accordingly.

Tool validations

Step 1:

Message ChangeAvailabilityRequest

operationalStatus Inoperative
evse.id <Configured evseId>
connectorId omit

Post scenario validations

A respond to report the state of a connector has been received for all connectors.