Portfolio-wide capabilities
Observe, Simulate and Analyse Charging Behaviour
Choose the task: record a real charging session, reproduce a charging partner, change a message or repeat a test series. Follow the matching capability to see how it works.

One technical foundation
Six actions. Different products. One decision chain.
A capability describes what the test must do. Product selection defines where that capability reaches the DUT (device under test) physically and which functions are released for the selected configuration.
Make test intent explicit
Connect DUT role, interfaces, parameters, automation and evidence requirements before hardware is selected.
Explore comframeControl counterpart behaviour
Challenge nominal, boundary and non-conform behaviour within the released product and protocol scope.
Professional SimulationKeep physical and protocol layers together
Correlate communication, low-level signals, power and application states on one time base.
Explore EVCAConnect observation and expectation
Relate measured behaviour to the applicable technical rule and the exact released evaluation scope.
Automated Standards AnalysisRepeat an approved test method
Use versioned test logic, controlled configurations and explicit verdict boundaries.
Conformance Test LibrariesKeep result and configuration attributable
Carry test identity, measurements, decisions and reports into engineering, release or production workflows.
Charge Cycle AutomationChoose the physical domain
The capability stays clear while the DUT changes.
The same action can require a different product, interface and control model. These routes identify the correct starting point without implying that every capability is available in every configuration.
EVCA + comframe
Communication, simulation, measurement, controlled faults, interoperability and released test logic.
Open the EVCA platformEasy Chester
Guided workflows for EOL (end-of-line), commissioning, service, inspection and calibration—using the control model appropriate to each product.
Choose the Easy Chester roleBattery Cell Simulator
Cell, sensor and fault simulation with an open interface. comframe is optional because many laboratories already operate another HiL (hardware-in-the-loop) environment.
Open BMS testing solutionsEMC Link
Keep charging communication observable across the chamber boundary while EMC stress is applied.
Open EMC LinkControl and integration
Use the software model that fits the operating environment.
comframe supports deep engineering analysis and extensibility for the compatible EVCA, Calimera and Battery Cell Simulator configurations.
On smaller screens, scroll the table horizontally to see every column.
| Product path | Primary control model | Why it fits |
|---|---|---|
| EVCA products | comframe | Shared configuration, synchronised analysis, automation and evidence across EV charging development. |
| Easy Chester Calimera | comframe | Connects the guided calibration system with traceable measurement and reporting workflows. |
| Battery Cell Simulator | comframe or another HiL environment | The open interface preserves the customer's established automation architecture; comframe remains an optional integrated path. |
| Easy Chester EOL / EOL HPC | RS-232 with SCPI commands | Provides straightforward deterministic integration into a production line; project-specific production-system extensions can be added. |
| Easy Chester Ultimate | Standalone guided operation | No laptop is required. Mobile report access is always available for retrieving completed test reports. |
Deep EV charging capability
Continue to the EVCA capability map.
The EVCA-specific hub explains Automated Standards Analysis, Professional Simulation, Manipulating Gateway, Charge Playback, Charge Cycle Automation and Conformance Test Libraries in their detailed charging context.
Frequently asked questions
EV Charging and BMS Testing Capabilities FAQ
How are test results documented?
Available evidence can include configurations, measured values, communication traces, evaluations and reports. The exact output depends on the selected workflow.
Capability scope
Define how this capability should support the test.
Specify the DUT, released configuration, controlled method and engineering result.