Capability / robustness testing
Test how charging systems handle unexpected messages
Control the simulated EV or EVSE, vary communication parameters and observe responses to communication errors. Alongside CCS PLC simulation, DC-China (GB/T DC) and CHAdeMO Professional Sim offer advanced CAN controls for repeatable robustness tests.

A simulated charging partner under control
Configure charging behaviour. Keep the sequence in view.
Professional Simulation controls a simulated charging partner. Manipulating Gateway varies communication while the real EV and EVSE stay connected.
Supported parameters are set in an application-focused interface; you see how charging systems handle unexpected messages and changes in the sequence. Customers also use this workflow to understand DIN 70121 and ISO 15118-2/-3 charging processes while developing their own implementation.
Four control domains
Vary values, message availability, timing and sequence
Protocol-specific parameters
For CCS PLC, use valid or invalid DIN 70121 and ISO 15118-2 message parameters within the XML schema ranges.
Message availability under control
For DC-China and CHAdeMO, configure CAN message loss (CAN loss), including its frequency, to test the DUT response to missing communication. CCS supports suppression or omission of supported optional behaviour.
Change timing by message
For DC-China and CHAdeMO, set CAN cycle times per message type. For CCS, vary individual-message timing and test responses to defined delays and timeout conditions.
Challenge the state machine
State-machine robustness tested in CCS, DC-China and CHAdeMO. Protocol-specific error controls show transitions and recovery. CCS additionally supports injecting messages into the charging sequence.
CAN communication
DC-China and CHAdeMO: Professional Sim for EV and EVSE
Advanced CAN parameters are available in EV and EVSE Professional Sim for both standards, alongside the message-loss and cycle-time controls described above.
Repeatable robustness tests
Change one condition and review the complete response
- Define the baseline
Choose the EV or EVSE test role, charging standard and expected response under normal conditions.
- Configure the challenge
Vary message values, timing or supported additional messages to test a defined behaviour.
- Observe the DUT
Run the scenario and correlate state transitions with communication, pilot signals, voltage and current.
- Repeat and compare
Save the configuration and compare the response with the baseline. Reuse the setup to check software changes.
Example: a delayed response
Change the timing. Understand the reaction.
- Record the baselineRun the configured EV simulation against the EVSE and record the response under normal conditions.
- Vary the timing of a supported messageSelect a message and change its response delay using the available controls. The selected protocol and release determine the options.
- Evaluate the DUT responseReview the timing deviation, subsequent states and measured response with the configured analysis. The results point to the next investigation.
- Save and repeatReuse the simulation configuration after a software change and compare the response with the baseline.
Development and regression tests
Use Professional Simulation in development, boundary tests and regression
Controller robustness
Validation, recovery and safe-state behaviour are tested early in development, while implementation changes are easier to make.
Hard-to-reach boundary cases
Timing and sequence conditions that are hard to create reliably, safely or with reasonable effort using real charging partners become reproducible.
Repeatable regression
Save an approved behaviour configuration and rerun it after changes to software, parameters or hardware.
Test configuration
Choose the licence and hardware for your robustness test
DUT role, charging standard and edition, normal partner behaviour and the message or state to vary are defined. Physical signals, electrical test scope, automation target and required records are specified.
Frequently asked questions
Professional Simulation FAQ
Is this the same as a Conformance Test Library?
Does every test require programming?
Can it test both EV and EVSE implementations?
Can configured behaviour be automated?
What should be supplied for configuration?
Controlled partner behaviour
Define the behaviour for your test
Simulated role, standard, value, timing or sequence variation and the response to measure are described.