Predicting material failure is always a challenge, especially when it comes to composites and advanced materials. There are plenty of theories that try to provide a numerical approach to solve this complex problem, such as Maximum Stress/Strain Theories, Hashin, Tsai-Hill or Tsai-Wu. Although all of them brought something valuable to the table, some of them don’t seem to be that precise when accurate results are needed. In these terms, Tsai-Wu is my least favourite criterion and I’ll explain the reasons for that.
First of all, Tsai-Wu is an interactive failure criterion for composite materials. This means that the theory takes into account the interaction of different stress components in order to predict failure. Basically, the criterion uses equation 1 (subjected to the condition given by equation 2) to calculate an index and, if its value is one, then it means the material is failing. Please note that i,j=1,2,…,6, where subindices 1 to 3 represent normal stress components and 4 to 6 are shear stress components. In the original publication, authors explain how the different coefficient can be determined through experimental tests (e.g. compression, tension, biaxial…). So far, so good.
If you are a regular Abaqus user, I am sure that eventually you will need to run models for long periods of time. It can be quite annoying to go back to the office just to check if the simulation has finished to then find out that it is still running. For that reason, I’ve coded a simple python script that sends an automatic e-mail to the user once the simulation is completed or aborts due to errors.
While you run FE models that take a huge amount of computational time to finish, it is likely that you will be working on other things, such as experimental tests, reports, meetings and so on. Obviously, we want to check our results as soon as they are ready, but in order to do so we need to be checking our computer every now and then. This can be particularly annoying when you leave a simulation running for a few days and you are doing things out of the office. Hence you need to go and check if the model is done… and then you realise it’s still there, calculating more stresses and strains and that your trip to the office was a waste of time. To overcome this problem, I decided to create a python script to send a notification directly to my e-mail every time my analyses finish. I will try to explain you the basics so you can use this code on your computer.Continue reading →
Basically, when we want to determine the forces and displacements in a certain structure using Finite Element Analysis (FEA), what we are doing is creating a system of equations that relates the stiffness of the elements to the displacements and forces in each node. When we run a simulation, we do not see all the calculations. For that reason, today I want to illustrate a simple case that can be easily solved by hand applying that methodology.
Before getting started, just think of a spring. Everyone has come across the Hooke’s law at a certain point during school. It states that the force in the spring is proportional to a constant “k” multiplied by the variation in length of the spring. FEA follows the same principle, but in this case the “k” constant is the stiffness matrix and the variation in length is a vector of displacements and rotations, depending on the case.
Let’s study a simple static case. Our structure consists of two bar elements connected at a common node, where a load “P” is applied. The other two nodes have both horizontal and vertical displacements constrained (see the boundary conditions). For this particular case, the reactions in nodes 1 and 3 and the displacements of node 2 are requested. I have solved the problem by hand following a few steps that, based on my experience, can be generalised for more complex problems. Pretty much, the summary of the methodology is:Continue reading →
The FEA dictionary is back and it’s time for letter D! Today I will introduce you to one of the methods to introduce damage in your material models.
Although it was created based on the failure of metals, this damage model can be used to introduce the degradation of mechanical properties for other types of materials. This option is available in Abaqus/Standard and Abaqus/Explicit and it requires the definition of the ideal elastic-plastic behaviour of the material, a damage initiation criterion and a damage evolution response. Please note that if any of the requirements cited before is not defined, the material properties will not be degraded.
In Abaqus there are different options for the damage initiation criterion and basically they can be classified as follows:
Criteria for fracture of metals (ductile and shear).
Happy New Year everyone! After a well deserved Christmas break I’m back with some more engineering topics. In this occasion I want to introduce a new series of brief posts about Finite Element Analysis. The idea is to cover one topic for each letter of the alphabet (i.e. from A to Z). Let’s get started!
Motivated by the “A-Z Challenge” that I followed for the first time thanks to Dr David Jesson, the idea of doing something similar has been growing in my head for some time. However, in this case I won’t be writing a post every day but, hopefully, once a week a new one will be published.
I had some doubts about the topic, but after meeting some of the members of the Formula Student Team of the University of Seville (Spain), I thought it would be a great idea to do some kind of simple Finite Element guide. In particular, this guide will be focused on the commercial package Abaqus. Some of you might be wondering why I’ve chosen this particular software, and the reason is pretty obvious: it is one of the most used FE packages in industry and loads of students struggle to understand how it works, especially if their first experience with FEA involved Ansys. Don’t get me wrong, I started using Ansys as well and I don’t want to give the impression that I have a problem with it. The thing is though, that a lot of people tend to learn how to model things in Ansys by heart and because of that, they won’t be able to reproduce the same models in other packages.
This week I wanted to write a brief post regarding a very common problem that can be found when running and post-processing Finite Element models: the correct definition of contact algorithms.
During this week, I had a conversation with other engineers about some issues related to the TIED CONTACT definition. In these terms, any commercial FE package gives you the opportunity to define this type of contact in a relatively easy way: you select the nodes or surfaces (master and slave) and then the pre-processor shows some kind of symbol in order to highlight that the contact has been established. However, the symbols and the fact that you have followed the standard steps of the software do not mean that the parts are going to behave as expected.Continue reading →