Road vehicles - Local Interconnect Network (LIN) - Part 1: General information and use case definition
1 Scope
This document gives an overview of the structure and the partitioning of GB/T 42691. In addition, it outlines the use case where the GB/T 42691 will be used.
The terminology defined in this document is common for all LIN communication systems and is used throughout GB/T 42691.
This document has been established in order to define the use cases for LIN.
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.
ISO 17987-4 Road vehicles - Local Interconnect Network (LIN) - Part 4: Electrical Physical Layer (EPL) specification 12 V/24 V
Note: 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 and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1.1
break field
entity that consists of a dominant part, the break and a recessive part, the break delimiter
3.1.2
byte field
10 bit entity, which consists of a dominant start bit, 8 bit payload (least significant bit first) and a recessive stop bit
3.1.3
checksum
frame verification byte
3.1.4
frame
entity that consists of the header and the PDU including payload and a checksum (3.1.3) byte at the end
3.1.5
LIN master
unique node in a LIN network that schedules the frames (3.1.4) and connected to a back bone network
3.1.6
LIN slave
node that serves the communication requests of a LIN master (3.1.5)
3.1.7
master task
task in the LIN master (3.1.5) sending all headers on the bus according to schedule table (3.1.10)
3.1.8
node address for diagnostics; NAD
diagnostic address assigned to each LIN slave (3.1.6) node
3.1.9
protected identifier
8 bit entity containing the 6 bit frame identifier (least significant bits) together with two parity bits
3.1.10
schedule table
list of frames (3.1.4) specifies the frames, their order and time distances to each other used for communication on the LIN bus
3.1.11
slave task
task in a LIN node responsible for listening to all headers on the bus and reacting accordingly, i.e. either publish a frame response or subscribe to it (or ignore it)
3.1.12
sync byte field
byte with fixed value located between the break field (3.1.1) and the protected identifier (3.1.9)
3.2 Abbreviated terms
API: application programmers interface
LDF: LIN description file
NAD: node address for diagnostics
OEM: original equipment manufacturer
OSI: open systems interconnection
PDU: protocol data unit
PID: protected identifier
SAP: service access point
UC: use case
UDS: unified diagnostic services
4 Conventions
ISO 17987 (all parts) is based on the conventions specified in the OSI Service Conventions (see ISO/IEC 10731) as they apply for physical layer, data link layer, network and transport protocol and diagnostic services.
Standard
GB/T 42691.1-2023 Road vehicles—Local Interconnect Network(LIN)—Part 1:General information and use case definition (English Version)
Standard No.
GB/T 42691.1-2023
Status
valid
Language
English
File Format
PDF
Word Count
8500 words
Price(USD)
240.0
Implemented on
2023-12-1
Delivery
via email in 1~3 business day
Detail of GB/T 42691.1-2023
Standard No.
GB/T 42691.1-2023
English Name
Road vehicles—Local Interconnect Network(LIN)—Part 1:General information and use case definition
Road vehicles - Local Interconnect Network (LIN) - Part 1: General information and use case definition
1 Scope
This document gives an overview of the structure and the partitioning of GB/T 42691. In addition, it outlines the use case where the GB/T 42691 will be used.
The terminology defined in this document is common for all LIN communication systems and is used throughout GB/T 42691.
This document has been established in order to define the use cases for LIN.
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.
ISO 17987-4 Road vehicles - Local Interconnect Network (LIN) - Part 4: Electrical Physical Layer (EPL) specification 12 V/24 V
Note: 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 and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1.1
break field
entity that consists of a dominant part, the break and a recessive part, the break delimiter
3.1.2
byte field
10 bit entity, which consists of a dominant start bit, 8 bit payload (least significant bit first) and a recessive stop bit
3.1.3
checksum
frame verification byte
3.1.4
frame
entity that consists of the header and the PDU including payload and a checksum (3.1.3) byte at the end
3.1.5
LIN master
unique node in a LIN network that schedules the frames (3.1.4) and connected to a back bone network
3.1.6
LIN slave
node that serves the communication requests of a LIN master (3.1.5)
3.1.7
master task
task in the LIN master (3.1.5) sending all headers on the bus according to schedule table (3.1.10)
3.1.8
node address for diagnostics; NAD
diagnostic address assigned to each LIN slave (3.1.6) node
3.1.9
protected identifier
8 bit entity containing the 6 bit frame identifier (least significant bits) together with two parity bits
3.1.10
schedule table
list of frames (3.1.4) specifies the frames, their order and time distances to each other used for communication on the LIN bus
3.1.11
slave task
task in a LIN node responsible for listening to all headers on the bus and reacting accordingly, i.e. either publish a frame response or subscribe to it (or ignore it)
3.1.12
sync byte field
byte with fixed value located between the break field (3.1.1) and the protected identifier (3.1.9)
3.2 Abbreviated terms
API: application programmers interface
LDF: LIN description file
NAD: node address for diagnostics
OEM: original equipment manufacturer
OSI: open systems interconnection
PDU: protocol data unit
PID: protected identifier
SAP: service access point
UC: use case
UDS: unified diagnostic services
4 Conventions
ISO 17987 (all parts) is based on the conventions specified in the OSI Service Conventions (see ISO/IEC 10731) as they apply for physical layer, data link layer, network and transport protocol and diagnostic services.