Search
Advanced Search
of the following are true
(
)

Results

Items (211,947)
This SAE Recommended Practice covers passive torque biasing axle and center differentials used in passenger car and light truck applications. Differentials are of the bevel gear, helical gear, and planetary types, although other configurations are possible.
Drivetrain Standards Committee
This SAE Recommended Practice covers the design and application of a 120 VAC single phase engine based auxiliary power unit or GENSET. This document is intended to provide design direction for the single phase nominal 120 VAC as it interfaces within the truck 12 VDC battery and electrical architecture providing power to truck sleeper cab hotel loads so that they may operate with the main propulsion engine turned off.
Truck and Bus Electrical Systems Committee
This material type has resistance to hot air, but generally has poor resistance to fuels and lubricants, but usage is not limited to such applications. Each application should be considered separately. This material type has a typical service temperature range of -85 to 500 °F (-65 to 260 °C). The operating temperature range of the material is a general temperature range, but the presence of particular fluids and design parameters may modify this range. Recommendations on the material selection are based on available technical data and are offered as suggestions only. Each user should make his own tests to determine the suitability for his own particular use.
A-6C2 Seals Committee
This specification provides dimensional standards for crimp type contact wire barrel design and is a replacement for MS3190. Some wire barrel designs may exist in AS39029 but are not considered approved for future use, therefore, will not appear in this specification. The crimp barrel sizes listed in this document have been standardized in AS39029 and AS22520 specifications, tools and contacts are available to support these listed sizes. These crimp barrel requirements shall be used for any contact, regardless of whether it is a standard or non-standard contact configuration. The specification lists details for three types of wire barrels: A, B, and C. Wire barrel type A is not recommended for new design. Table 4 lists each AS39029 detail sheet wire barrel type.
AE-8C1 Connectors Committee
It is expected that Level 4 and 5 automated driving systems-dedicated vehicles (ADS-DVs) will eventually enable persons to travel at will who are otherwise unable to obtain a driver's license for a conventional vehicle, namely, persons with certain visual, cognitive, and/or physical impairments. This information report focuses on these disabilities, but also provides guidance for those with other disabilities. This report is limited to fleet operated on-demand shared mobility scenarios, as this is widely considered to be the first way people will be able to interact with ADS-DVs. To be more specific, this report does not address fixed route transit services or private vehicle ownership. Similarly, this report is focused on road-worthy vehicles; not scooters, golf carts, etc. Lastly, this report does not address the design of chair lifts, ramps, or securements for persons who use wheeled mobility devices (WHMD) (e.g., wheelchair, electric cart, etc.), as these matters are addressed by
On-Road Automated Driving (ORAD) Committee
The demonstrated architectural model and associated graphical techniques defined herein were developed to provide a simple method of visualizing the general functional operation or behavior of a Distributed Embedded System with a strong emphasis on representing system time characteristics.
Embedded Software Standards Committee
The lane departure warning (LDW) system is a warning system that alerts drivers if they are drifting (or have drifted) out of their lane or from the roadway. This warning system is designed to reduce the likelihood of crashes resulting from unintentional lane departures (e.g., run-off-road, side collisions, etc.). This system will not take control of the vehicle; it will only let the driver know that he/she needs to steer back into the lane. An LDW is not a lane-change monitor, which addresses intentional lane changes, or a blind spot monitoring system, which warns of other vehicles in adjacent lanes. This informational report applies to original equipment manufacturer and aftermarket LDW systems for light-duty vehicles (gross vehicle weight rating of no more than 8500 pounds) on relatively straight roads with a radius of curvature of 500 m or more and under good weather conditions.
Advanced Driver Assistance Systems (ADAS) Committee
This SAE Recommended Practice establishes a uniform, powered vehicle test procedure and minimum performance requirement for lane departure warning systems used in highway trucks and buses greater than 4546 kg (10000 pounds) gross vehicle weight (GVW). Systems similar in function but different in scope and complexity, including lane keeping/lane assist and merge assist, are not included in this document. This document does not apply to trailers, dollies, etc. This document does not intend to exclude any particular system or sensor technology. This document will test the functionality of the lane departure warning system (LDWS) (e.g., ability to detect lane presence and ability to detect an unintended lane departure), its ability to indicate LDWS engagement, its ability to indicate LDWS disengagement, and its ability to determine the point at which the LDWS notifies the human machine interface (HMI) or vehicle control system that a lane departure event is detected. Moreover, this
Truck and Bus Automation Safety Committee
This SAE Recommended Practice establishes a test procedure for the evaluation of lane departure warning (LDW), lane keeping assistance (LKA), and lane centering assistance systems used in passenger vehicles and light trucks. This test procedure does not intend to exclude any particular system or sensing technology. The recommended practice can be used to test the functionality and performance of LDW, LKA, and lane centering assistance systems by assessing their ability to (1) warn (LDW) or control (LKA, lane centering assistance) in response to an unintended lane departure, and (2) the ability to indicate a system disengagement. The human machine interface (HMI) is not addressed herein but is considered in SAE J2808. The recommended practice specifies lane markers to enable lane departure testing, or road edges, to enable testing of road departure mitigation systems. The document is separated into two tiers. Tier One establishes a recommended minimum set of performance criteria for LDW
Active Safety Systems Standards Committee
This specification covers a titanium alloy in the form of sheet and strip up to and including 0.125 inch (3.18 mm) in nominal thickness.
AMS G Titanium and Refractory Metals Committee
AIR1608 ESTIMATION OF TOTAL ERROR IN ALTIMETRY proposes a method of estimating overall error of altimetry in order to provide a basis for safe vertical separation of aircraft.
A-4 Aircraft Instruments Committee
This standard defines the mechanical interface and specifies provisions for the electrical and environmental connectors between the host aircraft (“platform”) and a turreted electro-optic/infrared (EO/IR) sensor.
AS-1C Avionic Subsystems Committee
These recommendations cover the mechanical and electrical installation and installation test procedures for automatic pilots of the type normally used in transport type aircraft. The material in this ARP does not supercede any airworthiness requirement in the Civil Air Regulations.
A-4 Aircraft Instruments Committee
This SAE Aerospace Recommended Practice (ARP) sets forth design and operational recommendations concerning the human factors issues and criteria for cockpit display of traffic information systems. The visual and aural characteristics are covered for both the alerting components and traffic depiction/situation components. The display system may contain any one or a combination of these components Although the system functionality assumed for this document exemplifies fixed-wing aircraft implementation, the recommendations do not preclude other aircraft types. The recommendations contained in this document address both near and far term technology directed toward providing in flight traffic awareness, although the present version remains primarily focused on near term applications. Since this document provides recommendations, the guidance is provided in the form of “should” statements as opposed to the “shall” statements that appear in standards and requirements. The assumptions about
G-10EAB Executive Advisory Group
This document defines a set of standard application layer interfaces called JAUS HMI Services. JAUS Services provide the means for software entities in an unmanned system or system of unmanned systems to communicate and coordinate their activities. The HMI Services represent the platform-independent Human Machine Interface (HMI) capabilities commonly found across all domains and types of unmanned systems. Five services are defined in this document: Drawing Pointing Device Keyboard Digital Control Analog Control Each service is described by a JAUS Service Definition (JSD) which specifies the message set and protocol required for compliance. Each JSD is fully compliant with the JAUS Service Interface Definition Language (JSIDL) [AS5684].
AS-4JAUS Joint Architecture for Unmanned Systems Committee
This Aerospace Recommended Practice (ARP) provides guidance on developing requirements for systems that include Integrated Vehicle Health Management (IVHM) capability [REF1], [REF18]. IVHM is increasingly being implemented on military and commercial aircraft. Some examples include the F-35 Joint Strike Fighter (JSF) [REF1] and the AH-64 Apache [REF3] in the military domain, and the B787 [REF4] and A350XWB [REF5] in the commercial domain. This document provides a systematic approach for developing requirements related to the IVHM capabilities of a vehicle system. This document is not intended to repeat general guidelines on good requirements writing [REF13], [REF20]. Instead, the focus is on the unique elements, which need to be considered for IVHM and the resulting specific guidelines that will help define better requirements and hence better systems. The multi-faceted nature of IVHM should include the process of requirements gathering. Therefore, this document presents some guidance
HM-1 Integrated Vehicle Health Management Committee
This standard defines a generic set of electrical interfaces between a host aircraft (“platform”) and an electro-optic/infrared (EO/IR) sensor. This includes connectors, cabling, fiber optics, signals, and power.
AS-1C Avionic Subsystems Committee
This SAE Aerospace Standard (AS) covers automatic pilots intended for use on aircraft to automatically operate the primary and trim aerodynamic controls to maintain stable flight and/or to provide maneuvering about any of the three axes through servo control. Automatic control functions essential for primary or augmented flight control are excluded.
A-4 Aircraft Instruments Committee
This document addresses the operational safety and human factors aspects of unauthorized laser illumination events in navigable airspace. The topics addressed include operational procedures, training, and protocols that flight crew members should follow in the event of a laser exposure. Of particular emphasis, this document outlines coping strategies for use during critical phases of flight. Although lasers are capable of causing retinal damage, most laser cockpit illuminations, to date, has been relatively low in irradiance causing primarily startle reactions, visual glare, flashblindness and afterimages. Permanent eye injuries from unauthorized laser exposures have been extremely rare. This document describes pilot operational procedures in response to the visual disruptions associated with low to moderate laser exposures that pilots are most likely to encounter during flight operations. With education and training, pilots can take actions that safeguard both their vision and the
G-10OL Operational Laser Committee
Following a number of high-visibility collisions between aircraft on the airport surface, overall taxi operations have been brought under greater scrutiny. In addition, observation of taxi operations and the results of associated research programs have revealed that the efficiency of taxi operations could be significantly improved with available technologies and by applying a human centered design approach. Surface operations displays have been tested in prototype form and a number of manufacturers are moving toward product definition. This document provides guidance on the design of elements, which may be part of surface operations displays whose objectives would be to enhance safety and to improve overall efficiency of aircraft operations on the airport surface. Such efficiency increases should be realized not only in day-to-day operations, but should also be manifested in training for surface operations. This document sets forth functional and design recommendations concerning the
G-10EAB Executive Advisory Group
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 (informational, pre-trip and en route), all types of travelers (drivers, passengers, personal devices, computers, other servers), all categories of information, and all platforms for delivery of information (in-vehicle, portable devices, kiosks, etc.).
V2X Core Technical Committee
This document specifies the minimum recommendations for Blind Spot Monitoring System (BSMS) operational characteristics and elements of the user interface. A visual BSMS indicator is recommended. BSMS detects and conveys to the driver via a visual indicator the presence of a target (e.g., a vehicle), adjacent to the subject vehicle in the “traditional” Adjacent Blind Spot Zone (ABSZ). The BSMS is not intended to replace the need for interior and exterior rear-view mirrors or to reduce mirror size. BSMS is only intended as a supplement to these mirrors and will not take any automatic vehicle control action to prevent possible collisions. While the BSMS will assist drivers in detecting the presence of vehicles in their ABSZ, the absence of a visual indicator will not guarantee that the driver can safely make a lane change maneuver (e.g., vehicles may be approaching rapidly outside the ABSZ area). This document applies to original equipment and aftermarket BSMS systems for passenger
Advanced Driver Assistance Systems (ADAS) Committee
This document provides a list of data elements and event triggers for recording of event data relevant to crash investigations for heavy vehicles. The list of data elements includes recommended source(s) and formatting.
Truck and Bus Event Data Recorder Committee
This document describes an SAE Recommended Practice for Automatic Emergency Braking (AEB) system performance testing which: establishes uniform vehicle level test procedures identifies target equipment, test scenarios, and measurement methods identifies and explains the performance data of interest does not exclude any particular system or sensor technology identifies the known limitations of the information contained within (assumptions and “gaps”) is intended to be a guide toward standard practice and is subject to change on pace with the technology is limited to “Vehicle Front to Rear, In lane Scenarios” for initial release This document describes the equipment, facilities, methods and procedures needed to evaluate the ability of Automatic Emergency Braking (AEB) systems to detect and respond to another vehicle, in its immediate forward path, as it is approached from the rear. This document does not specify test conditions (e.g., speeds, decelerations, headways, etc.). Those values
Active Safety Systems Standards Committee
This document is the Architecture Description (AD) for the SAE Unmanned Systems (UxS) Control Segment (UCS) Architecture Library Revision B or, simply, the UCS Architecture. The architecture is expressed by a library of publications as referenced herein. The other SAE publications in the UCS Architecture Library Revision B are AS6513B and AS6518B. The library also includes the government-owned Autonomous Ground Vehicle Reference Architecture (AGVRA) Data Model Framework Version 3.1A.
AS-4UCS Unmanned Systems Control Segment Architecture
This recommended practice is applicable to reciprocating engines powering unmanned aerial vehicles (UAV) having rated power values less than 22.4 kW, and which are not to be used for human transport.
null, null
Create and publish a list of terms relevant to electrified propulsion aircraft with summary text descriptions. The terms and descriptions will not provide full explanations, diagrams, and other detailed technical descriptions. These deeper descriptions will be addressed in other documents. This document defines the relevant terms and abbreviations related to the design, development, and use of electrified propulsion in aircraft. This definition is provided to enable a consistent use of technical language throughout the standards developed by the E-40 committee.
E-40 Electrified Propulsion Committee
This SAE Recommended Practice provides common data output formats and definitions for a variety of data elements that may be useful for analyzing the performance of automated driving system (ADS) during an event that meets the trigger threshold criteria specified in this document. The document is intended to govern data element definitions, to provide a minimum data element set, and to specify a common ADS data logger record format as applicable for motor vehicle applications. Automated driving systems (ADSs) perform the complete dynamic driving task (DDT) while engaged. In the absence of a human “driver,” the ADS itself could be the only witness of a collision event. As such, a definition of the ADS data recording is necessary in order to standardize information available to the accident reconstructionist. For this purpose, the data elements defined herein supplement the SAE J1698-1 defined EDR in order to facilitate the determination of the background and events leading up to a
Event Data Recorder Committee
This SAE Information Report develops a concept of operations (ConOps) to evaluate a cooperative driving automation (CDA) Feature for occluded pedestrian collision avoidance using perception status sharing. It provides a test procedure to evaluate this CDA Feature, which is suitable for proof-of-concept testing in both virtual and test track settings.
Cooperative Driving Automation(CDA) Committee
This document provides a high-level ontology and lexicon for describing on-road ADS-operated vehicle behavioral competencies and driving maneuvers that comprise routine/normal performance of the complete DDT, as defined in SAE J3016. It provides definitions of behavior, maneuver, scenario, and scene. This initial high-level lexicon and ontology are developed for ADS driving behaviors, including considerations for hierarchy of behaviors, and relationships among maneuvers, operational design domain (ODD) elements, and object and event detection and response (OEDR). Considerations for describing scenarios using this lexicon and ontology are discussed. This document describes ADS-operated vehicle motion control maneuvers during routine/normal operation. Maneuvers of other road users are not evaluated. This document assumes left-hand drive vehicles and road infrastructure. Applicability to right-hand drive vehicles and roadway infrastructure would require adjustment to such vehicles and
On-Road Automated Driving (ORAD) Committee
Items per page:
1 – 50 of 211947