TC_005_3_CS — EV Side Disconnected - StopTransactionOnEVSideDisconnect = false -

UnlockConnectorOnEVSideDisconnect = false

Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 15.

Identification

Field	Value
Test case name	EV Side Disconnected - StopTransactionOnEVSideDisconnect = false -; UnlockConnectorOnEVSideDisconnect = false
Test case Id	TC_005_3_CS
System under test	Charge Point

Description

This scenario is used to keep the transaction active, even when the cable is disconnected at EV side.

Purpose

To test if the Charge Point is able to keep the transaction active, when the cable is disconnected at EV side and the Charge Point is configured to do so.

Prerequisite(s)

The configuration key StopTransactionOnEVSideDisconnect is implemented AND has the accessibility ReadWrite.

Before (Preparations)

Configuration State(s):

Value for "MinimumStatusDuration" is "0".
Value for "StopTransactionOnEVSideDisconnect" is "false".
Value for "UnlockConnectorOnEVSideDisconnect" is "false".

Memory State(s):

Reusable State(s):

Charging

Scenario Detail(s)

Charge Point (SUT)	Central System (Tool)
[EV driver unplugs cable on EV side.]; 1. The Charge Point sends a StatusNotification.req	2. The Central System responds with a StatusNotification.conf
4. The Charge Point responds with a RemoteStopTransaction.conf	3. The Central System sends a RemoteStopTransaction.req
[Step 5 and step 7 may be reversed.]; 5. The Charge Point sends a StatusNotification.req	6. The Central System responds with a StatusNotification.conf
[Step 5 and step 7 may be reversed.]; 7. The Charge Point sends a StopTransaction.req	8. The Central System responds with a StopTransaction.conf

Tool validation(s)

Charge Point side:

Step 1:

(Message: StatusNotification.req) status is SuspendedEV AND/OR SuspendedEVSE info is EV side disconnected

Step 5:

(Message: StatusNotification.req) status is Finishing (OR Available in case of a fixed cable)

Step 7:

(Message: StopTransaction.req) reason is Remote

Central System side:

Expected result(s) / behaviour

Charge Point side:

Central System side: