|
»Click here to display Table of Contents«
|
MPC |
|
|
|
|
|
MPC |
|
|
|
|
|
»Click here to display Table of Contents«
|
MPC |
|
|
|
|
|
MPC |
|
|
|
|
Bulk Data Entry
MPC – Multipoint Constraint
Description
The MPC bulk data entry defines a multipoint constraint equation of the form.
Where,
is the coefficient that can be used to define the relationship between the degrees-of-freedom associated with grid points (or a scalar point) in the model.
is the degree-of-freedom associated with a grid point (or a scalar point).
Format
(1) |
(2) |
(3) |
(4) |
(5) |
(6) |
(7) |
(8) |
(9) |
(10) |
MPC |
SID |
G |
C |
A |
G |
C |
A |
blank |
|
|
blank |
G |
C |
A |
-etc.- |
|
|
blank |
|
|
Field |
Contents |
SID |
Set identification number. (Integer > 0) |
G |
Grid point or a scalar point identification number. (Integer > 0 or <PartName.number>) See comment 4. |
C |
Component number. The component refers to the coordinate system referenced by the grid point. (Integer zero or blank for scalar points, or any one of the digits 1-6 for grid points) |
A |
Coefficient that can be used to define the relationship between the degrees-of-freedom associated with grid points (or a scalar point). (Real; the first A must be non-zero) |
| 1. | The first coordinate in the sequence is assumed to be the dependent coordinate. A dependent degree-of-freedom assigned by one MPC entry cannot be assigned dependent by another MPC entry or by a rigid element. |
| 2. | When the SPSYNTAX setting on the SYSSETTING I/O option is set to CHECK (default) or STRICT, it is required for grid/component pairs (G#/C#) that the component be 0 or blank when the grid reference is a scalar point (SPOINT), and that the component be > 1 when the grid reference is a structural grid point (GRID). When SPSYNTAX is set to MIXED, it is allowed for grid/component pairs (G#/C#) that the grid reference be either a scalar point (SPOINT) or a structural grid point (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 the component is greater than 1, the grid reference must always be a structural grid (GRID). |
| 3. | Illustrative Example: |
Figure 1 can be used to illustrate an MPC application. Independent grid points G1 and G2 of a 2D quad element are connected with the help of an MPC; where Gd is the dependent grid point. The objective of this example is to force the displacement of Gd to be equal to the sum of the displacements of grid points G1 and G2 in the X (1) direction using an MPC.
Figure 1: MPC Example Illustration
Rewriting the MPC equation for three grid points:
Substituting A1 = 1.0, A2 = -1.0 and A3 = -1.0 in the equation above:
Rearranging equation terms:
Where, ud is the displacement of grid point Gd in X direction, u1 is the displacement of grid point G1 in X direction, and u2 is the displacement of grid point G2 in X direction.
| 4. | Supported local entries in specific parts can be referenced by the use of “fully qualified references” on MPC 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 an equation in HyperMesh. |
See Also:
