The following restrictions and guidelines apply when using the internal MPC approach.
To prevent overconstraint, displacement boundary conditions and other constraint equations or coupling equations (ideally) should not be applied on the contact nodes for solid-solid, shell-shell, and shell-solid assemblies, or for rigid surface constraints and coupling constraints.
The Sparse and PCG solvers are recommended to solve models with constraint equations.
The MPC-based algorithm must be used with nodal detection (KEYOPT(4) = 1, 2, or 3) for CONTA171, CONTA172, CONTA173, and CONTA174. If nodal detection is not set, the program issues a warning message and automatically sets KEYOPT(4) = 2.
MPC no-separation contact (KEYOPT(12) = 4) may cause a discontinuity when contact nodes slide from one target segment to another. However this is not the case for MPC bonded contact (KEYOPT(12) = 5 or 6).
The internal MPC option does not support rigid-flexible contact when rigid surfaces are modeled by any primitive segments (such as circle, cylinder, cone, or sphere).
The shell-solid assembly is usually used for the case where the solid mesh is fine with respect to the shell thickness. The shell-solid interface should be located in a region of the structure where shell theory is valid for an approximation. The accuracy of local stresses near the shell-solid interface (at least within the shell thickness range) is not guaranteed. We recommend you include at least two solid elements along the layer of the shell-solid interface.
Using the force-distributed constraint type of MPC with a large number of contact nodes can result in large and dense submatrices for the global stiffness matrix. This may significantly increase the peak memory required during element stiffness assembly. Consider reducing the number of contact nodes if real memory or virtual memory is limited.
The force-distributed constraint creates internal constraint equations such that the motion of the pilot node is the average of the contact nodes. For the rotations, a least-squares approach is used to define the "average rotation" at the pilot node from the translations of the contact nodes. If the contact nodes are colinear, then one of the rotations on the pilot node that is parallel to the colinear direction can not be determined in terms of the translations of the contact nodes. Therefore, the associated moment component on the pilot node in that direction can not be transmitted. When this case occurs, a warning message is issued.
The contact related postprocessing items (ETABLE items, PRESOL,CONT, etc.) are not supported for the internal MPC option.
MPC contact only generates internal constraint equations. It does not
calculate element internal force and stiffness matrices. Therefore, during
postprocessing the option ITEM = CONT is not valid on
the PRNLD, NFORCE, and
FSUM commands.
You can use the CELIST command to list the internally-generated constraint equations associated with MPC contact . You can also use CELIST to convert the internal constraint equations to external constraint equation after a SOLVE command has been issued. (See CELIST for details.)
MPC contact generates constraint equations that can include constant terms. These terms are included on the right hand side of the system equation. Thus, they are scaled by the LVSCALE command when it is used in a mode superposition analysis. These terms are considered as harmonically varying loads when included in a harmonic analysis.