Skip to content
Documentation Menu

TC_E_37_CS — Stop transaction options - PowerPathClosed - EV side disconnect

TC_E_37_CS — Stop transaction options - PowerPathClosed - EV side disconnect

Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block E. Transactions, page 142.

Identification

FieldValue
Test case nameStop transaction options - PowerPathClosed - EV side disconnect
Test case IdTC_E_37_CS
Use case Id(s)E06(S5)
Requirement(s)E06.FR.06, E06.FR.15
System under testCharging Station
Functional blockE. Transactions

Description

OCPP 2.x.x has a flexible transaction mechanism that allows the transaction start and stop points to be configured differently. This test covers one of the stop options.

Purpose

To verify if the Charging Station stops a transaction when the EV and the EVSE get disconnected and TxStopPoint contains PowerPathClosed.

Prerequisite(s)

  • The Charging Station does NOT have the following configuration; The mutability of TxStopPoint is ReadOnly AND (the value PowerPathClosed is NOT set OR (EnergyTransfer OR EVConnected OR DataSigned is set)).
  • If the mutability of TxStopPoint is ReadWrite, then the value PowerPathClosed must be supported.

Before (Preparations)

Configuration State:

  • TxStopPoint contains PowerPathClosed StopTxOnEVSideDisconnect is false (If mutability is ReadWrite)

Memory State:

  • N/a

Reusable State(s):

  • State is EnergyTransferSuspended

Main (Test scenario)

Charging StationCSMS
Manual Action: Disconnect the EV and EVSE on EV side (EVSE loses connection with EV).
1. The Charging Station sends a TransactionEventRequest2. The OCTT responds with a TransactionEventResponse

Tool validations

Step 1:

Message: TransactionEventRequest

  • triggerReason must be EVCommunicationLost
  • transactionInfo.chargingState must be Idle
  • transactionInfo.stoppedReason must be EVDisconnected
  • eventType must be Ended

Post scenario validations

  • N/a