Institute of Technology
  Technical Support
      Knowledge Base
      Product Updates
      Product Feedback
      User Forums
      My Requests
  Download Center
  Order Manuals








  Support for the MSC.ADAMS Community 

MSC.ADAMS 12.0 What's New

ADAMS Online Help ADAMS/Controls ADAMS/Flex ADAMS/Tire
ADAMS/Aircraft ADAMS/Driveline ADAMS/Hydraulics ADAMS/Vibration
ADAMS/Animation ADAMS/Driver ADAMS/Insight ADAMS/View
ADAMS/AutoFlex ADAMS/Durability ADAMS/PostProcessor MECHANISM/Pro
ADAMS/Car ADAMS/EDM ADAMS/Rail
ADAMS/Chassis ADAMS/Engine ADAMS/Solver

 
Changes to all ADAMS products?

For information about the changes that impact all ADAMS products, click here.

Which partner products are supported?

To see a list of the ADAMS 12.0 supported partner products, click here.


 
ADAMS Online Help and Documentation

For 12.0, MDI documentation has been enhanced to include:

  • Online help for ADAMS/Car, ADAMS/Driveline, ADAMS/EDM, ADAMS/Engine, ADAMS/Hydraulics, ADAMS/Insight, ADAMS/Vibration, and ADAMS/View. The online help provides you with quick access to information about how to fill in a dialog box and basic procedures. It also contains an index and search capability, as well as pop-up definitions of terms. 
  • You can access the online help by opening a dialog box and pressing F1. You can also use the commands on the Help menu in a product.
     

  • More tutorials. We've added more tutorials in the following online guides: 
    • Getting Started Using ADAMS/Aircraft - A new guide with many tutorials on using ADAMS/Aircraft. 
    • Using ADAMS/AutoFlex - Contains three tutorials for defining flexible bodies and reference material for general use of ADAMS/AutoFlex. 
    • Getting Started Using ADAMS/Engine Valvetrain powered by FEV - Contains new tutorials for using the new ADAMS/Engine component valvetrain. 
    • Getting Started Using ADAMS/Engine Basic Cranktrain powered by FEV - Contains new tutorials for using the new ADAMS/Engine component cranktrain. 
    • Using ADAMS/EDM - Contains a tutorial for using this new product. 
    • Getting Started Using ADAMS/Driveline - Contains two new tutorials for creating a driveline template for an all-wheel-drive transmission and for creating an entire gearbox model.

    •  
  • Updated online guides. In addition, we've:
    • Created a new guide on translating finite element model data to ADAMS.
    • Continued to expand our template-based guides
    • Added more information on ADAMS/Controls
    • Made it easier to learn about the argument for a statement in the guide, Using ADAMS/Solver. Just click on an argument in the format description of a statement to go directly to the description of that argument.
    • Added many more descriptions of functions to the guide, Using the ADAMS/View Function Builder

back to top

ADAMS/Aircraft (new product)
What is ADAMS/Aircraft?

ADAMS/Aircraft Landing Gear is a specialized environment for modeling landing gear and aircraft during various landing-gear test conditions. It lets you create virtual prototypes of aircraft and landing-gear subsystems and analyze these virtual prototypes much like you would analyze the physical prototypes or test aircraft.

ADAMS/Aircraft enables you to closely analyze the landing-gear subsystems of a Functional Digital Aircraft™. The following figure shows the elements of the functional digital aircraft, which should essentially be a virtual version of your complete, functional aircraft. Similar to a real aircraft, the digital aircraft is an assembly of many unique subsystems. ADAMS/Aircraft allows you to model subsystems and components with varying levels of fidelity. 


 

ADAMS/Aircraft features

ADAMS/Aircraft Landing Gear allows you to:

  • Use a standard tool appropriate for both initial design and analysis throughout the aircraft life cycle. After design changes or validation of components, you can quickly refine your models throughout your design cycle, and perform again the exact same tests/simulations to reevaluate the effects of the changes.
  • Leverage work across many other functional groups in your organization. The database structure and standardized data formats in ADAMS/Aircraft facilitate the sharing of models and data between organizations, including suppliers and customers, thereby enabling efficient engineering communication.
    • Expert users - After you verify and validate your virtual aircraft, you can publish these models for others to use. Designers, structural analysts, dynamicists, fatigue analysts, and performance analysts can use the same models and databases to perform their own analyses.
    • Standard users - You can use published models to perform your own studies, on an already validated model.
  • Test your virtual components and subsystems to verify and validate their behavior as an isolated unit, as you would with the actual hardware. You can therefore minimize unknowns when you assemble the virtual full aircraft.
  • Analyze design changes much faster and at a lower cost than physical prototype testing. You can, for example, change tires with a few mouse clicks instead of waiting for a mechanic to install them before testing your design again. After you have a new validated component or subsystem, you can quickly replace the old one with the new one, and simulate again.
  • Focus on analysis rather than on re-coding legacy software. Typically, in-house legacy code requires modifications when significantly-different designs appear. ADAMS/Aircraft enables you to quickly build new subsystems, without having to modify equations of motion, and so on.
  • Vary the kinds of analyses faster and easier than modifying instrumentation, test fixtures, and test procedures. After your virtual prototype is validated, you can use it in many different types of tests. If you can think of a real test, it can be set up and conducted in ADAMS/Aircraft.
  • Quickly run standard sets of load conditions for different configurations by using ASCII files you develop or by using properly formatted files developed by other organizations.
  • Exchange data with CAD and FEM software, such as CATIA® and NASTRAN®. Note that this requires the purchase of additional software. For example, CAT/ADAMS is required to exchange data with CATIA, and ADAMS/Flex is required to exchange data with NASTRAN.
Analyses supported in ADAMS/Aircraft
 


 
 

Online help for ADAMS/Aircraft dialog boxes 

Online help is now available for ADAMS/Aircraft dialog boxes. To view the online help information, press F1 on an active dialog box.
ADAMS/Aircraft, copyright © 1999-2002 Lockheed Martin Corporation and © 2002 Mechanical Dynamics, Incorporated. Those portions of the Software copyrighted by Lockheed Martin Corporation are used under license by Mechanical Dynamics, Inc. All rights reserved.

The Landing Gear Toolbox are trademarks of the Lockheed Martin Corporation.

See also:

back to top

ADAMS/Animation

Maintenance and support

Although no new features have been introduced, ADAMS/Animation has been maintained and tested to ensure that the familiar functionality continues to be operational. To that end, all known bugs reported in ADAMS/Animation have been resolved. In addition. ADAMS/Animation has been tested and verified on all available platforms (UNIX only).

Transition to ADAMS/PostProcessor

As the ADAMS/Animation product reaches the end of its life, it is suggested that you transition your ADAMS postprocessing tasks to ADAMS/PostProcessor. The current release of ADAMS/PostProcessor contains several new features to close the gap between ADAMS/Animation, including clearance studies and improved lighting. During the current development cycle, detailed benchmarking shows a favorable performance comparison. These new features, along with features unavailable in ADAMS/Animation, such as flex body support and advanced plotting, make ADAMS/PostProcessor more suitable for many postprocessing tasks. During the transition period, licenses of ADAMS/PostProcessor are provided in parallel with ADAMS/Animation.

The next release of the ADAMS product line will not include ADAMS/Animation.

See also:
ADAMS/Animation Release Notes

back to top

ADAMS/AutoFlex

Meshing of Parasolid objects

In ADAMS 12.0, we introduce the capability of meshing Parasolid-defined geometries that are either imported from a CAD application or automatically built using ADAMS/View. This capability expands on the meshing of simple extruded sections provided in the previous release.

Extrusion

With ADAMS 12.0, the dialog box that handles the extrusion part of the meshing capabilities was redefined. You can now efficiently navigate through the various options (section definition, centerline, mesh properties, and so on).
Parameterized centerline and attachments

The following capabilities are now available:

  • The AFI file named CENTERLINE_PARAMETERS contains a block containing (when used) the list of the points defining the centerline.
  • The ADAMS/AutoFlex dialog box now allows you to select (and store in the appropriate data table) centerline reference frames. 
  • When reading in an AFI file, ADAMS/AutoFlex checks for the presence of the CENTERLINE_PARAMETERS block. If it is present, the locations stored in the CENTERLINE block are compared with the ones of the object written in the CENTERLINE_PARAMETERS block. Then, if the locations are different, you can choose to update dialog box values with current reference frame positions. 
For ATTACHMENT points, a column vector of reference frame names is reported in the block data named VIEW_DATA (ACAR_DATA in acar). The functionality for changed ATTACHMENT locations is identical to the CP parameterization.

Attachments

For Parasolid-meshed objects, you can now automatically specify attachments in three ways. These three ways are by selecting the:
  • Master node (external marker or location) and picking the temporary-created mesh nodes that will be slaves in the connection. 
  • Master node and defining a sphere centered on it, with variable radius. In this case, the intersected nodes belonging to the temporary mesh and sphere will be slave nodes in the connection. 
  • Master node and defining a cylinder centered on it, with axes definable by pointing any admissible location in ADAMS/View. In this case, the intersected nodes belonging to the temporary mesh and cylinder will be slave nodes in the connection.
Modal Truck Frame Modeler available in ADAMS/Car

The Truck Frame Modeler is available when ADAMS/AutoFlex is accessed as a plug-in to ADAMS/Car. The Truck Frame Modeler assembles a given list of previously modeled components (such as cross-member and rails) into one single flexible body frame.

See also:

ADAMS/AutoFlex Release Notes 

back to top

ADAMS/Car

New suspension test rig 

The new suspension test rig allows you to: 
  • Include a real tire model (.tir) for suspension simulations.
  • Swap the real (sometimes called live) tire with a semi-rigid model. 
  • Specify additional loads acting between the road part and the wheel part. In particular: 
    • Cornering lateral force 
    • Damage lateral force and damage radius (application points of damage forces)
    • Traction forces at the wheel hub
    • Braking forces at the contact patch 
    • Overturning moment
    • Aligning torque
    • Braking torque
  • Control the suspension with a force-based approach. 
  • Drive the suspension with a set of closed-loop controllers whose feedback channels can be: 
    • Displacements at the wheel center
    • Displacements at the contact patch
    • Wheel vertical forces 
  • Perform total vertical force and roll angle sweep analysis.

Scale factors for conceptual suspension module 

We have made modifications to templates and source routines so you can scale individual characteristics of suspension components, allowing you to perform design of experiments and optimization on conceptual suspensions.

Integration with ADAMS/Driveline 

You now can run ADAMS/Car 12.0 full-vehicle analyses with a driveline model created by ADAMS/Driveline 12.0.

Support EDM MIMO models in ADAMS/Car

You can create an EDM model with a test machine and EDM from MTS, and import it into ADAMS/Car 12.0.

Online help for ADAMS/Car dialog boxes 

We've improved the online help for ADAMS/Car to include pop-up definitions of terms, searching, and an improved look. To view the online help information, press F1 on an active dialog box. 

Quasi-static analysis supported through the DCF

In this release of ADAMS/Car, you can perform static-setup analyses that remove startup transients and also allow you to eliminate mini-maneuvers that you might normally use to set up a vehicle for cornering maneuvers. For example, in the past, to perform a brake-in-turn analysis you might have run a transient mini-maneuver to have the vehicle turn-in and reach static-setup on a given turn at a given speed/lateral acceleration before starting to brake the vehicle. Now, using the new language in the EXPERIMENT block of the dcf file, you can use a much faster (less CPU time) static-setup analysis. 

For more information see the guide, Running Analyses in ADAMS/Car.

See also:

back to top

ADAMS/Chassis

What is ADAMS/Chassis?

ADAMS/Chassis is the replacement for ADAMS/Pre. It represents a major step in the ongoing process of commonizing ADAMS/Car and ADAMS/Pre. ADAMS/Chassis works with .xml data files and python templates, and features a more modern interface for editing vehicle data.

ADAMS/Chassis architecture 

ADAMS/Chassis has undergone significant architectural changes in 12.0, as part of the ADAMS/Chassis - ADAMS/Car commonization project. 

XML data
The first time you run ADAMS/Chassis 12.0, your 11.0 data will be transformed into a 12.0 XML database. All vehicle data is stored in XML, in a three-level hierarchy: 

  • System files - Contain information about the particular vehicle configuration you are working with, and reference subsystem files. 
  • Subsystem files - Are closely related to the old ADAMS/Chassis data files (.fst, .sst, .rst, and so on).
  • Property files - Are smaller files that contain properties for one component in your system, such as a bushing or a spring. 

New data attributes

The new XML data format also represents an enhanced set of modeling objects. In many cases, new attributes have been added to existing elements to provide you with new modeling features. A sample list of these new features is shown below (see the ADAMS/Chassis Release Notes and the ADAMS/Chassis Online Reference Guide for a more detailed listing).

  • Symmetry. For all left-right objects, you have the choice to specify symmetric or asymmetric properties. For symmetric, you can specify the left or right data. Parts, bushings, and other objects have symmetry properties.
  • Part Inertial Reference Frame. You can optionally specify an inertial reference frame for each part.
  • Connector Orientation. You can override the default orientation for each bushing in your model with either Euler angle specification or ZPXP specification.

Python templates 

The ADAMS/Chassis .aft files have been converted to a python representation, also as part of the ADAMS/Chassis - ADAMS/Car commonization project. A translator is available (on the command Line enter achassis -aft2py) to aid you in converting your existing personal .aft files.

ADAMS/Chassis graphical interface 

Visual Data editing dialog boxes
New visual editors have been developed in conjunction with the migration to an XML data format.

Key features of new Visual Editors include:

  • Spline data is grouped with the relevant object
  • You no longer have to manage spline ID’s
  • Component attachment for springs, dampers, and so on, is specified directly using names (Frame, Subframe, Lower control Arm) instead of numbers (10,11,1)
  • Visual editor for 3D splines
  • Copy and paste with Microsoft Excel (Windows only)
  • Detailed comment blocks available for all objects
  • Import function in subsystem data file for saved alignment settings
  • Radio-button interface for construction options
  • Hierarchical tree editor for groups of parameters

Modeling methods 

Manufacturing tolerance option for bushings
A new feature for bushings (connector objects in Release 12.0) allows you to simulate the effect of manufacturing tolerance. You can set optional XYZ offset parameters for the I and J markers of all bushings. This allows you to determine which tolerances will most affect your system performance.

This feature is available when you setup an experiment with ADAMS/Insight. For each connector you will see i_marker_tolerance (XYZ) and j_marker_tolerance (XYZ) factor candidates.

Dual-path strut mount bushing option
A dual-path strut mount option is available for strut-type suspensions (Front and Rear Macpherson, Rear Quadralink Strut). This option lets you model the top mount as a dual-path bushing. With this approach, you specify inner and outer bushing properties, and a rotational stiffness for the attachment between the inner and outer mounting parts.

This feature is available through a construction option in strut property files.

Double-cardon joint modeling option
A double-cardon option is available for use with steering column templates. With this option the lower universal joint is replaced with a double-cardon joint.

This feature is available through the construction option in steering column subsystem files.

Subsystem templates 

Trailer templates
New advanced trailer templates are available for modeling dual-axle trailers. The new templates represent load leveling and non-load leveling versions of a dual torsion spring axle system. Key parameters include stiffness, damping, reference torque, and reference angle for all four springs. The load leveling version has additional parameters for chain free length and geometric and material properties of the leveling bar.

Tilt-bracket steering column templates
A new steering column template is available for tilt-bracket steering columns. With this column type, the upper column is attached to a tilt bracket, which has a pivot point forward of the wheel. You can place slider joints in either the intermediate or upper steering column shafts to allow articulation of the column during tilt adjustment. The tilt setting (in degrees) is a user-specified parameter that lets you fix the tilt angle during a simulation.

Simulations 

Gristmill event
The gristmill event is similar to step steer. You enter a maximum steering wheel angle and the vehicle is quickly steered to that angle while maintaining a constant speed. Instead of specifying the steering wheel angle, you can optionally use the maximum rack travel parameter, which is in your steering gear subsystem file. The post processing for this event consists of loads and displacements in all four tires. This information can indicate the loads your wheel hubs will see in limit situations.

Frame compliance event
The frame compliance event is a new half-vehicle event that helps calculate the displacement/rotation of the wheel centers during body attachment displacement. The analysis involves moving each body attachment (one at a time) 1 mm in XYZ. The result of this analysis can be used to construct a compliance matrix for your suspension to help determine where local body compliance most affects system performance.

Integration with ADAMS/Driveline

You can now export data from ADAMS/Driveline to ADAMS/Chassis. The export utility creates an .xml powertrain subsystem file compatible with ADAMS/Chassis. This subsystem file contains the bulk of the driveline model, as well as some parameters that aid the connection of the driveline subsystem to the rest of the ADAMS/Chassis system.

Integration with ADAMS/PostProcessor

Named Channels in Plotting
This release of ADAMS/Chassis has a new feature that allows requests and request data to have names. ADAMS/Chassis 12.0 models contain named requests in its models. The benefit of this is that in ADAMS/PostProcessor you can traverse your simulation data using named entities, reducing the need to be familiar with the numerical ID’s and REQSUB (see the ADAMS/Chassis Online Reference Guide for additional information).

Integration with ADAMS/Insight

Multiple-event experiments
In previous releases you have been restricted to working with one event at a time when performing Design of Experiment analyses using ADAMS/Insight. In 12.0, however, you have the choice to include any subset of events from your current fingerprint. You select responses for each event, and the ADAMS/Chassis-ADAMS/Insight utility guides you through the process of generating, simulating, and post processing all the necessary models. With this new capability some rules are enforced, such as, all experiments must be performed in a new directory. The models for each event in your experiment are placed in individual subdirectories. In addition, if you add user responses for any of your events, you must name these responses with the same prefix as the candidate responses for that event.

Expanded factor candidate list
When you setup your experiment in ADAMS/Insight, a more complete set of factor candidates is available. Virtually every parameter from your model is available for variation in an ADAMS/Insight experiment.

“Do-It-All” batch option
The setup panel in the ADAMS/Insight interface box now provides the option to build, run, and post process your trial runs with one button. After these steps are complete, ADAMS/Insight automatically launches with your completed experiment.

See also:

back to top

ADAMS/Controls

Controls available as a plug-in

We rearchitected ADAMS/Controls to function as a plug-in.  This means that instead of starting ADAMS/Controls as a separate application, you load the ADAMS/Controls functionality directly into ADAMS/View, ADAMS/Car, or any other template-based product that supports it. You load plug-ins from the Tools à Plug-ins menu.  
Improved method for linking plant inputs and outputs

We simplified the process of defining inputs and outputs of the ADAMS plant to connect to a control system. You can identify a set of variables as the plant input and output (called PINPUT and POUTPUT, respectively) and use them to connect the plant and control system. Subsequent reconnections are simplified by the use of previously defined PINPUTs and POUTPUTs. You can use the same plant input and output definitions with linear and nonlinear plant export, and with the new control system import (see the following feature).

Control system import

ADAMS/Controls now supports the import of control systems into ADAMS/View from MATLAB, using code generated by MATLAB Real Time Workshop (RTW). MATLAB RTW exports the control system as a set of C code files. You can compile these files into an object library which you can then import into ADAMS and link to the ADAMS plant. The simulation with the control system then runs entirely within ADAMS using the ADAMS integrators. Imported control systems can have continuous or discrete states.  The RTW Import function is not yet supported for the template-based products. 

See also:

back to top

ADAMS/Driveline
New tutorials 

The guide, Getting Started Using ADAMS/Driveline, contains two new tutorials: 

  • Driveline Template Tutorial 
  • Gearbox Tutorial

Improved integration with ADAMS/Car 

You can run analyses in ADAMS/Car using the SDI test rig with the driveline assembled in the model. We added a new functionality to initialize the rotational velocity of the driveline elements so that all the SDI capability is now accessible within ADAMS/Driveline.

Integration with ADAMS/Chassis

ADAMS/Driveline 12.0 has an export to ADAMS/Chassis feature. This export utility creates an .xml powertrain subsystem file compatible with ADAMS/Chassis. This subsystem file contains the bulk of the driveline model, as well as some parameters that aid the connection of the driveline subsystem to the rest of the ADAMS/Chassis system.

New and improved driveline maneuvers 

Improved dropped-clutch maneuvers
You can now perform a dropped-clutch analysis in either open-loop or closed-loop mode. The closed-loop mode allows you to specify a desired engine RPM, and a controller will apply the relative torque. The open-loop mode for these maneuvers remains unchanged; you can specify the engine torque value.

New static loadcase analysis
We added an additional quasi-static maneuver. The static-loadcase analysis allows you to evaluate the driveline loads and displacements due to an external load condition. The static loads are stored in a property file that you specify when submitting the analysis. 

The simulation is a sequence of static equilibrium under different environmental conditions: at each static phase, the model is under the load condition specified in the property file. You specify the longitudinal, lateral, and vertical acceleration, and the torque value along the x, y, z of the reference marker. You can also specify the reference marker using a communicator. 

New RPM-sweep analysis
We also added another dynamic maneuver. The RPM-sweep analysis allows you to evaluate the driveline dynamic behavior when the engine passes from an initial RPM value to another one. You only need to specify the initial and final RPM values.

New torque-converter element 

We added a new component to model a torque converter. We implemented the element as a user-defined element. You must select the impeller, the case and the turbine parts, and ADAMS/Driveline then creates two torques. The expression of the torque depends on the selected property file in which you specify the torque ratio as a function of the omega ratio, and the reaction torque acting on the impeller as a function of the omega.

New clutch-connector element 

We added a new component to model a clutch connector. We implemented the element as a user-defined element. You must select the I part, the J part and a reference frame, and ADAMS/Driveline then creates a torque. The torque expression depends on a property file where you specify the drag coefficient, the positive velocity threshold with the related positive transmitted torque, and the negative velocity threshold with the relative negative transmitted torque. You can use this implementation to model the one-way clutch.

Online help for ADAMS/Driveline dialog boxes 

We improved the online help for ADAMS/Driveline to include pop-up definitions of terms, searching, and an improved look. To view the online help information, press F1 on an active dialog box. 
See also:

back to top

ADAMS/Driver
There are no significant changes to ADAMS/Driver. We incorporated the previous version of ADAMS/Driver with this version of the vehicle products, ADAMS/Car and ADAMS/Chassis.
See also:
ADAMS/Driver Release Notes

back to top

ADAMS/Durability
Stress or strain visualization 

ADAMS/Durability extends the capabilities of ADAMS/PostProcessor to animate dynamic stress or strain on flexible bodies, or plot time histories of nodal stress or strain measures, such as von Mises, maximum shear, principal, or individual components of stress or strain. These stresses or strains are obtained from popular Finite Element Analysis programs, such as NASTRAN (69.X), ANSYS (6.0), or ABAQUS (6.3) during the creation of the modal neutral file.

FEA modal stress recovery

With ADAMS/Durability you can choose to perform conceptual stress or strain studies in ADAMS, or more detailed stress or strain analyses in NASTRAN or ANSYS using ADAMS results of flexible bodies. You can export flexible body modal deformations to ANSYS or NASTRAN. ADAMS/Durability provides a special DMAP alter for importing these modal deformations and recovering stress or strain in NASTRAN. For ANSYS, ADAMS/Durability provides customized macros for importing modal information and recovering stresses or strains.

Improved FEA-loads export

FEA-loads export in ADAMS/View now runs significantly faster. Forces due to contact incidents are now supported. Time history output of component forces to DAC or RPC files for a subsequent load-based durability analysis is provided. In addition, we enhanced the FEMDATA and OUTPUT statements with ADAMS/Durability for outputting component loads to the various file formats directly from ADAMS/Solver. 

See the guide, Using ADAMS/Solver, for updates to the OUTPUT and FEMDATA statement.

nCode FE-Fatigue interface

ADAMS/Durability provides a convenient interface to nCode's FE-Fatigue for performing fatigue life prediction of components in your ADAMS simulation. Both linear and modal superposition fatigue analyses are supported. Time histories of component loads with correct polarity can be output in DAC or RPC format, and a unit load FEA input file for computing corresponding unit stress cases can be created for linear superposition in FE-Fatigue. 

Alternatively, a flexible body's modal coordinates can be output in DAC or RPC formats and the modal stress or strain data to nCode's partial FES file for modal superposition in FE-Fatigue. In both cases, a Load Association File (LAF) relating the time history data to the unit or modal stress data is automatically generated for input into FE-Fatigue. Results of an FE-Fatigue analysis in universal file format can be imported and displayed on the flexible body in ADAMS with ADAMS/Durability.

Experimental data filtering

To greatly improve simulations, use ADAMS/Durability to filter out noise or unwanted frequencies in test data before importing into ADAMS/Solver. A variable ordered, Butterworth, two-pass digital filter from MATLAB is available in the ADAMS/Durability toolkit for filtering experimental data in DAC or RPC III file formats. Four types of filters are provided: High-pass, Low-pass, Band-pass and Band-stop.

See also:

back to top

ADAMS/EDM

Multi-input/multi-output (MIMO) cross-coupled bushing element in ADAMS/EDM 

You can now use EDM for bushings as well as for dampers. Only translational forces are supported. You can use a fully-coupled MIMO bushing with three inputs and three outputs and bushings with a combination of inputs and outputs.

Amplitude or frequency-dependent models 

You can use complementary models stored in the ED model file, such as pure amplitude-dependent models or frequency-dependent models. If an ED model is created under different test conditions, you can select which test condition to use.

Stretching methods

ADAMS/EDM 12.0 allows you to scale time, input signals, and output signals through a method called stretching for both Single-Input/Single-Output (SISO) and Multiple-Input/Multiple-Output (MIMO) models.

Input stretching
This is the value that scales the input signals given to the ED model.

Output stretching
These are the values that scale the outputs of an ED model. If a force of 100N is calculated and the scale factor 0.5 is given, the ED model returns the force 50N.

VFORCE time stretching
This allows you to scale the EDM sample rate. If the original sample rate is 100 and the time stretch is 0.5, the adjusted sample rate is 50.

See also:

back to top

ADAMS/Engine

New lighting control

We modified the ADAMS/Engine interface to allow you to control the light sources in terms of angle, number, and some other effects. You can find this functionality through the Settings à Lighting menu.

ADAMS/Engine Basic Cranktrain (new module)

You can use this module to model cranktrains for any type of engine based on rigid bodies. You can use the models to determine free forces as well as internal forces. One of the outstanding features of this new module is the way the model fidelity can be adjusted to the task at hand in the engine development process at all times, while retaining most of the data from the previous step. For example, you can model the crankshaft as rigid, torsional flexible, or entirely flexible using the ADAMS beam elements just by changing an option menu in a dialog box. Also, several refinement levels are available for the bearings up to 3D hydro-dynamic bearings, which account for the misalignment of the shaft due to bending, for example. This general philosophy of ADAMS/Engine is also reflected in every element class of the cranktrain module.

Cranktrain wizard
You can use the wizard to quickly generate new templates. The wizard automatically creates all the engine components such as pistons and connections, bearings, as well as the gas forces. The result is a fully functional and parametric template. The W18 or an inline 12 layout, for example, are no problems.

Environment
A number of elements, such as gas force, temperature, and oil viscosity element, available in this category.

Engine data element
The engine global data element is the basis for most of the parametrics in the engine. This element mainly serves as a depository for engine parameters, such as bore and stroke.

Crankshaft
You can model the crankshaft as rigid, torsional flexible, or fully flexible. The mass properties, as well as the stiffness properties, are automatically derived from user input. You can define the counterweights to optimize the balancing of the system and minimize the bending stresses in the shaft, for example.

Engine mounts
Three different types of engine mount elements are included: a simple representation based on linear stiffness and two frequency-dependent mounts that represent rubber and hydro mounts.

Flywheels
Single-mass and dual-mass flywheel elements are available. The dual-mass flywheel accounts for the frequency-dependent behavior, which is based on the spring stiffness and its friction between the two parts.

Vibration damper
Visco and rubber vibration dampers are included. Both are frequency dependent elements. You can approximate the detailed coefficients based on the general parameters, such as loss angle and dynamic stiffness, or you can set them directly. 

Piston, conrod, and piston pin
Simple elements representing the piston, conrod, and piston-pin are available. You can either enter the mass and inertia information or derive it from the auto-generated geometry.

Balancing shafts
You can add balancing shafts to the system to compensate for forces and moments.

Virtual test rig
The test rig consists of up to five rotating masses coupled with rotational spring-dampers. You can select this number of masses in the virtual test rig to represent the real-world test rig. You can perform standard events, such as RPM sweep and list of RPMs.

Requests
Every component has a number of predefined outputs, such as the oil film thickness in the bearing. Beyond this, you can add your own request at any time.

ADAMS/Engine Valvetrain

Cam-generation capability
You can now generate cam profiles based on valve lift data. To do so, you must enhance an existing template of a single valvetrain, such that it also contains the new cam-generation element accessible through the Build à Environment à Cam Generation Element menu and constraints, in parallel to the already existing contacts. 

For all other components with compliance, such as the hydraulic lash adjuster, there should be a noncompliance component equivalent added to the template as well. The elements are then added to the kinematic-active and kinematic-inactive group such that the template can be switched from being a kinematic to being a dynamic model. 

In Standard Interface, you can run a cam-generation analysis through the Tools à Generate Cam menu. During this analysis, all elements in the kinematic active group are activated and all elements in the inactive group are deactivated, such that the cam profile can be synthesized from the valve lift input through the kinematic chain of the valvetrain.

New crosshead element
You can access the new crosshead (bridge) element through the Build à Valve Train à Crosshead menu in the template-builder interface. You can switch the crosshead element to be compliant or rigid.

New pivot follower element
You can access the new pivot follower element through the Build à Valve Train à Followers menu in the template-builder interface. This new element is a follower, which pivots about an attachment point compared to the typical translation layout of follower mechanisms. It is used with pushrod designs most of the time.

New rocker arm element
You can access the new rocker arm element through the Build à Valve Train à Rocker Arms menu in the template-builder interface. This new rocker arm element represents a rocker arm, which pivots about a point and consists of two parts connected using a rotational spring-damper element reflecting the bending stiffness of the component.

ADAMS/Engine Chain Drive

Silent chain
We added silent chain capability to ADAMS/Engine Chain Drive to let you simulate silent chain systems using a similar approach to that implemented for the roller and bush chains. This means that every link is modeled as a rigid body. The contacts between the links and the sprockets, and between the link and the guides are modeled through GFORCEs considering the detailed profile of the parts. We've also extended all chain requests to function with this chain type.

New involute sprocket element
You can access the new involute sprocket element through the Build à Timing Mechanism à Chain menu and use it to model sprockets, which have a tooth profile based on the analytical involute function. You can find more details on the profile description in the online help for this element. 

New silent chain link element
You can access the new silent chain link element through the Build à Timing Mechanism à Chain à Silent Chain Element menu. Here you can define the properties, wrap the chain, and add requests. You can define the profile of the silent chain links based on up to 14 sections per tooth. These sections can be either points (2 points = line) or arcs such that it is possible to model all sorts of profiles. Prior to wrapping the chain, you can check the profile directly in the dialog box, using the profile viewer.

Switchable model complexity
You can now decide if a detailed representation of the chain or a constraint-based modeling approach should be used in a model. The new constraint-based approach allows for a coupling between the sprockets of the chain drive under consideration of the sprocket tooth number, therefore the ratio. The motion of the guides will be ignored.

ADAMS/Engine Timing Belt

Switchable model complexity
You can now decide if a detailed representation of the timing belt or a constraint-based modeling approach should be used in the model. The new constraint-based approach allows for a coupling between the pulleys of the timing belt under consideration of the pulley tooth number, therefore the ratio. The motion of the deviation pulleys will be ignored.

ADAMS/Engine Accessory Drive

Separate friction coefficients
You can now decide to use different friction coefficients for each side of the belt.

Switchable model complexity
You can now decide if a detailed representation of the belt or a constraint-based modeling approach should be used in the model. The new constraint-based approach allows for a coupling between the pulleys of the belt under consideration of the pulley diameter, therefore the ratio. The motion of the deviation pulleys will be ignored.

Online help for ADAMS/Engine dialog boxes 

We've improved the online help for ADAMS/Engine to include pop-up definitions of terms, searching, and an improved look. To view the online help information, press F1 on an active dialog box. 

Waterfall plot

You can now create a waterfall plot to compare the frequency spectrum of an objective from different rotational speed conditions. You define the objective by selecting components from the dashboard in the same way you select components for the dependent axis of a plot.

ADAMS/Engine performs for each component an FFT for a given angular interval or an interval of a start and end number of rounds of the independent component. The result is clipped in frequency, rotational speed, and amplitude. The calculated rotational speed is the average of the interval.

See also:
  • ADAMS/Engine Release Notes 
  • Getting Started Using ADAMS/Engine Accessory Drive 
  • Getting Started Using ADAMS/Engine Chain Drive 
  • Getting Started Using ADAMS/Engine Cranktrain 
  • Getting Started Using ADAMS/Engine Timing Belt 
  • Getting Started Using ADAMS/Engine Valvetrain

back to top

ADAMS/Flex

Improved control for flexible body damping

In previous releases, specification of damping ratio for flexible bodies was limited to simplified, defaults, or through damping subroutines. Access to flex body damping has been expanded to allow a function expression for CRATIO. Damping ratio expressions can be also be defined in terms of two new intrinsic variables, FXMODE and FXFREQ, to access the flexible body's modes and frequencies.

Obtain flexible body states from user subroutines

You can now obtain information about flexible bodies through user subroutines. SYSARY has been expanded to provide access to flex body modal coordinates and their time derivatives. A new access routine, NMODES returns the number of modal coordinates in a specific flex body. Another new access routine, MODINF returns the active mode numbers and their corresponding frequencies.

Contour plots for MFORCE in ADAMS/PostProcessor 

When you define MFORCES for flexible bodies, you can display the force magnitudes in ADAMS/PostProcessor. This is useful for verifying the MFORCE definition while debugging models. The MFORCE color contours are displayed in Cartesian coordinates. For each view, you can control the legend position, scale, and number of gradients.

Flexible bodies supported by the new C++-based Solver

Expansion and transition of the new C++-based Solver continues with support of flexible bodies. The transition created the opportunity to make many improvements over the traditional implementation. These improvements create some differences in behavior which are noted below:

  • The C++ Solver creates the analysis frame at the undeformed center of mass, not the finite element model origin:
    • Inertia invariant two can therefore be neglected.
    • ADAMS results become more invariant to finite element modeling choices; for example, selecting the origin. 
  • The C++ Solver assumes the flexible body's normal modes are orthogonal to the rigid body modes: 
    • Inertia invariant three and four can therefore be neglected. 
    • This assumption requires that the structure cannot be constrained in the finite element model; that is, no SPCs.
  • Neglecting inertia invariants two, three, and four results in a computationally less expensive implementation.
  • Only the new formats for INVAR5 and INVAR9 in matrix file are supported. In an early version of the mnf2mtx translator, the format of the INVAR5 and INVAR9 matrices was flawed. Although the formatting error has since been corrected, the FORTRAN Solver continues to support the earlier format. The C++ Solver, however, will only support the new format, and a matrix file with the old format will result in an aborted simulation. Therefore, if either the C++ Solver issues any of the following error messages, you should use either the MNF toolKit or ADAMS/View to obtain a new flexible body matrix file with the new format: 

    • INVAR5 matrix should have (number of selected modes) rows and (3 times the number of selected modes) columns. 
    • INVAR9 matrix should have 3*(number of selected modes)*(number of selected modes) rows and 3 columns.

  • MFORCE is not supported yet.
See also:
ADAMS/Flex Release Notes

back to top

ADAMS/Hydraulics

Dynamic pipe models 

New dynamic pipe models have been added to ADAMS/Hydraulics to model the following: 
  • Fluid inertial effects 
  • Nonlinear pipe friction 
  • Waterhammer (pressure spikes) 
  • Acceleration/deceleration of fluid 
  • Eigenfrequency analysis (ADAMS/Linear and ADAMS/Vibration)
  • Pressure dependency of eigenfrequencies 
  • Exit and entrance losses of the pipe 
  • Capacitance, fluid, and wall flexibility of the pipe 
  • Speed of sound (or pressure wave) in a pipe causing time delays to the response of the pipe 
There are three different versions of the dynamic pipe model. They differ in the way they connect with the rest of the system (different port types):
  1. pipe_2ff 

  2. Inputs flow rates and outputs pressures
     
  3. pipe_2pp 

  4. Inputs pressures and outputs flow rates