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!

Algor DOF errors

Status
Not open for further replies.

bbolton

Mechanical
Jun 9, 2003
1
Hello all,

I'm new to this forum, so bear with me... I'm having issues with an old version of Algor, specifically I get an error message saying "Model not tied down enough" with the number of the offending DOF. However, I don't know how to check what node is associated with this DOF, the solver terminates before printing anything useful off, even if I specify the PRTNEQ toggle.

As I said, I'm using an old version of Algor, circa about 1996...Superdraw is version 3.48-WIN. The model I'm trying to solve uses plate elements...essentially the model is retrained at one end and at the other a force/couple is applied to induce a moment in the structure.

Any help would be greatly appreciated!

 
Replies continue below

Recommended for you

Since no one has replied to your question, I will try to hep you. Fist of all, I have never used Algor, but have done a lot of FEA over the years. As Adolph Hitler was fond of saying, (in German of course) "there are two possibilities" :

1. You have underconstrained your model
2. There is something wrong with the software

The second possibility is unlikely, but possible.

Exactly how did you constrain your model ? It must be fixed to ground so that at least all six bodily displacement degrees of freedom are constrained (three translations and three rotations). One implication of this is that, with plate elements, if you are fixing just one edge, you must in many cases constrain at least some of the rotations at the edge nodes as well as the displacements. Maybe you neglected to do this. You shouldn't need to constrain the rotations in the plane of the plates. This assumes that your version of Algor has automatic removal of uncoupled (and unused)degrees of freedom - most modern codes do - but this is where my lack of specific Algor experience is a problem.
Maybe you have figured it out by now - but good luck anyway.
 
I just spent 2 days working with this exact problem.

We had our model fully constrained, but our geometry was not correct. Algor does not like elements runing into other elements where there is not an endpoint.
Try constraining first, but if it does not work.
Start looking to change a few lines here and there to make them more ALgor friendly.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor