<title>The Altus Metrum System</title>
<subtitle>An Owner's Manual for Altus Metrum Rocketry Electronics</subtitle>
<bookinfo>
- <mediaobject>
- <imageobject>
- <imagedata fileref="../altosui/altusmetrum.jpg" role="top"/>
- </imageobject>
- </mediaobject>
<author>
<firstname>Bdale</firstname>
<surname>Garbee</surname>
<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>
<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.
</section>
<section>
<title>TeleMetrum</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="telemetrum-v1.1-thside.jpg" width="5.5in" scalefit="1"/>
- </imageobject>
- </mediaobject>
+ <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>
- <mediaobject>
- <imageobject>
- <imagedata fileref="telemini-v1-top.jpg" width="5.5in" scalefit="1"/>
- </imageobject>
- </mediaobject>
+ <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>
- <mediaobject>
- <imageobject>
- <imagedata fileref="telemini-v2-top.jpg" width="5.5in" scalefit="1"/>
- </imageobject>
- </mediaobject>
+ <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>
- <mediaobject>
- <imageobject>
- <imagedata fileref="easymini-top.jpg" width="5.5in" scalefit="1"/>
- </imageobject>
- </mediaobject>
+ <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 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>
- <mediaobject>
- <imageobject>
- <imagedata fileref="telemega-v1.0-top.jpg" width="5.5in" scalefit="1"/>
- </imageobject>
- </mediaobject>
+ <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>
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
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
<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
is split into sections, each of which documents one of the tasks
provided from the top-level toolbar.
</para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="altosui.png" width="5.5in"/>
- </imageobject>
- </mediaobject>
<section>
<title>Monitor Flight</title>
<subtitle>Receive, Record and Display Telemetry Data</subtitle>
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
<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.
</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>
(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
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