Skip to content
Documentation Menu

TC_005_1_CS — EV Side Disconnected - StopTransactionOnEVSideDisconnect = true -

TC_005_1_CS — EV Side Disconnected - StopTransactionOnEVSideDisconnect = true -

UnlockConnectorOnEVSideDisconnect = true

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

Identification

FieldValue
Test case nameEV Side Disconnected - StopTransactionOnEVSideDisconnect = true -; UnlockConnectorOnEVSideDisconnect = true
Test case IdTC_005_1_CS
System under testCharge Point

Description

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

Purpose

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

Prerequisite(s)

  • The Charge Point does not have a fixed cable on Charge Point side.
  • The configuration key StopTransactionOnEVSideDisconnect does NOT have the accessibility ReadOnly in combination with value false.

Before (Preparations)

Configuration State(s):

  • Value for "MinimumStatusDuration" is "0".
  • Value for "StopTransactionOnEVSideDisconnect" is "true".
  • Value for "UnlockConnectorOnEVSideDisconnect" is "true".

Memory State(s):

  • N/a

Reusable State(s):

  • Charging

Scenario Detail(s)

Charge Point (SUT)Central System (Tool)
[EV driver unplugs cable on EV side.]; [Step 1 and step 3 may be reversed.]; 1. The Charge Point sends a StopTransaction.req2. The Central System responds with a StopTransaction.conf
[Step 1 and step 3 may be reversed.]; 3. The Charge Point sends a StatusNotification.req4. The Central System responds with a StatusNotification.conf
[EV driver unplugs the cable from the Charge Point.]; 5. The Charge Point sends a StatusNotification.req6. The Central System responds with a StatusNotification.conf

Tool validation(s)

Charge Point side:

Step 1:

(Message: StopTransaction.req) reason is EVDisconnected

Step 3:

(Message: StatusNotification.req) status is Finishing

Step 6:

(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