nx nastran 12 release guide - siemens€¦ · release guide. contents proprietary ......

SIEMENSSIEMENSSIEMENS

NX Nastran 12Release Guide

Contents

Proprietary & Restricted Rights Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

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

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

Dynamics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Support for Simcenter Motion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Random analysis control enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27Random analysis output enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30RESVALT parameter removed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30Direct-input, frequency-dependent components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30Output transformation matrices for frequency response analysis . . . . . . . . . . . . . . . . . . . . . 2-44

Acoustics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Finite Element Method Adaptive Order (FEMAO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Acoustics case control command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Monopole, dipole, and plane wave acoustic sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12Enforced acoustic pressure with complex data input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22Boundary conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25Acoustic materials with complex properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35Acoustic pressure results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37Support for random acoustic analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46Incident and transmitted acoustic power and acoustic power transmission loss results output . . 3-47Usability improvement for panel and grid contributions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59Acoustic transfer vectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65Output format for acoustic intensity and acoustic velocity results . . . . . . . . . . . . . . . . . . . . . 3-69

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

Frequency-dependent external superelements for frequency response analysis . . . . . . . . . . . . 4-1PVT0 data block in superelement OP2 files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

Multi-step nonlinear solution 401 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Shell element support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Bar and beam element support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Spring and bushing element support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5Nonlinear buckling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Bolt preload improvements for SOL 401 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23Balanced initial stress-strain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30Contact improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42Stress output coordinate system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43Progressive failure analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44

NX Nastran 12 Release Guide 3

Contents

User defined material improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58

Multi-step nonlinear kinematics solution 402 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Multi-step nonlinear kinematics SOL 402 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Fourier harmonic solution in SOL 402 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14Cyclic symmetric in SOL 402 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16SOL 402 vs SOL 401 comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17SOL 402 .f06 results file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18Linearized buckling solution in SOL 402 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20

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

Performance improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Bolt preload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Bolt preload improvements for linear solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Memory allocation for external applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Memory allocation for external applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Topology Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Topology Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Monitor points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Monitor points for element results and grid point forces . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1Monitor points example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-32

Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

HDF5 format output files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1Visualization elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2Separate mechanical and thermal strain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11Modal stress calculation when TEMPERATURE(LOAD) is specified . . . . . . . . . . . . . . . . . . 12-12P-elements in SOL 200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12

Documentation changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Removing documentation for legacy acoustic absorber and barrier elements . . . . . . . . . . . . . 13-1Removing documentation for the legacy VECTOR case control command . . . . . . . . . . . . . . 13-1

Upward compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Updated data blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1CASECC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1CONTACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-5DIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7DSCMCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8DYNAMIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8EDOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-15EDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-21

4 NX Nastran 12 Release Guide

Contents

Contents

ELRSCALV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-22EPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-23EPT705 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-25GEOM1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-26GEOM2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-27GEOM3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-30GEOM4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-35LAMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-35MPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-36OACCQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-40OACINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-41OACPWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-42OACVELO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-43OBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-44OBOLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-46OBG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-47OCKGAP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-47ODAMGCZD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-48ODAMGCZR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-49ODAMGCZT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-51ODAMGPFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-52ODAMGPFE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-55ODAMGPFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-56OEE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-57OEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-58OERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-84OES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-84OGF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-140OJINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-148OPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-149OPRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-149OQG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-150OSHT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-153OSLIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-154OSPDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-154OTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-156OUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-156OUGGC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-157OUGPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-157OUGRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-158OUMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-158R1TAB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-161

New data blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-161ATVMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-161OACPWRI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-162OACPWRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-164OACTRLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-166OBCKL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-167OCONST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-168


Contents

Contents

ODAMGPFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-172OEFMXORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-174ONMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-175TRMBD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-177TRMBU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-178

Updated modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-180ADDVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-180BOLTFOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-180CNTMAPTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-181CNTSTAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-181CONSTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-182CONTOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-182DOM9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-183DOM10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-183DOM12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-184DOPR1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-185DPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-187ELTPRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-187EMAAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-188EMG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-188FOCOEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-188FONOTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-189FRRD1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-189GP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-189GP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-190GPAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-190GPFDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-190IFP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-191INITSNCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-191LAMX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-191MATMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-192MODACC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-199MODUSETF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-199MPPARV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-199MPPOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-200MPPRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-200NLTRD3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-201OUTPRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-203RANDOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-207SDR2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-208SELA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-209SEMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-210SSG1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-210TA1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-210TRLG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-211UPGLSTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-211XSELOADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-211XYTRAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-212

New modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-213


Contents

Contents

ACPRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-213ATVGP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-213ATVPARTV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-214ATVPOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-215DAYTIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-216DOM13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-216DPDAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-217DSADJC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-218EULAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-218FEMAOAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-219FEMAOPRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-221FEMAOPST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-223FFREST1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-224FFREST2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-225FFREST3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-225FRFIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-226FRLGAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-230FTCHGM2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-231GPACAO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-232MFRQADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-233MODEQEXN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-234MODGMATV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-234MONEGRP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-236MONPNT2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-237MONVEC3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-237MPP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-238TOTLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-239TRLOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-240TRLPSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-241

Problem Report (PR) fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Problem Report (PR) fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1


Contents

Proprietary & Restricted Rights Notice

© 2017 Siemens Product Lifecycle Management Software Inc. All Rights Reserved.

This software and related documentation are proprietary to Siemens Product Lifecycle ManagementSoftware Inc. Siemens and the Siemens logo are registered trademarks of Siemens AG. Simcenter isa trademark or registered trademark of Siemens Product Lifecycle Management Software Inc. or itssubsidiaries in the United States and in other countries.

NASTRAN is a registered trademark of the National Aeronautics and Space Administration. NXNastran is an enhanced proprietary version developed and maintained by Siemens Product LifecycleManagement Software Inc.

MSC is a registered trademark of MSC.Software Corporation. MSC.Nastran and MSC.Patran aretrademarks 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-AvivUniversity, [email protected]. All Rights Reserved.

TAUCS License:

Your use or distribution of TAUCS or any derivative code implies that you agree to this License.

THIS MATERIAL IS PROVIDED AS IS, WITH ABSOLUTELY NO WARRANTY EXPRESSED ORIMPLIED. 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 codethat 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, thentyping "help taucs" must cite the Copyright, and "type taucs" must also cite this License and theAvailability note. Permission to modify the code and to distribute modified code is granted, providedthe Copyright, this License, and the Availability note are retained, and a notice that the code wasmodified is included. This software is provided to you free of charge.

Availability (TAUCS)

As of version 2.1, we distribute the code in 4 formats: zip and tarred-gzipped (tgz), with or withoutbinaries for external libraries. The bundled external libraries should allow you to build the testprograms on Linux, Windows, and MacOS X without installing additional software. We recommendthat you download the full distributions, and then perhaps replace the bundled libraries by higherperformance ones (e.g., with a BLAS library that is specifically optimized for your machine). If youwant to conserve bandwidth and you want to install the required libraries yourself, download thelean 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 tarzxvpf), otherwise you will have to change its permissions manually.



HDF5 (Hierarchical Data Format 5) Software Library and Utilities Copyright 2006-2016 byThe HDF Group

NCSA HDF5 (Hierarchical Data Format 5) Software Library and Utilities Copyright 1998-2006 by theBoard of Trustees of the University of Illinois. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted for anypurpose (including commercial purposes) provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions,and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions,and the following disclaimer in the documentation and/or materials provided with the distribution.

3. In addition, redistributions of modified forms of the source or binary code must carry prominentnotices stating that the original code was changed and the date of the change.

4. All publications or advertising materials mentioning features or use of this software are asked,but not required, to acknowledge that it was developed by The HDF Group and by the NationalCenter for Supercomputing Applications at the University of Illinois at Urbana-Champaign andcredit the contributors.

5. Neither the name of The HDF Group, the name of the University, nor the name of any Contributormay be used to endorse or promote products derived from this software without specific priorwritten permission from The HDF Group, the University, or the Contributor, respectively.

DISCLAIMER: THIS SOFTWARE IS PROVIDED BY THE HDF GROUP AND THE CONTRIBUTORS"AS IS" WITH NO WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED.

In no event shall The HDF Group or the Contributors be liable for any damages suffered by the usersarising out of the use of this software, even if advised of the possibility of such damage



Chapter 1: NX Nastran 12 summary of changes

NX Nastran 12 summary of changes to default settings and inputs

Default setting changes

Note

The following table lists changes to default settings that may produce differences inresults between NX Nastran 11 and NX Nastran 12. Default setting changes that produceadditional output only are not included in this table.

Input type Default changeKeywords NoneNastran statement NoneFile managementstatements NoneExecutive controlstatements NoneCase controlcommands

The default for the interface file request describer on the MBDEXPORT casecontrol command has changed from RECURDYN to SCMOTION.

Parameters The default for the MPCZERO parameter has changed from 1.0E-11 to1.0E-7.

Bulk entries The default for the AUTO parameter on the NXSTRAT entry has changedfrom 0 to 1.

Keyword changes

Keyword Keyword description Description of change

krylov Activates the Padé via Lanczosmethod in SOL 108. New keyword

Nastran statement changes

Systemcell

System cellname System cell description Description of change

205Defines the number of rows that aresimultaneously updated during asparse symmetric decomposition.

Update of the computer-dependentdefault rank value

NX Nastran 12 Release Guide 1-1


Systemcell

System cellname System cell description Description of change

627

In SOL 401, defines the outputcoordinate system for the 3Dsolids elements CTETRA, CHEXA,CPENTA and CPYRAM elements,the plane strain elements CPLSTN3,CPLSTN4, CPLSTN6, CPLSTN8, andthe plane stress elements CPLSTS3,CPLSTS4, CPLSTS6, CPLSTS8.

New system cell

640 PRESOUTDetermines the case controlcommand to be used for acousticpressure output at fluid grids.

New system cell

649 Controls whether the GDSTAT parallelsolution is used in SOL 401. New system cell

653

Controls whether the results arewritten to an HDF5 format output filein addition to an OP2 format outputfile.

New system cell

665 BSHDCPL

Turns off the computation of theCBUSH coupling moments which arecomputed when the connecting gridpoints are not coincident. Applies toall solutions except for SOLs 402,601, and 701.

New system cell

679 KRYLOV Activates the Pade via Lanczosmethod in SOL 108. New system cell

687Specifies the modulus of elasticity thatis used for rigid Lagrange elementsin a model.

New system cell

698

Controls the number of warning orerror messages from temperatureprocessing from the GP3 moduleprinted to the .f06 file.

New system cell

File management statement changes

No changes to file management statements.

Executive control statement changes

No changes to executive control statements.

Case control command changes

Case controlcommand Case control command description Description of change

ACCELERATION Acceleration output requestAdded remark on results recoveryfor points on frequency-dependentexternal superelements.

ACINTENSITY Acoustic intensity output Added SORT2 option.

1-2 NX Nastran 12 Release Guide


NX Nastran 12 summary of changes

Case controlcommand Case control command description Description of change

ACPOWER Acoustic power output Added options for random analysisresults.

ACVELOCITY Acoustic velocity output Added SORT2 option.ALOAD Acoustic load set selection New case control command

ATVOUT Acoustic transfer vector (ATV)creation specification New case control command

DISPLACEMENT Displacement output request

Added remark on results recoveryfor points on frequency-dependentexternal superelements.

Added remark that pressure resultsare separated from the displacementresults.

FRFIN Frequency-dependent frequencyresponse function matrix input New case control command

FRFOUT Frequency-dependent externalsuperelement creation specification New case control command

GRDCON Acoustic grid contribution request New case control command

IMPERF Selects grid point imperfections inSOL 401 New case control command

INITS Selects an initial stress or strain set oran offset strain set for SOL 401 New case control command

INPOWER Incident acoustic power output New case control command

MBDEXPORTCreates interface file for multibodyand control system software during aSOL 103, 111, or 112 run.

The Simcenter Motion solver isnow supported and the default forthe interface file request describerhas changed from RECURDYN toSCMOTION.

MONITOR Print selection for monitor data New case control command

NLARCL Requests nonlinear buckling in SOL401 New case control command

OTMFORC OTM force and moment output New case control command

PANCON Acoustic panel contribution request Eliminated the ability to request gridcontributions.

PRESSURE Pressure output request

By default, DISPLACEMENT casecontrol command can no longeroutput pressure results. The modifiedPRESSURE case control commandneeds to be used.

SETMC Modal contribution set definition Added PRESSURE response type.

TRLOSS Acoustic power transmission lossoutput New case control command

TRPOWER Transmitted acoustic power output New case control commandVECTOR Displacement output request Undocumented

VELOCITY Velocity output requestAdded remark on results recoveryfor points on frequency-dependentexternal superelements.




Parameter changes

Parameter Parameter description Description of change

BDMNCON

For SOL 200 topology optimization,defines the number of design cyclesin which the software will delay theapplication of any manufacturingconstraints.

New parameter

BRSYMFAC

Controls whether the stiffness anddamping that the software uses forCBEAR elements is the stiffness anddamping defined on PBEAR bulkentries or symmetrized versions ofthe stiffness and damping defined onPBEAR bulk entries.

New parameter

FLEXINVSelects the inversion method thatthe software uses when it invertsFRFFLEX bulk entry data.

New parameter

RESVALT

Determines whether the contributionof the residual vector modes tothe dynamic physical response isconsidered.

Undocumented

Degree-of-freedom set changes

No changes to degree-of-freedom sets.

Bulk entry changes

Bulk entry Bulk entry description Description of change

ACADAPTUser specified order adaptation rulefor acoustics FEM adaptive ordersolution

New bulk entry

ACORDER User specified order for acousticsFEM adaptive order solution New bulk entry

ACPLNW Acoustic plane wave source New bulk entryACPNVEL Acoustic panel normal velocity New bulk entryACPOLE1 Acoustic monopole source New bulk entryACPOLE2 Acoustic dipole source New bulk entryACPRESS Enforced pressure value on grids New bulk entryACTRAD Acoustic transfer admittance New bulk entry

ALOAD Acoustic load combination with unitscale factors New bulk entry

ATVBULK Selects acoustic transfer vector (ATV)results for an ATV system run New bulk entry

ATVFS Coupling interface definition for anacoustic transfer vector (ATV) New bulk entry





BCTPARM Control parameters for the contactalgorithm

The following new parameters havebeen added to the BCTPARM bulkentry for SOL 401: IPENRAMP,INTRFC, CTDAMP, CTDAMPN,CTDAMPT, and GAPVAL.

CHACAB Acoustic absorber element connection UndocumentedCHACBR Acoustic barrier element connection Undocumented

DMNCON Defines a manufacturing condition forSOL 200 topology optimization. New bulk entry

DMRLAW Defines a lattice type for SOL 200topology optimization. New bulk entry

DRESP1

Defines a set of structural responsesthat are used for the objective and/ordesign constraints, or for sensitivityanalysis purposes

For topology optimization, theDRESP1 now includes a complianceresponse type. It is defined byincluding CMPLNCE in the RTYPEfield.

DVTREL1 Selects the elements to be included ina SOL 200 topology optimization. New bulk entry

FRFFLEX Direct input of frequency-dependentdynamic flexibility matrix at points New bulk entry

FRFOMAP Assigns output type to FRFOTMresults New bulk entry

FRFOTMDirect input of frequency-dependentdynamic output transformation matrixat points

New bulk entry

FRFSTIF Direct input of frequency-dependentdynamic stiffness matrix at points New bulk entry

IMPERF Defines grid point imperfections inSOL 401 New bulk entry

IMPRADD Combines multiple IMPERF bulkentries in SOL 401 New bulk entry

MATPOR Defines material properties for porousmaterials used as acoustic absorbers

The defaults for the RHO, C, GAMMA,PR, MU, RES, POR, L1, and L2 fieldschange from "0.0" to "no default". Thedefault for the TORT field changesfrom "0.0" to "1.0".

The input for the RHO, C, GAMMA,PR, MU, L1, and L2 fields changefrom "REAL" to "REAL > 0.0". Theinput for the RES field changes from"REAL" to "REAL ≥ 0.0". The input forthe TORT field changes from "REAL"to "REAL ≥ 1.0". The input for thePOR field changes from "REAL" to"0.0 < REAL ≤ 1.0".





MAT10C

Defines constant or nominal materialproperties for fluid or absorberelements in coupled fluid-structuralanalysis

New bulk entry

MATF10CDefines tabular material properties forfluid or absorber elements in coupledfluid-structural analysis

New bulk entry

MONPNT2 Integrated load monitor point -element monitor output results item New bulk entry

MONPNT3 Integrated load monitor point - sumsgrid point forces New bulk entry

NLARCL Defines control parameters for SOL401 nonlinear buckling New bulk entry

NLCNTL Defines solution control parametersfor SOL 401

For SOL 401, the following newparameters have been added to theNLCNTL bulk entry: MSTAB, MSFAC

NXSTRATDefines parameters for solutioncontrol and strategy in advancednonlinear structural analysis

The following new parametershave been added to the NXSTRATbulk entry: ATSNSUB, ATSMASS,TETINT, DIAGSOL, BOLTDAMP,TFSHIFT

PAABSF1 Acoustic Impedance/AdmittanceElement Property New bulk entry

PACABS Acoustic absorber property UndocumentedPACBAR Acoustic barrier property Undocumented

PACTRAD Property of acoustic transferadmittance New bulk entry

PCOMPG1

Property entry to define a compositeproperty which allows for a differentfailure theory for each layer. SOLs401 and 402 only

New bulk entry

PLOTEL3 Triangular visualization element withthree grid points New bulk entry

PLOTEL4 Quadrilateral visualization elementwith four grid points New bulk entry

PLOTEL6 Triangular visualization element withsix grid points New bulk entry

PLOTEL8 Quadrilateral visualization elementwith eight grid points New bulk entry

PLOTHEXSix-sided hexahedron visualizationelement with eight to twenty gridpoints

New bulk entry

PLOTPEN Five-sided pentahedron visualizationelement with six to fifteen grid points New bulk entry

PLOTPYRFive-sided pyramid visualizationelement with five to thirteen gridpoints

New bulk entry

PLOTTET Four-sided tetrahedron visualizationelement with four to ten grid points New bulk entry




Bulk entry Bulk entry description Description of changeSEBULK Partitional superelement connection Added the TYPE = "FRFOP2" option

TABLEM5

For progressive ply failure with the UDdamage model in SOL 401, TABLEM5is optionally used to define a nonlinearfunction relating the shear damage(d12) to the thermodynamic force (Y)

New bulk entry



Chapter 2: Dynamics

Support for Simcenter MotionNow you can generate flexible body data during an NX Nastran SOL 103 run and write it to anOP2 file that is formatted for the Simcenter Motion to read. This capability is similar to the existingcapability to write interface files for ADAMS, RecurDyn, and SIMPACK.

You use the MBDEXPORT case control command to request that NX Nastran write an interface filefor all four of the motion applications. However, some notable differences exist.

• For ADAMS, RecurDyn and SIMPACK, NX Nastran can write interface files from a SOL 103,111, or 112 run. For the Simcenter Motion, NX Nastran can write the interface file from a SOL103 run only.

• For ADAMS, RecurDyn and SIMPACK, you must include a DTI,UNITS bulk entry in the NXNastran input file to explicitly define the units. For the Simcenter Motion, because the entireanalysis occurs within Pre/Post, this is not necessary.

• Results recovery is supported only for ADAMS and RecurDyn.

• Writing grid point stress and strain data to the interface file is only supported for ADAMS andRecurDyn.

For more information, see the updated MBDEXPORT case control command and “Multi-bodyDynamics and Control System Software Interfaces” in the NX Nastran Advanced Dynamic AnalysisUser’s Guide.


Chapter 2: Dynamics

MBDEXPORT

Multibody Dynamics Export

Creates interface file for multibody dynamics and control system software.FORMAT:

EXAMPLES:MBDEXPORT SCMOTION FLEXBODY=YES FLEXONLY=NOMBDEXPORT ADAMS STANDARD FLEXBODY=YES FLEXONLY=NO MINVAR=FULLMBDEXPORT OP4=22 STANDARD FLEXBODY=YESMBDEXPORT OP4=22 STATESPACE FLEXBODY=YESMBDEXPORT MATLAB STANDARD FLEXBODY=YESMBDEXPORT MATLAB STATESPACE FLEXBODY=YES

INTERFACEFILE

REQUESTDESCRIBERS:

Describer Interface file

SCMOTION Output Simcenter Motion solver OP2 file. (Default)

RECURDYN Output RecurDyn Flex Input (RFI) file.

ADAMS Output ADAMS Interface Modal Neutral File (MNF).


Chapter 2: Dynamics

Dynamics

Describer Interface file

SIMPACK Output SIMPACK Flexible Body Input (FBI) file.

OP4 Output OP4 file.

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 unitnumber on an ASSIGN statement.

MATLAB Output MATLAB script file.

OTHERDESCRIBERS:

Describer Meaning

STANDARD Matrices are based on the second-order representation of theequation of motion. (Default)

STATESPACE Matrices are based on first-order representation of the equationof motion.

Valid only when the OP4 or MATLAB interface file requestdescriber is specified.

FLEXBODY Controls whether the interface file is output. Specification of theFLEXBODY describer is required.

NO NX Nastran solution without output of the interface file. (Default)

YES NX Nastran solution with output of the interface file.

FLEXONLY Controls whether the DMAP solution and data recovery occursafter the interface file is output.

YES Interface file output only. (Default)

NO Interface file output and DMAP solution and data recovery.

MINVAR Controls how mass invariants are computed.

Valid only when the RECURDYN or ADAMS interface file requestdescribers are specified.


Dynamics

Chapter 2: Dynamics

Describer Meaning

PARTIAL Mass invariants 6 and 8 are not computed when the RECURDYNinterface file request describer is specified. (Default)

Mass invariants 5 and 9 are not computed when the ADAMSinterface file request describer is specified. (Default)

CONSTANT Mass invariants 1, 2, 3, and 8 are computed when theRECURDYN interface file request describer is specified.

Mass invariants 1, 2, 6, and 7 are computed when the ADAMSinterface file request describer is specified.

FULL All mass invariants are computed.

NONE No mass invariants are computed.

PSETID When the SCMOTION interface file request describer is specified,selects a set of elements that are exported to the OP2 file alongwith the grids that define their connectivity. The set of elementsis defined in the OUTPUT(PLOT) section (including PLOTEL) ofthe NX Nastran input file.

When the RECURDYN or SIMPACK interface file requestdescriber is specified, selects a set of elements that is exportedto the interface file. The set of elements is defined in theOUTPUT(PLOT) section (including PLOTEL) of the NX Nastraninput file.

When the ADAMS interface file request describer is specified,selects a set of elements whose connectivity is exported to facegeometry. The set of elements is defined in the OUTPUT(PLOT)section (including PLOTEL) of the NX Nastran input file or onan ADAMS sketch file.

Not valid when the OP4 or MATLAB interface file requestdescribers are specified.

NONE Export all grids, geometry and associated modal data. (Default)

setid Export face geometry for elements included in the SET casecontrol command with the same identification number as setid.

ALL Export face geometry for all elements included in SET casecontrol commands.


Chapter 2: Dynamics

Dynamics

Describer Meaning

sktunit Logical unit number for the ADAMS sketch file. Specify sktunit <0 to distinguish it from the setid.

Valid only when the ADAMS interface file request describers isspecified.

OUTGSTRS Controls whether grid point stress is written to interface file.


NO Do not write grid point stress to interface file. (Default)

YES Write grid point stress to interface file.

OUTGSTRN Controls whether grid point strain is written to interface file.


NO Do not write grid point strain to interface file. (Default)

YES Write grid point strain to interface file.

RECVROP2 Controls whether the FLEXBODY run outputs an NX NastranOP2 file for use in post processing of results.

NO OP2 file is not output. (Default)

YES OP2 file is output.

CHECK Controls whether debug output is written to the f06 file whenRECVROP2=YES.

NO Debug output is not written. (Default)

YES Debug output is written.

NONCUP Controls modal damping output.

Valid only when the SCMOTION, ADAMS, OP4 or MATLABinterface file request describers are specified.

-1 Output the full equivalent modal viscous damping matrix.(Default)

-2 Output the diagonal values of the equivalent modal viscousdamping matrix only.


Dynamics

Chapter 2: Dynamics

GENERALREMARKS:

1. Only one choice of SCMOTION, RECURDYN, ADAMS, SIMPACK, OP4, orMATLAB is allowed and must immediately follow the MBDEXPORT command.

2. The describers can be truncated to the first 4 characters.

3. MBDEXPORT must appear above the subcase level.

4. NX Nastran is a unitless code. RecurDyn, ADAMS, and SIMPACK are not. Thus,for a RecurDyn, ADAMS, or SIMPACK FLEXBODY=YES run, you must includea DTI,UNITS bulk entry in the NX Nastran input file. The DTI,UNITS bulk entryspecifies the units that are associated with the numerical data in the NX Nastraninput file.

For RecurDyn and ADAMS FLEXBODY=YES runs, NX Nastran writes theunits contained on the DTI,UNITS bulk entry directly to the interface file. WhenRecurDyn or ADAMS read the interface file, they associate the units with thenumerical data contained in the interface file.

For SIMPACK FLEXBODY=YES runs, NX Nastran uses the units contained on theDTI,UNITS bulk entry to convert the numerical data that it writes to the interface fileto SI (kg-m-sec) units. When SIMPACK reads the interface file, it recognizes thatthe numerical data contained in the interface file is already in SI (kg-m-sec) units.

The format of the DTI,UNITS bulk entry is as follows:

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)

MG – milligram (1E-6 kg)

MCG – microgram (1E-9 kg)

NG – nanogram (1E-12 kg)

UTON – U.S. ton (907.18474 kg)

SLI – slinch (175.1268352 kg)

Force:

N – Newton


Chapter 2: Dynamics

Dynamics

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) (Not valid for ADAMS)

P – poundal (0.138254954 N) (Not valid for ADAMS)

Length:

M – meter

KM – kilometer (1E3 m)

CM – centimeter (1E-2 m)

MM – millimeter (1E-3 m)

MI – mile (1609.344 m)

FT – foot (0.3048 m)

IN – inch (25.4E-3 m)

MCM – micrometer (1E-6 m)

NM – nanometer (1E-9 m)

A – Angstrom (1E-10 m)

YD – yard (0.9144 m)

ML – mil (25.4E-6 m)

MCI – microinch (25.4E-9 m)

Time:

S – second

H – hour (3600.0 sec)

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)


Dynamics

Chapter 2: Dynamics

Do not include a DTI,UNITS bulk entry in the NX Nastran input file when theSCMOTION, OP4, or MATLAB interface file request describer is specified. If youdo include a DTI,UNITS bulk entry, NX Nastran ignores it.

5. Because in a RecurDyn, ADAMS, or SIMPACK FLEXBODY=YES run theDTI,UNITS bulk entry defines the units, the scaling defined in WTMASS, whichis important for units consistency in NX Nastran, is ignored in the output to theinterface 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. To ensurethat NX Nastran works with the consistent set of kg, N, and m, the DTI,UNITSbulk entry is:

DTI UNITS 1 KG N M S

The remarks from this point on are specific to each interface type.SIMCENTER

MOTIONREMARKS:

1. The generation of standard matrices and the writing of them to a Simcenter MotionOP2 file via OUTPUT2, which is only applicable in a non-restart, residual-onlySOL 103 analysis, is initiated by MBDEXPORT SCMOTION FLEXBODY=YES.A specific ASSIGN statement is not required; the data will be written to thestandard OP2 file via PARAM,POST,-2. This implies that the user must includePARAM,POST,-2 in the bulk data.

2. The parameter LMODES can be used to control which modes are used to derivethe standard matrices.

3. The mode shape output will be reduced to the DOF defined in the DISPLACEMENTcase control output request.

4. Because Simcenter Motion requires the constrained Craig-Bampton modes, youmust use only the METHOD case control command in the flexbody creation run.The RSMETHOD case control command should not be used because it producesa modal basis that is invalid for Simcenter Motion.

RECURDYNREMARKS:

1. The creation of the RecurDyn Flex Input file is applicable in a non-restart SOL103, 111, or 112 analysis only. RFI files are named ‘jid_seid.rfi’, where seid is theinteger number of the superelement (0 for residual). These files are located inthe same directory as the jid.f06 file.

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

3. The eight mass variants are:


Chapter 2: Dynamics

Dynamics

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

φp = partitioned orthogonal modal matrix that corresponds to the translationaldegrees of freedom of grid p.

Ip = inertia tensor p.

φp* = partitioned orthogonal modal matrix that corresponds to the rotationaldegrees of freedom of grid p.

= skew-symmetric matrix formed for each grid translational degree of freedomfor each mode.

M = number of modes.

N = number of grids.

4. To accurately capture the mode shapes when supplying SPOINT/QSETcombinations, the number of SPOINTS (ns) should be at least ns=n+(6+p),assuming that residual flexibility is on. In the above equation for ns, the number ofmodes (n) is specified on the EIGR (METHOD=LAN) or EIGRL bulk entries; thenumber of load cases is p. In general, you cannot have too many SPOINTs, asexcess ones will be truncated with no performance penalty.


Dynamics

Chapter 2: Dynamics

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

6. OMIT or OMIT1 bulk entries are not supported.

7. Lumped mass formulation (default) is required. Either leave PARAM,COUPMASSout of the input file or supply PARAM,COUPMASS,-1 (default) to ensure lumpedmass.

8. CBEND elements are not allowed because they always use a coupled massformulation. Likewise, the MFLUID fluid structure interface is not allowed becausethe virtual mass matrix it generates is not diagonal.

9. PARAM,WTMASS,value with a value other than 1.0 may be used with an NXNastran run generating an RFI. It must have consistent units with regard to theDTI,UNITS bulk entry. Before generating the RFI, NX Nastran will appropriatelyscale the WTMASS from the physical mass matrix and mode shapes.

10. There is a distinction between how an MBDEXPORT RECURDYNFLEXBODY=YES run handles element-specific loads (such as a PLOAD4 entry)versus those that are grid-specific (such as a FORCE entry), especially whensuperelements are used. The superelement sees the total element-specificapplied load. For grid-specific loads, the loads attached to an external grid willmove downstream with the grid. That is to say, it is part of the boundary and notpart of the superelement. This distinction applies to a superelement run and not toa residual-only or parts superelement run.

11. The loads specified in NX Nastran generally fall into two categories: non-followeror fixed direction loads (non-circulatory) and follower loads (circulatory). Thefollower loads are nonconservative in nature. Examples of fixed direction loads arethe FORCE entry or a PLOAD4 entry when its direction is specified via directioncosines. Examples of follower loads are the FORCE1 entry or the PLOAD4 entrywhen used to apply a normal pressure. By default in NX Nastran, the followerloads are always active in SOL 103 and will result in follower stiffness being addedto the differential stiffness and elastic stiffness of the structure. In a run withMBDEXPORT RECURDYN FLEXBODY=YES and superelements, if the followerforce is associated with a grid description (such as a FORCE1) and the grid isexternal to the superelement, the follower load will move downstream with the grid.Thus, the downstream follower contribution to the component’s stiffness will belost, which could yield poor results. This caution only applies to a superelementrun and not to a residual-only or a part superelement run.

12. OUTGSTRS and OUTGSTRN entries require the use of standard NX NastranSTRESS= or STRAIN= used in conjunction with GPSTRESS= or GPSTRAIN=commands to produce grid point stress or strain. GPSTRESS(PLOT)= orGPSTRAIN(PLOT)= will suppress grid stress or strain print to the NX Nastran.f06 file.

13. To reduce the FE mesh detail for dynamic simulations, PSETID can include the IDof a SET entry. The SET entry lists PLOTEL or element IDs, whose connectivity


Chapter 2: Dynamics

Dynamics

is exported into the RFI to display the components in RecurDyn. This optioncan significantly reduce the size of the RFI without compromising accuracy inthe FunctionBay simulation providing that the mass invariant computation isrequested. With superelement analysis, for any of these elements that lie entirelyon the superelement boundary (all of the elements’ grids are attached only toa-set or exterior grids), a SEELT bulk entry must be specified to keep that displayelement with the superelement component. This can also be accomplishedusing PARAM, AUTOSEEL,YES. The SEELT entry is not required with partssuperelements, 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 gridsto display the component in RecurDyn. If PSETID does not find the set ID inOUTPUT(PLOT), it will search sets in the case control for a matching set ID. Thismatching 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 usedto select grids to display the component in RecurDyn. If you wish to select all ofthe sets in the OUTPUT(PLOT) section, then use PSETID=ALL.

The following element types are not supported for writing to an RFI, nor arethey supported as a ‘type’ entry in a set definition in OUTPUT(PLOT): CAABSF,CAEROi, CDUMi, CHBDYx, CDAMP3, CDAMP4, CELAS3, CELAS4, CMASS3,CMASS4, CRAC2D, CRAC3D, CTWIST, CWEDGE, CWELD, and GENEL.

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

Typical Parameters:

• PARAM,RESVEC,character_value – controls calculation of residual vectormodes.

• PARAM,GRDPNT,value - mass invariants 1I, 2I, and 3I will be computed usingresults of NX Nastran grid point weight generator execution in the basiccoordinate system.

Typical Case Control:

• MBDEXPORT RECURDYN FLEXBODY=YES is required for RFI generation.

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

• SUPER=n,SEALL=n is useful with multiple superelement models to selectan individual superelement as a flexible body. Cannot be used with a linearSTATSUB(PRELOAD) run.

• OUTPUT(PLOT) is necessary to define elements used to select grids todisplay the component in RecurDyn when PSETID=ALL or setid.

SET n=list of elements (including PLOTELs) is used to select grids to displaythe component.

• OUTPUT(POST) is necessary to define volume and surface for grid stressor strain shapes.


Dynamics

Chapter 2: Dynamics

SET n=list is a list of elements for surface definition for grid stress or strainshapes.

Stress and strain data in the RFI is limited to the six components (that is, 3normal 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 stressand strain data. Only one FIBER selection is allowed for each SURFACE, thusthe use of the FIBER ALL keyword on the SURFACE case control commandwill write stresses to the RFI at the Z1 fiber location only.

Because the FIBER keyword only applies to stresses, strain data will alwaysbe written to the RFI at the MID location.

Stress and strain data at grid points can only be written to the RFI for surfaceand volume type elements (for example, CQUAD and CHEXA).

VOLUME n SET n is a volume definition.

The default SYSTEM BASIC is required with SURFACE or VOLUME.

• STRESS(PLOT) is necessary for stress shapes.

• STRAIN(PLOT) is necessary for strain shapes.

• GPSTRESS(PLOT) is necessary for grid point stress shapes to be included inthe RFI.

• GPSTRAIN(PLOT) is necessary for grid point strain shapes to be included inthe RFI.

Typical Bulk Data:

• DTI,UNITS,1,MASS,FORCE,LENGTH,TIME is required for RFI generation.For input files containing superelements, this command must reside in themain bulk data section.

• SPOINT,id_list defines and displays modal amplitude.

• SESET,SEID,grid_list defines a superelement (see GRID and BEGIN BULKSUPER=). The exterior grids will represent the attachment points along withthe q-set.

• SEELT,SEID,element_list reassigns superelement boundary elements to anupstream superelement.

• RELEASE,SEID,C,Gi is an optional entry that removes DOFs from anattachment grid for which no constraint mode is desired. For example, thisallows the removal of rotational degrees of freedom from an analysis whereonly translational degrees of freedom are required.

• SEQSET,SEID,spoint_list defines modal amplitudes of a superelement (seeSEQSET1).


Chapter 2: Dynamics

Dynamics

• SENQSET,SEID,N defines modal amplitudes of a part superelement. It mustreside in the main bulk data section.

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

• QSET1,C,IDi defines modal amplitudes for the residual structure or modalamplitudes for a part superelement (see QSET).

• PLOTEL,EID,Gi can be used, along with existing model elements, to defineelements used to select grids to display the components in RecurDyn.

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

15. MBDEXPORT and ADAMSMNF case control entries cannot be used in the sameanalysis run. In other words, a RecurDyn RFI file or an Adams MNF file can begenerated during a particular NX Nastran execution, but not both files at the sametime. Attempting to generate both files in the same analysis will cause an error tobe issued and the execution to be terminated.

16. The RECVROP2=YES option is used when you would like results recovery (usingthe MBDRECVR case control entry) from an RecurDyn/Flex analysis. This optionrequires 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 willcause an OP2 file with a .out extension to be generated, which then can beused as input into an NX Nastran SOL 103 run using the MBDRECVR casecontrol 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 removedMAAEW - modal massKAAE - modal stiffnessCMODEXT - 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 beincluded in the recovered results when using MBDRECVR.

17. Setting CHECK=YES (which is only available when RECVROP2=YES) is notrecommended for large models due to the amount of data that will be written tothe f06.

18. The MBDEXPORT data routines use the environment variable TMPDIR fortemporary storage during the processing of mode shape data. As a result, TMPDIRmust be defined when using MBDEXPORT. TMPDIR should equate to a directorystring for temporary disk storage, preferably one with a large amount of free space.

19. Preload conditions are not supported.


Dynamics

Chapter 2: Dynamics

20. To request differential stiffness, include a static subcase that contains thestress-stiffening loads. In another subcase include STATSUB = n where n is thenumber of the static subcase.

ADAMSREMARKS:

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

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

3. The nine mass variants are:


Chapter 2: Dynamics

Dynamics

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

φp = partitioned orthogonal modal matrix that corresponds to the translationaldegrees of freedom of grid p.

Ip = inertia tensor p.

φp* = partitioned orthogonal modal matrix that corresponds to the rotationaldegrees of freedom of grid p.

= skew-symmetric matrix formed for each grid translational degree of freedomfor each mode.

M = number of modes.

N = number of grids.

4. To accurately capture the mode shapes when supplying SPOINT/QSETcombinations, the number of SPOINTS (ns) should be at least ns=n+(6+p),assuming that residual flexibility is on. In the above equation for ns, the number ofmodes (n) is specified on the EIGR (METHOD=LAN) or EIGRL bulk entries; thenumber of load cases is p. In general, you cannot have too many SPOINTs, asexcess ones are truncated with no performance penalty.

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

6. OMIT or OMIT1 bulk entries are not supported.

7. Lumped mass formulation (default) is required. Either leave PARAM,COUPMASSout of the input file or supply PARAM,COUPMASS,-1 (default) to ensure lumpedmass.



Dynamics

Chapter 2: Dynamics

9. PARAM,WTMASS,value with a value other than 1.0 may be used with an NXNastran run generating an MNF. It must have consistent units with regard to theDTI,UNITS bulk entry. Before generating the MNF, NX Nastran will appropriatelyscale the WTMASS from the physical mass matrix and mode shapes.

10. There is a distinction between how an MBDEXPORT ADAMS FLEXBODY=YESrun handles element-specific loads (such as a PLOAD4 entry) versus those thatare grid-specific (such as a FORCE entry), especially when superelementsare used. The superelement sees the total element-specific applied load. Forgrid-specific loads, the loads attached to an external grid will move downstreamwith the grid. That is to say, it is part of the boundary and not part of thesuperelement. This distinction applies to a superelement run and not to aresidual-only or parts superelement run.

11. The loads specified in NX Nastran generally fall into two categories: non-followeror fixed direction loads (non-circulatory) and follower loads (circulatory). Thefollower loads are nonconservative in nature. Examples of fixed direction loads arethe FORCE entry or a PLOAD4 entry when its direction is specified via directioncosines. Examples of follower loads are the FORCE1 entry or the PLOAD4 entrywhen used to apply a normal pressure. By default in NX Nastran, the followerloads are always active in SOL 103 and will result in follower stiffness being addedto the differential stiffness and elastic stiffness of the structure. In a run withMBDEXPORT ADAMS FLEXBODY=YES and superelements, if the follower forceis associated with a grid description (such as a FORCE1) and the grid is externalto the superelement, the follower load will move downstream with the grid. Thus,the downstream follower contribution to the component’s stiffness will be lost,which could yield poor results. This caution only applies to a superelement runand not to a residual-only or a part superelement run.

12. OUTGSTRS and OUTGSTRN entries require the use of standard NX NastranSTRESS= or STRAIN= used in conjunction with GPSTRESS= or GPSTRAIN=commands to produce grid point stress or strain. GPSTRESS(PLOT)= orGPSTRAIN(PLOT)= will suppress grid stress or strain print to the NX Nastran.f06 file.

13. To reduce the FE mesh detail for dynamic simulations, PSETID (on theMBDEXPORT Case Control command) defined with a SET entry (i.e. setid) isused to define a set of PLOTELs or other elements used to select grids to displaythe components in Adams. This option can significantly reduce the size of theMNF without compromising accuracy in the Adams simulation providing that themass invariant computation is requested. With superelement analysis, for any ofthese 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 specifiedto keep that display element with the superelement component. This can also beaccomplished using PARAM, AUTOSEEL,YES. The SEELT entry is not requiredwith parts superelements, as boundary elements stay with their component.

If the SET entry points to an existing set from the OUTPUT(PLOT) section, thissingle set is used explicitly to define elements used to select grids to display thecomponent in Adams. If PSETID does not find the set ID in OUTPUT(PLOT), it willsearch sets in the case control for a matching set ID. This matching set ID list then


Chapter 2: Dynamics

Dynamics

represents a list of OUTPUT(PLOT) defined elements’ sets, the union of whichwill be used to define a set of PLOTELs or other elements used to select gridsto display the component in Adams. If the user wishes to select all of the sets inthe OUTPUT(PLOT) section, then use PSETID=ALL.

The following element types are not supported for writing to an MNF, nor arethey supported as a ‘type’ entry in a set definition in OUTPUT(PLOT): CAABSF,CAEROi, CDUMi, CHBDYx, CDAMP3, CDAMP4, CELAS3, CELAS4, CMASS3,CMASS4, CRAC2D, CRAC3D, CTWIST, CWEDGE, CWELD, and GENEL.

PSETID can also point to a sketch file using PSETID= – sktunit, where sktunitreferences an ASSIGN statement of the form:

ASSIGN SKT=‘sketch_file.dat’,UNIT=sktunit.

The grids defined for the elements’ faces in the sketch file, along with all external(i.e. boundary) grids for the superelements, will be the only grids (and theirassociated 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_countface_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 ofa single brick element might be described as follows:

64 1000 1001 1002 10034 1007 1006 1005 10044 1000 1004 1005 10014 1001 1005 1006 10024 1002 1006 1007 10034 1003 1007 1004 1000

Alternatively, the mesh might be described as a stick figure using a collection oflines (two node faces), as shown below:

82 101 1022 102 1032 103 1042 104 1052 105 1062 106 1072 107 1082 108 109


Typical Parameters:


Dynamics

Chapter 2: Dynamics

• PARAM,RESVEC,character_value – controls calculation of residual vectormodes.

• PARAM,GRDPNT, value - mass invariants 1I, 2I, and 7I will be computedusing results of NX Nastran grid point weight generator execution in the basiccoordinate system.


• MBDEXPORT ADAMS FLEXBODY=YES is required for MNF generation.



• OUTPUT(PLOT) is necessary to define elements used to select grids todisplay the component in Adams when PSETID=ALL or setid.

SET n=list of elements (including PLOTELs) is used to select grids to displaythe component.

• OUTPUT(POST) is necessary to define volume and surface for grid stressor strain shapes.

SET n=list is a list of elements for surface definition for grid stress or strainshapes.

Stress and strain data in the MNF is limited to the six components (i.e. 3normal 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 stressand strain data. Only one FIBER selection is allowed for each SURFACE, thusthe use of the FIBRE ALL keyword on the SURFACE case control commandwill write stresses to the MNF at the Z1 fiber location only.

Because the FIBRE keyword only applies to stresses, strain data will alwaysbe written to the MNF at the MID location.

Stress and strain data at grid points can only be written to the MNF for surfaceand volume type elements (e.g. CQUAD and CHEXA).

VOLUME n SET n is a volume definition.

The default SYSTEM BASIC is required with SURFACE or VOLUME.

• STRESS(PLOT) is necessary for stress shapes.

• STRAIN(PLOT) is necessary for strain shapes.

• GPSTRESS(PLOT) is necessary for grid point stress shapes to be includedin the MNF.

• GPSTRAIN(PLOT) is necessary for grid point strain shapes to be includedin the MNF.


Chapter 2: Dynamics

Dynamics

Typical Bulk Data:

• DTI,UNITS,1,MASS,FORCE,LENGTH,TIME is required for MNF generation.For input files containing superelements, this command must reside in themain bulk data section.

• SPOINT,id_list defines and displays modal amplitude.SESET,SEID,grid_listdefines a superelement (see GRID and BEGIN BULK SUPER=). The exteriorgrids will represent the attachment points along with the q-set.







• PLOTEL,EID,Gi can be used, along with existing model elements, to defineelements used to select grids to display the components in Adams.


15. The RECVROP2=YES option is used when you would like results recovery (usingthe MBDRECVR case control entry) from an Adams/Flex analysis. This optionrequires the following assignment command:


be inserted into the file management section of the NX Nastran input file. It willcause an OP2 file with a .out extension to be generated, which then can beused as input into an NX Nastran SOL 103 run using the MBDRECVR casecontrol capability to perform results recovery from an Adams/Flex analysis.FLEXBODY=YES is required with its use.




Dynamics

Chapter 2: Dynamics



16. Setting CHECK=YES (which is only available when RECVROP2=YES) is notrecommended for models of realistic size due to the amount of data that will bewritten to the f06 file.


18. If any damping is defined in the model, an equivalent modal viscous dampingwill be determined for each mode and written to the MNF. This equivalent modalviscous damping is defined as:

D = ψT Be ψ

where D is the equivalent modal viscous damping matrix, ψ is the eigenvectormatrix, and Be is the equivalent viscous damping matrix.

The equivalent viscous damping matrix is given by:

where G,W3, andW4 are structural damping-related parameters described in the“Parameter Descriptions” section of this guide.

By default, the full equivalent modal viscous damping matrix is written to the MNF.To write only the diagonal values of the equivalent modal viscous damping matrixto the MNF, specify NONCUP=–2 or specify PARAM,NONCUP,-2.

If both the NONCUP describer and the NONCUP parameter are specified, theNONCUP describer specification takes precedence.



21. Cylindrical and spherical nodal displacement coordinate systems (i.e. CD on theGRID bulk entry) are not supported.

SIMPACKREMARKS:

1. The creation of a SIMPACK Flexible Body Input (FBI) file is applicable in anon-restart SOL 103, 111, and 112 analysis only. FBI files are named ‘jid_seid.fbi’,where seid is the integer number of the superelement (0 for residual). The locationof these files is the same directory as the jid.f06 file.


Chapter 2: Dynamics

Dynamics

2. The creation of the FBI file is initiated by MBDEXPORT SIMPACKFLEXBODY=YES (other describers are optional) and the inclusion of the bulkentry DTI,UNITS. This is only valid for a Component Mode Synthesis (CMS)analysis. Thus, it is necessary to define the modal coordinates using the SPOINTbulk entry, and to define them to be in the q-set using the QSET/QSET1 orSEQSET/SEQSET1 bulk entries as appropriate.

3. You can create flexible body attachment points by defining the component as asuperelement or part superelement, in which case the physical external (a-set)grids become the attachment points; or for a residual-only type model, you canuse NX Nastran ASET bulk entries to define the attachment points. Note that thevalues corresponding to these attachment points in the CMS-reduced mass andstiffness matrices written to the FBI file will be defined in the nodal displacementcoordinate systems of these attachment points. The user must account for thesecoordinate systems when loading or restraining these attachment points withinthe SIMPACK run.

4. To accurately capture the mode shapes when supplying SPOINT/QSETcombinations, the number of SPOINTs (ns) should be at least ns=n+(6+p). Inthe above equation for ns, the number of modes (n) is specified on the EIGR(METHOD=LAN) or EIGRL bulk entries; the number of load cases is p. In general,you cannot have too many SPOINTs. Excess SPOINTs will be truncated withno performance penalty.

5. OMIT and OMIT1 bulk entries are not supported.

6. Lumped mass formulation (default) is required. Either leave PARAM,COUPMASSout of the input file or supply PARAM,COUPMASS,-1 (default) to ensure lumpedmass formulation.


8. PARAM,WTMASS,value with a value other than 1.0 may be used with an NXNastran run generating an FBI file. It must have consistent units with regard to theDTI,UNITS bulk entry. Before generating the FBI file, NX Nastran will appropriatelyscale the WTMASS from the physical mass matrix and mode shapes.

9. There is a distinction between how an MBDEXPORT SIMPACK FLEXBODY=YESrun handles element-specific loads (such as a PLOAD4 entry) versus those thatare grid-specific (such as a FORCE entry), especially when superelementsare used. The superelement sees the total element-specific applied load. Forgrid-specific loads, the loads attached to an external grid will move downstreamwith the grid. That is to say, it is part of the boundary and not part of thesuperelement. This distinction applies to a superelement run and not to aresidual-only or parts superelement run.

10. The loads specified in NX Nastran generally fall into two categories: non-followeror fixed direction loads (non-circulatory) and follower loads (circulatory). Thefollower loads are nonconservative in nature. Examples of fixed direction loads are


Dynamics

Chapter 2: Dynamics

the FORCE entry or a PLOAD4 entry when its direction is specified via directioncosines. Examples of follower loads are the FORCE1 entry or the PLOAD4 entrywhen used to apply a normal pressure. By default in NX Nastran, the followerloads are always active in SOL 103 and will result in follower stiffness being addedto the differential stiffness and elastic stiffness of the structure. In a run withMBDEXPORT SIMPACK FLEXBODY=YES and superelements, if the followerforce is associated with a grid description (such as a FORCE1) and the grid isexternal to the superelement, the follower load will move downstream with the grid.Thus, the downstream follower contribution to the component’s stiffness will belost, which could yield poor results. This caution only applies to a superelementrun and not to a residual-only or a part superelement run.

11. To reduce the FE mesh detail for dynamic simulations, PSETID can include theID of a SET entry. PSETID is also used to define the grids to be included inthe recovery matrix that is written to the FBI file. The SET entry lists PLOTELor element IDs, whose connectivity is exported into the FBI file to display thecomponents in SIMPACK. This option can significantly reduce the size of the FBIfile without compromising accuracy in the SIMPACK simulation. With superelementanalysis, 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 SEELTbulk entry must be specified to keep that display element with the superelementcomponent. This can also be accomplished using PARAM, AUTOSEEL,YES. TheSEELT entry is not required with parts superelements, as boundary elements staywith 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 gridsto display the component in SIMPACK. If PSETID does not find the set ID inOUTPUT(PLOT), it will search sets in the case control for a matching set ID. Thismatching 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 usedto select grids to display the component in SIMPACK. If you wish to select all ofthe sets in the OUTPUT(PLOT) section, then use PSETID=ALL.

The following element types are not supported for writing to an FBI file, nor arethey supported as a ‘type’ entry in a set definition in OUTPUT(PLOT): CAABSF,CAEROi, CDUMi, CHBDYx, CDAMP3, CDAMP4, CELAS3, CELAS4, CMASS3,CMASS4, CPYRAM, CRAC2D, CRAC3D, CTWIST, CWEDGE, CWELD, andGENEL.



• MBDEXPORT SIMPACK FLEXBODY=YES is required for FBI file generation.




Chapter 2: Dynamics

Dynamics

Typical Bulk Data:

• DTI,UNITS,1,MASS,FORCE,LENGTH,TIME is required for FBI file generation.For input files containing superelements, this command must reside in themain bulk data section.

• SPOINT,id_list defines and displays modal amplitude.

• SESET,SEID,grid_list defines a superelement (see GRID and BEGIN BULKSUPER=). The exterior grids will represent the attachment points along withthe q-set.







• PLOTEL,EID,Gi can be used, along with existing model elements, to defineelements used to select grids to display the components in SIMPACK.


13. MBDEXPORT and ADAMSMNF case control entries cannot be used in the sameanalysis run. In other words, a SIMPACK FBI file or an Adams MNF file can begenerated during a particular NX Nastran execution, but not both files at the sametime. Attempting to generate both files in the same analysis will cause an error tobe issued and the solve to be terminated.

14. The RECVROP2=YES option is used when you would like results recovery (usingthe MBDRECVR case control entry) from a SIMPACK analysis. This optionrequires the following assignment command:


be inserted into the file management section of the NX Nastran input file. It willcause an OP2 file with a .out extension to be generated, which then can be usedas input into an NX Nastran SOL 103 run using the MBDRECVR case controlcapability to perform results recovery from a SIMPACK analysis. FLEXBODY=YESis required with its use.


Dynamics

Chapter 2: Dynamics









OP4REMARKS:

1. The generation of standard or state-space matrices and the writing of themto an OP4 file via OUTPUT4, which is applicable in a non-restart SOL 103,111, or 112 analysis only, is initiated by MBDEXPORT OP4=unit STANDARDFLEXBODY=YES, or MBDEXPORT OP4=unit STATESPACE FLEXBODY=YES(other describers are optional) and the inclusion of the ASSIGN file managementstatement. This ASSIGN statement must be of the form:

ASSIGN OUTPUT4=’filename’,UNIT=n,etc.

where ‘n’ matches the absolute value for unit on the MBDEXPORT OP4=unitcase control command.

The number of digits of precision for matrix data is controlled by the DIGITSparameter.

For a model with superelements, only one OP4 file will be generated. This OP4file will be generated for the first superelement (or the residual) that satisfies theconditions defined in Remarks 3 and 4. For standard matrices, if user-defined setU8 is not defined, the residual will be written to the OP4.

2. The parameters LFREQ/HFREQ or LMODES can be used to control which modesare used to derive the standard or state-space matrices.

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


Chapter 2: Dynamics

Dynamics

partitioned superelements and refer to the SEUSET/SEUSET1 bulk entries fornon-partitioned superelements.

4. For standard matrices, user-defined set U8 is used for output DOF. The modeshape output will be reduced to the DOF defined in DOF set U8. If DOF setU8 is not defined, the mode shape data for all DOF will be written. Refer tothe USET/USET1 bulk entries for partitioned superelements and refer to theSEUSET/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 beingthe direction code (1 through 6).

6. For the standard option, the OP4 file contains the modal mass, equivalent modalviscous damping, modal stiffness, mode shapes, and modal forces defined asMMASS, MDAMP, MSTIF, U8PHIX, and MFORC, respectively. The physical DOFcorresponding one-to-one with the rows of U8PHIX are defined as U8DOF. Thefirst column contains the grid ID and the second column contains the directioncode (1 through 6).

7. The RECVROP2=YES option is used when you would like results recovery (usingthe MBDRECVR case control entry) from a system analysis. This option requiresthe 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 willcause an OP2 file with a .out extension to be generated, which can then be usedas an input into an NX Nastran SOL 103 run using the MBDRECVR case controlcommand. FLEXBODY=YES is required when specifying RECVROP2=YES.


MGGEW – physical mass external sort with weight mass removed

MAAEW – modal mass

KAAE – modal stiffness

CMODEXT – component modes

This capability is limited to one superelement per NX Nastran model. Residual-onlyanalyses are supported.



9. Differential stiffness is only supported for standard second-order systemrepresentation. To request differential stiffness, include a static subcase that


Dynamics

Chapter 2: Dynamics

contains the stress-stiffening loads. In another subcase include STATSUB = nwhere n is the number of the static subcase.

10. By default, the full equivalent modal viscous damping matrix is written to standardor state-space OP4 files. To write only the diagonal values of the equivalentmodal viscous damping matrix to OP4 files, specify NONCUP=–2, or specifyPARAM,NONCUP,-2.


MATLABREMARKS:

1. The generation of standard or state-space matrices and the writing of themto a MATLAB script file, which is applicable in a non-restart SOL 103, 111,or 112 analysis only, is initiated by MBDEXPORT MATLAB STANDARDFLEXBODY=YES, or MBDEXPORT MATLAB STATESPACE FLEXBODY=YES(other describers are optional). The MATLAB script files are named jid_seid.mwhere seid is the integer number of the superelement (0 for residual). The locationof the MATLAB script files is the same directory as the jid.f06 file.

2. The parameters LFREQ/HFREQ or LMODES can be used to control which modesare used to derive the standard or state-space matrices.

3. For state-space matrices, user-defined set U7 is used for input DOF. User-definedset U8 is used for output DOF. Refer to the USET/USET1 bulk entries forpartitioned superelements and refer to the SEUSET/SEUSET1 bulk entries fornon-partitioned superelements.

4. For standard matrices, user-defined set U8 is used for output DOF. The modeshape output will be reduced to the DOF defined in DOF set U8. If DOF setU8 is not defined, the mode shape data for all DOF will be written. Refer tothe USET/USET1 bulk entries for partitioned superelements and refer to theSEUSET/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 beingthe 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 modalforces defined as MMASS, MDAMP, MSTIF, MSHAP, and MFORC, respectively.The physical DOF corresponding one-to-one with the rows of MSHAP are definedas U8DOF. The first column contains the grid ID and the second column containsthe direction code (1 through 6).

7. The RECVROP2=YES option is used when you would like results recovery (usingthe MBDRECVR case control entry) from a system analysis. This option requiresthe following assignment command:


Chapter 2: Dynamics

Dynamics

ASSIGN OUTPUT2=’name.out’ STATUS=UNKNOWN UNIT=20 FORM=UNFORM

be inserted into the file management section of the NX Nastran input file. It willcause an OP2 file with a .out extension to be generated, which can then be usedas an input into an NX Nastran SOL 103 run using the MBDRECVR case controlcommand. FLEXBODY=YES is required when specifying RECVROP2=YES.


MGGEW – physical mass external sort with weight mass removed

MAAEW – modal mass

KAAE – modal stiffness

CMODEXT – component modes

This capability is limited to one superelement per NX Nastran model. Residual-onlyanalyses are supported.




10. By default, the full equivalent modal viscous damping matrix is written tostandard or state-space MATLAB script files. To write only the diagonal valuesof the equivalent modal viscous damping matrix to MATLAB script files, specifyNONCUP=–2 or specify PARAM,NONCUP,-2.


Random analysis control enhancement

Note

This enhancement was implemented in NX Nastran 11, but is fully documented in thisrelease.

In SOL 108 and 111, the software can now use the results from the same frequency responsesubcases in multiple random analyses. In earlier versions of NX Nastran, the software mustrecalculate the frequency response subcases for each random analysis. This enhancement resultsin a significant reduction in the computational effort required to perform multiple random analyses,especially when the random analyses reference many frequency response subcases.


Dynamics

Chapter 2: Dynamics

To implement this capability, the RANDOM option for the TYPE describer on the ANALYSIS casecontrol command is now available. Include ANALYSIS = RANDOM in each subcase in which youwant to perform a random analysis.

Example

Suppose that a structure is excited by two loads, and you want to evaluate the random responseof the structure for two PSD functions using SOL 111. For NX Nastran 12, the subcase structureof the input file can be organized as follows:

SUBCASE 1$$ Subcase 1 calculates the normal modes$ANALYSIS=MODESDISP=ALL$SUBCASE 2$$ Subcase 2 calculates the frequency response of the structure to the$ loading specified by DLOAD 111 at the frequencies specified by$ FREQUENCY set 13$FREQUENCY=13DLOAD=111$SUBCASE 3$$ Subcase 3 calculates the frequency response of the structure to the$ loading specified by DLOAD 211 at the frequencies specified by$ FREQUENCY set 13$FREQUENCY=13DLOAD=211$SUBCASE 4$$ Subcase 4 uses the frequency responses from Subcases 2 and 3 to$ calculate the random response of the structure for the PSD function$ specified by RANDOM 100$ANALYSIS=RANDOMRANDOM=100$SUBCASE 5$$ Subcase 5 uses the frequency responses from Subcases 2 and 3 to$ calculate the random response of the structure for the PSD function$ specified by RANDOM 200$ANALYSIS=RANDOMRANDOM=200

As you can see, in the above subcase organization, the software calculates each frequency responseonce regardless of the number of PSD functions that you want to consider.


Chapter 2: Dynamics

Dynamics

Note

To use multiple frequency responses in a random calculation:

• For SOL 108 or 111, each frequency response must reference the same set offrequencies.

• For SOL 111, if SDAMPING is specified, each frequency response must reference thesame SDAMPING specification.

For earlier versions of NX Nastran, the subcase structure of the input file for the same solutionmust be organized as follows:

SUBCASE 1$$ Subcase 1 calculates the normal modes$ANALYSIS=MODESDISP=ALL$SUBCASE 2$$ Subcase 2 calculates the frequency response of the structure to the$ loading specified by DLOAD 111 at the frequencies specified by$ FREQUENCY set 13 and requests the software calculate the random$ response of the structure for the PSD function specified by$ RANDOM 100$RANDOM=100FREQUENCY=13DLOAD=111$SUBCASE 3$$ Subcase 3 calculates the frequency response of the structure to the$ loading specified by DLOAD 211 at the frequencies specified by$ FREQUENCY set 13$FREQUENCY=13DLOAD=211$SUBCASE 4$$ Subcase 4 recalculates the frequency response of the structure to$ the loading specified by DLOAD 211 at the frequencies specified by$ FREQUENCY set 23 and requests the software calculate the random$ response of the structure for the PSD function specified by$ RANDOM 200$RANDOM=200FREQUENCY=23DLOAD=111$SUBCASE 5


Dynamics

Chapter 2: Dynamics

$$ Subcase 5 recalculates the frequency response of the structure to$ the loading specified by DLOAD 211 at the frequencies specified by$ FREQUENCY set 23$FREQUENCY=23DLOAD=211

Note

In the example, FREQUENCY=13 and FREQUENCY=23 reference FREQi bulk entriesthat contain the same set of frequencies.

As you can see, in the above subcase organization, the software recalculates the frequencyresponses for each PSD function that you want to consider. Thus, for this example, the computationaleffort to calculate the frequency responses is twice the amount expended when you use theANALYSIS = RANDOM capability.

Random analysis output enhancementNow when you perform a random analysis, the software automatically calculates and outputs thezero-mean crossing for the RMS von Mises stress. The zero-mean crossing for RMS von Misesstress represents the apparent (or dominant) frequency of the response.

The software calculates the zero-mean crossing for all of the elements and at all of the same locationsthat the software calculates the RMS von Mises stress. When the software calculates the zero-meancrossing, it uses the computed spectral density function of the RMS result.

In earlier versions of NX Nastran, the software automatically calculates the apparent frequency forall the RMS results except von Mises stress.

The software writes the zero-mean crossing for RMS von Mises stress results to the new OESXNOdata block.

RESVALT parameter removedBeginning with NX Nastran 12, the RESVALT parameter is removed from the software anddocumentation.

Now to exclude mass and damping effects from the residual vectors, specify the NODYNRSPdescriber on the RESVEC case control command.

Direct-input, frequency-dependent componentsIn a SOL 108 or 111 frequency response analysis, you can now define frequency-dependentcomponents by direct input of tabular dynamic stiffness versus frequency or dynamic flexibility versusfrequency data. With this capability, you can use empirically obtained dynamic stiffness or dynamicflexibility data to represent a component of an assembly.


Chapter 2: Dynamics

Dynamics

The dynamic stiffness represents the cumulative effect of inertia, damping, and stiffness withinthe component.

For example, the dynamic stiffness for an FE model is given as:

where:

ω Frequency in radians per unit time

[M] Global mass matrix

[B] Global viscous damping matrix

G Overall structural damping coefficient (PARAM,G)

[K] Global stiffness matrix

GE Structural damping coefficient of the elements (GE on material, property, orelement entries)

[KE] Stiffness matrix of the elements

The dynamic flexibility matrix is the inverse of the dynamic stiffness matrix.

The dynamic stiffness is expressed in terms of force per unit displacement (moment per unit angulardisplacement). However, you can also enter dynamic stiffness data as force per unit velocity or forceper unit acceleration (moment per unit angular velocity or moment per unit angular acceleration).

The dynamic flexibility is expressed in terms of displacement per unit force (angular displacementper unit moment). However, you can also enter dynamic flexibility data as velocity per unit force oracceleration per unit force (angular velocity per unit moment or angular acceleration per unit moment).

The values you enter for dynamic stiffness or dynamic flexibility must align with the physicalcoordinates and directions of the attachment grid points.

If you enter dynamic stiffness data in terms of velocity or acceleration, the software multiplies velocitydata by iω and acceleration data by –ω2 to convert the data to force (moment) per unit displacement(angular displacement).

If you enter dynamic flexibility data in terms of velocity or acceleration, the software divides velocitydata by iω and acceleration data by –ω2 to convert the data to force (moment) per unit displacement(angular displacement). The software then inverts the dynamic flexibility matrix to obtain the dynamicstiffness matrix.

Because the unit basis of the dynamic stiffness or flexibility data may differ from the unit basis of theFE model, you can define displacement and force scaling factors. The software uses the scalingfactors to convert the dynamic stiffness or flexibility data to the units of the FE model.

Direct frequency response analysis

For a SOL 108 direct frequency response analysis, the software:

1. Adds the dynamic stiffness of the component to the dynamic stiffness of the FE model.

2. Performs the direct frequency response analysis of the combined system.


Dynamics

Chapter 2: Dynamics

Modal frequency response analysis

For a SOL 111 modal frequency response analysis, the software:

1. Performs a real eigenvalue solution on the FE portion of the model only. During this solve, thesoftware ignores the frequency-dependent components and automatically calculates residualvectors for the interface DOF of the attachment grid points.

2. Uses the results of the real eigenvalue solution to transform the dynamic stiffness or flexibility forthe component from physical coordinates to modal coordinates.

3. Adds the transformed dynamic stiffness of the component to the modal dynamic stiffness ofthe FE model.

4. Performs the modal frequency response analysis of the combined system.

User interface requirements

You use the new FRFSTIF or FRFFLEX bulk entries to define the dynamic stiffness or dynamicflexibility for the frequency-dependent component. The dynamic stiffness or dynamic flexibility matrixyou define should represent the dynamic stiffness or dynamic flexibility expressed at the interfaceDOF of the attachment grid points. The FRFSTIF and FRFFLEX bulk entries reference the newTABLED6 bulk entries, which contain the tabular data of dynamic stiffness or dynamic flexibilityversus frequency in cycles per unit time. You use the new FRFIN case control command to trigger theaddition of the dynamic stiffness for the direct-input, frequency-dependent component to the dynamicstiffness of the FE model. When using the FRFFLEX bulk entry, you can use the FLEXINV parameterto specify the method that the software uses to invert the flexibility data into stiffness data.

For more information, see FRFIN, FRFSTIF, FRFFLEX, and TABLED6.


Chapter 2: Dynamics

Dynamics

FRFIN

Frequency-Dependent Frequency Response Function Matrix Input

Selects FRFSTIF, FRFFLEX, or FRFOTM bulk entries to define frequency-dependentfrequency response function matrices.

FORMAT:

EXAMPLES:SET 99=230,231,233FRFIN=99

DESCRIBERS:

Describer Meaning

ALL Select all FRFSTIF, FRFFLEX, and FRFOTM bulk entries.

n Set identification number of a previously appearing SETcommand. Only FRFSTIF, FRFFLEX, and FRFOTM bulk entrieswith identification numbers that appear on this SET commandare selected. (Integer>0)

NONE No FRFSTIF, FRFFLEX, and FRFOTM bulk entries are selected.(Default)

REMARKS:1. The FRFIN command must be included above any subcases.


Dynamics

Chapter 2: Dynamics

FRFSTIF

Direct-Input, Frequency-Dependent Component, Stiffness Entry

Defines the dynamic stiffness matrix at grid and scalar points for a frequency-dependentcomponent in a frequency response analysis.

The matrix is defined by a single header entry and a column entry for each columnin the matrix. The matrix must be square. The numerical data that defines thedynamic stiffness vs. frequency is contained in TABLED6 bulk entries. The dynamicstiffness data on the TABLED6 bulk entries can be defined in terms of force per unitdisplacement, velocity, or acceleration, or moment per unit angular displacement,velocity, or acceleration.

HEADERENTRY

FORMAT:

1 2 3 4 5 6 7 8 9 10FRFSTIF ID "0" TYPE SYMFLAG LSCALE FSCALE PSCALE QSCALE

COLUMN 1FORMAT:

FRFSTIF ID GRID1 COMP1

GRID1 COMP1 TID11 GRID2 COMP2 TID21

GRID3 COMP3 TID31 -etc.-

COLUMN 2FORMAT:

FRFSTIF ID GRID2 COMP2



COLUMN "N"FORMAT:

FRFSTIF ID GRIDn COMPn

GRID1 COMP1 TID1n GRID2 COMP2 TID2n

GRID3 COMP3 TID3n -etc.-

EXAMPLE:The following example represents a 4 x 4 unsymmetric dynamic stiffness matrix fora component that is connected to the residual structure at grid 80 (components 1and 3) and grid 200 (components 2 and 3). Assume the unit basis of the FE modeland the FRFSTIF are identical.FRFSTIF 101 0 VELO 1FRFSTIF 101 80 1

80 1 11 80 3 21

200 2 31 200 3 41


Chapter 2: Dynamics

Dynamics

FRFSTIF 101 80 3

80 1 12 80 3 22

200 2 32 200 3 42

FRFSTIF 101 200 2

80 1 13 80 3 23

200 2 33 200 3 43

FRFSTIF 101 200 3

80 1 14 80 3 24

200 2 34 200 3 44

FIELDS:

Field Contents

ID Unique identification number. (Integer > 0)

TYPE Type of data in TABLED6 bulk entries. See Remarks 3 and 4. (Integer= 1, 2, or 3, or character: DISP, VELO, or ACCE; Default = 1)

TYPE = 1 or DISP for force per unit displacement vs. frequency ormoment per unit angular displacement vs. frequency

TYPE = 2 or VELO for force per unit velocity vs. frequency or momentper unit angular velocity vs. frequency

TYPE = 3 or ACCE for force per unit acceleration vs. frequency ormoment per unit angular acceleration vs. frequency

SYMFLAG Symmetry flag. See Remark 5. (Integer = 0 or 1; Default = 0)

SYMFLAG = 0 for a symmetric matrix

SYMFLAG = 1 for an unsymmetric matrix

LSCALE Length scaling factor. See Remark 6. (Real > 0.0; Default = 1.0)

FSCALE Force scaling factor. See Remark 6. (Real > 0.0; Default = 1.0)

PSCALE Pressure scaling factor. See Remark 6. (Real > 0.0; Default = 1.0)

QSCALE Acoustic source strength scaling factor. See Remark 6. (Real > 0.0;Default = 1.0)

GRIDi Identification number of the ith connection grid or scalar point andcomponent combination. See Remark 7. (Integer > 0; No default)

COMPi Component of the connection grid or scalar point listed in the GRIDifield. (Any one of the integers 1 through 6 for structural grid points;1 for fluid grid points; 0, 1, or blank for scalar points; see Remark 8for default behavior)

TIDij Identification number of TABLED6 bulk entry that gives the stiffness,kij. See Remark 9. (Integer > 0; No default)


Dynamics

Chapter 2: Dynamics

REMARKS:1. The FRFIN case control command references FRFSTIF bulk entries.

2. FRFSTIF and FRFFLEX bulk entries cannot have the same identification number.

3. The software uses data expressed in terms of force per unit displacement ormoment per unit angular displacement for dynamic stiffness. However, thesoftware permits the data in TABLED6 bulk entries to be expressed in terms offorce per unit displacement, velocity, or acceleration, or moment per unit angulardisplacement, velocity or acceleration. Thus, if the TABLED6 data is expressedin terms of force per unit velocity, force per unit acceleration, moment per unitangular velocity, or moment per unit angular acceleration, the software performsthe following conversions to obtain data expressed in terms of force per unitdisplacement or moment per unit angular displacement:

• If TYPE = 2 or VELO, the software multiplies the tabular data by iω.

• If TYPE = 3 or ACCE, the software multiplies the tabular data by -ω2.

4. Angular measures must be in radians and the unit of time used to define velocity,acceleration, angular velocity, and angular acceleration must be the same as theunit of time used to define frequency.

For example, for moment per unit angular velocity vs. frequency data, if the unitof time is seconds, angular velocity must be in rad/sec and the frequency mustbe in Hz.

5. If SYMFLAG = 0, specify entries for the lower tridiagonal of the matrix only.

6. Use the LSCALE, FSCALE, PSCALE, and QSCALE fields to convert the units ofthe FRFSTIF to the units of the FE model. If TYPE = 2 or 3, the software convertsthe TABLED6 data to force per unit displacement or moment per unit angulardisplacement prior to unit conversion.

The relationship between the FRFSTIF units, FE model units, and the scalingfactors are as follows:

LFE model = LSCALE · LFRFSTIFFFE model = FSCALE · FFRFSTIFPFE model = PSCALE · PFRFSTIFQFE model = QSCALE · QFRFSTIF

For example, suppose that the FE model requires the units for dynamic stiffnessto be N/mm. If the FRFSTIF data is in lbf/in, use LSCALE = 25.4 and FSCALE= 4.448.

As a second example, suppose that the FE model requires the units for dynamicstiffness to be N-mm/rad. If the FRFSTIF data is in lbf-in/rad, use LSCALE = 25.4and FSCALE = 4.448.

After the software performs the units conversion, it adds the values to the dynamicstiffness of the model.


Chapter 2: Dynamics

Dynamics

7. Only DOF that connect the direct-input, frequency-dependent component to theresidual structure are valid GRIDi and COMPi combinations.

8. If the COMPi field corresponds to a GRIDi field that references a structural gridpoint, you must specify a component number in the COMPi field.

If the COMPi field corresponds to a GRIDi field that references a fluid grid point,you must enter "1" in the COMPi field.

If the COMPi field corresponds to a GRIDi field that references a scalar point, youcan enter "0" or "1" in the COMPi field or leave the COMPi field blank.

9. Stiffness, kij, represents the contribution to the force at the ith grid or scalar pointand component combination that results from a unit displacement, velocity, oracceleration at the jth grid or scalar point and component combination.


Dynamics

Chapter 2: Dynamics

FRFFLEX

Direct-Input, Frequency-Dependent Component, Flexibility Entry

Defines the dynamic flexibility matrix at grid and scalar points for a frequency-dependentcomponent in a frequency response analysis.

The matrix is defined by a single header entry and a column entry for each column inthe matrix. The matrix must be square. The numerical data that defines the dynamicflexibility vs. frequency is contained in TABLED6 bulk entries. The dynamic flexibilitydata on the TABLED6 bulk entries can be defined in terms of displacement, velocity,or acceleration per unit force, or angular displacement, velocity, or acceleration perunit moment.

HEADERENTRY

FORMAT:

1 2 3 4 5 6 7 8 9 10FRFFLEX ID "0" TYPE SYMFLAG LSCALE FSCALE PSCALE QSCALE

EPS

COLUMN 1FORMAT:

FRFFLEX ID GRID1 COMP1



COLUMN 2FORMAT:

FRFFLEX ID GRID2 COMP2



COLUMN "N"FORMAT:

FRFFLEX ID GRIDn COMPn

GRID1 COMP1 TID1n GRID2 COMP2 TID2n

GRID3 COMP3 TID3n -etc.-

EXAMPLE:The following example represents a 4 x 4 unsymmetric dynamic flexibility matrix fora component that is connected to the residual structure at grid 80 (components 1and 3) and grid 200 (components 2 and 3). Assume the unit basis of the FE modeland the FRFFLEX are identical.FRFFLEX 101 0 VELO 1FRFFLEX 101 80 1

80 1 11 80 3 21


Chapter 2: Dynamics

Dynamics

200 2 31 200 3 41

FRFFLEX 101 80 3

80 1 12 80 3 22

200 2 32 200 3 42

FRFFLEX 101 200 2

80 1 13 80 3 23

200 2 33 200 3 43

FRFFLEX 101 200 3

80 1 14 80 3 24

200 2 34 200 3 44

FIELDS:

Field Contents


TYPE Type of data in TABLED6 bulk entries. See Remarks 3 and 4. (Integer= 1, 2, or 3, or character: DISP, VELO, or ACCE; Default = 1)

TYPE = 1 or DISP for displacement per unit force vs. frequency orangular displacement per unit moment vs. frequency

TYPE = 2 or VELO for velocity per unit force vs. frequency or angularvelocity per unit moment vs. frequency

TYPE = 3 or ACCE for acceleration per unit force vs. frequency orangular acceleration per unit moment vs. frequency

SYMFLAG Symmetry flag. See Remark 5. (Integer = 0 or 1; Default = 0)

SYMFLAG = 0 for a symmetric matrix

SYMFLAG = 1 for an unsymmetric matrix





EPS Filter for normalized singular values. See Remark 7. (Real > 0.0;Default= 1.0E-11)

GRIDi Identification number of the ith connection grid or scalar point andcomponent combination. See Remark 8. (Integer > 0; No default)


Dynamics

Chapter 2: Dynamics

Field Contents

COMPi Component of the connection grid or scalar point listed in the GRIDifield. (Any one of the integers 1 through 6 for structural grid points;1 for fluid grid points; 0, 1, or blank for scalar points; see Remark 9for default behavior)

TIDij Identification number of TABLED6 bulk entry that gives the flexibility,cij. See Remark 10. (Integer > 0; No default)

REMARKS:1. The FRFIN case control command references FRFFLEX bulk entries.

2. FRFFLEX and FRFSTIF bulk entries cannot have the same identification number.

3. The software uses data expressed in terms of displacement per unit force orangular displacement per unit moment for dynamic flexibility. However, thesoftware permits the data in TABLED6 bulk entries to be expressed in terms ofdisplacement, velocity, or acceleration per unit force, or angular displacement,velocity or acceleration per unit moment. Thus, if the TABLED6 data is expressedin terms of velocity per unit force, acceleration per unit force, angular velocity perunit moment, or angular acceleration per unit moment, the software performs thefollowing conversions to obtain data expressed in terms of displacement per unitforce or angular displacement per unit moment:

• If TYPE = 2 or VELO, the software divides the tabular data by iω.

• If TYPE = 3 or ACCE, the software divides the tabular data by -ω2.


For example, for angular velocity per unit moment vs. frequency data, if the unitof time is seconds, angular velocity must be in rad/sec and the frequency mustbe in Hz.

5. If SYMFLAG = 0, specify entries for the lower tridiagonal of the matrix only.

6. Use the LSCALE, FSCALE, PSCALE, and QSCALE fields to convert the units ofthe FRFFLEX to the units of the FE model. If TYPE = 2 or 3, the software convertsthe TABLED6 data to displacement per unit force or angular displacement perunit moment prior to unit conversion.

The relationship between the TABLED6 units, frequency response analysis units,and the scaling factors are as follows:

LFE model = LSCALE · LFRFFLEXFFE model = FSCALE · FFRFFLEXPFE model = PSCALE · PFRFFLEXQFE model = QSCALE · QFRFFLEX


Chapter 2: Dynamics

Dynamics

For example, suppose that the FE model requires the units for dynamic flexibilityto be mm/N. If the FRFFLEX data is in in/lbf, use LSCALE = 25.4 and FSCALE= 4.448.

As a second example, suppose that the FE model requires the units for dynamicflexibility to be rad/N-mm. If the FRFFLEX data is in rad/lbf-in, use LSCALE = 25.4and FSCALE = 4.448.

After the software performs the units conversion, it inverts the direct input flexibilitymatrix to find the corresponding values for stiffness. It then adds the stiffnessvalues to the dynamic stiffness of the model.

7. The software uses the EPS value when singular value decomposition is selectedto invert the dynamic flexibility matrix into a dynamic stiffness matrix. Because thedynamic flexibility matrix may be rank deficient, the software removes near-zerosingular values prior to inversion. To do so, after the software calculates theeigenvalues, it normalizes them with respect to the eigenvalue that has the largestvalue. It then removes any eigenvalue whose normalized value is less than theEPS value. To select singular value decomposition as the inversion method,specify PARAM,FLEXINV,SVD.

8. Only DOF that connect the direct-input, frequency-dependent component to theresidual structure are valid GRIDi and COMPi combinations.

9. If the COMPi field corresponds to a GRIDi field that references a structural gridpoint, you must specify a component number in the COMPi field.

If the COMPi field corresponds to a GRIDi field that references a fluid grid point,you must enter "1" in the COMPi field.

If the COMPi field corresponds to a GRIDi field that references a scalar point, youcan enter "0" or "1" in the COMPi field or leave the COMPi field blank.

10. Flexibility, cij, represents the contribution to the displacement, velocity, oracceleration at the ith grid or scalar point and component combination that resultsfrom a unit force at the jth grid or scalar point and component combination.


Dynamics

Chapter 2: Dynamics

TABLED6

Dynamic Load Tabular Function, Form 6

Defines a tabular function of the form w(x) = u(x) + iv(x) or w(x) = |u(x)|eiv(x).FORMAT:

1 2 3 4 5 6 7 8 9 10TABLED6 TID TYPE EXTRAP

x1 u1 v1 x2 u2 v2 -etc.- “ENDT”

EXAMPLE:

TABLED6 101 MP 1

10.0 2.9 16.5 20.0 5.2 93.0

30.0 4.9 132.0 40.0 4.1 108.0 ENDT

FIELDS:

Field Contents

TID Unique table identification number. See Remark 1. (Integer > 0)

TYPE Complex format of response data. (Character: RI or MP; Default= RI)

TYPE = RI for real / imaginary

TYPE = MP for magnitude / phase

EXTRAP Extrapolation option. See Remark 4. (Integer = 0 or 1; Default = 0)

EXTRAP = 0 to extrapolate the two starting data points to obtainthe table lookup when x < xi, and extrapolate the two ending datapoints to obtain the table lookup when x > xi

EXTRAP = 1 to use the value of the table field at the starting datapoint for the table lookup when x < xi, and use the value of the tablefield at the ending data point for the table lookup when x > xi

xi Tabular values of the independent variable. (Real ≥ 0; No default)

ui Real part of the dependent variable if TYPE = RI. (Real; Default =0.0)

Magnitude of the dependent variable if TYPE = MP. (Real ≥ 0.0;Default = 0.0)

vi Imaginary part of the dependent variable if TYPE = RI. (Real;Default = 0.0)

Phase of the dependent variable in degrees if TYPE = MP. (Real;Default = 0.0)


Chapter 2: Dynamics

Dynamics

Field Contents

“ENDT” Flag indicating the end of the table.

REMARKS:1. The TID must be unique for all TABLEDi bulk entries.

2. xi must be in either ascending or descending order, but not both.

3. Discontinuities are not allowed. See Figure 2-1.

4. When EXTRAP = 0, the tabular data for the two starting or ending points arelinearly extrapolated to obtain values of x that are outside the range of the table.See Figure 2-1. Warning messages are not issued if the tabular data is inputincorrectly.

Figure 2-1. Example of Table Extrapolation and Discontinuity

5. At least one continuation entry must be present.

6. Any (xi,ui,vi) combination is ignored by placing “SKIP” in one of the three fields.

7. The end of the table is indicated by the existence of “ENDT” in the field followingthe last entry. An error is detected if any continuations follow the entry containingthe end-of-table flag “ENDT”.

8. TABLED6 interpolates the tabular data as follows:

a. If TYPE = RI, the tabular data is converted to magnitude and phase.

b. The magnitudes are linearly interpolated to obtain the lookup value.


Dynamics

Chapter 2: Dynamics

c. The phase angles are linearly interpolated to obtain the lookup value. Forthis calculation the software uses the smallest subtended angle between thephase angles that are used in the interpolation calculation.

For example, suppose a TABLED6 bulk entry is defined as follows:

TABLED6 100 MP 1 +10.0 2.9 16.5 20.0 5.2 93.0 +30.0 4.9 132.0 40.0 4.1 326.0 ENDT

The lookup value for the magnitude at x = 27.5 is:

The lookup value for the phase angle at x = 27.5 is:

The lookup value for the magnitude at x = 35.0 is:

At x = 35.0, the smallest subtended angle between 132.0° and 326° is 166.0°.Thus, the lookup value for the phase at x = 35.0 is:

9. If xi is frequency, it must be measured in cycles per unit time.

Output transformation matrices for frequency response analysisDuring results recovery in a SOL 108 or 111 frequency response analysis, the software can nowcalculate results for grid and scalar points that are not part of the FE model.

In a structural frequency response analysis, the results for these points can be linear combinations of:

• Displacement results from the FE solve.

• Time derivatives of the displacement results from the FE solve.

• Forces that the software calculates from an FRFSTIF or FRFFLEX bulk entry and thedisplacement results from the FE solve.

For an acoustic frequency response analysis, the results for these points can be linear combinationsof:

• Pressure results from the FE solve.


Chapter 2: Dynamics

Dynamics

To get these additional results, you use tabular data to define a frequency-dependent outputtransformation matrix (OTM) that the software uses to combine the results of the FE solve. The OTMrelationship can be expressed mathematically as:

where:

{x(ω)} N x 1 input vector of values that are derived from the results of the FE solve

[OTM(ω)] M x N output transformation matrix

{y(ω)} M x 1 output vector that the software calculates during results recovery

Typically, the tabular data that you use to define the OTM is obtained through physical testing.

For a SOL 111 modal frequency response analysis, the software performs the OTM calculations afterit transforms the results of the FE solve to physical coordinates.

As an example of how you might use this new capability, consider performing a frequency responseanalysis on a model that includes a direct-input, frequency-dependent component that is definedby an FRFSTIF or FRFFLEX bulk entry. When you perform such an analysis, the only results thatthe software calculates for the component during the FE solve are the responses at the DOF thatconnect the component to the FE model.

To obtain results for other points on the component, you can use the new FRFOTM bulk entry todefine an OTM that relates the results at DOF in the FE model to results at the other points on thecomponent. During results recovery, the software uses the OTM and the results of the FE solve tocalculate results for these points. You can then assign a physical meaning to the results and usethem in post-processing.

OTM in structural frequency response analysis

In a structural frequency response analysis, you can specify displacements, velocities, andaccelerations for any DOF in the FE model to populate {x(ω)}. If you are using the OTM capability inconjunction with a direct-input, frequency-dependent component that is defined by an FRFSTIF orFRFFLEX bulk entry, you can also populate {x(ω)} with loads for DOF that connect the direct-input,frequency-dependent component to the FE model.

The software calculates velocities and accelerations from the displacements. Because the motion isharmonic, the velocity and acceleration are related to the displacement as follows:

• For velocity:

• For acceleration:

where:

u Displacement result from the FE solve

ω Frequency in radians per unit time


Dynamics

Chapter 2: Dynamics

Because the unit of length for the OTM entries may differ from the unit of length used in the FE model,you can define a length scaling factor (LSCALE field on the FRFOTM bulk entry) that the softwareuses to convert the displacement results from the FE model unit of length to the OTM unit of length.

For example, suppose unit of length in the FE model is mm and the unit of length in the OTM is m.For this case, you enter 1000.0 in the LSCALE field of the FRFOTM bulk entry.

When {x(ω)} includes load entries, the software calculates the loads from the FRFSTIF matrix (or theinverse of the FRFFLEX matrix) and the displacements as follows:

Note

The inverse of an FRFFLEX matrix is equivalent to an FRFSTIF matrix. Thus, theremainder of this topic refers to the FRFSTIF matrix only.

Because the unit of length for the FRFSTIF matrix may differ from the unit of length used in the FEmodel, you can define a length scaling factor (LSCALE field on the FRFSTIF bulk entry) that thesoftware uses to convert the displacement results from the FE model unit of length to the FRFSTIFunit of length.

For example, suppose unit of length in the FE model is mm and the unit of length in the FRFSTIFF isinches. For this case, you enter 25.4 in the LSCALE field of the FRFSTIF bulk entry.

In addition, the unit of force obtained from:

may not be the same as the unit of force used in the OTM calculation. Thus, you can define aforce scaling factor (FSCALE field on the FRFOTM bulk entry) that the software uses to convert theforce units of {f(ω)} to the force units of the OTM.

For example, suppose that the OTM needs the unit of force for {f(ω)} to be N and the unit of force inthe FRFSTIFF is lbf. For this case, you enter 4.448 in the FSCALE field of the FRFOTM bulk entry.

Note

When a model includes a direct-input, frequency-dependent component that is defined byan FRFSTIF bulk entry, during the FE solve, the software uses the value in the FSCALEfield of the FRFSTIF bulk entry to convert the force units of the FRFSTIF entries to theforce unit of the FE model.

OTM in acoustic frequency response analysis

In an acoustic frequency response analysis, you can specify pressure for any DOF in the FE model topopulate {x(ω)}.

Because the unit of pressure for the OTM entries may differ from the unit of pressure used in theFE model, you can define a pressure scaling factor (PSCALE field on the FRFOTM bulk entry) thatthe software uses to convert the pressure results from the FE model unit of pressure to the OTMunit of pressure.


Chapter 2: Dynamics

Dynamics

For example, suppose the unit of pressure in the FE model is Pa and the unit of pressure in the OTMis psi. For this case, you enter 6895.0 in the PSCALE field of the FRFOTM bulk entry.

Interpreting OTM results

By default, the software does not assign physical meaning to the values in {y(ω)}.

For example, if the values in the OTM represent stiffness, and the values in {x(ω)} representdisplacement, you might assume that the software interprets the result of the OTM calculation to beforce, but it does not.

You can use the FRFOMAP bulk entry to assign a physical meaning to the values in {y(ω)}.

• In a structural frequency response analysis, you can designate values in {y(ω)} to bedisplacements, velocities, accelerations, or forces. If an entry in {y(ω)} is associated witha rotational DOF, the software automatically uses the rotational analog. That is, angulardisplacement for displacement, moment for force, and so on.

• In an acoustic frequency response analysis, you can designate values in {y(ω)} to be pressuresonly.

FRFOTM bulk entry

To define an OTM, use the new FRFOTM bulk entry as follows:

• Reference TABLED6 bulk entries that contain the tabular data that defines how each entry in theOTM varies as a function of frequency in cycles per unit time.

The TIDij fields on the FRFOTM bulk entry reference the TABLED6 bulk entries.

• Specify the DOF and type combinations that comprise {x(ω)}.

The IGRIDj and ICOMPj fields on the FRFOTM bulk entry specify the DOF. The TYPEj fieldon the FRFOTM bulk entry specifies whether to use the displacement, velocity, acceleration,or load for the DOF.

• Specify the DOF with which the values in {y(ω)} are associated.

The OGRIDi and OCOMPi fields on the FRFOTM bulk entry specify these DOF.

• Define the scaling factors that the software uses to convert the units for the displacement,force, pressure, and acoustic source strength from those used in the OTM to those used inthe FE model as follows:

FRFOMAP bulk entry

To assign physical meaning to values in {y(ω)}, use the new FRFOMAP bulk entry as follows:

• Specify the physical meaning in the YTYPEi field.


Dynamics

Chapter 2: Dynamics

• For each YTYPEi, specify all the YGRIDj and YCOMPj combinations to which to assign thatphysical meaning type.

FRFIN case control command

To trigger the software to use the FRFOTM bulk entry during results recovery, include the newFRFIN case control command in your input file.

Example problem using an OTM

Suppose you perform a structural frequency response analysis that includes a direct-input,frequency-dependent component defined by an FRFSTIF (or FRFFLEX) bulk entry and you wantthe software to calculate the following results:

where:

u1, u2,........, u5 Displacements calculated during the FE solve

f2, f5 Loads calculated during results recovery from the FRFSTIF (or FRFFLEX)matrix and displacements calculated during the FE solve

The following table maps each displacement to a grid point and displacement component combination.

Displacement Grid point Componentu1 100 3

u2 (1) 100 2u3 108 1u4 105 3

u5 (1) 112 1(1) DOF that connect the direct-entry, frequency-dependent component to the FE model

The following table maps each result to a grid point and displacement component combination.

Result Grid point Componenty1 104 2y2 121 3y3 108 2

Note

Any grid point and displacement component combination that is used as an input DOF onan FRFOTM bulk entry cannot be used as an output DOF on any FRFOTM bulk entry inthe input file. In addition, the output from one OTM cannot be the input to another OTM.


Chapter 2: Dynamics

Dynamics

Assuming the units of the FE model match the units of the OTM matrix, the following table outlineshow you specify the FRFOTM bulk entries. In the actual coding of the FRFOTM bulk entries, the cellsthat contain real values like 2.3, 3.7, and so on, actually contain integer identification numbers ofTABLED6 bulk entries that contain the numerical data.

FRFOTM 10 0

FRFOTM 10 100 3 DISP

104 2 2.3 121 3 3.7

FRFOTM 10 100 3 VELO

104 2 3.0


104 2 -4.5


121 3 6.0

FRFOTM 10 100 2 LOAD

108 2 4.1


108 2 6.3

FRFOTM 10 105 3 ACCE

121 3 8.3

FRFOTM 10 112 1 ACCE

108 2 -2.8

FRFOTM 10 112 1 LOAD

104 2 1.6

Suppose that you want to define y1 as a displacement, y2 as an acceleration, and y3 as a load. To doso, you can define an FRFOMAP bulk entry as follows:

FRFOMAP 10

DISP 104 2

ACCE 121 3

LOAD 108 2

Additional resources

For more information, see the new FRFOTM and FRFOMAP bulk entries and the new FRFIN casecontrol command.


Dynamics

Chapter 2: Dynamics

FRFOTM

Output Transformation Matrix Definition

Defines a frequency-dependent output transformation matrix (OTM) that the softwareuses during results recovery to calculate results for grid and scalar points that are notpart of the FE model as follows:

where {x(ω)} are values derived from the results of the FE solve.

The OTM is defined by a single header entry and a column entry for each column.

HEADERENTRY

FORMAT:

1 2 3 4 5 6 7 8 9 10FRFOTM ID "0" LSCALE FSCALE PSCALE QSCALE

COLUMN 1FORMAT:

FRFOTM ID XGRID1 XCOMP1 XTYPE1

YGRID1 YCOMP1 TID11 YGRID2 YCOMP2 TID21

YGRID3 YCOMP3 TID31 -etc.-

COLUMN 2FORMAT:

FRFOTM ID XGRID2 XCOMP2 XTYPE2

YGRID1 YCOMP1 TID12 YGRID2 YCOMP2 TID22


COLUMN "N"FORMAT:

FRFOTM ID XGRIDn XCOMPn XTYPEn

YGRID1 YCOMP1 TID1n YGRID2 YCOMP2 TID2n


Note

The column format for each non-null column begins with an XGRIDj,XCOMPj, and XTYPEj combination. The continuation of the columnformat lists all of the YGRIDi and YCOMPi combinations that the XGRIDj,XCOMPj, and XTYPEj combination contributes to. YGRIDi and YCOMPicombinations that do not contribute can be omitted from the list. The orderthat the YGRIDi and YCOMPi combinations are listed is arbitrary.


Chapter 2: Dynamics

Dynamics

EXAMPLE:The following example represents a 2 row by 4 column OTM where the output at grid100 (component 2) and grid 150 (component 3) are calculated as a linear combinationof the displacements at grid 80 (components 1 and 3) and the velocities at grid 200(components 2 and 3). Assume that the unit basis of the FE model and the OTMare identical.

FRFOTM 101 0FRFOTM 101 80 1 DISP

100 2 11 150 3 21FRFOTM 101 80 3 DISP

100 2 12 150 3 22


100 2 13 150 3 23


100 2 14 150 3 24

FIELDS:

Field Contents






XGRIDj Identification number of the jth input grid or scalar point. See Remark5. (Integer > 0; No default)

XCOMPj Component of the grid or scalar point listed in the XGRIDj field. SeeRemark 5. (Any one of the integers 1 through 6 for structural gridpoints; 1 for fluid grid points; 0, 1, or blank for scalar points; seeRemark 6 for default behavior)

XTYPEj Result type of the XGRIDj and XCOMPj combination. See Remarks 8and 9. (Integer = 1, 2, or 3, or character; Default = 1)

= 0 or LOAD for force or acoustic source strength

= 1 or DISP for displacement or pressure

= 2 or VELO for velocity

= 3 or ACCE for acceleration

YGRIDi Identification number of the ith output grid or scalar point. See Remark5. (Integer > 0; No default)


Dynamics

Chapter 2: Dynamics

Field Contents

YCOMPi Component of the grid or scalar point listed in the YGRIDi field. SeeRemark 5. (Any one of the integers 1 through 6 for structural gridpoints; 1 for fluid grid points; 0, 1, or blank for scalar points; seeRemark 10 for default behavior)

TIDij Identification number of TABLED6 bulk entry that corresponds to theith output grid or scalar point and component combination, and the jthinput grid or scalar point, component, and result type combination.See Remark 7. (Integer > 0; No default)

REMARKS:1. The FRFIN case control command references FRFOTM bulk entries.

2. Unlike the FRFFLEX and FRFSTIF bulk entries, the FRFOTM bulk entry does notadd stiffness to the model. Its only use is to recover results for the DOF specifiedby YGRIDi and YCOMPi combinations. The intended use for the FRFOTM bulkentry is to recover results for grid or scalar point, component, and result typecombinations on a substructure that is defined by FRFFLEX or FRFSTIF bulkentries. However, other applications are possible.

3. The OTM relates the input at XGRIDj, XCOMPj, and XTYPEj combinations to theoutput at YGRIDi and YCOMPi combinations as follows:

The OTM is an M x N matrix, where M is the total number of YGRIDi and YCOMPicombinations and N is the total number of XGRIDj, XCOMPj, and XTYPEjcombinations.

4. Use the LSCALE, FSCALE, PSCALE, and QSCALE fields to convert the units ofthe FE model to the units of the OTM as follows:

LFE model = LSCALE · LOTMFFE model = FSCALE · FOTMPFE model = PSCALE · POTMQFE model = QSCALE · QOTM

For example, enter 1000.0 in the LSCALE field if the unit of length in the FE modelis millimeters and the unit of length in the OTM is meters.

5. Any XGRIDj and XCOMPj combination that is used as an input DOF on anFRFOTM bulk entry cannot be used as a YGRIDi and YCOMPi combination onany FRFOTM bulk entry in the input file. In addition, the output from one OTMcannot be the input to another OTM.

6. If the XCOMPj field corresponds to a XGRIDj field that references a structural gridpoint, you must specify a component number in the XCOMPj field.


Chapter 2: Dynamics

Dynamics

If the XCOMPj field corresponds to a XGRIDj field that references a fluid grid point,you must enter "1" in the XCOMPj field.

If the XCOMPj field corresponds to a XGRIDj field that references a scalar point,you can enter "0" or "1" in the XCOMPj field or leave the XCOMPj field blank.


For example, for moment per unit angular velocity vs. frequency data, if the unitof time is seconds, angular velocity must be in rad/sec and the frequency mustbe in Hz.

8. XTYPEj = 0 or LOAD is a valid selection only if a FRFFLEX or FRFSTIF bulk entrywith the same ID as the FRFOTM bulk entry is present, and the correspondingXGRIDj and XCOMPj combination are DOF that connect a direct-entry,frequency-dependent component to the FE model.

9. If XTYPEj = 0 or LOAD, the software uses the FRFFLEX or FRFSTIF bulk entrywith the same ID as the FRFOTM bulk entry and the displacement results from theFE solve to calculate the load to use in the OTM calculation.

If XTYPEj = 1 or DISP, the software uses:

• In a structural frequency response analysis, the displacement result fromthe FE solve.

• In an acoustic frequency response analysis, the pressure result from the FEsolve.

If XTYPEj = 2 or VELO, the software uses the displacement result from the FEsolve multiplied by iω.

If XTYPEj = 3 or ACCE, the software uses the displacement result from the FEsolve multiplied by -ω2.

10. If the YCOMPi field corresponds to a YGRIDi field that references a structural gridpoint, you must specify a component number in the YCOMPi field.

If the YCOMPi field corresponds to a YGRIDi field that references a fluid grid point,you must enter "1" in the YCOMPi field.

If the YCOMPi field corresponds to a YGRIDi field that references a scalar point,you can enter "0" or "1" in the YCOMPi field or leave the YCOMPi field blank.


Dynamics

Chapter 2: Dynamics

FRFOMAP

Assigns Output Type to FRFOTM Results

Assigns an output type to the results calculated from FRFOTM bulk entries.FORMAT:

1 2 3 4 5 6 7 8 9 10FRFOMAP ID

YTYPE1 YGRID1 YCOMP1 YGRID2 YCOMP2 YGRID3 YCOMP3

YGRID4 YCOMP4 -etc.-

YTYPE2 YGRID1 YCOMP1 YGRID2 YCOMP2 YGRID3 YCOMP3

YGRID4 YCOMP4 -etc.-

-etc.-

ALTERNATEFORMAT:

Use to assign the same type to all output grid / component combinations.FRFOMAP ID

YTYPE1 "ALL"

EXAMPLE:This is a continuation of the example provided with the FRFOTM bulk entry. Thefollowing FRFOMAP defines the output at grid 100 (component 2) as displacementand the output at grid 150 (component 3) as velocity.FRFOMAP 101

DISP 100 2

VELO 200 3

FIELDS:

Field Contents

ID Identification number of the corresponding FRFOTM bulk entry. SeeRemark 1. (Integer > 0)

YTYPEj Type of output. (Integer = 0, 1, 2, 3, or 4, or character; Default = 0)

= 0 or NONE for user-defined

= 1 or DISP for displacement or pressure

= 2 or VELO for velocity

= 3 or ACCE for acceleration

= 4 or LOAD for load

YGRIDi Identification number of the ith output grid or scalar point andcomponent combination. See Remark 2. (Integer > 0; No default)


Chapter 2: Dynamics

Dynamics

Field Contents

YCOMPi Component of the grid or scalar point listed in the YGRIDi field. (Anyone of the integers 1 through 6 for structural grid points; 1 for fluidgrid points; 0, 1, or blank for scalar points; see Remark 3 for defaultbehavior)

ALL Assigns the specified YTYPEj to all YGRIDi and YCOMPicombinations in the FRFOTM output.

REMARKS:1. Although the use of FRFOMAP bulk entries is optional, an FRFOMAP bulk entry

can be specified for each FRFOTM bulk entry.

2. Only YGRIDi and YCOMPi combinations that are listed on the correspondingFRFOTM bulk entry are valid entries. The software assigns YTYPE = NONEto any YGRIDi and YCOMPi combinations that are listed on the correspondingFRFOTM bulk entry, but are not listed on the FRFOMAP bulk entry.

3. If the YCOMPi field corresponds to a YGRIDi field that references a structural gridpoint, you must specify a component number in the YCOMPi field.

If the YCOMPi field corresponds to a YGRIDi field that references a fluid grid point,you must enter "1" in the YCOMPi field.

If the YCOMPi field corresponds to a YGRIDi field that references a scalar point,you can enter "0" or "1" in the YCOMPi field or leave the YCOMPi field blank.


Dynamics

Chapter 3: Acoustics

Finite Element Method Adaptive Order (FEMAO)NX Nastran now supports the Finite Element Method Adaptive Order (FEMAO) method.

Finite Element Method Adaptive Order (FEMAO) is a higher-order polynomial method for acousticand vibro-acoustic analyses. It provides more accurate results and faster solve times by adapting thecomputational effort to the complexity of the analysis. You can use FEMAO with SOL 108.

Working principles of the FEMAO method

The FEMAO method adapts each element’s basis of shape functions at each frequency to provide anaccurate representation of the acoustic pressure inside the element.

The FEMAO method uses:

• Higher-order acoustic shape functions for high frequencies, large elements, or a combination ofboth.

• Lower-order acoustic shape functions for low frequencies, small elements, or a combination ofboth.

The order of shape functions in an element can be as high as polynomial order 10. At order 1, anelement that uses linear shape functions can span only 1/8 to 1/6 of a wavelength. With the standard(fixed low-order) FEM method, you need 6 to 8 elements per wavelength. The maximum admissiblefrequency would be x Hz. However, at order 10 with FEMAO, you need only about a 6/10 element perwavelength. The maximum admissible frequency would be 10x Hz. Thus, if you use FEMAO, youcan use the same mesh to compute frequencies more than 10 times higher than with standard FEM.

The following example shows the same 2D mesh with different element orders for two frequencies:

f = 100Hz f = 1000Hz



When you use FEMAO, you specify the level of accuracy you want in an NX Nastran adaptation rule.To ensure the chosen accuracy, the FEMAO method chooses the optimal polynomial order of shapefunctions per element. The order adaptation is based on the following parameters:

Parameter Modeling considerations Solver behavior

Element size

You can use larger elements forvoids and local mesh refinementnear geometric boundaries toaccurately capture the geometricof the acoustic domain (forexample, an engine surface) orwhere local variations of the fluidproperties exist.

FEMAO automatically choosesthe order per element by takingthe element size into account.

Frequency

You can use larger elementseven if you need to capture ahigh maximum frequency ofinterest in the mesh.

FEMAO uses lower-ordershape functions (lower numberDOFs per element) at lowfrequencies, and higher-ordershape functions (higher numberDOFs per element) at highfrequencies.

The solver can return themaximum admissible frequencyas a quality result.

Local speed of sound

You can define the speed ofsound using the NX Nastranmaterial bulk entries MAT10,MAT10C, MATF10C, andMATPOR.

FEMAO incorporates thespecified speed of soundper element to determine theelement order (shape functions).

Adaptation rule

You can use the NX Nastranbulk entry ACADAPT to definethe adaptation rule, and set therule to COARSE, STANDARD,or FINE.

The FINE adaptation rule usesmore higher-order elementsat lower frequencies, and forthe same mesh, the COARSEadaptation rule uses morelower-order elements at lowerfrequencies.

Polynomial order

You can use the NX Nastranbulk entry ACORDER to controlthe lowest and highest allowedpolynomial order for the entiremodel.

FEMAO automatically chooses1 for the lowest and 10 for thehighest polynomial order unlesslimits are specified.

Shape functions

A large number of polynomial shape functions is required to represent the pressure field within eachelement. In first-order, linear elements, the number of shape functions and DOFs is the same as thenumber of physical nodes in the element. In higher-order elements, the number of shape functionsand DOFs is much higher. Because FEMAO adapts the order on a per element and per frequencybasis, it allows a more efficient representation of the pressure field.



Acoustics

Note

FEMAO uses the hierarchical Lobatto shape functions, which are more flexible and efficientthan the Lagrangian shape functions used in standard (low-order) FEM. (For detailedinformation on shape functions, see Reference.)

The following table outlines typical numbers of shape functions defined on a tetrahedral element as afunction of the order.

Order External (bubble) Internal (vertex +edge + face) Total shape functions

1 4 0 42 10 0 103 20 0 204 34 1 355 52 4 566 74 10 847 100 20 1208 130 35 1659 164 56 22010 202 84 286

Four types of shape functions are shown below on a tetrahedral element:


Acoustics


FEMAO benefits

• Accuracy through element order

Standard FEM does not adjust the element order (shape functions). In standard FEM, youtypically use a single mesh for the full frequency range of the analysis, which results in anover-discretized model at lower frequencies. At higher frequencies, the standard FEM modelbecomes under-discretized and less accurate. It may even miss the targeted accuracy becauseno automatic correction is in place.



Acoustics

FEMAO, however, adjusts the element order automatically, and the model is represented eachtime with the right number of DOFs for each frequency to reach the desired accuracy.

• Performance through adaptivity

An over-discretized model results in longer solve times.

In FEMAO, however, the order adaptation for each frequency guarantees the optimal model sizeand consequently the optimal solve time for each frequency. This yields much faster computationtimes compared to the fixed number of DOFs approach that standard FEM uses.

Computation by FEMAO as a function of time and frequency

• Performance through shape function efficiency

The higher-order shape function basis is also more efficient in capturing the acoustic pressurefield within each element compared to a standard first-order or second-order elements-basedFEM approach.

For example, if you fill a volume with large elements using higher-order shape functions, whichresults in more DOFs and shape functions in a single element, and then fill the same volume withsmall elements using first-order or second-order shape functions as in standard FEM, the totalnumber of DOFs to reach the same accuracy is higher for the standard FEM than for the FEMAOmethod. Thus, FEMAO becomes more efficient as the frequency increases.

• Pre-processing

FEMAO allows you to use large elements in the acoustic domain. This results in a lean FEMAOmodel that contains fewer elements than an equivalent standard FEM model. This also meansthat you can mesh the model faster in any pre-processor, and a coarser-meshed model improvesgraphics performance.


Acoustics


The below images show the differences between a typical FEM mesh, a FEMAO mesh, and aFEMAO mesh with local refinement. For a 1 meter box, all are designed for a frequency of3000 Hz.

FEM mesh FEMAO mesh FEMAO mesh with localrefinement

A coarse mesh may not represent the boundary accurately or provide an accurate solution, so astandard FEM model must use many small elements for an accurate high-frequency solution.

In FEMAO, you should ensure that the spatial variations of the geometry, fluid properties (soundvelocity and density), and boundary conditions (velocity and admittance) are well represented bythe geometrically linear or the quadratic mesh. For this, you can use local refinement.

Example

Consider a velocity boundary condition, which is applied as acoustic panel velocity onthe fluid mesh, with spatial variations of the order of a centimeter required on two facesof the unit box. The FEM mesh (2) typically yields a poor representation. Therefore,you should use mesh local refinements (3).

However, if the vibrations originate from a meshed structural panel next to the free fluidfaces, the FEMAO mesh (2) with coarse elements at the fluid structure interface issupported. In this case, the coupling matrix also includes the higher-order DOFs ofthe coarse fluid elements. The structural mesh must be discretized finely enough tocapture the spatial variations in the velocity boundary condition it imposes on the fluid.

Maximum frequency

• The maximum frequency of a FEMAO mesh is reached when the order of any element Pef isgreater than 10. If you assume 8 elements per wavelength for linear elements, the edge size touse is

h < (1/8) * (c0 / fmax)

For higher-order elements this becomes

h < (Pef / 8) * (c0 / fmax)

This means that the maximum frequency can be estimated by



Acoustics

where:

o Pef is the order of the element.

o c0 is the speed of sound in the ambient medium.

o h is the element dimension.

However, the Lobatto shape function basis of FEMAO is more efficient compared to standardFEM. This means that at higher orders, fewer DOFs can be used per wavelength to representthe acoustic field accurately.

When the ACADAPT adaptation rule is:

o Coarse, 2.2 times fewer DOFs can be used per wavelength.

o Standard, 2 times fewer DOFs can be used per wavelength.

o Fine, 1.6 times fewer DOFs can be used per wavelength.

The maximum frequency criterion therefore becomes

Bulk entries

When you use FEMAO, make sure that your model uses the correct bulk entries:

• For a simple acoustic source, use the new acoustic monopole source ACPOLE1. Do not useACSRCE.

• For a damping and stiffness absorber, use CAABSF with the new bulk entry PAABSF1. Donot use the CAABSF/PAABSF combination.

• For gluing features, use the new ACTRAD bulk entry to enforce acoustic continuity across twosurfaces of acoustic meshes. Do not use BGSET and BGADD.

Note

The software ignores unsupported bulk entries.

Workflow

1. Create a SOL 108 acoustic or vibro-acoustic solution.


Acoustics


2. Set the following bulk entries:

a. ACADAPT to invoke the FEMAO solution and to define the adaptation (refinement) rule.

Note

The RULE parameter ensures that the numerical error stays within an acceptablerange. This allows you to perform and compare multiple solutions with the samemesh, but different RULE values.

b. ACORDER to specify the lowest and highest allowed polynomial order for FEMAO.

Reference

Efficient implementation of high-order finite elements for Helmholtz problems, Hadrien Bériot, AlbertPrinn, and Gwénaël Gabard, International Journal for Numerical Methods in Engineering, 2015.



Acoustics

ACADAPT

Order Adaptation Rule for Acoustics FEM Adaptive Order Solution (FEMAO) Method

Invokes the FEMAO method for both uncoupled acoustic and coupled vibro-acousticanalyses.

FORMAT:

1 2 3 4 5 6 7 8 9 10

ACADAPT RULE

EXAMPLE:

ACADAPT COARSE

FIELDS:

Field Contents

RULE Type of adaptation rule. (Character; "COARSE", "STANDARD", or"FINE"; Default = "STANDARD")

REMARKS:1. ACADAPT is only supported in SOL 108 acoustic or vibro-acoustic analyses.


Acoustics


ACORDER

Order for Acoustics FEM Adaptive Order (FEMAO) Method

Defines the polynomial order for the FEMAO method.FORMAT:

1 2 3 4 5 6 7 8 9 10

ACORDER ORDER NUMBER

EXAMPLES:

ACORDER MINIMUM 2

ACORDER MAXIMUM 8

FIELDS:

Field Contents

ORDER Type of adaptive order. (Character = "MINIMUM" or "MAXIMUM").See Remark 3.

NUMBER Adaptive order number. (1 ≤ Integer ≤ 10)

If ORDER = "MINIMUM", the default value for NUMBER = 1.

If ORDER = "MAXIMUM", the default value for NUMBER = 10.

REMARKS:1. ACORDER is supported in SOL 108 with FEMAO for both uncoupled acoustics

and coupled vibro-acoustic analyses.

2. The specified order is applied to the entire model.

3. If ACORDER has no arguments or does not exist, the software uses all of thefollowing arguments:

a. ORDER = "MINIMUM" and NUMBER = 1.

b. ORDER = "MAXIMUM" and NUMBER = 10.

Acoustics case control commandNX Nastran is expanded to include the new enforced acoustic pressure load with complex data input,panel normal velocity boundary condition, and monopole, dipole, and plane wave sources. Use thenew case control command ALOAD to specify these new acoustic loads, boundary condition, andsources. ALOAD can optionally reference a corresponding bulk entry ALOAD. This bulk entry allowsyou to specify a load combination, but it does not currently support scaling of loads.

For detailed information on the new acoustic loads and sources, see the Acoustics User’s Guide.



Acoustics

ALOAD

Acoustic Load Set Selection

Selects an acoustic load or source to be applied in a frequency response problem.FORMAT:

ALOAD=nEXAMPLES:

ALOAD=57

DESCRIBERS:

Describer Meaning

n Set identification of an ALOAD, ACPOLE1, ACPOLE2,ACPLNW, ACPNVEL, or ACPRESS bulk entry. (Integer > 0)

REMARKS:None.


Acoustics


ALOAD

Acoustic Load Combination with Unit Scale Factors

Defines an acoustic loading condition for frequency response as a linear combinationof load sets defined via ACPOLE1, ACPOLE2, ACPLNW, ACPNVEL, and ACPRESSbulk entries.

FORMAT:

1 2 3 4 5 6 7 8 9 10

ALOAD SID L1 L2 L3 L4 L5

L6 L7 L8 L9 L10 L11 L12 L13

-etc.-

EXAMPLE:

ALOAD 200 8 9 200

FIELDS:

Field Contents

SID Load set identification number. (Integer > 0)

Li Load set identification numbers defined on entry types listed above.(Integer > 0; No default)

REMARKS:1. Dynamic load sets must be selected in the Case Control section with ALOAD =

SID.

2. Load set IDs (Li) must be unique.

3. An ALOAD entry may not reference a set identification number defined by anotherALOAD entry.

Monopole, dipole, and plane wave acoustic sourcesNX Nastran now supports acoustic monopole, dipole, and plane wave sources in SOL 108 andSOL 111.

Acoustic monopole source

An acoustic monopole is a pulsating sound source that radiates equally in all directions.



Acoustics

Note

The plus sign means that the monopole source expands.

In NX Nastran FEM acoustics, you can create acoustic monopoles:

• Inside the meshed fluid volume at a fluid grid point or inside an element.

• Outside the meshed fluid volume.

The monopole source generates an incident sound field at a location of a distance R due given by

where:

• is the monopole amplitude.

• R is the distance from the source.

• k is the wave number.

The monopole source can also be specified by its volume velocity Qs. The relationship between the

monopole amplitude and volume velocity is given by

Another method you can use to specify the monopole source is to use its acoustic power.


Acoustics


where:

• is the fluid density.

• c is the speed of sound.

You use the new bulk entry ACPOLE1 to specify a monopole source.

• The bulk entry supports power and monopole amplitude inputs that can be constant or frequencydependent.

• In ACPOLE1, the source location is defined by the coordinate that can be inside or outside ofthe meshed fluid volume. For sources outside the FEM mesh, you specify an AMLREG on allor part of the free faces of the fluid model. This captures the effect of the monopole incidentfield inside the fluid domain.

• ACPOLE1 inherits the density and speed of sound from the location of the monopole source. Ifthe source is outside the meshed fluid volume, the fluid properties are acquired by averagingthe properties used in those fluid elements that their free faces are used in the definition ofthe AMLREG.

Acoustic dipole source

The dipole source can be visualized as an oscillating sphere with no deformation as shown in theimage below. The fluid near the source moves back and forth to produce sound. Unlike a monopolesource, the sound does not radiate equally in all directions.

Also, the dipole source can be visualized as two out-of-phase monopole sources separated by adistance, where one monopole contracts (- sign) and the other one (+ sign) expands. In this case, thedipole generates a sound field that can be written as



Acoustics

(1) Evaluation point

where:

• d is the distance between two out of phase monopole sources.

• r is the line that connects the midpoint between the monopole sources and the evaluation point (1).

• is the angle between the line that connects those monopole sources and the line that connectsthe evaluation point (1) and the midpoint between the monopole sources.

To specify the dipole source in your simulation, you define the dipole moment Sd

where:

• S is the source strength.

• d is the direction vector.

You use the new ACPOLE2 bulk entry to specify a dipole source. The bulk entry supports:

• The definition of the dipole moment in a coordinate system.

• The source location inside or outside the meshed fluid volume. If the source is outside themeshed fluid volume, you must define an AMLREG bulk entry to account correctly for the incidentfield from the dipole.

Acoustic plane wave source

A plane wave source generates a plane wave on only one side of the space, in the positive directionof the source vector.


Acoustics


(1) Incident field

(2) Vector

(3) Position

(4) Non-incident field

The incident acoustic pressure pi due to a plane wave source is

where:

• A is the amplitude of the plane wave.

• k is the wave number.

• d is the perpendicular distance from the plane source.

Note

• NX Nastran uses surface integration to compute acoustic power. For a monopolesource, you can create a spherical microphone mesh that encloses the source, andthe software computes the acoustic power on this sphere. This also means that youcan define acoustic power for a monopole source. However, for plane waves, youcannot define acoustic power because the plane waves are infinitely large in terms ofdirection, and the surface integration would result in infinite numbers.

• You can use a preprocessor, such as Pre/Post, to create a collection of discrete planewave sources equally distributed in space that model an acoustic diffuse field. Thiscollection is usually used for a random vibro-acoustic analysis.

You use the new bulk entry ACPLNW to specify a plane wave acoustic source and define location,direction, and amplitude that can be constant or frequency dependent.

If the monopole, dipole, and plane wave sources are outside of the meshed fluid volume, you mustdefine an AMLREG bulk entry to correctly account for the incident field of these sources inside themeshed fluid volume. Also, in this case, a new incident-scattered formulation is used in NX NastranFEM acoustics.



Acoustics

ACPOLE1

Acoustic Monopole Source

Defines an acoustic monopole sourceFORMAT:

1 2 3 4 5 6 7 8 9 10

ACPOLE1 SID TYPE FORM A TR/TM TI/TP

CID X1 X2 X3

EXAMPLES:

ACPOLE1 200 POWER PHASE 2.0 300 60.0

FIELDS:

Field Contents


TYPE Monopole source type. (Character; "AMP" or "POWER"; Default= AMP)

If TYPE = AMP, define the monopole source in terms of sourceamplitude.

If TYPE = POWER, define the monopole source in terms of power.

FORM Format to define the monopole amplitude or power. (Character;"REAL" or "PHASE"; Default = REAL)

If FORM = REAL, define the monopole amplitude in rectangularformat (real and imaginary).

If FORM = PHASE, define the monopole amplitude or power in polarformat (magnitude and phase). See Remark 3.

A Scale factor for TR, TI, or TM. (Real; Default = 1.0)

TR Real part of the amplitude of monopole source. (Real or Integer;Default = 0.0)

For a constant amplitude, enter a real value.

For a frequency-dependent amplitude, enter the ID of the TABLEDibulk entry that contains the amplitude as a function of frequency.


Acoustics


Field Contents

TM Magnitude of the amplitude or power of monopole source. (Real orInteger; Default = 0.0)

For a constant amplitude or power, enter a real value.

For a frequency-dependent amplitude or power, enter the ID of theTABLEDi bulk entry that contains the amplitude as a function offrequency.

TI Imaginary part of the amplitude of monopole source. (Real or Integer;Default = 0.0)


For a frequency-dependent amplitude, enter the ID of the TABLEDibulk entry that contains the amplitude as a function of frequency.

TP Phase angle in degrees of the amplitude or the power of monopolesource. (Real or Integer; Default = 0.0)

For a constant amplitude or power, enter a real value.

For a frequency-dependent amplitude or power, enter the ID of theTABLEDi bulk entry that contains the amplitude as a function offrequency.

CID Identification number of coordinate system in which the location ofmonopole is defined. (Integer ≥ 0 or blank; Default = blank). SeeRemark 4.

X1, X2, X3 Location of monopole source in coordinate system CID. (Real;Default= 0.0)

REMARKS:1. ACPOLE1 is supported by the FEM Adaptive Order (FEMAO) method.

2. The SID must be unique with respect to ALOAD.

3. If TYPE = POWER, the FORM can only be defined as PHASE.

4. A CID of zero or blank (the default) references the basic coordinate system.

5. You can also define a monopole source with the ACSRCE bulk entry. However,ACSRCE is not supported by FEMAO.



Acoustics

ACPOLE2

Acoustic Dipole Source

Defines an acoustic dipole sourceFORMAT:

1 2 3 4 5 6 7 8 9 10

ACPOLE2 SID FORM CID1 X1 X2 X3

CID2 A1 TR1/TM1 TI1/TP1 A2 TR2/TM2 TI2/TP2

A3 TR3/TM3 TI3/TP3

EXAMPLES:

ACPOLE2 300 REAL 2 1.0 1.0 1.00.1 0.1 0.2 0.2

FIELDS:

Field Contents


FORM Format to define the dipole moment. (Character; "REAL" or "PHASE";Default = REAL)

If FORM = REAL, define the dipole moment in rectangular format(real and imaginary).

If FORM = PHASE, define the dipole moment in polar format(magnitude and phase).

CID1 Identification number of coordinate system in which the location ofdipole is defined. (Integer ≥ 0 or blank; Default = blank). See Remark3.

X1, X2, X3 Location of dipole source in coordinate system CID1. (Real; Default =0.0)

CID2 Identification number of coordinate system in which the dipole momentis defined. (Integer ≥ 0 or blank; Default = blank). See Remark 3.

Ai The scale factor for TRi, TIi, or TMi. (Real; Default = 1.0)

TRi Real part of dipole moment in the coordinate system CID2. (Realor Integer; Default = 0.0)

For a constant moment, enter a real value.

For a frequency-dependent moment, enter the ID of the TABLEDi bulkentry that contains the moment as a function of frequency.


Acoustics


Field Contents

TMi Magnitude of dipole moment in the coordinate system CID2. (Realor Integer; Default = 0.0)



TIi Imaginary part of dipole moment in the coordinate system CID2. (Realor Integer; Default = 0.0)



TPi Phase angle in degrees of dipole moment. (Real or Integer; Default =0.0)

For a constant phase angle, enter a real value.

For a frequency-dependent phase angle, enter the ID of the TABLEDibulk entry that contains the phase angle as a function of frequency.

REMARKS:1. ACPOLE2 is supported by the FEM Adaptive Order (FEMAO) method.


3. A CID1 or CID2 of zero or blank (the default) references the basic coordinatesystem.



Acoustics

ACPLNW

Acoustic Plane Wave Source

Defines an acoustic plane wave source.FORMAT:

1 2 3 4 5 6 7 8 9 10

ACPLNW SID FORM A TR/TM TI/TP

CID1 X1 X2 X3 CID2 N1 N2 N3

EXAMPLES:

ACPLNW 200 PHASE 0.5 20.2 100.0 0.0 0.0 3 0.0 1.

FIELDS:

Field Contents


FORM Format to define the plane wave amplitude. (Character; "REAL" or"PHASE"; Default = REAL)

If FORM = REAL, define the plane wave amplitude in rectangularformat (real and imaginary).

If FORM = PHASE, define the plane wave amplitude in polar format(magnitude and phase).


TR Real part of plane wave amplitude. (Real or Integer; Default = 0.0)

For a constant real amplitude, enter a real value.

For a frequency-dependent amplitude, enter the ID of the TABLEDibulk entry that contains the real amplitude as a function of frequency.

TM Magnitude of plane wave amplitude. (Real or Integer; Default = 0.0)


For a frequency-dependent amplitude, enter the ID of the TABLEDibulk entry that contains the magnitude as a function of frequency.

TI Imaginary part of plane wave amplitude. (Real or Integer; Default =0.0)

For a constant imaginary amplitude, enter a real value.

For a frequency-dependent amplitude, enter the ID of the TABLEDibulk entry that contains the imaginary amplitude as a function offrequency.


Acoustics


Field Contents

TP Phase angle in degrees of plane wave amplitude. (Real or Integer;Default = 0.0)


For a frequency-dependent phase angle, enter the ID of the TABLEDibulk entry that contains the phase angle as a function of frequency.

CID1 Identification number of coordinate system in which the location ofplane wave is defined. (Integer ≥ 0 or blank; Default = blank). SeeRemark 3.

X1, X2, X3 Location of plane wave in coordinate system CID1. (Real; Default=0.0)

CID2 Identification number of coordinate system in which the direction ofplane wave is defined. (Integer ≥ 0 or blank; Default = blank). SeeRemark 3.

N1, N2, N3 Direction of plane wave in coordinate system CID2. (Real; Default=0.0)

REMARKS:1. ACPLNW is supported by the FEM Adaptive Order (FEMAO) method.


3. A CID1 or CID2 of zero or blank (the default) references the basic coordinatesystem.

4. N1, N2, and N3 cannot be all equal to zero.

Enforced acoustic pressure with complex data inputWhen acoustic pressures on certain grids are known beforehand (for example, the pressures areidentified through measurement or previous calculation), you can apply them using the new enforcedacoustic pressure card ACPRESS. SOL 108 and SOL 111 acoustic and vibro-acoustic solutionssupport ACPRESS.

ACPRESS supports complex data and the definition of:

• Magnitude and phase of pressure on multiple grids.

• Constant and frequency dependency.



Acoustics

Note

NX Nastran adds the degrees of freedom referenced by ACPRESS to the s-set. Fordetailed information on the s-set, see the Understanding Sets and Matrix Operationschapter in the User’s Guide.

Prior to NX Nastran 12, you can define enforced acoustic pressure with the RLOAD1, SPC1, andSPCD bulk entries.


Acoustics


ACPRESS

Enforced Pressure Value on Grids

Defines an enforced pressure value for a frequency response analysisFORMAT:

1 2 3 4 5 6 7 8 9 10

ACPRESS SID FORM A TR/TM TI/TP G1

G2 G3 "THRU" G4 "BY" n G5 G6

-etc.-

EXAMPLES:

ACPRESS 200 REAL 1.0 -3.0 5001

FIELDS:

Field Contents


FORM Format to define the pressure value. (Character; "REAL" or "PHASE";Default = REAL)

If FORM = REAL, define the pressure in rectangular format (real andimaginary).

If FORM = PHASE, define the pressure in polar format (magnitudeand phase).


TR Real part of pressure. (Real or Integer; Default = 0.0)

For a constant pressure, enter a real value.

For a frequency-dependent pressure, enter the ID of the TABLEDibulk entry that contains the pressure as a function of frequency.

TM Magnitude of the pressure. (Real or Integer; Default = 0.0)



TI Imaginary part of the pressure. (Real or Integer; Default = 0.0)





Acoustics

Field Contents

TP Phase angle in degrees of the pressure. (Real or Integer; Default =0.0)


For a frequency-dependent phase angle, enter the ID of the TABLEDibulk entry that contains the pressure as a function of frequency.

Gi Grid identification number. (Integer > 0; No default)

G3"THRU"G4

Grid identification number. (G4 > G3; Integer > 0; No default)

"BY" Specifies an increment for a THRU specification. (Character; Nodefault)

n Increment for THRU range. (Integer > 0; No default)

REMARKS:1. ACPRESS is supported by the FEM Adaptive Order (FEMAO) method.


3. The continuation field is optional.

Boundary conditionsNX Nastran now supports acoustic panel normal velocity, constant real and imaginary impedanceand admittance, and transfer admittance boundary conditions in SOL 108 and SOL 111. Theacoustic panel normal velocity and transfer admittance boundary conditions are required for acousticworkflows such as muffler transmission loss. Transmission Loss is a measure of a product’s abilityto reduce sound.

Acoustic panel normal velocity

NX Nastran supports an acoustic panel normal velocity boundary that can be applied to 2D acousticelement faces, for example, free faces of a 3D fluid element. This velocity boundary can be:

• Used to represent acoustically rigid yet vibrating panels. In such case, the applied panel velocitycorresponds with the particle velocity of the fluid in front of the panels.

• Combined with an acoustic impedance or admittance on the same panel. In such case, theacoustic panel normal velocity represents the structural vibration of an acoustically treated andtherefore soft panel. Also, the particle velocity of the fluid in front of the panel is different from thestructural panel velocity, which is pre-defined.

You use the new bulk entry ACPNVEL to specify the boundary. ACPNVEL supports the definition of:


Acoustics


• Magnitude and phase of acoustic velocity.

• Constant or frequency-dependent complex velocity.

Impedance or admittance

Prior to NX Nastran 12, the acoustic absorber element CAABSF defines frequency-dependentimpedance or admittance boundary conditions. When CAABSF references the physical propertyPAABSF, it supports the constant equivalent structural damping coefficient B and stiffness coefficientK.

Beginning with NX Nastran 12, constant real and imaginary impedance and admittance is alsosupported on a 2D fluid free surface when CAABSF references the new physical property PAABSF1.

Note

• Parabolic element faces are also supported because only corner grids are used todefine the element faces.

• Point and line impedance are not supported in the acoustic method introduced in NXNastran 11 which includes AML, porous materials, and microphone elements.

• Point and line impedance are only supported through CAABSF that referencesPAABSF if the system cell 617 (ACFORM) is set to 0. ACFORM = 0 reverts to the NXNastran 10 acoustics behavior.

• While PAABSF is not supported by the FEM Adaptive Order (FEMAO) method,PAABSF1 is supported by both the standard FEM and the FEM Adaptive Order(FEMAO) method.

Transfer admittance

NX Nastran 12 supports the definition of transfer admittance between two sets of acoustic free facesfor SOL 108 and SOL 111. The transfer admittance defines a relationship between the acousticvelocities and the pressures on one side of the surface, and the acoustic velocities and the pressureson the other side of the surface. You use the new bulk entry ACTRAD that references PACTRAD tospecify the transfer admittance.

The admittance can be measured, calculated from Mechel's formula, or derived from transfermatrices. In its most general form, the transfer admittance is expressed as

where:

• n1 is the normal velocity on the nodes of the face selection.

• n2 is the normal velocity on the nodes of the second face selection.



Acoustics

• 1 is the pressure on the nodes of the first face selection.

• 2 is the pressure on the nodes of the second face selection.

• 1, 2, 4, and 5 are complex admittance coefficients.

• 3 and 6 are complex source coefficients.

The six coefficients 1 through 6 are determined by the nature of the relation. Because thesecoefficients have the dimension [velocity/pressure], they are called transfer admittance coefficients.

Note

The matrix element values depend on the structure between the nodes defined at twosides of the surface. For example, in a physical problem, the two sides represent two sidesof a wall that contains perforations. Instead of modeling the perforations by using manysmall elements, you model only the volumes on both sides of the wall, and you capturethe effect of the perforations, which causes the acoustic results between both sides of thewall to be coupled, through the transfer admittance matrix.

In this case, the nature of the relation encompasses the number of holes and their porosity,the viscosity of the fluid in the holes, and so on. These are the parameters in the Mechel'sformula to derive the transfer admittance values.


Acoustics


ACPNVEL

Acoustic Panel Normal Velocity

Defines panel normal velocity on fluid free surfaces.FORMAT:

1 2 3 4 5 6 7 8 9 10

ACPNVEL SID FORM A TR/TM TI/TP BID

EXAMPLES:

ACPNVEL 200 REAL 0.2 0.5 300

FIELDS:

Field Contents


FORM Format to define the panel normal velocity. (Character; "REAL" or"PHASE"; Default = REAL)

If FORM = REAL, define the panel normal velocity in rectangularformat (real and imaginary).

If FORM = PHASE, define the panel normal velocity in polar format(magnitude and phase).


TR Real part of velocity. (Real or Integer; Default = 0.0)

For a constant velocity, enter a real value.

For a frequency-dependent velocity, enter the ID of the TABLEDi bulkentry that contains the velocity as a function of frequency.

TM Magnitude of velocity. (Real or Integer; Default = 0.0)



TI Imaginary part of velocity. (Real or Integer; Default = 0.0)





Acoustics

Field Contents

TP Phase angle in degrees of velocity. (Real or Integer; Default = 0.0)


For a frequency-dependent phase angle, enter the ID of the TABLEDibulk entry that contains the velocity as a function of frequency.

BID Identification number of BSURFS bulk entry that normal velocity isapplied to. (Integer > 0; No default)

REMARKS:1. ACPNVEL is supported by the FEM Adaptive Order (FEMAO) method.



Acoustics


PAABSF1

Acoustic Impedance or Admittance Element Property

Defines the properties of a frequency-dependent acoustic impedance or admittanceelement.

FORMAT:

1 2 3 4 5 6 7 8 9 10

PAABSF1 PID PTYPE FORM ZR ZI

EXAMPLE:

PAABSF1 100 IMP -0.01 20.0

FIELDS:

Field Contents

PID Property identification number that matches the identification numberof the corresponding CAABSF entry. (Integer > 0)

PTYPE Type of the acoustic element property. (Character; "IMP" or "ADM";Default = IMP)

If PTYPE = IMP, define the impedance property.

If PTYPE = ADM, define the admittance property.

FORM Format to define the impedance or admittance. (Character; Default =REAL)

If FORM = REAL, define the impedance or admittance in rectangularformat (real and imaginary).

If FORM = PHASE, define the impedance or admittance in polarformat (magnitude and phase).

ZR Real part of impedance or admittance. (Real or Integer; Default = 0.0)

For a constant impedance or admittance, enter a real value.

For a frequency-dependent impedance or admittance, enter the ID ofthe TABLEDi bulk entry that contains the impedance or admittance asa function of frequency. See Remark 2.

ZI Imaginary part of impedance or admittance. (Real or Integer; Default= 0.0)

For a constant impedance or admittance, enter a real value.

For a frequency-dependent impedance or admittance, enter the ID ofthe TABLEDi bulk entry that contains the impedance or admittance asa function of frequency. See Remark 2.



Acoustics

REMARKS:1. CAABSF in combination with PAABSF1 is supported by the FEM Adaptive Order

(FEMAO) method.

2. ZR and ZI cannot both be equal to zero.


Acoustics


ACTRAD

Acoustic Transfer Admittance

Defines transfer admittance for acousticsFORMAT:

1 2 3 4 5 6 7 8 9 10

ACTRAD TID PID BIDS BIDT AREA SDIST ANGLE

EXAMPLES:

ACTRAD 300 400 5 6 0.001 30.

FIELDS:

Field Contents

TID Identification number of transfer admittance. (Integer > 0)

PID Identification number of the PACTRAD bulk entry. (Integer > 0 orblank; Default = blank). See Remark 3.

If PID = blank, the transfer admittance continuity is defined betweenthe source and target region.

BIDS Acoustic source region identification number for transfer admittancepairing. (Integer > 0; Default = blank)

BIDT Acoustic target region identification number for transfer admittancepairing. (Integer > 0; Default = blank)

AREA Area correction factor. (Real ≥ 0.0; Default = 0.0). See Remark 3.

SDIST Search distance for transfer admittance region. (Real > 0.0; Default= 10.0)

Angle Angular tolerance in degrees used to decide whether the acousticsource and target region can be considered as overlapping.

If the angle between the normal of the acoustic source and targetregion exceeds this value, they cannot be coupled. (Real > 0.0;Default = 60.0)

REMARKS:1. ACTRAD is supported by the Finite Element Method Adaptive Order (FEMAO)

method.

2. The TID must be unique with respect to ACTRAD.

3. If PID = blank, the AREA input is ignored.

If AREA = blank or 0.0, the solver automatically computes the area correctionfactor.



Acoustics

If AREA > 0.0, the input value is used.


Acoustics


PACTRAD

Property of Acoustic Transfer Admittance

Defines the property of transfer admittance for acoustics.FORMAT:

1 2 3 4 5 6 7 8 9 10

PACTRAD PID A1R A1I A2R A2I A3R A3I

A4R A4I A5R A5I A6R A6I

EXAMPLES:

PACTRAD 300 0.3 0.3 0.4 0.4 0.5 0.5

0.6 0.6 0.1 0.1 0.2 0.2

FIELDS:

Field Contents

PID Identification number of the parameters of acoustic transferadmittance. (Integer > 0)

AiR

(i =1,2,3...)

Real parameters for transfer admittance. (Real or Integer; Default =0.0)

For a constant transfer admittance, enter a real value.

For a frequency-dependent transfer admittance, enter the ID of theTABLEDi bulk entry that contains the transfer admittance as a functionof frequency. See Remark 3.

AiI

(i =1,2,3...)

Imaginary parameters for transfer admittance. (Real or Integer;Default = 0.0)

For a constant transfer admittance, enter a real value.

For a frequency-dependent transfer admittance, enter the ID of theTABLEDi bulk entry that contains the transfer admittance as a functionof frequency. See Remark 3.

REMARKS:1. The PID must be unique with respect to each PACTRAD.

2. AiR and AiI cannot both be equal to zero, except for 3 and 6.

3. Ai are the transfer admittance coefficients that define the relationship of normalvelocity and pressure between the two surfaces.

In its most general form, this relationship is expressed as



Acoustics

where:

• n1 is the normal velocity on the nodes of the first face selection or normalvelocity on the positive sides of the element selection.

• n2 is the normal velocity on the nodes of the second face selection or normalvelocity on the negative sides of the element selection.

• 1 is the pressure on the nodes of the first face selection or pressure on thepositive sides of the element selection.

• 2 is the pressure on the nodes of the second face selection or pressure onthe negative sides of the element selection.

• 1, 2, 4, and 5 are complex admittance coefficients.

• 3 and 6 are complex source coefficients.

The six coefficients 1 through 6 are determined by the nature of the relation(see Acoustics User's Guide). Because these coefficients have the dimension[velocity/pressure], they are called transfer admittance coefficients.

Acoustic materials with complex propertiesThe new acoustic material bulk entries MAT10C and MATF10C allow users to input complex densityand speed of sound for SOL 108 and 111.

• MAT10C allows you to define constant or nominal properties.

• MATF10C allows you to define material properties in tabular format.

For example, in a SOL111, when a modal analysis is first performed, the nominal value is used tocalculate the eigenvalue and eigenvector. In the frequency response, however, the actual value isused if MATF10C is specified.


Acoustics


MAT10C

Fluid or Absorber Material Property Definition in Complex Format

Defines constant or nominal material properties for fluid or absorber elements incoupled fluid-structural analysis.

FORMAT:

1 2 3 4 5 6 7 8 9 10

MAT10C ID FORM RHOR RHOI CR CI

EXAMPLE:

MAT10C 100 3 -0.01 20.0 5

FIELDS:

Field Contents

ID Material identification number. (Integer > 0)

FORM Format to define the fluid density and speed of sound. (Character;"REAL" or "PHASE"; Default = REAL)

If FORM = REAL, define the fluid density and speed of sound inrectangular format (real and imaginary).

If FORM = PHASE, define the fluid density and speed of sound inpolar format (magnitude and phase).

RHOR Real part of density. (Real; Default = 0.0)

RHOI Imaginary part of density. (Real; Default = 0.0)

CR Real part of speed of sound. (Real; Default = 0.0)

CI Imaginary part of speed of sound. (Real; Default = 0.0)

REMARKS:1. RHOR and RHOI cannot both be equal to zero.

2. CR and CI cannot both be equal to zero.



Acoustics

MATF10C

Fluid or Absorber Material Property Definition in Complex Format

Defines tabular material properties for fluid or absorber elements in coupledfluid-structural analysis.

FORMAT:

1 2 3 4 5 6 7 8 9 10

MATF10C ID TIDRHOR TIDRHOI TIDCR TIDCI

EXAMPLE:

MATF10C 100 501 502 601 602

FIELDS:

Field Contents

ID Material identification number. (Integer > 0)

TIDRHOR Identification number of TABLEDi bulk entry which defines the realpart of density. (Integer > 0; Default = 0)

TIDRHOI Identification number of TABLEDi bulk entry which defines theimaginary part of density. (Integer > 0; Default = 0)

TIDCR Identification number of TABLEDi bulk entry which defines the realpart of speed of sound. (Integer > 0; Default=0)

TIDCI Identification number of TABLEDi bulk entry which defines imaginarypart of speed of sound. (Integer > 0; Default=0)

REMARKS:1. If TIDRHOR, TIDRHOI, TIDCR, or TIDCI field = blank, the corresponding value

specified in MAT10C will be used in the computation.

2. TIDRHOR, TIDRHOI, TIDCR, or TIDCI cannot be all equal to zero.

3. MATF10C will be used only when MAT10C with the same ID is specified.

4. The FORM specified in MAT10C bulk entry will be applied to MATF10C bulk entry.

Acoustic pressure resultsPRESSURE and DISPLACEMENT case control commands are no longer interchangeable. You cannow use the PRESSURE case control command to request only the output of acoustic pressureresults at fluid points. Thus, the pressure results are separated from the displacement results inthe NX Nastran results file.

You can also use this case control command to obtain acoustic pressure at fluid grids referenced bymicrophone elements.


Acoustics


Note

• The new system cell 640 (PRESOUT) is available to revert to the pre-NX Nastran12 behavior, where DISPLACEMENT and PRESSURE case control commands areinterchangeable.

• If you submit a legacy input file that contains a DISPLACEMENT case controlcommand requesting pressure output at fluid grids and system cell 640 (PRESOUT):

= 1 (Default), NX Nastran only outputs the displacements.

= 0, NX Nastran reverts to the pre-NX Nastran 12 behavior.

Also, the bulk entries RCROSS and RCROSSC that define the quantities for computing cross-powerspectral density and cross-correlation functions in a random analysis are enhanced by includingan acoustic response quantity type.



Acoustics

PRESSURE

Pressure Output Request for Fluid Grid Points

Requests the form and type of pressure output for fluid grid points.FORMAT:

EXAMPLES:PRESSURE=5PRESSURE(REAL)=ALLPRESSURE(SORT2,PUNCH,REAL)=ALL

DESCRIBERS:

Describer Meaning

SORT1 Output is presented as a tabular listing of grid points for eachload, frequency, eigenvalue, or time, depending on the solutionsequence. (Default)

SORT2 Output is presented as a tabular listing of load, frequency ortime for each grid point.

PRINT The printer is the output medium. (Default)

PUNCH The punch file is the output medium.

PLOT Generates, but does not print, pressure data.

REAL or IMAG Requests rectangular format (real and imaginary) of complexoutput. Use of either REAL or IMAG yields the same output.(Default)

PHASE Requests polar format (magnitude and phase) of complexoutput. Phase output is in degrees.


Acoustics


Describer Meaning

TOTAL Outputs the total pressure for the incident-scatteredformulation. (Default)

SCATR Outputs the scattered pressure for the incident-scatteredformulation.

PSDF Requests that the power spectral density function becalculated for random analysis post-processing. The requestmust be made above the subcase level and RANDOM mustbe selected in the Case Control. See Remark 4.

ATOC Requests that the autocorrelation function be calculated forrandom analysis post-processing. The request must be madeabove the subcase level and RANDOM must be selected inthe Case Control. See Remark 4.

CRMS Requests that the cumulative root mean square function becalculated for random analysis post-processing. Request mustbe made above the subcase level and RANDOM must beselected in the Case Control. See Remark 4.

RMS Requests that the root mean square and zero crossingfunctions be calculated for random analysis post-processing.Request must be made above the subcase level and RANDOMmust be selected in the Case Control. (Default) See Remark 4.

RALL Requests that all of PSDF, ATOC, RMS, and CRMS becalculated for random analysis post-processing. The requestmust be made above the subcase level and RANDOM mustbe selected in the Case Control. See Remark 4.

RPRINT Writes random analysis results to the print file. (Default) SeeRemark 4.

NORPRINT Disables the writing of random analysis results to the print file.See Remark 4.

RPUNCH Writes random analysis results to the punch file. See Remark4.

ALL Outputs acoustic pressure for all points.

NONE Outputs acoustic pressure for no points.(Default)

n Sets identification of a previous SET command. Only acousticpressure of points with identification numbers that appear onthis SET command are output. (Integer > 0)

REMARKS:1. Both PRINT and PUNCH may be requested.



Acoustics

2. By default, the PRESSURE case control command requests pressure output atfluid grid points only and the DISPLACEMENT case control command requestsdisplacement at structural grid points only. In versions prior to NX Nastran 12, thePRESSURE and DISPLACEMENT case control commands were interchangeable.Use SYSTEM(640) to revert to the pre-NX Nastran 12 behavior.

3. PRESSURE = NONE overrides an overall output request.

4. The following applies to random solutions:

• By default, frequency response results are not output. If you want both randomoutput and frequency response output, specify SYSTEM(524) = 1 or RANFRF= 1 in the input file. The PRINT, PUNCH, and PLOT describers controlthe frequency response output. The RPRINT, NORPRINT, and RPUNCHdescribers control the random output.

• The SORT1 and SORT2 describers control the output format for the frequencyresponse output only. The output format for random results is controlledusing the RPOSTS1 describer on the RANDOM case control command orthe parameter RPOSTS1, except for RMS results, which are only availablein SORT1 format.

• You can select any combination of the PSDF, ATOC, RMS, and CRMSdescribers. The RALL describer selects all four.

• Autocorrelation (ATOC) calculations require the RANDT1 bulk entry.

5. Any structural points that you include in SET = n are ignored.

6. During a SOL 108 or SOL 111 frequency-dependent external superelementcreation run, on the SET case control command that is referenced by thePRESSURE case control command, include any points at which you want torecover results during the system run.


Acoustics


RCROSS

Cross-Power Spectral Density and Cross-Correlation Function Output

Defines a pair of response quantities for computing the cross-power spectral densityand cross-correlation functions in random analysis.

FORMAT:

1 2 3 4 5 6 7 8 9 10

RCROSS SID RTYPE1 ID1 COMP1 RTYPE2 ID2 COMP2 CURID

EXAMPLES:

RCROSS 20 DISP 50 2 STRESS 150 8 4

RCROSS 200 PRESS 101 1 DISP 50 2

FIELDS:

Field Contents

SID Case control RCROSS identification number for cross-power spectraldensity and cross-correlation functions. (Integer>0)

RTYPEi Type of response quantity. At least one field must be selected. SeeRemark 2. (Character or blank)

IDi Element, grid, or scalar point identification number. (Integer > 0)

COMPi Component code (item) identification number. See Remark 3. (Integer> 0)

CURID Curve identification number. See Remark 5. (Integer > 0 or blank)

REMARKS:1. This entry is required for computing the cross-power spectral density and

cross-correlation functions. SID must be selected with the case control command(RCROSS=SID). Fields RTYPE1, ID1, and COMP1 represent the first responsequantity; fields RTYPE2, ID2, and COMP2 represent the second response quantity.



Acoustics

2. The keywords for field RTYPEi are listed as follows:

Keyword Meaning

DISP Displacement Vector

VELO Velocity Vector

ACCEL Acceleration Vector

OLOAD Applied Load Vector

SPCF Single-point Constraint Force Vector

MPCF Multi-point Constraint Force Vector

STRESS Element Stress

STRAIN Element Strain

FORCE Element Force

PRESS Acoustic Pressure

If either RTYPE1 or RTYPE2 is blank, then the blank field takes the default fromthe defined field.

3. For elements, the item code COMPi represents a component of the element stress,strain or force and is described in Tables “Element Stress-Strain Item Codes” and“Element Force Item Codes”. For an item having both a real and imaginary part,the code of the real part must be selected. This is required for computing both thecross-power spectral density function and cross-correlation function.

For grid points, the item code is one of 1,2,3,4,5, and 6, which represent themnemonics T1, T2, T3, R1, R2, and R3, respectively. For scalar points or PRESS,always use 1.

4. Elements defined as a laminate cannot be selected by the RCROSS entry. TheRCROSSC entry should be used to request cross-power spectral density andcross-correlation function output for shell composites defined with the PCOMPand PCOMPG property entries, and solid element composites defined with thePCOMPS property entry.

5. Field CURID is optional. It is for your convenience to identify the output by using asingle index.


Acoustics


RCROSSC

Cross-Power Spectral Density and Cross-Correlation Function Output for Shell andSolid Element Composites

Defines a pair of response quantities for computing the cross-power spectral densityand cross-correlation functions in random analysis for shell and solid elementcomposites.

FORMAT:

1 2 3 4 5 6 7 8 9 10

RCROSSC SID RTYPE1 ID1 COMP1 PLY1

RTYPE2 ID2 COMP2 PLY2 CURID

EXAMPLES:

RCROSSC 20 DISP 50 2

STRESS 150 8 2 4

RCROSSC 200 PRESS 101 1

STRESS 150 8 2 4

FIELDS:

Field Contents

SID RCROSS case control command identification number. (Integer>0)

RTYPEi Response quantity. (Character; For default behavior, see Remark 2)

IDi Element, grid, or scalar point identification number. (Integer > 0; Nodefault)

COMPi Component (item) code identification number. See Remark 3. (Integer> 0; No default)

PLYi Ply number. (Integer ≥ 0; For default behavior, see Remark 4)

CURID Optional curve identification number. See Remark 5. (Integer > 0;No default)

REMARKS:1. The RCROSSC entry is used to request cross-power spectral density and

cross-correlation function output for shell composites defined with the PCOMPand PCOMPG property entries, and solid element composites defined with thePCOMPS property entry.



Acoustics

2. The keywords for field RTYPEi are listed as follows:

Keyword Meaning

DISP Displacement Vector

VELO Velocity Vector

ACCEL Acceleration Vector

OLOAD Applied Load Vector

SPCF Single-point Constraint Force Vector

MPCF Multi-point Constraint Force Vector

STRESS Element Stress

STRAIN Element Strain

FORCE Element Force

PRESS Acoustic Pressure

If either the RTYPE1 or RTYPE2 field is blank, then the blank field defaults to theresponse quantity listed in the defined field.

3. For elements, the component (item) code COMPi represents a component of theelement stress, strain or force as described in the “Element Stress (or Strain) ItemCodes” and “Element Force Item Codes” tables. For an item having both a realand imaginary part, the code of the real part must be selected. This is required forcomputing both the cross-power spectral density function and cross-correlationfunction.

For grid points, the item code is one of 1,2,3,4,5, and 6, which represent T1, T2,T3, R1, R2, and R3, respectively.

For scalar points or PRESS, always use 1.

4. PLY1 and PLY2 cannot both be zero or blank. If it is desired to have both zero,use the RCROSS bulk entry.

For a non-composite element, grid point, or scalar point, specify PLYi = 0 or leavethe PLYi field blank. For a non-composite element, grid point, or scalar point, ifPLYi > 0, the ply number specification is ignored.

For a composite element, if PLYi = 0 or the PLYi field is blank or PLYi is greaterthan the actual number of plies, the ply number specification is ignored.

5. To identify the output with a single index, specify the index in the CURID field.


Acoustics


Support for random acoustic analysisFor distributed acoustic plane wave problems, you can now perform power spectral density (PSD)random acoustics analysis. This capability is supported for both SOL 108 and SOL 111. In earlierversions of the software, you are limited to deterministic acoustic analysis.

To request that the software calculate the random response, in your input file include the RANDOMcase control command. Then, organize the subcases as follows:

1. Create a frequency response subcase for each acoustic loading. Make sure that all of thesesubcases reference the same set of frequencies.

The acoustic loads can include acoustic monopole, dipoles, or plane waves. A typical acousticloading, is that of an acoustic diffuse field. You can represent an acoustic diffuse field with anumber of subcases that each contain an acoustic plane wave source. Orient each plane wavesource differently with respect to the object that sees the acoustic diffuse field. For example, theobject might be a panel or a spacecraft. To define a diffuse acoustic field, you can define thesesources as uncorrelated sources in a RANDOM subcase by specifying the diagonal (auto-PSD)factors in the RANDPS bulk entries only.

2. Below the frequency response subcases, include a random analysis subcase for each PSDfunction that you want to evaluate. Include ANALYSIS = RANDOM in these subcases.

The software uses the frequency response functions that are calculated in the immediatelypreceding frequency response subcases as the inputs to the random calculations.

Example

Suppose that the fluid in a vibro-acoustic problem is excited by three plane wave loadings, andyou want to evaluate the acoustic random response for two PSD functions. You can organize thesubcase structure of the input file as follows:

SUBCASE 1$$ Subcase 1 calculates the frequency response function for the$ loading specified by ALOAD 111 at the frequencies specified by$ FREQUENCY set 13$FREQUENCY=13ALOAD=111$SUBCASE 2$$ Subcase 2 calculates the frequency response function for the$ loading specified by ALOAD 211 at the frequencies specified by$ FREQUENCY set 13$FREQUENCY=13ALOAD=211$SUBCASE 3$$ Subcase 3 calculates the frequency response function for the$ loading specified by ALOAD 311 at the frequencies specified by$ FREQUENCY set 13$



Acoustics

FREQUENCY=13ALOAD=311$SUBCASE 4$$ Subcase 4 uses the frequency responses from Subcases 1-3 to$ calculate the random response of the structure for the PSD function$ specified by RANDOM 100$ANALYSIS=RANDOMRANDOM=100$SUBCASE 5$$ Subcase 5 uses the frequency responses from Subcases 1-3 to$ calculate the random response of the structure for the PSD function$ specified by RANDOM 200$ANALYSIS=RANDOMRANDOM=200

Incident and transmitted acoustic power and acoustic powertransmission loss results outputFor SOL 108 and 111, you can now request results output for incident acoustic power, transmittedacoustic power, and acoustic power transmission loss in deterministic and random acoustic analysis.In NX Nastran 11, you were limited to output of acoustic power results.

Because acoustic power results include both incident and scattered (reflected) components, thenew output requests allow you to examine acoustic results in more detail and compute acoustictransmission loss.

• To isolate the acoustic power that is incident on a surface like a 2D microphone mesh or a setof acoustic free faces (BSURFS) and that is attributable to acoustic sources like monopoles oracoustic plane waves, but not reflections, use the INPOWER case control command.

• To request the acoustic power that is transmitted through an automatically matched layer (AML)region or a 2D microphone mesh that includes both incident and scattered components, use theTRPOWER case control command.

• To request the acoustic power transmission loss, use the TRLOSS case control command. Thesoftware calculates the acoustic power transmission loss from the INPOWER and TRPOWERresults as follows:

Calculating acoustic power transmission loss through a structural panel

As an example, you can use TRLOSS to calculate the acoustic power transmission loss through astructural panel.


Acoustics


In a laboratory setting, you can measure the acoustic power transmission loss through a structuralpanel by mounting the panel in an aperture of a wall between two rooms. One room is reverberantand contains a diffuse acoustic plane wave source. The other room is anechoic and has no pureacoustic sources. The anechoic room also contains the instrumentation for measuring the acousticpower. Because the room is anechoic, you measure the acoustic power that radiates from the panel,and the measurement is not influenced by reflections.

A simulation for such a laboratory setup is shown below:

AMLREG1 (reverberantside)

Structural panel

Acoustic free faces(reverberant side)

AMLREG2 (anechoicside)

Figure 3-1. Panel test

In the simulation, both rooms are represented by fluid meshes using AML regions. AMLREG1represents the reverberant room where the fluid domain opens to the half space in front of the panel.The acoustic power source within the reverberant room can be modeled by a set of random planewaves that are typically outside the fluid mesh. AMLREG2 represents the anechoic room where thefluid domain opens to the half space behind the panel.

1. Use INPOWER to calculate the incident acoustic power on the free acoustic faces on thereverberant room side that couple with the panel.

2. Use TRPOWER to calculate the acoustic power flowing through AMLREG2.

3. Use TRLOSS to calculate the acoustic power transmission loss through the panel.

Random results

If you request random results with the INPOWER, TRPOWER, and TRLOSS case control commands,only real output is supported. Thus, these case control commands do not honor the followingspecifications:

• RANCPLX = 1 on the RANDOM case control command

• PARAM,RANCPLX,1

For more information, see the new INPOWER, TRPOWER, and TRLOSS case control commands,and the updated ACPOWER case control command.



Acoustics

ACPOWER

Acoustic Power Results Output

Acoustic power results output request for AML regions or 2D microphone elements(SORT2 results only).

FORMAT:

EXAMPLES:SET 123=3,6,9

ACPOWER(AMLREG=123)

SET 5=5,10

ACPOWER(GROUP=5,PRINT,PUNCH,PHASE)

ACPOWER=NO

ACPOWER

DESCRIBERS:

Describer Meaning

AMLREG =ALL

Calculate acoustic power results for all AMLREG bulk entries.(Default)

AMLREG =NONE

Do not calculate acoustic power results for any AMLREG bulkentries.

AMLREG = na na (integer>0) is the identification number of the SET casecontrol command that lists the identification numbers of AMLREGbulk entries at which to calculate acoustic power results. SeeRemark 3.

GROUP = ng ng (integer>0) is the identification number of the SET casecontrol command that lists the identification numbers of GROUPbulk entries that contain the 2D microphone elements at which tocalculate acoustic power results. See Remark 3.

PRINT Write the acoustic power results to the print (.f06) file. (Default)

NOPRINT Do not print the acoustic power results.


Acoustics


Describer Meaning

PUNCH Write the acoustic power results to the standard punch (.pch) file.


PHASE Requests polar format (magnitude and phase) of complex output.Phase output is in degrees.

RPRINT Write the random analysis results to the print (.f06) file. SeeRemark 5. (Default)

NORPRINT Do not write the random analysis results to the print file. SeeRemark 5.

RPUNCH Write the random analysis results to the punch (.pch) file. SeeRemark 5.

YES Honor describer settings and calculate and output acoustic powerresults. (Default)

NO Ignore describer settings and do not calculate or output acousticpower results. See Remark 5.

REMARKS:1. The PRESSURE case control command settings determine whether the acoustic

power results are total or scattered.

2. Both PRINT and PUNCH may be requested.

3. Only AML regions or 2D microphone elements referenced in GROUP bulk entriesare processed for acoustic power results. Either or both of the AMLREG andGROUP describers must be specified. Microphone elements must referencea PMIC property.

4. Acoustic power results are written to the op2 file, if PARAM, POST,-1 orPARAM,POST,-2.


• By default, frequency response results are not output. If in addition to randomoutput, frequency response output is desired, specify SYSTEM(524)=1 orRANFRF=1 in the input file. The PRINT, NOPRINT, PUNCH describerscontrol the frequency response output. The RPRINT, NORPRINT, RPUNCHdescribers control the random output.

• Only SORT2 output format is available for the frequency response andrandom results output.



Acoustics

• Only real random analysis results are generated regardless of how theRANCPLX describer on the RANDOM case control command or theRANCPLX parameter are specified.

• Only the power spectral density function (PSDF) is calculated. For RANDPSbulk entries that refer to n subcases, when i = j the results in W/Hz arecomputed as follows:

If i ≠ j, then a warning message is issued and the RANDPS bulk entries areignored.

For more information, see the RANDPS bulk entry.

• Use ACPOWER=NO within a subcase to override a ACPOWER specificationabove the subcase level.


Acoustics


INPOWER

Incident Acoustic Power Results Output

Incident acoustic power results output request for 2D microphone elements or acousticfree faces (SORT2 results only).

FORMAT:

EXAMPLES:SET 5=5,10

INPOWER(GROUP=5,PRINT,PUNCH,PHASE)

SET 6=100

INPOWER(FACES=6)

INPOWER=NO

DESCRIBERS:

Describer Meaning

GROUP = ng ng (integer>0) is the identification number of the SET casecontrol command that lists the identification numbers of GROUPbulk entries that contain the 2D microphone elements at which tocalculate incident acoustic power results. See Remark 2.

FACES = nf nf (integer>0) is the identification number of the SET case controlcommand that lists the identification numbers of BSURFS bulkentries that contain the acoustic free faces at which to calculateincident acoustic power results. See Remark 2.

PRINT Write the incident acoustic power results to the print (.f06) file.(Default)

NOPRINT Do not print the incident acoustic power results.

PUNCH Write the incident acoustic power results to the standard punch(.pch) file.





Acoustics

Describer Meaning




YES Honor describer settings and calculate and output incidentacoustic power results. (Default)

NO Ignore describer settings and do not calculate or output incidentacoustic power results. See Remark5.


2. Only 2D microphone elements referenced in GROUP bulk entries or acousticfree faces at the structural boundary referenced on BSURFS bulk entries areprocessed for incident acoustic power results. Either the GROUP describer or theFACES describer must be specified, but not both. Microphone elements mustreference a PMIC property.

3. Incident acoustic power results are written to the op2 file, if PARAM, POST,-1 orPARAM,POST,-2.







Acoustics




5. Use INPOWER=NO within a subcase to override a INPOWER specification abovethe subcase level.

6. The computed incident power takes into account the incident acoustic energy fromthe ACPOLE1, ACPOLE2, and ACPLNW acoustic sources only, and not fromacoustic sources like ACPNVEL that can contain a scattered component.



Acoustics

TRPOWER

Transmitted Acoustic Power Results Output

Transmitted acoustic power results output request for AML regions or 2D microphoneelements (SORT2 results only).

FORMAT:

EXAMPLES:SET 123=3,6,9

TRPOWER(AMLREG=123)

SET 5=5,10

TRPOWER(GROUP=5,PRINT,PUNCH,PHASE)

TRPOWER=NO

TRPOWER

DESCRIBERS:

Describer Meaning

AMLREG =ALL

Calculate transmitted acoustic power results for all AMLREG bulkentries. (Default)

AMLREG =NONE

Do not calculate transmitted acoustic power results for anyAMLREG bulk entries.

AMLREG = na na (integer>0) is the identification number of the SET case controlcommand that lists the identification numbers of AMLREG bulkentries at which to calculate transmitted acoustic power results.See Remark 2.

GROUP = ng ng (integer>0) is the identification number of the SET casecontrol command that lists the identification numbers of GROUPbulk entries that contain the 2D microphone elements at which tocalculate transmitted acoustic power results. See Remark 2.

PRINT Write the transmitted acoustic power results to the print (.f06)file. (Default)

NOPRINT Do not print the transmitted acoustic power results.


Acoustics


Describer Meaning

PUNCH Write the transmitted acoustic power results to the standardpunch (.pch) file.






YES Honor describer settings and calculate and output transmittedacoustic power results. (Default)

NO Ignore describer settings and do not calculate or outputtransmitted acoustic power results. See Remark 5.


2. Only AML regions and 2D microphone elements referenced in GROUP bulkentries are processed for transmitted acoustic power results. The AMLREGdescriber and the GROUP describer can be specified simultaneously. Microphoneelements must reference a PMIC property. Any other entities that are contained ina GROUP that is referenced by TRPOWER are ignored.

3. Transmitted acoustic power results are written to the op2 file if PARAM, POST,-1or PARAM,POST,-2.






Acoustics





5. Use TRPOWER=NO within a subcase to override a TRPOWER specificationabove the subcase level.


Acoustics


TRLOSS

Acoustic Transmission Loss Results Output

Acoustic transmission loss results output request (SORT2 results only).FORMAT:

EXAMPLES:TRLOSS(PRINT,PUNCH)

TRLOSS=NO

TRLOSS

DESCRIBERS:

Describer Meaning

PRINT Write the transmitted acoustic power results to the print (.f06)file. (Default)

NOPRINT Do not print the transmitted acoustic power results.

PUNCH Write the transmitted acoustic power results to the standardpunch (.pch) file.




YES Honor describer settings and calculate and output transmittedacoustic power results. (Default)

NO Ignore describer settings and do not calculate or outputtransmitted acoustic power results. See Remark 8.


2. TRLOSS results are always real values.

3. To produce transmission loss results for a specific subcase, the subcase mustrequest both incident acoustic power (INPOWER) and transmitted acousticpower (TRPOWER) results. TRLOSS can be requested for frequency responseor random subcases.



Acoustics

4. For frequency response analysis, transmission loss is computed from:

5. For random PSD analysis, the transmission loss is computed from:

6. Transmission loss results are written to the op2 file if PARAM, POST,-1 orPARAM,POST,-2.





8. Use TRLOSS=NO within a subcase to override a TRLOSS specification abovethe subcase level.

9. The computed incident power takes into account the incident acoustic energy fromthe ACPOLE1, ACPOLE2, and ACPLNW acoustic sources only, and not fromacoustic sources like ACPNVEL that can contain a scattered component.

Usability improvement for panel and grid contributionsNow you can only use the PANCON case control command to request panel contributions. To requestgrid contributions, you must use the new GRDCON case control command.

In earlier versions of NX Nastran, you use the PANCON case control command to request both gridand panel contributions. However, because you can only include a single PANCON case controlcommand in an input file, the software is limited to writing both the grid and panel contributionsin the same output format.

With the removal of the grid contributions request from the PANCON case control command, and theaddition of the new GRDCON case control command, you can now direct the software to write gridcontributions to one output format and panel contributions to another.


Acoustics


For example, you can use a PANCON case control command to write panel contributions in theSORT2 output format, and use a GRDCON case control command to write grid contributions inthe SORT1 output format.

When using NX Nastran 12, if you run a legacy input file that contains a PANCON case controlcommand that requests grid contributions, a fatal error occurs. To avoid the fatal error, you canedit the legacy input file as follows:

1. If the PANEL describer is set to NONE, remove the PANCON case control command altogether.If the PANEL describer is unspecified or is not set to NONE, remove any TOPG and GRIDdescriber specifications from the PANCON case control command.

2. Write a GRDCON case control command that contains the TOPG and GRID describerspecifications that you removed from the PANCON case control command.

For more information, see the updated PANCON case control command and the new GRDCONcase control command.



Acoustics

GRDCON

Acoustic Contribution Request for Grids of Structural Panels

Requests acoustic contribution results for the grids of structural panels and for theresidual.

FORMAT:

EXAMPLES:GRDCON=123GRDCON(SORT1,PHASE,PRINT,PUNCH,BOTH,TOPG=5)=ALL

DESCRIBERS:

Describer Meaning

SORT1 Present output as a tabular listing of grids for each frequency.(Default)

SORT2 Present output as a tabular listing of frequency for each grid.

REAL orIMAG

Requests rectangular format (real and imaginary) of complex output.Use of either REAL or IMAG yields the same output. (Default)


PRINT Write acoustic grid contribution results to the print (.f06) file. (Default)

NOPRINT Do not print the acoustic grid contribution results.

PUNCH Write acoustic grid contribution results to the standard punch (.pch)file.

ABS Output acoustic grid contributions in absolute terms. (Default)

NORM Output acoustic grid contributions in normalized terms.

BOTH Output acoustic grid contributions in both absolute and normalizedterms.

TOPG = ALL List all of the structural grids in the output. The output is sortedin descending order from the structural grid having the greatestcontribution. (Default)


Acoustics


Describer Meaning

TOPG = pg

pg (integer>0) is the number of structural grids to list in theoutput that have the greatest contribution to the response ateach frequency. The output is sorted in descending order fromthe structural grid having the greatest contribution. If pg = 0, nostructural grid contributions are output, only totals.

SOLUTION= ALL

Perform the contribution calculations at all frequencies defined bythe FREQUENCY case control commands. (Default)

SOLUTION= setf

setf (integer>0) is the identification number of the SET case controlcommand that contains the frequencies at which to perform thecontribution calculations.

GRID = ALL Output contributions for all structural grids that are part of theacoustic coupling matrix. (Default)

GRID = setg

setg (integer>0) is the identification number of the SET case controlcommand that contains the grids at which to output the contributionresults. Any grid in the set that is not part of the coupling matrixis ignored.

n Calculate grid contributions for the list defined by the SETMC casecontrol command that has set identification number n (integer>0).Any response listed in SETMC = n that is not an acoustic responseis ignored.

ALL Calculate grid contributions for all the SETMC case controlcommands specified in and above the current subcase. Anyresponse listed in the SETMC case control commands that is notan acoustic response is ignored. (Default)

NONE Do not calculate grid contributions. This is useful to turn offcontribution output for a specific subcase.


2. GRDCON = NONE overrides an overall output request.

3. SOL 108 and 111 are supported.

4. The parameters LFREQ, LFREQFL, HFREQ, HFREQFL, LMODES, andLMODESFL are supported.

5. The SOLUTION keyword can be abbreviated to SOLU.

6. The SET case control command referenced by SOLUTION = setf must containreal values for frequencies. Using integer values may lead to unintended results.

7. GRDCON supports results for microphone points.



Acoustics

PANCON

Acoustic Contribution Request for Structural Panels

Requests acoustic contribution results for structural panels and for the residual.FORMAT:

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

DESCRIBERS:

Describer Meaning

SORT1 Present output as a tabular listing of panels for each frequency.

SORT2 Present output as a tabular listing of frequency for each panel.(Default)

REAL orIMAG

Requests rectangular format (real and imaginary) of complex output.Use of either REAL or IMAG yields the same output. (Default)


PRINT Write acoustic panel contribution results to the print (.f06) file.(Default)

NOPRINT Do not print the acoustic panel contribution results.

PUNCH Write acoustic panel contribution results to the standard punch(.pch) file.

ABS Output acoustic panel contributions in absolute terms. (Default)

NORM Output acoustic panel contributions in normalized terms.

BOTH Output acoustic panel contributions in both absolute and normalizedterms.

TOPP = ALL List all of the structural panels in the output. The output is sortedin descending order from the structural panel having the greatestcontribution.


Acoustics


Describer Meaning

TOPP = pp pp (integer>0) is the number of structural panels to list in theoutput that have the greatest contribution to the response at eachfrequency. The output is sorted in descending order from thestructural panel having the greatest contribution. If pp = 0, nostructural panel contributions are output, only totals. (Default=5)

SOLUTION= ALL

Perform the contribution calculations at all frequencies defined bythe FREQUENCY case control commands. (Default)

SOLUTION= setf

setf (integer>0) is the identification number of the SET case controlcommand that contains the frequencies at which to perform thecontribution calculations.

PANEL =ALL

Output contributions for all panels defined by PANEL bulk entries.(Default)

PANEL =setp

setp (integer>0) is the identification number of the SET casecontrol command that contains the panels at which to output thecontribution results.

n Calculate panel contributions for the list defined by the SETMC casecontrol command that has set identification number n (integer>0).Any response listed in SETMC = n that is not an acoustic responseis ignored.

ALL Calculate panel contributions for all the SETMC case controlcommands specified in and above the current subcase. Anyresponse listed in the SETMC case control commands that is notan acoustic response is ignored. (Default)

NONE Do not calculate panel contributions. This is useful to turn offcontribution output for a specific subcase.


2. PANCON = NONE overrides an overall output request.

3. SOL 108 and 111 are supported.

4. PANCON supports results for microphone points.

5. The parameters LFREQ, LFREQFL, HFREQ, HFREQFL, LMODES, andLMODESFL are supported.

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

7. The SET case control command referenced by SOLUTION = setf must containreal values for frequencies. Using integer values may lead to unintended results.



Acoustics

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

Acoustic transfer vectorsYou can now use acoustic transfer vectors (ATV) to solve external acoustics problems. An ATV is afrequency-dependent acoustical representation of fluid volume that you can use in SOL 108 and 111acoustic analysis. ATVs relate the response at microphone points and 2D microphone elements toexcitation at the fluid-structure (coupling) interface. The primary benefit of ATVs is computationalefficiency.

ATVs are similar to output transformation matrices (OTMs). They both use a matrix to relate theresponse at specific spatial locations or over specific regions to the excitation at specific locations orfrom specific regions. (For more information on OTMs, see Output transformation matrices.)

For example, suppose you want to examine how the acoustic response at specific locations tostructural excitation varies with respect to structural materials, loads, and so on. Rather than solvingthe entire acoustics problem repeatedly, you can solve the acoustics problem once to create an ATV,and then use the ATV repeatedly to examine how the response varies.

To use the ATV capability, two NX Nastran runs are required.

• The first run is the ATV computation run. During this run, the software creates and writes thematrix representation of the ATV to an OP2 file. The ATV computation run must be SOL 108.

• The second run is the ATV response run. During this run, the software retrieves and uses thematrix representation of the ATV to calculate the acoustic response at microphone points andelements to the excitation of the structural portion of the model. The ATV response run can beeither SOL 108 or 111 and can use one ATV only.

The ATV capability is supported by a new case control command and two new bulk entries.

In the ATV computation run:

• Use the ATVOUT case control command to trigger the creation of the ATV, reference the ATVFSbulk entry that specifies the coupling interface, and reference the SET case control commandthat specifies the microphone elements that comprise 2D microphone meshes.

• Use the new ATVFS bulk entry to specify the BSURFS bulk entries that define the couplinginterface.

• Use a FREQi bulk entry to specify the frequencies at which the software calculates the matrixrepresentation of the ATV.

Note

During the ATV response run, the software interpolates ATV data over the frequencyrange defined by the FREQi bulk entry. Because the software does not extrapolateATV data, a fatal error occurs if the frequency is out of the range defined by theFREQi bulk entry.

In the ATV response run:


Acoustics


• Use the new ATVBULK bulk entry to select the OP2 file that contains the matrix representation ofthe ATV and to offset the element, grid point, and property IDs in the ATV to ensure that theyare unique from those in the structural portion of the model.

• Use an ACMODL bulk entry to specify the coupling interface parameters.

• Use the PRESSURE case control command to request acoustic pressure results at microphonepoints.

• Use the PANCON case control command to request the acoustic pressure at microphone pointsthat are attributable to the vibration of selected structural panels.

o Use PANEL bulk entries to define the structural panels.

o Use SETMC case control commands to specify the microphone points.

For microphone points, specify RTYPE = PRES.

• Use the GRDCON case control command to request the response at microphone points tovibration at structural grids.

• Use the MODCON case control command to request the contribution of modes to the acousticpressure at microphone points. This is valid for a SOL 111 ATV response run only.

o Use SETMC case control commands to specify the microphone points.

For microphone points, specify RTYPE = PRES.

For more information, see the new ATVOUT case control command and the new ATVBULK andATVFS bulk entries.



Acoustics

ATVOUT

ATV Creation Specification

Specifies requirements for the creation of an acoustic transfer vector (ATV).

FORMAT:

EXAMPLES:ATVOUT(ATVOP2=33,ATVFS=110)=200

DESCRIBERS:

Describer Meaning

ATVOP2 = unit unit (integer>0) is the Fortran unit number for the .op2 file towhich the ATV results are written. See Remark 2.

ATVFS = sid sid (integer>0) is the identification number of the ATVFS bulkentry that defines the set of fluid element faces that define thecoupling interface.

ALL Output ATV results for all microphone elements. See Remark6. (Default)

n n (integer>0) is the identification number of a previouslyappearing SET case control command that contains microphoneelement identification numbers at which to output the ATV results.See Remark 6.

REMARKS:1. ATVOUT is valid for SOL 108 only. If ATVOUT is included in the input file for any

other solution, the software issues a user fatal message.

2. For specifying ATVOP2 = unit, an appropriate ASSIGN OUTPUT2 statement mustbe present in the File Management Section of the input file.

3. An OUTPUT2 file created from a LP-64 executable ATV creation run cannot beused in an ILP-64 Nastran executable system run and vice versa. Note thatbeginning in NX Nastran 12, only the ILP-64 executable is available.

4. ATVOUT can only be specified above subcases. If ATVOUT is included in asubcase, it is ignored.

5. Only one ATVOUT can be included in an input file.

6. ATV output is controlled by the specification of ALL or n only. Any otheroutput-related case control commands like DISPLACEMENT or PRESSURE areignored.


Acoustics


ATVBULK

Selects ATV results for an ATV system run

Specifies the Fortran unit number for the OUTPUT2 file that contains the ATV results,and the element, grid point, and element property offsets to be used in an ATV systemrun.

FORMAT:

1 2 3 4 5 6 7 8 9 10

ATVBULK UNITNO EOFFSET GOFFSET POFFSET

EXAMPLE:

ATVBULK 33 1000 2000 20

FIELDS:

Field Contents

UNITNO Fortran unit number for the OUTPUT2 file that contains the ATVresults. See Remarks 1 and 2. (Integer > 0; No default)

EOFFSET Element ID offset. See Remark 3. (Integer > 0; Default = 0)

GOFFSET Grid point ID offset. See Remark 3. (Integer > 0; Default = 0)

POFFSET Element property ID offset. See Remark 3. (Integer > 0; Default = 0)

REMARKS:1. For specifying UNITNO, an appropriate ASSIGN OUTPUT2 statement must be

present in the File Management Section of the input file.

2. An OUTPUT2 file that is created during a LP-64 Nastran executable ATV creationrun cannot be used in an ILP-64 Nastran executable system run and vice versa.Note that beginning in NX Nastran 12, only the ILP-64 executable is available.

3. The element, grid, and element property IDs associated with the ATV resultsmust be unique from element, grid, and element property IDs in the system run.To assure that they are unique, specify appropriate element, grid, and elementproperty ID offsets.



Acoustics

ATVFS

Coupling interface definition for an ATV

Defines the interface that couples the acoustic transfer vector (ATV) to the structurein the ATV system run.

FORMAT:

1 2 3 4 5 6 7 8 9 10

ATVFS SID ID1 ID2 ID3 ID4 ID5 ID6

ID7 ID8 -etc-

EXAMPLE:

ATVFS 100 201 202

FIELDS:

Field Contents

SID Set identification number of the fluid element faces that define thecoupling interface. See Remark 1. (Integer > 0; No default)

IDi Identification number of BSURFS bulk entries that list the fluid elementfaces that define the coupling interface. (Integer>0; No default)

REMARKS:1. SID is referenced by the ATVFS describer specification on the ATVOUT case

control command.

Output format for acoustic intensity and acoustic velocity resultsYou can now request that acoustic intensity and acoustic velocity results be output in the SORT2format. The SORT2 format allows you to more easily examine how acoustic intensity and acousticvelocity at a particular DOF vary with respect to frequency.

In earlier versions of the software, only the SORT1 format is available for these results.

For more information, see the ACINTENSITY and ACVELOCITY case control commands.


Acoustics


ACINTENSITY

Acoustic Intensity Output

Acoustic intensity output request at microphone points.FORMAT:

EXAMPLES:SET 123=5,10,15,25

ACINTENSITY=123

SET 5=6,8,11

ACINTENSITY(PRINT,PUNCH,PHASE)=5

DESCRIBERS:

Describer Meaning



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

NOPRINT Generates, but does not print intensity results.

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



n ID of SET case control command containing the list ofidentification numbers of fluid grids referenced by microphoneelements at which to calculate acoustic intensity results. (Integer> 0)

ALL Requests acoustic intensity results for all microphone elementsin the model.



Acoustics

Describer Meaning

NONE Turns this output request off; useful for controlling output requestsacross subcases.


intensity results are based on total or scattered pressure.

2. Acoustic intensity results will be written to the op2 file, if the value of PARAM,POST is -1 or -2.

3. When the fluid domain is represented by an acoustic transfer vector (ATV),acoustic particle velocity and acoustic intensity results cannot be computed, andthe ACINTENSITY and ACVELOCITY case control commands are ignored.


Acoustics


ACVELOCITY

Acoustic Velocity Output

Acoustic velocity output request at microphone points.FORMAT:

EXAMPLES:SET 123=5,10,15,25

ACVELOCITY=123

SET 5=6,8,11

ACVELOCITY(PRINT,PUNCH,PHASE)=5

DESCRIBERS:

Describer Meaning



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

NOPRINT Generates, but does not print, acoustic velocity.

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



n ID of SET case control command containing the list ofidentification numbers of fluid grids referenced by microphoneelements at which to calculate acoustic velocity results. (Integer> 0)

ALL Request acoustic velocity results for all microphone elementsin the model.

NONE Turns this output request off; useful for controlling output requestsacross subcases.



Acoustics


velocity results are based on total or scattered pressure.

2. Acoustic velocity results will be written to the op2 file, if the value of PARAM,POST is -1 or -2.

3. When the fluid domain is represented by an acoustic transfer vector (ATV),acoustic particle velocity and acoustic intensity results cannot be computed, andthe ACINTENSITY and ACVELOCITY case control commands are ignored.


Acoustics

Chapter 4: Superelements

Frequency-dependent external superelements for frequencyresponse analysisDuring a SOL 108 or 111 frequency response analysis superelement creation run, you can now createfrequency-dependent external superelements. You can then use the frequency-dependent externalsuperelement in a SOL 108 or 111 system run.

In earlier versions of NX Nastran, you cannot create frequency-dependent external superelements.

The primary advantages of frequency-dependent external superelements are as follows:

• Unlike conventional superelements that include boundary DOF and component modes,frequency-dependent superelements contain only boundary DOF, which improves computationalefficiency.

• Unlike conventional superelements, frequency-dependent superelements supportfrequency-dependent material properties.

The primary disadvantage of frequency-dependent external superelements are as follows:

• Because the superelement creation run is performed repeatedly at multiple frequencies, morecomputational effort is required up front.

• Because each superelement creation run generates the dynamic stiffness matrix for the boundaryDOF and a data recovery matrix for displacement data recovery, more disk storage is required.

During the SOL 108 or 111 system run, the software adds the dynamic stiffness for the boundary DOFto the dynamic stiffness of the residual structure and uses the data recovery matrices to calculatedisplacement, velocity, and acceleration output.

The workflow to use frequency-dependent superelements is essentially identical to the workflowto create and use conventional external superelements. First you perform a SOL 108 or 111superelement creation run. In the input file for the superelement creation run, use the FRFOUT casecontrol command in place of the EXTSEOUT case control command. The FRFOUT case controlcommand triggers the software to:

1. Create the frequency-dependent dynamic stiffness matrices for the boundary DOF and the datarecovery matrices for displacement data recovery.

2. Write the frequency-dependent dynamic stiffness matrices for the boundary DOF and datarecovery matrices to the OP2 file.

To define the frequencies at which the software calculates the dynamic stiffness matrices for theboundary DOF and the data recovery matrices, use a FREQ bulk entry.



During the SOL 108 or 111 system run, the software uses the FRFOUT files that are generated by thesuperelement creation run. To trigger the software to read the FRFOUT files from the superelementcreation run, use the SEBULK bulk entry with the TYPE field set to FRFOP2.

For more information, see the new FRFOUT case control command and the updated SEBULKbulk entry.

Component reduction methods

The software supports the following methods for reducing a component to a frequency-dependentexternal superelement during a superelement creation run:

• For SOL 108 direct frequency response analysis:

o Schur complement reduction

This is the default method when you specify SOL 108.

o Schur complement reduction with component modes

The software uses this method when you include a METHOD case control command and aQSETi bulk entry in the input file for the superelement creation run.

• For SOL 111 modal frequency response analysis, modal reduction.

For more information on these reduction methods, see Frequency-Dependent ExternalSuperelements in the Superelement User's Guide.

Example

Perform a SOL 108 frequency response analysis on the structure depicted in Figure 1. Assume thatthe beam is steel and has a 20.0 mm diameter cross section. Model the left half of the beam as afrequency-dependent external superelement. Use Schur complement reduction without componentmodes.

Use the following values for the undefined quantities in Figure 1:

L = 200.0 mm

M = 200.0 kg

f1(t) = 50.0eiωt N

f2(t) = -50.0eiωt N



Superelements

Figure 4-1. Beam with concentrated masses that is subject to harmonic excitation

The following input file is for the superelement creation run. The left half of the beam is modeled withten CBEAM elements. The ASET1 bulk entry specifies the boundary DOF.

ASSIGN output2='frf.out',unit=89$SOL 108DIAG 8, 15, 56$CEND$DISP(phase)=allFREQ=100SPC=100$FRFOUT(asmbulk,extbulk,geom,

extid=10, dmigop2=89,solve,asmbulk)

$BEGIN BULK$$ Units: N, mm, sec, C$FREQ1, 100, 10.0, 10.0, 9$SPC1, 100, 123456, 1$GRID, 1, 0, -100.0, 0.0, 0.0GRID, 2, 0, -90.0, 0.0, 0.0GRID, 3, 0, -80.0, 0.0, 0.0GRID, 4, 0, -70.0, 0.0, 0.0GRID, 5, 0, -60.0, 0.0, 0.0GRID, 6, 0, -50.0, 0.0, 0.0GRID, 7, 0, -40.0, 0.0, 0.0GRID, 8, 0, -30.0, 0.0, 0.0GRID, 9, 0, -20.0, 0.0, 0.0GRID, 10, 0, -10.0, 0.0, 0.0


Superelements


GRID, 11, 0, 0.0, 0.0, 0.0$CBEAM, 101, 100, 1, 2, 0.0, 1.0, 0.0CBEAM, 102, 100, 2, 3, 0.0, 1.0, 0.0CBEAM, 103, 100, 3, 4, 0.0, 1.0, 0.0CBEAM, 104, 100, 4, 5, 0.0, 1.0, 0.0CBEAM, 105, 100, 5, 6, 0.0, 1.0, 0.0CBEAM, 106, 100, 6, 7, 0.0, 1.0, 0.0CBEAM, 107, 100, 7, 8, 0.0, 1.0, 0.0CBEAM, 108, 100, 8, 9, 0.0, 1.0, 0.0CBEAM, 109, 100, 9, 10, 0.0, 1.0, 0.0CBEAM, 110, 100, 10, 11, 0.0, 1.0, 0.0$PBEAML, 100, 100, , rod,, 10.0$MAT1, 100, 2.040+5, , 0.29, 7.86-12, 12.0-6, 0.0, 0.02$CONM2, 1001, 6, 0, 0.2$ASET1, 123456, 11$ENDDATA

The following input file is for the system run. The right half of the beam is modeled with ten CBEAMelements. The harmonic excitation forces are modeled with RLOAD2, DAREA, and TABLED1 bulkentries.

ASSIGN inputt2='frf.out', unit=100$SOL 108DIAG 8, 15, 56$CEND$DISP(phase)=allFREQ=100SPC=100DLOAD=100$BEGIN BULK$$ Units: N, mm, sec, C$FREQ1, 100, 10.0, 10.0, 9$SPC1, 100, 123456, 11$GRID, 1, 0, 0.0, 0.0, 0.0GRID, 2, 0, 10.0, 0.0, 0.0GRID, 3, 0, 20.0, 0.0, 0.0GRID, 4, 0, 30.0, 0.0, 0.0GRID, 5, 0, 40.0, 0.0, 0.0GRID, 6, 0, 50.0, 0.0, 0.0GRID, 7, 0, 60.0, 0.0, 0.0



Superelements

GRID, 8, 0, 70.0, 0.0, 0.0GRID, 9, 0, 80.0, 0.0, 0.0GRID, 10, 0, 90.0, 0.0, 0.0GRID, 11, 0, 100.0, 0.0, 0.0$CBEAM, 101, 100, 1, 2, 0.0, 1.0, 0.0CBEAM, 102, 100, 2, 3, 0.0, 1.0, 0.0CBEAM, 103, 100, 3, 4, 0.0, 1.0, 0.0CBEAM, 104, 100, 4, 5, 0.0, 1.0, 0.0CBEAM, 105, 100, 5, 6, 0.0, 1.0, 0.0CBEAM, 106, 100, 6, 7, 0.0, 1.0, 0.0CBEAM, 107, 100, 7, 8, 0.0, 1.0, 0.0CBEAM, 108, 100, 8, 9, 0.0, 1.0, 0.0CBEAM, 109, 100, 9, 10, 0.0, 1.0, 0.0CBEAM, 110, 100, 10, 11, 0.0, 1.0, 0.0$PBEAML, 100, 100, , rod,, 10.0$MAT1, 100, 2.040+5, , 0.29, 7.86-12, 12.0-6, 0.0, 0.02$CONM2, 1001, 6, 0, 0.2$RLOAD2, 100, 101, 0.0, 0.0, 1001, 0.0, 0DAREA, 101, 1, 2, 50.0DAREA, 101, 6, 2, -50.0$TABLED1, 1001,, 0.0, 1.0, 1000.0, 1.0, endt$SEBULK, 10, frfop2, , , , , 100$BEGIN SUPER 10$INCLUDE './beam_model.pch'$ENDDATA


Superelements


FRFOUT

Frequency-Dependent External Superelement Creation Specification

Creates a frequency-dependent external superelement using Schur complementreduction.

FORMAT:

EXAMPLES:FRFOUTFRFOUT(ASMBULK,EXTID=100)FRFOUT(ASMBULK,EXTID=100,GEOM)FRFOUT(ASMBULK,EXTID=100,DMIGOP2=99)

DESCRIBERS:

Describer Meaning

ASMBULK Generate bulk entries related to the subsequent superelementassembly process and store them on the assembly punch file(.asm). This data is to be included in the main bulk portion of thesubsequent assembly solution. See Remarks 3 and 5.

EXTBULK Generate and store bulk entries for the external superelementon the standard punch file (.pch). This data is used in theBEGIN SUPER portion of the bulk section of the subsequentassembly solution. If EXTBULK is not specified, the subsequentassembly solution retrieves the required data for the externalsuperelement from the OP2 file. See Remarks 4 and 5.

GEOM Store full model geometry. See Remark 10.

SOLVE Compute the response to the input load with the reduced FRFmatrices and loads. Data recovery to the analysis DOFs usesthe same back transformations that are used for the outputtransformation matrix (OTM) generation. Data recovery isperformed the same way in a modal solution as in a directsolution.

EXTID = seid seid (integer > 0) is the frequency-dependent superelement IDto be used in the SEBULK and SECONCT bulk entries stored onthe assembly punch file (.asm) if ASMBULK is specified. SeeRemarks 2, 3, and 4.

DMIGOP2 =unit

Store the boundary matrices as DMIG bulk entries on anOUTPUT2 file whose Fortran unit number is given by unit(integer>0). See Remarks 6 and 7.



Superelements

REMARKS:1. The default is to output the frequency-dependent impedance and loads. Use the

NOLOAD option to disable the load output.

2. EXTID and an seid value must be specified if one or more of ASMBULK orEXTBULK are specified.

3. If ASMBULK is specified, the following bulk entries are generated and stored onthe assembly punch file (.asm):

SEBULK seid …

SECONCT seid …

GRID entries for the boundary points

CORD2x entries associated with the above GRID entries

4. If EXTBULK is specified, the following bulk entries are generated and stored onthe standard punch file (.pch):

BEGIN SUPER seid …

GRID entries for the boundary points

CORD2x entries associated with the above GRID entries

EXTRN

ASET/ASET1

5. The punch output resulting from FRFOUT usage is determined by ASMBULK andEXTBULK as follows:

• No ASMBULK or EXTBULK results in no punch output.

• ASMBULK, but no EXTBULK, results in punch output being generated andstored on the assembly punch file (.asm). See Remark 3.

• ASMBULK and EXTBULK results in punch output consisting of two distinctand separate parts. One part is generated and stored on the assembly punchfile (.asm) as indicated in Remark 3. The other part is generated and storedon the standard punch file (.pch) as indicated in Remark 4.

6. If DMIGOP2 = unit is specified, an appropriate ASSIGN OUTPUT2 statement mustbe present in the File Management Section (FMS) for the absolute value of unit. AnOUTPUT2 file created during a LP-64 Nastran executable superelement creationrun cannot be used in a ILP-64 Nastran executable system run and vice versa.Note that beginning in NX Nastran 12, only the ILP-64 executable is available.

7. The default unit number for the DMIGOP2 describer is 30. To change the defaultunit number, use the EXTUNIT parameter.


Superelements


8. The creation of a frequency-dependent external superelement using FRFOUTinvolves running a NX Nastran job with the following additional data:

• The data for the creation of the frequency-dependent external superelement isspecified by the FRFOUT case control command, which must appear abovethe subcase level.

• The boundary points of the frequency-dependent external superelementare specified by ASET/ASET1, CSET/CSET1, BNDFIX/BNDFIX1, andBNDFREE/BNDFREE1 bulk entries.

• If the creation involves component mode reduction, the optional generalizedcoordinates are specified using QSET/QSET1 bulk entries. The boundarydata for the component mode reduction may be specified using theBNDFIX/BNDFIX1 and BNDFREE/BNDFREE1 bulk entries (or their equivalentBSET/BSET1 and CSET/CSET1 bulk entries). (The default scenario assumesthat all boundary points are fixed for the component mode reduction.)

9. To include differential stiffness in the definition of a frequency-dependent externalsuperelement, two subcases are required in the creation run. The first subcaseis a static subcase. The second subcase performs the analysis and generationof the frequency-dependent external superelement. To obtain the displacementfield used to generate the differential stiffness effects, include a STATSUB casecontrol command in the second subcase that references the first subcase. Alwaysinclude the EXTSEOUT case control command above the subcase level. Anexample of the required setup is as follows:

…SOL 111CENDTITLE = …EXTSEOUT(…)$SUBCASE 1

$ STATIC SUBCASE$SUBCASE 2

$ DYNAMIC SUBCASETSTEP = 100STATSUB = 1METHOD = 10DLOAD = 20

BEGIN BULK…

For accuracy and consistency, the loads used to generate differential stiffness forthe frequency-dependent external superelement during the creation run should bethe same loads used in the system run without any scaling. If the loads are scaledby a non-unity scaling factor from a case control command like P2G or a bulk entrylike LOAD, the differential stiffness portion of the frequency-dependent externalsuperelement impedance will no longer be consistent with the applied loads.



Superelements

10. The GEOM describer outputs geometry data blocks GEOM1EXA, GEOM2EXA,and GEOM4EXA that contain all of the frequency-dependent externalsuperelement geometry to support post-processing. By default, the full geometryis not exported; the GEOM describer must be explicitly defined to have thesegeometry data blocks written.

11. The OFREQ command should not be specified and is ignored for thefrequency-dependent external superelement creation.


Superelements


SEBULK

Partitional Superelement Connection

Defines superelement boundary search options and a repeated, mirrored, or collectorsuperelement.

FORMAT:

1 2 3 4 5 6 7 8 9 10SEBULK SEID TYPE RSEID METHOD TOL LOC UNITNO

EXAMPLES:

SEBULK 14 REPEAT 4 AUTO 1.0E-3

SEBULK 101 FRFOP2 AUTO 1.0E-3 99

FIELDS:

Field Contents

SEID Partitioned superelement identification number. (Integer > 0)

TYPE Superelement type. (Character; No Default)

PRIMARY Primary

REPEAT Identical. See Remark 1.

MIRROR Mirror. See Remarks 1 and 6.

COLLCTR Collector. See Remark 7.

EXTERNAL External. See Remark 8.

EXTOP2 External using an OP2 file created in an earlier run.See Remark 8.

EXTOP4 External using an OP4 file created in an earlierrun.See Remark 8.

FRFOP2 External using an OP2 file created in an earlier run.See Remarks 10 and 11.

RSEID Identification number of the reference superelement, used ifTYPE=“REPEAT” and “MIRROR”. (Integer≥0; Default=0)

METHOD Method to be used when searching for boundary grid points.(Character: “AUTO” or “MANUAL”; Default=“AUTO”)

TOL Location tolerance to be used when searching for boundary gridpoints. (Real; Default=10E-5)



Superelements

Field Contents

LOC Coincident location check option for manual connection option.(Character: “YES” or “NO”; Default=“YES”)

UNITNO Fortran unit number for the OUTPUT2 or OP4 file (applicable andmeaningful only when TYPE = ”EXTOP2”, “EXTOP4”, or "FRFOP2").

REMARKS:1. The TYPE=“REPEAT” or “MIRROR” does not include superelements upstream

of the reference superelement. A repeated or mirrored superelement can haveboundaries, loads, constraints, and reduction procedures that are different thanthe reference superelement.

2. METHOD=“MANUAL” requires SECONCT entries. SEBNDRY and SEEXCLD,which reference SEID, will produce a fatal message.

3. SECONCT, SEBNDRY, and SEEXCLD entries can be used to augment the searchprocedure and/or override the global tolerance.

4. For combined automatic and manual boundary search, the METHOD=“AUTO”should be specified and connections should be specified on a SECONCT entry.

5. TOL and LOC are the default values that can be modified between twosuperelements by providing the required tolerance on the SECONCT entry.

6. TYPE=“MIRROR” also requires specification of a SEMPLN entry.

7. TYPE=“COLLCTR” indicates a collector superelement, which does not containany grids or scalar points.

8. For TYPE = “EXTERNAL”, “EXTOP2”, or “EXTOP4”, see discussion underthe description of the EXTSEOUT case control command for employingexternal superelements using the two-step procedure. For employing externalsuperelements using the three-step procedure, see discussion under thedescription of the EXTOUT parameter.

9. This entry will only work if PART superelements (BEGIN SUPER) or externalsuperelements created by employing the EXTSEOUT case control entry exist.

10. Specify TYPE = "FRFOP2" for frequency-dependent boundary matrices that arevalid for SOL 108 and 111 only.

11. For TYPE = "FRFOP2", the boundary DOF must connect to the residual structure(SEID=0).


Superelements


PVT0 data block in superelement OP2 filesTo allow for differences in units between an external superelement and the residual, the PVT0 datablock is now written to external superelement OP2 files. The PVT0 data block contains the units datathat is specified on the DTI,UNITS bulk entry for the external superelement.



Chapter 5: Multi-step nonlinear solution 401

Shell element supportSolution 401 now supports shell elements defined with the CTRIAR, CQUADR, CTRIA6, andCQUAD8 entries. CQUAD4 and CTRIA3 elements are also supported as inputs, and the software willtreat them as CQUADR and CTRIAR elements.

The shell elements are supported in the subcase types STATIC, PRELOAD, and MODAL. They arenot supported in the BUCKLING, CYCLIC and FOURIER subcase types.

The existing PSHELL is supported. In addition, the new PCOMPG1 property entry is available todefine a composite property which allows for a different failure theory for each layer.

The shell element using the PSHELL bulk entry supports geometry nonlinear conditions (largedisplacement, large rotation, and contact) and material nonlinear (plasticity and creep). When youuse a nonlinear plastic or creep material, the NLAYERS parameter is supported to define the numberof integration points through the thickness. The NLAYERS parameter supports 3, 5, 7, and 9 pointsthrough the thickness.

A composite shell element using the PCOMPG1 property bulk entry supports the geometry nonlinearconditions, but does not support material nonlinear.

The ZOFF field on the element entry is supported to offset the element reference plane.

PSHELL property

• The MID1, MID2, and MID3 are all required. MID1 and MID2 must be explicitly defined, and theMID3 field defaults to the MID2 value.

• MID4 is optional. If MID4 is defined, MID1 and MID2 must be defined. MID4 is applied withrespect to the element plane regardless if ZOFF is defined or not. A ZOFF definition on theelement entry produces a coupling independent of the MID4. As a result, defining both MID4 andZOFF together will create two independent sources of coupling. If you define both MID4 andZOFF, the MID4 should represent an additional coupling which is unique to the ZOFF coupling.

• When plastic or creep nonlinear materials are defined, the MID1, MID2, and MID3 must allbe the same, and MID4 must be undefined.

• The Z1 and Z2 fields on the PSHELL, which define fiber distances for stress calculations in othersolution types, are not supported by SOL 401.

PCOMPG1 property

• The new PCOMPG1 property entry is available to define a composite property which allows for adifferent failure theory for each layer.

• The existing MATFT defines the failure theory allowables for both shell and solid composites.MATFT is required to define allowables with the MAT9 and MAT11 material entries. If you areusing the MAT1 material entry, you can optionally define the allowables with the MATFT, or you can



specify them on the MAT1 entry directly. For shell composites, only FT = HILL/HOFF/TSAI/STRNare supported (NO FT = STRS/TS), and the transverse material properties are ignored for shells:

FT = HILL/HOFF: Zt, Zc, S13, S23 are ignored.

FT = TSAI: Zt, Zc, S13, S23, F13, F23 are ignored.

FT = STRN: Zet, Zec, Se13, Se23 are ignored.

• When a composite property is used, the software does not create a smeared, homogeneous shellrepresentation using classical lamination theory. Instead, an integration scheme similar to what isused for solid composites is used.

• Failure index and strength ratio output are supported for all failure indices.

Material support

• The MAT1 and MATT1 bulk entries define isotropic materials for any shell and composite property.

• The MAT2 and MATT2 bulk entries define anisotropic materials for any shell and compositeproperty.

• The MAT8 and MATT8 bulk entries define orthotropic materials for any shell and compositeproperty.

• The MAT9 and MATT9 bulk entries define anisotropic materials for any shell and compositeproperty.

• The MAT11 and MATT11 bulk entries define orthotropic materials for any shell and compositeproperty.

• The nonlinear plastic and creep material are only supported for the PSHELL.

• User defined materials defined with the UMAT external program are only supported for thePSHELL property.

Material coordinate system

The material coordinate system is used to define the orientation of material properties whenorthotropic or anisotropic materials are selected. In addition, stress and strain results are alwaysoutput in the material coordinate system. The material coordinates are updated when large rotationoccurs.

The X-axis of the material coordinate system for the shell element is determined as follows:

• Option 1: If a material coordinate system is not explicitly selected on the element entry, the X-axisof the material coordinate system is, by default, aligned with the element edge defined by gridpoints G1 and G2. The X-axis can optionally be rotated by defining THETA on the element entry.

• Option 2: A material coordinate system can be selected with the MCID field on the element entry.The X-axis of the selected material coordinate system is projected onto the plane of the shellto define the shell material X-axis.



Multi-step nonlinear solution 401

In addition, if a composite property is used for the element with the PCOMPG1 entry, a uniqueTHETA value can be defined for each ply. The THETA on the ply rotates the material x-axis for eachply relative to the element material x-axis as described above.

The material Z-axis is the positive out-of-plane shell normal defined by the right-hand-rule and thegrid point connection order. The material Y-axis is determined by the cross product of the materialX-axis and Z-axis.

Supported Loads

• Pressure loads are supported with the PLOAD, PLOAD2, or PLOAD4 bulk entries.

• General loads are supported with the FORCE, FORCE1, FORCE2, MOMENT, MOMENT1,MOMENT2, DAREA, and SLOAD.

• Body loads are supported with the ACCELi, GRAV, RFORCE, and RFORCE1. The RFORCE2 isnot supported.

• Temperature loads with variation through the element thickness are not supported using theTEMPP1 bulk entry.

Shell element output summary

• Engineering stress and strain are always output.

• Stress and strain results are always output in the material coordinate system. The materialcoordinates are updated when large rotation occurs and large displacements effects arerequested with PARAM,LGDISP,1.

• Shell elements using a PSHELL support stress/strain results at grid or Gauss points. Stress andstrain is computed at the top and bottom of the element. The STRCUR describer, which requestsoutput at the middle plane, is not supported.

• Composite shell elements using the PCOMPG1 entry only supports stress/strain results at gridpoints.

• The CENTER, CUBIC, or SGAGE options on the STRESS and STRAIN case control commandsare not supported.

• The OMID parameter which is used in other solutions to output stress and strain in the elementcoordinate system is not supported.

• The Z1 and Z2 fields on the PSHELL, which define fiber distances for stress calculations for othersolution types, is not supported by SOL 401.

• For composite shell elements, FI and SR is supported for all failure indices.

• New item codes have been created for the SOL 401 shell element output.

• The FORCE case control command can be used to request shell element resultants in materialcoordinates.

• Grid point forces are supported.




• Shell elements support surface-to-surface contact and surface-to-surface glue. Edge-to-edgeand surface-to-edge glue is not supported for shells in SOL 401. Both glue and contact resultsare support for the shell elements.

Additional information

• The SNORM parameter and bulk entry are only supported by the CTRIAR and CQUADRelements.

• The K6ROT parameter and bulk entry are only supported by the CTRIA6 and CQUAD8 elements.

Bar and beam element supportSolution 401 now supports bar and beam elements defined with the CBAR and CBEAM entries. Thebar and beam elements support large displacements and rotations when large displacements arerequested with PARAM,LGDISP,1.

Physical properties

• The existing PBAR and PBARL entries define the physical properties for the BAR element.

• The existing PBEAM and PBEAML entries define the physical properties for the BEAM element.

• The intermediate stations defined with the X/XB field are permitted on the PBEAM and PBEAMLentries if, for example, the beam cross section properties change in the middle. Although, outputrequests are only supported at the ends A and B. The software ignores output requests at theintermediate locations (0 < X/XB < 1.0).

Materials

• Only the MAT1 and MATT1 are supported.

• Plasticity and creep are not supported.

Supported loads

• The PLOAD1 bulk entry is supported to apply distributed loads.

• General loads supported by SOL 401 are also supported with bar and beam elements. Forexample, forces using the FORCE, FORCE1, and DAREA bulk entries, and body loads definedwith the ACCELi, GRAV, and RFORCEi bulk entries.

Bar and beam element output summary

• Element results include stress, element force, total strain, elastic strain, and thermal strain.

• Stress and force output requests are only supported at the ends A and B. The software ignoresoutput requests at the intermediate locations (0 < X/XB < 1.0).

• Stress, strain, and force results are always output in the element coordinate system. Theelement coordinates are updated when large rotation occurs and large displacements effects arerequested with PARAM,LGDISP,1.




• The stress & strain output is similar to the existing format for other solutions, except that theminimum and maximum values (S-MIN and S-MAX), and the margin of safety values (M.S. -T,and M.S. -C) are not computed by SOL 401.

• The reported stresses SXC, SXD, SXE, and SXF are a combination of the normal and bendingstress reported in the element axial direction at the cross section locations C, D, E, and F.

• The element force output includes the bending moment and shear force in planes 1 and 2,axial force, total torque, and warping torque.

Spring and bushing element supportYou can now use the CELAS1, CELAS2, CBUSH1D, and CBUSH elements in SOL 401 for stiffnessdefinitions.

CELAS1 - Scalar Spring Connection

• A single CELAS1 element connects two degrees-of-freedom at two different grid points. Itbehaves as a simple extension/compression or rotational spring, carrying either force or momentloads.

• If you define the CELAS1 element between non-coincident grid points, the CELAS1 element doesnot account for the distance between the connecting grid points when transfering loads. This isimportant when you expect your spring stiffness to carry tranverse loads. The CELAS1 elementis safe to use when connecting coincident grid points. The CBUSH element is recommendwhen connecting non-coincident grid points.

• With the CELAS1 element, you can define either a constant or a nonlinear stiffness.

o You define the constant stiffness in the Ki field on the PELAS entry. The constant springstiffness definition is independent of the displacement.

o You define the nonlinear spring when the CELAS1 references both the PELAS and PELASTbulk entries. The TKNID field on the PELAST entry selects a TABLEDi entry, which definesthe force versus displacement data.

• The CELAS1 element does not support large displacement effects when PARAM,LGDISP,1 isdefined. You can include the CELAS1 element in a solution with PARAM,LGDISP,1 defined, butit should not be located in a region of the model where large rotations occur. If you define theCELAS1 as a nonlinear spring, the software uses the nonlinear spring defintion whether largedisplacements are turned on or off.

• You can request force and stress output for the CELAS1 element.

CELAS2 - Scalar Spring Connection

• A single CELAS1 element connects two degrees-of-freedom at two different grid points. Itbehaves as a simple extension/compression or rotational springs, carrying either force ormoment loads.

• If you define the CELAS2 element between non-coincident grid points, the CELAS2 element doesnot account for the distance between the connecting grid points when transfering loads. This is




important when you expect your spring stiffness to carry tranverse loads. The CELAS2 elementis safe to use when connecting coincident grid points. The CBUSH element is recommendwhen connecting non-coincident grid points.

• The CELAS2 element only supports a constant spring stiffness which is independent of thedisplacement. This stiffness is defined in the Ki field on the CELAS2 entry. No property entryis used with the CELAS2 element.

• The CELAS2 element does not support large displacement effects when PARAM,LGDISP,1 isdefined. You can include the CELAS2 element in a solution with PARAM,LGDISP,1 defined, but itshould not be located in a region of the model where large rotations occur.

• You can request force and stress output for the CELAS2 element.

CBUSH1D - Rod Type Spring Connection

• The CBUSH1D element is a one dimensional axial spring.

• The CBUSH1D element stiffness and forces are only axial. It can be used to define an axialspring between coincident or non-coincident grid points. When the grid points are coincident,the x-axis of the coordinate system selected with the CID field on the CBUSH1D entry becomesthe axial direction. When the grid points are non-coincident, the line from grid point A to gridpoint B is the element axis.

• A CBUSH1D element connecting non-coincident grid points supports large displacement effectswhen PARAM,LGDISP,1 is defined. The CBUSH1D element with non-coincident grid points is theonly spring element in SOL 401 which supports large displacements.

A CBUSH1D element connecting coincident grid points does not support large displacementeffects when PARAM,LGDISP,1 is defined. In this case, the CBUSH1D element axis remainsfixed.

• The CBUSH1D element supports either a constant or a nonlinear stiffness option.

The constant spring stiffness definition is independent of the displacement and is defined with theK field on the on the PBUSH1D entry.

The nonlinear spring definition is a force versus displacement table. The software uses thenonlinear spring data when large displacements are turned on or off with the parameter LGDISP.The nonlinear spring is defined by the following fields in the continuation row on the PBUSH1Dentry:

o “SPRING” should be defined in the field 2 of the continuation row.

o "TABLE" should be defined in field 3 of the continuation row.

o The ID of a TABLEDi entry should be defined in field 4 of the continuation row.

o The TABLEDi entry defines the force versus displacement relationship.

• You can request force and stress output for the CBUSH1D element.

CBUSH - Defines a generalized spring.




• A unique feature of the CBUSH element relative to the other spring elements is that it accountsfor the distance between the connecting grid points when transfering loads. As a result, it is asafe choice for connecting either coincident or non-coincident grid points.

• The CBUSH entry supports either a constant, or a nonlinear stiffness option:

o The constant spring stiffness definition is independent of the displacement. This stiffness isdefined in a “K” row on the PBUSH entry, following by a stiffness value for each of the sixdegree-of-freedom.

o The nonlinear spring definition is a force versus displacement table. The nonlinear spring isdefined when the CBUSH entry references both the PBUSH and PBUSHT bulk entries. TheTKNIDi fields on the PBUSHT select the force versus displacement tables. The softwareuses the nonlinear spring when large displacements are turned on or off with the parameterLGDISP.

• The CBUSH element does not support large displacement effects when PARAM,LGDISP,1 isdefined. You can include the CBUSH element in a solution with PARAM,LGDISP,1 defined, but itshould not be located in a region of the model where large rotations occur.

• You can request force, stress, and strain output for the CBUSH element.

• The new system cell 665 is available to globally turn off the computation of the CBUSH couplingmoments when the connecting grid points are not coincident. The new system cell applies to allsolutions except for SOLs 402, 601, and 701.

SYSTEM(665) = 0 (default) The coupling moments are computed.

SYSTEM(665) = 1 The coupling moments are not computed.

Nonlinear bucklingA nonlinear buckling analysis is used to accurately determine what the critical buckling load is andhow a structure behaves after it has buckled. You can now request a nonlinear buckling analysis in aSOL 401 statics subcase. You can choose from one of the following three arc-length methods:

• Riks arc-length method

• Modified Riks arc-length method

• Crisfield arc-length method

To request the nonlinear buckling analysis, your statics subcase should include the standardANALYSIS=STATICS command along with the new NLARCL=ID case control command. The ID onthe NLARCL command selects the new NLARCL bulk entry which defines the nonlinear bucklingparameters.

The NLARCL command in the subcase is the trigger which the software uses to start the nonlinearbuckling analysis. The referenced NLARCL bulk entry is also required, even when the default valuesare used.

The nonlinear buckling statics subcase must be either the first subcase, or the last in a sequence ofstatic subcases. A nonlinear buckling statics subcase can only be followed by a modal subcase.




• If the nonlinear buckling statics subcase is the first subcase, all of the loads defined in the currentsubcase are incrementally applied by the software during the arc-length solution.

• If the nonlinear buckling statics subcase is the last subcase and it is sequentially dependent, theloads applied in the previous subcase are held constant in the current subcase. The differencebetween the load defined in the nonlinear buckling statics subcase and the load from the previoussubcase is computed. This load difference is incrementally applied by the software during thearc-length solution.

You select loads in a nonlinear buckling statics subcase with either the LOAD=n or DLOAD=n casecontrol commands. Although, you cannot increment loads in a nonlinear buckling statics subcasewith a TSTEP1 bulk entry since the software increments the loads for you. If you define a TSTEP1entry in a nonlinear buckling statics subcase, you must define it with a constant time. That is, it musthave an end time (Tend) which is the same as the start time for that subcase. In addition, the outputfrequency option Nout on the TSTEP1 entry is ignored in a nonlinear buckling statics subcase. Theoutput frequency is instead controlled by the NOUTAL parameter on the NLARCL bulk entry.

If you want to define a specific load sequence up to the point of buckling, you can do this with staticsubcases without buckling defined before your nonlinear buckling statics subcase. In these previousstatic subcases, you can increment loads with the TSTEP1 bulk entry.

The new NLARCL bulk entry has the following solution parameters:

TYPE

= RIKS selects the Riks arc-length method

= MRIKS selects the modified Riks arc-length method (Default)

= CRIS selects the Crisfield arc-length method

MINALR Minimum allowable arc-length adjustment ratio between increments for the adaptivearc-length method. (0.0<Real≤1.0; Default=0.25)

MAXALR Maximum allowable arc-length adjustment ratio between increments for the adaptivearc-length method. (Real>=1.0, Default=4.0)

MAXR Defines the overall upper and lower bounds on the load increment /arc-length inthe subcase.

SCALE Scale factor for controlling loading contribution in the arc-length constraint.(Real>0.0; Default = 0.0)

DESITER Desired number of iterations for convergence to be used for the adaptive arc-lengthadjustment. (Integer>0, Default=12)

MXINC Maximum number of controlled load increments done in the arc-length subcase(Integer>0; default=20)

LDFACIN Initial load factor. This load factor will be used to compute initial arc-length (REAL>0,DEFAULT=1.0).

NOUTAL

Skip factor for output of the incremental results. Output always occurs at the finalincrement. For example, if you define NOUTAL=2, output occurs at every otherconverged solution increment and for the final increment. If you define NOUTAL=0,output only occurs at the final increment. (Integer≥0; Default=1)

MXLDFAC Maximum value of load-factor at which solution will be terminated. (Real, Default =1.0)

Initial Imperfections

You define the X,Y,Z location of a grid point on the GRID entry. An option is now available to adjustthis location with a +/- delta X,Y,Z position. For example, if a grid point is defined on the GRID




entry at 1.0, 1.0, 0.0, and a delta of .2, 0.0, 0.0 is defined, the new modeled location for this gridpoint becomes 1.2, 1.0, 0.0. This location adjustment is useful in the nonlinear buckling analysis todefine an imperfection. For example, an imperfection on the side of a cylinder which is under axialcompression will impose a deliberate location for buckling.

The grid point imperfections are selected with the new IMPERF case control command which selectsthe new IMPERF or IMPRADD bulk entries. The IMPRADD entry allows you to combine multipleIMPERF entries, and scale the referenced imperfection sets either independently or collectively.

The IMPERF case control command must be defined globally (above the subcases). As a result, theupdated location of the referenced grid points applies to all subcases.

Restrictions

• The software issues a fatal error if LGDISP=-1 and an arc-length solution is requested.

• The software issues a fatal error if an arc-length solution is requested in the context of aSimcenter Multiphysics solution.

• The software issues a fatal error if a sequentially dependent STATICS or PRELOAD subcasefollows an arc-length subcase.

• The software issues a fatal error if a sequentially dependent arc-length subcase follows anothersequentially dependent arc-length subcase.

• An enforced displacement defined with the SPCD bulk entry is held constant in a nonlinearbuckling solution.

Arc-length theory

The concept of the arc-length method is to modulate the applied loads in order to produce solutionswith displacement increments of manageable size of a given load step. In order to modulate theapplied load, an additional variable, the load factor, and a constraint equation are introduced. Thereare various approaches to providing a constraint equation.

Consider a residual load {R}.

Equation 5-1.

where F represents the internal forces, and the total external load P is expressed as:

Equation 5-2.

where P0 denotes the applied load at the end of the preceding subcase, ΔP represents the loadincrement in the current subcase, and μ is the load factor varying from 0 to 1, but not limited to thisrange, within the subcase. Linearizing {R} about (u,μ), R(u,μ) can be expressed as:




Equation 5-3.

Based on the above equations, the equilibrium condition at (u+Δu, μ+Δμ) dictates that

Equation 5-4.

where, is the follower matrix, is the stiffness matrix , and .

The iteration equation can be derived by rearranging Equation 5-4:

Equation 5-5.

where the follower matrix is omitted. The iterative process can be established by decomposing theequation above into two parts:

Equation 5-6.

Then the trial solution is obtained by

Equation 5-7.

with

Equation 5-8.

where Δμ can be obtained from the constraint equation.

Riks Method and Its Variations

The displacement increment is limited by a constraint equation:

Equation 5-9.




where w is a scaling factor you specify with the SCALE parameter on the NLARCL bulk entry, andΔl is defined by

Equation 5-10.

You define the initial value of Δμ with the LDFACIN parameter on the NLARCL bulk entry. Theconstraint of Equation 5-9 has a disparity in the dimension by mixing the displacements with the loadfactor. For this reason, the scaling factor (w) is introduced so that you can scale μ to the appropriatedimension or delete the Δμ term. The default value of w is zero as demonstrated in Figure 5-4. Theiteration follows the path on the plane normal to the initial tangent as shown in Figure 5-1. Thereforethe subsequent iterations (i > 1) must satisfy

Equation 5-11.

Recalling that the first iteration should result in

Equation 5-12.

Equation 5-11 may be reduced to

Equation 5-13.

from which the load factors for the subsequent iterations are determined by

Equation 5-14.

and

Equation 5-15.

Notice that the normal plane does not change during the iteration by Riks method. In addition, {ΔuP}remains constant if the iteration process is the modified Newton's method.




Alternatively, the normal plane may be updated at every iteration. If the normal plane is to be normalto the cumulative incremental displacements for the preceding iterations as shown in Figure 5-2, theorthogonality condition in Equation 5-11 should be modified to:

Equation 5-16.

The increment in the load factor for i > 1 is obtained by solving Equation 5-16,

Equation 5-17.

This variation of Riks method has an advantage over the Crisfield method as it avoids the solution ofa quadratic equation.

Crisfield Method

Instead of iterating on the normal plane, the solution is sought on the surface defined by Equation 5-9with an arc-length of Δl as depicted in Figure 5-3,

Equation 5-18.

This constraint can be interpreted as keeping the incremental displacement constant, if w=0, asshown in Figure 5-4. Substituting Equation 5-8 into the preceding equation, we obtain a quadraticequation in terms of Δμ:

Equation 5-19.

where

Equation 5-20.

Since the Crisfield method leads to a quadratic equation, the selection of the proper root of thisequation becomes the most critical process for the success of this method. There are two roots toEquation 5-19,




Equation 5-21.

The root is chosen so that the angle between two vectors {ui-1 - uo} and {ui - uo} is less than 90degrees,

Equation 5-22.

There are cases where no roots can be found. Such is the case when the trial solution is far from thetrue solution and stays outside the region covered by the arc-length. In this case, the trial solutionvector is scaled so that the direction vector intersects with the surface defined by Equation 5-18.

The wrong choice of the root could cause an unintentional loading path reversal, by which the solutionreturns to the previous state. Such cases can be detected by checking the orthogonality of theincremental displacements of the two successive solutions. If this case is detected, the root is chosenso that the angle between {ui - uo} and {ui - uo} is an acute angle.

Adaptive Arc-Length Method

It is difficult to estimate a proper arc-length for multi-degree-of-freedom problems. The initialarc-length for the Crisfield method can be determined by

Equation 5-23.

with

Δμ1 = μ1 = LDFACIN parameter on the NLARCL bulk entry.

You can define the maximum number of increments in the subcase with the MXINC parameteron the NLARCL bulk entry.

The arc-length should be continuously updated at every increment using the information gatheredduring the preceding increment. One method is to reduce the arc-length if it requires an excessivenumber of iterations to attain a converged solution,

Equation 5-24.




where Id is the desired number of iterations for convergence and defined with the DESITERparameter on the NLARCL bulk entry, and Imax is the number of iterations required for convergencefrom the preceding step.

The adaptive process should be based on the arc-length ratio,

Equation 5-25.

Combining two criteria, the new arc-length ratio is adapted to the nonlinearity by

Equation 5-26.

In order to maintain the stability for the adaptive process, ALRATIO should also be bounded,

MINALR < ALRATIO < MAXALR

You can define the parameters MINALR and MAXALR on the NLARCL bulk entry, which have thedefaults of 0.25 and 4., respectively. If the adjusted ALRATIO falls outside the bounds, ALRATIOis reset to the limit. Then the arc-length is updated at the beginning of the next step based onALRATIO as follows:

Δlnew = ALRATIO * Δlold

In the unstable regime where the stiffness is negative, the load factor decreases with a forward step.When this happens, the sign of Δμ1 should be reversed. This possibility should be examined at thebeginning of each increment. The sign can be determined by the sign of a dot product,

Equation 5-27.

An adaptive bisection algorithm is also incorporated to cope with divergent cases. If the iterativeprocess using the arc-length method tends to diverge, the arc-length is bisected. The bisection iscombined in concert with the stiffness matrix update strategy. The bisection procedure continuesuntil the iterative process is stabilized and a converged solution is found. However, the number ofcontiguous bisections is limited by the parameter MAXBIS on the NLCNTL bulk entry. The variablearc-length at every increment invokes the recovery from the bisection process once the difficulties inconvergence are overcome.




Figure 5-1. Riks Method

Figure 5-2. Modified Riks Method




Figure 5-3. Crisfield Method - Arc-length in terms of Combined Variables

Figure 5-4. Crisfield Method - Arc-length in terms of Displacements




NLARCL

SOL 401 nonlinear buckling request

Requests a nonlinear buckling solution in a SOL 401 statics subcaseFORMAT:

NLARCL=nEXAMPLES:

NLARCL=33

DESCRIBERS:

Describer Meaning

n Set identification number of a NLARCL bulk entry. (Integer>0)

REMARKS:1. To request the nonlinear buckling analysis in SOL 401, your statics subcase

should include the standard ANALYSIS=STATICS command and the NLARCLcommand. The ID on the NLARCL command selects the NLARCL bulk entrywhich defines the nonlinear buckling parameters.

2. The NLARCL command in the subcase is the trigger which the software uses tostart the nonlinear buckling analysis. The referenced NLARCL bulk entry is alsorequired, even when the default values are used.

3. The nonlinear buckling statics subcase must be either the first subcase, or thelast in a sequence of static subcases. A nonlinear buckling statics subcase canonly be followed by a modal subcase.

a. If the nonlinear buckling statics subcase is the first subcase, all of the loadsdefined in the current subcase are incrementally applied by the softwareduring the arc-length solution.

b. If the nonlinear buckling statics subcase is the last subcase and it issequentially dependent, the loads applied in the previous subcase are heldconstant in the current subcase. The difference between the load defined inthe nonlinear buckling statics subcase and the load from the previous subcaseis computed. This load difference is incrementally applied by the softwareduring the arc-length solution.




IMPERF

SOL 401 Grid Point Position Deltas

Selects grid point position deltas in SOL 401.FORMAT:

IMPERF=nEXAMPLES:

IMPERF=33

DESCRIBERS:

Describer Meaning

n Set identification number of an IMPRADD or IMPERF bulk entry.(Integer>0)

REMARKS:1. This command is only supported in SOL 401.

2. The IMPERF case control command must be defined globally (above thesubcases). As a result, the updated location of the referenced grid points appliesto all subcases.

3. You can use the IMPERF bulk entry to adjust the X,Y,Z location of a grid pointwith a positive or negative delta.

4. The set identification number n can refer to a IMPRADD entry which thencombines multiple IMPERF entries, or it can refer to an individual IMPERF entry.

5. The deltas are also referred to as imperfections since they can be used in anonlinear buckling solution to induce a buckling condition.




NLARCL

SOL 401 Nonlinear Buckling Control

Defines control parameters for SOL 401 nonlinear buckling.FORMAT:

1 2 3 4 5 6 7 8 9 10

NLARCL ID PARAM1 VALUE1 PARAM2 VALUE2 PARAM3 VALUE3

PARAM4 VALUE4 PARAM5 VALUE5 -etc-

EXAMPLE:

NLARCL 1 TYPE CRIS MINALR 0.25 MAXALR 4.0

SCALE 0.0

FIELDS:

Field Contents

SID Identification number. (Integer > 0)

PARAMi Name of the NLARCL parameter. Allowable names are given in theparameter listing below. (Character)

VALUEi Value of the parameter. (Real, Integer, or Character)

NLARCLPARAMETERS:

Table 5-1.

Name Description

TYPE = RIKS selects the Riks arc-length method

= MRIKS selects the modified Riks arc-length method (Default)

= CRIS selects the Crisfield arc-length method

MINALR Minimum allowable arc-length adjustment ratio between increments forthe adaptive arc-length method. (0.0<Real≤1.0; Default=0.25)

MAXALR Maximum allowable arc-length adjustment ratio between incrementsfor the adaptive arc-length method. (Real≥1.0, Default=4.0)

MAXR Defines the overall upper and lower bounds on the load increment/arc-length in the subcase. (Real>0.0; Default = 20.0)

SCALE Scale factor for controlling loading contribution in the arc-lengthconstraint. (Real>0.0; Default = 0.0)




Table 5-1.

Name Description

DESITER Desired number of iterations for convergence to be used for theadaptive arc-length adjustment. (Integer>0, Default=12)

MXINC Maximum number of controlled load increments done in the arc-lengthsubcase (Integer>0; Default=20)

LDFACIN Initial load factor. This load factor will be used to compute initialarc-length (Real>0, Default=1.0).

NOUTAL Skip factor for output of the incremental results. Output always occursat the final increment. For example, if you define NOUTAL=2, outputoccurs at every other converged solution increment and for the finalincrement. If you define NOUTAL=0, output only occurs at the finalincrement. (Integer≥0; Default=1)

MXLDFAC Maximum value of load-factor at which solution will be terminated.(Real, Default = 1.0)

REMARKS:1. To request the nonlinear buckling analysis in SOL 401, your statics subcase

should include the standard ANALYSIS=STATICS command and the NLARCLcommand. The ID on the NLARCL command selects the NLARCL bulk entrywhich defines the nonlinear buckling parameters.

2. The NLARCL case control command in a statics subcase is the trigger which thesoftware uses to start the nonlinear buckling analysis. The referenced NLARCLbulk entry is also required, even when the default values are used.

3. The nonlinear buckling statics subcase must be either the first subcase, or thelast in a sequence of static subcases. A nonlinear buckling statics subcase canonly be followed by a modal subcase.

a. If the nonlinear buckling statics subcase is the first subcase, all of the loadsdefined in the current subcase are incrementally applied by the softwareduring the arc-length solution.

b. If the nonlinear buckling statics subcase is the last subcase and it issequentially dependent, the loads applied in the previous subcase are heldconstant in the current subcase. The difference between the load defined inthe nonlinear buckling statics subcase and the load from the previous subcaseis computed. This load difference is incrementally applied by the softwareduring the arc-length solution.




IMPERF

SOL 401 Grid Point Position Deltas

Defines grid point position deltas for SOL 401.FORMAT:

1 2 3 4 5 6 7 8 9 10

IMPERF SID CS

GRID 1 ΔX1 ΔY1 ΔZ1

GRID 2 ΔX2 ΔY2 ΔZ2

-etc-

EXAMPLE:

IMPERF 2 0

1 -0.008 0.0367 0.234

2 0.001 -0.0005 0.067

FIELDS:

Field Contents

SID Set identification number. (Integer > 0)

CS Coordinate system in which deltas are specified. (Integer > 0;Default=0)

GRIDi Grid point identification number. (Integer > 0)

ΔXi, ΔYi,ΔZi

Grid point position deltas (Real; No default)

REMARKS:1. Only supported in SOL 401.

2. You can use the IMPERF bulk entry to adjust the X,Y,Z location of a grid pointwith a positive or negative delta.

3. The IMPERF case control command which references a IMPERF bulk entry mustbe defined globally (above the subcases). As a result, the updated location of thereferenced grid points applies to all subcases.

4. The grid point deltas are also referred to as imperfections since they can be usedin a nonlinear buckling solution to induce a buckling condition.




IMPRADD

SOL 401 Union of Grid Point Position Delta Sets

Defines a union of grid point position delta sets defined with multiple IMPERF bulkentries for SOL 401.

FORMAT:

1 2 3 4 5 6 7 8 9 10IMPRADD SID S S1 I1 S2 I2 S3 I3

S4 I4 -etc-

EXAMPLE:

IMPRADD 1 1.000 1.000 1 1.2 2 0.25 3

-1.5 7

FIELDS:

Field Contents

SID Overall set identification number referenced on the IMPERF casecontrol command. (Integer > 0)

S Overall scale factor (Real, Default=1.0)

Si Scale factor for individual IMPERF bulk entries. (Real, Default=1.0)

Ii Set identification numbers of individual IMPERF bulk entries. (Integer> 0)

REMARKS:1. Only supported in SOL 401.

2. SID must be unique to other IMPRADD entries.

3. The IMPRADD entry allows you to combine multiple IMPERF bulk entries into asingle set and optionally scale the referenced individual sets either independentlyor collectively.




Bolt preload improvements for SOL 401The SOL 401 bolt preload method iterates to determine the uniform axial strain which produces theaxial bolt force you request. The software then reapplies the computed strain for the consecutivesubcases. The initial strain method is selected by defining ETYPE=3 on the BOLT bulk entry.

A new optional cut-plane method is available for SOL 401 and selected by defining ETYPE=2 on theBOLT bulk entry. With the new cut-plane method, the software cuts the bolt in half, it creates newgrid points such that grid pairs exist at the cut, it creates a glue connection at the cut with the axialstiffness zeroed out, it evenly distributes the opposing axial bolt force to the grids on each side ofthe cut, then it solves a statics solution to determine the axial displacement of each bolt half. Thesoftware then stiffens the axial glue connection which holds the grid pairs in their relative deformedstate for the consecutive subcases.

Both the existing ETYPE=3 uniform strain method and the new ETYPE=2 cut-plane method produceaccurate results, including when the bolt bends or when large rotations occur with geometry nonlinear.

Two advantages of the new ETYPE=2 cut-plane method are:

• Since the software does not need to iterate on the axial strain, this method can be more efficient.

• Since the inputs are consistent with SOL 101, it is easier to convert an input file from SOL 101 toSOL 401.

Both the ETYPE=3 uniform strain method, and the ETYPE=2 cut-plane method allow you to modelbolts with either the 3D solid elements CHEXA, CPENTA, and CTETRA, or the 2D plane stresselements CPLSTS3, CPLSTS4, CPLSTS6, and CPLSTS8. A preload subcase is required, and it caninclude geometric and material nonlinear conditions.

Note that all of the BOLT bulk entries referenced in the same input file must be either ETYPE=2, or allETYPE=3. A fatal error will occur if BOLT entries with both ETYPE=2 and ETYPE=3 are referenced.

See the updated BOLT entry.

Defining a BOLT bulk entry for the cut-plane method (ETYPE=2)

The cut-plane method requires that you use the ETYPE=2 input format on the BOLT bulk entry. Withthis format, you list the grid point IDs connected to the element edges (2D bolt) or faces (3D bolt)where the software will cut the bolt. You define the list of grid points in the Gi fields on the BOLT entry.

You optionally define the CSID and IDIR fields on the BOLT bulk entry:

• The bolt coordinate system can optionally be defined on the CSID field.

• The bolt axial direction can optionally be defined on the IDIR field.

Alternately, if you leave both the CSID and IDIR fields blank, the software will automatically determinethe coordinate system and the bolt axis. In this case, the grid points listed in Gi must be coplanar.

When you define IDIR as non-zero, the software does not determine the bolt axis, and the grid pointslisted in Gi do not need to be coplanar. Although, it is recommended that they are approximately on aplane perpendicular to the bolt axis you defined.




Note

For the NX Nastran 12 release, when using the new ETYPE=2 cut-plane method, the gridpoints listed in Gi should be coplanar, or at least close to coplanar. If your bolt cut-plane isnot planar, your solution results may not be accurate. If you define a ETYPE=2 bolt with anon-planar cut-plane, the software will still solve without a warning.

If the grid points listed on Gi are not coplanar, you should use the uniform strain method bydefining the ETYPE=3 bolt.

When you use the cut-plane method and you choose to define your preload on an associatedBOLTFRC bulk entry, you can define your preload on an associated BOLTFRC bulk entry as adisplacement or a force. The STRAIN preload option on the BOLTFRC bulk entry is not supported withthe cut-plane method and will cause a fatal error if defined. If you use the displacement option, thevalue you enter is the total shortening of the bolt length as result of your bolt preload. The LEN field onthe BOLTFRC bulk entry which defines the bolt length is ignored when you use the cut-plane method.

Defining a BOLT bulk entry for the uniform strain method (ETYPE=3)

The uniform strain method requires that you use the ETYPE=3 input format on the BOLT bulk entry.With this format, you list all of the 2D or 3D element IDs which define the bolt.

You optionally define the CSID and IDIR fields on the BOLT bulk entry:

• The bolt coordinate system can optionally be defined on the CSID field, and the bolt axialdirection can optionally be defined on the IDIR field.

• Alternately, if you leave both the CSID and IDIR fields blank, the software will automaticallydetermine the coordinate system and the bolt axis.

You optionally define the GP field on the BOLT bulk entry:

• You can optionally define the GP field identification number of the grid point where the bolt crosssectional area is calculated. The grid point you enter must be included in the connectivity ofelements that are used to model the bolt. As a best practice, you should select GP such that it isnear the middle of the cross section of the bolt.

• Alternately, if you leave the GP field blank, the software will automatically determine a middlelocation to compute the cross sectional area.




BOLT

Bolt definition

Selects the elements to be included in the bolt preload calculation.FORMAT FOR

ETYPE = 1:

1 2 3 4 5 6 7 8 9 10

BOLT BID ETYPE EID1 EID2 EID3 EID4 EID5 EID6

EID7 “THRU” EID8 “BY” INC

-etc-

FORMAT FORETYPE = 2:

1 2 3 4 5 6 7 8 9 10

BOLT BID ETYPE CSID IDIR G1 G2 G3 G4

G5 “THRU” G6 “BY” INC

-etc-

FORMAT FORETYPE = 3:

1 2 3 4 5 6 7 8 9 10

BOLT BID ETYPE CSID IDIR GP

EID1 EID2 EID3 EID4 EID5 EID6 EID7 EID8

EID9 “THRU” EID10 “BY” INC

-etc-

EXAMPLES:ETYPE = 1 for SOLs 101, 103, 105, 107 through 112

BOLT 4 1 11

ETYPE = 1 for SOL 601BOLT 4 1 11 8 2 1 20 14

15 16 28 30 33

ETYPE = 2BOLT 8 2 4 3 12 23 55 128

133 THRU 165

ETYPE = 3BOLT 9 3 1 3 148

56 24 43 21 73 52 62 41

106 THRU 202




FIELDS:

Field Contents

BID Bolt identification number. (Integer > 0)

ETYPE Element type. (Integer; No default)

= 1 to model bolts with CBAR and CBEAM elements in SOLs 101,103, 105, 107 through 112, 402, and 601.

= 2 to model bolts with CHEXA, CPENTA and CTETRA elements inSOLs 101, 103, 105, 107 through 112, 401 and 402.

= 3 to model bolts with CHEXA, CPENTA, CTETRA, CPLSTS3,CPLSTS4, CPLSTS6, and CPLSTS8 elements in SOLs 401 and 402,or CHEXA, CPENTA, CPYRAM, and CTETRA elements in SOL 601.

“BY” Specifies an increment when using THRU option. (Character)

INC Increment used with THRU option. (Integer; Default = 1)

INC > 0 can be defined, for example ...106,THRU,126,BY,INC,2

INC < 0 can be defined, for example ...126,THRU,106,BY,INC,-2

FIELDS FORETYPE = 1:

Field Contents

EIDi Selects element identification numbers to include in the bolt preloadcalculation. See Remark 2 and SOL 601 Remark 1. (Integer > 0, orusing “THRU”; EID7 < EID8 for THRU option; No default)


Field Contents

CSID Identification number of the coordinate system used to define the boltaxis. For the basic coordinate system, CSID = 0. (Integer ≥ 0; SeeRemark 7 for default behaviour.)

IDIR Direction of bolt axis relative to CSID. (Integer; See Remark 7 fordefault behaviour.)

= 1 for the X direction

= 2 for the Y direction

= 3 for the Z direction

See SOL 401 Remark 2.

See SOL 402 Remark 6.




Field Contents

Gi Identification numbers of grid points that form a cross section throughthe bolt. See Remarks 3 and 4. (Integer ≥ 0; No default)


Field Contents

EIDi Selects element identification numbers to include in the bolt preloadcalculation. All elements representing the bolt must be included inEIDi, and have the same PID. (Integer > 0, or using “THRU”; EID7 <EID8 for THRU option; No default)

CSID Identification number of the coordinate system used to define thebolt axis. For the basic coordinate system, CSID = 0. (Integer ≥ 0;Default=0)

IDIR Direction of bolt axis relative to CSID. (Integer; Default = 0)

= 0 for automatic determination of the bolt axis.

= 1 for the X direction

= 2 for the Y direction

= 3 for the Z direction

See SOL 401 Remark 3. See SOL 402 Remarks 1, 2 and 3 . SeeSOL 601 Remark 2.

GP For SOL 401, the identification number of the grid point where the boltcross sectional area is calculated. See Remarks 3 and 5. See alsoSOL 401 Remark 3. (Integer > 0 or blank)

For SOL 402, the identification number of the grid point where the boltcross sectional area is calculated. See Remark 3. See also SOL 402Remarks 4 and 5. (Integer > 0; No default)

For SOL 601, the identification number of the grid point where the boltis split. See Remark 3 and SOL 601 Remarks 3 and 4. (Integer ≥0 or blank)

REMARKS:1. Each BOLT entry defines a single physical bolt which can be composed of multiple

elements.

2. If multiple CBAR and CBEAM elements are used to model a bolt in SOL 101, 103,105, 107 through 112, only one of the elements must be listed on the BOLT entry.Enter the element ID in the EID1 field.

3. Any grid point listed in the Gi or GP fields must be included in the connectivity ofelements that are used to model the bolt.




4. Gi must select enough GRID entries to define a cross section through the bolt.The selected Gi can only be included on a single BOLT entry. The grids can belisted in any order on the BOLT entry. For parabolic elements, mid-nodes mustalso be listed. Any Gi listed on a BOLT entry cannot be used in the connectivity ofa solid composite element or be included in an SPC.

The software splits the bolt mesh by duplicating each Gi on the BOLT entry.The identification numbers for the duplicated grid points start at the highestuser-defined grid ID in the model plus one and continue sequentially higher.

A pressure load cannot be applied to any face of an element if the connectivityof the element includes a Gi listed on a BOLT entry.

5. As a best practice, select GP such that it is near the middle of the cross section ofthe bolt.

6. In SOL 105, both the bolt preload and service load are scaled to determine thebuckling load.

7. For SOLs 101, 103, 105, 107 through 112, if you leave both the CSID and IDIRfields blank, the software automatically determines the coordinate system and thebolt axis. In order to do this computation, the grid points listed in the Gi fields mustlie approximately on a plane perpendicular to the intended bolt axis. If the cut youdefine is not close to being planar, a fatal error will occur. In addition, if the cut isplanar but the plane is not perpendicular to the intended bolt axis, the softwarecomputed coordinate system and bolt axis will be skewed from the intended boltaxis, and your preloads will not be accurate.

Regardless if the CSID and IDIR fields are defined or not defined, when using theETYPE=2 cut-plane method, the grid points listed in Gi should be coplanar, or atleast close to coplanar. If your bolt cut-plane is not planar, your solution resultsmay not be accurate. If you define a ETYPE=2 bolt with a non-planar cut-plane,the software will still solve without a warning.

8. For SOL 101, when you define a bolt with ETYPE=2, the software cuts the bolt inhalf, it creates new grid points resulting in grid pairs at the cut, it evenly distributesthe opposing axial bolt force to the grids on each side of the cut, and it solves astatics solution to determine the axial displacement of each bolt half. The softwarethen holds the grid pairs in their relative deformed state for the consecutive staticsolution. Begininning in NX Nastran 12, the software creates a glue connection atthe cut which holds the grid pairs in their relative deformed state. The glue basedapproach accounts for bending along the bolt axis since rotational stiffness isincluded in the glue condition.

The glue approach is supported by the default sparse solver, but not supported bythe element iterative solver in SOL 101. If you run with the element iterative solverin SOL 101 and you have defined the ETYPE=2 bolt, the software will revert to anMPC approach. The MPC approach accounts for the axial stiffness, but not therotations. As a result, bending is not accounted for with the MPC approach.




REMARKSRELATED TO

SOL 601:1. All CBAR and CBEAM elements used to model the bolt must be included in EIDi

list and they all must have the same PID.

2. When IDIR = 0 or blank (default), the direction of the bolt axis is automaticallydetermined by the software to coincide with minimum principal moment of inertiaof the bolt. CSID is ignored when IDIR = 0 or blank.

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

4. GP = 0 or blank is allowed only if IDIR = 0 or blank. In this case, the location of thebolt plane is automatically determined by the program.

REMARKSRELATED TO

SOL 401:1. All of the BOLT bulk entries referenced in the same input file must be either

TYPE=2, or all TYPE=3. A fatal error will occur if BOLT entries with both TYPE=2and TYPE=3 are referenced.

2. ETYPE=2 remarks.

• When using the ETYPE=2 cut-plane method, the grid points listed in Gi shouldbe coplanar, or at least close to coplanar. If your bolt cut-plane is not planar,your solution results may not be accurate. If you define a ETYPE=2 bolt witha non-planar cut-plane, the software will still solve without a warning. If thegrid points listed on Gi are not coplanar, you should use the uniform strainmethod by defining the ETYPE=3 bolt.

• When CSID and IDIR are both blank, the software automatically determinesthe coordinate system and the bolt axis. In this case, the grid points listed inGi must be coplanar.

• If you define IDIR as non-zero, the software does not determine the bolt axis.In this case, the grid points listed in Gi do not need to be coplanar. Although,it is recommended that they are approximately on a plane perpendicular tothe bolt axis.

3. ETYPE=3 remarks.

• When CSID and IDIR are blank, the software automatically determines thecoordinate system and the bolt axis.

• When GP blank, the software automatically determines a middle locationto compute the cross sectional area.

4. Composite solid elements (PCOMPS property card) are not supported forpreloaded bolts.




REMARKSRELATED TO

SOL 402:1. When IDIR = 0 or blank (default), the direction of the bolt axis is automatically

determined by the software to coincide with minimum principal moment of inertiaof the bolt. CSID is ignored when IDIR = 0 or blank.

2. When IDIR is not specified, internal faces along the bolt cut are connected usingcontact elements. When it is specified, each face of the bolt cut are connected toan RBE3 element and both elements are linked to the same master node.

3. If IDIR >0, the cut cannot be perpendicular to the bolt axis.

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

5. If GP = 0 or blank, the location of the bolt plane is automatically determined bythe program.

6. When ETYPE = 2, if grid points of the cut are not coplanar, IDIR must be specified.

7. ETYPE=2 is the preferred method to model bolts.

Balanced initial stress-strainThe option to apply an unbalanced initial stress-strain became available in NX Nastran 11. Anunbalanced initial stress-strain results in deformation when applied to an unconstrained body withthe possibility of residual stress. For example, since approximate methods are used to measureresidual stress, the application of the residual stress in your finite element analysis as an initialcondition may not result in a state of complete equilibrium, and instead may result in both residualstress and deformation.

Note that the definition of an NX Nastran unbalanced initial stress-strain references the unconstrainedbody, although, an initial stress-strain can be applied to constrained or unconstrained models.

A new method is available in NX Nastran 12 which you can use to balance an unbalanced initialstress-strain. The method removes the unbalanced part by removing the strains which producea deformation. After you use the new balancing method, your initial stress-strain will produce aself-equilibrating stress state and no deformations.

The method requires that a part of your unbalanced initial stress-strain is actually balanced.

Offset solutionThe balancing method requires that you first run a static offset-solution to obtain the total strain outputas a result of your unbalanced initial stress-strain with the model unconstrained. You only apply theunbalanced initial stress-strain in the offset solution. No temperature loads, mechanical loads, orenforced displacements are applied for this step.

Since there is no thermal strain {εth}, the total strain output {ε} from the offset-solution is computed as:

{ε} = {εe} + {εin} - {ε0}

where,

{ε} = total strains you can request with the STRAIN case control command,




{εe} = elastic strains you can request with the ELSTRN case control command,

{εin}= inelastic strains you can request with the PLSTRN or CRSTRN case control commands,

{ε0} = initial strains you can request with the OSTNINI case control command.

The part of the unbalanced initial stress-strain {ε0} which yields a stress is included in the elastic strain{εe} and possibly the inelastic strain {εin} if you have included any nonlinear materials. After removing{εe} and {εin} from the unbalanced initial stress-strain {ε0}, the total strain {ε} output from the offsetsolution includes only the part of the initial stress-strain which causes deformation.

You will use the total strain {ε} output from the offset-solution as an offset strain {εoff} in theconsecutive solution.

The total strain output is requested with the STRAIN=ALL case control command. If your modelcontains multiple components, each with a unique balanced initial strain, you can run an offset-solutionfor each component separately. The offset strains can be used in a consecutive assembly solution.

Note that, regardless if your initial stress-strain is applied to all locations on a component or to only aportion, the offset strains are the total strains at all locations on that component.

To allow the static offset-solution to complete with the unconstrained condition, a matrix stabilizationoption is available. Setting the new parameter MSTAB to 1 on the NLCNTL bulk entry will turn onthe option. In addition, the new MSFAC parameter is available to define a scale factor for matrixstabilization. Specifically, when you define MSTAB=1, the software scales the diagonal terms bythe factor (1+MSFAC).

Balanced solution

Once your offset strains are computed, you can run the consecutive balanced solution that includesyour initial stress-strain {ε0}, your offset strain {εoff}, and any other loads (temperature loads,mechanical loads, enforced displacements).

You can optionally run a consecutive balanced solution as unconstrained with only your initialstress-strain {ε0} and your offset strain {εoff} to verify that the strain offsets have removed alldeformation leaving only the stress state. You can use the matrix stabilization option (MSTAB=1) inthe verification solution if you choose to keep your model unconstrained for this step. Finally, youcan apply initial stress-strain {ε0} and your offset strain {εoff} in a balanced component or assemblysolution which includes any load types and constraints.

During the balanced solution, the offset strains are included in the internal force calculation tocompensate for the deformations caused by your initial stress-strain. See Balanced stress-straincomputation for details.

Defining a balanced initial stress or strain condition

The new INITS(OFFSET) case control command and INITSO bulk entry are available to input theoffset strain. Multiple INITSO bulk entries can be combined with the existing INITADD bulk entry.

You define the initial stress-strain with the INITS case control command, which selects the INITS bulkentry. You can also define multiple INITS bulk entries, each with a unique ID, and then combine themusing the INITADD bulk entry. The INITADD entry is selected with the ID on the INITS case control.The INITS case control command must be defined globally, above the subcases. It is reapplied inevery static subcase.

The software does not need to associate a balanced initial stress-strain definition with an offset straindefinition in the balanced solution. As a result, the SID defined on the INITS(OFFSET) command




selecting your offset strains, and the SID defined on the INIT command selecting your unbalancedinitial stress-strain can match, or not match. There is no software requirement either way.

You cannot define an initial stress-strain on the newly supported beam and shell elements, although,these elements can be included in the solution which includes an initial stress-strain.

Multiple initial stress-strain at the same location

Currently, if you define initial stress-strain on the same grid or element corner location, a fatal erroroccurs.

In NX Nastran 12, this will no longer be a restriction. You can now define multiple unbalanced andbalanced initial stress-strain at the same location. They can also be defined using different coordinatesystems. The software first converts all stress definitions to strain, then it transforms all strain into thebasic coordinate system, and finally it adds the strains defined at common locations.

Balanced stress-strain computation

The reference (modeled) configuration of a component with balanced initial stress/strain includesinitial strains. Therefore, under the deformation field resulting from combined initial strains andservice loads, the total strains measured from the reference configuration is given by:

{ε} = f({u}) + {εoff}

where,

f({u}) = [B]{u}

with [B] being the strain displacement matrix for small strain formulation.

The total strains are decomposed as:

{ε} = {εe} + {εth} + {εin} - {ε0}

where,

{ε} = total strains which you can request with the STRAIN case control command,

{εe} = elastic strains you can request with the ELSTRN case control command,

{εth} = thermal strains you can request with the THSTRN case control command,

{εin} = inelastic strains you can request with the PLSTRN case control command,

{ε0} = initial strains you can request with the OSTNINI case control command.

The elastic strains are obtained as,

{εe} = {ε} - {εth} - {εin} + {ε0}

In terms of balanced strain offsets, and assuming small strain formulation, the elastic strains aregiven by

{εe} = [B]{u} - {εth} - {εin} + ({ε0} + {εoff})

For components in the model without initial strains, {ε0} = {0} and {εoff} = {0}. For the components withunbalanced initial strains, {εoff} = {0}.

Note that if you request the total strain output {ε} for the balanced solution with the STRAIN casecontrol command, the software will add the offset strain back to the total as if it was never removed forthe solution. As a result, the total strain computation when a balanced initial stress-strain is defined isthe same as when an unbalanced initial stress-strain is defined.




Converting an initial stress to an initial strain

If you define an initial stress {σ0}, the software converts this to a corresponding initial strain {ε0} byusing the elasticity matrix {D0} at the reference temperature Tref.

{ε0} = {D0}-1 {σ0}

Defining an initial stress or strain condition

The option to define an initial stress or strain condition is available on all elements in SOL 401except for beam elements, shell elements, plane strain elements, generalized plane strain elements,solid composite elements, and rigid elements.

You define the initial stress or strain with the INITS case control command, which selects the INITSbulk entry. The INITS case control command must be defined globally, above the subcases. Itis reapplied in every static subcase.

The first row on the INITS bulk entry includes the following fields.

• The TYPE field defines the data type: TYPE=STRESS or TYPE=STRAIN

• The CSYS field selects the coordinate system for the stress or strain components. The default isthe basic coordinate system. CSYS = -1 can also be defined to select the material system.

• The LOC field defines the location:

LOC= GRID: Specifies that data is defined at grid points.

LOC= NOE: Specifies that data is defined on an element at grid locations. This can includecorner and/or midside grid locations.

You define the stress or strain data on the consecutive rows on the INITS entry. The softwareassumes the data is either engineering stress or engineering strain. The format of these rowsdepends on the data location defined in the LOC field, and the element type.

Format for the 3D solid elements CTETRA, CHEXA, CPENTA and CPYRAM:Stress at grid points (TYPE=STRESS, LOC=GRID):

GRID ID Sxx Syy Szz Sxy Syz Szx....

Strain data at grid points (TYPE=STRAIN, LOC=GRID):GRID ID Exx Eyy Ezz Exy Eyz Ezx

...

Stress data at the element corners (TYPE=STRESS, LOC=NOE):ElemID GRIDID Sxx Syy Szz Sxy Syz Szx

...

Strain data at the element corners (TYPE= STRAIN, LOC=NOE):ElemID GRIDID Exx Eyy Ezz Exy Eyz Ezx

...

For the plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8, the software uses bothin-plane and out-of-plane initial strain values. Although, only in-plane initial stress values are used.For example, the following formats should be used when the plane stress elements are defined onthe XY plane, and the basic coordinate system (default) is used. For elements defined on the XZplane, Sxx, Szz, Szx or Exx, Eyy, Ezz, Ezx would be defined.




Stress data at grid points (TYPE=STRESS, LOC=GRID):GRID ID Sxx Syy Sxy

...

Strain data at grid points (TYPE=STRAIN, LOC=GRID):GRID ID Exx Eyy Ezz Exy

...

Stress data at the element corners (TYPE=STRESS, LOC=NOE):ElemID GRIDID Sxx Syy Sxy

...

Strain data at the element corners (TYPE= STRAIN, LOC=NOE):ElemID GRIDID Exx Eyy Ezz Exy

...

For the axisymmetric elements CQUADX4, CQUADX8, CTRAX3, CTRAX6, in-plane (radial andaxial) and out-of-plane (theta) initial stress or strain values are used by the software. For example,the following formats should be used when the axisymmetric elements are defined on the XY plane,and the basic coordinate system (default) is used. For elements defined on the XZ plane, Sxx,Szz, Szx or Exx, Ezz, Ezx should be defined.

Stress data at grid points (TYPE=STRESS, LOC=GRID):GRID ID Sxx Syy Szz Sxy

...

Strain data at grid points (TYPE= STRAIN, LOC=GRID):GRID ID Exx Eyy Ezz Exy

...

Stress data at the element corners (TYPE=STRESS, LOC=NOE):ElemID GRIDID Sxx Syy Szz Sxy

...

Strain data at the element corners (TYPE= STRAIN, LOC=NOE):ElemID GRIDID Exx Eyy Ezz Exy

...

For the plane stress and axisymmetric elements, if you select a coordinate system other than thebasic system in the CSYS field on the INITS entry, the software first transforms the data into the basicsystem, and then uses the components consistent with the formats described above.

The option to output the initial strains using the OSTNINI case control command is available. Theoutput can be requested at either the grid or corner Gauss locations on elements. The OSTNINIcommand must be defined globally, and the output occurs once at the beginning of the solution. Thestrains are output in the basic coordinate system.

Additional information:

• Initial stress and strain can be defined on a subset of the model. The software assumes a valueof 0.0 at the locations where data is undefined. An exception is when data is undefined at amid-side grid point, and data is defined at both or either related corners. In this case, the softwareinterpolates a value for that mid-side grid point.

• The option to apply an initial stress or strain condition before applying other loads in an initialsubcase is available to help convergence. The first subcase should have Tend=0.0 on the




TSTEP1 entry and no load set selected. The number of increments can optionally be definedwith NINC on the TSTEP1 entry to increment the initial stress or strain. When NINC=1 (default),the initial stress or strain is applied in a single step. When NINC>1, the initial stress or strain isramped. A service load cannot be defined when ramping initial stress or strain with NINC>1.

• The software converts an initial stress to an initial strain using the elastic modulus defined onthe MATi entries. If you define MATTi bulk entries to define the elastic modulus as temperaturedependent, the software uses the initial temperatures selected by the TEMPERATURE(INIT)case control command to evaluate the temperature dependent elastic modulus. Data on theMATS1 bulk entry, if defined, is not used to convert stress to strain.

• You can define multiple INITS bulk entries, each with a unique ID, and then combine them usingthe INITADD bulk entry. The INITADD entry is selected with the ID on the INITS case control. TheINITS entries selected by the INITADD entry must be all TYPE=STRESS or all TYPE=STRAIN.As a result, you cannot mix initial stress and initial strain definitions in the same input file.

• If you define data on the same grid or element corner location, a fatal error occurs.




INITSO

Defines initial strain offsets in SOL 401.

Defines initial strain offsets in SOL 401.FORMAT OF

INITIALOFFSETSTRAIN

DEFINED ONGRID POINTS(TYPE=STRAIN

ANDLOC=GRID):

1 2 3 4 5 6 7 8 9 10

INITS SID STRAIN GRID CSYS

GRID ID Exx Eyy Ezz Exy Eyz Ezx


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

FORMAT OFINITIALOFFSET

STRAIN ATELEMENT

GRIDLOCATIONS

(TYPE=STRAINAND LOC =

NOE):

1 2 3 4 5 6 7 8 9 10

INITS SID STRAIN NOE CSYS

Elem ID GRID ID Exx Eyy Ezz Exy Eyz Ezx


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

EXAMPLE:

1 2 3 4 5 6 7 8 9 10

INITS 3 STRAIN NOE 0

12 3 .0045 .0342 .00015

12 28 .00012 .0035 .00015

12 65 .00012 .0035 .00015

12 72 .00012 .0035 .00015

FIELDS:

Field Contents

SID Initial stress or strain set identification number. (Integer>0; alsosee Remark 3)




Field Contents

TYPE Offset strains can only be defined as TYPE=STRAIN. This fieldmust be defined. (Character)

LOC The location where the data is defined. There is no default valuefor this field. This field must be defined. (Character)

= GRID for data on grid points.

= NOE for data on an element at grid locations. This can includecorner and/or midside grid locations.

CSYS Selects a coordinate system to define the initial stress or strainorientation. (Integer)

= -1 Material coordinate system is used.

= 0 Basic coordinate system is used. (Default)

> 0 Selects a specific CSYS.

Exx,Eyy,Ezz,

Exy,Eyz,Ezx

Engineering offset strains representing the symmetric portion ofthe strain tensor. (Real)

When LOC=GRID:

GRID ID Grid point ID where data is applied. (Integer>0)

When LOC=NOE:

Elem ID Element where the data is applied. (Integer>0)

GRID ID Grid point ID defining a location on the element. (Integer>0)

REMARKS:1. The ID of all INITSO and INITADD entries must be unique.

2. Multiple INITSO bulk entries can be defined, each with a unique ID, then combinedwith the INITADD entry. The INITADD entry is selected with the ID on the INITSOcase control. The INITADD entry must include either all INITSO, or all INITS.

3. The option to define an initial stress or strain is available on all elements in SOL401 except for the plane strain elements including the generalized plane strainelements, solid composite elements defined with the PCOMPS entry, rigid, beam,and shell elements.

4. The INITSO case control must be defined above the subcases (globally), and isreapplied in each static subcase. If you want to include the effects of initial stressor strain including any other load in a normal modes subcase, you should includea static subcase before the sequentially dependent normal modes subcase.

5. For the plane stress and axisymmetric elements, if you select a coordinate systemother than the basic system in the CSYS field on the INITS entry, the software first




transforms the data into the basic system, then uses the components consistentwith the formats described below.

For the plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8, bothin-plane and out-of-plane initial strain values are used by the software.

For the axisymmetric elements CQUADX4, CQUADX8, CTRAX3, CTRAX6,in-plane (radial and axial) and out-of-plane (theta) initial offset strain values areused by the software.

6. Initial offset strains can be defined on a subset of the model. The softwareassumes a value of 0.0 at the locations where data is undefined. An exceptiionis when data is undefined at a mid-side grid point, and data is defined at both oreither of the related corners. In this case, the software will interpolate a value forthat mid-side grid point.




INITS

Defines initial stress or strain state in SOL 401.

Defines initial stress or strain state in SOL 401.FORMAT OF

INITIALSTRESS

DEFINED ONGRID POINTS(TYPE=STRESS

ANDLOC=GRID):

1 2 3 4 5 6 7 8 9 10

INITS SID STRESS GRID CSYS

GRID ID Sxx Syy Szz Sxy Syz Szx

GRID ID Sxx Syy Szz Sxy Syz Szx

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

FORMAT OFINITIALSTRESS

DEFINED ATELEMENT

GRIDLOCATIONS

(TYPE=STRESSAND LOC =

NOE):

1 2 3 4 5 6 7 8 9 10

INITS SID STRESS NOE CSYS

Elem ID GRID ID Sxx Syy Szz Sxy Syz Szx

Elem ID GRID ID Sxx Syy Szz Sxy Syz Szx

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

FORMAT OFINITIALSTRAIN

DEFINED ONGRID POINTS(TYPE=STRAIN

ANDLOC=GRID):

1 2 3 4 5 6 7 8 9 10

INITS SID STRAIN GRID CSYS



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




FORMAT OFINITIAL

STRAIN ATELEMENT

GRIDLOCATIONS

(TYPE=STRAINAND LOC =

NOE):

1 2 3 4 5 6 7 8 9 10

INITS SID STRAIN NOE CSYS



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

EXAMPLE:

1 2 3 4 5 6 7 8 9 10

INITS SID STRAIN NOE 0

12 3 .0045 .0342 .00015

12 28 .00012 .0035 .00015

12 65 .00012 .0035 .00015

12 72 .00012 .0035 .00015

FIELDS:

Field Contents

SID Initial stress or strain set identification number. (Integer>0; alsosee Remark 3)

TYPE Defines if the defined data is initial stress or initial strain. Thereis no default value for this field. This field must be defined.(Character)

= STRAIN for initial strain.

= STRESS for initial stress.

LOC The location where the data is defined. There is no default valuefor this field. This field must be defined. (Character)

= GRID for data on grid points.

= NOE for data on an element at grid locations. This can includecorner and/or midside grid locations.




Field Contents

CSYS Selects a coordinate system to define the initial stress or strainorientation. (Integer)

= -1 Material coordinate system is used.

= 0 Basic coordinate system is used. (Default)

> 0 Selects a specific CSYS.

Exx,Eyy,Ezz,

Exy,Eyz,Ezx

Engineering normal strains and engineering shear strains. (Real)

Sxx,Syy,Szz,

Sxy,Syz,Szx,

Engineering normal stresses and engineering shear stresses.(Real)

When LOC=GRID:

GRID ID Grid point ID where data is applied. (Integer>0)

When LOC=NOE:

Elem ID Element where the data is applied. (Integer>0)

GRID ID Grid point ID defining a location on the element. (Integer>0)

REMARKS:1. The ID of all INITS and INITADD entries must be unique.

2. The option to define an initial stress or strain is available on all elements in SOL401 except for the plane strain elements including the generalized plane strainelements, solid composite elements defined with the PCOMPS entry, and rigidelements.

3. The INITS case control must be defined above the subcases (globally), and isreapplied in each static subcase. If you want to include the effects of initial stressor strain including any other load in a normal modes subcase, you should includea static subcase before the sequentially dependent normal modes subcase.

4. For the plane stress and axisymmetric elements, if you select a coordinate systemother than the basic system in the CSYS field on the INITS entry, the software firsttransforms the data into the basic system, then uses the components consistentwith the formats described below.

For the plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8, bothin-plane and out-of-plane initial strain values are used by the software. Although,only in-plane initial stress values are used. For example, when the plane stresselements are defined on the XY plane and the basic coordinate system is usedto define the initial stress or strain, Sxx, Syy, Sxy or Exx, Eyy, Ezz, Exy shouldbe defined. For elements defined on the XZ plane, Sxx, Szz, Szx or Exx, Eyy,Ezz, Ezx should be defined.




For the axisymmetric elements CQUADX4, CQUADX8, CTRAX3, CTRAX6,in-plane (radial and axial) and out-of-plane (theta) initial stress or strain valuesare used by the software. For example, when the axisymmetric elements aredefined on the XY plane and the basic coordinate system is used to define theinitial stress or strain, Sxx, Syy, Szz, Sxy or Exx, Eyy, Ezz, Exy should be defined.For elements defined on the XZ plane, Sxx, Syy, Szz, Szx or Exx, Eyy, Ezz, Ezxshould be defined.

5. Initial stress and strain can be defined on a subset of the model. The softwareassumes a value of 0.0 at the locations where data is undefined. An exceptiionis when data is undefined at a mid-side grid point, and data is defined at both oreither of the related corners. In this case, the software will interpolate a value forthat mid-side grid point.

6. The software converts initial stress to strain using the elastic modulus.Stress/strain data and the yield point on the MATS1 bulk entry, if defined, are notused to convert stress to strain.

7. Multiple INITS bulk entries can be defined, each with a unique ID, then combinedwith the INITADD entry. The INITADD entry is selected with the ID on the INITScase control. The INITS entries selected by the INITADD entry must be allTYPE=STRESS or all TYPE=STRAIN. As a result, you cannot mix initial stressand initial strain definitions in the same input file.

8. If data is defined on the same grid or element location, a fatal error will occur.

Contact improvementsNX Nastran 12 includes the following new parameters on the BCTPARM bulk entry forsurface-to-surface and edge-to-edge contact.

• The new IPENRAMP parameter is available to request that the software ramp the removal ofinitial penetrations when INIPENE = 0 or 1. Initial penetrations can exist due to geometry or meshirregularities between source and target faces or edges. (Integer; Default=0)

= 0 (Default) No ramping is applied in the constant time subcase.

= 1 The initial penetrations are ramped in a subcase using the load factor.

• The new INTRFC parameter is available to select the interface behavior between source andtarget regions. (Integer; Default=1)

= 0 InactiveNo interaction between the source and target regions.

= 1 Standard (Default)Standard segment-segment contact algorithm with large sliding (pairing updates) and friction.

= 2 No SlidingDoes not allow sliding by assuming infinite friction. Source and target regions can separate.

= 3 Bonded/TiedNo relative displacement is permitted in both normal and tangential directions.




= 4 No SeparationNo relative displacement in normal direction. Frictionless small sliding (no pairing updates) intangential directions.

= 5 Small slidingSimplified contact algorithm with no pairing updates or friction.

• The new CTDAMP parameter is available to request the stabilization damping option when youare relying on the contact condition to prevent rigid body conditions, but the contact condition isnot active.

= 0 (Default) No stabilization damping.

= 1 Stabilization damping applied only in the first subcase and it is ramped down to zero bythe end of the subcase. The stabilization damping is only applied this way when the entirepair status is open.

= 2 Stabilization damping applied always as long as the pair status is open.

= 3 Stabilization damping applied always regardless of the time and the pair status.

• If you request stabilization damping with the CTDAMP parameter, the new CTDAMPN parameteris available to either scale the normal damping value which the software automatically computes,or to define the normal damping value explicitly. (0.0<Real<0.0; Default=1.0)

If you define a positive value for CTDAMPN, the software automatically computes the normaldamping value, then scales the automatically computed value by CTDAMPN.

If you define a negative value for CTDAMPN, the software uses the absolute value of CTDAMPNdirectly as the normal damping value.

• If you request stabilization damping with the CTDAMP parameter, the new CTDAMPT parameteris available to either scale the tangential damping value which the software automaticallycomputes, or to define the normal damping value explicitly. (0.0<Real<0.0; Default=1.0)

If you define a positive value for CTDAMPT, the software automatically computes the tangentialdamping value, then scales the automatically computed value by CTDAMPT.

If you define a negative value for CTDAMPT, the software uses the absolute value of CTDAMPTdirectly as the tangential damping value.

• The new GAPVAL parameter is available to optionally define a constant gap or penetrationbetween the source and target regions when INIPENE = 3. A negative GAPVAL means initialpenetrations which will be eliminated. (Real; Default = 0.0)

Stress output coordinate systemPreviously, SOL 401 would output stress and strain in basic coordinates for the 3D solid, plane strain,and plane stress elements.

Now, SOL 401 outputs stress and strain in the body-fixed material coordinate system. The body-fixedmaterial coordinate system is the material coordinate system relative to the deformed state.




The transformation matrix from the initial or the body-fixed material coordinate system to the basiccoordinate system is written to the new TRMBU or TRMBD datablocks, respectively, for postprocessors.

The SYSTEM(627)=0 setting is available to optionally revert the stress and strain output for the 3Dsolid, plane strain, and plane stress elements back to the basic coordinate system.

• SYSTEM(627)=0 - SOL 401 outputs stress and strain on the 3D solid, plane strain, and planestress elements in the basic coordinate system.

• SYSTEM(627)=1 (Default) - SOL 401 outputs stress and strain on the 3D solid, plane strain, andplane stress elements in the body-fixed material coordinate system.

System cell 627 specifically applies to the 3D solids elements CTETRA, CHEXA, CPENTA andCPYRAM elements, the plane strain elements CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8, and theplane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8.

The system cell 627 does not apply to the beam, shell, and cohesive elements. The followingsummarizes the stress and strain output for these elements.

• For the newly supported CBAR and CBEAM elements, the stress, strain, and element force(beam resultants) are always output in the body-fixed element coordinate system. CBAR andCBEAM elements only support isotropic materials. As a result, they do not have a materialcoordinate system.

• For the newly supported CTRIAR, CQUADR, CTRIA6, and CQUAD8 elements along with theCQUAD4 and CTRIA3 elements which are automatically converted to CQUADR and CTRIARelements, the stress, strain, and element force (shell resultants) are always output in thebody-fixed material coordinate system.

• For the cohesive elements, the relative displacements and tractions are always output in thebody-fixed material coordinate system.

Progressive failure analysisThe unidirectional fibre reinforced ply damage model (UD) became available in NX Nastran 11 todefine progressive ply failure for solid element composites in SOL 401. This model is referred to asthe UD ply failure model. The UD ply failure model is selected by entering UD in the PPFMODfield on the MATDMG entry.

The following two ply failure enhancements are now available.

1. The shear damage (d12) for the UD ply failure model now supports a nonlinear function ofthermodynamic force Y. You can specify the nonlinear function with the TABLEM5 bulk entry,which is referenced by the TID field on the MATDMG bulk entry. The TABLEM5 specifies thefunction d12=f(sqrt(Y)), where d12 is the y data, and sqrt(Y) is the x data.

2. A new enhanced unidirectional fibre reinforced ply damage model (EUD) is available. You canselect the new model by entering EUD in the PPFMOD field on the MATDMG entry. Relative tothe UD model, the EUD model allows for additional damage caused by fiber-matrix debondingand transverse cracking. The MATDMG bulk entry includes a new input format specificallyfor the EUD definition.




Additional details:

• The UD and EUD models are both supported by composite solid elements.

• The UD and EUD models only support orthotropic materials. The material ID defined for acomposite ply on the PCOMPS entry references a MAT11 and a MATDMG. You enter PFA inthe FTi field on the PCOMPS entry.

• The UD and EUD models both require that you specify PARAM,MATNL,1 to activate thedamage property. By default, PARAM,MATNL,-1, and PFA behavior is turned off.

• The UD and EUD models both support geometry nonlinear.

• You can include both the UD and EUD models on different plies on the same compositedefined with the PCOMPS entry.

• The PFRESULTS case control command includes the CRKDSTY describer to request thecrack density output. The ODAMGPFR datablock stores the crack density output.

When you include the CRKDSTY describer on the PFRESULTS command, the EUD modeloutputs the transverse crack density output. It is a scalar value reported at the mid plylocation for each ply at the element corners. The crack density is dimensionless.

• Both the UD and EUD models allow you to include coupling with plasticity. If you haveincluded the coupling with plasticity, you can define the PLSTRN case control command ina subcase to request plastic strain output at grid points. The plastic strain at the Gausspoints is not computed for composite solids.

• You can define six damage variables for the EUD method; d11, d22, d33, d12, d23, d13,which correspond to the variables df, d', d', d, d23, d in the constitutive model, respectively.You can include the DAMAGE describer on the PFRESULTS command to request thedamage output. The damage values are reported at the mid ply location (per ply at theelement corners). For both the UD and EUD models, damage values are computed relativeto the ply coordinate system and are scalar quantities.

• For both the UD and EUD models, when you include the STATUS describer on thePFRESULTS command, a damage status is computed as an element result. The integermeaning of each damage status (0, 1, 2, or 3) is documented on the PFRESULTS command.

• For both the UD and EUD models, within a single ply, if the worst damage value is greaterthan 0.0 on a Gauss point, the software considers the ply as damaged. If the worst damagevalue on all Gauss points reaches the maximum allowed damage value specified in theDMAX field on the MATDMG entry, the ply has completely failed. The DMAX default is 0.999.

• For both the UD and EUD models, the dissipated energy requested with the ENERGYdescriber on the PFRESULTS case control command represents the energy dissipated dueto damage and plasticity in the material. The output is a single scalar value per element.

• For both the UD and EUD models, stress and strain can be requested for specific elements,by ply and in the ply coordinate system. The plastic strain is only output at the middlelocation of each ply.




• The shear damage (d12) used for the UD ply failure model can be defined as a linear ornonlinear function of the thermodynamic force Y. You can specify the nonlinear function withthe TABLEM5 bulk entry, which is referenced by the TID field on the MATDMG bulk entry.The TABLEM5 specifies the function d12=f(sqrt(Y)), where d12 is the y data, and sqrt(Y) isthe x data.

Enhanced unidirectional (EUD) ply model

You can select the EUD model by entering EUD in the PPFMOD field on the MATDMG entry. Relativeto the UD model, the EUD model allows for additional damage caused by fiber-matrix debondingand transverse cracking. The MATDMG bulk entry includes an input format specifically for the EUDdefinition.

EUD model - Elastic strain and thermodynamic forces

The consititutive model for the EUD model is:

with,

and,

where,

df is the damage variable linked to fibers direction,

d, d', and d23 are the three damage variables linked to diffuse damage, with,




are the three damage variables linked to transverse cracking,

the superscript 0 is related to the undamaged material, and

[x+] is 1 when x is positive, and 0 otherwise.

EUD model - Thermodynamic forces

Thermodynamic forces are obtained by taking the derivative of the potential with respect to thedamage variables, taking the mean value over the ply thickness:

where,

is the mean value of x over the ply thickness,

is x when x is positive, and 0 otherwise,

h is the ply thickness, and

hc is a critical thickness defining the threshold between thin and thick ply behaviour.

For external plies, min(h,hc) should be replaced by min(2h,hc).

EUD model - Evolution laws of the damage variable linked to fibers

First, a "static" damage w is computed. Its evolution is a function of the thermodynamic forcesdescribed above:




where,

are the breaking thresholds in traction and compression,

Yc is a critical thermodynamic force,

k is a coupling coefficient.

If a delay effect is considered, the damage becomes,

where,

τc and ac,

dmax is the maximum fibers damage.

In option, w can be limited to dmax before taking into account the time delay effect.

EUD model - Evolution laws of damage variables linked to diffuse damageFirst, a "static" damage w is computed. Its evolution is a function of the thermodynamic forcesdescribed above,

Y0 is a fiber/matrix debonding threshold,

YC is a critical thermodynamic force,

b2 is a coupling coefficient.

If a delay effect is considered, the damages become,

where,

τc and ac are parameters of the delay law,




b3 is a coupling coefficient between the damage variables,

ds is the maximum diffuse damage.

In option, w can be limited to ds before taking into account the time delay effect.

Diffuse damages are not influenced by the damage linked to the fibers.

EUD model - Evolution laws of damage variables linked to transverse cracking

We have , where ρ is the crack density.

The rupture envelope is written,

where,

τc and ac are parameters of the delay law,

b3 is a coupling coefficient between the damage variables,

ρs is the maximum crack damage.

EUD model and plasticity

We define the effective stresses,

A yield criteria is defined as a function of the effective stresses,

where,

R(p)=Kpɣ is the yield function,

p is the cumulated plastic strain,

R0 is the initial plasticity threshold,

a is a coupling coefficient,

K and ɣ are material parameters given by experimental testing.

The plastic strain velocities are given by,




EUD model - Specifying material properties and parameters

The following table shows where you specify the various material properties and parameters used inthe EUD model.

Material proy or parameter Bulk entry (field name)Ei0, Gij0, νij0 MAT11b2 MATDMG (B2 field)b3 MATDMG (B3 field)h PCOMPS (TRi field)τc MATDMG (TAU field)ac MATDMG (ADEL field)dmax MATDMG (DMAX field)a MATDMG (A field)R0 MATDMG (LITK field)Κ MATDMG (BIGK field)Y MATDMG (EXPN field)ζ+ MATDMG (KSIT field)ζ- MATDMG (KSIC field)YdfT MATDMG (Y11LIMT field)YdfC MATDMG (Y11LIMC field)Y0 MATDMG (Y012 field)Yc MATDMG (YC12 field)K MATDMG (K field)ds MATDMG (DS field)GIC MATDMG (GIC field)GIIC MATDMG (GIIC field)GIIIC MATDMG (GIIIC field)ρs MATDMG (RO1 field)min(h,hc) MATDMG (HBAR field)ɑ MATDMG (ALPHA field)Controls if delay effect is usedbefore applying the maximumdamage.

MATDMG (USER field)




MATDMG

Material Properties for Progressive Ply Failure

Defines material properties and parameters for progressive ply failure in compositesolid elements. Used in combination with MAT11 entries that have the same MID. Validfor SOLs 401 and 402.

FORMAT:

1 2 3 4 5 6 7 8 9 10MATDMG MID PPFMOD

COEF1 COEF1 COEF1 -etc-

FORMAT FORPPFMOD="UD":

1 2 3 4 5 6 7 8 9 10MATDMG MID UD

Y012 YC12 YS12 YS22 Y11LIMT Y11LIMC KSIT KSICB2 B3 A LITK BIGK EXPN TAU ADEL

PLYUNI TID HBAR DMAX PE

FORMAT FORPPFMOD="EUD":

1 2 3 4 5 6 7 8 9 10MATDMG MID EUD

Y012 YC12 K ALPHA Y11LIMT Y11LIMC KSIT KSICB2 B3 A LITK BIGK EXPN TAU ADEL

USER R01 HBAR DMAX DS GIC GIIC GIIIC

EXAMPLE:

MATDMG 3 UD0.1 12.0 10.0 0.08 5.7 1.0E16 8.00.3 0.5 0.9 20.0 750.0 0.4 0.0001

0.43

FIELDS:

Field Contents

MID Material identification number. (Integer > 0)

PPFMOD Progressive ply failure model. Allowable entries are:

“UD” for the unidirectional ply model.

“EUD” for the enhanced unidirectional ply model.

(Character; No default)

If PPFMOD="UD"




Field Contents

Y012 Energy threshold for shear damage d12. (Real > 0; For defaultbehavior, see Remark 1)

YC12 Critical value of energy for shear damage d12. (Real > 0; Fordefault behavior, see Remark 1)

YS12 Limit value of energy for shear damage d12. (Real > 0.0; Nodefault)

YS22 Limit energy in the matrix direction. (Real > 0.0; No default)

Y11LIMT Energy threshold in tension for the fiber direction. (Real > 0.0;No default)

Y11LIMC Energy threshold in compression for the fiber direction. (Real> 0.0; No default)

KSIT Nonlinearity coefficient in tension for the fiber direction. SeeRemark 2. (Real; Default = 0.0)

KSIC Nonlinearity coefficient in compression for the fiber direction.See Remark 2. (Real; Default = 0.0)

B2 Coupling coefficient. (Real ≥ 0.0; Default = 0.0)

B3 Coupling coefficient between the damage variables. (Real >0.0; Default = 1.0)

A Coupling coefficient. (Real ≥ 0.0; Default = 0.0)

LITK Initial plastic threshold. (Real > 0.0; Default = 1.0E15)

BIGK Parameter for Plastic Law. (Real ≥ 0.0; Default = 0.0)

EXPN Exponent for Plastic Law. (Real ≥ 0.0; Default = 0.0)

TAU Time constant. See Remark 3. (Real; Default = 0.0)

ADEL Parameter for delay. See Remark 4. (Real > 0.0; Default = 1.0)

PLYUNI Control parameter for the application of nonlinearitycoefficients. (Integer = 0 or 1; Default = 0)

0: Nonlinearity coefficients are applied to stress.

1: Nonlinearity coefficients are applied to strain.

TIDTable identification number of a TABLEM5 entry. Used todefine a nonlinear damage evolution law for in-plane shear.Integer ≥ 0 or blank; for default behavior, see Remark 1)

HBAR Transition thickness of ply. (Real ≥ 0.0; Default = 0.0)




Field Contents

DMAX Maximum damage value at a Gauss point. (0.0 < Real ≤0.999; Default = 0.999)

PE 3D effect parameter. (Integer = 0 or 1; Default = 0)

0: Plane stress effect option. The effect of damage in thenormal and shear stress associated with the out-of-planedirection are ignored.

1: 3D stress effect option. The effect of damage in the normaland shear stress associated with the out-of-plane directionare included.

If PPFMOD="EUD"

Y012 Fiber/matrix debonding threshold. (Real > 0.0; No default).

YC12 Critical thermodynamic force. (Real > 0.0; No default).

K Coupling coefficient to account for the contribution ofthermodynamic force Yd to fiber damage in compression. Ydis thermodynamic force linked to shear stress σ12 and σ13.(Real >=0.0; Default=0.0).

ALPHA Parameter given by the user to define the relationship for threecrack modes in rupture envelope. (Real > 0.0; Default=1.0).

Y11LIMT Energy threshold in tension for the fiber direction. (Real >0.0; No default).

Y11LIMC Energy threshold in compression for the fiber direction. (Real> 0.0; No default).

KSIT Nonlinearity coefficient in tension for the fiber direction. SeeRemark 2. (Real; Default = 0.0).

KSIC Nonlinearity coefficient in compression for the fiber direction.See Remark 2. (Real; Default = 0.0).

B2 Coupling coefficient to account for the contribution ofthermodynamic force Yd’ to shear damage variable d. whered is the damage variable linked to shear stress σ12 and σ13.Yd’ is the thermodynamic force linked to normal stress σ22 andσ33. (Real ≥ 0.0; Default = 0.0).

B3 Coupling coefficient between damage variables d and d’; (Real≥ 0.0; Default = 0.0).

A Coupling coefficient for plasticity; (Real>=0; Default=0.0).

LITK Initial plastic threshold. (Real > 0.0; Default = 1.0E15).

BITK Parameter for Plastic Law. (Real ≥ 0.0; Default = 0.0).




Field Contents

EXPN Exponent for Plastic Law. (Real ≥ 0.0; Default = 0.0).

TAU Time constant. See Remark 3. (Real; Default = 0.0).

ADEL Parameter for delay. See Remark 4. (Real > 0.0; Default= 1.0).

USER If USER is equal to 1, static damage w is limited to themaximum damage before taking into account time delay effect.If USER is equal to 0, the “delayed” damage d after taking intoaccount time delay effect is limited to the maximum damage.(Integer 0, 1; Default = 0).

R01 Maximum transverse micro-cracking density. (Real; Default= 0.7).

HBAR A critical thickness defining the threshold between thin andthick ply behavior. (Real ≥ 0.0; Default = 0.0).

DMAX Maximum fiber damage value at a Gauss point. (0.0 < Real ≤0.999; Default = 0.999).

DS Maximum diffuse damage value at a Gauss point. (0.0 < Real≤ 0.999; Default = 0.55).

GIC Critical mode I crack energy release rates for the ply. (Real >0.0; No default).

GIIC Critical mode II crack energy release rates for the ply. (Real >0.0; No default).

GIIC Critical mode III crack energy release rates for the ply. (Real >0.0; No default).

REMARKS:1. An error message is issued if the Y012 and YC12 fields are both blank, or if the

Y012 field or the YC12 field is defined and the other is not.

2. The software uses the nonlinearity coefficients KSIT and KSIC to calculate theelastic modulus in the fiber direction as a nonlinear function of stress if PLYUNI= 0, or strain if PLYUNI = 1.

3. Use a positive value to define time delay. The software interprets negative valuesas zero time delay.

4. If TAU ≤ 0.0, there is no time delay and the ADEL field is ignored.

5. To define a nonlinear damage model for shear, you should leave the Y012 andYC12 fields blank and use the TID field to reference a TABLEM5 entry. On theTABLEM5 entry, you will include tabular data that defines how shear damage d12varies as a function of thermodynamic force Y. An error message is issued if the




Y012, YC12, and TID fields are all defined or are all blank, or if the Y012 field orthe YC12 field is defined and the other is not.

6. For the UD model, the software uses the nonlinearity coefficients KSIT and KSICto calculate the elastic modulus in the fiber direction as a nonlinear function ofstress if PLYUNI= 0, or strain if PLYUNI = 1. For the EUD model, the softwareuses the nonlinearity coefficients KSIT and KSIC to calculate the elastic modulusin the fiber direction as a nonlinear function of strain.

7. You should enter the time delay as a positive value. The software interprets anegative time delay value as zero.

8. If TAU ≤ 0.0, there is no time delay and the ADEL field is ignored.

9. The shear damage (d12) used for the UD ply failure model can be defined asa linear or nonlinear function of the thermodynamic force Y. You can specifythe nonlinear function with the TABLEM5 bulk entry, which is referenced bythe TID field on the MATDMG bulk entry. The TABLEM5 specifies the functiond12=f(sqrt(Y)), where d12 is the y data, and sqrt(Y) is the x data.

10. The coupling coefficient A determines if the normal stress in the transversedirection σ22 and the normal stress in the out-of-plane direction σ33 are takeninto consideration when plasticity occurs. For example, if A=0.0, then εp22 andεp33, and the contribution of σ22 and σ33 to the yielding surface are ignored. Theradius of the yielding surface follows the rule specified by R0+Kεɣp, where εp is theequivalent plastic strain, Ro is specified by LITK, K is specified by BIGK, and ɣis specified by EXPN.




TABLEM5

Tabular Function for Progressive Ply Failure

For progressive ply failure with the UD damage model in SOL 401, TABLEM5 isoptionally used to define a nonlinear function relating the shear damage (d12) to thethermodynamic force (Y). TABLEM5 can only be referenced by the TID field on aMATDMG entry with PPFMOD=UD defined.

FORMAT:

1 2 3 4 5 6 7 8 9 10TABLEM5 TID EXTRAP

X1 Y1 X2 Y2 X3 Y3 -etc.- "ENDT"

EXAMPLE:

TABLEM5 1

0.0 1.0 1.0 2.0 2.0 3.0 ENDT

FIELDS:

Field Contents

TID Table identification number. (Integer > 0)

EXTRAP Extrapolation option. (Integer= 0 or 1; Default=0)

• If EXTRAP = 0, extrapolate the two starting data points toobtain the table look up when x < xi, and extrapolate the twoending data points to obtain the table look up when x > xi.

• If EXTRAP = 1, use the value of the table field at the startingdata point for the table look up when x < xi, and use the valueof the table field at the ending data point for the table look upwhen x > xi.

Xi, Yi Tabular values. Xi are the thermodynamic force values. Yi are thethe shear damage values. (Real)

“ENDT” Flag indicating the end of the table.

REMARKS:1. The TABLEM5 entry can only be referenced by the TID field on the MATDMG

entry. The TABLEM5 entry defines the shear damage nonlinear functiond12=f(sqrt(Y)), where d12 is the yi data, and sqrt(Y) is the xi data. Y in the functionis the thermodynamic force.

2. The linear shear damage d12 is computed using Y012 and YC12, which you defineon the MATDMG entry. Linear and nonlinear parameters can not be specified atthe same time: An error message will be issued if the Y012, YC12, and TID fieldson the MATDMG entry are either all defined or are all blank, or if the Y012 field orthe YC12 field is defined and the other is not.




3. Xi must be in either ascending or descending order, but not both. No warningmessage is issued if tabular data is input incorrectly.

4. Discontinuities may be specified between any two points except the two startingpoints or the two end points. For example, in Figure 5-5, discontinuities areallowed only between points X2 through X7.

The value of Y at X3 in Figure 5-5 is:

y = (y3 + y4) / 2

5. At least one continuation entry must be specified.

6. Any xi, yi pair may be ignored by placing “SKIP” in either of the two fields.

7. The end of the table is indicated by the existence of “ENDT” in either of the twofields following the last entry. An error will occur if any continuations follow theentry containing the end-of-table flag “ENDT”.

8. The tabular data is interpolated for values of x that lie within the range of thetabular data and, when EXTRAP=0, the tabular data is extrapolated from the twostarting or end points for values of x that lie outside the range of the tabular data.

The value y that the software returns for the shear damage at thermodynamicforce x is:

where yT(x) is the table look up at x. The table look-up is performed using linearinterpolation within the table and linear extrapolation outside the table using thetwo starting or end points if EXTRAP = 0.

Figure 5-5. Example of Table Extrapolation and Discontinuity




User defined material improvementsIn NX Nastran 11, SOL 401 began supporting externally computed, user defined material models.You can define material models by developing and compiling an external routine.

The MUMAT bulk entry is available to define the material data in the NX Nastran input file. TheMUMAT entry in your input file is the trigger NX Nastran uses to call the external routine.

The elements referencing the MUMAT entry material ID use an associated material law defined in theexternal material routine NXUMAT.

The elements referencing the MUMAT entry must also reference MATi, and optional MATTi entries.NX Nastran uses the MATi / MATTi properties to compute an initial elastic stiffness. The initial elasticstiffness computed by NX Nastran, the data defined on the MATi, MATTI, and TABLEMi entries, andthe data defined on the MUMAT entry, are all passed from NX Nastran to the external routine.

Now in NX Nastran 12, you can optionally have your external routine update the elastic stiffnesscomputed initially by NX Nastran, and then have the external routine pass this updated stiffness backto NX Nastran to use for the initial computations.

The following two compiled example routines and NX Nastran input files are included with the NXNastran installation to demonstrate the new initial stiffness update.

MODNAME1 Input File Description

EHOOK nxumatex11.dat Hook matrix of initial stiffness for solidelements

CZEHOOK nxumatex12.dat Hook matrix of initial stiffness for cohesiveelements

See User defined materials in the Multi-Step Nonlinear User's Guide for details.



Chapter 6: Multi-step nonlinear kinematics solution 402

Multi-step nonlinear kinematics SOL 402A new NX Nastran solution sequence, SOL 402 - NLSTPKIN, is now available.

SOL 402 is a multi-step, structural solution that supports a combination of subcase types (static linear,static nonlinear, nonlinear dynamic, preload, modal, Fourier, buckling) and large rotation kinematics.

Subcase analysis typeInitial static / steady-state computationGeometric nonlinear effectsSubcase sequencingDefining solution time stepsBoundary conditionsMechanical loadsThermal inputElement supportMaterial supportGlue supportContact supportNonlinear parametersSolver supportCyclic symmetry analysisFourier analysisBuckling analysisSupported outputInput summaryResults fileInput file exampleSOL 402 vs SOL 401



Subcase analysis type

SOL 402 allows a combination of the following subcases. The ANALYSIS case control commanddefines the subcase analysis type.

STATICS (Nonlinear) static analysis.

DYNAMICS (Nonlinear) dynamic analysis, including damping and inertia effects.

MODES Normal Modes.

PRELOAD Bolt Preload subcase computation.

CYCMODES Cyclic Normal Modes.

FOURIER Fourier Normal Modes.

BUCKLING Buckling Modes (Incremental Stability)

The ANALYSIS case control command does not have a default in SOL 402.

Initial static / steady-state computation

You define an initial condition with the IC case control command which references the TIC bulk entry.You can control the computation of initial conditions using the parameter IREF on the NLCNTLG entry.

No initial static or steady-state computation are performed by default.

An initial static computation can be used to define initial displacements.

An initial steady-state computation can be used in a dynamics subcase to define initial velocities.

Geometric nonlinear effects

The parameter LGDISP turns the nonlinear large displacement capability on/off. If you define theparameter LGDISP for SOL 402, you must include it in the bulk data portion of your input file. Thesingle PARAM,LGDISP setting is global and applies to all subcases.

• PARAM,LGDISP,-1 (default) - Large displacement effects are turned off for ANALYSIS=STATIC,ANALYSIS=PRELOAD or ANALYSIS=DYNAMICS subcases.

For further ANALYSIS=MODES, ANALYSIS=CYCMODES or ANALYSIS=FOURIER subcases,second order effects are ignored, in particular the stress stiffening effect of the previous staticsubcase.

As a consequence, further ANALYSIS=BUCKLING subcases are not allowed.

Small strains are assumed and follow the Engineering strain law.

• PARAM,LGDISP,1 - Large displacement effects are turned on for ANALYSIS=STATIC,ANALYSIS=PRELOAD, or ANALYSIS=DYNAMICS subcases.

For further ANALYSIS=MODES, ANALYSIS=CYCMODES, or ANALYSIS=FOURIER subcases,second order effects are taken into account, in particular the stress stiffening effect of theprevious static subcase.

For further ANALYSIS=BUCKLING subcases, nonlinear effects are split in two terms: a deadload part and a varying part. The varying part is related to the loads variation from its lateststatic equilibrium.

Small strains are assumed and follow the Piola-Kirchoff strain law.



Multi-step nonlinear kinematics solution 402

The parameter LGSTRN turns on/off large strains, displacements, and rotations.

• PARAM,LGSTRN,0 (default) — Small strains are assumed.

• PARAM,LGSTRN,1 — Large strains, displacements, and rotations are assumed (that is, LGDISPis automatically set to 1). Large strain formulation is applicable to all elements.

In particular, nonlinear material laws will switch to a Cauchy stress and Logarithmic strain. AllTABLES1 stress/strain hardening curves should also use the same convention.

Subcase sequencing

Subcase sequencing in SOL 402 defines the initial state for a subcase. You can use the SEQDEPcase control command to define any subcase as sequentially dependent (SD), or non-sequentiallydependent (NSD). SOL 402 uses time as the variable to increment loads. Both SD and NSDsubcases in SOL 402 always use the final time from the previous subcase for their start time.

• SEQDEP=YES (default) - The subcase is an SD subcase.

An SD subcase uses the final computation state from the previous subcase for its starting state(for example, stress, strain, and displacements).

An SD subcase ignores the RSUB parameter on the new NLCNTL2 bulk entry.

• SEQDEP=NO - The subcase is an NSD subcase.

By default, an NSD subcase does not use a previous computation state for its starting state.However, an NSD subcase can optionally reload the computation state from the end of anyprevious subcase using the RSUB=n parameter on the NLCNTL2 bulk entry, where n can be-1, 0, or >0:

-1 Same behavior as SEQDEP=YES.

0 Subcase does not use a computation state from a previous subcase for itsstarting state (default for SEQDEP=NO).

>0 Restart from the end of subcase n, where n references a previous subcasenumber.

In an ANALYSIS=PRELOAD subcase, the start time must be equal to the end time. ForANALYSIS=STATIC and DYNAMICS subcases, the end time must be greater than the start time.

An ANALYSIS=PRELOAD subcase can be defined after an ANALYSIS=STATIC or DYNAMICSsubcase. The ANALYSIS=PRELOAD subcase can only contain bolt forces and/or contact definitions.

Defining solution time steps

Both the TSTEP and TSTEP1 entries are supported in SOL 402, but we recommend the TSTEP1entry. You cannot use both definitions in the same model.

When more than one subcase is specified in the case control, the TSTEP1 entry is required in allsubcases assigned by ANALYSIS = STATIC, PRELOAD, and DYNAMICS.

The TSTEP1 bulk entry defines the time step intervals at which a solution is generated and output.

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




1 2 3 4 5 6 7 8 9 10

Tend2 Ninc2 Nout2

Tend3 Ninc3 Nout3

-etc.-

Output always occurs at Tendi and every Nouti specified increment.

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

Nout Output frequencyYES Output occurs at all increments defined on TSTEP1.END Output occurs at the end time.ALL Output occurs at all increments on TSTEP1 and any software subincrements.Integer ≥ 0 Output is computed at every Nout increment specific with TSTEP1.

Automatic time stepping strategy is turned on by default and can be controlled using the NLCNTL2parameters CIBL, DTI0, HMIN, HMAX, RUP, and RDOWN.

Time stepping is not allowed for an ANALYSIS=BUCKLING subcase because SOL 402 performsstatic buckling.

Constraints

SOL 402 supports constraints defined with the SPC, SPCD, and MPC entries.


• SPCs are allowed to change between subcases, but the SPCD and MPC boundary conditionsare not allowed to change between subcases.

Unlike most other NX Nastran solutions, SOL 402 does not require any SPC (or SPC1) companioncard to fix the degrees-of-freedom that also have an imposed displacement. Any fixation wouldhave priority over the imposed displacement, which would then be ignored with a warningmessage. The absence of the companion card should be tagged in the input file using the systemcell SYS674=1, which is written automatically if you create an SOL 402 input file using Simcenter.

• However, if running with a SOL 402 input file that was originally exported with companion cards(for example, exported as SOL 401), the solver will treat the companion card correctly, providedthat SYS674=0 (or is not defined).

• If you define an SPC with a nonzero Di value, you must request an initial static computation withthe IREF parameter of the NLCNTLG entry.

• If a SPCD is defined in one subcase, in all the other subcases where it is not defined, its value isforced to zero, that is the DOFs are not free.

Mechanical loads

SOL 402 supports the following mechanical loads:

• FORCE, FORCE1, FORCE2

MOMENT, MOMENT1, MOMENT2




• GRAV

RFORCE, RFORC1

• PLOAD1, PLOAD2, PLOAD4, PLOADE1, PLOADX1

• BOLTD, BOLTFOR

• LOAD, TLOAD1

Dynamic tabular load definitions TABLED1, TABLED2, TABLED3, TABLED4 are also supported.


• For the TABLED1 dynamic load tabular function, only the linear-linear case is allowed.

• FORCE1, FORCE2, MOMENT1, MOMENT2 used in a large displacement analysis(PARAM,LGDISP,1) act as follower forces.

• For bolt loads:

o SOL 402 does not support bolt sequence (BOLTSEQ).

o You can combine several bolt preloads in the same subcase. But if you want to apply severalbolt preloads sequentially, define each bolt preload in a separate subcase.

o If the bolt load is imposed in an ANALYSIS=PRELOAD, the load will be gradually activatedduring the subcase, from 0 at the beginning of the subcase, to reach its full value at the endof the subcase (ramp-up effect).

o If the bolt load is imposed in a regular subcase (not ANALYSIS=PRELOAD), the bolt load is afunction of time; the bolt force varies linearly from its value at the beginning of the subcaseto its imposed value at the end.

• ACCEL/ACCEL1 are not supported but can be replaced by GRAV, RFORCE, or RFORCE1.

• There is no difference in the use of loads in STATICS or DYNAMICS subcases.

• Transient initial condition (TIC) are constraints, not loads.

Thermal input

A thermal load requires a load temperature (Tload), an initial temperature (Tinit), and a referencetemperature (Tref).

Thermal strain is calculated by

ε = αload(Tload – Tref) – αinit(Tinit – Tref)

where:

• Tload is the temperature load that induces a thermal strain. See the TEMP, TEMPD, or DTEMPbulk entries, and TEMP(LOAD) case control commands.

The TEMP entry defines a temperature on a grid point. The TEMPD entry defines a temperaturefor all grid points in which a TEMP entry is not defined.




The TEMP(LOAD) case control command selects either the TEMP or TEMPD bulk entries.

• Tinit is the strain free temperature used in the analysis. See the TEMP(INIT) case controlcommand.

The TEMP(INIT) case control command selects either the TEMP or TEMPD bulk entries.

• Tref is the initial temperature used when computing the temperature-dependent coefficient ofthermal expansion, and is defined on the MATi entry.

SOL 402 supports the following thermal loads: TEMP, TEMPD, DTEMP, TEMPEX, DTEMPEX


• Thermal loads can be used in both static and dynamics analyses. Thermal loads can be timedependent.

• If TEMP(INIT) is not specified, then the initial temperatures are assumed to be 0.0 for the materialparameters evaluation (see TREF on the MATi bulk entries).

• If neither TEMPERATURE(LOAD) nor TEMPERATURE(INITIAL) is defined, MATTi temperaturedependent material properties are ignored.

• If TEMP(INIT) is defined but neither TEMPERATURE(LOAD) nor a time-dependenttemperature load using DLOAD entry is defined, TEMPERATURE(LOAD) defaults toTEMPERATURE(INITIAL). As a result, thermal strain is zero.

• If TEMP(INIT) is not specified but TEMP(LOAD) is, a fatal error is issued.

• In dynamic analyses, you can also load thermal-solved temperatures through the TEMPEXor DTEMPEX bulk entries.

Element support

SOL 402 supports the following elements:

• 0D elements: CELAS1, CELAS2, CMASS1, CMASS2, CDAMP1, CDAMP2

• 1D (line) elements: CBAR, CBEAM, CROD, CONROD

• 2D elements

o Shell elements: CQUAD4, CQUAD8,CTRIA3, CTRIA6

o Plate elements: CQUADR, CTRIAR

o 2D Plane Strain elements: CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8

o 2D Plane Stress elements: CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8

• 3D elements

o CHEXA, CPYRAM, CTETRA, CPENTA

o 3D Axisymmetric elements: CTRAX3, CTRAX6, CTRIAX, CQUADX4, CQUADX8, CQUADX




o 3D Cohesive elements: CHEXCZ, CPENTCZ

o 3D Rigid elements: RBAR, RBE2, RBE3

• Special element types: CBUSH, CONM1, CONM2, CBUSH1D, CGAP


• CQUAD element is not supported in SOL 402. Instead, use CPLSTN*.

• CQUAD4 element is supported only if system cell 370 is turned on. Otherwise, a fatal error isissued. Use CQUADR instead, or turn on the system cell.

• CQUAD4 and CQUADR elements follow the Mindlin first order formulation, and CQUAD8elements follow the heterosis second order integration formulation.

• SOL 402 does not support chocking elements.

• For CTRIA3, CQUAD4, CTRIAR, or CQUADR elements, you can set the PARAM,SNORMparameter to automatically generate grid point normals (based on the average normal betweenadjacent elements) to solve discontinuities of normals orientations in adjacent shells.

• Results are output in the material coordinate system. If these axes are not specified, outputwill be:

o In the element coordinate systems for solid elements, which is the basic coordinate systemunless another one is specified on the property card using CORDM of the PSOLID bulk entry.

o In the element coordinate systems for shell elements, which is parallel to the first edge G1-G2.

Material support

SOL 402 supports the following materials (with optional temperature dependencies):

• Isotropic: MAT1 (+MATT1)

• Orthotropic: MAT11 (+ MATT11), MAT3 (+MATT3), MAT8 (+ MATT8)

• Anisotropic: MAT2 (+ MATT2), MAT9 (+ MATT9)

• Hyperelastic: MATHE, MATHM, MATHEV, MATHP

• Creep: MATCRP and CREEP (+ MATTC)

• Ply failure: MATDMG

• Material for cohesive elements: MATCZ


• MATS1 bulk entry can be used to specify stresses dependence to MAT1, MAT3, MAT9, orMAT11. However, the Yield function is limited to the von Mises law.

• In MATHP, the order of the distortional strain energy polynomial function is limited to 4.




• The choice of the stress-strain measure for all material laws is defined in the NLCNTLG entry.

• If the MATNL parameter is set to -1 (PARAM,MATNL, -1):

o Plasticity effects of MATS1 materials are turned off. This can also be enabled on asubcase-by-subcase basis using NLTNCL2 PLASTIC.

o Creep effects of the MATCRP materials are turned off. This can also be enabled on asubcase-by-subcase basis using NLTNCL2 CREEP.

o Damage material properties for cohesive elements of the MATCZ materials are discarded.

Glue support• SOL 402 supports only the BGOPT parameter of the BGPARM bulk entry.

• Depending on the source and target region defined in the BGSET bulk entry and the BGOPTparameter of the BGPARM entry, you can set up the following gluing types:

BGSET: source/target BGPARM: BGOPTparameter Gluing characteristics

BEDGE/BEDGE Edge to edge gluing for shells, plane strain,or plane stress elements.

BSURFS/BEDGE Faces of solid to edges of shells gluing.BSURFS/BSURFS Solids to solids gluing.BSURFS/BSURF Nodes of solids to shells faces gluing.

BEDGE/BSURFSNodes of shells to faces of solids gluing.

The source node rotation is computed as themean rotation of the target solid face.Nodes of shells to shells gluing

3 (default) The source node rotation is computed as themean rotation of the target shell.BEDGE/BSURF

2 Three additional kinematics constraints areused to drive the source node rotation.Shells to shells gluing

3 (default) The source node rotation is computed as themean rotation of the target shell.

2 Three additional kinematics constraints areused to drive the source node rotation.

BSURF/BSURF

1 Rotations are free.Shells to faces of solids gluing.

3 (default) Three additional kinematics constraints areused to drive the source node rotation.BSURF/BSURFS

1 Rotations are free.BSURF/BEDGE N/A

Contact supportIn SOL 402, you can define a node-to-surface contact, with or without friction. In the BCTSET bulkentry, you define the contact pairs, while you use the BCTPAR2 entry to define the contact parameters.

Additional information on the BCTPAR2 entry:




• In a subcase where contact is defined, the contact condition is gradually activated during thesubcase such that it is fully activated by the end of the subcase (ramp-up effect).

• The ramp-up of contact conditions occurs for all subcases except for the first one. By default inthe first subcase, contact conditions are immediately active at the beginning of the simulation(time = 0.). However, you can optionally define ACTIVE=0 on the BCTPAR2 bulk entry to requestthe ramp-up of contact conditions in the first subcase.

• Similarly, in a subcase in which contact is not defined, but was defined in the previous subcase,the contact conditions will be gradually disabled (ramp-down effect).

• SOL 402 does not support birth/death time for contacts. The activation/deactivation is onlypossible at the subcase level.

• You can request the large displacement contact formulation by setting DISP=2 on the BCTPAR2bulk entry to force the contact conditions to be updated when large sliding occurs. The DISP=2formulation is also automatically activated when you request large displacement effects with thesetting PARAM,LGDISP,1, or when you request large strains and displacement effects with thesetting PARAM,LGSTRN,1.

• The SEGNORM parameter on the BCTPAR2 bulk entry can be defined to request continuouscontact segment normals when the normals of two adjacent faces in contact present severediscontinuities.

Nonlinear parameters

You can define solution control parameters either globally (NLCNTLG bulk entry) or by subcase(NLCNTL2 bulk entry).

On the NLCNTLG bulk entry, you can choose the following:

• The stress-strain measure for all material laws (Kirchoff, Cauchy, Biot, and so on) usingSTRMEAS.

• Symmetric or unsymmetric matrices for subcases ANALYSIS=STATIC, PRELOAD or DYNAMICS.

• The solver (RESO). See Solver Support.

On the NLCNTL2 bulk entry:

• You can choose between fixed time steps or automatic time stepping. You can also control thetime step size (minimum, maximum, increase ratio).

• You can control the equilibrium iteration and convergence of the solution.

• You can use the IMPL parameter to define the time integration scheme (Newmark, HHT, orGeneralized-alpha) for DYNAMICS subcases. You can also control the integration error.

• You can use the LVAR and TVAR parameters to define if time unassigned loads and temperaturesare ramped (default) or stepped.

• For a non-sequentially dependent (NSD) static subcase (SEQDEP=NO), you can optionallyreload the computation state from the end of a previous subcase using the RSUB=n parameter.




Solver support

SOL 402 supports the sparse direct solver (default) or the parallel solver. The element iterativesolver is not supported.

• On the NLCNTLG bulk entry, you can choose the Skyline, Sparse, or parallel solver using theRESO parameter.

• For the parallel solver, SOL 402 supports distributed-memory parallel processing (DMP) andshared-memory parallel processing (SMP).

• The Nastran command MPI402 keyword specifies the maximum number of CPUs selected fordistributed-memory parallel processing. The NASTRAN command PARALLEL sets the numberof MKL threads.

Cyclic symmetry analysis

See Cyclic symmetric in SOL 402.

Fourier analysis

See Fourier harmonic solution in SOL 402.

Buckling analysis

See Linearized buckling solution in SOL 402.

Supported case control output requests

SOL 402 supports only SORT1 data. SORT2 is not supported.

Case control DescriptionACCELERATION Requests accelerations.BCRESULTS Requests contact forces and tractions.BGRESULTSBOLTRESULTS Requests bolt results.CRSTRN Requests creep strain at grid points.CZRESULT Requests results output for cohesive elements.DISPLACEMENT Requests displacement output.EKE Requests element kinetic energy output.ELSUM Requests output of an element property summary.ESE Requests the output of the strain energy.FORCE Requests element force output.GPFORCE Requests grid point force balance at selected grid points.HOUPUT Requests harmonic output for cyclic symmetry and axisymmetric models.MEFFMASS Requests modal effective mass output in a modal subcase.MONVAR Selects degree-of-freedom for a displacement monitor plot.MPCFORCES Requests the form and type of multipoint force of constraint vector output.OLOAD Requests the form and type of applied load vector output.OMODES Requests a set of modes for output.OTEMP Requests temperature output.PFRESULTS Requests progressive failure results output for composite solid elements.




PLSTRN Requests plastic strain at grid points.SET Defines a set of element or grid point numbers to be plotted.SETMC Set definitions for modal, panel, and grid contribution results.SETMCNAME Specifies the title of a displacement monitor plot.SHELLTHK Requests shell thickness output.SPCFORCES Requests single-point force of constraint vector output.STRAIN Requests element strain output.STRESS Requests element stress output.THSTRN Requests thermal strain at grid points on elements.VELOCITY Requests the form and type of velocity vector output.

Input summary

You can use the following parameters with SOL 402.

ALPHA1 LGDISP POSTALPHA2 LGSTRN SNORMF56 MATNL UNITSYSK6ROT NLAYERS

You can use the following case control commands with SOL 402.

ACCELERATION DLOAD METHOD SPCANALYSIS DTEMP MONVAR SPCFORCESBCRESULTS EKE MPC STRAINBCSET ELSUM MPCFORCES STRESSBGRESULTS ESE NLCNTL SUBCASEBGSET FORCE OLOAD SUBTITLEBOLTLD GPFORCE OTEMP TEMPERATUREBOLTRESULTS HARMONICS PFRESULTS THSTRNCRSTRN HOUTPUT PLSTRN TITLECYCFORCES IC SEQDEP TSTEPCYCSET LABEL SET VELOCITYCZRESULTS LOAD SETMCDISPLACEMENT MEFFMASS SHELLTHK

You can use the following bulk entries with SOL 402.

BCPROP CPLSTN6 MAT3 PLOAD1BCPROPS CPLSTN8 MAT8 PLOAD2BCRPARA CPLSTS3 MAT9 PLOAD4BCTADD CPLSTS4 MAT11 PLOADE1BCTPAR2 CPLSTS6 MATCID PLOADX1BCTSET CPLSTS8 MATCRP PLPLANEBEDGE CPYRAM MATCZ PLSOLID




BGADD CQUAD MATDMG PMASSBGPARM CQUAD4 MATFT PPLANEBGSET CQUAD8 MATHE PRODBOLFRC CQUADR MATHEM PSHELLBOLT CQUADX4 MATHEV PSHL3DBOLTFOR CQUADX8 MATS1 PSOLCZBOLTLD CREEP MATT2 PSOLIDBSURF CROD MATT3 RBARBSURFS CTETRA MATT8 RBE2CBAR CTRAX3 MATT9 RBE3CBEAM CTRAX6 MATT11 RFORCECBUSH CTRIA3 MATTC RFORCE1CBUSH1D CTRIA6 MOMENT SPCCDAMP1 CTRIAR MOMENT1 SPC1CDAMP2 CYCADD MOMENT2 SPCADDCELAS1 CYCAXIS MPC SPCDCELAS2 CYCSET MPCADD TABLED1CGAP DLOAD NLCNTG TABLED2CHEXA DTEMP NLCNTL2 TABLED3CHEXZ ECHOOFF PBAR TABLED4CMASS1 ECHOON PBARL TABLEM1CMASS2 EIGB PBEAM TABLEM2CONM1 EIGR PBEAML TABLEM3CONM2 EIGRL PBUSH TABLEM4CONROD ENDDATA PBUSH1D TABLEM5CORD1C FORCE PBUSHT TABLES1CORD1R FORCE1 PCOMP TABLESTCORD1S FORCE2 PCOMPG TEMPCORD2C GRAV PCOMPG1 TEMPDCORD2R GRID PCOMPS TICCORD2S GROUP PDAMP TLOAD1CPENTA INCLUDE PELAS TSTEPCPENTCZ LOAD PELAST TSTEP1CPLSTN3 MAT1 PGAPCPLSTN4 MAT2 PLOAD

You can use the following NASTRAN system cells in SOL 402:

57107143144370




442525674

The following NASTRAN command keyword is specific to SOL 402:

MPI402

Results file

See SOL 402 .f06 results file.

Input file example

NASTRAN SYSTEM(674) = 1assign output2='samcefnl.op2', unit=21SOL 402,106CEND$*$* +--------------+$* ! CASE CONTROL !$* +--------------+$*ECHO = NONEDISPLACEMENT(PLOT,PRINT) = ALLSPC = 100$* Subcase 1 : transient analysisSUBCASE 1ANALYSIS = TRANSIENTLABEL = Transient step 1TSTEP = 201IC = 301SUBCASE 2ANALYSIS = TRANSIENTLABEL = Transient step 2TSTEP = 202IC = 302SEQDEP = NO$*$* +-----------+$* ! BULK DATA !$* +-----------+$*BEGIN BULK$*$* PARAM CARDS$* ===========$*PARAM OMACHPR YESPARAM POST -2$*$* GRID CARDS$* ==========$--01--><--02--><--03--><--04--><--05--><--06--><--07--><--08--><--09--><--10-->GRID 1 0 0.0 0.0 0.0 0




GRID 2 0 100.0 0.0 0.0 0$*$* ELEMENT CARDS$* =============$--01--><--02--><--03--><--04--><--05--><--06--><--07--><--08--><--09--><--10-->CDAMP1 2 2 1 1 2 1CONM1 1 2 0 1.00E-3CELAS1 3 3 1 1 2 1$*$* PROPERTY CARDS$* ==============$--01--><--02--><--03--><--04--><--05--><--06--><--07--><--08--><--09--><--10-->PDAMP 2 5.03E-4PELAS 3 1.58E-3$*$* LOAD AND CONSTRAINT CARDS$* =========================$--01--><--02--><--03--><--04--><--05--><--06--><--07--><--08--><--09--><--10-->SPC 100 1 123456 0.0000SPC 100 2 23456 0.0000$*$* TSTEP CARDS$* ===========$--01--><--02--><--03--><--04--><--05--><--06--><--07--><--08--><--09--><--10-->TSTEP1 201 10.0 10000 100TSTEP1 202 20.0 10000 100$*$* INITIAL CONDITIONS$* ==================$--01--><--02--><--03--><--04--><--05--><--06--><--07--><--08--><--09--><--10-->TIC 301 2 1 2.0 2.5TIC 302 2 1 1.0 1.5$*ENDDATA

SOL 402 vs SOL 401 comparison

See SOL 402 vs SOL 401 comparison.

Fourier harmonic solution in SOL 402A Fourier normal modes subcase is available in SOL 402 for models that include axisymmetricelements. The subcase is designated with the ANALYSIS=FOURIER and HARMONICS=N casecontrol commands in the subcase.

The conventional axisymmetric element includes radial and axial degrees-of-freedom with novariation in theta.

In the Fourier normal modes subcase, the axisymmetric element has radial, axial, and thetadegrees-of-freedom. In addition, the degrees-of-freedom are represented with harmonic terms of aFourier series of the form:




where:

c=cos(kθ) and s=sin(kθ),

k is the harmonic number,

are symmetric displacements, and

are antisymmetric displacements.

Both symmetric and antisymmetric displacements are computed by NX Nastran for a particularharmonic k.

With the Fourier normal modes subcase, you request which harmonic numbers in a modalsolution should occur, and the harmonic terms for modal output. For each harmonic number inwhich you request modes and output, the software can compute the symmetric and antisymmetricdisplacements, stress, strain, SPC force, and grid point forces. You can use the typical case controlcommands to request the output. You can then optionally use the Simcenter post processor to displaythe physical results on either a 3D segment, or on a full 360-degree model display.

Static and modal (non-Fourier normal modes) subcases can also be included in the input, and aredesignated with the case control commands ANALYSIS=STATICS or ANALYSIS=MODES. However,the conventional axisymmetric element formulation is used in the static and modal subcases.

In addition to axisymmetric elements, the plane stress elements can also be included with the Fouriernormal modes subcase.

For grid points that are defined on the rotation axis, in addition to any conditions that you defined, NXNastran automatically applies the following SPC and MPC conditions during the solution.

• For the harmonic index k=0, NX Nastran fixes DOF 1, 2.

• For the harmonic index k=1, NX Nastran fixes DOF 3, and it creates the MPC condition Ux = Uyfor the cosine terms, and the MPC condition Ux = -Uy for the sine terms.

All harmonic terms are treated all together in a unique system of equations. As a consequence:

• For modal analysis, eigenvalues are sorted in increasing order independently of harmonic.Depending on the physical configuration, each eigenmode is associated with one harmonic.Modes are not sorted in increasing harmonic number.




• For static analysis, even if loading is axi-symmetrical (harmonic 0), one higher harmonic can beexcited. For instance, a cylinder axially loaded (harmonic 0) can buckle laterally (harmonic 1)or a cylindrical tank subjected to an external pressure (harmonic 0) can buckle in a doublewave shape (harmonic 2).

Fourier normal modes subcase input summary

• The ANALYSIS=FOURIER case control command should be defined in the subcase in which youare requesting the Fourier normal modes subcase in SOL 402.

• The HARMONICS case control command requests the specific harmonics in which modes willbe computed. The SET entry then lists the harmonic numbers to be computed, including "0" torequest the zeroth harmonic. Since there is an infinite number of harmonics in the Fourier normalmodes analysis, the describer "ALL" is not supported in the ANALYSIS= FOURIER subcase.

• The HOUTPUT case control command optionally requests the harmonics to output modes. "ALL"requests output for every harmonic requested on the HARMONICS command. An integer can bedefined to select the SID of a SET bulk entry listing the harmonic numbers to be output. TheseIDs typically represent a subset of the IDs requested on the HARMONICS command. The C, S,C*, and S* describers on the HOUTPUT command are not supported by SOL 402.

• The METHOD case control command selects the EIGRL bulk entry, which then defines theeigenvalue solution options, for example, the lower- and upper-frequency ranges and the numberof modes.

Cyclic symmetric in SOL 402The cyclic solution method takes advantage of cyclic symmetry to reduce the time needed to createand solve a full 360-degree model. To use this method, you create a 3D-solid element model thatrepresents a fundamental segment. The fundamental segment represents a structure that is made upof N repetitions, where each repetition can be obtained by rotating the fundamental segment an anglethat is an integer multiple of 2π/N.

Cyclic symmetry solution in SOL 402 follows the same capabilities as the cyclic symmetry in SOL401 (see ) except for the following limitations.

HARMONICS limitations

In SOL 402, the following limitations apply to the HARMONICS case control command that requeststhe solution harmonics:

• HARMONICS=ALL is not allowed.

• HARMONICS=n defines a SET number that contains only one unique harmonic to solve. Ifyou want to solve several harmonics, you must define one ANALYSIS=CYCMODES subcaseper harmonic to solve.

Miscellaneous limitations

You cannot use the parameters STRESSK, SPINK, and FOLLOWK of the NLCNTL bulk entryto request stress stiffening, spin softening, and follower stiffness because the NLCNTL entry isnot supported in SOL 402.




Cyclic modes subcase input summary

• The ANALYSIS=CYCMODES case control command is defined in the specific subcases in whichyou are requesting the cyclic modes solution method.

• The HARMONICS case control command requests the specific harmonic in which modes arecomputed. You cannot use the "ALL" request. You must define the SID of a SET bulk entry, andthe SET entry lists the unique harmonic number to be computed. If you want to solve severalharmonics, you must define one ANALYSIS=CYCMODES subcase per harmonic to solve.

• The HOUTPUT case control command optionally requests the harmonics to output modes. "ALL"requests output for the unique harmonic requested on the HARMONICS command. The C, S, C*,and S* describers on the HOUTPUT command are not supported by SOL 402.

• The METHOD case control command selects the EIGRL bulk entry which then defines theeigenvalue solution options, for example, the lower- and upper-frequency ranges and the numberof modes. Since a single EIGRL entry is selected in a subcase, the same EIGRL options areused when the software computes the modes for each harmonic.

SOL 402 vs SOL 401 comparisonContact

1. In SOL 401, the OFFSET distance can be defined per contact region (BCRPARA bulk entry).

In SOL 402, the OFFSET distance is defined at the contact level (BCTPAR2 entry).

2. In SOL 401, a contact with shells automatically take the half thicknesses of the shells into account.

In SOL 402, you must manually take the half thicknesses of the shells into account with theOFFSET parameter.

Bolt

1. In SOL 401, you cannot model bolts with CBAR/CBEAM elements.

In SOL 402, you can model bolts with beams.

2. In SOL 401, you cannot use CPYRAM and composite solids for a BOLT of the ETYPE=3 type.

In SOL 402, you can if the cut is planar.

3. Initial strain bolt preload force is allowed in SOL 401, not in SOL 402.

4. Bolt loading sequence (BOLTSEQ) is allowed in SOL 401, not in SOL 402. In SOL 402, bolts areactivated for the whole subcase time interval.

Subcases

1. In SOL 401, a NSD subcase (SEQDEP = NO) has a start time of zero. In addition, anon-sequentially dependent static or modal subcase does not use the displacement/stress/strainstate from the previous static subcase.




In SOL 402, a NSD subcase uses the final time from the previous subcase for its start time. Butthe computation state (stresses, state variables, and so on) can be reloaded from the end of anyof the previous subcases through the RSUB parameter of the NLCNTL2 bulk entry.

Miscellaneous

1. In SOL 401, you can apply an enforced motion (parameter Di of the SPC bulk entry) in anysubcase.

In SOL 402, enforced motion is always global and you must request an initial static computationwith the IREF parameter of the NLCNTLG entry.

2. In SOL 401, SPCD can vary from a subcase to another.

In SOL 402, SPCD must be global and cannot vary from one subcase to another because if anSPCD is defined in one subcase, in all the other subcases where it has not been defined, itsvalue is forced to zero instead of being free.

3. TSTEP bulk entry is compulsory for a transient analysis in SOL 401, but not in SOL 402

4. Strategy parameters must be defined in the NLCNTL bulk entry for SOL 401, but in the NLCNTL2bulk entry for SOL 402.

SOL 402 .f06 results fileThe output file that you will use most frequently is the .f06 file. The software writes this file toFORTRAN unit 6. The .f06 file contains all the requested results from your analysis, such as thedisplacements, stresses, and element forces, as well as any diagnostic messages. The information inthe .f06 file is critical for model checkout and debugging.

Structure of the file in SOL 402

The .f06 file contains the results of the NX Nastran job and also includes the output file of the SamcefMECANO run (also called the MECANO RES file).

The MECANO output file is included in the .f06 Nastran file between the starting lines:

DYNAMIC ALLOCATION OF MEMORY============================USER REQUESTED WORKSPACE 12000000 WORDS ( 96 MBYTES)Module: M E C A N O

and the finishing lines:

-------------------------------------------------------------------------------File size statisticsFile name Size-------------------------------------------------------------------------------./T40959_9/sim1-sol_402_me.w01 16560 Bytes./T40959_9/sim1-sol_402_me.w02 12488 Bytes./T40959_9/sim1-sol_402_me.w03 147520 Bytes




The following sections describe the most important contents of the .f06 file that you need to searchfor results or to diagnose problems.

Searching for errors, warnings, or information messages

Important MECANO messages have the following headers:

• %%%Enn-xxx <text> for error messages.

• %%%Ann-xxx <text> for warnings.

• %%%Inn-xxx <text> for informative messages.

where:

• nn is the message id.

• xxx is the message keyword; typically, the Samcef FORTRAN routine issues the message.

• <text> is the message short description.

Several lines of text may follow the message to complete the message description.

The following table lists the most important error message keywords.

%%%Enn-xxx DescriptionMMFERR All errors related to the BOEING solver: pivoting, memory zone, and so on.

ASGEN All errors related to element generation: missing or inconsistent physicalproperties, and so on.

OVVExx All errors related to materials definitions: missing property, datainconsistency, and so on.

DGOPPA All errors related to .sdb database access: memory zone, opening andsaving the file, and so on.

WRITES All errors related to the writing of data in files: disk space, permissions,and so on.

CONTAC All errors related to contact conditions: convergence, and so on.

Checking convergence

You can check the solution convergence by searching for the TIME STEP entries:

TIME STEP NR 1 (TIME 5.000000000E-02) #

Is the entry for all indicators regarding a specific time step value.

->ACCEPTED TIME STEP, ERROR = 6.667E-01 H RATIO= 1.000E+00 H = 5.000E-02

Indicates the converged state of the time step and the related convergence values.

->REJECTED TIME STEP, ERROR = 6.667E-01 H RATIO= 1.000E+00 H = 5.000E-02

Indicates the non-converged (and rejected) state of the time step and the related convergencevalues.




For each time step, a list of indicators is given for each Newton iteration. In the listing, you findthis information in a printout table like:

NEWTON ITERATIONS :-------------------ITER. TESF TESE TESQ RES ALGO CPU#1 6.2322E-01 1.0000E+00 1.0000E+00 3.1767E+03 NR 1.05#2 3.3973E-02 1.4139E+00 5.2422E+00 2.5920E+03 NR 1.05#

where ITER is the iteration number and where the most important parameters to watch are:

TESFThe force convergence test value. This is the norm of the residual vector to the sum of internal,external, and inertia forces incremented by a reference value given by the REFP parameterof the NLCNTL2 bulk entry.

TESEThe energy convergence test value. This is the square root of the ratio of the product of theresidue by the variation of the displacement during one iteration to the sum of kinetic, internal,and external energies incremented by a reference value given by the REFE parameter of theNLCNTL2 bulk entry.

TESQThe norm of the displacement increment divided by the sum position vector incremented by areference value given by the REFU parameter of the NLCNTL2 bulk entry.

All these parameters have to decrease during the iterations of a time step. Convergence is reachedwhen the test value lies under a convergence threshold:

• For TESF, the threshold is given by the PRCR parameter of the NLCNTL2 bulk entry.

• For TESE, the threshold is given by the PRCE parameter of the NLCNTL2 bulk entry.

• For TESQ, the threshold is given by the PRCQ parameter of the NLCNTL2 bulk entry.

For more details on convergence problems, see Listing of results and messages in the Non linearmechanics - Analysis manual of the Samcef documentation.

Browsing contact conditions

In the listing file, you can browse the contact conditions by searching for the MCT keyword. The MCT

number in the listing matches the CSID parameter of the BCTSET bulk entry.

In the case of non-convergence, a global status of the contact conditions is printed in the .f06 file. Formore information on this status and how to understand the printed data, see Convergence problemsand Summary of contact status in case of divergence in the Samcef documentation.

Linearized buckling solution in SOL 402The BUCKLING analysis in SOL 402 performs an incremental stability, which is also called initialbifurcation analysis or linearized buckling analysis.



custom/en_US/samcef_solver_documentation/m011/anal-m011.html

custom/en_US/samcef_solver_documentation/m011/anal-m011.html

custom/en_US/samcef_solver_documentation/m001/cont-guid-m001.html#conv

custom/en_US/samcef_solver_documentation/m001/stat-guid-m001.html


A model can buckle in different shapes under different levels of loading. The shape the model takeswhile buckling is called the buckling mode shape, and the loading is called the critical or buckling load.

The linearized buckling approach solves an eigenvalue problem around a reference state andestimates the critical buckling factors and the associated buckling mode shapes.

Usually, you are interested in the lowest mode because it is associated with the lowest critical load.

The buckling load factor (BLF) is the ratio of the buckling loads to the applied loads.

Buckling load factor (BLF) Buckling status

1 < BLF The applied loads are less than the estimatedcritical loads. Buckling is not expected.

0 < BLF < 1 The applied loads exceed the estimated criticalloads. Buckling is expected.

BLF = 1 The applied loads are exactly equal to theestimated critical loads. Buckling is expected.

BLF = -1

The buckling occurs when the directions of theapplied loads are all reversed. For example, ifa rod is under tensile load, the BLF should benegative. The rod will never buckle.

-1 < BLF < 0 Buckling is predicted if you reverse all loads.

BLF < -1 Buckling is not expected even if you reverseall loads.

Note

A structure can have both positive and negative buckling load factors. For example, for acylindrical pipe under internal pressure supported by columns, the vessel will never buckleas it is under tension; however, the columns may buckle as they are under compression.

Workflow

1. After at least one STATICS subcase, SUBCASE n, you define a BUCKLING subcase n+1.

For instance:

SUBCASE 3ANALYSIS = STATICSLABEL = Loading up to 100. [1-100]TSTEP = 102$SUBCASE 4ANALYSIS = BUCKLINGLABEL = Buckling analysis at 100 loadMETHOD = 40SEQDEP = YESEKE(PRINT,THRESH=0.3) = ALL

2. The BUCKLING subcase will use the final computation state of the previous SUBCASE n as thereference state and computes a new state at tn + 1 second, where tn is the latest computationtime of the SUBCASE n.




3. The loads in the model that do not vary in between the time interval [tn, tn + 1 sec] are consideredas dead loads: they are applied on the structure but are not involved in the buckling process.

The loads in the model that vary in between the time interval [tn, tn + 1 sec] are considered as lifeloads: these are the loads that are involved in the buckling process.

Note

It is then important that the definition time range of the loads covers the interval [tn, tn+ 1 sec].

Note

You can repeat the sequence "STATICS subcase then BUCKLING subcase" several times.

Example

Note

The following examples show the most important entries that are relevant to theBUCKLING workflow.

Case Control.

NASTRAN SYSTEM(674)=1$ASSIGN OUTPUT2='samcefnl.op2',UNIT=21$SOL 402CEND$*$*$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$*$* CASE CONTROL$*$*$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$*TITLE = Buckling analyses of a compressed plateSUBTITLE = Several load levelsECHO = UNSORTSPC = 1DLOAD = 2METHOD = 10DISPLACEMENT(PRINT) = ALLSTRESS(PRINT) = ALL$SUBCASE 1ANALYSIS = STATICSLABEL = First Loading [0-1]TSTEP = 101$




SUBCASE 2ANALYSIS = BUCKLINGLABEL = Buckling analysis with unitary loadMETHOD = 20SEQDEP = YESEKE(PRINT,THRESH=0.3) = ALL$SUBCASE 3ANALYSIS = STATICSLABEL = Loading up to 100. [1-100]TSTEP = 102$SUBCASE 4ANALYSIS = BUCKLINGLABEL = Buckling analysis at 100 loadMETHOD = 40SEQDEP = YESEKE(PRINT,THRESH=0.3) = ALL$SUBCASE 5ANALYSIS = STATICSLABEL = Loading up to 250. [100-250]TSTEP = 103

Time steps definition

TSTEP1 101 0.01 1 ENDTSTEP1 102 1.0 1 ENDTSTEP1 103 2.5 1 END

Loads

$$ Loading$$------1-------2-------3-------4-------5-------6-------7-------8-------9------10DLOAD 2 1. 1. 3TLOAD1 3 33 0 load 4TABLED2 4 0.+ 0. 0. 0.01 0. 10. 10. ENDT

In this example, the first buckling uses the loads time definition "buckling" interval of [0.01, 1.01], andthe second buckling uses the interval of [1.0, 2.0].

The loads are well defined in these intervals.

Output in the .f06 results file

THERE ARE 8 EIGENVALUES BETWEEN 0.000E+00 AND 5.000E+02RESULTS AT ITERATION 10, NUMBER OF VECTORS : 30EIGENVALUE BUCKLING FACTOR

1 -4.072133E-03 4.428440E+002 -4.770635E-03 4.038430E+01




3 -7.414269E-03 1.151249E+02



Chapter 7: Performance

Performance improvements

Direct frequency response performance

The following new performance options are available for the direct frequency response solution(SOL 108).

• Iterative solver for frequency-dependent solution

NX Nastran’s global iterative solver now supports frequency-dependent solutions. To activatethe global iterative solver in SOL 108, set either NASTRAN ITER = YES in the Nastran input file oradd iter = yes to the Nastran command line.

• Padé via Lanczos (PvL)

For models that have frequency-dependent matrices, you can request the new Padé via Lanczos(PvL) approach. The PvL approach utilizes factorization of the matrix at selected frequencies forall responses and depending on the number of frequencies computed, reduces the problem size.

To request the PvL approach, set either the new keyword krylov or the new system cell 679(krylov) to YES.

NASTRAN KRYLOV = YES

Note

• The iterative solver support for frequency-dependent solutions and the Padé viaLanczos (PvL) approach are mutually exclusive.

• If you request both PvL and global iterative solver solution, the PvL approach will takeprecedence over the frequency-dependent iterative solver approach.

Geometric Domain Static Analysis (GDSTAT) extension

GDSTAT is a parallel solution for the linear static analysis of large models.

The GDSTAT method is added to SOL 401 for fast static analysis. The performance of GDSTATdepends on the size of the boundary produced by the graph-based (GPART = 1) domain partition.When the boundary size is small, GDSTAT is most efficient. For most cases, DMP = 2 or DMP= 4 is sufficient.

You can use system cell 649 to control GDSTAT in SOL 401.

= 0 (default) Does not select GDSTAT. That is, NX Nastran performs serial processing.

= 1 Selects GDSTAT with null columns in the stiffness matrix.



= 2 Selects GDSTAT after null columns are removed from the stiffness matrix.

Use SYSTEM(649) = 1 for most parallel processing cases. However, for models with large opencontact patches, which generally include a large number of null columns, you may see a performanceincrease with SYSTEM(649) = 2.

For more information about parallel solutions, see the Parallel Processing User's Guide.

Improved sparse decomposition

The default value for the rank keyword (system cell 205) is changed from 32 to 128 for better SharedMemory Parallel (SMP) performance. The rank keyword determines the number of rows that aresimultaneously updated during the decomposition.



Chapter 8: Bolt preload

Bolt preload improvements for linear solutionsThe following bolt preload improvements are available for the linear solutions 101, 103, 105, 107through 112. Also see Bolt preload improvements for SOL 401.

Automatic bolt coordinate system and bolt axis

To model bolts with CHEXA, CPENTA and CTETRA elements for the linear solutions, you use theETYPE=2 input format described on the BOLT bulk entry. This format includes the CSID and IDIRfields which define the bolt coordinate system and the bolt axis, respectively.

Previously, a BOLT bulk entry with ETYPE=2 defined for a linear solution required that you defineboth the CSID and IDIR fields.

Now in NX Nastran 12, if you leave both the CSID and IDIR fields blank, the software willautomatically determine the coordinate system and the bolt axis.

The BOLT bulk entry defined with ETYPE=2 requires that you list the grid point IDs on the Gi fieldswhich are connected to the element faces where the software will cut the bolt. When you leave boththe CSID and IDIR fields blank, the software requires that the element faces which are associatedwith the grid points listed on the BOLT entry lie approximately on a plane perpendicular to theintended bolt axis. This is important for the software to automatically compute the bolt coordinatesystem and the bolt axis. If you leave both the CSID and IDIR fields blank, and the cut you define isnot close to being planar, a fatal error will occur. In addition, if the cut is planar but the plane is notperpendicular to the intended bolt axis, the software computed coordinate system and bolt axis will beskewed from the intended bolt axis, and your preloads will not be accurate.

Note

For the NX Nastran 12 release, regardless if the CSID and IDIR fields are defined or notdefined, when using the ETYPE=2 cut-plane method, the grid points listed in Gi should becoplanar, or at least close to coplanar. If your bolt cut-plane is not planar, your solutionresults may not be accurate. If you define a ETYPE=2 bolt with a non-planar cut-plane, thesoftware will still solve without a warning.

ETYPE=2 bolt glue approach

When you define a bolt with ETYPE=2 on the BOLT bulk entry, the software cuts the bolt in half, itcreates new grid points resulting in grid pairs at the cut, it evenly distributes the opposing axial boltforce to the grids on each side of the cut, and it solves a statics solution to determine the axialdisplacement of each bolt half. The software then holds the grid pairs in their relative deformedstate for the consecutive static solution.

Previously, the software would apply MPC conditions between the grid pairs to hold them in theirrelative deformed state.



Now, the software creates a glue connection at the cut which holds the grid pairs in their relativedeformed state. The glue based approach accounts for bending along the bolt axis since rotationalstiffness is included in the glue condition. The MPC approach accounts for the axial stiffness, but notthe rotations. As a result, bending is not accounted for with the MPC approach.

Note

The glue approach is not supported by the element iterative solver in SOL 101. If you runwith the element iterative solver in SOL 101 and you have defined the ETYPE=2 bolt, thesoftware will revert to the MPC approach.

Bolt preload specified by BOLTFOR bulk entry

Previously, linear solutions only supported the BOLTFOR bulk entry to define a bolt preload force.

You can now use the BOLTFRC bulk entry with TYPE=LOAD to define the bolt preload as a force.A bolt force defined with the BOLTFRC bulk entry with TYPE=LOAD or with the BOLTFOR bulkentry are equivalent.

The DISPLACEMENT and STRAIN preload options on the BOLTFRC bulk entry are not supported forthe linear solutions and will cause a fatal error if defined.



Chapter 9: Memory allocation for external applications

Memory allocation for external applicationsWhen you run SOLs 402, 601, 701, or a SOL 108 acoustic solution which includes FEMAO, NXNastran calls an external application after it processes the input file.

Prior to calling these external applications, NX Nastran automatically reduces most of the memoryyou had requested with the mem keyword. As a result, more memory is available for the externalapplication.

NX Nastran releases as much memory as possible prior to calling the external application, andit exports an environment variable that declares the amount of memory released. The externalapplication reads this environment variable and limits its allocation of memory to that amount. Thisguarantees that NX Nastran and the external applications use only the memory that you request.

The reduced amount of memory will be the difference between the amount specified by the memkeyword and the amount required by the Nastran Executive System. The amount required by theNastran Executive System is approximately 200 MB plus the amounts specified by the bpool andsmem keywords, or 10% of the memory specified by the mem keyword, whichever is greater.

Note

• Memory requested on the command line is the high-water mark.

• Memory reduction will not occur if half of the mem value is less than that required bythe Nastran Executive System.

• The memory allocation for external applications occurs automatically. You do notneed to request it.

• The amount of memory that NX Nastran reduces for the external application is labeledas Dynamic Memory in the .f04 file.

• NX Nastran calls external applications with the ISHELL module, or launches them byloading a DLL and executing the external application in the DLL.


Chapter 10: Topology Optimization

Topology OptimizationBeginning with NX Nastran 12, you can use the NX Nastran optimization solution sequence (SOL200) to run a topology optimization. The SOL 200 topology optimization removes material in a waythat is consistent with your objective function and constraints. You can request a single topologyoptimization solution across multiple analysis types including statics and dynamics.

The software removes material during the analysis by reducing the Young’s Modulus and thenormalized mass density (NMD). Note that, since you can replace mass density with weight densityon the MATi bulk entry, all following discussion of normalized mass density (NMD) also refers to theweight density case.

The software automatically creates a design variable for each element you select for the optimization.The NMD begins with a value of 1.0 which means that all of the element material is present. It isreduced during the analysis as the software removes material during optimization. An NMD valueapproaching 0.0 indicates that most of an element's material has been removed.

It should be noted that if the weight density of the material is input instead of the mass density, thenthe same arguments in SOL 200 topology optimization hold for normalized weight density.

The NMD result is output for each element you defined as active for the optimization. This outputappears under the heading “Normalized Mass Density” in the .f06 file, when requested with theparameter NASPDV, and in the new ONMD data block if an .op2 file is requested with the appropriatePARAM, POST setting (-1 or -2).

New tools are available in Simcenter Pre/Post 12.0 for you to post process the NMD results. Thesetools include the option to output smoothed geometry in STL or in bulk data format. You can thenimport these smoothed formats back into Simcenter Pre/Post, create a new meshed model based onthe new topology, then use the updated model for visualization and further analysis.

The new SOL 200 capability replaces the topology optimization that was available in NX Nastran11. The input requirements for the new SOL 200 capability are not the same as those for the NXNastran 11 topology optimization capability. As in previous NX Nastran releases, you can use SOL200 to run a parametric optimization, although currently it is not advisable to run simultaneouslywith topology optimization. In general, the inputs to define the SOL 200 topology optimization arethe same as the inputs used to define the SOL 200 parametric optimization. The most significantdifference is the new DVTREL1 bulk entry.

The SOL 200 topology optimization inputs are as follows:

Design Variables

Design variables define your allowable changes to the finite element model. For topologyoptimization, the software automatically creates a design variable for the elements that you selectfor the optimization.



You use the new DVTREL1 bulk entry to select the elements to be included or not to be included inthe topology optimization. The GRPID field on the DVTREL1 entry references the ID of a GROUPbulk entry that specifies a list of elements.

The following elements are topology optimizable elements:

• The 3D solid elements CHEXA, CPENTA, CPYRAM, CTETRA

• The shell elements CTRIA3, CTRIA6. CTRIAR, CQUAD4, CQUAD8, CQUADR

In the referenced GROUP bulk entry, you can include elements that are topology optimizableelements and elements that are not topology optimizable elements. However, only topologyoptimizable elements are considered for the relevant DVTREL1 bulk entry.

The elements that you select for the topology optimization can only reference an isotropic materialdefined with the MAT1 bulk entry. Elements in the model that are not selected for topologyoptimization can reference other material bulk entries.

The DVTREL1 entry is the only bulk entry you need to define to invoke topology optimization. Thefields on the DVTREL1 entry are described as follows:

The STATE field on the DVTREL1 entry allows you to optionally specify that the elements referencedin the GROUP field are either ACTIVE or FROZEN. The software creates design variables and otherrelevant data for active elements, but not for frozen elements. The STATE field default is ACTIVE.The following examples demonstrate how the STATE field is used.

• If you define one or multiple DVTREL1 entries and FROZEN is defined in the STATE field for all,the elements that are not referenced by a DVTREL1 entry are active. This scenario is usefulwhen you are designating most of your model as active except for a few elements. You only needto reference the few frozen elements on one or more DVTREL1 entries.

• If you define one or multiple DVTREL1 entries and all use the default for the STATE field(ACTIVE), only the elements designated as ACTIVE are active. The elements that are notreferenced by a DVTREL1 entry are frozen.

• If you define multiple DVTREL1 entries and some use the default for the STATE field (ACTIVE)and some have FROZEN defined, those elements that appear in both types of lists will be treatedas frozen. Elements not in either type of list, that is, not referenced by DVTREL1 entries, willalso be frozen.

Note that other elements that are not 3D solids or shell elements can be included in the modeland their stiffness and mass are included in the analysis. The software simply does not create adesign variable for these elements, so their stiffness and mass remain constant during the topologyoptimization process.

The DVID1 field on the DVTREL1 entry allows you to optionally control the identification numbers forthe auto-generated design variables. The software auto-generates a DESVAR entry for each elementthat is active. If used, the DVID1 field is interpreted differently for the various STATE field scenarios.

• When FROZEN is defined in the STATE field for all DVTREL1 entries, the design variable IDnumbering for the active elements begins with the largest DVID1 found among all DVTREL1entries. If none of the DVTREL1 entries have the DVID1 field defined, the element IDs of theactive elements become the design variable IDs with an automatic offset applied if a conflictoccurs.



Topology Optimization

• When ACTIVE is defined in the STATE field for a DVTREL1 entry, the design variable IDnumbering for the elements referenced by that DVTREL1 entry begins with the value definedin the DVID1 field. The numbering then continues incrementally for the remainder of the activeelements referenced by that DVTREL1 entry.

If DVID1 is undefined, the element IDs of the active elements become the design variable IDs withan automatic offset applied if a conflict occurs.

You can optionally restart a new solution using design variable values from the best design cycleof a previous solution. For this purpose, the original input file should include the following casecontrol command:

ECHO=PUNCH(BSTBULK)

This will create a jobname.pch file with the best design cycle bulk data.

For the consecutive solution, using a copy of your original input file, you will replace the bulk datawith the updated bulk data stored in the punch file jobname.pch.

You can also restart the new solution using design variable values from the last design cycle of aprevious solution. The original input file should include the following case control command:

ECHO=PUNCH(NEWBULK)

Note that, in both cases, the DSVFLG field on the DVTREL1 entries is automatically written out with avalue of 1 to the punch file. This indicates that the design variable values now start with those in thepunch file, where the DESVAR data is now in an expanded form.

For the consecutive solution, if the only item written into the punch file is the updated bulk data, youcan alternatively replace the original bulk data with the following line:

include jobname.pch

Design responses

The first-level design response selects an output such as weight (or mass, depending on how thematerial density is defined), stress, or displacement. You create first-level responses with theDRESP1 bulk entry.

The second-level and third-level responses combine many responses and other items, such asdesign variable values, using mathematical relationships. You create second-level responses withthe DRESP2 bulk entry and third-level responses with the DRESP3 bulk entry. The second-levelresponse uses the mathematical relationships available on the DEQATN bulk entry or a limitednumber of defined functions, such as AVG for averaging values. The third-level response is computedwith an external program that you would need to connect to the NX Nastran run. As a result, you canuse sophisticated mathematical relationships and external software when computing a third-levelresponse.

For example, to minimize the compliance value from a single load case, you would use the DRESP1entry. If you want to minimize the maximum of three separate compliance values from three separateload cases (for a MinMax solution), currently you will need to use a more sophisticated approach,such as either the Beta Method or a combination of the DRSPAN case control and the DRESP2 bulkentries. These methods are described below under Design responses across subcases.

These methods are slightly more involved to formulate in terms of standard NX Nastran input data. Asimplified approach will be available with the NX Nastran maintenance package 12.0.0 MP1 for the




special case of CMPLNCE (compliance) response. See NX Nastran maintenance package 12.0.0MP1 for a description of the simplified approach.

The design response must be referenced by a design objective or by a design constraint to beconsidered in the optimization process.

• A design objective works to minimize or maximize a response.

• A design constraint places bounds on a response.

• The stress, strain, and force responses require an item code that specifies the type of elementoutput and the component.

For example, a linear stress response at the center of a CQUAD4 (element code “33”), the von Misesstress at the Z1 fiber location (bottom side of the element) uses item code 9. For a list of item codes,see Item Codes in the NX Nastran Quick Reference Guide.

In addition to the existing responses available on the DRESP1 entry, the new compliance designresponse is now available for a static subcase. Compliance is a meaure of flexibility and isrepresented by the integration across the FE model of the dot product of the strain and stress tensors.It is also identically twice the total strain energy for a given subcase.

You define the new compliance design response by including CMPLNCE in the RTYPE field on theDRESP1 entry.

Design objective

The design objective is the single overall goal of the optimization. You define the single objectivewith the DESOBJ case control command, which selects a design response. Design objectives canuse the first-level responses (DRESP1 entry), or they can use second-level (DRESP2 entry) orthird-level (DRESP3 entry) responses. The DRESP2 and DRESP3 responses can be used to definesophisticated combinations of responses and computations, as well as to help in problem set-up,such as for MinMax problems.

• You define a single design response for the design objective.

• You choose to either minimize or maximize the design response.

• You can define the design objective for the solution (globally, above the subcases) or for onlya specific subcase.

For example, the objective to minimize weight is commonly defined globally. However, the objectiveto minimize the x-displacement at a grid point can normally only be defined for a specific subcase.For more sophisticated cases, as with MinMax problems, there are methods that allow responsescomputed across many subcases to be combined into a single global response. As a result, if youdefine an objective above the subcases (globally) and you reference a response that is subcasedependent such as compliance or displacement, and you have multiple subcases for which you mayor may not want this response computed, you must currently make yourself familiar with thesemethods. See Design responses across subcases.

Design constraints on response

Design constraints on response define limits on specific responses of your FE model. Theoptimization algorithm works within the scope of your constraints as it changes design variables whileattempting to meet your overall design objective.




• You define design constraints for the solution (globally, above the subcases) with the DESGLBcase control command. Design constraints defined globally can use the first-level responses(DRESP1) weight or volume, or they can use second-level (DRESP2) or third-level (DRESP3)responses computed as a combination of many response types defined at the subcase levelas well as other data types. However, to be combined into a global response, the subcasedependent responses should be exclusively assigned to their respective subcases by way ofthe DRSPAN case control command. Alternatively, the Beta Method can be used to combinesubcase dependent responses by a more roundabout though often smoother approach, wheresome other function is eventually assigned to the objective function or constraint. See Designresponses across subcases for a description of these methods.

• You define design constraints in a subcase with the DESSUB case control command. You canuse any type of subcase related response at the subcase level.

Both the DESGLB and the DESSUB commands select the DCONSTR or a DCONADD bulk entry,which reference specific design responses defined with the DRESPi bulk entries. The samedesign response can be selected in multiple design constraints from different subcases, as long asthat response is not exclusively assigned to a particular subcase with the DRSPAN case controlcommand. A single DESSUB entry can reference multiple DCONSTR entries with the same ID,but on different responses.

Subcase types

You can include multiple subcases in a single SOL 200 topology optimization solution. You use theANALYSIS case control command to designate the subcase type. The following subcase typesare supported:

Statics, Normal Modes, Modal Frequency, Modal Transient, and Buckling (also requires a Staticsubcase).

For example, several static subcases and a normal modes subcase could all be included.Displacement and stress results from the static subcases, along with specific eigenvalues from thenormal modes subcase, can all be used as design responses and referenced by design constraints orby the single objective.

SOL 200 parameters – Bulk Data

There are numerous parameters that control various aspects of the optimization process. You definesome of these parameters on the DOPTPRM bulk entry and others using the PARAM bulk entry.The following is a partial list of some of the key parameters that you can use in a SOL 200 topologyoptimization. See the DOPTPRM bulk entry and Parameter Descriptions in the Quick ReferenceGuide for a listing of all parameters and their full descriptions.

You can define the following parameters on the DOPTPRM bulk entry:

• DESMAX – Defines the maximum number of design cycles to be performed.

• EDVOUT – Defines what fraction of DVEREL1 generated design variables with increased anddecreased values are to be printed into the Design Variable History at the end of the f06 file, aswell as at requested cycles.

• GMAX – Maximum constraint violation allowed for a feasible design.

You can define the following key parameters with the PARAM bulk entry:




• BDMNCON – Defines the number of the design cycle at which the software will start theapplication of any manufacturing constraints, except for planar symmetry manufacturingconstraints. (Default=10)

• DESPCH – Defines the frequency in which the solver writes the updated design variables andother updated bulk data output, such as designed property types, to the file jobname.pch.

• DESPCH1 – Defines the level of detail in which the solver writes design cycle output to thefile jobname.pch.

• NASPDV – Defines if the topology optimization design variables are to be written to the .f06 file.The software automatically creates the design variables for the elements that you select for theoptimization. This output can be substantial for large models.

o NASPDV = 0 (Default) The topology optimization design variables are not written to the.f06 file.

o NASPDV = 1 The topology optimization design variables are written to the .f06 file.

• NASPRT – The frequency with which the solution performs data recovery and writes output to the.op2 file. The NASPRT parameter includes the following new options for topology optimization.

o NASPRT = 0 (Default): Output occurs for the 0th and the best design cycle.

o NASPRT = N where N>0: Output occurs for the 0th cycle and for every Nth increment.

o NASPRT = -1: No output occurs.

o NASPRT = -2: Output occurs for every improved design cycle.

Note that for topology optimization, none of the NASPRT settings specifically requests output forthe last design cycle. As a result, the NMD result for the last design cycle is only output when thelast design cycle happens to coincide with one of the NASPRT requests described above.

The following descriptions for NASPRT are specific to a non-topology optimization run. Thisbehavior is the same as in previous releases.

o NASPRT = 0 (default): Output occurs for the 0th and the last design cycle.

o NASPRT = N where N>0: Output occurs for the 0th, for every Nth increment, and for thelast design cycle.

o NASPRT < 0: No output occurs.

Lattice support

Structurally, a lattice is a two- or three-dimensional framework consisting of a crisscrossed patternof material strips. With modern technology, small scale lattices can be created using additivemanufacturing. Each lattice type has a unique averaged out NMD to stiffness relationship.

You can request that all of the elements you have designated as active with the DVTREL1 entry aremade of the same type of lattice structure. The new DMRLAW bulk entry is available to selectcurrently a single lattice type for your model. If you have selected a lattice type, the software willadjust design variable to property relations accordingly.




You can select from the following types on the new DMRLAW bulk entry:

TYPE Field Value: Lattice TypeOCTET OctetCUBIC CubicBCC BCCFCC FCCOCTAHDRL OctahedralBCCCUBIC BCC+CubicFCCCUBIC FCC+CubicBCCFCC BCC+FCCBFCUBIC BCC+FCC+CubicLINEAR NMD and Young’s modulus change at the same rate.SIMP See Penalty laws below.RAMP (Default) See Penalty laws below.

Penalty laws

In addition to the lattice definitions, you also have the option to define a mass density to stiffnessrelationship using one of two penalty laws on the DMRLAW bulk entry. The penalty laws define theeffective Young's modulus as a function of the NMD μ.

• For TYPE=SIMP, the SIMP law has the form:

where p is a penalty parameter defined with the TYPEPRM field. If you define TYPE=SIMP butleave the TYPEPRM field blank, the software uses the default value of p=3.

• For TYPE=RAMP, the RAMP law has the form:

where q is a penalty parameter defined with the TYPEPRM field. If you define TYPE=RAMP butleave the TYPEPRM field blank, the software uses the default value of q=5. If you leave bothTYPE and the TYPEPRM fields blank, the software uses RAMP with q = 5.0.

Manufacturing constraints

Manufacturing constraints are optional restrictions that you can include in your topology optimizationsolution to guide the design towards meeting your production criteria. You can use the new DMNCONbulk entry to request that the software enforce the manufacturing constraints listed below. MultipleDMNCON bulk entries are supported if you would like to define a variety of manufacturing constraints.

• Additive (ADDM)

Additive manufacturing such as 3D printing builds material layer by layer. The previous layersin a build-up should be able to support consecutive layers. When building up overhanginggeometry, if the overhang is built at an aggressive angle, there is a possibility that the structurecan collapse as a result of cantilevered material. Also, practical reasons may dictate that slender




members of an additive manufacturing built structure not be below a certain minimum size incross-sectional dimension.

For the angle requirement, you define a maximum overhang angle and the manufacturingdirection which is normal to the base plate. Overhang angles are measured relative to thepositive manufacturing direction vector.

For the minimum size requirement, you simply enter an allowable minimum dimension. Theoverhang angle and the minimum dimension are separate and independent options.

• Casting die direction (CDID)

Parts that are cast should not have any pockets or protrusions that would interfere with the moldor die pieces from parting, or the part coming out of the mold.

You define the coordinates of a point on the casting plane, a vector normal to the casting plane, avector along which a part of the mold travels when separating, and another optional vector alongwhich another part of the mold, if it exists, travels when separating.

• Checker-boarding control (CHBC)

Checker-boarding control is ON by default, even when a DMNCON bulk entry is not specified.

Checker-boarding is a condition where topology optimizers remove material in an alternatingpattern similar to a checker board, when simpler finite elements are used. It is undesirablebecause it does not represent an optimal distribution of material and the results are difficult tomanufacture. The checker-boarding control constraint can be used to help prevent this conditionfrom occurring.

Note: If you want to disable the checker-boarding control, you must define the DMNCON bulkentry with TYPE=CHBC and a negative real number in the OFF-FLAG field (currently labeled"Radius" in the Simcenter dialogs).

• Cyclic symmetry (SYMC)

This is similar to the planar symmetry scenario below, except that a full circular model is built.The mesh on each sector does not need to match.

The software works to symmetrize the NMD values on each sector, based on your specification ofeither repeated or reflected symmetry.

You define the axis of rotation, the number of sectors (NSECT) within the 360 degrees, andrelative to a 0-degree symmetry plane on one side of the representative sector, you definea point on the symmetry plane and a radial vector perpendicular to the axis of rotation alongone of the edges of the sector on the symmetry plane. The software sweeps the 0-degreesymmetry plane counterclockwise by the angle = 360/ | NSECT | to determine the other side ofthe representative sector.

When NSECT is a positive integer, the software treats your model as one of repeated sectors.When NSECT is a negative integer, the software treats your model as one of reflected sectors.With repeated symmetry, each sector is similar to every other sector. With reflected symmetry,each sector is the mirror image of the previous sector. You can use reflected symmetry only withan even number of sectors.

• Extrusion along a straight line (EXTC)

Extruded parts must have material continuity in the extrusion direction.




You define the extrusion direction.

• Min/Max size (MINS or MAXS)

This allows you to control the minimum or maximum member size, such as the minimum ormaximum dimension at a cross-section. For example, if you define the maximum member size,truss members created by the optimization process will tend to be no thicker in cross-sectionthan the specified size.

You define the size value.

• Planar symmetry (SYMP)

With this constraint, your model must be meshed on both sides of the symmetry plane. The meshdoes not need to match on each side of the symmetry plane.

The software works to symmetrize the NMD values on both sides of a given symmetry plane, bylinking design variables in an appropriate manner on two sides of the symmetry plane. More thanone symmetry plane manufacturing constraint may be specified.

You define a point on the symmetry plane and a vector normal to the symmetry plane.

Manufacturing constraint delay

The new parameter BDMNCON, normally with a default of 10, defines the number of the designcycles at which the software will start the application of manufacturing constraints during the SOL 200topology optimization solution, except for the SYMP type constraint. This delay has been found toimprove the results when manufacturing constraints are specified.

The SOL 200 maximum allowed number of design cycles, which is defined with the DESMAXparameter on the DOPTPRM bulk entry, may affect the default value of BDMNCON. As a result, theBDMNCON parameter default is the smaller of 10 cycles or of the value of the DESMAX parameterminus 3, but not less than 2.

Design responses across subcases

Most DRESP1 design response types are computed at the solution subcase level. Exceptions are theweight and volume response types which are computed independent of any subcases. When youdefine an objective or constraint above multiple subcases (globally), you cannot directly reference aDRESP1 response that is subcase dependent, such as compliance or displacement. You currentlymust instead define NX Nastran input syntax that exclusively assigns DRESP1 responses to relevantsubcases as a precursor to formulating a global response.

For this purpose, you will need to learn about the NX Nastran case control commands DRSPAN andSET, and about the bulk entries DRESP2, DRESP3, DEQATN. These inputs are not yet availablethrough the Simcenter dialogs. Below, we give an example of how this is done for a particularpopular class of problems.

Let us take the MinMax problem of minimizing the value of the maximum of a particular DRESP1response as computed in various subcases. Since an objective minimizes or maximizes a singlequantity, you must resolve the responses computed in your many subcases into a single value.For example, if you have ten subcases with ANALYSIS=STATIC, each with unique load cases,and you have a single objective to minimize compliance, you likely want to minimize the largest ofthe compliance values from the 10 subcases. However, the code will not automatically make thisassociation and you need to make this request in your input file by using standard NX Nastraninput syntax.




You can accomplish this by using either the DRSPAN or BETA methods which are both describedbelow. The DRSPAN method is simpler to define than the BETA method, although, when posedproperly, the BETA method achieves better convergence and results on the average. You are advisedto try both to see which one will produce the better result for your particular job type.

DRSPAN method

• The DRESP1 bulk entry defines the response type. For example, you can define a DRESP1bulk entry which requests that compliance be computed, but this response is not yet tied to aparticular subcase, as DRESP1 responses are not associated with any subcases unless throughuse of DRSPAN or DCONSTR.

• You define a DRSPAN=n case control command inside the subcase you want to exclusivelyassign certain DRESP1 entries to, where n is the ID of a SET command. This association tellsthe software that this is the only subcase you want these responses to be computed at. It isimportant to note that once a DRESP1 is associated with a particular subcase by use of DRSPAN,it may not be associated with another subcase. This is different than the use of DRESP1 inDCONSTR, where DCONSTR for different subcases may refer to the same DRESP1, such thatit is computed separately for each subcase.

• You define a SET n = ID1, ID2, ….IDi within case control, which lists the IDs of the DRESP1entries you want to exclusively associate with a subcase.

• You can create multiple DRSPAN and SET command combinations when you want to exclusivelyassign different sets of DRESP1 entries to different subcases.

• Once various DRESP1 are exclusively assigned to certain subcases by way of DRSPAN/SETcombinations, they can now be combined, together with other entities if needed, in one or moreDRESP2 or DRESP3 type response, which can now be treated as global responses. An examplewould be the use of the MAX function in a DRESP2, acting on DRESP1 from more than onesubcase, and pointing to the maximum of these as the DRESP2 response value. You define yourdesign objective or DESGLB constraint globally which selects such a DRESP2 or DRESP3 entry.

DRSPAN method example

The DRESP1 entries in the following input are each associated with a different subcase and arecombined into a single DRESP2 entry which is selected as a global response by the design objective(DESOBJ).

....SOL 200$DESOBJ(MIN) = 5DESGLB = 7$SET 100 = 111SET 200 = 222$SUBCASE 1LABEL = Nastopt - Statics 1LOAD = 1SPC = 2ANALYSIS = STATICSDRSPAN = 100




$SUBCASE 2LABEL = Nastopt - Statics 1_1LOAD = 3SPC = 4ANALYSIS = STATICSDRSPAN = 200

$BEGIN BULK....DRESP2 5 MAXCMP MAX+ DRESP1 111 222$DRESP1 111 SUBCAS1 CMPLNCEDRESP1 222 SUBCAS2 CMPLNCE$....

BETA method

• The BETA method requires that you first determine the order of magnitude of your subcaseresponses for the starting design. Currently, you will need to first run an initial analysis to getthese values. If you are using a compliance response for your objective, you can request strainenergy output using the ESE=ALL case control command and then multiply the total strain energyvalues at the tops of the tables for the various subcases by 2.0 to compute the compliance valuefor each. For this initial analysis, you can define DESMAX=0 on the DOPTPRM bulk entry toavoid unnecessary design cycles.

After your initial solution completes, open the *.f06 file and search for the following for eachsubcase. The example below includes output for two subcases.

....E L E M E N T S T R A I N E N E R G I E S

ELEMENT-TYPE = TETRA * TOTAL ENERGY OF ALL ELEMENTS IN PROBLEM = 9.730185E+04SUBCASE 1 * TOTAL ENERGY OF ALL ELEMENTS IN SET -1 = 9.730185E+04....

E L E M E N T S T R A I N E N E R G I E SELEMENT-TYPE = TETRA * TOTAL ENERGY OF ALL ELEMENTS IN PROBLEM = 4.452013E+04SUBCASE 2 * TOTAL ENERGY OF ALL ELEMENTS IN SET -1 = 4.452013E+04....

As a result:

For Subcase 1: Compliance = 2.0 * 9.730185E+04

= 1.946037E+05

For Subcase 2: Compliance = 2.0 * 4.452013E+04

= 8.904026E+04

From the computed compliance values, you need to determine a reasonable normalizing valuesuch that (compliance / normalizing value) < 1.0 (but not << 1.0) for all subcases. For theexample above, a normalizing value of 1.0E+06 achieves this goal. The normalizing value isused in the following steps.




• You will now create an artificial design variable which will act as a cap on the compliances fromthe associated subcases. See the Note below as to how an ID is assigned to this design variable.The artificial design variable serves the purpose of converting the discrete MAX concept to acontinuous one based on a single value. For the example described here, we will assume anID of 1000000.

Note: (a) For topology optimization, which is indicated by the DVTREL1 entry, the software willoffset internal design variables based on any explicit artificial variable ID, so the ID selection isarbitrary. (b) For classical SOL 200 optimization jobs, the ID of the artificial variable should notconflict with existing explicit design variable IDs. (c) For topometry optimization (indicated byDVEREL1 data), care should be taken to avoid conflict with DVEREL1 defined internal designvariable numbering. Future development is planned to remove this small complication for thelast two cases.

The starting value for your design variable should be larger than the maximum of the normalizedcompliance values computed for all subcases for the initial design. For example, usingthe subcase 1 compliance value of 1.946037E+05, the normalized value is computed as(1.946037E+05 / 1.0E+06) = 0.194, and as 0.089 for the second subcase. So, for the example,0.2 can be used as the starting value for the artificial design variable. This value is greaterthan both normalized compliance values, and is therefore a cap on the compliance values forthe initial design.

DESVAR 1000000 SYNTH1 0.2 1.0E-6 100.0

The upper bound for this design variable has been given high to allow the compliance valuesto increase as much as necessary. A small upper bound, such as 1.0, may constrain the jobunnecessarily. The lower bound is taken as 1.0E-06, a sufficiently small value, which we donot expect will be breached.

• Next, you will want to make sure that the value of the artificial design variable remains a cap onthe compliance values throughout the optimization process. Thus, at the optimum, the maximumof the two normalized compliance values will be no greater than the value of the artificial variable.This requires setting up constraints for each of the two subcases.

Let C1 and C2 be the actual compliance values from subcases 1 and 2, respectively. Also let Xbe the value of the artificial design variable. Thus, our constraints should be of the form:

Ci/1.0E6 ≤ X, i=1,2 and therefore,

Ci/1.0E6 - X ≤ 0.0, i=1,2

Since the software may have precision problems with values very close to 0.0, you can add 10.0(or some other reasonable number) to both sides:

Ci/1.0E6 - X +10.0 ≤ 10.0, i=1, 2

You now have a constraint on the function [Ci/1.0E6 – X + 10.0] with an upper bound of 10.0.This function on the left hand side will be represented by a DRESP2 type response, but first youneed to define the general compliance value Ci by a DRESP1. For example:

DRESP1 111 COMPLNCE CMPLNCE

Note that this DRESP1 can be used for both subcases (or, in general, multiple subcases), aswe will show. This is different than for the DRSPAN case, where a separate DRESP1 had to beexclusively assigned to each subcase.




You are now ready to define your DRESP2, which will be constrained as shown above:

DRESP2 201 BCOMPL1 500+ DESVAR 1000000+ DRESP1 111

and this DRESP2 refers to an equation given by DEQATN, 500:

DEQATN 500 F(B,C) = C/1.0E6 – B + 10.0

which is your function defining how the DRESP2 value should be computed. B and C are in thesame order as the items in the DRESP2 response. So far, both the DRESP1 and the DRESP2are simply templates. Only when referred to by appropriate DCONSTR will they be used tocompute values for relevant subcases.

• A DCONSTR specifies a constraint in a constraint set belonging either to a particular subcase orto DESGLB (global constraint set). From a subcase, DCONSTR are referenced by the DESSUBcase control command. Since you have two subcases, you will need a separate DESSUB foreach subcase, for example:

SUBCASE 1…DESSUB=101

$SUBCASE 2…DESSUB=102

In this particular case, we have only one DCONSTR for each DESSUB:

DCONSTR,101,201, ,10.0DCONSTR,102,201, ,10.0

Note that the response referred to from each DCONSTR is DRESP2, 201, which is now computedseparately at each subcase (as is the DRESP1, 111) for the evaluation of each DCONSTR. Alsonote the upper bound of 10.0 from our constraint expression above. For this case, it is best toleave the lower bound to default, as it is not expected to be instrumental in the process.

• You are now ready to define your objective, which is to find the minimum value of the artificialdesign variable that caps the compliance values as they increase. In NX Nastran, only a responsecan be assigned to the objective function, not a design variable. However, by employing a simpletrick, the artificial design variable value can be converted to a response value:

DRESP2 400 OBJ AVG+ DESVAR 1000000

where AVG means compute the average of the values of the listed items (of which there is onlyone), after which you can define the objective function as:

DESOBJ(MIN) = 400

BETA method example

The following lines of input demonstrate the BETA method for the two subcase example describedabove.




...SOL 200$DESOBJ(MIN) = 400....$SUBCASE 1LOAD = 1SPC = 2ANALYSIS = STATICSDESSUB=101

$SUBCASE 2LOAD = 3SPC = 4ANALYSIS = STATICSDESSUB=102

$BEGIN BULK$DRESP2 400 OBJ AVG+ DESVAR 1000000$DESVAR 1000000 SYNTH1 0.2 1.0E-6 100.0$DRESP1 111 COMPLNCE CMPLNCE$DRESP2 201 BCOMPL1 500+ DESVAR 1000000+ DRESP1 111$DEQATN 500 F(B,C)=C/1.0e6-B+10.0$DCONSTR,101,201,,10.0DCONSTR,102,201,,10.0$...

NX Nastran maintenance package 12.0.0 MP1

An alternative enhanced DESOBJ command will be available with the NX Nastran maintenancepackage 12.0.0 MP1. Since the NX Nastran 12.0.0 MP1 release will not include updateddocumentation, the enhanced DESOBJ command and software behavior is described below. Thisdescription does not apply to NX Nastran 12.0. The NX Nastran 12.0.0 MP1 release will be includedwith the release of the Simcenter maintenance package 12.0.0 MP1.

The enhancement simplifies the specification of jobs involving design objectives (DESOBJ) on theminimization of a function of compliance values for multiple static subcases, with specific emphasison the maximum of these compliance values. While this can already be done in NX Nastran 12.0with the DRSPAN or BETA methods described in Design responses across subcases, the enhancedDESOBJ command will make it much easier to prepare input data and to run jobs through Simcenter12.0.0 MP1 directly. It is planned to enhance the DESOBJ command further in future releases toaccommodate more use cases.




The Simcenter 12.0.0 MP1 release inputs will not change. However, when you use Simcenter 12.0.0MP1 and you assign a compliance (CMPLNCE) response (DRESP1) to the objective function,Simcenter will automatically write the following to the NX Nastran input file:

DESOBJ (MIN, SCSET=ALL, SCFUNC=MAX) = ID_of_compliance_DRESP1

In the above, SCSET=ALL refers to all static subcases, and SCFUNC=MAX specifies that theobjective is to minimize the maximum of the compliance values from the multiple static subcases.

You can also modify the values assigned to SCSET and SCFUNC using either the Simcenter texteditor window or an external text editor to allow any of the options described below.

The updated DESOBJ format for the NX Nastran 12.0.0 MP1 release will be as follows.

The MIN or MAX selection will still request that the objective is to be minimized or maximized.

Also, n will still refer to a response ID, although, when using the new format (that is, SCSET andSCFUNC are defined) in NX Nastran 12.0.0 MP1, n can only refer to a compliance response definedwith the DRESP1 bulk entry.

SCSET=ALL will refer to all static subcases.

SCSET=m will refer to specific static subcaces, where m is the ID of a SET case control commandthat lists the relevant subcases.

SCFUNC=function will have the following function choices:

Function Description

SUM Compute the sum of the compliance values from the multiple staticsubcases.

AVG Compute the average of the compliance values from the multiple staticsubcases.

SSQ Compute the sum of the squares of the compliance values from themultiple static subcases.

RSS Compute the square root of the sum of the squares of the compliancevalues from the multiple static subcases.

MAX Use the maximum of the compliance values from the multiple staticsubcases.

MIN Use the minimum of the compliance values from the multiple staticsubcases.

As stated above, Simcenter 12.0.0 MP1 will only write the following when you assign a compliance(CMPLNCE) response (DRESP1) to the objective function:




DESOBJ (MIN, SCSET=ALL, SCFUNC=MAX) = ID_of_compliance_DRESP1

To vary this definition, you will need to edit the input file. For example, the following input, whichwould apply the SSQ function to the responses from the multiple static subcases, will need to bedefined manually in an input file:

DESOBJ (MIN, SCSET=ALL, SCFUNC=SSQ) = ID_of_DRESP1




DVTREL1

Element Selection for Topology Optimization

Selects the elements for the software to automatically create design variables andother related data for topology optimization.

FORMAT:

1 2 3 4 5 6 7 8 9 10

DVTREL1 ID LABEL GRPID STATE DSVFLG

DVID1

EXAMPLE:

DVTREL1 200 24

30000

FIELDS:

Field Contents

ID Identification number of DVTREL1 entry. (Integer>0)

LABEL Optional user-defined label. (Character)

GRPID ID of GROUP bulk entry that specifies a list of elements. The softwareassociates the following types of elements with topology optimization:

The 3D solid elements CHEXA, CPENTA, CPYRAM, CTETRA. andthe shell elements CTRIA3, CTRIA6. CTRIAR, CQUAD4, CQUAD8,CQUADR. Any other element types or IDs for non-existent elementslisted on a GROUP entry are ignored. (Integer>0)

STATE Specifies that the elements referenced in the GRPID field are eitherACTIVE or FROZEN. The software modifies the active elements, butnot the frozen elements. (Character; Default =ACTIVE). See Remark1 for examples demonstrating how the STATE field is used.

DSVFLG Flag set by the software when you are recycling design variables froma previous solution for restart purposes. (Integer=0 or 1; Default=0)

DSVFLG=0 or blank (Default): Value used in a first pass optimizationsolution. This value triggers the software to create new designvariables and other relevant data for the elements designated asACTIVE.

DSVFLG=1: Value used in a restart solution. This value triggers thesoftware to use already existing design variables and their valuescreated in a previous solution. Normally, the software sets this valueof 1 for DSVFLG automatically when writing the updated bulk datainto the punch file. See Remark 2.




Field Contents

DVID1 Option to control the identification numbers for the auto-generateddesign variables. (Integer≥0; Default=0)

If DVID1=0 or blank (Default), the design variable IDs will be equal tothe IDs of the associated elements plus an automatically calculatedoffset to ensure no conflicts occur with any other design variables.

If DVID1>0, see Remark 3 for the description.

REMARKS:1. The STATE field allows you to optionally specify that the elements referenced in

the GROUP field are either ACTIVE or FROZEN. The software creates a designvariable for each active element, but not for frozen elements. The STATE fielddefault is ACTIVE. The following examples demonstrate how the STATE fieldis used.

• If you define one or multiple DVTREL1 entries and FROZEN is defined inthe STATE field for all DVTREL1 entries, the topology optimizable elementsthat are not referenced by a DVTREL1 entry are active. This scenario isuseful when you are designating most of your model as active except fora few elements. You only need to reference the few frozen elements on aDVTREL1 entry.

• If you define one or multiple DVTREL1 entries and all use the default for theSTATE field (ACTIVE), only those elements designated as ACTIVE are active.Elements that are not referenced by a DVTREL1 entry are frozen.

• If you define multiple DVTREL1 entries and some use the default for theSTATE field (ACTIVE) and some have FROZEN defined, the elementsdesignated as ACTIVE are active. An exception to this is when an element isreferenced by multiple DVTREL1 entries and is designated as both FROZENand as ACTIVE. Such elements are frozen. All other elements designated asFROZEN along with any elements that are not selected in any DVTREL1referenced GROUP data are also frozen.

Note that other elements that are not 3D solids or shell elements can be includedin the model and are included in the analysis. The software simply does not createdesign data for these elements, so they remain constant during the topologyoptimization process.

2. You can optionally recycle design variable values from a previous solution to usethem in a restart. The procedure is as follows.

• In the original solution, your DVTREL1 entries will use the default valueDSVFLG=0 and the software auto-generates new design variables with initialvalues of 1.0. Also, in your input file for the original optimization solution, youwill request a punch file output containing the bulk data for the best designcycle, using the following command in case control:

ECHO=SORT, PUNCH(BSTBULK)




At the end of the original solution, the punch file that the software createswill include an entire BEGIN BULK section which includes everything fromyour original BEGIN BULK section but with some changes and additions.Specifically, your DVTREL1 entries in the punch file will now have DSVFLG=1defined, and the punch file will include the explicit design variable valuescorresponding to the best design cycle found in the original solution.

• For the restart solution, you will create a new input file which uses the BEGINBULK contents from the punch file created in original solution.

• If you wish to restart from the last design cycle instead of the best one, youwill need to use the following ECHO case control command in your originalinput file:

ECHO=SORT,PUNCH(NEWBULK)

When the last design cycle is the best one, this selection does not matter.However, it is not possible to know this until the original solution is complete.

3. The DVID1 field allows you to optionally control the identification numbers for theauto-generated design variables. The software auto-generates a DESVAR andother various data for each element that is active. The software uses the DVID1field differently for the following STATE field scenarios.

• When FROZEN is defined in the STATE field for all DVTREL1 entries, thedesign variable ID numbering for the active elements begins with the largestDVID1 found among all DVTREL1 entries. If none of the DVTREL1 entrieshave the DVID1 field defined, the element IDs of the active elements becomethe design variable IDs with an automatic offset applied if a conflict occurs.

• When ACTIVE is defined in the STATE field for a DVTREL1 entry, thedesign variable ID numbering for the elements referenced by that DVTREL1entry begins with the value defined in the DVID1 field. The numbering thencontinues incrementally for the remainder of the active elements referencedby that DVTREL1 entry. If DVID1 is undefined, the element IDs of the activeelements become the design variable IDs with an automatic offset applied ifa conflict occurs.




DMNCON

Manufacturing Constraint for Topology Optimization

Defines a manufacturing constraint for topology optimization.ADDITIVE

MANUFACTURING(ADDM)

FORMAT:

1 2 3 4 5 6 7 8 9 10

DMNCON ID ADDM

ANGLE MIND X Y Z N1 N2 N3

CASTING DIEDIRECTION(S)

(CDID)FORMAT:

1 2 3 4 5 6 7 8 9 10

DMNCON ID CDID

X Y Z N1 N2 N3

D1 D2 D3 D21 D22 D23

CHECKER-BOARDINGCONTROL

(CHBC)FORMAT:

1 2 3 4 5 6 7 8 9 10

DMNCON ID CHBC

OFF-FLAG

CYCLICSYMMETRY

(SYMC)FORMAT:

1 2 3 4 5 6 7 8 9 10

DMNCON ID SYMC

X Y Z N1 N2 N3

M1 M2 M3 NSECT

EXTRUSIONALONG ASTRAIGHT

LINE (EXTC)FORMAT:

1 2 3 4 5 6 7 8 9 10

DMNCON ID EXTC

N1 N2 N3




MINIMUMSIZE (MINS)

FORMAT:

1 2 3 4 5 6 7 8 9 10

DMNCON ID MINS

Size

MAXIMUMSIZE (MAXS)

FORMAT:

1 2 3 4 5 6 7 8 9 10

DMNCON ID MAXS

Size

PLANARSYMMETRY

(SYMP)FORMAT:

1 2 3 4 5 6 7 8 9 10

DMNCON ID SYMP

X Y Z N1 N2 N3

EXAMPLES:

DMNCON 500 SYMP

0.0 1.0 0.0 0.7071 0.7071 1.0

DMNCON 200 EXTC

1.0 0.0 0.0

FIELDS:

Field Contents

General Fields:

ID Identification number. (Integer>0)

TYPE Type of manufacturing constraint. (TYPE examples: ADDM, CHBC,EXTC) See Remark 4. (Character; No default)

Fields for Additive Manufacturing (ADDM):

Note that either ANGLE or MIND can be blank, indicating there is no such constraint.

ANGLE Maximum angle from the normal that points away from the baseplate, for overhangs, in degrees. (Real)

MIND Minimum allowed size. (Real).




Field Contents

X,Y,Z Coordinates of a point on a plane for the base plate. (Real)

Ni Components of a vector normal to the base plate in the direction ofmaterial addition. (Real)

Fields for Casting die direction(s) (CDID):

X,Y,Z Coordinates of a point on the casting plane. (Real)

Ni Components of a vector normal to the casting plane. (Real)

Di Components of a vector that defines the first direction of moldremoval. (Real)

D2i Components of an optional vector that defines a second direction ofmold removal. If these components D2i are all 0.0 or blank, then onlythe first direction is used. (Real: default=0.0,0.0,0.0)

Fields for Checker-boarding control (CHBC):

OFF-FLAG This field is used only to turn off the default checker-boarding control,achieved by entering a negative real number in this field. (Real)

The checker-boarding control manufacturing constraint is on bydefault, even when you have not defined the DMNCON bulk entry.To disable checker-boarding control, you must define the DMNCONbulk entry with TYPE= CHBC and a negative real number in theOFF-FLAG field. Any other choices for the OFF-FLAG field will resultin the checker-boarding control remaining on by default.

Fields for Cyclic symmetry (SYMC):

X,Y,Z Coordinates of a point on a selected symmetry plane, thereforedefined to be at 0 degrees. (Real)

Ni Components of a vector defining the axis of rotation. (Real)

Mi Components of a vector perpendicular to the axis of rotation, alongone of the edges of the model on the 0-degree symmetry plane. Thesoftware will sweep the 0-degree symmetry plane counter clockwiseby the angle = 360/NSECT to determine each of the consecutivesymmetry planes. (Real)

NSECT The number of sectors which would fill the 360 degrees. (Positiveor negative integer)

When NSECT is a positive integer, the symmetry is that of repeatedsectors. When NSECT is a negative integer, the symmetry is thatof reflected sectors.




Field Contents

Fields for Extrusion along a straight line (EXTC):

Ni Components of a vector defining the extrusion direction. (Real)

Fields for Min and Max size (MINS or MAXS):

Size Minimum or maximum member size. (Real)

Fields for Planar symmetry (SYMP):

X,Y,Z Coordinates of a point on the symmetry plane. (Real)

Ni Components of a vector normal to the symmetry plane. (Real)

REMARKS:1. Multiple DMNCON bulk entries are supported if you would like to define a variety of

manufacturing conditions. For example, you can have multiple DMNCON entrieswith TYPE=SYMP, and could also add another DMNCON entry with TYPE=MAXS.

2. The manufacturing conditions currently apply to all of the active elements selectedfor topology optimization.

3. Except for TYPE=SYMP, the parameter BDMNCON defines the design cycle atwhich the software will start application of the manufacturing constraints duringthe SOL 200 topology optimization solution. The resulting delay has been foundto improve the quality of results in topology optimization with manufacturingconstraints. The BDMNCON parameter default is the smaller of 10 cycles, or thevalue of the DESMAX parameter minus 3, but not smaller than 2. The DESMAXparameter defines the maximum number of design cycles allowed, and is definedon the DOPTPRM bulk entry. SYMP is applied from the beginning.

4.

TYPE Description

Additive (ADDM)

Additive manufacturing builds material layer by layer. Theprevious layers in a build-up must be sufficient to supportconsecutive layers. When building up overhanging geometry,if the overhang is built in an aggressive angle, there is apossibility that the structure can collapse as a result ofcantilevered material. You define a maximum overhang angleand/or a minimum size applicable to any slender members,as well as the manufacturing direction.

Overhang angles are measured relative to the positivemanufacturing direction vector.




TYPE Description

Casting diedirection (CDID)

Parts that are cast should not have any pockets that cannotbe formed or protrusions that would interfere with the moldpieces from parting, or with the part coming out of the mold.You define the coordinates of a point on the casting plane,a vector normal to the casting plane, a vector along whichone part of the mold travels when separating, and another,optional, vector along which the other part of the mold, if itexists, travels when separating.

Checker-boardingcontrol (CHBC)

Checker-boarding is a condition where topology optimizersremove material in an alternating pattern similar to achecker board, when simpler finite elements are used. Itis undesirable because it does not represent an optimaldistribution of material and the results are difficult tomanufacture. The checker-boarding control constraint canbe used to help prevent this condition from occurring.

OFF-FLAG < 0.0, the checker-boarding control is turned off.

OFF-FLAG ≥ 0.0, the checker-boarding control is left on.

* Note: The software applies the checker-boarding control bydefault even when you have not defined a DMNCON bulkentry. If you want to disable the checker-boarding control,you must define the DMNCON bulk entry with TYPE=CHBCand a negative real number in the OFF-FLAG field.

Cyclic symmetry(SYMC)

You provide a full circular model which has repeated cyclicsymmetry sectors. The mesh on each sector does notneed to match. The software will work to symmetrize thenormalized mass density (NMD) values on each sector. Youdefine the axis of rotation, the number of sectors (NSECT)within 360 degrees, and relative to a 0-degree symmetryplane, you define a point on that symmetry plane and aradial vector perpendicular to the axis of rotation along oneof the edges of the symmetry plane. The software sweepsthe 0-degree symmetry plane counter clockwise by the angle= 360 / | NSECT | to determine the consecutive symmetryplanes.

When NSECT is a positive integer, the software treats yourmodel as having repeated sectors. When NSECT is anegative integer, the software treats your model as havingreflected sectors. With repeated symmetry, each sector issimilar to every other sector. With reflected symmetry, everysector is the mirror image of the previous sector. You can usereflected symmetry only with an even number of sectors.

Extrusion along astraight line (EXTC)

Extruded parts must have material continuity in the extrusiondirection. You define the straight line extrusion direction.

Min size (MINS)This allows you to control the minimum member size forcreated “slender” members. You define the minimumcross-sectional "thickness" size.




TYPE Description

Max size (MAXS)

This allows you to control the maximum member size. Forexample, if you define the maximum member size, trussmembers created by the optimization process will not be any"thicker" than the specified size.

Planar symmetry(SYMP)

With this condition, your model must be meshed on bothsides of the symmetry plane. The mesh on each side of thesymmetry plane does not need to match. The software worksto symmetrize the NMD values on both sides of a givensymmetry plane. You define a point on the symmetry planeand a vector normal to the symmetry plane.




DMRLAW

Material relation law definition for SOL 200 topology optimization.

Defines the relation between material properties and the normalized mass density(NMD) for SOL 200 topology optimization.

FORMAT:

1 2 3 4 5 6 7 8 9 10

DMRLAW ID TYPE TYPEPRM

EXAMPLE:

DMRLAW 200 SIMP 3.5

DMRLAW 200 SIMP

DMRLAW 302 CUBIC

FIELDS:

Field Contents

ID Material relation law ID. (Integer > 0)

TYPE Type of law. See Remarks 2 and 3 for the supported law types.(Character; Default=RAMP, with TYPEPRM=5.0)

TYPEPRM Defines p for the SIMP penalty law, and q for the RAMP penalty law.See Remark 3. (Real; Default is p=3.0 for the SIMP law and q=5.0for the RAMP law)

REMARKS:1. Only a single DMRLAW bulk entry is allowed.

2. A lattice in this context is a thin truss-like repeating cell structure that ismanufactured, for example, using additive manufacturing. Each lattice type has aunique mass density to stiffness relationship. With the “LINEAR“ type (see below),the software auto-generates the design variables for topology optimization suchthat a linear relationship exists between the NMD and the Young’s Modulus. Incontrast, lattices, as well as SIMP and RAMP, impose non-linear relations.

Currently you can only request a single DMRLAW bulk entry for all elements youhave designated as active with one or more DVTREL1 entries. The software willadjust design variable to property relations accordingly.

The following types of lattice cells and penalty functions are supported:

TYPE FieldValue: Lattice Type

OCTET OctetCUBIC Cubic




TYPE FieldValue: Lattice Type

BCC BCCFCC FCCOCTAHDRL OctahedralBCCCUBIC BCC+CubicFCCCUBIC FCC+CubicBCCFCC BCC+FCCBFCUBIC BCC+FCC+CubicSIMP See Remark 3RAMP See Remark 3

3. In addition to the lattice types, you also have the option to define a mass densityto stiffness relationship using one of two following penalty laws. These penaltylaws define the effective Young's modulus as a function of the normalized massdensity μ.

• For TYPE=SIMP, the SIMP law has the form:

where p is a penalty parameter defined with the TYPEPRM field. If you leavethe TYPEPRM field blank, the software uses the default value of p=3.0.

• For TYPE=RAMP, the RAMP law has the form:

where q is the penalty parameter defined with the TYPEPRM field. If youleave the TYPEPRM field blank, the software uses the default value of q=5.0.



Chapter 11: Monitor points

Monitor points for element results and grid point forcesIn previous releases, NX Nastran supports MONPNT1 for SOL 144. In this release, NX Nastransupport of monitor points is expanded to include the new MONPNT2 and MONPNT3 bulk entriesfor SOL 101 and SOL 103.

The capability of monitor points is enhanced to include element results from stress, strain, or force,and to provide summation of grid point forces at specified integrated load points in a local coordinatesystem.

You use the new bulk entry:

• MONPNT2 to output component of stress, strain, or force at a named element. The softwareoutputs the results in a table titled STRUCTURAL INTERNAL MONITOR POINT LOADS (MONPNT2).

Because MONPNT2 operates on the data block level, it can monitor an NDDL entry from theSTRESS-STRAIN (contained in the oes.dll file) or FORCE (contained in the oef.dll file) outputdata block.

• MONPNT3 to sum select grid point forces at a chosen integrated load point. You select a set ofgrids to sum forces and moments about a specified point. The software outputs the results in atable titled STRUCTURAL INTEGRATED FREE BODY MONITOR POINT LOADS (MONPNT3).

Also, you can use the new MONITOR case control command to control the output of MONPNT2 andMONPNT3 results to the .f06 output file. You can place the MONITOR command above the subcaselevel or in individual subcases.

Note

You can optionally use the OIBULK parameter to request that the software writes all casecontrol commands, including the MONITOR3 command, to the CASECC data block inyour .op2 file.

For more information, see PARAM, POST ,< 0.

For an example that demonstrates the use of MONITOR, MONPNT2, and MONPNT3, see Monitorpoints example.



MONPNT2

Integrated Load Monitor Point — Element Monitor Output Results Item

Defines an integrated load monitor point at a named element, and outputs componentof stress, strain, or force at that element for SOL 101 and SOL 103 (SORT1 formatonly).

FORMAT:

1 2 3 4 5 6 7 8 9 10

MONPNT2 NAME LABEL

TABLE TYPE COMP EID

EXAMPLE:

MONPNT2 MPT22 This is a MONPNT2 monitor point

STRAIN CBAR EX1A 1100082

STRESS CBAR SX1A 1100234

FIELDS:

Field Contents

NAME A unique character string that identifies the monitor point. (Character; 8characters maximum; No default)

LABEL A string that identifies and labels the monitor point. (Character; 56characters maximum; Optional)

TABLE Type of output to be monitored. (Character; "STRESS", "FORCE", or"STRAIN"; No default)

TYPE Element type. (Character; No default)

COMP Component of the element type to be monitored. This is the COMP labelfor the particular table and element type. For a list of supported elementsand their components, see Stress monitor table and Force monitor table.(Character; No default)

EID Element ID. (Integer > 0; No default)

REMARKS:1. For a list of supported elements and their components, see Stress monitor table

and Force monitor table.

2. Because of the name/descriptor field, free-field, and large field data formats arenot supported for this bulk entry.

3. For shell laminates, only the homogeneous stress/strain is output. The NOCOMPSparameter allows you to control the shell laminate output. If this parameter:

= 0 or -1, The homogeneous stress/strain is output.



Monitor points

= 1, No homogeneous stress/strain is output.

Note

Output for solid laminates and layer by layer output is not supported.

4. Output for superelements that are processed at the monitor point:

• For internal and partitioned superelements, MONPNT2 results can be outputfor the residual or downstream superelements.

• For external superelements, MONPNT2 results are only output for the residualsuperelement.

Note

The various elements defined for a MONPNT2 may not exist for all ofthe superelements in a model. When this occurs, the MONPNT2 is notprocessed for the superelement.

5. Invalid Table, Type, COMP, or EID generates a warning message and is ignored.

6. The software prints the results in a table titled STRUCTURAL INTERNAL MONITOR POINT

LOADS (MONPNT2)


Monitor points


STRESSMONITOR

TABLE

Real Stresses/Strains Complex Stresses or StrainsElement Name(Code) NDDL entity Item NDDL entity Item Real/Mag. or Imag./

Phase

SX1A/EX1A End A-Point C SX1AR/EX1AR End A-Point C RM

SX2A/EX2A End A-Point D SX2AR/EX2AR End A-Point D RM

SX3A/EX3A End A-Point E SX3AR/EX3AR End A-Point E RM

SX4A/EX4A End A-Point F SX4AR/EX4AR End A-Point F RM

AS/AE Axial ASR/AER Axial RM

BMAXA/EBMAXA End A maximum SX1AI/EX1AI End A-Point C lP

BMINA/EBMINA End A minimum SX2AI/EX2AI End A-Point D IP

MST/MST Safety margin intension SX3AI/EX3AI End A-Point E IP

SX1B/EX1B End B-Point C SX4AI/EX4AI End A-Point F IP

SX2B/EX2B End B-Point D ASI/AEI Axial IP

SX3B/EX3B End B-Point E SX1BR/EX1BR End B-Point C RM

SX4B/EX4B End B-Point F SX2BR/EX2BR End B-Point D RM

BMAXB/EBMAXB End B maximum SX3BR/EX3BR End B-Point E RM

BMINB/EBMINB End B minimum SX4BR/EX4BR End B-Point F RM

MSC Safety margin incompression SX1BI/EX1BI End B-Point C IP

SX2BI/EX2BI End B-Point D IP

SX3BI/EX3BI End B-Point E IP

SX4BI/EX4BI End B-Point F IP

CBAR

34

Real Stresses or Strains Complex Stresses or StrainsElement Name(Code) NDDL entity Item NDDL entity Item Real/Mag. or Imag./

Phase

SD StationDistance/Length SD Station

Distance/Length RM

SXC/EXC Point C SXCr/EXCr Point C RM

SXD/EXD Point D SXDr/EXDr Point D RM

SXE/EXE Point E SXEr/EXEr Point E RM

SXF/EXF Point F SXFr/EXFr Point F RM

AS/AE Axial ASr/AEr Axial RM

SMAX/EMAX Maximum SMAXr/EMAXr Maximum RM

SMIN/EMIN Minimum SMINr/EMINr Minimum RM

SXCi/EXCi Point C IP

SXDi/EXDi Point D IP

SXEi/EXEi Point E IP

SXFi/EXFi Point F IP

ASi/AEi Axial IP

SMAXi/EMAXi Maximum IP

CBAR

100

IntermediateStations

MS

Margin of Safety

(NDDL entitys aboveare given for End A.For codes 2 through10 at intermediatestations add (K-1)*9where K is the stationnumber, and for



Monitor points

codes at End B,K=number of stationsplus 1.)

SMINi/EMINi

Minimum

(NDDL entitys aboveare given for End A.For codes 2 through16 at intermediatestations add (K-1)*15where K is the stationnumber, and forcodes at End B,K=number of stationsplus 1.)

IP


Phase

GRID External grid point ID GRID External grid point ID

SD Stationdistance/length SD Station

distance/length

SXC/EXC Long. Stress/Strainat Point C SRCR/ERCR Long. Stress/Strain

at Point C RM

SXD/EXD Long. Stress/Strainat Point D SXDR/EXDR Long. Stress/Strain

at Point D RM

SXE/EXE Long. Stress/Strainat Point E SXER/EXER Long. Stress/Strain

at Point E RM

SXF/EXF Long. Stress/Strainat Point F SXFR/EXFR Long. Stress/Strain

at Point F RM

SMAX/EMAX MaximumStress/Strain SXCI/EXCI Long. Stress/Strain

at Point C IP

SMIN/EMIN MinimumStress/Strain SXDI/EXDI Long. Stress/Strain

at Point D IP

MST Safety margin intension SXEI/EXEI Long. Stress/Strain

at Point E IP

CBEAM

2

Linear Format

MSC

Safety margin incompression

NDDL entitys aregiven for End A.Addition of thequantity (K-1)*10to the NDDL entitypoints to the sameinformation for otherstations, where K isthe station number.K=11 for End B,and K=2 through10 for intermediatestations.

SXFI/EXFI

Long. Stress/Strainat Point F

NDDL entitys aregiven for End A.Addition of thequantity (K-1)*10to the NDDL entitypoints to the sameinformation for otherstations, where K isthe station number.K=11 for End B,and K=2 through10 for intermediatestations.

IP


Phase


Monitor points



CA Circumferentialangle CA Circumferential

angle

SC/EC Long. Stress/Strainat Point C SCR/ECR Long. Stress/Strain

at Point C RM

SD/ED Long. Stress/Strainat Point D SDR/EDR Long. Stress/Strain

at Point D RM

SE/EE Long. Stress/Strainat Point E SER/EER Long. Stress/Strain

at Point E RM

SF/EF Long. Stress/Strainat Point F SFR/EFR Long. Stress/Strain

at Point F RM

SMAX/EMAX MaximumStress/Strain SCI/ECI Long. Stress/Strain

at Point C IP

SMIN/EMIN MinimumStress/Strain SDI/EDI Long. Stress/Strain

at Point D IP

MST Safety margin intension SEI/EEI Long. Stress/Strain

at Point E IP

CBEND

69

MSC

Safety margin incompression

(NDDL entitys aregiven for End A.NDDL entitys 12through 21 point tothe same informationfor end B.)

SFI/EFI

Long. Stress/Strainat Point F

(NDDL entitys aregiven for End A.NDDL entitys 12through 21 point tothe same informationfor End B.)

IP


Phase

TX Translation-x TXR Translation-x R

TY Translation-y TYR Translation-y R

TZ Translation-z TZR Translation-z R

RX Rotation-x RXR Rotation-x R

RY Rotation-y RYR Rotation-y R

RZ Rotation-z RZR Rotation-z R

TXI Translation-x I

TYI Translation-y I

TZI Translation-z I

RXI Rotation-x I

RYI Rotation-y I

CBUSH

102

Linear Format

RZI Rotation-z I


Phase



Monitor points

FE Axial force

UE Axial displacement

VE Axial velocity

AS Axial stress

AE Axial strain

EP

CBUSH1D

40

FAIL


Phase

SR/ER Stress/Strain RMCELAS111 S/E Stress/Strain

SI/EI Stress/Strain IP






Phase

CPX Normal x

SHY Shear y

SHZ Shear z

AU Axial u

SHV Shear v

SHW Shear w

SLV Slip v

CGAP

86

SLP Slip w

Not applicable


Phase

CID Stress coordinatesystem CID Stress coordinate

system

CTYPE Coordinate type(Character) CTYPE Coordinate type

(Character)

NODEF Number of activepoints NODEF Number of active

points

GRID External grid ID(0=center) GRID External grid ID

(0=center)

SX/EX Normal x SXR/EXR Normal x RM

TXY/ETXY Shear xy SYR/EYR Normal y RM

P1/EP1 First principal SZR/EZR Normal z RM

P1X/P1X First principal xcosine TXYR/ETXYR Shear xy RM

P2X/P2X Second principal xcosine TYZR/ETYZR Shear yz RM

P3X/P3X Third principal xcosine TZXR/ETZXR Shear zx RM

CHEXA

67

Linear Format


Monitor points


PR/EPR Mean pressure SXI/EXI Normal x lP

OCT/EOCTvon Mises oroctahedral shearstress

SYI/EYI Normal y IP

SY/EY Normal y SZI/EZI Normal z IP

TYZ/ETYZ Shear yz TXYI/ETXYI Shear xy IP

P2/EP2 Second principal TYZI/ETYZI Shear yz IP

P1Y/P1Y First principal ycosine TZXI/ETZXI Shear zx IP

P2Y/P2Y Second principal ycosine

P3Y/P3Y Third principal ycosine

SZ/EZ Normal z

TZX/ETZX Shear zx

P3/EP3 Third principal

P1Z/P1Z First principal zcosine

P2Z/P2Z Second principal zcosine

P3Z/P3Z Third principal zcosine


Phase

AS/AE Axial Stress/Strain ASR/AER Axial Stress/Strain RM

MSA Axial safety margin ASI/AEI Axial Stress/Strain IP

TS/TE TorsionalStress/Strain TSR/TER Torsional

Stress/Strain RM

CONROD

10

Linear FormatMST Torsional safety

margin TSI/TEI TorsionalStress/Strain IP


Phase


system


(Character)


points

GRID External grid ID GRID External grid ID







PR/EPR Mean pressure SXI/EXI Normal x IP

CPENTA

68

Linear Format



Monitor points

OCT/EOCTvon Mises orOctahedral shearstress

SYI/EYI Normal y IP




P1Y/P1Y First principal ycosine TZXI/ETZXI Shear zx IP

P2Y/P2Y Second principal ycosine

P3Y/P3Y Third principal ycosine

SZ/EZ Normal z

TZX/ETZX Shear zx


P1Z/P1Z First principal zcosine

P2Z/P2Z Second principal zcosine

P3Z/P3Z Third principal zcosine


Phase

SX Normal stress in x SXR Normal stress in x RM

SY Normal stress in y SXI Normal stress in x IP

SZ Normal stress in z SYR Normal stress in y RM

SP In-plane shear stress SYI Normal stress in y IP

SMAX Von Mises stress SZR Normal stress in z RM

SZI Normal stress in z IP

SPR In-plane shear stress RM

CPLSTN3

271

Triangle plane strain

Linear Format

(Center Only)

SPI In-plane shear stress IP


Phase

GRID Grid ID, 0 for centroid GRID Grid ID, 0 for centroid








CPLSTN4

272

Quadrilateral planestrain

Linear Format

(Center and Corners)



Phase


Monitor points










CPLSTN6

273

Triangle plane strain

Linear Format




Phase









CPLSTN8

274

Quadrilateral planestrain

Linear Format




Phase








CPLSTS3

275

Triangle plane stress

Linear Format

(Center Only)



Phase









CPLSTS4

276

Quadrilateral planestress

Linear Format





Monitor points


Phase









CPLSTS6

277

Triangle plane stress

Linear Format




Phase









CPLSTS8

278

Quadrilateral planestress

Linear Format




Phase

CID Stress/Straincoordinate system CID Stress coordinate

system


(Character)


points

GRID External grid ID GRID External grid ID

(0=center) (0=center)








CPYRAM

255

Linear Format


Monitor points



SYI/EYI Normal y IP




P1Y First principal ycosine TZXI/ETZXI Shear zx IP

P2Y Second principal ycosine

P3Y Third principal ycosine

SZ/EZ Normal z

TZX/ETZX Shear zx


P1Z First principal zcosine

P2Z Second principal zcosine

P3Z Third principal zcosine


Phase

FD1 Z1=Fiber Distance 1 FD1 Z1=Fiber Distance 1

SX1/EX1 Normal x at Z1 SX1R/EX1R Normal x at Z1 RM

SY1/EY1 Normal y at Z1 SX1I/EX1I Normal x at Z1 IP

TXY1/EXY1 Shear xy at Z1 SY1R/EY1R Normal y at Z1 RM

SA1/EA1 Shear angle at Z1 SY1I/EY1I Normal y at Z1 IP

SMJRP1/EMJRP1 Major principal at Z1 TXY1R/EXY1R Shear xy at Z1 RM

SMNRP1/EMNRP1 Minor principal at Z1 TXY1I/EXY1I Shear xy at Z1 IP

SMAX1/EMAX1von Mises ormaximum shearat Z1

FD2/FD2 Z2=Fiber distance 2

FD2 Z2=Fiber distance 2 SX2R/EX2R Normal x at Z2 RM

SX2/EX2 Normal x at Z2 SX2I/EX2I Normal x at Z2 IP

SY2/EY2 Normal y at Z2 SY2R/EY2R Normal y at Z2 RM

TXY2/EXY2 Shear xy at Z2 SY2I/EY2I Normal y at Z2 IP

SA2/EA2 Shear angle at Z2 TXY2R/EXY2R Shear xy at Z2 RM

SMJRP2/EMJRP2 Major principal at Z2 TXY2I/EXY2I Shear xy at Z2 IP

SMNRP2/EMNRP2 Minor principal at Z2

CQUAD4

33

Linear Format

Center Only

SMAX2/EMAX2

von Mises ormaximum shearat Z2



Monitor points


Phase

TERM CEN/ TERM CEN/

GRID 4 GRID 4

FD1 Z1-Fiber distance FD1 Z1-Fiber distance



TXY1/ETXY1 Shear xy at Z1 SY1R/EY1R Normal y at Z1 RM

A1 Shear angle at Z1 SY1I/EY1I Normal y at Z1 IP

MJRP1/EMJRP1 Major principal at Z1 TXY1R/ETXY1R Shear xy at Z1 RM

MNRP1/EMNRP1 Minor principal at Z1 TXY1I/ETXY1I Shear xy at Z1 IP

TMAX1/ETMAX1


FD2 Z2-Fiber distance

FD2 Z2-Fiber distance SX2R/EX2R Normal x at Z2 RM



TXY2/ETXY2 Shear xy at Z2 SY2I/EY2I Normal y at Z2 IP

A2 Shear angle at Z2 TXY2R/ETXY2R Shear xy at Z2 RM

MJRP2/EMJRP2 Major principal at Z2 TXY2I/ETXY2I Shear xy at Z2 IP

MNRP2/EMNRP2 Minor principal at Z2

CQUAD144

144

Linear Format

Center and Corners

TMAX2/ETMRP2von Mises ormaximum shearat Z2


Phase

PLY Lamina Number PLY Lamina Number

SX1/EX1 Normal-1 SX1/EX1 Normal-1 RM

SY1/EY1 Normal-2 SY1/EY1 Normal-2 RM

T1/ET1 Shear-12 T1/ET1 Shear-12 RM

SL1/EL1 Shear-1Z SL1/EL1 Shear-1Z RM

SL2/EL2 Shear-2Z SL2/EL2 Shear-2Z RM

A1 Shear angle SX1I/EX1I Normal-1 IP

MJRP1/EMJRP1 Major principal SY1I/EY1I Normal-2 IP

MNRP1/EMNRP1 Minor principal T1I/ET1I Shear-12 IP

TMAX1/ETMAX1 Maximum shear SL1I/EL1I Shear-1Z IP

CQUAD4

95

Composite

Center Only

SL2I/EL2I Shear-2Z IP


Phase


Monitor points


TERM CEN/ TERM CEN/

GRID 4 GRID 4






SMJRP1/EMJRP1 Major principal at Z1 TXY1R/ETXY1R Shear xy at Z1 RM

SMNRP1/EMNRP1 Minor principal at Z1 TXY1I/ETXY1I Shear xy at Z1 IP

TMAX1/ETMAX1








SMJRP2/EMJRP2 Major principal at Z2 TXY2I/ETXY2I Shear xy at Z2 IP


CQUAD8

64

Linear Format

Center and Corners

TMAX2/ETMAX2



Phase

CQUAD896CompositeCenter Only

Same asCQUAD4(95)

Same asCQUAD4(95)

Same asCQUAD4(95)

Same asCQUAD4(95)


Phase

TERM CEN/ TERM CEN/

GRID 4 GRID 4








CQUADR

82

Center and Corners



Monitor points

TMAX1/ETMAX1von Mises ormaximum shearat Z1









TMAX2/ETMRP2von Mises ormaximum shearat Z2


Phase

CQUADR228Center only(not supported by oldformulation)

Same asCQUAD4(33)

Same asCQUAD4(33)

Same asCQUAD4(33)

Same asCQUAD4(33)


Phase

CQUADR232CompositeCenter Only(not supported by oldformulation)

Same asCQUAD4(95)

Same asCQUAD4(95)

Same asCQUAD4(95)

Same asCQUAD4(95)


Phase

CTYPE 0 (Result at Center) CTYPE 0 (Result at Center)

LOC Location LOC Location

SX Radial SXR Radial RM

SY Azimuthal SXI Radial IP

SZ Axial SYR Azimuthal RM

SS Shear stress SYI Azimuthal lP

MAXP Maximum principal SZR Axial RM

TMAX Maximum shear SZI Axial lP

OCTS von Mises oroctahedral SSR Shear stress RM

CQUADX4

243

Linear Format

Center and Corners

Grid and Gauss

SSI Shear stress IP


Phase


Monitor points


CQUADX8245Linear FormatGrid and GaussCenter and Corners

Same asCQUAD4(33)

Same asCQUAD4(33)

Same asCQUAD4(33)

Same asCQUAD4(33)


Phase

CROD1Linear Format

Same asCONROD(10)

Same asCONROD(10)

Same asCONROD(10)

Same asCONROD(10)


Phase

TMAX/ETMAX Maximum shear TMAXR/ETMAXR Maximum shear RM

TAVG/ETAVG Average shear TMAXI/ETMAXI Maximum shear lP

TAVGR/ETAVGR Average shear RM

CSHEAR

4MS Safety margin

TAVGI/ETAVGI Average shear IP


Phase


system


(Character)


points

External grid ID External grid IDGRID

(0=center)GRID

(0=center)




P1X First principal xcosine TXYR/ETXYR Shear xy RM

P2X Second principal xcosine TYZR/ETYZR Shear yz RM

P3X Third principal xcosine TZXR/ETZXR Shear zx RM



SYI/EYI Normal y IP




P1Y First principal ycosine TZXI/ETZXI Shear zx IP

P2Y Second principal ycosine

P3Y Third principal ycosine

CTETRA

39

Linear Format



Monitor points

SZ/EZ Normal z

TZX/ETZX Shear zx


P1Z First principal zcosine

P2Z Second principal zcosine

P3Z Third principal zcosine


Phase

CTRAX3242Linear FormatCenter and CornersGrid or Gauss

Same As CQUADX4(243)





Phase

CTRAX6244Linear FormatGrid and GaussCenter and Corners






Phase

CTRIA374Linear FormatCenter Only

Same asCQUAD4(33)

Same asCQUAD4(33)

Same asCQUAD4(33)

Same asCQUAD4(33)

CTRIA397CompositeCenter Only

Same asCQUAD4(95)

Same asCQUAD4(95)

Same asCQUAD4(95)

Same asCQUAD4(95)


Phase

CTRIA675Linear FormatCenter and Corners

Same asCQUAD8(64)

Same asCQUAD8(64)

Same asCQUAD8(64)

Same asCQUAD8(64)

CTRIA698CompositeCenter Only

Same asCQUAD4(95)

Same asCQUAD4(95)

Same asCQUAD4(95)

Same asCQUAD4(95)


Phase


Monitor points


TERM CEN/ TERM CEN/

GRID 4 GRID 4








TMAX1/ETMAX1










CTRlAR

70

Center and Corners

TMAX2/ETMAX2



Phase

FD1 Z1=Fiber Distance 1 FD1 Z1=Fiber Distance 1



TXY1/EXY1 Shear xy at Z1 SY1R/EY1R Normal y at Z1 RM

SA1/EA1 Shear angle at Z1 SY1I/EY1I Normal y at Z1 IP

SMJRP1/EMJRP1 Major principal at Z1 TXY1R/EXY1R Shear xy at Z1 RM

SMNRP1/EMNRP1 Minor principal at Z1 TXY1I/EXY1I Shear xy at Z1 IP

SMAX1/EMAX1


FD2/FD2 Z2=Fiber distance 2

FD2 Z2=Fiber distance 2 SX2R/EX2R Normal x at Z2 RM



TXY2/EXY2 Shear xy at Z2 SY2I/EY2I Normal y at Z2 IP

SA2/EA2 Shear angle at Z2 TXY2R/EXY2R Shear xy at Z2 RM

CTRlAR

227

Center Only

(not supported by oldformulation)



Monitor points

SMJRP2/EMJRP2 Major principal at Z2 TXY2I/EXY2I Shear xy at Z2 IP


TMAX2/EMAX2



Phase

CTRlAR233CompositeCenter Only(not supported by oldformulation)

Same asCQUAD4(95)

Same asCQUAD4(95)

Same asCQUAD4(95)

Same asCQUAD4(95)


Phase

AS Axial Stress

SE Equivalent Stress

TE Total Strain

EPS Eff Plastic Strain

ECS Eff Creep Strain

CTUBE

3

Linear Format

LTS Linear TorsionalStress


Monitor points


FORCEMONITOR

TABLE

Real Element Forces Complex Element ForcesElement Name Code

NDDL entity Item NDDL entity Item Real/Mag. or Imag/Phase

BM1A Bending End A plane1 BM1AR Bending End A plane

1 RM

BM2A Bending End A plane2 BM2AR Bending End A plane

2 RM

BM1B Bending End B plane1 BM1BR Bending End B plane

1 RM

BM2B Bending End B plane2 BM2BR Bending End B plane

2 RM

TS1 Shear plane 1 TS1R Shear plane 1 RM


AF Axial force AFR Axial force RM

TRQR Torque RM

BM1AI Bending End A plane1 IP

BM2AI Bending End A plane2 IP

BM1BI Bending End B plane1 IP

BM2BI Bending End B plane2 IP

TS1I Shear plane 1 IP


AFI Axial force lP

CBAR

34

TRQ Torque

TRQI Torque IP



SD Station Distance/Length SD Station Distance/

Length RM

BM1 Bending MomentPlane 1 BM1r Bending Moment

Plane 1 RM

BM2 Bending MomentPlane 2 BM2r Bending Moment

Plane 2 RM

TS1 Shear Force Plane 1 TP1r Shear Force Plane 1 RM

TS2 Shear Force Plane 2 TP2r Shear Force Plane 2 RM

AF Axial AFr Axial RM

TRQ Torque TrQR Torque RM

NDDL entitys aregiven for End A.Addition of thequantity (K-1) * 7to the NDDL entitypoints to the sameinformation for otherstations, whereK is the station

BM1i Bending MomentPlane 1 IP

CBAR

100



Monitor points

number. K=8 forEnd B and 2 through7 for intermediatestations.

BM2i Bending MomentPlane 2 IP

TS1i Shear Force Plane 1 IP

TS2i Shear Force Plane 2 IP

AFi Axial IP

Torque

TRQi

(NDDL entitys aboveare given for End A.For codes 2 through14 at intermediatestations add (K-1)* 13 and K is thestation number, andfor codes at End B,K+number of stationsplus 1.)

IP




SD Stationdistance/length SD Station

distance/length

BM1 Bending momentplane 1 BM1R Bending moment

plane 1 RM


plane 2 RM

TS1 Web shear plane 1 TS1R Web shear plane 1 RM

TS2 Web shear plane 2 TS2R Web shear plane 2 RM


TTRQ Total torque TTRQR Total torque RM

WTRQ Warping torque WTRQR Warping torque RM

(NDDL entitys aregiven for End A.Addition of thequantity (K-1) 9to the NDDL entitypoints to the sameinformation for otherstations, where K isthe station number.K=11 for End Band 2 through 10for intermediatestations.)

BM1I Bending momentplane 1 IP


TS1I Web shear plane 1 lP

TS2I Web shear plane 2 IP

AFI Axial force IP

CBEAM

2


Monitor points


TTRQI Total torque IP

WTRQI Warping torque lP

(NDDL entitys aregiven for End A.Addition of thequantity (K-1) 16to the NDDL entitypoints to the sameinformation for otherstations, where K isthe station number.K=11 for End Band 2 through 10for intermediatestations.)



TX Force-x TXR Force-x RM

TY Force-y TYR Force-y RM

TZ Force-z TZR Force-z RM

RX Moment-x RXR Moment-x RM

RY Moment-y RYR Moment-y RM

RZ Moment-z RZR Moment-z RM

TXI Force-x IP

TYI Force-y IP

TZI Force-z IP

RXI Moment-x IP

RYI Moment-y IP

CBEAR

280

RZI Moment-z IP





plane 1 RM


plane 2 RM




Torque TRQR Torque RM





CBEND

69

TRQ



Monitor points


AFI Axial force lP

Torque

TRQi


IP



FX Force-x FXR Force-x RM

FY Force-y FYR Force-y RM

FZ Force-z FZR Force-z RM

MX Moment-x MXR Moment-x RM

MY Moment-y MYR Moment-y RM

MZR Moment-z RM

FXI Force-x IP

FYI Force-y IP

FZI Force-z IP

MXI Moment-x IP

MYI Moment-y IP

CBUSH

102

Linear Format

MZ Moment-z

MZI Moment-z IP



Same asCELAS1(11)

Same asCELAS1(11)

Same asCELAS1(11)

Same asCELAS1(11)

Same asCELAS1(11)

Same asCELAS1(11)

Same asCELAS1(11)

Same asCELAS1(11)

Same asCELAS1(11)

Same asCELAS1(11)

Same asCELAS1(11)

Same asCELAS1(11)

CDAMP120

CDAMP221

CDAMP322

CDAMP423

Same asCELAS1(11)

Same asCELAS1(11)

Same asCELAS1(11)

Same asCELAS1(11)



CDUM3thruCDUM9(55-61)

Same asCELAS1(11)

Same asCELAS1(11)

Same asCELAS1(11)

Same asCELAS1(11)



F Force FR Force RMCELAS1

11 FI Force IP


Monitor points


CELAS212 Same as CELAS1 Same as CELAS1





BM1A mz bending End Aplane 1 BM1AR mz bending End A

plane 1 RM

BM2A my bending End Aplane 2 BM2AR my bending End A

plane 2 RM

BM1B mz bending End Bplane 1 BM1BR mz bending End B

plane 1 RM

BM2B my bending End Bplane 2 BM2BR my bending End B

plane 2 RM

TS1 fy shear force plane1 TS1R fy shear force plane

1 RM

TS2 fz shear force plane2 TS2R fz shear force plane

2 RM

AF fx axial force AFR fx axial force RM

TRQ mx torque TRQR mx torque RM

BM1AI mz bending End Aplane 1 IP

BM2AI my bending End Aplane 2 IP

BM1BI mz bending End Bplane 1 IP

BM2BI my bending End Bplane 2 IP

TS1I fy shear force plane1 IP

TS2I fz shear force plane2 IP

AFI fx axial force IP

CFAST

119

TRQI mx torque IP




AFI Axial force IP

TRQR Torque RM

CONROD

10 TRQ Torque

TRQI Torque lP





Monitor points

MX Membrane force x MXR Membrane force x RM

MY Membrane force y MYR Membrane force y RM

MXY Membrane force xy MXYR Membrane force xy RM

BMX Bending moment x BMXR Bending moment x RM

BMY Bending moment y BMYR Bending moment y RM

BMXY Bending moment xy BMXYR Bending moment xy RM

TX Shear x TXR Shear x RM

TY Shear y TYR Shear y RM

MXI Membrane force x IP

MYI Membrane force y IP

MXYI Membrane force xy IP

BMXI Bending moment x IP

BMYI Bending moment y IP

BMXYI Bending moment xy IP

TXI Shear x IP

CQUAD4

33

Center Only

TYI Shear y IP



TERM CEN/ TERM CEN/

GRID 4 GRID 4

MX Membrane x MXR Membrane x RM

MY Membrane y MYR Membrane y RM

MXY Membrane xy MXYR Membrane xy RM

BMX Bending x BMXR Bending x RM

BMY Bending y BMYR Bending y RM

BMXY Bending xy BMXYR Bending xy RM

TX Shear x TXR Shear x RM

TY Shear y TYR Shear y RM

MXI Membrane x IP

MYI Membrane y IP

MXYI Membrane xy IP

BMXI Bending x IP

BMYI Bending y IP

BMXYI Bending xy IP

TXI Shear x IP

CQUAD4

144

Center and Corners

TYI Shear y IP



CQUAD864Center and Corners

Same asCQUAD144(144)





Monitor points




CQUADR82Center and Corners





CQUADR228Center Only(not supported by oldformulation)

Same asCQUAD4(33)

Same asCQUAD4(33)

Same asCQUAD4(33)

Same asCQUAD4(33)



CROD1

Same asCONROD(10)

Same asCONROD(10)

Same asCONROD(10)

Same asCONROD(10)



F41 Force 4 to 1 F41R Force 4 to 1 RM








KF1 Kick force on 1 F41I Force 4 to 1 IP

S12 Shear 12 F21I Force 2 to 1 lP


S23 Shear 23 F32I Force 3 to 2 IP

KF3 Kick force on 3 F23I Force 2 to 3 lP




KF1R Kick force on 1 RM

S12R Shear 12 RM


S23R Shear 23 RM


S34R Shear 34 RM


S41R Shear 41 RM

KF1I Kick force on 1 IP

S12I Shear 12 lP


S23I Shear 23 IP

CSHEAR

4



Monitor points


S34I Shear 34 IP


S41I Shear 41 IP



CTRIA374Center Only

Same asCQUAD4(33)

Same asCQUAD4(33)

Same asCQUAD4(33)

Same asCQUAD4(33)

CTRlA675Center and Corners







CTRIAR70Center and Corners





CTRIAR227Center Only(not supported by oldformulation)

Same asCQUAD4(33)

Same asCQUAD4(33)

Same asCQUAD4(33)

Same asCQUAD4(33)




AFI Axial force IP

TRQR Torque RM

CTUBE

3 TRQ Torque

TEQI Torque lP



CVlSC24

Same asCONROD(10)

Same asCONROD(10)

Same asCONROD(10)

Same asCONROD(10)



BM1A mz bending End Aplane 1 BM1AR mz bending End A

plane 1 RM

BM2A my bending End Aplane 2 BM2AR my bending End A

plane 2 RM

BM1B mz bending End Bplane 1 BM1BR mz bending End B

plane 1 RM

BM2B my bending End Bplane 2 BM2BR my bending End B

plane 2 RM

TS1 fy shear force plane1 TS1R fy shear force plane

1 RM

TS2 fz shear force plane2 TS2R fz shear force plane

2 RM

AF fx axial force AFR fx axial force RM

CWELDP (118)ELPAT or PARTPAT

CWELDC (117)ELIMID or GRIDIDwith MSET=OFF

CWELD (200)ELIMID or GRIDIDwith MSET=ON


Monitor points


TRQ mx torque TRQR mx torque RM

BM1AI mz bending End Aplane 1 IP

BM2AI my bending End Aplane 2 IP

BM1BI mz bending End Bplane 1 IP

BM2BI my bending End Bplane 2 IP

TS1I fy shear force plane1 IP

TS2I fz shear force plane2 IP

AFI fx axial force IP

TRQI mx torque IP



Monitor points

MONPNT3

Integrated Load Monitor Point — Sums Grid Point Forces

Defines an integrated load monitor point at a chosen point and sums select grid pointforces for SOL 101 and SOL 103.

FORMAT:

1 2 3 4 5 6 7 8 9 10

MONPNT3 NAME LABEL

AXES GRIDGRP ELEMGRP CP X Y Z XFLAG

CD

EXAMPLE:

MONPNT3 MPT33 This is a MONPNT3 monitor point.

246 1001 2002 1.0 2.0 3.0 MD

1003

FIELDS:

Field Contents

NAME A unique character string that identifies the monitor point. (Character; 8characters maximum; No default)

LABEL A string that identifies and labels the monitor point. (Character; 56characters maximum; Optional)

AXES Component axes about which to sum. (Integer; Any unique combinationof the integers 1 through 6 with no embedded blanks; No default)

GRIDGRPGROUP entry that has a list of grids to be included in the monitor point.(Integer; No default). See Remark 1.

ELEMGRPGROUP entry that has a list of elements to process at the monitor point.(Integer; Optional). See Remark 2.

CP The identification number of a coordinate system in which the X, Y, and Zcoordinates are defined. (Integer; Default = 0; Optional). See Remark 5.

X, Y, Z The coordinates in the CP coordinate system about which the forces areto be summed. (Real; Default = 0.0).


Monitor points


Field Contents

XFLAG Exclusion flag excludes the indicated Grid Point Force types fromsummation at the monitor point. (Default = blank (no type excluded)).

If XFLAG = "S", SPC forces are excluded.

If XFLAG = "M", MPC forces are excluded.

If XFLAG = "A", "L", or "P", applied loads, which includes thermal loads,are excluded.

If XFLAG = "D", DMIGs at the monitored point are excluded.

CD The identification number of a coordinate system in which the resultsare output. (Integer ≥ 0; Default = Coordinate system specified by theCP field)

REMARKS:1. Requirements for grids that are included in the monitor point:

• You select a set of grids to sum forces and moments about the specified point.

• You must use only GRIDs in the GROUP definition. MONPNT3 does notprocess SPOINTs, EPOINTs, and fluid grid points when they are in theGROUP definition.

2. Requirements for elements that are processed at the monitor point:

• When ELEMGRP is defined for any MONPNT3 bulk entry, you must definethe GPFORCE=ALL case control command for all subcases, and the requestmust be for the SORT1 output format. You must either define GPFORCE=ALLin each subcase, or above the subcases (globally). When ELEMGRP is blank,no contributions are made from the set of elements attached to the grid. Theelements attached to the grid are excluded.

3. Output for superelements that are processed at the monitor point:

• For internal and partitioned superelements, MONPNT3 results can be outputfor the residual or downstream superelements.

• For external superelements, MONPNT3 results are only output for the residualsuperelement.

Note

The various GROUPs and CPs defined for a MONPNT3 may notexist for all of the superelements in a model. When this occurs, theMONPNT3 is not processed for the superelement. A warning messageindicates that the MONPNT3 is not processed.

4. Invalid grids or elements do not generate error or warning messages.



Monitor points

5. A CP of zero (the default) references the basic coordinate system.

6. In a structure, you can apply MONPNT3 to determine the internal shear, moment,torque, and thermal loads.

Example

A long and slender component is divided and all grids that reside on thedivision are placed in the GRIDGRP group. Based on the values of theELEMGRP and XFLAG fields, the software outputs various internalload resultants.

• ELEMGRP contains all elements connected to the GRIDGRP onthe outer part of the split:

o XFLAG is blank:

The software calculates the internal load with the elementsconnected to the GRIDGRP that are not included in ELEMGRP.This produces resultants on the inside of the split and containsany loads applied to the GRIDGRP from any other source.

o XFLAG = SMAD:

The software calculates the internal load with the elementslisted in ELEMGRP. This produces resultants on the outer partof the split and does not contain loads applied to the GRIDGRPfrom any other source.

7. The software prints the results in a table titled STRUCTURAL INTEGRATED FREE BODY

MONITOR POINT LOADS (MONPNT3). The total loads in this table include the thermalloads unless you set XFLAG = A.


Monitor points


MONITOR

Print Selection for Monitor Data

Requests the type of monitor data to be output to the .f06 file in SOL 101 and SOL 103.FORMAT:

EXAMPLES:MONITOR(NOPNT2) = ALL

DESCRIBERS:

Describer Meaning

NOPNT2 Do not include MONPNT2 results in the MONITOR pointprints. (Default = Provide these prints)

NOPNT3 Do not include MONPNT3 results in the MONITOR pointprints. (Default = Provide these prints)

ALL or YES Print all monitor point results except for the selected items.

NONE or NO Do not print the monitor point results. (Default)

REMARKS:1. The MONITOR command is required to obtain MONITOR results in the printed

output.

Monitor points example

Test problem descriptionIn this test problem, the physical problem represents a beam model with a rectangular section. Thebeam starts at 1 meter long, fixed at one end or two ends, and at –50° C is heated to 25° C.

The objective is to define an integrated load monitor point at a named element and output strain andstress, and to sum grid point forces around a specific point.

Executive and case controlTwo subcase runs with different restraints (one end fixed and two ends fixed) that use the samemodel are used to investigate the effects of different supports. In both cases, the MONITOR casecontrol command requests monitor points information. In both subcases, MONITOR requeststo print all monitor results.

Bulk dataThe key data in the Bulk Data section is as follows:

• SPC cards are used to restrain the model at one or two ends.

• A thermal load of 25° C is applied at all grid points of the bar model.



Monitor points

• MONPNT2 outputs EX1A (strain at end A at point C) and SX1A (bending stress at end A at therecovery location C).

• MONPNT3 sums the grid point forces at the first grid point around all six component axes in thebasic coordinate system.

Results from NX Nastran

Partial output shows Monitor point tables

Note

REST. APPLIED stands for Resultant Applied Load. Each Resultant Applied Load valuerepresents a sum of all the loads at the specified location in a specific direction.

Input file$*$* NX NASTRAN$*$* ANALYSIS TYPE: Structural$* SOLUTION TYPE: SOL 101 Linear Statics - Subcase Constraints$* SOLVER INPUT FILE: monitor-points.dat$*$*$*$* UNITS: SI-Meter (newton)$* ... LENGTH : meter$* ... TIME : sec$* ... MASS : kilogram (kg)$* ... FORCE : newton(N)$* ... TEMPERATURE : deg Celsius$*$*$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$*$* EXECUTIVE CONTROL$*


Monitor points


$*$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$*SOL 101TIME 60CEND$*$*$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$*$* CASE CONTROL$*$*$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$*TITLE = monitor-points - Thermal Strain, Displacement, and Stress on Heated BeamECHO = SORT$*TEMP(INIT) = 1$*SUBCASE = 1$*LABEL = One End FixedSPC = 1TEMP(LOAD) = 10DISPLACEMENT(PRINT,PUNCH) = ALLSPCFORCES(PRINT,PUNCH) = ALLFORCE(PRINT,PUNCH,CORNER) = ALLSTRESS = ALLSTRAIN(PRINT,PUNCH,CORNER,VONMISES,STRCUR) = ALLESE(PRINT,PUNCH) = ALLMONITOR = ALL$*SUBCASE = 2$*LABEL = Both Ends FixedSPC = 2TEMP(LOAD) = 10DISPLACEMENT(PRINT,PUNCH) = ALLSPCFORCES(PRINT,PUNCH) = ALLFORCE(PRINT,PUNCH,CORNER) = ALLSTRESS = ALLSTRAIN(PRINT,PUNCH,CORNER,VONMISES,STRCUR) = ALLESE(PRINT,PUNCH) = ALLMONITOR = ALL$*$*$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$*$* BULK DATA$*$*$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$*BEGIN BULK$*$* PARAM CARDS$*PARAM XFLAG 0PARAM AUTOSPC YESPARAM GRDPNT -1



Monitor points

PARAM POST -2PARAM POSTEXT YES$*$* GRID CARDS$*GRID 1 0 0.0 0.0 0.0 0GRID 2 0 .100000 0.0 0.0 0GRID 3 0 .200000 0.0 0.0 0GRID 4 0 .300000 0.0 0.0 0GRID 5 0 .400000 0.0 0.0 0GRID 6 0 .500000 0.0 0.0 0GRID 7 0 .600000 0.0 0.0 0GRID 8 0 .700000 0.0 0.0 0GRID 9 0 .800000 0.0 0.0 0GRID 10 0 .900000 0.0 0.0 0GRID 11 0 1.00000 0.0 0.0 0$*$* ELEMENT CARDS$*CBAR 1 1 1 2 0.01.000000 0.0CBAR 2 1 2 3 0.01.000000 0.0CBAR 3 1 3 4 0.01.000000 0.0CBAR 4 1 4 5 0.01.000000 0.0CBAR 5 1 5 6 0.01.000000 0.0CBAR 6 1 6 7 0.01.000000 0.0CBAR 7 1 7 8 0.01.000000 0.0CBAR 8 1 8 9 0.01.000000 0.0CBAR 9 1 9 10 0.01.000000 0.0CBAR 10 1 10 11 0.01.000000 0.0$*$* MATERIAL CARDS$*$* Material: 1 name: MATERIAL PROPERTY TABLE1MAT1 1206.80+9 .29000007820.0001.2000-5 0.0++ 1.5000+91.5000+96.8000+7$*$* PROPERTY CARDS$*$*$* Property: 1 name: PHYSICAL PROPERTY TABLE1$* Fore Section: 2 name: RECTANGLE 0.1 X 0.1PBAR 1 11.0000-28.3333-68.3333-61.4083-5 ++ .0500000.0500000.0500000-.050000-.050000-.050000-.050000.0500000++ .8333333.8333333$*$* RESTRAINT CARDS$*SPC 1 1 123456 0.0$*$* RESTRAINT CARDS$*SPC 2 1 123456 0.0SPC 2 11 123456 0.0$*$* TEMPERATURE CARDS$*


Monitor points


TEMP 10 125.00000 225.00000 325.00000TEMP 10 425.00000 525.00000 625.00000TEMP 10 725.00000 825.00000 925.00000TEMP 10 1025.00000 1125.00000TEMPD 1 -50.000$*$1.....12......23......34......45......56......67......78......89......9+MONPNT2 LOCA testing1

STRAIN CBAR EX1A 1STRESS CBAR SX1A 1

MONPNT3 A1123456 1 0 0.0 0.0 0.00

$1.....12......23......34......45......56......67......78......89......9+GROUP 1

GRID 1ENDDATA



Chapter 12: Miscellaneous

HDF5 format output filesYou can now write results to output files in the open-source HDF5 format. The HDF5 format allowsyou to more easily access and use NX Nastran results in your own utilities.

For example, an airframe business might have a proprietary failure criteria that needs to be evaluatewith in-house software. To use its utility, the analyst needs to access the stress results from the NXNastran run. For such a case, the HDF5 format offers the following advantages:

• It uses a hierarchical data format that is specifically designed to handle large amounts of data.

• Application programming interfaces (API) are readily available to read HDF5 files.

The standard OP2 file, although widely recognized by many Pre/Post tools, is not ideally suitedfor such applications for the following reasons:

• OP2 files use a serial file format, which may force the utility to read through the entire OP2file to recognize the structure of the OP2 file.

• Although an API that reads OP2 files written by NX Nastran is supplied with your NX Nastraninstallation, this API may not be able to read OP2 files written by other solvers.

Note

For information on the API supplied with your NX Nastran installation, see "Buildingand Using TABTST" in the NX Nastran 12 Installation and Operations Guide.

For NX Nastran 12, not all of the data blocks that the software writes to the OP2 file are written to theHDF5 file. The data blocks that are written to the HDF5 file are as follows:

Data block Description

BOUGV1 Table of displacement, velocity and acceleration in basiccoordinate system in SORT1 format

CSTM Table of coordinate system transformation matricesEPT Table of bulk entry images related to element properties (1)

GEOM1 Table of bulk entry images related to geometry

GEOM2 Table of bulk entry images related to element connectivity andscalar points (2)

IBULKOP2 Echo of bulk data input dataICASEOP2 Echo of case control input dataMPT Table of bulk entry images related to material properties (3)

OEE Output element energy (strain, kinetic, loss)OEF1 Table of element forces in SORT1 format



Data block DescriptionOES1 Table of element stresses or strains in SORT1 formatOGF Table of grid point forces

OQG1 Table of single-point or multi-point constraint forces in SORT1format

OSTR1 Table of total strain in SORT1 formatOSTR1TH Table of thermal strain in SORT1 formatOSTR1EL Table of elastic strain in SORT1 format

OUGV1 Table of displacement, velocity and acceleration in globalcoordinate system in SORT1 format

(1) Data from MATCID, NSM, NSML, NSML1, PBUSH1D, PCOMP, and PGPLSN is not supported.(2) Data from CFAST, CQUADRN, CTRIARN, and GENEL is not supported.(3) Data from MATCRP, MUMAT, NLARCL, NLCNTL, PLCYISO, RADBND, RADM, and RADMT isnot supported.

The variable names in an HDF5 file match those in the data definition language (DDL) schema. Tofind descriptions of the variables, see the DMAP Programmer's Guide.

To request that the software write the results to an HDF5 format output file in addition to the standardOP2 file, specify the following:

• SYSTEM(653) = 1

• PARAM,POST,-2

Note

For PARAM,POST,-2, OMACHPR=NO is the default. However, the software onlywrites data blocks in the current format to the HDF5 format output file, not the pre-MSCNastran Version 69 or pre-MSC Nastran 2001 formats. Normally, you need to specifyOMACHPR=YES to have the software write the data blocks in the current formatwhen PARAM,POST,-2.

The file extension for HDF5 format output files is .hdf.

Visualization elementsYou can now use eight new shell and solid visualization elements to model geometry without addingphysical effects such as mass, stiffness, and damping to the FE model. In earlier versions of NXNastran, the one-dimensional PLOTEL element is the only visualization element.

The new visualization elements are as follows:

Visualization Element DescriptionPLOTEL3 Triangular visualization element with three grid pointsPLOTEL4 Quadrilateral visualization element with four grid pointsPLOTEL6 Triangular visualization element with six grid pointsPLOTEL8 Quadrilateral visualization element with eight grid points



Miscellaneous

Visualization Element Description

PLOTHEX Six-sided hexahedron visualization element with eight to twentygrid points

PLOTPEN Five-sided pentahedron visualization element with six to fifteengrid points

PLOTPYR Five-sided pyramid visualization element with five to thirteen gridpoints

PLOTTET Four-sided tetrahedron visualization element with four to ten gridpoints

Typically, you use visualization elements in substructuring applications where the underlying FEmesh of the substructure is unavailable. For such situations, you can create a mesh of visualizationelements from the grid points associated with the substructure. Because the mesh is a geometricrepresentation of the substructure, you can display the analysis results across the entire model inpost-processing.

As an example, consider the following application where you also use the new direct-input,frequency-dependent component capability.

Suppose you want to perform a frequency response analysis on an airframe and you want to:

• Use frequency response test results to define the dynamic stiffness of the wings.

• Use FE to model the remainder of the airframe.

• Visualize the analysis results over the entire airframe.

You can use the new direct-input, frequency-dependent component capability to define the dynamicstiffness matrix of the wings from the test results. To do so, include an FRFSTIF bulk entry for eachwing. Each FRFSTIF bulk entry defines the dynamic stiffness matrix of a wing as seen by the DOFthat connect the wing to the fuselage.

You can define an output transformation matrix that relates the response at other points on the wingwhere test data is collected to the DOF that connect the wing to the fuselage. To do so, define gridpoints at these locations on the wings and include an FRFOTM bulk entry for each wing. EachFRFOTM bulk entry relates the response at these grid points to the response of the DOF that connectthe wing to the fuselage.

During the frequency response analysis solve, the software computes the response at the DOF thatconnect the wings to the fuselage. During results recovery, the software uses the response at theseDOF and the FRFOTM bulk entries to calculate the response at the other grid points on the wing.

To view the response of the entire airframe, the post-processor requires a geometric representationof the wing. You can use the new visualization elements and the grid points on the wings to createmeshes of the wings over which the post-processor can display results.

For more information on direct-input, frequency-dependent components, see Direct-input,frequency-dependent components.

For more information on output transformation matrices, see Output transformation matrices forfrequency response analysis.


Miscellaneous


PLOTEL3

Triangular Visualization Element

Defines the connectivity of a triangular visualization element with three grid points foruse in post-processing.

FORMAT:

1 2 3 4 5 6 7 8 9 10PLOTEL3 EID G1 G2 G3

EXAMPLE:

PLOTEL3 29 35 16 42

FIELDS:

Field Contents

EID Element identification number. (Integer > 0)

Gi Grid point identification numbers of connection points. (Integer > 0; AllGi must be unique)

REMARKS:1. The element connectivity is the same as a CTRIA3 element.

2. Element identification numbers should be unique with respect to all other PLOTibulk entries.

3. Grid point IDs G1 through G3 are mandatory.



Miscellaneous

PLOTEL4

Quadrilateral Visualization Element

Defines the connectivity of a quadrilateral visualization element with four grid points foruse in post-processing.

FORMAT:

1 2 3 4 5 6 7 8 9 10PLOTEL4 EID G1 G2 G3 G4

EXAMPLE:

PLOTEL4 29 35 16 42 23

FIELDS:

Field Contents



REMARKS:1. The element connectivity is the same as a CQUAD4 element.


3. Grid point IDs G1 through G4 are mandatory.


Miscellaneous


PLOTEL6

Triangular Visualization Element

Defines the connectivity of a triangular visualization element with three to six gridpoints for use in post-processing.

FORMAT:

1 2 3 4 5 6 7 8 9 10PLOTEL6 EID G1 G2 G3 G4 G5 G6

EXAMPLE:

PLOTEL6 29 35 16 42 23 57 39

FIELDS:

Field Contents



REMARKS:1. The element connectivity is the same as a CTRIA6 element.


3. Grid point IDs G1 through G3 are mandatory. Grid point IDs G4 through G6 areoptional.



Miscellaneous

PLOTEL8

Quadrilateral Visualization Element

Defines the connectivity of a quadrilateral visualization element with five to eight gridpoints for use in post-processing.

FORMAT:

1 2 3 4 5 6 7 8 9 10PLOTEL8 EID G1 G2 G3 G4 G5 G6 G7

G8

EXAMPLE:

PLOTEL6 29 35 16 42 23 57 39 45

48

FIELDS:

Field Contents



REMARKS:1. The element connectivity is the same as a CQUAD8 element.


3. Grid point IDs G1 through G4 are mandatory. Grid point IDs G5 through G8 areoptional.


Miscellaneous


PLOTHEX

Six-Sided Hexahedron Visualization Element

Defines the connectivity of a six-sided hexahedron visualization element with eight totwenty grid points for use in post-processing.

FORMAT:

1 2 3 4 5 6 7 8 9 10PLOTHEX EID G1 G2 G3 G4 G5 G6 G7

G8 G9 G10 G11 G12 G13 G14 G15

G16 G17 G18 G19 G20

EXAMPLE:

PLOTHEX 29 35 16 42 23 57 39 44

73 65 61 47 33 64 32 49

36 51 19 12 45

FIELDS:

Field Contents



REMARKS:1. The element connectivity is the same as a CHEXA element.


3. Grid point IDs G1 through G8 are mandatory. Grid point IDs G9 through G20are optional.



Miscellaneous

PLOTPEN

Five-Sided Pentahedron Visualization Element

Defines the connectivity of a five-sided pentahedron visualization element with six tofifteen grid points for use in post-processing.

FORMAT:

1 2 3 4 5 6 7 8 9 10PLOTPEN EID G1 G2 G3 G4 G5 G6 G7

G8 G9 G10 G11 G12 G13 G14 G15

EXAMPLE:

PLOTPEN 29 35 16 42 23 57 39 44

73 65 61 47 33 64 32 49

FIELDS:

Field Contents



REMARKS:1. The element connectivity is the same as a CPENTA element.




Miscellaneous


PLOTPYR

Five-Sided Pyramid Visualization Element

Defines the connectivity of a five-sided pyramid visualization element with five tothirteen grid points for use in post-processing.

FORMAT:

1 2 3 4 5 6 7 8 9 10PLOTPEN EID G1 G2 G3 G4 G5 G6 G7

G8 G9 G10 G11 G12 G13

EXAMPLE:

PLOTPEN 29 35 16 42 23 57 39 44

73 65 61 47 33 64

FIELDS:

Field Contents



REMARKS:1. The element connectivity is the same as a CPYRAM element.





Miscellaneous

PLOTTET

Four-Sided Tetrahedron Visualization Element

Defines the connectivity of a four-sided tetrahedron visualization element with four toten grid points for use in post-processing.

FORMAT:

1 2 3 4 5 6 7 8 9 10PLOTTET EID G1 G2 G3 G4 G5 G6 G7

G8 G9 G10

EXAMPLE:

PLOTTET 29 35 16 42 23 57 39 44

73 65 61

FIELDS:

Field Contents



REMARKS:1. The element connectivity is the same as a CTETRA element.



Separate mechanical and thermal strainWhen you use the STRAIN command in the linear solutions 101, 103, 105, 107-112, you arerequesting the total strain which includes both mechanical and thermal strain.

You can now request the mechanical and thermal strains separately for the shell and solid elementslisted below.

• ELSTRN case control command - requests the mechanical strain only.

• THSTRN case control command - requests the thermal strain only.

• STRAIN case control command - requests the total strain which includes both the mechanicaland thermal strain.

ELSTRN and THSTRN element support for linear solutions


Miscellaneous


• For SOL 101, ELSTRN and THSTRN are supported for the shell elements CQUAD4, CTRIA3 ,CQUAD8, CTRIA6, CTRIAR, and CQUADR that reference a PSHELL, PCOMP or PCOMPGentry, and the 3D solid elements CTETRA, CHEXA, CPENTA and CPYRAM that reference aPSOLID entry.

• For a static subcase in SOLs 103, 105, 107-112, ELSTRN and THSTRN are supported for theshell elements CQUAD4, CTRIA3 , CQUAD8, CTRIA6, CTRIAR, and CQUADR that referencea PSHELL entry, and the 3D solid elements CTETRA, CHEXA, CPENTA and CPYRAM thatreference a PSOLID entry. ELSTRN and THSTRN are ignored in a non-static subcase.

Modal stress calculation when TEMPERATURE(LOAD) is specifiedIn SOL 103, 110, 111, and 112 when TEMPERATURE(LOAD) is specified, the software now calculatesmodal stresses from the total strain for all elements. Thus, Remark 10 on the TEMPERATURE casecontrol command is removed. In earlier versions, the software calculates modal stresses from theelastic strain for CBEAM, CPLSTSi, CPLSTNi, CPYRAM, and, when used to model a compositesolid, CHEXA and CPENTA elements.

P-elements in SOL 200Beginning in NX Nastran 12, the p-element method has been removed from SOL 200. Attempting torun SOL 200 with p-elements will now cause a fatal error.

The p-element method is still available in the software, except for SOL 200. The p-elementdocumentation was removed in NX Nastran 11.



Chapter 13: Documentation changes

Removing documentation for legacy acoustic absorber and barrierelementsThe following bulk entries are removed from the documentation:

• CHACAB acoustic absorber element

• CHACBR acoustic barrier element

• PACABS acoustic absorber property

• PACBAR acoustic barrier property

Although these bulk entries are still supported in the software, you cannot use them with the newacoustics implementation that began in NX Nastran 11.

Removing documentation for the legacy VECTOR case controlcommandThe VECTOR case control command is now removed from the documentation.

If you run a legacy input file that contains the VECTOR case control command, the software treats theVECTOR case control command specification the same as it treats an equivalent DISPLACEMENTcase control command specification.

For example, suppose a legacy input file contains the following VECTOR specification:

VECTOR(SORT2,PUNCH,REAL)=ALL

When you run the legacy input file in NX Nastran 12, the software treats the VECTOR specificationthe same as the following DISPLACEMENT specification:

DISPLACEMENT(SORT2,PUNCH,REAL)=ALL


Chapter 14: Upward compatibility

Updated data blocks

CASECC

Updated Record - REPEAT

Word Name Type Description

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

309 GCTOPG I Grid contributions TOPG (GRDCON)

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

312 GCGRID I Grid contributions GRID (GRDCON)

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

421 PRSSET I Pressure output set (PRESSURE)

422 PRSMEDIA I Pressure output media (PRESSURE)

423 PRSFMT I Pressure output format (PRESSURE)

424 FRFIN I FRFIN set number

425 PRSTOTAL I Pressure output: total bit(0)=0, scatter bit(0)=0

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

433 ACTLDSET I Acoustic load set (ALOAD)

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

509 ATVFSID I SID of ATVF

510 ATVUNIT I ATVOUT OP2 unit

511 ATVSETNO I ATVOUT microphone set identification number

512 ATVFLAGS I ATVOUT bits for flags = 1 if ATVOUT specified

513 ACPANEL I PANEL in ACPOWER: 0 for none, -1 for all, >0for panel identification number

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




561 INITSSET I Initial stress/strain: INITS=n where n=0 fornone, n>0 for INITS or INITADD bulk entrySID, n<0 for invalid value

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

573 MPINTSET I Microphone point intensity, output set(ACINTENSITY)

574 MPINTDIA I Microphone point intensity, output media(ACINTENSITY)

575 MPINTFMT I Microphone point intensity, output format(ACINTENSITY)

576 OTMFORC I Output set (OTMFORC)

577 OTMFORCM I Output media (OTMFORC)

578 OTMFORCF I Output format (OTMFORC)

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

599 GRDCON I Grid contributions set

600 GCMEDIA I Grid contributions media

601 GCFMT I Grid contributions format

602 GCFORM I Grid contributions FORM

603 GCSOL I Grid contributions SOLUTION

604 INITSOFF I Initial strain offset for balanced initialstress/strain: INITS(OFFSET)=n where n=0for none, n>0 for INITS or INITADD bulk entrySID, n<0 for invalid value

605 INPWRGST I Incident acoustic power, GROUP output set(INPOWER)

606 INPWRFST I Incident acoustic power, FACES output set(INPOWER)

607 INPWRDIA I Incident acoustic power, output media(INPOWER)

608 INPWRFMT I Incident acoustic power, output format(INPOWER)



Upward compatibility


609 TRPWRGST I Transmitted acoustic power, GROUP outputset (TRPOWER)

610 TRPWRAST I Transmitted acoustic power, AMLREG outputset (TRPOWER)

611 TRPWRDIA I Transmitted acoustic power, output media(TRPOWER)

612 TRPWRFMT I Transmitted acoustic power, output format(TRPOWER)

613 TRLOSFLG I Acoustic transmission loss, YES/NO flag(1=yes, 0=no) (TRLOSS)

614 TRLOSDIA I Acoustic transmission loss, output media(TRLOSS)

615 TRLOSFMT I Acoustic transmission loss, output format(TRLOSS)

616 NLARCST I SOL 401 nonlinear arc-length solution flag setIF (NLARCL)

617 IMPRFST I SOL 401 imperfection set flag, SET IF(IMPERF)

618 MONPNT I MONPNTn output bit flag(s)

619 FRFOUT I Frequency-dependent component output flag(FRFOUT)

620 FRFOPT I Frequency-dependent component outputoptions (FRFOUT)

621 FRFSEID I SEID for frequency-dependent componentoutput (FRFOUT)

622 FRFOP2 I Unit for frequency-dependent componentoutput (FRFOUT)

623 UNDEF(577) None

LCC LSEM(C) I Number of symmetry subcase coefficientsfrom item SYMFLG

The value for LCC is set by word 166

LCC+1 COEF RS Symmetry subcase coefficients (SUBSEQ orSYMSEQ)





Word LCC+1 repeats LSEM times

LCC+2 SETID I Set identification number

LCC+3 SETLEN(C) I Length of this set

LCC+4 SETMEM I Set member identification number

Word LCC+4 repeats SETLEN times

Words LCC+2 through LCC+4 repeat NSETS times

LCC+5 PARA CHAR4 Hard-coded to "PARA"

LCC+6 PARLEN(C) I Length of this parameter value specification

LCC+7 CHTYPE(C) I Character type flag: 3 means character, 2otherwise

LCC+8 PARAM(2) CHAR4 Hard-coded to "PARA" and "M "

LCC+10 PNAME(2) CHAR4 Name of parameter

PARLEN =8 Length

LCC+12 INTEGER I Integer value

PARLEN =9 Real-double parameter value

LCC+12 TYPE I Real type - hard-coded to -4

LCC+13 REAL RD Real-double value

PARLEN =10 Complex-single parameter value

LCC+12 RTYPE I Real part type - hard-coded to -2

LCC+13 REAL RS Real part value

LCC+14 ITYPE I Imaginary part type - hard-coded to -2

LCC+15 IMAG RS Imaginary part value

PARLEN =12 Complex-double parameter value

LCC+12 RTYPE I Real part type - hard-coded to -4

LCC+13 REAL RD Real part value

LCC+14 ITYPE I Imaginary part type - hard-coded to -4

LCC+15 IMAG RD Imaginary part value





End PARLEN

Words LCC+5 through max repeat until NANQ occurs

Words LCC+5 through LCC+15 repeat until End of Record

Updated Record - NOTES

Note 13 is removed.

CONTACT

New Record – ATVFS(6571,65,657)


1 OPTION I 0 = set, 1 = ALL

2 BID I BSURFS identification number

3 -1 I Delimiter

New Record – ACTRAD(5907,60,654)


1 SID I Identification number

2 PID I Identification number of PACTRAD bulk entry

3 BIDS I Source BSURFS bulk entry identification number

4 BIDT I Target BSURFS bulk entry identification number

5 AREA RS Area correction factor

6 SDIST RS Search distance

7 ANGLE RS Tolerance angle

8 UNDEF(3) None

New Record – BCTPAR2(6621,66,662)

Same as BCTPARA(7610,76,593)




New Record – PACTRAD(6581,61,658)


1 PID I Parameter identification number

2 METHOD I Method to define the parameters: 0 for six, 1 for four

3 A1R RS Real part of parameter 1

4 TIDA1R I TABLEDi ID of real part of parameter 1

5 A1I RS Imaginary part of parameter 1

6 TIDA1I RS TABLEDi ID of imaginary part of parameter 1

























27 UNDEF(4) None

DIT

New Record - TABLED6(1605,16,117)


1 ID I Table identification number

2 TYPE I Type of table data: =0 for real/imaginary; =1 formagnitude/phase

3 FLAG I Extrapolation on/off flag

4 UNDEF(5) None

9 X RS X value (frequency in Hz)

10 YR RS Y real or magnitude value

11 YI RS Y imaginary or phase value (phase in degrees)

Words 9 through 11 repeat until (-1,-1,-1) occurs

New Record – TABLEM5(505,5,644)


1 ID I Table identification number

2 UNDEF(2) None

4 FLAG I Extrapolation on/off flag

5 UNDEF(4) None

9 X RS X tabular value

10 Y RS Y tabular value

Words 9 through 10 repeat until (-1,-1) occurs




DSCMCOL

New RTYPE=17


RTYPE =17 Compliance

4 UNDEF(2) None

6 SUBCASE I Subcase identification number

7 UNDEF(3) None

DYNAMIC

New Record – ACADAPT(9407,94,659)

Adaptation rule for FEM Adaptive Order solution


1 RULE(2) CHAR4 STANDARD, COARSE, or FINE

3 E1 I Element identification number (for future use)

Word 3 repeats until -1 occurs

New Record – ACNVEL(5507,55,650)

Acoustic normal velocity on surface


1 SID I Load set identification number

2 FORM I Complex format: 0 for real/imaginary, 1 formagnitude/phase

3 A RS Scale factor

4 TRTM RS Real part or magnitude

5 TIDTRTM I TABLEDi bulk entry identification number for realpart or magnitude

6 TITP RS Imaginary part or phase (in degrees)

7 TIDTITP I TABLEDi bulk entry identification number forimaginary part or phase (in degrees)

8 BID I BSURF identification number





9 UNDEF(3) None

New Record – ACORDER(9607,96,660)

Adaptivity order for FEM Adaptive Order solution


1 ORDER(2) CHAR4 Maximum or minimum

3 NUMBER I Order number

4 E1 I Element identification number (for future use)


New Record – ACPLNW(5807,59,653)

Acoustic plane wave source




3 A1 RS Scale factor 1

4 TRTM RS Real part or magnitude of plane wave

5 TIDTRTM I TABLEDi bulk entry identification number for realpart or magnitude of plane wave

6 TITP RS Imaginary part or phase (in degrees) of plane wave

7 TIDTITP I TABLEDi bulk entry identification number forimaginary part or phase (in degrees) of plane wave

8 CID1 I Coordinate system identification number for locationof plane wave source

9 X RS X-coordinate of plane wave source

10 Y RS Y-coordinate of plane wave source

11 Z RS Z-coordinate of plane wave source

12 CID2 I Coordinate system identification number fordirection of plane wave





13 NX RS Direction cosine between plane wave direction andX-axis

14 NY RS Direction cosine between plane wave direction andY-axis

15 NZ RS Direction cosine between plane wave direction andZ-axis

16 UNDEF(3) None

New Record – ACPOLE1(5607,56,651)

Acoustic monopole source



2 TYPE I 0 for amplitude, 1 for power


4 A RS Scale factor

5 TRTM RS Real part or magnitude of monopole source

6 TIDTRTM I TABLEDi bulk entry identification number for realpart or magnitude of monopole source

7 TITP RS Imaginary part or phase (in degrees) of monopolesource

8 TIDTITP I TABLEDi bulk entry identification number forimaginary part or phase (in degrees) of monopolesource

9 CID I Coordinate system identification number formonopole source location

10 X RS X-direction coordinate of monopole source

11 Y RS Y-direction coordinate of monopole source

12 Z RS Z-direction coordinate of monopole source

13 UNDEF(3) None




New Record – ACPOLE2(5707,58,652)

Acoustic dipole source




3 CID1 I Coordinate system identification number for dipolesource location

4 X RS X-direction coordinate of dipole source

5 Y RS Y-direction coordinate of dipole source

6 Z RS Z-direction coordinate of dipole source

7 CID2 I Coordinate system identification number for dipolemoment


9 TRTM1 RS Real part or magnitude of dipole moment inX-direction

10 TIDTRTM1 I TABLEDi bulk entry identification number for realpart or magnitude of dipole moment in X-direction

11 TITP1 RS Imaginary part or phase (in degrees) of dipolemoment in X-direction

12 TIDTITP1 I TABLEDi bulk entry identification number forimaginary part or phase (in degrees) of dipolemoment in X-direction


14 TRTM2 RS Real part or magnitude of dipole moment inY-direction

15 TIDTRTM2 I TABLEDi bulk entry identification number for realpart or magnitude of dipole moment in Y-direction

16 TITP2 RS Imaginary part or phase (in degrees) of dipolemoment in Y-direction

17 TIDTITP2 I TABLEDi bulk entry identification number forimaginary part or phase (in degrees) of dipolemoment in Y-direction






19 TRTM3 RS Real part or magnitude of dipole moment inZ-direction

20 TIDTRTM3 I TABLEDi bulk entry identification number for realpart or magnitude of dipole moment in Z-direction

21 TITP3 RS Imaginary part or phase (in degrees) of dipolemoment in Z-direction

22 TIDTITP3 I TABLEDi bulk entry identification number forimaginary part or phase (in degrees) of dipolemoment in Z-direction

23 UNDEF(3) None

New Record – ALOAD(5407,54,649)

Combination of acoustic loads



2 UNDEF(3) None

5 LI I Load set identification number i


New Record – FRFFLEX(2601,26,58)


1 ID I Identification number for FRF component

2 IDUM I Dummy word (always 0)

3 TYPE I Data type: =1 for displacement per unit force; =2for velocity per unit force; =3 for acceleration perunit force

4 SYMFLG I Symmetry flag: =0 for symmetric; =1 forunsymmetric

5 LSCALE RS Length scaling factor

6 FSCALE RS Force scaling factor





7 PSCALE RS Pressure scaling factor

8 QSCALE RS Acoustic source strength scaling factor

9 UNDEF(8) None

17 GJ I Grid identification number of excited location(column)

18 CJ I Component (0-6) of excited location (column)

19 GI I Grid identification number of response location(row)

20 CI I Component (0-6) of response location (row)

21 TIDI I Identification number of TABLED6 for dynamicflexibility value

Words 19 through 21 repeat for each row until (-1,-1) occurs

Words 17 and 18 along with 19 through 21 repeat for each column until (-1,-1) occurs

New Record – FRFOMAP(2807,28,79)



2 UNDEF(7) None

9 TYPE I Output data type: 1=displacement, 2=velocity,3=acceleration



Words 10 and 11 repeat for each response location i until (-1,-1) occurs

Words 9 through 11 repeat for each response type until (-1,-1) occurs

New Record – FRFOTM(2701,27,62 )












7 UNDEF(2) None

9 GIN I Grid identification number of input location

10 CIN I Component (0-6) of input location

11 TYPEIN I Input type: =0 for force/moment; =1 fordisplacement; =2 for velocity; =3 for acceleration

12 UNDEF(4) None

16 GOUT I Grid identification number of output i

17 COUT I Component (0-6) of output i

18 TIDI I Identification number of TABLED6 fordynamic/flexibility value

Words 16 through 18 repeat for each output i until (-1,-1) occurs

Words 9 through 15 along with 16 through 18 repeat for each input location until (-1,-1) occurs

New Record – FRFSTIF(2501,25,57)




3 TYPE I Data type: =1 for force per unit displacement; =2for force per unit velocity; =3 for force per unitacceleration

4 SYMFLG I Symmetry flag: =0 for symmetric; =1 forunsymmetric









9 UNDEF(8) None

17 GJ I Grid identification number of excited location(column)

18 CJ I Component (0-6) of excited location (column)



21 TIDI I Identification number of TABLED6 for dynamicstiffness value

Words 19 and 21 repeat for each row until (-1,-1) occurs

Words 17 and 18 along with 19 through 21 repeat for each column until (-1,-1) occurs

New Record – TLOAD3(7307,73,647)



2 EXCITID I SID of FORCDST entry

3 DELAYR RS Constant value for tau if DELAYI=0

4 TIDF(3) I Identification numbers of TABLEDi entries for threeforce components: F(t)

7 TIDM(3) I Identification numbers of TABLEDi entries for threemoment components: M(t)

EDOM

Updated Record – DRESP1(3806,38,359)


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

FLAG = 1 WEIGHT

5 UNDEF(2) None





7 REGION I Region identifier for constraint screening

8 ATTA I Response attribute (-10 for DWEIGHT which is thetopology optimization design weight

9 ATTB I Response attribute

10 MONE I Entry is -1

FLAG = 2 VOLUME

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

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

FLAG = 17 Compliance

5 UNDEF(2) None

7 UNDEF I Reserved for SEID for compliance DRESP1

8 UNDEF(2) None

10 MONE I Entry is -1

FLAG = 19 ERP

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

New Record – DMNCON(6903,69,637)


1 ID I Unique entry identifier

2 GID I GROUP identification number

3 IOPTION I Number of element layers to consider or forCYCLIC_SYMMETRY, REPREF=1 indicatesrepeated sector; 2 indicates reflected sector

4 FLAG I

FLAG = 1 Type of constraint = PLANE_SYMMETRY

5 X RS X axis of point on plane

6 Y RS Y axis of point on plane

7 Z RS Z axis of point on plane





8 N1 RS X component of vector normal to plane

9 N2 RS Y component of vector normal to plane

10 N3 RS Z component of vector normal to plane

11 UNDEF(5) None

FLAG = 2 Type of constraint = CYCLIC_SYMMETRY

5 X RS X component of point on axis

6 Y RS Y component of point on axis

7 Z RS Z component of point on axis

8 N1 RS X component of vector defining the rotational axis

9 N2 RS Y component of vector defining the rotational axis

10 N3 RS Z component of vector defining the rotational axis

11 M1 RS X component of vector defining symmetry plane

12 M2 RS Y component of vector defining symmetry plane

13 M3 RS Z component of vector defining symmetry plane

14 NSECT I Number of sectors

15 UNDEF(5) None

FLAG = 3 Type of constraint = EXTRUSION

5 N1 RS X component of vector to define extrusion

6 N2 RS Y component of vector to define extrusion

7 N3 RS Z component of vector to define extrusion

8 UNDEF(5) None

FLAG = 4 Type of constraint = CASTING

5 X RS X component of point on casting plane

6 Y RS Y component of point on casting plane

7 Z RS Z component of point on casting plane

8 N1 RS X component of a vector normal to the castingplane





9 N2 RS Y component of a vector normal to the castingplane

10 N3 RS Z component of a vector normal to the castingplane

11 D11 RS X component of a vector which defines the moldremoval direction 1 of casting

12 D12 RS Y component of a vector which defines the moldremoval direction 1 of casting

13 D13 RS Z component of a vector which defines the moldremoval direction 1 of casting

14 D21 RS X component of a vector which defines the moldremoval direction 2 of casting

15 D22 RS Y component of a vector which defines the moldremoval direction 2 of casting

16 D23 RS Z component of a vector which defines the moldremoval direction 2 of casting

17 UNDEF(5) None

FLAG = 5 Type of constraint = MAX_SIZE

5 MSIZE RS Maximum size

6 UNDEF(5) None

FLAG = 6 Type of constraint = MIN_SIZE

5 MSIZE RS Minimum size

6 UNDEF(5) None

FLAG = 7 Type of constraint = ADDITIVE

5 ANGLE RS Maximum angle measured from the vector N

6 MIND RS Minimum allowed dimension

7 X RS X coordinate of point on base plate

8 Y RS Y coordinate of point on base plate

9 Z RS Z coordinate of point on base plate





10 N1 RS X component of a vector normal to the castingplate in the direction of material addition

11 N2 RS Y component of a vector normal to the castingplate in the direction of material addition

12 N3 RS Z component of a vector normal to the castingplate in the direction of material addition

13 UNDEF(5) None

FLAG = 8 Type of constraint = CHECKERBOARDING

5 RADIUS RS Minimum radius to be considered

6 UNDEF(5) None

New Record – DMRLAW(7102,71,645)


1 ID I Material relation law identification number

2 FLAG I

FLAG = -1 Lattice octet cell law

3 PARAM I Equation parameter, currently unused

FLAG = -2 Lattice cubic cell law


FLAG = -3 Lattice BCC cell law


FLAG = -4 Lattice FCC cell law


FLAG = -5 Lattice octahedral cell law


FLAG = -6 Lattice BCC+cubic cell law


FLAG = -7 Lattice FCC+cubic cell law






FLAG = -8 Lattice BCC+FCC cell law


FLAG = -9 Lattice BCC+FCC+cubic cell law


FLAG = -1000 SIMP penalty exponent

3 PARAM RS SIMP penalty exponent

FLAG = -1001 RAMP penalty law

3 PARAM RS RAMP penalty exponent

FLAG = 0 LINEAR penalty law


4 RESERV I Reserved for future use

New Record – DVTREL1(6803,68,636)


1 ID I Identification number

2 LABEL(2) CHAR4 Label

4 GID I Referenced GROUP bulk entry identification number

5 STATE I 0=ACTIVE, 1=FROZEN

6 DSVFLG I Flag normally to be added by way of the punch filebulk output

7 UNDEF(3) None

10 DVID I Blank or identification number for the 1stauto-generated DESVAR entry

11 COEF RS Coefficient in the expression P=COEF*DV (currentlyinactive)

12 UNDEF(6) None




EDT

New Record – MONPNT2(1247,12,667)


1 NAME(2) CHAR4 Character string identifying the monitor point

3 LABEL(14) CHAR4 Character string identifying and labeling themonitor point

17 TABLE(2) CHAR4 Stress, strain, or force

19 ELTYP(2) CHAR4 Element type

21 ITEM(2) CHAR4 NDDL item

23 EID I Element identification number

Words 17 thru 23 repeat until -1 occurs

Words 1 thru 23 repeat until (-2,-2) occurs

New Record – MONPNT3(1448,14,668)


1 NAME(2) CHAR4 Parameter name

3 LABEL(14) CHAR4 Parameter name

17 AXES I Component axes about which to sum

18 GSET1 I Grid set group

19 ESET2 I Element set group

20 CID I Input coordinate system

21 X RS X-coordinate

22 Y RS Y-coordinate

23 Z RS Z-coordinate

24 XFLAG(2) CHAR4 Exclude flag

26 CD I Output coordinate system




ELRSCALV

Updated Record – IDENT


1 ACODE(C) I Device code + 10*Approach Code

2 TCODE(C) I Table code

3 DATCOD I Modal contribution code: 1/11=abs st/fl,2/12=norm st/fl


TCODE,1 =1 Sort 1

ACODE,4 =01 Statics (static and modal results are both designated as static)

5 LSDVMN I Load set number (always 1)

6 UNDEF(2 ) None

End TCODE,1

8 RCODE I Random code identification number (always 0)

9 FCODE I Format code (always 1)

10 NUMWDE I Number of words per entry in DATA record(always 2)

11 UNDEF(2) None

13 ACFLG(C) I Acoustic pressure flag (always 0)

14 UNDEF(9) None

23 THERMAL I 1 for heat transfer, 0 otherwise

24 UNDEF(27)

51 TITLE(32) CHAR4 Title “Topology Optimization”

83 SUBTITL(32) CHAR4 Subtitle “NAMEKEY Normalized MaterialDensity”





EPT

Updated RECORDS – NSM(3201,32,991), NSM1(3301,33,992), NSML(3501,35,994),NSML1(3701,37,995)


1 SID I Set identification number

2 PROP CHAR4 Set of properties

3 TYPE CHAR4 Set of elements

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

New RECORD – PAABSF1(6551,71,655)

Defines the properties of a frequency-dependent acoustic impedance/admittance


1 PID I Property identification number

2 PTYPE I Property type: 0 for impedance, 1 for admittance

3 FORM I Complex format: 0 for real/imaginary, 1 formagnitude/phase (in degrees)

4 ZR RS Real part/magnitude of impedance/admittance

5 TIDZR I TABLEDi bulk entry identification number for ZR

6 ZI RS Imaginary part/phase (in degrees) ofimpedance/admittance

7 TIDZI I TABLEDi bulk entry identification number for ZI

8 UNDEF(3) None

New RECORD – PCOMPG1(15106,151,953)



2 Z0 RS Distance from the reference plane to the bottomsurface

3 NSM RS Nonstructural mass per unit area

4 SB RS Allowable shear stress of the bonding material





5 UNDEF None

6 TREF RS Reference temperature

7 GE RS Damping coefficient

8 UNDEF None

9 GPLYIDi I Global ply identification number

10 MID I Material identification number

11 T RS Thicknesses of the ply

12 THETA RS Orientation angle of the longitudinal direction of theply

13 FT I Failure theory

14 SOUT I Stress or strain output request of the ply

15 UNDEF None

Words 9 through 15 repeat until (-1,-1,-1,-1,-1,-1,-1,-1) occurs

New RECORD – PSHELL1(8601,86,954)



2 MID1 I Material identification number for the membrane

3 T RS Default membrane thickness for Ti on the connectionentry

4 MID2 I Material identification number for bending

5 INTEG I Integration number through the thickness

6 UNDEF None

7 MID4 I Material identification number for membrane-bendingcoupling


9 UNDEF(3) None




EPT705

New RECORD – PCOMPG1(15106,151,953)



2 Z0 RS Distance from the reference plane to the bottomsurface


4 SB RS Allowable shear stress of the bonding material

5 UNDEF None

6 TREF RS Reference temperature

7 GE RS Damping coefficient

8 UNDEF None

9 GPLYIDi I Global ply identification number


11 T RS Thicknesses of the ply

12 THETA RS Orientation angle of the longitudinal direction of theply

13 FT I Failure theory

14 SOUT I Stress or strain output request of the ply

15 UNDEF None

Words 9 through 15 repeat N times

New RECORD – PSHELL1(8601,86,954)



2 MID1 I Material identification number for the membrane

3 T RS Default membrane thickness for Ti on the connectionentry

4 MID2 I Material identification number for bending





5 INTEG I Integration number through the thickness

6 UNDEF None

7 MID4 I Material identification number for membrane-bendingcoupling


9 UNDEF(3) None

GEOM1

New Record – ATVBULK(6591,65,659)


1 UNIT I FORTRAN unit identification number for ATV OP2file

2 EOFFSET I Element identification number offset

3 GOFFSET I Grid identification number offset

4 POFFSET I Property identification number offset

5 UNDEF(6) None

New Record – IMPERF(1209,96,665)


1 ID I Imperfection identification number

2 CP I Imperfection coordinate system identificationnumber

3 GID I Grid point identification number

4 X1 RX Imperfection at the point in coordinate 1 of CP



Words 3 through 6 repeat until (-1,-1) occurs




New Record – IMPRADD(1208,84,664)


1 SID I Imperfection set identification number

2 S RS Overall scale factor

3 SI RS Scale factor i

4 LI I Imperfection set identification number

Words 3 and 4 repeat until (-1,-1) occurs

Removed Records

CSUPER1(5701,57,323)CSUPUP(5801,58,324)GMCORD(6401,64,402)GMCURV(6601,66,392)

GEOM2

New RECORD – ACFACE3(15200,152,9912)



2 G(3) I Grid point identification numbers of connectionpoints

3 UNDEF(2) None





3 UNDEF(2) None









3 UNDEF(2) None





3 UNDEF(2) None

New RECORD – CBUSH1DNL(5609,60,9899)




3 G(2) I Grid point identification numbers

5 CID I Coordinate system identification number

6 UNDEF(3 ) None

New RECORD – CELAS1NL(6010,53,9900)

Same as record CELAS1 description.

New RECORD – CELAS2NL(7010,20,9898)

Same as record CELAS2 description.

New RECORD – CQUAD8L(3302,33,1694)

Same as record CQUAD8 description.

New RECORD – CQUAD8N(15901,159,9956)


New RECORD - CQUADRN(15401,154,9954)





New RECORD - CTRIA6L(3202,32,1693)

Same as record CTRIA6 description.

New RECORD - CTRIA6N(15801,158,9955)


New RECORD - CTRIARL(12902,129,1691)


New RECORD - CTRIARN(15301,153,9953)


New RECORD - PLOTEL3(5202,52,669)




New RECORD – PLOTEL4(5203,52,670)




New RECORD – PLOTEL6(5204,52,671




New RECORD – PLOTEL8(5205,52,672)







New RECORD - PLOTHEX(5206,52,673)




New RECORD – PLOTPEN(5208,52,675)




New RECORD – PLOTPYR(5209,52,676)




New RECORD – PLOTTET(5207,52,674)




GEOM3

New Record – FORCDST(5001,50,646)



2 GEOM I SID of BSURF/BSURFS/BEDGE

3 PLOC(2) CHAR4 Coordinate system identification number

5 GRID I Grid point identification numbers





6 OFFST(3) RS Offsets in x, y, and z-directions

9 F RS Force scale factor

10 FN(3) RS Vector for force direction such that Force = F x FN

13 M RS Moment scale factor

14 MN(3) RS Vector for moment direction such that Moment =M x MN

New Record – INITS(8701,87,625)


1 SID I INITS set identification number

2 TYPE I Type of data: 1=stress, 2=strain

3 LOC(C) I The location on the element where thestresses/strains are defined.

4 SYSTEM I Reference coordinate system used to definethe stress/strain orientation coordinate system.Values: -1 for MATCID, 0 for BASIC, >0 forCSYS ID

5 UNDEF(4) None

LOC=0 Stress/strain defined at element centroid (unsupported)


10 EXX RS Stress/strain xx

11 EYY RS Stress/strain yy

12 EZZ RS Stress/strain zz

13 EXY RS Stress/strain xy

14 EYZ RS Stress/strain yz

15 EXZ RS Stress/strain zx

Words 9 through 15 repeat until -1 occurs

LOC=1 Stress/strain defined at grids on element






10 GID I Grid identification number








LOC=2 Stress/strain defined at grid points









LOC=3 Stress/strain defined at element Gauss points (unsupported)

9 EID I Element identification number of grid or element

10 GID I Gauss point identification number











New Record – INITSO(2901,29,638)


1 SID I INITSO set identification number

2 TYPE I Type of data (only STRAIN is allowed): 2=strain

3 LOC(C) I The location on the element where thestresses/strains are defined.

4 SYSTEM I Reference coordinate system used to definethe stress/strain orientation coordinate system.Values: -1 for MATCID, 0 for BASIC, >0 forCSYS ID

5 UNDEF(4) None

LOC=0 Initial strain offset at element centroid (unsupported)









LOC=1 Initial strain offset at grids on elements














LOC=2 Initial strain offset at grid points









LOC=3 Initial strain offset at element Gauss points (unsupported)

9 EID I Element identification number of grid or element

10 GID I Gauss point identification number








New Record – INITADD(1101,11,626)



2 UNDEF(8) None

10 LI I INITS or INITSO set identification number





GEOM4

New Record – ACPRESS(5656,57,656)



2 FORM I Real/imaginary = 0, magnitude/phase = 1

3 A RS Scale factor

4 TRTM RS TR/RM

5 TIDTRTM I Table identification number of TR/RM

6 TITP RS TI/TP

7 TIDTRTM I Table identification number of TI/TP

8 UNDEF(3) None

11 ID I For GID, ID > 0; for "THRU", ID = 0; for "BY", ID = -6


LAMA

Updated Record 1 – OFPID


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

3 UNDEF None

4 SCID I Subcase ID

5 UNDEF(5) None

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

12 UNDEF(11) None

23 FLAG I Default = 0; SOL 401 Axi-Fourier = 2, SOL401 Cyclic = 3

24 UNDEF(2) None

26 HINDEX I Harmonic index for SOL 401 Axi-Fourieror SOL 401 Cyclic solutions. Default = -1if not SOL 401 Axi-Fourier or Cyclic.





27 UNDEF(24) None

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

MPT

Updated Record – MATCZ(5303,53,906)


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

DLAW = 5 UMAT

3 UNDEF(6) None

9 K03S RS Transverse stiffness

10 K02 RS Shear stiffness

11 K01 RS Second shear stiffness

12 UNDEF(13) None

Updated Record – MATDMG(5101,51,642)


PPFMOD=1 UD damage model

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

26 TID I Identification number of a TABLEM5 entry fornonlinear shear damage

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

PPFMOD=2 EUD damage model

3 UNDEF(6) None

9 Y012 RS Fiber/matrix de-bonding threshold

10 YC12 RS Critical thermodynamic force

11 K RS Coupling coefficient to account for the contributionof thermodynamic force Yd to fiber damage incompression





12 ALPHA RS Parameter given by the user to define therelationship for three crack modes in ruptureenvelope

13 Y11LIMT RS Breaking thresholds in tension

14 Y11LIMC RS Breaking thresholds in compression

15 KSIT RS Non-linearity coefficients in tension

16 KSIC RS Non-linearity coefficients in compression

17 B2 RS Coupling coefficient

18 B3 RS Coupling coefficient between the damage variables

19 A RS Coupling coefficient (plasticity)

20 LITK RS Initial plastic threshold

21 BIGK RS Parameter of plastic law

22 EXPN RS Exponent of plastic law

23 TAU RS Time for delay

24 ADEL RS Parameter for delay

25 USER I Indicator whether static damage w is limited to themaximum damage before taking into account timedelay effect

26 RO1 RS Maximum transverse micro-cracking density

27 HBAR RS Transition thickness

28 DMAX RS Maximum value of damage

29 DS RS Maximum diffuse damage

30 GIC RS Critical mode I crack energy release rates for the ply

31 GIIC RS Critical mode II crack energy release rates for the ply

32 GIIIC RS Critical mode III crack energy release rates for theply




New Record – MAT10C(4701,50,965)



2 FORM I Format of data: real/imaginary=0,magnitude/phase=1

3 RHOR RS Mass density real part or magnitude

4 UNDEF None

5 RHOI RS Mass density imaginary part or phase (in degrees)

6 UNDEF None

7 CR RS Speed of sound real part or magnitude

8 UNDEF None

9 CI RS Speed of sound imaginary part or phase (in degrees)

10 UNDEF(3) None

New Record – MATF10C(6610,52,661)



2 TIDRHOR I TABLEDi identification number that definesfrequency-dependent real part or magnitude of massdensity

3 TIDRHOI I TABLEDi identification number that definesfrequency-dependent imaginary part or phase (indegrees) of mass density

4 TIDCR I TABLEDi identification number that definesfrequency-dependent real part or magnitude of speedof sound

5 TIDCI I TABLEDi identification number that definesfrequency-dependent imaginary part or phase (indegrees) of speed of sound

6 UNDEF(5) None




New Record – MATT10(4901,49,960)



2 TBULK I TABLEMi ID for bulk modulus

3 TRHO I TABLEMi ID for mass density

4 TC I TABLEMi ID for speed of sound

5 TGE I TABLEMi ID for structural damping coefficient

6 ALPHA I TABLEMi ID for temporal damping coefficient

7 UNDEF(4) None

New Record – NLARCL(1308,13,663)


1 ID I NLARCL identification number

2 PARAM(i)1 CHAR4 First 4 characters in PARAM(i) name

3 PARAM(i)2 CHAR4 Second 4 characters in PARAM(i) name

4 PMLIST I Parameter value type

PMLIST=1 Parameter value is integer

5 IVAL I Integer value of PARAMi

PMLIST=2 Parameter value is real

5 RVAL RS Real parameter value

PMLIST=3 Parameter value is character

5 CVAL1 CHAR4 First 4 characters in PARAM(i) value

6 CVAL2 CHAR4 Second 4 characters in PARAM(i) value

If in previous loop PMLIST=1 or 2, words 3 through 5 repeat until (-1,-1) occursIf in previous loop PMLIST=3, words 3 through 6 repeat until (-1,-1) occurs

New Record – NLCNTL(1203,12,617)


1 ID I NLCNTL identification number





2 PARAM(i)1 CHAR4 First 4 characters in PARAM(i) name

3 PARAM(i)2 CHAR4 Second 4 characters in PARAM(i) name

4 PMLIST I Parameter value type

PMLIST=1 Parameter value is integer

5 IVAL I Integer value of PARAMi

PMLIST=2 Parameter value is real

5 RVAL RS Real parameter value

PMLIST=3 Parameter value is character

5 CVAL1 CHAR4 First 4 characters in PARAM(i) value

6 CVAL2 CHAR4 Second 4 characters in PARAM(i) value

If in previous loop PMLIST=1 or 2, words 3 through 5 repeat until (-1,-1) occursIf in previous loop PMLIST=3, words 3 through 6 repeat until (-1,-1) occurs

OACCQ



3 DATCOD I Data code:

• 0 = coupled fluid faces; normal projectiondistance in absolute units

• 1 = uncoupled fluid faces; outwardand inward normal search distance inabsolute units

• 2 = coupled and uncoupled fluid faces;for coupled faces, normal projectiondistance in absolute units; for uncoupledfaces, outward and inward normalsearch distance in absolute units

• 3 = coupled and uncoupled structuralfaces; for coupled faces, distance = 0.0;for uncoupled faces, distance = 1.0




OACINT

Acoustic intensity at fluid grids in SORT1 and SORT2 format



1 ACODE(C) I Device code + 10*Approach code

2 TCODE(C) I Table code = 54

3 UNDEF None

4 SUBCASE I Subcase identification number.

TCODE,1 = 01 Sort 1

5 FREQ RS Frequency (Hz)

TCODE,1 = 02 Sort 2

5 GID I Fluid grid ID

End TCODE,1

6 UNDEF(3) None

9 FCODE(C) I Format code

10 NUMWDE(C) I Number of words per entry in DATA record= 7

11 UNDEF(40) None

51 TITLE(32) CHAR4 Title character string (TITLE)

83 SUBTITL(32) CHAR4 Subtitle character string (SUBTITLE)

115 LABEL(32) CHAR4 LABEL character string (LABEL)

Updated Record – DATA


TCODE,1 = 01 Sort 1


TCODE,1 = 02 Sort 2


End TCODE,1





2 INTR(3) RS Intensity components - real part

5 INTI(3) RS Intensity components - imaginary part

OACPWR





3 DATCOD I Data code; 10*SID for AMLREG, 10*SID+1for GROUP

4 SUBCAS I Subcase identification number

TCODE,1 = 01 SORT1 format



5 SID I AMLREG / GROUP ID

End TCODE,1

6 UNDEF(1) None

7 RCODE I Random ID

8 UNDEF(1) None

9 FCODE(C) I Format type code

10 NUMWDE(C) I Number of words per entry in DATA record= 2 or 3

11 DESCR(12) CHAR4 AMLREG / GROUP description

23 UNDEF(28) None









TCODE,1 = 01 SORT1 Format

1 SID I AMLREG/GROUP ID



End TCODE,1

TCODE,7 = 01 Real or imaginary

2 POWERR RS Power - real part

3 POWERI RS Power - imaginary part

TCODE,7 = 0 or 2 Real or random response

2 POWER RS Power

End TCODE,7

Updated Record – TRAILER


1 NUMRF I Number of record pairs * number of frequencies

2 UNDEF(5) None

OACVELO

Acoustic velocity at fluid grids in SORT1 and SORT2 format





3 UNDEF

4 SUBCAS I Subcase identification number

TCODE,1 = 01 Sort 1






TCODE,1 = 02 Sort 2


End TCODE,1

6 UNDEF(3)

9 FCODE(C) I Format code

10 NUMWDE(C) I Number of words per entry in DATA record= 7

11 UNDEF(40)






TCODE,1 = 01 Sort 1


TCODE,1 = 02 Sort 2


End TCODE,1

2 VELR(3) RS Velocity components - real part

5 VELI(3) RS Velocity components - imaginary part

OBC



1 ACODE(C) I Device code + 10* Approach Code

2 TCODE(C) I Table code, 62





3 UNDEF None


TCODE=1 SORT1

ACODE=01 SOL 101 linear statics

5 LSDVMN I Load set number

6 UNDEF(2) None

ACODE=06 401 non arc-length

5 TIME RS Time step

6 UNDEF(2) None

ACODE=10 401, 601, and 701 nonlinear statics

5 LFTSFQ RS Load factor for SOL 401 arc-length only

6 TIME RS Time for SOL 401 arc-length only

7 AL_TOTAL RS Accumulated arc-length for SOL 401 arc-lengthonly

End ACODE

TCODE=2 SORT2

5 LSDVMN I Load set, mode number

6 UNDEF(2) None

End TCODE


9 FCODE I Format code

10 NUMWDE I Number of words per entry in DATA record

11 UNDEF None

12 PID I Physical property

13 UNDEF(38) None

51 TITLE(32) CHAR4 Title

83 SUBTITL(32) CHAR4 Subtitle






OBOLT



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

ACODE,4=06 Transient

5 TIME RS Current time step

6 UNDEF(4) None

ACODE,4=10 Nonlinear statics




8 UNDEF(2) None

End ACODE

10 NUMWDE(C) I Number of words per entry in DATA record

11 CSID I Bolt coordinate system ID

12 IDIR I Bolt direction vector

13 EULER1(3) RS Euler angles between basic and bolt CSYS inundeformed configuration

16 EULER2(3) RS Euler angles between basic and bolt CSYS indeformed configuration

19 UNDEF(32) None

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




OBG



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

ACODE=10 Nonlinear statics




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

OCKGAP1





3 ELTYPE(C) I Element type number


ACODE=06 Transient


6 UNDEF(4) None





8 UNDEF(2) None

End ACODE

10 NUMWPE I Number of words per entry element





11 UNDEF(40) None




ODAMGCZD

Updated Record - IDENT


1 ACODE(C) I Device code + 10*Approach code = 60 +iand (print, plot)

2 TCODE I Table code


4 SUBCASE I Subcase number

TCODE,1 = 01 Sort 1

ACODE,4 = 06 Transient


6 UNDEF(45) None

ACODE,4 = 10 Nonlinear statics

5 LFTSFQ RS Load step for SOL 401 arc-length only


7 AL_TOTAL RS Accumulated arc-length for SOL 401arc-length only

8 UNDEF(43) None

End ACODE,4

TCODE,1 = 02 Sort 2

End TCODE,1








ODAMGCZR







TCODE,1 = 01 Sort 1



6 UNDEF(4) None


5 LFTSFQ RS Load step for SOL401 arc-length only

6 TIME RS Time for SOL401 arc-length only

7 AL_TOTAL RS Accumulated arc-length for SOL401arc-length only

8 UNDEF(2) None

End ACODE,4

TCODE,1 = 02 Sort 2

End TCODE,1

10 NWDSPE I Number of words per element E335=41,E336=31, E353=34, E354=26

11 UNDEF(40) None










ELTYPE=335 or 336 ELTYPE=335 - Cohesive HEXA element (CHEXCZ)

ELTYPE=336 - Cohesive PENTA element (CPENTCZ)

1 EID I Element ID * 10 + device code

2 GRID I External identification number of grid

3 RDN RS Normal relative separation

4 RD1 RS In-plane relative motion in X direction (basiccoordinate system)

5 RD2 RS In-plane relative motion in Y direction (basiccoordinate system)

6 RD3 RS In-plane relative motion in Z direction (basiccoordinate system)

ELTYPE=353 or 354 ELTYPE=353 - Cohesive HEXA element (CHEXCZ) output inmaterial coordinate system

ELTYPE=354 - Cohesive PENTA element (CPENTCZ) output inmaterial coordinate system


2 CID I Material coordinate system identification number


4 RD1 RS Relative motion in X direction (material coordinatesystem)

5 RD2 RS Relative motion in Y direction (material coordinatesystem)

6 RD3 RS Relative motion in Z direction (material coordinatesystem)

Repeat words 2-6 for each corner grid point. (8 corners for cohesive CHEXA (CHEXCZ) and 6corners for cohesive PENTA element (CPENTCZ).)




ODAMGCZT







TCODE,1 = 01 Sort 1



6 UNDEF(4) None





8 UNDEF(2) None

End ACODE,4

TCODE,1 = 02 Sort 2

End TCODE,1

10 NWDSPE I Number of words per element, E335=41,E336=31, E353=34, E354=26

11 UNDEF(40) None









ELTYPE=335 or 336 ELTYPE=335 - Cohesive HEXA element (CHEXCZ)

ELTYPE=336 - Cohesive PENTA element (CPENTCZ)

1 ELID I Element ID * 10 + device code


3 TN RS Normal stress on face

4 T1 RS Shear stress on face in X direction (basiccoordinate system)

5 T2 RS Shear stress on face in Y direction (basiccoordinate system)

6 T3 RS Shear stress on face in Z direction (basiccoordinate system)

ELTYPE=353 or 354 ELTYPE=353 - Cohesive HEXA element (CHEXCZ) output inmaterial coordinate system

ELTYPE=354 - Cohesive PENTA element (CPENTCZ) output inmaterial coordinate system


2 CID I Material coordinate system ID


4 T1 RS Stress in direction X (material coordinate system)

5 T2 RS Stress in direction Y (material coordinate system)

6 T3 RS Stress in direction Z (material coordinate system)

Repeat words 2-6 for each corner grid point. (8 corners for cohesive CHEXA (CHEXCZ) and 6corners for cohesive PENTA element (CPENTCZ).)

ODAMGPFD

Table of damage values for ply failure for SOL 401

Damage values at corner grids on middle, and the values are unitless.










TCODE,1 = 01 Sort 1



6 UNDEF(4) None





8 UNDEF(2) None

End ACODE,4

TCODE,1 = 02 Sort 2

End TCODE,1


11 UNDEF(40) None









ELTYPE=267, 268, 355,356, 357, or 358

ELTYPE=267 - Composite HEXA element (CHEXAL)

ELTYPE=268 - Composite PENTA element (CPENTAL)

ELTYPE=355 - Composite triangular shell element (CTRIA6)

ELTYPE=356 - Composite quadrilateral shell element (CQUAD8)

ELTYPE=357 - Composite triangular shell element (CTRIAR)

ELTYPE=358 - Composite quadrilateral shell element (CQUADR)


2 PLY I Lamina number

3 DMID I Damage model identification number

DMID=1 UD damage model

4 NVPG I Number of active damage values, =6 for UD model

5 GRID I External grid ID

6 DV1 RS Damage value d11






DMID=2 EUD damage model

4 NVPG I Number of active damage values, =6 for EUDmodel












On each ply, words 5 thru 11 repeat for each corner grid point. (4 corners for composite HEXA andCQUADi elements, 3 corners for composite PENTA and CTRIAi elements.)

ODAMGPFE





3 ELTYPE I Element type number


TCODE,1 = 01 Sort 1



6 UNDEF(4) None





8 UNDEF(2) None

End ACODE,4

TCODE,1 = 02 Sort 2

End TCODE,1

10 NWDSPE I Number of words per element = 2

11 UNDEF(40) None








ODAMGPFS





3 ELTYPE I Element type number


TCODE,1 = 01 Sort 1



6 UNDEF(4) None





8 UNDEF(2) None

End ACODE,4

TCODE,1 = 02 Sort 2

End TCODE,1

10 NWDSPE I Number of words per element = 2

11 UNDEF(40) None








OEE

Updated Record - DATA


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

CVALRES=01 Complex value resolution: Average

2 ENERGYR RS Element Energy Average(real/mag part)

3 ENERGYI RS Element Energy Average(imag/phase part)

4 PCT RS Percent of Total Energy

5 DEN RS Element Energy Density,or '-1' after all elements

CVALRES=02 Complex value resolution: Amplitude

2 ENERGYR RS Element Energy Amplitude(real/mag part)

3 ENERGYI RS Element Energy Amplitude(imag/phase part)



CVALRES=03 Complex value resolution: Peak

2 ENERGYR RS Element Energy Peak(real/mag part)

3 ENERGYI RS Element Energy Peak(imag/phase part)



CVALRES=04 Complex value resolution: AVGAMP





2 ENERGRAV RS Element Energy Average(real/mag part)

3 ENERGIAV RS Element Energy Average(imag/phase part)

4 ENERGRAM RS Element Energy Amplitude(real/mag part)

5 ENERGIAM RS Element Energy Amplitude(imag/phase part)



End CVALRES

End TCODE,7

OEF



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

ACODE,4 =10 Nonlinear Statics




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

24 UNDEF(2) None

26 HINDEX I Harmonic index

27 SCFLAG I Sine/cosine flag: 0=0th harmonic, 1=cosinecomponent, 2=sine component, -1 (default)for other solution type output

28 UNDEF(23) None

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






TCODE,1 =1 SORT1 Format

1 EKEY I Device code + 10*Element identification number

TCODE,1 =02 SORT2 Format

ACODE,4 =01 Statics

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


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

ELTYPE =02 Beam element (CBEAM)

TCODE,7 =0 or 2 Real or Random Response

2 GRID I Grid point identification number

3 SD RS Station Distance divided by element's length

4 BM1 RS Bending moment plane 1


6 TS1 RS Shear Plane 1

7 TS2 RS Shear Plane 2

8 AF RS Axial Force

9 TTRQ RS Total Torque

10 WTRQ RS Warping Torque

TCODE,7 =1 Real/imaginary or magnitude/phase


3 SD RS Station Distance divided by element's length

4 BM1R RS Bending moment plane 1 - real/mag. part


6 TS1R RS Shear plane 1 - real/mag. part






8 AFR RS Axial force - real/mag. part

9 TTRQR RS Total torque - real/mag. part

10 WTRQR RS Warping torque - real/mag. part

11 BM1I RS Bending moment plane 1 - imag./phase part


13 TS1I RS Shear plane 1 - imag./phase part


15 AFI RS Axial force - imag./phase part

16 TTRQI RS Total torque - imag./phase part

17 WTRQI RS Warping torque - imag./phase part

End TCODE,7

Words 2 through max repeat 011 times

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


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

ELTYPE =64 Curved quadrilateral shell element (CQUAD8)


2 TERM CHAR4 Character string "CEN/"

3 GRID I Number of active grids or corner grid ID

4 MX RS Membrane force in x

5 MY RS Membrane force in y

6 MXY RS Membrane force in xy

7 BMX RS Bending moment in x

8 BMY RS Bending moment in y

9 BMXY RS Bending moment in xy

10 TX RS Shear force in x





11 TY RS Shear force in y




4 MXR RS Membrane force in x - real/mag. part

5 MYR RS Membrane force in y - real/mag. part

6 MXYR RS Membrane force in xy - real/mag. part

7 BMXR RS Bending moment in x - real/mag. part

8 BMYR RS Bending moment in y - real/mag. part

9 BMXYR RS Bending moment in xy - real/mag. part

10 TXR RS Shear force in x - real/mag. part

11 TYR RS Shear force in y - real/mag. part

12 MXI RS Membrane force in x - imag./phase part

13 MYI RS Membrane force in y - imag./phase part

14 MXYI RS Membrane force in xy - imag./phase part

15 BMXI RS Bending moment in x - imag./phase part

16 BMYI RS Bending moment in y - imag./phase part

17 BMXYI RS Bending moment in xy - imag./phase part

18 TXI RS Shear force in x - imag./phase part

19 TYI RS Shear force in y - imag./phase part

End TCODE,7


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

ELTYPE =69 Curved beam or pipe element (CBEND - see note)









5 TS1 RS Shear plane 1


7 AF RS Axial force

8 TRQ RS Torque


2 GRID I Grid point identification number - real/mag. part





7 AFR RS Axial force - real/mag. part

8 TRQR RS Torque - real/mag. part





13 AFI RS Axial force - imag./phase part

14 TRQI RS Torque - imag./phase part

End TCODE,7



ELTYPE =70 Triangular plate element (CTRIAR)








End TCODE,7


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

ELTYPE =75 Curved triangular shell element (CTRIA6)



































End TCODE,7


ELTYPE =76 Acoustic velocity/pressures in six-sided solid element (CHEXA)

TCODE,7 = 1 Real/imaginary or magnitude/phase

2 ELNAME(2) CHAR4 Element name: "HEXPR"

4 AXR RS Acceleration in x - real/mag. part

5 AYR RS Acceleration in y - real/mag. part

6 AZR RS Acceleration in z - real/mag. part

7 VXR RS Velocity in x - real/mag. part

8 VYR RS Velocity in y - real/mag. part

9 VZR RS Velocity in z - real/mag. part

10 PRESSURE RS Pressure in dB

11 AXI RS Acceleration in x - imag./phase part

12 AYI RS Acceleration in y - imag./phase part

13 AZI RS Acceleration in z - imag./phase part

14 VXI RS Velocity in x - imag./phase part

15 VYI RS Velocity in y - imag./phase part

16 VZI RS Velocity in z - imag./phase part


2 ELNAME(2) CHAR4 Element name: "HEXPR"





4 AX RS Acceleration in x - real/mag. part

5 AY RS Acceleration in y - real/mag. part

6 AZ RS Acceleration in z - real/mag. part

7 VX RS Velocity in x - real/mag. part

8 VY RS Velocity in y - real/mag. part

9 VZ RS Velocity in z - real/mag. part


ELTYPE =77 Acoustic velocity/pressures in five-sided solid element (CPENTA)


2 ELNAME(2) CHAR4 Element name: "PENPR"

4 AX RS Acceleration in x

5 AY RS Acceleration in y

6 AZ RS Acceleration in z

7 VX RS Velocity in x

8 VY RS Velocity in y

9 VZ RS Velocity in z


TCODE,7 =1 Complex

2 ELNAME(2) CHAR4 Element name: "PENPR"


















End TCODE,7

ELTYPE =78 Acoustic velocity/pressures in four-sided solid element (CTETRA)


2 ELNAME(2) CHAR4 Element name: "TETPR"








TCODE,7 =1

2 ELNAME(2) CHAR4 Element name: "TETPR"


















End TCODE,7

ELTYPE =79 Acoustic velocity/pressures in five-sided solid element(CPYRAM)

TCODE,7 = 0 or 2 Real or Random Response

2 ELNAME(2) CHAR4 Element name: “PYRAMPR”








TCODE,7 = 1

2 ELNAME(2) CHAR4 Element name: “PYRAMPR”

4 AXR RS Acceleration in x – real/mag. part

5 AYR RS Acceleration in y – real/mag. part

6 AZR RS Acceleration in z – real/mag. part

7 VXR RS Velocity in x – real/mag. part

8 VYR RS Velocity in y– real/mag. part

9 VZR RS Velocity in z– real/mag. part


11 AXI RS Acceleration in x – imag./phase part

12 AYI RS Acceleration in y – imag./phase part





13 AZI RS Acceleration in z – imag./phase part

14 VXI RS Velocity in x – imag./phase part

15 VYI RS Velocity in y – imag./phase part

16 VZI RS Velocity in z – imag./phase part

End TCODE,7


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

ELTYPE =82 Quadrilateral plate element (CQUADR)



3 GRID I Number of active grids (4) or corner grididentification number











3 GRID I Number of active grids (4) or corner grididentification number





















End TCODE,7


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


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

ELTYPE =144 Quadrilateral plate element for corner stresses (QUAD144)



3 GRID I Number of active grids (4) or corner grid ID

4 MX RS Membrane x

5 MY RS Membrane y

6 MXY RS Membrane xy

7 BMX RS Bending x





8 BMY RS Bending y

9 BMXY RS Bending xy

10 TX RS Shear x

11 TY RS Shear y



3 GRID I Number of active grids (4) or corner grid ID

4 MXR RS Membrane x - real/mag. part

5 MYR RS Membrane y - real/mag. part

6 MXYR RS Membrane xy - real/mag. part

7 BMXR RS Bending x - real/mag. part

8 BMYR RS Bending y - real/mag. part

9 BMXYR RS Bending xy - real/mag. part

10 TXR RS Shear x - real/mag. part

11 TYR RS Shear y - real/mag. part

12 MXI RS Membrane x - imag./phase part

13 MYI RS Membrane y - imag./phase part

14 MXYI RS Membrane xy - imag./phase part

15 BMXI RS Bending x - imag./phase part

16 BMYI RS Bending y - imag./phase part

17 BMXYI RS Bending xy - imag./phase part

18 TXI RS Shear x - imag./phase part

19 TYI RS Shear y - imag./phase part

End TCODE,7


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





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

ELTYPE =189 Quadrilateral plate view element (VUQUAD)

TCODE,7 =0 Real

2 PARENT I Parent p-element identification number

3 COORD I Coordinate system identification number

4 ICORD CHAR4 Flat/curved and so on

5 THETA I Material angle

6 UNDEF None

7 VUID I VU-grid identification number ID for corner

8 MFX RS Membrane force x

9 MFY RS Membrane force y

10 MFXY RS Membrane force xy

11 UNDEF(3 ) None

14 BMX RS Bending moment x

15 BMY RS Bending moment y

16 BMXY RS Bending moment xy

17 SYZ RS Shear yz

18 SZX RS Shear zx

19 UNDEF None






6 UNDEF None

7 VUID I VU-grid identification number for corner

8 MFXR RS Membrane force x real/mag.





9 MFYR RS Membrane force y real/mag.

10 MFXYR RS Membrane force xy real/mag.

11 UNDEF(3 ) None

14 BMXR RS Bending moment x real/mag.

15 BMYR RS Bending moment y real/mag.

16 BMXYR RS Bending moment xy real/mag.

17 SYZR RS Shear yz real/mag.

18 SZXR RS Shear zx real/mag.

19 UNDEF None

20 MFXI RS Membrane force x imag./phase

21 MFYI RS Membrane force y imag./phase

22 MFXYI RS Membrane force xy imag./phase

23 UNDEF(3 ) None

26 BMXI RS Bending moment x imag./phase

27 BMYI RS Bending moment y imag./phase

28 BMXYI RS Bending moment xy imag./phase

29 SYZI RS Shear yz imag./phase

30 SZXI RS Shear zx imag./phase

31 UNDEF None


End TCODE,7


ELTYPE =190 Triangular shell view element (VUTRIA)

TCODE,7 =0 Real









6 UNDEF None

7 VUID I VU grid ID for this corner

8 MFX RS Membrane force x

9 MFY RS Membrane force y

10 MFXY RS Membrane force xy

11 UNDEF(3 ) None

14 BMX RS Bending moment x

15 BMY RS Bending moment y

16 BMXY RS Bending moment xy

17 SYZ RS Shear yz

18 SZX RS Shear zx

19 UNDEF None






6 UNDEF None

7 VUID I VU grid ID this corner

8 MFXR RS Membrane force x real/mag.

9 MFYR RS Membrane force y real/mag.

10 MFXYR RS Membrane force xy real/mag.

11 UNDEF(3 ) None

14 BMXR RS Bending moment x real/mag.

15 BMYR RS Bending moment y real/mag.





16 BMXYR RS Bending moment xy real/mag.

17 SYZR RS Shear yz real/mag.

18 SZXR RS Shear zx real/mag.

19 UNDEF None

20 MFXI RS Membrane force x imag./phase

21 MFYI RS Membrane force y imag./phase

22 MFXYI RS Membrane force xy imag./phase

23 UNDEF(3 ) None

26 BMXI RS Bending moment x imag./phase

27 BMYI RS Bending moment y imag./phase

28 BMXYI RS Bending moment xy imag./phase

29 SYZI RS Shear yz imag./phase

30 SZXI RS Shear zx imag./phase

31 UNDEF None


End TCODE,7

ELTYPE =191 Beam view element (VUBEAM)

TCODE,7 =0 Real




5 VUGRID I VU grid ID for output grid

6 POSIT RS x/L position of VU grid identification number

7 FORCEX RS Force x

8 SHEARY RS Shear force y

9 SHEARZ RS Shear force z

10 TORSION RS Torsional moment x





11 BENDY RS Bending moment y

12 BENDZ RS Bending moment z





5 VUGRID I VU grid identification number for output grid

6 POSIT RS x/L position of VU grid identification number

7 FORCEXR RS Force x real/mag.

8 SHEARYR RS Shear force y real/mag.

9 SHEARZR RS Shear force z real/mag.

10 TORSINR RS Torsional moment x real/mag.

11 BENDYR RS Bending moment y real/mag.

12 BENDZR RS Bending moment z real/mag.

13 FORCEXI RS Force x imag./phase

14 SHEARYI RS Shear force y imag./phase

15 SHEARZI RS Shear force z imag./phase

16 TORSINI RS Torsional moment x imag./phase

17 BENDYI RS Bending moment y imag./phase

18 BENDZI RS Bending moment z imag./phase


End TCODE,7

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


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

ELTYPE =229 Triangular plate element (CTRIA3)





TCODE,7 =0 or 2 Real














4 MXR RS Membrane in x - real/mag. part

5 MYR RS Membrane in y - real/mag. part

6 MXYR RS Membrane in xy - real/mag. part

7 BMXR RS Bending in x - real/mag. part

8 BMYR RS Bending in y - real/mag. part

9 BMXYR RS Bending in xy - real/mag. part

10 TXR RS Shear in x - real/mag. part

11 TYR RS Shear in y - real/mag. part

12 MXI RS Membrane in x - imag./phase part

13 MYI RS Membrane in y - imag./phase part

14 MXYI RS Membrane in xy - imag./phase part

15 BMXI RS Bending in x - imag./phase part

16 BMYI RS Bending in y - imag./phase part





17 BMXYI RS Bending in xy - imag./phase part

18 TXI RS Shear in x - imag./phase part

19 TYI RS Shear in y - imag./phase part


End TCODE,7


ELTYPE =341 Triangular shell element (CTRIA3) for SOL 401

TCODE,7 =0 Real

2 THETA RS Material property orientation angle in degrees


4 MX RS Membrane in x

5 MY RS Membrane in y

6 MXY RS Membrane in xy

7 BMX RS Bending in x

8 BMY RS Bending in y

9 BMXY RS Bending in xy

10 TX RS Transverse shear in x

11 TY RS Transverse shear in y

Words 3 thru 11 repeat 3 times


ELTYPE =342 Quadrilateral shell element (CQUAD4) for SOL 401

TCODE,7 =0 Real

















ELTYPE =343 Triangular shell element (CTRIA6) for SOL 401

TCODE,7 =0 Real













ELTYPE =344 Quadrilateral shell element (CQUAD8) for SOL 401

TCODE,7 =0 Real

















ELTYPE =345 Triangular shell element (CTRIAR) for SOL 401

TCODE,7 =0 Real













ELTYPE =346 Quadrilateral shell element (CQUADR) for SOL 401

TCODE,7 =0 Real

















ELTYPE =347 Bar element (CBAR) for SOL 401

TCODE,7 =0 Real






7 AF RS Axial force

8 TTRQ RS Total torque

9 WTRQ RS Warping torque



ELTYPE =348 Beam element (CBEAM) for SOL 401

TCODE,7 =0 Real










7 AF RS Axial force

8 TTRQ RS Total torque

9 WTRQ RS Warping torque



ELTYPE =349 Bushing element (CBUSH1D) for SOL 401

TCODE,7 =0 Real

2 FX RS Axial force


ELTYPE =350 Spring element (CELAS1) for SOL 401

TCODE,7 =0 Real

2 FX RS Axial force


ELTYPE =351 Spring element (CELAS2) for SOL 401

TCODE,7 =0 Real

2 FX RS Axial force


ELTYPE =352 Bushing element (CBUSH) for SOL 401

TCODE,7 =0 Real





2 FX I Force in x

3 FY RS Force in y

4 FZ RS Force in z

5 RX RS Moment in YZ

6 RY RS Moment in ZX

7 RZ RS Moment in XY


ELTYPE =353ELTYPE =354ELTYPE =359ELTYPE =360ELTYPE =361ELTYPE =362

Reserved for CHEXCZReserved for CPENTCZReserved for PLOTEL3Reserved for PLOTEL4Reserved for PLOTEL6Reserved for PLOTEL8


ELTYPE =363 Rod element (CROD) for SOL 402

TCODE,7 =0 Real


3 AF RS Axial force

4 TF RS Torsional force



ELTYPE =364ELTYPE =365ELTYPE =366ELTYPE =367ELTYPE =368ELTYPE =369ELTYPE =370ELTYPE =371

Reserved for PLOTHEXReserved for PLOTTETReserved for PLOTPENReserved for PLOTPYRReserved for ACFACE3Reserved for ACFACE4Reserved for ACFACE6Reserved for ACFACE8




Updated Notes

1. The RECORD=IDENT and DATA pair is repeated for each subcase.

2. For composite elements, ELTYPEs 95-98 and 355-358, OEF contains composite failure indicesand the DATA record is repeated for each ply as well as each element. Also, the first EID of eachelement is Element ID, the subsequent EID=-1, then OFP module prints a blank line.

OERR



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



6 UNDEF(4) None

ACODE,4=10 Nonlinearstatics




8 UNDEF(2) None

End ACODE

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

OES



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









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

5 LSDVMN I Load set, mode number, time step, and soon. For composites this is 10*element_id+0(do not output) or +1 (do output)

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

22 BDFIXCS I Body-fixed coordinate system flag for SOL401 only: 0=in basic CS; 1=in body-fixedmaterial CS

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

24 STRMEAS I Strain/stress measurement for SOL 401/402only: 0=Engineering; 1=Green/PK2;2=Log/Cauchy; 3=Biot; 4=Log/Kirchhoff

25 UNDEF None

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



ELTYPE =189 Quadrilateral plate view element (VUQUAD)

SCODE,6 =0 Strain

TCODE,7 =0 Real


3 COORD I CID coordinate system identification number

4 ICORD CHAR4 ICORD flat/curved and so on

5 THETA I THETA angle

6 ITYPE I ITYPE strcur =0, fiber=1

7 VUID I VU grid identification number for this corner

8 UNDEF(2) None

10 MSX RS Membrane stain x





11 MSY RS Membrane strain y

12 MXY RS Membrane strain xy

13 UNDEF(3) None

16 BCX RS Bending curvature x

17 BCY RS Bending curvature y

18 BCXY RS Bending curvature xy

19 TYZ RS Shear yz

20 TZX RS Shear zx

21 UNDEF(3 ) None

Words 7 through 23 repeat 004 times

TCODE,7 =1 Real / Imaginary






7 VUID I VU grid identification number this corner

8 UNDEF(2 ) None

10 MSXR RS Membrane strain x RM

11 MSYR RS Membrane strain y RM

12 MXYR RS Membrane strain xy RM

13 UNDEF(3 ) None

16 BCXR RS Bending curvature x RM

17 BCYR RS Bending curvature y RM

18 BCXYR RS Bending curvature xy RM

19 TYZR RS Shear yz RM

20 TZXR RS Shear zx RM





21 UNDEF None

22 MSXI RS Membrane strain x IP

23 MSYI RS Membrane strain y IP

24 MXYI RS Membrane strain xy IP

25 UNDEF(3 ) None

28 BCXI RS Bending curvature x IP

29 BCYI RS Bending curvature y IP

30 BCXYI RS Bending curvature xy IP

31 TYZI RS Shear yz IP

32 TZXI RS Shear zx IP

33 UNDEF None


TCODE,7 =2 Random Response

2 UNDEF None

End TCODE,7

SCODE,6 =01 Stress

TCODE,7 =0 Real







8 Z1 RS Z1 fiber distance


10 NX1 RS Normal x at Z1

11 NY1 RS Normal y at Z1





12 TXY1 RS Shear xy at Z1

13 ANGLE1 RS Shear Angle at Z1 or n/a

14 MJRP1 RS Major principal at Z1 or n/a

15 MNRP1 RS Minor principal at Z1 or n/a

16 MAXSV1 RS vonMises/Max.Shear at Z1 or n/a


















10 NX1R RS Normal x rm at Z1

11 NX1I RS Normal x ip at Z1

12 NY1R RS Normal y rm at Z1

13 NY1I RS Normal y ip at Z1

14 TXY1R RS Shear xy rm at Z1





15 TXY1I RS Shear xy ip at Z1

16 NZ1R RS Normal z rm at Z1 or n/a

17 NZ1I RS Normal z ip at Z1 or n/a

18 TYZ1R RS Shear yz rm at Z1 or n/a

19 TYZ1I RS Shear yz ip at Z1 or n/a

20 TZX1R RS Shear zx rm at Z1 or n/a

21 TZX1I RS Shear zx ip at Z1 or n/a















2 UNDEF None

End TCODE,7

End SCODE,6


ELTYPE =190 Triangular shell view element (VUTRIA)





SCODE,6 =0 Strain

TCODE,7 =0 Real







8 NONE(2) I Nothing

10 MSX RS Membrane stain x

11 MSY RS Membrane strain y

12 MXY RS Membrane strain xy

13 NONE(3) RS Nothing

16 BCX RS bending curvature x

17 BCY RS Bending curvature y

18 BCXY RS Bending curvature xy

19 TYZ RS Shear yz

20 TZX RS Shear zx

21 NONE(3) RS Nothing








7 VUID I VU grid identification number this corner





8 UNDEF(2 ) None

10 MSXR RS Membrane strain x RM

11 MSYR RS Membrane strain y RM

12 MXYR RS Membrane strain xy RM

13 UNDEF(3 ) None

16 BCXR RS Bending curvature x RM

17 BCYR RS Bending curvature y RM

18 BCXYR RS Bending curvature xy RM

19 TYZR RS Shear yz RM

20 TZXR RS Shear zx RM

21 UNDEF None

22 MSXI RS Membrane strain x IP

23 MSYI RS Membrane strain y IP

24 MXYI RS Membrane strain xy IP

25 UNDEF(3 ) None

28 BCXI RS Bending curvature x IP

29 BCYI RS Bending curvature y IP

30 BCXYI RS Bending curvature xy IP

31 TYZI RS Shear yz IP

32 TZXI RS Shear zx IP

33 UNDEF None



2 UNDEF None

End TCODE,7

SCODE,6 =01 Stress

TCODE,7 =0 Real









2 UNDEF None

End TCODE,7

End SCODE,6

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

ELTYPE =269 Composite HEXA element (CHEXAL)

SCODE,6=0 Strain

TCODE,7 =0 Real

Q4CSTR=0 Center option


3 FLOC CHAR4 Fiber location (BOT, MID, TOP)

4 GRID I Edge grid ID (center=0)

5 E11 RS Normal strain in the 1-direction



8 E12 RS Shear strain in the 12-plane



11 ETMAX1 RS von Mises strain

Q4CSTR=1 Center and Corner option













11 ETMAX1 RS Von Mises strain

For each fiber location requested (PLSLOC), words 4 through 11 repeat 5 times.

TCODE,7 =1 Real/imaginary




4 GRID I Edge grid ID (Center = 0)

5 E11r RS Normal strain in the 1-direction, real part



8 E12r RS Shear strain in the 12-plane, real part



11 E11i RS Normal strain in the 1-direction, imaginary part



14 E12i RS Shear strain in the 12-plane, imaginary part

15 EL23i RS Shear strain in the 23-plane, imaginary part

16 EL13i RS Shear strain in the 13-plane, imaginary part















End TCODE,7

SCODE,6=1 Stress

TCODE,7 =0 Real





5 S11 RS Normal stress in the 1-direction



8 S12 RS Shear stress in the 12-plane



11 STMAX1 RS Von Mises stress





















5 S11r RS Normal stress in the 1-direction, real part



8 S12r RS Shear stress in the 12-plane, real part



11 S11i RS Normal stress in the 1-direction, imaginary part



14 S12i RS Shear stress in the 12-plane, imaginary part

















End TCODE,7

End SCODE,6

ELTYPE =270 Composite PENTA element (CPENTAL)

SCODE,6=0 Strain

TCODE,7 =0 Real



























End TCODE,7

SCODE,6=1 Stress

TCODE,7 =0 Real



























End TCODE,7

End SCODE,6

ELTYPE =304 Linear composite HEXA element (CHEXAL)

SCODE,6=0 Strain




4 EX1 RS Normal strain in the 1-direction

5 EY1 RS Normal strain in the 2-direction

6 EZ1 RS Normal strain in the 3-direction

7 ET1 RS Shear strain in the 12-plane

8 EL2 RS Shear strain in the 23-plane




SCODE,6=1 Stress




4 SX1 RS Normal stress in the 1-direction

5 SY1 RS Normal stress in the 2-direction




6 SZ1 RS Normal stress in the 3-direction

7 ST1 RS Shear stress in the 12-plane

8 SL2 RS Shear stress in the 23-plane


10 STMAX1 RS von Mises stress


End SCODE,6

ELTYPE =305 Linear composite PENTA element (CPENTAL)

SCODE,6=0 Strain












SCODE,6=1 Stress















End SCODE,6

ELTYPE =306 Nonlinear composite HEXA element (CHEXALN)

SCODE,6=0 Strain












SCODE,6=1 Stress















End SCODE,6

ELTYPE =307 Nonlinear composite PENTA element (CPENTALN)

SCODE,6=0 Strain












SCODE,6=1 Stress















End SCODE,6

ELTYPE =312 Axisymmetric tria element (TRAX3)

SCODE,6=0 Strain

TODE,7=0 Real

1 THETA RS Material orientation angle

2 CTYPE CHAR4 Grid or Gauss


4 EX RS Normal strain in the X-direction

5 EY RS Normal strain in the Y-direction

6 EZ RS Normal strain in the Z-direction

7 EXY RS Shear strain in the XY-plane

8 EYZ RS Shear strain in the YZ-plane

9 EZX RS Shear strain in the ZX-plane

10 EVM RS von Mises strain

Words 3 through 10 repeat 3 times.

SCODE,6=1 Stress

TCODE,7=0 Real







4 SX RS Normal stress in the X-direction

5 SY RS Normal stress in the Y-direction

6 SZ RS Normal stress in the Z-direction

7 SXY RS Shear stress in the XY-plane

8 SYZ RS Shear stress in the YZ-plane

9 SZX RS Shear stress in the ZX-plane

10 SVM RS von Mises stress


End SCODE,6

ELTYPE =313 Axisymmetric quad element (QUADX4)

SCODE,6=0 Strain

TODE,7=0 Real












SCODE,6=1 Stress

TCODE,7=0 Real















End SCODE,6

ELTYPE =314 Axisymmetric tria element (TRAX6)

SCODE,6=0 Strain

TODE,7=0 Real















SCODE,6=1 Stress

TCODE,7=0 Real












End SCODE,6

ELTYPE =315 Axisymmetric quad element (QUADX8)

SCODE,6=0 Strain

TODE,7=0 Real















SCODE,6=1 Stress

TCODE,7=0 Real












End SCODE,6

ELTYPE =316 Plane strain tria element (PLSTN3)

SCODE,6=0 Strain

TODE,7=0 Real















SCODE,6=1 Stress

TCODE,7=0 Real












End SCODE,6

ELTYPE =317 Plane strain quad element (PLSTN4)

SCODE,6=0 Strain

TODE,7=0 Real















SCODE,6=1 Stress

TCODE,7=0 Real












End SCODE,6

ELTYPE =318 Plane strain tria element (PLSTN6)

SCODE,6=0 Strain

TODE,7=0 Real















SCODE,6=1 Stress

TCODE,7=0 Real












End SCODE,6

ELTYPE =319 Plane strain quad element (PLSTN8)

SCODE,6=0 Strain

TODE,7=0 Real















SCODE,6=1 Stress

TCODE,7=0 Real












End SCODE,6

ELTYPE =320 Plane stress tria element (PLSTS3)

SCODE,6=0 Strain




TODE,7=0 Real












SCODE,6=1 Stress

TCODE,7=0 Real












End SCODE,6

ELTYPE =321 Plane stress quad element (PLSTS4)




SCODE,6=0 Strain

TODE,7=0 Real












SCODE,6=1 Stress

TCODE,7=0 Real












End SCODE,6




ELTYPE =322 Plane stress tria element (PLSTS6)

SCODE,6=0 Strain

TODE,7=0 Real












SCODE,6=1 Stress

TCODE,7=0 Real















End SCODE,6

ELTYPE =323 Plane stress quad element (PLSTS8)

SCODE,6=0 Strain

TODE,7=0 Real












SCODE,6=1 Stress

TCODE,7=0 Real















End SCODE,6

ELTYPE =328 Generalized plane strain tria element (GPLSTN3)

SCODE,6=0 Strain

TODE,7=0 Real












SCODE,6=1 Stress

TCODE,7=0 Real















End SCODE,6

ELTYPE =329 Generalized plane strain quad element (GPLSTN4)

SCODE,6=0 Strain

TODE,7=0 Real












SCODE,6=1 Stress

TCODE,7=0 Real















End SCODE,6

ELTYPE =330 Generalized plane strain tria element (GPLSTN6)

SCODE,6=0 Strain

TODE,7=0 Real












SCODE,6=1 Stress

TCODE,7=0 Real















End SCODE,6

ELTYPE =331 Generalized plane strain quad element (GPLSTN8)

SCODE,6=0 Strain

TODE,7=0 Real












SCODE,6=1 Stress

TCODE,7=0 Real















End SCODE,6

ELTYPE =337 Chocking triangular element (CHOCK3)

SCODE,6=0 Strain

TODE,7=0 Real












SCODE,6=1 Stress




TCODE,7=0 Real












End SCODE,6

ELTYPE =338 Chocking quad element (CHOCK4)

SCODE,6=0 Strain

TODE,7=0 Real















SCODE,6=1 Stress

TCODE,7=0 Real












End SCODE,6

ELTYPE =339 Chocking triangular element (CHOCK6)

SCODE,6=0 Strain

TODE,7=0 Real















SCODE,6=1 Stress

TCODE,7=0 Real












End SCODE,6

ELTYPE =340 Chocking quad element (CHOCK8)

SCODE,6=0 Strain

TODE,7=0 Real















SCODE,6=1 Stress

TCODE,7=0 Real












End SCODE,6


ELTYPE =347 Bar element for SOL 401 (CBAR)

SCODE,6=0 Strain

TCODE,7 =0 Real

2 GRID I External grid point ID

3 EXC RS Longitudinal strain at Point C

4 EXD RS Longitudinal strain at Point D

5 EXE RS Longitudinal strain at Point E





6 EXF RS Longitudinal strain at Point F


SCODE,6=1 Stress

TCODE,7 =0 Real


3 SXC RS Longitudinal stress at Point C

4 SXD RS Longitudinal stress at Point D

5 SXE RS Longitudinal stress at Point E

6 SXF RS Longitudinal stress at Point F


End SCODE,6


ELTYPE =348 Beam element for SOL 401 (CBEAM)

SCODE,6=0 Strain

TCODE,7 =0 Real


3 EXC RS Longitudinal strain at Point C

4 EXD RS Longitudinal strain at Point D

5 EXE RS Longitudinal strain at Point E

6 EXF RS Longitudinal strain at Point F


SCODE,6=1 Stress

TCODE,7 =0 Real


3 SXC RS Longitudinal stress at Point C

4 SXD RS Longitudinal stress at Point D





5 SXE RS Longitudinal stress at Point E

6 SXF RS Longitudinal stress at Point F


End SCODE,6


ELTYPE =349 Bushing element for SOL 401 (CBUSH1D)

SCODE,6=0 Strain

TCODE,7 =0 Real

2 ST RS Axial strain

SCODE,6=1 Stress

TCODE,7 =0 Real

2 ST RS Axial stress

End SCODE,6


ELTYPE =350 Spring element for SOL 401 (CELAS1)

SCODE,6=0 Strain

TCODE,7 =0 Real


SCODE,6=1 Stress

TCODE,7 =0 Real


End SCODE,6


ELTYPE =351 Spring element for SOL 401 (CELAS2)

SCODE,6=0 Strain





TCODE,7 =0 Real


SCODE,6=1 Stress

TCODE,7 =0 Real


End SCODE,6


ELTYPE =352 Bushing element for SOL 401 (CBUSH)

SCODE,6=0 Strain

TCODE,7 =0 Real

2 SXX RS Strain in x

3 SYY RS Strain in y

4 SZZ RS Strain in z

5 SXY RS Strain in xy

6 SYZ RS Strain in yz

7 SZX RS Strain in zx

SCODE,6=1 Stress

TCODE,7 =0 Real

2 SXX RS Stress in x

3 SYY RS Stress in y

4 SZZ RS Stress in z

5 SXY RS Stress in xy

6 SYZ RS Stress in yz

7 SZX RS Stress in zx

End SCODE,6





ELTYPE =355 Composite triangular shell element (CTRIA6)

SCODE,6=0 Strain

TCODE,7 =0 Real




5 EX1 RS Normal -1

6 EY1 RS Normal -2

7 EZ1 RS Normal -3

8 ET1 RS Shear-12

9 EL2 RS Shear-2Z

10 EL1 RS Shear-1Z

11 ETMAX1 RS von Mises


SCODE,6=1 Stress

TCODE,7 =0 Real




5 SX1 RS Normal -1

6 SY1 RS Normal -2

7 SZ1 RS Normal -3

8 ST1 RS Shear-12

9 SL2 RS Shear-2Z

10 SL1 RS Shear-1Z

11 TMAX1 RS von Mises






End SCODE,6


ELTYPE =356 Composite quadrilateral shell element (CQUAD8)

SCODE,6=0 Strain

TCODE,7 =0 Real




5 EX1 RS Normal -1

6 EY1 RS Normal -2

7 EZ1 RS Normal -3

8 ET1 RS Shear-12

9 EL2 RS Shear-2Z

10 EL1 RS Shear-1Z



SCODE,6=1 Stress

TCODE,7 =0 Real




5 SX1 RS Normal -1

6 SY1 RS Normal -2

7 SZ1 RS Normal -3

8 ST1 RS Shear-12

9 SL2 RS Shear-2Z





10 SL1 RS Shear-1Z



End SCODE,6


ELTYPE =357 Composite triangular shell element (CTRIAR)

SCODE,6=0 Strain

TCODE,7 =0 Real




5 EX1 RS Normal -1

6 EY1 RS Normal -2

7 EZ1 RS Normal -3

8 ET1 RS Shear-12

9 EL2 RS Shear-2Z

10 EL1 RS Shear-1Z



SCODE,6=1 Stress

TCODE,7 =0 Real




5 SX1 RS Normal -1

6 SY1 RS Normal -2





7 SZ1 RS Normal -3

8 ST1 RS Shear-12

9 SL2 RS Shear-2Z

10 SL1 RS Shear-1Z



End SCODE,6


ELTYPE =358 Composite quadrilateral shell element (CQUADR)

SCODE,6=0 Strain

TCODE,7 =0 Real




5 EX1 RS Normal -1

6 EY1 RS Normal -2

7 EZ1 RS Normal -3

8 ET1 RS Shear-12

9 EL2 RS Shear-2Z

10 EL1 RS Shear-1Z



SCODE,6=1 Stress

TCODE,7 =0 Real








5 SX1 RS Normal -1

6 SY1 RS Normal -2

7 SZ1 RS Normal -3

8 ST1 RS Shear-12

9 SL2 RS Shear-2Z

10 SL1 RS Shear-1Z



End SCODE,6


ELTYPE =363 Rod element for SOL 402 (CROD)

SCODE,6=0 Strain

TCODE,7 =0 Real


3 AE RS Axial strain

4 TE RS Torsional strain


SCODE,6=1 Stress

TCODE,7 =0 Real


3 AE RS Axial stress

4 TE RS Torsional stress


End SCODE,6




OGF




2 TCODE(C) I Table code; always 19

3 UNDEF None


TCODE,1=01

ACODE,4=0

5 UNDEF(2) None Not defined

ACODE,4=01 Statics

5 UNDEF None See word 8

6 UNDEF None

ACODE,4=02 Real Eigenvalues

5 MODE I Mode Number

6 UNDEF None

ACODE,4=03 Differential Stiffness 0


6 UNDEF None

ACODE,4=04 Differential Stiffness 1


6 UNDEF None

ACODE,4=05 Frequency

5 FREQ RS Frequency

6 UNDEF None


5 TIME RS Time step

6 UNDEF None





ACODE,4=07 Buckling 0 (Pre-buckling)


6 UNDEF None

ACODE,4=08 Buckling 1 (Post-buckling)

5 MODE I Mode number

6 UNDEF None

ACODE,4=09 Complex Eigenvalues


6 UNDEF None

ACODE,4=10 Nonlinear Statics (Sol 106)

5 LFTSFQ RS Load factor

6 UNDEF None

ACODE,4=11 Geometric Nonlinear Statics


6 UNDEF None

ACODE,4=12 CONTRAN

5 TIME RS Time step

6 UNDEF None

End ACODE,4

TCODE,1=02

5 EKEY I Device code + 10*Point ID

6 EID I Element identification number if element force,otherwise zero

End TCODE,1

7 UNDEF None

8 LOADSET I Load set or zero

9 FCODE I Format Code





10 NUMWDE(C) I Number of words per entry in DATA record

11 ELNAME(2) CHAR4 UNDEF(2) if SORT1. Element name ifSORT2: APP-LOAD, F-OF-SPC, F-OF-MPC,or *TOTALS*

13 SETID I Set identification number

14 EIGENR RS Natural eigenvalue – real part

15 EIGENI RS Natural eigenvalue – imaginary part

16 FREQ RS Natural frequency

17 UNDEF(6) None

23 THERMAL I THERMAL = 1 for heat transfer; = 2 foraxisymmetric Fourier; = 3 for cyclic symmetric;= 0 otherwise

24 UNDEF(2) None

26 HINDEX I Harmonic index

27 SCFLAG I Sine/cosine flag. SCFLAG = 0 for 0thharmonic; = 1 for cosine component; = 2for sine component; = -1 (default) for othersolution type output


29 AL_TOTAL RS Accumulated arc-length for SOL401 arc-lengthonly

30 UNDEF(21) None






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

NUMWDE =8 Real - SORT2

TCODE,1 =1 SORT1





2 EID I Element identification number if element force;otherwise zero

3 ELNAME(2) CHAR4 Element name, APP-LOAD, F-OF-SPC,F-OF-MPC, or *TOTALS*

5 F1 RS Force in displacement coordinate systemdirection 1



8 M1 RS Moment in displacement coordinate systemdirection 1



TCODE,1 =02 SORT2 - Swap with word 5 of IDENT

2 GCHAR CHAR4 G







End TCODE,1

NUMWDE =10 Real - SORT1

TCODE,1 =1 SORT1














2 GCHAR CHAR4 G







End TCODE,1

NUMWDE =14 Complex - SORT2

TCODE,1 =1 SORT1







5 F1R RS Force in displacement coordinate systemdirection 1 - real part



8 M1R RS Moment in displacement coordinate systemdirection 1 - real part



11 F1I RS Force in displacement coordinate systemdirection 1 - imaginary part



14 M1I RS Moment in displacement coordinate systemdirection 1 - imaginary part




2 GCHAR CHAR4 G

















End TCODE,1

NUMWDE =16 Complex - SORT1

TCODE,1 =1 SORT1




















2 GCHAR CHAR4 G

















End TCODE,1

End NUMWDE

OJINT





3 UNDEF None

4 SUBCASE I Subcase or Random identification number

ACODE=06 Transient

5 TIMESTEP RS Current time step

6 UNDEF(4) None





8 UNDEF(2) None





End ACODE


11 UNDEF(40) None




OPG



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

2 TCODE(C) I Table Code; 2 for OPG, 52 for OGFFRF

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

ACODE =10 Nonlinear statics




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

OPRESS




2 TCODE(C) I Table Code

3 ELTYPE I Element Code

4 SUBCASE I Subcase ID





ACODE=06 Transient




End ACODE

6 PCODE(C) I PLOAD Code

ACODE=06 Transient

7 UNDEF(3) None


7 TIMESTEP RS Time for SOL 401 arc-length only


9 UNDEF None

End ACODE


11 UNDEF(40) None




OQG



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

ACODE =10 Nonlinear statics








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



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

MPCFORCE =1 MPC forces

TCODE,7 =1 Real/Imaginary

2 TYPE I Point type: 1->G for grid and 2->S for scalar

3 QF1R RS Constraint force in direction 1 - Real



6 QM1R RS Constraint moment in direction 1 - Real



9 QF1I RS Constraint force in direction 1 - Imaginary



12 QM1I RS Constraint moment in direction 1 - Imaginary



TCODE,7 ≠1 Real or Random


3 QF1 RS Constraint force in direction 1







6 QM1 RS Constraint moment in direction 1



End TCODE

MPCFORCE =0 SPC forces

TCODE,7 =1 Real/Imaginary














TCODE,7 ≠1 Real or Random












End TCODE

End MPCFORCE

OSHT



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

ELTYPE=343 CTRIA6

1 EKEY I

2 TERM CHAR4 “CEN”

3 GRID I Grid identification number; 0 for centroid

4 THICK RS Thickness


ELTYPE=344 CQUAD8

1 EKEY I





ELTYPE=345 CTRIAR

1 EKEY I









ELTYPE=346 CQUADR

1 EKEY I





OSLIDE



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





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

OSPDS





64 for Initial Separation Distance

65 for Deformed Separation Distance

3 UNDEF None


TCODE,1=1 SORT1





ACODE,4=01 SOL 101 linear statics


6 UNDEF(2) None

ACODE,4=06 401 non arc-length

5 TIME RS Time step

6 UNDEF(2) None

ACODE,4=10 401, 601, and 701 nonlinear statics




End ACODE

TCODE,1=2 SORT2


6 UNDEF(2) None

End TCODE




11 UNDEF None


13 UNDEF(38) None







OTEMP




2 TCODE(C) I Table code

3 UNDEF None

4 SUBCASE I Subcase or Random identification number

ACODE=06 Transient


6 UNDEF(3) None





8 UNDEF None

End ACODE



11 UNDEF(40) None




OUG



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





ACODE,4 =10 Nonlinear statics




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

14 SFFLAG I Structure/fluid flag: -1 for displacement, 0 forboth/old version, 1 for pressure only

15 UNDEF(2) None

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

OUGGC



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

3 GCODE I Grid contribution code: +/-1=absolute,+/-2=norm

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

OUGPC



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

3 PCODE I Panel contribution code: +/-1=absolute,+/-2=norm

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




OUGRC



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

3 PCODE I Reciprocal panel contribution code: +/-1=abs,+/-2=norm

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

OUMAT





3 ELTYPE(C) I Element Type

4 SUBCASE I Subcase ID

ACODE=06 Transient


6 UNDEF(4) None





8 UNDEF(2) None

End ACODE

10 NUMWDE I Number of grids written to the DATA record

11 GGOPT I Grid/Gauss option: =0 for grid; =1 for Gauss

12 UNDEF(39) None










ELTYPE = 335 CHEXCZ

2 EID I Element ID

3 MATID I Material ID

4 NVPG I Number of values per grid or Gauss point

5 GRID I Grid or Gauss point

6 SVI I State variable index

7 SVV RS State variable value




ELTYPE = 336 CPENTCZ

2 EID I Element ID









ELTYPE = 343 CTRIA6N





2 EID I Element ID









ELTYPE = 344 CQUAD8N

2 EID I Element ID









ELTYPE = 345 CTRIARN

2 EID I Element ID













ELTYPE = 346 CQUADRN

2 EID I Element ID








R1TAB

Updated Record – REPEAT


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

Type = 17 CMPLNCE

8 UNDEF(2) None

10 UNDEF None SEID,I not yet supported for Cmplnce DRESP1

11 UNDEF(2) None

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

New data blocks

ATVMAP

Table of mapping vector of the microphone grids and fluid grids on the structural-fluid interfacefor ATV analysis.




Record 0 – HEADER


1 NAME(2) CHAR4 Data block name

Record 1 – ROWMAP


1 EXTID I Microphone point external ID

Word 1 repeats until End of Record

Record 2 – COLMAP


1 EXTID I Interface point external ID


Record 5 – TRAILER


1 NROW I Number of rows in ATV matrix

2 NCOL I Number of columns in ATV matrix

3 UNDEF(4) None

OACPWRI

Incident acoustic power

Record - HEADER



Record - IDENT








3 DATCOD I Data code; 10*SID+1 for GROUP, 10*SID+2for FACES

4 SUBCAS I Subcase ID




5 SID I GROUP or FACES set ID

End TCODE,1

6 UNDEF None

7 RCODE I Random ID

8 UNDEF None


10 NUMWDE I Number of words per entry in DATA record= 3

11 UNDEF(40) None




Record - DATA



1 SID I GROUP or FACES set ID



End TCODE,1






2 IPWR RS Incident acoustic power

TCODE,7 = 1 Real/Imaginary

2 IPWRR RS Incident acoustic power - real part

3 IPWRI RS Incident acoustic power - imaginary part

End TCODE,7

Record - TRAILER


1 NUMREC I Number of records

2 UNDEF(5) None

OACPWRT

Transmitted acoustic power

Record - HEADER



Record - IDENT




3 DATCOD I Data code; 10*SID for AMLREG, 10*SID+1for GROUP





5 SID I AMLREG or GROUP ID





End TCODE,1

6 UNDEF None

7 RCODE I Random ID

8 UNDEF None



11 UNDEF(40) None




Record - DATA



1 SID I AMLREG or GROUP ID



End TCODE,1


2 TPWR RS Transmitted acoustic power

TCODE,7 = 1 Real/Imaginary

2 TPWRR RS Transmitted acoustic power - real part

3 TPWRI RS Transmitted acoustic power - imaginary part

End TCODE,7




Record - TRAILER



2 UNDEF(5) None

OACTRLS

Acoustic power transmission loss

Record - HEADER



Record - IDENT




3 IDATCOD I Data code for incident power; 10*ISID+1 forGROUP, 10*ISID+2 for FACES





5 ISID I GROUP or FACES set ID for incident power

End TCODE,1

6 TDATCOD I Data code for transmitted power; 10*TSIDfor AMLREG, 10*TSID+1 for GROUP

7 RCODE I Random ID

8 TSID I AMLREG or GROUP set ID for transmittedpower







11 UNDEF(40) None




Record - DATA



1 ISID I GROUP or FACES set ID for incident power



End TCODE,1

2 TRLS RS Acoustic transmission loss in decibels =10*log10(|incident/transmitted| ) or PSDF

Record - TRAILER



2 UNDEF(5) None

OBCKL

Table of load factor versus arc-length from SOL 401

Record 0 – HEADER



3 WORD I No Def or Month, Year, One, One




Record 1 – IDENT


1 ACODE I Device code + 10*Approach code (always10 for nonlinear statics)


3 UNDEF None


5 TIME RS Time Step

6-8 UNDEF(3) None

9 FCODE RS Format code

10 NUMWDE I Number of words per entry in DATA record(always 2 words)

11-50 UNDEF(40) None

51-82 TITLE(32) CHAR4 Title character string (TITLE)

83-114 SUBTITL(32) CHAR4 Subtitle character string (SUBTITLE)

115-146 LABEL(32) CHAR4 LABEL character string (LABEL)

Record 2 – DATA


1 AL I Arc length

2 LF I Load factor

Record 3 – TRAILER


1 UNDEF(6) None

OCONST

Table of contact node/grid status




Record - HEADER





Record - IDENT




3 UNDEF None


TCODE,1 =1 Sort 1

ACODE,4 =01 Statics


6 UNDEF(2) None

ACODE,4 =02 Real eigenvalues


6 EIGN RS Eigenvalue

7 MODECYCL RS Mode or cycle

ACODE,4 =03 Differential stiffness


6 UNDEF(2) None

ACODE,4 =04 Differential stiffness


6 UNDEF(2) None

ACODE,4 =05 Frequency

5 FREQ RS Frequency





6 UNDEF(2) None

ACODE,4 =06 Transient

5 TIME RS Time step

6 UNDEF(2) None

ACODE,4 =07 Buckling Phase 0 (Pre-buckling)

5 LSDVMN I Load set

6 UNDEF(2) None

ACODE,4 =08 Buckling Phase 1 (Post-buckling)

5 LSDVMN I Mode number

6 EIGR RS Eigenvalue

7 UNDEF None

ACODE,4 =09 Complex eigenvalues

5 MODE I Mode

6 EIGR RS Eigenvalue (real)

7 EIGI RS Eigenvalue (imaginary)

ACODE,4 =10 Nonlinear statics

5 LFTSFQ RS Load step



ACODE,4 =11 Old geometric nonlinear statics

5 LSDVMN I Load set

6 UNDEF(2) None

ACODE,4 =12 CONTRAN (Can appear as ACODE=6)

5 TIME RS Time

6 UNDEF(2) None

End ACODE,4





TCODE,1 =02 Sort 2


6 UNDEF(2) None

End TCODE,1

8 LSDVMN I Load set



11 UNDEF None


13 UNDEF(38) None




Record - DATA


TCODE,1 =01 Sort 1

1 EKEY I Device code + 10* Point identification number

TCODE,1 =02 Sort 2 - Swap with word 5 of IDENT

ACODE,4 =01


ACODE,4 =02


ACODE,4 =03


ACODE,4 =04






ACODE,4 =05

1 FREQ RS Frequency

ACODE,4 =06

1 TIME RS Time step

ACODE,4 =07


ACODE,4 =08


ACODE,4 =09


ACODE,4 =10

1 FQTS RS Frequency or time step

ACODE,4 =11


ACODE,4 =12


End ACODE,4

End TCODE,1

2 I1 I Contact node/grid status

3 UNDEF(2) None

Record - TRAILER


1 UNDEF(6) None

ODAMGPFR

Table of crack density for ply failure EUD model from SOL 401.

Crack density at corner grids on middle, and the values are unitless.




Record – HEADER




Record – IDENT



2 TCODE I Table code 88



TCODE,1 = 01 Sort 1



6 UNDEF(4) None





8-9 UNDEF(2) None

End ACODE,4

TCODE,1 = 02 Sort 2

End TCODE,1


11 UNDEF(40) None








Record – DATA


ELTYPE=267, 268, 355,356, 357, or 358

ELTYPE=267 - Composite HEXA element (CHEXAL)

ELTYPE=268 - Composite PENTA element (CPENTAL)

ELTYPE=355 - Composite triangular shell element (CTRIA6)

ELTYPE=356 - Composite quadrilateral shell element (CQUAD8)

ELTYPE=357 - Composite triangular shell element (CTRIAR)

ELTYPE=358 - Composite quadrilateral shell element (CQUADR)



3 GRID I External grid identification number

4 CRKD RS Crack density value

On each ply, words 3 and 4 repeat for each corner grid point. (4 corners for composite HEXA andCQUADi elements, 3 corners for composite PENTA and CTRIAi elements.)

Record – TRAILER


1 UNDEF(6) None

OEFMXORD

Maximum frequency per element and element order contribution in SOL 108 FEMAO analysis

Record – HEADER


1 NAME(2) CHAR4 Data block Name






Record – IDENT


1 UNDEF(50) None




Record - DATA


1 QUALTYPE(C) I Quality type

QUALTYPE = 01 Maximum frequency

2 NELEM I Number of elements

3 EID I Element ID

4 FREQ RS Maximum frequency for element ID

Words 3 and 4 repeat until -1 occurs

QUALTYPE = 02 Element order contribution

2 NORDER I Number of orders

3 NFREQ I Number of frequencies

4 FREQ RS Frequency


Record – TRAILER



2 UNDEF(5) None

ONMD

Normalized material density for topology optimization output.




Record – HEADER



Record – IDENT



2 TCODE(C) I Table code 92

3 UNDEF(3) None

6 DCYCLE I Design cycle number

7 ROBJ RS Objective value

8 RCON RS Critical constraint value

9 UNDEF None

10 NUMWDE I Number of words per entry in DATA record(always 2)

11 UNDEF(40) None




Record – DATA


1 EKEY I Device code + 10*Element ID

2 VALUE RS Scalar value for element

Record – TRAILER


1 WORD1 I 2*number of elements

2 UNDEF(5) None




TRMBD

Table of Euler Angles for transformation from material to basic coordinate system in the deformedconfiguration.

Record – HEADER




Record – IDENT






TCODE,1 = 1 Sort 1

ACODE,4 = 02 Real eigenvalues

5 UNDEF(5) None



6 UNDEF(4) None





8 UNDEF(2) None

End ACODE,4

TCODE,1 = 02 Sort 2





End TCODE,1


11 UNDEF(40) None




Record – DATA




3 AX RS Euler angle X

4 AY RS Euler angle Y

5 AZ RS Euler angle Z

Words 2 thru 5 repeat for each end or corner grid point (for example, 8 grids for CHEXA, 6 gridsfor CPENTA, 2 grids for CBAR, 4 grids for CQUADX4 )

Record – TRAILER


1 UNDEF(6) None

TRMBU

Table of Euler Angles for transformation from material to basic coordinate system in the undeformedconfiguration

Record – HEADER







Record – IDENT


1 ACODE I Device code + 10*Approach code = 60 +iand (print, plot)




5 TIME RS Time Step

6-9 UNDEF(4) None


11-50 UNDEF(40) None

51-82 TITLE(32) CHAR4 Title character string (TITLE)

83-114 SUBTITL(32) CHAR4 Subtitle character string (SUBTITLE)

115-146 LABEL(32) CHAR4 LABEL character string (LABEL)

Record – DATA



2 AX RS Euler Angle X

3 AY RS Euler Angle Y

4 AZ RS Euler Angle Z

Record – TRAILER


1 UNDEF(6) None




Updated modules

ADDVM

Updated Format:

ADDVM VEC,MAT/MATO/ICOL/IOPT/NCOL/ICOL_MAT $

New Parameter:

ICOL_MAT Input-integer-default=1. Identifies the column number of matrix MATI to whichinput vector VEC is added or subtracted

BOLTFOR

Updated Format:

BOLTFOR CASECC,BGPDT,CSTM,GEOM3,ECT,EDT,SIL,SBDATA,EST,PGBOLT,USET1,YSGL/BTFG,ELIST,SEQBG,PGBOLT1,USETB,YSGB/NSKIP/NDOFG/S,N,NBOLTS/S,N,SEQUFLG/S,N,NSEQU/PGRED $

New Input Data Blocks:

EST Element summary table

PGBOLT Glue forces in the model including the bolt cut

USET1 Set definition table

YSGL Enforced displacement table in g-set

New Output Data Blocks:

SEQBG Table of BOLTSEQ bolt IDs which are sequenced in the current step

PGBOLT1 Glue forces only at the bolt cut for those bolts which are not being tightened

USETB USET updated with enforced displacement bits at bolt cut (DISP option in BOLTbulk entry)

YSGB YS updated with enforced displacement values at bolt cut (DISP option in BOLTbulk entry)




New Parameters:

SEQUFLG Input-integer-default=0. BOLTSEQ flag indicating if sequenced (1) or not (0)

NSEQU Input-integer-no default. Number of bolt sequences done

PGRED Input-integer-no default. Flag indicating if PGBOLT is to be reduced to PGBOLT1(1-yes/0-no)

CNTMAPTR

Updated Format:

CNTMAPTR CNELM,INPUT,UGCB,BGPDT,INPUT2,CNELMT/OUTPUT/IOPT/LGDISP $


INPUT2 Table of tractions or slip at contact element locations from prior contact pairingupdate

CNELMT Contact element definition table from previous geometry update

CNTSTAT

Updated Format:

CNTSTAT CNELM,ECSTAT,DLAMDA,TLAMDA,PLAMDA,UGCP,UGCB,BGPDT,OFFSETP,ELSLIP/ECSTAT2,TLAMDAM/S,N,CITO/CNTNINC/S,N,NCS0/S,N,NCS1/S,N,NCS2/S,N,NCS3/S,N,NCSC/CNTCONV/S,N,NOGSET/LGDISP/SEQDEPFL/CNTNSUB/ANAI/RSTIME $

New Input Data Block:

UGCP Matrix of previous converged time step displacements

Changed Parameters:

• The 8th input data block changes from GEOMUPDT to CNTCONV.

New Parameters:

CNTCONV Input-integer-no default. Convergence flag=0 the current step is not converged=1 beginning of a new step after convergence

CNTNSUB Input-integer-no default. Subcase counter

ANAI Input-integer-no default. Analysis type




RSTIME Input-real-no default. Current time

CONSTF

Updated Format:

CONSTF CNELM,BGPDT,CSTM,UGCB,ECSTAT,TLAMDA,UGCD,PLAMDA,ELSLIP,OFFSETP,DLAMDA/KELMC,KDICTC/GSIZE/LGDISP/IOPT/CNTNINC/DELTIME/CITO/SCINIT/SCENDT/RSTIME/CNTNSUB/CNTSTPS/ANAI $


OFFSETP Table of offsets from prior subcase

DLAMDA Matrix of augmented contact elements tractions

New Parameters:

DELTIME Input-real-no default. Time increment

CITO Input-integer-no default. Contact outer loop ID

SCINIT Input-real-no default. Subcase start time

SCENDT Input-real-no default. Subcase end time

RSTIME Input-real-no default. Current time

CNTNSUB Input-integer-no default. Subcase counter

CNTSTPS Input-integer-no default. Number of increments in the current subcase

ANAI Input-integer-no default. Analysis type

CONTOUT

Updated Format:

CONTOUT CNELM,ECDISP,CASESX2H,ECSTAT,ECDISD,BGPDT,CNTPENTR,UGC,ISLIP,TFSLIP/OSPDS1,OSLIDE1,OCONST1/NVEC/DMAPNO/RSTIME/LGDISP/ANAI/LDFACAL/ARCLNTH $

New Parameters:

ANAI Input-integer-default=1. Analysis type flag used in SOL 401. ANAI=4 indicates aSOL 401 arc-length solution




LDFACAL Input-real-no default. Load factor for SOL 401 arc-length solution

ARCLNTH Input-real-no default. Cumulative arc-length SOL 401 arc-length solution

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,GCMMAI, DSVCSV, XLURNG, XOTSID, CNTBSV,CVALSV, UVLCIN,XUPDMF,CONTEL,DLKCON/XO,CVALO,R1VALO,R2VALO,PROPO,R3VALO,GCMMAO, XNRANG, DESVEC, UVLCOT/OBJIN/S,N,OBJOUT/PROTYP/PROPTN/PBRPROP/DESMAX/ DESCYCLE/ S,N,FLGINT//UNUSED5/UNUSED6/UNUSED7/UNUSED8/UNUSED9/UNUSED10 $


XUPDMF Design variables values array updated based on manufacturing constraints

CONTEL DVTREL1 bulk data based continuum elements information

DLKCON Table of dependent design variable IDs based on user prescribed linkingto separate them from any symmetry linking. Does not exist if no topologyoptimization or no planar symmetry constraint

DOM10

Updated Format:

DOM10 DESTAB,XINIT,X0,CNTABRG,CVALRG,CVALO,DVPTAB*,PROPI*,PROPO*,R1TABRG,R1VALRG,R1VALO,RSP2RG,R2VALRG,R2VALO,OPTPRMG,OBJTBG,DRSTBLG,TOL1,FOL1,FRQRPRG,DBMLIB,BCON0,BCONXI,WMID,RSP3RG,R3VALRG,R3VALO,EDT,HIS,CONTEL//DESCYCLE/DESMAX/OBJIN/OBJOUT/EIGNFREQ/PROTYP/RESTYP/NASPDV $

Updated Input Data Block:

CONTEL DVEREL1 or DVTREL1 bulk data based continuum elements information.




Note

The SHELDT input data block is renamed CONTEL. This is a documentation correctiononly.

New Parameter:

NASPDV Input-integer-default=0. Design variable output control=0 to suppress output of design variable information to the .f06 file=1 to output design variable information to the .f06 file

Updated Examples:

In each code example, six commas are added after the WMIDG data block.

Note

This is a documentation correction only.

DOM12

Updated Format:

DOM12XINIT,XO,CVAL,PROPI*,PROPO*,OPTPRM,HIS,DESTAB,GEOM1N,COORDO,EDOM,MTRAK,EPT,GEOM2,MPT,EPTTAB*,DVPTAB*,XVALP,GEOM1P,R1TABRG,R1VALRG,RSP2RG,R2VALRG,PCOMPT,OBJTBG,ALBULK,AMLIST,DIT,CNTABRG,CONTEL,CASEXX,XBEST,PBESTF,XUPDMF/HISADD,NEWPRM,DBCOPT,NEWDES,XNTSID,OSHT1,ELRSCALV/DESCYCLE/OBJIN/OBJOUT/S,N,CNVFLG/CVTYP/OPTEXIT/DESMAX/MDTRKFLG/DESPCH/DESPCH1/MODETRAK/EIGNFREQ/DSAPRT/PROTYP/BADMESH/XYUNIT/FSDCYC/S,N,FLGINT/POST/S,N,ISBEST/OBJBEST/NASPDV/BDMNCON $


CONTEL Element ID vs. design variable ID information

Note

The SHELDT input data block is renamed CONTEL. This is a documentation correctiononly.





CASEXX Case control data block

XBEST Design variables values array for best design cycle so far

PBESTF Family of data blocks with arrays of designed property values for best designcycle so far

XUPDMF Design variables values array updated based on manufacturing constraints

New Output Data Block:

ELRSCALV Element normalized mass densities data block in topology optimization

New Parameters:

ISBEST Output-integer-no default

0 This is not the best design so far

1 This is the best design so far

OBJBEST Output-real-no default. Objective function value for the best design so far

NASPDV Input-integer-default=0. Design variable output control

0 Suppress output of design variable information to the .f06 file

1 Output design variable information to the .f06 file

BDMNCON Input-integer-default=the lesser of 10 or (DESMAX-3), but no less than 2.Starting design cycle for application of manufacturing constraints, except forplanar symmetry

DOPR1

Updated Format:

DOPR1EDOM,EPT,DEQATN,DEQIND,GEOM2,MPT,CASEXX,DIT,EDT,CONELS,ECT,BGPDT/DESTAB,XZ,DXDXI,DTB,DVPTAB*,EPTTAB*,CONSBL*,DPLDXI*,PLIST2*,XINIT,PROPI*,DSCREN,DTOS2J*,OPTPRM,CONS1T,DBMLIB,BCON0,BCONXI,DMATCK,DISTAB,CASETM,SPAN23,MFRDEP,DESVUP,EDOMNU,GEOM2N,ECTNU,EPTNU,CONTEL,MPTNU,DLKCON/S,N,MODEPT/S,N,MODGEOM2/S,N,MODMPT/DPEPS/S,N,PROTYP/S,N,DISVAR/S,N,IDVTRL/NASPRT $





CONELS Temporary data block which contains DVEREL1 bulk data supported shell, orDVTREL1 supported shell and solid elements information.

Note

The SHLLDT input data block is renamed CONELS. This is a documentation correctiononly.


BGPDT Basic grid point definition table

Updated Output Data Block:

CONTEL DVEREL1 or DVTREL1 bulk data based continuum elements information.

Note

The SHELDT output data block is renamed CONTEL. This is a documentation correctiononly.


MPTNU Temporary, updated version of MPT data block.

DLKCON Table of dependent design variable IDs based on user prescribed linkingto separate them from any symmetry linking. Does not exist if no topologyoptimization or no planar symmetry constraint

New Parameters:

IDVTRL Output-integer-default=0

1 If there is any DVTREL1 bulk entries in the input deck

2 After topology optimization related elements are determined

NASPRT Input-integer-no default. NASPRT bulk data parameter (data recoveryfrequency)




DPD

Updated Format:

DPD DYNAMIC,GPL,SIL,USET,CASECC,PG,PKYG,PBYG,PMYG,YG,SLT,GEOM4/GPLD,SILD,USETD,TFPOOL,DLT,PSDL,RCROSSL,NLFT,TRL,EED,EQDYN/LUSET/S,N,LUSETD/S,N,NOTFL/S,N,NODLT/S,N,NOPSDL/DATAREC/S,N,NONLFT/S,N,NOTRL/S,N,NOEED/UNUSED10/S,N,NOUE/UNUSED12/SEID/KSKIP $

New Parameter:

KSKIP Input-integer-default=0. Controls reading GEOM4 and storing SPCDinformation=0 to read GEOM4 and store SPCD information=1 to not read GEOM4 and not store SPCD information

ELTPRT

Updated Format:

ELTPRT ECT,GPECT,BGPDT,NSMEST,EST,CSTM,MPT,DIT,CASECC,EPT,COMPEST,CMPGEST/VELEM,CONELS/PROUT/S,N,ERROR/WTMASS $


CMPGEST Composite shell element summary table

Updated Output Data Block:

CONELS Temporary data block to be later used for input to DOPR1 module call. It containsDVEREL1 bulk data supported shell, or DVTREL1 supported shell and solidelements information.

Note

The SHLLDT output data block is renamed CONELS. This is a documentation correctiononly.




EMAAC

Updated Format:

EMAAC DIT/KGGF,K4GGF,MGGF,BGGF/S,N,NOKGGF/S,N,NOK4GGF/S,N,NOMGGF/S,N,NOBGGF/FREQ/LUSET


DIT Direct input tables

EMG

Updated Format:

EMG EST,CSTM,MPT,DIT,CASECC,UG,ETT,EDT,DEQATN,DEQIND,BGPDT,GPSNT,ECTA,EPTA,EHTA,DITID,EBOLT,COMPEST,EFILL,PCOMPT,EPT,CMPGEST/KELM,KDICT,MELM,MDICT,BELM,BDICT,ELMMOD,CONFAC2/S,N,NOKGG/S,N,NOMGG/S,N,NOBGG/S,N,NOK4GG/S,N,NONLHT/COUPMASS/TEMPSID/DEFRMSID/PENFAC/IGAPS/LUMPD/LUMPM/MATCPX/KDGEN/TABS/SIGMA/K6ROT/LANGLE/NOBKGG/ALTSHAPE/PEXIST/FREQTYP/FREQVAL/FREQWA/UNSYMF/S,N,BADMESH/DMGCHK/BOLTFACT/REDMAS/TORSIN/SHLDAMP/SHLDMP/BSHDMP/LMSTAT/LMDYN/STFOPTN/MODOPTN/HINDEX/HOOPDOF/ISPCSTR$



FOCOEL

Updated Format:

FOCOEL CASECC,BGPDT,CSTM,GEOM2,EST,MPT,CONTACT,SIL,GPSNTC,UGCB,GEOM4,FEPEN,UGCP,ELMMOD/CNELM,GPECTC,SPCCY/NSKIP/OPTION/NLHEAT/GSIZE/S,N,REFOPT/S,N,CNTSET/S,N,NCELS/S,N,MAXO/S,N,MAXI/CNTS/S,N,AITK/S,N,MPLI/S,N,RESET/S,N,FRICTM////S,N,CTOL/CNTLOOP/LGDISP/S,N,NSEGCYC/S,N,CYCAXID/FSYMTOL $


ELMMOD Element modulus table




FONOTR

Updated Format:

FONOTR CNELM,ECSTAT,ELAMDA,CASESX/OQGCFF1,OBC1,CONFON,ELTRCT/NROW/NVEC/DMAPNO/RSTIME/LGDISP/FLAG/ANAI/LDFACAL/ARCLNTH $

New Parameters:

FLAG Input-integer-no default. Output flag=1 to recover OQGCF1, OBC1, and CONFON outputs=2 to generate ELTRCT for traction mapping purposes in SOL 401

ANAI Input-integer-default=1. Analysis type flag used in SOL 401. ANAI=4 indicates aSOL 401 arc-length solution

LDFACAL Input-real-no default. Load factor for SOL 401 arc-length solution

ARCLNTH Input-real-no default. Cumulative arc-length SOL 401 arc-length solution

FRRD1

Updated Format:

FRRD1 CASECC,DIT,KXX,BXX,MXX,K4XX,PXF,FRL,FOL,EDT,SILD,USETD,PARTVEC/UXF,FOLT,FBSOUT/SOLTYP/NONCUP/ITSEPS/ITSMAX/NSKIP/FRRD1SEL/S,N,FIRSTBAD/SETNAME/FREQDEP/FRQLOOP $


FBSOUT Nonstandard lower triangular factor for Iterative or Krylov method options

New Parameter:

FRQLOOP Input-integer-default=0. The number of the current frequency loop. If FRQLOOP> 1, there is no solver duplicated information message output.

GP1

Updated Format:

GP1 GEOM1,GEOM2,GEOM3,GDNTAB,MEDGE,SGPDT,DYNAMIC/GPL,EQEXIN,GPDT,CSTM,BGPDT,SIL,VGF,GEOM3B,DYNAMICB/S,N,LUSET/S,N,NOCSTM/S,N,NOPOINTS/UNIT/UPERM/UPRMT/NUFLAG/SEID/NUMLM/IMPRFSET $




New Parameter:

IMPRFSET Input-integer-default=0. Imperfection set ID from case control. Applicable forSOL 401 only

GP3

Updated Format:

GP3 GEOM3,EQEXIN,GEOM2,EDT,UGH,ESTH,BGPDTH,CASEHEAT,CASECC,GEOM5,CSTMS/SLT,ETT,CASECCN/S,N,NOLOAD/S,N,NOGRAV/S,N,NOTEMP $


CSTMS Table of coordinate system transformation matrices

GPAC

Updated Format:

GPAC EQEXIN,BGPDT,GEOM1,SIL,EPT,ECT,MPT,CONTACT,VGF,GPL,GPDT,DIT/VGFO,SILO,EQEXINO,BGPDTO,GPLO,GPDTO,VGFDAML,VGFCG,VGFP,/LUSET/S,N,AMLDOF/SEID/REENTRY//GFL $


VGFP Partition vector for DOFs on which ACPRESS is applied

New Parameter:

GFL Input-real-no default. The uniform fluid damping coefficient

GPFDR

Updated Format:

GPFDR CASECC,UG,KELM,KDICT,ECT,EQEXIN,GPECT,PG,QG,BGPDT,{LAMA or FOL or TOL or OLF},CSTM,VELEM,PTELEM,QMG,NFDICT,FENL,MELM,MDICT,BELM,BDICT,MDLIST,LDFACAL,CUMMAL/ONRGY1,OGPFB1,OEKE1,OEDE1/APP/TINY/XFLAG/CYCLIC/WTMASS/S,N,NOSORT2/HINDEX/SCFLAG/CYC_SUBCAS $


LDFACAL Table of output load factors for SOL 401 arc-length solution




CUMMAL Table of cumulative arc-length for SOL 401 arc-length solution

IFP1

Updated Format:

IFP1 /CASECC,PCDB,XYCDB,POSTCDB,FORCE,SETMC,JCASE/S,N,NOGOIFP1/S,N,LASTCC/S,N,BEGSUP/DMAPNO/S,N,K402 $

New Parameter:

K402 Integer-output-default=-1. Reserved for SOL 402

INITSNCR

Updated Format:

INITSNCR CASECC,GEOM3,ESTNLH,BGPDTS,GPECT,SILS,CSTMS,MPTS,DITS/INITNODE,INITGAUS,INITGAUC,INOFFND,INOFFGA,INOFFGC/S,N,ERRINICR/-1$


INOFFND Initial strain offsets at corner grids in the basic coordinate system. This output isgenerated if CASECC has the INITS(OFFSET) case control set

INOFFGA Initial strain offsets at all Gauss points in the basic coordinate system. This outputis generated if CASECC has the INITS(OFFSET) case control set

INOFFGC Initial strain offsets at corner Gauss points in the basic coordinate system. Thisoutput is generated if CASECC has the INITS(OFFSET) case control set

LAMX

New Format to Modify LAMA for SOL 401 cyclic modes and axi-Fourier modes:

LAMX EMAT,LAMA/LAMAX/NLAM/RESFLG/FRCYCANL/FRCYSCID/FRCYFLG/FRCYHARM $

New Parameters:

FRCYCANL Input-integer-default=0. If FRCYANL=1, it indicates that the current solution is aSOL 401 cyclic normal modes or SOL 401 axi-Fourier modes solution

FRCYSCID Input-integer-default=0. Subcase ID for current analysis




FRCYFLG Input-integer-default=0. If FRCYFLG=2, it indicates a SOL 401 axi-Fouriersolution. FRCYFLG=3 indicates a SOL 401 cyclic modes solution

FRCYHARM Input-integer-default=0. Indicates the harmonic index for a SOL 401 axi-Fouriersolution or SOL 401 cyclic modes solution

MATMOD

Updated Format for All Options:

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

Updated Option P1=36

Reduce the GRID record in the GEOM1 table to the entries corresponding to grid identificationnumbers specified in a Case Control set.

Updated Format:

MATMOD GEOM1,CASECC,GEOM2,,,,,,,,,,,,,,/GEOM1R,/36/GRIDSET/S,N,NOGEOM1/ELEMSET $


GEOM2 Table of Bulk Data entry images related to geometry (optional; only required ifELEMSET = -1 or ELEMSET > 0)

Updated Parameters:

GRIDSET Input-integer-default=0. SET Case Control command identification number (> 0)which contains a list of grid point identification numbers.

-1 Implies ALL

0 Implies NONE

NOGEOM1 Output-integer. Processing status flag.

>0 No grid data found matching gridset.

0 GRIDSET found and contents match some GRIDs in GEOM1.

-1 GRIDSET found and contents matches all GRIDs in GEOM1.




New Parameter:

ELEMSET Input-integer-default=0. SET Case Control command identification number (> 0)which contains a list of element identification numbers from which their grid pointidentification numbers are derived.

-1 Implies ALL

0 Implies NONE

New Remarks:

1. Only the GRID record is processed and all other GEOM1 records are copied as is to GEOM1R.

2. GEOM1 and GEOM2 must be indexed with the IFPINDX module before being used as input tothis MATMOD option:

FILE GEOM1=APPEND/GEOM2=APPEND $IFPINDX /GEOM1 $IFPINDX /GEOM2 $MATMOD GEOM1,CASECC,GEOM2,,,,,,,,,,,,,,/GEOM1R,/36/GRIDSET/

S,N,NOGEOM1/ELEMSET $

3. It is recommended that GEOM1 and GEOM2 be converted by the SECONVRT module and thenused as input to MATMOD.

4. If GRIDSET = 0 and ELEMSET = 0, GEOM1R is not created. If either GRIDSET = -1 orELEMSET = -1, GEOM1R is not created.


Reduce the element and SPOINT records in the GEOM2 table to the entries corresponding toelement or SPOINT identification numbers specified in a Case Control set.

Updated Parameters:

ELEMSET Input-integer-default=0. SET Case Control command identification number (> 0)which contains a list of element identification numbers.

-1 Implies ALL

0 Implies NONE

GRIDSET Input-integer-default=0. SET Case Control command identification number (> 0)which contains a list SPOINT identification numbers.

-1 Implies ALL

0 Implies NONE

NOGEOM2 Output-integer. Processing status flag.

>0 No element and SPOINTs found matching ELEMSET and GRIDSET.




0 ELEMSET and GRIDSET found and contents match some elements andSPOINTs in GEOM2.

-1 ELEMSET and GRIDSET found and contents match all elements andSPOINTs in GEOM2.

New Remarks:

1. GEOM2 must be indexed with the IFPINDX module before being used as input to this MATMODoption:

FILE GEOM2=APPEND $IFPINDX /GEOM2 $MATMOD GEOM2,CASECC,,,,,,,,,,,,,,,/GEOM2R,/37/ELEMSET/

GRIDSET/S,N,NOGEOM1 $

2. It is recommended that GEOM2 be converted by the SECONVRT module and then used asinput to MATMOD.

3. If ELEMSET = 0 and GRIDSET = 0, GEOM2R is not created. If either ELEMSET = -1 orGRIDSET = -1, GEOM2R is not created.


Replace or add a value to a single term in a matrix, or overwrite a value in a table.

Format:

MATMOD I1,,,,,,,,,,,,,,,,/O1,/56/ICOL/IROW/TYPE/REAL//NCOL/NROW/INT/TFLAG//CHAR/////REALD/CMPLX/CMPLXD $

New Parameter:

CHAR Character value. (Table only)




Updated Parameter:

TYPE Type of value to be replaced or added.

0 Replace current value with INT. (Table only)

1 Replace current value with REAL. (Table and matrix)

2 Replace current value with REALD. (Matrix only)

3 Replace current value with CMPLX. (Matrix only)

4 Replace current value with CMPLXD. (Matrix only)

5 Replace current value with CHAR. (Table only)

-1 Add REAL to current value. (Matrix only)

-2 Add REALD to current value. (Matrix only)

-3 Add CMPLX to current value. (Matrix only)

-4 Add CMPLXD to current value. (Matrix only)

New Option P1=63

On an term-by-term basis, linearly interpolates [A(xn)] and [A(xn+1)] to find [A(x)], where xn ≤ x ≤ xn+1or xn ≥ x ≥ xn+1, and aij = (aij)real + i(aij)imaginary.

Format:

MATMOD I1,I2,,,,,,,,,,,,,,,/O1,/63////VAL1/VAL2//////////////VAL3 $

Input Data Blocks:

I1 Complex matrix [A(xn)] at xn

I2 Complex matrix [A(xn+1)] at xn+1

Output Data Block:

O1 Complex matrix [A(x)] of interpolated values at x

Parameters:

VAL1 Input-real-no default. Value for xn

VAL2 Input-real-no default. Value for xn+1




VAL3 Input-real-no default. Value for x

Remarks:

1. VAL1 ≠ VAL2

2. VAL1 ≤ VAL3 ≤ VAL2 or VAL1 ≥ VAL3 ≥ VAL2

3. Option P1 = 63 interpolates complex data on a term-by-term basis as follows:

a. The module converts the real/imaginary data to the magnitude/phase format.

b. The module linearly interpolates the magnitudes at xn and xn+1 to obtain the magnitudeat x from the following equation:

Note

xn is VAL1, xn+1 is VAL2, and x is VAL3.

c. The module linearly interpolates the phase angles at xn and xn+1 to obtain the phase angleat x as follows:

A. If necessary, the module converts the phase angles at xn and xn+1 so that they rangebetween 0 and 2π.

For example, θ = -π / 2 is converted to θ = +3π / 2.

B. The module calculates the angle subtended between the phase angles at xn and xn+1as follows:

C. If Δθ ≤ π, the module calculates the value for the phase angle at x from the followingequation:

D. If Δθ > π, the module calculates the value for the phase angle at x from the followingequation:




d. The software converts the magnitude/phase data at x to real/imaginary format.

Example:

Suppose [I1] is a matrix of complex responses at frequency VAL1 and [I2] is a matrix of complexresponses at frequency VAL2. You can use Option P1 = 63 to interpolate the complex responses atfrequencies VAL1 and VAL2 to estimate the complex response at frequency VAL3.

New Option P1=64

Reorder a column vector.

Format:

MATMOD I1,,,,,,,,,,,,,,,,/O1,/64/INC $

Input Data Block:

I1 Column vector to be reordered

Output Data Block:

O1 Reordered column vector

Parameter:

INC Input-integer-no default. Reordering increment

Example:

Suppose {I1} is a column vector of responses for two DOF at three different frequencies and hasthe following values:

In {I1}, the first pair of entries are the responses at frequency 1, the second pair of entries are theresponses at frequency 2, and the third pair of entries are the responses at frequency 3.




To reorder the contents of {I1} so that the first three entries are the responses at the first DOF at eachfrequency, and the second three entries are the responses at the other DOF at each frequency, useOption P1 = 64 with INC = 2. The reordered column vector {O1} is as follows:

New Option P1=65

Create a permutation matrix [P] for the input matrix [A] (or input matrices [A] and [B]) such that:

where the matrix [F] is the matrix that would result from reordering the input matrix [A] (or inputmatrices [A] and [B]) in the sparse solver, based on the method selected by system cell 206.

Thus, it is possible to use [P] to generate the reordered version (or versions) of the input matrix [A](or matrices [A] and [B]) for use in a DMAP program, where the reordered version (or versions) areequivalent to the matrix (or matrices) that would be the input to the sparse solver.

The matrix [A] is typically the stiffness matrix, and if provided, the matrix [B] is typically the massmatrix.

Format:

MATMOD A,B,,,,,,,,,,,,,,,/P,/65 $

Input Data Blocks:

A Required input matrix

B Optional input matrix

Output Data Block:

P Permutation matrix

Examples:

MATMOD KAA,MAA,,,,,,,,,,,,,,,/PAA,/65 $




MODACC

Updated Parameter Options:

IOPT Input-integer-default=0. Processing options:

0=process OFREQ or OTIME or OMODES.

1=process SETMC for MODCON.

2=process SETMC for PANCON.

3=process SETMC for ERP.

4=process MDLIST. Only valid if APP=‘REIGEN’.

5=process OMODES as a request for pairs of modes rather than individualmodes. Only valid for Fourier modes with a harmonic index > 0 and cyclicmodes with 0 < harmonic index < N/2, where N is the number or repetitionsin the cyclic geometry.

6=process SETMC for GRDCON.

MODUSETF

Updated Format:

MODUSETF BGPDT,USET,SILS,GEOM4,DYNAMICS/USETF,RMG,RMG2,SILSF,DYNAAXIF/P1/P2$


DYNAMICS Table of bulk entry images related to dynamics


DYNAAXIF Table related to DYNAMICS in axi-Fourier solution

MPPARV

Updated Format:

MPPARV CASECC,CONTACT,ECTS,EDT,GEOM2S,EQEXINS/ACPARV/NFLUID $




Note

The REQID parameter that followed the NFLUID parameter is removed.

MPPOST

Updated Format:

MPPOST CASEDR,UG,UFF,OL1,CONTACT,ECTS,EDT,GEOM2S,EQEXINS,ATVMIC/UGNEW,OACVELO1,OACINT1,OACPWR1,OACPWRI1,OACPWRT1 $

Note

The REQID parameter is removed.


UG Displacement matrix for all DOF, g-set

ATVMIC List of microphone element IDs that belong to an ATV

Updated Input Data Block Description:

UFF Pressure matrix for fluid DOF, g-set; must be scattered pressure


UGNEW New displacement/pressure matrix for all DOF, g-set, that includes microphonepoint pressures

OACPWRI1 Output data block of incident acoustic power for FACES or GROUPs of 2Delements. SORT1 format

OACPWRT1 Output data block of transmitted acoustic power for AML regions and GROUPsof 2D elements. SORT1 format

Note

The UGNEW output data block replaces the OACPRES1 output data block.

MPPRESS

The MPPRESS module is now obsolete and is removed from the documentation.




NLTRD3

Updated Format:

NLTRD3 CASESX2H,PDT,YS,ELDATAH,KELMNL,KDDL,GMNL,MPTS,DITS,KBDD,DLT1,CSTMS,BGPDT,SILS,USETD,UNUSED,MJJ,NLFT,UNUSED,UNUSED,UNUSED,GPSNTS,DITID,DEQIND,DEQATN,ELGNST,GLUESEQ,COMPEST,KDICTUP,EPT,ECTS,EDT,RGNL,EQEXINS,SLT,KELMUP,GEOM3,GEOM5,ETT,FBSIN,CNELM,ECSTAT,ELSLIP,TLAMDA,UNUSED,EST,GPECT,INITGAUS,UGCP,YS1I,ECDISPG,DLT,KDICTNL,CONFAC2,GEOM1,GEOM2,PVT0,SETMC,OFFSETP,RFRCEI,UNUSED,DLT2,PGT,INOFFGA,CMPGEST,PGBOLT1,SBDATA/ULNTH,IFSH,ESTNLH,IFDH,OES1,PNLH,TELH,MULNT,MESTNL,MESTNL2,UNUSED,PBDATA,OSTR1,OSTR1EL,OSTR1TH,OSTR1PL,OSTR1CR,OES1G,OSTR1G,OSTR1ELG,OSTR1THG,OSTR1PLG,OSTR1CRG,OTEMP1,OES1C,OSTR1C,OSTR1ELC,OSTR1THC,OQGGF1,OBG1,PLPG,FENLR,PLFG,UGLAST,FBSOUT,TLAMUP,ADGPECT,ADEST,ADSTRES,OERRES,OERREP,OERRSS,OERRSP,CNELMUP,OJINT,UNUSED,ELAMUP,YS2F,UDLAST,ESTNLINI,CSDATA,PBDATA,OJINE,CNTPENTR,UMATINL,STATVAR2,OUMAT,OUMATG,ODAMGPFD,ODAMGPFE,ODAMGPFS,ODAMGCZT,ODAMGCZR,ODAMGCZD,OCKGAP1,OCKGAP1G,OBOLT1,UGGPO,OSLIDEG1,DLAMDA,OSTR1PLC,RFRCEF,ECSTATUP,TSLIP,PLPG2,GESTNL,GESTNL2,ESTNLG,ODAMGPFR,OEF1,TRMBD,UNUSED,ELSLIPUP,LDFACAL,ALCUMM,OBCKL,OEFIT,OESRT,OQGCF1,OBC1X,OSPDS1X,OSLIDE1,OCONST1,PSLIP,PLAMDA/KRATIO/S,N,CONV/S,N,RSTIME/S,N,NEWP/S,N,NEWDT/S,N,OLDDT/S,N,NSTEP/LGDISP/S,N,ANAL/S,N,ITERID/ITIME/S,N,KTIME/S,N,LASTUPD/S,N,NOGONL/S,N,NBIS/MAXLP/TSTATIC/LANGLE/NDAMP/TABS/S,N,LDFACAL/MATNL/S,N,ARCLNTH/ITERMP/0/GLUE/GPFORCE/BCSET/S,N,CITO/S,N,CITI/S,N,AUGLOOP/S,N,CNVO/S,N,CNTPUPDT/S,N,CONFLAG/S,N,CNTNINC/S,N,BISFLAG/S,N,DTLAST/S,N,CPLFLG/S,N,PBCONV/S,N,CNTUPDT/NCELS/S,N,CRPFLAG/ETYPE/S,N,MESTFLG/RSTMPREV/ENDTIME/S,N,CNTNDIV/K6ROT/S,N,OFSTFLG/MASSNEWM $

Changed Input Data Blocks:

• The 34th input data block changes from UNUSED to EQEXINS.

• The 45th input data block changes from PLAMDA to UNUSED.

• The 61st input data block changes from PSLIP to UNUSED.


EQEXINS Table between external and internal DOF

INOFFGA Initial strain offsets for balanced initial stress/strain at all Gauss points. The formatis the same as INITGAUS, but the elements are those on which balanced initialstress/strain is specified


PGBOLT1 Table of bolt forces at bolt grids not being preloaded in the current subcase




SBDATA Data related to solid bolts


GESTNL Nonlinear element summary table at current step

GESTNL2 Nonlinear element summary table at current step

ESTNLG Nonlinear element summary table at current step

ODAMGPFR Table of crack density for ply failure EUD model from SOL 401. Crack density atcorner grids on the middle of plies. The values are unitless

OEF1 Table of element forces in SORT1 format

TRMBD Table of Euler angles for transformation from material to basic coordinate systemin the deformed configuration

ELSLIPUP Matrix that contains updated contact element elastic slip


ALCUMM Table of cumulative arc-length for SOL 401 arc-length solution

OBCKL Table of load factor vs. cumulative arc-length in SORT2 format

OEFIT Table of composite element failure indices

OESRT Table of composite element strength ratios

OQGCF1 Contact force at grid point

OBC1X Contact pressures and tractions at grid points

OSPDS1X Final separation distance

OSLIDE1 Incremental and total slide/slip distance in SORT1 format

OCONST1 Contact status in SORT1 format

PSLIP Contact element slip from prior time step

PLAMDA Contact tractions from prior step

Changed Parameters:

• The 21st parameter changes from UNUSED to LDFACAL.

• The 23rd parameter changes from UNUSED to ARCLNTH.

• The 43rd parameter changes from COUNT to ETYPE.




New Parameters:

LDFACAL Output-real-no default. Load factor for SOL 401 arc-length solution

ARCLNTH Output-real-no default. Cumulative arc-length SOL 401 arc-length solution

ETYPE Input-integer-default=0. Bolt type information from EDT

K6ROT Input-real-default=100.0. Specifies the stiffness to be added to the normalrotation for CQUAD4 and CTRIA3 elements

OFSTFLG Output-integer-no default. Flag to indicate whether any element(CBEAM/CBAR/CQUADR/CTRIAR/CQUAD8/CTRIA6) with non-zero offset ispresent in the model

MASSNEWM Output-integer-no default. MASS Matrix update flag MASSNEWM for CBEAMand CBAR

OUTPRT

Note

Because of the extent to which the OUTPRT module has changed, the documentation forthe entire module is included below.

Constructs sparse load reduction and sparse data recovery partitioning vectors.

Format for MCFLAG = 0, 1, 2, 3, 5:

OUTPRT CASECC,ECT,BGPDT,SIL,XYCDB,DYNAMIC,MATPOOL,PG,VGFD,TABEVP,TABEVS,SETMC,TEXTSE,EDT,GEOM2/PVGRID,PVSPC,PVMPC,PVLOAD,PVCODES,,,TEXTOU/S,N,SDRMETH/NOSE/SDROVR/SDRDENS/MCSET/MCFLAG/IRTYPE/MATTYP/APP $

Format for MCFLAG = 4:

OUTPRT CASECC,ECT,BGPDT,SIL,XYCDB,DYNAMIC,MATPOOL,PG,VGFD,TABEVP,TABEVS,SETMC,TEXTSE,EDT,GEOM2/PVGRID,PVGRID1,PVGRID2,,PVCODES,PVCODE1,PVCODE2,TEXTOU/S,N,SDRMETH/NOSE/SDROVR/SDRDENS/MCSET/MCFLAG/IRTYPE/MATTYP/APP $

Input Data Blocks:

CASECC Table of Case Control command images

ECT Element connectivity table


SIL Scalar index list




XYCDB Table of x-y plotting commands

DYNAMIC Table of Bulk Data entry images related to dynamics

MATPOOL Table of Bulk Data entry images related to hydroelastic boundary, heat transferradiation, virtual mass, DMIG, and DMIAX entries

PG Static load matrix applied to the g-set

VGFD Partitioning vector with ones at rows corresponding to DOF connected tofrequency-dependent elements

TABEVP Cross-reference table between ESTDVP records and element and designvariable identification numbers

TABEVS Cross reference table between ESTDVS records and element and designvariable identification numbers

SETMC Modal contribution set definitions

TEXTSE Directory table for external superelement

EDT Element deformation table

GEOM2 Table of bulk entry images related to element connectivity and scalar points

Output Data Blocks for MCFLAG = 0, 1, 2, 3, 5:

PVGRID Partitioning vector with ones at rows corresponding to DOF connectedto elements or grids specified on the following Case Control commands:ACCELERATION, DISPLACEMENT, EDE, EKE, ESE, FORCE, GPFORCE,GPKE, MODCON, MPCFORCE, MPRES, PANCON, SPCFORCE, STRAIN,STRESS, VELOCITY

PVSPC Partitioning vector with ones at rows corresponding to DOF connected toelements or grids specified on the SPCFORCE Case Control command

PVMPC Partitioning vector with ones at rows corresponding to DOF connected toelements or grids specified on the MPCFORCE Case Control command

PVLOAD Partitioning vector with ones at rows corresponding to DOF at which static anddynamic loads are applied

PVCODES For MCFLAG=0, 1, or 5, modal/panel contributions output request codescorresponding to selections contained in PVGRID

For MCFLAG=2, a 3-column matrix where column 1 is a list of output requestcodes, column 2 is a list of element IDs, and column 3 is a list of element itemcodes

For MCFLAG=3, PVCODES is not generated




TEXTOU Modified directory table for external superelement. Created if TEXTSE exists,MCFLAG=2, and IRTYPE=9, 10, or 11, or in the context of extended acoustics,if TEXTSE does not exist and there are microphone points in the model. For theextended acoustics case, TEXTOU is a real single-precision 2 column matrixof microphone point internal IDs and SIL numbers.

Output Data Blocks for MCFLAG = 4:

PVGRID Partitioning vector with ones at rows corresponding to DOF connected tostructural grids specified on SETMC Case Control commands

PVGRID1 Partitioning vector with ones at rows corresponding to DOF connected tovelocities at structural grids specified on SETMC Case Control commands

PVGRID2 Partitioning vector with ones at rows corresponding to DOF connected toaccelerations at structural grids specified on SETMC Case Control commands

PVCODES Modal/panel contributions output request codes corresponding to selectionscontained in PVGRID

PVCODE1 Panel contribution output request code corresponding to selections in PVGRID1

PVCODE2 Panel contribution output request code corresponding to selections in PVGRID2

TEXTOU Same as for MCFLAG = 0, 1, 2, 3, 5

Parameters:

SDRMETH Output-integer-no default. Data recovery method flag:

-1 Sparse data recovery

0 Full (or standard) data recovery

1 No data recovery is requested or required

NOSE Input-integer-default=0.

Set to -1 if there are no superelements; 0 otherwise. Superelement presenceflag.

SDROVR Input-character-default=‘AUTO’. Override for data recovery method flag, SDR:

AUTO Choose full or sparse data recovery based on SDRDENS

FULL Choose full data recovery

SPARSE Choose sparse data recovery

SDRDENS Input-integer-default=0. Sparse data recovery ceiling density. If the density ofPVGRID is greater than SDRDENS divided by 100, choose full data recovery




MCSET Input-integer-default=0. Modal contribution set to use:

-1 Use all sets in SETMC

0 Ignore SETMC

>0 Use set=MCSET in SETMC

MCFLAG Input-integer-default=0. Modal contribution set usage flag:

0 Grids and elements

1 Grids only

2 Elements only

3 Acoustic/fluid points only

4 Grids only for SETMC specified DOF

5 Grids only; PVGRID does not contain all 6 DOF for a grid, but onlyselected DOF.

IRTYPE Input-integer-default=0. Response type:

9 Element stress

10 Element strain

11 Element force

MATTYP Input-integer-default=0. External superelement matrix type

APP Input-character-default=‘ ’. Analysis type

Remarks:

1. PVCODES is only created for MCFLAG=0, 1, 2, 4, or 5.

2. If TEXTSE is present, external superelement processing is assumed. Therefore, all other inputdata blocks will be ignored except SETMC, and MCFLAG must be either 1 or 2.

3. If TEXTSE is present, MCFLAG=2, and IRTYPE=9, 10, or 11, TEXTOU is created. The values ofIRTYPE and MATTYP must be consistent with the type of data contained in the TEXTSE datablock. In the context of extended acoustics, if TEXTSE is not present and there are microphonepoints in the model, TEXTOU is created as a real single-precision 2 column matrix of microphonepoint internal IDs and SIL numbers.




RANDOM

Updated Format:

RANDOM XYCDB,DIT,PSDL,OUG2,OPG2,OQG2,OES2,OEF2,CASECC,OSTR2,OQMG2,RCROSSL,OFMPF2M,OSMPF2M,OLMPF2M,OPMPF2M,OGPMPF2M,OUGF2,OACPWR2,OACPWRI2,OACPWRT2/PSDF,AUTO,OUGPSD2,OUGATO2,OUGRMS2,OUGNO2,OUGCRM2,OPGPSD2,OPGATO2,OPGRMS2,OPGNO2,OPGCRM2,OQGPSD2,OQGATO2,OQGRMS2,OQGNO2,OGGCRM2,OESPSD2,OESATO2,OESRMS2,OESNO2,OESCRM2,OEFPSD2,OEFATO2,OEFRMS2,OEFNO2,OEFCRM2,OEEPSD2,OEEATO2,OEERMS2,OEENO2,OEECRM2,OQMPSD2,OQMATO2,OQMRMS2,OQMNO2,OGMCRM2,OUGFPSD2,OUGFATO2,OUGFRMS2,OOGFNO2,OUGFCRM2,OAPPSD2,OIPPSD2,OTPPSD2,OCPSDF,OCCORF,SABFIL/S,N,NORAND/RMSINT/CPLX/SSFLAG/RMSSF/CMPFLAG/RANDSC $

Updated Input Data Block Description:

OUG2 Table of displacements in SORT2 format. Table of displacements and pressuresin SORT2 format if SYSTEM(640)=0


OUGF2 Table of pressures in SORT2 format (only if SYSTEM(640)≠0)

OACPWR2 Table of acoustic power in SORT2 format

OACPWRI2 Table of acoustic incident power in SORT2 format

OACPWRT2 Table of acoustic transmitted power in SORT2 format

Updated Output Data Block Descriptions:

OUGPSD2 Table of displacements in SORT2 format for the PSD function. Table ofdisplacements and pressures in SORT2 format for the PSD function ifSYSTEM(640)=0

OUGATO2 Table of displacements in SORT2 format for the autocorrelation function. Table ofdisplacements and pressures in SORT2 format for the autocorrelation function ifSYSTEM(640)=0

OUGRMS2 Table of displacements in SORT2 format for the RMS function. Table ofdisplacements and pressures in SORT2 format for the RMS function ifSYSTEM(640)=0

OUGNO2 Table of displacements in SORT2 format for the NO function. Table ofdisplacements and pressures in SORT2 format for the NO function ifSYSTEM(640)=0




OUGCRM2 Table of displacements in SORT2 format for the cross correlation function. Tableof displacements and pressures in SORT2 format for the cross correlation functionif SYSTEM(640)=0


OUGFPSD2 Table of pressures in SORT2 format for the PSD function (only if SYSTEM(640)≠0)

OUGFATO2 Table of pressures in SORT2 format for the autocorrelation function (only ifSYSTEM(640)≠0)

OUGFRMS2 Table of pressures in SORT2 format for the RMS function (only if SYSTEM(640)≠0)

OOGFNO2 Table of pressures in SORT2 format for the NO function (only if SYSTEM(640)≠0)

OUGFCRM2 Table of pressures in SORT2 format for the cross correlation function (only ifSYSTEM(640)≠0)

OAPPSD2 Table of acoustic power in SORT2 format for the PSD function

OIPPSD2 Table of acoustic incident power in SORT2 format for the PSD function

OTPPSD2 Table of acoustic transmitted power in SORT2 format for the PSD function

New Parameter:

RANDSC Input-integer-default = 0. Random subcase ID.

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,CBRROT,LDFACAL,CUMMAL,CMPGEST/OPG1,OQG1,OUG1,OES1,OEF1,PUG,OGPKE1,OEFIIP,OEFIIS,OESRIP,OESRIS,OEFIT,OESRT/APP/S,N,NOSORT2/NOCOMP/ACOUSTIC/METRIK/ISOFLG/GPF/ACOUT/PREFDB/TABS/SIGMA/ADPTINDX/ADPTEXIT/BSKIP/FREQW/BTBRS/LANGLE/OMID/SRCOMPS/APP1/GSPF/RPM/SWPANGLE/STFOPTN/RUNIT/HINDEX/HOOPDOF/SCFLAG/CYCAXID/NACEXTRA $



CUMMAL Table of cumulative arc-length for SOL 401 arc-length solution






OEFIT Table of composite element failure indices

OESRT Table of composite element strength ratios

Updated Parameter Descriptions:

NOCOMP Input-integer-default=-1. Composite stress/strain flag.

-5 Forces of composites in STRAIN=sid

-2 Forces of composites in STRESS=sid

-1 Stresses for all elements (same as 0 except in DMAP)

0 Stresses for all elements

1 Stresses for non-composites only

2 Strain/curvature and forces of composites in STRESS=sid

3 Strains for all elements and MPC forces

4 Strains for non-composites only

5 Strain/curvature of composites in STRAIN=sid

8 FRF forces

ACOUSTIC Input-integer-default=0. Fluid-structure analysis flag. If set to 2, acoustic pressureis computed for fluid elements.

0 No fluid elements exist

1 Penalty or fluid acoustic elements exists

2 Fluid/structure coupling exists

3 The acoustic output is based on PRESSURE case controlcommand

SELA

Updated Format:

SELA PJ,SLIST,SEMAP,BGPDTS,PA*,MAPS*,GDNTAB/PG/SEID/QUALNAM/S,N,LDSEQ/S,N,NOPG/PRTUIM/SEFLAG $




New Parameter:

SEFLAG Input-integer-default=0. Superelement processing flag= 0 to assemble standard superelement loads= 1 to assemble frequency-dependent superelement loads

SEMA

Updated Format:

SEMA BGPDTS,SLIST,SEMAP,XJJ,XAA*,MAPS*,GDNTAB/XGG/SEID/LUSETS/QUALNAM/UPFM/SEFLAG $

New Parameter:

SEFLAG Input-integer-default=0. Superelement processing flag= 0 to assemble standard superelement matrices= 1 to assemble frequency-dependent superelement matrices

SSG1

Updated Format:

SSG1 SLT,BGPDT,CSTM,MEDGE,EST,MPT,ETT,EDT,MGG,CASECC,DIT,UG,DEQATN,DEQIND,GPSNT,CSTMO,SCSTM,GEOM4,EPT,PCOMPT,COMPEST,FORCDSTT/{PG or AG},PTELEM,SLTH/LUSET/NSKIP/DSENS/APP/ALTSHAPE/TABS/SEID/LMFACT $


FORCDSTT Table of patch center of area, patch triad, and load vector for each distributed loadin GEOM3. FORCDSTT must be created with the TOTLOAD module

TA1

Updated Format:

TA1

MPT,ECT,EPT,BGPDT,SIL,ETT,CSTM,DIT,ECTA,EHT/EST,ESTNL,GEI,GPECT,ESTL,VGFD,DITID,NFDICT,COMPEST,NSMEST,CMPGEST/LUSET/S,N,NOESTL/S,N,NOSIMP/NOSUP/S,N,NOGENL/SEID/LGDISP/NLAYERS/S,N,FREQDEP/BSHDAMP/S,N,BSHDMP/NSMID/MATNL $






TRLG

Updated Format:

TRLG CASECC,USETD,DLT,SLT,BGPDT,SIL,CSTM,TRL,DIT,GMD,GOD,{PHDH or RPX},EST,MPT,MGG,V01P,FORCDSTT/{PPT or PGT},PST,PDT,PDT1,{PHT or PXT},TOL,DLTH,YPT,YPO/S,N,NOSET/S,N,PDEPDO/IMETHOD/STIME/BETA/S,N,FAC1/S,N,FAC2/S,N,FAC3/TOUT/TABS/OPT $


FORCDSTT Table of patch center of area, patch triad, and load vector for each distributed loadin GEOM3. FORCDSTT must be created with the TOTLOAD module

UPGLSTF

Updated Format:

UPGLSTF GNELM,BGPDT,CSTM,UGVBAS,ELMMOD/ELGNST/IOPT/NROW/K6ROT/BLT $


ELMMOD Element modulus table

New Parameter:

BLT Input-integer-default=0. Bolt preload solve number for linear solution sequences(1-first solve/2-second solve)

XSELOADS

Updated Format:

XSELOADS CASECC,SELOAD,GEOM3,DYNAMIC,PA/XSELOADS/NCOL $

New Parameter:

NCOL Input-integer-default=0. If NCOL > 0, number of columns to auto-generateXSELOADS data block (no input data blocks required). If NCOL ≤ 0, uses inputdata blocks to generate XSELOADS data block.




XYTRAN

Updated Format for SDR2 Outputs:

XYTRAN XYCDB,OPG2,OQG2,OUG2,OES2,OEF2,OSTR2,OQMG2,OUGF2/XYPLOT/APP/XYSET/S,N,PLTNUM/S,N,CARDNO/S,N,NOXYPLOT/S,N,TABID $

Updated Format for RPSEC Outputs:

XYTRAN XYCDB,OXRESP,,,,,,,/XYPLOT/'RSPEC'/XYSET/S,N,PLTNUM/S,N,CARDNO/S,N,NOXYPLOT/S,N,TABID $

Updated Format for MODEPOUT Outputs:

XYTRAN

Updated Format for VDR Outputs:

XYTRAN XYCDB,OUXY2,OPNL2,,,,,,/XYPLOT/APP/XYSET/S,N,PLTNUM/S,N,CARDNO/S,N,NOXYPLOT/S,N,TABID $

Updated Format for RANDOM Outputs:

XYTRAN XYCDB,PSDF,AUTO,,,,,,/XYPLOT/APP/XYSET/S,N,PLTNUM/S,N,CARDNO/S,N,NOXYPLOT/S,N,TABID $





OUGF2 Table of pressures in SORT2 format

New modules

ACPRESS

Computes frequency response acoustic enforced pressure matrix in the p-set. Computes theacoustic enforced pressure matrix.

Format:

ACPRESS CASECC,USETD,FRL,DYNAMIC,GEOM4,DIT,BGPDT,/YPFAC,/ $

Input Data Blocks:

CASECC Table of case control images

USETD Grid point definition table

FRL Frequency response list

DYNAMIC Table of bulk entry images related to dynamics

GEOM4 Table of bulk entry images related to constraints, degree-of-freedom membership,and rigid element connectivity

DIT Table of TABLEij bulk entry images

BGPDT Grid point definition table

Output Data Blocks:

YPFAC Frequency response enforced pressure matrix in the p-set

ATVGP

Generate geometry, element and property tables for microphone elements and 2-D surface fluidelements in the ATV computation.

Format:

ATVGP CASECC,BGPDT,CONTACT,GEOM1,GEOM2,EPT/GEOM1ATV,GEOM2ATV,EPTATV,MICLOC,ATVMAP,VGATV/S,N,SOLATV/S,N,OP2UNIT/LUSET $




Input Data Blocks:



CONTACT Table of bulk entry images related to contact



EPT Table of bulk entry images related to element properties

Output Data Blocks:

GEOM1ATV Table of bulk entry images related to geometry of microphone and 2D surfacefluid elements

GEOM2ATV Table of bulk entry images related to microphone and 2D surface fluid elementconnectivity

EPTATV Table of bulk entry images related to microphone element properties

MICLOC Table of microphone grid locations

ATVMAP Table of mapping index for ATV grids

VGATV Partition vector for the degrees-of-freedom specified by ATVFS

Parameters:

SOLATV Output-integer-default=0. Controls ATV computation.

0 Do not perform ATV computation

1 Perform ATV computation

OP2UNIT Output-integer-no default. ATV OP2 IO number.

LUSET Input-integer-no default. Number of degrees-of-freedom in the g-set.

ATVPARTV

Generate the partition vectors of ATV microphone and interface.

Format:

ATVPARTV BGPDT,ATVMAP/VGMIC,VGIP,VIPLS/GOFFSET/LUSET $




Input Data Blocks:


ATVMAP Table of mapping index of ATV grids

Output Data Blocks:

VGMIC Partition vector for DOFs of ATV microphone grids

VGIP Partition vector for DOFs of ATV interface fluid grids

VIPLS ATV interface fluid grids list

Parameters:

GOFFSET Input-integer-default=0. Grid offset of ATV component

LUSET Input-integer-no default. Number of DOFs in the g-set

ATVPOST

Post-process the results of ATV microphone point; Compute the acoustic power of 2D microphoneelement of ATV using the plane wave approach.

Format:

ATVPOST CASECC,UG,FOL,ECTS,EDT,BGPDTS,ATVMIC,PTMIC,FOLATV,GEOM1/OACPWR $

Input Data Blocks:


UG Displacement matrix in g-set

FOL Frequency response frequency output list

ECTS Element connectivity table for current superelement

EDT Element definition table

BGPDTS Grid point definition table for current superelement

ATVMIC List of microphone element IDs that belong to an ATV

PTMIC Microphone property table for ATV computation

FOLATV Frequency response frequency output list of ATV





Output Data Block:

OACPWR Output data block of acoustic power for ATV 2D microphone elements

Parameters:

None

DAYTIM

Returns the local clock time, using the same 24-hour format that appears in the .f04 file.

Format:

DAYTIM //S,N,P1 $

Input Data Blocks:

None

Output Data Blocks:

None

Parameter:

P1 Output-character-no default. 8 character value

Example:

TYPE PARM,,CHAR8,N,WALTIM $DAYTIM //S,N,WALTIMMESSAGE //'BEFORE DMIIN THE WALL TIME= '/ WALTIM $

The output from the above DMAP program will look as follows:

^^^BEFORE DMIIN THE WALL TIME= 17:38:54

DOM13

Adjusts the mass densities during a SOL 200 Topology Optimization solution to conform to themanufacturing constraints supplied with the DMNCON bulk entry.

Format:

DOM13 BGPDT,GEOM2,GPECT,VELEM,XINIT,CONTEL,EDOM,EDT,HIS,/XUPDMF,ONMD,,,/NASPRT,ISBEST,DESCYCLE,BDMNCON $




Input Data Blocks:


GEOM2 Table of bulk entries related to element connectivity

GPECT Grid point element connection table

VELEM Table of element lengths, areas, and volumes

XINIT Matrix of initial values of the design variables

CONTEL Element ID versus design variable ID information

EDOM Table of bulk entries related to design sensitivity and optimization

EDT Data block that contains the needed GROUP bulk entries in a record

HIS Table of design cycles history

Output Data Blocks:

XUPDMF Array of design variables updated based on manufacturing constraints

ONMD Normalized mass densities data block for output into the OP2 file

Parameters:

NASPRT Input-integer-default=0. SOL 200 output frequency control parameter

ISBEST Input-integer-no default. Indicates best design so far when 1. Otherwise, 0

DESCYCLE Input-integer-no default. Current design cycle number

BDMNCON Input-integer-default=10. User defined start cycle for application ofmanufacturing constraints (except for planar symmetry)

DPDAC

Inputs the bulk entry images for acoustic analysis. Requires that the GPAC module is called first.

Format:

DPDAC CASECC,DYNAMIC,GEOM4,MICLOC,DIT// $

Input Data Blocks:

CASECC Table of case control command images





GEOM4 Table of bulk entry images related to constraints, degree-of-freedommembership, and rigid element connectivity

MICLOC Microphone location table for ATV computation


Remarks:

1. If MICLOC is not purged, the CASECC, DYNAMICS, GEOM4, and DIT tables are not usedin the module.

DSADJC

Adjoint solution vectors for compliance responses are created and appended to any existing adjointsolution vectors for other statics analysis responses.

Format:

DSADJC UG,ADJG,DRDUTB/ADJGTOT,DRDUTC/MFACTOR $

Input Data Blocks:

UG Matrix of analysis model displacements

ADJG Matrix of existing adjoint solution vectors

DRDUTB Table of adjoint load attributes

Output Data Blocks:

ADJGTOT Matrix of adjoint solution vectors matrix appended with compliance related vectors

DRDUTC Table of adjoint load attributes with updated solution vectors ID

Parameter:

MFACTOR Input-real-default=1.0. Multiplicative factor applied to compliance adjointsolution vectors before appending them

EULAN

Computes transformation matrix.

Format:

EULAN CASEDR,BGPDTS,CSTMS,ESTNL/TRMBD,TRMBU/S,N,ITRMBUD $




Input Data Blocks:

CASEDR Table of case control command images

BGPDTS Basic grid point definition table


ESTNL Nonlinear element summary table at current step

Output Data Blocks:

TRMBD Table of Euler angles for transformation from material to basic coordinatesystem in the deformed configuration

TRMBU Table of Euler angles for transformation from material to basic coordinatesystem in the undeformed configuration

Parameter:

ITRMBUD Input-integer-no default. Output flag=1 for TRMBU=2 for TRMBD

FEMAOAC

Frequency response FEM Adaptive Order Solution interface for acoustics and vibro-acousticproblems in SOL 108. FEMAOAC requires that the FEMAOPRE module be called first.

Format:

FEMAOAC BGPDTS,CASEALL,CONTACT,CSTMS,DITS,DLT,DYNAMIC,ECTS,EDTS,EPT,EQEXINS,FRL,FOL,GEOM4S,FEMAOMAT,,,,,,,,MPT,PDFTAB,SILS,USETD,UDFTAB,SYSVEC,DOFASET,DOFSTR,UGSTAB,PGSTAB/UGFAO,VELAO,INTAO,XACPWRT2,XACPWRI2,XACPWR2,XACTRLS2,UDSAO,,,,,,,/IERR $

Input Data Blocks:


CASEALL Table of case control command images. Output by IFP1

CONTACT Table of bulk entry related to surface contact


DITS Table of TABLEij bulk entry images

DLT Table of dynamic loads. Output by DPD





ECTS Element connectivity table

EDTS Element data table

EPT Element property table

EQEXINS Equivalence table between external and internal grid/scalar identification numbers

FRL Frequency response list. Output by FRLGEN

FOL Frequency response frequency output list. Output by FRLG

GEOM4S Table of bulk entries related to constraints

FEMAOMAT Table containing stiffness, mass, viscous damping, and structural dampingnominal matrices, delta matrices and their scale factors as an input for stronglycoupled vibro-acoustics FEMAO solution

MPT Table of bulk entry images related to material properties

PDFTAB Table containing structural loads as an input for vibro-acoustics FEMAO solution

SILS Scalar index list

USETD DOF set membership table for p-set. Output by DPD

UDFTAB Table containing d-size displacements as an input for weakly coupledvibro-acoustics FEMAO solution

SYSVEC Table containing current system cell values

DOFASET DOF look up table containing a-set grid IDs and components

DOFSTR DOF look up table containing g-set grid IDs and components

UGSTAB Table containing g-size displacements as an input for weakly coupledvibro-acoustics FEMAO solution

PGSTAB Table containing g-size loads as an input for weakly coupled vibro-acousticsFEMAO solution

Output Data Blocks:

UGFAO Table of acoustic pressures output at microphone points

VELAO Table of acoustic velocities output at microphone points

INTAO Table of acoustic intensity output at microphone points

XACPWRT2 Data block that contains transmitted power output for AML regions and GROUPsof 2D elements




XACPWRI2 Data block containing incident acoustic power output for FACES or GROUPs of2D elements

XACPWR2 Data block containing acoustic power output for AML regions and GROUPs of2D elements

XACTRLS2 Table of transmission loss output from acoustic or vibro-acoustic FEMAO solution

UDSAO Table of structural displacements output in strongly vibro-acoustic solution

Parameter:

IERR Output-integer-default=0. Error flag output by acoustics/vibro-acoustics FEMAOsolver

FEMAOPRE

FEMAOPRE produces the input tables for the FEMAOAC module, which is the solver interface forSOL 108 FEM Adaptive-Order direct frequency response.

Format for Strongly-Coupled Vibro-Acoustic SOL 108 FEMAO Solution:

FEMAOPRE BGPDTS,CASEF,EQEXINS,DOFVEC,FOL,UDF,PDF,UGS,PGS,CKDD,CMDD,CBDD,CK4DD,SCALEFAC/DOFASET,DOFSTR,SYSVEC,UDFTAB,PDFTAB,UGSTAB,PGSTAB,FEMAOMAT/IERR/NOASET/NOGSET//FREQDEP/YSFLAG $

Format for Weakly-Coupled SOL 108 FEMAO Solution:

FEMAOPRE BGPDTS,CASEF,EQEXINS,DOFVEC,FOL,UDF,PDF,UGS,PGS,,,,,/DOFASET,DOFSTR,SYSVEC,UDFTAB,PDFTAB,UGSTAB,PGSTAB,/IERR/NOASET/NOGSET//FREQDEP/YSFLAG $

Input Data Blocks:


CASEF Table of case control command images. Output by IFP1

EQEXINS Equivalence table between external and internal grid/scalar identification numbers

DOFVEC Output from VEC module. DOFVEC is DOF vector containing grid IDs and activeDOF component numbers. The size of the SET2 specified on the VEC moduledetermines the DOFVEC size. For more information, see the VEC module in theDMAP Programmer's Guide.

FOL Frequency response frequency output list. Output by FRLG

UDF Data block containing d-size weakly-coupled structural displacements




PDF Data block containing d-size weakly-coupled structural loads

UGS Data block containing g-size weakly-coupled structural displacements

PGS Data block containing g-size weakly-coupled structural loads

CKDD Data block for stiffness. CKDD can also be frequency dependent stiffness

CMDD Data block for mass

CBDD Data block for viscous damping. CBDD can also be frequency dependent viscousdamping

CK4DD Data block for structural damping. CK4DD can also be frequency dependentstructural damping

SCALEFAC Data block containing frequency dependent scale factors. Generated by FFREST3

Output Data Blocks:

DOFASET Table that contains DOFVEC for a-size in table format

DOFSTR Table that contains DOFVEC for g-size in table format

SYSVEC Table that contains current system cell values

UDFTAB Table that contains a-set size structural displacements to be input to FEMAOACmodule

PDFTAB Table that contains a-set size structural loads to be input to FEMAOAC module

UGSTAB Table that contains a-set size structural displacements to be input to FEMAOACmodule

PGSTAB Table that contains g-set size structural loads to be input to FEMAOAC module

FEMAOMAT Table that contains stiffness, mass, viscous damping, and structural dampingnominal matrices, and if frequency dependent, also contains delta matrices andtheir scale factors to be an input to FEMAOAC module for strongly-coupledvibro-acoustics FEMAO solution

Parameter:


NOASET Input-integer-no default. Size of a-set

NOGSET Input-integer-no default. Size of g-set




FREQDEP Input-integer-default=0. Flag to denote frequency-dependent problem= 0 for not frequency-dependent= 1 for frequency-dependent

YSFLAG Input-integer-default=0. Flag to denote presence of structural enforced motion= 0 for no structural SPCDs found= 1 for structural SPCDs present

FEMAOPST

Produces sorted output data blocks from a FEMAO solution that can be further post-processed indownstream data recovery performed in SUPER3. FEMAOPST requires the solver interface for SOL108 FEMAO direct frequency response. The FEMAOAC module must be called first to generate theinput for FEMAOPST.

Format:

FEMAOPST CASEF,UGFAO,VELAO,INTAO,UNUSED,XACPWRT2,XACPWRI2,XACPWR2,XACTRLS2/OUGF1,OACVELO1,OACINT1,UNUSED,OACPWRT2,OACPWRI2,OACPWR2,OACTRLS2/IERR/NOASET $

Input Data Blocks:

CASEF Table of case control command images. Output by IFP1

UGFAO Table of acoustic pressures output at microphone points output by FEMAOAC

VELAO Table of acoustic velocities output at microphone points output by FEMAOAC

INTAO Table of acoustic intensities output at microphone points output by FEMAOAC

XACPWRT2 Data block that contains transmitted power output for AML regions and GROUPsof 2D elements output by FEMAOAC

XACPWRI2 Data block that contains incident acoustic power output for FACES or GROUPsof 2D elements output by FEMAOAC

XACPWR2 Data block containing acoustic power output for AML regions and GROUPs of 2Delements output by FEMAOAC

XACTRLS2 Table of transmission loss output from acoustic or vibro-acoustic femao solutionoutput by FEMAOAC

Output Data Blocks:

OUGF1 Data block of acoustic pressures at microphone points in SORT1 format

OACVELO1 Data block of acoustic velocities at microphone points in SORT1 format

OACINT1 Data block of acoustic intensities at microphone points in SORT1 format




OACPWRT2 Data block of transmitted acoustic power for AML regions and GROUPs of 2Delements in SORT2 format

OACPWRI2 Data block of incident acoustic power for FACES or GROUPs of 2D elementsin SORT2 format

OACPWR2 Data block of acoustic power for AML regions and GROUPs of 2D elements inSORT2 format

OACTRLS2 Data block of acoustic transmission loss in SORT2 format

Parameter:


NOASET Input-integer-no default. Size of a-set

FFREST1

FFREST1 generates an ESTF table that contains frequency-dependent CDAMP, CELAST andCBUSH entries from the EST table and other tables in SOL 108 FEM Adaptive-Order strongly-coupleddirect frequency response with frequency-dependent structural materials.

Format:

FFREST1 ECT,EST/ESTF,PIDT,PIDTID/ETOPT $

Input Data Blocks:



Output Data Blocks:

ESTF Reduced EST data block that contains CELASi, CDAMPi, and CBUSH entrieswith frequency-dependent properties only

PIDT Table that contains frequency-dependent property IDs and associated table IDs

PIDTID Table that contains element IDs with frequency-dependent property IDs andassociated table IDs




Parameter:

ETOPT Input-integer-default=1. Option for frequency-dependent element type= 1 for CDAMP1 and CDAMP3 elements, and CBUSH elements with B(i) andTBID(i)= 2 for CELAS1 and CELAS3 elements, and CBUSH elements with K(i), GE(i),TKID(i), and TGEID(i)

FFREST2

FFREST2 generates a unit ESTF table that contains frequency-dependent CDAMP, CELAST, andCBUSH entries from EST table for SOL 108 FEM Adaptive-Order strongly-coupled direct frequencyresponse with frequency-dependent structural materials. A call to FFREST1 is required to generatethe input data blocks for FFREST2.

Format:

FFREST2 ESTF,PIDTID/ESTUNIT/PIDVAL/ETOPT $

Input Data Blocks:

ESTF Reduced EST data block that contains CELASi, CDAMPi, and CBUSH entrieswith frequency-dependent properties only. ESTF is generated by FFREST1

PIDTID Table that contains element IDs with frequency-dependent property IDs andassociated table IDs. PIDTID is generated by FFREST1

Output Data Block:

ESTUNIT ESTF data block with nominal values replaced with 1.0

Parameters:

PIDVAL Input-integer-no default. Property ID of the current frequency-dependent elementtype


FFREST3

FFREST3 generates scale factors for each frequency-dependent property at each frequency for SOL108 FEM Adaptive-Order strongly-coupled direct frequency response with frequency-dependentstructural materials.




Format:

FFREST3 DIT/TABSCAL/FREQVAL/TKID/TBID/TGEID/ETOPT $

Input Data Block:


Output Data Block:

TABSCAL Table that contains frequency value and corresponding scale factor

Parameters:

FREQVAL Input-integer-no default. Frequency at which scale factors are calculated

TKID Input-integer-no default. TABLEDi entry identification number forfrequency-dependent stiffness

TBID Input-integer-no default. TABLEDi entry identification number forfrequency-dependent viscous damping

TGEID Input-integer-no default. TABLEDi entry identification number forfrequency-dependent structural damping


FRFIN

Interpolates complex frequency-dependent matrices.

Interpolates complex frequency-dependent matrices defined by FRFSTIF, FRFFLEX, FRFOTM, andFRFOMAP bulk entries. The magnitude and phase are linearly interpolated separately.

Format:

FRFIN DYNAMIC,EQEXIN,DIT/O1,O2,O3,O4/FREQVAL/P2/FRFID/P4/P5/P6/P7/P8/P9/S,N,FOUND $

Input Data Blocks:


EQEXIN Equivalence table between external and internal grid/scalar identification numbers





Output Data Blocks:

Oi Output data blocks that depend on the value P2

Parameters:

FREQVAL Input-real-no default. Frequency value in Hz for retrieving frequency-dependentmatrix terms

P2 Input/integer-default=0. Option selection described in the table that follows

FRFID Input-integer-no default. Identification number of the requested FRFSTIF,FRFFLEX, or FRFOTM bulk entry

P4 Output-integer-no default. Parameter definition depends on P2

P5 Output-integer-no default. Parameter definition depends on P2

P6 Output-real-default=1.0. Parameter definition depends on P2




P10 Output-real-default=1.0E-11. Parameter definition depends on P2

FOUND Output-integer-no default. Output flag that indicates whether FRFSTIF, FRFFLEX,or FRFOTM bulk entries are found: 0 if not found; 1 if found

Remarks:

1. The following procedure explains how the module interpolates complex stiffness or flexibilityvs. frequency tabular data.

a. The module identifies the bounding tabular data points (flower,klower) and (fupper,kupper) suchthat fupper ≤ f ≤ fupper, where frequencies are denoted as f and stiffness or flexibility values aredenoted by k.

b. If the tabular stiffness or flexibility values are given in the real/imaginary format, the moduleconverts the data to the magnitude/phase format.

Note

When the module calculates phase angles from the real and imaginary parts of acomplex number, the result ranges between -π and +π.




c. The module uses the magnitudes of the bounding stiffness or flexibility values to calculate themagnitude of the lookup value for the stiffness or flexibility from the following equation:

d. The module interpolates the phase angles as follows:

A. If necessary, the module converts the phase angles for the bounding phase angle valuesso that they range between 0 and 2π.

For example, θ = -π / 2 is converted to θ = +3π / 2.

B. The module calculates the angle subtended between the bounding phase angles asfollows:

C. If Δθ ≤ π, the module calculates the lookup value for the phase angle from the followingequation:

D. If Δθ > π, the module calculates the lookup value for the phase angle from the followingequation:

2. The module converts the lookup value from the magnitude/phase format to the real/imaginaryformat.

Summary of Options:

P2 Option Description

P2 = 0 Module configuration for FRFSTIF and FRFFLEX input.

P2 = 1 Module configuration for FRFOTM input.

P2 = 2 Module configuration for FRFOMAP input.

Option P2 = 0

Module configuration for FRFSTIF and FRFFLEX input.




Format:

FRFIN DYNAMIC,EQEXIN,DIT/MATFRF,,,/FREQVAL/0/FRFID/S,N,FRFTYPE/S,N,TYPE/S,N,LSCALE/S,N,FSCALE/S,N,PSCALE/S,N,QSCALE/S,N,EPS/S,N,FOUND $

Output Data Block:

MATFRF Interpolated dynamic matrix from FRFSTIF or FRFFLEX bulk entries

Parameters:

FRFTYPE Output-integer-no default. Type of FRF matrix: 0 for FRFSTIF; 1 for FRFFLEX

TYPE Output-integer-no default. Type of dynamic stiffness/flexibility: 1 fordisplacement; 2 for velocity; 3 for acceleration

LSCALE Output-real-default=1.0. Length scale factor

FSCALE Output-real-default=1.0. Force scale factor

PSCALE Output-real-default=1.0. Pressure scale factor

QSCALE Output-real-default=1.0. Acoustic source scale factor

EPS Output-real-default=1.0E-11. Singular value threshold (only output for FRFFLEX)

Example:

FRFIN DYNAMIC,EQEXIN,DIT/MATFRF,,,/350.0/0/100/S,N,FRFTYPE/S,N,TYPE/S,N,LSCALE/S,N,FSCALE/S,N,PSCALE/S,N,QSCALE $

Option P2 = 1

Module configuration for FRFOTM input.

Format:

FRFIN DYNAMIC,EQEXIN,DIT/MATOTMF,MATOTMD,MATOTMV,MATOTMA/FREQVAL/1/FRFID///S,N,LSCALE/S,N,FSCALE/S,N,PSCALE/S,N,QSCALE//S,N,FOUND $

Output Data Blocks:

MATOTMF Interpolated dynamic matrix from FRFOTM bulk entries with column TYPEINset to FORC

MATOTMD Interpolated dynamic matrix from FRFOTM bulk entries with column TYPEINset to DISP




MATOTMV Interpolated dynamic matrix from FRFOTM bulk entries with column TYPEINset to VELO

MATOTMA Interpolated dynamic matrix from FRFOTM bulk entries with column TYPEINset to ACCE

Parameters:

LSCALE Output-real-default=1.0. Length scale factor

FSCALE Output-real-default=1.0. Force scale factor

PSCALE Output-real-default=1.0. Pressure scale factor

QSCALE Output-real-default=1.0. Acoustic source scale factor

Example:

FRFIN DYNAMIC,EQEXIN,DIT/MATOTM,VTYPE,,/15.5/1/99///S,N,LSCALE//S,N,PSCALE $

Option P2 = 2

Module configuration for FRFOMAP input.

Format:

FRFIN DYNAMIC,EQEXIN,DIT/VECOTMF,VECOTMD,VECOTMV,VECOTMA/FREQVAL/2/FRFID////////S,N,FOUND $

Output Data Blocks:

VECOTMF Vector with 1.0 at positions where output is specified as force

VECOTMD Vector with 1.0 at positions where output is specified as displacement

VECOTMV Vector with 1.0 at positions where output is specified as velocity

VECOTMA Vector with 1.0 at positions where output is specified as acceleration

FRLGAC

Generates frequency-dependent acoustic loads. Requires that the GPAC module be called first.

Format:

FRLGAC CASECC,USETD,FRL,MICLOC,DIT,FOL/PGFAC,PIGFAC,PTMIC $




Input Data Blocks:


USETD Grid point definition table


MICLOC Microphone location table for ATV computation



Output Data Blocks:

PGFAC Acoustic loads

PIGFAC Incident pressure

PTMIC Microphone property table for ATV computation

Remarks:

1. If MICLOC is not purged, the output data block is load vectors for the ATV computation.

FTCHGM2

Searches the GEOM2 data block to retrieve the maximum element ID for use in SOL 402.

Format:

FTCHGM2 GEOM2,,//MAXEID $

Input Data Block:

GEOM2 Table of bulk entries related to element connectivity and scalar points

Output Data Blocks:

None

Parameters:

MAXEID Output-integer-no default. Returned maximum element ID number




GPACAO

Outputs coupling quality data block for fluid/structure interface by processing geometry and elementinformation for frequency response FEM Adaptive Order solution interface for acoustics andvibro-acoustic problems in SOL 108. Also outputs additional FEMAO solution diagnostics such asthe maximum frequency per element and element orders information. GPACAO requires that theFEMAOPRE module be called first to generate the SYSARR input table.

Format:

GPACAO BGPDT,CSTM,SIL,ECT,EQEXIN,EDT,GEOM2,CASECC,DYNAMIC,EPT,DIT,CONTACT,SYSARR,FRL,GEOM4,MPT/OEFMXORD,,OACCQ,,,,,,,/S,N,LUSET/S,N,MATCH/S,N,CTYPE $

Input Data Blocks:



SIL Scalar index list



EDT Element data table

GEOM2 Table of bulk entry images related to element connectivity and scalar points.Output by IFP



EPT Element property table


CONTACT Table of bulk entry related to surface contact

SYSARR Table containing current system cell values

FRL Frequency response list. Output by FRLGEN

GEOM4 Table of bulk entries related to constraints

MPT Table of bulk entry images related to material properties




Output Data Blocks:

OEFMXORD Data block that contains a list of element IDs with maximum frequency andelement order diagnostics for FEMAO solution

OACCQ Data block that contains acoustic coupling quality

Parameter:

LUSET Input-integer-default=0. The number of DOF in the g-set

MATCH Input-integer-default=0. Type of fluid/structural mesh matching= 0 for matching mesh= 1 for non-matching mesh

CTYPE Input-integer-default=0. Flag to denote the type of acoustic coupling= 0 for uncoupled acoustics= 1 for vibro-acoustic coupling

MFRQADD

Compute total or scatted pressure output matrices based on the TOTAL or SCATR option in thePRESSURE case control command.

Format:

MFRQADD CASECC,FRL,PI,FOL,PS/POUT,PT/S,N,ATVSOL $

Input Data Blocks:



PI Incident pressure that corresponds to the FRL table


PS Scattered pressure that corresponds to the FOL table

Output Data Blocks:

POUT Pressure matrix with columns that correspond to the FOL. The output depends onthe TOTAL or SCATR option in the PRESSURE case control command

PT Output matrix with columns that correspond to the FOL. The output is the TOTALpressure




Parameters:

ATVSOL Output-integer-default=0. Controls ATV computation.

0 Do not perform ATV computation

1 Perform ATV computation

MODEQEXN

Splits equivalence table into an equivalence table for the structure and an equivalence table for thefluid.

Format:

MODEQEXN EQEXIN,BGPDT,GLIST/EQEXINS,EQEXINF/ $

Input Data Blocks:



GLIST Grid list to remove

Output Data Blocks:

EQEXINS Equivalence table between external and internal grid/scalar identification numbersfor the structure

EQEXINF Equivalence table between external and internal grid/scalar identification numbersfor the fluid

Remarks:

1. Both EQEXIN and BGPDT cannot be purged.

MODGMATV

Inputs the bulk entry images specified for acoustic analysis. Requires that the GPAC module becalled first.

Format:

MODGMATV GEOM1,GEOM2,EPT,EDT,PVT,GEOM1ATV,GEOM2ATV,EPTATV,PVTATV/OGEOM1,OGEOM2,OEPT,ATVMIC/EOFFSET/GOFFSET/POFFSET/S,N,ACEXIT $




Input Data Blocks:



EPT Table of bulk entry images related to element properties

EDT Table of aero and element deformations

PVT Parameter value table from IFP module (PARAM entries)

GEOM1ATV Table of bulk entry images related to geometry of ATV

GEOM2ATV Table of bulk entry images related to element connectivity and scalar points of ATV

EPTATV Table of bulk entry images related to element properties of ATV

PVTATV Parameter value table from IFP module (PARAM entries) of ATV

Output Data Blocks:

OGEOM1 Table of bulk entry images related to combined geometry

OGEOM2 Table of bulk entry images related to combined element connectivity and scalarpoints

OEPT Table of bulk entry images related to combined element properties

ATVMIC Microphone grids of ATV

Parameters:

EOFFSET Input-integer-default=0. Element offset of ATV component.

GOFFSET Input-integer-default=0. Grid offset of ATV component.

POFFSET Input-integer-default=0. Property offset of ATV component.

ACEXIST Output-integer-no default. Acoustic solid element existence.

0 Acoustic solid elements do not exist

1 Acoustic solid elements exist

Remarks:

1. All of the input datablocks cannot be purged.




MONEGRP3

Forms MONPNT3 ELEMGRP g-set load vector for each subcase. The load vector is constructedfrom the grid point force output.

Format:

MONEGRP3 XFLGEGRP,BGPDT,CSTM,EDT,GEOM2,OGPFB1/GPFEGRP,XFLGEGRP2/NMLODMOD $

Input Data Blocks:

XFLGEGRP The TABLE stores 5 times the number of MONPNT3 values. The value consist ofthe following:

1. The "BIT" pattern for the XFLAG setting for each MONPNT3. The XFLAG bitpattern is as follows:= 0 - includle all forces (nothing to exclude)= 1 - S defined exclude SPC FORCES= 2 - M defined exclude MPC FORCES= 4 - A, L or P defined exclude applied FORCES= 8 - D defined exclude DMIG FORCES= 15 excludes all loads

2. The AXES (number of columns) DOF for the MONPNT3. Set a negativeNCOL to indicate an empty GROUP C. When this occurs the MONPNT3 willnot be processed, but others C will continue to be processed. Necessaryfor Superelement C processing where a GROUP may only exist in certainsuperelements.

3. THE ELEMGRP group number for the MONPNT3s

4. The MONPNT3 name (2 words)



CSTM Coordinate system transformation table with required CIDs

EDT GROUP definition that is used by Group access routines


OGPFB1 Grid point forces

Output Data Blocks:

GPFEGRP Grid point force matrix (g-set x numsubcases)




XFLGEGRP2 TABLE from MONVEC3 with partial MONPNT3 definitions. (Same as XFLGEGRPunless an error has occurred.)

Parameter:

NMLODMOD Input/output-integer. The number of subcases/modes (load sets). The numberof subcases contained in OGPFB1 is used. Enforce that every subcase has aGPFORCE request. Set to a negative value if ERROR

MONPNT2

Computes force/stress/strain values for elements specified on the MONPNT2 bulk entry.

Format:

MONPNT2 EDT,OES1,OEF1,OSTR1,CASEDR//NMSUBCAS $

Input Data Blocks:

EDT Element data table

OES1 Table of element stresses or strains in SORT1 format

OEF1 Table of element forces in SORT1 format

OSTR1 Table of element strains in SORT1 format

CASEDR Case control data block for data recovery of a specific subcase

Output Data Blocks:

None

Parameters:

NMSUBCAS Input-integer-no default. Total number of subcases

MONVEC3

Forms the rigid body vectors for MONPNT3 monitor points.

Format:

MONVEC3 EDT,BGPDT,CSTM,GEOM2/SMK,XFLGEGRP/ $




Input Data Blocks:

EDT Table that defines the requested MONPNT3 output vectors


CSTM Coordinate system transformation table with required CIDs


Output Data Blocks:

SMK Matrix that stores the collection of vectors that are requested by the MONPNT3table







Parameters:

None

MPP3

Controls the MONPNT3 monitor point output.

Format:

MPP3 EDT,BGPDT,CSTMS,CASECC,MONOUT3,XFLGEGRP//NMSUBCAS/NMODES $




Input Data Blocks:

EDT Table that defines the requested MONPNT3 output vectors


CSTMS Coordinate system transformation table with required CIDs

CASECC Case control data table

MONOUT3 Monitor point3 output vector. Each column represents the “AXES” (i.e. DOF)results for the monitor point3 in the basic coordinate system







Output Data Blocks:

None

Parameters:

NMSUBCAS Input-integer. Number of subcases (load sets)

NMODES Input-integer. Number of modes. Zero for statics

TOTLOAD

Calculates load vector for distributed load defined by the FORCDST bulk entry. This module reads allof the FORCDST present in GEOM3, computes the load vector for each of them, and then stores




the result in a FORCDSTT table. The FORCDSTT table can then be input to other modules suchas TRLG and SSG1.

Format:

TOTLOAD GEOM2,GEOM3,EQEXINS,BGPDTS,SILS,CSTMS,CONTACT,EST/FORCDSTT/S,N,ERRTOTLD/F06OUTPT $

Input Data Blocks:

GEOM2 Table of element definitions

GEOM3 Distributed load definitions (FORCDST bulk entries)

EQEXINS Table between external and internal DOFs


SILS Scalar index list

CSTMS Table of coordinate systems

CONTACT BSURF, BSURFS, and BEDGE definitions that are used by FORCDST


Output Data Block:

FORCDSTT Table of patch center of area, patch triad, and load vector for each distributedload in GEOM3

Parameter:

ERRTOTLD Output-logical-no default. Table of patch center of area, patch triad, and loadvector for each distributed load in GEOM3=FALSE for no error=NOT(0) for fatal error

F06OUTPT Input-integer-default=0. Print load vector information for each distributed load thatis processed to the .f06 file=0 for no output=1 for FORCDST SID, patch cg, and triad vectors

TRLOSS

Calculates acoustic transmission loss from acoustic incident power and acoustic transmitted poweras follows:




where TL is the acoustic transmission loss, Pi is the acoustic incident power, and Pt is the acoustictransmitted power.

Format:

TRLOSS CASEDR,FOL,OACPWRI1,OACPWRT1/OACTRLS1 $

Input Data Blocks:

CASEDR Case Control data block for data recovery

FOL Output frequency list

OACPWRI1 Acoustic incident power output data block in Sort 1 format

OACPWRT1 Acoustic transmitted power output data block in Sort 1 format

Output Data Block:

OACTRLS1 Acoustic transmission loss output data block in Sort 1 format

TRLPSD

Calculates acoustic transmission loss PSD function from acoustic incident power PSD function andacoustic transmitted power PSD function as follows:

where TL is the acoustic transmission loss PSD, Pi,PSD is the acoustic incident power PSD, andPt,PSD is the acoustic transmitted power PSD.

Format:

TRLPSD CASERAND,CASEDR,FOL,OIPPSD1,OTPPSD1/OTLPSD1 $

Input Data Blocks:

CASERAND Case Control data block for random data recovery

CASEDR Case Control data block for data recovery

FOL Output frequency list

OIPPSD1 Acoustic incident power PSD output data block in Sort 1 format




OTPPSD1 Acoustic transmitted power PSD output data block in Sort 1 format

Output Data Block:

OTLPSD1 Acoustic transmission loss PSD output data block in Sort 1 format



Chapter 15: Problem Report (PR) fixes

Problem Report (PR) fixesThe following list summarizes the problems that are fixed in NX Nastran 12. If applicable, workaroundinformation is provided for use with earlier versions of NX Nastran.

PR#Problemfound inversion

Problem Description

1882042 V8.0In specific SOL 101 contact models, when contact is defined with tetrahedralelements on one side and hexahedral elements on the other side, the resultsare inaccurate.

1923676 V8.5In SOL 101, when you constrain a bolt node with an SPC, the solver outputsincorrect SPC forces at the bolt node. Also, in this case, there is a mismatchbetween the results for the OLOAD and SPCFORCE resultants.

1978373 V9.0

In SOL 101 bolt processing, the following issues may occur.

• The beam axial force does not line up with the requested bolt pre-load.

• Convergence problems.

1991389 V9.0

In SOL 101, when you perform a contact analysis with composite elements(elements pointing to PCOMP card) and the ply angle exceeds or undercutsa certain angle threshold, grid point singularities occur. This results froma negative equivalent Young's modulus for contact or glue elements withanisotropic materials.

The following workaround presents a method to evaluate the equivalent Young'smodulus for MAT2 or MAT9 and guarantee a positive EMOD, when the inputmaterial properties are correct:

• For MAT2:

EMOD = (C11 + C22) / 2

POI = C12 / EMOD

EMOD = EMOD*(1 - POI*POI)

where:

Cii is component of modulus matrix.

• For MAT9:

EMOD = (E11+E22+E33) / 3

where:



Eii are obtained from compliance matrix (compliance matrix = inverse ofelastic modulus matrix).

2085584 V5.0In SOL 101, NX Nastran terminates when a model contains shell elements withoffset and TEMPP1 load is applied. The results for element forces and stressesare incorrect.

2206167 V7.1

In SOL 107, the output of complex modes varies with the memory allocatedby the solver. An error message such as the one shown below is printed inthe .f06 file.

*** SYSTEM INFORMATION MESSAGE 6940 (CLREDS)SPILL OCCURRED WHEN CALCULATING LANCZOS VECTORS.... OUT OF A TOTAL OF LANCZOS VECTORS HAVE BEEN STOREDOUT OF CORE.USER ACTION: TO PREVENT SPILL, INCREASE OPEN CORE SIZE BYAT LEAST .25848E+08 WORDS

2226569 V8.5

SOL 101 does not generate correct results for models with CWELD elementsthat have the ELEMID, ELPAT, or PARTPAT weld format. This is due to incorrectprocessing of weld thickness when the SPOT option is set on the PWELD bulk entry.CWELD thickness was always considered as the distance between the weld nodesGA and GB on the CWELD bulk entry.

2233974 V9.0

In a SOL 101, contact result are not always correct for models that have INIPENE

set to 0.

The problem has been fixed and the contact algorithm has been improved tohandle INIPENE=0 better.

2235147 V9.0 The contact algorithm needs to be improved when it deals with friction models.

6003819 V6.0

In SOL 103, depending on the shift pattern, some eigenvectors may have verylarge rotational terms.

In NX Nastran 12.0, the shift selection process in Lanczos algorithm is improvedto avoid this issue.

6758817 V8.1 SOL 101 generates incorrect stress results for models with CQUAD4 elements withoffset and variable thickness.

6896933 V8.5

In SOL 101, the solver terminates with the following fatal error message(preceded by a warning message) when the model contains pre-loaded boltsand a TEMP(LOAD) specification.

*** USER WARNING MESSAGE 4012 (GP3D)THERE IS NO ELEMENT, GRID POINT, OR DEFAULT TEMPERATUREDATA FOR TEMPERATURE SET ..., WITH RESPECT TOELEMENT ID = ...

*** USER FATAL MESSAGE 4016 (GETEMP)THERE ARE NO TEMPERATURES FOR TETRA ELEMENT ... IN SET ...

6945701 V9.0 In SOL 112, residual vector calculation for RDMODES produces a fatal error iflinearly dependent loads are present in the model.



Problem Report (PR) fixes

6971532 V8.5

In SOL 101, results of inertia relief with INREL = -1 are incorrect for a contactmodel in which parts of the structure comes in contact with another part.

The problem occurs because the solver does not include inertia forces in thedisplacement computation.

The workaround is to use the following DMAP alters. You must add these altersto the executive section between the SOL 101 and the CEND line.

$ Following alter searches for occurrences of INREL in$ example.dat and adds APPEND PT,PT6/PTX $ just after the$ statement:$ "IF(INREL = -1 OR (INREL = -2 AND DMAPNO = 101))THEN $."$compile example, list $ example.dat $alter 'inrel'(11,),''$$MESSAGE '**** CODE ADDED 1:: TO ADD CONTACT FORCE TO '$$MESSAGE 'LOAD VECTOR ****' $APPEND PT,PT6/PTX $$$ Following alter searches for line: $$ SOLVE QRR,QRL,,,/URAX//-1 $$ in example.dat and $$ adds EQUIVX PLI/PT/-1 $ just before the endif of the $$ "IF (INREL = -1 OR (INREL = -2 AND DMAPNO =101)) THEN $ "$ statement.$alter 'SOLVE'(3,15),''$$MESSAGE '** CODE ADDED 2::ACCOUNT FOR INERTIA LOADS**' $EQUIVX PLI/PT/-1 $$endalter $

7107136 V9.0

When NX Nastran solves a SOL 111 solution for RDMODES with DMP setting,the solver outputs redundant data blocks to the .op2 file.

The problem was fixed in V9.1, although the problem report was closed in NXNastran 12.0.

7149385 V10.0 In a SOL 111 random response analysis, for models with CQUADR elements, stressresults are reported in incorrect nodal order for elements.

7365107 V9.0

In SOL 101 bolt processing, when you set the BCTPARM RESET entry to either 1 or0, the solver may generate different results in some models that have multiplesubcases.

The RESET=0 (default) behavior has not changed in NX Nastran 12. See thedescription below.

The RESET=1 behavior has changed. See the full description below. Prior toNX Nastran 12, the RESET=1 functionality would resume the contact iterationsfrom the initial contact state which did not include the effects of bolt preloador service loads.

The following is the full description of the NX Nastran 12 behavior.

When a bolt preload is defined on CBEAM or CBAR elements and contact isin the model, the software runs an initial preload solution to compute the strain




in the bolt and to compute a converged set of contact status conditions beforeapplying any service loads. The bolt preload behavior depends on the RESETcontact parameter defined on the BCTPARM bulk entry.

• When RESET=1, for the consecutive solutions in the same subcase asthe preload and for any consecutive subcases, the software applies thecomputed bolt strain from the initial preload solution and it uses the finalcontact status from the initial bolt preload solution as the starting contactstatus.

• When RESET=0 (default), for the consecutive solution for the same subcaseas the preload, the software applies the computed bolt strain from the initialpreload solution and it uses the final contact status from the initial boltpreload solution as the starting contact status (same as RESET=1). For thesolutions for any consecutive subcases, the software applies the computedbolt strain from the initial preload solution, and it applies the final contactstatus from the end of the prior subcase.

• When both RESET=0 or RESET=1, if the subcase which computes the boltpreload includes only the bolt preload and no service loads, the two passsolution described above still occurs. That is, the first solution computes thestrain in the bolt and the converged set of contact status conditions. Sincethere are no service loads for this scenario, the second solution is almosta repeat of the first, although the contact status results from the secondsolution may be slightly different than the contact status results from the first.The reason is that the second solution begins with the final contact statusfrom the first, but also continues to iterate on this contact condition untilthe hard coded minimum number of contact iterations is reached. You canoptionally adjust the contact convergence criteria with the NCHG parameteron the BCTPARM bulk entry if you would like the contact status betweenthe first and second solutions to be more similar.

7387293 V8.5

In a SOL 101 bolt pre-load computation, when you solve two subcases with thesame bolt parameter setting but with different ordering of glue sets, displacementresults differ. Contact iterations should be the same for the bolt pre-load portionin the two subcases because only the order of the specified glue container isdifferent in the deck.

Because NX Nastran 12 deals with contact friction differently, this issue hasbeen addressed.

7425926 V9.0In SOL 101, for models with contact, when the user sets PENT option to 0.0 onthe BCTPARM entry, the PENN value is also set to 0.0 instead of the default valueof 100.0.

7516560 V10.0.2

In SOL 101, when you perform a structural analysis with contacts and symmetricconstraints after a thermal analysis, the solve terminates with the following fatalerror.

*** SYSTEM FATAL MESSAGE 6144 (MERGE1)THE SIZES OF THE INPUT MATRICES AND PARTITIONING VECTORSARE INCOMPATIBLE. SPECIFICALLY:The number of rows in PSC is not equal to the numberof zeros in partitioning vector ...




7711075 V10.2

In SOL 153, when a nodal heat generation load is added to a node of ahexahedral element and a constant temperature is added to a beam element,SPCFORCE and OLOAD do not match in the .f06 file.

This issue occurs for heat transfer problems where SLOAD is combined with anodal displacement coordinate. Because a heat transfer problem has one DOFper node, it is not appropriate to use a nodal displacement coordinate system.

In NX Nastran 12, the solver checks that transformations are applied correctlyfor heat transfer problems.

7723354 V10.0 In SOL 101, bolt axial load results are different when the output request is part ofa single subcase and when it is part of a multi-subcase deck.

7724954 V9.1

In SOL 101, models with specified bolt pre-load direction for 3D solid boltelements fail with the fatal error message:

*** USER FATAL MESSAGE 2101 (GP4)GRID POINT # COMPONENT 3 ILLEGALLY DEFINED IN SETS UM US

The issue is a drawback of the cut method used in NX Nastran 11.0 and earlierreleases. This method uses MPCs at the cut to simulate a bolt pre-load. A newmethod is introduced for the cut bolts in NX Nastran 12.0 using glue.

7800777 V10.2 In SOL 111, solve terminates with a fatal error message from EMA module whena fluid glue pair is defined as the last glue pair on a BGADD bulk entry.

7819517 V9.1

In SOL 101, when the solver tries to solve a model with rigid elements usingLagrange method and with temperature load, a fatal error message is issuedfor elements having missing nodal temperature data. However, the fatal errormessage, reports the internal element ID instead of the external ID making itdifficult for the user to track the problem.

Now, NX Nastran reports the external element ID instead of the internal ID.

7855090 V11.0

In SOL 101, for some contact problems, the automatic penalty factor for contactcan be on the order of 1.0e-12 and can produce incorrect results.

The problem is fixed by improving the automatic penalty factor computationalgorithm.

The workaround is to set the PENN option in BCTPARM to manually select a penaltyfactor that is suitable for the problem.

7864728 V11.0 In SOL 101, for models with RFORCE with METHOD option set to 1, wrong centrifugalforces are calculated.

7891379 V9.0In SOL 101, models with contact definitions solved may report some contactelements in the active contact set that actually should not be in contact.

The error is due to an incorrect angle tolerance check for face normals.

7902486 V11.0

SOL101 fails with PIVOT ratio error when the model contains CTRIAR elementsthat have nodes with coordinate components (X, Y, or Z) with small numericalvalues.

The error is due to incorrect stiffness matrix calculation resulting in singularmatrices.




7908265 V11.0

A design optimization solution fails with the following message when the inputdeck contains PBEAML and PCOMPG bulk entries:

*** USER FATAL MESSAGE 7190 (DOPR1I) PTYPEPCOMPG DEFINED ON A DVPREL1 ... ENTRY CAN NOT BE FOUND ONA PROPERTY ENTRY.USER ACTION:DELETE THE DVPREL1 ENTRY OR INCLUDE AN ADDITIONAL PROPERTYENTRY.

7918473 P12.0 In SOL 101, a request to only output strain at CORNER and CPLYBMT does not workfor a composite solid model. Strain are output at the center and middle of plies.

7920631 V9.0

When SOL 111 with AMLS or RDMODES option computes modes, the solvereports numerical zeros for equivalent radiative power (ERP) for the DOFs thatare not part of any output request such as displacement, stress, or strain.

The workaround is to explicitly specify DOF sets for both ERP and displacementoutput.

7926799 V10.2

SEMODES analysis with STATSUB using an RLOAD produces the SYSTEM FATAL

MESSAGE 6704 during sparse matrix decomposition.

The workaround is to run the input decks with the following DMAP alter:

compile phase1e,nolist $alter 'ADD5', '' $ADD KGGT,KGGG/KGGGL/// $

7928583 V10.0In SOL 103, a response simulation solve fails when memory = estimate.

In NX Nastran 12, when memory = estimate, a minimum of 24MW is assignedto both LP64 and ILP64 executables.

7931648 V11.0In SOL 200, when NX Nastran solves a deck containing shell elements, thesolver writes internally generated PSHELL SIDs as opposed to the originalPSHELL SIDs that you assigned to the punch file.

7931781 V11.0

The punch file output request in SOL 200 for models with designedfrequency-dependent properties generates a punch file that contains updatedTABLED1 data in both the updated data portion and not updated portion of thepunch file. The not updated part should contain only the original TABLED1 data.

7940931 V10.0 In SOL108 for models with fluid superelements, the sparse data recovery resultsare incorrect (recovery results are zero) when QSET is not specified in PRESSURE.

7946418 V10.0.2

SOL 106 generates incorrect stress results for models that contain elements withhyperplastic material property.

This is due to inaccurate calculation of material properties for hyperplasticmaterials.

7949990 V11.0A SOL401 coupled multi-physics solution does not ramp the loads correctly atthe intermediate time points. Consequently, results from coupled multi-physicssolution are incorrect.

7954099 V11.0 If you submit a SOL 601, 106 input deck with SEPDIS on contact and a BCRESULTS

output request, the solver terminates with a fatal error message.

7961940 V10.0 NX Nastran outputs incorrect element strain energy for CELAS1 and CELAS3

elements.




7968374 V10.0

When SOL106 with iterative solver fails to converge, the intermediate resultsprior to failure of analysis are not saved.

The problem is fixed by saving the intermediate results before convergencefailure.

The workaround is to use the following DMAP alter in the deck:

COMPILE NLSTATIC,NOLIST$ALTER 'RUN TERMINATED BECAUSE AN ERROR OCCURRED'(1,1),'' $LOOPFLAG=FALSE $JUMP LENDDO $

7972075 V9.1 Request for output of gasket results in SOL 601, 106 yields no result output.

7978177 V9.1 SOL 601 does not output SPC forces at the master grid point for BCRESULTSoutput requests.

7996277 V11.0In SOL 103, a SEMODES solve for a model with superelements does not outputgrid point forces for one or multiple grids, when PARAM, SECOMB, YES is set.Outputs exist, when PARAM, SECOMB, NO (Default) is set.

8002668 V11.0

Bolt pre-load calculation in NX Nastran uses an MPC-based cut approach thatdoes not properly capture the bending of bolts. This is because MPC constraintsbetween the grid pairs on the cut surface do not capture rotations.

For SOL 101, when you define a bolt with ETYPE=2, the software cuts the boltin half, it creates new grid points resulting in grid pairs at the cut, it evenlydistributes the opposing axial bolt force to the grids on each side of the cut,and it solves a statics solution to determine the axial displacement of each bolthalf. The software then holds the grid pairs in their relative deformed state forthe consecutive static solution.

Beginning with NX Nastran 12, the software creates a glue connection at thecut which holds the grid pairs in their relative deformed state. The glue basedapproach accounts for bending along the bolt axis since rotational stiffness isincluded in the glue condition.

The glue approach is supported by the default sparse solver, but not supportedby the element iterative solver in SOL 101. If you run with the element iterativesolver in SOL 101 and you have defined the ETYPE=2 bolt, the software willrevert to an MPC approach. The MPC approach accounts for the axial stiffness,but not the rotations. As a result, bending is not accounted for with the MPCapproach.

8004008 V9.1

In SOL 101, when the RIGID = LAGRAN method is used for rigid and RBE3

elements, the Lagrange multiplier DOFs are created and the stiffness are scaledby the LMSTAT parameter. If any of these Lagrange DOFs are AUTOSPC’d, theintended effect of the Lagrange DOF is not obtained. Moreover, grounding checkgives incorrect results for such models.

NX Nastran 12 generates correct results, and to fix the grounding check,stiffness scaling for the rigid elements (RBE2, RBAR, and RTRPLT) is available. Thisenables the GROUNDCHECK criteria to pass for the G-set.




The workaround is to eliminate the AUTOSPC of the Lagrange DOF by specifyingPARAM, LMSTAT = 5. When you specify LMSTAT = 5, no Lagrange DOFs areAUTOSPC’d and the desired solution can be obtained.

Note

The use of PARAM, LMSTAT is available since the introduction of theRIGID = LAGRAN method in NX Nastran 5. However, the scaling of therigid elements is new for NX Nastran 12.

8293701 V9.0

In SOL 103, the grounding check can give wrong results for models with gluewith PIVOT ratio warning.

^^^ USER WARNING MESSAGE 9136 (SEKRRS) ^^^ENCOUNTERED EXCESSIVE PIVOT RATIOS IN MATRIX KLL.

This is due to a limitation of the glue formulation.

In NX Nastran 12.0, the glue formulation is improved to produce clean groundcheck results.

8314984

8324262V10.0

In a SOL101 model containing both beam bolts and solid bolts, NX Nastrancomputes wrong axial load in beam elements when any of the solid bolts havean ID less than the largest beam bolt ID.

The workaround in prior releases is to ensure that all solid bolt IDs are greater innumerical value than the largest beam bolt ID.

8317860 V10.0

SOL 103 computes incorrect rigid mode eigenvalues, when the model containspre-loaded bolts. The rigid body eigenvalues should be 0.0 (or numerical zero),but those computed by SOL 103 for a model with bolts are larger than 0.

The incorrect eigenvalues are caused by grounding effects that result fromstress-stiffening induced by bolt pre-load.

8323055 V10.0 In SOL 401, the applied loads at the constrained DOFs are excluded from OLOAD

output. As a result, the output of SPC resultant does not match the OLOAD resultant.

8327397 V11.0.1SOL 101 produces incorrect displacement results for contact models that involvefriction when you use the SMP option. The serial option generates correctresults.

8327570 V11.0 In SOL 109, the virtual mass associated with MFLUID in a model is not accountedfor in a direct transient analysis.

8327679 V11.0 SOL109 with MFLUID terminates without a solution when using PARAM, VMOPT, 2.It runs successfully with PARAM, VMOPT, 0 or 1.

8327724 V11.0In SOL 112, if you solve a model with MFLUID and PARAM, VMOPT, 0 or 1, theresults do not show the expected frequency shift. However, if you set PARAM,VMOPT, 2, the frequency shift is as expected.

8330693 V11.0 SOL 112 analysis that involves a model with a MFLUID does not output thefluid-structure pressure results requested by MPRES when parameter VMOPT = 2.

8333620

8333621V11.0

A SOL 106 model that contains CBEAM elements with scalar grid points (SPOINT) atSA and SB, and these elements are allowed to warp, fails to solve with the ILP64executable. SOL 401 models may run into a similar issue.

As workaround, use the LP64 executable.




8339546 V11.0In SOL 401, if the input deck contains a BOLTRESULTS case control command andthe model does not have any bolts, the solver issues a fatal error. The solverneeds to ignore the BOLTRESULTS case control when no bolts are present.

8341965 V11.0.1

In SOL 101, the request for writing MIN/MAX values to a punch file usingRMAXMIN, for example,

RMAXMIN(FORCE, STRESS, DISP, PRINT, PLOT, PUNCH, MAXIMUM) = YES

results in incorrect numbers (for example, 6.013470-154, and so on) written tothe .pch file.

8342137 V11.0.2

While trying to create SIMPACK flexible body input file (.fbi file) in SOL 103, thecalculation ends with the following user fatal message:

^^^ CREATING FBI FILE FOR RESIDUAL STRUCTURE*** USER FATAL MESSAGE 3111 (NXNSMPK) ERROR PROCESSINGELEMENT FACES FOR SIMPACK FBI

8347570 V11.0.1

In SOL 401, when you perform a structural analysis and use nodal temperaturedata from a .bun file that incorrectly specifies duplicate nodal temperature, thesolver generates the unclear message:

*** USER FATAL MESSAGE 4228 (GP3B)TEMPERATURE SET ... CONTAINS DUPLICATE GRID ID ( ... ).

The message refers to a temperature SID that is not part of your input deck andis internally generated by NX Nastran.

NX Nastran 12.0 prints the following more detailed message:

*** USER FATAL MESSAGE 22910 (GP7ARUNV)PROBLEM ENCOUNTERED WHILE CREATING DTEMP CARD FROM BUN/UNVFILE SPECIFIED ON UNIT %1.BUN/UNV FILE NAME = %2THE BUN FILE HAS MULTIPLE 2414 NODAL TEMPERATURE DATASETSFOR SAME TIME INSTANT.EXAMPLE OF SUCH BUN/UNV FILE IS ONE WITH A NODALTEMPERATURE DATASET AND ALSO A NODAL ABSOLUTE OR NODALTOTAL TEMPERATURE DATASET.CHECK THE BUN FILE FOR MULTIPLE 2414 NODAL TEMPERATUREDATASET AT SAME TIME INSTANT. THE BUN FILE SHOULD HAVEONLY ONE NODAL TEMPERATURE DATASET FOR ANY GIVEN TIMEINSTANT.

User information:A grid point has referenced more than one temperature valuefor same given time instant.




8347783 V11.0.1

In Simcenter Pre/Post, the Solution Monitor may idle when it prints a largenumber of output messages to the .f06 file. For example, the software prints alarge number of error or warning messages from temperature processing fromthe GP3 module. You may notice a warning message that is repeated for everynode missing temperature data.

*** USER WARNING MESSAGE 2009 (GP3B)TEMPERATURE SET ... REFERENCES UNDEFINED GRID POINT ...

In NX Nastran 12, the number of repeated warning and error messages fromtemperature processing module (GP3) is limited to 100, which is the default. Youcan use the system cell 698 to control the number of error messages. See thesystem cell 698 description in the Quick Reference Guide.

8534257 V11.0

SOL 111 rotor dynamic analysis incorrectly outputs the following fatal errormessage when an ROFRCE1 or RFORCE2 is applied to a rotating component inthe model.

^^^ USER FATAL MESSAGE 9220 (SELG) ^^^RFORCE REFERENCED ON ROTORD NOT FOUND.

Now, NX Nastran 12 also accepts RFORCE1 and RFORCE2 as loading.

8800947 V10.2

SOL 101 solve for models with solid element, bolt pre-load, and contact givesincorrect results when using a half symmetric model with constraints specified bya combination of SPC and SPC1. The full model produces correct results.

The problem is due to the constraint combination with SPCADD in models thatutilize symmetry. A model created with a single non-combination SPC constraintset that specifies the symmetry and the fixed end conditions using only SPC

bulk data entry, gives correct results.

A workaround is to use SPC instead of SPC1.

8804981 V11.0.1

SOL 108 issues fatal error messages for a model with external superelementwhen you request GPFORCE output.

*** USER FATAL MESSAGE 22006 (SPDRPVA)UNABLE TO OPEN INPUT DATA BLOCK EXT*** SYSTEM FATAL MESSAGE 3001 (MATMOD)THE INPUT DATA BLOCK NAMED CASES AT POSITION 3 DOES NOTEXIST.

8804997 V11.0.1 SOL 108 gives incorrect results for displacement, velocity, and accelerations fora model with an external superelement and multiple subcases.

8812247 V11.0.1

NX Nastran does not correctly write SORT2 data for a SOL 108 model withexternal superelements.

In NX Nastran 11, the workaround is to use the following DMAP alter:

compile sedrcvr2 nolist $ alter 'file' (3,-1) $file oesvm2=ovrwrt/ostrvm2=ovrwrt $

8821578 V11.0

In SOL 108 or SOL 111, NX Nastran terminates with the SYSTEM FATAL MESSAGE

3007 (SSG3) error when it encounters a vibro-acoustic solution that containsboth of the following:

1. A STATSUB case control command.

2. A static analysis subcase with mechanical loads as the first subcase.




8824887 P11.0 SOL 103 solve for models with superelements does not write the GPFORCE resultsfor grid point forces to the .f06 and .op2 file.

8824918 V11.0.1 SOL 103 outputs the grid point force balance results to the .f06 file, but not tothe .op2 file.

8828114 V11.0

SOL 101 model with RIGID = LAGRANGE and CBUSH elements, but no contact orglue, terminates with the fatal error message:

*** USER FATAL MESSAGE 4690 (CNTMAT)THE MATRIX/TABLE MPT IS REQUIRED IN A CONTACT/GLUE ANALYSIS

The error is because of material property IDs for internally created beamelements for Lagrange rigid are missing.

Now, NX Nastran 12:

1. Prints a warning instead of an error message.

2. Sets the elasticity modulus to 1.0E+12. To modify this value, use systemcell 687.

8844955 V10.2

SOL 101 models, where RIGID = LARANGE is set and contain RBE2 elements,produce incorrect results and the following warning message in the .f06 file:

*** USER WARNING MESSAGE 4693 (CNTMAT)AVERAGE MODULUS COULD NOT BE COMPUTED AS MATRIX/TABLE MPTCOULD NOT BE LOCATED OR DOES NOT EXIST.

The problem is fixed for models that do not require a specific MATi definition.A default stiffness is assigned that prevents the AUTOSPC process fromeliminating the unnecessary DOF.

The workaround is to add a material definition, for example, a MAT1 bulk entrywith a stiffness value, which prevents the DOF of the RBE2 from being eliminatedby AUTOSPC.

8845145 V11.0.1In SOL 101, when you set PENT option to 0.0 on the BGPARM bulk entry for modelswith surface-to-surface gluing, the software sets the PENN option to 0.0 insteadof the default value of 100.0.

8846975 V11.0.1

A vibro-acoustic analysis in SOL 111 or SOL 108 with AML produces thefollowing fatal error:

^^^ USER FATAL MESSAGE 9421 (AMLTRAP) ^^^EXTENDED ACOUSTICS FEATURE AML IS NOT SUPPORTED WHEN THEVALUE OF OUTPUT FREQUENCY EQUALS TO ZERO.

This error can be due to:

• Multiple frequency bulk entries (FREQi) that are specified in the acousticsolutions SOL108 or SOL111.

• FREQi bulk entry that is not referenced by the case control and the bulk entryhas 0.0 frequency specified.

• AMLREG that is specified.




The workaround is to use a DMAP alter to disable the AMLTRAP subdmapin SEDFREQ or SEMFREQ.

8850633 V11.0

In DMP mode, SOL 111 prevents the solution from distributing frequenciesbetween ranks in a frequency-dependent modal frequency analysis. As a result,the DMP solve runs the same frequency across the board (on all ranks) leadingto duplication of effort.

8850676 V11.0.1 A logic error in SOL 111 random restart analysis of a model with compositeelements causes some of the elements to be skipped from result reporting.

8859220 P12.0In a SOL 401 coupled thermal and structural solve, the OPRESS outputs areincorrect for fluid pressures that are applied to a surface of the structure. Thisdoes not affect the final solution for displacements, stresses, and loads.

8861401 P12.0

In SOL 401, the solver cannot calculate results for some models with pre-loadedbolt and contact.

The contact algorithm needs to be improved with better contact stabilizationdamping.

8889870 V11.0.1A vibro-accoustic analysis in SOL 108 and SOL 111 produces a fatal error whenyou define the structural glue pair in the deck before the fluid glue pair(s).

The workaround is to define the fluid glue pair before the structural glue pair.8890789 V11.0 In SOL 601, the solve fails if the case control includes a GPFORCE output request.

8891760 V10.2

In SOL 103, if you use EXTSEOUT in combination with RIGID = LAGRANGE, the solveresults in the following fatal messages:

*** USER WARNING MESSAGE 4012 (GP3D)THERE IS NO ELEMENT, GRID POINT, OR DEFAULT TEMPERATUREDATA FOR TEMPERATURE SET ..., WITH RESPECT TOELEMENT ID = ...

*** SYSTEM FATAL MESSAGE 3200 (BDYINF)LOGIC ERROR 28 ENCOUNTERED IN SUBROUTINE BDYINFUSER ACTION:REPORT THIS PROBLEM TO SIEMENS PLM SOFTWARE CUSTOMERSUPPORT

*** SYSTEM FATAL MESSAGE 3008 (BDRYINFO)INSUFFICIENT MEMORY AVAILABLE FOR SUBROUTINE BDYINF0FATAL ERROR

8891984 V10.2

SOL 101 generates the USER FATAL MESSAGE (UFM 610 (IFP1D)) if the deckcontains the statement P2G =1.25*PA90 without any gap between the = signand the number 1.25.

The workaround is to add a gap, for example P2G = 1.25*PA90.

8898094 P12.0 In SOL 103, if you request residual vector computation with RESVEC = YES, thesolver issues a fatal error message.

8900134 P12.0 The results from SOL 601 are incorrect when a FORCE1 refers to a coordinatesystem card of type CORD2R, CORD2C, or CORD2S.




8900569 V11.0

In SOL 111, models with multiple subcases having DLOAD that combine SPCD withnon-SPCD type mechanical loads issue the following fatal message:

*** USER FATAL MESSAGE 5423 (MPYAD)ATTEMPT TO MULTIPLY INCOMPATIBLE MATRICES

COLS ROWS FORM TYPE NZWD DENSTRAILER FOR SCRATCH IS 305 132 6 2 1 6 10000TRAILER FOR SCRATCH IS 301 600 133 2 3 264 9925TRAILER FOR (NONE) IS 0 1800 133 2 1 264 0TRANSPOSE FLAG IS 0

8902533 V11.0

In SOL 101, if a load is applied to an independent node of an RBE3 element andRIGID is set to LAGRAN in a model with multiple subcases, the solver producesincorrect MPC and grid point forces.

The following workarounds are available:

• Run one subcase at a time for the RIGID = LAGRAN condition.

Note

This is a computationally intensive workaround.

• For simple models, maybe you can use an RBE2 element instead of the RBE3

element.

8921661 V11.0A combined SOL 103 and SOL 111 solve that computes modal frequencyresponse with MFLUID on and VMOPT = 0 (Default), uses dry modes instead of wetmodes. Therefore, SOL 111 produces incorrect results.

8928638 P12.0

Computation of RDMODES in SOL 111, Frequency Response, FRRDRU, resultsin an incorrect fatal error message. Although correct eigenvalues are computed,the message states that there are no excitations in the model.

*** USER FATAL MESSAGE 3046 (FRRUD2)THIS FREQUENCY RESPONSE ANALYSIS HAS NO EXCITATIONSPECIFIED FOR IT. APPLIED LOADS AND ENFORCED MOTIONARE BOTH NULL. THE RESULT WILL THEREFORE BE A ZEROSOLUTION

8931569 V11.0.2

The title of the NX Nastran 11.0.2 shortcut icon on your desktop is incorrectlydisplayed as "Siemens NX Nastran 11.0.1". To update the title to include thecorrect version number, contact technical support (GTAC) for information onhow to download the fix.

8934623 V10.0

ADAMS or RecurDyn export from SOL 103 results in export of incorrect MNFmode shapes. The root cause of this error is due to the application of incorrectcylindrical and spherical nodal displacement coordinate system transformationsof the ADAMS MNF mode shapes. There is no problem if Cartesian coordinatesystems are used.

The workaround is to use only Cartesian displacement coordinate systems inyour models.

8934958 P12.0In SOL 106 and SOL 401, incorrect eigenvalues are computed for thick beamswhen different rigid body rotations are applied to the model. However, rigid bodyrotation of 360 degrees does give correct eigenvalues.




8941389 V10.0

Rotor dynamic transient response with either the synchronous option or withnonlinear bearings produces incorrect results. The solver incorrectly assumes azero acceleration state at the beginning of the restart.

In NX Nastran 12, these incorrect results are trapped by a fatal error message.

8941795 V11.0

In SOL 111, a fatal error occurs when the solve restarts from SOL 103 withparameters RSOPT and RSCON.

*** USER FATAL MESSAGE 3046 (FRDSMP)THIS FREQUENCY RESPONSE ANALYSIS HAS NO EXCITATIONSPECIFIED FOR IT.APPLIED LOADS AND ENFORCED MOTION ARE BOTH NULL.THE RESULT WILL THEREFORE BE A ZERO SOLUTION.

8945787 P12.0 In SOL 401, OPRESS results for a zero time subcase involving coupledthermal-structural solution are not output.

8945865 V11.0.2In SOL 401, OPRESS results generated from a coupled thermal-structural solutionare not saved in the .op2 file. This occurs for models where pressure is definedon convective zones with a condition sequence parameter.

8946257 P10.2

In SOL 101, if you request the output of MPC forces for models with pre-loadedbolts and use the element iterative solver, the solve terminates with a fatal errormessage.

The workaround is to use the sparse solver.

8952804 V11.0

In SOL 111, a specific PSD solution with random response shows the followingissues:

• Only the element force results are written. The accelerations ordisplacements outputs are missing.

• The last random subcase is written with the incorrect Random ID = 0 label.

• No .pch file is written for ELFORCE output request.

• RANFRF set to on or off does not produce different random results output, andFRFs are only written for the ELFORCE results.

• When you include the case control command RESVEC(DYNRSP), the solvergenerates NaNs in forced response results.

• To get a model to run on Linux, you must:

1. In the EIGRL bulk entry, specify a negative V1 value and a positive V2

value.

Example

EIGRL, 1,-.1, 2800

2. Add NASTRAN SYSTEM(263) = 15.

3. Add NASTRAN RANFRF = 1 to the input deck to receive the FRF output.




8953029 V11.0 A random response analysis in SOL 111 computes incorrect RMS von Misesresults when magnitude/phase frequency response results are used.

8961627 P12.0The Simcenter Pre/Post solution monitor idles when it monitors a specific SOL200 design optimization solution. The solution monitor gives you the impressionthat the solution still runs.

8966347 V11.0.1 SOL 601, 106 results are incorrect when model contains time-varying thermalloads that are defined with DLOAD and TLOAD1 bulk entries.



Siemens Industry Software

HeadquartersGranite Park One5800 Granite ParkwaySuite 600Plano, TX 75024USA+1 972 987 3000

AmericasGranite Park One5800 Granite ParkwaySuite 600Plano, TX 75024USA+1 314 264 8499

EuropeStephenson HouseSir William Siemens SquareFrimley, CamberleySurrey, GU16 8QD+44 (0) 1276 413200

Asia-PacificSuites 4301-4302, 43/FAIA Kowloon Tower, Landmark East100 How Ming StreetKwun Tong, KowloonHong Kong+852 2230 3308

About Siemens PLM Software

Siemens PLM Software, a business unit of the SiemensIndustry Automation Division, is a leading global providerof product lifecycle management (PLM) software andservices with 7 million licensed seats and 71,000 customersworldwide. Headquartered in Plano, Texas, SiemensPLM Software works collaboratively with companiesto deliver open solutions that help them turn moreideas into successful products. For more informationon Siemens PLM Software products and services, visitwww.siemens.com/plm.

© 2017 Siemens Product Lifecycle ManagementSoftware Inc. Siemens and the Siemens logo areregistered trademarks of Siemens AG. D-Cubed,Femap, Geolus, GO PLM, I-deas, Insight, JT, NX,Parasolid, Solid Edge, Teamcenter, Tecnomatix andVelocity Series are trademarks or registered trademarksof Siemens Product Lifecycle Management SoftwareInc. or its subsidiaries in the United States and in othercountries. All other trademarks, registered trademarksor service marks belong to their respective holders.

nx nastran 12 release guide - siemens€¦ · release guide. contents proprietary ......

Documents