Troubleshooting by symptom
A map from what you see on the bench to the stage where the session stopped, the checks that look at it and the article that lists the usual causes.
The method
A charging session is a fixed chain of steps, and each step can only start once the one before it has finished. Troubleshooting is therefore mostly about finding the first link that broke, not the last error message. Three questions get you there:
- What was the last stage that passed? The stage strip shows it: Plug-in, SLAC, SDP, TCP / TLS, Handshake, Setup, Parameters, Energy transfer, Stop, Unplug for a high level session. Everything to the right of the break is a consequence, not a cause.
- Who owed the next message? In ISO 15118 and DIN SPEC 70121 the car always asks and the charger always answers. If the last message is a request, the charger owed the answer; if it is a response, the car owed the next request. SLAC has a fixed order too, and the verdict names the side whose message is missing.
- What does the verdict say? It gives an outcome (Completed, Never charged, Stopped early, Incomplete capture), a category such as SLAC timeout or FAILED response, the likely party and a confidence. It is a triage hint, not a certification result.
Then open the Findings list with errors first. The findings the verdict leans on are marked, and each one names the messages it is about, so a click takes you to the right row of the message table.
Symptom index
| Symptom | Where it stops | Look at | Checks | Article |
|---|---|---|---|---|
| The Control Pilot shows a wrong level, state E or F, or a duty cycle that allows nothing | Plug-in, or any stage after it | CP state and Duty % lanes, Power tab | CP-01 to CP-10 | Control Pilot problems |
| Car plugged in, no SLAC match | Plug-in or SLAC | CP state and Duty % lanes, SLAC tab | CP-04, CP-05, SL-01 to SL-09 | Car plugged in, no SLAC match |
| SLAC needs several attempts, SDP repeats, TCP resends, answers come late | SLAC, or later as Connection lost | SLAC tab, Capture tool, SDP and TCP/TLS lanes | SL-06, SL-07, SL-09, TC-03 | A weak or disturbed powerline link |
| SLAC matched, no SDP answer or TCP never connects | SDP or TCP / TLS | SDP and TCP/TLS lanes, SDP rows in the message table | SD-01 to SD-06, TC-01, TIM-04 | SLAC matched, but no SDP answer or TCP connection |
| TLS handshake fails | TCP / TLS | TLS tab, TCP/TLS lane | TL-01 to TL-08, PK-01, PK-02 | The TLS handshake fails |
| App handshake answered Failed_NoNegotiation | Handshake | The two supportedAppProtocol messages | HS-01 to HS-03 | No common protocol in the app handshake |
| Authorization stays Ongoing until the car gives up, or the payment option or contract is refused | Setup | The Authorization loop in the message table, OCPP tab | TIM-02, SQ-07, SQ-05 | The session stops at authorization |
| A response carries a FAILED code | Setup, Parameters or later | Findings, Message tab, code dictionary | SQ-05, SQ-01, SQ-04, SQ-06 to SQ-08 | The charger answers with a FAILED response code |
| DC stalls in CableCheck or PreCharge | Parameters | Timing tab, loop fields | DC-01, TIM-01, TIM-02, SQ-05 | DC session stalls in CableCheck or PreCharge |
| Session stops during charging | Energy transfer | Last messages, TCP/TLS and CP lanes | TIM-01, TIM-03, TC-02, SQ-09, CP-09 | The session stops during charging |
| Charging ended, but not cleanly: current after the stop, WeldingDetection repeating, no SessionStop | Stop | Last messages, CP state lane, Power tab | PW-03, CP-08, TC-02, IS20-06 | The session does not end cleanly |
| Communication fine, but no current | Energy transfer | Power tab, CP state lane | CP-07, PW-01, PW-02 | Communication works but no current flows |
| Charges slower than expected | Energy transfer | Power tab, limits in the messages | PW-01, PP-01, IS20-03, IS20-04 | Charging is slower than expected |
| CHAdeMO or GB/T session stops | CAN stages | CAN lane, flags and stop reasons | CAN-01, CAN-02, CH-01 to CH-06, GB-01 to GB-07 | A CHAdeMO or GB/T session stops |
From verdict category to article
| Verdict category | Stage | Read |
|---|---|---|
| No digital communication | Plug-in or SLAC | Car plugged in, no SLAC match |
| SLAC timeout, SLAC attenuation too high | SLAC | Car plugged in, no SLAC match, A weak or disturbed powerline link |
| SDP failure, TCP failure | SDP, TCP / TLS | SLAC matched, but no SDP answer or TCP connection |
| TLS failure | TCP / TLS | The TLS handshake fails |
| Encrypted, not decrypted | TCP / TLS | Not a failure: load the key log, see TLS in charging captures |
| Protocol negotiation failed | Handshake | No common protocol in the app handshake |
| Pre-charge failed | Parameters | DC session stalls in CableCheck or PreCharge |
| FAILED response, Authorization not granted | Setup or Parameters | The charger answers with a FAILED response code, The session stops at authorization |
| Connection lost, Timeout, EVSE stopped, EV stopped early, CP fault | Energy transfer | The session stops during charging, Control Pilot problems, The session does not end cleanly |
| One side is missing, Handshake failure, Vehicle fault, Charger fault, Vehicle error message, Charger error message | CAN stages | A CHAdeMO or GB/T session stops |
| No current delivered | CAN charging stage | A CHAdeMO or GB/T session stops, Communication works but no current flows |
| EXI error | Any | The troubleshooting help page |
| Incomplete capture | Any | The capturing help page |
Before you blame a side
- Is the capture complete? A recording started after plug-in misses SLAC and SDP, and one stopped early reads as Incomplete capture. Start recording before the plug goes in and stop it after the unplug.
- Where was it taken? A sniffer modem on the cable sees both sides. A capture on the IP side of one modem has no SLAC at all, and a capture on a host interface may miss what the other modem sent.
- Are the clocks aligned? CP checks that compare the Control Pilot log with messages (CP-07, CP-08, PW-02) depend on the alignment shown in the Alignment tab.
- The likely party is a heuristic. It says who owed the next step, which is usually but not always who is broken. A charger that never answers may be waiting on its own backend.
Articles in this section
- Control Pilot problems
- Car plugged in, no SLAC match
- A weak or disturbed powerline link
- SLAC matched, but no SDP answer or TCP connection
- The TLS handshake fails
- No common protocol in the app handshake
- The session stops at authorization
- The charger answers with a FAILED response code
- DC session stalls in CableCheck or PreCharge
- The session stops during charging
- The session does not end cleanly
- Communication works but no current flows
- Charging is slower than expected
- A CHAdeMO or GB/T session stops
- Worked examples: the demo sessions that fail, read step by step
- Every timer and timeout (reference)
Sources
- SPEC.md of this tool, section 10, session end verdicts
- ISO 15118-2:2014, ISO 15118-3:2015, IEC 61851-1:2017, as cited in the linked articles