Search Results

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.

This SAE Information Report is a summary comparison of existing protocols found in manufacturing, automotive, aviation, military, and computer applications which provide background or may be applicable for Class C application. The intent of this report is to present a summary of each protocol, not an evaluation. This is not intended to be a comprehensive review of all applicable protocols. The form for evaluation of a protocol exists in this paper and new protocols can be submitted on this form to the committee for consideration in future revisions of this report. This report contains a table which provides a side-by-side comparison of each protocol considered. The subsequent section provides a more detailed examination of the protocol attributes. Many of the protocols do not specify a method for one or more of the criteria. In these circumstances 'under defined' or 'not specified' will appear under the heading.

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.

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.

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 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.

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.

This document covers the requirements for SAE implementations based on ISO 17987:2016. 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 adding additional requirements that are not present in ISO 17987:2016 (e.g., fault tolerant operation, network topology, etc.). The intended audience includes, but is not limited to, ECU suppliers, LIN controller suppliers, LIN transceiver suppliers, component release engineers, and vehicle system engineers. The term “master” has been replaced by “commander” and term “slave” with “responder” in the following sections.

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 500 kbps arbitration bus with CAN FD data at 5 Mbps 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 500 kbps arbitration bus with CAN FD Data at 5 Mbps. The minimum performance level shall be specified by system level performance requirements or characteristics described in detail in Section 6 of this document.

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 500 kbps arbitration bus with CAN FD data at 2 Mbps 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 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 500 kbps arbitration bus with CAN FD data at 2 Mbps. The minimum performance level shall be specified by system level performance requirements or characteristics described in detail in Section 6 of this document.

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 500 kbps high-speed CAN (HSC) protocol implementation. Both electronic control unit (ECU) and media design requirements for networks will be specified. Requirements will primarily address the controller area network (CAN) physical layer implementation. Requirements will focus on a minimum standard level of performance from the 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 500 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 ECU requirements defined in Section 6 are met, then the system level attributes should be obtainable.

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.

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 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 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 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.

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.

This SAE Recommended Practice covers the requirements for ethernet physical layer (PHY) qualification. Requirements stated in this document provide a minimum standard level of performance for the PHY in the IC to which all compatible ethernet communications PHY shall be designed. When the communications chipset is an ethernet switch with an integrated automotive PHY (xBASE-T1), then the testing shall include performance for all switch PHY ports as well as each controller interface. No other features in the IC are tested or qualified as part of this SAE Recommended Practice. This assures robust serial data communication among all connected devices regardless of supplier. The goal of SAE J2962-3 is to commonize approval processes of ethernet PHYs across OEMs. The intended audience includes, but is not limited to, ethernet PHY suppliers, component release engineers, and vehicle system engineers.

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.