How the charging standards fit together

Conductive charging is described by a stack of standards: the connector, the charging system and its Control Pilot, the link that carries data, the charging protocol itself and the backend behind the charger. This page places each one in that stack and says which one answers which test question.

The layers

Every conductive session crosses the same layers, whatever the region. The connector carries the power and a few signal contacts. The charging system standard says what the charger and car must do electrically and for safety, including the analogue Control Pilot or its equivalent. A link layer carries data over one of those signal contacts: powerline on the pilot wire for CCS and NACS, CAN on separate pins for CHAdeMO and GB/T. The charging protocol on top negotiates limits, authorisation and the energy transfer. Behind the charger, a backend protocol reports sessions and meter values to the operator.

  • Physical and connector: IEC 62196 (parts 2 and 3), SAE J1772, GB/T 20234, SAE J3400.
  • Charging system and Control Pilot: IEC 61851-1 (general and AC), -21-1 and -21-2 (EMC of on-board and off-board chargers), -23 (DC stations), -24 (DC digital communication), -25 (DC with protection by electrical separation).
  • Powerline link and pairing: ISO 15118-3 (HomePlug Green PHY and SLAC). ISO 15118-8 (Wi-Fi) and ISO 15118-10 (single pair Ethernet) are the alternatives for wireless and megawatt charging.
  • High level communication over IP: DIN SPEC 70121, ISO 15118-2, ISO 15118-20.
  • CAN based DC protocols: CHAdeMO and GB/T 27930.
  • Backend: OCPP between charger and operator, OCPI and OICP for roaming between operators and mobility providers, IEC 63110 and IEC 63119 as the IEC work on the same interfaces.
  • Plug and Charge PKI: the certificate hierarchy defined by ISO 15118-2 and -20 and run by root certificate authorities, spanning car, charger and backend.

One table per region

LayerEurope/US (CCS)JapanChinaNorth America (J3400)
ConnectorIEC 62196-2 Type 2 and -3 configuration FF (CCS2); SAE J1772 Type 1 and -3 configuration EE (CCS1)IEC 62196-3 configuration AA (CHAdeMO) for DC, Type 1 for ACGB/T 20234.2 (AC) and GB/T 20234.3 (DC), IEC 62196-3 configuration BBSAE J3400, one inlet for AC and DC
Charging system and safetyIEC 61851-1 and IEC 61851-23 (system C); SAE J1772 in the USIEC 61851-23 (system A) and the CHAdeMO specificationGB/T 18487.1 and IEC 61851-23 (system B)SAE J1772 electrical behaviour, J3400 for the coupler
Pilot and detectionControl Pilot PWM and PP resistor (IEC 61851-1, J1772)Analogue start, permission and proximity lines next to CANCC1 and CC2 detection circuits of GB/T 18487.1Control Pilot PWM as in J1772
LinkHomePlug Green PHY on CP, SLAC (ISO 15118-3)CAN, 500 kbit/sCAN with J1939 addressingHomePlug Green PHY on CP, SLAC (ISO 15118-3)
Charging protocolDIN SPEC 70121, ISO 15118-2, ISO 15118-20 (IEC 61851-24 Annex C)CHAdeMO (IEC 61851-24 Annex A)GB/T 27930 (IEC 61851-24 Annex B)DIN SPEC 70121, ISO 15118-2, ISO 15118-20
BackendOCPP, OCPI, OICPOCPP and national systemsNational platforms, OCPPOCPP, OCPI
Tool modulehlc (DIN, ISO 15118-2, ISO 15118-20)can (CHAdeMO)can (GB/T 27930)hlc, as for CCS

The GB/T CAN bus rate (commonly 250 kbit/s) and the GB/T 18487.1 detection circuit names are given from secondary sources. Check them against the edition you test to.

ChaoJi and the Megawatt Charging System add two more columns in the future: ChaoJi keeps CAN but changes the connector, MCS keeps ISO 15118-20 but replaces powerline with single pair Ethernet.

Which standard answers which test question

Question from the labStandard to openWhat to captureChecks in this tool
Is the pilot signal right: levels, frequency, duty cycle?IEC 61851-1 Annex A, SAE J1772Oscilloscope or CP logger traceCP-01 to CP-03, CP-10
Does the car pair with the right charger?ISO 15118-3Powerline sniffer capture from before plug inSL-01 to SL-09
Which protocol did they agree on, and why not the newer one?ISO 15118-2 or -20, clause on the app handshakeCapture from SDP onwardsHS-01 to HS-03
Are the messages in the right order and answered in time?DIN SPEC 70121, ISO 15118-2, ISO 15118-20Full session captureSQ-01 to SQ-11, TIM-01 to TIM-06
Why does TLS fail or which certificate is wrong?ISO 15118-2 or -20 security clausesCapture plus key logTL-01 to TL-08, PK-01, PK-02
Does the DC charger check insulation and precharge correctly?IEC 61851-23 and its system annexSession capture plus voltage and current on the DC linesSQ-05 for the response codes; the electrical part needs a scope
Does a CHAdeMO or GB/T charger follow the car's request?IEC 61851-24 Annex A or B, CHAdeMO, GB/T 27930CAN logCH-01 to CH-06, GB-01 to GB-07
Will this plug and cable fit and carry the current?IEC 62196-2 and -3, SAE J3400Inspection, PP resistor measurementPP-01
Why did the backend show a fault for this session?OCPPOCPP log next to the capturenone, see the OCPP page for correlation
Is the implementation conformant?ISO 15118-4 and -5, DIN SPEC 70122A conformance test system, not a passive capturenone, this tool does not certify

Why the layers matter when debugging

A failure always has a lowest layer. If the pilot never reached 5 percent duty, SLAC cannot start; if SLAC did not match, no IP traffic exists; if the handshake refused every protocol, no session messages follow. When a session never reached the charging protocol, the tool's verdict looks at the layers below (SLAC, SDP, TCP, TLS) and says where the session stopped, so a missing CurrentDemand is not blamed on the protocol when the link never came up.

When a report blames the protocol, first confirm the layers below it were healthy in the capture. Many protocol symptoms (timeouts, lost connections) start as a powerline or pilot problem.

Sources

  • IEC 61851 series, parts 1, 21-1, 21-2, 23, 24 and 25
  • IEC 62196 series, parts 1, 2 and 3
  • ISO 15118 series, parts 1 to 5, 8, 10 and 20
  • DIN SPEC 70121:2014-12
  • SAE J1772, SAE J3400, North American couplers
  • GB/T 18487.1, GB/T 20234, GB/T 27930, Chinese charging system, couplers and DC communication
  • OCPP 1.6 and 2.0.1, Open Charge Alliance