-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>The Altus Metrum System</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.78.1" /></head><body><div xml:lang="en" class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a id="idm45058136831984"></a>The Altus Metrum System</h1></div><div><h2 class="subtitle">An Owner's Manual for Altus Metrum Rocketry Electronics</h2></div><div><h3 class="corpauthor">
- <span class="inlinemediaobject"><img src="altusmetrum-oneline.svg" width="360" /></span>
-</h3></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Bob</span> <span class="surname">Finch</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Anthony</span> <span class="surname">Towns</span></h3></div></div><div><p class="copyright">Copyright © 2016 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45058136014592"></a><p>
- This document is released under the terms of the
- <a class="ulink" href="http://creativecommons.org/licenses/by-sa/3.0/" target="_top">
- Creative Commons ShareAlike 3.0
- </a>
- license.
- </p></div></div><div><a href="altusmetrum-revhistory.html">Revision History</a></div></div><hr /></div><div class="dedication"><div class="titlepage"><div><div><h1 class="title"><a id="_acknowledgments"></a>Acknowledgments</h1></div></div></div><p>Thanks to Bob Finch, W9YA, NAR 12965, TRA 12350 for writing “The
+<!DOCTYPE html>
+<html lang="en">
+<head>
+<meta charset="UTF-8">
+<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 2.0.16">
+<meta name="author" content="Keith Packard, Bdale Garbee, Bob Finch, Anthony Towns">
+<meta name="copyright" content="Bdale Garbee and Keith Packard 2021">
+<title>The Altus Metrum System: An Owner’s Manual for Altus Metrum Rocketry Electronics</title>
+<link rel="stylesheet" href="./am.css">
+</head>
+<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="author" class="author">Keith Packard</span><br>
+<span id="email" class="email"><a href="mailto:keithp@keithp.com">keithp@keithp.com</a></span><br>
+<span id="author2" class="author">Bdale Garbee</span><br>
+<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.8,</span>
+<span id="revdate">20 Sep 2021</span>
+</div>
+<div id="toc" class="toc">
+<div id="toctitle">Table of Contents</div>
+<ul class="sectlevel1">
+<li><a href="#_license">License</a></li>
+<li><a href="#_acknowledgments">Acknowledgments</a></li>
+<li><a href="#_introduction_and_overview">1. Introduction and Overview</a></li>
+<li><a href="#_getting_started">2. Getting Started</a>
+<ul class="sectlevel2">
+<li><a href="#_batteries">2.1. Batteries</a></li>
+<li><a href="#_ground_station_hardware">2.2. Ground Station Hardware</a></li>
+<li><a href="#_linuxmacwindows_ground_station_software">2.3. Linux/Mac/Windows Ground Station Software</a></li>
+<li><a href="#_android_ground_station_software">2.4. Android Ground Station Software</a></li>
+</ul>
+</li>
+<li><a href="#_using_altus_metrum_hardware">3. Using Altus Metrum Hardware</a>
+<ul class="sectlevel2">
+<li><a href="#_wiring_and_electrical_interference">3.1. Wiring and Electrical Interference</a></li>
+<li><a href="#_hooking_up_lithium_polymer_batteries">3.2. Hooking Up Lithium Polymer Batteries</a></li>
+<li><a href="#_hooking_up_pyro_charges">3.3. Hooking Up Pyro Charges</a></li>
+<li><a href="#_hooking_up_a_power_switch">3.4. Hooking Up a Power Switch</a></li>
+<li><a href="#_understanding_beeps">3.5. Understanding Beeps</a></li>
+<li><a href="#_turning_on_the_power">3.6. Turning On the Power</a></li>
+<li><a href="#_using_an_external_active_switch_circuit">3.7. Using an External Active Switch Circuit</a></li>
+<li><a href="#_using_a_separate_pyro_battery">3.8. Using a Separate Pyro Battery</a></li>
+<li><a href="#_using_a_different_kind_of_battery">3.9. Using a Different Kind of Battery</a></li>
+<li><a href="#_using_packet_link_mode">3.10. Using Packet Link Mode</a></li>
+</ul>
+</li>
+<li><a href="#_telemetrum">4. TeleMetrum</a>
+<ul class="sectlevel2">
+<li><a href="#_telemetrum_screw_terminals">4.1. TeleMetrum Screw Terminals</a></li>
+<li><a href="#_using_a_separate_pyro_battery_with_telemetrum">4.2. Using a Separate Pyro Battery with TeleMetrum</a></li>
+<li><a href="#_using_an_active_switch_with_telemetrum">4.3. Using an Active Switch with TeleMetrum</a></li>
+</ul>
+</li>
+<li><a href="#_telemini">5. TeleMini</a>
+<ul class="sectlevel2">
+<li><a href="#_telemini_v3_screw_terminals">5.1. TeleMini v3 Screw Terminals</a></li>
+<li><a href="#_using_a_separate_pyro_battery_with_telemini_v3">5.2. Using a Separate Pyro Battery with TeleMini v3</a></li>
+<li><a href="#_using_an_active_switch_with_telemini_v3">5.3. Using an Active Switch with TeleMini v3</a></li>
+<li><a href="#_using_packet_link_mode_with_telemini">5.4. Using Packet Link Mode with TeleMini</a></li>
+<li><a href="#_forcing_telemini_radio_parameters_to_known_defaults">5.5. Forcing TeleMini radio parameters to known defaults</a></li>
+<li><a href="#_telemini_v1">5.6. TeleMini v1</a></li>
+</ul>
+</li>
+<li><a href="#_easymini">6. EasyMini</a>
+<ul class="sectlevel2">
+<li><a href="#_easymini_screw_terminals">6.1. EasyMini Screw Terminals</a></li>
+<li><a href="#_connecting_a_battery_to_easymini">6.2. Connecting A Battery To EasyMini</a></li>
+<li><a href="#_charging_lithium_batteries">6.3. Charging Lithium Batteries</a></li>
+<li><a href="#_using_a_separate_pyro_battery_with_easymini">6.4. Using a Separate Pyro Battery with EasyMini</a></li>
+<li><a href="#_using_an_active_switch_with_easymini">6.5. Using an Active Switch with EasyMini</a></li>
+</ul>
+</li>
+<li><a href="#_telemega">7. TeleMega</a>
+<ul class="sectlevel2">
+<li><a href="#_telemega_screw_terminals">7.1. TeleMega Screw Terminals</a></li>
+<li><a href="#_using_a_separate_pyro_battery_with_telemega">7.2. Using a Separate Pyro Battery with TeleMega</a></li>
+<li><a href="#_using_only_one_battery_with_telemega">7.3. Using Only One Battery With TeleMega</a></li>
+<li><a href="#_using_an_active_switch_with_telemega">7.4. Using an Active Switch with TeleMega</a></li>
+</ul>
+</li>
+<li><a href="#_easymega">8. EasyMega</a>
+<ul class="sectlevel2">
+<li><a href="#_easymega_screw_terminals">8.1. EasyMega Screw Terminals</a></li>
+<li><a href="#_using_a_separate_pyro_battery_with_easymega">8.2. Using a Separate Pyro Battery with EasyMega</a></li>
+<li><a href="#_using_only_one_battery_with_easymega">8.3. Using Only One Battery With EasyMega</a></li>
+<li><a href="#_using_an_active_switch_with_easymega">8.4. Using an Active Switch with EasyMega</a></li>
+</ul>
+</li>
+<li><a href="#_easytimer">9. EasyTimer</a>
+<ul class="sectlevel2">
+<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="#_installation">10. Installation</a></li>
+<li><a href="#_using_altus_metrum_products">11. Using Altus Metrum Products</a>
+<ul class="sectlevel2">
+<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="#_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>
+<ul class="sectlevel2">
+<li><a href="#_firmware_modes">A.1. Firmware Modes</a></li>
+<li><a href="#_gps">A.2. GPS</a></li>
+<li><a href="#_controlling_an_altimeter_over_the_radio_link">A.3. Controlling An Altimeter Over The Radio Link</a></li>
+<li><a href="#_ground_testing">A.4. Ground Testing</a></li>
+<li><a href="#_radio_link">A.5. Radio Link</a></li>
+<li><a href="#_aprs">A.6. APRS</a></li>
+<li><a href="#_configurable_parameters">A.7. Configurable Parameters</a></li>
+</ul>
+</li>
+<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_or_newer_telemini_v3_easymega_easymini_teledongle_v3_or_telebt_v3_firmware">C.1. Updating TeleMega, TeleMetrum v2 or newer, TeleMini v3, 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="#_flight_data_recording">Appendix D: Flight Data Recording</a></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_8">F.1. Release Notes for Version 1.9.8</a></li>
+<li><a href="#_release_notes_for_version_1_9_7">F.2. Release Notes for Version 1.9.7</a></li>
+<li><a href="#_release_notes_for_version_1_9_6">F.3. Release Notes for Version 1.9.6</a></li>
+<li><a href="#_release_notes_for_version_1_9_5">F.4. Release Notes for Version 1.9.5</a></li>
+<li><a href="#_release_notes_for_version_1_9_4">F.5. Release Notes for Version 1.9.4</a></li>
+<li><a href="#_release_notes_for_version_1_9_3">F.6. Release Notes for Version 1.9.3</a></li>
+<li><a href="#_release_notes_for_version_1_9_2">F.7. Release Notes for Version 1.9.2</a></li>
+<li><a href="#_release_notes_for_version_1_9_1">F.8. Release Notes for Version 1.9.1</a></li>
+<li><a href="#_release_notes_for_version_1_9">F.9. Release Notes for Version 1.9</a></li>
+<li><a href="#_release_notes_for_version_1_8_7">F.10. Release Notes for Version 1.8.7</a></li>
+<li><a href="#_release_notes_for_version_1_8_6">F.11. Release Notes for Version 1.8.6</a></li>
+<li><a href="#_release_notes_for_version_1_8_5">F.12. Release Notes for Version 1.8.5</a></li>
+<li><a href="#_release_notes_for_version_1_8_4">F.13. Release Notes for Version 1.8.4</a></li>
+<li><a href="#_release_notes_for_version_1_8_3">F.14. Release Notes for Version 1.8.3</a></li>
+<li><a href="#_release_notes_for_version_1_8_2">F.15. Release Notes for Version 1.8.2</a></li>
+<li><a href="#_release_notes_for_version_1_8_1">F.16. Release Notes for Version 1.8.1</a></li>
+<li><a href="#_release_notes_for_version_1_8">F.17. Release Notes for Version 1.8</a></li>
+<li><a href="#_release_notes_for_version_1_7">F.18. Release Notes for Version 1.7</a></li>
+<li><a href="#_release_notes_for_version_1_6_8">F.19. Release Notes for Version 1.6.8</a></li>
+<li><a href="#_release_notes_for_version_1_6_5">F.20. Release Notes for Version 1.6.5</a></li>
+<li><a href="#_release_notes_for_version_1_6_4">F.21. Release Notes for Version 1.6.4</a></li>
+<li><a href="#_release_notes_for_version_1_6_3">F.22. Release Notes for Version 1.6.3</a></li>
+<li><a href="#_release_notes_for_version_1_6_2">F.23. Release Notes for Version 1.6.2</a></li>
+<li><a href="#_release_notes_for_version_1_6_1">F.24. Release Notes for Version 1.6.1</a></li>
+<li><a href="#_release_notes_for_version_1_6">F.25. Release Notes for Version 1.6</a></li>
+<li><a href="#_release_notes_for_version_1_5">F.26. Release Notes for Version 1.5</a></li>
+<li><a href="#_release_notes_for_version_1_4_2">F.27. Release Notes for Version 1.4.2</a></li>
+<li><a href="#_release_notes_for_version_1_4_1">F.28. Release Notes for Version 1.4.1</a></li>
+<li><a href="#_release_notes_for_version_1_4">F.29. Release Notes for Version 1.4</a></li>
+<li><a href="#_release_notes_for_version_1_3_2">F.30. Release Notes for Version 1.3.2</a></li>
+<li><a href="#_release_notes_for_version_1_3_1">F.31. Release Notes for Version 1.3.1</a></li>
+<li><a href="#_release_notes_for_version_1_3">F.32. Release Notes for Version 1.3</a></li>
+<li><a href="#_release_notes_for_version_1_2_1">F.33. Release Notes for Version 1.2.1</a></li>
+<li><a href="#_release_notes_for_version_1_2">F.34. Release Notes for Version 1.2</a></li>
+<li><a href="#_release_notes_for_version_1_1">F.35. Release Notes for Version 1.1</a></li>
+<li><a href="#_release_notes_for_version_1_1_2">F.36. Release Notes for Version 1.1</a></li>
+<li><a href="#_release_notes_for_version_1_0_1">F.37. Release Notes for Version 1.0.1</a></li>
+<li><a href="#_release_notes_for_version_0_9_2">F.38. Release Notes for Version 0.9.2</a></li>
+<li><a href="#_release_notes_for_version_0_9">F.39. Release Notes for Version 0.9</a></li>
+<li><a href="#_release_notes_for_version_0_8">F.40. Release Notes for Version 0.8</a></li>
+<li><a href="#_release_notes_for_version_0_7_1">F.41. Release Notes for Version 0.7.1</a></li>
+</ul>
+</li>
+</ul>
+</div>
+</div>
+<div id="content">
+<div id="preamble">
+<div class="sectionbody">
+<div id="logo" class="imageblock">
+<div class="content">
+<a class="image" href="https://altusmetrum.org"><img src="altusmetrum-oneline.svg" alt="Altus Metrum"></a>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_license">License</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Copyright © 2021 Bdale Garbee and Keith Packard</p>
+</div>
+<div class="paragraph">
+<p>This document is released under the terms of the <a href="http://creativecommons.org/licenses/by-sa/3.0/">Creative Commons ShareAlike 3.0 License</a></p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_acknowledgments">Acknowledgments</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Thanks to Bob Finch, W9YA, NAR 12965, TRA 12350 for writing “The
Mere-Mortals Quick Start/Usage Guide to the Altus Metrum Starter
Kit” which formed the basis of the original Getting Started chapter
in this manual. Bob was one of our first customers for a production
TeleMetrum, and his continued enthusiasm and contributions
-are immensely gratifying and highly appreciated!</p><p>And thanks to Anthony (AJ) Towns for major contributions including
+are immensely gratifying and highly appreciated!</p>
+</div>
+<div class="paragraph">
+<p>And thanks to Anthony (AJ) Towns for major contributions including
the AltosUI graphing and site map code and associated documentation.
Free software means that our customers and friends can become our
collaborators, and we certainly appreciate this level of
-contribution!</p><p>Have fun using these products, and we hope to meet all of you
-out on the rocket flight line somewhere.</p><div class="blockquote"><blockquote class="blockquote"><div class="literallayout"><p>Bdale Garbee, KB0G<br />
-NAR #87103, TRA #12201</p></div></blockquote></div><div class="blockquote"><blockquote class="blockquote"><div class="literallayout"><p>Keith Packard, KD7SQG<br />
-NAR #88757, TRA #12200</p></div></blockquote></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#_introduction_and_overview">1. Introduction and Overview</a></span></dt><dt><span class="chapter"><a href="#_getting_started">2. Getting Started</a></span></dt><dd><dl><dt><span class="section"><a href="#_batteries">2.1. Batteries</a></span></dt><dt><span class="section"><a href="#_ground_station_hardware">2.2. Ground Station Hardware</a></span></dt><dt><span class="section"><a href="#_linux_mac_windows_ground_station_software">2.3. Linux/Mac/Windows Ground Station Software</a></span></dt><dt><span class="section"><a href="#_android_ground_station_software">2.4. Android Ground Station Software</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_using_altus_metrum_hardware">3. Using Altus Metrum Hardware</a></span></dt><dd><dl><dt><span class="section"><a href="#_wiring_and_electrical_interference">3.1. Wiring and Electrical Interference</a></span></dt><dt><span class="section"><a href="#_hooking_up_lithium_polymer_batteries">3.2. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#_hooking_up_pyro_charges">3.3. Hooking Up Pyro Charges</a></span></dt><dt><span class="section"><a href="#_hooking_up_a_power_switch">3.4. Hooking Up a Power Switch</a></span></dt><dt><span class="section"><a href="#_understanding_beeps">3.5. Understanding Beeps</a></span></dt><dt><span class="section"><a href="#_turning_on_the_power">3.6. Turning On the Power</a></span></dt><dt><span class="section"><a href="#_using_an_external_active_switch_circuit">3.7. Using an External Active Switch Circuit</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery">3.8. Using a Separate Pyro Battery</a></span></dt><dt><span class="section"><a href="#_using_a_different_kind_of_battery">3.9. Using a Different Kind of Battery</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_telemetrum">4. TeleMetrum</a></span></dt><dd><dl><dt><span class="section"><a href="#_telemetrum_screw_terminals">4.1. TeleMetrum Screw Terminals</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery_with_telemetrum">4.2. Using a Separate Pyro Battery with TeleMetrum</a></span></dt><dt><span class="section"><a href="#_using_an_active_switch_with_telemetrum">4.3. Using an Active Switch with TeleMetrum</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_telemini_v1_0">5. TeleMini v1.0</a></span></dt><dd><dl><dt><span class="section"><a href="#_telemini_v1_0_screw_terminals">5.1. TeleMini v1.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery_with_telemini_v1_0">5.2. Using a Separate Pyro Battery with TeleMini v1.0</a></span></dt><dt><span class="section"><a href="#_using_an_active_switch_with_telemini_v1_0">5.3. Using an Active Switch with TeleMini v1.0</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_easymini">6. EasyMini</a></span></dt><dd><dl><dt><span class="section"><a href="#_easymini_screw_terminals">6.1. EasyMini Screw Terminals</a></span></dt><dt><span class="section"><a href="#_connecting_a_battery_to_easymini">6.2. Connecting A Battery To EasyMini</a></span></dt><dt><span class="section"><a href="#_charging_lithium_batteries">6.3. Charging Lithium Batteries</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery_with_easymini">6.4. Using a Separate Pyro Battery with EasyMini</a></span></dt><dt><span class="section"><a href="#_using_an_active_switch_with_easymini">6.5. Using an Active Switch with EasyMini</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_telemega">7. TeleMega</a></span></dt><dd><dl><dt><span class="section"><a href="#_telemega_screw_terminals">7.1. TeleMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery_with_telemega">7.2. Using a Separate Pyro Battery with TeleMega</a></span></dt><dt><span class="section"><a href="#_using_only_one_battery_with_telemega">7.3. Using Only One Battery With TeleMega</a></span></dt><dt><span class="section"><a href="#_using_an_active_switch_with_telemega">7.4. Using an Active Switch with TeleMega</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_easymega">8. EasyMega</a></span></dt><dd><dl><dt><span class="section"><a href="#_easymega_screw_terminals">8.1. EasyMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery_with_easymega">8.2. Using a Separate Pyro Battery with EasyMega</a></span></dt><dt><span class="section"><a href="#_using_only_one_battery_with_easymega">8.3. Using Only One Battery With EasyMega</a></span></dt><dt><span class="section"><a href="#_using_an_active_switch_with_easymega">8.4. Using an Active Switch with EasyMega</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_installation">9. Installation</a></span></dt><dt><span class="chapter"><a href="#_using_altus_metrum_products">10. Using Altus Metrum Products</a></span></dt><dd><dl><dt><span class="section"><a href="#_being_legal">10.1. Being Legal</a></span></dt><dt><span class="section"><a href="#_in_the_rocket">10.2. In the Rocket</a></span></dt><dt><span class="section"><a href="#_on_the_ground">10.3. On the Ground</a></span></dt><dt><span class="section"><a href="#_data_analysis">10.4. Data Analysis</a></span></dt><dt><span class="section"><a href="#_future_plans">10.5. Future Plans</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_altosui">11. AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#_monitor_flight">11.1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#_launch_pad">11.1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#_ascent">11.1.2. Ascent</a></span></dt><dt><span class="section"><a href="#_descent">11.1.3. Descent</a></span></dt><dt><span class="section"><a href="#_landed">11.1.4. Landed</a></span></dt><dt><span class="section"><a href="#_table">11.1.5. Table</a></span></dt><dt><span class="section"><a href="#_site_map">11.1.6. Site Map</a></span></dt><dt><span class="section"><a href="#_igniter">11.1.7. Igniter</a></span></dt></dl></dd><dt><span class="section"><a href="#_save_flight_data">11.2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#_replay_flight">11.3. Replay Flight</a></span></dt><dt><span class="section"><a href="#_graph_data">11.4. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#_flight_graph">11.4.1. Flight Graph</a></span></dt><dt><span class="section"><a href="#_configure_graph">11.4.2. Configure Graph</a></span></dt><dt><span class="section"><a href="#_flight_statistics">11.4.3. Flight Statistics</a></span></dt><dt><span class="section"><a href="#_map">11.4.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#_export_data">11.5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#_comma_separated_value_format">11.5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#_keyhole_markup_language_for_google_earth">11.5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#_configure_altimeter">11.6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#_main_deploy_altitude">11.6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#_apogee_delay">11.6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#_apogee_lockout">11.6.3. Apogee Lockout</a></span></dt><dt><span class="section"><a href="#_frequency">11.6.4. Frequency</a></span></dt><dt><span class="section"><a href="#_rf_calibration">11.6.5. RF Calibration</a></span></dt><dt><span class="section"><a href="#_telemetry_rdf_aprs_enable">11.6.6. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#_telemetry_baud_rate">11.6.7. Telemetry baud rate</a></span></dt><dt><span class="section"><a href="#_aprs_interval">11.6.8. APRS Interval</a></span></dt><dt><span class="section"><a href="#_aprs_ssid">11.6.9. APRS SSID</a></span></dt><dt><span class="section"><a href="#_aprs_format">11.6.10. APRS Format</a></span></dt><dt><span class="section"><a href="#_callsign">11.6.11. Callsign</a></span></dt><dt><span class="section"><a href="#_maximum_flight_log_size">11.6.12. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#_ignitor_firing_mode">11.6.13. Ignitor Firing Mode</a></span></dt><dt><span class="section"><a href="#_pad_orientation">11.6.14. Pad Orientation</a></span></dt><dt><span class="section"><a href="#_beeper_frequency">11.6.15. Beeper Frequency</a></span></dt><dt><span class="section"><a href="#_logging_trigger_motion">11.6.16. Logging Trigger Motion</a></span></dt><dt><span class="section"><a href="#_position_reporting_interval">11.6.17. Position Reporting Interval</a></span></dt><dt><span class="section"><a href="#_configure_pyro_channels">11.6.18. Configure Pyro Channels</a></span></dt></dl></dd><dt><span class="section"><a href="#_configure_altosui">11.7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#_voice_settings">11.7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#_log_directory">11.7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#_callsign_2">11.7.3. Callsign</a></span></dt><dt><span class="section"><a href="#_imperial_units">11.7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#_serial_debug">11.7.5. Serial Debug</a></span></dt><dt><span class="section"><a href="#_font_size">11.7.6. Font size</a></span></dt><dt><span class="section"><a href="#_look_amp_feel">11.7.7. Look & feel</a></span></dt><dt><span class="section"><a href="#_menu_position">11.7.8. Menu position</a></span></dt><dt><span class="section"><a href="#_map_cache_size">11.7.9. Map Cache Size</a></span></dt><dt><span class="section"><a href="#_manage_frequencies">11.7.10. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#_configure_groundstation">11.8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#_frequency_2">11.8.1. Frequency</a></span></dt><dt><span class="section"><a href="#_rf_calibration_2">11.8.2. RF Calibration</a></span></dt><dt><span class="section"><a href="#_telemetry_rate">11.8.3. Telemetry Rate</a></span></dt></dl></dd><dt><span class="section"><a href="#_flash_image">11.9. Flash Image</a></span></dt><dt><span class="section"><a href="#_fire_igniter">11.10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#_scan_channels">11.11. Scan Channels</a></span></dt><dt><span class="section"><a href="#_load_maps">11.12. Load Maps</a></span></dt><dt><span class="section"><a href="#_monitor_idle">11.13. Monitor Idle</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_altosdroid">12. AltosDroid</a></span></dt><dd><dl><dt><span class="section"><a href="#_installing_altosdroid">12.1. Installing AltosDroid</a></span></dt><dt><span class="section"><a href="#_charging_telebt_battery">12.2. Charging TeleBT Battery</a></span></dt><dt><span class="section"><a href="#_connecting_to_telebt_over_bluetooth">12.3. Connecting to TeleBT over Bluetooth™</a></span></dt><dt><span class="section"><a href="#_connecting_to_teledongle_or_telebt_over_usb">12.4. Connecting to TeleDongle or TeleBT over USB</a></span></dt><dt><span class="section"><a href="#_configuring_altosdroid">12.5. Configuring AltosDroid</a></span></dt><dt><span class="section"><a href="#_altosdroid_flight_monitoring">12.6. AltosDroid Flight Monitoring</a></span></dt><dt><span class="section"><a href="#_pad">12.7. Pad</a></span></dt><dt><span class="section"><a href="#_flight">12.8. Flight</a></span></dt><dt><span class="section"><a href="#_recover">12.9. Recover</a></span></dt><dt><span class="section"><a href="#_map_2">12.10. Map</a></span></dt><dt><span class="section"><a href="#_downloading_flight_logs">12.11. Downloading Flight Logs</a></span></dt></dl></dd><dt><span class="appendix"><a href="#_system_operation">A. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#_firmware_modes">A.1. Firmware Modes</a></span></dt><dt><span class="section"><a href="#_gps">A.2. GPS</a></span></dt><dt><span class="section"><a href="#_controlling_an_altimeter_over_the_radio_link">A.3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#_ground_testing">A.4. Ground Testing</a></span></dt><dt><span class="section"><a href="#_radio_link">A.5. Radio Link</a></span></dt><dt><span class="section"><a href="#_aprs">A.6. APRS</a></span></dt><dt><span class="section"><a href="#_configurable_parameters">A.7. Configurable Parameters</a></span></dt></dl></dd><dt><span class="appendix"><a href="#_handling_precautions">B. Handling Precautions</a></span></dt><dt><span class="appendix"><a href="#_updating_device_firmware">C. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><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></span></dt><dd><dl><dt><span class="section"><a href="#_recovering_from_self_flashing_failure">C.1.1. Recovering From Self-Flashing Failure</a></span></dt></dl></dd><dt><span class="section"><a href="#_pair_programming">C.2. Pair Programming</a></span></dt><dd><dl><dt><span class="section"><a href="#_updating_telemetrum_v1_x_firmware">C.2.1. Updating TeleMetrum v1.x Firmware</a></span></dt><dt><span class="section"><a href="#_updating_telemini_firmware">C.2.2. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#_updating_teledongle_v0_2_firmware">C.2.3. Updating TeleDongle v0.2 Firmware</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#_flight_data_recording">D. Flight Data Recording</a></span></dt><dt><span class="appendix"><a href="#_altus_metrum_hardware_specifications">E. Altus Metrum Hardware Specifications</a></span></dt><dt><span class="appendix"><a href="#_release_notes">F. Release Notes</a></span></dt><dd><dl><dt><span class="section"><a href="#_release_notes_for_version_1_6_2">F.1. Release Notes for Version 1.6.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos">F.1.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications">F.1.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_documentation">F.1.3. Documentation</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_1">F.2. Release Notes for Version 1.6.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_2">F.2.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_2">F.2.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_altosdroid_2">F.2.3. AltosDroid</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6">F.3. Release Notes for Version 1.6</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_3">F.3.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_3">F.3.2. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_5">F.4. Release Notes for Version 1.5</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_4">F.4.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_4">F.4.2. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_4_2">F.5. Release Notes for Version 1.4.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_and_telegps_applications_5">F.5.1. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_4_1">F.6. Release Notes for Version 1.4.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_and_telegps_applications_6">F.6.1. AltosUI and TeleGPS Applications:</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_4">F.7. Release Notes for Version 1.4</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_5">F.7.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application">F.7.2. AltosUI Application</a></span></dt><dt><span class="section"><a href="#_telegps_application">F.7.3. TeleGPS Application</a></span></dt><dt><span class="section"><a href="#_documentation_2">F.7.4. Documentation</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_3_2">F.8. Release Notes for Version 1.3.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_6">F.8.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_2">F.8.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_3_1">F.9. Release Notes for Version 1.3.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_7">F.9.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_3">F.9.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_3">F.10. Release Notes for Version 1.3</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_8">F.10.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_4">F.10.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_2_1">F.11. Release Notes for Version 1.2.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_9">F.11.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_5">F.11.2. AltosUI Application</a></span></dt><dt><span class="section"><a href="#_altosdroid_3">F.11.3. AltosDroid</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_2">F.12. Release Notes for Version 1.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_10">F.12.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_micropeak_application">F.12.2. AltosUI and MicroPeak Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_1">F.13. Release Notes for Version 1.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_11">F.13.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_2">F.13.2. AltosUI</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_1_2">F.14. Release Notes for Version 1.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_12">F.14.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_3">F.14.2. AltosUI</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_0_1">F.15. Release Notes for Version 1.0.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_13">F.15.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_6">F.15.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_0_9_2">F.16. Release Notes for Version 0.9.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_4">F.16.1. AltosUI</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_0_9">F.17. Release Notes for Version 0.9</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_14">F.17.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_7">F.17.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_0_8">F.18. Release Notes for Version 0.8</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_application_8">F.18.1. AltosUI Application:</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_0_7_1">F.19. Release Notes for Version 0.7.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_application_9">F.19.1. AltosUI Application</a></span></dt></dl></dd></dl></dd></dl></div><div class="list-of-figures"><p><strong>List of Figures</strong></p><dl><dt>4.1. <a href="#idm45058137013184">TeleMetrum v2 Board</a></dt><dt>4.2. <a href="#idm45058131219712">TeleMetrum v1 Board</a></dt><dt>5.1. <a href="#idm45058131173360">TeleMini v1.0 Board</a></dt><dt>6.1. <a href="#idm45058131130096">EasyMini Board</a></dt><dt>7.1. <a href="#idm45058131075552">TeleMega Board</a></dt><dt>8.1. <a href="#idm45058130988752">EasyMega Board</a></dt><dt>11.1. <a href="#idm45058130868928">AltosUI Main Window</a></dt><dt>11.2. <a href="#idm45058130863296">Device Selection Dialog</a></dt><dt>11.3. <a href="#idm45058130849200">Monitor Flight Launch Pad View</a></dt><dt>11.4. <a href="#idm45058130830016">Monitor Flight Ascent View</a></dt><dt>11.5. <a href="#idm45058130823280">Monitor Flight Descent View</a></dt><dt>11.6. <a href="#idm45058130815168">Monitor Flight Landed View</a></dt><dt>11.7. <a href="#idm45058130806592">Monitor Flight Table View</a></dt><dt>11.8. <a href="#idm45058130801760">Monitor Flight Site Map View</a></dt><dt>11.9. <a href="#idm45058130793680">Monitor Flight Additional Igniter View</a></dt><dt>11.10. <a href="#idm45058130777360">Flight Data Graph</a></dt><dt>11.11. <a href="#idm45058130771968">Flight Graph Configuration</a></dt><dt>11.12. <a href="#idm45058130767456">Flight Statistics</a></dt><dt>11.13. <a href="#idm45058130763168">Flight Map</a></dt><dt>11.14. <a href="#idm45058130751680">Altimeter Configuration</a></dt><dt>11.15. <a href="#idm45058130694496">Additional Pyro Channel Configuration</a></dt><dt>11.16. <a href="#idm45058130656608">Configure AltosUI Dialog</a></dt><dt>11.17. <a href="#idm45058130628688">Configure Groundstation Dialog</a></dt><dt>11.18. <a href="#idm45058130608144">Fire Igniter Window</a></dt><dt>11.19. <a href="#idm45058130598992">Scan Channels Window</a></dt><dt>11.20. <a href="#idm45058130594176">Load Maps Window</a></dt><dt>11.21. <a href="#idm45058130577728">Monitor Idle Window</a></dt></dl></div><div class="list-of-tables"><p><strong>List of Tables</strong></p><dl><dt>3.1. <a href="#idm45058131365520">AltOS Modes</a></dt><dt>3.2. <a href="#idm45058131311360">Pad/Idle Indications</a></dt><dt>3.3. <a href="#idm45058131285120">Pad Radio Indications</a></dt><dt>4.1. <a href="#idm45058131209152">TeleMetrum Screw Terminals</a></dt><dt>5.1. <a href="#idm45058131166752">TeleMini v1.0 Screw Terminals</a></dt><dt>6.1. <a href="#idm45058131124080">EasyMini Screw Terminals</a></dt><dt>7.1. <a href="#idm45058131066192">TeleMega Screw Terminals</a></dt><dt>8.1. <a href="#idm45058130983408">EasyMega Screw Terminals</a></dt><dt>A.1. <a href="#idm45058130419360">Altus Metrum APRS Comments</a></dt><dt>D.1. <a href="#idm45058130283472">Data Storage on Altus Metrum altimeters</a></dt><dt>E.1. <a href="#idm45058130237152">Altus Metrum Flight Computer Electronics</a></dt><dt>E.2. <a href="#idm45058130154144">Altus Metrum Flight Computer Mechanical Components</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_introduction_and_overview"></a>Chapter 1. Introduction and Overview</h1></div></div></div><p>Welcome to the Altus Metrum community! Our circuits and software reflect
+contribution!</p>
+</div>
+<div class="paragraph">
+<p>Have fun using these products, and we hope to meet all of you
+out on the rocket flight line somewhere.</p>
+</div>
+<div class="verseblock">
+<pre class="content">Bdale Garbee, KB0G
+NAR #87103, TRA #12201</pre>
+</div>
+<div class="verseblock">
+<pre class="content">Keith Packard, KD7SQG
+NAR #88757, TRA #12200</pre>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_introduction_and_overview">1. Introduction and Overview</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Welcome to the Altus Metrum community! Our circuits and software reflect
our passion for both hobby rocketry and Free Software. We hope their
capabilities and performance will delight you in every way, but by
releasing all of our hardware and software designs under open licenses,
we also hope to empower you to take as active a role in our collective
-future as you wish!</p><p>The first device created for our community was TeleMetrum, a dual
+future as you wish!</p>
+</div>
+<div class="paragraph">
+<p>Our goal is to include in this document all of the information required
+to successfully configure and use Altus Metrum products. But
+documentation is a lot like software in that it can contain "bugs",
+and can probably always be improved! If you have questions that
+aren’t answered in this manual, or just need a little help figuring
+things out, we strongly suggest joining the Altus Metrum user email
+list, which you can do by visiting
+<a href="https://lists.gag.com/mailman/listinfo/altusmetrum" class="bare">https://lists.gag.com/mailman/listinfo/altusmetrum</a>. There’s a lot
+of useful information in the mailing list archives!</p>
+</div>
+<div class="paragraph">
+<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
-improved sensors and radio to offer increased performance.</p><p>Our second device was TeleMini, a dual deploy altimeter 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">
+<p>Our second device was TeleMini, a dual deploy altimeter with
radio telemetry and radio direction finding. The first version
of this device was only 13mm by 38mm (½ inch by 1½ inches) and
-could fit easily in an 18mm air-frame. The latest version, v2.0,
-includes a beeper, USB data download and extended on-board
-flight logging, along with an improved barometric sensor.</p><p>TeleMega is our most sophisticated device, including six pyro
+could fit easily in an 18mm air-frame. The latest version, v3.0,
+includes a beeper, higher power radio, extended on-board
+flight logging and an improved barometric sensor.</p>
+</div>
+<div class="paragraph">
+<p>TeleMega is our most sophisticated device, including six pyro
channels (four of which are fully programmable), integrated GPS,
integrated gyroscopes for staging/air-start inhibit and high
-performance telemetry.</p><p>EasyMini is a dual-deploy altimeter with logging and built-in
-USB data download.</p><p>EasyMega is essentially a TeleMega board with the GPS receiver
+performance telemetry.</p>
+</div>
+<div class="paragraph">
+<p>EasyMini is a dual-deploy altimeter with logging and built-in
+USB data download.</p>
+</div>
+<div class="paragraph">
+<p>EasyMega is essentially a TeleMega board with the GPS receiver
and telemetry transmitter removed. It offers the same 6 pyro
-channels and integrated gyroscopes for staging/air-start inhibit.</p><p>TeleDongle v0.2 was our first ground station, providing a USB to RF
+channels and integrated gyroscopes for staging/air-start inhibit.</p>
+</div>
+<div class="paragraph">
+<p>TeleDongle v0.2 was our first ground station, providing a USB to RF
interfaces for communicating with the altimeters. Combined with
your choice of antenna and notebook computer, TeleDongle and our
associated user interface software form a complete ground
aiding rocket recovery, then processing and archiving flight
data for analysis and review. The latest version, TeleDongle
v3, has all new electronics with a higher performance radio
-for improved range.</p><p>For a slightly more portable ground station experience that also
+for improved range.</p>
+</div>
+<div class="paragraph">
+<p>For a slightly more portable ground station experience that also
provides direct rocket recovery support, TeleBT offers flight
monitoring and data logging using a Bluetooth™ connection between
the receiver and an Android device that has the AltosDroid
-application installed from the Google Play store.</p><p>More products will be added to the Altus Metrum family over time, and
+application installed from the Google Play store.</p>
+</div>
+<div class="paragraph">
+<p>More products will be added to the Altus Metrum family over time, and
we currently envision that this will be a single, comprehensive manual
-for the entire product family.</p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_getting_started"></a>Chapter 2. Getting Started</h1></div></div></div><p>The first thing to do after you open the box is to hook up a
-battery and charge it if necessary.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_batteries"></a>2.1. Batteries</h2></div></div></div><p>For TeleMetrum, TeleMega and EasyMega, the battery can be charged by plugging it into the
+for the entire product family.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_getting_started">2. Getting Started</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The first thing to do after you open the box is to hook up a
+battery and charge it if necessary.</p>
+</div>
+<div class="sect2">
+<h3 id="_batteries">2.1. Batteries</h3>
+<div class="paragraph">
+<p>For TeleMetrum, TeleMega and EasyMega, the battery can be charged by plugging it into the
corresponding socket of the device and then using the USB
-cable to plug the flight computer into your computer’s USB socket. The
+cable to plug the flight computer into your computer’s USB socket. The
on-board circuitry will charge the battery whenever it is plugged
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
-battery charger such as <a class="ulink" href="http://altusmetrum.org/LipoCharger" target="_top">LipoCharger</a>, and
+battery charger such as <a href="http://altusmetrum.org/LipoCharger">LipoCharger</a>, and
connecting that via a USB cable to a laptop or other
-USB power source.</p><p>You can also choose to use another battery with
+USB power source.</p>
+</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
-the battery supplies enough current to fire your chosen e-matches.</p><div class="note" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Note</h3><p>On TeleMetrum v1 boards, when the GPS chip is initially
+the battery supplies enough current to fire your chosen e-matches.</p>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<img src="./images/icons/note.svg" alt="Note">
+</td>
+<td class="content">
+<div class="paragraph">
+<p>On TeleMetrum v1 boards, when the GPS chip is initially
searching for satellites, TeleMetrum will consume more current
than it pulls from the USB port, so the battery must be
attached in order to get satellite lock. Once GPS is locked,
the current consumption goes back down enough to enable charging
-while running. So it’s a good idea to fully charge the battery
+while running. So it’s a good idea to fully charge the battery
as your first item of business so there is no issue getting and
maintaining satellite lock. The yellow charge indicator led
will go out when the battery is nearly full and the charger goes
to trickle charge. It can take several hours to fully recharge a
-deeply discharged battery.</p><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></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_ground_station_hardware"></a>2.2. Ground Station Hardware</h2></div></div></div><p>There are two ground stations available, the TeleDongle USB to
+deeply discharged battery.</p>
+</div>
+<div class="paragraph">
+<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>
+</table>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_ground_station_hardware">2.2. Ground Station Hardware</h3>
+<div class="paragraph">
+<p>There are two ground stations available, the TeleDongle USB to
RF interface and the TeleBT Bluetooth/USB to RF interface. If
you plug either of these in to your Mac or Linux computer it should
“just work”, showing up as a serial port device. Windows systems need
our software before plugging in TeleDongle if you are using a Windows
computer. If you are using an older version of Linux and are having
problems, try moving to a fresher kernel (2.6.33 or
-newer).</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_linux_mac_windows_ground_station_software"></a>2.3. Linux/Mac/Windows Ground Station Software</h2></div></div></div><p>Next you should obtain and install the AltOS software.
+newer).</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_linuxmacwindows_ground_station_software">2.3. Linux/Mac/Windows Ground Station Software</h3>
+<div class="paragraph">
+<p>Next you should obtain and install the AltOS software.
The AltOS distribution includes the AltosUI ground
station program, current firmware images for all of
the hardware, and a number of standalone utilities
available for Linux, Microsoft Windows, Mac OSX. Full
source code and build instructions are also
available. The latest version may always be downloaded
-from <a class="ulink" href="http://altusmetrum.org/AltOS" target="_top">http://altusmetrum.org/AltOS</a></p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_android_ground_station_software"></a>2.4. Android Ground Station Software</h2></div></div></div><p>TeleBT can also connect to an Android device over
+from <a href="http://altusmetrum.org/AltOS" class="bare">http://altusmetrum.org/AltOS</a></p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_android_ground_station_software">2.4. Android Ground Station Software</h3>
+<div class="paragraph">
+<p>TeleBT can also connect to an Android device over
BlueTooth or USB. The
-<a class="ulink" href="https://play.google.com/store/apps/details?id=org.altusmetrum.AltosDroid" target="_top">AltosDroid
+<a href="https://play.google.com/store/apps/details?id=org.altusmetrum.AltosDroid">AltosDroid
Android application</a> is available from the
-<a class="ulink" href="https://play.google.com" target="_top">Google Play system</a>.</p><p>You don’t need a data plan to use AltosDroid, but
-without network access, you’ll want to download
+<a href="https://play.google.com">Google Play system</a>.</p>
+</div>
+<div class="paragraph">
+<p>You don’t need a data plan to use AltosDroid, but
+without network access, you’ll want to download
offline map data before wandering away from the
-network.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_using_altus_metrum_hardware"></a>Chapter 3. Using Altus Metrum Hardware</h1></div></div></div><p>Here are general instructions for hooking up an Altus Metrum
+network.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_using_altus_metrum_hardware">3. Using Altus Metrum Hardware</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Here are general instructions for hooking up an Altus Metrum
flight computer. Instructions specific to each model will be
-found in the section devoted to that model below.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_wiring_and_electrical_interference"></a>3.1. Wiring and Electrical Interference</h2></div></div></div><p>To prevent electrical interference from affecting the
-operation of the flight computer, it’s important to always
+found in the section devoted to that model below.</p>
+</div>
+<div class="sect2">
+<h3 id="_wiring_and_electrical_interference">3.1. Wiring and Electrical Interference</h3>
+<div class="paragraph">
+<p>To prevent electrical interference from affecting the
+operation of the flight computer, it’s important to always
twist pairs of wires connected to the board. Twist the switch
leads, the pyro leads and the battery leads. This reduces
-interference through a mechanism called common mode rejection.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_hooking_up_lithium_polymer_batteries"></a>3.2. Hooking Up Lithium Polymer Batteries</h2></div></div></div><p>All Altus Metrum flight computers have a two pin JST PH
+interference through a mechanism called common mode rejection.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_hooking_up_lithium_polymer_batteries">3.2. Hooking Up Lithium Polymer Batteries</h3>
+<div class="paragraph">
+<p>All Altus Metrum flight computers have a two pin JST PH
series connector to connect up a single-cell Lithium Polymer
cell (3.7V nominal). You can purchase matching batteries
from the Altus Metrum store, or other vendors, or you can
make your own. Pin 1 of the connector is positive, pin 2 is
negative. Spark Fun sells a cable with the connector
attached, which they call a
-<a class="ulink" href="https://www.sparkfun.com/products/9914" target="_top">JST Jumper 2 Wire Assembly</a></p><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>Many RC vendors also sell lithium polymer batteries with
+<a href="https://www.sparkfun.com/products/9914">JST Jumper 2 Wire Assembly</a></p>
+</div>
+<div class="admonitionblock warning">
+<table>
+<tr>
+<td class="icon">
+<img src="./images/icons/warning.svg" alt="Warning">
+</td>
+<td class="content">
+Many RC vendors also sell lithium polymer batteries with
this same connector. All that we have found use the opposite
polarity, and if you use them that way, you will damage or
-destroy the flight computer.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_hooking_up_pyro_charges"></a>3.3. Hooking Up Pyro Charges</h2></div></div></div><p>Altus Metrum flight computers always have two screws for
-each pyro charge. This means you shouldn’t need to put two
+destroy the flight computer.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_hooking_up_pyro_charges">3.3. Hooking Up Pyro Charges</h3>
+<div class="paragraph">
+<p>Altus Metrum flight computers always have two screws for
+each pyro charge. This means you shouldn’t need to put two
wires into a screw terminal or connect leads from pyro
-charges together externally.</p><p>On the flight computer, one lead from each charge is hooked
+charges together externally.</p>
+</div>
+<div class="paragraph">
+<p>On the flight computer, one lead from each charge is hooked
to the positive battery terminal through the power switch.
The other lead is connected through the pyro circuit, which
is connected to the negative battery terminal when the pyro
-circuit is fired.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_hooking_up_a_power_switch"></a>3.4. Hooking Up a Power Switch</h2></div></div></div><p>Altus Metrum flight computers need an external power switch
+circuit is fired.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_hooking_up_a_power_switch">3.4. Hooking Up a Power Switch</h3>
+<div class="paragraph">
+<p>Altus Metrum flight computers need an external power switch
to turn them on. This disconnects both the computer and the
pyro charges from the battery, preventing the charges from
firing when in the Off position. The switch is in-line with
-the positive battery terminal.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_understanding_beeps"></a>3.5. Understanding Beeps</h2></div></div></div><p>Altus Metrum flight computers include a beeper to
+the positive battery terminal.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_understanding_beeps">3.5. Understanding Beeps</h3>
+<div class="paragraph">
+<p>Altus Metrum flight computers include a beeper to
provide information about the state of the system.
-TeleMini doesn’t have room for a beeper, so instead it
+TeleMini doesn’t have room for a beeper, so instead it
uses an LED, which works the same, except for every
-beep is replaced with the flash of the LED.</p><p>Here’s a short summary of all of the modes and the
+beep is replaced with the flash of the LED.</p>
+</div>
+<div class="paragraph">
+<p>Here’s a short summary of all of the modes and the
beeping
(or flashing, in the case of TeleMini v1)
that accompanies each mode. In the description of the
beeping pattern, “dit” means a short beep while "dah"
means a long beep (three times as long). “Brap” means
-a long dissonant tone.</p><div class="table"><a id="idm45058131365520"></a><p class="title"><strong>Table 3.1. AltOS Modes</strong></p><div class="table-contents"><table summary="AltOS Modes" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /><col class="col_4" /></colgroup><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Mode Name</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Abbreviation</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Beeps</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Description</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Startup</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>S</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>battery voltage in decivolts</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Calibrating sensors, detecting orientation.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Idle</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>I</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Ready to accept commands over USB
-or radio link.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Pad</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>P</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dah dah dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Waiting for launch. Not listening for commands.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Boost</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dah dit dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Accelerating upwards.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Fast</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>F</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dit dah dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Decelerating, but moving faster than 200m/s.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Coast</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>C</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dah dit dah dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Decelerating, moving slower than 200m/s</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Drogue</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dah dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Descending after apogee. Above main height.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>M</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dah dah</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Descending. Below main height.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Landed</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>L</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dah dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Stable altitude for at least ten seconds.</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Sensor error</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>X</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>dah dit dit dah</p></td><td style="" align="left" valign="top"><p>Error detected during sensor calibration.</p></td></tr></tbody></table></div></div><br class="table-break" /><p>Here’s a summary of all of the Pad and Idle mode
-indications. In Idle mode, you’ll hear one of these
+a long dissonant tone.</p>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<caption class="title">Table 1. AltOS Modes</caption>
+<colgroup>
+<col style="width: 16.6666%;">
+<col style="width: 16.6666%;">
+<col style="width: 33.3333%;">
+<col style="width: 33.3335%;">
+</colgroup>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Mode Name</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Abbreviation</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Beeps</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Description</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Startup</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">S</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">battery voltage in decivolts</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Calibrating sensors, detecting orientation.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Idle</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">I</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">dit dit</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Ready to accept commands over USB
+or radio link.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Pad</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">P</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">dit dah dah dit</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Waiting for launch. Not listening for commands.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Boost</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">dah dit dit dit</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Accelerating upwards.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Fast</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">F</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">dit dit dah dit</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Decelerating, but moving faster than 200m/s.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Coast</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">dah dit dah dit</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Decelerating, moving slower than 200m/s</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Drogue</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">dah dit dit</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Descending after apogee. Above main height.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Main</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">M</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">dah dah</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Descending. Below main height.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Landed</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">L</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">dit dah dit dit</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Stable altitude for at least ten seconds.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Sensor error</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">dah dit dit dah</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Error detected during sensor calibration.</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>Here’s a summary of all of the Pad and Idle mode
+indications. In Idle mode, you’ll hear one of these
just once after the two short dits indicating idle
mode. In Pad mode, after the dit dah dah dit
-indicating Pad mode, you’ll hear these once every five
-seconds.</p><div class="table"><a id="idm45058131311360"></a><p class="title"><strong>Table 3.2. Pad/Idle Indications</strong></p><div class="table-contents"><table summary="Pad/Idle Indications" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Name </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Beeps </th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Neither</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>brap</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>No continuity detected on either apogee or main igniters.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Continuity detected only on apogee igniter.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Continuity detected only on main igniter.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Both</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Continuity detected on both igniters.</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Storage Full</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>warble</p></td><td style="" align="left" valign="top"><p>On-board data logging storage is full. This will
+indicating Pad mode, you’ll hear these once every five
+seconds.</p>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<caption class="title">Table 2. Pad/Idle Indications</caption>
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 20%;">
+<col style="width: 60%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Beeps</th>
+<th class="tableblock halign-left valign-top">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Neither</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">brap</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">No continuity detected on either apogee or main igniters.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">dit</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Continuity detected only on apogee igniter.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Main</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">dit dit</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Continuity detected only on main igniter.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Both</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">dit dit dit</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Continuity detected on both igniters.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Storage Full</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">warble</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">On-board data logging storage is full. This will
not prevent the flight computer from safely
controlling the flight or transmitting telemetry
signals, but no record of the flight will be
-stored in on-board flash.</p></td></tr></tbody></table></div></div><br class="table-break" /><p>For devices with a radio transmitter, in addition to
+stored in on-board flash.</p></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 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>
+</tbody>
+</table>
+<div class="paragraph">
+<p>For devices with a radio transmitter, in addition to
the digital and APRS telemetry signals, you can also
receive audio tones with a standard amateur
70cm FM receiver. While on the pad, you will hear
-igniter status once every five seconds.</p><div class="table"><a id="idm45058131285120"></a><p class="title"><strong>Table 3.3. Pad Radio Indications</strong></p><div class="table-contents"><table summary="Pad Radio Indications" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Name </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Beeps </th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Neither</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>½ second tone</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>No continuity detected on either apogee or main igniters.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Continuity detected only on apogee igniter.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Continuity detected only on main igniter.</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Both</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>dit dit dit</p></td><td style="" align="left" valign="top"><p>Continuity detected on both igniters.</p></td></tr></tbody></table></div></div><br class="table-break" /><p>During ascent, the tones will be muted to allow the
-telemetry data to consume the full radio bandwidth.</p><p>During descent and after landing, a ½ second tone will
+igniter status once every five seconds.</p>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<caption class="title">Table 3. Pad Radio Indications</caption>
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 20%;">
+<col style="width: 60%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Name</th>
+<th class="tableblock halign-left valign-top">Beeps</th>
+<th class="tableblock halign-left valign-top">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Neither</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">½ second tone</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">No continuity detected on either apogee or main igniters.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">dit</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Continuity detected only on apogee igniter.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Main</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">dit dit</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Continuity detected only on main igniter.</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Both</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">dit dit dit</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Continuity detected on both igniters.</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>During ascent, the tones will be muted to allow the
+telemetry data to consume the full radio bandwidth.</p>
+</div>
+<div class="paragraph">
+<p>During descent and after landing, a ½ second tone will
be transmitted every five seconds. This can be used to
find the rocket using RDF techniques when the signal
is too weak to receive GPS information via telemetry
-or APRS.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_turning_on_the_power"></a>3.6. Turning On the Power</h2></div></div></div><p>Connect a battery and power switch and turn the switch
+or APRS.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_turning_on_the_power">3.6. Turning On the Power</h3>
+<div class="paragraph">
+<p>Connect a battery and power switch and turn the switch
to "on". The flight computer will signal power on by
reporting the battery voltage and then perform an internal self
-test and sensor calibration.</p><p>Once the self test and calibration are complete, there
+test and sensor calibration.</p>
+</div>
+<div class="paragraph">
+<p>Once the self test and calibration are complete, there
are two modes that an Altus Metrum flight computer can
-operate in:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
-Flight/Pad
-</span></dt><dd>
-The flight computer is waiting to detect
+operate in:</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">Flight/Pad</dt>
+<dd>
+<p>The flight computer is waiting to detect
launch and then fly the rocket. In this mode, the USB
link is
disabled, and the radio goes into transmit-only mode.
The only way to get out of this
-mode is to power the flight computer down.
-</dd><dt><span class="term">
-Idle
-</span></dt><dd>
-The flight computer is ready to communicate over USB
+mode is to power the flight computer down. See below for how to get the flight
+computer to come up in Flight/Pad mode at power on.</p>
+</dd>
+<dt class="hdlist1">Idle</dt>
+<dd>
+<p>The flight computer is ready to communicate over USB
and in packet mode over the radio.
You can configure
the flight computer, download data or display
-the current state.
-</dd></dl></div><p>For flight computers with accelerometers (TeleMetrum,
-EasyMega and TeleMega), the mode is selected by the
+the current state. See below for how to get the flight
+computer to come up in Idle mode at power on.</p>
+</dd>
+</dl>
+</div>
+<div class="paragraph">
+<p>For flight computers with accelerometers (TeleMetrum,
+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
-enter Idle mode.</p><p>For EasyMini, if the USB cable is connected to a
+enter Idle mode.</p>
+</div>
+<div class="paragraph">
+<p>For EasyMini, if the USB cable is connected to a
computer, it will enter Idle mode. Otherwise, it will
-enter Flight/Pad mode.</p><p>For TeleMini v1.0, if a packet link is waiting to
+enter Flight/Pad mode.</p>
+</div>
+<div class="paragraph">
+<p>For TeleMini v1.0, if a packet link is waiting to
connect when the device is powered on, it will enter
-Idle mode, otherwise it will enter Flight/Pad mode.</p><p>You can see in <a class="xref" href="#_understanding_beeps" title="3.5. Understanding Beeps">Section 3.5, “Understanding Beeps”</a>
-how to tell which mode the flight computer is in.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_an_external_active_switch_circuit"></a>3.7. Using an External Active Switch Circuit</h2></div></div></div><p>You can use an active switch circuit, such as the
+Idle mode, otherwise it will enter Flight/Pad mode.</p>
+</div>
+<div class="paragraph">
+<p>You can see in <a href="#_understanding_beeps">Understanding Beeps</a>
+how to tell which mode the flight computer is in.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_using_an_external_active_switch_circuit">3.7. Using an External Active Switch Circuit</h3>
+<div class="paragraph">
+<p>You can use an active switch circuit, such as the
Featherweight Magnetic Switch, with any Altus Metrum
flight computer. These require three connections, one to
the battery, one to the positive power input on the flight
computer and one to ground. Find instructions on how to
hook these up for each flight computer below. Then follow
the instructions that come with your active switch to
-connect it up.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_a_separate_pyro_battery"></a>3.8. Using a Separate Pyro Battery</h2></div></div></div><p>As mentioned above in <a class="xref" href="#_hooking_up_pyro_charges" title="3.3. Hooking Up Pyro Charges">Section 3.3, “Hooking Up Pyro Charges”</a>, one
+connect it up.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_using_a_separate_pyro_battery">3.8. Using a Separate Pyro Battery</h3>
+<div class="paragraph">
+<p>As mentioned above in <a href="#_hooking_up_pyro_charges">Hooking Up Pyro Charges</a>, one
lead for each of the pyro charges is connected through
the power switch directly to the positive battery
terminal. The other lead is connected to the pyro
circuit, which connects it to the negative battery
terminal when the pyro circuit is fired. The pyro
circuit on all of the flight computers is designed to
-handle up to 16V.</p><p>To use a separate pyro battery, connect the negative pyro
+handle up to 16V.</p>
+</div>
+<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
terminal, firing the igniter. Specific instructions on how
to hook this up for each flight computer will be found
-in the section below for that flight computer.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_a_different_kind_of_battery"></a>3.9. Using a Different Kind of Battery</h2></div></div></div><p>EasyMini
-and TeleMini v2 are
+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 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
-battery.</p><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>TeleMega, EasyMega and TeleMetrum are only designed to
+battery.</p>
+</div>
+<div class="admonitionblock warning">
+<table>
+<tr>
+<td class="icon">
+<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
different kind of battery to any of these will destroy
-the board.</p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_telemetrum"></a>Chapter 4. TeleMetrum</h1></div></div></div><div class="figure"><a id="idm45058137013184"></a><p class="title"><strong>Figure 4.1. TeleMetrum v2 Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telemetrum-v2.0-th.jpg" width="495" alt="telemetrum-v2.0-th.jpg" /></div></div></div><br class="figure-break" /><div class="figure"><a id="idm45058131219712"></a><p class="title"><strong>Figure 4.2. TeleMetrum v1 Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telemetrum-v1.1-thside.jpg" width="495" alt="telemetrum-v1.1-thside.jpg" /></div></div></div><br class="figure-break" /><p>TeleMetrum is a 1 inch by 2¾ inch circuit board. It was designed to
+the board.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_using_packet_link_mode">3.10. Using Packet Link Mode</h3>
+<div class="paragraph">
+<p>All AltusMetrum flight computers that have a radio can
+communicate with the ground station software for
+configuration and other operations using the Packet
+Link mode. This uses radio communication instead of a
+USB cable. To set this up, the ground station software
+must be configured to the correct data rate, frequency
+and callsign.</p>
+</div>
+<div class="paragraph">
+<p>You can monitor Packet Link mode from TeleBT or
+TeleDongle by watching the LEDs. Each time the device
+transmits, the red LED will flash. When the link is
+busy, or when the link is not working, the device will
+transmit 10 times per second, so the LED will flash
+rapidly. When the link is working and there is no data
+to send, the link will flash once per second, and the
+LED will flash more slowly.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_telemetrum">4. TeleMetrum</h2>
+<div class="sectionbody">
+<div class="imageblock">
+<div class="content">
+<img src="telemetrum-v2.0-th.jpg" alt="telemetrum v2.0 th" width="400">
+</div>
+<div class="title">Figure 1. TeleMetrum v2 Board</div>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="telemetrum-v1.1-thside.jpg" alt="telemetrum v1.1 thside" width="400">
+</div>
+<div class="title">Figure 2. TeleMetrum v1 Board</div>
+</div>
+<div class="paragraph">
+<p>TeleMetrum is a 1 inch by 2¾ inch circuit board. It was designed to
fit inside coupler for 29mm air-frame tubing, but using it in a tube that
small in diameter may require some creativity in mounting and wiring
to succeed! The presence of an accelerometer means TeleMetrum should
antenna wire is about 7 inches long, and wiring for a power switch and
the e-matches for apogee and main ejection charges depart from the
fin can end of the board, meaning an ideal “simple” avionics
-bay for TeleMetrum should have at least 10 inches of interior length.</p><p>There are two generations of the TeleMetrum design. The
-major changes in the v2 generation are:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-uBlox GPS chip certified for altitude records
-</li><li class="listitem">
-Higher power radio (40mW vs 10mW)
-</li><li class="listitem">
-APRS support
-</li></ul></div><p>Otherwise, they’re the same size, with mounting holes and
-screw terminals in the same position.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_telemetrum_screw_terminals"></a>4.1. TeleMetrum Screw Terminals</h2></div></div></div><p>TeleMetrum has six screw terminals on the end of the board
+bay for TeleMetrum should have at least 10 inches of interior length.</p>
+</div>
+<div class="paragraph">
+<p>There are two generations of the TeleMetrum design. The
+major changes after v1 generation are:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>uBlox GPS chip certified for altitude records</p>
+</li>
+<li>
+<p>Higher power radio (40mW vs 10mW)</p>
+</li>
+<li>
+<p>APRS support</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Otherwise, they’re the same size, with mounting holes and
+screw terminals in the same position.</p>
+</div>
+<div class="sect2">
+<h3 id="_telemetrum_screw_terminals">4.1. TeleMetrum Screw Terminals</h3>
+<div class="paragraph">
+<p>TeleMetrum has six screw terminals on the end of the board
opposite the telemetry antenna. Two are for the power
switch, and two each for the apogee and main igniter
circuits. Using the picture above and starting from the top,
-the terminals are as follows:</p><div class="table"><a id="idm45058131209152"></a><p class="title"><strong>Table 4.1. TeleMetrum Screw Terminals</strong></p><div class="table-contents"><table summary="TeleMetrum Screw Terminals" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal #</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal Name</th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Output</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to flight computer</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Input</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to positive battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main +</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>5</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee +</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>6</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Apogee -</p></td><td style="" align="left" valign="top"><p>Apogee pyro channel connection to pyro circuit</p></td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_a_separate_pyro_battery_with_telemetrum"></a>4.2. Using a Separate Pyro Battery with TeleMetrum</h2></div></div></div><p>As described above, using an external pyro battery involves
+the terminals are as follows:</p>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<caption class="title">Table 4. TeleMetrum 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">1</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">2</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>
+<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 +</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>
+<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 connection to pyro circuit</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 +</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>
+<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 connection to pyro circuit</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect2">
+<h3 id="_using_a_separate_pyro_battery_with_telemetrum">4.2. Using a Separate Pyro Battery with TeleMetrum</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><p>To connect the negative battery terminal to the TeleMetrum
+lead to the per-channel pyro circuit connection.</p>
+</div>
+<div class="paragraph">
+<p>To connect the negative battery terminal to the TeleMetrum
ground, insert a small piece of wire, 24 to 28 gauge
stranded, into the GND hole just above the screw terminal
-strip and solder it in place.</p><p>Connecting the positive battery terminal to the pyro
+strip and solder it in place.</p>
+</div>
+<div class="paragraph">
+<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><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></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_an_active_switch_with_telemetrum"></a>4.3. Using an Active Switch with TeleMetrum</h2></div></div></div><p>As explained above, an external active switch requires three
+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>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_using_an_active_switch_with_telemetrum">4.3. Using an Active Switch with TeleMetrum</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.</p><p>The positive battery terminal is available on screw terminal
+the flight computer positive input and one to ground.</p>
+</div>
+<div class="paragraph">
+<p>The positive battery terminal is available on screw terminal
2, the positive flight computer input is on terminal 1. To
hook a lead to ground, solder a piece of wire, 24 to 28
-gauge stranded, to the GND hole just above terminal 1.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_telemini_v1_0"></a>Chapter 5. TeleMini v1.0</h1></div></div></div><div class="figure"><a id="idm45058131173360"></a><p class="title"><strong>Figure 5.1. TeleMini v1.0 Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telemini-v1-top.jpg" width="495" alt="telemini-v1-top.jpg" /></div></div></div><br class="figure-break" /><p>TeleMini v1.0 is ½ inches by 1½ inches. It was
+gauge stranded, to the GND hole just above terminal 1.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_telemini">5. TeleMini</h2>
+<div class="sectionbody">
+<div class="imageblock">
+<div class="content">
+<img src="telemini-v3.0-top.jpg" alt="telemini v3.0 top" width="400">
+</div>
+<div class="title">Figure 3. TeleMini v3 Board</div>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="telemini-v3.0-bottom.jpg" alt="telemini v3.0 bottom" width="400">
+</div>
+</div>
+<div class="paragraph">
+<p>TeleMini v3 is 0.5 inches by 1.67 inches. It was
designed to fit inside an 18mm air-frame tube, but using it in
a tube that small in diameter may require some creativity in
mounting and wiring to succeed! Since there is no
accelerometer, TeleMini can be mounted in any convenient
orientation. The default ¼ wave UHF wire antenna attached to
-the center of one end of the board is about 7 inches long. Two
-wires for the power switch are connected to holes in the
+the center of one end of the board is about 7 inches long. Screw
+terminals for the power switch are located in the
middle of the board. Screw terminals for the e-matches for
apogee and main ejection charges depart from the other end of
the board, meaning an ideal “simple” avionics bay for TeleMini
-should have at least 9 inches of interior length.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_telemini_v1_0_screw_terminals"></a>5.1. TeleMini v1.0 Screw Terminals</h2></div></div></div><p>TeleMini v1.0 has four screw terminals on the end of the
+should have at least 9 inches of interior length.</p>
+</div>
+<div class="sect2">
+<h3 id="_telemini_v3_screw_terminals">5.1. TeleMini v3 Screw Terminals</h3>
+<div class="paragraph">
+<p>TeleMini v3 has four screw terminals on the end of the
board opposite the telemetry antenna. Two are for the apogee
-and two are for main igniter circuits. There are also wires
-soldered to the board for the power switch. Using the
-picture above and starting from the top for the terminals
-and from the left for the power switch wires, the
-connections are as follows:</p><div class="table"><a id="idm45058131166752"></a><p class="title"><strong>Table 5.1. TeleMini v1.0 Screw Terminals</strong></p><div class="table-contents"><table summary="TeleMini v1.0 Screw Terminals" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal #</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal Name</th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Left</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Output</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to flight computer</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Right</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Switch Input</p></td><td style="" align="left" valign="top"><p>Switch connection to positive battery terminal</p></td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_a_separate_pyro_battery_with_telemini_v1_0"></a>5.2. Using a Separate Pyro Battery with TeleMini v1.0</h2></div></div></div><p>As described above, using an external pyro battery involves
+and two are for main igniter circuits. Another two
+screw terminals are located in the middle of the board
+for the power switch. Using the
+picture above and starting from the top for the pyro terminals
+and from the left for the power switch terminals, the
+connections are as follows:</p>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<caption class="title">Table 5. TeleMini v3 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">1</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 connection to pyro circuit</p></td>
+</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 +</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>
+<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 connection to pyro circuit</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 +</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>
+<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">Right</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="_using_a_separate_pyro_battery_with_telemini_v3">5.2. Using a Separate Pyro Battery with TeleMini v3</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. Because
-there is no solid ground connection to use on TeleMini, this
-is not recommended.</p><p>The only available ground connection on TeleMini v1.0 are
+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
the two mounting holes next to the telemetry
antenna. Somehow connect a small piece of wire to one of
-those holes and hook it to the negative pyro battery terminal.</p><p>Connecting the positive battery terminal to the pyro
-charges must be done separate from TeleMini v1.0, by soldering
-them together or using some other connector.</p><p>The other lead from each pyro charge is then inserted into
+those holes and hook it to the negative pyro battery terminal.</p>
+</div>
+<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. 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
the appropriate per-pyro channel screw terminal (terminal 3 for the
-Main charge, terminal 1 for the Apogee charge).</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_an_active_switch_with_telemini_v1_0"></a>5.3. Using an Active Switch with TeleMini v1.0</h2></div></div></div><p>As explained above, an external active switch requires three
+Main charge, terminal 1 for the Apogee charge).</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_using_an_active_switch_with_telemini_v3">5.3. Using an Active Switch with TeleMini v3</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. Again,
-because TeleMini doesn’t have any good ground connection,
-this is not recommended.</p><p>The positive battery terminal is available on the Right
+because TeleMini doesn’t have any good ground connection,
+this is not recommended.</p>
+</div>
+<div class="paragraph">
+<p>The positive battery terminal is available on the Right
power switch wire, the positive flight computer input is on
the left power switch wire. Hook a lead to either of the
-mounting holes for a ground connection.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_easymini"></a>Chapter 6. EasyMini</h1></div></div></div><div class="figure"><a id="idm45058131130096"></a><p class="title"><strong>Figure 6.1. EasyMini Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="easymini-top.jpg" width="495" alt="easymini-top.jpg" /></div></div></div><br class="figure-break" /><p>EasyMini is built on a 0.8 inch by 1½ inch circuit board. It’s
-designed to fit in a 24mm coupler tube.</p><p>You usually don’t need to configure EasyMini at all; it’s set
+mounting holes for a ground connection.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_using_packet_link_mode_with_telemini">5.4. Using Packet Link Mode with TeleMini</h3>
+<div class="paragraph">
+<p>After TeleMini powers up, it will check to see if some
+device is attempting to communicate with it using
+Packet Link Mode. If so, it will switch to idle mode
+and start communicating. To switch to flight mode,
+reboot the device either over the radio link or by
+powering it off and back on.</p>
+</div>
+<div class="paragraph">
+<p>If no ground station is attempting to communicate
+using Packet Link Mode, TeleMini will enter pad mode
+and prepare for flight.</p>
+</div>
+<div class="paragraph">
+<p>The sequence of operations to use Packet Link Mode
+with TeleMini is:</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>Configure the ground station data rate, frequency
+and callsign to match the TeleMini settings.</p>
+</li>
+<li>
+<p>Start Packet Link Mode in the ground station by
+selecting the desired operation (Safe Flight Data,
+Configure Altimeter, Fire Igniter or Monitor
+Idle). Select the TeleBT or TeleDongle device. The
+red LED should begin flashing rapidly.</p>
+</li>
+<li>
+<p>Turn on TeleMini. You should see the red LED flash
+very rapidly during the initial communication burst,
+but it should then slow down when the link is idle.</p>
+</li>
+</ol>
+</div>
+<div class="paragraph">
+<p>Once TeleMini is in Idle mode, it will stay in that
+mode until rebooted. That means you can stop one
+Packet Link operation, wait a while and start another
+Packet Link operation.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_forcing_telemini_radio_parameters_to_known_defaults">5.5. Forcing TeleMini radio parameters to known defaults</h3>
+<div class="paragraph">
+<p>If you don’t know what the TeleMini frequency and
+callsign settings are, you can temporarily force it
+back to the original default values (frequency
+434.550MHz, callsign N0CALL) by connecting a wire
+between hole 3 and hole 6 on the debug connector. Hole
+3 has the square pad around it, hole 6 is the one
+nearest the MS5607 baro sensor, which is a rectangular
+component with a metal cap that has two holes in it.</p>
+</div>
+<div class="paragraph">
+<p>Once TeleMini has been powered up with this wire
+connected, the wire may be removed. The radio
+parameters will stay set to these default values until
+changed by the user or when the device is rebooted.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_telemini_v1">5.6. TeleMini v1</h3>
+<div class="paragraph">
+<p>TeleMini v1 is the earlier version of this product. It
+has a lower-power radio, less storage, no beeper and
+soldered-in wires instead of screw terminals for the
+power switch.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="telemini-v1-top.jpg" alt="telemini v1 top" width="400">
+</div>
+<div class="title">Figure 4. TeleMini v1 Board</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_easymini">6. EasyMini</h2>
+<div class="sectionbody">
+<div class="imageblock">
+<div class="content">
+<img src="easymini-top.jpg" alt="easymini top" width="400">
+</div>
+<div class="title">Figure 5. EasyMini Board</div>
+</div>
+<div class="paragraph">
+<p>EasyMini 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>You usually don’t need to configure EasyMini at all; it’s set
up to do dual-deployment with an event at apogee to separate
the airframe and deploy a drogue and another event at 250m
(820ft) to deploy the main. Install EasyMini in your airframe,
-hook up a battery, igniters and a power switch and you’re
-ready to fly.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_easymini_screw_terminals"></a>6.1. EasyMini Screw Terminals</h2></div></div></div><p>EasyMini has two sets of four screw terminals near one end of the
+hook up a battery, igniters and a power switch and you’re
+ready to fly.</p>
+</div>
+<div class="sect2">
+<h3 id="_easymini_screw_terminals">6.1. EasyMini Screw Terminals</h3>
+<div class="paragraph">
+<p>EasyMini has two sets of four screw terminals near one end of the
board. Using the picture
above, the top four have connections for the main pyro
circuit and an external battery and the bottom four have
connections for the apogee pyro circuit and the power
-switch. Counting from the left, the connections are as follows:</p><div class="table"><a id="idm45058131124080"></a><p class="title"><strong>Table 6.1. EasyMini Screw Terminals</strong></p><div class="table-contents"><table summary="EasyMini Screw Terminals" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal #</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal Name</th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Battery</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Positive external battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Battery -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Negative external battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Output</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to flight computer</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Bottom 4</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Switch Input</p></td><td style="" align="left" valign="top"><p>Switch connection to positive battery terminal</p></td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_connecting_a_battery_to_easymini"></a>6.2. Connecting A Battery To EasyMini</h2></div></div></div><p>There are two possible battery connections on
+switch. Counting from the left, the connections are as follows:</p>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<caption class="title">Table 6. EasyMini 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">Main -</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Main pyro channel 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">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 +</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">Apogee -</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee pyro channel 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">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>
+<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_easymini">6.2. Connecting A Battery To EasyMini</h3>
+<div class="paragraph">
+<p>There are two possible battery connections on
EasyMini. You can use either method; both feed
-through the power switch terminals.</p><p>One battery connection is the standard Altus Metrum
+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><p>The other is a pair of screw terminals marked <span class="emphasis"><em>Battery
-+</em></span> and <span class="emphasis"><em>Battery -</em></span>. Connect a battery from 4 to 12
-volts to these terminals, being careful to match polarity.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_charging_lithium_batteries"></a>6.3. Charging Lithium Batteries</h2></div></div></div><p>Because EasyMini allows for batteries other than the
+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">6.3. Charging Lithium Batteries</h3>
+<div class="paragraph">
+<p>Because EasyMini 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
+using a Litium Polymer cell, you’ll need an external
charger. These are available from Altus Metrum, or
-from Spark Fun.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_a_separate_pyro_battery_with_easymini"></a>6.4. Using a Separate Pyro Battery with EasyMini</h2></div></div></div><p>As described above, using an external pyro battery involves
+from Spark Fun.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_using_a_separate_pyro_battery_with_easymini">6.4. Using a Separate Pyro Battery with EasyMini</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><p>To connect the negative pyro battery terminal to EasyMini
+lead to the per-channel pyro circuit connection.</p>
+</div>
+<div class="paragraph">
+<p>To connect the negative pyro battery terminal to EasyMini
ground, connect it to the negative external battery
-connection, top terminal 4.</p><p>Connecting the positive battery terminal to the pyro
+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 EasyMini, by soldering
-them together or using some other connector.</p><p>The other lead from each pyro charge is then inserted into
+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 the Main charge, bottom terminal 1 for the
-Apogee charge).</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_an_active_switch_with_easymini"></a>6.5. Using an Active Switch with EasyMini</h2></div></div></div><p>As explained above, an external active switch requires three
+Apogee charge).</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_using_an_active_switch_with_easymini">6.5. Using an Active Switch with EasyMini</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><p>The positive battery terminal is available on bottom
+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 class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_telemega"></a>Chapter 7. TeleMega</h1></div></div></div><div class="figure"><a id="idm45058131075552"></a><p class="title"><strong>Figure 7.1. TeleMega Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telemega-v1.0-top.jpg" width="495" alt="telemega-v1.0-top.jpg" /></div></div></div><br class="figure-break" /><p>TeleMega is a 1¼ inch by 3¼ inch circuit board. It was
+bottom terminal 3.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_telemega">7. TeleMega</h2>
+<div class="sectionbody">
+<div class="imageblock">
+<div class="content">
+<img src="telemega-v1.0-top.jpg" alt="telemega v1.0 top" width="400">
+</div>
+<div class="title">Figure 6. TeleMega Board</div>
+</div>
+<div class="paragraph">
+<p>TeleMega is a 1¼ inch by 3¼ inch circuit board. It was
designed to easily fit in a 38mm coupler. Like TeleMetrum,
TeleMega has an accelerometer and so it must be mounted so that
the board is aligned with the flight axis. It can be mounted
-either antenna up or down.</p><p>TeleMega v2.0 has a few minor changes from v1.0:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Companion connector matches EasyMega functions
-</li><li class="listitem">
-Serial port connector replaced with servo connector with
-support for up to 4 PWM channels.
-</li><li class="listitem">
-Radio switched from cc1120 to cc1200.
-</li></ul></div><p>None of these affect operation using the stock firmware, but
+either antenna up or down.</p>
+</div>
+<div class="paragraph">
+<p>TeleMega v2.0 has a few minor changes from v1.0:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Companion connector matches EasyMega functions</p>
+</li>
+<li>
+<p>Serial port connector replaced with servo connector with
+support for up to 4 PWM channels.</p>
+</li>
+<li>
+<p>Radio switched from cc1120 to cc1200.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>None of these affect operation using the stock firmware, but
they do mean that the device needs different firmware to
operate correctly, so make sure you load the right firmware
-when reflashing the device.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_telemega_screw_terminals"></a>7.1. TeleMega Screw Terminals</h2></div></div></div><p>TeleMega has two sets of nine screw terminals on the end of
-the board opposite the telemetry antenna. They are as follows:</p><div class="table"><a id="idm45058131066192"></a><p class="title"><strong>Table 7.1. TeleMega Screw Terminals</strong></p><div class="table-contents"><table summary="TeleMega Screw Terminals" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal #</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal Name</th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Input</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to positive battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Output</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to flight computer</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>GND</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Ground connection for use with external active switch</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 5</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 6</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 7</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 8</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 9</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>GND</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Ground connection for negative pyro battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Pyro</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Positive pyro battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Lipo</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Power switch output. Use to connect main battery to pyro battery input</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 5</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 6</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 7</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 8</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>C -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>C pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Bottom 9</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>C</p></td><td style="" align="left" valign="top"><p>C pyro channel common connection to battery</p></td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_a_separate_pyro_battery_with_telemega"></a>7.2. Using a Separate Pyro Battery with TeleMega</h2></div></div></div><p>TeleMega provides explicit support for an external pyro
+when reflashing the device.</p>
+</div>
+<div class="sect2">
+<h3 id="_telemega_screw_terminals">7.1. TeleMega Screw Terminals</h3>
+<div class="paragraph">
+<p>TeleMega has two sets of nine screw terminals on the end of
+the board opposite the telemetry antenna. They are as follows:</p>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<caption class="title">Table 7. TeleMega 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">Switch Input</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Switch connection to positive battery terminal</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">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">Top 3</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">GND</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Ground connection for use with external active switch</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">Main -</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Main pyro channel connection to pyro circuit</p></td>
+</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 +</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>
+<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 connection to pyro circuit</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 +</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>
+<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 connection to pyro circuit</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 +</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>
+<td class="tableblock halign-left valign-top"><p class="tableblock">GND</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Ground connection for negative pyro battery terminal</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">Pyro</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Positive pyro battery terminal</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">Lipo</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Power switch output. Use to connect main battery to pyro battery input</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">A -</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">A pyro channel connection to pyro circuit</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 +</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>
+<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 connection to pyro circuit</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 +</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>
+<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 connection to pyro circuit</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 +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">C pyro channel common connection to battery +</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect2">
+<h3 id="_using_a_separate_pyro_battery_with_telemega">7.2. Using a Separate Pyro Battery with TeleMega</h3>
+<div class="paragraph">
+<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
-terminals to hook up all of the pyro charges.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_only_one_battery_with_telemega"></a>7.3. Using Only One Battery With TeleMega</h2></div></div></div><p>Because TeleMega has built-in support for a separate pyro
+(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="sect2">
+<h3 id="_using_only_one_battery_with_telemega">7.3. Using Only One Battery With TeleMega</h3>
+<div class="paragraph">
+<p>Because TeleMega has built-in support for a separate pyro
battery, if you want to fly with just one battery running
both the computer and firing the charges, you need to
connect the flight computer battery to the pyro
circuit. TeleMega has two screw terminals for this—hook a
wire from the Lipo terminal (Bottom 3) to the Pyro terminal
-(Bottom 2).</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_an_active_switch_with_telemega"></a>7.4. Using an Active Switch with TeleMega</h2></div></div></div><p>As explained above, an external active switch requires three
+(Bottom 2).</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_using_an_active_switch_with_telemega">7.4. Using an Active Switch with TeleMega</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.</p><p>The positive battery terminal is available on Top terminal
+the flight computer positive input and one to ground.</p>
+</div>
+<div class="paragraph">
+<p>The positive battery terminal is available on Top terminal
1, the positive flight computer input is on Top terminal
-2. Ground is on Top terminal 3.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_easymega"></a>Chapter 8. EasyMega</h1></div></div></div><div class="figure"><a id="idm45058130988752"></a><p class="title"><strong>Figure 8.1. EasyMega Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="easymega-v1.0-top.jpg" width="405" alt="easymega-v1.0-top.jpg" /></div></div></div><br class="figure-break" /><p>EasyMega is a 1¼ inch by 2¼ inch circuit board. It was
+2. Ground is on Top terminal 3.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_easymega">8. EasyMega</h2>
+<div class="sectionbody">
+<div class="imageblock">
+<div class="content">
+<img src="easymega-v1.0-top.jpg" alt="easymega v1.0 top" width="400">
+</div>
+<div class="title">Figure 7. EasyMega Board</div>
+</div>
+<div class="paragraph">
+<p>EasyMega is a 1¼ inch by 2¼ inch circuit board. It was
designed to easily fit in a 38mm coupler. Like TeleMetrum,
EasyMega has an accelerometer and so it must be mounted so that
the board is aligned with the flight axis. It can be mounted
-either antenna up or down.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_easymega_screw_terminals"></a>8.1. EasyMega Screw Terminals</h2></div></div></div><p>EasyMega has two sets of nine screw terminals on the end of
-the board opposite the telemetry antenna. They are as follows:</p><div class="table"><a id="idm45058130983408"></a><p class="title"><strong>Table 8.1. EasyMega Screw Terminals</strong></p><div class="table-contents"><table summary="EasyMega Screw Terminals" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal #</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal Name</th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Input</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to positive battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Output</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to flight computer</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>GND</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Ground connection for use with external active switch</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 5</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 6</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 7</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 8</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 9</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>GND</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Ground connection for negative pyro battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Pyro</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Positive pyro battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Lipo</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Power switch output. Use to connect main battery to pyro battery input</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 5</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 6</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 7</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 8</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>C -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>C pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Bottom 9</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>C</p></td><td style="" align="left" valign="top"><p>C pyro channel common connection to battery</p></td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_a_separate_pyro_battery_with_easymega"></a>8.2. Using a Separate Pyro Battery with EasyMega</h2></div></div></div><p>EasyMega provides explicit support for an external pyro
+either antenna up or down.</p>
+</div>
+<div class="sect2">
+<h3 id="_easymega_screw_terminals">8.1. EasyMega Screw Terminals</h3>
+<div class="paragraph">
+<p>EasyMega has two sets of nine screw terminals on the end of
+the board opposite the telemetry antenna. They are as follows:</p>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<caption class="title">Table 8. EasyMega 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">Switch Input</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Switch connection to positive battery terminal</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">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">Top 3</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">GND</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Ground connection for use with external active switch</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">Main -</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Main pyro channel connection to pyro circuit</p></td>
+</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 +</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>
+<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 connection to pyro circuit</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 +</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>
+<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 connection to pyro circuit</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 +</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>
+<td class="tableblock halign-left valign-top"><p class="tableblock">GND</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Ground connection for negative pyro battery terminal</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">Pyro</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Positive pyro battery terminal</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">Lipo</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Power switch output. Use to connect main battery to pyro battery input</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">A -</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">A pyro channel connection to pyro circuit</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 +</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>
+<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 connection to pyro circuit</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 +</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>
+<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 connection to pyro circuit</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 +</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">C pyro channel common connection to battery +</p></td>
+</tr>
+</tbody>
+</table>
+</div>
+<div class="sect2">
+<h3 id="_using_a_separate_pyro_battery_with_easymega">8.2. Using a Separate Pyro Battery with EasyMega</h3>
+<div class="paragraph">
+<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
-terminals to hook up all of the pyro charges.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_only_one_battery_with_easymega"></a>8.3. Using Only One Battery With EasyMega</h2></div></div></div><p>Because EasyMega has built-in support for a separate pyro
+(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="sect2">
+<h3 id="_using_only_one_battery_with_easymega">8.3. Using Only One Battery With EasyMega</h3>
+<div class="paragraph">
+<p>Because EasyMega has built-in support for a separate pyro
battery, if you want to fly with just one battery running
both the computer and firing the charges, you need to
connect the flight computer battery to the pyro
circuit. EasyMega has two screw terminals for this—hook a
wire from the Lipo terminal (Bottom 3) to the Pyro terminal
-(Bottom 2).</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_an_active_switch_with_easymega"></a>8.4. Using an Active Switch with EasyMega</h2></div></div></div><p>As explained above, an external active switch requires three
+(Bottom 2).</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_using_an_active_switch_with_easymega">8.4. Using an Active Switch with EasyMega</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.</p><p>The positive battery terminal is available on Top terminal
+the flight computer positive input and one to ground.</p>
+</div>
+<div class="paragraph">
+<p>The positive battery terminal is available on Top terminal
1, the positive flight computer input is on Top terminal
-2. Ground is on Top terminal 3.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_installation"></a>Chapter 9. Installation</h1></div></div></div><p>A typical installation involves attaching
+2. Ground is on Top terminal 3.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<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
only a suitable battery, a single pole switch for
power on/off, and two pairs of wires connecting e-matches for the
apogee and main ejection charges. All Altus Metrum products are
designed for use with single-cell batteries with 3.7 volts
nominal.
-TeleMini v2.0 and
EasyMini may also be used with other
-batteries as long as they supply between 4 and 12 volts.</p><p>The battery connectors are a standard 2-pin JST connector; you
+batteries as long as they supply between 4 and 12 volts.</p>
+</div>
+<div class="paragraph">
+<p>The battery connectors are a standard 2-pin JST connector; you
can purchase suitable batteries from the any vendor selling
Altus Metrum products. These batteries are
single-cell Lithium Polymer batteries that nominally provide 3.7
generally reversed from the batteries used by Altus Metrum
products. In particular, the Tenergy batteries supplied for use
in Featherweight flight computers are not compatible with Altus
-Metrum flight computers or battery chargers.</p><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>Check polarity and voltage before connecting any battery not
-purchased from Altus Metrum.</p></div><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>Spark Fun sells batteries that have a matching connector with
+Metrum flight computers or battery chargers.</p>
+</div>
+<div class="admonitionblock warning">
+<table>
+<tr>
+<td class="icon">
+<img src="./images/icons/warning.svg" alt="Warning">
+</td>
+<td class="content">
+Check polarity and voltage before connecting any battery not
+purchased from Altus Metrum.
+</td>
+</tr>
+</table>
+</div>
+<div class="admonitionblock warning">
+<table>
+<tr>
+<td class="icon">
+<img src="./images/icons/warning.svg" alt="Warning">
+</td>
+<td class="content">
+Spark Fun sells batteries that have a matching connector with
the correct polarity. However, these batteries include an
integrated current limiting circuit. That circuit will cause
the battery to shut down when firing the igniter circuit. Do
not use these batteries unless you remove the current limiting
-circuit.</p></div><p>By default, we use the unregulated output of the battery
+circuit.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>By default, we use the unregulated output of the battery
directly to fire ejection charges. This works marvelously
with standard low-current e-matches like the J-Tek from MJG
Technologies, and with Quest Q2G2 igniters. However, if you
want or need to use a separate pyro battery, check out
-<a class="xref" href="#_using_a_separate_pyro_battery" title="3.8. Using a Separate Pyro Battery">Section 3.8, “Using a Separate Pyro Battery”</a> for instructions on how to wire
+<a href="#_using_a_separate_pyro_battery">Using a Separate Pyro Battery</a> for instructions on how to wire
that up. The altimeters are designed to work with an external
-pyro battery of no more than 15 volts.</p><p>Ejection charges are wired directly to the screw terminal block
-at the aft end of the altimeter. You’ll need a very small straight
+pyro battery of no more than 15 volts.</p>
+</div>
+<div class="paragraph">
+<p>Ejection charges are wired directly to the screw terminal block
+at the aft end of the altimeter. You’ll need a very small straight
blade screwdriver for these screws, such as you might find in a
-jeweler’s screwdriver set.</p><p>Except for TeleMini v1.0, the flight computers also use the
+jeweler’s screwdriver set.</p>
+</div>
+<div class="paragraph">
+<p>Except for TeleMini v1.0, the flight computers also use the
screw terminal block for the power switch leads. On TeleMini v1.0,
the power switch leads are soldered directly to the board and
-can be connected directly to a switch.</p><p>For most air-frames, the integrated antennas are more than
+can be connected directly to a switch.</p>
+</div>
+<div class="paragraph">
+<p>For most air-frames, the integrated antennas are more than
adequate. However, if you are installing in a carbon-fiber or
metal electronics bay which is opaque to RF signals, you may need to
use off-board external antennas instead. In this case, you can
replace the stock UHF antenna wire with an edge-launched SMA connector,
and, on TeleMetrum v1, you can unplug the integrated GPS
antenna and select an appropriate off-board GPS antenna with
-cable terminating in a U.FL connector.</p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_using_altus_metrum_products"></a>Chapter 10. Using Altus Metrum Products</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_being_legal"></a>10.1. Being Legal</h2></div></div></div><p>In the US, you need an
-<a class="ulink" href="http://www.altusmetrum.org/Radio/" target="_top">amateur radio license</a>
+cable terminating in a U.FL connector.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_using_altus_metrum_products">11. Using Altus Metrum Products</h2>
+<div class="sectionbody">
+<div class="sect2">
+<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>
or other authorization to legally operate the radio
-transmitters that are part of our products.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_in_the_rocket"></a>10.2. In the Rocket</h2></div></div></div><p>In the rocket itself, you just need a flight computer
+transmitters that are part of our products.</p>
+</div>
+</div>
+<div class="sect2">
+<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
TeleMini or
-EasyMini.</p><p>By default, we ship TeleMini, TeleMetrum and TeleMega
+EasyMini.</p>
+</div>
+<div class="paragraph">
+<p>By default, we ship TeleMini, TeleMetrum and TeleMega
flight computers with a simple wire antenna. If your
electronics bay or the air-frame it resides within is
made of carbon fiber, which is opaque to RF signals,
elsewhere in the rocket. However, note that the GPS
antenna is fixed on all current products, so you
really want to install the flight computer in a bay
-made of RF-transparent materials if at all possible.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_on_the_ground"></a>10.3. On the Ground</h2></div></div></div><p>To receive the data stream from the rocket, you need
+made of RF-transparent materials if at all possible.</p>
+</div>
+</div>
+<div class="sect2">
+<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
-<a class="ulink" href="http://www.altusmetrum.org/TeleDongle/" target="_top">TeleDongle</a>
+<a href="http://www.altusmetrum.org/TeleDongle/">TeleDongle</a>
units. If possible, use an SMA to BNC adapter instead
of feedline between the antenna feedpoint and
TeleDongle, as this will give you the best
into the USB port on a notebook computer. Because
TeleDongle looks like a simple serial port, your
computer does not require special device
-drivers… just plug it in.</p><p>The GUI tool, AltosUI, is written in Java and runs
-across Linux, Mac OS and Windows. There’s also a suite
+drivers…​ just plug it in.</p>
+</div>
+<div class="paragraph">
+<p>The GUI tool, AltosUI, is written in Java and runs
+across Linux, Mac OS and Windows. There’s also a suite
of C tools for Linux which can perform most of the
-same tasks.</p><p>Alternatively, a TeleBT attached with an SMA to BNC
+same tasks.</p>
+</div>
+<div class="paragraph">
+<p>Alternatively, a TeleBT attached with an SMA to BNC
adapter at the feed point of a hand-held yagi used in
conjunction with an Android device running AltosDroid
-makes an outstanding ground station.</p><p>After the flight,
+makes an outstanding ground station.</p>
+</div>
+<div class="paragraph">
+<p>After the flight,
you can use the radio link to
extract the more detailed data logged in either
TeleMetrum or TeleMini devices, or
you can use a
USB cable to plug into the flight computer board directly.
A USB cable is also how you
-charge the Li-Po battery, so you’ll want one of those
+charge the Li-Po battery, so you’ll want one of those
anyway. The same cable used by lots of digital
cameras and other modern electronic stuff will work
-fine.</p><p>If your rocket lands out of sight, you may enjoy
+fine.</p>
+</div>
+<div class="paragraph">
+<p>If your rocket lands out of sight, you may enjoy
having a hand-held GPS receiver, so that you can put
in a way-point for the last reported rocket position
before touch-down. This makes looking for your rocket
-a lot like Geo-Caching… just go to the way-point and
+a lot like Geo-Caching…​ just go to the way-point and
look around starting from there. AltosDroid on an
Android device with GPS receiver works great for this,
-too!</p><p>You may also enjoy having a ham radio “HT” that covers
-the 70cm band… you can use that with your antenna to
+too!</p>
+</div>
+<div class="paragraph">
+<p>You may also enjoy having a ham radio “HT” that covers
+the 70cm band…​ you can use that with your antenna to
direction-find the rocket on the ground the same way
you can use a Walston or Beeline tracker. This can be
handy if the rocket is hiding in sage brush or a tree,
-or if the last GPS position doesn’t get you close
+or if the last GPS position doesn’t get you close
enough because the rocket dropped into a canyon, or
the wind is blowing it across a dry lake bed, or
-something like that… Keith currently uses a Yaesu
+something like that…​ Keith currently uses a Yaesu
FT1D, Bdale has a Yaesu VX-7R, which is a nicer radio
-in most ways but doesn’t support APRS.</p><p>So, to recap, on the ground the hardware you’ll need includes:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
-an antenna and feed-line or adapter
-</li><li class="listitem">
-a TeleDongle
-</li><li class="listitem">
-a notebook computer
-</li><li class="listitem">
-optionally, a hand-held GPS receiver
-</li><li class="listitem">
-optionally, an HT or receiver covering 435 MHz
-</li></ol></div><p>The best hand-held commercial directional antennas we’ve found for radio
+in most ways but doesn’t support APRS.</p>
+</div>
+<div class="paragraph">
+<p>So, to recap, on the ground the hardware you’ll need includes:</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>an antenna and feed-line or adapter</p>
+</li>
+<li>
+<p>a TeleDongle</p>
+</li>
+<li>
+<p>a notebook computer</p>
+</li>
+<li>
+<p>optionally, a hand-held GPS receiver</p>
+</li>
+<li>
+<p>optionally, an HT or receiver covering 435 MHz</p>
+</li>
+</ol>
+</div>
+<div class="paragraph">
+<p>The best hand-held commercial directional antennas we’ve found for radio
direction finding rockets are from
-<a class="ulink" href="http://www.arrowantennas.com/" target="_top">Arrow Antennas</a>.</p><p>The 440-3 and 440-5 are both good choices for finding
+<a href="http://www.arrowantennas.com/">Arrow Antennas</a>.</p>
+</div>
+<div class="paragraph">
+<p>The 440-3 and 440-5 are both good choices for finding
a TeleMetrum- or TeleMini- equipped rocket when used
with a suitable 70cm HT. TeleDongle and an SMA to BNC
adapter fit perfectly between the driven element and
-reflector of Arrow antennas.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_data_analysis"></a>10.4. Data Analysis</h2></div></div></div><p>Our software makes it easy to log the data from each
+reflector of Arrow antennas.</p>
+</div>
+</div>
+<div class="sect2">
+<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
itself, and the more complete data log recorded in the
flash memory on the altimeter board. Once this data
velocity of the rocket during flight. And you can
even export a flight log in a format usable with Google
Maps and Google Earth for visualizing the flight path
-in two or three dimensions!</p><p>Our ultimate goal is to emit a set of files for each
+in two or three dimensions!</p>
+</div>
+<div class="paragraph">
+<p>Our ultimate goal is to emit a set of files for each
flight that can be published as a web page per flight,
-or just viewed on your local disk with a web browser.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_future_plans"></a>10.5. Future Plans</h2></div></div></div><p>We have designed and prototyped several “companion
+or just viewed on your local disk with a web browser.</p>
+</div>
+</div>
+<div class="sect2">
+<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
TeleMetrum, TeleMega and EasyMega flight computers to
collect more data, provide more pyro channels, and so
If you have specific interests for data collection or
control of events in your rockets beyond the
capabilities of our existing productions, please let
-us know!</p><p>Because all of our work is open, both the hardware
+us know!</p>
+</div>
+<div class="paragraph">
+<p>Because all of our work is open, both the hardware
designs and the software, if you have some great idea
for an addition to the current Altus Metrum family,
feel free to dive in and help! Or let us know what
-you’d like to see that we aren’t already working on,
-and maybe we’ll get excited about it too…</p><p>Watch our <a class="ulink" href="http://altusmetrum.org/" target="_top">web site</a> for
+you’d like to see that we aren’t already working on,
+and maybe we’ll get excited about it too…​</p>
+</div>
+<div class="paragraph">
+<p>Watch our <a href="http://altusmetrum.org/">web site</a> for
more news and information as our family of products
-evolves!</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_altosui"></a>Chapter 11. AltosUI</h1></div></div></div><div class="figure"><a id="idm45058130868928"></a><p class="title"><strong>Figure 11.1. AltosUI Main Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="altosui.png" width="414" alt="altosui.png" /></div></div></div><br class="figure-break" /><p>The AltosUI program provides a graphical user interface for
+evolves!</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<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 9. AltosUI Main Window</div>
+</div>
+<div class="paragraph">
+<p>The AltosUI program provides a graphical user interface for
interacting with the Altus Metrum product family. AltosUI can
monitor telemetry data, configure devices and many other
tasks. The primary interface window provides a selection of
buttons, one for each major activity in the system. This
chapter is split into sections, each of which documents one of
-the tasks provided from the top-level toolbar.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_monitor_flight"></a>11.1. Monitor Flight</h2></div></div></div><p>Selecting this item brings up a dialog box listing all
+the tasks provided from the top-level toolbar.</p>
+</div>
+<div class="sect2">
+<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
one of these, AltosUI will create a window to display
telemetry data as received by the selected TeleDongle
-device.</p><div class="figure"><a id="idm45058130863296"></a><p class="title"><strong>Figure 11.2. Device Selection Dialog</strong></p><div class="figure-contents"><div class="mediaobject"><img src="device-selection.png" width="279" alt="device-selection.png" /></div></div></div><br class="figure-break" /><p>All telemetry data received are automatically recorded
+device.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="device-selection.png" alt="device selection" width="300">
+</div>
+<div class="title">Figure 10. Device Selection Dialog</div>
+</div>
+<div class="paragraph">
+<p>All telemetry data received are automatically recorded
in suitable log files. The name of the files includes
-the current date and rocket serial and flight numbers.</p><p>The radio frequency being monitored by the TeleDongle
+the current date and rocket serial and flight numbers.</p>
+</div>
+<div class="paragraph">
+<p>The radio frequency being monitored by the TeleDongle
device is displayed at the top of the window. You can
configure the frequency by clicking on the frequency
box and selecting the desired frequency. AltosUI
remembers the last frequency selected for each
TeleDongle and selects that automatically the next
-time you use that device.</p><p>Below the TeleDongle frequency selector, the window
+time you use that device.</p>
+</div>
+<div class="paragraph">
+<p>Below the TeleDongle frequency selector, the window
contains a few significant pieces of information about
-the altimeter providing the telemetry data stream:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-The configured call-sign
-</li><li class="listitem">
-The device serial number
-</li><li class="listitem">
-The flight number. Each altimeter remembers how
-many times it has flown.
-</li><li class="listitem">
-The rocket flight state. Each flight passes through
+the altimeter providing the telemetry data stream:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>The configured call-sign</p>
+</li>
+<li>
+<p>The device serial number</p>
+</li>
+<li>
+<p>The flight number. Each altimeter remembers how
+many times it has flown.</p>
+</li>
+<li>
+<p>The rocket flight state. Each flight passes through
several states including Pad, Boost, Fast, Coast,
-Drogue, Main and Landed.
-</li><li class="listitem">
-The Received Signal Strength Indicator value. This
+Drogue, Main and Landed.</p>
+</li>
+<li>
+<p>The Received Signal Strength Indicator value. This
lets you know how strong a signal TeleDongle is
receiving. At the default data rate, 38400 bps, in
bench testing, the radio inside TeleDongle v0.2
environment with radio noise may cause the data to
not be received. The packet link uses error
detection and correction techniques which prevent
-incorrect data from being reported.
-</li><li class="listitem">
-The age of the displayed data, in seconds since the
+incorrect data from being reported.</p>
+</li>
+<li>
+<p>The age of the displayed data, in seconds since the
last successfully received telemetry packet. In
normal operation this will stay in the low single
digits. If the number starts counting up, then you
are no longer receiving data over the radio link
-from the flight computer.
-</li></ul></div><p>Finally, the largest portion of the window contains a
+from the flight computer.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Finally, the largest portion of the window contains a
set of tabs, each of which contain some information
-about the rocket. They’re arranged in <span class="emphasis"><em>flight order</em></span>
+about the rocket. They’re arranged in 'flight order'
so that as the flight progresses, the selected tab
automatically switches to display data relevant to the
current state of the flight. You can select other tabs
-at any time. The final <span class="emphasis"><em>table</em></span> tab displays all of the
+at any time. The final 'table' tab displays all of the
raw telemetry values in one place in a
-spreadsheet-like format.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_launch_pad"></a>11.1.1. Launch Pad</h3></div></div></div><div class="figure"><a id="idm45058130849200"></a><p class="title"><strong>Figure 11.3. Monitor Flight Launch Pad View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="launch-pad.png" width="495" alt="launch-pad.png" /></div></div></div><br class="figure-break" /><p>The <span class="emphasis"><em>Launch Pad</em></span> tab shows information used to decide when the
+spreadsheet-like format.</p>
+</div>
+<div class="sect3">
+<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 11. Monitor Flight Launch Pad View</div>
+</div>
+<div class="paragraph">
+<p>The 'Launch Pad' tab shows information used to decide when the
rocket is ready for flight. The first elements include red/green
-indicators, if any of these is red, you’ll want to evaluate
-whether the rocket is ready to launch:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
-Battery Voltage
-</span></dt><dd>
-This indicates whether the Li-Po battery powering the
+indicators, if any of these is red, you’ll want to evaluate
+whether the rocket is ready to launch:</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">Battery Voltage</dt>
+<dd>
+<p>This indicates whether the Li-Po battery powering the
flight computer has sufficient charge to last for
the duration of the flight. A value of more than
-3.8V is required for a <span class="emphasis"><em>GO</em></span> status.
-</dd><dt><span class="term">
-Apogee Igniter Voltage
-</span></dt><dd>
-This indicates whether the apogee
+3.8V is required for a 'GO' status.</p>
+</dd>
+<dt class="hdlist1">Apogee Igniter Voltage</dt>
+<dd>
+<p>This indicates whether the apogee
igniter has continuity. If the igniter has a low
resistance, then the voltage measured here will be close
to the Li-Po battery voltage. A value greater than 3.2V is
-required for a <span class="emphasis"><em>GO</em></span> status.
-</dd><dt><span class="term">
-Main Igniter Voltage
-</span></dt><dd>
-This indicates whether the main
+required for a 'GO' status.</p>
+</dd>
+<dt class="hdlist1">Main Igniter Voltage</dt>
+<dd>
+<p>This indicates whether the main
igniter has continuity. If the igniter has a low
resistance, then the voltage measured here will be close
to the Li-Po battery voltage. A value greater than 3.2V is
-required for a <span class="emphasis"><em>GO</em></span> status.
-</dd><dt><span class="term">
-On-board Data Logging
-</span></dt><dd>
-This indicates whether there is space remaining
+required for a 'GO' status.</p>
+</dd>
+<dt class="hdlist1">On-board Data Logging</dt>
+<dd>
+<p>This indicates whether there is space remaining
on-board to store flight data for the upcoming
-flight. If you’ve downloaded data, but failed to erase
+flight. If you’ve downloaded data, but failed to erase
flights, there may not be any space left. Most of our
flight computers can store multiple flights, depending
on the configured maximum flight log size. TeleMini
data. This only affects on-board flight logging; the
altimeter will still transmit telemetry and fire
ejection charges at the proper times even if the
-flight data storage is full.
-</dd><dt><span class="term">
-GPS Locked
-</span></dt><dd>
-For a TeleMetrum or TeleMega device, this indicates
+flight data storage is full.</p>
+</dd>
+<dt class="hdlist1">GPS Locked</dt>
+<dd>
+<p>For a TeleMetrum or TeleMega device, this indicates
whether the GPS receiver is currently able to compute
position information. GPS requires at least 4
-satellites to compute an accurate position.
-</dd><dt><span class="term">
-GPS Ready
-</span></dt><dd>
-For a TeleMetrum or TeleMega device, this indicates
+satellites to compute an accurate position.</p>
+</dd>
+<dt class="hdlist1">GPS Ready</dt>
+<dd>
+<p>For a TeleMetrum or TeleMega device, this indicates
whether GPS has reported at least 10 consecutive
positions without losing lock. This ensures that the
GPS receiver has reliable reception from the
-satellites.
-</dd></dl></div><p>The Launchpad tab also shows the computed launch pad
+satellites.</p>
+</dd>
+</dl>
+</div>
+<div class="paragraph">
+<p>The Launchpad tab also shows the computed launch pad
position and altitude, averaging many reported
-positions to improve the accuracy of the fix.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_ascent"></a>11.1.2. Ascent</h3></div></div></div><div class="figure"><a id="idm45058130830016"></a><p class="title"><strong>Figure 11.4. Monitor Flight Ascent View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="ascent.png" width="495" alt="ascent.png" /></div></div></div><br class="figure-break" /><p>This tab is shown during Boost, Fast and Coast
+positions to improve the accuracy of the fix.</p>
+</div>
+</div>
+<div class="sect3">
+<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 12. Monitor Flight Ascent View</div>
+</div>
+<div class="paragraph">
+<p>This tab is shown during Boost, Fast and Coast
phases. The information displayed here helps monitor the
-rocket as it heads towards apogee.</p><p>The height, speed, acceleration and tilt are shown along
+rocket as it heads towards apogee.</p>
+</div>
+<div class="paragraph">
+<p>The height, speed, acceleration and tilt are shown along
with the maximum values for each of them. This allows you to
-quickly answer the most commonly asked questions you’ll hear
-during flight.</p><p>The current latitude and longitude reported by the GPS are
+quickly answer the most commonly asked questions you’ll hear
+during flight.</p>
+</div>
+<div class="paragraph">
+<p>The current latitude and longitude reported by the GPS are
also shown. Note that under high acceleration, these values
may not get updated as the GPS receiver loses position
fix. Once the rocket starts coasting, the receiver should
-start reporting position again.</p><p>Finally, the current igniter voltages are reported as in the
+start reporting position again.</p>
+</div>
+<div class="paragraph">
+<p>Finally, the current igniter voltages are reported as in the
Launch Pad tab. This can help diagnose deployment failures
-caused by wiring which comes loose under high acceleration.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_descent"></a>11.1.3. Descent</h3></div></div></div><div class="figure"><a id="idm45058130823280"></a><p class="title"><strong>Figure 11.5. Monitor Flight Descent View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="descent.png" width="495" alt="descent.png" /></div></div></div><br class="figure-break" /><p>Once the rocket has reached apogee and (we hope)
+caused by wiring which comes loose under high acceleration.</p>
+</div>
+</div>
+<div class="sect3">
+<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 13. Monitor Flight Descent View</div>
+</div>
+<div class="paragraph">
+<p>Once the rocket has reached apogee and (we hope)
activated the apogee charge, attention switches to
tracking the rocket on the way back to the ground, and
for dual-deploy flights, waiting for the main charge
-to fire.</p><p>To monitor whether the apogee charge operated
+to fire.</p>
+</div>
+<div class="paragraph">
+<p>To monitor whether the apogee charge operated
correctly, the current descent rate is reported along
with the current height. Good descent rates vary based
on the choice of recovery components, but generally
range from 15-30m/s on drogue and should be below
10m/s when under the main parachute in a dual-deploy
-flight.</p><p>With GPS-equipped flight computers, you can locate the
+flight.</p>
+</div>
+<div class="paragraph">
+<p>With GPS-equipped flight computers, you can locate the
rocket in the sky using the elevation and bearing
information to figure out where to look. Elevation is
in degrees above the horizon. Bearing is reported in
rocket and can help figure out where the rocket is
likely to land. Note that all of these values are
relative to the pad location. If the elevation is near
-90°, the rocket is over the pad, not over you.</p><p>Finally, the igniter voltages are reported in this tab
+90°, the rocket is over the pad, not over you.</p>
+</div>
+<div class="paragraph">
+<p>Finally, the igniter voltages are reported in this tab
as well, both to monitor the main charge as well as to
see what the status of the apogee charge is. Note
that some commercial e-matches are designed to retain
continuity even after being fired, and will continue
to show as green or return from red to green after
-firing.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_landed"></a>11.1.4. Landed</h3></div></div></div><div class="figure"><a id="idm45058130815168"></a><p class="title"><strong>Figure 11.6. Monitor Flight Landed View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="landed.png" width="495" alt="landed.png" /></div></div></div><br class="figure-break" /><p>Once the rocket is on the ground, attention switches
+firing.</p>
+</div>
+</div>
+<div class="sect3">
+<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 14. Monitor Flight Landed View</div>
+</div>
+<div class="paragraph">
+<p>Once the rocket is on the ground, attention switches
to recovery. While the radio signal is often lost once
the rocket is on the ground, the last reported GPS
position is generally within a short distance of the
-actual landing location.</p><p>The last reported GPS position is reported both by
+actual landing location.</p>
+</div>
+<div class="paragraph">
+<p>The last reported GPS position is reported both by
latitude and longitude as well as a bearing and
distance from the launch pad. The distance should give
you a good idea of whether to walk or hitch a ride.
Take the reported latitude and longitude and enter
them into your hand-held GPS unit and have that
-compute a track to the landing location.</p><p>Our flight computers will continue to transmit RDF
+compute a track to the landing location.</p>
+</div>
+<div class="paragraph">
+<p>Our flight computers will continue to transmit RDF
tones after landing, allowing you to locate the rocket
by following the radio signal if necessary. You may
need to get away from the clutter of the flight line,
-or even get up on a hill (or your neighbor’s RV roof)
-to receive the RDF signal.</p><p>The maximum height, speed and acceleration reported
+or even get up on a hill (or your neighbor’s RV roof)
+to receive the RDF signal.</p>
+</div>
+<div class="paragraph">
+<p>The maximum height, speed and acceleration reported
during the flight are displayed for your admiring
observers. The accuracy of these immediate values
depends on the quality of your radio link and how many
packets were received. Recovering the on-board data
-after flight may yield more precise results.</p><p>To get more detailed information about the flight, you
-can click on the <span class="emphasis"><em>Graph Flight</em></span> button which will
-bring up a graph window for the current flight.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_table"></a>11.1.5. Table</h3></div></div></div><div class="figure"><a id="idm45058130806592"></a><p class="title"><strong>Figure 11.7. Monitor Flight Table View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="table.png" width="495" alt="table.png" /></div></div></div><br class="figure-break" /><p>The table view shows all of the data available from the
+after flight may yield more precise results.</p>
+</div>
+<div class="paragraph">
+<p>To get more detailed information about the flight, you
+can click on the 'Graph Flight' button which will
+bring up a graph window for the current flight.</p>
+</div>
+</div>
+<div class="sect3">
+<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 15. Monitor Flight Table View</div>
+</div>
+<div class="paragraph">
+<p>The table view shows all of the data available from the
flight computer. Probably the most useful data on
this tab is the detailed GPS information, which includes
horizontal dilution of precision information, and
-information about the signal being received from the satellites.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_site_map"></a>11.1.6. Site Map</h3></div></div></div><div class="figure"><a id="idm45058130801760"></a><p class="title"><strong>Figure 11.8. Monitor Flight Site Map View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="site-map.png" width="495" alt="site-map.png" /></div></div></div><br class="figure-break" /><p>When the TeleMetrum has a GPS fix, the Site Map tab
-will map the rocket’s position to make it easier for
+information about the signal being received from the satellites.</p>
+</div>
+</div>
+<div class="sect3">
+<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 16. Monitor Flight Site Map View</div>
+</div>
+<div class="paragraph">
+<p>When the TeleMetrum has a GPS fix, the Site Map tab
+will map the rocket’s position to make it easier for
you to locate the rocket, both while it is in the air,
-and when it has landed. The rocket’s state is
+and when it has landed. The rocket’s state is
indicated by color: 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><p>The map’s default scale is approximately 3m (10ft) per
+dark blue for main, and black for landed.</p>
+</div>
+<div class="paragraph">
+<p>The map’s default scale is approximately 3m (10ft) per
pixel. The map can be dragged using the left mouse
button. The map will attempt to keep the rocket
-roughly centered while data is being received.</p><p>You can adjust the style of map and the zoom level
+roughly centered while data is being received.</p>
+</div>
+<div class="paragraph">
+<p>You can adjust the style of map and the zoom level
with buttons on the right side of the map window. You
can draw a line on the map by moving the mouse over
the map with a button other than the left one pressed,
or by pressing the left button while also holding down
the shift key. The length of the line in real-world
-units will be shown at the start of the line.</p><p>Images are fetched automatically via the Google Maps
+units will be shown at the start of the line.</p>
+</div>
+<div class="paragraph">
+<p>Images are fetched automatically via the Google Maps
Static API, and cached on disk for reuse. If map
-images cannot be downloaded, the rocket’s path will be
-traced on a dark gray background instead.</p><p>You can pre-load images for your favorite launch sites
-before you leave home; check out <a class="xref" href="#_load_maps" title="11.12. Load Maps">Section 11.12, “Load Maps”</a>.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_igniter"></a>11.1.7. Igniter</h3></div></div></div><div class="figure"><a id="idm45058130793680"></a><p class="title"><strong>Figure 11.9. Monitor Flight Additional Igniter View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="ignitor.png" width="495" alt="ignitor.png" /></div></div></div><br class="figure-break" /><p>TeleMega includes four additional programmable pyro
+images cannot be downloaded, the rocket’s path will be
+traced on a dark gray background instead.</p>
+</div>
+<div class="paragraph">
+<p>You can pre-load images for your favorite launch sites
+before you leave home; check out <a href="#_load_maps">Load Maps</a>.</p>
+</div>
+</div>
+<div class="sect3">
+<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 17. Monitor Flight Additional Igniter View</div>
+</div>
+<div class="paragraph">
+<p>TeleMega includes four additional programmable pyro
channels. The Ignitor tab shows whether each of them has
continuity. If an ignitor has a low resistance, then the
voltage measured here will be close to the pyro battery
-voltage. A value greater than 3.2V is required for a <span class="emphasis"><em>GO</em></span>
-status.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_save_flight_data"></a>11.2. Save Flight Data</h2></div></div></div><p>The altimeter records flight data to its internal
+voltage. A value greater than 3.2V is required for a 'GO'
+status.</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<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.
Data logged on board is recorded at a much
higher rate than the telemetry system can handle, and
is not subject to radio drop-outs. As such, it
provides a more complete and precise record of the
flight.
-The <span class="emphasis"><em>Save Flight Data</em></span> button allows you to
-read the flash memory and write it to disk.</p><p>Clicking on the <span class="emphasis"><em>Save Flight Data</em></span> button brings up a
+The 'Save Flight Data' button allows you to
+read the flash memory and write it to disk.</p>
+</div>
+<div class="paragraph">
+<p>Clicking on the 'Save Flight Data' button brings up a
list of connected flight computers and TeleDongle
devices. If you select a flight computer, the flight
data will be downloaded from that device directly.
If you select a TeleDongle device, flight data will be
downloaded from a flight computer over radio link via
the specified TeleDongle. See
-<a class="xref" href="#_controlling_an_altimeter_over_the_radio_link" title="A.3. Controlling An Altimeter Over The Radio Link">Section A.3, “Controlling An Altimeter Over The Radio Link”</a> for
-more information.</p><p>After the device has been selected, a dialog showing
+<a href="#_controlling_an_altimeter_over_the_radio_link">Controlling An Altimeter Over The Radio Link</a> for
+more information.</p>
+</div>
+<div class="paragraph">
+<p>After the device has been selected, a dialog showing
the flight data saved in the device will be shown
allowing you to select which flights to download and
which to delete. With version 0.9 or newer firmware,
accidentally losing flight data if you neglect to
download data before flying again. Note that if there
is no more space available in the device, then no data
-will be recorded during the next flight.</p><p>The file name for each flight log is computed
+will be recorded during the next flight.</p>
+</div>
+<div class="paragraph">
+<p>The file name for each flight log is computed
automatically from the recorded flight date, altimeter
-serial number and flight number information.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_replay_flight"></a>11.3. Replay Flight</h2></div></div></div><p>Select this button and you are prompted to select a flight
+serial number and flight number information.</p>
+</div>
+</div>
+<div class="sect2">
+<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
.eeprom file containing flight data saved from the altimeter
-flash memory.</p><p>Once a flight record is selected, the flight monitor interface
+flash memory.</p>
+</div>
+<div class="paragraph">
+<p>Once a flight record is selected, the flight monitor interface
is displayed and the flight is re-enacted in real
time.
Check
-<a class="xref" href="#_monitor_flight" title="11.1. Monitor Flight">Section 11.1, “Monitor Flight”</a> to learn how this window operates.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_graph_data"></a>11.4. Graph Data</h2></div></div></div><p>Select this button and you are prompted to select a flight
+<a href="#_monitor_flight">Monitor Flight</a> to learn how this window operates.</p>
+</div>
+</div>
+<div class="sect2">
+<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
.eeprom file containing flight data saved from
-flash memory.</p><p>Note that telemetry files will generally produce poor graphs
+flash memory.</p>
+</div>
+<div class="paragraph">
+<p>Note that telemetry files will generally produce poor graphs
due to the lower sampling rate and missed telemetry packets.
-Use saved flight data in .eeprom files for graphing where possible.</p><p>Once a flight record is selected, a window with multiple tabs is
-opened.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_flight_graph"></a>11.4.1. Flight Graph</h3></div></div></div><div class="figure"><a id="idm45058130777360"></a><p class="title"><strong>Figure 11.10. Flight Data Graph</strong></p><div class="figure-contents"><div class="mediaobject"><img src="graph.png" width="495" alt="graph.png" /></div></div></div><br class="figure-break" /><p>By default, the graph contains acceleration (blue),
-velocity (green) and altitude (red).</p><p>The graph can be zoomed into a particular area by
+Use saved flight data in .eeprom files for graphing where possible.</p>
+</div>
+<div class="paragraph">
+<p>Once a flight record is selected, a window with multiple tabs is
+opened.</p>
+</div>
+<div class="sect3">
+<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 18. Flight Data Graph</div>
+</div>
+<div class="paragraph">
+<p>By default, the graph contains acceleration (blue),
+velocity (green) and altitude (red).</p>
+</div>
+<div class="paragraph">
+<p>The graph can be zoomed into a particular area by
clicking and dragging down and to the right. Once
zoomed, the graph can be reset by clicking and
dragging up and to the left. Holding down control and
clicking and dragging allows the graph to be panned.
The right mouse button causes a pop-up menu to be
displayed, giving you the option save or print the
-plot.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_configure_graph"></a>11.4.2. Configure Graph</h3></div></div></div><div class="figure"><a id="idm45058130771968"></a><p class="title"><strong>Figure 11.11. Flight Graph Configuration</strong></p><div class="figure-contents"><div class="mediaobject"><img src="graph-configure.png" width="495" alt="graph-configure.png" /></div></div></div><br class="figure-break" /><p>This selects which graph elements to show, and, at the
-very bottom, lets you switch between metric and
-imperial units</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_flight_statistics"></a>11.4.3. Flight Statistics</h3></div></div></div><div class="figure"><a id="idm45058130767456"></a><p class="title"><strong>Figure 11.12. Flight Statistics</strong></p><div class="figure-contents"><div class="mediaobject"><img src="graph-stats.png" width="495" alt="graph-stats.png" /></div></div></div><br class="figure-break" /><p>Shows overall data computed from the flight.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_map"></a>11.4.4. Map</h3></div></div></div><div class="figure"><a id="idm45058130763168"></a><p class="title"><strong>Figure 11.13. Flight Map</strong></p><div class="figure-contents"><div class="mediaobject"><img src="graph-map.png" width="495" alt="graph-map.png" /></div></div></div><br class="figure-break" /><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></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_export_data"></a>11.5. Export Data</h2></div></div></div><p>This tool takes the raw data files and makes them
+plot.</p>
+</div>
+</div>
+<div class="sect3">
+<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 19. Flight Graph Configuration</div>
+</div>
+<div class="paragraph">
+<p>This selects which graph elements to show, and, at the
+very bottom. It also lets you configure how
+the graph is drawn:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Whether to use metric or imperial units</p>
+</li>
+<li>
+<p>Whether to show a marker at each data
+point. When displaying a small section of
+the graph, these can be useful to know what
+data values were recorded.</p>
+</li>
+<li>
+<p>How wide to draw the lines in the graph</p>
+</li>
+<li>
+<p>How to filter speed and acceleration data
+computed from barometric data. Flight
+computers with accelerometers never display
+computed acceleration data, and only use
+barometric data to compute speed during
+descent. Flight computers without
+accelerometers always compute both speed and
+acceleration from barometric data. A larger
+value smooths the data more.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<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 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">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 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
+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">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
button, you are prompted to select a flight data file,
which can be either a .eeprom or .telem. The .eeprom
which is used to select where to write the resulting
file.
It has a selector to choose between CSV and KML
-file formats.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_comma_separated_value_format"></a>11.5.1. Comma Separated Value Format</h3></div></div></div><p>This is a text file containing the data in a form
+file formats.</p>
+</div>
+<div class="sect3">
+<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
external data analysis tool. The first few lines of
the file contain the version and configuration
information from the altimeter, then there is a single
header line which labels all of the fields. All of
-these lines start with a <span class="emphasis"><em>#</em></span> character which many
-tools can be configured to skip over.</p><p>The remaining lines of the file contain the data, with
+these lines start with a '#' character which many
+tools can be configured to skip over.</p>
+</div>
+<div class="paragraph">
+<p>The remaining lines of the file contain the data, with
each field separated by a comma and at least one
space. All of the sensor values are converted to
standard units, with the barometric data reported in
-both pressure, altitude and height above pad units.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_keyhole_markup_language_for_google_earth"></a>11.5.2. Keyhole Markup Language (for Google Earth)</h3></div></div></div><p>This is the format used by Google Earth to provide an
+both pressure, altitude and height above pad units.</p>
+</div>
+</div>
+<div class="sect3">
+<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
use Google Earth to see the whole flight path
-in 3D.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_configure_altimeter"></a>11.6. Configure Altimeter</h2></div></div></div><div class="figure"><a id="idm45058130751680"></a><p class="title"><strong>Figure 11.14. Altimeter Configuration</strong></p><div class="figure-contents"><div class="mediaobject"><img src="configure-altimeter.png" width="324" alt="configure-altimeter.png" /></div></div></div><br class="figure-break" /><p>Select this button and then select either an altimeter or
+in 3D.</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<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 22. Altimeter Configuration</div>
+</div>
+<div class="paragraph">
+<p>Select this button and then select either an altimeter or
TeleDongle Device from the list provided. Selecting a TeleDongle
device will use the radio link to configure a remote
-altimeter.</p><p>The first few lines of the dialog provide information about the
+altimeter.</p>
+</div>
+<div class="paragraph">
+<p>The first few lines of the dialog provide information about the
connected device, including the product name,
software version and hardware serial number. Below that are the
-individual configuration entries.</p><p>At the bottom of the dialog, there are four buttons:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
-Save
-</span></dt><dd>
-This writes any changes to the configuration parameter
-block in flash memory. If you don’t press this button,
-any changes you make will be lost.
-</dd><dt><span class="term">
-Reset
-</span></dt><dd>
-This resets the dialog to the most recently saved
-values, erasing any changes you have made.
-</dd><dt><span class="term">
-Reboot
-</span></dt><dd>
-This reboots the device. Use this to switch from idle
+individual configuration entries.</p>
+</div>
+<div class="paragraph">
+<p>At the bottom of the dialog, there are four buttons:</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">Save</dt>
+<dd>
+<p>This writes any changes to the configuration parameter
+block in flash memory. If you don’t press this button,
+any changes you make will be lost.</p>
+</dd>
+<dt class="hdlist1">Reset</dt>
+<dd>
+<p>This resets the dialog to the most recently saved
+values, erasing any changes you have made.</p>
+</dd>
+<dt class="hdlist1">Reboot</dt>
+<dd>
+<p>This reboots the device. Use this to switch from idle
to pad mode by rebooting once the rocket is oriented
for flight, or to confirm changes you think you saved
-are really saved.
-</dd><dt><span class="term">
-Close
-</span></dt><dd>
-This closes the dialog. Any unsaved changes will be
-lost.
-</dd></dl></div><p>The rest of the dialog contains the parameters to be configured.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_main_deploy_altitude"></a>11.6.1. Main Deploy Altitude</h3></div></div></div><p>This sets the altitude (above the recorded pad
-altitude) at which the <span class="emphasis"><em>main</em></span> igniter will fire. The
+are really saved.</p>
+</dd>
+<dt class="hdlist1">Close</dt>
+<dd>
+<p>This closes the dialog. Any unsaved changes will be
+lost.</p>
+</dd>
+</dl>
+</div>
+<div class="paragraph">
+<p>The rest of the dialog contains the parameters to be configured.</p>
+</div>
+<div class="sect3">
+<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
drop-down menu shows some common values, but you can
edit the text directly and choose whatever you
like. If the apogee charge fires below this altitude,
then the main charge will fire two seconds after the
-apogee charge fires.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_apogee_delay"></a>11.6.2. Apogee Delay</h3></div></div></div><p>When flying redundant electronics, it’s often
-important to ensure that multiple apogee charges don’t
+apogee charge fires.</p>
+</div>
+</div>
+<div class="sect3">
+<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
fire at precisely the same time, as that can over
pressurize the apogee deployment bay and cause a
structural failure of the air-frame. The Apogee Delay
parameter tells the flight computer to fire the apogee
charge a certain number of seconds after apogee has
-been detected.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_apogee_lockout"></a>11.6.3. Apogee Lockout</h3></div></div></div><p>Apogee lockout is the number of seconds after boost
+been detected.</p>
+</div>
+</div>
+<div class="sect3">
+<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
charge, even if the rocket appears to be at
-apogee. This is often called <span class="emphasis"><em>Mach Delay</em></span>, as it is
+apogee. This is often called 'Mach Delay', as it is
intended to prevent a flight computer from
unintentionally firing apogee charges due to the
pressure spike that occurrs across a mach
transition. Altus Metrum flight computers include a
Kalman filter which is not fooled by this sharp
pressure increase, and so this setting should be left
-at the default value of zero to disable it.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_frequency"></a>11.6.4. Frequency</h3></div></div></div><p>This configures which of the frequencies to use for
+at the default value of zero to disable it.</p>
+</div>
+<div class="admonitionblock warning">
+<table>
+<tr>
+<td class="icon">
+<img src="./images/icons/warning.svg" alt="Warning">
+</td>
+<td class="content">
+Firmware versions older than 1.8.6 have a
+bug which resets the time since launch to zero each
+time a motor starts burning. Update firmware to get
+the correct behavior.
+</td>
+</tr>
+</table>
+</div>
+</div>
+<div class="sect3">
+<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
you set this value via packet command mode, the
TeleDongle frequency will also be automatically
reconfigured to match so that communication will
-continue afterwards.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_rf_calibration"></a>11.6.5. RF Calibration</h3></div></div></div><p>The radios in every Altus Metrum device are calibrated
+continue afterwards.</p>
+</div>
+</div>
+<div class="sect3">
+<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
receive on the specified frequency. If you need to
you can adjust the calibration by changing this value.
Do not do this without understanding what the value
means, read the appendix on calibration and/or the
source code for more information. To change a
-TeleDongle’s calibration, you must reprogram the unit
-completely.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_telemetry_rdf_aprs_enable"></a>11.6.6. Telemetry/RDF/APRS Enable</h3></div></div></div><p>Enables the radio for transmission during
+TeleDongle’s calibration, you must reprogram the unit
+completely.</p>
+</div>
+</div>
+<div class="sect3">
+<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
-transmit anything during flight at all.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_telemetry_baud_rate"></a>11.6.7. Telemetry baud rate</h3></div></div></div><p>This sets the modulation bit rate for data
+transmit anything during flight at all.</p>
+</div>
+</div>
+<div class="sect3">
+<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
link mode. Lower bit rates will increase range
while reducing the amount of data that can be
telemetry is done using a rate 1/2 constraint
4 convolution code, so the actual data
transmission rate is 1/2 of the modulation bit
-rate specified here.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_aprs_interval"></a>11.6.8. APRS Interval</h3></div></div></div><p>How often to transmit GPS information via APRS
+rate specified here.</p>
+</div>
+</div>
+<div class="sect3">
+<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
takes nearly a full second to transmit, so
enabling this option will prevent sending any
-other telemetry during that time.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_aprs_ssid"></a>11.6.9. APRS SSID</h3></div></div></div><p>Which SSID to report in APRS packets. By
+other telemetry during that time.</p>
+</div>
+</div>
+<div class="sect3">
+<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
serial number, but can be configured to any
-value from 0 to 9.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_aprs_format"></a>11.6.10. APRS Format</h3></div></div></div><p>Whether to send APRS data in Compressed or
+value from 0 to 9.</p>
+</div>
+</div>
+<div class="sect3">
+<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
smaller and more precise. Uncompressed
format is older, but may work better with your
altitude information with Uncompressed
format, while the Yaesu FT1D only displays
altitude with Compressed format. Test before
-you fly to see which to use.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_callsign"></a>11.6.11. Callsign</h3></div></div></div><p>This sets the call sign included in each
+you fly to see which to use.</p>
+</div>
+</div>
+<div class="sect3">
+<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
-conform to your local radio regulations.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_maximum_flight_log_size"></a>11.6.12. Maximum Flight Log Size</h3></div></div></div><p>This sets the space (in kilobytes) allocated
+conform to your local radio regulations.</p>
+</div>
+</div>
+<div class="sect3">
+<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
be divided into chunks of this size. A smaller
value will allow more flights to be stored, a
larger value will record data from longer
-flights.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_ignitor_firing_mode"></a>11.6.13. Ignitor Firing Mode</h3></div></div></div><p>This configuration parameter allows the two standard ignitor
+flights.</p>
+</div>
+</div>
+<div class="sect3">
+<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
-configurations.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
-Dual Deploy
-</span></dt><dd>
-This is the usual mode of operation; the
-<span class="emphasis"><em>apogee</em></span> channel is fired at apogee and the
-<span class="emphasis"><em>main</em></span> channel at the height above ground
-specified by the <span class="emphasis"><em>Main Deploy Altitude</em></span> during
-descent.
-</dd><dt><span class="term">
-Redundant Apogee
-</span></dt><dd>
-This fires both channels at apogee, the
-<span class="emphasis"><em>apogee</em></span> channel first followed after a two
-second delay by the <span class="emphasis"><em>main</em></span> channel.
-</dd><dt><span class="term">
-Redundant Main
-</span></dt><dd>
-This fires both channels at the height above
+configurations.</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">Dual Deploy</dt>
+<dd>
+<p>This is the usual mode of operation; the
+'apogee' channel is fired at apogee and the
+'main' channel at the height above ground
+specified by the 'Main Deploy Altitude' during
+descent.</p>
+</dd>
+<dt class="hdlist1">Redundant Apogee</dt>
+<dd>
+<p>This fires both channels at apogee, the
+'apogee' channel first followed after a two
+second delay by the 'main' channel.</p>
+</dd>
+<dt class="hdlist1">Redundant Main</dt>
+<dd>
+<p>This fires both channels at the height above
ground specified by the Main Deploy Altitude
-setting during descent. The <span class="emphasis"><em>apogee</em></span> channel
+setting during descent. The 'apogee' channel
is fired first, followed after a two second
-delay by the <span class="emphasis"><em>main</em></span> channel.
-</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_pad_orientation"></a>11.6.14. Pad Orientation</h3></div></div></div><p>Because they include accelerometers,
+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">12.6.15. Pad Orientation</h4>
+<div class="paragraph">
+<p>Because they include accelerometers,
TeleMetrum, TeleMega and EasyMega are
sensitive to the orientation of the board. By
default, they expect the antenna end to point
forward. This parameter allows that default to
be changed, permitting the board to be mounted
-with the antenna pointing aft instead.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
-Antenna Up
-</span></dt><dd>
-In this mode, the antenna end of the flight
-computer must point forward, in line with the
-expected flight path.
-</dd><dt><span class="term">
-Antenna Down
-</span></dt><dd>
-In this mode, the antenna end of the flight
-computer must point aft, in line with the
-expected flight path.
-</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_beeper_frequency"></a>11.6.15. Beeper Frequency</h3></div></div></div><p>The beeper on all Altus Metrum flight
+with the antenna pointing aft instead.</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">Antenna Up</dt>
+<dd>
+<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 (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">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
have more than one flight computer in a single
airframe, having all of them sound at the same
frequency can be confusing. This parameter
lets you adjust the base beeper frequency
-value.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_logging_trigger_motion"></a>11.6.16. Logging Trigger Motion</h3></div></div></div><p>This sets the amount of motion that TeleGPS
+value.</p>
+</div>
+</div>
+<div class="sect3">
+<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
position. Motions smaller than this are
-skipped, which saves storage space.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_position_reporting_interval"></a>11.6.17. Position Reporting Interval</h3></div></div></div><p>The interval between TeleGPS position reports,
+skipped, which saves storage space.</p>
+</div>
+</div>
+<div class="sect3">
+<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
this to reduce the frequency of radio
transmissions and the length of time available
-in the log.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_configure_pyro_channels"></a>11.6.18. Configure Pyro Channels</h3></div></div></div><div class="figure"><a id="idm45058130694496"></a><p class="title"><strong>Figure 11.15. Additional Pyro Channel Configuration</strong></p><div class="figure-contents"><div class="mediaobject"><img src="configure-pyro.png" width="495" alt="configure-pyro.png" /></div></div></div><br class="figure-break" /><p>This opens a separate window to configure the
-additional pyro channels available on TeleMega
-and EasyMega. One column is presented for
+in the log.</p>
+</div>
+</div>
+<div class="sect3">
+<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
+flight computer with the antenna end, or end opposite
+the screw terminals, in the case of EasyMega, first up
+and then down.</p>
+</div>
+<div class="paragraph">
+<p>When the calibration is complete, return to the
+Configure Altimeter window and save the new
+calibration values.</p>
+</div>
+</div>
+<div class="sect3">
+<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 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,
+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
-fired.</p><p>Select conditions and set the related value;
-the pyro channel will be activated when <span class="strong"><strong>all</strong></span>
+fired.</p>
+</div>
+<div class="paragraph">
+<p>Select conditions and set the related value;
+the pyro channel will be activated when <strong>all</strong>
of the conditions are met. Each pyro channel
has a separate set of configuration values, so
you can use different values for the same
-condition with different channels.</p><p>At the bottom of the window, the <span class="emphasis"><em>Pyro Firing
-Time</em></span> configuration sets the length of time
+condition with different channels.</p>
+</div>
+<div class="paragraph">
+<p>At the bottom of the window, the 'Pyro Firing
+Time' configuration sets the length of time
(in seconds) which each of these pyro channels
-will fire for.</p><p>Once you have selected the appropriate
+will fire for.</p>
+</div>
+<div class="paragraph">
+<p>Once you have selected the appropriate
configuration for all of the necessary pyro
channels, you can save the pyro configuration
along with the rest of the flight computer
-configuration by pressing the <span class="emphasis"><em>Save</em></span> button in
-the main Configure Flight Computer window.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
-Acceleration
-</span></dt><dd>
-Select a value, and then choose
-whether acceleration should be above or below
-that value. Acceleration is positive upwards,
-so accelerating towards the ground would
-produce negative numbers. Acceleration during
-descent is noisy and inaccurate, so be careful
-when using it during these phases of the
-flight.
-</dd><dt><span class="term">
-Vertical speed
-</span></dt><dd>
-Select a value, and then
-choose whether vertical speed should be above
-or below that value. Speed is positive
-upwards, so moving towards the ground would
-produce negative numbers. Speed during descent
-is a bit noisy and so be careful when using it
-during these phases of the flight.
-</dd><dt><span class="term">
-Height
-</span></dt><dd>
-Select a value, and then choose
-whether the height above the launch pad should
-be above or below that value.
-</dd><dt><span class="term">
-Orientation
-</span></dt><dd>
-TeleMega and EasyMega contain a
-3-axis gyroscope and accelerometer which is
-used to measure the current angle. Note that
-this 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 launch
-pad and initialize the system.
-</dd></dl></div><div class="note" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Note</h3><p>Because this value is computed by integrating
+configuration by pressing the 'Save' button in
+the main Configure Flight Computer window.</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">Vertical Acceleration</dt>
+<dd>
+<p>Select a value, and then choose whether
+acceleration away from the ground should be above or below that
+value. Acceleration is positive upwards, so accelerating towards the
+ground would produce negative numbers. Acceleration during descent is
+noisy and inaccurate, so be careful when using it during these phases
+of the flight.</p>
+</dd>
+<dt class="hdlist1">Ascent rate</dt>
+<dd>
+<p>Select a value, and then choose whether ascent rate
+should be above or below that value. Ascent rate is positive upwards,
+so moving towards the ground would produce negative numbers. Ascent
+rate during descent is a bit noisy and so be careful when using it
+during these phases of the flight.</p>
+</dd>
+<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. 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, 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
+launch pad and initialize the system.</p>
+</dd>
+</dl>
+</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<img src="./images/icons/note.svg" alt="Note">
+</td>
+<td class="content">
+<div class="paragraph">
+<p>Because this value is computed by integrating
rate gyros, it gets progressively less
accurate as the flight goes on. It should have
an accumulated error of less than 0.2°/second
(after 10 seconds of flight, the error should
-be less than 2°).</p><p>The usual use of the orientation configuration
+be less than 2°).</p>
+</div>
+<div class="paragraph">
+<p>The usual use of the orientation configuration
is to ensure that the rocket is traveling
mostly upwards when deciding whether to ignite
air starts or additional stages. For that,
choose a reasonable maximum angle (like 20°)
and set the motor igniter to require an angle
-of less than that value.</p></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">
-Flight Time
-</span></dt><dd>
-Time since boost was detected. Select a value and choose
-whether to activate the pyro channel before or after that amount of
-time.
-</dd><dt><span class="term">
-Ascending
-</span></dt><dd>
-A simple test saying whether the rocket is going up or
-not. This is exactly equivalent to testing whether the speed is > 0.
-</dd><dt><span class="term">
-Descending
-</span></dt><dd>
-A simple test saying whether the rocket is going down or
-not. This is exactly equivalent to testing whether the speed is < 0.
-</dd><dt><span class="term">
-After Motor
-</span></dt><dd>
-The flight software counts each time the rocket starts
+of less than that value.</p>
+</div>
+</td>
+</tr>
+</table>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">Flight Time</dt>
+<dd>
+<p>Time since launch. Select a value and choose whether to
+activate the pyro channel before or after that amount of time.</p>
+</dd>
+</dl>
+</div>
+<div class="admonitionblock warning">
+<table>
+<tr>
+<td class="icon">
+<img src="./images/icons/warning.svg" alt="Warning">
+</td>
+<td class="content">
+Firmware versions older than 1.8.6 have a bug which resets the time
+since launch to zero each time a motor starts burning. Update firmware
+to get the correct behavior.
+</td>
+</tr>
+</table>
+</div>
+<div class="admonitionblock warning">
+<table>
+<tr>
+<td class="icon">
+<img src="./images/icons/warning.svg" alt="Warning">
+</td>
+<td class="content">
+Firmware versions older than 1.9.8 cannot use times longer
+than 327.67 seconds. Update firmware if you need a longer time.
+</td>
+</tr>
+</table>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">Ascending</dt>
+<dd>
+<p>A deprecated configuration value which was the same as
+setting Ascent rate > 0. Existing configurations using this will be
+cleared and must be reconfigured by the user.</p>
+</dd>
+<dt class="hdlist1">Descending</dt>
+<dd>
+<p>A deprecated configuration value which was the same as
+setting Ascent rate < 0. Existing configurations using this will be
+cleared and must be reconfigured by the user.</p>
+</dd>
+<dt class="hdlist1">After Motor</dt>
+<dd>
+<p>The flight software counts each time the rocket starts
accelerating and then decelerating (presumably due to a motor or
motors burning). Use this value for multi-staged or multi-airstart
-launches.
-</dd><dt><span class="term">
-Delay
-</span></dt><dd>
-This value doesn’t perform any checks, instead it inserts a
-delay between the time when the other parameters become true and when
-the pyro channel is activated.
-</dd><dt><span class="term">
-Flight State
-</span></dt><dd><p class="simpara">
-The flight software tracks the flight
-through a sequence of states:
-</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Boost. The motor has lit and the rocket is
-accelerating upwards.
-</li><li class="listitem">
-Fast. The motor has burned out and the
+launches. As of version 1.8.6 firmware, this checks to make sure at
+least this many motors have burned. Before version 1.8.6, this checked
+to make sure that exactly this many motors had burned.</p>
+</dd>
+<dt class="hdlist1">Delay</dt>
+<dd>
+<p>Once the other parameters all become true, a timer is
+started for the specified amount of time. While the timer is running,
+the other parameters are checked repeatedly and if any of them become
+false, then the pyro channel is disabled and will not fire. If the
+timer expires and all of the other parameters have remained true for
+the entire time, then the pyro channel is fired.</p>
+</dd>
+</dl>
+</div>
+<div class="admonitionblock warning">
+<table>
+<tr>
+<td class="icon">
+<img src="./images/icons/warning.svg" alt="Warning">
+</td>
+<td class="content">
+Firmware versions older than 1.9.8 cannot use delays longer
+than 327.67 seconds. Update firmware if you need a longer delay.
+</td>
+</tr>
+</table>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">Flight State</dt>
+<dd>
+<p>The flight software tracks the flight
+through a sequence of states:</p>
+<div class="ulist">
+<ul>
+<li>
+<p>Boost. The motor has lit and the rocket is
+accelerating upwards. Ascent rate will be greater than zero.
+Vertical acceleration will be greater than zero.</p>
+</li>
+<li>
+<p>Fast. The motor has burned out and the
rocket is decelerating, but it is going
-faster than 200m/s.
-</li><li class="listitem">
-Coast. The rocket is still moving upwards
-and decelerating, but the speed is less
-than 200m/s.
-</li><li class="listitem">
-Drogue. The rocket has reached apogee and
-is heading back down, but is above the
-configured Main altitude.
-</li><li class="listitem">
-Main. The rocket is still descending, and
-is below the Main altitude
-</li><li class="listitem">
-Landed. The rocket is no longer moving.
-</li></ul></div></dd></dl></div><p>You can select a state to limit when the pyro channel may activate;
-note that the check is based on when the rocket transitions <span class="strong"><strong>into</strong></span> the
+faster than 200m/s. Ascent rate will be greater than zero. Vertical
+acceleration will be less than zero.</p>
+</li>
+<li>
+<p>Coast. The rocket is still moving upwards
+and decelerating, but the Ascent rate is less
+than 200m/s. Ascent rate will greater than zero. Vertical
+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
+acceleration are very noisy in this state, so be careful when
+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
+is below the Main altitude. Ascent rate will be less than zero
+during this state. Vertical acceleration may be briefly less than
+zero as the rocket slows from drogue descent to main descent, but
+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. This state selection is not available on EasyTimer.</p>
+</li>
+<li>
+<p>Landed. The rocket is no longer moving.</p>
+</li>
+</ul>
+</div>
+</dd>
+</dl>
+</div>
+<div class="paragraph">
+<p>You can select a state to limit when the pyro channel may activate;
+note that the check is based on when the rocket transitions <strong>into</strong> the
state, and so checking for “greater than Boost” means that the rocket
-is currently in boost or some later state.</p><p>When a motor burns out, the rocket enters either Fast or Coast state
+is currently in boost or some later state.</p>
+</div>
+<div class="paragraph">
+<p>When a motor burns out, the rocket enters either Fast or Coast state
(depending on how fast it is moving). If the computer detects upwards
-acceleration again, it will move back to Boost state.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_configure_altosui"></a>11.7. Configure AltosUI</h2></div></div></div><div class="figure"><a id="idm45058130656608"></a><p class="title"><strong>Figure 11.16. Configure AltosUI Dialog</strong></p><div class="figure-contents"><div class="mediaobject"><img src="configure-altosui.png" width="216" alt="configure-altosui.png" /></div></div></div><br class="figure-break" /><p>This button presents a dialog so that you can
-configure the AltosUI global settings.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_voice_settings"></a>11.7.1. Voice Settings</h3></div></div></div><p>AltosUI provides voice announcements during
+acceleration again, it will move back to Boost state.</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<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 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">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
sky and still get information about the
current flight status. However, sometimes you
-don’t want to hear them.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
-Enable
-</span></dt><dd>
-Turns all voice announcements on and off
-</dd><dt><span class="term">
-Test Voice
-</span></dt><dd>
-Plays a short message allowing you to verify
+don’t want to hear them.</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">Enable</dt>
+<dd>
+<p>Turns all voice announcements on and off</p>
+</dd>
+<dt class="hdlist1">Test Voice</dt>
+<dd>
+<p>Plays a short message allowing you to verify
that the audio system is working and the volume settings
-are reasonable
-</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_log_directory"></a>11.7.2. Log Directory</h3></div></div></div><p>AltosUI logs all telemetry data and saves all
+are reasonable</p>
+</dd>
+</dl>
+</div>
+</div>
+<div class="sect3">
+<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
directory is also used as the staring point
when selecting data files for display or
-export.</p><p>Click on the directory name to bring up a
+export.</p>
+</div>
+<div class="paragraph">
+<p>Click on the directory name to bring up a
directory choosing dialog, select a new
-directory and click <span class="emphasis"><em>Select Directory</em></span> to
+directory and click 'Select Directory' to
change where AltosUI reads and writes data
-files.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_callsign_2"></a>11.7.3. Callsign</h3></div></div></div><p>This value is transmitted in each command
+files.</p>
+</div>
+</div>
+<div class="sect3">
+<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
an altimeter. It is not used in telemetry
mode, as the callsign configured in the
altimeter board is included in all telemetry
packets. Configure this with the AltosUI
operators call sign as needed to comply with
-your local radio regulations.</p><p>Note that to successfully command a flight
+your local radio regulations.</p>
+</div>
+<div class="paragraph">
+<p>Note that to successfully command a flight
computer over the radio (to configure the
altimeter, monitor idle, or fire pyro
charges), the callsign configured here must
exactly match the callsign configured in the
flight computer. This matching is case
-sensitive.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_imperial_units"></a>11.7.4. Imperial Units</h3></div></div></div><p>This switches between metric units (meters)
+sensitive.</p>
+</div>
+</div>
+<div class="sect3">
+<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
affects the display of values use during
flight monitoring, configuration, data
graphing and all of the voice
announcements. It does not change the units
used when exporting to CSV files, those are
-always produced in metric units.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_serial_debug"></a>11.7.5. Serial Debug</h3></div></div></div><p>This causes all communication with a connected
+always produced in metric units.</p>
+</div>
+</div>
+<div class="sect3">
+<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
-AltosUI was started. If you’ve started it from
+AltosUI was started. If you’ve started it from
an icon or menu entry, the output will simply
be discarded. This mode can be useful to debug
-various serial communication issues.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_font_size"></a>11.7.6. Font size</h3></div></div></div><p>Selects the set of fonts used in the flight
+various serial communication issues.</p>
+</div>
+</div>
+<div class="sect3">
+<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,
-medium and large sets.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_look_amp_feel"></a>11.7.7. Look & feel</h3></div></div></div><p>Switches between the available Java user
+medium and large sets.</p>
+</div>
+</div>
+<div class="sect3">
+<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
is supposed to match the native window system
-appearance for the target platform.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_menu_position"></a>11.7.8. Menu position</h3></div></div></div><p>Selects the initial position for the main
+appearance for the target platform.</p>
+</div>
+</div>
+<div class="sect3">
+<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
-command buttons.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_map_cache_size"></a>11.7.9. Map Cache Size</h3></div></div></div><p>Sets the number of map <span class="emphasis"><em>tiles</em></span> kept in memory
+command buttons.</p>
+</div>
+</div>
+<div class="sect3">
+<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
consume more memory, but will make panning
-around the map faster.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_manage_frequencies"></a>11.7.10. Manage Frequencies</h3></div></div></div><p>This brings up a dialog where you can
+around the map faster.</p>
+</div>
+</div>
+<div class="sect3">
+<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
various frequency menus. You can add as many
as you like, or even reconfigure the default
set. Changing this list does not affect the
frequency settings of any devices, it only
changes the set of frequencies shown in the
-menus.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_configure_groundstation"></a>11.8. Configure Groundstation</h2></div></div></div><div class="figure"><a id="idm45058130628688"></a><p class="title"><strong>Figure 11.17. Configure Groundstation Dialog</strong></p><div class="figure-contents"><div class="mediaobject"><img src="configure-groundstation.png" width="279" alt="configure-groundstation.png" /></div></div></div><br class="figure-break" /><p>Select this button and then select a TeleDongle or
-TeleBT Device from the list provided.</p><p>The first few lines of the dialog provide information
+menus.</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<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 25. Configure Groundstation Dialog</div>
+</div>
+<div class="paragraph">
+<p>Select this button and then select a TeleDongle or
+TeleBT Device from the list provided.</p>
+</div>
+<div class="paragraph">
+<p>The first few lines of the dialog provide information
about the connected device, including the product
name, software version and hardware serial
number. Below that are the individual configuration
-entries.</p><p>Note that TeleDongle and TeleBT don’t save any
+entries.</p>
+</div>
+<div class="paragraph">
+<p>Note that TeleDongle and TeleBT don’t save any
configuration data, the settings here are recorded on
the local machine in the Java preferences
database. Moving the device to another machine, or
using a different user account on the same machine
-will cause settings made here to have no effect.</p><p>At the bottom of the dialog, there are three
-buttons:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
-Save
-</span></dt><dd>
-This writes any changes to the local Java
-preferences file. If you don’t press this
-button, any changes you make will be lost.
-</dd><dt><span class="term">
-Reset
-</span></dt><dd>
-This resets the dialog to the most recently
+will cause settings made here to have no effect.</p>
+</div>
+<div class="paragraph">
+<p>At the bottom of the dialog, there are three
+buttons:</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">Save</dt>
+<dd>
+<p>This writes any changes to the local Java
+preferences file. If you don’t press this
+button, any changes you make will be lost.</p>
+</dd>
+<dt class="hdlist1">Reset</dt>
+<dd>
+<p>This resets the dialog to the most recently
saved values, erasing any changes you have
-made.
-</dd><dt><span class="term">
-Close
-</span></dt><dd>
-This closes the dialog. Any unsaved changes
-will be lost.
-</dd></dl></div><p>The rest of the dialog contains the parameters
-to be configured.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_frequency_2"></a>11.8.1. Frequency</h3></div></div></div><p>This configures the frequency to use for both
+made.</p>
+</dd>
+<dt class="hdlist1">Close</dt>
+<dd>
+<p>This closes the dialog. Any unsaved changes
+will be lost.</p>
+</dd>
+</dl>
+</div>
+<div class="paragraph">
+<p>The rest of the dialog contains the parameters
+to be configured.</p>
+</div>
+<div class="sect3">
+<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
before starting any operation involving packet
command mode so that it will use the right
frequency. Telemetry monitoring mode also
provides a menu to change the frequency, and
that menu also sets the same Java preference
-value used here.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_rf_calibration_2"></a>11.8.2. RF Calibration</h3></div></div></div><p>The radios in every Altus Metrum device are
+value used here.</p>
+</div>
+</div>
+<div class="sect3">
+<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
transmit and receive on the specified
-frequency. To change a TeleDongle or TeleBT’s
+frequency. To change a TeleDongle or TeleBT’s
calibration, you must reprogram the unit
completely, so this entry simply shows the
-current value and doesn’t allow any changes.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_telemetry_rate"></a>11.8.3. Telemetry Rate</h3></div></div></div><p>This lets you match the telemetry and packet
-link rate from the transmitter. If they don’t
-match, the device won’t receive any data.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_flash_image"></a>11.9. Flash Image</h2></div></div></div><p>This reprograms Altus Metrum devices with new
+current value and doesn’t allow any changes.</p>
+</div>
+</div>
+<div class="sect3">
+<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
+match, the device won’t receive any data.</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_flash_image">12.9. Flash Image</h3>
+<div class="paragraph">
+<p>This reprograms Altus Metrum devices with new
firmware.
-TeleMetrum v1.x, TeleDongle v0.2, TeleMini
-and TeleBT are all reprogrammed by using another
+TeleMetrum v1.x, TeleDongle v0.2, TeleMini v1.0
+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
-<a class="xref" href="#_updating_device_firmware" title="Appendix C. Updating Device Firmware">Appendix C, <em>Updating Device Firmware</em></a>.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_fire_igniter"></a>11.10. Fire Igniter</h2></div></div></div><div class="figure"><a id="idm45058130608144"></a><p class="title"><strong>Figure 11.18. Fire Igniter Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="fire-igniter.png" width="108" alt="fire-igniter.png" /></div></div></div><br class="figure-break" /><p>This activates the igniter circuits in the flight
+<a href="#_updating_device_firmware">Updating Device Firmware</a>.</p>
+</div>
+</div>
+<div class="sect2">
+<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 26. Fire Igniter Window</div>
+</div>
+<div class="paragraph">
+<p>This activates the igniter circuits in the flight
computer to help test recovery systems
deployment.
Because this command can operate over the
Packet Command Link, you can prepare the rocket as for
flight and then test the recovery system without
-needing to snake wires inside the air-frame.</p><p>Selecting the <span class="emphasis"><em>Fire Igniter</em></span> button brings up the
+needing to snake wires inside the air-frame.</p>
+</div>
+<div class="paragraph">
+<p>Selecting the 'Fire Igniter' button brings up the
usual device selection dialog. Pick the desired
device. This brings up another window which shows the
current continuity test status for all of the pyro
-channels.</p><p>Next, select the desired igniter to fire. This will
-enable the <span class="emphasis"><em>Arm</em></span> button.</p><p>Select the <span class="emphasis"><em>Arm</em></span> button. This enables the <span class="emphasis"><em>Fire</em></span>
-button. The word <span class="emphasis"><em>Arm</em></span> is replaced by a countdown
+channels.</p>
+</div>
+<div class="paragraph">
+<p>Next, select the desired igniter to fire. This will
+enable the 'Arm' button.</p>
+</div>
+<div class="paragraph">
+<p>Select the 'Arm' button. This enables the 'Fire'
+button. The word 'Arm' is replaced by a countdown
timer indicating that you have 10 seconds to press the
-<span class="emphasis"><em>Fire</em></span> button or the system will deactivate, at which
+'Fire' button or the system will deactivate, at which
point you start over again at selecting the desired
-igniter.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_scan_channels"></a>11.11. Scan Channels</h2></div></div></div><div class="figure"><a id="idm45058130598992"></a><p class="title"><strong>Figure 11.19. Scan Channels Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="scan-channels.png" width="288" alt="scan-channels.png" /></div></div></div><br class="figure-break" /><p>This listens for telemetry packets on all of the
+igniter.</p>
+</div>
+</div>
+<div class="sect2">
+<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 27. Scan Channels Window</div>
+</div>
+<div class="paragraph">
+<p>This listens for telemetry packets on all of the
configured frequencies, displaying information about
each device it receives a packet from. You can select
which of the baud rates and telemetry formats should
be tried; by default, it only listens at 38400 baud
with the standard telemetry format used in v1.0 and
-later firmware.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_load_maps"></a>11.12. Load Maps</h2></div></div></div><div class="figure"><a id="idm45058130594176"></a><p class="title"><strong>Figure 11.20. Load Maps Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="load-maps.png" width="468" alt="load-maps.png" /></div></div></div><br class="figure-break" /><p>Before heading out to a new launch site, you can use
-this to load satellite images in case you don’t have
-internet connectivity at the site.</p><p>There’s a drop-down menu of launch sites we know
-about; if your favorites aren’t there, please let us
+later firmware.</p>
+</div>
+</div>
+<div class="sect2">
+<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 28. Load Maps Window</div>
+</div>
+<div class="paragraph">
+<p>Before heading out to a new launch site, you can use
+this to load satellite images in case you don’t have
+internet connectivity at the site. Try not to wait
+until the last minute, though, particularly if you’re
+heading to a major launch. If too many people are
+all trying to download map data at once, Google may
+limit access until the next day.</p>
+</div>
+<div class="paragraph">
+<p>There’s a drop-down menu of launch sites we know
+about; if your favorites aren’t there, please let us
know the lat/lon and name of the site. The contents of
this list are actually downloaded from our server at
-run-time, so as new sites are sent in, they’ll get
+run-time, so as new sites are sent in, they’ll get
automatically added to this list. If the launch site
-isn’t in the list, you can manually enter the lat/lon
-values</p><p>There are four different kinds of maps you can view;
+isn’t in the list, you can manually enter the lat/lon
+values</p>
+</div>
+<div class="paragraph">
+<p>There are four different kinds of maps you can view;
you can select which to download by selecting as many
-as you like from the available types:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
-Hybrid
-</span></dt><dd>
-A combination of satellite imagery and road data. This
-is the default view.
-</dd><dt><span class="term">
-Satellite
-</span></dt><dd>
-Just the satellite imagery without any annotation.
-</dd><dt><span class="term">
-Roadmap
-</span></dt><dd>
-Roads, political boundaries and a few geographic
-features.
-</dd><dt><span class="term">
-Terrain
-</span></dt><dd>
-Contour intervals and shading that show hills and
-valleys.
-</dd></dl></div><p>You can specify the range of zoom levels to download;
+as you like from the available types:</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">Hybrid</dt>
+<dd>
+<p>A combination of satellite imagery and road data. This
+is the default view.</p>
+</dd>
+<dt class="hdlist1">Satellite</dt>
+<dd>
+<p>Just the satellite imagery without any annotation.</p>
+</dd>
+<dt class="hdlist1">Roadmap</dt>
+<dd>
+<p>Roads, political boundaries and a few geographic
+features.</p>
+</dd>
+<dt class="hdlist1">Terrain</dt>
+<dd>
+<p>Contour intervals and shading that show hills and
+valleys.</p>
+</dd>
+</dl>
+</div>
+<div class="paragraph">
+<p>You can specify the range of zoom levels to download;
smaller numbers show more area with less
resolution. The default level, 0, shows about
3m/pixel. One zoom level change doubles or halves that
number. Larger zoom levels show more detail, smaller
-zoom levels less.</p><p>The Map Radius value sets how large an area around the
+zoom levels less.</p>
+</div>
+<div class="paragraph">
+<p>The Map Radius value sets how large an area around the
center point to download. Select a value large enough
to cover any plausible flight from that site. Be aware
that loading a large area with a high maximum zoom
hybrid maps with a 10km radius at a minimum zoom of -2
and a maximum zoom of 2 consumes about 120MB of
space. Terrain and road maps consume about 1/10 as
-much space as satellite or hybrid maps.</p><p>Clicking the <span class="emphasis"><em>Load Map</em></span> button will fetch images from
+much space as satellite or hybrid maps.</p>
+</div>
+<div class="paragraph">
+<p>Clicking the 'Load Map' button will fetch images from
Google Maps; note that Google limits how many images
you can fetch at once, so if you load more than one
launch site, you may get some gray areas in the map
which indicate that Google is tired of sending data to
-you. Try again later.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_monitor_idle"></a>11.13. Monitor Idle</h2></div></div></div><div class="figure"><a id="idm45058130577728"></a><p class="title"><strong>Figure 11.21. Monitor Idle Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="monitor-idle.png" width="468" alt="monitor-idle.png" /></div></div></div><br class="figure-break" /><p>This brings up a dialog similar to the Monitor Flight
+you. Try again later.</p>
+</div>
+</div>
+<div class="sect2">
+<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 29. Monitor Idle Window</div>
+</div>
+<div class="paragraph">
+<p>This brings up a dialog similar to the Monitor Flight
UI, except it works with the altimeter in “idle” mode
by sending query commands to discover the current
state rather than listening for telemetry
packets. Because this uses command mode, it needs to
have the TeleDongle and flight computer callsigns
match exactly. If you can receive telemetry, but
-cannot manage to run Monitor Idle, then it’s very
-likely that your callsigns are different in some way.</p><p>You can change the frequency and callsign used to
+cannot manage to run Monitor Idle, then it’s very
+likely that your callsigns are different in some way.</p>
+</div>
+<div class="paragraph">
+<p>You can change the frequency and callsign used to
communicate with the flight computer; they must both
match the configuration in the flight computer
-exactly.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_altosdroid"></a>Chapter 12. AltosDroid</h1></div></div></div><p>AltosDroid provides the same flight monitoring capabilities as
+exactly.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_altosdroid">13. AltosDroid</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>AltosDroid provides the same flight monitoring capabilities as
AltosUI, but runs on Android devices. AltosDroid is designed
to connect to a TeleBT receiver over Bluetooth™ and (on
Android devices supporting USB On-the-go) TeleDongle and
TeleBT devices over USB. AltosDroid monitors telemetry data,
logging it to internal storage in the Android device, and
-presents that data in a UI similar to the <span class="emphasis"><em>Monitor Flight</em></span>
-window in AltosUI.</p><p>This manual will explain how to configure AltosDroid, connect
+presents that data in a UI similar to the 'Monitor Flight'
+window in AltosUI.</p>
+</div>
+<div class="paragraph">
+<p>This manual will explain how to configure AltosDroid, connect
to TeleBT or TeleDongle, operate the flight monitoring
-interface and describe what the displayed data means.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_installing_altosdroid"></a>12.1. Installing AltosDroid</h2></div></div></div><p>AltosDroid is available from the Google Play store. To
+interface and describe what the displayed data means.</p>
+</div>
+<div class="sect2">
+<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
Play Store application and search for
-“altosdroid”. Make sure you don’t have a space between
-“altos” and “droid” or you probably won’t find what
+“altosdroid”. Make sure you don’t have a space between
+“altos” and “droid” or you probably won’t find what
you want. That should bring you to the right page from
-which you can download and install the application.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_charging_telebt_battery"></a>12.2. Charging TeleBT Battery</h2></div></div></div><p>Before using TeleBT with AltosDroid, make sure the
+which you can download and install the application.</p>
+</div>
+</div>
+<div class="sect2">
+<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,
attach a micro USB cable from a computer or other USB
power source to TeleBT. A dual LED on the circuit
board should illuminate, showing red while the battery
is charging, green when charging is completed, and
both red and green on at the same time if there is a
-battery fault.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_connecting_to_telebt_over_bluetooth"></a>12.3. Connecting to TeleBT over Bluetooth™</h2></div></div></div><p>Press the Android <span class="emphasis"><em>Menu</em></span> button or soft-key to see the
-configuration options available. Select the <span class="emphasis"><em>Connect a
-device</em></span> option and then the <span class="emphasis"><em>Scan for devices</em></span> entry
+battery fault.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_connecting_to_telebt_over_bluetooth">13.3. Connecting to TeleBT over Bluetooth™</h3>
+<div class="paragraph">
+<p>Note that when turning TeleBT on, you may see a brief LED
+flash, but there will be no "activity" indicated until you
+pair with the device from AltosDroid.</p>
+</div>
+<div class="paragraph">
+<p>Press the Android 'Menu' button or soft-key to see the
+configuration options available. Select the 'Connect a
+device' option and then the 'Scan for devices' entry
at the bottom to look for your TeleBT device. Select
your device, and when it asks for the code, enter
-<span class="emphasis"><em>1234</em></span>.</p><p>Subsequent connections will not require you to enter
-that code, and your <span class="emphasis"><em>paired</em></span> device will appear in the
-list without scanning.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_connecting_to_teledongle_or_telebt_over_usb"></a>12.4. Connecting to TeleDongle or TeleBT over USB</h2></div></div></div><p>Get a special USB On-the-go adapter cable. These
+'1234'.</p>
+</div>
+<div class="paragraph">
+<p>Subsequent connections will not require you to enter
+that code, and your 'paired' device will appear in the
+list without scanning.</p>
+</div>
+</div>
+<div class="sect2">
+<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
and a standard A female connector on the other
end. Plug in your TeleDongle or TeleBT device to the
adapter cable and the adapter cable into your phone
and AltosDroid should automatically start up. If it
-doesn’t, the most likely reason is that your Android
-device doesn’t support USB On-the-go.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_configuring_altosdroid"></a>12.5. Configuring AltosDroid</h2></div></div></div><p>There are several configuration and operation
-parameters available in the AltosDroid menu.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
-Select radio frequency
-</span></dt><dd>
-This selects which frequency to listen on by bringing
+doesn’t, the most likely reason is that your Android
+device doesn’t support USB On-the-go.</p>
+</div>
+</div>
+<div class="sect2">
+<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 class="dlist">
+<dl>
+<dt class="hdlist1">Connect a device</dt>
+<dd>
+<p>Offers a menu of available TeleBT devices, and an
+option to scan for additional devices.</p>
+</dd>
+<dt class="hdlist1">Disconnect device</dt>
+<dd>
+<p>Disconnects the current TeleBT or TeleDongle
+device. You can reconnect TeleBT over bluetooth by
+using Connect a Device. You can reconnect a USB device
+by unplugging it and then plugging it back in.</p>
+</dd>
+<dt class="hdlist1">Select radio frequency</dt>
+<dd>
+<p>This selects which frequency to listen on by bringing
up a menu of pre-set radio frequencies. Pick the one
-which matches your altimeter.
-</dd><dt><span class="term">
-Select data rate
-</span></dt><dd>
-Altus Metrum transmitters can be configured to operate
+which matches your altimeter.</p>
+</dd>
+<dt class="hdlist1">Select Tracker</dt>
+<dd>
+<p>Switches the information displays to show data for a
+different transmitting device. The map will always
+show all of the devices in view. Trackers are shown
+and selected by serial number, so make sure you note
+the serial number of devices in each airframe.</p>
+</dd>
+<dt class="hdlist1">Delete Track</dt>
+<dd>
+<p>Deletes all information about a transmitting device.</p>
+</dd>
+<dt class="hdlist1">Setup</dt>
+<dd>
+<p>Offers additional configuration operations. See
+<a href="#_setup">Setup</a>.</p>
+</dd>
+<dt class="hdlist1">Idle Mode</dt>
+<dd>
+<p>Communicate with an altimeter in Idle mode. See <a href="#_idle_mode">Idle Mode</a></p>
+</dd>
+<dt class="hdlist1">Quit</dt>
+<dd>
+<p>Shuts down AltosDroid.</p>
+</dd>
+</dl>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_setup">13.6. Setup</h3>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">Telemetry Rate</dt>
+<dd>
+<p>Altus Metrum transmitters can be configured to operate
at lower data rates to improve transmission range. If
you have configured your device to do this, this menu
-item allows you to change the receiver to match.
-</dd><dt><span class="term">
-Change units
-</span></dt><dd>
-This toggles between metric and imperial units.
-</dd><dt><span class="term">
-Load maps
-</span></dt><dd>
-Brings up a dialog allowing you to download offline
-map tiles so that you can have maps available even if
-you have no network connectivity at the launch site.
-</dd><dt><span class="term">
-Map type
-</span></dt><dd>
-Displays a menu of map types and lets you select
+item allows you to change the receiver to match.</p>
+</dd>
+<dt class="hdlist1">Units</dt>
+<dd>
+<p>Selects which units used to report values.</p>
+</dd>
+<dt class="hdlist1">Map Type</dt>
+<dd>
+<p>Displays a menu of map types and lets you select
one. Hybrid maps include satellite images with a
roadmap overlaid. Satellite maps dispense with the
roadmap overlay. Roadmap shows just the roads. Terrain
includes roads along with shadows indicating changes
-in elevation, and other geographical features.
-</dd><dt><span class="term">
-Toggle Online/Offline maps
-</span></dt><dd>
-Switches between online and offline maps. Online maps
-will show a <span class="emphasis"><em>move to current position</em></span> icon in the
+in elevation, and other geographical features.</p>
+</dd>
+<dt class="hdlist1">Map Source</dt>
+<dd>
+<p>Select between online and offline maps. Online maps
+will show a 'move to current position' icon in the
upper right corner, while offline maps will have
copyright information all over the map. Otherwise,
-they’re pretty similar.
-</dd><dt><span class="term">
-Select Tracker
-</span></dt><dd>
-Switches the information displays to show data for a
-different transmitting device. The map will always
-show all of the devices in view. Trackers are shown
-and selected by serial number, so make sure you note
-the serial number of devices in each airframe.
-</dd><dt><span class="term">
-Delete Track
-</span></dt><dd>
-Deletes all information about a transmitting device.
-</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosdroid_flight_monitoring"></a>12.6. AltosDroid Flight Monitoring</h2></div></div></div><p>AltosDroid is designed to mimic the AltosUI flight
+they’re pretty similar.</p>
+</dd>
+<dt class="hdlist1">Preload Maps</dt>
+<dd>
+<p>Brings up a dialog allowing you to download offline
+map tiles so that you can have maps available even if
+you have no network connectivity at the launch site.</p>
+</dd>
+<dt class="hdlist1">Manage Frequencies</dt>
+<dd>
+<p>This presents a dialog containing the current list of
+frequencies that will be show in the 'Select radio
+frequency' menu. You can change the label for existing
+frequencies, delete or add new frequencies.</p>
+</dd>
+</dl>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_idle_mode">13.7. Idle Mode</h3>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">Callsign</dt>
+<dd>
+<p>Lets you configure the callsign used by AltosDroid to
+communicate with the flight computer. The callsign on
+the two devices must match or the communication will
+fail. This provides a modest amount of protection
+against accidentally controlling another persons
+flight computer.</p>
+</dd>
+<dt class="hdlist1">Monitor</dt>
+<dd>
+<p>This provides similar information to monitoring the
+telemetry stream from a flight computer in flight
+mode. The title of the application will change to
+include (idle) so you can tell this mode is active.</p>
+</dd>
+<dt class="hdlist1">Reboot</dt>
+<dd>
+<p>Remotely reboots the flight computer. This is useful
+when the flight computers turned on while the airframe
+is horizontal and you want to restart the flight
+computers in pad mode after raising the airframe to
+vertical.</p>
+</dd>
+<dt class="hdlist1">Fire Igniters</dt>
+<dd>
+<p>Remotely control igniters for ground testing recovery
+systems.</p>
+</dd>
+</dl>
+</div>
+</div>
+<div class="sect2">
+<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
stage of your rocket flight along with a tab
containing a map of the local area with icons marking
the current location of the altimeter and the Android
-device.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_pad"></a>12.7. Pad</h2></div></div></div><p>The <span class="emphasis"><em>Pad</em></span> tab shows information used to decide when
+device.</p>
+</div>
+</div>
+<div class="sect2">
+<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
include red/green indicators, if any of these is red,
-you’ll want to evaluate whether the rocket is ready to
-launch.</p><p>When the pad tab is selected, the voice responses will
+you’ll want to evaluate whether the rocket is ready to
+launch.</p>
+</div>
+<div class="paragraph">
+<p>When the pad tab is selected, the voice responses will
include status changes to the igniters and GPS
reception, letting you know if the rocket is still
-ready for launch.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
-Battery
-</span></dt><dd>
-This indicates whether the Li-Po battery powering the
+ready for launch.</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">Battery</dt>
+<dd>
+<p>This indicates whether the Li-Po battery powering the
transmitter has sufficient charge to last for the
duration of the flight. A value of more than 3.8V is
-required for a <span class="emphasis"><em>GO</em></span> status.
-</dd><dt><span class="term">
-Receiver Battery
-</span></dt><dd>
-This indicates whether the Li-Po battery powering the
+required for a 'GO' status.</p>
+</dd>
+<dt class="hdlist1">Receiver Battery</dt>
+<dd>
+<p>This indicates whether the Li-Po battery powering the
TeleBT has sufficient charge to last for the duration
of the flight. A value of more than 3.8V is required
-for a <span class="emphasis"><em>GO</em></span> status.
-</dd><dt><span class="term">
-Data Logging
-</span></dt><dd>
-This indicates whether there is space remaining
+for a 'GO' status.</p>
+</dd>
+<dt class="hdlist1">Data Logging</dt>
+<dd>
+<p>This indicates whether there is space remaining
on-board to store flight data for the upcoming
-flight. If you’ve downloaded data, but failed to erase
+flight. If you’ve downloaded data, but failed to erase
flights, there may not be any space left. TeleMetrum
and TeleMega can store multiple flights, depending on
the configured maximum flight log size. TeleGPS logs
-data continuously. TeleMini stores only a single
+data continuously. TeleMini v1.0 stores only a single
flight, so it will need to be downloaded and erased
after each flight to capture data. This only affects
on-board flight logging; the altimeter will still
transmit telemetry and fire ejection charges at the
-proper times.
-</dd><dt><span class="term">
-GPS Locked
-</span></dt><dd>
-For a TeleMetrum or TeleMega device, this indicates
+proper times.</p>
+</dd>
+<dt class="hdlist1">GPS Locked</dt>
+<dd>
+<p>For a TeleMetrum or TeleMega device, this indicates
whether the GPS receiver is currently able to compute
position information. GPS requires at least 4
-satellites to compute an accurate position.
-</dd><dt><span class="term">
-GPS Ready
-</span></dt><dd>
-For a TeleMetrum or TeleMega device, this indicates
+satellites to compute an accurate position.</p>
+</dd>
+<dt class="hdlist1">GPS Ready</dt>
+<dd>
+<p>For a TeleMetrum or TeleMega device, this indicates
whether GPS has reported at least 10 consecutive
positions without losing lock. This ensures that the
GPS receiver has reliable reception from the
-satellites.
-</dd><dt><span class="term">
-Apogee Igniter
-</span></dt><dd>
-This indicates whether the apogee igniter has
+satellites.</p>
+</dd>
+<dt class="hdlist1">Apogee Igniter</dt>
+<dd>
+<p>This indicates whether the apogee igniter has
continuity. If the igniter has a low resistance, then
the voltage measured here will be close to the Li-Po
battery voltage. A value greater than 3.2V is required
-for a <span class="emphasis"><em>GO</em></span> status.
-</dd><dt><span class="term">
-Main Igniter
-</span></dt><dd>
-This indicates whether the main igniter has
+for a 'GO' status.</p>
+</dd>
+<dt class="hdlist1">Main Igniter</dt>
+<dd>
+<p>This indicates whether the main igniter has
continuity. If the igniter has a low resistance, then
the voltage measured here will be close to the Li-Po
battery voltage. A value greater than 3.2V is required
-for a <span class="emphasis"><em>GO</em></span> status.
-</dd><dt><span class="term">
-Igniter A-D
-</span></dt><dd>
-This indicates whether the indicated additional pyro
+for a 'GO' status.</p>
+</dd>
+<dt class="hdlist1">Igniter A-D</dt>
+<dd>
+<p>This indicates whether the indicated additional pyro
channel igniter has continuity. If the igniter has a
low resistance, then the voltage measured here will be
close to the Li-Po battery voltage. A value greater
-than 3.2V is required for a <span class="emphasis"><em>GO</em></span> status.
-</dd></dl></div><p>The Pad tab also shows the location of the Android
-device.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_flight"></a>12.8. Flight</h2></div></div></div><p>The <span class="emphasis"><em>Flight</em></span> tab shows information used to evaluate
+than 3.2V is required for a 'GO' status.</p>
+</dd>
+</dl>
+</div>
+<div class="paragraph">
+<p>The Pad tab also shows the location of the Android
+device.</p>
+</div>
+</div>
+<div class="sect2">
+<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
and height data to monitor the health of the rocket,
along with elevation, range and bearing to help locate
-the rocket in the sky.</p><p>While the Flight tab is displayed, the voice
+the rocket in the sky.</p>
+</div>
+<div class="paragraph">
+<p>While the Flight tab is displayed, the voice
announcements will include current speed, height,
-elevation and bearing information.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
-Speed
-</span></dt><dd>
-Shows current vertical speed. During descent, the
+elevation and bearing information.</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">Speed</dt>
+<dd>
+<p>Shows current vertical speed. During descent, the
speed values are averaged over a fairly long time to
-try and make them steadier.
-</dd><dt><span class="term">
-Height
-</span></dt><dd>
-Shows the current height above the launch pad.
-</dd><dt><span class="term">
-Max Speed
-</span></dt><dd>
-Shows the maximum vertical speed seen during the
-flight.
-</dd><dt><span class="term">
-Max Height
-</span></dt><dd>
-Shows the maximum height above launch pad.
-</dd><dt><span class="term">
-Elevation
-</span></dt><dd>
-This is the angle above the horizon from the android
-devices current position.
-</dd><dt><span class="term">
-Range
-</span></dt><dd>
-The total distance from the android device to the
+try and make them steadier.</p>
+</dd>
+<dt class="hdlist1">Height</dt>
+<dd>
+<p>Shows the current height above the launch pad.</p>
+</dd>
+<dt class="hdlist1">Max Speed</dt>
+<dd>
+<p>Shows the maximum vertical speed seen during the
+flight.</p>
+</dd>
+<dt class="hdlist1">Max Height</dt>
+<dd>
+<p>Shows the maximum height above launch pad.</p>
+</dd>
+<dt class="hdlist1">Elevation</dt>
+<dd>
+<p>This is the angle above the horizon from the android
+devices current position.</p>
+</dd>
+<dt class="hdlist1">Range</dt>
+<dd>
+<p>The total distance from the android device to the
rocket, including both ground distance and difference
in altitude. Use this to gauge how large the rocket is
-likely to appear in the sky.
-</dd><dt><span class="term">
-Bearing
-</span></dt><dd>
-This is the aziumuth from true north for the rocket
+likely to appear in the sky.</p>
+</dd>
+<dt class="hdlist1">Bearing</dt>
+<dd>
+<p>This is the azimuth from true north for the rocket
from the android device. Use this in combination with
the Elevation value to help locate the rocket in the
sky, or at least to help point the antenna in the
general direction. This is provided in both degrees
-and a compass point (like West South West). You’ll
+and a compass point (like West South West). You’ll
want to know which direction is true north before
-launching your rocket.
-</dd><dt><span class="term">
-Ground Distance
-</span></dt><dd>
-This shows the distance across the ground to the
+launching your rocket.</p>
+</dd>
+<dt class="hdlist1">Ground Distance</dt>
+<dd>
+<p>This shows the distance across the ground to the
lat/lon where the rocket is located. Use this to
-estimate what is currently under the rocket.
-</dd><dt><span class="term">
-Latitude/Longitude
-</span></dt><dd>
-Displays the last known location of the rocket.
-</dd><dt><span class="term">
-Apogee Igniter
-</span></dt><dd>
-This indicates whether the apogee igniter has
+estimate what is currently under the rocket.</p>
+</dd>
+<dt class="hdlist1">Latitude/Longitude</dt>
+<dd>
+<p>Displays the last known location of the rocket.</p>
+</dd>
+<dt class="hdlist1">Apogee Igniter</dt>
+<dd>
+<p>This indicates whether the apogee igniter has
continuity. If the igniter has a low resistance, then
the voltage measured here will be close to the Li-Po
battery voltage. A value greater than 3.2V is required
-for a <span class="emphasis"><em>GO</em></span> status.
-</dd><dt><span class="term">
-Main Igniter
-</span></dt><dd>
-This indicates whether the main igniter has
+for a 'GO' status.</p>
+</dd>
+<dt class="hdlist1">Main Igniter</dt>
+<dd>
+<p>This indicates whether the main igniter has
continuity. If the igniter has a low resistance, then
the voltage measured here will be close to the Li-Po
battery voltage. A value greater than 3.2V is required
-for a <span class="emphasis"><em>GO</em></span> status.
-</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_recover"></a>12.9. Recover</h2></div></div></div><p>The <span class="emphasis"><em>Recover</em></span> tab shows information used while
-recovering the rocket on the ground after flight.</p><p>While the Recover tab is displayed, the voice
+for a 'GO' status.</p>
+</dd>
+</dl>
+</div>
+</div>
+<div class="sect2">
+<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 class="paragraph">
+<p>While the Recover tab is displayed, the voice
announcements will include distance along with either
bearing or direction, depending on whether you are
-moving.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
-Bearing
-</span></dt><dd>
-This is the aziumuth from true north for the rocket
+moving.</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">Bearing</dt>
+<dd>
+<p>This is the azimuth from true north for the rocket
from the android device. Use this in combination with
the Elevation value to help locate the rocket in the
sky, or at least to help point the antenna in the
general direction. This is provided in both degrees
-and a compass point (like West South West). You’ll
+and a compass point (like West South West). You’ll
want to know which direction is true north before
-launching your rocket.
-</dd><dt><span class="term">
-Direction
-</span></dt><dd>
-When you are in motion, this provides the angle from
-your current direction of motion towards the rocket.
-</dd><dt><span class="term">
-Distance
-</span></dt><dd>
-Distance over the ground to the rocket.
-</dd><dt><span class="term">
-Tar Lat/Tar Lon
-</span></dt><dd>
-Displays the last known location of the rocket.
-</dd><dt><span class="term">
-My Lat/My Lon
-</span></dt><dd>
-Displays the location of the Android device.
-</dd><dt><span class="term">
-Max Height
-</span></dt><dd>
-Shows the maximum height above launch pad.
-</dd><dt><span class="term">
-Max Speed
-</span></dt><dd>
-Shows the maximum vertical speed seen during the
-flight.
-</dd><dt><span class="term">
-Max Accel
-</span></dt><dd>
-Shows the maximum vertical acceleration seen during
-the flight.
-</dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_map_2"></a>12.10. Map</h2></div></div></div><p>The <span class="emphasis"><em>Map</em></span> tab shows a map of the area around the
+launching your rocket.</p>
+</dd>
+<dt class="hdlist1">Direction</dt>
+<dd>
+<p>When you are in motion, this provides the angle from
+your current direction of motion towards the rocket.</p>
+</dd>
+<dt class="hdlist1">Distance</dt>
+<dd>
+<p>Distance over the ground to the rocket.</p>
+</dd>
+<dt class="hdlist1">Tar Lat/Tar Lon</dt>
+<dd>
+<p>Displays the last known location of the rocket.</p>
+</dd>
+<dt class="hdlist1">My Lat/My Lon</dt>
+<dd>
+<p>Displays the location of the Android device.</p>
+</dd>
+<dt class="hdlist1">Max Height</dt>
+<dd>
+<p>Shows the maximum height above launch pad seen during
+the flight.</p>
+</dd>
+<dt class="hdlist1">Max Speed</dt>
+<dd>
+<p>Shows the maximum vertical speed seen during the
+flight.</p>
+</dd>
+<dt class="hdlist1">Max Accel</dt>
+<dd>
+<p>Shows the maximum vertical acceleration seen during
+the flight.</p>
+</dd>
+</dl>
+</div>
+</div>
+<div class="sect2">
+<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
-recover it.</p><p>On the map itself, icons showing the location of the
+recover it.</p>
+</div>
+<div class="paragraph">
+<p>On the map itself, icons showing the location of the
android device along with the last known location of
each tracker. A blue line is drawn from the android
-device location to the currently selected tracker.</p><p>Below the map, the distance and either bearing or
+device location to the currently selected tracker.</p>
+</div>
+<div class="paragraph">
+<p>Below the map, the distance and either bearing or
direction along with the lat/lon of the target and the
-android device are shown</p><p>The Map tab provides the same voice announcements as
-the Recover tab.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_downloading_flight_logs"></a>12.11. Downloading Flight Logs</h2></div></div></div><p>AltosDroid always saves every bit of telemetry data it
+android device are shown</p>
+</div>
+<div class="paragraph">
+<p>The Map tab provides the same voice announcements as
+the Recover tab.</p>
+</div>
+</div>
+<div class="sect2">
+<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
AltosUI, remove the SD card from your Android device,
-or connect your device to your computer’s USB port and
+or connect your device to your computer’s USB port and
browse the files on that device. You will find
-<span class="emphasis"><em>.telem</em></span> files in the TeleMetrum directory that will
-work with AltosUI directly.</p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_system_operation"></a>Appendix A. System Operation</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_firmware_modes"></a>A.1. Firmware Modes</h2></div></div></div><p>The AltOS firmware build for the altimeters has two
+'.telem' files in the TeleMetrum directory that will
+work with AltosUI directly.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_system_operation">Appendix A: System Operation</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="_firmware_modes">A.1. Firmware Modes</h3>
+<div class="paragraph">
+<p>The AltOS firmware build for the altimeters has two
fundamental modes, “idle” and “flight”. Which of these modes
the firmware operates in is determined at start up
time.
For
-TeleMetrum, 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
+rocket (well, actually the board, of course…​) at the time
power is switched on. If the rocket is “nose up”, then
-the flight computer assumes it’s on a rail or rod being prepared for
+the flight computer assumes it’s on a rail or rod being prepared for
launch, so the firmware chooses flight mode. However, if the
rocket is more or less horizontal, the firmware instead enters
idle mode.
Since
-EasyMini doesn’t
+EasyMini doesn’t
have an
accelerometer we can use to determine orientation, “idle” mode
is selected if the board is connected via USB to a computer,
otherwise the board enters “flight” mode.
-TeleMini v1.0
-selects “idle” mode if it receives a command packet within the
-first five seconds of operation.</p><p>At power on, the altimeter will beep out the battery voltage
+TeleMini
+selects “idle” mode if it receives a command packet
+within the
+first five seconds of operation.</p>
+</div>
+<div class="paragraph">
+<p>At power on, the altimeter will beep out the battery voltage
to the nearest tenth of a volt. Each digit is represented by
a sequence of short “dit” beeps, with a pause between
digits. A zero digit is represented with one long “dah”
beep. Then there will be a short pause while the altimeter
completes initialization and self test, and decides which mode
-to enter next.</p><p>In flight or “pad” mode, the altimeter engages the flight
+to enter next.</p>
+</div>
+<div class="paragraph">
+<p>In flight or “pad” mode, the altimeter engages the flight
state machine, goes into transmit-only mode to send telemetry,
and waits for launch to be detected. Flight mode is indicated
by an “di-dah-dah-dit” (“P” for pad) on the beeper or lights,
three beeps/flashes indicate both apogee and main continuity,
and one longer “brap” sound which is made by rapidly
alternating between two tones indicates no continuity. For a
-dual deploy flight, make sure you’re getting three beeps or
+dual deploy flight, make sure you’re getting three beeps or
flashes before launching! For apogee-only or motor eject
-flights, do what makes sense.</p><p>If idle mode is entered, you will hear an audible “di-dit” or
+flights, do what makes sense.</p>
+</div>
+<div class="paragraph">
+<p>If idle mode is entered, you will hear an audible “di-dit” or
see two short flashes (“I” for idle), and the flight state
machine is disengaged, thus no ejection charges will fire.
The altimeters also listen for the radio link when in idle
mode for requests sent via TeleDongle. Commands can be issued
in idle mode over either USB or the radio link
equivalently.
-TeleMini v1.0 only has the radio link.
+TeleMini only has the radio link.
Idle mode is useful for configuring the altimeter, for
extracting data from the on-board storage chip after
-flight, and for ground testing pyro charges.</p><p>In “Idle” and “Pad” modes, once the mode indication
+flight, and for ground testing pyro charges.</p>
+</div>
+<div class="paragraph">
+<p>In “Idle” and “Pad” modes, once the mode indication
beeps/flashes and continuity indication has been sent, if
there is no space available to log the flight in on-board
memory, the flight computer will emit a warbling tone (much
-slower than the “no continuity tone”)</p><p>See <a class="xref" href="#_understanding_beeps" title="3.5. Understanding Beeps">Section 3.5, “Understanding Beeps”</a> for a summary of all of
-the audio signals used.</p><p>Once landed, the flight computer will signal that by emitting
+slower than the “no continuity tone”)</p>
+</div>
+<div class="paragraph">
+<p>See <a href="#_understanding_beeps">Understanding Beeps</a> for a summary of all of
+the audio signals used.</p>
+</div>
+<div class="paragraph">
+<p>Once landed, the flight computer will signal that by emitting
the “Landed” sound described above, after which it will beep
out the apogee height (in meters). Each digit is represented
by a sequence of short “dit” beeps, with a pause between
digits. A zero digit is represented with one long “dah”
beep. The flight computer will continue to report landed mode
-and beep out the maximum height until turned off.</p><p>One “neat trick” of particular value when TeleMetrum, TeleMega
+and beep out the maximum height until turned off.</p>
+</div>
+<div class="paragraph">
+<p>One “neat trick” of particular value when TeleMetrum, TeleMega
or EasyMega are used with
very large air-frames, is that you can power the board up while the
rocket is horizontal, such that it comes up in idle mode. Then you can
-raise the air-frame to launch position, and issue a <span class="emphasis"><em>reset</em></span> command
+raise the air-frame to launch position, and issue a 'reset' command
via TeleDongle over the radio link to cause the altimeter to reboot and
come up in flight mode. This is much safer than standing on the top
step of a rickety step-ladder or hanging off the side of a launch
tower with a screw-driver trying to turn on your avionics before
-installing igniters!</p><p>TeleMini v1.0 is configured solely via the radio link. Of course, that
+installing igniters!</p>
+</div>
+<div class="paragraph">
+<p>TeleMini is configured solely via the radio link. Of course, that
means you need to know the TeleMini radio configuration values
-or you won’t be able to communicate with it. For situations
-when you don’t have the radio configuration values, TeleMini v1.0
-offers an <span class="emphasis"><em>emergency recovery</em></span> mode. In this mode, TeleMini is
-configured as follows:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Sets the radio frequency to 434.550MHz
-</li><li class="listitem">
-Sets the radio calibration back to the factory value.
-</li><li class="listitem">
-Sets the callsign to N0CALL
-</li><li class="listitem">
-Does not go to <span class="emphasis"><em>pad</em></span> mode after five seconds.
-</li></ul></div><p>To get into <span class="emphasis"><em>emergency recovery</em></span> mode, first find the row of
+or you won’t be able to communicate with it. For situations
+when you don’t have the radio configuration values,
+TeleMini v1.0
+offers an 'emergency recovery' mode. In this mode,
+TeleMini v1.0 is
+configured as follows:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Sets the radio frequency to 434.550MHz</p>
+</li>
+<li>
+<p>Sets the radio calibration back to the factory value.</p>
+</li>
+<li>
+<p>Sets the callsign to N0CALL</p>
+</li>
+<li>
+<p>Does not go to 'pad' mode after five seconds.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>To get into 'emergency recovery' mode, first find the row of
four small holes opposite the switch wiring. Using a short
piece of small gauge wire, connect the outer two holes
together, then power TeleMini up. Once the red LED is lit,
-disconnect the wire and the board should signal that it’s in
-<span class="emphasis"><em>idle</em></span> mode after the initial five second startup
-period.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_gps"></a>A.2. GPS</h2></div></div></div><p>TeleMetrum and TeleMega include a complete GPS receiver. A
+disconnect the wire and the board should signal that it’s in
+'idle' mode after the initial five second startup
+period.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_gps">A.2. GPS</h3>
+<div class="paragraph">
+<p>TeleMetrum and TeleMega include a complete GPS receiver. A
complete explanation of how GPS works is beyond the scope of
this manual, but the bottom line is that the GPS receiver
needs to lock onto at least four satellites to obtain a solid
-3 dimensional position fix and know what time it is.</p><p>The flight computers provide backup power to the GPS chip any time a
+3 dimensional position fix and know what time it is.</p>
+</div>
+<div class="paragraph">
+<p>The flight computers provide backup power to the GPS chip any time a
battery is connected. This allows the receiver to “warm start” on
the launch rail much faster than if every power-on were a GPS
“cold start”. In typical operations, powering up
RSO review and installation on a launch rod or rail. When the board
is turned back on, the GPS system should lock very quickly, typically
long before igniter installation and return to the flight line are
-complete.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_controlling_an_altimeter_over_the_radio_link"></a>A.3. Controlling An Altimeter Over The Radio Link</h2></div></div></div><p>One of the unique features of the Altus Metrum system is the
+complete.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_controlling_an_altimeter_over_the_radio_link">A.3. Controlling An Altimeter Over The Radio Link</h3>
+<div class="paragraph">
+<p>One of the unique features of the Altus Metrum system is the
ability to create a two way command link between TeleDongle
and an altimeter using the digital radio transceivers
built into each device. This allows you to interact with the
altimeter from afar, as if it were directly connected to the
-computer.</p><p>Any operation which can be performed with a flight computer can
+computer.</p>
+</div>
+<div class="paragraph">
+<p>Any operation which can be performed with a flight computer can
either be done with the device directly connected to the
computer via the USB cable, or through the radio
-link. TeleMini v1.0 doesn’t provide a USB connector and so it is
+link. TeleMini doesn’t provide a USB connector and so it is
always communicated with over radio. Select the appropriate
TeleDongle device when the list of devices is presented and
-AltosUI will interact with an altimeter over the radio link.</p><p>One oddity in the current interface is how AltosUI selects the
+AltosUI will interact with an altimeter over the radio link.</p>
+</div>
+<div class="paragraph">
+<p>One oddity in the current interface is how AltosUI selects the
frequency for radio communications. Instead of providing
an interface to specifically configure the frequency, it uses
whatever frequency was most recently selected for the target
-TeleDongle device in Monitor Flight mode. If you haven’t ever
+TeleDongle device in Monitor Flight mode. If you haven’t ever
used that mode with the TeleDongle in question, select the
Monitor Flight button from the top level UI, and pick the
appropriate TeleDongle device. Once the flight monitoring
window is open, select the desired frequency and then close it
-down again. All radio communications will now use that frequency.</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Save Flight Data—Recover flight data from the
-rocket without opening it up.
-</li><li class="listitem">
-Configure altimeter apogee delays, main deploy
+down again. All radio communications will now use that frequency.</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Save Flight Data—Recover flight data from the
+rocket without opening it up.</p>
+</li>
+<li>
+<p>Configure altimeter apogee delays, main deploy
heights and additional pyro event conditions to
respond to changing launch conditions. You can also
-<span class="emphasis"><em>reboot</em></span> the altimeter. Use this to remotely enable
+'reboot' the altimeter. Use this to remotely enable
the flight computer by turning TeleMetrum or
TeleMega on in “idle” mode, then once the air-frame
is oriented for launch, you can reboot the
altimeter and have it restart in pad mode without
-having to climb the scary ladder.
-</li><li class="listitem">
-Fire Igniters—Test your deployment charges without snaking
+having to climb the scary ladder.</p>
+</li>
+<li>
+<p>Fire Igniters—Test your deployment charges without snaking
wires out through holes in the air-frame. Simply assemble the
rocket as if for flight with the apogee and main charges
loaded, then remotely command the altimeter to fire the
-igniters.
-</li></ul></div><p>Operation over the radio link for configuring an
+igniters.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Operation over the radio link for configuring an
altimeter, ground testing igniters, and so forth uses
the same RF frequencies as flight telemetry. To
configure the desired TeleDongle frequency, select the
monitor flight tab, then use the frequency selector
and close the window before performing other desired
-radio operations.</p><p>The flight computers only enable radio commanding in
-<span class="emphasis"><em>idle</em></span> mode. TeleMetrum and TeleMega use the
+radio operations.</p>
+</div>
+<div class="paragraph">
+<p>The flight computers only enable radio commanding in
+'idle' mode. TeleMetrum and TeleMega use the
accelerometer to detect which orientation they start
up in, so make sure you have the flight computer lying
horizontally when you turn it on. Otherwise, it will
-start in <span class="emphasis"><em>pad</em></span> mode ready for flight, and will not be
-listening for command packets from TeleDongle.</p><p>TeleMini listens for a command packet for five seconds
-after first being turned on, if it doesn’t hear
-anything, it enters <span class="emphasis"><em>pad</em></span> mode, ready for flight and
+start in 'pad' mode ready for flight, and will not be
+listening for command packets from TeleDongle.</p>
+</div>
+<div class="paragraph">
+<p>TeleMini listens for a command packet for five seconds
+after first being turned on, if it doesn’t hear
+anything, it enters 'pad' mode, ready for flight and
will no longer listen for command packets. The easiest
way to connect to TeleMini is to initiate the command
and select the TeleDongle device. At this point, the
TeleDongle will be attempting to communicate with the
TeleMini. Now turn TeleMini on, and it should
immediately start communicating with the TeleDongle
-and the desired operation can be performed.</p><p>You can monitor the operation of the radio link by watching the
+and the desired operation can be performed.</p>
+</div>
+<div class="paragraph">
+<p>You can monitor the operation of the radio link by watching the
lights on the devices. The red LED will flash each time a packet
is transmitted, while the green LED will light up on TeleDongle when
-it is waiting to receive a packet from the altimeter.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_ground_testing"></a>A.4. Ground Testing</h2></div></div></div><p>An important aspect of preparing a rocket using electronic deployment
+it is waiting to receive a packet from the altimeter.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_ground_testing">A.4. Ground Testing</h3>
+<div class="paragraph">
+<p>An important aspect of preparing a rocket using electronic deployment
for flight is ground testing the recovery system.
Thanks
to the bi-directional radio link central to the Altus Metrum system,
this can be accomplished in a TeleMega, TeleMetrum or TeleMini equipped rocket
with less work than you may be accustomed to with other systems. It
-can even be fun!</p><p>Just prep the rocket for flight, then power up the altimeter
+can even be fun!</p>
+</div>
+<div class="paragraph">
+<p>Just prep the rocket for flight, then power up the altimeter
in “idle”
mode (placing air-frame horizontal for TeleMetrum or TeleMega, or
selecting the Configure Altimeter tab for TeleMini).
manual command.
You can now command the altimeter to fire the apogee
or main charges from a safe distance using your
-computer and the Fire Igniter tab to complete ejection testing.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_radio_link"></a>A.5. Radio Link</h2></div></div></div><p>TeleMetrum, TeleMini and TeleMega all incorporate an
-RF transceiver, but it’s not a full duplex system;
+computer and the Fire Igniter tab to complete ejection testing.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_radio_link">A.5. Radio Link</h3>
+<div class="paragraph">
+<p>TeleMetrum, TeleMini and TeleMega all incorporate an
+RF transceiver, but it’s not a full duplex system;
each end can only be transmitting or receiving at any
given moment. So we had to decide how to manage the
-link.</p><p>By design, the altimeter firmware listens for the
-radio link when it’s in “idle mode”, which allows us
+link.</p>
+</div>
+<div class="paragraph">
+<p>By design, the altimeter firmware listens for the
+radio link when it’s in “idle mode”, which allows us
to use the radio link to configure the rocket, do
things like ejection tests, and extract data after a
flight without having to crack open the air-frame.
However, when the board is in “flight mode”, the
-altimeter only transmits and doesn’t listen at all.
-That’s because we want to put ultimate priority on
+altimeter only transmits and doesn’t listen at all.
+That’s because we want to put ultimate priority on
event detection and getting telemetry out of the
rocket through the radio in case the rocket crashes
-and we aren’t able to extract data later.</p><p>We don’t generally use a <span class="emphasis"><em>normal packet radio</em></span> mode
-like APRS because they’re just too inefficient. The
+and we aren’t able to extract data later.</p>
+</div>
+<div class="paragraph">
+<p>We don’t generally use a 'normal packet radio' mode
+like APRS because they’re just too inefficient. The
GFSK modulation we use is FSK with the base-band
pulses passed through a Gaussian filter before they go
into the modulator to limit the transmitted bandwidth.
interleaving, this allows us to have a very robust
19.2 kilobit data link with only 10-40 milliwatts of
transmit power, a whip antenna in the rocket, and a
-hand-held Yagi on the ground. We’ve had flights to
+hand-held Yagi on the ground. We’ve had flights to
above 21k feet AGL with great reception, and
calculations suggest we should be good to well over
40k feet AGL with a 5-element yagi on the ground with
our 10mW units and over 100k feet AGL with the 40mW
devices. We hope to fly boards to higher altitudes
over time, and would of course appreciate customer
-feedback on performance in higher altitude flights!</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_aprs"></a>A.6. APRS</h2></div></div></div><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 class="xref" href="#_configure_altimeter" title="11.6. Configure Altimeter">Section 11.6, “Configure Altimeter”</a>.</p><p>AltOS supports both compressed and uncompressed APRS
+feedback on performance in higher altitude flights!</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_aprs">A.6. APRS</h3>
+<div class="paragraph">
+<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
position report data formats. The compressed format
provides for higher position precision and shorter
-packets than the uncompressed APRS format. We’ve found
+packets than the uncompressed APRS format. We’ve found
some older APRS receivers that do not handle the
compressed format. The Kenwood TH-72A requires the use
of uncompressed format to display altitude information
correctly. The Yaesu FT1D requires the use of
-compressed format to display altitude information.</p><p>APRS packets include an SSID (Secondary Station Identifier)
+compressed format to display altitude information.</p>
+</div>
+<div class="paragraph">
+<p>APRS packets include an SSID (Secondary Station Identifier)
field that allows one operator to have multiple
transmitters. AltOS allows you to set this to a single digit
from 0 to 9, allowing you to fly multiple transmitters at the
same time while keeping the identify of each one separate in
the receiver. By default, the SSID is set to the last digit of
-the device serial number.</p><p>The APRS packet format includes a comment field that
+the device serial number.</p>
+</div>
+<div class="paragraph">
+<p>The APRS packet format includes a comment field that
can have arbitrary text in it. AltOS uses this to send
-status information as shown in the following table.</p><div class="table"><a id="idm45058130419360"></a><p class="title"><strong>Table A.1. Altus Metrum APRS Comments</strong></p><div class="table-contents"><table summary="Altus Metrum APRS Comments" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Field </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Example </th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>L</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>GPS Status U for unlocked, L for locked</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>6</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Number of Satellites in View</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B4.0</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Altimeter Battery Voltage</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A3.7</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee Igniter Voltage</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>5</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>M3.7</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main Igniter Voltage</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>6</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1286</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Device Serial Number</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>4</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>1286</p></td><td style="" align="left" valign="top"><p>Device Serial Number</p></td></tr></tbody></table></div></div><br class="table-break" /><p>Here’s an example of an APRS comment showing GPS lock with 6
+status information as shown in the following table.</p>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<caption class="title">Table 10. Altus Metrum APRS Comments</caption>
+<colgroup>
+<col style="width: 20%;">
+<col style="width: 20%;">
+<col style="width: 60%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Field</th>
+<th class="tableblock halign-left valign-top">Example</th>
+<th class="tableblock halign-left valign-top">Description</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">1</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">L</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">GPS Status U for unlocked, L for locked</p></td>
+</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">6</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Number of Satellites in View</p></td>
+</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">B4.0</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Altimeter Battery Voltage</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">A3.7</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee Igniter Voltage</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">M3.7</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Main Igniter Voltage</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">6</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">1286</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Device Serial Number</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">1286</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Device Serial Number</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>Here’s an example of an APRS comment showing GPS lock with 6
satellites in view, a primary battery at 4.0V, and
-apogee and main igniters both at 3.7V from device 1286.</p><pre class="literallayout">L6 B4.0 A3.7 M3.7 1286</pre><p>Here’s an example of an APRS comment showing GPS lock with 6
-satellites in view and a primary battery at 4.0V from device 1876.</p><pre class="literallayout">L6 B4.0 1876</pre><p>Make sure your primary battery is above 3.8V
+apogee and main igniters both at 3.7V from device 1286.</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>L6 B4.0 A3.7 M3.7 1286</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Here’s an example of an APRS comment showing GPS lock with 6
+satellites in view and a primary battery at 4.0V from device 1876.</p>
+</div>
+<div class="literalblock">
+<div class="content">
+<pre>L6 B4.0 1876</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Make sure your primary battery is above 3.8V
any connected igniters are above 3.5V
and GPS is locked with at least 5 or 6 satellites in
view before flying. If GPS is switching between L and
-U regularly, then it doesn’t have a good lock and you
-should wait until it becomes stable.</p><p>If the GPS receiver loses lock, the APRS data
+U regularly, then it doesn’t have a good lock and you
+should wait until it becomes stable.</p>
+</div>
+<div class="paragraph">
+<p>If the GPS receiver loses lock, the APRS data
transmitted will contain the last position for which
GPS lock was available. You can tell that this has
happened by noticing that the GPS status character
-switches from <span class="emphasis"><em>L</em></span> to <span class="emphasis"><em>U</em></span>. Before GPS has locked, APRS
+switches from 'L' to 'U'. Before GPS has locked, APRS
will transmit zero for latitude, longitude and
-altitude.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_configurable_parameters"></a>A.7. Configurable Parameters</h2></div></div></div><p>Configuring an Altus Metrum altimeter for flight is
+altitude.</p>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_configurable_parameters">A.7. Configurable Parameters</h3>
+<div class="paragraph">
+<p>Configuring an Altus Metrum altimeter for flight is
very simple. Even on our baro-only TeleMini and
EasyMini boards, the use of a Kalman filter means
there is no need to set a “mach delay”. All of the
configurable parameters can be set using AltosUI. Read
-<a class="xref" href="#_configure_altimeter" title="11.6. Configure Altimeter">Section 11.6, “Configure Altimeter”</a> for more information.</p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_handling_precautions"></a>Appendix B. Handling Precautions</h1></div></div></div><p>All Altus Metrum products are sophisticated electronic devices.
+<a href="#_configure_altimeter">Configure Altimeter</a> for more information.</p>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_handling_precautions">Appendix B: Handling Precautions</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>All Altus Metrum products are sophisticated electronic devices.
When handled gently and properly installed in an air-frame, they
will deliver impressive results. However, as with all electronic
-devices, there are some precautions you must take.</p><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>The Lithium Polymer rechargeable batteries have an
+devices, there are some precautions you must take.</p>
+</div>
+<div class="admonitionblock warning">
+<table>
+<tr>
+<td class="icon">
+<img src="./images/icons/warning.svg" alt="Warning">
+</td>
+<td class="content">
+The Lithium Polymer rechargeable batteries have an
extraordinary power density. This is great because we can fly with
much less battery mass than if we used alkaline batteries or previous
-generation rechargeable batteries… but if they are punctured
+generation rechargeable batteries…​ but if they are punctured
or their leads are allowed to short, they can and will release their
energy very rapidly!
Thus we recommend that you take some care when handling our batteries
and consider giving them some extra protection in your air-frame. We
often wrap them in suitable scraps of closed-cell packing foam before
-strapping them down, for example.</p></div><p>The barometric sensors used on all of our flight computers are
+strapping them down, for example.
+</td>
+</tr>
+</table>
+</div>
+<div class="paragraph">
+<p>The barometric sensors used on all of our flight computers are
sensitive to sunlight. In normal mounting situations, the baro sensor
and all of the other surface mount components
are “down” towards whatever the underlying mounting surface is, so
use clear plastic for the payload bay! Replacing these with an opaque
cardboard tube, painting them, or wrapping them with a layer of masking
tape are all reasonable approaches to keep the sensor out of direct
-sunlight.</p><p>The barometric sensor sampling port must be able to “breathe”,
+sunlight.</p>
+</div>
+<div class="paragraph">
+<p>The barometric sensor sampling port must be able to “breathe”,
both by not being covered by foam or tape or other materials that might
directly block the hole on the top of the sensor, and also by having a
-suitable static vent to outside air.</p><p>As with all other rocketry electronics, Altus Metrum altimeters must
+suitable static vent to outside air.</p>
+</div>
+<div class="paragraph">
+<p>As with all other rocketry electronics, Altus Metrum altimeters must
be protected from exposure to corrosive motor exhaust and ejection
-charge gasses.</p></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_updating_device_firmware"></a>Appendix C. Updating Device Firmware</h1></div></div></div><p>TeleMega, TeleMetrum v2, EasyMega, EasyMini and TeleDongle v3
+charge gasses.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_updating_device_firmware">Appendix C: Updating Device Firmware</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>TeleMega, TeleMetrum v2 and newer, EasyMega, EasyMini and TeleDongle v3
are all
programmed directly over their USB connectors (self
programming).
-TeleMetrum v1, TeleMini and TeleDongle v0.2 are
+TeleMetrum v1, TeleMini v1.0 and TeleDongle v0.2 are
all programmed by using another device as a programmer (pair
-programming). It’s important to recognize which kind of devices
-you have before trying to reprogram them.</p><p>You may wish to begin by ensuring you have current firmware
+programming). It’s important to recognize which kind of devices
+you have before trying to reprogram them.</p>
+</div>
+<div class="paragraph">
+<p>TeleMini v3 can be updated directly over USB, but has no USB connector
+on the board. Instead, the USB signals are present on a row of 6
+holes adjacent to the copyright assertion in the silk screen. Thus,
+updating firmware on TeleMini v3 requires making up a special cable,
+after which you can treat it just like TeleMetrum or TeleMega. Many
+USB cables seem to follow the color code of red is +5V, black is GND,
+green is USB +, and white is USB -. On TeleMini v3, pin 3 which has
+a square copper pad is ground, pin 1 is USB -, and pin 2 is USB +.</p>
+</div>
+<div class="paragraph">
+<p>You may wish to begin by ensuring you have current firmware
images. These are distributed as part of the AltOS software
bundle that also includes the AltosUI ground station program.
Newer ground station versions typically work fine with older
-firmware versions, so you don’t need to update your devices
+firmware versions, so you don’t need to update your devices
just to try out new software features. You can always
download the most recent version from
-<a class="ulink" href="http://www.altusmetrum.org/AltOS/" target="_top">http://www.altusmetrum.org/AltOS/</a></p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_updating_telemega_telemetrum_v2_easymega_easymini_or_teledongle_v3_firmware"></a>C.1. Updating TeleMega, TeleMetrum v2, EasyMega, EasyMini or TeleDongle v3 Firmware</h2></div></div></div><p>Self-programmable devices are reprogrammed by
-connecting them to your computer over USB.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
-Attach a battery if necessary and power switch to
-the target device. Power up the device.
-</li><li class="listitem">
-Using a Micro USB cable, connect the target device to your
-computer’s USB socket.
-</li><li class="listitem">
-Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from the File menu.
-</li><li class="listitem">
-Select the target device in the Device Selection dialog.
-</li><li class="listitem">
-Select the image you want to flash to the device,
+<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_or_newer_telemini_v3_easymega_easymini_teledongle_v3_or_telebt_v3_firmware">C.1. Updating TeleMega, TeleMetrum v2 or newer, TeleMini v3, 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>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>Attach a battery if necessary and power switch to
+the target device. Power up the device.</p>
+</li>
+<li>
+<p>Using a Micro USB cable, connect the target device to your
+computer’s USB socket. If the target is a TeleMini v3,
+make up and attach a special USB cable.</p>
+</li>
+<li>
+<p>Run AltosUI, and select 'Flash Image' from the File menu.</p>
+</li>
+<li>
+<p>Select the target device in the Device Selection dialog.</p>
+</li>
+<li>
+<p>Select the image you want to flash to the device,
which should have a name in the form
<product>-v<product-version>-<software-version>.ihx,
-such as EasyMini-v1.0-1.6.0.ihx.
-</li><li class="listitem">
-Make sure the configuration parameters are
+such as EasyMini-v1.0-1.6.0.ihx.</p>
+</li>
+<li>
+<p>Make sure the configuration parameters are
reasonable looking. If the serial number and/or RF
-configuration values aren’t right, you’ll need to
-change them.
-</li><li class="listitem">
-Hit the <span class="emphasis"><em>OK</em></span> button and the software should proceed
+configuration values aren’t right, you’ll need to
+change them.</p>
+</li>
+<li>
+<p>Hit the 'OK' button and the software should proceed
to flash the device with new firmware, showing a
-progress bar.
-</li><li class="listitem">
-Verify that the device is working by using the
-<span class="emphasis"><em>Configure Altimeter</em></span> or <span class="emphasis"><em>Configure Groundstation</em></span>
-item to check over the configuration.
-</li></ol></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_recovering_from_self_flashing_failure"></a>C.1.1. Recovering From Self-Flashing Failure</h3></div></div></div><p>If the firmware loading fails, it can leave the device
+progress bar.</p>
+</li>
+<li>
+<p>Verify that the device is working by using the
+'Configure Altimeter' or 'Configure Groundstation'
+item to check over the configuration.</p>
+</li>
+</ol>
+</div>
+<div class="sect3">
+<h4 id="_recovering_from_self_flashing_failure">C.1.1. Recovering From Self-Flashing Failure</h4>
+<div class="paragraph">
+<p>If the firmware loading fails, it can leave the device
unable to boot. Not to worry, you can force the device to
start the boot loader instead, which will let you try to
-flash the device again.</p><p>On each device, connecting two pins from one of the exposed
+flash the device again.</p>
+</div>
+<div class="paragraph">
+<p>On each device, connecting two pins from one of the exposed
connectors will force the boot loader to start, even if the
-regular operating system has been corrupted in some way.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
-TeleMega
-</span></dt><dd>
-Connect pin 6 and pin 1 of the companion
+regular operating system has been corrupted in some way.</p>
+</div>
+<div class="dlist">
+<dl>
+<dt class="hdlist1">TeleMega</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
-the board. Be very careful to <span class="strong"><strong>not</strong></span> short pin 8 to
+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.
-</dd><dt><span class="term">
-EasyMega
-</span></dt><dd>
-Connect pin 6 and pin 1 of the companion
+if that is connected to pin 1, but shouldn’t damage
+the board.</p>
+</dd>
+<dt class="hdlist1">EasyMega</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
-the board. Be very careful to <span class="strong"><strong>not</strong></span> short pin 8 to
+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.
-</dd><dt><span class="term">
-TeleMetrum v2
-</span></dt><dd>
-Connect pin 6 and pin 1 of the companion
+if that is connected to pin 1, but shouldn’t damage
+the board.</p>
+</dd>
+<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
-the board. Be very careful to <span class="strong"><strong>not</strong></span> short pin 8 to
+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.
-</dd><dt><span class="term">
-EasyMini
-</span></dt><dd>
-Connect pin 6 and pin 1 of the debug connector, which
+if that is connected to pin 1, but shouldn’t damage
+the board.</p>
+</dd>
+<dt class="hdlist1">EasyMini</dt>
+<dd>
+<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
-the one on the other end of the row.
-</dd><dt><span class="term">
-TeleDongle v3
-</span></dt><dd>
-Connect pin 32 on the CPU to ground. Pin 32 is closest
+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
to the USB wires on the row of pins towards the center
of the board. Ground is available on the capacitor
-next to it, on the end towards the USB wires.
-</dd></dl></div><p>Once you’ve located the right pins:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
-Turn the altimeter power off.
-</li><li class="listitem">
-Connect a battery.
-</li><li class="listitem">
-Connect the indicated terminals together with a
+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
+pin from the right on the top when the unit is oriented
+such that the SMA is at the top.</p>
+</dd>
+</dl>
+</div>
+<div class="paragraph">
+<p>Once you’ve located the right pins:</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>Turn the altimeter power off.</p>
+</li>
+<li>
+<p>Connect a battery.</p>
+</li>
+<li>
+<p>Connect the indicated terminals together with a
short piece of wire. Take care not to accidentally
-connect anything else.
-</li><li class="listitem">
-Connect USB
-</li><li class="listitem">
-Turn the board power on.
-</li></ol></div><p>The board should now be visible over USB as
-<span class="emphasis"><em>AltosFlash</em></span> and be ready to receive firmware. Once
+connect anything else.</p>
+</li>
+<li>
+<p>Connect USB</p>
+</li>
+<li>
+<p>Turn the board power on.</p>
+</li>
+</ol>
+</div>
+<div class="paragraph">
+<p>The board should now be visible over USB as
+'AltosFlash' and be ready to receive firmware. Once
the board has been powered up, you can remove the
-piece of wire.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_pair_programming"></a>C.2. Pair Programming</h2></div></div></div><p>The big concept to understand is that you have to use
+piece of wire.</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_pair_programming">C.2. Pair Programming</h3>
+<div class="paragraph">
+<p>The big concept to understand is that you have to use
a TeleMetrum v1.0, TeleBT v1.0 or TeleDongle v0.2 as a
programmer to update a pair programmed device. Due to
-limited memory resources in the cc1111, we don’t
+limited memory resources in the cc1111, we don’t
support programming directly over USB for these
-devices.</p><p>If you need to update the firmware on a TeleDongle
+devices.</p>
+</div>
+<div class="paragraph">
+<p>If you need to update the firmware on a TeleDongle
v0.2, we recommend updating the altimeter first,
before updating TeleDongle. However, note that
TeleDongle rarely need to be updated. Any firmware
version 1.0.1 or later will work, version 1.2.1 may
-have improved receiver performance slightly.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_updating_telemetrum_v1_x_firmware"></a>C.2.1. Updating TeleMetrum v1.x Firmware</h3></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
-Find the <span class="emphasis"><em>programming cable</em></span> that you got as
+have improved receiver performance slightly.</p>
+</div>
+<div class="sect3">
+<h4 id="_updating_telemetrum_v1_x_firmware">C.2.1. Updating TeleMetrum v1.x Firmware</h4>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>Find the 'programming cable' that you got as
part of the starter kit, that has a red
8-pin MicroMaTch connector on one end and a
red 4-pin MicroMaTch connector on the other
-end.
-</li><li class="listitem">
-Take the 2 screws out of the TeleDongle v0.2
+end.</p>
+</li>
+<li>
+<p>Take the 2 screws out of the TeleDongle v0.2
or TeleBT v1.0 case to get access to the
-circuit board.
-</li><li class="listitem">
-Plug the 8-pin end of the programming cable
+circuit board.</p>
+</li>
+<li>
+<p>Plug the 8-pin end of the programming cable
to the matching connector on the TeleDongle
v0.2 or TeleBT v1.0, and the 4-pin end to
the matching connector on the TeleMetrum.
Note that each MicroMaTch connector has an
alignment pin that goes through a hole in
the PC board when you have the cable
-oriented correctly.
-</li><li class="listitem">
-Attach a battery to the TeleMetrum board.
-</li><li class="listitem">
-Plug the TeleDongle v0.2 or TeleBT v1.0 into
-your computer’s USB port, and power up the
-TeleMetrum.
-</li><li class="listitem">
-Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from
-the File menu.
-</li><li class="listitem">
-Pick the TeleDongle v0.2 or TeleBT v1.0
+oriented correctly.</p>
+</li>
+<li>
+<p>Attach a battery to the TeleMetrum board.</p>
+</li>
+<li>
+<p>Plug the TeleDongle v0.2 or TeleBT v1.0 into
+your computer’s USB port, and power up the
+TeleMetrum.</p>
+</li>
+<li>
+<p>Run AltosUI, and select 'Flash Image' from
+the File menu.</p>
+</li>
+<li>
+<p>Pick the TeleDongle v0.2 or TeleBT v1.0
device from the list, identifying it as the
-programming device.
-</li><li class="listitem">
-Select the image you want put on the
+programming device.</p>
+</li>
+<li>
+<p>Select the image you want put on the
TeleMetrum, which should have a name in the
form telemetrum-v1.2-1.0.0.ihx. It should
be visible in the default directory, if not
you may have to poke around your system to
-find it.
-</li><li class="listitem">
-Make sure the configuration parameters are
+find it.</p>
+</li>
+<li>
+<p>Make sure the configuration parameters are
reasonable looking. If the serial number
-and/or RF configuration values aren’t right,
-you’ll need to change them.
-</li><li class="listitem">
-Hit the <span class="emphasis"><em>OK</em></span> button and the software should
+and/or RF configuration values aren’t right,
+you’ll need to change them.</p>
+</li>
+<li>
+<p>Hit the 'OK' button and the software should
proceed to flash the TeleMetrum with new
-firmware, showing a progress bar.
-</li><li class="listitem">
-Confirm that the TeleMetrum board seems to
+firmware, showing a progress bar.</p>
+</li>
+<li>
+<p>Confirm that the TeleMetrum board seems to
have updated OK, which you can do by
plugging in to it over USB and using a
terminal program to connect to the board and
-issue the <span class="emphasis"><em>v</em></span> command to check the version,
-etc.
-</li></ol></div><p>If something goes wrong, give it another try.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_updating_telemini_firmware"></a>C.2.2. Updating TeleMini Firmware</h3></div></div></div><p>You’ll need a special <span class="emphasis"><em>programming cable</em></span> to
-reprogram the TeleMini. You can make your own
+issue the 'v' command to check the version,
+etc.</p>
+</li>
+</ol>
+</div>
+<div class="paragraph">
+<p>If something goes wrong, give it another try.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_updating_telemini_v1_0_firmware">C.2.2. Updating TeleMini v1.0 Firmware</h4>
+<div class="paragraph">
+<p>You’ll need a special 'programming cable' to
+reprogram the TeleMini v1.0. You can make your own
using an 8-pin MicroMaTch connector on one end
-and a set of four pins on the other.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
-Take the 2 screws out of the TeleDongle v0.2
+and a set of four pins on the other.</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>Take the 2 screws out of the TeleDongle v0.2
or TeleBT v1.0 case to get access to the
-circuit board.
-</li><li class="listitem">
-Plug the 8-pin end of the programming cable
+circuit board.</p>
+</li>
+<li>
+<p>Plug the 8-pin end of the programming cable
to the matching connector on the TeleDongle
v0.2 or TeleBT v1.0, and the 4-pins into the
-holes in the TeleMini circuit board. Note
+holes in the TeleMini v1.0 circuit board. Note
that the MicroMaTch connector has an
alignment pin that goes through a hole in
the PC board when you have the cable
oriented correctly, and that pin 1 on the
-TeleMini board is marked with a square pad
-while the other pins have round pads.
-</li><li class="listitem">
-Attach a battery to the TeleMini board.
-</li><li class="listitem">
-Plug the TeleDongle v0.2 or TeleBT v1.0 into
-your computer’s USB port, and power up the
-TeleMini
-</li><li class="listitem">
-Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from
-the File menu.
-</li><li class="listitem">
-Pick the TeleDongle v0.2 or TeleBT v1.0
+TeleMini v1.0 board is marked with a square pad
+while the other pins have round pads.</p>
+</li>
+<li>
+<p>Attach a battery to the TeleMini v1.0 board.</p>
+</li>
+<li>
+<p>Plug the TeleDongle v0.2 or TeleBT v1.0 into
+your computer’s USB port, and power up the
+TeleMini v1.0</p>
+</li>
+<li>
+<p>Run AltosUI, and select 'Flash Image' from
+the File menu.</p>
+</li>
+<li>
+<p>Pick the TeleDongle v0.2 or TeleBT v1.0
device from the list, identifying it as the
-programming device.
-</li><li class="listitem">
-Select the image you want put on the
-TeleMini, which should have a name in the
+programming device.</p>
+</li>
+<li>
+<p>Select the image you want put on the
+TeleMini v1.0, which should have a name in the
form telemini-v1.0-1.0.0.ihx. It should be
visible in the default directory, if not you
may have to poke around your system to find
-it.
-</li><li class="listitem">
-Make sure the configuration parameters are
+it.</p>
+</li>
+<li>
+<p>Make sure the configuration parameters are
reasonable looking. If the serial number
-and/or RF configuration values aren’t right,
-you’ll need to change them.
-</li><li class="listitem">
-Hit the <span class="emphasis"><em>OK</em></span> button and the software should
-proceed to flash the TeleMini with new
-firmware, showing a progress bar.
-</li><li class="listitem">
-Confirm that the TeleMini board seems to
+and/or RF configuration values aren’t right,
+you’ll need to change them.</p>
+</li>
+<li>
+<p>Hit the 'OK' button and the software should
+proceed to flash the TeleMini v1.0 with new
+firmware, showing a progress bar.</p>
+</li>
+<li>
+<p>Confirm that the TeleMini v1.0 board seems to
have updated OK, which you can do by
configuring it over the radio link through
the TeleDongle, or letting it come up in
-“flight” mode and listening for telemetry.
-</li></ol></div><p>If something goes wrong, give it another try.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_updating_teledongle_v0_2_firmware"></a>C.2.3. Updating TeleDongle v0.2 Firmware</h3></div></div></div><p>Updating TeleDongle v0.2 firmware is just like
-updating TeleMetrum v1.x or TeleMini firmware, but you
+“flight” mode and listening for telemetry.</p>
+</li>
+</ol>
+</div>
+<div class="paragraph">
+<p>If something goes wrong, give it another try.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_updating_teledongle_v0_2_firmware">C.2.3. Updating TeleDongle v0.2 Firmware</h4>
+<div class="paragraph">
+<p>Updating TeleDongle v0.2 firmware is just like
+updating TeleMetrum v1.x or TeleMini v1.0 firmware, but you
use either a TeleMetrum v1.x, TeleDongle v0.2 or
-TeleBT v1.0 as the programmer.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
-Find the <span class="emphasis"><em>programming cable</em></span> that you got as part of
+TeleBT v1.0 as the programmer.</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>Find the 'programming cable' that you got as part of
the starter kit, that has a red 8-pin MicroMaTch
connector on one end and a red 4-pin MicroMaTch
-connector on the other end.
-</li><li class="listitem">
-Find the USB cable that you got as part of the
+connector on the other end.</p>
+</li>
+<li>
+<p>Find the USB cable that you got as part of the
starter kit, and plug the “mini” end in to the
mating connector on TeleMetrum v1.x, TeleDongle v0.2
-or TeleBT v1.0.
-</li><li class="listitem">
-Take the 2 screws out of the TeleDongle v0.2 or
-TeleBT v1.0 case to get access to the circuit board.
-</li><li class="listitem">
-Plug the 8-pin end of the programming cable to the
+or TeleBT v1.0.</p>
+</li>
+<li>
+<p>Take the 2 screws out of the TeleDongle v0.2 or
+TeleBT v1.0 case to get access to the circuit board.</p>
+</li>
+<li>
+<p>Plug the 8-pin end of the programming cable to the
matching connector on the programmer, and the 4-pin
end to the matching connector on the TeleDongle
v0.2. Note that each MicroMaTch connector has an
alignment pin that goes through a hole in the PC
-board when you have the cable oriented correctly.
-</li><li class="listitem">
-Attach a battery to the TeleMetrum v1.x board if
-you’re using one.
-</li><li class="listitem">
-Plug both the programmer and the TeleDongle into
-your computer’s USB ports, and power up the
-programmer.
-</li><li class="listitem">
-Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from the File
-menu.
-</li><li class="listitem">
-Pick the programmer device from the list,
-identifying it as the programming device.
-</li><li class="listitem">
-Select the image you want put on the TeleDongle
+board when you have the cable oriented correctly.</p>
+</li>
+<li>
+<p>Attach a battery to the TeleMetrum v1.x board if
+you’re using one.</p>
+</li>
+<li>
+<p>Plug both the programmer and the TeleDongle into
+your computer’s USB ports, and power up the
+programmer.</p>
+</li>
+<li>
+<p>Run AltosUI, and select 'Flash Image' from the File
+menu.</p>
+</li>
+<li>
+<p>Pick the programmer device from the list,
+identifying it as the programming device.</p>
+</li>
+<li>
+<p>Select the image you want put on the TeleDongle
v0.2, which should have a name in the form
teledongle-v0.2-1.0.0.ihx. It should be visible in
the default directory, if not you may have to poke
-around your system to find it.
-</li><li class="listitem">
-Make sure the configuration parameters are
+around your system to find it.</p>
+</li>
+<li>
+<p>Make sure the configuration parameters are
reasonable looking. If the serial number and/or RF
-configuration values aren’t right, you’ll need to
+configuration values aren’t right, you’ll need to
change them. The TeleDongle v0.2 serial number is
on the “bottom” of the circuit board, and can
usually be read through the translucent blue plastic
case without needing to remove the board from the
-case.
-</li><li class="listitem">
-Hit the <span class="emphasis"><em>OK</em></span> button and the software should proceed
+case.</p>
+</li>
+<li>
+<p>Hit the 'OK' button and the software should proceed
to flash the TeleDongle v0.2 with new firmware,
-showing a progress bar.
-</li><li class="listitem">
-Confirm that the TeleDongle v0.2 board seems to have
+showing a progress bar.</p>
+</li>
+<li>
+<p>Confirm that the TeleDongle v0.2 board seems to have
updated OK, which you can do by plugging in to it
over USB and using a terminal program to connect to
-the board and issue the <span class="emphasis"><em>v</em></span> command to check the
-version, etc. Once you’re happy, remove the
+the board and issue the 'v' command to check the
+version, etc. Once you’re happy, remove the
programming cable and put the cover back on the
-TeleDongle v0.2.
-</li></ol></div><p>If something goes wrong, give it another try.</p><p>Be careful removing the programming cable from the
-locking 8-pin connector on TeleMetrum. You’ll need a
+TeleDongle v0.2.</p>
+</li>
+</ol>
+</div>
+<div class="paragraph">
+<p>If something goes wrong, give it another try.</p>
+</div>
+<div class="paragraph">
+<p>Be careful removing the programming cable from the
+locking 8-pin connector on TeleMetrum. You’ll need a
fingernail or perhaps a thin screwdriver or knife
blade to gently pry the locking ears out slightly to
extract the connector. We used a locking connector on
TeleMetrum to help ensure that the cabling to
-companion boards used in a rocket don’t ever come
-loose accidentally in flight.</p></div></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_flight_data_recording"></a>Appendix D. Flight Data Recording</h1></div></div></div><p>Each flight computer logs data at 100 samples per second
+companion boards used in a rocket don’t ever come
+loose accidentally in flight.</p>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_flight_data_recording">Appendix D: Flight Data Recording</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Each flight computer logs data at 100 samples per second
during ascent and 10 samples per second during
descent, except for TeleMini v1.0, which records ascent at 10 samples
per second and descent at 1 sample per second.
Data are logged to
an on-board flash memory part, which can be partitioned into
-several equal-sized blocks, one for each flight.</p><div class="table"><a id="idm45058130283472"></a><p class="title"><strong>Table D.1. Data Storage on Altus Metrum altimeters</strong></p><div class="table-contents"><table summary="Data Storage on Altus Metrum altimeters" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /><col class="col_4" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Device </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Bytes per Sample </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Total Storage </th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Minutes at Full Rate</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1MB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>20</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v1.1 v1.2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2MB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>40</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v2.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>16</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>80</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMini v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>5kB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>4</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>EasyMini</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>16</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1MB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>10</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMega</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>32</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>40</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>EasyMega</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>32</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="" align="left" valign="top"><p>40</p></td></tr></tbody></table></div></div><br class="table-break" /><p>The on-board flash is partitioned into separate flight logs,
+several equal-sized blocks, one for each flight.</p>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<caption class="title">Table 11. Data Storage on Altus Metrum altimeters</caption>
+<colgroup>
+<col style="width: 25%;">
+<col style="width: 25%;">
+<col style="width: 25%;">
+<col style="width: 25%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Device</th>
+<th class="tableblock halign-left valign-top">Bytes per Sample</th>
+<th class="tableblock halign-left valign-top">Total Storage</th>
+<th class="tableblock halign-left valign-top">Minutes at Full Rate</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">TeleMetrum v1.0</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">8</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">1MB</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">20</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">TeleMetrum v1.1 v1.2</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">8</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">2MB</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">40</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">TeleMetrum v2.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">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>
+<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">TeleMini 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">512kB</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">5</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">16</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">1MB</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">10</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">TeleMega</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">32</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">40</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">EasyMega</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">32</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">40</p></td>
+</tr>
+</tbody>
+</table>
+<div class="paragraph">
+<p>The on-board flash is partitioned into separate flight logs,
each of a fixed maximum size. Increase the maximum size of
each log and you reduce the number of flights that can be
-stored. Decrease the size and you can store more flights.</p><p>Configuration data is also stored in the flash memory on
+stored. Decrease the size and you can store more flights.</p>
+</div>
+<div class="paragraph">
+<p>Configuration data is also stored in the flash memory on
TeleMetrum v1.x,
-TeleMini and
+TeleMini v3.0 and
EasyMini.
This consumes 64kB
of flash space. This configuration space is not available
-for storing flight log data.</p><p>TeleMetrum v2.0, TeleMega and EasyMega
+for storing flight log data.</p>
+</div>
+<div class="paragraph">
+<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><p>To compute the amount of space needed for a single flight, you
+more flight data.</p>
+</div>
+<div class="paragraph">
+<p>To compute the amount of space needed for a single flight, you
can multiply the expected ascent time (in seconds) by 100
times bytes-per-sample, multiply the expected descent time (in
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><p>The default size allows for several flights on each flight
+could store dozens of these flights in the on-board flash.</p>
+</div>
+<div class="paragraph">
+<p>The default size allows for several flights on each flight
computer, except for TeleMini v1.0, which
only holds data for a single flight.
-You can adjust the size.</p><p>Altus Metrum flight computers will not overwrite existing
+You can adjust the size.</p>
+</div>
+<div class="paragraph">
+<p>Altus Metrum flight computers will not overwrite existing
flight data, so be sure to download flight data and erase it
from the flight computer before it fills up. The flight
computer will still successfully control the flight even if it
-cannot log data, so the only thing you will lose is the data.</p></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_altus_metrum_hardware_specifications"></a>Appendix E. Altus Metrum Hardware Specifications</h1></div></div></div><p>Here’s the full set of Altus Metrum products, both in
-production and retired.</p><div class="table"><a id="idm45058130237152"></a><p class="title"><strong>Table E.1. Altus Metrum Flight Computer Electronics</strong></p><div class="table-contents"><table summary="Altus Metrum Flight Computer Electronics" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /><col class="col_4" /><col class="col_5" /><col class="col_6" /><col class="col_7" /><col class="col_8" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Device </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"> Barometer </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"> Z-axis accel </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"> GPS </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"> 3D sensors </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"> Storage </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"> RF Output </th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top"> Battery</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MP3H6115 10km (33k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MMA2202 50g</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>SkyTraq</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>10mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v1.1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MP3H6115 10km (33k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MMA2202 50g</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>SkyTraq</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>10mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v1.2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MP3H6115 10km (33k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>ADXL78 70g</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>SkyTraq</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>10mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v2.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MS5607 30km (100k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MMA6555 102g</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>uBlox Max-7Q</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>40mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMini v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MP3H6115 10km (33k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>5kB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>10mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>EasyMini v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MS5607 30km (100k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7-12V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMega v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MS5607 30km (100k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MMA6555 102g</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>uBlox Max-7Q</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MPU6000 HMC5883</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>40mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>EasyMega v1.0</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>MS5607 30km (100k')</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>MMA6555 102g</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>MPU6000 HMC5883</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="" align="left" valign="top"><p>3.7V</p></td></tr></tbody></table></div></div><br class="table-break" /><p></p><div class="table"><a id="idm45058130154144"></a><p class="title"><strong>Table E.2. Altus Metrum Flight Computer Mechanical Components</strong></p><div class="table-contents"><table summary="Altus Metrum Flight Computer Mechanical Components" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /><col class="col_4" /><col class="col_5" /><col class="col_6" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Device</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Connectors</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Screw Terminals</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Width</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Length</th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Tube Size</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Antenna Debug Companion USB Battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro Switch</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1 inch (2.54cm)</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2 ¾ inch (6.99cm)</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>29mm coupler</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMini v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Antenna Debug Battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>½ inch (1.27cm)</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1½ inch (3.81cm)</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>18mm coupler</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMini v2.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Antenna Debug USB Battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro Battery Switch</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>0.8 inch (2.03cm)</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1½ inch (3.81cm)</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>24mm coupler</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>EasyMini</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Debug USB Battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro Battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>0.8 inch (2.03cm)</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1½ inch (3.81cm)</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>24mm coupler</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMega</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Antenna Debug Companion USB Battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro Pyro A-D Switch Pyro battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1¼ inch (3.18cm)</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3¼ inch (8.26cm)</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>38mm coupler</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>EasyMega</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Debug Companion USB Battery</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro Pyro A-D Switch Pyro battery</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>1¼ inch (3.18cm)</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>2¼ inch (5.62cm)</p></td><td style="" align="left" valign="top"><p>38mm coupler</p></td></tr></tbody></table></div></div><br class="table-break" /></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_release_notes"></a>Appendix F. Release Notes</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6_2"></a>F.1. Release Notes for Version 1.6.2</h2></div></div></div><p>Version 1.6.2 includes support for our updated TeleMega v2.0
+cannot log data, so the only thing you will lose is the data.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_altus_metrum_hardware_specifications">Appendix E: Altus Metrum Hardware Specifications</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Here’s the full set of Altus Metrum products, both in
+production and retired.</p>
+</div>
+<table class="tableblock frame-all grid-all stretch">
+<caption class="title">Table 12. Altus Metrum Flight Computer Electronics</caption>
+<colgroup>
+<col style="width: 12.5%;">
+<col style="width: 12.5%;">
+<col style="width: 12.5%;">
+<col style="width: 12.5%;">
+<col style="width: 12.5%;">
+<col style="width: 12.5%;">
+<col style="width: 12.5%;">
+<col style="width: 12.5%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Device</th>
+<th class="tableblock halign-left valign-top">Barometer</th>
+<th class="tableblock halign-left valign-top">Z-axis accel</th>
+<th class="tableblock halign-left valign-top">GPS</th>
+<th class="tableblock halign-left valign-top">3D sensors</th>
+<th class="tableblock halign-left valign-top">Storage</th>
+<th class="tableblock halign-left valign-top">RF Output</th>
+<th class="tableblock halign-left valign-top">Battery</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">TeleMetrum 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">MMA2202 50g</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">SkyTraq</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">-</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">1MB</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">10mW</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">TeleMetrum v1.1</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">MMA2202 50g</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">SkyTraq</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">-</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">2MB</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">10mW</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">TeleMetrum v1.2</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">ADXL78 70g</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">SkyTraq</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">-</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">2MB</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">10mW</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">TeleMetrum v2.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">uBlox Max-7Q</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">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">-</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">-</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">5kB</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">10mW</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 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">-</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">512kB</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">EasyMini 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">-</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">1MB</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>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">EasyMini v2.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">-</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">1MB</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>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">TeleMega 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">uBlox Max-7Q</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">MPU6000 HMC5883</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">TeleMega v2.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">uBlox Max-7Q</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">MPU6000 HMC5883</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">TeleMega 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">MMA6555 102g</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">uBlox Max-7Q</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">MPU9250</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">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">TeleMega v5.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">MPU6000 MMC5983</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">MPU6000 HMC5883</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">-</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 v2.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">-</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">MPU9250</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">-</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>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">EasyMotor v2.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">ADXL375 200g</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">-</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">-</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">6.5-15V</p></td>
+</tr>
+</tbody>
+</table>
+<div style="page-break-after: always;"></div>
+<table class="tableblock frame-all grid-all stretch">
+<caption class="title">Table 13. Altus Metrum Flight Computer Mechanical Components</caption>
+<colgroup>
+<col style="width: 16.6666%;">
+<col style="width: 16.6666%;">
+<col style="width: 16.6666%;">
+<col style="width: 16.6666%;">
+<col style="width: 16.6666%;">
+<col style="width: 16.667%;">
+</colgroup>
+<thead>
+<tr>
+<th class="tableblock halign-left valign-top">Device</th>
+<th class="tableblock halign-left valign-top">Connectors</th>
+<th class="tableblock halign-left valign-top">Screw Terminals</th>
+<th class="tableblock halign-left valign-top">Width</th>
+<th class="tableblock halign-left valign-top">Length</th>
+<th class="tableblock halign-left valign-top">Tube Size</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">TeleMetrum</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Antenna Debug Companion USB Battery</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee pyro Main pyro Switch</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">1 inch (2.54cm)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">2 ¾ inch (6.99cm)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">29mm coupler</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">Antenna Debug Battery</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee pyro Main pyro</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">½ inch (1.27cm)</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">18mm coupler</p></td>
+</tr>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">TeleMini v2.0</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Antenna Debug USB Battery</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee pyro Main pyro Battery Switch</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>
+<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">Apogee pyro Main pyro 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>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">TeleMega</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Antenna Debug Companion USB Battery</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee pyro Main pyro Pyro A-D Switch Pyro battery</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">1¼ inch (3.18cm)</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">3¼ inch (8.26cm)</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">EasyMega</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Debug Companion USB Battery</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Apogee pyro Main pyro Pyro A-D Switch Pyro battery</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">1¼ inch (3.18cm)</p></td>
+<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">EasyTimer</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>
+<tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">EasyMotor</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Debug USB</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">+5V Pres GND Switch 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>
+</div>
+<div class="sect1">
+<h2 id="_release_notes">Appendix F: Release Notes</h2>
+<div class="sectionbody">
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_9_8">F.1. Release Notes for Version 1.9.8</h3>
+<div class="paragraph">
+<p>Version 1.9.8</p>
+</div>
+<div class="sect3">
+<h4 id="_altos">F.1.1. AltOS</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Add support for TeleMega v5.0</p>
+</li>
+<li>
+<p>Extend extra pyro channel times to support delay > 327 seconds</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_2">F.1.2. AltosUI</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Support ARM devices in Linux binary release</p>
+</li>
+<li>
+<p>Add support for TeleMega v5.0</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosdroid_2">F.1.3. AltosDroid</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Show tilt angle in pad and flight tabs</p>
+</li>
+<li>
+<p>Show altitude as well as height (useful for TeleGPS)</p>
+</li>
+<li>
+<p>Support devices without GPS receivers</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_micropeak_gui">F.1.4. MicroPeak GUI</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Show error dialog if device open fails</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_9_7">F.2. Release Notes for Version 1.9.7</h3>
+<div class="paragraph">
+<p>Version 1.9.7</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_2">F.2.1. AltOS</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Fix TeleGPS logging so that new data are appended to an existing log correctly</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_3">F.2.2. AltosUI</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Support Mac OS X 11 (Big Sur)</p>
+</li>
+<li>
+<p>Support Monitor Idle on Easy Timer</p>
+</li>
+<li>
+<p>Fix TeleMega v4.0 and TeleMetrum v3.0 configuration in Antenna Down mode</p>
+</li>
+<li>
+<p>Show launch sites in Load Maps view</p>
+</li>
+<li>
+<p>Add IMU header names to CSV files</p>
+</li>
+<li>
+<p>Clean up TeleGPS log corruption due to firmware bugs during firmware update</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosdroid_3">F.2.3. AltosDroid</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Support older devices back to Android version 5.1</p>
+</li>
+<li>
+<p>Fix a number of issues that could result in app crashes</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_9_6">F.3. Release Notes for Version 1.9.6</h3>
+<div class="paragraph">
+<p>Version 1.9.6</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_3">F.3.1. AltOS</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Fix EasyTimer bug where it might mis-detect boost (either
+detect it early or not at all) due to small errors in
+accelerometer calibration leading to large accumulated error
+in speed.</p>
+</li>
+<li>
+<p>Adjust self-test of new 9-axis IMU (BMX-160) so that it
+doesn’t think the part has a failure when tested sitting
+horizontally.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_9_5">F.4. Release Notes for Version 1.9.5</h3>
+<div class="paragraph">
+<p>Version 1.9.5</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_4">F.4.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_4">F.4.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.5. Release Notes for Version 1.9.4</h3>
+<div class="paragraph">
+<p>Version 1.9.4</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_5">F.5.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_5">F.5.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.6. Release Notes for Version 1.9.3</h3>
+<div class="paragraph">
+<p>Version 1.9.3</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_6">F.6.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.6.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.7. Release Notes for Version 1.9.2</h3>
+<div class="paragraph">
+<p>Version 1.9.2</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_7">F.7.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.7.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_4">F.7.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.8. Release Notes for Version 1.9.1</h3>
+<div class="paragraph">
+<p>Version 1.9.1</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_8">F.8.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.8.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.9. Release Notes for Version 1.9</h3>
+<div class="paragraph">
+<p>Version 1.9</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_9">F.9.1. AltOS</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Add support for EasyMega v2.0</p>
+</li>
+<li>
+<p>Replace C library for ARM devices</p>
+</li>
+<li>
+<p>Remove support for 8051-based devices and SDCC compiler</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_telegps_micropeak_4">F.9.2. AltosUI, TeleGPS, MicroPeak</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Select ROM images based on product name when reflashing</p>
+</li>
+<li>
+<p>Fix TeleGPS v2 battery voltage display</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_8_7">F.10. Release Notes for Version 1.8.7</h3>
+<div class="paragraph">
+<p>Version 1.8.7</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_10">F.10.1. AltOS</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Include TeleMega v3.0 firmware</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_telegps_micropeak_5">F.10.2. AltosUI, TeleGPS, MicroPeak</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Poll for new devices while Device dialog is displayed</p>
+</li>
+<li>
+<p>Wait for device to re-appear when flashing new firmware</p>
+</li>
+<li>
+<p>Fetch correct TeleBT v4.0 RF calibration values from web
+site when reflashing.</p>
+</li>
+<li>
+<p>Change gyro headings in .csv files from x/y/z to
+roll/pitch/yaw</p>
+</li>
+<li>
+<p>Add documentation about Packet Link mode</p>
+</li>
+<li>
+<p>Add documentation about forcing TeleMini RF parameters to
+known values.</p>
+</li>
+<li>
+<p>Create a proxy server for Google Maps to re-enable map
+images</p>
+</li>
+<li>
+<p>Fix Java version info in all distributed jar files so that
+applications will run with standard Mac OS X Java.</p>
+</li>
+<li>
+<p>Replace JavaApplicationStub for Mac OS X so that
+applications will run with Oracle Java.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_8_6">F.11. Release Notes for Version 1.8.6</h3>
+<div class="paragraph">
+<p>Version 1.8.6</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_11">F.11.1. AltOS</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Use maximum of 64 previous tilt values in pyro tilt tests</p>
+</li>
+<li>
+<p>Eliminate 100m height requirement for coast detection</p>
+</li>
+<li>
+<p>Change After Motor pyro check to be >= instead of ==</p>
+</li>
+<li>
+<p>Change Time since Boost to be Time since launch.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_telegps">F.11.2. AltosUI, TeleGPS</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Clarify pyro test phrasing</p>
+</li>
+<li>
+<p>Remove ascending/descending from pyro config UI</p>
+</li>
+<li>
+<p>Fix accel calibration in Antenna Down mode</p>
+</li>
+<li>
+<p>Add mag sensor reporting for TeleMega v3 idle monitoring.</p>
+</li>
+<li>
+<p>Fix radio parameter saving at 2400 bps telmetry rate.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_micropeak">F.11.3. MicroPeak</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Report altimeter-recorded maximum height value</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_8_5">F.12. 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_12">F.12.1. AltOS</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Fix startup beeps that indicate sensor failures.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_telegps_2">F.12.2. AltosUI, TeleGPS</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>When updating device firmware, make sure selected firmware
+matches target device.</p>
+</li>
+<li>
+<p>Correct Bluetooth device matching when looking for TeleBT
+devices.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_8_4">F.13. 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_13">F.13.1. AltOS</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Support for EasyMini version 2.0 hardware.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_8_3">F.14. 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
+changes KML export data to make Tripoli Record reporting
+better and some updates to graph presentation and data
+downloading.</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_14">F.14.1. AltOS</h4>
+<div class="sect4">
+<h5 id="_altos_new_features">AltOS New Features</h5>
+<div class="ulist">
+<ul>
+<li>
+<p>Support for TeleMega version 3.0 hardware.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect4">
+<h5 id="_altos_bug_fixes">AltOS Bug Fixes</h5>
+<div class="ulist">
+<ul>
+<li>
+<p>Ground testing EasyMega and TeleMega additional pyro
+channels could result in a sticky 'fired' status which would
+prevent these channels from firing on future flights.</p>
+</li>
+<li>
+<p>Corrupted flight log records could prevent future flights
+from capturing log data.</p>
+</li>
+<li>
+<p>Fixed saving of pyro configuration that ended with
+'Descending'.</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_and_telegps_applications">F.14.2. AltosUI and TeleGPS Applications</h4>
+<div class="sect4">
+<h5 id="_altosui_new_features">AltosUI New Features</h5>
+<div class="ulist">
+<ul>
+<li>
+<p>Support for TeleMega version 3.0.</p>
+</li>
+<li>
+<p>Graph lines have improved appearance to make them easier to
+distinguish. Markers may be placed at data points to show
+captured recorded data values.</p>
+</li>
+<li>
+<p>Graphing offers the ability to adjust the smoothing of
+computed speed and acceleration data.</p>
+</li>
+<li>
+<p>The download dialog now offers to graph new flights, checks
+for existing files to avoid overwriting data and reports if
+there are checksum errors in the downloaded data.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect4">
+<h5 id="_altosuitelegps_bug_fixes">AltosUI/TeleGPS Bug Fixes</h5>
+<div class="ulist">
+<ul>
+<li>
+<p>Restore TeleGPS tracking behavior.</p>
+</li>
+<li>
+<p>Display flight computer call sign and serial number in
+Monitor Idle mode instead of ground station values.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect4">
+<h5 id="_altosui_and_telegps_changes">AltosUI and TeleGPS Changes</h5>
+<div class="ulist">
+<ul>
+<li>
+<p>KML export now reports both barometric and GPS altitude data
+to make it more useful for Tripoli record reporting.</p>
+</li>
+<li>
+<p>CSV export now includes TeleMega/EasyMega pyro voltages and
+tilt angle.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_8_2">F.15. 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>
+</div>
+<div class="paragraph">
+<p>1.8.2 also contains a couple of minor fixes for AltosUI when
+analyzing saved data files.</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_15">F.15.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS New Features</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Support for TeleGPS version 2.0 hardware.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_and_telegps_applications_2">F.15.2. AltosUI and TeleGPS Applications</h4>
+<div class="paragraph">
+<p>AltosUI and TeleGPS New Features</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Support for TeleGPS version 2.0.</p>
+</li>
+<li>
+<p>Accelerometer re-calibration user interface.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltosUI and TeleGPS Bug Fixes</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Prevent some crashes when reading older saved flight data
+for graphing or KML export.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_8_1">F.16. 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
+must update firmware.</p>
+</div>
+<div class="paragraph">
+<p>This release also contains a change in how flight computers
+with accelerometers deal with speeds around and above Mach
+1. In previous versions, the flight computer would completely
+disregard the barometric sensor above 330m/s (around Mach
+1). Now, the data from the barometric sensor is reduced in
+effect without ever going away entirely. This prevents early
+drogue deployment for flights which spend considerable time
+above Mach 1.</p>
+</div>
+<div class="paragraph">
+<p>1.8.1 also contains a couple of minor fixes for AltosUI when
+analyzing saved data files.</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_16">F.16.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS Bug Fixes</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Handle time value wrapping in Apogee Lockout
+correctly. Without this, apogee lockout would sometimes
+prevent any drogue charge from firing.</p>
+</li>
+<li>
+<p>Change Kalman filter on flight computers with accelerometer
+to continue using the barometric sensor even at high speeds
+to avoid unintentional drogue deployment during
+deceleration.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_and_telegps_applications_3">F.16.2. AltosUI and TeleGPS Applications</h4>
+<div class="paragraph">
+<p>AltosUI New Features</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add new 'Huge' font size to make text even bigger on high
+resolution monitors.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltosUI Bug Fixes</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Prevent some crashes when reading older saved flight data
+for graphing or KML export.</p>
+</li>
+<li>
+<p>Load frequency preference at startup. The loading code was
+broken, so you’d see only the default frequencies.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_8">F.17. 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
+software 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>
+<div class="paragraph">
+<p>AltOS New Features</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add support for TeleBT v4.0 boards.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_and_telegps_applications_4">F.17.2. AltosUI and TeleGPS Applications</h4>
+<div class="paragraph">
+<p>AltosUI New Features</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add support for TeleBT v4.0 hardware</p>
+</li>
+<li>
+<p>Rewrite graphing and export functions. This code now handles
+each data series separately so that graphs are drawn
+correctly. Smoothing now uses a filter that looks both
+forward and backwards in time to make computed speed and
+acceleration data more accurate.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltosUI Bug Fixes</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Correct axis labeling of magnetic sensor in TeleMega and
+EasyMega. The Y and Z axes were flipped.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_7">F.18. 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_18">F.18.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS New Features</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add support for TeleMini v3.0 boards.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltOS Fixes</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Fix interrupt priorities on STM32L processors. Run timer
+interrupt at lowest priority so that device interrupts get
+serviced first.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_and_telegps_applications_5">F.18.2. AltosUI and TeleGPS Applications</h4>
+<div class="paragraph">
+<p>AltosUI New Features</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add support for TeleMini v3.0 hardware</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_6_8">F.19. 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
+telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum
+v2.0 users should update their flight firmware.</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_19">F.19.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Fix STM32L DMA driver to work around STM32L SoC DMA priority
+issue t lock-up in the logging or radio code, either of
+which could stop data logging and telemetry.</p>
+</li>
+<li>
+<p>Avoid having TeleBT battery status values smash telemetry
+packet data by holding a lock during both operations.</p>
+</li>
+<li>
+<p>Don’t start reporting 'flight 0' when the log fills in
+flight.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltOS changes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Flash LEDS on all products briefly during power up so that
+they can be tested during production.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_telegps_and_altosdroid_applications">F.19.2. AltosUI, TeleGPS and AltosDroid Applications</h4>
+<div class="paragraph">
+<p>AltosUI fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Re-enable go/no-go entries after they’ve been disabled due
+to lack of data. If telemetry information is delayed when
+the Ui starts up, sometimes important fields would get
+disabled to never re-appear.</p>
+</li>
+<li>
+<p>Deal with ground station failure better during Configure
+Ground Station operation by cleaning up pending operations.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_6_5">F.20. 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
+telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum
+v2.0 users should update their flight firmware.</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_20">F.20.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Fix STM32L SPI driver to prevent lock-up in the logging or
+radio code, either of which could stop data logging and
+telemetry. Found and characterized by Chuck Haskin, who also
+tested the new firmware before release.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_telegps_and_altosdroid_applications_2">F.20.2. AltosUI, TeleGPS and AltosDroid Applications</h4>
+<div class="paragraph">
+<p>AltosUI fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Deliver firmward for TeleMega v2.0 and TeleBT v3.0 with
+Windows package.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_6_4">F.21. 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_21">F.21.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Fix hardware flow control on TeleBT v1.0. Hardware RTS/CTS
+doesn’t seem to work, switch from using the hardware to
+driving these pins with software.</p>
+</li>
+<li>
+<p>Fix ARM USB drivers to deal with OS restarts. Needed to
+reset all USB-related state when the USB bus is reset. These
+fixes affect all STM32L, STM32F0 and LPC11U14 based devices.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_telegps_and_altosdroid_applications_3">F.21.2. AltosUI, TeleGPS and AltosDroid Applications</h4>
+<div class="paragraph">
+<p>AltosUI, TeleGPS and AltosDroid New Features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Automatically switch from meters or feet to kilometers or
+miles for distance units.</p>
+</li>
+<li>
+<p>Add Monitor Idle mode to TeleGPS application.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltosUI, TeleGPS and AltosDroid Fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Abort map preloading when the preload map dialog is closed.</p>
+</li>
+<li>
+<p>In AltosDroid, Don’t reconnect to last device if the user
+had disconnected it the last time the application was
+active.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_documentation">F.21.3. Documentation</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Mention TeleMega v2.0 in hardware specs table.</p>
+</li>
+<li>
+<p>Document TeleGPS RF output in telegps manual.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_6_3">F.22. 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_22">F.22.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Fix hardware flow control on TeleBT v3.0. RTS/CTS is
+wired backwards on this board, switch from using the
+hardware to driving these pins with software.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_and_telegps_applications_6">F.22.2. AltosUI and TeleGPS Applications</h4>
+<div class="paragraph">
+<p>AltosUI and TeleGPS New Features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add BlueTooth support for Windows operating system. This
+supports connections to TeleBT over BlueTooth rather than
+just USB.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltosUI and TeleGPS Fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Change Java detection and install on Windows. Detection is
+now done by looking for the 'javaw.exe' program, and
+installation by opening a browser on the java.com web site.</p>
+</li>
+<li>
+<p>Delay polling while the Fire Igniters is visible to allow
+for TeleMega to report back complete status over the radio.</p>
+</li>
+<li>
+<p>Disallow changing RF calibration numbers in the
+configuration UI. There’s no good reason to change this from
+the field, and recovering is really hard if you haven’t
+written down the right number.</p>
+</li>
+<li>
+<p>Fix USB device discovery on Mac OS X El Capitan. This makes
+the connected Altus Metrum USB devices appear again.</p>
+</li>
+<li>
+<p>Fix acceleration data presented in MonitorIdle mode for
+TeleMetrum v2.0 flight computers.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosdroid_5">F.22.3. AltosDroid</h4>
+<div class="paragraph">
+<p>AltosDroid new features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Monitor Idle mode. Check state of flight computer while in
+idle mode over the radio link</p>
+</li>
+<li>
+<p>Fire Igniters. Remotely fire ignires for recovery system
+ground tests.</p>
+</li>
+<li>
+<p>Remote reboot. Cause the flight computer to reboot over the
+radio link. This provides a method for switching the flight
+computer from idle to flight mode without needing to reach
+the power switch.</p>
+</li>
+<li>
+<p>Configurable frequency menu. Change the set of available
+frequencies and provide more descriptive names.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltosDroid bug fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Don’t set target location if GPS hasn’t locked yet.</p>
+</li>
+<li>
+<p>Fix saving target states so they can be reloaded when the
+application restarts. When the application is shut down and
+restarted, all previous target state information will be
+restored (including GPS position if available).</p>
+</li>
+<li>
+<p>Fix crash on some Android devices for offline maps when
+changing the map scale or location.</p>
+</li>
+<li>
+<p>Don’t require USB OTG support. This kept the latest
+AltosDroid from being offered on devices without USB device
+support, although it can work without that just fine using
+BlueTooth.</p>
+</li>
+<li>
+<p>Don’t require bluetooth to be enabled. This allows the
+application to operate with USB devices or just show old
+data without turning on the bluetooth radio.</p>
+</li>
+<li>
+<p>Recover old tracker positions when restarting
+application. This finally allows you to safely stop and
+restart the application without losing the last known
+location of any tracker.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_documentation_2">F.22.4. Documentation</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Document TeleMega and EasyMega additional pyro channel
+continuity audio alert pattern.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_6_2">F.23. 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 class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos"></a>F.1.1. AltOS</h3></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Add support for TeleMega v2.0 boards.
-</li><li class="listitem">
-Add PWM servo driver. There’s no higher level code using
+and ground station interfaces.</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_23">F.23.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS New Features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add support for TeleMega v2.0 boards.</p>
+</li>
+<li>
+<p>Add PWM servo driver. There’s no higher level code using
this yet, but the driver allows testing of the TeleMega v2.0
-servo output connector.
-</li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Slow down telemetry packets to allow receiver to keep
-up.
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications"></a>F.1.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Fix post-flight orientation computation when processing
-TeleMega and EasyMega eeprom data files.
-</li><li class="listitem">
-Capture complete eeprom data even when there are invalid
+servo output connector.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltOS Fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Slow down telemetry packets to allow receiver to keep
+up.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_and_telegps_applications_7">F.23.2. AltosUI and TeleGPS Applications</h4>
+<div class="paragraph">
+<p>AltosUI and TeleGPS Fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Fix post-flight orientation computation when processing
+TeleMega and EasyMega eeprom data files.</p>
+</li>
+<li>
+<p>Capture complete eeprom data even when there are invalid
entries in the data. This keeps reading eeprom contents and
-writing the associated .eeprom file when an error is detected.
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation"></a>F.1.3. Documentation</h3></div></div></div><p>We spent a bunch of time trying to improve our documentation</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-HTML versions now have a table of contents on the left side.
-</li><li class="listitem">
-EasyMini now has its own shorter manual.
-</li><li class="listitem">
-Provide links between sections in each document.
-</li><li class="listitem">
-Lots of minor rewriting and restructuring to avoid
-duplication of information
-</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6_1"></a>F.2. Release Notes for Version 1.6.1</h2></div></div></div><p>Version 1.6.1 includes support for our updated TeleBT v3.0
+writing the associated .eeprom file when an error is detected.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_documentation_3">F.23.3. Documentation</h4>
+<div class="paragraph">
+<p>We spent a bunch of time trying to improve our documentation</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>HTML versions now have a table of contents on the left side.</p>
+</li>
+<li>
+<p>EasyMini now has its own shorter manual.</p>
+</li>
+<li>
+<p>Provide links between sections in each document.</p>
+</li>
+<li>
+<p>Lots of minor rewriting and restructuring to avoid
+duplication of information</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_6_1">F.24. 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 class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_2"></a>F.2.1. AltOS</h3></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Add support for TeleBT v3.0 boards.
-</li><li class="listitem">
-Add support for uncompressed APRS data, providing support
+and ground station interfaces.</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_24">F.24.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS New Features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add support for TeleBT v3.0 boards.</p>
+</li>
+<li>
+<p>Add support for uncompressed APRS data, providing support
for older APRS receivers. Uncompressed APRS data is less
-precise, takes more bandwidth and doesn’t have integrated
-altitude data.
-</li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Make TeleDongle and TeleBT more tolerant of data rate
-variations from transmitting devices.
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_2"></a>F.2.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Add map to Monitor Idle display. It’s nice to be able to
+precise, takes more bandwidth and doesn’t have integrated
+altitude data.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltOS Fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Make TeleDongle and TeleBT more tolerant of data rate
+variations from transmitting devices.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_and_telegps_applications_8">F.24.2. AltosUI and TeleGPS Applications</h4>
+<div class="paragraph">
+<p>AltosUI and TeleGPS New Features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add map to Monitor Idle display. It’s nice to be able to
verify that maps are working, instead of needing to use
-Monitor Flight.
-</li></ul></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Fix frequency configuration to round values instead of
-truncate them, avoiding a common 1kHz error in the setting.
-</li><li class="listitem">
-Turn the Windows stub into a more useful program that can
+Monitor Flight.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltosUI and TeleGPS Fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Fix frequency configuration to round values instead of
+truncate them, avoiding a common 1kHz error in the setting.</p>
+</li>
+<li>
+<p>Turn the Windows stub into a more useful program that can
launch the application with parameters so that file manager
-icons work more reliably.
-</li><li class="listitem">
-Force KML export to use a C locale so that numbers are
-formatted with <span class="emphasis"><em>.</em></span> instead of <span class="emphasis"><em>,</em></span> for a decimal separator in
-non-US locales.
-</li><li class="listitem">
-Preload map tiles based on distance rather than number of
+icons work more reliably.</p>
+</li>
+<li>
+<p>Force KML export to use a C locale so that numbers are
+formatted with '.' instead of ',' for a decimal separator in
+non-US locales.</p>
+</li>
+<li>
+<p>Preload map tiles based on distance rather than number of
tiles; this means you get the same resolution covering the
entire area, rather than having high resolution near the
-center and low resolution further away.
-</li><li class="listitem">
-Allow configuration of frequency and callsign in Monitor
-Idle mode.
-</li><li class="listitem">
-Fix layout weirdness when resizing windows on
-Windows. Windows shouldn’t have giant blank spaces around
-the useful content anymore.
-</li><li class="listitem">
-Fix layout weirdness when resizing windows on
-Windows. Windows shouldn’t have giant blank spaces around
-the useful content anymore.
-</li><li class="listitem">
-Use a longer filter for descent speed values. This should
+center and low resolution further away.</p>
+</li>
+<li>
+<p>Allow configuration of frequency and callsign in Monitor
+Idle mode.</p>
+</li>
+<li>
+<p>Fix layout weirdness when resizing windows on
+Windows. Windows shouldn’t have giant blank spaces around
+the useful content anymore.</p>
+</li>
+<li>
+<p>Fix layout weirdness when resizing windows on
+Windows. Windows shouldn’t have giant blank spaces around
+the useful content anymore.</p>
+</li>
+<li>
+<p>Use a longer filter for descent speed values. This should
provide something more useful on the display, although it
-will take longer to respond to changes now.
-</li><li class="listitem">
-Make Replay Flight run in realtime again. It had been set to
-run at 10x speed by mistake.
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosdroid_2"></a>F.2.3. AltosDroid</h3></div></div></div><p>AltosDroid New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Add offline map support using mapping code from AltosUI.
-</li><li class="listitem">
-Support TeleDongle (and TeleBT via USB) on devices
-supporting USB On-The-Go.
-</li><li class="listitem">
-Display additional TeleMega pyro channel status in Pad tab.
-</li><li class="listitem">
-Switch between metric and imperial units.
-</li><li class="listitem">
-Monitor TeleBT battery voltage.
-</li><li class="listitem">
-Track multiple devices at the same time, selecting between
-them with a menu or using the map.
-</li><li class="listitem">
-Add hybrid, satellite and terrain map types.
-</li></ul></div><p>AltosDroid Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Use standard Android display conventions so that a menu
-button is available in the application title bar.
-</li><li class="listitem">
-Adjust layout to work on large and small screens; shrinking
+will take longer to respond to changes now.</p>
+</li>
+<li>
+<p>Make Replay Flight run in realtime again. It had been set to
+run at 10x speed by mistake.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosdroid_6">F.24.3. AltosDroid</h4>
+<div class="paragraph">
+<p>AltosDroid New Features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add offline map support using mapping code from AltosUI.</p>
+</li>
+<li>
+<p>Support TeleDongle (and TeleBT via USB) on devices
+supporting USB On-The-Go.</p>
+</li>
+<li>
+<p>Display additional TeleMega pyro channel status in Pad tab.</p>
+</li>
+<li>
+<p>Switch between metric and imperial units.</p>
+</li>
+<li>
+<p>Monitor TeleBT battery voltage.</p>
+</li>
+<li>
+<p>Track multiple devices at the same time, selecting between
+them with a menu or using the map.</p>
+</li>
+<li>
+<p>Add hybrid, satellite and terrain map types.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltosDroid Fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Use standard Android display conventions so that a menu
+button is available in the application title bar.</p>
+</li>
+<li>
+<p>Adjust layout to work on large and small screens; shrinking
the go/no-go lights in smaller environments to try and make
-everything visible.
-</li><li class="listitem">
-Make voice announcements depend on current tab.
-</li><li class="listitem">
-Compute adjustment to current travel direction while in
-motion towards rocket.
-</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6"></a>F.3. Release Notes for Version 1.6</h2></div></div></div><p>Version 1.6 includes support for our updated TeleDongle v3.0
+everything visible.</p>
+</li>
+<li>
+<p>Make voice announcements depend on current tab.</p>
+</li>
+<li>
+<p>Compute adjustment to current travel direction while in
+motion towards rocket.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_6">F.25. 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 class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_3"></a>F.3.1. AltOS</h3></div></div></div><p>AltOS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Add support for TeleDongle v3.0 boards.
-</li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Don’t beep out the continuity twice by accident in idle mode.
+and ground station interfaces.</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_25">F.25.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS New Features</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add support for TeleDongle v3.0 boards.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltOS Fixes</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Don’t beep out the continuity twice by accident in idle mode.
If the battery voltage report takes longer than the initialiation
-sequence, the igniter continuity would get reported twice.
-</li><li class="listitem">
-Record all 32 bits of gyro calibration data in TeleMega and
+sequence, the igniter continuity would get reported twice.</p>
+</li>
+<li>
+<p>Record all 32 bits of gyro calibration data in TeleMega and
EasyMega log files. This fixes computation of the gyro rates
-in AltosUI.
-</li><li class="listitem">
-Change TeleDongle LED usage. Green LED flashes when valid
+in AltosUI.</p>
+</li>
+<li>
+<p>Change TeleDongle LED usage. Green LED flashes when valid
packet is received. Red LED flashes when invalid packet is
-received.
-</li><li class="listitem">
-Replace LPC11U14 SPI driver with non-interrupt version. The
+received.</p>
+</li>
+<li>
+<p>Replace LPC11U14 SPI driver with non-interrupt version. The
interrupt code would occasionally wedge on long transfers
if interrupts were blocked for too long. This affects all
released TeleGPS products; if you have a TeleGPS device,
-you’ll want to reflash the firmware.
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_3"></a>F.3.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Compute tilt angle from TeleMega and EasyMega log
+you’ll want to reflash the firmware.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_and_telegps_applications_9">F.25.2. AltosUI and TeleGPS Applications</h4>
+<div class="paragraph">
+<p>AltosUI and TeleGPS New Features</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Compute tilt angle from TeleMega and EasyMega log
files. This duplicates the quaternion-based angle tracking
code from the flight firmware inside the ground station
software so that post-flight analysis can include evaluation
-of the tilt angle.
-</li><li class="listitem">
-Shows the tool button window when starting with a data file
+of the tilt angle.</p>
+</li>
+<li>
+<p>Shows the tool button window when starting with a data file
specified. This means that opening a data file from the file
manager will now bring up the main window to let you operate
-the whole application.
-</li></ul></div><p>AltosUI Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Show the <span class="emphasis"><em>Connecting</em></span> dialog when using Monitor Idle. Lets
+the whole application.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltosUI Fixes</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Show the 'Connecting' dialog when using Monitor Idle. Lets
you cancel the Monitor Idle startup when connecting over the
-radio link.
-</li><li class="listitem">
-Make <span class="emphasis"><em>Monitor Idle</em></span> work for TeleGPS devices when connected
-over USB. It’s nice for testing without needing to broadcast
-over the radio.
-</li><li class="listitem">
-Use different Windows API to discover USB devices. This
+radio link.</p>
+</li>
+<li>
+<p>Make 'Monitor Idle' work for TeleGPS devices when connected
+over USB. It’s nice for testing without needing to broadcast
+over the radio.</p>
+</li>
+<li>
+<p>Use different Windows API to discover USB devices. This
works better on my Windows 7 box, and will be used if the
-older API fails to provide the necessary information.
-</li><li class="listitem">
-Look in more places in the registry to try and identify the
+older API fails to provide the necessary information.</p>
+</li>
+<li>
+<p>Look in more places in the registry to try and identify the
installed Java version on Windows. If you install the
default 32-bit version of Windows on a 64-bit OS, the Java
registry information is hiding \SOFTWARE\Wow6432Node for
-some reason.
-</li><li class="listitem">
-Fix file association on Windows by searching for the
+some reason.</p>
+</li>
+<li>
+<p>Fix file association on Windows by searching for the
javaw.exe program instead of assuming it is in
%SYSTEMROOT%. This makes double-clicking on Altus Metrum
-data files in the file manager work correctly.
-</li><li class="listitem">
-When replaying a file, put <span class="emphasis"><em>done</em></span> in the Age field when we
-reach the end of the file, instead of continuing to count forever.
-</li><li class="listitem">
-In the Scan Channels code, wait for five seconds if we see
+data files in the file manager work correctly.</p>
+</li>
+<li>
+<p>When replaying a file, put 'done' in the Age field when we
+reach the end of the file, instead of continuing to count forever.</p>
+</li>
+<li>
+<p>In the Scan Channels code, wait for five seconds if we see
any packet. This is needed because AltOS now sends the
callsign, serial number and flight number only once every
-five seconds these days.
-</li><li class="listitem">
-In the Scan Channels code, reset pending flight state
+five seconds these days.</p>
+</li>
+<li>
+<p>In the Scan Channels code, reset pending flight state
information each time we change channels. This avoids having
-flight computers appear on multiple frequencies by accident.
-</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_5"></a>F.4. Release Notes for Version 1.5</h2></div></div></div><p>Version 1.5 is a major release. It includes support for our new
+flight computers appear on multiple frequencies by accident.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_5">F.26. 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 class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_4"></a>F.4.1. AltOS</h3></div></div></div><p>AltOS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Add support for EasyMega boards.
-</li><li class="listitem">
-Make the APRS SSID be configurable. This lets you track
+software for all our boards and the AltosUI ground station</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_26">F.26.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS New Features</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add support for EasyMega boards.</p>
+</li>
+<li>
+<p>Make the APRS SSID be configurable. This lets you track
different rockets on the same receiver without getting
-things mixed up.
-</li><li class="listitem">
-Report extra pyro channel continuity state on EasyMega and
+things mixed up.</p>
+</li>
+<li>
+<p>Report extra pyro channel continuity state on EasyMega and
TeleMega via the beeper. This lets you easily verify flight
readiness on these boards after powering up the electronics
-on the rail.
-</li><li class="listitem">
-Add lower telemetry data rates (2400 and 9600 bps) to
+on the rail.</p>
+</li>
+<li>
+<p>Add lower telemetry data rates (2400 and 9600 bps) to
increase telemetry radio range. This reduces the amount of
data received as well as increasing battery consumption in
-the transmitter.
-</li><li class="listitem">
-Change TeleGPS to have only a single log, and append new
+the transmitter.</p>
+</li>
+<li>
+<p>Change TeleGPS to have only a single log, and append new
data to it rather than using seperate per-flight logs. This
avoids accidentally filling up log storage by turning
-TeleGPS on/off several times.
-</li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Increase the maximum range for altitude values from +/-32767m
+TeleGPS on/off several times.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltOS Fixes</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Increase the maximum range for altitude values from +/-32767m
to +/-2147483647m, allowing the flight computers to function
-correctly above the 32km level.
-</li><li class="listitem">
-Continuously test pyro firing conditions during delay stage,
+correctly above the 32km level.</p>
+</li>
+<li>
+<p>Continuously test pyro firing conditions during delay stage,
inhibiting the pyro channel if the test fails. This prevents
firing pyro charges where the conditions were good before
-the delay, but become bad before the delay expires.
-</li><li class="listitem">
-Allow negative numbers in pyro configuration values. This
+the delay, but become bad before the delay expires.</p>
+</li>
+<li>
+<p>Allow negative numbers in pyro configuration values. This
lets you specify things like descending speed or
-deceleration.
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_4"></a>F.4.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Support telemetry baud rate selection. Adds menus to
+deceleration.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_and_telegps_applications_10">F.26.2. AltosUI and TeleGPS Applications</h4>
+<div class="paragraph">
+<p>AltosUI and TeleGPS New Features</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Support telemetry baud rate selection. Adds menus to
the flight monitoring and configuration for baud rate
-selection.
-</li><li class="listitem">
-Support APRS SSID configuration.
-</li><li class="listitem">
-Integrate with file managers. This provides icons for all of
+selection.</p>
+</li>
+<li>
+<p>Support APRS SSID configuration.</p>
+</li>
+<li>
+<p>Integrate with file managers. This provides icons for all of
our file types and associates our application with the files
so that using a file manager to open a AltOS data file
-results in launching our application.
-</li></ul></div><p>AltosUI Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Make the <span class="emphasis"><em>Graph</em></span> button on the landed tab work again.
-</li><li class="listitem">
-Make tests for Java on Windows a bit smarter, and also
+results in launching our application.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltosUI Fixes</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Make the 'Graph' button on the landed tab work again.</p>
+</li>
+<li>
+<p>Make tests for Java on Windows a bit smarter, and also
provide the user with the option to skip installing Java for
-cases where we just can’t figure out what version is installed.
-</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_4_2"></a>F.5. Release Notes for Version 1.4.2</h2></div></div></div><p>Version 1.4.2 is a minor release. It fixes Java-related install issues on
-Windows</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_5"></a>F.5.1. AltosUI and TeleGPS Applications</h3></div></div></div><p>Windows Install Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Checks for Java installation data in more registry locations.
-</li><li class="listitem">
-Allows user to bypass Java installation in case the
-detection fails.
-</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_4_1"></a>F.6. Release Notes for Version 1.4.1</h2></div></div></div><p>Version 1.4.1 is a minor release. It fixes install issues on
+cases where we just can’t figure out what version is installed.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_4_2">F.27. 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.27.1. AltosUI and TeleGPS Applications</h4>
+<div class="paragraph">
+<p>Windows Install Fixes</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Checks for Java installation data in more registry locations.</p>
+</li>
+<li>
+<p>Allows user to bypass Java installation in case the
+detection fails.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_4_1">F.28. 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
-aren’t any changes to the firmware or host applications at
+aren’t any changes to the firmware or host applications at
all. All Windows users will want to upgrade to get the signed
driver, but Mac and Linux users who do not need the TeleMetrum
-V2.0 firmware image will not need to upgrade.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_6"></a>F.6.1. AltosUI and TeleGPS Applications:</h3></div></div></div><p>Windows Install Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Provide signed Windows driver files. This should avoid any need to
-disable driver signature checking on Windows 7 or 8.
-</li><li class="listitem">
-Fix Java version detection and download. Previously, the
+V2.0 firmware image will not need to upgrade.</p>
+</div>
+<div class="sect3">
+<h4 id="_altosui_and_telegps_applications_12">F.28.1. AltosUI and TeleGPS Applications:</h4>
+<div class="paragraph">
+<p>Windows Install Fixes</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Provide signed Windows driver files. This should avoid any need to
+disable driver signature checking on Windows 7 or 8.</p>
+</li>
+<li>
+<p>Fix Java version detection and download. Previously, the
installer would only look for Java 6 or 7 and insist on
downloading its own Java bits if there was something else
-installed. Furthermore, the 64-bit Java link provided didn’t
+installed. Furthermore, the 64-bit Java link provided didn’t
work for anyone other than Keith, making it impossible to
-install AltOS on any machine with Java SE 8 installed.
-</li></ul></div><p>Other Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Include 1.4 firmware for TeleMetrum V2.0. None of the
-installers shipped this file. Now it’s included in the AltOS
-packages for Linux, Mac and Windows.
-</li><li class="listitem">
-Include Google Application Key for map downloading. The 1.4
-release didn’t have this key in the released version of the
-software, making map downloading fail for most people.
-</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_4"></a>F.7. Release Notes for Version 1.4</h2></div></div></div><p>Version 1.4 is a major release. It includes support for our new
+install AltOS on any machine with Java SE 8 installed.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Other Fixes</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Include 1.4 firmware for TeleMetrum V2.0. None of the
+installers shipped this file. Now it’s included in the AltOS
+packages for Linux, Mac and Windows.</p>
+</li>
+<li>
+<p>Include Google Application Key for map downloading. The 1.4
+release didn’t have this key in the released version of the
+software, making map downloading fail for most people.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_4">F.29. 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 class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_5"></a>F.7.1. AltOS</h3></div></div></div><p>AltOS new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Add support for TeleGPS boards.
-</li><li class="listitem">
-Make the beeper tone configurable, making it
+software for all our boards and the AltosUI ground station</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_27">F.29.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS new features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add support for TeleGPS boards.</p>
+</li>
+<li>
+<p>Make the beeper tone configurable, making it
possible to distinguish between two Altus Metrum
-products in the same ebay.
-</li><li class="listitem">
-Make the firing time for extra pyro channels
+products in the same ebay.</p>
+</li>
+<li>
+<p>Make the firing time for extra pyro channels
configurable, allowing longer (or shorter) than the
default 50ms. Only relevant for TeleMega at this
-time.
-</li></ul></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Replace the <span class="emphasis"><em>dit dit dit</em></span> tones at startup with the
+time.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltOS fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Replace the 'dit dit dit' tones at startup with the
current battery voltage, measured in tenths of a
volt. This lets you check the battery voltage
without needing telemetry, which is especially
-useful on EasyMini.
-</li><li class="listitem">
-Change state beeping to "Farnsworth spacing", which
-means they’re quite a bit faster than before, and so
-they take less time to send.
-</li><li class="listitem">
-Fix bug preventing the selection of the <span class="emphasis"><em>Flight
-State After</em></span> mode in pyro configuration.
-</li><li class="listitem">
-Fix bug where erasing flights would reset the flight
-number to 2 on TeleMega and TeleMetrum v2.
-</li><li class="listitem">
-Fix u-Blox GPS driver to mark course and speed data
-as being present.
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application"></a>F.7.2. AltosUI Application</h3></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Add zooming and new content types (terrain and road
+useful on EasyMini.</p>
+</li>
+<li>
+<p>Change state beeping to "Farnsworth spacing", which
+means they’re quite a bit faster than before, and so
+they take less time to send.</p>
+</li>
+<li>
+<p>Fix bug preventing the selection of the 'Flight
+State After' mode in pyro configuration.</p>
+</li>
+<li>
+<p>Fix bug where erasing flights would reset the flight
+number to 2 on TeleMega and TeleMetrum v2.</p>
+</li>
+<li>
+<p>Fix u-Blox GPS driver to mark course and speed data
+as being present.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_application">F.29.2. AltosUI Application</h4>
+<div class="paragraph">
+<p>AltosUI new features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add zooming and new content types (terrain and road
maps) to map view. Change map storage format from
PNG to Jpeg, which saves a huge amount of disk
space. You will need to re-download all of your
-pre-loaded map images.
-</li><li class="listitem">
-Add a distance measuring device to the maps
+pre-loaded map images.</p>
+</li>
+<li>
+<p>Add a distance measuring device to the maps
view. Select this by using any button other than the
left one, or by pressing shift or control on the
-keyboard while using the left button.
-</li><li class="listitem">
-Add new <span class="emphasis"><em>Ignitor</em></span> tab to the flight monitor display
-for TeleMega’s extra ignitors.
-</li><li class="listitem">
-Add additional ignitor firing marks and voltages to
+keyboard while using the left button.</p>
+</li>
+<li>
+<p>Add new 'Ignitor' tab to the flight monitor display
+for TeleMega’s extra ignitors.</p>
+</li>
+<li>
+<p>Add additional ignitor firing marks and voltages to
the graph so you can see when the ignitors fired,
-along with the ignitor voltages.
-</li><li class="listitem">
-Add GPS course, ground speed and climb rate as
-optional graph elements.
-</li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-When flashing new firmware, re-try opening the
+along with the ignitor voltages.</p>
+</li>
+<li>
+<p>Add GPS course, ground speed and climb rate as
+optional graph elements.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltosUI fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>When flashing new firmware, re-try opening the
device as sometimes it takes a while for the
underlying operating system to recognize that the
device has rebooted in preparation for the flashing
-operation.
-</li><li class="listitem">
-Hide Tilt Angle in ascent tab for devices that don’t
-have a gyro.
-</li><li class="listitem">
-Increase the width of data lines in the graphs to
-make them easier to read.
-</li><li class="listitem">
-Filter out speed and acceleration spikes caused by
+operation.</p>
+</li>
+<li>
+<p>Hide Tilt Angle in ascent tab for devices that don’t
+have a gyro.</p>
+</li>
+<li>
+<p>Increase the width of data lines in the graphs to
+make them easier to read.</p>
+</li>
+<li>
+<p>Filter out speed and acceleration spikes caused by
ejection charge firing when computing the maximum
values. This provides a more accurate reading of
-those maximums.
-</li><li class="listitem">
-Fix EasyMini voltage displays. Early EasyMini
+those maximums.</p>
+</li>
+<li>
+<p>Fix EasyMini voltage displays. Early EasyMini
prototypes used a 3.0V regulator, and AltosUI still
used that value as the basis of the
computation. Production EasyMini boards have always
boards sensed the battery voltage past the blocking
diode, resulting in a drop of about 150mV from the
true battery voltage. Compensate for that when
-displaying the value.
-</li><li class="listitem">
-Display error message when trying to configure
+displaying the value.</p>
+</li>
+<li>
+<p>Display error message when trying to configure
maximum flight log size while the flight computer
-still has flight data stored.
-</li><li class="listitem">
-Handle TeleMetrum and TeleMini eeprom files
+still has flight data stored.</p>
+</li>
+<li>
+<p>Handle TeleMetrum and TeleMini eeprom files
generated with pre-1.0 firmware. Those ancient
-versions didn’t report the log format, so just use
-the product name instead.
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_telegps_application"></a>F.7.3. TeleGPS Application</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-New application designed for use with TeleGPS boards.
-</li><li class="listitem">
-Shares code with AltosUI, mostly just trimmed down
-to focus on TeleGPS-related functions.
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation_2"></a>F.7.4. Documentation</h3></div></div></div><p>Documentation changes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Re-create the drill template images; they should
+versions didn’t report the log format, so just use
+the product name instead.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_telegps_application">F.29.3. TeleGPS Application</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>New application designed for use with TeleGPS boards.</p>
+</li>
+<li>
+<p>Shares code with AltosUI, mostly just trimmed down
+to focus on TeleGPS-related functions.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_documentation_4">F.29.4. Documentation</h4>
+<div class="paragraph">
+<p>Documentation changes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Re-create the drill template images; they should
print correctly from Firefox at least. Ship these as
-individual PDF files so they’re easy to print.
-</li><li class="listitem">
-Add a description of the <span class="emphasis"><em>Apogee Lockout</em></span> setting,
+individual PDF files so they’re easy to print.</p>
+</li>
+<li>
+<p>Add a description of the 'Apogee Lockout' setting,
which prevents the apogee charge from firing for a
-configurable amount of time after boost.
-</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_3_2"></a>F.8. Release Notes for Version 1.3.2</h2></div></div></div><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 class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_6"></a>F.8.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-On TeleMega, limit number of logged GPS status
-information to 12 satellites. That’s all there is
-room for in the log structure.
-</li><li class="listitem">
-Improve APRS behavior. Remembers last known GPS
+configurable amount of time after boost.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_3_2">F.30. 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_28">F.30.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>On TeleMega, limit number of logged GPS status
+information to 12 satellites. That’s all there is
+room for in the log structure.</p>
+</li>
+<li>
+<p>Improve APRS behavior. Remembers last known GPS
position and keeps sending that if we lose GPS
lock. Marks locked/unlocked by sending L/U in the
APRS comment field along with the number of sats in
-view and voltages.
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_2"></a>F.8.2. AltosUI Application</h3></div></div></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-If the TeleMega flight firmware reports that it has
+view and voltages.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_application_2">F.30.2. AltosUI Application</h4>
+<div class="paragraph">
+<p>AltosUI fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>If the TeleMega flight firmware reports that it has
logged information about more than 12 satellites,
-don’t believe it as the log only holds 12 satellite
-records.
-</li><li class="listitem">
-Track the maximum height as computed from GPS
+don’t believe it as the log only holds 12 satellite
+records.</p>
+</li>
+<li>
+<p>Track the maximum height as computed from GPS
altitude data and report that in the flight summary
-data.
-</li><li class="listitem">
-Use letters (A, B, C, D) for alternate pyro channel
+data.</p>
+</li>
+<li>
+<p>Use letters (A, B, C, D) for alternate pyro channel
names instead of numbers (0, 1, 2, 3) in the Fire
-Igniter dialog.
-</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_3_1"></a>F.9. Release Notes for Version 1.3.1</h2></div></div></div><p>Version 1.3.1 is a minor release. It improves support for
-TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_7"></a>F.9.1. AltOS</h3></div></div></div><p>AltOS new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Improved APRS mode. Now uses compressed position
+Igniter dialog.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_3_1">F.31. 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_29">F.31.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS new features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Improved APRS mode. Now uses compressed position
format for smaller data size, improved precision and
to include altitude data as well as latitude and
longitude. Also added battery and pyro voltage
reports in the APRS comment field so you can confirm
-that the unit is ready for launch.
-</li></ul></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Improve sensor boot code. If sensors fail to
+that the unit is ready for launch.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltOS fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Improve sensor boot code. If sensors fail to
self-test, the device will still boot up and check
for pad/idle modes. If in idle mode, the device will
warn the user with a distinct beep, if in Pad mode,
Z-axis accelerometer now uses the factory
calibration values instead of re-calibrating on the
pad each time. This avoids accidental boost detect
-when moving the device around while in Pad mode.
-</li><li class="listitem">
-Fix antenna-down mode accelerometer
-configuration. Antenna down mode wasn’t working
+when moving the device around while in Pad mode.</p>
+</li>
+<li>
+<p>Fix antenna-down mode accelerometer
+configuration. Antenna down mode wasn’t working
because the accelerometer calibration values were
-getting re-computed incorrectly in inverted mode.
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_3"></a>F.9.2. AltosUI Application</h3></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Display additional TeleMega sensor values in real
+getting re-computed incorrectly in inverted mode.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_application_3">F.31.2. AltosUI Application</h4>
+<div class="paragraph">
+<p>AltosUI new features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Display additional TeleMega sensor values in real
units. Make all of these values available for
plotting. Display TeleMega orientation value in the
-Ascent and Table tabs.
-</li><li class="listitem">
-Support additional TeleMega pyro channels in the
+Ascent and Table tabs.</p>
+</li>
+<li>
+<p>Support additional TeleMega pyro channels in the
Fire Igniter dialog. This lets you do remote testing
of all of the channels, rather than just Apogee and
-Main.
-</li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Limit data rate when downloading satellite images
+Main.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltosUI fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Limit data rate when downloading satellite images
from Google to make sure we stay within their limits
-so that all of the map tiles download successfully.
-</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_3"></a>F.10. Release Notes for Version 1.3</h2></div></div></div><p>Version 1.3 is a major release. It adds support for TeleMega,
-TeleMetrum v2.0, TeleMini v2.0 and EasyMini.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_8"></a>F.10.1. AltOS</h3></div></div></div><p>AltOS new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Add STM32L processor support. This includes
+so that all of the map tiles download successfully.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_3">F.32. 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_30">F.32.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS new features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add STM32L processor support. This includes
enhancements to the scheduler to support products
-with many threads.
-</li><li class="listitem">
-Add NXP LPC11U14 processor support.
-</li><li class="listitem">
-Support additional pyro channels. These are
+with many threads.</p>
+</li>
+<li>
+<p>Add NXP LPC11U14 processor support.</p>
+</li>
+<li>
+<p>Support additional pyro channels. These are
configurable through the UI to handle air starts,
staging, additional recovery events and external
-devices such as cameras.
-</li><li class="listitem">
-Add 3-axis gyro support for orientation
+devices such as cameras.</p>
+</li>
+<li>
+<p>Add 3-axis gyro support for orientation
tracking. This integrates the gyros to compute the
angle from vertical during flight, allowing the
additional pyro events to be controlled by this
-value.
-</li><li class="listitem">
-Many more device drivers, including u-Blox Max 7Q
+value.</p>
+</li>
+<li>
+<p>Many more device drivers, including u-Blox Max 7Q
GPS, Freescale MMA6555 digital single-axis
accelerometer, Invensense MPU6000 3-axis
accelerometer + 3 axis gyro, Honeywell HMC5883
3-axis magnetic sensor and the TI CC1120 and CC115L
-digital FM transceivers
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_4"></a>F.10.2. AltosUI Application</h3></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Support TeleMega, TeleMetrum v2.0, TeleMini v2.0 and
-EasyMini telemetry and log formats.
-</li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Use preferred units for main deployment height
+digital FM transceivers</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_application_4">F.32.2. AltosUI Application</h4>
+<div class="paragraph">
+<p>AltosUI new features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Support TeleMega, TeleMetrum v2.0, TeleMini v2.0 and
+EasyMini telemetry and log formats.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltosUI fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Use preferred units for main deployment height
configuration, instead of always doing configuration in
meters.
-== MicroPeak Application
-</li><li class="listitem">
-Add <span class="emphasis"><em>Download</em></span> button to menu bar.
-</li><li class="listitem">
-Save the last log directory and offer that as the
-default for new downloads
-</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_2_1"></a>F.11. Release Notes for Version 1.2.1</h2></div></div></div><p>Version 1.2.1 is a minor release. It adds support for TeleBT and
+== MicroPeak Application</p>
+</li>
+<li>
+<p>Add 'Download' button to menu bar.</p>
+</li>
+<li>
+<p>Save the last log directory and offer that as the
+default for new downloads</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_2_1">F.33. 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 class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_9"></a>F.11.1. AltOS</h3></div></div></div><p>AltOS new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Add support for TeleBT
-</li></ul></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-In TeleMini recovery mode (when booted with the
+AltosUI and fixes some bugs in the AltOS firmware.</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_31">F.33.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS new features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add support for TeleBT</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltOS fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>In TeleMini recovery mode (when booted with the
outer two debug pins connected together), the radio
parameters are also set back to defaults
-(434.550MHz, N0CALL, factory radio cal).
-</li><li class="listitem">
-Correct Kalman filter model error covariance
+(434.550MHz, N0CALL, factory radio cal).</p>
+</li>
+<li>
+<p>Correct Kalman filter model error covariance
matrix. The values used previously assumed
continuous measurements instead of discrete
-measurements.
-</li><li class="listitem">
-Fix some bugs in the USB driver for TeleMetrum and
-TeleDongle that affected Windows users.
-</li><li class="listitem">
-Adjusted the automatic gain control parameters that
+measurements.</p>
+</li>
+<li>
+<p>Fix some bugs in the USB driver for TeleMetrum and
+TeleDongle that affected Windows users.</p>
+</li>
+<li>
+<p>Adjusted the automatic gain control parameters that
affect receive performance for TeleDongle. Field
tests indicate that this may improve receive
-performance somewhat.
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_5"></a>F.11.2. AltosUI Application</h3></div></div></div><p>AltosUI application new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Make the initial position of the AltosUI top level
+performance somewhat.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_application_5">F.33.2. AltosUI Application</h4>
+<div class="paragraph">
+<p>AltosUI application new features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Make the initial position of the AltosUI top level
window configurable. Along with this change, the
-other windows will pop up at <span class="emphasis"><em>sensible</em></span> places now,
-instead of on top of one another.
-</li><li class="listitem">
-Add GPS data and a map to the graph window. This
+other windows will pop up at 'sensible' places now,
+instead of on top of one another.</p>
+</li>
+<li>
+<p>Add GPS data and a map to the graph window. This
lets you see a complete summary of the flight
-without needing to <span class="emphasis"><em>replay</em></span> the whole thing.
-</li></ul></div><p>AltosUI application fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Handle missing GPS lock in <span class="emphasis"><em>Descent</em></span>
+without needing to 'replay' the whole thing.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltosUI application fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Handle missing GPS lock in 'Descent'
tab. Previously, if the GPS position of the pad was
unknown, an exception would be raised, breaking the
-Descent tab contents.
-</li><li class="listitem">
-Improve the graph, adding tool-tips to show values
+Descent tab contents.</p>
+</li>
+<li>
+<p>Improve the graph, adding tool-tips to show values
near the cursor and making the displayed set of
values configurable, adding all of the flight data
as options while leaving the default settings alone
so that the graph starts by showing height, speed
-and acceleration.
-</li><li class="listitem">
-Add callsign to Monitor idle window and connecting
+and acceleration.</p>
+</li>
+<li>
+<p>Add callsign to Monitor idle window and connecting
dialogs. This makes it clear which callsign is being
used so that the operator will be aware that it must
match the flight computer value or no communication
-will work.
-</li><li class="listitem">
-When downloading flight data, display the block
+will work.</p>
+</li>
+<li>
+<p>When downloading flight data, display the block
number so that the user has some sense of
-progress. Unfortunately, we don’t know how many
+progress. Unfortunately, we don’t know how many
blocks will need to be downloaded, but at least it
-isn’t just sitting there doing nothing for a long
-time.
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosdroid_3"></a>F.11.3. AltosDroid</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-First version of this application
-</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_2"></a>F.12. Release Notes for Version 1.2</h2></div></div></div><p>Version 1.2 is a major release. It adds support for MicroPeak
-and the MicroPeak USB adapter.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_10"></a>F.12.1. AltOS</h3></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Add MicroPeak support. This includes support for the
+isn’t just sitting there doing nothing for a long
+time.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosdroid_7">F.33.3. AltosDroid</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>First version of this application</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_2">F.34. 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_32">F.34.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS New Features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add MicroPeak support. This includes support for the
ATtiny85 processor and adaptations to the core code
to allow for devices too small to run the
-multi-tasking scheduler.
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_micropeak_application"></a>F.12.2. AltosUI and MicroPeak Application</h3></div></div></div><p>New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Added MicroPeak application
-</li></ul></div><p>AltosUI and MicroPeak fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Distribute Mac OS X packages in disk image (<span class="emphasis"><em>.dmg</em></span>)
-format to greatly simplify installation.
-</li><li class="listitem">
-Provide version numbers for the shared Java
+multi-tasking scheduler.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_and_micropeak_application">F.34.2. AltosUI and MicroPeak Application</h4>
+<div class="paragraph">
+<p>New Features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Added MicroPeak application</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltosUI and MicroPeak fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Distribute Mac OS X packages in disk image ('.dmg')
+format to greatly simplify installation.</p>
+</li>
+<li>
+<p>Provide version numbers for the shared Java
libraries to ensure that upgrades work properly, and
to allow for multiple Altus Metrum software packages
to be installed in the same directory at the same
-time.
-</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_1"></a>F.13. Release Notes for Version 1.1</h2></div></div></div><p>Version 1.1.1 is a bug-fix release. It fixes a couple of bugs
+time.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_1">F.35. 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
version 1.0 boards. Thanks to Bob Brown for help diagnosing
the Google Earth file export issue, and for suggesting the
-addition of the Ground Distance value in the Descent tab.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_11"></a>F.13.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-TeleMetrum v1.0 boards use the AT45DB081D flash
+addition of the Ground Distance value in the Descent tab.</p>
+</div>
+<div class="sect3">
+<h4 id="_altos_33">F.35.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>TeleMetrum v1.0 boards use the AT45DB081D flash
memory part to store flight data, which is different
from later TeleMetrum boards. The AltOS v1.1 driver
-for this chip couldn’t erase memory, leaving it
+for this chip couldn’t erase memory, leaving it
impossible to delete flight data or update
-configuration values. This bug doesn’t affect newer
-TeleMetrum boards, and it doesn’t affect the safety
-of rockets flying version 1.1 firmware.
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_2"></a>F.13.2. AltosUI</h3></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-The “Descent” tab displays the range to the rocket,
+configuration values. This bug doesn’t affect newer
+TeleMetrum boards, and it doesn’t affect the safety
+of rockets flying version 1.1 firmware.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_6">F.35.2. AltosUI</h4>
+<div class="paragraph">
+<p>AltosUI new features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>The “Descent” tab displays the range to the rocket,
which is a combination of the over-the-ground
distance to the rockets current latitude/longitude
-and the height of the rocket. As such, it’s useful
+and the height of the rocket. As such, it’s useful
for knowing how far away the rocket is, but
difficult to use when estimating where the rocket
might eventually land. A new “Ground Distance” field
has been added which displays the distance to a spot
-right underneath the rocket.
-</li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Creating a Google Earth file (KML) from on-board
+right underneath the rocket.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltosUI fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Creating a Google Earth file (KML) from on-board
flight data (EEPROM) would generate an empty
file. The code responsible for reading the EEPROM
-file wasn’t ever setting the GPS valid bits, and so
+file wasn’t ever setting the GPS valid bits, and so
the KML export code thought there was no GPS data in
-the file.
-</li><li class="listitem">
-The “Landed” tab was displaying all values in metric
+the file.</p>
+</li>
+<li>
+<p>The “Landed” tab was displaying all values in metric
units, even when AltosUI was configured to display
imperial units. Somehow I just missed this tab when
-doing the units stuff.
-</li><li class="listitem">
-Sensor data wasn’t being displayed for TeleMini
+doing the units stuff.</p>
+</li>
+<li>
+<p>Sensor data wasn’t being displayed for TeleMini
flight computers in Monitor Idle mode, including
things like battery voltage. The code that picked
which kinds of data to fetch from the flight
computer was missing a check for TeleMini when
-deciding whether to fetch the analog sensor data.
-</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_1_2"></a>F.14. Release Notes for Version 1.1</h2></div></div></div><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 class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_12"></a>F.14.1. AltOS</h3></div></div></div><p>AltOS Firmware New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Add apogee-lockout value. Overrides the apogee
+deciding whether to fetch the analog sensor data.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_1_2">F.36. 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_34">F.36.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS Firmware New Features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add apogee-lockout value. Overrides the apogee
detection logic to prevent incorrect apogee charge
-firing.
-</li><li class="listitem">
-Force the radio frequency to 434.550MHz when the
+firing.</p>
+</li>
+<li>
+<p>Force the radio frequency to 434.550MHz when the
debug clock pin is connected to ground at boot
time. This provides a way to talk to a TeleMini
-which is configured to some unknown frequency.
-</li><li class="listitem">
-Provide RSSI values for Monitor Idle mode. This
+which is configured to some unknown frequency.</p>
+</li>
+<li>
+<p>Provide RSSI values for Monitor Idle mode. This
makes it easy to check radio range without needing
-to go to flight mode.
-</li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Fix a bug where the data reported in telemetry
-packets was from 320ms ago.
-</li><li class="listitem">
-Fix a bug which caused the old received telemetry
+to go to flight mode.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltOS Fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Fix a bug where the data reported in telemetry
+packets was from 320ms ago.</p>
+</li>
+<li>
+<p>Fix a bug which caused the old received telemetry
packets to be retransmitted over the USB link when
-the radio was turned off and back on.
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_3"></a>F.14.2. AltosUI</h3></div></div></div><p>AltosUI New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Make the look-n-feel configurable, providing a choice from
-the available options.
-</li><li class="listitem">
-Add an <span class="emphasis"><em>Age</em></span> element to mark how long since a
+the radio was turned off and back on.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_7">F.36.2. AltosUI</h4>
+<div class="paragraph">
+<p>AltosUI New Features:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Make the look-n-feel configurable, providing a choice from
+the available options.</p>
+</li>
+<li>
+<p>Add an 'Age' element to mark how long since a
telemetry packet has been received. Useful to
quickly gauge whether communications with the rocket
-are still active.
-</li><li class="listitem">
-Add <span class="emphasis"><em>Configure Ground Station</em></span> dialog to set the
+are still active.</p>
+</li>
+<li>
+<p>Add 'Configure Ground Station' dialog to set the
radio frequency used by a particular TeleDongle
-without having to go through the flight monitor UI.
-</li><li class="listitem">
-Add configuration for the new apogee-lockout
+without having to go through the flight monitor UI.</p>
+</li>
+<li>
+<p>Add configuration for the new apogee-lockout
value. A menu provides a list of reasonable values,
-or the value can be set by hand.
-</li><li class="listitem">
-Add Imperial units mode to present data in feet
-instead of meters.
-</li></ul></div><p>AltosUI Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Fix a bug that caused GPS ready to happen too
+or the value can be set by hand.</p>
+</li>
+<li>
+<p>Add Imperial units mode to present data in feet
+instead of meters.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltosUI Fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Fix a bug that caused GPS ready to happen too
quickly. The software was using every telemetry
packet to signal new GPS data, which caused GPS
ready to be signalled after 10 packets instead of 10
-GPS updates.
-</li><li class="listitem">
-Fix Google Earth data export to work with recent
+GPS updates.</p>
+</li>
+<li>
+<p>Fix Google Earth data export to work with recent
versions. The google earth file loading code got a
lot pickier, requiring some minor white space
-changes in the export code.
-</li><li class="listitem">
-Changed how flight data are downloaded. Now there’s
+changes in the export code.</p>
+</li>
+<li>
+<p>Changed how flight data are downloaded. Now there’s
an initial dialog asking which flights to download,
and after that finishes, a second dialog comes up
-asking which flights to delete.
-</li><li class="listitem">
-Re-compute time spent in each state for the flight
+asking which flights to delete.</p>
+</li>
+<li>
+<p>Re-compute time spent in each state for the flight
graph; this figures out the actual boost and landing
times instead of using the conservative values
provide by the flight electronics. This improves the
accuracy of the boost acceleration and main descent
-rate computations.
-</li><li class="listitem">
-Make AltosUI run on Mac OS Lion. The default Java
+rate computations.</p>
+</li>
+<li>
+<p>Make AltosUI run on Mac OS Lion. The default Java
heap space was dramatically reduced for this release
causing much of the UI to fail randomly. This most
often affected the satellite mapping download and
-displays.
-</li><li class="listitem">
-Change how data are displayed in the <span class="emphasis"><em>table</em></span> tab of
+displays.</p>
+</li>
+<li>
+<p>Change how data are displayed in the 'table' tab of
the flight monitoring window. This eliminates
entries duplicated from the header and adds both
current altitude and pad altitude, which are useful
-in <span class="emphasis"><em>Monitor Idle</em></span> mode.
-</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_0_1"></a>F.15. Release Notes for Version 1.0.1</h2></div></div></div><p>Version 1.0.1 is a major release, adding support for the
-TeleMini device and lots of new AltosUI features</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_13"></a>F.15.1. AltOS</h3></div></div></div><p>AltOS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Add TeleMini v1.0 support.
-</li><li class="listitem">
-Support operation of TeleMetrum with the antenna pointing
+in 'Monitor Idle' mode.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_1_0_1">F.37. 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_35">F.37.1. AltOS</h4>
+<div class="paragraph">
+<p>AltOS New Features</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add TeleMini v1.0 support.</p>
+</li>
+<li>
+<p>Support operation of TeleMetrum with the antenna pointing
aft. Previous firmware versions required the antenna to be
pointing upwards, now there is a configuration option
allowing the antenna to point aft, to aid installation in
-some airframes.
-</li><li class="listitem">
-Ability to disable telemetry. For airframes where an antenna
-just isn’t possible, or where radio transmissions might
-cause trouble with other electronics, there’s a
+some airframes.</p>
+</li>
+<li>
+<p>Ability to disable telemetry. For airframes where an antenna
+just isn’t possible, or where radio transmissions might
+cause trouble with other electronics, there’s a
configuration option to disable all telemetry. Note that the
-board will still enable the radio link in idle mode.
-</li><li class="listitem">
-Arbitrary frequency selection. The radios in Altus Metrum
+board will still enable the radio link in idle mode.</p>
+</li>
+<li>
+<p>Arbitrary frequency selection. The radios in Altus Metrum
devices can be programmed to a wide range of frequencies, so
-instead of limiting devices to 10 pre-selected <span class="emphasis"><em>channels</em></span>,
+instead of limiting devices to 10 pre-selected 'channels',
the new firmware allows the user to choose any frequency in
the 70cm band. Note that the RF matching circuit on the
boards is tuned for around 435MHz, so frequencies far from
-that may reduce the available range.
-</li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Change telemetry to be encoded in multiple 32-byte
+that may reduce the available range.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltOS Fixes</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Change telemetry to be encoded in multiple 32-byte
packets. This enables support for TeleMini and other devices
without requiring further updates to the TeleDongle
-firmware.
-</li><li class="listitem">
-Kalman-filter based flight-tracking. The model based sensor
+firmware.</p>
+</li>
+<li>
+<p>Kalman-filter based flight-tracking. The model based sensor
fusion approach of a Kalman filter means that AltOS now
computes apogee much more accurately than before, generally
within a fraction of a second. In addition, this approach
allows the baro-only TeleMini device to correctly identify
Mach transitions, avoiding the error-prone selection of a
-Mach delay.
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_6"></a>F.15.2. AltosUI Application</h3></div></div></div><p>AltosUI New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Add main/apogee voltage graphs to the data
+Mach delay.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_application_6">F.37.2. AltosUI Application</h4>
+<div class="paragraph">
+<p>AltosUI New Features</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Add main/apogee voltage graphs to the data
plot. This provides a visual indication if the
-igniters fail before being fired.
-</li><li class="listitem">
-Scan for altimeter devices by watching the defined
+igniters fail before being fired.</p>
+</li>
+<li>
+<p>Scan for altimeter devices by watching the defined
telemetry frequencies. This avoids the problem of
remembering what frequency a device was configured
to use, which is especially important with TeleMini
-which does not include a USB connection.
-</li><li class="listitem">
-Monitor altimeter state in "Idle" mode. This
+which does not include a USB connection.</p>
+</li>
+<li>
+<p>Monitor altimeter state in "Idle" mode. This
provides much of the information presented in the
"Pad" dialog from the Monitor Flight command,
monitoring the igniters, battery and GPS status
withing requiring the flight computer to be armed
-and ready for flight.
-</li><li class="listitem">
-Pre-load map images from home. For those launch
-sites which don’t provide free Wi-Fi, this allows
+and ready for flight.</p>
+</li>
+<li>
+<p>Pre-load map images from home. For those launch
+sites which don’t provide free Wi-Fi, this allows
you to download the necessary satellite images
given the location of the launch site. A list of
known launch sites is maintained at altusmetrum.org
which AltosUI downloads to populate a menu; if
-you’ve got a launch site not on that list, please
+you’ve got a launch site not on that list, please
send the name of it, latitude and longitude along
with a link to the web site of the controlling club
-to the altusmetrum mailing list.
-</li><li class="listitem">
-Flight statistics are now displayed in the Graph
+to the altusmetrum mailing list.</p>
+</li>
+<li>
+<p>Flight statistics are now displayed in the Graph
data window. These include max height/speed/accel,
average descent rates and a few other bits of
information. The Graph Data window can now be
-reached from the <span class="emphasis"><em>Landed</em></span> tab in the Monitor Flight
+reached from the 'Landed' tab in the Monitor Flight
window so you can immediately see the results of a
-flight.
-</li></ul></div><p>AltosUI Changes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Wait for altimeter when using packet mode. Instead
+flight.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>AltosUI Changes</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Wait for altimeter when using packet mode. Instead
of quicly timing out when trying to initialize a
packet mode configuration connection, AltosUI now
waits indefinitely for the remote device to appear,
providing a cancel button should the user get
bored. This is necessary as the TeleMini can only be
-placed in "Idle" mode if AltosUI is polling it.
-</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_0_9_2"></a>F.16. Release Notes for Version 0.9.2</h2></div></div></div><p>Version 0.9.2 is an AltosUI bug-fix release, with no firmware
-changes.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_4"></a>F.16.1. AltosUI</h3></div></div></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Fix plotting problems due to missing file in the Mac
-OS install image.
-</li><li class="listitem">
-Always read whole eeprom blocks, mark empty records
-invalid, display parsing errors to user.
-</li><li class="listitem">
-Add software version to Configure AltosUI dialog
-</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_0_9"></a>F.17. Release Notes for Version 0.9</h2></div></div></div><p>Version 0.9 adds a few new firmware features and accompanying
-AltosUI changes, along with new hardware support.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_14"></a>F.17.1. AltOS</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Support for TeleMetrum v1.1 hardware. Sources for the flash
+placed in "Idle" mode if AltosUI is polling it.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_0_9_2">F.38. 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_8">F.38.1. AltosUI</h4>
+<div class="paragraph">
+<p>AltosUI fixes:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Fix plotting problems due to missing file in the Mac
+OS install image.</p>
+</li>
+<li>
+<p>Always read whole eeprom blocks, mark empty records
+invalid, display parsing errors to user.</p>
+</li>
+<li>
+<p>Add software version to Configure AltosUI dialog</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_0_9">F.39. 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_36">F.39.1. AltOS</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Support for TeleMetrum v1.1 hardware. Sources for the flash
memory part used in v1.0 dried up, so v1.1 uses a different
part which required a new driver and support for explicit
-flight log erasing.
-</li><li class="listitem">
-Multiple flight log support. This stores more than one
+flight log erasing.</p>
+</li>
+<li>
+<p>Multiple flight log support. This stores more than one
flight log in the on-board flash memory. It also requires
-the user to explicitly erase flights so that you won’t lose
+the user to explicitly erase flights so that you won’t lose
flight logs just because you fly the same board twice in one
-day.
-</li><li class="listitem">
-Telemetry support for devices with serial number >= 256.
+day.</p>
+</li>
+<li>
+<p>Telemetry support for devices with serial number >= 256.
Previous versions used a telemetry packet format that
provided only 8 bits for the device serial number. This
change requires that both ends of the telemetry link be
-running the 0.9 firmware or they will not communicate.
-</li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_7"></a>F.17.2. AltosUI Application</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Support for telemetry format changes.
-</li><li class="listitem">
-Support for multiple flight logs.
-</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_0_8"></a>F.18. Release Notes for Version 0.8</h2></div></div></div><p>Version 0.8 offers a major upgrade in the AltosUI
-interface.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_8"></a>F.18.1. AltosUI Application:</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Post-flight graphing tool. This lets you explore the
+running the 0.9 firmware or they will not communicate.</p>
+</li>
+</ul>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_altosui_application_7">F.39.2. AltosUI Application</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Support for telemetry format changes.</p>
+</li>
+<li>
+<p>Support for multiple flight logs.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_0_8">F.40. 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.40.1. AltosUI Application:</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Post-flight graphing tool. This lets you explore the
behaviour of your rocket after flight with a scroll-able and
zoom-able chart showing the altitude, speed and acceleration
of the airframe along with events recorded by the flight
computer. You can export graphs to PNG files, or print them
-directly.
-</li><li class="listitem">
-Real-time moving map which overlays the in-progress flight
+directly.</p>
+</li>
+<li>
+<p>Real-time moving map which overlays the in-progress flight
on satellite imagery fetched from Google Maps. This lets you
see in pictures where your rocket has landed, allowing you
-to plan recovery activities more accurately.
-</li><li class="listitem">
-Wireless recovery system testing. Prep your rocket for
+to plan recovery activities more accurately.</p>
+</li>
+<li>
+<p>Wireless recovery system testing. Prep your rocket for
flight and test fire the deployment charges to make sure
things work as expected. All without threading wires through
-holes in your airframe.
-</li><li class="listitem">
-Optimized flight status displays. Each flight state now has
-it’s own custom <span class="emphasis"><em>tab</em></span> in the flight monitoring window so you
+holes in your airframe.</p>
+</li>
+<li>
+<p>Optimized flight status displays. Each flight state now has
+it’s own custom 'tab' in the flight monitoring window so you
can focus on the most important details. Pre-flight, the
system shows a set of red/green status indicators for
battery voltage, apogee/main igniter continutity and GPS
-reception. Wait until they’re all green and your rocket is
+reception. Wait until they’re all green and your rocket is
ready for flight. There are also tabs for ascent, descent
and landing along with the original tabular view of the
-data.
-</li><li class="listitem">
-Monitor multiple flights simultaneously. If you have more
+data.</p>
+</li>
+<li>
+<p>Monitor multiple flights simultaneously. If you have more
than one TeleDongle, you can monitor a flight with each one
-on the same computer.
-</li><li class="listitem">
-Automatic flight monitoring at startup. Plug TeleDongle into
+on the same computer.</p>
+</li>
+<li>
+<p>Automatic flight monitoring at startup. Plug TeleDongle into
the machine before starting AltosUI and it will
-automatically connect to it and prepare to monitor a flight.
-</li><li class="listitem">
-Exports Google Earth flight tracks. Using the Keyhole Markup
+automatically connect to it and prepare to monitor a flight.</p>
+</li>
+<li>
+<p>Exports Google Earth flight tracks. Using the Keyhole Markup
Language (.kml) file format, this provides a 3D view of your
-rocket flight through the Google Earth program.
-</li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_0_7_1"></a>F.19. Release Notes for Version 0.7.1</h2></div></div></div><p>Version 0.7.1 is the first release containing our new
-cross-platform Java-based user interface.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_9"></a>F.19.1. AltosUI Application</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
-Receive and log telemetry from a connected TeleDongle
+rocket flight through the Google Earth program.</p>
+</li>
+</ul>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_release_notes_for_version_0_7_1">F.41. 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.41.1. AltosUI Application</h4>
+<div class="ulist">
+<ul>
+<li>
+<p>Receive and log telemetry from a connected TeleDongle
device. All data received is saved to log files named with
the current date and the connected rocket serial and flight
numbers. There is no mode in which telemetry data will not
-be saved.
-</li><li class="listitem">
-Download logged data from TeleMetrum devices, either through
+be saved.</p>
+</li>
+<li>
+<p>Download logged data from TeleMetrum devices, either through
a direct USB connection or over the air through a TeleDongle
-device.
-</li><li class="listitem">
-Configure a TeleMetrum device, setting the radio channel,
+device.</p>
+</li>
+<li>
+<p>Configure a TeleMetrum device, setting the radio channel,
callsign, apogee delay and main deploy height. This can be
done through either a USB connection or over a radio link
-via a TeleDongle device.
-</li><li class="listitem">
-Replay a flight in real-time. This takes a saved telemetry
+via a TeleDongle device.</p>
+</li>
+<li>
+<p>Replay a flight in real-time. This takes a saved telemetry
log or eeprom download and replays it through the user
-interface so you can relive your favorite rocket flights.
-</li><li class="listitem">
-Reprogram Altus Metrum devices. Using an Altus Metrum device
+interface so you can relive your favorite rocket flights.</p>
+</li>
+<li>
+<p>Reprogram Altus Metrum devices. Using an Altus Metrum device
connected via USB, another Altus Metrum device can be
reprogrammed using the supplied programming cable between
-the two devices.
-</li><li class="listitem">
-Export Flight data to a comma-separated-values file. This
+the two devices.</p>
+</li>
+<li>
+<p>Export Flight data to a comma-separated-values file. This
takes either telemetry or on-board flight data and generates
data suitable for use in external applications. All data is
exported using standard units so that no device-specific
-knowledge is needed to handle the data.
-</li><li class="listitem">
-Speak to you during the flight. Instead of spending the
+knowledge is needed to handle the data.</p>
+</li>
+<li>
+<p>Speak to you during the flight. Instead of spending the
flight hunched over your laptop looking at the screen, enjoy
the view while the computer tells you what’s going on up
there. During ascent, you hear the current flight state and
altitude information. During descent, you get azimuth,
elevation and range information to try and help you find
your rocket in the air. Once on the ground, the direction
-and distance are reported.
-</li></ul></div></div></div></div></div></body></html>
\ No newline at end of file
+and distance are reported.</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div id="footer">
+<div id="footer-text">
+Version v1.9.8<br>
+Last updated 2021-09-20 21:44:12 -0600
+</div>
+</div>
+</body>
+</html>
\ No newline at end of file
projects / web / altusmetrum / blobdiff