TC_044_1_CS — Firmware Update - Download and Install

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

Identification

Field	Value
Test case name	Firmware Update - Download and Install
Test case Id	TC_044_1_CS
System under test	Charge Point

Description

The firmware of a Charge Point is updated.

Purpose

Check whether the Charge Point can update its firmware.

Prerequisite(s)

The Charge Point supports the Firmware Management feature profile and a dummy firmware is prepared.
Based on the configuration key SupportedFileTransferProtocols. FTP, FTPS, HTTP, HTTPS. The tester has to setup a server which supports one of the specified protocols.
A valid firmware needs to stored at the server and configured at the Firmware Download URL.

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. If the Charge Point supports installation of firmware during a charging session, the Charge Point MAY install the firmware after only setting all other connectors to Unavailable.]; [The Charge Point starts downloading the firmware]; 3. The Charge Point sends a FirmwareStatusNotification.req	4. The Central System responds with a FirmwareStatusNotification.conf
[The Charge Point has finished downloading the firmware]; 5. The Charge Point sends a FirmwareStatusNotification.req	6. The Central System responds with a FirmwareStatusNotification.conf
[The Charge Point starts installing the firmware]; 7. The Charge Point sends a FirmwareStatusNotification.req	8. The Central System responds with a FirmwareStatusNotification.conf
9. The Charge Point sends a BootNotification.req	10. The Central System responds with a BootNotification.conf
11. The Charge Point sends a StatusNotification.req	12. The Central System responds with a StatusNotification.conf
13. The Charge Point sends a FirmwareStatusNotification.req	14. The Central System responds with a FirmwareStatusNotification.conf
[The following steps are only applicable if the central system did not receive a BootNotification.req within the configured max timeout period.]
16. The Charge Point responds with a Reset.conf	15. The Central System sends a Reset.req

Tool validation(s)

Charge Point side:

Step 3:

(Message: FirmwareStatusNotification.req) The status is Downloading

Step 5:

(Message: FirmwareStatusNotification.req) The status is Downloaded

Step 7:

(Message: FirmwareStatusNotification.req) The status is Installing

SAtep 9 / 14: The messages can be in a different order, but the described order is recommended.

Step 11:

(Message: StatusNotification.req) The status is Available

Step 13:

(Message: FirmwareStatusNotification.req) The status is Installed

Step 15:

(Message: Reset.req) The type is Hard

Central System side:

Step 1:

(Message: UpdateFirmware.req) The firmware.location is <Firmware Download URL from test data>

Expected result(s) / behaviour

Charge Point side:

The Charge Point handles the firmware update correctly and is Available after the update.

Central System side: