Hyperlyceum.com

How to Solve and Debug Common Abaqus Errors (A Comprehensive Guide): Part-2

Abaqus errors content-2
Share This Post

Welcome back to our comprehensive guide on troubleshooting Abaqus software errors. In Part 1, we delved into some of the most common errors users encounter and provided detailed solutions to resolve them. If you missed it, we highly recommend reviewing Part 1 here, to ensure you have a solid foundation before diving into this next section.

In Part 2, we will continue our journey by exploring more complex and nuanced errors that can arise during the use of Abaqus. These issues may be less frequent but can pose significant challenges when they do occur. Our aim is to equip you with the knowledge and tools needed to diagnose and address these problems effectively, minimizing downtime and ensuring a smoother simulation process.

By the end of this section, you should be well-prepared to tackle a broader range of Abaqus errors, enhancing your problem-solving toolkit and optimizing your simulation workflows. Let’s get started!

Node have Inactive DOF

Each element in Abaqus covers specific degrees of freedom. For example, elements like Continuum or Solid incorporated in Abaqus lack the capability to model and consider rotation. If the loading contradicts the element’s degrees of freedom, Abaqus will terminate with an error.

This error indicates that the applied loading on the component is incompatible with the degrees of freedom of the element used. To rectify this error in Abaqus, go to the Mesh module and modify the element.

In some cases where you’re not allowed to change the element type and are required to use a specific type of element, you should utilize constraints inherent in the Interaction module to apply the load. For instance, you can define a Coupling or Rigid Body constraint between the desired face of the body and a reference point, and apply the desired load or torque to this point.

Simultaneous definition of two or more boundary conditions and contradictory loading for analysis

The error “some nodes have dof on which velocity/displacement/acceleration/base motion etc are specified simultaneously” in Abaqus is considered one of the most common errors resulting from users’ negligence during analysis. While it may seem obvious and clear that boundary conditions and loading defined for a problem should not contradict each other, the reason for encountering the above error is precisely due to a violation of this clear rule. If contradictory boundary conditions are defined for a set of nodes, you’ll face an error like the one shown below:

For instance, suppose you’ve constrained all points at the end of a component with the Encastre constraint and then applied displacement to the same points! In this case, due to the inconsistency between the boundary conditions and the applied loading, Abaqus will be unable to solve the problem and will terminate with the aforementioned error.

It’s crucial to note that to resolve this error, you need to navigate to the Load module and meticulously examine the boundary conditions and applied loading on the component to eliminate the existing contradiction.

Analysis Input File Processor exited with an error

The occurrence of this type of error can have various reasons. One of the most significant ones is that the generated job file has created a significant hidden cache in the background, rendering the job unable to execute the codes and continue the process with its initial title. Another reason for encountering this message relates to the memory and processor capabilities of the simulation computer system.

To resolve this error, the first step is to rename the previous job using the Rename function. If the solution fails, delete the previous job and initiate a new job with a distinct name. If this workaround also fails, once again check or edit the Property, Boundary Condition, and Mesh modules.

The elements contained in element set have distorted excessively

Element distortion Abaqus error

The error indicating that “some nodes have dof on which velocity/displacement/acceleration/base motion etc are specified simultaneously” is commonly caused by inaccuracies during analysis. This issue can arise due to excessive loading rates or sizes on components defined as deformable. Such errors typically occur in analyses involving significant material deformation.

Specifically, this error might manifest in:

  • Plasticity or shaping analyses where materials undergo large strains and deformations.
  • Coupled structural and fluid analyses, such as sloshing, aiming to model fluid sloshing by assigning state equations and special properties to the fluid, attempting to solve fluid equations using finite element techniques instead of computational fluid dynamics (CFD) methods.

To address this error, precautions must be taken to ensure that elements do not excessively deform during job execution. Consider the following approaches:

  • Refine element sizes and modify meshing techniques to improve element quality, which can aid in completing the analysis successfully.
  • Changing element orders from 1 to 2, although this increases the analysis volume and RAM consumption, is one of the easiest ways to enhance the likelihood of analysis completion.
  • In some cases, the calculated strain levels may reach a point where the material enters its damage zone. Defining appropriate damage initiation and growth criteria for the material is crucial for continued analysis. Failure to define suitable damage criteria is a common mistake among Abaqus users that can lead to this error.

For certain shaping analyses where increasing mesh density and elevating element orders alone do not complete the analysis, employing an adaptive meshing algorithm like Arbitrary Lagrangian-Eulerian (ALE) for parts undergoing significant deformation can significantly aid in completing and advancing the analysis. However, using this technique in simulation, like other proposed solutions, may increase analysis time.

The executable standard.exe aborted with system error code 1073741819

In other Abaqus errors, the error message typically provides explanations regarding its relationship with convergence issues or insufficient settings. However, in the case of this error, which is perhaps the most cryptic Abaqus error, no similar explanations are provided. The error arises when the software struggles to identify the problem, resulting in this elusive error message.

In models lacking subroutines (especially UMAT subroutines), this error may occur due to inadequate definition of physical behaviors in the Property module. For instance, improper definition of mechanical behavior parameters for soil (in geotechnical problems) can lead to the issuance of this error.

If you are using Abaqus version 6.13 or higher and encounter this error, prior to making any modifications to the model, you can navigate to the path: Simulia/abaqus/6.13(or 14 or…)/code/bin, and find the file mkl_avx2.dll, then rename it to mkl_avx2.dll.11.0.0.1. This renaming does not have any negative impact on the software. If after renaming, you still encounter this error upon resubmitting the corresponding job, it indicates that there is inconsistency between some of the settings and parameters in your model, which needs to be addressed.

To diagnose the error, adjust settings, values, and observe results by adding, removing, or modifying them accordingly. For example, if you have defined predefined fields in the model’s initial conditions, remove them and resubmit the job. If the error does not occur at this point, it means that the issue was with the defined initial condition.

Abaqus Subroutine Problem during Compilation Error

This error appears in model development using the Abaqus subroutine.

Abaqus Subroutine Problem during Compilation Error

There are three main reasons to this error; the syntax error, and the conflict between the code and Abaqus solver.

Error due to linking Abaqus

One of the main reasons for this error is a mistake in linking Abaqus. If you want to learn more about the linking method please, watch the following video:

How to Link Abaqus with Intel FORTRAN

To check if the problem is due to linking you can download the files here and execute them. If you receive any errors executing these files, it means the problem is linking Abaqus. If not, it means your code has a problem and you need to follow the approach explained here. There are two main approaches to detect and fix the problem which are explained in this video by examples.

Methods to debug the Abaqus subroutine errors

The first method is using the file with *.log extension as includes the data regarding the simulation process. Debugging via file opening is time-consuming, so a method linked to the command window is explained to report errors efficiently.

Moreover, you can visit the following links to get a complete tutorial about this error and its solutions:

More To Explore

Leave a Reply

Your email address will not be published. Required fields are marked *

Subscribe To Our Newsletter
Get updates and learn from the best

Table of Contents

Do you need help from experts?
drop us a line and keep in touch