Skip to content
Documentation Menu

TC_041_CS — Fault Behavior

TC_041_CS — Fault Behavior

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

Identification

FieldValue
Test case nameFault Behavior
Test case IdTC_041_CS
System under testCharge Point

Description

This scenario is used to refuse starting a transaction, when the Charge Point in fault state.

Purpose

To test if the Charge Point refuses starting a transaction, when it is in fault 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)
[Set the Charge Point in fault state.]; 1. The Charge Point sends a StatusNotification.req2. The Central System responds with a StatusNotification.conf
3. [The EV Driver tries to start a transaction.]; [The Charge Point does not start a transaction.]

Tool validation(s)

Charge Point side:

Step 1:

(Message: StatusNotification.req) status is Faulted

Step 3:

The tool waits for <Configured Transaction Duration> to verify that no transaction is started.

Central System side:

  • N/a

Expected result(s) / behaviour

Charge Point side:

  • N/a

Central System side:

  • N/a