Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wing structure - Add rib posts #628

Closed
rmaierl opened this issue Mar 2, 2020 · 6 comments
Closed

Wing structure - Add rib posts #628

rmaierl opened this issue Mar 2, 2020 · 6 comments
Milestone

Comments

@rmaierl
Copy link

rmaierl commented Mar 2, 2020

An additional element is required to improve the automated FEM model generation with our in-house tool Descartes.
The additional ribPost element represent the connection between a wing rib and a wing spar in an idealized way, modeled in a global finite element model.
The proposal is to add an optional element to the ribCrossSection node with the identical type as the rib caps.

The schema proposal is attached to this issue
ribPosts_schema

@MarAlder
Copy link
Collaborator

MarAlder commented Mar 4, 2020

I got good feedback from SL and BT colleages. So I'll implement a prototype and schedule it for CPACS 3.3.

@sfreund-DLR
Copy link
Contributor

Hello,
I don't really understand which finite element should be modelled with the ribPost. Could you please explain this a little more and maybe also add an image?

@rmaierl
Copy link
Author

rmaierl commented Mar 10, 2020

The Rib posts will be modeled as rod elements.
Please find attached two screenshots of geometrical and structural representation of the rib posts.

ribPosts_geom
ribPosts_fem

Additionally, I added a FEM export in Nastran format with the rib posts. (please replace file ending)
ElemId: 41701433 - 41701438

femMesh_out_bdf.txt

@sfreund-DLR
Copy link
Contributor

Thanks a lot! I got it. So the ribPost is located at the cross section between rib and spar. If this is the case, with the proposed definition, the ribPost at the front spar must be the same as at the rear spar, right?
Additionally, should the ribPost also be added to wingRibCellType?
@MarAlder : I just saw it on the above image:should ribReinforcement also be added to wingRibCellType?

best Regards

@MarAlder
Copy link
Collaborator

I implemented the proposal and added a simple example (77ff211).

Illustrating example

Let's see if I fully understand it. We are describing the vertical brackets/caps connecting the rib to the spars:
ribSparIllustration
[Siedlak et al., 2017]

Once I define the ribPost elements it implicitly applies for all intersections to a spar, e.g. the front and rear edge of this simple rib element:
example

So we assume that they are always identical right?

Further extensions

  • How about extending/modifying the capType with respect to Definition of wing spar caps #558?
  • What is your experience with ribReinforcement?
    • Is it typical for ribs to also have stringers and frames?
    • Is it semantically correct to describe stringers and frames in ribCrossSection?

@sdeinert
Copy link

As a first step I think it would be ok to assume the same cap for all crossings with spars.
If we would like to specify this in a more detailed way, we would somehow need to reference the spar (or possibly another rib) and provide an area/material combination for each of these spar references.
Regarding your questions for further extensions:

  • Definition of wing spar caps #558 seems very detailed, so there it would be necessary to assure that simpler definitions for early stages are still possible. Something relevant in that regard would be cutouts in ribs and spars, as there always need to be holes in the structure elements for cables, pipes etc. If a new rib/spar cutout definition would be flexible enough, maybe some of the cases described in Definition of wing spar caps #558 could be solved through cutouts?
  • Yes especially for larger rib or spar webs it becomes necessary to add reinforcements to avoid buckling of such large web patches. Concerning the nomenclature I don't really have an opinion.

@MarAlder MarAlder mentioned this issue Jul 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants