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.
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.
The following steps outline how to add an events to the previously built model.
Currently, there are sixteen event types available in the Advanced Driver models:
Constant Radius
Single Lane Change
Double Lane Change
Swept Sine
Straight Line Acceleration
Straight Line Braking
Sinusoidal Steering
BrakeIn Turn
J Turn
Throttle off cornering
Swept Steer
Pulse Steer
Throttle off TurnIn
Step Steer
Power off ln Straight Line
Altair Driver File (if you have a .adf file that needs
to be executed)
Road Course
n-Post
Each event type has different options that need to be addressed. For example, the
Single Lane Change event is explained in the following steps.
Right-click on the Model in the Project Browser and click Add
Events.
The Add Scripted Driver Task dialog is
displayed.
OK
Applies the selected type and closes the window.
Apply
Adds the event without closing the window.
Cancel
Exits the wizard.
Select the Single Lane Change required event type from
the Type drop-down menu.
Click OK.
The Single Lane Change event is added in the Project Browser.
The Event Editor is displayed in the panel area.
Open the Event Editor by right clicking on the event type in the Project Browser and selecting Event
Editor.
Or
Click the Event Editor button in the panel area.
The Single Lane Change event’s parameters are displayed.
Enter the required information in the Parameters section and browse and locate
the required file path in the Output XML File.
Click on the Simulation Settings button to enter the
required data.
This dialog invokes the same options as in the Run panel.
Click on the Output Options button to enter the required
data.
Now after entering all the required data, the event is ready to run. Click the
Run button.
HyperWorksMotionSolve is invoked in the
background.
After the MotionSolve run is completed, close the
window and return to the MotionView interface.
The Event Menu options are explained below:
Build Event
Applies the event to the model and it exports the
.xml and .adf
files.