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.