hexagon logo
Register Sign in
  • State Not Answered
  • Replies 4 replies
  • Subscribers 4 subscribers
  • Views 160 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)
Parents
  • 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.
Reply
  • 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.
Children
No Data
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement