ISO 17987-6:2016
(Main)Road vehicles — Local Interconnect Network (LIN) — Part 6: Protocol conformance test specification
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
Relations
Standards Content (Sample)
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 .
...
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 2016
© 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
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
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 .
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.