Capability / live interoperability debugging
Test a Communication Change during a Real Charging Session
Keep the real EV and EVSE connected while changing communication in either direction. Use PLC manipulation for CCS/NACS, the CAN Manipulating Gateway for DC-China (GB/T DC), or Control Pilot variation for AC low-level charging.

Choose the intervention
Change the communication condition. Observe the real response.
A passive gateway records the original charging session. Manipulating Gateway introduces a controlled change to investigate a charging problem or test the response to a defined deviation.
CAN communication
DC-China (GB/T DC): bidirectional CAN manipulation
Pass, filter or manipulate CAN messages towards the EV or EVSE. Edit individual values and hexadecimal data within messages, modify J1939 CAN frame/header fields including ID, Data Page, Priority and Reserved Bit, and add delays per message type. Compare the original exchange with the response to each controlled change.
One test workflow
Record. Change. Compare.
Record the baseline
Capture the original charging session and the suspected deviation.
Define one change
Select the supported PLC parameter, GB/T DC CAN message value, frame field or delay, or the CP voltage or duty cycle. State the response you expect.
Apply it live
Activate the configured change while the real EV and EVSE remain connected.
Compare the response
Compare communication, pilot signals, voltage and current before and after the change. Retain the setting and both recordings.
Where it changes the decision
Use the real charging pair when replacing either side would hide the problem.
Parameter and signal boundaries
Test whether a specific PLC parameter or AC Control Pilot change explains the observed charging behaviour.
Optional behaviour
Challenge an implementation assumption without first waiting for a software build from one partner.
Supplier alignment
Replace competing trace interpretations with a shared before-and-after charging experiment.
Illustrative AC low-level example · EV under test
Does a change in the CP duty cycle alter the charging behaviour?
Configuration boundary
Define the real pair, the suspected cause and the one change that would prove it.
Identify EV, EVSE, charging standard and edition, physical interface, security context, observed failure, selected communication element, expected recovery, measured layers and required evidence.
Questions before configuration
Manipulating Gateway, precisely scoped.
Does the gateway replace either charging partner?
How is it different from Professional Simulation?
What can I change with Manipulating Gateway?
What evidence should be retained?
What is needed to scope a project?
Controlled real-pair change
Define the suspected cause and one controlled change.
Describe the real EV and EVSE, observed failure, supported communication element and expected recovery.