Criteria

Text:
Content:
Display:

Results

Viewing 1 to 30 of 50
2014-07-30
WIP Standard
J2364
This document applies to both Original Equipment Manufacturer and aftermarket route-guidance and navigation system functions for passenger vehicles. It establishes two alternative procedures, a static method and an interrupted vision method, for determining which navigation and route guidance functions should be accessible to the driver while the vehicle is in motion. These methods apply only to the presentation of visual information and the use of manual control inputs to accomplish a navigation or route guidance task. The document does not apply to visual monitoring tasks which do not require a manual control input, such as route following. Voice-activated controls or passenger operation of controls are also excluded. There are currently no compelling data that would support the extension of this document to in-vehicle systems other than navigation systems.
2014-05-08
Standard
J1698_201405
This recommended practice describes common definitions and operational elements of Event Data Recorders. The SAE J1698 series of documents consists of the following: • SAE J1698-1 - Event Data Recorder - Output Data Definition; Provides common data output formats and definitions for a variety of data elements that may be useful for analyzing vehicle crash and crash-like events that meet specified trigger criteria. • SAE J1698-2 - Event Data Recorder - Retrieval Tool Protocol; Utilizes existing industry standards to identify a common physical interface and define the protocols necessary to retrieve records stored by light duty vehicle Event Data Recorders (EDRs). • SAE J1698-3 - Event Data Recorder - Compliance Assessment; Defines procedures that may be used to validate that relevant EDR output records conform with the reporting requirements specified in Part 563, Table 1 during the course of FMVSS-208, FMVSS-214 and other applicable vehicle level crash testing.
2014-04-29
Standard
ARP1967B
This SAE Aerospace Recommended Practice (ARP) recommends design and test criteria for reusable shipping and storage containers for aircraft engines and modules, weapon systems and components, etc. The containers are to provide water-vaporproof and physical protection.
2013-04-29
Standard
J1698/1_201304
This Recommended Practice provides common data output formats and definitions for a variety of data elements that may be useful for analyzing vehicle crash and crash-like events that meet specified trigger criteria. The document is intended to govern data element definitions and EDR record format as applicable for light-duty motor vehicle Original Equipment applications.
2013-01-14
Standard
J1698/2_201301
This Recommended Practice utilizes existing industry standards to identify a common physical interface and define the protocols necessary to retrieve records stored by light duty vehicle Event Data Recorders (EDRs). To accomplish this, the SAE J1962 Diagnostic Connector is designated as the primary physical interface for EDR Retrieval Tools. This Recommended Practice is intended to be used for the development of EDR Retrieval Tools. Retrieval tools are intended to interface with light duty vehicles and to produce EDR Record Reports with data element formats specified by SAE J1698-1. Limitations: • This Recommend Practice specifies how EDR records should be imaged, translated, and reported by EDR Retrieval Tools.
2012-08-20
WIP Standard
J1757/1
The scope of this SAE Standard is to provide methods to determine display optical performance in all typical automotive ambient light illumination - with focus on High Ambient Contrast Ratio, which is critical for display legibility in a sunshine environment. It covers indoor measurements and simulated outdoor lighting. It is not the scope of this document to set threshold values for automotive compliance, however some recommended values are presented for reference.
2011-06-01
Standard
ARP5021A
This document provides guidance for oxygen cylinder installation on commercial aircraft based on rules and methods practiced in aerospace industry and applicable in other associations. It covers considerations for oxygen systems from beginning of project phase up to production, maintenance, and servicing. The document is focused on requirements regarding DOT approved oxygen cylinders. However, its basic rules may also be applicable to new development pertaining to use of such equipment in an oxygen environment. For information regarding oxygen cylinders itself, reference should be made to AIR825/12 also.
2009-11-19
Standard
J2540/2_200911
null, null
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.
2007-04-23
Standard
J1757/1_200704
The scope of this SAE Standard is to provide methods to determine display optical performance in all typical automotive ambient light illumination - with focus on High Ambient Contrast Ratio, which is critical for display legibility in a sunshine environment. It covers indoor measurements and simulated outdoor lighting. It is not the scope of this document to set threshold values for automotive compliance, however some recommended values are presented for reference.
2006-11-14
Standard
J2540/2_200611
This SAE Standard provides a table of textual messages meeting the requirements for expressing "International Traveler Information Systems" (ITIS) phrases commonly used in the ITS industry. The tables provided herein 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 for use in the description of traffic related events of interest to travelers and other traffic practitioners. Other phrases exit 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.
2006-05-19
Standard
ARP5943
This SAE Aerospace Recommended Practice (ARP) covers various requirements for airport runway plows, ramp plows, wings, and hitches to be used with various carrier vehicles primarily used to cast snow away from airport airside operational areas, such as runways, ramps, and taxiways. It does not apply to plows and hitches for non-airport snow removal equipment such as highway plows or construction/farm machinery.
2005-03-07
Standard
J1698/1_200503
This document is part of the J1698 document family, and provides the definitions for event-related data items.
2005-02-04
Standard
J1698_200502
This recommended practice aims to establish a common format for displaying and presenting crash-related data recorded and stored within certain electronic components currently installed in many light-duty vehicles. This recommended practice pertains only to the post-download format of such data and is not intended to standardize the format of the data stored within any on-board storage unit, or to standardize the method of data recording, storing, or extraction. Historically, crash data recording technology in light-duty vehicles has developed and evolved based on differing technical needs of manufacturers and their customers without industry standards or government regulation. As a result, wide variations currently exist among vehicle manufacturers regarding the scope and extent of recorded data. For this reason, this recommended practice is not intended to standardize or mandate the recording of any specific data element or to specify a minimum data set.
2004-10-29
Standard
J2266_200410
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.
2004-08-30
Standard
J2678_200408
This document provides the rationale used by the Navigation Function Accessibility Subcommittee (the Subcommittee) for the development and content of a SAE J2364 Recommended Practice: Navigation and Route Guidance Function Accessibility While Driving. It provides both the reasoning for the overall recommended practice as well as each of its elements.
2004-08-10
Standard
J2364_200408
This document applies to both Original Equipment Manufacturer and aftermarket route-guidance and navigation system functions for passenger vehicles. It establishes two alternative procedures, a static method and an interrupted vision method, for determining which navigation and route guidance functions should be accessible to the driver while the vehicle is in motion. These methods apply only to the presentation of visual information and the use of manual control inputs to accomplish a navigation or route guidance task. The document does not apply to visual monitoring tasks which do not require a manual control input, such as route following. Voice-activated controls or passenger operation of controls are also excluded. There are currently no compelling data that would support the extension of this document to in-vehicle systems other than navigation systems.
2004-05-26
Standard
J2540/2_200405
This SAE Standard provides a table of textual messages meeting the requirements for expressing "International Traveler Information Systems" (ITIS) phrases commonly used in the ITS industry. The tables provided herein 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 for use in the description of traffic related events of interest to travelers and other traffic practitioners. Other phrases exit 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.
2004-05-06
Standard
J1698/2_200405
This Recommended Practice is intended to define a common method for determining how to extract Event Data from a motor vehicle, including the Event Data Set needed to output the Event Record of data elements defined in SAE J 1698. It is intended for use by those developing tools for the purpose of Event Data Set extraction. This Recommended Practices aims to utilize existing industry standards to define a common physical interface and the protocols necessary to Event Data Set extraction. To accomplish this, the SAE J 1962 Diagnostics Connector has been designed the primary physical interface and associated industry standard diagnostic protocols have been designated for communications.
2003-12-15
Standard
J2399_200312
Adaptive cruise control (ACC) is an enhancement of conventional cruise control systems that allows the ACC equipped vehicle to follow a forward vehicle at a pre-selected time gap by controlling the engine, power train, and/or service brakes. This SAE Standard focuses on specifying the minimum requirements for ACC system operating characteristics and elements of the user interface. This document applies to original equipment and aftermarket ACC systems for passenger vehicles (including motorcycles). This document does not apply to commercial vehicles. Furthermore, this document does not address future variations on ACC, such as "stop&go" ACC, that can bring the equipped vehicle to a stop and reaccelerate. Future revisions of this document should consider enhanced versions of ACC, as well as the integration of ACC with Forward Collision Warning (FCW).
2003-12-15
Standard
J1698_200312
This recommended practice aims to establish a common format for displaying and presenting crash-related data recorded and stored within certain electronic components currently installed in many light-duty vehicles. This recommended practice pertains only to the post-download format of such data and is not intended to standardize the format of the data stored within any on-board storage unit, or to standardize the method of data recording, storing, or extraction. Historically, crash data recording technology in light-duty vehicles has developed and evolved based on differing technical needs of manufacturers and their customers without industry standards or government regulation. As a result, wide variations currently exist among vehicle manufacturers regarding the scope and extent of recorded data. For this reason, this recommended practice is not intended to standardize or mandate the recording of any specific data element or to specify a minimum data set.
2003-12-02
Standard
J2630_200312
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.
2003-08-29
Standard
J2400_200308
Forward Collision Warning (FCW) systems are onboard systems intended to provide alerts to assist drivers in avoiding striking the rear end of another moving or stationary motorized vehicle. This SAE Information Report describes elements for a FCW operator interface, as well as requirements and test methods for systems capable of warning drivers of rear-end collisions. This Information Report applies to original equipment and aftermarket FCW systems for passenger vehicles including cars, light trucks, and vans. This report does not apply to heavy trucks. Furthermore, this document does not address integration issues associated with adaptive cruise control (ACC), and consequently, aspects of the document could be inappropriate for an ACC system integrated with a FCW system.
2003-05-05
Standard
J1761_200304
This SAE Information Report defines consistent terminology for Intelligent Transportation Systems (ITS). The list of defined terms is followed by a list of acronyms. Certain criteria were used in selecting terms for this document. Terms in widespread use in the ITS community covering significant services, technologies and applications were chosen. This document focuses on terms used in the United States, although it covers aspects of worldwide ITS deployment. This document focuses on automotive applications, which include interfaces to and from the automobile. Later version may include a wider scope. ITS includes a wide array of services, applications, and technologies. The Department of Transportation ITS National program Plan divides ITS into 29 User Services, which are included in this glossary. The User Services range from pre-Trip Travel Planning to Fully Automated Highway Systems.
2003-05-05
Standard
J1763_200304
This SAE Information Report represents an information report on a conceptual ITS architecture and its accompanying protocols from the perspective of Advanced Traveller Information Systems providers and users. While a specific logical and physical architecture for ITS is still in the development stages, this conceptual architecture provides a robust general view of ITS functions and interfaces.
2002-07-25
Standard
J2540/1_200207
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.
2002-07-25
Standard
J2540_200207
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.
2002-07-18
Standard
J1757/1_200207
The scope of this SAE Standard is to provide methods to determine display optical performance in all typical automotive ambient light illumination - with focus on High Ambient Contrast Ratio, which is critical for display legibility in a sunshine environment. It covers indoor measurements and simulated outdoor lighting. It is not the scope of this document to set threshold values for automotive compliance, however some recommended values are presented for reference.
2002-05-10
Standard
J2365_200205
This SAE Recommended Practice applies to both Original Equipment Manufacturer (OEM) and aftermarket route-guidance and navigation system functions for passenger vehicles. This recommended practice provides a method for calculating the time required to complete navigation system-related tasks. These estimates may be used as an aid to assess the safety and usability of alternative navigation and route guidance system interfaces to assist in their design. This document does not consider voice-activated controls, voice output from the navigation system, communication between the driver and others, or passenger operation.
2002-04-12
Standard
J2366/7_200204
NOTE: SAE J2366-7LX--ITS Data Bus Application Message Layer Lexicon is now combined (as an appendix) with SAE J2366-7 to provide for a quicker revision process in the future. This SAE Surface Vehicle Recommended Practice defines an Application Message Layer, which may be used as part of a complete protocol stack with the other protocol layers in the SAE J2366 family. The Application Message Layer provides application message support for devices that are interconnected via a bus or network. Design of the messages and headers has stressed flexibility, expandability, economy (in terms of octets on the bus), and reusability. The Application Message Layer is independent of the underlying network used, and may be used on any network. Sections of this document make specific reference to the use of SAE J2366-7 with other layers of the SAE J2366 family of protocols, and may not apply when SAE J2366-7 is used with other networks.
2002-03-20
Standard
J2366/4_200203
This SAE Recommended Practice details the Thin Transport Layer of the Intelligent Transportation Systems (ITS) Data Bus, which is generally intended for in-vehicle use. The Thin Transport Layer sits between SAE J2366-2 and J2366-7. It provides the handling of such activities as the packetizing of long messages and message reassembly. Design of the messages and headers has stressed economy, in terms of bits within a CAN 2.0B frame. The ITS Data Bus (IDB) is a non-proprietary virtual token passing bus, designed to allow disparate consumer, vehicle, and commercial electronic components to communicate and share information across a standard, open data bus.
Viewing 1 to 30 of 50