Rotordynamic Analysis-code bug

[PearlRock]

Hey guys, I've been asked to do a rotordynamic analysis in ANSYS. I'm not terribly familiar with the software (v12.1), so I started searching their help topics. I found the following helpfile which with some modifications can fairly accurately describe my system.

https://www.sharcnet.ca/Software/Fluent13/help/ans_adv/Hlp_G_ADVRSDSMP3.html

Anyway, I quickly found out the input code listed has a couple bugs in it. I fixed the first one, but the second one is why I'm here.

After reviewing the output, I am pretty certain what is happening is that Body 1 is being displayed on body 2 trajectory path. Body 2 is being displayed on body 1 trajectory path.

I'd like to know more specifically which area of the code I should focus on in order to fix the problem. I don't think the post-processing has an error. I think the initialized body definitions are also fine. Between the beginning and the end though...some areas I'm a little fuzzy what's going on. Any help on fixing the output would be much appreciated.

-PearlRock

 

[PearlRock]

AAAAAAAAAHHAAAAAAHHH!


I got it. In the example, they display the trajectory and animated simulation at a frequency of 262. But the code posted online has an animation frequency of 500. It just so happens that 500 appears to have a reversed trajectory path as the frequency at 262. Change the frequency back to 262, and everything looks like the web example. Very interesting...

Anyway, I am glad this is solved.