ISO 17987-6:2016

Road vehicles — Local Interconnect Network (LIN) — Part 6: Protocol conformance test specification

ISO 17987-6:2016 specifies the LIN protocol conformance test. This test verifies the conformance of LIN communication controllers with respect to ISO 17987‑2 and ISO 17987‑3. ISO 17987-6:2016 provides all necessary technical information to ensure that test results are identical even on different test systems, provided that the particular test suite and the test system are compliant to the content of this document.

Véhicules routiers — Réseau Internet local (LIN) — Partie 6: Spécification du protocole d'essai de conformité

General Information

• Status: Published
• Publication Date: 05-Oct-2016
• ICS: 01.040.43 - Road vehicle engineering (Vocabularies)
• ICS: 43.020 - Road vehicles in general
• ICS: 43.040.15 - Car informatics. On board computer systems
• Technical Committee: ISO/TC 22/SC 31 - Data communication
• Drafting Committee: ISO/TC 22/SC 31/WG 3 - In-vehicle networks
• Parallel Committee: ISO/TC 43/SC 1 - Noise
• Current Stage: 9092 - International Standard to be revised
• Completion Date: 30-May-2022

Relations

• Consolidated By: ISO 25239-2:2020 - Friction stir welding — Aluminium — Part 2: Design of weld joints
• Effective Date: 06-Jun-2022

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 17987-6
First edition
2016-10-01
Road vehicles — Local Interconnect
Network (LIN) —
Part 6:
Protocol conformance test
specification
Véhicules routiers — Réseau Internet local (LIN) —
Partie 6: Spécification du protocole d’essai de conformité
Reference number
ISO 17987-6:2016(E)
©
ISO 2016

---------------------- Page: 1 ----------------------
ISO 17987-6: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. [phone]
Fax [phone]
[e-mail]
www.iso.org
ii © ISO 2016 – All rights reserved

---------------------- Page: 2 ----------------------
ISO 17987-6:2016(E)

Contents Page
Foreword .vii
Introduction .viii
1 Scope . 1
2 Normative references . 1
3 Terms, definitions, symbols and abbreviated terms . 1
3.1 Terms and definitions . 1
3.2 Symbols . 2
3.3 Abbreviated terms . 3
4 Conventions . 4
5 General test specification considerations . 4
5.1 General . 4
5.2 Test conditions . 4
5.3 Mandatory requirements for IUT as master . 4
5.4 Mandatory requirements for IUT as slave . 5
5.5 Test case architecture . 5
5.6 Classification . 6
5.7 Test system requirements . 6
5.7.1 Generation of LIN frames . 6
5.7.2 Standard requirements for the test cases . 6
5.7.3 Special requirements for bit timing testing . 6
5.7.4 Test system for IUT as slave node . 6
5.7.5 Sleep state verification for IUT as slave node . 6
5.8 Test system definition . 7
5.9 Global predefinitions for the test setup . 7
5.9.1 Configuration of IUT and test system. 7
5.9.2 Default delays for frame headers . 9
5.9.3 Default bit rate . 9
5.9.4 Time measurement . 9
5.9.5 Default spaces between the different frame parts of a LIN message . 9
6 Essential test cases before test start .10
6.1 General .10
6.2 [PT-CT 1] Diagnostic frame “master request”, IUT as slave .10
6.3 [PT-CT 2] Diagnostic frame “slave response”, IUT as slave .10
6.4 [PT-CT 3] Error in received frame, IUT as slave .10
7 Timing parameters .11
7.1 General .11
7.2 [PT-CT 4] Length of break field low phase, IUT as master .11
7.3 [PT-CT 5] Variation of length of break field low phase, IUT as slave .11
7.4 [PT-CT 6] Length of break delimiter, IUT as master .12
7.5 [PT-CT 7] Variation of length of break delimiter, IUT as slave .12
7.6 [PT-CT 8] Inconsistent break field error, IUT as slave .13
7.7 [PT-CT 9] Inconsistent sync byte field error, IUT as slave .13
7.8 [PT-CT 10] Verification of the sync byte field, IUT as master .14
7.9 [PT-CT 11] Incomplete frame reception, IUT as slave .14
7.10 [PT-CT 12] Unknown frame reception, IUT as slave .15
7.11 [PT-CT 13] Length of header, IUT as master .16
7.12 [PT-CT 14] Variation of length of header, IUT as slave .16
7.13 [PT-CT 15] Bit rate tolerance, IUT as master.17
7.14 [PT-CT 16] Bit rate tolerance, IUT as slave without making use of synchronization .17
7.15 [PT-CT 17] Bit rate tolerance, IUT as slave with making use of synchronization .18
7.16 Length of response .18
7.16.1 [PT-CT 18] Length of response, IUT as slave.18
© ISO 2016 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO 17987-6:2016(E)

7.16.2 [PT-CT 19] Length of response, IUT as master.19
7.16.3 [PT-CT 20] Acceptance of response field, IUT as slave .20
7.17 Verification of schedule table timing .21
7.17.1 [PT-CT 21] Verification of jitter, IUT as master .21
7.17.2 [PT-CT 22] Schedule table management, IUT as master .22
7.18 [PT-CT 23] Sample point test, IUT as slave .22
7.19 [PT-CT 24] Initialization time, IUT as slave .23
8 Communication without failure .24
8.1 Variation of LIN identifier.24
8.1.1 [PT-CT 25] Variation of LIN PID, IUT as master .24
8.1.2 [PT-CT 26] Variation of LIN PIDs of subscribed frames, IUT as slave .24
8.1.3 [PT-CT 27] Variation of LIN identifier of published frames, IUT as slave .25
8.2 Transmission of the checksum byte.25
8.2.1 [PT-CT 28] Transmission of the checksum byte “classic checksum”, IUT as slave 25
8.2.2 [PT-CT 29] Transmission of the checksum byte “enhanced checksum”, IUT
as slave . .26
8.2.3 [PT-CT 30] Transmission of the checksum byte “classic checksum”, IUT
as master . .26
8.2.4 [PT-CT 31] Transmission of the checksum byte of unconditional frames,
IUT as master .26
8.3 Unused bits .27
8.3.1 [PT-CT 32] Unused bits, IUT as master .27
8.3.2 [PT-CT 33] Unused bits, IUT as slave .27
8.4 Reserved frame .28
8.4.1 [PT-CT 34] Reserved frame, IUT as slave .28
8.5 [PT-CT 35] Diagnostic frame master request, IUT as master.28
8.6 Supported frames according to the IUT specification .29
8.6.1 [PT-CT 36] Supported Tx frames according to the IUT specification, IUT
as slave . .29
8.6.2 [PT-CT 37] Supported Rx frames according to the IUT specification, IUT
as slave . .29
9 Communication with failure .30
9.1 General .30
9.2 [PT-CT 38] Bit error, IUT as slave .30
9.3 [PT-CT 39] Framing error in header of published frame, IUT as slave .31
9.4 [PT-CT 40] Framing error in response field of subscribed frame, IUT as slave .32
9.5 [PT-CT 41] Checksum error by inversion, IUT as slave .32
9.6 [PT-CT 42] Checksum error by carry, IUT as slave .32
9.7 [PT-CT 43] Communication robustness, IUT as slave .33
10 Event triggered frames .33
10.1 General .33
10.2 [PT-CT 44] Event triggered frame, IUT as slave .33
10.3 Event triggered frame with collision .34
10.3.1 [PT-CT 45] Event triggered frame with collision resolving, IUT as slave .34
10.3.2 [PT-CT 46] Event triggered frame with errors in collision resolving, IUT
as slave . .34
10.3.3 [PT-CT 47] Event triggered frame with collision resolving, IUT as master .35
10.3.4 [PT-CT 48] Error in transmitted frame with collision, IUT as slave . .35
11 Status management .36
11.1 [PT-CT 49] Error in received frame, IUT as slave .36
11.2 [PT-CT 50] Error in transmitted frame, IUT as slave .36
11.3 [PT-CT 51] response_error signal handling, IUT as slave .37
12 Sleep/wake up/power mode tests .37
12.1 [PT-CT 52] Send “go-to-sleep command”, IUT as master .37
12.2 [PT-CT 53] Receive “go-to-sleep command”, IUT as slave .38
12.3 [PT-CT 54] Receive a wake up signal, IUT as master .39
iv © ISO 2016 – All rights reserved

---------------------- Page: 4 ----------------------
ISO 17987-6:2016(E)

12.4 [PT-CT 55] Receive a wake up signal, IUT as slave .39
12.5 Send a wake up signal .40
12.5.1 [PT-CT 56] Send a wake up signal, IUT as master and IUT as slave .40
12.5.2 [PT-CT 57] Send a block of wake up signals, IUT as slave .40
12.5.3 [PT-CT 58] Wait after one block of wake up signals, IUT as slave .41
12.5.4 [PT-CT 59] Send a wake up signal, frame header from a master following,
IUT as slave .41
12.6 [PT-CT 60] ECU power loss, IUT as master .42
12.7 [PT-CT 61] Powered up with LIN shorted, IUT as master .43
12.8 [PT-CT 62] LIN shorted before scheduling, IUT as master .43
12.9 [PT-CT 63] LIN shorted after start of scheduling, IUT as master .44
13 Sleep state after bus idle .44
13.1 [PT-CT 64] Sleep state after event and bus idle, IUT as slave .44
13.2 [PT-CT 65] Sleep state after bus idle with power up and wake up signal, IUT as slave .45
13.3 [PT-CT 66] Timeout after bus idle, IUT as slave .46
14 Frame ID range assignment .46
14.1 [PT-CT 67] Frame ID range assignment with indirect response, IUT as slave .46
14.2 [PT-CT 68] Frame ID range unassignment with indirect response, IUT as slave .47
15 Wildcards .48
15.1 [PT-CT 69] Request with direct response, IUT as slave .48
16 ReadByIdentifier command .48
16.1 LIN product identification .48
16.1.1 [PT-CT 70] LIN product identification request with direct response, IUT
as slave . .48
16.1.2 [PT-CT 71] LIN product identification — With interleaved unconditional
frame, IUT as slave.49
16.2 [PT-CT 72] ReadByIdentifier command with correct NAD, IUT as slave .49
16.3 [PT-CT 73] ReadByIdentifier command with incorrect addressing, IUT as slave .50
17 NAD assignment .51
17.1 General .51
17.2 [PT-CT 74] NAD assignment — Followed by ReadByIdentifier service, IUT as slave .51
17.3 [PT-CT 75] NAD assignment — With positive response, IUT as slave.51
17.4 [PT-CT 76] NAD assignment — Initial NAD, IUT as slave .51
18 Save Configuration .52
18.1 General .52
18.2 [PT-CT 77] Save Configuration — With positive response, IUT as slave .52
18.3 [PT-CT 78] Save Configuration — Save a new NAD, IUT as slave .52
18.4 [PT-CT 79] Save Configuration — Save new frame identifiers, IUT as slave .53
19 Transport protocol .54
19.1 [PT-CT 80] Transport layer functional request, IUT as slave .54
19.2 [PT-CT 81] Abort diagnostic communication with new diagnostic request, IUT as slave .54
19.3 [PT-CT 82] IUT receives a segmented request as specified, IUT as slave .54
19.4 [PT-CT 83] IUT receives a segmented request interleaved with unconditional
frame, IUT as slave .55
19.5 [PT-CT 84] IUT receives a segmented request with interleaved functional request,
IUT as slave.56
19.6 IUT shall ignore request after timeout .57
19.6.1 [PT-CT 85] IUT shall ignore segmented requests on N_Cr timeout, IUT
Max
as slave . .57
19.6.2 [PT-CT 86] IUT shall observe transport layer N_As timeout, IUT as slave .58
Max
19.7 [PT-CT 87] IUT shall ignore segmented requests with wrong sequence numbering,
IUT as slave.59
19.8 [PT-CT 88] IUT shall respond with correct segmented response, IUT as slave .60
19.9 IUT sends a segmented response with interleaved unconditional frames .61
© ISO 2016 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO 17987-6:2016(E)

19.9.1 [PT-CT 89] IUT sends a segmented response with interleaved
unconditional frame, IUT as slave .61
19.9.2 [PT-CT 90] IUT sends a segmented response with interleaved functional
request, IUT as slave .62
19.10 [PT-CT 91] IUT shall not respond to slave response header if there is no request
before, IUT as slave .63
19.11 [PT-CT 92] IUT shall not respond to slave response header if the response is
already sent, IUT as slave .63
19.12 [PT-CT 93] IUT shall abort segmented response on N_Cs timeout, IUT as slave .64
Max
Bibliography .66
vi © ISO 2016 – All rights reserved

---------------------- Page: 6 ----------------------
ISO 17987-6: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 committ
...

DRAFT INTERNATIONAL STANDARD
ISO/DIS 17987-6.2
ISO/TC 22/SC 31 Secretariat: DIN
Voting begins on: Voting terminates on:
2015-10-12 2015-12-12
Road vehicles — Local Interconnect Network (LIN) —
Part 6:
Protocol conformance test specification
Véhicules routiers — Réseau Internet local (LIN) —
Partie 6: Spécification du protocole d’essai de conformité
ICS: 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-6.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-6.2:2015(E) ISO/DIS 17987-6.2

Contents Page
Foreword . vi
Introduction . vii
1 Scope . 1
2 Normative references . 1
3 Terms, definitions, symbols and abbreviated terms . 1
3.1 Terms and definitions . 1
3.2 Symbols . 1
3.3 Abbreviated terms . 3
4 Conventions . 4
5 General test specification considerations . 4
5.1 General . 4
5.2 Test conditions . 4
5.3 Mandatory requirements for IUT as master . 4
5.4 Mandatory requirements for IUT as slave . 4
5.5 Test case architecture . 5
5.6 Classification . 5
5.7 Test system requirements . 6
5.8 Test system definition . 7
5.9 Global predefinitions for the test setup . 7
6 Essential test cases before test start . 9
6.1 General . 9
6.2 [PT-CT 1] Diagnostic frame 'master request', IUT as slave . 10
6.3 [PT-CT 2] Diagnostic frame 'slave response', IUT as slave . 10
6.4 [PT-CT 3] Error in received frame, IUT as slave . 11
7 Timing parameters . 11
7.1 General . 11
7.2 [PT-CT 4] Length of break field low phase, IUT as master . 11
7.3 [PT-CT 5] Variation of length of break field low phase, IUT as slave . 12
7.4 [PT-CT 6] Length of break delimiter, IUT as master . 12
7.5 [PT-CT 7] Variation of length of break delimiter, IUT as slave . 13
7.6 [PT-CT 8] Inconsistent break field error, IUT as slave . 13
7.7 [PT-CT 9] Inconsistent sync byte field error, IUT as slave . 14
7.8 [PT-CT 10] Verification of the sync byte field, IUT as master . 14
7.9 [PT-CT 11] Incomplete frame reception, IUT as slave . 15
7.10 [PT-CT 12] Unknown frame reception, IUT as slave . 16
7.11 [PT-CT 13] Length of header, IUT as master. 16
7.12 [PT-CT 14] Variation of length of header, IUT as slave . 17
7.13 [PT-CT 15] Bit rate tolerance, IUT as master . 18
7.14 [PT-CT 16] Bit rate tolerance, IUT as slave without making use of synchronization . 18
COPYRIGHT PROTECTED DOCUMENT
7.15 [PT-CT 17] Bit rate tolerance, IUT as slave with making use of synchronization . 19
7.16 Length of response . 19
© ISO 2015, Published in Switzerland
7.17 Verification of schedule table timing . 22
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
7.18 [PT-CT 23] Sample point test, IUT as slave. 24
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
7.19 [PT-CT 24] Initialization time, IUT as slave . 25
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
8 Communication without failure . 26
ISO copyright office
8.1 Variation of LIN identifier . 26
Ch. de Blandonnet 8 • CP 401
8.2 Transmission of the checksum byte . 27
CH-1214 Vernier, Geneva, Switzerland
8.3 Unused bits . 29
Tel. [phone]
8.4 Reserved frame . 30
Fax [phone]
8.5 [PT-CT 35] Diagnostic frame master request, IUT as master. 31
[e-mail]
www.iso.org
ii © ISO 2015 – All rights reserved
© ISO 2015 – All rights reserved iii

---------------------- Page: 2 ----------------------
ISO/DIS 17987-6.2
Contents Page
Foreword . vi
Introduction . vii
1 Scope . 1
2 Normative references . 1
3 Terms, definitions, symbols and abbreviated terms . 1
3.1 Terms and definitions . 1
3.2 Symbols . 1
3.3 Abbreviated terms . 3
4 Conventions . 4
5 General test specification considerations . 4
5.1 General . 4
5.2 Test conditions . 4
5.3 Mandatory requirements for IUT as master . 4
5.4 Mandatory requirements for IUT as slave . 4
5.5 Test case architecture . 5
5.6 Classification . 5
5.7 Test system requirements . 6
5.8 Test system definition . 7
5.9 Global predefinitions for the test setup . 7
6 Essential test cases before test start . 9
6.1 General . 9
6.2 [PT-CT 1] Diagnostic frame 'master request', IUT as slave . 10
6.3 [PT-CT 2] Diagnostic frame 'slave response', IUT as slave . 10
6.4 [PT-CT 3] Error in received frame, IUT as slave . 11
7 Timing parameters . 11
7.1 General . 11
7.2 [PT-CT 4] Length of break field low phase, IUT as master . 11
7.3 [PT-CT 5] Variation of length of break field low phase, IUT as slave . 12
7.4 [PT-CT 6] Length of break delimiter, IUT as master . 12
7.5 [PT-CT 7] Variation of length of break delimiter, IUT as slave . 13
7.6 [PT-CT 8] Inconsistent break field error, IUT as slave . 13
7.7 [PT-CT 9] Inconsistent sync byte field error, IUT as slave . 14
7.8 [PT-CT 10] Verification of the sync byte field, IUT as master . 14
7.9 [PT-CT 11] Incomplete frame reception, IUT as slave . 15
7.10 [PT-CT 12] Unknown frame reception, IUT as slave . 16
7.11 [PT-CT 13] Length of header, IUT as master. 16
7.12 [PT-CT 14] Variation of length of header, IUT as slave . 17
7.13 [PT-CT 15] Bit rate tolerance, IUT as master . 18
7.14 [PT-CT 16] Bit rate tolerance, IUT as slave without making use of synchronization . 18
7.15 [PT-CT 17] Bit rate tolerance, IUT as slave with making use of synchronization . 19
7.16 Length of response . 19
7.17 Verification of schedule table timing . 22
7.18 [PT-CT 23] Sample point test, IUT as slave. 24
7.19 [PT-CT 24] Initialization time, IUT as slave . 25
8 Communication without failure . 26
8.1 Variation of LIN identifier . 26
8.2 Transmission of the checksum byte . 27
8.3 Unused bits . 29
8.4 Reserved frame . 30
8.5 [PT-CT 35] Diagnostic frame master request, IUT as master. 31
© ISO 2015 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/DIS 17987-6.2
8.6 Supported frames according to the IUT specification . 31
9 Communication with failure . 32
9.1 General . 32
9.2 [PT-CT 38] Bit error, IUT as slave . 32
9.3 [PT-CT 39] Framing error in header of published frame, IUT as slave . 34
9.4 [PT-CT 40] Framing error in response field of subscribed frame, IUT as slave . 35
9.5 [PT-CT 41] Checksum error by inversion, IUT as slave . 35
9.6 [PT-CT 42] Checksum error by carry, IUT as slave . 36
9.7 [PT-CT 43] Communication robustness, IUT as slave . 36
10 Event triggered frames . 37
10.1 General . 37
10.2 [PT-CT 44] Event triggered frame, IUT as slave . 37
10.3 Event triggered frame with collision . 38
11 Status management . 40
11.1 [PT-CT 49] Error in received frame, IUT as slave . 40
11.2 [PT-CT 50] Error in transmitted frame, IUT as slave . 40
11.3 [PT-CT 51] response_error signal handling, IUT as slave . 41
12 Sleep / wake up / power mode tests . 42
12.1 [PT-CT 52] Send 'go-to-sleep command', IUT as master . 42
12.2 [PT-CT 53] Receive 'go-to-sleep command', IUT as slave . 42
12.3 [PT-CT 54] Receive a wake up signal, IUT as master . 43
12.4 [PT-CT 55] Receive a wake up signal, IUT as slave . 44
12.5 Send a wake up signal . 45
12.6 [PT-CT 60] ECU power loss, IUT as master . 47
12.7 [PT-CT 61] Powered up with LIN shorted, IUT as master . 48
12.8 [PT-CT 62] LIN shorted before scheduling, IUT as master . 49
12.9 [PT-CT 63] LIN shorted after start of scheduling, IUT as master . 50
13 Sleep state after bus idle . 50
13.1 [PT-CT 64] Sleep state after event and bus idle, IUT as slave . 50
13.2 [PT-CT 65] Sleep state after bus idle with power up and wake up signal, IUT as slave . 51
13.3 [PT-CT 66] Timeout after bus idle, IUT as slave . 52
14 Frame ID range assignment . 53
14.1 [PT-CT 67] Frame ID range assignment with indirect response, IUT as slave . 53
14.2 [PT-CT 68] Frame ID range unassignment with indirect response, IUT as slave . 54
15 Wildcards . 55
15.1 [PT-CT 69] Request with direct response, IUT as slave . 55
16 ReadByIdentifier command . 56
16.1 LIN product identification . 56
16.2 [PT-CT 72] ReadByIdentifier command with correct NAD, IUT as slave . 57
16.3 [PT-CT 73] ReadByIdentifier command with incorrect addressing, IUT as slave . 57
17 NAD assignment . 58
17.1 General . 58
17.2 [PT-CT 74] NAD assignment – followed by ReadByIdentifier service, IUT as slave . 58
17.3 [PT-CT 75] NAD assignment – with positive response, IUT as slave . 59
17.4 [PT-CT 76] NAD assignment – initial NAD, IUT as slave . 59
18 Save Configuration . 61
18.1 General . 61
18.2 [PT-CT 77] Save Configuration – with positive response, IUT as slave . 61
18.3 [PT-CT 78] Save Configuration – save a new NAD, IUT as slave . 61
18.4 [PT-CT 79] Save Configuration – save new frame identifiers, IUT as slave . 62
19 Transport protocol . 62
19.1 [PT-CT 80] Transport layer functional request, IUT as slave . 62
19.2 [PT-CT 81] Abort diagnostic communication with new diagnostic request, IUT as slave . 63
19.3 [PT-CT 82] IUT receives a segmented request as specified, IUT as slave . 63
19.4 [PT-CT 83] IUT receives a segmented request interleaved with unconditional frame, IUT
as slave . 64
iv © ISO 2015 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/DIS 17987-6.2
19.5 [PT-CT 84] IUT receives a segmented request with interleaved functional request, IUT as
slave . 65
19.6 IUT shall ignore request after timeout . 66
19.7 [PT-CT 87] IUT shall ignore segmented requests with wrong sequence numbering, IUT as
slave . 68
19.8 [PT-CT 88] IUT shall respond with correct segmented response, IUT as slave . 69
19.9 IUT sends a segmented response with interleaved unconditional frames . 70
19.10 [PT-CT 91] IUT shall not respond to slave response header if there is no request before,
IUT as slave . 73
19.11 [PT-CT 92] IUT shall not respond to slave response header if the response is already
sent, IUT as slave . 73
19.12 [PT-CT 93] IUT shall abort segmented response on N_Cs timeout, IUT as slave . 73
Max
Bibliography . 75

© ISO 2015 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO/DIS 17987-6.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-6 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 31,
Electrical and electronic equipment.
This second/third/. edition cancels and replaces the first/second/. edition (), [clause(s) / subclause(s) /
table(s) / figure(s) / annex(es)] of which [has / have] been technically revised.
ISO 17987 consists of the following parts, under the general title Road vehicles — Local Interconnect Network
(LIN):
 Part 6: Protocol conformance test specification
 Part [n]:
 Part [n+1]:
 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
vi © ISO 2015 – All rights reserved

---------------------- Page: 6 ----------------------
ISO/DIS 17987-6.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;
 Bit rate 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 state 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 la
...