TC_032_2_CS — Power failure boot charging point-configured to stop transaction(s)

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

Identification

Field	Value
Test case name	Power failure boot charging point-configured to stop transaction(s)
Test case Id	TC_032_2_CS
System under test	Charge Point

Description

This scenario is used to stop transaction all transactions, when a power failure occurred.

Purpose

To test if the Charge Point first stops all transactions after going down, when a power failure occurs.

Prerequisite(s)

The Charge Point does NOT have a back-up power source and thereby is configured to stop transactions after going down.

Before (Preparations)

Configuration State(s):

Memory State(s):

Reusable State(s):

Charging

Scenario Detail(s)

Charge Point (SUT)	Central System (Tool)
[Disconnect and reconnect the power of the Charge Point.]; 1. The Charge Point sends a BootNotification.req	2. The Central System responds with a BootNotification.conf
[Send per connector and connectorId = 0.]; 3. The Charge Point sends a StatusNotification.req	4. The Central System responds with a StatusNotification.conf
[When transaction is resumed by Charge Point (status is Charging) EV driver authorizes / swipes the card with the idTag which was used for the transaction to manually stop the transaction]
5. The Charge Point sends a StopTransaction.req	6. The Central System responds with a StopTransaction.conf
[Only send when not already notified of the status Finishing.]; 7. The Charge Point sends a StatusNotification.req	8. The Central System responds with a StatusNotification.conf

Tool validation(s)

Charge Point side:

Steps 3-7: The order in which the messages are sent may be different.

Step 3:

(Message: StatusNotification.req) connectorId is <The connector which had the ongoing transaction> status is Preparing, Finishing OR Charging (intermediate status unavailable or available are alloAwed) (Message: StatusNotification.req) The other StatusNotification messages. status is Available

Step 5:

(Message: StopTransaction.req) reason is Local or omitted when transaction was manually stopped reason is PowerLoss when transaction was stopped by charger due to power loss

Step 7:

(Message: StatusNotification.req) status is Preparing or Finishing

Central System side:

Step 2:

(Message: BootNotification.conf) status is Accepted

Expected result(s) / behaviour

Charge Point side:

Central System side: