Merge parts in FE models

hi,

for some reason and limitation of 2D STL format is failed to create compound part. so i’m thinking mesh it separately to be merge in FE models, however the node coincident did not merge and still keep it separated.

is this limitation or the design approach with another purpose? may it be possible to merge coincident/duplicated nodes were it’s common feature in FE software.

tie constraint or tied contact can be easily generated in PrePoMax, but merging coincident nodes is the effective workflow due to duplicated node coordinates.

best,

Generally speaking, the STL format is not good for FEA. It’s much better to use STEP files instead.

Can you share this geometry for tests ?

right, i have no problem with 2D STP file when doing compound parts.

but as my previous comment at another threads, i have no serious problem using 2D STL format as the base of geometry.

also, it’s commonly supported by many CAD software.

yes, thanks for look further of the problem in compound part (geometry modules/tabs)

innerboundaryrun.pmx (1.5 MB)

I can confirm that there’s an error (very long generic message) when trying to create a compound part out of these two parts and that merging them in the FE Model tab doesn’t actually connect the nodes, as can be seen in the results. Maybe this could be fixed.

Compound parts are only possible for the CAD geometry and should not be possible for the .stl geometry.

Merge parts is a feature that was created in the beginnings of the PrePoMax development. It is an opposite feature of the Convert element set to part feature. It is only meant to assign elements from two separate parts to one common part and does not change the mesh at all.

So for the functionality you need, new features would be needed. Something like Merge mesh and Split mesh.

1 Like

it could be better to disable compound part of STL files in geometry modules if not supported.

an option to merge nodes with coincident/same coordinates or called merge mesh is common in FE software.

more simple ways rather defining node/face for tie constraint or tied contact definition. also, not making conflict when penalty contact available there.

Of course, you are right. However, merge option can be used successfully only when meshes in the contact zones are compatible and corresponding nodes nearly coincide. IMHO Netgen version used inside PPM for mesh generation does not allow to define mesh density on edges or surfaces so precisely. Perhaps you should simply use another mesher (like GMSH) in such a case.

right, may some tolerance based on nearest distance can apply, generate new node at mids or intermediate coordinates is common also.

so coordinates of both selection groups not to be precisely or exactly the same, but number of nodes in each group need to be equal (mandatory)

*edited
tie constraint in my previous example files attached lead to problem also, since each group of nodes is not equal in numbers.


(mesh:min=2.5mm,max=5mm)

user need to remeshing to make the model properly,


(mesh:min=5mm,max=10mm)

may i correcting my previous comment, this is due to default position tolerances. set manually to higher values solved the problems.

*edited

still clearly shown, not all can be done automatically. some adjustment by the user is required to set properly.