Criteria

Text:
Content:
Display:

Results

Viewing 31 to 57 of 57
HISTORICAL
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.
HISTORICAL
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.
CURRENT
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.
CURRENT
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. This document describes the Thin Transport Layer of the IDB, as shown in Figure 1.
HISTORICAL
2002-02-22
Standard
J2540/2_200202
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.
CURRENT
2002-02-22
Standard
J2539_200202
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.
CURRENT
2002-02-07
Standard
J2395_200202
This SAE Recommended Practice applies to both Original Equipment Manufacturer (OEM) and aftermarket ITS message-generating systems for passenger vehicles and heavy trucks. The recommended practice describes the method for prioritizing ITS in-vehicle messages and/or displayed information based on a defined set of criteria. Each criterion has a fixed number of levels that are used to rate/rank a given message or information item to determine its prioritization value. The prioritization value is used to determine the priority in which simultaneous, or overlapping, in-vehicle messages are presented to the driver.
CURRENT
2002-01-23
Standard
J2540/3_200201
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.
CURRENT
2001-12-26
Standard
J1760_200112
The scope of this SAE Recommended Practice is to require the use of the same Security Services as defined by the International Standard ISO/CD 15764, modified by the Class of Security as determined by the resource provider and referenced in Table 1, Extended Data Link Security References.
CURRENT
2001-12-19
Standard
J2590_200112
This SAE Recommended Practice describes the power mode requirements for in-vehicle networks that conform to the Automotive Multimedia Interface Collaboration (AMI-C) specifications. These networks include, but are not limited to, the IDB-C (SAE J2366), IDB-1394, and MOST. This version of the document covers primarily IDB-C and may be revised when the PMODE requirements for the other networks are more fully developed by AMI-C.
CURRENT
2001-11-27
Standard
J2366/1_200111
This SAE Recommended Practice details the Physical Layer of the Intelligent Transportation Systems (ITS) Data Bus on CAN (IDB-C), which is generally intended for in-vehicle use. It has been developed by the ITS Data Bus (IDB) Physical Layer Subcommittee of the IDB Committee. The objectives of the subcommittee are to develop information reports, recommended practices and standards concerned with the requirements, design, and usage of devices that communicate electronic signals and control information among ITS related components within the vehicle environment. The IDB-C 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. This document describes the Physical Layer of the IDB-C, as shown in Figure 1. The Physical Layer of the IDB-C incorporates the CAN 2.0B specification per SAE J2284-2, with modifications as noted in this document.
CURRENT
2001-11-27
Standard
J2366/1L_200111
This SAE Recommended Practice describes the Low Impedance Stereo Audio (LISA) bus, which may be used in conjunction with the Physical Layer of the IDB-C, as described in SAE J2366-1. The audio arbitration messages used to control access to the LISA bus are specified in SAE J2366-7. The IDB-C is a non-proprietary virtual token passing bus, designed to allow disparate consumer, vehicle, and commercial electronic components to communicate and share information.
CURRENT
2001-11-27
Standard
J2366/2_200111
This SAE Recommended Practice details the Link Layer of the Intelligent Transportation Systems (ITS) Data Bus, which is generally intended for in-vehicle use. The ITS Data Bus (IDB) is a non-proprietary token passing bus, designed to allow disparate consumer, vehicle, and commercial electronic components to communicate and share information across a standard, open data bus. This first version of the IDB is called IDB-C. This Recommended Practice describes the Link Layer of the IDB-C, as shown in Section 1. Below the Link Layer of the IDB-C is the CAN 2.0B Link Layer. The Physical Layer of the IDB-C incorporates the Physical Layer as specified by SAE J2366-1 and J2590. The IDB-C Link Layer is logically divided into two functional sub-layers, viz., Logical Link Control (LLC) and Media Access Control (MAC). However, these are logical groupings that re-use some of the same bits within the CAN 2.0B frame for efficiency.
CURRENT
2000-04-15
Standard
J2373_200004
This SAE Information Report describes requirements gathering workshops for Public Sector use of ITS Referencing Datums.
CURRENT
2000-03-24
Standard
J2369_200003
This SAE Standard outlines the US standard for sending Advanced Traveler Information Services (ATIS) messages over various Bandwidth Reduced Media (BRM). It specifies the “over the air” format and method for such data messages at a bit level. The methodology allows a cooperative sharing of the media’s total bandwidth with other non-ATIS data services. It allows for further expansion to other ATIS messages such as transit schedules and weather use. It uses a common directory of messages to divide out those messages which are the subject of this specification from others. It is built upon the concept of “waveform neutrality” in that it can be hosted by a wide variety of media often found in the delivery of wireless data services (although it is also useful for wire line applications). This message set is incorporated into each medium (“host medium”) by a formatting process specific to each media. A graphical overview ofthis process is shown in Figure 1.
CURRENT
1999-12-15
Standard
J1746_199912
This SAE Standard is intended to be used for the communication of spatial data references between central sites and mobile vehicles on roads. References can be communicated from central site to vehicles, or from vehicles to central sites. The document may also be used where appropriate by other ITS applications requiring location references between data sets.
CURRENT
1999-12-14
Standard
J2372_199912
This SAE Information Report describes results of testing of the SAE J1746 ISP-Vehicle Standard for the communication of spatial data references between central sites and mobile vehicles on roads. Testing was performed by the Oak Ridge National Laboratory and its contractors, resulting in a document from which this Information Report has been extracted. Tests were performed by computer analysis and corroborated by field tests with a mobile vehicle.
HISTORICAL
1999-12-01
Standard
ARP5021
This document provides guidance for oxygen cylinder installation on commercial aircraft based on rules and methods practiced in aerospace industry and as far as applicable in other associations. It covers considerations to be taken 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.
HISTORICAL
1999-12-01
Standard
ARP1967A
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.
HISTORICAL
1999-11-27
Standard
J2354_199911
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.). The purpose of this SAE Standard is to enable the rapid development of the market for ATIS products and services.
CURRENT
1999-10-19
Standard
J2353_199910
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.
CURRENT
1999-09-28
Standard
J2313_199909
This SAE Standard describes the interface between an on-vehicle Mayday detection, reporting system and the off-vehicle response center that will manage the response to the vehicle's call for assistance. The automatic detection and reporting by either the intelligent vehicle itself or by the intelligent roadway of a vehicle that is disabled or involved in an accident, [referred to as Automatic Mayday], is one of the key services identified by the ITS America program plan road map. This effort has been identified, as STD SAE J2313 in recent DOT-FHWA efforts to advance needed National standards. This document primarily addresses the responsibilities of a vehicle in detecting and reporting such an event. Equipment suites on each vehicle will vary widely, as will the communications channel employed to report the incident.
HISTORICAL
1995-12-01
Standard
J1761_199512
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.
HISTORICAL
1995-07-01
Standard
J1763_199507
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.
CURRENT
1969-03-01
Standard
J345_196903
This SAE Recommended Practice defines the best known techniques for evaluating peak and locked wheel braking traction. It covers an important phase of tire braking traction, namely, the wet or dry pavement straight ahead conditions. However, this is but a small portion of the whole field of tire traction. As test procedures are established for other phases of this complex study, additional supplementary procedures will be written. A discussion of this entire subject is contained in Appendix B to this recommended practice.
HISTORICAL
1969-03-01
Standard
J345A_196903
This SAE Recommended Practice defines the best known techniques for evaluating peak and locked wheel braking traction. It covers an important phase of tire braking traction, namely, the wet or dry pavement straight ahead conditions. However, this is but a small portion of the whole field of tire traction. As test procedures are established for other phases of this complex study, additional supplementary procedures will be written. A discussion of this entire subject is contained in Appendix B to this recommended practice.
HISTORICAL
1968-06-01
Standard
J345_196806
This SAE Recommended Practice defines the best known techniques for evaluating peak and locked wheel braking traction. It covers an important phase of tire braking traction, namely, the wet or dry pavement straight ahead conditions. However, this is but a small portion of the whole field of tire traction. As test procedures are established for other phases of this complex study, additional supplementary procedures will be written. A discussion of this entire subject is contained in Appendix B to this recommended practice.
Viewing 31 to 57 of 57