Browse Topic: Level 4 (High driving automation)
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
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
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
Unsettled Topics in Automated Vehicle Data Sharing for Verification and Validation Purposes discusses the unsettled issue of sharing the terabytes of driving data generated by Automated Vehicles (AVs) on a daily basis. Perception engineers use these large datasets to analyze and model the automated driving systems (ADS) that will eventually be integrated into future “self-driving” vehicles. However, the current industry practices of collecting data by driving on public roads to understand real-world scenarios is not practical and will be unlikely to lead to safe deployment of this technology anytime soon. Estimates show that it could take 400 years for a fleet of 100 AVs to drive enough miles to prove that they are as safe as human drivers.Yet, data-sharing can be developed – as a technology, culture, and business – and allow for rapid generation and testing of the billions of possible scenarios that are needed to prove practicality and safety of an ADS – resulting in lower research
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
Items per page:
50
1 – 50 of 133