Stage: DC pre-charge

The charger raises its output to the battery voltage the car names, so the car can close its contactors without an inrush. The messages in the three standards, the target and tolerance, the loop, and what makes it stall.

What the stage does

After the cable check the output of the charger is near zero and the battery sits at several hundred volts behind the open contactors of the car. Closing them into that difference would drive a large current through the contacts. Pre-charge closes the gap first: the car names its battery voltage as the target, the charger raises its output to it with only a small current allowed, and the car closes its contactors once the two match.

  • The target is the present battery voltage, not the end of charge voltage. It is sent as EVTargetVoltage in every request.
  • DIN SPEC 70121 and ISO 15118-2 also send EVTargetCurrent, the small current the charger may use; ISO 15118-20 sends the present battery voltage (EVPresentVoltage) instead, and EVProcessing to say when the car is done.
  • The charger reports its output as EVSEPresentVoltage in every response.
  • When the voltages match, the car closes its contactors and sends PowerDeliveryReq with ChargeProgress Start (DIN SPEC 70121: ReadyToChargeState true).

The loop

  1. EVSE: CableCheckRes, Finished: the previous stage is done
  2. EV: PreChargeReq, EVTargetVoltage the battery voltage, EVTargetCurrent small
  3. EVSE: PreChargeRes, EVSEPresentVoltage still low
  4. both: more PreCharge pairs, the output climbs with each answer
  5. EVSE: PreChargeRes, EVSEPresentVoltage within tolerance of the target
  6. EV: PowerDeliveryReq, ChargeProgress Start, contactors of the car closed
DIN SPEC 70121 and ISO 15118-2ISO 15118-20
RequestPreChargeReq: DC_EVStatus, EVTargetVoltage, EVTargetCurrentDC_PreChargeReq: EVProcessing, EVPresentVoltage, EVTargetVoltage
ResponsePreChargeRes: ResponseCode, DC_EVSEStatus, EVSEPresentVoltageDC_PreChargeRes: ResponseCode, EVSEPresentVoltage
End of the loopThe car stops repeating and sends PowerDeliveryReqThe car sets EVProcessing Finished, then sends PowerDeliveryReq

Target, tolerance and timers

ValueLimit profile keyProfile default
Largest difference between output and target that counts as reacheddc.prechargeToleranceV20 V
V2G_EVCC_PreCharge_Timeout, first request to the last answerdc.prechargeTimeoutS7 s
Each PreCharge response (V2G_EVCC_Msg_Timeout, general case)tim.msgTimeoutS2 s
From a response to the next requesttim.sequenceTimeoutS60 s

All four values are flagged for verification in the limit profile. The tolerance is common practice for IEC 61851-23 pre-charge, and the pre-charge timeout comes from secondary sources. The car applies its own tolerance, which is not in the capture.

What usually breaks

  • The output levels off below the target: a power module range, a voltage limit set lower than the range the charger announced, or a converter that cannot regulate the small current at that voltage.
  • EVSEPresentVoltage is stale: the output does reach the target, but the charger reports a number it does not update. A value that does not change over many answers is the hint.
  • The output settles just outside the tolerance of the car and the car keeps waiting until its timer runs out.
  • The target of the car does not match its real battery voltage, for example a sensor offset. Pre-charge passes, then a current spike or a fault follows right after the contactors close.
  • The output overshoots, and the car or the charger stops to protect the battery.

The symptom page is DC session stalls in CableCheck or PreCharge; Worked example: pre-charge stalls at 312 V reads a stalled pre-charge message by message.

In the analyzer

  • Stage strip: Pre-charge, on DC sessions, between Cable check and Energy transfer.
  • DC-01 reads the last PreChargeRes or DC_PreChargeRes. When no PowerDelivery Start follows, it reports how far the output was from the target and whether the loop ran past dc.prechargeTimeoutS, and names the charger when the output never got close or the car when it did and still stopped.
  • The Timers tool shows the pre-charge loop against its limit; the Negotiation tool shows whether the target lies inside the voltage range the charger announced.
  • Verdict: Pre-charge failed, when the session ends in this stage.

Sources

  • DIN SPEC 70121:2014-12, PreCharge request and response
  • ISO 15118-2:2014, PreCharge request and response, timing tables
  • ISO 15118-20:2022, DC_PreCharge request and response
  • IEC 61851-23, pre-charge of a DC charging station