Skip to product information
1 of 8

PayPal, credit cards. Download editable-PDF and invoice in 1 second!

GB/T 42691.6-2023 English PDF (GBT42691.6-2023)

GB/T 42691.6-2023 English PDF (GBT42691.6-2023)

Regular price $1,130.00 USD
Regular price Sale price $1,130.00 USD
Sale Sold out
Shipping calculated at checkout.
Quotation: In 1-minute, 24-hr self-service. Click here GB/T 42691.6-2023 to get it for Purchase Approval, Bank TT...

GB/T 42691.6-2023: Road vehicles -- Local Internet Network(LIN) -- Part 6: Protocol conformance test specification

GB/T 42691.6-2023
GB
NATIONAL STANDARD OF THE
PEOPLE’S REPUBLIC OF CHINA
ICS 43.040.15
CCS T 36
GB/T 42691.6-2023 / ISO 17987-6:2016
Road vehicles - Local Interconnect Network (LIN) - Part 6:
Protocol conformance test specification
(ISO 17987-6:2016, IDT)
ISSUED ON: MAY 23, 2023
IMPLEMENTED ON: DECEMBER 01, 2023
Issued by: State Administration for Market Regulation;
Standardization Administration of the People’s Republic of China.
Table of Contents
Foreword ... 6
Introduction ... 8
1 Scope ... 11
2 Normative references ... 11
3 Terms, definitions, symbols and abbreviated terms ... 11
3.1 Terms and definitions ... 11
3.2 Symbols ... 12
3.3 Abbreviated terms ... 14
4 Conventions ... 15
5 General test specification considerations ... 16
5.1 General ... 16
5.2 Test conditions ... 16
5.3 Mandatory requirements for IUT as master ... 16
5.4 Mandatory requirements for IUT as slave ... 16
5.5 Test case architecture ... 16
5.6 Classification ... 17
5.7 Test system requirements ... 18
5.8 Test system definition ... 20
5.9 Global predefinitions for the test setup ... 20
6 Essential test cases before test start ... 22
6.1 General ... 22
6.2 [PT-CT 1] Diagnostic frame “master request”, IUT as slave ... 22
6.3 [PT-CT 2] Diagnostic frame “slave response”, IUT as slave ... 23
6.4 [PT-CT 3] Error in received frame, IUT as slave ... 23
7 Timing parameters ... 24
7.1 General ... 24
7.2 [PT-CT 4] Length of break field low phase, IUT as master ... 24
7.3 [PT-CT 5] Variation of length of break field low phase, IUT as slave ... 24 7.4 [PT-CT 6] Length of break delimiter, IUT as master ... 25
7.5 [PT-CT 7] Variation of length of break delimiter, IUT as slave ... 25 7.6 [PT-CT 8] Inconsistent break field error, IUT as slave ... 26
7.7 [PT-CT 9] Inconsistent sync byte field error, IUT as slave ... 27
7.8 [PT-CT 10] Verification of the sync byte field, IUT as master ... 27 7.9 [PT-CT 11] Incomplete frame reception, IUT as slave ... 28
7.10 [PT-CT 12] Unknown frame reception, IUT as slave ... 28
7.11 [PT-CT 13] Length of header, IUT as master ... 29
7.12 [PT-CT 14] Variation of length of header, IUT as slave ... 29
7.13 [PT-CT 15] Bit rate tolerance, IUT as master ... 30
7.14 [PT-CT 16] Bit rate tolerance, IUT as slave without making use of synchronization ... 31
7.15 [PT-CT 17] Bit rate tolerance, IUT as slave with making use of synchronization .. 31 7.16 Length of response ... 32
7.17 Verification of schedule table timing ... 35
7.18 [PT-CT 23] Sample point test, IUT as slave ... 36
7.19 [PT-CT 24] Initialization time, IUT as slave ... 37
8 Communication without failure ... 37
8.1 Variation of LIN identifier ... 37
8.2 Transmission of the checksum byte ... 39
8.3 Unused bits ... 41
8.4 Reserved frame ... 42
8.5 [PT-CT 35] Diagnostic frame master request, IUT as master ... 42
8.6 Supported frames according to the IUT specification ... 43
9 Communication with failure ... 44
9.1 General ... 44
9.2 [PT-CT 38] Bit error, IUT as slave ... 44
9.3 [PT-CT 39] Framing error in header of published frame, IUT as slave ... 46 9.4 [PT-CT 40] Framing error in response field of subscribed frame, IUT as slave ... 46 9.5 [PT-CT 41] Checksum error by inversion, IUT as slave ... 47
9.6 [PT-CT 42] Checksum error by carry, IUT as slave ... 47
9.7 [PT-CT 43] Communication robustness, IUT as slave ... 48
10 Event triggered frames ... 48
10.1 General ... 48
10.2 [PT-CT 44] Event triggered frame, IUT as slave ... 48
10.3 Event triggered frame with collision ... 49
11 Status management ... 51
11.1 [PT-CT 49] Error in received frame, IUT as slave ... 51
11.2 [PT-CT 50] Error in transmitted frame, IUT as slave ... 52
11.3 [PT-CT 51] response_error signal handling, IUT as slave ... 52
12 Sleep/wake up/power mode tests ... 53
12.1 [PT-CT 52] Send “go-to-sleep command”, IUT as master ... 53
12.2 [PT-CT 53] Receive “go-to-sleep command”, IUT as slave ... 53
12.3 [PT-CT 54] Receive a wake up signal, IUT as master ... 54
12.4 [PT-CT 55] Receive a wake up signal, IUT as slave ... 55
12.5 Send a wake up signal ... 56
12.6 [PT-CT 60] ECU power loss, IUT as master ... 58
12.7 [PT-CT 61] Powered up with LIN shorted, IUT as master ... 59
12.8 [PT-CT 62] LIN shorted before scheduling, IUT as master ... 59
12.9 [PT-CT 63] LIN shorted after start of scheduling, IUT as master... 60 13 Sleep state after bus idle ... 61
13.1 [PT-CT 64] Sleep state after event and bus idle, IUT as slave ... 61 13.2 [PT-CT 65] Sleep state after bus idle with power up and wake up signal, IUT as slave ... 62
13.3 [PT-CT 66] Timeout after bus idle, IUT as slave ... 62
14 Frame ID range assignment ... 63
14.1 [PT-CT 67] Frame ID range assignment with indirect response, IUT as slave ... 63 14.2 [PT-CT 68] Frame ID range unassignment with indirect response, IUT as slave ... 64 15 Wildcards ... 65
15.1 [PT-CT 69] Request with direct response, IUT as slave ... 65
16 ReadByIdentifier command ... 65
16.1 LIN product identification ... 65
16.2 [PT-CT 72] ReadByIdentifier command with correct NAD, IUT as slave ... 66 16.3 [PT-CT 73] ReadByIdentifier command with incorrect addressing, IUT as slave .. 67 17 NAD assignment ... 68
17.1 General ... 68
17.2 [PT-CT 74] NAD assignment — Followed by ReadByIdentifier service, IUT as slave ... 68
17.3 [PT-CT 75] NAD assignment — With positive response, IUT as slave ... 69 17.4 [PT-CT 76] NAD assignment — Initial NAD, IUT as slave ... 69
18 Save Configuration ... 70
18.1 General ... 70
18.2 [PT-CT 77] Save Configuration — With positive response, IUT as slave ... 70 18.3 [PT-CT 78] Save Configuration — Save a new NAD, IUT as slave ... 70 18.4 [PT-CT 79] Save Configuration — Save new frame identifiers, IUT as slave ... 71 19 Transport protocol ... 71
19.1 [PT-CT 80] Transport layer functional request, IUT as slave ... 71 19.2 [PT-CT 81] Abort diagnostic communication with new diagnostic request, IUT as slave ... 72
19.3 [PT-CT 82] IUT receives a segmented request as specified, IUT as slave ... 73 19.4 [PT-CT 83] IUT receives a segmented request interleaved with unconditional frame, IUT as slave ... 73
19.5 [PT-CT 84] IUT receives a segmented request with interleaved functional request, IUT as slave ... 74
19.6 IUT shall ignore request after timeout ... 75
19.7 [PT-CT 87] IUT shall ignore segmented requests with wrong sequence numbering, IUT as slave ... 77
19.8 [PT-CT 88] IUT shall respond with correct segmented response, IUT as slave ... 78 19.9 IUT sends a segmented response with interleaved unconditional frames ... 79 19.10 [PT-CT 91] IUT shall not respond to slave response header if there is no request before, IUT as slave ... 81
19.11 [PT-CT 92] IUT shall not respond to slave response header if the response is already sent, IUT as slave ... 82
19.12 [PT-CT 93] IUT shall abort segmented response on N_CsMax timeout, IUT as slave ... 82
Bibliography ... 84
Foreword
This document was drafted in accordance with the rules provided in GB/T 1.1-2020 Directives for standardization - Part 1: Rules for the structure and drafting of standardizing documents.
This document is Part 6 of GB/T 42691 Road vehicles - Local Interconnect Network (LIN). The following parts have been issued for GB/T 42691:
-- 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; -- Part 8: Electrical physical layer (EPL) specification: LIN over DC powerline (DC- LIN).
This document is identical to ISO 17987-6:2016, Road vehicles - Local Interconnect Network (LIN) - Part 6: Protocol conformance test specification.
Please note that some of the contents of this document may involve patents. The issuing organization of this document is not responsible for identifying patents. This document was proposed by the Ministry of Industry and Information Technology of the People’s Republic of China.
This document shall be under the jurisdiction of National Technical Committee on Road Vehicles of Standardization Administration of China (SAC/TC 114).
Drafting organizations of this document: FAW Car Co., Ltd., China Automotive Technology and Research Center Co., Ltd., Great Wall Motor Company Limited, Beijing National New Energy Vehicle Technology Innovation Center Co., Ltd., FAW- Volkswagen, Geely Automobile Research Institute (Ningbo) Co., Ltd., Pan Asia Technical Automotive Center Co., Ltd., Huizhou Desay SV Automotive Co., Ltd., Dongfeng Motor Corporation, SAIC-GM-Wuling Automobile, CATARC (Tianjin) Automotive Engineering Research Institute Co., Ltd., SAIC MAXUS Automotive Co., Ltd.
Road vehicles - Local Interconnect Network (LIN) - Part 6:
Protocol conformance test specification
1 Scope
This document specifies the protocol conformance test requirements and methods for Local Area Network (hereinafter referred to as LIN) of road vehicles. This test verifies the conformance of LIN communication controllers with respect to ISO 17987-2 and ISO 17987-3.
This document 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.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the version corresponding to that date is applicable to this document; for undated references, the latest version (including all amendments) is applicable to this document. GB/T 42691.2-2023, Road vehicles - Local Interconnect Network (LIN) - Part 2: Transport protocol and network layer services (ISO 17987-2:2016, IDT)
GB/T 42691.3-2023, Road vehicles - Local Interconnect Network (LIN) - Part 3: Protocol specification (ISO 17987-3:2016, IDT)
GB/T 42691.4-2023, Road vehicles - Local Interconnect Network (LIN) - Part 4: Electrical physical layer (EPL) specification 12 V/24 V (ISO 17987-4:2016, IDT) 3 Terms, definitions, symbols and abbreviated terms
3.1 Terms and definitions
3.1.1
class B device
μC-based LIN device.
Note: These are devices where it is possible to take measurements on the Rx and Tx interface circuits between the μC and the transceiver.
-- The test system forces the sleep state transition. After that, the IUT is stimulated to send a wakeup signal in sleep state. If possible, it should also be verified that a wake up frame can’t be triggered during normal communication (a slave node shall not be able to send a wakeup if it is in operational state). Prerequisite: ECU wake up can be triggered by an external stimulus.
-- The test system forces the sleep state transition. In the next step, the test system sends the header of TST_FRM_STATUS_SIG multiple times without preceding wake up one or more headers are not answered by the slave node because the first SynchBreak is taken as wake up event and the slave node performs its
initialization sequence. Latest after 100 ms, the slave shall answer to the headers. Prerequisite: ECU enters a low power mode when sleep state is entered and requires more than one header to recover from sleep state (otherwise, it could not be distinguished from operational state).
-- A monitor or debugger is used to verify the network management state of the IUT. Prerequisite: Accessible port for monitor or debugger.
-- An ECU test pin is used to indicate the current network management state. Prerequisite: Free and accessible test pin.
-- In Class B devices, the LIN transceiver is set into sleep state – verify LIN transceiver state by oscilloscope/logger/…
Prerequisite: LIN transceiver is set to sleep state (with a specified delay) when the slave node enters sleep state.
-- A sleep counter is implemented in the slave node which is incremented anytime the sleep state is entered. The current sleep counter state can be read out by a ReadByIdentifier request. Depending on the ECU power mode, the counter is located in RAM or non-volatile memory. The test system verifies the sleep counter before and after performing the test and derives the verdict from the counter difference.
Prerequisite: The counter is implemented in the ECU and accessible via
ReadByIdentifier request.
Note: LIN sleep state and ECU power mode are not identical. ECU power mode transitions depend on ECU requirements that can be triggered by LIN sleep state transitions. This test only verifies the valid reception of a sleep state frame and entering LIN sleep state. The ECU power mode may only be used as indicator for the LIN sleep state.

View full details