The scope of this specification is to define the transfer layer and the consequences of the Controller Area Network (CAN) protocol on the surrounding layers.
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 Recommended Practice will focus on the requirements of Class C applications. The requirements for these applications are different from those required for either Class A or Class B applications. An overall example is provided for consistency of discussion. Cancelled due to lack of interest.
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.
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 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.
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.
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 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 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 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 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 SAE Recommended Practice 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. Additionally, this document outlines one Physical Layer alternative to the two fully defined implementations that may allow the network to operate at a 125 Kbps data rate.
This SAE Recommended Practice establishes the requirements for a Class B Data Communication Network Interface applicable to all on and off-road land based vehicles. This document 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. Although this document addresses all seven layers of the OSI model, it primarily focuses on the Network, Data Link and Physical Layers. Taken in total, the requirements contained in this document specify a data communications network philosophy that satisfies the needs of automotive manufacturers. Although the higher layer OSI requirements are essentially identical for all networks defined by this document (see Section 3.3, Figure 1), differing data rate requirements necessitate the use of different physical layers.
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.