Search Results

This SAE Recommended Practice establishes the requirements for a Class B Data Communication Network Interface applicable to all On and Off-Road Land Based Vehicles. It defines a minimum set of data communication requirements such that the resulting network is cost effective for simple applications and flexible enough to use in complex applications. Taken in total, the requirements contained in this document specify a data communications network that satisfies the needs of automotive manufacturers. This specification describes two specific implementations of the network, based on media/Physical Layer differences. One Physical Layer is optimized for a data rate of 10.4 Kbps while the other Physical Layer is optimized for a data rate of 41.6 Kbps. Additionally, this document outlines one Physical Layer alternative to the two fully defined implementations that may allow the network to operate at a 125 Kbps data rate.

The objective of this document is to define a minimum set of physical and data link layer requirements applicable to a vehicle data communication network that is cost effective for simple applications and flexible enough to use in complex applications. Network requirements "above" the physical and data link layers are generally application specific and are, therefore, left to the system designer. The requirements contained in this document define a data communications network philosophy that satisfies the needs of the automotive manufacturers. In its present form, this document defines a cohesive set of data link layer requirements. On the other hand, several alternative physical layer approaches are specified to accommodate a variety of application requirements.

This SAE Recommended Practice establishes the requirements for a Class B Data Communication Network Interface applicable to all on and off-road land based vehicles. This document defines a minimum set of data communication requirements such that the resulting network is cost effective for simple applications and flexible enough to use in complex applications. Although this document addresses all seven layers of the OSI model, it primarily focuses on the Network, Data Link and Physical Layers. Taken in total, the requirements contained in this document specify a data communications network philosophy that satisfies the needs of automotive manufacturers. Although the higher layer OSI requirements are essentially identical for all networks defined by this document (see Section 3.3, Figure 1), differing data rate requirements necessitate the use of different physical layers.

This SAE Standard establishes the requirements for a Class B Data Communication Network Interface applicable to all On- and Off-Road Land-Based Vehicles. It defines a minimum set of data communication requirements such that the resulting network is cost effective for simple applications and flexible enough to use in complex applications. Taken in total, the requirements contained in this document specify a data communications network that satisfies the needs of automotive manufacturers. This specification describes two specific implementations of the network, based on media/Physical Layer differences. One Physical Layer is optimized for a data rate of 10.4 Kbps while the other Physical Layer is optimized for a data rate of 41.6 Kbps (see Appendix A for a checklist of application-specific features).

This SAE Standard establishes the requirements for a Class B Data Communication Network Interface applicable to all On- and Off-Road Land-Based Vehicles. It defines a minimum set of data communication requirements such that the resulting network is cost effective for simple applications and flexible enough to use in complex applications. Taken in total, the requirements contained in this document specify a data communications network that satisfies the needs of automotive manufacturers. This specification describes two specific implementations of the network, based on media/Physical Layer differences. One Physical Layer is optimized for a data rate of 10.4 Kbps while the other Physical Layer is optimized for a data rate of 41.6 Kbps (see Appendix A for a checklist of application-specific features). The Physical Layer parameters are specified as they would be detected on the network media, not within any particular module or integrated circuit implementation.

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.

The Class A Task Force of the Vehicle Network for Multiplex and Data Communications Committee is publishing this SAE Information Report to provide insight into Class A Multiplexing. Multiplexed actuators are generally defined as devices which accept information from the multiplexed bus. A multiplexed actuator can be an output device controlled by the operator or an intelligent controller. A Multiplex actuator can also be a display device that reports the status of a monitored vehicle function. This document is intended to help the network system engineers and is meant to stimulate the design thought process. A list of multiplexed actuator examples is provided in Appendix A, Figure A1. Many other examples can be it identified.

The subject matter contained within this SAE Information Report is set forth by the Class A Task Force of the Vehicle Network for Multiplexing and Data Communications (Multiplex) Committee as information the network system designer should consider. The Task Force realizes that the information contained in this report may be somewhat controversial and a consensus throughout the industry does not exist at this time. The Task Force also intends that the analysis set forth in this document is for sharing information and encouraging debate on the benefits of utilizing a multiple network architecture.

The subject matter contained within this SAE Information Report is set forth by the Class A Task Force of the Vehicle Network for Multiplexing and Data Communications (Multiplex) Committee as information the network system designer should consider. The Task Force realizes that the information contained in this report may be somewhat controversial and a consensus throughout the industry does not exist at this time. The Task Force also intends that the analysis set forth in this document is for sharing information and encouraging debate on the benefits of utilizing a multiple network architecture.

The Class A Task Force of the Vehicle Network for Multiplexing and Data Communications Subcommittee is providing information on sensors that could be applicable for a Class A Bus application. Sensors are generally defined as any device that inputs information onto the bus. Sensors can be an input controlled by the operator or an input that provides the feedback or status of a monitored vehicle function. Although there is a list of sensors provided, this list is not all-inclusive. This SAE Information Report is intended to help the network system engineer and is meant to stimulate the design thought process.

The Class A Task Force of the Vehicle Network for Multiplexing and Data Communications Subcommittee is providing information on sensors that could be applicable for a Class A Bus application. Sensors are generally defined as any device that inputs information onto the bus. Sensors can be an input controlled by the operator or an input that provides the feedback or status of a monitored vehicle function. Although there is a list of sensors provided, this list is not all-inclusive. This SAE Information Report is intended to help the network system engineer and is meant to stimulate the design thought process.

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 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 Standard establishes the requirements for a Class B Data Communication Network Interface applicable to all On-and OffRoad Land-Based Vehicles. It defines a minimum set of data communication requirements such that the resulting network is cost effective for simple applications and flexible enough to use in complex applications. Taken in total, the requirements contained in this document specify a data communications network that satisfies the needs of automotive manufacturers. This specification describes two specific implementations of the network, based on media/Physical Layer differences. One Physical Layer is optimized for a data rate of 10.4 Kbps while the other Physical Layer is optimized for a data rate of 41.6 Kbps (see Appendix A for a checklist of application-specific features). The Physical Layer parameters are specified as they would be detected on the network media, not within any particular module or integrated circuit implementation.

This SAE Recommended Practice will focus on the requirements of Class C applications. The requirements for these applications are different from those required for either Class A or Class B applications. An overall example is provided for consistency of discussion. Cancelled due to lack of interest.

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

The scope of this specification is to define the transfer layer and the consequences of the Controller Area Network (CAN) protocol on the surrounding layers.

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.