Skip to content
Documentation Menu

TC_005_1_CSMS — EV Side Disconnected - StopTransactionOnEVSideDisconnect = true -

TC_005_1_CSMS — EV Side Disconnected - StopTransactionOnEVSideDisconnect = true -

UnlockConnectorOnEVSideDisconnect = true

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

Identification

FieldValue
Test case nameEV Side Disconnected - StopTransactionOnEVSideDisconnect = true -; UnlockConnectorOnEVSideDisconnect = true
Test case IdTC_005_1_CSMS
System under testCentral System

Description

This scenario is used to stop the transaction when the cable is disconnected at EV side.

Purpose

To test if the Central System can handle when the Charge Point stops the transaction when the cable is disconnected at EV side, and it is configured to do so.

Prerequisite(s)

  • N/a

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)
[EV driver disconnects cable on EV side.]; 1. The Charge Point sends a StatusNotification.req2. The Central System responds with a StatusNotification.conf
3. The Charge Point sends a StopTransaction.req4. The Central System responds with a StopTransaction.conf
5. The Charge Point sends a StatusNotification.req6. The Central System responds with a StatusNotification.conf
[EV driver unplugs the cable from the Charge Point.]; 7. The Charge Point sends a StatusNotification.req8. The Central System responds with a StatusNotification.conf

Tool validation(s)

Charge Point side:

Step 1:

(Message: StatusNotification.req) status is SuspendedEV

Step 3:

(Message: StopTransaction.req) reason is EVDisconnected

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