A CHAdeMO or GB/T session stops

Reading a CAN log of a DC session that failed: which side is on the bus, the fault and stop flags, the step that timed out and the stop reason each side reported.

What you see

  • A CAN log where the session never reaches charging, or where current stops before the car is full.
  • The verdict comes from the protocol module. CHAdeMO categories: One side is missing, Battery incompatibility, Vehicle fault, Vehicle left park, Charger fault, No current delivered, Vehicle never allowed charging, Stopped without a normal stop request. GB/T categories: No handshake, Handshake failure, Vehicle error message, Charger error message, Vehicle stopped, Charger stopped, Vehicle fault, Charger fault, Charger never became ready, No current delivered.

CHAdeMO

SignalFromCheck
No frames from one side (0x100 to 0x102 from the car, 0x108 and 0x109 from the charger)The silent sideCH-01
Fault flags in 0x102: battery overvoltage, undervoltage, current deviation, high temperature, voltage deviation, charging system faultCarCH-04; verdict Vehicle fault
Flags in 0x109: charger malfunction, battery incompatibility, charging system malfunctionChargerCH-04; verdict Charger fault or Battery incompatibility
Output current above the request in 0x102ChargerCH-02
Output voltage above the battery maximum in 0x100ChargerCH-03
Current while the car's charging enabled flag is clearChargerCH-05
Different control protocol numbersEitherCH-06

A normal end shows the car's normal stop request flag or the charger's stop control flag. When current stops with neither, the verdict is Stopped without a normal stop request. The cause is then often on the analogue lines (charge sequence signals and the charge permission contact), which a CAN log does not show: log them on a scope next to the bus.

GB/T 27930

SignalWhoCheck
CHM repeated, no BHMBMSGB-01; verdict Handshake failure
CRM repeated, no BRMBMSGB-02
BCP without CMLChargerGB-03
BRO ready without CRO readyChargerGB-04; verdict Charger never became ready
BEM: the BMS reports which charger message it did not receive in timePoints at the chargerVerdict Vehicle error message
CEM: the charger reports which BMS message it did not receive in timePoints at the BMSVerdict Charger error message
BST or CST with a stop reason (target reached, fault, insulation, temperature, connector)The senderVerdict Vehicle stopped, Charger stopped or a fault
Output current above the BCL demandChargerGB-05
Measured voltage above the BMS maximumChargerGB-06
No BST or CST, or no statistics afterwardsEitherGB-07

BEM and CEM are the key to a GB/T failure: the side that sends one is reporting the other side's silence. The code dictionary lists the stop reasons, faults and timeout reports.

Bus level problems

  • CAN-01 reports gaps where the bus falls silent during a session, CAN-02 cyclic messages that drift from their period or stall.
  • Periods that wander are often gateway jitter in the logger rather than a fault; the tolerance in the profile is wide for that reason.
  • Check the bit rate (CHAdeMO runs at 500 kbit/s, GB/T 27930 commonly at 250 kbit/s) and the termination when frames are missing from one side only.

The CHAdeMO and GB/T timing and margin values in the limit profile are all flagged for verification, and the CHAdeMO byte offsets come from secondary sources.

Sources

  • CHAdeMO protocol as implemented by the analyzer's field table, offsets marked for verification
  • GB/T 27930-2015, message sequence, BEM and CEM