Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

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

run time error 1

Status
Not open for further replies.

ajroc

Aerospace
Jul 14, 2006
14
Hello

I am still struggling with my model. I have eliminated bolts that are not of interest to me and instead used bonded contact to join parts. I have run the model using draft elements to troubleshoot, and the model solves with no problem.



Using high quality elements the problem takes a long time to solve (as expected) – I left it running over night and came in this morning to this






We have a screen saver that engages after the computer is left untouched for about 5 mins. I intentionally locked the system per the advice of my IT guy. Any ideas what could be going on?
 
Replies continue below

Recommended for you

Hi,
I see the dimension of your problem is relatively limited: less than 100000 nodes with 3DOF/node would probably fit in about 700-800 MB of free RAM space. The error reported seems like a memory allocation error, where the solver tried several mem adresses before finding them all unexpectedly unavailable: this can happen if Windows writes "something" in these allocations which were at first alocated by STAR.exe (the Cosmos solver).
So, first of all check that you have about 700 MB free in RAM before launching the solution (this is probably a useless advice, because otherwise Cosmos would have warned you that it was running "out of core"). Then, before letting Cosmos run overnight, stop any other running program and, if possible, any useless Windows service, INCLUDED the screen-saver. In my opinion, this is very important. "Heavy" processes that use a lot of memory (and so, a lot of memory BLOCKS) can be severely disturbed by useless Windows activity.
Hope this helps...

Regards
 
Thanks for the help! Unfortunately due to our security policy I cannot disable the screen saver (I am working on changing that policy, but do not see it happening anytime soon). Any other suggestions?
 
It may be more work but I would start debugging the model such as:

1) perform a modal analysis using the sparse solver and activate the soft springs options. If it solves it may indicate where the problem is in the model.

or

2) Suppress most of the parts in the assembly except two or three parts and then retry the analysis. If it works then add more parts or if it does not remove a part.

I often get a runtime error if the contacts are not working.
 
You might also consider saving the assy as a part and running it in part mode. This could fix any possible bonding errors you might have.

Boggs
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor