Your Selections

TEVEES12
Show Only

Collections

File Formats

Content Types

Dates

Sectors

Topics

Publishers

Committees

Committee Codes

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…
Datasets icon
Annotation icon

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…
Datasets icon
Annotation icon

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…
Datasets icon
Annotation icon

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.…
Datasets icon
Annotation icon

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…
Datasets icon
Annotation icon

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…
Datasets icon
Annotation icon

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.
Datasets icon
Annotation icon

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.
Datasets icon
Annotation icon

Class B Data Communications Network Interface

Vehicle Architecture For Data Communications Standards
  • Ground Vehicle Standard
  • J1850_201510
  • Current
Published 2015-10-14 by SAE International in United States
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. Although devices may be constructed that can be configured to operate in either of the two primary implementations defined herein, it is expected that most manufacturers will focus specifically on either the…
Datasets icon
Annotation icon

LIN Network for Vehicle Applications

Vehicle Architecture For Data Communications Standards
  • Ground Vehicle Standard
  • J2602/1_201211
  • Current
Published 2012-11-19 by SAE International in United States
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. ECU environmental and other requirements, when provided in the component technical specification, shall supersede the requirements of this document. The intended audience includes, but is not limited to, ECU suppliers, LIN…
Datasets icon
Annotation icon