Usually, you will run MotionSolve using one of the following methods:
| • | from the Start menu, via the HyperWorks Solver Run Manger (on Windows platforms) |
| • | by the command line via motionsolve script (sets the environment for you) |
| • | by the command line via mbd_d (requires environment variables) |
When running in any of these methods, MotionSolve calls each of its modules:
| • | Preprocessor module (mspre): This is the pre-processing module that enables the solver to handle ADAMS input files (ADM/ACF). The input to this module is ADM/ACF. For flexible multi-body models, a flex-H3D file is also required for each flexible body. The output of this module is the MotionSolve XML format. |
| • | Solver module (msolve): This is the module that actually solves your model. The input to this module is only the MotionSolve XML file. This module outputs the LOG file and the MRF file and other output files as requested. |
| • | Postprocessor module (mspost): This is the post-processing module. The inputs to this module are the MotionSolve XML and MRF files. For flexible multi-body models, a flex-H3D file is also required to be input for each flexible body. The outputs from this module are the ABF, PLT and H3D files. |
Note that you also can run any part of MotionSolve by calling the individual modules that makeup its solution process. In order to run these modules, you need the following environment variables set:
For more information, see the MotionSolve Environment Variables.
The executable's corresponding to the three modules listed above reside in the following location:
[install-path]\hwsolvers\motionsolve\bin\<platform>.
The contents of the XML, LOG, MRF, ABF, PLT, and H3D files can be found in the Input and Output File Formats topic.
See Also:
Version of Binary Files
Input and Output File Formats
MotionSolve Modules
Running MotionSolve at the Command Prompt
Running MotionSolve Using the Windows Start Menu
Using the ADAMS Dataset Language Input with MotionSolve
