...With other applied boundary conditions or other contact or symmetry regions. This may reduce solution accuracy. For MPC formulation based remote boundary conditions, you can set Relaxation Method property to Yes to eliminate over constraints. Tip: You can graphically display FE Connections from the Solution Information Object. Refer to Troubleshooting in the Help System for more details.
During solution it was found that one or more contact pairs using MPC (multi point constraint) or Lagrange Multiplier based contact formulation overlaps with another contact region or boundary condition. The same is true for remote boundary conditions overlapping with another contact region or boundary condition.
Due to the fact that MPC formulation can cause over constraint if applied to the same nodes more than once, the program may have not been able to completely bond the desired entities together. You may check the solution output located in the Worksheet of a Solution Information object to determine which pairs and nodes are affected by this condition. Specifically this can happen when:
Due to the fact that MPC formulation can cause over constraint if applied to the same nodes more than once, the application may have not been able to completely bond the desired entities together. For MPC formulation-based remote boundary conditions (Formulation property set to ), you can set Relaxation Method property to to eliminate over constraints. If this does not resolve the over-constraint issue, you may check the solution output located in the Worksheet of a Solution Information object to determine which pairs and nodes are affected by this condition. Specifically this can happen when:
A contact pair entity (either an edge or face) also has a Dirichlet (prescribed displacement/temperature) boundary condition applied to it. In this case, the MPC constraints will not be created at nodes that have prescribed conditions and may possibly causing parts to lose contact. Sometimes this warning may be disregarded in cases such as a large face with a fixed support at one edge and a contact pair on another. If it is determined that overlap does indeed exist, consider relocating the applied support or using a formulation other than MPC.
Two MPC contact pairs share topology (such as a face or an edge). Again it is possible for one or both of these pairs to lose contact. This message may especially occur when edge/face contact is automatically generated by the program because often 2 complementary contact pairs (that is, edge part 1/face part 2 and edge part 2/face part 1) are created. Often in this case the message can be ignored after verifying result correctness and if necessary, deleting/suppressing one of the inverse pairs. This condition may also occur when 1 part (typically a surface body), is being contacted by 2 or more parts in the same spatial region. In this case it is possible for one or more of the parts to lose contact. Consider reducing the Pinball Radius to avoid overlap or changing one or more of the regions in question to use a contact formulation other than MPC.
When MPC contact is used to connect rigid bodies and joints, the overconstraint situation can sometimes occur.
When Remote Boundary conditions overlap the Low/High Regions of the Periodic/Cyclic symmetry regions, you may experience an overconstraint situation. In a severe situation, the application may terminate.
Note: For bonded contacts involving shell bodies, the setting for the Formulation property internally selects the MPC formulation. If these contacts have overlapping geometry or mesh scoping with other connections or boundary conditions it can lead to overconstraint. You can either flip the contact/target scoping or use any formulation other than MPC to resolve this issue.