How EV charging is tested

The kinds of testing a car, a charger and a backend go through: communication conformance, protocol certification, safety and type testing, EMC, interoperability events, OCPP certification, metrology, cybersecurity and field reliability, and who does each.

Many tests, different questions

A charger that reaches the market has been tested many times, and each test answers a different question. Is it safe to touch and to install? Does it disturb the radio spectrum? Does it speak the protocol as the standard writes it? Does it work with the cars that will plug into it? Does its backend understand it? Is the energy it bills measured correctly? Can an attacker take it over? And, after it is installed, does it keep working?

  • Conformance testing checks one product against a standard. A test system plays the other side and provokes the reactions the standard requires.
  • Certification adds a body that checks the process and issues a certificate, a listing or a type-examination certificate.
  • Interoperability testing puts real products together. It finds what conformance misses: two readings of the same clause, timing that is legal on both sides but does not fit.
  • Field monitoring measures what drivers experience: sessions that start, sessions that finish, and the errors in between.

Test levels at a glance

LevelWhat is testedBy whomStandard or programResult
CCS communication conformance, first generationEVCC or SECC against ISO 15118-2 and -3, or against DIN SPEC 70121Test labs and manufacturers, with a conformance test systemISO 15118-4 (layer 3 and up), ISO 15118-5 (layers 1 and 2), DIN SPEC 70122Test report against the PICS of the product
CCS communication conformance, ISO 15118-20EVCC or SECC against ISO 15118-20Test labs and manufacturersISO 15118-21:2025 (common), ISO/PAS 15118-23:2026 (DC), ISO 15118-22 (security, a work item)Test report
CHAdeMO certificationCharger against the CHAdeMO specificationCertification bodies registered by the CHAdeMO AssociationCHAdeMO certification schemeCertification of the charger
GB/T conformance and interoperabilityCharger to BMS protocol; supply equipment interoperabilityTest labs in ChinaGB/T 34658, GB/T 34657.1Test report
Safety and type testingProtection against shock, fire and faults; the charging functions of the Control PilotAccredited labs and certification bodies (NRTLs in North America)IEC 61851-1, IEC 61851-23; UL 2594 (AC), UL 2202 (DC)Type test report, certification or listing
EMCEmissions and immunity of the charger, and of the car while chargingEMC labsIEC 61851-21-2 (off-board), IEC 61851-21-1 (on-board)Test report
Interoperability eventsReal cars against real chargersManufacturers together, hosted by associations and national labsCharIN Testivals; ChargeX EV-EVSE Interoperability Test PlanFindings per pairing, no certificate
Backend protocolCharging station or CSMS against OCPPLabs authorised by the Open Charge Alliance, with OCTTOCPP 1.6 and 2.0.1 certificationOCA certificate naming the certification profiles
MetrologyEnergy measurement and the data used for billingNational metrology institutes, notified bodies, weights and measures authoritiesEichrecht (Germany), MID (EU), NIST Handbook 44 section 3.40 (US)Type-examination certificate, type evaluation
CybersecurityNetwork security, data protection, fraud resistance of the chargerNotified bodies and test labs; the manufacturer for self assessmentEU RED delegated regulation 2022/30 with EN 18031; UK Smart Charge Points Regulations 2021Assessment report, declaration of conformity
Field reliabilitySessions in daily useOperators, programs that fund charging, national labsChargeX KPIs and Minimum Required Error Codes; funding program rulesUptime and success figures

Communication conformance

For the first generation of ISO 15118, two parts carry the tests. ISO 15118-4:2018 specifies an abstract test suite for an EVCC or SECC that implements ISO 15118-2, written in TTCN-3 for the network layer and above. ISO 15118-5:2018 does the same for the physical and data link layers of ISO 15118-3, including basic signalling. Both split their tests into capability tests (does the product have what it claims) and behaviour tests (does it act as required over the range of its capabilities).

For ISO 15118-20, the tests are split by topic. ISO 15118-21, published in 2025, covers the requirements common to all energy transfer types and describes its test cases in tables for layers 3 to 7. ISO/PAS 15118-23, approved in April 2026, adds the DC specific requirements on the same test architecture. ISO 15118-22 on security (Plug and Charge, XML signatures, TLS error cases) is an approved work item, and a new edition of part 21 is registered as a work item too (ISO catalogue, September 2026).

DIN SPEC 70122:2018 is the conformance test for DIN SPEC 70121. It covers SLAC, SDP, V2GTP, the protocol handshake and the messages of setup, charging loop and termination.

CHAdeMO runs its own certification. A charger maker must be a regular member of the CHAdeMO Association, hands its documentation to one of the registered certification bodies and has the protocol tested there. In China, GB/T 34658 is the conformance test for the charger to BMS protocol of GB/T 27930, and GB/T 34657.1 the interoperability test for supply equipment; both got 2025 editions that apply from 1 March 2026. Commercial test systems implement it: Keysight, for example, announced test case software for GB/T 34657.1. Part 2, GB/T 34657.2-2017, is the interoperability test for the vehicle side, and test system makers such as Keysight and ITECH offer test software for it too.

Which bodies CHAdeMO lists today, and whether GB/T 34657.2 has a newer edition than 2017, were not confirmed from a primary page for this article. Check them with the CHAdeMO Association and the SAC catalogue.

Safety, EMC, metrology and security

  • Safety and function: IEC 61851-1 sets the general rules of conductive charging, including the Control Pilot, and IEC 61851-23 adds the DC charging station. In North America, UL 2594 covers AC supply equipment up to 1 000 V AC (cord sets, wall boxes, fixed stations) and UL 2202 covers off-board DC chargers. More in Safety and type approval of chargers and cars.
  • EMC: IEC 61851-21-2:2018 covers off-board equipment for modes 1 to 4. IEC 61851-21-1:2017 covers the on-board charger, tested on the complete vehicle or as a component. Both editions now contain only EMC tests; earlier editions mixed in other electrical tests.
  • Metrology: in Germany, a charger that bills by energy needs a Module B type-examination certificate as the first step under the calibration law. In the EU, meters fall under the Measuring Instruments Directive, and a 2025 proposal adds an annex for EVSE measuring systems. In the US, NIST Handbook 44 section 3.40 applies where energy is sold by measurement, and NTEP accepts a charger for type evaluation only after safety certification by an NRTL. More in Billing and measurement testing.
  • Cybersecurity: since 1 August 2025, radio equipment placed on the EU market, chargers with a radio included, must meet the cybersecurity requirements added to the Radio Equipment Directive, assessed against EN 18031. In Great Britain, the Smart Charge Points Regulations 2021 set security requirements for smart charge points from 30 December 2022. More in Security testing of chargers.

Interoperability, backend and the field

CharIN Testivals bring cars and chargers together for days of pairings; see Interoperability test events. In the US, the ChargeX Consortium (national labs with industry, June 2023 to September 2025) wrote the EV-EVSE Interoperability Test Plan. Version 2.0 of July 2025 sorts its cases into baseline functionality and safety tests (authentication methods and timeouts, protocol priority selection, idle faults, session initialization, power transfer) and advanced tests (two cars on one dispenser, seamless retry). At the June 2024 Testival, ChargeX ran eight of these scenarios in the last 30 minutes of each 90 minute slot.

For the backend, the Open Charge Alliance certifies OCPP implementations. The device runs the conformance tests of the OCPP Compliance Testing Tool (OCTT) at an authorised lab; for OCPP 2.0.1 these are DEKRA, DNV and the Korea Smart Grid Association. The certificate names the certification profiles passed. See OCPP certification and Backend, Plug and Charge and payment test cases.

In the field, ChargeX published 26 Minimum Required Error Codes, prefixed CX, that were later codified in SAE J2953/3, and a calculator for interim reliability KPIs from OCPP 2.0.1 logs. See Reliability of public charging: what field data says.

Who does what

PartyRole in testing
ManufacturerDevelops against the standard, runs its own test plan and a pre-test, writes the PICS and PIXIT, signs the declaration of conformity
Test labRuns the test suite on the product with its own test system and writes the report
Certification bodyIssues the certificate or listing: OCA for OCPP, the registered bodies for CHAdeMO, NRTLs for UL standards, notified bodies for EU directives, PTB for Eichrecht
Protocol ownerWrites the test specification or the tool and authorises the labs (OCA, CHAdeMO Association, CharIN)
OperatorTests a product before buying it, accepts each site, monitors sessions and faults
Regulator or funderMakes some of the above mandatory, and sets uptime rules for funded chargers

Reading on

In this tool

The analyzer is passive: it judges a capture of two real products, and does not play either side. That makes it useful beside every test level above. It explains a failed conformance run if the test system exports a capture, it keeps the evidence of each pairing at an interoperability event, and its command line runner (v2g-analyze --junit) turns a folder of lab captures into a test report for a regression run. A pass here is not a certificate: an option that was not used or a fault that did not happen is not seen. See Session end verdicts.

Sources