Next: Example Model Up: Error Messages Previous: Error Message Logging
Next: Example Model
Up: Error Messages
Previous: Error Message Logging
The following errors/warnings arise from incorrectly defined FEMGEN data. The interface will attempt to continue processing the model in order to detect as many such errors as possible.
ERROR: CANNOT GET LOADED FACE FOR LOAD Load_name
ERROR: INCOMPATIBLE LOAD/PART TYPE FOR LOAD Load_name
ERROR: INCORRECT ELEMENT VARIANT ON PART Part_name
ERROR: INVALID D.O.F FOR MPC Constraint_name
ERROR: INVALID D.O.F. FOR LOAD Load_name
ERROR: INVALID MATERIAL TYPE FOR MATERIAL Material_name
ERROR: INVALID POINT DEFINITION FOR LOAD Load_name
ERROR: INVALID PROPERTY FOR PART Part_name
ERROR: LOAD TYPE NOT SUPPORTED FOR LOAD Load_name
ERROR: MISSING MATERIAL FOR PART Part_name
ERROR: MISSING PROPERTY FOR PART Part_name
ERROR: NO ELEMENTS ON PART FOR LOAD Load_name
ERROR: NO NODE AT FIRST AXIS POINT FOR LOAD Load_name
ERROR: NO NODES ON PART FOR CONSTRAINT Constraint_name
ERROR: NO NODES ON PART FOR LOAD Load_name
ERROR: UNEQUAL NODES ON PARTS FOR CONSTRAINT Constraint_name
The interface (with the exception of GRID and RINGAX coordinates) attempts to pack all real number values into 8 character fields. Where the interface cannot do this to a reasonable precision it will issue the following errors. It is then up to the user to modify real number data items either in FEMGEN or in the NASTRAN input file.
ERROR: CANNOT OUTPUT TO DESIRED PRECISION IN CFNAST
ERROR: CANNOT OUTPUT TO DESIRED PRECISION IN DINAST
ERROR: CANNOT OUTPUT TO DESIRED PRECISION IN ETNAST
ERROR: CANNOT OUTPUT TO DESIRED PRECISION IN FONAST
ERROR: CANNOT OUTPUT TO DESIRED PRECISION IN GRNAST
ERROR: CANNOT OUTPUT TO DESIRED PRECISION IN HYNAST
ERROR: CANNOT OUTPUT TO DESIRED PRECISION IN LANAST
ERROR: CANNOT OUTPUT TO DESIRED PRECISION IN MANAST
ERROR: CANNOT OUTPUT TO DESIRED PRECISION IN PPNAST
ERROR: CANNOT OUTPUT TO DESIRED PRECISION IN PRNAST
ERROR: CANNOT OUTPUT TO DESIRED PRECISION IN TENAST
The following errors relate to the interface's use of files. They are often an indication that mid-way through the translation process a file has either been closed, deleted, or locked by some external source or via a hardware fault. For the external material and results files an incorrectly defined resource can cause the interface to search for files in the wrong area. These errors will cause the interface to terminate immediately.
ERROR: FORTRAN WRITE ERROR ON INPUT FILE CHANNEL Integer
ERROR: UNABLE TO OPEN SOLUTION SEQUENCE FILE Filename
ERROR: UNABLE TO READ SOLUTION SEQUENCE FILE Filename
ERROR: UNABLE TO OPEN EXTERNAL MATERIAL FILE Filename
ERROR: UNABLE TO READ EXTERNAL MATERIAL FILE Filename
The following errors can occur with very large models (40,000+ Nodes/Elements). Under such circumstances please consult your local FEMGV distributor in order to increase the interface limits. The interface will terminate immediately.
ERROR: NUMBER OF LOADCASES EXCEEDS LIMIT OF Integer
ERROR: LOADCASE NUMBER EXCEEDS LIMIT OF Integer
ERROR: GROUP ARRAY OVERFLOW IN ETNAST, CURRENT SIZE Integer
ERROR: WORK ARRAY OVERFLOW IN DINAST, CURRENT SIZE Integer
ERROR: WORK ARRAY OVERFLOW IN FONAST, CURRENT SIZE Integer
ERROR: WORK ARRAY OVERFLOW IN HYNAST, CURRENT SIZE Integer
ERROR: WORK ARRAY OVERFLOW IN LANAST, CURRENT SIZE Integer
ERROR: WORK ARRAY OVERFLOW IN MPNAST, CURRENT SIZE Integer
ERROR: WORK ARRAY OVERFLOW IN PRNAST, CURRENT SIZE Integer
ERROR: WORK ARRAY OVERFLOW IN TENAST, CURRENT SIZE Integer
Femsys Limited