View new features for MotionView 2021.1.
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.
Explore the various vehicle modeling tools.
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.
The Altair Driver is a set of MotionView models and libraries that allows MotionView users to control and script vehicle events.
Controllers form the core of the driver. The Controller Library has various basic controllers its arsenal to calculate different driver outputs.
Open-loop controllers define vehicle inputs directly without feedback (for example, steering wheel angle vs. time).
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 demand lean profile (for two wheelers) or a path.
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.
Driver uses the Altair Driver File (ADF) to access all the event parameters in the Solver.
Discover optimization with MotionView, MotionSolve, and HyperStudy.
Use the FMU tool to add a Functional Mock-up Unit and connect it to a multi-body model.
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.
Reference materials for the MotionView Python Language.
MotionView help for HyperWorks.
Explore the various vehicle modeling tools.
Controllers form the core of the driver. The Controller Library has various basic controllers its arsenal to calculate different driver outputs.
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 demand lean profile (for two wheelers) or a path.
(c) 2021. Altair Engineering Inc. All Rights Reserved.