ADAS: Moving Objects and Sensors

CarSim,TruckSim, and BikeSim support Movng Objects and Sensors that are helpful in simulations involving advanced driver assistance systems (ADAS) and autonomous vehicles (AVs).

Traffic
ADAS: Part 1, Multiple Moving Objects. This 6-min video shows how to add traffic vehicles. July 2020.
Sensors and signs
ADAS: Part 2, Sensors, Signs, and the Symbol Stack. This 7-min video shows how the built-in ADAS Sensors work with traffic signs. July 2020.
Pedestrians
ADAS: Part 3, Animated Pedestrians, Animals, and Bicycles. This 7-min video pedestrians with animated walking motions, and bicycles with animated pedaling, and leaning in a turn. July 2020.
collision
ADAS: Part 4, Sensing Walls, Buildings, and the Ego Vehicle. This 6-min video shows polygonal shapes, occlusion, and collision with the ego vehicle. July 2020.
Multiple Vehicles
ADAS: Part 5, Multiple Vehicles. This 9-min video shows three options for simulating multiple vehicles interacting. July 2020.

Traffic and Target Objects

BikeSim, CarSim, and TruckSim include up to 200 objects whose locations and motions are independent of the simulated vehicle. These objects can represent other vehicles, fixed objects (trees, buildings), pedestrians, animals, paint markings, and other objects of interest for ADAS scenarios.

A VS Moving Object is something with a location and orientation that might be of interest when simulating a vehicle in a VehicleSim product. As a minimum, the object is represented by a set of variables that define a location and orientation for animation or communication with other software. When combined with ranging sensors, the object becomes a target that can be detected.

Advanced users can control the motions using built-in options, with VS Commands, or with external models (e.g., Simulink). They can also be attached to vehicle sprung masses to make the vehicle detectible.

If using custom controls, each object can be located in the XY plane using either X and Y global coordinates, or using a station coordinate S along with a specified Reference Path ID. Vertical information can be set directly, or based on S and L coordinate for a specified VS Road.

Moving objects can be linked to 3D objects with their own embedded animations, such as walking pedestrians or pedaling bicyclists.

If there are ADAS sensors in the simulation, each object has a shape that influences the detection. Shapes may be rectangular, circular, a straight segment (with limited visibility, used for signs), or polygonal.

ADAS Sensors

BikeSim, CarSim, and TruckSim support up to 99 ADAS sensors that detect the moving objects. An extended license is needed in order to use ADAS sensors. However, moving objects are available with any license.

Each sensor has a location fixed in a part of the simulated vehicle, with a designated aiming direction and sensitivity to radiation pattern and range. Alternatively, sensors may be located in moving objects. (One application for this is to detect a point of collision with a vehicle that has an attached polygonal target shape.)

The main outputs of interest are variables that link a sensor to a detected object. Each possible combination of sensor and target object has an associated set of 24 detection variables that can be used in user-defined models to simulate advanced intervention controls. The detection variables include bearing angles, distances, coordinates and speed components in the sensor coordinate system, user-defined variables, etc.

occlusion
The sensing of object points takes occlusion (blocking) into account using rectangular or circular shapes. Click for full size.
Euro NCAP
Using CarSim to Simulate Euro NCAP AEB VRU Tests. This 6-min video some of the EURO NCAP Autonomous Emergency Braking (AEB) Vulnerable Road User (VRU) tests. July 2020.
Contact Us
Subscribe to Newsletter