HyperWorks Solvers

Custom Translation Rules from ADAMS to XML Translation

Custom Translation Rules from ADAMS to XML Translation

 Previous topic Next topic No expanding text in this topic  

Custom Translation Rules from ADAMS to XML Translation

 Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function  

The ADAMS files (ADM and ACF) are interpreted by the ADAMS Dataset Reader (ADR), which is responsible for identifying and translating this file’s information into XML.  The generated XML is the input for MotionSolve.

data_adams_msolve

Data flow from ADAMS to MotionSolve

Without a mapping file, some manual editing is required after the ADR converts the deck to XML format.

To eliminate the manual editing process, a customizable configuration XML file is created called a Mapping file.

mapping_ms_adams_trans

Role of the mapping file in ADAMS  and MotionSolve

To translate ADAMS input files into MotionSolve XML input files:

1.Edit the mapping file as shown below:

map_file_ex

Example of a mapping file

2.As shown below, fill in the Variable name: and Variable value: fields in the Edit User Variable dialog.  This tells MotionSolve how to find the mapping file you edited.

set_env_var

Set Environment Variable

With all the various customization features discussed in this chapter, you are able to create your own environment around the core solver.  Solver enhancements are available and the product can be customized to suit your needs.

See Also:

Custom Functions

Custom Statements

Custom Messaging

Custom Results Output

Custom Results Output