Browsers supply a great deal of view-related functionality by listing the parts of a model in a tabular and/or tree-based
format, and providing controls inside the table that allow you to alter the display of model parts.
FE geometry is topology on top of mesh, meaning CAD and mesh exist as a single entity. The purpose of FE geometry
is to add vertices, edges, surfaces, and solids on FE models which have no CAD geometry.
Tools and workflows that are dedicated to rapidly creating new parts for specific use cases, or amending existing
parts. The current capabilities are focused on stiffening parts.
This section describes how to build events in the full vehicle model with Altair Driver. The new event user interface is supported only for models with Altair Driver. The interface exports .adf and .xml files and submits them to MotionSolve. Files can be edited or updated in the Event Editor. Eighteen event types are supported.
This section describes all of the full vehicle events currently supported with Altair Driver. It also describes all of
the events and their parameters.
Driver can be loaded using the Model Wizard of MDLLIB when the Full Vehicle with Driver option is chosen. 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.
Full Vehicle with Driver
This section describes how to build events in the full vehicle model with Altair Driver. The new event user interface is supported only for models with Altair Driver. The interface exports .adf and .xml files and submits them to MotionSolve. Files can be edited or updated in the Event Editor. Eighteen event types are supported.
Event Types
This section describes all of the full vehicle events currently supported with Altair Driver. It also describes all of the events and their parameters.
Driver Overview
The Altair Driver is a set of MotionView models and libraries that allows MotionView users to control and script vehicle events.
Controllers Library
Controllers form the core of the driver. The Controller Library has various basic controllers its arsenal to calculate different driver outputs.
MotionView Interface
Driver can be loaded using the Model Wizard of MDLLIB when the Full Vehicle with Driver option is chosen. 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.
Altair Driver File
Driver uses the Altair Driver File (ADF) to access all the event parameters in the Solver.