TC_044_2_CS — Firmware Update - Download Failed

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

Identification

Field	Value
Test case name	Firmware Update - Download Failed
Test case Id	TC_044_2_CS
System under test	Charge Point

Description

The firmware of a Charge Point is being updated, but downloading the firmware fails.

Purpose

Check whether the Charge Point can exchange valid messages for a firmware update in case downloading of the firmware fails.

Prerequisite(s)

The Charge Point supports the Firmware Management feature profile.

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 UpdateFirmware.conf	1. The Central System sends a UpdateFirmware.req
[Before downloading the firmware the Charge Point MAY set all connectors to Unavailable.]; [The Charge Point starts downloading the firmware]; 3. The Charge Point sends a FirmwareStatusNotification.req	4. The Central responds with a FirmwareStatusNotification.conf
[Downloading the firmware fails]; 5. The Charge Point sends a FirmwareStatusNotification.req	6. The Central responds with a FirmwareStatusNotification.conf

Tool validation(s)

Charge Point side:

Step 3:

(This message is optional, because the download may fail immediately) (Message: FirmwareStatusNotification.req) The status is Downloading

Step 5:

(Message: FirmwareStatusNotification.req) The status is DownloadFailed

Central System side:

Step 1:

(Message: UpdateFirmware.req) location is <Configured firmware location> where the filename part of the location is prefixed with "does_not_exist_". retries is 0

Expected result(s) / behaviour

Charge Point side:

Old firmware remains active, Charge Point becomes Available again after being set to Unavailable when downloading the firmware.

Central System side: