Contents
StandardISO

ISO 14229 (UDS)

Road vehicles — Unified diagnostic services (UDS)

ISO 14229 defines the diagnostic requests and responses that tools use to inspect, troubleshoot, control and reprogram vehicle electronic control units.

What it is

ISO 14229 is the multi-part standard for Unified Diagnostic Services, usually called UDS. It gives diagnostic clients and ECU servers a common language: a client requests an operation, and the server returns data, confirms completion or explains why the request cannot be performed.

The application layer defines what diagnostic exchanges mean independently of the underlying network. Other parts address their use over particular communication technologies. UDS supports workshop diagnostics, manufacturing tests and ECU programming. It does not define ordinary application messages exchanged between ECUs. The full standard is paid; its scope is publicly described in the ISO catalogue.

Who it applies to

UDS matters to vehicle manufacturers, ECU suppliers, diagnostic-tool developers and teams building onboard diagnostic or programming clients. An onboard update controller can act as a diagnostic client just as a workshop tester can.

Projects select the applicable parts and specify which services each ECU supports. Using UDS does not mean implementing every service. The vehicle manufacturer’s diagnostic specification normally supplies project choices such as identifiers, available routines, access conditions and programming sequences. Contractual requirements and applicable regulations determine what a particular product must provide.

What it covers

UDS defines service requests and responses, including negative responses when an operation is unsupported, incorrectly requested or temporarily unavailable. Sessions and access conditions help determine which operations are permitted.

Service group Typical purpose
Sessions and ECU control Change diagnostic mode, maintain a session or request a reset
Data access Read identification, measurements or configured data
Trouble-code handling Retrieve diagnostic trouble codes and associated information, or request clearing
Input/output and routines Temporarily control supported outputs or execute ECU-defined procedures
Programming Request a download, transfer data and finish a transfer
Access control Support restricted operations through SecurityAccess or Authentication

The standard provides service semantics; the project defines the meaning of individual data items and routines. Authentication can support certificate-based workflows, but a working deployment also needs credential provisioning, trust management and authorization policy.

How it fits with other documents

ISO 14229-1 defines application-layer services, while ISO 14229-2 addresses session-layer services. Network-specific parts adapt UDS to particular communication environments; for example, ISO 14229-3 describes the CAN implementation profile. ISO’s description of that profile explains its relationship to the application and session layers.

ISO 15765-2 supplies transport and network-layer services commonly used beneath UDS on CAN. ISO 13400 defines Diagnostics over Internet Protocol, or DoIP. These documents address delivery of diagnostic messages; UDS supplies their diagnostic meaning.

AUTOSAR diagnostic modules provide an implementation framework. Project diagnostic descriptions and manufacturer requirements connect standardized services to actual ECU data and behavior. Cybersecurity, functional-safety and software-update requirements add constraints that UDS alone does not resolve.

In practice

Start with an ECU diagnostic specification listing supported services, sessions, identifiers, routines, access rules and timing. Make the application, diagnostic stack and bootloader agree on those choices.

For programming, a project might enter a programming session, establish authorized access, check prerequisites, request a download, transfer software, verify it through a routine and reset. The supported sequence is project-specific. UDS does not by itself guarantee image authenticity, rollback protection or recovery after power loss.

Validate unsuccessful paths as carefully as successful ones: denied access, invalid requests, interrupted transfers, session expiry and unavailable operating conditions. A useful diagnostic implementation gives tools predictable responses and leaves the ECU in a defined state.

What it means for your discipline

  • Diagnostics & lifecycleCore

    Owns the supported diagnostic services, data identifiers, trouble-code access and tester behavior. Defines and verifies requests, responses, timing and error handling.

  • Base softwareCore

    Implements and configures diagnostic service handling, session behavior and application callbacks. Connects the diagnostic stack to fault storage, communication and bootloader functions.

  • Software update & OTACore

    Defines and validates ECU programming sequences using diagnostic download, transfer, routine and reset services. Coordinates these services with update prerequisites and recovery behavior.

  • CybersecurityPartial

    Defines authorization rules for sensitive diagnostic operations and integrates access-control services. Checks that authentication and session handling enforce the vehicle's security policy.

  • HPC & application softwarePartial

    Provides application data and routines exposed through diagnostics. Implements handlers with predictable results, appropriate access checks and defined failure behavior.

  • Networks & communicationPartial

    Ensures diagnostic traffic reaches the correct ECU through the chosen transport and gateways. Investigates addressing, timing and connection behavior alongside service-level responses.

  • E/E architecturePartial

    Allocates diagnostic clients, servers and gateway responsibilities across the vehicle. Defines how workshop tools and onboard update controllers reach ECUs.

  • Functional safetyPartial

    Reviews diagnostic operations that can affect actuators, communication or ECU availability. Defines operating conditions and safeguards with the diagnostic and application teams.

No direct stake: Hardware & silicon