Professional Documents
Culture Documents
Guide
Contents
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
Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-83
Equivalent Radiated Power as Design Response . . . . . . . . . . . . . . . . . . . 5-83
DRESP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-87
Expanding optimization for larger problems . . . . . . . . . . . . . . . . . . . . . . 5-98
Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-107
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
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.
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 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
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
SHFSCL Estimate of the first flexible mode natural frequency. See Remark
10. (Real or blank)
Field Contents
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,
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.
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.
Table 2-1. Number and Type of Roots Found with EIGRL Entry
Table 2-1. Number and Type of Roots Found with EIGRL Entry
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.
12. NASTRAN SYSTEM(146) provides options for I/O in sparse method only:
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
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.
(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
Example:
EIGR 13 LAN 12
Fields:
Field Contents
Modern Methods:
Obsolete Methods:
Field Contents
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)
Table 2-4. Relationship Between METHOD Field and Other Fields for
Obsolete Methods
METHOD Field
Field
INV or SINV GIV, MGIV, HOU, or MHOU
Remarks:
1. The EIGR entry must be selected with the Case Control command METHOD =
SID.
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.
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.
Stress resultants, which are requested with the FORCE case control
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
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
Z0 Distance from the reference plane to the bottom surface. See Remark
14. (Real; Default = -0.5 times the element thickness.)
Field Contents
GE Damping coefficient. See Remark 6 and Remark 16. (Real; Default = 0.0)
Blank All plies must be specified and all stiffness terms are
developed.
BEND All plies must be specified, but only bending terms (MID2
on the derived PSHELL entry) are computed.
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.)
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.
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
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.
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.
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.
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.
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.
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.
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.
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:
Fields:
Field Contents
Z0 Distance from the reference plane to the bottom surface. See Remark
14. (Real; Default = -0.5 times the element thickness.)
Field Contents
Blank All plies must be specified and all stiffness terms are
developed.
BEND All plies must be specified, but only bending terms (MID2
on the derived PSHELL entry) are computed.
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.
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.)
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
and
36 Relative motion datablock
The root-mean-square value for von Mises stress in frequency domain, PRMS, is
given by
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
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.
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 111, 112, 118, 146, and 200 (ANALYSIS=MODES, MCEIG, MTRAN,
or MFREQ), the default is RESVEC=YES.
For additional information, see the updated RESVEC case control command.
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
Examples:
RESVEC = SYSTEM
RESVEC(NOINRL) = COMPONENT
RESVEC = YES
Describers:
Describer Meaning
Describer Meaning
INRLOD Compute residual vectors for inertia relief load. See Remark
4. (Default)
The defaults for the following describers are solution dependent. The defaults
apply even when the RESVEC case control entry is undefined. See Remark 10.
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.)
Remarks:
1. If the RESVEC case control command is present, the parameters RESVEC and
RESVINER are ignored.
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.
7. If a CBUSHi, CDAMPi, CELASi, and CVISC element is grounded, the unit load
is applied to only the ungrounded end.
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
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,
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
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
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
The pitch and yaw loads will produce the gyroscopic forces at
the grid points included on the rotors.
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
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.
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
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.
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
$...
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
$...
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
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
....
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)
Field Contents
RUNIT Units used for rotor speed inputs (CMOUT, RSTART and RSTEP)
and output (units for output list and Campbell diagram output).
(Character; Default = RPM)
Field Contents
ORBEPS Threshold value for detection of whirl direction. (Real > 0.0;
Default = 1.E-6)
= 0 no print.
= 3 combination of 1 & 2.
= 1 synchronous
= 0 asynchronous
Field Contents
RIDi Identification number of rotor i. (Integer > 0 with RIDi+1 > RIDi;
Default = i)
RSPEEDi Multiplier of reference rotor speed for rotor i. See Remark 12.
(Real 0.0 or Integer > 0 or blank; Default = 1.0)
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.
3. The Steiners term option (ZSTEIN) should only be used when analyzing solid
models in the fixed system.
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.
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
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
Remarks:
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
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
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)
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:
NOMVAL Valid if TYPE = KD, KF, BD, BF. Field is ignored if TYPE =
K, B. See Remark 6. (Real 0.0)
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
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.
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.
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
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
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
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.
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.
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
-etc-
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
The 3rd row has an end time of 100.0, 2 increments, and output at all time steps.
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
When Tend1=0.0,
o No other times are allowed. This is the only time for the associated
subcase.
Nouti controls the frequency of results output. The table below summarizes
the input options.
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
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.
o TABLEDi (i=1,2,3,4) - Table that defines the load variation with time.
o The supported static loads types are DAREA, FORCE, FORCE1, FORCE2,
GRAV, PLOAD, PLOAD4, RFORCE, RFORCE1 (New), and SLOAD.
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 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.
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.
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.
The new OTEMP case control command can be included to request solution
temperature output.
New multi-step nonlinear solution 401 75
The PSOLID or the PCOMPS bulk entries define the element properties. The
PCOMPS is optionally used to define a layered solid composite property.
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.
Supported Output
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
Name Description
THRMST Controls the loading due to thermal strain in a static analysis (Character;
Default=YES)
YES
NO
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
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)
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.
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
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
5 Optimization
ERP density on a panel, where density is the total magnitude divided by the
normal surface area of the panel.
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.
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
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.
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.
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
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
Fields:
Field Contents
Field Contents
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.
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 .
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 .
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
Stress limits in the ST, SC, and SS fields on all MATi entries.
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.
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
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.
EIGN No region
FREQ No region
LAMA No region
VOLUME No region
WEIGHT No region
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.
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.
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.
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:
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.
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.
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.
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.
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
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.
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
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
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.
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-
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.
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
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.
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.
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.
7 Element enhancements
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
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
...
...
$* 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
...
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
Describer Meaning
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.
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).
Describer Meaning
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.
Remarks:
4. If ASMBULK is specified, the following bulk entries are generated and stored on
the assembly punch file (.asm):
SEBULK seid
SECONCT seid
EXTRN
ASET/ASET1
QSET/QSET1
SPOINT
PLOTEL
7. If DMIGPCH is specified, the following bulk entries are generated and stored on
the standard punch file (.pch):
BEGIN SUPER seid
ASET/ASET1
SPOINT
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)
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)
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.
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 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.
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.
If both LOADSET and LOAD appear in the case control, LOADSET takes
precedence.
118 EXTSEOUT
External Superelement Creation Specification
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.
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
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
General Remarks:
Describer Meaning
Describer Meaning
NONE No specific sets are selected, thus all grids, geometry and
associated modal data are written to RFI. (default)
ALL The connectivity of all element sets are used to export face
geometry.
Describer Meaning
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.
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
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
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.
sp = [xyz]T are the coordinates of grid point p in the basic coordinate system.
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.
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.
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.
Typical Parameters:
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.
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.
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.
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.
Describer Meaning
Describer Meaning
ALL The connectivity of all element sets are used to export face
geometry.
Describer Meaning
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
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
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.
sp = [xyz]T are the coordinates of grid point p in the basic coordinate system.
Ip = inertia tensor p.
fp* = partitioned orthogonal modal matrix that corresponds to the rotational
degrees of freedom of grid p.
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.
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.
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
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
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
Typical Parameters:
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
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
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.
Describer Meaning
NONE All grids, geometry and associated modal data is written to the
FBI file. (default)
ALL The connectivity of all element sets are used to export geometry
and associated model data.
Describer Meaning
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
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
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.
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.
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.
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
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.
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.
Describer Meaning
OP4 Remarks:
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
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
MATLAB Describers:
Describer Meaning
Describer Meaning
MATLAB Remarks:
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
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.
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.
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:
See the Parallel Processing Guide for information on all parallel options.
Chapter
11 Upward compatibility
CASECC
DIT
5 UNDEF(4) None
4 UNDEF(5) None
5 UNDEF(4) None
3 UNDEF(6) None
DSCMCOL
7 FREQUENCY RS Frequency
8 UNDEF None
DYNAMIC
5 UNDEF(6) None
8 UNDEF None
10 UNDEF(12) None
28 UNDEF None
Updated data blocks 167
30 UNDEF(11) None
EDOM
FLAG = 19 ERP
5 UNDEF(2) None
EDT
FLAG = 3
168 Updated data blocks
1 = element
2 = grid
3 = property
170 Updated data blocks
GEOM3
GEOM4
MPT
2 E RS Youngs modulus
3 NU RS Poissons ratio
12 UNDEF(5) None
4 EP RS Hardening modulus
5 UNDEF(4) None
6 UNDEF(3) None
4 UNDEF(5) None
OEF
2 FX RS Force x
3 FY RS Force y
4 FZ RS Force z
OES
19 UNDEF(32) None
ELTYPE = 300 through 307 are added to the OES data block.
SCODE,6=0 Strain
TCODE,7=0 Real
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
SCODE,6=1 Stress
TCODE,7=0 Real
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
End SCODE,6
SCODE,6=0 Strain
TCODE,7=0 Real
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
SCODE,6=1 Stress
TCODE,7=0 Real
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
End SCODE,6
SCODE,6=0 Strain
TCODE,7=0 Real
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
SCODE,6=1 Stress
TCODE,7=0 Real
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
End SCODE,6
SCODE,6=0 Strain
TCODE,7=0 Real
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
SCODE,6=1 Stress
TCODE,7=0 Real
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
End SCODE,6
1 I
PLY Lamina number
SCODE,6=0 Strain
For each fiber location requested (PLSLOC), words 3 through 10 repeat 4 times.
182 Updated data blocks
SCODE,6=1 Stress
For each fiber location requested (PLSLOC), words 3 through 10 repeat 4 times.
End SCODE,6
1 I
PLY Lamina number
SCODE,6=0 Strain
For each fiber location requested (PLSLOC), words 3 through 10 repeat 3 times.
SCODE,6=1 Stress
For each fiber location requested (PLSLOC), words 3 through 10 repeat 3 times.
End SCODE,6
1 I
PLY Lamina number
SCODE,6=0 Strain
For each fiber location requested (PLSLOC), words 3 through 10 repeat 4 times.
SCODE,6=1 Stress
For each fiber location requested (PLSLOC), words 3 through 10 repeat 4 times.
End SCODE,6
1 I
PLY Lamina number
Updated data blocks 185
SCODE,6=0 Strain
For each fiber location requested (PLSLOC), words 3 through 10 repeat 3 times.
SCODE,6=1 Stress
For each fiber location requested (PLSLOC), words 3 through 10 repeat 3 times.
End SCODE,6
186 Updated data blocks
R1TAB
9 UNDEF None
11 FREQ RS Frequency
12 UNDEF None
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
Record IDENT
TCODE,1 = 1 Sort 1
ACODE,4 = 05 Frequency
5 FREQ RS Frequency
6 UNDEF None
End ACODE,4
TCODE,1 = 02 Sort 2
6 UNDEF(2) None
End TCODE,1
19 UNDEF(32) None
Record DATA
TCODE,1 =1
ACODE,4 =05
1 FREQ RS Frequency
End ACODE,4
End ACODE/10
2 UNDEF none
TCODE,7 =2 Real
2 AS RS Axial Stress
3 TS RS Torsional Stress
End TCODE,7
TCODE,7=1 Real/Imaginary
3 SD RS Station Distance/Length
TCODE,7 =2 Real
3 SD RS Station Distance/Length
End
TCODE,7
TCODE,7 =2 Real
2 AS RS Axial Stress
3 TS RS Torsional Stress
End TCODE,7
TCODE,7 =2 Real
End TCODE,7
2 UNDEF None
2 UNDEF None
192 New data blocks
2 UNDEF None
2 UNDEF None
2 UNDEF None
TCODE,7 =2 Real
2 AS RS Axial Stress
3 TS RS Torsional Stress
End TCODE,7
TCODE,7 =0 Real
2 S RS Stress
2 SR RS Stress
New data blocks 193
3 SI RS Stress
End TCODE,7
TCODE,7 =2 Real
2 S RS Stress
TCODE,7 =1 Real/Imaginary
2 SR RS Stress
3 SI RS Stress
End TCODE,7
TCODE,7 =2 Real
2 S RS Stress
TCODE,7 =1
2 SR RS Stress
3 SI RS Stress
End TCODE,7
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
4 TAUR RS Torque
New data blocks 195
5 TAUI RS Torque
TCODE,7 =2 Real
2 AS RS Axial Stress
3 TAU RS Torque
End TCODE,7
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
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
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
TCODE,7 =2 Real
New data blocks 197
3 SX1 RS Normal in x at Z1
4 SY1 RS Normal in y at Z1
5 TXY1 RS Shear in xy at Z1
8 SX2 RS Normal in x at Z2
9 SY2 RS Normal in y at Z2
10 TXY2 RS Shear in xy at Z2
End TCODE,7
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
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
2 UNDEF None
New data blocks 199
2 UNDEF None
2 UNDEF None
2 UNDEF None
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
13 SXI RS Normal in x
14 SYI RS Normal in y
15 SZI RS Normal in z
200 New data blocks
16 TXYI RS Shear in xy
17 TYZI RS Shear in yz
18 TZXI RS Shear in zx
TCODE,7 =2 Real
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
End TCODE,7
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
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
TCODE,7 =2 Real
2 RA RS Radial Axis
3 AA RS Axial Axis
4 TE RS Tangential Edge
5 CE RS Circumferential Edge
End TCODE,7
TCODE,7 =2 Real
2 RC RS Radial centroid
3 CC RS Circumferential centroid
4 AC RS Axial centroid
End TCODE,7
TCODE,7 =2 Real
2 RC RS Radial centroid
3 CC RS Circumferential centroid
4 AC RS Axial centroid
End TCODE,7
206 New data blocks
TCODE,7 =2 Real
2 RC RS Radial centroid
3 AC RS Axial centroid
End TCODE,7
TCODE,7 =2 Real
2 RC RS Radial centroid
New data blocks 207
3 AC RS Axial centroid
End TCODE,7
2 UNDEF None
TCODE,7 =2 Real
3 SX RS Normal stress in X
4 SY RS Normal stress in Y
5 SZ RS Normal stress in Z
9 OCTS RS Octahedral
New data blocks 209
End TCODE,7
2 UNDEF None
TCODE,7 =2 Real
End TCODE,7
TCODE,7 =2 Real
End TCODE,7
TCODE,7 =2 Real
End TCODE,7
TCODE,7 =2 Real
End TCODE,7
TCODE,7 =2 Real
End TCODE,7
2 UNDEF none
New data blocks 211
2 UNDEF none
2 UNDEF None
2 UNDEF None
2 TERM CHAR4
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
14 SX2R RS Normal in x at Z2
212 New data blocks
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
TCODE,7 =2 Real
5 EX1 RS Normal in x at Z1
6 EY1 RS Normal in y at Z1
7 ETXY1 RS Shear in xy at Z1
10 EX2 RS Normal in x at Z2
11 EY2 RS Normal in y at Z2
12 ETXY2 RS Shear in xy at Z2
End TCODE,7
2 UNDEF None
2 UNDEF None
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
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
17 TYZI RS Shear in yz
18 TZXI RS Shear in zx
TCODE,7 =2 Real
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
End TCODE,7
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
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
TCODE,7 =2 Real
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
End TCODE,7
3 CA RS Circumferential Angle
TCODE,7 =2 Real
3 CA RS Circumferential Angle
End TCODE,7
2 TERM CHAR4
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
9 TXY1R RS Shear in xy at Z1
10 TXY1I RS Shear in xy 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
TCODE,7 =2 Real
2 TERM CHAR4
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
10 SX2 RS Normal in x at Z2
11 SY2 RS Normal in y at Z2
12 TXY2 RS Shear in xy at Z2
End TCODE,7
2 UNDEF None
2 UNDEF None
2 UNDEF None
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
8 TXY1I RS Shear in xy at Z1
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
TCODE,7 =2 Real
3 SX1 RS Normal in x at Z1
4 SY1 RS Normal in y at Z1
5 TXY1 RS Shear in xy at Z1
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
End TCODE,7
2 TERM CHAR4
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
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
TCODE,7 =2 Real
2 TERM CHAR4
5 SX1 RS Normal in x at Z1
6 SY1 RS Normal in y at Z1
7 TXY1 RS Shear in xy at Z1
10 SX2 RS Normal in x at Z2
11 SY2 RS Normal in y at Z2
12 TXY2 RS Shear in xy at Z2
End TCODE,7
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 TERM CHAR4
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
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
TCODE,7 =2 Real
2 TERM CHAR4
5 SX1 RS Normal in x at Z1
6 SY1 RS Normal in y at Z1
7 TXY1 RS Shear in xy at Z1
10 SX2 RS Normal in x at Z2
New data blocks 225
11 SY2 RS Normal in y at Z2
12 TXY2 RS Shear in xy at Z2
End TCODE,7
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
226 New data blocks
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
TCODE,7 =2 Real
7 AS RS Axial stress
228 New data blocks
End TCODE,7
TCODE,7 =2 Real
2 IMPED RS Impedance
2 IMPEDR RS Impedance
3 IMPEDI RS Impedance
End TCODE,7
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
2 TXR RS Translation x R
New data blocks 229
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
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
230 New data blocks
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
232 New data blocks
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 TERM CHAR4
3 GRID I
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
8 SY1I RS Normal in y at z1
9 TXY1R RS Shear in xy at z1
10 TXY1I RS Shear in xy 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
TCODE,7 =2 Real
2 TERM CHAR4
3 GRID I
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
10 SX2 RS Normal in x at z2
11 SY2 RS Normal in y at z2
12 TXY2 RS Shear in xy at z2
End TCODE,7
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
236 New data blocks
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
New data blocks 237
2 UNDEF None
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
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
TCODE,7 =2 Real
2 UNDEF None
End TCODE,7
New data blocks 239
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
New data blocks 241
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
242 New data blocks
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
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
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
TCODE,7 =2 Real
3 SX1 RS Normal in x at Z1
4 SY1 RS Normal in y at Z1
244 New data blocks
5 TXY1 RS Shear in xy at Z1
8 SX2 RS Normal in x at Z2
9 SY2 RS Normal in y at Z2
10 TXY2 RS Shear in xy at Z2
End TCODE,7
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
12 SX2R RS Normal in x at Z2
13 SX2I RS Normal in x at Z2
New data blocks 245
14 SY2R RS Normal in y at Z2
15 SY2I RS Normal in y at Z2
16 TXY2R RS Shear in xy at Z2
TCODE,7 =2 Real
3 SX1 RS Normal in x at Z1
4 SY1 RS Normal in y at Z1
5 TXY1 RS Shear in xy at Z1
8 SX2 RS Normal in x at Z2
9 SY2 RS Normal in y at Z2
10 TXY2 RS Shear in xy at Z2
End TCODE,7
2 UNDEF None
2 UNDEF None
246 New data blocks
2 UNDEF None
2 UNDEF None
TCODE,7 =2 Real
New data blocks 247
4 SX RS Normal stress in X
5 SY RS Normal stress in Y
6 SZ RS Normal stress in Z
End TCODE,7
TCODE,7 =2 Real
3 SX RS Normal stress in X
4 SY RS Normal stress in Y
5 SZ RS Normal stress in Z
End TCODE,7
TCODE,7 =2 Real
3 SX RS Normal stress in X
4 SY RS Normal stress in Y
5 SZ RS Normal stress in Z
End TCODE,7
TCODE,7 =2 Real
3 SX RS Normal stress in X
4 SY RS Normal stress in Y
5 SZ RS Normal stress in Z
End TCODE,7
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
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
TCODE,7 =2 Real
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
End TCODE,7
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
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
End TCODE,7
TCODE,7=2 Real
4 SX RS Normal stress in x
5 SY RS Normal stress in y
6 SZ RS Normal stress in z
End TCODE,7
TCODE,7=2 Real
4 SX RS Normal stress in x
5 SY RS Normal stress in y
6 SZ RS Normal stress in z
End TCODE,7
TCODE,7=2 Real
4 SX RS Normal stress in x
5 SY RS Normal stress in y
6 SZ RS Normal stress in z
End TCODE,7
New data blocks 259
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
End TCODE,7
TCODE,7=2 Real
4 SX RS Normal stress in x
5 SY RS Normal stress in y
6 SZ RS Normal stress in z
End TCODE,7
New data blocks 261
TCODE,7=2 Real
4 SX RS Normal stress in x
5 SY RS Normal stress in y
6 SZ RS Normal stress in z
End TCODE,7
TCODE,7=2 Real
4 SX RS Normal stress in x
5 SY RS Normal stress in y
6 SZ RS Normal stress in z
End TCODE,7
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
264 New data blocks
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
2 UNDEF None
End ELTYPE
Record TRAILER
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
Record IDENT
3 UNDEF None
6 UNDEF(3) None
11 UNDEF(40) None
Record DATA
Record TRAILER
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 $
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 $
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 $
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 $
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:
MODGM2B
Updated Format:
MODGM2B CASECC,MPT,EPT,GEOM1,GEOM2,GEOM4,CONTACT,EDT,IGEOM3/
MGEOM1,MGEOM2,MGEOM4,MCONTACT,SBDATA,MGEOM3/
BOLTFACT/S,N,IBTEX $
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:
PANELERP
Updated Format:
PANELERP CASEG,BGPDTS,CSTMS,ECTS,EDTS,FOLX,UGCASE/OERP,OERPEL1,ERPFIL $
RSVECEL
Updated Format:
RSVECEL ECT,GEOM4,BGPDT,CSTM,EPT/
RVELG/
NOGSET/OPTION $
New Parameter:
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
XYTRAN
Removed Parameters:
New modules
CHKPNL
Checks Bulk Data PANEL input against ERP requests in Case Control.
Format:
CHKPNL CASECC,EDT//S,N,NOGO $
EDT Table of a subset of Bulk Data entries that also includes PANEL
entries
None
Parameters:
DLT2SLT
Generates static loads from the dynamic load values at a given time.
Format:
DLT2SLT DLT,SLT,DIT,EST/NEWSLT/DTIME/CASEDLOD $
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
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 $
Parameters:
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 $
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.
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
BDDL Damping matrix for the d-set for linear elements only
IFDH Matrix of nonlinear element forces in the d-set at the output time
steps
PNLH Nonlinear load matrix appended from each output time step
Parameters:
On input:
0 Initialization
On output:
1 Gimbal angle
2 Rotation vector
UPGLSTF
Creates/updates glue stiffness in SOL 401.
282 New modules
Format:
UPGLSTF GNELM,BGPDT,CSTM,UGVBAS/ELGNST/NLHEAT/NROW $
Parameters:
Problem
PR# Problem Description
Reported
During a nonlinear buckling solve, the following
fatal error occurs because a scratch data block is not
saved.
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
Note