Software Use > FEM Coupling (HyperFEA)

HyperSizer writting duplicate PCOMP entries

(1/1)

MGerhardt:
Hello,
while updating FEM HyperSizer creates a .bdf file with the original PCOMP entries (IDs starting with 1) at the beginning of the file, like:
$ Elements and Element Properties for region : Rib_01
$ Composite Property Reference Material: Rib_01
$ Composite Material Description :
PCOMP    1         100.     STRN
         1   2.17   45.   [...]
$ Pset: "Rib_01" will be imported as: "pcomp.1"
Also the modified materials are exported (also IDs starting with 1):
$ Component 1: Rib_01
MAT8*                291  [...]
PCOMP*                 1  [...]
Nastran aborts the analysis due to the duplicate PCOMP entries. So, why does HyperSizer print out the original PCOMPS? And how can I deactivate it?
Best Regards

Ryan:
Hi Marco,

What version are you running? The original POMPs should be deleted in the iteration (_i.bdf). For some reason it is not picking up the original PCOMP 1.

1) If you switch the PCOMP from small to large format (PCOMP*), does that fix the issue?

2) Are there any complicated INCLUDE statements that may be causing issues?

-Ryan

MGerhardt:
I'm using 6.4.10.
1) It works with the large PCOMPS from the nastran .pch file
2) There are no INCLUDE statements

And I found the mistake. Looks like there was a special combination of spacing and tabs in the PCOMP (I edited them manually), so HyperSizer didn't identify the PCOMPs. (Though for the Analysis with Nastran no problem.)
Thanks for your help.

Ryan:
Good to hear that it is working now. Could you attach a text file with the PCOMP entry with tabs that caused the issue in HyperSizer?

MGerhardt:
Sure.

Navigation

[0] Message Index