ISO/FDIS 15765-5

Road vehicles -- Diagnostic communication over Controller Area Network (DoCAN)

Véhicules routiers -- Communication de diagnostic sur gest ionnaire de réseau de communication (DoCAN)

General Information

• Status: Published
• ICS: 43.040.15 - Car informatics. On board computer systems
• ICS: 43.180 - Diagnostic, maintenance and test equipment
• Technical Committee: ISO/TC 22/SC 31 - Data communication
• Drafting Committee: ISO/TC 22/SC 31/WG 2 - Vehicle diagnostic protocols
• Current Stage: 5060 - Close of voting Proof returned by Secretariat
• Start Date: 14-Apr-2021
• Completion Date: 13-Apr-2021

Standards Content (sample)

FINAL
INTERNATIONAL ISO/FDIS
DRAFT
STANDARD 15765-5
ISO/TC 22/SC 31
Road vehicles — Diagnostic
Secretariat: DIN
communication over Controller Area
Voting begins on:
2021-02-16 Network (DoCAN) —
Voting terminates on:
Part 5:
2021-04-13
Specification for an in-vehicle network
connected to the diagnostic link
connector
Véhicules routiers — Communication de diagnostic sur gest ionnaire
de réseau de communication (DoCAN) —
Partie 5: spécification pour un réseau véhicule connecté sur la prise
de diagnostic
RECIPIENTS OF THIS DRAFT ARE INVITED TO
SUBMIT, WITH THEIR COMMENTS, NOTIFICATION
OF ANY RELEVANT PATENT RIGHTS OF WHICH
THEY ARE AWARE AND TO PROVIDE SUPPOR TING
DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
Reference number
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO-
ISO/FDIS 15765-5:2021(E)
LOGICAL, COMMERCIAL AND USER PURPOSES,
DRAFT INTERNATIONAL STANDARDS MAY ON
OCCASION HAVE TO BE CONSIDERED IN THE
LIGHT OF THEIR POTENTIAL TO BECOME STAN-
DARDS TO WHICH REFERENCE MAY BE MADE IN
NATIONAL REGULATIONS. ISO 2021
---------------------- Page: 1 ----------------------
ISO/FDIS 15765-5:2021(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2021

All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may

be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting

on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address

below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
ii © ISO 2021 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/FDIS 15765-5:2021(E)
Contents Page

Foreword ........................................................................................................................................................................................................................................iv

Introduction ..................................................................................................................................................................................................................................v

1 Scope ................................................................................................................................................................................................................................. 1

2 Normative references ...................................................................................................................................................................................... 1

3 Terms and definitions ..................................................................................................................................................................................... 1

4 Symbols and abbreviated terms ........................................................................................................................................................... 1

4.1 Symbols ......................................................................................................................................................................................................... 1

4.2 Abbreviated terms ............................................................................................................................................................................... 2

5 Conventions ............................................................................................................................................................................................................... 3

6 In-vehicle network to external test equipment connection .................................................................................... 3

6.1 Connectivity scenarios between external test equipment and vehicle .................................................. 3

6.2 Technical requirements overview .......................................................................................................................................... 3

6.3 SI — Data.req, Data.ind and Data.conf service interface..................................................................................... 4

6.4 SI — Parameter mapping and configuration of OSI-layers ............................................................................... 5

6.5 Transport layer (TL) ........................................................................................................................................................................... 5

6.5.1 TL – Data interface primitive parameter mapping ............................................................................. 5

6.5.2 TL – Message segmentation ................................................................................................................................... 6

6.5.3 TL ISO 15765-2 packet flow control ............................................................................................................... 6

6.6 Network layer (NL) ............................................................................................................................................................................. 6

6.6.1 NL – Data interface primitive parameter mapping ............................................................................ 6

6.6.2 NL – ISO 15765-2 network layer services .................................................................................................. 7

6.6.3 NL – ISO 15765-2 network layer timing parameters ....................................................................... 7

6.6.4 NL – ISO 15765-2 uniqueness of node diagnostic address ......................................................... 7

6.6.5 NL – ISO 15765-2 supported addressing formats ............................................................................... 7

6.7 Data link layer (DLL) .......................................................................................................................................................................... 8

6.7.1 DLL – Data interface primitive parameter mapping ......................................................................... 8

6.7.2 DLL – Service interface parameter requirements ............................................................................... 9

6.7.3 DLL – Device acceptance of CAN identifier ............................................................................................10

6.8 Physical layer (PHY) ........................................................................................................................................................................10

6.8.1 PHY – Physical signalling (PS) requirements .......................................................................................10

6.8.2 PHY – Physical medium attachment (PMA) requirements ......................................................14

6.8.3 PHY – Physical media dependent (PMD) sub-layer requirements ....................................14

Annex A (informative) Compatibility between test equipment and in-vehicle network

connected to diagnostic link connector .....................................................................................................................................16

Bibliography .............................................................................................................................................................................................................................17

© ISO 2021 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/FDIS 15765-5:2021(E)
Foreword

ISO (the International Organization for Standardization) is a worldwide federation of national standards

bodies (ISO member bodies). The work of preparing International Standards is normally carried out

through ISO technical committees. Each member body interested in a subject for which a technical

committee has been established has the right to be represented on that committee. International

organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.

ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of

electrotechnical standardization.

The procedures used to develop this document and those intended for its further maintenance are

described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the

different types of ISO documents should be noted. This document was drafted in accordance with the

editorial rules of the ISO/IEC Directives, Part 2 (see www .iso .org/ directives).

Attention is drawn to the possibility that some of the elements of this document may be the subject of

patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of

any patent rights identified during the development of the document will be in the Introduction and/or

on the ISO list of patent declarations received (see www .iso .org/ patents).

Any trade name used in this document is information given for the convenience of users and does not

constitute an endorsement.

For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and

expressions related to conformity assessment, as well as information about ISO's adherence to the

World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www .iso .org/

iso/ foreword .html.

This document was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 31,

Data communication.
A list of all parts in the ISO 15765 series can be found on the ISO website.

Any feedback or questions on this document should be directed to the user’s national standards body. A

complete listing of these bodies can be found at www .iso .org/ members .html.
iv © ISO 2021 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/FDIS 15765-5:2021(E)
Introduction

The ISO 15765 series defines common requirements for vehicle diagnostic systems using the controller

area network (CAN), as specified in the ISO 11898 series.

The ISO 15765 series presumes the use of external test equipment for inspection, diagnostics, repair

and other possible use cases connected to the vehicle.

This document does not specify any requirements related to the in-vehicle CAN network architecture.

It defines the requirements to enable the in-vehicle CAN network to successfully establish, maintain

and terminate communication with the devices externally connected to the diagnostic link connector.

This document has been structured according to the open systems interconnection (OSI) basic reference

model, in accordance with ISO/IEC 7498-1 and ISO/IEC 10731, which structures communication systems

into seven layers. When mapped on this model, the OSI layer 4 to OSI layer 1 framework requirements

specified or referenced in the ISO 15765 series are structured according to Figure 1, which shows the

related documents of OSI layer 4 to OSI layer 1.
Figure 1 — CAN documents reference according to OSI model
The documents include the following content:
— transport layer (TL) -related requirements with reference to ISO 15765-2;
— network layer (NL) -related requirements with reference to ISO 15765-2;

— data link layer (DLL) -related requirements with reference to ISO 11898-1, which are composed of:

— DLL protocol entity requirements;
— DLL device interface requirements;
© ISO 2021 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/FDIS 15765-5:2021(E)
— DLL network system requirements;

— physical layer (PHY) -related requirements with reference to ISO 11898-2, which are composed of:

— physical signalling (PS) requirements, which are composed of:
— PS entity requirements;
— PS device interface requirements;
— PS network system requirements;
— physical medium attachment (PMA) requirements, which are composed of:
— PMA protocol entity requirements;
— PMA device interface requirements;
— physical medium dependent (PMD) requirements, which are composed of:
— PMD entity requirements;
— PMD device interface requirements;
— PMD network system requirements.

The PS sub-layer is implemented in the CAN protocol controller. The PMA sub-layer is implemented

normally in the CAN transceiver or the system base chip (SBC). Optionally it may comprise also

additional protection circuitry. The media-dependent sub-layer comprises the connectors and the

cabling.

Figure 2 shows an implementation example of the data link and physical layers block diagram.

Figure 2 — Implementation example of lower OSI layers block diagram

The above structure is chosen to provide the following implementers with relevant requirements:

— transceiver developers;
— device (e.g. electronic control unit) developers;
— system network developers.

All requirements are numbered and headlined uniquely, so that each implementer can reference them.

Annex A provides a description of the compatibility between test equipment and in-vehicle network

connected to the diagnostic link connector.
vi © ISO 2021 – All rights reserved
---------------------- Page: 6 ----------------------
FINAL DRAFT INTERNATIONAL STANDARD ISO/FDIS 15765-5:2021(E)
Road vehicles — Diagnostic communication over
Controller Area Network (DoCAN) —
Part 5:
Specification for an in-vehicle network connected to the
diagnostic link connector
1 Scope

This document specifies the requirements related to the connection between the external test

equipment externally connected to the diagnostic link connector and the in-vehicle CAN network to

successfully establish, maintain and terminate communication.
2 Normative references

The following documents are referred to in the text in such a way that some or all of their content

constitutes requirements of this document. For dated references, only the edition cited applies. For

undated references, the latest edition of the referenced document (including any amendments) applies.

ISO 11898 (all parts), Road vehicles — Controller area network (CAN)

ISO 15031-3, Road vehicles — Communication between vehicle and external equipment for emissions-

related diagnostics — Part 3: Diagnostic connector and related electrical circuits: Specification and use

ISO 15765-2, Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 2:

Transport protocol and network layer services

ISO 15765-4, Road vehicles — Diagnostic communication over Controller Area Networks (DoCAN) —

Part 4: Requirements for emissions-related systems
3 Terms and definitions

For the purposes of this document, the terms and definitions given in the ISO 11898 series, ISO 15765-2

and ISO 15765-4 apply.

ISO and IEC maintain terminological databases for use in standardization at the following addresses:

— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at http:// www .electropedia .org/
4 Symbols and abbreviated terms
4.1 Symbols
– empty table cell or feature undefined
Δf oscillator tolerance
f nominal data bit rate
© ISO 2021 – All rights reserved 1
---------------------- Page: 7 ----------------------
ISO/FDIS 15765-5:2021(E)
f data bit rate
L cable length between in-vehicle CAN node and diagnostic link connector
CABLE
t arbitration bit time
t data bit time
t bit time
BIT
t receive bit time
BIT_RX
t transmit bit time
BIT_TX
t nominal arbitration bit time quantum length
t nominal data bit time quantum length
t arbitration bit synchronisation jump width
SJWa
t data bit synchronisation jump width
SJWd
t time quantum
t nominal arbitration bit sample point position
SPa
t nominal data bit sample point position
SPd
X table cell selected or feature defined
4.2 Abbreviated terms
AE address extension
AL application layer
CAN controller area network
CAN FD controller area network flexible data-rate
CBFF classical base frame format
CEFF classical extended frame format
DCC diagnostic communication channel
DLL data link layer
DoCAN diagnostic communication over controller area network
Ftype frame type
FBFF FD base frame format
FEFF FD extended frame format
L_ data link
MSb most significant bit
Mtype message type
2 © ISO 2021 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/FDIS 15765-5:2021(E)
N_ network
NL network layer
N_PDU network protocol data unit
PDU protocol data unit
PHY physical layer
Ptype packet type
SA source address
SJW synchronisation jump width
SP sample point
T_ transport
TA target address
TAtype target address type
TL transport layer
T_PDU transport protocol data unit
DiagNormAddr diagnostic message with normal addressing
DiagNormFixAddr diagnostic message with normal fixed addressing
DiagExtAddr diagnostic message with extended addressing
RDiagMixAddr remote diagnostic message with mixed addressing
5 Conventions
This document is based on OSI service conventions as specified in ISO/IEC 10731.
6 In-vehicle network to external test equipment connection
6.1 Connectivity scenarios between external test equipment and vehicle

This document specifies the requirements for the diagnostic link connector providing access to CAN FD

network. A backward compatibility to classical CAN is described in Annex A.
6.2 Technical requirements overview

Table 1 provides an overview of the technical requirements and associated requirement numbers.

Table 1 — Technical requirements overview
REQ # Technical requirement title
4 Transport layer (TL)
4.1 TL – ISO 15765-2 T_Data interface primitive parameter mapping
4.2 TL – ISO 15765-2 TX_DL = 8
© ISO 2021 – All rights reserved 3
---------------------- Page: 9 ----------------------
ISO/FDIS 15765-5:2021(E)
Table 1 (continued)
REQ # Technical requirement title
4.3 TL – ISO 15765-2 TX_DL > 8
3 Network layer (NL)
3.1 NL – ISO 15765-2 N_Data interface primitive parameter mapping
3.2 NL – ISO 15765-2 network layer services
3.3 NL – ISO 15765-2 network layer timing parameters
3.4 NL – ISO 15765-2 uniqueness of node diagnostic address
3.5 NL – ISO 15765-2 supported addressing formats
3.6 NL – ISO 15765-2 functional addressing
3.7 NL – ISO 15765-2 reception of N_PDU
2 Data link layer (DLL)

DLL – Data interface primitive parameter mapping – Mapping of upper OSI layer service inter-

2.1
face parameters
2.2 DLL – Data interface primitive parameter mapping – ISO 11898-1
2.3 DLL – Mapping of N_AI into the 11-bit CAN identifier
2.4 DLL – Mapping of N_AI into the 29-bit CAN identifier
2.5 DLL – Device acceptance of CAN identifier
1 Physical layer (PHY)
1.1 PHY – PS entity requirements – ISO 11898-1 conformance
1.2 PHY – PS device interface requirements – Classical CAN bit timing parameters
1.3 PHY – PS device interface requirements – CAN FD sampling method
1.4 PHY – PS device interface requirements – CAN FD bit timing parameters

1.5 PHY – PS device interface requirements – CAN FD transmitter delay compensation

1.6 PHY – PS device interface requirements – Termination resistance
1.7 PHY – PMA entity requirements – ISO 11898-2 conformance
1.8 PHY – PMA entity requirements – Qualification
1.9 PHY – PMD entity requirements – Diagnostic link connector

1.10 PHY – PMD entity requirements – DoCAN pin assignment on diagnostic link connector

PHY – PMD entity requirements – Cable characteristics between vehicle network connected to

1.11
the diagnostic link connector for data bit rates > 500 kbit/s
1.12 PHY – PMD network system requirements

1.13 PHY – PMD network system requirements – Cable length between single CAN node and diagnos-

tic link connector
6.3 SI — Data.req, Data.ind and Data.conf service interface

The service interface defines the service and parameter mapping from the application layer to the

session layer.

Figure 3 shows the Data.req (request), Data.ind (indication) and Data.conf (confirmation) service

interface.
4 © ISO 2021 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/FDIS 15765-5:2021(E)
Key
1 service access point
2 read back from N-layer service provider
Figure 3 — Data.req, Data.ind and Data.conf service interface
6.4 SI — Parameter mapping and configuration of OSI-layers

Each OSI layer contains layer-specific information to manipulate or edit the PDU depending on whether

the PDU is provided as a Data.req (sender), Data.ind (receiver) or Data.conf (receiver).

A PDU, which is sent by an application (service user), is assembled by each applicable OSI-layer based

on PDU identification information. A PDU, which is received by the OSI-layers (service provider), has

PDU identification information used by each applicable OSI layer to disassemble the PDU before it is

transferred to the application (service user).

A specific implementation of the service primitive interface parameter management for each OSI-layer

is not specified in this document.
6.5 Transport layer (TL)
6.5.1 TL – Data interface primitive parameter mapping

This requirement specifies the A_Data to T_Data interface primitive parameter mapping between the

application layer and the TL.
REQ 4.1 TL – ISO 15765-2 T_Data interface primitive parameter mapping

The T_Data service primitive shall use the service primitive parameters as specified in Table 2.

Table 2 — T_Data service primitive parameter mapping
TL .req .ind .conf Description
T_TAtype
X X X target address type: the configurable TX_DL value is an upper bound for
the valid CAN frame data length (CAN_DL) for the transmitting node.
AddrType: (DiagNormAddr, DiagNormFixAddr, DiagExtAddr,
RDiagMixAddr)
T_Length
X X X length of PDU
X Supported.
– Not supported.
© ISO 2021 – All rights reserved 5
---------------------- Page: 11 ----------------------
ISO/FDIS 15765-5:2021(E)
Table 2 (continued)
TL .req .ind .conf Description
T_Data
X X – transport layer data
T_Result
– – X result
X Supported.
– Not supported.
6.5.2 TL – Message segmentation

The TL performs message segmentation into packets of 8 byte. The support of the ISO 15765-2 transport

protocol is determined by the application.
REQ 4.2 TL – ISO 15765-2 TX_DL = 8

The CAN node(s) shall support the transport protocol feature TX_DL = 8 as specified in ISO 15765-2:

— single segment transmission with TX_DL = 8 byte;

— multiple-segments transmission with TX_DL = 8 up to 2 - 1 byte for first packet escape sequence.

The TL performs message segmentation into packets greater than 8 byte. The support of the ISO 15765-2

transport protocol is determined by the application.
REQ 4.3 TL – ISO 15765-2 TX_DL > 8

The CAN node(s) shall support the transport protocol feature TX_DL > 8 as specified in ISO 15765-2:

— single segment transmission with TX_DL > 8 byte;

— multiple segments transmission with TX_DL > 8 up to 2 - 1 data byte for first packet escape

sequence.
6.5.3 TL ISO 15765-2 packet flow control
The TL controls the packet flow by means of the FlowControl packet.
REQ 4.4 TL – ISO 15765-2 definition of Flow Control parameter values

The CAN node(s) shall be capable of adapting to any valid parameter in a FlowControl packet as spec-

ified in ISO 15765-2.
6.6 Network layer (NL)
6.6.1 NL – Data interface primitive parameter mapping

The requirements specified in this subclause are applicable to NL implementations.

REQ 3.1 NL – ISO 15765-2 N_Data interface primitive parameter mapping

The N_Data service primitive shall use the service primitive parameters as specified in Table 3.

6 © ISO 2021 – All rights reserved
---------------------- Page: 12 ----------------------
ISO/FDIS 15765-5:2021(E)
Table 3 — N_Data service primitive parameter mapping
NL .req .ind .conf Description
N_AI[N_TAtype]
X X – [AddrType: (DiagNormAddr, DiagNormFixAddr, DiagExtAddr,
RDiagMixAddr),
N_TAtype #1: physical addressing, CBFF, 11-bit CAN identifier,
N_TAtype #2: functional addressing, CBFF, 11-bit CAN identifier,
N_TAtype #3: physical addressing, FBFF, 11-bit CAN identifier,
N_TAtype #4: functional addressing, FBFF, 11-bit CAN identifier,
N_TAtype #5: physical addressing, CEFF, 29-bit CAN identifier,
N_TAtype #6: functional addressing, CEFF, 29-bit CAN identifier,
N_TAtype #7: physical addressing, FEFF, 29-bit CAN identifier,
N_TAtype #8: functional addressing, FEFF, 29-bit CAN identifier]
N_AI[TA]
X X – target address to be added to PDU if N_TAtype = DiagExtAddr.
N_AI[AE]
X X – address extension to be added to PDU if N_TAtype = RDiagMixAddr.
N_Length
X X X length of PDU
N_Data
X X – network layer data
N_Result
– – X result
X Supported.
– Not supported.
6.6.2 NL – ISO 15765-2 network layer services
A detailed specification of the NL services is given in ISO 15765-2.
REQ 3.2 NL – ISO 15765-2 network layer services
The NL services of the vehicle's ECU(s) shall be in accordance with ISO 15765-2.
6.6.3 NL – ISO 15765-2 network layer timing parameters

A detailed specification of the NL timing parameter values is given in ISO 15765-2.

REQ 3.3 NL – ISO 15765-2 network layer timing parameters

The NL timing parameters of the vehicle's ECU(s) shall be in accordance with ISO 15765-2.

6.6.4 NL – ISO 15765-2 uniqueness of node diagnostic address

The node diagnostic address in a CAN network is used to indicate to all nodes on the network that the

node with this diagnostic address is the targeted.
REQ 3.4 NL – ISO 15765-2 uniqueness of node diagnostic address

The node diagnostic address ('XX ') shall be unique for a node in a given vehicle.

6.6.5 NL – ISO 15765-2 supported addressing formats

ISO 15765-2 specifies several addressing formats. The addressing information is contained in the N_

Ptype N_Data interface parameter.
REQ 3.5 NL – ISO 15765-2 supported addressing formats
© ISO 2021 – All rights reserved 7
---------------------- Page: 13 ----------------------
ISO/FDIS 15765-5:2021(E)

The CAN node(s) shall use one of the following addressing formats as specified in ISO 15765-2:

— N_Ptype = DiagNormAddr: no address information N_AI[N_SA, N_TA] mapped in the N_PDU;

— N_Ptype = DiagNormFixAddr: no address information N_AI[N_SA, N_TA] mapped in the N_PDU;

— N_Ptype = DiagExtAddr: address information N_AI[N_TA] mapped in the N_PDU;

— N_Ptype = RDiagMixAddr: address information N_AI[N_AE] mapped into the N_PDU.

Functional addressing is used to reach more than one CAN node connected to the network.

REQ 3.6 NL – ISO 15765-2 functional addressing

Functional addressed N_PDU shall not exceed the packet limitation as specified in ISO 15765-2.

Physical addressing is used to reach only one CAN node connected to the network.
REQ 3.7 NL – ISO 15765-2 reception of N_PDU

The NL shall extract the N_AI or N_AE from the N_PDU depending on the addressing format as speci-

fied in REQ 3.5.
6.7 Data link layer (DLL)
6.7.1 DLL – Data interface primitive parameter mapping

The DLL protocol entity transfers data frames between network nodes on the CAN network. The

following requirements are applicable to DLL implementations.

REQ 2.1 DLL – Data interface primitive parameter mapping – Mapping of upper OSI layer ser-

vice interface parameters

The L_Data service primitive shall use the service primitive parameters as specified in Table 4.

Table 4 — L_Data service primitive parameter mapping
ISO 11898-1 .req .ind .conf Description
Format
X X X N_TAtype #1: physical address, CBFF, 11-bit CAN identifier;
N_TAtype #2: functional address, CBFF, 11-bit CAN identifier;
N_TAtype #3: physical addressing, FBFF, 11-bit CAN identifier;
N_TAtype #4: functional addressing, FBFF, 11-bit CAN identifier;
N_TAtype #5: physical addressing, CEFF, 29-bit CAN identifier;
N_TAtype #6: functional addressing, CEFF, 29-bit CAN identifier;
N_TAtype #7: physical addressing, FEFF, 29-bit CAN identifier;
N_TAtype #8: functional addressing, FEFF, 29-bit CAN identifier.
Identifier
X X – If 11-bit CAN identifier: target and source address are mapped to a
PDU-specific CAN identifier value.
Identifier
– – X If 29-bit CAN identifier: target and source address are mapped
into the CAN identifier TA and SA fields of the PDU-specific CAN
identifier value.
DLC
X X X Data Length Code
Data
X X – (CAN) data field
Transfer_Status
– – X Result information
X Supported.
– Not supported.
8 © ISO 2021 – All rights reserved
---------------------- Page: 14 ----------------------
ISO/FDIS 15765-5:2021(E)
The DLL is specified in ISO 11898-1.

REQ 2.2 DLL – Data interface primitive parameter mapping – ISO 11898-1 conformance

The DLL shall be conform with ISO 11898-1 and support the optional data frame formats (FBFF and FEFF).

6.7.2 DLL – Service interface parameter requirements

The DLL uses the value of the L_Ftype service interface parameter to identify the address information

N_AI[N_TA, N_SA] mapping into the CAN identifier.

For 11-bit CAN identifiers the DLL uses the value included in the L_Ftype service interface parameter to

set the applicable 11-bit CAN identifier.
REQ 2.3 DLL – Mapping of N_AI into the 11-bit CAN identifier

The CAN node(s) shall support the mapping of N_AI into the 11-bit CAN identifier based on the L_Ftype

service interface parameter value as specified in Table 5.
Table 5 — Mapping of N_AI into the 11-bit CAN identifier
L_Ftype N_AI 11-bit CAN ID Description
DiagNormAddr N _TA , XXX XXXX XXXX The SA and TA values are mapped to
N_SA a predefined CAN identifier.
(diagnostics with normal addressing)
DiagExtAddr N_SA XXX XXXX XXXX The SA value is mapped to a prede-
fined CAN identifier.
(diagnostics with extended addressing)
RDiagMixAddr N _TA , XXX XXXX XXXX The SA value is mapped to a prede-
N_SA fined CAN identifier.
(remote diagnostics with mixed addressing)
REQ 2.4 DLL – Mapping of N_AI into th
...