iTeh StandardsiTeh Standards
EURUSD
Your shopping cart is empty.
ISO

ISO 17987-6:2025

(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

This document 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. 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. Annex A, Annex B and Annex C specify the protocol conformance test plans for responder nodes supporting auto addressing procedures according procedure C, procedure D or procedure E, see ISO 17987-3:2025, Annex C.

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

General Information

Status
Published
Publication Date
30-Apr-2025
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 - Data communication
Current Stage
6060 - International Standard published
Start Date
01-May-2025
Due Date
30-May-2025
Completion Date
01-May-2025
Ref Project

Relations

Revises
ISO 17987-6:2016 - Road vehicles — Local Interconnect Network (LIN) — Part 6: Protocol conformance test specification
Effective Date
06-Jun-2022

Buy Standard

ISO 17987-6:2025 - Road vehicles — Local Interconnect Network (LIN) — Part 6: Protocol conformance test specification Released:1. 05. 2025ISO 17987-6:2025 - Road vehicles — Local Interconnect Network (LIN) — Part 6: Protocol conformance test specification Released:1. 05. 2025
PreviousNext
Standard
ISO 17987-6:2025 - Road vehicles — Local Interconnect Network (LIN) — Part 6: Protocol conformance test specification Released:1. 05. 2025
English language
104 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


International
Standard
ISO 17987-6
Second edition
Road vehicles — Local Interconnect
2025-05
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 2025
All rights reserved. Unless otherwise specified, or required in the context of its implementation, 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
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
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 . 5
5.1 General .5
5.2 Test conditions .5
5.3 Mandatory requirements for IUT as commander .5
5.4 Mandatory requirements for IUT as responder .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 Common requirements for the test cases .6
5.7.3 Common requirements for bit timing testing .6
5.7.4 Test system for IUT as responder node .7
5.7.5 Sleep state verification for IUT as responder node .7
5.8 Test system definition .8
5.9 Global predefinitions for the test setup .8
5.9.1 Configuration of IUT and test system .8
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 .10
6 Essential test cases before test start . 10
6.1 General .10
6.2 [PT-CT 1] Diagnostic frame “commander request”, IUT as responder .10
6.3 [PT-CT 2] Diagnostic frame “responder response”, IUT as responder .10
6.4 [PT-CT 3] Error in received frame, IUT as responder .11
7 Timing parameters .11
7.1 General .11
7.2 [PT-CT 4] Length of break field low phase, IUT as commander .11
7.3 [PT-CT 5] Variation of length of break field low phase, IUT as responder . 12
7.4 [PT-CT 6] Length of break delimiter, IUT as commander . 12
7.5 [PT-CT 7] Variation of length of break delimiter, IUT as responder . 13
7.6 [PT-CT 8] Inconsistent break field error, IUT as responder .14
7.7 [PT-CT 9] Inconsistent sync byte field error, IUT as responder .14
7.8 [PT-CT 10] Bit rate detection, IUT as responder with making use of detection .14
7.9 [PT-CT 10] Verification of the sync byte field, IUT as commander .16
7.10 [PT-CT 11] Incomplete frame reception, IUT as responder .16
7.11 [PT-CT 12] Unknown frame reception, IUT as responder .17
7.12 [PT-CT 13] Length of header, IUT as commander .17
7.13 [PT-CT 14] Variation of length of header, IUT as responder .18
7.14 [PT-CT 15] Bit rate tolerance, IUT as commander .18
7.15 [PT-CT 16] Bit rate tolerance, IUT as responder without making use of synchronization .19
7.16 [PT-CT 17] Bit rate tolerance, IUT as responder with making use of synchronization .19
7.17 Length of response . 20

iii
7.17.1 [PT-CT 18] Length of response, IUT as responder . 20
7.17.2 [PT-CT 19] Length of response, IUT as commander .21
7.17.3 [PT-CT 20] Acceptance of response field, IUT as responder .21
7.18 Verification of schedule table timing . 22
7.18.1 [PT-CT 21] Verification of jitter, IUT as commander . 22
7.18.2 [PT-CT 22] Schedule table management, IUT as commander . 23
7.19 [PT-CT 23] Sample point test, IUT as responder .24
7.20 [PT-CT 24] Initialization time, IUT as responder. 25
8 Communication without failure .26
8.1 Variation of LIN identifier . 26
8.1.1 [PT-CT 25] Variation of LIN PID, IUT as commander . 26
8.1.2 [PT-CT 26] Variation of LIN PIDs of subscribed frames, IUT as responder . 26
8.1.3 [PT-CT 27] Variation of LIN identifier of published frames, IUT as responder .27
8.2 Transmission of the checksum byte .27
8.2.1 [PT-CT 28] Transmission of the checksum byte “classic checksum”, IUT as
responder .27
8.2.2 [PT-CT 29] Transmission of the checksum byte “enhanced checksum”, IUT as
responder . 28
8.2.3 [PT-CT 30] Transmission of the checksum byte “classic checksum”, IUT as
commander. 28
8.2.4 [PT-CT 31] Transmission of the checksum byte of unconditional frames, IUT as
commander. 28
8.3 Unused bits . 29
8.3.1 [PT-CT 32] Unused bits, IUT as commander . 29
8.3.2 [PT-CT 33] Unused bits, IUT as responder . 29
8.4 Reserved frame . 30
8.4.1 [PT-CT 34] Reserved frame, IUT as responder . 30
8.5 [PT-CT 35] Diagnostic frame commander request, IUT as commander . 30
8.6 Supported frames according to the IUT specification .
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

This May Also Interest You

ISO
ISO 17987-1:2025(Main)
Road vehicles — Local Interconnect Network (LIN) — Part 1: General information and use case definition

This document gives an overview of the structure and the partitioning of the ISO 17987 series. In addition, it outlines the use cases where the ISO 17987 series is used. The terminology defined in this document is common for all LIN communication systems and is used throughout the ISO 17987 series. This document has been established to define the use cases for LIN.

  • Standard
    8 pages
    English language
    sale 15% off
ISO
ISO 13209-4:2024(Main)
Road vehicles — Open Test sequence eXchange format (OTX) — Part 4: Expanded extensions interface definition

This document defines the Open Test sequence eXchange (OTX) additional extension requirements and data model specifications. The requirements are derived from the use cases described in ISO 13209-1. They are listed in Clause 4. The data model specification aims at an exhaustive definition of all features of the OTX extensions which have been implemented to satisfy the requirements. This document establishes rules for the syntactical entities of each extension. Each of these syntactical entities is accompanied by semantic rules which determine how OTX documents containing extension features are interpreted. The syntax rules are provided by UML[2] class diagrams and XML schemas, whereas the semantics are given by UML activity diagrams and prose definitions.

  • Standard
    457 pages
    English language
    sale 15% off
ISO
ISO 11898-1:2024(Main)
Road vehicles — Controller area network (CAN) — Part 1: Data link layer and physical coding sublayer

This document specifies the controller area network (CAN) data link layer (DLL) and the physical coding sub-layer (PCS). The CAN DLL features data fields of up to 2048 byte when the CAN extended data field length (XL) frame format is used. This document divides the CAN DLL into the logical link control (LLC) and the medium access control (MAC) sub-layers. The DLL’s service data unit (SDU), which interfaces the LLC and the MAC, is implemented by means of the LLC frame. The LLC frame also features the service data unit type (SDT) and the virtual CAN channel identifier (VCID), which provide higher-layer protocol configuration and identification information. How the higher-layer functions are handled is not specified in this document. There are five implementation options: 1) support of the CAN classic frame format only, not tolerating the CAN flexible data rate (FD) frame format; 2) support of the CAN classic frame format and tolerating the CAN FD frame format; 3) support of the CAN classic frame format and the CAN FD frame format; 4) support of the CAN classic frame format, the CAN FD frame format and the CAN XL frame format; 5) support of the CAN FD frame format for CAN FD light responders (Annex A). NOTE Nodes of the first option can communicate with nodes of the third and fourth option when only the CAN classic frame format is used. Nodes of the first option cannot communicate with nodes of the fifth option: any attempt at communication generates error frames. Therefore, new designs implementing the fourth option can communicate with all other nodes.

  • Standard
    82 pages
    English language
    sale 15% off
ISO
ISO 15765-2:2024(Main)
Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 2: Transport protocol and network layer services

This document specifies a transport and network layer protocol with transport and network layer services tailored to meet the requirements of CAN-based vehicle network systems on controller area networks as specified in ISO 11898-1. The diagnostic communication over controller area network (DoCAN) protocol supports the standardized abstract service primitive interface as specified in ISO 14229-2 (UDS). This document supports different application layer protocols such as: — enhanced vehicle diagnostics (emissions-related system diagnostics beyond legislated functionality, non-emissions-related system diagnostics); — emissions-related on-board diagnostics (OBD) as specified in the ISO 15031 series and SAE J1979 series; — world-wide harmonized on-board diagnostics (WWH-OBD) as specified in the ISO 27145 series; and — end of life activation of on-board pyrotechnic devices (the ISO 26021 series). The transport protocol specifies an unconfirmed communication. NOTE This document does not determine whether CAN CC, CAN FD or both are recommended or required to be implemented by other standards referencing this document.

  • Standard
    47 pages
    English language
    sale 15% off
ISO
ISO 11898-2:2024(Main)
Road vehicles — Controller area network (CAN) — Part 2: High-speed physical medium attachment (PMA) sublayer

This document specifies physical medium attachment (PMA) sublayers for the controller area network (CAN). This includes the high-speed (HS) PMA without and with low-power mode capability, without and with selective wake-up functionality. Additionally, this document specifies PMAs supporting the signal improvement capability (SIC) mode and the FAST mode in Annex A. The physical medium dependent (PMD) sublayer is not in the scope of this document.

  • Standard
    64 pages
    English language
    sale 15% off
ISO
ISO 15765-5:2023(Main)
Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 5: Specification for an in-vehicle network connected to the diagnostic link connector

This document specifies the OSI layers 4 to 1 (transport layer, network layer, data link layer and physical layer) requirements related to the connection between the external test equipment externally connected to the diagnostic link connector and the in-vehicle CAN network to successfully establish and maintain communication utilizing the communication parameters (communication profile) specified in (application-type) standards referencing this document. The SIC (signal improvement capability) transceiver options, as specified in ISO 11898-2, are out of scope in this document.

  • Standard
    18 pages
    English language
    sale 15% off
ISO
ISO 23150:2023(Main)
Road vehicles — Data communication between sensors and data fusion unit for automated driving functions — Logical interface

This document is applicable to road vehicles with automated driving functions. The document specifies the logical interface between in-vehicle environmental perception sensors (for example, radar, lidar, camera, ultrasonic) and the fusion unit which generates a surround model and interprets the scene around the vehicle based on the sensor data. The interface is described in a modular and semantic representation and provides information on object level (for example, potentially moving objects, road objects, static objects) as well as information on feature and detection levels based on sensor technology specific information. Further supportive information is available. This document does not provide electrical and mechanical interface specifications. Raw data interfaces are also excluded.

  • Standard
    344 pages
    English language
    sale 15% off
ISO
ISO 11992-4:2023(Main)
Road vehicles — Interchange of digital information on electrical connections between towing and towed vehicles — Part 4: Diagnostic communication

This document specifies diagnostic application requirements and OSI-layer related communication profiles to ensure the interchange of digital information between towing and towed vehicles with a maximum authorized total mass greater than 3 500 kg. The conformance and interoperability test plans are not part of this document.

  • Standard
    30 pages
    English language
    sale 15% off
ISO
ISO 11992-2:2023(Main)
Road vehicles — Interchange of digital information on electrical connections between towing and towed vehicles — Part 2: Application layer for brakes and running gear

This document specifies the SAE J1939-based application layer, the payload of messages, and parameter groups for electronically controlled braking systems, including anti-lock braking systems (ABS), vehicle dynamics control systems (VDC), and running gears equipment, to ensure the interchange of digital information between road vehicles with a maximum authorized total mass greater than 3 500 kg and their towed vehicles, including communication between towed vehicles. Conformance and interoperability test plans are not part of this document.

  • Standard
    103 pages
    English language
    sale 15% off
ISO
ISO 13209-2:2022(Main)
Road vehicles — Open Test sequence eXchange format (OTX) — Part 2: Core data model specification and requirements

This document defines the OTX core requirements and data model specifications. The requirements are derived from the use cases described in ISO 13209-1. They are listed in the requirements section. The data model specification aims at an exhaustive definition of all OTX core features implemented to satisfy the core requirements. Since OTX is designed for describing test sequences, which themselves represent a kind of program, the core data model follows the basic concepts common to most programming languages. Thus, this document establishes rules for syntactical entities like parameterised procedures, constant and variable declarations, data types, basic arithmetic, logic and string operations, flow control statements like loop, branch or return, simple statements like assignment or procedure call as well as exception handling mechanisms. Each of these syntactical entities is accompanied by semantic rules which determine how OTX documents are interpreted. The syntax rules are provided by UML class diagrams and XML schemas, whereas the semantics are given by UML activity diagrams and prose definitions. With respect to documentation use cases, special attention is paid to defining a specification/realisation concept (which allows for “hybrid” test sequences: human readable test sequences that are at the same time machine-readable) and so-called floating comments (which can refer to more than one node of the sequence). The core data model does not define any statements, expressions or data types that are dependent on a specific area of application. For the convenience of the user, the ISO 13209-2 OTX XML schema definition file (XSD) is published alongside this document.

  • Standard
    191 pages
    English language
    sale 15% off