Who performs the analysis—the software or the engineer?
Automated Standards Analysis relates recorded charging communication and timing to the configured DIN 70121 and ISO 15118 requirements. The software highlights deviations; the engineer reviews the evidence and decides what the result means for the test.
Test scenario: a response arrives after the expected window
Illustrative timing example, not a quoted standard limit: a test expects a response within 100 ms, but the recording shows 120 ms. The useful result connects the measured event, the 100 ms expectation and the 20 ms deviation. In a real test, the selected standard, message and charging phase define the applicable expectation.
| Event | Expected | Measured | Deviation |
|---|---|---|---|
| Partner response | Within 100 ms | 120 ms | 20 ms after the example limit |
Compare recorded behaviour with the expected charging sequence
A protocol decoder can tell the engineer which message was sent. It does not automatically explain whether the message arrived in the correct phase, whether the timing matched the applicable expectation or whether a required state was missing.
Automated Standards Analysis productises charging-standard expertise inside the test workflow. It correlates the measurement with normative expectations and highlights the point where the session diverges. The engineer moves from searching across traces to reviewing an evaluated technical event. This turns charging protocol analysis into a repeatable workflow instead of a project-specific manual task.
Automate the repeatable comparison work
The capability keeps the source data visible while adding the standard context required to understand it. This does not hide engineering depth. It places that depth where it belongs: inside a repeatable charging workflow.
DIN 70121 and ISO 15118 timing analysis that shows the expectation, not only the timestamp
DIN 70121 and ISO 15118 timing analysis relates measured messages and state transitions to the applicable timing window. A late, early or missing event becomes visible immediately, while the original trace remains available for detailed engineering review.
DIN 70121
Review supported message timing and charging-sequence behaviour in the context of the configured implementation.
ISO 15118-2 and -3
Connect high-level communication with PLC (power line communication) and low-level timing where the selected EVCA configuration provides the required channels.
ISO 15118-20
Apply release-approved analysis functions to supported message sequences and timing. Exact coverage must match the current software release.
Release qualification: standards, editions, message sets and timing checks are configuration-dependent. The selected product release and approved quotation define the exact scope.
See DC charging states in the context of the real session
The Cross-Layer State Monitoring combines the expected charging sequence with the measured event. PLC message type, Control Pilot (CP) state, Proximity Pilot (PP) state, DC voltage and DC current can be viewed in the context of the active charging phase.
Expected, missing or excessive
Expected behaviour is presented clearly. Missing states, missing values or behaviour that appears where it should not can be marked for review. The user sees where the charge diverged instead of searching through separate communication and oscilloscope traces.
IEC 61851-23 Annex CC with measured evidence
The sequence view provides a common reference for engineers who need to discuss a charging event across software, power electronics and system teams. Exact panel content and standard edition require release approval.
One method. Technology-specific charging states for DC CCS, CHAdeMO and GB/T DC.
Cross-Layer State Monitoring checks whether protocol messages, low-level signals, state transitions and electrical values form an allowed and technically consistent combination at a given point in the charging process. The technology determines the communication and signal layers. The measurement and evaluation method remains consistent.
PLC, CP/PP and electrical state
- DIN 70121 and ISO 15118 communication
- CP and PP state context
- IEC 61851-23 charging phases and Annex CC context
- DC voltage, current and expected transition
CAN communication and CHAdeMO state context
- CHAdeMO CAN messages and timing
- Technology-specific control and connector states
- Charging sequence and permitted combinations
- DC voltage, current and reaction of both partners
GB/T CAN communication and low-level state
- GB/T 27930 communication and timing
- GB/T 18487.1 interface and state context
- Technology-specific charging phases
- DC voltage, current and highlighted deviation
Exact protocol versions, state models, measured channels and evaluation functions depend on the selected EVCA system, hardware modules and released comframe configuration. Cross-Layer State Monitoring complements, but does not replace, a formal Conformance Test Library.
Find the first meaningful deviation across every configured layer
Protocol messages explain only part of a charging failure. Correlating them with CP, PP, voltage and current helps determine whether communication, low-level control or power behaviour initiated the event.
Analysis, simulation and conformance are different jobs
Choose data capture to inspect what happened, continuous analysis to investigate supported rules, and a configured test case when the task requires a controlled stimulus and an explicit evaluation.
Professional Simulation
Configures the behaviour to be tested, including supported message content, timing and non-conform variants.
Conformance Test Libraries
Execute defined test cases and verdict logic for a supported implementation profile.
Interoperability & Charging Analysis
Uses synchronised evidence to understand a real EV and EVSE (electric vehicle supply equipment, or charging station) interaction and reproduce the issue.
Reuse the evaluation when you repeat the test
Automated Standards Analysis supports individual development sessions, real-pair recordings and repeatable test campaigns. The same charging protocol analysis principles remain reusable across these contexts. The selected EVCA system determines which standards, measurement layers and evaluation panels are available.
Controller and vehicle integration
Review timing, states and charging behaviour before the complete power environment is available or during integrated vehicle validation.
Charging-station analysis
See how the simulated or real vehicle reacts to SECC (station-side charging communication controller) behaviour, charging states and measured power transitions.
Real EV ↔ real EVSE sessions
Apply evaluated context to synchronised recordings so the first deviation can be discussed across both implementation teams.
Neutral technical evidence
Preserve the measured behaviour and normative expectation together for repeatable laboratory decisions and customer communication.
Automated charging campaigns
Reuse the released evaluation logic across variants instead of rebuilding the analysis for every configuration.
One evidence base
Share the evaluated event with software, controller, power-electronics and system partners without reducing the issue to a raw trace attachment.
Choose the device, standard and measurements for the test
A useful configuration defines more than a protocol name. It states which measured layers, normative references, panels, outputs and EVCA system path are required.
DUT and test role
EV, EVSE, controller or real charging pair
Charging standard
Protocol family, version and implementation profile
Measured layers
Messages, timing, CP, PP, voltage and current
Evaluation scope
Timing, states, values, phases and normative limits
Evidence output
Monitoring view, traces, reports and exported data
System path
ComOnly, Multi Mobile, Interop, Flex or MCS configuration
Selected EVCA system + released analysis coverage + approved normative references
Automated Standards Analysis FAQ
What is Automated Standards Analysis?
Automated Standards Analysis connects measured charging behaviour with applicable timing, states, phases and normative expectations. Instead of showing only decoded protocol data, it highlights where the observed session matches the expected behaviour and where a technical review is required.
How is this different from a protocol trace viewer?
A trace viewer exposes messages and timestamps. The engineer still has to compare them manually with the relevant standards. This capability adds the applicable standard requirements, correlates configured measurement layers and makes deviations visible inside the charging workflow.
Does Automated Standards Analysis replace the test engineer?
No. It removes repetitive comparison work and presents the measurement, expectation and deviation together. The engineer remains responsible for technical interpretation, root-cause confirmation, product decisions and the approved test conclusion.
Which standards can be included?
The capability scope can include DIN 70121 and ISO 15118 timing analysis as well as IEC 61851-23 Cross-Layer State Monitoring for DC CCS, CHAdeMO and DC China / GB/T DC. Exact standard editions, protocol versions, measured layers and evaluation functions depend on the released software and EVCA configuration.
How is ISO 15118 timing evaluated?
DIN 70121 and ISO 15118 timing analysis relates a measured message or state transition to the applicable timing expectation. The result shows both the real timestamp and the configured normative window so that late, early or missing behaviour can be reviewed immediately.
What is the Cross-Layer State Monitoring?
The Cross-Layer State Monitoring places the measured charging session in the context of the expected DC charging sequence. Depending on configuration it combines PLC message type, CP and PP state, DC voltage, DC current and the active charging phase.
Standards-aware review
Show the deviation; keep judgement with the engineer.
Define the measured layers, applicable expectations and evidence required for engineering review.