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

SymptomWhere it stopsLook atChecksArticle
The Control Pilot shows a wrong level, state E or F, or a duty cycle that allows nothingPlug-in, or any stage after itCP state and Duty % lanes, Power tabCP-01 to CP-10Control Pilot problems
Car plugged in, no SLAC matchPlug-in or SLACCP state and Duty % lanes, SLAC tabCP-04, CP-05, SL-01 to SL-09Car plugged in, no SLAC match
SLAC needs several attempts, SDP repeats, TCP resends, answers come lateSLAC, or later as Connection lostSLAC tab, Capture tool, SDP and TCP/TLS lanesSL-06, SL-07, SL-09, TC-03A weak or disturbed powerline link
SLAC matched, no SDP answer or TCP never connectsSDP or TCP / TLSSDP and TCP/TLS lanes, SDP rows in the message tableSD-01 to SD-06, TC-01, TIM-04SLAC matched, but no SDP answer or TCP connection
TLS handshake failsTCP / TLSTLS tab, TCP/TLS laneTL-01 to TL-08, PK-01, PK-02The TLS handshake fails
App handshake answered Failed_NoNegotiationHandshakeThe two supportedAppProtocol messagesHS-01 to HS-03No common protocol in the app handshake
Authorization stays Ongoing until the car gives up, or the payment option or contract is refusedSetupThe Authorization loop in the message table, OCPP tabTIM-02, SQ-07, SQ-05The session stops at authorization
A response carries a FAILED codeSetup, Parameters or laterFindings, Message tab, code dictionarySQ-05, SQ-01, SQ-04, SQ-06 to SQ-08The charger answers with a FAILED response code
DC stalls in CableCheck or PreChargeParametersTiming tab, loop fieldsDC-01, TIM-01, TIM-02, SQ-05DC session stalls in CableCheck or PreCharge
Session stops during chargingEnergy transferLast messages, TCP/TLS and CP lanesTIM-01, TIM-03, TC-02, SQ-09, CP-09The session stops during charging
Charging ended, but not cleanly: current after the stop, WeldingDetection repeating, no SessionStopStopLast messages, CP state lane, Power tabPW-03, CP-08, TC-02, IS20-06The session does not end cleanly
Communication fine, but no currentEnergy transferPower tab, CP state laneCP-07, PW-01, PW-02Communication works but no current flows
Charges slower than expectedEnergy transferPower tab, limits in the messagesPW-01, PP-01, IS20-03, IS20-04Charging is slower than expected
CHAdeMO or GB/T session stopsCAN stagesCAN lane, flags and stop reasonsCAN-01, CAN-02, CH-01 to CH-06, GB-01 to GB-07A CHAdeMO or GB/T session stops

From verdict category to article

Verdict categoryStageRead
No digital communicationPlug-in or SLACCar plugged in, no SLAC match
SLAC timeout, SLAC attenuation too highSLACCar plugged in, no SLAC match, A weak or disturbed powerline link
SDP failure, TCP failureSDP, TCP / TLSSLAC matched, but no SDP answer or TCP connection
TLS failureTCP / TLSThe TLS handshake fails
Encrypted, not decryptedTCP / TLSNot a failure: load the key log, see TLS in charging captures
Protocol negotiation failedHandshakeNo common protocol in the app handshake
Pre-charge failedParametersDC session stalls in CableCheck or PreCharge
FAILED response, Authorization not grantedSetup or ParametersThe charger answers with a FAILED response code, The session stops at authorization
Connection lost, Timeout, EVSE stopped, EV stopped early, CP faultEnergy transferThe 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 messageCAN stagesA CHAdeMO or GB/T session stops
No current deliveredCAN charging stageA CHAdeMO or GB/T session stops, Communication works but no current flows
EXI errorAnyThe troubleshooting help page
Incomplete captureAnyThe 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