<!DOCTYPE html
  PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!--
Copyright (c) 2006 UGS Corp.

All Rights Reserved.

This software and related documentation are proprietary to UGS Corp.
-->
<html>
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <title>ADAMSMNF</title>
      <script language="javaScript">
        abridged="false";
        displayConditions=new Array();
      </script>
      <link type="text/css" href="../css/main_styles.css" rel="stylesheet">
   </head>
   <body class="bodydocs" onload="top.pageLoader()" bgcolor="#FFFFFF">
      <hr noshade="true">
      <div class="title_refTopic" id="xps10_pagetitle">ADAMSMNF </div>
      <hr noshade="true">
      <h4 class="refClassification">Generates ADAMS Interface Modal Neutral File </h4>
      <p class="para_refTopic">Generates ADAMS Interface Modal Neutral File (MNF) during SOL 103. </p>
      <div class="title_refCategory">Format: </div>
      <div class="refCategoryContent">
         <p align="center"><img align="bottom" src="graphics/casecontrol4a-ufig04.gif"></p>
      </div>
      <div class="title_refCategory">Examples: </div>
      <div class="refCategoryContent"><pre class="indent">ADAMSMNF FLEXBODY=YES</pre></div>
      <div class="title_refCategory">Describers:</div>
      <div class="refCategoryContent">
         <table cellpadding="10" cellspacing="" width="100%" align="center">
            <colgroup span="1">
               <col span="1" width="21.48*">
               <col span="1" width="78.52*">
            </colgroup>
            <thead>
               <tr>
                  <th align="left" colspan="1" rowspan="1">
                     <p class="para_th" align="center"><b class="uiTerm">Describer </b></p>
                  </th>
                  <th align="left" colspan="1" rowspan="1">
                     <p class="para_th"><b class="uiTerm">Meaning </b></p>
                  </th>
               </tr>
            </thead>
            <tbody>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">FLEXBODY </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Requests the generation of MNF. </p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">NO </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Standard NX Nastran solution without MNF creation (default). </p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">YES </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">MNF generation requested. </p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">FLEXONLY </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Determines if standard DMAP solution runs or not after MNF creation is complete. </p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">YES</p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Only MNF creation occurs (default). </p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">NO</p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">MNF file creation occurs along with standard DMAP solution. </p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">OUTGSTRS </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Determines if grid point stress is written to MNF. </p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">NO </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Do not write grid point stress to MNF (default). </p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" height="38" rowspan="1" valign="top">
                     <p class="para_td">YES </p>
                  </td>
                  <td align="left" colspan="1" height="38" rowspan="1" valign="top">
                     <p class="para_td">Write grid point stress to MNF. </p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">OUTGSTRN </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Determines if grid point strain is written to MNF. </p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">NO </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Do not write grid point strain to MNF (default). </p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">YES </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Write grid point strain to MNF. </p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">MINVAR </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Determines how mass invariants are computed. </p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">PARTIAL </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Mass invariants 5 and 9 are not computed. </p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">CONSTANT </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Mass invariants 1,2,6 and 7 are computed. </p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">FULL </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">All nine mass invariants are computed. </p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">NONE </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">No mass invariants are computed. </p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">PSETID </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Selects a set of elements defined in the OUTPUT(PLOT) section (including PLOTEL) or on a sketch file whose connectivity is exported to face geometry to be used in ADAMS. (See Remark 15) </p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">NONE </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">All grids, geometry and associated modal data is written to MNF (default). </p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">setid </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">The connectivity of a specific element set is used to export face geometry. </p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">ALL </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">The connectivity of all element sets are used to export face geometry. </p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">sktunit </p>
                  </td>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">The connectivity of element faces defined on a sketch file is used to export face geometry. Note that the value must be a negative number to distinguish it from a setid value.</p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">ADMOUT</p>
                  </td>
                  <td colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Requests that the FLEXBODY run output an NX Nastran OP2 file for use in post processing of ADAMS/Flex results. </p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">NO </p>
                  </td>
                  <td colspan="1" rowspan="1" valign="top">
                     <p class="para_td">OP2 file will not be generated (default). </p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">YES </p>
                  </td>
                  <td colspan="1" rowspan="1" valign="top">
                     <p class="para_td">OP2 file will be generated.</p>
                  </td>
               </tr>
               <tr>
                  <td align="left" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">CHECK</p>
                  </td>
                  <td colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Requests debug output be written to the f06 file when ADMOUT=YES (See Remark 19).</p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">NO </p>
                  </td>
                  <td colspan="1" rowspan="1" valign="top">
                     <p class="para_td">No debug output will be written (default).</p>
                  </td>
               </tr>
               <tr>
                  <td align="right" colspan="1" rowspan="1" valign="top">
                     <p class="para_td">YES </p>
                  </td>
                  <td colspan="1" rowspan="1" valign="top">
                     <p class="para_td">Debug output will be written.</p>
                  </td>
               </tr>
            </tbody>
         </table><br></div>
      <div class="title_refCategory">Remarks: </div>
      <div class="refCategoryContent">
         <ol type="1" start="1">
            <li>
               <p class="para_item">The creation of the Adams MNF, which is applicable in a non-restart SOL 103 analysis only, is initiated by ADAMSMNF FLEXBODY=YES (other describers are optional) along with the inclusion of the bulk data entry DTI,UNITS. </p>
            </li>
            <li>
               <p class="para_item">The Data Table Input Bulk Data entry DTI,UNITS, which is required for an ADAMSMNF FLEXBODY=YES run, is used to specify the system of units for the data stored in the MNF (unlike NX Nastran, ADAMS is not a unitless code). Once identified, the units will apply to all superelements in the model. The complete format is: </p><pre class="indent">DTI     UNITS   1       MASS    FORCE   LENGTH  TIME</pre><p class="para_item">All entries are required. Acceptable character strings are listed below. </p>
               <ul class="unmarkedList">
                  <li>
                     <p class="para_item">Mass:</p>
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">KG - kilogram </p>
                           <p class="para_item">LBM &ndash; pound-mass (0.45359237 kg)</p>
                           <p class="para_item">SLUG &ndash; slug (14.5939029372 kg)</p>
                           <p class="para_item">GRAM &ndash; gram (1E-3 kg)</p>
                           <p class="para_item">OZM &ndash; ounce-mass (0.02834952 kg)</p>
                           <p class="para_item">KLBM &ndash; kilo pound-mass (1000 lbm) (453.59237 kg)</p>
                           <p class="para_item">MGG &ndash; megagram (1E3 kg)</p>
                           <p class="para_item">MG &ndash; milligram (1E-6 kg)</p>
                           <p class="para_item">MCG &ndash; microgram (1E-9 kg)</p>
                           <p class="para_item">NG &ndash; nanogram (1E-12 kg)</p>
                           <p class="para_item">UTON &ndash; U.S. ton (907.18474 kg)</p>
                           <p class="para_item">SLI &ndash; slinch (175.1271524 kg)</p>
                        </li>
                     </ul>
                     <p class="para_item">Force: </p>
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">N &ndash; Newton </p>
                           <p class="para_item">LBF &ndash; pound-force (4.44822161526 N)</p>
                           <p class="para_item">KGF &ndash; kilograms-force (9.80665 N)</p>
                           <p class="para_item">OZF &ndash; ounce-force (0.2780139 N)</p>
                           <p class="para_item">DYNE &ndash; dyne (1E-5 N)</p>
                           <p class="para_item">KN &ndash; kilonewton (1E3 N)</p>
                           <p class="para_item">KLBF &ndash; kilo pound-force (1000 lbf) (4448.22161526 N)</p>
                           <p class="para_item">MN &ndash; millinewton (1E-3 N)</p>
                           <p class="para_item">MCN &ndash; micronewton (1E-6 N)</p>
                           <p class="para_item">NN &ndash; nanonewton (1E-9 N)</p>
                        </li>
                     </ul>
                     <p class="para_item">Length: </p>
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">M &ndash; meter </p>
                           <p class="para_item">KM &ndash; kilometer (1E3 m)</p>
                           <p class="para_item">CM &ndash; centimeter (1E-2 m)</p>
                           <p class="para_item">MM &ndash; millimeter (1E-3 m)</p>
                           <p class="para_item">MI &ndash; mile (1609.344 m)</p>
                           <p class="para_item">FT &ndash; foot (0.3048 m)</p>
                           <p class="para_item">IN &ndash; inch (25.4E-3 m)</p>
                           <p class="para_item">MCM &ndash; micrometer (1E-6 m)</p>
                           <p class="para_item">NM &ndash; nanometer (1E-9 m)</p>
                           <p class="para_item">A &ndash; Angstrom (1E-10 m)</p>
                           <p class="para_item">YD &ndash; yard (0.9144 m)</p>
                           <p class="para_item">ML &ndash; mil (25.4E-6 m)</p>
                           <p class="para_item">MCI &ndash; microinch (25.4E-9 m)</p>
                        </li>
                     </ul>
                     <p class="para_item">Time: </p>
                     <ul class="unmarkedList">
                        <li>
                           <p class="para_item">S &ndash; second </p>
                           <p class="para_item">H &ndash; hour (3600.0 sec)</p>
                           <p class="para_item">MIN-minute (60.0 sec)</p>
                           <p class="para_item">MS &ndash; millisecond (1E-3 sec)</p>
                           <p class="para_item">MCS &ndash; microsecond (1E-6 sec)</p>
                           <p class="para_item">NS &ndash; nanosecond (1E-9 sec)</p>
                           <p class="para_item">D &ndash; day (86.4E3 sec)</p>
                        </li>
                     </ul>
                  </li>
               </ul>
            </li>
            <li>
               <p class="para_item">Since DTI,UNITS determines all units for the MNF, the units defined in WTMASS, which are important for units consistency in NX Nastran, are ignored in the output to the MNF. For example, if the model mass is kilograms, force in Newtons, length in meters, and time in seconds, then WTMASS would equal 1 ensuring that NX Nastran works with the consistent set of kg, N, and m. The units written to the MNF would be: &ldquo;DTI,UNITS,1,KG,N,M,S&rdquo;. </p>
            </li>
            <li>
               <p class="para_item">You can create flexible body attachment points by defining the component as a superelement or part superelement, in which case the physical external (a-set) grids become the attachment points; or for a residual-only type model, you can use standard NX Nastran ASET Bulk Data entries to define the attachment points. </p>
            </li>
            <li>
               <p class="para_item">The nine mass variants are: </p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-equ01.gif" border="0"></p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-equ02.gif" border="0"></p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-equ03.gif" border="0"></p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-equ04.gif" border="0"></p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-equ05.gif" border="0"></p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-equ06.gif" border="0"></p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-equ07.gif" border="0"></p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-equ08.gif" border="0"></p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-equ09.gif" border="0"></p>
               <p class="para_item"><em>s<sub class="subscript">p</sub></em> = [<em>xyz</em>]<em><sup class="superscript">T</sup></em> are the coordinates of grid point p in the basic coordinate system. 
               </p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-equ10.gif" border="0"></p>
               <p class="para_item">&phi;<em><sub class="subscript">p</sub></em>=partitioned orthogonal modal matrix that corresponds to the translational degrees of freedom of grid <em>p</em>. 
               </p>
               <p class="para_item"><em>I<sub class="subscript">p</sub></em>=inertia tensor <em>p</em>. 
               </p>
               <p class="para_item">&phi;<em><sub class="subscript">p</sub></em><sup class="superscript">*</sup>=partitioned orthogonal modal matrix that corresponds to the rotational degrees of freedom of grid <em>p</em>. 
               </p>
               <p class="para_item"><img align="bottom" src="graphics/casecontrol4a-ufig05.gif" border="0">=skew-symmetric matrix formed for each grid translational degree of freedom for each mode. 
               </p>
               <p class="para_item">M=number of modes. </p>
               <p class="para_item">N=number of grids. </p>
            </li>
            <li>
               <p class="para_item">To accurately capture the mode shapes when supplying SPOINT/QSET combinations, the number of SPOINTS (ns) should be at least ns=n+(6+p), assuming that residual flexibility is on. In the above equation for ns, the number of modes (n) is specified on the EIGR or EIGRL Bulk Data entries; the number of load cases is p. In general, you can&rsquo;t have too many SPOINTs, as excess ones will simply be truncated with no performance penalty. </p>
            </li>
            <li>
               <p class="para_item">For FLEXBODY=YES runs, residual vectors for the component should always be calculated as they result in a more accurate representation of the component shapes at little additional cost. </p>
            </li>
            <li>
               <p class="para_item">OMIT or OMIT1 Bulk Data entries are not supported. </p>
            </li>
            <li>
               <p class="para_item">Lumped mass formulation (default) is required. Either leave PARAM,COUPMASS out of the input file or supply PARAM,COUPMASS,-1 (default) to ensure lumped mass. </p>
            </li>
            <li>
               <p class="para_item">P-elements are not allowed because they are always use a coupled mass formulation. </p>
            </li>
            <li>
               <p class="para_item">PARAM,WTMASS,value with a value other than 1.0 may be used with an NX Nastran run generating an MNF. It must have consistent units with regard to the DTI,UNITS Bulk Data entry. Before generating the MNF, NX Nastran will appropriately scale the WTMASS from the physical mass matrix and mode shapes. </p>
            </li>
            <li>
               <p class="para_item">There is a distinction between how an ADAMSMNF FLEXBODY=YES run handles element-specific loads (such as a PLOAD4 entry) versus those that are grid-specific (such as a FORCE entry), especially when superelements are used. The superelement sees the total element-specific applied load. For grid-specific loads, the loads attached to an external grid will move downstream with the grid. That is to say, it is part of the boundary and not part of the superelement. This distinction applies to a superelement run and not to a residual-only or parts superelement run. </p>
            </li>
            <li>
               <p class="para_item">The loads specified in NX Nastran generally fall into two categories: non-follower or fixed direction loads (non-circulatory) and follower loads (circulatory). The follower loads are nonconservative in nature. Examples of fixed direction loads are the FORCE entry or a PLOAD4 entry when its direction is specified via direction cosines. Examples of follower loads are the FORCE1 entry or the PLOAD4 entry when used to apply a normal pressure. By default in NX Nastran, the follower loads are always active in SOL 103 and will result in follower stiffness being added to the differential stiffness and elastic stiffness of the structure. In a run with ADAMSMNF FLEXBODY=YES and superelements, if the follower force is associated with a grid description (such as a FORCE1) and the grid is external to the superelement, the follower load will move downstream with the grid. Thus, the downstream follower contribution to the component&rsquo;s stiffness will be lost, which could yield poor results. This caution only applies to a superelement run and not to a residual-only or a part superelement run. </p>
            </li>
            <li>
               <p class="para_item">OUTGSTRS and OUTGSTRN entries require the use of standard NX Nastran STRESS= or STRAIN= used in conjunction with GPSTRESS= or GPSTRAIN= commands to produce grid point stress or strain. GPSTRESS(PLOT)= or GPSTRAIN(PLOT)= will suppress grid stress or strain print to the NX Nastran .f06 file. </p>
            </li>
            <li>
               <p class="para_item">To reduce the FE mesh detail for dynamic simulations, PSETID (on the ADAMSMNF Case Control command) defined with a SET entry (i.e. setid) is used to define a set of PLOTELs or other elements used to select grids to display the components in ADAMS. This option can significantly reduce the size of the MNF without compromising accuracy in the ADAMS simulation providing that the mass invariant computation is requested. With superelement analysis, for any of these elements that lie entirely on the superelement boundary (all of the elements&rsquo; grids attached only to a-set or exterior grids), a SEELT Bulk Data entry must be specified to keep that display element with the superelement component. This can also be accomplished using PARAM, AUTOSEEL,YES. The SEELT entry is not required with parts superelements, as boundary elements stay with their component. </p>
               <p class="para_item">If the SET entry points to an existing set from the OUTPUT(PLOT) section, this single set is used explicitly to define elements used to select grids to display the component in ADAMS. If PSETID does not find the set ID in OUTPUT(PLOT), it will search sets in the case control for a matching set ID. This matching set ID list then represents a list of OUTPUT(PLOT) defined elements&rsquo; sets, the union of which will be used to define a set of PLOTELs or other elements used to select grids to display the component in ADAMS. If the user wishes to select all of the sets in the OUTPUT(PLOT) section, then use PSETID=ALL. </p>
               <p class="para_item">The following element types are not supported for writing to an MNF, nor are they supported as a &lsquo;type&rsquo; entry in a set definition in OUTPUT(PLOT): CAABSF, CAEROi, CDUMi, CHACAB, CHACBR, CHBDYx, CDAMP3, CDAMP4, CELAS3, CELAS4, CFLUIDi, CMASS3, CMASS4, CRAC2D, CRAC3D, CTRMEM, CTWIST, CWEDGE, CWELD, and GENEL.</p>
               <p class="para_item">PSETID can also point to a sketch file using PSETID=-sktunit, where sktunit references an ASSIGN statement of the form </p><pre class="indent">ASSIGN SKT=&lsquo;sketch_file.dat&rsquo;,UNIT=sktunit.</pre><p class="para_item">The grids defined for the elements&rsquo; faces in the sketch file, along with <em>all</em> external (i.e. boundary) grids for the superelements, will be the only grids (and their associated data) written to the MNF. 
               </p>
               <p class="para_item">The format of the sketch file, which describes the mesh as a collection of faces, must be as follows: </p><pre class="indent">face_count
face_1_node_count face_1_nodeid_1 face_1_nodeid_2 ...
face_2_node_count face_2_nodeid_1 face_2_nodeid_2 ...
&lt;etc&gt;</pre><p class="para_item">Faces must have a node count of at least two. For example, a mesh comprised of a single brick element might be described as follows: </p><pre class="indent">
6
4 1000 1001 1002 1003
4 1007 1006 1005 1004
4 1000 1004 1005 1001
4 1001 1005 1006 1002
4 1002 1006 1007 1003
4 1003 1007 1004 1000</pre><p class="para_item">Alternatively, the mesh might be described as a stick figure using a collection of lines (two node faces), as shown below: </p><pre class="indent">
8
2 101 102
2 102 103
2 103 104
2 104 105
2 105 106
2 106 107
2 107 108
2 108 109</pre></li>
            <li>
               <p class="para_item">Typical NX Nastran data entry requirements are described below. </p>
               <p class="para_item">Typical Parameters: </p>
               <ul>
                  <li>
                     <p class="para_item">PARAM,RESVEC,character_value &ndash; controls calculation of residual flexibility (including inertia relief) modes. In SOL 103, residual flexibility is on by default for only component modes (o-set). </p>
                  </li>
                  <li>
                     <p class="para_item">PARAM,GRDPNT, value - mass invariants <sup class="superscript">1</sup><em>I</em>, <sup class="superscript">2</sup><em>I</em>, and <sup class="superscript">7</sup><em>I</em> will be computed using results of NX Nastran grid point weight generator execution in the basic coordinate system. 
                     </p>
                  </li>
               </ul>
               <p class="para_item">Typical Case Control: </p>
               <ul>
                  <li>
                     <p class="para_item">ADAMSMNF FLEXBODY=YES is required for MNF generation. </p>
                  </li>
                  <li>
                     <p class="para_item">METHOD=n is required before or in the first subcase for modal solutions. </p>
                  </li>
                  <li>
                     <p class="para_item">SUPORT1=seid is necessary to select a static support set for a residual only linear preload run. </p>
                  </li>
                  <li>
                     <p class="para_item">SUPER=n,SEALL=n is useful with multiple superelement models to select an individual superelement as a flexible body. Cannot be used with a linear STATSUB(PRELOAD) run. </p>
                  </li>
                  <li>
                     <p class="para_item">OUTPUT(PLOT) is necessary to define elements used to select grids to display the component in ADAMS when PSETID=ALL or setid. </p>
                     <p class="para_item">SET n=list of elements (including PLOTELs) is used to select grids to display the component. </p>
                  </li>
                  <li>
                     <p class="para_item">OUTPUT(POST) is necessary to define volume and surface for grid stress or strain shapes. </p>
                     <p class="para_item">SET n=list is a list of elements for surface definition for grid stress or strain shapes. </p>
                     <p class="para_item">Stress and strain data in the MNF is limited to the six components (i.e. 3 normal and 3 shear) for a grid point for a given mode. </p>
                     <p class="para_item">SURFACE n SET n NORMAL z3 is used to define a surface for writing stress and strain data. Only one FIBER selection is allowed for each SURFACE, thus the use of the FIBRE ALL keyword on the SURFACE case control command will write stresses to the MNF at the Z1 fiber location only. </p>
                     <p class="para_item">Since the FIBRE keyword only applies to stresses, strain data will always be written to the MNF at the MID location. </p>
                     <p class="para_item">Stress and strain data at grid points can only be written to the MNF for surface and volume type elements (e.g. CQUAD and CHEXA). </p>
                     <p class="para_item">VOLUME n SET n is a volume definition. </p>
                     <p class="para_item">The default SYSTEM BASIC is required with SURFACE or VOLUME. </p>
                  </li>
                  <li>
                     <p class="para_item">STRESS(PLOT) is necessary for stress shapes. </p>
                  </li>
                  <li>
                     <p class="para_item">STRAIN(PLOT) is necessary for strain shapes. </p>
                  </li>
                  <li>
                     <p class="para_item">GPSTRESS(PLOT) is necessary for grid point stress shapes to be included in the MNF. </p>
                  </li>
                  <li>
                     <p class="para_item">GPSTRAIN(PLOT) is necessary for grid point strain shapes to be included in the MNF. </p>
                     <p class="para_item">Typical Bulk Data: </p>
                  </li>
                  <li>
                     <p class="para_item">DTI,UNITS,1,MASS,FORCE,LENGTH,TIME is required for MNF generation. For input files containing superelements, this command must reside in the main bulk data section. </p>
                  </li>
                  <li>
                     <p class="para_item">SPOINT,id_list defines and displays modal amplitude.SESET,SEID,grid_list defines a superelement (see GRID and BEGIN BULK SUPER=). The exterior grids will represent the attachment points along with the q-set. </p>
                  </li>
                  <li>
                     <p class="para_item">SEELT,SEID,element_list reassigns superelement boundary elements to an upstream superelement. </p>
                  </li>
                  <li>
                     <p class="para_item">RELEASE,SEID,C,Gi is an optional entry that removes DOFs from an attachment grid for which no constraint mode is desired. For example, this allows the removal of rotational degrees of freedom from an analysis where only translational degrees of freedom are required. </p>
                  </li>
                  <li>
                     <p class="para_item">SEQSET,SEID,spoint_list defines modal amplitudes of a superelement (see SEQSET1). </p>
                  </li>
                  <li>
                     <p class="para_item">SENQSET,SEID,N defines modal amplitudes of a part superelement. It must reside in the main Bulk Data Section. </p>
                  </li>
                  <li>
                     <p class="para_item">ASET,IDi,Ci defines attachment points for a residual-only run (see ASET1). </p>
                  </li>
                  <li>
                     <p class="para_item">QSET1,C,IDi defines modal amplitudes for the residual structure or modal amplitudes for a part superelement (see QSET). </p>
                  </li>
                  <li>
                     <p class="para_item">SUPORT1,SID,IDi,Ci defines the static support for a preload condition with a residual-only run. This entry is case control selectable. Do not use SUPORT. </p>
                  </li>
                  <li>
                     <p class="para_item">PLOTEL,EID,Gi can be used, along with existing model elements, to define elements used to select grids to display the components in ADAMS. </p>
                  </li>
                  <li>
                     <p class="para_item">EIGR,SID,METHOD,&hellip; obtains real eigenvalue extraction (see EIGRL).</p>
                  </li>
               </ul>
            </li>
            <li>
               <p class="para_item">ADAMSMNF and RECURDYNRFI case control entries cannot be used in the same analysis run. In other words, an ADAMS MNF file or a RecurDyn RFI file can be generated during a particular NX Nastran execution, but not both files at the same time. Attempting to generate both files in the same analysis will cause an error to be issued and the execution to be terminated. </p>
            </li>
            <li>
               <p class="para_item">The ADMOUT=YES option is used when you would like results recovery (using the ADMRECVR case control entry) from an ADAMS/Flex analysis. This option requires the following assignment command:</p>
               <p class="para_item">ASSIGN OUTPUT2='name.out' STATUS=UNKNOWN UNIT=20 FORM=UNFORM</p>
               <p class="para_item">inserted into the file management section of the NX Nastran input file. It will cause an OP2 file with a .out extension to be generated, which then can be used as input into an NX Nastran SOL 103 run using the ADMRECVR case control capability to perform results recovery from an ADAMS/Flex analysis. FLEXBODY=YES is required with its use. </p>
               <p class="para_item">The data blocks output are: </p>
               <p class="para_item">MGGEW - physical mass external sort with weight mass removed <br>MAAEW - modal mass <br>KAAE - modal stiffness <br>CMODEXT - component modes.
               </p>
               <p class="para_item">This capability is limited to one superelement per NX Nastran model. Residual-only analyses are <em>not</em> supported.
               </p>
            </li>
            <li>
               <p class="para_item">Setting CHECK=YES (which is only available when ADMOUT=YES) is <em>not</em> recommended for models of realistic size due to the amount of data that will be written to the f06.
               </p>
            </li>
            <li>
               <p class="para_item">The ADAMSMNF data routines use the environment variable TMPDIR for temporary storage during the processing of mode shape data. As a result, TMPDIR must be defined when using ADAMSMNF. TMPDIR should equate to a directory string for temporary disk storage, preferably one with a large amount of free space.</p>
            </li>
         </ol>
      </div>
   </body>
</html>