LIN Network for Vehicle ApplicationsIssued 2004-08Revised 2005-09Superseding J2602-1 AUG2004
Foreword
The objective of this document is to define a level of standardization in the implementation of low speed vehicle serial data network communications using the Local Interconnect Network (LIN) protocol. The goal of this document is to define a serial data physical layer, data link layer and media design criteria to be installed in various automotive Electronic Control Units (ECU). This standard will allow ECU and tool manufacturers to satisfy the needs of multiple end users with minimum modifications to the basic design. This standard will benefit vehicle Original Equipment Manufacturers (OEMs) by achieving lower ECU costs due to higher industry volumes of the basic design.
NOTE—Understanding of this document requires a working knowledge of the LIN 2.0 Specification
Package. 1.
Scope of Document
This document covers the requirements for SAE implementations based on LIN 2.0. Requirements stated in this document will provide a minimum standard level of performance to which all compatible ECUs and media shall be designed. This will assure full serial data communication among all connected devices regardless of supplier.
The goal of SAE J2602 is to improve the interoperability and interchangeability of LIN devices within a network by resolving those LIN 2.0 requirements that are ambiguous, conflicting, or optional. Moreover, SAE J2602 provides additional requirements that are not present in LIN 2.0 (e.g., fault tolerant operation, network topology, etc.).
This document is to be referenced by the particular vehicle OEM component technical specification that describes any given ECU in which the single wire data link controller and physical layer interface is located. Primarily, the performance of the physical layer is specified in this document. ECU environmental and other requirements, when provided in the component technical specification, shall supercede the requirements of this document.
The intended audience includes, but is not limited to, ECU suppliers, LIN controller suppliers, LIN transceiver suppliers, component release engineers and vehicle system engineers. 1.1
Rationale
During the development of the Conformance test (J2602-2) for J2602 some issues were found which we have decided to correct. These include the following:
1. Section 3.1 – Added definitions for Command Frame and Request Frame.
2. Section 5.3 – It was decided that the Master device should detect errors and stop transmitting when
an error is detected during the message header. This will simplify the Master software and will make the behavior of the bus more predictable.
3. Section 5.4.1 – The names of the errors in this section did not match the names of the errors in
Sections 5.8.5.1.3-6 where they are described. They will now match.
4. Section 5.4.3 – The spec now explicitly states that if the sync byte data received by the slave is not
correct the slave shall set an error code and ignore the rest of the message.
5. Section 5.5 - TFrame_Maximum was used twice for the range, the first time it should have been TFrame_Minimum.