Named DIDs
Discovered identifiers show their real name from the ODX/CDD, so results read like your diagnostic spec, not a hex dump.
Engine · Diagnostics
Your ODX and CDD, turned into tests.
Upload the diagnostic description you already have. AutoST names every DID it discovers and calls exactly the routines the ECU defines, instead of guessing.
In short
AutoST imports ODX, ODX-D, PDX and Vector CDD files per ECU and normalises them into data identifiers and routines. The DID names enrich the enumeration results, so a discovered identifier shows its real name instead of a raw number. Routines (UDS service 0x31) are never brute-forced: AutoST calls only the routines defined in your file, with the request payload you can override, and stores the request and response. Optional write-probing (0x2E) is destructive, off by default and clearly warned.
From file to findings
What the import gives you
Real routines
AutoST starts routines (0x31) defined in your file and reads their results, with a payload you can override per routine.
Write-probing
Optionally probe DID writes (0x2E) with wrong-length and write-back checks. Destructive, off by default, confirmed before it runs.
Formats
The files you already have
AutoST reads ODX and PDX (the ASAM standard) and Vector CDD (Candela). You attach the file to the ECU once, and every scan uses it.
Because routines come from your description and not from brute force, the scan is faster, safer and maps directly onto the ECU your team knows.
- ODX, ODX-D and PDX (ASAM)
- Vector CDD (Candela XML)
- Per-ECU, reused across scans
- Confidential files stay on your instance
FAQ
Frequently asked questions
Which diagnostic formats are supported?
ODX, ODX-D, PDX and Vector CDD. AutoST normalises them into a list of DIDs and routines.
Are routines brute-forced?
No. Routines cannot be sensibly brute-forced, so AutoST only calls the routines defined in your ODX/CDD, with a payload you can override.
Is write-probing dangerous?
Writing to an ECU can change its state, so write-probing (0x2E) is destructive, switched off by default and requires explicit confirmation.
See it on your ECU
Run AutoST on your own ECU
In one hour we scope a pilot: your bench, your protocols, the targets and what success looks like.
- A concrete test plan for your setup
- Works on CAN, CAN FD, DoIP and SOME/IP
- NDA on request before we start
Your demo is withTom ZaubermannFounder of Zyberum, ex-lead of the VW InCar Security Testing Lab
Already trusted by Tier 1, Tier 2 suppliers and OEMs. References on request.
Or send us a message
We reply within one business day.