Search Results

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 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 compilation of terms, acronyms and symbols was drawn from usage which should be familiar to those working in automotive electronics reliability. Terms are included which are used to describe how items, materials and systems are evaluated for reliability, how they fail, how failures are modeled and how failures are prevented. Terms are also included from the disciplines of designing for reliability, testing and failure analysis as well as the general disciplines of Quality and Reliability Engineering. This glossary is intended to augment SAE J1213, Glossary of Automotive Electronic Terms.

The Token Slot Data Link is intended to provide periodic, broadcast communications (communication that must occur on a regular, predetermined basis) within a vehicle system. The Token Slot protocol achieves this by implementing a masterless, deterministic, non-contention Token Slot sequence which is designed to offer a transmit token to all devices (or nodes) without requiring that they respond. After acquiring the token, messages may be sent and verified using a variety of built-in techniques. The token passing slot sequence is then reinitiated by the current token holder.

The Token Slot Data Link is intended to provide periodic, broadcast communications (communication that must occur on a regular, predetermined basis) within a vehicle system. The Token Slot protocol achieves this by implementing a masterless, deterministic, non-contention Token Slot sequence which is designed to offer a transmit token to all devices (or nodes) without requiring that they respond. After acquiring the token, messages may be sent and verified using a variety of built-in techniques. The token passing slot sequence is then reinitiated by the current token holder.

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.

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 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 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 will define the Physical Layer and portions of the Data Link Layer of the ISO model for a 125 Kbps High Speed CAN (HSC) protocol implementation. Both ECU and media design requirements for networks will be specified. Requirements will primarily address the CAN physical layer implementation. Requirements will focus on a minimum standard level of performance from the High Speed CAN (HSC) implementation. All ECUs and media shall be designed to meet certain component level requirements in order to ensure the HSC implementation system level performance at 125 Kbps. The minimum performance level shall be specified by system level performance requirements or characteristics described in detail in Section 6 of this document. This document is designed such that if the Electronic Control Unit requirements defined in Section 6 are met, then the system level attributes should be obtainable. This document will address only requirements which may be tested at the ECU and media level.

This SAE Recommended Practice will define the Physical Layer and portions of the Data Link Layer of the Open Systems Interconnection model (ISO 7498) for a 125 kbps High Speed CAN (HSC) protocol implementation. Both ECU and media design requirements for networks will be specified. Requirements will primarily address the CAN physical layer implementation. Requirements will focus on a minimum standard level of performance from the High Speed CAN (HSC) implementation. All ECUs and media shall be designed to meet certain component level requirements in order to ensure the HSC implementation system level performance at 125 kbps. The minimum performance level shall be specified by system level performance requirements or characteristics described in detail in Section 5 of this document. This document is designed such that if the Electronic Control Unit requirements defined in Section 6 are met, then the system level attributes should be obtainable.

This document will define the Physical Layer and portions of the Data Link Layer of the ISO model for a 250 Kbps High Speed CAN (HSC) protocol implementation. Both ECU and media design requirements for networks will be specified. Requirements will primarily address the CAN physical layer implementation. Requirements will focus on a minimum standard level of performance from the High Speed CAN (HSC) implementation. All ECUs and media shall be designed to meet certain component level requirements in order to ensure the HSC implementation system level performance at 250 Kbps. The minimum performance level shall be specified by system level performance requirements or characteristics described in detail in Section 6 of this document. This document is designed such that if the Electronic Control Unit requirements defined in Section 6 are met, then the system level attributes should be obtainable. This document will address only requirements which may be tested at the ECU and media level.

This SAE Recommended Practice will define the Physical Layer and portions of the Data Link Layer of the Open Systems Interconnection model (ISO 7498) for a 250 kbps High Speed CAN (HSC) protocol implementation. Both ECU and media design requirements for networks will be specified. Requirements will primarily address the CAN physical layer implementation. Requirements will focus on a minimum standard level of performance from the High Speed CAN (HSC) implementation. All ECUs and media shall be designed to meet certain component level requirements in order to ensure the HSC implementation system level performance at 250 kbps. The minimum performance level shall be specified by system level performance requirements or characteristics described in detail in Section 5 of this document. This document is designed such that if the Electronic Control Unit (ECU) requirements defined in Section 6 are met, then the system level attributes should be obtainable.

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.

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.