Criteria

Text:
Sector:
Content:
Display:

Results

Viewing 1 to 29 of 29
WIP Standard
2014-03-24
Inclusion of structured standards inputs received from diverse stakeholders and related applications.
WIP Standard
2014-01-14
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.
Standard
2013-08-14
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.
Standard
2012-09-12
This document defines a physical layer having a robust immunity to EMI and physical properties suitable for harsh environments. 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.
WIP Standard
2010-05-24
This document specifies the minimum communication performance requirements of the DSRC Message message sets, the associated data frames and data elements defined in SAE J2735 DSRC Message Set Dictionary. The document consists of multiple sections. Each section describes a specific message set's requirements. For example, J2945-1 represents Basic Safety Message communication minimum performance requirements.
Standard
2009-11-19
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.
WIP Standard
2009-11-11
All vehicle interface methodology for IntelliDrive devices for new and existing vehicles.
Standard
2008-02-01
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.
Standard
2008-01-23
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.
Standard
2006-12-19
This SAE Recommended Practice is intended as a guide toward standard practice and is subject to chagne to keep pace with experience and technical advances. This SAE Recommended Practice specifies standard message sets, data frames and data elements 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"), communication systems. The scope is limited to specifying initial representative message structure and providing sufficient background information to allow readers to properly interpret the DSRC standards and message definitions from the point of view of an application developer.
Standard
2006-09-18
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.
Standard
2005-12-19
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.
Standard
2004-10-29
The Location Referencing Message Specification (LRMS) standardizes location referencing for ITS applications that require the communication of spatial data references between databases. ITS databases may reside in central sites, vehicles, or devices on or off roads or other transportation links. The LRMS is applicable to both homogeneous (same database) and mixed database environments that may be implemented on wireless or landline networks. While developed for ITS applications, the LRMS may be used for non-ITS applications as well within the field of geographic information processing.
Standard
2004-02-10
This SAE Standard describes standardized medium-independent messages needed by information service providers for Advanced Traveler Information Systems (ATIS). The messages contained herein address all stages of travel (pre-trip and en-route), all types of travelers (drivers, passengers), all categories of information, and all platforms for delivery of information (in-vehicle, portable devices, kiosks, etc.).
Standard
2003-12-02
This SAE Standard presents a set of rules for transforming an Abstract Syntax Notation (ASN.1) message set definition into an eXtensible Markup Language (XML) schema. The result is intended to be a stand-alone XML Schema that is fully consistent with an existing ASN.1 information model. This is a different goal from other related work by other standards bodies developing a set of XML encoding rules for ASN.1 or ASN.1 encodings for XML Schema. These rules were initially developed in order to produce an XML schema for the SAE ATIS standard. While other standards may also choose to use these rules, the rules may not be applicable for all environments. The goal for these transformation rules is twofold. The first goal is to provide a uniform set of such rules that all interested parties can use. The second goal is to use such rules to define an adopted schema for traveler information that reflects the preferred translation of ASN.1 message sets to XML for use by ITS system implementers. The first goal is met by this document.
Standard
2002-07-25
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. Vehicle Architecture for Data Communication Standards Committee voted to cancel document - 7/19/2002 J2058 and J2106 Rationale Per Jack Volk, Vice Chairperson of Vehicle Architecture for Data Communication Standards Committee, document not being used. Information may be contained in other documents, (not necessarily SAE documents).
Standard
2002-07-25
This SAE Standard provides a table of textual messages meeting the requirements for expressing "Radio Data Systems" (RDS) phrases commonly used in the ITS industry. They can be used both over the RDS subcarrier transmission media as part of a 37-bit long "Group 8a message" as well as being used to provide a common content list of phrases used in a wide number of other media and applications. This document SHALL define the normative index values to be used, extending the CEN established list to provide phrases needed by US practitioners. This standard provides non-normative textual phrases which MAY be used by implementers to ensure intelligible results. This document SHALL follow the formats and rules established in SAE J2540 in the expressions, manipulations, and use of such tables. It should be pointed out that within the rules established by this document a variety of final table are all considered "compliant" with the document, and may vary as fits the needs of implementers.
Standard
2002-07-25
This SAE Standard defines methods and messages to efficiently translate sequences of text and other types of data into and out of indexed values and look-up tables for effective transmission. This document defines: Methods and Data Elements for handling indexes and strings in ATIS applications and message sets Message Sets to support the delivery and translations of tables used in such strings Tables of Nationally standardized strings for use in ATIS message descriptions And examples of each in illustrative portions. While developed for ATIS use, the methods defined in this document are useful for any textual strings in any Telematics applications found both in Intelligent Vehicles and elsewhere.
Standard
2002-02-22
This SAE Information Report provides a comparative summary between the various messages found in the SAE ATIS standards work (notably SAE J2313, J2353, J2354, J2369 and J2374) and that found in the GATS standard (Global Automotive Telematics Standard). GATS is a message set meant to be deployed on mobile phone systems based on the GSM (Global System for Mobile Communication) phone system which is being deployed in European markets and which the SAE may need to harmonize with as part of the World Standards activities of TC204. This document provides an overview of the various types of supported messages and how they compare with US terms and messages. Some selected features of the GATS work are recommended for assimilation into the next revision of ATIS standards. No attempt at determining a U.S. policy in this regard is provided. This document seeks to provide the reader familiar with SAE ATIS with a high level overview of technical knowledge of the GATS approach in similar areas.
Standard
2002-01-23
This SAE Standard provides a table of textual messages meeting the requirements for expressing the names of street and roads and some basic building blocks for phrases commonly used in the ITS industry. The tables provided herein are taken from SAE J2369, and follow the rules of SAE J2540 and therefore allow a local representation in various different languages, media expressions, etc. to allow true international use of these phrases. The phrases are predominantly intended to provide a means to express street names including pre and post fixes (North Oak Street is an example name with a prefix "North" and main portion "Oak" and a suffix "Street"). Other phrases exist for other specific specialty areas of ITS, and all such phrases follow a set of encoding and decoding rules outlined in SAE J2540 to ensure that the use of these phrases in messages remain interoperable between disparate types of user equipment. Implementers are cautioned to obtain the most recent set of tables by means of the ITS data registry, a process which involves the SAE and other standards setting organizations and which is intended to maintain and enhance the level of harmonization between ITS standards set by each of the organizations.
Standard
2000-04-10
These Recommended Practices 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 Recommended Practices is to provide an open interconnect system for electronic systems. It is the intention of these Recommended Practices to allow Electronic Control Units to communicate with each other by providing a standard architecture.
Standard
2000-03-21
This series of SAE Recommended Practices was developed to provide an open architecture system for on-board electronic systems. It is the intention of these documents to allow electronic devices to communicate with each other by providing a standard architecture. This particular document describes the Network Interface and Cabling which defines the requirements needed for communicating between devices that are on different segments of the SAE J2496 Transport Area Network. While these recommended practices may be used in retrofitting older vehicles, the primary intent is for implementation in new bus procurements.
Standard
1999-10-19
This SAE Recommended Practice provides a set of core data elements needed by information service providers for Advanced Traveler Information Systems (ATIS). The data dictionary herein provides the foundation for ATIS message sets for all stages of travel (pre-trip and en route), all types of travelers (drivers, passengers), all categories of information, and all platforms for delivery of information (in-vehicle, portable devices, kiosks, etc.). The elements of this document are the basis for the SAE ATIS Message Set Standard J2354 and are entered into the SAE Data Registry for ITS wide coordination.
Standard
1999-10-05
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.
Standard
1996-10-01
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.
Standard
1994-12-01
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. 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 devices to communicate with each other by providing a standard architecture.
Standard
1993-04-01
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. Certain protocol specifics or details are omitted for the sake of brevity.
Standard
1991-04-29
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. Vehicle Architecture for Data Communication Standards Committee voted to cancel document - 7/19/2002 J2058 and J2106 Rationale Per Jack Volk, Vice Chairperson of Vehicle Architecture for Data Communication Standards Committee, document not being used. Information may be contained in other documents, (not necessarily SAE documents).
Viewing 1 to 29 of 29

    Filter

    • Standard
      29