1. 三点约束
载人潜水器耐压壳在水下工作时不受任何约束,但采用有限元位移法进行计算的时候要消除结构的刚体位移,且不妨碍相对变形。所以计算模型应有足够的位移约束。文献对于完善球壳采用三点约束,即在球壳位于x 和z 坐标轴的位置上(相隔 90°)取三个节点:在 z 轴上的节点 1 和 2,其中 ux, uy=0;在x 轴上的节点,其中uy, uz=0.
2. 惯性释放
采用结构的惯性力以使得与外力相平衡,从而使得模型成为一个平衡力系。对于受约束的支座,有限元计算软件首先计算出在外力作用下每个节点在每个方向上加速度,通过加速度转化惯性力,然后再将这个惯性力施加到模型的每个节点上,从而使得模型保持一个自平衡的力系。即满足了约束条件。
惯性释放中把质心设为虚约束
水压24.5MPa
约束:
SPC1:Single-Point Constraint,单点约束
Format
(1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) |
SPC1 | SID | C | G1 | G2 | G3 | G4 | G5 | G6 |
|
| G7 | G8 | G9 | -etc.- |
|
|
|
|
|
Alternate Format
(1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) |
SPC1 | SID | C | G1 | "thru" | G2 |
|
|
|
|
Field | Contents |
SID | Single-point constraint set identification number. (Integer > 0) |
C | Component number. (Integer zero or blank for scalar points, or up to six unique digits (0 < digit < 6) may be placed in the field with no embedded blanks for grid points. The components refer to the coordinate system referenced by the grid points.) |
Gi | Grid or scalar point identification numbers. (Integer > 0) |
Comments
1 | The degree-of-freedom declared dependent on this entry may not be: |
• | Included in another single-point constraint (SPC or SPC1) |
• | Declared a dependent degree-of-freedom on an MPC set referenced in the same subcase |
2 | Note that enforced displacements are not available via this entry. |
3 | Any number of continuations may appear. |
4. | Multiple “thru” sequences can be used on a single card, and can span across continuation lines. |
5. | SPC degrees-of-freedom may be redundantly specified as permanent constraints on the GRID entry. |
6. | If the "thru" comment is used, G1 and G2 must exist, but the grid points between G1 and G2 are not required to exist. |
7. | For static and dynamic analyses, when the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or MIXED, it is allowed that when grid lists are provided for a given component, that the grid references be either scalar points (SPOINT) or structural grid points (GRID) when the component is 0, 1 or blank; interpreting all of these as 0 for scalar points and as 1 for structural grids. When SPSYNTAX is set to STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank when the grid references are to scalar points (SPOINT), and that the component be > 1 when the grid references are to structural grid points (GRID). When the component is greater than 1, the grid references must always be a structural grid (GRID). |
8. | For linear steady-state heat transfer analysis, SPC1 may be used to define temperature boundary conditions; however, unless paired with an SPCD entry, the enforced temperature is 0.0. For thermal boundary conditions, the component should be 0 or blank when the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or STRICT. When SPSYNTAX is set to MIXED, 1 is also accepted as the component. |
9. | This card is represented as a constraint load in HyperMesh. |
SPCADD: Single-Point Constraint Set Combination,单点约束集合
Format
Format
(1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | (9) | (10) |
SPCADD | SID | S1 | S2 | S3 | S4 | S5 | S6 | S7 |
|
| S8 | S9 |
| -etc- |
|
|
|
|
|
Field | Contents |
SID | New single-point constraint set identification number.(约束集标号) (Integer > 0) |
Si | Single-point constraint sets identification numbers defined via SPC or SPC1 entries. The Si values must be unique. (Integer > 0 or <PartName.number>) See comment 4. |
Comments
1. | The Si field should not reference the identification number of a single-point constraint set defined by another SPCADD entry. |
2. | SPCADD entries take precedence over SPC or SPC1 entries. If both have the same set ID, only the SPCADD entry is used. |
3. | If all Si are non-existent, the solver will exit with an error termination. |
4. | Supported local entries in specific parts can be referenced by the use of “fully qualified references” on SPCADD entries in the model. A fully qualified reference (“PartName.number”) is similar to the format of a numeric reference. “PartName” is the name of the part that contains the referenced local entry (part names are defined on the BEGIN Bulk Data entry in the model). “number” is the identification number of a referenced local entry in the part “PartName”. See Parts and Instances in the User’s Guide for detailed information on the use of fully qualified references. |
5. | This card is represented as a loadcollector in HyperMesh. |