Road vehicles - Local Interconnect Network (LIN) - Part 3: Protocol specification
1 Scope
This document specifies the LlN protocol including the signal management, frame transfer, schedule table handling, task behaviour and status management and LlN master and slave node. It contains also OSl layer 5 properties according to IS0 14229-7 UDSonLIN-based node configuration and identification services (SID: B016 to B816) belonging to the core protocol specification.
A node (normally a master node) that is connected to more than one LIN network is handled by higher layers (i.e. the application) not within the scope 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 edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
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.4-2023 Road vehicles - Local Interconnect Network (LIN) - Part 4: Electrical physical layer (EPL) specification 12 V/24 V (ISO 17987-4:2016, IDT)
GB/T 42691.6-2023 Road vehicles - Local Interconnect Network (LIN) - Part 6: Protocol conformance test specification (ISO 17987-6:2016, IDT)
3 Terms, definitions, symbols and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 17987-1 and the following apply.
3.1.1
big-endian
method of storage of multi-byte numbers with the most significant bytes at the lowest memory addresses
3.1.2
broadcast NAD
addressing every slave node on LIN
3.1.3
bus interface
hardware (transceiver, UART, etc.) of a node that is connected to the physical bus wire in a cluster (3.1.6)
3.1.4
bus sleep state
state in which a node only expects an internal or external wake up
Note: The nodes switch output level to the recessive state.
[SOURCE: GB/T 42691.2-2023, 5.2]
3.1.5
classic checksum
used for diagnostic frames (3.1.10) and legacy LlN slave nodes frames of protocol version 1.x
Note: The classic checksum considers the frame response data bytes only.
3.1.6
cluster
communication system comprising the LIN wire and all connected nodes
3.1.7
cluster design
process of designing the LDF
[SOURCE: GB/T 42691.2-2023, 11.2.3]
3.1.8
data
response (3.1.27) part of a frame carrying one to eight data bytes (3.1.9)
3.1.9
data byte
one of the bytes in the data
3.1.10
diagnostic frame
master request frame (3.1.21) and the slave response frame (3.1.29)
3.1.11
diagnostic trouble code; DTC
value making reference to a specific fault in a system implemented in the server
3.1.12
enhanced checksum
checksum model used for all non-diagnostic frames and legacy 1.x LIN slave nodes
3.1.13
event-triggered frame
allowing multiple slave nodes to provide their response (3.1.27) to the same header
3.1.14
frame
communication entity consisting of a header and response (3.1.27)
3.1.15
frame identifier
value identifier uniquely a frame
3.1.16
frame slot
time period reserved for the transfer of a specific frame on LIN
Note: This corresponds to one entry in the schedule table.
3.1.17
go-to-sleep command
special master request frame (3.1.21) issued to force slave nodes to bus sleep state (3.1.4)
[SOURCE: GB/T 42691.2-2023, 5.4]
3.1.18
header
first part of a frame consists of a break field, sync byte field and protected identifier; it is always sent by the LIN master node
3.1.19
LIN product identification
number containing the supplier and function and variant identification in a LlN slave node
3.1.20
little-endian
method of storage of multi-byte numbers with the least significant bytes at the lowest memory addresses
3.1.21
master request frame
diagnostic frames (3.1.10) issued by the master node frame identifier (3.1.15)
3.1.22
node capability file; NCF
file format describes a slave node as seen from the LIN network
3.1.23
operational state
slave node may transmit/receive frames in this state
[SOURCE: GB/T 42691.2-2023, 5.2]
3.1.24
protected identifier; PID
8-bit value consisting of a unique 6-bit frame identifier (3.1.15) and 2-bit parity
3.1.25
publisher
node providing a frame response containing signals (3.1.30)
3.1.26
request
diagnostic frame (3.1.10) transmitted by the master node requesting data from a slave nodes
3.1.27
response
answer sent by a slave node on a diagnostic request (3.1.26)
3.1.28
service
combination of a diagnostic request (3.1.26) and response (3.1.27)
3.1.29
slave response frame
frame used for diagnostic communication sent by one of the slave nodes
3.1.30
signal
value or byte array transmitted in the cluster (3.1.6) using a signal carrying frame (3.1.31)
3.1.31
signal carrying frame
unconditional frames (3.1.34), sporadic frames (3.1.32), and event-triggered frames (3.1.13) containing signals (3.1.30)
Road vehicles - Local Interconnect Network (LIN) - Part 3: Protocol specification
1 Scope
This document specifies the LlN protocol including the signal management, frame transfer, schedule table handling, task behaviour and status management and LlN master and slave node. It contains also OSl layer 5 properties according to IS0 14229-7 UDSonLIN-based node configuration and identification services (SID: B016 to B816) belonging to the core protocol specification.
A node (normally a master node) that is connected to more than one LIN network is handled by higher layers (i.e. the application) not within the scope 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 edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
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.4-2023 Road vehicles - Local Interconnect Network (LIN) - Part 4: Electrical physical layer (EPL) specification 12 V/24 V (ISO 17987-4:2016, IDT)
GB/T 42691.6-2023 Road vehicles - Local Interconnect Network (LIN) - Part 6: Protocol conformance test specification (ISO 17987-6:2016, IDT)
3 Terms, definitions, symbols and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 17987-1 and the following apply.
3.1.1
big-endian
method of storage of multi-byte numbers with the most significant bytes at the lowest memory addresses
3.1.2
broadcast NAD
addressing every slave node on LIN
3.1.3
bus interface
hardware (transceiver, UART, etc.) of a node that is connected to the physical bus wire in a cluster (3.1.6)
3.1.4
bus sleep state
state in which a node only expects an internal or external wake up
Note: The nodes switch output level to the recessive state.
[SOURCE: GB/T 42691.2-2023, 5.2]
3.1.5
classic checksum
used for diagnostic frames (3.1.10) and legacy LlN slave nodes frames of protocol version 1.x
Note: The classic checksum considers the frame response data bytes only.
3.1.6
cluster
communication system comprising the LIN wire and all connected nodes
3.1.7
cluster design
process of designing the LDF
[SOURCE: GB/T 42691.2-2023, 11.2.3]
3.1.8
data
response (3.1.27) part of a frame carrying one to eight data bytes (3.1.9)
3.1.9
data byte
one of the bytes in the data
3.1.10
diagnostic frame
master request frame (3.1.21) and the slave response frame (3.1.29)
3.1.11
diagnostic trouble code; DTC
value making reference to a specific fault in a system implemented in the server
3.1.12
enhanced checksum
checksum model used for all non-diagnostic frames and legacy 1.x LIN slave nodes
3.1.13
event-triggered frame
allowing multiple slave nodes to provide their response (3.1.27) to the same header
3.1.14
frame
communication entity consisting of a header and response (3.1.27)
3.1.15
frame identifier
value identifier uniquely a frame
3.1.16
frame slot
time period reserved for the transfer of a specific frame on LIN
Note: This corresponds to one entry in the schedule table.
3.1.17
go-to-sleep command
special master request frame (3.1.21) issued to force slave nodes to bus sleep state (3.1.4)
[SOURCE: GB/T 42691.2-2023, 5.4]
3.1.18
header
first part of a frame consists of a break field, sync byte field and protected identifier; it is always sent by the LIN master node
3.1.19
LIN product identification
number containing the supplier and function and variant identification in a LlN slave node
3.1.20
little-endian
method of storage of multi-byte numbers with the least significant bytes at the lowest memory addresses
3.1.21
master request frame
diagnostic frames (3.1.10) issued by the master node frame identifier (3.1.15)
3.1.22
node capability file; NCF
file format describes a slave node as seen from the LIN network
3.1.23
operational state
slave node may transmit/receive frames in this state
[SOURCE: GB/T 42691.2-2023, 5.2]
3.1.24
protected identifier; PID
8-bit value consisting of a unique 6-bit frame identifier (3.1.15) and 2-bit parity
3.1.25
publisher
node providing a frame response containing signals (3.1.30)
3.1.26
request
diagnostic frame (3.1.10) transmitted by the master node requesting data from a slave nodes
3.1.27
response
answer sent by a slave node on a diagnostic request (3.1.26)
3.1.28
service
combination of a diagnostic request (3.1.26) and response (3.1.27)
3.1.29
slave response frame
frame used for diagnostic communication sent by one of the slave nodes
3.1.30
signal
value or byte array transmitted in the cluster (3.1.6) using a signal carrying frame (3.1.31)
3.1.31
signal carrying frame
unconditional frames (3.1.34), sporadic frames (3.1.32), and event-triggered frames (3.1.13) containing signals (3.1.30)
