Home
Multibody Modeling
MotionView is a general pre-processor for Multibody Dynamics.
Vehicle Modeling
Explore the various vehicle modeling tools.
Build and Analyze Models
Add and Run Analysis
Analyze
Create and edit outputs, add an analysis using the task wizard, check the model, and run the solver.
Outputs
Use the Outputs tool to create a result output request to the solver, which writes out the requested data for plotting data.
Editing Outputs
The main types of outputs that can be defined using output requests are displacement, velocity, acceleration, and force. In addition to these, more complex outputs can be extracted using the Expressions and User-defined output types. The output request plays a very important role in post processing the results from a solver run. Output requests also pave the way for signal processing of data that is generated by a multibody simulation.

Welcome
What's New
View new features for Altair HyperWorks 2024.1.
Get Started
Learn the basics and discover the workspace.
Tutorials
Learn more about the Altair HyperWorks suite of products with interactive tutorials.
Startup Procedures and Customizations
Start and configure the applications.
Tool Finder
View a list of deprecated panels and their newer, equivalent workflows.
Manage Files and Data
Create, open, import, and save models.
Sessions and Report Templates
Set up sessions and create report templates.
Interface with External Products
Solver interfaces supported in HyperMesh.
Entities and Solver Interfaces
A solver interface is made up of a template and a FE-input reader.
Browsers
Browsers provide a structured view of model data, which you can use to review, modify, create, and manage the contents of a model. In addition to visualization, browsers offer features like search, filtering, and sorting, which enhance your ability to navigate and interact with the model data.
Sketching
Create and edit 2D parametric sketch geometry.
Topology
Create, edit, and cleanup geometry.
FE Geometry
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.
Meshing and Elements
Explore the different types of mesh you can create in HyperMesh and create and edit 0D, 1D, 2D, and 3D elements.
Model Build and Assembly
Create, organize and manage parts and subsystems.
Composites
HyperMesh composites modeling.
Connectors
Create connections between parts of your model.
Morph
Rapidly change the shape of the FE mesh without severely sacrificing the mesh quality.
Skeleton Modeling
Create a reduced ordered model to facilitate optimization at the concept phase.
Design Space
Workflow to support topology optimization model build and setup.
Optimization
Setup an Optimization in HyperMesh.
Design Explorer
Multi-disciplinary design exploration and optimization tools.
Validate
Validate the model built before running solver analysis.
Analyze
Models require loads and boundary conditions in order to represent the various physics and/or physical equivalents to bench and in-use testing.
Axisymmetry
Reduce a full 3D model with axisymmetric surfaces while accounting for imperfections.
Concept Modeling
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.
Crash and Safety
Tools used for crash and safety analysis.
Airbag
Use airbag folder utilities and export a resulting airbag in a Radioss deck.
Aerospace
Essential utility tools developed using HyperMesh-Tcl.
Aeroelasticity
Import an aeroelastic finite element model with Nastran Bulk Data format.
Certification
Framework to plug certification methods to assess margin of safety from the model and result information.
PhysicsAI
Use PhysicsAI to build fast predictive models from CAE data. PhysicsAI can be trained on data with any physics or remeshing and without design variables.
Results Data
Results data can be post-processed using both HyperMesh and HyperView.
Developer
The Developer ribbon contains tools for automation and customization.
Plot Data
HyperGraph is a data analysis and plotting tool with interfaces to many file formats.
Multibody Modeling
MotionView is a general pre-processor for Multibody Dynamics.
- MotionView Overview
  MotionView is a general pre-processor for Multibody Dynamics.
- Model Browser
  The Model Browser allows you to view the MotionView model structure while providing display and editing control of entities.
- MotionView Ribbons
  The MotionView ribbons allows you to quickly access tools and standard functions, and is located along the top of 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 multibody dynamics models.
- Functional Mockup Unit (FMU)
  Add an FMU to the model or export a model as an FMU.
- Vehicle Modeling
  Explore the various vehicle modeling tools.
  - Build and Analyze Models
    - Add and Run Analysis
      - Analyze
        Create and edit outputs, add an analysis using the task wizard, check the model, and run the solver.
        Outputs
        Use the Outputs tool to create a result output request to the solver, which writes out the requested data for plotting data.
        Creating Outputs
        Editing Outputs
        The main types of outputs that can be defined using output requests are displacement, velocity, acceleration, and force. In addition to these, more complex outputs can be extracted using the Expressions and User-defined output types. The output request plays a very important role in post processing the results from a solver run. Output requests also pave the way for signal processing of data that is generated by a multibody simulation.
        Defining a Force Output Using an Entity
        Defining an Output Using an Entity
        In this case, the output is generated with respect to a selected entity
        Defining an Output Using an Entity Set
        Using this method, the output can be measured for all entities of a certain type that are currently present in the model.
        Defining an Expression Output
        An expression based output can be used to generate outputs based on solver run time functions. Solvers like MotionSolve and ADAMS provide several functions to track various outputs during the solution process.
        Defining an Output Using Two Points
        Through this method, a displacement , velocity, or acceleration between two bodies can be measured relative to each other.
        Using User-Defined Properties for an Output
        Define the output using the User-Defined tab which will allow you to specify the properties of the output using user subroutines.
        Checking the Model
        Use the Check tool to search for any missing references in defined entities or errors in properties.
        Save and Run the Current Model
        The Run Solver tool allows you to save and run the current model.
      - View Reports
        Use the Reports tool to view the report definitions of associated analysis tasks.
  - Vehicle Libraries
  - Components Library
  - Leaf Spring Modeling
  - Road Modeling
  - Tire Modeling
  - Soft Soil Modeling
  - Full Vehicle Events and Altair Driver
  - Road Tools
  - 1D Vehicle System Models
  - Update Model Tool
  - Aerodynamics
  - Track Builder
- Tcl/Tk Reference Guide
  Reference material for the 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.
Media Files
MediaView plays video files, displays static images, tracks objects, and measures distances.
Tabulate Results
Use TableView to create an Excel-like spreadsheet.
Text Files
TextView math scripts reference vector data from HyperGraph windows to automate data processing and data summary.
Publishing and Reporting
Create, define, and export reports.

View All Altair HyperWorks Help

Editing Outputs

The main types of outputs that can be defined using output requests are displacement, velocity, acceleration, and force. In addition to these, more complex outputs can be extracted using the Expressions and User-defined output types. The output request plays a very important role in post processing the results from a solver run. Output requests also pave the way for signal processing of data that is generated by a multibody simulation.

If the Outputs panel is not currently displayed, select the desired output by clicking on it in the Model Browser or in the modeling window.
The Outputs panel is automatically displayed.
From the Result Type drop-down menu (the topmost menu), select the type of results that need to be extracted.

Select an output method from the second drop-down menu.

There are three main ways to define displacement/velocity/acceleration outputs between any two bodies:

Option	Description
Using Two Points	The output can be measured between two points that belong to two different bodies.
Using an Entity	The output can be defined for an entity. The supported entities for this method of output are: body, joint, beam, bushing, field, force, spring damper, and contact.
Using an Entity Set	The output can be defined for all entities of a certain type that are currently present in the model. The supported entities for this method of output are: body, joint, beam, bushing, field, force, spring damper, and contact.

There are two methods of defining a force output:

Option	Description
Using an Entity	The output can be defined for an entity. The supported entities for this method of output request are: body, joint, beam, bushing, field, force, spring damper, and contact.
Using an Entity Set	The output can be defined for all entities of a certain type that are present in the model. The supported entities for this method of request are: body, joint, beam, bushing, field, force, spring damper, and contact..