Refine Your Search

Search Results

Viewing 1 to 11 of 11
Standard

Class B Data Communication Network Messages - Part 3 - Frame IDs for Single-Byte Forms of Headers

2011-05-02
CURRENT
J2178/3_201105
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.
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

Single Wire CAN Network for Vehicle Applications

2000-02-14
CURRENT
J2411_200002
This SAE Recommended Practice defines the Physical Layer and portions of the Data Link Layer of the OSI model for data communications. In particular, this document specifies the physical layer requirements for any Carrier Sense Multiple Access/Collision Resolution (CSMA/CR) data link which operates on a single wire medium to communicate among Electronic Control Units (ECU) on road vehicles. 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. This document is to be referenced by the particular vehicle OEM Component Technical Specification which 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.
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

Selection of Transmission Media

2000-02-23
CURRENT
J2056/3_200002
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.
Standard

Glossary of Vehicle Networks for Multiplexing and Data Communications

1997-09-01
CURRENT
J1213/1_199709
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.
Standard

LIN Network for Vehicle Applications Conformance Test

2012-11-19
CURRENT
J2602/2_201211
This document covers the tests to be performed on all SAE J2602-1 defined Master and Slave nodes. Tests described in this document will ensure a minimum standard level of performance to which all compatible Electronic Control Unit (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-2 is to improve the interoperability and interchangeability of LIN devices within a network by verifying the devices pass a minimum set of tests. To allow for easy cross-reference, this document is arranged such that the conformance test for a given section in SAE J2602-1 is in the same section in SAE J2602-2. This document is to be referenced by the particular vehicle Original Equipment Manufacturer (OEM) component technical specification that describes any given ECU in which the LIN data link controller and physical layer interface is located.
Standard

LIN Network for Vehicle Applications

2012-11-19
CURRENT
J2602/1_201211
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.
Standard

Class B Data Communications Network Interface

2015-10-14
CURRENT
J1850_201510
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.
Standard

Class B Data Communications Network Interface

2006-06-07
HISTORICAL
J1850_200606
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.
X