Worked example: a CHAdeMO charger stops with a fault flag
The chademo-stop demo read step by step: a CHAdeMO session that charges at 100 A until the charger sets its malfunction and stop flags at 12.0 s, takes its output to zero in 0.3 s, and the car withdraws and opens its contactor.
What you see
- Load the demo Charger fault stop (chademo-stop): 14 s of CAN frames in a SocketCAN pcap, five messages every 100 ms, 703 frames in all.
- Stage strip: Plug-in, Capability exchange, Vehicle ready, Contactor closed and Energy transfer passed; Stop not reached, because neither side asked for a normal stop.
- One check fails, CH-04, with one finding: the malfunction flag set at 12.022 s and kept to the end of the session, 21 frames up to 14.022 s. CAN-01, CAN-02, CH-01, CH-02, CH-03, CH-05 and CH-06 pass.
The verdict
Stopped early, Charger fault, likely party EVSE, confidence high. The explanation reads: the charger reported a malfunction at 12.0 s. The chain of evidence is CH-04.
Reading the capture step by step
- EV: VehicleStatus (0x102), 0.004 s: control protocol 2, target 400 V, charging not enabled, contactor open
- EVSE: ChargerStatus (0x109), 0.122 s: standby, connector locked
- EV: VehicleStatus, 2.004 s: charging enabled
- EV: VehicleStatus, 3.004 s: main contactor closed
- both: Current ramp, 3.1 to 5.0 s: request and output rise together by 5 A every 100 ms
- both: Steady charging, 5.0 to 12.0 s: 100 A requested and delivered at 381 V
- EVSE: ChargerStatus, 12.022 s: charger malfunction and charger stopping set, output 75 A
- EVSE: ChargerStatus, 12.122 s: 50 A, 12.222 s: 25 A
- EVSE: ChargerStatus, 12.322 s: 0 A, 0 V, standby; both flags stay set
- EV: VehicleStatus, 12.404 s: current request 0 A
- EV: VehicleStatus, 12.504 s: charging not enabled
- EV: VehicleStatus, 13.004 s: main contactor open
- Before 12 s nothing is wrong: the output follows the request within the margin of CH-02, the voltage stays inside the window of the car (CH-03), and both sides speak control protocol 2 (CH-06).
- At 12.022 s the charger sets two bits in the status byte of 0x109 in the same frame: ChargerMalfunction and ChargerStopControl. The car has not changed anything: its request is still 100 A and it reports no fault of its own.
- The charger takes the output down on its own, 25 A per frame, and is at 0 A 300 ms later. Only then does the car withdraw its request and its permission, and it opens the contactor about 1 s after the flag.
- CH-04 raises one finding for the stretch during which ChargerStatus carries the malfunction flag: it starts at the first frame with the flag and counts the frames until the flag clears, here never. CH-05 passes, because current flowed only while the car allowed it.
The flag positions come from the CHAdeMO field table of this tool, which is marked for verification: the CHAdeMO specification is not public. Check a surprising flag against the document before quoting it.
What the cause is
- The charger stopped for a fault of its own. The order of the frames shows it: the flag comes first, the output falls while the car still asks for 100 A, and the car only follows.
- The CAN frames do not say which fault. ChargerMalfunction is one bit for everything inside the charger: a power module, its cooling, its measurement, or a protection that tripped.
- This is not a normal end, which starts with NormalStopRequest from the car, as in the chademo demo. The Stop stage stays not reached for that reason.
What to fix
- Read the charger's own error log at the time of the flag, 12.0 s into the session. It names the module and the protection behind the bit.
- Repeat the session at the same current: a fault that appears after the same time at the same power points to heat or a protection threshold; one that appears at random points to a measurement or a connection.
- If the charger has several power modules, check whether the fault follows one of them.
- A CHAdeMO or GB/T session stops covers the other ways a CHAdeMO or GB/T session ends early, including the flags the car sets.
How to confirm the fix
- A session of the same length and current in which no ChargerStatus carries ChargerMalfunction, so CH-04 passes.
- The session ends with NormalStopRequest from the car and the charger going to standby: the Stop stage passes and the verdict reads Completed normally, like the chademo demo.
Sources
- CHAdeMO specification, charger status message 0x109 and its status flags
- IEC 61851-24, digital communication for DC charging, the CHAdeMO annex
- SPEC.md of this tool, FR-ENC-05, the failing demo sessions