Using Adams Durability with Adams Solver

Although we recommend that you use Adams View to access Adams Durability functionality, you can perform these functions directly within Adams Solver. This topic provides specific statement syntax that you can use to implement Adams Durability functionality in Adams Solver. For complete details on any statements in this topic, see the Adams Solver online help.

Adams Solver includes the INTERP function as part of Adams Durability support. When defining a motion or force with data from an RPC III Format or DAC Format file, you must define a spline with the data file as input, and use the INTERP function in the MOTION, GFORCE, SFORCE, or VFORCE statement. For example, you could define a translational motion as follows:

where:

With Adams Durability, the SPLINE statement includes arguments that let you input RPC III Format or DAC Format time history data files. These data files provide one dependent variable and one independent variable, TIME, as a fixed-time interval. Because RPC III files support multiple channels of data in a single file, you must specify a channel for this type of file. DAC time history files only have a single channel of data in a file.

The SPLINE statement, as it appears for durability analysis, looks like:

Where:

You use the FEMDATA statement to indicate the set of data you want Adams Solver to write for subsequent finite-element (FE) or durability analyses. You can specify loads on a component, modal coordinates or nodal deformations, or stresses or strains of a flexible body.

As part of Adams Durability, the OUTPUT statement indicates output options for each type of FEMDATA. You use the OUTPUT statement to specify the format of each type.

The following output formats may be available, depending on the type of data you are using:

You use the REQUEST statement to indicate the set of data you want Adams Solver to write. Adams Durability supports any existing form of the REQUEST statement. You can specify functions, forces, displacements, velocities, acceleration, and user requests.

As part of Adams Durability, the OUTPUT statement includes three additional output types, MATSAVE, RPCSAVE and DACSAVE. When you specify an OUTPUT statement with one of these types, Adams Solver writes the request to a file with a .mat, .rsp or .dac extension, respectively.

For MAT or RPC files, Adams Solver writes all of the requests to a single file. Because DAC files can only have a single channel per file, Adams Solver writes a separate file for each component of each request. Therefore, every request results in six output files.

The statement for RPC III output is:

The statement for DAC output is:

With Adams Durability you use the ARRAY statement to indicate the order and subset of request data you want Adams Solver to write to when saving to DAC, MAT or RPC III format. If you define any arrays that begins with the name “DUROUT*”, Adams Durability will use the numbers in the array to define the order and subset of request data to output. The odd numbers in the array specify the REQUEST ID to output, and the even numbers specify its components.

The text that follows “DUROUT” specifies the name of the formatted file. If no text is provided after the DUROUT array name, the run name is used by default to name the formatted file.

Will result in an RPC file named “example.rsp” with a total of six channels, 3 from REQUEST/101 and 3 from REQUEST/102 in the following order