EVCA capability hub

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.

EVCA capability illustration: configure, simulate, measure, analyse, validate and preserve evidence.
AnalyseRelate measurements to normative expectations
ConfigureCreate nominal and non-conform charging behaviour
ReproduceBring real field partners back to the physical interface
AutomateRun campaigns and preserve measurements linked to their test conditions
Four selection questions for one architecture

Choose the test method and the EVCA system

Start with the application and the question your test should answer. Choose an EVCA capability for the investigation and recorded evidence. EVCA systems provide the physical interfaces, mobility and power scope. Use comframe and related software functions for configuration, data, reports and integration.

Selection model from application through capability and EVCA system to software and evidence
Select by test task first. Combine all four layers in the final project specification.
Six shared EVCA capabilities

Six EV charging test capabilities for your engineering questions

Use the filter to find 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.

01 Understand
Asa

Automated Standards Analysis

I have decoded data. Does the measured session follow the expected timing, states and limits?

Compare measurements, messages and signal states with normative expectations and highlight deviations for review.

Automated Standards Analysis
02 Challenge
Ps

Professional Simulation

How does the DUT (device under test) react when the simulated charging partner sends borderline or non-conform behaviour?

Set HLC (high-level communication) content, optional messages, delays, timeouts and unexpected sequences in the simulation configuration.

Professional Simulation
03 Reproduce
CP

Charge 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 Playback
04 Test live
Mg

Manipulating 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 Gateway
05 Automate
Ca

Charge 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. Keep measurements and reports linked to the active configuration.

Charge Cycle Automation
06 Verify
Tl

Conformance Test Libraries

Which ready-to-run test cases cover the required standard, edition, DUT role and released scope?

Run implemented, versioned and supported test logic with controlled execution, structured verdicts and reports. Use lifecycle support to maintain the test setup.

Conformance Test Libraries
Configuration note: Not every capability is available for every protocol, standard version or EVCA system. Final support depends on the current release, hardware, licences, security conditions and project configuration.
Choose by engineering question

Choose a capability for your next engineering decision

Decision map from six EV charging engineering questions to the relevant EVCA capabilities
Use the hub for orientation and selection, then confirm exact feature intent and released scope on the detailed capability page.
From feature to evidence chain

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.

Root-cause and conformance workflows combining EVCA capabilities into evidence chains
The sequence is illustrative. Select only the steps supported and required by the project.
Root cause

From deviation to verified correction

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.

Conformance

From standard scope to understandable verdict

Run released test cases, connect each verdict to traces and measurements, challenge additional robustness boundaries and preserve the same campaign after DUT changes.

Integration

Extend the workflow through open interfaces

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.
Capability to system routing

Choose the EVCA system for your test capabilities

The same capability can appear in more than one system. The table indicates typical relationships, not released compatibility. The quotation and current release matrix remain authoritative.

EVCA systems connected to the shared capability hub with configuration-dependent support
Context illustration, not a product identity photograph. External power equipment and the EMC chamber are separate from the EVCA or EMC Link system. Interfaces and features must be confirmed for the selected configuration.
Primary fit Common option Project-specific Release-specific Via connected EVCA

On smaller screens, scroll the table horizontally to see every column.

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
Routing only: confirm protocol, edition, direction, hardware modules, software release, licences, TLS and certificate conditions, Test Library version, power integration and operating limits.
One capability layer across applications

Use EVCA capabilities across development, interoperability and release decisions

Test the communication controller directly

Combine nominal simulation, non-conform behaviour, timing analysis, test cases and regression before the complete vehicle or charger exists.

Connect charging behaviour with vehicle reactions

Use simulation, standards-aware evaluation, field-derived partners and repeatable campaigns as vehicle development progresses.

Test charger communication and electrical behaviour

Test software versions with controlled EV behaviour, conformance workflows and robustness variants. Keep regression results linked to their test conditions.

Build a repeatable test case from a real charging pair

Analyse the real interaction, test a live hypothesis, reproduce the partner and preserve the case for later regression.

Use defined tests and understandable evidence

Connect versioned Test Libraries and verdicts with traces, timing, signals, reports and release processes.

Keep the test basis stable while the DUT changes

Reuse saved configurations and the same test-record structure after a build, parameter change, hardware revision or corrective action.

Capability selection

EVCA capabilities at a glance

  • Choose from six EVCA capabilities to answer different engineering questions.
  • Combine capabilities in one workflow for the required evidence.
  • Choose the capability, then configure the system and project.
  • Explore each capability for its operating principle and release limits.
Configuration details

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.
From test objective to project specification

Configure the capability combination for your test task

Define the DUT, protocol and evidence needed. Specify the EVCA system, software release and integration path for the setup.

1. DUT and role EV, EVCC, EVSE, SECC, real pair, subsystem or complete product.
2. Charging interface Connector, protocol family, standard edition and regional profile.
3. Engineering question Understand, challenge, reproduce, test live, automate or verify.
4. Physical environment Controller bench, laboratory, high power, field, MCS or EMC chamber.
5. Capability combination One focused function or a multi-step evidence chain.
6. Evidence Measurements, the applicable standard requirements, verdicts, reports and traceability.
7. Automation and integration Campaigns, REST API, Python, CI/CD and external orchestration.
8. Release and licence Hardware, software, Test Library, security and known limitations.
Frequently asked questions

EVCA Capability Hub FAQ

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.

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.

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.

Automated Standards Analysis compares measured timing, messages, signal states and relevant electrical values with normative expectations. It highlights deviations alongside the recorded evidence.

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.

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

Define the EVCA capabilities for your test

Specify the DUT, released configuration, controlled method and engineering result.