Choose EVCA capabilities for your charging test
Choose from six EVCA test capabilities for your engineering task. Find the supporting systems, standards and releases, then define the hardware, licences and Test Libraries for your setup.
Choose the test method and the EVCA system
It starts with the application and the question your test should answer. Each EVCA capability serves an investigation and its recorded data. EVCA systems provide the physical interfaces, mobility and power scope. comframe and related software functions handle configuration, data, reports and integration.
Six EV charging test capabilities for your engineering questions
The filter shows the capability for the result you need. The detail pages explain how it works, which workflows are compatible and what configuration and release scope apply.
Showing all six capabilities.
Automated Standards Analysis
I have decoded data. Does the measured session follow the expected timing, states and limits?
Automated Standards AnalysisProfessional Simulation
How does the DUT (device under test) react when the simulated charging partner sends borderline or non-conform behaviour?
HLC (high-level communication) content, optional messages, delays, timeouts and unexpected sequences are set in the simulation configuration.
Professional SimulationCharge Playback
Can the real field partner be brought back into the laboratory as an active, repeatable simulation?
Use recorded EV or EVSE (electric vehicle supply equipment, or charging station) protocol behaviour as a reusable charging partner at the physical interface. Active playback reproduces partner behaviour during a test.
Charge PlaybackManipulating Gateway
Will a selected message, value or timing change alter the result while the real EV and EVSE remain connected?
Test a correction hypothesis through a controlled communication change between both real charging partners, before implementing software changes in either product.
Manipulating GatewayCharge Cycle Automation
How can complete charging configurations become repeatable campaigns for regression and unattended laboratory use?
Arrange saved behaviour configurations, define repetitions and run complete charging cycles. Measurements and reports stay linked to the active configuration.
Charge Cycle AutomationConformance Test Libraries
Which ready-to-run test cases cover the required standard, edition, DUT role and released scope?
Implemented, versioned and supported test logic runs with controlled execution, structured verdicts and reports. Lifecycle support maintains the test setup.
Conformance Test LibrariesChoose a capability for your next engineering decision
Combine EVCA capabilities in your test workflow
Combine capabilities for root-cause investigations and release decisions. Keep the measurements linked to their test conditions throughout.
Use charging analysis to locate the first meaningful deviation. Test a live hypothesis, reproduce the recorded partner, create controlled variants and repeat the case after the correction.
Run released test cases, connect each verdict to traces and measurements, challenge additional robustness boundaries and preserve the same campaign after DUT changes.
Extend released EV charging test workflows through REST API, Python or CI/CD integration. The interfaces connect external automation with charging-specific test logic.
Showing decoded data is not the same as analysing it. Configure the test. Do not develop the test environment.
Choose the EVCA system for your test capabilities
| Capability | ComOnly | Multi Mobile | Interop | Flex | MCS | EMC Link |
|---|---|---|---|---|---|---|
| Automated Standards Analysis | Primary fit | Primary fit | Primary fit | Primary fit | Release-specific | Via connected EVCA |
| Professional Simulation | Primary fit | Common option | Common option | Primary fit | Release-specific | Via connected EVCA |
| Charge Playback | Published option | Primary fit | Primary fit | Common option | Release-specific | Via connected EVCA |
| Manipulating Gateway | Project-specific | Primary fit | Primary fit | Common option | Release-specific | Via connected EVCA |
| Charge Cycle Automation | Common option | Common option | Common option | Primary fit | Release-specific | Via connected EVCA |
| Conformance Test Libraries | Primary fit | Common option | Supporting role | Primary fit | Release-specific | Via connected EVCA |
Use EVCA capabilities across development, interoperability and release decisions
The communication controller, tested directly
Nominal simulation, non-conform behaviour, timing analysis, test cases and regression come together before the complete vehicle or charger exists.
Charging behaviour connected with vehicle reactions
Simulation, standards-aware evaluation, field-derived partners and repeatable campaigns follow vehicle development.
Charger communication and electrical behaviour, tested
Software versions are tested with controlled EV behaviour, conformance workflows and robustness variants.
A repeatable test case from a real charging pair
The real interaction is analysed, a live hypothesis tested, the partner reproduced and the case kept for later regression.
Defined tests and understandable results
Versioned Test Libraries and verdicts connect with traces, timing, signals, reports and release processes.
A stable test basis while the DUT changes
Saved configurations and the same test-record structure return after a build, parameter change, hardware revision or corrective action.
EVCA capabilities at a glance
- Six EVCA capabilities answer different engineering questions.
- First the capability, then system and project configuration.
- Each capability page explains its operating principle and release limits.
What requires release approval
- Protocol, standard edition, DUT role and direction.
- Supported systems, hardware modules and operating modes.
- Licences, Test Libraries, TLS and certificate conditions.
- Automation, API, reporting and unattended-operation scope.
Configure the capability combination for your test task
DUT, protocol and needed records are defined. EVCA system, software release and integration path are specified for the setup.
EVCA Capability Hub FAQ
What is the EVCA Capability Hub?
The EVCA Capability Hub helps you choose the test functions for your task: analyse, challenge, reproduce, manipulate, automate or verify. Use it to select the method before configuring the EVCA system and project.
What is the difference between an EVCA capability and an EVCA system?
A capability describes the test mechanism or engineering outcome. An EVCA system describes the hardware, interfaces, mobility and power depth used to apply it. One capability can appear in several systems, while one system can combine several capabilities.
Are all EVCA capabilities available on every EVCA system?
No. Availability depends on the charging protocol, standard edition, DUT role, hardware modules, software release, licences, security conditions and selected Test Libraries. The system-fit matrix is a routing aid, not a compatibility guarantee.
Which capability analyses a charging session against standards?
Automated Standards Analysis compares measured timing, messages, signal states and relevant electrical values with normative expectations. It highlights deviations alongside the recorded data.
Which capability creates non-conform charging behaviour?
Professional Simulation configures the simulated charging partner. Where released, it can change supported HLC values, optional messages, timing, timeouts and unexpected sequences for robustness testing without requiring the core test to be programmed from scratch.
What is the difference between Professional Simulation and Manipulating Gateway?
Professional Simulation controls a simulated EV or EVSE charging partner. Manipulating Gateway operates between a real EV and a real EVSE and changes selected live communication to test a specific engineering hypothesis.
Capability scope
DUT, released configuration, controlled method and engineering result are specified.