General Multi-Point Constraints

Identifying the Nodes Involved in the MPC

For any MPC type, either node sets or individual nodes can be given as input. If the first entry is a node, subsequent entries must be nodes. If the first entry is a node set, subsequent entries can be either node sets or single nodes. The latter option is useful if a degree of freedom at each of a set of nodes depends on a degree of freedom of a single node, such as might occur in certain symmetry conditions or in the simulation of a rigid body.

If node sets are used, corresponding set entries will be constrained to each other. If sorted node sets are given as input, you must ensure that the nodes are numbered such that they will match up correctly when sorted. The nodes in an unsorted node set (see Node Definition) will be used in the order that they are given in defining the set.

In Abaqus/Standard multi-point constraints cannot be used to connect two rigid bodies at nodes other than the reference nodes, since multi-point constraints use degree-of-freedom elimination and the other nodes on a rigid body do not have independent degrees of freedom. In Abaqus/Explicit a rigid body reference node or any other node on a rigid body can be used in a multi-point constraint definition.

Abaqus/CAE uses connectors to define multi-point constraints between two points and constraints to define multi-point constraints between a point and secondary nodes in a region. Set-to-set multi-point constraints and unsorted node sets are not supported in Abaqus/CAE.

Input File Usage

MPC

Abaqus/CAE Usage

Use the following options to define a multi-point constraint between two points:

Interaction module: 
ConnectorGeometryCreate Wire Feature
ConnectorSectionCreate: Connection Category: MPC, 
MPC type: select type
ConnectorAssignmentCreate: select wires: Section: select MPC connector section

Use the following options to define a multi-point constraint between a point and secondary nodes in a region:

Interaction module: 
ConstraintCreate: MPC Constraint: select control point and region; MPC type: select type

Use with Transformed Coordinate Systems

Local coordinate systems (see Transformed Coordinate Systems) can be defined for any nodes connected to MPCs. Some special considerations apply for user-defined MPCs, as described in MPC.

Defining Multiple Multi-Point Constraints at a Point

See About Kinematic Constraints for details on how multiple kinematic constraints at a point are treated in Abaqus/Standard and Abaqus/Explicit.

In Abaqus/Standard MPCs are usually imposed by eliminating the degree of freedom at the first node given (the dependent degree of freedom). MPC types BEAM, CYCLSYM, LINK, PIN, REVOLUTE, TIE, and UNIVERSAL are sorted internally by Abaqus/Standard so that the MPC in which a node is used as a dependent node is the last MPC that uses this node. Therefore, groups of these MPCs can be given in any order. However, even for these MPCs, a node can be used only once as a dependent node. In other cases dependent degrees of freedom should not be used subsequently to impose kinematic constraints; this generally precludes the use of the first node in an MPC definition as an independent node in any subsequent multi-point constraint, equation constraint, kinematic coupling constraint, or tie constraint definition.

Using MPCS in Implicit Dynamic Analysis

In implicit dynamic analysis Abaqus/Standard enforces MPCs rigorously for the displacements. The velocities and accelerations are derived from the displacements with the relations defined by the dynamic integration operator (see Implicit dynamic analysis). For linear MPCs (such as PIN, TIE, and mesh refinement MPCs) and geometrically linear analysis the velocities obtained in this way satisfy the constraint exactly. However, the accelerations satisfy the constraint only approximately. If nonlinear MPCs (such as BEAM, LINK, and SLIDER) are used in geometrically nonlinear analysis, both the velocities and accelerations satisfy the constraint only approximately. In most cases the approximation is quite accurate, but in some cases high frequency oscillations might occur in the accelerations of the nodes involved in the MPC.

Using Nonlinear MPCS in Geometrically Linear Abaqus/Standard Analysis

If a nonlinear MPC is used in a geometrically linear Abaqus/Standard analysis (see General and Perturbation Procedures), the MPC is linearized. For example, if MPC LINK is used in a geometrically nonlinear Abaqus/Standard analysis, the distance between the two nodes of the link remains constant. If it is used in a geometrically linear Abaqus/Standard analysis, the distance between the two nodes is held constant after projection onto the direction of the line between the original positions of the nodes. The difference should be noticeable only if the magnitudes of the rotations and displacements are not small.

Defining MPCS in a User Subroutine

In Abaqus/Standard you can define multi-point constraints in user subroutine MPC.

Constraints defined in user subroutine MPC can only use degrees of freedom that also exist on an element somewhere in the same model. For example, if a model contains no elements with rotational degrees of freedom, user subroutine MPC cannot use degrees of freedom 4, 5, or 6. This limitation can be overcome by adding a suitable element somewhere in the model to introduce the required degrees of freedom. This element can be added so that it does not affect the response of the model.

Constraints defined in the user subroutine are applied to the transformed degrees of freedom. A boundary nonlinearity occurs in Abaqus/Standard when MPCs are activated/deactivated in a user subroutine.

Input File Usage

MPC, USER

Abaqus/CAE Usage

Use one of the following options:

Interaction module: Create Connector Section: select MPC as the Connection Category and User-defined as the MPC Type

Interaction module: Create Constraint: MPC Constraint; select User-defined as the MPC Type

Specifying the Version of User Subroutine MPC

You must specify whether the user subroutine will be coded in degree of freedom mode or in nodal mode.

Input File Usage

Use one of the following options:

MPC, USER, MODE=DOF
MPC, USER, MODE=NODE

Abaqus/CAE Usage

Use one of the following options:

Interaction module: Create Connector Section: select MPC as the Connection Category and User-defined as the MPC Type, choose DOF-by-DOF or Node-by-Node

Interaction module: Create Constraint: MPC Constraint: select User-defined as the MPC Type, choose DOF-by-DOF or Node-by-Node

Reading the Data from an Alternate Input File

The input for an MPC definition can be contained in a separate input file.

Input File Usage

MPC, INPUT=file_name

If the INPUT parameter is omitted, it is assumed that the data lines follow the keyword line.

Abaqus/CAE Usage

Reading data from an alternate input file is not supported in Abaqus/CAE.

MPCS for Mesh Refinement

LINEAR

This MPC is a standard method for mesh refinement of first-order elements. It applies to all active degrees of freedom at the involved nodes including temperature, pressure, and electrical potential.

In Abaqus/Explicit it might be preferable to use a surface-based tie constraint (see Mesh Tie Constraints) for mesh refinement, particularly when one or more of the meshes to be constrained involve shell elements with thickness.

QUADRATIC^(S)

This MPC is a standard method for mesh refinement of second-order elements. It applies to all active degrees of freedom at the involved nodes except for temperature degrees of freedom in coupled temperature-displacement analysis and coupled thermal-electrical-structural analysis and to pressure degrees of freedom in coupled pore pressure analysis. For refinement using second-order pore pressure or coupled-temperature displacement elements, the P LINEAR or T LINEAR MPC must be used with this MPC.

BILINEAR^(S)

This MPC is a standard method for mesh refinement of first-order solid elements in three dimensions. It applies to all active degrees of freedom at the involved nodes including temperature, pressure, and electrical potential.

C BIQUAD^(S)

This MPC is a standard method for mesh refinement of second-order solid elements in three dimensions. It applies to all active degrees of freedom at the involved nodes except for temperature degrees of freedom in coupled temperature-displacement analysis and coupled thermal-electrical-structural analysis and to pressure degrees of freedom in coupled pore pressure analysis. For refinement using pore pressure or coupled-temperature displacement elements in three dimensions, the P BILINEAR or T BILINEAR MPC must be used with this MPC.

P LINEAR^(S)

This MPC can be used with the QUADRATIC MPC for mesh refinement of second-order, fully coupled pore fluid flow-displacement elements. It applies to pressure degrees of freedom only. For acoustic analysis it applies the same constraint as the LINEAR MPC.

T LINEAR^(S)

This MPC can be used with the QUADRATIC MPC for mesh refinement of second-order, fully coupled temperature-displacement and fully coupled thermal-electrical-structural elements. It applies to temperature degrees of freedom only. For heat transfer analysis it applies the same constraint as the LINEAR MPC.

P BILINEAR^(S)

This MPC can be used in the C BIQUAD MPC for mesh refinement of pore fluid flow-displacement elements in three dimensions. It applies to pressure degrees of freedom only. For acoustic analysis it applies the same constraint as the BILINEAR MPC.

T BILINEAR^(S)

This MPC can be used in the C BIQUAD MPC for mesh refinement of fully coupled temperature-displacement and fully coupled thermal-electrical-structural elements in three dimensions. It applies to temperature degrees of freedom only. For heat transfer analysis it applies the same constraint as the BILINEAR MPC.

Using Mesh Refinement MPCS with Shell or Beam Elements

The Abaqus/Standard shell elements S4R5, S8R5, S9R5, and STRI65 use a penalty method to enforce transverse shear constraints on the edges of the element. The use of mesh refinement MPCs LINEAR and QUADRATIC might, therefore, lead to overconstraining or “shear locking” of the bending behavior. Graded meshes, using the triangular elements as necessary to create a transition zone, are recommended for mesh refinement with these elements.

The shear flexible beam elements in Abaqus/Standard such as B31 or B32 will also “lock” if used as stiffeners along a mesh line where the mesh refinement MPCs are used.

For shell elements in Abaqus/Explicit the rotational degrees of freedom are not constrained by the LINEAR MPC; therefore, a hinge is formed along the line defined by the constrained nodes.

Using MPC Type LINEAR

MPC type LINEAR is a standard method for mesh refinement of first-order elements. However, in Abaqus/Explicit it might be preferable to use a surface-based tie constraint (see Mesh Tie Constraints) for mesh refinement, particularly when one or more of the meshes to be constrained involve shell elements with thickness.

This MPC constrains each degree of freedom at node p to be interpolated linearly from the corresponding degrees of freedom at nodes a and b (see Figure 1).

Input Data

Give the nodes p, a, and b as shown in Figure 1.

Input File Usage

MPC
LINEAR, p, a, b

Abaqus/CAE Usage

Mesh refinement multi-point constraints are not supported in Abaqus/CAE.

Using MPC Type QUADRATIC

MPC type QUADRATIC is a standard method for mesh refinement of second-order elements. This MPC type is available only in Abaqus/Standard.

This MPC constrains each degree of freedom at node p (where p is either $p_{1}$ or $p_{2}$ ) to be interpolated quadratically from the corresponding degrees of freedom at nodes a, b, and c (Figure 2). For coupled temperature-displacement, coupled thermal-electrical-structural, or pore pressure elements, only the displacement degrees of freedom are constrained.

Input Data

Give the nodes p, a, b, and c as shown in Figure 2, where p is either $p_{1}$ or $p_{2}$ .

Input File Usage

MPC
QUADRATIC, p, a, b, c

Abaqus/CAE Usage

Mesh refinement multi-point constraints are not supported in Abaqus/CAE.

Using MPC Type BILINEAR

MPC type BILINEAR is a standard method for mesh refinement of first-order solid elements in three dimensions. This MPC type is available only in Abaqus/Standard.

This MPC constrains each degree of freedom at node p to be interpolated bilinearly from the corresponding degrees of freedom at nodes a, b, c, and d (Figure 3).

Input Data

Give the nodes p, a, b, c, and d as shown in Figure 3.

Input File Usage

MPC
BILINEAR, p, a, b, c, d

Abaqus/CAE Usage

Mesh refinement multi-point constraints are not supported in Abaqus/CAE.

Using MPC Type C BIQUAD

MPC type C BIQUAD is a standard method for mesh refinement of second-order solid elements in three dimensions. This MPC type is available only in Abaqus/Standard.

This MPC constrains each degree of freedom at node p to be interpolated by a constrained biquadratic from the corresponding degrees of freedom at the eight nodes a, b, c, d, e, f, g, and h (Figure 4). For coupled temperature-displacement, coupled thermal-electrical-structural, or pore pressure elements, only the displacement degrees of freedom are constrained.

Input Data

Give the nodes p, a, b, c, d, e, f, g, and h as shown in Figure 4.

Input File Usage

MPC
C BIQUAD, p, a, b, c, d, e, f, g, h

Abaqus/CAE Usage

Mesh refinement multi-point constraints are not supported in Abaqus/CAE.

Using MPC Types P LINEAR and T LINEAR

The P LINEAR MPC can be used in the QUADRATIC MPC for mesh refinement of second-order, fully coupled pore fluid flow-displacement elements.

The T LINEAR MPC can be used in the QUADRATIC MPC for mesh refinement of second-order, fully coupled temperature-displacement and fully coupled thermal-electrical-structural elements.

These MPC types are available only in Abaqus/Standard.

These MPCs constrain the pore pressure (P LINEAR) or temperature (T LINEAR) degree of freedom at node p to be interpolated linearly from the degrees of freedom at nodes a and b (Figure 5).

Input Data

Give the nodes p, a, and b as shown in Figure 5.

Input File Usage

Use the following option to define a P LINEAR MPC:

MPC
P LINEAR, p, a, b

Use the following option to define a T LINEAR MPC:

MPC
T LINEAR, p, a, b

Abaqus/CAE Usage

Mesh refinement multi-point constraints are not supported in Abaqus/CAE.

Using MPC Types P BILINEAR and T BILINEAR

The P BILINEAR MPC can be used in the C BIQUAD MPC for mesh refinement of pore fluid flow-displacement elements in three dimensions.

The T BILINEAR MPC can be used in the C BIQUAD MPC for mesh refinement of fully coupled temperature-displacement and fully coupled thermal-electrical-structural elements in three dimensions.

These MPC types are available only in Abaqus/Standard.

These MPCs constrain the pore pressure (P LINEAR) or temperature (T LINEAR) at node p to be interpolated bilinearly from the pore pressure or temperature at nodes a, b, c, and d (Figure 6).

Input Data

Give the nodes p, a, b, c, and d as shown in Figure 6.

Input File Usage

Use the following option to define a P BILINEAR MPC:

MPC
P BILINEAR, p, a, b, c, d

Use the following option to define a T BILINEAR MPC:

MPC
T BILINEAR, p, a, b, c, d

Abaqus/CAE Usage

Mesh refinement multi-point constraints are not supported in Abaqus/CAE.

MPCS for Connections and Joints

BEAM: Provide a rigid beam between two nodes to constrain the displacement and rotation at the first node to the displacement and rotation at the second node, corresponding to the presence of a rigid beam between the two nodes.
CYCLSYM^(S): Constrain nodes to impose cyclic symmetry in a model.
ELBOW^(S): Constrain two nodes of ELBOW31 or ELBOW32 elements together, where the cross-sectional direction, $a_{2}$ , changes (see Pipes and Pipebends with Deforming Cross-Sections: Elbow Elements).
LINK: Provide a pinned rigid link between two nodes to keep the distance between the two nodes constant. The displacements of the first node are modified to enforce this constraint. The rotations at the nodes, if they exist, are not involved in this constraint.
PIN: Provide a pinned joint between two nodes. This MPC makes the displacements equal but leaves the rotations, if they exist, independent of each other.
REVOLUTE^(S): Provide a revolute joint.
SLIDER: Keep a node on a straight line defined by two other nodes, but allow the possibility of moving along the line and allow the line to change length.
TIE: Make all active degrees of freedom equal at two nodes.
UNIVERSAL^(S): Provide a universal joint.
V LOCAL^(S): Allow the velocity at the constrained node to be expressed in terms of velocity components at the third node defined in a local, body axis system. These local velocity components can be constrained, thus providing prescribed velocity boundary conditions in a rotating, body axis system.

See About Connectors for element-based versions of several of these MPCs for connections and joints.

Using MPC Type BEAM

MPC type BEAM provides a rigid beam between two nodes to constrain the displacement and rotation at the first node to the displacement and rotation at the second node, corresponding to the presence of a rigid beam between the two nodes.

Input Data

Give the nodes a and b as shown in Figure 7.

Input File Usage

MPC
BEAM, a, b

Abaqus/CAE Usage

Use one of the following options:

Interaction module: Create Connector Section: select MPC as the Connection Category and Beam as the MPC Type

Interaction module: Create Constraint: MPC Constraint; select Beam as the MPC Type

Constraining a Beam Stiffener to a Shell

The general method of using a beam as a stiffener on a shell is to define the beam and shell elements with separate nodes. These nodes can then be constrained to each other using BEAM type MPCs.

A more economical way, when applicable, is to use the same node for the beam node and the shell node and then define the offset of the center of the cross-section of the beam in the beam section data. Figure 8 shows a T-shaped stiffener attached to a shell, using the I-beam cross-section. You can define this configuration by setting l (see Beam Cross-Section Library) equal to the distance between the node and the underside of the lower flange and setting the thickness of the top flange to zero. You can use this approach with all beam elements that use TRAPEZOID, I, CHANNEL, or ARBITRARY beam sections. Alternatively, you can define the offset directly as described in Using a Beam Section Integrated during the Analysis to Define the Section Behavior and Using a General Beam Section to Define the Section Behavior. You can use this approach for all beam cross-sections available in the beam cross section library (see Beam Cross-Section Library).

Thermal Expansion with BEAM MPC

In Abaqus/Standard a BEAM MPC can experience expansion due to a temperature increase. The magnitude of the expansion depends on the distance between the nodes of the MPC. The temperature change for computing the expansion is the average of the temperature change at both the nodes of the MPC. The temperature change at any node is the difference between the initial temperature of the node and the current temperature of the node. You must provide the value of the thermal expansion coefficient so that Abaqus/Standard can compute the expansion. Thermal expansion can be used only when temperature is a field variable.

Input File Usage

MPC, ALPHA=thermal_expansion_coeff
BEAM, a, b

Abaqus/CAE Usage

Thermal expansion with BEAM type MPCs is not supported in Abaqus/CAE.

Using MPC Type CYCLSYM

MPC type CYCLSYM is used to enforce proper constraints on the radial faces bounding a segment of a cyclic symmetric structure (see Figure 9). This MPC type is available only in Abaqus/Standard.

MPC type CYCLSYM imposes the cyclic symmetry by equating radial, circumferential, and axial displacement components (and rotations, if active) at the two nodes (a and b). The symmetry axis can be defined by the original coordinates of two additional nodes (c and d) that do not need to be connected to any element in the structure. Scalar degrees of freedom (such as temperature) are made equal.

Input Data

Give the nodes a, b, and (optionally) node c and/or d that define the axis of symmetry as shown in Figure 9. Node set names can be used instead of the nodes a and b. If neither c nor d is given, the global z-axis is taken to be the axis of cyclic symmetry. If only node c is given, the symmetry axis passes through c and is parallel to the global z-axis. Thus, node d is not needed in two-dimensional cases.

Input File Usage

MPC
CYCLSYM, a, b, c, d

Abaqus/CAE Usage

Cyclic symmetry multi-point constraints are not supported in Abaqus/CAE.

Using MPC Type ELBOW

MPC type ELBOW constrains two nodes of ELBOW31 or ELBOW32 elements together, where the cross-sectional direction, $a_{2}$ , changes (see Pipes and Pipebends with Deforming Cross-Sections: Elbow Elements). This MPC type is available only in Abaqus/Standard.

Input Data

Give the nodes a and b as shown in Figure 10.

Input File Usage

MPC
ELBOW, a, b

Abaqus/CAE Usage

Use one of the following options:

Interaction module: Create Connector Section: select MPC as the Connection Category and Elbow as the MPC Type

Interaction module: Create Constraint: MPC Constraint; select Elbow as the MPC Type

Using MPC Type LINK

MPC type LINK provides a pinned rigid link between two nodes to keep the distance between the nodes constant, as shown in Figure 11. The displacements of the first node are modified to enforce this constraint. The rotations at the nodes, if they exist, are not involved in this constraint.

Input Data

Give the nodes a and b as shown in Figure 11.

Input File Usage

MPC
LINK, a, b

Abaqus/CAE Usage

Use one of the following options:

Interaction module: Create Connector Section: select MPC as the Connection Category and Link as the MPC Type

Interaction module: Create Constraint: MPC Constraint; select Link as the MPC Type

Thermal Expansion with LINK MPC

In Abaqus/Standard a LINK MPC can experience expansion due to a temperature increase. The magnitude of the expansion depends on the distance between the nodes of the MPC. The temperature change for computing the expansion is the average of the temperature change at both the nodes of the MPC. The temperature change at any node is the difference between the initial temperature of the node and the current temperature of the node. You must provide the value of the thermal expansion coefficient so that Abaqus/Standard can compute the expansion. Thermal expansion can be used only when temperature is a field variable.

Input File Usage

MPC, ALPHA=thermal_expansion_coeff
LINK, a, b

Abaqus/CAE Usage

Thermal expansion with LINK type MPCs is not supported in Abaqus/CAE.

Using MPC Type PIN

MPC type PIN provides a pinned joint between two nodes. This MPC makes the global displacements equal but leaves the rotations, if they exist, independent of each other, as shown in Figure 12.

Input Data

Give the nodes a and b as shown in Figure 12.

Input File Usage

MPC
PIN, a, b

Abaqus/CAE Usage

Use one of the following options:

Interaction module: Create Connector Section: select MPC as the Connection Category and Pin as the MPC Type

Interaction module: Create Constraint: MPC Constraint; select Pin as the MPC Type

Using MPC Type REVOLUTE

This MPC type is available only in Abaqus/Standard.

A revolute joint is a joint in which relative rotation is allowed between two nodes about an axis that rotates during the motion (see Figure 13). The axis of the joint is defined in the initial configuration as the line from node b to node c. If these nodes are coincident, the axis is assumed to be the global z-axis. The rotation of the joint axis is that of node b.

The relative rotation in the joint is a single variable and is stored as degree of freedom 6 at node c. This degree of freedom can be used with other members in the model, but caution should be used because of the nonstandard use of degree of freedom 6. For example, a SPRING1 element (a spring to ground) might be attached to this degree of freedom. Since the degree of freedom measures a relative rotation, this spring would then be a torsional spring between nodes a and b.

The displacements at node a are not constrained by the REVOLUTE MPC to be the same as the displacements at node b. Thus, the joint definition must usually be completed either by using a PIN type MPC between nodes a and b or by using suitable stiffness members between these two nodes.

An example of a revolute joint and application of the REVOLUTE MPC is provided in Revolute MPC verification: rotation of a crank. See Revolute joint for more details on revolute joints.

Input Data

Give the nodes a, b, and c as shown in Figure 13. Degree of freedom 6 at node c defines the relative rotation between nodes a and b; therefore, this degree of freedom does not obey the standard convention for degrees of freedom in Abaqus.

Input File Usage

MPC
REVOLUTE, a, b, c

Abaqus/CAE Usage

Revolute joint multi-point constraints are not supported in Abaqus/CAE.

Using MPC Type SLIDER

MPC type SLIDER keeps a node on a straight line defined by two other nodes but allows the possibility of moving along the line and allows the line to change length.

When transitioning from multiple layers of solid elements to shells, it is often desirable to constrain the nodes on the free edge of the solid elements to remain in a straight line. (This constraint is consistent with shell theory.) The SLIDER MPC can perform this function without restraining the “thinning” behavior of the solid layers. The SS LINEAR MPC is then used to attach the shell element to this edge.

In Abaqus/Standard when a SLIDER MPC is used with one of the shell-solid MPCs—SS LINEAR, SS BILINEAR, or SSF BILINEAR—it must be given following the shell-solid MPCs.

Input Data

For each node p shown in Figure 14 and Figure 15, give the nodes p, a, and b for each line of nodes that should remain straight. For each node q shown in Figure 14, give the nodes q, c, and d, and so on for each line of nodes that should remain straight.

Input File Usage

MPC
SLIDER, p, a, b 
SLIDER, q, c, d

Abaqus/CAE Usage

Slider multi-point constraints are not supported in Abaqus/CAE.

Using MPC Type TIE

MPC type TIE makes the global displacements and rotations as well as all other active degrees of freedom equal at two nodes. If there are different degrees of freedom active at the two nodes, only those in common will be constrained.

MPC type TIE is usually used to join two parts of a mesh when corresponding nodes on the two parts are to be fully connected (“zipping up” a mesh). For example, when a mesh is generated on a cylindrical body, the solution at the nodes at 0° and those at 360° must be the same. This can be done either by renumbering the nodes on one of the mesh extremes or by using this MPC for each pair of corresponding nodes, as shown in Figure 16.

Input Data

Give the nodes a and b as shown in Figure 16.

Input File Usage

MPC
TIE, a, b

Abaqus/CAE Usage

Use one of the following options:

Interaction module: Create Connector Section: select MPC as the Connection Category and Tie as the MPC Type

Interaction module: Create Constraint: MPC Constraint; select Tie as the MPC Type

Using MPC Type UNIVERSAL

This MPC type is available only in Abaqus/Standard.

A universal joint is a joint in which relative rotation is allowed between two nodes, about two axes that are connected rigidly, and each of which rotates with the rotation of one end of the joint (see Figure 17). Such a joint might be used to couple two shafts that have an angular misalignment. The first axis of the joint, which is attached to node b, is defined in the initial configuration as the line from node b to node c. If these nodes are coincident, the axis is assumed to be the global z-axis. The second axis of the joint is at right angles to the first axis and is in the plane defined by the first axis and node d.

The relative rotations in the joint are stored as degree of freedom 6 at the nodes c and d. These degrees of freedom can be used with other members in the model, but caution should be used because of the nonstandard use of degree of freedom 6. For example, a SPRING1 element (a spring to ground) might be attached to one of these degrees of freedom. Since the degree of freedom measures a relative rotation, this spring would then be a torsional spring, restraining that component of relative rotation.

The displacements at node a are not constrained by the UNIVERSAL MPC to be the same as the displacements at node b. Thus, the joint definition must usually be completed either by using a PIN type MPC between nodes a and b or by using suitable stiffness members between these two nodes.

See Universal joint for more details on universal joints.

Input Data

Give the nodes a, b, c, and d as shown in Figure 17. Degrees of freedom 6 at nodes c and d define the relative rotation in the joint; therefore, these degrees of freedom do not obey the standard convention for degrees of freedom in Abaqus.

Input File Usage

MPC
UNIVERSAL, a, b, c, d

Abaqus/CAE Usage

Universal joint multi-point constraints are not supported in Abaqus/CAE.

Using MPC Type V LOCAL

This MPC type is available only in Abaqus/Standard.

As shown in Figure 18, MPC type V LOCAL constrains the velocity components associated with degrees of freedom 1, 2, and 3 at a first node (a) to be equal to the velocity components at a third node (c) along local, rotating directions. These local directions rotate according to the rotation at a second node (b). In the initial configuration, the first local direction is from the second to the third node of the MPC (from b to c, as indicated by the arrows in Figure 18), or it is the global z-axis if these nodes coincide. The other local directions are then defined by the standard Abaqus convention for such directions (see Conventions). In Figure 18 this MPC is applied to nodes d, e, and f in the same manner.

MPC type V LOCAL can be useful for defining a complex motion within a model. For example, the MPC can be used to model the steering of an automobile in a dynamic analysis for which the resulting inertial effects are of interest. See Local velocity constraint for more details on the local velocity constraint.

Input Data

Give the node whose velocity components are constrained (node a or d in Figure 18), the node whose rotation defines the rotation of the local directions (node b or e in Figure 18), and the node whose velocity components are in these local directions (node c or f in Figure 18). Nodes a and b (or d and e) can be the same.

Input File Usage

MPC
V LOCAL, a, b, c 
V LOCAL, d, e, f

Abaqus/CAE Usage

Local velocity component multi-point constraints are not supported in Abaqus/CAE.

MPCS for Transitions

SS LINEAR: Constrain a shell node to a solid node line for linear elements (such as S4, S4R, S4R5, C3D8, C3D8R, SAX1, and CAX4).
SS BILINEAR^(S): Constrain a shell node to a solid node line for edge lines on quadratic elements (such as S8R, S8R5, C3D20, C3D20R, SAX2, and CAX8).
SSF BILINEAR^(S): Constrain a midside node of a quadratic shell element (such as S8R and S8R5) to midface lines on 20-node bricks (such as C3D20 and C3D20R).

Modeling a Shell-to-Solid Element Transition

The SLIDER, SS LINEAR, SS BILINEAR, and SSF BILINEAR MPCs allow for a transition from shell element modeling to solid element modeling on a shell surface. This modeling technique can be used to obtain solutions at shell-solid intersections or other discontinuities, where the local modeling should use full three-dimensional theory but the other parts of the structure can be modeled as shells. The shell-to-solid submodeling capability (About Submodeling) and the surface-based shell-to-solid coupling constraint (Shell-to-Solid Coupling) can also be used to obtain more accurate solutions in such cases, with considerably less modeling effort.

In Abaqus/Standard the MPC usage assumes that the interface between the shell and solid elements is a surface containing the normals to the shell along the line of intersection of the meshes, so that the lines of nodes on the solid mesh side of the interface in the normal direction to the surface are straight lines. (Line a, $p^{1}$ , $p^{2}$ , …, b in Figure 14 and lines $p^{1}$ , $p^{2}$ , …, $p^{n}$ in Figure 19 to Figure 20 should be straight lines.) It also assumes that the nodes of the solid elements are spaced uniformly on the interface surface as indicated in Figure 14 and Figure 19 to Figure 20. For each shell node on the edge use MPC type SS LINEAR, SS BILINEAR, or SSF BILINEAR, as appropriate, to constrain the shell node to the corresponding line or face of solid element nodes through the thickness. Then, use a SLIDER MPC to constrain each interior node on the line through the thickness to remain on the straight line defined by the bottom and top nodes of that line. For an example, see Multi-point constraints.

The SS BILINEAR and SSF BILINEAR MPCs are not intended for use with the variable node solid elements (C3D27, C3D27H, C3D27R, and C3D27RH).

In Abaqus/Standard MPCs SS LINEAR, SS BILINEAR, and SSF BILINEAR eliminate all displacement components and two of the rotation components at the shell node, and the SLIDER MPC eliminates two displacement components at each interior solid element node in the interface. Therefore, any boundary conditions needed at the interface (such as those required when the shell/solid interface intersects a symmetry plane) should be applied only to the top and bottom nodes on the solid element side of the interface.

Using MPC Type SS LINEAR

MPC type SS LINEAR constrains a shell corner node to a line of edge nodes on solid elements for linear elements (S4, S4R, or S4R5; C3D8, C3D8R; SAX1; CAX4; etc.).

The constrained nodes need not lie exactly on these lines, but it is suggested that they be in close proximity to the lines for meaningful results.

Input Data

Give the shell node, S, then the list of nodes along the corresponding line through the thickness in the solid element mesh. In Abaqus/Explicit only two solid nodes can be given. Referring to Figure 19, in Abaqus/Standard give S, $p^{1}$ , $p^{2}$ , …, $p^{n}$ , and in Abaqus/Explicit give S, $p^{1}$ , $p^{n}$ , where $n \geq 2$ . The shell node number must be different from the solid mesh node numbers.

Input File Usage

In Abaqus/Standard use the following option:

MPC
 SS LINEAR, S,  $p^{1}$ ,  $p^{2}$ , …,  $p^{n}$

In Abaqus/Explicit use the following option:

MPC
 SS LINEAR, S,  $p^{1}$ ,  $p^{n}$

Abaqus/CAE Usage

Multi-point constraints for transitions are not supported in Abaqus/CAE.

Using MPC Type SS BILINEAR

MPC type SS BILINEAR constrains a corner node of a quadratic shell element (S8R, S8R5) to a line of edge nodes on 20-node bricks. This MPC type is available only in Abaqus/Standard.

The constrained node need not lie exactly on the line, but it is suggested that it be in close proximity to the line for meaningful results.

Input Data

Give the shell node, S, then the list of nodes along the corresponding line through the thickness in the solid element mesh. Referring to Figure 20, give S, $p^{1}$ , $p^{2}$ ,…, $p^{n}$ . The shell node number must be different from the solid mesh node numbers.

Input File Usage

MPC
SS BILINEAR, S,  $p^{1}$ ,  $p^{2}$ , …,  $p^{n}$

Abaqus/CAE Usage

Multi-point constraints for transitions are not supported in Abaqus/CAE.

Using MPC Type SSF BILINEAR

MPC type SSF BILINEAR constrains a midside node on a quadratic shell element (S8R, S8R5) to a line of midface nodes on solid 20-node bricks. This MPC type is available only in Abaqus/Standard.

The constrained node need not lie exactly on the line, but it is suggested that it be in close proximity to the line for meaningful results.

Input Data

Give the shell node, S, then the list of nodes on the solid face, in the order $p^{1}$ , $p^{2}$ ,…, $p^{n}$ as shown in Figure 21.

Input File Usage

MPC
SSF BILINEAR, S,  $p^{1}$ ,  $p^{2}$ , …,  $p^{n}$

Abaqus/CAE Usage

Multi-point constraints for transitions are not supported in Abaqus/CAE.