Area overview
Start here
Classic ECU diagnostics uses UDS (ISO 14229): diagnostic sessions, reading and clearing Diagnostic Trouble Codes (DTCs) with freeze frames, routines, I/O control and reprogramming. It runs over CAN (ISO-TP) or Ethernet (DoIP, ISO 13400). Emissions-relevant diagnostics follow the legal OBD requirements.
Towards SOVD
HPCs run many processes, containers and VMs rather than one firmware image, and byte-oriented UDS fits them poorly. SOVD (Service-Oriented Vehicle Diagnostics) offers a REST/HTTP API with JSON, usable from workshop testers, the cloud and in-vehicle apps alike. It adds things UDS never had: access to logs, configuration and software state, and discovery of what a component offers.
UDS and SOVD will coexist for many years. A Classic Diagnostic Adapter on the HPC translates SOVD requests into UDS for legacy ECUs.
Security
Diagnostic access is a classic attack vector. Baseline expectations today: authenticated access (certificate-based, beyond legacy seed/key), role-based authorisation, gateway filtering of diagnostic traffic, and logging of every privileged session.
State of play (late 2026)
- ISO 17978 (SOVD) is published — Part 3 (API) in March 2026, Part 2 (use cases) in April and Part 1 (general) in May 2026. ASAM is preparing SOVD v1.2 with monitoring and data-collection features.
- Tooling has arrived. Vector announced an end-to-end SOVD toolchain in July 2026 that starts by testing SOVD concepts on existing UDS vehicles without modifying them.
Commercial-vehicle angle
For fleets, remote diagnostics and predictive maintenance directly reduce downtime. Independent workshops and the right-to-repair debate make secure but fair access to diagnostic data a policy issue as well as a technical one.
Key sources & further reading
- ISO 17978-3:2026 — SOVD API (paid) and ASAM SOVD.
- ISO 14229-1:2020 (UDS) and ISO 13400 (DoIP) — paid.
- Vector: complete SOVD solution — a practical migration model (vendor material).