This section describes how to build events in the full vehicle model with advanced driver. The new event user interface
is supported only for models with advanced driver. The interface exports .adf and .xml files and submits them to MotionSolve. Files can be edited or updated in the Event Editor. Sixteen event types are supported.
Controllers form the core of the driver. The Controller Library has various basic controllers its arsenal as of now and
will be enhanced with many advanced controllers in the near future.
Altair Driver is a simple driver model. This is used in all MotionView and MotionSolve vehicle events. The controller can predict the future road path based on the current vehicle state, has knowledge of
the vehicle dynamics, and has access to user-defined driver parameters.
Driver can be loaded using the Task Wizard of MDLLIB. Driver has some special requirements to interface with the vehicle
model. These requirements are resolved automatically if the vehicle model is built using the Full vehicle with advanced
driver option in the Model Wizard in MDLLIB.
The TeimOrbit reader can parse various entities to get data from the ADF file. These entities include: attributes, blocks,
subblocks, tables, units and comments.
Driver can be loaded using the Task Wizard of MDLLIB. Driver has some special requirements to interface with the vehicle
model. These requirements are resolved automatically if the vehicle model is built using the Full vehicle with advanced
driver option in the Model Wizard in MDLLIB.
There should be only one option for the full vehicle with
advanced driver.
Altair Driver Analysis: At the end of the selection procedure and after the
FINISH button is clicked, the Driver analysis with the driver panel should
appear.