You can submit ADAMS dataset language files (ADM and ACF) directly to MotionSolve, thus avoiding manual translation.  The ADAMS model is first automatically translated into the MotionSolve XML format and then solved.

MotionSolve supports most of the ADAMS statements, commands, functions, and user subroutines.  It issues a warning message when an unsupported ADAMS element is found in the input.

Tables 1-4 show the mapping between MotionSolve and the ADAMS/Solver features.  The correspondence between model elements, commands, functions, and user subroutines is shown in detail.  ADAMS features not currently supported by MotionSolve are marked as Not Supported in the MotionSolve column.  These unsupported items will be targeted for completion in future releases.  Some of ADAMS/Solver features have been deprecated and are marked as such.

MotionSolve also provides a few modeling elements that are not supported by the ADAMS solver.  To use these elements with your ADAMS models, ADAMS statements have been added, as have ADAMS commands and functions.  These statements, commands, and functions are marked, in parenthesis, with Not in ADAMS next to the element name in the ADAMS column in tables 2-4.

The ADAMS statements and commands are documented in the section ADM/ACF Entities in the XML Format help.  The new functions are documented in the MotionSolve Functions section of the XML Format help.

See Also:

Table 1- Mapping between ADAMS and MotionSolve Modeling Elements

Table 2- Mapping between ADAMS and MotionSolve Command Elements

Table 3- Mapping between ADAMS and MotionSolve Functions

Table 4- Mapping between ADAMS and MotionSolve User Subroutines

Input and Output File Formats

MotionSolve Modules

Running MotionSolve at the Command Prompt

Running MotionSolve Using the Windows Start Menu

Graphical User Interfaces - HyperMesh and MotionView