+ === Understanding Beeps
+
+ Altus Metrum flight computers include a beeper to
+ provide information about the state of the system.
+ ifdef::telemini[]
+ TeleMini doesn't have room for a beeper, so instead it
+ uses an LED, which works the same, except for every
+ beep is replaced with the flash of the LED.
+ endif::telemini[]
+
+ Here's a short summary of all of the modes and the
+ beeping
+ ifdef::telemini[(or flashing, in the case of TeleMini v1)]
+ that accompanies each mode. In the description of the
+ beeping pattern, “dit” means a short beep while "dah"
+ means a long beep (three times as long). “Brap” means
+ a long dissonant tone.
+
+ .AltOS Modes
+ [options="border",cols="1,1,2,2"]
+ |====
+ |Mode Name
+ |Abbreviation
+ |Beeps
+ |Description
+
+ |Startup
+ |S
+ |battery voltage in decivolts
+ |Calibrating sensors, detecting orientation.
+
+ |Idle
+ |I
+ |dit dit
+ |Ready to accept commands over USB
+ ifdef::radio[or radio link.]
+
+ |Pad
+ |P
+ |dit dah dah dit
+ |Waiting for launch. Not listening for commands.
+
+ |Boost
+ |B
+ |dah dit dit dit
+ |Accelerating upwards.
+
+ |Fast
+ |F
+ |dit dit dah dit
+ |Decelerating, but moving faster than 200m/s.
+
+ |Coast
+ |C
+ |dah dit dah dit
+ |Decelerating, moving slower than 200m/s
+
+ |Drogue
+ |D
+ |dah dit dit
+ |Descending after apogee. Above main height.
+
+ |Main
+ |M
+ |dah dah
+ |Descending. Below main height.
+
+ |Landed
+ |L
+ |dit dah dit dit
+ |Stable altitude for at least ten seconds.
+
+
+ |Sensor error
+ |X
+ |dah dit dit dah
+ |Error detected during sensor calibration.
+ |====
+
+ Here's a summary of all of the Pad and Idle mode
+ indications. In Idle mode, you'll hear one of these
+ just once after the two short dits indicating idle
+ mode. In Pad mode, after the dit dah dah dit
+ indicating Pad mode, you'll hear these once every five
+ seconds.
+
+ .Pad/Idle Indications
+ [options="header",cols="1,1,3"]
+ |====
+ |Name |Beeps |Description
+
+ |Neither
+ |brap
+ |No continuity detected on either apogee or main igniters.
+
+ |Apogee
+ |dit
+ |Continuity detected only on apogee igniter.
+
+ |Main
+ |dit dit
+ |Continuity detected only on main igniter.
+
+
+ |Both
+ |dit dit dit
+ |Continuity detected on both igniters.
+
+
+ |Storage Full
+ |warble
+ |On-board data logging storage is full. This will
+ not prevent the flight computer from safely
+ controlling the flight or transmitting telemetry
+ signals, but no record of the flight will be
+ stored in on-board flash.
+
+ ifdef::easymega,telemega[]
+ |Additional Igniters
+ |four very short beeps
+ |Continuity indication for the four additional pyro
+ channels on TeleMega and EasyMega. One high tone for
+ no continuity, one low tone for continuity. These are
+ produced after the continuity indicators for the two
+ primary igniter channels.
+ endif::easymega,telemega[]
+
+ |====
+
+ ifdef::radio[]
+ For devices with a radio transmitter, in addition to
+ the digital and APRS telemetry signals, you can also
+ receive audio tones with a standard amateur
+ 70cm FM receiver. While on the pad, you will hear
+ igniter status once every five seconds.
+
+ .Pad Radio Indications
+ [options="header",cols="1,1,3"]
+ |====
+ |Name |Beeps |Description
+
+ |Neither
+ |½ second tone
+ |No continuity detected on either apogee or main igniters.
+
+ |Apogee
+ |dit
+ |Continuity detected only on apogee igniter.
+
+ |Main
+ |dit dit
+ |Continuity detected only on main igniter.
+
+
+ |Both
+ |dit dit dit
+ |Continuity detected on both igniters.
+
+ |====
+
+ During ascent, the tones will be muted to allow the
+ telemetry data to consume the full radio bandwidth.
+
+ During descent and after landing, a ½ second tone will
+ be transmitted every five seconds. This can be used to
+ find the rocket using RDF techniques when the signal
+ is too weak to receive GPS information via telemetry
+ or APRS.
+ endif::radio[]
+
+ === Turning On the Power
+
+ Connect a battery and power switch and turn the switch
+ to "on". The flight computer will signal power on by
+ reporting the battery voltage and then perform an internal self
+ test and sensor calibration.
+
+ Once the self test and calibration are complete, there
+ are two modes that an Altus Metrum flight computer can
+ operate in:
+
+ Flight/Pad::
+ The flight computer is waiting to detect
+ launch and then fly the rocket. In this mode, the USB
+ link is
+ ifdef::radio[disabled, and the radio goes into transmit-only mode.]
+ ifndef::radio[disabled.]
+ The only way to get out of this
+ mode is to power the flight computer down. See below for how to get the flight
+ computer to come up in Flight/Pad mode at power on.
+
+ Idle::
+ The flight computer is ready to communicate over USB
+ ifdef::radio[and in packet mode over the radio.]
+ You can configure
+ the flight computer, download data or display
+ the current state. See below for how to get the flight
+ computer to come up in Idle mode at power on.
+
+ ifdef::telemetrum,easymega,telemega[]
+ For flight computers with accelerometers (TeleMetrum,
+ EasyMega and TeleMega), the mode is selected by the
+ orientation of the board during the self test
+ interval. If the board is pointing upwards as if ready
+ to fly, it will enter Flight/Pad mode. Otherwise, it will
+ enter Idle mode.
+ endif::telemetrum,easymega,telemega[]
+
+ ifdef::easymini[]
+ For EasyMini, if the USB cable is connected to a
+ computer, it will enter Idle mode. Otherwise, it will
+ enter Flight/Pad mode.
+ endif::easymini[]
+
+ ifdef::telemini[]
+ For TeleMini v1.0, if a packet link is waiting to
+ connect when the device is powered on, it will enter
+ Idle mode, otherwise it will enter Flight/Pad mode.
+ endif::telemini[]
+
+ You can see in <<_understanding_beeps>>
+ how to tell which mode the flight computer is in.
+