UDS

Unified Diagnostic Service

ISO-14229

@ Gowthamraj Mahadevan
 UDS

an
UDS is a standard protocol (ISO 14229) that allows

ev
diagnostic tools to talk directly with a vehicle's
electronic control units (ECUs).

ad
https://nvdungx.github.io/unified-diagnostic-protocol-overview/

ah
jM
ra
am
th
w
Go
 What is UDS?

an
UDS is a client-server diagnostic communication

ev
protocol used in automotive electronics.

ad
It allows diagnostic tools (clients or testers) to
communicate with vehicle ECUs (servers) to perform

ah
various diagnostic and control functions.

Client (Tester): This is usually a diagnostic tool or

jM
software that sends requests to the ECU. It can be
an off-board scan tool used by mechanics or an
ra

onboard tester used in manufacturing plants.

am

Server (ECU): The ECU is the embedded system

inside the vehicle that responds to the tester’s
requests. It provides services such as reading fault
th

codes, running tests, resetting itself, and updating

software.
w
Go
 What is UDS?

an
ev
ad
ah
jM
https://piembsystech.com/uds-protocol/
ra
am

https://piembsystech.com/uds-protocol/
th
w
Go
 an
Why is UDS Important?

ev
Universal Standard: Accepted globally by OEMs (Original

Equipment Manufacturers), making diagnostics interoperable.

ad
Rich Diagnostic Functions: Supports reading/clearing fault

ah
codes, ECU programming, security access, and routine control.

Session Management: Allows switching between different

jM
diagnostic sessions with varying access levels.

Security: Implements security access to protect critical

ra

functions like firmware updates.

Extensibility: Supports custom functions and flexible sub-

am

functions for advanced diagnostics.

th
w
Go
 How Does UDS Work?

an
UDS operates on a request-response model over communication

ev
buses like CAN (Controller Area Network).

ad
Here is a simplified overview:

ah
1. Tester Sends Request: The diagnostic tool sends a request

message to the ECU. This message contains a Service Identifier

jM
(SID) that specifies the requested diagnostic service.

2. ECU Processes Request: The ECU interprets the SID and

ra

executes the requested service.

3. ECU Sends Response: The ECU replies with either a positive

am

response containing the requested data or a negative response

indicating an error.
th
w
Go
 How Does UDS Work?

an
Example

To read the ECU software version, the tester sends a request

ev
with SID 0x22 (Read Data by Identifier) and a Data Identifier

(DID) specifying the software version.

ad
The ECU responds with SID 0x62 plus the software version data

ah
if successful.

If the request fails, the ECU sends a negative response with SID
jM
0x7F and an error code.
ra
am
th
w
Go

https://nvdungx.github.io/unified-diagnostic-protocol-overview/
 an
Important UDS Services (SIDs)

ev
There are many services in UDS, but let's focus on the most commonly used ones:

ad
Service Description Example

ah
0x10 Diagnostic Session Control Switch to programming mode

0x11 ECU Reset Ask ECU to restart itself

0x14
jMClear Diagnostic Information Clear all stored fault codes

Read DTCs (Diagnostic Trouble

0x19 Read fault memory
Codes)
ra

0x22 Read Data By Identifier Get sensor values or VIN number

0x2E Write Data By Identifier Change configuration values

am

0x27 Security Access Unlock ECU for programming

0x34 Request Download Start programming new software

0x36 Transfer Data Send chunks of software

th

0x37 Request Transfer Exit Complete programming session

w
Go
 an
Key Diagnostic Services in UDS

ev
1. Diagnostic and Communication Management:

ad
Manages diagnostic sessions and communication settings.

2. Data Transmission: Allows reading and writing of ECU data.

ah
3. Stored Data Transmission
jM
4. Input/Output Control: Controls ECU inputs and outputs for

testing.
ra

5. Remote Activation of Routine: Runs specific routines or tests.

am

6. Upload/Download:Used for ECU programming and data transfer.

th
w
Go
 Positive and Negative Responses

an
When a tester sends a request:

ev
If everything is OK, ECU replies with a positive response

ad
(starting with 0x50, 0x62, etc.).
If something is wrong (bad request, timing issue, security lock),
ECU sends a negative response (0x7F) with an error code.

ah
Common Negative Response Codes (NRCs):
jM
0x11: Service Not Supported
0x12: Sub-function Not Supported
0x13: Incorrect Message Length
ra

0x31: Request Out of Range

0x33: Security Access Denied
am
th
w
Go
 Example

an
ev
Reading ECU Software Version

Tester sends: 0x22 0xF1 0x80

ad
0x22 = Read Data by Identifier
0xF180 = DID for software version

ah
ECU responds: 0x62 + software version bytes
jM
If failed, ECU responds: 0x7F 0x22 <error_code>

https://piembsystech.com/uds-protocol/
ra
am
th
w
Go
 an
FOR EXTENSIVE UDS CONTENT
SCAN BELOW QR CODE

ev
ad
ah
jM
ra
am
th
w
Go
Follow for More

@ Gowthamraj Mahadevan