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

A diagnostic connection combines a vehicle network, a way to carry messages, and services that define what a tester can ask for. The scan tool may also use a software interface to reach its vehicle communication adapter. Identify each layer before choosing a tool or interpreting a trace.

From the wire to the application

The OSI model gives each layer a job. Vehicle standards sometimes cover more than one layer. For example, UDS defines services, ISO-TP moves their payloads across CAN frames, and CAN defines frame delivery and signalling through the applicable parts of ISO 11898. UDS can also use DoIP over an IP network.

7 Application, Diagnostic services, UDS. 6 Presentation, Data encoding, Application formats. 5 Session, Session services, ISO 14229-2. 4 Transport, Message transfer, ISO-TP or TCP. 3 Network, Addressing and routing, DoCAN or IP. 2 Data link, Frame delivery, CAN or Ethernet. 1 Physical, Signal transmission, Twisted pair
OSI layers for vehicle diagnostics. Original Tuning Wiki diagram.

Interpreting a CAN diagnostic trace

First identify the network and CAN frame format, then the diagnostic addressing and transport format before interpreting the service bytes. A CAN identifier, an ISO-TP addressing byte and a diagnostic data identifier have different roles; similar numbers do not make them interchangeable. A short ISO-TP message can fit in a single frame. A longer message uses a first frame, flow control and consecutive frames, which must be reassembled before interpreting the complete diagnostic response. Addressing and frame capacities depend on the transport configuration and CAN format. CAN Newsletter: UDS on CAN and ISO-TP.

A CAN acknowledgement indicates that at least one receiver acknowledged a consistent frame; it does not identify the receiver or establish that the intended diagnostic service completed successfully. Examine the diagnostic response and its context separately. CAN in Automation: acknowledgement definition.

Vehicle networks

Transport and diagnostic services

Diagnostic software interfaces and test sequences

Manufacturer-specific CAN

Use the CAN bus ID database to find platform-specific frame identifiers. BMW D-CAN, K-CAN and PT-CAN includes scoped examples of diagnostic requests and a body-network broadcast. Volkswagen TP 2.0 covers negotiated diagnostic channels.

Older manufacturer networks

These pages cover legacy body and infotainment networks and K-line diagnostics. Examples are chassis-specific; each page marks gaps where a sourced CAN ID or read-only frame is unavailable.

Off-highway and equipment CAN

These pages cover CANopen and J1939 applications in forklifts, construction machinery, municipal equipment, collision-avoidance systems, truck-trailer links and machine attachments.

Sources

Topic coverage follows the ACTIA IME vehicle diagnostics index. Individual pages credit their references and include original diagrams.