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