Choosing FEA Contact Settings: A Practical Comparison Guide

Open ten contact definitions across ten different projects and you'll usually find the same four settings copied forward from whichever model was open last: same constraint method, same pairing scheme, same friction value, same separation behaviour. Nobody re-decided any of it. That's the problem with FEA contact settings — there are four genuinely separate decisions stacked into what looks like one dialog box, and treating them as one decision is how a bearing seat ends up modelled the same way as a bonded bracket. We're not talking about meshing or material cards here. We're talking about the four choices that sit underneath almost every contact interaction in Abaqus or Ansys: how the constraint is enforced, how surfaces are paired up, whether separation is even allowed, and how friction actually behaves. Get any one of them wrong and the rest of the model can converge cleanly and still be wrong. ## Lagrange multiplier, penalty, and augmented Lagrangian — what you're actually trading off Abaqus gives you three ways to enforce a "thou shalt not penetrate" constraint, and they are not interchangeable defaults. The direct (Lagrange multiplier) method enforces the constraint exactly — zero penetration, no approximation. It's the textbook-correct answer, and it's also the one most likely to give you convergence trouble on a contact-heavy model, because exact constraints add equations that can over-constrain a node already pinned by something else. The penalty method is the workhorse default for surface-to-surface and general contact under a "hard" pressure-overclosure relationship. It treats contact as a very stiff spring: small penetration is allowed, the stiffness pushes back hard enough that the penetration stays small, and in exchange you get a method that converges far more reliably than the direct method. The cost is that "small" penetration is a number you're trusting, not zero. The augmented Lagrangian method is the practical middle ground. It starts from the same stiff-spring approximation as penalty, but adds an outer iteration: if a node penetrates past the tolerance (0.1% of the characteristic interface length, by default), the contact pressure gets augmented and the solver iterates again until the penetration is actually small. You pay for that with more iterations. What you get back is penetration control close to the direct method's accuracy without its convergence fragility — which is exactly why it's worth reaching for deliberately on interfaces where penetration error would matter, like a precision bearing fit, rather than leaving every contact pair on whatever the software defaulted to. ## General contact or surface-to-surface — this is a setup decision, not a software preference General contact and surface-to-surface contact pairs solve the same underlying problem in opposite directions, and which one is right depends on the assembly, not on a house style. General contact scans the whole model and figures out who's touching whom — node-to-face, edge-to-edge, self-contact, deformable-to-rigid, all of it, without you naming a single pair. That's genuinely useful on a complex assembly where enumerating every interaction by hand would be its own source of error, or wherever self-contact is a real possibility (a cable, a snap-fit clip, a sheet-metal part that can fold back on itself). The cost is that the algorithm has to keep monitoring the entire model for new contact status, and on a large assembly that shows up directly in solve time. Surface-to-surface contact pairs ask you to name the interfaces explicitly. More setup effort, but the solver only has to track exactly what you told it to track, which is faster and gives you tighter control over contact pressure distribution and stiffness on the interfaces that actually matter to the result. We default to surface-to-surface for the handful of fastener and bearing interfaces that drive a stress or fatigue result, and reach for general contact when the question is whether something touches something else at all, not how accurately we can resolve the pressure once it does. ## Bonded, no separation, frictional, or rough — the FEA contact settings that govern separation This is the decision that gets skipped most often, because "frictional, 0.2" feels like a safe default. It isn't always. Bonded contact ties two surfaces together completely — no separation, no sliding, in either direction. It's linear, it solves in one iteration, and it's correct for a weld, an adhesive joint at full cure, or any interface you genuinely intend to be permanent. It is not correct for a bolted joint you're hoping stays clamped, because bonded contact can't tell you if it doesn't. No separation allows sliding in the tangential direction but locks the normal direction — the surfaces can't pull apart, but they can move across each other without friction. This is the right call for a press fit or a pin that you know stays engaged under every load case in the analysis, where you want the normal constraint without pretending the interface is glued. Frictionless and frictional contact are where most real joints belong: separation is allowed in the normal direction, sliding is allowed in the tangential direction, and frictional contact adds resistance proportional to a coefficient of friction. Both are nonlinear and both need multiple iterations, because the solver has to work out where contact is actually closed at each step rather than assuming it from the start. Rough contact is the extreme case of frictional contact — effectively an infinite friction coefficient, separation still allowed, but no sliding once contact is closed. It's the right model for a surface finish specified to prevent slip entirely, and the wrong model for anything where you actually expect relative motion, because it will hide a slip failure mode instead of showing it to you. The decision that matters isn't which of these five sounds most "realistic." It's which one matches what the interface is actually allowed to do under the loads you're applying — and that's a question about the joint, not about the contact menu. ## Pressure-dependent friction — when a single coefficient stops being good enough A constant coefficient of friction is a reasonable assumption for a lot of contact, and a genuinely wrong one for some of it. Real interfaces — especially anything with surface coatings, elastomers, or high contact pressure variation across the interface — have a friction coefficient that changes with normal pressure, not a fixed number from a materials handbook. Both Abaqus and Ansys let you define friction as a function of contact pressure instead of a constant: in Ansys, through the TB,FRIC material command, which accepts pressure (or temperature, or sliding velocity) as a field variable and interpolates between the data points you give it. The practical reason to bother is that the tangential contact stiffness gets recalculated from the current pressure and current friction coefficient at every iteration — so on an interface where contact pressure varies a lot across the joint (a bolt head bearing surface is the obvious case), a single average friction value can be quietly wrong across most of the interface even if it's right at one point. We reach for pressure-dependent friction on exactly that kind of joint: anywhere the contact pressure distribution itself is part of the question we're answering, not just an input we're assuming. ## How we actually decide this on a project None of these four choices is independent of the other three. A bonded assumption makes the constraint method almost irrelevant, because there's no penetration question to enforce carefully. A general contact model across a whole assembly with twenty interfaces is a bad place to also turn on pressure-dependent friction everywhere, because you'd be spending modelling effort on interfaces that were never going to drive the result. The judgment call is sequencing: decide what the joint is actually allowed to do first, then pick the pairing scheme that matches how many of those joints actually need individual attention, then reach for augmented Lagrangian or pressure-dependent friction only on the specific interfaces where the simpler default would be wrong. That sequencing — not any single setting — is what separates a contact model that happens to converge from one that's actually telling you something true about the joint. ## The bottom line FEA contact settings are four decisions wearing one dialog box's clothes: how the constraint is enforced, how surfaces get paired, what the interface is actually allowed to do, and whether friction is a constant or a function of pressure. Copying last project's settings forward answers none of them — it just hides the fact that nobody asked the question this time. Working through which contact settings actually fit your next assembly? Get in touch.