Showing posts with label abaqus. Show all posts
Showing posts with label abaqus. Show all posts

Wednesday, April 3, 2013

Talking About Work


I have not specifically addressed this topic with an entire article. It’s a shame that this post should rectify. Let us begin.

Who’s intellectual property is it? If I write something at work does my employer own it? Yes, at least I think so. If I say something at work does my employer own it? I don’t know. If I think something at work does my employer own it? I hope not. I mean, of course not, or at least they would have a hard time finding evidence they own it. Plus, they probably don't want to own every evil thought in my head. But it’s really an interesting process, from idea to written communication I lose ownership of my idea. My work is no longer my work but the company’s work. 

That’s pretty much the basis of the whole argument.

So my dilemma every week when I write my weekly summary is that of elation about the problem solving that I did, and terror that I will say too much and get fired. I do fully expect at some point in my life to lose a position of economic income because of what I say on my blog and also I expect one or more times to gain an economic income for the fact that I do say things on my blog. In other words, Seth Godin and Guy Kawasaki get paid a lot doing traditional things like consulting and strategizing for traditional companies even though they convey a lot of information to scores of thousands of people. On the other hand, people get fired for things posted on Facebook and other sites. 

When I was younger I always thought I would go into the aerospace defense industry and work on secret projects that I could not tell anyone about. I did the stint at Sikorsky, but my project had nothing to do with any product for national defense. Rather, anyone with the money can buy the products I work on and look at the work that I do. Frankly you can probably buy a little 1/32nd scale model and still see much of the work that I do with gussets, tails and radii. Or at least in about two years you will be able to see it. 

So the rules I set out for myself are:
  • If the work I did is related to production I don’t show it. In other words, I’m not going to show some strain contour plots of a brand new boom. Honestly, I might never show strain contour plots of any assembly because inevitably a crack will show up in a place where we didn’t predict it would. 
  • If the work is related to a failure I don’t show it because I would probably get fired for admitting that things fail during the warranty period (regardless of the fact that we probably fail far less in the warranty period than the competition). 
  • Nobody else at work agreed to the terms I did to blog about my life. Therefore I will not name names or discuss others work. If I can somehow claim that I am responsible, both for the credit and the blame, than I might discuss it. Otherwise, you will not hear about it from me. Most of the time this is not a problem because I usually don’t know what other people are working on and I often spend 35+ hours alone working on a project just to turn around and spend eight minutes presenting it. It’s not that I want authority, but I do enjoy accountability.
So that is where I stand. Am I too open? Some would say so. However, unlike the weekly changes to the privacy policies of Google and Facebook I am all I have to work with. I have done what I have done, both right and wrong. I certainly don’t want you to know everything, but given the choice between unlimited sharing and absolutely no sharing or communication I choose the sharing. Should I share more? Some would say so. Secrets are a strange thing. We all have things from our past we did wrong. General Petraus had a mistress and affair and he was supposed to be the leader of the CIA.  

It interests me that articles about Abaqus and Ansys continually rate as my most viewed, yet most of them I wrote in 2009. I am so much better at finite element analysis now than I was back then. I read the struggling comments and see the page views, and I want to help! I want to make the world a better place!

What does that leave to talk about? Abstract business concept discussions, show pictures of "science projects" that I work on when work is slow, and when I am learning new skills that are probably unrelated to my daily job. Also, it leaves running, which is why I talk about running so much. I bet a lot of people go home and don't really think about work, it's almost 9 at night and I'm thinking about learning Optistruct. And I want to share that with people. My contributions to Wikipedia and Squidoo only satisfy me so far. I want to tell people how awesome finite element analysis is! I want to recruit new engineers from middle school! I want to show animations!!!

Sunday, March 3, 2013

I Live in Iowa: Week 97

Another week in the bag. I will tell you what. I was tired a number of times this week. I had two under six mile running days. I slept ten hours Friday night. And at the moment I just finished a 20.6 mile run so I'm pretty tired again.

When a complex finite element simulation converges for the first increment after lots of convergence issues it's an exciting day. So Abaqus outputs a file with the extension .sta. For Abaqus Standard this records all of the increments that occur. Instead of the .sta file showing:

Attempt:  Time Increment:
1U          0.01
2U          0.0025
3U          0.0008125
4U          0.0002031
5U          5.076e-5

Indicating the file did not converge after five attempts to reduce the time increment, the file shows:

1           0.01

Meaning one increment converged without cutting back the time increment, it's party time! In fact, I am working on several variations of the simulation and one of them was something like:


1U          0.01
2U          0.0025
3U          0.0008125
4U          0.0002031
5             5.076e-5

Meaning that it just converged at a very small time increment. I was pretty happy about that too. In short, I had some good moments at work Thursday and Friday. Then I went in on Saturday and ate up over 750 GB of RAM and 48 new Intel Sandy Bridge cpus running my complex jobs.

I like work because I can put it in a box north of town. In school, there is always work to be done and it can be accessed from anywhere, which made it more stressful on the weekends, but I was way more productive on the nights and weekends. That being said, I miss school for the ability to go in at 8 PM and pound out an hour of work without a meeting or email to distract me.

Coaching was a nice week. It was nice because two athletes had pretty big races in the mile Saturday. One ran 4:38 and another ran 4:40, which are both PRs by maybe 5-6 seconds each. We are moving in a good direction! (Now if we can just get everyone to run for the next few weeks over spring break and as the majority of the team takes a break. College runners get a break after outdoor track in May and after cross country in November. They are only slowing themselves down if they take a break every time school takes a break.)

My own running went quite well. Two good workouts 6x1000 and 3x600, 3x200 and 86 miles for the week. The 1000s my total quality time was 19:18, which is good for me especially considering I had only 200 meters of jogging rest. The 600s were great! I did them all in 1:40! I am running a mile at a high school indoor meet this Friday and I think I can break 4:30. We will have to see, but there are two guys in the race both planning to go under 4:30 so I should just be able to hop on the train and run a PR.

Not much else. Happy Lent!

Friday, September 28, 2012

Understanding Stress Concentrations Using Finite Element Analysis


I spent a significant amount of time working with design engineers and occasionally designers. At my company there are probably 5-8 design engineers for every finite element analysis (FEA) engineer. That ratio seems to work out well most of the time. The problem is that design engineers, even structural design engineers, often have trouble visualizing how the stress and strain will “flow” through any given product. This can be a difficult topic because every product, part or assembly is different and is loaded in a different way. If we knew everywhere that something would crack, we would fix it before it cracked.

In my experience it is best to start with simple examples and get more difficult from there. We will start with a simple L shaped corner. In this particular example I started with a 10x10 (mm)  square and deleted a 6x6 section from it. I constrained the five nodes along the lower left vertical edge from all translational motion (but not constrained from any rotation). To each of the five nodes along the horizontal edge on the upper right I applied a 100 (N) force in the X and Y direction (so 141 N to each node at a 45 degree angle). Since I model everything in three dimensional space I applied a thickness of 1 (mm) to the shell (2D) elements. (As a side note Abaqus is unitless so I just put in numbers. The program does not have to have units, it could be meters or inches for distance instead of mm.)
Typical First Design Demonstrating a Square Inside Corner
Running that simulation gives us the pretty pictures below. The main one of the four that we are concerned with is in the lower left corner showing the maximum tensile strain. Tensile strains are often the most damaging and I designed this example to really demonstrate tensile strain.

Clockwise from Upper Left: Displacement; Von Mises Stress; Minimum Principal Strain (Compression); Maximum Principal Strain (Tension)
We quantify this by looking at the strain readings, in this case there is 5000 micro-strain or .005 (mm/mm). That is a huge amount! If this was an actual part, I predict it would break quickly.

One of the main things we try to do is provide a clear path from the load to the constraint. Think of this like standing. It is easier to stand with your legs under you than off to the side. It is easier to hold a weight in your hand at your side than with your arm outstretched. The reason is that the acceleration of gravity exerts a force on the weight that passes directly in line with your shoulder when your arm is down. When your arm is out stretched the force exerted is nowhere close to your shoulder.



A Great Design!

We build a clear path for the stress to flow often by adding a larger radius to an area that is over-stressed. In this example we went from having basically no radius to having a nice 6 (mm) radius. When the same force is applied we get the following images. 
Clockwise from Upper Left: Displacement; Von Mises Stress; Minimum Principal Strain (Compression); Maximum Principal Strain (Tension)
Isn't this great! Looking again at the maximum tensile strain in the lower left we see that there is only about 275 micro-strain! Wow! For an increase of 7.73 sq. (mm) we achieve a strain reduction of 94%! In other words, we increased the total weight of the part from 64 units to 71.73 units a 12% weight increase gave us a 94% strain reduction! 

Now, this is an oversimplification but for every 10% strain reduction the life is approximately double what it was before. That depends enormously on the material and where in the strain life region we are (it's more accurate for long life fatigue estimations in steels). However, using those rough numbers we can estimate that this part will last roughly more than 500 times as long the original design! (Another side note, if I actually used math that simple to build devices I would get fired. We have sophisticated software that helps us make more complex calculations.)

In conclusion, stress "flows" from load to constraint, and more strait the path the lower the stress.

Friday, August 10, 2012

The Jacobian: Finite Element Mesh Quality

This is as technical as engineering comes. Bring up a Jacobian to a bunch of finite element engineers and hopefully they will all know what you are talking about. This is so technical that it it typically only covered in senior level college classes or graduate school classes. Although, if you do cover it in college you will probably do the actual matrix equations, even though in real life (the business world) a computer does it in fractions of a second.

Now more specifically the Jacobian, which is short for the Jacobian Matrix Determinate, is really the best measure of finite element mesh quality. It is one number which defines how good or bad an element is. The Jacobian is a measure of the normals of the element faces relative to each other. Unfortunately, Hypermesh does not show the element face normals on solid elements, but it is basically an arrow on each face pointing out perpendicular to the face. The range of a Jacobian is from 1, a perfect cube, to something lower, -1 or even lower. The smallest Jacobian I have seen was -1.45. When the element face normals start to cross, that is they are not perpendicular to each other, your element quality gets worse.

For several examples I created the image below. In all of the elements, except for the red one, I simply translated one node (vertex) to a new location and kept the other seven in the original cube positions. You can see that as the node moves farther away from the cube position the element quality gets worse.

Sample Jacobians (J): Orange Cube J = 1.0; Blue J = .942 (z is .9 for one point); Purple J = .883 (z and y are .9 for one point); Pink J = .398 (z and y are .5 for one point); Green J = -.409 (z and y are -.1 for one point); Tan J = -.130 (z and y are .1 for one point); Red J = 1.0 (z is 3 for all four end points); Light Blue J = .072 (x y and z are .5 for one point)

How bad is bad? Abaqus will not run a job with a Jacobian below 0, at least not for me. Ansys on the other hand has less strict mesh quality requirements. Often times Abaqus will not run a solid element Jacobian below 0.2 and a shell element Jacobian below 0.3. And yes, I have had one element with a negative Jacobian prevent an Abaqus job with over 100,000 elements from running. If you can get all of the Jacobians in your model above .5 you can typically say you have a good quality mesh.

If you liked this click on something below or leave a comment, please. I can do more like this, but only if there is demand.

Monday, March 14, 2011

The Life of a Contract Engineer: Week 7

Seven weeks! It is still surreal that I have the opportunity to go to work and get paid for doing something that I enjoy. I spent the majority of my week learning how to use HyperMesh, which is part of the HyperWorks finite element suite. This is the third finite element software that I have learned. First it took me a year (working part time) to understand Abaqus and DANTE, then it took me a month to understand ANSYS and in less than a week using HyperMesh I have made significant progress. I now feel more valuable as a finite element engineer than I ever did in graduate school. I just need CATIA and NASTRAN to round out my repertoire and I'll be more qualified than most of the tech support for all of those companies.

Secondly at work, I enjoy the people I work with. I think that is an important factor. I have never really been in a bad working situation, but I can imagine and I have heard stories. Even five minutes of socializing with my coworkers per day is a nice mental boost.

My running injury just took a ginormous (that is an actual word!) leap forward! I went to a massage therapist and had fingers and thumbs pressed into my knots to the point that I was in significant pain and the knots started to release. I continued to do my exercises and I even bought a foam roller so that I could work on rolling out my tight muscles. In total I ran about 77 miles including a 3.3 mile tempo at 5:54 pace and a 12 mile and 10 mile run at 6:55 and 6:50 pace respectively. Those are three very pleasing runs compared to the amount of pain that I was in for two weeks.
Foam Roller
In other news I started an account with mint.com at the recommendation of a friend who is traveling in Laos right now. It is pretty cool. It updates all of my account information every time that I log in so that I can see how my net worth or paying off my loans is going. I am worth negative tens of thousands of dollars. That's old news, but it's nice to see it change for the less negative. For me simply seeing the numbers helps me make the numbers a little less terrible to look at by applying money where it makes the most difference.

Additionally relating to money, I've done some reading about history and it is not that hard to make substantial profits in the stock market. From a mathematical point of view there are a number of quarterly published variables which indicate that certain stocks are worth more than the price that you have to pay for them. It's not physics, so you will not get the same reaction every time. However, it is statistics, and if you play the numbers in enough quantity for long enough, according to the history of the stock market, you will make money. I'll write more on that in the future.

I hit a deer with my van. It has a huge dent in it and I would take a picture except that it's dark out right now. I'll do a post about the six accidents I have had in the last nine years.

Finally, in news relating to the book I am writing, I passed 48,000 words and 100 pages this week. That's 100 pages of single spaced writing with only four pictures and four pages of contents and title stuff. I am very excited about how well that is going. Although, I don't have an agent, much less a publisher, and I have not done any speaking engagements yet. So I have a long way to go, but I feel I am on the right path. My goal is to have a rough draft finished in the next few weeks. I do not have too much more left to add. I am sure that things that I have written thus far could be a huge help to others in their early 20s tackling unemployment, underemployment and misemployment.

Oh and one more note along the investing lines, about a year ago I solicited investors for Janzen Gear. I had a few bites but did not reel in the kind of investor that I was looking for. I am thankful that I did not find an investor at that point in my life. I learned a lot about product costs and failure. The hangboards are a much better situation. I am able to fund the costs out of my own pocket, and thus will put all the profits back into my pocket, or rather into manufacturing more. This product has a much greater ability to generate profits from batch one (ten hangboards). The ice axe would require huge batches (hundreds and ideally thousands) and even lower profit margins (although not much lower) and required safety testing. I just did not understand all of those challenges a year ago, yet it makes a huge difference in business. Also, running this as my second job allows me to think small. I am not relying on Janzen Gear to pay my bills. It allows me to deal in smaller volumes with lower profits than the big boys. Which means a high value product for the price and the prestige of limited quantities.

Thursday, December 9, 2010

I am Awesome!

Sometimes I have to tell myself that to avoid depressing thoughts. Specifically, applying for jobs! Finding a job has to be the worst job there is.

One of the things that I started doing a few months ago was attaching a sample of my work. People can say anything, but can you show what you do? You want to actually know what I can do? Well look at this:

An Abaqus finite element simulation frame taken 10 seconds into the quenching operation during the heat treating process of a transmission ring gear made of Pyrowear 53 showing the percent austenite in the steel.

I have close ups and other examples if necessary.

Wednesday, November 10, 2010

Do I Start to Lie?

I am a terrible lier. Ask anyone. A typical lie will manifest itself about once every two months humorously around my friends which will be followed by myself saying ten seconds later, "I'm sorry. That was a lie..." just incase they did not get the joke and I will explain the truth.

I was taking a true and false quiz for a position at an aerospace company. I was applying for an engineering job. The position was a statics load engineer. One of the questions was, "Do you have a masters degree in Aeronautical or Aerospace Engineering?" I answered "False" because of course I do not have that degree. I have a masters in Materials Science and Engineering. As I stared at the job title and the question I thought, 'Really? A master's in Aeronautical or Aerospace Engineering would know something about static loads that I don't?'

This is not nearly the first question that I have answered "wrong". I often answer questions about specific programs that I have used. Many aerospace companies use CATIA, a CAD and FEA software package. I have not used CATIA but I have used SolidWorks, ProEngineer, AutoCAD and Abaqus as well as creating MatLab simulations. How hard would it be for me learn CATIA? I am 99% confident that in less that one business day I could create a beam and bend it in a finite element simulation. Sure that is very simple to an experienced user, but considering I have never touched the software that would be impressive. I have spent so much time learning different CAD programs and a fair amount of time learning FEA that switching to a new system would be measured in hours or days instead of weeks and months and even years for a true beginner.

So when I am asked how much experience I have with CATIA and I answer "none" I can feel the recruiter passing my application into the junk pile. Interestingly enough CATIA and SIMULIA (the company that produces Abaqus) are owned by the same company. Lest one of my readers think that my education was lacking I would not change a thing. Abaqus supports DANTE which is a very powerful piece of software for heat treating steels and something that CATIA does not do, as far as I know. CATIA can model kinetics, however, I am not sure to what extent it covers. Steel, particularly the Pyrowear 53 I was working with, has fairly complex heat treating kinetics compared to most things.

Wow, that got detailed.

Anyway, I'm not going to lie. I can't. Also, it doesn't make sense. Despite the fact that I could probably pass myself off as knowing CATIA (let's be honest, companies don't actually test your technical skills until you start working; they only ask questions about your technical skills) however, truthfully I don't know CATIA.

Frustrating to say the least. It's like asking if I drive a Ferrari. Well, I've never driven a Ferrari. Does a Porsche count? No. Once again I wonder, do nice guys finish last?

Actually, finishing last would be fine with me. At this point it would be nice to know that I even get to start the race.

Tuesday, October 27, 2009

A first fruition of my work!

I'm working on this complex model of half of a ring gear. I've been working on it for several weeks, probably more like months. The last two weeks I've been working on associating the mesh with the geometry which is a problem with bottom-up meshing sometimes. In short, the mesh made up of a finite number of elements is not the same as the geometry that you planned. They may look the same but when you take a closer look you will see slightly off angles in the range of .1 or .2 degrees away from parallel. There are also curves that are approximated as strait lines that you need to associate with the geometry. So you must select Mesh > Associate Mesh with Geometry..., then select the feature (face, edge, etc. ) on the geometry, then select the mesh (using "by angle" instead of "individual" works better but keep the degrees like .3 or something low) then click done and the face or other feature you selected on the mesh is now associated with the geometry.

So I just finished associating the mesh with the geometry on my 400 faces or so and Abaqus successfully wrote out the input file (which I still have to edit so that if actually runs)! The point is I am hours (perhaps days) away from a truly fantastic carburizing simulation!

Tuesday, September 29, 2009

Stress!

The finite element stress simulations I create using Abaqus often have very interesting stress fields. The interesting thing about stress is that it is not just a number. It is several vectors, in fact it is actually a tensor. So this is way cooler than temperature because you can't just specify that those nodes are at a certain stress level. So that you can see here is the stress at element 1 in one of my simulations (all numbers are in MegaPascals):

Element: 1 Von Mises: 2.91804 Maximum In-plane: -153.946E-03 Minimum In-Plane: -2.99197 Out of Plane: 0. Maximum Principle: 0. Mid-Principle: -153.946E-03 Minimum Principle: -2.99197 Tresca: 2.99197 Pressure: 1.04864 Third Invariant: -2.90889 S11: -205.309E-03 S22: -2.94061 S33: 0. S12: -378.328E-03

Monday, September 21, 2009

Making Assumptions (in Abaqus)

At the conference I attended last week I was able to talked to the creators and owners of DANTE. It is a material database with kinetic phase transformation information that interfaces with Abaqus. What that means is that when Austenite transforms to Martensite and there is a volume change you can simulate that. (It is a really big thing in the heat treating world because only two companies have created software to do that.)

I talked to them about my specific problems and learned that they make many simplifications such as only using one or two heat transfer coefficients in each step on complex parts and simulating the interactions between parts by simplifying the geometry of the parts. I know those are two vague descriptions but I really should not delve into the details. The point is that they just made my job a lot easier. It is amazing how much a 10 minute conversation in person can be so much more informative than an email conversation or trying to read technical papers looking for the answer.

The moral of the story is: perhaps you can find the solution to your problem by simplifying the problem. Of course sometime it can not be simplified...

Thursday, September 10, 2009

Abaqus: How to Reduce the Size of your .stt file

Often .stt files can be larger than the .odb files. When you have a limited storage space it becomes important to try and reduce the size of your files. The way to do this is simple: increase the output frequency. This means that instead of writing the resulting data in every single time step to the .stt file only 1/5 or 1/20 or 1/1000 of the step data is written to the .stt file. I think this also makes the simulation run faster but I can not be sure. To reduce the frequency either specify when creating the output requests in Abaqus CAE or edit the input (.inp) file. Here is an example of how to reduce your output requests by editing the input file:

** OUTPUT REQUESTS
**
*Restart, write, frequency=25
**
** FIELD OUTPUT: F-Output-1
**
*Output, field, frequency=25
*Node Output
NT,
*Element Output, directions=YES
SDV,
*Output, history, frequency=25

The frequency could be reduced more or less until you are able to see the information you desire and have a reasonably sized .stt file. A higher frequency means fewer steps are output and your .stt file will be smaller. Also it is important to note that when viewing the time history results of a simulation that the beginning and end of every step will be show. That means that for a step that is ten seconds long you will be able to view the results of the simulation at 0.0 seconds and 10.0. That holds even if the output frequency is 1000.

Friday, August 21, 2009

Abaqus: How to Know if your Simulation is Running

As soon as you start a simulation you spend time waiting for it to finish. However, it is not obvious from Terminal (the program I use on my Mac) if the simulation is running or has stopped or ended. All you need to do is check the files in the folder or directory where you started your simulation. I use a simple program called Cyberduck. It is a file management system that allows me to navigate the servers I use (which are two buildings away) as well as download and delete files.

Now when a simulation is running in Abaqus 6.7 the files that will appear have the extensions: .stt, .msg, .odb, .sta, .res, .dat, .mdl, .log, .lck, .023, .prt, .cid, .com, .inp, and sometimes .fil depending on the simulation. The file name will be the same for all the extensions. When the simulation is over the .lck, .cid, and .023 files will disappear. That's all there is to it. Either you have those three files or you don't.

Tuesday, August 18, 2009

Asking the Right People the Wrong Questions

I've been struggling with an Abaqus problem recently and I asked one of the true experts of the field a question directed to what I thought the problem might be. He then answered my question with the answer to the question that I should be asking. I was totally looking in the wrong place.

I've said many times that I surround myself with great people and just draw off of them. This is another example where someone was able to answer my question, even though I wasn't really asking it. For someone that really knows their stuff it doesn't take much for him or her to understand your problem.

Find the right people in your life.

Tuesday, April 28, 2009

Abaqus: Create Animations

So you spend half an hour loading Abaqus and getting it started to watch the movie of the simulation you ran last night and it was a good simulation so you need to make a movie so you can show your boss or professor or whoever. Here is how to make an .avi, Quicktime, or VRML movie. 
1. Select the Visualization module if it isn't already selected. 
2. Select the Result drop down menu and select the desired result to view. In this example I selected Field History > NT11.
3. Select Animate > Time History ( you can select other options but this is what is most commonly used)


4. Select Animate > Save As...
5. Complete the Save Image Animation box. Be sure to make a unique name and select the file type that you want (.mov in this example because I've had lots of problems with .avi files). Select the Capture: Current Viewport or All Viewports option if you have multiple viewports. You can select the Capture Viewport Decorations and Capture Viewport Compass so that each frame has more information and you can tell what step you are in at any given time. Finally select a very low frames per second rate. I usually do one or two frames per minute because I spend hours working on a simulation that I want other people to watch it for 30 seconds and not 3 seconds. This of course depends on your output rate but for any simulation with many steps your output rate will be low to conserve gigabites so make
 your frames go slowly. An art major once told me that it takes at least 15 seconds of looking at a picture to take in what is happening. 

6. Watch your movie!

Thursday, April 23, 2009

Easy Finite Element Modeling

It doesn't exist. For anyone that thinks that setting up a computer simulation is something to do in an hour and then let it run for four hours and look at the pretty pictures you are misinformed. I spent five hours this morning running Jominy end quench blocks in Abaqus using different quenching recipes. It is one thing to create a part or a mesh or several steps or interactions but getting them all to work together and give you the same results that hundreds of scientific papers have proven is a little more challenging. If your elastic modulus is off by one order of magnitude because you missed a centimeter to millimeter conversion it could take you hours to figure out why the wing doesn't flex. 

Modeling isn't easy or fast. Although, I can run a Jominy end quench test in only two minutes after changing the heat transfer coefficients compared to the three hours of actual time to complete a test in real life. 

While my blog has no theme except the challenges I face or stories from my life as a 22 year old in 2009, I post about Abaqus because I spent hundreds of hours figuring things out the hard way so if I can give people a few tips and save them ten hours this world just may be a better place.

Wednesday, April 22, 2009

Abaqus: Modules

I started to get a few hits of people looking for basic Abaqus information so I'm going to post several posts about the basics. First, Modules. There are ten modules in Abaqus (version 6.7 at least): Part, Property, Assembly, Step, Interaction, Load, Mesh, Job, Visualization, and Sketch. It is important to be in the right module when you do certain things like when you use the Tools drop down menu. Below you can see where the module drop down menu is so that you can change the module as needed.


A short description of each module:
  • Part: Used to create the geometry of the part. It is basically a simple CAD tool. You can import more complicated models from ProE and Solidworks from File > Import > Part.
  • Property: Used to create the material properties that you will use in the simulation. Be sure to create a section (with your material) and assign the section to the part.
  • Assembly: Used to instance the part meaning if you have several parts you can put them in the same assembly but if you have one part it still has to be in an assembly. You can then either mesh on the part or the assembly.
  • Step: Create the simulation steps required for your simulation. 
  • Interaction: Used to create interactions between parts or between a property and a part. I use this in heat treating to describe the property of the heating and quenching fluids. 
  • Load: Used to create loads, boundary conditions, and predefined fields (like initial temperature).
  • Mesh: This module is for creating finite element meshes.
  • Job: Simply go to Job > Create then (I prefer to go to) Job > Write Input and then you can do the rest of the editing using kwrite and going through the input file (.inp file). 
  • Visualization: Used after your analysis to see distortion and whatever else you are looking for.
  • Sketch: It is like the Part module but for sketching. I don't use it.
Leave a comment if there is something specific you want me to write about.

Tuesday, April 21, 2009

Abaqus: Deciphering .dat files

Understanding .dat files is the first step to understanding why your simulation didn't work. First you will know the simulation didn't work because there is an .0db_f file or you look at the .odb file and the simulation ends before it gets to the end of the last time step. Second open the .dat file and scroll to the bottom and it will tell you the total number of errors. Just because it says you have 15 errors doesn't mean you have 15 problems. Most of the time one error in the program will show up multiple times. Third scroll through the .dat file finding where it lists the errors and try to correct them with the .inp file open at the same time. Use kwrite instead of kedit to view and edit multiple large files at one time. In case of a very large file you might have to open it with a text editor.

For example if you define the element type to be C3D8 instead of DC3D8 for a heat transfer analysis you will end up with perhaps eight errors on the .dat file. Often the problems are created by editing the input file and not copying and pasting the correct value. 

For example if you want to apply a load to PickedSet12 in one of the steps be careful to make sure if is _PickedSet12 or just PickedSet12 by looking into the Assembly section and noting the number of underscores that precede the set name. If there are two underscores in the Assembly section then you need one underscore in the Step section. Similarly one underscore in Assembly means no underscore in Step. It is important to make sure that what you reference in each step is the same thing that the program reads  from the Assembly information. 

Another common problem can be not defining hourglass stiffness. Solve that problem by deleting an R at the end of the element type. For example C3D8R becomes C3D8.

Friday, April 17, 2009

Abaqus: Selecting Inside Surfaces

If you need to select an interior plane or surface but you are having trouble there is a way. First select the options button on the bottom of the screen between the drop-down box for how you select surfaces and the Done button. 

Second, select the surface type box within the Options box. The left option is all surfaces possible, the middle box is only interior surfaces, and the right box is exterior surfaces.

Thursday, April 9, 2009

Abaqus: Bottom-up mesh example

So swept meshing and structured meshing have failed or aren't available but bottom-up meshing is complicated and hard right? Not as much as you might think. Here is a sample of how I meshed a region of a part using bottom-up meshing technique. This is using Abaqus version 6.7 and I'm skipping the parts about seeding, partitioning, and element type that you have to do to make a mesh. Be sure you seed the region before you mesh it or it will not mesh.

Step 1: Select Mesh > Controls... > Hex (in this case it could be something else but hex looks the most professional) > Bottom-up. Then you select the region (partition, cell) of the part you wish to mesh with bottom-up technique.



Step 2: Click on Mesh > Create Bottom-Up Mesh... Then select the cell (region, partition) that you just gave mesh controls to. The "Create Bottom-Up Mesh" box will appear.


Step 3: Select the Source side. Click "Done" when you have selected the source side. This is the side where the mesh will be created in two dimensions, essentially the bottom of the part, so that the mesh can be swept through the volume.
Step 4: Then select at least one connecting side in this example I choose five connecting sides. The more sides you have the more structured the mesh will be. When you have selected the side(s) click "Done". In some cases you have have to specify a Target side but in general is is not necessary.

Step 5: Click "Apply" in the "Create Bottom-Up Mesh" box and you are done! So that you know the details this mesh had 2304 elements, with 0 analysis errors and 48 analysis warnings. (That means it's pretty good.)


If you have any questions just ask, although I might not respond quickly.

Monday, April 6, 2009

Abaqus: loads

When selecting surfaces for loads it is possible to select multiple surfaces at once by selecting the "by angle" option on the drop down list at the bottom of the screen.  At the bottom of the screen it says: Select surfaces for the load (drop down box). First select the by angle option and then an angle (default is 20 degrees). Then select a surface and all adjoining surfaces within 20 degrees of the plane you chose will be selected. When you have a slow computer or internet connection this really helps speed things up. 

When specifying fluxes be sure that the flux you specify is in the correct units (like kg/mm^2/s for a surface flux instead of something like g/cm^2/s). Units in Abaqus can drive people crazy because Abaqus doesn't care if the numbers are logical or not.