Results
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
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.
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.
This SAE Recommended Practice defines a document for the format of messages and data that is of general value to modules on the data communications link. Included are field descriptions, size, scale, internal data representation, and position within a message. This document also describes guidelines for the frequency of and circumstances in which messages are transmitted. In order to promote compatibility among all aspects of electronic data used in heavy-duty applications, it is the intention of the SAE Truck and Bus Low Speed Communications Network Subcommittee (formerly Data Format Subcommittee) (in conjunction with other industry groups) to develop recommended message formats for: a Vehicle and Component Information—This includes all information that pertains to the operation of the vehicle and its components (such as performance, maintenance, and diagnostic data). b Routing and Scheduling Information—Information related to the planned or actual route of the vehicle. It includes
This document defines a set of standard application layer interfaces called JAUS Mission Spooling 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 Mission Spooling Services represent the physical platform-independent capabilities commonly found across all domains and types of unmanned systems. At present, one service is defined in this document (more services are planned for future versions of this document): Mission Spooler: Stores, manages, and executes lists of tasks The Mission Spooler service is described by a JAUS Service Definition (JSD) which specifies the message set and message protocol required for compliance. The JSD is fully compliant with the JAUS Service Interface Definition Language (JSIDL).
This SAE Standard describes the concept of operation, use cases, and message flows to create a Sensor Sharing Service (SSS). This service enable RSUs and V2X1 vehicles to share information about their localized driving environment. This work defines message structure, V2X entity requirements, and information elements to describe detected objects to facilitate sensor sharing.
This User Guide describes the content of the Rhapsody version of the UCS Architectural Model and how to use this model within the Rhapsody modeling tool environment. The purpose of the Rhapsody version of the UCS Architectural Interface Control Document (ICD) model is to provide a model for Rhapsody users, derived from the Enterprise Architect (EA) model (AIR6515). The AIR6515 EA Model, and by derivation, the AIR6517 Rhapsody Model, have been validated to contain the same content as the AS6518 model for: all UCS ICD interfaces all UCS ICD messages all UCS ICD data directly or indirectly referenced by ICD messages and interfaces the Domain Participant, Information, Service and Non-Functional Properties Models
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, up to a driver selected speed, 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 heavy vehicles (GVWR > 10,000 lbs. or 4,536 kg). Furthermore, this document does not address other 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 Vehicle Collision Warning Systems (FVCWS).
This Recommended Practice defines the technical requirements for a terrestrial-based PNT system to improve vehicle (e.g., unmanned, aerial, ground, maritime) positioning/navigation solutions and ensure critical infrastructure security, complementing GNSS technologies.
This recommended practice describes a process for testing the comprehension of static (i.e., fixed or non-dynamic) symbols for all ground vehicles, for both OEM and aftermarket products. With advancing display technology, it is now possible to display dynamic symbols (e.g., a spinning beach ball to show that a process is ongoing, or a diagram showing energy distribution in hybrid vehicles). Such graphics are outside of the scope of this recommended practice, though extensions of this process may be useful for testing them. However, several symbols which occupy the same space on a display may change state without movement (e.g. play/pause button); these are within the scope of this recommended practice. The process described in this recommended practice includes criteria that are used to identify how well the perceived meaning matches the intended meaning for a representative sample of drivers. The data from this process are analyzed to determine the drivers’ comprehension of the symbol
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.).
This document, the JAUS Compliance and Interoperability Policy (ARP6012), recommends an approach to documenting the complete interface of an unmanned system or component in regard to the application of the standard set. While non-SAE AS-4 JAUS documents are referenced in this ARP they are not within the scope of this document and should be viewed as examples only.
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
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.
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
This SAE Aerospace Standard (AS) specifies a data communications layer for the transport of messages defined by the Joint Architecture for Unmanned Systems (JAUS) or other Software Defined Protocols (SDP). This Transport Specification defines the formats and protocols used for communication between compliant entities for all supported link-layer protocols and media. Although JAUS is the SDP used as the example implemented throughout this document, AS5669 can be used for any SDP that meets the required capabilities. A Software Defined Protocol is defined as an application data interface for communicating between software elements. The SDP is agnostic of the underlying communications protocol and in fact communicates in much the same manner regardless if the communicating entities are collocated in the same memory space or separated by a satellite link.
Items per page:
50
1 – 50 of 211949