Applications / EV charging EMC testing
EV and EVSE EMC Testing during Charging
Electromagnetic compatibility (EMC) testing checks how equipment behaves around electrical disturbances. Keep charging communication observable while the vehicle or charging station is tested in the EMC chamber.
The core test question
Did the DUT react to the EMC condition, or did the charging setup fail for another reason?
Charging is a closed-loop interaction. A protocol trace alone cannot prove that the pilot state, power path, communication sequence and DUT response remained valid when the condition was applied.
The method begins with the DUT and acceptance decision. It then defines the charging counterpart, required state, chamber boundary and evidence channels against the agreed test requirements.
One method. Two DUT directions.
Test the vehicle side or charging-station side without changing the measurement and evaluation method.
The DUT changes. The need for an operational counterpart, a defined chamber boundary and a common time base does not.

EV, OBC or EVCC under stress
Place the complete vehicle, charging inlet, onboard charger or vehicle-side controller in the EMC environment. Keep the EVSE (electric vehicle supply equipment, or charging station) counterpart, control and analysis outside.
- Vehicle-side DUT and applicable ports are explicit
- Real EVSE or EVSE simulation remains operational
- Pilot states, protocol and vehicle reaction remain attributable
EVSE, module or SECC under stress
Place the charging station, charging module or supply-equipment controller in the chamber. Keep the EV simulator, control and analysis outside.
- EVSE-side DUT and operating mode are explicit
- Real EV or EV simulation remains operational
- Communication, state and charger response remain attributable
The standard defines the DUT and acceptance. The optical path preserves the charging interaction.
Map the document before the hardware
Vehicle, off-board charging equipment, regulatory approval and AC power quality use different scopes and laboratory responsibilities. State the exact document, edition, DUT mode and project-specific acceptance criteria before configuring the boundary.

Vehicle and onboard-charger EMC
Applies to the onboard charging unit, either in the complete EV or as an electronic subassembly, while conductively connected to the supply.
Off-board charging-equipment EMC
Covers off-board conductive charging equipment and defines ports, operating modes, test setups and limits for the EVSE-side route.
Vehicle and ESA approval context
Use the applicable series of amendments, revision and approval route. The short name “ECE R10” is not a complete project definition.
Harmonics, voltage changes and flicker
These are separate power-quality routes where applicable. Grid sources, analyzers, impedances and the final assessment remain dedicated laboratory functions.
EMC Link does not replace antennas, disturbance generators, artificial networks, power analyzers, chamber procedures or the laboratory verdict. It preserves the selected charging-specific signal path across the boundary.
One charging configuration. Defined EMC conditions.
Establish the charging state first. Apply the condition second.
A repeatable chamber test treats configuration, charging state, EMC sequence, DUT reaction and recovery as one workflow.

- 1
Define
DUT, standard, ports, condition, counterpart and acceptance.
- 2
Configure
Charging technology, simulation parameters, signals and evidence.
- 3
Establish
Connect, negotiate and reach the required charging phase.
- 4
Apply
Execute the approved conducted or radiated laboratory sequence.
- 5
Capture
Record the condition, charging state, messages and DUT response.
- 6
Repeat
Reproduce the same configuration for correction and regression.
The published EMC Link concept is designed to maintain a stable charging interaction through long immunity and emissions sequences. Fewer interruptions mean fewer restarts and clearer comparisons.
Preserve the interfaces the selected charging technology actually uses.
Charging-specific signal depth
The optical boundary is configured around the live charging interaction. It is not a generic network bridge and it does not transfer charging power.
High-level communication
PLC (power line communication) communication for applicable charging technologies.
Low-level charging states
Control Pilot (CP)/Proximity Pilot (PP), CS1/CS2, CC1/CC2, CE/ID and temperature paths as configured.
Auxiliary handling
Digital relay control for the published 12 V AUX handling concept.
Supporting interfaces
CAN and Ethernet within the released laboratory configuration.
High-level communication
PLC charging communication through the optical path.
Low-level charging signals
CP / PP, CS1 / CS2, CC1 / CC2, CE / ID and temperature.
Auxiliary control
Charging-specific AUX handling through digital relay control.
Vehicle and test interfaces
CAN and Ethernet for the configured laboratory setup.
Test intelligence outside
EVCA and comframe logging, analysis, simulation and evidence.
Published technology context
- AC
- DC-CCS Combo 1
- DC-CCS Combo 2
- NACS
- CHAdeMO
- GB/T DC
- MCS — separate route
Charging power, sources, loads, chamber feedthroughs, cooling, interlocks and electrical safety remain part of the external laboratory architecture.
Correlated evidence
See the first meaningful deviation on one timeline.
A common time base helps distinguish an electromagnetic effect from an unrelated protocol, setup or system issue. The relevant question is not only whether charging stopped. It is what changed first, during which condition, and how the DUT recovered.

What was applied?
Test step, level, frequency range, dwell or laboratory event.
What changed in charging?
Messages, timing, pilot state, measurements and charging phase.
How did the DUT respond?
Continued operation, transition, derating, interruption, stop or recovery.
Can the result be reproduced?
Configuration, trace, technical assessment and repeatable rerun.
Use the transparent link alone, or add EVCA and comframe where the test needs intelligence.
Standalone or integrated
Use the chamber method to define the test boundary, then confirm the interfaces, connectors, software functions and licences released for the project configuration.

Standalone real pair
Connect a real EV and real EVSE across the optical link while preserving the supported charging paths.
EV in the chamber
Keep EVSE simulation, control, measurement and analysis outside while the vehicle side is exposed.
EVSE in the chamber
Keep EV simulation, control and analysis outside while the charging-station side is exposed.
EMC or climate environment
Use the same boundary logic wherever the DUT must remain connected to its charging counterpart through an isolated optical path.
Clear system boundaries
Separate transport, test intelligence and laboratory responsibility.
This prevents a transparent interface from being mistaken for a complete EMC laboratory or a protocol-analysis system.
EMC Link
- Optical charging-specific signal transport
- Standalone real-pair operation
- Supported communication and low-level paths
- Chamber-side and external-side units
EVCA + comframe
- EV or EVSE simulation
- Logging and synchronised analysis
- Debugging and simulation control
- Automation and reporting where configured
EMC test environment
- Condition generation and measurement
- Antennas, networks and chamber setup
- Power, loads, cooling and safety
- Acceptance criteria and final verdict
Configure from the chamber test, not from a generic parts list.
Plan the complete agreed test requirements
Define the decision, interfaces and laboratory boundary before selecting the released EMC Link and EVCA configuration.
Configure the optical link around the actual chamber test
DUT in the chamber
Vehicle, inlet, controller or charging station
Counterpart outside
Real EV / EVSE or EVCA simulation
Charging technology
AC, CCS / NACS, CHAdeMO, GB/T DC or separate MCS path
Transparent signals
PLC, low-level charging signals, CAN, Ethernet and AUX
Environment
EMC or climate chamber, supply filtering and fibre routing
Evidence
Standalone path or EVCA + comframe logging, analysis and reports
Defined result
EMC Link configuration + compatible EVCA path + approved chamber setup
Then define the optical path and test intelligence required outside the chamber.
Explore EMC test systems, standards and setup guidance.
Explore the equipment and available test functions.
EMC Link
Optical hardware, topologies, signal paths and configuration inputs.
PlatformEVCA
EV and EVSE simulation, measurement, analysis and laboratory automation.
Softwarecomframe
Logging, synchronised analysis, orchestration and reporting.
StandardsCharging, Safety & EMC
Map document, edition, DUT role and released scope before the test.
Official brochureEMC Link technical brochure
Published technology coverage, signal transport, architecture and setup notes.
Existing systemTechnical support
Use the support route for an existing configuration or reproducible issue.
Frequently asked questions
EV charging EMC test FAQ
Use the exact project standard, released product documentation and approved laboratory procedure for the final test plan.
What is EV charging EMC testing?
It verifies how an EV, onboard charger, EVCC (vehicle-side charging communication controller), EVSE or SECC (station-side charging communication controller) behaves while a defined electromagnetic condition is applied or measured. The charging state, DUT response and laboratory condition must remain attributable on one evidence basis.
What is the difference between EV EMC testing and EVSE EMC testing?
EV EMC testing places the vehicle, inlet, onboard charger or EVCC in the chamber while the EVSE counterpart remains outside. EVSE EMC testing places the charging station, module or SECC under stress while a real EV or EV simulation remains outside.
Why use an optical link at the chamber boundary?
The optical path keeps the selected charging communication and low-level signals connected without extending a conventional copper communication path through the chamber boundary. Fibre routing, filtered supply, charging power and chamber feedthroughs remain part of the approved laboratory setup.
Can EMC Link operate without an EVCA test system?
Yes. The published architecture supports standalone operation between a real EV and a real EVSE. EVCA and comframe can be added when simulation, logging, analysis, debugging, automation or reporting is required.
Continue with your selected boundary
Turn the application into a test-system brief.
The configurator carries the decision forward and keeps every recommendation editable.