Basic Flight Simulation
|
The current User's Guide is very much a work in progress, any help would be greatly appreciated! |
Basic Flight Simulation
In this section we'll take a quick look at running a basic Flight Simulation.
Simulations are often used by mid- and high-power rocketeers to determine what altitude a rocket and motor combination will attain, in order to keep it below the maximum launch waiver altitude, or below cloud cover, or just so it won't disappear miles downwind on the breeze.
They're also often used to determine how long an ejection delay needs to be, if you're using motor ejection.
You may not have simulated flights on your Estes A, B and C motors, but once you start buying and assembling some of the many motors you could choose for mid- or high-power rocketry, you'll need to simulate regularly.
OpenRocket can do the basic simulations for altitude, velocity off the rod/rail, optimum delay with just a few clicks. But if you'd like to get more deeply into simulation, OpenRocket can graph flight parameters, take local wind speed and direction into account, and a lot more.
If you already know how run basic simulations, you can jump to the next section.
The Flight Simulations Window
Below you'll see a picture of the Flight Simulations window. We're using the A Simple Model Rocket example here, and it includes the list of simulations pictured.
In the Flight Simulations window, you'll see the simulations listed, initially in Name order. Note that the second column is "Configuration" - the name of the configuration used in the sim, usually named for the rocket motor used in that configuration. The remaining values in the simulation's row are calculated by "running" the simulation. You can run one simulation by selecting a sim and clicking the Run simulations button:
...or run them all at once by selecting more than one...
...or run them in any combination you choose. Below you'll see the Simulation Results. Note that the indicator at each simulation has turned green, and that beside every working simulation, you'll see a check mark.
Note also that Simulation 3 has an exclamation point instead of a check mark. This is because the simulation reveals that the motor delay is so short that the rocket will be moving very fast when the parachute comes out. This will usually cause severe damage to a rocket - called a "zipper", where the pulled-taut shock cord cuts a rough slot in the tube as the chute deploys while the rocket continues to move rapidly forward.
OpenRocket can detect several conditions which will mark a simulation as non-working. For example:
- Too slow off launch rod - unstable launch
- Too short a delay - early deploy of chute, zipper, damage or separation likely
- Too long a delay - late deploy of chute, zipper, damage, separation or hard ground-hit likely
- Ground-hit velocity too high - damage, and potential danger to ground personnel
These are common failure conditions, but are not intended to be an exhaustive list.
Getting a Good Simulation
OpenRocket simulates an ideal rocket flying in an ideal virtual world. It's a model of how a rocket interacts with the physics of the real world. As a model, it's useful, but imperfect. OpenRocket's sim can vary from reality due to many things, for example:
- Local air density at launch time (a function of local temperature and barometric pressure)
- Manufacturer variations in motor components
- Imperfect match between launch angle or heading, and simulation
- Local wind speed, direction, gust mismatch from simulation
- Varying wind speed at altitude, or wind shift during flight
- Performance under stress of simulated components (fin flutter, etc.)
- Imperfect match of simulated model to real model
That, again, is not an exhaustive list, but the last item: Imperfect match to real model counts for a lot.
It's probably obvious that you have to get the simulated model's weight right to get a good simulation, but what about its weight distribution? What about its diameter, the match of its nose cone and fin profile to the actual model? Even the texture of surface components can cause variation in drag as the rocket flies.
Your best simulations will come from building the simulated model before you build the actual rocket. You'll want to weigh every component. And once components are assembled, you'll want to weigh each section to check your work (glue, filler and finishes add weight, too.)
A digital kitchen scale can be useful to weigh each part as you create a simulation of all the parts of your rocket. You'll also need to measure thicknesses and lengths. You can obtain inexpensive digital calipers which are fine for this measuring purpose, from suppliers like Harbor Freight.
Working in the Rocket design window, weigh and record the weight of each component as you model it. Try and choose the correct material to reflect the density and mass of the actual component. Often, creating a more-correct material (using the "Custom" option of the Component Material menu) is a better choice than using weight overrides, because the weight override may not reflect the correct center of mass of the overridden material.
Include every component the actual rocket uses, except for the motor: motors are set in the Motors & Configuration tab. If a part is too light to weigh, weigh multiples of the part, and divide by the number you weighted. If you need to weigh a short bit of shock cord, weigh 20 feet of it, divide by 20 to get the weight of 1 foot.
If you begin a model with a downloaded OpenRocket (.ork) or RockSim (.rkt) file (OpenRocket can open both), check that the downloaded file's components match your own, and that the specified weight and center of mass match those of your own model. Often, downloaded files feature mass overrides to get the center of mass of an imperfect OpenRocket model to agree with that of a real-world rocket. These overrides may get the rocket's weight distribution all wrong, so it's important to adjust the downloaded model to match your rocket exactly.
A very good simulated design can go a long way to predicting the correct eject delay and altitude as-flown.
The better your model, the better the prediction, though note that this author finds that OpenRocket predicts a bit more altitude than you'll attain most of the time (an average of 29% more in an informal calculation of a dozen of my logged flights - though the variance ranged from dead-on to 43% off).
