You are on page 1of 303

NX Nastran 9 Release

Guide
Contents

Proprietary & Restricted Rights Notice

NX Nastran 9 summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1


NX Nastran 9 summary of changes to default settings and inputs . . . . . . . . 1-1

Dynamics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
AF mode normalization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
EIGRL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
EIGR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Laminate ply results in transient dynamics . . . . . . . . . . . . . . . . . . . . . . 2-20
PCOMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
PCOMPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
SOL 111 solution methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
RMS von Mises stress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
Relative motion datablock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36
Residual vector defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
RESVEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39

Rotor dynamics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43


Rotor dynamic forces in SOL 101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
Dependent bearing properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
ROTORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52
CBEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
PBEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59
CBEAR force output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63

Multi-step nonlinear solution 401 . . . . . . . . . . . . . . . . . . . . . . . . . . 4-65


New multi-step nonlinear solution 401 . . . . . . . . . . . . . . . . . . . . . . . . . 4-65

Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-83
Equivalent Radiated Power as Design Response . . . . . . . . . . . . . . . . . . . 5-83
DRESP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-87
Expanding optimization for larger problems . . . . . . . . . . . . . . . . . . . . . . 5-98

Advanced nonlinear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-101


Plastic-cyclic material model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-101
Bolt preload with 3D solid elements . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-102
Edge-to-edge glue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-103
New rotational load RFORCE1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-103

Element enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-105

CTETRA stress recovery in SOLs 106 and 129 . . . . . . . . . . . . . . . . . . . . 7-105

Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-107

Line numbers in PUNCH file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-107


Multiple ACCEL1 bulk entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-107
DMAP compiler warning messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-109
Numerical precision of matrix data written to OP4 files . . . . . . . . . . . . . . 8-109
EXTSEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-110
MBDEXPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-120

Glue stiffness output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-157

Glue stiffness output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-157

RDMODES improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-159

RDMODES improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-159

Upward compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-161

Updated data blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-161


New data blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-186
Updated modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-267
New modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-273

NX Nastran 9 Problem Report (PR) fixes . . . . . . . . . . . . . . . . . . . . 12-283

NX Nastran 9 Problem Report (PR) fixes . . . . . . . . . . . . . . . . . . . . . . . 12-283

System description summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-297

System description summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-297


Proprietary & Restricted Rights Notice

2013 Siemens Product Lifecycle Management Software Inc. All Rights Reserved.
This software and related documentation are proprietary to Siemens Product
Lifecycle Management Software Inc. Siemens and the Siemens logo are registered
trademarks of Siemens AG. NX is a trademark or registered trademark of Siemens
Product Lifecycle Management Software Inc. or its subsidiaries in the United
States and in other countries.
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, stoledo@tau.ac.il. 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 (TAUCS)
Proprietary & Restricted Rights Notice

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.
Chapter

1 NX Nastran 9 summary of changes

NX Nastran 9 summary of changes to default settings and


inputs

Default setting changes

Input type Default change


Keywords None
Nastran statement The default for system cell 539 changes from 0 to 3.
File management
None
statements
Executive control
None
statements
For the RESVEC case control command, if one
of the SYSTEM, NOSYSTEM, COMPONENT,
Case control commands NOCOMPONENT, BOTH or YES, and NO describers
is not specified, the describer that the software uses as
the default now depends on the solution type.
The RESVEC and RESVINER parameters no longer
determine the default behavior for requesting residual
Parameters
vectors. This default behaviour is controlled by the
RESVEC case control command.
Bulk entries None

Nastran statement changes


System System cell Description of
System cell description
cell name change
Added
in-core SMP
462 Solution options for SOL 111. option when
SYSTEM(462)
= 1.
2 NX Nastran 9 summary of changes to default settings and inputs

System System cell Description of


System cell description
cell name change
Added options
and changed
539 Selects optimization enhancements.
default from 0
to 3.
Selects SSG1 performance
542 New system cell
improvements.
Determines if the RMS von Mises stress
is computed when the stress RMS output
550 RMSVM New system cell
is requested with the RMS describer on
the STRESS case control command.
Longest edge to shortest edge aspect
553 QAD_AR ratio GEOMCHECK check value for New system cell
CQUAD4 elements.
Determines if the line numbers are
560 PCHLN New system cell
included in the PUNCH file.
Taper ratio GEOMCHECK check value
563 Q8_TAPER New system cell
for CQUAD8 elements.
Minimum interior angle GEOMCHECK
564 Q8_IAMIN New system cell
check value for CQUAD8 elements.
Maximum interior angle GEOMCHECK
565 Q8_IAMAX New system cell
check value for CQUAD8 elements.
Longest edge to shortest edge aspect
566 Q8_AR ratio GEOMCHECK check value for New system cell
CQUAD8 elements.
Edge point length ratio GEOMCHECK
567 Q8_EPLR New system cell
check value for CQUAD8 elements.
Skew angle GEOMCHECK check value
568 Q8_SKEW New system cell
for CQUAD8 elements.
Longest edge to shortest edge aspect
569 TA6_AR ratio GEOMCHECK check value for New system cell
CTRIA6 elements.
Edge point length ratio GEOMCHECK
570 TA6_EPLR New system cell
check value for CTRIA6 elements.
Minimum interior angle GEOMCHECK
571 TA6_IAMN New system cell
check value for CTRIA6 elements.
Maximum interior angle GEOMCHECK
572 TA6_IAMX New system cell
check value for CTRIA6 elements.
Suppresses warning messages from the
DMAP compiler that occur because of
580 New system cell
undefined inputs or outputs to a DMAP
command
Turns off the error trap which occurs
581 when an SPCD is defined with a bolt New system cell
preload.
NX Nastran 9 summary of changes to default settings and inputs 3

File management statement changes


No changes to file management statements.

Executive control statement changes


Executive
Executive control statement
control Description of change
description
statement
Added QAD_AR geometry check
for CQUAD4 elements.

Added Q8_TAPER, Q8_IAMIN,


Q8_IAMAX, Q8_AR, Q8_EPLR,
Specifies tolerance values for and Q8_SKEW geometry checks
GEOMCHECK
finite element geometry tests. for CQUAD8 elements.

Added TA6_AR, TA6_EPLR,


TA6_IAMN, and TA6_IAMX
geometry checks for CTRIA6
elements.
Specifies the solution
SOL sequence or main subDMAP Added 401 MSTEP solution.
to be executed.

Case control command changes(1)


Case control
Case control command description Description of change
command
ELFORCE Undocumented
ELSTRAIN Undocumented
ELSTRESS Undocumented
Requests elastic strain at grid points
ELSTRN New case control command
on elements.
Requests elastic strain at Gauss
GELSTRN New case control command
points.
GSTRAIN Requests strain at Gauss points. New case control command
GSTRESS Requests stress at Gauss points. New case control command
Requests thermal strain at Gauss
GTHSTRN New case control command
points.
Selects the parameters used for
NLCNTL New case control command
static analysis in SOL 401.
Requests temperature output at grid
OTEMP New case control command
points.
PAGE Undocumented
4 NX Nastran 9 summary of changes to default settings and inputs

Case control
Case control command description Description of change
command
If one of the SYSTEM,
NOSYSTEM, COMPONENT,
NOCOMPONENT, BOTH or
Controls the computation of residual YES, and NO describers is
RESVEC
vectors. not specified, the describer
that the software uses as the
default now depends on the
solution type.
Defines whether or not a subcase
SEQDEP is sequentially dependent on the New case control command
previous subcase.
Requests thermal strain at grid
THSTRN New case control command
points on elements.
The OUTPUT(PLOT) case control command section is removed from the NX
Nastran Quick reference guide.

(1) Case control command applicability changes are not included.

Parameter changes(2)
Parameter Parameter description Description of change
Used to specify the user-defined scale
AFNORM factor in AF (amplitude-frequency) New parameter
normalization.
Controls the number of digits of precision
for matrix data written to an OP4 file for
DIGITS New parameter
the EXTSEOUT and MBDEXPORT case
control commands.
When F56=YES, an *.f56 file is written
in addition to the *.f06 file. The input file
echo, grid point singularity table, results
data, and eigenvalue and eigenvector data
are written to the *.f56 file instead of the
F56 New parameter
*.f06 file. This reduces the information
written to the .f06 file such that messages,
warnings and errors are more easily
viewed. The parameter F56 is supported
by all solutions.
Requests the glue stiffness matrix in
DMIG format. The solver writes the glue
KGGLPCHstiffness matrix into a PUNCH file in the New parameter
format required for DMIG (Direct Matrix
Input at Grids).
NX Nastran 9 summary of changes to default settings and inputs 5

(2) Parameter applicability changes are not included.

Item code changes


Item code Item code description Description of change
102 Force on CBEAR elements. New item code

Degree-of-freedom set changes


No changes to degree-of-freedom sets.

Bulk entry changes


Bulk entry Bulk entry description Description of change
Added element type 3 which
Selects the elements to be included
BOLT supports modeling bolts with
in the bolt preload calculation.
solid elements in SOL 601.
Defines a set of structural responses
that are used for the objective and/or
DRESP1 Added ERP response type.
design constraints, or for sensitivity
analysis purposes.
Defines data needed to perform real Added the AF eigenvector
EIGR
eigenvalue analysis. normalization method.
Defines data needed to perform
Added the AF eigenvector
EIGRL real eigenvalue analysis with the
normalization method.
Lanczos method.
Defines a group of grid points,
GROUP New bulk data entry
elements, or physical properties.
Specifies properties for a material
MATPLCY New bulk data entry
used to model cyclic plasticity.
Defines solution control parameters
NLCNTL New bulk data entry
for SOL 401.
Added NOMVAL field which
defines a nominal relative
Defines stiffness and viscous displacement or relative force
PBEAR damping matrices for bearing value when stiffness or damping
connection. are dependent on speed and
relative displacement or speed
and relative force.
Specifies the dependence of the
radius of the yield surface (stress
PLCYISO radius) on accumulated effective New bulk data entry
plastic strains for the plastic-cyclic
material.
6 NX Nastran 9 summary of changes to default settings and inputs

Bulk entry Bulk entry description Description of change


Specifies the dependence of the back
PLCYKIN stresses on the plastic strains for the New bulk data entry
plastic-cyclic material.
Specifies the rupture criterion for
PLCYRUP New bulk data entry
the plastic-cyclic material.
Applies rotational velocities and
RFORCE1 New bulk data entry
accelerations to specific grid-points.
Added THRSHOLD and
MAXITER fields, which
specify the threshold value for
Defines rotor dynamics solution convergence and the maximum
ROTORD
options. number of iterations when
stiffness or damping defined on
a PBEAR entry is dependent on
displacement or force.
Defines the time step intervals for
TSTEP1 New bulk data entry
SOL 401.
Added KDAMP and KUPDATE
fields, which support including
Defines parametric controls and data differential stiffness in the
TSTEPNL for nonlinear transient structural or calculation of structural
heat transfer analysis. damping and specify the
method for controlling stiffness
updates.
Chapter

2 Dynamics

AF mode normalization
Beginning with NX Nastran 9.0, the EIGR and EIGRL bulk entries now include
the AF (Amplitude-Frequency) mode normalization option. You can select the AF
normalization option with the Automatic Householder, Lanczos, and RDMODES
eigenvalue methods.
For example,
EIGRL,100,1.0,900.0,,,,,AF

requests all modes from 1.0 Hz to 900.0 Hz using AF normalization with the
Lanczos eigenvalue extraction method.
Another example with the EIGR bulk entry,
EIGR,1,AHOU,1.0,900.0 +
+ AF

requests all modes from 1.0 Hz to 900.0 Hz using AF normalization with the
automatic Householder eigenvalue extraction method.
With AF normalization, the normalized eigenvectors are given by:
(C / w max) {x}
where C is an optional user-defined scale factor, w is the natural frequency for the
mode, max is the magnitude of the maximum grid point translation for the mode,
and {x} is the un-normalized eigenvector for the mode.
The optional user-defined scale factor, C, is specified with the AFNORM parameter.
The default for the AFNORM parameter is 1.0.
If the natural frequency is very small, AF normalization will revert to MAX
normalization rather than risk overflow. The tolerance to determine a small
frequency is 1.0e-4.
If you use the AF or MAX normalization with RDMODES for large models
with output requested at relatively few degrees-of-freedom (DOF), the sparse
eigenvector recovery greatly improves the RDMODES performance by computing
eigenvectors only at the requested DOF. Therefore, the maximum in the AF
normalization holds over the computed DOF only; changing the output DOF may
8 AF mode normalization

change the resulting normalization. If normalization over all DOF is critical, the
sparse eigenvector recovery may be deactivated with PARAM,RDSPARSE,NO, but
this will significantly impact performance.
EIGRL 9
Real Eigenvalue Extraction Data, Lanczos Method

EIGRL Real Eigenvalue Extraction Data, Lanczos Method

Defines data needed to perform real eigenvalue (vibration or buckling) analysis


with the Lanczos method.

Format:

1 2 3 4 5 6 7 8 9 10
EIGRL SID V1 V2 ND MSGLVL MAXSET SHFSCL NORM
option_1 = value_1 option_2 = value_2, etc.

Example:
EIGRL 1 0.1 3.2 10
NORM=MAX NUMS=2

Fields:

Field Contents

SID Set identification number. (Unique Integer>0)

V1, V2 For vibration analysis: frequency range of interest. For buckling


analysis: eigenvalue range of interest. See Remark 4. (Real or blank,
5 1016 V1 <V2 5. 1016)

ND Number of roots desired. See Remark 4. (Integer>0 or blank)

MSGLVL Diagnostic level. (0 Integer 4; Default = 0)

MAXSET Number of vectors in block or set. Default is machine dependent.


See Remark 14.

SHFSCL Estimate of the first flexible mode natural frequency. See Remark
10. (Real or blank)

NORM Method for normalizing eigenvectors (Character: MASS, MAX,


or AF)

MASS Normalize to unit value of the generalized mass. Not


available for buckling analysis. (Default for normal
modes analysis.)
10 EIGRL
Real Eigenvalue Extraction Data, Lanczos Method

Field Contents

MAX Normalize to unit value of the largest displacement


in the analysis set. Displacements not in the analysis
set may be larger than unity. (Default for buckling
analysis.)

AF Amplitude-Frequency normalization method. See


Remark 20.

ALPH Specifies a constant for the calculation of the frequencies (Fi) at the
upper boundary segments for the fdmodes and hdmodes parallel
methods or the multisegment serial method based on the following
formula: (0.0 < Real 1.0; Default = 1.0).

ALPH < 1.0,

ALPH = 1.0,

The number of frequency segments N is defined as follows:

FDMODES: N is defined either by the NUMSEG keyword or the


NASTRAN NUMSEG statement and is limited to 16. See Remark 13.

HDMODES: N is defined by the NCLUST keyword. See Remark 13.

Multisegment serial method: N is defined either by the NUMS field


on the EIGRL entry or the NUMSEG keyword. See Remark 19.

Fi Frequencies at the upper boundary of each i-th segment for the


fdmodes parallel method or the multisegment serial method. Fi is
optionally used instead of ALPH to explicitly define the boundaries.
Fi cannot be used with hdmodes.

The number of Fi boundaries = N 1 where the number of segments


N is defined above in the description of ALPH. (Real or blank;
V1<F1<F2<... F15<V2)

NUMS Number of frequency segments for the multisegment serial method.


(0 < Integer 16; Default = 1) See Remark 19.
EIGRL 11
Real Eigenvalue Extraction Data, Lanczos Method

Field Contents

option_i= Assigns a value to the fields above except for SID. ALPH, NUMS, and
value_I Fi must be specified in this format. V1, V2, ND, MSGLVL, MAXSET,
SHFSCL, and NORM may be specified in this format as long as their
corresponding field is blank in the parent entry.

Remarks:

1. Real eigenvalue extraction data sets must be selected with the Case Control
command METHOD = SID.

2. The units of V1 and V2 are cycles per unit time in vibration analysis, and are
eigenvalues in buckling analysis. Each eigenvalue is the factor by which the
prebuckling state of stress is multiplied to produce buckling in the shape defined
by the corresponding eigenvector.

3. NORM = MASS is ignored in buckling analysis and NORM = MAX will be


applied.

4. The roots are found in order of increasing magnitude; that is, those closest to
zero are found first. V2 should be set to a physically meaningful upper bound on
the desired eigenvalues, or omitted. Extremely large values of V2 may result in
a fatal message, depending on the model.

If ND is specified, it is possible that the requested eigenvalues include some but


not all from a set of multiple eigenvalues (for example, if ND=3 and there are
six rigid modes). In this case, the modal space spanned by the eigenvectors is
not uniquely defined, which is undesirable in frequency or transient response.
In this situation, the eigensolution is computed as requested, accompanied by
a warning message. Alternatively, setting system(509)=1 allows the READ
module to increase the number of computed eigenpairs automatically to include
the entire set.
The number and type of roots to be found can be determined from Table 2-1.

Table 2-1. Number and Type of Roots Found with EIGRL Entry

V1 V2 ND Number and Type of Roots Found


V1 V2 ND Lowest ND or all in range, whichever is smaller.
V1 V2 blank All in range
V1 blank ND Lowest ND in range [V1,+]
12 EIGRL
Real Eigenvalue Extraction Data, Lanczos Method

Table 2-1. Number and Type of Roots Found with EIGRL Entry

V1 V2 ND Number and Type of Roots Found


V1 blank blank Lowest root in range [V1,+]
blank blank ND Lowest ND roots in [-,+]
blank blank blank Lowest root. See Remark 11.
blank V2 ND Lowest ND roots below V2

blank V2 blank All below V2

5. In vibration analysis, if V1<0.0, the negative eigenvalue range will be searched.


(Eigenvalues are proportional to Vi squared; therefore, the negative sign would
be lost.) This is a means for diagnosing improbable models. In buckling analysis,
negative V1 and/or V2 require no special logic.

6. Eigenvalues are sorted on order of magnitude for output. An eigenvector is


found for each eigenvalue.

7. MSGLVL controls the amount of diagnostic output during the eigenvalue


extraction process. The default value of zero suppresses all diagnostic output. A
value of one prints eigenvalues accepted at each shift. Higher values result in
increasing levels of diagnostic output.

8. MAXSET is used to limit the maximum block size. It is otherwise set by the
region size or by ND with a maximum size of 15. It may also be reset if there is
insufficient memory available. The default value is recommended.

9. In vibration analysis, if V1 is blank, all roots less than zero are calculated. Small
negative roots are usually computational zeroes which indicate rigid body modes.
Finite negative roots are an indication of modeling problems. If V1 is set to zero,
negative eigenvalues are not calculated.

10. A specification for SHFSCL may improve performance, especially when large
mass techniques are used in enforced motion analysis. Large mass techniques
can cause a large gap between the rigid body and flexible frequencies. If this field
is blank, a value for SHFSCL is estimated automatically.

11. On occasion, it may be necessary to compute more roots than requested to


ensure that all roots in the range have been found. However, this method will
not output the additional roots.
EIGRL 13
Real Eigenvalue Extraction Data, Lanczos Method

12. NASTRAN SYSTEM(146) provides options for I/O in sparse method only:

Table 2-2. SYSTEM(146) Options


SYSTEM(146) Description
Increase memory reserved for sparse method by
2
approximately 100%.
Increase memory reserved for sparse method by
3
approximately 300%.
Increase memory reserved for sparse method by
4
approximately 400%.

13. For the fdmodes distributed parallel method, the frequency range between V1
and V2 is subdivided into segments and analyzed in parallel. V1 and V2 must
be defined, and the number of frequency segments must be specified with the
NUMSEG keyword or the NASTRAN NUMSEG statement. NUMSEG should
equal the number of processors which is defined with the DMP keyword. If
NUMSEG and DMP are not the same, DMP will overwrite the NUMSEG value.
The upper frequencies of each segment may be generated automatically by
ALPH or specified directly in Fi. If both are specified, then Fi takes precedence
over ALPH as long as they are consistent. ALPH, if multiplied by 100, may
also be specified on FRQSEQ keyword of the NASTRAN statement. For best
performance, ND should not be used with fdmodes. The segment boundaries are
distributed automatically in units of frequency, not cycles.

For the gdmodes distributed parallel method, the geometry is partitioned into
segments and analyzed in parallel. ND, V1 and V2 can all be used with gdmodes.
On the rare occasion that the geometry partitioning fails, gdmodes will revert to
the fdmodes method if the keyword gpart=1 (default).
For the hdmodes distributed parallel method, the frequency range between V1
and V2 is subdivided into segments, as in fdmodes. Also as in fdmodes, V1
and V2 must be defined. However, the number of segments equals the value
of the NCLUST keyword. If desired, the upper frequencies of each segment
may be adjusted using ALPH; they cannot be specified directly in Fi. For best
performance, ND should not be used with hdmodes.
The rdmodes distributed parallel method uses substructuring technology for very
large scale normal modes problems. The rdmodes method generally computes
fewer modes with lower accuracy compared to standard Lanczos solution in
order to gain performance. The rdmodes method requires V1 and V2, but ND
should not be used. This method is not supported in buckling solutions.
14 EIGRL
Real Eigenvalue Extraction Data, Lanczos Method

Table 2-3. EIGRL Input Summary for DMP Methods


Modal Solution (SOL 103) Buckling Solution (SOL 105)
V1 and V2 are required. V1 and V2 are required.
fdmodes
ND is not supported. ND is not supported.
ND, V1 and V2 can all be
ND, V1 and V2 can all be used. If ND is not specified,
gdmodes
used. See Table 2-1. both V1 and V2 must be
specified.
V1 and V2 are required. V1 and V2 are required.
hdmodes
ND is not supported. ND is not supported.
V1 and V2 are required.
rdmodes Not supported.
ND is not supported.

14. Increasing MAXSET may improve performance for large problems where a
large number of eigenvalues are being found. The default is 7 on all machines.
SYSTEM(263) may be set in an rcfile to effectively modify the default; however
the setting on the EIGRL entry always takes precedence.

15. SYSTEM(196), keyword SCRSAVE, controls reuse of scratch files when segment
logic is invoked. SYSTEM(196) is useful only when multiple frequency segments
are requested on a Lanczos run. (Multiple frequency segments can be requested
via the NUMS field in the EIGRL entry and by SYSTEM(197).) Each frequency
segment requires a minimum of three scratch files. When multiple frequency
segments are used on a single processor computer then each frequency segment
is solved serially. In this case, it makes sense to let segment #2 use the scratch
files which were used by segment #1 since work for segment #1 has been
completed (otherwise it wouldnt be working on #2). Similarly, when work for
segment #2 is finished, segment #3 should be able to use #2s scratch files.
SYSTEM(196)=1 allows such file reuse and is considered a safe default on
Version 70 and later systems.

16. The new buckling shift logic in Version 70.5 tends to shift to 1.0 first. The logic
may have difficulty finding the lowest ND roots if a problem requests a small
number of roots (ND) when there are thousands of roots below 1. In this case
either the loading should be scaled, SHFSCL specified, or a smaller frequency
range requested.

17. Because Lanczos performance is tuned for medium to large problems, this has
caused difficulties with very small problems. Thus, by default, on problems
with fewer than 20 degrees-of-freedom when the LAN method is selected, the
method is switched to AHOU. The criteria for automatic switching is controlled
by SYSTEM(359) on the NASTRAN entry.
EIGRL 15
Real Eigenvalue Extraction Data, Lanczos Method

18. The parameter input VMOPT=2 should not be used with MAX normalization.
VMOPT=2 will only yield correct results with MASS normalization.

19. The multisegment serial method subdivides the frequency range between V1
and V2 into segments, as in fdmodes. Unlike fdmodes, the multisegment method
analyzes each segment in turn on one processor only. V1 and V2 must be
defined, and ND must not be defined. The number of segments may be specified
in NUMS, with the NUMSEG keyword, or with the NASTRAN NUMSEG
statement. If both NUMS and NUMSEG are specified, NUMS takes precedence.
Unlike the parallel methods, the multisegment serial method is not meant to
decrease solution times. It is sometimes used to solve an eigenvalue solution
which otherwise has numerical problems.

20. In AF (amplitude-frequency) normalization, the normalized eigenvectors are


given by:

(C / w max) {x}
where C is an optional user-defined scale factor, w is the natural frequency for
the mode in Hz, max is the magnitude of the maximum grid point translation for
the mode, and {x} is the un-normalized eigenvector for the mode. The optional
user-defined scale factor, C, is specified with the AFNORM parameter.
16 EIGR
Real Eigenvalue Extraction Data

EIGR Real Eigenvalue Extraction Data

Defines data needed to perform real eigenvalue analysis.


Format:
1 2 3 4 5 6 7 8 9 10
EIGR SID METHOD F1 F2 NE ND
NORM G C

Example:
EIGR 13 LAN 12

Fields:

Field Contents

SID Set identification number. (Unique Integer>0)

METHOD Method of eigenvalue extraction.(Character)

Modern Methods:

LAN Lanczos Method

AHOU Automatic selection of HOU or MHOU method. See


Remark 13.

Obsolete Methods:

INV Inverse Power method.

SINV Inverse Power method with enhancements.

GIV Givens method of tridiagonalization.

MGIV Modified Givens method.

HOU Householder method of tridiagonalization.

MHOU Modified Householder method.

AGIV Automatic selection of METHOD = GIV or MGIV.


See Remark 13.
EIGR 17
Real Eigenvalue Extraction Data

Field Contents

NORM Method for normalizing eigenvectors. (Character: MASS, MAX,


AF, or POINT; Default = MASS)

MASS Normalize to unit value of the generalized mass.


(Default)

MAX Normalize to unit value of the largest component in the


analysis set.

AF Amplitude-Frequency normalization method. See


Remark 20.

Supported when METHOD=LAN or AHOU.

POINT Normalize to a positive or negative unit value of the


component defined in fields 3 and 4. POINT is not
supported when METH=LAN. (Defaults to MASS if
defined component is zero).

G Grid or scalar point identification number. Required only if NORM


= POINT. (Integer>0)

C Component number. Required only if NORM = POINT and G is a


geometric grid point. (1 Integer 6)

Table 2-4. Relationship Between METHOD Field and Other Fields for
Obsolete Methods
METHOD Field
Field
INV or SINV GIV, MGIV, HOU, or MHOU

F1, F2 Frequency range of interest. F1 must be Frequency range of interest. Eigenvectors are
input. If METHOD = SINV and ND, is found with natural frequencies that lie in the
blank, then F2 must be input. (Real 0.0) range between F1 and F2. If ND is not blank,
at most ND eigenvectors are found. (Real 0.0;
F1<F2)

NE Estimate of number of roots in range Not used.


(Required for METHOD = INV). Not
used by SINV method. (Integer>0)
18 EIGR
Real Eigenvalue Extraction Data

Table 2-4. Relationship Between METHOD Field and Other Fields for
Obsolete Methods
METHOD Field
Field
INV or SINV GIV, MGIV, HOU, or MHOU

ND Desired number of roots. If this field is Desired number of eigenvectors. If ND is zero,


blank and METHOD = SINV, then all the number of eigenvectors is determined from
roots between F1 and F2 are searched and F1 and F2. If all three are blank, then ND is
the limit is 600 roots. (Integer>0, Default automatically set to one more than the number
is 3 NE for METHOD = INV only.) of degrees-of-freedom listed on SUPORTi
entries. (Integer 0; Default = 0)

Remarks:

1. The EIGR entry must be selected with the Case Control command METHOD =
SID.

2. See Eigenvalue Extraction Methods in the NX Nastran Basic Dynamic Analysis


Users Guide for a discussion of method selection.

3. The units of F1 and F2 are cycles per unit time.

4. The continuation entry is optional. If the continuation entry is not specified,


then mass normalization is performed.

5. The contemporary methods are LAN and AHOU. The other methods are in a
maintenance-only status, with no enhancements planned for them. They may be
eliminated in a future release.

6. The LAN method is the most general-purpose method, and may be used on
both small- and large-size problems. It takes advantage of sparsity of input
matrices, leading to greater efficiency on large-size problems. Because Lanczos
performance is tuned for medium to large problems, this has caused difficulties
with very small problems. Thus, by default, on problems with fewer than 20
degrees-of-freedom when the LAN method is selected, the method is switched
to AHOU. The criteria for automatic switching is controlled by SYSTEM(359)
on the NASTRAN entry. The NE, G, and C fields are ignored for the LAN
method. The NORM field may be set to MASS (the default value) or NORM. The
conventions used when both the Fi and ND fields are specified are described in
Table 1 of the EIGRL entry description. The EIGRL entry is an alternate method
to select the LAN method. It has several other input options for special cases.
When both and EIGRL and EIGR have the same SID and that SID is selected by
a METHOD command the EIGRL entry takes precedence.
EIGR 19
Real Eigenvalue Extraction Data

7. The AHOU method is competitive with the LAN method when there are small,
dense matrices and many eigenvectors are required. This most commonly occurs
when static or dynamic reduction is performed. The AHOU method does not take
advantage of matrix sparsity, so that computation cost rises with the cube of the
number of DOFs. The AHOU method responds to all permitted values for all the
other fields except NE, which is ignored.

8. All methods require a positive semi-definite (psd) mass matrix for stable
solutions. The mass matrix may be tested for this condition for all methods
of solution by setting SYSTEM(303). A value of -4 should be sufficient to
identify problem matrices. A fatal error exit is taken when it is not met. All NX
Nastran metric elements are designed to produce psd mass matrices. CMASSi
elements, DMIG matrices selected by the M2GG command, and matrices input
via INPUTT4 are special methods that allow addition of non-psd terms by use of
non-metric element input. If none of this type of special input is present and the
fatal error exit is taken you may have encountered an error in a metric element.
Contact a Technical Support representative for corrective action in this case.

9. The LAN and AHOU methods allow singular but psd mass matrices.

10. The tridiagonal methods include the xGIV and xHOU methods, where x is
described in the following comments. All tridiagonal methods compute all
eigenvalues, and the number of eigenvectors specified by the Fi and Nd fields, as
described in Table 14-14 above.

11. If x is blank (for example, the HOU method is selected) the mass matrix must
be non-singular.

12. If x is M (for example, the MHOU method is selected) the mass matrix may
be singular. A modified, shifted problem is solved in an inverse basis with
this method. Some precision in the solution and longer computation time is
exchanged for a more stable solution.

13. If x is A (for example, the AHOU method is selected) an attempt is made


to solve the problem without shifting, in the interest of cost reduction and
maximum precision. If the mass matrix is determined to be poorly conditioned
for inversion the basis is automatically shifted with the modified method.

14. If NORM = MAX, components that are not in the analysis set may have values
larger than unity.

15. If NORM = POINT, the selected component should be in the analysis set (a-set).
(The program uses NORM = MAX when it is not in the analysis set.) The
displacement value at the selected component will be positive or negative unity.
20 Laminate ply results in transient dynamics

16. The SINV method is an enhanced version of the INV method. It uses Sturm
sequence number techniques to make it more likely that all roots in the range
have been found. It is generally more reliable and more efficient than the INV
method.

17. For the INV and SINV methods, convergence is achieved at 106.
Convergence is tested by other criteria for the other methods.

18. For the SINV method only, if F2 is blank, the first shift will be made at F1, and
only one eigensolution above F1 will be calculated. If there are no modes below
F1, it is likely that the first mode will be calculated. If there are modes below F1
(including rigid body modes defined by SUPORT entries), a mode higher than
the first mode above F1 may be calculated.

19. When F1, F2, and ND are all zero or blank, ND is reset to 1. A User Warning
Message is produced for this condition, which is interpreted as likely to be due to
an inadvertent omission by the user.

20. In AF (amplitude-frequency) normalization, the normalized eigenvectors are


given by:
(C / w max) {x}
where C is an optional user-defined scale factor, w is the natural frequency for
the mode in Hz, max is the magnitude of the maximum grid point translation for
the mode, and {x} is the un-normalized eigenvector for the mode. The optional
user-defined scale factor, C, is specified with the AFNORM parameter.

Laminate ply results in transient dynamics


You can use the PCOMP and PCOMPG property entries in all structural solutions
to represent a layered composite. You reference these property entries with the
shell elements CTRIA3, CTRIA6, CTRIAR, CQUAD4, CQUAD8, and CQUADR.
Previously, the stress and strain output for the individual lamina was only
supported in solutions 101, 103, 105, 106*, 114, 144, 200, and 601.
Beginning with NX Nastran 9.0, the transient response solutions 109, 112, and
129 can also output the stress and strain for the individual lamina in either
SORT1 or SORT2 format.
The output you may now request for PCOMP or PCOMPG entries in solutions 101,
103, 105, 106*, 109, 112, 114, 129*, 144, and 200 includes the following:
Stresses and strains for the equivalent laminate (that is, output on the
equivalent PSHELL created by the software)
Laminate ply results in transient dynamics 21

Stress resultants, which are requested with the FORCE case control

Stresses and strains in the individual lamina including approximate


interlaminar shear stress in the bonding material output

A failure index table

The output is supported in either SORT1 or SORT2 format

In all other structural solutions, stress and strain can only be recovered for the
equivalent laminate. That is, output on the equivalent PSHELL created by the
software.

See the remarks on the PCOMP and PCOMPG bulk entry listings in the Quick
Reference Guide for information on these output requests.

See the remarks related to SOL 601 on the PCOMP bulk entry listing in the Quick
Reference Guide for information on how to request laminate results for SOL 601.

* The ply results are not computed in solutions 106 or 129 when PARAM,LGDISP,1
is defined.
22 PCOMP
Layered Composite Element Property

PCOMP Layered Composite Element Property

Defines the properties of an n-ply composite material laminate.

Format:

1 2 3 4 5 6 7 8 9 10
PCOMP PID Z0 NSM SB FT TREF GE LAM
MID1 T1 THETA1 SOUT1 MID2 T2 THETA2 SOUT2
MID3 T3 THETA3 SOUT3 -etc.-

Example:
PCOMP 181 -0.224 7.45 10000.0 HOFF
171 0.056 0.0 YES 45.0
-45.0 90.0

Fields:

Field Contents

PID Property identification number. (0 < Integer < 10000000)

Z0 Distance from the reference plane to the bottom surface. See Remark
14. (Real; Default = -0.5 times the element thickness.)

NSM Nonstructural mass per unit area. (Real)

SB Allowable shear stress of the bonding material (allowable interlaminar


shear stress). Required if FT is also specified. (Real > 0.0) See Remark
12.
PCOMP 23
Layered Composite Element Property

Field Contents

FT Failure theory. The following theories are allowed (Character or blank.


If blank, then no failure calculation will be performed):

HILL for the Hill theory.

HOFF for the Hoffman theory.

TSAI for the Tsai-Wu theory.

STRN for the Maximum Strain theory.

See the Laminates chapter in the NX Nastran Users Guide for a


detailed explanation of each theory.

TREF Reference temperature. See Remark 5. (Real; Default = 0.0)

GE Damping coefficient. See Remark 6 and Remark 16. (Real; Default = 0.0)

LAM Laminate Options. (Character or blank, Default = blank). See Remark


17.

Blank All plies must be specified and all stiffness terms are
developed.

SYM Only plies on one side of the laminate centerline are


specified. The plies are numbered starting with 1 for the
bottom ply. If the laminate contains an odd number of
plies, then model the center ply as half the thickness of
the actual center ply.

MEM All plies must be specified, but only membrane terms


(MID1 on the derived PSHELL entry) are computed.

BEND All plies must be specified, but only bending terms (MID2
on the derived PSHELL entry) are computed.

SMEAR All plies must be specified, stacking sequence is ignored,


MID1=MID2 on the derived PSHELL entry and MID3,
MID4 and TS/T and 12I/T**3 terms are set to zero.
24 PCOMP
Layered Composite Element Property

Field Contents

SMCORE Face plies on one side of the laminate and the core are
specified to define a laminate that is symmetric about the
midplane of the core. The core is specified last. When
calculating face sheet stiffness, stacking sequence of the
face sheets is ignored.

MIDi Material ID of the various plies. The plies are identified by serially
numbering them from 1 at the bottom layer. The MIDs can refer to
MAT1, MAT2, MAT8, MATSMA (SOL 601 only) or MATVE (SOL 601
only) bulk entries. See Remark 2 and SOL 601 Remark 4. (Integer > 0
or blank, except MID1 must be specified.)

Ti Thicknesses of the various plies. See Remark 2. (Real or blank, except


T1 must be specified.)

THETAi Orientation angle of the longitudinal direction of each ply with the
material axis of the element. (If the material angle on the element
connection entry is 0.0, the material axis and side 1-2 of the element
coincide.) The plies are to be numbered serially starting with 1 at the
bottom layer. The bottom layer is defined as the surface with the largest
-Z value in the element coordinate system. (Real; Default = 0.0)

SOUTi Controls individual ply stress and strain print or punch output. See
Remark 7 and Remark 8. (Character: YES or NO; Default = NO)

Remarks:

1. PID must be unique with respect to all PCOMP, PCOMPG, and PSHELL entries.

2. The default for MIDi+1, ..., MIDn is the last defined MIDi. In the example
above, MID(PLY1) is the default for MID(PLY2), MID(PLY3), and MID(PLY4).
The same logic applies to Ti.

3. Composite shell elements do not support nonlinear elastic materials defined


with the MATS1 bulk entry.

4. At least one of the four values (MIDi, Ti, THETAi, SOUTi) must be present for a
ply to exist. The minimum number of plies is one.

5. The TREF specified on the material entries referenced by plies are not used.
Instead TREF on the PCOMP entry is used for all plies of the element. If not
specified, it defaults to 0.0.
PCOMP 25
Layered Composite Element Property

If the PCOMP references temperature dependent material properties, then


the TREF given on the PCOMP will be used as the temperature to determine
material properties.
TEMPERATURE Case Control commands are ignored for deriving the
equivalent PSHELL and MATi entries used to describe the composite element.

6. GE given on the PCOMP entry will be used for the element and the values
supplied on material entries for individual plies are ignored. You are responsible
for supplying the equivalent damping value on the PCOMP entry. GE is ignored
in a transient analysis if PARAM,W4 is not specified. See the parameter W4.

7. The parameter NOCOMPS determines if stress and/or strain recovery is at the


composite ply layers (default), on the equivalent PSHELL, or both. See the
parameter NOCOMPS. The STRESS and/or STRAIN case control commands
are required for any of these recovery options. When ply results are requested,
stress and/or strain are computed at the middle of each ply. To print the ply
stress and/or strain results, the case control command request must include the
PRINT option (default). To punch these results, the case control command
request must include the PUNCH option. SOUTi=YES should then be defined
on any ply definitions in which you would like print or punch output. The SOUTi
entry is not used in the computing or printing of failure indices. See Remark 9.

8. Stress and strain output for individual plies are available in all superelement
static and normal modes analysis and requested by the STRESS and STRAIN
case control commands.

9. To compute STRESS failure index, the following must be present:

a. STRESS case control command.

b. The parameter NOCOMPS set to 1 (default) or 0.

c. SB and FT (= to HILL, HOFF or TSAI) on the PCOMP bulk entry.

d. Stress allowables Xt, Xc, Yt, Yc, and S on all referenced MAT8 bulk entries.

e. Stress allowables ST, SC, and SS on all referenced MAT1 bulk entries.

To compute STRAIN failure index, the following must be present:

a. STRESS case control command.

b. The parameter NOCOMPS set to 1 (default) or 0.

c. SB and FT (= STRN) on the PCOMP bulk entry.


26 PCOMP
Layered Composite Element Property

d. Strain allowables Xt, Xc, Yt, Yc, S, and STRN=1.0 on all referenced MAT8
bulk entries.

By default, failure index output prints in the f06 file even when using the PLOT
or PUNCH describers on the STRESS and STRAIN case control commands. The
parameter entry PARAM,NOFISR,1 can be used to turn off the printing of the
failure index output. See the parameter NOFISR.

10. To output strength ratio, the failure index output conditions listed in Remark 9
must exist, and the parameter SRCOMPS must equal YES. See the parameter
SRCOMPS.

11. Stress resultant output can be requested with the FORCE case control command.

12. The failure index of the bonding material is calculated by:


FIbonding = ( (t1z, t2z)/ allowable bonding stress).
The allowable bonding stress is defined on the SB field. The strength ratio for
the bonding material is:
SRbonding = (1 / FIbonding).

13. The software automatically creates equivalent PSHELL and MATi entries from a
PCOMP definition. You can optionally include a sorted echo request to print the
derived PSHELL and MATi entries in User Information Message 4379, or to the
punch file. The parameter NOCOMPS controls if stress and strain are computed
for the composite elements, the equivalent homogeneous element, or both. See
the parameter NOCOMPS. The software designates the equivalent homogeneous
elements with a MID1 or MID2 ID greater than or equal to 108 on the PSHELL
entry. Homogenous stresses are based upon a smeared representation of the
laminates properties and in general will be significantly different than the more
accurate lamina stresses available from PCOMP-based elements.

14. If the value specified for Z0 is not equal to -0.5 times the thickness of the element
and PARAM,NOCOMPS,-1 is specified, then the homogeneous element stresses
are incorrect, while lamina stresses and element forces and strains are correct.
For correct homogeneous stresses, use ZOFFS on the corresponding connection
entry.

15. An unsymmetrical layup or the use of Z0 to specify an unsymmetrical layup, is


not recommended in buckling analysis or the calculation of differential stiffness.
Also, Z0 should not be used to specify an unsymmetrical layup.

16. To obtain the damping coefficient GE, multiply the critical damping ratio C/Co
by 2.0.

17. The SYM option for the LAM option computes the complete stiffness properties
while specifying half the plies. The MEM, BEND, SMEAR and SMCORE
PCOMP 27
Layered Composite Element Property

options provide the following special purpose stiffness calculations: MEM option
only considers membrane effects, BEND option only considers bending effects,
SMEAR ignores stacking sequence and is intended for cases where the sequence
is not yet known, SMCORE allows simplified modeling of a sandwich panel with
equal face sheets and a central core.

18. Element output for the SMEAR and SMCORE options are produced using the
PARAM NOCOMPS -1 methodology that suppresses ply stress/strain results and
prints results for the equivalent homogeneous element.

19. When the PCOMP or PCOMPG bulk entries are included in a distributed
parallel method, the gpart keyword used for selecting the partitioning method
must be gpart=1.

20. PCOMP is supported in all solutions except SOL 153 or 159 heat transfer
analysis, and 701.

21. For elements referencing a PCOMP, stress and strain output for the individual
lamina is supported in solutions 101, 103, 105, 106, 109, 112, 114, 129, 144,
200, and 601. In other solutions, stress and strain can only be recovered for
the equivalent laminate. That is, output on the equivalent PSHELL created
by the software.

Remarks related to SOL 601:

1. Z0, NSM, SB, FT, TREF, GE, LAM and SOUTi are ignored.

2. When the STRESS and/or STRAIN case control commands are defined, results
at the composite ply layers are computed. Stress and strain components are
computed at the center of each ply. Inter-laminar results, failure indices, and
strength ratios are not computed. Stress resultant output is not supported.

3. Large strain formulation is not available for multi-layered shell elements.

4. Elasto-plastic material model is supported, but not nonlinear elastic material


model. That is, a MATS1 entry with TYPE=PLASTIC is supported, but not
TYPE=NLELAST.
28 PCOMPG
Layered Composite Element Property with global ply IDs

PCOMPG Layered Composite Element Property with global ply IDs

Defines the properties of an n-ply composite material laminate which includes global
ply IDs.

Format:

1 2 3 4 5 6 7 8 9 10
PCOMPG PID Z0 NSM SB FT TREF GE LAM
GPLYIDi MIDi Ti THETAi SOUTi

Example:

PCOMPG 73 2.E-4 0.0 8.E+7 TSAI


101 1 1.E-4 0. YES
102 1.E-4 0. YES
103 1.E-4 0. YES
104 1.E-4 0. YES

Fields:

Field Contents

PID Property identification number. (0 < Integer < 10000000)

Z0 Distance from the reference plane to the bottom surface. See Remark
14. (Real; Default = -0.5 times the element thickness.)

NSM Nonstructural mass per unit area. (Real)

SB Allowable shear stress of the bonding material (allowable interlaminar


shear stress). Required if FT is also specified. (Real > 0.0) See Remark
12.
PCOMPG 29
Layered Composite Element Property with global ply IDs

Field Contents

FT Failure theory. The following theories are allowed (Character or blank.


If blank, then no failure calculation will be performed):

HILL for the Hill theory

HOFF for the Hoffman theory

TSAI for the Tsai-Wu theory

STRN for the Maximum Strain theory

See the Laminates chapter in the NX Nastran Users Guide for a


detailed explanation of each theory.

TREF Reference temperature. See Remark 6. (Real; Default = 0.0)

GE Damping coefficient. See Remarks 7 and 16. (Real; Default = 0.0)

LAM Laminate Options. (Character or blank, Default = blank). See Remark


17.

Blank All plies must be specified and all stiffness terms are
developed.

MEM All plies must be specified, but only membrane terms


(MID1 on the derived PSHELL entry) are computed.

BEND All plies must be specified, but only bending terms (MID2
on the derived PSHELL entry) are computed.

SMEAR All plies must be specified, stacking sequence is ignored,


MID1=MID2 on the derived PSHELL entry and MID3,
MID4 and TS/T and 12I/T**3 terms are set to zero.

SMCORE Face plies on one side of the laminate and the core are
specified to define a laminate that is symmetric about the
midplane of the core. The core is specified last. When
calculating face sheet stiffness, stacking sequence of the
face sheets is ignored.

GPLYIDi Global ply IDs. See Remark 2. (Integer > 0)


30 PCOMPG
Layered Composite Element Property with global ply IDs

Field Contents

MIDi Material ID of the various plies. The plies are identified by serially
numbering them from 1 at the bottom layer. The MIDs must refer to
MAT1, MAT2, or MAT8 Bulk Data entries. See Remark 4. (Integer > 0
or blank, except MID1 must be specified.)

Ti Thicknesses of the various plies. See Remark 4. (Real or blank, except


T1 must be specified.)

THETAi Orientation angle of the longitudinal direction of each ply with the
material axis of the element. (If the material angle on the element
connection entry is 0.0, the material axis and side 1-2 of the element
coincide.) The plies are to be numbered serially starting with the first
listed at the bottom layer. The bottom layer is defined as the surface
with the largest -Z value in the element coordinate system. (Real;
Default = 0.0)

SOUTi Controls individual ply stress and strain print or punch output. See
Remarks 8 and 9. (Character: YES or NO; Default = NO)

Remarks:

1. PID must be unique with respect to all PCOMP, PCOMPG, and PSHELL entries.

2. Each global ply identification number GPLYIDi in a single PCOMPG entry


should be unique.
The global ply identification numbers (GPLYIDi) are reused across different
PCOMPG bulk entires in order to post-process relative ply layers with common
GPLYIDi.

3. Composite shell elements do not support nonlinear elastic materials defined


with the MATS1 bulk entry.

4. The default for MIDi+1, ..., MIDn is the last defined MIDi. In the example
above, MID(PLY1) is the default for MID(PLY2), MID(PLY3), and MID(PLY4).
The same logic applies to Ti.

5. At least one of the four values (MIDi, Ti, THETAi, SOUTi) must be present for a
ply to exist. The minimum number of plies is one.

6. The TREF specified on the material entries referenced by plies are not used.
Instead TREF on the PCOMPG entry is used for all plies of the element. If not
specified, it defaults to 0.0.
PCOMPG 31
Layered Composite Element Property with global ply IDs

If the PCOMPG references temperature dependent material properties, then the


TREF given on the PCOMPG will be used as the temperature to determine
material properties.
TEMPERATURE Case Control commands are ignored for deriving the
equivalent PSHELL and MATi entries used to describe the composite element.

7. GE given on the PCOMPG entry will be used for the element and the values
supplied on material entries for individual plies are ignored. You are responsible
for supplying the equivalent damping value on the PCOMPG entry. GE is ignored
in a transient analysis if PARAM,W4 is not specified. See the parameter W4.

8. The parameter NOCOMPS determines if stress and/or strain recovery is at the


composite ply layers (default), on the equivalent PSHELL, or both. See the
parameter NOCOMPS. The STRESS and/or STRAIN case control commands
are required for any of these recovery options. When ply results are requested,
stress and/or strain are computed at the middle of each ply. To print the ply
stress and/or strain results, the case control command request must include the
PRINT option (default). To punch these results, the case control command
request must include the PUNCH option. SOUTi=YES should then be defined
on any ply definitions in which you would like print or punch output. The SOUTi
entry is not used in the computing or printing of failure indices. See Remark 10.

9. Stress and strain output for individual plies are available in all superelement
static and normal modes analysis and requested by the STRESS and STRAIN
case control commands.

10. To output STRESS failure index, the following must be present:


a. STRESS case control command.

b. The parameter NOCOMPS set to 1 (default) or 0.

c. SB and FT (= to HILL, HOFF or TSAI) on the PCOMPG Bulk Data entry.

d. Stress allowables Xt, Xc, Yt, Yc, and S on all referenced MAT8 Bulk Data
entries.

e. Stress allowables ST, SC, and SS on all referenced MAT1 Bulk Data entries.

To output STRAIN failure index, the following must be present:


a. STRESS case control command.

b. The parameter NOCOMPS set to 1 (default) or 0.

c. SB and FT (= STRN) on the PCOMPG Bulk Data entry.


32 PCOMPG
Layered Composite Element Property with global ply IDs

d. Strain allowables Xt, Xc, Yt, Yc, S, and STRN=1.0 on all referenced MAT8
Bulk Data entries.

By default, failure index output prints in the f06 file even when using the PLOT
or PUNCH describers on the STRESS and STRAIN case control commands. The
parameter entry PARAM,NOFISR,1 can be used to turn off the printing of the
failure index output. See the parameter NOFISR.

11. To output strength ratio, the failure index output conditions listed in Remark 10
must exist, and the parameter SRCOMPS must equal YES. See the parameter
SRCOMPS.

12. The failure index of the bonding material is calculated by:


FIbonding = ( (t1z, t2z)/ allowable bonding stress).
The allowable bonding stress is defined on the SB field. The strength ratio for
the bonding material is:
SRbonding = (1 / FIbonding).

13. The software automatically creates equivalent PSHELL and MATi entries from a
PCOMPG definition. You can optionally include a sorted echo request to print the
derived PSHELL and MATi entries in User Information Message 4379, or to the
punch file. The parameter NOCOMPS controls if stress and strain are computed
for the composite elements, the equivalent homogeneous element, or both. See
the parameter NOCOMPS. The software designates the equivalent homogeneous
elements with a MID1 or MID2 ID greater than or equal to 108 on the PSHELL
entry. Homogenous stresses are based upon a smeared representation of the
laminates properties and in general will be significantly different than the more
accurate lamina stresses available from PCOMP-based elements.

14. If the value specified for Z0 is not equal to -0.5 times the thickness of the element
and PARAM,NOCOMPS,-1 is specified, then the homogeneous element stresses
are incorrect, while lamina stresses and element forces and strains are correct.
For correct homogeneous stresses, use ZOFFS on the corresponding connection
entry.

15. An unsymmetrical layup or the use of Z0 to specify an unsymmetrical layup, is


not recommended in buckling analysis or the calculation of differential stiffness.
Also, Z0 should not be used to specify an unsymmetrical layup.

16. To obtain the damping coefficient GE, multiply the critical damping ratio C/Co
by 2.0.

17. The MEM, BEND, SMEAR and SMCORE options provide the following special
purpose stiffness calculations: MEM option only considers membrane effects,
BEND option only considers bending effects, SMEAR ignores stacking sequence
SOL 111 solution methods 33

and is intended for cases where the sequence is not yet known, SMCORE allows
simplified modeling of a sandwich panel with equal face sheets and a central core.

18. Element output for the SMEAR and SMCORE options are produced using the
PARAM NOCOMPS -1 methodology that suppresses ply stress/strain results and
prints results for the equivalent homogeneous element.

19. When the PCOMP or PCOMPG bulk entries are included in a distributed
parallel method (DMP), the gpart keyword used for selecting the partitioning
method must be gpart=1.

20. PCOMPG is supported in all solutions except SOL 153 or 159 heat transfer
analysis, 601 and 701.

21. For elements referencing a PCOMPG, stress and strain output for the individual
lamina is supported in solutions 101, 103, 105, 106, 109, 112, 114, 129, 144, and
200. In other solutions, stress and strain can only be recovered for the equivalent
laminate. That is, output on the equivalent PSHELL created by the software.

SOL 111 solution methods


If viscous damping is included in modal frequency response (SOL 111), the
orthogonality property of the modes does not, in general, diagonalize the
generalized viscous damping matrix. Similarly, if structural damping is present,
the orthogonality property does not, in general, diagonalize the generalized
stiffness matrix. Consequently, in the presence of viscous damping or structural
damping, the equations of motion are typically coupled.
NX Nastran 9 includes a new option to solve these coupled equations. The new
option is suitable for any damped model, and it scales well in SMP. The option is
particularly beneficial if a large amount of RAM, and a large number of cores
are available. Some solution times have been reduced almost 50% with the new
in-core direct solution.
To select the new option, specify SYSTEM(462) = 1. However, if ITER = YES is
also specified in the input file, the software will use the in-core iterative FRRD1
method introduced with NX Nastran 6.
For a complete listing of the options available with SYSTEM(462), see Summary of
options.
If there is insufficient memory to utilize all cores independently, a fall back is taken
and one of the following messages is printed to the f06 file:
*** USER INFORMATION MESSAGE 6682 (FRDSMP)
NEEDS xxxx ADDITIONAL WORDS OF MEMORY TO USE IN-CORE FRRD1 WITH PARALLEL=%yy.
FALL BACK TO USE IN-CORE FRRD1 WITH PARALLEL=zz.
USER ACTION: INCREASE MEMORY FOR BETTER PERFORMANCE IN FRRD1.
34 SOL 111 solution methods

This indicates that there is not enough memory to utilize all cores requested,
but there is enough to continue with the in-core method and fewer cores. A
performance benefit is still expected, compared to the standard direct solver.
*** USER INFORMATION MESSAGE 6682 (FRDSMP)
NEEDS xxxx ADDITIONAL WORDS OF MEMORY TO USE IN-CORE FRRD1 WITH PARALLEL=%yy.
FALL BACK TO NXN85 FRRD1.
USER ACTION: FOR BETTER PERFORMANCE, INCREASE MEMORY TO USE PARALLEL IN-CORE FRRD1.

Here, there is not enough memory to saturate enough cores to make the in-core
method worthwhile. The software reverts to the standard direct solver, which
utilizes SMP as usual.
Summary of options
Specifying SYSTEM(462) = 0 (the default option) selects the original FRRD1
method. This method is a good choice when the number of modes is small
or the model is undamped.

Specifying SYSTEM(462) = 1 selects the in-core direct FRRD1 method


introduced in NX Nastran 9. This method is suitable for any damped model,
and it scales well in SMP. This method is particularly beneficial if a large
amount of RAM, and a large number of cores is available. Some solution times
have been reduced almost 50% with this method.

Specifying SYSTEM(462) = 1 when ITER = YES is also specified selects the


in-core iterative FRRD1 method introduced in NX Nastran 6. This method is a
good choice when the number of modes is large and the model is damped.

Specifying SYSTEM(462) = 2 selects the FRRDRU method introduced in NX


Nastran 7, and then enhanced in NX Nastran 8. This method is a good choice
for models that contain significant structural damping, but relatively few
viscous dampers. This method is recommended when the number of modes is
large (more than 3000), and the desired frequency range is also large (more
than 20 frequencies). This method cannot handle multiple eigenvalues (either
repeated roots or rigid body modes). If multiple eigenvalues occur, the method
defaults to the original FRRD1 method.

Specifying SYSTEM(462) = 4 selects the enhanced FRRDRU method


introduced in NX Nastran 8.5. This method is a good choice for models that
contain significant structural damping, but relatively few viscous dampers.
This method is recommended when the number of modes is large (more
than 3000), and the desired frequency range is also large (more than 20
frequencies). This method allows for multiple eigenvalues. If the model
contains modal viscous damping, this method automatically converts it to
modal structural damping by setting KDAMP = -1.
RMS von Mises stress 35

RMS von Mises stress


NX Nastran can compute the response of a structure due to random loads. You
can request a random analysis with the RANDOM case control command in the
frequency response solutions 108 and 111. Random response output includes
the response PSD, autocorrelation functions, the number of zero crossings with
positive slope per unit time, and the RMS (root-mean-square) values of response.
These random output options can be requested on the individual case control
commands. For example, the STRESS, STRAIN, DISPLACEMENT, VELOCITY,
and ACCELERATION commands.

Beginning with NX Nastran 9.0, when the stress RMS output is requested using
the RMS describer on the STRESS case control command, an RMS von Mises
stress is now included in the output for those elements that support von Mises
stress calculation.

To accommodate the new RMS von Mises stress, the new datablocks OESXRMS1
and OESXRMS2 have been created. These datablocks are written by default when
STRESS is requested in a random analysis. The system cell setting
NASTRAN SYSTEM(550)=1 or NASTRAN RMSVM=1

can be included to turn off the RMS von Mises stress, and the original datablocks
OESRMS1 and OESRMS2 will be written to the op2 file.

Mathematical description

The methodology used to compute the RMS von Mises stress is based on the
Sandia Report SAND98-0260 from Sandia National Laboratories titled An
Efficient Method for Calculating RMS von Mises Stress in a Random Vibration
Environment. This is the same method used in NX Response Simulation and in
I-deas Model Solution.

Consider the following quadratic function of stress:

where A is a symmetric, constant, positive semi-definite matrix.

In the case of von Mises stress:

and
36 Relative motion datablock

The root-mean-square value for von Mises stress in frequency domain, PRMS, is
given by

After some trigonometric manipulations, the time-averaged value of the square

of von Mises stress, , is

where denotes the Hermitian operator (complex conjugate transpose).

To be useful, the above expressions must be expressed in terms of the input forces

With ensemble averaging, this expression can be expressed in terms of the input
cross spectral density matrix

Relative motion datablock


For enforced motion dynamic analysis, the REL and ABS describers on the
DISPLACEMENT, VELOCITY, and ACCELERATION case control commands
determine if these output types are stored as absolute or relative.

Previously, NX Nastran wrote the ROUGV datablock when relative was request.
Residual vector defaults 37

Beginning with NX Nastran 9.0, the OUGV datablock is written when either
relative or absolute is requested. This reduces the amount of output data when
relative displacement/velocity/acceleration output is requested.
The OUGV datablock now includes a data flag to indicate relative or absolute
results.

Residual vector defaults


The modal method is a common approach for dynamic forced response solutions
because of the computational efficiencies gained by the normal mode reduction. In
practice, a small subset of the modes are computed and used for the computation
while the effects of truncated higher frequency modes are ignored. The typical rule
of thumb for modal sufficiency is to compute modes up to a frequency twice as
high as the excitation frequency range. This is suitable for most responses, but
some responses, in particular force and stress, can have errors because of the
missing truncated modes. Since the missing modes have high frequencies, their
omission leads to errors in the static response contributions. Residual vectors are
an effective means for reducing the response errors by adding the missing static
flexibility from the truncated modes.
To streamline the use of the RESVEC case control command, the default settings
have changed*.

New RESVEC Defaults

The defaults now apply even when the RESVEC case control command is
undefined. Previously the RESVEC command was required to request residual
vectors.

For SOLs 103, 106 (PARAM,NMLOOP,0), 110, 115, 153 (PARAM,NMLOOP,0),


and 187, the new default is RESVEC=COMPONENT.

For SOLs 111, 112, 118, 146, and 200 (ANALYSIS=MODES, MCEIG, MTRAN,
or MFREQ), the default is RESVEC=YES.

In addition, a new DAMPLOD describer requests residual vectors by default


for the degree-of-freedom in which viscous damping is defined on the CBUSHi,
CDAMPi, and CVISC elements.
Note that the existing RVEL describer requests residual vectors for the
degree-of-freedom associated with the CBUSHi, CDAMPi, CELASi, and CVISC
elements selected on a RVEL bulk entry, regardless if damping is defined or not. If
DAMPLOD and RVEL are both defined (default), and RVEL bulk data entries are
defined, residual vectors will be requested for the combined degree-of-freedom list.
38 Residual vector defaults

For additional information, see the updated RESVEC case control command.

* These defaults did exist in NX Nastran 8.5.1. Although, in order to transition to


the new defaults, for that release only, you had to remove the parameter settings
PARAM,RESVEC,NO and PARAM,RESVINER,NO from the NX Nastran 8.5.1 rc
file. These parameter settings do not exist in the NX Nastran 9 rc file.

Note: To turn off the new default behavior in NX Nastran 9, you can add
PARAM,RESVEC,NO and PARAM,RESVINER,NO into the NX Nastran 9 rc file
(installation_path/conf/nast9.rcf).
RESVEC 39
Residual Vector Request

RESVEC Residual Vector Request

Used to control the computation of residual vectors.


Format:

Examples:
RESVEC = SYSTEM
RESVEC(NOINRL) = COMPONENT
RESVEC = YES

Describers:

Describer Meaning

APPLOD Compute residual vectors for applied loads. See Remark 5.


(Default)

NOAPPL Do not compute residual vectors for applied loads.

RVDOF Compute residual vectors for degree-of-freedom included in


RVDOF and RVDOF1 bulk entries. See Remark 6. (Default)

NORVDO Do not compute residual vectors for degree-of-freedom


included in RVDOF and RVDOF1 bulk entries.

RVEL Compute residual vectors for degree-of-freedom defining


CBUSHi, CDAMPi, CELASi, and CVISC elements referenced
by a RVEL bulk entry. See Remarks 7 and 9. (Default)

NORVEL Do not compute residual vectors for degree-of-freedom defining


CBUSHi, CDAMPi, CELASi, and CVISC elements referenced
by a RVEL bulk entry.
40 RESVEC
Residual Vector Request

Describer Meaning

INRLOD Compute residual vectors for inertia relief load. See Remark
4. (Default)

NOINRL Do not compute residual vectors for inertia relief load.

DAMPLOD Compute residual vectors for the degree-of-freedom in which


viscous damping is defined on the CBUSHi, CDAMPi, and
CVISC elements. See Remark 9. (Default)

NODAMP Do not compute residual vectors for the degree-of-freedom in


which viscous damping is defined on the CBUSHi, CDAMPi,
and CVISC elements.

DYNRSP Include the dynamic effect of residual vector modes in the


forced response solution. See Remark 8. (Default)

NODYNRSP Do not include the dynamic effect of residual vector modes in


the forced response solution.

The defaults for the following describers are solution dependent. The defaults
apply even when the RESVEC case control entry is undefined. See Remark 10.

SYSTEM Request residual vectors for residual structure


degree-of-freedom only (a-set).

NOSYSTEM Do not compute residual vectors for residual structure


degree-of-freedom (a-set).

COMPONENT Request residual vectors for superelement degree-of-freedom


only (o-set). (Default for SOLs 103, 106 with PARAM,
NMLOOP=0, 110, 115, 153 with PARAM, NMLOOP=0, and
187.)

NOCOMPONENT Do not compute residual vectors for superelement


degree-of-freedom (o-set).

BOTH (or YES) Request residual vectors for both residual structure DOF
(a-set) and for superelement DOF (o-set). (Default for SOLs
111, 112, 118, 146, and 200 with ANALYSIS=MTRAN or
MFREQ.)

NO Turns off calculation of residual vectors.


RESVEC 41
Residual Vector Request

Remarks:

1. If the RESVEC case control command is present, the parameters RESVEC and
RESVINER are ignored.

2. A unique RESVEC case control definition can be defined in different


superelement subcases. You can use the NOSYSTEM and NOCOMPONENT
describers in a superelement subcase to turn off a setting which may have been
defined globally.

3. If a RESVEC case control command is present in a cold start analysis, then


only the RESVEC case control command can be used in a restart. Similarly, if
parameter RESVEC/RESVINER is used in a cold start, then only the same
can be used in a restart.

4. INRLOD designates that inertia load residual vectors are to be calculated.


INRLOD is functionally equivalent to PARAM,RESVINER,YES. Inertia loads
are computed for each of the 6 basic coordinate system directions and residual
vectors are computed for each load.

5. APPLOD designates that the applied load residual vectors are to be calculated.
There are two input scenarios to determine the applied loads for computing
residual vectors.
a. The load set IDs selected with the EXCITEID field on all RLOAD1,
RLOAD2, TLOAD1, TLOAD2, ACSRCE, and SELOAD entries in the bulk
data are processed. No DLOAD case control is required in this case. If a
LOADSET case control command exists, these are all ignored.

b. If a LOADSET case control command exists, and it selects an LSEQ bulk


entry, the load set ID selected in the LID field in the LSEQ bulk entry
is processed.

6. The operation of the residual vector calculation with RVDOF is functionally


equivalent to PARAM,RESVEC,YES when USET, U6 DOF are present. The
RVDOF/RVDOF1 bulk entries can select both a-set and o-set DOF. This is
different than the USET, U6 capability which requires USET, U6 to select a-set
DOF, but requires SEUSET, U6 to select o-set DOF.
The unit loads applied to the interior points of a superelement due to RVDOFi
bulk entries are passed downstream to the residual for the purpose of residual
vector processing by all superelements in its downstream path. This produces
more accurate results as compared to the results produced when USETi,U6
or SEUSETi,U6 bulk entries are used for residual vector processing. When
USETi,U6 or SEUSETi,U6 bulk entries are used, unit loads on a superelement
are not passed downstream for residual vector processing by the downstream
superelements.
42 RESVEC
Residual Vector Request

7. If a CBUSHi, CDAMPi, CELASi, and CVISC element is grounded, the unit load
is applied to only the ungrounded end.

8. DYNRSP/NODYNRSP is only applicable to modal forced response solutions


(SOLs 111, 112, 146, and 200). For models containing superelements,
DYNRSP/NODYNRSP is only applicable to the residual structure.

9. DAMPLOD requests residual vectors for the degree-of-freedom in which viscous


damping is defined on the CBUSHi, CDAMPi, and CVISC elements. RVEL
requests residual vectors for the degree-of-freedom associated with the CBUSHi,
CDAMPi, CELASi, and CVISC elements selected on a RVEL bulk entry,
regardless if damping is defined or not. If DAMPLOD and RVEL are both
defined (default), and RVEL bulk data entries are defined, residual vectors will
be requested for the combined degree-of-freedom list.

10. For SOLs 111, 112, 118, 146, and 200 (ANALYSIS=MODES, MCEIG,
MTRAN, or MFREQ), the default is RESVEC=YES. For SOLs 103, 106
(PARAM,NMLOOP,0), 110, 115, 153 (PARAM,NMLOOP,0), and 187, the default
is RESVEC=COMPONENT. These defaults apply even when the RESVEC case
control entry is undefined.
Chapter

3 Rotor dynamics

Rotor dynamic forces in SOL 101


Beginning with NX Nastran 9.0, the rotor dynamic capability has been extended to
compute the following rotor dynamic forces in a linear static solution (SOL 101).
Gyroscopic forces can be computed at the grid points included on the rotor
definitions. If you have rotors defined with the ROTORD entry, and an angular
velocity body load defined with the RFORCE or the new RFORCE1 entry, the
software will compute the gyroscopic force

where,
is the angular velocity of the entire body defined with the RFORCE
w
or RFORCE1 entry,
is the rotor speed defined in the RSTART field on the ROTORD entry,

is the gyroscopic
matrix,

is the polar moment of inertia.

If damping is included on the rotor, for example, if the rotor material includes
structural damping GE, the following damping force is computed at the grid
points included on a rotor definition.

where,
44 Rotor dynamic forces in SOL 101

is the skew-symmetric damping on the rotor, and

are the displacements.


In the fixed system, this force is the effect of the internal damping of the rotor
on the foundation. It is carried through the bearing connection.

Note that you must select a fixed reference system for all rotors included in your
linear static solution by setting REFSYS=FIX on the ROTORD entry.

In addition to the gyroscopic rotor dynamic static load, when you define an angular
velocity (w) and/or acceleration (a) with the RFORCE or RFORCE1 entries, the
following static inertia force is also computed at all grid points.

where [M] is the nodal mass matrix and r is the position vector for each grid.

The software computes r for each grid by taking the difference between the position
vector for the grid and the position vector for the grid listed on the RFORCE
or RFORCE1 entry. Both position vectors are expressed relative to the basic
coordinate system. The grid listed on the RFORCE or RFORCE1 entry is a point
through which the rotation vector acts.

This static inertia force is not a new feature in NX Nastran 9, and is not specific to
rotor dynamic models. For additional information, see the RFORCE and RFORCE1
bulk entries in the Quick Reference Guide.

Example

An application of gyroscopic forces is an aircraft maneuvering during flight. The


aircraft rotates about the three axes passing through its center of gravity (CG).
The example in Figure 3-1 has a coordinate system located at the CG. The X, Y,
and Z axis of this system are aligned such that the maneuvers loads, defined with
RFORCE or RFORCE1 entries are pitch (wx, ax), yaw (wy, ay), and roll (wz, az).

The multiple rotors in this example would each be defined with an individual
ROTORD entry, each with unique speeds.
Rotor dynamic forces in SOL 101 45

Figure 3-1. Aircraft maneuvers


The static forces computed in this example include the following.

The pitch and yaw loads will produce the gyroscopic forces at
the grid points included on the rotors.

The damping force will be computed at the grid points


included on the rotors if damping is defined on the rotors.

The inertia body forces will be computed


at all grid points.

Any additional conventional static loads can be included. For example, gravity,
pressures, forces, and enforced displacements.

Input Example
In the following bulk data example,
the rotor is oriented in the basic z direction,

the body rotational velocities in subcase 1 are wx = .0223 rad/sec (.159 x .14)
and wy = .668 rad/sec (.159 x 4.2), and

the rotor speed is = 52.35 rad/sec (500 RPM).


RMETHOD=99
46 Dependent bearing properties

SUBCASE 1
LOAD=11
BEGIN BULK
$ SID RSTART RSTEP NUMSTEP REFSYS CMOUT RUNIT FUNIT
ROTORD 99 10000.0 1.0 1 FIX 1. RPM HZ+
$ ZSTEIN ORBEPS ROTPRT
+ NO 1.0E-5 3 +
$ RID RSET RSPEED RCORD W3 W4 RFORCE BRGSET
+ 1 1 1.0 1 1+
+ 2 2 1.0 1 2+
+ 3 3 1.4 2 3
$CG location
GRID, 999, 0, 36.42, 0.12, 12.3
$Unit Translational Acceleration Loads (gs)
GRAV, 1, 0, 386., 1., 0., 0.
GRAV, 2, 0, 386., 0., 1., 0.
GRAV, 3, 0, 386., 0., 0., 1.

$Unit Rotational Velocity Loads (rad/sec)


RFORCE, 11, 999, .159, 1., 0., 0.
RFORCE, 12, 999, .159, 0., 1., 0.
RFORCE, 13, 999, .159, 0., 0., 1.

$Unit Rotational Acceleration Loads (rad/sec/sec)


RFORCE, 21, 999, 0., 1., 0., 0., ,+
+, .159
RFORCE, 22, 999, 0., 0., 1., 0., ,+
+, .159
RFORCE, 23, 999, 0., 0., 0., 1., ,+
+, .159

$Combined and scaled unit loads

LOAD, 11, 1., .7, 1, 1.1, 2, .6, 3,+


+, .14, 11, 4.2, 12, .17, 13, .36, 21,+
+, 6.4, 22, 1.7, 23

For examples of complete input files, see rot101*.dat in


install_directory\nxn9\nast\tpl.

Dependent bearing properties


The CBEAR and PBEAR bulk entries became available in NX Nastran 8.5 to model
the bearing support stiffness and viscous damping for each rotor. You can define
the stiffness and viscous damping values as constant, or as speed-dependent. The
coordinate frame for each rotor is defined by a coordinate system selected with the
RCORDi field on the ROTORD bulk entry. The Z-axis of this system is the axis of
rotation for that rotor. The KXX, KYY, KXY, KYX, BXX, BYY, BYX, and BXY fields
on the PBEAR bulk entry define the bearing stiffness and viscous damping.

Prior to NX Nastran 9.0, bearing stiffness and viscous damping could be constant
or speed dependent. Now when using SOL 101, the bearing stiffness and viscous
Dependent bearing properties 47

damping can be dependent on speed and displacement, or speed and force. For
example,

Note

If bearings are defined as speed and displacement dependent, or as speed


and force dependent, only a single subcase should exist. This is because the
bearing stiffness and damping computed in an initial subcase would be
used in all successive subcases. This limitation will be removed in a future
release.

The updated procedure to define bearing stiffness or viscous damping is as follows.

1. Use a CBEAR bulk entry to model each bearing connection. Each CBEAR
bulk entry is defined by a pair of coincident grid points that lie on the axis of
rotation. List one of the coincident grid points on a ROTORG bulk entry for
the rotor. The software interprets this grid point as rotating. List the other
coincident grid point on a ROTORB bulk entry for the rotor. The software
interprets this grid point as stationary. If the model contains only a single
rotor, you do not need to include a ROTORB bulk entry. By default, the
software assumes that the coincident grid point not listed on the ROTORG
bulk entry is stationary.

To associate the ROTORB bulk entry for a rotor with the ROTORG bulk entry
for the same rotor, use the same identification number in the RSETID fields of
both entries, and also include this identification number in the RSETi field for
the corresponding rotor on the ROTORD bulk entry.
48 Dependent bearing properties

2. Define the new GROUP bulk entry for each rotor that has corresponding
CBEAR bulk entries. On each GROUP bulk entry, list the CBEAR bulk
entries. Associate each GROUP bulk entry with a rotor on the BRGSETi field
on the ROTORD bulk entry.

3. Reference a PBEAR bulk entry on each CBEAR bulk entry. The PBEAR bulk
entry defines the stiffness and viscous damping for CBEAR elements. Use the
PBEAR bulk entry to optionally define the support stiffness values KXX, KYY,
KXY, KYX, or the viscous damping values BXX, BYY, BYX, and BXY. The X
and Y in these field designations refer to the X- and Y-axes of the coordinate
system referenced in the RCORDi field of the ROTORD bulk entry.

The stiffness and viscous damping values can be defined as constant


(independent of speed). See Constant stiffness and viscous damping input
example.

The stiffness and viscous damping values can be defined as speed


dependent. See Speed dependent stiffness and viscous damping input
example.

The stiffness and viscous damping values can be defined as dependent on


speed and displacement or speed and force. Valid for SOL 101 only. See
Speed and displacement dependent stiffness and viscous damping input
example.

For additional information on specifying speed and displacement, or speed and


force dependent bearing stiffness and viscous damping, see the updated PBEAR
and ROTORD bulk entries.

Constant stiffness and viscous damping input example

When the stiffness and viscous damping is constant, you enter the stiffness and
viscous damping directly on the PBEAR entry.
$...
$2345678123456781234567812345678123456781234567812345678123456781234567812345678
$PBEAR PBEARID TYPE TXX TXY TYX TYY
$
PBEAR 789 K 2.0E3 105.6 105.6 2.0E3 +
+ B 310.0 85.0 85.0 310.0
$...

Speed dependent stiffness and viscous damping input example

When stiffness or viscous damping is dependent on speed,

you define stiffness or viscous damping versus speed tables on TABLEDi bulk
entries,
Dependent bearing properties 49

you enter the TABLEDi bulk entry IDs in the stiffness and viscous damping
fields on the PBEAR entry.
$...
$PBEAR PBEARID TYPE TXX TXY TYX TYY
$
PBEAR 789 K 7891 7892 7893 7894 +
+ B 7895 7896 7897 7898
$
$ Define speed dependency of bearing properties
$
$TABLED1TID XAXIS YAXIS
$ X1 Y1 X2 Y2 ENDT
$
TABLED1 7891 LINEAR LINEAR
0.0 0.0 1.0E3 1.0E3 ENDT
TABLED1 7892
0.0 0.0 1.0E3 2.0E3 ENDT
TABLED1 7893
0.0 0.0 1.0E3 3.0E3 ENDT
TABLED1 7894
0.0 0.0 1.0E3 4.0E3 ENDT
TABLED1 7895
0.0 0.0 1.0E3 1.0E2 ENDT
TABLED1 7896
0.0 0.0 1.0E3 2.0E2 ENDT
TABLED1 7897
0.0 0.0 1.0E3 3.0E2 ENDT
TABLED1 7898
0.0 0.0 1.0E3 4.0E2 ENDT
$...

Speed and displacement dependent stiffness and viscous damping input


example
When stiffness or viscous damping is dependent on speed and displacement or
speed and force,
you define stiffness or viscous damping versus speed tables on TABLEDi bulk
entries,

you define displacement or force versus TABLEDi ID tables on the TABLEST


entries,

you enter the TABLEST bulk entry IDs in the stiffness and viscous damping
fields on the PBEAR entry.
$...
$ pbearid type txx txy tyx tyy nominal
BEAR 789 KD 7891 7892 7893 7894 1.0 +
$ type tdxx tdxy tdyx tdyy nominal
+ BD 7895 7896 7897 7898 1.0
$
$ TABLEST tables for pbear
$
TABLEST 7891
50 Dependent bearing properties

0.0 8891 1.0 9891 2.0 6891 ENDT


TABLEST 7892
0.0 8892 1.0 9892 2.0 6892 ENDT
TABLEST 7893
0.0 8893 1.0 9893 2.0 6893 ENDT
TABLEST 7894
0.0 8894 1.0 9894 2.0 6894 ENDT
TABLEST 7895
0.0 8895 1.0 9895 2.0 6895 ENDT
TABLEST 7896
0.0 8896 1.0 9896 2.0 6896 ENDT
TABLEST 7897
0.0 8897 1.0 9897 2.0 6897 ENDT
TABLEST 7898
0.0 8898 1.0 9898 2.0 6898 ENDT
$
$ Disp = 0.0 RPM tables
$
TABLED1 8891 LINEAR LINEAR
0.0 0.0 1.0E3 1.0E3 ENDT
TABLED1 8892
0.0 0.0 1.0E3 2.0E3 ENDT
TABLED1 8893
0.0 0.0 1.0E3 3.0E3 ENDT
TABLED1 8894
0.0 0.0 1.0E3 4.0E3 ENDT
TABLED1 8895
0.0 0.0 1.0E3 1.0E2 ENDT
TABLED1 8896
0.0 0.0 1.0E3 2.0E2 ENDT
TABLED1 8897
0.0 0.0 1.0E3 3.0E2 ENDT
TABLED1 8898
0.0 0.0 1.0E3 4.0E2 ENDT
$
$ Disp = 1.0 RPM tables
$
TABLED1 9891 LINEAR LINEAR
0.0 0.0 1.0E3 2.0E3 ENDT
TABLED1 9892
0.0 0.0 1.0E3 4.0E3 ENDT
TABLED1 9893
0.0 0.0 1.0E3 6.0E3 ENDT
TABLED1 9894
0.0 0.0 1.0E3 8.0E3 ENDT
TABLED1 9895
0.0 0.0 1.0E3 2.0E2 ENDT
TABLED1 9896
0.0 0.0 1.0E3 4.0E2 ENDT
TABLED1 9897
0.0 0.0 1.0E3 6.0E2 ENDT
TABLED1 9898
0.0 0.0 1.0E3 8.0E2 ENDT
$
$ Disp = 2.0 RPM tables
$
TABLED1 6891 LINEAR LINEAR
0.0 0.0 1.0E3 3.0E3 ENDT
TABLED1 6892
0.0 0.0 1.0E3 6.0E3 ENDT
TABLED1 6893
Dependent bearing properties 51

0.0 0.0 1.0E3 9.0E3 ENDT


TABLED1 6894
0.0 0.0 1.0E3 1.2E4 ENDT
TABLED1 6895
0.0 0.0 1.0E3 3.0E2 ENDT
TABLED1 6896
0.0 0.0 1.0E3 6.0E2 ENDT
TABLED1 6897
0.0 0.0 1.0E3 9.0E2 ENDT
TABLED1 6898
0.0 0.0 1.0E3 1.2E3 ENDT
$...

For examples of complete input files, see rotbr5*.dat and rotbr60*.dat in


install_directory\nxn9\nast\tpl.
52 ROTORD
Define Rotor Dynamics Solution Options

ROTORD Define Rotor Dynamics Solution Options

Defines rotor dynamics solution options.

Format:

1 2 3 4 5 6 7 8 9 10
ROTORD SID RSTART RSTEP NUMSTEP REFSYS CMOUT RUNIT FUNIT
ZSTEIN ORBEPS ROTPRT SYNC ETYPE EORDER THRSHOLD MAXITER
RID1 RSET1 RSPEED1 RCORD1 W3_1 W4_1 RFORCE1 BRGSET1
RID2 RSET2 RSPEED2 RCORD2 W3_2 W4_2 RFORCE2 BRGSET2
....

RIDi RSETi RSPEEDi RCORDi W3_i W4_i RFORCEi BRGSETi


....

RID10 RSET10 RSPEED10 RCORD10 W3_10 W4_10 RFORCE10 BRGSET10

Example:
ROTORD 998 0.0 250.0 58 fix -1.0 cps
no
1 11 1 0.0 0.0 1 101
2 12 1 0.0 0.0 102
3 13 1.5 1 0.0 0.0 103
4 14 1.75 1 0.0 0.0 104
5 15 1.75 1 0.0 0.0 105
6 16 1 0.0 0.0 106
7 17 2.0 1 0.0 0.0 107
8 18 2.25 1 0.0 0.0 108
9 19 7.5 1 0.0 0.0 109
10 20 1 0.0 0.0 10 110

Fields:

Field Contents

SID Set identifier for all rotors. Must be selected in the case control
deck by RMETHOD = SID. (Integer > 0)

RSTART Starting value of reference rotor speed. (Real 0.0)


ROTORD 53
Define Rotor Dynamics Solution Options

Field Contents

RSTEP Step-size of reference rotor speed. (Real > 0.0)

NUMSTEP Number of steps for reference rotor speed including RSTART.


(Integer > 0)

REFSYS Reference system. (Character; Default = ROT)

= FIX analysis is performed in the fixed reference system.

= ROT analysis is performed in the rotational reference system.

CMOUT Determines the rotor speeds at which eigenvectors are calculated


and output. (Real; Default = 0.0)

= 0.0 no eigenvectors are calculated; no eigenvectors are output;


no whirl directions are output.

> 0.0 eigenvectors are calculated at the specified speed;


eigenvectors are output at the specified speed; whirl direction is
output at the specified speed.

= -1.0 eigenvectors are calculated at all speeds; eigenvectors are


output at all speeds; whirl directions are output at all speeds.

RUNIT Units used for rotor speed inputs (CMOUT, RSTART and RSTEP)
and output (units for output list and Campbell diagram output).
(Character; Default = RPM)

= RPM revolutions per minute.

= CPS cycles per second.

= HZ cycles per second.

= RAD radians per second.

FUNIT Units used for frequency output (Campbell diagram output).


(Character; Default = RPM)

= RPM revolutions per minute.

= CPS cycles per second.

= HZ cycles per second.

= RAD radians per second.


54 ROTORD
Define Rotor Dynamics Solution Options

Field Contents

ZSTEIN Option to incorporate Steiners inertia terms. (Character; Default


= NO)

= YES Steiners inertia terms are included.

= NO Steiners inertia terms are not included.

ORBEPS Threshold value for detection of whirl direction. (Real > 0.0;
Default = 1.E-6)

ROTPRT Controls .f06 output options. (Integer; Default = 0))

= 0 no print.

= 1 print generalized matrices.

= 2 print eigenvalue summary and eigenvectors at each RPM.

= 3 combination of 1 & 2.

SYNC Option to select synchronous or asynchronous analysis for


frequency response analysis. (Integer; Default = 1)

= 1 synchronous

= 0 asynchronous

ETYPE Excitation type. (Integer; Default = 1)

= 1 Mass unbalanced. Specify mass unbalance = m x r on DLOAD


bulk entry and the program will multiply by 2.

= 0 Force excitation. Specify force = m x r x 2 on DLOAD bulk


entry.

EORDER Excitation order. (Real; Default 1.0)

= 1.0 (Default) (modes crossing with 1P line in the fixed system)

= 0.0 Forward whirl (modes crossing with 0P line in the rotating


system)

= 2.0 Backward whirl (modes crossing with 2P line in the rotating


system)
ROTORD 55
Define Rotor Dynamics Solution Options

Field Contents

THRSHOLD Convergence threshold when iterating to determine bearing


stiffness or viscous damping for CBEAR elements that have speed
and displacement or speed and force dependent stiffness or viscous
damping. See Remark 14. (Real > 0.0; Default = 0.02)

MAXITER Maximum number of iterations to determine bearing stiffness


or viscous damping for CBEAR elements that have speed and
displacement or speed and force dependent stiffness or viscous
damping. A value of 0 implies that no iterations are performed.
See Remark 14. (0 Integer 10; Default = 0)

RIDi Identification number of rotor i. (Integer > 0 with RIDi+1 > RIDi;
Default = i)

RSETi Refers to a RSETID value on a ROTORG bulk entry and a


ROTORB bulk entry. Each ROTORG bulk entry specifies the grids
for a single rotor. If only one rotor exists, field can be left blank
and all grid points are considered rotating by default. For multiple
rotors, there is no default. (Integer > 0 or blank if only one rotor)

RSPEEDi Multiplier of reference rotor speed for rotor i. See Remark 12.
(Real 0.0 or Integer > 0 or blank; Default = 1.0)

If real entry, value of multiplier at all reference rotor speeds.

If integer entry, identification number of a TABLEDi entry that


contains value of multiplier as a function of reference rotor speed.

RCORDi Identification number of the coordinate system whose z axis is the


rotation axis of rotor i. (Integer; Default = 0 for basic coordinate
system)

W3_i Reference frequency for structural damping defined by PARAM,G


for rotor i. (Real; Default = 0.0)

W4_i Reference frequency for structural damping defined by GE for


rotor i. See Remark 6. (Real; Default = 0.0)

RFORCEi Points to RFORCE bulk entry for rotor i. (Integer; Default = 0


for no rotational force applied; a rotational force is required for
differential stiffness to be calculated.)

BRGSETi Identification number of a GROUP bulk entry that lists the


CBEAR elements for the corresponding RIDi. Only the GROUP
type ELEM is supported. (Integer 0 or blank; no default)
56 ROTORD
Define Rotor Dynamics Solution Options

Remarks:

1. Any entries where defaults exist are optional. Thus, if the defaults are acceptable
for a particular model, then a continuation line would not be needed.

2. There is a maximum limit of 10 rotors (i.e. 11 continuation lines).

3. The Steiners term option (ZSTEIN) should only be used when analyzing solid
models in the fixed system.

4. The W3 parameter defines the reference frequency for structural damping


defined by PARAM,G.

5. The W4 parameter defines the reference frequency for structural damping


defined by GE.

6. Depending on element type, GE is specified on either material bulk entries,


property bulk entries, or on the element bulk entries themselves.

7. The W3 and W4 parameters are required for all direct solutions. In the modal
solutions, the eigenvalues are used as default. If the W3 and W4 parameters
are defined for modal analysis, they will be used, but these parameters are not
recommended for modal solutions.

8. The static centrifugal force is calculated for unit speed measured in rad/sec. On
the RFORCE bulk entry, the unit of Hz is used, thus the conversion 1/(2) =
0.159155 must be used by the user.

9. For calculating frequency response using synchronous analysis, the rotation


speeds are defined by the RSTART, RSTEP, and NUMSTEP fields on the
ROTORD bulk entry. The frequencies corresponding to these rotation speeds are
computed and the dynamic loads are calculated accordingly. The FREQi bulk
entry may contain only a dummy term, but its presence is mandatory.

10. For calculating the frequency or transient response using asynchronous analysis,
the unique rotation speed is defined by the RSTART field on the ROTORD
bulk entry. The RSTEP and NUMSTEP fields in this case will be ignored. The
frequency and dynamic load definitions are defined with the standard FREQ,
DLOAD, RLOAD, etc. bulk entries for frequency response, and with the TSTEP,
DLOAD, TLOAD, etc. bulk entries for transient response.

11. The rotor speed defined by RSTART, RSTEP, and NUMSTEP is called the
reference rotor speed. Rotors with relative speed defined by RSPEED will spin
at the defined factor multiplied by the reference rotor speed.

12. RSPEEDi entries must be either all real values or all integer values.
Combinations of real and integer entries are not allowed.
ROTORD 57
Define Rotor Dynamics Solution Options

13. The SYNC, ETYPE, and EORDER fields are ignored during a SOL 107 or SOL
110 complex eigenvalue analysis.

14. For additional information on how the values in the THRSHOLD and MAXITER
fields are used, see the PBEAR bulk entry.
58 CBEAR
Speed-Dependent Bearing Connection

CBEAR Speed-Dependent Bearing Connection

Defines speed-dependent bearing connection.

Format:

1 2 3 4 5 6 7 8 9 10
CBEAR EID PID GA GB

Example:
CBEAR 1 2 100 101

Fields:

Field Contents

EID Element identification number. (Integer > 0)

PID Property identification number of a PBEAR entry. (Integer


> 0)

GA, GB Grid point identification number of bearing connection


points. See Remark 2. (Integer > 0; GA GB)

Remarks:

1. Element identification numbers should be unique with respect to all other


element identification numbers.

2. List either GA or GB on ROTORG bulk entry for the rotor. The software
interprets this grid point as rotating, and interprets the other grid point as
stationary. If more than one rotor are present, the stationary grid point must be
listed on a ROTORB bulk entry.

3. You must define a GROUP bulk entry for each rotor that has corresponding
CBEAR entries. On each GROUP entry, list the CBEAR entries. Associate each
GROUP entry with a rotor on the BRGSETi field on the ROTORD entry.
PBEAR 59
Bearing Property Definition

PBEAR Bearing Property Definition

Defines stiffness and viscous damping matrices for bearing connection.

Format:

1 2 3 4 5 6 7 8 9 10
PBEAR PID TYPE TXX TXY TYX TYY NOMVAL

Example:
PBEAR 5 K 1001 1002 25.0 27.5
B 2001 2002 2003 2004

Fields:

Field Contents

PID Property identification number which is referenced by a CBEAR


entry. (Integer > 0)

TYPE Type of data in the TXX, TYY, TXY, and TYX fields on the same line.
See Remark 1. (Character: K, B, KD, KF, BD, BF)

If TYPE = K, specifies constant stiffness or stiffness that is a


function of rotor speed.

If TYPE = B, specifies constant viscous damping or viscous


damping that is a function of rotor speed.

If TYPE = KD, specifies constant stiffness or stiffness that is a


function of rotor speed and relative displacement. See Remark
2.

If TYPE = KF, specifies constant stiffness or stiffness that is a


function of rotor speed and relative force. See Remark 2.

If TYPE = BD, specifies constant viscous damping or


viscous damping that is a function of rotor speed and relative
displacement.

If TYPE = BF, specifies constant viscous damping or viscous


damping that is a function of rotor speed and relative force.
60 PBEAR
Bearing Property Definition

Field Contents

TXX, TXY, Stiffness or viscous damping matrix entry. See Remark 3. (Real or
TYX, TYY Integer 0 or blank; for default behavior, see Remark 4)

If TYPE = K, B:

If real entry, value of stiffness or viscous damping matrix entry


used for all rotor speeds.

If integer entry, identification number of a TABLEDi bulk entry


that defines the stiffness or viscous damping matrix entry as
a function of rotor speed. See Remark 5.

If TYPE = KD, KF, BD, BF:

If real entry, value of stiffness or viscous damping matrix entry


used for all rotor speeds and relative displacements or rotor
speeds and relative forces.

If integer entry, identification number of a TABLEST bulk entry


that defines the stiffness or viscous damping matrix entry as a
function of rotor speed and relative displacement or rotor speed
and relative force. The TABLEST bulk entry references a series
of TABLEDi bulk entries. The TABLEDi bulk entries contain
tabular data of stiffness or viscous damping vs. rotor speed at
constant values of relative displacement or relative force. See
Remark 5 and Remark 9.

NOMVAL Valid if TYPE = KD, KF, BD, BF. Field is ignored if TYPE =
K, B. See Remark 6. (Real 0.0)

For SOL 101, defines the relative displacement or relative force


that is used to either directly compute the bearing stiffness or
viscous damping, or initiate iteration for the bearing stiffness
or viscous damping. See Remark 7.

For SOLs 107, 110, defines the relative displacement or relative


force that is used to directly compute the bearing stiffness or
viscous damping.

Remarks:

1. TYPE = K,B are applicable for SOLs 101, 107, 108, 109, 110, 111, 112.
TYPE = KD, KF, BD, BF are applicable for SOLs 101, 107, 110.
PBEAR 61
Bearing Property Definition

2. Relative displacement is the displacement between the two coincident grids


used to define the CBEAR connection. Relative force is the force carried through
the CBEAR connection. The relative force is calculated from the relative
displacement.

3. X and Y in TXX, TXY, TYX, and TYY refer to the X- and Y-axes of the
coordinate system referenced in the RCORDi field of the ROTORD bulk entry.
In a rotor dynamic analysis, a rotors axis of rotation must be aligned with the
Z-axis of the coordinate system referenced in the RCORDi field of the ROTORD
bulk entry.

4. If any of TXX, TXY, TYX, and TYY fields are blank or zero (either integer zero or
real zero), the software uses real zero as the value for the corresponding field.

5. In TABLEDi bulk entries, enter rotor speed data in rad/time.

6. If a NOMVAL is defined in both a stiffness and damping row, the value in the
stiffness row is used.

7. When TYPE = KD, KF, BD, BF for SOL 101, the method used to
determine the stiffness and viscous damping for CBEAR elements depends on
the value of MAXITER.
If MAXITER = 0, the value specified in the NOMVAL field is used to directly
compute the bearing stiffness and viscous damping.

If MAXITER 0, the value specified in the NOMVAL field is used to


initiate iteration over relative displacement or relative force. Consecutive
iterations use the relative displacement and relative force from the previous
iteration to update the bearing stiffness and viscous damping. The relative
displacement or relative force magnitude on the CBEAR element at each
iteration is compared with the value from the previous iteration to evaluate
convergence. When iterating over relative displacement, convergence is
reached when:
|(Disp (old) - Disp (new)) / Disp (old)| < THRSHOLD
When iterating over relative force, convergence is reached when:
|(Force (old) - Force (new)) / Force (old)| < THRSHOLD
Iterating stops when either convergence is met, or the number of iterations
exceeds MAXITER.
MAXITER and THRSHOLD are specified on the ROTORD bulk entry.

8. When TYPE = KD, KF, BD, BF for SOL 101, only a single subcase
should exist. This is because the bearing stiffness and damping computed in an
62 PBEAR
Bearing Property Definition

initial subcase would be used in all successive subcases. This limitation will be
removed in a future release.

9. On a TABLEST bulk entry referenced by a PBEAR bulk entry, the values for
relative displacement or relative force that correspond to the TABLEDi bulk
entries must be consistently defined for all TABLEDi bulk entries. For example,
a valid entry is as follows:
PBEAR 789 KD 6891 6892 6893 6894
$
$ TABLEST tables for PBEAR
$
TABLEST 6891
0.0 7891 0.1 8891 0.3 9891 ENDT
TABLEST 6892
0.0 7892 0.1 8892 0.3 9892 ENDT
TABLEST 6893
0.0 7893 0.1 8893 0.3 9893 ENDT
TABLEST 6894
0.0 7894 0.1 8894 0.3 9894 ENDT

The following entry is invalid:


PBEAR 789 KD 6891 6892 6893 6894
$
$ TABLEST tables for PBEAR
$
TABLEST 6891
0.0 7891 0.1 8891 0.3 9891 ENDT
TABLEST 6892
0.0 7892 0.1 8892 0.4 9892 ENDT
TABLEST 6893
0.0 7893 0.1 8893 0.3 9893 ENDT
TABLEST 6894
0.0 7894 0.1 8894 0.3 9894 ENDT

The following entry is also invalid:


PBEAR 789 KD 6891 6892 6893 6894
$
$ TABLEST tables for PBEAR
$
TABLEST 6891
0.0 7891 0.1 8891 0.3 9891 ENDT
TABLEST 6892
0.0 7892 0.1 8892 0.3 9892 ENDT
TABLEST 6893
0.0 7893 0.1 8893 ENDT
TABLEST 6894
0.0 7894 0.1 8894 0.3 9894 ENDT

However, the tabular data entered on the TABLEDi bulk entries that are
referenced by a TABLEST bulk entry do not need to have the same range.
CBEAR force output 63

CBEAR force output


CBEAR elements are used to represent bearing support stiffness and viscous
damping.

Beginning with NX Nastran 9.0, you can use the FORCE case control command to
request element forces for CBEAR elements. For example, you can request element
forces for all elements including CBEAR elements by specifying:
FORCE = ALL

You can request element forces for any subset of elements by using the SET
case control command in conjunction with the FORCE case control command.
For example, you can request element forces for the elements 45, 56, 87, and 35
by specifying:
SET 100 = 45,56,87,35
FORCE = 100

In this example, the list of elements may or may not include CBEAR elements.
Chapter

4 Multi-step nonlinear solution 401

New multi-step nonlinear solution 401


A new NX Nastran solution sequence, SOL 401 - NLSTEP, has been created. SOL
401 is a multistep, structural solution which supports a combination of static
(linear or nonlinear) subcases and modal (real eigenvalue) subcases.
SOL 401 is the structural solution used by the NX multi-physics environment.
This environment is a new capability with the NX 9 Advanced Simulation product
release. NX 9 supports the one way coupling in which you can apply the resulting
temperatures from an NX Thermal solution to a consecutive SOL 401 structural
solution. In future NX releases, all combinations of structural-to-thermal and
thermal-to-structural coupling are planned.
This release of SOL 401 lays the groundwork for future nonlinear solution
capabilities. Over several releases, it will become a full purpose nonlinear solution
supported with the NX multiphysics environment, and also as a stand alone NX
Nastran solution.
Caveat

If your last solution time interval defined by the TSTEP1 entry coincides
with the last data point defined on the TABLEDi entry, the software will still
extrapolate a dummy table point, and will issue a warning regarding the data
extrapolation. You can disregard this warning since this is not an actual
solution time interval. See Mechanical Loads.

SOL 401 Topics


Subcase Analysis Type
Geometric Nonlinear Effects
Subcase Sequencing
Defining Solution Time Steps
Boundary Conditions
Mechanical Loads
Thermal Loads
66 New multi-step nonlinear solution 401

SOL 401 Topics


Element and Material Support
Surface-to-Surface Glue Support
Supported Output
Nonlinear Parameters
Solver Support
Input Summary
Example
New multi-step nonlinear solution 401 67

Subcase analysis type


SOL 401 allows a combination of static subcases and modal (real eigenvalue)
subcases. The first subcase must be a static subcase. After the first, the subcases
can be in any order. The ANALYSIS case control command defines the subcase
analysis type.
Modal subcase: You include ANALYSIS=MODAL in a subcase.

Static subcase: You include ANALYSIS=STATIC in a subcase.

The ANALYSIS case control command does not have a default in SOL 401. You
must defined it in every subcase, and it cannot be defined above the subcases
(globally).
Geometric Nonlinear Effects
The parameter LGDISP turns the nonlinear large displacement capability on/off
for the static subcases. If you define the parameter LGDISP for SOL 401, you must
include it in the bulk data portion of your input file. The single PARAM,LGDISP
setting applies to all static subcases.
PARAM,LGDISP,-1 (default) Large displacement effects are turned off.
Subcases which include ANALYSIS=STATIC are linear static subcases.

PARAM,LGDISP,1 Large displacement effects are turned on. Subcases


which include ANALYSIS=STATIC are nonlinear static subcases.

PARAM,LGDISP,1 turns on large displacement effects, but small strains are


assumed in this release.
Subcase sequencing
Subcase sequencing defines the initial time for a subcase. You can use the
new SEQDEP case control command to define a static subcase as sequentially
dependent (SD), or non-sequentially dependent (NSD).
SEQDEP=YES (default) the static subcase is an SD subcase.
SOL 401 uses time as the variable to increment loads. A static SD subcase uses
the final time from the previous static subcase for its start time. The start time
is used to compute the solution time steps. See Defining Solution Time Steps.

SEQDEP=NO the static subcase is an NSD subcase.


A static NSD subcase is independent. The start time for a static NSD subcase
is 0.0. See Defining Solution Time Steps.

Time does not apply to a modal subcases.


68 New multi-step nonlinear solution 401

The SEQDEP case control command setting only determines the start time for a
static subcase. The initial stiffness condition for a subcase is controlled with the
parameter inputs on the new NLCNTL bulk entry. For example, a modal subcase
can potentially include the stress stiffening, the follower stiffness, and the spin
softening from the previous static subcase. This depends on the type of loading in
the previous static subcase, and the parameter settings on the NLCNTL bulk entry.
Defining Solution Time Steps
Loads are defined in SOL 401 as a function of time. SOL 401 is a static solution,
and time is only used as the mechanism to increment loads. The new TSTEP1 bulk
entry defines the time step intervals in which a solution will be generated and
output in a static subcase. You include the TSTEP case control command in the
static subcase to select a specific TSTEP1 definition in the bulk data.
The TSTEP1 entry includes the end times (Tendi), the number of increments
(Ninci), and the increment for computing output (Nouti). The start time for a
particular subcase depends if it is sequentially dependent (SD) or not sequentially
dependent (NSD).

1 2 3 4 5 6 7 8 9 10
TSTEP1 SID Tend1 Ninc1 Nout1

Tend2 Ninc2 Nout2

Tend3 Ninc3 Nout3

-etc-

TSTEP1 Input Example:


TSTEP1 1 10.0 5 2
50.0 4 3
100 2 ALL

In this example, assuming a start time=0.0 for the subcase, the resulting time
steps are as follows. Output always occurs at the end time. The time steps in
which output occurs are highlighted.
The 1st row has an end time of 10.0, 5 increments, and output at every 2nd time
step.

Time Step 1 Time Step 2 Time Step 3 Time Step 4 Time Step 5
2.0 4.0 6.0 8.0 10.0

The 2nd row has an end time of 50.0, 4 increments, and output frequency at every
3rd time step.
New multi-step nonlinear solution 401 69

Time Step 1 Time Step 2 Time Step 3 Time Step 4


20.0 30.0 40.0 50.0

The 3rd row has an end time of 100.0, 2 increments, and output at all time steps.

Time Step 1 Time Step 2


75.0 100.0

In the same example, assuming a start time=5.0 for the subcase, the resulting time
steps for the first row are as follows.

Time Step 1 Time Step 2 Time Step 3 Time Step 4 Time Step 5
6.0 7.0 8.0 9.0 10.0

The 2nd and 3rd row are the same:

Time Step 1 Time Step 2 Time Step 3 Time Step 4


20.0 30.0 40.0 50.0

Time Step 1 Time Step 2


75.0 100.0

Additional Information about TSTEP1:


Output always occurs at Tendi.

Tendi must be increasing (Tendi < Tendi+1).

When Tend1=0.0,
o No other times are allowed. This is the only time for the associated
subcase.

o Ninci and Nouti are ignored.

o Results are output at time = 0.0.

Nouti controls the frequency of results output. The table below summarizes
the input options.

Nout Output frequency


YES Output occurs at all increments defined on TSTEP1.
END Output occurs at the end time.
70 New multi-step nonlinear solution 401

Output occurs at all increments on TSTEP1 and any


ALL
software subincrements.
Output is computed at every Nout increment specific with
Integer 0
TSTEP1.

The start time (Tstart) for a static subcase is determined as follows:


o If a static subcase definition in the case control includes SEQDEP=NO,
that subcase is not sequentially dependent (NSD). The start time for an
NSD subcase is 0.0.

o For a sequentially dependent (SD) static subcase (default), the final Tendi
from a previous SD or NSD static subcase is the start time (Tstart) for
the current SD subcase. If an SD subcase has no previous SD or NSD
static subcases, the start time is 0.0 for that SD subcase, and Tend1=0.0 is
permitted. Otherwise, Tend1 > Tstart for all other SD subcases.

Boundary Conditions
The SPC=n case control command selects either the SPC, SPC1, or SPCADD
bulk entry.
The SPC condition can change between subcases.
The SPC entry can optionally be used to define an enforced displacement.
An SPC entry cannot be defined as time dependent. That is, it cannot be
selected with the EXCITEID on the TLOAD1 entry.
The SPCFORCE case control command is supported to request the SPC force
output.

The MPC=n case control command selects either the MPC or MPCADD bulk
entry.
MPCs cannot change between subcases, so the MPC=n case control command
must be defined globally.
MPCs do not update for large displacements (PARAM,LGDISP,1).

Mechanical Loads
Mechanical loads are defined in SOL 401 as a function of time. SOL 401 is a static
solution, and time is only used as the mechanism to increment loads.
Load selection in Case Control:
o Loads are selected with the DLOAD case control command,
DLOAD=n
New multi-step nonlinear solution 401 71

where n points to a load set defined by a TLOAD1 bulk entry, or a DLOAD


bulk entry if you want to combine multiple TLOAD1 entries into a single
load set.

o The LOAD case control command is not supported. All static load
definitions must be defined as a function of time. A load which is constant
in time can be defined with a time function of constant value.

Load Definition in Bulk Data:

o TLOAD1 - Defines a time-dependent load.

o TABLEDi (i=1,2,3,4) - Table that defines the load variation with time.

o DLOAD - Combines several TLOAD1 entries.

Defining the TLOAD1 entry:

o The EXCITEID on TLOAD1 selects the static load set IDs.

o The supported static loads types are DAREA, FORCE, FORCE1, FORCE2,
GRAV, PLOAD, PLOAD4, RFORCE, RFORCE1 (New), and SLOAD.

o An enforced displacement condition defined with an SPC cannot be


selected on the EXCITEID field. See Boundary Conditions.

o A temperature load cannot be selected on the EXCITEID field. See


Thermal Loads.

o TYPE=0 must be selected.

o The TID field selects a TABLEDi, which defines a load scaling versus
time function.

o The figure below demonstrates how the DLOAD, TLOAD1, FORCE (for
example), and TABLEDi bulk entries relate to one another.
72 New multi-step nonlinear solution 401

o Load Input Example 1:


When there is more than one time-varying load set, the DLOAD bulk
entry is required:
$2345678$2345678$2345678$2345678$2345678$2345678$2345678$2345678$2345678
$
$ DLOAD COMBINES MULTIPLE TLOAD1 (102 AND 105)
DLOAD 17 1. 1. 102 1. 105
$
$ TIME-DEPENDENT FORCE, EXCITEID=125, TYPE=0 (DEFAULT), TIME FUNCTION TID=13
TLOAD1 102 125 13
$
FORCE 125 80 0 1. 3. 0. 0.
$
$ TIME FUNCTION 13 USED FOR FORCE LOAD
TABLED2 13 0. +
+ 0. 0. 1. 100. 2. 0. ENDT
$
$ TIME-DEPENDENT FORCE EXCITEID=3, TYPE=0 (DEFAULT), TIME FUNCTION TID=12
TLOAD1 105 3 1 12
$
FORCE 3 73 0 2. 8. 0. 0.
$
$ TIME FUNCTION 12 USED FOR FORCE LOAD
TABLED2 12 0. +
+ 0. 0. 2. 1. ENDT

o Load Input Example 2:


When there is only one time-varying load set, the DLOAD entry is not
required:
$2345678$2345678$2345678$2345678$2345678$2345678$2345678$2345678$2345678
$
$ TIME-DEPENDENT FORCE, EXCITEID=125, TYPE=0 (DEFAULT), TIME FUNCTION TID=13
TLOAD1 102 125 13
$
FORCE 125 80 0 1. 3. 0. 0.
PLOAD 125 100.0 21 30 18 10
New multi-step nonlinear solution 401 73

PLOAD 125 100.0 10 18 22 25


$
$ TIME FUNCTION 13 USED FOR LOAD
TABLED2 13 0. +
+ 0. 0. 1. 100. 2. 0. ENDT
$

Additional Information about Loads:


o Loads in any subcase are total loads as opposed to incremental loads from
the previous subcase. In other words, the ending load from a previous
subcase does not become the initial loading for the consecutive subcase.

o If no load is applied in a subcase, the total load is zero.

o DLOAD=n defined at the global level is used in all statics subcases unless
a different DLOAD=n is defined in a subcase.

o The new TSTEP1 bulk entry defines the time step intervals in which a
solution will be generated and output in a static subcase. If your time
steps defined by the TSTEP1 entry exceed the time values defined in your
TABLEDi entry, the software will extrapolate the data defined in the
TABLEDi entry. The software will issue a warning if extrapolation occurs.
There is one caveat. If your last solution time interval defined by the
TSTEP1 entry coincides with the last data point defined on the TABLEDi
entry, the software will still extrapolate a dummy table point, and will
issue the warning regarding the data extrapolation. You can disregard
this warning since this is not an actual solution time interval.

o In SOL 401, when RFORCE or RFORCE1 entries are referenced by the


EXCITEID field on a TLOAD1 entry, the data on the associated TABLEDi,
along with the scale factors S and Si on a DLOAD entry (if defined), scale
the angular velocity (w) and acceleration (a), which are used to compute an
inertia force in the equation F = [m] [w x (w x r)) + a x r]. Since w is squared
in the force computation, the resulting scaling is not linearly related to
the computed force (F). All other solutions scale the computed force (F).

Thermal Loads
Temperature loads are selected with the TEMP(LOAD) case control command.
TEMP(LOAD) can be defined both in a subcase and globally. The initial
temperature used for all subcases is selected with the TEMP(INIT) case control
command. TEMP(INIT) must be defined globally.
The TEMP(LOAD) and TEMP(INIT) case control commands select either the
TEMP or TEMPD bulk entry. The TEMP bulk entry defines a temperature on
74 New multi-step nonlinear solution 401

a grid point. The TEMPD bulk entry defines a temperature for all grid points
in which a TEMP entry is not defined.
Thermal strain is calculated in SOL 401 by
 = aload(Tload Tref) ainit(Tinit Tref)
where aload is evaluated at TEMP(LOAD), and ainit is evaluated at TEMP(INIT).
Tref is defined on the MATi entry.
The TVAR parameter on the NLCNTL bulk entry controls if the temperature loads
are ramped, or applied as a constant for each subcase.
When TVAR=RAMP, the software ramps the load temperatures from the
TEMP(LOAD) defined for the previous static subcase to the TEMP(LOAD)
defined for the current subcase. The software determines the load temperature
increments using the total number of time increments defined for that subcase.
If there is not a TEMP(LOAD) from the previous subcase, the software ramps
from TEMP(INIT) to the current TEMP(LOAD).

When TVAR=STEP, the load temperatures are applied as a constant for that
subcase.

The default is RAMP except when Tend1 = 0.0 is defined on the TSTEP1 entry in
the first static subcase. STEP occurs in this case.
Additional information:
The specification of TEMP(MATERIAL) or TEMP(BOTH) are unsupported
and will cause a fatal error if defined.

TEMP(LOAD) is used to update temperature-dependent material properties.


Temperature-dependent material properties are specified with MATi and
MATTi bulk entries.

You can turn off the thermal strain computation by defining the parameter
setting THRMST=NO (default=YES) on the NLCNTL bulk entry. This is useful
for temperature dependent material evaluation without thermal loading.

If TEMP(INITIAL) is defined, but TEMP(LOAD) is not defined in a specific


subcase, MATTi temperature dependent material properties are evaluated at
TEMP(INITIAL), and no thermal strains result for that subcase.

Note that if TEMP(LOAD) is specified in the modal subcase, it will be ignored.


Instead, TEMP(LOAD) from the previous static subcase will be used (if
specified).

The new OTEMP case control command can be included to request solution
temperature output.
New multi-step nonlinear solution 401 75

Element and Material Support


The 3D solids elements CTETRA, CHEXA, CPENTA and CPYRAM elements
are supported.

The mass elements CMASSi and CONMi are supported.

The solid elements support the nonlinear, large displacement capability


when PARAM,LGDISP,1 is defined. The elements behave linearly when
PARAM,LGDISP,-1 (default).

The PSOLID or the PCOMPS bulk entries define the element properties. The
PCOMPS is optionally used to define a layered solid composite property.

The supported material types include the following.


The MAT1 and MATT1 (temperature dependent) bulk entries define isotropic
materials.
The MAT9 and MATT9 (temperature dependent) bulk entries define
anisotropic materials.
The MAT11 and MATT11 (temperature dependent) bulk entries define
orthotropic materials.

Surface-to-Surface Glue Support


Surface-to-surface glue can be defined between the faces of the solid elements
CTETRA, CHEXA, CPENTA and CPYRAM.

The BGSET case control command, and the BGPARM, BGSET, BSURFS and
BCPROPS bulk entries are used to define the glue conditions. The BGSET
case control command must be above the subcases. As a result, the same glue
conditions apply to all static and modal subcases.

Only GLUETYPE=2 is supported. If you request GLUETYPE=1, the software


will continue the solution using GLUETYPE=2. See the BGPARM entry in the
Quick Reference Guide for a definition of GLUETYPE.

Large displacement effects defined with PARAM,LGDISP,1 are supported. The


glue element orientation updates as the solution proceeds.

The BGRESULTS case control command is supported to request the glue


forces and tractions in SORT1 format.

Supported Output

Case Control Description


76 New multi-step nonlinear solution 401

BGRESULTS Requests glue forces and tractions.


DISPLACEMENT Requests displacement output.
EKE Requests element kinetic energy output.
ELSTRN (New) Requests elastic strain at grid points on elements.
ESE Requests the output of the strain energy.
FORCE Requests element force output.
GELSTRN (New) Requests elastic strain at gauss points.
GPKE Requests kinetic energy at grid points in a modal subcase.
GSTRAIN (New) Requests strain at gauss points.
GSTRESS (New) Requests stress at gauss points.
GTHSTRN (New) Requests thermal strain at gauss points.
MEFFMASS Requests modal effective mass output in a modal subcase.
OLOAD Requests the form and type of applied load vector output.
OMODES Requests selects a set of modes for output.
OTEMP (New) Requests solution temperatures output on grid points.
SPCFORCES Requests single-point force of constraint vector output.
STRAIN Requests element strain output.
STRESS Requests element stress output.
THSTRN (New) Requests thermal strain at grid points on elements.

Nonlinear Parameters

The new NLCNTL bulk entry defines the parameters for SOL 401 control. The
NLCNTL=n case control command selects the NLCNTL bulk entry, and can be
defined in a subcase or globally. You can define the parameters on the NLCNTL
bulk entry using the following format.

1 2 3 4 5 6 7 8 9 10
NLCNTL ID Param1 Value1 Param2 Value2 Param3 Value3
Param4 Value4 Param5 Value5 -etc-

For example,
NLCNTL 1 EPSU 1E-3 EPSP 1E-3 EPSW 1E-7 +
+ CONV PW KSTEP 5 MAXITER 25

The supported parameters are listed below.


New multi-step nonlinear solution 401 77

Name Description

MAXITER Maximum number of iterations per time step. (Integer>0; Default=25)

CONV Convergence criterion. (Character; Default=W)

Any combination of U, P and W.

EPSU Error tolerance on displacement. (Real>0.0; Default=1.0E-2)

EPSP Error tolerance on force. (Real> 0.0; Default=1.0E-2)

EPSW Error tolerance on work . (Real> 0.0; Default=1.0E-6)

MAXDIV Number of divergences before solution is assumed to diverge. (Integer>0;


Default=3)

MAXBIS Maximum number of bisections allowed. (0<Integer<10; Default=5)

THRMST Controls the loading due to thermal strain in a static analysis (Character;
Default=YES)
YES
NO

TVAR Selects whether temperature loads are ramped or stepped. (Character;


Default=RAMP)
RAMP
STEP

SOLVER Selects the solver. (Character; Default=SPARSE)


SPARSE
PARDISO
ELEMITER

SPINK Spin softening flag. A modal subcase computes spin softening using the
RFORCE or RFORCE1 entries defined in the previous static subcase.
(Character; Statics default=NO; Modal default=YES)
YES
NO

STRESSK Stress stiffening flag. (Character; Statics default=YES; Modal default=YES)


YES
NO

FOLLOWK Follower stiffness flag. Follower stiffness is computed from the follower loads
defined with the FORCE1, FORCE2, PLOAD, or PLOAD4 entries. A modal
subcase computes the follower force using loads defined in the previous
static subcase. The static subcase uses loads defined in the current subcase.
(Character; Statics default=NO; Modal default=YES)
YES
NO
78 New multi-step nonlinear solution 401

Name Description

QNRITER Number of iterations before a stiffness update. If QNRITER=1, the Full Newton
Raphson method is used. (Integer>0; Default=5)

MSGLVL Diagnostic level. (Integer; Default=0)


0 - no additional diagnostic output.
1 -Convergence information is output for each iteration.

Solver Support
SOL 401 supports the sparse direct solver (default), the element iterative solver,
or the PARDISO solver (new NLTRD3 nonlinear solution module). To select the
SOL 401 solver type, supply a pair of fields on the NLCNTL card of the form
SOLVER SPARSE, SOLVER ELEMITER, or SOLVER PARDISO. The default
is SPARSE.
The sparse direct solver is a robust and reliable option, well-suited to sparse
models where accuracy is desired.

The element iterative solver, which is already supported in SOL 101, performs
particularly well with solid element-dominated models. It may be a faster
choice if lower accuracy is acceptable. As in SOL 101, convergence tolerances
and other options may be set by supplying an SMETHOD card in case control
and matching ITER card in bulk data.

The new PARDISO solver is a hybrid direct-iterative solver, potentially faster


with larger numbers of cores than the sparse solver but with slightly lower
accuracy.

Input Summary
You can use the following Parameters with SOL 401.
COUPMASS OGEOM POSTEXT
F56 (New) OMAXR PRGPST
GRDPNT OMPT PROUT
LGDISP OPG UNITSYS
MAXRATIO OUGCORD WTMASS
NOFISR POST

You can use the following Case Control commands with SOL 401.
ANALYSIS GSTRAIN (New) PARAM
BEGIN BULK GSTRESS (New) SEQDEP (New)
New multi-step nonlinear solution 401 79

BGRESULTS GTHSTRN (New) SET


BGSET INCLUDE SMETHOD
DISPLACEMENT LABEL SPC
DLOAD LINE SPCFORCES
ECHO MAXLINES STRAIN
EKE MEFFMASS STRESS
ELSTRN (New) METHOD SUBCASE
ELSUM MPC SUBTITLE
ESE NLCNTL (New) TEMP(INIT) and
TEMP(LOAD)
FORCE NSM THSTRN (New)
GELSTRN (New) OLOAD TITLE
GPKE OMODES TSTEP
GROUNDCHECK OTEMP (New) WEIGHTCHECK

You can use the following Bulk Data Entries with SOL 401.
ACCEL CORD3G MAT11 SLOAD
ACCEL1 CPENTA MAT9 SPC
BGADD CPYRAM MATCID SPC1
BGPARM CTETRA MATFT SPCADD
BGSET DAREA MATT1 SPOINT
BSURFS DLOAD MATT11 TABLED1
CHEXA ECHOOFF MATT9 TABLED2
CMASS1 ECHOON MPC TABLED3
CMASS2 EIGRL MPCADD TABLED4
CMASS3 ENDDATA NLCNTL (New) TABLEM1
CMASS4 FORCE PARAM TABLEM2
CONM1 FORCE1 PCOMPS TABLEM3
CONM2 FORCE2 PLOAD TABLEM4
CORD1C GRAV PLOAD4 TEMP
CORD1R GRDSET PLOTEL TEMPD
CORD1S GRID PMASS TLOAD1
CORD2C GROUP (New) PSOLID TSTEP1 (New)
CORD2R INCLUDE RFORCE
CORD2S MAT1 RFORCE1 (New)
80 New multi-step nonlinear solution 401

Example

For other examples of complete input files, see n401*.dat in


install_directory\nxn9\nast\tpl.
INIT MASTER(S)
NASTRAN SYSTEM(442)=-1, SYSTEM(319)=1, SYSTEM(554)=1, SYSTEM(556)=1
$
SOL 401
TIME 10000
CEND
TITLE=NX NASTRAN NL STATIC ANALYSIS SET
ECHO=NONE
LINE=80000
DISPLACEMENT(SORT1,PRINT)=ALL
STRESS=ALL
STRAIN=ALL
SPC=1
NLCNTL=1
$
SUBCASE 1
ANALYSIS=STATICS
DLOAD=1
TSTEPNL=1
PARAM,TSTATIC,1
$
SUBCASE 2
ANALYSIS=STATICS
DLOAD=2
TSTEPNL=2
PARAM,TSTATIC,1
$
SUBCASE 3
ANALYSIS=STATICS
DLOAD=1
TSTEPNL=3
PARAM,TSTATIC,1
$
BEGIN BULK
$
NLCNTL 1 EPSU 1E-3 EPSP 1E-3 EPSW 1E-7 +
+ CONV PW KSTEP 5 MAXITER 25
$
TSTEP1 1 1.0 100 100
TSTEP1 2 2.0 100 100
TSTEP1 3 3.0 100 100
$
PARAM,LGDISP,1
PARAM,POST,-1
PARAM,OGEOM,NO
PARAM,GRDPNT,0
$
CORD2C 1 0 0.0 0.0 0.0 0.0 0.0 1.0+
+ 1.0 0.0 1.0
CORD2S 2 0 0.0 0.0 0.0 0.0 0.0 1.0+
+ 1.0 0.0 1.0
$
TLOAD1 101 102 LOAD 2
$
FORCE 102 21 0 1.0 2.50+6 0.0 0.0
New multi-step nonlinear solution 401 81

FORCE 102 22 0 1.0 2.50+6 0.0 0.0


FORCE 102 23 0 1.0 2.50+6 0.0 0.0
FORCE 102 24 0 1.0 2.50+6 0.0 0.0
$
DLOAD 1 1.0 1.0 101
DLOAD 2 1.0 1.0 201
$
TLOAD1 201 202 LOAD 2
$
FORCE 202 21 0 1.0 1.25+6 0.0 0.0
FORCE 202 22 0 1.0 1.25+6 0.0 0.0
FORCE 202 23 0 1.0 1.25+6 0.0 0.0
FORCE 202 24 0 1.0 1.25+6 0.0 0.0
$
TABLED2 2 0.0 +
+ 0.0 1.0 1.0 1.0 ENDT
$
SPC1 1 123456 1
SPC1 1 123456 2
SPC1 1 123456 3
SPC1 1 123456 4
SPC1 1 2 5
SPC1 1 2 6
SPC1 1 2 7
SPC1 1 2 8
SPC1 1 2 9
SPC1 1 2 10
SPC1 1 2 11
SPC1 1 2 12
SPC1 1 2 13
SPC1 1 2 14
SPC1 1 2 15
SPC1 1 2 16
SPC1 1 2 17
SPC1 1 2 18
SPC1 1 2 19
SPC1 1 2 20
SPC1 1 2 21
SPC1 1 2 22
SPC1 1 2 23
SPC1 1 2 24
$
PSOLID 1 1 0
MAT1 1 206840.79553.85 0.307.8334-9 0.0 0.0
$
GRID 1 0 0.0 50.0 25.0 0
GRID 2 0 0.0 50.0 -25.0 0
GRID 3 0 0.0 -50.0 -25.0 0
GRID 4 0 0.0 -50.0 25.0 0
GRID 5 0 200.0 50.0 25.0 0
GRID 6 0 200.0 50.0 -25.0 0
GRID 7 0 200.0 -50.0 -25.0 0
GRID 8 0 200.0 -50.0 25.0 0
GRID 9 0 400.0 50.0 25.0 0
GRID 10 0 400.0 50.0 -25.0 0
GRID 11 0 400.0 -50.0 -25.0 0
GRID 12 0 400.0 -50.0 25.0 0
GRID 13 0 600.0 50.0 25.0 0
GRID 14 0 600.0 50.0 -25.0 0
GRID 15 0 600.0 -50.0 -25.0 0
GRID 16 0 600.0 -50.0 25.0 0
82 New multi-step nonlinear solution 401

GRID 17 0 800.0 50.0 25.0 0


GRID 18 0 800.0 50.0 -25.0 0
GRID 19 0 800.0 -50.0 -25.0 0
GRID 20 0 800.0 -50.0 25.0 0
GRID 21 0 1000.0 50.0 25.0 0
GRID 22 0 1000.0 50.0 -25.0 0
GRID 23 0 1000.0 -50.0 -25.0 0
GRID 24 0 1000.0 -50.0 25.0 0
$
CHEXA 1 1 5 6 7 8 1 2+
+ 3 4
CHEXA 2 1 9 10 11 12 5 6+
+ 7 8
CHEXA 3 1 13 14 15 16 9 10+
+ 11 12
CHEXA 4 1 17 18 19 20 13 14+
+ 15 16
CHEXA 5 1 21 22 23 24 17 18+
+ 19 20
$
ENDDATA
Chapter

5 Optimization

Equivalent Radiated Power as Design Response


Equivalent radiated power (ERP) was introduced in NX Nastran 8.5 as an output
option to quantify the noise level that radiates from a vibrating surface. ERP
output is a measure of the normal velocity distribution over the face of elements.
It is requested on panels composed of the shell elements CQUAD4, CQUAD8,
CQUADR, CTRIA3, CTRIA6, and CTRIAR.
In order to minimize noise radiated from a structure, it is important to identify
the areas of the structure that are the primary sources of the noise. Therefore,
beginning in NX Nastran 9, the ERP output can be defined as a design response
quantity on the DRESP1 bulk entry. ERP design responses are supported in SOL
200 for the MFREQ (modal frequency) and DFREQ (direct frequency) analysis
types. In addition, an ERP design response defined with the DRESP1 entry can be
used within the higher order response types, DRESP2 and DRESP3.
The two forms of ERP design responses available are:
ERP total magnitude on a panel.

ERP density on a panel, where density is the total magnitude divided by the
normal surface area of the panel.

An ERP design response can be associated with a single frequency or a set of


frequencies. When the ERP design response is associated with a set of frequencies,
a set of ERP responses is spawned so that there is a separate design response
for each frequency. The one exception to this is when the design response is an
integrated response over the set of frequencies. In this case, the design response
is considered to be a single response over the frequency set, and is treated as a
DRESP2 type response automatically.
For information on integrated responses, see Remark 20 of the DRESP1 bulk entry
in the NX Nastran Quick Reference Guide.
You are not required to define the ERP case control command to use ERP as a
design response in SOL 200. However, you should familiarize yourself with the
remarks on the ERP case control command, the PANEL bulk entry, and the SET3
84 Equivalent Radiated Power as Design Response

bulk entry. With SOL 200, each panel referenced in the ERP design responses is
referenced by the unique ID of a corresponding SET3 entry.
Theory for ERP sensitivity analysis with the adjoint load method
The approach adopted is to create a single composite adjoint load for an entire
panel so that the sensitivities (derivatives) are obtained directly.
The expression for the total derivative of the element ERP magnitude (ERPEi(w))
with respect to the element nodal displacements gives the adjoint load for that
particular element. Therefore, this derivative summed over the elements over
which the ERP is found (as for a panel) gives the corresponding adjoint load for the
ERP in question.
The adjoint load for the ERP magnitude on a single element is

where:
J The Jth Gauss point
hJ The relevant weighted surface area for the Jth Gauss point
[N] A matrix that converts the nodal displacements to the
displacements at the Gauss point
{t} A vector that transforms the Gauss point displacements to
the surface normal displacement at the Gauss point
{ur} The real part of the element nodal displacements vector,
{ug}
c A scaling coefficient, usually taken to be the product of
density and speed of sound for the fluid medium
w The frequency, in cycles per unit time, at which the ERP
magnitude is computed
The element ERP adjoint load becomes the basis for panel adjoint load for the
ERP design response. The adjoint load for the panel is then used to find the ERP
derivatives with respect to the design variables in the usual manner.
As for the panel ERP density derivatives, given that the ERP density for a panel
is defined as

where E is the ERP total magnitude over the panel, and A is the normal surface
area, the derivative of D with respect to a single design variable is then
Equivalent Radiated Power as Design Response 85

NX Nastran currently disregards changes in the panel normal surface area with
changes in the design variables. Therefore, the second term drops out, and the
derivative expression is simplified to

where dE/dx is obtained with the adjoint load approach described above.

General DRESP1 input format

1 2 3 4 5 6 7 8 9 10
DRESP1 ID LABEL RTYPE PTYPE REGION ATTA ATTB ATT1
ATT2 ATT3 ATT4 -etc.-

For an ERP response, the DRESP1 fields have the following definitions.

Field Contents

RTYPE Should be ERP for an ERP type response.

PTYPE Should be blank or PANEL.

REGION Not used.

ATTA Blank or 0: To specify ERP magnitude design responses.

1: To specify ERP density design responses.

See the Caveat below for more information on specifying ATTA.

ATTB Single frequency value to evaluate the ERP response.

If blank, all of the frequencies in the relevant frequency set are


used, spawning a design response for each frequency.

If character, then the character input refers to one of the


integrated response quantities described in Remark 20 of the
DRESP1 bulk entry.

ATTi List of relevant SET3 IDs referenced on PANEL bulk entries.


(i=1,2,3)
86 Equivalent Radiated Power as Design Response

ERP responses example 1

For this input example, the software will create ERP magnitude design responses
(ATTA is blank) for panels which are defined by the SET3 IDs 444 and 543, at all
of the frequencies in the relevant frequency set (ATTB is blank). Since there are 2
panels listed, if there are 10 frequencies in the frequency set, 20 separate DRESP1
responses are generated. That is, 10 responses for each panel.

DRESP1 333 EQRDPW1 ERP PANEL 444


543

ERP responses example 2

For this input example, the software will create ERP density design responses
(ATTA=1) for panels which are defined by the SET3 IDs 444, 543, 615, 789, and
793, at frequency 3.75 in a relevant frequency set. Since there are 5 panels listed,
5 separate DRESP1 responses are generated. That is, 1 response for each panel.

DRESP1 333 EQRDPW1 ERP PANEL 1 3.75 444


543 615 789 793

For examples of complete input files, see opterp*.dat in


install_directory\nxn9\nast\tpl.

Caveat

NX Nastran 9 does not trap specifying ATTA as integer < 0 or integer > 1.
If you specify ATTA as integer other than 0 or 1, ERP magnitude design
responses will be selected.

Future versions of NX Nastran will trap all values for ATTA except 0 or 1.
Thus, to assure the compatibility of your NX Nastran input file with future
versions, restrict specifying ATTA to 1 for ERP density design responses, and
0 or blank for ERP magnitude design responses.
DRESP1 87
Design Response Quantities

DRESP1 Design Response Quantities

Defines a set of structural responses that are used for the objective and/or design
constraints, or for sensitivity analysis purposes.

Format:

1 2 3 4 5 6 7 8 9 10
DRESP1 ID LABEL RTYPE PTYPE REGION ATTA ATTB ATT1

ATT2 ATT3 ATT4 -etc.-

DRESP1 1 DX1 STRESS PROD 2 3 102


103

Fields:

Field Contents

ID Unique entry identifier. (Integer>0)

LABEL User-defined label. (Character. See Bulk Data Syntax Rules.)

RTYPE Response type. See Table 5-1. (Character)

PTYPE Element flag (PTYPE = ELEM), or property entry name, or


panel flag for ERP responses (PTYPE = PANEL See Remark
33), or RANDPS ID. Blank for grid point responses. ELEM or
property name used only with element type responses (stress,
strain, force, etc.) to identify the relevant element IDs, or the
property type and relevant property IDs. (Character: ELEM,
PBAR, PSHELL, PCOMP, PANEL, etc.). PTYPE =
RANDPS ID when RTYPE = PSDDISP or PSDVELO or
PSDACCL. See Remarks 6 and 31.

REGION Region identifier for constraint screening. See Remark 10 for


defaults. (Integer>0)

ATTA Response attribute. See Table 5-1. See Remark 7. (Integer>0, or


Blank if specified)

ATTB Response attribute. See Table 5-1. (Integer>0 or Real>0.0 or


Character or Blank)
88 DRESP1
Design Response Quantities

Field Contents

ATTi List of response attributes. See Table 5-1. (Integer>0, or Blank


(i=1,2,3) if specified)

Table 5-1. Design Response Attributes


Response Attributes
Response Type ATTB (Integer>0 or ATTi (i=1,2,3...)
(RTYPE) ATTA (Integer>0, or
Real>0.0 or Character (Integer>0, or Blank
Blank if specified)
or Blank) if specified)

CEIG Complex Eigenvalue ALPHA or OMEGA Blank


Mode Number (Character)
(Default=ALPHA)
See Remark 22.

CFAILURE Failure Criterion LAMINA Number PCOMP Property entry


See Remark 2. Item Code (Integer>0; Default = PID(s)
1). See Remark 3. See Remark 6.

CSTRAIN Strain Item Code LAMINA Number PCOMP Property entry


See Remark 2. See Remark 1. (Integer>0; Default = PID(s)
1). See Remark 3. See Remark 6.

CSTRESS Stress Item Code LAMINA Number PCOMP Property entry


See Remark 2. See Remark 1. (Integer>0; Default = PID(s)
1). See Remark 3. See Remark 6.

DISP Displacement Blank Grid ID(s)


Component See Remark 27.

EIGN Normal Modes Mode Approximation Code Blank


See Remark 18. Number (Integer 1 or 2)
See Remark 19.

ERP For ERP magnitude: Frequency Value Panel related SET3 IDs
Blank or 0 (Blank or Real>0.0
or Character)
For ERP density: 1
See Remarks 15 and
See Remark 32. 20.

ESE Strain Energy Item Blank Property entry PID(s)


Code See Remark 6.
See Remark 21.

FLUTTER Blank Blank See Remark 14.

FORCE Force Item Code Blank Property entry PID(s)


See Remark 1. See Remark 6.
DRESP1 89
Design Response Quantities

Table 5-1. Design Response Attributes


Response Attributes
Response Type ATTB (Integer>0 or ATTi (i=1,2,3...)
(RTYPE) ATTA (Integer>0, or
Real>0.0 or Character (Integer>0, or Blank
Blank if specified)
or Blank) if specified)

FRACCL Acceleration Frequency Value Grid ID(s)


Component (Blank, Real>0.0 or See Remark 27.
See Remarks 8 and 9. Character)
See Remarks 15 and
20.

FRDISP Displacement Frequency Value Grid ID(s)


Component (Blank, Real>0.0 or See Remark 27.
See Remarks 8 and 9. Character)
See Remarks 15 and
20.

FREQ Normal Modes Mode Approximation Code Blank


See Remark 18. Number (Integer 1 or 2)
See Remark 19.

FRFORC Force Item Code Frequency Value Property entry PID(s)


See Remark 1. (Blank or Real>0.0 See Remark 6.
or Character)
See Remarks 15 and
20 .

FRSPCF SPC Force Frequency Value Grid ID(s)


Component (Blank, Real>0.0 or See Remark 27.
See Remarks 8 and 9. Character)
See Remarks 15 and
20.

FRSTRE Stress Item Code Frequency Value. Property entry PID(s)


See Remark 1. (Blank or Real>0.0 or See Remark 6.
Character)
See Remarks 15 and
20 .

FRVELO Velocity Component Frequency Value. Grid ID(s)


See Remarks 8 and 9. (Blank, Real>0.0 or See Remark 27.
Character)
See Remarks 15 and
20.

LAMA Buckling Mode Approximation Code Blank


Number (Integer 1 or 2)
See Remark 19.

PRES Acoustic Pressure Frequency Value Grid ID(s)


Component (Real>0.0) See Remark 27.
See Remark 15.
90 DRESP1
Design Response Quantities

Table 5-1. Design Response Attributes


Response Attributes
Response Type ATTB (Integer>0 or ATTi (i=1,2,3...)
(RTYPE) ATTA (Integer>0, or
Real>0.0 or Character (Integer>0, or Blank
Blank if specified)
or Blank) if specified)

PSDACCL Acceleration Frequency Value. Grid ID(s)


Component (Blank, Real>0.0 or See Remark 27.
See Remarks 26, 28, 29, See Remark 8. Character)
30. See Remarks 15 and
20.

PSDDISP Displacement Frequency Value. Grid ID(s)


Component (Blank, Real>0.0 or See Remark 27.
See Remarks 26, 28, 29, See Remark 8. Character)
30. See Remarks 15 and
20.

PSDVELO Velocity Component Frequency Value. Grid ID(s)


See Remark 8. (Blank, Real>0.0 or See Remark 27.
See Remarks 26, 28, 29, Character)
30. See Remarks 15 and
20.

RMSACCL Acceleration RANDPS ID Grid ID(s)


Component (Integer>0) See Remark 27.
See Remarks 26, 30. See Remark 8.

RMSDISP Displacement RANDPS ID Grid ID(s)


Component (Integer>0) See Remark 27.
See Remarks 26, 30. See Remark 8.

RMSVELO Velocity Component RANDPS ID Grid ID(s)


See Remark 8. (Integer>0) See Remark 27.
See Remarks 26, 30.

SPCFORCE SPC Force Blank Grid ID(s)


Component See Remark 27.

STABDER AESTAT or AESURF Restraint Flag. Component


Entry ID (Integer 0 or 1)
See Remark 13.

STRAIN Strain Item Code Blank Property entry PID(s)


See Remark 1. See Remark 6.

STRESS Stress Item Code Blank Property entry PID(s)


See Remark 1. See Remark 6.

TACCL Acceleration Time Value (Blank, Grid ID(s)


Component Real>0.0, or Character) See Remark 27.
See Remarks 16 and
20.
DRESP1 91
Design Response Quantities

Table 5-1. Design Response Attributes


Response Attributes
Response Type ATTB (Integer>0 or ATTi (i=1,2,3...)
(RTYPE) ATTA (Integer>0, or
Real>0.0 or Character (Integer>0, or Blank
Blank if specified)
or Blank) if specified)

TDISP Displacement Time Value (Blank, Grid ID(s)


Component Real>0.0, or Character) See Remark 27.
See Remarks 16 and
20.

TFORC Force Item Code Time Value. (Blank or Property entry PID(s)
See Remark 1. Real>0.0 or Character) See Remark 6.
See Remarks 16 and
20 .

TRIM AESTAT or AESURF Blank Blank


Entry ID

TSPCF SPC Force Time Value. (Blank, Grid ID(s)


Component Real>0.0, or Character) See Remark 27.
See Remarks 16 and
20.

TSTRE Stress Item Code Time Value. (Blank or Property entry PID(s)
See Remark 1. Real>0.0 or Character) See Remark 6.
See Remarks 16 and
20 .

TVELO Velocity Component Time Value (Blank, Grid ID(s)


Real>0.0, or Character) See Remark 27.
See Remarks 16 and
20.

VOLUME Blank Blank SEIDi or ALL

WEIGHT Row Number Column Number SEIDi or All or blank


(1 ROW 6) (Integer)
See Remark 25. (1 COL 6)

Remarks:

1. Stress, strain, and force item codes can be found in Item Codes. For stress or
strain item codes that have dual meanings, such as von Mises or maximum
shear, the option specified in the Case Control Section will be used; i.e.,
STRESS(VONM) or STRESS(MAXS). Note that item codes may vary depending
on whether CENTER or CORNER is chosen with the relevant output request in
case control.

2. RTYPE = CSTRESS, CSTRAIN, and CFAILURE are used only with the
PCOMP and PCOMPG entries. CSTRESS and CSTRAIN item codes are
92 DRESP1
Design Response Quantities

described under Table 1 (Element Stress/Strain Item Codes) in Item Codes.


CFAILURE item codes are described under Table 2 (Element Force Item Codes)
in Item Codes. Only force item codes that refer to failure indices of direct stress
and interlaminar shear stress are valid.
The CFAILURE response type requires the following specifications on the
applicable entries:

Failure theory in the FT field on PCOMP entry.

Allowable bonding shear stress in the SB field on PCOMP entry.

Stress limits in the ST, SC, and SS fields on all MATi entries.

3. ATTB is used only for responses of composite laminae, dynamics, complex


eigenvalue, and stability derivatives. For other responses, this field must be
blank. When including the ID of a PCOMPG entry in a DRESP1 response, the
lamina number entered in the ATTB field is relative to the order of the ply
definitions (1,2,3, ..) and is not the global ply id.

4. All grids associated with a DRESP1 entry are considered to be in the same
region for screening purposes. Only up to NSTR displacement constraints
(see DSCREEN entry) per group per load case will be retained in the design
optimization phase.

5. DRESP1 identification numbers must be unique with respect to DRESP2 and


DRESP3 identification numbers.

6. If PTYPE = ELEM, the ATTi correspond to element identification numbers. If


RTYPE=ERP and PTYPE = blank or PANEL, the ATTi correspond to one or
more panel related SET3 IDs (as in the PANEL bulk data).

7. If RTYPE = DISP, TDISP, TVELO, TACCL, TSPCF, TFORC or


TSTRE, multiple component numbers (any unique combination of the digits 1
through 6 with no embedded blanks) may be specified on a single entry. Multiple
response components may not be used on any other response types.

8. For grid frequency response type DRESP1, i.e. those starting with FR, RMS,
or PSD, only one component number may be specified in the ATTA field.
Numbers 1 through 6 correspond to real (or magnitude) components and 7
through 12 imaginary (or phase) components. If more than one component for
the same grid is desired, then a separate entry is required.
Note that, in case the response is used for a constraint, the choice of response
computation format (real/imaginary vs. magnitude/phase) will affect constraint
values. See also Remark 9.
DRESP1 93
Design Response Quantities

9. Real/imaginary representation is the default for complex response types.


Magnitude/phase representation must be requested by the corresponding Case
Control command; e.g., DlSP(PHASE) = ALL.

10. REGION is used for constraint screening. The NSTR field on DSCREEN entries
gives the maximum number of constraints retained for each region per load case.

IF RTYPE = WEIGHT, VOLUME, LAMA, EIGN or FREQ, no REGION


identification number should be specified. For all other responses, if the REGION
field is left blank, the default specified in Table 5-2 is used. Usually, the default
value is appropriate.
If the REGION field is not blank, all the responses on this entry as well as all
responses on other DRESP1 entries that have the same RTYPE and REGION
identification number will be grouped into the same region.

Table 5-2. Default Regions for Design Sensitivity Response Types

Response Type Default Region

EIGN No region

FREQ No region

LAMA No region

VOLUME No region

WEIGHT No region

DISP One region per DRESP1 entry

ERP One region per DRESP1 entry

FLUTTER One region per DRESP1 entry

FRACCL One region per DRESP1 entry

FRDISP One region per DRESP1 entry

FRSPCF One region per DRESP1 entry

FRVELO One region per DRESP1 entry

PRES One region per DRESP1 entry

SPCFORCE One region per DRESP1 entry

TACCL One region per DRESP1 entry

TDISP One region per DRESP1 entry

TSPCF One region per DRESP1 entry


94 DRESP1
Design Response Quantities

Table 5-2. Default Regions for Design Sensitivity Response Types

Response Type Default Region

TVELO One region per DRESP1 entry

OTHER One region per PROPERTY entry. If PTYPE = ELEM, then


one region per DRESP1 entry

11. REGION is valid only among the same type of responses. Responses of different
types will never be grouped into the same region, even if they are assigned the
same REGION identification number by the user.

12. If RTYPE = WEIGHT or VOLUME, field ATTi = ALL implies total


weight/volume of all superelements except external superelements.

13. RTYPE = STABDER identifies a stability derivative response. ATTB is the


restraint flag for the stability derivative. ATTB = 0 means unrestrained, and
ATTB = 1 means restrained. For example, ATTA = 4000, ATTB = 0, and ATT1
= 3 reference the unrestrained Cz derivative for the AESTAT (or AESURF)
entry ID = 4000.

14. RTYPE = FLUTTER identifies a set of damping responses. The set is specified
by ATTi:
ATT1 = Identification number of a SET1 entry that specifies a set of modes.
ATT2 = Identification number of an FLFACT entry that specifies a list of
densities.
ATT3 = Identification number of an FLFACT entry that specifies a list of Mach
numbers.
ATT4 = Identification number of an FLFACT entry that specifies a list of
velocities.
If the flutter analysis is type PKNL, it is necessary to put PKNL in the PTYPE
field of this entry.

15. For RTYPE = ERP, FRDISP, FRVELO, FRACCL, FRSPCF, FRFORC,


FRSTRE, PSDDISP, PSDVELO, and PSDACCL, a real value for ATTB
specifies a frequency value in cycles per unit time. If ATTB is specified, then
the responses are evaluated at the closest frequency selected by the OFREQ
command. The default for ATTB is all frequencies selected by the OFREQ
command. See Remark 20 for additional ATTB options.

16. For RTYPE = TDISP, TVELO, TACCL, TSPCF, TFORC, and TSTRE,
ATTB specifies a time value. If ATTB is specified, then the responses are
DRESP1 95
Design Response Quantities

evaluated at the closest time selected by the OTIME command. The default for
ATTB is all time steps selected by the OTIME command.

17. Intermediate station responses on CBAR elements due to PLOAD1 and/or


CBARAO entries may not be defined on the DRESP1 entry.

18. RTYPE = EIGN refers to normal modes response in terms of eigenvalue


(radian/time)**2 while RTYPE = FREQ refers to normal modes response in
terms of natural frequency or units of cycles per unit time.

19. For RTYPE = LAMA, EIGN or FREQ, the response approximation used for
optimization can be individually selected using the ATTB field. (Approximation
Code = 1 = direct linearization, = 2 = Inverse Linearization).

20. Character input for ATTB is available for RTYPE of ERP, FRDISP, FRVELO,
FRACCL, FRSPCF, PSDDISP, PSDVELO, PSDACCL, TDISP, TVELO, TACCL,
TSPCF, FRFORC, FRSTRE, TFORC, and TSTRE. The character input
represents a mathematical function and the options for character input are
SUM, AVG, SSQ, RSS, MAX and MIN. The expression of mathematical function
is shown as follows:

MAX (X1, X2, ..., Xn) = Largest value among Xi (i=1 to n)


MIN (X1, X2, ..., Xn) = Smallest value among Xi (i=1 to n)
where Xi is the response for a forcing frequency. For example
DRESP1,10,DX1,FRSTRE,ELEM,,3,AVG,10
96 DRESP1
Design Response Quantities

yields a response which is equal to the average stress for element 10. The average
is done by first adding up the component 3 stress of element 10 for all forcing
frequencies (all time steps for transient response), and then dividing by the
number of forcing frequencies. Note that the response computed is considered as
type 2 response. Therefore, if referenced on a DRESP2, the ID of such DRESP1
(ATTB with character input) must be listed following the DRESP2 keyword.
Such DRESP1 may only be referenced from a DRESP2 (not from a DRESP3),
and may only be nested one level. That is, the referencing DRESP2 may not be
referenced further from another DRESP2 or a DRESP3.
(Important note: If any such integrated response DRESP1 is either erroneously
or intentionally referred to as DRESP1 from within a DRESP2 or DRESP3,
the program will spawn multiple responses over the frequency set, or, for the
objective function, take only the value corresponding to the first frequency in
the set, not the integrated response, whether or not the DRESP1 is DRSPAN
related.)

21. Element strain energy item codes can be found in Element Strain Energy Item
Codes. Only element strain energy and element strain energy density can be
referenced on a DRESP1 entry.

22. For RTYPE=CEIG, the allowable character inputs are ALPHA (for the real
component) and OMEGA (for the imaginary component), with ALPHA being
the default.

23. For RTYPE=RMSDISP, RMSVELO, or RMSACCL the ATTB specifies the


appropriate RANDPS ID.

24. Input other than 1 or 7 of ATTA field, acoustic pressure component, for PRES
response type will be reset to 1 (if less than 7) or 7 (if greater than 7 and less
than 13).

25. Design response weight is obtained from the Grid Point Weight Generator for a
reference point (see the parameter GRDPNT). For SOL 200, if PARAM,GRDPNT
is either not defined, equal to zero, or not a defined grid point, the reference point
is taken as the origin of the basic coordinate system. Fields ATTA and ATTB
refer to the row and column numbers of the rigid body weight matrix, which is
partitioned as follows:
DRESP1 97
Design Response Quantities

The default value of ATTA and ATTB is 3, which specifies the Wz value.
Typically the value of Wx, Wy, and Wz each equal the weight of the structure.
Although, if directional mass is defined, which is possible using the CONM1,
CMASS, or DMI bulk entries, the values can be different. If you are uncertain
about the weight matrix value to use in your response, include the parameter
GRDPNT to print the weight matrix in the .f06 file.
The first field of ATTi: ATT1 = ALL implies total weight of all superelements
except external superelements. When the ATTi fields contain SEIDi, each SEIDi
refers to a superelement identification number. SEIDi= 0 refers to the residual
superelement. The default for this first field of ATTi, ATT1, is blank which
is equivalent to ALL.

26. PSD and RMS type DRESP1 responses are meaningful only for those random
loading frequency response analysis subcases listed in the RANDPS bulk data
referred to by the relevant RANDOM ID.

27. Multiple grid point IDs in the ATTi fields are supported.

28. Since PSD type DRESP1 responses are a summation over the sets of relevant
subcases correlated in the RANDPS bulk data, a constraint on a PSD type
DRESP1 response should be specified only in the lead subcase of such a batch of
subcases. Any PSD response specified otherwise will be ignored. For example,
if the subcases referred to by RANDPS ID=75 are (3,3); (4,4); (5,5); and (3,5),
where the last two numbers indicate cross-correlation among two subcases,
any PSD response for this particular RANDPS ID should be placed in subcase
3, as that is the lead subcase.

29. If a PSD type response is to appear in a DRESP2 or DRESP3 response together


with responses from other subcases, it should then be assigned to the lead
98 Expanding optimization for larger problems

subcase defined in item 28 above by an appropriate DRSPAN case control


command and a related set.

30. Models with superelements will either ignore any RMS and PSD type DRESP1
design responses, or will fail in the presence of such DRESP1.

31. For PBUSHT, PDAMPT, and PELAST property types, currently use PBUSH,
PDAMP, or PELAS, as appropriate, in the PTYPE field, since the latter have the
same IDs as the corresponding frequency dependent properties.

32. ATTA can be 0 for ERP magnitude responses. This is equivalent to leaving it
blank.

33. Currently, for ERP design responses, any entry or blank in the PTYPE field
defaults to PANEL.

Expanding optimization for larger problems


Beginning with NX Nastran 9, the ability of the software to optimize larger
models is enhanced with the introduction of selective modification of design
variable bounds. Selective modification of design variable bounds reduces the
computational effort required to solve optimization problems that contain a large
number of designed properties that are linearly related to a single design variable.
Many practical problems have designed properties that are linearly related to a
single design variable. For example, consider the case where the thickness of each
ply of a composite shell element is proportional to the thickness of all other plies
of the same element. You can:
1. Define a single arbitrary design variable, X.

2. Define a designed property for each ply thickness, t.

3. Linearly relate the design variable and the ply thickness. An example of such
a linear relationship is t = CX, where C is a constant.

When you use the new approach, the software is able to drastically reduce the
problem size through selective modification of design variable bounds, wherein any
critical property bounds are transferred to those of the design variables.
For NX Nastran 9, the default behavior includes selective modification of design
variable bounds, and the optimizer enhancements introduced with NX Nastran
8.5. You can optionally use system cell 539 to override the default behavior.

System cell setting Optimizer behavior


NASTRAN SYSTEM(539)=0 NX Nastran 8.1 enhancement level (old default behavior)
Expanding optimization for larger problems 99

System cell setting Optimizer behavior


NASTRAN SYSTEM(539)=1 NX Nastran 8.5 enhancement level
NX Nastran 8.1 enhancement level plus selective
NASTRAN SYSTEM(539)=2
modification of design variable bounds
NX Nastran 8.5 enhancement level plus selective
NASTRAN SYSTEM(539)=3 modification of design variable bounds (new default
behavior)

Selective modification of design variable bounds


NX Nastran not only allows lower and upper bounds to be specified for design
variables, but also for designed properties that are functions of design variables.
While design variable bounds can never be violated, the lower and upper bounds
for designed properties are applied in a manner similar to that for response
constraints. Thus, if a response is violated more than a property bound, the
property bound will remain violated, whether it is a real, user specified bound,
or a bound imposed on the designed property for that particular cycle due to
automatically applied move limits.
Even when property bounds are not specified, move limits still may constrain the
designed properties. The property bounds add constraints to the problem, and may
increase the problem size considerably. In the case of designed properties linearly
related to only one design variable, it is possible to remove the bounds on the
designed properties by transferring more restrictive bounds to the related design
variables using the linear relationship. This removes any relevant constraints
that were based on the property bounds. In some cases, this drastically reduces
the problem size.
For example, consider the case where a designed property, P, and a design variable,
X, are linearly related as follows:
P = 3.0 + 2.0*X
Solving for X yields:
X = (P 3.0)/2.0
Suppose the bounds for P and X are specified to be:
10.0 P 30.0
and
2.0 X 9.0
Applying the property bounds to the above equation for X gives:
3.5 X 13.5
100 Expanding optimization for larger problems

The new lower bound of 3.5 is more restrictive than the specified lower bound of
2.0. Thus, the bounds for X are modified such that:

3.5 X 9.0

and the bounds on the property P are removed.

If an even more restrictive value for the lower bound of the same X is found from
another designed property, then the bound is further modified.

Move limit factors remain a problem, as they are, in general, different for designed
properties and for design variables.

If a design variable limit is modified due to property bounds, the property move
limit factor is transferred to the design variable for that design cycle. However,
this procedure will be fine tuned in later versions, as smaller property move
limits applied to design variables may sometimes slow down moves away from the
infeasible region. In the meantime, as a best practice, use larger than default
move limits for such designed properties related to only a single design variable
if slow progress is expected or noted.

To realize the full benefit of selective automatic property bound removal, starting
design variable values and any user defined move limits factors (DELX and DELP
in the DOPTPRM bulk entry) have to be well thought out prior to running a
large job.

For example, consider a design variable with the following bounds:

0.0001 X 10.0

and a starting value of X = 0.001 with a DELX of 1.0. The software will quickly hit
a move limit imposed bound, thus adding a possibly redundant side constraint to
the problem size. For this example, a starting value of X = 1.0 would, in general, be
a much better choice.

When design variable bounds are modified as above, the current default for
property move limit of DELP = 0.2 may be too conservative. A minimum value of
DELP = 0.5 is recommended.

The value of DELP = 0.5 is expected to replace the current default in later versions
of NX Nastran.
Chapter

6 Advanced nonlinear

Plastic-cyclic material model


The new MATPLCY bulk entry is available for solutions 601 and 701 to define
a plastic-cyclic material model. The new model provides unique inputs for the
isotropic hardening rule, the kinematic hardening rule, and the rupture criterion.
This material model is based on
The von Mises yield condition

A flow rule using the von Mises yield function

An isotropic and/or kinematic hardening rule. The isotropic and kinematic


hardening rules used in the plastic-cyclic model are suitable for use in
modeling cyclic plasticity.

The new material model can be used with the rod (CONROD, CROD), Hermitian
beam (CBAR, CBEAM), plane stress (CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8),
plane strain (CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8), axisymmetric
(CQUADX4, CQUADX8, CTRAX3, CTRAX6), 3-D solid (CHEXA, CPENTA
, CTETRA, CPYRAM), and shells (CQUAD4, CQUAD8*, CTRIA3, CTRIA6,
CQUADR, CTRIAR).
* The CQUAD8 entry supports the plastic-cyclic material only when ELCV=1
is included in the NXSTRAT entry. ELCV=1 converts the CQUAD8 to a 9-node
element.
The new material model can be used with the small displacement/small strain,
large displacement/small strain and large displacement/large strain formulations.
Large displacement/large strain kinematics are not supported by the rod and
beam elements.
Composite shell elements using a PCOMP property are not supported by the
plastic-cyclic material.
Inputs
The new MATPLCY bulk entry defines the new material model.
102 Bolt preload with 3D solid elements

1 2 3 4 5 6 7 8 9 10

MATPLCY MID E NU RHO A ISO KIN RUP

BETA MAXITE RTOL

The ISO, KIN, RUP fields select the PLCYISO, PLCYKIN, PLCYRUP bulk entries
to define isotropic, kinematic and rupture parts of the plastic-cyclic model. If you
leave the KIN or RUP fields undefined, the software will ignore the kinematic and
rupture portions of the material model.
See section 3.4.2, Plastic-cyclic material model in the Advanced Nonlinear Theory
and Modeling Guide for a description of all inputs.
For examples of complete input files, see anlplcy*.dat in
install_directory\nxn9\nast\tpl.

Bolt preload with 3D solid elements


You can now model bolts with the solid elements CHEXA, CPENTA, CTETRA, or
CPYRAM elements for solution 601. The BOLT bulk entry, which is used to select
the elements representing the bolt, has been updated with the new ETYPE=3
option.

1 2 3 4 5 6 7 8 9 10
BOLT BID ETYPE=3 CSID IDIR GP
EID1 EID2 EID3 EID4 EID5 EID6 EID7 EID8
EID9 THRU EID10 BY INC
-etc-

When ETYPE=3 (this option is specifically for solution 601):


All CHEXA, CPENTA, CPYRAM, or CTETRA elements representing the bolt
must be included in EIDi. All of the elements must have the same property ID.

The software splits the bolt mesh at the grid point entered in the GP field.

The bolt-plane is defined using the IDIR field. The bolt plane gives the bolt
direction and the approximate location of the bolt split faces. When IDIR = 0
or blank (default), the direction of the bolt is automatically determined by the
software as the direction with minimum principal moment of inertia. CSID
is ignored when IDIR = 0 or blank.

GP = 0 or blank is allowed only if IDIR = 0 or blank. In this case, the location


of the bolt plane is automatically determined by the program.
Edge-to-edge glue 103

The program outputs the bolt direction and bolt cross-sectional area for each bolt
during data file generation. This information can be used to confirm that the
bolt plane is defined correctly.
For more information, see section 10.7.2 3D-bolt in the Advanced Nonlinear
Theory and Modeling Guide.
For examples of complete input files, see anlbolt*.dat in
install_directory\nxn9\nast\tpl.

Edge-to-edge glue
Edge-to-edge glue is now supported in solution 601 for the following elements:
Axisymmetric elements CTRAX3, CQUADX4, CTRAX6, CQUADX8

Plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8

Plane strain elements CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8

You use the existing BGSET bulk entry to pair the element regions. An edge pair is
defined with the BEDGE entry.
The two glued edges can have different mesh densities. The glue definition results
in a smooth transition of displacements and tractions between these edges.

Table 6-1. Glue Summary in solution 601


Type Description
Glue between the edges of axisymmetric, plane
Edge-to-Edge
stress, and plane strain elements.
Surface-to-Surface Glue between solid element faces.

See section 5.9, Mesh gluing in the Advanced Nonlinear Theory and Modeling
Guide.
For examples of complete input files, see anlbedg1*.dat in
install_directory\nxn9\nast\tpl.

New rotational load RFORCE1


The RFORCE bulk entry is supported in solutions 601 and 701 to define an angular
velocity (w) and/or acceleration (a) to all grid-points. The following inertia forces
are computed at all grid points as a result of an RFORCE defintion.
104 New rotational load RFORCE1

Beginning in NX Nastran 9, the new RFORCE1 bulk entry is available to apply


an angular velocity (w) and/or acceleration (a) inertia load to the grid points
associated to specific elements.

The RFORCE1 entry has the following input format.

1 2 3 4 5 6 7 8 9 10
RFORCE1 SID G CID A R1 R2 R3 METHOD
RACC MB GROUPID

The GROUPID field selects the ID of a GROUP bulk entry, which is also a new
feature for this release. You will use the GROUP entry to select a list of element
or physical property IDs. If you select property IDs, the software automatically
determines the associated elements. The RFORCE1 load is then computed at the
grid-points associated with these elements.

Elements which are not in your GROUP do not contribute to the resulting
grid-point mass used to compute the load. For example, if a grid-point is used by
elements A and B, but only element A is included in the GROUP, the mass of
element A contributes to the grid-point mass used to compute the RFORCE1 load.
The mass of element B does not contribute.

This behavior is unique to solutions 601 and 701. Using the same example, the
other NX Nastran solutions use the mass contribution of both elements A and B
when computing the RFORCE1 load.

See section 5.4, Inertia loads -centrifugal and mass proportional loading in the
Advanced Nonlinear Theory and Modeling Guide.

For examples of complete input files, see anlrforce1*.dat in


install_directory\nxn9\nast\tpl.
Chapter

7 Element enhancements

CTETRA stress recovery in SOLs 106 and 129


In versions prior to NX Nastran 9, in SOLs 106 and 129 with material plasticity,
the software computes the stress and strain at the grid points of CTETRA elements
as follows:

1. The strain field is evaluated at specific integration points to obtain the total
strain at those points.

2. The elastic strain, plastic strain, and stress are directly computed at the
integration points.

3. The elastic strain, plastic strain, and stress at the integration points are
extrapolated to the grid points.

Because the elastic strain, plastic strain, and stress are extrapolated to the grids
independently, the values at the grids may not lie on the stress-strain curve for
the material.

Beginning with NX Nastran 9, in SOLs 106 and 129 with material plasticity, the
software computes the stress and strain at the grid points of CTETRA elements as
follows:

1. The strain field is evaluated at specific integration points to obtain the total
strain at those points.

2. The total strain at the integration points is extrapolated to the grid points.

3. The elastic strain, plastic strain, and stress are computed at the grids from
extrapolated total strain.

This method assures that the values for elastic strain, plastic strain, and stress
that are recovered at the grid points lie on the stress-strain curve of the material.
Chapter

8 Miscellaneous

Line numbers in PUNCH file


A new system cell is available to optionally turn off the line numbers in the
PUNCH file.
Including the following system setting will turn off the line numbers.
NASTRAN SYSTEM(560)=1 -or- NASTRAN PCHLN=1

The line numbers, which appear in columns 73-80, are on by default.


For example, the line numbers are on (default) in the punch output below.
...
$DISPLACEMENTS 4
$REAL OUTPUT 5
$SUBCASE ID = 1 6
$POINT ID = 1 7
0.000000E+00 G 0.000000E+00 0.000000E+00 0.000000E+00 8
-CONT- 0.000000E+00 0.000000E+00 0.000000E+00 9
5.000000E-05 G 0.000000E+00 0.000000E+00 0.000000E+00 10
...

The line numbers have been turned off in the punch output below.
...
$DISPLACEMENTS
$REAL OUTPUT
$SUBCASE ID = 1
$POINT ID = 1
0.000000E+00 G 0.000000E+00 0.000000E+00 0.000000E+00
-CONT- 0.000000E+00 0.000000E+00 0.000000E+00
5.000000E-05 G 0.000000E+00 0.000000E+00 0.000000E+00
...

Multiple ACCEL1 bulk entries


The ACCEL1 bulk entry defines an acceleration load on specific grids. Previously,
the load set identification number (SID) on an ACCEL1 entry could not be the
same as the SID defined on other ACCEL1 entries. The LOAD bulk entry was
required to combine multiple ACCEL1 entries.
For example,
108 Multiple ACCEL1 bulk entries

...
$* CASE CONTROL
LOAD = 101
...
$* BULK DATA
...
LOAD 1011.0000001.000000 21.000000 3
...
ACCEL1 2 01.000000 10.0000 0.0000 0.0000 +
+ 5 THRU 8 11 12 15 16 19+
+ 20 23 THRU 25 28 30 32
...
ACCEL1 3 01.000000 20.0000 0.0000 0.0000 +
+ 1 THRU 4 9 10 13 14 17+
+ 18 21
...

Beginning with NX Nastran 9, the SID on an ACCEL1 entry can be the same as
the SID defined on other ACCEL1 entries. As a result, multiple ACCEL1 entries
with the same SID are now permitted, and the LOAD bulk entry is not required.

For example,
...
$* CASE CONTROL
LOAD = 2
...
$* BULK DATA
...
ACCEL1 2 01.000000 10.0000 0.0000 0.0000 +
+ 5 THRU 8 11 12 15 16 19+
+ 20 23 THRU 25 28 30 32
...
ACCEL1 2 01.000000 20.0000 0.0000 0.0000 +
+ 1 THRU 4 9 10 13 14 17+
+ 18 21
...

Note that the SID on an ACCEL1 entry cannot be the same as the SID defined on
other types of load entries. For example, you cannot use the same SID on ACCEL1
and FORCE entries. The LOAD bulk entry is required to combine these loads.

For example,
...
$* CASE CONTROL
LOAD = 101
...
$* BULK DATA
...
LOAD 1011.0000001.000000 21.000000 3
...
ACCEL1 2 01.000000 10.0000 0.0000 0.0000 +
+ 5 THRU 8 11 12 15 16 19+
+ 20 23 THRU 25 28 30 32
...
ACCEL1 2 01.000000 20.0000 0.0000 0.0000 +
DMAP compiler warning messages 109

+ 1 THRU 4 9 10 13 14 17+
+ 18 21
...
FORCE 3 13 01.5000+5 0.00001.000000 0.0000
FORCE 3 14 03.5000+4 0.00001.000000 0.0000
...

DMAP compiler warning messages


You can now suppress DMAP compiler warning messages that arise because of
undefined input or output to DMAP commands. To suppress the warning messages,
include the following instruction in your input file:
NASTRAN SYSTEM(580)=1

Numerical precision of matrix data written to OP4 files


Beginning with NX Nastran 9, you can control the numerical precision of matrix
data that NX Nastran writes to OP4 files for the EXTSEOUT and MBDEXPORT
case control commands. To do so, include the new DIGITS parameter in your input
file. The value you specify for the DIGITS parameter represents the number of
digits after the decimal point for the matrix data. Thus, for the default value of
15, there are actually 16 digits of precision because of the one digit that precedes
the decimal point.
110 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)
EXTSEOUT(STIF,MASS,DAMP,GEOM,EXTID=600)

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 loads matrix and associated DTI,SELOAD entries.


See Remarks 1, 2, and 21.
EXTSEOUT 111
External Superelement Creation Specification

Describer Meaning

GEOM Store geometry. See Remark 20.

ASMBULK Generate bulk 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 portion of
the subsequent assembly solution. See Remarks 4 and 13.

EXTBULK Generate and store bulk 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 section 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 entries stored on the assembly
punch file (.asm) if ASMBULK is specified and in the BEGIN
SUPER bulk entry stored on the standard punch file (.pch) if
DMIGPCH or MATOP4 is specified. See Remarks 3, 4, 5, and 7.

DMIGSFIX = cccccc is the suffix (up to six characters and must not = any
cccccc 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 through
11.

DMIGSFIX = The seid defined by the EXTID keyword is the suffix that is
EXTID 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 through 11.

MATDB (or Store the boundary matrices and other information on the
MATRIXDB) database (default).

DMIGDB Similar to MATDB (or MATRIXDB) except that the boundary


matrices are stored as DMIG bulk entries on the database.
112 EXTSEOUT
External Superelement Creation Specification

Describer Meaning

DMIGOP2 = Store the boundary matrices as DMIG bulk entries on an


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

DMIGPCH Store the boundary matrices as DMIG bulk entries on the


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

MATOP4 Store the boundary matrices on an OP4 file whose Fortran unit
= unit (or number is given by unit. (Integer 0)
MATRIXOP4
= unit) If unit > 0, matrices are written to the OP4 file in sparse
format.

If unit < 0, matrices are written to the OP4 file in full matrix
format.

See Remarks 3, 5, 6, 13, 14, and 23.

Remarks:

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


are specified, then all of the boundary matrices are stored by default. If any
subset of the describers STIFFNESS, MASS, DAMPING, K4DAMP, and LOADS
are specified, then only the boundary matrices specified 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 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


EXTSEOUT 113
External Superelement Creation Specification

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


MATDB, DMIGDB, or DMIGOP2) is specified, the following bulk 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

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 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)


114 EXTSEOUT
External Superelement Creation Specification

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)

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.
EXTSEOUT 115
External Superelement Creation Specification

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
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 absolute value of unit.

15. The creation of an external superelement using EXTSEOUT involves running a


NX Nastran job with the following additional data:
The data for the creation of the external superelement is specified by the
EXTSEOUT case control command, which must appear above the subcase
level.

The boundary points of the external superelement are specified by


ASET/ASET1 bulk entries.

If the creation involves component mode reduction, the required generalized


coordinates are specified using QSET/QSET1 bulk entries. The boundary
data for the component mode reduction may be specified using the
BNDFIX/BNDFIX1 and BNDFREE/BNDFREE1 bulk entries (or their
equivalent BSET/BSET1 and CSET/CSET1 bulk 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 bulk
entries can be obtained in the assembly job even if there is no output request
specified for these points in the creation run.
116 EXTSEOUT
External Superelement Creation Specification

If the assembly job involves the use of PARAM bulk entries, then the
following points should be noted:
o PARAM entries specified in the main bulk portion of the input data
apply only to the residual and not to the external superelement.

o PARAM entries specified in the BEGIN SUPER portion of the bulk


section for an external superelement apply only to the superelement.

o 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 section. 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 exist, they will be ignored.


The existence of the EXTSEOUT case control command takes precedence over
PARAM,EXTOUT and PARAM,EXTUNIT.

18. This capability is enabled in SOLs 101, 103, 107-112, 114, 115, 118, 129, 144-146,
159, and 187. This capability is not enabled for thermal analyses or models that
contain fluids. For SOL 103, this capability will create the external superelement
and also create the component results and data blocks to be written to an .op2 file
if requested. For the other solution sequences, this capability will only create the
external superelement and no other analyses will be performed. Superelement
EXTSEOUT 117
External Superelement Creation Specification

results can be recovered in the second step (i.e. superelement assembly, analysis,
and data recovery) for SOLs 101, 103, 105, 107-112, and 144-146.

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.).

20. The GEOM describer will output geometry data blocks GEOM1EXA,
GEOM2EXA, and GEOM4EXA containing all of the external superelement
geometry to support post-processing. This describer only works for the MATDB
(or MATRIXDB), DMIGDB, and DMIGOP2 storage options. By default, the full
geometry will not be exported; the GEOM describer must be explicitly defined to
have these geometry data blocks written.

21. The LOADS describer will output load information in the [Pa] matrix along
with associated DTI,SELOAD bulk entries for each load represented in the
[Pa] matrix. DTI,SELOAD bulk entries will not be output for the DMIGPCH
option; the use of the DMIGPCH option requires the use of the P2G case control
command in the system analysis in order to access the load information defined
in the [Pa] matrix that is stored in DMIG format. Thermal loads and enforced
motion loads using the SPCD bulk data definition method are not supported.
The load information and DTI,SELOAD bulk entries that are output depend on
the method in which loads are defined and referenced.
Static solutions. For example, SOL 101:
In a creation run, the LOAD = n case control command will create a single
load. The [Pa] matrix will have a single column that contains the load
values referenced by n. The corresponding LIDSE and EXCSE values on
the DTI,SELOAD bulk entry will be the value n.
To select this load in a system run, the LIDSE field on the SELOAD bulk
entry should equal the value of n from the creation run.

In a creation run, the LOADSET = n case control command is generally


used to create multiple loads. Each definition of an LSEQ bulk entry will
create a column in the [Pa] matrix regardless of whether or not the LSEQ
is referenced by the LOADSET = n case control command. However, an
unreferenced LSEQ will generate a null column in the [Pa] matrix. The
corresponding LIDSE and EXCSE on an DTI,SELOAD bulk entry will be
the value of LID and EXCITEID, respectively, on an LSEQ bulk entry.
To select these loads in a system run, the LIDSE field on the SELOAD bulk
entry should equal the value of an EXCITEID from the creation run.

If both LOADSET and LOAD appear in the case control, LOADSET takes
precedence.
118 EXTSEOUT
External Superelement Creation Specification

Dynamic solutions. For example, SOL 103:

In a creation run, a column in the [Pa] matrix is created for each load (not
enforced motion) defined on RLOADi and TLOADi bulk entries whether
or not they are referenced in the case control. The corresponding LIDSE
and EXCSE on the DTI,SELOAD bulk entries will both be the value of
EXCITEID on the RLOADi or TLOADi bulk entry.
To select these loads in a system run, the LIDSE field on the SELOAD entry
should equal the value of an EXCITEID from the creation run.

In a creation run, the LOADSET = n case control command can be used to


create multiple loads. Each definition of an LSEQ bulk entry will create a
column in the [Pa] matrix. A LSEQ bulk entry must be referenced by a
LOADSET case control command in order to generate a column in the [Pa]
matrix. The corresponding LIDSE and EXCSE on an DTI,SELOAD bulk
entry will be the value of LID and EXCITEID, respectively, on an LSEQ
bulk entry.
To select these loads in a system run, the LIDSE field on the SELOAD entry
should equal the value of an EXCITEID from the creation run.

22. To include differential stiffness in the definition of an external superelement, two


subcases are required in the creation run. The first subcase is a static subcase.
The second subcase performs the analysis and generation of the external
superelement. To obtain the displacement field used to generate the differential
stiffness effects, include a STATSUB case control command in the second subcase
that references the first subcase. Always include the EXTSEOUT case control
command above the subcase level. An example of the required setup is as follows:

SOL 112
CEND
TITLE =
EXTSEOUT()
$
SUBCASE 1
$ STATIC SUBCASE
LOAD = 11
$
SUBCASE 2
$ DYNAMIC SUBCASE
TSTEP = 100
STATSUB = 1
METHOD = 10
DLOAD = 20
BEGIN BULK

For accuracy and consistency, the loads used to generate differential stiffness for
the external superelement during the creation run should be the same loads used
EXTSEOUT 119
External Superelement Creation Specification

in the system run without any scaling. If the loads are scaled by a non-unity
scaling factor from a case control command like P2G or a bulk entry like LOAD,
the differential stiffness portion of the external superelement stiffness matrix
will no longer be consistent with the applied loads.
The ability to generate an external superelement including differential
stiffness effects is available for SOLs 103, 107-112, and 187. For SOL 112,
the IC(STATSUB,DIFFK) or IC(TZERO,DIFFK) case control commands can
be used to generate differential stiffness effects instead of the STATSUB case
control command.

23. For the MATOP4 (or MATRIXOP4) option, the number of digits of precision for
matrix data is controlled by the DIGITS parameter.
120 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 solution 103, 111, or 112.

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 ADAMS STANDARD FLEXBODY=YES FLEXONLY=NO
MBDEXPORT FLEXBODY=YES MINVAR=FULL
MBDEXPORT OP4=22 STANDARD FLEXBODY=YES
MBDEXPORT OP4=22 STATESPACE FLEXBODY=YES
MBDEXPORT MATLAB STANDARD FLEXBODY=YES
MBDEXPORT MATLAB STATESPACE FLEXBODY=YES
MBDEXPORT SIMPACK FLEXBODY=YES
MBDEXPORT 121
Multi-Body Dynamics Export

General Describers:

Describer Meaning

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

ADAMS Generate ADAMS Interface Modal Neutral File (MNF).

SIMPACK Generate SIMPACK Flexible Body Input (FBI) file.

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 RECURDYN, ADAMS, SIMPACK, 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 RECURDYN, ADAMS or SIMPACK.

4. MBDEXPORT must appear above the subcase level.

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


RECURDYN STANDARD Describers:

Describer Meaning

FLEXBODY Requests the generation of RFI (required).

NO Standard NX Nastran solution without RFI creation. (default)

YES RFI generation requested.


122 MBDEXPORT
Multi-Body Dynamics Export

Describer Meaning

FLEXONLY Determines if DMAP solution and data recovery runs or not


after RFI creation is complete.

YES Only RFI creation occurs. (default)

NO RFI file creation occurs along with standard DMAP solution


and data recovery.

MINVAR Determines how mass invariants are computed.

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

CONSTANT Mass invariants 1,2,3 and 9 are computed.

FULL All nine mass invariants are computed.

NONE No mass invariants are computed.

PSETID 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 Determines if grid point stress is written to RFI.

NO Do not write grid point stress to RFI. (default)

YES Write grid point stress to RFI.

OUTGSTRN Determines if grid point strain is written to RFI.

NO Do not write grid point strain to RFI. (default)


MBDEXPORT 123
Multi-Body Dynamics Export

Describer Meaning

YES Write grid point strain to RFI.

RECVROP2 Requests that the FLEXBODY run output an NX Nastran OP2


file for use in post processing of RecurDyn/Flex results.

NO OP2 file will not be generated. (default)

YES OP2 file will be generated.

CHECK Requests debug output be written to the f06 file when


RECVROP2=YES. (See Remark 20)

NO No debug output will be written. (default)

YES 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, 111, or 112 analysis only. RFI files are named jid_seid.rfi, where seid is the
integer number of the superelement (0 for residual). 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 entry DTI,UNITS.

3. Because RecurDyn is not a unitless code, the Data Table Input bulk entry
DTI,UNITS is required for an MBDEXPORT RECURDYN FLEXBODY=YES
run. The DTI,UNITS entry specifies the system of units of the original NX
Nastran input file, and is then included with the data written to the RFI file.
NX Nastran does not do a units conversion of the nastran data when writing the
RFI file. Once identified, the units will apply to all superelements in the model.
The complete format is:
DTI UNITS 1 MASS FORCE LENGTH TIME

All entries are required. Acceptable character strings are listed below.

Mass:
KG - kilogram
124 MBDEXPORT
Multi-Body Dynamics Export

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)
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)
MBDEXPORT 125
Multi-Body Dynamics Export

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)


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 entries to define the attachment points.

6. The eight mass variants are:


126 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.
MBDEXPORT 127
Multi-Body Dynamics Export

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 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.

9. OMIT or OMIT1 bulk 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 and CBEND 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 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
128 MBDEXPORT
Multi-Body Dynamics Export

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.

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 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, 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.
MBDEXPORT 129
Multi-Body Dynamics Export

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.

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.
Because 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.


130 MBDEXPORT
Multi-Body Dynamics Export

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.

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).

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.
MBDEXPORT 131
Multi-Body Dynamics Export

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
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.
If differential stiffness is included, the static portion of the results will not be
included in the recovered results when using MBDRECVR.

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.

22. Preload conditions are not supported.

23. To request differential stiffness, include a static subcase that contains the
stress-stiffening loads. In another subcase include STATSUB = n where n is the
number of the static subcase.

ADAMS STANDARD Describers:

Describer Meaning

FLEXBODY Requests the generation of MNF.


132 MBDEXPORT
Multi-Body Dynamics Export

Describer Meaning

NO Standard NX Nastran solution without MNF creation. (default)

YES MNF generation requested.

FLEXONLY Determines if DMAP solution runs or not after MNF creation is


complete.

YES Only MNF creation occurs. (default)

NO MNF file creation occurs along with standard DMAP solution.

MINVAR Determines how mass invariants are computed.

PARTIAL Mass invariants 5 and 9 are not computed. (default)

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

FULL All nine mass invariants are computed.

NONE No mass invariants are computed.

PSETID 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 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.

OUTGSTRS Determines if grid point stress is written to MNF.

NO Do not write grid point stress to MNF. (default)

YES Write grid point stress to MNF.


MBDEXPORT 133
Multi-Body Dynamics Export

Describer Meaning

OUTGSTRN Determines if grid point strain is written to MNF.

NO Do not write grid point strain to MNF. (default)

YES Write grid point strain to MNF.

RECVROP2 Requests that the FLEXBODY run output an NX Nastran OP2


file for use in post processing of ADAMS/Flex results.

NO OP2 file will not be generated. (default)

YES OP2 file will be generated.

CHECK Requests debug output be written to the f06 file when


RECVROP2=YES. (See Remark 18)

NO No debug output will be written. (default)

YES Debug output will be written.

ADAMS STANDARD Remarks:

1. The creation of the Adams MNF, which is applicable in a non-restart


SOL 103, 111, or 112 analysis only, is initiated by MBDEXPORT ADAMS
FLEXBODY=YES (other describers are optional) and the inclusion of the bulk
entry DTI,UNITS. MNF files are named jid_seid.mnf, where seid is the integer
number of the superelement (0 for residual). The location of these files is the
same directory as the jid.f06 file.

2. Because ADAMS is not a unitless code, the Data Table Input bulk entry
DTI,UNITS is required for an MBDEXPORT ADAMS FLEXBODY=YES run.
The DTI,UNITS entry specifies the system of units of the original NX Nastran
input file, and is then included with the data written to the MNF file. NX
Nastran does not do a units conversion of the nastran data when writing the
MNF file. Once identified, the units will apply to all superelements in the model.
The complete format is:
DTI UNITS 1 MASS FORCE LENGTH TIME

All entries are required. Acceptable character strings are listed below.

Mass:
KG - kilogram
LBM pound-mass (0.45359237 kg)
134 MBDEXPORT
Multi-Body Dynamics Export

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)
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)
MBDEXPORT 135
Multi-Body Dynamics Export

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)
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. Because 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 entries to define the attachment points.

5. The nine mass variants are:


136 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.
MBDEXPORT 137
Multi-Body Dynamics Export

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
of modes (n) is specified on the EIGR (METHOD=LAN) or EIGRL bulk 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 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 and CBEND 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 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.
138 MBDEXPORT
Multi-Body Dynamics Export

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
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
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,
MBDEXPORT 139
Multi-Body Dynamics Export

CAEROi, CDUMi, CHACAB, CHACBR, CHBDYx, CDAMP3, CDAMP4,


CELAS3, CELAS4, CFLUIDi, CMASS3, CMASS4, CRAC2D, CRAC3D, 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:
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 1000 1001 1002 1003
4 1007 1006 1005 1004
4 1000 1004 1005 1001
4 1001 1005 1006 1002
4 1002 1006 1007 1003
4 1003 1007 1004 1000

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


lines (two node faces), as shown below:

8
2 101 102
2 102 103
2 103 104
2 104 105
2 105 106
2 106 107
2 107 108
2 108 109

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

Typical Parameters:

PARAM,RESVEC,character_value controls calculation of residual vector


modes.
140 MBDEXPORT
Multi-Body Dynamics Export

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.

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.
Because 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.
MBDEXPORT 141
Multi-Body Dynamics Export

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.

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).

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
142 MBDEXPORT
Multi-Body Dynamics Export

control capability to perform results recovery from an ADAMS/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.
If differential stiffness is included, the static portion of the results will not be
included in the recovered results when using MBDRECVR.

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.
By default, the full modal damping matrix is written to the MNF. If only the
diagonal modal damping values are desired, include the parameter setting
PARAM,NONCUP,-2 in your bulk data.
MBDEXPORT 143
Multi-Body Dynamics Export

21. Preload conditions are not supported.

22. To request differential stiffness, include a static subcase that contains the
stress-stiffening loads. In another subcase include STATSUB = n where n is the
number of the static subcase.

SIMPACK STANDARD Describers:

Describer Meaning

FLEXBODY Requests the generation and writing of standard matrices


(CMS) to an FBI file.

NO NX Nastran solution without standard matrix generation.


(default)

YES Standard matrix generation requested.

FLEXONLY Determines if DMAP solution runs or not after standard matrix


generation is complete.

YES Only standard matrix generation occurs. (default)

NO Standard matrix generation occurs along with the DMAP


solution.

PSETID Selects a set of elements defined in the OUTPUT(PLOT) section


(including PLOTEL) whose connectivity is exported to the FBI
file. See Remark 13.

NONE All grids, geometry and associated modal data is written to the
FBI file. (default)

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


geometry and associated model data.

ALL The connectivity of all element sets are used to export geometry
and associated model data.

RECVROP2 Requests that the FLEXBODY run output an NX Nastran OP2


file for use in post processing of results. See Remark 16.

NO OP2 file will not be generated. (default)

YES OP2 file will be generated.


144 MBDEXPORT
Multi-Body Dynamics Export

Describer Meaning

CHECK Requests debug output be written to the f06 file when


RECVROP2=YES. See Remark 17.

NO No debug output will be written. (default)

YES Debug output will be written.

SIMPACK STANDARD Remarks:

1. The creation of a SIMPACK Flexible Body Input (FBI) file is applicable in


a non-restart SOL 103, 111, and 112 analysis only. FBI files are named
jid_seid.fbi, where seid is the integer number of the superelement (0 for
residual). The location of these files is the same directory as the jid.f06 file.

2. The creation of the FBI file is initiated by MBDEXPORT SIMPACK


FLEXBODY=YES (other describers are optional) and the inclusion of the bulk
entry DTI,UNITS. This is only valid for a Component Mode Synthesis (CMS)
analysis. Thus, it is necessary to define the modal coordinates using the SPOINT
bulk entry, and to define them to be in the q-set using the QSET/QSET1 or
SEQSET/SEQSET1 bulk entries as appropriate.

3. The Data Table Input bulk entry DTI,UNITS, which is required for an
MBDEXPORT SIMPACK FLEXBODY=YES run, specifies the system of units in
the original NX Nastran input file. When NX Nastran creates the FBI file, it
converts the nastran data from the units defined on the DTI,UNITS entry to SI
units. Once identified, the units will apply to all superelements in the model.
The complete format is:
DTI UNITS 1 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)
MBDEXPORT 145
Multi-Body Dynamics Export

MG milligram (1E-6 kg)


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 (1E-2 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)
146 MBDEXPORT
Multi-Body Dynamics Export

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)


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 FBI file, the units defined in
WTMASS, which are important for units consistency in NX Nastran, are ignored
in the output to the FBI file. 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 FBI file 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 entries to define the attachment points. Note
that the values corresponding to these attachment points in the CMS-reduced
mass and stiffness matrices written to the FBI file will be defined in the
nodal displacement coordinate systems of these attachment points. The user
must account for these coordinate systems when loading or restraining these
attachment points within the SIMPACK run.

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). In
the above equation for ns, the number of modes (n) is specified on the EIGR
(METHOD=LAN) or EIGRL bulk entries; the number of load cases is p. In
general, you cannot have too many SPOINTs. Excess SPOINTs will be truncated
with no performance penalty.

7. OMIT and OMIT1 bulk entries are not supported.


MBDEXPORT 147
Multi-Body Dynamics Export

8. 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 formulation.

9. P-elements and CBEND 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.

10. PARAM,WTMASS,value with a value other than 1.0 may be used with an NX
Nastran run generating an FBI file. It must have consistent units with regard
to the DTI,UNITS bulk entry. Before generating the FBI file, NX Nastran will
appropriately scale the WTMASS from the physical mass matrix and mode
shapes.

11. There is a distinction between how an MBDEXPORT SIMPACK


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.

12. 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 SIMPACK 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.

13. To reduce the FE mesh detail for dynamic simulations, PSETID can include
the ID of a SET entry. PSETID is also used to define the grids to be included
in the recovery matrix that is written to the FBI file. The SET entry lists
PLOTEL or element IDs, whose connectivity is exported into the FBI file to
display the components in SIMPACK. This option can significantly reduce the
size of the FBI file without compromising accuracy in the SIMPACK simulation.
148 MBDEXPORT
Multi-Body Dynamics Export

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 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 SIMPACK. 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 SIMPACK. 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 FBI file, 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, CPYRAM, CRAC2D,
CRAC3D, CTWIST, CWEDGE, CWELD, and GENEL.

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

Typical Case Control:

MBDEXPORT SIMPACK FLEXBODY=YES is required for FBI file


generation.

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

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.

Typical Bulk Data:

DTI,UNITS,1,MASS,FORCE,LENGTH,TIME is required for FBI file


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

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.
MBDEXPORT 149
Multi-Body Dynamics Export

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).

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


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

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

15. MBDEXPORT and ADAMSMNF case control entries cannot be used in the same
analysis run. In other words, a SIMPACK FBI 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.

16. The RECVROP2=YES option is used when you would like results recovery (using
the MBDRECVR case control entry) from a SIMPACK 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 a SIMPACK 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
150 MBDEXPORT
Multi-Body Dynamics Export

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.
If differential stiffness is included, the static portion of the results will not be
included in the recovered results when using MBDRECVR.

17. 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.

18. 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.

19. Preload conditions are not supported.

20. To request differential stiffness, include a static subcase that contains the
stress-stiffening loads. In another subcase include STATSUB = n where n is the
number of the static subcase.

OP4 Describers:

Describer Meaning

unit The OP4 file is written to the specified logical unit number.
(Integer 0)

If unit > 0, matrices are written to the OP4 file in sparse format.

If unit < 0, matrices are written to the OP4 file in full matrix
format.

The absolute value of the logical unit number must match the
unit number on an ASSIGN statement.

FLEXBODY Requests the generation and writing of standard or state-space


matrices to an OP4 file.

NO NX Nastran solution without standard or state-space matrix


generation. (default)

YES Standard or state-space matrix generation requested.


MBDEXPORT 151
Multi-Body Dynamics Export

Describer Meaning

FLEXONLY Determines if DMAP solution runs or not after standard or


state-space matrix generation is complete.

YES Only standard or state-space matrix generation occurs. (default)

NO Standard or state-space matrix generation occurs along with


the standard DMAP solution.

RECVROP2 Requests that the FLEXBODY run output an NX Nastran OP2


file for use in post-processing of controls results. See Remark 7.

NO OP2 file will not be generated. (default)

YES OP2 file will be generated.

CHECK Requests debug output be written to the f06 file when


RECVROP2=YES. See Remark 8.

NO No debug output will be written. (default)

YES 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,
111, or 112 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 absolute value for unit on the MBDEXPORT OP4=unit
case control command.
The number of digits of precision for matrix data is controlled by the DIGITS
parameter.
For a model with superelements, only one OP4 file will be generated. This OP4
file will be generated for the first superelement (or the residual) that satisfies the
conditions defined in Remarks 3 and 4. For standard matrices, if user-defined set
U8 is not defined, the residual will be written to the OP4.
152 MBDEXPORT
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/USET1 bulk entries for
partitioned superelements and refer to the SEUSET/SEUSET1 bulk entries for
non-partitioned superelements.

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/USET1 bulk entries for partitioned superelements and refer to the
SEUSET/SEUSET1 bulk entries for non-partitioned superelements.

5. For the state-space option, the OP4 file contains the [A], [B], [C], and [E]
state-space matrices. They are defined as AMAT, BMAT, CMAT, and EMAT,
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 OP4 file contains the modal mass, equivalent modal
viscous damping, modal stiffness, mode shapes, and modal forces defined as
MMASS, MDAMP, MSTIF, U8PHIX, and MFORC, respectively. The physical
DOF corresponding one-to-one with the rows of U8PHIX 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
MBDEXPORT 153
Multi-Body Dynamics Export

This capability is limited to one superelement per NX Nastran model.


Residual-only analyses are supported.
If differential stiffness is included, the static portion of the results will not be
included in the recovered results when using MBDRECVR.

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.

9. Differential stiffness is only supported for standard second-order system


representation. To request differential stiffness, include a static subcase that
contains the stress-stiffening loads. In another subcase include STATSUB = n
where n is the number of the static subcase.

MATLAB Describers:

Describer Meaning

FLEXBODY Requests the generation and writing of standard or state-space


matrices to a MATLAB script file.

NO NX Nastran solution without standard or state-space matrix


generation. (default)

YES Standard or state-space matrix generation requested.

FLEXONLY Determines if DMAP solution runs or not after standard or


state-space matrix generation is complete.

YES Only standard or state-space matrix generation occurs. (default)

NO Standard or state-space matrix generation occurs along with


the standard DMAP solution.

RECVROP2 Requests that the FLEXBODY run output an NX Nastran OP2


file for use in post-processing of controls results. See Remark 7.

NO OP2 file will not be generated. (default)

YES OP2 file will be generated.

CHECK Requests debug output be written to the f06 file when


RECVROP2=YES. See Remark 8.

NO No debug output will be written. (default)


154 MBDEXPORT
Multi-Body Dynamics Export

Describer Meaning

YES 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, 111,
or 112 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). 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/USET1 bulk entries for
partitioned superelements and refer to the SEUSET/SEUSET1 bulk entries for
non-partitioned superelements.

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/USET1 bulk entries for partitioned superelements and refer to the
SEUSET/SEUSET1 bulk entries for non-partitioned superelements.

5. For the state-space option, the MATLAB script file contains the [A], [B], [C], and
[E] state-space matrices. They are defined as AMAT, BMAT, CMAT, and EMAT,
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:
MBDEXPORT 155
Multi-Body Dynamics Export

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.
If differential stiffness is included, the static portion of the results will not be
included in the recovered results when using MBDRECVR.

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.

9. To request differential stiffness, include a static subcase that contains the


stress-stiffening loads. In another subcase include STATSUB = n where n is the
number of the static subcase.
Chapter

9 Glue stiffness output

Glue stiffness output


You can now output the glue stiffness matrix in DMIG format. In your input file
which includes a glue definition, you can request the glue stiffness matrix by
including the following parameter input.
PARAM,KGGLPCH,1

The solver writes the glue stiffness matrix into a PUNCH file in the format required
for DMIG (Direct Matrix Input at Grids). You can request the glue stiffness matrix
in any solution except 144-146, 401, 601 and 701. This option is only available with
the default sparse solver. The iterative solvers do not support this option.

To include the glue stiffness in a consecutive solution:

You include the K2GG case control command to select the DMIG entry.
...
Case Control
k2gg=KGGG
...

You will include the DMIG in the bulk data section of your consecutive input
file. You can optionally use the INCLUDE entry. For example,
...
begin bulk
...
include name_of_dmig_punch_file.pch
...
Chapter

10 RDMODES improvements

RDMODES improvements
Recursive Domain Normal Modes (RDMODES) is a parallel capability that uses
substructuring technology for large scale normal modes analysis.

The RDMODES performance has improved in NX Nastran 9. The improvements


reduce I/O. In one test case of a car body model that contains 384,000 elements,
391,000 grids, and 2,300,000 DOF, the elapsed time is reduced by 50%.

RDMODES can run in either DMP, serial, or SMP configurations. No changes


to the user interface are required to take advantage of the NX Nastran 9
improvements. The DMP, serial, and SMP runs will all benefit.

You activate RDMODES by entering the Nastran keyword nrec on the command
line. To specify the desired parallel functionality, you can also enter the Nastran
keywords dmp or smp. Sample command line entries include:

DMP: NASTRAN nrec = m dmp = p

Serial: NASTRAN nrec = m

SMP: NASTRAN nrec = m smp = p

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

See the Parallel Processing Guide for information on all parallel options.
Chapter

11 Upward compatibility

Updated data blocks

CASECC

Updated Record REPEAT

Word Name Type Description

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

519 SEQDEP CHAR4 Sequence dependency on or off


(SEQDEP)

520 NLCSET I Set Identification nonlinear control


(NLCNTL)

521 GSTRESET I Gauss point stress output set


(GSTRESS)

522 GSTMEDIA I Gauss point stress output media


(GSTRESS)

523 GSTREFMT I Gauss point stress output format


(GSTRESS)

524 GSTRNSET I Gauss point total strain output set


(GSTRAIN)

525 GSNMEDIA I Gauss point total strain output media


(GSTRAIN)

526 GSTRNFMT I Gauss point total strain output


format (GSTRAIN)
162 Updated data blocks

Word Name Type Description

527 ELSTNSET I Nodal elastic strain on elements,


output set (ELSTRN)

528 ELNMEDIA I Nodal elastic strain on elements,


output media (ELSTRN)

529 ELSTNFMT I Nodal elastic strain on elements,


output format (ELSTRN)

530 GELSSET I Gauss point elastic strains on


elements, output set (GELSTRN)

531 GESMEDIA I Gauss point elastic strains on


elements, output media (GELSTRN)

532 GELSFMT I Gauss point elastic strains on


elements, output format (GELSTRN)

533 CRSTSET I Nodal creep strains on elements,


output set (CRSTRN)

534 CRSMEDIA I Nodal creep strains on elements,


output media (CRSTRN)

535 CRSTFMT I Nodal creep strains on elements,


output format (CRSTRN)

536 GCRSSET I Gauss point creep strains on


elements, output set (GCRSTRN)

537 GCRMEDIA I Gauss point creep strains on


elements, output media (GCRSTRN)

538 GCRSFMT I Gauss point creep strains on


elements, output format (GCRSTRN)

539 PLSTSET I Nodal plastic strains on elements,


output set (PLSTRN)

540 PLSMEDIA I Nodal plastic strains on elements,


output media (PLSTRN)
Updated data blocks 163

Word Name Type Description

541 PLSTFMT I Nodal plastic strains on elements,


output format (PLSTRN)

542 GPLSSET I Gauss point plastic strains on


elements, output set (GPLSTRN)

543 GPLMEDIA I Gauss point plastic strains on


elements, output media (GPLSTRN)

544 GPLSFMT I Gauss point plastic strains on


elements, output format (GPLSTRN)

545 THSTSET I Nodal thermal strains on elements,


output set (THSTRN)

546 THSMEDIA I Nodal thermal strains on elements,


output media (THSTRN)

547 THSTFMT I Nodal thermal strains on elements,


output format (THSTRN)

548 GTHSSET I Gauss point thermal strains on


elements, output set (GTHSTRN)

549 GTHMEDIA I Gauss point thermal strains on


elements, output media (GTHSTRN)

550 GTHSFMT I Gauss point thermal strains on


elements, output format (GTHSTRN)

551 OTEMPSET I Temperatures used at solution


points, output set (OTEMP)

552 OTEMEDIA I Temperatures used at solution


points, output media (OTEMP)

553 OTEMPFMT I Temperatures used at solution


points, output format (OTEMP)

554 UNDEF(46) None

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


164 Updated data blocks

DIT

Updated Record TABLED1(1105,11,133)

Word Name Type Description

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

4 FLAG I Extrapolation on/off flag

5 UNDEF(4) None

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

Updated Record TABLED2(1205,12,134)

Word Name Type Description

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

3 FLAG I Extrapolation on/off flag

4 UNDEF(5) None

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

Updated Record TABLED3(1305,13,140)

Word Name Type Description

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

4 FLAG I Extrapolation on/off flag

5 UNDEF(4) None

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

Updated Record TABLEST(1905,19,178)

Word Name Type Description

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


Updated data blocks 165

Word Name Type Description

2 FLAG I Extrapolation on/off flag

3 UNDEF(6) None

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

DSCMCOL

Updated Record Type 1 Responses

Word Name Type Description

RTYPE =19 Equivalent radiated power

4 PANEL I Element identification number

5 FLAG I A subcase ID based code. +:


magnitude; : density

6 SUBCASE I Subcase identification number

7 FREQUENCY RS Frequency

8 UNDEF None

9 SEID I Superelement identification number

DYNAMIC

New Record CBEAR(9010,90,569)

Word Name Type Description

1 EID I Element identification number

2 PID I Property identification number

3 GA I Grid point at end A

4 GB I Grid point at end B


166 Updated data blocks

Word Name Type Description

5 UNDEF(6) None

New Record PBEAR(9110,91,570)

Word Name Type Description

1 PID I Property identification number

2 TYPE1(2) CHAR4 Data type name

4 TXX1 RS/I Real constant XX value or integer table ID


for XX values

5 TXY1 RS/I Real constant XY value or integer table ID


for XY values

6 TYX1 RS/I Real constant YX value or integer table ID


for YX values

7 TYY1 RS/I Real constant YY value or integer table ID


for YY values

8 UNDEF None

9 NOMVAL1 RS Nominal value for displacement or force

10 UNDEF(12) None

22 TYPE2(2) CHAR4 Data type name

24 TXX2 RS/I Real constant XX value or integer table ID


for XX values

25 TXY2 RS/I Real constant XY value or integer table ID


for XY values

26 TYX2 RS/I Real constant YX value or integer table ID


for YX values

27 TYY2 RS/I Real constant YY value or integer table ID


for YY values

28 UNDEF None
Updated data blocks 167

Word Name Type Description

29 NOMVAL2 RS Nominal value for displacement or force

30 UNDEF(11) None

EDOM

Updated Record DRESP1(3806,38,359)

Word Name Type Description

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

FLAG = 19 ERP

5 UNDEF(2) None

7 REGION I Region identifier

8 ATTA I Response attribute

9 ATTB I Frequency or real code for character


input, or -1 = spawn)

10 ATTi I Panel SET3 IDs

Word 10 repeats until -1 occurs

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

EDT

Updated Record BOLT(7108,82,251)


The triplet is changed from BOLT(7108,71,251) to BOLT(7108,82,251) and FLAG =
3 option is added.

Word Name Type Description

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

FLAG = 3
168 Updated data blocks

Word Name Type Description

3 CID I Coordinate system identification number


defining bolt direction

4 IDIR I Direction of bolt axis relative to CID

5 GID I Grid point identification number

6 EID I Element identification number

Word 6 repeats until -1

New Record GROUP(17400,174,616)


Group definition.

Word Name Type Description

1 GID I Group identification number

2 NDESC(C) I Length of group description

3 GDESC(2) CHAR4 Group description

Word 3 repeats NDESC times

NDESC+3 GTYPE I Group type


-2 = Meta data
-3 = Property identification numbers
-4 = Grid identification numbers
-5 = Element identification numbers

GTYPE = -2 Meta data

NDESC+4 NMETA I Length of meta data

NDESC+5 MDESC(2) CHAR4 Meta data

Word NDESC+5 repeats NMETA times

GTYPE = -3 Property identification numbers


Updated data blocks 169

Word Name Type Description

NDESC+5 ID I Property identification numbers


+NMETA > 0 for ID
= 0 for THRU
= -6 for BY
= -7 for ALL

Word NDESC+5+NMETA repeats until -1 occurs

GTYPE = -4 Grid identification numbers

NDESC+5 ID I Property identification numbers


+NMETA > 0 for ID
= 0 for THRU
= -6 for BY
= -7 for ALL

Word NDESC+5+NMETA repeats until -1 occurs

GTYPE = -5 Element identification numbers

NDESC+5 ID I Property identification numbers


+NMETA > 0 for ID
= 0 for THRU
= -6 for BY
= -7 for ALL

Word NDESC+5+NMETA repeats until -1 occurs

Updated Record SET3(4302,43,607)


Definition for set types 1 and 2 are switched.

Word Name Type Description

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

2 TYPE I Set type

1 = element

2 = grid

3 = property
170 Updated data blocks

Word Name Type Description

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

GEOM3

Updated Record BOLTFOR(7002,85,254)


The triplet is changed from BOLTFOR(7002,70,254) to BOLTFOR(7002,85,254).

New Record RFORCE1(17300,173,615)

Word Name Type Description

1 SID I Load set identification number

2 G I Grid point identification number

3 CID I Coordinate system identification number

4 A RS Scale factor of the angular velocity

5 R(3) RS Rectangular components of rotation


vector

8 METHOD I Method used to compute centrifugal


forces

9 RACC RS Scale factor of the angular acceleration

10 MB I Bulk data section with CID definition:


-1=main, 0=partitioned

11 GROUPID I Identification number of the GROUP bulk


entry that specifies the grids to which
this RFORCE1 bulk entry is applied
Updated data blocks 171

GEOM4

Updated Record BLTMPC(12001,120,601)

Word Name Type Description

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

3 GID1 I Grid point identification numbers

4 GID2 I Grid point identification numbers

5 C(3) I Component directions

MPT

New Record MATPLCY(3801,38,970)

Word Name Type Description

1 MID I Material identification number

2 E RS Youngs modulus

3 NU RS Poissons ratio

4 RHO RS Mass density

5 A RS Coefficient of thermal expansion

6 ISO I Identification number of isotropic


hardening rule

7 KIN I Identification number of kinematic


hardening rule

8 RUP I Identification number of rupture


criterion

9 BETA RS Factor used in the stress integration

10 MAXITE I Maximum number of iterations used for


solving the incremental plastic strains
172 Updated data blocks

Word Name Type Description

11 RTOL RS Relative tolerance used to assess


convergence of the iterations

12 UNDEF(5) None

New Record PLCYISO(3901,39,971)

Word Name Type Description

1 HID I Isotropic hardening identification


number

2 HMODEL I Hardening model

HMODEL=1 Bilinear hardening

3 YIELD RS Yield strength

4 EP RS Hardening modulus

5 UNDEF(4) None

HMODEL=2 Multilinear hardening

3 AEPS RS Accumulated effective plastic strain at


data point i

4 SR RS Radius of yield surface corresponding


to aeps(i)

Words 3 and 4 repeat until -1 is reached

HMODEL=3 Exponential hardening

3 YIELD RS Yield strength

4 Q RS Parameter giving the change in yield


stress with respect to accumulated
effective plastic strain

5 B RS Parameter giving the change in yield


stress with respect to accumulated
effective plastic strain
Updated data blocks 173

Word Name Type Description

6 UNDEF(3) None

HMODEL=4 Memory exponential hardening

3 YIELD RS Yield strength

4 Q0 RS Parameter giving the change in yield


stress with respect to accumulated
effective plastic strain

5 QM RS Parameter giving the change in yield


stress with respect to accumulated
effective plastic strain

6 MU RS Parameter giving the change in yield


stress with respect to accumulated
effective plastic strain

7 B RS Parameter giving the change in yield


stress with respect to accumulated
effective plastic strain

8 ETA RS Strain memory surface parameter

New Record PLCYKIN(4001,40,972)

Word Name Type Description

1 HID I Kinematic hardening identification


number

2 TYPE I Type of kinematic hardening, currently


only TYPE=1 (Armstrong-Fredrick/AF)
is allowed

3 H RS Linear kinematic hardening constant


at data point i

4 ZETA RS Nonlinear kinematic hardening


constant at data point i

Words 3 and 4 repeat until -1 is reached


174 Updated data blocks

New Record PLCYRUP(4101,41,973)

Word Name Type Description

1 RID I Rupture criterion identification number

2 TYPE I Type of rupture criterion, currently only


TYPE=1 (Accumulated effective plastic
strain/AEPS) is allowed

3 RSTR RS Accumulated effective plastic strain at


which the material ruptures

4 UNDEF(5) None

New Record TSTEP1(17500,175,618)

Word Name Type Description

1 SID I Set identification number

2 TEND RS End time

3 NINC I Number of load increments

4 NOUT I >0, output at each NOUT; =-1, YES;


=-2, END; =-3, ALL

Words 2 through 4 repeat until (-1,-1,-1) occurs

Updated Record TSTEPNL(3103,31,337)

Word Name Type Description

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

23 KDAMP I Flags to include differential stiffness to


form structural damping

24 KUPDATE I Method for dynamic matrix update

25 KUSTEP I Number of iterations before the stiffness


update
Updated data blocks 175

Word Name Type Description

26 TINTOPT I Time integration method

27 GAMMA RS Amplitude decay factor for 2nd order


transient integration

OEF

Updated Record DATA


Note

CBEAR element forces are added to the OEF data block.

Word Name Type Description

ELTYPE =280 Generalized bearing element (CBEAR)

TCODE,7 =0 or 2 Real or Random Response

2 FX RS Force x

3 FY RS Force y

4 FZ RS Force z

TCODE,7 =1 Real/imaginary or magnitude/phase

2 FXR RS Force x - real/mag. part

3 FYR RS Force y - real/mag. part

4 FZR RS Force z - real/mag. part

5 FXI RS Force x - imag./phase part

6 FYI RS Force y - imag./phase part

7 FZI RS Force z - imag./phase part


176 Updated data blocks

OES

Updated Record IDENT

Word Name Type Description

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

18 EPSTYPE(C) I Designates the type of strain.


0 = Total Strain
1 = Elastic Strain
2 = Thermal Strain

19 UNDEF(32) None

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

Updated Record DATA


Note

ELTYPE = 300 through 307 are added to the OES data block.

ELTYPE =300 HEXA element (CHEXA)

SCODE,6=0 Strain

TCODE,7=0 Real

2 CID I Coordinate System

3 CTYPE CHAR4 Grid or Gaus

4 GRID I Corner grid ID

5 EX RS Strain in X

6 EY RS Strain in Y

7 EZ RS Strain in Z

8 EXY RS Strain in XY

9 EYZ RS Strain in YZ
Updated data blocks 177

10 EZX RS Strain in ZX

11 EVM RS Von Mises strain

Words 4 through 11 repeat 8 times.

SCODE,6=1 Stress

TCODE,7=0 Real

2 CID I Coordinate System

3 CTYPE CHAR4 Grid or Gaus

4 GRID I Corner grid ID

5 EX RS Strain in X

6 EY RS Strain in Y

7 EZ RS Strain in Z

8 EXY RS Strain in XY

9 EYZ RS Strain in YZ

10 EZX RS Strain in ZX

11 EVM RS Von Mises strain

Words 4 through 11 repeat 8 times.

End SCODE,6

ELTYPE =301 PENTA element (CPENTA )

SCODE,6=0 Strain

TCODE,7=0 Real

2 CID I Coordinate System

3 CTYPE CHAR4 Grid or Gaus

4 GRID I Corner grid ID


178 Updated data blocks

5 EX RS Strain in X

6 EY RS Strain in Y

7 EZ RS Strain in Z

8 EXY RS Strain in XY

9 EYZ RS Strain in YZ

10 EZX RS Strain in ZX

11 EVM RS Von Mises strain

Words 4 through 11 repeat 6 times.

SCODE,6=1 Stress

TCODE,7=0 Real

2 CID I Coordinate System

3 CTYPE CHAR4 Grid or Gaus

4 GRID I Corner grid ID

5 EX RS Strain in X

6 EY RS Strain in Y

7 EZ RS Strain in Z

8 EXY RS Strain in XY

9 EYZ RS Strain in YZ

10 EZX RS Strain in ZX

11 EVM RS Von Mises strain

Words 4 through 11 repeat 6 times.

End SCODE,6

ELTYPE =302 TETRA element (CTETRA)


Updated data blocks 179

SCODE,6=0 Strain

TCODE,7=0 Real

2 CID I Coordinate System

3 CTYPE CHAR4 Grid or Gaus

4 GRID I Corner grid ID

5 EX RS Strain in X

6 EY RS Strain in Y

7 EZ RS Strain in Z

8 EXY RS Strain in XY

9 EYZ RS Strain in YZ

10 EZX RS Strain in ZX

11 EVM RS Von Mises strain

Words 4 through 11 repeat 4 times.

SCODE,6=1 Stress

TCODE,7=0 Real

2 CID I Coordinate System

3 CTYPE CHAR4 Grid or Gaus

4 GRID I Corner grid ID

5 EX RS Strain in X

6 EY RS Strain in Y

7 EZ RS Strain in Z

8 EXY RS Strain in XY

9 EYZ RS Strain in YZ
180 Updated data blocks

10 EZX RS Strain in ZX

11 EVM RS Von Mises strain

Words 4 through 11 repeat 4 times.

End SCODE,6

ELTYPE =303 PYRAM element (CPYRAM)

SCODE,6=0 Strain

TCODE,7=0 Real

2 CID I Coordinate System

3 CTYPE CHAR4 Grid or Gaus

4 GRID I Corner grid ID

5 EX RS Strain in X

6 EY RS Strain in Y

7 EZ RS Strain in Z

8 EXY RS Strain in XY

9 EYZ RS Strain in YZ

10 EZX RS Strain in ZX

11 EVM RS Von Mises strain

Words 4 through 11 repeat 5 times.

SCODE,6=1 Stress

TCODE,7=0 Real

2 CID I Coordinate System

3 CTYPE CHAR4 Grid or Gaus

4 GRID I Corner grid ID


Updated data blocks 181

5 EX RS Strain in X

6 EY RS Strain in Y

7 EZ RS Strain in Z

8 EXY RS Strain in XY

9 EYZ RS Strain in YZ

10 EZX RS Strain in ZX

11 EVM RS Von Mises strain

Words 4 through 11 repeat 5 times.

End SCODE,6

ELTYPE =304 Linear composite HEXA element (CHEXAL)

1 I
PLY Lamina number

SCODE,6=0 Strain

2 FLOC CHAR4 Fiber location (BOT, MID, TOP)

3 GRID I Edge grid ID (center=0)

4 EX1 RS Normal strain in the 1-direction

5 EY1 RS Normal strain in the 2-direction

6 ET1 RS Shear strain in the 12-plane

7 EZ1 RS Normal strain in the 3-direction

8 EL1 RS Shear strain in the 13-plane

9 EL2 RS Shear strain in the 23-plane

10 ETMAX1 RS Von Mises strain

For each fiber location requested (PLSLOC), words 3 through 10 repeat 4 times.
182 Updated data blocks

SCODE,6=1 Stress

2 FLOC CHAR4 Fiber location (BOT, MID, TOP)

3 GRID I Edge grid ID (center=0)

4 SX1 RS Normal stress in the 1-direction

5 SY1 RS Normal stress in the 2-direction

6 ST1 RS Shear stress in the 12-plane

7 SZ1 RS Normal stress in the 3-direction

8 SL1 RS Shear stress in the 13-plane

9 SL2 RS Shear stress in the 23-plane

10 STMAX1 RS Von Mises stress

For each fiber location requested (PLSLOC), words 3 through 10 repeat 4 times.

End SCODE,6

ELTYPE =305 Linear composite PENTA element (CPENTAL)

1 I
PLY Lamina number

SCODE,6=0 Strain

2 FLOC CHAR4 Fiber location (BOT, MID, TOP)

3 GRID I Edge grid ID (center=0)

4 EX1 RS Normal strain in the 1-direction

5 EY1 RS Normal strain in the 2-direction

6 ET1 RS Shear strain in the 12-plane

7 EZ1 RS Normal strain in the 3-direction


Updated data blocks 183

8 EL1 RS Shear strain in the 13-plane

9 EL2 RS Shear strain in the 23-plane

10 ETMAX1 RS Von Mises strain

For each fiber location requested (PLSLOC), words 3 through 10 repeat 3 times.

SCODE,6=1 Stress

2 FLOC CHAR4 Fiber location (BOT, MID, TOP)

3 GRID I Edge grid ID (center=0)

4 SX1 RS Normal stress in the 1-direction

5 SY1 RS Normal stress in the 2-direction

6 ST1 RS Shear stress in the 12-plane

7 SZ1 RS Normal stress in the 3-direction

8 SL1 RS Shear stress in the 13-plane

9 SL2 RS Shear stress in the 23-plane

10 STMAX1 RS Von Mises stress

For each fiber location requested (PLSLOC), words 3 through 10 repeat 3 times.

End SCODE,6

ELTYPE =306 Nonlinear composite HEXA element (CHEXALN)

1 I
PLY Lamina number

SCODE,6=0 Strain

2 FLOC CHAR4 Fiber location (BOT, MID, TOP)

3 GRID I Edge grid ID (center=0)

4 EX1 RS Normal strain in the 1-direction


184 Updated data blocks

5 EY1 RS Normal strain in the 2-direction

6 ET1 RS Shear strain in the 12-plane

7 EZ1 RS Normal strain in the 3-direction

8 EL1 RS Shear strain in the 13-plane

9 EL2 RS Shear strain in the 23-plane

10 ETMAX1 RS Von Mises strain

For each fiber location requested (PLSLOC), words 3 through 10 repeat 4 times.

SCODE,6=1 Stress

2 FLOC CHAR4 Fiber location (BOT, MID, TOP)

3 GRID I Edge grid ID (center=0)

4 SX1 RS Normal stress in the 1-direction

5 SY1 RS Normal stress in the 2-direction

6 ST1 RS Shear stress in the 12-plane

7 SZ1 RS Normal stress in the 3-direction

8 SL1 RS Shear stress in the 13-plane

9 SL2 RS Shear stress in the 23-plane

10 STMAX1 RS Von Mises stress

For each fiber location requested (PLSLOC), words 3 through 10 repeat 4 times.

End SCODE,6

ELTYPE =307 Nonlinear composite PENTA element (CPENTALN)

1 I
PLY Lamina number
Updated data blocks 185

SCODE,6=0 Strain

2 FLOC CHAR4 Fiber location (BOT, MID, TOP)

3 GRID I Edge grid ID (center=0)

4 EX1 RS Normal strain in the 1-direction

5 EY1 RS Normal strain in the 2-direction

6 ET1 RS Shear strain in the 12-plane

7 EZ1 RS Normal strain in the 3-direction

8 EL1 RS Shear strain in the 13-plane

9 EL2 RS Shear strain in the 23-plane

10 ETMAX1 RS Von Mises strain

For each fiber location requested (PLSLOC), words 3 through 10 repeat 3 times.

SCODE,6=1 Stress

2 FLOC CHAR4 Fiber location (BOT, MID, TOP)

3 GRID I Edge grid ID (center=0)

4 SX1 RS Normal stress in the 1-direction

5 SY1 RS Normal stress in the 2-direction

6 ST1 RS Shear stress in the 12-plane

7 SZ1 RS Normal stress in the 3-direction

8 SL1 RS Shear stress in the 13-plane

9 SL2 RS Shear stress in the 23-plane

10 STMAX1 RS Von Mises stress

For each fiber location requested (PLSLOC), words 3 through 10 repeat 3 times.

End SCODE,6
186 Updated data blocks

R1TAB

Updated Record Repeat

Word Name Type Description

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

TYPE =19 ERP

8 COMP I Subcase ID + 100

9 UNDEF None

10 SET3 I Panel SET3 identification number

11 FREQ RS Frequency

12 UNDEF None

New data blocks

OESXRMS
Table of element RMS stresses for random analysis that includes von Mises stress
output.

For all analysis types (real and complex) and SORT1 and SORT2 formats.

Record HEADER

Word Name Type Description

1 NAME(2) CHAR4 Data block Name

3 WORD I No Def or Month, Year, One, One

Word 3 repeats until End of Record


New data blocks 187

Record IDENT

Word Name Type Description

1 ACODE(C) I Device code + 10*Approach Code

2 TCODE(C) I Table Code

3 ELTYPE(C) I Element Type

4 RANDID I Random identification number

TCODE,1 = 1 Sort 1

ACODE,4 = 05 Frequency

5 FREQ RS Frequency

6 UNDEF None

7 RANDOM ID I Random identification number

End ACODE,4

TCODE,1 = 02 Sort 2

5 LSDVMN I Frequency step

6 UNDEF(2) None

End TCODE,1

8 LOADSET I Random code ID

9 FCODE I Format Code

10 NUMWDE(C) I Number of words per entry in DATA


record

11 SCODE I Stress code

12 PID (SOL 601 I Physical Property ID for SOL 601 &


and 701 only) 701 only. UNDEF for all other SOLs
188 New data blocks

Word Name Type Description

13 ELRESCS I Coordinate system in which stresses


are written. Applicable to SOL
601/701, solid elements only.

0 = in element coordinate system


(default)

1 = stresses are written according


to CORDM

14 Q4CSTR(C) I Corner Stress Flag

15 PLSLOC(C) I Ply stress location

16 CSOPT I Plane flag for axisymmetric and


plane stress/strain elements

17 RMSSF RS RMS scale factor.

18 VMFLAG I RMS von Mises presence flag (=1 if


present)

19 UNDEF(32) None

51 TITLE(32) CHAR4 Title

83 SUBTITL(32) CHAR4 Subtitle

115 LABEL(32) CHAR4 Label

Record DATA

Word Name Type Description

SORTCODE=1 Sort 1 - SortCode=((TCODE/1000)+2)/2

TCODE,1 =1

1 EKEY I Device code + 10*Point identification


number

TCODE,1 =02 Sort 2


New data blocks 189

Word Name Type Description

ACODE/10=01 Analysis type

ACODE,4 =05

1 FREQ RS Frequency

End ACODE,4

End ACODE/10

Word Name Type Description

ELTYPE =00 Grid - OES1G table

2 UNDEF none

ELTYPE =01 Rod element (CROD)

TCODE,7 =1 Real / Imaginary

2 ASR RS Axial Stress

3 ASI RS Axial Stress

4 TSR RS Torsional Stress

5 TSI RS Torsional Stress

TCODE,7 =2 Real

2 AS RS Axial Stress

3 TS RS Torsional Stress

End TCODE,7

ELTYPE =02 Beam element (CBEAM)

TCODE,7=1 Real/Imaginary

2 GRID I External Grid Point identification


number
190 New data blocks

Word Name Type Description

3 SD RS Station Distance/Length

4 SRCR RS Long. Stress at Point C

5 SXDR RS Long. Stress at Point D

6 SXER RS Long. Stress at Point E

7 SXFR RS Long. Stress at Point F

8 SXCI RS Long. Stress at Point C

9 SXDI RS Long. Stress at Point D

10 SXEI RS Long. Stress at Point E

11 SXFI RS Long. Stress at Point F

Words 2 through 11 repeat 011 times

TCODE,7 =2 Real

2 GRID I External Grid Point identification


number

3 SD RS Station Distance/Length

4 SXC RS Long. Stress at Point C

5 SXD RS Long. Stress at Point D

6 SXE RS Long. Stress at Point E

7 SXF RS Long. Stress at Point F

Words 2 through 7 repeat 011 times

End
TCODE,7

ELTYPE=03 Tube element (CTUBE)

TCODE,7 =1 Real / Imaginary


New data blocks 191

Word Name Type Description

2 ASR RS Axial Stress

3 ASI RS Axial Stress

4 TSR RS Torsional Stress

5 TSI RS Torsional Stress

TCODE,7 =2 Real

2 AS RS Axial Stress

3 TS RS Torsional Stress

End TCODE,7

ELTYPE =04 Shear panel element (CSHEAR)

TCODE,7 =1 Real / Imaginary

2 TMAXR RS Maximum Shear

3 TMAXI RS Maximum Shear

4 TAVGR RS Average Shear

5 TAVGI RS Average Shear

TCODE,7 =2 Real

2 TMAX RS Maximum Shear

3 TAVG RS Average Shear

End TCODE,7

ELTYPE =05 FORCE1/FORCE2/MOMENT1/MOMENT2


(follower stiffness)

2 UNDEF None

ELTYPE =06 Unused

2 UNDEF None
192 New data blocks

Word Name Type Description

ELTYPE =07 PLOAD4 (follower stiffness)

2 UNDEF None

ELTYPE =08 PLOADX1 (follower stiffness)

2 UNDEF None

ELTYPE =09 PLOAD and PLOAD2 (follower stiffness)

2 UNDEF None

Word Name Type Description

ELTYPE =10 Rod element connection and property (CONROD)

TCODE,7 =1 Real / Imaginary

2 ASR RS Axial Stress

3 ASI RS Axial Stress

4 TSR RS Torsional Stress

5 TSI RS Torsional Stress

TCODE,7 =2 Real

2 AS RS Axial Stress

3 TS RS Torsional Stress

End TCODE,7

ELTYPE =11 Scalar spring element (CELAS1)

TCODE,7 =0 Real

2 S RS Stress

TCODE,7 =1 Real / Imaginary

2 SR RS Stress
New data blocks 193

Word Name Type Description

3 SI RS Stress

End TCODE,7

ELTYPE =12 Scalar spring element with properties (CELAS2)

TCODE,7 =2 Real

2 S RS Stress

TCODE,7 =1 Real/Imaginary

2 SR RS Stress

3 SI RS Stress

End TCODE,7

ELTYPE =13 Scalar spring element to scalar points only


(CELAS3)

TCODE,7 =2 Real

2 S RS Stress

TCODE,7 =1

2 SR RS Stress

3 SI RS Stress

End TCODE,7

ELTYPE =14 Scalar spring element to scalar points only with


properties (CELAS4)

2 UNDEF None

ELTYPE =15 AEROT3

2 UNDEF None

ELTYPE =16 AEROBEAM


194 New data blocks

Word Name Type Description

2 UNDEF None

ELTYPE =17 Unused (pre-V69 TRIA2 Same as TRIA1)

2 UNDEF None

ELTYPE =18 Unused (pre-V69 QUAD2 Same as TRIA1)

2 UNDEF None

ELTYPE =19 Unused (pre-V69 QUAD1 Same as TRIA1)

2 UNDEF None

Word Name Type Description

ELTYPE =20 Scalar damper (CDAMP1)

2 UNDEF None

ELTYPE =21 Scalar damper with properties (CDAMP2)

2 UNDEF None

ELTYPE =22 Scalar damper to scalar points only (CDAMP3)

2 UNDEF None

ELTYPE =23 Scalar damper to scalar points only with properties


(CDAMP4)

2 UNDEF None

ELTYPE =24 Viscous damper (CVISC)

TCODE,7 =1 Real / Imaginary

2 ASR RS Axial Stress

3 ASI RS Axial Stress

4 TAUR RS Torque
New data blocks 195

Word Name Type Description

5 TAUI RS Torque

TCODE,7 =2 Real

2 AS RS Axial Stress

3 TAU RS Torque

End TCODE,7

ELTYPE =25 Scalar mass (CMASS1)

2 UNDEF None

ELTYPE =26 Scalar mass with properties (CMASS2)

2 UNDEF None

ELTYPE =27 Scalar mass to scalar points only (CMASS3)

2 UNDEF None

ELTYPE =28 Scalar mass to scalar pts. only with properties


(CMASS4)

2 UNDEF None

ELTYPE =29 Concentrated mass element - general form (CONM1)

2 UNDEF None

Word Name Type Description

ELTYPE =30 Concentrated mass element - rigid body form


(CONM2)

2 UNDEF None

ELTYPE =31 Dummy plot element (PLOTEL)

2 UNDEF None

ELTYPE =32 Unused


196 New data blocks

Word Name Type Description

2 UNDEF None

ELTYPE =33 Quadrilateral plate element (CQUAD4)

TCODE,7 =1 Real / Imaginary

2 FD1 RS Z1 = Fibre Distance

3 SX1R RS Normal in x at Z1

4 SX1I RS Normal in x at Z1

5 SY1R RS Normal in y at Z1

6 SY1I RS Normal in y at Z1

7 TXY1R RS Shear in xy at Z1

8 TXY1I RS Shear in xy at Z1

9 RMSVM1R RS RMS von Mises at Z1

10 RMSVM1I RS RMS von Mises at Z1

11 FD2 RS Z2 = Fibre Distance

12 SX2R RS Normal in x at Z2

13 SX2I RS Normal in x at Z2

14 SY2R RS Normal in y at Z2

15 SY2I RS Normal in y at Z2

16 TXY2R RS Shear in xy at Z2

17 TXY2I RS Shear in xy at Z2

18 RMSVM2R RS RMS von Mises at Z2

19 RMSVM2I RS RMS von Mises at Z2

TCODE,7 =2 Real
New data blocks 197

Word Name Type Description

2 FD1 RS Z1 = Fibre Distance

3 SX1 RS Normal in x at Z1

4 SY1 RS Normal in y at Z1

5 TXY1 RS Shear in xy at Z1

6 RMSVM1 RS RMS von Mises at Z1

7 FD2 RS Z2 = Fibre Distance

8 SX2 RS Normal in x at Z2

9 SY2 RS Normal in y at Z2

10 TXY2 RS Shear in xy at Z2

11 RMSVM2 RS RMS von Mises at Z2

End TCODE,7

ELTYPE =34 Simple beam element (CBAR and see also


ELTYPE=100)

TCODE,7 =1 Real / Imaginary

2 SX1AR RS SA1

3 SX2AR RS SA2

4 SX3AR RS SA3

5 SX4AR RS SA4

6 ASR RS Axial

7 SX1AI RS SA1

8 SX2AI RS SA2

9 SX3AI RS SA3

10 SX4AI RS SA4
198 New data blocks

Word Name Type Description

11 ASI RS Axial

12 SX1BR RS SB1

13 SX2BR RS SB2

14 SX3BR RS SB3

15 SX4BR RS SB4

16 SX1BI RS SB1

17 SX2BI RS SB2

18 SX3BI RS SB3

19 SX4BI RS SB4

TCODE,7 =2 Real

2 SX1A RS SA1

3 SX2A RS SA2

4 SX3A RS SA3

5 SX4A RS SA4

6 AS RS Axial

7 SX1B RS SB1

8 SX2B RS SB2

9 SX3B RS SB3

10 SX4B RS SB4

End TCODE,7

ELTYPE =35 Axisymmetric shell element (CCONEAX)

2 UNDEF None
New data blocks 199

Word Name Type Description

ELTYPE =36 Unused (Pre-V69 CTRIARG)

2 UNDEF None

ELTYPE =37 Unused (Pre-V69 CTRAPRG)

2 UNDEF None

ELTYPE =38 Gap element (CGAP)

2 UNDEF None

ELTYPE =39 Tetra

TCODE,7 =1 Real / Imaginary

2 CID I Stress Coordinate System

3 CTYPE CHAR4 Coordinate System Type (BCD)

4 NODEF I Number of Active Points

5 GRID I External grid identification number


(0=center)

6 SXR RS Normal in x

7 SYR RS Normal in y

8 SZR RS Normal in z

9 TXYR RS Shear in xy

10 TYZR RS Shear in yz

11 TZXR RS Shear in zx

12 RMSVMR RS RMS von Mises

13 SXI RS Normal in x

14 SYI RS Normal in y

15 SZI RS Normal in z
200 New data blocks

Word Name Type Description

16 TXYI RS Shear in xy

17 TYZI RS Shear in yz

18 TZXI RS Shear in zx

19 RMSVMI RS RMS von Mises

Words 5 through 19 repeat 005 times

TCODE,7 =2 Real

2 CID I Stress Coordinate System

3 CTYPE CHAR4 Coordinate System Type (BCD)

4 NODEF I Number of Active Points

5 GRID I External grid identification number


(0=center)

6 SX RS Normal in x

7 SY RS Normal in y

8 SZ RS Normal in z

9 TXY RS Shear in xy

10 TYZ RS Shear in yz

11 TZX RS Shear in zx

12 RMSVM RS RMS von Mises

Words 5 through 12 repeat 005 times

End TCODE,7

Word Name Type Description

ELTYPE =40 Rod type spring and damper (CBUSH1D)


New data blocks 201

Word Name Type Description

TCODE,7 =1 Real / Imaginary

2 FER RS Element Force

3 UER RS Axial Displacement

4 ASR RS Axial Stress*

5 AER RS Axial Strain*

6 FEI RS Element Force

7 UEI RS Axial Displacement

8 ASI RS Axial Stress*

9 AEI RS Axial Strain*

TCODE,7 =2 Real

2 FE RS Element Force

3 UE RS Axial Displacement

4 AS RS Axial Stress*

5 AE RS Axial Strain*

End TCODE,7

ELTYPE =41 Unused (Pre-V69 CHEXA1)

2 UNDEF None

ELTYPE =42 Unused (Pre-V69 CHEXA2)

2 UNDEF None

ELTYPE =43 Fluid element with 2 points (CFLUID2)

2 UNDEF None

ELTYPE =44 Fluid element with 3 points (CFLUID3)


202 New data blocks

Word Name Type Description

2 UNDEF None

ELTYPE =45 Fluid element with 4 points (CFLUID4)

2 UNDEF None

ELTYPE =46 Cflmass

2 UNDEF None

ELTYPE =47 Fluid element with 2 points (CAXIF2)

TCODE,7 =2 Real

2 RA RS Radial Axis

3 AA RS Axial Axis

4 TE RS Tangential Edge

5 CE RS Circumferential Edge

TCODE,7 =1 Real / Imaginary

2 RAR RS Radial Axis

3 AAR RS Axial Axis

4 TER RS Tangential Edge

5 CER RS Circumferential Edge

6 RAI RS Radial Axis

7 AAI RS Axial Axis

8 TEI RS Tangential Edge

9 CEI RS Circumferential Edge

End TCODE,7

ELTYPE =48 Fluid element with 3 points (CAXIF3)


New data blocks 203

Word Name Type Description

TCODE,7 =2 Real

2 RC RS Radial centroid

3 CC RS Circumferential centroid

4 AC RS Axial centroid

5 TE1 RS Tangential edge 1

6 CE1 RS Circumferential edge 1

7 TE2 RS Tangential edge 2

8 CE2 RS Circumferential edge 2

9 TE3 RS Tangential edge 3

10 CE3 RS Circumferential edge 3

TCODE,7 =1 Real / Imaginary

2 RCR RS Radial centroid

3 CCR RS Circumferential centroid

4 ACR RS Axial centroid

5 TE1R RS Tangential edge 1

6 CE1R RS Circumferential edge 1

7 TE2R RS Tangential edge 2

8 CE2R RS Circumferential edge 2

9 TE3R RS Tangential edge 3

10 CE3R RS Circumferential edge 3

11 RCI RS Radial centroid

12 CCI RS Circumferential centroid


204 New data blocks

Word Name Type Description

13 ACR RS Axial centroid

14 TE1I RS Tangential edge 1

15 CE1I RS Circumferential edge 1

16 TE2I RS Tangential edge 2

17 CE2I RS Circumferential edge 2

18 TE3I RS Tangential edge 3

19 CE3I RS Circumferential edge 3

End TCODE,7

ELTYPE =49 Fluid element with 4 points (CAXIF4)

TCODE,7 =2 Real

2 RC RS Radial centroid

3 CC RS Circumferential centroid

4 AC RS Axial centroid

5 TE1 RS Tangential edge 1

6 CE1 RS Circumferential edge 1

7 TE2 RS Tangential edge 2

8 CE2 RS Circumferential edge 2

9 TE3 RS Tangential edge 3

10 CE3 RS Circumferential edge 3

11 TE4 RS Tangential edge 4

12 CE4 RS Circumferential edge 4

TCODE,7 =1 Real / Imaginary


New data blocks 205

Word Name Type Description

2 RCR RS Radial centroid

3 CCR RS Circumferential centroid

4 ACR RS Axial centroid

5 TE1R RS Tangential edge 1

6 CE1R RS Circumferential edge 1

7 TE2R RS Tangential edge 2

8 CE2R RS Circumferential edge 2

9 TE3R RS Tangential edge 3

10 CE3R RS Circumferential edge 3

11 TE4R RS Tangential edge 4

12 CE4R RS Circumferential edge 4

13 RCI RS Radial centroid

14 CCI RS Circumferential centroid

15 ACR RS Axial centroid

16 TE1I RS Tangential edge 1

17 CE1I RS Circumferential edge 1

18 TE2I RS Tangential edge 2

19 CE2I RS Circumferential edge 2

20 TE3I RS Tangential edge 3

21 CE3I RS Circumferential edge 3

22 TE4I RS Tangential edge 4

23 CE4I RS Circumferential edge 4

End TCODE,7
206 New data blocks

Word Name Type Description

ELTYPE =50 Three-point slot element (CSLOT3)

TCODE,7 =2 Real

2 RC RS Radial centroid

3 AC RS Axial centroid

4 TE1 RS Tangential edge 1

5 TE2 RS Tangential edge 2

6 TE3 RS Tangential edge 3

TCODE,7 =1 Real / Imaginary

2 RCR RS Radial centroid

3 ACR RS Axial centroid

4 TE1R RS Tangential edge 1

5 TE2R RS Tangential edge 2

6 TE3R RS Tangential edge 3

7 RCI RS Radial centroid

8 ACI RS Axial centroid

9 TE1I RS Tangential edge 1

10 TE2I RS Tangential edge 2

11 TE3I RS Tangential edge 3

End TCODE,7

ELTYPE =51 Four-point slot element (CSLOT4)

TCODE,7 =2 Real

2 RC RS Radial centroid
New data blocks 207

Word Name Type Description

3 AC RS Axial centroid

4 TE1 RS Tangential edge 1

5 TE2 RS Tangential edge 2

6 TE3 RS Tangential edge 3

7 TE4 RS Tangential edge 4

TCODE,7 =1 Real / Imaginary

2 RCR RS Radial centroid

3 ACR RS Axial centroid

4 TE1R RS Tangential edge 1

5 TE2R RS Tangential edge 2

6 TE3R RS Tangential edge 3

7 TE4R RS Tangential edge 4

8 RCI RS Radial centroid

9 ACI RS Axial centroid

10 TE1I RS Tangential edge 1

11 TE2I RS Tangential edge 2

12 TE3I RS Tangential edge 3

13 TE4I RS Tangential edge 4

End TCODE,7

ELTYPE =52 Heat transfer plot element for CHBDYG and


CHBDYP

2 UNDEF None

ELTYPE =53 Axisymmetric triangular element (CTRIAX6)


208 New data blocks

Word Name Type Description

TCODE,7 =1 Real / Imaginary

2 LOC I Location Code

3 SXR RS Normal stress in X real part

4 SXI RS Normal stress in X imaginary part

5 SYR RS Normal stress in Y real part

6 SYI RS Normal stress in Y imaginary part

7 SZR RS Normal stress in Z real part

8 SZI RS Normal stress in Z imaginary part

9 SPR RS In-plane shear stress real part

10 SPI RS In-plane shear stress imaginary part

11 RMSVMR RS RMS von Mises

12 RMSVMI RS RMS von Mises

Words 2 through 12 repeat 004 times

TCODE,7 =2 Real

2 LOC I Location Code

3 SX RS Normal stress in X

4 SY RS Normal stress in Y

5 SZ RS Normal stress in Z

6 SP RS In-plane shear stress

7 MAXP RS Maximum Principal

8 TMAX RS Maximum Shear

9 OCTS RS Octahedral
New data blocks 209

Word Name Type Description

10 RMSVM RS RMS von Mises

Words 2 through 10 repeat 004 times

End TCODE,7

ELTYPE =54 Unused (Pre-V69 CTRIM6)

2 UNDEF None

ELTYPE =55 Three-point dummy element (CDUM3)

TCODE,7 =2 Real

2 S(9) RS User defined

TCODE,7 =1 Real/imaginary or magnitude/phase

2 SR(9) RS User defined - real/mag.

11 SI(9) RS User defined - mag./phase

End TCODE,7

ELTYPE =56 Four-point dummy element (CDUM4)

TCODE,7 =2 Real

2 S(9) RS User defined

TCODE,7 =1 Real/imaginary or magnitude/phase

2 SR(9) RS User defined - real/mag.

11 SI(9) RS User defined - mag./phase

End TCODE,7

ELTYPE =57 Five-point dummy element (CDUM5)

TCODE,7 =2 Real

2 S(9) RS User defined


210 New data blocks

Word Name Type Description

TCODE,7 =1 Real/imaginary or magnitude/phase

2 SR(9) RS User defined - real/mag.

11 SI(9) RS User defined - mag./phase

End TCODE,7

ELTYPE =58 Six-point dummy element (CDUM6)

TCODE,7 =2 Real

2 S(9) RS User defined

TCODE,7 =1 Real/imaginary or magnitude/phase

2 SR(9) RS User defined - real/mag.

11 SI(9) RS User defined - mag./phase

End TCODE,7

ELTYPE =59 Seven-point dummy element (CDUM7)

TCODE,7 =2 Real

2 S(9) RS User defined

TCODE,7 =1 Real/imaginary or magnitude/phase

2 SR(9) RS User defined - real/mag.

11 SI(9) RS User defined - mag./phase

End TCODE,7

Word Name Type Description

ELTYPE =60 Two-dimensional crack tip element (CRAC2D or


CDUM8)

2 UNDEF none
New data blocks 211

Word Name Type Description

ELTYPE =61 Three-dimensional crack tip element (CRAC3D or


CDUM9)

2 UNDEF none

ELTYPE =62 Unused (Pre-V69 CQDMEM1)

2 UNDEF None

ELTYPE =63 Unused (Pre-V69 CQDMEM2)

2 UNDEF None

ELTYPE =64 Curved quadrilateral shell element (CQUAD8)

TCODE,7 =1 Real / Imaginary

2 TERM CHAR4

3 GRID I Number active grids identification


numbers or grid identification number

4 FD1 RS Fiber distance at Z1

5 SX1R RS Normal in x at Z1

6 SX1I RS Normal in x at Z1

7 SY1R RS Normal in y at Z1

8 SY1I RS Normal in y at Z1

9 TXY1R RS Shear in xy at Z1

10 TXY1I RS Shear in xy at Z1

11 RMSVM1R RS RMS von Mises at Z1

12 RMSVM1I RS RMS von Mises at Z1

13 FD2 RS Fiber distance at Z2

14 SX2R RS Normal in x at Z2
212 New data blocks

Word Name Type Description

15 SX2I RS Normal in x at Z2

16 SY2R RS Normal in y at Z2

17 SY2I RS Normal in y at Z2

18 TXY2R RS Shear in xy at Z2

19 TXY2I RS Shear in xy at Z2

20 RMSVM2R RS RMS von Mises at Z2

21 RMSVM2I RS RMS von Mises at Z2

Words 3 through 21 repeat 005 times

TCODE,7 =2 Real

2 TERM CHAR4 "CENTER"

3 GRID I Number active grids identification


number or grid identification number

4 FD1 RS Fiber distance at Z1

5 EX1 RS Normal in x at Z1

6 EY1 RS Normal in y at Z1

7 ETXY1 RS Shear in xy at Z1

8 RMSVM1 RS RMS von Mises at Z1

9 FD2 RS Fiber distance at Z2

10 EX2 RS Normal in x at Z2

11 EY2 RS Normal in y at Z2

12 ETXY2 RS Shear in xy at Z2

13 RMSVM2 RS RMS von Mises at Z2

Words 3 through 13 repeat 005 times


New data blocks 213

Word Name Type Description

End TCODE,7

ELTYPE =65 Unused (Pre-V69 CHEX8)

2 UNDEF None

ELTYPE =66 Unused (Pre-V69 CHEX20)

2 UNDEF None

ELTYPE =67 Hexa

TCODE,7 =1 Real / Imaginary

2 CID I Stress Coordinate System

3 CTYPE CHAR4 Coordinate System Type (BCD)

4 NODEF I Number of Active Points

5 GRID I External grid identification number


(0=center)

6 SXR RS Normal in x

7 SYR RS Normal in y

8 SZR RS Normal in z

9 TXYR RS Shear in xy

10 TYZR RS Shear in yz

11 TZXR RS Shear in zx

12 RMSVMR RS RMS von Mises

13 SXI RS Normal in x

14 SYI RS Normal in y

15 SZI RS Normal in z

16 TXYI RS Shear in xy
214 New data blocks

Word Name Type Description

17 TYZI RS Shear in yz

18 TZXI RS Shear in zx

19 RMSVMI RS RMS von Mises

Words 5 through 19 repeat 009 times

TCODE,7 =2 Real

2 CID I Stress Coordinate System

3 CTYPE CHAR4 Coordinate System Type (BCD)

4 NODEF I Number of Active Points

5 GRID I External grid identification number


(0=center)

6 SX RS Normal in x

7 SY RS Normal in y

8 SZ RS Normal in z

9 TXY RS Shear in xy

10 TYZ RS Shear in yz

11 TZX RS Shear in zx

12 RMSVM RS RMS von Mises

Words 5 through 12 repeat 009 times

End TCODE,7

ELTYPE =68 Penta

TCODE,7 =1 Real / Imaginary

2 CID I Stress Coordinate System

3 CTYPE CHAR4 Coordinate System Type (BCD)


New data blocks 215

Word Name Type Description

4 NODEF I Number of Active Points

5 GRID I External grid identification number


(0=center)

6 SXR RS Normal in x

7 SYR RS Normal in y

8 SZR RS Normal in z

9 TXYR RS Shear in xy

10 TYZR RS Shear in yz

11 TZXR RS Shear in zx

12 RMSVMR RS RMS von Mises

13 SXI RS Normal in x

14 SYI RS Normal in y

15 SZI RS Normal in z

16 TXYI RS Shear in xy

17 TYZI RS Shear in yz

18 TZXI RS Shear in zx

19 RMSVMI RS RMS von Mises

Words 5 through 19 repeat 007 times

TCODE,7 =2 Real

2 CID I Stress Coordinate System

3 CTYPE CHAR4 Coordinate System Type (BCD)

4 NODEF I Number of Active Points


216 New data blocks

Word Name Type Description

5 GRID I External grid identification number


(0=center)

6 SX RS Normal in x

7 SY RS Normal in y

8 SZ RS Normal in z

9 TXY RS Shear in xy

10 TYZ RS Shear in yz

11 TZX RS Shear in zx

12 RMSVM RS RMS von Mises

Words 5 through 12 repeat 007 times

End TCODE,7

ELTYPE =69 Curved beam or pipe element (CBEND)

TCODE,7 =1 Real / Imaginary

2 GRID I External Grid Point identification


number

3 CA RS Circumferential Angle

4 SCR RS Long. Stress at Point C

5 SDR RS Long. Stress at Point D

6 SER RS Long. Stress at Point E

7 SFR RS Long. Stress at Point F

8 SCI RS Long. Stress at Point C

9 SDI RS Long. Stress at Point D

10 SEI RS Long. Stress at Point E


New data blocks 217

Word Name Type Description

11 SFI RS Long. Stress at Point F

Words 2 through 11 repeat 002 times

TCODE,7 =2 Real

2 GRID I External Grid Point identification


number

3 CA RS Circumferential Angle

4 SC RS Long. Stress at Point C

5 SD RS Long. Stress at Point D

6 SE RS Long. Stress at Point E

7 SF RS Long. Stress at Point F

Words 2 through 7 repeat 002 times

End TCODE,7

Word Name Type Description

ELTYPE =70 Triangular plate element (CTRIAR)

TCODE,7 =1 Real / Imaginary

2 TERM CHAR4

3 GRID I Number active grids identification


number or grid identification number

4 FD1 RS Fiber distance at Z1

5 SX1R RS Normal in x at Z1

6 SX1I RS Normal in x at Z1

7 SY1R RS Normal in y at Z1

8 SY1I RS Normal in y at Z1
218 New data blocks

Word Name Type Description

9 TXY1R RS Shear in xy at Z1

10 TXY1I RS Shear in xy at Z1

11 FD2 RS Fiber distance at Z2

12 RMSVM1R RS RMS von Mises at Z1

13 RMSVM1I RS RMS von Mises at Z1

14 SX2R RS Normal in x at Z2

15 SX2I RS Normal in x at Z2

16 SY2R RS Normal in y at Z2

17 SY2I RS Normal in y at Z2

18 TXY2R RS Shear in xy at Z2

19 TXY2I RS Shear in xy at Z2

20 RMSVM2R RS RMS von Mises at Z2

21 RMSVM2I RS RMS von Mises at Z2

Words 3 through 21 repeat 004 times

TCODE,7 =2 Real

2 TERM CHAR4

3 GRID I Number active grids identification


number or grid identification number

4 FD1 RS Fiber distance at Z1

5 SX1 RS Normal in x at Z1

6 SY1 RS Normal in y at Z1

7 TXY1 RS Shear in xy at Z1
New data blocks 219

Word Name Type Description

8 RMSVM1 RS RMS von Mises at Z1

9 FD2 RS Fiber distance at Z2

10 SX2 RS Normal in x at Z2

11 SY2 RS Normal in y at Z2

12 TXY2 RS Shear in xy at Z2

13 RMSVM2 RS RMS von Mises at Z2

Words 3 through 13 repeat 004 times

End TCODE,7

ELTYPE =71 Unused

2 UNDEF None

ELTYPE =72 AEROQ4

2 UNDEF None

ELTYPE =73 Unused (Pre-V69 CFTUBE)

2 UNDEF None

ELTYPE =74 Triangular shell element (CTRIA3)

TCODE,7 =1 Real / Imaginary

2 FD1 RS Z1 = Fibre Distance

3 SX1R RS Normal in x at Z1

4 SX1I RS Normal in x at Z1

5 SY1R RS Normal in y at Z1

6 SY1I RS Normal in y at Z1

7 TXY1R RS Shear in xy at Z1
220 New data blocks

Word Name Type Description

8 TXY1I RS Shear in xy at Z1

9 RMSVM1R RS RMS von Mises at Z1

10 RMSVM1I RS RMS von Mises at Z1

11 FD2 RS Z2 = Fibre Distance

12 SX2R RS Normal in x at Z2

13 SX2I RS Normal in x at Z2

14 SY2R RS Normal in y at Z2

15 SY2I RS Normal in y at Z2

16 TXY2R RS Shear in xy at Z2

17 TXY2I RS Shear in xy at Z2

18 RMSVM2R RS RMS von Mises at Z2

19 RMSVM2I RS RMS von Mises at Z2

TCODE,7 =2 Real

2 FD1 RS Z1 = Fibre Distance

3 SX1 RS Normal in x at Z1

4 SY1 RS Normal in y at Z1

5 TXY1 RS Shear in xy at Z1

6 RMSVM1 RS RMS von Mises at Z1

7 FD2 RS Z2 = Fibre Distance

8 SX2 RS Normal in x at Z2

9 SY2 RS Normal in y at Z2

10 TXY2 RS Shear in xy at Z2
New data blocks 221

Word Name Type Description

11 RMSVM2 RS RMS von Mises at Z2

End TCODE,7

ELTYPE =75 Curved triangular shell element (CTRIA6)

TCODE,7 =1 Real / Imaginary

2 TERM CHAR4

3 GRID I Number active grids identification


number or grid identification number

4 FD1 RS Fiber distance at Z1

5 SX1R RS Normal in x at Z1

6 SX1I RS Normal in x at Z1

7 SY1R RS Normal in y at Z1

8 SY1I RS Normal in y at Z1

9 TXY1R RS Shear in xy at Z1

10 TXY1I RS Shear in xy at Z1

11 RMSVM1R RS RMS von Mises at Z1

12 RMSVM1I RS RMS von Mises at Z1

13 FD2 RS Fiber distance at Z2

14 SX2R RS Normal in x at Z2

15 SX2I RS Normal in x at Z2

16 SY2R RS Normal in y at Z2

17 SY2I RS Normal in y at Z2

18 TXY2R RS Shear in xy at Z2

19 TXY2I RS Shear in xy at Z2
222 New data blocks

Word Name Type Description

20 RMSVM2R RS RMS von Mises at Z2

21 RMSVM2I RS RMS von Mises at Z2

Words 3 through 21 repeat 004 times

TCODE,7 =2 Real

2 TERM CHAR4

3 GRID I Number active grids identification


number or grid identification number

4 FD1 RS Fiber distance at Z1

5 SX1 RS Normal in x at Z1

6 SY1 RS Normal in y at Z1

7 TXY1 RS Shear in xy at Z1

8 RMSVM1 RS RMS von Mises at Z1

9 FD2 RS Fiber distance at Z2

10 SX2 RS Normal in x at Z2

11 SY2 RS Normal in y at Z2

12 TXY2 RS Shear in xy at Z2

13 RMSVM2 RS RMS von Mises at Z2

Words 3 through 13 repeat 004 times

End TCODE,7

ELTYPE =76 Acoustic velocity/pressures in six-sided solid


element (CHEXA)

2 UNDEF None

ELTYPE =77 Acoustic velocity/pressures in five-sided solid


element (CPENTA)
New data blocks 223

Word Name Type Description

2 UNDEF None

ELTYPE =78 Acoustic velocity/pressures in four-sided solid


element (CTETRA)

2 UNDEF None

ELTYPE =79 Undef

2 UNDEF None

Word Name Type Description

ELTYPE =80 Undef

2 UNDEF None

ELTYPE =81 Undef

2 UNDEF None

ELTYPE =82 Quadrilateral plate element (CQUADR)

TCODE,7 =1 Real / Imaginary

2 TERM CHAR4

3 GRID I Number active grids identification


number or grid identification number

4 FD1 RS Fiber distance at Z1

5 SX1R RS Normal in x at Z1

6 SX1I RS Normal in x at Z1

7 SY1R RS Normal in y at Z1

8 SY1I RS Normal in y at Z1

9 TXY1R RS Shear in xy at Z1

10 TXY1I RS Shear in xy at Z1
224 New data blocks

Word Name Type Description

11 RMSVM1R RS RMS von Mises at Z1

12 RMSVM1I RS RMS von Mises at Z1

13 FD2 RS Fiber distance at Z2

14 SX2R RS Normal in x at Z2

15 SX2I RS Normal in x at Z2

16 SY2R RS Normal in y at Z2

17 SY2I RS Normal in y at Z2

18 TXY2R RS Shear in xy at Z2

19 TXY2I RS Shear in xy at Z2

20 RMSVM2R RS RMS von Mises at Z2

21 RMSVM2I RS RMS von Mises at Z2

Words 3 through 21 repeat 005 times

TCODE,7 =2 Real

2 TERM CHAR4

3 GRID I Number active grids identification


number or grid identification number

4 FD1 RS Fiber distance at Z1

5 SX1 RS Normal in x at Z1

6 SY1 RS Normal in y at Z1

7 TXY1 RS Shear in xy at Z1

8 RMSVM1 RS RMS von Mises at Z1

9 FD2 RS Fiber distance at Z2

10 SX2 RS Normal in x at Z2
New data blocks 225

Word Name Type Description

11 SY2 RS Normal in y at Z2

12 TXY2 RS Shear in xy at Z2

13 RMSVM2 RS RMS von Mises at Z2

Words 3 through 13 repeat 005 times

End TCODE,7

ELTYPE =83 Acoustic absorber element (CHACAB)

2 UNDEF None

ELTYPE =84 Acoustic barrier element (CHACBR)

2 UNDEF None

ELTYPE =85 TETRA - Nonlinear

2 UNDEF None

ELTYPE =86 GAP - Nonlinear

2 UNDEF None

ELTYPE =87 Nonlinear tube element (CTUBE)

2 UNDEF None

ELTYPE =88 TRIA3 - Nonlinear (Same as QUAD4)

2 UNDEF None Z1 = Fiber distance

ELTYPE =89 Nonlinear rod element (CROD)

2 UNDEF None

Word Name Type Description

ELTYPE =90 QUAD4 - Nonlinear

2 UNDEF None
226 New data blocks

Word Name Type Description

ELTYPE =91 Nonlinear five-sided solid element (CPENTA)

2 UNDEF None

ELTYPE =92 Nonlinear rod element connection and property


(CONROD)

2 UNDEF None

ELTYPE =93 Nonlinear six-sided solid element (CHEXA)

2 UNDEF None

ELTYPE =94 Nonlinear beam element (CBEAM)

2 UNDEF None

ELTYPE =95 QUAD4 composite

2 UNDEF None

ELTYPE =96 QUAD8 composite (Same as QUAD4 composite)

2 UNDEF None

ELTYPE =97 TRIA3 composite (Same as QUAD4 composite)

2 UNDEF None

ELTYPE =98 TRIA6 composite (Same as QUAD4 composite)

2 UNDEF None

ELTYPE =99 Undef

2 UNDEF None

Word Name Type Description

ELTYPE =100 Simple beam element w/stations (CBAR with


CBARAO or PLOAD1)

TCODE,7 =1 Real / Imaginary


New data blocks 227

Word Name Type Description

2 SD RS % along bar for output

3 SXCR RS Stress at point c

4 SXDR RS Stress at point d

5 SXER RS Stress at point e

6 SXFR RS Stress at point f

7 ASR RS Axial stress

8 SMAXR RS Maximum stress

9 SMINR RS Minimum stress

10 SXCI RS Stress at point c

11 SXDI RS Stress at point d

12 SXEI RS Stress at point e

13 SXFI RS Stress at point f

14 ASI RS Axial stress

15 SMAXI RS Maximum stress

16 SMINI RS Minimum stress

TCODE,7 =2 Real

2 SD RS % along bar for output

3 SXC RS Stress at point c

4 SXD RS Stress at point d

5 SXE RS Stress at point e

6 SXF RS Stress at point f

7 AS RS Axial stress
228 New data blocks

Word Name Type Description

8 SMAX RS Maximum stress

9 SMIN RS Minimum stress

End TCODE,7

ELTYPE =101 Acoustic absorber element with freq. dependence


(CAABSF)

TCODE,7 =2 Real

2 IMPED RS Impedance

3 ABSORB RS Absorption Coefficient

TCODE,7 =1 Real / Imaginary

2 IMPEDR RS Impedance

3 IMPEDI RS Impedance

4 ABSORB RS Absorption Coefficient

End TCODE,7

ELTYPE =102 Generalized spring and damper element (CBUSH)

TCODE,7 =2 Real

2 TX RS Translation x

3 TY RS Translation y

4 TZ RS Translation z

5 RX RS Rotation x

6 RY RS Rotation y

7 RZ RS Rotation z

TCODE,7 =1 Real / Imaginary

2 TXR RS Translation x R
New data blocks 229

Word Name Type Description

3 TYR RS Translation y R

4 TZR RS Translation z R

5 RXR RS Rotation x R

6 RYR RS Rotation y R

7 RZR RS Rotation z R

8 TXI RS Translation x I

9 TYI RS Translation y I

10 TZI RS Translation z I

11 RXI RS Rotation x I

12 RYI RS Rotation y I

13 RZI RS Rotation z I

End TCODE,7

ELTYPE =103 Quadrilateral shell element (QUADP)

2 UNDEF None

ELTYPE =104 Triangular shell p-element (TRIAP)

2 UNDEF None

ELTYPE =105 Beam p-element (BEAMP)

2 UNDEF None

ELTYPE =106 Scalar damper with material property (CDAMP5)

2 UNDEF None

ELTYPE =107 Heat transfer boundary condition element -


(CHBDYE)

2 UNDEF None
230 New data blocks

Word Name Type Description

ELTYPE =108 Heat transfer boundary condition element


(CHBDYG)

2 UNDEF None

ELTYPE =109 Heat transfer boundary condition element


(CHBDYP)

2 UNDEF None

Word Name Type Description

ELTYPE =110 CONV

2 UNDEF None

ELTYPE =111 CONVM

2 UNDEF None

ELTYPE =112 QBDY3

2 UNDEF None

ELTYPE =113 QVECT

2 UNDEF None

ELTYPE =114 QVOL

2 UNDEF None

ELTYPE =115 Radbc

2 UNDEF None

ELTYPE =116 Slideline contact (SLIF1D)

2 UNDEF None

Word Name Type Description

ELTYPE =127 CQUAD


New data blocks 231

Word Name Type Description

2 UNDEF None

ELTYPE =128 CQUADX

2 UNDEF None

ELTYPE =129 RELUC

2 UNDEF None

Word Name Type Description

ELTYPE =130 RES

2 UNDEF None

ELTYPE =131 TETRAE

2 UNDEF None

ELTYPE =132 CTRIA

2 UNDEF None

ELTYPE =133 CTRIAX

2 UNDEF None

ELTYPE =134 LINEOB

2 UNDEF None

ELTYPE =135 LINXOB

2 UNDEF None

ELTYPE =136 QUADOB

2 UNDEF None

ELTYPE =137 TRIAOB

2 UNDEF None
232 New data blocks

Word Name Type Description

ELTYPE =138 LINEX

2 UNDEF None

ELTYPE =139 Hyperelastic QUAD4FD

2 UNDEF None

Word Name Type Description

ELTYPE =140 Hyperelastic 8-noded hexahedron element linear


format (HEXAFD)

2 UNDEF None

ELTYPE =141 Six-sided solid p-element (HEXAP)

2 UNDEF None

ELTYPE =142 Five-sided solid p-element (PENTAP)

2 UNDEF None

ELTYPE =143 Four-sided solid p-element (TETRAP)

2 UNDEF None

ELTYPE =144 Quadrilateral plate element for corner stresses


(QUAD144)

TCODE,7 =1 Real / Imaginary

2 TERM CHAR4

3 GRID I

4 FD1 RS Fiber distance at z1

5 SX1R RS Normal in x at z1

6 SX1I RS Normal in x at z1

7 SY1R RS Normal in y at z1
New data blocks 233

Word Name Type Description

8 SY1I RS Normal in y at z1

9 TXY1R RS Shear in xy at z1

10 TXY1I RS Shear in xy at z1

11 RMSVM1R RS RMS von Mises at z1

12 RMSVM1I RS RMS von Mises at z1

13 FD2 RS Fiber distance at z2

14 SX2R RS Normal in x at z2

15 SX2I RS Normal in x at z2

16 SY2R RS Normal in y at z2

17 SY2I RS Normal in y at z2

18 TXY2R RS Shear in xy at z2

19 TXY2I RS Shear in xy at z2

20 RMSVM2R RS RMS von Mises at z2

21 RMSVM2I RS RMS von Mises at z2

Words 3 through 21 repeat 005 times

TCODE,7 =2 Real

2 TERM CHAR4

3 GRID I

4 FD1 RS Fiber distance at z1

5 SX1 RS Normal in x at z1

6 SY1 RS Normal in y at z1

7 TXY1 RS Shear in xy at z1
234 New data blocks

Word Name Type Description

8 RMSVM1 RS RMS von Mises at z1

9 FD2 RS Fiber distance at z2

10 SX2 RS Normal in x at z2

11 SY2 RS Normal in y at z2

12 TXY2 RS Shear in xy at z2

13 RMSVM2 RS RMS von Mises at z2

Words 3 through 13 repeat 005 times

End TCODE,7

ELTYPE =145 Six-sided solid display element (VUHEXA)

2 UNDEF None

ELTYPE =146 Five-sided solid display element (VUPENTA)

2 UNDEF None

ELTYPE =147 Four-sided solid display element (VUTETRA)

2 UNDEF None

ELTYPE =148 HEXAM

2 UNDEF None

ELTYPE =149 PENTAM

2 UNDEF None

Word Name Type Description

ELTYPE =150 TETRAM

2 UNDEF None

ELTYPE =151 QUADM


New data blocks 235

Word Name Type Description

2 UNDEF None

ELTYPE =152 TRIAM

2 UNDEF None

ELTYPE =153 QUADXM

2 UNDEF None

ELTYPE =154 TRIAXM

2 UNDEF None

ELTYPE =155 QUADPW

2 UNDEF None

ELTYPE =156 TRIAPW

2 UNDEF None

ELTYPE =157 LINEPW

2 UNDEF None

ELTYPE =158 QUADOBM

2 UNDEF None

ELTYPE =159 TRIAOBM

2 UNDEF None

Word Name Type Description

ELTYPE =160 Hyperelastic 5-sided 6-noded solid element


(PENTAFD) Linear form

2 UNDEF None

ELTYPE =161 Linear form for hyperelastic 4 node TETRA

2 UNDEF None
236 New data blocks

Word Name Type Description

ELTYPE =162 Linear form for hyperelastic 3 node TRIA (strain)

2 UNDEF None

ELTYPE =163 Linear form for hyperelastic 20 node HEXAFD

2 UNDEF None

ELTYPE =164 Hyperelastic quadrilateral 9-noded element


(QUADFD) Linear

2 UNDEF None

ELTYPE =165 Hyperelastic 5-sided 15-noded solid element


(PENTAFD) Linear

2 UNDEF None

ELTYPE =166 Linear form for hyperelastic 10 node TETRA

2 UNDEF None

ELTYPE =167 Linear form for hyperelastic 6 node TRIA (plane


strain)

2 UNDEF None

ELTYPE =168 Linear form for hyperelastic 3 node TRIA (axisymm)

2 UNDEF None

ELTYPE =169 Linear form for hyperelastic 6 node TRIA (axisymm)

2 UNDEF None

Word Name Type Description

ELTYPE =170 Linear form for hyperelastic 4 node QUAD


(axisymm)

2 UNDEF None
New data blocks 237

Word Name Type Description

ELTYPE =171 Linear form for hyperelastic 9 node QUAD


(axisymm)

2 UNDEF None

Word Name Type Description

ELTYPE =189 Quadrilateral plate view element (VUQUAD)

2 PARENT I Parent p-element identification


number

3 COORD I CID coordinate system identification


number

4 ICORD CHAR4 ICORD flat/curved and so on

5 THETA I THETA angle

6 ITYPE I ITYPE strcur =0, fiber=1

TCODE,7 =1 Real / Imaginary

7 VUID I VU grid identification number for this


corner

8 Z1 RS Z1 fiber distance

9 Z2 RS Z2 fiber distance

10 NX1R RS Normal x rm at Z1

11 NX1I RS Normal x ip at Z1

12 NY1R RS Normal y rm at Z1

13 NY1I RS Normal y ip at Z1

14 TXY1R RS Shear xy rm at Z1

15 TXY1I RS Shear xy ip at Z1

16 NZ1R RS Normal z rm at Z1 or n/a


238 New data blocks

Word Name Type Description

17 NZ1I RS Normal z ip at Z1 or n/a

18 TYZ1R RS Shear yz rm at Z1 or n/a

19 TYZ1I RS Shear yz ip at Z1 or n/a

20 TZX1R RS Shear zx rm at Z1 or n/a

21 TZX1I RS Shear zx ip at Z1 or n/a

22 NX2R RS Normal x rm at Z2

23 NX2I RS Normal x ip at Z2

24 NY2R RS Normal y rm at Z2

25 NY2I RS Normal y ip at Z2

26 TXY2R RS Shear xy rm at Z2

27 TXY2I RS Shear xy ip at Z2

28 NZ1R RS Normal z rm at Z1 or n/a

29 NZ1I RS Normal z ip at Z1 or n/a

30 TYZ1R RS Shear yz rm at Z1 or n/a

31 TYZ1I RS Shear yz ip at Z1 or n/a

32 TZX1R RS Shear zx rm at Z1 or n/a

33 TZX1I RS Shear zx ip at Z1 or n/a

Words 7 through 33 repeat 004 times

TCODE,7 =2 Real

2 UNDEF None

End TCODE,7
New data blocks 239

Word Name Type Description

ELTYPE =190 Triangular shell view element (VUTRIA)

2 UNDEF None

ELTYPE =191 Beam view element (VUBEAM)

2 UNDEF None

ELTYPE =192 CVINT

2 UNDEF None

ELTYPE =193 QUADFR

2 UNDEF None

ELTYPE =194 TRIAFR

2 UNDEF None

ELTYPE =195 LINEFR

2 UNDEF None

ELTYPE =196 LINXFR

2 UNDEF None

ELTYPE =197 GMINTS

2 UNDEF None

ELTYPE =198 CNVPEL

2 UNDEF None

ELTYPE =199 VUHBDY

2 UNDEF None

Word Name Type Description

ELTYPE =200 CWELD


240 New data blocks

Word Name Type Description

2 UNDEF None

ELTYPE =201 Hyperelastic quadrilateral 4-noded, nonlinear


format (QUAD4FD)

2 UNDEF None

ELTYPE =202 Hyperelastic hexahedron 8-noded, nonlinear format


(HEXA8FD)

2 UNDEF None

ELTYPE =203 Slideline contact (SLIF1D)

2 UNDEF None

ELTYPE =204 Hyperelastic pentahedron 6-noded, nonlinear


format (PENTA6FD)

2 UNDEF None

ELTYPE =205 Hyperelastic tetrahedron 4-noded, nonlinear format


(TETRA4FD)

2 UNDEF None

ELTYPE =206 Hyperelastic triangular 3-noded, nonlinear format


(TRIA3FD)

2 UNDEF None

ELTYPE =207 Hyperelastic hexahedron 20-noded, nonlinear


format (HEXAFD)

2 UNDEF None

ELTYPE =208 Hyperelastic quadrilateral 8-noded, nonlinear


format (QUADFD)

2 UNDEF None

ELTYPE =209 Hyperelastic pentahedron 15-noded nonlinear


format (PENTAFD)

2 UNDEF None
New data blocks 241

Word Name Type Description

ELTYPE =210 Hyperelastic tetrahedron 10-noded nonlinear format


(TETRAFD)

2 UNDEF None

ELTYPE =211 Hyperelastic triangular 6-noded, nonlinear format


(TRIAFD)

2 UNDEF None

ELTYPE =212 Hyperelastic axi. triangular 3-noded nonlinear


format (TRIAX3FD)

2 UNDEF None

ELTYPE =213 Hyperelastic axi. triangular 6-noded nonlinear


format (TRIAXFD)

2 UNDEF None

ELTYPE =214 Hyperelastic axi. quadrilateral 4-noded nonlinear


format(QUADX4FD)

2 UNDEF None

ELTYPE =215 Hyperelastic axi. quadrilateral 8-noded nonlinear


format (QUADXFD)

2 UNDEF None

ELTYPE =216 Hyperelastic tetrahedron 4-noded nonlinear format


(TETRA4FD)

2 UNDEF None

ELTYPE =217 Hyperelastic triangular 3-noded nonlinear format


(TRIA3FD)

2 UNDEF None

ELTYPE =218 Hyperelastic hexahedron 20-noded nonlinear format


(HEXAFD)

2 UNDEF None
242 New data blocks

Word Name Type Description

ELTYPE =219 Hyperelastic quadrilateral 8-noded nonlinear


format (QUADFD)

2 UNDEF None

Word Name Type Description

ELTYPE =220 Hyperelastic pentahedron 15-noded nonlinear


format (PENTAFD)

2 UNDEF None

ELTYPE =221 Hyperelastic tetrahedron 10-noded nonlinear format


(TETRAFD)

2 UNDEF None

ELTYPE =222 Hyperelastic axi. triangular 3-noded nonlinear


format (TRIAX3FD)

2 UNDEF None

ELTYPE =223 Hyperelastic axi. quadrilateral 8-noded nonlinear


format (QUADXFD)

2 UNDEF None

ELTYPE =224 Nonlinear ELAS1

2 UNDEF None

ELTYPE =225 Nonlinear ELAS3

2 UNDEF None

ELTYPE =226 Nonlinear BUSH

2 UNDEF None

ELTYPE =227 Triangular shell element (CTRIAR)

TCODE,7 =1 Real / Imaginary


New data blocks 243

Word Name Type Description

2 FD1 RS Z1 = Fibre Distance

3 SX1R RS Normal in x at Z1

4 SX1I RS Normal in x at Z1

5 SY1R RS Normal in y at Z1

6 SY1I RS Normal in y at Z1

7 TXY1R RS Shear in xy at Z1

8 TXY1I RS Shear in xy at Z1

9 RMSVM1R RS RMS von Mises at Z1

10 RMSVM1I RS RMS von Mises at Z1

11 FD2 RS Z2 = Fibre Distance

12 SX2R RS Normal in x at Z2

13 SX2I RS Normal in x at Z2

14 SY2R RS Normal in y at Z2

15 SY2I RS Normal in y at Z2

16 TXY2R RS Shear in xy at Z2

17 TXY2I RS Shear in xy at Z2

18 RMSVM2R RS RMS von Mises at Z2

19 RMSVM2I RS RMS von Mises at Z2

TCODE,7 =2 Real

2 FD1 RS Z1 = Fibre Distance

3 SX1 RS Normal in x at Z1

4 SY1 RS Normal in y at Z1
244 New data blocks

Word Name Type Description

5 TXY1 RS Shear in xy at Z1

6 RMSVM1 RS RMS von Mises at Z1

7 FD2 RS Z2 = Fibre Distance

8 SX2 RS Normal in x at Z2

9 SY2 RS Normal in y at Z2

10 TXY2 RS Shear in xy at Z2

11 RMSVM2 RS RMS von Mises at Z2

End TCODE,7

ELTYPE =228 Quadrilateral plate element (CQUADR)

TCODE,7 =1 Real / Imaginary

2 FD1 RS Z1 = Fibre Distance

3 SX1R RS Normal in x at Z1

4 SX1I RS Normal in x at Z1

5 SY1R RS Normal in y at Z1

6 SY1I RS Normal in y at Z1

7 TXY1R RS Shear in xy at Z1

8 TXY1I RS Shear in xy at Z1

9 RMSVM1R RS RMS von Mises at Z1

10 RMSVM1I RS RMS von Mises at Z1

11 FD2 RS Z2 = Fibre Distance

12 SX2R RS Normal in x at Z2

13 SX2I RS Normal in x at Z2
New data blocks 245

Word Name Type Description

14 SY2R RS Normal in y at Z2

15 SY2I RS Normal in y at Z2

16 TXY2R RS Shear in xy at Z2

17 RMSVM2R RS RMS von Mises at Z2

18 RMSVM2I RS RMS von Mises at Z2

TCODE,7 =2 Real

2 FD1 RS Z1 = Fibre Distance

3 SX1 RS Normal in x at Z1

4 SY1 RS Normal in y at Z1

5 TXY1 RS Shear in xy at Z1

6 RMSVM1 RS RMS von Mises at Z1

7 FD2 RS Z2 = Fibre Distance

8 SX2 RS Normal in x at Z2

9 SY2 RS Normal in y at Z2

10 TXY2 RS Shear in xy at Z2

11 RMSVM2 RS RMS von Mises at Z2

End TCODE,7

Word Name Type Description

ELTYPE =232 QUADR composite

2 UNDEF None

ELTYPE =233 TRIAR composite (Same as TRIAR composite)

2 UNDEF None
246 New data blocks

Word Name Type Description

ELTYPE =240 CTRIA6 - Nonlinear - Center and corners

2 UNDEF None

Word Name Type Description

ELTYPE =241 CQUAD8 - Nonlinear - Center and corners

2 UNDEF None

ELTYPE =242 Axisymmetric triangular element (CTRAX3)


Linear Stress - Center and corners

TCODE,7 =1 Real / Imaginary

2 CTYPE CHAR4 Coordinate Type (BCD)

3 LOC I Location Code

4 SXR RS Normal stress in X Real part

5 SXI RS Normal stress in X Imaginary part

6 SYR RS Normal stress in Y Real part

7 SYI RS Normal stress in Y Imaginary part

8 SZR RS Normal stress in Z Real part

9 SZI RS Normal stress in Z Imaginary part

10 SPR RS In-plane shear stress Real part

11 SPI RS In-plane shear stress Imaginary part

12 RMSVMR RS RMS von Mises Real part

13 RMSVMI RS RMS von Mises Imaginary part

Words 3 through 13 process 4 times

TCODE,7 =2 Real
New data blocks 247

2 CTYPE CHAR4 Coordinate Type (BCD)

3 LOC I Location Code

4 SX RS Normal stress in X

5 SY RS Normal stress in Y

6 SZ RS Normal stress in Z

7 SP RS In-plane shear stress

8 RMSVM RS RMS von Mises

Words 3 through 8 process 4 times

End TCODE,7

ELTYPE =243 Axisymmetric quad element (CQUADX4) Linear


Stress - Center and corners

TCODE,7 =1 Real / Imaginary

2 LOC I Location Code

3 SXR RS Normal stress in X Real part

4 SXI RS Normal stress in X Imaginary part

5 SYR RS Normal stress in Y Real part

6 SYI RS Normal stress in Y Imaginary part

7 SZR RS Normal stress in Z Real part

8 SZI RS Normal stress in Z Imaginary part

9 SPR RS In-plane shear stress Real part

10 SPI RS In-plane shear stress Imaginary part

11 RMSVMR RS RMS von Mises Real part

12 RMSVMI RS RMS von Mises Imaginary part


248 New data blocks

Words 2 through 12 process 5 times

TCODE,7 =2 Real

2 LOC I Location Code

3 SX RS Normal stress in X

4 SY RS Normal stress in Y

5 SZ RS Normal stress in Z

6 SP RS In-plane shear stress

7 RMSVM RS RMS von Mises

Words 2 through 7 process 5 times

End TCODE,7

ELTYPE =244 Axisymmetric triangle element (CTRAX6) Linear


Stress - Center and corners

TCODE,7 =1 Real / Imaginary

2 LOC I Location Code

3 SXR RS Normal stress in X Real part

4 SXI RS Normal stress in X Imaginary part

5 SYR RS Normal stress in Y Real part

6 SYI RS Normal stress in Y Imaginary part

7 SZR RS Normal stress in Z Real part

8 SZI RS Normal stress in Z Imaginary part

9 SPR RS In-plane shear stress Real part

10 SPI RS In-plane shear stress Imaginary part

11 RMSVMR RS RMS von Mises Real part


New data blocks 249

12 RMSVMI RS RMS von Mises Imaginary part

Words 2 through 12 process 4 times

TCODE,7 =2 Real

2 LOC I Location Code

3 SX RS Normal stress in X

4 SY RS Normal stress in Y

5 SZ RS Normal stress in Z

6 SP RS In-plane shear stress

7 RMSVM RS RMS von Mises

Words 2 through 7 process 4 times

End TCODE,7

ELTYPE =245 Axisymmetric quad element (CQUADX8) Linear


Stress - Center and corners

TCODE,7 =1 Real / Imaginary

2 LOC I Location Code

3 SXR RS Normal stress in X Real part

4 SXI RS Normal stress in X Imaginary part

5 SYR RS Normal stress in Y Real part

6 SYI RS Normal stress in Y Imaginary part

7 SZR RS Normal stress in Z Real part

8 SZI RS Normal stress in Z Imaginary part

9 SPR RS In-plane shear stress Real part

10 SPI RS In-plane shear stress Imaginary part


250 New data blocks

11 RMSVMR RS RMS von Mises Real part

12 RMSVMI RS RMS von Mises Imaginary part

Words 2 through 12 process 5 times

TCODE,7 =2 Real

2 LOC I Location Code

3 SX RS Normal stress in X

4 SY RS Normal stress in Y

5 SZ RS Normal stress in Z

6 SP RS In-plane shear stress

7 RMSVM RS RMS von Mises

Words 2 through 7 process 5 times

End TCODE,7

ELTYPE =246 Axisymmetric triangle element (CTRAX3)


Nonlinear Stress/Strain - Center and corners

2 UNDEF None

ELTYPE =247 Axisymmetric quad element (CQUADX4) Nonlinear


Stress/Strain - Center and corners

2 UNDEF None

ELTYPE =248 Axisymmetric triangle element (CTRAX6)


Nonlinear Stress/Strain - Center and corners

2 UNDEF None

ELTYPE =249 Axisymmetric quad element (CQUADX8) Nonlinear


Stress/Strain - Center and corners
New data blocks 251

2 UNDEF None

ELTYPE =250 Axisymmetric triangle element (CTRAX3) Linear


form of hyperelastic Gauss Location

2 UNDEF None

ELTYPE =251 Axisymmetric quad element (CQUADX4) Linear


form of hyperelastic Gauss Locations

2 UNDEF None

ELTYPE =252 Axisymmetric triangle element (CTRAX6) Linear


form of hyperelastic Gauss Locations

2 UNDEF None

ELTYPE =253 Axisymmetric quad element (CQUADX8) Linear


form of hyperelastic Gauss Locations

2 UNDEF None

Word Name Type Description

ELTYPE =254 CQUAD4 - Nonlinear - Center and corners

2 UNDEF None

ELTYPE = 255 CPYRAM Linear Stress

TCODE,7 =1 Real / Imaginary

2 CID I Stress Coordinate System

3 CTYPE CHAR4 Coordinate System Type (BCD)

4 NODEF I Number of Active Points

5 GRID I External grid identification number


(0=center)
252 New data blocks

6 SXR RS Normal in x

7 SYR RS Normal in y

8 SZR RS Normal in z

9 TXYR RS Shear in xy

10 TYZR RS Shear in yz

11 TZXR RS Shear in zx

12 SXI RS Normal in x

13 SYI RS Normal in y

14 SZI RS Normal in z

15 TXYI RS Shear in xy

16 TYZI RS Shear in yz

17 TZXI RS Shear in zx

18 RMSVMR RS RMS von Mises

19 RMSVMI RS RMS von Mises

Words 5 through 19 process 6 times

TCODE,7 =2 Real

2 CID I Stress Coordinate System

3 CTYPE CHAR4 Coordinate System Type (BCD)

4 NODEF I Number of Active Points

5 GRID I External grid identification number


(0=center)

6 SX RS Normal in x

7 SY RS Normal in y

8 SZ RS Normal in z
New data blocks 253

9 TXY RS Shear in xy

10 TYZ RS Shear in yz

11 TZX RS Shear in zx

12 RMSVM RS RMS von Mises

Words 5 through 12 process 6 times

End TCODE,7

ELTYPE =256 CPYRAM - Nonlinear

2 UNDEF None

ELTYPE =257 CPYRAM (linear element, 5 grids) Hyperelastic


nonlinear format

2 UNDEF None

ELTYPE =258 CPYRAM (parabolic element, 13 grids)


Hyperelastic nonlinear format

2 UNDEF None

ELTYPE =259 Reserved for hyperelastic PYRAM 5-noded, linear


form.

ELTYPE =260 Reserved for hyperelastic PYRAM 13-noded, linear


form.

ELTYPE =261 Axisymmetric triangle element (CTRAX3)


Nonlinear form of hyperelastic

2 UNDEF None

ELTYPE =262 Axisymmetric quad element (CQUADX4) Nonlinear


form of hyperelastic
254 New data blocks

2 UNDEF None

ELTYPE =263 Axisymmetric triangle element (CTRAX6)


Nonlinear form of hyperelastic

2 UNDEF None

ELTYPE =264 Axisymmetric quad element (CQUADX8) Nonlinear


form of hyperelastic Grid Locations

2 UNDEF None

ELTYPE =266 Axisymmetric quad element (CQUADX8) Nonlinear


form of hyperelastic 9 Gauss Locations

2 UNDEF None

ELTYPE =269 Composite HEXA element (CHEXAL) Center and


corners

2 UNDEF None

ELTYPE =270 Composite PENTA element (CPENTAL) Center


and corners

2 UNDEF None

ELTYPE =271 Triangle plane strain (CPLSTN3) Center

TCODE,7=1 Real / Imaginary

2 SXR RS Normal stress in x real part

3 SXI RS Normal stress in x imaginary part

4 SYR RS Normal stress in y real part

5 SYI RS Normal stress in y imaginary part

6 SZR RS Normal stress in z real part


New data blocks 255

7 SZI RS Normal stress in z imaginary part

8 SPR RS In-plane shear stress real part

9 SPI RS In-plane shear stress imaginary part

10 RMSVMR RS RMS von Mises real part

11 RMSVMI RS RMS von Mises imaginary part

TCODE,7=2 Real

2 SX RS Normal stress in x

3 SY RS Normal stress in y

4 SZ RS Normal stress in z

5 SP RS In-plane shear stress

6 RMSVM RS RMS von Mises

End TCODE,7

ELTYPE =272 Quadrilateral plane strain (CPLSTN4) Center and


Corners

TCODE,7=1 Real / Imaginary

2 TERM CHAR4 CEN

3 GRID I Grid identification number; 0 for


centroid

4 SXR RS Normal stress in x real part

5 SXI RS Normal stress in x imaginary part

6 SYR RS Normal stress in y real part

7 SYI RS Normal stress in y imaginary part

8 SZR RS Normal stress in z real part

9 SZI RS Normal stress in z imaginary part


256 New data blocks

10 SPR RS In-plane shear stress real part

11 SPI RS In-plane shear stress imaginary part

12 RMSVMR RS RMS von Mises real part

13 RMSVMI RS RMS von Mises imaginary part

Words 3 through 13 repeat 5 times

TCODE,7=2 Real

2 TERM CHAR4 CEN

3 GRID I Grid identification number; 0 for


centroid

4 SX RS Normal stress in x

5 SY RS Normal stress in y

6 SZ RS Normal stress in z

7 SP RS In-plane shear stress

8 RMSVM RS RMS von Mises

Words 3 through 8 repeat 5 times

End TCODE,7

ELTYPE =273 Triangle plane strain (CPLSTN6 ) Center and


Corners

TCODE,7=1 Real / Imaginary

2 TERM CHAR4 CEN

3 GRID I Grid identification number; 0 for


centroid

4 SXR RS Normal stress in x real part

5 SXI RS Normal stress in x imaginary part


New data blocks 257

6 SYR RS Normal stress in y real part

7 SYI RS Normal stress in y imaginary part

8 SZR RS Normal stress in z real part

9 SZI RS Normal stress in z imaginary part

10 SPR RS In-plane shear stress real part

11 SPI RS In-plane shear stress imaginary part

12 RMSVMR RS RMS von Mises real part

13 RMSVMI RS RMS von Mises imaginary part

Words 3 through 13 repeat 4 times

TCODE,7=2 Real

2 TERM CHAR4 CEN

3 GRID I Grid identification number; 0 for


centroid

4 SX RS Normal stress in x

5 SY RS Normal stress in y

6 SZ RS Normal stress in z

7 SP RS In-plane shear stress

8 RMSVM RS RMS von Mises

Words 3 through 8 repeat 4 times

End TCODE,7

ELTYPE =274 Quadrilateral plane strain (CPLSTN8) Center and


Corners

TCODE,7=1 Real / Imaginary

2 TERM CHAR4 CEN


258 New data blocks

3 GRID I Grid identification number; 0 for


centroid

4 SXR RS Normal stress in x real part

5 SXI RS Normal stress in x imaginary part

6 SYR RS Normal stress in y real part

7 SYI RS Normal stress in y imaginary part

8 SZR RS Normal stress in z real part

9 SZI RS Normal stress in z imaginary part

10 SPR RS In-plane shear stress real part

11 SPI RS In-plane shear stress imaginary part

12 RMSVMR RS RMS von Mises real part

13 RMSVMI RS RMS von Mises imaginary part

Words 3 through 13 repeat 5 times

TCODE,7=2 Real

2 TERM CHAR4 CEN

3 GRID I Grid identification number; 0 for


centroid

4 SX RS Normal stress in x

5 SY RS Normal stress in y

6 SZ RS Normal stress in z

7 SP RS In-plane shear stress

8 RMSVM RS RMS von Mises

Words 3 through 8 repeat 5 times

End TCODE,7
New data blocks 259

ELTYPE =275 Triangle plane stress (CPLSTS3) Center

TCODE,7=1 Real / Imaginary

2 SXR RS Normal stress in x real part

3 SXI RS Normal stress in x imaginary part

4 SYR RS Normal stress in y real part

5 SYI RS Normal stress in y imaginary part

6 SZR RS Normal stress in z real part

7 SZI RS Normal stress in z imaginary part

8 SPR RS In-plane shear stress real part

9 SPI RS In-plane shear stress imaginary part

10 RMSVMR RS RMS von Mises real part

11 RMSVMI RS RMS von Mises imaginary part

TCODE,7=1 Real

2 SX RS Normal stress in x

3 SY RS Normal stress in y

4 SZ RS Normal stress in z

5 SP RS In-plane shear stress

6 RMSVM RS RMS von Mises

End TCODE,7

ELTYPE =276 Quadrilateral plane stress (CPLSTS4) Center and


Corners

TCODE,7=1 Real / Imaginary

2 TERM CHAR4 CEN


260 New data blocks

3 GRID I Grid identification number; 0 for


centroid

4 SXR RS Normal stress in x real part

5 SXI RS Normal stress in x imaginary part

6 SYR RS Normal stress in y real part

7 SYI RS Normal stress in y imaginary part

8 SZR RS Normal stress in z real part

9 SZI RS Normal stress in z imaginary part

10 SPR RS In-plane shear stress real part

11 SPI RS In-plane shear stress imaginary part

12 RMSVMR RS RMS von Mises real part

13 RMSVMI RS RMS von Mises imaginary part

Words 3 through 13 repeat 5 times

TCODE,7=2 Real

2 TERM CHAR4 CEN

3 GRID I Grid identification number; 0 for


centroid

4 SX RS Normal stress in x

5 SY RS Normal stress in y

6 SZ RS Normal stress in z

7 SP RS In-plane shear stress

8 RMSVM RS RMS von Mises

Words 3 through 8 repeat 5 times

End TCODE,7
New data blocks 261

ELTYPE =277 Triangle plane stress (CPLSTS6) Center and


Corners

TCODE,7=1 Real / Imaginary

2 TERM CHAR4 CEN

3 GRID I Grid identification number; 0 for


centroid

4 SXR RS Normal stress in x real part

5 SXI RS Normal stress in x imaginary part

6 SYR RS Normal stress in y real part

7 SYI RS Normal stress in y imaginary part

8 SZR RS Normal stress in z real part

9 SZI RS Normal stress in z imaginary part

10 SPR RS In-plane shear stress real part

11 SPI RS In-plane shear stress imaginary part

12 RMSVMR RS RMS von Mises real part

13 RMSVMI RS RMS von Mises imaginary part

Words 3 through 13 repeat 4 times

TCODE,7=2 Real

2 TERM CHAR4 CEN

3 GRID I Grid identification number; 0 for


centroid

4 SX RS Normal stress in x

5 SY RS Normal stress in y

6 SZ RS Normal stress in z

7 SP RS In-plane shear stress


262 New data blocks

8 RMSVM RS RMS von Mises

Words 3 through 8 repeat 4 times

End TCODE,7

ELTYPE =278 Quadrilateral plane stress (CPLSTS8) Center and


Corners

TCODE,7=1 Real / Imaginary

2 TERM CHAR4 CEN

3 GRID I Grid identification number; 0 for


centroid

4 SXR RS Normal stress in x real part

5 SXI RS Normal stress in x imaginary part

6 SYR RS Normal stress in y real part

7 SYI RS Normal stress in y imaginary part

8 SZR RS Normal stress in z real part

9 SZI RS Normal stress in z imaginary part

10 SPR RS In-plane shear stress real part

11 SPI RS In-plane shear stress imaginary part

12 RMSVMR RS RMS von Mises real part

13 RMSVMI RS RMS von Mises imaginary part

Words 3 through 13 repeat 5 times

TCODE,7=2 Real

2 TERM CHAR4 CEN

3 GRID I Grid identification number; 0 for


centroid
New data blocks 263

4 SX RS Normal stress in x

5 SY RS Normal stress in y

6 SZ RS Normal stress in z

7 SP RS In-plane shear stress

8 RMSVM RS RMS von Mises

Words 3 through 8 repeat 5 times

End TCODE,7

ELTYPE =281 Triangle plane strain (CPLSTN3) Nonlinear format


Center

2 UNDEF None

ELTYPE =283 Triangle plane strain (CPLSTN6) Nonlinear format


Center and Corners

2 UNDEF None

ELTYPE =284 Quadrilateral plane strain (CPLSTN8) Nonlinear


format Center and Corners

2 UNDEF None

ELTYPE =285 Triangle plane stress (CPLSTS3) Nonlinear format


Center

2 UNDEF None

ELTYPE =287 Triangle plane stress (CPLSTS6) Nonlinear format


Center and Corners

2 UNDEF None
264 New data blocks

ELTYPE =288 Quadrilateral plane stress (CPLSTS8) Nonlinear


format Center and Corners

2 UNDEF None

ELTYPE =289 Quadrilateral plane strain (CPLSTN4) Nonlinear


format Center and Corners

2 UNDEF None

ELTYPE =290 Quadrilateral plane stress (CPLSTS4) Nonlinear


format Center and Corners

2 UNDEF None

ELTYPE =291 Triangle plane strain (CPLSTN3) Hyperelastic -


Grid

2 UNDEF None

ELTYPE =292 Quadrilateral plane strain (CPLSTN4) Hyperelastic


- Grid

2 UNDEF None

ELTYPE =293 Triangle plane strain (CPLSTN6) Hyperelastic -


Grid

2 UNDEF None

ELTYPE =294 Quadrilateral plane strain (CPLSTN8) Hyperelastic


- Grid

2 UNDEF None

ELTYPE =295 Triangle plane stress (CPLSTS3) Hyperelastic -


Grid
New data blocks 265

2 UNDEF None

ELTYPE =296 Quadrilateral plane stress (CPLSTS4) Hyperelastic


- Grid

2 UNDEF None

ELTYPE =297 Triangle plane stress (CPLSTS6) Hyperelastic -


Grid

2 UNDEF None

ELTYPE =298 Quadrilateral plane stress (CPLSTS8) Hyperelastic


- Grid

2 UNDEF None

Word Name Type Description

End ELTYPE

Record TRAILER

Word Name Type Description

1 UNDEF(6) None

Notes:
1. For CBEAM (2) Item codes are given for end A. Addition of the quantity (K-1)
10 to the item code points to the same information for other stations, where K
is the station number. K=11 for end B and 2-10 for intermediate stations.

2. For CHEX8 there are 9 stress points for each element. For CHEX20 there are 9
plus (the number of nondeleted mid-side nodes) stress points for each element.

3. For QUAD8 (64) For corner grids, real , add 17I to items 3 through 19, where I
= 1,2,3,4 (87 total words). For corner grids, real/imaginary add 15I to items 3
through 19, where I = 1,2,3,4 (77 total words).
266 New data blocks

OTEMP
Table of grid point temperatures.

Record HEADER

Word Name Type Description

1 NAME(2) CHAR4 Data block Name

3 WORD I No Def or Month, Year, One, One

Word 3 repeats until End of Record

Record IDENT

Word Name Type Description

1 ACODE(C) I Device code + 10*Approach Code

2 TCODE(C) I Table Code

3 UNDEF None

4 SUBCASE I Subcase or random identification


number

5 TIMESTEP RS Current time step

6 UNDEF(3) None

9 FCODE I Format code

10 NUMWDE I Number of words per entry in DATA


record

11 UNDEF(40) None

51 TITLE(32) CHAR4 Title

83 SUBTITL(32) CHAR4 Subtitle

115 LABEL(32) CHAR4 Label


New data blocks 267

Record DATA

Word Name Type Description

1 EKEY I Device code + 10*Point identification


number

2 TEMP RS Grid point temperature

Record TRAILER

Word Name Type Description

1 UNDEF(6) None

Updated modules

DOM9

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,DESVUP/
XO,CVALO,R1VALO,R2VALO,PROPO,R3VALO/
OBJIN/S,N,OBJOUT/PROTYP/PROPTN/PBRPROP/
UNUSED2/UNUSED3/UNUSED4/UNUSED5/UNUSED6/
UNUSED7/UNUSED8/UNUSED9/UNUSED10 $

New Input Data Block:

DESVUP Updates for design variable bounds based on relevant DV*REL1


data.
268 Updated modules

DOPFS

Updated Format:

DOPFS R1TABRG,CNTABRG,DESELM,DVPTAB*,CVALRG,
PROPI,OPTPRMG,DPLDXT*,CONSBL*,DESTAB,
XINIT,DPLDXI*,PLIST2*,DEQIND,DEQATN,
EPTTAB*,DBMLIB,XZ,DXDXI,DXDXIT,DESVUP/
XO,PROPO $

New Input Data Block:

DESVUP Updates for design variable bounds based on relevant DV*REL1


data.

DOPR1

Updated Format:

DOPR1 EDOM,EPT,DEQATN,DEQIND,GEOM2,MPT,CASEXX,DIT/
DESTAB,XZ,DXDXI,DTB,DVPTAB*,EPTTAB*,CONSBL*,
DPLDXI*,PLIST2*,XINIT,PROPI*,DSCREN,DTOS2J*,
OPTPRM,CONS1T,DBMLIB,BCON0,BCONXI,DMATCK,DISTAB,
CASETM,SPAN23,MFRDEP,DESVUP/
S,N,MODEPT/S,N,MODGEOM2/S,N,MODMPT/DPEPS/
S,N,PROTYP/S,N,DISVAR $

New Output Data Block:

DESVUP Updates for design variable bounds based on relevant DV*REL1


data.
Updated modules 269

DSAD

Updated Format:
DSAD RSPCSC,R1TCSC,R12CSC,OBJCSC,CONCSC,
BLAMA,LAMA,CLAMA,DIVTAB,AUXTAB,STBTAB,
FLUTAB,OUG1DS,OES1DS,OSTR1DS,OEF1DS,
OEFITDS,OES1CDS,OSTR1CDS,OQG1DS,DSCREN,
XINIT,COORDN,OL,FRQRSP,CASEER,
CASERS,UGX,OPTPRM,DVPTAB*,PROPI*,
BGPDT,DNODEL,WGTM,ONRGYDS,
GLBTABDS,GLBRSPDS,R3CSC,RMSTAB,RMSVAL,SPAN1RG,
OUGPSD1,DYNAMICS,SABFIL,OERP200,OERPEL0,ERPFIL*/
R1VAL,R2VAL,RSP2R,R2VALR,CVAL,
CVALR,OBJTBR,CNTABR,R1TABR,R1VALR,
DRSTBL,FRQRPR,UGX1,AUG1,R1MAPR,
R2MAPR,CASDSN,CASDSX,DRDUG,DRDUTB,
CASADJ,LCDVEC,RR2IDR,R3VAL,R3VALR,RESP3R,RMSTABR,
RMSVALR,SPANSV,SPANSVG/
WGTS/VOLS/S,N,OBJVAL/S,N,NR1OFFST/S,N,NR2OFFST/
S,N,NCNOFFST/APP/DMRESD/SEID/DESITER/
EIGNFREQ/S,N,ADJFLG/PEXIST/MBCFLG/RGSENS/
PROTYP/AUTOADJ/FSDCYC/S,N,NR3OFFST/INREL $

New Input Data Blocks:

OERP200 Panel ERP design responses.

OERPEL0 Element ERP design responses in SORT1 format.

ERPFIL* Subcase based family of element level ERP design response


derivatives.

GP4

Updated Format:
GP4 CASECC,GEOM4,EQEXIN,SIL,GPDT,BGPDT,CSTM,
MEDGE,MFACE,MBODY,GEOM2,GDNTAB,GPECTO/
RMG,YS0,USET0,PARTV/
LUSET/S,N,NOMSET/S,N,MPCF2/S,N,NOSSET/S,N,NOOSET/
S,N,NORSET/S,N,NSKIP/S,N,REPEAT/S,N,NOSET/S,N,NOL/
S,N,NOA/SEID/ALTSHAPE/SEBULK/DMAPNO/AUTOMPC/AMPCZ/RSONLY $

New Parameter:

RSONLY Input-logical-default=FALSE. Residual structure only flag.


270 Updated modules

MODGM2B

Updated Format:
MODGM2B CASECC,MPT,EPT,GEOM1,GEOM2,GEOM4,CONTACT,EDT,IGEOM3/
MGEOM1,MGEOM2,MGEOM4,MCONTACT,SBDATA,MGEOM3/
BOLTFACT/S,N,IBTEX $

New Input Data Block:

IGEOM3 Static and thermal load information

New Output Data Block:

MGEOM3 Modified static and thermal load information

OFP

Updated Format:
OFP OFP1,OFP2,OFP3,OFP4,OFP5,OFP6,
CSTM,EHT,BGPDTVU,ERROR1,DEQATN,DEQIND,DIT//
S,N,CARDNO/ODCODE/PVALID/ABSEM $

Removed Parameters:

DFLAG Input-integer-default=0. Displacement output flag.


= 0 output displacement as is
= 1 output displacement as "relative motion
= 2 do not output displacement

VFLAG Input-integer-default=0. Velocity output flag.


= 0 output velocity as is
= 1 output velocity as "relative motion
= 2 do not output velocity

AFLAG Input-integer-default=0. Acceleration output flag.


= 0 output acceleration as is
= 1 output acceleration as "relative motion
= 2 do not output acceleration
Updated modules 271

PANELERP

Updated Format:

PANELERP CASEG,BGPDTS,CSTMS,ECTS,EDTS,FOLX,UGCASE/OERP,OERPEL1,ERPFIL $

New Output Data Blocks:

OERPEL1 ERP design responses at element level in SORT1 format for a


particular subcase.

ERPFIL Element level ERP design response derivatives for a particular


subcase.

RSVECEL

Updated Format:

RSVECEL ECT,GEOM4,BGPDT,CSTM,EPT/
RVELG/
NOGSET/OPTION $

New Parameter:

OPTION Input-integer-default=0. Residual vector request option.


=0 No RVEL/DAMP
=1 RVEL only
=2 DAMP only
=3 RVEL and DAMP
272 Updated modules

SDR2

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,COMPEST,EPT,DYNAMIC,EDT/
OPG1,OQG1,OUG1,OES1,OEF1,PUG,OGPKE1,OEFIIP,OEFIIS,OESRIP,OESRIS/
APP/S,N,NOSORT2/NOCOMP/ACOUSTIC/METRIK/
ISOFLG/GPF/ACOUT/PREFDB/TABS/
SIGMA/ADPTINDX/ADPTEXIT/BSKIP/FREQW/
BTBRS/LANGLE/OMID/SRCOMPS/APP1/GSPF/RPM $

New Parameter:

RPM Input-real-default=0.0

Reference rotor speed in units of RPM.

XYTRAN

Updated Format for SDR2 Outputs:


XYTRAN XYCDB,OPG2,OQG2,OUG2,OES2,OEF2,OSTR2,OQMG2/
XYPLOT/
APP/XYSET/S,N,PLTNUM/S,N,CARDNO/S,N,NOXYPLOT/
S,N,TABID $

Removed Parameters:

DFLAG Input-integer-default=0. Displacement output flag.


= 0 output displacement
= 1 do not output displacement

VFLAG Input-integer-default=0. Velocity output flag.


= 0 output velocity
= 1 do not output velocity

AFLAG Input-integer-default=0. Acceleration output flag.


= 0 output acceleration
= 1 do not output acceleration
New modules 273

New modules

CHKPNL
Checks Bulk Data PANEL input against ERP requests in Case Control.

Format:
CHKPNL CASECC,EDT//S,N,NOGO $

Input Data Blocks:

CASECC Table of Case Control entries

EDT Table of a subset of Bulk Data entries that also includes PANEL
entries

Output Data Blocks:

None

Parameters:

NOGO Output-logical-default=FALSE. Set to TRUE if an error is detected

DLT2SLT
Generates static loads from the dynamic load values at a given time.

Format:
DLT2SLT DLT,SLT,DIT,EST/NEWSLT/DTIME/CASEDLOD $

Input Data Blocks:

DLT Dynamic load table

SLT Static load table


274 New modules

DIT Direct input table

EST Element summary table

Output Data Block:

NEWSLT New static load table with values sampled from the time-dependent
load at DTIME

Parameters:

DTIME Input-real-no default. Solution time when the values for the new
static load table are sampled

CASEDLOD Input-integer-no default. DLOAD ID for the subcase

Remarks:
1. Currently, TLOAD1 is supported to generate SLT from DLT. In the future,
more load types will be supported.

IN4WA
Reads binary input file in special format for use with AMLS. Similar to INPUTT4
with IUNIT = 46.

Format:
IN4WA /DB/IUNIT/VSIZE $

Output Data Blocks:

DB Matrix stored in binary file.

Parameters:

IUNIT Integer-input-default=0. FORTRAN unit number (typically 46).


The module will open a file named fort.IUNIT.
New modules 275

VSIZE Integer-input-default=0. Size of output vector.

Remarks:
The INPUTT4 module may be used similarly as follows:
NASTRAN SYSTEM(459) = 0
ASSIGN INPUTT4 = fort.46
.....
.....
INPUTT4/DB,,,,/1/46/VSIZE $

NLCPRM
Returns value of parameter set in NLCNTL bulk data entry.

Format:
NLCPRM CASECC,MPT//P1/P2/S,N,P3/S,N,P4/S,N,P5 $

Input Data Blocks:

CASECC Table of case control command images

MPT Table of bulk data entry images related to material properties

Output Data Blocks:

None

Parameters:

P1 Input-character-no default

P2 Input-character-no default

P3 Output-integer-default=0

P4 Output-real-default=0.0

P5 Output-character-default=blank
276 New modules

Remarks:
1. Currently, P1 can be set to any character string and does not have any impact
on the modules operation. In the future, more options will be added. Example,
P1=DTI.

2. P2 is the parameter whose value the user requires to be returned. This


parameter can be any of those allowed in NLCNTL bulk data entry. The entire
parameter name is required. Example, P2=FOLLOWK. See the NLCNTL
bulk data entry for a complete list of parameter names in the NX NASTRAN
Quick Reference Guide.

3. Depending on the parameter requested, P3, P4, or P5 will need to be requested


in order to return the value of that parameter. For instance, P2=FOLLOWK
will require a character output variable to be specified in P5, leaving P3 and
P4 blank.

4. If the output variable is specified in the wrong location, there will be no


fatal or warning and the returned value will be incorrect. For instance, for
P2=FOLLOWK, if an output variable is requested in P4 (which is a real)
instead of P5, then there will be no fatal or warning but P4 will not contain the
value of FOLLOWK.

NLTRD3
Computes nonlinear analysis solution matrices and tables for SOL 401. Applicable
to quasi-static structural and thermal analysis.

Format:

NLTRD3 CASESX2H,PDT,YS,ELDATAH,KELMNL,
KDDL,GMNL,MPTS,DITS,KBDD,
DLT1,CSTMS,BGPDTS,SILS,USETD,
BRDD,MJJ,NLFT,UNUSED,UNUSED,
BDDL,GPSNTS,DITID,DEQIND,DEQATN,
ELGNST,GLUESEQ,COMPEST,KDICTNL,EPT,
ECTS,EDT,RGNL,YG,SLT,KELMUP/
ULNTH,IFSH,ESTNLH,IFDH,OES1,
PNLH,TELH,MULNT,MESTNL,UNUSED,
UNUSED,UNUSED,OSTR1,OSTR1EL,OSTR1TH,
OSTR1PL,OSTR1CR,OES1G,OSTR1G,OSTR1ELG,
OSTR1THG,OSTR1PLG,OSTR1CRG,OTEMP1,OES1C,
OSTR1C,OSTR1ELC,OSTR1THC,OQGGF1,OBG1,PLPG/
KRATIO/S,N,CONV/S,N,RSTIME/S,N,NEWP/S,N,NEWDT/
S,N,OLDDT/S,N,NSTEP/LGDISP/S,N,UNUSED/S,N,ITERID/
ITIME/S,N,KTIME/S,N,LASTUPD/S,N,NOGONL/S,N,NBIS/
MAXLP/TSTATIC/LANGLES/NDAMP/TABS/UNUSED/UNUSED/
S,N,UNUSED/UNUSED/UNUSED/GLUE $
New modules 277

Input Data Blocks:

CASESX2H Table of case control command images for current subcase

PDT Time-dependent load vectors for quasi-static analysis in the d-set

YS Matrix of enforced displacements

ELDATAH Table of combined nonlinear information data

KELMNL Table of element matrices for stiffness for nonlinear elements

KDDL Stiffness matrix for the d-set, linear elements only

GMNL Multipoint constraint transformation matrix for multipoint


constraint reduction

MPTS Table of bulk data entry images related to material properties

DITS Table of TABLEij bulk data entry images

KBDD Tangential stiffness in d-set

DLT1 Table of dynamic loads updated for nonlinear analysis

CSTMS Table of coordinate system transformation matrices

BGPDTS Basic grid point definition table

SILS Scalar index list

USETD Degree-of-freedom set membership table for the p-set

BRDD Damping matrix in the d-set for linear elements only

MJJ Mass matrix for the d-set

NLFT Nonlinear forcing function table

BDDL Damping matrix for the d-set for linear elements only

GPSNTS Grid point shell normal table

DITID Table of identification numbers in DIT

DEQIND Index table to DEQATN data block


278 New modules

DEQATN Table of DEQATN bulk data entry images

ELGNST Table of glue element stiffness

GLUESEQ Data table for glue elements

COMPEST Summary table for composite solid elements

KDICTNL KELMNL dictionary table, output by EMG

EPT Element property table

ECTS Element connectivity table, output by GP2

EDT Element data table for iterative solver

RGNL Matrix for multipoint constraint equations

YG Specified non-zero displacements in g-set

SLT Static load table

KELMUP Updated element stiffness matrix

Output Data Blocks:

ULNTH Solution matrix from nonlinear quasi-static analysis in the d-set

IFSH Matrix of nonlinear element forces at constrained points at the


output time steps

ESTNLH Nonlinear element summary table at converged step

IFDH Matrix of nonlinear element forces in the d-set at the output time
steps

OES1 Table of nonlinear element stresses in SORT1 format

PNLH Nonlinear load matrix appended from each output time step

TELH Time output list

MULNT Solution matrix from nonlinear quasi-static analysis in the d-set


from the previous subcase. Not supported in NX Nastran 9.
New modules 279

MESTNL Nonlinear element summary table at current step

OSTR1 Table of total strain in SORT1 format

OSTR1EL Table of elastic strain in SORT1 format

OSTR1TH Table of thermal strain in SORT1 format

OSTR1PL Table of plastic strain in SORT1 format

OSTR1CR Table of creep strain in SORT1 format

OES1G Table of stress at Gauss points in SORT1 format

OSTR1G Table of total strain at Gauss points in SORT1 format

OSTR1ELG Table of elastic strain at Gauss points in SORT1 format

OSTR1THG Table of thermal strain at Gauss points in SORT1 format

OSTR1PLG Table of plastic strain at Gauss points in SORT1 format

OSTR1CRG Table of creep strain at Gauss points in SORT1 format

OTEMP1 Table of grid point temperatures

OES1C Table of ply stress in SORT1 format

OSTR1C Table of ply strain in SORT1 format

OSTR1ELC Table of ply strains-elastic in SORT1 format

OSTR1THC Table of ply strains-thermal in SORT1 format

OQGGF1 Table of glue forces

OBG1 Table of glue tractions

PLPG Matrix of load vectors (P external + P follower force)

Parameters:

KRATIO Input/output-complex-default=(1.0,0.0). Stiffness ratio used for


time step adjustment. Not implemented on NX Nastran 9.
280 New modules

CONV Input/output-integer-default=1. Nonlinear analysis convergence


flag

On input:

0 Initialization

On output:

-1 Convergence has not been achieved

1 Convergence has been achieved

RSTIME Input/output-real-default=0.0. Time corresponding to the


current entry into NLTRD3

NEWP Output-integer-default=1. New subcase flag

-1 Current subcase has not been completed

1 Current subcase has been completed

NEWK Input/output-integer-default=1. Stiffness update flag

-1 Do not update stiffness

>0 Update stiffness

OLDDT Input/output-real-default=0.0. Time step increment used in


the previous iteration or time step to be used after the matrix
update or subcase switch

NSTEP Input/output-integer-default=0. Current time step position for


subcase, set to 0 at the beginning of the subcase

LGDISP Input-integer-no default. Large displacement flag

-1 No large displacement effects are considered

1 Large displacement effects are considered

ITERID Input/output-integer-no default. Nonlinear analysis iteration


count

ITIME Input-real-default=0.0. Initial time step at the beginning of


a subcase
New modules 281

KTIME Input/output-real-no default. CPU time remaining. If KTIME


is positive, KTIME is the time remaining at the start of the
stiffness update. If negative, no stiffness update was done since
the last exit from NLTRD3. KTIME still holds the negative of
the stiffness update time from the last stiffness update

LASTUPD Input/output-integer-default=0. The time step number of the


last stiffness update

NOGONL Output-integer-default=0. Nonlinear "no-go" flag. Set to +1 to


continue or -1 to terminate

NBIS Input/output-integer-default=0. Current bisection counter

MAXLP Input-integer-default=0. Maximum limit allowed for element


relaxation iteration and the material subincrement processes.
Set to 10 in NX Nastran 9 because only TSTATIC = 1
(quasi-static analysis) is supported.

TSTATIC Input-integer-default=-1. Static analysis flag. Set to 1 to ignore


inertia and damping forces. In NX Nastran 9, only TSTATIC
= 1 is supported.

LANGLE Input-integer-default=1. Large rotation calculation method:

1 Gimbal angle

2 Rotation vector

NDAMP Input-real-default=0.0. Numerical damping. Set to 0.01 for SOL


401 in NX Nastran 9.

TABS Input-real-default=0.0. Absolute temperature conversion


constant. For example, set to 273.16 when specifying
temperatures in Celsius or 459.69 in Fahrenheit

GLUE Input-logical-no default. Set to TRUE if glue is defined

UPGLSTF
Creates/updates glue stiffness in SOL 401.
282 New modules

Format:

UPGLSTF GNELM,BGPDT,CSTM,UGVBAS/ELGNST/NLHEAT/NROW $

Input Data Blocks:

GNELM Glue element definition table

BGPDT Basic grid point data table

CSTM Table of coordinate system transformation matrices

UGVBAS G-set displacements in basic coordinate system

Output Data Blocks:

ELGNST Glue element stiffness table

Parameters:

NLHEAT Input-logical-no default. Currently always set to FALSE for SOL


401

NROW Input-integer-no default. Number of rows in G-set


Chapter

12 NX Nastran 9 Problem Report (PR) fixes

NX Nastran 9 Problem Report (PR) fixes


The following list summarizes the problems found in previous releases of NX
Nastran and prototype versions of NX Nastran 9 that are fixed in NX Nastran 9.
If applicable, workaround information is provided for use with earlier versions of
NX Nastran.

Problem
PR# Problem Description
Reported
During a nonlinear buckling solve, the following
fatal error occurs because a scratch data block is not
saved.

USER INFORMATION MESSAGE 9005


(NLSTATIC)
1909559 V8.1 THE SOLUTION FOR LOOPID= 10 IS SAVED FOR
RESTART
SYSTEM FATAL MESSAGE 3007 (MCE1)
ILLEGAL INPUT TO SUBROUTINE PARTN
OFATAL ERROR

There is no workaround.
A SOL 106 run with CTETRA elements fails to
converge because of the integration points that are
used. The integration points are now changed and
the problem converges. The method to compute
1913958 V8.1 stress and plastic strain is also changed so that the
stress and plastic strain follow the stress-strain
curve.

There is no workaround.
284 NX Nastran 9 Problem Report (PR) fixes

During SOL 103 response simulation runs when


nodal force location is used for the computation of
attachment modes, a "MAIN: "Access violation"
(C0000005) exception encountered error occurs
because of an overlap between the USET U3 DOF set
1920149 V8.0 and DOF that the AUTOMPC process selects. The
AUTOMPC process has been corrected to no longer
select DOF from the USET U3 DOF for elimination.

The workaround is to not use the AUTOMPC


functionality.
For axisymmetric models with CTRAX3, CQUADX4,
CTRAX6, and CQUADX8 elements, the software
may not use the correct TREF in the computation of
1921654 V8.5
thermal load, and stress and strain. If only a single
value for TREF is used on all the MATi bulk entries,
the results are correct.
Solving a model with bolt preload applied to solid
elements and with AUTOMPC = YES produces the
following message:

1922210 V8.5 SYSTEM FATAL MESSAGE 3007 (MCE1)


ILLEGAL INPUT TO SUBROUTINE PARTN

The workaround is to not use the AUTOMPC


functionality.
For structural analysis with thermal loading and
bubble functions, incorrect stresses are computed
1923534 V8.5
at the corner grids of CPENTA elements because a
term is omitted from the thermal strain calculation.
When running SOL 200 with PRES type DRESP1
design responses, the following error message is
issued.

SYSTEM FATAL MESSAGE 4276 (BLDPRD)


ERROR CODE 210 PID= 0
USER INFORMATION MESSAGE 4276 (BLDPRD)

1924242 V8.5 The workaround is to change all PRES type DRESP1


design responses to FRDISP type DRESP1 design
responses. PRES and FRDISP are essentially the
same.

Note

For versions of the software without the


corrective action, the sensitivities obtained
NX Nastran 9 Problem Report (PR) fixes 285

for PRES type DRESP1 design responses


may be incorrect even if no error message is
issued.
Beginning with NX Nastran 9, the SID on an
ACCEL1 entry can be the same as the SID defined
1928564 V8.5 on other ACCEL1 entries. As a result, multiple
ACCEL1 entries with the same SID are now
permitted.
When using the LP-64 executable, the following
error message is issued for a model that contains an
element that references an undefined grid:

USER FATAL MESSAGE 2007 (GP2)


1930709 V8.5 ELEMENT 51214 REFERENCES UNDEFINED
GRID POINT 426

In the error message, the grid number is truncated.

The workaround is to use the ILP-64 executable.


CTRIAR elements fail formatting check when a
seven digit MCID is used.
1933177 V8.5
The workaround is to use an MCID having six or
less digits.
For models that contain external superelements, a
1933471 V8.5 partial decomposition error occurs during SOL 103
DMP runs.
During a SOL 111 run, the SDAMPING(FLUID)
1935262 V8.5
table for the last subcase is used in all subcases.
A model containing PCOMPG bulk entries runs
on ILP64, but produces excessive pivot errors on
1935607 V8.5 LP64. The pivot errors occur because the internally
generated MAT2 bulk entries for the PCOMPG bulk
entries are corrupt.
A SOL 106 model that contains superelements
produces an unformatted I/O error because
1935909 V8.5 PARAM,POST,-2 is reset to PARAM,POST,1 when
processing the superelement data at the end of the
solution.
286 NX Nastran 9 Problem Report (PR) fixes

During a restart of a SOL 103 run, a model that


contains an external superelement issues the
following error message:

SYSTEM FATAL MESSAGE 4276 (GREAD)


1936046 V8.5 The problem occurs because the BULK data block is
stored with incorrect qualifiers.

The workaround is to use the following DMAP alter:


COMPILE PHASE0 NOLIST $
ALTER 246, 246 $
The following error message that superelement
matrices for some, but not all superelements, are
unrecoverable is issued when attempting to solve
the residual:

SYSTEM FATAL MESSAGE 4252 (SEMA)


MATRIX XAAV FOR UPSTREAM
SUPERELEMENT 12 DOES NOT EXIST.
USER INFORMATION: THE CURRENT
SUPERELEMENT REQUIRES ALL OF ITS
UPSTREAM SUPERELEMENT MATRICES
FOR ASSEMBLY INTO THE CURRENT
SUPERELEMENT. THE PROBABLE CAUSES
1937205 V8.5 ARE:
1. THE UPSTREAM SUPERELEMENTS DBSET
OR DATABASE IS NOT ATTACHED.
2. THE UPSTREAM SUPERELEMENT DID
NOT COMPLETE REDUCTION IN A PREVIOUS
RUN. USER ACTION: RERUN THE REDUCTION
OF THE UPSTREAM SUPERELEMENT
AND/OR ENSURE THAT THE DBSET AND/OR
DBLOCATED DATABASE WHICH CONTAINS
THE UPSTREAM SUPERELEMENT MATRIX IS
ATTACHED.
USER FATAL MESSAGE 9031 (ERRPH1)
NOGO ENCOUNTERED IN SUBDMAP SEMA1
The results from running a model on Linux differ
from the results obtained when running the same
1939062 V8.1 model on Windows. This occurs because when the
solution fails to converge and is subdivided by the
ATS method, an incorrect bolt preload is applied.
NX Nastran 9 Problem Report (PR) fixes 287

A valid solution is obtained for a model that contains


contact and bolts modeled with solid elements. When
a new subcase that contains mapped temperatures
results is added, the following error message is
issued:

USER FATAL MESSAGE 4016 (GETEMP)


THERE ARE NO TEMPERATURES FOR HEXA
ELEMENT 21328 IN SET 202
1940651 V8.5 0FATAL ERROR

The error is due to duplicate nodes along the bolt


cut plane definition that do not have temperatures
defined.

The workaround is to define a TEMPD temperature


set definition that defines a constant temperature
on all of the grids in the model that do not have a
mapped temperature defined.
The peak displacement component is used in AF
1941508 P9.0 normalization calculations rather than the peak
displacement resultant.
The following error message is issued when a SOL
601 run crashes:

INTERNAL ERROR: FNDLBL: IA(MSTART)


1943414 V8.5
The error occurs when the THRU option for a
PLOAD4 bulk entry is used over a large range of
elements.
When running a model that contains MODCON
functionality on NX Nastran 8.5, system
1944395 V8.5
performances is noted to be worse than when the
model is run on NX Nastran 7.1.
When running a model that contains CFAST
elements, the following error message is issued:

SYSTEM FATAL MESSAGE 7558 (EWLDPS)


AN ERROR OCCURED PROCESSING SPOT
1945145 V8.5
WELD GRID GS ID=9004272.
VERIFY THE NODAL CONNECTIVITY IS VALID.

The workaround is to use CROD elements in place


of CFAST elements.
288 NX Nastran 9 Problem Report (PR) fixes

When running a model that contains enforced


displacements and bolt preload, the following error
message is issued:

USER FATAL MESSAGE 22102 (BOLTFOR)


SPECIFIED DISPLACEMENTS (SPCD) NOT
PERMITTED IN A PRELOADED BOLT ANALYSIS
1946412 V8.5
For NX Nastran 9, bolt preload with SPCD definitions
can be solved by specifying SYSTEM(581)=1. For
earlier versions of NX Nastran, a workaround is
to use a 2 subcase approach where the global bolt
preload and contact conditions are specified and
solved in SUBCASE1, and the SPCD is applied as a
service load in SUBCASE2.
A hyper-threading issue arises because NX Nastran
does not support hyper-threading. The NX Nastran
2209019 V7.1 9 Installations and Operations Guide now states
that hyper-threading must be turned off.

The workaround is to turn off hyper-threading.


In SOL 129, damping specified using
2209314 V8.1 PARAM,ALPHA2 is not applied to CROD
elements.
2211442 V8.5 Same as PR#1922210.
The following error messages occur when running a
model that contains an external superelement and
glue that is defined in the residual.

USER FATAL MESSAGE 1126 (GNFIST)


DMAP MODULE SEDRCVR IS ATTEMPTING TO
OUTPUT DATABLOCK 284
2214629 V8.5
and

USER FATAL MESSAGE 1126 (GNFIST)


DMAP MODULE SEDRCVR IS ATTEMPTING TO
OUTPUT DATABLOCK 285

The workaround is to run the model without the


BGRESULT output request.
NX Nastran 9 Problem Report (PR) fixes 289

For the EDE, EKE, and ESE case control commands,


IFP1 sets the default values for the THRESH
variable to -1 before reading the actual value of the
2216573 V8.5 THRESH variable from the input file. The software
does this to avoid overriding the value of TINY in
GPFPCC. However, IFP1EA resets the value if it is
zero back to -1.
2217481 V8.5 Same as PR#1936046.
A deck that contains a TLOAD1 bulk entry runs
without error in NX Nastran 8.1, but issues the
following error message when run on NX Nastran
8.5.
2218744 V8.5
SYSTEM FATAL MESSAGE 2090 (TRLG)

The fatal error does not occur when the TLOAD1


bulk entry is removed from the input file.
A SOL 601,106 run of a model that contains a
hyperelastic material with the K field left blank
issues the following error message:
2218829 V8.5 USER FATAL MESSAGE 315 (IFPDRV)

In the absence of explicitly defined bulk moduli, the


software should calculate the bulk moduli from the
values in the MUi and ALPHAi fields.
A SOL 110 rotor dynamics run produces a MERGE
error because the model does not generate forward
2219958 V8.5 whirl modes.

The workaround is to add PARAM,ROTSYNC,NO to


the input file.
For modal dynamics solutions where the model
includes a virtual fluid mass, a MERGE error occurs
2220908 V8.5 when both VMOPT = 2 and MPRES are specified.

The workaround is to use VMOPT = 0 or VMOPT = 1.


For models that contain external superelements,
SECOMB output is incorrectly combined
when only 2 of the 3 output requests for
2221168 V8.5 displacement/velocity/acceleration are requested.

The workaround is either to request a single


displacement/velocity/acceleration output or to
request all three outputs.
290 NX Nastran 9 Problem Report (PR) fixes

For models that contain superelements, the rigid


body modes calculated during a SOL 103 run differ
6786238 V8.0 depending on whether the job is run on a machine
with the Windows operating system or the Linux
operating system.
Duing SOL 101 with contact, bolt preload, many load
cases, and with the following output requests:
STRESS(PLOT,CORNER) = ALL
BCRESULTS(TRACTION,FORCE,SEPDIS,PLOT) = ALL

the following fatal error message is issued:

USER FATAL MESSAGE 3005 (SDR2)


ATTEMPT TO OPERATE ON THE SINGULAR
MATRIX (NONE) IN SUBROUTINE SQD43D
6795089 V8.0
The workaround is to define a dummy temperature
condition/load. To do so, add the following syntax to
the input file.
TEMPERATURE(INITIAL)=1
.....
.....
BEGIN BULK
TEMPD 1 0.0

The use of the temperature set disables the portion


of the code where the error arises.
6804964 V8.5 Same as PR#1937205.
For SOL 601,106, a model that contains contact runs
when FRICMOD=0, but fails when FRICMOD>1.
6805114 V8.1
The workaround is to specify non-zero friction on
the BCTSET bulk entry.
For SOL 200, the sensitivities provided in MATRIX
6813661 V8.5 DELTAK in the .f06 file differ between the 32-bit
and 64-bit versions of NX Nastran.
In models that contain PLOTEL elements, the
6815156 V8.5 coordinates of grids are changed when they are
written to the .pch file.
NX Nastran ignores the specification of a logarithmic
6819021 V8.5
y-axis when using the TABLEM1 bulk entry.
NX Nastran desktop produces an incorrect checksum
when control characters are present in the bulk data
6820311 V8.5 or in files included in the bulk data.

There is no workaround except to remove the special


control characters.
NX Nastran 9 Problem Report (PR) fixes 291

SPCF and MPCF are not calculated properly because


6820362 V8.5 a displacement matrix data block from the original
solution fails to get regenerated on the restart.
6822076 P8.5 Same as PR#6820311.
For some large field bulk entries, the software
searches for a continuation line when one does not
need to be present and issues a fatal error message
6823290 V8.5 when one is not found.

The workaround is for the user to supply fields 5


through 8.
Test cases are failing because of differences in the
6823296 P9.0
minimum heat flux results.
During a SOL 200 run, the following fatal error
occurs when design variables related to PCOMP
and PCOMPG bulk entries coexist in the same data
deck, and one or more PCOMPG bulk entries have
ID numbers that are less than the ID number of the
highest numbered PCOMP bulk entry.

USER FATAL MESSAGE 7193 (DOPR1I)


6826484 P9.0
PID= 1 OF PTYPE PCOMPG ON A DVPREL1
900001 ENTRY, IS NOT DEFINED ON A
PROPERTY ENTRY.

The workaround is to renumber PCOMPG bulk


entries so that all PCOMPG ID numbers are greater
than the highest ID number for the PCOMP bulk
entries.
The runtime and memory requirement for a run
using an input file with MODCON and PANCON
case control commands is significantly greater
6833025 P8.5 than the runtime and memory requirement for
a run where the MODCON and PANCON case
control commands are replaced with an essentially
equivalent FLSPOUT case control command.
Execution time in the SDR2 module is extremely
long because merging the SDR2B, SDR2D, and
6833031 P8.5 SDR2E routines into a single routine, SDR2BDE,
eliminated the reduction in size of the element
summary table before phase II of the SDR2 module.
For SOL 601, a fatal error is issued when the
LIMIT1 field on the MATS1 bulk entry is left blank
6833533 V8.0
even though a TABLES1 bulk entry is referenced in
the TID field.
292 NX Nastran 9 Problem Report (PR) fixes

During a run, NX Nastran 8.5 erroneously issues the


following error message.

USER FATAL MESSAGE 4692 (DPD)


NO RANDPS BULK DATA ENTRY REFERENCED
6835330 P8.5
BY CASE CONTROL RANDOM 77566

The error message is wrong because RANDPS 77566


is present. The error message is not issued when the
input file is run in NX Nastran 8.1.
When using double-precision (LP) machines, there
are differences between the input and punch file
6836395 V8.1
output generated by the EXTSEOUT case control
command for grids and coordinate systems.
UFM 2089 in ROTSDB is issued during a run where
6856145 P9.0 the input file contains PBEAR bulk entries with
damping terms referencing tables.
The presence of RANDPS bulk entries prevents
6857515 V8.5 frequency response output unless System Cell 524
(RANFRF = 1) is set.
Different results are produced when a model is run
using SOL 601/129 versus SOL 129. The difference
6860567 V8.5 occurs because the direction of forces defined with
FORCE1 bulk entries are reversed during the SOL
601/129 run.
6860834 V8.5 Same as PR#1935607.
SOL 112 produces incorrect results because the code
fails to account for non-unity modal mass during the
6861669 V8.1
conversion from physical initial conditions to modal
initial conditions.
For SOL 108 and SOL 111, equivalent radiated
power (ERP) results are incorrect when a PANEL
is defined using the GRID option on the SET3 bulk
6862671 V8.5 entry.

The workaround is to use the ELEM or PROP


options on the SET3 bulk entry to define the PANEL.
NX Nastran 9 Problem Report (PR) fixes 293

When the DRSPAN case control command and the


DCONADD bulk entry both appear in the same SOL
200 input file, a significant number of constraints
are deactivated in error, leading to incorrect results
for the SOL 200 run.
6873727 V8.5
The workaround is not to use the DCONADD bulk
entry when there is DRSPAN case control command,
and to number all DCONSTR constraints of a
subcase with the same ID as the DESSUB case
control command for that subcase.
The .op2 file does not contain force and stress results
6876969 V8.5 for CBUSH elements that can be imported into a
post-processor.
During a SOL 103 run, the modes are computed, but
6879086 V8.5
the run fails while preparing the ADAMS MNF file.
For SOL 200, the output of random analysis results,
other than those for displacements, velocities, and
accelerations, does not occur after the initial cycle.

6881165 P9.0 The workaround is to restart the SOL 200 job at


the desired cycle, using the modified design for that
cycle. Because the initial analysis of a restart run is
not affected by the output issue, the complete output
will be obtained for that initial cycle.
A SOL 200 run fatals out when a relative enforced
motion subcase (system422=0) is accompanied by
other type(s) of analysis subcase(s) in the same input
6886137 P9.0 file.

The workaround is to modify the relative enforced


motion subcase into an absolute enforced motion
subcase (system422=1).
The following error message is issued when running
a RDMODES job with enforced motion.

USER FATAL MESSAGE 3046


THIS FREQUENCY RESPONSE ANALYSIS HAS
NO EXCITATION SPECIFIED FOR IT.
6888169 P9.0 APPLIED LOADS AND ENFORCED MOTION ARE
BOTH NULL.
THE RESULT WILL THEREFORE BE A ZERO
SOLUTION.

The workaround is to add the NOINRL describer to


the RESVEC case control command.
294 NX Nastran 9 Problem Report (PR) fixes

The following error messages are issued when


running RDMODES on disjoint structures (two
unconnected structures - both structures are
free-free).

USER FATAL MESSAGE 5006 (APPEND)


6888182 P9.0
INPUT FILES HAVE DIFFERENT RECORD
TYPES
SYSTEM FATAL MESSAGE 3007 (APPEND)
ILLEGAL INPUT TO SUBROUTINE APPEND

The workaround is to perform a Lanczos run.


The following error message is issued during a DMP
eigensolution.

USER FATAL MESSAGE 3047 (GKAM)


6888185 P9.0 NO MODES WITHIN RANGE AND LMODES = 0.
A MODAL FORMULATION CANNOT BE MADE

The error arises because slave nodes fatal during a


bogus eigensolution with DMP eigensolvers.
RDMODES does not work for jobs that contain a
large number of RBE3 connections. For such jobs,
6888190 P9.0
RDMODES reverts to the Lanczos eigensolution
method.
When a model contains a PSOLID bulk entry that
6894605 V8.5 references a MATHE bulk entry, the software fails to
issue an error message.
A base input response analysis runs without
completion due to an infinite loop in the SMPYAD
module.

6895033 P9.0 The workaround is to use the following DMAP alter:


COMPILE SPMPYAD NOLIST $
ALTER 38,38 $
MPYAD MA,B,/MABT/ $
MERGE ,,MABT,,,,PVA/MD/1 $

A SOL 111 run with PARAM,DDRMM,-1 fails in the


6896672 P9.0
DISPRS subdmap while calling SMPYAD.
NX Nastran 9 Problem Report (PR) fixes 295

For SOL 103 with an EXTSEOUT case control


command present, if SPOINT/QSET DOF are not
present, Guyan reduction is performed instead of
component mode synthesis. The Guyan reduction
6896889 V8.1
only uses the ASET DOF specified in the input
file. If BSET/BNDFIX DOF are specified, they are
ignored and the entire model becomes the ASET for
the reduction.
Non-ASCII characters appear in the .f04 file because
multiple files open in a loop require additional
6899626 P9.0 buffers that are not normally needed. The extra
buffers prevent the memory overwrites that cause
the non-ASCII characters.
A SOL 200 job, with glue and different boundary
conditions across multiple static analysis subcases,
fails when the program automatically chooses the
adjoint load method for sensitivity analysis. The
following error message is issued:

USER FATAL MESSAGE 9144 (FEA)


THE ADJOINT SOLUTION FOR THE RESIDUAL
6910828 P9.0
STRUCTURE AND THE CURRENT SUBCASE
DOES NOT EXIST

A workaround may be to add a large number of


non-trivial displacement constraints for this type of
problem. This triggers the program to automatically
choose the pseudo-load type of sensitivity analysis
for the displacement constraints.
Other Fixes
The various formats of the MATFT bulk entry have
either two or three continuation lines. The third
continuation line is typically used to enter allowable
transverse shear stresses and strains. If the third
continuation is omitted, NX Nastran considers only
in-plane stresses and strains in the assessment of
N/A V8.0
lamina failure. Although NX Nastran calculates
the correct results for such a situation, omitting the
third continuation line can result in erroneous data
being written to the MPT data block. When read by
post-processors, the erroneous data in the MPT data
block can cause the post-processor to crash.
Chapter

13 System description summary

System description summary


The list of supported systems is included in the README.txt file located in the NX
Nastran installation under the nxn9 directory.

You might also like