-
Notifications
You must be signed in to change notification settings - Fork 39
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
Comments
I got good feedback from SL and BT colleages. So I'll implement a prototype and schedule it for CPACS 3.3. |
Hello, |
The Rib posts will be modeled as rod elements. Additionally, I added a FEM export in Nastran format with the rib posts. (please replace file ending) |
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? best Regards |
I implemented the proposal and added a simple example (77ff211). Illustrating exampleLet's see if I fully understand it. We are describing the vertical brackets/caps connecting the rib to the spars: 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: So we assume that they are always identical right? Further extensions
|
As a first step I think it would be ok to assume the same cap for all crossings with spars.
|
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](https://user-images.githubusercontent.com/10923333/75697748-d15f4200-5cad-11ea-80ec-e5767c1dfafd.png)
The text was updated successfully, but these errors were encountered: