What happens
You send UpdateFirmware or GetDiagnostics (GetLog in 2.0.1), the charger says yes and then nothing happens, or a DownloadFailed, InstallationFailed or UploadFailed arrives. The command only gives it a URL: the real work is a download or upload the charger does on its own.
Check it in two minutes
The test server doesn't send firmware on purpose, but “Read configuration” tells you whether the charger has the FirmwareManagement profile (without it there's no remote update), and the log shows any firmware or diagnostics status notification it sends. Open the OCPP test server →
The causes, most likely first
1. The charger can't reach that URL or doesn't speak that protocol
Some units only download over FTP, others only over HTTP or HTTPS, and some don't follow redirects. A URL on an internal network or a link that asks you to log in won't work either.
How to fix it: Use a public, direct URL to the file, with the protocol the charger's manual says.
2. The server receiving the upload rejects it
A diagnostics log easily takes several megabytes, and many web servers cut off at 1 MB by default. We had a log of almost 900 KB that only just got through. It also fails if the destination folder isn't writable.
How to fix it: If the server is yours, raise the size limit on that path and check the folder permissions. If not, use one that already has it sorted.
3. The start date is in the future, or the charger's clock is off
UpdateFirmware carries a date from which to download. If the charger's clock is ahead or behind, it may wait hours or never start.
How to fix it: Set the date to now and check the charger's time (NTP).
4. The file isn't for the exact model, or the signature is missing
Firmware for another variant of the same model downloads fine and fails to install. In 2.0.1, many chargers require signed firmware and the manufacturer's certificate.
How to fix it: Ask the manufacturer for the exact file for the model and hardware version, and in 2.0.1 the signature and certificate that go with it.
5. Nobody is looking at the status notifications
The charger reports progress with FirmwareStatusNotification and DiagnosticsStatusNotification: Downloading, Downloaded, Installing, Installed, Uploading, Uploaded. If the platform doesn't show them, it all looks like “it did nothing”.
How to fix it: Check the message log: the last status tells you which step it got stuck on.
What askacharge.com does
You can upload the manufacturer's firmware and we give you an HTTPS URL ready to send to the charger, up to 64 MB. For diagnostics, the charger gets a signed upload URL just for it, valid for 24 hours and up to 50 MB, which still works if it retries.
Frequently asked questions
Why does my OCPP charger return DownloadFailed when updating firmware?
Almost always because it can't reach the URL: a protocol it doesn't support (FTP versus HTTP), a redirect, an internal network or a link that asks you to log in.
Where does the charger upload its diagnostics log?
To the URL you send it in GetDiagnostics (or GetLog in 2.0.1). It has to be a server that accepts the upload and doesn't cut it off for size.