No common protocol in the app handshake
The charger answers supportedAppProtocolReq with Failed_NoNegotiation: the car and the charger share no protocol, or one side lists it wrongly.
What you see
- supportedAppProtocolReq from the car, supportedAppProtocolRes with ResponseCode Failed_NoNegotiation, then the connection closes.
- The stage strip stops at Handshake. The verdict is Never charged with Protocol negotiation failed and Either as party, because the fault can sit on either side.
Likely causes
| Cause | Who | How to confirm in the capture |
|---|---|---|
| No overlap: the car offers only ISO 15118-20 or ISO 15118-2, the charger only DIN SPEC 70121 (or the other way round) | Either | Compare the namespaces in the request with what the charger is configured for; HS-02 |
| A protocol that needs TLS offered on a plain TCP connection | EV or EVSE | HS-03; the SDP request asked for no TLS |
| Malformed entry: a namespace typo, a wrong VersionNumberMajor, duplicate SchemaID or priority | EV | HS-01 names the entry |
| A protocol disabled in the charger configuration | EVSE | The car's list is correct and includes a protocol the charger model is known to support |
Related faults that do not end in Failed_NoNegotiation: a charger that answers OK with a SchemaID the car never offered, and a car that carries on after Failed_NoNegotiation. HS-02 reports both.
What to check in this tool
- Message tab of supportedAppProtocolReq: each entry with ProtocolNamespace, VersionNumberMajor and Minor, SchemaID and Priority (1 is the most preferred).
- Message tab of the response: ResponseCode and SchemaID. The code dictionary explains each app handshake code.
- SD-04 and the SDP security byte, to see whether the connection is TLS.
Fixes that usually work
- Enable a protocol both sides speak. For DC, DIN SPEC 70121 is still the common fallback of most cars.
- For ISO 15118-20, get TLS 1.3 working first; the protocol is only negotiated over TLS.
- Correct the namespaces and major versions to the table in the app handshake article. A different minor version is fine: it is answered with OK_SuccessfulNegotiationWithMinorDeviation.
- On AC, a charger that supports it may fall back to basic PWM charging after a failed negotiation (V2G20-1837), so a car that still charges slowly may be in this state.
Sources
- ISO 15118-2:2014, supportedAppProtocol
- ISO 15118-20:2022, V2G20-167 to V2G20-173, V2G20-1837