Why ISO 15118-20 Interoperability Testing Needs More Than Output Power Verification
Date:
09 Nov,2026
Share:
An EV charger can show the correct voltage, current and power on a meter—and still fail to charge a real vehicle reliably. This is the central reason why ISO 15118-20 interoperability testing must go beyond conventional output power verification.
For many years, EVSE factory tests concentrated on electrical performance: output voltage regulation, current accuracy, power capability, insulation, protection and metering. These checks remain essential. But modern charging is no longer only a power-delivery process. It is an interaction between a vehicle, a charger, a connector, a control pilot circuit, a communication stack, security credentials and, increasingly, a charging-management platform.
ISO 15118-20 expands the role of vehicle-to-grid communication. It supports functions such as Plug & Charge, scheduled and bidirectional charging, and richer energy-management messages. As a result, a charger that is electrically correct but weak in communication behavior can create failed sessions, repeated reconnection attempts, delayed billing, vehicle incompatibility or difficult field-service cases.
Output power is necessary—but it is not the whole acceptance test
Traditional output testing answers important questions:
Can the charger deliver the requested voltage and current?
Is output ripple within the design target?
Does it stop safely under over-voltage, over-current, over-temperature or emergency-stop conditions?
Is the energy meter reading accurate?
These checks do not prove that the charger can complete a charging session with different vehicle implementations. A vehicle may connect successfully, then fail during session setup. It may reject a certificate chain, time out during message exchange, misinterpret a charging schedule or react unexpectedly after a communication interruption.
That is why an EVSE needs two complementary test layers: electrical performance validation and protocol/interoperability validation.
What should an ISO 15118-20 interoperability test cover?
A practical test program should reproduce the journey of an actual charging session rather than examine only isolated signals. Typical test areas include:
Connection and state transitions. Verify connection detection, CP/PP behavior where applicable, locking, session initiation and normal termination.
Communication establishment. Confirm that the EVSE and vehicle-side emulator negotiate the expected communication path and recover correctly from retries or timeouts.
Plug & Charge authentication. Test certificate installation, validation, authorization success, invalid certificates and authorization failures.
Charge parameter exchange. Check how the charger processes requested voltage, current, power limits and schedule information.
Dynamic charging control. Verify response to changing limits, pause/resume commands, derating and smart-charging instructions.
Abnormal-condition behavior. Simulate communication loss, connector interruption, emergency stop, insulation or safety fault, and confirm a controlled transition to a safe state.
Session records and backend coordination. Confirm that charging-session data is complete and consistent for operation, billing and maintenance.
Why interoperability failures are expensive in the field
A lab-only output test may allow a hidden protocol issue to reach installation. Once deployed, the problem is often described simply as “the charger will not charge this vehicle.” The root cause may instead be a timing sequence, unsupported message option, certificate condition, software-version interaction or recovery behavior.
These faults are costly because they are intermittent and vehicle-specific. Technicians may need to visit site several times; operators lose charging availability; and manufacturers face warranty exposure. Testing against multiple realistic vehicle behaviors before release is significantly more efficient than debugging after deployment.
A better test architecture
The most effective approach combines a programmable load or vehicle-side power interface with communication simulation, safety-signal control and automated data capture. The test platform should be able to set electrical demand, emulate changing battery conditions, trigger communication events and store synchronized evidence from the entire session.
For AC EVSE, this commonly includes CP, PE and proximity-related checks, PWM behavior, metering verification and a vehicle simulator. For DC EVSE, the platform must additionally address high-voltage/current power control, connector signals, insulation-related checks and DC communication behavior. The exact configuration depends on connector standard, regional market and rated power.
From “power output OK” to “charging session proven”
For EVSE manufacturers, the goal is not simply to prove that a charger can energize its output. The goal is to prove that it can start, control, protect, record and end a charging session reliably with the vehicles and systems it will meet in the market.
IUXPOWER EVSE test solutions support electrical verification, controllable charging conditions and repeatable acceptance or maintenance testing. When planning an ISO 15118-20 validation program, start by mapping the target markets, connector types, vehicle compatibility requirements and backend interfaces. This turns interoperability testing into a defined release gate rather than a late-stage troubleshooting task.
More News
Landline
Mobile/WeChat
Mobile/WeChat
Add：Building 17, Zhixin Zhizao Valley Industrial Park, Yuexi Town, Ninghai City, Zhejiang Province, China
