Nobody likes Nastran fatal messages, but they are a part of FEA just like meshing. I’m going to use this location to document the solutions to the Nastran FATAL errors messages I receive when I make NX Nastran a little upset. I’m sorry this will be sparse to start out. My plan is to populate it as times goes on and I encounter more error messages.
By the way, you can always refer to ..\nastranhelp\pdf\error.pdf in your Femap install path to find the official list of Nastran error codes. They aren’t the most helpful, though, hence the reason for this table:
| FATAL message | NASTRAN message | Solution | FATAL ID |
|---|---|---|---|
| SYSTEM FATAL MESSAGE 5407 (LNCCKD) | INERTIA (STURM SEQUENCE) COUNT DISAGREES WITH THE NUMBER OF MODES ACTUALLY COMPUTED IN A (PARTIAL) INTERVAL | Research indicated that the fix would be to increase the number of requested modes, albeit this fix was associated with a free-free modes check. This other "fix" was traced back to requesting fewer modes than rigid body (near zero) modes existing in the model, as the user had multiple disconnected meshes. I was running SOL103 normal modes in a fixed configuration. Finally fix was to eliminate K6ROT=0 parameter usage and leave to default value of 100. | 5407 |
| SYSTEM FATAL MESSAGE 3094 (SSGSLT) | Femap write out more ACCEL1 cards than NX Nastran can manage (10k). Fix is to add a line for "WriteCompactAccel1=1" to your Femap.INI file. Note there is a post about this on LearningFEA.com dated 3/17/16. | 3094 | |
| USER FATAL MESSAGE 1250 (BIOWRT) | ERROR MESSAGE IS — There is not enough space on the disk. | Specified supplemental scratch directory locations on another computer HD that had extra capacity to give to the solution process. Note there is a post about this on LearningFEA.com dated 1/20/16. | 1250 |
| SYSTEM FATAL MESSAGE 4276 (IONAST) | USER INFORMATION: THIS ERROR MAY BE CAUSED BY EXCEEDING THE CAPACITY OF A SYSTEM RESOURCE. (E.G., ALLOCATED DISK IS FULL, OR MAXIMUM FILE SIZE HAS BEEN REACHED) | Related to FATAL 1250. Specified supplemental scratch directory locations on another computer HD that had extra capacity to give to the solution process. Note there is a post about this on LearningFEA.com dated 1/20/16. | 4276 |
| USER FATAL MESSAGE 4654 (EHEXGS) | ELEMENT WITH ID = 86389 CONNECTS TWO POINTS HAVING THE SAME COORDINATES. CONNECTION ORDER OF GRID POINTS IN QUESTION = 3 AND 7 User information: Two grid points which should be unique are defined as coincident. Check connectivity. | A model had been converted from mm to meters length units. A simple solution would then fail with this message. Connectivity was not setup incorrectly. The problem lied in the unit conversion. When Femap wrote out the Nastran input file in the default short-field format, the spacing between some nodes was on the order of mm, which, when described in meters, are essentially the same number. Solution was to either maintain mm units or use long field format, which is an option under the Bulk Data options dialog (edit analysis). | 4654 |
| USER FATAL MESSAGE 2038 (RBE3S) | RBE3 ELEMENT 18 IS SINGULAR. USER ACTION: ADD MORE DOFS TO THE CONNECTED POINTS TO INSURE THAT THEY CAN CONSTRAIN ALL 6 RIGID BODY MODES OF THE ELEMENT. | An RBE3 interpolation element was (somehow) created without any weighting assigned to the independent nodes. This weighting is usually set to 1 by default in Femap. It was set to 0 in this particular model. Easy fix to update the independent nodes weighting function once this was identified as the issue. | 2038 |
| USER FATAL MESSAGE 608 (IFP1D) | THE SET ID SPECIFIED ON THE ABOVE CARD MUST BE DEFINED PRIOR TO THIS CARD. User information: Set identification numbers must be specified prior to their use. Also sets specified within a subcase are valid only within that subcase. Redefine the errant set (or define a required set) or move the set out of the subcase it is in. 7 STRESS(PLOT,CORNER) = 1 | I manually edited the case control section and the SET definition was placed AFTER a line that used it. In this case, STRESS command referenced SET 1, but SET 1 was defined after that line. | 608 |
| USER FATAL MESSAGE 9025 (IFPL) | ^^^ ERROR ENCOUNTERED IN THE CASE CONTROL SECTION ^^^ SEE MESSAGES ABOVE. ERROR ENCOUNTERED IN MODULE IFP1. | Appears to be a general indicator that something went wrong in the case control, in this case, due to the 608 error. | 9025 |
| SYSTEM FATAL MESSAGE 7340 (LNNHERR) | WARNING REPORTED BY SUBROUTINE LNNDRVS (IER= 725) USER INFORMATION: NUMBER OF COMPUTED EIGENVALUES EXCEED ALLOCATED STORAGE. | Solution was a buckling breakout analysis using system FEM internal loads (SPCDs, interface forces) of a rather intricate structure. Attempted adjusting MAXRATIO and introducing K6ROT to no avail. Went back and ran normal modes solutions, which showed the true problem of disconnected mesh. So the system FEM internal loads weren't being applied to a comparable breakout structure and thus 105 must've been recovering too many modes. | 7340 |