TC_018_1_CS — Unlock Connector - With Charging Session (Not fixed cable)
TC_018_1_CS — Unlock Connector - With Charging Session (Not fixed cable)
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 30.
Identification
| Field | Value |
|---|---|
| Test case name | Unlock Connector - With Charging Session (Not fixed cable) |
| Test case Id | TC_018_1_CS |
| System under test | Charge Point |
Description
This scenario is used to unlock a connector of a Charge Point, while a transaction is ongoing.
Purpose
To test if the Charge Point unlocks the connector, when requested by the Central System.
Prerequisite(s)
Charging Station does not have a fixed cable.
Before (Preparations)
Configuration State(s):
- N/a
Memory State(s):
- N/a
Reusable State(s):
- Charging
Scenario Detail(s)
| Charge Point (SUT) | Central System (Tool) |
|---|---|
| 2. The Charge Point responds with a UnlockConnector.conf | 1. The Central System sends a UnlockConnector.req |
| 3. The Charge Point sends a StopTransaction.req | 4. The Central System responds with a StopTransaction.conf |
| 5. The Charge Point sends a StatusNotification.req | 6. The Central System responds with a StatusNotification.conf |
| [EV driver unplugs the cable.]; 7. The Charge Point sends a StatusNotification.req | 8. The Central System responds with a StatusNotification.conf |
Tool validation(s)
Charge Point side:
Step 2:
(Message: UnlockConnector.conf) status is Unlocked
Step 3:
(Message: StopTransaction.req) reason is UnlockCommand
Step 5:
(Message: StatusNotification.req) status is Finishing
Step 7:
(Message: StatusNotification.req) status is Available
Central System side:
- N/a
Expected result(s) / behaviour
Charge Point side:
- N/a
Central System side:
- N/a