NX Nastran 7.

1 Release
Guide

Proprietary & Restricted Rights Notice

2010 Siemens Product Lifecycle Management Software Inc. All Rights Reserved.
This software and related documentation are proprietary to Siemens Product Lifecycle
Management Software Inc.
NASTRAN is a registered trademark of the National Aeronautics and Space Administration.
NX Nastran is an enhanced proprietary version developed and maintained by Siemens
Product Lifecycle Management Software Inc.
MSC is a registered trademark of MSC.Software Corporation. MSC.Nastran and MSC.Patran
are trademarks of MSC.Software Corporation.
All other trademarks are the property of their respective owners.

TAUCS Copyright and License

TAUCS Version 2.0, November 29, 2001. Copyright (c) 2001, 2002, 2003 by Sivan Toledo,
Tel-Aviv University, [email protected]. All Rights Reserved.
TAUCS License:
Your use or distribution of TAUCS or any derivative code implies that you agree to this
License.
THIS MATERIAL IS PROVIDED AS IS, WITH ABSOLUTELY NO WARRANTY
EXPRESSED OR IMPLIED. ANY USE IS AT YOUR OWN RISK.
Permission is hereby granted to use or copy this program, provided that the Copyright,
this License, and the Availability of the original version is retained on all copies. User
documentation of any code that uses this code or any derivative code must cite the Copyright,
this License, the Availability note, and "Used by permission." If this code or any derivative
code is accessible from within MATLAB, then typing "help taucs" must cite the Copyright,
and "type taucs" must also cite this License and the Availability note. Permission to modify
the code and to distribute modified code is granted, provided the Copyright, this License, and
the Availability note are retained, and a notice that the code was modified is included. This
software is provided to you free of charge.
Availability
As of version 2.1, we distribute the code in 4 formats: zip and tarred-gzipped (tgz), with or
without binaries for external libraries. The bundled external libraries should allow you to
build the test programs on Linux, Windows, and MacOS X without installing additional

software. We recommend that you download the full distributions, and then perhaps replace
the bundled libraries by higher performance ones (e.g., with a BLAS library that is specifically
optimized for your machine). If you want to conserve bandwidth and you want to install
the required libraries yourself, download the lean distributions. The zip and tgz files are
identical, except that on Linux, Unix, and MacOS, unpacking the tgz file ensures that the
configure script is marked as executable (unpack with tar zxvpf), otherwise you will have to
change its permissions manually.

Contents

Dynamics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Multi-body dynamics and control system software interfaces . .
MBDEXPORT . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structural damping . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DDAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modal effective mass . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MEFFMASS . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selection of fluid modes . . . . . . . . . . . . . . . . . . . . . . . . . .
MODSEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Acoustic/fluid-structure coupling matrices . . . . . . . . . . . . . .
A2GG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PANEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modal and panel contributions . . . . . . . . . . . . . . . . . . . . . .
MODCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PANCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Support for damping element forces . . . . . . . . . . . . . . . . . .
FORCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Beta capability: Initial conditions for modal transient analysis
IC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sparse data recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unsymmetric A-set reduction for rotor dynamics . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

. . 1-1
. . 1-3
. 1-30
. 1-33
. 1-42
. 1-44
. 1-46
. 1-48
. 1-49
. 1-51
. 1-53
. 1-55
. 1-57
. 1-59
. 1-60
. 1-62
. 1-65
. 1-68
. 1-70
. 1-71
. 1-74
. 1-76
. 1-77
. 1-78

Superelements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
External superelements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EXTSEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-79
2-80

Advanced nonlinear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Advanced nonlinear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contact for linear solutions

3-87

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Solid element property regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-89

BCPROPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contact conditions with linear buckling . . . . . . . . . . . . . . . . . . . . . . . . .
Glue enhancements

4-90
4-90

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Edge-to-surface glue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BLSEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Solid element property regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-93
5-96
5-98

Bolt Preload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Combining and scaling bolt preload forces
BOLTFOR . . . . . . . . . . . . . . .
BOLTLD (bulk entry) . . . . . . . .
BOLTLD (case control) . . . . . . .
Bolt preload with contact definitions . . . .
Bolt stiffness update . . . . . . . . . . . . . .
Optimization

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

6-99
6-104
6-106
6-108
6-109
6-109

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Best design cycle . . . . . . . . . . . . . .

Updated bulk data output . . . . . . . .
ECHO . . . . . . . . . . . . . . .
PCOMPG support . . . . . . . . . . . . .
PSHELL structural damping support
PBUSH structural damping support .
Additional enhancements . . . . . . . .
New materials

.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

.
.
.
.
.
.
.

7-111
7-112
7-114
7-116
7-117
7-118
7-118

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

3-D orthotropic materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-121

MAT11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-122
MATT11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-124
Element enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Solid element support in solutions 106 and 129
Shell element material coordinate tolerance . .
Shell element thickness check . . . . . . . . . . .
CPYRAM in acoustics . . . . . . . . . . . . . . . . .

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

9-127
9-128
9-128
9-129

DMP improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Multilevel RDMODES enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . 10-131
GDSTAT method improvement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-132

Electromagnetics interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-135
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-135
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-137
Acoustics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Default updates . . . . . . . .
CPYRAM in acoustics . . . .
Alternative coupling option
ACMODL . . . . . .

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

12-141
12-141
12-142
12-143

Windows I/O Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Upward compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Updated modules . .
New modules . . . .
Updated datablocks
New datablocks . . .

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

14-151
14-168
14-171
14-210

NX NASTRAN 7.1 problem report (PR) fixes . . . . . . . . . . . . . . . . . 15-1

System description summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

Chapter

Dynamics

Multi-body dynamics and control system software interfaces

The capability to export a state-space (first-order) representation of a dynamic
system was added with NX Nastran 7. The state-space representation is generated
from an NX Nastran normal modes solution and written to an OUTPUT4 file.
Outside of NX Nastran, you can convert the OUTPUT4 file to a format readable
by third-party control system software.
Beginning with NX Nastran 7.1, the capability to export dynamic system
representations has been enhanced. Now you can also:

Export a standard (second-order) representation of a dynamic system to an

OUTPUT4 file for use with control system software.

Export a standard or state-space representation of a dynamic system to a

MATLAB script file.

You can access the new capabilities using the MBDEXPORT case control command.
To request a standard representation written to an OUTPUT4 file, specify the
following describers:
OP4=unit
STANDARD
FLEXBODY=YES
A new describer, MATLAB, has been created to request a MATLAB script file.
To request a standard representation written to a MATLAB script file, specify
the following describers:
MATLAB
STANDARD
FLEXBODY=YES

Multi-body dynamics and control system software interfaces

To obtain a state-space representation written to a MATLAB script file, specify
the following describers:
MATLAB
STATESPACE
FLEXBODY=YES
For a mathematical description of the standard and state-space representations of
a dynamic system, see Multi-body Dynamics and Control System Interfaces in
the Advanced Dynamic Analysis Users Guide.
See the updated MBDEXPORT case control command.

MBDEXPORT
Multi-Body Dynamics Export

MBDEXPORT

Multi-Body Dynamics Export

Generates interface file for third-party multi-body dynamics and control system
software during a normal mode solution (SOL 103).
Format:

The general examples, describers, and remarks are an overview for all interface
types. Below this are specific examples, describers, and remarks sections for each
interface type.
General Examples:
MBDEXPORT
MBDEXPORT
MBDEXPORT
MBDEXPORT
MBDEXPORT
MBDEXPORT

ADAMS STANDARD FLEXBODY=YES FLEXONLY=NO

FLEXBODY=YES MINVAR=FULL
OP4=22 STANDARD FLEXBODY=YES
OP4=22 STATESPACE FLEXBODY=YES
MATLAB STANDARD FLEXBODY=YES
MATLAB STATESPACE FLEXBODY=YES

General Describers:
Describer

Meaning

ADAMS

Generate ADAMS Interface Modal Neutral File (MNF).

RECURDYN

Generate RecurDyn Flex Input (RFI) file. (default)

MBDEXPORT
Multi-Body Dynamics Export
Describer

Meaning

OP4

Generate OP4 file.

MATLAB

Generate MATLAB script file.

STANDARD

Matrices are based on standard second order differential

equations of motion. (default)

STATESPACE

Matrices are based on first order differential equations that

represent the equations of motion, and are suitable for use with
control system software.

General Remarks:
1.

Only one choice of ADAMS, RECURDYN, OP4, or MATLAB is allowed and must
immediately follow the MBDEXPORT command.

2.

The describers can be truncated to the first 4 characters.

3.

STATESPACE is not valid for ADAMS or RECURDYN.

The information from this point on is specific to each interface type.

RECURDYN STANDARD Describers:

Describer

FLEXBODY
NO
YES
FLEXONLY

YES
NO

MINVAR

Meaning

Requests the generation of RFI (required).

Standard NX Nastran solution without RFI creation. (default)
RFI generation requested.
Determines if DMAP solution and data recovery runs or not
after RFI creation is complete.
Only RFI creation occurs. (default)
RFI file creation occurs along with standard DMAP solution
and data recovery.
Determines how mass invariants are computed.

MBDEXPORT
Multi-Body Dynamics Export

Describer

PARTIAL
CONSTANT
FULL
NONE
PSETID

Meaning

Mass invariants 6 and 8 are not computed. (default)

Mass invariants 1,2,3 and 9 are computed.
All nine mass invariants are computed.
No mass invariants are computed.
Selects a set of elements defined in the OUTPUT(PLOT)
(including PLOTEL) whose connectivity is exported into the
RFI. (See Remark 16)

NONE

No specific sets are selected, thus all grids, geometry and

associated modal data are written to RFI. (default)

setid

The connectivity of a specific element set is used to export face

geometry.

ALL

The connectivity of all element sets are used to export face

geometry.

OUTGSTRS
NO
YES
OUTGSTRN
NO
YES
RECVROP2

NO
YES

Determines if grid point stress is written to RFI.

Do not write grid point stress to RFI. (default)
Write grid point stress to RFI.
Determines if grid point strain is written to RFI.
Do not write grid point strain to RFI. (default)
Write grid point strain to RFI.
Requests that the FLEXBODY run output an NX Nastran OP2
file for use in post processing of RecurDyn/Flex results.
OP2 file will not be generated. (default)
OP2 file will be generated.

MBDEXPORT
Multi-Body Dynamics Export

Describer

CHECK

Meaning

Requests debug output be written to the f06 file when

RECVROP2=YES. (See Remark 20)
NO
YES

No debug output will be written. (default)

Debug output will be written.

RECURDYN STANDARD Remarks:

1.

The creation of the RecurDyn Flex Input file is applicable in a non-restart SOL
103 analysis only. RFI files are named jid_seid.rfi, where seid is the integer
number of the superelement (0 for residual-only run). These files are located in
the same directory as the jid.f06 file.

2.

The creation of the RecurDyn Flex Input file is initiated by MBDEXPORT

RECURDYN FLEXBODY=YES (other describers are optional) and the inclusion
of the bulk data entry DTI,UNITS.

3.

The Data Table Input Bulk Data entry DTI,UNITS, which is required for an
MBDEXPORT RECURDYN FLEXBODY=YES run, is used to specify the system
of units for the data stored in the RFI (unlike NX Nastran, RecurDyn is not a
unitless code). Once identified, the units will apply to all superelements in the
model. The complete format is:
DTI

UNITS

MASS

FORCE

LENGTH

TIME

All entries are required. Acceptable character strings are listed below.
Mass:
KG - kilogram
LBM pound-mass (0.45359237 kg)
SLUG slug (14.5939029372 kg)
GRAM gram (1E-3 kg)
OZM ounce-mass (0.02834952 kg)
KLBM kilo pound-mass (1000 lbm) (453.59237 kg)
MGG megagram (1E3 kg)
MG milligram (1E-6 kg)

MBDEXPORT
Multi-Body Dynamics Export
MCG microgram (1E-9 kg)
NG nanogram (1E-12 kg)
UTON U.S. ton (907.18474 kg)
SLI slinch (175.1268352 kg)
Force:
N Newton
LBF pound-force (4.44822161526 N)
KGF kilograms-force (9.80665 N)
OZF ounce-force (0.2780139 N)
DYNE dyne (1E-5 N)
KN kilonewton (1E3 N)
KLBF kilo pound-force (1000 lbf) (4448.22161526 N)
MN millinewton (1E-3 N)
MCN micronewton (1E-6 N)
NN nanonewton (1E-9 N)
CN centinewton (1E2 N)
P poundal (0.138254954 N)
Length:
M meter
KM kilometer (1E3 m)
CM centimeter (1E-2 m)
MM millimeter (1E-3 m)
MI mile (1609.344 m)
FT foot (0.3048 m)
IN inch (25.4E-3 m)
MCM micrometer (1E-6 m)
NM nanometer (1E-9 m)
A Angstrom (1E-10 m)
YD yard (0.9144 m)

MBDEXPORT
Multi-Body Dynamics Export
ML mil (25.4E-6 m)
MCI microinch (25.4E-9 m)
Time:
S second
H hour (3600.0 sec)
MIN-minute (60.0 sec)
MS millisecond (1E-3 sec)
MCS microsecond (1E-6 sec)
NS nanosecond (1E-9 sec)
D day (86.4E3 sec)
4.

Because DTI,UNITS determines all units for the RFI, the units defined in
WTMASS, which are important for units consistency in NX Nastran, are ignored
in the output to the RFI. For example, if the model mass is in kilograms, force in
Newtons, length in meters, and time in seconds, then WTMASS would equal 1
ensuring that NX Nastran works with the consistent set of kg, N, and m. The
units written to the RFI would be: DTI,UNITS,1,KG,N,M,S.

5.

You can create flexible body attachment points by defining the component as a
superelement or part superelement, in which case the physical external (a-set)
grids become the attachment points; or for a residual-only type model, you can
use NX Nastran ASET Bulk Data entries to define the attachment points.

6.

The eight mass variants are:

MBDEXPORT

Multi-Body Dynamics Export

sp = [xyz]T are the coordinates of grid point p in the basic coordinate system.

fp = partitioned orthogonal modal matrix that corresponds to the translational

degrees of freedom of grid p.
Ip = inertia tensor p.
fp* = partitioned orthogonal modal matrix that corresponds to the rotational
degrees of freedom of grid p.
= skew-symmetric matrix formed for each grid translational degree of
freedom for each mode.
M = number of modes.
N = number of grids.
7.

To accurately capture the mode shapes when supplying SPOINT/QSET

combinations, the number of SPOINTS (ns) should be at least ns=n+(6+p),
assuming that residual flexibility is on. In the above equation for ns, the number
of modes (n) is specified on the EIGR (METHOD=LAN) or EIGRL Bulk Data
entries; the number of load cases is p. In general, you cannot have too many
SPOINTs, as excess ones will be truncated with no performance penalty.

8.

For FLEXBODY=YES runs, residual vectors for the component should always be
calculated as they result in a more accurate representation of the component
shapes with little additional computational effort.

10

MBDEXPORT
Multi-Body Dynamics Export
9.

OMIT or OMIT1 Bulk Data entries are not supported.

10. Lumped mass formulation (default) is required. Either leave

PARAM,COUPMASS out of the input file or supply PARAM,COUPMASS,-1
(default) to ensure lumped mass.
11. P-elements are not allowed because they always use a coupled mass formulation.
Likewise, the MFLUID fluid structure interface is not allowed because the
virtual mass matrix it generates is not diagonal.
12. PARAM,WTMASS,value with a value other than 1.0 may be used with an NX
Nastran run generating an RFI. It must have consistent units with regard to
the DTI,UNITS Bulk Data entry. Before generating the RFI, NX Nastran will
appropriately scale the WTMASS from the physical mass matrix and mode
shapes.
13. There is a distinction between how an MBDEXPORT RECURDYN
FLEXBODY=YES run handles element-specific loads (such as a PLOAD4
entry) versus those that are grid-specific (such as a FORCE entry), especially
when superelements are used. The superelement sees the total element-specific
applied load. For grid-specific loads, the loads attached to an external grid will
move downstream with the grid. That is to say, it is part of the boundary and not
part of the superelement. This distinction applies to a superelement run and not
to a residual-only or parts superelement run.
14. The loads specified in NX Nastran generally fall into two categories: non-follower
or fixed direction loads (non-circulatory) and follower loads (circulatory). The
follower loads are nonconservative in nature. Examples of fixed direction loads
are the FORCE entry or a PLOAD4 entry when its direction is specified via
direction cosines. Examples of follower loads are the FORCE1 entry or the
PLOAD4 entry when used to apply a normal pressure. By default in NX
Nastran, the follower loads are always active in SOL 103 and will result in
follower stiffness being added to the differential stiffness and elastic stiffness of
the structure. In a run with MBDEXPORT RECURDYN FLEXBODY=YES and
superelements, if the follower force is associated with a grid description (such as
a FORCE1) and the grid is external to the superelement, the follower load will
move downstream with the grid. Thus, the downstream follower contribution
to the components stiffness will be lost, which could yield poor results. This
caution only applies to a superelement run and not to a residual-only or a part
superelement run.
15. OUTGSTRS and OUTGSTRN entries require the use of standard NX Nastran
STRESS= or STRAIN= used in conjunction with GPSTRESS= or GPSTRAIN=
commands to produce grid point stress or strain. GPSTRESS(PLOT)= or
GPSTRAIN(PLOT)= will suppress grid stress or strain print to the NX Nastran
.f06 file.

MBDEXPORT

11

Multi-Body Dynamics Export

16. To reduce the FE mesh detail for dynamic simulations, PSETID can include
the ID of a SET entry. The SET entry lists PLOTEL or element IDs, whose
connectivity is exported into the RFI to display the components in RecurDyn.
This option can significantly reduce the size of the RFI without compromising
accuracy in the FunctionBay simulation providing that the mass invariant
computation is requested. With superelement analysis, for any of these elements
that lie entirely on the superelement boundary (all of the elements grids are
attached only to a-set or exterior grids), a SEELT Bulk Data entry must be
specified to keep that display element with the superelement component. This
can also be accomplished using PARAM, AUTOSEEL,YES. The SEELT entry is
not required with parts superelements, as boundary elements stay with their
component.
If the SET entry points to an existing set from the OUTPUT(PLOT) section,
this single set is used explicitly to define elements that are used to select grids
to display the component in RecurDyn. If PSETID does not find the set ID in
OUTPUT(PLOT), it will search sets in the case control for a matching set ID.
This matching set ID then represents a list of OUTPUT(PLOT) defined elements
sets. The union of which will be used to define a set of PLOTELs or other
elements used to select grids to display the component in RecurDyn. If you wish
to select all of the sets in the OUTPUT(PLOT) section, then use PSETID=ALL.
The following element types are not supported for writing to an RFI, nor are
they supported as a type entry in a set definition in OUTPUT(PLOT): CAABSF,
CAEROi, CDUMi, CHACAB, CHACBR, CHBDYx, CDAMP3, CDAMP4,
CELAS3, CELAS4, CFLUIDi, CMASS3, CMASS4, CRAC2D, CRAC3D,
CTRMEM, CTWIST, CWEDGE, CWELD, and GENEL.
17. Typical NX Nastran data entry requirements are described below.
Typical Parameters:

PARAM,RESVEC,character_value controls calculation of residual vector

modes.

PARAM,GRDPNT,value - mass invariants 1I, 2I, and 3I will be computed

using results of NX Nastran grid point weight generator execution in the
basic coordinate system.

Typical Case Control:

MBDEXPORT RECURDYN FLEXBODY=YES is required for RFI

generation.

METHOD=n is required before or in the first subcase for modal solutions.

SUPORT1=seid is necessary to select a static support set for a residual

only linear preload run.

12

MBDEXPORT
Multi-Body Dynamics Export

SUPER=n,SEALL=n is useful with multiple superelement models to select

an individual superelement as a flexible body. Cannot be used with a linear
STATSUB(PRELOAD) run.

OUTPUT(PLOT) is necessary to define elements used to select grids to

display the component in RecurDyn when PSETID=ALL or setid.
SET n=list of elements (including PLOTELs) is used to select grids to
display the component.

OUTPUT(POST) is necessary to define volume and surface for grid stress

or strain shapes.
SET n=list is a list of elements for surface definition for grid stress or strain
shapes.
Stress and strain data in the RFI is limited to the six components (that is, 3
normal and 3 shear) for a grid point for a given mode.
SURFACE n SET n NORMAL z3 is used to define a surface for writing stress
and strain data. Only one FIBER selection is allowed for each SURFACE,
thus the use of the FIBER ALL keyword on the SURFACE case control
command will write stresses to the RFI at the Z1 fiber location only.
Since the FIBER keyword only applies to stresses, strain data will always be
written to the RFI at the MID location.
Stress and strain data at grid points can only be written to the RFI for
surface and volume type elements (for example, CQUAD and CHEXA).
VOLUME n SET n is a volume definition.
The default SYSTEM BASIC is required with SURFACE or VOLUME.

STRESS(PLOT) is necessary for stress shapes.

STRAIN(PLOT) is necessary for strain shapes.

GPSTRESS(PLOT) is necessary for grid point stress shapes to be included

in the RFI.

GPSTRAIN(PLOT) is necessary for grid point strain shapes to be included

in the RFI.
Typical Bulk Data:

DTI,UNITS,1,MASS,FORCE,LENGTH,TIME is required for RFI generation.

For input files containing superelements, this command must reside in the
main bulk data section.

MBDEXPORT

13

Multi-Body Dynamics Export

SPOINT,id_list defines and displays modal amplitude.

SESET,SEID,grid_list defines a superelement (see GRID and BEGIN BULK

SUPER=). The exterior grids will represent the attachment points along
with the q-set.

SEELT,SEID,element_list reassigns superelement boundary elements to

an upstream superelement.

RELEASE,SEID,C,Gi is an optional entry that removes DOFs from an

attachment grid for which no constraint mode is desired. For example, this
allows the removal of rotational degrees of freedom from an analysis where
only translational degrees of freedom are required.

SEQSET,SEID,spoint_list defines modal amplitudes of a superelement (see

SEQSET1).

SENQSET,SEID,N defines modal amplitudes of a part superelement. It

must reside in the main Bulk Data Section.

ASET,IDi,Ci defines attachment points for a residual-only run (see ASET1).

QSET1,C,IDi defines modal amplitudes for the residual structure or modal

amplitudes for a part superelement (see QSET).

SUPORT1,SID,IDi,Ci defines the static support for a preload condition

with a residual-only run. This entry is case control selectable. Do not use
SUPORT.

PLOTEL,EID,Gi can be used, along with existing model elements, to define

elements used to select grids to display the components in RecurDyn.

EIGR,SID,METHOD, obtains real eigenvalue extraction (see EIGRL).

18. MBDEXPORT and ADAMSMNF case control entries cannot be used in the same
analysis run. In other words, a RecurDyn RFI file or an ADAMS MNF file can be
generated during a particular NX Nastran execution, but not both files at the
same time. Attempting to generate both files in the same analysis will cause an
error to be issued and the execution to be terminated.
19. The RECVROP2=YES option is used when you would like results recovery (using
the MBDRECVR case control entry) from an RecurDyn/Flex analysis. This
option requires the following assignment command:
ASSIGN OUTPUT2=name.out STATUS=UNKNOWN UNIT=20
FORM=UNFORM

14

MBDEXPORT
Multi-Body Dynamics Export
be inserted into the file management section of the NX Nastran input file. It
will cause an OP2 file with a .out extension to be generated, which then can be
used as input into an NX Nastran SOL 103 run using the MBDRECVR case
control capability to perform results recovery from an RecurDyn/Flex analysis.
FLEXBODY=YES is required with its use.
The data blocks output are:
MGGEW - physical mass external sort with weight mass removed
MAAEW - modal mass
KAAE - modal stiffness
CMODEXT - component modes.
This capability is limited to no more than one superelement per NX Nastran
model. Residual-only analyses are supported.
20. Setting CHECK=YES (which is only available when RECVROP2=YES) is not
recommended for models of realistic size due to the amount of data that will
be written to the f06.
21. The MBDEXPORT data routines use the environment variable TMPDIR for
temporary storage during the processing of mode shape data. As a result,
TMPDIR must be defined when using MBDEXPORT. TMPDIR should equate
to a directory string for temporary disk storage, preferably one with a large
amount of free space.
ADAMS STANDARD Describers:
Describer
FLEXBODY
NO
YES
FLEXONLY

YES
NO
MINVAR
PARTIAL

Meaning
Requests the generation of MNF.
Standard NX Nastran solution without MNF creation. (default)
MNF generation requested.
Determines if DMAP solution runs or not after MNF creation is
complete.
Only MNF creation occurs. (default)
MNF file creation occurs along with standard DMAP solution.
Determines how mass invariants are computed.
Mass invariants 5 and 9 are not computed. (default)

MBDEXPORT

15

Multi-Body Dynamics Export

Describer

Meaning

CONSTANT

Mass invariants 1,2,6 and 7 are computed.

FULL
NONE
PSETID

All nine mass invariants are computed.

No mass invariants are computed.
Selects a set of elements defined in the OUTPUT(PLOT) section
(including PLOTEL) or on a sketch file whose connectivity is
exported to face geometry to be used in ADAMS. (See Remark
15)

NONE

All grids, geometry and associated modal data is written to

MNF. (default)

setid

The connectivity of a specific element set is used to export face

geometry.

ALL

The connectivity of all element sets are used to export face

geometry.

sktunit

OUTGSTRS
NO
YES
OUTGSTRN
NO
YES
RECVROP2

NO
YES

The connectivity of element faces defined on a sketch file is used

to export face geometry. Note that the value must be a negative
number to distinguish it from a setid value.
Determines if grid point stress is written to MNF.
Do not write grid point stress to MNF. (default)
Write grid point stress to MNF.
Determines if grid point strain is written to MNF.
Do not write grid point strain to MNF. (default)
Write grid point strain to MNF.
Requests that the FLEXBODY run output an NX Nastran OP2
file for use in post processing of ADAMS/Flex results.
OP2 file will not be generated. (default)
OP2 file will be generated.

16

MBDEXPORT
Multi-Body Dynamics Export
Describer
CHECK

Meaning
Requests debug output be written to the f06 file when
RECVROP2=YES. (See Remark 18)

NO
YES

No debug output will be written. (default)

Debug output will be written.

ADAMS STANDARD Remarks:

1.

The creation of the Adams MNF, which is applicable in a non-restart SOL 103
analysis only, is initiated by MBDEXPORT ADAMS FLEXBODY=YES (other
describers are optional) and the inclusion of the bulk data entry DTI,UNITS.
MNF files are named jid_seid.mnf, where seid is the integer number of the
superelement (0 for residual-only run). The location of these files is the same
directory as the jid.f06 file.

2.

The Data Table Input Bulk Data entry DTI,UNITS, which is required for an
MBDEXPORT ADAMS FLEXBODY=YES run, is used to specify the system
of units for the data stored in the MNF. Unlike NX Nastran, ADAMS is not a
unitless code. Once identified, the units will apply to all superelements in the
model. The complete format is:
DTI

UNITS

MASS

FORCE

LENGTH

TIME

All entries are required. Acceptable character strings are listed below.
Mass:
KG - kilogram
LBM pound-mass (0.45359237 kg)
SLUG slug (14.5939029372 kg)
GRAM gram (1E-3 kg)
OZM ounce-mass (0.02834952 kg)
KLBM kilo pound-mass (1000 lbm) (453.59237 kg)
MGG megagram (1E3 kg)
MG milligram (1E-6 kg)
MCG microgram (1E-9 kg)
NG nanogram (1E-12 kg)
UTON U.S. ton (907.18474 kg)

MBDEXPORT
Multi-Body Dynamics Export
SLI slinch (175.1268352 kg)
Force:
N Newton
LBF pound-force (4.44822161526 N)
KGF kilograms-force (9.80665 N)
OZF ounce-force (0.2780139 N)
DYNE dyne (1E-5 N)
KN kilonewton (1E3 N)
KLBF kilo pound-force (1000 lbf) (4448.22161526 N)
MN millinewton (1E-3 N)
MCN micronewton (1E-6 N)
NN nanonewton (1E-9 N)
Length:
M meter
KM kilometer (1E3 m)
CM centimeter (1E-2 m)
MM millimeter (1E-3 m)
MI mile (1609.344 m)
FT foot (0.3048 m)
IN inch (25.4E-3 m)
MCM micrometer (1E-6 m)
NM nanometer (1E-9 m)
A Angstrom (1E-10 m)
YD yard (0.9144 m)
ML mil (25.4E-6 m)
MCI microinch (25.4E-9 m)
Time:
S second
H hour (3600.0 sec)

17

18

MBDEXPORT
Multi-Body Dynamics Export
MIN-minute (60.0 sec)
MS millisecond (1E-3 sec)
MCS microsecond (1E-6 sec)
NS nanosecond (1E-9 sec)
D day (86.4E3 sec)
3.

Since DTI,UNITS determines all units for the MNF, the units defined in
WTMASS, which are important for units consistency in NX Nastran, are ignored
in the output to the MNF. For example, if the model mass is in kilograms, force
in Newtons, length in meters, and time in seconds, then WTMASS would equal
1, ensuring that NX Nastran works with the consistent set of kg, N, and m. The
units written to the MNF would be: DTI,UNITS,1,KG,N,M,S.

4.

You can create flexible body attachment points by defining the component as a
superelement or part superelement, in which case the physical external (a-set)
grids become the attachment points. For a residual-only type model, you can use
standard NX Nastran ASET Bulk Data entries to define the attachment points.

5.

The nine mass variants are:

MBDEXPORT

19

Multi-Body Dynamics Export

sp = [xyz]T are the coordinates of grid point p in the basic coordinate system.

fp = partitioned orthogonal modal matrix that corresponds to the translational

degrees of freedom of grid p.
Ip = inertia tensor p.
fp* = partitioned orthogonal modal matrix that corresponds to the rotational
degrees of freedom of grid p.
= skew-symmetric matrix formed for each grid translational degree of
freedom for each mode.
M = number of modes.
N = number of grids.
6.

To accurately capture the mode shapes when supplying SPOINT/QSET

combinations, the number of SPOINTS (ns) should be at least ns=n+(6+p),
assuming that residual flexibility is on. In the above equation for ns, the number

20

MBDEXPORT
Multi-Body Dynamics Export
of modes (n) is specified on the EIGR (METHOD=LAN) or EIGRL Bulk Data
entries; the number of load cases is p. In general, you cannot have too many
SPOINTs, as excess ones are truncated with no performance penalty.
7.

For FLEXBODY=YES runs, residual vectors for the component should always be
calculated as they result in a more accurate representation of the component
shapes at little additional cost.

8.

OMIT or OMIT1 Bulk Data entries are not supported.

9.

Lumped mass formulation (default) is required. Either leave

PARAM,COUPMASS out of the input file or supply PARAM,COUPMASS,-1
(default) to ensure lumped mass.

10. P-elements are not allowed because they always use a coupled mass formulation.
Likewise, the MFLUID fluid structure interface is not allowed because the
virtual mass matrix it generates is not diagonal.
11. PARAM,WTMASS,value with a value other than 1.0 may be used with an NX
Nastran run generating an MNF. It must have consistent units with regard
to the DTI,UNITS Bulk Data entry. Before generating the MNF, NX Nastran
will appropriately scale the WTMASS from the physical mass matrix and mode
shapes.
12. There is a distinction between how an MBDEXPORT ADAMS FLEXBODY=YES
run handles element-specific loads (such as a PLOAD4 entry) versus those
that are grid-specific (such as a FORCE entry), especially when superelements
are used. The superelement sees the total element-specific applied load. For
grid-specific loads, the loads attached to an external grid will move downstream
with the grid. That is to say, it is part of the boundary and not part of the
superelement. This distinction applies to a superelement run and not to a
residual-only or parts superelement run.
13. The loads specified in NX Nastran generally fall into two categories: non-follower
or fixed direction loads (non-circulatory) and follower loads (circulatory). The
follower loads are nonconservative in nature. Examples of fixed direction loads
are the FORCE entry or a PLOAD4 entry when its direction is specified via
direction cosines. Examples of follower loads are the FORCE1 entry or the
PLOAD4 entry when used to apply a normal pressure. By default in NX
Nastran, the follower loads are always active in SOL 103 and will result in
follower stiffness being added to the differential stiffness and elastic stiffness
of the structure. In a run with MBDEXPORT ADAMS FLEXBODY=YES and
superelements, if the follower force is associated with a grid description (such as
a FORCE1) and the grid is external to the superelement, the follower load will
move downstream with the grid. Thus, the downstream follower contribution
to the components stiffness will be lost, which could yield poor results. This

MBDEXPORT

21

Multi-Body Dynamics Export

caution only applies to a superelement run and not to a residual-only or a part
superelement run.
14. OUTGSTRS and OUTGSTRN entries require the use of standard NX Nastran
STRESS= or STRAIN= used in conjunction with GPSTRESS= or GPSTRAIN=
commands to produce grid point stress or strain. GPSTRESS(PLOT)= or
GPSTRAIN(PLOT)= will suppress grid stress or strain print to the NX Nastran
.f06 file.
15. To reduce the FE mesh detail for dynamic simulations, PSETID (on the
MBDEXPORT Case Control command) defined with a SET entry (i.e. setid) is
used to define a set of PLOTELs or other elements used to select grids to display
the components in ADAMS. This option can significantly reduce the size of the
MNF without compromising accuracy in the ADAMS simulation providing that
the mass invariant computation is requested. With superelement analysis, for
any of these elements that lie entirely on the superelement boundary (all of the
elements grids attached only to a-set or exterior grids), a SEELT Bulk Data
entry must be specified to keep that display element with the superelement
component. This can also be accomplished using PARAM, AUTOSEEL,YES. The
SEELT entry is not required with parts superelements, as boundary elements
stay with their component.
If the SET entry points to an existing set from the OUTPUT(PLOT) section, this
single set is used explicitly to define elements used to select grids to display the
component in ADAMS. If PSETID does not find the set ID in OUTPUT(PLOT), it
will search sets in the case control for a matching set ID. This matching set ID
list then represents a list of OUTPUT(PLOT) defined elements sets, the union of
which will be used to define a set of PLOTELs or other elements used to select
grids to display the component in ADAMS. If the user wishes to select all of the
sets in the OUTPUT(PLOT) section, then use PSETID=ALL.
The following element types are not supported for writing to an MNF, nor are
they supported as a type entry in a set definition in OUTPUT(PLOT): CAABSF,
CAEROi, CDUMi, CHACAB, CHACBR, CHBDYx, CDAMP3, CDAMP4,
CELAS3, CELAS4, CFLUIDi, CMASS3, CMASS4, CRAC2D, CRAC3D,
CTRMEM, CTWIST, CWEDGE, CWELD, and GENEL.
PSETID can also point to a sketch file using PSETID= sktunit, where sktunit
references an ASSIGN statement of the form:
ASSIGN SKT=sketch_file.dat,UNIT=sktunit.

The grids defined for the elements faces in the sketch file, along with all external
(i.e. boundary) grids for the superelements, will be the only grids (and their
associated data) written to the MNF.
The format of the sketch file, which describes the mesh as a collection of faces,
must be as follows:

22

MBDEXPORT
Multi-Body Dynamics Export
face_count
face_1_node_count face_1_nodeid_1 face_1_nodeid_2 ...
face_2_node_count face_2_nodeid_1 face_2_nodeid_2 ...
<etc>

Faces must have a node count of at least two. For example, a mesh comprised of
a single brick element might be described as follows:
6
4
4
4
4
4
4

1000
1007
1000
1001
1002
1003

1001
1006
1004
1005
1006
1007

1002
1005
1005
1006
1007
1004

1003
1004
1001
1002
1003
1000

Alternatively, the mesh might be described as a stick figure using a collection of

lines (two node faces), as shown below:
8
2
2
2
2
2
2
2
2

101
102
103
104
105
106
107
108

102
103
104
105
106
107
108
109

16. Typical NX Nastran data entry requirements are described below.

Typical Parameters:

PARAM,RESVEC,character_value controls calculation of residual vector

modes.

PARAM,GRDPNT, value - mass invariants 1I, 2I, and 7I will be computed

using results of NX Nastran grid point weight generator execution in the
basic coordinate system.

Typical Case Control:

MBDEXPORT ADAMS FLEXBODY=YES is required for MNF generation.

METHOD=n is required before or in the first subcase for modal solutions.

SUPORT1=seid is necessary to select a static support set for a residual

only linear preload run.

MBDEXPORT

23

Multi-Body Dynamics Export

SUPER=n,SEALL=n is useful with multiple superelement models to select

an individual superelement as a flexible body. Cannot be used with a linear
STATSUB(PRELOAD) run.

OUTPUT(PLOT) is necessary to define elements used to select grids to

display the component in ADAMS when PSETID=ALL or setid.
SET n=list of elements (including PLOTELs) is used to select grids to
display the component.

OUTPUT(POST) is necessary to define volume and surface for grid stress

or strain shapes.
SET n=list is a list of elements for surface definition for grid stress or strain
shapes.
Stress and strain data in the MNF is limited to the six components (i.e. 3
normal and 3 shear) for a grid point for a given mode.
SURFACE n SET n NORMAL z3 is used to define a surface for writing stress
and strain data. Only one FIBER selection is allowed for each SURFACE,
thus the use of the FIBRE ALL keyword on the SURFACE case control
command will write stresses to the MNF at the Z1 fiber location only.
Since the FIBRE keyword only applies to stresses, strain data will always be
written to the MNF at the MID location.
Stress and strain data at grid points can only be written to the MNF for
surface and volume type elements (e.g. CQUAD and CHEXA).
VOLUME n SET n is a volume definition.
The default SYSTEM BASIC is required with SURFACE or VOLUME.

STRESS(PLOT) is necessary for stress shapes.

STRAIN(PLOT) is necessary for strain shapes.

GPSTRESS(PLOT) is necessary for grid point stress shapes to be included

in the MNF.

GPSTRAIN(PLOT) is necessary for grid point strain shapes to be included

in the MNF.
Typical Bulk Data:

DTI,UNITS,1,MASS,FORCE,LENGTH,TIME is required for MNF

generation. For input files containing superelements, this command must
reside in the main bulk data section.

24

MBDEXPORT
Multi-Body Dynamics Export

SPOINT,id_list defines and displays modal amplitude.SESET,SEID,grid_list

defines a superelement (see GRID and BEGIN BULK SUPER=). The
exterior grids will represent the attachment points along with the q-set.

SEELT,SEID,element_list reassigns superelement boundary elements to

an upstream superelement.

RELEASE,SEID,C,Gi is an optional entry that removes DOFs from an

attachment grid for which no constraint mode is desired. For example, this
allows the removal of rotational degrees of freedom from an analysis where
only translational degrees of freedom are required.

SEQSET,SEID,spoint_list defines modal amplitudes of a superelement (see

SEQSET1).

SENQSET,SEID,N defines modal amplitudes of a part superelement. It

must reside in the main Bulk Data Section.

ASET,IDi,Ci defines attachment points for a residual-only run (see ASET1).

QSET1,C,IDi defines modal amplitudes for the residual structure or modal

amplitudes for a part superelement (see QSET).

SUPORT1,SID,IDi,Ci defines the static support for a preload condition

with a residual-only run. This entry is case control selectable. Do not use
SUPORT.

PLOTEL,EID,Gi can be used, along with existing model elements, to define

elements used to select grids to display the components in ADAMS.

EIGR,SID,METHOD, obtains real eigenvalue extraction (see EIGRL).

17. The RECVROP2=YES option is used when you would like results recovery (using
the MBDRECVR case control entry) from an ADAMS/Flex analysis. This option
requires the following assignment command:
ASSIGN OUTPUT2=name.out STATUS=UNKNOWN UNIT=20
FORM=UNFORM
be inserted into the file management section of the NX Nastran input file. It
will cause an OP2 file with a .out extension to be generated, which then can be
used as input into an NX Nastran SOL 103 run using the MBDRECVR case
control capability to perform results recovery from an ADAMS/Flex analysis.
FLEXBODY=YES is required with its use.
The data blocks output are:

MBDEXPORT

25

Multi-Body Dynamics Export

MGGEW - physical mass external sort with weight mass removed
MAAEW - modal mass
KAAE - modal stiffness
CMODEXT - component modes.
This capability is limited to no more than one superelement per NX Nastran
model. Residual-only analyses are supported.
18. Setting CHECK=YES (which is only available when RECVROP2=YES) is not
recommended for models of realistic size due to the amount of data that will be
written to the f06 file.
19. The MBDEXPORT data routines use the environment variable TMPDIR for
temporary storage during the processing of mode shape data. As a result,
TMPDIR must be defined when using MBDEXPORT. TMPDIR should equate
to a directory string for temporary disk storage, preferably one with a large
amount of free space.
20. If any damping is defined in the model, an equivalent modal viscous damping
will be determined for each mode and written to the MNF. This equivalent modal
viscous damping is defined as:

= yTBey

where d = equivalent modal viscous damping

y = mode shapes
Be = equivalent viscous damping defined by:

G, W3, and W4 are parameters described in the Parameter Descriptions section

of this guide.
OP4 Describers:
Describer
unit

Meaning
The OP4 file is written to the specified logical unit number.
The logical unit number must match the unit number on an
ASSIGN statement.

26

MBDEXPORT
Multi-Body Dynamics Export

Describer
FLEXBODY

NO

YES
FLEXONLY

YES
NO

RECVROP2

NO
YES
CHECK

Meaning
Requests the generation and writing of standard or state-space
matrices to an OP4 file.
NX Nastran solution without standard or state-space matrix
generation. (default)
Standard or state-space matrix generation requested.
Determines if DMAP solution runs or not after standard or
state-space matrix generation is complete.
Only standard or state-space matrix generation occurs. (default)
Standard or state-space matrix generation occurs along with
the standard DMAP solution.
Requests that the FLEXBODY run output an NX Nastran OP2
file for use in post-processing of controls results. (See Remark 5)
OP2 file will not be generated. (default)
OP2 file will be generated.
Requests debug output be written to the f06 file when
RECVROP2=YES. (See Remark 6).

NO
YES

No debug output will be written. (default)

Debug output will be written.

OP4 Remarks:
1.

The generation of standard or state-space matrices and the writing of them to an

OP4 file via OUTPUT4, which is applicable in a non-restart SOL 103 analysis
only, is initiated by MBDEXPORT OP4=unit STANDARD FLEXBODY=YES,
or MBDEXPORT OP4=unit STATESPACE FLEXBODY=YES (other describers
are optional) and the inclusion of the ASSIGN file management statement. This
ASSIGN statement must be of the form:
ASSIGN OUTPUT4=filename,UNIT=n,etc.
where n matches the value for unit on the MBDEXPORT OP4=unit case control
command.

MBDEXPORT

27

Multi-Body Dynamics Export

2.

The parameters LFREQ/HFREQ or LMODES can be used to control which

modes are used to derive the standard or state-space matrices.

3.

For state-space matrices, user-defined set U7 is used for input DOF. User-defined
set U8 is used for output DOF. Refer to the USET and USET1 bulk data entries.

4.

For standard matrices, user-defined set U8 is used for output DOF. The mode
shape output will be reduced to the DOF defined in DOF set U8. If DOF set U8
is not defined, the mode shape data for all DOF will be written. Refer to the
USET and USET1 bulk data entries.

5.

The RECVROP2=YES option is used when you would like results recovery (using
the MBDRECVR case control entry) from a system analysis. This option requires
the following assignment command:
ASSIGN OUTPUT2=name.out STATUS=UNKNOWN UNIT=20
FORM=UNFORM
be inserted into the file management section of the NX Nastran input file. It will
cause an OP2 file with a .out extension to be generated, which can then be used
as an input into an NX Nastran SOL 103 run using the MBDRECVR case control
command. FLEXBODY=YES is required when specifying RECVROP2=YES.
The data blocks output are:
MGGEW physical mass external sort with weight mass removed
MAAEW modal mass
KAAE modal stiffness
CMODEXT component modes
This capability is limited to one superelement per NX Nastran model.
Residual-only analyses are supported.

6.

Setting CHECK=YES (which is only available when RECVROP2=YES) is not

recommended for models of realistic size due to the amount of data that will be
written to the f06 file.

MATLAB Describers:
Describer
FLEXBODY

Meaning
Requests the generation and writing of standard or state-space
matrices to a MATLAB script file.

28

MBDEXPORT
Multi-Body Dynamics Export

Describer
NO

YES
FLEXONLY

YES
NO

RECVROP2

NO
YES
CHECK

Meaning
NX Nastran solution without standard or state-space matrix
generation. (default)
Standard or state-space matrix generation requested.
Determines if DMAP solution runs or not after standard or
state-space matrix generation is complete.
Only standard or state-space matrix generation occurs. (default)
Standard or state-space matrix generation occurs along with
the standard DMAP solution.
Requests that the FLEXBODY run output an NX Nastran OP2
file for use in post-processing of controls results. (See Remark 7)
OP2 file will not be generated. (default)
OP2 file will be generated.
Requests debug output be written to the f06 file when
RECVROP2=YES. (See Remark 8).

NO
YES

No debug output will be written. (default)

Debug output will be written.

MATLAB Remarks:
1.

The generation of standard or state-space matrices and the writing of them to

a MATLAB script file, which is applicable in a non-restart SOL 103 analysis
only, is initiated by MBDEXPORT MATLAB STANDARD FLEXBODY=YES, or
MBDEXPORT MATLAB STATESPACE FLEXBODY=YES (other describers are
optional). The MATLAB script files are named jid_seid.m where seid is the
integer number of the superelement (0 for residual-only run). The location of the
MATLAB script files is the same directory as the jid.f06 file.

2.

The parameters LFREQ/HFREQ or LMODES can be used to control which

modes are used to derive the standard or state-space matrices.

3.

For state-space matrices, user-defined set U7 is used for input DOF. User-defined
set U8 is used for output DOF. Refer to the USET and USET1 bulk data entries.

MBDEXPORT

29

Multi-Body Dynamics Export

4.

For standard matrices, user-defined set U8 is used for output DOF. The mode
shape output will be reduced to the DOF defined in DOF set U8. If DOF set U8
is not defined, the mode shape data for all DOF will be written. Refer to the
USET and USET1 bulk data entries.

5.

For the state-space option, the MATLAB script file contains the [A], [B], and [C]
state-space matrices. They are defined as AMAT, BMAT, and CMAT, respectively.
The input and output DOF are defined as U7DOF and U8DOF, respectively with
the first column being the grid ID and the second column being the direction
code (1 through 6).

6.

For the standard option, the MATLAB script file contains the modal mass,
equivalent modal viscous damping, modal stiffness, mode shapes, and modal
forces defined as MMASS, MDAMP, MSTIF, MSHAP, and MFORC, respectively.
The physical DOF corresponding one-to-one with the rows of MSHAP are defined
as U8DOF. The first column contains the grid ID and the second column contains
the direction code (1 through 6).

7.

The RECVROP2=YES option is used when you would like results recovery (using
the MBDRECVR case control entry) from a system analysis. This option requires
the following assignment command:
ASSIGN OUTPUT2=name.out STATUS=UNKNOWN UNIT=20
FORM=UNFORM
be inserted into the file management section of the NX Nastran input file. It will
cause an OP2 file with a .out extension to be generated, which can then be used
as an input into an NX Nastran SOL 103 run using the MBDRECVR case control
command. FLEXBODY=YES is required when specifying RECVROP2=YES.
The data blocks output are:
MGGEW physical mass external sort with weight mass removed
MAAEW modal mass
KAAE modal stiffness
CMODEXT component modes
This capability is limited to one superelement per NX Nastran model.
Residual-only analyses are supported.

8.

Setting CHECK=YES (which is only available when RECVROP2=YES) is not

recommended for models of realistic size due to the amount of data that will be
written to the f06 file.

30

Structural damping

Structural damping
In order to include the effects of structural damping in a modal transient analysis
(SOL 112), you must convert structural damping to viscous damping.
Prior to NX Nastran 7.1, there was only one method available to convert structural
damping to viscous damping for a modal transient analysis. When using this
method, you must specify either one or two frequency factors using the W3 and W4
parameters. The software uses these frequency factors to convert the structural
damping to viscous damping. Typically, you specify the frequency factors to
account for the dominant frequency at which the damping is active. For more
information regarding the W3 and W4 parameters, see the Basic Dynamic Analysis
Users Guide.
Now a second method is available that you can use either independently or in
conjunction with the original method. When you use it independently, you do
not need to specify any frequency factors to use in the conversion. The software
automatically uses the solved modal frequencies in the conversion. As a result, the
conversion is valid over a much wider range of frequencies.
If you use the original structural-to-viscous conversion method, you must specify
one or both of the W3 and W4 parameters. With these parameters specified, the
structural damping is converted to viscous damping using:

where
= assembled stiffness matrix.
= assembled elemental damping matrix.
= overall structural damping coefficient. (See the G parameter.)
= user-defined conversion frequency for overall structural damping. (See
the W3 parameter.)
= user-defined conversion frequency for elemental structural damping.
(See the W4 parameter.)
Then, the modal viscous damping matrix is calculated using:

where
= modal viscous damping matrix.

Structural damping

31

= mode shape matrix.

= assembled viscous damping matrix.
= viscous damping matrix from DMIG input.

= converted structural damping matrix.

Beginning with NX Nastran 7.1, a new parameter named WMODAL is available
that allows you to specify that structural damping be converted to viscous damping
using:

where wi are the modal frequencies in rad/sec.

For rigid body modes, the software partitions the diagonal entries,
, out of the
calculation. The FZERO parameter is used to identify rigid body modes. (See the
FZERO parameter.) Because all the modal frequencies of flexible body modes are
used in the conversion, the resulting viscous damping is representative over a
much wider range of frequencies.
Because the WMODAL parameter can be used in conjunction with the W3 and W4
parameters, you now have three options for converting structural damping to
viscous damping.

If you specify one or both of the W3 and W4 parameters, and either omit the
WMODAL parameter from the input file or specify WMODAL = NO, the
structural-to-viscous damping conversion is calculated using:

Therefore, the modal viscous damping matrix is calculated using:

This is identical to the method available prior to NX Nastran 7.1.

32

Structural damping

If you specify WMODAL = YES, and either omit the W3 and W4 parameters
from the input file or accept their default value of 0.0, the structural-to-viscous
damping conversion is calculated using:

Therefore, the modal viscous damping matrix is calculated using:

You do not need to specify any frequency factors to use in the conversion if you
use this option.

If you specify WMODAL = YES and specify one or both of the W3 and W4
parameters, the contributions from both structural-to-viscous damping
conversion methods are summed and the modal viscous damping matrix is
calculated using:

An example of a complete input file containing the WMODAL parameter is

wmod_rbm.dat. It can be found in install_dir/nxn7p1/nast/tpl.

WMODAL parameter
The WMODAL parameter is only applicable for SOL 112 and can be placed in
either the bulk data or case control sections of the input file.

DDAM
WMODAL

33

Default = NO
WMODAL specifies a structural-to-viscous damping conversion
method that uses the solved modal frequencies as conversion
factors. WMODAL is only applicable to modal transient analysis
(SOL 112). When one or both of the W3 and W4 parameters
are specified (see the W3, W4, W3FL, W4FL parameter) in
conjunction with WMODAL, the structural-to-viscous damping
conversion is calculated using:

where wi are the modal frequencies in rad/sec.

, are partitioned
For rigid body modes, the diagonal entries,
out of the calculation. The FZERO parameter is used to identify
rigid body modes (see the FZERO parameter).

DDAM
NX Nastran 7.1 contains four enhancements to DDAM analysis.

Results from a DDAM analysis can now be written to an .op2 file.

Any consistent set of units can now be used in the NX Nastran model for a
DDAM analysis.

The formula for reference acceleration, Ao, has now been generalized to
support all DDAM specifications including NRL-1396.

The built-in weighting factors used to compute reference velocity and reference
acceleration in the default user option are now set to values specified in
NRL-1396.

DDAM results output

Beginning with NX Nastran 7.1, you can write results from standard case control
requests to an .op2 file. Prior to NX Nastran 7.1, you could write the results from

34

DDAM
standard case control requests only to an .f06 file. The binary formatting of .op2
files is ideal for accessing the results with standard post processors. To write
results to an .op2 file, you should include PARAM,POST,n<0 in either the case
control or bulk entry sections of the input file.

DDAM units
Beginning with NX Nastran 7.1, you can use any consistent set of units in the NX
Nastran model for a DDAM analysis. Prior to NX Nastran 7.1, you could run a
DDAM analysis only if the model unit for force was lbf and the model unit for
acceleration was in/sec2.
In order to change the units from lbf and in/sec2, you specify a force conversion
factor cf and an acceleration conversion factor ca. The conversion factors cf and ca
are defined in the DDAM input (.inp) file as lines 10 and 11, respectively.
First Line - spectrum control - format a1,1x,a1
First Item - coefficients from external file or built-in source
T=use coefficients from external file
F=use built-in coefficients
Second item - DDAM or general spectrum run flag
T=general non-DDAM spectrum run
F=DDAM
Second Line - file name (if needed) -format a80
If 1st item on line 1 is T, name of external coefficient file
If 2nd item on line 1 is T, name of external spectrum file
If neither are T, line is not needed and should be omitted do not leave
a blank line
Third Line - location flags - format i1,1x,i1,1x,i1
First Item - surface or submarine
1=surface
2=submarine
Second Item - equipment location
1=deck
2=hull
3=shell
Third Item - coefficient type
1=elastic
2=elastic/plastic

DDAM

35

4th Line - Weight cutoff percentage mcutoff - format F8.3 (0. To 100.)
5th Line - Axis Orientation - format a1,1x,a1
First Item - F/A axis,X,Y, or Z
Second Item - vertical axis X,Y, or Z
6th Line - Input file name -format a80
7th Line - Output file name - format a80
8th Line - Verification file name - format a80
9th Line - Minimum acceleration value gmin (units of Gs) - format F8.3 (must
be >0.0)
10th Line - Force conversion factor cf (converts lbf to model force units) - format
F8.3 (must be >0.0)
11th Line - Acceleration conversion factor ca (converts in/sec2 to model acceleration
units) - format F8.3 (must be >0.0)
Note
You should always include values for lines 9, 10, and 11. If the desired
DDAM analysis units for force are lbf, enter 1.0 for line 10. If the desired
DDAM analysis units for acceleration are in/sec2, enter 1.0 for line 11. You
can verify DDAM inputs by examining the verification file specified on line
8.
The three control file formats have changed to reflect the new unit conversion
capability and are now:
Default user option:
FF
nsurf nstruc nplast
mcutoff (user-supplied value)
f/a_axis vert_axis
.f11 filename
.f13 filename
.ver filename
gmin (user-supplied value)
cf (user-supplied value)
ca (user-supplied value)

36

DDAM
User coefficient option:
TF
.dat filename
nsurf nstruc nplast
mcutoff (user-supplied value)
f/a_axis vert_axis
.f11 filename
.f13 filename
.ver filename
gmin (user-supplied value)
cf (user-supplied value)
ca (user-supplied value)
User spectrum option:
FT
.dat filename
mcutoff (user-supplied value)
f/a_axis vert_axis
.f11 filename
.f13 filename
.ver filename
gmin (user-supplied value)
cf (user-supplied value)
ca (user-supplied value)

DDAM

37

An example DDAM input (.inp) file that uses N for the model force units and
mm/sec2 for the model acceleration units is:
FF
111
75.
XZ
navs1.f11
navs1.f13
navs1.ver
6.
4.448
25.4
Note
Because the line 1 specification is F F, this example is the default option
and line 2 is not needed and is omitted from the file without leaving a blank
line.
An example DDAM input (.inp) file that uses lbf for the model force units and
ft/sec2 for the model acceleration units is:
TF
navs1.dat
111
75.
XZ
navs1.f11
navs1.f13
navs1.ver
6.
1.
0.08333
Note
Because the line 1 specification is T F, this example is the user coefficient
option and line 2 is required.

38

DDAM

DDAM reference acceleration

Beginning with NX Nastran 7.1, the formula for reference acceleration, Ao, has
been generalized to support all DDAM specifications including NRL-1396. The
reference acceleration is now calculated using:

where M is modal weight in kips and AA, AB, AC, AD, and AF are weighting
factors. The built-in weighting factors are used for the default user option. For
the user coefficient option, you must specify the weighting factors in an external
coefficient file.
You can optionally specify the alternative form of the reference acceleration
equation by setting AD = AC. By doing so, the reference acceleration equation
simplifies to:

DDAM

39

DDAM weighting factors

NAVSHOCK has built-in weighting factors that are used to calculate the reference
velocity and reference acceleration for the default user option. A default value for
the weight cutoff percentage of 80.0 is also included with the built-in weighting
factors in NAVSHOCK.
Beginning with NX Nastran 7.1, the built-in weighting factors are set to values
specified in NRL-1396. The following tables list the values specified in NRL-1396.
In both tables:

nsurf Refers to the ship type. Allowable values are SUB (submerged) and
SURF (surfaceship).

nstruc Refers to the mounting location. Allowable values are DECK, HULL,
and SHELL.

nplast Refers to elastic or elastic-plastic factors. Allowable values are

ELASTIC and ELPL.

In the following table, (1), (2), and (3) after VF and AF refer to directions:

(1) = fore/aft

(2) = athwartship

(3) = vertical

nsurf/nstruc/nplast
SURF/DECK/ELASTIC
SURF/HULL/ELASTIC

VF(1)
0.4
0.2

VF(2)
0.4
0.4

VF(3)
1.0
1.0

AF(1)
0.4
0.2

AF(2)
0.4
0.4

AF(3)
1.0
1.0

SURF/SHELL/ELASTIC
SURF/DECK/ELPL

0.1
0.2

0.2
0.2

1.0
0.5

0.1
0.4

0.2
0.4

1.0
1.0

SURF/HULL/ELPL
SUB/DECK/ELASTIC

0.1
0.8

0.2
2.0

0.5
1.0

0.2
0.8

0.4
2.0

1.0
1.0

SUB/HULL/ELASTIC

0.4

1.0

1.0

0.4

1.0

1.0

SUB/SHELL/ELASTIC

0.08

0.2

1.0

0.08

0.2

1.0

SUB/DECK/ELPL

0.4

1.0

0.5

0.8

2.0

1.0

SUB/HULL/ELPL

0.2

0.5

0.5

0.4

1.0

1.0

40

DDAM
nsurf/nstruc/nplast
SURF/DECK/ELASTIC

VA
30.0

VB
12.0

VC
6.0

AA
10.0

AB
37.5

AC
12.0

AD
6.0

SURF/HULL/ELASTIC
SURF/SHELL/ELASTIC

60.0
120.0

12.0
12.0

6.0
6.0

20.0
40.0

37.5
37.5

12.0
12.0

6.0
6.0

SURF/DECK/ELPL
SURF/HULL/ELPL

30.0
60.0

12.0
12.0

6.0
6.0

10.0
20.0

37.5
37.5

12.0
12.0

6.0
6.0

SUB/DECK/ELASTIC

10.0

480.0

100.0

5.2

480.0

20.0

20.0

SUB/HULL/ELASTIC
SUB/SHELL/ELASTIC

20.0
100.0

480.0
480.0

100.0
100.0

10.4
52.0

480.0
480.0

20.0
20.0

20.0
20.0

SUB/DECK/ELPL
SUB/HULL/ELPL

10.0
20.0

480.0
480.0

100.0
100.0

5.2
10.4

480.0
480.0

20.0
20.0

20.0
20.0

For information on formatting an external coefficient file, see DDAM Process

Automation in the Dynamic Solution Techniques chapter of the Advanced
Dynamic Analysis Users Guide.

DDAM units mathematical basis

The conversion factors cf and ca specified in the DDAM input (.inp) file are used to
convert the modal effective mass Meff calculated by NX Nastran to modal weight
M in kips using:

The modal weight is subsequently used by NAVSHOCK to calculate the reference

velocity and reference acceleration. The reference velocity is calculated using:

where VA, VB, VC, and VF are built-in or user-specified weighting factors. The
reference acceleration is calculated using:

where AA, AB, AC, AD, and AF are built-in or user-specified weighting factors.
The acceleration loading calculated by NAVSHOCK for use in the response
simulation requires conversion of the acceleration to the NX Nastran model units.
This conversion is accomplished using:

DDAM

41

where w is the modal frequency in rad/sec. For clarity, this equation can also be
written as:

DDAM documentation updates

The following updates are applicable to the DDAM Process Automation section
of the Dynamic Solution Techniques chapter of the NX Nastran 7 Advanced
Dynamic Analysis Users Guide.
Input file unit assignment
The unit to assign the DDAM input file is correct in the example, but is incorrect in
the text. In both instances, you must assign unit 21 to the INPUT4 file that stores
the input control options for the FORTRAN program. An example of an ASSIGN
statement assigning unit 21 to the ddam.inp file is:
ASSIGN INPUTT4=ddam.inp, UNIT=21, FORM=FORMATTED

User coefficient option

When using the user coefficient option for the DDAM input (.inp) file, the
documentation states that you must include a complete set of weighting factors in
the DDAM coefficient file. In actuality, if you provide a blank DDAM coefficient
file, the software will use the built-in default values in NAVSHOCK.
Note
As a best practice, you should specify a complete set of weighting factors
in the DDAM coefficient file when using the user coefficient option for the
DDAM input (.inp) file.

Weight cutoff percentage

You can specify a weight cutoff percentage in either the control file or the coefficient
file. A default value for the weight cutoff percentage of 80.0 is included with the
built-in weighting factors in NAVSHOCK. The weight cutoff percentage value that
is used by the software in the DDAM calculations depends on the weight cutoff
percentage value specified in the control file.

42

Modal effective mass

If the weight cutoff percentage value specified in the control file is greater than
1.0 x 103, it is used by the software in the DDAM calculations.

If the weight cutoff percentage value specified in the control file is less than
or equal to 1.0 x 103 and a value for the weight cutoff percentage is specified
in the coefficient file, the value specified in the coefficient file is used by the
software in the DDAM calculations.

If the weight cutoff percentage value specified in the control file is less than
or equal to 1.0 x 103 and a coefficient file either does not exist or does not
include a value for the weight cutoff percentage, the default value of 80.0
included with the built-in weighting factors in NAVSHOCK is used by the
software in the DDAM calculations.
Note
As a best practice, you should specify the weight cutoff percentage in the
control file.

Optionally defined shock spectra

Information on how to define a shock spectra is included in the documentation, but
details on how to format the DATATYP entry are omitted. You should be aware
that for the DATATYP entry:

Each field has eight spaces.

The fields cannot be comma separated.

Entries in each field must be left justified.

Modal effective mass

The MEFFMASS case control command requests modal effective mass,
participation factors, and modal effective mass fractions in a SOL 103, normal
modes analysis.
In addition to these requests, the new THRESH describer has been created to
optionally limit mode output by the effective mass fractions. Modes which have
an effective mass fraction greater than the value of THRESH in at least one
translational or rotational direction, are output to the .f06 and .op2 files.
For example, if you define THRESH=0.1 on the MEFFMASS case control command:
MEFFMASS(PRINT,PLOT,FRACSUM,THRESH=0.1) = YES

Modal effective mass

43

only modes which have a modal effective mass fraction greater than 0.1 in at least
one direction are written to the .op2 file.
The highlighted modal effective mass fraction values are greater than 0.1 in the
example below. The result is that only modes 1, 2, 3, and 10 are output to the
.f06 and .op2 files.

The .f06 file includes a statement similar to the following to indicate the modes
that are written to the .f06 and .op2 files:
MODES THAT EXCEED THE EFFECTIVE MASS THRESHOLD AND STORED ARE:
1
2
3
10

Note that THRESH does not limit mode storage for consecutive dynamic response
solutions (SOL 111 or 112). You can use the MODSEL case control command to
select/deselect modes in these solutions.
See the updated MEFFMASS case control command.

44

MEFFMASS

Modal effective mass output request. Optionally limits

mode output by effective mass.

MEFFMASS

Modal effective mass output request. Optionally limits mode

output by effective mass.
Requests the output of the modal effective mass, participation factors, and modal
effective mass fractions in normal modes analysis. Optionally can limit mode output
by effective mass fraction.
Format:

Examples:
MEFFMASS
MEFFMASS(GRID=12, SUMMARY, PARTFAC)
MEFFMASS (PLOT, ALL, THRESH=0.001)=YES

Describers:
Describer

Meaning

PRINT

Writes output to the print file. (Default)

PUNCH

Writes output to the punch file.

PLOT

Writes output to the output2 file.

GRID

Reference grid point for the calculation of the Rigid Body Mass
Matrix. The default is the origin of the basic coordinate system.

SUMMARY

Requests calculation of the Total Effective Mass Fraction,

Modal Effective Mass Matrix, and the Rigid Body Mass Matrix.
(Default)

PARTFAC

Requests calculation of Modal Participation Factors.

MEFFM

Requests calculation of the Modal Effective Mass in units of

mass.

MEFFW

Requests calculation of the Modal Effective Mass in units of

weight.

FRACSUM

Requests calculation of the Modal Effective Mass Fraction.

MEFFMASS

45

Modal effective mass output request. Optionally limits mode output by effective mass.
Describer

Meaning

Threshold value of effective mass fraction for mode output.

(Real; 0.0 < THRESH < 1.0; Default = all modes are stored).
See Remark 8.

Remarks:
1.

The SUMMARY describer produces three outputs:

Modal Effective Mass Matrix [T][m][] where
=

Modal Participation Factors

[m]-1[f]T[Maa][Dar]

Generalized mass matrix

Eigenvectors

Maa =

Mass matrix reduced to the a-set (g-set for superelements)

Dar =

Rigid body transformation matrix with respect to the a-set

A-set Rigid Body Mass Matrix: [DTar][Maa][Dar]. For a superelement this is

computed at the g-set.
Total Effective Mass Fraction: i.e., diagonal elements of the Modal Effective
Mass Matrix divided by the Rigid Body Mass Matrix.
2.

The PARTFAC describer outputs the Modal Participation Factors table: 

3.

The MEFFM describer outputs the Modal Effective Mass table: 2, the term-wise
square of the Modal Participation Factors table.

4.

The MEFFW describer outputs the Modal Effective Weight table; i.e., the Modal
Effective mass multiplied by user PARAMeter WTMASS.

5.

The FRACSUM describer outputs the Modal Effective Mass Fraction table; i.e.,
the Generalized Mass Matrix (diagonal term) multiplied by the Modal Effective
Mass and then divided by the Rigid Body Mass Matrix (diagonal term).

6.

For superelements the MEFFMASS command uses the residual structure

eigenvalues and eigenvectors, by default. If however, PARAM, FIXEDB, -1 is
specified then MEFFMASS command uses the component mode eigenvalues
and eigenvectors.

46

Selection of fluid modes

7.

Effective mass is computed in the basic coordinate system.

8.

Modes which have an effective mass fraction greater than the value of THRESH
in at least one translational or rotational direction are output in the .f06 and .op2
files. THRESH does not limit modes for consecutive dynamic response solutions
(SOL 111 or 112). Use the MODSEL case control command to select/deselect
modes in these solutions.

Selection of fluid modes

Prior to NX Nastran 7.1, the MODSEL case control command could only be used to
select a subset of structural modes for use in a response solution. For acoustic or
coupled acoustic/structural models, you could not exclude any of the fluid modes
from the response solution.
The functionality of the MODSEL case control command has been expanded to
include fluid modes. Now you can use the MODSEL case control command to select
either structural or fluid modes to use in a response solution. If you include a
MODSEL case control command for both structural modes and fluid modes in the
same input file, subsets of both the structural and fluid modes can be used in the
response solution. If you do not include a MODSEL case control command in the
input file, all the structural and fluid modes are used in the response solution.
The MODSEL case control command is used in conjunction with the SET case
control command to define which structural and fluid modes to include in the
response solution. An example is provided below.

Selection of fluid modes

47

MODSEL example
SOL 111
...
...
...
$ Specify that SET 12 includes the structural modes to use in the response solution
$
MODSEL(STRUCTURAL)=12
$
$ Specify that SET 110 includes the fluid modes to use in the response solution
$
MODSEL(FLUID)=110
$
$ SET 12 includes the first two structural modes
$
SET 12 = 1,2
$
$ SET 110 includes the first 10 fluid modes
$
SET 110 = 1 THRU 10
...
...
...
BEGIN BULK
...
...
...
ENDDATA

Note
MODSEL case control commands are typically located outside of subcases.
If you include a MODSEL case control command in a subcase, it is ignored
unless the modes are recalculated for the subcase.
An example of a complete input file using the MODSEL case control command is
ac1102s1.dat. It can be found in install_dir/nxn7p1/nast/tpl.
See the updated MODSEL case control command.

48

MODSEL
Selects mode numbers

MODSEL

Selects mode numbers

Used to select mode numbers to include in a modal dynamic response solution.

Format:

Examples:
MODSEL=3
MODSEL(STRUCTURAL)=4
MODSEL(FLUID)=5

Describers:
Describer

Meaning

STRUCTURAL Specifies the structural modes to include in the response

solution. (Default)
FLUID

Specifies the fluid modes to include in the response solution.

ALL

Designates that all the structural or fluid modes be used in the

response solution. (Default)

Identification number of the SET case control command

containing either structural or fluid modes. The mode numbers
included in the SET case control command are used in the
response solution. The mode numbers not included in the SET
case control command are removed from the modal space. Mode
numbers larger than the number of eigenvalues computed are
ignored. (Integer>0)

Remarks:
1.

All structural and fluid modes are used in the response solution if a MODSEL
entry is not included in the input file.

2.

Multiple MODSEL entries can be included in a single input file.

3.

The use of MODSEL in a subcase is only effective if the modes are recalculated
for the subcase.

Acoustic/fluid-structure coupling matrices

49

Acoustic/fluid-structure coupling matrices

In a coupled acoustic/fluid-structure analysis, the coupling between the fluid and
structure for the stiffness and mass is computed by default. Prior to NX Nastran
7.1, you had to either use the computed coupling matrices or ignore the coupling by
preventing the coupling matrices from being computed.
Beginning with NX Nastran 7.1, you can also do the following:

Select direct input acoustic/fluid-structure coupling matrices to use in the

analysis. These matrices can be used to represent the acoustic/fluid-structure
coupling either independently or in conjunction with the computed
acoustic/fluid-structure coupling matrices.

Scale the direct input and/or the computed acoustic/fluid-structure coupling

matrices.

You control the expanded functionality using a new case control command named
A2GG, an enhanced ASCOUP parameter, and new parameters named CA1 and
CA2.
When you specify both ASCOUP and A2GG, the software either adds the direct
input acoustic/fluid-structure coupling matrices to the computed coupling matrix
or the computed coupling matrix is ignored altogether in favor of direct input
matrices. In either case, you can scale the coupling matrices in one of these ways:

Specify one or both of the CA1 and CA2 parameters.

Specify in-line scale factors using the A2GG case control command.

Specify both in-line scale factors using the A2GG case control command and
one or both of the CA1 and CA2 parameters.

If PARAM,ASCOUP,YES and A2GG are both specified, the total

acoustic/fluid-structure coupling matrix is:

where [ Axjj ] is the computed acoustic/fluid-structure coupling matrix and [ A2jj ] is

the direct input acoustic/fluid-structure coupling matrix specified using A2GG.
If PARAM,ASCOUP,NO and A2GG are both specified, the computed coupling
matrix is ignored and the total acoustic/fluid coupling matrix is:

where [ A2jj ] is the direct input acoustic/fluid-structure coupling matrix specified

using A2GG.

50

Acoustic/fluid-structure coupling matrices

An example of a complete input file containing the A2GG case control command,
the ASCOUP parameter, and the CA2 parameter is ac11201a.dat. It can be found
in install_dir/nxn7p1/nast/tpl.
See the new A2GG case control command.

A2GG

51

Direct Input Acoustic/Fluid-Structure Matrix Selection

A2GG

Direct Input Acoustic/Fluid-Structure Matrix Selection

Selects direct input acoustic/fluid-structure coupling matrix or matrices.

Format:
A2GG=name
Examples:
A2GG=ADMIG
A2GG=ADMIG1, ADMIG2, ADMIG3
A2GG=1.25*ADMIG1, 1.0*ADMIG2, 0.75*ADMIG3
SET 100=A1, A2
A2GG=100

Describers:
Describer

Meaning

name

Name of direct input acoustic/fluid-structure coupling matrix

[ A2gg ] defined using DMIG bulk entries. (Character) Scale
factors may be included (see Remarks 4 and 5).

Remarks:
1.

DMIG matrices are not used unless selected using A2GG.

2.

If PARAM,ASCOUP,YES, the direct input acoustic/fluid-structure

coupling matrix selected using A2GG is added to the computed
acoustic/fluid-structure coupling matrix. If PARAM,ASCOUP,NO, the direct
input acoustic/fluid-structure coupling matrix selected using A2GG replaces the
computed acoustic/fluid-structure coupling matrix.

3.

The matrix must be square and field 4 of the DMIG bulk entry must contain
the integer 1. When filling out the DMIG bulk entries, the GJ column index
corresponds to fluid points, CJ is zero, the Gi row index corresponds to structural
points, Ci corresponds to DOF, and Ai are the area values.

4.

The associated DMIG matrices can be scaled using either in-line scale factors
entered on A2GG (for example, A2GG=1.25*ADMIG1), or the parameter CA2
(for example, PARAM,CA2,1.25), or both. For information regarding the CA2
parameter, see Parameter Descriptions.

5.

Multiple matrices separated by a comma or a blank are additive. When multiple

matrices and in-line scale factors are used together, each matrix name in the list
must include a scale factor. 1.0 should be entered for matrices in the list that are

52

A2GG
Direct Input Acoustic/Fluid-Structure Matrix Selection
not scaled. For example, if A2GG=1.25*ADMIG1,1.0*ADMIG2,0.75*ADMIG3 is
specified, the result is A2GG=1.25*ADMIG1 + ADMIG2 + 0.75*ADMIG3.
Specifying the CA2 parameter scales all the A2GG. For example, if both
PARAM,CA2,1.30 and A2GG=1.25*ADMIG1,1.0*ADMIG2,0.75*ADMIG3 are
specified, the result is A2GG=1.30(1.25*ADMIG1 + ADMIG2 + 0.75*ADMIG3).
6.

A2GG is supported in dynamic solutions with acoustic/fluid-structure coupling.

7.

Only one A2GG case control command should be used in an input file and it
should appear above any subcases.

ASCOUP parameter
The ASCOUP parameter is applicable to all solutions except SOL 601/701 and
must be placed in the bulk entry section of the input file.
ASCOUP

Default = YES
In coupled fluid-structure analysis, if PARAM,ASCOUP,YES is
specified in or omitted from the input file, and the A2GG case
control command is also omitted from the input file, coupling for
the stiffness and mass is computed. If PARAM,ASCOUP,NO is
specified and A2GG is omitted, the coupling is not computed.
When ASCOUP and A2GG are both specified, direct input
acoustic/fluid-structure coupling matrices can be added to the
computed coupling matrix or the computed coupling matrix can
be ignored altogether in favor of direct input matrices. In either
case, the coupling matrices can be scaled by:

Specifying one or both of the CA1 and CA2 parameters.

Specifying in-line scale factors using the A2GG case control

command.

Specifying both in-line scale factors using the A2GG case

control command and one or both of the CA1 and CA2
parameters.

If PARAM,ASCOUP,YES and A2GG are both specified, the total

acoustic/fluid-structure coupling matrix is:

where [ Axjj ] is the computed acoustic/fluid-structure coupling

matrix and [ A2jj ] is the direct input acoustic/fluid-structure
coupling matrix specified using A2GG.

Defining panels

53

If PARAM,ASCOUP,NO and A2GG are both specified, the

computed coupling matrix is ignored and the total acoustic/fluid
coupling matrix is:

where [ A2jj ] is the direct input acoustic/fluid-structure coupling

matrix specified using A2GG.

CA1, CA2 parameters

The CA1, CA2 parameter is applicable to all solutions except SOL 601/701 and can
be placed in either the bulk entry or case control sections of the input file.
CA1, CA2

Default = (1.0, 0.0)

CA1 and CA2 specify factors for scaling the total
acoustic/fluid-structure coupling matrix. The total
acoustic/fluid-structure coupling matrix is:

where [ Axjj ] is the computed acoustic/fluid-structure coupling

matrix and [ A2jj ] is the direct input acoustic/fluid-structure
coupling matrix specified using the A2GG case control command.
CA1 and CA2 are only effective if A2GG is specified in the case
control section.

Defining panels
Panels are collections of structural grid points, and are used to evaluate the
transfer path of structural vibration into dynamic acoustic pressure. Panels are
defined using the PANEL bulk entry. Prior to NX Nastran 7.1, PANEL bulk entries
referenced only SET1 bulk entries. SET1 bulk entries list structural grid points.
Now PANEL bulk entries can also reference the new SET3 bulk entries. The SET3
bulk entry can list identification numbers for structural grid points, elements,
or physical properties.

When a PANEL bulk entry references SET3 bulk entries that have the GRID
field, the panels will consist of the structural grid points listed on the SET3
bulk entries.

54

Defining panels

When a PANEL bulk entry references SET3 bulk entries that have the ELEM
field, the panels will consist of the grid points that are connection points for
the structural elements listed on the SET3 bulk entries.

When a PANEL bulk entry references SET3 bulk entries that have the PROP
field, the panels will consist of the grid points that are connection points for
the structural elements that reference the physical properties listed on the
SET3 bulk entries.

An example of a complete input file using the SET3 bulk entry with the GRID field
is ac11102.dat. An example of a complete input file using the SET3 bulk entry
with the ELEM field is ac11102el.dat. An example of a complete input file using
the SET3 bulk entry with the PROP field is ac11102pr.dat. All three files can be
found in install_dir/nxn7p1/nast/tpl.
See the updated PANEL bulk entry.
See the updated SET1 bulk entry.
See the new SET3 bulk entry.

PANEL

55

Panel Definition for Coupled Fluid-Structural Analysis

PANEL

Panel Definition for Coupled Fluid-Structural Analysis

Selects sets of structural grid points, elements, or physical properties that define
one or more panels.
Format:
1
PANEL

NAME1

SID1

NAME2

SID2

NAME3

SID3

NAME4

SID4

10

Example:
PANEL

BKDOOR

103

Fields:
Field

Contents

NAMEi

Panel label. (Character)

SIDi

Identification number of a SET1 or SET3 bulk entry that lists the

structural grid points, elements, or physical properties of the panel.
(Integer > 0)

Remarks:
1.

2.

Panels are groups of structural grid points.

If a set of grid points is referenced, the set must include only structural grid
points. The panel will consist of all the grid points in the referenced set.
SET1 and SET3 bulk entries are used to define sets of grid points.

If a set of elements is referenced, the set must include only structural

elements. The panel will consist of all the grid points that are connection
points for these elements. SET3 bulk entries are used to define sets of
elements.

If a set of physical property identifiers is referenced, the physical properties

must be referenced by structural elements. The panel will consist of all grid
points that are connection points for the structural elements referencing the
physical properties included in the set. SET3 bulk entries are used to define
sets of physical property identifiers.

If the referenced SET1 or SET3 bulk entries include structural grid points, the
sets must include at least four grid points for quadrilateral faces and three grid
points for triangular faces.

56

PANEL
Panel Definition for Coupled Fluid-Structural Analysis
3.

It is recommended that all of the connection points for a given element belong to
the same panel.

4.

NAMEi is used only for labeling the output of the panel modal participation
factors (refer to the MODCON and PANCON case control commands). See
Performing a Coupled Fluid-Structural Analysis in the NX Nastran Users
Guide.

SET1

57

Set Definition

SET1

Set Definition

Defines a list of structural grid points for aerodynamic analysis, for XY-plots with
SORT1 output, and for the PANEL bulk data entry. Also defines a list of DRESPi
(i=1,2,3) response IDs for the P2RSET option on the DOPTPRM bulk entry.
Grid ID Format:
1
SET1

SID

G1

G2

G3

G4

G5

G6

G7

G8

-etc.-

SID

R1

R2

R3

R4

R5

R6

R7

R8

-etc.-

31

62

93

124

16

17

18

10

Response ID Format:
1
SET1

10

Example:
SET1

19

Alternate Formats and Example:

SET1

SID

G1

THRU

G2
or

SET1

SID

R1

THRU

R2

SET1

32

THRU

50

Fields:
Field

Contents

SID

Unique identification number. (Integer > 0)

Gi

List of structural grid point identification numbers. (Integer > 0 or

THRU; for the THRU option, G1 < G2.)

Ri

List of DRESPi (i=1,2,3) response IDs for the P2RSET option on the
DOPTPRM bulk entry. (Integer > 0 or THRU; for the THRU
option, R1 < R2.)

58

SET1
Set Definition
Remarks:
1.

SET1 entries may be referenced by the SPLINEi entries, PANEL entries,

XYOUTPUT, and the P2RSET option on the DOPTPRM bulk entry.

2.

When using the THRU option for SPLINEi or PANEL data entries, all
intermediate grid points must exist.

3.

When using the THRU option for XYOUTPUT requests, missing grid points
are ignored.

4.

When using the THRU option for DRESPi requests, missing response IDs
are ignored.

5.

The SID must be unique from other SET1 and SET3 SIDs.

SET3

59

Set Definition

SET3

Set Definition

Defines a list of structural grid points, elements, or physical properties.

Grid ID Format:
1
SET3

SID

TYPE

ID1

ID2

ID3

ID4

ID5

ID6

ID7

-etc.-

GRID

11

13

14

15

20

22

34

41

10

Example:
SET3

Alternate Formats and Example:

SET3

SID

TYPE

ID1

THRU

ID2

SET3

ELEM

20

THRU

33

Fields:
Field

Contents

SID

Unique identification number. (Integer > 0)

TYPE

Set type. (Character: GRID, ELEM, PROP)

IDi

Identifying numbers of structural grids, elements, or physical

properties. (Integer > 0)

Remarks:
1.

The SID must be unique from other SET1 and SET3 SIDs.

2.

By specifying the GRID field, the PANEL bulk entry referencing the SET3 bulk
entry interprets the IDi as structural grid point IDs.

3.

By specifying the ELEM field, the PANEL bulk entry referencing the SET3 bulk
entry interprets the IDi as structural element IDs.

4.

By specifying the PROP field, the PANEL bulk entry referencing the SET3 bulk
entry interprets the IDi as physical property IDs for structural elements.

60

Modal and panel contributions

Modal and panel contributions

Prior to NX Nastran 7.1, you could request output of modal contributions to
structural response. Now the modal contributions capability has been expanded
to support acoustic responses. In addition, the current release includes panel
participation capability that allows you to examine acoustic response contributions
by panel.

Use the enhanced MODCON case control command to request structural

mode and fluid mode contributions using the TOPS and TOPF describers,
respectively.

Use the new PANCON case control command to request structural panel
and structural grid contributions using the TOPP and TOPG describers,
respectively. Use the PANEL and GRID describers to specify the panels and
grids to output panel contributions.

The PANCON capabilities are only supported for SOL 108 and 111.
An example of a complete input file containing the MODCON and PANCON case
control commands is ac11104.dat. It can be found in install_dir/nxn7p1/nast/tpl.
In the example, the MODCON case control command is used with the TOP
describer specified. The TOP describer is a legacy describer for the MODCON case
control command and is equivalent to and can be used interchangeably with the
new TOPS describer. However, the use of the TOPS describer is recommended
for clarity.
See the updated MODCON case control command.
See the new PANCON case control command.
See the updated SET case control command.

Modal and panel contributions mathematical basis

The structural modal contribution from structural modes is given by:

where [ s ] are the uncoupled, undamped structural modes and [ xs ] are the
structural modal amplitudes.
The fluid modal contribution from fluid modes is given by:

where [ f ] are the uncoupled, undamped, rigid-wall acoustic modes and [ xf ]

are the fluid modal amplitudes.

Modal and panel contributions

61

The fluid modal participation from structural modes is given by:

where w is the excitation frequency in rad/sec. The matrix [ Z2 ] is given by:

where [ mf ] is the fluid modal mass, [ bf ] is the fluid modal damping, and [ kf ] is
the fluid modal stiffness.
The matrix [ a ] is a modal representation of the acoustic coupling matrix given by:

where [ A ] is the acoustic coupling matrix.

The fluid-structure panel participation is given by:

where [ A ]panel is a reduced form of the acoustic coupling matrix for specific panels.
The fluid-structure panel-grid participation is given by:

Matrix [ { ATb } ] is formed from columns extracted from the bth boundary panel for
panel grid i. Matrix [ s ] is formed from rows of the structural modal matrix
corresponding to panel grid i.

62

MODCON
Modal Contribution Request

MODCON

Modal Contribution Request

Requests the output of modal contribution results.

Format:

Examples:
MODCON=123
MODCON(SORT1,PHASE,PRINT,PUNCH,BOTH,TOPS=5)=ALL

Describers:
Describer

Meaning

SORT1

Output will be presented as a tabular listing of modal dof for each

frequency or time. (Default)

SORT2

Output will be presented as a tabular listing of frequency or time

for each modal dof. This option is not available for SOL 110.

REAL or
IMAG

Requests rectangular format (real and imaginary) of complex

output. Use of either REAL or IMAG yields the same output.
(Default)

PHASE

Requests polar format (magnitude and phase) of complex output.

Phase output is in degrees.

PRINT

The print file (.f06) will be the output medium. (Default)

PUNCH

The standard punch file (.pch) will be the output medium.

NOPRINT

Generates, but does not print, modal contribution results.

ABS

Output modal contributions in absolute terms. (Default)

NORM

Output modal contributions in normalized terms.

MODCON

63

Modal Contribution Request

Describer

Meaning

BOTH

Output modal contributions in both absolute and normalized

terms.

TOPS (or
TOP)

The number of structural modes to list in the output that have the
greatest contribution to the response at each frequency or time.
The output is sorted in descending order from the structural mode
having the greatest contribution; ps > 0. If ps = 0, no structural
mode contributions will be output, only totals. (Default is ps = 5)

TOPF

The number of fluid modes to list in the output that have the
greatest contribution to the response at each frequency or time.
The output is sorted in descending order from the fluid mode
having the greatest contribution; pf > 0. If pf = 0, no fluid mode
contributions will be output, only totals. (Default is pf = 5)

SOLUTION

SOLUTION = ALL (default) requests that modal contribution

calculations be performed at all frequencies or times defined
by either the FREQUENCY or TSTEP case control commands,
respectively. For SOLUTION = setout, modal contribution
calculations are performed at the frequencies or times specified by
a SET case control command having the identification number of
setout.

Calculate modal contributions for the list defined in SETMC n.

ALL

Calculate modal contributions for the lists defined in all SETMC

sets defined in and above the current subcase.

NONE

Do not calculate modal contributions. This is useful to turn off

modal contribution output for a specific subcase.

Remarks:
1.

Both PRINT and PUNCH may be requested.

2.

MODCON = NONE overrides an overall output request.

3.

SOL 110, 111, 112, and 146 are supported. For SOL 110, modal contributions for
superelements are not supported. The TOPF keyword is only supported for SOL
111. The SOLUTION keyword is only supported for SOL 111, 112, and 146.

4.

Results for SPC forces do not include the effect of any enforced motion applied
at the DOF.

64

MODCON
Modal Contribution Request
5.

The parameters LFREQ, LFREQFL, HFREQ, HFREQFL, LMODES, and

LMODESFL are supported.

6.

The SOLUTION keyword can be abbreviated to SOLU.

7.

The SET case control command referenced by SOLUTION = setout must contain
real values for frequencies or times. Using integer values may lead to erroneous
results.

PANCON

65

Acoustic Panel Contribution Request

PANCON

Acoustic Panel Contribution Request

Requests acoustic panel contribution results.

Format:

Examples:
PANCON=123
PANCON(SORT1,PHASE,PRINT,PUNCH,BOTH,TOPP=5)=ALL

Describers:
Describer

Meaning

SORT1

Output will be presented as a tabular listing of panels or grids for

each frequency. (Default)

SORT2

Output will be presented as a tabular listing of frequency for each

panel or grid.

REAL or
IMAG

Requests rectangular format (real and imaginary) of complex

output. Use of either REAL or IMAG yields the same output.
(Default)

PHASE

Requests polar format (magnitude and phase) of complex output.

Phase output is in degrees.

PRINT

The print file (.f06) will be the output medium. (Default)

PUNCH

The standard punch file (.pch) will be the output medium.

66

PANCON
Acoustic Panel Contribution Request
Describer

Meaning

NOPRINT

Generates, but does not print, contribution results.

ABS

Output contributions in absolute terms. (Default)

NORM

Output contributions in normalized terms.

BOTH

Output contributions in both absolute and normalized terms.

TOPP

The number of structural panels to list in the output that have

the greatest contribution to the response at each frequency. The
output is sorted in descending order from the structural panel
having the greatest contribution; pp > 0. If pp = 0, no structural
panel contributions will be output, only totals. (Default is pp = 5)

TOPG

The number of structural grids to list in the output that have

the greatest contribution to the response at each frequency. The
output is sorted in descending order from the structural grid
having the greatest contribution; pg > 0. If pg = 0, no structural
grid contributions will be output, only totals. (Default is pg = 20)

SOLUTION

SOLUTION = ALL (default) requests that contribution calculations

be performed at all frequencies defined by the FREQUENCY
case control commands. For SOLUTION = setf, contribution
calculations are performed at the frequencies specified by a SET
case control command having the identification number of setf.

PANEL

Specifies the set of panels to output panel contributions. PANEL =

ALL (default) requests that contributions from all panels defined
in the bulk entry section be output. PANEL = setp requests
contributions from panels included in the SET case control
command having the identification number of setp. PANEL =
NONE requests that no contributions from panels be output.

GRID

Specifies the set of grids to output contributions. GRID = NONE

(default) requests that no structural grid contributions be output.
GRID = setg requests contributions from structural grids included
in the SET case control command having the identification number
of setg. GRID = ALL requests contributions from all structural
grids that are part of the acoustic coupling matrix.

Calculate panel and/or grid contributions for the list defined in

SETMC n. Any response defined in SETMC n that is not an
acoustic response will be ignored.

PANCON

67

Acoustic Panel Contribution Request

Describer

Meaning

ALL

Calculate panel and/or grid contributions for the lists defined in

all SETMC sets defined in and above the current subcase. Any
response defined in SETMC sets that is not an acoustic response
will be ignored.

NONE

Do not calculate panel or grid contributions. This is useful to turn

off contribution output for a specific subcase.

Remarks:
1.

Both PRINT and PUNCH may be requested.

2.

PANCON = NONE overrides an overall output request.

3.

SOL 108 and 111 are supported.

4.

The parameters LFREQ, LFREQFL, HFREQ, HFREQFL, LMODES, and

LMODESFL are supported.

5.

The SOLUTION and PANEL keywords can be abbreviated to SOLU and PANE,
respectively.

6.

The SET case control command referenced by SOLUTION = setf must contain
real values for frequencies or times. Using integer values may lead to unintended
results.

7.

The SET case control command referenced by PANEL = setp must contain the
alphanumeric name of existing panels defined by PANEL bulk entries.

68

SET
Set Definition, General Form

SET

Set Definition, General Form

Sets are used to define the following lists:

Lists
1.

Identification numbers (point, element, or superelement) for processing and

output requests.

2.

Times for which output will be printed in transient response problems using the
OTIME case control command or the MODCON case control command with the
SOLUTION = setout describer specified.

3.

Frequencies for which output will be printed in frequency response problems

using the OFREQ case control command or the MODCON case control command
with the SOLUTION = setout describer specified or the PANCON case control
command with the SOLUTION = setf describer specified.

4.

Panels for which output will be printed in frequency response problems using
the PANCON case control command with the PANEL describer specified.

5.

Surface or volume identification numbers to be used in GPSTRESS or STRFIELD

case control commands.

6.

With SOL 200, DRESP1 design responses that are assigned to a specific subcase
via a DRSPAN case control command which refers to a particular SET.

Formats:
SET n = {i1[,i2, i3, THRU i4, EXCEPT i5, i6, i7, i8, THRU i9]}
SET n = {r1, [r2, r3, r4]}
SET n = {name1,[name2,name3,name4]}
SET n = ALL
Examples:
SET
SET
SET
SET
SET
SET

77=5
88=5, 6, 7, 8, 9, 10 THRU 55 EXCEPT 15, 16, 77, 78, 79, 100 THRU 300
99=1 THRU 100000
101=1.0, 2.0, 3.0
105=1.009, 10.2, 13.4, 14.0, 15.0
5=PANEL1,PANEL3,PANEL4

SET

69

Set Definition, General Form

Describers:
Describer

Meaning

Set identification number. Any set may be redefined by

reassigning its identification number. SETs specified under a
SUBCASE command are recognized for that SUBCASE only.
(Integer>0)

i1, i2, etc.

Identification numbers. If no such identification number exists,

the request is ignored. (Integer 0)

i3 THRU i4

Identification numbers (i4>i3). (Integer>0)

EXCEPT

Set identification numbers following EXCEPT will be deleted

from the output list as long as they are in the range of the set
defined by the immediately preceding THRU. An EXCEPT list
may not include a THRU list or ALL.

r1, r2, etc.

Frequencies or times for output. The nearest solution frequency

or time will be output. EXCEPT and THRU cannot be used. If an
OFREQ, OTIME, MODCON (with SOLUTION = setout describer
specified), or PANCON (with SOLUTION = setf describer
specified) case control command references the set, then the
values must be listed in ascending sequences, r1>r2>r3>r4...etc.,
otherwise some output may be missing. (Real>0.0)

name1,
name2, etc.

Alphanumeric names of panels defined by PANEL bulk entries.

(Character)

ALL

All members of the set will be processed. This option may not be
used in a DRSPAN referenced set.

Remarks:
1.

A SET command may be more than one physical command. A comma at the end
of a physical command signifies a continuation command. Commas may not end
a set. THRU may not be used for continuation. Place a number after the THRU.

2.

Set identification numbers following EXCEPT within the range of the THRU
must be in ascending order.

3.

In SET 88 in the example section above, the numbers 77, 78, etc., are included in
the set because they are outside the prior THRU range.

70

Support for damping element forces

Support for damping element forces

Prior to NX Nastran 7.1, force output on damping elements was not available for
transient response analysis. Force output on damping elements was available
for modal frequency response analysis, but you were required to select the mode
displacement method (PARAM,DDRMM,-1).
Force output on damping elements is now available for:

Transient response analysis.

Modal frequency response analysis without having to select the mode

displacement method.

For both of these analysis types, you can output the forces on damping elements by
simply including the damping elements in the force request.
See the updated FORCE case control command.

FORCE

71

Element Force Output or Particle Velocity Request

FORCE

Element Force Output or Particle Velocity Request

Requests the form and type of element force output or particle velocity output in
coupled fluid-structural analysis. Note: ELFORCE is an equivalent command.
Format:

Examples:
FORCE=ALL
FORCE(REAL, PUNCH, PRINT)=17
FORCE=25

Describers:
Describer

Meaning

SORT1

Output will be presented as a tabular listing of elements for

each load, frequency, eigenvalue, or time, depending on the
solution sequence.

SORT2

Output will be presented as a tabular listing of frequency or

time for each element type.

PLOT

Generates force output for requested set but no printed output.

PRINT

The printer will be the output medium.

PUNCH

The punch file will be the output medium.

REAL or IMAG

Requests rectangular format (real and imaginary) of complex

output. Use of either REAL or IMAG yields the same output.

PHASE

Requests polar format (magnitude and phase) of complex

output. Phase output is in degrees.

72

FORCE
Element Force Output or Particle Velocity Request
Describer

Meaning

PSDF

Requests the power spectral density function be calculated for

random analysis post-processing. The request must be made
above the subcase level and RANDOM must be selected in the
case control. See Remark 8.

ATOC

Requests the autocorrelation function be calculated for random

analysis post-processing. The request must be made above
the subcase level and RANDOM must be selected in the case
control. See Remark 8.

CRMS

Requests the cumulative root mean square function be

calculated for random analysis post-processing. Request must
be made above the subcase level and RANDOM must be made
in the case control. See Remark 8.

RALL

Requests all of PSDF, ATOC, and CRMS be calculated for

random analysis post-processing. The request must be made
above the subcase level and RANDOM must be selected in the
case control. See Remark 8.

RPRINT

Writes random analysis results to the print file. (Default) See

Remark 8.

NORPRINT

Disables the writing of random analysis results to the print

file. See Remark 8.

RPUNCH

Writes random analysis results to the punch file. See Remark

8.

CENTER

Output CQUAD4, CQUADR, CTRIAR element forces at the

center only.

CORNER or
BILIN

Output CQUAD4, CQUADR, CTRIAR element forces at the

center and grid points using strain gage approach with bilinear
extrapolation.

SGAGE

Output CQUAD4 element forces at center and grid points

using strain gage approach.

CUBIC

Output CQUAD4 element forces at center and grid points

using cubic bending correction.

ALL

Forces for all elements will be output.

FORCE

73

Element Force Output or Particle Velocity Request

Describer

Meaning

Set identification of a previously appearing SET command.

Only forces of elements with identification numbers that
appear on this SET command will be output. (Integer>0)

NONE

Forces for no elements will be output.

Remarks:
1.

ALL should not be used in a transient problem.

2.

The defaults for SORT1 and SORT2 depend on the type of analysis:

SORT1 is the default in static analysis, frequency response, steady state

heat transfer analysis, real and complex eigenvalue analysis, flutter
analysis, and buckling analysis. If SORT2 is selected in a frequency
response solution for one or more of the commands ACCE, DISP, FORC,
GPFO, MPCF, OLOA, SPCF, STRA, STRE, and VELO then the remaining
commands will also be output in SORT2 format.

SORT2 is the default in transient response analysis (structural and heat

transfer). SORT2 is not available for real eigenvalue (including buckling),
complex eigenvalue, or flutter analysis. If SORT1 is selected in a transient
solution for one or more of the commands ACCE, DISP, ENTH, FORC,
GPFO, HDOT, MPCF, OLOA, SPCF, STRA, STRE, and VELO then the
remaining commands will also be output in SORT1 format.

XY plot requests will force SORT2 format thus overriding SORT1 format
requests.

3.

ELFORCE is an alternate form and is entirely equivalent to FORCE.

4.

FORCE=NONE overrides an overall request.

5.

For composite stress and/or failure index output, a FORCE request is required
for the desired elements.

6.

In nonlinear transient analysis, this request is ignored for nonlinear elements.

7.

The options CENTER, CORNER, CUBIC, SGAGE, and BILIN are recognized
only in the first subcase and determine the option to be used in all subsequent
subcases with the STRESS, STRAIN, and FORCE commands. Consequently,
options specified in subcases other than the first subcase will be ignored.

74

Beta capability: Initial conditions for modal transient analysis

8.

If the STRESS command is specified in the first subcase then the option on
the STRESS command is used in all subcases with STRESS, STRAIN, and
FORCE commands.

If the STRAIN command and no STRESS command is specified in the first

subcase, then the option on the STRAIN command is used in all subcases
containing STRESS, STRAIN, and FORCE commands.

If the FORCE command and no STRESS or STRAIN command is specified

in the first subcase, then the option on the FORCE command is used in all
subcases containing STRESS, STRAIN, and FORCE commands.

If STRESS, STRAIN, and FORCE commands are not specified in the first
subcase, then the CENTER option is used in all subcases containing
STRESS, STRAIN, and FORCE commands.

The following applies to SOL 111 PSD solutions:

Frequency response output occurs in addition to any random output. The

PRINT,PUNCH,PLOT describers control the frequency response output.
The RPRINT,NORPRINT,RPUNCH describers control the random output.

The SORT1 and SORT2 describers only control the output format for
the frequency response output. The output format for random results is
controlled using the parameter RPOSTS.

Any combination of the PSDF, ATOC, and CRMS describers can be selected.
The RALL describer selects all three.

When requesting PSDF, CRMS, ATOC, or RALL, both the overall RMS and
the Number of Zero Crossing tables are always calculated.

Beta capability: Initial conditions for modal transient

analysis
You can calculate the response of a structure to an arbitrary loading using direct
transient analysis (SOL 109) or modal transient analysis (SOL 112). You can
use the IC case control command to specify the initial condition for both types of
analysis.
For direct transient analysis (SOL 109) using the IC case control command:

If you specify the PHYSICAL (default) describer, TIC bulk entries that contain
the initial condition in physical space are referenced.

Beta capability: Initial conditions for modal transient analysis

75

If you specify the STATSUB describer, the results of a static subcase are used
as the initial condition.

If you specify the DIFFK describer in conjunction with the STATSUB

describer, the results of a static subcase are used as the initial condition and
the effects of differential stiffness are accounted for during the analysis.

For modal transient analysis (SOL 112) using the IC case control command:

If you specify the PHYSICAL (default) describer, TIC bulk entries that contain
the initial condition in physical space are referenced. The initial conditions in
physical space are converted to modal space during the solve.

If you specify the MODAL describer, TIC bulk entries that contain the initial
condition in modal space are referenced.

If you specify the STATSUB describer, the results of a static subcase are
converted to modal space during the solve and used as the initial condition.

If you specify the DIFFK describer in conjunction with the STATSUB

describer, the results of a static subcase are converted to modal space during
the solve and used as the initial condition. The effects of differential stiffness
are accounted for during the analysis.

Beginning with the NX Nastran 7.1 release, as a beta capability, you can optionally
use the new TZERO describer with the IC case control command. When you specify
the TZERO describer, the static deflection in modal space resulting from the loading
at time = 0 is used as the initial condition for a modal transient analysis (SOL 112).
Note
At present, there is no way to account for the effects of differential stiffness
in a modal transient analysis (SOL 112) when you specify the TZERO
describer.
An example of a complete input file containing the IC case control command
with the TZERO describer specified is ictzero1.dat. It can be found in
install_dir/nxn7p1/nast/tpl.
See the updated IC case control command.

76

IC
Transient Initial Condition Set Selection

IC

Transient Initial Condition Set Selection

Selects the initial conditions for transient analyses (SOLs 109, 112, 129, 159, 601,
and 701).
Format:

Examples:
IC = 17
IC(PHYSICAL) = 10
IC(MODAL) = 20
IC(STATSUB) = 30
IC(STATSUB,DIFFK) = 1030
IC(TZERO)

Describers:
Describer

Meaning

PHYSICAL

The TIC bulk entries selected by set n define initial conditions

for coordinates involving grid and scalar points (default). See
Remark 6.

MODAL

The TIC bulk entries selected by set n define initial conditions

for modal coordinates. See Remarks 3 and 6.

STATSUB

Use the solution of the static analysis subcase n as the initial

conditions. See Remark 4.

DIFFK

Include the effects of differential stiffness in the solution. See

Remarks 4 and 5.

TZERO

Use the static deflection resulting from the loading at time =

0 as the initial condition for a modal transient analysis (SOL
112). For this option, n is not needed. If n is specified, it will
be ignored.

Sparse data recovery

77

Describer

Meaning

For the PHYSICAL option, n is the set identification number

of TIC bulk entries for structural analysis (SOLs 109, 112,
129, 601, and 701) or TEMP and TEMPD bulk entries for heat
transfer analysis (SOL 159). For the MODAL option, n is the set
identification number of TIC bulk entries for modal transient
analysis (SOL 112). For the STATSUB option, n is the ID of a
static analysis subcase (SOL 109 and 112). (Integer>0)

Remarks:
1.

For structural analysis, TIC bulk entries will not be used unless selected in
the case control section.

2.

Only the PHYSICAL option (the default) may be specified in direct transient
analysis (SOL 109), nonlinear or linear transient analysis (SOL 129), heat
transfer analysis (SOL 159), advanced implicit nonlinear analysis (SOL 601,N),
and advanced explicit nonlinear analysis (SOL 701).

3.

IC(MODAL) may be specified only in modal transient analysis (SOL 112).

4.

IC(STATSUB) and IC(STATSUB,DIFFK) may not both be specified in the same

execution. They are only applicable to direct transient analysis (SOL 109) and
modal transient analysis (SOL 112), but not in a DMP solution.

5.

The DIFFK keyword is meaningful only when used in conjunction with the
STATSUB keyword.

6.

Initial condition definitions on extra points are not supported and will be ignored.

7.

IC(TZERO) may be specified only in modal transient analysis (SOL112).

8.

The IC case control command is not supported in multiple subcases.

Sparse data recovery

An improved sparse data recovery option became available in NX Nastran 5 for
modal frequency response analysis (SOL 111), modal transient response analysis
(SOL 112), and optimization (SOL 200; ANALYSIS=MFREQ or MTRAN).
This sparse data recovery option is now also supported for direct frequency
response (SOL 108), and is used by default. This change can significantly reduce
your run times when large amounts of data are recovered.

78

Unsymmetric A-set reduction for rotor dynamics

The sparse data recovery option is on by default, but you can deactivate it with
system cell 421:
NASTRAN SYSTEM(421) = 0
or by using the keyword SPARSEDR:
NASTRAN SPARSEDR = 0.

Unsymmetric A-set reduction for rotor dynamics

Rotor dynamic effects produce unsymmetric stiffness matrices. NX Nastran can
now perform an A-set reduction of these matrices to increase solution efficiency.
This method reduces problem sizes for dynamic analysis by extracting modes
from the O-set, and preserving the degrees of freedom in the A-set. It is efficient
for SOL 107 jobs with rotor dynamics.
Inputs
You must specify the desired A-set degrees of freedom with ASET or ASET1 bulk
entries. For best accuracy and performance, select the A-set carefully. For a solid
rotor example, it is sufficient if you specify points on the center line as A-set grid
points; for turbines, you must also specify the grid points on the blades. For other
structures, make a reasonable choice.
Remark
You must specify the EIGRL bulk entry in addition to the EIGC bulk entry to
extract modes from the O-set. An appropriate EIGRL setting is problem dependent;
more modes improve accuracy, but also increase run time.
Example

Turbine model

45,350 grid points, 272,100 degrees of freedom

Machine: 1.9 GHz Xeon

2 GB memory

10 steps in ROTORD

Method
Elapsed (min:sec)
CPU (seconds)

Direct Sol 107

3636:47
139897

Unsym A-set Sol 107

Disk IO (GB)

2575

1120

131:10
6784

Chapter

Superelements

External superelements
A more efficient external superelement procedure was introduced with NX Nastran
6 and enhanced in subsequent releases. The capabilities of external superelements
are further enhanced in this release.
Prior to NX Nastran 7.1, the assembly solution required you to include
external superelement output data in the assembly input file for each external
superelement. It could be obtained as punch output in the external superelement
solution by requesting EXTBULK output on the EXTSEOUT case control.
This data however is redundant because it is also available in the external
superelement files containing the matrix data. Therefore, beginning in NX Nastran
7.1, the external superelement data is not required in the assembly input file
and will be retrieved from the external superelement matrix files if not present
in the input file.

80

EXTSEOUT
External Superelement Creation Specification

EXTSEOUT

External Superelement Creation Specification

Specify the various requirements for the creation of an external superelement.

Format:

Examples:
EXTSEOUT
EXTSEOUT(ASMBULK,EXTID=100)
EXTSEOUT(ASMBULK,EXTBULK,EXTID=200)
EXTSEOUT(EXTBULK,EXTID=300)
EXTSEOUT(DMIGDB)
EXTSEOUT(ASMBULK,EXTID=400,DMIGOP2=21)
EXTSEOUT(EXTID=500,DMIGPCH)
EXTSEOUT(ASMBULK,EXTBULK,EXTID=500,DMIGSFIX=XSE500,DMIGPCH)
EXTSEOUT(ASMBULK,EXTBULK,EXTID=500,DMIGSFIX=EXTID,DMIGPCH)
EXTSEOUT(STIF,MASS,DAMP,EXTID=600,ASMBULK,EXTBULK,MATDB)
See Remarks 10, 11, and 12.

Describers:
Describer

Meaning

STIFFNESS

Store the boundary stiffness matrix. See Remarks 1 and 2.

MASS

Store the boundary mass matrix. See Remark 1.

DAMPING

Store the boundary viscous damping matrix. See Remarks 1

and 2.

K4DAMP

Store the boundary structural damping matrix. See Remarks 1

and 2.

LOADS

Store the boundary static loads matrix. See Remarks 1 and 2.

EXTSEOUT

81

External Superelement Creation Specification

Describer

Meaning

ASMBULK

Generate bulk data entries related to the subsequent

superelement assembly process and store them on the
assembly punch file (.asm). This data is to be included in the
main bulk data portion of the subsequent assembly solution.
See Remarks 4 and 13.

EXTBULK

Generate and store bulk data entries for the external

superelement on the standard punch file (.pch) when used
in combination with one of either MATDB, DMIGDB, or
DMIGOP2. This data is used in the BEGIN SUPER portion of
the bulk data of the subsequent assembly solution. EXTBULK
is ignored if either DMIGPCH or MATOP4 is specified. If
EXTBULK is not specified, the subsequent assembly solution
retrieves the required data for the external superelement from
the medium on which the boundary matrices are stored. See
Remarks 5 and 6.

EXTID = seid

seid (integer>0) is the superelement ID to be used in the

SEBULK and SECONCT bulk data entries stored on the
assembly punch file (.asm) if ASMBULK is specified and in the
BEGIN SUPER bulk data entry stored on the standard punch
file (.pch) if DMIGPCH or MATOP4 is specified. See Remarks
3, 4, 5, and 7.

DMIGSFIX =
cccccc

cccccc is the suffix (up to six characters and must not = any
EXTSEOUT keyword) that is to be employed in the names of
the DMIG matrices stored on the standard punch file (.pch) if
the DMIGPCH keyword is specified. See Remarks 8 11.

DMIGSFIX =
EXTID

The seid defined by the EXTID keyword is the suffix that is

to be employed in the names of the DMIG matrices stored on
the standard punch file (.pch) if the DMIGPCH keyword is
specified. See Remarks 8 11.

MATDB (or
MATRIXDB)

Store the boundary matrices and other information on the

database (default).

DMIGDB

Similar to MATDB (or MATRIXDB) except that the boundary

matrices are stored as DMIG bulk data entries on the database.

DMIGOP2=unit

Store the boundary matrices as DMIG bulk data entries on an

OUTPUT2 file whose Fortran unit number if given by unit
(integer>0). See Remark 14.

82

EXTSEOUT
External Superelement Creation Specification
Describer

Meaning

DMIGPCH

Store the boundary matrices as DMIG bulk data entries on the

standard punch file (.pch). See Remarks 6 13.

MATOP4
= unit (or
MATRIXOP4
= unit)

Store the boundary matrices on an OP4 file whose Fortran

unit number is given by unit (Integer>0). See Remarks 3, 5,
6, 8, and 10.

Remarks:
1.

If none of the describers STIFFNESS, MASS, DAMPING, K4DAMP, and LOADS

are specified, then all matrices are stored.

2.

STIFFNESS, DAMPING, K4DAMP, and LOADS may be abbreviated to STIF,

DAMP, K4DA, and LOAD, respectively.

3.

EXTID and an seid value must be specified if one or more of ASMBULK,

EXTBULK, DMIGPCH, or MATOP4 are specified. If the DMIGSFIX=EXTID
form is employed along with the DMIGPCH keyword, the value seid may not
exceed 999999, since this value becomes part of the names given to the DMIG
matrices generated on the standard punch file (.pch). See Remark 11.

4.

If ASMBULK is specified, the following bulk data entries are generated and
stored on the assembly punch file (.asm):
SEBULK seid
SECONCT seid
GRID entries for the boundary points
CORD2x entries associated with the above GRID entries

5.

If DMIGPCH is not specified, but MATOP4 or EXTBULK (in combination with

MATDB, DMIGDB, or DMIGOP2) is specified, the following bulk data entries
are generated and stored on the standard punch file (.pch):
BEGIN SUPER seid
GRID entries for the boundary points
GRID entries for the interior points referenced by PLOTEL entries
CORD2x entries associated with the above GRID entries

EXTSEOUT

83

External Superelement Creation Specification

EXTRN
ASET/ASET1
QSET/QSET1
SPOINT
PLOTEL
6.

If DMIGPCH or MATOP4 is specified, then EXTBULK is ignored even if it is

specified.

7.

If DMIGPCH is specified, the following bulk data entries are generated and
stored on the standard punch file (.pch):
BEGIN SUPER seid
GRID entries for the boundary points
CORD2x entries associated with the above GRID entries
ASET/ASET1
SPOINT
DMIG entries for the requested boundary matrices

8.

The DMIGSFIX keyword is ignored if DMIGPCH is not specified.

9.

If DMIGPCH is specified without the DMIGSFIX keyword, then the boundary

DMIG matrices generated and stored on the standard punch file (.pch) will have
names of the following form:
KAAX (boundary stiffness matrix)
MAAX (boundary mass matrix)
BAAX (boundary viscous damping matrix)
K4AAX (boundary structural damping matrix)
PAX (boundary load matrix)

10. If the DMIGSFIX = cccccc form is employed along with the DMIGPCH keyword,
then the boundary DMIG matrices generated and stored on the standard punch
file (.pch) will have names of the following form:
Kcccccc (boundary stiffness matrix)

84

EXTSEOUT
External Superelement Creation Specification
Mcccccc (boundary mass matrix)
Bcccccc (boundary viscous damping matrix)
K4cccccc (boundary structural damping matrix)
Pcccccc (boundary load matrix)
11. If the DMIGSFIX = EXTID form is employed along with the DMIGPCH keyword,
then the boundary DMIG matrices generated and stored on the standard punch
file (.pch) will have names of the following form:
Kseid (boundary stiffness matrix)
Mseid (boundary mass matrix)
Bseid (boundary viscous damping matrix)
K4seid (boundary structural damping matrix)
Pseid (boundary load matrix)
12. If the DMIGPCH option is specified, the boundary DMIG matrices generated and
stored on the standard punch file (.pch) may not be as accurate as the boundary
matrices resulting from other options (MATDB/MATRIXDB or DMIGOP2 or
MATOP4/MATRIXOP4). Accordingly, this may result in decreased accuracy from
the subsequent assembly job utilizing these DMIG matrices.
13. The punch output resulting from EXTSEOUT usage is determined by
ASMBULK, EXTBULK, DMIGPCH, and MATOP4 as follows:

No ASMBULK, EXTBULK, DMIGPCH, or MATOP4 results in no punch

output.

ASMBULK, but no DMIGPCH, MATOP4, or EXTBULK (in combination

with MATDB, DMIGDB, or DMIGOP2) results in punch output being
generated and stored on the assembly punch file (.asm). See Remark 4.

No ASMBULK, but DMIGPCH, MATOP4, or EXTBULK (in combination

with MATDB, DMIGDB, or DMIGOP2) results in punch output being
generated and stored on the standard punch file (.pch). See Remarks 5 or 7,
as appropriate.

ASMBULK and DMIGPCH, MATOP4, or EXTBULK (in combination with

MATDB, DMIGDB, or DMIGOP2) results in punch output consisting of
two distinct and separate parts. One part is generated and stored on the
assembly punch file (.asm) as indicated in Remark 4. The other part is

EXTSEOUT

85

External Superelement Creation Specification

generated and stored on the standard punch file (.pch) as indicated in
Remark 5 or 7, as appropriate.
14. If DMIGOP2=unit or MATOP4=unit is specified, an appropriate ASSIGN
OUTPUT2 or ASSIGN OUTPUT4 statement must be present in the File
Management Section (FMS) for the unit.
15. The creation of an external superelement using EXTSEOUT involves running a
non-superelement NX Nastran job, with the following additional data:

The data for the creation of the external superelement is specified by the
EXTSEOUT case control entry.

The boundary points of the external superelement are specified by

ASET/ASET1 bulk data entries.

If the creation involves component mode reduction, the required generalized

coordinates are specified using QSET/QSET1 bulk data entries. The
boundary data for the component mode reduction may be specified using the
BNDFIX/BNDFIX1 and BNDFREE/BNDFREE1 bulk data entries (or their
equivalent BSET/BSET1 and CSET/CSET1 bulk data entries). (The default
scenario assumes that all boundary points are fixed for the component
mode reduction.)

The output for the external superelement is generated in the assembly job.
This output consists of displacements, velocities, accelerations, SPC forces,
MPC forces, grid point force balances, stresses, strains, and element forces.
However, in order for this output to be generated in the assembly job, the
output requests must be specified in the external superelement creation run.
Normally, the only output requests for the external superelement that are
honored in the assembly job are those that are specified in the creation
run. There is, however, one important exception to this: the displacement,
velocity, acceleration, SPC forces, and MPC forces output for the boundary
grid points as well as for all grid points associated with PLOTEL entries can
be obtained in the assembly job even if there is no output request specified
for these points in the creation run.

If the assembly job involves the use of PARAM Bulk Data entries, then
the following points should be noted:

PARAM entries specified in the Main Bulk Data portion of the input
data apply only to the residual and not to the external superelement.

PARAM entries specified in the BEGIN SUPER portion of the Bulk

Data for an external superelement apply only to the superelement.

86

EXTSEOUT
External Superelement Creation Specification

The most convenient way of ensuring that PARAM entries apply not
only to the residual but also to all external superelements is to specify
such PARAM entries in Case Control, not in the Main Bulk Data. This
is particularly relevant for such PARAMs as POST.

16. Output transformation matrices (OTMs) are generated for the following outputs
requested in the in external superelement run with EXTSEOUT:

DISPLACEMENT

VELOCITY

ACCELERATION

SPCFORCE

MPCFORCES

GPFORCE

STRESS

STRAIN

FORCE

Only these external superelement results can be output in the system analysis
run. PARAM,OMID,YES is not applicable to the OTMs.
17. If a PARAM,EXTOUT or PARAM,EXTUNIT also exit, they will be ignored.
The existence of the EXTSEOUT case control entry takes precedence over
PARAM,EXTOUT and PARAM,EXTUNIT.
18. This capability is enabled in SOLs 101, 103, 105, 107-112, 114, 115, 118, 129,
144-146, 159, 187, and 200. This capability is not enabled for thermal analyses.
Superelement results can be recovered in the second step (i.e. superelement
assembly, analysis, and data recovery) for SOLs 101, 103, 105-112, 129, 144-146,
153, and 159.
19. The run creating the external superelement using this capability is not a
superelement run. No superelement designations are allowed (i.e. SUPER,
SEALL, SESET, BEGIN SUPER, etc.).

Chapter

Advanced nonlinear

Advanced nonlinear
Element enhancements

Four new plane stress elements CPLSTS3, CPLSTS4, CPLSTS6 and

CPLSTS8 and four new plane strain elements CPLSTN3, CPLSTN4,
CPLSTN6 and CPLSTN8 are available for SOL 601. The new PPLANE
bulk entry defines the properties for the eight new elements.
The examples of complete input files using the new plane stress elements
are anlplsts*.dat. The examples of complete input files using the new
plane strain elements are anlplstn*.dat. All of these files can be found
in install_dir/nxn7p1/nast/tpl/.
See chapter 2 of the NX Nastran 7.1 Advanced Nonlinear Theory and
Modeling Guide and the NX Nastran 7.1 Quick Reference Guide for input
descriptions.

Contact and glue enhancements

The 2D edge-to-edge contact inputs used with axisymmetric elements are

supported with the new plane stress and plane strain elements. You can
use the existing BLSEG bulk entry for the 2D contact region definition.
The 2D contact definition uses the bulk entries BCRPARA, BCTSET,
BCTPARA, which are also used to define 3D contact. All three of these
element types (axisymmetric, plane stress, plane strain) including 2D
contact conditions can exist in the same model.
An example of a complete input file using the new plane stress
elements with contact conditions is anlplsts07.dat. An example of a
complete input file using the new plane strain elements with contact
conditions is anlplstn11.dat. Both of these files can be found in
install_dir/nxn7p1/nast/tpl/.

You can use the new BCPROPS bulk entry in SOL 601 to create solid
element contact/glue regions by property ID. The BCPROPS bulk
entry works similar to the BCPROP bulk entry that is used to create
shell element regions by property ID. Only solid element free faces

88

Advanced nonlinear
are considered in the contact and glue algorithms. The free faces are
automatically determined by the software.

Beginning in version 7.0, variable grid CTETRA and CPYRAM elements

became available for SOL 601. They now can be included in contact or
glue regions.
Mixed order CPYRAM and CTETRA elements are useful to transition
from a linear CHEXA mesh to a parabolic CTETRA mesh.

See the NX Nastran 7.1 Advanced Nonlinear Theory and Modeling Guide and
the NX Nastran 7.1 Quick Reference Guide for input descriptions.
Results recovery restart
You can use the new SOL 601 restart option to recover results that you did not
request in the original solution. Use the new MODEX parameter option 2 on
the NXSTRAT bulk entry to request the results recovery solution.
See section 10.2 in the NX Nastran 7.1 Advanced Nonlinear Theory and
Modeling Guide and the NXSTRAT bulk entry in the NX Nastran 7.1 Quick
Reference Guide.
PUNCH output
SOL 601 now supports PUNCH output requests. The grid and element sets
are also supported by the punch output request.

Chapter

Contact for linear solutions

Solid element property regions

The new BCPROPS bulk entry is available to create solid element contact and
glue regions by property ID (PSOLID bulk entry ID). The BCPROPS entry works
similar to the supported BCPROP bulk entry. The BCPROP bulk entry is used to
create shell element contact and glue regions by property ID (PSHELL bulk entry
ID). Only the solid element free faces are considered in the contact and/or glue
algorithm. The free faces of the solid elements selected with a property ID are
automatically determined by the software.
See the BCPROPS bulk entry.

90

BCPROPS

BCPROPS

Contact or Glue Region Definition by PSOLID Property ID

Defines a surface-to-surface contact or glue region by PSOLID Property ID.

Format:
1

BCPROPS

ID

IP1

IP2

IP3

IP4

IP5

IP6

IP7

22

IP8

IP9

IP10

-etc-

10

Example:
BCPROPS

Fields:
Field

Contents

ID

Identification number of a contact or glue region. See Remark 2 and

3. (Integer > 0)

IPi

PSOLID Property IDs. (Integer > 0)

Remarks:
1.

The continuation field is optional.

2.

BCPROPS is a collection of one or more solid property IDs. BCPROPS defines a

contact or glue region formed by the free faces of the solid elements and may act
as a source or target.

3.

The ID must be unique with respect to all other BLSEG, BSURFS, BSURF,
BCPROP, and BCPROPS entries.

4.

Only the solid element free faces within the given set of PIDs are considered in
the contact and/or glue algorithm. These free faces are automatically determined
by the software.

Contact conditions with linear buckling

Contact conditions can be included in a linear buckling solution (SOL 105),
although there are important considerations. The initial linear statics solution
determines the differential stiffness (Ks) and the final contact stiffness (Kcontact).
The final contact stiffness is added to the stiffness matrix for the buckling subcase:

Contact conditions with linear buckling

91

([K + Kcontact] + l[Ks]){D}=0

Normally the buckling load is determined by multiplying l from the first buckling
mode by the applied load. When contact conditions are included, this is valid only
when the first l is close to "1.0". Although contact conditions can be included in
linear solutions, they are iterative and nonlinear conditions. Because contact
conditions are nonlinear, the contact stiffness from the initial statics solution is
nonlinearly dependent on the applied load. As a result, the contact stiffness
result which was valid for the original loading, may not be valid for the scaled
load condition.
The buckling solution will report a warning if the lowest l is not within 10% of
1.0 (0.9 - 1.1). When the warning is issued, you can scale your load by l, and then
rerun both the linear statics solution with contact conditions, and the buckling
solution again. You will need to repeat this process until l is close 1.0.
The inputs for a linear buckling solution with contact conditions require a subcase
for the linear statics subcase and the buckling solution.
In addition, the linear statics subcase must include the BCSET case control
command. If the linear statics subcase is the first subcase, then a STATSUB bulk
entry is not needed. If it is not the first subcase, a STATSUB bulk entry is needed
in the buckling subcase to reference the linear statics subcase ID.

Chapter

Glue enhancements

Edge-to-surface glue
An edge-to-surface glue capability is now available. You can glue the edges of shell
elements to the faces of a solid or shell elements.

The existing BLSEG bulk entry defines the shell element edge regions.

You can use any of the face region inputs to define the solid and/or shell face
regions. Face region inputs include the BSURF, BSURFS, BCPROP, and
BCPROPS bulk entries.

The BGSET bulk entry defines the connection between the edge region ID
and the face region ID.

A weld like formulation is used to make the connection (the software always
uses the GLUETYPE=2 option on the BGPARM bulk entry).

Edge-to-surface gluing remarks:

94

Edge-to-surface glue

A glue edge region defined with the BLSEG entry consists of one or more line
segments defined between consecutive grid points. You must enter the grid
points that define the edge region in a continuous topological order on the
BLSEG entry. If an edge region or curve forms a closed loop, for example,
the grid points around the perimeter of a cylinder edge, the last grid point
identification number should be the same as the first grid point number.

The grid point IDs on the BLSEG entry used to define a glue edge region can
only be part of the CQUAD4, CQUADR, CQUAD8, CTRIA3, CTRIAR and
CTRIA6 element connectivity.

On the BGSET bulk entry, you must enter the BLSEG ID as the source region
ID, and a shell or solid element face region ID as the target region ID.

The grid points on glued edges and surfaces do not need to be coincident.

Edge-to-surface glue definitions are supported in all solution sequences except

solutions 144 -146, 153, 159, 601 and 701. Edge-to-surface glue definitions
cannot be used to represent acoustic glue connections.

Refinement is ignored for edge-to-surface glue pairs.

Shell offsets are not accounted for in any glue definitions. The gluing occurs
at the grid locations and not at the offset location.

Only the PENGLUE and PENTYP parameters on the BGPARM bulk entry are
applicable to the edge-to-surface glue. All other parameters are ignored.

Input example:
...
Case Control
BGSET = 114
...
Bulk Data
...
$Grid points entered on a BLSEG entry define the edge region
BLSEG
2
1534
1699
1535
1697
1536
1695
+
1693
1538
1690
1539

1537+

$BSURFS defines the surface region in this example

BSURFS
1
220
442
543
620+
+
210
441
620
619
200
440
619
477+
+
380
614
593
594
370
613
594
473
...
$The BLSEG ID must be entered as the source region on the BGSET entry
BGSET
114
2
1.0100504

Edge-to-surface glue

The input file gluedgsurf01.dat is included in the

installation_path\nxn7p1\nast\tpl directory to demonstrate the enhancement.

95

96

BLSEG
Defines a glue or contact edge region, or a curve for slideline contact.

BLSEG

Defines a glue or contact edge region, or a curve for slideline contact.

Defines a glue or contact edge region or a curve for slideline contact via grid numbers.
Format 1: (Formats 1 and 2 cannot be combined on the same line)
1
BLSEG

ID

G1

G2

G3

G4

G5

G6

G7

BY

INC

10

Format 2:
ID

BLSEG

G1

THRU

G2

Continuation Format 1: (Continuation formats 1 and 2 cannot be

combined on a single continuation line)
G8

G9

G10

G11

etc.

Continuation Format 2:
G8

THRU

G9

BY

INC

THRU

190

BY

82

16

Example:
BLSEG

14

101

46

23

57

201

THRU

255

93

94

95

97

Fields:
Field

Contents

ID

Edge region or curve identification number. See Remark 1 (Integer

> 0).

Gi

Grid point identification numbers in a continuous topological order.

See Remark 2 (Integer > 0).

INC

Grid point identification number increment. See Remark 3 for

default (Integer or blank).

BLSEG

97

Defines a glue or contact edge region, or a curve for slideline contact.

Remarks:
1.

The ID must be unique with respect to all other BLSEG entries and all surface
region IDs defined with the BSURF, BSURFS, BCPROP, and BCPROPS entries.

2.

An edge region or curve consists of one or more line segments defined between
consecutive grid points. The grid points defining the edge region or curve must
be entered in a continuous topological order. If an edge region or curve forms a
closed loop, for example, the grids around the perimeter of a cylinder edge, the
last grid point identification number should be the same as the first grid point
number.

3.

When selecting grid points in a range using THRU, the default increment
value is 1 if grid numbers are increasing or -1 if grid numbers are decreasing.

4.

With edge-to-surface gluing:

5.

The BLSEG entry is used to define an edge region that can be glued to
the face of solid or shell elements. The BLSEG ID must be entered as the
source region ID on the BGSET bulk entry, and a shell or solid element
face region ID ( BSURF, BSURFS, BCPROP, and BCPROPS) is entered as
the target region ID.

The grid point IDs on the BLSEG entry used to define a glue edge region
can only be part of the CQUAD4, CQUADR, CQUAD8, CTRIA3, CTRIAR
and CTRIA6 element connectivity.

The BWIDTH bulk entry is ignored.

With slideline contact:

A corresponding BWlDTH Bulk Data entry may be required to define the

width/thickness of each line segment. If the corresponding BWlDTH is not
present, the width/thickness for each line segment is assumed to be unity.

Each line segment has a width in a 3-D slideline and a thickness in a 2-D
slideline contact to calculate contact stresses. The width/thickness of each
line segment is defined via the BWIDTH Bulk Data entry. The ID in BLSEG
must be same as the ID specified in the BWIDTH. That is, there must be a
one to one correspondence between BLSEG and BWIDTH. BWIDTH Bulk
Data entry may be omitted only if the width/thickness of each segment is
unity.

The normal to the segment is determined by the cross product of the

slideline plane vector (i.e., the Z direction of the coordinate system defined in
the ClD field of the BCONP Bulk Data entry) and the tangential direction

98

Solid element property regions

of the segment. The tangential direction is the direction from node 1 to
node 2 of the line segment.
Remarks related to SOL 601 edge contact:
1.

BLSEG defines a flexible or rigid 2D contact region on axisymmetric elements

CQUADX4, CQUADX8, CTRAX3 and CTRAX6, plane stress elements CPLSTS3,
CPLSTS4, CPLSTS6 and CPLSTS8, plane strain elements CPLSTN3,
CPLSTN4, CPLSTN6 and CPLSTN8, or a rigid 2D contact target region when
the grid points are not attached to any elements.

2.

The grid points in a BLSEG entry must either be all attached to elements or
all not attached to elements.

3.

For a rigid target region, it is important to note that the top surface is on the
left side of the line from Gi to Gi+1. By default, contact is expected to occur
from the top surface. SURF=BOT in BCRPARA entry may be used to change
the contact side.

4.

Grid points in BLSEG entry must lie in the basic XZ plane.

5.

The BWIDTH bulk entry is ignored.

6.

Contact set pairs are defined by BCTSET entry instead of BCONP entry.

7.

Contact region properties are defined by BCRPARA entry and contact set
properties are defined by BCTPARA entry in a similar way as for 3-D contact. In
addition, global contact settings may be specified in the NXSTRAT entry.

Solid element property regions

The new BCPROPS bulk entry is available to create solid element contact and
glue regions by property ID (PSOLID bulk entry ID). The BCPROPS entry works
similar to the supported BCPROP bulk entry which is used to create shell element
contact and glue regions by property ID (PSHELL bulk entry ID). Only the solid
element free faces are considered in the contact and glue algorithm. The free faces
are automatically determined by the software.
See the BCPROPS bulk entry.

Chapter

Bolt Preload

Combining and scaling bolt preload forces

NX Nastran allows for direct entry of bolt preload forces. When you use this
functionality, the input file must contain:

BOLT bulk entries to select CBEAM and CBAR elements to treat as bolts.

BOLTFOR bulk entries to define bolt preload forces and assign them to the
bolts defined by BOLT bulk entries.

BOLTLD case control commands to select BOLTFOR bulk entries to include

in either the global case or subcases.

Beginning with NX Nastran 7.1, the new BOLTLD bulk entry is available for
use in conjunction with the existing bolt preload procedure. The BOLTLD bulk
entry provides flexibility in defining combinations of bolts and bolt preload forces
to include in the global case or subcases. It also provides a means to scale bolt
preload forces.
When you use the BOLTLD bulk entry, the input file must contain:

BOLT bulk entries to select CBEAM and CBAR elements to treat as bolts.

BOLTFOR bulk entries to define bolt preload forces and assign them to the
bolts defined by BOLT bulk entries.

BOLTLD bulk entries to define combinations of BOLTFOR bulk entries and

scale the corresponding bolt preload forces.

BOLTLD case control commands to select BOLTLD bulk entries to include

in either the global case or subcases.

You can also have an input file where some BOLTLD case control commands select
BOLTLD bulk entries and some BOLTLD case control commands select BOLTFOR
bulk entries. In this case, if the set identification number (SID) referenced by
a BOLTLD case control command exists on both a BOLTLD bulk entry and
BOLTFOR bulk entries, the BOLTLD bulk entry is selected.

100

Combining and scaling bolt preload forces

The use of the BOLTLD bulk entry is optional. In the absence of BOLTLD bulk
entries, the pre-NX Nastran 7.1 bolt preload procedure is still valid.
For more information regarding bolt preload, see the Applied Loads chapter of the
NX Nastran 7.0 Users Guide.

Bolt preload example

A structure contains two bolts. One bolt has a M10 x 1.5 thread and the other has
a M20 x 2.5 thread. Both bolts are modeled using CBAR elements. Four subcases
are considered:

Bolt preload forces at 70% of proof strength and the service loads excluded.

Bolt preload forces at 70% of proof strength and the service loads included.

Bolt preload forces at 80% of proof strength and the service loads excluded.

Bolt preload forces at 80% of proof strength and the service loads included.

The following table contains bolt and proof strength data for use in the model. The
equivalent radius is calculated from the tensile stress area.

Bolt size

Grade

M10 x 1.5

5.8

M20 x 2.5

5.8

Preload Preload Preload

Tensile
force at force at force at
Equivalent Proof
stress
70% of 80% of
100%
radius strength
area
proof
proof
of proof
(mm)
(MPa)
(mm2)
strength strength strength
(kN)
(kN)
(kN)
58
4.30
380
15.4
17.6
22.0
245

8.83

380

65.2

74.5

93.1

Three input files are provided that model this situation:

The first input file does not include the new BOLTLD bulk entry. In this
case, the BOLTLD case control commands select the BOLTFOR bulk entries
having the same SID.

The second input file includes BOLTLD bulk entries. In this case, the BOLTLD
case control commands select the BOLTLD bulk entries having the same SID.

The third input file demonstrates how both BOLTLD bulk entries and
BOLTFOR bulk entries can be selected by BOLTLD case control commands in
the same input file. In this case, the BOLTLD case control commands in two
subcases select a BOLTLD bulk entry and the BOLTLD case control commands
in the other two subcases select BOLTFOR bulk entries.

Combining and scaling bolt preload forces

101

Input file without BOLTLD bulk entries

SOL 101
$
SUBCASES
$
SUBCASE = 1
SUBTITLE
BOLTLD = 1
$
SUBCASE = 2
SUBTITLE
BOLTLD = 1
LOAD = 1
$
SUBCASE = 3
SUBTITLE
BOLTLD = 2
$
SUBCASE = 4
SUBTITLE
BOLTLD = 2
LOAD = 1
$
BEGIN BULK

= Bolt preload force at 70% of proof strength without service loads

= Bolt preload force at 70% of proof strength with service loads

= Bolt preload force at 80% of proof strength without service loads

= Bolt preload force at 80% of proof strength with service loads

CBAR
2237
2
CBAR
2238
3
$
$
BOLT ENTRIES
$
BOLT
1
1
BOLT
2
1
$
$
BOLT PRELOAD ENTRIES
$
BOLTFOR
1 15.4+3
BOLTFOR
1 65.2+3
BOLTFOR
2 17.6+3
BOLTFOR
2 74.5+3
ENDDATA

8001
8003

2237
2238

1
2
1
2

8000
8002

1.0
1.0

0.0
0.0

0.0
0.0

102

Combining and scaling bolt preload forces

Input file with BOLTLD bulk entries
SOL 101
$
SUBCASES
$
SUBCASE = 1
SUBTITLE
= Bolt preload force
BOLTLD = 1
$
SUBCASE = 2
SUBTITLE
= Bolt preload force
BOLTLD = 1
LOAD = 1
$
SUBCASE = 3
SUBTITLE
= Bolt preload force
BOLTLD = 2
$
SUBCASE = 4
SUBTITLE
= Bolt preload force
BOLTLD = 2
LOAD = 1
$
BEGIN BULK
........
........
CBAR
2237
2
8001
CBAR
2238
3
8003
$
$
BOLT ENTRIES
$
BOLT
1
1
2237
BOLT
2
1
2238
$
$
BOLT PRELOAD ENTRIES
$
BOLTFOR
1 22.0+3
1
BOLTFOR
2 93.1+3
2
$
$
SCALE BOLT PRELOAD ENTRIES
$
BOLTLD
1
0.70
1.0
BOLTLD
2
0.80
1.0
ENDDATA

at 70% of proof strength without service loads

at 70% of proof strength with service loads

at 80% of proof strength without service loads

at 80% of proof strength with service loads

8000
8002

1.0
1.0

0.0
0.0

1
1

1.0
1.0

2
2

0.0
0.0

Combining and scaling bolt preload forces

103

Input file with BOLTLD case control commands selecting both BOLTLD and
BOLTFOR bulk entries
SOL 101
$
SUBCASES
$
SUBCASE = 1
SUBTITLE
BOLTLD = 1
$
SUBCASE = 2
SUBTITLE
BOLTLD = 1
LOAD = 1
$
SUBCASE = 3
SUBTITLE
BOLTLD = 2
$
SUBCASE = 4
SUBTITLE
BOLTLD = 2
LOAD = 1
$
BEGIN BULK

= Bolt preload force at 70% of proof strength without service loads

= Bolt preload force at 70% of proof strength with service loads

= Bolt preload force at 80% of proof strength without service loads

= Bolt preload force at 80% of proof strength with service loads

CBAR
2237
2
8001
CBAR
2238
3
8003
$
$
BOLT ENTRIES
$
BOLT
1
1
2237
BOLT
2
1
2238
$
$
BOLT PRELOAD ENTRIES
$
BOLTFOR
2 17.6+3
1
BOLTFOR
2 74.5+3
2
BOLTFOR
3 22.0+3
1
BOLTFOR
3 93.1+3
2
$
$
SCALE BOLT PRELOAD ENTRIES
$
BOLTLD
1
0.70
1.0
ENDDATA

8000
8002

1.0
1.0

0.0
0.0

0.0
0.0

104

BOLTFOR
Preload Force on Set of Bolts

BOLTFOR

Preload Force on Set of Bolts

Defines preload force for a set of bolts.

Format:
1

BOLTFOR

SID

LOAD

B1

B2

B3

B4

B5

B6

B7

THRU

B8

B9

B10

-etc-

1000.0

12

THRU

21

10

26

32

34

37

43

51

10

Example:
BOLTFOR

Fields:
Field

Contents

SID

Set identification number (SID) of BOLTFOR bulk entry. (Integer>0)

LOAD

Magnitude of the preload force. (Real)

Bi

Bolt identification numbers (BID) defined by BOLT bulk entries.

(Integer>0 or use THRU option. For THRU option, B7<B8)

Remarks:
1.

Multiple BOLTFOR entries having the same SID can be used and the data will
be combined.

2.

If the SID referenced by a BOLTLD case control command is present on both a

BOLTLD bulk entry and BOLTFOR bulk entries, the BOLTLD bulk entry takes
precedence and is selected. The BOLTFOR bulk entries that are not selected can
optionally be included in the subcase by listing their SID in one of the Li fields
on the BOLTLD bulk entry.

3.

Repeated BID in a subcase is not allowed. A repeated BID occurs when:

A BID is included more than once on a BOLTFOR bulk entry.

A BID is included on multiple BOLTFOR bulk entries having the same SID.

BOLTFOR

105

Preload Force on Set of Bolts

A BID is included on multiple BOLTFOR bulk entries having different SID,

but referenced by the same BOLTLD bulk entry.

106

BOLTLD (bulk entry)

Bolt preload combining and scaling

BOLTLD (bulk entry)

Bolt preload combining and scaling

Combines sets of bolts defined by BOLTFOR bulk entries and optionally scales the
corresponding bolt preload forces.
Format:
1

BOLTLD

SID
S4

S1

L1

S2

L2

S3

L3

L4

-etc-

101

0.5

1.0

6.2

10

Example:
BOLTLD

Fields:

Field

Contents

SID

Set identification number (SID) of BOLTLD bulk entry. (Integer>0)

Overall scale factor. (Real)

Si

Scale factor for individual Li. (Real)

Li

SID of BOLTFOR bulk entries. (Integer>0)

Remarks:
1.

The applied preload value Pi for each BOLT bulk entry referenced by BOLTFOR
bulk entry Li is given by:
Pi = S * Si * PLi
where PLi is the preload value defined for BOLTFOR bulk entry Li, Si is the
individual scale factor corresponding to Li, and S is the overall scale factor.

2.

Li must be unique. However, a single Li on a BOLTLD bulk entry can reference

multiple BOLTFOR bulk entries. When this occurs, all the preload forces
defined by the BOLTFOR bulk entries sharing the same SID are scaled by the
corresponding individual scale factor Si and the overall scale factor S.

BOLTLD (bulk entry)

107

Bolt preload combining and scaling

3.

The bolt identification numbers (BID) in all BOLTFOR bulk entries selected by a
single BOLTLD bulk entry must be unique.

4.

The SID of each BOLTLD bulk entry must be unique.

108

BOLTLD (case control)

Bolt Preload Set Selection

BOLTLD (case control)

Bolt Preload Set Selection

Selects either a BOLTLD bulk entry or BOLTFOR bulk entries for bolt preload
processing.
Format:
BOLTLD=n
Examples:
BOLTLD=5

Describers:
Describer

Meaning

Set identification number (SID) of a BOLTLD bulk entry or

BOLTFOR bulk entries. See Remark 2. (Integer>0)

Remarks:
1.

Bolt preload is supported in SOLs 101, 103, 105, 107 through 112, and 601.

2.

If the SID referenced by a BOLTLD case control command exists on both a

BOLTLD bulk entry and BOLTFOR bulk entries, the BOLTLD bulk entry is
selected.

3.

Subcases without BOLTLD case control commands should be placed at either

the beginning or end of the subcases.

4.

For the special case where the sparse solver is used, the model does not contain
contact, and the keyword scratch = yes, BOLTLD case control commands in the
subcases must be ordered. For example, if a model contains three subcases with
BOLTLD = 1 used twice and BOLTLD = 2 used once, the BOLTLD case control
commands should be ordered with:

The first and second subcases containing BOLTLD = 1 and the third subcase
containing BOLTLD = 2.

The first subcase containing BOLTLD = 2 and the second and third subcases
containing BOLTLD = 1.

If the iterative solver is used or contact is used or the keyword scratch = no,
ordering the subcases in this way is not necessary, but is recommended. Doing so
minimizes the number of matrix decompositions required during the solution.

Bolt preload with contact definitions

109

5.

Superelements with preloaded bolts are allowed. However, the elements used to
define the bolts along with the bolt preload forces must be in the residual.

6.

For dynamic solution sequences, a static subcase containing the BOLTLD case
control command must be referenced by a STATSUB case control command.

Bolt preload with contact definitions

When a bolt preload definition exists, a two solution process occurs:
1.

Preload Solution
The elements representing the bolts are reduced in stiffness, the bolt preloads
are applied, and a linear statics solution runs.

2.

Final Solution
The bolt strains determined from the preload solution plus the service loads
are applied, and the final linear statics solution runs.

When a contact definition exists in the bolt preload process, the contact conditions
are included in both the preload and final solutions. To decrease the solution time,
now the final solution begins with the contact status from the end of the preload
solution. As a result, the contact element creation steps and some of the initial
contact iterations are avoided in the final solution.
Models that include bolt preload and contact definitions could produce slightly
different results relative to previous releases, especially if the number of contact
changes at convergence is not close to zero.

Bolt stiffness update

During the bolt preload solution process, the elements representing the bolts are
reduced in stiffness and the bolt preloads are applied. Previously the bolt stiffness
was decreased by BOLTFACT in all degrees-of-freedom (DOF). A problem when
reducing the stiffness in all DOF is that if sliding occurs, the preload results are
unpredictable. Beginning in NX Nastran 7.1, only the axial stiffness is decreased
and the other five DOF remain unchanged.

Chapter

Optimization

Best design cycle

The SOL 200 optimization process adjusts design variables as it searches for
the optimum conditions while it works in the domain of the constraints and the
objective. At specific times in this solution process, the FE model is updated
with the current values of the design variables, and a finite element analysis is
requested. Such analysis results are used to update the optimization algorithm
with current design responses and their gradients. Each loop through a finite
element analysis, a sensitivity analysis, a solution of the generated optimization
problem, and design updating in the SOL 200 process is considered a design cycle.
The .f06 file reports the design variables, constraints, responses, and the objective
for each design cycle in which output is requested. By default, the initial
and final design cycles are reported, but you can request output for all using
PARAM,NASPRT,1.
The design variables, the value of the objective, and the most critical constraint
value for the final design cycle do not necessarily reflect the best design, while
often this may be the case. In previous releases, finding the design cycle which best
satisfies the constraints and objective was a manual process. You had to consider
the design responses from many design cycles.
Now the best design cycle is automatically determined by the SOL 200 process.
An arrow points to the best design in the Summary of Design Cycle History
table in the .f06 output file. In addition, the best design cycle is indicated under
the table heading.
The following example .f06 output for an objective function maximization job
demonstrates this enhancement.
Note that the best design in this example is consistent with Remark 9 on the
DESOBJ case control command, except that the highest value among the feasible
objectives has been selected because this is a maximization problem.

112

Updated bulk data output

***************************************************************
S U M M A R Y
O F
D E S I G N
C Y C L E
H I S T O R Y
***************************************************************
NUMBER OF FINITE ELEMENT ANALYSES COMPLETED
NUMBER OF OPTIMIZATIONS W.R.T. APPROXIMATE MODELS

11
10

OBJECTIVE AND MAXIMUM CONSTRAINT HISTORY

***(Best Design Found At Cycle
6)***
---------------------------------------------------------------------------------------OBJECTIVE FROM OBJECTIVE FROM
FRACTIONAL ERROR MAXIMUM VALUE
CYCLE
APPROXIMATE
EXACT
OF
OF
NUMBER
OPTIMIZATION
ANALYSIS
APPROXIMATION
CONSTRAINT
---------------------------------------------------------------------------------------INITIAL
1.519072E+05
1.236165E+01
1
1.461574E+05
1.295791E+05
1.279397E-01
4.037928E-01
2
1.212510E+05
1.205930E+05
5.455981E-03
2.678087E-02
3
1.146383E+05
1.123581E+05
2.029436E-02
7.671907E-01
4
1.123708E+05
1.118530E+05
4.629403E-03
-4.006884E-02
5
1.103805E+05
1.103248E+05
5.053970E-04
8.832471E-01
6
1.123653E+05
1.123211E+05
3.942382E-04
-4.216779E-02<<== BEST DESIGN
7
1.119073E+05
1.117819E+05
1.122373E-03
-5.640221E-02
8
1.085288E+05
1.084036E+05
1.154684E-03
-1.635617E-02
9
1.081977E+05
1.081934E+05
3.928151E-05
-4.287751E-02
10
1.076919E+05
1.076685E+05
2.173193E-04
-4.717002E-02
----------------------------------------------------------------------------------------

Updated bulk data output

The optimization algorithm adjusts your design variables while searching for
optimum values. At the end of a successful optimization solution, you may want
to update the complete bulk data with the new design variables as well as with
any other design variable dependent data that will have changed in order to run
some relevant analysis or to continue with the optimization. NX Nastran now
automates this step for you.
You can now request the complete, updated bulk data output. The new bulk data,
which is written to the punch file, will match your original except that it will
contain updated design variables, related properties, grid point data for shape
optimization, and when mode tracking is requested, eigenvalue DRESP1 data for
the design cycle for which the bulk data is written. You can merge this entire
new bulk data containing the updated bulk data with the other components of a
relevant input file for any consecutive solution.
The existing ECHO case control command is used to make the request. The new
option ECHO=PUNCH(BSTBULK) is used to output the bulk data for the best
design cycle, or ECHO=PUNCH(NEWBULK) to output the bulk data for the
last design cycle. Often the last design cycle and the best design cycle coincide.
However, BSTBULK is useful for cases where the best design cycle is actually an

Updated bulk data output

113

earlier cycle. In contrast, NEWBULK may be useful when you know that the job
will be continued later starting from the last design cycle.

114

ECHO
Bulk Data Echo Request

ECHO

Bulk Data Echo Request

Controls echo (i.e., printout) of the Bulk Data.

Format:

Examples:
ECHO=NOSORT
ECHO=BOTH
ECHO=PUNCH,SORT(MAT1,PARAM)
ECHO=SORT(EXCEPT DMI,DMIG)
ECHO=PUNCH(BSTBULK)
ECHO=PUNCH(NEWBULK)
ECHO=SORT,PUNCH(BSTBULK)

Describers:
Describer

Meaning

UNSORT

The unsorted Bulk Data will be printed. If SORT is also not

specified then the sorted Bulk Data will not be printed.

SORT

The sorted (arranged in alphanumeric order) Bulk Data will

be printed.

NOSORT

The sorted Bulk Data will not be printed. If UNSORT is also not
specified then the unsorted Bulk Data will not be printed.

cdni,...

Bulk Data entry names to be included or excluded by EXCEPT, in

the sorted echo printout. The PUNCH file is not affected by cdni.

EXCEPT

Exclude cdni Bulk Data entries from sorted echo printout. See
Remark 6.

BOTH

Both sorted and unsorted Bulk Data will be printed. This is

equivalent to ECHO=SORT, UNSORT.

NONE

Neither sorted nor unsorted Bulk Data will be printed.

ECHO

115

Bulk Data Echo Request

Describer

Meaning

PUNCH

The entire Bulk Data will be written to the punch file in sorted
form.

BSTBULK

For SOL 200 design optimization runs, an unsorted updated

bulk data file will be written to the punch file, using the updated
design variables and properties as well as any mode-tracked
eigenvalue DRESP1 (i.e. the updated design data) for the BEST
design cycle obtained and indicated in the SOL 200 run. See
Remark 7.

NEWBULK

For SOL 200 design optimization runs, an unsorted updated

bulk data file will be written to the punch file, using the updated
design variables and properties as well as any mode-tracked
eigenvalue DRESP1 (i.e. the updated design data) for the LAST
design cycle obtained and indicated in the SOL 200 run. See
Remark 7.

Remarks:
1.

If no ECHO command appears, a sorted Bulk Data will be printed.

2.

Comments will appear at the front of the sorted file if ECHO=PUNCH.

3.

Portions of the unsorted Bulk Data can be selectively echoed by including the
commands ECHOON and ECHOOFF at various places within the Bulk Data.
ECHOOFF stops the unsorted echo until an ECHOON command is encountered.
Many such pairs of commands may be used. The ECHOON and ECHOOFF
commands may be used in the Executive and Case Control Sections; however,
ECHOOF should not be the first entry as continuation entries will not be
handled correctly.

4.

If the SORT (cdni,...) is specified in a restart in SOLs 101 through 200, then the
continuation entries will not be printed.

5.

If the SORT (cdni,...) describer is used, then it must appear as the last describer,
as in the example above.

6.

If EXCEPT is specified then it must be specified before all cdni. All Bulk Data
entry types will be listed except those given for cdn1, cdn2, etc. If EXCEPT is
not specified, then only those Bulk Data entry types listed under cdn1, cdn2,
etc. will be listed.

116

PCOMPG support
7.

For SOL 200, often the last design cycle and the best design cycle coincide.
However, BSTBULK is useful for cases where the best design cycle is actually an
earlier cycle. In contrast, NEWBULK may be useful when the user knows that
the job will be continued later starting from the last design cycle.

PCOMPG support
The PCOMPG bulk entry was introduced in NX Nastran 7 to define a different
number of shell composite layers and a different ply order on adjacent elements.
The composite properties defined with the PCOMPG entry can now be included as
design variables in a SOL 200 optimization or sensitivity analysis.
The design variable inputs for the PCOMPG entry, which are the same as for the
PCOMP entry, are defined with the DVPREL1 or DVPREL2 bulk entries.
The following tables list the DVPREL1 and PCOMPG bulk entries input formats:
1

DVPREL1

ID

TYPE

PID

PNAME/FID

PMIN

PMAX

C0

DVID1

COEF1

DVID2

COEF2

DVID3

-etc.-

1
PCOMPG

TREF

GE

LAM

PID

Z0

NSM

SB

FT

GPLYID1

MID1

T1

THETA1

SOUT1

GPLYID2

MID2

T2

THETA2

SOUT2

10

10

To define a DVPREL1 property relation input for the PCOMPG entry, TYPE
should be PCOMPG, PID should be assigned to the PCOMPG property ID,
and PNAME/FID can refer to any of the PCOMPG field names or numbers. For
example, entering either THETA1 or 15 will both define the same PCOMPG
field position.
The input example below represents four PCOMPG design variable/relations:
THETA1 (field number 15), THETA2 (field number 25), THETA3 (field number
35), and THETA4 (field number 40).

PSHELL structural damping support

....
PCOMPG
+
+
+
+
+
+
+
+

1
101
102
103
104
105
106
107
108

1
1
1
1
1
1
1
1

0.
1.E-4
1.E-4
1.E-4
1.E-4
1.E-4
1.E-4
1.E-4
1.E-4

8.E+7
0.
90.
45.
45.
45.
45.
90.
0.

HOFF
YES
YES
YES
YES
YES
YES
YES
YES

117

+
+
+
+
+
+
+
+

....
DVPREL1,5,PCOMPG,1,15,,,,,+
+,5,1.0
DVPREL1,6,PCOMPG,1,25,,,,,+
+,6,1.0
DVPREL1,7,PCOMPG,1,35,,,,,+
+,7,1.0
DVPREL1,8,PCOMPG,1,40,,,,,+
+,8,1.0
....
DESVAR,5,THETA1,1.0,1.0,90.0
DESVAR,6,THETA2,1.0,1.0,90.0
DESVAR,7,THETA3,1.0,1.0,90.0
DESVAR,8,THETA4,1.0,1.0,90.0

PSHELL structural damping support

You can select a different material on the PSHELL bulk entry for membrane
(MID1), bending (MID2), transverse shear (MID3), and membrane-bending
coupling (MID4). You can now also include the structure damping value from each
of these materials as design variables in a SOL 200 optimization or sensitivity
analysis. The DVMREL1 or DVMREL2 bulk entries define the material/variable
relations.
The parameter input PARAM,SHLDAMP,DIFF is required to use the capability:
When PARAM,SHLDAMP = SAME (default), the structural damping coefficient
(GE) defined on a PSHELL MID1 material will be used by all MIDi for that
PSHELL.
When PARAM,SHLDAMP = DIFF, the structural damping coefficient (GE) defined
on each PSHELL MIDi will be used. Any structural damping coefficient (GE)
values which are blank default to zero.

118

PBUSH structural damping support

PBUSH structural damping support

The PBUSH bulk entry includes the fields GE1, GE2, GE3, GE4, GE5, and GE6 to
define structural damping for each degree-of-freedom.
You can now include these fields as design variables in a SOL 200 optimization
or sensitivity analysis. The DVPREL1 or DVPREL2 bulk entries define the
property/variable relations.
The parameter input PARAM,BSHDAMP is not required to turn on the
capability since the default value DIFF includes the fields GE2-GE6. When
PARAM,BSHDAMP,SAME is defined, the fields GE2-GE6 are ignored, and only
fields GE1 are considered.
Note: When you use any of the GE2-GE6 fields, it is important to fully define
all degrees-of-freedom deemed critical to the result, because a blank field will
default to a zero value.

Additional enhancements
Alternate optimizer update
The alternate optimizer developed by Siemens PLM has been updated with several
improvements. The enhancements include better quality of results in general due
to algorithmic improvements and some improvement in the use of memory.
A major modification involves the normalization of constraints for purposes of this
optimizer. Now when you select the alternate optimizer, a true normalization is
performed, and the normalized constraint values always vary between -1.0 and
+1.0 in a symmetric manner. Due to the method of normalization employed with
the use of this optimizer, you do not need to account for a small denominator. Note
that the Maximum Value of Constraint column in the Summary of Design Cycle
History table in the f06 file will also contain different values based on which
optimizer is selected.
The normalization for the alternate optimizer follows the expressions below.
If a bound is sandwiched between zero and r:
g=(LALLOWr) / |r|

or

g=(rUALLOW) / |r|

Otherwise:
g=(LALLOWr) / |2*LALLOWr|

or

g=(rUALLOW) / |2*UALLOWr|

The only special case gives a constraint value of 0.0, thus no difficulties arise
with a zero denominator.
The constraint normalization for the DOT optimizer remains the same as before.

Additional enhancements

119

The alternate optimizer is selected with the system cell 425 (ADSOPT):
NASTRAN SYSTEM(425) = 1 -or- NASTRAN ADSOPT = 1
The DOT optimizer remains the default for NX Nastran 7.1:
NASTRAN SYSTEM(425) = 0 (default)
DRSPAN update
When the DRSPAN case control command was introduced with NX Nastran 6.0,
it was noted that it was not available for use with superelements (see the NX
Nastran 6.0 Release Guide). With NX Nastran 7.1, the DRSPAN command now
can be used with superelements, as long as all DRESP1 responses in a DRSPAN
related DRESP2 or DRESP3 are from the same superelement.

Chapter

New materials

3-D orthotropic materials

The new MAT11 and MATT11 bulk entries are available to define a 3-D orthotropic
material definition. The new materials can be used by the CHEXA, CPENTA,
CPYRAM, and CTETRA element types, and are selected with the MID field on the
PSOLID bulk entry. They are supported in all solutions except SOL 601 and 701.
Although you can include the MAT11 and MATT11 bulk entries in SOL 200, they
cannot be used as design variables by the DVMREL1 and DVMREL2 bulk entries.

122

MAT11
Solid Element Orthotropic Material Property Definition

MAT11

Solid Element Orthotropic Material Property Definition

Defines the material properties for a 3-D orthotropic material for isoparametric
solid elements.
Format:
1
MAT11

MID

E1

E2

E3

NU12

NU13

NU23

G12

G13

G23

RHO

A1

A2

A3

TREF

GE

101

2.1E7

2.2E7

2.3E7

0.31

0.29

0.33

2.1E6

2.2E6

2.3E6

0.34

0.35

0.36

0.37

0.38

0.39

10

Example:
MAT11

Fields:
Field

Contents

MID

Material identification number. (Integer > 0)

E1

Modulus of elasticity in longitudinal direction, also defined as the

fiber direction or 1-direction. (Real > 0.0; no default, must be defined)

E2

Modulus of elasticity in lateral direction, also defined as the matrix

direction or 2-direction. (Real > 0.0; no default, must be defined)

E3

Modulus of elasticity in ply layup direction, also defined as the

thickness direction or 3-direction. (Real > 0.0; no default, must be
defined)

NU12

Poissons ratio (2/1 for uniaxial loading in 1-direction). Note that

NU21=1/2 for uniaxial loading in 2-direction is related to NU12, E1,
and E2 by the relation NU12*E2=NU21*E1. (Real > 0.0; no default,
must be defined)

NU13

Poissons ratio (3/1 for uniaxial loading in 1-direction). Note that

NU31=1/3 for uniaxial loading in 3-direction is related to NU13, E3,
and E1 by the relation NU31*E1=NU13*E3. (Real > 0.0; no default,
must be defined)

MAT11

123

Solid Element Orthotropic Material Property Definition

Field

Contents

NU23

Poissons ratio (3/2 for uniaxial loading in 2-direction). Note that

NU32=2/3 for uniaxial loading in 3-direction is related to NU23, E2,
and E3 by the relation NU23*E3=NU32*E2. (Real > 0.0; no default,
must be defined)

G12

Shear modulus in plane 1-2. (Real > 0.0; no default, must be defined)

G13

Transverse shear modulus in shear in 1-3 plane. (Real > 0.0; no

default, must be defined)

G23

Transverse shear modulus in shear in 2-3 plane. (Real > 0.0; no

default, must be defined)

RHO

Mass density. (Real or blank; Default = 0.0)

A1

Thermal expansion coefficient in longitudinal direction. (Real or

blank; Default = 0.0)

A2

Thermal expansion coefficient in lateral direction. (Real or blank;

Default = 0.0)

A3

Thermal expansion coefficient in thickness direction. (Real or blank;

Default = 0.0)

TREF

Reference temperature for the calculation of thermal loads, or a

temperature-dependent thermal expansion coefficient. (Real or
blank; Default = 0.0)

GE

Structural damping coefficient. (Real or blank; Default = 0.0)

Remarks:
1.

In general, NU12 is not the same as NU21, but they are related by NUij/Ei
= NUji/Ej. Furthermore, material stability requires that Ei > NUij2Ej and
1-NU12NU21-NU23NU32-NU31NU13-2NU21NU32NU13 > 0.0.

2.

MAT11 materials may be made temperature dependent by use of the MATT11

entry.

3.

MAT11 entries cannot be used as design variables in SOL 200 (via the
DVMREL1 and DVMREL2 bulk entries).

124

MATT11
Solid Orthotropic Material Temperature Dependence

MATT11

Solid Orthotropic Material Temperature Dependence

Defines the temperature dependent material property for a 3-D orthotropic material
for isoparametric solid elements.
Format:
1

MATT11

MID

T(E1)

T(E2)

T(E3)

T(G13)

T(G23)

T(RHO)

T(A1)

20

10

T(NU12) T(NU13) T(NU23)

T(A2)

T(A3)

10

T(G12)
T(GE)

Example:
MATT11

11

Fields:
Field

Contents

MID

Material property identification number that matches the

identification number on MAT11 entry. (Integer > 0)

T(E1)

Identification number of a TABLEMi entry for Youngs modulus

1. (Integer 0 or blank)

T(E2)

Identification number of a TABLEMi entry for Youngs modulus

2. (Integer 0 or blank)

T(E3)

Identification number of a TABLEMi entry for Youngs modulus

3. (Integer 0 or blank)

T(NU12)

Identification number of a TABLEMi entry for Poissons ratio 12.

(Integer 0 or blank)

T(NU13)

Identification number of a TABLEMi entry for Poissons ratio 13.

(Integer 0 or blank)

T(NU23)

Identification number of a TABLEMi entry for Poissons ratio 23.

(Integer 0 or blank)

T(G12)

Identification number of a TABLEMi entry for shear modulus 12.

(Integer 0 or blank)

MATT11

125

Solid Orthotropic Material Temperature Dependence

Field

Contents

T(G13)

Identification number of a TABLEMi entry for shear modulus 13.

(Integer 0 or blank)

T(G23)

Identification number of a TABLEMi entry for shear modulus 23.

(Integer 0 or blank)

T(RHO)

Identification number of a TABLEMi entry for mass density.

(Integer 0 or blank)

T(A1)

Identification number of a TABLEMi entry for thermal expansion

coefficient 1 in 1-direction. (Integer 0 or blank)

T(A2)

Identification number of a TABLEMi entry for thermal expansion

coefficient 2 in 2-direction. (Integer 0 or blank)

T(A3)

Identification number of a TABLEMi entry for thermal expansion

coefficient 2 in 3-direction. (Integer 0 or blank)

T(GE)

Identification number of a TABLEMi entry for structural damping

coefficient. (Integer 0 or blank)

Remarks:
1.

Fields 3, 4, etc., of this entry correspond, field-by-field, to fields 3, 4, etc., of

the MAT11 entry referenced in field 2. The value in a particular field of the
MAT11 entry is replaced or modified by the table referenced in the corresponding
field of this entry. In the example shown, E1 is modified by TABLEMi 10 and
A1 is modified by TABLEMi 11. Blank or zero entries mean that there is no
temperature dependence of the fields on the MAT11 entry.

2.

Any quantity modified by this entry must have a value on the MAT11 entry.

Chapter

Element enhancements

Solid element support in solutions 106 and 129

The CPYRAM solid pyramid element now supports geometry nonlinear conditions
in solutions 106 and 129. Previously, the CPYRAM element behaved linearly in
these solutions.
In addition, the variable grid CHEXA, CPENTA elements now support geometry
nonlinear conditions in solutions 106 and 129. These previously behaved linearly
in these solutions.
The following table summarizes the solid element support in solutions 106 and 129.
Table 9-1. SOL 106 and 129 Solid Element Support
Element

CHEXA
CTETRA
CPENTA
CPYRAM

Material Nonlinear Conditions

Plasticity,
Hyperelastic
Nonlinear Elastic,
Creep

Number of
Grids

Geometry
Nonlinear
Conditions

9 20
4

X (new)
X

5 10

7 15

X (new)

5
6 13

X (new)
X (new)

X
X

128

Shell element material coordinate tolerance

Shell element material coordinate tolerance

The MCID field on the shell elements CTRIA3, CTRIA6, CTRIAR, CQUAD4,
CQUAD8, and CQUADR selects a material coordinate system. The X-direction
of the material coordinate system is projected onto the face of the shell element
to determine the material X-direction.

If the X-direction of a material coordinate system is perpendicular or very close

to being perpendicular to the element face, a projection is either impossible or
unpredictable.
The new system cell 489 is now available to adjust the perpendicularity angle
tolerance for shell element material orientations. A fatal error will occur when the
angle between a shell element face normal and the X-direction of the material
coordinate system (MCID) is less than the value of SYSTEM(489). The default
is 1.0E-8 degrees.

Shell element thickness check

A more rigorous shell element thickness check now exists. A fatal error occurs
if a Ti value of 0.0 exists on any of the elements CTRIA3, CTRIA6, CTRIAR,
CQUAD4, CQUAR8, CQUADR, CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8.
The system cell 495 is available to turn the new thickness check off.
If SYSTEM(495) = 0 (default), a fatal error occurs if a thickness value of 0.0
exists on any shell element.
If SYSTEM(495) = 1, the new thickness check is turned off.

CPYRAM in acoustics

129

CPYRAM in acoustics
The pyramid element CPYRAM can now be included in acoustic models. You
can use these models to perform fully coupled fluid-structure analysis. Common
applications are acoustic and noise control analysis; for example, in the passenger
compartments of automobiles. The pyramid can be included as part of either the
fluid or structure, and is permitted at the interface regions where fluid-structure
coupling occurs.

Chapter

10 DMP improvements

Multilevel RDMODES enhancement

The multi-level Recursive Domain Lanczos method (RDMODES) was introduced
in NX Nastran 6.1 for very large scale normal modes solutions. In NX Nastran 7,
RDMODES was enabled for the frequency response solutions (SOL 111) including
coupled acoustics problems. In addition, a new sparse eigenvector recovery option
was added.
RDMODES includes the following enhancements in this release.

The performance of RDMODES is enhanced in the partition phase. The

RDMODES partitioning modification improves performance for multilevel
RDMODES applications, especially with large nrec values. No additional
inputs are required.

You can now include superelements with an RDMODES modal analysis. This
DMP superelement feature improves performance by allowing RDMODES to
be used (using the nrec keyword) in a DMP superelement job.

RDMODES with the rdsparse option now supports residual vectors (PARAM,
RESVEC), panel participation factors (PARAM, PANELMP), absolute
displacement enforced motion (sys422=1), and modal contributions. No new
inputs are required.
Note that the accelerated residual vector calculation with RDMODES takes
advantage of the rdsparse option, and is more efficient than the original one
in terms of computational time and I/O usage. The residual vectors with the
accelerated calculation may differ slightly from the original, which cannot be
used in conjunction with rdsparse. If necessary, you can request the original
resvec method by specifying PARAM, RDRESVEC, NO in the bulk data. In
this case, the rdsparse option will be disabled automatically, which is likely to
result in dramatically reduced performance.

Inputs for RDMODES

Multilevel RDMODES is activated by the nastran keywords dmp and nrec:
NASTRAN dmp=p nrec=m

132

GDSTAT method improvement

where p is the number of processors and m is the number of external partitions.
Remarks
1.

The optional keyword rdscale is a factor to modify the selected frequency

range in the EIGRL specification for eigensolutions of each substructure. The
default value of rdscale is 3.5 for multilevel RDMODES.

2.

There is no default value for the nrec keyword.

RDMODES performance case study example

(partitioning performance improvement)

Vehicle model

About 546,000 grid points, 500,000 elements, 3,280,000 degrees of freedom

SOL 111 frequency response analysis

IBM Power 6/4.2GHz workstation

The following table compares multi-level RDMODES runs (parallel=8, nrec=128)

with and without the partitioning improvement.
Partitioning

Elapsed

I/O

min:sec

min:sec

GBytes

3:58

115:01

1828.6

9:05

123:11

1837.5

Method
RDMODES
NXN71
RDMODES
NXN70

With the improvement, it is more than a factor of 2 faster than version 7.0 in
the partitioning phase (4 min vs. 9 min). I/O usage is also reduced. Larger
improvements can be expected when the model and nrec values are large.

GDSTAT method improvement

The GDSTAT method (SOL 101 using geometric domain decomposition and DMP)
in NX Nastran 7 partitioned the model using the SEQP module. Now in NX
Nastran 7.1, two methods are available: using SEQP and using the GPARTN
module. The SEQP method is selected with gpart=0, and GPARTN is selected
with gpart=1 (default).
You can activate this method by the following:

GDSTAT method improvement

133

nastran dmp=n gpart=1

where n denotes the number of processors. gpart=1 is optional since it is the
default.
Remark
The GDSTAT method (gpart=1) can handle solution 101 jobs with CWELD
elements, CFAST elements, and glue conditions. These elements and glue
conditions are not supported in the SEQP method.

Chapter

11 Electromagnetics interface

Overview
NX Nastran 7.1 delivers a new capability for transferring an external force field to
an NX NASTRAN structural load. The new functionality is useful when analyzing
structural components of linear and torque motors. In these applications, the
surface loads from a 3rd party electromagnetic simulation product such as
MAXWELL are integrated into an NX Nastran solution. Responses of the structure
to the combined structural and external electromagnetic field loads are computed.
The external force field is described by 3D force components and their spatial
coordinates. These locations are referred to as external force points. A set of
structural grid points in the vicinity of the external force points are selected to
define a surface patch. NX Nastran transfers the external forces to the grids on the
surface patch using an existing surface spline technique used in the aero-elastic
solutions. The existing structural forces in the model will be augmented with the
equivalent structural forces to execute the analysis.

Inputs
The coupling mechanism may be applied to linear static, normal modes and direct
frequency response solutions in NX Nastran 7.1. The user interface is based on a
new case control entry selection and DMI matrix input.
The availability of external field loads must be indicated by one or more subcases
containing the new case control command
EFLOAD (NDIR=n, SCID=m) = yes/no.
The value n indicates a general surface normal of the surface patch upon which
the external load is applied. The values of n are 1, 2 and 3, indicating a normal
direction of z, y, or x, respectively. In the case of cylindrical local coordinate system
specified by SCID=m, the values of n = 1, 2, or 3 indicate the surface normal
orientation of z, theta, or r. In the cylindrical coordinate case the angles must
be in the 0 to 360 degrees range. In this initial implementation, the cylindrical
coordinate systems origin and z-axis must be consistent with the origin and z-axis
of the basic coordinate system. This restriction will be removed in future versions.

136

Inputs
The short version of the format EFLOAD (NDIR=n) = yes is also allowed, resulting
in everything being in the basic coordinate system. The shortest form of EFLOAD
= yes will use the default value of n=1 and is equivalent to EFLOAD (NDIR=1) =
yes. Finally any form of the EFLOAD command with no on the right hand side
will result in the omission of external field loads.
The same subcase where EFLOAD is applied defines the external load files via
the existing command
P2G = efpoints, efforce
where the files are in standard DMI format with names that you specify. The
efpoints file may contain points in rectangular or cylindrical coordinates, in order
to follow the geometry conveniently. The corresponding efforce file, however,
contains the forces in rectangular components in both cases, in adherence to the
spatial external field solution.
The surface section of the structural model to receive the loads (in the proximity
of, but not necessarily coincident with, the epoints) is defined by the existing
mechanism
SET k = G1, G2, etc
PARTN k
There may be as many subcases with the above content as many external load
surface segments.
The projection of the external solution points, contained in the efpoints file, onto
the structure must fall into the envelope of the designated interface area of the
structure specified by the SET and PARTN mechanism.
Note that the last subcase of any job must not contain external field loads, but only
structural loads (if any) or general output requests. Thus, in the case of only one
external field load surface, there must be two subcases.
Using the statically pre-stressed normal modes capability, you must run a static
solution (SOL101) with EFLOAD to generate the .pch file. The SOL101.pch file
simply needs to be included in the bulk data section of the normal modes restart
run.
The static subcase of the normal modes restart run must contain:
EFLOAD = yes
The normal modes subcase must contain the STATSUB case control word referring
to the subcase with the EFFLOAD keyword. Otherwise the process is as usual
in pre-stressed normal modes.

Example

137

The set-up of the direct frequency response (108) solution is conceptually the same
as the linear static run. The external field loads will constitute the scaling factor
component of the dynamic load.

Example
A cylindrical shell modeled with CQUAD4 elements is constrained along the
bottom edge. The external field loads are applied half way between the top two
rings of nodes at 45degree increments around the perimeter. The loads include
FX and FZ of 100.0 units applied in the basic coordinate system at each location.
The grids shown in the partial model below define the surface patch.

The relevant components of the input file are:

Case Control
....
SUBCASE 1
$
$SET selects the grids for the surface patch
SET 1 = 1 thru 8, 44 thru 50, 58
$
PARTN 1
p2g = ep1, ef1
efload (nDIR=3, SCID=9) = yes
$
SUBCASE 2
OUTPUT
DISPLACEMENT(PRINT) = ALL
STRESS(PRINT) = ALL
Bulk Data
.....
$Cylindrical coordinate system used for surface normal and external force locations
CORD2C, 9, , 0.0, 0.0, 0.0, 0.0, 0.0, 1.0, +C1
+C1, 20.0, 0.0, 1.0
......
$Force Locations entered in cylindrical coodinates
$
dmi,ep1,0,2,1,0,,3,8
dmi,ep1,1,1, 20. , 0.0, 74.286
dmi,ep1,2,1, 20. , 45., 74.286

138

Example

dmi,ep1,3,1, 20. , 90.0, 74.286

dmi,ep1,4,1, 20. , 135.0, 74.286
dmi,ep1,5,1, 20. , 180.0, 74.286
dmi,ep1,6,1, 20. , 225.0, 74.286
dmi,ep1,7,1, 20. , 270.0, 74.286
dmi,ep1,8,1, 20. , 315.0, 74.286
$
$Force Vectors entered in basic coordinates
$
dmi,ef1,0,2,1,0,,3,8
dmi,ef1,1,1, 100.0,
0.0, 100.
dmi,ef1,2,1, 100.0,
0.0, 100.
dmi,ef1,3,1, 100.0,
0.0, 100.
dmi,ef1,4,1, 100.0,
0.0, 100.
dmi,ef1,5,1, 100.0,
0.0, 100.
dmi,ef1,6,1, 100.0,
0.0, 100.
dmi,ef1,7,1, 100.0,
0.0, 100.
dmi,ef1,8,1, 100.0,
0.0, 100.
$

Example

139

The structural loads resulting from the external force vectors produce the following
deformations.

Chapter

12 Acoustics

Default updates
The defaults for the NORMAL and OVLPANG parameters on the ACMODL bulk
entry have been modified.

The default for the parameter NORMAL when METHOD = AS has been
modified from 0.2 to 0.5.

The default for the parameter OVLPANG has been modified from 30.0 to 60.0.

Table 12-1. NORMAL and OVLPANG descriptions

Field

Contents

NORMAL

Outward normal search distance to detect fluid-structure interface.

(Real > 0.0; Default = 0.5 for METHOD = AS)
If METHOD = AS and SRCHUNIT is REL, NORMAL is a ratio
of the height of the fluid box in the outward normal direction to the
fluid surface to the maximum edge length of the fluid free face.
IF METHOD = AS and SRCHUNIT is ABS, NORMAL is the
outward search distance in the model/absolute units.

OVLPANG

Angular tolerance in degrees used to decide whether a fluid free

face and a structural face can be considered as overlapping. If the
angle between the normals of the fluid and structural faces exceeds
this value, they cannot be coupled. (Real > 0.0; Default = 60.0).

See the updated ACMODL bulk entry.

CPYRAM in acoustics
The pyramid element CPYRAM can now be included in acoustic models. You
can use these models to perform fully coupled fluid-structure analysis. Common

142

Alternative coupling option

applications are acoustic and noise control analysis; for example, in the passenger
compartments of automobiles. The pyramid can be included as part of either the
fluid or structure, and is permitted at the interface regions where fluid-structure
coupling occurs.

Alternative coupling option

The new AREAOP field on the ACMODL bulk entry is available to select an
alternate fluid-to-structural coupling option. AREAOP=0 selects the default
recommended NX Nastran coupling option. Specifying AREAOP=1 selects
the alternate option, which applies an area correction and removes parallel
disconnected faces from coupling.
See the updated ACMODL bulk entry.

ACMODL

143

Fluid-Structure Interface Modeling Parameters

ACMODL

Fluid-Structure Interface Modeling Parameters

Defines modeling parameters for the interface between the fluid and the structure.
Format:
1

ACMODL INTER INFOR

FSET

SSET

NORMAL

METHOD

10

OVLPANG SRCHUNIT

INTOL AREAOP reserved

Example:
0.25

ACMODL

AS

Fields:
Field

Contents

INTER

INTER is ignored when METHOD=AS.

When METHOD = CP, INTER defines the type of interface between
the fluid and the structure. (Character = IDENT or DIFF; Default
= DIFF).

INFOR

Indicates if FSET and SSET are to be used to define the

fluid-structure interface.
(Character = ALL, ELEMENTS, PID or NONE, Default =
NONE). See Remark 2.
Acceptable values for AS method are ELEMENTS and PID.
Acceptable values for CP method are ALL or NONE.

144

ACMODL
Fluid-Structure Interface Modeling Parameters
Field

Contents

FSET

Defines the fluid elements for the interface.

When METHOD = AS, FSET can be blank, or is the +/-ID of a SET1
bulk entry. The SET1 is interpreted according to the value of INFOR:
If INFOR = ELEMENTS, SET1 is a list of fluid element IDs.
If INFOR = PID, SET1 is a list of fluid element property IDs.
When a positive SET1 ID is entered on FSET, only these fluid
elements are considered.
When a negative SET1 ID is entered on FSET, these elements will be
excluded, and all other fluid elements are considered. See Remark 3.
(Integer or blank)
If METHOD = CP, FSET represents the SET1 entry that contains
a list of fluid grid points on the interface. (Integer > 0 or blank)

SSET

Defines the structural elements for the interface.

When METHOD = AS, SSET can be blank, or is the +/-ID of a SET1
bulk entry. The SET1 is interpreted according to the value of INFOR:
If INFOR = ELEMENTS, SET1 is a list of structural element IDs.
If INFOR = PID, SET1 is a list of structural element property IDs.
When a positive SET1 ID is entered on SSET, only these structural
elements are considered.
When a negative SET1 ID is entered on FSET, these elements will
be excluded, and all other structural elements are considered. See
Remark 3. (Integer or blank)
If METHOD = CP, SSET represents the SET1 entry that contains
a list of structure grid points on the interface. (Integer > 0 or blank)

NORMAL

Outward normal search distance to detect fluid-structure interface.

(Real > 0.0; Default = 0.5 for METHOD = AS) See Remark 4.
If METHOD = AS and SRCHUNIT is REL, NORMAL is a ratio
of the height of the fluid box in the outward normal direction to the
fluid surface to the maximum edge length of the fluid free face.
IF METHOD = AS and SRCHUNIT is ABS, NORMAL is the
outward search distance in the model/absolute units.
If METHOD = CP and INTER = IDENT, NORMAL represents a
tolerance in units of length used in determining the fluid-structure
interface. (Real > 0.0; Default = 0.001 for METHOD = CP)

ACMODL

145

Fluid-Structure Interface Modeling Parameters

Field

Contents

METHOD

Interface calculation method.

AS = Accelerated Search Method (Default).
CP = Closed Pressure Method (old method).

OVLPANG

Angular tolerance in degrees used to decide whether a fluid free face

and a structural face can be considered as overlapping. If the angle
between the normals of the fluid and structural faces exceeds this
value, they cannot be coupled. (Real > 0.0; Default = 60.0).

SRCHUNIT Search units. (Character; Default=REL). See Remark 4.

= ABS for absolute model units.
= REL for relative model units based on element size.
INTOL

Inward normal search distance to detect fluid-structure interface.

See Remark 4.
INTOL is ignored when METHOD = CP.
If METHOD = AS and SRCHUNIT is REL, INTOL is a ratio of
the height of the fluid box in the inward normal direction to the fluid
surface to the maximum edge length of the fluid free face.
IF METHOD = AS and SRCHUNIT is ABS, INTOL is the inward
search distance in the model/absolute units (Real > 0.0; Default =
0.20)

AREAOP

Alternative fluid-structure coupling method selection. See Remark 5.

(Integer; Default=0)
= 0 The recommended method is used (default).
= 1 The alternative method is used.

Remarks:
1.

Only one ACMODL entry is allowed. If this entry is not present, defaults will
be used.

2.

The INFOR field is interpreted as follows:

AS Method:
The acceptable values for this method are INFOR = ELEMENTS or PID. The
AS method will interpret the FSET and SSET as described in Remark 4.
If INFOR = ALL or NONE, this field will be ignored.
CP Method:

146

ACMODL
Fluid-Structure Interface Modeling Parameters
If INTER = IDENT and INFOR = NONE, the FSET and SSET entries are
ignored.
When INTER = IDENT and INFOR = ALL, matching is checked only at those
grid points referenced by FSET and SSET.
If INTER = DIFF, the FSET and SSET are used as described in Remark 4.
If INFOR = ELEMENTS, NX Nastran will reset this field to INFOR = NONE .
3.

The FSET and the SSET fields are interpreted as follows:

AS Method:
FSET and SSET are used only when INFOR = ELEMENTS or PID.

If FSET > 0, only the fluid elements included in this set will participate in
the coupling. All the other fluid elements will be ignored.

If FSET < 0, the fluid elements included in this set will be suppressed from
coupling computations.

If FSET is blank, all fluid elements will be used for coupling computations.

If SSET > 0, only the structural elements included in this set will participate
in the coupling. All the other fluid elements will be ignored.

If SSET < 0, the structural elements included in this set will be suppressed
from coupling computations.

If SSET is blank, all structural elements will be used for coupling

computations.

CP Method:
If INTER = IDENT, FSET and SSET should be greater than zero. If
FSET/SSET is <= 0, a FATAL message is issued.
The grid points defined by FSET and SSET must lie exactly on the fluid-structure
interface. A FATAL message is issued if the FSET or SSET do not have a
corresponding and coincident point in SSET or FSET, respectively.
If INTER = DIFF a FATAL message is issued if any point in SSET or FSET
does not lie exactly on the interface.
4.

The fields NORMAL and INTOL are interpreted as follows:

AS Method: (Real > 0.0; Default = 0.20)
If SRCHUNIT = REL, NORMAL is a ratio of the outward height of the
bounding box to the maximum edge length of the fluid free face. That is, if L is

ACMODL

147

Fluid-Structure Interface Modeling Parameters

the largest edge of the fluid free face, the height H of the bounding box used to
search for structural faces will be NORMAL * L. INTOL applies similarly, but
the inward direction.
If SRCHUNIT = ABS, NORMAL defines the outward height of the fluid
bounding box in the model/absolute units. INTOL defines the inward height of
the fluid bounding box in the model/absolute units.
If SRCHUNIT = ABS and NORMAL or INTOL are blank, SRCHUNIT will be
reset to REL and their corresponding default value is used.
CP Method: (Real > 0.0; Default = 0.001)
INTOL is not used when METHOD=CP.
If INTER = IDENT or DIFF, NORMAL represents a tolerance in units of
length used in determining the fluid-structure interface. The default value is
0.001.
5.

AREAOP=0 selects the default, recommended NX Nastran coupling option.

Specifying AREAOP=1 selects an alternate option, which applies an area
correction and removes parallel disconnected faces from the coupling.

Chapter

13 Windows I/O Option

The default I/O option on the windows platforms have changed from File Mapping
to Raw I/O. This is necessary for Windows 7, Windows Server 2008, and Vista
systems but might slightly degrade the performance on Windows XP and Windows
Server 2003; especially on systems that have a lot of memory. If you have a
Windows XP or Windows Server 2003 system and wish to use File Mapping,
remove the entry sysfield=... from the nastran rcf file.

Chapter

14 Upward compatibility

Updated modules
ACMG
Computes the coupling matrix for fluid/structure interface at all points or only
points on a given structural panel.

Updated Format:
ACMG

PANSLT,BGPDT,CSTM,SIL,ECT,EQACST,NORTAB,EQEXIN,EDT,GEOM2/
{AGG or APART}/
LUSET/MPNFLG/NUMPAN/S,N,PANAME/IPANEL/MATCH/
PNLPTV $

New Input Data Block:

GEOM2

Table of bulk data images related to element connectivity

Updated Input Data Block:

EDT

Element deformation table, which contains SET1 and SET3

entries

CNTITER
Perform surface to surface contact using the element iterative solver.

152

Updated modules
Updated Format:
CNTITER

KELM,PGALL,KDICT,SILS,ECT,BGPDT,CSTM,EDT,CASECC,USET,RG,MPT,
YG,SLT,MDICT,MELM,EPT,CNELM,ELCNST,ELCTST,ELGSTF,GLUESEQ,BIN/
UGV1,QG1,OQGCF1,OBC1,CONFON,ELTRCT1,OSPDSI1,OSPDS1,BOUT/
NSKIP/NLOADS/NOFAC/
S,N,MAXO/S,N,MAXI/S,N,CNTS/S,N,AITK/S,N,RESET/S,N,MINOLP/
S,N,TARPEN/S,N,ADAPT/S,N,SCALMT/S,N,IMODE/WTMASS $

New Input Data Block:

BIN

Results from bolt preload phase.

New Output Data Block:

BOUT

Results from bolt preload phase.

New Parameter:
WTMASS

Input-real-default=1.0. Weight to mass conversion factor.

DDRMM
Performs matrix method data recovery
Computes data recovery items (stress, displacements, forces, strains, forces)
directly from the modal solution in frequency response, transient response, or
scaled response spectra analysis using the matrix method.

Updated Format:
DDRMM

CASECC,UH,OL,IUG,IQG,IES,IEF,XYCDB,IUG1,IQG1,IES1,IEF1,UHD/
OUG,OQG,OES,OEF,UNUSED5/
OPTION/NOCOMP/PEXIST/ACOUSTIC/ACOUT/PREFDB/SEID/APP $

New Input Data Block:

UHD

Modal velocities solution matrix for the h-set (modal

degrees-of-freedom). Required only for frequency response.

Updated modules

153

DMIIN
Inputs DMI entries to DMAP.
Input matrices referenced on DMI Bulk Data entries.

Updated Format:
DMIIN

DMI,DMINDX/DMI1,DMI2,DMI3,DMI4,DMI5,DMI6,DMI7,
DMI8,DMI9,DMI10/PARM1/PARM2/PARM3/PARM4/PARM5/
PARM6/PARM7/PARM8/PARM9/PARM10/NAME1/NAME2 $

New Parameters:
NAME1

Input-character-default = . If NAME1 is specified, read the DMI

matrix associated with NAME1 instead of the output data block
DMI1.

NAME2

Input-character-default = . If NAME2 is specified, read the DMI

matrix associated with NAME2 instead of the output data block
DMI2.

DOM12
Performs soft and hard convergence checks in design optimization.

Updated Format:
DOM12

XINIT,XO,CVAL,PROPI*,PROPO*,OPTPRM,HIS,
DESTAB,GEOM1N,COORDO,EDOM,MTRAK,EPT,GEOM2,MPT,
EPTTAB*,DVPTAB*,XVALP,GEOM1P,
R1TABRG,R1VALRG,RSP2RG,R2VALRG,PCOMPT,OBJTBG,
ALBULK,AMLIST/
HISADD,OPTNEW,DBCOPT,DESNEW/
DESCYCLE/OBJIN/OBJOUT/S,N,CNVFLG/CVTYP/OPTEXIT/
DESMAX/MDTRKFLG/DESPCH/DESPCH1/MODETRAK/
EIGNFREQ/DSAPRT/PROTYP/BADMESH/XYUNIT/FSDCYC $

New Input Data Blocks:

OBJTBG

Overall (global) objective function data block.

ALBULK

Family of data blocks for bulk files for the original analysis/design
model as well as for all auxiliary models, if any.

154

Updated modules

AMLIST

List of auxiliary model identification numbers.

DOM9
Performs the approximate optimization problem.
Performs the approximate optimization problem using design variables,
constraints, responses and sensitivity information.

Updated Format:
DOM9

XINIT,DESTAB,CONSBL*,DPLDXI*,XZ,
DXDXI,DPLDXT*,DEQATN,DEQIND,DXDXIT,
PLIST2*,OPTPRMG,R1VALRG,RSP2RG,R1TABRG,
CNTABRG,DSCMG,DVPTAB*,PROPI*,CONS1T,
OBJTBG,COORDO,CON,SHPVEC,DCLDXT,
TABDEQ,EPTTAB*,DBMLIB,BCON0,BCONXI,
BCONXT,DNODEL,RR2IDR,RESP3RG,CVALRG/
XO,CVALO,R1VALO,R2VALO,PROPO,R3VALO/
OBJIN/S,N,OBJOUT/PROTYP/PROPTN/UNUSED1/
UNUSED2/UNUSED3/UNUSED4/UNUSED5/UNUSED6/
UNUSED7/UNUSED8/UNUSED9/UNUSED10 $

Updated Input Data Block:

CVALRG

The global data block for retained constraint values.

DOPR3
Preprocesses DCONSTR, DRESP1, DRESP2, and DRESP3 Bulk Data entries per
analysis type and superelement. Creates tables related to the design objective and
a Case Control table for recovering design responses.

Updated Format:
DOPR3

CASE,EDOMS,DTB,ECT,EPT,DESTAB,EDT,TMPFRL,DEQIND,
DEQATN,DESGID,DVPTAB,VIEWTB,OINT,PELSET,DFRFNC,
TSPAN23,DIT,EDOM/
OBJTAB,CONTAB,R1TAB,RESP12,RSP1CT,FRQRSP,CASEDS,
OINTDS,PELSETDS,DESELM,RESP3,TNSPAN23,SPAN1RG/
DMRESD/S,N,DESGLB/S,N,DESOBJ/S,N,R1CNT/S,N,R2CNT/
S,N,CNCNT/SOLAPP/SEID/S,N,EIGNFREQ/PROTYP/DSNOKD/
SHAPES/S,N,R3CNT $

Updated modules

155

New Input Data Block:

EDOMS

Table of Bulk Data entries related to design sensitivity and

optimization for current superelement.

Updated Input Data Block:

EDOM

Global table of Bulk Data entries related to design sensitivity and

optimization.

EFFMAS
Computes modal effective mass.
Compute the modal effective mass based on the normal modes.

Updated Format:
EFFMAS

CASECC,MAA,PHA,LAMA,USET,BGPDT,UNUSED,CSTM,VGQ/
TEMF,EMM,DMA,MEMF,MPFEM,MEM,MEW,MDLIST/
SEID/WTMASS/S,N,CARDNO/SETNAM/IUNIT/EFOPT $

New Output Data Block:

MDLIST

List of modes for output selected by effective mass fraction

FOCOEL
Form contact elements.

Updated Format:
FOCOEL

CASECC,BGPDT,CSTM,GEOM2,EST,MPT,CONTACT,SIL,GPSNTC/
CNELM,GPECTC/
S,N,NSKIP/S,Y,CONTGLUE/S,N,NLHEAT/S,N,GLUSET/S,N,NCELS/S,N,MAXO/
S,N,MAXI/S,N,CNTS/S,N,AITK/S,N,MPLI/S,N,RESET/S,N,FRICTM/
S,N,TARPEN/S,N,ADAPT/S,N,SCALMT//S,N,REFOPT/S,N,MEL $

New Input Data Block:

GPSNTC

Table of grid point shell normals.

156

Updated modules
New Parameter:
MEL

Input-integer-no default. Maximum number of elements connected

to a grid.

GP5
Creates table of static loads for panels in coupled fluid/structure analysis.

Updated Format:
GP5

ECT,BGPDT,EQEXIN,EDT,SIL,GEOM2/
PANSLT,EQACST,NORTAB/
S,N,MPNFLG/S,N,NUMPAN/S,N,MATCH/NASOUT/GETNUMPN/
S,N,METHOD/S,N,SKINOUT/S,N,NORMAL/S,N,OVLPANG/
S,N,INTOL/S,N,ABSFLG/S,N,NGAUSS $

New Input Data Block:

GEOM2

Table of bulk data images related to element connectivity

Updated Input Data Block:

EDT

Table of Bulk Data entry images related to element deformation,

aerodynamics, p-element analysis, divergence analysis, and the
iterative solver. Also contains SET1 and SET3 entries

IFP
Reads Bulk Data Section
Reads in the Bulk Data and outputs the finite element model in table form.

Updated Input Data Block:

EDT

Table of Bulk Data entry images related to element deformation,

aerodynamics, p-element analysis, divergence analysis, and the
iterative solver. Also contains SET1 and SET3 entries

Updated modules

157

MATMOD
Transforms matrix or table data blocks according to one of many options into
output matrix or table data blocks.

Updated Format:
MATMOD

I1,I2,I3,I4,I5,I6,I7,I8,I9,I10,I11,I12,I13,I14,I15/
O1,O2/
P1/P2/P3/P4/P5/P6/P7/P8/P9/P10/P11/P12/p13/p14/p15 $

Updated Input Data Blocks:

Ii

Input data blocks. I1 is required; I2 through I15 may not be

necessary depending on the value P1.

Updated Option P1=40

Remove unused q-set degrees-of-freedom from USET.

Updated Format:
MATMOD

USET,VAXW,,,,,,,,,,,,,/USETN,VAXWN/40 $

New Output Data Block:

VAXWN

Modified VAXW corresponding to USETN.

Updated Option P1=44

Create a g-set partitioning vector for sparse data recovery based on the output
requests in the case control section. This option is only valid for frequency and
transient response output requests.

158

Updated modules
Updated Format:
MATMOD

BGPDTS,SILS,CASES,USETS,EPTS,GEOM2S,EQEXINS,
XYCDB,GMTG,GOATG,GPECT,PCDB,POSTCDB,SETMC,EDT/PARTV,
/44/NOEPT/NOSE/IWHO///NUMPAN $

New Input Data Block:

EDT

Element deformation table. Contains PANEL, SET1,

and SET3 bulk entries.

New Parameter:
NUMPAN

Input-integer default=0. Number of acoustic panels.

Updated Remark:
4. The supported case control output requests are:
a.

DISPLACEMENT

b.

VELOCITY

c.

ACCELERATION
OLOAD

d.
e.
f.
g.
h.
I.
j.
k.
l.
m.

STRESS/ELSTRESS
STRAIN/ELSTRAIN
FORCE/ELFORCE
EDE
EKE
ESE
XYPEAK
XYPRINT
XYPLOT

n.

XYPUNCH

o.
p.

MPCFORCE

q.

GPFORCE

SPCFORCE

Updated modules
r.

GPSTRESS

s.

GPSTRAIN

t.

MODCON

u.

PANCON

159

New Option P1=51

Generate a surface spline to connect two point fields in close proximity, but not
necessarily coincident.

Format:
MATMOD

IM1,IM2,,,,,,,,,,,,,/OM1,/51/P2/P3/P4/P5 $

Input Data Blocks:

IM1

Matrix of independent points. 3 rows by NI columns. NI = number

of independent points.

IM2

Matrix of dependent points. 3 rows by ND columns. ND = number

of dependent points.

Output Data Block:

OM1

Transformation matrix describing the surface spline connection.

NI rows by ND columns. NI = number of independent points. ND
= number of dependent points.

Parameters:
P2,P3

Input-integer default=0,0. Used to define boundary condition of

the surface spline.
0,0

Surface spline is unconstrained at the edges.

-1,0 A zero moment X-directional end condition is imposed on

the surface spline.
0,-1 A zero moment Y-directional end condition is imposed on
the surface spline.

160

Updated modules

P4

P5

Input-integer default=1. Coordinate pair selection.

1

XY point pairs are used for the surface spline fit.

XZ point pairs are used for the surface spline fit.

YZ point pairs are used for the surface spline fit.

Input-real default=1.0. Used to stiffen springs applied during the

surface spline generation.

New Option P1=53

Generate a g-size partitioning vector and a list of grid IDs that correspond to the
structural grids that are a part of an acoustic coupling matrix.

Format:
MATMOD

EQEXIN,USET,SIL,AG0MAX,,,,,,,,,,,/PARTV,ACGRIDS/53///
S,N,NOPARTV $

Input Data Blocks:

EQEXIN

Equivalence table between external and internal grid/scalar

identification numbers.

USET

Degree-of-freedom set membership table for g-set.

SIL

Scalar index list.

AG0MAX

Column matrix of maximum values in each row of the AG0 matrix

(usually derived using MATMOD option 6).

Output Data Block:

PARTV

Column partitioning vector for all 6 degrees-of-freedom of grids

which are a part of the acoustic coupling.

ACGRIDS

Column vector containing the grid IDs of the grids which are a
part of the acoustic coupling; the grid IDs are represented as real
values.

Updated modules

161

Parameters:
NOPARTV

Output-integer. NOPARTV is set to -1 if the output data blocks

are null or cannot be generated. Otherwise, it is set to zero.

Remarks:
1.

None of the data blocks can be purged.

MODACC
OFREQ and OTIME command processor.
Removes columns in solution and load matrices based on the OTIME and OFREQ
case control commands.

Updated Format:
MODACC

CASECC,OL,U,P1,P2,P3/
OL1,U1,P11,P21,P31/APP/IOPT $

New Parameter:
IOPT

Input-integer-default=0. Processing options:

0=process OFREQ or OTIME.
1=process SETMC for MODCON.
2=process SETMC for PANCON.

MODEPF
Computes mode participation factors for fluid-structure models in frequency
response analysis.

162

Updated modules
Updated Format:
MODEPF

BGPDT,USET,CASECC,EDT,ABESF*,
PHASH2,UHFS,PHDFH,MFHH,BFHH,
KFHH,FOL,ABEH*,PHDFH1,PHDFH2,
UHFF,AH,PFHF,UNUSED,PNLLST,
VGA,GEOM2/
GPMPF,FMPF,SMPF,PMPF,LMPF,
MPFMAP/
NOFREQ/NOLOADF/GRIDFMP/NUMPAN/PNQALNAM/
SYMFLG/MPNFLG/FLUIDMP/STRUCTMP/PANELMP/
GRIDMP/NOSASET/FILTERF/FILTERS $

New Input Data Block:

GEOM2

Table of bulk data images related to element connectivity

MTRXIN
Converts matrices input on DMIG Bulk Data entries to matrix data blocks.

Updated Formats:
Form 1 Simplified (CASECC is purged)
MTRXIN

Note
An output data block has been added.

Form 2 Case Control Command Selection of stiffness, mass, and damping (or
square) matrices (IOPT=1 for K2GG, and so on, and IOPT=0 for K2PP, and so on,
and TF)

Updated modules

163

MTRXIN

Form 3 Case Control Command selection of load (or rectangular) matrix (IOPT=2)
MTRXIN

Form 4 Selection of DMIK, DMIJ and DMIJI by data block names MATKi,
MATJi, and MATJIi.
MTRXIN

Form 5 Selection of stiffness, mass, damping, and loads (or square) matrices by
K2PNAM, and so on, input parameter values (IOPT=10 through 12).

164

Updated modules

MTRXIN

Form 6 - Selection of DMIK, DMIJ, and DMIJI matrices by the MATNAMi input
parameter values (IOPT=13 through 15)
MTRXIN

Updated Output Data Block:

K2GG,
etc.

Matrices defined on DMIG Bulk Data entries and referenced by

the K2GG, M2GG, B2GG, K42GG, A2GG, K2PP, M2PP, B2PP, or
P2G Case Control commands

Updated modules

165

Updated Parameter:
IOPT

Input-integer-default=0. Case Control command selection flag.

0

No Case Control command selection (see Form 1) or K2GG,

and so on, and TFL Case Control command selection (see
Form 2)

K2GG, and so on, Case Control command selection (see Form

2)

P2G Case Control command selection (see Form 3)

DMIK selection by output data block name (see Form 4)

DMIJ selection by output data block name (see Form 4)

DMIJI selection by output data block name (see Form 4)

10

K2PP, M2PP, and B2PP selection by input parameter value

(see Form 5)

11

K2GG, M2GG, B2GG, K42GG, and A2GG selection by input

parameter value (see Form 5)

12

P2G selection by input parameter value (see Form 5)

13

DMIK selection by input parameter value (see Form 6)

14

DMIJ selection by input parameter value (see Form 6)

15

DMIJI selection by input parameter value (see Form 6)

Updated Remark 3:
3.

Forms 2 and 3 are used to select the matrices with Case Control
commands: K2GG, M2GG, B2GG, K42GG, A2GG, K2PP, M2PP,
B2PP, or P2G. -2GG matrices are of dimension g by g. -2PP
matrices are of dimension p by p. The P2G matrix has g-rows,
with the number of columns determined by the several methods
used to input rectangular matrices described on the DMIG entry.

166

Updated modules
Updated Examples:
1.

Assume the Bulk Data contains two DMIG matrices, named M1 and M2,
which reference grid and/or scalar points only. The following set of DMAP
instructions generate these two matrices in matrix format, multiply them,
and print the result.
MTRXIN
,,MATPOOL,EQEXIN,,/Ml,M2,,,/LUSET/S,N,NOMl/S,N,NOM2$
IF (NOM1 > -1 AND NOM2 > -1) THEN $
MPYAD
M1,M2,/PRODUCT $
MATPRN PRODUCT//$
ENDIF $

2.

Assume the Bulk Data contains two DMIG matrices, MASS and STIFF, which
reference grid and/or scalar points only. The following Case Control and
DMAP instructions generate these two matrices in matrix format and add
them to the structural mass and stiffness.
Case Control:
M2GG = MASS
K2GG = STIFF

DMAP instructions:
MTRXIN

CASECC,MATPOOL,EQEXIN,,/STIFF,MASS,,,/
LUSET/S,N,NOSTIFF/S,N,NOMASS///1 $
IF (NOSTIFF > -1) THEN $
ADD
KGG,STIFF/KGGNEW $
EQUIVX KGGNEW/KGG/ALWAYS $
ENDIF $
IF (NOMASS > -1) THEN $
ADD
MGG,MASS/MGGNEW $
EQUIVX MGGNEW/MGG/ALWAYS $
ENDIF

OUTPRT
Constructs sparse load reduction and sparse data recovery partitioning vectors.

Updated Parameter:
MCFLAG

Input-integer-default=0. Modal contribution set usage flag.

0

grids and elements

grids only

elements only

acoustic/fluid points only

Updated modules

167

RESTART
Data block comparison
Compares two data blocks and invokes dependencies.

Updated Format:
RESTART

DB1,DB2,DLSTIN/DLSTOUT/
INVOKE/SPEXP/DPEXP/NDDLNAM/S,CMPDIF $

New Parameter:
CMPDIF

Output-integer. If CMPDIF=1, the comparison between DB1 and

DB2 found differences. Only valid for DB1 and DB2 existing with
DLSTIN purged.

SDR2
Creates output tables.
Creates tables based on output requests for forces of single-point and multipoint
forces of constraint, applied loads, displacements, velocities, accelerations, element
stresses, element strains, and element forces. These output tables are suitable for
printing, plotting, and various other postprocessing.

Updated Format:
SDR2

CASECC,CSTM,MPT,DIT,EQEXIN,SILD,
ETT,{OL or EDT},BGPDT,PG,QG,UG,EST,XYCDB,
OINT,PELSET,VIEWTB,GPSNT,DEQATN,DEQIND,DITID,
PCOMPT,GPKE,BOLTFOR,MDLIST/
OPG1,OQG1,OUG1,OES1,OEF1,PUG,OGPKE1/
APP/S,N,NOSORT2/NOCOMP/ACOUSTIC/METRIK/
ISOFLG/GPF/ACOUT/PREFDB/TABS/
SIGMA/ADPTINDX/ADPTEXIT/BSKIP/FREQW/
BTBRS/LANGLE/OMID $

New Input Data Block:

MDLIST

List of modes for output selected by effective mass fraction.

168

New modules

VDRMC
Creates modal contribution tables based on modal contribution output requests.

Updated Format:
VDRMC

CASEG,SETMC,AMC,NMC,MAG,OL,MFRQ,ECT,BGPDT,TEXTSE/
OUTFLE/
APP/S,N,NOSORT2/S,N,NOSOUT/FMODE/IRTYPE/FSFLAG $

New Parameter:
FSFLAG

Input-integer-default=0. Fluid/structure flag. Only applies to

IRTYPEs 1 thru 7.
0 = structural modal contribution results from structural modes
1 = fluid modal contribution results from structural modes
11 = fluid modal contribution results from fluid modes

New modules
NXNMATLB
Creates an MATLAB .m script file for a superelement.
Creates an MATLAB .m script file for a superelement. The output is based on the
MBDEXPORT case control command with the MATLAB describer specified.

Format:
For the STANDARD case control option:
NXNMATLB

CASES,LAMA,PHIG,EMVD,U8DOF,,MFORC//
SEID/WTMASS/FLXERR $

For the STATESPACE case control option:

NXNMATLB

CASES,AMAT,BMAT,CMAT,U7DOF,U8DOF,//
SEID/WTMASS/FLXERR $

New modules

169

Input Data Blocks:

CASES

Case control table associated with superelement.

LAMA

Eigenvalue summary table for superelement.

PHIG

Mode shape matrix (U8-set) for superelement.

EMVD

Equivalent modal viscous damping matrix for superelement.

AMAT

State-space [A] matrix for superelement.

BMAT

State-space [B] matrix for superelement.

CMAT

State-space [C] matrix for superelement.

U7DOF

U7-set DOF vector (input DOF) for superelement.

U8DOF

U8-set DOF vector (output DOF) for superelement.

MFORC

Modal force vector for superelement.

Parameters:
SEID

Input-integer-no default. Superelement ID number.

WTMASS

Input-real-no default. Value of WTMASS parameter from

PARAM,WTMASS,value.

FLXERR

Output-integer-no default. Error flag. Options are:

0: No error
1: Error

Remarks:
This module will generate a MATLAB .m script file.

VDRPC
Creates panel or grid contribution tables based on panel/grid contribution output
requests.

170

New modules
Format:
VDRPC

Input Data Blocks:

CASEG

Table of Case Control command images for current subcase.

SETMC

Table of SETMC Case Control definitions.

APC

Absolute panel contributions results matrix.

NPC

Normalized panel contributions results matrix.

MAG

Magnitudes of modal contributions matrix.

FOL

Frequency response frequency output list.

BGPDT

Basic grid point definition table.

PNLLST

Panels list table (for DATTYP=1).

SLGRIDS

List of selected grids (for DATTYP=2).

Output Data Blocks:

OUTFLE

Table of panel or grid contributions in SORT1 format.

Parameters:
APP

Input-character-no default. Analysis type. Allowable values:

FREQRESP

Frequency response

NOSORT2 Output-integer-no default. Solution set SORT2 format flag. Set to 1

if SORT2 format is requested; -1 otherwise.

Updated datablocks

171

NOSOUT Output-integer-default=0. Output flag. Set to 1 if any output is

requested; -1 otherwise.
IRTYPE

Input-integer-default=1. Panel contributions results type.

1 = pressures
2 = first derivative of pressures
3 = pressure and first derivatives
4 = second derivative of pressures
5 = pressures and second derivatives
6 = first and second derivative of pressures
7 = pressures, first derivatives, and second derivatives

DATTYP

Input-integer-no default. Data type.

1 = panel contributions
2 = grid contributions

Remarks:
1.

Contribution totals will appear as ID number 0 in OUTFLE and will be printed

to the .f06 file with the label TOTAL.

2.

None of the data blocks can be purged.

Updated datablocks
AXIC68
Element property table (Pre-MSC Nastran Version 69).

New RECORD FORCE(4201,42,18)

Static force.
Name

Word

Type

Description

SID

Load set identification number

Grid point identification number

CID

Coordinate system identification

number

172

Updated datablocks

Name

Word

Type

Description

RS

Scale factor

N1

RS

Vector component in the coordinate

system defined by CID

N2

RS

Vector component in the coordinate

system defined by CID

N3

RS

Vector component in the coordinate

system defined by CID

New RECORD GRAV(4401,44,26)

Acceleration or gravity load.
Name

Word

Type

Description

SID

Load set identification number

CID

Coordinate system identification number

RS

Acceleration scale factor

N1

RS

Vector component in the coordinate

system defined by CID

N2

RS

Vector component in the coordinate

system defined by CID

N3

RS

Vector component in the coordinate

system defined by CID

MB

Bulk data section with CID definition:

-1=main, 0=partitioned

New RECORD LOAD(4551,61,84)

Static load combination.
Word
1

Name
SID

Type
I

Description
Load set identification number

Updated datablocks

Name

Word

Type

173

Description

RS

Overall scale factor

Si

RS

Scale factor on Li

Li

Load set identification number

Words 3 and 4 repeat until (-1,-1) occurs

New RECORD MOMENT(4801,48,19)

Static moment.
Name

Word

Type

Description

SID

Load set identification number

Grid point identification number

CID

Coordinate system identification number

RS

Moment scale factor

N1

RS

Vector component in the coordinate

system defined by CID

N2

RS

Vector component in the coordinate

system defined by CID

N3

RS

Vector component in the coordinate

system defined by CID

New RECORD MPCADD(4891,60,83)

Multipoint constraint set combination.
Name

Word

Type

Description

SID

Set identification number

Set identification number of multipoint

constraint set

174

Updated datablocks

Name

Word

Type

Description

Word 2 repeats until -1 occurs

New RECORD SEQGP(5301,53,4)

Grid and scalar point resequencing.
Name

Word

Type

Description

ID

Grid or scalar point identification

number

SEQID

Sequenced identification number

New RECORD SPCADD(5491,59,13)

Single-point constraint set combination.
Name

Word

Type

Description

SID

Set identification number

Single-point constraint set identification

number

Word 2 repeats until -1 occurs

New RECORD TEMPD(5641,65,98)

Grid point temperature field default.
Name

Word

Type

Description

SID

Temperature set identification number

RS

Temperature

CASECC
Case control information

Updated datablocks

175

Updates for Record REPEAT

Word

Name

Type

Description

....
304

PANCON

Panel contributions set

(PANCON)

305

PCMEDIA

Panel contributions media

(PANCON)

306

PCFMT

Panel contributions format

(PANCON)

307

PCFORM

Panel contributions form

(PANCON)

308

PCTOPP

Panel contributions TOPP

(PANCON)

309

PCTOPG

Panel contributions TOPG

(PANCON)

310

PCSOL

Panel contributions
SOLUTION (PANCON)

311

PCPAN

Panel contributions
PANEL (PANCON)

312

PCGRID

Panel contributions GRID

(PANCON)

313

MODSLF

Mode selection set (fluid)

A2GG(2)

CHAR4

Name of direct input

(g-set) acoustic coupling
matrix (A2GG)

333

UNDEF

None

334

NA2GG

....
317

....

Internal set id for A2GG

176

Updated datablocks

Word

Name

Type

Description

....
392

EXSEDMFX(2)

CHAR4

External Superelement
DMIGSFIX String

394

NSMID

Non-Structural Mass Set

ID

395

UNDEF(2)

None

397

OP4UNIT

398

UNDEF

None

399

CHECK

ADAMSMNF/MBDEXPORT
CHECK flag

400

ADMOUT

ADAMSMNF ADMOUT
flag/MBDEXPORT
RECVROP2 flag

401

FLEXBODY

ADAMSMNF/MBDEXPORT
FLEXBODY flag

402

FLEXONLY

ADAMSMNF/MBDEXPORT
FLEXONLY flag

403

MINVAR

ADAMSMNF/MBDEXPORT
MINVAR parameter

404

PSETID

ADAMSMNF/MBDEXPORT
PSETID parameter

405

OUTGSTRS

ADAMSMNF/MBDEXPORT
OUTGSTRS flag

406

OUTGSTRN

ADAMSMNF/MBDEXPORT
OUTGSTRN flag

407

UNDEF(6)

None

....

MBDEXPORT OP4 logical

unit number

Updated datablocks

Word

Name

Type

177

Description

430

MCSOL

Modal contributions
SOLUTION (MODCOM)

431

MCPAN

Modal contributions
PANELMC (MODCOM)

MCTOPF

Modal contributions TOPF

(MODCON)

MODSEL

Mode selection set

(structural)

455

UNDEF(14)

None

469

MCTOPS

Modal contributions TOPS

(MODCON)

475

FK2PP

Internal set id for K2PP

scale factor

476

FM2PP

Internal set id for M2PP

scale factor

477

FB2PP

Internal set id for B2PP

scale factor

478

FK2GG

Internal set id for K2GG

scale factor

479

FM2GG

Internal set id for M2GG

scale factor

480

FB2GG

Internal set id for B2GG

scale factor

....
442
....
445
....

....

178

Updated datablocks

Name

Word

Type

Description

481

FK42GG

Internal set id for K42GG

scale factor

482

FP2G

Internal set id for P2G

scale factor

483

FA2GG

Internal set id for A2GG

scale factor

484

GPRSORT

Global ply results sorted

with global ply ID
numbers

485

EFLOAD1

External field load

orientation

486

EFLOAD2

External field coordinate

system

487

UNDEF(113)

None

....

EPT
Element property table.

Updated Record PLPLANE(4606,46,375)

Name

Word

Type

Description

PID

Property identification number

MID

Material identification number

CID

Coordinate system identification number

STR

CHAR4

Location of stress and strain output

RS

Default membrane thickness for Ti on

the connection entry

UNDEF(6)

None

Updated datablocks

179

New Record PPLANE(3801,38,978)

Name

Word

Type

Description

PID

Property identification number

MID

Material identification number

RS

Default membrane thickness for Ti on

the connection entry

NSM

RS

Nonstructural mass per unit area

UNDEF(4)

None

EPT705
Element property table (Pre-MSC Nastran 2001).

New RECORD NSM(3201,32,991)

Defines the properties of a nonstructural mass.
Name

Word

Type

Description

SID

Set identification number

PROP(2)

CHAR4

Set of properties or elements

ORIGIN

Entry origin

ID

Property or element identification

number

VALUE

RS

Nonstructural mass value

Words 5 through 6 repeat until End of Record

New RECORD NSM1(3301,33,992)

Defines the properties of a nonstructural mass.

180

Updated datablocks

Name

Word

Type

Description

SID

Set identification number

PROP(2)

CHAR4

Set of properties or elements

ORIGIN

Entry origin

VALUE

RS

Nonstructural mass value

SPECOPT

Specification option

SPECOPT=1

By IDs

ID

Word 7 repeats until End of Record

SPECOPT=2

All

CHAR4

ALL(2)

Words 7 and 8 repeat until End of Record

SPECOPT=3

Thru range

ID

THRU(2)

CHAR4

10

ID

Words 7 through 10 repeat until End of Record

SPECOPT=4

Thru range with by

ID

THRU(2)

CHAR4

10

ID

11

BY(2)

CHAR4

13

Updated datablocks

Name

Word

Type

181

Description

Words 7 through 13 repeat until End of Record

End SPECOPT

New RECORD NSMADD(3401,34,993)

Combines the nonstructural mass inputs.
Name

Word

Type

Description

SID

Set identification number

ID

Set of properties or elements

Word 2 repeats until End of Record

New RECORD NSML(3501,35,994)

Defines a set of lumped nonstructural mass by ID.
Name

Word

Type

Description

SID

Set identification number

PROP(2)

CHAR4

Set of properties or elements

ID

Property of element identification number

VALUE

RS

Lumped nonstructural mass value

Words 4 and 5 repeat until -1 occurs

New RECORD NSML1(3701,37,995)

Alternate form of NSML entry. Defines lumped nonstructural mass entries by
VALUE, ID list.
Word
1

Name
SID

Type
I

Description
Set identification number

182

Updated datablocks

Name

Word

Type

Description

PROP(2)

CHAR4

Set of properties or elements

VALUE

RS

Lumped nonstructural mass value

SPECOPT

Specification option

SPECOPT=1

By IDs

ID

Property of element identification number

Word 6 repeats until -1 occurs

SPECOPT=2

All

CHAR4

ALL(2)

Keyword ALL

Words 6 and 7 repeat until -1 occurs

SPECOPT=3

Thru range

ID1

Starting identification number

THRU(2)

CHAR4

Keyword THRU

ID2

Ending identification number

Words 6 through 9 repeat until -1 occurs

SPECOPT=4

Thru range with by

ID1

Starting identification number

THRU(2)

CHAR4

Keyword THRU

ID2

Ending identification number

10

BY(2)

CHAR4

Keyword BY

12

Increment

Words 6 through 12 repeat until -1 occurs

Updated datablocks

183

New RECORD PCOMPG(15006,150,604)

Name

Word

Type

Description

PID

Property identification number

LAMOPT

Laminate option

Z0

RS

Distance from the reference plane to the

bottom surface

NSM

RS

Nonstructural mass per unit area

SB

RS

Allowable shear stress of the bonding

material

FT

Failure theory

TREF

RS

Reference temperature

GE

RS

Damping coefficient

GPLYIDi

Global ply IDs.

10

MID

Material identification number

11

RS

Thicknesses of the ply

12

THETA

RS

Orientation angle of the longitudinal

direction of the ply

13

SOUT

Stress or strain output request of the ply

Words 9 through 13 repeat N times

New RECORD PFAST(3601,36,55)

Name

Word

Type

Description

PID

Property identification number

RS

Diameter of the spot weld

MCID

Element stiffness coordinate system

184

Updated datablocks

Name

Word

Type

Description

MFLAG

Defines MCID as absolute or relative

5-7

KT(3)

RS

Translational stiffness

8-10

KR(3)

RS

Rotational stiffness

11

MASS

RS

Lumped mass

12

GE

RS

Structural damping

New RECORD PPLANE(3801,38,978)

Name

Word

Type

Description

PID

Property identification number

MID

Material identification number

RS

Default membrane thickness for Ti on

the connection entry

NSM

RS

Nonstructural mass per unit area

UNDEF(4)

None

GEOM168
Table of Bulk Data entry images related to geometry (Pre-MSC Nastran Version
69).

Updated Record 18 SEBULK(1427,14,465)

Word

Name

Type

Description

SEID

Superelement identification number

TYPE

Superelement type

RSEID

Reference superelement identification

number

Updated datablocks

Word

Name

Type

185

Description

METHOD

Boundary point search method:

1=automatic or 2=manual

TOL

RS

Location tolerance

LOC

Coincident location check option: yes=1

or no=2

MEDIA

Media format of boundary data of

external SE

UNIT

FORTRAN unit number of OP2 and OP4

input of external SE

GEOM2
Table of Bulk Data entries related to element connectivity.
GEOM2 also contains information on scalar points. ECT is identical in format
to GEOM2 except all grid and scalar point external identification numbers are
replaced by internal numbers. Also, ECT does not contain SPOINT records.

New Record CPLSTN3(8801,88,980)

Word

Name

Type

Description

EID

Element identification number

PID

Property identification number

G(3)

Grid point identification numbers of

connection points

THETA

RS

Material property orientation angle or

coordinate system ID

UNDEF(10)

None

186

Updated datablocks
New Record CPLSTN4(9301,93,981)
Word

Name

Type

Description

EID

Element identification number

PID

Property identification number

G(4)

Grid point identification numbers of

connection points

THETA

RS

Material property orientation angle or

coordinate system ID

UNDEF(9)

None

New Record CPLSTN6(9401,94,982)

Word

Name

Type

Description

EID

Element identification number

PID

Property identification number

G(6)

Grid point identification numbers of

connection points

THETA

RS

Material property orientation angle or

coordinate system ID

10

UNDEF(7)

None

New Record CPLSTN8(9501,95,983)

Word

Name

Type

Description

EID

Element identification number

PID

Property identification number

G(8)

Grid point identification numbers of

connection points

Updated datablocks

Word

Name

Type

11

THETA

RS

12

UNDEF(5)

None

187

Description
Material property orientation angle or
coordinate system ID

New Record CPLSTS3(9601,96,984)

Word

Name

Type

Description

EID

Element identification number

PID

Property identification number

G(3)

Grid point identification numbers of

connection points

UNDEF

None

THETA

RS

UNDEF(4)

None

12

TFLAG

Flag signifying meaning of T(3) values

13

T(3)

RS

Membrane thickness of element at

grid points

16

UNDEF

None

Material property orientation angle or

coordinate system ID

New Record CPLSTS4(8401,84,985)

Word

Name

Type

Description

EID

Element identification number

PID

Property identification number

G(4)

Grid point identification numbers of

connection points

188

Updated datablocks

Word

Name

Type

Description

THETA

RS

UNDEF(4)

None

12

TFLAG

Flag signifying meaning of T(4) values

13

T(4)

RS

Membrane thickness of element at

grid points

Material property orientation angle or

coordinate system ID

New Record CPLSTS6(9801,98,986)

Word

Name

Type

Description

EID

Element identification number

PID

Property identification number

G(6)

Grid point identification numbers of

connection points

UNDEF(2)

None

11

THETA

RS

Material property orientation angle or

coordinate system ID

12

TFLAG

Flag signifying meaning of T(3) values

13

T(3)

RS

Membrane thickness of element at

grid points

16

UNDEF

None

New Record CPLSTS8(9901,99,987)

Word

Name

Type

Description

EID

Element identification number

PID

Property identification number

Updated datablocks

Word

Name

Type

189

Description

G(8)

Grid point identification numbers of

connection points

11

THETA

RS

Material property orientation angle or

coordinate system ID

12

TFLAG

Flag signifying meaning of T(4) values

13

T(4)

RS

Membrane thickness of element at

grid points

17

UNDEF(8)

None

New Record CPYRA5FD(25700,257,9948)

Same as record CPYRAM description.

New Record CPYRA13F(25800,258,9947)

Same as record CPYRAM description.

New Record CPYRAMPR(7909,79,9946)

Word

Name

Type

Description

EID

Element identification number

PID

Property identification number

G(13)

Grid point identification numbers of

connection points

16

UNDEF

None

GEOM3
Table of Bulk Data entry images related to static and thermal loads.

190

Updated datablocks
New Record BOLTLD(7601,76,577)
Name

Word

Type

Description

SID

Set identification number of BOLTLD

bulk entry

RS

Overall scale factor

Si

RS

Scale factor on Li

Li

Set identification number of BOLTFOR

bulk entries

Word 4 repeats until (-1,-1) occurs

GEOM4705
Table of Bulk Data entry images related to constraints (Pre-MSC Nastran 2001).
Table of Bulk Data entry images related to constraints, degree-of-freedom
membership and rigid element connectivity.

New Record BNDFIX(110,1,584)

Word

Name

Type

Description

ID

Grid or scalar point identification number

Component numbers

New Record BNDFIX1(210,2,585)

Name

Word

Type

Description

Component numbers

THRUFLAG

Thru range flag

THRUFLAG=0

No

ID

Grid or scalar point identification

number

Updated datablocks

Name

Word

Type

191

Description

Word 3 repeats until End of Record

THRUFLAG=1

Yes

ID1

First grid or scalar point identification

number

ID2

Second grid or scalar point identification

number

End THRUFLAG

New Record BNDFREE(310,3,586)

Word

Name

Type

Description

ID

Grid or scalar point identification number

Component numbers

New Record BNDFREE1(410,4,587)

Name

Word

Type

Description

Component numbers

THRUFLAG

Thru range flag

THRUFLAG=0

No

ID

Grid or scalar point identification

number

Word 3 repeats until End of Record

THRUFLAG=1

Yes

ID1

First grid or scalar point identification

number

ID2

Second grid or scalar point identification

number

192

Updated datablocks

Name

Word

Type

Description

End THRUFLAG

New Record RWELD(11901,119,561)

Word

Name

Type

Description

EID

Element ID

GA

Grid ID of GA

TYPE

Type of shell element

GI(8)

Grid IDs of shell element

12

GS

Grid ID of GS

MPT
Table of Bulk Data entry images related to material properties.

New Record MAT11(2903,29,371)

Solid element orthotropic material property definition.
Defines the material properties for a 3-D orthotropic material for isoparametric
solid elements.
Name

Word

Type

Description

MID

Material identification number

E1

RS

Modulus of elasticity in the longitudinal

direction or 1-direction

E2

RS

Modulus of elasticity in the lateral

direction or 2-direction

E3

RS

Modulus of elasticity in the thickness

direction or 3-direction

NU12

RS

Poissons ratio (2/1 for uniaxial loading

in the 1-direction)

Updated datablocks

Name

Word

Type

193

Description

NU13

RS

Poissons ratio (3/1 for uniaxial loading

in the 1-direction)

NU23

RS

Poissons ratio (3/2 for uniaxial loading

in the 2-direction)

G12

RS

In-plane shear modulus

G13

RS

Transverse shear modulus for shear in

the 13 plane

10

G23

RS

Transverse shear modulus for shear in

the 23 plane

11

RHO

RS

Mass density

12

A1

RS

Thermal expansion coefficient in the

longitudinal direction

13

A2

RS

Thermal expansion coefficient in the

lateral direction

14

A3

RS

Thermal expansion coefficient in the

thickness direction

15

TREF

RS

Reference temperature for calculation of

thermal loads

16

GE

RS

Structural damping coefficient

17

UNDEF(16)

None

New Record MATT11(3303,33,988)

Solid orthotropic material temperature dependence.
Defines the temperature dependent material property for a 3-D orthotropic
material for isoparametric solid elements.
Word
1

Name
MID

Type
I

Description
Material identification number

194

Updated datablocks

Word

Name

Type

Description

TE1

TABLEMi ID for modulus of elasticity in

the 1-direction

TE2

TABLEMi ID for modulus of elasticity in

the 2-direction

TE3

TABLEMi ID for modulus of elasticity in

the 3-direction

TNU12

TABLEMi ID for Poissons ratio (2/1 for

uniaxial loading in the 1-direction)

TNU13

TABLEMi ID for Poissons ratio (3/1 for

uniaxial loading in the 1-direction)

TNU23

TABLEMi ID for Poissons ratio (3/2 for

uniaxial loading in the 2-direction)

TRHO

TABLEMi ID for mass density

TG12

TABLEMi ID for shear modulus in 12

plane

10

TG13

TABLEMi ID for shear modulus in 13

plane

11

TG23

TABLEMi ID for shear modulus in 23

plane

12

TA1

TABLEMi ID for thermal expansion

coefficient in the 1-direction

13

TA2

TABLEMi ID for thermal expansion

coefficient in the 2-direction

14

TA3

TABLEMi ID for thermal expansion

coefficient in the 3-direction

15

UNDEF

None

16

TGE

RS

17

UNDEF(16)

None

TABLEMi ID for structural damping

coefficient

Updated datablocks

195

OEF
Table of element forces
Also contains composite failure indices and analysis types (real and complex), and
SORT1 and SORT2 formats.

Updated Record - DATA

Name

Word

Type

Description

....
ELTYPE =79

Acoustic velocity/pressures in five-sided solid

element (CPYRAM)

CHAR4

ELNAME(2)

Element name: PYRAMPR

TCODE,7 = 0 or 2

Real or Random Response

AX

RS

Acceleration in x

AY

RS

Acceleration in y

AZ

RS

Acceleration in z

VX

RS

Velocity in x

VY

RS

Velocity in y

VZ

RS

Velocity in z

10

PRESSURE

RS

Pressure in dB

TCODE,7 = 1
4

AXR

RS

Acceleration in x real/mag. part

AYR

RS

Acceleration in y real/mag. part

AZR

RS

Acceleration in z real/mag. part

VXR

RS

Velocity in x real/mag. part

VYR

RS

Velocity in y real/mag. part

VZR

RS

Velocity in z real/mag. part

196

Updated datablocks

Name

Word

Type

Description

10

PRESSURE

RS

Pressure in dB

11

AXI

RS

Acceleration in x imag./phase part

12

AYI

RS

Acceleration in y imag./phase part

13

AZI

RS

Acceleration in z imag./phase part

14

VXI

RS

Velocity in x imag./phase part

15

VYI

RS

Velocity in y imag./phase part

16

VZI

RS

Velocity in z imag./phase part

End TCODE,7
....

OES
Table of element
stresses or strains

For all analysis types (real and complex) and SORT1 and
SORT2 formats.

Record 2 - DATA
New ELTYPEs 271-278, 281, 283285, 287-298
ELTYPE =271

Triangle plane strain (CPLSTN3) Center

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

SMAX

RS

Von Mises stress

ELTYPE =272

Quadrilateral plane strain (CPLSTN4) Center and

Corners

Updated datablocks

TERM

CHAR4

CEN

GRID

Grid identification number; 0 for

centroid

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

SMAX

RS

Von Mises stress

197

Words 3 through 8 repeat 5 times

ELTYPE =273

Triangle plane strain (CPLSTN6 ) Center and

Corners

TERM

CHAR4

CEN

GRID

Grid identification number; 0 for

centroid

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

SMAX

RS

Von Mises stress

Words 3 through 8 repeat 4 times

ELTYPE =274

Quadrilateral plane strain (CPLSTN8) Center and

Corners

CHAR4

TERM

CEN

198

Updated datablocks

GRID

Grid identification number; 0 for

centroid

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

SMAX

RS

Von Mises stress

Words 3 through 8 repeat 5 times

ELTYPE =275

Triangle plane stress (CPLSTS3) Center

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

SMAX

RS

Von Mises stress

ELTYPE =276

Quadrilateral plane stress (CPLSTS4) Center and

Corners

TERM

CHAR4

CEN

GRID

Grid identification number; 0 for

centroid

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

SMAX

RS

Von Mises stress

Updated datablocks

199

Words 3 through 8 repeat 5 times

ELTYPE =277

Triangle plane stress (CPLSTS6) Center and

Corners

TERM

CHAR4

CEN

GRID

Grid identification number; 0 for

centroid

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

SMAX

RS

Von Mises stress

Words 3 through 8 repeat 4 times

ELTYPE =278

Quadrilateral plane stress (CPLSTS8) Center and

Corners

TERM

CHAR4

CEN

GRID

Grid identification number; 0 for

centroid

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

SMAX

RS

Von Mises stress

Words 3 through 8 repeat 5 times

200

Updated datablocks

ELTYPE =281

Triangle plane strain (CPLSTN3) Nonlinear format

Center

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

ES

RS

Equivalent stress

EPS

RS

Effective plastic/inelastic strain

ECS

RS

Effective creep strain

EX

RS

Strain in x

10

EY

RS

Strain in y

11

EZ

RS

Strain in z

12

ETXZ

RS

Shear strain in xz

ELTYPE =283

Triangle plane strain (CPLSTN6) Nonlinear format

Center and Corners

TERM

CHAR4

CEN

GRID

Grid identification number; 0 for

centroid

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

ES

RS

Equivalent stress

EPS

RS

Effective plastic/inelastic strain

Updated datablocks

10

ECS

RS

Effective creep strain

11

EX

RS

Strain in x

12

EY

RS

Strain in y

13

EZ

RS

Strain in z

14

ETXZ

RS

Shear strain in xz

201

Words 3 through 14 repeat 4 times

ELTYPE =284

Quadrilateral plane strain (CPLSTN8) Nonlinear

format Center and Corners

TERM

CHAR4

CEN

GRID

Grid identification number; 0 for

centroid

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

ES

RS

Equivalent stress

EPS

RS

Effective plastic/inelastic strain

10

ECS

RS

Effective creep strain

11

EX

RS

Strain in x

12

EY

RS

Strain in y

13

EZ

RS

Strain in z

14

ETXZ

RS

Shear strain in xz

Words 3 through 14 repeat 5 times

202

Updated datablocks

ELTYPE =285

Triangle plane stress (CPLSTS3) Nonlinear format

Center

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

ES

RS

Equivalent stress

EPS

RS

Effective plastic/inelastic strain

ECS

RS

Effective creep strain

EX

RS

Strain in x

10

EY

RS

Strain in y

11

EZ

RS

Strain in z

12

ETXZ

RS

Shear strain in xz

ELTYPE =287

Triangle plane stress (CPLSTS6) Nonlinear format

Center and Corners

TERM

CHAR4

CEN

GRID

Grid identification number; 0 for

centroid

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

ES

RS

Equivalent stress

EPS

RS

Effective plastic/inelastic strain

Updated datablocks

10

ECS

RS

Effective creep strain

11

EX

RS

Strain in x

12

EY

RS

Strain in y

13

EZ

RS

Strain in z

14

ETXZ

RS

Shear strain in xz

203

Words 3 through 14 repeat 4 times

ELTYPE =288

Quadrilateral plane stress (CPLSTS8) Nonlinear

format Center and Corners

TERM

CHAR4

CEN

GRID

Grid identification number; 0 for

centroid

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

ES

RS

Equivalent stress

EPS

RS

Effective plastic/inelastic strain

10

ECS

RS

Effective creep strain

11

EX

RS

Strain in x

12

EY

RS

Strain in y

13

EZ

RS

Strain in z

14

ETXZ

RS

Shear strain in xz

Words 3 through 14 repeat 5 times

204

Updated datablocks

ELTYPE =289

Quadrilateral plane strain (CPLSTN4) Nonlinear

format Center and Corners

TERM

CHAR4

CEN

GRID

Grid identification number; 0 for

centroid

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

ES

RS

Equivalent stress

EPS

RS

Effective plastic/inelastic strain

10

ECS

RS

Effective creep strain

11

EX

RS

Strain in x

12

EY

RS

Strain in y

13

EZ

RS

Strain in z

14

ETXZ

RS

Shear strain in xz

Words 3 through 14 repeat 5 times

ELTYPE =290

Quadrilateral plane stress (CPLSTS4) Nonlinear

format Center and Corners

TERM

CHAR4

CEN

GRID

Grid identification number; 0 for

centroid

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

Updated datablocks

SXZ

RS

Shear stress in xz

ES

RS

Equivalent stress

EPS

RS

Effective plastic/inelastic strain

10

ECS

RS

Effective creep strain

11

EX

RS

Strain in x

12

EY

RS

Strain in y

13

EZ

RS

Strain in z

14

ETXZ

RS

Shear strain in xz

Words 3 through 14 repeat 5 times

ELTYPE =291

Triangle plane strain (CPLSTN3) Hyperelastic Grid

TERM

CHAR4

GRID

ID

Point ID

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

PRESSURE

RS

Pressure

VOLSTR

RS

Volume strain

10

EX

RS

Strain in x

11

EY

RS

Strain in y

12

EZ

RS

Strain in z

13

ETXZ

RS

Shear strain in xz

205

206

Updated datablocks

Words 3 through 13 repeat 3 times

ELTYPE =292

Quadrilateral plane strain (CPLSTN4) Hyperelastic

- Grid

TERM

CHAR4

GRID

ID

Point ID

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

PRESSURE

RS

Pressure

VOLSTR

RS

Volume strain

10

EX

RS

Strain in x

11

EY

RS

Strain in y

12

EZ

RS

Strain in z

13

ETXZ

RS

Shear strain in xz

Words 3 through 13 repeat 4 times

ELTYPE =293

Triangle plane strain (CPLSTN6) Hyperelastic Grid

TERM

CHAR4

GRID

ID

Point ID

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

Updated datablocks

SXZ

RS

Shear stress in xz

PRESSURE

RS

Pressure

VOLSTR

RS

Volume strain

10

EX

RS

Strain in x

11

EY

RS

Strain in y

12

EZ

RS

Strain in z

13

ETXZ

RS

Shear strain in xz

207

Words 3 through 13 repeat 3 times

ELTYPE =294

Quadrilateral plane strain (CPLSTN8) Hyperelastic

- Grid

TERM

CHAR4

GRID

ID

Point ID

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

PRESSURE

RS

Pressure

VOLSTR

RS

Volume strain

10

EX

RS

Strain in x

11

EY

RS

Strain in y

12

EZ

RS

Strain in z

13

ETXZ

RS

Shear strain in xz

208

Updated datablocks

Words 3 through 13 repeat 4 times

ELTYPE =295

Triangle plane stress (CPLSTS3) Hyperelastic Grid

TERM

CHAR4

GRID

ID

Point ID

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

PRESSURE

RS

Pressure

VOLSTR

RS

Volume strain

10

EX

RS

Strain in x

11

EY

RS

Strain in y

12

EZ

RS

Strain in z

13

ETXZ

RS

Shear strain in xz

Words 3 through 13 repeat 3 times

ELTYPE =296

Quadrilateral plane stress (CPLSTS4) Hyperelastic

- Grid

TERM

CHAR4

GRID

ID

Point ID

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

Updated datablocks

SXZ

RS

Shear stress in xz

PRESSURE

RS

Pressure

VOLSTR

RS

Volume strain

10

EX

RS

Strain in x

11

EY

RS

Strain in y

12

EZ

RS

Strain in z

13

ETXZ

RS

Shear strain in xz

Words 3 through 13 repeat 4 times

ELTYPE =297

Triangle plane stress (CPLSTS6) Hyperelastic Grid

TERM

CHAR4

GRID

ID

Point ID

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

PRESSURE

RS

Pressure

VOLSTR

RS

Volume strain

10

EX

RS

Strain in x

11

EY

RS

Strain in y

12

EZ

RS

Strain in z

13

ETXZ

RS

Shear strain in xz

209

210

New datablocks

Words 3 through 13 repeat 3 times

ELTYPE =298

Quadrilateral plane stress (CPLSTS8) Hyperelastic

- Grid

TERM

CHAR4

GRID

ID

Point ID

SX

RS

Normal stress in x

SY

RS

Normal stress in y

SZ

RS

Normal stress in z

SXZ

RS

Shear stress in xz

PRESSURE

RS

Pressure

VOLSTR

RS

Volume strain

10

EX

RS

Strain in x

11

EY

RS

Strain in y

12

EZ

RS

Strain in z

13

ETXZ

RS

Shear strain in xz

Words 3 through 13 repeat 4 times

Word

Name

End ELTYPE

New datablocks
OUGGC
Table of grid contributions.

Type

Description

New datablocks
For frequency analysis types (complex), and SORT1 and SORT2 formats.

Record 0 - HEADER
Name

Type

NAME(2)

CHAR4

Data block name

WORD

No Def or Month, Year, One, One

Word

Description

Word 3 repeats until End of Record

Record 1 - IDENT
Name

Word

Type

Description

ACODE(C)

Device code + 10*Approach Code

TCODE(C)

Table Code

GCODE

Grid contributions code: 1=absolute

(modal), 2=normalized (modal),
-1=absolute (direct), -2=normalized
(direct)

SUBCASE

Subcase number

DCODE

Acoustic dof code (10*grid ID +

direction)

TCODE,1=01

Sort 1

ACODE,4=05

Frequency

FREQ

RS

UNDEF

None

Frequency (Hz)

End ACODE,4
TCODE,1=02

Sort 2

GID

UNDEF

None

Grid ID (0 for TOTAL)

211

212

New datablocks

Name

Word

Type

Description

End TCODE,1
8

DATTYP

Data Type (1=pressure, 2=first

derivative, 3=second derivative)

FCODE

Format Code

10

NUMWDE

Number of words per entry in DATA

record

11

UNDEF(40)

None

51

TITLE(32)

CHAR4

83

SUBTITL(32) CHAR4

115

LABEL(32)

CHAR4

Title
Subtitle
Label

Record 2 - DATA
Name

Word

Type

TCODE,1=01

Sort 1

GID

UNDEF

None

TCODE,1=02

Sort 2

FREQ

RS

UNDEF

None

Description

Grid ID (0 for TOTAL)

Frequency (Hz)

End TCODE,1
TCODE,2=01

Pressure

TCODE,7=01

Real/Imaginary

GCR

RS

Grid contribution real part

GCI

RS

Grid contribution imaginary part

New datablocks

Word

Name

Type

Description

Name

Type

Description

End TCODE,7

Word
TCODE,2=10

First derivative of pressure

TCODE,7=01

Real/Imaginary

GCR

RS

Grid contribution real part

GCI

RS

Grid contribution imaginary part

End TCODE,7

Name

Word

Type

Description

TCODE,2=11

Second derivative of pressure

TCODE,7=01

Real/Imaginary

GCR

RS

Grid contribution real part

GCI

RS

Grid contribution imaginary part

End TCODE,7

Record 3 - TRAILER
Word

Name

Type

NREC

UNDEF(5 )

None

Description
Number of records

OUGPC
Table of panel contributions.
For frequency analysis types (complex), and SORT1 and SORT2 formats.

213

214

New datablocks
Record 0 - HEADER
Name

Type

NAME(2)

CHAR4

Data block name

WORD

No Def or Month, Year, One, One

Word

Description

Word 3 repeats until End of Record

Record 1 - IDENT
Name

Word

Type

Description

ACODE(C)

Device code + 10*Approach Code

TCODE(C)

Table Code

PCODE

Panel contributions code: 1=absolute

(modal), 2=normalized (modal),
-1=absolute (direct), -2=normalized
(direct)

SUBCASE

Subcase number

DCODE

Acoustic dof code (10*grid ID +

direction)

TCODE,1=01

Sort 1

ACODE,4=05

Frequency

FREQ

RS

UNDEF

None

Frequency (Hz)

End ACODE,4
TCODE,1=02

Sort 2

CHAR4

PNAME(2)

End TCODE,1

Panel name (0 for TOTAL)

New datablocks

Name

Word

Type

215

Description

DATTYP

Data Type (1=pressure, 2=first

derivative, 3=second derivative)

FCODE

Format Code

10

NUMWDE

Number of words per entry in DATA

record

11

UNDEF(40)

None

51

TITLE(32)

CHAR4

83

SUBTITL(32) CHAR4

115

LABEL(32)

CHAR4

Title
Subtitle
Label

Record 2 - DATA
Name

Word

Type

TCODE,1=01

Sort 1

CHAR4

PNAME(2)

TCODE,1=02

Sort 2

FREQ

RS

UNDEF

None

Description

Panel name (0 for TOTAL)

Frequency (Hz)

End TCODE,1
TCODE,2=01

Pressure

TCODE,7=01

Real/Imaginary

PCR

RS

Panel contribution real part

PCI

RS

Panel contribution imaginary part

End TCODE,7

216

New datablocks

Name

Word

Type

Description

TCODE,2=10

First derivative of pressure

TCODE,7=01

Real/Imaginary

PCR

RS

Panel contribution real part

PCI

RS

Panel contribution imaginary part

End TCODE,7

Name

Word

Type

Description

TCODE,2=11

Second derivative of pressure

TCODE,7=01

Real/Imaginary

PCR

RS

Panel contribution real part

PCI

RS

Panel contribution imaginary part

End TCODE,7

Record 3 - TRAILER
Word

Name

Type

NREC

UNDEF(5)

None

Description
Number of records

Chapter

15 NX

NASTRAN 7.1 problem

report (PR) fixes

PR#

Problem
Reported

1701255

V6.0

1708954

Problem
Description
Originated
A model produces contact and glue
V6.0
refinement failures and performance
issues.
Same as PR#1701255.

1714716
1735610

V6.1

1744990

V6.1

V6.1

1750083

V7.0

V6.1

1751390

V6.1

V6.1

1756907

V7.0

V4.1

1760330

V6.1

V4.0

1767317

V7.0

V7.0

Same as PR#1701255.
Unable to specify redundant license server
using a comma separated list.
Using SOL 601, the 3D iterative solver
fails during a linear static analysis using
multiple time steps.
SOL 601 lists numerous Jacobian errors for
a single element, but does not list all the
elements that failed.
License borrowing is not fully functional.
For older versions, the work around points
to the local copy of the license file on the
disconnected client.
During a linear contact analysis, CGAP
incorrectly uses separation data from the
INIPENE parameter of the BCTPARM
card.
The msrmode=2 option of the ADMRECVR
case control command is not working
properly causing the ADMRECVR case
control command to solve a much larger
problem than necessary.
A SOL 601 run solved to only 98% of the
applied load with AUTO=3 or 4 and bolt
preload.

218

1769119

V6.1

V6.1

1770633

V7.0

V4.0

1774623

V6.1

V1.0

1777383

V7.0

V7.0

1777426

V7.0

V7.0

1780451

V7.0

V3.0

1784580

V7.0

V1.0

2135045

V6.1

V6.1

2136995

V6.1

V4.0

2137567

V6.1

V6.1

2138258

V6.1

V6.1

2141050

V7.0

V6.1

2141142

V6.1

V6.1

2143793

V7.0

V7.0

A SOL 601 run fails using 64-bit NX

Nastran 6.1. The run does not fail using
32-bit NX Nastran 6.1.
Runs having a large number of active
DRESP2 based constraints resulting
from a large number of specified DRESP2
based constraints and a loose DSCREEN
requirement fail due to insufficient local
memory.
Random analysis in SOL 111 failed on
64-bit platforms because of a memory
coding error.
Runs fail due to incorrect partitioning with
DMP RDMODES.
The MAXRATIO message is
misleading/wrong in DMP RDMODES.
SOL 601 may crash when BUFFSIZE >
8193 with a large model.
A run failed on Linux and reported error
message 3008. The work around is to
specify less than 7.9GB.
A SOL 601 run containing 8-node composite
shell elements and stress output requests
failed.
With only the SDISP case control output
request, sparse data recovery was
incorrectly turned off, resulting in an
excessively large problem solution.
For a conical shell, the azimuthal locations
for stress output are limited to four places.
When the RMAXMIN option NPAVG is
set greater than 1, the disk space required
to solve NX Nastran 6.1 and NX Nastran
7 models becomes quite large. If the
problem size is large, the disk requirement
can exceed that available on even large
systems.
Columns greater than 16777217 (2^24) are
not included in the OUTPUT4 file.
The .op2 file is not converted from big
endian to little endian correctly when the
integer IDs are greater than 2^23.
During SOL 111 restart runs, geometry
data blocks are not written to the .op2 file.

219

2145154

P7.0

V2.0

6161112

V6.1

V4.0

6202164
6205065

6205381

V7.0

V1.0

6210057

V7.0

V6.1

6211625

V7.0

V1.0

6219609

V6.1

V6.1

6225650
6229910

6241419

V6.1

V1.0

6244819

V7.0

V5.1

6247629

V7.0

V6.1

6250642

V7.0

V7.0

6252275

V7.0

V7.0

Runs using the element iterative solver

produce incorrect results when multiple
subcases with multiple GRAV entries are
present and the first GRAV entry is used
in all subcases.
The error message prompted when contact
is not found in a linear contact analysis is
inadequate.
Same as PR#1751390.
Same as PR#1701255.
Jobs including both RMS responses and
other types of frequency responses like FR
and PSD are likely to generate incorrect
sensitivity analysis results for some
responses under certain conditions.
SOL 601 does not support variable node
pyramid and tetra elements in surface
contact.
For solves that include superelements,
non-existent referenced DRESPi are
not trapped and related constraints are
ignored.
An invalid warning message that MATHP
does not support TABi and TABD occurs.
Same as PR#1751390.
Same as PR#6161112.
The existence of a comma at the end
of a SET case control command is not
recognized, which results in the next
case control command being ignored. The
comma at the end of a SET case control
command is now trapped as a syntax error.
OLOAD results are not written to an
.op2 file for a subcase that includes stress
stiffening and bolt preload conditions.
A SOL 601 solve may hang when rigid links
and BGSET are present.
AUTOMPC fails when the GN grid of an
RBE2 is the only grid in the O-set.
Glue separation distance messages are
sometimes reported incorrectly. A new
reporting method has been created which
only reports the ten largest values for each
pair.

220

6254705

V7.0

V7.0

6255599

V7.0

V7.0

6261459

P7.1

V7.1

6263081

V7.0

V1.0

6264879

V6.0

V1.0

6268819

V7.0

V7.0

6269008

V6.0

6272973

V7.0

V1.0

6274156

V7.0

V7.0

6274522

V7.0

V1.0

6281779

V7.0

V1.0

A SOL 110 rotor dynamics solve creates an

empty .csv file when using the new mode
tracking algorithm and the user requests
Campbell diagram data.
Using MFLUID with VMOPT=2 produces
the incorrect modal effective mass.
A memory error occurs on multiple
subcases. The pipe opened for executing
the command to get memory is not being
closed.
During a SOL 111 run, the sorting/look-up
code caused a failure and issued warning
message 979 when processing all of the
XYPEAK output requests.
When using SORT2, OLOAD results are
not written into an .op2 file.
Incorrect results are produced by a linear
contact analysis that uses the iterative
solver when all bodies are restrained to
prevent rigid body motion and contact does
not exist between any of the bodies.
A SOL 601 solve fails when the number of
PELAS elements exceeds 9999.
For certain circumstances when insufficient
memory is available, a run can produce
corrupt element stress tables without
warning. A FATAL error is now issued
when insufficient memory is available for
stress table processing.
A model containing glue does not produce
six rigid body modes.
Direct frequency analysis (SOL 108) fails
to ignore FREQ3/FREQ4 bulk entries as
stated in the Quick Reference Guide. These
bulk entries are intended to only be valid
for modal frequency analyses (SOL 111,
146, and 200 (MFREQ)).
When solving a random response solution
using mem=estimate, the run fails and
prompts system fatal message 3007
(DDRMM). The message has now been
enhanced to inform the user how to better
allocate memory.

221

6282350

V7.0

V1.0

6282820

V7.0

V3.0

6284706

V7.0

V1.0

6285173

V7.0

V6.1

6286416

V7.0

V1.0

6292253

V6.1

V1.0

6293567

V7.0

V6.0

6298909

V7.0

V7.0

6299413

V6.1

V6.1

6302615

V7.0

V6.1

A SOL 106 run produces system fatal

message 3002 and does not write results to
the .op2 file. The problem has been traced
to the load factor for subcase 2 exceeding
1.0. This causes SUBCASE 2 to be solved
twice. Resolving SUBCASE 2 produces too
many results and causes the end of file
problem.
When a model is defined using connection
dof, the modes in the .op2 file differ from
the modes in the RFI file.
A SOL 106 run produces error message
3204 unexpectedly. The following
information has been added to the error
message: "This message will also be output
if the case control LOAD card references
only SPCD cards. If this is the case, this
message can be ignored as there are no
follower forces associated with SPCD
loading."
When using SOL 601 with element birth
and death specified for CDAMP1 or
CDAMP2, all CDAMP1 and CDAMP2
elements with the same PID are mistakenly
removed.
The virtual mass defined with MFLUID
produces results that are not independent
of element grid ordering.
Strains for CTRIA6 elements are reported
incorrectly when PARAM, OMID,YES
is used to print results in the material
coordinate system.
When generating element forces using
EXTOUT, error message 3008 incorrectly
occurs.
BCPROP does not trap non-existent PIDs
causing an error to occur later in the run.
A SOL 601,129 large displacement analysis
does not converge because the CBUSH1D
node-to-node damper effect is incorrect.
In a SOL 601, 106 run, reaction forces are
missing when the grids are part of a 2D
contact region and there are constraints on
the grids.

222

6303510

V7.0

V7.0

6305946

V7.0

V5.0

6306164

V7.0

V7.0

6313421

P7.1

V1.0

6314316

V7.0

V1.0

6317037
6319514
6321451
6322247

V7.0

V1.0

6332135

P7.1

V7.0

6332167

P7.1

V7.0

6336763

P7.1

V7.0

6338526

P7.1

V7.0

Several additional data items were added

to the DDAM input file for NX Nastran 7.
There was a problem reading old files input
without the additional entries present.
This has been corrected and the additional
data entries do not need to present. If they
have not been entered, a reasonable default
will be used.
An MFLUID enclosed volume fatal error
occurs when a fluid cavity (void) is modeled
in an infinite fluid and the VMOPT=2
option is used.
Processing of U6 dof (defined via
USET/USET1 bulk data) fails when
generating residual vectors.
MCEIG analysis fails when earlier subcases
relating to eigenvalue analysis (such as
frequency response) are present.
The combination of MFLUID with the
SPCD enforced motion capability works
incorrectly. This has been corrected for
the constraint mode method of enforced
motion (SYSTEM(422) / ENFMOTN = 0,
the default).
Same as PR#6303510.
Same as PR#1751390.
Same as PR#6332167.
CHBDYE end area SIDE selection on
CTUBE is unknown. The error occurs
when the SIDE field on the CHBDYE bulk
entry is 3 or 4 (indicating the point sides).
Grounding problems occur when
overlapping shells are glued together with
no offsets.
A contact analysis model containing
acceleration loads fails when using the
element iterative solver.
In SOL 111, element forces for CDAMPi
and CVISC elements are calculated
incorrectly.
Windows 64 fails during a SOL 112 restart
run because of a pivot ratio error.

223

6344799

V7.0

V7.0

6350305

V7.0

V5.0

6357654

V7.0

V3.0

6358791

V7.0

V1.0

Certain optimization problem types fail

on the Windows 64 platform. The ilp64
version of the Windows 64 platform and
other platforms do not have this problem.
A SOL 112 performance/disk usage error
occurs when generating the right-hand side
constraint forces for SPCD enforced motion
and calculating SPC forces.
A SOL 601 run gives incorrect results when
PCOMP has only one layer.
A run produces fatal error 9056. The error
message is not adequately descriptive. The
error message has been updated to: "This
error might also be caused by no residual
subcase specified in a superelement model.

Chapter

16 System description summary

Beginning with this release, the list of supported systems is included in the
README.txt file located in the NX Nastran installation under the nxn7p1 directory.