GB/T 42691.3-2023 PDF English
Search result: GB/T 42691.3-2023 English: PDF (GB/T42691.3-2023)
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Name of Chinese Standard | Status |
| GB/T 42691.3-2023 | English | 650 |
Add to Cart
|
0-9 seconds. Auto-delivery.
|
Road vehicles -- Local Interconnect Network(LIN) -- Part 3: Protocol specification
| Valid |
BUY with any currencies (Euro, JPY, GBP, KRW etc.): GB/T 42691.3-2023 Related standards: GB/T 42691.3-2023
PDF Preview: GB/T 42691.3-2023
GB/T 42691.3-2023: PDF in English (GBT 42691.3-2023) GB/T 42691.3-2023
GB
NATIONAL STANDARD OF THE
PEOPLE’S REPUBLIC OF CHINA
ICS 43.020
CCS T 36
GB/T 42691.3-2023 / ISO 17987-3:2016
Road Vehicles – Local Interconnect Network (LIN) – Part 3:
Protocol Specification
(ISO 17987-3:2016, IDT)
ISSUED ON: MAY 23, 2023
IMPLEMENTED ON: DECEMBER 01, 2023
Issued by: State Administration for Market Regulation;
Standardization Administration of the People’s Republic of China.
Table of Contents
Foreword ... 4
Introduction ... 6
1 Scope ... 8
2 Normative References ... 8
3 Terms, Definitions, Symbols and Abbreviated Terms ... 8
3.1 Terms and definitions ... 8
3.2 Symbols ... 12
3.3 Abbreviated terms ... 12
4 Node Concept... 13
4.1 General ... 13
4.2 Concept of operation... 14
5 Protocol Requirements ... 15
5.1 Signal ... 15
5.2 Frame ... 18
5.3 Schedule tables ... 30
5.4 Task behavior model ... 31
5.5 Status management ... 34
6 Node Configuration and Identification ... 36
6.1 General ... 36
6.2 LIN product identification ... 36
6.3 Slave node model ... 37
Annex A (Normative) Definition of Properties, Frame Identifiers and Various Examples
... 47
A.1 Definition of numerical properties ... 47
A.2 Definition of valid frame identifiers ... 47
A.3 Example of checksum calculation ... 49
A.4 Example of sequence diagrams ... 49
Annex B (Informative) LIN History and Version Compatibility ... 51
B.1 LIN history and background ... 51
B.2 LIN version compatibility ... 51
B.3 Changes between LIN versions ... 52
Annex C (Informative) LIN Auto Addressing Methods ... 55
C.1 Auto addressing method and method IDs ... 55
C.2 Auto addressing method ID ... 55
Bibliography ... 56
Foreword
This Document was drafted as per the rules specified in GB/T 1.1-2020 Directives for
Standardization – Part 1: Rules for the Structure and Drafting of Standardizing Documents.
This Document was Part 3 of GB/T 42691 Road Vehicles – Local Interconnect Network (LIN).
GB/T 42691 has already published the following parts:
--- Part 1: General Information and Use Case Definition;
--- Part 2: Transport Protocol and Network Layer Services;
--- Part 3: Protocol Specification;
--- Part 4: Electrical Physical Layer (EPL) Specification 12V/24V;
--- Part 5: Application Programmers Interface (API);
--- Part 6: Protocol Conformance Test Specification;
--- Part 7: Electrical Physical Layer (EPL) Conformance Test Specification;
--- Part 8: Electrical Physical Layer (EPL) Specification: LIN over DC Powerline (DC-LIN).
This Document equivalently adopts ISO 17987-3:2016 Road Vehicles – Local Interconnect
Network (LIN) – Part 3: Protocol Specification.
Please note some contents of this Document may involve patents. The issuing agency of this
Document shall not assume the responsibility to identify these patents.
This Document was proposed by the Ministry of Industry and Information Technology of the
People’s Republic of China.
This Document shall be under the jurisdiction of National Technical Committee of Auto
Standardization (SAC/TC 114).
Drafting organizations of this Document: Pan-Asia Technical Automotive Center Co., Ltd.;
China Automotive Technology and Research Center Co., Ltd.; Geely Automobile Research
Institute (Ningbo) Co., Ltd.; Dongfeng Motor Group Co., Ltd.; SAIC Maxus Automotive Co.,
Ltd.; Great Wall Motor Company Limited; SAIC-GM-Wuling Automobile Co., Ltd.; China
FAW Group Corporation; National New Energy Vehicle Technology Innovation Center Co.,
Ltd.; Huizhou Desay SV Automotive Co., Ltd.; FAW-Volkswagen Automotive Co., Ltd.; and
China Automotive Research Institute (Tianjin) Automotive Engineering Research Institute Co.,
Ltd.
Chief drafting staffs of this Document: Wu Shang, Ji Guotian, Ding Juan, Zhu Tong, Zhen
Road Vehicles – Local Interconnect Network (LIN) – Part 3:
Protocol Specification
1 Scope
This Document specifies the LIN protocol including the signal management, frame transfer,
schedule table handling, task behavior and status management and LIN master and slave node.
It also contains OSI layer 5 properties according to ISO 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 provisions in following documents become the essential provisions of this Document
through reference in this Document. For the dated documents, only the versions with the dates
indicated are applicable to this Document; for the undated documents, only the latest version
(including all the amendments) is applicable to this Document.
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 12V/24V (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 following terms and definitions apply.
3.1.1 Big-endian
Method of storage of multi-byte numbers with the most significant bytes at the lowest memory
Each signal shall have one publisher, i.e., it shall be always sent by the same node in the cluster.
Zero, one or multiple nodes may subscribe to the signal.
All signals shall have initial values. The initial value for a published signal should be valid until
the node writes a new value to this signal. The initial value for a subscribed signal should be
valid until a new updated value is received from another node.
5.1.3 Consistency
Scalar signal writing or reading shall be atomic operations, i.e. it shall not be possible for an
application to receive a signal value that is partly updated. This shall also apply to byte arrays.
However, no consistency is guaranteed between any signals.
5.1.4 Packing
There is no restriction on packing scalar signals over byte boundaries. Each byte in a byte array
shall map to a single frame byte starting with the lowest numbered data byte, see 5.2.2.6.
Several signals may be packed into one frame as long as they do not overlap each other.
NOTE: Signal packing/unpacking is implemented more efficient in software-based nodes if signals are
byte aligned and/or if they do not cross byte boundaries.
The same signal may be packed into multiple frames as long as the publisher of the signal is
the same. If a node is receiving one signal packed into multiple frames, the latest received signal
value is valid. Handling the same signal packed into frames on different LIN clusters is out of
the scope.
5.1.5 Reception and transmission
The point in time when a signal is transmitted/received needs to be defined to help design tools
and testing tools to analyze timing of signals. This means that all implementations behave in a
predictable way.
The definitions below do not contain factors such as bit rate tolerance, jitter, buffer copy
execution time, etc. These factors need be taken into account to get a more detailed analysis.
The intention for the definitions below is to have a basis for such analysis.
The timing is different for a master node and a slave node. The reason is that the master node
controls the schedule and is aware of the due frame. A slave node gets this information first
when the header is received.
The time base and time base tick is defined in 5.3.
A signal is considered received and available to the application as shown in Figure 4.
— Master node, at the next time base tick after the maximum frame length. The master node
......
Source: Above contents are excerpted from the PDF -- translated/reviewed by: www.chinesestandard.net / Wayne Zheng et al.
|