Line #122, Error #3316, Layups must be numbered 10000 through 19999

[SD_Gabe]

I keeping getting an application error regarding a material import:

Line #122, Error #3316, Layups must be numbered 10000 through 19999

followed by:

Line #33, Error #1, Error importing NASTRAN material...

I've received the error before but I can't remember what I did to get rid of it. I'm importing FEM that I have successfully imported before. There is an almost identical project with no error previous run in the same database.

[James]

Gabe,

Can you confirm the material names have only 5 digits after KMAT8%

To import the PCOMP definition and automatically apply material definitions to the layups, the materials have to include the KMAT8%##### identifier at the end of the material name. the numbers should only be 5 digits.

[SD_Gabe]

Hey James,

The MAT ID's we are using have 8 digits, however we have a modified version of HyperSizer to remove the last 3 digits and only read the first 5. So that shouldn't be an issue.

The MATS and PCOMPS are identical in the successful and unsuccessful imports. The only difference in the two projects I had mentioned was that 1 gap value has been modified in one of the models.

Thanks,

-g

[James]

Gabe,

You may have too many layup definitions in your database. What happens if you try importing the FEM into a new database containing the required orthotropic materials?

If you want to use the same database, you could try to remove the unused layups (using the material cleanup feature), then compact the database and try importing the FEM again.

If neither of these suggestions work, then I could take a look at your database. For me to look at it you will have to post the database and .bdf to our secure transfers site.

-James

[SD_Gabe]

The material cleanup/compacting did not work.

I imported the second model into a new database and it seems to be working. I guess I'll have to keep track of two databases now...

Thanks for your help James.

[James]

Can you import the other project into the new database? Then you only need to track one database.

-James