Why it exists
Workshops need a common way to ask any ECU what is wrong, read data and update software. UDS (Unified Diagnostic Services) is that common language.
What it is
A request/response protocol with numbered services, e.g.:
- 0x10 Diagnostic Session Control (default, extended, programming)
- 0x22 / 0x2E Read / Write Data By Identifier
- 0x19 / 0x14 Read / Clear DTC Information
- 0x31 Routine Control
- 0x27 / 0x29 Security Access / Authentication
- 0x34 / 0x36 / 0x37 Download (reprogramming)
DTCs are fault codes with status bits (e.g. test failed, confirmed) plus snapshot and extended data.
Example for sub-function 0x02 (reportDTCByStatusMask): each item is one byte except the final records, which contain zero or more three-byte DTCs each followed by one status byte; transport headers are omitted.
A UDS negative response contains these three bytes, without a sub-function echo; transport headers are omitted.
How it works in an ECU
Monitors detect faults → Dem debounces them and stores DTCs → a tester reads them via Dcm → workshop repairs → DTCs are cleared.
Best practices
- Define DTCs from the workshop’s perspective: actionable and specific.
- Debounce carefully to avoid false entries.
- Protect write, routine and download services.
Common pitfalls
- DTC floods during low-voltage events or network sleep transitions.