1 <?xml version="1.0" encoding="UTF-8"?>
2 <!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>EasyMini Owner’s Manual</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.79.1" /></head><body><div xml:lang="en" class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a id="idm1"></a>EasyMini Owner’s Manual</h1></div><div><h2 class="subtitle">A Dual-Deploy Rocketry Flight Computer</h2></div><div><h3 class="corpauthor">
3 <span class="inlinemediaobject"><img src="altusmetrum-oneline.svg" width="270" /></span>
4 </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><p class="copyright">Copyright © 2016 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm23"></a><p>
5 This document is released under the terms of the
6 <a class="ulink" href="http://creativecommons.org/licenses/by-sa/3.0/" target="_top">
7 Creative Commons ShareAlike 3.0
10 </p></div></div><div><a href="easymini-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
11 Mere-Mortals Quick Start/Usage Guide to the Altus Metrum Starter
12 Kit” which formed the basis of the original Getting Started chapter
13 in this manual. Bob was one of our first customers for a production
14 TeleMetrum, and his continued enthusiasm and contributions
15 are immensely gratifying and highly appreciated!</p><p>And thanks to Anthony (AJ) Towns for major contributions including
16 the AltosUI graphing and site map code and associated documentation.
17 Free software means that our customers and friends can become our
18 collaborators, and we certainly appreciate this level of
19 contribution!</p><p>Have fun using these products, and we hope to meet all of you
20 out on the rocket flight line somewhere.</p><div class="blockquote"><blockquote class="blockquote"><div class="literallayout"><p>Bdale Garbee, KB0G<br />
21 NAR #87103, TRA #12201</p></div></blockquote></div><div class="blockquote"><blockquote class="blockquote"><div class="literallayout"><p>Keith Packard, KD7SQG<br />
22 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="#_linux_mac_windows_ground_station_software">2.2. Linux/Mac/Windows 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><dt><span class="section"><a href="#_using_packet_link_mode">3.10. Using Packet Link Mode</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_easymini">4. EasyMini</a></span></dt><dd><dl><dt><span class="section"><a href="#_easymini_screw_terminals">4.1. EasyMini Screw Terminals</a></span></dt><dt><span class="section"><a href="#_connecting_a_battery_to_easymini">4.2. Connecting A Battery To EasyMini</a></span></dt><dt><span class="section"><a href="#_charging_lithium_batteries">4.3. Charging Lithium Batteries</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery_with_easymini">4.4. Using a Separate Pyro Battery with EasyMini</a></span></dt><dt><span class="section"><a href="#_using_an_active_switch_with_easymini">4.5. Using an Active Switch with EasyMini</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_installation">5. Installation</a></span></dt><dt><span class="chapter"><a href="#_using_altus_metrum_products">6. Using Altus Metrum Products</a></span></dt><dd><dl><dt><span class="section"><a href="#_in_the_rocket">6.1. In the Rocket</a></span></dt><dt><span class="section"><a href="#_on_the_ground">6.2. On the Ground</a></span></dt><dt><span class="section"><a href="#_data_analysis">6.3. Data Analysis</a></span></dt><dt><span class="section"><a href="#_future_plans">6.4. Future Plans</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_altosui">7. AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#_save_flight_data">7.1. Save Flight Data</a></span></dt><dt><span class="section"><a href="#_replay_flight">7.2. Replay Flight</a></span></dt><dt><span class="section"><a href="#_graph_data">7.3. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#_flight_graph">7.3.1. Flight Graph</a></span></dt><dt><span class="section"><a href="#_configure_graph">7.3.2. Configure Graph</a></span></dt><dt><span class="section"><a href="#_flight_statistics">7.3.3. Flight Statistics</a></span></dt></dl></dd><dt><span class="section"><a href="#_export_data">7.4. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#_comma_separated_value_format">7.4.1. Comma Separated Value Format</a></span></dt></dl></dd><dt><span class="section"><a href="#_configure_altimeter">7.5. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#_main_deploy_altitude">7.5.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#_apogee_delay">7.5.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#_apogee_lockout">7.5.3. Apogee Lockout</a></span></dt><dt><span class="section"><a href="#_maximum_flight_log_size">7.5.4. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#_ignitor_firing_mode">7.5.5. Ignitor Firing Mode</a></span></dt><dt><span class="section"><a href="#_beeper_frequency">7.5.6. Beeper Frequency</a></span></dt></dl></dd><dt><span class="section"><a href="#_configure_altosui">7.6. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#_log_directory">7.6.1. Log Directory</a></span></dt><dt><span class="section"><a href="#_imperial_units">7.6.2. Imperial Units</a></span></dt><dt><span class="section"><a href="#_serial_debug">7.6.3. Serial Debug</a></span></dt><dt><span class="section"><a href="#_font_size">7.6.4. Font size</a></span></dt><dt><span class="section"><a href="#_look_amp_feel">7.6.5. Look & feel</a></span></dt><dt><span class="section"><a href="#_menu_position">7.6.6. Menu position</a></span></dt></dl></dd><dt><span class="section"><a href="#_flash_image">7.7. Flash Image</a></span></dt><dt><span class="section"><a href="#_fire_igniter">7.8. Fire Igniter</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="#_ground_testing">A.2. Ground Testing</a></span></dt><dt><span class="section"><a href="#_configurable_parameters">A.3. 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_easymini_firmware">C.1. Updating EasyMini 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></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_8_6">F.1. Release Notes for Version 1.8.6</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_telegps">F.1.2. AltosUI, TeleGPS</a></span></dt><dt><span class="section"><a href="#_micropeak">F.1.3. MicroPeak</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_8_5">F.2. Release Notes for Version 1.8.5</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_telegps_2">F.2.2. AltosUI, TeleGPS</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_8_4">F.3. Release Notes for Version 1.8.4</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_3">F.3.1. AltOS</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_8_3">F.4. Release Notes for Version 1.8.3</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">F.4.2. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_8_2">F.5. Release Notes for Version 1.8.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_5">F.5.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_2">F.5.2. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_8_1">F.6. Release Notes for Version 1.8.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_6">F.6.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_3">F.6.2. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_8">F.7. Release Notes for Version 1.8</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_7">F.7.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_4">F.7.2. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_7">F.8. Release Notes for Version 1.7</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_8">F.8.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_5">F.8.2. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_8">F.9. Release Notes for Version 1.6.8</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_9">F.9.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_telegps_and_altosdroid_applications">F.9.2. AltosUI, TeleGPS and AltosDroid Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_5">F.10. Release Notes for Version 1.6.5</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_10">F.10.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_telegps_and_altosdroid_applications_2">F.10.2. AltosUI, TeleGPS and AltosDroid Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_4">F.11. Release Notes for Version 1.6.4</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_11">F.11.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_telegps_and_altosdroid_applications_3">F.11.2. AltosUI, TeleGPS and AltosDroid Applications</a></span></dt><dt><span class="section"><a href="#_documentation">F.11.3. Documentation</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_3">F.12. Release Notes for Version 1.6.3</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_12">F.12.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_6">F.12.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_altosdroid">F.12.3. AltosDroid</a></span></dt><dt><span class="section"><a href="#_documentation_2">F.12.4. Documentation</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_2">F.13. Release Notes for Version 1.6.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_13">F.13.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_7">F.13.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_documentation_3">F.13.3. Documentation</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="#idm284">EasyMini Board</a></dt><dt>7.1. <a href="#idm415">AltosUI Main Window</a></dt><dt>7.2. <a href="#idm442">Flight Data Graph</a></dt><dt>7.3. <a href="#idm453">Flight Graph Configuration</a></dt><dt>7.4. <a href="#idm472">Flight Statistics</a></dt><dt>7.5. <a href="#idm490">Altimeter Configuration</a></dt><dt>7.6. <a href="#idm562">Configure AltosUI Dialog</a></dt><dt>7.7. <a href="#idm596">Fire Igniter Window</a></dt></dl></div><div class="list-of-tables"><p><strong>List of Tables</strong></p><dl><dt>3.1. <a href="#idm96">AltOS Modes</a></dt><dt>3.2. <a href="#idm204">Pad/Idle Indications</a></dt><dt>4.1. <a href="#idm296">EasyMini Screw Terminals</a></dt><dt>D.1. <a href="#idm696">Data Storage on Altus Metrum altimeters</a></dt><dt>E.1. <a href="#idm727">Altus Metrum Flight Computer Electronics</a></dt><dt>E.2. <a href="#idm784">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
23 our passion for both hobby rocketry and Free Software. We hope their
24 capabilities and performance will delight you in every way, but by
25 releasing all of our hardware and software designs under open licenses,
26 we also hope to empower you to take as active a role in our collective
27 future as you wish!</p><p>Our goal is to include in this document all of the information required
28 to successfully configure and use Altus Metrum products. But
29 documentation is a lot like software in that it can contain "bugs",
30 and can probably always be improved! If you have questions that
31 aren’t answered in this manual, or just need a little help figuring
32 things out, we strongly suggest joining the Altus Metrum user email
33 list, which you can do by visiting
34 <a class="ulink" href="https://lists.gag.com/mailman/listinfo/altusmetrum" target="_top">https://lists.gag.com/mailman/listinfo/altusmetrum</a>. There’s a lot
35 of useful information in the mailing list archives!</p><p>The first device created for our community was TeleMetrum, a dual
36 deploy altimeter with fully integrated GPS and radio telemetry
37 as standard features, and a “companion interface” that will
38 support optional capabilities in the future. The latest version
39 of TeleMetrum, v2.0, has all of the same features but with
40 improved sensors and radio to offer increased performance.</p><p>Our second device was TeleMini, a dual deploy altimeter with
41 radio telemetry and radio direction finding. The first version
42 of this device was only 13mm by 38mm (½ inch by 1½ inches) and
43 could fit easily in an 18mm air-frame. The latest version, v3.0,
44 includes a beeper, higher power radio, extended on-board
45 flight logging and an improved barometric sensor.</p><p>TeleMega is our most sophisticated device, including six pyro
46 channels (four of which are fully programmable), integrated GPS,
47 integrated gyroscopes for staging/air-start inhibit and high
48 performance telemetry.</p><p>EasyMini is a dual-deploy altimeter with logging and built-in
49 USB data download.</p><p>EasyMega is essentially a TeleMega board with the GPS receiver
50 and telemetry transmitter removed. It offers the same 6 pyro
51 channels and integrated gyroscopes for staging/air-start inhibit.</p><p>TeleDongle v0.2 was our first ground station, providing a USB to RF
52 interfaces for communicating with the altimeters. Combined with
53 your choice of antenna and notebook computer, TeleDongle and our
54 associated user interface software form a complete ground
55 station capable of logging and displaying in-flight telemetry,
56 aiding rocket recovery, then processing and archiving flight
57 data for analysis and review. The latest version, TeleDongle
58 v3, has all new electronics with a higher performance radio
59 for improved range.</p><p>For a slightly more portable ground station experience that also
60 provides direct rocket recovery support, TeleBT offers flight
61 monitoring and data logging using a Bluetooth™ connection between
62 the receiver and an Android device that has the AltosDroid
63 application installed from the Google Play store.</p><p>More products will be added to the Altus Metrum family over time, and
64 we currently envision that this will be a single, comprehensive manual
65 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
66 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>The Lithium Polymer
67 EasyMini battery can be charged by disconnecting it
68 from the board and plugging it into a standalone
69 battery charger such as <a class="ulink" href="http://altusmetrum.org/LipoCharger" target="_top">LipoCharger</a>, and
70 connecting that via a USB cable to a laptop or other
71 USB power source.</p><p>You can also choose to use another battery with
72 EasyMini, anything supplying between 4 and 12 volts should
73 work fine (like a standard 9V battery), but if you are planning
74 to fire pyro charges, ground testing is required to verify that
75 the battery supplies enough current to fire your chosen e-matches.</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.2. Linux/Mac/Windows Ground Station Software</h2></div></div></div><p>Next you should obtain and install the AltOS software.
76 The AltOS distribution includes the AltosUI ground
77 station program, current firmware images for all of
78 the hardware, and a number of standalone utilities
79 that are rarely needed. Pre-built binary packages are
80 available for Linux, Microsoft Windows, Mac OSX. Full
81 source code and build instructions are also
82 available. The latest version may always be downloaded
83 from <a class="ulink" href="http://altusmetrum.org/AltOS" target="_top">http://altusmetrum.org/AltOS</a></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
84 flight computer. Instructions specific to each model will be
85 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
86 operation of the flight computer, it’s important to always
87 twist pairs of wires connected to the board. Twist the switch
88 leads, the pyro leads and the battery leads. This reduces
89 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
90 series connector to connect up a single-cell Lithium Polymer
91 cell (3.7V nominal). You can purchase matching batteries
92 from the Altus Metrum store, or other vendors, or you can
93 make your own. Pin 1 of the connector is positive, pin 2 is
94 negative. Spark Fun sells a cable with the connector
95 attached, which they call a
96 <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
97 this same connector. All that we have found use the opposite
98 polarity, and if you use them that way, you will damage or
99 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
100 each pyro charge. This means you shouldn’t need to put two
101 wires into a screw terminal or connect leads from pyro
102 charges together externally.</p><p>On the flight computer, one lead from each charge is hooked
103 to the positive battery terminal through the power switch.
104 The other lead is connected through the pyro circuit, which
105 is connected to the negative battery terminal when the pyro
106 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
107 to turn them on. This disconnects both the computer and the
108 pyro charges from the battery, preventing the charges from
109 firing when in the Off position. The switch is in-line with
110 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
111 provide information about the state of the system.</p><p>Here’s a short summary of all of the modes and the
113 that accompanies each mode. In the description of the
114 beeping pattern, “dit” means a short beep while "dah"
115 means a long beep (three times as long). “Brap” means
116 a long dissonant tone.</p><div class="table"><a id="idm96"></a><p class="title"><strong>Table 3.1. AltOS Modes</strong></p><div class="table-contents"><table class="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</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
117 indications. In Idle mode, you’ll hear one of these
118 just once after the two short dits indicating idle
119 mode. In Pad mode, after the dit dah dah dit
120 indicating Pad mode, you’ll hear these once every five
121 seconds.</p><div class="table"><a id="idm204"></a><p class="title"><strong>Table 3.2. Pad/Idle Indications</strong></p><div class="table-contents"><table class="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
122 not prevent the flight computer from safely
123 controlling the flight or transmitting telemetry
124 signals, but no record of the flight will be
125 stored in on-board flash.</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="_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
126 to "on". The flight computer will signal power on by
127 reporting the battery voltage and then perform an internal self
128 test and sensor calibration.</p><p>Once the self test and calibration are complete, there
129 are two modes that an Altus Metrum flight computer can
130 operate in:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
133 The flight computer is waiting to detect
134 launch and then fly the rocket. In this mode, the USB
137 The only way to get out of this
138 mode is to power the flight computer down. See below for how to get the flight
139 computer to come up in Flight/Pad mode at power on.
140 </dd><dt><span class="term">
143 The flight computer is ready to communicate over USB
145 the flight computer, download data or display
146 the current state. See below for how to get the flight
147 computer to come up in Idle mode at power on.
148 </dd></dl></div><p>For EasyMini, if the USB cable is connected to a
149 computer, it will enter Idle mode. Otherwise, it will
150 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>
151 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
152 Featherweight Magnetic Switch, with any Altus Metrum
153 flight computer. These require three connections, one to
154 the battery, one to the positive power input on the flight
155 computer and one to ground. Find instructions on how to
156 hook these up for each flight computer below. Then follow
157 the instructions that come with your active switch to
158 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
159 lead for each of the pyro charges is connected through
160 the power switch directly to the positive battery
161 terminal. The other lead is connected to the pyro
162 circuit, which connects it to the negative battery
163 terminal when the pyro circuit is fired. The pyro
164 circuit on all of the flight computers is designed to
165 handle up to 16V.</p><p>To use a separate pyro battery, connect the negative pyro
166 battery terminal to the flight computer ground terminal,
167 the positive battery terminal to the igniter and the other
168 igniter lead to the negative pyro terminal on the flight
169 computer. When the pyro channel fires, it will complete the
170 circuit between the negative pyro terminal and the ground
171 terminal, firing the igniter. Specific instructions on how
172 to hook this up for each flight computer will be found
173 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
175 designed to use either a
176 lithium polymer battery or any other battery producing
177 between 4 and 12 volts, such as a rectangular 9V
178 battery.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_packet_link_mode"></a>3.10. Using Packet Link Mode</h2></div></div></div><p>All AltusMetrum flight computers that have a radio can
179 communicate with the ground station software for
180 configuration and other operations using the Packet
181 Link mode. This uses radio communication instead of a
182 USB cable. To set this up, the ground station software
183 must be configured to the correct data rate, frequency
184 and callsign.</p><p>You can monitor Packet Link mode from TeleBT or
185 TeleDongle by watching the LEDs. Each time the device
186 transmits, the red LED will flash. When the link is
187 busy, or when the link is not working, the device will
188 transmit 10 times per second, so the LED will flash
189 rapidly. When the link is working and there is no data
190 to send, the link will flash once per second, and the
191 LED will flash more slowly.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_easymini"></a>Chapter 4. EasyMini</h1></div></div></div><div class="figure"><a id="idm284"></a><p class="title"><strong>Figure 4.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
192 designed to fit in a 24mm coupler tube.</p><p>You usually don’t need to configure EasyMini at all; it’s set
193 up to do dual-deployment with an event at apogee to separate
194 the airframe and deploy a drogue and another event at 250m
195 (820ft) to deploy the main. Install EasyMini in your airframe,
196 hook up a battery, igniters and a power switch and you’re
197 ready to fly.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_easymini_screw_terminals"></a>4.1. EasyMini Screw Terminals</h2></div></div></div><p>EasyMini has two sets of four screw terminals near one end of the
198 board. Using the picture
199 above, the top four have connections for the main pyro
200 circuit and an external battery and the bottom four have
201 connections for the apogee pyro circuit and the power
202 switch. Counting from the left, the connections are as follows:</p><div class="table"><a id="idm296"></a><p class="title"><strong>Table 4.1. EasyMini Screw Terminals</strong></p><div class="table-contents"><table class="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>4.2. Connecting A Battery To EasyMini</h2></div></div></div><p>There are two possible battery connections on
203 EasyMini. You can use either method; both feed
204 through the power switch terminals.</p><p>One battery connection is the standard Altus Metrum
205 white JST plug. This mates with single-cell Lithium
206 Polymer batteries sold by Altus Metrum.</p><p>The other is a pair of screw terminals marked <span class="emphasis"><em>Battery
207 +</em></span> and <span class="emphasis"><em>Battery -</em></span>. Connect a battery from 4 to 12
208 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>4.3. Charging Lithium Batteries</h2></div></div></div><p>Because EasyMini allows for batteries other than the
209 standard Altus Metrum Lithium Polymer cells, it cannot
210 incorporate a battery charger circuit. Therefore, when
211 using a Litium Polymer cell, you’ll need an external
212 charger. These are available from Altus Metrum, or
213 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>4.4. Using a Separate Pyro Battery with EasyMini</h2></div></div></div><p>As described above, using an external pyro battery involves
214 connecting the negative battery terminal to the flight
215 computer ground, connecting the positive battery terminal to
216 one of the igniter leads and connecting the other igniter
217 lead to the per-channel pyro circuit connection.</p><p>To connect the negative pyro battery terminal to EasyMini
218 ground, connect it to the negative external battery
219 connection, top terminal 4.</p><p>Connecting the positive battery terminal to the pyro
220 charges must be done separate from EasyMini, by soldering
221 them together or using some other connector.</p><p>The other lead from each pyro charge is then inserted into
222 the appropriate per-pyro channel screw terminal (top
223 terminal 1 for the Main charge, bottom terminal 1 for the
224 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>4.5. Using an Active Switch with EasyMini</h2></div></div></div><p>As explained above, an external active switch requires three
225 connections, one to the positive battery terminal, one to
226 the flight computer positive input and one to ground. Use
227 the negative external battery connection, top terminal 4 for
228 ground.</p><p>The positive battery terminal is available on bottom
229 terminal 4, the positive flight computer input is on the
230 bottom terminal 3.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_installation"></a>Chapter 5. Installation</h1></div></div></div><p>A typical installation involves attaching
231 only a suitable battery, a single pole switch for
232 power on/off, and two pairs of wires connecting e-matches for the
233 apogee and main ejection charges. All Altus Metrum products are
234 designed for use with single-cell batteries with 3.7 volts
236 EasyMini may also be used with other
237 batteries as long as they supply between 4 and 12 volts.</p><p>The battery connectors are a standard 2-pin JST connector; you
238 can purchase suitable batteries from the any vendor selling
239 Altus Metrum products. These batteries are
240 single-cell Lithium Polymer batteries that nominally provide 3.7
241 volts. Other vendors sell similar batteries for RC aircraft
242 using mating connectors, however the polarity for those is
243 generally reversed from the batteries used by Altus Metrum
244 products. In particular, the Tenergy batteries supplied for use
245 in Featherweight flight computers are not compatible with Altus
246 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
247 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
248 the correct polarity. However, these batteries include an
249 integrated current limiting circuit. That circuit will cause
250 the battery to shut down when firing the igniter circuit. Do
251 not use these batteries unless you remove the current limiting
252 circuit.</p></div><p>By default, we use the unregulated output of the battery
253 directly to fire ejection charges. This works marvelously
254 with standard low-current e-matches like the J-Tek from MJG
255 Technologies, and with Quest Q2G2 igniters. However, if you
256 want or need to use a separate pyro battery, check out
257 <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
258 that up. The altimeters are designed to work with an external
259 pyro battery of no more than 15 volts.</p><p>Ejection charges are wired directly to the screw terminal block
260 at the aft end of the altimeter. You’ll need a very small straight
261 blade screwdriver for these screws, such as you might find in a
262 jeweler’s screwdriver set.
263 The screw terminal block is also used for the power switch leads.</p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_using_altus_metrum_products"></a>Chapter 6. Using Altus Metrum Products</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_in_the_rocket"></a>6.1. In the Rocket</h2></div></div></div><p>In the rocket itself, you just need a flight computer
264 and a single-cell, 3.7 volt nominal Li-Po rechargeable
266 A 110mAh battery weighs less
267 than a triple A battery and is a good choice for use
269 EasyMini.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_on_the_ground"></a>6.2. On the Ground</h2></div></div></div><p>The GUI tool, AltosUI, is written in Java and runs
270 across Linux, Mac OS and Windows. There’s also a suite
271 of C tools for Linux which can perform most of the
272 same tasks.</p><p>After the flight,
274 USB cable to plug into the flight computer board directly.
275 A USB cable is also how you
276 charge the Li-Po battery, so you’ll want one of those
277 anyway. The same cable used by lots of digital
278 cameras and other modern electronic stuff will work
279 fine.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_data_analysis"></a>6.3. Data Analysis</h2></div></div></div><p>Our software makes it easy to log the data from each
280 flight, both the telemetry received during the flight
281 itself, and the more complete data log recorded in the
282 flash memory on the altimeter board. Once this data
283 is on your computer, our post-flight tools make it
284 easy to quickly get to the numbers everyone wants,
285 like apogee altitude, max acceleration, and max
286 velocity. You can also generate and view a standard
287 set of plots showing the altitude, acceleration, and
288 velocity of the rocket during flight. And you can
289 even export a flight log in a format usable with Google
290 Maps and Google Earth for visualizing the flight path
291 in two or three dimensions!</p><p>Our ultimate goal is to emit a set of files for each
292 flight that can be published as a web page per flight,
293 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>6.4. Future Plans</h2></div></div></div><p>Because all of our work is open, both the hardware
294 designs and the software, if you have some great idea
295 for an addition to the current Altus Metrum family,
296 feel free to dive in and help! Or let us know what
297 you’d like to see that we aren’t already working on,
298 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
299 more news and information as our family of products
300 evolves!</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_altosui"></a>Chapter 7. AltosUI</h1></div></div></div><div class="figure"><a id="idm415"></a><p class="title"><strong>Figure 7.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
301 interacting with the Altus Metrum product family. AltosUI can
302 monitor telemetry data, configure devices and many other
303 tasks. The primary interface window provides a selection of
304 buttons, one for each major activity in the system. This
305 chapter is split into sections, each of which documents one of
306 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="_save_flight_data"></a>7.1. Save Flight Data</h2></div></div></div><p>The altimeter records flight data to its internal
308 The <span class="emphasis"><em>Save Flight Data</em></span> button allows you to
309 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
310 list of connected flight computers and TeleDongle
311 devices. If you select a flight computer, the flight
312 data will be downloaded from that device directly.</p><p>After the device has been selected, a dialog showing
313 the flight data saved in the device will be shown
314 allowing you to select which flights to download and
315 which to delete. With version 0.9 or newer firmware,
316 you must erase flights in order for the space they
317 consume to be reused by another flight. This prevents
318 accidentally losing flight data if you neglect to
319 download data before flying again. Note that if there
320 is no more space available in the device, then no data
321 will be recorded during the next flight.</p><p>The file name for each flight log is computed
322 automatically from the recorded flight date, altimeter
323 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>7.2. Replay Flight</h2></div></div></div><p>Select this button and you are prompted to select a flight
324 record file, either a .telem file recording telemetry data or a
325 .eeprom file containing flight data saved from the altimeter
326 flash memory.</p><p>Once a flight record is selected, the flight monitor interface
327 is displayed and the flight is re-enacted in real
328 time.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_graph_data"></a>7.3. Graph Data</h2></div></div></div><p>Select this button and you are prompted to select a flight
329 record file, either a .telem file recording telemetry data or a
330 .eeprom file containing flight data saved from
331 flash memory.</p><p>Note that telemetry files will generally produce poor graphs
332 due to the lower sampling rate and missed telemetry packets.
333 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
334 opened.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_flight_graph"></a>7.3.1. Flight Graph</h3></div></div></div><div class="figure"><a id="idm442"></a><p class="title"><strong>Figure 7.2. 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),
335 velocity (green) and altitude (red).</p><p>The graph can be zoomed into a particular area by
336 clicking and dragging down and to the right. Once
337 zoomed, the graph can be reset by clicking and
338 dragging up and to the left. Holding down control and
339 clicking and dragging allows the graph to be panned.
340 The right mouse button causes a pop-up menu to be
341 displayed, giving you the option save or print the
342 plot.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_configure_graph"></a>7.3.2. Configure Graph</h3></div></div></div><div class="figure"><a id="idm453"></a><p class="title"><strong>Figure 7.3. 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
343 very bottom. It also lets you configure how
344 the graph is drawn:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
345 Whether to use metric or imperial units
346 </li><li class="listitem">
347 Whether to show a marker at each data
348 point. When displaying a small section of
349 the graph, these can be useful to know what
350 data values were recorded.
351 </li><li class="listitem">
352 How wide to draw the lines in the graph
353 </li><li class="listitem">
354 How to filter speed and acceleration data
355 computed from barometric data. Flight
356 computers with accelerometers never display
357 computed acceleration data, and only use
358 barometric data to compute speed during
359 descent. Flight computers without
360 accelerometers always compute both speed and
361 acceleration from barometric data. A larger
362 value smooths the data more.
363 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_flight_statistics"></a>7.3.3. Flight Statistics</h3></div></div></div><div class="figure"><a id="idm472"></a><p class="title"><strong>Figure 7.4. 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><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_export_data"></a>7.4. Export Data</h2></div></div></div><p>This tool takes the raw data files and makes them
364 available for external analysis. When you select this
365 button, you are prompted to select a flight data file,
366 which can be either a .eeprom or .telem. The .eeprom
367 files contain higher resolution and more continuous
368 data, while .telem files contain receiver signal
369 strength information. Next, a second dialog appears
370 which is used to select where to write the resulting
371 file.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_comma_separated_value_format"></a>7.4.1. Comma Separated Value Format</h3></div></div></div><p>This is a text file containing the data in a form
372 suitable for import into a spreadsheet or other
373 external data analysis tool. The first few lines of
374 the file contain the version and configuration
375 information from the altimeter, then there is a single
376 header line which labels all of the fields. All of
377 these lines start with a <span class="emphasis"><em>#</em></span> character which many
378 tools can be configured to skip over.</p><p>The remaining lines of the file contain the data, with
379 each field separated by a comma and at least one
380 space. All of the sensor values are converted to
381 standard units, with the barometric data reported in
382 both pressure, altitude and height above pad units.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_configure_altimeter"></a>7.5. Configure Altimeter</h2></div></div></div><div class="figure"><a id="idm490"></a><p class="title"><strong>Figure 7.5. 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 an altimeter.</p><p>The first few lines of the dialog provide information about the
383 connected device, including the product name,
384 software version and hardware serial number. Below that are the
385 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">
388 This writes any changes to the configuration parameter
389 block in flash memory. If you don’t press this button,
390 any changes you make will be lost.
391 </dd><dt><span class="term">
394 This resets the dialog to the most recently saved
395 values, erasing any changes you have made.
396 </dd><dt><span class="term">
399 This reboots the device. Use this to switch from idle
400 to pad mode by rebooting once the rocket is oriented
401 for flight, or to confirm changes you think you saved
403 </dd><dt><span class="term">
406 This closes the dialog. Any unsaved changes will be
408 </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>7.5.1. Main Deploy Altitude</h3></div></div></div><p>This sets the altitude (above the recorded pad
409 altitude) at which the <span class="emphasis"><em>main</em></span> igniter will fire. The
410 drop-down menu shows some common values, but you can
411 edit the text directly and choose whatever you
412 like. If the apogee charge fires below this altitude,
413 then the main charge will fire two seconds after the
414 apogee charge fires.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_apogee_delay"></a>7.5.2. Apogee Delay</h3></div></div></div><p>When flying redundant electronics, it’s often
415 important to ensure that multiple apogee charges don’t
416 fire at precisely the same time, as that can over
417 pressurize the apogee deployment bay and cause a
418 structural failure of the air-frame. The Apogee Delay
419 parameter tells the flight computer to fire the apogee
420 charge a certain number of seconds after apogee has
421 been detected.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_apogee_lockout"></a>7.5.3. Apogee Lockout</h3></div></div></div><p>Apogee lockout is the number of seconds after launch
422 where the flight computer will not fire the apogee
423 charge, even if the rocket appears to be at
424 apogee. This is often called <span class="emphasis"><em>Mach Delay</em></span>, as it is
425 intended to prevent a flight computer from
426 unintentionally firing apogee charges due to the
427 pressure spike that occurrs across a mach
428 transition. Altus Metrum flight computers include a
429 Kalman filter which is not fooled by this sharp
430 pressure increase, and so this setting should be left
431 at the default value of zero to disable it.</p><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>Firmware versions older than 1.8.6 have a
432 bug which resets the time since launch to zero each
433 time a motor starts burning. Update firmware to get
434 the correct behavior.</p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_maximum_flight_log_size"></a>7.5.4. Maximum Flight Log Size</h3></div></div></div><p>This sets the space (in kilobytes) allocated
435 for each flight log. The available space will
436 be divided into chunks of this size. A smaller
437 value will allow more flights to be stored, a
438 larger value will record data from longer
439 flights.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_ignitor_firing_mode"></a>7.5.5. Ignitor Firing Mode</h3></div></div></div><p>This configuration parameter allows the two standard ignitor
440 channels (Apogee and Main) to be used in different
441 configurations.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
444 This is the usual mode of operation; the
445 <span class="emphasis"><em>apogee</em></span> channel is fired at apogee and the
446 <span class="emphasis"><em>main</em></span> channel at the height above ground
447 specified by the <span class="emphasis"><em>Main Deploy Altitude</em></span> during
449 </dd><dt><span class="term">
452 This fires both channels at apogee, the
453 <span class="emphasis"><em>apogee</em></span> channel first followed after a two
454 second delay by the <span class="emphasis"><em>main</em></span> channel.
455 </dd><dt><span class="term">
458 This fires both channels at the height above
459 ground specified by the Main Deploy Altitude
460 setting during descent. The <span class="emphasis"><em>apogee</em></span> channel
461 is fired first, followed after a two second
462 delay by the <span class="emphasis"><em>main</em></span> channel.
463 </dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_beeper_frequency"></a>7.5.6. Beeper Frequency</h3></div></div></div><p>The beeper on all Altus Metrum flight
464 computers works best at 4000Hz, however if you
465 have more than one flight computer in a single
466 airframe, having all of them sound at the same
467 frequency can be confusing. This parameter
468 lets you adjust the base beeper frequency
469 value.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_configure_altosui"></a>7.6. Configure AltosUI</h2></div></div></div><div class="figure"><a id="idm562"></a><p class="title"><strong>Figure 7.6. 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
470 configure the AltosUI global settings.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_log_directory"></a>7.6.1. Log Directory</h3></div></div></div><p>AltosUI logs all telemetry data and saves all
471 flash data to this directory. This
472 directory is also used as the staring point
473 when selecting data files for display or
474 export.</p><p>Click on the directory name to bring up a
475 directory choosing dialog, select a new
476 directory and click <span class="emphasis"><em>Select Directory</em></span> to
477 change where AltosUI reads and writes data
478 files.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_imperial_units"></a>7.6.2. Imperial Units</h3></div></div></div><p>This switches between metric units (meters)
479 and imperial units (feet and miles). This
480 affects the display of values use during
481 flight monitoring, configuration, data
482 graphing and all of the voice
483 announcements. It does not change the units
484 used when exporting to CSV files, those are
485 always produced in metric units.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_serial_debug"></a>7.6.3. Serial Debug</h3></div></div></div><p>This causes all communication with a connected
486 device to be dumped to the console from which
487 AltosUI was started. If you’ve started it from
488 an icon or menu entry, the output will simply
489 be discarded. This mode can be useful to debug
490 various serial communication issues.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_font_size"></a>7.6.4. Font size</h3></div></div></div><p>Selects the set of fonts used in the flight
491 monitor window. Choose between the small,
492 medium and large sets.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_look_amp_feel"></a>7.6.5. Look & feel</h3></div></div></div><p>Switches between the available Java user
493 interface appearances. The default selection
494 is supposed to match the native window system
495 appearance for the target platform.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_menu_position"></a>7.6.6. Menu position</h3></div></div></div><p>Selects the initial position for the main
496 AltosUI window that includes all of the
497 command buttons.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_flash_image"></a>7.7. Flash Image</h2></div></div></div><p>This reprograms Altus Metrum devices with new
501 over USB (self programming). Please read
502 the directions for flashing devices in
503 <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>7.8. Fire Igniter</h2></div></div></div><div class="figure"><a id="idm596"></a><p class="title"><strong>Figure 7.7. 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
504 computer to help test recovery systems
505 deployment.</p><p>Selecting the <span class="emphasis"><em>Fire Igniter</em></span> button brings up the
506 usual device selection dialog. Pick the desired
507 device. This brings up another window which shows the
508 current continuity test status for all of the pyro
509 channels.</p><p>Next, select the desired igniter to fire. This will
510 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>
511 button. The word <span class="emphasis"><em>Arm</em></span> is replaced by a countdown
512 timer indicating that you have 10 seconds to press the
513 <span class="emphasis"><em>Fire</em></span> button or the system will deactivate, at which
514 point you start over again at selecting the desired
515 igniter.</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
516 fundamental modes, “idle” and “flight”. Which of these modes
517 the firmware operates in is determined at start up
522 accelerometer we can use to determine orientation, “idle” mode
523 is selected if the board is connected via USB to a computer,
524 otherwise the board enters “flight” mode.</p><p>At power on, the altimeter will beep out the battery voltage
525 to the nearest tenth of a volt. Each digit is represented by
526 a sequence of short “dit” beeps, with a pause between
527 digits. A zero digit is represented with one long “dah”
528 beep. Then there will be a short pause while the altimeter
529 completes initialization and self test, and decides which mode
530 to enter next.</p><p>In flight or “pad” mode, the altimeter engages the flight
531 state machine, goes into transmit-only mode to send telemetry,
532 and waits for launch to be detected. Flight mode is indicated
533 by an “di-dah-dah-dit” (“P” for pad) on the beeper or lights,
534 followed by beeps or flashes indicating the state of the
535 pyrotechnic igniter continuity. One beep/flash indicates
536 apogee continuity, two beeps/flashes indicate main continuity,
537 three beeps/flashes indicate both apogee and main continuity,
538 and one longer “brap” sound which is made by rapidly
539 alternating between two tones indicates no continuity. For a
540 dual deploy flight, make sure you’re getting three beeps or
541 flashes before launching! For apogee-only or motor eject
542 flights, do what makes sense.</p><p>If idle mode is entered, you will hear an audible “di-dit” or
543 see two short flashes (“I” for idle), and the flight state
544 machine is disengaged, thus no ejection charges will fire.
545 Idle mode is useful for configuring the altimeter, for
546 extracting data from the on-board storage chip after
547 flight, and for ground testing pyro charges.</p><p>In “Idle” and “Pad” modes, once the mode indication
548 beeps/flashes and continuity indication has been sent, if
549 there is no space available to log the flight in on-board
550 memory, the flight computer will emit a warbling tone (much
551 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
552 the audio signals used.</p><p>Once landed, the flight computer will signal that by emitting
553 the “Landed” sound described above, after which it will beep
554 out the apogee height (in meters). Each digit is represented
555 by a sequence of short “dit” beeps, with a pause between
556 digits. A zero digit is represented with one long “dah”
557 beep. The flight computer will continue to report landed mode
558 and beep out the maximum height until turned off.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_ground_testing"></a>A.2. Ground Testing</h2></div></div></div><p>An important aspect of preparing a rocket using electronic deployment
559 for flight is ground testing the recovery system.</p><p>Just prep the rocket for flight, then power up the altimeter
562 You can now command the altimeter to fire the apogee
563 or main charges from a safe distance using your
564 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="_configurable_parameters"></a>A.3. Configurable Parameters</h2></div></div></div><p>Configuring an Altus Metrum altimeter for flight is
565 very simple. Even on our baro-only TeleMini and
566 EasyMini boards, the use of a Kalman filter means
567 there is no need to set a “mach delay”. All of the
568 configurable parameters can be set using AltosUI. Read
569 <a class="xref" href="#_configure_altimeter" title="7.5. Configure Altimeter">Section 7.5, “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.
570 When handled gently and properly installed in an air-frame, they
571 will deliver impressive results. However, as with all electronic
572 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
573 extraordinary power density. This is great because we can fly with
574 much less battery mass than if we used alkaline batteries or previous
575 generation rechargeable batteries… but if they are punctured
576 or their leads are allowed to short, they can and will release their
578 Thus we recommend that you take some care when handling our batteries
579 and consider giving them some extra protection in your air-frame. We
580 often wrap them in suitable scraps of closed-cell packing foam before
581 strapping them down, for example.</p></div><p>The barometric sensors used on all of our flight computers are
582 sensitive to sunlight. In normal mounting situations, the baro sensor
583 and all of the other surface mount components
584 are “down” towards whatever the underlying mounting surface is, so
585 this is not normally a problem. Please consider this when designing an
586 installation in an air-frame with a see-through plastic payload bay. It
587 is particularly important to
588 consider this with TeleMini v1.0, both because the baro sensor is on the
589 “top” of the board, and because many model rockets with payload bays
590 use clear plastic for the payload bay! Replacing these with an opaque
591 cardboard tube, painting them, or wrapping them with a layer of masking
592 tape are all reasonable approaches to keep the sensor out of direct
593 sunlight.</p><p>The barometric sensor sampling port must be able to “breathe”,
594 both by not being covered by foam or tape or other materials that might
595 directly block the hole on the top of the sensor, and also by having a
596 suitable static vent to outside air.</p><p>As with all other rocketry electronics, Altus Metrum altimeters must
597 be protected from exposure to corrosive motor exhaust and ejection
598 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>EasyMini is
599 programmed directly over their USB connectors (self
600 programming).</p><p>You may wish to begin by ensuring you have current firmware
601 images. These are distributed as part of the AltOS software
602 bundle that also includes the AltosUI ground station program.
603 Newer ground station versions typically work fine with older
604 firmware versions, so you don’t need to update your devices
605 just to try out new software features. You can always
606 download the most recent version from
607 <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_easymini_firmware"></a>C.1. Updating EasyMini Firmware</h2></div></div></div><p>Self-programmable devices are reprogrammed by
608 connecting them to your computer over USB.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
609 Attach a battery if necessary and power switch to
610 the target device. Power up the device.
611 </li><li class="listitem">
612 Using a Micro USB cable, connect the target device to your
613 computer’s USB socket.
614 </li><li class="listitem">
615 Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from the File menu.
616 </li><li class="listitem">
617 Select the target device in the Device Selection dialog.
618 </li><li class="listitem">
619 Select the image you want to flash to the device,
620 which should have a name in the form
621 <product>-v<product-version>-<software-version>.ihx,
622 such as EasyMini-v1.0-1.6.0.ihx.
623 </li><li class="listitem">
624 Make sure the configuration parameters are
625 reasonable looking. If the serial number and/or RF
626 configuration values aren’t right, you’ll need to
628 </li><li class="listitem">
629 Hit the <span class="emphasis"><em>OK</em></span> button and the software should proceed
630 to flash the device with new firmware, showing a
632 </li><li class="listitem">
633 Verify that the device is working by using the
634 <span class="emphasis"><em>Configure Altimeter</em></span> or <span class="emphasis"><em>Configure Groundstation</em></span>
635 item to check over the configuration.
636 </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
637 unable to boot. Not to worry, you can force the device to
638 start the boot loader instead, which will let you try to
639 flash the device again.</p><p>On each device, connecting two pins from one of the exposed
640 connectors will force the boot loader to start, even if the
641 regular operating system has been corrupted in some way.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
644 Connect pin 6 and pin 1 of the debug connector, which
645 is the six holes next to the beeper. Pin 1 can be
646 identified by the square pad around it, and then the
647 pins could sequentially across the board, making Pin 6
648 the one on the other end of the row.
649 </dd></dl></div><p>Once you’ve located the right pins:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
650 Turn the altimeter power off.
651 </li><li class="listitem">
653 </li><li class="listitem">
654 Connect the indicated terminals together with a
655 short piece of wire. Take care not to accidentally
656 connect anything else.
657 </li><li class="listitem">
659 </li><li class="listitem">
660 Turn the board power on.
661 </li></ol></div><p>The board should now be visible over USB as
662 <span class="emphasis"><em>AltosFlash</em></span> and be ready to receive firmware. Once
663 the board has been powered up, you can remove the
664 piece of wire.</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
665 during ascent and 10 samples per second during
668 an on-board flash memory part, which can be partitioned into
669 several equal-sized blocks, one for each flight.</p><div class="table"><a id="idm696"></a><p class="title"><strong>Table D.1. Data Storage on Altus Metrum altimeters</strong></p><div class="table-contents"><table class="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; " align="left" valign="top"><p>EasyMini</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>16</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>1MB</p></td><td style="" align="left" valign="top"><p>10</p></td></tr></tbody></table></div></div><br class="table-break" /><p>The on-board flash is partitioned into separate flight logs,
670 each of a fixed maximum size. Increase the maximum size of
671 each log and you reduce the number of flights that can be
672 stored. Decrease the size and you can store more flights.</p><p>Configuration data is also stored in the flash memory on
675 of flash space. This configuration space is not available
676 for storing flight log data.</p><p>To compute the amount of space needed for a single flight, you
677 can multiply the expected ascent time (in seconds) by 100
678 times bytes-per-sample, multiply the expected descent time (in
679 seconds) by 10 times the bytes per sample and add the two
680 together. That will slightly under-estimate the storage (in
681 bytes) needed for the flight.</p><p>The default size allows for several flights on each flight
683 You can adjust the size.</p><p>Altus Metrum flight computers will not overwrite existing
684 flight data, so be sure to download flight data and erase it
685 from the flight computer before it fills up. The flight
686 computer will still successfully control the flight even if it
687 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
688 production and retired.</p><div class="table"><a id="idm727"></a><p class="title"><strong>Table E.1. Altus Metrum Flight Computer Electronics</strong></p><div class="table-contents"><table class="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>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; " align="left" valign="top"><p>EasyMini v2.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>-</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>-</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>1MB</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="" align="left" valign="top"><p>3.7-12V</p></td></tr></tbody></table></div></div><br class="table-break" /><p></p><div class="table"><a id="idm784"></a><p class="title"><strong>Table E.2. Altus Metrum Flight Computer Mechanical Components</strong></p><div class="table-contents"><table class="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; " align="left" valign="top"><p>EasyMini</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Debug USB Battery</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro Battery</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>0.8 inch (2.03cm)</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>1½ inch (3.81cm)</p></td><td style="" align="left" valign="top"><p>24mm 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_8_6"></a>F.1. Release Notes for Version 1.8.6</h2></div></div></div><p>Version 1.8.6</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos"></a>F.1.1. AltOS</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
689 Use maximum of 64 previous tilt values in pyro tilt tests
690 </li><li class="listitem">
691 Eliminate 100m height requirement for coast detection
692 </li><li class="listitem">
693 Change After Motor pyro check to be >= instead of ==
694 </li><li class="listitem">
695 Change Time since Boost to be Time since launch.
696 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_telegps"></a>F.1.2. AltosUI, TeleGPS</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
697 Clarify pyro test phrasing
698 </li><li class="listitem">
699 Remove ascending/descending from pyro config UI
700 </li><li class="listitem">
701 Fix accel calibration in Antenna Down mode
702 </li><li class="listitem">
703 Add mag sensor reporting for TeleMega v3 idle monitoring.
704 </li><li class="listitem">
705 Fix radio parameter saving at 2400 bps telmetry rate.
706 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_micropeak"></a>F.1.3. MicroPeak</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
707 Report altimeter-recorded maximum height value
708 </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_8_5"></a>F.2. Release Notes for Version 1.8.5</h2></div></div></div><p>Version 1.8.5 includes fixes to the ground software support
709 for TeleBT v4, along with a few other minor updates.</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><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
710 Fix startup beeps that indicate sensor failures.
711 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_telegps_2"></a>F.2.2. AltosUI, TeleGPS</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
712 When updating device firmware, make sure selected firmware
713 matches target device.
714 </li><li class="listitem">
715 Correct Bluetooth device matching when looking for TeleBT
717 </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_8_4"></a>F.3. Release Notes for Version 1.8.4</h2></div></div></div><p>Version 1.8.4 includes support for EasyMini version 2.0</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><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
718 Support for EasyMini version 2.0 hardware.
719 </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_8_3"></a>F.4. Release Notes for Version 1.8.3</h2></div></div></div><p>Version 1.8.3 includes support for TeleMega version 3.0 along
720 with two important flight computer fixes. This version also
721 changes KML export data to make Tripoli Record reporting
722 better and some updates to graph presentation and data
723 downloading.</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><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_altos_new_features"></a>AltOS New Features</h4></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
724 Support for TeleMega version 3.0 hardware.
725 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_altos_bug_fixes"></a>AltOS Bug Fixes</h4></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
726 Ground testing EasyMega and TeleMega additional pyro
727 channels could result in a sticky <span class="emphasis"><em>fired</em></span> status which would
728 prevent these channels from firing on future flights.
729 </li><li class="listitem">
730 Corrupted flight log records could prevent future flights
731 from capturing log data.
732 </li><li class="listitem">
733 Fixed saving of pyro configuration that ended with
734 <span class="emphasis"><em>Descending</em></span>.
735 </li></ul></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications"></a>F.4.2. AltosUI and TeleGPS Applications</h3></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_altosui_new_features"></a>AltosUI New Features</h4></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
736 Support for TeleMega version 3.0.
737 </li><li class="listitem">
738 Graph lines have improved appearance to make them easier to
739 distinguish. Markers may be placed at data points to show
740 captured recorded data values.
741 </li><li class="listitem">
742 Graphing offers the ability to adjust the smoothing of
743 computed speed and acceleration data.
744 </li><li class="listitem">
745 The download dialog now offers to graph new flights, checks
746 for existing files to avoid overwriting data and reports if
747 there are checksum errors in the downloaded data.
748 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_altosui_telegps_bug_fixes"></a>AltosUI/TeleGPS Bug Fixes</h4></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
749 Restore TeleGPS tracking behavior.
750 </li><li class="listitem">
751 Display flight computer call sign and serial number in
752 Monitor Idle mode instead of ground station values.
753 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_altosui_and_telegps_changes"></a>AltosUI and TeleGPS Changes</h4></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
754 KML export now reports both barometric and GPS altitude data
755 to make it more useful for Tripoli record reporting.
756 </li><li class="listitem">
757 CSV export now includes TeleMega/EasyMega pyro voltages and
759 </li></ul></div><p></p></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_8_2"></a>F.5. Release Notes for Version 1.8.2</h2></div></div></div><p>Version 1.8.2 includes support for TeleGPS version 2.0 along
760 with accelerometer recalibration support in AltosUI.</p><p>1.8.2 also contains a couple of minor fixes for AltosUI when
761 analyzing saved data files.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_5"></a>F.5.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">
762 Support for TeleGPS version 2.0 hardware.
763 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_2"></a>F.5.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">
764 Support for TeleGPS version 2.0.
765 </li><li class="listitem">
766 Accelerometer re-calibration user interface.
767 </li></ul></div><p>AltosUI and TeleGPS Bug Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
768 Prevent some crashes when reading older saved flight data
769 for graphing or KML export.
770 </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_8_1"></a>F.6. Release Notes for Version 1.8.1</h2></div></div></div><p>Version 1.8.1 includes an important bug fix for Apogee Lockout
771 operation in all flight computers. Anyone using this option
772 must update firmware.</p><p>This release also contains a change in how flight computers
773 with accelerometers deal with speeds around and above Mach
774 1. In previous versions, the flight computer would completely
775 disregard the barometric sensor above 330m/s (around Mach
776 1). Now, the data from the barometric sensor is reduced in
777 effect without ever going away entirely. This prevents early
778 drogue deployment for flights which spend considerable time
779 above Mach 1.</p><p>1.8.1 also contains a couple of minor fixes for AltosUI when
780 analyzing saved data files.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_6"></a>F.6.1. AltOS</h3></div></div></div><p>AltOS Bug Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
781 Handle time value wrapping in Apogee Lockout
782 correctly. Without this, apogee lockout would sometimes
783 prevent any drogue charge from firing.
784 </li><li class="listitem">
785 Change Kalman filter on flight computers with accelerometer
786 to continue using the barometric sensor even at high speeds
787 to avoid unintentional drogue deployment during
789 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_3"></a>F.6.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
790 Add new <span class="emphasis"><em>Huge</em></span> font size to make text even bigger on high
792 </li></ul></div><p>AltosUI Bug Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
793 Prevent some crashes when reading older saved flight data
794 for graphing or KML export.
795 </li><li class="listitem">
796 Load frequency preference at startup. The loading code was
797 broken, so you’d see only the default frequencies.
798 </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_8"></a>F.7. Release Notes for Version 1.8</h2></div></div></div><p>Version 1.8 includes support for our new TeleBT v4.0 ground
799 station, updates for data analysis in our ground station
800 software and bug fixes in in the flight software for all our
801 boards and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_7"></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">
802 Add support for TeleBT v4.0 boards.
803 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_4"></a>F.7.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
804 Add support for TeleBT v4.0 hardware
805 </li><li class="listitem">
806 Rewrite graphing and export functions. This code now handles
807 each data series separately so that graphs are drawn
808 correctly. Smoothing now uses a filter that looks both
809 forward and backwards in time to make computed speed and
810 acceleration data more accurate.
811 </li></ul></div><p>AltosUI Bug Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
812 Correct axis labeling of magnetic sensor in TeleMega and
813 EasyMega. The Y and Z axes were flipped.
814 </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_7"></a>F.8. Release Notes for Version 1.7</h2></div></div></div><p>Version 1.7 includes support for our new TeleMini v3.0
815 flight computer and bug fixes in in the flight software for all our boards
816 and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_8"></a>F.8.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">
817 Add support for TeleMini v3.0 boards.
818 </li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
819 Fix interrupt priorities on STM32L processors. Run timer
820 interrupt at lowest priority so that device interrupts get
822 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_5"></a>F.8.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
823 Add support for TeleMini v3.0 hardware
824 </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_8"></a>F.9. Release Notes for Version 1.6.8</h2></div></div></div><p>Version 1.6.8 fixes a TeleMega and TeleMetrum v2.0 bug where
825 the device could stop logging data and transmitting
826 telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum
827 v2.0 users should update their flight firmware.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_9"></a>F.9.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
828 Fix STM32L DMA driver to work around STM32L SoC DMA priority
829 issue t lock-up in the logging or radio code, either of
830 which could stop data logging and telemetry.
831 </li><li class="listitem">
832 Avoid having TeleBT battery status values smash telemetry
833 packet data by holding a lock during both operations.
834 </li><li class="listitem">
835 Don’t start reporting <span class="emphasis"><em>flight 0</em></span> when the log fills in
837 </li></ul></div><p>AltOS changes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
838 Flash LEDS on all products briefly during power up so that
839 they can be tested during production.
840 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_telegps_and_altosdroid_applications"></a>F.9.2. AltosUI, TeleGPS and AltosDroid Applications</h3></div></div></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
841 Re-enable go/no-go entries after they’ve been disabled due
842 to lack of data. If telemetry information is delayed when
843 the Ui starts up, sometimes important fields would get
844 disabled to never re-appear.
845 </li><li class="listitem">
846 Deal with ground station failure better during Configure
847 Ground Station operation by cleaning up pending operations.
848 </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_5"></a>F.10. Release Notes for Version 1.6.5</h2></div></div></div><p>Version 1.6.5 fixes a TeleMega and TeleMetrum v2.0 bug where
849 the device would often stop logging data and transmitting
850 telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum
851 v2.0 users should update their flight firmware.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_10"></a>F.10.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
852 Fix STM32L SPI driver to prevent lock-up in the logging or
853 radio code, either of which could stop data logging and
854 telemetry. Found and characterized by Chuck Haskin, who also
855 tested the new firmware before release.
856 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_telegps_and_altosdroid_applications_2"></a>F.10.2. AltosUI, TeleGPS and AltosDroid Applications</h3></div></div></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
857 Deliver firmward for TeleMega v2.0 and TeleBT v3.0 with
859 </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_4"></a>F.11. Release Notes for Version 1.6.4</h2></div></div></div><p>Version 1.6.4 fixes a bluetooth communication problem with
860 TeleBT v1.0 devices, along with some altosui and altosdroid
861 minor nits. It also now ships firmware for some newer devices.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_11"></a>F.11.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
862 Fix hardware flow control on TeleBT v1.0. Hardware RTS/CTS
863 doesn’t seem to work, switch from using the hardware to
864 driving these pins with software.
865 </li><li class="listitem">
866 Fix ARM USB drivers to deal with OS restarts. Needed to
867 reset all USB-related state when the USB bus is reset. These
868 fixes affect all STM32L, STM32F0 and LPC11U14 based devices.
869 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_telegps_and_altosdroid_applications_3"></a>F.11.2. AltosUI, TeleGPS and AltosDroid Applications</h3></div></div></div><p>AltosUI, TeleGPS and AltosDroid New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
870 Automatically switch from meters or feet to kilometers or
871 miles for distance units.
872 </li><li class="listitem">
873 Add Monitor Idle mode to TeleGPS application.
874 </li></ul></div><p>AltosUI, TeleGPS and AltosDroid Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
875 Abort map preloading when the preload map dialog is closed.
876 </li><li class="listitem">
877 In AltosDroid, Don’t reconnect to last device if the user
878 had disconnected it the last time the application was
880 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation"></a>F.11.3. Documentation</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
881 Mention TeleMega v2.0 in hardware specs table.
882 </li><li class="listitem">
883 Document TeleGPS RF output in telegps manual.
884 </li></ul></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_3"></a>F.12. Release Notes for Version 1.6.3</h2></div></div></div><p>Version 1.6.3 adds idle mode to AltosDroid and has bug fixes
885 for our host software on desktops, laptops an android devices
886 along with BlueTooth support for Windows.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_12"></a>F.12.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
887 Fix hardware flow control on TeleBT v3.0. RTS/CTS is
888 wired backwards on this board, switch from using the
889 hardware to driving these pins with software.
890 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_6"></a>F.12.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">
891 Add BlueTooth support for Windows operating system. This
892 supports connections to TeleBT over BlueTooth rather than
894 </li></ul></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
895 Change Java detection and install on Windows. Detection is
896 now done by looking for the <span class="emphasis"><em>javaw.exe</em></span> program, and
897 installation by opening a browser on the java.com web site.
898 </li><li class="listitem">
899 Delay polling while the Fire Igniters is visible to allow
900 for TeleMega to report back complete status over the radio.
901 </li><li class="listitem">
902 Disallow changing RF calibration numbers in the
903 configuration UI. There’s no good reason to change this from
904 the field, and recovering is really hard if you haven’t
905 written down the right number.
906 </li><li class="listitem">
907 Fix USB device discovery on Mac OS X El Capitan. This makes
908 the connected Altus Metrum USB devices appear again.
909 </li><li class="listitem">
910 Fix acceleration data presented in MonitorIdle mode for
911 TeleMetrum v2.0 flight computers.
912 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosdroid"></a>F.12.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">
913 Monitor Idle mode. Check state of flight computer while in
914 idle mode over the radio link
915 </li><li class="listitem">
916 Fire Igniters. Remotely fire ignires for recovery system
918 </li><li class="listitem">
919 Remote reboot. Cause the flight computer to reboot over the
920 radio link. This provides a method for switching the flight
921 computer from idle to flight mode without needing to reach
923 </li><li class="listitem">
924 Configurable frequency menu. Change the set of available
925 frequencies and provide more descriptive names.
926 </li></ul></div><p>AltosDroid bug fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
927 Don’t set target location if GPS hasn’t locked yet.
928 </li><li class="listitem">
929 Fix saving target states so they can be reloaded when the
930 application restarts. When the application is shut down and
931 restarted, all previous target state information will be
932 restored (including GPS position if available).
933 </li><li class="listitem">
934 Fix crash on some Android devices for offline maps when
935 changing the map scale or location.
936 </li><li class="listitem">
937 Don’t require USB OTG support. This kept the latest
938 AltosDroid from being offered on devices without USB device
939 support, although it can work without that just fine using
941 </li><li class="listitem">
942 Don’t require bluetooth to be enabled. This allows the
943 application to operate with USB devices or just show old
944 data without turning on the bluetooth radio.
945 </li><li class="listitem">
946 Recover old tracker positions when restarting
947 application. This finally allows you to safely stop and
948 restart the application without losing the last known
949 location of any tracker.
950 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation_2"></a>F.12.4. Documentation</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
951 Document TeleMega and EasyMega additional pyro channel
952 continuity audio alert pattern.
953 </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_2"></a>F.13. Release Notes for Version 1.6.2</h2></div></div></div><p>Version 1.6.2 includes support for our updated TeleMega v2.0
954 product and bug fixes in in the flight software for all our boards
955 and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_13"></a>F.13.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">
956 Add support for TeleMega v2.0 boards.
957 </li><li class="listitem">
958 Add PWM servo driver. There’s no higher level code using
959 this yet, but the driver allows testing of the TeleMega v2.0
960 servo output connector.
961 </li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
962 Slow down telemetry packets to allow receiver to keep
964 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_7"></a>F.13.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">
965 Fix post-flight orientation computation when processing
966 TeleMega and EasyMega eeprom data files.
967 </li><li class="listitem">
968 Capture complete eeprom data even when there are invalid
969 entries in the data. This keeps reading eeprom contents and
970 writing the associated .eeprom file when an error is detected.
971 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation_3"></a>F.13.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">
972 HTML versions now have a table of contents on the left side.
973 </li><li class="listitem">
974 EasyMini now has its own shorter manual.
975 </li><li class="listitem">
976 Provide links between sections in each document.
977 </li><li class="listitem">
978 Lots of minor rewriting and restructuring to avoid
979 duplication of information
980 </li></ul></div></div></div></div></div></body></html>
projects / web / altusmetrum / blob