LIN Network for Vehicle Applications
- Ground Vehicle Standard
- J2602-1_202110
- Revised
Scope
Rationale
Recommended Content
Ground Vehicle Standard | LIN Network for Vehicle Applications Conformance Test |
Ground Vehicle Standard | File Structures for a Node Capability File (NCF) and LIN Description File (LDF) |
Ground Vehicle Standard | High-Speed CAN (HSC) for Vehicle Applications at 500 kbps |
Topic
Data Sets - Support Documents
Title | Description | Download |
---|---|---|
Unnamed Dataset 1 | ||
Unnamed Dataset 2 | ||
Unnamed Dataset 3 | ||
Table 1 | Common signal encoding type mapping to LIN defined data entities | |
Unnamed Dataset 5 | SAE J2602-1 Status Byte | |
Table 2 | NAD to message ID mapping | |
Unnamed Dataset 7 | ||
Unnamed Dataset 8 | ||
Unnamed Dataset 9 | ||
Unnamed Dataset 10 | ||
Unnamed Dataset 11 | ||
Unnamed Dataset 12 | ||
Table 3 | Wake-up signal timing | |
Table 4 | Commander-responder-node communication clock tolerance | |
Table 5 | LIN bus signals and loading requirements | |
Table 6 | LIN bus loading requirements for normal battery supply operating range | |
Table 7 | LIN bus loading requirements for low battery supply operating range | |
Table 8 | #Nodes/network resistance/commander-node capacitance versus max wire length | |
Unnamed Dataset 19 | ||
Table C1 | Transmitter propagation delay timings | |
Table D1 | Multiplexed calibrate/configindex/calibrate/configdata mapping to unique internal LIN responder-node calibrate/config data | |
Table D2 | Calibrate/configuring LIN responder-nodes - responder-node requirements | |
Table D3 | Multiplexed partnumindex/parnumdata mapping to LIN commander-node partnumber data | |
Table D5 | LIN responder-node part number reporting - responder-node requirements | |
Unnamed Dataset 25 | ||
Unnamed Dataset 26 |
Issuing Committee
Vehicle Architecture For Data Communications Standards
The ever-increasing consumer expectations of vehicle internal functions and connectivity to the environment are outstripping the capability of current data communication architecture design. To address this vulnerability, this committee will investigate and endorse new vehicle architectures that meet system requirements such as: Reliability, System design metrics, Data security, Fault Tolerance, Built in testability, Validation/Verification , Compatibility, and Redundancy. This committee's mission is the investigation and development of vehicle architecture and data communication protocols and methods required to achieve the growth expected in the area of vehicle electronics. The committee shall continue to contribute to the understanding and use of semiconductor devices such as microprocessors, power devices, and other integrated circuits and the data transmission media used in these systems. Thus, all vehicle architectures (excluding aircraft) and devices used in these systems shall be included. Specific objectives shall include: Address the effect of electrical power environments (e.g., 42V, ground offsets) , Sponsor forums to evaluate new technologies (e.g., MOST, Bluetooth, Firewire), Publish technical reports on vehicle architecture and system partitioning, interfacing, modes of operation, protocol standards, recommended conformance test methods, and evaluation methods of those standards , Maintain the existing documents relevant to this committee (e.g., glossary of automotive electronics terms, SAE J1213/1), Encourage the applicable industries, government and educational institutions to support the efforts of this committee.