1 / 17

SECTION 1 Introducing Adams/Car

SECTION 1 Introducing Adams/Car. Introducing Adams/Car. This module discusses the advantages of using Adams/Car, as well as the organization of the basic files. Introducing Adams/Car (Cont.). What’s in this section: Motivation for Using Adams/Car User Modes

kiri
Download Presentation

SECTION 1 Introducing Adams/Car

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SECTION 1 Introducing Adams/Car

  2. Introducing Adams/Car • This module discusses the advantages of using Adams/Car, as well as the organization of the basic files.

  3. Introducing Adams/Car (Cont.) • What’s in this section: • Motivation for Using Adams/Car • User Modes • Database Structure—A Directory Hierarchy • Saving Files: Working Directory versus Database • Configuration Files

  4. Engine Advanced Engineering Test lab Suppliers Chassis engineering Body engineering Driveline Motivation for Using Adams/Car • Bridges departments by sharing models and data • Facilitates quick subsystem changes • Templates

  5. Advanced Engineering Test lab Engine Suppliers Chassis engineering Body engineering Driveline Motivation for Using Adams/Car (Cont.) • Bridges departments by sharing models and data • Different departments can work with the same database, which minimizes data loss.

  6. MacPherson SLA Motivation for Using Adams/Car (Cont.) • Facilitates quick subsystem changes • You can easily replace one subsystem without changing any other part of the vehicle.

  7. Motivation for Using Adams/Car (Cont.) • Templates • Allow you to tailor one system for multiple vehicles.

  8. User Modes • Within the Adams/Car configuration file (acar.cfg and .acar.cfg), the particular application of Adams/Car is specified as either standard user mode or expert user mode. • Expert user (Template Builder and Standard Interface) • Allows creation of building-block of Adams/Car, templates, with access to Template Builder • For experienced Adams users • Access to all Adams modeling entities • Standard user (Standard Interface only) • Specifically for designers and testing engineers • Use libraries from the Adams/Car database to easily create vehicle (sub)assemblies • Simulation environment tailored to automotive standards

  9. Database Structure—A Directory Hierarchy • A database is a collection of tables (directories) stored on the hard drive. The top directory, which has the extension .cdb, stores a number of tables (directories). Each table is a placeholder for model information. • Three types of databases: • Shared - Common to all users, provided by MSC.Software with example files • Private - User workspace (created by Adams/Car in your $HOME directory) • User - User/site specific

  10. Database Structure—A Directory Hierarchy (Cont.) • The databases are defined in private .acar.cfg or common acar.cfg • No limitations on number of databases • Each project should have a separate database • You can only save to one database at a time • For more information about managing Adams/Car databases, see the Adams/Car online help.

  11. Saving Files: Working Directory Versus Database • Adams/Car divides your suspension or full-vehicle model into subsystems and components so you can manage the data more easily. It saves these components into an Adams/Car database. The ultimate goal is to build .adm files and produce results, which are stored in the working directory. • You can set up the database that stores the components that build up the model, and so on, using the database management tools (Tools  Database Management). • Adams/Car saves your .adm, .acf, and results to your working directory (File  Select Directory).

  12. Configuration Files • Configuration files contain information that Adams/Car reads during startup to correctly initialize the session: • User mode (expert versus standard) • Personal databases and tables • Default property files • Default writable database • Database search order • Orientation of global reference frame • Other preferences

  13. Configuration Files (Cont.) For more information about configuration files, see the Adams/Car online help.

  14. Configuration Files (Cont.) • Shared versus private configuration files • Adams/Car uses two configuration files: • Shared configuration file (acar.cfg) - Is a common file that sets up default parameters (read first). Can be a specially created site-specific file. This file is located in the <adams_install>/acar directory (where <adams_install> is the path to your Adams installation directory). • Private configuration file (.acar.cfg - note the period at the front) - Is a private file that also sets up parameters, but takes precedence over the common acar.cfg file (read second). The private configuration file is located in the HOME directory (environment variable). • Having both configuration files allows users on a network to work from default parameters and to customize their own workstations with the private .acar.cfg file.

  15. Configuration Files (Cont.) • Saving configuration files • You can save your configuration files as follows: • Shared configuration file (acar.cfg) - Manually open the file in a text editor and save it. This file is located in the <adams_install>/acar directory (where <adams_install> is the path to your Adams installation directory). You typically do not edit this file unless you are making a site-specific configuration file. • Private configuration file (.acar.cfg) - Use Settings  Save A/Car Configuration.

More Related