RS-485: Imported from Wikipedia (overwrite)

2026-05-03T14:41:26Z

Imported from Wikipedia (overwrite)

New page

{{Short description|Diagnostic communication protocol}}
'''Unified Diagnostic Services''' ('''UDS''') is a diagnostic [[communication protocol]] used by [[electronic control unit]]s (ECUs) in automotive electronics.<ref>{{Cite web|url=https://www.iso.org/standard/72439.html|title=Iso 14229-1:2020 Unified diagnostic services (UDS) Part 1: Application layer}}</ref> UDS is defined by ISO 14229 and evolved from ISO 14230 ([[KWP2000]]), which is now largely obsolete. UDS specifies functionality at the session, presentation, and application layers (layers 5–7) of the [[OSI model]]. Because of this, it can operate on different physical and data link layers such as [[Controller Area Network|CAN]] (ISO 11898), [[Local Interconnect Network|LIN]] (ISO 17987), [[Ethernet]] (ISO 13400), [[FlexRay]] (ISO 17458), and K-Line (ISO 14230). In practice, UDS is most commonly used over [[CAN bus|CAN]] via ''Diagnostic over CAN'' (DoCAN), defined in [[ISO 15765-2|ISO 15765]].

The term "unified" refers to the fact that UDS is an [[international standard]] rather than a manufacturer-specific protocol. Today, nearly all Tier 1 suppliers implement UDS in [[Electronic control unit|ECUs]] developed for automotive [[Original equipment manufacturer|original equipment manufacturers (OEMs)]]. UDS is also integrated into larger software architectures, including [[AUTOSAR]].

Modern vehicles have a diagnostic interface for [[on-board diagnostics]], which makes it possible to connect a computer (client) or diagnostics tool, which is referred to as tester, to the communication system of the vehicle. Thus, UDS requests can be sent to the controllers which provide responses (this may be positive or negative). This makes it possible to [[Interrogation|interrogate]] the fault memory of the individual control units, to update them with new [[firmware]], have low-level interaction with their hardware (e.g. to turn a specific output on or off), or to make use of special functions (referred to as routines) to attempt to understand the environment and operating conditions of an ECU to be able to [[diagnose]] faulty or otherwise undesirable behavior.

== Services ==

SID (Service Identifier)<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#service-identifier |access-date=2025-11-09 |website=uds.readthedocs.io |language=en}}</ref>
{| Class = "wikitable sortable"
|-
! Request Service Identifier (SID) !! Response Service Identifier (RSID) !! Service name !! Description
|-
| Style = "text-align: center" | 0x10
| Style = "text-align: center" | 0x50
| DiagnosticSessionControl<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (DiagnosticSessionControl) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#diagnosticsessioncontrol-0x10 |access-date=2025-11-09 |website=uds.readthedocs.io |language=en}}</ref>
| '''DiagnosticSessionControl''' service is used to change diagnostic sessions in the server(s). In each diagnostic session a different set of diagnostic services (and/or functionalities) is enabled in the server.
Server shall always be in exactly one diagnostic session.
|-
| Style = "text-align: center" | 0x11
| Style = "text-align: center" | 0x51
| ECUReset<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (ECUReset) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#ecureset-0x11 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''ECUReset''' service is used by the client to request that the server perform a reset. The server, after receiving this request, performs the specified type of reset (either before or after transmitting the positive response).
|-
| style="text-align: center" | 0x14
| style="text-align: center" | 0x54
| ClearDiagnosticInformation<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (ClearDiagnosticInformation) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#cleardiagnosticinformation-0x14 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''ClearDiagnosticInformation''' service is used by the client to clear [[Diagnostic Trouble Code|Diagnostic Trouble Codes (DTCs)]] and related data stored in one or more server memories.
|-
| style="text-align: center" | 0x19
| style="text-align: center" | 0x59
| ReadDTCInformation<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (ReadDTCInformation) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#readdtcinformation-0x19 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''ReadDTCInformation''' service allows the client to request current [[Diagnostic Trouble Code|Diagnostic Trouble Code (DTC)]] information from one or more servers within the vehicle.
|-
| style="text-align: center" | 0x22
| style="text-align: center" | 0x62
| ReadDataByIdentifier<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (ReadDataByIdentifier) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#readdatabyidentifier-0x22 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''ReadDataByIdentifier''' service allows the client to request data record values from the server identifier by one or more DataIdentifiers (DIDs).
|-
| style="text-align: center" | 0x23
| style="text-align: center" | 0x63
| ReadMemoryByAddress<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (ReadMemoryByAddress) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#readmemorybyaddress-0x23 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''ReadMemoryByAddress''' service allows the client to request server's memory data stored under provided memory address.
|-
| style="text-align: center" | 0x24
| style="text-align: center" | 0x64
| ReadScalingDataByIdentifier<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (ReadScalingDataByIdentifier) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#readscalingdatabyidentifier-0x24 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
|'''ReadScalingDataByIdentifier''' service allows the client to request the scaling information associated with a Data Identifier (DID). Scaling data provides information required to correctly interpret the actual data value, such as:

* data encoding type (e.g. integer, floating-point, ASCII)
* units and formats
* conversion formulas and coefficients
* bit mappings, and other interpretation details
|-
| style="text-align: center" | 0x27
| style="text-align: center" | 0x67
| SecurityAccess<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (SecurityAccess) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#securityaccess-0x27 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''SecurityAccess''' service allows the client to unlock functions/services with restricted access.
Unlocking sequence:

# The client requests a seed from the server.
# The server responds with a positive response that includes a randomly generated seed value.
# Both the client and server compute a key value based on the seed (using a secret algorithm).
# The client sends the computed key to the server.
# The server validates the client by comparing the received key with its own calculated key. If they match, the client is granted access to the protected functionality for the corresponding security level.
|-
| style="text-align: center" | 0x28
| style="text-align: center" | 0x68

| CommunicationControl<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (CommunicationControl) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#communicationcontrol-0x28 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''CommunicationControl''' service allows the client to switch on/off the transmission and/or the reception of certain messages on the server(s).
|-
| style="text-align: center" | 0x29
| style="text-align: center" | 0x69
| Authentication<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (Authentication) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#authentication-0x29 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''Authentication''' service provides a mechanism for the client to prove its identity, allowing access to data and/or diagnostic services that have restricted access due to security, emissions, or safety requirements.
It is an alternative for '''SecurityAccess''' service.
|-
| Style = "text-align: center" | 0x2A
| Style = "text-align: center" | 0x6A
| ReadDataByPeriodicIdentifier<ref name=":0">{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (ReadDataByPeriodicIdentifier) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#readdatabyperiodicidentifier-0x2a |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''ReadDataByPeriodicIdentifier''' service allows the client to request periodic transmission of data record values from the server. Each periodic data record is identified by Periodic DID (the second byte of a DID with a fixed first byte 0xF2).
|-
| Style = "text-align: center" | 0x2C
| Style = "text-align: center" | 0x6C
| DynamicallyDefineDataIdentifier<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (DynamicallyDefineDataIdentifier) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#dynamicallydefinedataidentifier-0x2c |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''DynamicallyDefineDataIdentifier''' service allows the client to define Data Identifiers.
|-
| Style = "text-align: center" | 0x2E
| Style = "text-align: center" | 0x6E
| WriteDataByIdentifier<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (WriteDataByIdentifier) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#writedatabyidentifier-0x2e |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''WriteDataByIdentifier''' service allows the client to set data values stored under given Data Identifier.
|-
| style="text-align: center" | 0x2F
| style="text-align: center" | 0x6F
| InputOutputControlByIdentifier<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (InputOutputControlByIdentifier) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#inputoutputcontrolbyidentifier-0x2f |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''InputOutputControlByIdentifier''' service allows the client to take temporary control over Data Identifier values.
|-
| style="text-align: center" | 0x31
| style="text-align: center" | 0x71
| RoutineControl<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (RoutineControl) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#routinecontrol-0x31 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''RoutineControl''' service allows the client to execute any sequence of actions that are defined as routines. Each routine has Routine Identifier assigned.
|-
| style="text-align: center" | 0x34
| style="text-align: center" | 0x74
| RequestDownload<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (RequestDownload) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#requestdownload-0x34 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''RequestDownload''' service allows the client to initiate data transfer from the client to the server.
|-
| style="text-align: center" | 0x35
| style="text-align: center" | 0x75
| RequestUpload<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (RequestUpload) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#requestupload-0x35 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''RequestUpload''' service allows the client to initiate data transfer from the server to the client.
|-
| style="text-align: center" | 0x36
| style="text-align: center" | 0x76
| TransferData<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (TransferData) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#transferdata-0x36 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''TransferData''' service transfers the actual data that were earlier requested by either '''RequestDownload''', '''RequestUpload''' or '''RequestFileTransfer''' service'''.'''
|-
| style="text-align: center" | 0x37
| style="text-align: center" | 0x77
| RequestTransferExit<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (RequestTransferExit) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#requesttransferexit-0x37 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''RequestTransferExit''' services ends the data transmission using '''TransferData''' service.
|-
| style="text-align: center" | 0x38
| style="text-align: center" | 0x78
| RequestFileTransfer<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (RequestFileTransfer) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#requestfiletransfer-0x38 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''RequestFileTransfer''' service allows the client to initiate a file transfer (either download or upload).
It is an alternative for '''RequestDownload''' and '''RequestUpload''' services.
|-
| Style = "text-align: center" | 0x3D
| Style = "text-align: center" | 0x7D
| WriteMemoryByAddress<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (WriteMemoryByAddress) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#writememorybyaddress-0x3d |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''WriteMemoryByAddress''' service allows the client to set values directly in the server's memory.
|-
| style="text-align: center" | 0x3E
| style="text-align: center" | 0x7E
| TesterPresent<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (TesterPresent) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#testerpresent-0x3e |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''TesterPresent''' service informs server(s) that the diagnostic tester device (client) is connected and server(s) shall not exit their current diagnostic session.
|-
| style="text-align: center;" |''0x83''
| style="text-align: center;" |''0xC3''
|''AccessTimingParameter<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Services (AccessTimingParameter) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#accesstimingparameter-0x83 |access-date=2026-01-08 |website=uds.readthedocs.io |language=en}}</ref>''
|'''''AccessTimingParameter''' was withdrawn in ISO 14229-1:2020.''
|-
| style="text-align: center;" |0x84
| style="text-align: center;" |0xC4
|SecuredDataTransmission<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (SecuredDataTransmission) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#secureddatatransmission-0x84 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
|'''SecuredDataTransmission''' service allows the client to secure UDS communication using either encryption or signature.
|-
| style="text-align: center" | 0x85
| style="text-align: center" | 0xC5
| ControlDTCSettings<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (ControlDTCSetting) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#controldtcsetting-0x85 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''ControlDTCSettings''' service allows the client to manage DTCs' statuses updating.
|-
| style="text-align: center" | 0x86
| style="text-align: center" | 0xC6
| ResponseOnEvent<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (ResponseOnEvent) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#responseonevent-0x86 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
|'''ResponseOnEvent''' service allows the client to define events and request messages that the server is supposed to respond to when the event occurs.
This can be used to diagnose complicated issues. For example the client can request from the server to respond to '''ReadMemoryByAddress''' request (to provide detailed information about the reason for DTC reporting) when ''testFailed'' bit of a certain DTC is set.
|-
| style="text-align: center" | 0x87
| style="text-align: center" | 0xC7
| LinkControl<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (LinkControl) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#linkcontrol-0x87 |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>
| '''LinkControl''' service allows the client to change physical connection parameters.
As an example, for [[CAN bus]], the client could change [[baudrate]] and version of CAN protocol (e.g. from CAN-FD to Classical CAN).
|}

== Diagnostic Message ==
There are two types of diagnostic messages transmitted using UDS protocol:

* Request
* Response

=== Request Message ===
Request messages are transmitted by a Client towards one or more Servers.<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Message (Diagnostic Request) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/diagnostic_message.html#diagnostic-request |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>

Service Identifier (SID) is the first byte in each request message.<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (SID) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#request-service-identifier |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>

=== Response Message ===
Response messages are transmitted by Servers to a Client.<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Message (Diagnostic Response) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/diagnostic_message.html#diagnostic-response |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref>

The first byte in the response message is usually Response Service Identifier (RSID) value (with the exception of following responses to ReadDataByPeriodicIdentifier service).<ref>{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Service (RSID) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/service.html#response-service-identifier |access-date=2025-11-11 |website=uds.readthedocs.io |language=en}}</ref><ref name=":0" />

==== Positive Response Message ====
Format of each positive response message is specific for the diagnostic service it relates to.

==== Negative Response Message ====
{| class="wikitable"
|+Negative Response Message format
!Byte
!Value
!Description
|-
|#1
|0x7F
|Negative Response SID
|-
|#2
|SID
|SID value from request message
|-
|#3
|NRC
|reason for the rejection
|}

===== Negative Response Codes =====
Negative Response Codes (NRC in short) carry the information for request message rejection.<ref name=":1">{{Cite web |last=Dąbrowski |first=Maciej |title=Diagnostic Message (Negative Response Codes) — py-uds documentation |url=https://uds.readthedocs.io/en/stable/pages/knowledge_base/diagnostic_message.html#negative-response-code |access-date=2025-11-09 |website=uds.readthedocs.io |language=en}}</ref>
{| class="wikitable"
|+Negative Response Codes<ref name=":1" />
! Value!! Name
|-
| 0x10 || generalReject
|-
| 0x11 || serviceNotSupported
|-
| 0x12 || SubFunctionNotSupported
|-
| 0x13 || incorrectMessageLengthOrInvalidFormat
|-
| 0x14 || responseTooLong
|-
| 0x21 || busyRepeatRequest
|-
| 0x22 || conditionsNotCorrect
|-
| 0x24 || requestSequenceError
|-
| 0x25 || noResponseFromSubnetComponent
|-
| 0x26 || FailurePreventsExecutionOfRequestedAction
|-
| 0x31 || requestOutOfRange
|-
| 0x33 || securityAccessDenied
|-
| 0x34 || authenticationRequired
|-
| 0x35 || invalidKey
|-
| 0x36 || exceedNumberOfAttempts
|-
| 0x37 || requiredTimeDelayNotExpired
|-
| 0x38 || secureDataTransmissionRequired
|-
| 0x39 || secureDataTransmissionNotAllowed
|-
| 0x3A || secureDataVerificationFailed
|-
| 0x50 || Certificate verification failed, Invalid Time Period
|-
| 0x51 || Certificate verification failed, Invalid Signature
|-
| 0x52 || Certificate verification failed, Invalid Chain of Trust
|-
| 0x53 || Certificate verification failed, Invalid Type
|-
| 0x54 || Certificate verification failed, Invalid Format
|-
| 0x55 || Certificate verification failed, Invalid Content
|-
| 0x56 || Certificate verification failed, Invalid Scope
|-
| 0x57 || Certificate verification failed, Invalid Certificate ''(revoked)''
|-
| 0x58 || Ownership verification failed
|-
| 0x59 || Challenge calculation failed
|-
| 0x5A || Setting Access Rights failed
|-
| 0x5B || Session key creation/derivation failed
|-
| 0x5C || Configuration data usage failed
|-
| 0x5D || DeAuthentication failed
|-
| 0x70 || uploadDownloadNotAccepted
|-
| 0x71 || transferDataSuspended
|-
| 0x72 || generalProgrammingFailure
|-
| 0x73 || wrongBlockSequenceCounter
|-
| 0x78 || requestCorrectlyReceived-ResponsePending
|-
| 0x7E || SubFunctionNotSupportedInActiveSession
|-
| 0x7F || serviceNotSupportedInActiveSession
|-
| 0x81 || rpmTooHigh
|-
| 0x82 || rpmTooLow
|-
| 0x83 || engineIsRunning
|-
| 0x84 || engineIsNotRunning
|-
| 0x85 || engineRunTimeTooLow
|-
| 0x86 || temperatureTooHigh
|-
| 0x87 || temperatureTooLow
|-
| 0x88 || vehicleSpeedTooHigh
|-
| 0x89 || vehicleSpeedTooLow
|-
| 0x8A || throttle/PedalTooHigh
|-
| 0x8B || throttle/PedalTooLow
|-
| 0x8C || transmissionRangeNotInNeutral
|-
| 0x8D || transmissionRangeNotInGear
|-
| 0x8F || brakeSwitch(es)NotClosed (Brake Pedal not pressed or not applied)
|-
| 0x90 || shifterLeverNotInPark
|-
| 0x91 || torqueConverterClutchLocked
|-
| 0x92 || voltageTooHigh
|-
| 0x93 || voltageTooLow
|-
| 0x94 || ResourceTemporarilyNotAvailable
|}

==See also==
*[[On-board diagnostics]], general article about diagnostic services in vehicles
*[[OBD-II PIDs]], about the US standard
*[https://uds.readthedocs.io/en/stable/pages/knowledge_base.html UDS Knowledge Base - py-uds package]

==References==
{{Reflist}}

==External links==
*[https://automotive.softing.com/fileadmin/sof-files/pdf/de/ae/poster/UDS_Faltposter_softing2016.pdf Unified Diagnostic Services - ISO 14229] (poster by softing.com)
*[https://www.peak-system.com/produktcd/Pdf/English/PCAN-UDS-API_UserMan_eng.pdf PCAN-UDS 2.x API description]

[[Category:Automotive technologies]]
[[Category:Embedded systems]]

Unified Diagnostic Services - Revision history

RS-485: Imported from Wikipedia (overwrite)