Advertisement
The Global Settings Page
The Global Settings page is used to change settings that are either hardware-specific or are not
generally changed from flight to flight. You get into this page by clicking on the "Settings"
link on the Status Page:
Launch Detect Altitude (LDA) (100'-500' by 50', default 200')
This setting allows you to select at what altitude the Proton decides that a valid flight has started.
The 200' default is good for most flights. However, there may be some cases in which you may
want to turn it up, and some very special cases in which you may want to turn it down.
If your flying site is subject to wind gusts, you may want to turn it up a bit so that when the wind
gust subsides the decrease in pressure isn't viewed as the rocket ascending. That's not likely to
happen, however, because we filter the readings to prevent this (and other similar occurrances).
You may also want to turn it up if you increase the Launch Samples per Second.
If you have a very low flight you may want to turn it down, although generally we don't
recommend it.
Ascent Samples per Second (10,15, 20, 25, 30, 33 samples/sec. , default 20 samples/sec.)
This setting allows you to select the number of samples per second that are taken from the time
that you arm the Proton until it detects nose-over. The default setting (20 samples per second) is
adequate for most flights. However, there may be reasons why you want to turn it up or down.
For example, if you have a very short-burn motor (like a CTI V-Max) you may want to turn it up
to 33 samples per second to make the velocity and acceleration figures more accurate. If you
have a very long-burn motor you may want to turn it down to 15 samples per second, although
20 should be fine. Note that increasing the sample rate decreases the amount of memory at the
expense of flight data accuracy... more on that later.
Descent Samples per Second (1, 2, 4, 5, 8, 10 samples/sec, default 2 samples/sec.)
The setting allows you to select the number of samples per second that are taken after nose-over
is detected. When you're coming down, you're generally not going to be going very fast relative
to your velocity going up, even if you freefall for a few seconds and the FailSafe kicks in.
Consequently, there's really no reason to have the same high rate of sampling that you use for
the ascent part of the flight. Reducing the sampling rate after nose-over saves a lot of memory,
and allows you to record longer flights. For most flights, the default 2 samples/sec. rate is fine.
If you are going over 20,000' you may want to take this down to 1 sample/sec... the reduction in
data accuracy by reducing the sampling rate is minimal.
- 26 -
Advertisement
