TC_014_CS — Soft Reset Without Transaction

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

Identification

Field	Value
Test case name	Soft Reset Without Transaction
Test case Id	TC_014_CS
System under test	Charge Point

Description

This scenario is used to soft reset a Charge Point, while no transaction is active.

Purpose

To test if the Charge Point will soft reset, after being requested by the Central System.

Prerequisite(s)

Before (Preparations)

Configuration State(s):

Memory State(s):

Reusable State(s):

Scenario Detail(s)

Charge Point (SUT)	Central System (Tool)
2. The Charge Point responds with a ChangeAvailability.conf	1. The Central System sends a ChangeAvailability.req
3. The Charge Point sends a StatusNotification.req	4. The Central System responds with a StatusNotification.conf
6. The Charge Point responds with a Reset.conf	5. The Central System sends a Reset.req
[This message is optional.]; 7. The Charge Point sends a BootNotification.req	8. The Central System responds with a BootNotification.conf
[These StatusNotification messages will only be sent if step 7 is sent.]; 9. The Charge Point sends a StatusNotification.req	10. The Central System responds with a StatusNotification.conf
12. The Charge Point responds with a ChangeAvailability.conf	11. The Central System sends a ChangeAvailability.req
13. The Charge Point sends a StatusNotification.req	14. The Central System responds with a StatusNotification.conf

Tool validation(s)

Charge Point side:

Step 2:

(Message: ChangeAvailability.conf) The status is Accepted

Step 3:

(Message: StatusNotification.req) connectorId is <Configured ConnectorId> status is Unavailable

Step 6:

(Message: Reset.conf) status is Accepted

Step 9:

(Message: StatusNotification.req) connectorId is <Configured ConnectorId> status is Unavailable (Message: StatusNotification.req) The other StatusNotification messages. status is Available

Step 12:

(Message: ChangeAvailability.conf) The status is Accepted

Step 13:

(Message: StatusNotification.req) connectorId is <Configured ConnectorId> status is Available

Central System side:

Step 1:

(Message: ChangeAvailability.req) The connectorId is <Configured ConnectorId> The type is Inoperative

Step 5:

(Message: Reset.req) The type is Soft

Step 8:

(Message: BootNotification.conf) status is Accepted

Step 11:

(Message: ChangeAvailability.req) The connectorId is <Configured ConnectorId> The type is Operative

Expected result(s) / behaviour

Charge Point side:

Central System side: