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

SYSTEM WARNING MESSAGE 6065 (DBC); Tech Articles ID KB8019399 Reference Question and MSC's answer below in "Details" My follow-up question: What is the recommended avoidance if Nastran DBCFACT = 4 is already being used?

dmcsorle
Tech Articles ID   KB8019399
Status:   Published
Published date:   08/13/2010
Updated:   07/12/2014
Reported In:   MSC Nastran
 
Abstract (Question)
How one can avoid this error when running Sol 111?
0                                                                                                           SUBCASE 1             
 *** SYSTEM WARNING MESSAGE 6065 (DBC)
 *** DBCMSG ERROR MESSAGE  43 FROM SUBROUTINE GRIDBK 
    31 BIT ACCESS KEY WILL BE EXCEEDED, GRID/ELEMENT INDEX   235838 QUALIFIER FACTOR    10000.
    USER ACTION: SUPPLY PARAM,DBCDIAG,4 TO DETERMINE DBC TRANSLATIONAL FAILURE POINT.
    THEN CONTACT MSC.NASTRAN REPRESENTATIVE FOR POSSIBLE AVOIDANCE.
 
Description (Answer)
This is common error when one has huge model with lots of output frequencies. Avoidance is to use new xdb format (see PS***) that won't have this problem. In order to create xdb with new style, one needs to use following Nastran System Cell, as the very first line of the bdf file/input deck.
Nastran DBCFACT = 4
  • 0
    Can you please supply some additional information... what version of Nastran are you running?  What specific error messages are you getting? 
     
    The easy answer is to reduce the data requests using SET's or to reduce the number of forcing frequencies.   After getting more information, there might be additional options to suggest.​
  • 0
    Hi Don, Thanks for the quick reply. This is a large model running in MSC Nastran V2018.2. I am running a SOL 111 restart requesting a few  grid accelerations. The full message is pasted below (this is from a run where I included the Param,​DBCDIAG,4). I am getting this error when I request Acceleration output, I have output some CBUSH element forces from the same model and I do not get this error.
     
    Here is the error from the f06:
     MSC.XL      DATA BASE CONVERSION STARTED
      PARAMETER PATH QUALIFIERS RECOVERY
      SUPERELEMENT LIST RECOVERY
      AERO CONTROL LIST RECOVERY
            BEGIN COORDINATE SYSTEM DATA RECOVERY
      POST-PROCESSING DATA RECOVERY INITIATED
            BEGIN CASE CONTROL RECOVERY
            ATTEMPT LAMA TABLE RECOVERY
            ATTEMPT OUTPUT LIST RECOVERY
         OUTPUT RECOVERY FOR SUPERELEMENT        0
            BEGIN P-ELEMENT ERROR RECOVERY
            BEGIN GRID POINT OUTPUT DATA RECOVERY
     *** SYSTEM WARNING MESSAGE 6065 (DBC)
     *** DBCMSG ERROR MESSAGE  43 FROM SUBROUTINE GRIDBK 
        31 BIT ACCESS KEY WILL BE EXCEEDED, GRID/ELEMENT INDEX   819742 QUALIFIER FACTOR    10000.
        USER ACTION: SUPPLY PARAM,DBCDIAG,4 TO DETERMINE DBC TRANSLATIONAL FAILURE POINT.
        THEN CONTACT MSC.NASTRAN REPRESENTATIVE FOR POSSIBLE AVOIDANCE.
            BEGIN ELEMENT OUTPUT DATA RECOVERY
            BEGIN GRID POINT STRESS DATA RECOVERY
            BEGIN GRID POINT FORCE DATA RECOVERY
            BEGIN ELEMENT STRAIN ENERGY DENSITY DATA RECOVERY
            BEGIN GRID POINT STRESS DISCONTINUITY DATA RECOVERY
            BEGIN ELEMENT STRESS DISCONTINUITY DATA RECOVERY
            BEGIN MAX/MIN DATA RECOVERY
     MSC.XL      DATA BASE CONVERSION FINISHED
  • 0
    Can you cut and paste the top of the input file, all the way to the Begin Bulk section?​  Usually, with NASTRAN DBCFACT=4 used, this error doesn't occur.  For RESTART runs, there might be some additional considerations.
  • 0
    Don,

    Please see attached file. I have both the SOL 103 and restart SOL 111 top of decks

    Thanks
    Dan McSorley
    Harris Corp
    Rochester, NY
    Phone: 585-269-7397
    Email: dmcsorle@harris.com
  • 0
    We worked this offline, and it comes down to the RESTART run also needing the NASTRAN DBCFACT=4 at the top of the input file, in addition to the coldstart run having it.
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement