Interactions

This page describes recent changes in Abaqus Interactions.

2025 GA

Step Cycling for Contact Wear Simulations

You can now use step cycling and step cycling controls to avoid explicitly specifying each instance of repeated steps associated with wear accumulation and to allow the number of physical wear cycles represented per simulated cycle to evolve based on current wear rates in Abaqus/Standard.
Benefits: Step cycling makes it easier to specify the model and enables more computationally efficient wear simulations.

In many contact wear workflows, surface wear accumulates over thousands of physical wear cycles. It is often prohibitively expensive to simulate each physical wear cycle, so each simulated cycle typically represents a "batch" of multiple similar physical cycles. The animation below shows a wear simulation over five simulated cycles that represent 110,000 physical wear cycles in total. Step cycling allows the "batch size" to evolve during the simulation based on the maximum incremental wear distance in the simulated cycle. The number of simulated cycles is often not known before running such a simulation. For each simulated cycle, the user-specified wear coefficients are scaled by the current batch size.



The animation shows the wear distance accumulation on the slider and the bottom block as the slider repeatedly moves back and forth. In this example, the simulated wear cycle is modeled in two steps:

  • In “Step-2” the slider moves to the right and returns to the center.
  • In “Step-3” the slider moves to the left and returns to the center.
These two steps are repeated using step cycling until a threshold wear distance exceeds 0.012 or reaches a cap of 10 repetitions of the simulated wear cycle. The batch size for scaling the wear coefficients has an initial value of 10,000 and a cap of 25,000. The target incremental wear distance is 0.006 accumulated per simulated cycle. The batch size for the next simulated wear cycle is internally calculated so that the estimated maximum wear accumulation is less than the target value of 0.006 while respecting the batch size cap. The example simulation reaches the threshold wear distance in 5 simulated cycles. The batch size for the initial cycle is 10,000 based on user input. For the subsequent cycles, the batch sizes are calculated to be 25,000 (the cap value) while maintaining the maximum wear accumulated in each simulated cycle to be less than 0.006.

Contact Involving Beams with Noncircular Cross-Sections in Abaqus/Explicit

The contact surface representation of beams with noncircular cross-sections in Abaqus/Explicit now uses internally generated meshes of surface elements that are available for postprocessing.
Benefits: The new contact surface representation is consistent with Abaqus/Standard, and it more accurately and realistically represents contact output.

In earlier releases of Abaqus/Explicit, similar internally generated meshes could be used for simulations but they were not available for postprocessing. The following images compare plots of contact forces and contact opening distances on beam elements to plots on internally generated surface-element representations of the beams. Plots on surface elements show variations over the surfaces, similar to plots that would occur on the outer surface of a solid body, whereas plots based on beam elements are limited in that they represent a single value at each axial location.

Furthermore, some rounding of edges in the contact representation to improve numerics is achieved by offsetting nodes of internally generated surface elements inward and adding a small corresponding contact thickness. This contact thickness is not represented in plots, so the parts appear a bit smaller than the actual size.

Figure 1. Tweezers beam model contact force vector plot across versions (beam rendering not available for vector plots).

Figure 2. Tweezers beam model contact opening distance output in previous versions (beam rendering shown for Abaqus 2024).

2024 FD03

Arbitrary Lagrangian-Eulerian (ALE) Adaptive Meshing Supports Contact Wear in Abaqus/Explicit

You can now use arbitrary Lagrangian-Eulerian (ALE) adaptive meshing together with wear in Abaqus/Explicit, which accounts for local surface wear distances in underlying element calculations.
Benefits: Users can more easily and accurately account for wear distances that are large compared to element dimensions.

The capability to simulate wear in general contact in Abaqus/Explicit was introduced in 2024 FD02. In that release Abaqus/Explicit treated the evolution of wear exclusively by considering nodal wear distances in contact penetration calculations. Now you can use arbitrary Lagrangian-Eulerian (ALE) adaptive meshing together with wear in Abaqus/Explicit to account for surface wear (erosion) in part geometries while preserving mesh quality, even for wear distances on the order of element dimensions.

The simulation on the left below shows the preexisting behavior (wear distances accounted for with offsets in contact penetration calculations). The simulation on the right demonstrates the use of ALE in the context of wear modeling. Similar wear accumulation occurs for both models, but it is much easier to interpret the wear configurations with ALE. Most wear occurs on the smaller block in this model, with the maximum wear distance being approximately half of the original element depth. In this example, ALE mesh smoothing effectively provides a realistic representation of the evolving part geometry while maintaining good mesh quality.



Related topics: Contact Wear and *ADAPTIVE MESH.

2024 FD02

Cohesive Contact in Abaqus/Explicit

Performance for Abaqus/Explicit models with cohesive contact is improved compared to earlier releases. In addition, scaling the default contact penalty stiffness now also scales the default contact cohesive stiffness in Abaqus/Explicit; this behavior is consistent with that in Abaqus/Standard.
Benefits: The improvements facilitate more efficient user workflows and user adjustments to increase or decrease the contact cohesive stiffness from its default value.

Enhancements to cohesive contact in Abaqus/Explicit make cohesive contact a preferred alternative to surface-based tie constraints for modeling permanent, stiff bonds in more cases (for example, models where ties result in large implicit constraint systems or when you require interfacial traction results across connected surfaces).

Performance improvements for cohesive contact are most noticeable for models with a large fraction of nodes participating in cohesive contact. For example, simulations for the models shown in Figure 3 and Figure 4 with permanent, stiff cohesive contact bonds have sped up by 13% and 12%, respectively, compared to simulations in 2024 FD01.

Figure 3. Two plates modeled with solid elements bonded together with permanent, stiff cohesive contact.

Figure 4. Two plates modeled with shell elements (shown with shell thickness rendering) bonded together with permanent, stiff cohesive contact.

A second enhancement allows the default cohesive stiffness to be scaled by existing options to scale the contact penalty stiffness in Abaqus/Explicit. Cohesive contact, like other contact constraints, has a finite bond stiffness. You can assign the bond stiffness or allow it to take on the same contact penalty stiffness that would be in effect to resist penetrations for regular contact behavior, as discussed in Contact Cohesive Behavior. You can use a scale factor to increase the cohesive stiffness relative to the default value.

Figure 5 shows two blocks bonded together with uniform tensile (negative pressure) loading of 1 × 106 N/m2 applied to the top face of the top block while the bottom of the bottom block is constrained. Loading is smoothly ramped on and damping is included to obtain a quasi-static solution.

Figure 5. Model characteristics.

Figure 6 shows that the axial stress results correspond to the expected uniaxial stress solution regardless of details of how the bond is modeled.
Figure 6. Vertical stress (S11) for three model variants.

Figure 7 shows that some additional displacement occurs when a penalty stiffness is used to enforce the bond. Increasing the penalty stiffness via a scale factor is a convenient mechanism to control the resistance to relative motion across the bond.
Figure 7. Vertical displacement (U1) for four model variants.

The mesh is quite coarse in this example. The default penalty stiffness would be greater with a more refined mesh. Increasing the penalty stiffness tends to decrease the time increment size in Abaqus/Explicit unless contact mass scaling is used (see Mass Scaling to Account for Contact Stiffness).

Alternatively, you can directly specify cohesive stiffness components, as discussed in Cohesive Stiffness. When you specify the cohesive stiffness, the penalty stiffness scale factor has no effect.

Contact Wear in Abaqus/Explicit

Abaqus/Explicit can now model the evolution of wear and visualize nodal wear distances on contact surfaces due to mechanical contact based on the Archard’s wear equation.
Benefits: You can now model wear accumulated at the contact level in Abaqus/Explicit.

This new capability is available in Abaqus/Explicit for general contact analysis involving solid elements. Similar to the implementation introduced for Abaqus/Standard in 2024 FD01, the modeling approach accounts for local surface wear distances in contact penetration calculations but not in underlying element calculations.

The image below shows an example of accumulation of wear (shown as CWEAR contour output) in a simplified helical bevel gear analysis.



Usability enhancement for specifying reference thread geometry in Abaqus/Standard

Abaqus/Standard allows reference thread geometry to be specified on either surface (secondary or main) of a small-sliding interaction for general contact.
Benefits: Reference thread data for reference thread geometry can be specified for either surface of a small-sliding interaction of general contact.

Allowing reference thread geometry to be specified on either surface of a small-sliding interaction for general contact improves usability. Previously, this data was expected to be specified on whichever surface acting as the secondary surface of the contact formulation. However, main and secondary roles are typically left as default assignments for general contact in Abaqus/Standard, so a user typically would not know the secondary and main roles before running a simulation (and typically should not need to be aware of those roles).

The right side of Figure 8 shows that results in Abaqus 2024 HF2 are insensitive to whether reference thread geometry is specified for the bolt or hole surface for small sliding interactions of general contact. In prior versions, the expected behavior was obtained only if reference thread geometry was specified for the secondary surface.

Figure 8. Cut-away views of contact force vectors on bolt nodes.

2024 FD01

Contact Wear in Abaqus/Standard

You can now model the evolution of wear and visualize nodal wear distances on contact surfaces due to mechanical contact, based on the Archard’s wear equation.
Benefits: Abaqus/Standard can now handle wear modeling workflows in automotive, aerospace, life sciences, and packaging applications.

In many workflows, mechanical contact can cause wear on contacting surfaces due to mechanisms like abrasion and fretting. The new wear capability in Abaqus/Standard models wear evolution based on the Archard’s wear equation. Accordingly, contact nodal wear distances evolve based on wear properties of the surface material and on contact variables such as normal stress and slip distance. Abaqus/Standard treats wear distances as nodal offsets to the contact algorithm, resulting in a simplified approach to model wear fully within contact. It does not model the changes to geometry from wear explicitly. The approach considers the two-way physical influence of wear distance evolution on contact stresses (and underlying material stresses) and vice versa.

Figure 9 shows two blocks in contact.

Figure 9. Wear accumulation on contact surfaces.



Wear properties for the Archard’s wear equation are specified on the contact surfaces. Nodal wear distances accumulate as the blocks slide relative to each other under compression. The nodal wear distances on the two surfaces are shown as CWEAR output contours at the end of the simulation.