Getting Started Using Adams Car MDR3
Getting Started Using Adams Car MDR3
Getting Started Using Adams Car MDR3
Introducing Adams/Car
Overview
This chapter introduces you to Adams/Car. It contains the following sections:
• Starting Adams/Car Standard Interface
• Starting Adams/Car Template Builder
• Switching Between Interface Modes
• Familiarizing Yourself with Adams/Car
• Plotting Results
3
Introducing Adams/Car
Menu bar
View triad
Status bar
The Welcome dialog box appears on top of the Adams/Car main window.
5
Introducing Adams/Car
Menu bar
The Welcome dialog box appears on top of the Adams/Car main window.
Plotting Results
When you’re ready to review the results of your analyses, you can display the post-processing tool and
view the results of the simulations you performed.
To plot results:
1. While in Adams/Car Standard Interface, from the Review menu, select Postprocessing Window
or press F8.
Adams/Car launches Adams/PostProcessor, a post-processing tool that lets you view the results
of simulations you performed. For more information about Adams/PostProcessor, see the
Adams/PostProcessor online help.
2. To return to Adams/Car, select the Return to Modeling Environment tool or press F8.
12 Getting Started Using Adams/Car
13
Introducing the Driving Machine
Overview
This tutorial introduces you to the Driving Machine and the associated Event Builder. It contains the
following sections:
• About the Driving Machine
• About the Event Builder
15
Introducing the Driving Machine
Overview
In this chapter, you will learn the basics of creating multiple mini-maneuvers, establishing the
appropriate application areas for those mini-maneuvers, and setting end conditions for each mini-
maneuver.
The chapter contains the following sections:
• Creating an Event
• Creating the Three Mini-Maneuvers
• Defining the Mini-Maneuver Parameters
• Running the New Analysis
19
Using the Event Builder
Creating an Event
Before you can create an event, you must create a new file, as explained next. The instructions will point
out differences between procedures in Adams/Car and Adams/Chassis, as needed.
The Event File text box shows the file name you specified when you created or opened the file, and
the path, for new files, is the working directory. You can’t change the file name or path in the Event
Builder. You can use the Speed and Gear text boxes to enter an initial speed and gear, respectively, for
the vehicle prior to starting the first mini-maneuver.
The Static Set-up tab lets you complete the definition of the vehicle state prior to beginning of the
first mini-maneuver. The Gear Shifting Parameters tab lets you define global parameters
related to gear shifting. The Event Builder outputs this information so that the Driving Machine uses
these parameters for any shifting required by any mini-maneuver.
For this exercise, the default Gear Shifting Parameters should be adequate, so you won’t change them.
Because the first mini-maneuver that you specify is going to be a straight line, you will use the straight
static setup. For a description of the static setup methods available in the Driving Machine, see the
Analyze tab in the Adams/Car online help.
1. In the Static Set-up tab, change set Task to straight. Note that the rest of the parameters
are not used because they will be overwritten by the initial values computed during the quasi-
static setup.
You must set the initial velocity of the vehicle. The value of the initial velocity depends on the
units in which you are using the Event Builder.
2. To check the units or make a change, from the Settings menu, select Units.
21
Using the Event Builder
By default, the length unit is set to meters and the time unit is set to seconds. Therefore, the
velocity must be set in meters/second.
3. To verify that velocity units are in meters/second, click in the Speed text box at the top of the
Event Builder, and then read what is displayed in the Current Field Unit text box at the bottom
of the Event Builder.
4. To set the target vehicle velocity, in the Speed text box, enter 27.7 (as previously explained, units
are meters/second), which corresponds to approximately 100 km/h.
5. To set the initial gear, in the Gear text box, enter 5.
22 Getting Started Using Adams/Car
The Velocity setting enables the Driving Machine to maintain the steady-state velocity that
you established earlier. The Driving Machine will control the throttle to maintain this velocity
much like a cruise control system.
• Braking tab
Control Method: machine
The Throttle and Brake settings control the longitudinal velocity of the vehicle.
• Gear tab
Control Method: open
Control Type: constant
Control Value: 5
Maintain the same gear specified for the static setup.
• Clutch tab
Control Method: open
Control Type: constant
Control Value: 0.0
For the first mini-maneuver, you’re using the Driving Machine for the steering and the
throttle, so you can maintain the vehicle speed during straight-line driving.
The purpose of the first mini-maneuver is to reach a dynamic steady-state end condition.
Although not absolutely necessary for this type of event, it helps demonstrate some important
aspects of the Driving Machine. To satisfy a steady-state condition, the vehicle must be
traveling a straight line (very low lateral acceleration) at a stable velocity (very low
longitudinal velocity). You can use end conditions to group these two conditions together to
satisfy the steady-state requirements.
For the third mini-maneuver, you use the Driving Machine for all vehicle activity; you want
the Driving Machine to maintain the vehicle radius while at the same time braking the vehicle
at 3 m/s2. You use a single end condition for the third mini-maneuver, which is velocity. You
trigger the end of the simulation if the velocity is below 10 kph which is approximately
2.77 m/s.
After you create the suspension and steering assembly, you perform two types of analyses to understand
its kinematics:
33
Suspension Analysis Tutorial
• A baseline parallel wheel travel analysis that moves the assembly vertically through the
suspension’s rebound-bump travel.
• A baseline pull analysis to measure the brake pull at the steering wheel.
Once you understand the kinematics of the assembly, you modify the suspension subsystem’s geometry
to decrease the scrub radius, which should reduce the pull on the steering wheel. You confirm the
reduction by analyzing the modified assembly again, using the same type of analysis and comparing the
new results to the results yielded by the previous analysis.
34 Getting Started Using Adams/Car
Tip: For information on any dialog box, press F1 when the dialog box is active.
9. In the Comment Text text box, enter Baseline UAN Front Suspension.
10. Select OK.
11. Select OK again.
Adams/Car creates the suspension subsystem using the default data contained in the template and
displays it as shown next:
The Message Window appears, informing you of the steps Adams/Car takes when performing the
analysis. Adams/Car analyzes the suspension and steering assembly and applies to it the
displacements and loads defined in the submission dialog box.
7. When the analysis is complete, select Close.
Adams/Car animates the motion of the suspension analysis. Notice that the suspension moves
from rebound (down), to bump (up), and that the steering wheel does not rotate.
3. When the animation is complete, close the dialog box.
Notice that the scrub radius varies little with wheel travel and is approximately 34 mm. A positive
scrub radius means the steering axis lies inboard of the center of the tire contact patch.
From the analysis you’ve completed, you have enough information to calculate the approximate
torques produced about the steering axes using the difference in left to right braking forces and
the 34 mm scrub radius.
In addition, using the results of that calculation and the steering geometry, you can calculate the
resulting unbalanced force at the steering rack and the pull (torque) needed at the steering wheel
to keep the wheels straight.
In the next sections, you use Adams/Car to perform these calculations.
Deleting Plots
To prepare for the baseline pull analysis, delete the plots you created in the previous sections.
To delete plots:
1. In the treeview, hold down the left mouse button, and then drag the cursor across the names of the
plots you want to delete.
2. From the Edit menu, select Delete.
3. From the File menu, select Close Plot Window or press F8.
Adams/Car returns to the main window.
41
Suspension Analysis Tutorial
Note: If Select Loadcase Type is not set to Static Load, your dialog box will look slightly
different. Make sure you select Static Load first, and then proceed to fill in the dialog box.
2. Fill in the dialog box as shown next, and then select OK.
42 Getting Started Using Adams/Car
Adams/Car creates the loadcase file, named brake_pull.lcf, and stores it in your private
database. It stores the loadcase file as text (ASCII) and you can print it or edit it manually.
To create the loadcase file, Adams/Car takes the parameters that you entered and generates a table
of input values. For the parameters that you entered, Adams/Car generates a table that varies
steering wheel angle from -180 to 180 in 15 steps, while holding the braking forces constant.
Table 1 shows the loadcase file values
43
Suspension Analysis Tutorial
The plot shows the torque that the test rig applies to the steering wheel to hold the wheel in
position. The torque is negative, meaning that the test rig applies a clockwise torque to counteract
the unequal braking force that pulls the wheel counterclockwise, as if making a left turn.
7. Right-click the treeview area, point to Type Filter, point to Plotting, and then select Axes.
8. Double-click plot_2 to expand it so the names of the axes are visible.
9. From the treeview, select haxis.
10. In the property editor, select Labels.
11. In the Label text box, enter Steering Wheel Angle [degrees].
12. From the treeview, select vaxis.
13. In the Label text box, enter Scrub Radius [mm].
Notice that the scrub radius appears to vary a lot with respect to the steering angle because of the
vertical plot scale, when in fact it only varies 0.21 mm over the total range of steering wheel angle.
To show that this variation is small, you must modify the vertical axis so it covers a larger range
of values.
Notice that the variation in scrub radius with respect to the steering wheel angle now appears
smaller.
3. Scroll the table window down until you see the hardpoint hpl_uca_outer.
4. Click the cell common to hpl_uca_outer and loc_y.
5. Change the existing value to -700. This moves the hardpoint 25 mm outboard.
6. Select Apply.
Adams/Car changes the hardpoint locations of the two hardpoints and their symmetrical right
pairs.
7. Close the dialog box.
Figure 8 Comparison Plot for Steering Wheel Torque vs Steering Wheel Angle
54 Getting Started Using Adams/Car
9. Cycle through the plots until you see a plot of the Scrub Radius vs Steering Wheel Angle, shown
below. This plot also contains values for both the baseline and the modified suspension and
steering assembly. Notice that the scrub radius decreased from 34 mm to 8 mm because of the
suspension modifications.
Figure 9 Comparison Plot for Scrub Radius versus Steering Wheel Angle
55
Suspension Analysis Tutorial
56 Getting Started Using Adams/Car
Finishing Up
Before you continue with the full-vehicle tutorial in the next chapter, you should clean up your directory
by deleting the plots and simulations, and closing the subsystems that you created and modified.
• Deleting Simulations
• Closing Assemblies
Deleting Simulations
You first delete the simulations for the baseline and modified analyses and then you return to the
Adams/Car main window.
To delete simulations:
1. Right-click the treeview, point to Type Filter, point to Modeling, and then select Analyses.
2. To show the current simulations, double-click my_assembly.
The treeview updates and displays the current simulations.
3. Select the simulations you want to delete.
4. From the Edit menu, select Delete.
Adams/Car deletes the simulations.
5. From the File menu, select Close Plot Window.
Adams/Car returns to the main window.
Closing Assemblies
You can now close the suspension and steering assembly.
Overview
In this tutorial, you run analyses on suspension and full-vehicle assemblies to see the effects of flexible
bodies.
Before you work through this tutorial, make sure you have:
• Adams/Flex.
• Completed the tutorial we’ve provided with Adams/Flex in the guide, Getting Started Using
Adams/Flex.
• A moderate level of finite element modeling proficiency.
When you integrate a flexible body into a template, you have to supply the following:
• A modal neutral file. This means that the MNF should have been previously created and stored
in a shared or private database.
• Location and orientation information for the part that you will create. Adams/Car uses the
location and orientation information to rigidly rotate and translate the flexible body.
• Inertia coupling and the damping ratio.
You can now integrate flexible bodies into your subsystems or assemblies. The process of swapping rigid
bodies with flexible bodies is fast, easy, and convenient, it eliminates the need for multiple templates,
and is fairly automatic. With rigid-to-flexible swapping, modal flexibility becomes a property of the
body. When you integrate a flexible body into a subsystem, you must:
• Supply a modal neutral file. This means that the MNF should have been previously created and
stored in a shared or private database.
• Position the flexible body with respect to the rigid parts. For help, from the Adjust menu, point
to General Part, select Rigid to Flex, and then press F1.
60 Getting Started Using Adams/Car
• Monitor the connectivity. For help, from the Adjust menu, point to General Part, select Rigid to
Flex, and then press F1.
To successfully integrate a flexible body into an Adams/Car template or subsystem and run simulations,
consider these precautions:
• Use flexible bodies if a component flexibility affects the dynamic behavior of your model or if
you are interested in accurate deformations of the flexible body under various load conditions.
• Because flexible body deformations are a linear combination of deformation shapes, be careful
when modeling components undergoing high nonlinear deformations.
• Consider the computational load that a flexible body representation demands, especially if the
MNF description is very detailed, that is, if several modes have been included.
• Verify your flexible body and check the natural frequencies associated with the significant mode
shapes and the mass and inertia properties.
During simulations, Adams/Car displays in the Message Window the type of damping that you selected
for each flexible body in the model.
We suggest that in this tutorial you work with the default damping ratio.
61
Flexible Bodies Tutorial
Tip: For information on any dialog box, press F1 when the dialog box is active.
Note: A warning message informs you that orientation parameterization references the old rigid
body, so parameterization will be lost. You can ignore this message.
Adams/Car deactivates the rigid body and replaces it with the corresponding flexible body.
7. Select OK in the Modify General Part dialog box.
8. Repeat the steps in this procedure for the left part, gel_lower_control_arm, making sure that you
select the MNF file named LCA_left_shl.mnf.
2. Select Close.
66 Getting Started Using Adams/Car
Adams/Car performs the analysis and displays messages about the simulation. The static load
analysis simulates the front suspension during a braking maneuver. The change in brake forces
causes a longitudinal wheel displacement.
69
Flexible Bodies Tutorial
Note: Requests are hierarchically arranged under their respective models. You can find
wheel_travel_base under the testrig entry. Double-click the plus sign (+) in
front of testrig to expand the entry.
The plot shows the effect of the flexible body on the displacement of the wheel center due to a
longitudinal braking force.
5. Select OK.
Swapping MNFs
If the FEM expert produced the lower control arm modal neutral files maintaining the same node number
for the attachment points, you can easily swap the flexible body (modal neutral files) and maintain the
parameterization. You can replace the flexible body by selecting a different MNF provided in the shared
database. This is analogous to replacing a damper or spring property file.
8. To return to the full-vehicle assembly, from the View menu, select Assembly.
9. Select OK.
To increase the efficiency of the simulations, you should disable any modes that do not contribute to the
motion that your flexible part will undergo during the simulation. Be careful when disabling modes,
because a disabled mode corresponds to a constraint to the part. Changing the modal content of a flexible
body corresponds to a flexible body setup.
You can manually toggle modes on or off. This gives you greater flexibility and helps you avoid potential
problems. You can enable and disable modes in several ways:
• Individually, based on their mode number.
• As a group, based on their mode number or frequency.
• Through a table editor. The table editor also lets you define displacement and velocity initial
conditions associated with every mode.
• Based on their strain energy contribution, but you can only do this after a successful analysis.
For more information on this technique, see the Adams/Flex online help.
Figures 15 and 16 show some of the plots. The flexible lower control arms cause the differences
between the curves.
4. View the plots shown next and then return to Adams/Car.
Damper
Spring
Tie rod
Wheel
Carrier
Hub
Control arm
Attachment
bushing
79
Template Builder Tutorial
Creating a Template
You must create a template in which to build suspension parts. You should assign to your template a
major role as a suspension template, because a major role defines the function the template serves for the
vehicle.
To create a template:
1. Start Adams/Car Template Builder as explained in Starting Adams/Car Template Builder.
2. From the File menu, select New.
Tip: For information on any dialog box, press F1 when the dialog box is active.
• Geometry-based method lets you tell Adams/Car to automatically create mass properties using
the geometry and material type that you specify.
In the next sections, you create all the parts that make up the suspension template:
• Creating the Control Arm
• Creating the Wheel Carrier
• Creating the Strut
• Creating the Tie Rod
• Creating the Toe and Camber Variables
• Creating the Hub
Note: Depending on how you set up your environment variables, the longitudinal axis can be any
axis. In this tutorial, the longitudinal axis is the x-axis. For information on setting your
environment variables, see the Adams/Car online help.
8. When you’re done creating the hardpoints, close the dialog box.
9. To see all six hardpoints in the main window, fit your model to view (type a lowercase f).
Adams/Car creates a part coordinate system, also referred to as local part reference frame (LPRF,
which is also known as the Body Coordinate System (BCS)), at the specified location, but it
doesn’t create geometry.
Adams/Car displays the control arm part. If you want the control arm to be shaded, put the cursor
in the main window and type an uppercase S. This toggles the rendering mode between shaded
and wireframe.
Note: Based on the geometry, the option Calculate Mass Properties of General Part computes the
mass properties for the part, and adds that to the total mass of the part. (You can have more
than one geometry associated with a part.) Also, note that the mass of the part is not
parameterized to its geometry. Therefore, if you want to base the mass of the part on new
geometry, you must use the Calculate Mass functionality for the part.
3. To display the hardpoints in the main window, fit your model to view.
To create a hardpoint:
1. Create a hardpoint with the following specifications:
• Hardpoint Name: tierod_inner
• Location: 200, -350, 250
2. Select OK.
Note: When Adams/Car creates the toe and camber values, it also creates output communicators
of the same name. For details on communicators, see Assembling the Model for Analysis.
Creating Forces
In this section, you create a damper and a spring.
To create a hardpoint:
1. Create a hardpoint as follows:
• Hardpoint Name: strut_upper
• Location: 0, -600, 600
2. Select OK.
• C is a constant.
• FL is the free length of the spring, as defined in the property file.
• IL is the defined installed length.
• DM(i,j) is the change in the displacement between the i and j coordinate reference points as the
simulation progresses.
• DM’(i,j) is the initial displacement between the i and j coordinate reference points. If you enter a
smaller value for DM(i,j), Adams/Car calculates an increased preload for the spring. Conversely,
if you enter a larger value, Adams/Car calculates a decreased preload. In this tutorial, you enter
the value that Adams/Car automatically calculates for you.
• Force represents the spring force.
• k is the nonlinear spring stiffness derived from the property file.
2. Select OK.
a mount part is to be replaced by another part (for example, vehicle body, subframe, wheel, and so on) if
its associated input communicator(s) find matching output communicator(s), or to be replaced by ground
if no matching output communicator is found.
When you create a mount part, Adams/Car automatically creates an input communicator for it of class
mount. The input communicator requests the name of the part to which the mount part should connect.
If Adams/Car finds a matching communicator during assembly, it replaces the mount part with the part
that the output communicator indicates. The replacement part is from another subsystem. If Adams/Car
finds no matching output communicator, it replaces the mount part with the ground part.
To create a mount part, you specify a hardpoint and mount part name. If the hardpoint has a left or right
symmetrical twin, Adams/Car creates left and right mount parts and input communicators. Otherwise, it
creates a single mount part and a single input communicator.
After you create the mount parts, you create bushings for the control arm. You specify the parameters,
such as preload and offset, that define bushings. In this example, you use the default values that
Adams/Car provides. If you want, you can modify the bushing properties. You also set its inactive status
to kinematic, so that during a kinematic analysis Adams/Car deactivates this bushing.
Finally, you create the control arm revolute joint. This time, you set its active status to kinematic. This
tells Adams/Car that during a kinematic analysis it should use the revolute joint, but it should replace the
joint with a bushing during a compliant analysis.
Adams/Car creates the front bushing and leaves the dialog box open so you can create the rear
bushing.
• J Part: ._macpherson.mtl_tierod_to_steering
• Joint Type: hooke
• Active: always
• Coordinate Reference: ._macpherson.ground.hpl_tierod_inner
• I-Part Axis:._macpherson.ground.hpl_tierod_outer
• J-Part Axis: ._macpherson.ground.hpr_tierod_inner
2. Select Apply.
Every subsystem or test rig in Adams/Car has input communicators that need information from other
subsystems to function correctly in the model. Similarly, the corresponding subsystem or test rig, needs
to have a correctly named output communicator that will send it information. For example, an input
communicator needs information on the location of a hardpoint. A corresponding output communicator
provides the location information.
During the assembly process, Adams/Car scans the model for subsystems with minor roles. It then looks
through those subsystems for any input communicators that require information. It then tries to find an
output communicator, of the same entity type, with the same matching name. If it can’t find one, it won’t
match the communicators and the model may be incorrectly assembled.
For example, whenever you create a mount part in your template, Adams/Car automatically creates a
corresponding input communicator. During assembly, this input communicator should match the correct
output mount communicator located in the test rig. If Adams/Car finds no matching output
communicator, it replaces the mount part with the ground part.
Adams/Car automatically creates an input communicator corresponding to that mount on the test rig.
Then, you need to create a matching output communicator on the template you are creating. These
communicators must have the exact same name for Adams/Car to know which communicators to use.
This is explained in detail in Defining Communicators.
100 Getting Started Using Adams/Car
Defining Communicators
For the assembly process to work correctly, you must define how the suspension is to connect to the
suspension test rig (_MDI_SUSPENSION_TESTRIG). To do this, you define the communicators that
attach the hub to the suspension test rig at the wheel center, as follows:
• To tell the suspension test rig to which part it needs to be connected, you define an output
communicator of type mount. This communicator accomplishes two tasks:
• Communicates the part to which the testrig is being connected.
• Defines the I part of the static lock actuator.
• To tell the suspension test rig where the connection takes place, you define an output
communicator of type location.
• To tell the suspension test rig which is the upright part (wheel carrier), to create a static lock
actuator, you define an output communicator of type mount. This communicators defines the J
part of the static lock actuator.
When you analyze the suspension in static mode, you must lock the hub to the wheel carrier. If you don’t
lock the hub to the wheel carrier, your assembly will have a rotational degree of freedom that prevents
the analysis from converging to a solution. Adams/Car creates the actuator between the hub and the
upright (wheel carrier), automatically based on the communicators mentioned above.
The Information window lists the mount input communicators. Notice that Adams/Car
automatically adds the prefix ci[lr] (which designates communicator input left or right) to the
name of input communicators. If you want to see the entire contents of the Information window,
use the vertical scroll bar. If you want to see the matching name for each communicator, use the
horizontal scroll bar.
6. Select Close.
102 Getting Started Using Adams/Car
Note: Adams/Car allows you to specify one or more Matching Names so that you can
designate different communicators for the front and rear subsystems in case you might be
using the same template for both subsystems. In this case, you’ll just leave it blank since
Adams/Car defaults to assigning the communicator name as the matching name if none is
specified.
6. Select Apply.
Adams/Car selects the hub as the part to which the test rig connects.
7. In the Output Communicator Name text box, enter suspension_upright.
8. In the Part Name text box, enter ._macpherson.gel_wheel_carrier.
9. Select Apply.
10. In the Output Communicator Name text box, enter wheel_center.
11. Set Entity to location.
12. Verify that To Minor Role is set to inherit.
13. In the Coordinate Reference Name text box, enter ._macpherson.ground. hpl_wheel_center.
14. Select OK.
Adams/Car will use this location communicator to select the location on the hub to which the test
rig connects.
Testing Communicators
To verify that you correctly specified the input and output communicators, you can test communication
in your template. Testing your communicators lets you find out whether to add or modify communicators
to ensure that your suspension template will assemble properly with the suspension test rig.
The Information window lists which communicators are matched, and which are not. First, it
shows you the matched communicators that are correctly sending and receiving information
between subsystems and test rigs. Notice that the mount communicators for
suspension_mount, suspension_upright, and wheel_center are listed in the
matched communicator section.
105
Template Builder Tutorial
The Information window also lists input and output communicators that are not matched
correctly. Many communicators are unmatched. Many of these communicators are related to
items such as the steering or chassis that we do not currently have open. When you start creating
your own templates, you can use the Information window to verify that you included all necessary
communicators.
3. Select Close.
Finishing Up
After you finish building the template, save it in your private database so you can use it later to create
suspension subsystems. Adams/Car assigns the extension .tpl to your template.
After you save your template, you can exit template-builder mode and start the Adams/Car Standard
Interface.
To create a subsystem:
1. From the File menu, point to New, and then select Subsystem.
2. Fill in the dialog box as shown next, and then select OK.
To modify hardpoints:
1. From the Adjust menu, point to Hardpoint, and then select Table.
2. Modify the hardpoint values to match those listed in Table 2:
3. Select Apply.
4. Select Cancel.
To define a preload:
1. Right-click either spring, point to the name of the spring, and then select Modify.
2. Set Installed Length to 135.0.
3. Select OK.
2. Fill in the dialog box as shown next, and then select OK.
Adams/Car performs the analysis and displays messages about the simulation.
3. When the analysis is complete, select Close.
Note that the elastic toe angle is greater than the toe angle as measured in kinematic mode.
117
Full-Vehicle Analysis Tutorial
Overview
This tutorial teaches you how to create a full-vehicle assembly, run different types of analyses, and view
the results.
To be able to run through this tutorial, you must have purchased the Adams/Car Vehicle Dynamics
Package.
This chapter includes the following sections:
• What You Will Create and Analyze
• Opening a Full-Vehicle Assembly
• Performing a Single Lane-Change Analysis
• Performing a Quasi-Static Constant-Radius Cornering (CRC) Analysis
• Performing a Baseline ISO Lane-Change Analysis
• To evaluate the vehicle’s understeer and oversteer characteristics, you run a constant radius
cornering analysis.
• To drive the vehicle through a lane-change course as described in ISO-3888, you run an ISO
lane-change analysis.
• After you run each analysis, you animate and plot its results.
121
Full-Vehicle Analysis Tutorial
To open an assembly:
1. Start Adams/Car Standard Interface as described in Starting Adams/Car Standard Interface.
2. From the File menu, point to Open, and then select Assembly.
Tip: For information on any dialog box, press F1 when the dialog box is active.
3. Right-click the Assembly Name text box, point to Search, and then select the acar_shared
database.
4. Double-click MDI_Demo_Vehicle.asy.
5. Select OK.
The Message Window appears, informing you that Adams/Car is opening the assembly.
6. When Adams/Car is done loading the assembly, select Close.
Adams/Car displays the full-vehicle assembly.
122 Getting Started Using Adams/Car
Adams/Car updates the force entities, such as dampers, springs, and bushings, with the values
specified in their property files and sets up the vehicle assembly for the maneuver. Setting up the
vehicle assembly includes adjusting the road height so the road is in contact with the tires and
deactivating certain motions and forces, depending on the type of steering input you selected and
the inputs you specified. For example, because you set the steering input to angle, Adams/Car
deactivates the torque on the steering wheel and the force on the rack, and activates a motion on
the steering wheel revolute joint.
The test rig, which is part of the assembly, applies the inputs you specified in the analysis
submission dialog box to the assembly, and performs a static analysis, followed by a dynamic
analysis.
3. When the analysis is complete, select Close.
124 Getting Started Using Adams/Car
After you animate, create plots using a plot configuration file (.plt), as explained next.
6. To view the rest of the plots, select them from the treeview. For example, to view the second plot,
select page_plot_2.
130 Getting Started Using Adams/Car
Adams/Car displays a plot of the chassis roll angle versus lateral acceleration.
7. Return to Adams/Car.
131
Full-Vehicle Analysis Tutorial
For information on the Driving Machine and XMLs, see the online help for Adams/Car.
Note: XML event files replace TiemOrbit DCF files. Adams/Car still supports DCF files, but it
automatically converts them to their XML representation.
115.0 3.586
140.0 0.172
147.0 0.172
155.0 0.172
162.0 0.172
170.0 0.172
200.0 0.172
300.0 0.172
400.0 0.172
500.0 0.172
For information on .dcd files, see the online help for Adams/Car.