Welcome to Adams/Solver Subroutines - Kxcad.net

Input Arguments
Welcome to Adams/Solver Subroutines
id An integer variable that provides the identifier of the REQUEST
statement requesting information from REQSUB. From the identifier,
Adams/Solver automatically knows other information (such as the par
argument) available in the corresponding statement.
iflag A logical variable that Adams/Solver sets to true for the initial call to
REQSUB. In general, you do not need to test this flag in the subroutine.
But if there are computations that need to be evaluated once at the
beginning of the simulation, you can test the iflag argument. In this case,
if the iflag argument is true, the subroutine should evaluate the
computations.
npar An integer variable that indicates the number of constants specified in
the USER parenthetical list. The primary purpose of npar is to provide
REQSUB with the number of values stored in the par array.
par A double-precision array of constants taken in order from the USER
parenthetical list of the REQUEST statement.
time A double-precision variable through which Adams/Solver conveys the
current simulation time.
Output Argument
result A double-precision array of eight values that contains the values you
calculate in the REQSUB. Adams/Solver sends all the values and the
current time to the tabular output file.
Extended Definition
If the dataset contains an OUTPUT statement with the REQSAVE
argument, Adams/Solver stores values two through four, and six through
eight in the request file for subsequent plotting in the postprocessor (see
the C++ OUTPUT command or the FORTRAN OUTPUT command).
Adams/Solver does not store columns one and five in the request file.
These columns usually contain translational and rotational magnitude
values for the request. If the dataset contains a RESULTS statement
without the NODATASTRUCTURES argument, Adams/Solver stores
all eight values in the results file for subsequent postprocessing. If fewer
than eight values are used in the result array, Adams/Solver sets the
remaining values to zero.
The REQUEST and MREQUEST statements are usually adequate for outputting displacement, velocity,
acceleration, or force data between two markers in the system. But if you want to output other quantities,
191