TC_F_07_CS — Remote unlock Connector - Without ongoing transaction - No cable connected
TC_F_07_CS — Remote unlock Connector - Without ongoing transaction - No cable connected
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block F. Remote Control, page 179.
Identification
| Field | Value |
|---|---|
| Test case name | Remote unlock Connector - Without ongoing transaction - No cable connected |
| Test case Id | TC_F_07_CS |
| Use case Id(s) | F05 |
| Requirement(s) | F05.FR.01, F05.FR.06 |
| System under test | Charging Station |
| Functional block | F. Remote Control |
Description
This test case describes how the CSMS can be requested to sent an UnlockConnectorRequest to the charging station. It sometimes happens that a connector of a Charging Station socket does not unlock correctly. This happens most of the time when there is tension on the charging cable. This means the driver cannot unplug his charging cable from the Charging Station. To help a driver, the CSO can send a UnlockConnectorRequest to the Charging Station. The Charging Station will then try to unlock the connector again.
Purpose
To verify if the Chargin Station is able to perform the remote unlock connector mechanism and report the result without ongoing transaction while no cable is connected as described at the OCPP specification.
Prerequisite(s)
The Charging Station has a connector lock.
Before (Preparations)
Configuration State:
- N/a
Memory State:
- N/a
Reusable State(s):
- N/a
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 2. The Charging Station responds with a UnlockConnectorResponse | 1. The OCTT sends a UnlockConnectorRequest with evseId <Configured evseId> connectorId <Configured connectorId> |
Tool validations
Step 2:
Message UnlockConnectorResponse
- status Unlocked
Post scenario validations
- N/a