Criteria

Text:
Sector:
Content:
Display:

Results

Viewing 1 to 30 of 63
CURRENT
2016-11-21
Standard
J2284/1_201611
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.
CURRENT
2016-11-08
Standard
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.
2016-09-30
WIP Standard
J2945/4
This standard will serve to re-work and extend the existing SAE J2735 message elements in order to include additional travel and roadway information from the infrastructure to enhance safety awareness and promote the exchange and transfer of such messages types between vehicles and the infrastructure (V2I). Fundamentally this document will outline the needs and detail the system requirements to support a variety of use cases linking to the J2735 effort as other J2945/x documents do. The initial scope will be to revise the structure of the existing “TIM” message to reflect the lessons learned from the various deployment activities such as the BIM developed by an automotive OEM consortium. The objective is to improve the general functionality of the message set in key areas such as message linking, content segmentation, message forwarding within a security framework, and new application areas beyond what is enabled by the TIM.
2016-09-06
WIP Standard
J2818
This Technical Information Report defines the diagnostic communication protocol Keyword Protocol 1281 (KWP1281). This document should be used in conjunction with SAE J2534-2 in order to fully implement the communication protocol in an SAE J2534 interface. Some Volkswagen of America and Audi of America vehicles are equipped with ECUs, in which a KWP1281 proprietary diagnostic communication protocol is implemented. The purpose of this document is to specify the KWP1281 protocol in enough detail to support the requirements necessary to implement the communication protocol in an SAE J2534 interface device.
2016-09-06
WIP Standard
J2819
This Technical Information Report defines the diagnostic communication protocol TP2.0. This document should be used in conjunction with SAE J2534-2 in order to fully implement the communication protocol in an SAE J2534 interface. Some Volkswagen of America and Audi of America vehicles are equipped with ECU(s), in which a TP2.0 proprietary diagnostic communication protocol is implemented. The purpose of this document is to specify the requirements necessary to implement the communication protocol in an SAE J2534 interface.
2016-07-27
WIP Standard
J2945/12
This recommended practice will provide guidance on Traffic Probe Use data to manufacturers that are either Transportation System Management (TSM) core or aligned entities. The recommended practice originates from prior work of the Society of Automotive Engineers (SAE) Dedicated Short Range Communication (DSRC) Technical Committee, as well as existing practices implemented by industry, academia and government. The recommended practice informs manufacturers and practitioners of message use and operation within an automated collection system involved in the orchestration of safe, efficient, and reliable movement of people and goods. The recommended practice for Traffic Probe Use and Operation will support practitioners through the definition of message structure, on-board processing and storage requirements, the operational preservation of vehicle anonymity, and message event management criteria.
2016-06-02
WIP Standard
J2836/5
This SAE Information Report J2836/5™ establishes the use cases for communications between Plug-In Electric Vehicles (PEV) and their customers. The use case scenarios define the information to be communicated related to customer convenience features for charge on/off control, charge power curtailment, customer preference settings, charging status, EVSE availability/access, and electricity usage. Also addresses customer information resulting from conflicts to customer charging preferences. This document only provides the use cases that define the communications requirements to enable customers to interact with the PEV and to optimize their experience with driving a Plug-In Electric Vehicle. Specifications such as protocols and physical transfer methods for communicating information are not within the scope of this document.
2016-04-05
WIP Standard
J2945/11
This effort will be a recommend best practices document outlining how to use the J2735 Signal Request and Signal Status messages in the standard relating to signalized systems status. It primary content will deal with explaining and demonstrating by small working examples how these messages are constructed and used to meet operational needs of user. Particular attention will be paid to the interaction between the SAE work and the relevant NTCIP standards used in the signal control system. [The SAE J2735 document, being a data dictionary and not a guide, allowed only a brief summary of this sort of material.] The intended audience for this effort are those developing new deployment using these messages in connection with intersection safety applications. This will be a recommend practice, not a standard.
2016-04-05
WIP Standard
J2945/10
This effort will be a recommend best practices document outlining how to use the current MAP and SPAT message content found in the recently published J2735. It’s primary content will deal with better explaining and demonstrating by small working examples of how suitable messages are constructed and used to meet operational needs of user. [The SAE J2735 document, being a data dictionary and not a guide, allowed only a briefs summary of this sort of material.] The intended audience for this effort are those developing new deployment using these messages in connection with intersection safety applications. This will be a recommend practice, not a standard.
CURRENT
2016-03-30
Standard
J2735ASN_201603
This Abstract Syntax Notation (ASN.1) File is the precise source code used for SAE International Standard J2735. As part of an international treaty, all US ITS standards are expressed in "ASN.1 syntax". ASN.1 Syntax is used to define the messages or "ASN specifications". Using the ASN.1 specification, a compiler tool produces the ASN library which will then be used to produce encodings (The J2735 message set uses UPER encoding). The library is a set of many separate files that collectively implement the encoding and decoding of the standard. The library is then used by any application (along with the additional logic of that application) to manage the messages. The chosen ASN tool is used to produce a new copy of the library when changes are made and it is then linked to the final application being developed. The ASN library manages many of the details associated with ASN syntax, allowing for subtle manipulation to make the best advantage of the encoding style.
CURRENT
2016-03-30
Standard
J2735SET_201603
This Abstract Syntax Notation (ASN.1) File is the precise source code used for SAE International Standard J2735. As part of an international treaty, all US ITS standards are expressed in "ASN.1 syntax". ASN.1 Syntax is used to define the messages or "ASN specifications". Using the ASN.1 specification, a compiler tool produces the ASN library which will then be used to produce encodings (The J2735 message set uses UPER encoding). The library is a set of many separate files that collectively implement the encoding and decoding of the standard. The library is then used by any application (along with the additional logic of that application) to manage the messages. The chosen ASN tool is used to produce a new copy of the library when changes are made and it is then linked to the final application being developed. The ASN library manages many of the details associated with ASN syntax, allowing for subtle manipulation to make the best advantage of the encoding style.
CURRENT
2016-03-30
Standard
J2735_201603
This SAE Standard specifies a message set, and its data frames and data elements, specifically for use by applications intended to utilize the 5.9 GHz Dedicated Short Range Communications for Wireless Access in Vehicular Environments (DSRC/WAVE, referenced in this document simply as “DSRC”) communications systems. Although the scope of this Standard is focused on DSRC, this message set, and its data frames and data elements, have been designed, to the extent possible, to be of potential use for applications that may be deployed in conjunction with other wireless communications technologies as well. This Standard therefore specifies the definitive message structure and provides sufficient background information to allow readers to properly interpret the message definitions from the point of view of an application developer implementing the messages according to the DSRC Standards.
CURRENT
2016-03-30
Standard
J2945/1_201603
This standard specifies the system requirements for an on-board vehicle-to-vehicle (V2V) safety communications system for light vehicles1, including standards profiles, functional requirements, and performance requirements. The system is capable of transmitting and receiving the Society of Automotive Engineers (SAE) J2735-defined Basic Safety Message (BSM) [1] over a Dedicated Short Range Communications (DSRC) wireless communications link as defined in the Institute of Electrical and Electronics Engineers (IEEE) 1609 suite and IEEE 802.11 standards [2] – [6].
2016-03-02
WIP Standard
J1939
This top level document provides a general overview of the SAE J1939 network and describes the subordinate document structure. This document includes definitions of terms and abbreviations which are used among the various SAE J1939 subordinate documents. The SAE J1939DA Digital Annex spreadsheet replaces the Appendices of this document for the publication of the list of all SPN assignments, PGN assignments, NAME Function assignments, Manufacturer Code assignments, and Preferred Address assignments. This document has been updated to reflect the change to discontinue publishing the content of Table A2, Tables B1 through B12, and Table C1 in Appendix A, Appendix B, and Appendix C; instead, this content is now published in the SAE J1939DA Digital Annex spreadsheet.
HISTORICAL
2016-01-19
Standard
J2735_201601
This SAE Standard specifies a message set, and its data frames and data elements, specifically for use by applications intended to utilize the 5.9 GHz Dedicated Short Range Communications for Wireless Access in Vehicular Environments (DSRC/WAVE, referenced in this document simply as “DSRC”) communications systems. Although the scope of this Standard is focused on DSRC, this message set, and its data frames and data elements, have been designed, to the extent possible, to be of potential use for applications that may be deployed in conjunction with other wireless communications technologies as well. This Standard therefore specifies the definitive message structure and provides sufficient background information to allow readers to properly interpret the message definitions from the point of view of an application developer implementing the messages according to the DSRC Standards.
CURRENT
2015-10-14
Standard
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.
CURRENT
2015-10-14
Standard
J1939/16_201510
Define a process enabling devices to detect the baud rate of a network automatically with the intent of minimizing or eliminating communication disruption between existing devices.
CURRENT
2015-09-22
Standard
J1939/74_201509
The SAE J1939 documents are intended for light, medium, and heavy-duty vehicles used on or off road as well as appropriate stationary applications which use vehicle derived components (e.g. generator sets). Vehicles of interest include, but are not limited to, on- and off-highway trucks and their trailers, construction equipment, and agricultural equipment and implements. The purpose of these documents is to provide an open interconnect system for electronic systems. It is the intention of these documents to allow Electronic Control Units to communicate with each other by providing a standard architecture. This particular document, SAE J1939-74, describes the message structure for a set of messages which enable the user to determine and announce to others on the network, the parameter placement within a particular message from the special set of messages defined within this document.
HISTORICAL
2015-09-02
Standard
J2735_201509
This SAE Standard specifies a message set, and its data frames and data elements specifically for use by applications intended to utilize the 5.9 GHz Dedicated Short Range Communications for Wireless Access in Vehicular Environments (DSRC/WAVE, referenced in this document simply as “DSRC”), communications systems. Although the scope of this Standard is focused on DSRC, this message set, and its data frames and data elements have been designed, to the extent possible, to also be of potential use for applications that may be deployed in conjunction with other wireless communications technologies. This Standard therefore specifies the definitive message structure and provides sufficient background information to allow readers to properly interpret the message definitions from the point of view of an application developer implementing the messages according to the DSRC Standards.
HISTORICAL
2015-08-28
Standard
J1939/73_201508
SAE J1939-73 Diagnostics Application Layer defines the SAE J1939 messages to accomplish diagnostic services and identifies the diagnostic connector to be used for the vehicle service tool interface. Diagnostic messages (DMs) provide the utility needed when the vehicle is being repaired. Diagnostic messages are also used during vehicle operation by the networked electronic control modules to allow them to report diagnostic information and self-compensate as appropriate, based on information received. Diagnostic messages include services such as periodically broadcasting active diagnostic trouble codes, identifying operator diagnostic lamp status, reading or clearing diagnostic trouble codes, reading or writing control module memory, providing a security function, stopping/starting message broadcasts, reporting diagnostic readiness, monitoring engine parametric data, etc.
CURRENT
2015-08-27
Standard
J2931/6_201508
This SAE Information Report J2931/6 establishes the requirements for physical and data link layer communications between Plug-in Electric Vehicles (PEV) and the Electric Vehicle Supply Equipment (EVSE).
CURRENT
2015-08-05
Standard
J2847/6_201508
This SAE Recommended Practice SAE J2847-6 establishes requirements and specifications for communications messages between wirelessly charged electric vehicles and the wireless charger. Where relevant, this document notes, but does not formally specify, interactions between the vehicle and vehicle operator. This is the 1st version of this document and captures the initial objectives of the SAE task force. The intent of step 1 is to record as much information on “what we think works” and publish. The effort continues however, to step 2 that allows public review for additional comments and viewpoints, while the task force also continues additional testing and early implementation. Results of step 2 effort will then be incorporated into updates of this document and lead to a republished version. The next revision will address the harmonization between SAE J2847-6 and ISO/IEC 15118-7 to ensure interoperability.
2015-05-13
WIP Standard
J2847/2
This SAE Recommended Practice SAE J2847-2 establishes requirements and specifications for communication between Plug-in Electric Vehicle (PEV) and the DC Off-board charger. Where relevant, this document notes, but does not formally specify, interactions between the vehicle and vehicle operator. This document applies to the off-board DC charger for conductive charging, which supplies DC current to the Rechargable Energy Storage System (RESS) of the electric vehicle through a SAE J1772™ coupler. Communications will be on the SAE J1772 Pilot line for PLC communication. The details of PowerLine Communications (PLC) are found in SAE J2931/4. The specification supports DC energy transfer via Forward Power Flow (FPF) from source to vehicle.
CURRENT
2015-05-07
Standard
J2836/5_201505
This SAE Information Report J2836/5™ establishes the use cases for communications between Plug-In Electric Vehicles (PEV) and their customers. The use case scenarios define the information to be communicated related to customer convenience features for charge on/off control, charge power curtailment, customer preference settings, charging status, EVSE availability/access, and electricity usage. Also addresses customer information resulting from conflicts to customer charging preferences. This document only provides the use cases that define the communications requirements to enable customers to interact with the PEV and to optimize their experience with driving a Plug-In Electric Vehicle. Specifications such as protocols and physical transfer methods for communicating information are not within the scope of this document.
HISTORICAL
2015-04-30
Standard
J1939/21_201504
The SAE J1939 documents are intended for light, medium, and heavy-duty vehicles used on or off road as well as appropriate stationary applications which use vehicle derived components (e.g., generator sets). Vehicles of interest include, but are not limited to, on- and off-highway trucks and their trailers, construction equipment, and agricultural equipment and implements. The purpose of these documents is to provide an open interconnect system for electronic systems. It is the intention of these documents to allow Electronic Control Units to communicate with each other by providing a standard architecture. This particular document, SAE J1939-21, describes the data link layer using the CAN protocol with 29-bit Identifiers. For SAE J1939 no alternative data link layers are permitted.
2015-04-19
WIP Standard
J2740
This Technical Information Report defines the General Motors UART Serial Data Communications Bus, commonly referred to as GM UART. This document should be used in conjunction with SAE J2534-2 in order to fully implement GM UART in an SAE J2534 interface. SAE J2534-1 includes requirements for an interface that can be used to program certain emission-related Electronic Control Units (ECU) as required by U.S. regulations, and SAE J2534-2 defines enhanced functionality required to program additional ECUs not mandated by current U.S. regulations. The purpose of this document is to specify the requirements necessary to implement GM UART in an aftermarket SAE J2534 interface intended for use by independent automotive service facilities to program GM UART ECUs in General Motors vehicles.
2015-04-15
WIP Standard
J1939/11
This document defines a physical layer having a robust immunity to EMI and physical properties suitable for harsh environments. CAN controllers are available which support the CAN Flexible Data Rate Frame Format. These controllers, when used on SAE J1939-11 networks, must be restricted to use only the Classical Frame Format compliant to ISO 11898-1:2015. These SAE Recommended Practices are intended for light- and heavy-duty vehicles on- or off-road as well as appropriate stationary applications which use vehicle derived components (e.g., generator sets). Vehicles of interest include but are not limited to: on- and off-highway trucks and their trailers; construction equipment; and agricultural equipment and implements.
CURRENT
2015-04-09
Standard
J2847/2_201504
This SAE Recommended Practice SAE J2847-2 establishes requirements and specifications for communication between Plug-in Electric Vehicle (PEV) and the DC Off-board charger. Where relevant, this document notes, but does not formally specify, interactions between the vehicle and vehicle operator. This document applies to the off-board DC charger for conductive charging, which supplies DC current to the Rechargable Energy Storage System (RESS) of the electric vehicle through a SAE J1772™ coupler. Communications will be on the SAE J1772 Pilot line for PLC communication. The details of PowerLine Communications (PLC) are found in SAE J2931/4. The specification supports DC energy transfer via Forward Power Flow (FPF) from source to vehicle. SAE has published multiple documents relating to PEV and vehicle-to-grid interfaces. The various document series are listed below, with a brief explanation of each.
2015-03-24
WIP Standard
J2945/2
DSRC interface requirements for V2V Safety Awareness applications, including detailed Systems Engineering documentation (needs and requirements mapped to appropriate message exchanges)
2015-01-27
WIP Standard
J2945/6
This standard defines the data exchange will be necessary for coordinated maneuvers and that definition of the categories should start with differentiating Platooning and CACC, then determining message sets and performance to realize cooperative vehicles. It is an important step in realizing the role of vehicle-to-x communication with automated vehicles.
Viewing 1 to 30 of 63

Filter

  • Standard
    63