MotionView is designed for users who are primarily interested in multi-body simulation.  Users appreciate its simplicity, hierarchical model organization, and systems modeling focus.  MotionView models are represented using the Model Definition Language (MDL).  MDL is ideal for hierarchical modeling of complex mechanical systems, such as full car and truck assemblies.  When running the MotionSolve from MotionView, the model is first translated into MotionSolve XML format, and then submitted to MotionSolve.

The MotionView interface has the following strengths:

The HyperMesh interface provides multi-body simulation capabilities for finite element analysis with the following benefits:

The multi-body system model is used to generate correct boundary conditions for component models.  This data may be used to compute realistic predictions for stress and fatigue-life.

The multi-body solver can be used for fast, automated repositioning of a finite element assembly to a new configuration for a finite element simulation.

HyperMesh contains morphing technology useful for parametrizing the shape and size of components.  This technology can be used in conjunction with MotionSolve to automate the design of mechanical systems, simultaneously satisfying multiple performance criteria on motion, packaging, strength, and durability.        

The HyperMesh interface works in the following way.  First, the model is exported into the OptiStruct bulk data file and then submitted to the OptiStruct solver, which scans the file for multi-body elements such as constraints, nonlinear bushings, and motions.  If none are found, the model is considered to be a finite element model and processed with the OptiStruct structural analysis solver.  If multi-body elements are found, the model is translated into a MotionSolve XML file and solved using MotionSolve.  This process is entirely automated.  For more information, see Multi-body Dynamics Simulation in the OptiStruct User's Guide.