ISO 17987-6:2016

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

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
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. +41 22 749 01 11
8.4 Reserved frame . 30
Fax +41 22 749 09 47
8.5 [PT-CT 35] Diagnostic frame master request, IUT as master. 31
copyright@iso.org
www.iso.org
ii © ISO 2015 – All rights reserved
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/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

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/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

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 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.

ISO/DIS 17987-6.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.

viii © ISO 2015 – All rights reserved

DRAFT INTERNATIONAL STANDARD ISO/DIS 17987-6.2

1 Road vehicles — Local Interconnect Network (LIN) — Part 6:
2 Protocol conformance test specification
3 1 Scope
4 This part of ISO 17987 specifies the LIN protocol conformance test. This test verifies the conformance of LIN
5 communication controllers with respect to ISO 17987-2 LIN transport protocol and network layer services and
6 ISO 17987-3 LIN protocol specification.
7 This document shall provide all necessary technical information to ensure that test results are identical even
8 on different test systems, provided that the particular test suite and the test system are compliant to the
9 content of this document.
10 2 Normative references
11 The following referenced documents are indispensable for the application of this document. For dated
12 references, only the edition cited applies. For undated references, the latest edition of the referenced
13 document (including any amendments) applies.
14 ISO 17987 (Part 2, 3, 4 and 7), Road vehicles – Local interconnect network (LIN)
15 3 Terms, definitions, symbols and abbreviated terms
16 3.1 Terms and definitions
17 For the purposes of this document, the following terms and definitions apply.
18 3.1.1
19 class B device
20 μC-based LIN device. These are devices where it is possible to take measurements on the Rx and Tx
21 interface circuits between the μC and the transceiver.
22 3.1.2
23 class C device
24 integrated LIN devices (ECU) with μC and transceiver. These are devices where it is not possible to take
25 measurements on the Rx and Tx interface circuits between the μC and the transceiver.
26 3.2 Symbols
F bit rate tolerance of the master node (absolute value), according to %
TOL_RES_MASTER
ISO 17987-3
F bit rate tolerance of a slave node without making use of %
TOL_RES_SLAVE
synchronization (absolute value), according to ISO 17987-3
F bit rate tolerance of a slave node making use of synchronization %
TOL_SYNC
(relative value to master node after synchronization, valid for the
complete message), according to ISO 17987-3
ISO/DIS 17987-6.2
F bit rate tolerance of a slave node making use of synchronization, %
TOL_UNSYNC
according to ISO 17987-3
T measured time between end of Wake up signal and start of break s
AWAKE
of a header
T Length of a bit (time), depending on the bit rate s
BIT
T T = T (1 - F ) s
BIT_MAX_MASTER BIT_MAX_MASTER BIT TOL_RES_MASTER
T T = T (1 + F ) s
BIT_MIN_MASTER BIT_MIN_MASTER BIT TOL_RES_MASTER
T T = T s
BIT_NOM_MASTER BIT_NOM_MASTER BIT
T break delimiter, according to ISO 17987-3 1 – 14,6 T
BRKDEL BIT
T calculated maximum of break delimiter: 14,6 T
BRKDEL_MAX BIT
T –(T + 20 T )
HEADER_MAX BRKFLD_MIN BIT
T minimum of break delimiter, according to ISO 17987-3 1 T
BRKDEL_MIN BIT
T break field low phase, according to ISO 17987-3 13 -26,6 T
BRKFLD BIT
T calculated maximum of break field low phase:  26,6 T
BRKFLD_MAX BIT
T –(T + 20 T )
HEADER_MAX BRKDEL_MIN BIT
T minimum of break field low phase, according to ISO 17987-3 13 T
BRKFLD_MIN BIT
T length of a 8 byte frame, according to ISO 17987-3 (see frame 124 – 173,6
FRAME
length) T
BIT
T =T + T
FRAME HEADER RESPONSE
T maximum length of a 8 byte frame, according to ISO 17987-3 173,6 T
FRAME_MAX BIT
T minimum length of a 8 byte frame, according to ISO 17987-3 124 T
FRAME_MIN BIT
T shall be measured between falling edges of the break field s
FRAME_SLOT_MEASURE
T the length is specified in the LDF s
FRAME_SLOT_SPECIFIED
T inter-byte space between sync byte field and protected identifier 0 – 13,6 T
H_INTERBYTE BIT
T length of the header of a message frame based on T nominal 34 – 47,6 T
HEADER BIT BIT
T maximum length of the header of a message frame, according to 47,6 T
HEADER_MAX BIT
ISO 17987-3
T minimum length of the header of a message frame, according to 34 T
HEADER_MIN BIT
ISO 17987-3
T jitter according LDF or NCF of the IUT s
JITTER_DEFINED
T measured jitter as described in ISO 17987-3 (see frame slot) s
JITTER_MEASURE
T maximum response length 126 T
RESPONSE_MAX BIT
T nominal response length 90 T
RESPONSE_MIN BIT
T measured time after that a slave node enters automatically a sleep s
SLEEP
state ISO 17987-2 (see 5.1.4)
2 © ISO 2015 – All rights reserved

ISO/DIS 17987-6.2
28 3.3 Abbreviated terms
AC alternate current
API application programming interface
BFS byte field synchronization
CF transport layer consecutive frame
DC direct current
EBS earliest bit sample
EMC electromagnetic compatibility
EMI electromagnetic interference
EPL electrical physical layer
ESD electrostatic discharge
FF transport layer first frame
GND ground
IUT implementation under test
LBS latest bit sample
Max maximum
Min minimum
NVM non-volatile memory
no. number
OSI open systems interconnection
PID protected identifier
PDU protocol data unit
PT-CT LIN data link layer, network layer and transport layer protocol conformance test
RSID response service identifier
Rx Rx pin of the transceiver
RXD receive data
SF transport layer single frame
SID service identifier
SR sample window repetition
ISO/DIS 17987-6.2
TC test case
TRX transceiver
Tx Tx pin of the transceiver
TXD transmit data
Typ typical
UART universal asynchronous receiver transmitter
30 4 Conventions
31 ISO 17987 and ISO 14229-7 [5] are based on the conventions specified in the OSI Service Conventions
32 (ISO/IEC 10731) [2] as they apply for physical layer, protocol, network and transport protocol and diagnostic
33 services.
34 5 General test specification considerations
35 5.1 General
36 This test specification is not able to cover all contingencies. Due to the fact of the missing vehicle
37 environment, it is possible that the IUT's behaviour differs.
38 5.2 Test conditions
39 The tests shall be done at temperature in the range of 15 °C to 35 °C.
40 5.3 Mandatory requirements for IUT as master
41 The LDF is mandatory to perform the LIN conformance tests for IUT as master.
42 If the LDF is not able to describe all features of the IUT, an additional device specific datasheet is necessary
43 (for example used diagnostic services).
44 Depending on the implementation of the IUT as master, it is allowed to use all possible master request frames
45 (e.g. instead of TST_FRM_ASSIGNIDRANGE) for testing, except mandatory supported frames.
46 IUT initialization is required before each test case. Deviations are marked in the test case respectively.
47 5.4 Mandatory requirements for IUT as slave
48 The NCF or alternatively the LDF is mandatory to perform the LIN conformance tests for IUT as slave.
49 The used test tool shall verify the syntax of the NCF/LDF for plausibility (not for the content).
50 The NCF/LDF shall match with the implementation of the device.
51 If the NCF/LDF is not able to describe all features of the IUT, an additional device specific datasheet is
52 necessary (for example used diagnostic services).
53 If an IUT is not fully configured after reset, an IUT initialization is required before each test case, except if the
54 AssignFrameIdentifierRange command is part of the test. Preconfigured slaves are fully configured after reset.
55 Deviations are marked in the test case respectively.
4 © ISO 2015 – All rights reserved

ISO/DIS 17987-6.2
56 5.5 Test case architecture
57 In the description of each test case it is specified for which device type the test case is applicable, for master
58 or slave.
59 Each specification of a test case consists of five parts:
60  Set Up
61  defines the IUT as master or slave;
62  defines settings for the Implementation Under Test (IUT) and the test system (details see 5.9.1);
63  defines the bit rate for the respective test case;
64  System Init
65  defines to what state the IUT shall have been set before starting the execution of the test. If not
66 otherwise defined, the IUT as master sends requests respective the IUT as slave waits for requests;
67  an initialization of the IUT shall be performed before each test case. To initialise the IUT a reset is
68 carried out and thereafter the IUT shall be reconfigured e.g. by a Frame ID configuration process;
69  Test
70  defines the way of stimulating the IUT;
71  If more than one step is defined in this field, the steps shall be executed in the order as they are
72 stated in the document;
73  Verification
74  defines the expected behaviour of the IUT when executing the test steps,
75  Reference
76  defines the reference to this or other parts of ISO 17987.
77 5.6 Classification
78 The classification describes the LIN integration level.
79 Table 1 defines the classification.
80 Table 1 — Classification
No. Classification Description Comment
1 Class A Device Transceiver devices Data Link Layer and Node Configuration / Network
Management Tests not applicable
2 Class B Device μC based devices IUT as master or slave with Rx and Tx pin connectors
3 Class C Device integrated devices (ECU) IUT as master or slave with analog LIN bus connector
with μC and transceiver available
ISO/DIS 17987-6.2
82 5.7 Test system requirements
83 5.7.1 Generation of LIN frames
84 The test system shall ensure the precision of the bit time of a master node defined in ISO 17987-3.
85 5.7.2 Standard requirements for the test cases
86 For proper measurement and verification of LIN frames, the test system shall use a minimum over sampling
87 factor of 16; see equation (1).
Definition of equation (1)
T
BIT
sample resolution <=
89 5.7.3 Special requirements for bit timing testing
90 For proper measurement and verification of the bit timing tests, the test system shall measure with a minimum
91 over sampling of 10 to the precision of the master tolerance given by the ISO 17987-4; see equation (2). See
92 7.13, 7.14, 7.15.
Definition of equation (2)
0,5
T
BIT
bit time sample resolution <=
94 5.7.4 Test system for IUT as slave node
95 If the IUT is a slave node the test system acts as a master node. The transmission of a frame by the test
96 system is a synonym for the transmission of the frame header if the specific frame is published by the IUT
97 according to the frame definition.
98 Example: "The test system sends TST_FRM_IUT_TX" is corresponding to "The test system sends the header of
99 TST_FRM_IUT_TX".
100 5.7.5 Sleep state verification for IUT as slave node
101 Some test cases require verification of the slave node bus sleep state after transmission of a go-to-sleep
102 command or bus idle timeout. As a direct verification is not possible due to the design of the test system an
103 indirect method is needed. Depending on the IUT specification one of the following verification alternatives
104 shall be selected for the sleep state verification procedure:
105  Observing of the current consumption of the IUT. It shall be verified that the current consumption is
106 reduces after sleep state criteria is fulfilled and the ECU specific delay is passed. The ECU specific delay
107 between entering sleep state and reduction of ECU current shall be provided by IUT vendor and
108 considered in the test verification.
109 Prerequisite: ECU enters low power mode after a specified delay when the LIN sleep state is entered.
110  The test system forces the sleep state transition. After that the IUT is stimulated to send a wakeup signal
111 in sleep state. If possible it should also be verified that a wake up frame can't be triggered during normal
112 communication. (A slave node shall not be able to send a wakeup if it is in operational state.)
113 Prerequisite: ECU wake up can be triggered by an external stimulus.
114  The test system forces the sleep state transition. In the next step the test system sends the header of
115 TST_FRM_STATUS_SIG multiple times without preceding wake up one or more headers are not
6 © ISO 2015 – All rights reserved

ISO/DIS 17987-6.2
116 answered by the slave node because the
...