Communication works but no current flows
The charging loop runs, the messages look fine, and the meter does not move: the car never switched to state C, the charger never closed its contactor, or a limit is zero.
What you see
- PowerDelivery Start was answered OK, ChargingStatus or CurrentDemand requests repeat, and the meter reading in the responses stays the same.
- In the Power tab (with a Control Pilot log that carries currents) the current stays at zero.
Likely causes on AC
| Cause | Who | How to confirm in the capture |
|---|---|---|
| The car never switches to state C after PowerDeliveryReq Start | EV | The CP state lane stays at B; CP-07 compares the B to C change with PowerDeliveryReq Start |
| The charger does not close its contactor after state C | EVSE | State C in the CP lane, zero current, and no phase voltage if the log has one |
| A current limit of zero: EVSEMaxCurrent zero or very low, or a schedule whose PMax is zero | EVSE | AC_EVSEChargeParameter in ChargeParameterDiscoveryRes and the SAScheduleList |
| A nominal duty cycle that allows no current: the charger left the 5 percent window for a value between 7 and 8 percent, or below 3 percent | EVSE | Duty % lane; with digital communication the lower of the PWM value and EVSEMaxCurrent applies |
| The residual current device tripped | EVSE | RCD true in the AC EVSE status |
| The on-board charger does not start, or draws only on a phase that is not energised | EV | Currents per phase in the Power tab |
Likely causes on DC
| Cause | Who | How to confirm in the capture |
|---|---|---|
| The car asks for no current: EVTargetCurrent zero, EVReady false (cold battery, a car fault) | EV | CurrentDemandReq fields |
| The charger does not deliver what was asked | EVSE | EVSEPresentCurrent near zero while EVTargetCurrent is not; DC_EVSEStatusCode other than EVSE_Ready; limit achieved flags set |
| A power or current limit of zero in the charger's limits | EVSE | EVSEMaximumCurrentLimit and EVSEMaximumPowerLimit in the loop responses |
What to check in this tool
- CP state and Duty % lanes around PowerDelivery Start. The alignment of the Control Pilot log with the capture has to be right for CP-07 and PW-02 to mean anything.
- Power tab: measured current and the permitted current at each moment, with the limit that binds.
- Message tab: EVSEMaxCurrent, EVMaxCurrent, the schedule, and the status fields of the loop responses.
- Checks: CP-07, CP-08, PW-01 to PW-03 and SQ-08.
Fixes that usually work
- Car: confirm the software switches S2 within 250 ms of sending PowerDeliveryReq Start.
- Charger: confirm the contactor is commanded on state C, and check its auxiliary contact and the RCD.
- Check where the zero limit comes from: a load management setting, a backend profile or an empty schedule.
- For a car that draws on one phase only, check which phase the charger feeds first.
The allowed delay between PowerDeliveryReq Start and the B to C change (cp.transition.maxDelayAfterPowerDeliveryS, 250 ms) is flagged for verification in the limit profile.
Sources
- IEC 61851-1:2017, Tables A.6 and A.8
- ISO 15118-2:2014, AC and DC charge parameters