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.
Test scenario: repeat the recorded vehicle behaviour in the laboratory
Keep the original session recording. Use the supported playback functions to prepare the simulated charging partner, repeat its behaviour against the DUT and compare the original and new response. Choose the communication, timing and physical test scope for that 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
Replay 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. Keep using the existing evidence while examining communication, timing and the available measurement context.
EV simulation in comframe
Planned for Q1/2027
Replay EV behaviour recorded in CANoe 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.
Test a correction with the recorded charging partner
Review the original charging sequence, then use supported Charge Playback functions to reproduce the partner behaviour in a new physical test. Compare the DUT (device under test) response after a correction with the original session.
Turn a real charging session into a repeatable test
Document the source recording and the supported behaviour used to create the active simulation.
Use EVCA Flex or EVCA Multi Mobile for laboratory reproduction, according to the required setup.
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.
Create the supported behaviour model from the recording. Keep its source identifier, protocol version, direction and transformation status with it.
Run the derived charging partner at the physical interface. Compare the DUT response after a fix, variant or release change.
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.
Present a recorded vehicle as the simulated EV
Capture how a real EV communicated, derive the supported behaviour and use 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?
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?
Compare offline replay, power playback and Charge Playback
These workflows can use the same source session, but they answer different engineering questions.
On smaller screens, scroll the table horizontally to see every column.
| Selection criterion | Offline data replay | Power playback | Charge Playback |
|---|---|---|---|
| Primary purpose | Review stored traces and measurements | Reproduce voltage or current profiles | Make the DUT interact 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 |
Keep partner-specific charging cases for later tests
Bring a field case into the laboratory
Capture a partner-specific charging case at a testival, during a field campaign or at the customer site.
Verify vehicle changes with the recorded charger
Use the same simulated charging-station behaviour after EVCC or vehicle software changes.
Verify charger changes with the recorded vehicle
Challenge the SECC (station-side charging communication controller) or charger with the same field-derived vehicle behaviour.
Keep customer cases traceable across releases
Keep the source recording, transformation, test execution and result together. Your team can trace the case across projects and releases.
Reduce repeated site visits
Investigate the captured case in the laboratory and test the proposed correction before returning to the site.
Reuse the case after every relevant change
Add the derived partner to a repeatable campaign where automation is supported.
Choose the EVCA setup for recording and laboratory tests
Use your existing recordings today
- Charge Playback is already available in CANoe for the agreed recording, direction and system configuration.
- CANoe measurement recordings can already be imported into comframe for analysis.
- The released active playback workflow lets the DUT interact at the physical charging interface.
- A qualified case can be retained for repeated verification.
Match the workflow 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.
Plan the playback test before selecting hardware
Playback and field-to-lab FAQ
What does this capability do?
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.
How is it different from offline replay?
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.
How is it different from power playback?
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.
What is recorded during the field session?
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.
What is EV behaviour playback?
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.
What is EVSE behaviour playback?
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.
Specify the captured direction, supported behaviour, laboratory DUT and comparison result.