Tuning Wiki

This is a historical revision. Read the current page or return to its history.

Page organisation in this revision
Page type
Technical article
Subject
Protocols
Parent
Section level
Applies to
No ECU-specific applicability
Tool groups
None
Manufacturers
None

Changes from revision 1 to revision 2

Removed text is struck through; added text is highlighted.

ISO 14229-3 defines the UDS application profile for CAN. Use ISO-TP to reconstruct a multi-frame payload before interpreting its diagnostic service identifier and parameters.UDS over CAN. Original Tuning Wiki diagram.Reading the network or diagnostic traceFor a read-data response, separate the service identifier, data identifier and record bytes. The ECU documentation defines the record layout and supported identifiers.See ISO-TP on CAN and the vehicle diagnostics protocol guide.Sources: ACTIA IME overview and standard or technical reference.Detailed reference

Unified Diagnostic Services (UDS) defines the diagnostic requests a tester sends to an ECU and the responses the ECU returns. ISO 14229-3 defines how UDS is implemented on CAN, building on the diagnostic services and session-layer requirements in ISO 14229-1 and ISO 14229-2.

Reading a diagnostic trace

Use the CAN identifier and the applicable addressing format to work out which diagnostic conversation a frame belongs to. Consult OBD-II and UDS diagnostic CAN IDs for 11-bit and 29-bit examples and manufacturer addressing context.Use ISO-TP on CAN to recover the diagnostic payload. A short message can fit into one CAN frame. Longer messages are split across frames and reassembled by the receiver.Interpret the resulting UDS payload as a service request or response, such as a request to read a diagnostic data identifier. Use the ECU documentation to establish which services and identifiers it supports.

ISO-TP also carries legislated OBD traffic. When identifying a protocol in a trace, check the diagnostic payload and vehicle documentation as well as the CAN identifier.

Related references

CAN bus ID databaseCAN bus in the car

Sources

ISO 14229-3:2022, Unified diagnostic services on CAN implementationISO 15765-2:2024, Transport protocol and network layer services

Rendered revisions

Open each version to inspect formatting, tables and photographs.

Revision 1: UDS over CAN

Unified Diagnostic Services (UDS) defines the diagnostic requests a tester sends to an ECU and the responses the ECU returns. ISO 14229-3 defines how UDS is implemented on CAN, building on the diagnostic services and session-layer requirements in ISO 14229-1 and ISO 14229-2.

Reading a diagnostic trace

  1. Use the CAN identifier and the applicable addressing format to work out which diagnostic conversation a frame belongs to. Consult OBD-II and UDS diagnostic CAN IDs for 11-bit and 29-bit examples and manufacturer addressing context.
  2. Use ISO-TP on CAN to recover the diagnostic payload. A short message can fit into one CAN frame. Longer messages are split across frames and reassembled by the receiver.
  3. Interpret the resulting UDS payload as a service request or response, such as a request to read a diagnostic data identifier. Use the ECU documentation to establish which services and identifiers it supports.

ISO-TP also carries legislated OBD traffic. When identifying a protocol in a trace, check the diagnostic payload and vehicle documentation as well as the CAN identifier.

Related references

Sources

Revision 2: UDS over CAN

ISO 14229-3 defines the UDS application profile for CAN. Use ISO-TP to reconstruct a multi-frame payload before interpreting its diagnostic service identifier and parameters.

UDS service, ISO-TP transport, CAN link
UDS over CAN. Original Tuning Wiki diagram.

Reading the network or diagnostic trace

For a read-data response, separate the service identifier, data identifier and record bytes. The ECU documentation defines the record layout and supported identifiers.

See ISO-TP on CAN and the vehicle diagnostics protocol guide.

Sources: ACTIA IME overview and standard or technical reference.

Detailed reference

Unified Diagnostic Services (UDS) defines the diagnostic requests a tester sends to an ECU and the responses the ECU returns. ISO 14229-3 defines how UDS is implemented on CAN, building on the diagnostic services and session-layer requirements in ISO 14229-1 and ISO 14229-2.

Reading a diagnostic trace

  1. Use the CAN identifier and the applicable addressing format to work out which diagnostic conversation a frame belongs to. Consult OBD-II and UDS diagnostic CAN IDs for 11-bit and 29-bit examples and manufacturer addressing context.
  2. Use ISO-TP on CAN to recover the diagnostic payload. A short message can fit into one CAN frame. Longer messages are split across frames and reassembled by the receiver.
  3. Interpret the resulting UDS payload as a service request or response, such as a request to read a diagnostic data identifier. Use the ECU documentation to establish which services and identifiers it supports.

ISO-TP also carries legislated OBD traffic. When identifying a protocol in a trace, check the diagnostic payload and vehicle documentation as well as the CAN identifier.

Related references

Sources