The car side of charging

What sits behind the car's inlet: the pilot and proximity circuits, the communication controller, the onboard charger, the battery management system and the contactors, and how the car decides between AC and DC.

The inlet: pilot and proximity circuits

PartValueEffect
Diode in series with the pilotblocks the negative halfThe -12 V level stays; a short to PE would pull it to 0 V
Permanent resistor (R3)2.74 kilohmWith the charger's 1 kilohm source: +9 V, state B
Switched resistor (R2) via S21.3 kilohmIn parallel with R3: +6 V, state C, energy wanted
R2 for ventilation270 ohmGives +3 V, state D, rarely used
PP measuring circuitmaker specificDetects the plug, reads the cable rating on Type 2, blocks driving away

Closing S2 is the car's only analogue way to ask for energy. On AC with ISO 15118 the car closes it only after the charger answered PowerDeliveryReq Start (CP-07) and opens it after Stop (CP-08). On DC the car closes S2 earlier, before CableCheck, and the energy flows through the DC pins.

EVCC, onboard charger and battery

  • EVCC: the communication controller, with a Green PHY modem (the QCA7005 is common) coupled onto the pilot. It runs SLAC, SDP, TLS and the V2G messages, and passes set points to and from the battery management system.
  • Onboard charger (OBC): converts AC to the battery voltage. Common ratings are 3.7 or 7.4 kW single phase (16 or 32 A at 230 V), 11 kW three phase (16 A per phase) and 22 kW three phase (32 A). North American cars charge from 240 V single or split phase, commonly up to 48 A.
  • Battery management system (BMS): measures every cell voltage and temperature, estimates the state of charge and sets the current the battery can take now. That limit becomes EVTargetCurrent on DC and the car's own draw on AC.
  • Main contactors: connect the battery to the high voltage bus. The DC inlet has its own contactors, or shares the main ones, depending on the design.

An 11 kW OBC on a 32 A three phase wallbox draws 16 A per phase: the car, not the charger, is the limit, and the capture shows a duty cycle for 32 A with 16 A measured. That is correct behaviour; PW-01 only fails on current above the limit.

Phase switching: a wallbox that follows solar surplus can switch between one and three phases. IEC 61851-1 has no message for it, so wallboxes stop the current, switch, and resume, often passing through state B or a short state F or E. Some cars need a new plug in or refuse to restart after a changed phase count.

How individual cars react to a phase change is field experience, not specified behaviour; test the car you care about.

DC pre-charge and welding check from the car's view

  1. EV: CableCheckReq, the car's DC contactors are open; the charger tests the cable
  2. EV: PreChargeReq, EVTargetVoltage is the battery voltage, EVTargetCurrent a few amperes at most
  3. EVSE: PreChargeRes, EVSEPresentVoltage approaches the target
  4. EV: PowerDeliveryReq, Start; the car closes its contactors once the voltages match
  5. EV: CurrentDemandReq, the charge loop
  6. EV: PowerDeliveryReq, Stop; the charger ramps down, the car opens its contactors
  7. EV: WeldingDetectionReq, repeats; the car watches EVSEPresentVoltage fall
  • The car closes its contactors only when the charger output is close to the battery voltage. Closing across a large difference would give an inrush that damages the contacts.
  • Welding check: after Stop the car opens its contactors and the charger reports the voltage at its output. If the voltage stays at battery level, a contactor is welded. CHAdeMO and GB/T have equivalent steps with the charger checking its output voltage before unlocking.
  • A car that never gets the voltage it asked for in pre-charge stops the session; the troubleshooting page on pre-charge covers that case.

The pre-charge current limit (commonly 2 A) and the tolerance within which the car accepts the pre-charge voltage are to be checked against IEC 61851-23 and the car maker's specification; the PreCharge timeout of DIN SPEC 70121 and ISO 15118-2 is commonly quoted as 7 s.

Wake up and the choice between AC and DC

  • A parked car sleeps with only its 12 V system alive. Plugging in (the PP change) or a pilot change (A to B) wakes the EVCC. The charger's short E or F pulse when SLAC does not start (CP-05) exists to wake a car that fell asleep again.
  • The plug decides first: a combo plug fills the DC pins, which the car detects. A Type 1 or Type 2 plug alone means AC.
  • The pilot decides next: a nominal duty cycle without 5 percent means basic AC charging, no communication. A 5 percent duty cycle means the car must start SLAC.
  • With communication, the charger lists the energy transfer modes it offers (ServiceDiscoveryRes in ISO 15118-2, the service list in ISO 15118-20) and the car picks one in ChargeParameterDiscoveryReq or ServiceSelectionReq. SQ-06 checks that the car picked one that was offered.

What the car logs

An EVCC log is maker specific, but most record the same things: pilot state and duty cycle, SLAC results with the attenuation per charger that answered, the SDP answer, the negotiated protocol, every V2G message with timestamps, and the error the car reported. On DC that error travels in DC_EVStatus as EVErrorCode; the code dictionary explains each value. A car log and a capture from the cable together are the best way to tell whether a message was sent and not received or never sent at all.

Sources

  • IEC 61851-1:2017, Annex A, vehicle side of the Control Pilot circuit
  • ISO 15118-3:2015, EVCC, PLC and SLAC
  • ISO 15118-2:2014, energy transfer modes, WeldingDetection
  • IEC 61851-23, DC charging sequence