Exchanging Data in Adams

Adams products import and export modeling data in many different formats so you can exchange
modeling data with other Adams products, as well as other software manufacturer’s products.
This entries in this section of the table of contents explain how to import and export modeling data in
Adams products and the optional module, Adams/Exchange. The dialog boxes shown are Adams/View
dialog boxes. The available options may change depending on the Adams product you are using.
2 Adams/View
Supported File Formats for Import and/or Export

Supported File Formats for Import and/or Export

The following table shows the formats that Adams/View, Adams/Exchange, and Adams/Durability
support. The only formats that require an additional product are:
• STEP, IGES, DXF, DWG, and Parasolid - Require Adams/Exchange
• CatiaV4, CatiaV5, Inventor, Acis, ProE, SolidWorks, Unigraphics, VDA - Require 'Adams CAD
Translators' license
• RPC III and DAC - Require Adams/Durability

You can import all other formats using standard Adams/View.

Can be:
File format: Description: Imported Exported
Adams/Solver Describes a model using Adams/Solver Data Yes Yes
dataset (.adm) Language (ADL) statements.
Adams/Solver Set of three Adams/Solver analysis files: request, Yes Yes
analysis files (.req, results, and graphics. You can import the entire set
.res, .gra) or just a single analysis file.
Adams/View Set of Adams/View commands. You can use Yes Yes
command file command files to automate the creation of a model
(.cmd) or the investigation of simulation results.
Test data Numerical results generated from an external Yes No
program.
Numeric data Numerical results generated during an No Yes
Adams/View session.
 Exchanging Data in Adams 3
Supported File Formats for Import and/or Export

Can be:
File format: Description: Imported Exported
CAD files Requires Adams/Exchange. Yes Yes

Model geometry. You can import and export the

following formats: STEP, IGES, DXF, DWG, and
Parasolid.

With the Adams_CAD_Translators license, the

following formats are supported

Import: CatiaV4, CatiaV5, Inventor, Acis, ProE,

SolidWorks, Unigraphics, VDA

Export: CatiaV4, CatiaV5, IGES, ACIS, STEP,

VDA

Note: CatiaV5 import/export is not supported

on the linux platforms (32-bit and 64-
bit). Also, for IGES/STEP, the
environment variable
MSC_GEOM_TRANSLATE_INTEROP
needs to be set to 1 in order to use
Interop.
Stereolithography Polygonal representation of surfaces. Yes No
and render files
Wavefront files Set of output files that contain a description of the Yes Yes
model graphics and motion data.
FEA loads Complete load histories. No Yes
Spreadsheet Simulation results in a spreadsheet format. No Yes
Shell Geometry representations. Yes (Adams/ Yes
PostProcessor)
Adams/ All the files required to view the results of No Yes
PostProcessor simulations in a stand-alone version of
Adams/PostProcessor.
RPC III and DAC Requires Adams/Durability. For more Yes Yes
information, Adams/Durability online help.

MTS Systems Corporation's RPC III and nCode's

DAC files that let you interface with durability
test machines and fatigue life calculation
programs.
4 Adams/View
Comparison of Adams File Formats

Comparison of Adams File Formats

The advantages and disadvantages of the different Adams file formats in which you can save or export
your modeling data are listed in the table below.

Format: Advantages: Disadvantages: Upward Compatibility:

Adams/Solver • Creates a model definition for • Saves ADL for a single • Upwardly compatible with
dataset Adams/Solver analysis. model only. Adams for two major
• Uses standard Adams data • Doesn't contain releases. For example, files
language (ADL) commands. Adams/View created in version 7.0 are
environment information compatible with versions 8
• ASCII format that is easy to read and 9.
and portable to different (modeling entity color,
computer platforms. size, and visibility • Files created in a Beta
attributes). version are never
• Enables you to build and compatible with the final
investigate the results of the • Doesn't save all types of
geometry, such as version.
analysis on a different platform
from your analysis. polylines, revolutions,
extrusions, ellipsoids,
• Provides a standardized format links, and toruses.
and allows extensive comments.
Adams/View • Restores an Adams/View session • The file size can be large. • Interface customization is
Modeling exactly as it was when you saved • You have to load the lost between versions.
database the file. binary file into the Before upgrading, export
(binary) • Saves an entire database with product to debug your the customization content
multiple models, analysis cases, mode. as text files (macros, dialog
and simulation results. boxes, menus, and so on)
and then import the files
• Provides unified, precise storage into Adams.
and fast read/write capability.
• Files created in a beta
version are never
compatible with the final
version.
Adams/View • Defines a single model. • Reads slower than binary. • Upwardly compatible with
command • Allows reading and writing of • Contains only a single Adams for two major
file since it is in text format. model definition, with no releases. For example, files
simulation data. created in version 7.0 are
• Enables transferring of data to compatible with versions 8
different computer systems. • Doesn't contain and 9.
• Saves all types of geometry, such Adams/View
environment information • Files created in a beta
as polylines, and links. version are never
(view layouts, menu
definitions, and so on). compatible with the final
version.
 Exchanging Data in Adams 5
Comparison of CAD File Formats

Comparison of CAD File Formats

The following compares the different CAD file formats for importing geometry using Adams/Exchange
or Adams/View.

The file format: Has the advantages/disadvantages:

IGES • When exporting geometry from a CAD program, the shapes are represented by
triangles and rectangles. You can adjust the tolerance on the approximated
shape when importing in Adams/View.
• Volume information is not supported in Adams/Exchange if the geometry is
imported as a polygon or if the original shape is not a solid. Therefore,
Adams/View cannot calculate the mass properties of the imported shape. You
have to define them manually.
• Color information is retained.
• To import shells as solids, be sure to set the options Solids instead of Polygons
and turn off Consolidate to shells. Also the originals have to be solid to be
imported as solid. If something goes wrong during the import process,
approximation will be tried and the imported shape will be represented by
polygons. Note that if you import the geometry as a solid, Adams/View can
calculate mass properties.
Render • Volume information is supported in Adams/Exchange, within the given
tolerance in the shape. Adams products, therefore, can calculate mass
properties.
• Each render file can contain many shapes, but when you import it,
Adams/Exchange attaches all its geometry to only one part.
• Color information is retained.
• Importing your geometry as Stereolithography (STL) or render geometry is
more reliable than using other CAD formats, such as IGES or STEP.
• File format is very simple.
• The files are much larger than IGES and DXF files.
• Because the surfaces have been represented as polygons, you cannot change
the accuracy of the surface representations in Adams/View. You must specify
the accuracy when you create the files in your CAD program.
6 Adams/View
Comparison of CAD File Formats

The file format: Has the advantages/disadvantages:

STEP • Adams/Exchange supports STEP AP203 and AP214. Note, however, as stated
in the ITI PDELIB manual:
It is important to realize that AP 214 is still at the "Committee Draft" stage of
its development and as such is a continuously changing and evolving beast.
While it is our intent to update this subsystem as necessary, no guarantees are
expressed or implied, that is, use at your own risk!
• Adams/Exchange does not support conformance class 5, which contains
faceted B-rep shape representation. ITI explains that faceted B-rep shape
representation takes up too much memory to exchange, and most vendors do
not support it.
• Volume information is supported in Adams/Exchange, within the given
tolerance in the shape. Adams products, therefore, can calculate mass
properties. You may find a small difference between the mass properties
calculated in Pro/ENGINEER and those calculated in Adams.
• Each STEP file can contain many shapes, but when you import it,
Adams/Exchange attaches all its geometry to only one part.
• Color information is not retained.
Stereolithography • When exporting geometry from a CAD program, shapes are represented by
triangles. Most CAD programs support the ability to specify a tolerance, and,
therefore, the number of triangles.
• Volume information of solid bodies is supported in Adams/View, within the
given tolerance in the shape. Using that shape, Adams products can calculate
mass properties. Volume information of thin-walled bodies is not supported, so
no mass properties can be calculated for it.
• Only one body for each STL file.
• Color information is not retained.
Parasolid • Currently, Adams/Exchange supports Parasolid version 19.0.17.
• Using Parasolid files, you can import the whole model while you can only
import part by part using STEP, IGES, STL, DWG, and DXF.
 Exchanging Data in Adams 7
Exporting Data Defining a Geometric Spline

Exporting Data Defining a Geometric Spline

You can export data defining a geometric spline element (for example, a spline that you created by
following a point during an animation. Learn about Creating Trace Spline).

To export the data:

1. Right-click the spline geometry, point to its geometry name, and then select Modify.
2. To the right of the Values text box, click the More button .
3. The Location Table appears.
4. Use the Write button to export the data. Learn about Reading and Writing Location Information..
8 Adams/View
Import and Export

Import and Export

Imports modeling data in a wide variety of formats so you can exchange modeling data among different
Adams products, as well as with other software manufacturer’s products.
See File Import and Export Dialog Box help.

Sources of Command Files

There are three possible sources for a command file:
• Use your system editor to type in Adams commands.
• Convert a Log file from a previous Adams session into a command file. You should be careful,
however, to avoid recursive execution of command files (command file that calls itself). This can
happen easily if you try to execute the log file that the system is currently writing. Learn about
Using the Adams/View Log File.
• Export a command file to reproduce a model currently in the Adams Modeling database into
Adams command.

Command File Format

A command file contains the following types of elements:
• Comments, which Adams does not read or execute. Begin comments with exclamation points
(!).
• Executable Adams commands, including your responses to prompts from Adams/View. The
commands are the same ones that you enter in the Command window or that Adams executes in
response to menu and dialog box choices.
You can also enter pauses in your command file so that Adams/View stops and waits for input or a
specified time before preceding.
You can use any combination of upper or lowercase characters for commands in a command file, except
for text system commands and filenames.
Each command must start a new line. Remember to include the response to any prompts that you expect.
If you find you need more than a single line for a command and its associated parameters, place an
ampersand (&) as the last character on the line to be continued. In this way, you can use as many lines as
you need for each command.

Command File Example

To help make the command file easier for you to read, many of the lines are blank comment lines.
! Read Adams files eject.gra, eject.req, and eject.res. The data
! will be put into an analysis, named ‘eject’, by default.
 Exchanging Data in Adams 9
Import and Export

!
file analysis read file_name=eject
!
! Remove all but one view (the one that will remain is, the “active”
view),
! and display the bottom view in it (this actually recalls from the
data
! base the set of view attributes saved under the name “bottom”).
!
view management delete view_name=all
view management restore saved_view_name=bottom
!
! Display frame 150 from the simulation graphics file.
!
graphic_results single_frame_display frame_number=150
!
! Create a Postscript hardcopy file of this frame.
!
hardcopy generate
! Done
!
exit confirmation=yes

Ensuring Upward Compatibility of Command Files

If you want to ensure upward compatibility of your command files with subsequent releases of Adams,
use the complete names of commands, not their abbreviations. If you use the menus and dialog boxes in
Adams to execute commands, then all the commands are fully expanded in the Adams/View log file,
which you can then use as source of your command file.

To expand the abbreviations in a command file to complete commands:

1. Add the following commands to the beginning of the command file:
FILE LOG_FILE SET EXPAND_COMMANDS=ON &
COMMAND_WRITE=ON
2. Import the command file into Adams/View at the start of a new session.
3. Exit as soon as Adams has read and executed the complete command file.
4. Remove the following commands from the log file:
FILE COMMAND READ FILE_NAME=file_name &
EXIT CONFIRMATION=YES
5. Rename the log file from this session and give it a name to indicate that it is a command file. It is
now the original command file with expanded command abbreviations.
10 Adams/View
Import and Export

Command File Import Error Options

You can specify that Adams do one of the following as it imports command files:
• Ignore command - Instructs Adams to ignore the line on which it found the error and start
processing the next line as a new command. Adams can usually recover and execute subsequent
commands in the file. If subsequent commands depend on the results of the invalid command,
however, they may fail or give unexpected results.
• Continue the command file execution - Instructs Adams to continue processing the line as if it
were typed interactively. This can be dangerous if there is no correction later on in the line,
because Adams keeps issuing error messages until the error is corrected. The errors can continue
beyond the end of the line, even to the end of the file, if carriage returns are invalid. Use this
value only if the command file is a literal recording of your key strokes, complete with back
spaces or other corrections of mistakes.
• Cancel the command file execution and abort file - Instructs Adams to immediately close all
the command files and returns control to interactive input. This is the most conservative setting
because it guarantees subsequent commands will cause no further errors or unexpected results.

About Exporting FEA Loads

You can export Adams/View dynamic load information about any rigid or flexible body in your model to
a finite element analysis (FEA) program for modeling and analysis. Adams/View gives you the option to
export complete load histories that include load information for all output steps in a Simulation or export
load information for only those Output steps of interest. The FEA program uses the load information for
a variety of purposes, such as stress and strain analyses.
You can export load information from Adams/View in the following formats:
• ANSYS from Swanson Analysis Systems, Inc.
• MSC.Nastran from MSC.Software
• ABAQUS from Hibbitt, Karlsson & Sorensen, Inc.
• DAC or RPC III file formats (available with Adams/Durability only)

Adams/View calculates the loads on a desired body at the specified output steps in a simulation and
exports the load information to a loads file. The loads file contains a series of load cases where the body
is at an instantaneous dynamic equilibrium, such that the external (applied) forces and joint reactions are
in balance with the inertial and gravitational forces. The loads file can be in any of the three formats listed
above. After Adams/View exports the file, you can use the loads file directly in the FEA program without
any conversions or edit the file in a text editor, as desired.
See Export - FEA Loads dialog box help.
 Exchanging Data in Adams 11
Import and Export

Process for Exporting FEA Loads

When exporting dynamic load information, you perform the following general steps:
• Run a Simulation - Before exporting FEA loads, you need to run a Simulation of your model so
that Adams/View can determine the loads acting on the bodies in the model. There is no special
preparation needed for this simulation; you run it just like any other simulation.
• Identify the Body - You identify the body whose load information you want to export by
specifying a marker belonging to a rigid body or directly selecting a flexible body. For a rigid
body, Adams/View calculates all load information relative to the marker you select. Therefore,
the marker’s location must correspond to the origin of the body as it appears in the FEA tool. For
a flexible body, Adams/View assumes that its FEA origin is unchanged.
• Find Load Points - After identifying a body whose load information is to be exported,
Adams/View finds all locations (load points) on the body that have external loads placed on
them and displays the locations in a table. The node coordinate locations are displayed relative to
the FEA origin of the body.
For a flexible body, Adams/View also populates the table with the node IDs of the load points
that correspond to the node IDs on the part in the FEA program. For a rigid body, you assign
node IDs to the load points as explained next.
• Assign Node IDs to Load Points, if desired - For a rigid body, you can assign IDs to the load
points that correspond to the node IDs on the part in the FEA program before exporting the load
information. You can assign the IDs using either of two ways:
• Type the node IDs into the table in Adams/View.
• Store the node IDs in a text file and have Adams/View read the file. As Adams/View reads a
file, it associates the load points it found on the part with the node IDs and locations listed in
the file. Adams/View searches the file for node IDs with locations closest to the ones it found
and fills the node IDs into the table in Adams/View.
The node location file must be in the following format with commas (,) separating each
element:
Node IDn, X, Y, Z
Node IDn+1, X, Y, Z
...
If your model contains several node IDs, you might want to create a text file of node IDs.
If you choose not to specify any node IDs, the FEA input file that is generated will contain the locations
(with respect to the FEA coordinate reference) and ADAMS ID labels of the specified marker forces. You
will need to replace the ADAMS ID labels with node IDs in the input file before submitting an analysis.

Limitations for Exporting FEA Loads

The following are limitations for exporting FEA loads from Adams/View.
12 Adams/View
Import and Export

Redundant Constraints
You cannot export loads at the locations of redundant constraints. This is because Adams removes all
redundant constraints in the simulation. Therefore, forces are not computed for these constraints. It is best
to manually remove redundant constraints defined at a part before simulating if you want to export FEA
loads.

Couplers and Gears

Loads due to couplers or gears are only exported on a part if the motion of that part is driving the coupler
or gear. If, instead, the motion of the part is being driven by a coupler or gear, then the load resulting from
that constraint will not be included in an FEA loads export of that part.

Friction
Reaction loads resulting from friction in joints are not supported. In fact, you receive an error if you
attempt to export loads on joints that include friction.

Floating Markers
You cannot export FEA loads if the part has a floating marker. You receive the following error message
from Adams/View when you try to export loads for a part with a floating marker:
No application point for reaction force. Unable to export loads on floating markers.
This can happen if there are forces, such as six-component general force, three-component force, or
three-component torque, or higher-pair constraints, such as curve-point or curve-curve, are defined on
the part. In the case of forces, there is a workaround:
• Redefine the force by swapping the I- and J-parts so that the part in question does not have a J-
floating marker.

Missing Result Set Components

Adams/View exports an incomplete load set if results of components defined on the part are missing from
the simulation. This condition is checked and a warning message is issued for each component that does
not have a result component. This usually happens when the computation of certain types of results, such
as forces, is turned off.

HTML Files Created for HTML Reports

When you export Adams/PostProcessor files to an HTML report, the result is a series of HTML pages,
images, and style sheets, including a main homepage. The homepage is an HTML page with two frames:
 Exchanging Data in Adams 13
Import and Export

the left frame is a treeview of the top-level objects, the right frame displays the object selected in the
treeview.

In the treeview, there are three top-level objects:

• Title Page - Displays a title page with general information about the data exported.
• Pages - Lists the pages exported from Adams/PostProcessor. Click a page to display an image of
a plot or animation or play a movie of an animation.
• Model - Lists the models for which you selected to export information. When you click a model,
its different objects (parts, forces, constraints, requests, measures, and assembly objects) appear
in the treeview. Click an object to display information about the object in the right frame.

To display the main HTML homepage:

1. In a Web browser, change to the folder containing the results of the export.
2. Select the file with the same name was you entered in the Files tab. For example, if you entered
suspension_1, select suspension_1.htm.

Test Data Format

The test data that you want to import into Adams must be in an ASCII file composed of columns of
values. Each column should hold the values for a separate component. The values in each column should
be in order by the time step, from earliest to latest.
Adams reads the columns from left to right and from top to bottom. One or more blank spaces separates
each column from the column on either side, and one or more comment lines separates columns placed
beneath each other. You can separate numbers with a comma (,) and you do not have to line them up
evenly. Adams considers any lines that do not begin with a number as a comment line.
Adams reads a column until it reaches a comment line, which indicates the end of the component. For
example, in the sample numeric data file the columns beginning with 1 and 10.0 are the first two
components. The third component is the column beginning with 22. Each component has ten numbers.
14 Adams/View
Import and Export

If you specify that one of the columns contains a time index, then Adams stores the data in that column
as the x data for each spline it creates. In addition, you can specify that Adams assign the names for the
splines using the text in the column headers. If you do not specify that Adams obtain the names from the
column headers, Adams automatically generates their names.
Be sure that any text in the file does not begin with a number. If it does, Adams tries to read the line. To
prevent Adams from reading text as a value, place a non-numeric character in front of text that you want
Adams to ignore. We recommend that you use an exclamation point (!).

Test Format Example

Test Format Example
1 10.0
2. 11.0
3.4 12.5
-4 13.0
5 +14.0
6 15.5
7 17
8 18
9 ,19
10, 20
22
23
.24
25
26
27
28
29
30
31

Example of Number in Text

This sample file contains only one component but contains the number
3 at the beginning of a line in this header paragraph. Adams/View will
try to read
this line because it is not considered a comment.
1.5
3.0

! This sample file contains only one component and contains the number
! 3. Because we used an exclamation point (!) in front of each line in
this header
! paragraph, however, Adams/View does not read the line starting with
3.
1.5
3.0
 Exchanging Data in Adams 15
Import and Export

Tips on Importing Wavefront Files

The Wavefront file is unitless even though most of the ViewPoint graphics internally use one hardcoded
unit system. You will need to scale the vertices to make them fit the units set in the Adams/View model.
For example, if the Viewpoint graphics were originally created using the length unit, mm, then, if your
Adams/View session units are in meters, you’ll use a scale factor of .001.
You may find that you need to experiment with different scale factors to create a model that contains
practical scales. To experiment with the different scale factors, just undo the import if it does not work
using the Undo command.
Before importing the graphics, create a dummy part to which you’ll attach the Wavefront graphics.
Creating dummy parts is helpful because the orientation within the Viewpoint dataset is usually different
than the orientation of your model. Dummy parts provide an easy method of moving and rotating the
graphics to match your Adams model. To move the graphics, you just move the dummy part.
Here is a procedure for ensuring that the geometry is attached to the correct part:
1. From the View menu, select Part, and select the dummy part to view.
2. Rename each shell so that it belongs to the correct part.
Different shells start disappearing from the dummy part while in View Part Only mode.
3. After renaming all the geometry, delete the dummy part.
4. Display the model.
Now you have the model with different graphics elements attached to correct parts and at correct
locations and orientations.
A convenient way to read in an entire Viewpoint dataset and avoid some of the problems mentioned
earlier is to reduce the number of group names in the dataset before importing it into Adams/View.
Generally, groups in the Wavefront file become parts in Adams/View. If a part already exists that has the
same name as a group, however, the graphics simply attach to the existing part without creating a new
part. If Adams/View finds a group with no corresponding part, it creates a new part for the group.
If you have multiple groups with the same name in the Wavefront file, all groups attach to the same
Adams/View part but become separate geometric entities. This allows you to use different colors within
the same Adams part to create more realistic images.
The only lines that are significant in the Wavefront file are the ones that begin with g (groups), f (facets),
and v (vertex). Adams/View ignores everything else.
To reduce the number of group names, open the dataset in a text editor and substitute names before
importing the set into Adams/View. For example, a car body dataset typically has the following group
names:
• g hood
• g fender
• g windows
16 Adams/View
Import and Export

• g bumper

Change them to the same name so they attach to a single part. For example:
• g body
• g body
• g body
• g body
 Exchanging Data in Adams 17
About Adams/Exchange

About Adams/Exchange
Adams/Exchange supports four data exchange formats:

• IGES
• STEP
• DXF/DWG
• Parasolid

The geometry translator underneath Adams/Exchange that supports IGES, STEP, and DXF/DWG is
PDE/Lib. It was provided by International Technegroup Incorporated (ITI) of Milford, Ohio. You can
contact them at 513-576-3900. ITI reserves all rights with respect to PDE/Lib.

About Importing and Exporting CAD Data Using

Adams/Exchange
Adams/Exchange imports standard geometry files from any software package that supports IGES, STEP,
DXF/DWG, and Parasolid file formats, and converts the data into a set of Adams/View geometry
elements. These elements correspond to standard Adams/Solver GRAPHICS statements, polylines, or
shells. You associate the geometry with any rigid body part of the Adams/View model before or after you
run an Adams/View simulation.
Adams/Exchange reduces the need to recreate geometry primitives within Adams/View and enhances
your ability to realistically view the behavior of complicated mechanical systems. You can also use the
imported geometry for model building in Adams/View and for locating parts, constraints, and forces
based on the imported geometric data.
For recommendations of the best ways to export data from the CAD packages so you can import it
effectively into Adams, see Recommendations for Exporting CAD Data.

About Exporting CAD Data

Adams/Exchange exports the geometric definition of an Adams model from Adams/View to the
geometry file format, whether IGES, STEP, DXF/DWG, or Parasolid. The geometry file can then be read
into CAD or CAE software.

About IGES Import and Export

The Initial Graphics Exchange Specification (IGES) was originally developed in 1979, by the National
Bureau of Standards (NBS), to facilitate the transfer of geometry and annotations from one CAD/CAM
system to another. IGES is the predominant format used for the transfer of geometry information. The
IGES specification defines a structured hierarchical file format and the representation of a variety of
entities within the format. The entity set includes: geometric, annotation, structure, associativity,
property, and attribute entities.
18 Adams/View
About Adams/Exchange

The next sections explain how Adams/Exchange works with IGES files. For a detailed explanation of the
IGES entity types, please refer to The Initial Graphics Exchange Specification (IGES) Version 5.0
manual.

Linear Approximation
Adams/View directly supports only a subset of the geometry encountered in the IGES file. Some of the
unsupported IGES entities are approximated using a technique called linear approximation.
Adams/Exchange translates the nonlinear entities (for example, surface, curve, and so on) it encounters
in the IGES file to polylines. For IGES curves, surfaces, and annotation entities that are nonlinear in
definition, linear approximation produces a piecewise linear string of points or polygons that
approximates the geometry to within a specified tolerance. For more information, refer to the discussion
of the tolerance option in Import - STEP, IGES, DXF/DWG.

Unit Conversion
Adams/Exchange automatically converts all coordinate data in the IGES file to the internal units (meters,
kilograms, seconds) of Adams/View.

Automatic Import of a CAD Mechanism

Some CAD packages support the automatic transfer of a mechanism model that was developed using an
integrated Adams interface to Adams/View. These packages include:
• Mechanical Dynamics MECHANISM/Pro for PTC Pro/ENGINEER
• Mechanical Dynamics Adams/MS Mechanisms for Bentley MicroStation
• I-DEAS Mechanism Design for I-DEAS (embedded starting with MS7)
• Unigraphics UG/Mechanisms (available as a macro/user function)
• Adams/MechanismWorks for Solidworks (available with initial release)

Manually Importing Assemblies

The concept of assemblies within IGES only exists within the IGES CSG definition (Constructed Solid
Geometry; entity type 184). Adams/Exchange explodes all of the instances of the assembly into
individual Adams parts.
There are three methods of importing assemblies into Adams/View from an IGES file.
• Defining Levels Before Generating IGES File (this is the recommended method)
• Generating Separate IGES File
• Importing Assembly as One Part

The different method are explained in the next sections.

Defining Levels Before Generating IGES File

Defining levels in the IGES file is the best method to import an assembly into Adams/View. When using
this method, before importing the IGES file to Adams/View, place each part in the assembly that
 Exchanging Data in Adams 19
About Adams/Exchange

corresponds to an Adams/View part on a separate level. Refer to the CAD program that you are using to
generate the IGES file for information on IGES levels.
After you generate the IGES file with the parts separated by levels, import the file into Adams/View.
Follow the instructions in Import - STEP, IGES, DXF/DWG. or use the IGES FILE READ command once
for each part in the model using the PART_NAME parameter and the LEVEL parameter to ensure that
the geometry from the appropriate level is placed on the correct part. You might find it easier to use the
IGES FILE READ command than using the dialog box explained in the earlier section because you can
create a command file that repeats the IGES FILE READ command as necessary.
For example, if you wanted to import an assembly of a pendulum, you first generate the IGES file with
the ground part on level 1 and the pendulum on level 2. The complete geometric definition of the
pendulum assembly exists in the IGES file but the levels identify the geometry on the ground part and
the geometry on the pendulum part. Execute the following commands to read the IGES file and associate
the desired geometry with the appropriate part:
FILE GEOM READ TYPE=IGES FILE= "pendulum.igs" PART_NAME= /pend/ground LEVEL= 1
FILE GEOM READ TYPE=IGES FILE= "pendulum.igs" PART_NAME= /pend/mass LEVEL= 2

Generating Separate IGES File

The second method to import an assembly is to generate a separate IGES file for each part in the
assembly. For the previous example, you would generate two files: pendulum_ground.igs and
pendulum_mass.igs. You would then execute the following commands to read the IGES files and transfer
the geometry to the appropriate part:
FILE GEOMETRY READ TYPE=IGES FILE= "pendulum_ground.igs" PART_NAME= /pend/ground
FILE GEOMETRY READ TYPE=IGES FILE= "pendulum_mass.igs" PART_NAME= /pend/mass
This method has the advantage of not requiring the existence of levels in the IGES file but does require
that you create multiple IGES files.

Importing Assembly as One Part

The third method is to import the geometry for the entire assembly onto one part and then use
Adams/View commands to move the geometry to the appropriate part. This method is tedious if the IGES
file contains a large number of parts or a large number of geometric entities.

IGES Input Log File

Adams/Exchange generates a log file containing a list of any warnings or errors that may have occurred
during the translation to Adams/View. Adams/Exchange creates the log file in the current directory and
assigns it the same name as the IGES file with the extension .log.

Imported Mass Properties

Adams/Exchange does not support mass properties for IGES files if you import the geometry as a
polygon or if the original shape is not solid.
20 Adams/View
About Adams/Exchange

Imported Subfigures
Adams/Exchange does not support subfigures. Therefore, Adams/Exchange does not translate any
geometry defined as subfigures in an IGES file to Adams/View.

Exported IGES Levels

When Adams/Exchange exports geometry in IGES format, it places the geometry for each Adams/View
part on a separate level within the IGES file. This provides for easier handling of geometry for individual
parts after the IGES file has been written.
Adams/Exchange uses the Adams ID of the part as the integer ID identifying the IGES level. It writes
dynamic geometry (graphic spring dampers and outlines that span multiple parts) to a separate level with
an integer ID that is equal to 1 greater than the highest Adams part ID.

Exported Colors
Adams/Exchange writes the colors of geometric entities in Adams/View to the IGES file. It supports any
color defined within Adams/View. The RGB (red, green, blue) values are stored as entity number 314,
Color Definition, in the IGES file. Note that not all IGES vendors support RGB color values.

Exported Visibility
Adams/Exchange translates invisible geometric objects to the IGES file as blanked entities. The visibility
of the object as it appears in Adams/View determines how it is interpreted when written to the IGES file
as shown in the table below.

Adams/View visibility: IGES translation:

On Normal
Off Blanked
No Opinion Normal

Supported IGES Entities

A summary of the supported IGES entities is shown in the table below. Note that the three-dimensional
graphic icons representing Adams modeling elements (joints, and so on) are not translated to the IGES
file.

Adams/ View Entity type Import, export,

object: number: IGES entity: or both:
Arc 100 Circular arc Both
Circle 100 Circular arc Both
Graphic force 102 Composite curve Export
Spline 102 Composite curve Export
 Exchanging Data in Adams 21
About Adams/Exchange

Adams/ View Entity type Import, export,

object: number: IGES entity: or both:
Outline 102 or 106 Composite curve or Export
copious data
Polyline 102 or 106 Composite curve or Both
copious data
Ellipse/nurbcurve 104 Ellipse/nurb_curve Both
Block 106 Copious data Export
Cylinder 106 Copious data Export
Ellipsoid 106 Copious data Export
Extrusion 106 Copious data Export
Frustum 106 Copious data Export
Link 106 Copious data Export
Graphic spring 106 Copious data Export
damper
Revolution 106 Copious data Export
Shell 106 Copious data Export
Tire 106 Copious data Export
Torus 106 Copious data Export
Face (trimmed surf) 108:1 Plane Both
Polyline 110:0 Line Both
nurb_curve 112:0 Parametric spline Both
curve
nurb_surf 114:0 Parametric spline Both
surface
Marker 116 Point NS
Polyline 116:0 Point Import
nurb_surf 118 Ruled surface Import
nurb_surf 120:0 Surface of Import
revolution
nurb_surf 122:0 Tabulated cylinder Import
Explode 125:0 Flash entity Import
Polyline 125:2 Polyline Import
arc 125:3 Arc Import
polyline 125:4 Polyline Import
22 Adams/View
About Adams/Exchange

Adams/ View Entity type Import, export,

object: number: IGES entity: or both:
nurb_curve 126 Rational b-spline Import
curve
nurb_surf 128 Rational b-spline Import
surface
nurb_curve 130:0 Offset curve Import
explode 132:0 Connect point entity Import
nurb_surf 140:0 Offset surface Import
Chain 141:0 Composite edge Import
curve (boundary)
Chain 142:0 Composite edge Import
curve
Face 143:0 Bounded surface Both
Face 144:0 Trimmed parametric Both
surface
Solid 186:0 Manifold solid B- Import
rep object
Explode 202:0 Angular dimension Import
Explode 204:0 Curve dimension Import
Explode 206:0 Diameter dimension Import
106:11 and explode 208:0 Flag note Import
Explode 210:0 General label Import
Polyline 212 Polyline Import
Polyline 214 Leader Import
Explode 216 Linear dimension Import
Explode 220:0 Point dimension Import
Explode 222 Radius dimension Import
Explode 228 General symbol Import
106 and explode 230 Sectioned area Import
Explode 308:0 Subfigure definition Import
Explode 320:0 Network subfigure Import
definition
Explode 408:0 Singular subfigure Import
instance
 Exchanging Data in Adams 23
About Adams/Exchange

Adams/ View Entity type Import, export,

object: number: IGES entity: or both:
Explode 412:0 Rectangular array Import
subfigure
Explode 414:0 Circular array Import
subfigure
Explode 420:0 Network subfigure Import
instance

About STEP Import and Export

STEP is officially known as ISO 10303 - Exchange of Product Model Data. A summary of STEP is
provided in the ISO document, STEP Part 1: overview and fundamental principles. The following is a
paragraph from the ISO document describing STEP format.
The Standard for the Exchange of Product Model Data (STEP) is a neutral mechanism capable of
completely representing product data throughout the life cycle of a product (Neutral in this context
indicates independence from any particular CAx software system). The completeness of this
representation makes it suitable not only for neutral file exchange, but also as a basis for implementing
and sharing product databases and archiving. There is an undeniable need to transfer product data in
computer-readable form from one site to another. These sites may have one of a number of relationships
between them (contractor and subcontractor, customer and supplier); the information invariably needs to
iterate between the sites, retaining both data completeness and functionality, until it is ultimately
archived. The most cost effective manner to encapsulate such information is in a neutral format,
independent of any Computer-Aided (CAx) software system.
Contact the U.S. Product Data Association (USPRO) for more information on STEP. Their address is P.O
Box 3310, Gaithersberg, Maryland, 20885-3310. Their phone number is 301-975-4658, their FAX
number is 310-926-8730, and their e-mail is [email protected].

Imported Mass Properties

Adams calculates mass properties for parts using STEP geometry by multiplying the volume of the STEP
geometry by the material density defined in the Adams part. Mass properties that are explicitly defined
in Adams will continue to be used.

Supported STEP Entities

Adams/Exchange supports STEP applications protocols AP 203 and AP 214 for import and AP 203 for
export. A summary of the supported STEP entities is provided in the table below. Note that the three-
dimensional graphic icons representing Adams modeling elements (joints, and so on) are not translated
to the STEP file.
24 Adams/View
About Adams/Exchange

In addition, note that we do not support conformance class 5, which contains faceted B-rep shape
representations. AP 214 is still in the committee-draft stages of its development and, therefore, we do not
encourage its use.

Adams/View object: STEP entity: Import, export or both:

Arc step_circle Both
Polyline step_cartesian_point Import
Polyline step_line Both
Polyline step_polyline Both
Cone step_conical_surface Import
Cylinder step_cylindrical_surface Import
Ellipse step_ellipse Both
Sphere step_spherical_surface Import
Torus step_toroidal_surface Import
nurb_curve step_bezier_curve Import
nurb_curve step_b_spline_curve_with_knots Both
nurb_curve step_offset_curve_2d Import
nurb_curve step_offset_curve_3d Import
nurb_curve step_parabola Import
nurb_curve step_hyperbola Import
nurb_curve step_quasi_uniform_curve Import
nurb_curve step_rational_bezier_curve Import
nurb_curve step_rational_b_spline_curve_with_knots Both
nurb_curve step_rational_quasi_uniform_curve Import
nurb_curve step_rational_uniform_curve Import
nurb_curve step_trimmed_curve Import
nurb_curve step_uniform_curve Import
nurb_surf step_bezier_surface Import
nurb_surf step_offset_surface Import
nurb_surf step_b_spline_surface_with_knots Both
nurb_surf step_quasi_uniform_surface Import
nurb_surf step_rational_bezier_surface Import
nurb_surf step_rational_b_spline_surface_with_knot Both
s
nurb_surf step_rational_quasi_uniform_surface Import
 Exchanging Data in Adams 25
About Adams/Exchange

Adams/View object: STEP entity: Import, export or both:

nurb_surf step_rational_uniform_surface Import
nurb_surf step_rectangular_trimmed_surface Import
nurb_surf step_surface_of_linear_extrusion Import
nurb_surf step_surface_of_revolution Import
nurb_surf step_uniform_surface Import
Solid step_brep_with_voids Both
Solid step_manifold_solid_brep Both
Chain step_composite_curve Both
Face (trimmed surf) step_curve_bounded_surface Both

About DXF/DWG Import and Export

Adams/Exchange imports and exports geometry in DXF/DWG file format. A summary of the supported
DXF/DWG entities is provided in the table below. Note that the three-dimensional graphic icons
representing Adams modeling elements (joints, and so on) are not translated to the DXF/DWG file.
Contact Autodesk, Inc. for more information on the DXF and DWG file formats. Their address is 111
McInnis Parkway, San Rafael, California, 94903. Their telephone number is 415-507-5000 and their
FAX number is 415-507-5100. Autodesk has a web site at http://www.autodesk.com.

Adams/View object: DXF/DWG entity: Import, export or both:

Arc dxf_arc Both
Circle dxf_circle Both
Polyline dxf_2dpolyline Import
Polyline dxf_3dpolyline Both
Polyline dxf_line Both
Polyline dxf_point Import
Polyline dxf_polygon_mesh Import
Ellipse dxf_ellipse Both
nurb_curve dxf_bezier_bspline_curve Import
nurb_curve dxf_bspline_curve Both
nurb_curve dxf_spline Import
nurb_curve dxf_spline_fit Import
Shell dxf_3dface Import
Shell dxf_polyface_mesh Import
26 Adams/View
About Adams/Exchange

Adams/View object: DXF/DWG entity: Import, export or both:

nurb_surf dxf_2dpolyline_ext Import
nurb_surf dxf_3dface_ext Import
nurb_surf dxf_3dpolyline_ext Import
nurb_surf dxf_arc_ext Import
nurb_surf dxf_bezier_bspline_curve_ext Import
nurb_surf dxf_bezier_bspline_surf Import
nurb_surf dxf_bezier_bspline_surf_ext Import
nurb_surf dxf_bspline_curve_ext Import
nurb_surf dxf_bspline_surf Import
nurb_surf dxf_bspline_surf_ext Import
nurb_surf dxf_circle_ext Import
nurb_surf dxf_circle_ext Import
nurb_surf dxf_ellipse_ext Import
nurb_surf dxf_line_ext Import
nurb_surf dxf_point_ext Import
nurb_surf dxf_polyface_mesh_ext Import
nurb_surf dxf_polygon_mesh_ext Import
nurb_surf dxf_spline_ext Import
nurb_surf dxf_spline_fit_ext Import
Explode dxf_block Import
Explode dxf_insert Import
Chain dxf_curve_fit Both
 Exchanging Data in Adams 27
Recommendations for Exporting CAD Data

Recommendations for Exporting CAD Data

The following sections provide recommendations for how you should export data from different CAD
packages so you can best import them into Adams:
• General Comments on Exporting
• Table of Recommendations for Exporting CAD Data

General Comments on Exporting

For those CAD systems based on the Parasolids kernel, there are many benefits to transferring geometry
in Parasolid files. Adams/View creates solid bodies from the Parasolids information that allows for
further Boolean operations as well as the selection of geometric features such as the center of a circle. It
is important that you export the version of the Parasolids file that Adams/View supports.
In general, the simpler the representation of the geometric information the better. This is why we often
recommend that you used Stereolithography over formats such as IGES and STEP. Other simple formats
include render and shell files. Shell files are Adams-specfic so you will not find them as part of the
standard CAD export formats. Please remember that some of these formats do not have colors.
Successful transfer of IGES and STEP files from CAD systems to Adams/View depends on both systems.
Some CAD systems export information that is easily processed by Adams/View while others CAD
systems generate files that are difficult or impossible for Adams/View to import. We have taken this into
consideration in the Recommendations for Exporting CAD Data.

Recommendations for Exporting CAD Data

The following table provides recommendations for the file formats in which you should export data from
a CAD program so you can import it effectively into Adams. Please note that the recommendations are
28 Adams/View
Recommendations for Exporting CAD Data

in order of preference. For a comparison of the different file formats, see Comparison of CAD File
Formats.

For the CAD Recommendations in order

package: of preference: Comments:
Unigraphics (UG) Export from UG/Mechanism or • Exporting from the embedded motion
Scenario for Motion in these file products automates the geometry
formats in order of preference: export/import process. Only three-
dimensional solids are transferred.
• Parasolids
• Using Parasolids (without the
• Stereolithography embedded motion products) is
Or, export from UG in these file convenient because one file contains
formats in order of preference: all the geometry and Adams/Exchange
creates a separate part for each solid.
• Parasolids • Stereolithography is dependable but
• Stereolithography requires you to output each part
separately. It only works on solid
bodies.
CATIA Export using CAT/Adams in these • Exporting from the embedded motion
file formats in order of preference: product automates the geometry
export/import process. It transfers
• Quickshell two-dimensional and three-
• STEP dimensional geometry.
• IGES • IGES and STEP export is time
consuming and Adams/Exchange can
Or, export from CATIA in these
have difficulties reading the resulting
formats in order of preference:
files.
• Stereolithography
• STEP
• IGES
I-DEAS Export using Mechanism Design or • Exporting from the embedded motion
Mechanism Simulation export with product automates the geometry
shells. export/import process.
• IGES geometry transfer is without
Or, export from I-DEAS in these
colors.
formats in order of preference:
• Stereolithography only works for a
• Stereolithography part, not an assembly.
• IGES
 Exchanging Data in Adams 29
Recommendations for Exporting CAD Data

For the CAD Recommendations in order

package: of preference: Comments:
Pro/ENGINEER Export using MECHANISM/Pro in • Exporting from the embedded motion
these formats in order of product automates the geometry
preference: export/import process.
• Render files contain color, while
• Render
Stereolithography files do not.
• Stereolithography
Or, export from Pro/ENGINEER in
these formats in order of
preference:

• Render
• Stereolithography
• IGES
Solidworks Export using Dynamic Designer • Exporting from the embedded motion
with Shells (v2000) product automates the geometry
export/import process.
Or, export from Solidworks in
• Using Parasolid is convenient because
these formats in order of
one file contains all the geometry and
preference:
Adams/Exchange creates a separate
• Parasolid part for each solid.

• Stereolithography • Stereolithography is dependable but

requires you to output each part
• IGES separately. It only works on solid
bodies.
SolidEdge Export using Dynamic Designer • Exporting from the embedded motion
with Shells (v2000). product automates the geometry
export/import process.
Or, export from SolidEdge in these
• Using Parasolid is convenient because
file formats in order of preference:
one file contains all the geometry and
• Parasolids Adams/Exchange creates a separate
part for each solid.
• Stereolithography
• Stereolithography is dependable but
• IGES requires you to output each part
separately. It only works on solid
bodies.
30 Adams/View
Recommendations for Exporting CAD Data

For the CAD Recommendations in order

package: of preference: Comments:
Mechanical Export using Dynamic Designer • Exporting from the embedded motion
Desktop with Shells (v2000). product automates the geometry
export/import process.
Or, export from Mechanical
• IGES transfers are complicated but are
Desktop in these file formats in
reasonably dependable.
order of preference:
• Stereolithography exports are
• IGES unpredictable because the model has
• Stereolithography to be in a particular quadrant before
exporting.
• DXF
• DXF can be used to transfer two-
dimensional information.
Microstation Parasolid Using Parasolid is convenient because
one file contains all the geometry and
Adams/Exchange creates a separate part
for each solid.