Exporting mesh from NGSolve/Netgen issues

[TheoF13]

Hi all, I've been trying to mesh a very complex solid of sports headgear to use in impact simulations in Abaqus and was finally successful when I managed to mesh it using NGSolve. I am now having issues exporting this mesh and importing it to Abaqus successfully. Shown in the images below are how the mesh looks in NGSolve and then how it looks when I import it into Abaqus (the crown section of the headgear disappears).

It will only import the mesh at all when exported as a .inp file. I've tried using multiple different file types but they it gives an error when I try any other than .inp.

Any help on this would be much appreciated, as I've spent quite some time trying different ways to get the entire mesh to export. Thank you in advance!

 

[FEA way]

I don't use NGSolve but maybe this top part of the headgear is defined as a separate object or somehow suppressed/hidden and has to be selected or resumed for export. What are the error messages that you get when you try with other file formats ?

 

[BlasMolero]

Dear Theo,
I can try to read the file in Simcenter FEMAP, please post it here and will inform you of the results, FEMAP is really powerful both meshing and importing/exporting many FE formats & FEA results.

The new version of Simcenter FEMAP V2021.2 due for next end of April, 2021 will feature a new TET & QUAD mesher leveraging the powerful meshing capabilities of STAR-CCM+, so I am excited to put my hands on it ... waiting the BETA for testing anxiously!!.
Best regards,
Blas.

~~~~~~~~~~~~~~~~~~~~~~
Blas Molero Hidalgo
Ingeniero Industrial
Director

IBERISA
48004 BILBAO (SPAIN)
WEB:

http://www.iberisa.com

Blog de FEMAP & NX Nastran:

http://iberisa.wordpress.com/

 

[TheoF13]

Hi FEA way,
Thanks for the reply! I will try to see if this is an option in NGSolve, thank you for the suggestion.

The error in Abaqus is the same for any file type other than .inp (see below)

 

[TheoF13]

Hi Blas,

Thank you for your response! Please see the original geometry in a .stp file format and the exported .inp mesh from NGSolve. Your help is much appreciated! Hopefully this will solve the issue.

 

[TheoF13]

Please see second file attached below, as mentioned.

 

[BlasMolero]

Hello!,
The STEP *.stp file is imported in FEMAP with success, the two components appear correctly defined as solids:

The ABAQUS *.inp file imports with errors, when reading the *.inp file I get a lot of errors, you forget to define the properties of the elements, but tetrahedral elements are imported unless with no properties, then it seems that you failed to export the mesh for the two components, only one part exported from NETGEN:
Reading...
0 Coordinate System(s) Translated.
113576 Node(s) Translated.
0 Property(s) Translated.
0 Material(s) Translated.
256296 Element(s) Translated.
0 Load Set(s) Translated.
0 Constraint Set(s) Translated.
Beginning Update of Database...
Property 1 Does Not Exist. Referenced by Element 1.
Property 1 Does Not Exist. Referenced by Element 2.
Property 1 Does Not Exist. Referenced by Element 3.
Property 1 Does Not Exist. Referenced by Element 4.

Best regards,
Blas.


~~~~~~~~~~~~~~~~~~~~~~
Blas Molero Hidalgo
Ingeniero Industrial
Director

IBERISA
48004 BILBAO (SPAIN)
WEB:

http://www.iberisa.com

Blog de FEMAP & NX Nastran:

http://iberisa.wordpress.com/

 

[TheoF13]

Hi Blas,

Thank you so much! This is a great help. I hadn't realised that the headgear was defined as two separate solids, as they were given as a single file to me in an orphan mesh and I had to create a solid from the mesh itself and then remesh, so that is handy to know!
I'm not sure you have any experience with NGSolve? As there doesn't seem to be an option to distinguish between solids to export, there is only a single option.

Again, thank you for your help!