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

SYSTEM FATAL MESSAGE 3001 (READ)

MOzer
Dear All,
Any idea regarding thie error msg ?
THE INPUT DATA BLOCK IN POSITION  11 DOES NOT EXIST.
   USER INFORMATION: THIS ERROR IS CAUSED BY ONE OF THE FOLLOWING:
     1. THE DATA BLOCK IS UNSPECIFIED ON THE DMAP MODULE.
     2. THE DATA BLOCK IS SPECIFIED ON THE DMAP MODULE AND ON THE SUBDMAP STATEMENT
       BUT NOT ON THE CORRESPONDING CALL STATEMENT.
i add also *.fo6 file.
Massless mechanism is reported but solved base model (ok model) also include these structures (items) reported as MASSLESS MECHANISMS .
 
Thanks for your help
regards
 
 
Attached Files (1)
  • 0
    Without the f04 file, it is not easy to say where the problem occurred. However, if the model has massless mechanisms, the simple statement is that you need to do some troubleshooting before proceeding. A massless mechanism is usually a sign of a modeling problem.
  • 0
    The input data block in position 11 does not exist, means the DMAP module was expecting and input data but was not found at the time of it execution or was not created. Generally, these types of error are likely due to DMAP errors. You are using BAR elements. Try using NASTRAN BARMASS=1, I don't think it may resolve the DMAP FATAL but may avoid some massless mechanisms.
     
    See comment in the QRG:
     
    Allows the user to select the bar torsional mass moment of inertia.
    If set to 0, request the pre-MSC Nastran 2004 (Default = 0).
    If set to greater than 0, the torsional mass moment of inertia term
    is included in the mass matrix formulation of bar elements. For
    both values of COUPMASS, the torsional inertia is added.
    For COUPMASS = 1, the axial mass will be consistent rather than
    coupled.
     
    You may also want to contact support and send them the bdf. These error generally end up being DMAP issues which may have to be corrected in subsequent versions.
  • 0
    Looking at the f04 file, the final line in the execution summary is:
     18:30:14   34:57     306.9G       3.0    15830.1       0.0   XREAD  159    READ   BEGN * 
    This indicates that it is trying to run the READ module (Lanczos) at line 159 in subDMAP XREAD. Looking at the DMAP listing (obtained by adding COMPILE XREAD, LIST just before the CEND), line 159 is:
        159        READ    KXX2,MXX2,MR,DXR,DYNAMICS,USET,CASES,VSPC1,SILS,,                  
                             INVEC,LLL,EQEXINS,/                                                
                             LAMA,PHIX,MIX,OEIGS,ROOTS,/                                        
                             READAPP/S,N,NEIGV/NSKIP/METHF/CMSET/SID/                           
                             METHTYPE/F1/UPF2/NE///////MAXRATIO $                               
    your error says that the input datablock in position 11 does not exist - that is INVEC (or if you look at the DMAP module dictionary, EQMAP - Table of degree-of-freedom global-to-local maps for domain decomposition. Required only for geometric domain decomp.
    At this point, I would say the best thing is to directly contact MSC support and send them the input file, so they can try to determine what the problem is.
    In the meantime, you might try Sanjay's suggestion or mine (troubleshoot the model).
    As I stated, massless mechanisms are an indication of a modeling problem - my personal opinion is that if they exist, there is a potential major problem in the model and you should try to determine where they are and correct the modeling errors. The best way to do this is to try running statics first and troubleshooting those runs.
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement