×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

Floworks stops before physical time is reached

Floworks stops before physical time is reached

Floworks stops before physical time is reached

(OP)
I'm doing a time dependent study for a brake disc under pulsating heat energy loading.

Basically 3 sec. heat input -> 3sec. cool down -> 3sec. heat input, and so on. Solutions finish condition is solely on physical time in the calculation control setup.

With rotation enabled(even as low as 1rad/s), FW progresses with equal time steps until correct physical end time is reached, so all good.

But, when i disable rotation, FW suddenly "jumps" half way in the sim. to the physical end time, with the notification that physical end time is reached.

Obviously this is not correct and this is confirmed when i plot the results (Temp vs time). The pulsating load is not even recognizable(basically one continous load application)?!

I never had this "problem" before.


I realy cannot figure this one out, anybody?  

RE: Floworks stops before physical time is reached

(OP)
The "problem" seems to lie in the assembly somehow. The problem dissapears if i analyse the brakedisc as a sole part.

Then the solver proceeds normally with the pre-determined timesteps of 0.1s.

As soon as i add another component(the rim) and analyse as an assembly, things go wrong, i.e. the timesteps are disregarded at some stage in the simulation. It looks like the solver for some reason increases the timesteps dramatically (0.5s->1.5s->5s->15s) in assembly setup, as apposed to the pre-determined timesteps of 0.1s for the part setup.

Simply put.. i don't get it.
 

RE: Floworks stops before physical time is reached

(OP)
I seem to have figured it out myself, for those that may be running into this in the future also.

Insufficient  mesh density seemed to be the problem. Pls see the attachment.

With low mesh density, the solver simply "cuts out" some time in the simulation and seems to extrapolate results linearly for some reason and in the process disregarding the toggled load steps.

 

RE: Floworks stops before physical time is reached

It's a finite difference solver so in order for it to get meaningful solutions the mesh has to be fine enough to pick up fine detail in the model. Prepping a model for FloWorks should concentrate on removing unnecessary fine detail.  

TOP
CSWP, BSSE
www.engtran.com  www.niswug.org

"Node news is good news."

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources