Browse Topic: Driving automation

Items (371)
Automated vehicles, in the form we see today, started off-road. Ideas, technologies, and engineers came from agriculture, aerospace, and other off-road domains. While there are cases when only on-road experience will provide the necessary learning to advance automated driving systems, there is much relevant activity in off-road domains that receives less attention. Implications of Off-road Automation for On-road Automated Driving Systems argues that one way to accelerate on-road ADS development is to look at similar experiences off-road. There are plenty of people who see this connection, but there is no formalized system for exchanging knowledge. Click here to access the full SAE EDGETM Research Report portfolio.
Vehicles equipped with Level 4 and 5 autonomy will need to be tested according to regulatory standards (or future revisions thereof) that vehicles with lower levels of autonomy are currently subject to. Today, dynamic Federal Motor Vehicle Safety Standards (FMVSS) tests are performed with human drivers and driving robots controlling the test vehicle’s steering wheel, throttle pedal, and brake pedal. However, many Level 4 and 5 vehicles will lack these traditional driver controls, so it will be impossible to control these vehicles using human drivers or traditional driving robots. Therefore, there is a need for an electronic interface that will allow engineers to send dynamic steering, speed, and brake commands to a vehicle. This paper describes the design and implementation of a market-ready Automated Driving Systems (ADS) Test Data Interface (TDI), a secure electronic control interface which aims to solve the challenges outlined above. The interface consists of a communication port
Zagorski, ScottNguyen, AnHeydinger, GaryAbbey, Howard
In this work, we present a lightweight pipeline for robust behavioral cloning of a human driver using end-to-end imitation learning. The proposed pipeline was employed to train and deploy three distinct driving behavior models onto a simulated vehicle. The training phase comprised of data collection, balancing, augmentation, preprocessing, and training a neural network, following which the trained model was deployed onto the ego vehicle to predict steering commands based on the feed from an onboard camera. A novel coupled control law was formulated to generate longitudinal control commands on the go based on the predicted steering angle and other parameters such as the actual speed of the ego vehicle and the prescribed constraints for speed and steering. We analyzed the computational efficiency of the pipeline and evaluated the robustness of the trained models through exhaustive experimentation during the deployment phase. We also compared our approach against state-of-the-art
Samak, Tanmay VilasSamak, Chinmay VilasKandhasamy, Sivanathan
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 document describes machine-to-machine (M2M) communication to enable cooperation between two or more participating entities or communication devices possessed or controlled by those entities. The cooperation supports or enables performance of the dynamic driving task (DDT) for a subject vehicle with driving automation feature(s) engaged. Other participants may include other vehicles with driving automation feature(s) engaged, shared road users (e.g., drivers of manually operated vehicles or pedestrians or cyclists carrying personal devices), or road operators (e.g., those who maintain or operate traffic signals or workzones). Cooperative driving automation (CDA) aims to improve the safety and flow of traffic and/or facilitate road operations by supporting the movement of multiple vehicles in proximity to one another. This is accomplished, for example, by sharing information that can be used to influence (directly or indirectly) DDT performance by one or more nearby road users
Cooperative Driving Automation(CDA) Committee
This SAE Information Report classifies and defines a harmonized set of safety principles intended to be considered by ADS and ADS-equipped vehicle development stakeholders. The set of safety principles herein is based on the collection and analysis of existing information from multiple entities, reflecting the content and spirit of their efforts, including: SAE ITC AVSC Best Practices CAMP Automated Vehicle Research for Enhanced Safety - Final Report RAND Report - Measuring Automated Vehicle Safety: Forging a Framework U.S. DOT: Automated Driving Systems 2.0 - A Vision for Safety Safety First for Automated Driving (SaFAD) UNECE WP29 amendment proposal UNECE/TRANS/WP.29/GRVA/2019/13 On a Formal Model of Safe and Scalable Self-Driving Cars (Intel RSS model) SAE J3018 This SAE Information Report provides guidance for the consideration and application of the safety principles for the development and deployment of ADS and ADS-equipped vehicles. This SAE Information Report is not intended to
On-Road Automated Driving (ORAD) committee
This document describes [motor] vehicle driving automation systems that perform part or all of the dynamic driving task (DDT) on a sustained basis. It provides a taxonomy with detailed definitions for six levels of driving automation, ranging from no driving automation (Level 0) to full driving automation (Level 5), in the context of [motor] vehicles (hereafter also referred to as “vehicle” or “vehicles”) and their operation on roadways: Level 0: No Driving Automation Level 1: Driver Assistance Level 2: Partial Driving Automation Level 3: Conditional Driving Automation Level 4: High Driving Automation Level 5: Full Driving Automation These level definitions, along with additional supporting terms and definitions provided herein, can be used to describe the full range of driving automation features equipped on [motor] vehicles in a functionally consistent and coherent manner. “On-road” refers to publicly accessible roadways (including parking areas and private campuses that permit
On-Road Automated Driving (ORAD) committee
Items per page:
1 – 50 of 371