TC_011_2_CS — Remote Start Charging Session – Time Out

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

Identification

Field	Value
Test case name	Remote Start Charging Session – Time Out
Test case Id	TC_011_2_CS
System under test	Charge Point

This scenario is used to set a connector back to available, after receiving a RemoteStartTransaction.req and it takes to long to plugin the cable.

To test if the Charge Point sets the connector back to available, after reaching the configured connection timeout.

Configuration State(s):

Memory State(s):

Reusable State(s):

Charge Point (SUT)	Central System (Tool)
2. The Charge Point responds with a GetConfiguration.conf	1. The Central System sends a GetConfiguration.req
4. The Charge Point responds with a RemoteStartTransaction.conf	3. The Central System sends a RemoteStartTransaction.req
[If AuthorizeRemoteTxRequests = true (from step 2), send an Authorize.req.]; 5. The Charge Point sends an Authorize.req	6. The Central System responds with an Authorize.conf
7. The Charge Point sends a StatusNotification.req	8. The Central System responds with a StatusNotification.conf
[After the configured connection timeout has been reached.]; 9. The Charge Point sends a StatusNotification.req	10. The Central System responds with a StatusNotification.conf

Charge Point side:

Step 2:

(Message: GetConfiguration.conf) The configurationKey.key is AuthorizeRemoteTxRequests

Step 4:

(Message: RemoteStartTransaction.conf) status is Accepted

Step 7:

(Message: StatusNotification.req) status is Preparing

Step 9:

(Message: StatusNotification.req) status is Available

Central System side:

Step 1:

(Message: GetConfiguration.req) The key is AuthorizeRemoteTxRequests

Step 6:

(Message: Authorize.conf) idTagInfo.status is Accepted

Charge Point side:

Central System side: