Product: Abaqus/Standard
There are features in Abaqus that, when used in combination, may overconstrain a model. Several of these combinations are detected and resolved by Abaqus automatically, while others are only identified and warning or error messages are issued. By default, overconstraint checking is performed.
A surface-based tie constraint joins two surfaces by eliminating the nodes on the slave surface with multi-point constraints. Multiple surface-based tie constraint definitions may intersect. At these intersections the slave nodes are involved in an overconstraint. Only one surface-based tie constraint is needed to eliminate a slave node. Additional surface-based tie constraint definitions are not needed.
In these tests intersecting surface-based tie constraint definitions are used such that one or more slave nodes are included in more than one surface-based tie constraint pair. Only one surface-based tie constraint should be enforced at any slave node.
These tests verify that Abaqus properly removes the consistent overconstraints. Warning or error messages in the data file confirm that all overconstraints are removed or identified.
C3D8 element test for three-way *TIE intersection.
CAX4 element test.
B21 element test, T-junction.
S4 element test, T-junction.
S8R and B32element test with three-way *TIE intersection.
A rigid body constraint eliminates all the degrees of freedom at the nodes of the rigid body in favor of the degrees of freedom at the reference node. Therefore, any surface-based tie constraints used to tie surfaces inside a single rigid body or between rigid bodies is a consistent overconstraint. In this case the surface-based tie constraint is ignored. Similarly, if the surface-based tie constraint is used to tie a rigid surface to a deformable surface and the surface on the rigid body is the slave surface, a consistent overconstraint exists for the tie nodes on the rigid body. If possible, Abaqus reverses the master/slave pair.
In these tests the surface-based tie constraints tie surfaces within a rigid body, between rigid bodies, or between a slave rigid body and a master deformable body.
These tests verify that Abaqus properly removes the consistent overconstraint. Warning messages in the data file confirm that the consistent overconstraints are removed.
*TIE within a rigid body in two dimensions.
*TIE within a rigid body in three dimensions.
*TIE between rigid bodies in two dimensions.
*TIE between a slave rigid surface and a deformable master surface in two dimensions.
*TIE between rigid bodies in three dimensions.
*TIE between a slave rigid surface and a deformable master surface in three dimensions.
If the rigid body constraint refers to nodes or elements that are already part of a rigid body, the common nodes will be involved in a consistent overconstraint.
In these tests rigid body constraints are used to create a single rigid body from other individual rigid bodies or to define a rigid body that includes a part of another rigid body.
These tests verify that Abaqus properly removes the consistent overconstraints. Warning messages in the data file confirm that the consistent overconstraints are removed.
*RIGID BODY intersection in two dimensions.
*RIGID BODY intersection in three dimensions.
A surface-based tie constraint eliminates the degrees of freedom at the slave nodes using multi-point constraints. If a boundary condition is imposed on the slave node, an overconstraint results.
In these tests two surfaces are tied and boundary conditions are assigned to the slave nodes such that a consistent overconstraint is created.
These tests verify that Abaqus properly removes the consistent overconstraints. Warning messages in the data file confirm that the consistent overconstraints are removed.
Rigid body constraints create a rigid body that eliminates the degrees of freedom at all the nodes on the rigid body in favor of the degrees of freedom at the reference node. If a boundary condition is defined at one of the eliminated nodes, an overconstraint results.
In these tests a rigid body is defined and boundary conditions are assigned to the eliminated nodes on the rigid body such that a consistent overconstraint is created.
These tests verify that Abaqus properly removes the consistent overconstraints. Warning messages in the data file confirm that the consistent overconstraints are removed.
*RIGID BODYand *BOUNDARY in two dimensions.
*RIGID BODY and *BOUNDARY in three dimensions.
If connector elements are used to connect nodes within a rigid body, a consistent overconstraint is introduced since the nodes at both ends of the connector element already have a rigid constraint. In this case the connector element should be removed. If multiple connector elements are used between rigid bodies, all kinematic constraints beyond three translational constraints and three rotational constraints (in three dimensions) or two translational constraints and one rotational constraint (in two dimensions) are overconstraints. In the case when the connector elements produce a consistent overconstraint between the two rigid bodies, all the connector elements are removed and a connector element of type BEAM is attached between the two rigid body reference nodes.
In these tests connector elements are connected either between nodes within a rigid body or between nodes on different rigid bodies.
These tests verify that Abaqus properly removes the consistent overconstraints. Warning messages in the data file confirm that the consistent overconstraints are removed.
Connector elements between rigid bodies in two dimensions.
Connector elements between rigid bodies in three dimensions.
Connector elements inside a rigid body in two dimensions.
Connector elements inside a rigid body in three dimensions.
Rigid body constraints eliminate all the degrees of freedom at the nodes belonging to the rigid body. If coupling constraints are also used, an overconstraint may occur. Abaqus/Standard will automatically eliminate the unnecessary coupling constraints.
These tests verify that Abaqus properly removes the consistent overconstraints. Warning or error messages in the data file confirm that these overconstraints are removed or identified.
The *RIGID BODY and *COUPLING options with the *DISTRIBUTING option.
The *RIGID BODY and *COUPLING options with the *KINEMATIC option.
A surface-based tie constraint eliminates the degrees of freedom at the slave node through multi-point constraints. If the tied surfaces intersect a surface where a contact interaction is defined (normal contact with or without Lagrange friction), the contact interactions at the slave node are overconstraints.
In these tests surface-based tie constraints intersect surfaces with contact interactions.
These tests verify that Abaqus properly removes the consistent overconstraints. Warning messages in the data file confirm that the consistent overconstraints are removed.
Contact and *TIE in two dimensions.
Contact and *TIE in three dimensions.
Contact interactions and prescribed boundary conditions may lead to overconstraints if either normal contact with the default “hard contact” formulation or Lagrange frictional contact is used.
In these tests hard contact or Lagrange friction is defined and boundary conditions are applied to contact slave nodes.
These tests verify that Abaqus properly removes the consistent overconstraints. Warning messages in the data file confirm that the consistent overconstraints are removed.
Normal contact and *BOUNDARY in two dimensions.
Normal contact and *BOUNDARY in three dimensions.
Lagrange frictional contact and *BOUNDARY in two dimensions.
Lagrange frictional contact and *BOUNDARY in three dimensions.