From the UDS server inside a constrained ECU, through SOVD on the vehicle HPC, to the pass-thru on the workshop bench. Every layer to the standard. Every layer from one supplier.
DOIP SERVER FOOTPRINT
UDS SERVER FOOTPRINT
FOR A 20 MB BLOCK TRANSFER
One codebase behaves the same way at end-of-line, in the workshop and remotely. That consistency is the point.
J2534 v05.00
ISO 22900-2
SOVD / HTTPS
ISO 17978
UDS client · Classic Diagnostic Adapter
SOVD server · ISO 17978
J2534 v05.00ISO 22900-2
01 — In the ECU
A diagnostic server for targets where memory is scarce. No AUTOSAR dependency: runs on FreeRTOS, Zephyr, bare-metal, embedded Linux and Android Automotive.
ISO 14229:2021 · ISO 13400:2025
02 — In the vehicle
The Classic Diagnostic Adapter translates between SOVD and classic UDS, so legacy ECUs stay reachable from a service-oriented architecture.
ISO 17978
03 — In the workshop
Both standardised access APIs, plus D-Server and OTX runtime. One software base covers the European and North American access regimes.
SAE J2534 v05.00 · ISO 22900-2 · ISO 22900-3
04 — In the cloud
Remote diagnostics without a second implementation. The behaviour you validated at end-of-line is the behaviour you get over the air.
SOVD over HTTPS
Our diagnostic server implements ISO 14229:2021 and ISO 13400:2025 and runs where memory is scarce.
DoIP server
DoIP server
22 KB
UDS server1
24 KB
Block transfer
20 MB in 470 ms
LanguagesRust ·
C/C++
Targets
FreeRTOS · Zephyr · bare-metal · Linux · AAOS
Independent : no AUTOSAR dependency. If your ECU is not an AUTOSAR node, you should not need an AUTOSAR stack to make it diagnosable.
Memory-safe : a complete UDS server and client implementation in Rust, in production, compiled with a qualified toolchain. Not a research topic when your diagnostic server is exposed on the vehicle network over DoIP.
Concurrent : native multi-client DoIP. Several testers, one ECU, no queueing.
Data-driven : configuration generated from ODX. Your existing diagnostic database drives the code, not a parallel hand-maintained configuration.
Long-lived : services 0x27 and 0x29 with authentication designed for vehicles that will still be on the road in 2045.
ACTIA experts have contributed to ISO 17978 since version 1.1, inside the ASAM working group and ISO WG5. We offer two ways to adopt it, and we will not push you toward one.
Our UDS client integrates with Eclipse OpenSOVD and its Classic Diagnostic Adapter.
A complete server with the plugins and generation chain around it.
Most suppliers can only sell you Route B. If avoiding lock-in matters to your organisation, Route A exists — and we will help you take it.
The Diagnostic Event Manager is where safety mechanisms report their faults. Reading a DTC is not safety-relevant; losing a fault report is.
The DCM and transport layers remain QM by architectural choice, with documented freedom from interference.
We provide the documentation your integration team actually needs to close its own safety case.
Vulnerabilities in our components are monitored and reported to you throughout the product lifecycle.
ACTIA has been a permanent member of ASAM and ISO for more than twenty years.
Our engineers contribute to ISO 17978 (SOVD) and ISO 13209 (OTX).
Permanent member for over twenty years, inside the SOVD working group since version 1.1.
Contributing Member, and Supporter Member of the Eclipse SDV Working Group.
Active contributor to both projects.
Non-exclusive
One-time fee or per-vehicle. Your choice, not ours.
Binary or source code
Source delivery is a normal option here, not an exception.
Engineering support
Integration, customisation, maintenance, training, and Build-Operate-Transfer models.
A real ECU. A fault you trigger yourself. The result as a SOVD resource in your browser — in under three minutes.