If you have an extreme flight, say 50,000’, it may take a bit longer to get up there, let’s say 45
seconds. That’s 900 samples, leaving 1100. If you take the descent sample rate down to one
sample per second (reasonable since the events are happening relatively slowly and the air is
pretty thin at 50K), you still have 1100 seconds, or over 18 minutes. No way it’s gonna take that
long to come down, unless for some reason the main comes out near apogee. At a conservative
50 ft/sec average speed under drogue, it’s going to take 1,000 seconds, leaving you with at least
100 samples. Remember that at that altitude the air is very thin, so you’re going to be coming
down faster near apogee than you will be when the air thickens as you descend. It’s very likely
that you’re going to be using a lot less memory than that.
So, as you see, there’s plenty of memory for just about any flight scenario if you manage it
wisely. For just about any flight under 30,000’, just leave it at 20 samples per second for the
Launch rate and 2 samples per second for the Descent rate, and you’ll be fine.
Auto-Arm
Values: Yes/No, default No
This controls if the Quasar will enter the automatic arming sequence after power is applied. See
the discussion of auto-arming previously, in the Arming Your Quasar section.
Name
Text box, default is blank
This is an 8-character field that is sent out along with the telemetry data. This would typically
be used with the 70 cm Ham version of the Quasar, you should put your Ham call sign here,
satisfying the FCC’s requirement that your call sign must be transmitted “periodically”.