<html lang="en">
<head>
<meta charset="UTF-8">
-<!--[if IE]><meta http-equiv="X-UA-Compatible" content="IE=edge"><![endif]-->
+<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
-<meta name="generator" content="Asciidoctor 1.5.8">
+<meta name="generator" content="Asciidoctor 2.0.10">
<meta name="author" content="Keith Packard, Bdale Garbee, Bob Finch, Anthony Towns">
-<meta name="copyright" content="Bdale Garbee and Keith Packard 2018">
+<meta name="copyright" content="Bdale Garbee and Keith Packard 2020">
<title>The Altus Metrum System: An Owner’s Manual for Altus Metrum Rocketry Electronics</title>
<link rel="stylesheet" href="./am.css">
</head>
-<body class="article">
+<body class="book">
<div id="header">
<h1>The Altus Metrum System: An Owner’s Manual for Altus Metrum Rocketry Electronics</h1>
<div class="details">
<span id="email2" class="email"><a href="mailto:bdale@gag.com">bdale@gag.com</a></span><br>
<span id="author3" class="author">Bob Finch</span><br>
<span id="author4" class="author">Anthony Towns</span><br>
-<span id="revnumber">version v1.9,</span>
-<span id="revdate">31 Dec 2018</span>
-<br><span id="revremark">Add EasyMega v2.0 support</span>
+<span id="revnumber">version v1.9.5,</span>
+<span id="revdate">29 Sep 2020</span>
</div>
<div id="toc" class="toc">
<div id="toctitle">Table of Contents</div>
<li><a href="#_using_an_active_switch_with_easymega">8.4. Using an Active Switch with EasyMega</a></li>
</ul>
</li>
-<li><a href="#_installation">9. Installation</a></li>
-<li><a href="#_using_altus_metrum_products">10. Using Altus Metrum Products</a>
+<li><a href="#_easytimer">9. EasyTimer</a>
<ul class="sectlevel2">
-<li><a href="#_being_legal">10.1. Being Legal</a></li>
-<li><a href="#_in_the_rocket">10.2. In the Rocket</a></li>
-<li><a href="#_on_the_ground">10.3. On the Ground</a></li>
-<li><a href="#_data_analysis">10.4. Data Analysis</a></li>
-<li><a href="#_future_plans">10.5. Future Plans</a></li>
+<li><a href="#_easytimer_screw_terminals">9.1. EasyTimer Screw Terminals</a></li>
+<li><a href="#_connecting_a_battery_to_easytimer">9.2. Connecting A Battery To EasyTimer</a></li>
+<li><a href="#_charging_lithium_batteries_2">9.3. Charging Lithium Batteries</a></li>
+<li><a href="#_using_a_separate_pyro_battery_with_easytimer">9.4. Using a Separate Pyro Battery with EasyTimer</a></li>
+<li><a href="#_using_an_active_switch_with_easytimer">9.5. Using an Active Switch with EasyTimer</a></li>
</ul>
</li>
-<li><a href="#_altosui">11. AltosUI</a>
+<li><a href="#_installation">10. Installation</a></li>
+<li><a href="#_using_altus_metrum_products">11. Using Altus Metrum Products</a>
<ul class="sectlevel2">
-<li><a href="#_monitor_flight">11.1. Monitor Flight</a></li>
-<li><a href="#_save_flight_data">11.2. Save Flight Data</a></li>
-<li><a href="#_replay_flight">11.3. Replay Flight</a></li>
-<li><a href="#_graph_data">11.4. Graph Data</a></li>
-<li><a href="#_export_data">11.5. Export Data</a></li>
-<li><a href="#_configure_altimeter">11.6. Configure Altimeter</a></li>
-<li><a href="#_configure_altosui">11.7. Configure AltosUI</a></li>
-<li><a href="#_configure_groundstation">11.8. Configure Groundstation</a></li>
-<li><a href="#_flash_image">11.9. Flash Image</a></li>
-<li><a href="#_fire_igniter">11.10. Fire Igniter</a></li>
-<li><a href="#_scan_channels">11.11. Scan Channels</a></li>
-<li><a href="#_load_maps">11.12. Load Maps</a></li>
-<li><a href="#_monitor_idle">11.13. Monitor Idle</a></li>
-</ul>
-</li>
-<li><a href="#_altosdroid">12. AltosDroid</a>
+<li><a href="#_being_legal">11.1. Being Legal</a></li>
+<li><a href="#_in_the_rocket">11.2. In the Rocket</a></li>
+<li><a href="#_on_the_ground">11.3. On the Ground</a></li>
+<li><a href="#_data_analysis">11.4. Data Analysis</a></li>
+<li><a href="#_future_plans">11.5. Future Plans</a></li>
+</ul>
+</li>
+<li><a href="#_altosui">12. AltosUI</a>
<ul class="sectlevel2">
-<li><a href="#_installing_altosdroid">12.1. Installing AltosDroid</a></li>
-<li><a href="#_charging_telebt_battery">12.2. Charging TeleBT Battery</a></li>
-<li><a href="#_connecting_to_telebt_over_bluetooth">12.3. Connecting to TeleBT over Bluetooth™</a></li>
-<li><a href="#_connecting_to_teledongle_or_telebt_over_usb">12.4. Connecting to TeleDongle or TeleBT over USB</a></li>
-<li><a href="#_altosdroid_menu">12.5. AltosDroid Menu</a></li>
-<li><a href="#_setup">12.6. Setup</a></li>
-<li><a href="#_idle_mode">12.7. Idle Mode</a></li>
-<li><a href="#_altosdroid_flight_monitoring">12.8. AltosDroid Flight Monitoring</a></li>
-<li><a href="#_pad">12.9. Pad</a></li>
-<li><a href="#_flight">12.10. Flight</a></li>
-<li><a href="#_recover">12.11. Recover</a></li>
-<li><a href="#_map_2">12.12. Map</a></li>
-<li><a href="#_downloading_flight_logs">12.13. Downloading Flight Logs</a></li>
+<li><a href="#_monitor_flight">12.1. Monitor Flight</a></li>
+<li><a href="#_save_flight_data">12.2. Save Flight Data</a></li>
+<li><a href="#_replay_flight">12.3. Replay Flight</a></li>
+<li><a href="#_graph_data">12.4. Graph Data</a></li>
+<li><a href="#_export_data">12.5. Export Data</a></li>
+<li><a href="#_configure_altimeter">12.6. Configure Altimeter</a></li>
+<li><a href="#_configure_altosui">12.7. Configure AltosUI</a></li>
+<li><a href="#_configure_groundstation">12.8. Configure Groundstation</a></li>
+<li><a href="#_flash_image">12.9. Flash Image</a></li>
+<li><a href="#_fire_igniter">12.10. Fire Igniter</a></li>
+<li><a href="#_scan_channels">12.11. Scan Channels</a></li>
+<li><a href="#_load_maps">12.12. Load Maps</a></li>
+<li><a href="#_monitor_idle">12.13. Monitor Idle</a></li>
+</ul>
+</li>
+<li><a href="#_altosdroid">13. AltosDroid</a>
+<ul class="sectlevel2">
+<li><a href="#_installing_altosdroid">13.1. Installing AltosDroid</a></li>
+<li><a href="#_charging_telebt_battery">13.2. Charging TeleBT Battery</a></li>
+<li><a href="#_connecting_to_telebt_over_bluetooth">13.3. Connecting to TeleBT over Bluetooth™</a></li>
+<li><a href="#_connecting_to_teledongle_or_telebt_over_usb">13.4. Connecting to TeleDongle or TeleBT over USB</a></li>
+<li><a href="#_altosdroid_menu">13.5. AltosDroid Menu</a></li>
+<li><a href="#_setup">13.6. Setup</a></li>
+<li><a href="#_idle_mode">13.7. Idle Mode</a></li>
+<li><a href="#_altosdroid_flight_monitoring">13.8. AltosDroid Flight Monitoring</a></li>
+<li><a href="#_pad">13.9. Pad</a></li>
+<li><a href="#_flight">13.10. Flight</a></li>
+<li><a href="#_recover">13.11. Recover</a></li>
+<li><a href="#_map_2">13.12. Map</a></li>
+<li><a href="#_downloading_flight_logs">13.13. Downloading Flight Logs</a></li>
</ul>
</li>
<li><a href="#_system_operation">Appendix A: System Operation</a>
<li><a href="#_handling_precautions">Appendix B: Handling Precautions</a></li>
<li><a href="#_updating_device_firmware">Appendix C: Updating Device Firmware</a>
<ul class="sectlevel2">
-<li><a href="#_updating_telemega_telemetrum_v2_easymega_easymini_or_teledongle_v3_firmware">C.1. Updating TeleMega, TeleMetrum v2, EasyMega, EasyMini or TeleDongle v3 Firmware</a></li>
+<li><a href="#_updating_telemega_telemetrum_v2_or_newer_easymega_easymini_teledongle_v3_or_telebt_v3_firmware">C.1. Updating TeleMega, TeleMetrum v2 or newer, EasyMega, EasyMini, TeleDongle v3 or TeleBT v3 Firmware</a></li>
<li><a href="#_pair_programming">C.2. Pair Programming</a></li>
</ul>
</li>
<li><a href="#_altus_metrum_hardware_specifications">Appendix E: Altus Metrum Hardware Specifications</a></li>
<li><a href="#_release_notes">Appendix F: Release Notes</a>
<ul class="sectlevel2">
-<li><a href="#_release_notes_for_version_1_9">F.1. Release Notes for Version 1.9</a></li>
-<li><a href="#_release_notes_for_version_1_8_7">F.2. Release Notes for Version 1.8.7</a></li>
-<li><a href="#_release_notes_for_version_1_8_6">F.3. Release Notes for Version 1.8.6</a></li>
-<li><a href="#_release_notes_for_version_1_8_5">F.4. Release Notes for Version 1.8.5</a></li>
-<li><a href="#_release_notes_for_version_1_8_4">F.5. Release Notes for Version 1.8.4</a></li>
-<li><a href="#_release_notes_for_version_1_8_3">F.6. Release Notes for Version 1.8.3</a></li>
-<li><a href="#_release_notes_for_version_1_8_2">F.7. Release Notes for Version 1.8.2</a></li>
-<li><a href="#_release_notes_for_version_1_8_1">F.8. Release Notes for Version 1.8.1</a></li>
-<li><a href="#_release_notes_for_version_1_8">F.9. Release Notes for Version 1.8</a></li>
-<li><a href="#_release_notes_for_version_1_7">F.10. Release Notes for Version 1.7</a></li>
-<li><a href="#_release_notes_for_version_1_6_8">F.11. Release Notes for Version 1.6.8</a></li>
-<li><a href="#_release_notes_for_version_1_6_5">F.12. Release Notes for Version 1.6.5</a></li>
-<li><a href="#_release_notes_for_version_1_6_4">F.13. Release Notes for Version 1.6.4</a></li>
-<li><a href="#_release_notes_for_version_1_6_3">F.14. Release Notes for Version 1.6.3</a></li>
-<li><a href="#_release_notes_for_version_1_6_2">F.15. Release Notes for Version 1.6.2</a></li>
-<li><a href="#_release_notes_for_version_1_6_1">F.16. Release Notes for Version 1.6.1</a></li>
-<li><a href="#_release_notes_for_version_1_6">F.17. Release Notes for Version 1.6</a></li>
-<li><a href="#_release_notes_for_version_1_5">F.18. Release Notes for Version 1.5</a></li>
-<li><a href="#_release_notes_for_version_1_4_2">F.19. Release Notes for Version 1.4.2</a></li>
-<li><a href="#_release_notes_for_version_1_4_1">F.20. Release Notes for Version 1.4.1</a></li>
-<li><a href="#_release_notes_for_version_1_4">F.21. Release Notes for Version 1.4</a></li>
-<li><a href="#_release_notes_for_version_1_3_2">F.22. Release Notes for Version 1.3.2</a></li>
-<li><a href="#_release_notes_for_version_1_3_1">F.23. Release Notes for Version 1.3.1</a></li>
-<li><a href="#_release_notes_for_version_1_3">F.24. Release Notes for Version 1.3</a></li>
-<li><a href="#_release_notes_for_version_1_2_1">F.25. Release Notes for Version 1.2.1</a></li>
-<li><a href="#_release_notes_for_version_1_2">F.26. Release Notes for Version 1.2</a></li>
-<li><a href="#_release_notes_for_version_1_1">F.27. Release Notes for Version 1.1</a></li>
-<li><a href="#_release_notes_for_version_1_1_2">F.28. Release Notes for Version 1.1</a></li>
-<li><a href="#_release_notes_for_version_1_0_1">F.29. Release Notes for Version 1.0.1</a></li>
-<li><a href="#_release_notes_for_version_0_9_2">F.30. Release Notes for Version 0.9.2</a></li>
-<li><a href="#_release_notes_for_version_0_9">F.31. Release Notes for Version 0.9</a></li>
-<li><a href="#_release_notes_for_version_0_8">F.32. Release Notes for Version 0.8</a></li>
-<li><a href="#_release_notes_for_version_0_7_1">F.33. Release Notes for Version 0.7.1</a></li>
+<li><a href="#_release_notes_for_version_1_9_5">F.1. Release Notes for Version 1.9.5</a></li>
+<li><a href="#_release_notes_for_version_1_9_4">F.2. Release Notes for Version 1.9.4</a></li>
+<li><a href="#_release_notes_for_version_1_9_3">F.3. Release Notes for Version 1.9.3</a></li>
+<li><a href="#_release_notes_for_version_1_9_2">F.4. Release Notes for Version 1.9.2</a></li>
+<li><a href="#_release_notes_for_version_1_9_1">F.5. Release Notes for Version 1.9.1</a></li>
+<li><a href="#_release_notes_for_version_1_9">F.6. Release Notes for Version 1.9</a></li>
+<li><a href="#_release_notes_for_version_1_8_7">F.7. Release Notes for Version 1.8.7</a></li>
+<li><a href="#_release_notes_for_version_1_8_6">F.8. Release Notes for Version 1.8.6</a></li>
+<li><a href="#_release_notes_for_version_1_8_5">F.9. Release Notes for Version 1.8.5</a></li>
+<li><a href="#_release_notes_for_version_1_8_4">F.10. Release Notes for Version 1.8.4</a></li>
+<li><a href="#_release_notes_for_version_1_8_3">F.11. Release Notes for Version 1.8.3</a></li>
+<li><a href="#_release_notes_for_version_1_8_2">F.12. Release Notes for Version 1.8.2</a></li>
+<li><a href="#_release_notes_for_version_1_8_1">F.13. Release Notes for Version 1.8.1</a></li>
+<li><a href="#_release_notes_for_version_1_8">F.14. Release Notes for Version 1.8</a></li>
+<li><a href="#_release_notes_for_version_1_7">F.15. Release Notes for Version 1.7</a></li>
+<li><a href="#_release_notes_for_version_1_6_8">F.16. Release Notes for Version 1.6.8</a></li>
+<li><a href="#_release_notes_for_version_1_6_5">F.17. Release Notes for Version 1.6.5</a></li>
+<li><a href="#_release_notes_for_version_1_6_4">F.18. Release Notes for Version 1.6.4</a></li>
+<li><a href="#_release_notes_for_version_1_6_3">F.19. Release Notes for Version 1.6.3</a></li>
+<li><a href="#_release_notes_for_version_1_6_2">F.20. Release Notes for Version 1.6.2</a></li>
+<li><a href="#_release_notes_for_version_1_6_1">F.21. Release Notes for Version 1.6.1</a></li>
+<li><a href="#_release_notes_for_version_1_6">F.22. Release Notes for Version 1.6</a></li>
+<li><a href="#_release_notes_for_version_1_5">F.23. Release Notes for Version 1.5</a></li>
+<li><a href="#_release_notes_for_version_1_4_2">F.24. Release Notes for Version 1.4.2</a></li>
+<li><a href="#_release_notes_for_version_1_4_1">F.25. Release Notes for Version 1.4.1</a></li>
+<li><a href="#_release_notes_for_version_1_4">F.26. Release Notes for Version 1.4</a></li>
+<li><a href="#_release_notes_for_version_1_3_2">F.27. Release Notes for Version 1.3.2</a></li>
+<li><a href="#_release_notes_for_version_1_3_1">F.28. Release Notes for Version 1.3.1</a></li>
+<li><a href="#_release_notes_for_version_1_3">F.29. Release Notes for Version 1.3</a></li>
+<li><a href="#_release_notes_for_version_1_2_1">F.30. Release Notes for Version 1.2.1</a></li>
+<li><a href="#_release_notes_for_version_1_2">F.31. Release Notes for Version 1.2</a></li>
+<li><a href="#_release_notes_for_version_1_1">F.32. Release Notes for Version 1.1</a></li>
+<li><a href="#_release_notes_for_version_1_1_2">F.33. Release Notes for Version 1.1</a></li>
+<li><a href="#_release_notes_for_version_1_0_1">F.34. Release Notes for Version 1.0.1</a></li>
+<li><a href="#_release_notes_for_version_0_9_2">F.35. Release Notes for Version 0.9.2</a></li>
+<li><a href="#_release_notes_for_version_0_9">F.36. Release Notes for Version 0.9</a></li>
+<li><a href="#_release_notes_for_version_0_8">F.37. Release Notes for Version 0.8</a></li>
+<li><a href="#_release_notes_for_version_0_7_1">F.38. Release Notes for Version 0.7.1</a></li>
</ul>
</li>
</ul>
<p>The first device created for our community was TeleMetrum, a dual
deploy altimeter with fully integrated GPS and radio telemetry
as standard features, and a “companion interface” that will
-support optional capabilities in the future. The latest version
-of TeleMetrum, v2.0, has all of the same features but with
+support optional capabilities in the future. The later versions
+of TeleMetrum, v2 and newer, have all of the same features but with
improved sensors and radio to offer increased performance.</p>
</div>
<div class="paragraph">
in, because the on-off switch does NOT control the
charging circuitry.
The Lithium Polymer
+EasyTimer,
TeleMini and
EasyMini battery can be charged by disconnecting it
from the board and plugging it into a standalone
</div>
<div class="paragraph">
<p>You can also choose to use another battery with
+EasyTimer 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
deeply discharged battery.</p>
</div>
<div class="paragraph">
-<p>TeleMetrum v2.0, TeleMega and EasyMega use a higher power battery charger,
-allowing them to charge the battery while running the board at
-maximum power. When the battery is charging, or when the board
-is consuming a lot of power, the red LED will be lit. When the
-battery is fully charged, the green LED will be lit. When the
-battery is damaged or missing, both LEDs will be lit, which
-appears yellow.</p>
+<p>TeleMetrum v2 or newer, TeleMega and EasyMega use a
+higher power battery charger, allowing them to charge
+the battery while running the board at maximum
+power. When the battery is charging, or when the board
+is consuming a lot of power, the red LED will be
+lit. When the battery is fully charged, the green LED
+will be lit. When the battery is damaged or missing,
+both LEDs will be lit, which appears yellow.</p>
</div>
</td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Additional Igniters</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">four very short beeps</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Continuity indication for the four additional pyro
-channels on TeleMega and EasyMega. One high tone for
-no continuity, one low tone for continuity. These are
+<td class="tableblock halign-left valign-top"><p class="tableblock">Continuity indication for the additional pyro
+channels on TeleMega, EasyMega and EasyTimer. One high tone for
+no continuity, one low tone for continuity. On TeleMega and EasyMegay, these are
produced after the continuity indicators for the two
primary igniter channels.</p></td>
</tr>
</div>
<div class="paragraph">
<p>For flight computers with accelerometers (TeleMetrum,
-EasyMega and TeleMega), the mode is selected by the
+EasyMega, TeleMega and EasyTimer), the mode is selected by the
orientation of the board during the self test
interval. If the board is pointing upwards as if ready
to fly, it will enter Flight/Pad mode. Otherwise, it will
<div class="paragraph">
<p>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
+the the switched 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
to hook this up for each flight computer will be found
in the section below for that flight computer.</p>
</div>
+<div class="paragraph">
+<p>Note that you must include a switch in the positive lead of
+the pyro battery for safety, as the on-board power switch
+circuit on our product only controls current flow from the
+the primary or system battery!</p>
+</div>
</div>
<div class="sect2">
<h3 id="_using_a_different_kind_of_battery">3.9. Using a Different Kind of Battery</h3>
<div class="paragraph">
<p>EasyMini
-and TeleMini v2 are
+and EasyTimer are
designed to use either a
lithium polymer battery or any other battery producing
between 4 and 12 volts, such as a rectangular 9V
<img src="./images/icons/warning.svg" alt="Warning">
</td>
<td class="content">
+TeleMini,
TeleMega, EasyMega and TeleMetrum are only designed to
operate off a single-cell Lithium Polymer battery and
cannot be used with any other kind. Connecting a
</div>
<div class="paragraph">
<p>There are two generations of the TeleMetrum design. The
-major changes in the v2 generation are:</p>
+major changes after v1 generation are:</p>
</div>
<div class="ulist">
<ul>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">3</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Main<br></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Main pyro channel common connection to battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Main +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Main pyro channel common connection to battery +</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">4</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">5</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee<br></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee pyro channel common connection to battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee pyro channel common connection to battery +</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">6</p></td>
strip and solder it in place.</p>
</div>
<div class="paragraph">
-<p>Connecting the positive battery terminal to the pyro
+<p>Connecting the switched positive battery terminal to the pyro
charges must be done separate from TeleMetrum, by soldering
-them together or using some other connector.</p>
+them together or using some other connector. Note that you
+must include a switch in the positive lead from the pyro
+battery for safety!</p>
</div>
<div class="paragraph">
<p>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).</p>
+the appropriate per-pyro channel screw terminal (terminal 4
+for the Main charge, terminal 6 for the Apogee charge).</p>
</div>
</div>
<div class="sect2">
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">2</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee<br></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee pyro channel common connection to battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee pyro channel common connection to battery +</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">3</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">4</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Main<br></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Main pyro channel common connection to battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Main +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Main pyro channel common connection to battery +</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Left</p></td>
<div class="paragraph">
<p>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.</p>
+computer ground, connecting the switched 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.</p>
</div>
<div class="paragraph">
<p>The only available ground connection on TeleMini v3 are
<div class="paragraph">
<p>Connecting the positive battery terminal to the pyro
charges must be done separate from TeleMini v3, by soldering
-them together or using some other connector.</p>
+them together or using some other connector. Note that you
+must include a switch in the pyro battery positive lead for
+safety!</p>
</div>
<div class="paragraph">
<p>The other lead from each pyro charge is then inserted into
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Top 2</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Main<br></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Main pyro channel common connection to battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Main +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Main pyro channel common connection to battery +</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Top 3</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Battery +</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Positive external battery terminal</p></td>
</tr>
<tr>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Bottom 2</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee<br></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee pyro channel common connection to battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee pyro channel common connection to battery +</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Bottom 3</p></td>
connection, top terminal 4.</p>
</div>
<div class="paragraph">
-<p>Connecting the positive battery terminal to the pyro
+<p>Connecting the switched positive battery terminal to the pyro
charges must be done separate from EasyMini, by soldering
-them together or using some other connector.</p>
+them together or using some other connector. Note that for
+safety, you must put a switch between the pyro battery and
+the rest of the circuit!</p>
</div>
<div class="paragraph">
<p>The other lead from each pyro charge is then inserted into
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Top 5</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Main<br></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Main pyro channel common connection to battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Main +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Main pyro channel common connection to battery +</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Top 6</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Top 7</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee<br></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee pyro channel common connection to battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee pyro channel common connection to battery +</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Top 8</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Top 9</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">D<br></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">D pyro channel common connection to battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">D +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">D pyro channel common connection to battery +</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Bottom 1</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Bottom 5</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">A<br></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">A pyro channel common connection to battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">A +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">A pyro channel common connection to battery +</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Bottom 6</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Bottom 7</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">B<br></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">B pyro channel common connection to battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">B +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">B pyro channel common connection to battery +</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Bottom 8</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Bottom 9</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">C<br></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">C pyro channel common connection to battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">C +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">C pyro channel common connection to battery +</p></td>
</tr>
</tbody>
</table>
<p>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
+(Bottom 2). Then hook the negative pyro battery terminal to
+ground (Bottom 1) and the switched positive pyro battery to
+the pyro battery input (Bottom 2). Note that you must include
+a switch between the pyro battery and the board for safety,
+as the on-board power switch circuit only supports the primary
+battery! You can then use the existing pyro screw
terminals to hook up all of the pyro charges.</p>
</div>
</div>
<div class="sectionbody">
<div class="imageblock">
<div class="content">
-<img src="easymega-v1.0-top.jpg" alt="easymega v1.0 top" width="430">
+<img src="easymega-v1.0-top.jpg" alt="easymega v1.0 top" width="400">
</div>
<div class="title">Figure 7. EasyMega Board</div>
</div>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Top 5</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Main<br></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Main pyro channel common connection to battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Main +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Main pyro channel common connection to battery +</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Top 6</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Top 7</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee<br></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee pyro channel common connection to battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee pyro channel common connection to battery +</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Top 8</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Top 9</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">D<br></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">D pyro channel common connection to battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">D +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">D pyro channel common connection to battery +</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Bottom 1</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Bottom 5</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">A<br></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">A pyro channel common connection to battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">A +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">A pyro channel common connection to battery +</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Bottom 6</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Bottom 7</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">B<br></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">B pyro channel common connection to battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">B +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">B pyro channel common connection to battery +</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Bottom 8</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Bottom 9</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">C<br></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">C pyro channel common connection to battery<br></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">C +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">C pyro channel common connection to battery +</p></td>
</tr>
</tbody>
</table>
<p>EasyMega 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
+(Bottom 2). Then hook the negative pyro battery terminal to
+ground (Bottom 1) and the switched positive pyro battery to
+the pyro battery input (Bottom 2). Note that you must include
+a switch between the pyro battery and the board for safety,
+as the on-board power switch circuit only supports the primary
+battery! You can then use the existing pyro screw
terminals to hook up all of the pyro charges.</p>
</div>
</div>
</div>
</div>
<div class="sect1">
-<h2 id="_installation">9. Installation</h2>
+<h2 id="_easytimer">9. EasyTimer</h2>
+<div class="sectionbody">
+<div class="imageblock">
+<div class="content">
+<img src="easytimer.jpg" alt="easytimer" width="400">
+</div>
+<div class="title">Figure 8. EasyTimer Board</div>
+</div>
+<div class="paragraph">
+<p>EasyTimer is built on a 0.8 inch by 1½ inch circuit board. It’s
+designed to fit in a 24mm coupler tube.</p>
+</div>
+<div class="paragraph">
+<p>EasyTimer is designed to control events during ascent. It has
+an accelerometer and gyroscope that can measure acceleration
+and rotation and compute speed and tilt angle. EasyTimer has
+two pyro channels which can be configured to fire at various
+points during flight. Because EasyTimer has no barometric
+sensor, it cannot be used to fire recovery charges at apogee
+or during descent. EasyTimer is configured using the AltosUI
+application which is available for Linux, Mac OS X and Windows.</p>
+</div>
+<div class="sect2">
+<h3 id="_easytimer_screw_terminals">9.1. EasyTimer Screw Terminals</h3>
+<div class="paragraph">
+<p>EasyTimer has two sets of four screw terminals near
+one end of the board. Using the picture above, the top
+four have connections for pyro channel B and an
+external battery and the bottom four have connections
+for pyro circuit A and the power switch. Counting from
+the left, the connections are as follows:</p>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<caption class="title">Table 9. EasyTimer Screw Terminals</caption>
+<colgroup>
+<col style="width: 13.3333%;">
+<col style="width: 20%;">
+<col style="width: 66.6667%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Terminal #</th>
+<th class="tableblock halign-left valign-top">Terminal Name</th>
+<th class="tableblock halign-left valign-top">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Top 1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">B -</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Pyro channel B connection to pyro circuit</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Top 2</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">B +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Pyro channel B common connection to battery +</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Top 3</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Battery +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Positive external battery terminal</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Top 4</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Battery -</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Negative external battery terminal</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Bottom 1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">A -</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Pyro channel A connection to pyro circuit</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Bottom 2</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">A +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Pyro channel A common connection to battery +</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Bottom 3</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Switch Output</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Switch connection to flight computer</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Bottom 4</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Switch Input</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Switch connection to positive battery terminal</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect2">
+<h3 id="_connecting_a_battery_to_easytimer">9.2. Connecting A Battery To EasyTimer</h3>
+<div class="paragraph">
+<p>There are two possible battery connections on
+EasyTimer. You can use either method; both feed
+through the power switch terminals.</p>
+</div>
+<div class="paragraph">
+<p>One battery connection is the standard Altus Metrum
+white JST plug. This mates with single-cell Lithium
+Polymer batteries sold by Altus Metrum.</p>
+</div>
+<div class="paragraph">
+<p>The other is a pair of screw terminals marked 'Battery
++' and 'Battery -'. Connect a battery from 4 to 12
+volts to these terminals, being careful to match polarity.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_charging_lithium_batteries_2">9.3. Charging Lithium Batteries</h3>
+<div class="paragraph">
+<p>Because EasyTimer allows for batteries other than the
+standard Altus Metrum Lithium Polymer cells, it cannot
+incorporate a battery charger circuit. Therefore, when
+using a Litium Polymer cell, you’ll need an external
+charger. These are available from Altus Metrum, or
+from Spark Fun.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_using_a_separate_pyro_battery_with_easytimer">9.4. Using a Separate Pyro Battery with EasyTimer</h3>
+<div class="paragraph">
+<p>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.</p>
+</div>
+<div class="paragraph">
+<p>To connect the negative pyro battery terminal to EasyTimer
+ground, connect it to the negative external battery
+connection, top terminal 4.</p>
+</div>
+<div class="paragraph">
+<p>Connecting the switched positive battery terminal to the pyro
+charges must be done separate from EasyTimer, by soldering
+them together or using some other connector. Note that for
+safety, you must put a switch between the pyro battery and
+the rest of the circuit!</p>
+</div>
+<div class="paragraph">
+<p>The other lead from each pyro charge is then inserted into
+the appropriate per-pyro channel screw terminal (top
+terminal 1 for pyro channel A charge, bottom terminal 1 for
+pyro channel B charge).</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_using_an_active_switch_with_easytimer">9.5. Using an Active Switch with EasyTimer</h3>
+<div class="paragraph">
+<p>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.</p>
+</div>
+<div class="paragraph">
+<p>The positive battery terminal is available on bottom
+terminal 4, the positive flight computer input is on the
+bottom terminal 3.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_installation">10. Installation</h2>
<div class="sectionbody">
<div class="paragraph">
<p>A typical installation involves attaching
</div>
</div>
<div class="sect1">
-<h2 id="_using_altus_metrum_products">10. Using Altus Metrum Products</h2>
+<h2 id="_using_altus_metrum_products">11. Using Altus Metrum Products</h2>
<div class="sectionbody">
<div class="sect2">
-<h3 id="_being_legal">10.1. Being Legal</h3>
+<h3 id="_being_legal">11.1. Being Legal</h3>
<div class="paragraph">
<p>In the US, you need an
<a href="http://www.altusmetrum.org/Radio/">amateur radio license</a>
</div>
</div>
<div class="sect2">
-<h3 id="_in_the_rocket">10.2. In the Rocket</h3>
+<h3 id="_in_the_rocket">11.2. In the Rocket</h3>
<div class="paragraph">
<p>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, TeleMega
-or EasyMega for hours.
+alkaline battery, and will run a TeleMetrum, TeleMega,
+EasyMega or EasyTimer for hours.
A 110mAh battery weighs less
than a triple A battery and is a good choice for use
with
</div>
</div>
<div class="sect2">
-<h3 id="_on_the_ground">10.3. On the Ground</h3>
+<h3 id="_on_the_ground">11.3. On the Ground</h3>
<div class="paragraph">
<p>To receive the data stream from the rocket, you need
an antenna and short feed-line connected to one of our
</div>
</div>
<div class="sect2">
-<h3 id="_data_analysis">10.4. Data Analysis</h3>
+<h3 id="_data_analysis">11.4. Data Analysis</h3>
<div class="paragraph">
<p>Our software makes it easy to log the data from each
flight, both the telemetry received during the flight
</div>
</div>
<div class="sect2">
-<h3 id="_future_plans">10.5. Future Plans</h3>
+<h3 id="_future_plans">11.5. Future Plans</h3>
<div class="paragraph">
<p>We have designed and prototyped several “companion
boards” that can attach to the companion connector on
</div>
</div>
<div class="sect1">
-<h2 id="_altosui">11. AltosUI</h2>
+<h2 id="_altosui">12. AltosUI</h2>
<div class="sectionbody">
<div class="imageblock">
<div class="content">
<img src="altosui.png" alt="altosui" width="450">
</div>
-<div class="title">Figure 8. AltosUI Main Window</div>
+<div class="title">Figure 9. AltosUI Main Window</div>
</div>
<div class="paragraph">
<p>The AltosUI program provides a graphical user interface for
the tasks provided from the top-level toolbar.</p>
</div>
<div class="sect2">
-<h3 id="_monitor_flight">11.1. Monitor Flight</h3>
+<h3 id="_monitor_flight">12.1. Monitor Flight</h3>
<div class="paragraph">
<p>Selecting this item brings up a dialog box listing all
of the connected TeleDongle devices. When you choose
<div class="content">
<img src="device-selection.png" alt="device selection" width="300">
</div>
-<div class="title">Figure 9. Device Selection Dialog</div>
+<div class="title">Figure 10. Device Selection Dialog</div>
</div>
<div class="paragraph">
<p>All telemetry data received are automatically recorded
spreadsheet-like format.</p>
</div>
<div class="sect3">
-<h4 id="_launch_pad">11.1.1. Launch Pad</h4>
+<h4 id="_launch_pad">12.1.1. Launch Pad</h4>
<div class="imageblock">
<div class="content">
<img src="launch-pad.png" alt="launch pad" width="400">
</div>
-<div class="title">Figure 10. Monitor Flight Launch Pad View</div>
+<div class="title">Figure 11. Monitor Flight Launch Pad View</div>
</div>
<div class="paragraph">
<p>The 'Launch Pad' tab shows information used to decide when the
</div>
</div>
<div class="sect3">
-<h4 id="_ascent">11.1.2. Ascent</h4>
+<h4 id="_ascent">12.1.2. Ascent</h4>
<div class="imageblock">
<div class="content">
<img src="ascent.png" alt="ascent" width="400">
</div>
-<div class="title">Figure 11. Monitor Flight Ascent View</div>
+<div class="title">Figure 12. Monitor Flight Ascent View</div>
</div>
<div class="paragraph">
<p>This tab is shown during Boost, Fast and Coast
</div>
</div>
<div class="sect3">
-<h4 id="_descent">11.1.3. Descent</h4>
+<h4 id="_descent">12.1.3. Descent</h4>
<div class="imageblock">
<div class="content">
<img src="descent.png" alt="descent" width="400">
</div>
-<div class="title">Figure 12. Monitor Flight Descent View</div>
+<div class="title">Figure 13. Monitor Flight Descent View</div>
</div>
<div class="paragraph">
<p>Once the rocket has reached apogee and (we hope)
</div>
</div>
<div class="sect3">
-<h4 id="_landed">11.1.4. Landed</h4>
+<h4 id="_landed">12.1.4. Landed</h4>
<div class="imageblock">
<div class="content">
<img src="landed.png" alt="landed" width="400">
</div>
-<div class="title">Figure 13. Monitor Flight Landed View</div>
+<div class="title">Figure 14. Monitor Flight Landed View</div>
</div>
<div class="paragraph">
<p>Once the rocket is on the ground, attention switches
</div>
</div>
<div class="sect3">
-<h4 id="_table">11.1.5. Table</h4>
+<h4 id="_table">12.1.5. Table</h4>
<div class="imageblock">
<div class="content">
<img src="table.png" alt="table" width="400">
</div>
-<div class="title">Figure 14. Monitor Flight Table View</div>
+<div class="title">Figure 15. Monitor Flight Table View</div>
</div>
<div class="paragraph">
<p>The table view shows all of the data available from the
</div>
</div>
<div class="sect3">
-<h4 id="_site_map">11.1.6. Site Map</h4>
+<h4 id="_site_map">12.1.6. Site Map</h4>
<div class="imageblock">
<div class="content">
<img src="site-map.png" alt="site map" width="400">
</div>
-<div class="title">Figure 15. Monitor Flight Site Map View</div>
+<div class="title">Figure 16. Monitor Flight Site Map View</div>
</div>
<div class="paragraph">
<p>When the TeleMetrum has a GPS fix, the Site Map tab
</div>
</div>
<div class="sect3">
-<h4 id="_igniter">11.1.7. Igniter</h4>
+<h4 id="_igniter">12.1.7. Igniter</h4>
<div class="imageblock">
<div class="content">
<img src="ignitor.png" alt="ignitor" width="400">
</div>
-<div class="title">Figure 16. Monitor Flight Additional Igniter View</div>
+<div class="title">Figure 17. Monitor Flight Additional Igniter View</div>
</div>
<div class="paragraph">
<p>TeleMega includes four additional programmable pyro
</div>
</div>
<div class="sect2">
-<h3 id="_save_flight_data">11.2. Save Flight Data</h3>
+<h3 id="_save_flight_data">12.2. Save Flight Data</h3>
<div class="paragraph">
<p>The altimeter records flight data to its internal
flash memory.
</div>
</div>
<div class="sect2">
-<h3 id="_replay_flight">11.3. Replay Flight</h3>
+<h3 id="_replay_flight">12.3. Replay Flight</h3>
<div class="paragraph">
<p>Select this button and you are prompted to select a flight
record file, either a .telem file recording telemetry data or a
</div>
</div>
<div class="sect2">
-<h3 id="_graph_data">11.4. Graph Data</h3>
+<h3 id="_graph_data">12.4. Graph Data</h3>
<div class="paragraph">
<p>Select this button and you are prompted to select a flight
record file, either a .telem file recording telemetry data or a
opened.</p>
</div>
<div class="sect3">
-<h4 id="_flight_graph">11.4.1. Flight Graph</h4>
+<h4 id="_flight_graph">12.4.1. Flight Graph</h4>
<div class="imageblock">
<div class="content">
<img src="graph.png" alt="graph" width="400">
</div>
-<div class="title">Figure 17. Flight Data Graph</div>
+<div class="title">Figure 18. Flight Data Graph</div>
</div>
<div class="paragraph">
<p>By default, the graph contains acceleration (blue),
</div>
</div>
<div class="sect3">
-<h4 id="_configure_graph">11.4.2. Configure Graph</h4>
+<h4 id="_configure_graph">12.4.2. Configure Graph</h4>
<div class="imageblock">
<div class="content">
<img src="graph-configure.png" alt="graph configure" width="400">
</div>
-<div class="title">Figure 18. Flight Graph Configuration</div>
+<div class="title">Figure 19. Flight Graph Configuration</div>
</div>
<div class="paragraph">
<p>This selects which graph elements to show, and, at the
</div>
</div>
<div class="sect3">
-<h4 id="_flight_statistics">11.4.3. Flight Statistics</h4>
+<h4 id="_flight_statistics">12.4.3. Flight Statistics</h4>
<div class="imageblock">
<div class="content">
<img src="graph-stats.png" alt="graph stats" width="400">
</div>
-<div class="title">Figure 19. Flight Statistics</div>
+<div class="title">Figure 20. Flight Statistics</div>
</div>
<div class="paragraph">
<p>Shows overall data computed from the flight.</p>
</div>
</div>
<div class="sect3">
-<h4 id="_map">11.4.4. Map</h4>
+<h4 id="_map">12.4.4. Map</h4>
<div class="imageblock">
<div class="content">
<img src="graph-map.png" alt="graph map" width="400">
</div>
-<div class="title">Figure 20. Flight Map</div>
+<div class="title">Figure 21. Flight Map</div>
</div>
<div class="paragraph">
-<p>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.</p>
+<p>Shows a satellite image of the flight area
+overlaid with the path of the flight. The
+flight path will have different colored
+sections for each state of the flight (just
+like the Site Map in Monitor Flight mode):
+white for pad, red for boost, pink for fast,
+yellow for coast, light blue for drogue, dark
+blue for main, and black for landed.</p>
+</div>
+<div class="paragraph">
+<p>The red concentric circles mark the launch
+pad, the black concentric circles mark the
+landing location. Data for the point along the
+along the flight path nearest the cursor will
+be displayed at the bottom of the window. This
+data includes flight time (so you can
+correlate data in the graph window), latitude,
+longitude, height above ground and vertical
+speed. The selected point will be highlighted
+with concentric circles in the same color as
+the flight path at that point.</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_export_data">11.5. Export Data</h3>
+<h3 id="_export_data">12.5. Export Data</h3>
<div class="paragraph">
<p>This tool takes the raw data files and makes them
available for external analysis. When you select this
file formats.</p>
</div>
<div class="sect3">
-<h4 id="_comma_separated_value_format">11.5.1. Comma Separated Value Format</h4>
+<h4 id="_comma_separated_value_format">12.5.1. Comma Separated Value Format</h4>
<div class="paragraph">
<p>This is a text file containing the data in a form
suitable for import into a spreadsheet or other
</div>
</div>
<div class="sect3">
-<h4 id="_keyhole_markup_language_for_google_earth">11.5.2. Keyhole Markup Language (for Google Earth)</h4>
+<h4 id="_keyhole_markup_language_for_google_earth">12.5.2. Keyhole Markup Language (for Google Earth)</h4>
<div class="paragraph">
<p>This is the format used by Google Earth to provide an
overlay within that application. With this, you can
</div>
</div>
<div class="sect2">
-<h3 id="_configure_altimeter">11.6. Configure Altimeter</h3>
+<h3 id="_configure_altimeter">12.6. Configure Altimeter</h3>
<div class="imageblock">
<div class="content">
<img src="configure-altimeter.png" alt="configure altimeter" width="350">
</div>
-<div class="title">Figure 21. Altimeter Configuration</div>
+<div class="title">Figure 22. Altimeter Configuration</div>
</div>
<div class="paragraph">
<p>Select this button and then select either an altimeter or
<p>The rest of the dialog contains the parameters to be configured.</p>
</div>
<div class="sect3">
-<h4 id="_main_deploy_altitude">11.6.1. Main Deploy Altitude</h4>
+<h4 id="_main_deploy_altitude">12.6.1. Main Deploy Altitude</h4>
<div class="paragraph">
<p>This sets the altitude (above the recorded pad
altitude) at which the 'main' igniter will fire. The
</div>
</div>
<div class="sect3">
-<h4 id="_apogee_delay">11.6.2. Apogee Delay</h4>
+<h4 id="_apogee_delay">12.6.2. Apogee Delay</h4>
<div class="paragraph">
<p>When flying redundant electronics, it’s often
important to ensure that multiple apogee charges don’t
</div>
</div>
<div class="sect3">
-<h4 id="_apogee_lockout">11.6.3. Apogee Lockout</h4>
+<h4 id="_apogee_lockout">12.6.3. Apogee Lockout</h4>
<div class="paragraph">
<p>Apogee lockout is the number of seconds after launch
where the flight computer will not fire the apogee
</div>
</div>
<div class="sect3">
-<h4 id="_frequency">11.6.4. Frequency</h4>
+<h4 id="_frequency">12.6.4. Frequency</h4>
<div class="paragraph">
<p>This configures which of the frequencies to use for
both telemetry and packet command mode. Note that if
</div>
</div>
<div class="sect3">
-<h4 id="_rf_calibration">11.6.5. RF Calibration</h4>
+<h4 id="_rf_calibration">12.6.5. RF Calibration</h4>
<div class="paragraph">
<p>The radios in every Altus Metrum device are calibrated
at the factory to ensure that they transmit and
</div>
</div>
<div class="sect3">
-<h4 id="_telemetryrdfaprs_enable">11.6.6. Telemetry/RDF/APRS Enable</h4>
+<h4 id="_telemetryrdfaprs_enable">12.6.6. Telemetry/RDF/APRS Enable</h4>
<div class="paragraph">
<p>Enables the radio for transmission during
flight. When disabled, the radio will not
</div>
</div>
<div class="sect3">
-<h4 id="_telemetry_baud_rate">11.6.7. Telemetry baud rate</h4>
+<h4 id="_telemetry_baud_rate">12.6.7. Telemetry baud rate</h4>
<div class="paragraph">
<p>This sets the modulation bit rate for data
transmission for both telemetry and packet
</div>
</div>
<div class="sect3">
-<h4 id="_aprs_interval">11.6.8. APRS Interval</h4>
+<h4 id="_aprs_interval">12.6.8. APRS Interval</h4>
<div class="paragraph">
<p>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
+available on TeleMetrum v2 or newer and TeleMega
boards. TeleMetrum v1 boards cannot transmit
APRS packets.
Note that a single APRS packet
</div>
</div>
<div class="sect3">
-<h4 id="_aprs_ssid">11.6.9. APRS SSID</h4>
+<h4 id="_aprs_ssid">12.6.9. APRS SSID</h4>
<div class="paragraph">
<p>Which SSID to report in APRS packets. By
default, this is set to the last digit of the
</div>
</div>
<div class="sect3">
-<h4 id="_aprs_format">11.6.10. APRS Format</h4>
+<h4 id="_aprs_format">12.6.10. APRS Format</h4>
<div class="paragraph">
<p>Whether to send APRS data in Compressed or
Uncompressed format. Compressed format is
</div>
</div>
<div class="sect3">
-<h4 id="_callsign">11.6.11. Callsign</h4>
+<h4 id="_aprs_offset">12.6.11. APRS Offset</h4>
+<div class="paragraph">
+<p>The delay from the top of the minute before sending
+the first APRS packet of the minute. Coordinating
+values for this parameter between multiple devices can
+allow a single receiver to reliably receive APRS
+packets from multiple devices. Note that this offset only
+takes effect while the GPS signal is locked so that the
+transmitting device knows the current time.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_callsign">12.6.12. Callsign</h4>
<div class="paragraph">
<p>This sets the call sign included in each
telemetry packet. Set this as needed to
</div>
</div>
<div class="sect3">
-<h4 id="_maximum_flight_log_size">11.6.12. Maximum Flight Log Size</h4>
+<h4 id="_maximum_flight_log_size">12.6.13. Maximum Flight Log Size</h4>
<div class="paragraph">
<p>This sets the space (in kilobytes) allocated
for each flight log. The available space will
</div>
</div>
<div class="sect3">
-<h4 id="_ignitor_firing_mode">11.6.13. Ignitor Firing Mode</h4>
+<h4 id="_ignitor_firing_mode">12.6.14. Ignitor Firing Mode</h4>
<div class="paragraph">
<p>This configuration parameter allows the two standard ignitor
channels (Apogee and Main) to be used in different
is fired first, followed after a two second
delay by the 'main' channel.</p>
</dd>
+<dt class="hdlist1">Separation & Apogee</dt>
+<dd>
+<p>This fires the 'main' channel when the first motor
+burns out and fires the 'apogee' charge at apogee.</p>
+</dd>
</dl>
</div>
</div>
<div class="sect3">
-<h4 id="_pad_orientation">11.6.14. Pad Orientation</h4>
+<h4 id="_pad_orientation">12.6.15. Pad Orientation</h4>
<div class="paragraph">
<p>Because they include accelerometers,
TeleMetrum, TeleMega and EasyMega are
<dl>
<dt class="hdlist1">Antenna Up</dt>
<dd>
-<p>In this mode, the antenna end of the flight
-computer must point forward, in line with the
-expected flight path.</p>
+<p>In this mode, the antenna (or beeper, for devices
+without an antenna) of the flight computer must point
+forward, in line with the expected flight path.</p>
</dd>
<dt class="hdlist1">Antenna Down</dt>
<dd>
-<p>In this mode, the antenna end of the flight
-computer must point aft, in line with the
-expected flight path.</p>
+<p>In this mode, the antenna (or beeper, for devices
+without an antenna) end of the flight computer must
+point aft, in line with the expected flight path.</p>
</dd>
</dl>
</div>
</div>
<div class="sect3">
-<h4 id="_beeper_frequency">11.6.15. Beeper Frequency</h4>
+<h4 id="_beeper_frequency">12.6.16. Beeper Frequency</h4>
<div class="paragraph">
<p>The beeper on all Altus Metrum flight
computers works best at 4000Hz, however if you
</div>
</div>
<div class="sect3">
-<h4 id="_logging_trigger_motion">11.6.16. Logging Trigger Motion</h4>
+<h4 id="_logging_trigger_motion">12.6.17. Logging Trigger Motion</h4>
<div class="paragraph">
<p>This sets the amount of motion that TeleGPS
needs to see before logging the new
</div>
</div>
<div class="sect3">
-<h4 id="_position_reporting_interval">11.6.17. Position Reporting Interval</h4>
+<h4 id="_position_reporting_interval">12.6.18. Position Reporting Interval</h4>
<div class="paragraph">
<p>The interval between TeleGPS position reports,
both over the air and in the log. Increase
</div>
</div>
<div class="sect3">
-<h4 id="_calibrate_accelerometer">11.6.18. Calibrate Accelerometer</h4>
+<h4 id="_calibrate_accelerometer">12.6.19. Calibrate Accelerometer</h4>
<div class="paragraph">
<p>This opens a separate window to recalibrate the
accelerometers. Follow the instructions, orienting the
</div>
</div>
<div class="sect3">
-<h4 id="_configure_pyro_channels">11.6.19. Configure Pyro Channels</h4>
+<h4 id="_configure_pyro_channels">12.6.20. Configure Pyro Channels</h4>
<div class="imageblock">
<div class="content">
<img src="configure-pyro.png" alt="configure pyro" width="400">
</div>
-<div class="title">Figure 22. Additional Pyro Channel Configuration</div>
+<div class="title">Figure 23. Additional Pyro Channel Configuration</div>
</div>
<div class="paragraph">
<p>This opens a separate window to configure the
-additional pyro channels available on TeleMega
-and EasyMega. One column is presented for
+additional pyro channels available on TeleMega,
+EasyMega and EasyTimer. One column is presented for
each channel. Each row represents a single
parameter, if enabled the parameter must meet
the specified test for the pyro channel to be
<dt class="hdlist1">Height above pad</dt>
<dd>
<p>Select a value, and then choose whether the height
-above the launch pad should be above or below that value.</p>
+above the launch pad should be above or below that value. Note that
+because EasyTimer has only a low-range accelerometer and no barometer,
+this value will not be very reliable on that device.</p>
</dd>
<dt class="hdlist1">Orientation</dt>
<dd>
-<p>TeleMega and EasyMega contain a 3-axis gyroscope and
-accelerometer which is used to compute the orientation of the
-rocket. A record of orientations over the last 0.64 seconds is kept
-and the largest value within this period is compared with the
+<p>TeleMega, EasyMega and EasyTimer contain a 3-axis
+gyroscope and accelerometer which is used to compute the orientation
+of the rocket. A record of orientations over the last 0.64 seconds is
+kept and the largest value within this period is compared with the
specified value. Note that the tilt angle is not the change in angle
from the launch pad, but rather absolute relative to gravity—the
3-axis accelerometer is used to compute the angle of the rocket on the
acceleration will be less than zero.</p>
</li>
<li>
-<p>Drogue. The rocket has reached apogee and
-is heading back down, but is above the
-configured Main altitude. Ascent rate will be less than zero during
-this state. Vertical acceleration will be negative until the rocket
-reaches a terminal descent rate, at which point Vertical
-acceleration will be zero. Both Ascent rate and Vertical
+<p>Drogue. The rocket has reached apogee and is heading back down, but
+is above the configured Main altitude. Ascent rate will be less
+than zero during this state. Vertical acceleration will be negative
+until the rocket reaches a terminal descent rate, at which point
+Vertical acceleration will be zero. Both Ascent rate and Vertical
acceleration are very noisy in this state, so be careful when
-trying to use them to control pyro channels.</p>
+trying to use them to control pyro channels. This state selection
+is not available on EasyTimer.</p>
</li>
<li>
<p>Main. The rocket is still descending, and
it will settle down to a zero value once the rocket has reached the
terminal velocity under the main chute. Ascent rate and Vertical
acceleration should be much less noisy once the main chute has
-deployed.</p>
+deployed. This state selection is not available on EasyTimer.</p>
</li>
<li>
<p>Landed. The rocket is no longer moving.</p>
</div>
</div>
<div class="sect2">
-<h3 id="_configure_altosui">11.7. Configure AltosUI</h3>
+<h3 id="_configure_altosui">12.7. Configure AltosUI</h3>
<div class="imageblock">
<div class="content">
<img src="configure-altosui.png" alt="configure altosui" width="230">
</div>
-<div class="title">Figure 23. Configure AltosUI Dialog</div>
+<div class="title">Figure 24. Configure AltosUI Dialog</div>
</div>
<div class="paragraph">
<p>This button presents a dialog so that you can
configure the AltosUI global settings.</p>
</div>
<div class="sect3">
-<h4 id="_voice_settings">11.7.1. Voice Settings</h4>
+<h4 id="_voice_settings">12.7.1. Voice Settings</h4>
<div class="paragraph">
<p>AltosUI provides voice announcements during
flight so that you can keep your eyes on the
</div>
</div>
<div class="sect3">
-<h4 id="_log_directory">11.7.2. Log Directory</h4>
+<h4 id="_log_directory">12.7.2. Log Directory</h4>
<div class="paragraph">
<p>AltosUI logs all telemetry data and saves all
flash data to this directory. This
</div>
</div>
<div class="sect3">
-<h4 id="_callsign_2">11.7.3. Callsign</h4>
+<h4 id="_callsign_2">12.7.3. Callsign</h4>
<div class="paragraph">
<p>This value is transmitted in each command
packet sent from TeleDongle and received from
</div>
</div>
<div class="sect3">
-<h4 id="_imperial_units">11.7.4. Imperial Units</h4>
+<h4 id="_imperial_units">12.7.4. Imperial Units</h4>
<div class="paragraph">
<p>This switches between metric units (meters)
and imperial units (feet and miles). This
</div>
</div>
<div class="sect3">
-<h4 id="_serial_debug">11.7.5. Serial Debug</h4>
+<h4 id="_serial_debug">12.7.5. Serial Debug</h4>
<div class="paragraph">
<p>This causes all communication with a connected
device to be dumped to the console from which
</div>
</div>
<div class="sect3">
-<h4 id="_font_size">11.7.6. Font size</h4>
+<h4 id="_font_size">12.7.6. Font size</h4>
<div class="paragraph">
<p>Selects the set of fonts used in the flight
monitor window. Choose between the small,
</div>
</div>
<div class="sect3">
-<h4 id="_look_feel">11.7.7. Look & feel</h4>
+<h4 id="_look_feel">12.7.7. Look & feel</h4>
<div class="paragraph">
<p>Switches between the available Java user
interface appearances. The default selection
</div>
</div>
<div class="sect3">
-<h4 id="_menu_position">11.7.8. Menu position</h4>
+<h4 id="_menu_position">12.7.8. Menu position</h4>
<div class="paragraph">
<p>Selects the initial position for the main
AltosUI window that includes all of the
</div>
</div>
<div class="sect3">
-<h4 id="_map_cache_size">11.7.9. Map Cache Size</h4>
+<h4 id="_map_cache_size">12.7.9. Map Cache Size</h4>
<div class="paragraph">
<p>Sets the number of map 'tiles' kept in memory
while the application is running. More tiles
</div>
</div>
<div class="sect3">
-<h4 id="_manage_frequencies">11.7.10. Manage Frequencies</h4>
+<h4 id="_manage_frequencies">12.7.10. Manage Frequencies</h4>
<div class="paragraph">
<p>This brings up a dialog where you can
configure the set of frequencies shown in the
</div>
</div>
<div class="sect2">
-<h3 id="_configure_groundstation">11.8. Configure Groundstation</h3>
+<h3 id="_configure_groundstation">12.8. Configure Groundstation</h3>
<div class="imageblock">
<div class="content">
<img src="configure-groundstation.png" alt="configure groundstation" width="300">
</div>
-<div class="title">Figure 24. Configure Groundstation Dialog</div>
+<div class="title">Figure 25. Configure Groundstation Dialog</div>
</div>
<div class="paragraph">
<p>Select this button and then select a TeleDongle or
to be configured.</p>
</div>
<div class="sect3">
-<h4 id="_frequency_2">11.8.1. Frequency</h4>
+<h4 id="_frequency_2">12.8.1. Frequency</h4>
<div class="paragraph">
<p>This configures the frequency to use for both
telemetry and packet command mode. Set this
</div>
</div>
<div class="sect3">
-<h4 id="_rf_calibration_2">11.8.2. RF Calibration</h4>
+<h4 id="_rf_calibration_2">12.8.2. RF Calibration</h4>
<div class="paragraph">
<p>The radios in every Altus Metrum device are
calibrated at the factory to ensure that they
</div>
</div>
<div class="sect3">
-<h4 id="_telemetry_rate">11.8.3. Telemetry Rate</h4>
+<h4 id="_telemetry_rate">12.8.3. Telemetry Rate</h4>
<div class="paragraph">
<p>This lets you match the telemetry and packet
link rate from the transmitter. If they don’t
</div>
</div>
<div class="sect2">
-<h3 id="_flash_image">11.9. Flash Image</h3>
+<h3 id="_flash_image">12.9. Flash Image</h3>
<div class="paragraph">
<p>This reprograms Altus Metrum devices with new
firmware.
and TeleBT v1.0 are all reprogrammed by using another
similar unit as a programming dongle (pair
programming).
-TeleMega, EasyMega, TeleMetrum v2,
-EasyMini and TeleDongle v3 are all
+TeleMega, EasyMega, TeleMetrum v2 or newer,
+EasyMini, EasyTimer, TeleBT v3 or newer and TeleDongle v3
+or newer are all
programmed directly
over USB (self programming). Please read
the directions for flashing devices in
</div>
</div>
<div class="sect2">
-<h3 id="_fire_igniter">11.10. Fire Igniter</h3>
+<h3 id="_fire_igniter">12.10. Fire Igniter</h3>
<div class="imageblock">
<div class="content">
<img src="fire-igniter.png" alt="fire igniter" width="120">
</div>
-<div class="title">Figure 25. Fire Igniter Window</div>
+<div class="title">Figure 26. Fire Igniter Window</div>
</div>
<div class="paragraph">
<p>This activates the igniter circuits in the flight
</div>
</div>
<div class="sect2">
-<h3 id="_scan_channels">11.11. Scan Channels</h3>
+<h3 id="_scan_channels">12.11. Scan Channels</h3>
<div class="imageblock">
<div class="content">
<img src="scan-channels.png" alt="scan channels" width="300">
</div>
-<div class="title">Figure 26. Scan Channels Window</div>
+<div class="title">Figure 27. Scan Channels Window</div>
</div>
<div class="paragraph">
<p>This listens for telemetry packets on all of the
</div>
</div>
<div class="sect2">
-<h3 id="_load_maps">11.12. Load Maps</h3>
+<h3 id="_load_maps">12.12. Load Maps</h3>
<div class="imageblock">
<div class="content">
<img src="load-maps.png" alt="load maps" width="500">
</div>
-<div class="title">Figure 27. Load Maps Window</div>
+<div class="title">Figure 28. Load Maps Window</div>
</div>
<div class="paragraph">
<p>Before heading out to a new launch site, you can use
</div>
</div>
<div class="sect2">
-<h3 id="_monitor_idle">11.13. Monitor Idle</h3>
+<h3 id="_monitor_idle">12.13. Monitor Idle</h3>
<div class="imageblock">
<div class="content">
<img src="monitor-idle.png" alt="monitor idle" width="500">
</div>
-<div class="title">Figure 28. Monitor Idle Window</div>
+<div class="title">Figure 29. Monitor Idle Window</div>
</div>
<div class="paragraph">
<p>This brings up a dialog similar to the Monitor Flight
</div>
</div>
<div class="sect1">
-<h2 id="_altosdroid">12. AltosDroid</h2>
+<h2 id="_altosdroid">13. AltosDroid</h2>
<div class="sectionbody">
<div class="paragraph">
<p>AltosDroid provides the same flight monitoring capabilities as
interface and describe what the displayed data means.</p>
</div>
<div class="sect2">
-<h3 id="_installing_altosdroid">12.1. Installing AltosDroid</h3>
+<h3 id="_installing_altosdroid">13.1. Installing AltosDroid</h3>
<div class="paragraph">
<p>AltosDroid is available from the Google Play store. To
install it on your Android device, open the Google
</div>
</div>
<div class="sect2">
-<h3 id="_charging_telebt_battery">12.2. Charging TeleBT Battery</h3>
+<h3 id="_charging_telebt_battery">13.2. Charging TeleBT Battery</h3>
<div class="paragraph">
<p>Before using TeleBT with AltosDroid, make sure the
internal TeleBT battery is charged. To do this,
</div>
</div>
<div class="sect2">
-<h3 id="_connecting_to_telebt_over_bluetooth">12.3. Connecting to TeleBT over Bluetooth™</h3>
+<h3 id="_connecting_to_telebt_over_bluetooth">13.3. Connecting to TeleBT over Bluetooth™</h3>
<div class="paragraph">
<p>Press the Android 'Menu' button or soft-key to see the
configuration options available. Select the 'Connect a
</div>
</div>
<div class="sect2">
-<h3 id="_connecting_to_teledongle_or_telebt_over_usb">12.4. Connecting to TeleDongle or TeleBT over USB</h3>
+<h3 id="_connecting_to_teledongle_or_telebt_over_usb">13.4. Connecting to TeleDongle or TeleBT over USB</h3>
<div class="paragraph">
<p>Get a special USB On-the-go adapter cable. These
cables have a USB micro-B male connector on one end
</div>
</div>
<div class="sect2">
-<h3 id="_altosdroid_menu">12.5. AltosDroid Menu</h3>
+<h3 id="_altosdroid_menu">13.5. AltosDroid Menu</h3>
<div class="paragraph">
<p>The main AltosDroid menu has a selection of operation
and configuration options.</p>
</div>
</div>
<div class="sect2">
-<h3 id="_setup">12.6. Setup</h3>
+<h3 id="_setup">13.6. Setup</h3>
<div class="dlist">
<dl>
<dt class="hdlist1">Telemetry Rate</dt>
</div>
</div>
<div class="sect2">
-<h3 id="_idle_mode">12.7. Idle Mode</h3>
+<h3 id="_idle_mode">13.7. Idle Mode</h3>
<div class="dlist">
<dl>
<dt class="hdlist1">Callsign</dt>
</div>
</div>
<div class="sect2">
-<h3 id="_altosdroid_flight_monitoring">12.8. AltosDroid Flight Monitoring</h3>
+<h3 id="_altosdroid_flight_monitoring">13.8. AltosDroid Flight Monitoring</h3>
<div class="paragraph">
<p>AltosDroid is designed to mimic the AltosUI flight
monitoring display, providing separate tabs for each
</div>
</div>
<div class="sect2">
-<h3 id="_pad">12.9. Pad</h3>
+<h3 id="_pad">13.9. Pad</h3>
<div class="paragraph">
<p>The 'Pad' tab shows information used to decide when
the rocket is ready for flight. The first elements
</div>
</div>
<div class="sect2">
-<h3 id="_flight">12.10. Flight</h3>
+<h3 id="_flight">13.10. Flight</h3>
<div class="paragraph">
<p>The 'Flight' tab shows information used to evaluate
and spot a rocket while in flight. It displays speed
</div>
</div>
<div class="sect2">
-<h3 id="_recover">12.11. Recover</h3>
+<h3 id="_recover">13.11. Recover</h3>
<div class="paragraph">
<p>The 'Recover' tab shows information used while
recovering the rocket on the ground after flight.</p>
</div>
</div>
<div class="sect2">
-<h3 id="_map_2">12.12. Map</h3>
+<h3 id="_map_2">13.12. Map</h3>
<div class="paragraph">
<p>The 'Map' tab shows a map of the area around the
rocket being tracked along with information needed to
</div>
</div>
<div class="sect2">
-<h3 id="_downloading_flight_logs">12.13. Downloading Flight Logs</h3>
+<h3 id="_downloading_flight_logs">13.13. Downloading Flight Logs</h3>
<div class="paragraph">
<p>AltosDroid always saves every bit of telemetry data it
receives. To download that to a computer for use with
the firmware operates in is determined at start up
time.
For
-TeleMetrum, TeleMega and EasyMega, which have accelerometers, the mode is
+TeleMetrum, TeleMega, EasyMega and EasyTimer, 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
<div class="sect2">
<h3 id="_aprs">A.6. APRS</h3>
<div class="paragraph">
-<p>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
-battery power or radio channel bandwidth. You can configure
-the APRS interval using AltosUI; that process is described in
-<a href="#_configure_altimeter">Configure Altimeter</a>.</p>
+<p>TeleMetrum v2 and newer 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 battery power or radio channel
+bandwidth. You can configure the time within each
+minute that APRS transmits by changing the APRS offset
+value. When the GPS signal is locked and knows the
+current time, the APRS offset selects the time with
+each minute for the first APRS transmission;
+subsequent transmissions occur each APRS interval
+seconds thereafter. You can configure the APRS
+interval and APRS offset using AltosUI; that
+process is described in <a href="#_configure_altimeter">Configure Altimeter</a>.</p>
</div>
<div class="paragraph">
<p>AltOS supports both compressed and uncompressed APRS
status information as shown in the following table.</p>
</div>
<table class="tableblock frame-all grid-all stretch">
-<caption class="title">Table 9. Altus Metrum APRS Comments</caption>
+<caption class="title">Table 10. Altus Metrum APRS Comments</caption>
<colgroup>
<col style="width: 20%;">
<col style="width: 20%;">
<h2 id="_updating_device_firmware">Appendix C: Updating Device Firmware</h2>
<div class="sectionbody">
<div class="paragraph">
-<p>TeleMega, TeleMetrum v2, EasyMega, EasyMini and TeleDongle v3
+<p>TeleMega, TeleMetrum v2 and newer, EasyMega, EasyMini and TeleDongle v3
are all
programmed directly over their USB connectors (self
programming).
<a href="http://www.altusmetrum.org/AltOS/" class="bare">http://www.altusmetrum.org/AltOS/</a></p>
</div>
<div class="sect2">
-<h3 id="_updating_telemega_telemetrum_v2_easymega_easymini_or_teledongle_v3_firmware">C.1. Updating TeleMega, TeleMetrum v2, EasyMega, EasyMini or TeleDongle v3 Firmware</h3>
+<h3 id="_updating_telemega_telemetrum_v2_or_newer_easymega_easymini_teledongle_v3_or_telebt_v3_firmware">C.1. Updating TeleMega, TeleMetrum v2 or newer, EasyMega, EasyMini, TeleDongle v3 or TeleBT v3 Firmware</h3>
<div class="paragraph">
<p>Self-programmable devices are reprogrammed by
connecting them to your computer over USB.</p>
<dd>
<p>Connect pin 6 and pin 1 of the companion
connector. Pin 1 can be identified by the square pad
-around it, and then the pins could sequentially across
+around it, and then the pins count sequentially across
the board. Be very careful to <strong>not</strong> short pin 8 to
anything as that is connected directly to the
battery. Pin 7 carries 3.3V and the board will crash
<dd>
<p>Connect pin 6 and pin 1 of the companion
connector. Pin 1 can be identified by the square pad
-around it, and then the pins could sequentially across
+around it, and then the pins count sequentially across
the board. Be very careful to <strong>not</strong> short pin 8 to
anything as that is connected directly to the
battery. Pin 7 carries 3.3V and the board will crash
if that is connected to pin 1, but shouldn’t damage
the board.</p>
</dd>
-<dt class="hdlist1">TeleMetrum v2</dt>
+<dt class="hdlist1">EasyTimer</dt>
+<dd>
+<p>Connect pin 5 and pin 1 of the debug connector, which
+is the six holes next to the beeper. Pin 1 can be
+identified by the square pad around it, and then the
+pins count sequentially across the board, making Pin 5
+the one on the other end of the row.</p>
+</dd>
+<dt class="hdlist1">TeleMetrum v2 and newer</dt>
<dd>
<p>Connect pin 6 and pin 1 of the companion
connector. Pin 1 can be identified by the square pad
-around it, and then the pins could sequentially across
+around it, and then the pins count sequentially across
the board. Be very careful to <strong>not</strong> short pin 8 to
anything as that is connected directly to the
battery. Pin 7 carries 3.3V and the board will crash
<p>Connect pin 6 and pin 1 of the debug connector, which
is the six holes next to the beeper. Pin 1 can be
identified by the square pad around it, and then the
-pins could sequentially across the board, making Pin 6
+pins count sequentially across the board, making Pin 6
the one on the other end of the row.</p>
</dd>
+<dt class="hdlist1">TeleGPS v1</dt>
+<dd>
+<p>Connect pin 32 on the CPU to ground. Pin 32 is the
+right-most pin on the bottom edge of the CPU when the
+board is oriented with the USB and battery connectors
+to the right.</p>
+</dd>
+<dt class="hdlist1">TeleGPS v2</dt>
+<dd>
+<p>Connect together pins 1 and 5 of the Debug connector.
+Pin 1 is the pin with the square pad around the hole.</p>
+</dd>
<dt class="hdlist1">TeleDongle v3</dt>
<dd>
<p>Connect pin 32 on the CPU to ground. Pin 32 is closest
of the board. Ground is available on the capacitor
next to it, on the end towards the USB wires.</p>
</dd>
+<dt class="hdlist1">TeleBT v3</dt>
+<dd>
+<p>Connect pin 4 on the CPU to 3.3V, which can be done by
+connecting pin 1 to pin 4. Pin 1 is the left pin on
+the lower edge of the chip when the unit is oriented
+such that the SMA is at the top.</p>
+</dd>
<dt class="hdlist1">TeleBT v4</dt>
<dd>
<p>Connect pin 30 on the CPU to ground. Pin 30 is the 6th
several equal-sized blocks, one for each flight.</p>
</div>
<table class="tableblock frame-all grid-all stretch">
-<caption class="title">Table 10. Data Storage on Altus Metrum altimeters</caption>
+<caption class="title">Table 11. Data Storage on Altus Metrum altimeters</caption>
<colgroup>
<col style="width: 25%;">
<col style="width: 25%;">
<td class="tableblock halign-left valign-top"><p class="tableblock">80</p></td>
</tr>
<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">TeleMetrum v3.0</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">16</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">8MB</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">80</p></td>
+</tr>
+<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">TeleMini v1.0</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">2</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">5kB</p></td>
for storing flight log data.</p>
</div>
<div class="paragraph">
-<p>TeleMetrum v2.0, TeleMega and EasyMega
+<p>TeleMetrum v2 or newer, TeleMega and EasyMega
store configuration data in a bit of eeprom available within
the processor chip, leaving that space available in flash for
more flight data.</p>
seconds) by 10 times the bytes per sample and add the two
together. That will slightly under-estimate the storage (in
bytes) needed for the flight.
-For instance, a TeleMetrum v2.0 flight spending
+For instance, a TeleMetrum v2 or newer flight spending
20 seconds in ascent and 150 seconds in descent will take
about (20 * 1600) + (150 * 160) = 56000 bytes of storage. You
could store dozens of these flights in the on-board flash.</p>
production and retired.</p>
</div>
<table class="tableblock frame-all grid-all stretch">
-<caption class="title">Table 11. Altus Metrum Flight Computer Electronics</caption>
+<caption class="title">Table 12. Altus Metrum Flight Computer Electronics</caption>
<colgroup>
<col style="width: 12.5%;">
<col style="width: 12.5%;">
<td class="tableblock halign-left valign-top"><p class="tableblock">3.7V</p></td>
</tr>
<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">TeleMetrum v3.0</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">MS5607 30km (100k')</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ADXL375 200g</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">uBlox Max-8Q</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">-</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">8MB</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">40mW</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">3.7V</p></td>
+</tr>
+<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">TeleMini v1.0</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">MP3H6115 10km (33k')</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">-</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">3.7V</p></td>
</tr>
<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">TeleMega v4.0</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">MS5607 30km (100k')</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">ADXL375 200g</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">uBlox Max-8Q</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">BMX160</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">8MB</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">40mW</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">3.7V</p></td>
+</tr>
+<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">EasyMega v1.0</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">MS5607 30km (100k')</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">MMA6555 102g</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">-</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">3.7V</p></td>
</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">EasyTimer v1.0</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">-</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">16g</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">-</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">BMX160</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">-</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">-</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">3.7-12V</p></td>
+</tr>
</tbody>
</table>
<div style="page-break-after: always;"></div>
<table class="tableblock frame-all grid-all stretch">
-<caption class="title">Table 12. Altus Metrum Flight Computer Mechanical Components</caption>
+<caption class="title">Table 13. Altus Metrum Flight Computer Mechanical Components</caption>
<colgroup>
<col style="width: 16.6666%;">
<col style="width: 16.6666%;">
<td class="tableblock halign-left valign-top"><p class="tableblock">2¼ inch (5.62cm)</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">38mm coupler</p></td>
</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">EasyMini</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Debug USB Battery</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Pyro A Pyro B Battery</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">0.8 inch (2.03cm)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">1½ inch (3.81cm)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">24mm coupler</p></td>
+</tr>
</tbody>
</table>
</div>
<h2 id="_release_notes">Appendix F: Release Notes</h2>
<div class="sectionbody">
<div class="sect2">
-<h3 id="_release_notes_for_version_1_9">F.1. Release Notes for Version 1.9</h3>
+<h3 id="_release_notes_for_version_1_9_5">F.1. Release Notes for Version 1.9.5</h3>
<div class="paragraph">
-<p>Version 1.9</p>
+<p>Version 1.9.5</p>
</div>
<div class="sect3">
<h4 id="_altos">F.1.1. AltOS</h4>
<div class="ulist">
<ul>
<li>
+<p>Add Booster mode for all dual-deploy altimeters. Select
+"Separation & Apogee" mode in AltosUI to fire the 'main'
+channel at first motor burnout and the 'apogee' channel at
+apogee.</p>
+</li>
+<li>
+<p>Improve reliability of stm32l firmware under heavy
+load. This was found using Monitor Idle on TeleMega with all
+flash slots full of data which would occasionally lock up.</p>
+</li>
+<li>
+<p>Fix orientation label in AltosUI for devices with
+radios. This makes the orientation say 'Antenna up' and
+'Antenna Down' for TeleMetrum and TeleMega again.</p>
+</li>
+<li>
+<p>Fix log data for pyro channels which were inhibited (often
+because of a tilt limit). They used to report 'fired' as
+soon as they were inhibited, which was misleading. Now they
+never report as having been fired.</p>
+</li>
+<li>
+<p>Allow Igniter Test to fire each igniter more than once.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_2">F.1.2. AltosUI</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Improve performance of Monitor Idle mode by sending less data for each
+update.</p>
+</li>
+<li>
+<p>Improve Mac OS X install scripts so that they work on
+Catalina. This involves sending the user to get Java from
+the AdoptOpenJDK project which provides a version that works
+with Java applications.</p>
+</li>
+<li>
+<p>Make larger dialogs scrollable for use on smaller screens.</p>
+</li>
+<li>
+<p>Fix troubles re-flashing EasyMega boards running older
+firmware.</p>
+</li>
+<li>
+<p>Add TeleMetrum v3.0 firmware to the Windows
+AltosUI packages.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_9_4">F.2. Release Notes for Version 1.9.4</h3>
+<div class="paragraph">
+<p>Version 1.9.4</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_2">F.2.1. AltOS</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Fixed firmware for TeleDongle v3.0 and TeleBT v4.0. Version 1.9.3 bricked those
+devices requiring them to be opened up to get them working again.</p>
+</li>
+<li>
+<p>Fixed firmware for EasyMini v1.0. Changes in the storage
+code caused it to use significantly more RAM which made the
+interrupt stack smash into other data structures and cause
+the device to panic at startup time.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_3">F.2.2. AltosUI</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Add TeleMetrum v3.0 firmware to the Linux and Mac OSX
+AltosUI packages.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_9_3">F.3. Release Notes for Version 1.9.3</h3>
+<div class="paragraph">
+<p>Version 1.9.3</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_3">F.3.1. AltOS</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Add APRS offset. Allows multiple APRS transmitters to coordinate when
+transmission occurs to allow them to share a frequency.</p>
+</li>
+<li>
+<p>Fix max log size. Flight computer storage is erased in 64kB chunks. Adjust max
+log size to be a multiple of this size.</p>
+</li>
+<li>
+<p>Check flight erasing more carefully. Handle interrupting erasing in the
+middle.</p>
+</li>
+<li>
+<p>Add EasyTimer support.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_telegps_micropeak">F.3.2. AltosUI, TeleGPS, MicroPeak</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Add configuration support for APRS offset.</p>
+</li>
+<li>
+<p>Adjust flight log sizes to be a multiple of the flight
+computer erase block size.</p>
+</li>
+<li>
+<p>Report barometric pad altitude in Pad tab for TeleMini.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_9_2">F.4. Release Notes for Version 1.9.2</h3>
+<div class="paragraph">
+<p>Version 1.9.2</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_4">F.4.1. AltOS</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Add support for TeleMega v4.0</p>
+</li>
+<li>
+<p>Fix time wrapping issue with TeleLCO and TeleFire</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_telegps_micropeak_2">F.4.2. AltosUI, TeleGPS, MicroPeak</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Add column in AltosUI for IMU data from TeleMega and EasyMega</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosdroid_2">F.4.3. AltosDroid</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Allow sorting of trackers by call, serial, frequency or age</p>
+</li>
+<li>
+<p>Offer selection of font sizes</p>
+</li>
+<li>
+<p>Various bug fixes for older Android versions</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_9_1">F.5. Release Notes for Version 1.9.1</h3>
+<div class="paragraph">
+<p>Version 1.9.1</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_5">F.5.1. AltOS</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Add support for TeleMetrum v3.0</p>
+</li>
+<li>
+<p>Fix accel cal value when changing EasyMega v2.0 pad orientation</p>
+</li>
+<li>
+<p>Correct EasyMega v2.0 magnetometer data axes</p>
+</li>
+<li>
+<p>Fix EasyMega v2.0 idle monitor display of IMU data</p>
+</li>
+<li>
+<p>Report all sensor failures at power-up time.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_telegps_micropeak_3">F.5.2. AltosUI, TeleGPS, MicroPeak</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Display error message when attempting to graph unknown format file.</p>
+</li>
+<li>
+<p>Make it possible to disable APRS once enabled.</p>
+</li>
+<li>
+<p>Display some data for point near cursor in map tab.</p>
+</li>
+<li>
+<p>Support upgrading devices from pre-1.8 firmware</p>
+</li>
+<li>
+<p>Wait for Windows to prepare new devices during firmware
+upgrade. This should avoid the “COMxx: open failed” message.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_9">F.6. Release Notes for Version 1.9</h3>
+<div class="paragraph">
+<p>Version 1.9</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_6">F.6.1. AltOS</h4>
+<div class="ulist">
+<ul>
+<li>
<p>Add support for EasyMega v2.0</p>
</li>
<li>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_telegps_micropeak">F.1.2. AltosUI, TeleGPS, MicroPeak</h4>
+<h4 id="_altosui_telegps_micropeak_4">F.6.2. AltosUI, TeleGPS, MicroPeak</h4>
<div class="ulist">
<ul>
<li>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_8_7">F.2. Release Notes for Version 1.8.7</h3>
+<h3 id="_release_notes_for_version_1_8_7">F.7. Release Notes for Version 1.8.7</h3>
<div class="paragraph">
<p>Version 1.8.7</p>
</div>
<div class="sect3">
-<h4 id="_altos_2">F.2.1. AltOS</h4>
+<h4 id="_altos_7">F.7.1. AltOS</h4>
<div class="ulist">
<ul>
<li>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_telegps_micropeak_2">F.2.2. AltosUI, TeleGPS, MicroPeak</h4>
+<h4 id="_altosui_telegps_micropeak_5">F.7.2. AltosUI, TeleGPS, MicroPeak</h4>
<div class="ulist">
<ul>
<li>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_8_6">F.3. Release Notes for Version 1.8.6</h3>
+<h3 id="_release_notes_for_version_1_8_6">F.8. Release Notes for Version 1.8.6</h3>
<div class="paragraph">
<p>Version 1.8.6</p>
</div>
<div class="sect3">
-<h4 id="_altos_3">F.3.1. AltOS</h4>
+<h4 id="_altos_8">F.8.1. AltOS</h4>
<div class="ulist">
<ul>
<li>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_telegps">F.3.2. AltosUI, TeleGPS</h4>
+<h4 id="_altosui_telegps">F.8.2. AltosUI, TeleGPS</h4>
<div class="ulist">
<ul>
<li>
</div>
</div>
<div class="sect3">
-<h4 id="_micropeak">F.3.3. MicroPeak</h4>
+<h4 id="_micropeak">F.8.3. MicroPeak</h4>
<div class="ulist">
<ul>
<li>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_8_5">F.4. Release Notes for Version 1.8.5</h3>
+<h3 id="_release_notes_for_version_1_8_5">F.9. Release Notes for Version 1.8.5</h3>
<div class="paragraph">
<p>Version 1.8.5 includes fixes to the ground software support
for TeleBT v4, along with a few other minor updates.</p>
</div>
<div class="sect3">
-<h4 id="_altos_4">F.4.1. AltOS</h4>
+<h4 id="_altos_9">F.9.1. AltOS</h4>
<div class="ulist">
<ul>
<li>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_telegps_2">F.4.2. AltosUI, TeleGPS</h4>
+<h4 id="_altosui_telegps_2">F.9.2. AltosUI, TeleGPS</h4>
<div class="ulist">
<ul>
<li>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_8_4">F.5. Release Notes for Version 1.8.4</h3>
+<h3 id="_release_notes_for_version_1_8_4">F.10. Release Notes for Version 1.8.4</h3>
<div class="paragraph">
<p>Version 1.8.4 includes support for EasyMini version 2.0</p>
</div>
<div class="sect3">
-<h4 id="_altos_5">F.5.1. AltOS</h4>
+<h4 id="_altos_10">F.10.1. AltOS</h4>
<div class="ulist">
<ul>
<li>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_8_3">F.6. Release Notes for Version 1.8.3</h3>
+<h3 id="_release_notes_for_version_1_8_3">F.11. Release Notes for Version 1.8.3</h3>
<div class="paragraph">
<p>Version 1.8.3 includes support for TeleMega version 3.0 along
with two important flight computer fixes. This version also
downloading.</p>
</div>
<div class="sect3">
-<h4 id="_altos_6">F.6.1. AltOS</h4>
+<h4 id="_altos_11">F.11.1. AltOS</h4>
<div class="sect4">
<h5 id="_altos_new_features">AltOS New Features</h5>
<div class="ulist">
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_and_telegps_applications">F.6.2. AltosUI and TeleGPS Applications</h4>
+<h4 id="_altosui_and_telegps_applications">F.11.2. AltosUI and TeleGPS Applications</h4>
<div class="sect4">
<h5 id="_altosui_new_features">AltosUI New Features</h5>
<div class="ulist">
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_8_2">F.7. Release Notes for Version 1.8.2</h3>
+<h3 id="_release_notes_for_version_1_8_2">F.12. Release Notes for Version 1.8.2</h3>
<div class="paragraph">
<p>Version 1.8.2 includes support for TeleGPS version 2.0 along
with accelerometer recalibration support in AltosUI.</p>
analyzing saved data files.</p>
</div>
<div class="sect3">
-<h4 id="_altos_7">F.7.1. AltOS</h4>
+<h4 id="_altos_12">F.12.1. AltOS</h4>
<div class="paragraph">
<p>AltOS New Features</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_and_telegps_applications_2">F.7.2. AltosUI and TeleGPS Applications</h4>
+<h4 id="_altosui_and_telegps_applications_2">F.12.2. AltosUI and TeleGPS Applications</h4>
<div class="paragraph">
<p>AltosUI and TeleGPS New Features</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_8_1">F.8. Release Notes for Version 1.8.1</h3>
+<h3 id="_release_notes_for_version_1_8_1">F.13. Release Notes for Version 1.8.1</h3>
<div class="paragraph">
<p>Version 1.8.1 includes an important bug fix for Apogee Lockout
operation in all flight computers. Anyone using this option
analyzing saved data files.</p>
</div>
<div class="sect3">
-<h4 id="_altos_8">F.8.1. AltOS</h4>
+<h4 id="_altos_13">F.13.1. AltOS</h4>
<div class="paragraph">
<p>AltOS Bug Fixes</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_and_telegps_applications_3">F.8.2. AltosUI and TeleGPS Applications</h4>
+<h4 id="_altosui_and_telegps_applications_3">F.13.2. AltosUI and TeleGPS Applications</h4>
<div class="paragraph">
<p>AltosUI New Features</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_8">F.9. Release Notes for Version 1.8</h3>
+<h3 id="_release_notes_for_version_1_8">F.14. Release Notes for Version 1.8</h3>
<div class="paragraph">
<p>Version 1.8 includes support for our new TeleBT v4.0 ground
station, updates for data analysis in our ground station
boards and ground station interfaces.</p>
</div>
<div class="sect3">
-<h4 id="_altos_9">F.9.1. AltOS</h4>
+<h4 id="_altos_14">F.14.1. AltOS</h4>
<div class="paragraph">
<p>AltOS New Features</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_and_telegps_applications_4">F.9.2. AltosUI and TeleGPS Applications</h4>
+<h4 id="_altosui_and_telegps_applications_4">F.14.2. AltosUI and TeleGPS Applications</h4>
<div class="paragraph">
<p>AltosUI New Features</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_7">F.10. Release Notes for Version 1.7</h3>
+<h3 id="_release_notes_for_version_1_7">F.15. Release Notes for Version 1.7</h3>
<div class="paragraph">
<p>Version 1.7 includes support for our new TeleMini v3.0
flight computer and bug fixes in in the flight software for all our boards
and ground station interfaces.</p>
</div>
<div class="sect3">
-<h4 id="_altos_10">F.10.1. AltOS</h4>
+<h4 id="_altos_15">F.15.1. AltOS</h4>
<div class="paragraph">
<p>AltOS New Features</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_and_telegps_applications_5">F.10.2. AltosUI and TeleGPS Applications</h4>
+<h4 id="_altosui_and_telegps_applications_5">F.15.2. AltosUI and TeleGPS Applications</h4>
<div class="paragraph">
<p>AltosUI New Features</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_6_8">F.11. Release Notes for Version 1.6.8</h3>
+<h3 id="_release_notes_for_version_1_6_8">F.16. Release Notes for Version 1.6.8</h3>
<div class="paragraph">
<p>Version 1.6.8 fixes a TeleMega and TeleMetrum v2.0 bug where
the device could stop logging data and transmitting
v2.0 users should update their flight firmware.</p>
</div>
<div class="sect3">
-<h4 id="_altos_11">F.11.1. AltOS</h4>
+<h4 id="_altos_16">F.16.1. AltOS</h4>
<div class="paragraph">
<p>AltOS fixes:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_telegps_and_altosdroid_applications">F.11.2. AltosUI, TeleGPS and AltosDroid Applications</h4>
+<h4 id="_altosui_telegps_and_altosdroid_applications">F.16.2. AltosUI, TeleGPS and AltosDroid Applications</h4>
<div class="paragraph">
<p>AltosUI fixes:</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_6_5">F.12. Release Notes for Version 1.6.5</h3>
+<h3 id="_release_notes_for_version_1_6_5">F.17. Release Notes for Version 1.6.5</h3>
<div class="paragraph">
<p>Version 1.6.5 fixes a TeleMega and TeleMetrum v2.0 bug where
the device would often stop logging data and transmitting
v2.0 users should update their flight firmware.</p>
</div>
<div class="sect3">
-<h4 id="_altos_12">F.12.1. AltOS</h4>
+<h4 id="_altos_17">F.17.1. AltOS</h4>
<div class="paragraph">
<p>AltOS fixes:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_telegps_and_altosdroid_applications_2">F.12.2. AltosUI, TeleGPS and AltosDroid Applications</h4>
+<h4 id="_altosui_telegps_and_altosdroid_applications_2">F.17.2. AltosUI, TeleGPS and AltosDroid Applications</h4>
<div class="paragraph">
<p>AltosUI fixes:</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_6_4">F.13. Release Notes for Version 1.6.4</h3>
+<h3 id="_release_notes_for_version_1_6_4">F.18. Release Notes for Version 1.6.4</h3>
<div class="paragraph">
<p>Version 1.6.4 fixes a bluetooth communication problem with
TeleBT v1.0 devices, along with some altosui and altosdroid
minor nits. It also now ships firmware for some newer devices.</p>
</div>
<div class="sect3">
-<h4 id="_altos_13">F.13.1. AltOS</h4>
+<h4 id="_altos_18">F.18.1. AltOS</h4>
<div class="paragraph">
<p>AltOS fixes:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_telegps_and_altosdroid_applications_3">F.13.2. AltosUI, TeleGPS and AltosDroid Applications</h4>
+<h4 id="_altosui_telegps_and_altosdroid_applications_3">F.18.2. AltosUI, TeleGPS and AltosDroid Applications</h4>
<div class="paragraph">
<p>AltosUI, TeleGPS and AltosDroid New Features:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_documentation">F.13.3. Documentation</h4>
+<h4 id="_documentation">F.18.3. Documentation</h4>
<div class="ulist">
<ul>
<li>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_6_3">F.14. Release Notes for Version 1.6.3</h3>
+<h3 id="_release_notes_for_version_1_6_3">F.19. Release Notes for Version 1.6.3</h3>
<div class="paragraph">
<p>Version 1.6.3 adds idle mode to AltosDroid and has bug fixes
for our host software on desktops, laptops an android devices
along with BlueTooth support for Windows.</p>
</div>
<div class="sect3">
-<h4 id="_altos_14">F.14.1. AltOS</h4>
+<h4 id="_altos_19">F.19.1. AltOS</h4>
<div class="paragraph">
<p>AltOS fixes:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_and_telegps_applications_6">F.14.2. AltosUI and TeleGPS Applications</h4>
+<h4 id="_altosui_and_telegps_applications_6">F.19.2. AltosUI and TeleGPS Applications</h4>
<div class="paragraph">
<p>AltosUI and TeleGPS New Features:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosdroid_2">F.14.3. AltosDroid</h4>
+<h4 id="_altosdroid_3">F.19.3. AltosDroid</h4>
<div class="paragraph">
<p>AltosDroid new features:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_documentation_2">F.14.4. Documentation</h4>
+<h4 id="_documentation_2">F.19.4. Documentation</h4>
<div class="ulist">
<ul>
<li>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_6_2">F.15. Release Notes for Version 1.6.2</h3>
+<h3 id="_release_notes_for_version_1_6_2">F.20. Release Notes for Version 1.6.2</h3>
<div class="paragraph">
<p>Version 1.6.2 includes support for our updated TeleMega v2.0
product and bug fixes in in the flight software for all our boards
and ground station interfaces.</p>
</div>
<div class="sect3">
-<h4 id="_altos_15">F.15.1. AltOS</h4>
+<h4 id="_altos_20">F.20.1. AltOS</h4>
<div class="paragraph">
<p>AltOS New Features:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_and_telegps_applications_7">F.15.2. AltosUI and TeleGPS Applications</h4>
+<h4 id="_altosui_and_telegps_applications_7">F.20.2. AltosUI and TeleGPS Applications</h4>
<div class="paragraph">
<p>AltosUI and TeleGPS Fixes:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_documentation_3">F.15.3. Documentation</h4>
+<h4 id="_documentation_3">F.20.3. Documentation</h4>
<div class="paragraph">
<p>We spent a bunch of time trying to improve our documentation</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_6_1">F.16. Release Notes for Version 1.6.1</h3>
+<h3 id="_release_notes_for_version_1_6_1">F.21. Release Notes for Version 1.6.1</h3>
<div class="paragraph">
<p>Version 1.6.1 includes support for our updated TeleBT v3.0
product and bug fixes in in the flight software for all our boards
and ground station interfaces.</p>
</div>
<div class="sect3">
-<h4 id="_altos_16">F.16.1. AltOS</h4>
+<h4 id="_altos_21">F.21.1. AltOS</h4>
<div class="paragraph">
<p>AltOS New Features:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_and_telegps_applications_8">F.16.2. AltosUI and TeleGPS Applications</h4>
+<h4 id="_altosui_and_telegps_applications_8">F.21.2. AltosUI and TeleGPS Applications</h4>
<div class="paragraph">
<p>AltosUI and TeleGPS New Features:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosdroid_3">F.16.3. AltosDroid</h4>
+<h4 id="_altosdroid_4">F.21.3. AltosDroid</h4>
<div class="paragraph">
<p>AltosDroid New Features:</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_6">F.17. Release Notes for Version 1.6</h3>
+<h3 id="_release_notes_for_version_1_6">F.22. Release Notes for Version 1.6</h3>
<div class="paragraph">
<p>Version 1.6 includes support for our updated TeleDongle v3.0
product and bug fixes in in the flight software for all our boards
and ground station interfaces.</p>
</div>
<div class="sect3">
-<h4 id="_altos_17">F.17.1. AltOS</h4>
+<h4 id="_altos_22">F.22.1. AltOS</h4>
<div class="paragraph">
<p>AltOS New Features</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_and_telegps_applications_9">F.17.2. AltosUI and TeleGPS Applications</h4>
+<h4 id="_altosui_and_telegps_applications_9">F.22.2. AltosUI and TeleGPS Applications</h4>
<div class="paragraph">
<p>AltosUI and TeleGPS New Features</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_5">F.18. Release Notes for Version 1.5</h3>
+<h3 id="_release_notes_for_version_1_5">F.23. Release Notes for Version 1.5</h3>
<div class="paragraph">
<p>Version 1.5 is a major release. It includes support for our new
EasyMega product, new features and bug fixes in in the flight
software for all our boards and the AltosUI ground station</p>
</div>
<div class="sect3">
-<h4 id="_altos_18">F.18.1. AltOS</h4>
+<h4 id="_altos_23">F.23.1. AltOS</h4>
<div class="paragraph">
<p>AltOS New Features</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_and_telegps_applications_10">F.18.2. AltosUI and TeleGPS Applications</h4>
+<h4 id="_altosui_and_telegps_applications_10">F.23.2. AltosUI and TeleGPS Applications</h4>
<div class="paragraph">
<p>AltosUI and TeleGPS New Features</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_4_2">F.19. Release Notes for Version 1.4.2</h3>
+<h3 id="_release_notes_for_version_1_4_2">F.24. Release Notes for Version 1.4.2</h3>
<div class="paragraph">
<p>Version 1.4.2 is a minor release. It fixes Java-related install issues on
Windows</p>
</div>
<div class="sect3">
-<h4 id="_altosui_and_telegps_applications_11">F.19.1. AltosUI and TeleGPS Applications</h4>
+<h4 id="_altosui_and_telegps_applications_11">F.24.1. AltosUI and TeleGPS Applications</h4>
<div class="paragraph">
<p>Windows Install Fixes</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_4_1">F.20. Release Notes for Version 1.4.1</h3>
+<h3 id="_release_notes_for_version_1_4_1">F.25. Release Notes for Version 1.4.1</h3>
<div class="paragraph">
<p>Version 1.4.1 is a minor release. It fixes install issues on
Windows and provides the missing TeleMetrum V2.0 firmware. There
V2.0 firmware image will not need to upgrade.</p>
</div>
<div class="sect3">
-<h4 id="_altosui_and_telegps_applications_12">F.20.1. AltosUI and TeleGPS Applications:</h4>
+<h4 id="_altosui_and_telegps_applications_12">F.25.1. AltosUI and TeleGPS Applications:</h4>
<div class="paragraph">
<p>Windows Install Fixes</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_4">F.21. Release Notes for Version 1.4</h3>
+<h3 id="_release_notes_for_version_1_4">F.26. Release Notes for Version 1.4</h3>
<div class="paragraph">
<p>Version 1.4 is a major release. It includes support for our new
TeleGPS product, new features and bug fixes in in the flight
software for all our boards and the AltosUI ground station</p>
</div>
<div class="sect3">
-<h4 id="_altos_19">F.21.1. AltOS</h4>
+<h4 id="_altos_24">F.26.1. AltOS</h4>
<div class="paragraph">
<p>AltOS new features:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_application">F.21.2. AltosUI Application</h4>
+<h4 id="_altosui_application">F.26.2. AltosUI Application</h4>
<div class="paragraph">
<p>AltosUI new features:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_telegps_application">F.21.3. TeleGPS Application</h4>
+<h4 id="_telegps_application">F.26.3. TeleGPS Application</h4>
<div class="ulist">
<ul>
<li>
</div>
</div>
<div class="sect3">
-<h4 id="_documentation_4">F.21.4. Documentation</h4>
+<h4 id="_documentation_4">F.26.4. Documentation</h4>
<div class="paragraph">
<p>Documentation changes:</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_3_2">F.22. Release Notes for Version 1.3.2</h3>
+<h3 id="_release_notes_for_version_1_3_2">F.27. Release Notes for Version 1.3.2</h3>
<div class="paragraph">
<p>Version 1.3.2 is a minor release. It includes small bug fixes for
the TeleMega flight software and AltosUI ground station</p>
</div>
<div class="sect3">
-<h4 id="_altos_20">F.22.1. AltOS</h4>
+<h4 id="_altos_25">F.27.1. AltOS</h4>
<div class="paragraph">
<p>AltOS fixes:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_application_2">F.22.2. AltosUI Application</h4>
+<h4 id="_altosui_application_2">F.27.2. AltosUI Application</h4>
<div class="paragraph">
<p>AltosUI fixes:</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_3_1">F.23. Release Notes for Version 1.3.1</h3>
+<h3 id="_release_notes_for_version_1_3_1">F.28. Release Notes for Version 1.3.1</h3>
<div class="paragraph">
<p>Version 1.3.1 is a minor release. It improves support for
TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini.</p>
</div>
<div class="sect3">
-<h4 id="_altos_21">F.23.1. AltOS</h4>
+<h4 id="_altos_26">F.28.1. AltOS</h4>
<div class="paragraph">
<p>AltOS new features:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_application_3">F.23.2. AltosUI Application</h4>
+<h4 id="_altosui_application_3">F.28.2. AltosUI Application</h4>
<div class="paragraph">
<p>AltosUI new features:</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_3">F.24. Release Notes for Version 1.3</h3>
+<h3 id="_release_notes_for_version_1_3">F.29. Release Notes for Version 1.3</h3>
<div class="paragraph">
<p>Version 1.3 is a major release. It adds support for TeleMega,
TeleMetrum v2.0, TeleMini v2.0 and EasyMini.</p>
</div>
<div class="sect3">
-<h4 id="_altos_22">F.24.1. AltOS</h4>
+<h4 id="_altos_27">F.29.1. AltOS</h4>
<div class="paragraph">
<p>AltOS new features:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_application_4">F.24.2. AltosUI Application</h4>
+<h4 id="_altosui_application_4">F.29.2. AltosUI Application</h4>
<div class="paragraph">
<p>AltosUI new features:</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_2_1">F.25. Release Notes for Version 1.2.1</h3>
+<h3 id="_release_notes_for_version_1_2_1">F.30. Release Notes for Version 1.2.1</h3>
<div class="paragraph">
<p>Version 1.2.1 is a minor release. It adds support for TeleBT and
the AltosDroid application, provides several new features in
AltosUI and fixes some bugs in the AltOS firmware.</p>
</div>
<div class="sect3">
-<h4 id="_altos_23">F.25.1. AltOS</h4>
+<h4 id="_altos_28">F.30.1. AltOS</h4>
<div class="paragraph">
<p>AltOS new features:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_application_5">F.25.2. AltosUI Application</h4>
+<h4 id="_altosui_application_5">F.30.2. AltosUI Application</h4>
<div class="paragraph">
<p>AltosUI application new features:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosdroid_4">F.25.3. AltosDroid</h4>
+<h4 id="_altosdroid_5">F.30.3. AltosDroid</h4>
<div class="ulist">
<ul>
<li>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_2">F.26. Release Notes for Version 1.2</h3>
+<h3 id="_release_notes_for_version_1_2">F.31. Release Notes for Version 1.2</h3>
<div class="paragraph">
<p>Version 1.2 is a major release. It adds support for MicroPeak
and the MicroPeak USB adapter.</p>
</div>
<div class="sect3">
-<h4 id="_altos_24">F.26.1. AltOS</h4>
+<h4 id="_altos_29">F.31.1. AltOS</h4>
<div class="paragraph">
<p>AltOS New Features:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_and_micropeak_application">F.26.2. AltosUI and MicroPeak Application</h4>
+<h4 id="_altosui_and_micropeak_application">F.31.2. AltosUI and MicroPeak Application</h4>
<div class="paragraph">
<p>New Features:</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_1">F.27. Release Notes for Version 1.1</h3>
+<h3 id="_release_notes_for_version_1_1">F.32. Release Notes for Version 1.1</h3>
<div class="paragraph">
<p>Version 1.1.1 is a bug-fix release. It fixes a couple of bugs
in AltosUI and one firmware bug that affects TeleMetrum
addition of the Ground Distance value in the Descent tab.</p>
</div>
<div class="sect3">
-<h4 id="_altos_25">F.27.1. AltOS</h4>
+<h4 id="_altos_30">F.32.1. AltOS</h4>
<div class="paragraph">
<p>AltOS fixes:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_2">F.27.2. AltosUI</h4>
+<h4 id="_altosui_4">F.32.2. AltosUI</h4>
<div class="paragraph">
<p>AltosUI new features:</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_1_2">F.28. Release Notes for Version 1.1</h3>
+<h3 id="_release_notes_for_version_1_1_2">F.33. Release Notes for Version 1.1</h3>
<div class="paragraph">
<p>Version 1.1 is a minor release. It provides a few new features
in AltosUI and the AltOS firmware and fixes bugs.</p>
</div>
<div class="sect3">
-<h4 id="_altos_26">F.28.1. AltOS</h4>
+<h4 id="_altos_31">F.33.1. AltOS</h4>
<div class="paragraph">
<p>AltOS Firmware New Features:</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_3">F.28.2. AltosUI</h4>
+<h4 id="_altosui_5">F.33.2. AltosUI</h4>
<div class="paragraph">
<p>AltosUI New Features:</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_1_0_1">F.29. Release Notes for Version 1.0.1</h3>
+<h3 id="_release_notes_for_version_1_0_1">F.34. Release Notes for Version 1.0.1</h3>
<div class="paragraph">
<p>Version 1.0.1 is a major release, adding support for the
TeleMini device and lots of new AltosUI features</p>
</div>
<div class="sect3">
-<h4 id="_altos_27">F.29.1. AltOS</h4>
+<h4 id="_altos_32">F.34.1. AltOS</h4>
<div class="paragraph">
<p>AltOS New Features</p>
</div>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_application_6">F.29.2. AltosUI Application</h4>
+<h4 id="_altosui_application_6">F.34.2. AltosUI Application</h4>
<div class="paragraph">
<p>AltosUI New Features</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_0_9_2">F.30. Release Notes for Version 0.9.2</h3>
+<h3 id="_release_notes_for_version_0_9_2">F.35. Release Notes for Version 0.9.2</h3>
<div class="paragraph">
<p>Version 0.9.2 is an AltosUI bug-fix release, with no firmware
changes.</p>
</div>
<div class="sect3">
-<h4 id="_altosui_4">F.30.1. AltosUI</h4>
+<h4 id="_altosui_6">F.35.1. AltosUI</h4>
<div class="paragraph">
<p>AltosUI fixes:</p>
</div>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_0_9">F.31. Release Notes for Version 0.9</h3>
+<h3 id="_release_notes_for_version_0_9">F.36. Release Notes for Version 0.9</h3>
<div class="paragraph">
<p>Version 0.9 adds a few new firmware features and accompanying
AltosUI changes, along with new hardware support.</p>
</div>
<div class="sect3">
-<h4 id="_altos_28">F.31.1. AltOS</h4>
+<h4 id="_altos_33">F.36.1. AltOS</h4>
<div class="ulist">
<ul>
<li>
</div>
</div>
<div class="sect3">
-<h4 id="_altosui_application_7">F.31.2. AltosUI Application</h4>
+<h4 id="_altosui_application_7">F.36.2. AltosUI Application</h4>
<div class="ulist">
<ul>
<li>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_0_8">F.32. Release Notes for Version 0.8</h3>
+<h3 id="_release_notes_for_version_0_8">F.37. Release Notes for Version 0.8</h3>
<div class="paragraph">
<p>Version 0.8 offers a major upgrade in the AltosUI
interface.</p>
</div>
<div class="sect3">
-<h4 id="_altosui_application_8">F.32.1. AltosUI Application:</h4>
+<h4 id="_altosui_application_8">F.37.1. AltosUI Application:</h4>
<div class="ulist">
<ul>
<li>
</div>
</div>
<div class="sect2">
-<h3 id="_release_notes_for_version_0_7_1">F.33. Release Notes for Version 0.7.1</h3>
+<h3 id="_release_notes_for_version_0_7_1">F.38. Release Notes for Version 0.7.1</h3>
<div class="paragraph">
<p>Version 0.7.1 is the first release containing our new
cross-platform Java-based user interface.</p>
</div>
<div class="sect3">
-<h4 id="_altosui_application_9">F.33.1. AltosUI Application</h4>
+<h4 id="_altosui_application_9">F.38.1. AltosUI Application</h4>
<div class="ulist">
<ul>
<li>
</div>
<div id="footer">
<div id="footer-text">
-Version v1.9<br>
-Last updated 2019-01-03 00:31:55 -0700
+Version v1.9.5<br>
+Last updated 2020-09-30 00:31:18 -0600
</div>
</div>
</body>
projects / web / altusmetrum / blobdiff