Unpublish Firmware
Source: OCPP 2.0.1 Part 2 — Specification (Edition 2, 2022-12-15) — Section 1.63 (Messages); Use Case L04 — Unpublish Firmware file on Local Controller (Functional Block L. FirmwareManagement)
Overview
The CSMS sends UnpublishFirmwareRequest to a Local Controller (acting as Charging Station in the OCPP topology) to remove a previously-published firmware file. The file is identified by its MD5 checksum.
Pairs with PublishFirmware (L03).
Sequence Diagram
CSMS ──── UnpublishFirmwareRequest ────▶ Charging Station (Local Controller)
(checksum)
CSMS ◀─── UnpublishFirmwareResponse ──── Charging Station (Local Controller)
(status)
Initiator
CSMS → Charging Station (Local Controller)
Fields
| Field Name | Field Type | Card. | Description |
|---|---|---|---|
| checksum | identifierString [0..32] | 1..1 | Required. MD5 checksum (hex string of length 32) over the firmware file. |
| Field Name | Field Type | Card. | Description |
|---|---|---|---|
| status | UnpublishFirmwareStatusEnumType | 1..1 | Required. Whether the Local Controller succeeded in unpublishing the firmware. |
UnpublishFirmwareStatusEnumType values
DownloadOngoing— Cannot unpublish; a download is in progress.NoFirmware— No matching firmware found.Unpublished— Successfully unpublished.
Examples
{
"checksum": "9e107d9d372bb6826bd81d3542a419d6"
}{
"status": "Unpublished"
}Schema
Source:
schemas/UnpublishFirmwareRequest.json,schemas/UnpublishFirmwareResponse.json(OCPP 2.0.1 FINAL)