TC_034_CS — Power Failure with Unavailable Status
TC_034_CS — Power Failure with Unavailable Status
Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 45.
Identification
| Field | Value |
|---|---|
| Test case name | Power Failure with Unavailable Status |
| Test case Id | TC_034_CS |
| System under test | Charge Point |
Description
This scenario is used to persist the status of the connectors, when a power failure occurs.
Purpose
To test if the Charge Point persists the status of the connectors, when a power failure occurs.
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) |
|---|---|
| 2. The Charge Point responds with a ChangeAvailability.conf | 1. The Central System sends a ChangeAvailability.req |
| [Send per connector and connectorId = 0.]; 3. The Charge Point sends a StatusNotification.req | 4. The Central System responds with a StatusNotification.conf |
| [Disconnect and reconnect the power of the Charge Point.]; 5. The Charge Point sends a BootNotification.req | 6. The Central System responds with a BootNotification.conf |
| [Send per connector and connectorId = 0.]; 7. The Charge Point sends a StatusNotification.req | 8. 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) status is Unavailable
Step 7:
(Message: StatusNotification.req) status is Unavailable
Central System side:
Step 1:
(Message: ChangeAvailability.req) The connectorId is 0 The type is Inoperative
Step 6:
(Message: BootNotification.conf) status is Accepted
Expected result(s) / behaviour
Charge Point side:
- N/a
Central System side:
- N/a