TC_024_CSMS — Start Charging Session Lock Failure
Start Charging Session Lock Failure (TC_024_CSMS) — OCPP 1.6 OCTT compliance test. This scenario is used to report a connector lock failure.
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Central System, page 142.
Identification
| Field | Value |
|---|---|
| Test case name | Start Charging Session Lock Failure |
| Test case Id | TC_024_CSMS |
| System under test | Central System |
Description
This scenario is used to report a connector lock failure.
Purpose
To test if the Central System is able to handle a report of a connector lock failure.
Prerequisite(s)
- N/a
Before (preparations)
Configuration State(s):
- N/a
Memory State(s):
- N/a
Reusable State(s):
- Authorized
Scenario detail(s)
| Charge Point (SUT) | Central System (Tool) |
|---|---|
| 1. The Charge Point sends a StatusNotification.req | 2. The Central System responds with a StatusNotification.conf |
| [EV driver plugs in the cable.]; 3. The Charge Point sends a StatusNotification.req | 4. The Central System responds with a StatusNotification.conf |
Tool validation(s)
Charge Point side:
Step 1:
(Message: StatusNotification.req) status is Preparing
Step 3:
(Message: StatusNotification.req) errorCode is ConnectorLockFailure status is Faulted
Central System side:
- N/a
Expected result(s) / behaviour
Charge Point side:
- N/a
Central System side:
- N/a