The charger answers with a FAILED response code
A request is refused with a FAILED code and the session ends. The code names the rule the charger applied; the request and what the charger offered earlier say why.
What you see
- A response whose ResponseCode starts with FAILED, usually followed by the end of the session.
- SQ-05 reports the request and the code. The verdict is FAILED response: Never charged when it happened before energy transfer, Stopped early after it, and Completed when the car had already asked to stop and only the wrap-up was refused.
- A related verdict, Authorization not granted, has no FAILED code at all: AuthorizationRes stays at EVSEProcessing Ongoing until the capture ends.
Reading a code
- Find the request that was refused (the finding links to it) and open both in the Message tab.
- Find what the charger announced earlier: ServiceDiscoveryRes for services and payment options, ChargeParameterDiscoveryRes for limits and schedules. Most refusals are a request that asks for something that was not on offer.
- Look the code up in the code dictionary: response codes for ISO 15118-2 and DIN SPEC 70121, and a separate list for ISO 15118-20.
- ISO 15118-20 also has WARNING codes. They do not end the session, and the tool does not count them as failures.
Likely causes
| Code | Usual cause | How to confirm in the capture |
|---|---|---|
FAILED_SequenceError | A message the charger did not expect in its current state, often after a lost response or a retry | SQ-01, and SQ-03 when the car did not wait for a response |
FAILED_UnknownSession | A SessionID other than the one assigned, or a resume of a session the charger no longer knows | SQ-04, SQ-11 |
FAILED_ServiceSelectionInvalid, FAILED_PaymentSelectionInvalid | The car selected a service or payment option the charger did not offer | SQ-07 and the lists in ServiceDiscoveryRes |
FAILED_WrongEnergyTransferMode | RequestedEnergyTransferMode not in the charger's supported list (DIN SPEC 70121 names the code differently) | SQ-06 |
FAILED_WrongChargeParameter | EV parameters outside what the charger accepts, for example a maximum current, voltage or energy request it cannot serve | The ChargeParameterDiscovery pair; try the ac-failed demo |
FAILED_TariffSelectionInvalid, FAILED_ChargingProfileInvalid | PowerDelivery names a schedule tuple the charger did not send, or a charging profile above the schedule | SQ-08 and the SAScheduleList |
FAILED_PowerDeliveryNotApplied, FAILED_ContactorError | The charger could not switch the power on | The EVSE status fields in the same response; the charger's own log |
FAILED_CertificateExpired, FAILED_CertChainError, FAILED_SignatureError, FAILED_CertificateRevoked, FAILED_NoCertificateAvailable, FAILED_ContractCanceled | Plug and Charge: the contract certificate or its signature was rejected | PaymentDetails, Authorization and certificate messages; see the PKI articles |
FAILED | A generic refusal without a reason | Only the charger's log can tell |
Fixes that usually work
- Make the car request only what the charger offered: energy transfer mode, payment option, schedule tuple.
- Compare the EV limits in ChargeParameterDiscoveryReq with the charger's range. A car limit the charger cannot serve, for example a maximum voltage outside its range, is a common trigger for FAILED_WrongChargeParameter.
- For sequence errors, look at the message before the refused one: a missing response, a timeout that made the car retry, or a step the car skipped.
- For Authorization not granted, check the charger's backend: an RFID card that was never presented, an offline backend, or a Plug and Charge contract that is not known.
Sources
- ISO 15118-2:2014, response codes
- DIN SPEC 70121:2014-12, response codes
- ISO 15118-20:2022, response codes