Refine Your Search

Topic

Search Results

Standard

Bluetooth™ Wireless Protocol for Automotive Applications

2001-12-31
HISTORICAL
J2561_200112
This SAE Information Report defines the functionality of typical Bluetooth applications used for remotely accessing in-vehicle automotive installations of electronic devices. Remote access may be achieved directly with on-board Bluetooth modules, or indirectly via a custom designed gateway that communicates with Bluetooth and non-Bluetooth modules alike. Access to the vehicle, in the form of two-way communications, may be made via a single master port, or via multiple ports on the vehicle. The Bluetooth technology may also be used in conjunction with other types of off-board wireless technology. This report recommends using a message strategy that is already defined in one or more of the documents listed in 2.1.1, 2.1.4, 2.1.5, and 2.1.6. Those strategies may be used for some of the typical remote communications with a vehicle. It is recognized, however, that there may be specific applications requiring a unique message strategy or structure.
Standard

Bluetooth™ Wireless Protocol for Automotive Applications

2016-11-08
CURRENT
J2561_201611
This SAE Information Report defines the functionality of typical Bluetooth applications used for remotely accessing in-vehicle automotive installations of electronic devices. Remote access may be achieved directly with on-board Bluetooth modules, or indirectly via a custom designed gateway that communicates with Bluetooth and non-Bluetooth modules alike. Access to the vehicle, in the form of two-way communications, may be made via a single master port, or via multiple ports on the vehicle. The Bluetooth technology may also be used in conjunction with other types of off-board wireless technology. This report recommends using a message strategy that is already defined in one or more of the documents listed in 2.1.1, 2.1.4, 2.1.5, and 2.1.6. Those strategies may be used for some of the typical remote communications with a vehicle. It is recognized, however, that there may be specific applications requiring a unique message strategy or structure.
Standard

Chrysler Sensor and Control (CSC) Bus Multiplexing Network for Class 'A' Applications

1990-06-21
HISTORICAL
J2058_199006
THE CSC Bus components defined herein were developed to provide simple, yet reliable, communication between a host master module and its sensors and actuators. The scheme chosen provides the ability to communicate in both polling mode and direct addressing modes. Vehicle Architecture for Data Communication Standards Committee voted to cancel document - 7/19/2002 J2058 and J2106 Rationale Per Jack Volk, Vice Chairperson of Vehicle Architecture for Data Communication Standards Committee, document not being used. Information may be contained in other documents, (not necessarily SAE documents).
Standard

Chrysler Sensor and Control (CSC) Bus Multiplexing Network for Class 'A' Applications

2002-07-25
CURRENT
J2058_200207
THE CSC Bus components defined herein were developed to provide simple, yet reliable, communication between a host master module and its sensors and actuators. The scheme chosen provides the ability to communicate in both polling mode and direct addressing modes. Vehicle Architecture for Data Communication Standards Committee voted to cancel document - 7/19/2002 J2058 and J2106 Rationale Per Jack Volk, Vice Chairperson of Vehicle Architecture for Data Communication Standards Committee, document not being used. Information may be contained in other documents, (not necessarily SAE documents).
Standard

Class A Application/Definition

2006-09-12
CURRENT
J2057/1_200609
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.
Standard

Class A Application/Definition

1991-06-01
HISTORICAL
J2057/1_199106
This SAE Information Report will explain the difference 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.
Standard

Class A Multiplexing Actuators

2001-08-30
HISTORICAL
J2057/2_200108
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.
Standard

Class A Multiplexing Actuators

2006-09-12
CURRENT
J2057/2_200609
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.
Standard

Class A Multiplexing Architecture Strategies

2006-09-12
CURRENT
J2057/4_200609
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.
Standard

Class A Multiplexing Architecture Strategies

2001-08-30
HISTORICAL
J2057/4_200108
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.
Standard

Class A Multiplexing Sensors

2006-09-12
CURRENT
J2057/3_200609
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.
Standard

Class A Multiplexing Sensors

2001-08-30
HISTORICAL
J2057/3_200108
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.
Standard

Class B Data Communication Network Interface

1996-11-01
HISTORICAL
J1850_199611
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.
Standard

Class B Data Communication Network Messages - Detailed Header Formats and Physical Address Assignments

1999-03-01
HISTORICAL
J2178/1_199903
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.
Standard

Class B Data Communication Network Messages - Detailed Header Formats and Physical Address Assignments

2004-07-27
HISTORICAL
J2178/1_200407
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.
Standard

Class B Data Communication Network Messages - Detailed Header Formats and Physical Address Assignments

2011-04-01
CURRENT
J2178/1_201104
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.
Standard

Class B Data Communication Network Messages - Detailed Header Formats and Physical Address Assignments

1992-06-01
HISTORICAL
J2178/1_199206
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.
Standard

Class B Data Communication Network Messages - Message Definitions for Three Byte Headers

1999-03-11
HISTORICAL
J2178/4_199903
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.
X