BS ISO 17987-6-2016 Road vehicles Local Interconnect Network (LIN) Protocol conformance test specification《道路车辆 局域互连网络(LIN) 协议一致性试验规范》.pdf

1、BS ISO 17987-6:2016Road vehicles LocalInterconnect Network (LIN)Part 6: Protocol conformance testspecificationBSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06BS ISO 17987-6:2016 BRITISH STANDARDNational forewordThis British Standard is the UK implementation of ISO 17

2、987-6:2016.The UK participation in its preparation was entrusted to TechnicalCommittee AUE/16, Data Communication (Road Vehicles).A list of organizations represented on this committee can beobtained on request to its secretary.This publication does not purport to include all the necessaryprovisions

3、of a contract. Users are responsible for its correctapplication. The British Standards Institution 2016.Published by BSI Standards Limited 2016ISBN 978 0 580 81733 5ICS 43.040.15Compliance with a British Standard cannot confer immunity fromlegal obligations.This British Standard was published under

4、the authority of theStandards Policy and Strategy Committee on 31 October 2016.Amendments/corrigenda issued since publicationDate Text affectedBS ISO 17987-6:2016 ISO 2016Road vehicles Local Interconnect Network (LIN) Part 6: Protocol conformance test specificationVhicules routiers Rseau Internet lo

5、cal (LIN) Partie 6: Spcification du protocole dessai de conformitINTERNATIONAL STANDARDISO17987-6First edition2016-10-01Reference numberISO 17987-6:2016(E)BS ISO 17987-6:2016ISO 17987-6:2016(E)ii ISO 2016 All rights reservedCOPYRIGHT PROTECTED DOCUMENT ISO 2016, Published in SwitzerlandAll rights re

6、served. 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

7、ISO at the address below or ISOs member body in the country of the requester.ISO copyright officeCh. de Blandonnet 8 CP 401CH-1214 Vernier, Geneva, SwitzerlandTel. +41 22 749 01 11Fax +41 22 749 09 47copyrightiso.orgwww.iso.orgBS ISO 17987-6:2016ISO 17987-6:2016(E)Foreword viiIntroduction viii1 Scop

8、e . 12 Normative references 13 Terms, definitions, symbols and abbreviated terms . 13.1 Terms and definitions . 13.2 Symbols . 23.3 Abbreviated terms . 34 Conventions . 45 General test specification considerations 45.1 General . 45.2 Test conditions 45.3 Mandatory requirements for IUT as master 45.4

9、 Mandatory requirements for IUT as slave . 55.5 Test case architecture 55.6 Classification . 65.7 Test system requirements . 65.7.1 Generation of LIN frames . 65.7.2 Standard requirements for the test cases 65.7.3 Special requirements for bit timing testing 65.7.4 Test system for IUT as slave node .

10、 65.7.5 Sleep state verification for IUT as slave node . 65.8 Test system definition . 75.9 Global predefinitions for the test setup . 75.9.1 Configuration of IUT and test system. 75.9.2 Default delays for frame headers . 95.9.3 Default bit rate . 95.9.4 Time measurement 95.9.5 Default spaces betwee

11、n the different frame parts of a LIN message 96 Essential test cases before test start .106.1 General 106.2 PT-CT 1 Diagnostic frame “master request”, IUT as slave .106.3 PT-CT 2 Diagnostic frame “slave response”, IUT as slave 106.4 PT-CT 3 Error in received frame, IUT as slave 107 Timing parameters

12、 .117.1 General 117.2 PT-CT 4 Length of break field low phase, IUT as master .117.3 PT-CT 5 Variation of length of break field low phase, IUT as slave .117.4 PT-CT 6 Length of break delimiter, IUT as master .127.5 PT-CT 7 Variation of length of break delimiter, IUT as slave 127.6 PT-CT 8 Inconsisten

13、t break field error, IUT as slave 137.7 PT-CT 9 Inconsistent sync byte field error, IUT as slave 137.8 PT-CT 10 Verification of the sync byte field, IUT as master 147.9 PT-CT 11 Incomplete frame reception, IUT as slave 147.10 PT-CT 12 Unknown frame reception, IUT as slave 157.11 PT-CT 13 Length of h

14、eader, IUT as master . 167.12 PT-CT 14 Variation of length of header, IUT as slave .167.13 PT-CT 15 Bit rate tolerance, IUT as master 177.14 PT-CT 16 Bit rate tolerance, IUT as slave without making use of synchronization 177.15 PT-CT 17 Bit rate tolerance, IUT as slave with making use of synchroniza

15、tion .187.16 Length of response . 187.16.1 PT-CT 18 Length of response, IUT as slave.18 ISO 2016 All rights reserved iiiContents PageBS ISO 17987-6:2016ISO 17987-6:2016(E)7.16.2 PT-CT 19 Length of response, IUT as master197.16.3 PT-CT 20 Acceptance of response field, IUT as slave .207.17 Verificatio

16、n of schedule table timing 217.17.1 PT-CT 21 Verification of jitter, IUT as master .217.17.2 PT-CT 22 Schedule table management, IUT as master 227.18 PT-CT 23 Sample point test, IUT as slave 227.19 PT-CT 24 Initialization time, IUT as slave . 238 Communication without failure 248.1 Variation of LIN

17、identifier. 248.1.1 PT-CT 25 Variation of LIN PID, IUT as master .248.1.2 PT-CT 26 Variation of LIN PIDs of subscribed frames, IUT as slave .248.1.3 PT-CT 27 Variation of LIN identifier of published frames, IUT as slave 258.2 Transmission of the checksum byte. 258.2.1 PT-CT 28 Transmission of the ch

18、ecksum byte “classic checksum”, IUT as slave 258.2.2 PT-CT 29 Transmission of the checksum byte “enhanced checksum”, IUT as slave .268.2.3 PT-CT 30 Transmission of the checksum byte “classic checksum”, IUT as master 268.2.4 PT-CT 31 Transmission of the checksum byte of unconditional frames, IUT as m

19、aster .268.3 Unused bits 278.3.1 PT-CT 32 Unused bits, IUT as master 278.3.2 PT-CT 33 Unused bits, IUT as slave .278.4 Reserved frame 288.4.1 PT-CT 34 Reserved frame, IUT as slave .288.5 PT-CT 35 Diagnostic frame master request, IUT as master.288.6 Supported frames according to the IUT specification

20、 298.6.1 PT-CT 36 Supported Tx frames according to the IUT specification, IUT as slave .298.6.2 PT-CT 37 Supported Rx frames according to the IUT specification, IUT as slave .299 Communication with failure .309.1 General 309.2 PT-CT 38 Bit error, IUT as slave . 309.3 PT-CT 39 Framing error in header

21、 of published frame, IUT as slave 319.4 PT-CT 40 Framing error in response field of subscribed frame, IUT as slave .329.5 PT-CT 41 Checksum error by inversion, IUT as slave .329.6 PT-CT 42 Checksum error by carry, IUT as slave 329.7 PT-CT 43 Communication robustness, IUT as slave .3310 Event trigger

22、ed frames 3310.1 General 3310.2 PT-CT 44 Event triggered frame, IUT as slave . 3310.3 Event triggered frame with collision . 3410.3.1 PT-CT 45 Event triggered frame with collision resolving, IUT as slave .3410.3.2 PT-CT 46 Event triggered frame with errors in collision resolving, IUT as slave .3410.

23、3.3 PT-CT 47 Event triggered frame with collision resolving, IUT as master 3510.3.4 PT-CT 48 Error in transmitted frame with collision, IUT as slave 3511 Status management 3611.1 PT-CT 49 Error in received frame, IUT as slave .3611.2 PT-CT 50 Error in transmitted frame, IUT as slave .3611.3 PT-CT 51

24、 response_error signal handling, IUT as slave 3712 Sleep/wake up/power mode tests 3712.1 PT-CT 52 Send “go-to-sleep command”, IUT as master .3712.2 PT-CT 53 Receive “go-to-sleep command”, IUT as slave .3812.3 PT-CT 54 Receive a wake up signal, IUT as master .39iv ISO 2016 All rights reservedBS ISO 1

25、7987-6:2016ISO 17987-6:2016(E)12.4 PT-CT 55 Receive a wake up signal, IUT as slave 3912.5 Send a wake up signal 4012.5.1 PT-CT 56 Send a wake up signal, IUT as master and IUT as slave 4012.5.2 PT-CT 57 Send a block of wake up signals, IUT as slave .4012.5.3 PT-CT 58 Wait after one block of wake up s

26、ignals, IUT as slave 4112.5.4 PT-CT 59 Send a wake up signal, frame header from a master following, IUT as slave 4112.6 PT-CT 60 ECU power loss, IUT as master 4212.7 PT-CT 61 Powered up with LIN shorted, IUT as master .4312.8 PT-CT 62 LIN shorted before scheduling, IUT as master .4312.9 PT-CT 63 LIN

27、 shorted after start of scheduling, IUT as master .4413 Sleep state after bus idle .4413.1 PT-CT 64 Sleep state after event and bus idle, IUT as slave 4413.2 PT-CT 65 Sleep state after bus idle with power up and wake up signal, IUT as slave 4513.3 PT-CT 66 Timeout after bus idle, IUT as slave 4614 F

28、rame ID range assignment .4614.1 PT-CT 67 Frame ID range assignment with indirect response, IUT as slave 4614.2 PT-CT 68 Frame ID range unassignment with indirect response, IUT as slave 4715 Wildcards 4815.1 PT-CT 69 Request with direct response, IUT as slave 4816 ReadByIdentifier command .4816.1 LI

29、N product identification 4816.1.1 PT-CT 70 LIN product identification request with direct response, IUT as slave .4816.1.2 PT-CT 71 LIN product identification With interleaved unconditional frame, IUT as slave.4916.2 PT-CT 72 ReadByIdentifier command with correct NAD, IUT as slave .4916.3 PT-CT 73 R

30、eadByIdentifier command with incorrect addressing, IUT as slave 5017 NAD assignment .5117.1 General 5117.2 PT-CT 74 NAD assignment Followed by ReadByIdentifier service, IUT as slave .5117.3 PT-CT 75 NAD assignment With positive response, IUT as slave 5117.4 PT-CT 76 NAD assignment Initial NAD, IUT a

31、s slave 5118 Save Configuration .5218.1 General 5218.2 PT-CT 77 Save Configuration With positive response, IUT as slave 5218.3 PT-CT 78 Save Configuration Save a new NAD, IUT as slave .5218.4 PT-CT 79 Save Configuration Save new frame identifiers, IUT as slave 5319 Transport protocol 5419.1 PT-CT 80

32、 Transport layer functional request, IUT as slave .5419.2 PT-CT 81 Abort diagnostic communication with new diagnostic request, IUT as slave 5419.3 PT-CT 82 IUT receives a segmented request as specified, IUT as slave 5419.4 PT-CT 83 IUT receives a segmented request interleaved with unconditional fram

33、e, IUT as slave 5519.5 PT-CT 84 IUT receives a segmented request with interleaved functional request, IUT as slave 5619.6 IUT shall ignore request after timeout 5719.6.1 PT-CT 85 IUT shall ignore segmented requests on N_CrMaxtimeout, IUT as slave .5719.6.2 PT-CT 86 IUT shall observe transport layer

34、N_AsMaxtimeout, IUT as slave 5819.7 PT-CT 87 IUT shall ignore segmented requests with wrong sequence numbering, IUT as slave 5919.8 PT-CT 88 IUT shall respond with correct segmented response, IUT as slave 6019.9 IUT sends a segmented response with interleaved unconditional frames 61 ISO 2016 All rig

35、hts reserved vBS ISO 17987-6:2016ISO 17987-6:2016(E)19.9.1 PT-CT 89 IUT sends a segmented response with interleaved unconditional frame, IUT as slave 6119.9.2 PT-CT 90 IUT sends a segmented response with interleaved functional request, IUT as slave 6219.10 PT-CT 91 IUT shall not respond to slave res

36、ponse header if there is no request before, IUT as slave . 6319.11 PT-CT 92 IUT shall not respond to slave response header if the response is already sent, IUT as slave 6319.12 PT-CT 93 IUT shall abort segmented response on N_CsMaxtimeout, IUT as slave 64Bibliography .66vi ISO 2016 All rights reserv

37、edBS ISO 17987-6:2016ISO 17987-6:2016(E)ForewordISO (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 bod

38、y 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 Electrote

39、chnical 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

40、 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 resp

41、onsible 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

42、 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 ISOs adherence to the World Trade Organization (WTO) principles in the Technical Barriers to Tra

43、de (TBT) see the following URL: www.iso.org/iso/foreword.html.The committee responsible for this document is ISO/TC 22, Road vehicles, Subcommittee SC 31, Data communication.A list of all parts in the ISO 17987 series can be found on the ISO website. ISO 2016 All rights reserved viiBS ISO 17987-6:20

44、16ISO 17987-6:2016(E)IntroductionISO 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 asynchro

45、nous 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 l

46、ow 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 s

47、upport 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

48、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 programme

49、rs 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, tran