Applications
Products
Software
Knowledge
Company
Field-to-lab EVCA capability

Reproduce recorded charging behaviour in the laboratory

Bring a recorded charging case into the laboratory and test the DUT response after a fix. Charge Playback uses supported recorded behaviour to create a simulated charging partner, so your team can repeat the case when the original vehicle is no longer available.

Schematic record-playback player with recording, timeline and playback controls

Illustration of the record/playback workflow

Real sourceStarts from a captured session
Active partnerRecreate EV or EVSE behaviour
Physical interfaceThe DUT interacts again
Regression readyThe qualified case, reused
Test scenario: repeat the recorded vehicle behaviour in the laboratory

The original session recording stays. Supported playback functions prepare the simulated charging partner, repeat its behaviour against the DUT and compare original and new response. Communication, timing and physical test scope follow the case; the configuration checklist and FAQ explain what to specify.

From CANoe recordings to comframe

Use your recordings for analysis and active playback.

Continue using your measurement data as you move to comframe. The status cards show which functions are available and which EV simulation workflow is planned.

Charge Playback in CANoe

Available in CANoe

Replays supported recorded charging-partner behaviour as an active simulation. Charge Playback has long been available in comemso’s CANoe implementation; agree the protocol, direction and hardware for your recording.

CANoe recordings in comframe

Import and analysis available

Import measurement recordings from CANoe and analyse them in comframe today. Existing recordings stay in use while communication, timing and the available measurement context are examined.

EV simulation in comframe

Planned for Q1/2027

EV behaviour recorded in CANoe replays as an EV simulation with Charge Playback in comframe, so an EVSE can interact with it again. This workflow is planned and is not yet released.

For your recording, confirm the file format, captured content, protocol and matching EVCA setup. Import and analysis are available independently of the planned active EV playback release.

TestLib software status

The core difference

Test a correction with the recorded charging partner

The original charging sequence is reviewed; supported Charge Playback functions then reproduce the partner behaviour in a new physical test. The DUT (device under test) response after a correction is compared with the original session.

Replay versus playback Replay reproduces data for the engineer. Charge Playback reproduces the charging partner for the DUT.
Field-to-lab charging

Turn a real charging session into a repeatable test

Document the source recording and the supported behaviour used to create the active simulation.

Field capture with EVCA Interop
EVCA Interop records the real EV and EVSE interaction in the field. The recording is analysed and reused for laboratory testing.
Capture the real charging session with EVCA Interop.
Field capture with EVCA Multi Mobile
EVCA Multi Mobile records the real EV and EVSE interaction in the field. The recording is analysed and reused for laboratory testing.
Capture the real charging session with EVCA Multi Mobile.

Use EVCA Flex or EVCA Multi Mobile for laboratory reproduction, according to the required setup.

Record the real interaction

Capture the protocol sequence, relevant timing and available signal or measurement context while the real EV and EVSE (electric vehicle supply equipment, or charging station) interact.

Extract supported behaviour

Create the supported behaviour model from the recording. Keep its source identifier, protocol version, direction and transformation status with it.

Run the DUT again

Run the derived charging partner at the physical interface. Compare the DUT response after a fix, variant or release change.

Current software status: the active playback workflow is available in CANoe. EV simulation with Charge Playback in comframe is planned; import and analysis of CANoe recordings in comframe are already available.
The DUT direction

Recorded EV behaviour for EVSE tests. Recorded EVSE behaviour for EV tests.

The capability has two engineering directions, each with its own interface, protocol, security and release definition. The Q1/2027 comframe target stated here applies to recorded EV behaviour used as EV simulation for an EVSE DUT.

Two Charge Playback directions showing recorded EV behaviour testing an EVSE and recorded EVSE behaviour testing an EV
One recorded interaction. Two possible playback directions.
EV behaviour playback

Present a recorded vehicle as the simulated EV

Captures how a real EV communicated, derives the supported behaviour and uses it as the active counterpart for an EVSE DUT. This is useful when a charger problem only appears with one vehicle implementation.

  • DUT: EVSE or SECC
  • Partner: simulated EV from a recorded session
  • Decision: does the charger now handle the same behaviour correctly?
EVSE behaviour playback

Present a recorded charger as the simulated EVSE

Capture how a real EVSE communicated, derive the supported behaviour and use it as the active counterpart for an EV or EVCC (vehicle-side charging communication controller) DUT. This is useful when a vehicle issue depends on one charger implementation.

  • DUT: EV or EVCC
  • Partner: simulated EVSE from a recorded session
  • Decision: does the vehicle now handle the same behaviour correctly?
Direction note: recording in one topology does not automatically guarantee active playback in both directions. Confirm the exact protocol, connector, low-level interface, TLS context and system configuration. For recorded EVSE behaviour used to test an EV, confirm the application software and release separately.
Playback is not generic replay

Compare offline replay, power playback and Charge Playback

These workflows can use the same source session, but they answer different engineering questions.

Comparison between offline data replay, power playback and active charging partner playback
Three similar words. Three different engineering outputs. Only active physical playback lets the DUT react to the recorded charging partner again.
Selection criterion Offline data replay Power playback Charge Playback
Primary purpose Stored traces and measurements, reviewed Voltage or current profiles, reproduced The DUT interacts with a recorded charging partner again
Output A charging session replay in analysis tools Electrical source or load behaviour Active EV or EVSE protocol behaviour at the physical interface
Who reacts? The engineer The power stage and connected DUT The EV, EVCC, EVSE or SECC under test
Best use Review, sharing and diagnosis Power-stage and energy-profile studies Field issue reproduction and regression verification
Protocol-focused positioning: the defining value is not file replay and not generic voltage/current emulation. The defining value is active reproduction of the recorded charging partner for the DUT.
Where the capability earns its place

Keep partner-specific charging cases for later tests

A field case comes into the laboratory

A partner-specific charging case is captured at a testival, during a field campaign or at the customer site.

Vehicle changes verified with the recorded charger

The same simulated charging-station behaviour runs after EVCC or vehicle software changes.

Charger changes verified with the recorded vehicle

Challenge the SECC (station-side charging communication controller) or charger with the same field-derived vehicle behaviour.

Customer cases traceable across releases

Source recording, transformation, test execution and result stay together. Your team can trace the case across projects and releases.

Reduce repeated site visits

The captured case is investigated in the laboratory, and the proposed correction tested before returning to the site.

The case reused after every relevant change

Where automation is supported, the derived partner joins a repeatable campaign.

System and release fit

Choose the EVCA setup for recording and laboratory tests

Available software functions

Your existing recordings, usable today

  • Charge Playback is already available in CANoe for the agreed recording, direction and system configuration.
  • The released active playback workflow lets the DUT interact at the physical charging interface.
  • A qualified case can be retained for repeated verification.
Project configuration

The workflow, matched to your test case

  • Supported protocols, roles and versions.
  • Low-level signals, physical interface and power integration.
  • Editable content, timing and parameter boundaries.
  • TLS, certificates, automation, reporting and APIs.
From field case to project configuration

Plan the playback test before selecting hardware

1. Source session Real EV, real EVSE, location, failure and available recording.
2. DUT and direction Recorded EV to EVSE DUT, or recorded EVSE to EV DUT.
3. Charging protocol Standard, version, role, security and connector context.
4. Behaviour scope Content, sequence, timing, low-level states and measurements.
5. Controlled edits Which supported parameters may be varied and why.
6. Laboratory interface EVCA system, power hardware, loads, sources and safety scope.
7. Evidence Original session, derived configuration, playback result and report.
8. Automation Repetitions, campaigns, abort logic, API and regression workflow.
Frequently asked questions

Playback and field-to-lab FAQ

Charge Playback uses a recorded real charging session to create a reusable active laboratory test. The DUT interacts at the physical charging interface with a simulated EV or EVSE derived from the supported behaviour in that recording.

Offline replay lets engineers review stored traces, charts and measurements. Charge Playback runs a new physical test in which the DUT reacts to the supported recorded partner behaviour.

Power playback reproduces voltage or current profiles through source or load equipment. The capability described here is protocol-focused. It reproduces the charging partner behaviour at the EV or EVSE interface. Power integration remains a separate configuration scope.

The recording can include supported charging-protocol content, sequence and timing together with relevant signal and measurement context. Exact protocols, low-level signals, encrypted communication access and measurement channels depend on the selected EVCA, recording software and application release.

It uses behaviour recorded from a real vehicle to create an active simulated EV for testing an EVSE. Availability depends on the supported protocol, recording quality, selected hardware and released transformation workflow. Charge Playback is available in CANoe; EV simulation with Charge Playback in comframe is planned for Q1/2027.

It uses behaviour recorded from a real charging station to create an active simulated EVSE for testing an EV. The supported direction, protocol scope and physical interface must be confirmed for the project.

Field to laboratory

Bring the real charging case back to the laboratory.

Captured direction, supported behaviour, laboratory DUT and comparison result are specified.

¹ Scope

Functions, charging standards, interfaces, power ratings and Test Libraries depend on the EVCA system, the software release and your project configuration. Automated standards analysis supports, but does not replace, formal conformance testing. The quotation confirms the scope for your project.

  • EVCA playback depends on the system and software.