<surname>Towns</surname>
</author>
<copyright>
- <year>2013</year>
+ <year>2014</year>
<holder>Bdale Garbee and Keith Packard</holder>
</copyright>
<legalnotice>
</para>
</legalnotice>
<revhistory>
+ <revision>
+ <revnumber>1.3.2</revnumber>
+ <date>24 January 2014</date>
+ <revremark>
+ Bug fixes for TeleMega and AltosUI.
+ </revremark>
+ </revision>
+ <revision>
+ <revnumber>1.3.1</revnumber>
+ <date>21 January 2014</date>
+ <revremark>
+ Bug fixes for TeleMega and TeleMetrum v2.0 along with a few
+ small UI improvements.
+ </revremark>
+ </revision>
<revision>
<revnumber>1.3</revnumber>
<date>12 November 2013</date>
</para>
<table frame='all'>
<title>Altus Metrum Electronics</title>
+ <?dbfo keep-together="always"?>
<tgroup cols='8' align='center' colsep='1' rowsep='1'>
<colspec align='center' colwidth='*' colname='Device'/>
<colspec align='center' colwidth='*' colname='Barometer'/>
</table>
<table frame='all'>
<title>Altus Metrum Boards</title>
+ <?dbfo keep-together="always"?>
<tgroup cols='6' align='center' colsep='1' rowsep='1'>
<colspec align='center' colwidth='*' colname='Device'/>
<colspec align='center' colwidth='*' colname='Connectors'/>
</section>
<section>
<title>TeleMetrum</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="telemetrum-v1.1-thside.jpg" width="5.5in" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
TeleMetrum is a 1 inch by 2¾ inch circuit board. It was designed to
fit inside coupler for 29mm air-frame tubing, but using it in a tube that
</section>
<section>
<title>TeleMini</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="telemini-v1-top.jpg" width="5.5in" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
TeleMini v1.0 is ½ inches by 1½ inches. It was
designed to fit inside an 18mm air-frame tube, but using it in
the board, meaning an ideal “simple” avionics bay for TeleMini
should have at least 9 inches of interior length.
</para>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="telemini-v2-top.jpg" width="5.5in" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
TeleMini v2.0 is 0.8 inches by 1½ inches. It adds more
on-board data logging memory, a built-in USB connector and
</section>
<section>
<title>EasyMini</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="easymini-top.jpg" width="5.5in" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
EasyMini is built on a 0.8 inch by 1½ inch circuit board. It's
designed to fit in a 24mm coupler tube. The connectors and
</section>
<section>
<title>TeleMega</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="telemega-v1.0-top.jpg" width="5.5in" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
TeleMega is a 1¼ inch by 3¼ inch circuit board. It was
designed to easily fit in a 38mm coupler. Like TeleMetrum,
</para>
<table frame='all'>
<title>Data Storage on Altus Metrum altimeters</title>
+ <?dbfo keep-together="always"?>
<tgroup cols='4' align='center' colsep='1' rowsep='1'>
<colspec align='center' colwidth='*' colname='Device'/>
<colspec align='center' colwidth='*' colname='Bytes per sample'/>
the altimeter completes initialization and self test, and decides
which mode to enter next.
</para>
+ <para>
+ Here's a short summary of all of the modes and the beeping (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.
+ <table frame='all'>
+ <title>AltOS Modes</title>
+ <?dbfo keep-together="always"?>
+ <tgroup cols='4' align='center' colsep='1' rowsep='1'>
+ <colspec align='center' colwidth='*' colname='Mode Name'/>
+ <colspec align='center' colwidth='*' colname='Letter'/>
+ <colspec align='center' colwidth='*' colname='Beeps'/>
+ <colspec align='center' colwidth='*' colname='Description'/>
+ <thead>
+ <row>
+ <entry>Mode Name</entry>
+ <entry>Abbreviation</entry>
+ <entry>Beeps</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Startup</entry>
+ <entry>S</entry>
+ <entry>dit dit dit</entry>
+ <entry>
+ <para>
+ Calibrating sensors, detecting orientation.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>Idle</entry>
+ <entry>I</entry>
+ <entry>dit dit</entry>
+ <entry>
+ <para>
+ Ready to accept commands over USB or radio link.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>Pad</entry>
+ <entry>P</entry>
+ <entry>dit dah dah dit</entry>
+ <entry>
+ <para>
+ Waiting for launch. Not listening for commands.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>Boost</entry>
+ <entry>B</entry>
+ <entry>dah dit dit dit</entry>
+ <entry>
+ <para>
+ Accelerating upwards.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>Fast</entry>
+ <entry>F</entry>
+ <entry>dit dit dah dit</entry>
+ <entry>
+ <para>
+ Decellerating, but moving faster than 200m/s.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>Coast</entry>
+ <entry>C</entry>
+ <entry>dah dit dah dit</entry>
+ <entry>
+ <para>
+ Decellerating, moving slower than 200m/s
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>Drogue</entry>
+ <entry>D</entry>
+ <entry>dah dit dit</entry>
+ <entry>
+ <para>
+ Descending after apogee. Above main height.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>Main</entry>
+ <entry>M</entry>
+ <entry>dah dah</entry>
+ <entry>
+ <para>
+ Descending. Below main height.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>Landed</entry>
+ <entry>L</entry>
+ <entry>dit dah dit dit</entry>
+ <entry>
+ <para>
+ Stable altitude for at least ten seconds.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>Sensor error</entry>
+ <entry>X</entry>
+ <entry>dah dit dit dah</entry>
+ <entry>
+ <para>
+ Error detected during sensor calibration.
+ </para>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
<para>
In flight or “pad” mode, the altimeter engages the flight
- state machine, goes into transmit-only mode to
- send telemetry, and waits for launch to be detected.
- Flight mode is indicated by an “di-dah-dah-dit” (“P” for pad)
- on the beeper or lights, followed by beeps or flashes
- indicating the state of the pyrotechnic igniter continuity.
- One beep/flash indicates apogee continuity, two beeps/flashes
- indicate main continuity, three beeps/flashes indicate both
- apogee and main continuity, and one longer “brap” sound or
- rapidly alternating lights indicates no continuity. For a
+ state machine, goes into transmit-only mode to send telemetry,
+ and waits for launch to be detected. Flight mode is indicated
+ by an “di-dah-dah-dit” (“P” for pad) on the beeper or lights,
+ followed by beeps or flashes indicating the state of the
+ pyrotechnic igniter continuity. One beep/flash indicates
+ apogee continuity, two beeps/flashes indicate main continuity,
+ three beeps/flashes indicate both apogee and main continuity,
+ and one longer “brap” sound which is made by rapidly
+ alternating between two tones indicates no continuity. For a
dual deploy flight, make sure you're getting three beeps or
flashes before launching! For apogee-only or motor eject
flights, do what makes sense.
data from the on-board storage chip after flight, and for
ground testing pyro charges.
</para>
+ <para>
+ In “Idle” and “Pad” modes, once the mode indication
+ beeps/flashes and continuity indication has been sent, if
+ there is no space available to log the flight in on-board
+ memory, the flight computer will emit a warbling tone (much
+ slower than the “no continuity tone”)
+ </para>
+ <para>
+ Here's a summary of all of the “pad” and “idle” mode indications.
+ <table frame='all'>
+ <title>Pad/Idle Indications</title>
+ <?dbfo keep-together="always"?>
+ <tgroup cols='3' align='center' colsep='1' rowsep='1'>
+ <colspec align='center' colwidth='*' colname='Name'/>
+ <colspec align='center' colwidth='*' colname='Beeps'/>
+ <colspec align='center' colwidth='*' colname='Description'/>
+ <thead>
+ <row>
+ <entry>Name</entry>
+ <entry>Beeps</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Neither</entry>
+ <entry>brap</entry>
+ <entry>
+ <para>
+ No continuity detected on either apogee or main
+ igniters.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>Apogee</entry>
+ <entry>dit</entry>
+ <entry>
+ <para>
+ Continuity detected only on apogee igniter.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>Main</entry>
+ <entry>dit dit</entry>
+ <entry>
+ <para>
+ Continuity detected only on main igniter.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>Both</entry>
+ <entry>dit dit dit</entry>
+ <entry>
+ <para>
+ Continuity detected on both igniters.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>Storage Full</entry>
+ <entry>warble</entry>
+ <entry>
+ <para>
+ 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.
+ </para>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+ <para>
+ Once landed, the flight computer will signal that by emitting
+ the “Landed” sound described above, after which it will beep
+ out the apogee height (in meters). Each digit is represented
+ by a sequence of short “dit” beeps, with a pause between
+ digits. A zero digit is represented with one long “dah”
+ beep. The flight computer will continue to report landed mode
+ and beep out the maximum height until turned off.
+ </para>
<para>
One “neat trick” of particular value when TeleMetrum or TeleMega are used with
very large air-frames, is that you can power the board up while the
</chapter>
<chapter>
-
<title>AltosUI</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="altosui.png" width="4.6in"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
The AltosUI program provides a graphical user interface for
interacting with the Altus Metrum product family. AltosUI can
AltosUI will create a window to display telemetry data as
received by the selected TeleDongle device.
</para>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="device-selection.png" width="3.1in"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
All telemetry data received are automatically recorded in
suitable log files. The name of the files includes the current
</para>
<section>
<title>Launch Pad</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="launch-pad.png" width="5.5in"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
The 'Launch Pad' tab shows information used to decide when the
rocket is ready for flight. The first elements include red/green
</section>
<section>
<title>Ascent</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="ascent.png" width="5.5in"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
This tab is shown during Boost, Fast and Coast
phases. The information displayed here helps monitor the
rocket as it heads towards apogee.
</para>
<para>
- The height, speed and acceleration are shown along with the
- maximum values for each of them. This allows you to quickly
- answer the most commonly asked questions you'll hear during
- flight.
+ The height, speed, acceleration and tilt are shown along
+ with the maximum values for each of them. This allows you to
+ quickly answer the most commonly asked questions you'll hear
+ during flight.
</para>
<para>
The current latitude and longitude reported by the GPS are
</section>
<section>
<title>Descent</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="descent.png" width="5.5in"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
Once the rocket has reached apogee and (we hope) activated the
apogee charge, attention switches to tracking the rocket on
</section>
<section>
<title>Landed</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="landed.png" width="5.5in"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
Once the rocket is on the ground, attention switches to
recovery. While the radio signal is often lost once the
graph window for the current flight.
</para>
</section>
+ <section>
+ <title>Table</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="table.png" width="5.5in"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
+ <para>
+ The table view shows all of the data available from the
+ flight computer. Probably the most useful data on
+ this tab is the detailed GPS information, which includes
+ horizontal dilution of precision information, and
+ information about the signal being received from the satellites.
+ </para>
+ </section>
<section>
<title>Site Map</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="site-map.png" width="5.5in"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
When the TeleMetrum has a GPS fix, the Site Map tab will map
the rocket's position to make it easier for you to locate the
.eeprom file containing flight data saved from
flash memory.
</para>
+ <para>
+ Note that telemetry files will generally produce poor graphs
+ due to the lower sampling rate and missed telemetry packets.
+ Use saved flight data in .eeprom files for graphing where possible.
+ </para>
<para>
Once a flight record is selected, a window with multiple tabs is
opened.
- <variablelist>
- <varlistentry>
- <term>Flight Graph</term>
- <listitem>
- <para>
- By default, the graph contains acceleration (blue),
- velocity (green) and altitude (red).
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Configure Graph</term>
- <listitem>
- <para>
- This selects which graph elements to show, and, at the
- very bottom, lets you switch between metric and
- imperial units
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Flight Statistics</term>
- <listitem>
- <para>
- Shows overall data computed from the flight.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Map</term>
- <listitem>
- <para>
- Shows a satellite image of the flight area overlaid
- with the path of the flight. The red concentric
- circles mark the launch pad, the black concentric
- circles mark the landing location.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
</para>
+ <section>
+ <title>Flight Graph</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="graph.png" width="6in" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
+ <para>
+ By default, the graph contains acceleration (blue),
+ velocity (green) and altitude (red).
+ </para>
<para>
The graph can be zoomed into a particular area by clicking and
dragging down and to the right. Once zoomed, the graph can be
The right mouse button causes a pop-up menu to be displayed, giving
you the option save or print the plot.
</para>
- <para>
- Note that telemetry files will generally produce poor graphs
- due to the lower sampling rate and missed telemetry packets.
- Use saved flight data in .eeprom files for graphing where possible.
- </para>
+ </section>
+ <section>
+ <title>Configure Graph</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="graph-configure.png" width="6in" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
+ <para>
+ This selects which graph elements to show, and, at the
+ very bottom, lets you switch between metric and
+ imperial units
+ </para>
+ </section>
+ <section>
+ <title>Flight Statistics</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="graph-stats.png" width="6in" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
+ <para>
+ Shows overall data computed from the flight.
+ </para>
+ </section>
+ <section>
+ <title>Map</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="graph-map.png" width="6in" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
+ <para>
+ Shows a satellite image of the flight area overlaid
+ with the path of the flight. The red concentric
+ circles mark the launch pad, the black concentric
+ circles mark the landing location.
+ </para>
+ </section>
</section>
<section>
<title>Export Data</title>
</section>
<section>
<title>Configure Altimeter</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="configure-altimeter.png" width="3.6in" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
Select this button and then select either an altimeter or
TeleDongle Device from the list provided. Selecting a TeleDongle
<para>
At the bottom of the dialog, there are four buttons:
</para>
- <itemizedlist>
- <listitem>
- <para>
- Save. This writes any changes to the
- configuration parameter block in flash memory. If you don't
- press this button, any changes you make will be lost.
- </para>
- </listitem>
- <listitem>
- <para>
- Reset. This resets the dialog to the most recently saved values,
- erasing any changes you have made.
- </para>
- </listitem>
- <listitem>
- <para>
- Reboot. This reboots the device. Use this to
- switch from idle to pad mode by rebooting once the rocket is
- oriented for flight, or to confirm changes you think you saved
- are really saved.
- </para>
- </listitem>
- <listitem>
- <para>
- Close. This closes the dialog. Any unsaved changes will be
- lost.
- </para>
- </listitem>
- </itemizedlist>
+ <variablelist>
+ <varlistentry>
+ <term>Save</term>
+ <listitem>
+ <para>
+ This writes any changes to the
+ configuration parameter block in flash memory. If you don't
+ press this button, any changes you make will be lost.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Reset</term>
+ <listitem>
+ <para>
+ This resets the dialog to the most recently saved values,
+ erasing any changes you have made.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Reboot</term>
+ <listitem>
+ <para>
+ This reboots the device. Use this to
+ switch from idle to pad mode by rebooting once the rocket is
+ oriented for flight, or to confirm changes you think you saved
+ are really saved.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Close</term>
+ <listitem>
+ <para>
+ This closes the dialog. Any unsaved changes will be
+ lost.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
<para>
The rest of the dialog contains the parameters to be configured.
</para>
computers. This configuration parameter allows the two
channels to be used in different configurations.
</para>
- <itemizedlist>
- <listitem>
- <para>
- Dual Deploy. This is the usual mode of operation; the
- 'apogee' channel is fired at apogee and the 'main'
- channel at the height above ground specified by the
- 'Main Deploy Altitude' during descent.
- </para>
- </listitem>
- <listitem>
- <para>
- Redundant Apogee. This fires both channels at
- apogee, the 'apogee' channel first followed after a two second
- delay by the 'main' channel.
- </para>
- </listitem>
- <listitem>
- <para>
- Redundant Main. This fires both channels at the
- height above ground specified by the Main Deploy
- Altitude setting during descent. The 'apogee'
- channel is fired first, followed after a two second
- delay by the 'main' channel.
- </para>
- </listitem>
- </itemizedlist>
+ <variablelist>
+ <varlistentry>
+ <term>Dual Deploy</term>
+ <listitem>
+ <para>
+ This is the usual mode of operation; the
+ 'apogee' channel is fired at apogee and the 'main'
+ channel at the height above ground specified by the
+ 'Main Deploy Altitude' during descent.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Redundant Apogee</term>
+ <listitem>
+ <para>
+ This fires both channels at
+ apogee, the 'apogee' channel first followed after a two second
+ delay by the 'main' channel.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Redundant Main</term>
+ <listitem>
+ <para>
+ This fires both channels at the
+ height above ground specified by the Main Deploy
+ Altitude setting during descent. The 'apogee'
+ channel is fired first, followed after a two second
+ delay by the 'main' channel.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section>
<title>Pad Orientation</title>
parameter allows that default to be changed, permitting the
board to be mounted with the antenna pointing aft instead.
</para>
- <itemizedlist>
- <listitem>
- <para>
- Antenna Up. In this mode, the antenna end of the
- flight computer must point forward, in line with the
- expected flight path.
- </para>
- </listitem>
- <listitem>
- <para>
- Antenna Down. In this mode, the antenna end of the
- flight computer must point aft, in line with the
- expected flight path.
- </para>
- </listitem>
- </itemizedlist>
+ <variablelist>
+ <varlistentry>
+ <term>Antenna Up</term>
+ <listitem>
+ <para>
+ In this mode, the antenna end of the
+ flight computer must point forward, in line with the
+ expected flight path.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Antenna Down</term>
+ <listitem>
+ <para>
+ In this mode, the antenna end of the
+ flight computer must point aft, in line with the
+ expected flight path.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section>
<title>Configure Pyro Channels</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="configure-pyro.png" width="6in" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
This opens a separate window to configure the additional
pyro channels available on TeleMega. One column is
</section>
<section>
<title>Configure AltosUI</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="configure-altosui.png" width="2.4in" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
This button presents a dialog so that you can configure the AltosUI global settings.
</para>
the current flight status. However, sometimes you don't want
to hear them.
</para>
- <itemizedlist>
- <listitem>
- <para>Enable—turns all voice announcements on and off</para>
- </listitem>
- <listitem>
- <para>
- Test Voice—Plays a short message allowing you to verify
- that the audio system is working and the volume settings
- are reasonable
- </para>
- </listitem>
- </itemizedlist>
+ <variablelist>
+ <varlistentry>
+ <term>Enable</term>
+ <listitem>
+ <para>Turns all voice announcements on and off</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Test Voice</term>
+ <listitem>
+ <para>
+ Plays a short message allowing you to verify
+ that the audio system is working and the volume settings
+ are reasonable
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<section>
<title>Log Directory</title>
</section>
<section>
<title>Configure Groundstation</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="configure-groundstation.png" width="3.1in" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
Select this button and then select a TeleDongle Device from the list provided.
</para>
<para>
At the bottom of the dialog, there are three buttons:
</para>
- <itemizedlist>
- <listitem>
- <para>
- Save. This writes any changes to the
- local Java preferences file. If you don't
- press this button, any changes you make will be lost.
- </para>
- </listitem>
- <listitem>
- <para>
- Reset. This resets the dialog to the most recently saved values,
- erasing any changes you have made.
- </para>
- </listitem>
- <listitem>
- <para>
- Close. This closes the dialog. Any unsaved changes will be
- lost.
- </para>
- </listitem>
- </itemizedlist>
+ <variablelist>
+ <varlistentry>
+ <term>Save</term>
+ <listitem>
+ <para>
+ This writes any changes to the
+ local Java preferences file. If you don't
+ press this button, any changes you make will be lost.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Reset</term>
+ <listitem>
+ <para>
+ This resets the dialog to the most recently saved values,
+ erasing any changes you have made.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Close</term>
+ <listitem>
+ <para>
+ This closes the dialog. Any unsaved changes will be
+ lost.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
<para>
The rest of the dialog contains the parameters to be configured.
</para>
(self programming). Please read the directions for flashing
devices in the Updating Device Firmware chapter below.
</para>
- <para>
- For “self programming”, connect USB to the device to be
- programmed and push the 'Flash Image' button. That will
- present a dialog box listing all of the connected
- devices. Carefully select the device to be programmed.
- </para>
- <para>
- For “pair programming”, once you have the programmer and
- target devices connected, push the 'Flash Image' button. That
- will present a dialog box listing all of the connected
- devices. Carefully select the programmer device, not the
- device to be programmed.
- </para>
- <para>
- Next, select the image to flash to the device. These are named
- with the product name and firmware version. The file selector
- will start in the directory containing the firmware included
- with the AltosUI package. Navigate to the directory containing
- the desired firmware if it isn't there.
- </para>
- <para>
- Next, a small dialog containing the device serial number and
- RF calibration values should appear. If these values are
- incorrect (possibly due to a corrupted image in the device),
- enter the correct values here.
- </para>
- <para>
- Finally, a dialog containing a progress bar will follow the
- programming process.
- </para>
- <para>
- When programming is complete, the target device will
- reboot. Note that if a pair programmed target device is
- connected via USB, you will have to unplug it and then plug it
- back in for the USB connection to reset so that you can
- communicate with the device again.
- </para>
</section>
<section>
<title>Fire Igniter</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="fire-igniter.png" width="1.2in" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
This activates the igniter circuits in the flight computer to help
test recovery systems deployment. Because this command can operate
<para>
Selecting the 'Fire Igniter' button brings up the usual device
selection dialog. Pick the desired device. This brings up another
- window which shows the current continuity test status for both
- apogee and main charges.
+ window which shows the current continuity test status for all
+ of the pyro channels.
</para>
<para>
Next, select the desired igniter to fire. This will enable the
</section>
<section>
<title>Scan Channels</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="scan-channels.png" width="3.2in" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
This listens for telemetry packets on all of the configured
frequencies, displaying information about each device it
</section>
<section>
<title>Load Maps</title>
+ <informalfigure>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="load-maps.png" width="5.2in" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
<para>
Before heading out to a new launch site, you can use this to
load satellite images in case you don't have internet
<section>
<title>Installing AltosDroid</title>
<para>
- AltosDroid is included in the Google Play store. To install
- it on your Android device, open open the Google Play Store
+ AltosDroid is available from the Google Play store. To install
+ it on your Android device, open the Google Play Store
application and search for “altosdroid”. Make sure you don't
have a space between “altos” and “droid” or you probably won't
find what you want. That should bring you to the right page
<section>
<title>In the Rocket</title>
<para>
- In the rocket itself, you just need a <ulink url="http://www.altusmetrum.org/TeleMetrum/">TeleMetrum</ulink> or
- <ulink url="http://www.altusmetrum.org/TeleMini/">TeleMini</ulink> board and
+ In the rocket itself, you just need a flight computer and
a single-cell, 3.7 volt nominal Li-Po rechargeable battery. An
850mAh battery weighs less than a 9V alkaline battery, and will
- run a TeleMetrum for hours.
- A 110mAh battery weighs less than a triple A battery and will run a TeleMetrum for
- a few hours, or a TeleMini for much (much) longer.
+ run a TeleMetrum or TeleMega for hours.
+ A 110mAh battery weighs less than a triple A battery and is a good
+ choice for use with TeleMini.
</para>
<para>
- By default, we ship the altimeters with a simple wire antenna. If your
- electronics bay or the air-frame it resides within is made of carbon fiber,
- which is opaque to RF signals, you may choose to have an SMA connector
- installed so that you can run a coaxial cable to an antenna mounted
- elsewhere in the rocket.
+ By default, we ship flight computers with a simple wire antenna.
+ If your electronics bay or the air-frame it resides within is made
+ of carbon fiber, which is opaque to RF signals, you may prefer to
+ install an SMA connector so that you can run a coaxial cable to an
+ antenna mounted elsewhere in the rocket. However, note that the
+ GPS antenna is fixed on all current products, so you really want
+ to install the flight computer in a bay made of RF-transparent
+ materials if at all possible.
</para>
</section>
<section>
Linux, Mac OS and Windows. There's also a suite of C tools
for Linux which can perform most of the same tasks.
</para>
+ <para>
+ Alternatively, a TeleBT attached with an SMA to BNC adapter at the
+ feed point of a hand-held yagi used in conjunction with an Android
+ device running AltosDroid makes an outstanding ground station.
+ </para>
<para>
After the flight, you can use the radio link to extract the more detailed data
logged in either TeleMetrum or TeleMini devices, or you can use a mini USB cable to plug into the
of digital cameras and other modern electronic stuff will work fine.
</para>
<para>
- If your TeleMetrum-equipped rocket lands out of sight, you may enjoy having a hand-held GPS
- receiver, so that you can put in a way-point for the last reported rocket
- position before touch-down. This makes looking for your rocket a lot like
- Geo-Caching... just go to the way-point and look around starting from there.
+ If your rocket lands out of sight, you may enjoy having a hand-held
+ GPS receiver, so that you can put in a way-point for the last
+ reported rocket position before touch-down. This makes looking for
+ your rocket a lot like Geo-Caching... just go to the way-point and
+ look around starting from there. AltosDroid on an Android device
+ with GPS receiver works great for this, too!
</para>
<para>
You may also enjoy having a ham radio “HT” that covers the 70cm band... you
</section>
<section>
<title>Future Plans</title>
+ <para>
+ We've designed a simple GPS based radio tracker called TeleGPS.
+ If all goes well, we hope to introduce this in the first
+ half of 2014.
+ </para>
<para>
- In the future, we intend to offer “companion boards” for the rocket
- that will plug in to TeleMetrum to collect additional data, provide
- more pyro channels, and so forth.
- </para>
- <para>
- Also under design is a new flight computer with more sensors, more
- pyro channels, and a more powerful radio system designed for use
- in multi-stage, complex, and extreme altitude projects.
- </para>
- <para>
- We are also working on alternatives to TeleDongle. One is a
- a stand-alone, hand-held ground terminal that will allow monitoring
- the rocket's status, collecting data during flight, and logging data
- after flight without the need for a notebook computer on the
- flight line. Particularly since it is so difficult to read most
- notebook screens in direct sunlight, we think this will be a great
- thing to have. We are also working on a TeleDongle variant with
- Bluetooth™ that will work with Android phones and tablets.
+ We have designed and prototyped several “companion boards” that
+ can attach to the companion connector on TeleMetrum and TeleMega
+ flight computers to collect more data, provide more pyro channels,
+ and so forth. We do not yet know if or when any of these boards
+ will be produced in enough quantity to sell. If you have specific
+ interests for data collection or control of events in your rockets
+ beyond the capabilities of our existing productions, please let
+ us know!
</para>
<para>
Because all of our work is open, both the hardware designs and the
<para>
Building high-power rockets that fly safely is hard enough. Mix
in some sophisticated electronics and a bunch of radio energy
- and oftentimes you find few perfect solutions. This chapter
+ and some creativity and/or compromise may be required. This chapter
contains some suggestions about how to install Altus Metrum
- products into the rocket air-frame, including how to safely and
+ products into a rocket air-frame, including how to safely and
reliably mix a variety of electronics into the same air-frame.
</para>
<section>
<title>Mounting the Altimeter</title>
<para>
The first consideration is to ensure that the altimeter is
- securely fastened to the air-frame. For TeleMetrum, we use
- nylon standoffs and nylon screws; they're good to at least 50G
- and cannot cause any electrical issues on the board. For
- TeleMini, we usually cut small pieces of 1/16 inch balsa to fit
+ securely fastened to the air-frame. For most of our products, we
+ prefer nylon standoffs and nylon screws; they're good to at least 50G
+ and cannot cause any electrical issues on the board. Metal screws
+ and standoffs are fine, too, just be careful to avoid electrical
+ shorts! For TeleMini v1.0, we usually cut small pieces of 1/16 inch
+ balsa to fit
under the screw holes, and then take 2x56 nylon screws and
screw them through the TeleMini mounting holes, through the
balsa and into the underlying material.
<orderedlist inheritnum='inherit' numeration='arabic'>
<listitem>
<para>
- Make sure TeleMetrum is aligned precisely along the axis of
+ Make sure accelerometer-equipped products like TeleMetrum and
+ TeleMega are aligned precisely along the axis of
acceleration so that the accelerometer can accurately
capture data during the flight.
</para>
culprit here -- CF is a good conductor and will effectively
shield the antenna, dramatically reducing signal strength and
range. Metallic flake paint is another effective shielding
- material which is to be avoided around any antennas.
+ material which should be avoided around any antennas.
</para>
<para>
If the ebay is large enough, it can be convenient to simply
consuming very little space.
</para>
<para>
- If you need to place the antenna at a distance from the
+ If you need to place the UHF antenna at a distance from the
altimeter, you can replace the antenna with an edge-mounted
SMA connector, and then run 50Ω coax from the board to the
antenna. Building a remote antenna is beyond the scope of this
<section>
<title>Preserving GPS Reception</title>
<para>
- The GPS antenna and receiver in TeleMetrum are highly
- sensitive and normally have no trouble tracking enough
+ The GPS antenna and receiver used in TeleMetrum and TeleMega is
+ highly sensitive and normally have no trouble tracking enough
satellites to provide accurate position information for
- recovering the rocket. However, there are many ways to
- attenuate the GPS signal.
+ recovering the rocket. However, there are many ways the GPS signal
+ can end up attenuated, negatively affecting GPS performance.
<orderedlist inheritnum='inherit' numeration='arabic'>
<listitem>
<para>
<para>
Avoid resonant lengths. Know what frequencies are present
in the environment and avoid having wire lengths near a
- natural resonant length. Altusmetrum products transmit on the
+ natural resonant length. Altus Metrum products transmit on the
70cm amateur band, so you should avoid lengths that are a
simple ratio of that length; essentially any multiple of ¼
of the wavelength (17.5cm).
decreasing pressure.
</para>
<para>
- The barometric sensor in the altimeter is quite sensitive to
- chemical damage from the products of APCP or BP combustion, so
- make sure the ebay is carefully sealed from any compartment
- which contains ejection charges or motors.
+ All barometric sensors are quite sensitive to chemical damage from
+ the products of APCP or BP combustion, so make sure the ebay is
+ carefully sealed from any compartment which contains ejection
+ charges or motors.
</para>
</section>
<section>
version from <ulink url="http://www.altusmetrum.org/AltOS/"/>.
</para>
<para>
- We recommend updating the altimeter first, before updating TeleDongle.
+ If you need to update the firmware on a TeleDongle, we recommend
+ updating the altimeter first, before updating TeleDongle. However,
+ note that TeleDongle rarely need to be updated. Any firmware version
+ 1.0.1 or later will work, version 1.2.1 may have improved receiver
+ performance slightly.
</para>
<para>
Self-programmable devices (TeleMega, TeleMetrum v2 and EasyMini)
<listitem>
<para>
You'll need a special 'programming cable' to reprogram the
- TeleMini. It's available on the Altus Metrum web store, or
- you can make your own using an 8-pin MicroMaTch connector on
- one end and a set of four pins on the other.
+ TeleMini. You can make your own using an 8-pin MicroMaTch
+ connector on one end and a set of four pins on the other.
</para>
</listitem>
<listitem>
</listitem>
<listitem>
<para>
- Uses Li-Po to fire e-matches, can be modified to support
- optional separate pyro battery if needed.
+ Can use either main system Li-Po or optional separate pyro battery
+ to fire e-matches.
</para>
</listitem>
<listitem>
<chapter>
<title>FAQ</title>
<para>
- TeleMetrum seems to shut off when disconnected from the
- computer. Make sure the battery is adequately charged. Remember the
+ <emphasis>TeleMetrum seems to shut off when disconnected from the
+ computer.</emphasis> <?linebreak?>
+ Make sure the battery is adequately charged. Remember the
unit will pull more power than the USB port can deliver before the
GPS enters “locked” mode. The battery charges best when TeleMetrum
is turned off.
</para>
<para>
- It's impossible to stop the TeleDongle when it's in “p” mode, I have
- to unplug the USB cable? Make sure you have tried to “escape out” of
+ <emphasis>It's impossible to stop the TeleDongle when it's in “p” mode, I have
+ to unplug the USB cable? </emphasis><?linebreak?>
+ Make sure you have tried to “escape out” of
this mode. If this doesn't work the reboot procedure for the
TeleDongle *is* to simply unplug it. 'cu' however will retain it's
outgoing buffer IF your “escape out” ('~~') does not work.
communication.
</para>
<para>
- The amber LED (on the TeleMetrum) lights up when both
- battery and USB are connected. Does this mean it's charging?
+ <emphasis>The amber LED (on the TeleMetrum) lights up when both
+ battery and USB are connected. Does this mean it's charging?
+ </emphasis><?linebreak?>
Yes, the yellow LED indicates the charging at the 'regular' rate.
If the led is out but the unit is still plugged into a USB port,
then the battery is being charged at a 'trickle' rate.
</para>
<para>
- There are no “dit-dah-dah-dit” sound or lights like the manual mentions?
+ <emphasis>There are no “dit-dah-dah-dit” sound or lights like the manual
+ mentions?</emphasis><?linebreak?>
That's the “pad” mode. Weak batteries might be the problem.
- It is also possible that the TeleMetrum is horizontal and the output
+ It is also possible that the flight computer is horizontal and the
+ output
is instead a “dit-dit” meaning 'idle'. For TeleMini, it's possible that
it received a command packet which would have left it in “pad” mode.
</para>
<para>
- How do I save flight data?
+ <emphasis>How do I save flight data?</emphasis><?linebreak?>
Live telemetry is written to file(s) whenever AltosUI is connected
to the TeleDongle. The file area defaults to ~/TeleMetrum
but is easily changed using the menus in AltosUI. The files that
Then, divide 434.550 MHz by the
measured frequency and multiply by the current radio cal value show
in the 'c s' command. For an unprogrammed board, the default value
- is 1186611. Take the resulting integer and program it using the 'c f'
+ is 1186611 for cc1111 based products and 7119667 for cc1120
+ based products. Take the resulting integer and program it using the 'c f'
command. Testing with the 'C' command again should show a carrier
within a few tens of Hertz of the intended frequency.
As with all 'c' sub-commands, follow this with a 'c w' to write the
- change to the parameter block in the on-board DataFlash chip.
+ change to the configuration memory.
</para>
<para>
Note that the 'reboot' command, which is very useful on the altimeters,
TeleMega has overall dimensions of 1.250 x 3.250 inches, and
the mounting holes are sized for use with 4-40 or M3 screws.
</para>
- <mediaobject id="TeleMegaTemplate">
- <imageobject>
- <imagedata format="SVG" fileref="telemega-outline.svg"/>
- </imageobject>
- </mediaobject>
+ <informalfigure>
+ <mediaobject id="TeleMegaTemplate">
+ <imageobject>
+ <imagedata format="SVG" fileref="telemega-outline.svg"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
</section>
<section>
<title>TeleMetrum template</title>
TeleMetrum has overall dimensions of 1.000 x 2.750 inches, and the
mounting holes are sized for use with 4-40 or M3 screws.
</para>
- <mediaobject id="TeleMetrumTemplate">
- <imageobject>
- <imagedata format="SVG" fileref="telemetrum.svg"/>
- </imageobject>
- </mediaobject>
+ <informalfigure>
+ <mediaobject id="TeleMetrumTemplate">
+ <imageobject>
+ <imagedata format="SVG" fileref="telemetrum.svg"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
</section>
<section>
<title>TeleMini v2/EasyMini template</title>
TeleMini v2 and EasyMini have overall dimensions of 0.800 x 1.500 inches, and the
mounting holes are sized for use with 4-40 or M3 screws.
</para>
- <mediaobject id="MiniTemplate">
- <imageobject>
- <imagedata format="SVG" fileref="easymini-outline.svg"/>
- </imageobject>
- </mediaobject>
+ <informalfigure>
+ <mediaobject id="MiniTemplate">
+ <imageobject>
+ <imagedata format="SVG" fileref="easymini-outline.svg"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
</section>
<section>
<title>TeleMini v1 template</title>
TeleMini has overall dimensions of 0.500 x 1.500 inches, and the
mounting holes are sized for use with 2-56 or M2 screws.
</para>
- <mediaobject id="TeleMiniTemplate">
- <imageobject>
- <imagedata format="SVG" fileref="telemini.svg"/>
- </imageobject>
- </mediaobject>
+ <informalfigure>
+ <mediaobject id="TeleMiniTemplate">
+ <imageobject>
+ <imagedata format="SVG" fileref="telemini.svg"/>
+ </imageobject>
+ </mediaobject>
+ </informalfigure>
</section>
</appendix>
<appendix>
</appendix>
<appendix>
<title>Release Notes</title>
+ <simplesect>
+ <title>Version 1.3.2</title>
+ <xi:include
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="release-notes-1.3.2.xsl"
+ xpointer="xpointer(/article/*)"/>
+ </simplesect>
+ <simplesect>
+ <title>Version 1.3.1</title>
+ <xi:include
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="release-notes-1.3.1.xsl"
+ xpointer="xpointer(/article/*)"/>
+ </simplesect>
<simplesect>
<title>Version 1.3</title>
<xi:include
projects / fw / altos / blobdiff