hexagon logo
Register Sign in
  • State Not Answered
  • Replies 6 replies
  • Subscribers 4 subscribers
  • Views 82 views
  • Users 0 members are here
Options
Related

SFAM 9160

thomas.roy
Running SOL111 for Structural output in NAS2019.1 with ACMS
leads to job abort with ^   
 *** SYSTEM FATAL MESSAGE 9160 (SUBDMAP MDACMS)
   PROBLEM ENCOUNTERED IN CALCULATING DOMAINSOLVER ACMS DOMAIN MODES.
   USER ACTION: IF LARGE MASS IS BEING USED FOR ENFORCED MOTION THEN REPLACE LARGE MASS METHOD WITH DIRECT METHOD
         USING THE SPCD BULK DATA ENTRY.
   USER INFORMATION: IF THE LARGE MASS METHOD IS NOT BEING USED THEN MASSLESS MECHANISMS MAY EXIST.
            PARAM,MECHFIX,YES MAY BE USED TO IDENTIFY MASSLESS MECHANISMS.
1                                     SEPTEMBER 25, 2020 MSC Nastran 12/18/18  PAGE 2780
 
What other can be done, when the presesnt of massles mechanism where checked ?
Parents
  • 0
    1. The CGAP element is intended for the nonlinear solution sequences 106, 129, 153, 159, and 400.
    However, it will produce a linear stiffness matrix for the other solutions, but remains linear with the
    initial stiffness. The stiffness used depends on the value for the initial gap opening (U0 field in the
    PGAP entry).
     
    So i think if you want to make sure this works well in SOL 111 and also with ACMS, make sure the U0 field in PGAP as significant values as SOL 111 being linear solution it will take only the initial stiffness..
Reply
  • 0
    1. The CGAP element is intended for the nonlinear solution sequences 106, 129, 153, 159, and 400.
    However, it will produce a linear stiffness matrix for the other solutions, but remains linear with the
    initial stiffness. The stiffness used depends on the value for the initial gap opening (U0 field in the
    PGAP entry).
     
    So i think if you want to make sure this works well in SOL 111 and also with ACMS, make sure the U0 field in PGAP as significant values as SOL 111 being linear solution it will take only the initial stiffness..
Children
No Data
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement