Explore the various vehicle modeling tools.
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.
Closed-loop controllers use vehicle responses (for example, speed, position, yaw rate, etc.) as feedback to determine the vehicle inputs needed to match a desired vehicle response, such as following a path.
View new features for MotionView 2020.
Learn the basics and discover the workspace.
Discover MotionView functionality with interactive tutorials.
MotionView is a general pre-processor for Multi-body Dynamics.
Explore the MotionView menus which provide access to the various wizards, dialogs, tools, and panels.
The Project Browser allows you to view the MotionView model structure while providing display and editing control of entities.
Explore the various panels and tools in MotionView.
MotionView supports the importing of several types of CAD and FE formats.
MotionView has many pre-processing and post-processing capabilities with regards to flexible bodies, or flexbodies, for multi-body dynamics models.
Solvers and translators supported in MotionView.
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 Altair Driver is a set of MotionView models and libraries that allows MotionView users to control and script vehicle events.
Open-loop controllers define vehicle inputs directly without feedback (for example, steering wheel angle vs. time).
The Feed-forward controller is the predictive controller of the Altair Driver. It predicts some of the states of the vehicle after look ahead time, or look ahead distance, and accordingly drives the throttle and brake signals to match the demand signal (for example, speed).
A Proportional-Integral-Derivative (PID) controller is a feedback controller that computes a vehicle input using the error, the integral of error, and the rate of change of error between a desired vehicle response and the actual vehicle response.
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.
Discover optimization with MotionView, MotionSolve, and HyperStudy.
Learn more about the Functional Mockup Unit (FMU) in MotionView and MotionSolve.
MotionView supports a limited version of interface with HyperWorks Collaboration Tools.
Reference material for the HyperWorks Desktop scripting interface which is a set of Tcl/Tk commands.
Reference materials for the MotionView MDL Language, Tire Modeling, and the MDL Library.
Reference material detailing command statements, model statements, functions and the Subroutine Interface available in MotionSolve.
Reference material for Templex (a general purpose text and numeric processor) and additional mathematical functions and operators.
View All Altair HyperWorks Help