Constraint Conditions (Constraint) — CAE Glossary
What are Constraint Conditions?
So constraint conditions are basically about "deciding where things don't move"?
Roughly speaking, yes. In FEM, each node has a maximum of 6 degrees of freedom (DOF: 3 translational + 3 rotational), and the most basic constraint is fixing unwanted directions to zero. For example, if a steel plate is bolted to a wall at one end, all DOFs at that end are constrained — this is called complete fixation (Encastre).
Are there different types of constraints beyond just "not moving"?
Yes, broadly there are three categories. (1) SPC (Single Point Constraint): Fix a specific DOF at a specific node to a fixed value (usually zero). Simplest type. (2) MPC (Multi-Point Constraint): Relate displacements of multiple nodes through equations. RBE2 and RBE3 belong here. (3) Symmetry and Anti-Symmetry Constraints: Use model symmetry to reduce computational load. They all work as different ways to impose constraints on the global stiffness equation $[K]\{u\} = \{F\}$.
DOF Constraint Basics
Mathematically, what happens when you constrain a DOF?
It's essentially removing rows and columns from the global stiffness equation corresponding to constrained DOFs. For example, if you specify node $i$'s X-direction displacement $u_i = 0$, you zero out the corresponding row and column in $[K]$, put a large value on the diagonal, or delete those rows and columns entirely. In Nastran this is the SPC card; in Abaqus it's Boundary Conditions like "ENCASTRE" or "PINNED".
What's the difference between ENCASTRE and PINNED?
ENCASTRE constrains all 6 DOFs — complete fixation. PINNED constrains only the 3 translational DOFs and allows rotation — it's a pin support. In beam analysis, comparing a cantilever (ENCASTRE at one end) to a simply supported beam (PINNED at one end) is a common practical pattern.
Rigid Body Motion and Insufficient Constraints
My senior told me "insufficient constraints cause rigid body motion and the calculation fails." What exactly is rigid body motion?
Rigid body motion (RBM) is when the entire structure translates or rotates without deformation. In 3D space there are 6 rigid body modes: 3 translational directions (X, Y, Z) and 3 rotational directions (Rx, Ry, Rz). If these are not constrained, $[K]$ becomes singular, the inverse cannot be computed, and the solver throws an error.
So you need to constrain at least 6 DOFs?
In principle, yes. But how you choose those 6 matters. Constraining all 6 DOFs at a single point concentrates reaction forces and creates unrealistic local stresses. In practice, we often use the "1-2-3 method": Point 1 fixes all 3 translational directions, Point 2 fixes 2 rotational directions, Point 3 fixes the remaining rotational direction. This distributes reaction forces and mitigates local stress problems.
What kind of error messages appear?
Typical Nastran errors: "FATAL: MATRIX IS SINGULAR" or "MECHANISM DETECTED". Abaqus: "NUMERICAL SINGULARITY" or "ZERO PIVOT". When you see these, the first priority is checking constraints. Also, in Nastran you can use PARAM,BAILOUT,-1 to output results despite errors, and viewing the displacement animation will immediately show which directions have rigid body motion.
Symmetry Boundary Conditions
I heard you can use half the model with symmetry boundary conditions. How does that work?
Suppose the YZ plane is your symmetry plane. You constrain the nodes on that plane with zero displacement perpendicular to it ($u_x = 0$) and zero rotation within the plane ($\theta_y = 0, \theta_z = 0$). This is mathematically equivalent to having the mirror image model on the other side. If your model size is halved, computation time drops to roughly 1/4 to 1/8 (memory also halves).
Is there anti-symmetry too?
Yes. For anti-symmetry, you constrain displacements parallel to the symmetry plane while leaving perpendicular displacement free — the opposite of symmetry. Used for cases like torsion on a symmetric beam. But anti-symmetry only works if both geometry and loading are anti-symmetric. If geometry is symmetric but loading isn't, you can't use it — that's a common mistake.
MPC (Multi-Point Constraints)
"MPC" means "Multi-Point Constraint," right? What does it do?
MPC defines an equation relating displacements across multiple nodes. General form:
$$\sum_{j} A_j \cdot u_j = 0$$
where $A_j$ are coefficients and $u_j$ are DOFs. For example, "X-displacement at node 1 equals X-displacement at node 2" is $u_1 - u_2 = 0$, so $A_1 = 1, A_2 = -1$. Practically used for: connecting mismatched meshes, modeling bolted joints, representing rigid zones. Very broad applicability.
What should you watch out for when setting up MPCs?
The most common mistake is "over-constraint" — same DOF constrained by both SPC and MPC creates a contradiction and causes solver errors or silently wrong results. Also critical is choosing dependent vs. independent nodes correctly. If you make a loaded node dependent, the force may not transfer correctly. Pay attention to this.
Difference Between RBE2 and RBE3
I don't quite grasp the RBE2 vs. RBE3 difference…
This is where nearly all FEM beginners get confused, so let me clarify carefully.
RBE2 (Rigid Body Element, Type 2) is a rigid link. One independent node controls multiple dependent nodes that follow it exactly. If the independent node moves, all dependent nodes move the same way. It adds stiffness. Used for modeling bolted holes and mass attachments.
RBE3 is a load distribution element. One dependent node's displacement is a weighted average of multiple independent nodes. Critically, it does NOT add stiffness. Used to collect distributed loads at a single point or find representative values.
Wait — RBE2 adds stiffness but RBE3 doesn't? How does that affect the results?
Consider a hole surrounded by nodes. Connecting them to the center with RBE2 makes the hole completely rigid — far stiffer than a real bolted joint. With RBE3, you just distribute loads without adding artificial stiffness; the hole can still deform freely.
A common mistake: using RBE2 where RBE3 should go, resulting in overly high local stiffness and unrealistic stresses. The rule: "Are you transmitting force (use RBE2) or distributing it (use RBE3)?"
Practical Tips
What's most important when setting up constraint conditions?
Three things stand out.
First: Physical realism. Constraints must faithfully represent how the real structure is supported. Bolted to a wall = ENCASTRE; bearing support = constrain only one direction. Over-constraining gives artificially low stress (unsafe), under-constraining gives no solution at all.
Second: Always check reaction forces. After solving, verify constraint reactions sum to applied forces and that no single constraint point shows unrealistic values. This catches most constraint mistakes.
Third: Constraint influence zone. Stress concentrations occur near constraints, so keep constraints away from regions you're evaluating. Saint-Venant's principle: effects decay 2–3 characteristic lengths away from the constraint.
Related Terms
- SPC (Single Point Constraint): Fixes one specific DOF at one node to a fixed value
- MPC (Multi-Point Constraint): Relates DOFs across multiple nodes via equations
- RBE2: Rigid link element. Dependent nodes follow independent node. Adds stiffness.
- RBE3: Load distribution element. Dependent node motion is weighted average of independent nodes. Does not add stiffness.
- DOF (Degree of Freedom): Independent motion components at a node
- Rigid Body Motion: Translation or rotation without deformation. Occurs with insufficient constraints.
- Symmetry Boundary Condition: Constraining perpendicular translation and in-plane rotation on a symmetry plane to use a half-model
- Saint-Venant's Principle: Local details of loads/constraints don't affect distant regions
Precise understanding of CAE terminology is the foundation of team communication. — Project NovaSolver supports engineer learning.
Share your real-world constraint challenges with us
Project NovaSolver tackles the problems CAE engineers face daily — setup complexity, computational cost, result interpretation. Your practical experience drives better tools.
Contact (Coming Soon)