ISO 17987-2:2016
(Main)Road vehicles — Local Interconnect Network (LIN) — Part 2: Transport protocol and network layer services
Road vehicles — Local Interconnect Network (LIN) — Part 2: Transport protocol and network layer services
ISO 17987-2:2016 specifies a transport protocol and network layer services tailored to meet the requirements of LIN‑based vehicle network systems on local interconnect networks. The protocol specifies an unconfirmed communication. The LIN protocol supports the standardized service primitive interface as specified in ISO 14229‑2. ISO 17987-2:2016 provides the transport protocol and network layer services to support different application layer implementations like - normal communication messages, and - diagnostic communication messages. The transport layer defines transportation of data that is contained in one or more frames. The transport layer messages are transported by diagnostic frames. A standardized API is specified for the transport layer. Use of the transport layer is targeting systems where diagnostics are performed on the backbone bus (e.g. CAN) and where the system builder wants to use the same diagnostic capabilities on the LIN sub-bus clusters. The messages are in fact identical to the ISO 15765‑2 and the PDUs carrying the messages are very similar. The goals of the transport layer are - low load on LIN master node, - to provide full (or a subset thereof) diagnostics directly on the LIN slave nodes, and - targeting clusters built with powerful LIN nodes (not the mainstream low cost).
Véhicules routiers — Réseau Internet local (LIN) — Partie 2: Protocole de transport et couches de services réseau
General Information
Relations
Buy Standard
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 17987-2
First edition
2016-08-15
Road vehicles — Local Interconnect
Network (LIN) —
Part 2:
Transport protocol and network layer
services
Véhicules routiers — Réseau Internet local (LIN) —
Partie 2: Protocole de transport et couches de services réseau
Reference number
ISO 17987-2:2016(E)
©
ISO 2016
---------------------- Page: 1 ----------------------
ISO 17987-2:2016(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2016, Published in Switzerland
All rights reserved. Unless otherwise specified, 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
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2016 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 17987-2:2016(E)
Contents Page
Foreword .vi
Introduction .vii
1 Scope . 1
2 Normative references . 2
3 Terms, definitions, symbols and abbreviated terms . 2
3.1 Terms and definitions . 2
3.2 Symbols . 4
3.3 Abbreviated terms . 4
4 Conventions . 5
5 Network management . 5
5.1 Network management general information . 5
5.2 LIN node communication state diagram . 5
5.3 Wake up . 6
5.3.1 Wake up general information . 6
5.3.2 Master generated wake up . 6
5.3.3 Slave generated wake up . 6
5.4 Go-to-sleep . 8
6 Network layer overview . 8
6.1 General . 8
6.2 Format description of network layer services . 9
6.3 Internal operation of network layer . 9
6.4 Service data unit specification .10
6.4.1 N_AI, address information .10
6.4.2 .11
6.4.3 .11
6.4.4 .11
6.5 Services provided by network layer to higher layers .12
6.5.1 Specification of network layer service primitives .12
6.5.2 N_USData.request .13
6.5.3 N_USData.confirm .13
6.5.4 N_USData_FF.indication .13
6.5.5 N_USData.indication .13
7 Transport layer protocol .14
7.1 Protocol functions .14
7.2 Single frame transmission .14
7.3 Multiple frame transmission .14
7.4 Transport layer protocol data units .16
7.4.1 Protocol data unit types . .16
7.4.2 SF N_PDU .16
7.4.3 FF N_PDU .16
7.4.4 CF N_PDU .16
7.4.5 Protocol data unit field description .16
7.5 Protocol control information specification .17
7.5.1 N_PCI .17
7.5.2 SingleFrame N_PCI parameter definition .18
7.5.3 FirstFrame N_PCI parameter definition .19
7.5.4 ConsecutiveFrame N_PCI parameter definition .19
7.6 Network layer timing .20
7.6.1 Timing constraints .20
7.6.2 Network layer timeouts .25
7.6.3 Network layer error handling .25
7.6.4 Unexpected arrival of N_PDU .26
© ISO 2016 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO 17987-2:2016(E)
8 Data link layer usage .27
8.1 Data link layer service parameters .28
8.2 Data link layer interface services .28
8.2.1 L_Data.request .28
8.2.2 L_Data.confirm .28
8.2.3 L_Data.indication .28
8.3 Mapping of the N_PDU fields .28
8.4 Transport layer PDU structure and communication .29
8.4.1 PDU structure .29
8.4.2 Communication .31
9 Diagnostic communication requirements .31
9.1 Definition of diagnostic classes .31
9.1.1 General.31
9.1.2 Diagnostic class I . . .31
9.1.3 Diagnostic class II .31
9.1.4 Diagnostic class III .31
9.1.5 Summary of slave node diagnostic classes .32
9.2 Diagnostic messages .32
9.3 Using the transport layer .32
9.4 Slave node diagnostic timing requirements .34
9.5 Response pending .36
9.6 Transport protocol handling in LIN master .36
9.6.1 General.36
9.6.2 Diagnostic master request schedule .36
9.6.3 Diagnostic slave response schedule .37
9.6.4 Diagnostic schedule execution .37
9.7 Transmission handler requirements .42
9.7.1 General.42
9.7.2 Master node transmission handler .42
9.7.3 Slave node transmission handler.46
9.8 Diagnostic service prioritization .48
10 LIN node capability language (NCL) .48
10.1 General .48
10.2 Plug and play workflow concept.49
10.2.1 General.49
10.2.2 LIN node generation .50
10.2.3 LIN cluster design .50
10.2.4 Debugging .51
11 Node capability file (NCF) .51
11.1 Overview of NCF syntax .51
11.2 Global structure definition .51
11.2.1 Node capability file marker .51
11.2.2 Language version number definition .52
11.2.3 NCF revision .52
11.2.4 Big-endian signal encoding variant .52
11.3 Node definition .52
11.3.1 General node definition .52
11.3.2 Diagnostic definition .53
11.3.3 Frame definition .54
11.3.4 Signal encoding type definition.55
11.3.5 Status management .56
11.3.6 Free text definition .56
11.4 NCF example .56
12 LIN description file (LDF) .57
12.1 General .57
12.2 Overview of LDF syntax .57
iv © ISO 2016 – All rights reserved
---------------------- Page: 4 ----------------------
ISO 17987-2:2016(E)
12.3 LDF definition .58
12.3.1 Global structure definition .58
12.3.2 Signal definition .59
12.3.3 Frame definition .60
12.3.4 Node definition .62
12.3.5 Schedule table definition .65
12.3.6 Signal encoding type definition.67
12.3.7 Signal representation definition .69
12.4 LDF example .69
Bibliography .72
© ISO 2016 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO 17987-2:2016(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 on 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 the following URL: www.iso.org/iso/foreword.html.
The committee responsible for this document is ISO/TC 22, Road vehicles, SC 31, Data communication.
A list of all parts in the ISO 17987 series can be found on the ISO website.
vi © ISO 2016 – All rights reserved
---------------------- Page: 6 ----------------------
ISO 17987-2:2016(E)
Introduction
This ISO 17987 (all parts) specifies the use cases, the communication protocol and physical layer
requirements of an in-vehicle communication network called Local Interconnect Network (LIN).
The LIN protocol as proposed is an automotive focused low speed universal asynchronous receiver
transmitter (UART) based network. Some of the key characteristics of the LIN protocol are signal
based communication, schedule table based frame transfer, master/slave communication with error
detection, node configuration and diagnostic service transportation.
The LIN protocol is for low cost automotive control applications, for example, door module and air
condition systems. It serves as a communication infrastructure for low-speed control applications in
vehicles by providing:
— signal based communication to exchange information between applications in different nodes;
— bitrate support from 1 kbit/s to 20 kbit/s;
— deterministic schedule table based frame communication;
— network management that wakes up and puts the LIN cluster into sleep mode in a controlled manner;
— status management that provides error handling and error signalling;
— transport layer that allows large amount of data to be transported (such as diagnostic services);
— specification of how to handle diagnostic services;
— electrical physical layer specifications;
— node description language describing properties of slave nodes;
— network description file describing behaviour of communication;
— application programmer’s interface.
ISO 17987 (all parts) is based on the open systems interconnection (OSI) basic reference model as
specified in ISO/IEC 7498-1 which structures communication systems into seven layers.
The OSI model structures data communication into seven layers called (top down) application layer
(layer 7), presentation layer, session layer, transport layer, network layer, data link layer and physical layer
(layer 1). A subset of these layers is used in ISO 17987 (all parts).
ISO 17987 (all parts) distinguishes between the services provided by a layer to the layer above it and
the protocol used by the layer to send a message between the peer entities of that layer. The reason for
this distinction is to make the services, especially the application layer services and the transport layer
services, reusable also for other types of networks than LIN. In this way, the protocol is hidden from the
service user and it is possible to change the protocol if special system requirements demand it.
ISO 17987 (all parts) provides all documents and references required to support the implementation of
the requirements related to the following.
— ISO 17987-1: This part provides an overview of the ISO 17987 (all parts) and structure along with
the use case definitions and a common set of resources (definitions, references) for use by all
subsequent parts.
— ISO 17987-2: This part specifies the requirements related to the transport protocol and the network
layer requirements to transport the PDU of a message between LIN nodes.
— ISO 17987-3: This part specifies the requirements for implementations of the LIN protocol on the
logical level of abstraction. Hardware related properties are hidden in the defined constraints.
© ISO 2016 – All rights reserved vii
---------------------- Page: 7 ----------------------
ISO 17987-2:2016(E)
— ISO 17987-4: This part specifies the requirements for implementations of active hardware
components which are necessary to interconnect the protocol implementation.
— ISO/TR 17987-5: This part specifies the LIN application programmers interface (API) and the
node configuration and identification services. The node configuration and identification services
are specified in the API and define how a slave node is configured and how a slave node uses the
identification service.
— ISO 17987-6: This part specifies tests to check the conformance of the LIN protocol implementation
according to ISO 17987-2 and ISO 17987-3. This comprises tests for the data link layer, the network
layer and the transport layer.
— ISO 17987-7: This part specifies tests to check the conformance of the LIN electrical physical layer
implementation (logical level of abstraction) according to ISO 17987-4.
viii © ISO 2016 – All rights reserved
---------------------- Page: 8 ----------------------
INTERNATIONAL STANDARD ISO 17987-2:2016(E)
Road vehicles — Local Interconnect Network (LIN) —
Part 2:
Transport protocol and network layer services
1 Scope
This document specifies a transport protocol and network layer services tailored to meet the
requirements of LIN-based vehicle network systems on local interconnect networks. The protocol
specifies an unconfirmed communication.
The LIN protocol supports the standardized service primitive interface as specified in ISO 14229-2.
This
...
DRAFT INTERNATIONAL STANDARD
ISO/DIS 17987-2.2
ISO/TC 22/SC 31 Secretariat: DIN
Voting begins on: Voting terminates on:
2015-10-05 2015-12-05
Road vehicles — Local Interconnect Network (LIN) —
Part 2:
Transport protocol and network layer services
Véhicules routiers — Réseau Internet local (LIN) —
Partie 2: Protocole de transport et couches de services réseau
ICS: 35.240.60; 43.040.15
THIS DOCUMENT IS A DRAFT CIRCULATED
FOR COMMENT AND APPROVAL. IT IS
THEREFORE SUBJECT TO CHANGE AND MAY
NOT BE REFERRED TO AS AN INTERNATIONAL
STANDARD UNTIL PUBLISHED AS SUCH.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL,
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
Reference number
NATIONAL REGULATIONS.
ISO/DIS 17987-2.2:2015(E)
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 SUPPORTING DOCUMENTATION. ISO 2015
---------------------- Page: 1 ----------------------
ISO/DIS 17987-2.2:2015(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2015, Published in Switzerland
All rights reserved. Unless otherwise specified, 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
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2015 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/DIS 17987-2.2
Contents Page
1 Scope . 1
2 Normative references . 2
3 Terms, definitions, symbols and abbreviated terms . 2
3.1 Terms and definitions . 2
3.2 Symbols . 3
3.3 Abbreviated terms . 3
4 Conventions . 4
5 Network management . 4
6 Network layer overview . 8
6.1 General . 8
6.2 Format description of network layer services . 8
6.3 Internal operation of network layer . 9
6.4 Service data unit specification . 9
6.5 Services provided by network layer to higher layers . 12
7 Transport layer protocol . 14
7.1 Protocol functions . 14
7.2 Single frame transmission. 14
7.3 Multiple frame transmission . 14
7.4 Transport layer protocol data units . 16
7.5 Protocol control information specification . 17
7.6 Network layer timing . 20
8 Data link layer usage . 28
8.1 Data link layer service parameters . 28
8.2 Data link layer interface services . 28
8.3 Mapping of the N_PDU fields . 29
8.4 Transport layer PDU structure and communication . 29
9 Diagnostic communication requirements . 32
9.1 Definition of diagnostic classes . 32
9.2 Diagnostic messages . 33
9.3 Using the transport layer . 33
9.4 Slave node diagnostic timing requirements . 34
9.5 Response Pending . 36
9.6 Transport protocol handling in LIN master . 37
9.7 Transmission handler requirements . 43
9.8 Diagnostic service prioritization . 48
10 LIN node capability language (NCL) . 50
10.1 General . 50
10.2 Plug and play workflow concept . 50
11 Node capability file (NCF) . 52
11.1 Overview of NCF syntax . 52
11.2 Global structure definition. 52
11.3 Node definition . 53
11.4 NCF example . 58
12 LIN description file (LDF) . 59
12.1 General . 59
12.2 Overview of LDF syntax . 59
12.3 LDF definition . 59
© ISO 2015 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/DIS 17987-2.2
12.4 LDF example . 74
iv © ISO 2015 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/DIS 17987-2.2
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.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
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.
ISO 17987-2 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 31,
Electrical and electronic equipment.
ISO 17987 consists of the following parts, under the general title Road vehicles — Local Interconnect Network
(LIN):
Part 1: General information and use case definition
Part 2: Transport protocol and network layer services
Part 3: Protocol specification
Part 4: Electrical Physical Layer (EPL) specification (12 V/24 V)
Part 5: Application Programmers Interface (API)
Part 6: Protocol conformance test specification
Part 7: Electrical Physical Layer (EPL) conformance test specification
© ISO 2015 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/DIS 17987-2.2
Introduction
This document set specifies the use cases, the communication protocol and physical layer requirements of an
in-vehicle communication network called "Local Interconnect Network (LIN)".
The LIN protocol as proposed is an automotive focused low speed UART-based network (Universal
Asynchronous Receiver Transmitter). Some of the key characteristics of the LIN protocol are signal based
communication, schedule table based frame transfer, master/slave communication with error detection, node
configuration and diagnostic service transportation.
The LIN protocol is for low cost automotive control applications, for example door module and air condition
systems. It serves as a communication infrastructure for low-speed control applications in vehicles by
providing:
Signal based communication to exchange information between applications in different nodes;
Bitrate support from 1 kbit/s to 20 kbit/s;
Deterministic schedule table based frame communication;
Network management that wakes up and puts the LIN cluster into sleep mode in a controlled manner;
Status management that provides error handling and error signalling;
Transport layer that allows large amount of data to be transported (such as diagnostic services);
Specification of how to handle diagnostic services;
Electrical physical layer specifications;
Node description language describing properties of slave nodes;
Network description file describing behaviour of communication;
Application programmer's interface;
ISO 17987 is based on the Open Systems Interconnection (OSI) Basic Reference Model as specified in
ISO/IEC 7498-1 which structures communication systems into seven layers.
The OSI model structures data communication into seven layers called (top down) application layer (layer 7),
presentation layer, session layer, transport layer, network layer, data link layer and physical layer (layer 1). A
subset of these layers is used in ISO 17987.
ISO 17987 distinguishes between the services provided by a layer to the layer above it and the protocol used
by the layer to send a message between the peer entities of that layer. The reason for this distinction is to
make the services, especially the application layer services and the transport layer services, reusable also for
other types of networks than LIN. In this way the protocol is hidden from the service user and it is possible to
change the protocol if special system requirements demand it.
vi © ISO 2015 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/DIS 17987-2.2
This document set provides all documents and references required to support the implementation of the
requirements related to.
Part 1: General information and use case definitions
This part provides an overview of the document set and structure along with the use case definitions and
a common set of resources (definitions, references) for use by all subsequent parts.
Part 2:
This part specifies the requirements related to the transport protocol and the network layer requirements
to transport the PDU of a message between LIN nodes.
Part 3:
This part specifies the requirements for implementations of the LIN protocol on the logical level of
abstraction. Hardware related properties are hidden in the defined constraints.
Part 4:
This part specifies the requirements for implementations of active hardware components which are
necessary to interconnect the protocol implementation.
Part 5 (published as a non-normative technical report):
This part specifies the LIN API (Application Programmers Interface) and the node configuration and
identification services. The node configuration and identification services are specified in the API and
define how a slave node is configured and how a slave node uses the identification service.
Part 6:
This part specifies tests to check the conformance of the LIN protocol implementation according to
ISO 17987-2 and ISO 17987-3. This comprises tests for the data link layer, the network layer and the
transport layer.
Part 7:
This part specifies tests to check the conformance of the LIN electrical physical layer implementation
(logical level of abstraction) according to ISO 17987-4.
© ISO 2015 – All rights reserved vii
---------------------- Page: 7 ----------------------
DRAFT INTERNATIONAL STANDARD ISO/DIS 17987-2.2
1 Road vehicles — Local Interconnect Network (LIN) — Part 2:
2 Transport protocol and network layer services
3 1 Scope
4 This part of ISO 17987 specifies a transport protocol and network layer services tailored to meet the
5 requirements of LIN-based vehicle network systems on local interconnect networks. The protocol specifies an
6 unconfirmed communication.
7 The LIN protocol supports the standardized service primitive interface as specified in ISO 14229-2.
8 This part of ISO 17987 provides the transport protocol and network layer services to support different
9 application layer implementations like
10 Normal communication messages;
11 Diagnostic communication messages;
12 The transport layer defines transportation of data that is contained in one or more frames. The transport layer
13 messages are transported by diagnostic frames. A standardized API is specified for the transport layer.
14 Use of the transport layer is targeting systems where diagnostics are performed on the backbone bus (e.g.
15 CAN) and where the system builder wants to use the same diagnostic capabilities on the LIN sub-bus
16 clusters. The messages are in fact identical to the ISO 15765-2 and the PDUs carrying the messages are very
17 similar.
18 The goals of the transport layer are
19 low load on LIN master node;
20 to provide full (or a subset thereof) diagnostics directly on the LIN slave nodes;
21 targeting clusters built with powerful LIN nodes (not the mainstream low cost);
22 A typical system configuration is shown in Figure 1.
back-bone bus
Tester
Master
LIN cluster
Slave 2
Slave 1
23
24 Figure 1 — Typical system setup for a LIN cluster using the transport layer
© ISO 2015 – All rights reserved 1
---------------------- Page: 8 ----------------------
ISO/DIS 17987-2.2
25 2 Normative references
26 The following referenced documents are indispensable for the application of this document. For dated
27 references, only the edition cited applies. For undated references, the latest edition of the referenced
28 document (including any amendments) applies.
29 ISO 17987 (Part 2, 4, 6 and 7), Road vehicles – Local Interconnect Network (LIN)
30 3 Terms, definitions, symbols and abbreviated terms
31 3.1 Terms and definitions
32 For the purposes of this document, the terms and definitions given in ISO/IEC 7498-1 apply.
33 3.1.1
34 Broadcast NAD
35 Any slave node receiving a message with a NAD equal to the broadcast NAD 7F the message is received
16
36 and processed.
37 3.1.2
38 Configured NAD
39 Each of the slave nodes requires a unique configured NAD which is used for node configuration and
40 identification services as well as UDS services according to ISO 14229-7. The assignment of configured NAD
41 is defined in the LDF.
42 The master node can assign new configured NADs to slave nodes supporting the "Assign NAD" service.
43 The configured NAD is in the range [01 – 7D ].
16 16
44 An API alternatively used in a slave node to assign the configured NAD.
45 The configured NAD is assigned with a static configuration
46 3.1.3
47 Functional NAD
48 (7E ) Used to broadcast diagnostic requests
16
49 3.1.4
50 Initial NAD
51 Each of the slave nodes shall have an initial NAD. The combination of initial NAD, Suppler ID and Function ID
52 shall be unique in a LIN cluster. The initial NAD value is constant/static and may be derived before entering
53 the operational state (regular LIN communication) from a pin configuration, EEPROM or slave node position
54 detection algorithms. The initial NAD is used to assign a unique configured NAD. If no initial NAD is defined
55 for a slave node (LDF, NCF) the value is identical to the configured NAD. The initial NAD is in the range of
56 [01 – 7D ]
16 16
57 3.1.5
58 P2 timing parameter
59 Application timing parameter for the ECU(s) and the external test equipment
60 3.1.6
61 P2* timing parameter
62 Enhanced response timing parameter for the ECU(s) application after response pending frame transmission
63 3.1.7
64 P4 timing parameter
65 Timing parameter for the ECU(s) application defining the time between reception of a request and the final
66 response
2 © ISO 2015 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/DIS 17987-2.2
67 3.1.8
68 Proprietary NAD
69 NAD values in the range [80 – FF ] are used for not standardized communication purpose such as Tier-1
16 16
70 slave node diagnostics.
71
72 3.2 Symbols
% percentage
µs microsecond
ms millisecond
| The vertical bar indicates choice. Either the left hand side or the right hand side of the vertical bar
shall appear
73
74 3.3 Abbreviated terms
API application programmers interface
BNF Bachus-Naur format
CF ConsecutiveFrame
FF FirstFrame
LDF LIN description file
L_Data data link data
MRF master request frame
N_AI network address information
N_As network layer timing parameter As
N_As timeout on As
max
N_Cr network layer timing parameter Cr
N_Cr timeout on Cr
max
N_Cs network layer timing parameter Cs
N_Cs timeout on Cs
max
N_Data network data
N_PCI network protocol control information
N_PCItype network protocol control information type
N_PDU network protocol data unit
© ISO 2015 – All rights reserved 3
---------------------- Page: 10 ----------------------
ISO/DIS 17987-2.2
N_SA network source address
N_SDU network service data unit
N_TAtype network target address type
N_USData network layer LIN data transfer service name
NAD node address for slave nodes
NCF node capability file
NCL node capability language
NRC negative response code
NWL network layer
OBD on-board diagnostics
OSI Open Systems Interconnection
PDU protocol data unit
PID protected identifier
RSID response service identifier
SF SingleFrame
SID service identifier
SN SequenceNumber
SRF slave response frame
ST SeparationTime minimum
min
75 4 Conventions
76 ISO 17987 (all parts) and ISO 14229-7 [5] are based on the conventions specified in the OSI Service
77 Conventions (ISO/IEC 10731) [2] as they apply for physical layer, protocol, transport protocol & network layer
78 services and diagnostic services.
79 5 Network management
80 5.1.1 Network management general information
81 Network management in a LIN cluster refers to cluster wake up and go-to-sleep only. Other network
82 management features, e.g. configuration detection and limp home management are left to the application.
83 5.1.2 LIN node communication state diagram
84 The state diagram in Figure 2 shows the behaviour model for LIN communication state.
4 © ISO 2015 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/DIS 17987-2.2
85 Bus Sleep
86 Bus Sleep state is entered after first connection to power source and the system initialization, reset or
87 when a go-to-sleep command is transmitted by the master or received by the slave node. The level on the
88 bus is set to recessive. Only the wake up signal may be transmitted on the cluster.
89 Operational
90 The protocol behaviour (transmitting and receiving frames) specified in this document only applies to the
91 Operational state.
92
93 Note: The LIN 'Bus Sleep' state does not necessarily correlate to the node's power state.
94
Wake up signal received
OR
internal reason to wake up the cluster
Bus Sleep Operational
Go-to-sleep command
transmitted / received OR
bus inactivity for 4 to 10 s
95
96 Figure 2 — LIN node communication state diagram
97
98 5.1.3 Wake up
99 5.1.3.1 Wake up general information
100 Any node in a sleeping LIN cluster may request a wake up, by transmitting a wake up signal. The wake up
101 signal is started by forcing the bus to the dominant state for 250 µs to 5 ms, and is valid with the return of the
102 bus signal to the recessive state.
103 5.1.3.2 Master generated wake up
104 The master node may issue a break field, e.g. by issuing an ordinary header since the break acts as a wake
105 up signal (in this case the master shall be aware of that this frame may not be processed by the slave nodes
106 since they may not yet awake and ready to listen to headers).
107 Every slave node (connected to power) should detect the wake up signal (a dominant pulse longer than
108 150 µs followed by a rising edge of the bus signal) and be ready to listen to bus commands within 100 ms,
109 measured from the ending edge of the dominant pulse, see Figure 3. The check for the rising edge shall be
110 done by the transceiver and also could be done by the microcontroller LIN interface.
111 A detection threshold of 150 µs combined with a 250 µs pulse generation gives a detection margin that is
112 enough for uncalibrated slave nodes. Following the detection of the wake up pulse, the Slave task machine
© ISO 2015 – All rights reserved 5
---------------------- Page: 12 ----------------------
ISO/DIS 17987-2.2
113 (ISO 17987-3 subclause 7.5.3) shall start and enter into the idle state. During the idle state, the slave shall
114 never issue a dominant level pulse on the bus until the state machine enters into an active state.
115 5.1.3.3 Slave generated wake up
116 If the node that transmitted the wake up signal is a slave node, it shall be ready to receive or transmit frames
117 immediately. The master node shall also wake up and, when the slave nodes are ready (>100 ms), start
118 transmitting headers to find out the cause (using signals) of the wake up.
The slave node is
ready to receive or
Slave node is initializing
transmit frames
> 150 µs max 100 ms
119
120 Figure 3 — Wake up signal reception in slave nodes
121
122 The master node shall detect the wake up signal (a dominant pulse longer than 150 µs followed by a rising
123 edge of the bus signal) and be ready to start communication within a time that is decided by the cluster
124 designer or application specific. The check for the rising edge shall be done by the transceiver and also could
125 be done by the microcontroller LIN interface.
126 If the master node does not transmit a break field (i.e. starts to transmit a frame) or if the node issuing the
127 wake up signal does not receive a wakeup signal (from another node) within 150 ms to 250 ms from the wake
128 up signal, the node issuing the wake up signal shall transmit a new wake up signal, see Figure 4. In case the
129 slave node transmits a wake up signal in the same time as the master node transmits a break field, the slave
130 shall receive and recognize this break field.
250µs – 5ms 150 ms – 250 ms 250µs – 5ms 150 ms – 250 ms 250µs – 5ms
131
132 Figure 4 — One block of wake up signals
133
134 After three (failing) requests the node shall wait minimum 1,5 s before issuing a fourth wake up signal. The
135 reason for this longer duration is to allow the cluster to communicate in case the waking slave node has
136 problems, e.g. if the slave node has problems with reading the bus it probably retransmit the wake up signal
137 infinitely. There is no restriction of how many times a slave may transmit the wake up signal. However, it is
138 recommended that a slave node transmits not more than one block of three wake up signals for each wake up
139 condition. Figure 5 shows how wake up signals are transmitted over a longer time
140
6 © ISO 2015 – All rights reserved
---------------------- Page: 13 ----------------------
ISO/DIS 17987-2.2
> 1,5 s > 1,5 s > 1,5 s
141
142 Figure 5 — Wake up signals over long time
143
144 5.1.4 Go-to-sleep
145 The master sets each node in the cluster instantly into bus sleep state by transmitting a go-to-sleep command.
146 The request does not necessarily enforce the slave nodes into a low-power mode. The slave node application
147 may still be active after the go-to-sleep command has been received. This behaviour is application specific.
148 The go-to-sleep command is a master request frame with the first data field (Byte 1) set to 00 and the rest
16
149 set to FF , see Table 1. The slave nodes shall ignore the data fields (bytes) 2 to 8 and interpret only the first
16
150 data field (Byte 1).
151 Table 1 — Go-to-sleep command
LIN frame
Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Byte 8
00 FF FF FF FF FF FF FF
16 16 16 16 16 16 16 16
152
153 The normal way for setting the cluster to sleep is that the master node transmits the go-to-sleep command. In
154 case of bus inactivity a slave node shall be able to receive/transmit frames for 4 s. The slave node shall
155 automatically enter bus sleep mode earliest 4 s and latest 10 s of bus inactivity. Bus inactivity is defined as no
1)
156 transitions between recessive and dominant bit values . Bus activity is the inverse.
157
1) LIN transceivers normally have filters to remove short spikes on the bus. The transition here refers to the signal after
this filter.
© ISO 2015 – All rights reserved 7
---------------------- Page: 14 ----------------------
ISO/DIS 17987-2.2
158 6 Network layer overview
159 6.1 General
160 This part of ISO 17987 specifies an unconfirmed network layer communication protocol for the exchange of
161 data between network nodes, e.g. from ECU to ECU, or between external test equipment and an ECU. If the
162 data to be transferred do not fit into a single LIN frame, a segmentation method is provided.
163 In order to describe the function of the network layer, services provided to higher layers and the internal
164 operation of the network layer shall be considered.
165 All network layer services have the same general structure. To define the services, three types of service
166 primitives are specified:
167 a service request primitive, used by higher communication layers or the application to pass control
168 information and data required to be transmitted to the network layer;
169 a service indication primitive, used by the network layer to pass status information and received data to
170 upper communication layers or the application;
171 a service confirmation primitive, used by the network layer to pass status info
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.