Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations KootK on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Big shell model problems with 400+ Connectors

Status
Not open for further replies.

Zwicky

Marine/Ocean
Jan 28, 2013
7
Hello everyone,

I'm currently working on a 40 meters ship model for linear static analysis, mainly all shell elements QUAD4 (small thickness structures). The geometry has been prepared with rhino in order to use the new Femap V11 improved edge-surface glue feature.
First of all I made a couple of tries with femap v10 to see if it was really not working properly, as said by siemens' salesmen, and it actually seems right, i noticed some relative displacement where it shouldn't have been.
My question is this: my model has approx. 400 connectors, and i know that nastran is not very happy when same elements belonging to a surface are attached on both sides (this by the way for a deck-like surface is not very nice,
because it is laying on the hull frames and has deckhouse or other structures on top of it, so this sounds like an omission from salesman in my opinion), but going on with the modeling, some connections that were working perfectly just start to fail,
without me modifying any of the associated elements, properties, entities, etc. etc.. Does someone have an idea why that happens?
To be more precise i use glue-contact connection type, glue type ''weld'', glue factor ''1'', search distance of 3.5 mm because all the shell haven't more that 6 mm thickness, and i repeat there
are only edge (curves) on surfaces. The sources regions are surfaces and the targets are curves (also this was adviced by femap training partner but i read on nastran help that actually the source should be the curves and present also a finer mesh
because nastran creates edge elements to model the connection). If it was not clear until now, i have a big chaos in my mind about this topic, if someone had more experience about this and can give a clearer explanations please give your advice,
I would be glad to hear from you.

Best regards,

Zwicky.
 
Replies continue below

Recommended for you

"glue" the edges ? why ? why not just nodes to ground (to test the model) then CBUSH or springs to control stiffness ?

a pic would help explain the problem.

Quando Omni Flunkus Moritati
 
Hello!,
The source region in the GLUE pair must be the edge region. The target region consists of shell or solid element faces.
A simplistic description of edge-to-surface glue is that the software creates pseudo-faces along the edges in the source region. It then connects these pseudo-faces to the shell or solid faces in the target region with weld like connections.

Also, the future release of FEMAP V11.1 will be extremely powerful dealing with NonManifold geometry, a big improvement will be in Parasolid kernel modeler engine, then you can get rid of using so many glue edge-to-face contacts, only when necessary, making easy the shell meshing takeing care with displacements compatibility.

Best regards,
Blas.


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

IBERISA
48011 BILBAO (SPAIN)
WEB: Blog de FEMAP & NX Nastran:
 
Hello,

upload immagini gratis


As you can see, one big surface with big mesh on which are lying other surfaces with different mesh. There are many ways to model this, one can split (in rhino or in femap also) the bigger surface on the location where the contact is and the merge nodes, otherwise you glue them, this is what i know can be done. The reason can be that you're not much interested in the big shell, you want to save elements and thus computing time, so you use different meshes; on the other side, starting to have 500 connections doesn't make things much easier. I am also curious if someone else is facing such big model (150.000 elements) using this new feature.

For Blas, thank you,you confirm the little i knew. Last, i'm building just half of the model respect to its longitudinal axis: can be a stupid question, but if i wanted to mirror it, i think i can't mirror all the connections, they are referred to geometries and meshes, and of course i don't want to start from zero with another half. Also what i discovered is that such edges, if belonging to 90 degrees surfaces, should belong to different regions (i often get an error like ''nodes not in topological order or branching'').

Thank you!






 
Dear Zwicky,
You can mirror surfaces, and automatically new regions & connectors will be created as well, this is nice in FEMAP and runs OK.
Is critical to apply mesh attributes to surfaces geometry, this way when mirroring surfaces you will mirror properties as well. All geometry will have mesh attributes, don't forget this important detail.
I run big Shell models as well, combining all techniques: glue surface-to-surface, glue edge-to-surface, glue edge-to-edge, and also NonManifoldAdd Surfaces, this last resource is very, very practical & powerful indeed. Take care with proper surface orientation (Top/Bottom faces compatibility!), when meshing with Shell elements this is critical as well!.

Branching is a problem when you define regions with multiple branchs, this sould be avoided at all, gives error. An edge region should be defined between consecutive grid points. The grid points defining the edge region must be entered in a continuous topological order. If an edge region or curve forms a closed loop, for example, the grids around the perimeter of a cylinder edge, the last grid point identification number should be the same as the first grid point number.

Best regards,
Blas.

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

IBERISA
48011 BILBAO (SPAIN)
WEB: Blog de FEMAP & NX Nastran:
 
Dear Blas,

thank you for your , as usual, very useful advices.
I just mirrored the surfaces and as you said connections regions are mirrored as well, i just get an error when i try to merge the nodes on my simmetry axis, which goes:

nodes not merged due to Output Coordinate System conflicts!

If anyone knows anything about this i would like to undestand more.

Best regards,
Zwicky.
 
Dear Zwicky,
Yes, simply use "Modify > Update Other > Output CSys... ", select ALL nodes and assign the GLOBAL CARTESIAN "0. Basic Rectangular" coodinate system, and you are done. Next, do the node merging process as usual.

Best regards,
Blas.


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

IBERISA
48011 BILBAO (SPAIN)
WEB: Blog de FEMAP & NX Nastran:
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor