<surname>Towns</surname>
</author>
<copyright>
- <year>2013</year>
+ <year>2014</year>
<holder>Bdale Garbee and Keith Packard</holder>
</copyright>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="../themes/background.png" width="6.0in"/>
+ </imageobject>
+ </mediaobject>
<legalnotice>
<para>
This document is released under the terms of the
</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>
For a slightly more portable ground station experience that also
provides direct rocket recovery support, TeleBT offers flight
- monitoring and data logging using a Bluetooth connection between
- the receiver and an Android device that has the Altos Droid
+ monitoring and data logging using a Bluetooth™ connection between
+ the receiver and an Android device that has the AltosDroid
application installed from the Google Play store.
</para>
<para>
<para>
On TeleMetrum v1 boards, when the GPS chip is initially
searching for satellites, TeleMetrum will consume more current
- than it can pull from the USB port, so the battery must be
+ than it pulls from the USB port, so the battery must be
attached in order to get satellite lock. Once GPS is locked,
the current consumption goes back down enough to enable charging
while running. So it's a good idea to fully charge the battery
and EasyMini, anything supplying between 4 and 12 volts should
work fine (like a standard 9V battery), but if you are planning
to fire pyro charges, ground testing is required to verify that
- the battery supplies enough current.
+ the battery supplies enough current to fire your chosen e-matches.
</para>
<para>
The other active device in the starter kit is the TeleDongle USB to
driver information that is part of the AltOS download to know that the
existing USB modem driver will work. We therefore recommend installing
our software before plugging in TeleDongle if you are using a Windows
- computer. If you are using Linux and are having problems, try moving
- to a fresher kernel (2.6.33 or newer), as the USB serial driver had
- ugly bugs in some earlier versions.
+ computer. If you are using an older version of Linux and are having
+ problems, try moving to a fresher kernel (2.6.33 or newer).
</para>
<para>
- Next you should obtain and install the AltOS software. These
- include the AltosUI ground station program, current firmware
+ Next you should obtain and install the AltOS software. The AltOS
+ distribution includes the AltosUI ground station program, current
+ firmware
images for all of the hardware, and a number of standalone
utilities that are rarely needed. Pre-built binary packages are
available for Linux, Microsoft Windows, and recent MacOSX
<ulink url="http://altusmetrum.org/AltOS"/>.
</para>
<para>
- If you're using a TeleBT instead of the TeleDongle, you'll want
- to go install the Altos Droid application from the Google Play
- store. You don't need a data plan to use Altos Droid, but
+ If you're using a TeleBT instead of the TeleDongle, you'll want to
+ install the AltosDroid application from the Google Play store on an
+ Android device. You don't need a data plan to use AltosDroid, but
without network access, the Map view will be less useful as it
won't contain any map data. You can also use TeleBT connected
over USB with your laptop computer; it acts exactly like a
sensitive to sunlight. In normal mounting situations, the baro sensor
and all of the other surface mount components
are “down” towards whatever the underlying mounting surface is, so
- this is not normally a problem. Please consider this, though, when
- designing an installation, for example, in an air-frame with a
- see-through plastic payload bay. It is particularly important to
+ this is not normally a problem. Please consider this when designing an
+ installation in an air-frame with a see-through plastic payload bay. It
+ is particularly important to
consider this with TeleMini v1.0, both because the baro sensor is on the
“top” of the board, and because many model rockets with payload bays
use clear plastic for the payload bay! Replacing these with an opaque
<chapter>
<title>Altus Metrum Hardware</title>
<section>
- <title>Overview</title>
+ <title>General Usage Instructions</title>
+ <para>
+ Here are general instructions for hooking up an Altus Metrum
+ flight computer. Instructions specific to each model will be
+ found in the section devoted to that model below.
+ </para>
+ <para>
+ To prevent electrical interference from affecting the
+ operation of the flight computer, it's important to always
+ twist pairs of wires connected to the board. Twist the switch
+ leads, the pyro leads and the battery leads. This reduces
+ interference through a mechanism called common mode rejection.
+ </para>
+ <section>
+ <title>Hooking Up Lithium Polymer Batteries</title>
+ <para>
+ All Altus Metrum flight computers have a two pin JST PH
+ series connector to connect up a single-cell Lithium Polymer
+ cell (3.7V nominal). You can purchase matching batteries
+ from the Altus Metrum store, or other vendors, or you can
+ make your own. Pin 1 of the connector is positive, pin 2 is
+ negative. Spark Fun sells a cable with the connector
+ attached, which they call a <ulink
+ url="https://www.sparkfun.com/products/9914">JST Jumper 2
+ Wire Assembly</ulink>.
+ </para>
+ <para>
+ Many RC vendors also sell lithium polymer batteries with
+ this same connector. All that we have found use the opposite
+ polarity, and if you use them that way, you will damage or
+ destroy the flight computer.
+ </para>
+ </section>
+ <section>
+ <title>Hooking Up Pyro Charges</title>
+ <para>
+ Altus Metrum flight computers always have two screws for
+ each pyro charge. This means you shouldn't need to put two
+ wires into a screw terminal or connect leads from pyro
+ charges together externally.
+ </para>
+ <para>
+ On the flight computer, one lead from each charge is hooked
+ to the positive battery terminal through the power switch.
+ The other lead is connected through the pyro circuit, which
+ is connected to the negative battery terminal when the pyro
+ circuit is fired.
+ </para>
+ </section>
+ <section>
+ <title>Hooking Up a Power Switch</title>
+ <para>
+ Altus Metrum flight computers need an external power switch
+ to turn them on. This disconnects both the computer and the
+ pyro charges from the battery, preventing the charges from
+ firing when in the Off position. The switch is in-line with
+ the positive battery terminal.
+ </para>
+ <section>
+ <title>Using an External Active Switch Circuit</title>
+ <para>
+ You can use an active switch circuit, such as the
+ Featherweight Magnetic Switch, with any Altus Metrum
+ flight computer. These require three connections, one to
+ the battery, one to the positive power input on the flight
+ computer and one to ground. Find instructions on how to
+ hook these up for each flight computer below. The follow
+ the instructions that come with your active switch to
+ connect it up.
+ </para>
+ </section>
+ </section>
+ <section>
+ <title>Using a Separate Pyro Battery</title>
+ <para>
+ As mentioned above in the section on hooking up pyro
+ charges, one lead for each of the pyro charges is connected
+ through the power switch directly to the positive battery
+ terminal. The other lead is connected to the pyro circuit,
+ which connects it to the negative battery terminal when the
+ pyro circuit is fired. The pyro circuit on all of the flight
+ computers is designed to handle up to 16V.
+ </para>
+ <para>
+ To use a separate pyro battery, connect the negative pyro
+ battery terminal to the flight computer ground terminal,
+ the positive battery terminal to the igniter and the other
+ igniter lead to the negative pyro terminal on the flight
+ computer. When the pyro channel fires, it will complete the
+ circuit between the negative pyro terminal and the ground
+ terminal, firing the igniter. Specific instructions on how
+ to hook this up will be found in each section below.
+ </para>
+ </section>
+ <section>
+ <title>Using a Different Kind of Battery</title>
+ <para>
+ EasyMini and TeleMini v2 are designed to use either a
+ lithium polymer battery or any other battery producing
+ between 4 and 12 volts, such as a rectangular 9V
+ battery. TeleMega and TeleMetrum are not designed for this,
+ and must only be powered by a lithium polymer battery. Find
+ instructions on how to use other batteries in the EasyMini
+ and TeleMini sections below.
+ </para>
+ </section>
+ </section>
+ <section>
+ <title>Specifications</title>
<para>
Here's the full set of Altus Metrum products, both in
production and retired.
</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'/>
</para></entry>
<entry>½ inch (1.27cm)</entry>
<entry>1½ inch (3.81cm)</entry>
- <entry>18mm airframe</entry>
+ <entry>18mm coupler</entry>
</row>
<row>
<entry>TeleMini <?linebreak?>v2.0</entry>
</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
fin can end of the board, meaning an ideal “simple” avionics
bay for TeleMetrum should have at least 10 inches of interior length.
</para>
+ <section>
+ <title>TeleMetrum Screw Terminals</title>
+ <para>
+ TeleMetrum has six screw terminals on the end of the board
+ opposite the telemetry antenna. Two are for the power
+ switch, and two each for the apogee and main igniter
+ circuits. Using the picture above and starting from the top,
+ the terminals are as follows:
+ </para>
+ <table frame='all'>
+ <title>TeleMetrum Screw Terminals</title>
+ <?dbfo keep-together="always"?>
+ <tgroup cols='3' align='center' colsep='1' rowsep='1'>
+ <colspec align='center' colwidth='*' colname='Pin #'/>
+ <colspec align='center' colwidth='2*' colname='Pin Name'/>
+ <colspec align='left' colwidth='5*' colname='Description'/>
+ <thead>
+ <row>
+ <entry align='center'>Terminal #</entry>
+ <entry align='center'>Terminal Name</entry>
+ <entry align='center'>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>1</entry>
+ <entry>Switch Output</entry>
+ <entry>Switch connection to flight computer</entry>
+ </row>
+ <row>
+ <entry>2</entry>
+ <entry>Switch Input</entry>
+ <entry>Switch connection to positive battery terminal</entry>
+ </row>
+ <row>
+ <entry>3</entry>
+ <entry>Main +</entry>
+ <entry>Main pyro channel common connection to battery +</entry>
+ </row>
+ <row>
+ <entry>4</entry>
+ <entry>Main -</entry>
+ <entry>Main pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>5</entry>
+ <entry>Apogee +</entry>
+ <entry>Apogee pyro channel common connection to battery +</entry>
+ </row>
+ <row>
+ <entry>6</entry>
+ <entry>Apogee -</entry>
+ <entry>Apogee pyro channel connection to pyro circuit</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+ <section>
+ <title>Using a Separate Pyro Battery with TeleMetrum</title>
+ <para>
+ As described above, using an external pyro battery involves
+ connecting the negative battery terminal to the flight
+ computer ground, connecting the positive battery terminal to
+ one of the igniter leads and connecting the other igniter
+ lead to the per-channel pyro circuit connection.
+ </para>
+ <para>
+ To connect the negative battery terminal to the TeleMetrum
+ ground, insert a small piece of wire, 24 to 28 gauge
+ stranded, into the GND hole just above the screw terminal
+ strip and solder it in place.
+ </para>
+ <para>
+ Connecting the positive battery terminal to the pyro
+ charges must be done separate from TeleMetrum, by soldering
+ them together or using some other connector.
+ </para>
+ <para>
+ The other lead from each pyro charge is then inserted into
+ the appropriate per-pyro channel screw terminal (terminal 4 for the
+ Main charge, terminal 6 for the Apogee charge).
+ </para>
+ </section>
+ <section>
+ <title>Using an Active Switch with TeleMetrum</title>
+ <para>
+ As explained above, an external active switch requires three
+ connections, one to the positive battery terminal, one to
+ the flight computer positive input and one to ground.
+ </para>
+ <para>
+ The positive battery terminal is available on screw terminal
+ 2, the positive flight computer input is on terminal 1. To
+ hook a lead to ground, solder a piece of wire, 24 to 28
+ gauge stranded, to the GND hole just above terminal 1.
+ </para>
+ </section>
</section>
<section>
- <title>TeleMini</title>
+ <title>TeleMini v1.0</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>
+ <section>
+ <title>TeleMini v1.0 Screw Terminals</title>
+ <para>
+ TeleMini v1.0 has four screw terminals on the end of the
+ board opposite the telemetry antenna. Two are for the apogee
+ and two are for main igniter circuits. There are also wires
+ soldered to the board for the power switch. Using the
+ picture above and starting from the top for the terminals
+ and from the left for the power switch wires, the
+ connections are as follows:
+ </para>
+ <table frame='all'>
+ <title>TeleMini v1.0 Connections</title>
+ <?dbfo keep-together="always"?>
+ <tgroup cols='3' align='center' colsep='1' rowsep='1'>
+ <colspec align='center' colwidth='*' colname='Pin #'/>
+ <colspec align='center' colwidth='2*' colname='Pin Name'/>
+ <colspec align='left' colwidth='5*' colname='Description'/>
+ <thead>
+ <row>
+ <entry align='center'>Terminal #</entry>
+ <entry align='center'>Terminal Name</entry>
+ <entry align='center'>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>1</entry>
+ <entry>Apogee -</entry>
+ <entry>Apogee pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>2</entry>
+ <entry>Apogee +</entry>
+ <entry>Apogee pyro channel common connection to battery +</entry>
+ </row>
+ <row>
+ <entry>3</entry>
+ <entry>Main -</entry>
+ <entry>Main pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>4</entry>
+ <entry>Main +</entry>
+ <entry>Main pyro channel common connection to battery +</entry>
+ </row>
+ <row>
+ <entry>Left</entry>
+ <entry>Switch Output</entry>
+ <entry>Switch connection to flight computer</entry>
+ </row>
+ <row>
+ <entry>Right</entry>
+ <entry>Switch Input</entry>
+ <entry>Switch connection to positive battery terminal</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+ <section>
+ <title>Using a Separate Pyro Battery with TeleMini v1.0</title>
+ <para>
+ As described above, using an external pyro battery involves
+ connecting the negative battery terminal to the flight
+ computer ground, connecting the positive battery terminal to
+ one of the igniter leads and connecting the other igniter
+ lead to the per-channel pyro circuit connection. Because
+ there is no solid ground connection to use on TeleMini, this
+ is not recommended.
+ </para>
+ <para>
+ The only available ground connection on TeleMini v1.0 are
+ the two mounting holes next to the telemetry
+ antenna. Somehow connect a small piece of wire to one of
+ those holes and hook it to the negative pyro battery terminal.
+ </para>
+ <para>
+ Connecting the positive battery terminal to the pyro
+ charges must be done separate from TeleMini v1.0, by soldering
+ them together or using some other connector.
+ </para>
+ <para>
+ The other lead from each pyro charge is then inserted into
+ the appropriate per-pyro channel screw terminal (terminal 3 for the
+ Main charge, terminal 1 for the Apogee charge).
+ </para>
+ </section>
+ <section>
+ <title>Using an Active Switch with TeleMini v1.0</title>
+ <para>
+ As explained above, an external active switch requires three
+ connections, one to the positive battery terminal, one to
+ the flight computer positive input and one to ground. Again,
+ because TeleMini doesn't have any good ground connection,
+ this is not recommended.
+ </para>
+ <para>
+ The positive battery terminal is available on the Right
+ power switch wire, the positive flight computer input is on
+ the left power switch wire. Hook a lead to either of the
+ mounting holes for a ground connection.
+ </para>
+ </section>
+ </section>
+ <section>
+ <title>TeleMini v2.0</title>
+ <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
board fits in a 24mm coupler. There's also a battery connector
for a LiPo battery if you want to use one of those.
</para>
+ <section>
+ <title>TeleMini v2.0 Screw Terminals</title>
+ <para>
+ TeleMini v2.0 has two sets of four screw terminals on the end of the
+ board opposite the telemetry antenna. Using the picture
+ above, the top four have connections for the main pyro
+ circuit and an external battery and the bottom four have
+ connections for the apogee pyro circuit and the power
+ switch. Counting from the left, the connections are as follows:
+ </para>
+ <table frame='all'>
+ <title>TeleMini v2.0 Connections</title>
+ <?dbfo keep-together="always"?>
+ <tgroup cols='3' align='center' colsep='1' rowsep='1'>
+ <colspec align='center' colwidth='*' colname='Pin #'/>
+ <colspec align='center' colwidth='2*' colname='Pin Name'/>
+ <colspec align='left' colwidth='5*' colname='Description'/>
+ <thead>
+ <row>
+ <entry align='center'>Terminal #</entry>
+ <entry align='center'>Terminal Name</entry>
+ <entry align='center'>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Top 1</entry>
+ <entry>Main -</entry>
+ <entry>Main pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>Top 2</entry>
+ <entry>Main +</entry>
+ <entry>Main pyro channel common connection to battery +</entry>
+ </row>
+ <row>
+ <entry>Top 3</entry>
+ <entry>Battery +</entry>
+ <entry>Positive external battery terminal</entry>
+ </row>
+ <row>
+ <entry>Top 4</entry>
+ <entry>Battery -</entry>
+ <entry>Negative external battery terminal</entry>
+ </row>
+ <row>
+ <entry>Bottom 1</entry>
+ <entry>Apogee -</entry>
+ <entry>Apogee pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>Bottom 2</entry>
+ <entry>Apogee +</entry>
+ <entry>Apogee pyro channel common connection to
+ battery +</entry>
+ </row>
+ <row>
+ <entry>Bottom 3</entry>
+ <entry>Switch Output</entry>
+ <entry>Switch connection to flight computer</entry>
+ </row>
+ <row>
+ <entry>Bottom 4</entry>
+ <entry>Switch Input</entry>
+ <entry>Switch connection to positive battery terminal</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+ <section>
+ <title>Using a Separate Pyro Battery with TeleMini v2.0</title>
+ <para>
+ As described above, using an external pyro battery involves
+ connecting the negative battery terminal to the flight
+ computer ground, connecting the positive battery terminal to
+ one of the igniter leads and connecting the other igniter
+ lead to the per-channel pyro circuit connection.
+ </para>
+ <para>
+ To connect the negative pyro battery terminal to TeleMini
+ ground, connect it to the negative external battery
+ connection, top terminal 4.
+ </para>
+ <para>
+ Connecting the positive battery terminal to the pyro
+ charges must be done separate from TeleMini v2.0, by soldering
+ them together or using some other connector.
+ </para>
+ <para>
+ The other lead from each pyro charge is then inserted into
+ the appropriate per-pyro channel screw terminal (top
+ terminal 1 for the Main charge, bottom terminal 1 for the
+ Apogee charge).
+ </para>
+ </section>
+ <section>
+ <title>Using an Active Switch with TeleMini v2.0</title>
+ <para>
+ As explained above, an external active switch requires three
+ connections, one to the positive battery terminal, one to
+ the flight computer positive input and one to ground. Use
+ the negative external battery connection, top terminal 4 for
+ ground.
+ </para>
+ <para>
+ The positive battery terminal is available on bottom
+ terminal 4, the positive flight computer input is on the
+ bottom terminal 3.
+ </para>
+ </section>
</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
- screw terminals match TeleMini, so you can swap an EasyMini
- with a TeleMini.
+ screw terminals match TeleMini v2.0, so you can easily swap between
+ EasyMini and TeleMini.
</para>
+ <section>
+ <title>EasyMini Screw Terminals</title>
+ <para>
+ EasyMini has two sets of four screw terminals on the end of the
+ board opposite the telemetry antenna. Using the picture
+ above, the top four have connections for the main pyro
+ circuit and an external battery and the bottom four have
+ connections for the apogee pyro circuit and the power
+ switch. Counting from the left, the connections are as follows:
+ </para>
+ <table frame='all'>
+ <title>EasyMini Connections</title>
+ <?dbfo keep-together="always"?>
+ <tgroup cols='3' align='center' colsep='1' rowsep='1'>
+ <colspec align='center' colwidth='*' colname='Pin #'/>
+ <colspec align='center' colwidth='2*' colname='Pin Name'/>
+ <colspec align='left' colwidth='5*' colname='Description'/>
+ <thead>
+ <row>
+ <entry align='center'>Terminal #</entry>
+ <entry align='center'>Terminal Name</entry>
+ <entry align='center'>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Top 1</entry>
+ <entry>Main -</entry>
+ <entry>Main pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>Top 2</entry>
+ <entry>Main +</entry>
+ <entry>Main pyro channel common connection to battery +</entry>
+ </row>
+ <row>
+ <entry>Top 3</entry>
+ <entry>Battery +</entry>
+ <entry>Positive external battery terminal</entry>
+ </row>
+ <row>
+ <entry>Top 4</entry>
+ <entry>Battery -</entry>
+ <entry>Negative external battery terminal</entry>
+ </row>
+ <row>
+ <entry>Bottom 1</entry>
+ <entry>Apogee -</entry>
+ <entry>Apogee pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>Bottom 2</entry>
+ <entry>Apogee +</entry>
+ <entry>Apogee pyro channel common connection to
+ battery +</entry>
+ </row>
+ <row>
+ <entry>Bottom 3</entry>
+ <entry>Switch Output</entry>
+ <entry>Switch connection to flight computer</entry>
+ </row>
+ <row>
+ <entry>Bottom 4</entry>
+ <entry>Switch Input</entry>
+ <entry>Switch connection to positive battery terminal</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+ <section>
+ <title>Using a Separate Pyro Battery with EasyMini</title>
+ <para>
+ As described above, using an external pyro battery involves
+ connecting the negative battery terminal to the flight
+ computer ground, connecting the positive battery terminal to
+ one of the igniter leads and connecting the other igniter
+ lead to the per-channel pyro circuit connection.
+ </para>
+ <para>
+ To connect the negative pyro battery terminal to TeleMini
+ ground, connect it to the negative external battery
+ connection, top terminal 4.
+ </para>
+ <para>
+ Connecting the positive battery terminal to the pyro
+ charges must be done separate from EasyMini, by soldering
+ them together or using some other connector.
+ </para>
+ <para>
+ The other lead from each pyro charge is then inserted into
+ the appropriate per-pyro channel screw terminal (top
+ terminal 1 for the Main charge, bottom terminal 1 for the
+ Apogee charge).
+ </para>
+ </section>
+ <section>
+ <title>Using an Active Switch with EasyMini</title>
+ <para>
+ As explained above, an external active switch requires three
+ connections, one to the positive battery terminal, one to
+ the flight computer positive input and one to ground. Use
+ the negative external battery connection, top terminal 4 for
+ ground.
+ </para>
+ <para>
+ The positive battery terminal is available on bottom
+ terminal 4, the positive flight computer input is on the
+ bottom terminal 3.
+ </para>
+ </section>
</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,
the board is aligned with the flight axis. It can be mounted
either antenna up or down.
</para>
+ <section>
+ <title>TeleMega Screw Terminals</title>
+ <para>
+ TeleMega has two sets of nine screw terminals on the end of
+ the board opposite the telemetry antenna. They are as follows:
+ </para>
+ <table frame='all'>
+ <title>TeleMega Screw Terminals</title>
+ <?dbfo keep-together="always"?>
+ <tgroup cols='3' align='center' colsep='1' rowsep='1'>
+ <colspec align='center' colwidth='*' colname='Pin #'/>
+ <colspec align='center' colwidth='2*' colname='Pin Name'/>
+ <colspec align='left' colwidth='5*' colname='Description'/>
+ <thead>
+ <row>
+ <entry align='center'>Terminal #</entry>
+ <entry align='center'>Terminal Name</entry>
+ <entry align='center'>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Top 1</entry>
+ <entry>Switch Input</entry>
+ <entry>Switch connection to positive battery terminal</entry>
+ </row>
+ <row>
+ <entry>Top 2</entry>
+ <entry>Switch Output</entry>
+ <entry>Switch connection to flight computer</entry>
+ </row>
+ <row>
+ <entry>Top 3</entry>
+ <entry>GND</entry>
+ <entry>Ground connection for use with external active switch</entry>
+ </row>
+ <row>
+ <entry>Top 4</entry>
+ <entry>Main -</entry>
+ <entry>Main pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>Top 5</entry>
+ <entry>Main +</entry>
+ <entry>Main pyro channel common connection to battery +</entry>
+ </row>
+ <row>
+ <entry>Top 6</entry>
+ <entry>Apogee -</entry>
+ <entry>Apogee pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>Top 7</entry>
+ <entry>Apogee +</entry>
+ <entry>Apogee pyro channel common connection to battery +</entry>
+ </row>
+ <row>
+ <entry>Top 8</entry>
+ <entry>D -</entry>
+ <entry>D pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>Top 9</entry>
+ <entry>D +</entry>
+ <entry>D pyro channel common connection to battery +</entry>
+ </row>
+ <row>
+ <entry>Bottom 1</entry>
+ <entry>GND</entry>
+ <entry>Ground connection for negative pyro battery terminal</entry>
+ </row>
+ <row>
+ <entry>Bottom 2</entry>
+ <entry>Pyro</entry>
+ <entry>Positive pyro battery terminal</entry>
+ </row>
+ <row>
+ <entry>Bottom 3</entry>
+ <entry>Lipo</entry>
+ <entry>
+ Power switch output. Use to connect main battery to
+ pyro battery input
+ </entry>
+ </row>
+ <row>
+ <entry>Bottom 4</entry>
+ <entry>A -</entry>
+ <entry>A pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>Bottom 5</entry>
+ <entry>A +</entry>
+ <entry>A pyro channel common connection to battery +</entry>
+ </row>
+ <row>
+ <entry>Bottom 6</entry>
+ <entry>B -</entry>
+ <entry>B pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>Bottom 7</entry>
+ <entry>B +</entry>
+ <entry>B pyro channel common connection to battery +</entry>
+ </row>
+ <row>
+ <entry>Bottom 8</entry>
+ <entry>C -</entry>
+ <entry>C pyro channel connection to pyro circuit</entry>
+ </row>
+ <row>
+ <entry>Bottom 9</entry>
+ <entry>C +</entry>
+ <entry>C pyro channel common connection to battery +</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+ <section>
+ <title>Using a Separate Pyro Battery with TeleMega</title>
+ <para>
+ TeleMega provides explicit support for an external pyro
+ battery. All that is required is to remove the jumper
+ between the lipo terminal (Bottom 3) and the pyro terminal
+ (Bottom 2). Then hook the negative pyro battery terminal to ground
+ (Bottom 1) and the positive pyro battery to the pyro battery
+ input (Bottom 2). You can then use the existing pyro screw
+ terminals to hook up all of the pyro charges.
+ </para>
+ </section>
+ <section>
+ <title>Using Only One Battery With TeleMega</title>
+ <para>
+ Because TeleMega has built-in support for a separate pyro
+ battery, if you want to fly with just one battery running
+ both the computer and firing the charges, you need to
+ connect the flight computer battery to the pyro
+ circuit. TeleMega has two screw terminals for this—hook a
+ wire from the Lipo terminal (Bottom 3) to the Pyro terminal
+ (Bottom 2).
+ </para>
+ </section>
+ <section>
+ <title>Using an Active Switch with TeleMega</title>
+ <para>
+ As explained above, an external active switch requires three
+ connections, one to the positive battery terminal, one to
+ the flight computer positive input and one to ground.
+ </para>
+ <para>
+ The positive battery terminal is available on Top terminal
+ 1, the positive flight computer input is on Top terminal
+ 2. Ground is on Top terminal 3.
+ </para>
+ </section>
</section>
<section>
<title>Flight Data Recording</title>
</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'/>
apogee and main ejection charges. All Altus Metrum products are
designed for use with single-cell batteries with 3.7 volts
nominal. TeleMini v2.0 and EasyMini may also be used with other
- batteries as long as they supply between 4 and 12 volts.
+ batteries as long as they supply between 4 and 12 volts.
</para>
<para>
The battery connectors are a standard 2-pin JST connector and
pyro battery, check out the “External Pyro Battery” section in this
manual for instructions on how to wire that up. The altimeters are
designed to work with an external pyro battery of no more than 15 volts.
-
</para>
<para>
Ejection charges are wired directly to the screw terminal block
adequate. However, if you are installing in a carbon-fiber or
metal electronics bay which is opaque to RF signals, you may need to
use off-board external antennas instead. In this case, you can
- order an altimeter with an SMA connector for the UHF antenna
- connection, and, on TeleMetrum v1, you can unplug the integrated GPS
+ replace the stock UHF antenna wire with an edge-launched SMA connector,
+ and, on TeleMetrum v1, you can unplug the integrated GPS
antenna and select an appropriate off-board GPS antenna with
cable terminating in a U.FL connector.
</para>
The AltOS firmware build for the altimeters has two
fundamental modes, “idle” and “flight”. Which of these modes
the firmware operates in is determined at start up time. For
- TeleMetrum, the mode is controlled by the orientation of the
+ TeleMetrum and TeleMega, which have accelerometers, the mode is
+ controlled by the orientation of the
rocket (well, actually the board, of course...) at the time
power is switched on. If the rocket is “nose up”, then
- TeleMetrum assumes it's on a rail or rod being prepared for
+ the flight computer assumes it's on a rail or rod being prepared for
launch, so the firmware chooses flight mode. However, if the
rocket is more or less horizontal, the firmware instead enters
idle mode. Since TeleMini v2.0 and EasyMini don't have an
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>
+ Decelerating, but moving faster than 200m/s.
+ </para>
+ </entry>
+ </row>
+ <row>
+ <entry>Coast</entry>
+ <entry>C</entry>
+ <entry>dah dit dah dit</entry>
+ <entry>
+ <para>
+ Decelerating, 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
<section>
<title>Radio Link </title>
<para>
- The chip our boards are based on incorporates an RF transceiver, but
+ Our flight computers all incorporate an RF transceiver, but
it's not a full duplex system... each end can only be transmitting or
receiving at any given moment. So we had to decide how to manage the
link.
performance in higher altitude flights!
</para>
<para>
- TeleMetrum v2.0 and TeleMega can send APRS if desired, the
+ TeleMetrum v2.0 and TeleMega can send APRS if desired, and the
interval between APRS packets can be configured. As each APRS
packet takes a full second to transmit, we recommend an
interval of at least 5 seconds to avoid consuming too much
the available storage, future flights will not get logged
until you erase some of the stored ones.
</para>
+ <para>
+ Even though our flight computers (except TeleMini v1.0) can store
+ multiple flights, we strongly recommend downloading and saving
+ flight data after each flight.
+ </para>
</section>
<section>
<title>Ignite Mode</title>
Instead of firing one charge at apogee and another charge at
a fixed height above the ground, you can configure the
altimeter to fire both at apogee or both during
- descent. This was added to support an airframe that has two
- altimeters, one in the fin can and one in the
- nose.
+ descent. This was added to support an airframe Bdale designed that
+ had two altimeters, one in the fin can and one in the nose.
</para>
<para>
Providing the ability to use both igniters for apogee or
</para>
</section>
<section>
- <title>Pyro Channels</title>
+ <title>Configurable Pyro Channels</title>
<para>
In addition to the usual Apogee and Main pyro channels,
TeleMega has four additional channels that can be configured
system. Because this value is computed by integrating
rate gyros, it gets progressively less accurate as the
flight goes on. It should have an accumulated error of
- less than .2°/second (after 10 seconds of flight, the
+ less than 0.2°/second (after 10 seconds of flight, the
error should be less than 2°).
</para>
<para>
<listitem>
<para>
Fast. The motor has burned out and the rocket is
- descellerating, but it is going faster than 200m/s.
+ decelerating, but it is going faster than 200m/s.
</para>
</listitem>
<listitem>
</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
monitor telemetry data, configure devices and many other
tasks. The primary interface window provides a selection of
- buttons, one for each major activity in the system. This manual
- is split into chapters, each of which documents one of the tasks
+ buttons, one for each major activity in the system. This chapter
+ is split into sections, each of which documents one of the tasks
provided from the top-level toolbar.
</para>
<section>
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
<term>Battery Voltage</term>
<listitem>
<para>
- This indicates whether the Li-Po battery
- powering the TeleMetrum has sufficient charge to last for
+ This indicates whether the Li-Po battery powering the
+ flight computer has sufficient charge to last for
the duration of the flight. A value of more than
3.8V is required for a 'GO' status.
</para>
space remaining on-board to store flight data for the
upcoming flight. If you've downloaded data, but failed
to erase flights, there may not be any space
- left. TeleMetrum can store multiple flights, depending
- on the configured maximum flight log size. TeleMini
- stores only a single flight, so it will need to be
+ left. Most of our flight computers can store multiple
+ flights, depending on the configured maximum flight log
+ size. TeleMini v1.0 stores only a single flight, so it
+ will need to be
downloaded and erased after each flight to capture
data. This only affects on-board flight logging; the
altimeter will still transmit telemetry and fire
- ejection charges at the proper times.
+ ejection charges at the proper times even if the flight
+ data storage is full.
</para>
</listitem>
</varlistentry>
</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 TeleMetrum GPS are
+ The current latitude and longitude reported by the GPS are
also shown. Note that under high acceleration, these values
may not get updated as the GPS receiver loses position
fix. Once the rocket starts coasting, the receiver should
</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
be below 10m/s when under the main parachute in a dual-deploy flight.
</para>
<para>
- For TeleMetrum altimeters, you can locate the rocket in the
+ With GPS-equipped flight computers, you can locate the rocket in the
sky using the elevation and bearing information to figure
out where to look. Elevation is in degrees above the
horizon. Bearing is reported in degrees relative to true
</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
unit and have that compute a track to the landing location.
</para>
<para>
- Both TeleMini and TeleMetrum will continue to transmit RDF
+ Our flight computers will continue to transmit RDF
tones after landing, allowing you to locate the rocket by
following the radio signal if necessary. You may need to get
away from the clutter of the flight line, or even get up on
during the flight are displayed for your admiring observers.
The accuracy of these immediate values depends on the quality
of your radio link and how many packets were received.
- Recovering the on-board data after flight will likely yield
+ Recovering the on-board data after flight may yield
more precise results.
</para>
<para>
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
system can handle, and is not subject to radio drop-outs. As
such, it provides a more complete and precise record of the
flight. The 'Save Flight Data' button allows you to read the
- flash memory and write it to disk. As TeleMini has only a barometer, it
- records data at the same rate as the telemetry signal, but there will be
- no data lost due to telemetry drop-outs.
+ flash memory and write it to disk.
</para>
<para>
Clicking on the 'Save Flight Data' button brings up a list of
- connected TeleMetrum and TeleDongle devices. If you select a
- TeleMetrum device, the flight data will be downloaded from that
+ connected flight computers and TeleDongle devices. If you select a
+ flight computer, the flight data will be downloaded from that
device directly. If you select a TeleDongle device, flight data
- will be downloaded from an altimeter over radio link via the
+ will be downloaded from a flight computer over radio link via the
specified TeleDongle. See the chapter on Controlling An Altimeter
Over The Radio Link for more information.
</para>
.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>
<para>
This tool takes the raw data files and makes them available for
external analysis. When you select this button, you are prompted to
- select a flight
- data file (either .eeprom or .telem will do, remember that
- .eeprom files contain higher resolution and more continuous
- data). Next, a second dialog appears which is used to select
+ select a flight data file, which can be either a .eeprom or .telem.
+ The .eeprom files contain higher resolution and more continuous data,
+ while .telem files contain receiver signal strength information.
+ Next, a second dialog appears which is used to select
where to write the resulting file. It has a selector to choose
between CSV and KML file formats.
</para>
</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>
<section>
<title>APRS Interval</title>
<para>
- How often to transmit GPS information via APRS. This option
- is available on TeleMetrum v2 and TeleMega
- boards. TeleMetrum v1 boards cannot transmit APRS
+ How often to transmit GPS information via APRS (in
+ seconds). When set to zero, APRS transmission is
+ disabled. This option is available on TeleMetrum v2 and
+ TeleMega boards. TeleMetrum v1 boards cannot transmit APRS
packets. Note that a single APRS packet takes nearly a full
second to transmit, so enabling this option will prevent
sending any other telemetry during that time.
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>
<para>
- Because it includes an accelerometer, TeleMetrum and
+ Because they include accelerometers, TeleMetrum and
TeleMega are sensitive to the orientation of the board. By
- default, it expects the antenna end to point forward. This
+ default, they expect the antenna end to point forward. This
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
- TeleMetrum board must point forward, in line with the
- expected flight path.
- </para>
- </listitem>
- <listitem>
- <para>
- Antenna Down. In this mode, the antenna end of the
- TeleMetrum board 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>
<section>
<title>Flash Image</title>
<para>
- This reprograms Altus Metrum device with new
+ This reprograms Altus Metrum devices with new
firmware. TeleMetrum v1.x, TeleDongle, TeleMini and TeleBT are
all reprogrammed by using another similar unit as a
programming dongle (pair programming). TeleMega, TeleMetrum v2
(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 TeleMetrum to help test
- recovery systems deployment. Because this command can operate
+ This activates the igniter circuits in the flight computer to help
+ test recovery systems deployment. Because this command can operate
over the Packet Command Link, you can prepare the rocket as
for flight and then test the recovery system without needing
to snake wires inside the air-frame.
</para>
<para>
Selecting the 'Fire Igniter' button brings up the usual device
- selection dialog. Pick the desired TeleDongle or TeleMetrum
- device. This brings up another window which shows the current
- continuity test status for both apogee and main charges.
+ selection dialog. Pick the desired device. This brings up another
+ 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
There's a drop-down menu of launch sites we know about; if
your favorites aren't there, please let us know the lat/lon
and name of the site. The contents of this list are actually
- downloaded at run-time, so as new sites are sent in, they'll
- get automatically added to this list.
+ downloaded from our server at run-time, so as new sites are sent
+ in, they'll get automatically added to this list.
</para>
<para>
If the launch site isn't in the list, you can manually enter the lat/lon values
<para>
AltosDroid provides the same flight monitoring capabilities as
AltosUI, but runs on Android devices and is designed to connect
- to a TeleBT receiver over Bluetooth™. Altos Droid monitors
+ to a TeleBT receiver over Bluetooth™. AltosDroid monitors
telemetry data, logging it to internal storage in the Android
device, and presents that data in a UI the same way the 'Monitor
Flight' window does in AltosUI.
<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
</para>
</section>
<section>
- <title>Altos Droid Flight Monitoring</title>
+ <title>AltosDroid Flight Monitoring</title>
<para>
- Altos Droid is designed to mimic the AltosUI flight monitoring
+ AltosDroid is designed to mimic the AltosUI flight monitoring
display, providing separate tabs for each stage of your rocket
flight along with a tab containing a map of the local area
with icons marking the current location of the altimeter and
<section>
<title>Downloading Flight Logs</title>
<para>
- Altos Droid always saves every bit of telemetry data it
+ AltosDroid always saves every bit of telemetry data it
receives. To download that to a computer for use with AltosUI,
simply remove the SD card from your Android device, or connect
your device to your computer's USB port and browse the files
<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
</book>
<!-- LocalWords: Altusmetrum
--->
\ No newline at end of file
+-->
projects / fw / altos / blobdiff