Configuring Templates-ADAMS

Configuring Template-
Based Products
About This Guide 3
Introducing Management Tasks and Tools 5
Managing Databases 9
Publishing to Databases 23
Working With Configuration Files 27
Standard Table Directory Entries 45

2 Configuring Template-Based Products
Copyright
U.S. Government Restricted Rights: If the Software and Documentation are provided in connection with a government
contract, then they are provided with RESTRICTED RIGHTS. Use, duplication or disclosure is subject to restrictions
stated in paragraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at 252.227-7013.
Mechanical Dynamics, Incorporated, 2300 Traverwood Drive, Ann Arbor, Michigan 48105.
The information in this document is furnished for informational use only, may be revised from time to time, and should
not be construed as a commitment by Mechanical Dynamics, Incorporated. Mechanical Dynamics, Incorporated,
assumes no responsibility or liability for any errors or inaccuracies that may appear in this document.
This document contains proprietary and copyrighted information. Mechanical Dynamics, Incorporated permits
licensees of ADAMS® software products to print out or copy this document or portions thereof solely for internal use
in connection with the licensed software. No part of this document may be copied for any other purpose or distributed
or translated into any other language without the prior written permission of Mechanical Dynamics, Incorporated.
©2002 by Mechanical Dynamics, Incorporated. All rights reserved. Printed in the United States of America.
ADAMS ® is a registered United States trademark of Mechanical Dynamics, Incorporated.

All other product names are trademarks of their respective companies.
Part number: 120TEMCN-01

Configuring Template-Based Products 3
About This Guide
About This Guide
Welcome to Configuring ADAMS Template-Based Products

Welcome to the ADAMS template-based products: ADAMS/Aircraft, ADAMS/Car,
ADAMS/Driveline, ADAMS/Engine powered by FEV, and ADAMS/Rail. The template-
based products are Mechanical Dynamics’ (MDI) industry-specific virtual prototyping
software.
The template-based products expand the full-simulation package to provide you with
standard building blocks and analyses, so you can rapidly prototype your real system, such
as engines, car suspensions, and rail cars. They offer fully parametric modeling
techniques, so for example, if you move one entity, its dependents move accordingly.
The template-based products consist of two interfaces: Standard Interface and Template
Builder. This guide introduces you to the Template Builder interface, provides an
overview of the system architecture, and explains the role of communicators. The
information in this guide is common to all template-based products. For information
specific to a certain template-based product, please see the guides associated with that
product:
■ Road Map to ADAMS/Aircraft Documentation
■ Road Map to ADAMS/Car Documentation
■ Road Map to ADAMS/Driveline Documentation
■ Road Map to ADAMS/Engine Documentation
■ Road Map to ADAMS/Rail Documentation
This guide describes how you can manage the files, users, and configurations of template-
based products.
What This Guide Assumes

This guide assumes you know the basics of using your template-based product. For an
introduction to your template-based product, see its getting started guide.
About This Guide
1 Introducing Management Tasks
and Tools
Overview
The ADAMS template-based products provide a powerful
modeling and simulating environment that helps you to build,
simulate, and refine your systems. This chapter gives you an
overview of how you can efficiently manage the environment
of your template-based product.
■ About the Management Tasks, 6
■ Accessing the Management Tools, 7

Introducing Management Tasks and Tools
About the Management Tasks

When you start your template-based product, it automatically creates the necessary files
for you to begin working immediately. As you become more familiar with your template-
based product, you may find that you want to set up custom private versions of it or change
the way it is configured. In addition, you may want to set up custom site versions that all
users can share.
The template-based products let you do these different management tasks depending on
the type of user privileges you have been assigned. You should give one user, who has
expert privileges, the responsibility of managing the site version, if you have one, of your
template-based product so only one user, the site manager, makes changes.
Table 1 lists the different management tasks that you can perform depending on your user
privileges. You can perform many of these tasks using the menus in your template-based
product. Other tasks require you to set variables in different configuration files.
Table 1. Management Tasks by User Type
This type of user: Can:
Standard user ■ Create and set up private databases in which to store files,
such as subsystems and templates, with which you are
working.
■ Make copies of files in your private database or copy the
entire database to share with other users.
■ Configure the operation of your template-based product for
your private use.
Expert user ■ Perform the same tasks as a standard user.
■ Publish a template so all users can use it.
Site manager ■ Set up site databases in which general project information is
stored.
■ Define the access that users can have to functionality.
■ Set up a custom version of your template-based product and
configure its operation.
■ Assigns privileges to common databases to allow read and
write permissions for standard and expert users.
Accessing the Management Tools

Your access to management tools depend on your user access.
■ Standard users - You can access your template-based product’s tools that let
you manage your private database. The tools are under the Tools menu.
■ Expert user - You can access the management tools from the Tools menu.
To get expert privileges, modify your private .acar.cfg configuration file, and
change your user mode to EXPERT. For more information, see Working With
Configuration Files on page 27.
2 Managing Databases
Overview
This chapter describes the structure of databases and the
procedures to manage them.
■ Overview of Database Management, 10
■ Managing Databases, 14
■ Setting Up the Search List and Order, 17

Managing Databases
Overview of Database Management

ADAMS template-based products define assemblies using several different files. The files
define the topology, dynamic element characteristics, analysis information, and more.
Your template-based product stores these files in hierarchical databases. The next sections
explain more about the databases in which these files are stored:
■ Types of Databases, 10
■ Database Structure, 11
■ About the Database Search List, 13
Types of Databases
ADAMS template-based products provide two types of default databases:
■ Private database for each user - A private database is for your personal use.
You can store and retrieve data from your private database. In addition, you can
share your private database with others. If a private database does not exist,
your template-based product creates the private database at the beginning of a
session.
■ Shared database for all users - A shared database provides all users with
access to standard, accurate data. To prevent loss of data or the storing of
inaccurate data in a shared database, standard users can only retrieve data from
a shared database. Only an expert user, typically the site manager, has the
permissions necessary to create files in a shared database. An example of a
shared database is distributed with your template-based product, and it is
usually placed in the installation directory.
Managing Databases
Database Structure
Each database consists of one directory (*.cdb) and several subdirectories (*.tbl), called
tables. Each subdirectory contains files for specific types of components, such as springs
and dampers, or files for performing tests, such as loadcases and wheel envelopes. The
number of tables varies, but you can define the number in the shared and private
configuration files.
By default, your template-based product divides a database into the following table
elements:
■ Models and topological information (templates, assemblies, subsystems, and
flexible bodies)
■ Analysis information (such as analysis scripts, loadcases, driver loadcases, and
suspension curves)
■ Postprocessing (plot configuration files)
■ In ADAMS/Car, driver files (such as driver inputs and roads)
■ In ADAMS/Car, tires and roads
■ Property files (such as springs, dampers, and remaining tables)
Each type of file that a table stores has a unique three-letter extension that identifies its
contents. For example, all files stored in the assembly table contain a .asy extension.
An example of the default structure of a database for ADAMS/Car is shown in the
information window in Figure 1 on page 12. The information window shows all the tables
in the database, their names, the type of files they store, and the file extension of the files
that they store.
You can also add your own tables since the database is an open-architecture file repository.
For example, you might want to create a table that stores data files for an analysis that is
specific to your company. For more information on managing tables, see Managing Tables
Through Configuration Files on page 41.
Managing Databases
Figure 1. Database Structure

Managing Databases
About the Database Search List

During startup, your template-based product stores any databases that are defined in your
private, site, and shared configuration files in its search list. The databases in the search
list are the only databases that appear in dialog boxes when you select to display databases
and files, such as subsystem or property. For example, when you want to change the
database to which you can write files, your template-based product only displays those
databases in its search list in the dialog box as shown below.
Figure 2. Example of Database Search List
Databases on CDB
search list
Your template-based product searches the databases in its search list using a search order
that you can modify.
You can change the databases in the search list and their search order either by using the
menus or by editing the configuration files directly. All configuration files can define the
databases, including the private, site, and shared configuration files.
For your template-based product to be able to store a database in its search list, the file
system to which the database points must be accessible on the current file system of the
computer.
For more information on configuration files, see Working With Configuration Files on
page 27. For information on setting up the search list and the order in which databases are
searched, see Setting Up the Search List and Order on page 17.
Managing Databases
Managing Databases
The next sections outline the operations that you can perform on databases:
■ Creating Databases During a Session, 14
■ Setting the Writable Database, 15
■ Managing Tables in a Database, 16
■ Creating Tar Files of Databases, 16
Creating Databases During a Session

You can create a new database anytime during a session. When you create a database, your
template-based product adds it to its search list and places the database at the lowest level
in its database search order. Your template-based product also creates database tables
within the new database according to the table information stored in your private, site, and
shared configuration files. For more information on search order, see About Search Order
on page 17.
Note: Unless you save database changes to your private configuration file,
ADAMS/Solver will not be able to access the databases you added or created in a
session.
You should create a database for every project on which you are working. By creating
separate databases for each project, you can ensure that the property files belonging to
different subsystems are kept separate.
When you create a database, you define two elements for it:
■ Name - You use the name, or database alias, to select the database from the
search list in dialog boxes.
■ Path - The location of the database in the file system.
Note: You can also create databases directly using the configuration files. For more
information, see Managing Databases Through Configuration Files on page 39.
Managing Databases
To create a database:
1 From the Tools menu, point to Database Management, and then select Create Database.
The Create New Database dialog box appears.
Tip: For more information on any dialog box, press F1 when the dialog box is
active.
2 In the Database Name text box, enter the name you want to assign to the database.
The name does not necessarily have to match its file system name.
3 In the Database Path text box, enter the location of the database in the file system.
4 Select OK.
Setting the Writable Database

You can set up one of your active databases as the repository for templates, subsystems,
and property files. This database is called your default writable database. The default
writable database is defined in your private configuration file, but you can change it at
anytime during a session. You can select any database in the search list as your default
writable database, as long as you have permission to write to the file system to which the
database points.
To set the writable database:
1 From the Tools menu, point to Database Management, and then select Default Writable.
The Set Default Writable Database dialog box appears.
active.
2 From the Database Name option menu, select the database that you want to set as the
default writable database. Only those databases to which you have write
permission appear in the list.
3 Select OK.
Managing Databases
Managing Tables in a Database

You can add your own tables to a database. You use the configuration files to define the
tables that you want to include in a database. For more information on configuration files
and table definitions in them, see Managing Tables Through Configuration Files on
page 41.
Creating Tar Files of Databases

On UNIX, you can create a tar file of any database that is listed in the search list. When
you create a tar file of a database, your template-based product groups together all of the
database’s subdirectories and files into one tar file. It then writes the tar file to the default
writable database using the name database_name.tar, where database_name is the name
of the database you saved.
Saving a database as a tar file is an efficient way to save a snapshot of the current state of
a database or to transfer the database to an external file system. You can easily transfer the
databases through e-mail or through a file transfer protocol (ftp) process.
As you create a tar file, you can select to encode and compress the database using standard
UNIX compression and encoding techniques.
To create a tar file of a database in UNIX:
1 From the Tools menu, point to Database Management, and then select Bundle Database.
The Bundle X Database dialog box appears, where X represents the name of your
template-based product.
active.
2 Set Database Name to the database you want to bundle into a tar file. If the desired
database is not on the list, add it to the list as explained in Creating Databases
During a Session on page 14.
3 Select the appropriate check boxes if you want to compress or encode the file.
Note that the resulting file will have the appropriate file extensions if you select to
encode (*.uu) or compress (*.Z) the files.
4 Select OK.
Managing Databases
Setting Up the Search List and Order

As explained in About the Database Search List on page 13, your template-based product
stores in its search list, all the databases currently defined in your configuration files.
When you request a file from the databases, your template-based product uses a defined
search order to search the databases for the requested file. The next sections explains more
about the search order, how it impacts you, and how you set it up:
■ About Search Order, 17
■ Adding Databases to the Search List, 18
■ Removing Databases from the Search List, 19
■ Changing the Search Order, 20
About Search Order

During a session, you can have many databases listed in the search list. Your template-
based product assigns to each database in the search list a numerical value representing its
place in the search order. For example, if there are three databases in your search list, your
template-based product numbers them 1, 2, and 3, with 1 representing the first database it
searches.
When you request a file, such as a property file, your template-based product searches the
databases in the specified search order. It first tries to open the file as specified. If the
filename has a database alias, your template-based product expands it to a full file system
path.
If your template-based product cannot find the file in the specified database, it begins
searching the other databases in its search list in the search order. Your template-based
product begins with the first database in the search order. It continues through all the
databases in the search order until it finds a matching filename.
Your private configuration file sets the search order of these databases, but you can change
it at anytime during a session.
Managing Databases
Note that in many cases changing the database search order can cause your template-based
product to find a different file. For example, if two databases contain a file with the same
name but with different data, changing the search order may change which file your
template-based product uses. You may find this helpful in many cases, but it can produce
unintended results when you change the search order without realizing that you can access
different files. The database search order is also important if you specify the database path
incorrectly.
To avoid using the search order to find a file, which can result in longer searches and
unintended results, you can specify the database name (its alias) directly in the associated
property file to ensure that your template-based product searches the correct database.
You can look at the search order of the databases in the search list using the Database Info
command, as shown in Viewing Database and Table Information on page 21. Your
template-based product displays the current list of databases, showing the search order
level of each database in the first column. For more information on displaying database
information, see Viewing Database and Table Information on page 21.
Adding Databases to the Search List

As you are working with your template-based product, you can add databases to the
current search list. Your template-based product adds the databases to the end of the search
order. To change the search order, see Changing the Search Order on page 20.
To add a database to the search list:
1 From the Tools menu, point to Database Management, and then select Add to Search.
The Add Database to Search dialog box appears.
active.
2 In the Database Name text box, enter the name of the database.
3 In the Database Path text box, enter the location of an existing database in the file
system.
4 Select OK.
Managing Databases
Removing Databases from the Search List

You can remove a database from the search list so that your template-based product does
not search for files in it. Removing a database from the search list does not remove the
database from the file system.
If you want to remove the current default writable database from the search list, you must
first specify another database as the default writable database. For more information on
default writable databases, see Setting the Writable Database on page 15.
To remove a database from the search order:
1 From the Tools menu, point to Database Management, and then select Remove from
Search.
The Remove Database from Search dialog box appears.
active.
2 Set Database Name to the database you want to remove.

3 Select OK.
Managing Databases
Changing the Search Order

You can change the order in which your template-based product searches databases for
files. For more information on search order, see About Search Order on page 17.
To change the search order:
1 From the Tools menu, point to Database Management, and then select Change Search
Order.
The Change Database Search Order dialog box appears.
active.
2 Set Database Name to the database whose order you want to change.
3 To view the current search order of databases, select Database Info.
4 In the Level text box, enter a numerical value representing the level of the database
in the new search order.
5 Select OK.
Managing Databases
Viewing Database and Table Information

You can view the current set of databases in the search list. The information includes the
database names, file system paths, and levels in the current search order. You can also
view the table structure of the current writable database.
To view database information:
1 From the Tools menu, point to Database Management, and then select Database Info.
2 View the database information, and then select Close.
active.
To view the tables in the writable database:
1 From the Tools menu, point to Database Management, and then select Table Info.
2 View the table information, and then select Close.
Saving Database Management Changes

At any point during a session, you can save the list of databases that is currently available
during the session and the search order to your private configuration file. For more
information on private configuration files, see About Private Configuration Files on
page 29.
To save database management changes:

■ From the Tools menu, point to Database Management, and then select Save
Configuration.
Managing Databases
3 Publishing to Databases
Overview
This chapter explains how you can publish a subsystem or an
assembly to an existing database so other users can share it.
■ Publishing a Subsystem, 24
■ Publishing an Assembly, 25
Publishing to Databases
Publishing a Subsystem
When you publish a subsystem, you copy the subsystem file and all its associated property
files to the target database. You can also select to publish the subsystem’s template file.
As you publish the subsystem, you can choose to write over existing files or create
backups of the files.
The subsystem you are publishing must be currently opened in the standard interface, and
the target database must be writable. For more information on writable databases, see
Setting the Writable Database on page 15.
You can also publish an entire assembly. For more information, see Publishing an
Assembly on page 25.
To publish a subsystem:
1 From the Tools menu, point to Database Management, and then select Publish
Subsystem.
The Publish an Open Subsystem dialog box appears.
active.
2 Set Subsystem Name to the name of the subsystem you want to publish.
3 Depending on whether or not you want to overwrite or create backups of the files
currently in the database, set Write Mode to overwrite or backup.
4 Set Target Database to the desired target database. If the desired database is not on
the list, add it to the list as explained in Setting Up the Search List and Order on
page 17.
5 If you want to include the template associated with the subsystem, select Include
Template File.
6 Select OK.
Publishing an Assembly
When you publish an assembly, you copy each subsystem file included in the assembly
definition, including the associated property files for each subsystem, to the target
database. You can also select to publish each subsystem’s template file. As you publish
the assembly, you can select to write over existing files or create backups of the files.
The assembly you are publishing must be currently opened in the standard interface, and
the target database must be writable. For more information on writable databases, see
Setting the Writable Database on page 15.
You can choose to publish only a subsystem, not an entire assembly. For more information
see Publishing a Subsystem on page 24.
To publish an assembly:
1 From the Tools menu, point to Database Management, and then select Publish Assembly.
The Publish an Open Assembly dialog box appears.
active.
2 Set Assembly Name to the name of the assembly you want to publish.
3 Depending on whether or not you want to overwrite or create backups of the files
currently in the database, set Write Mode to overwrite or backup.
4 Set Target Database to the desired target database. If the desired database is not on
the list, add it to the list as explained in Setting Up the Search List and Order on
page 17.
5 If you want to include each template associated with the individual subsystems,
select Include Template File.
6 Select OK.
4 Working With Configuration Files
Overview
This chapter explains how to set up your template-based
product using configuration files. It introduces you to the
concepts of private, site, and shared configuration files, and
explains how you customize the configuration files to set up
the environment of your template-based product.
■ About Configuration Files, 28
■ Format of Configuration Files, 31
■ Using Configuration Files to Set Up Your Template-

Based Product, 33
Working With Configuration Files
About Configuration Files

Your template-based product’s configuration file contains information that your template-
based product reads during startup to correctly initialize the session. Your template-based
product looks for the following configuration files when it starts up: shared, site (if it
exists), and private configuration files, in that order.
The private configuration file contains personal settings that are then merged with the
general settings defined in the shared or site configuration file. Together, the settings
define your work environment. The shared and private configuration files are required,
while the site configuration file is optional. You use the site configuration file only if you
want to set up a custom version that all users can access.
To personalize the settings in the configuration files, you edit the configuration file using
a text editor. You can, however, use the menus to set up the databases without having to
directly edit the configuration files. See Managing Databases on page 9.
Each of the configuration files is explained in the next sections:
■ About Private Configuration Files, 29
■ About the Site Configuration File, 30
■ About the Shared Configuration File, 30

About Private Configuration Files

As an expert or standard user, you have your own private configuration file with a default
name of .acar.cfg. Your template-based product accesses this file at the beginning of every
session. The private configuration file is found at $HOME/.acar.cfg, where $HOME is the
location of your home directory.
If you have more that one private configuration file, you can choose the file you want to
use for a given session. Depending on the platform you are using, you do the following:
■ On UNIX - You use the Registry Editor on the ADAMS Toolbar to choose the
file you want to use. The registry setting name for your private configuration
file is privateCfg. For more information on the Registry Editor, see Making
Choices and Entering Files in the Registry Editor on page 9, in the guide,
Running and Configuring ADAMS on UNIX.
■ On Windows - You can specify the private configuration file using an
environment variable. You can set this environment variable using the System
option from the Control Panel, just as you would for any other variable.
Depending on your template-based product, you can specify the following
environment variables:
❖ For ADAMS/Aircraft, enter MDI_AIR_PRIVATE_CFG
❖ For ADAMS/Car, enter MDI_ACAR_PRIVATE_CFG
❖ For ADAMS/Engine, enter MDI_AENG_PRIVATE_CFG
❖ For ADAMS/Rail, enter MDI_RAIL_PRIVATE_CFG
You should set up your private configuration file so it contains information specific to the
work you are performing. For example, you can set up your own tables in databases in
which to store project data. You can also override many of the default settings provided in
the shared and site configuration files.
About the Site Configuration File

If you create a site configuration file, you call it acar.cfg, and place it in the template-based
product site repository. You can have only one site configuration file for a site installation
of your template-based product. The site configuration file provides settings common to
users at a particular site. For more information on the location of the site repository, see
Organizing Custom Binaries and Libraries on page 32 in the guide, Customizing Template-
Based Products.
For example, your company may have engineers working across a network, each wanting
to access some common information, such as files and variables. You could set up the site
configuration file so that when they run the site version, each engineer’s session is
configured to access the common information.
Note: We recommend that only the site manager changes the site configuration file.
You should make any personal modifications using private configuration files.
About the Shared Configuration File

The shared configuration file is called acar.cfg, and is generally found in the installation
directory. See your system administrator for location details.
Only one shared configuration file exists for an installation of your template-based
product. The shared configuration file contains predefined information common to all
users.
Note: We recommend that no one changes the shared configuration file. You should
make any personal modifications using private configuration files.
Format of Configuration Files

A configuration file is divided into the blocks listed below. An example of the blocks in a
configuration file are shown in Figure 3 on page 32. In the example, ! indicates comments.
■ Environment Variables - The first block in a configuration file sets up the
environment of your template-based product. For example, it identifies the type
of user associated with the configuration file. It also sets the mode in which
your template-based product starts, Standard Interface or Template Builder, and
any other environment settings.
■ Databases - The second block defines the databases in which users store files,
the order in which your template-based product searches databases, and the
database to which files are written by default.
■ Table Directories - The third block defines the list of personal table directories.
For example, you could create a table in which to store examples.
■ Property Files - The fourth block contains a listing of default property files.
When a dialog box requires a property file, it automatically knows to load the
desired files if you enter property files in the property file block. You usually
define property files in the shared configuration file. If you enter values in your
private configuration file, your template-based product overrides the shared files
with your personal property files.
■ Test Rigs - The fifth block defines the default test rig for a given assembly
class. When a dialog box requires a test rig, it automatically knows to load the
desired test rigs. You usually define test rigs in the shared configuration file.
Figure 3. Configuration File Blocks

!-----------------------------------------------------------------------------------------------!
! ********************* ADAMS/X Configuration File ******************* !
!-----------------------------------------------------------------------------------------------!
!-----------------------------------------------------------------------------------------------!
! - List of personal environment variables
!-----------------------------------------------------------------------------------------------!
ENVIRONMENT MDI_ACAR_USERMODE expert
!-----------------------------------------------------------------------------------------------!
! - List of personal database directories
! Database name Path of Database
!------------------------------------------------------------------------------------------------!
DATABASE private /usr/private.cdb
DATABASE staff /staff/private.cdb
DEFAULT_WRITE_DB private
!
!-----------------------------------------------------------------------------------------------!
! - Desired database search order
!-----------------------------------------------------------------------------------------------!
DATABASE_ORDER shared, private, mkrueger
!
!-----------------------------------------------------------------------------------------------!
! - List of personal tables directories
! Type class Name of table Extension
!-----------------------------------------------------------------------------------------------!
! Example table entry:
!TABLE example example.tbl exa
!
!-----------------------------------------------------------------------------------------------!
! - List of personal default property files
! Type class Default property file
!-----------------------------------------------------------------------------------------------!
! Example property file entry:
!PROPFILE assembly <private>/assembly.tbl/myfile.dpr
!
! Example test rig entry:
!TESTRIG four_post .__MY_FOURPOST
Using Configuration Files to Set Up Your Template-Based

Product
The next sections explain how to use configuration files to set up your template-based
product:
■ Setting Up the Environment Through Configuration Files, 33
■ Managing Databases Through Configuration Files, 39
■ Managing Tables Through Configuration Files, 41
■ Managing: Property Files Through Configuration Files, 43
Setting Up the Environment Through Configuration Files

You need to set a standard set of ENVIRONMENT keyword entries in a configuration file.
The entries have the following format:
ENVIRONMENT VARIABLE_NAME VARIABLE_VALUE
We’ve set up default environment variables in the shared configuration file, but we
recommend that you redefine them in the private or site configuration file to customize the
work environment of your template-based product. You can also define your own
environment variables for use with user-written subroutines or macros.
The next sections explain the standard environment entries that you can set and how to
create your own environment variables:
■ Setting User Privileges, 34
■ Accessing ADAMS/View, 35
■ Setting Defaults in the Welcome Dialog Box, 35
■ Setting the Display of the Welcome Dialog Box, 36
■ Replacing the Image on the Welcome and Exit Dialog Boxes, 36
■ Setting Up Side Preferences, 36
■ Setting the Orientation of the Global Reference Frame, 37
■ Managing Result File Output, 37

■ Automatically Executing an ADAMS/Rail Command File, 38
■ Defining Your Own Environment Keywords, 38
Setting User Privileges

Your template-based product allows different access to its modules and commands
depending on the type of user privileges that you assign. For example, it allows users with
expert privileges, called expert users, to create and publish templates and view and modify
macros.
Your template-based product has two modes:
■ Standard Interface in which standard users create and analyze virtual
prototypes of suspensions, steering systems, and full vehicles based on existing
templates.
■ Template Builder in which expert users create new templates or modify
existing ones.
You use the MDI_ACAR_USERMODE keyword in the private configuration file to set the
users’ access to the Template Builder and other development tools. You can set
USERMODE to:
■ STANDARD - User can only access the Standard Interface.
■ EXPERT - User can access the Template Builder and create and modify
templates. User can access the Template Builder and other development tools
that are located under the Tools menu. Expert users can use the
MDI_ACAR_PLUS_AVIEW keyword in the private configuration file to access
ADAMS/View. For more information, see Accessing ADAMS/View on page 35.
To change the value of this keyword, you need to edit the private configuration file using
a text editor and modify the corresponding string. In ADAMS/Car for example, the
following gives a user expert privileges:
! Desired user mode (standard/expert)
ENVIRONMENT MDI_ACAR_USERMODE expert
When you start a new session, your template-based product reflects the changes to the
private configuration file.
Accessing ADAMS/View
If you are an expert user, you can use the MDI_ACAR_PLUS_AVIEW keyword in the
private configuration file to obtain access to ADAMS/View.
MDI_ACAR_PLUS_AVIEW has the following format:
ENVIRONMENT MDI_ACAR_PLUS_AVIEW (yes, no)
To access ADAMS/View:
1 Set MDI_ACAR_PLUS_AVIEW to yes.

2 From the Tools menu, select ADAMS/View Interface.
To return to your template-based product:

■ From the Tools menu, point to Select Mode, and then select the mode to which you
want to return: Standard Interface or Template Builder.
Setting Defaults in the Welcome Dialog Box

You can use the MDI_ACAR_INITMODE keyword to set the default selection in the
Welcome dialog box when the user has expert privileges. MDI_ACAR_INITMODE has the
following format:
ENVIRONMENT MDI_ACAR_INITMODE (template_builder, standard_interface)
In ADAMS/Car for example, if you set MDI_ACAR_INITMODE to standard_interface, the

Welcome dialog box sets the selection of Standard Interface as the default, as shown next.
Figure 4. Welcome Dialog Box
Setting the Display of the Welcome Dialog Box

You can use the MDI_ACAR_MODEPROMPT keyword to set your template-based product
so that it does not display the Welcome dialog box (see the ADAMS/Car dialog box shown
in Figure 4 on page 35) at start up. MDI_ACAR_MODEPROMPT has the following format:
ENVIRONMENT MDI_ACAR_MODEPROMPT (yes, no)
Setting it to yes displays the Welcome dialog box; setting it to no turns off the display of
the Welcome dialog box.
Replacing the Image on the Welcome and Exit Dialog Boxes

You can replace the image on the Welcome and Exit dialog boxes with any image that you
prefer.
To replace the image:
1 Create a color X pixmap image (.xpm) with a size of approximately 197x192

pixels.
2 Copy the new pixmap file to a designated directory.
3 Add the following entry in your .acar configuration file:
ENVIRONMENT MDI_ACAR_LOGO_BMP <your_directory/filename>
Setting Up Side Preferences

You can use the MDI_ACAR_SIDE_PREF keyword entry to define the preferred side for
creation. When you set the side preferences:
■ The creation dialog box in the Template Builder sets the default type based on
the side preference you set.
■ The guesses in the pop-up menus in dialog boxes only contain left and single or
right and single entities based on the side preference. Your template-based
product does this to limit the number of guesses.
The MDI_ACAR_SIDE_PREF keyword entry has the following format:
ENVIRONMENT MDI_ACAR_SIDE_PREF (right, left)
Setting the Orientation of the Global Reference Frame

You can set the orientation of the global reference frame using direction cosines. You use
either of the following keywords to define the orientation:
ENVIRONMENT MDI_ACAR_VEHICLE_REAR 1,0,0
ENVIRONMENT MDI_ACAR_VEHICLE_LEFT 0,-1,0
Managing Result File Output

Result files include all the simulation output from an analysis. The following environment
keyword sets the default attribute of whether the result file is output during the analysis. If
the assembled model contains flexible bodies, your template-based product automatically
outputs a result file regardless of the keyword setting.
If the assembled model does not contain flexible bodies, use the following command
(example is for ADAMS/Car) to indicate that you want your template-based product to
output a result file:
ENVIRONMENT MDI_ACAR_WRITE_RES (yes, no)
If a result file exists, your template-based product will automatically read it in with the
analysis, if you run an interactive simulation.
If you run the simulation externally (background, files_only), you can read in the result
file using either of these two methods:
■ Review -> Analysis Management -> Read
■ File -> Import -> ADAMS Results File (*.res)
For ADAMS/Rail, you can decide not to write the result file, even if a flexible body exists
in the model setting the environment:
ENVIRONMENT MDI_ARAIL_NORES (yes, no)
where the default is no.
Automatically Executing an ADAMS/Rail Command File

This information pertains only to ADAMS/Rail.
ADAMS/Rail automatically loads a command file named arail.cmd, if it finds it in the
working directory when you start ADAMS/Rail. You can use this file to customize the
interface, such as reading user-defined macros and menus.
If you want to be able to read in different customized environments when you start
ADAMS/Rail, independently from the working directory, use the following environment
variable:
ENVIRONMENT MDI_ARAIL_EXECMD <command file name with complete path>
For information on customizing ADAMS/Rail or any other template-based product, see

the guide, Customizing Template-Based Products.
Defining Your Own Environment Keywords

You can define your own environment keywords in the private and site configuration files
for use with user-written subroutines or macros. For example, you can define a keyword
called debug_mode in your private or site configuration file. Then, in your own macros,
you can query for the value of debug_mode, and execute some instructions depending on
its value. The example below shows a portion of the macro that would query for the value
of debug_mode:
IF condition =(getenv(“debug_mode”)==”yes”)
default command echo=on
END
.
.
.
To define your own environment variables, use the format below. Your template-based
product initializes the variables at startup.
ENVIRONMENT VARIABLE_NAME VARIABLE_VALUE
For the previous example, you would use the following:

ENVIRONMENT debug_mode yes
For more information on macros, see Customizing the Interface on page 13 in the guide,
Customizing Template-Based Products. For more information on subroutines, see Ways to
Extend Functionality on page 32 in the guide, Customizing Template-Based Products.
Managing Databases Through Configuration Files

You can use three keywords to manage your template-based product’s databases in the
configuration file:
■ DATABASE - Sets up databases.
■ DEFAULT_WRITE_DB - Sets the default writable database.
■ DATABASE_ORDER - Sets the search order of databases.
You can place DATABASE entries in the private, site, or shared configuration files. The
DEFAULT_WRITE_DB and DATABASE_ORDER, however, are reserved for the private
and site configuration files.
Note that you can also set up databases through menus, as explained in Managing
Databases on page 9. You may find it more convenient to use the menus.
For an overview to managing databases, see Managing Databases on page 9.
Setting Up Databases
You can define databases in your template-based product using the keyword DATABASE.
A DATABASE keyword entry has the following format:
DATABASE DB_NAME DB_PATH
In the format, DB_NAME is the name assigned to the database and DB_PATH is the location
of the database in your file system. You can add any database to the DATABASE definition
in any configuration file. If the database does not exist, your template-based product
creates it in the specified location and adds it to the database list.
Specifying Default Writable Database

You can specify the database that you want to use as the database to which all files are
written. You use the keyword DEFAULT_WRITE_DB to define the default writable
database. The DEFAULT_WRITE_DB keyword entry has the following format:
DEFAULT_WRITE_DB DB_NAME
The keyword entry defines the initial database that you want as the default location for
writing files. Usually, you define the default writable database in your private
configuration file, although you can set the writable database in any configuration file.
You can change it during the session as explained in Setting the Writable Database on
page 15. Note that you will need permission to write to the file system location to which
the DEFAULT_WRITE_DB points.
Setting Database Search Order

You can set up the order in which your template-based product searches databases using
the keyword DATABASE_ORDER. The DATABASE_ORDER keyword entry has the
following format:
DATABASE_ORDER DB_NAME_1, DB_NAME_2, DB_NAME_3
To set the order, enter the databases in the order in which you would like them searched.
For example, if you’d like your private database searched first, followed by the site and
then the shared, you enter the following:
DATABASE_ORDER private, site, shared
For more information on database order and setting it up through your template-based
product menus, see Setting Up the Search List and Order on page 17.
Managing Tables Through Configuration Files

As explained in Database Structure on page 11, a template-based product’s database is
comprised of a number of directories or tables in which you store files. In addition to the
standard set of table directories, you can create your own tables.
Generally, you only add table directories to the databases defined in your private
configuration file. As the site manager, you may decide to add tables for general use in the
site configuration file.
The next sections explain how to create tables and the standard table entries.
Creating Tables
At start up, your template-based product determines when to create new table directories
as follows:
1 Your template-based product verifies that all database directories defined in the
private configuration file contain table directories for the corresponding table
directories also defined in the private configuration file.
2 If a table directory does not exist inside the database, your template-based product
creates one.
3 If a site configuration file exists, your template-based product ensures that for any
table directory specified in the site configuration file, a corresponding table
directory exists for all database directories defined in both the site and private
configuration files.
4 Your template-based product ensures that for all table directories specified in the
shared configuration file, a corresponding table directory exists for all database
directories defined in the private, site (if it exists), and shared configuration files.
The TABLE keyword entry for creating tables has the format:
TABLE TABLE_CLASS TABLE_NAME TABLE_EXTENSION
where:
■ TABLE_CLASS - A string identifying the table.
■ TABLE_NAME - The name that you want used to access the table.
■ TABLE_EXTENSION - The three-character extension of files stored in the table.

Your template-based product only recognizes files in the table that have the
extension that you specify.
For example, the following creates a table that stores aerodynamic forces:
TABLE aeroforces /staff/my_name/my_db.cdb/aeroforces.tbl aer
Adding the table definition shown above in the configuration file causes your template-
based product to recognize and correctly access files stored in that particular database
table.
Standard TABLE Directory Entries

The TABLE directory entries in the shared configuration file are briefly explained in the
following tables:
■ ADAMS/Car - Table 2 on page 46
■ ADAMS/Engine - Table 3 on page 49
■ ADAMS/Rail - Table 4 on page 54
They are the standard set of tables that are distributed with your template-based product’s
database. You cannot reconfigure TABLE entries. Changing these values disables your
template-based product’s ability to assign properties to a class of entities.
Managing: Property Files Through Configuration Files

A PROPFILE entry in the configuration file assigns a default property file used when
creating the following entity types: bumpstop, bushing, damper, reboundstop, spring, and
tire.
A PROPFILE keyword entry in a configuration file has the following format:
PROPFILE PROPFILE_CLASS PROPFILE_NAME
where:
■ PROPFILE_CLASS is a string that identifies the property file.
■ PROPFILE_NAME is the name of the property file.
For example:
PROPFILE bushing mdids://shared/bushings.tbl/mdi_0001.bus
You can define the property files in the private, site, or shared configuration files.
Managing Test Rigs Through Configuration Files

A TESTRIG entry in the configuration file assigns a default test rig to a particular class of
assemblies.
A TESTRIG keyword entry in a configuration file has the following format:
TESTRIG TESTRIG_CLASS TESTRIG_NAME
where:
■ ASSEMBLY_CLASS is a string that identifies the type of assemblies which
correspond to the test rig.
■ TESTRIG_NAME is the name of the test rig model.
For example:
TESTRIG four_post .__MY_FOURPOST
You can define the default test rigs in the private, site, or shared configuration files.
A Standard Table Directory Entries
Overview
This appendix briefly explains the TABLE directory entries in
the shared configuration file:
■ ADAMS/Car Standard TABLE Entries, 46
■ ADAMS/Engine Standard TABLE Entries, 49
■ ADAMS/Rail Standard TABLE Entries, 54
Standard Table Directory Entries
Table 2. ADAMS/Car Standard TABLE Entries
The entry: Defines tables for:
TABLE assembly assemblies.tbl asy Assembly files that list the subsystems
that make up ADAMS/Car assemblies.
TABLE template templates.tbl tpl Template files that define the topology
and major role (for example, suspension
or steering) of ADAMS/Car models.
TABLE subsystem subsystems.tbl sub Subsystem files that contain information
unique to the specific instance of the
template the subsystem file references.
TABLE aero_force aero_forces.tbl aer Aero_force files that contain wind-force
mappings.
TABLE bushing bushings.tbl bus Bushing files that define a six degree-
of-freedom force relationships between
user-specified locations on two parts.
TABLE linear bushing bushings.tbl lbf Bushing files that define a six degree-
of-freedom force relationship between
user-specified locations on two parts,
using constant coefficients for each of
the six degrees of freedom.
TABLE bumpstop bumpstop.tbl bum Bumpstop files that define a force-
displacement relationship between user-
specified locations on two parts.
TABLE damper dampers.tbl dam Damper files that define a force-velocity
relationship between user-specified
locations on two parts.
Table 2. ADAMS/Car Standard TABLE Entries (continued)
TABLE linear damper dampers.tbl ldf Damper files that define the linear
damping force relationship between
user-specified locations on two parts,
using a constant damping coefficient.
TABLE flex_body flexbodys.tbl mnf Files that define flexible body
representations usually through modal
neutral files.
TABLE powertrain powertrains.tbl pwr Powertrain files that define the engine
speed-torque relationship at different
throttle positions.
TABLE differential differentials.tbl dif Differential files that define the slip
speed-torque characteristics of a
differential.
TABLE reboundstop reboundstops.tbl reb Rebound stop files that define a force-
TABLE shell_graphic shell_graphics.tbl shl Shell graphic files.
TABLE spring springs.tbl spr Spring files that define a force-
TABLE linear spring springs.tbl lsf Spring files that define the linear elastic
force relationship between user-
specified locations on two parts, using a
constant stiffness coefficient.
TABLE steering_assist steering_assists.tbl Steering_assist files that contain torsion
ste bar data relating torsion bar deflection
to both torque and pressure.
TABLE tire tires.tbl tir Tire files that define data needed to
characterize tire behavior (a tire model).
TABLE road roads.tbl rdf Road files that define roads that the
contact algorithms in the ADAMS/Tire
module use.
TABLE driver_controls driver_controls.tbl Driver control files that contain
dcf maneuver descriptions for the Driving
Machine.
TABLE driver_data driver_data.tbl dcd Driver data files that contain data for the
Driving Machine.
TABLE driver_loadcase Driver loadcase files that contain
driver_loadcases.tbl dri driving signals used in a data-driven,
full-vehicle analysis. The driver
loadcase specifies inputs to the vehicle.
TABLE loadcase loadcases.tbl lcf Loadcase files that contain data used in
suspension analyses.
TABLE suspension_curve Suspension curves used in the
suspension_curves.tbl scf Conceptual Suspension Modeling
module.
TABLE wheelenv wheel_envelopes.tbl wen Wheel envelope files that contain
location vector information that
represents the wheel center location and
orientation in space. They are used for
wheel envelope analyses.
TABLE plot_config plot_configs.tbl plt Plot configuration files that define a

suite of plots to be automatically
generated after completion of an
analysis.
TABLE driver_road driver_roads.tbl drd ADAMS/Driver road definitions.
TABLE driver_knowledge ADAMS/Driver knowledge file.
driver_knowledge.tbl kno
TABLE driver_input driver_inputs.tbl din ADAMS/Driver input files used in an

ADAMS/Driver full-vehicle analysis.
Table 3. ADAMS/Engine Standard TABLE Entries
TABLE assembly assemblies.tbl asy Assembly files that list the subsystems
that make up ADAMS/Engine
assemblies.
TABLE template templates.tbl tpl Template files that define the topology
and major role of ADAMS/Engine
models.
TABLE damper dampers.tbl dpr Damper files that define a force-velocity
Table 3. ADAMS/Engine Standard TABLE Entries (continued)
TABLE flex_body flex_bodys.tbl mnf Files that define flexible body

neutral files.
TABLE shell_graphic shell_graphics.tbl Shell graphic files.
shl

TABLE gas_force gas_force.tbl gaf Files that define the crank angle-
cylinder pressure relationship at
different engine speeds.
TABLE contact_stiffness Files that define the displacement-
contact_stiffness. tbl con stiffness relationship for curve to flat
contacts.
TABLE cam_profile cam_profile.tbl pro Files that define cam profiles.
TABLE dyno dynos.tbl dyn Files that contain Fourier series
coefficients that define the motion or
torque function of dynos.
TABLE cam cams.tbl cam Files that reference a cam profile
property file, and contain mass
properties and geometry data of cams.
TABLE nli_chain_properties Files that contain nonlinear stiffness
chain_properties.tbl chn parameters, mass properties, and
geometry data of timing chains.
TABLE chain_properties Files that contain linear stiffness
chain_properties.tbl chp parameters, mass properties, and
geometry data of timing chains.
TABLE gear_element gear_elements.tbl Files that contain mass properties and

gea geometry data of straight or helical
gears.
TABLE fixed_guide guides.tbl guf Files that contain mass properties and
geometry data of fixed guides.
TABLE pivot_guide guides.tbl gup Files that contain mass properties and
geometry data of pivoting guides.
TABLE trans_guide guides.tbl gut Files that contain mass properties and
geometry data of translational guides.
TABLE plate plates.tbl pla Files that contain mass properties and
geometry data of plates.
TABLE deviation_pulley pulleys.tbl pyd Files that contain mass properties and
geometry data of deviation pulleys.
TABLE trapezoidal_pulley pulleys.tbl pyt Files that contain mass properties and
geometry data of trapezoidal pulleys.
TABLE flex_rod rods.tbl puf Files that contain stiffness parameters,
mass properties, and geometry data of
flexible pushrod.
TABLE rig_rod rods.tbl pur Files that contain mass properties and
geometry data of rigid pushrod.
TABLE rocker_radii rockers.tbl rad Files that contain mass properties and
geometry data of rockers with two
contact radii.
TABLE rocker_rol_rad rockers.tbl ror Files that contain mass properties and
geometry data of rockers with one
contact radius (rocker) using a roller.
TABLE rocker_soc_radii rockers.tbl sra Files that contain mass properties and
contact radius and one socket.
TABLE rocker_soc_rol_rad rockers.tbl sro Files that contain mass properties and
contact radius and one socket (rocker)
using a roller.
TABLE roller rollers.tbl rol Files that contain mass properties and
geometry data of rollers.
TABLE sprocket sprockets.tbl spt Files that contain mass properties and
geometry data of sprockets.
TABLE hy1_tappet tappets.tbl th1 Files that contain hydraulic force
properties, mass properties, and
geometry data of hydraulic lash
adjusters with check valve in piston.
TABLE hy2_tappet tappets.tbl th2 Files that contain hydraulic force
properties, mass properties, and
geometry data of hydraulic lash
adjusters with check valve in housing.
TABLE nli_spd_tappet tappets.tbl tnl Files that reference a spring and a
damper property file, and contain mass
properties and geometry data of spring-
damper tappets.
TABLE rig_tappet tappets.tbl tri Files that contain mass properties and
geometry data of rigid tappets.
TABLE spd_tappet tappets.tbl tsp Files that contain stiffness parameters,
spring-damper tappets.
TABLE trapezoidal_tbelt_properties Files that contain material properties,

trapezoidal_tbelt_properties.tbl tbe mass properties, and geometry data of
timing belts.
TABLE tensioner tensioners.tbl ten Files that contain rotational stiffness
parameters, mass properties, and
geometry data of tensioners.
TABLE flex_valve valves.tbl vaf Files that contain stiffness parameters,
flexible valves.
TABLE rig_valve valves.tbl var Files that contain mass properties and
geometry data of rigid valves.
TABLE mms_valve_spring Files that contain material properties
valve_springs. tbl vmm and geometry data of multi-mass valve
springs.
TABLE nli_valve_spring valve_springs.tbl Files that reference a spring property
vnl file, and contain mass properties and
geometry data of spring-damper valve
springs.
TABLE spd_valve_spring valve_springs.tbl Files that contain stiffness parameters,
vsp mass properties, and geometry data of
spring-damper valve springs.
TABLE plot_config plot_configs.tbl plt Plot configuration files that define a
suite of plots to be automatically
generated after completion of an
analysis.
Table 4. ADAMS/Rail Standard TABLE Entries
TABLE airspring airsprings.tbl air Airspring files that define the parameters to
be used for the description of a Nishimura
or Krettek airspring element.
TABLE assembly assemblies.tbl asy Assembly files that list the subsystems that
make up ADAMS/Rail assemblies.
TABLE bumpstop bumpstop.tbl bum Bumpstop files that define a force-
TABLE bushing bushings.tbl bus Bushing files that define a six degree-of-
freedom force relationships between user-
TABLE contact_configuration contact_ Contact configuration files that contain the
configurations.tbl ccf contact models and properties to be used
for a certain analysis.
TABLE damper dampers.tbl dam Damper files that define a force-velocity
TABLE flex_body flexbodys.tbl mnf Files that define flexible body
neutral files.
TABLE flexref_config flexref_configs.tbl Files that define the linear track flexibility
ftp properties (mass and inertias of the track
beam and ballast parts, and stiffnesses and
damping of their supports).
TABLE friction_damper Property files that define the friction
friction_dampers.tbl fdp damper characteristics.
Table 4. ADAMS/Rail Standard TABLE Entries (continued)
TABLE plot_config plot_configs.tbl plt Plot configuration files that define a suite
of plots to be automatically generated after
completion of an analysis.
TABLE reboundstop reboundstops.tbl Rebound stop files that define a force-
reb displacement relationship between user-
TABLE shear_spring shear_springs.tbl Property files that define the shear spring
ssp characteristics.
TABLE shell_graphic shell_graphics.tbl Shell graphic files.
shl

TABLE suspension_element Suspension element files that define the
suspension_elements.tbl sel stiffness parameters to be used for the
description of a suspension element.
TABLE template templates.tbl tpl Template files that define the topology and
major role (for example, suspension or
steering) of ADAMS/Rail models.
TABLE track_irregularity Teim orbit-formatted track irregularities
track_irregularities.tbl idf data. You can specify a reference to this
file from the .trk file written in version 5.0.
TABLE track tracks.tbl trk Track files that contain the track properties.
They are used for track and rail profile
description.
Table 4. ADAMS/Rail Standard TABLE Entries (continued)
TABLE velocity_profile velocity_profiles.tbl User-defined velocity profiles as function

vpf of time or track distance for ADAMS/Rail
dynamic analyses.
TABLE wheel wheels.tbl wpf Wheel files that contain the wheel profile
properties. They are used for wheels-
wheelsets generation.
Index
Index
Symbols A-B
.acar.cfg, about 29
C-D
A-B
Access needed for management tasks 6 E-F
Accessing ADAMS/View, about 35
G-H
ADAMS/Car TABLE entries, defined 46
ADAMS/Engine TABLE entries, defined 49 I-J
ADAMS/Rail TABLE entries, defined 54
K-L
ADAMS/View, accessing 35
Add to Search commands, using 18 M-N
Adding, databases to search list 18 O-P
Analysis, setting output to result files 37
Q-R
Assemblies, publishing 25
Assumptions in this guide 3 S-T
Bundling databases 16
U-V
C-D
Change Search Order command, using 20 W-Z
Changes, saving database configuration 21
Changing
search order 20
search order using configuration files 40
Index
Commands A-B
Add to Search 18
Change Search Order 20 C-D
Create Database 15
Database Info 21
E-F
Default Writable 15
Publish Assembly 25
G-H
Publish Subsystem 24
Remove from Search 19
I-J
Save Configuration 21
Table Info 21 K-L
Configuration files
about 28 M-N
example of 32
format of 31 O-P
managing databases using 39
managing tables using 41 Q-R
managing test rigs using 43
setting up databases in 39 S-T
Copying subsystem 24, 25
U-V
Create Database command, using 15
Creating W-Z
custom keywords 38
databases 14
tables 41
Custom keywords, creating 38
Database Info command, using 21
DATABASE keyword 39
DATABASE_ORDER keyword 40
Index
Databases A-B
adding to search list 18
changing order searched 20 C-D
changing order searched using configuration files 40
creating 14
E-F
creating tar files of 16
removing from search list 19
G-H
saving management changes 21
search list for 13
I-J
setting default writable 15
setting default writable using configuration file 40 K-L
setting up in configuration files 39
structure of 11
M-N
types of 10
viewing information about 21
O-P
Default
for Welcome dialog box 35 Q-R
setting writable database 15
setting writable database using configuration file 40 S-T
Default Writable command, using 15
U-V
Default writable database
setting 15
W-Z
setting using configuration file 40
DEFAULT_WRITE_DB keyword 40
Display, setting Welcome dialog box 36
Index
E-F A-B
ENVIRONMENT keywords
defining your own 38 C-D
MDI_ACAR_INITMODE 35
MDI_ACAR_LOGO_BMP 36 E-F
MDI_ACAR_MODEPROMPT 36
MDI_ACAR_PLUS_AVIEW 35 G-H
MDI_ACAR_SIDE_PREF 36
MDI_ACAR_USERMODE 34 I-J
MDI_ACAR_VEHICLE_LEFT 37
MDI_ACAR_VEHICLE_REAR 37 K-L
MDI_ACAR_WRITE_RES 37
MDI_ARAIL_NORES 37 M-N
Example configuration file 32
O-P
Exit dialog box, replacing image on 36
Expert users Q-R
management tasks 6
setting up 34 S-T
tools for managing 7
U-V
Files
about configuration 28
creating tar 16 W-Z
format of configuration 31
property, managing 43
setting output to result 37
Format of configuration files 31
Frame, setting orientation of global reference 37
Index
I-J A-B
Image, replacing in dialog box 36
Information C-D
viewing database 21
viewing table 21 E-F
K-L G-H
Keywords
defining your own 38
I-J
in configuration files 33
K-L
M-N
M-N
Management tasks
about 6
O-P
accessing tools for 7
Managing Q-R
databases through configuration files 39
property files 43 S-T
tables 41
test rigs 43 U-V
MDI_ACAR_INITMODE keyword 35
W-Z
MDI_ACAR_LOGO_BMP keyword 36
MDI_ACAR_MODEPROMPT keyword 36
MDI_ACAR_PLUS_AVIEW keyword 35
MDI_ACAR_SIDE_PREF keyword 36
MDI_ACAR_USERMODE keyword 34
MDI_ACAR_VEHICLE_LEFT keyword 37
MDI_ACAR_VEHICLE_REAR keyword 37
MDI_ACAR_WRITE_RES keyword 37
MDI_ARAIL_NORES keyword 37
Names, setting for databases 14
Index
O-P A-B
Order
about search 17 C-D
changing search 20
changing search using configuration files 40 E-F
Orientation, setting global reference frame 37
G-H
Output, setting to results files 37
Paths, assigning to databases 14 I-J
Preferences, setting side 36 K-L
Private configuration files
about 29 M-N
environment variables for 29
saving 21 O-P
Private database, about 10
Q-R
privateCfg, about 29
Publish Assembly command, using 25 S-T
Publish Subsystem command, using 24
U-V
Publishing
assemblies 25 W-Z
subsystems 24
Q-R
Reference frame, setting orientation of global 37
Registry Editor, about 29
Remove from Search command, using 19
Removing, databases from search list 19
Replacing image
on Exit dialog box 36
on Welcome dialog box 36
Result files, setting output to 37
Index
S-T A-B
Save Configuration commands, using 21
Saving, database configuration 21 C-D
Search list E-F
about 13
adding databases to 18 G-H
removing databases from 19
Search order I-J
about 17
defined 13 K-L
potential problems with 18
using configuration files to change 40 M-N
using menus to change 20
O-P
Setting
databases through configuration file 39 Q-R
default writable database 15
default writable database using configuration file 40
orientation of global reference frame 37
S-T
output to result files 37
side preferences 36
U-V
Shared configuration file, about 30 W-Z

Shared database, about 10
Side preferences, setting 36
Site configuration file, about 30
Site manager, defining for management tasks 6
Standard interface, explained 34
Standard table entries, about 42
Standard users
management tasks 6
setting up 34
tools for managing 7
Index
Structure of databases 11 A-B

Subsystems, publishing 24
TABLE entries
C-D
for ADAMS/Car, defined 46
for ADAMS/Engine, defined 49 E-F
for ADAMS/Rail, defined 54
G-H
Table Info command, using 21
TABLE keyword 42 I-J
Tables K-L
about 11
creating 41 M-N
standard 42
viewing information 21
O-P
Tar files, creating 16
Q-R
Tasks, management 6
Template Builder, explained 34 S-T
Template-based products
management tasks 6 U-V
Template-based products, list of 3
W-Z
Templates, publishing 24, 25
Test rigs, managing using configuration files 43
Tools for managing 7
Tools menu 7
Types of databases 10
Index
U-V A-B
User access
and type of management tasks 6 C-D
setting 34
Users, setting up 34 E-F
Variables, creating your own 38 G-H
Viewing
database information 21 I-J
table information 21
K-L
W-Z
Welcome dialog box M-N
replacing image on 36
setting default in 35 O-P
setting display of 36
Q-R
Writable database, viewing tables in 21
Writing S-T
setting database for 15
setting database for using configuration file 40 U-V
W-Z

Configuring Templates-ADAMS

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configuring Templates-ADAMS

Uploaded by

Copyright:

Available Formats

Configuring Template-

About This Guide 3

Introducing Management Tasks and Tools 5

Working With Configuration Files 27

Standard Table Directory Entries 45

ADAMS ® is a registered United States trademark of Mechanical Dynamics, Incorporated.

Part number: 120TEMCN-01

About This Guide

Welcome to Configuring ADAMS Template-Based Products

What This Guide Assumes

■ Accessing the Management Tools, 7

About the Management Tasks

This type of user: Can:

Accessing the Management Tools

■ Setting Up the Search List and Order, 17

Overview of Database Management

■ About the Database Search List, 13

Figure 1. Database Structure

About the Database Search List

■ Setting the Writable Database, 15

■ Managing Tables in a Database, 16

■ Creating Tar Files of Databases, 16

Creating Databases During a Session

Setting the Writable Database

To set the writable database:

Managing Tables in a Database

Creating Tar Files of Databases

To create a tar file of a database in UNIX:

Setting Up the Search List and Order

■ Adding Databases to the Search List, 18

■ Removing Databases from the Search List, 19

■ Changing the Search Order, 20

About Search Order

Adding Databases to the Search List

To add a database to the search list:

Removing Databases from the Search List

To remove a database from the search order:

The Remove Database from Search dialog box appears.

2 Set Database Name to the database you want to remove.

Changing the Search Order

To change the search order:

The Change Database Search Order dialog box appears.

Viewing Database and Table Information

To view database information:

To view the tables in the writable database:

Saving Database Management Changes

To save database management changes:

The Publish an Open Subsystem dialog box appears.

■ Format of Configuration Files, 31

■ Using Configuration Files to Set Up Your Template-

About Configuration Files

■ About the Site Configuration File, 30

■ About the Shared Configuration File, 30

About Private Configuration Files

About the Site Configuration File

About the Shared Configuration File

Format of Configuration Files

Figure 3. Configuration File Blocks

Using Configuration Files to Set Up Your Template-Based

■ Managing Databases Through Configuration Files, 39

■ Managing Tables Through Configuration Files, 41

■ Managing: Property Files Through Configuration Files, 43

Setting Up the Environment Through Configuration Files

■ Setting Defaults in the Welcome Dialog Box, 35