Reproduce Recorded Charging Behaviour in the Laboratory
The vehicle that triggered a charging failure may no longer be available. Charge Playback uses supported behaviour from the recorded session to create a simulated charging partner for another test.
Test scenario: The vehicle has left; the failure still needs investigation
Keep the original recording of the failed session. Use the supported playback functions to build the simulated partner and repeat the relevant behaviour against the device. Compare the original and new response. Reproducing supported communication does not automatically reproduce every physical property of the original vehicle.
From CANoe recordings to comframe
Keep the recording. Choose analysis or active playback.
Your existing measurement data remains useful during the software transition. These three states distinguish what you can do today from the planned EV simulation in comframe.
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.
A trace can explain the past. The DUT needs the partner again.
Recorded traces are essential evidence, but they remain passive. They do not recreate the communication partner, they do not drive a new charging sequence and they cannot show whether the DUT (device under test) reacts differently after a correction.
Use the recording to reproduce charging behaviour under controlled conditions. The field case becomes a reusable test input instead of a one-time observation.
Turn one real event into a reusable laboratory partner
The workflow preserves the origin of the case while converting supported communication behaviour into a repeatable active simulation. It is designed to reproduce charging behaviour, not merely to display the session again.
Field capture with EVCA Interop
Field capture with EVCA Multi Mobile
Lab reproduction with EVCA Flex or EVCA Multi Mobile. Select either laboratory system for the required setup. Charge Playback converts supported recorded communication into an active test input.
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 a qualified behaviour model from the recording. Preserve source identity, protocol version, direction and transformation status.
Run the DUT again
Present the derived charging partner at the physical interface and compare the new result after a fix, variant or release change.
Use recorded vehicle behaviour to test the charger, or recorded charger behaviour to test the vehicle
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?
Separate data review, power profiles and active charging-partner behaviour
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 |
Turn difficult partner-specific issues into reusable test records
The strongest use case is not a nominal session. It is a real problem that disappears when the vehicle or charger leaves the site.
Close the gap between test event and laboratory
Bring a partner-specific failure back from a testival, field campaign or escalation site.
Repeat a charger-specific vehicle issue
Use the same simulated charging-station behaviour after EVCC or vehicle software changes.
Repeat a vehicle-specific charger issue
Challenge the SECC (station-side charging communication controller) or charger with the same field-derived vehicle behaviour.
Preserve customer cases as traceable test inputs
Keep source, transformation, execution and result attributable across projects and releases.
Reduce repeated site visits
Capture once, investigate in a controlled environment and return with a verified correction hypothesis.
Reuse the case after every relevant change
Add the derived partner to a repeatable campaign where automation is supported.
Use the right EVCA path for capture, root cause and laboratory depth
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.
Define the recording, direction and evidence before selecting hardware
Charge Playback is not one fixed bill of materials. The useful configuration starts with the real issue and ends with a defined active partner, physical interface and verification method.
Playback and field-to-lab FAQ
What does this capability do?
It converts a recorded real-world charging-partner interaction into a reusable active laboratory configuration. The DUT then interacts with a simulated EV or EVSE derived from the original session at the physical charging interface.
How is it different from offline replay?
Offline replay feeds stored information back into traces, charts or analysis tools. It helps an engineer inspect the past. This capability drives a new physical test so the DUT can react to the recorded partner behaviour again.
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.