Frequency response analysis is a method used to compute structural response to steady-state oscillatory excitation.

Examples of oscillatory excitation include rotating machinery, unbalanced tires, and helicopter blades. In frequency response analysis the excitation is explicitly dened in the frequency domain. All of the applied forces are known at each forcing frequency. Forces can be in the form of applied forces and/or enforced motions (displacements, velocities, or accelerations).
Phase Shift

Oscillatory loading is sinusoidal in nature. In its simplest case, this loading is dened as having an amplitude at a specic frequency. The steady-state oscillatory response occurs at the same frequency as the loading. The response may be shifted in time due to damping in the system. The shift in response is called a phase shift because the peak loading and peak response no longer occur at the same time. An example of phase shift is shown in Figure 5-1.

Figure 5-1. Phase Shift

Complex Numbers

The important results obtained from a frequency response analysis usually include the displacements, velocities, and accelerations of grid points as well as the forces and stresses of elements. The computed responses are complex numbers dened as magnitude and phase (with respect to the applied force) or as real and imaginary components, which are vector components of the response in the real/imaginary plane. These quantities are graphically presented in Figure 5-2.

Error Messages 1-1000 01 *** USER WARNING MESSAGE 1, POSSIBLE ERROR IN DMAP INSTRUCTION *** INSTRUCTION NO. ***ASSUMED LAST INPUT DATA BLOCK IS NULL.
User has specified N input data blocks when there should be N+1. A frequent avoidance is simply to add one more comma to the input list if the last input block doesn't exist.

03 *** USER FATAL MESSAGE 3, ERROR IN DMAP INSTRUCTION *** INSTRUCTION NO. ** FORMAT ERROR IN PARAMETER NO. ***.
Double delimiter appears in parameter section of previous DMAP instruction.

04 *** SYSTEM FATAL MESSAGE 4, MPL PARAMETER ERROR, MODULE NAME = ******** PARAMETER NO. ***.
MPL entry for module is incorrect. See block data program XMPLBD.

06 *** USER FATAL MESSAGE 6, ERROR IN DMAP INSTRUCTION *** INSTRUCTION NO. ** ILLEGAL VALUE FOR PARAMETER NO. ***.
The type of parameter in DMAP instruction does not correspond to type requested in the MPL. For example, the location on the DMAP statement calls for an integer parameter and a real parameter has been entered.

07 *** USER FATAL MESSAGE 7, ERROR IN DMAP INSTRUCTION *** INSTRUCTION NO. ** PARAMETER NO. *** NEEDS PARAMETER NAME.
Parameter is not in correct format.

08 *** USER FATAL MESSAGE 8, BULK DATA PARAM CARD ERROR. MUST NOT DEFINE PARAMETER NAMED ********.
The "N" in V,N ******** means user cannot set the value of the parameter with name ******** on a PARAM card. In DMAP, when defining a parameter, the "N" in V,N ******** means user cannot set the value of the parameter with name ******** on a PARAM entry in Bulk Data.

09 *** USER FATAL MESSAGE 9, ERROR IN DMAP INSTRUCTION *** INSTRUCTION NO. ** VALUE NEEDED FOR PARAMETER NO. ***.
Constant needs value in a DMAP instruction or on a PARAM entry. There is a parameter in the referenced DMAP instruction which must have a value assigned before the execution of the module.

10 *** USER FATAL MESSAGE 10, ERROR IN DMAP INSTRUCTION *** INSTRUCTION NO. ** ILLEGAL INPUT SECTION FORMAT.
Too many or too few inputs are specified in the input for the referenced module.

11 *** USER FATAL MESSAGE 11, ERROR IN DMAP INSTRUCTION *** INSTRUCTION NO. ** ILLEGAL OUTPUT SECTION FORMAT.
Too many or too few outputs are specified in the input for the referenced module.

12 *** USER FATAL MESSAGE 12, ERROR IN DMAP INSTRUCTION NO. ** ILLEGAL CHARACTER IN DMAP INSTRUCTION NAME.

www.cadfamily.com EMail:cadserv21@hotmail.com The document is for study only,if tort to your rights,please inform us,we will delete

Name of a module must be alpha-numeric characters, the first character being alphabetic. Special characters are not allowed. For example DMAP names like "8MOD" or "SETI=2" are not allowed.

13 *** USER FATAL MESSAGE 13, ERROR IN DMAP INSTRUCTION *** INSTRUCTION NO. ** DMAP INSTRUCTION NOT IN MODULE LIBRARY.
The named DMAP refers to a non-existent module name. Check spelling.

14 *** SYSTEM FATAL MESSAGE 14, ARRAY NAMED ******** OVERFLOWED.

See XGPI module description in MFD section of Programmer's Manual. The usual cause is insufficient open core. In other cases, it may be necessary to divide the DMAP sequence into subDMAPs.

15 *** USER FATAL MESSAGE 15, ERROR IN DMAP INSTRUCTION *** INSTRUCTION NO. ** INCONSISTENT LENGTH USED FOR PARAMETER NAMED ********.
This parameter was used in a previous DMAP instruction which gave it a different type. See Section 5.2.1 of the User's Manual.

16 ***

USER FATAL MESSAGE 16, ILLEGAL FORMAT.

Usually caused by early termination such as a LABEL without a NAME.

17 *** USER FATAL MESSAGE 17, UNIDENTIFIED NASTRAN CARD KEYWORD ********. ACCEPTABLE KEYWORDS FOLLOW --- Compare your NASTRAN command to the list of acceptable keywords 18 *** USER FATAL MESSAGE 18, ERROR IN DMAP INSTRUCTION *** INSTRUCTION NO. ** TOO MANY PARAMETERS IN DMAP PARAMETER LIST.
Incorrect calling sequence for DMAP instruction. Compare the DMAP statement to the description in the User's Manual Section 5 or the Programmers Manual to find the error.

19 *** USER FATAL MESSAGE 19, ERROR IN DMAP INSTRUCTION *** INSTRUCTION NO. ** LABEL NAMED ******** IS MULTIPLY DEFINED.
LABEL named appears in more than one place in DMAP program.

22 *** USER FATAL MESSAGE 22, DATA BLOCK NAMED ******** MUST BE DEFINED PRIOR TO THIS INSTRUCTION.
See Section 5.2 of the User's Manual. Data blocks must be output before they can be input. A common mistake is to forget the DMAP statements DMIIN and DTIIN are required to read DMI and DTI matrices, respectively. Note that RF24D41 requires a DTIIN command (see Error Report 3734).

24 *** SYSTEM FATAL MESSAGE 24, CANNOT FIND FILE NAMED ******** ON DATA POOL TAPE.
Contents of /XDPL/ do not match contents of Pool Tape.

25 *** USER FATAL MESSAGE 25, ERROR IN DMAP INSTRUCTION *** INSTRUCTION NO. ** PARAMETER NAMED ******** HAS AN INCONSISTENT USER AUTHORIZATION.

www.cadfamily.com EMail:cadserv21@hotmail.com The document is for study only,if tort to your rights,please inform us,we will delete