|
»Click here to display Table of Contents«
|
Interfacing with Solvers |
|
|
|
|
|
Interfacing with Solvers |
|
|
|
|
|
»Click here to display Table of Contents«
|
Interfacing with Solvers |
|
|
|
|
|
Interfacing with Solvers |
|
|
|
|
MotionView MDL models can be exported to numerous solvers. Several solvers such as ADAMS, Abaqus, DADS and Nastran are programmed to directly map MDL modeling statements to corresponding entities within the solver input deck. In addition to this, Templex templates can be used to export information not contained in MDL and can be used in MotionView to pre-process any solver that requires an ASCII input deck.
Several considerations need to be made when interfacing with solvers. These are outlined below and are explained in more detail in the Help topics listed under See Also.
These parameters are unique relative to other entities. A description of each is included within each solver section.
This section covers details on mapping between MotionView MDL entities and the corresponding solver entities. It explains the subset of MDL statements that describe a mechanical system and the statements that apply to a particular solver.
MDL CommandSet statements apply to a solver command file. These statements are order dependent. The mapping of these statements is covered for each solver.
Within MotionView, Templex templates allow any syntax to be exported directly to a solver input deck. In addition, the data within a template can be parametric and depend on other MDL data values. Templex templates, however, are generally not solver neutral so any functionality that's captured within a template has to be captured for each solver used by that model.
MotionView supports function expressions that describe properties such as bushing stiffness, motions, and spring damper values. These expressions get passed into the solver input deck as a function for an entity's property. Function expressions can use the Templex statements solvercr and dtor, which are described in each solver section.
Many entities get their associated values from user subroutines in place of the pre-defined entity values. User subroutines are generally in the form of DLLs or are linked with the solver to create a user executable solver. User subroutines only map to a couple of solvers.
MotionView allows you to register one or more launch scripts that subsequently display in the Run Solver panel. If the Run Solver panel is used with one of these scripts, a solver input deck and supporting files are generated. In addition, a script is invoked with the name of the solver input deck as the first argument passed to the launch script.
Post-processing methods as they relate to the MotionView MDL file are explained.
Some solvers automatically remove redundant constraints while others do not. Depending on the modeling technique used, this may or may not be an issue for the solver. Details are explained in each solver section.
Exporting MDL Models to MotionSolve
Exporting MDL Models to Abaqus