Worked example: charge parameters refused

The ac-failed demo read step by step: an ISO 15118-2 AC session in which the charger answers ChargeParameterDiscovery with FAILED_WrongChargeParameter although both sets of parameters agree, and what that leaves you to check.

The capture

  • Load the demo AC, refused (ac-failed): 3.0 s of an ISO 15118-2 AC session with external identification, from SLAC to the closed TCP connection, without TLS and without a Control Pilot log.
  • Verdict: Never charged, FAILED response, likely party EVSE, confidence high. The explanation: the charger answered ChargeParameterDiscovery with FAILED_WrongChargeParameter 2.7 s after the start.
  • Stage strip: SLAC to Setup passed, Parameters failed, Energy transfer and Stop not reached.
  • One finding, SQ-05; 32 checks pass, and the Capture tool grades the file good.

Message by message

  1. EV: supportedAppProtocolReq, 1.700 s: ISO 15118-2 first, DIN SPEC 70121 second
  2. EVSE: supportedAppProtocolRes, ISO 15118-2 selected
  3. EVSE: SessionSetupRes, OK_NewSessionEstablished
  4. EVSE: ServiceDiscoveryRes, ExternalPayment; AC_single_phase_core and AC_three_phase_core
  5. EV: PaymentServiceSelectionReq, ExternalPayment
  6. EVSE: AuthorizationRes, 2.188 s: Ongoing
  7. EVSE: AuthorizationRes, 2.547 s: Finished
  8. EV: ChargeParameterDiscoveryReq, 2.620 s
  9. EVSE: ChargeParameterDiscoveryRes, 2.698 s: FAILED_WrongChargeParameter
  10. EV: SessionStopReq, 2.830 s: ChargingSession Terminate
  11. EVSE: SessionStopRes, 2.882 s: OK
  12. both: TCP connection closed, 3.000 s and 3.030 s

Everything around the refusal is orderly. The charger offered the mode the car asked for (SQ-06) and the payment option it chose (SQ-07), every response came within 78 ms (TIM-01), and after the refusal both sides closed the session properly.

The refused request and its answer

FieldCar (ChargeParameterDiscoveryReq)Charger (ChargeParameterDiscoveryRes)
Energy transfer modeAC_three_phase_coreOffered in ServiceDiscoveryRes
Maximum currentEVMaxCurrent 16 AEVSEMaxCurrent 16 A
Minimum currentEVMinCurrent 6 ANone stated
VoltageEVMaxVoltage 400 VEVSENominalVoltage 230 V
Energy and timeEAmount 20 kWh, DepartureTime 7200 sNone stated
SchedulesMaxEntriesSAScheduleTuple 3One SAScheduleTuple, PMax 11 kW from the start
OutcomeFAILED_WrongChargeParameter, EVSEProcessing Finished, EVSENotification None

The Negotiation tool puts these side by side and finds no conflict: both sides allow 16 A, the current ranges overlap, and the requested mode was offered. The response even carries a complete schedule of 11 kW, which is 16 A on three phases at 230 V. Only the code says no.

Confirming the cause

  • The capture shows that the charger refused, not why. FAILED_WrongChargeParameter says the charger applied a rule to the car's parameters; the rule lives in the charger.
  • Candidates to check in the charger's configuration and log: a limit on EVMaxVoltage (400 V is the line to line voltage of a 230 V three phase supply, and a charger that compares it with its phase voltage might object), a minimum current, the energy request or the departure time, or three phase charging switched off although it is offered.
  • If you drive an EV simulator, change one value at a time: AC_single_phase_core instead of three phases, a lower EVMaxVoltage, no DepartureTime. The change that makes the code go away names the rule.
  • The likely party is the charger, with high confidence, because it sent the code. That answers who stopped the session. Whether the charger or the car has to change depends on the rule, which may be a correct one the car breaks.

What a fix looks like

  • If the rule is wrong or too strict, fix the charger: it should accept parameters it can serve, and it should not offer a mode it then refuses.
  • If the rule is right, the car has to send parameters that satisfy it; the charger log names the value.
  • After the fix, expect ChargeParameterDiscoveryRes with OK, then PowerDeliveryReq Start naming SAScheduleTupleID 1, and the ChargingStatus loop. An AC session, message by message follows the rest of the session, and The charger answers with a FAILED response code lists the other FAILED codes.

Sources

  • ISO 15118-2:2014, ChargeParameterDiscovery, response codes
  • SPEC.md of this tool, section 14, the demo sessions