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.
A Double lane change event drives the vehicle through a lane change and a return to lane maneuver, attempting to follow
the centerline of the defined lane.
A Swept Sine event simulates a vehicle driving at a constant speed with a sinusoidal steering input of constant magnitude
but increasing frequency applied.
A J-turn event simulates a vehicle response to a large steer in one direction, a dwell time to allow the vehicle to react,
and a large steer in the opposite direction, with an additional reaction time.
A Throttle-off cornering event simulates the dynamics of a vehicle driving a constant radius turn at steady state and
the reaction of the vehicle due to a sudden removal of the drive torque while cornering.
A Throttle-off turn-in event simulates the dynamics of a vehicle driving a constant radius turn at steady state, the reaction
of the vehicle due to a sudden removal of drive torque during the cornering event.
The Road Course event can be used to simulate full vehicle models on the required road profile. The event also provides
a means to study vehicle performance in the areas of durability/fatigue and ride comfort.
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.
Three Joints are used to constrain the vehicle when the event is simulated.
Perpendicular Axes Joint between the Vehicle body and ground body. This is a static
simulation constraint, which is deactivated during the transient part of the
simulation.
Inline Joint between the Vehicle body and ground body. This is also a static
simulation constraint, which is deactivated during the transient part of the
simulation.
The Steering Wheel Joint is used to lock the steering wheel motion during the
simulation.
To stop vehicle drift, there is an option to add a Vehicle Restraint, which can be a
Bushing or a Fixed Joint. When the None option is selected, the vehicle will not be
constrained. The Bushing option has user-editable properties.
Attention: Once the posts are set up, you can click the ‘Assign
Signals’ button to add signals to each post.