Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations waross on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

[ABAQUS] No results

Status
Not open for further replies.

JoeJoeJoe94

Nuclear
Jun 18, 2020
8
Hi guys,

I'm using an object fixed at one end with a pressure on the other. When I use a very small section of that object, it runs fine (please see links), but using a larger section of the object, the job runs but displays no deformation at all.

The larger mesh has 400,000 elements, is this just too much?

For context, I've used a self made python script (possibly a cause of problems) to turn topographic data from an array into an STL file (with sides and a base), I then pass this into meshlab to get rid of duplicate faces/vertices, turn it into a BRep and fill any holes. I export it as a .step file which can be imported into Abaqus. I'm using the same process to produce the small area, which works fine, but the larger area doesn't. My end goal is to estimate different stress concentrations in different surfaces.

I appreciate any suggestions, thank you.

 
Replies continue below

Recommended for you

The image with or result shows the model at increment 0 - step time 0. So the initial state. Switch to another frame/increment.
 
Thank you, I'm having trouble figuring out how to switch to another frame/increment. There is a warning that 11 elements are distorted, could this have stopped it recording more than one increment?

When I click on monitor, after the job had completed it says "ODB output written for step 1 frame 0" but not for other frames.
 

It looks like only one frame is produced for the larger model, but two are for the smaller one. I can't find any differences in the setup to explain this.

The field output requests are the same.
The steps are the same.
The loads/ boundary conditions are the same.

All I can think of is maybe it is crashing due to distorted elements and not actually running the second step.
 
Open the .sta files of the two jobs in the work directory with a text editor and you'll see how many increments were solved. Maybe the job with no result aborted without any successfully solved increment.
 
Thanks a massive amount guys I've figured it out.

-No .sta file was being produced so I added in another step (so there was initial + step 1 + step 2) to try and force the production of a .sta file (or something). Both steps came out fine. No idea why.

Solution: Added another step and it worked.
 
If it works for you - fine. But I don't think that this is a proper solution. There is something else wrong. Upload the input file if you want to know what is actually going on with your model.

 
The analysis runs fine and I can see results for both steps.

But the deformations are very large compared to the model size. You should check your definitions.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor