Search Results

This document covers the general terms and corresponding definitions that support the design, development, implementation, testing, and application of vehicle networks. The terminology also covers some terms and concepts of distributed embedded systems, network hardware, network software, physical layers, protocols, and other related areas.

This SAE Information Report provides definition for terms (words and phrases) which are generally used within the SAE in describing network and data communication issues. In many cases, these definitions are different from those of the same or similar terms found in nonautomotive organizations, such as the Institute of Electrical and Electronic Engineers (IEEE). The Vehicle Networks for Multiplexing and Data Communications committee has found it useful to collect these specific terms and definitions into this document so documents related to the multiplexing and data communications issues will not need an extensive definitions section. This document is intended to be the central reference for terms and definitions related to multiplexing and data communications and as such is intended to apply equally to Passenger Car, Truck and Bus, and Construction and Agriculture organizations within SAE.

This Glossary confines its content to the specific field of electronic systems and subsystems as they pertain to the automotive engineer.

This SAE Recommended Practice defines the information contained in the header and data fields of non-diagnostic messages for automotive serial communications based on SAE J1850 Class B networks. This document describes and specifies the header fields, data fields, field sizes, scaling, representations, and data positions used within messages. The general structure of a SAE J1850 message frame without in-frame response is shown in Figure 1. The structure of a SAE J1850 message with in-frame response is shown in Figure 2. Figures 1 and 2 also show the scope of frame fields defined by this document for non-diagnostic messages. Refer to SAE J1979 for specifications of emissions related diagnostic message header and data fields. Refer to SAE J2190 for the definition of other diagnostic data fields. The description of the network interface hardware, basic protocol definition, electrical specifications, and the CRC byte is given in SAE J1850.

This SAE Recommended Practice defines the information contained in the header and data fields of non-diagnostic messages for automotive serial communications based on SAE J1850 Class B networks. This document describes and specifies the header fields, data fields, field sizes, scaling, representations, and data positions used within messages. The general structure of a SAE J1850 message frame without in-frame response is shown in Figure 1. The structure of a SAE J1850 message with in-frame response is shown in Figure 2. Figures 1 and 2 also show the scope of frame fields defined by this document for non-diagnostic messages. Refer to SAE J1979 for specifications of emissions related diagnostic message header and data fields. Refer to SAE J2190 for the definition of other diagnostic data fields. The description of the network interface hardware, basic protocol definition, the electrical specifications, and the CRC byte are given in SAE J1850.

This SAE Information Report studies the present transmission media axioms and takes a fresh look at the Class C transmission medium requirements and also the possibilities and limitations of using a twisted pair as the transmission medium. The choice of transmission medium is a large determining factor in choosing a Class C scheme.

This SAE Information Report studies the present transmission media axioms and takes a fresh look at the Class C transmission medium requirements and also the possibilities and limitations of using a twisted pair as the transmission medium. The choice of transmission medium is a large determining factor in choosing a Class C scheme.

This SAE Information Report will explain the differences between Class A, B, and C networks and clarify through examples, the differences in applications. Special attention will be given to a listing of functions that could be attached to a Class A communications network.

This SAE Information Report will explain the differences between Class A, B, and C networks and clarify through examples, the differences in applications. Special attention will be given to a listing of functions that could be attached to a Class A communications network.

This SAE Recommended Practice defines the information contained in the header and data fields of non-diagnostic messages for automotive serial communications based on SAE J1850 Class B networks. This document describes and specifies the header fields, data fields, field sizes, scaling, representations, and data positions used within messages. The general structure of a SAE J1850 message frame without in-frame response is shown in Figure 1. The structure of a SAE J1850 message with in-frame response is shown in Figure 2. Figures 1 and 2 also show the scope of frame fields defined by this document for non-diagnostic messages. Refer to SAE J1979 for specifications of emissions related diagnostic message header and data fields. Refer to SAE J2190 for the definition of other diagnostic data fields. The description of the network interface hardware, basic protocol definition, the electrical specifications, and the CRC byte are given in SAE J1850.

This document is an information report and intended to provide an overview of the Clock Extension Peripheral Interface (CXPI) protocol.

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-1 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-1 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.

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 systems, design and development tools, software, ECUs and media shall be designed. This will assure consistent and unambiguous serial data communication among all connected devices regardless of supplier. This document may be referenced by any vehicle OEM component technical specification that describes any given ECU in which the single wire data link controller and physical layer interface is located. The intended audience includes, but is not limited to, ECU suppliers, LIN controller suppliers, LIN transceiver suppliers, component release engineers and vehicle system engineers.

This document covers the requirements for transceiver qualification. Requirements stated in this document will provide a minimum standard level of performance for the LIN transceiver block in the IC to which all compatible transceivers shall be designed. No other features in the IC are tested or qualified as part of this recommended practice. This will assure robust serial data communication among all connected devices regardless of supplier. The goal of SAE J2962-1 is to commonize approval processes of LIN transceivers across OEMs. The intended audience includes, but is not limited to, LIN transceiver suppliers, component release engineers, and vehicle system engineers.

This document defines a level of standardization in the implementation of the digital pulse scheme for reporting sensor information via Single Edge Nibble Transmission (SENT) encoding. 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. Requirements stated in this document provide a minimum standard level of performance to which all compatible ECUs and media shall be designed. This assures data communication among all connected devices regardless of supplier. This document is a communication interface specification and no to be treated as product specification. The intended audience includes, but is not limited to, ECU suppliers, sensor suppliers, component release engineers and vehicle system engineers.

This document defines a level of standardization in the implementation of the digital pulse scheme for reporting sensor information via Single Edge Nibble Transmission (SENT) encoding. 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. Requirements stated in this document provide a minimum standard level of performance to which all compatible ECUs and media shall be designed. This assures data communication among all connected devices regardless of supplier. The intended audience includes, but is not limited to, ECU suppliers, sensor suppliers, component release engineers and vehicle system engineers.

This document defines a level of standardization in the implementation of the digital pulse scheme for reporting sensor information via Single Edge Nibble Transmission (SENT) encoding. 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. Requirements stated in this document provide a minimum standard level of performance to which all compatible ECUs and media shall be designed. This assures data communication among all connected devices regardless of supplier. The intended audience includes, but is not limited to, ECU suppliers, sensor suppliers, component release engineers and vehicle system engineers.

This document defines a level of standardization in the implementation of the digital pulse scheme for reporting sensor information via Single Edge Nibble Transmission (SENT) encoding. 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. Requirements stated in this document provide a minimum standard level of performance to which all compatible ECUs and media shall be designed. This assures data communication among all connected devices regardless of supplier. The intended audience includes, but is not limited to, ECU suppliers, sensor suppliers, component release engineers and vehicle system engineers.

This document defines a level of standardization in the implementation of the digital pulse scheme for reporting sensor information via Single Edge Nibble Transmission (SENT) encoding. 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. Requirements stated in this document provide a minimum standard level of performance to which all compatible ECUs and media shall be designed. This assures data communication among all connected devices regardless of supplier. This document is a communication interface specification and no to be treated as product specification. The intended audience includes, but is not limited to, ECU suppliers, sensor suppliers, component release engineers and vehicle system engineers.