InteropEV Analyzer

Capture in. Audit-ready verdict out.

InteropEV Analyzer decodes a charging session, validates it against DIN 70121 and ISO 15118, explains the root cause and writes the report. All on your machine.

InteropEV Analyzer message view with a decoded SLAC, SDP and DIN 70121 sequence
Input formats.pcap.pcapng.blf ExportsPDFXLSXCSVJSON

Everything an interop review needs, in one workspace.

Stop hand-tracing thousands of frames. Jump straight to the failing message, see the clause it breaks, read why it happened, and hand your partner a report they can act on.

Full session decode

SLAC, NDP, SDP, TCP, TLS and every V2G message, navigable end to end with decoded fields and raw bytes side by side.

Conformance rules

Message sequence, mandatory fields, TLS requirement and cipher suites checked against DIN 70121, ISO 15118-2 and ISO 15118-20.

Timing analysis

Per-phase and per-message latency against the specification's timeout budgets, with hotspots and repeating loops grouped.

CAN and DBC decoding

Decode BLF captures against your own DBC databases per channel and line CAN signals up with the charging dialogue.

Root cause with AI diagnosis

The engine traces the failure to the first message that went wrong. The AI assistant then explains the mechanism, names the responsible side and proposes the next test, citing packet numbers you can click.

Branded reports

White-label PDF, XLSX, CSV and JSON with configurable contents. Your logo and colours on every page you send to a customer.

Timing and sequence

See where the seconds go.

Every phase from SLAC to Current Demand on one timeline, with the gaps and response times that decide whether a session passes.

  • Stacked phase breakdown with the longest phase and longest gap highlighted
  • Repeating charging loops grouped so the sequence stays readable
  • Each timing checked against the standard's limits, with status per row
Sequence timings view: stacked phase breakdown from SLAC to Current Demand with per-phase durations and status
AI assistant

A senior interop engineer's write-up, in seconds.

The deterministic verdict is ground truth. The assistant is only allowed to explain it: every packet it cites must exist in the evidence, every action must be concrete and checkable, and anything the capture cannot show goes into caveats.

Per session

Root-cause diagnosis

A one-line verdict in engineer language, the responsible side with the evidence behind it, supporting packets, confidence and the single next capture that would confirm or refute it.

Per campaign

Failure clusters and trends

Batch analysis groups captures by failure mode, tallies chargers and response codes across each cluster, and explains whether the pattern points at one unit's firmware, the EV, or the standard's interpretation.

In the report

Diagnosis on the page

The AI section exports with the rest of the report, clearly labelled, so a vendor or certification body reads the same explanation your engineers did.

What the model sees, and what it never sees.

You control the data-sharing agreement in the app, field by field.

  • Sent: the verdict, failed rules, phase timings and a slice of the message timeline around the failure
  • Never sent: raw packets, payload bytes, EXI streams, CAN frames, TLS keys, certificates or file paths
  • MAC addresses, session IDs and file names are replaced with stable pseudonyms before anything leaves the app
  • Managed inference through InteropEV with no API keys to hold, or a local model on your own hardware
Validation report with the compliance summary that the AI diagnosis is attached to

A report you can send to the other side.

Every finding carries the packet, the field and the clause behind it. Certification evidence, engineering review or a vendor hand-off, from the same export.

  • Compliance summary with pass and fail reasons
  • Session telemetry: voltage, current and state of charge over time
  • AI diagnosis included or left out, per template
  • Full or condensed templates, per audience
Validation report view with compliance summary and session telemetry charts

Built for sensitive captures.

DeploymentLocal-only desktop app

Captures and vehicle data never leave the device. Parsing runs in a background worker; sessions persist locally.

PlatformsWindows and macOS

Native installers with file associations for .pcap, .pcapng and .blf. Apple Silicon and Intel supported.

Live captureRecord from the interface

Capture directly from a network interface during a test run and analyse as soon as the session ends.

Rule engineTransparent and editable

Force a standard, toggle individual checks and browse the rule library with the clause each rule enforces.

Licensing that fits how test teams work.

Seats are activated per machine and keep working offline for seven days between check-ins. Floating pools share a set of seats across a lab. AI usage is metered per licence, so nobody in your team needs to hold a model API key.

Engineer

One named machine

Session decode, conformance rules, timing analysis and standard reports.

  • Node-locked seat
  • DIN 70121 and ISO 15118-2 / -20 rule packs
  • AI root-cause diagnosis, metered
  • PDF, XLSX, CSV and JSON export
Enterprise

Site-wide deployment

Custom rule packs, simulation and measurement modules, and an engineer on call.

  • Custom and private rule packs
  • Local model inference on your own hardware
  • Simulation and measurement modules
  • Priority support and onboarding

See it on your own captures.

Bring a failing session. We will run it through the Analyzer and walk you through the verdict, the evidence and the report, live.