Cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

ERROR MESSAGE 307

Valued Contributor
Valued Contributor

Hello everyone,

 

I have a problem with my SOL 101 submission on Nastran. I have a model exported from NX12.0.

 

Hereinafter is my .bdf:

******************************************************
SOL 101
CEND
ECHO = NONE
LOAD = 50000
SPC = 1000
TEMPERATURE(MATERIAL)= 10000

SUBCASE 1
TITLE=L1-EFFORTS
SUBTITLE=L1-EFFORTS
MPCFORCES(PRINT)=5

BEGIN BULK
PARAM POST -1
PARAM GRDPNT 0
PARAM PRTMAXIM YES
$
INCLUDE '../../01_FEM/FEM.dat'
INCLUDE '../../01_FEM/01_AERO_LOADS/Temperature.dat'
INCLUDE '../../01_FEM/01_AERO_LOADS/Force.dat'
INCLUDE '../../01_FEM/02_BOUNDARY_CONDITIONS/Boundary_Conditions.dat'


$ Pressure
LOAD, 50000, 1.3, 0.1, 1

******************************************************

 

In my F06 file I have the following error message:

 *** USER FATAL MESSAGE 307 (IFPDRV)
     ILLEGAL NAME FOR BULK DATA ENTRY 0.601347

 

Now the problem is that I don't have any "0.601347" in my .bdf and .dat !

 

Do you know were could be the problem please?

 

7 REPLIES

Re: ERROR MESSAGE 307

Gears Phenom Gears Phenom
Gears Phenom

in whichever file you have 0.601347 it's not correctly defined. On this nastran card you might be missing a space or have 1 too many. Do you have a 601347? It loosk like you have defined a nastran key word as 0.601347 as the msg refer to a name

Production: NX.CAE 9.0.3.4, NX.CAE 10.0.2.6
Development: VB.NET (amateur level !)

Re: ERROR MESSAGE 307

Siemens Phenom Siemens Phenom
Siemens Phenom

These types of errors are usually due to a formatting or escape/control character in the file that may not be visible in some editors.

 

The best course of action os to add a ECHO=UNSORT to the case control. This will print the unsorted bulk data read from all files (main deck + include files), as Nastran interpreted it, to the .f06 file. When you examine that, you should be able to determine which card triggered the error.

Re: ERROR MESSAGE 307

Valued Contributor
Valued Contributor

Thank you for your answer selex_ct.

 

I actually don't have any 0.601347 in my files, not even a 601347 !

 

I don't think I've defined a key word neither...

Re: ERROR MESSAGE 307

Gears Phenom Gears Phenom
Gears Phenom

Odd that Nastran if flagging something you think it's not there. On top of what JimB suggested, maybe there is a $ sign missing? A comment added to one of the file!

Try importing the (master) .bdf in Nx and see the warning message(s). During the import the "faulty" card should be skipped

Production: NX.CAE 9.0.3.4, NX.CAE 10.0.2.6
Development: VB.NET (amateur level !)

Re: ERROR MESSAGE 307

Valued Contributor
Valued Contributor

Thanks JimB for your reply!

 

I asked an ECHO=UNSORT. It sorted indeed the whole bulk data. I found all the data from the include files.

And as I was comparing the Temperature entries emported from Excel I found a "#VALUE!" hidden between the lines !   

*************************************************

                 9427-        TEMP,10000,69622,17.7649
                 9428-        TEMP,10000,69623,18.2249
                 9429-        TEMP,10000,69624,17.9866
                 9430-        #VALEUR!
                 9431-        TEMP,10000,69626,17.8301
                 9432-        TEMP,10000,69627,17.8301

************************************************

 

It was quite hard to notice between nearly 200.000 lines of temperature entries!

 

The problem is now solved!

 

Thank you all for your precious help!

Re: ERROR MESSAGE 307

Siemens Phenom Siemens Phenom
Siemens Phenom

Looks like there was an issue in Excel with the temperature data for grid 69625.

 

If that grid is missing from TEMP set 10000, it will be assigned the TEMPD temperature value.

Re: ERROR MESSAGE 307

Valued Contributor
Valued Contributor
Exactly!

The thing is that Excel skipped the grid 69625 (because of its coordinates...). The temperature of this grid was then defined with the TEMPD of the model.

Now the "#VALUE!" was still hidden in the TEMP,10000 list. And as there wasn't a $ in front of it, Nastran couldn't read it as an entry. Therefore it gave the error:
*** USER FATAL MESSAGE 307 (IFPDRV)
ILLEGAL NAME FOR BULK DATA ENTRY 0.601347

Which does not give any clue on what the problem is! I mean how did it choose this value of 0.601347 ?

Anyways, next time I will know that something is going wrong with the $! Smiley Very Happy