Already a subscriber? 

MADCAD.com Free Trial
Sign up for a 3 day free trial to explore the MADCAD.com interface, PLUS access the
2009 International Building Code to see how it all works.
If you like to setup a quick demo, let us know at support@madcad.com
or +1 800.798.9296 and we will be happy to schedule a webinar for you.
Security check
Please login to your personal account to use this feature.
Please login to your authorized staff account to use this feature.
Are you sure you want to empty the cart?

BS ISO 17987-6:2025 Road vehicles. Local Interconnect Network (LIN) - Protocol conformance test specification, 2025
- undefined
- Foreword
- Introduction
- 1 Scope
- 2 Normative references
- 3 Terms, definitions, symbols and abbreviated terms [Go to Page]
- 3.1 Terms and definitions
- 3.2 Symbols
- 3.3 Abbreviated terms
- 4 Conventions
- 5 General test specification considerations [Go to Page]
- 5.1 General
- 5.2 Test conditions
- 5.3 Mandatory requirements for IUT as commander
- 5.4 Mandatory requirements for IUT as responder
- 5.5 Test case architecture
- 5.6 Classification
- 5.7 Test system requirements [Go to Page]
- 5.7.1 Generation of LIN frames
- 5.7.2 Common requirements for the test cases
- 5.7.3 Common requirements for bit timing testing
- 5.7.4 Test system for IUT as responder node
- 5.7.5 Sleep state verification for IUT as responder node
- 5.8 Test system definition
- 5.9 Global predefinitions for the test setup [Go to Page]
- 5.9.1 Configuration of IUT and test system
- 5.9.2 Default delays for frame headers
- 5.9.3 Default bit rate
- 5.9.4 Time measurement
- 5.9.5 Default spaces between the different frame parts of a LIN message
- 6 Essential test cases before test start [Go to Page]
- 6.1 General
- 6.2 [PT-CT 1] Diagnostic frame “commander request”, IUT as responder
- 6.3 [PT-CT 2] Diagnostic frame “responder response”, IUT as responder
- 6.4 [PT-CT 3] Error in received frame, IUT as responder
- 7 Timing parameters [Go to Page]
- 7.1 General
- 7.2 [PT-CT 4] Length of break field low phase, IUT as commander
- 7.3 [PT-CT 5] Variation of length of break field low phase, IUT as responder
- 7.4 [PT-CT 6] Length of break delimiter, IUT as commander
- 7.5 [PT-CT 7] Variation of length of break delimiter, IUT as responder
- 7.6 [PT-CT 8] Inconsistent break field error, IUT as responder
- 7.7 [PT-CT 9] Inconsistent sync byte field error, IUT as responder
- 7.8 [PT-CT 10] Bit rate detection, IUT as responder with making use of detection
- 7.9 [PT-CT 10] Verification of the sync byte field, IUT as commander
- 7.10 [PT-CT 11] Incomplete frame reception, IUT as responder
- 7.11 [PT-CT 12] Unknown frame reception, IUT as responder
- 7.12 [PT-CT 13] Length of header, IUT as commander
- 7.13 [PT-CT 14] Variation of length of header, IUT as responder
- 7.14 [PT-CT 15] Bit rate tolerance, IUT as commander
- 7.15 [PT-CT 16] Bit rate tolerance, IUT as responder without making use of synchronization
- 7.16 [PT-CT 17] Bit rate tolerance, IUT as responder with making use of synchronization
- 7.17 Length of response [Go to Page]
- 7.17.1 [PT-CT 18] Length of response, IUT as responder
- 7.17.2 [PT-CT 19] Length of response, IUT as commander
- 7.17.3 [PT-CT 20] Acceptance of response field, IUT as responder
- 7.18 Verification of schedule table timing [Go to Page]
- 7.18.1 [PT-CT 21] Verification of jitter, IUT as commander
- 7.18.2 [PT-CT 22] Schedule table management, IUT as commander
- 7.19 [PT-CT 23] Sample point test, IUT as responder
- 7.20 [PT-CT 24] Initialization time, IUT as responder
- 8 Communication without failure [Go to Page]
- 8.1 Variation of LIN identifier [Go to Page]
- 8.1.1 [PT-CT 25] Variation of LIN PID, IUT as commander
- 8.1.2 [PT-CT 26] Variation of LIN PIDs of subscribed frames, IUT as responder
- 8.1.3 [PT-CT 27] Variation of LIN identifier of published frames, IUT as responder
- 8.2 Transmission of the checksum byte [Go to Page]
- 8.2.1 [PT-CT 28] Transmission of the checksum byte “classic checksum”, IUT as responder
- 8.2.2 [PT-CT 29] Transmission of the checksum byte “enhanced checksum”, IUT as responder
- 8.2.3 [PT-CT 30] Transmission of the checksum byte “classic checksum”, IUT as commander
- 8.2.4 [PT-CT 31] Transmission of the checksum byte of unconditional frames, IUT as commander
- 8.3 Unused bits [Go to Page]
- 8.3.1 [PT-CT 32] Unused bits, IUT as commander
- 8.3.2 [PT-CT 33] Unused bits, IUT as responder
- 8.4 Reserved frame [Go to Page]
- 8.4.1 [PT-CT 34] Reserved frame, IUT as responder
- 8.5 [PT-CT 35] Diagnostic frame commander request, IUT as commander
- 8.6 Supported frames according to the IUT specification [Go to Page]
- 8.6.1 [PT-CT 36] Supported Tx frames according to the IUT specification, IUT as responder
- 8.6.2 [PT-CT 37] Supported Rx frames according to the IUT specification, IUT as responder
- 9 Communication with failure [Go to Page]
- 9.1 General
- 9.2 [PT-CT 38] Bit error, IUT as responder
- 9.3 [PT-CT 39] Framing error in header of published frame, IUT as responder
- 9.4 [PT-CT 40] Framing error in response field of subscribed frame, IUT as responder
- 9.5 [PT-CT 41] Checksum error by inversion, IUT as responder
- 9.6 [PT-CT 42] Checksum error by carry, IUT as responder
- 9.7 [PT-CT 43] Communication robustness, IUT as responder
- 10 Event triggered frames [Go to Page]
- 10.1 General
- 10.2 [PT-CT 44] Event triggered frame, IUT as responder
- 10.3 Event triggered frame with collision [Go to Page]
- 10.3.1 [PT-CT 45] Event triggered frame with collision resolving, IUT as responder
- 10.3.2 [PT-CT 46] Event triggered frame with errors in collision resolving, IUT as responder
- 10.3.3 [PT-CT 47] Event triggered frame with collision resolving, IUT as commander
- 10.3.4 [PT-CT 48] Error in transmitted frame with collision, IUT as responder
- 11 Status management [Go to Page]
- 11.1 [PT-CT 49] Error in received frame, IUT as responder
- 11.2 [PT-CT 50] Error in transmitted frame, IUT as responder
- 11.3 [PT-CT 51] response_error signal handling, IUT as responder
- 12 Sleep/wake-up/power mode tests [Go to Page]
- 12.1 [PT-CT 52] Send “go-to-sleep command”, IUT as commander
- 12.2 [PT-CT 53] Receive “go-to-sleep command”, IUT as responder
- 12.3 [PT-CT 54] Receive a wake-up signal, IUT as commander
- 12.4 [PT-CT 55] Receive a wake-up signal, IUT as responder
- 12.5 Send a wake-up signal [Go to Page]
- 12.5.1 [PT-CT 56] Send a wake-up signal, IUT as commander and IUT as responder
- 12.5.2 [PT-CT 57] Send a block of wake-up signals, IUT as responder
- 12.5.3 [PT-CT 58] Wait after one block of wake-up signals, IUT as responder
- 12.5.4 [PT-CT 59] Trigger wake-up signal followed by a frame header from commander, IUT as responder
- 12.6 [PT-CT 60] ECU power loss, IUT as commander
- 12.7 [PT-CT 61] Powered up with LIN shorted, IUT as commander
- 12.8 [PT-CT 62] LIN shorted before scheduling, IUT as commander
- 12.9 [PT-CT 63] LIN shorted after start of scheduling, IUT as commander
- 13 Sleep state after bus idle [Go to Page]
- 13.1 [PT-CT 64] Sleep state after event and bus idle, IUT as responder
- 13.2 [PT-CT 65] Sleep state after bus idle with power up and wake-up signal, IUT as responder
- 13.3 [PT-CT 66] Timeout after bus idle, IUT as responder
- 14 Frame ID range assignment [Go to Page]
- 14.1 [PT-CT 67] Frame ID range assignment with indirect response, IUT as responder
- 14.2 [PT-CT 68] Frame ID range unassignment with indirect response, IUT as responder
- 15 Wildcards [Go to Page]
- 15.1 [PT-CT 69] Request with direct response, IUT as responder
- 16 ReadByIdentifier command [Go to Page]
- 16.1 LIN product identification [Go to Page]
- 16.1.1 [PT-CT 70] LIN product identification request with direct response, IUT as responder
- 16.1.2 [PT-CT 71] LIN product identification — With interleaved unconditional frame, IUT as responder
- 16.2 [PT-CT 72] ReadByIdentifier command with correct NAD, IUT as responder
- 16.3 [PT-CT 73] ReadByIdentifier command with incorrect addressing, IUT as responder
- 17 NAD assignment [Go to Page]
- 17.1 General
- 17.2 [PT-CT 74] NAD assignment — Followed by ReadByIdentifier service, IUT as responder
- 17.3 [PT-CT 75] NAD assignment — With positive response, IUT as responder
- 17.4 [PT-CT 76] NAD assignment — Initial NAD, IUT as responder
- 18 Save Configuration [Go to Page]
- 18.1 General
- 18.2 [PT-CT 77] Save configuration — With positive response, IUT as responder
- 18.3 [PT-CT 78] Save configuration — Save a new NAD, IUT as responder
- 18.4 [PT-CT 79] Save configuration — Save new frame identifiers, IUT as responder
- 19 Transport protocol [Go to Page]
- 19.1 [PT-CT 80] Transport layer functional request, IUT as responder
- 19.2 [PT-CT 81] Abort diagnostic communication with new diagnostic request, IUT as responder
- 19.3 [PT-CT 82] IUT receives a segmented request as specified, IUT as responder
- 19.4 [PT-CT 83] IUT receives a segmented request interleaved with unconditional frame, IUT as responder
- 19.5 [PT-CT 84] IUT receives a segmented request with interleaved functional request, IUT as responder
- 19.6 IUT shall ignore request after timeout [Go to Page]
- 19.6.1 [PT-CT 85] IUT shall ignore segmented requests on N_Crmax timeout, IUT as responder
- 19.6.2 [PT-CT 86] IUT shall observe transport layer N_Asmax timeout, IUT as responder
- 19.7 [PT-CT 87] IUT shall ignore segmented requests with wrong sequence numbering, IUT as responder
- 19.8 [PT-CT 88] IUT shall respond with correct segmented response, IUT as responder
- 19.9 IUT sends a segmented response with interleaved unconditional frames [Go to Page]
- 19.9.1 [PT-CT 89] IUT sends a segmented response with interleaved unconditional frame, IUT as responder
- 19.9.2 [PT-CT 90] IUT sends a segmented response with interleaved functional request, IUT as responder
- 19.10 [PT-CT 91] IUT shall not respond to responder response header if there is no request before, IUT as responder
- 19.11 [PT-CT 92] IUT shall not respond to responder response header if the response is already sent, IUT as responder
- 19.12 [PT-CT 93] IUT shall abort segmented response on N_Csmax timeout, IUT as responder
- Annex A (normative) LIN AA procedure C protocol conformance test plan
- Annex B (normative) LIN AA procedure D protocol conformance test plan
- Annex C (normative) LIN AA procedure E protocol conformance test plan
- Bibliography [Go to Page]