Difference between revisions of "Vehicle Automation"

Revision as of 13:25, 7 January 2018

As standard, the miniSim is equipped with two automation functions:

• Lane Following

This function allows the user to define a ‘path’ for the own-vehicle vehicle during scenario authoring in ISAT, and, when engaged, the own-vehicle will follow this path. Lane Follow can be engaged/disengaged manually by the driver or operator, or via scenario trigger. NBy default, this will disengage when the driver starts steering.

• Enhanced ACC

This function allows the driver or scenario to set the desired target speed and follow distance. The system will accelerate the own-vehicle from a standstill, and brake it to a stop as in stop and go traffic.

The Vehicle Automation option provides additional support for the following miniSim functions that allow the user to create and test automated vehicle control algorithms.

• Virtual World API

This is a programmer interface for the miniSim logical road network, or ‘virtual world’. Using this interface, a user’s system can query the scenario determine the location of scenario objects, road and lane locations, and the status of traffic control devices.

• Vehicle Automation Option

The NADS team have developed a set of low-level behaviors that can be activated by the scenario, by manual action, or by a user-designed external subsystem. There are also functions for transfer of control, high-level driving style parameters, and support for existing scenario control triggering systems.

• User-Defined Simulator Subsystem

The minSim supports linking to user-defined subsystems. The ability to link user developed functions to the subsystem has many applications, including the incorporation of active vehicle safety systems or automation functions into the miniSim driver in the loop simulation environment.