|
| int | m_blockedDOF |
| boost::optional< int > | m_fromStructureCounter |
| | Optional counter to specify numbered items, e.g. ribs in a ribSet.
|
| std::string | m_fromStructureUID |
| | The UID for the first connection UID may include for wings: skin, sparUID, ribDefinitionUID, ribNumber, stringerUID, stingerNumber, and for fuselages: skinSegmentUID, frameUID, stringerUID, crossBeamUID, crossBeamStrutUID, longFloorBeamUID.
|
| CPACSFuselageStructuralMounts * | m_parent |
| bool | m_takeOnlyEndPoints |
| | If this value is set to true then only the end points of the intersection shall be included as nodes in the model.
|
| boost::optional< int > | m_toStructureCounter |
| | Optional counter to specify numbered items, e.g. ribs in a ribSet.
|
| std::string | m_toStructureUID |
| | The UID for the second connection UID may include for wings: skin, sparUID, ribDefinitionUID, ribNumber, stringerUID, stingerNumber, and for fuselages: skinSegmentUID, frameUID, stringerUID, crossBeamUID, crossBeamStrutUID, longFloorBeamUID.
|
| std::string | m_uID |
| CTiglUIDManager * | m_uidMgr |
Structural mount.
In order to place non-structural masses in a model, it is necessary to define where these masses are attached to the structure. For example, you want to model a heavy on-board system, a piece of payload, a fuel tank, an engine, etc. as a fixed point mass. The first step would be to create a mass point at the center of gravity of your component. For some components this is directly available, the a fuel tank you would evaluate the volume and fill rate from its CPACS definition to get the CoG. The next step is to connect the mass point to the structure in a physically meaningful way to properly introduce any inertial loads generated by that mass into the structure. This purpose is fulfilled by the structural mounts. The logic of these mounts is to identify points or lines in the geometry created by the intersection of two referenced structural components ("fromStructureUID" and "toStructureUID"). These points or lines are then connected to the center of gravity of the mass point. The reasoning behind this is that the intersections between two structural objects (e.g., rib and spar) usually represent locations in the model that are stiff enough to support the additional loads from any equipment. For example, the following figure shows a heavy system represented by a generic sphere attached to the structure by three structural mounts:
- See also
- structuralAttachments From left to right: The leftmost attachment uses the end points of the intersection line between the starboard wall and the forward bulkhead. The middle attachment uses all points (here only 7 points are drawn for visualization) on the intersection line between the middle wall and the front bulkhead. The rightmost attachment has a similar definition to the left one, using the end points of the intersection line between the port wall and the front bulkhead. When creating a structural FEM model of this CPACS representation, a rigid body element (e.g. Nastran RBEx) can be generated based on the yellow lines. This is used, for example, to attach landing gear struts to the aircraft structure. In short, structural mounts identify points or lines by intersecting two structural components, the resulting points or lines are then attached to a third component that references this structural mount as its attachment. Typically, as in the example above, components reference more than one structural mount as their attachment points.
| std::string tigl::generated::CPACSStructuralMount::m_fromStructureUID |
|
protected |
The UID for the first connection UID may include for wings: skin, sparUID, ribDefinitionUID, ribNumber, stringerUID, stingerNumber, and for fuselages: skinSegmentUID, frameUID, stringerUID, crossBeamUID, crossBeamStrutUID, longFloorBeamUID.
| std::string tigl::generated::CPACSStructuralMount::m_toStructureUID |
|
protected |
The UID for the second connection UID may include for wings: skin, sparUID, ribDefinitionUID, ribNumber, stringerUID, stingerNumber, and for fuselages: skinSegmentUID, frameUID, stringerUID, crossBeamUID, crossBeamStrutUID, longFloorBeamUID.
