Skip to content
Documentation Menu

TC_044_3_CS — Firmware Update - Installation Failed

TC_044_3_CS — Firmware Update - Installation Failed

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

Identification

FieldValue
Test case nameFirmware Update - Installation Failed
Test case IdTC_044_3_CS
System under testCharge Point

Description

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

Purpose

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

Prerequisite(s)

  • Based on the configuration key SupportedFileTransferProtocols. FTP, FTPS, HTTP, HTTPS. The tester has to setup a server which supports one of the specified protocols.
  • An invalid firmware needs to stored at the server and configured at the Invalid Firmware Location.

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 UpdateFirmware.conf1. 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.req4. The Central responds with a FirmwareStatusNotification.conf
[The Charge Point has finished downloading the firmware]; 5. The Charge Point sends a FirmwareStatusNotification.req6. The Central responds with a FirmwareStatusNotification.conf
[The Charge Point starts installing the firmware]; 7. The Charge Point sends a FirmwareStatusNotification.req8. The Central responds with a FirmwareStatusNotification.conf
[This step is optional.]; 9. The Charge point reboots and sends a BootNotification.req10. The Central System responds with a BootNotification.conf
11. The Charge Point sends a FirmwareStatusNotification.req12. The Central responds with a FirmwareStatusNotification.conf
[This step is optional. The Charge Point reports the status of all connectors after a boot.]; 13. The Charge Point sends a StatusNotification.req14. The Central responds with a StatusNotification.conf

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:

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

Step 9 / 11 / 13:

The messages can be in a different order.

Step 11:

(Message: FirmwareStatusNotification.req) The status is InstallationFailed

Step 13:

(Message: StatusNotification.req) The status is Available

Central System side:

Step 1:

(Message: UpdateFirmware.req) location is <The location of a NOT supported file>

Expected result(s) / behaviour

Charge Point side:

  • N/a

Central System side:

  • N/a