OpenRocket famously (?) doesn't support ring tails, or tail rings, or ring fins, or whatever you want to call them. It's easy enough to use an internal tube to produce a proper visual representation and mass/CG calculation but what to do about CP and drag has been a bit of a mystery. I just tried a quick experiment and the results are interesting.
Here's what I've been doing until now. Given:
I have been creating what I think of as a "ring equivalent" set of trapezoidal fins with the following dimensions:
In my OR files I usually make those fins *almost* transparent, so I can just barely see that they're there but they don't ruin the 3D renders.
It occurred to me recently to try a different approach: use a single tube fin to represent the ring. In order to position it properly I need to attach it to a single pod with a phantom body tube.
I created a trivial design and compared the two approaches.
First, with the ring-equivalent fin set. Key metrics are CP = 10.685", and Cd = 1.454:
Now the tube fin, which yields CP = 10.651 and Cd = 1.152:
Mass and CG come out equal, which is no surprise. More interesting is that the CP comes out almost exactly the same (within a fraction of a percent), but drag is quite a bit lower with the tube fin. The difference in drag is large enough that I am now very interested in trying to figure out which drag calculation is likely to be closer to correct. Each approximation has its own obvious errors. Maybe the answer is somewhere in between? I suppose a comparison to Rocksim would be useful, anyone want to try it out?
Please note that all this is based on intuition and seat-of-the-pants calculations. I'm just trying to figure out a straightforward way to model my oft-used tail rings until OR supports them natively.
Here's what I've been doing until now. Given:
od = diameter of ring
id = diameter of tube inside ring
len = length of ring
th = thickness of ring
I have been creating what I think of as a "ring equivalent" set of trapezoidal fins with the following dimensions:
root cord = len
tip chord = len
sweep length = 0
thickness = th
height = od - id
number of fins = ((od-th)*PI) / height
Let's talk about those last two. What I am aiming for here is a set of fins that has the exact same total area as the ring, with the same average distance from the inner tube. This is entirely based on intuition and I have no idea if how accurate it might be. I have to think it's at least "in the ballpark" for typical ring configurations. It has worked for the ring designs I have done so far, where "has worked" means the rockets have been stable; I have no easy way to know how accurate my calculations are. Note that I only apply this when the difference between ID and OD is large enough that it seems like there will actually be airflow (this eliminates, for example, the two rings at the back of the Sirius Eradicator).In my OR files I usually make those fins *almost* transparent, so I can just barely see that they're there but they don't ruin the 3D renders.
It occurred to me recently to try a different approach: use a single tube fin to represent the ring. In order to position it properly I need to attach it to a single pod with a phantom body tube.
I created a trivial design and compared the two approaches.
First, with the ring-equivalent fin set. Key metrics are CP = 10.685", and Cd = 1.454:
Now the tube fin, which yields CP = 10.651 and Cd = 1.152:
Mass and CG come out equal, which is no surprise. More interesting is that the CP comes out almost exactly the same (within a fraction of a percent), but drag is quite a bit lower with the tube fin. The difference in drag is large enough that I am now very interested in trying to figure out which drag calculation is likely to be closer to correct. Each approximation has its own obvious errors. Maybe the answer is somewhere in between? I suppose a comparison to Rocksim would be useful, anyone want to try it out?
Please note that all this is based on intuition and seat-of-the-pants calculations. I'm just trying to figure out a straightforward way to model my oft-used tail rings until OR supports them natively.