Learn
The EV charging standards explained: ISO 15118, DIN 70121, IEC 61851, CHAdeMO, GB/T, message flows and troubleshooting.
- How the charging standards fit together
- ISO 15118-20: the second generation
- ISO 15118-20: TLS 1.3 and certificates
- ISO 15118-20: control modes, BPT and power profiles
- ISO 15118-2: the first generation application layer
- DIN SPEC 70121: DC charging, the early CCS protocol
- ISO 15118-3: powerline communication and SLAC
- IEC 61851-1: the Control Pilot
- HomePlug Green PHY: powerline on the Control Pilot
- SDP and V2GTP: finding the charger and framing messages
- The app protocol handshake
- TLS in charging captures
- EXI: how V2G messages are encoded
- A DC session, message by message
- An AC session, message by message
- Bidirectional power transfer in ISO 15118-20, message by message
- Stage: SLAC matching
- Stage: DC cable check and isolation test
- Stage: DC pre-charge
- Stage: PowerDelivery and the energy transfer loop
- Stage: ending a session
- CHAdeMO: DC charging over CAN
- GB/T 27930: the Chinese DC protocol
- SAE J1939 on a charging bus
- IEC 61851-23: DC charging stations
- IEC 61851-24: digital communication for DC charging
- IEC 62196: plugs, sockets, connectors and inlets
- ISO 15118-1: the parts and the use cases
- ISO 15118-8: wireless communication
- Conformance testing: ISO 15118-4, -5 and Testivals
- SAE J1772: the North American coupler and pilot
- SAE J2847: messages for smart, DC and reverse power charging
- SAE J3400: the NACS coupler
- MCS: the Megawatt Charging System
- OCPP: the charger's link to its backend
- ChaoJi and CHAdeMO 3.0
- Troubleshooting by symptom
- Car plugged in, no SLAC match
- SLAC matched, but no SDP answer or TCP connection
- The TLS handshake fails
- No common protocol in the app handshake
- The charger answers with a FAILED response code
- DC session stalls in CableCheck or PreCharge
- The session stops during charging
- Communication works but no current flows
- Charging is slower than expected
- A CHAdeMO or GB/T session stops
- Every timer and timeout
- Control Pilot problems
- A weak or disturbed powerline link
- The session stops at authorization
- The session does not end cleanly
- Worked example: SLAC that never matches
- Worked example: the car rejects the charger certificate
- Worked example: pre-charge stalls at 312 V
- Worked example: charge parameters refused
- Worked example: the cable check fails
- Worked example: the charger refuses the TCP connection
- Worked example: a CHAdeMO charger stops with a fault flag
- Worked example: the BMS stops a GB/T session with BST
- Worked example: the backend rejects the card
- Worked example: the charger certificate has expired
- Worked example: discharge above the target in ISO 15118-20
- Inside a charger
- Isolation monitoring and CableCheck
- Energy metering and signed meter values
- Connectors compared
- The car side of charging
- Why a charging curve looks the way it does
- Bidirectional charging: V2G, V2H, V2L
- Plug and Charge and its PKI
- Certificate lifecycle: validity, renewal and revocation
- A short history of conductive charging standards
- Who is who in charging standards
- OCPP 2.0.1 and ISO 15118: the backend behind the cable
- Measured current, permitted current and the cable
- Session end verdicts
- NACS, MCS, OCPP and friends
- Physical values: how numbers travel in V2G messages
- How the car sets its limits
- Recording a charging session for analysis
- Limit profiles: the numbers behind every check
- How EV charging is tested
- Anatomy of a test case
- AC test cases, worked
- DC test cases, worked
- Backend, Plug and Charge and payment test cases
- Test equipment for charging
- Safety and type approval of chargers and cars
- Interoperability test events
- OCPP certification
- Billing and measurement testing
- Security testing of chargers
- Open source in EV charging: a map
- Testing OCPP implementations
- ChargeX customer KPIs from OCPP logs
- Signed meter values and OCMF
- OCPI: roaming between charging networks
- The ChargeX EV-EVSE Interoperability Test Plan
- Fault injection on the Control Pilot and Proximity Pilot
- Grid code testing of bidirectional chargers
- CharIN Testivals and the first public test data
- Europe: AFIR, Type 2, CCS2 and ISO 15118
- China: GB/T charging, CCC certification and the largest charging network
- Japan: CHAdeMO, Type 1 and the 300,000 port target
- United Kingdom: smart charge points, the Public Charge Point Regulations and Type 2 with CCS2
- North America: J1772, CCS1, J3400 and the NEVI standards
- Latin America: Type 2 and CCS2 in Brazil, Chile, Colombia, Argentina, Uruguay and Costa Rica
- South Korea: Combo 1, KC certification and smart control chargers
- India: from Bharat chargers to CCS2, IS 17017 and PM E-DRIVE
- Southeast Asia: Type 2 and CCS2 from Singapore to the Philippines
- Australia and New Zealand
- Middle East and Africa
- Charging around the world
- Kinds of chargers
- Makers of chargers and charging controllers
- Charging software stacks
- Reliability of public charging: what field data says
- Home charging
- Workplace and destination charging
- Depot charging for bus, van and truck fleets
- Highway and urban fast charging hubs
- Heavy duty trucks and the Megawatt Charging System
- Bidirectional charging: V2H, V2B, V2G and V2L in practice
- Smart charging: schedules, limits and grid signals
- Payment, roaming and Plug and Charge