There are three methods available for extracting the reaction forces across a contact region in WB-Mechanical:
- Contact(Underlying Element)
- Contact (Contact Element)
- Target (Underlying Element)
When you choose ‘Contact(Underlying Element)’, the code is selecting the contact elements associated with that region, selecting nodes attached to the selected contact, and then selecting elements attached to the selected nodes before calculating the reaction.
Below is an equivalent APDL command script, where “cid1” is a parameterized contact element type number for the region of interest.
*****************
ESEL,s,type,,cid1
NSLE,s
ESLN,s
NFORCE
*****************
When you choose ‘Contact (Contact Element)’, the code is only selecting the contact elements and executing “NFORCE,cont”
Below is an equivalent APDL command script.
*****************
ESEL,s,type,,cid1
NFORCE,cont
*****************
The ‘Target (Underlying Element)’ option is similar to the first except we select the Target elements (Type=tid1) instead of the contact elements. Below is an equivalent APDL command script.
*****************
ESEL,s,type,,tid1
NSLE,s
ESLN,s
NFORCE
*****************
The availability of these reaction options is governed by the MISC option of the OUTRES command.
(Refer to on-line documentation: // Mechanical User Guide // Using Results // Structural Results // Structural Probes // Reactions: Forces and Moments for more details.)
Often all three methods produce the same calculated reaction.
Sometimes they will not agree because either the contact and/or the target surfaces share nodes with other constraints or other contact regions.
When this happens, one or more of the methods will calculate a force summation that represents the load transmitted across the contact region in question plus other loads from other sources. The overall result of the FEA model is not necessarily wrong, but these probed force calculations are no longer representing only the load across the contact region of interest. The first suggested workaround is to try to employ a strategically tighter trim tolerance to eliminate this unwanted force bleed off. Trim will remove both contact and target elements from respective surfaces that are separated by a distance larger than the user defined tolerance. In some cases, the default tolerance might be too large or perhaps Trim technology is turned off altogether.
Note, for Trim contact set to “Program Controlled”, it will be off for manually created pairs and if large deflection is ON (for models created in R14.5). If Trim options are not successful or not practical, you might need to consider a change to the way the model is constrained or a change in the contact regions definitions.
What happens if there are no shared constraints and the ‘Contact (Contact Element)’ option does not agree with the other two? The question to ask in this circumstance — Is this problem being run as small deflection with linear contact? If so, does the contact pressure profile look reasonable for the given load? If it does not look reasonable or you are not sure, try turning on large deflection and re-running the analysis. It is important to understand that the ‘Contact (Contact Element)’ extraction option is using the contact pressure profile integrate over the contact surface to calculate the overall reaction force. Hence, this calculation is only as accurate as the accuracy of contact pressure profile. If it is not really a large deflection application and you are not interested in running multiple iterations to improve the contact pressure profile, you could switch to MPC formulation. This will block the ‘Contact (Contact Element)’extraction method altogether.
The post Understanding Contact Reaction Probes in ANSYS Mechanical appeared first on ANSYS.