Cancel
Showing results for 
Search instead for 
Did you mean: 

Midside nodes vs. Mesh Sizing

Valued Contributor
Valued Contributor

Hello all.
After using the command Mesh Sizing (Meshing Toolbox) median nodes leave the geometric model of how to avoid this?Mesh Sizing.gif

 

2 REPLIES

Re: Midside nodes vs. Mesh Sizing

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom

Dear Cfytrr,

I note the error as well, this only happens when using th meshing toolbox. As a workaround do the TET10 meshing using command "MESH > GEOMETRY > SOLIDS" and click in OPTIONS:

 

MESHING-TET10-OPTIONS.png

 

In the new form make sure to activate the option "MIDSIDE NODES IN SURFACE", this way the new created midside nodes will be located for sure following the curved surfaces:

 

MESHING-TOOLBOX.png

 

In fact, the result will be something like this, the midside nodes follows perfectly the curved geometry:

 

MESHING-TET10-MIDSIDE-NODES.png

 

You can play with the MESH SIZING in the meshing toolbox and dynamically change the mesh size in curves, no problem, but when you are happy with the mesh density prescribed in curves run the tet meshing command from "MESH > GEOMETRY > SOLIDS", click in OPTIONS and make sure to activate the parameters "Midside Nodes on Surfaces". Also I suggest to activate the option "Detailed Status Messages", this way you will have plenty of information from the tet mesher that has been improved a lot in the last versiones of FEMAP 11.1, now it creates tetrahedral elements with very good quality!!.

 

I am sure the FEMAP guys will take care of this error in the Meshing ToolBox and will be fixed in the next release of FEMAP V11.2.

 

Best regards,
Blas.

Blas Molero Hidalgo, Ingeniero Industrial, Director
IBERISA • 48004 BILBAO (SPAIN)
WEB: http://www.iberisa.com
Blog Femap-NX Nastran: http://iberisa.wordpress.com/

Re: Midside nodes vs. Mesh Sizing

Siemens Phenom Siemens Phenom
Siemens Phenom
Blas is correct. This problem in the Meshing Toolbox has already been identified and corrected. It will work properly in v11.2.