MotionView User's Guide

Metadata File Generation

Metadata File Generation

Previous topic Next topic Expand/collapse all hidden text  

Metadata File Generation

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

A metadata file is automatically generated when you save the active MDL model as an ADAMS or MotionSolve deck or you run a solver analysis on the active model.

NoteA metadata file is generated only when there are force output requests on body entities.
hmtoggle_plus1To add body force output requests and generate a metadata file:
NoteMetadata files provide all the geometric, coordinate system, and/or other relevant information about the force outputs requested for one or more bodies in the model.  Metadata files are written out only when there is at least one body force output request.
1.From the MotionView toolbar or Model menu, select the Outputs panel.
2.Under the Output list, click Add.

The Add Output dialog is displayed.

3.Next to Parent:, double-click System.

The Select a System dialog is displayed.

4.Select a parent system from the model tree.  This is the system to which you want to add the entity.
5.Click OK.

The parent system name is displayed in the System field.

6.Enter a label and variable name.
7.Click OK.
8.Select the Properties tab.
9.From the top-most drop-down menu, select Force as the output type.
10.From the lower-most drop-down menu, select Entity as the object.
11.From the collector combo box, select Body as the entity type.
12.Select the body by either picking the body from the entity tree or from the body collector.
13.Select either General reference frame or Predefined reference frame from the right-most drop-down menu.

For General reference frame, select a reference marker using the Ref Marker collector.

metafilegen

For Predefined reference frame, select Lprf, Global, or Local.

metafilegen1

If Lprf or Local is used, set the force output reference in place of the default Global frame.

14.Add body force output request.
15.Repeat the above process to request force outputs on additional bodies.
16.Generate the metadata file:

Select File > Export > Solver Deck to save the model as an ADAMS or MotionSolve deck.

OR

Save and run an ADAMS or MotionSolve simulation on the model.

17.The metadata file name has the same base name as the ADAMS or MotionSolve deck file and has a meta extension.