Contents
StandardISO

ISO 15765-2 (ISO-TP)

Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 2: Transport protocol and network layer services

ISO 15765-2, commonly called ISO-TP, defines how diagnostic messages are carried over CAN, including messages too large to fit in a single CAN frame.

What it is

ISO 15765-2 defines the transport protocol and network layer services used to carry diagnostic messages over CAN. Engineers usually call it ISO-TP. It sits between an application protocol, such as Unified Diagnostic Services (UDS), and the CAN communication layer.

A diagnostic message can exceed the payload available in one CAN frame. ISO-TP provides rules for splitting that message into frames and rebuilding it at the receiver. It supports Classical CAN and CAN FD; the applicable vehicle requirements determine which is used. ISO describes the transport service as unconfirmed: completing a transfer does not itself prove that the receiving application accepted or executed a diagnostic request. ISO scope

Who it applies to

The standard is relevant to ECU suppliers, vehicle manufacturers, diagnostic tool developers, and engineers integrating CAN communication stacks. It matters wherever communicating endpoints are required to use ISO-TP, including workshop diagnostics and diagnostic programming over CAN.

Its use normally follows vehicle specifications, customer requirements, or another referencing document. Publication as an ISO standard does not by itself create a legal obligation. Projects must identify the required edition and any additional diagnostic profile or manufacturer constraints.

What it covers

ISO-TP defines transport services, message addressing, segmentation and reassembly, flow control, and timing and error behavior. For a typical segmented exchange, the sender starts the message, the receiver communicates its capacity and pacing requirements, and the sender transmits the remaining data accordingly.

Frame type Purpose
Single Frame Carries a message that fits without segmentation.
First Frame Starts a segmented message and communicates its total length.
Consecutive Frame Carries subsequent message data with sequence information.
Flow Control Communicates receiver readiness, block size, and minimum separation time.

Addressing configuration determines how endpoints identify their communication partners, using CAN identifiers and, for some formats, additional address information. Both endpoints must agree on the selected format. Linux ISO-TP documentation

How it fits with other documents

ISO 11898-1 provides the underlying CAN data link foundation. ISO 15765-2 adds the transport behavior needed to exchange complete diagnostic messages over that foundation.

The ISO 14229 family defines UDS services and associated diagnostic behavior. A request to read data or clear diagnostic information belongs to that application layer; transporting its bytes over CAN is ISO-TP’s job. Other parts of ISO 15765 provide related DoCAN context and requirements.

AUTOSAR CanTp specifications describe a software module implementing CAN transport behavior within an AUTOSAR stack. For diagnostics over IP, ISO 13400 defines DoIP; ISO-TP remains relevant on CAN segments that a diagnostic gateway serves.

In practice

Agree the edition, addressing format, CAN identifiers, CAN frame type, buffer capacity, and timing configuration before integration. Check that the tester, ECU, and any intervening gateway use compatible settings.

Validate both short messages and segmented transfers under realistic bus load. Exercise missing frames, sequence errors, flow-control delays, receiver overflow, and timeout recovery. A successful short request alone provides little evidence that longer transfers will work.

When debugging, inspect the transport exchange before interpreting the UDS payload. A missing flow-control response or an interrupted segmented transfer can prevent a complete request from reaching the diagnostic application. Keep transport failures distinct from UDS negative responses in logs and test reports.

What it means for your discipline

  • Diagnostics & lifecycleCore

    Diagnostic engineers specify and validate how testers and ECUs exchange diagnostic messages over CAN. They must distinguish transport failures from diagnostic service responses.

  • Base softwareCore

    Basic software engineers configure and integrate the CAN transport stack, including addressing, buffers, flow control, and timeouts. In AUTOSAR systems, this work typically involves CanTp and its surrounding communication modules.

  • Networks & communicationCore

    Network engineers allocate diagnostic CAN identifiers and assess transport timing under bus load. They coordinate CAN capabilities and gateway behavior so diagnostic transfers work across the intended vehicle paths.

  • HPC & application softwarePartial

    Application developers must understand the message interface and transport error reporting exposed by the stack. This helps them avoid treating individual CAN frames as complete diagnostic requests.

  • Software update & OTAPartial

    Update engineers using diagnostic programming over CAN must account for segmentation, receiver capacity, and transfer timing. ISO-TP behavior influences download throughput and failure handling.

No direct stake: E/E architecture · Cybersecurity · Functional safety · Hardware & silicon