MotionView

2022.2

Home
Vehicle Modeling
Explore the various vehicle modeling tools.
Full Vehicle Events and Altair Driver
Controllers Library
Controllers form the core of the driver. The Controller Library has various basic controllers its arsenal to calculate different driver outputs.
Closed Loop Controllers
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.
Throttle and Brake Controllers

What's New
Get Started
Tutorials
MotionView Overview
MotionView Menus
Project Browser
MotionView Panels
MotionView CAD Interfacing
Flexible Bodies
MotionView Solver Interfacing
Vehicle Modeling
Optimization
Functional Mockup Unit (FMU)
MotionView Interface with Collaboration Tools
Tcl/Tk Reference Guide
MDL Reference Guide
MotionSolve Reference Guide
Templex and Math Reference Guide
MotionView Python Reference Guide
HyperWorks MotionView Help

Index

2022.2

MotionView

What's New
View new features for MotionView 2022.2.
Get Started
Learn the basics and discover the workspace.
Tutorials
Discover MotionView functionality with interactive tutorials.
MotionView Overview
MotionView is a general pre-processor for Multi-body Dynamics.
MotionView Menus
Explore the MotionView menus which provide access to the various wizards, dialogs, tools, and panels.
Project Browser
The Project Browser allows you to view the MotionView model structure while providing display and editing control of entities.
MotionView Panels
Explore the various panels and tools in MotionView.
MotionView CAD Interfacing
MotionView supports the importing of several types of CAD and FE formats.
Flexible Bodies
MotionView has many pre-processing and post-processing capabilities with regards to flexible bodies, or flexbodies, for multi-body dynamics models.
MotionView Solver Interfacing
Solvers and translators supported in MotionView.
Vehicle Modeling
Explore the various vehicle modeling tools.
- Build and Analyze Models
- Vehicle Libraries
- Components Library
- Leaf Spring Modeling
- Road Modeling
- Tire Modeling
- Full Vehicle Events and Altair Driver
  - 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.
    - Open Loop Controllers
      Open-loop controllers define vehicle inputs directly without feedback (for example, steering wheel angle vs. time).
    - Closed Loop Controllers
      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.
      - Throttle and Brake Controllers
        
        Feed-forward Traction Controller
        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).
        
        Feedback Traction Controller - PID Controller
        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.
      - Steering Controllers
      - Gear and Clutch Controllers
      - Additional Controllers
      - Demand Signal for Controllers
      - Demand Path for Steering Controllers
  - Additional Altair Driver File Blocks
  - Altair Driver Mathematical Methods
  - Troubleshooting Driver Modeling
  - 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.
- Road Tools
- 1D Vehicle System Models
- Update Model Utility
- Aerodynamics
Optimization
Discover optimization with MotionView, MotionSolve, and HyperStudy.
Functional Mockup Unit (FMU)
Use the FMU tool to add a Functional Mock-up Unit and connect it to a multi-body model.
MotionView Interface with Collaboration Tools
MotionView supports a limited version of interface with HyperWorks Collaboration Tools.
Tcl/Tk Reference Guide
Reference material for the HyperWorks Desktop scripting interface which is a set of Tcl/Tk commands.
MDL Reference Guide
Reference materials for the MotionView MDL Language, Tire Modeling, and the MDL Library.
MotionSolve Reference Guide
Reference material detailing command statements, model statements, functions and the Subroutine Interface available in MotionSolve.
Templex and Math Reference Guide
Reference material for Templex (a general purpose text and numeric processor) and additional mathematical functions and operators.
MotionView Python Reference Guide
Reference materials for the MotionView Python Language.
HyperWorks MotionView Help
MotionView help for HyperWorks.

View All Altair Simulation Help

MotionView

2022.2

Home
Vehicle Modeling
Explore the various vehicle modeling tools.
Full Vehicle Events and Altair Driver
Controllers Library
Controllers form the core of the driver. The Controller Library has various basic controllers its arsenal to calculate different driver outputs.
Closed Loop Controllers
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.
Throttle and Brake Controllers

What's New
Get Started
Tutorials
MotionView Overview
MotionView Menus
Project Browser
MotionView Panels
MotionView CAD Interfacing
Flexible Bodies
MotionView Solver Interfacing
Vehicle Modeling
Optimization
Functional Mockup Unit (FMU)
MotionView Interface with Collaboration Tools
Tcl/Tk Reference Guide
MDL Reference Guide
MotionSolve Reference Guide
Templex and Math Reference Guide
MotionView Python Reference Guide
HyperWorks MotionView Help

Index

Throttle and Brake Controllers

Feed-forward Traction Controller
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).
Feedback Traction Controller - PID Controller
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.

Intellectual Property Rights Notice | Technical Support | Cookie Consent