Skip to content
Documentation Menu

TC_002_CS — Cold Boot Charge Point - Pending

TC_002_CS — Cold Boot Charge Point - Pending

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

Identification

FieldValue
Test case nameCold Boot Charge Point - Pending
Test case IdTC_002_CS
System under testCharge Point

Description

This scenario is used to delay the startup for a Charge Point. For example to set the correct configurations.

Purpose

To test if the Charge Point is able to retrieve and set configuration while in pending state.

Prerequisite(s)

  • N/a

Before (Preparations)

Configuration State(s):

  • N/a

Memory State(s):

  • N/a

Reusable State(s):

  • N/a

Scenario Detail(s)

Charge Point (SUT)Central System (Tool)
[Power cycle the Charge Point.]; 1. The Charge Point sends a BootNotification.req2. The Central System responds with a BootNotification.conf
4. The Charge Point responds with a GetConfiguration.conf3. The Central System sends a GetConfiguration.req
6. The Charge Point responds with a ChangeConfiguration.conf5. The Central System sends a ChangeConfiguration.req
7. The Charge Point sends a BootNotification.req8. The Central System responds with a BootNotification.conf
[Send a StatusNotification per connector and connectorId=0.]; 9. The Charge Point sends a StatusNotification.req10. The Central System responds with a StatusNotification.conf
[Every x seconds.]; 11. The Charge Point sends a Heartbeat.req12. The Central System responds with a Heartbeat.conf

Tool validation(s)

Charge Point side:

Step 6:

(Message: ChangeConfiguration.conf) status is Accepted

Step 7:

(Message: BootNotification.req) Send BootNotification after interval specified in BootNotification.conf from step 2.

Step 9:

(Message: StatusNotification.req) status is Available

Step 11:

(Message: Heartbeat.req) Send a Heartbeat.req every x seconds. x equals interval from step 8.

Central System side:

Step 2:

(Message: BootNotification.conf) The status is Pending

Step 3:

(Message: GetConfiguration.req) The key is <Omitted>

Step 5:

(Message: ChangeConfiguration.req) The key is MeterValueSampleInterval value is <Configured Meter Value interval>

Step 8:

(Message: BootNotification.conf) The status is Accepted The interval is <Configured Heartbeat interval>

Expected result(s) / behaviour

Charge Point side:

  • N/a

Central System side:

  • N/a