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.
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.
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 has been compiled to serve for reference in an effort to assist communications between the automotive engineer and the electronics engineer. 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, 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 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 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 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 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 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, 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, the electrical specifications, and the CRC byte are given in SAE J1850.
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.
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.
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.