Your Selections

TEVEES12
Show Only

Collections

File Formats

Content Types

Dates

Sectors

Topics

Publishers

Committees

Committee Codes

   This content is not included in your SAE MOBILUS subscription, or you are not logged in.

Communication Transceivers Qualification Requirements - LIN

Vehicle Architecture For Data Communications Standards
  • Ground Vehicle Standard
  • J2962/1_201907
  • Current
Published 2019-07-18 by SAE International in United States
This document covers the requirements for transceiver qualification. Requirements stated in this document will provide a minimum standard level of performance for the LIN transceiver block in the IC to which all compatible transceivers shall be designed. No other features in the IC are tested or qualified as part of this recommended practice. This will assure robust serial data communication among all connected devices regardless of supplier. The goal of SAE J2962-1 is to commonize approval processes of LIN transceivers across OEMs. The intended audience includes, but is not limited to, LIN transceiver suppliers, component release engineers, and vehicle system engineers.
This content contains downloadable datasets
Annotation ability available
   This content is not included in your SAE MOBILUS subscription, or you are not logged in.

Communication Transceivers Qualification Requirements - CAN

Vehicle Architecture For Data Communications Standards
  • Ground Vehicle Standard
  • J2962/2_201907
  • Current
Published 2019-07-18 by SAE International in United States
This document covers the requirements for transceiver qualification. Requirements stated in this document will provide a minimum standard level of performance for the CAN transceiver in the IC to which all compatible transceivers shall be designed. No other features in the IC are tested or qualified as part of this recommended practice. This will assure robust serial data communication among all connected devices, regardless of supplier. The goal of SAE J2962-2 is to commonize approval processes of CAN transceivers across OEMs. The intended audience includes, but is not limited to, CAN transceiver suppliers, component release engineers, and vehicle system engineers.
This content contains downloadable datasets
Annotation ability available
   This content is not included in your SAE MOBILUS subscription, or you are not logged in.

High-Speed CAN (HSC) for Vehicle Applications at 500 KBPS

Vehicle Architecture For Data Communications Standards
  • Ground Vehicle Standard
  • J2284/3_201611
  • Current
Published 2016-11-29 by SAE International in United States
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 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. 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 will address only requirements which may be tested at the ECU and media level. No requirements which apply to the testing of the HSC implementation as integrated into a vehicle…
This content contains downloadable datasets
Annotation ability available
   This content is not included in your SAE MOBILUS subscription, or you are not logged in.

High Speed CAN (HSC) for Vehicle Applications at 250 kbps

Vehicle Architecture For Data Communications Standards
  • Ground Vehicle Standard
  • J2284/2_201611
  • Current
Published 2016-11-22 by SAE International in United States
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 will address only requirements which may be tested at the ECU and media level. No requirements which apply to the testing of the HSC implementation as…
This content contains downloadable datasets
Annotation ability available
   This content is not included in your SAE MOBILUS subscription, or you are not logged in.

High Speed CAN (HSC) for Vehicle Applications at 125 kbps

Vehicle Architecture For Data Communications Standards
  • Ground Vehicle Standard
  • J2284/1_201611
  • Current
Published 2016-11-21 by SAE International in United States
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 address only requirements which may be tested at the ECU and media level. No requirements which apply to the testing of the HSC implementation as integrated…
This content contains downloadable datasets
Annotation ability available
   This content is not included in your SAE MOBILUS subscription, or you are not logged in.

Bluetooth™ Wireless Protocol for Automotive Applications

Vehicle Architecture For Data Communications Standards
  • Ground Vehicle Standard
  • J2561_201611
  • Current
Published 2016-11-08 by SAE International in United States
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 depicts five different levels of security measures that may be required for the various types of communication. The EMC test requirements for the implementation of this protocol are recommended.…
This content contains downloadable datasets
Annotation ability available
   This content is not included in your SAE MOBILUS subscription, or you are not logged in.

High-Speed CAN (HSC) for Vehicle Applications at 500 kbps with CAN FD Data at 5 Mbps

Vehicle Architecture For Data Communications Standards
  • Ground Vehicle Standard
  • J2284/5_201609
  • Current
Published 2016-09-09 by SAE International in United States
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 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 will address only requirements which may be tested at the…
This content contains downloadable datasets
Annotation ability available
   This content is not included in your SAE MOBILUS subscription, or you are not logged in.

High-Speed CAN (HSC) for Vehicle Applications at 500 kbps with CAN FD Data at 2 Mbps

Vehicle Architecture For Data Communications Standards
  • Ground Vehicle Standard
  • J2284/4_201606
  • Current
Published 2016-06-16 by SAE International in United States
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 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 will address only requirements which may be tested at the ECU and…
This content contains downloadable datasets
Annotation ability available
   This content is not included in your SAE MOBILUS subscription, or you are not logged in.

SENT - Single Edge Nibble Transmission for Automotive Applications

Vehicle Architecture For Data Communications Standards
  • Ground Vehicle Standard
  • J2716_201604
  • Current
Published 2016-04-29 by SAE International in United States
This document defines a level of standardization in the implementation of the digital pulse scheme for reporting sensor information via Single Edge Nibble Transmission (SENT) encoding. This standard will allow ECU and tool manufacturers to satisfy the needs of multiple end users with minimum modifications to the basic design. This standard will benefit vehicle Original Equipment Manufacturers (OEMs) by achieving lower ECU costs due to higher industry volumes of the basic design. Requirements stated in this document provide a minimum standard level of performance to which all compatible ECUs and media shall be designed. This assures data communication among all connected devices regardless of supplier. This document is a communication interface specification and no to be treated as product specification. The intended audience includes, but is not limited to, ECU suppliers, sensor suppliers, component release engineers and vehicle system engineers.
This content contains downloadable datasets
Annotation ability available
   This content is not included in your SAE MOBILUS subscription, or you are not logged in.

Clock Extension Peripheral Interface (CXPI)

Vehicle Architecture For Data Communications Standards
  • Ground Vehicle Standard
  • J3076_201510
  • Current
Published 2015-10-27 by SAE International in United States
This document is an information report and intended to provide an overview of the Clock Extension Peripheral Interface (CXPI) protocol.
This content contains downloadable datasets
Annotation ability available