When a degree of freedom is subjected to multiple constraints, overconstraint occurs. Overconstraint can be caused by the combination of the following constraints within the model:
Overconstraint may result in convergence difficulties or inaccurate solutions. In order to prevent this problem, the program tries to detect and eliminate overconstraints automatically. You can verify the eliminated constraints during postprocessing.
At the beginning of a contact analysis, warning messages may appear outlining the cause of the potential overconstraints. Use the CNCHECK,DETAIL command to identify the overconstraints indicated by the messages. Manually remove as many unnecessary constraints as possible.
Some overconstraints occur only during the solution due to new deformed configurations or due to changes in contact status. The program eliminates a limited set of overconstraints detected during solution; appropriate messages are issued when this occurs. For MPC-based contact pairs, the contact statuses (contact result item STAT) are set to negative values if one or more contact constraints are removed. STAT is set to -3 for bonded contact; STAT is set to -2 for no-separation contact. Be aware that, due to complexities, certain overconstraints may not be easily detected.
The way the program removes the overconstraint is not unique. The order of the redundant constraints will influence how they are removed (the first encountered is kept, the next is removed). You should always verify the modified model carefully. You can list and display the contact status using STAT as a contact result item for the PLESOL and PRESOL commands; for example:
PLESOL,CONT,STAT