Products: ABAQUS/Standard ABAQUS/Explicit ABAQUS/CAE
Boundary conditions:
can be used to specify the values of all basic solution variables (displacements, rotations, warping amplitude, fluid pressures, pore pressures, temperatures, electrical potentials, normalized concentrations, or acoustic pressures) at nodes;
can be given as “model” input data (within the initial step in ABAQUS/CAE) to define zero-valued boundary conditions; and
can be given as “history” input data (within an analysis step) to add, modify, or remove zero-valued or nonzero boundary conditions.
Only zero-valued boundary conditions can be prescribed as model data (i.e., in the initial step in ABAQUS/CAE). You can specify the data using either “direct” or “type” format. As described below, the “type” format is a way of conveniently specifying common types of boundary conditions in stress/displacement analyses. “Direct” format must be used in all other analysis types.
For both “direct” and “type” format you specify the region of the model to which the boundary conditions apply and the degrees of freedom to be restrained. (See “Conventions,” Section 1.2.2, for the degree of freedom numbers used in ABAQUS.)
Boundary conditions prescribed as model data can be modified or removed during analysis steps.
| ABAQUS/CAE Usage: | Load module: Create Boundary Condition: Step: Initial |
You can choose to enter the degrees of freedom to be constrained directly.
| Input File Usage: | Either a single degree of freedom or the first and last of a range of degrees of freedom can be specified. |
*BOUNDARY node or node set, degree of freedom *BOUNDARY node or node set, first degree of freedom, last degree of freedom For example, *BOUNDARY EDGE, 1 indicates that all nodes in node set EDGE are constrained in degree of freedom 1 ( EDGE, 1, 4 indicates that all nodes in node set EDGE are constrained in degrees of freedom 1–4 ( |
| ABAQUS/CAE Usage: | Load module: Create Boundary Condition: Step: Initial: Displacement/Rotation, Velocity/Angular velocity, or Acceleration/Angular acceleration: select regions and toggle on the degree or degrees of freedom |
The type of boundary condition can be specified instead of degrees of freedom. The following boundary condition “types” are available in both ABAQUS/Standard and ABAQUS/Explicit:
XSYMM Symmetry about a plane 
(degrees of freedom 
).
YSYMM Symmetry about a plane 
(degrees of freedom 
).
ZSYMM Symmetry about a plane 
(degrees of freedom 
).
ENCASTRE Fully built-in (degrees of freedom 
).
PINNED Pinned (degrees of freedom 
).
XASYMM Antisymmetry about a plane with (degrees of freedom 2, 3, 4 
).
YASYMM Antisymmetry about a plane with (degrees of freedom 1, 3, 5 ).
ZASYMM Antisymmetry about a plane with (degrees of freedom 1, 2, 6 ).
Caution: When boundary conditions are prescribed at a node in an analysis involving finite rotations, at least two rotation degrees of freedom should be constrained. Otherwise, the prescribed rotation at the node may not be what you expect. Therefore, antisymmetry boundary conditions should generally not be used in problems involving finite rotations.
NOWARP Prevent warping of an elbow section at a node.
NOOVAL Prevent ovalization of an elbow section at a node.
NODEFORM Prevent all cross-sectional deformation (warping, ovalization, and uniform radial expansion) at a node.
For example, applying a boundary condition of type XSYMM to node set EDGE indicates that the node set lies on a plane of symmetry that is normal to the X-axis (which will be the global X-axis or the local X-axis if a nodal transformation has been applied at these nodes). This boundary condition is identical to applying a boundary condition using the direct format to degrees of freedom 1, 5, and 6 in node set EDGE since symmetry about a plane X=constant implies 
, 
, and 
.
Once a degree of freedom has been constrained using a “type” boundary condition as model data, the constraint cannot be modified by using a boundary condition in “direct” format as model data; modifying a constraint in such a way will only produce an error message in the data (.dat) file indicating that conflicting boundary conditions exist in the model data.
| Input File Usage: | *BOUNDARY node or node set, boundary condition type |
| ABAQUS/CAE Usage: | Load module: Create Boundary Condition: Step: Initial: Symmetry/Antisymmetry/Encastre: select regions and toggle on the boundary condition type |
Boundary conditions can be prescribed within an analysis step using either “direct” or “type” format. In addition in ABAQUS/Standard, boundary conditions can be prescribed within an analysis step in user subroutine DISP. As with model data boundary conditions, the “type” format can be used only in stress/displacement analyses; the “direct” format must be used in all other analysis types.
When using “direct” format or user subroutine DISP, boundary conditions can be defined as the total value of a variable or, in a stress/displacement analysis, as the value of a variable's velocity or acceleration.
As many boundary conditions as necessary can be defined in a step.
| Input File Usage: | *BOUNDARY |
| ABAQUS/CAE Usage: | Load module: Create Boundary Condition: Step: analysis_step |
Specify the region of the model to which the boundary conditions apply, the degree or degrees of freedom to be specified (see “Conventions,” Section 1.2.2, for the degree of freedom numbers used in ABAQUS), and the magnitude of the boundary condition. If the magnitude is omitted, it is the same as specifying a zero magnitude.
In stress/displacement analysis you can specify a velocity history or an acceleration history. The default is a displacement history.
| Input File Usage: | Use either of the following options to prescribe a displacement history: |
*BOUNDARY or *BOUNDARY, TYPE=DISPLACEMENT node or node set, degree of freedom, magnitude node or node set, first degree of freedom, last degree of freedom, magnitude Use the following option to prescribe a velocity history (the data lines are the same as above): *BOUNDARY, TYPE=VELOCITY Use the following option to prescribe an acceleration history (the data lines are the same as above): *BOUNDARY, TYPE=ACCELERATION For example, *BOUNDARY, TYPE=VELOCITY EDGE, 1, 1, 0.5 indicates that all nodes in node set EDGE have a prescribed velocity magnitude of 0.5 in degree of freedom 1 ( |
| ABAQUS/CAE Usage: | Load module: Create Boundary Condition: Step: analysis_step: Displacement/Rotation, Velocity/Angular velocity, or Acceleration/Angular acceleration: select regions, toggle on the degree or degrees of freedom, and enter the magnitudes |
In ABAQUS/Standard you can prescribe jumps in displacements. For example, a displacement-type boundary condition is used to apply a prescribed displacement magnitude of 0.5 in degree of freedom 1 (
) to the nodes in node set EDGE. In a second step these nodes can be moved by another 0.5 length units (to a total displacement of 1.0) by applying a prescribed displacement magnitude of 1.0 in degree of freedom 1 to node set EDGE. Specifying a prescribed displacement magnitude of 0 (or omitting the magnitude) in degree of freedom 1 in the next step would return the nodes in node set EDGE to their original locations.
In contrast, ABAQUS/Explicit does not admit jumps in displacements and rotations. Displacement boundary conditions in displacement and rotation degrees of freedom are enforced in an incremental manner using the slope of the amplitude curve (see below). If no amplitude is specified, ABAQUS/Explicit will ignore the user-supplied displacement value and enforce a zero velocity boundary condition.
The displacement must remain continuous across steps. If amplitude curves are specified, it is possible, but not valid, to specify a jump in the displacement across a step boundary when using step time for the amplitude definition. ABAQUS/Explicit will ignore such jumps in displacement if they are specified.
The type of boundary condition can be specified (as history data) instead of degrees of freedom in the same manner as discussed above for model data. The boundary condition “types” that are available as history data are the same as those available as model data.
Once a degree of freedom has been constrained using a “type” boundary condition as history data, the constraint cannot be modified by using a boundary condition in “direct” format. The constraint can be redefined only by using a boundary condition in “direct” format after all previously applied boundary conditions specified using “type” format are removed.
| Input File Usage: | *BOUNDARY node or node set, boundary condition type |
| ABAQUS/CAE Usage: | Load module: Create Boundary Condition: Step: analysis_step: Symmetry/Antisymmetry/Encastre: select regions and toggle on the boundary condition type |
In ABAQUS/Standard you can prescribe the magnitudes of boundary conditions in user subroutine DISP. The time variation of the magnitude can be specified in the subroutine, which is sometimes preferable when the time history of the magnitude is complex.
The region to which the boundary conditions apply and the constrained degrees of freedom must be specified as part of the boundary condition definition. User subroutine DISP will be called for each constrained degree of freedom.
| Input File Usage: | *BOUNDARY, USER |
| ABAQUS/CAE Usage: | Load module: Create Boundary Condition: Step: analysis_step: Displacement/Rotation, Velocity/Angular velocity, or Acceleration/Angular acceleration: Distribution: User-defined |
The prescribed magnitude of a basic solution variable, a velocity, or an acceleration can vary with time during a step according to an amplitude definition (“Amplitude curves,” Section 27.1.2).
When an amplitude definition is used with a boundary condition in a dynamic or modal dynamic analysis, the first and second time derivatives of the constrained variable may be discontinuous. For example, ABAQUS will compute the corresponding velocity and acceleration from a given displacement boundary condition.
By default, ABAQUS/Standard will smooth the amplitude curve so that the derivatives of the specified boundary condition will be finite. You must ensure that the applied values are correct after smoothing.
ABAQUS/Explicit does not apply default smoothing to discontinuous amplitude curves. To avoid the “noisy” solution that may result from discontinuities in ABAQUS/Explicit, it is better to specify the velocity history of a node. See “Amplitude curves,” Section 27.1.2.
| Input File Usage: | Use both of the following options: |
*AMPLITUDE, NAME=name *BOUNDARY, AMPLITUDE=name |
| ABAQUS/CAE Usage: | Load or Interaction module: Create Amplitude: Name: amplitude_name |
By default, all boundary conditions defined in the previous general analysis step remain unchanged in the subsequent general step or in subsequent consecutive linear perturbation steps. Boundary conditions do not propagate between linear perturbation steps. You define the boundary conditions in effect for a given step relative to the preexisting boundary conditions. At each new step the existing boundary conditions can be modified and additional boundary conditions can be specified. Alternatively, you can release all previously applied boundary conditions in a step and specify new ones. In this case any boundary conditions that are to be retained must be respecified.
When you modify an existing boundary condition, the node or node set must be specified in exactly the same way as previously. For example, if a boundary condition is specified for a node set in one step and for an individual node contained in the set in another step, ABAQUS issues an error. You must remove the boundary condition and respecify it to change the way the node or node set is specified.
| ABAQUS/CAE Usage: | Load module: Create Boundary Condition or Boundary Condition Manager: Edit |
If you choose to remove any boundary condition in a step, no boundary conditions will be propagated from the previous general step. Therefore, all boundary conditions that are in effect during this step must be respecified. The only exception to this rule is during an eigenvalue buckling prediction procedure, as described in “Eigenvalue buckling prediction,” Section 6.2.3.
Setting a boundary condition to zero is not the same as removing it.
| ABAQUS/CAE Usage: | Use the following option to remove a boundary condition within a step: |
Load module: Boundary Condition Manager: Deactivate ABAQUS/CAE automatically respecifies any boundary conditions that should remain in effect during this step. |
In ABAQUS/Standard you can “freeze” specified degrees of freedom at their final values from the last general analysis step. Specifying a zero velocity or zero acceleration boundary condition will have the same effect as fixing the degrees of freedom for displacement or velocity, respectively.
| ABAQUS/CAE Usage: | Load module: Create Boundary Condition: Step: analysis_step: Displacement/Rotation, Velocity/Angular velocity, or Acceleration/Angular acceleration: Method: Fixed at Current Position (available only if a previous general analysis step exists) |
In a linear perturbation step (“General and linear perturbation procedures,” Section 6.1.2) the magnitudes of prescribed boundary conditions should be given as the magnitudes of the perturbations about the base state. Boundary conditions given within the model definition are always regarded as part of the base state, even if the first analysis step is a linear perturbation step. The boundary conditions given in a linear perturbation step will not affect subsequent steps.
If a perturbation step does not contain a boundary condition definition, degrees of freedom that are restrained/prescribed in the base state will be restrained in the perturbation step and will have perturbation magnitudes of zero. To prescribe nonzero perturbation magnitudes, you have to modify the existing boundary conditions. You can also fix and prescribe perturbation magnitudes of degrees of freedom that are unrestrained in the base state.
If degrees of freedom that are restrained/prescribed in the base state are released, all restraints that are to remain must be respecified, remembering that all magnitudes will be interpreted as perturbations.
Fixing the degrees of freedom at their final values from the last general analysis step (see previous discussion) has the same effect as modifying the existing boundary conditions to have zero perturbation magnitudes for all specified degrees of freedom.
In a direct-solution steady-state dynamic analysis both real and imaginary boundary conditions can be specified (see “Direct-solution steady-state dynamic analysis,” Section 6.3.4).
The antisymmetric buckling modes of a symmetric structure can be found in an eigenvalue buckling prediction analysis by specifying the proper boundary conditions (see “Eigenvalue buckling prediction,” Section 6.2.3).
In modal superposition procedures (“Dynamic analysis procedures: overview,” Section 6.3.1) prescribed displacements cannot be defined directly using a boundary condition. Instead, the boundary conditions are grouped into bases in a frequency extraction step. Then, the motion of each base is prescribed in the modal superposition step. See “Natural frequency extraction,” Section 6.3.5, and “Transient modal dynamic analysis,” Section 6.3.7, for details on this method.
| Input File Usage: | *BOUNDARY, BASE NAME *BASE MOTION |
| ABAQUS/CAE Usage: | Base motions are not supported in ABAQUS/CAE. |
When using the submodeling technique, the magnitudes of the boundary conditions in the submodel can be defined by interpolating the values of the prescribed degrees of freedom from the file output results of the global model. See “Submodeling,” Section 10.2.1, for details.
Sequential finite rotations about different axes of rotation are not additive, which can make direct specification of such rotations challenging. It is much simpler to apply finite-rotation boundary conditions by specifying the rotational velocity versus time. For a discussion of the rotation degrees of freedom and a multiple step finite rotation example that demonstrates why velocity-type boundary conditions are preferred for specifying finite-rotation boundary conditions, see “Conventions,” Section 1.2.2.
When velocity-type boundary conditions are used to prescribe rotations, the definition is given in terms of the angular velocity instead of the total rotation. If the angular velocity is associated with a nondefault amplitude, ABAQUS calculates the prescribed increment of rotation as the average of the prescribed angular velocities at the beginning and the end of each increment, multiplied by the time increment.
In ABAQUS/Explicit displacement-type boundary conditions that refer to an amplitude curve are effectively enforced as velocity boundary conditions using average velocities over time increments as computed by finite differences of values from the amplitude curve. As with prescribed displacements (see “Prescribed displacement” above), ABAQUS/Explicit does not admit jumps in rotations.
Displacement-type boundary conditions in ABAQUS/Standard that constrain just one component of rotation can have essentially no effect on the solution because the two unconstrained rotational degrees of freedom can combine to override the constraint.
For example, if a rotation of 
about the z-axis is required in a static step, with no rotation about the x- and y-axes, use a step time (specified as part of the static step definition) of 1.0, and define a velocity-type boundary condition to specify zero velocity for degrees of freedom 4 and 5 and a constant angular velocity of for degree of freedom 6. Since the default variation for a velocity-type boundary condition in a static procedure is a step, the velocity will be constant over the step. Alternatively, an amplitude reference could be used to specify the desired variation over the step.
*BOUNDARY, TYPE=VELOCITY NODE, 4 NODE, 5 NODE, 6, 6, 18.84955592
If, in the next step, the same node should have an additional rotation of 
radians about the global x-axis, use another static step with a step time of 1.0 and again define a velocity-type boundary condition to prescribe zero velocity for degrees of freedom 5 and 6 and a constant angular velocity of for degree of freedom 4.
*BOUNDARY, TYPE=VELOCITY NODE, 4, 4, 1.570796327 NODE, 5 NODE, 6
, 
, 
).