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></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_6_3">F.1. Release Notes for Version 1.6.3</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos">F.1.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications">F.1.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_altosdroid">F.1.3. AltosDroid</a></span></dt><dt><span class="section"><a href="#_documentation">F.1.4. Documentation</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_2">F.2. Release Notes for Version 1.6.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_2">F.2.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_2">F.2.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_documentation_2">F.2.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="#idm274">EasyMini Board</a></dt><dt>7.1. <a href="#idm405">AltosUI Main Window</a></dt><dt>7.2. <a href="#idm432">Flight Data Graph</a></dt><dt>7.3. <a href="#idm443">Flight Graph Configuration</a></dt><dt>7.4. <a href="#idm453">Flight Statistics</a></dt><dt>7.5. <a href="#idm471">Altimeter Configuration</a></dt><dt>7.6. <a href="#idm541">Configure AltosUI Dialog</a></dt><dt>7.7. <a href="#idm575">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="#idm90">AltOS Modes</a></dt><dt>3.2. <a href="#idm198">Pad/Idle Indications</a></dt><dt>4.1. <a href="#idm286">EasyMini Screw Terminals</a></dt><dt>D.1. <a href="#idm675">Data Storage on Altus Metrum altimeters</a></dt><dt>E.1. <a href="#idm706">Altus Metrum Flight Computer Electronics</a></dt><dt>E.2. <a href="#idm746">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>The first device created for our community was TeleMetrum, a dual
28 deploy altimeter with fully integrated GPS and radio telemetry
29 as standard features, and a “companion interface” that will
30 support optional capabilities in the future. The latest version
31 of TeleMetrum, v2.0, has all of the same features but with
32 improved sensors and radio to offer increased performance.</p><p>Our second device was TeleMini, a dual deploy altimeter with
33 radio telemetry and radio direction finding. The first version
34 of this device was only 13mm by 38mm (½ inch by 1½ inches) and
35 could fit easily in an 18mm air-frame. The latest version, v3.0,
36 includes a beeper, higher power radio, extended on-board
37 flight logging and an improved barometric sensor.</p><p>TeleMega is our most sophisticated device, including six pyro
38 channels (four of which are fully programmable), integrated GPS,
39 integrated gyroscopes for staging/air-start inhibit and high
40 performance telemetry.</p><p>EasyMini is a dual-deploy altimeter with logging and built-in
41 USB data download.</p><p>EasyMega is essentially a TeleMega board with the GPS receiver
42 and telemetry transmitter removed. It offers the same 6 pyro
43 channels and integrated gyroscopes for staging/air-start inhibit.</p><p>TeleDongle v0.2 was our first ground station, providing a USB to RF
44 interfaces for communicating with the altimeters. Combined with
45 your choice of antenna and notebook computer, TeleDongle and our
46 associated user interface software form a complete ground
47 station capable of logging and displaying in-flight telemetry,
48 aiding rocket recovery, then processing and archiving flight
49 data for analysis and review. The latest version, TeleDongle
50 v3, has all new electronics with a higher performance radio
51 for improved range.</p><p>For a slightly more portable ground station experience that also
52 provides direct rocket recovery support, TeleBT offers flight
53 monitoring and data logging using a Bluetooth™ connection between
54 the receiver and an Android device that has the AltosDroid
55 application installed from the Google Play store.</p><p>More products will be added to the Altus Metrum family over time, and
56 we currently envision that this will be a single, comprehensive manual
57 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
58 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
59 EasyMini battery can be charged by disconnecting it
60 from the board and plugging it into a standalone
61 battery charger such as <a class="ulink" href="http://altusmetrum.org/LipoCharger" target="_top">LipoCharger</a>, and
62 connecting that via a USB cable to a laptop or other
63 USB power source.</p><p>You can also choose to use another battery with
64 EasyMini, anything supplying between 4 and 12 volts should
65 work fine (like a standard 9V battery), but if you are planning
66 to fire pyro charges, ground testing is required to verify that
67 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.
68 The AltOS distribution includes the AltosUI ground
69 station program, current firmware images for all of
70 the hardware, and a number of standalone utilities
71 that are rarely needed. Pre-built binary packages are
72 available for Linux, Microsoft Windows, Mac OSX. Full
73 source code and build instructions are also
74 available. The latest version may always be downloaded
75 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
76 flight computer. Instructions specific to each model will be
77 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
78 operation of the flight computer, it’s important to always
79 twist pairs of wires connected to the board. Twist the switch
80 leads, the pyro leads and the battery leads. This reduces
81 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
82 series connector to connect up a single-cell Lithium Polymer
83 cell (3.7V nominal). You can purchase matching batteries
84 from the Altus Metrum store, or other vendors, or you can
85 make your own. Pin 1 of the connector is positive, pin 2 is
86 negative. Spark Fun sells a cable with the connector
87 attached, which they call a
88 <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
89 this same connector. All that we have found use the opposite
90 polarity, and if you use them that way, you will damage or
91 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
92 each pyro charge. This means you shouldn’t need to put two
93 wires into a screw terminal or connect leads from pyro
94 charges together externally.</p><p>On the flight computer, one lead from each charge is hooked
95 to the positive battery terminal through the power switch.
96 The other lead is connected through the pyro circuit, which
97 is connected to the negative battery terminal when the pyro
98 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
99 to turn them on. This disconnects both the computer and the
100 pyro charges from the battery, preventing the charges from
101 firing when in the Off position. The switch is in-line with
102 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
103 provide information about the state of the system.</p><p>Here’s a short summary of all of the modes and the
105 that accompanies each mode. In the description of the
106 beeping pattern, “dit” means a short beep while "dah"
107 means a long beep (three times as long). “Brap” means
108 a long dissonant tone.</p><div class="table"><a id="idm90"></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
109 indications. In Idle mode, you’ll hear one of these
110 just once after the two short dits indicating idle
111 mode. In Pad mode, after the dit dah dah dit
112 indicating Pad mode, you’ll hear these once every five
113 seconds.</p><div class="table"><a id="idm198"></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
114 not prevent the flight computer from safely
115 controlling the flight or transmitting telemetry
116 signals, but no record of the flight will be
117 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
118 to "on". The flight computer will signal power on by
119 reporting the battery voltage and then perform an internal self
120 test and sensor calibration.</p><p>Once the self test and calibration are complete, there
121 are two modes that an Altus Metrum flight computer can
122 operate in:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
125 The flight computer is waiting to detect
126 launch and then fly the rocket. In this mode, the USB
129 The only way to get out of this
130 mode is to power the flight computer down.
131 </dd><dt><span class="term">
134 The flight computer is ready to communicate over USB
136 the flight computer, download data or display
138 </dd></dl></div><p>For EasyMini, if the USB cable is connected to a
139 computer, it will enter Idle mode. Otherwise, it will
140 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>
141 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
142 Featherweight Magnetic Switch, with any Altus Metrum
143 flight computer. These require three connections, one to
144 the battery, one to the positive power input on the flight
145 computer and one to ground. Find instructions on how to
146 hook these up for each flight computer below. Then follow
147 the instructions that come with your active switch to
148 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
149 lead for each of the pyro charges is connected through
150 the power switch directly to the positive battery
151 terminal. The other lead is connected to the pyro
152 circuit, which connects it to the negative battery
153 terminal when the pyro circuit is fired. The pyro
154 circuit on all of the flight computers is designed to
155 handle up to 16V.</p><p>To use a separate pyro battery, connect the negative pyro
156 battery terminal to the flight computer ground terminal,
157 the positive battery terminal to the igniter and the other
158 igniter lead to the negative pyro terminal on the flight
159 computer. When the pyro channel fires, it will complete the
160 circuit between the negative pyro terminal and the ground
161 terminal, firing the igniter. Specific instructions on how
162 to hook this up for each flight computer will be found
163 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
165 designed to use either a
166 lithium polymer battery or any other battery producing
167 between 4 and 12 volts, such as a rectangular 9V
168 battery.</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="idm274"></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
169 designed to fit in a 24mm coupler tube.</p><p>You usually don’t need to configure EasyMini at all; it’s set
170 up to do dual-deployment with an event at apogee to separate
171 the airframe and deploy a drogue and another event at 250m
172 (820ft) to deploy the main. Install EasyMini in your airframe,
173 hook up a battery, igniters and a power switch and you’re
174 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
175 board. Using the picture
176 above, the top four have connections for the main pyro
177 circuit and an external battery and the bottom four have
178 connections for the apogee pyro circuit and the power
179 switch. Counting from the left, the connections are as follows:</p><div class="table"><a id="idm286"></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
180 EasyMini. You can use either method; both feed
181 through the power switch terminals.</p><p>One battery connection is the standard Altus Metrum
182 white JST plug. This mates with single-cell Lithium
183 Polymer batteries sold by Altus Metrum.</p><p>The other is a pair of screw terminals marked <span class="emphasis"><em>Battery
184 +</em></span> and <span class="emphasis"><em>Battery -</em></span>. Connect a battery from 4 to 12
185 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
186 standard Altus Metrum Lithium Polymer cells, it cannot
187 incorporate a battery charger circuit. Therefore, when
188 using a Litium Polymer cell, you’ll need an external
189 charger. These are available from Altus Metrum, or
190 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
191 connecting the negative battery terminal to the flight
192 computer ground, connecting the positive battery terminal to
193 one of the igniter leads and connecting the other igniter
194 lead to the per-channel pyro circuit connection.</p><p>To connect the negative pyro battery terminal to EasyMini
195 ground, connect it to the negative external battery
196 connection, top terminal 4.</p><p>Connecting the positive battery terminal to the pyro
197 charges must be done separate from EasyMini, by soldering
198 them together or using some other connector.</p><p>The other lead from each pyro charge is then inserted into
199 the appropriate per-pyro channel screw terminal (top
200 terminal 1 for the Main charge, bottom terminal 1 for the
201 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
202 connections, one to the positive battery terminal, one to
203 the flight computer positive input and one to ground. Use
204 the negative external battery connection, top terminal 4 for
205 ground.</p><p>The positive battery terminal is available on bottom
206 terminal 4, the positive flight computer input is on the
207 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
208 only a suitable battery, a single pole switch for
209 power on/off, and two pairs of wires connecting e-matches for the
210 apogee and main ejection charges. All Altus Metrum products are
211 designed for use with single-cell batteries with 3.7 volts
213 EasyMini may also be used with other
214 batteries as long as they supply between 4 and 12 volts.</p><p>The battery connectors are a standard 2-pin JST connector; you
215 can purchase suitable batteries from the any vendor selling
216 Altus Metrum products. These batteries are
217 single-cell Lithium Polymer batteries that nominally provide 3.7
218 volts. Other vendors sell similar batteries for RC aircraft
219 using mating connectors, however the polarity for those is
220 generally reversed from the batteries used by Altus Metrum
221 products. In particular, the Tenergy batteries supplied for use
222 in Featherweight flight computers are not compatible with Altus
223 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
224 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
225 the correct polarity. However, these batteries include an
226 integrated current limiting circuit. That circuit will cause
227 the battery to shut down when firing the igniter circuit. Do
228 not use these batteries unless you remove the current limiting
229 circuit.</p></div><p>By default, we use the unregulated output of the battery
230 directly to fire ejection charges. This works marvelously
231 with standard low-current e-matches like the J-Tek from MJG
232 Technologies, and with Quest Q2G2 igniters. However, if you
233 want or need to use a separate pyro battery, check out
234 <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
235 that up. The altimeters are designed to work with an external
236 pyro battery of no more than 15 volts.</p><p>Ejection charges are wired directly to the screw terminal block
237 at the aft end of the altimeter. You’ll need a very small straight
238 blade screwdriver for these screws, such as you might find in a
239 jeweler’s screwdriver set.
240 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
241 and a single-cell, 3.7 volt nominal Li-Po rechargeable
243 A 110mAh battery weighs less
244 than a triple A battery and is a good choice for use
246 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
247 across Linux, Mac OS and Windows. There’s also a suite
248 of C tools for Linux which can perform most of the
249 same tasks.</p><p>After the flight,
251 USB cable to plug into the flight computer board directly.
252 A USB cable is also how you
253 charge the Li-Po battery, so you’ll want one of those
254 anyway. The same cable used by lots of digital
255 cameras and other modern electronic stuff will work
256 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
257 flight, both the telemetry received during the flight
258 itself, and the more complete data log recorded in the
259 flash memory on the altimeter board. Once this data
260 is on your computer, our post-flight tools make it
261 easy to quickly get to the numbers everyone wants,
262 like apogee altitude, max acceleration, and max
263 velocity. You can also generate and view a standard
264 set of plots showing the altitude, acceleration, and
265 velocity of the rocket during flight. And you can
266 even export a flight log in a format usable with Google
267 Maps and Google Earth for visualizing the flight path
268 in two or three dimensions!</p><p>Our ultimate goal is to emit a set of files for each
269 flight that can be published as a web page per flight,
270 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
271 designs and the software, if you have some great idea
272 for an addition to the current Altus Metrum family,
273 feel free to dive in and help! Or let us know what
274 you’d like to see that we aren’t already working on,
275 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
276 more news and information as our family of products
277 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="idm405"></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
278 interacting with the Altus Metrum product family. AltosUI can
279 monitor telemetry data, configure devices and many other
280 tasks. The primary interface window provides a selection of
281 buttons, one for each major activity in the system. This
282 chapter is split into sections, each of which documents one of
283 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
285 The <span class="emphasis"><em>Save Flight Data</em></span> button allows you to
286 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
287 list of connected flight computers and TeleDongle
288 devices. If you select a flight computer, the flight
289 data will be downloaded from that device directly.</p><p>After the device has been selected, a dialog showing
290 the flight data saved in the device will be shown
291 allowing you to select which flights to download and
292 which to delete. With version 0.9 or newer firmware,
293 you must erase flights in order for the space they
294 consume to be reused by another flight. This prevents
295 accidentally losing flight data if you neglect to
296 download data before flying again. Note that if there
297 is no more space available in the device, then no data
298 will be recorded during the next flight.</p><p>The file name for each flight log is computed
299 automatically from the recorded flight date, altimeter
300 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
301 record file, either a .telem file recording telemetry data or a
302 .eeprom file containing flight data saved from the altimeter
303 flash memory.</p><p>Once a flight record is selected, the flight monitor interface
304 is displayed and the flight is re-enacted in real
305 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
306 record file, either a .telem file recording telemetry data or a
307 .eeprom file containing flight data saved from
308 flash memory.</p><p>Note that telemetry files will generally produce poor graphs
309 due to the lower sampling rate and missed telemetry packets.
310 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
311 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="idm432"></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),
312 velocity (green) and altitude (red).</p><p>The graph can be zoomed into a particular area by
313 clicking and dragging down and to the right. Once
314 zoomed, the graph can be reset by clicking and
315 dragging up and to the left. Holding down control and
316 clicking and dragging allows the graph to be panned.
317 The right mouse button causes a pop-up menu to be
318 displayed, giving you the option save or print the
319 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="idm443"></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
320 very bottom, lets you switch between metric and
321 imperial units</p></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="idm453"></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
322 available for external analysis. When you select this
323 button, you are prompted to select a flight data file,
324 which can be either a .eeprom or .telem. The .eeprom
325 files contain higher resolution and more continuous
326 data, while .telem files contain receiver signal
327 strength information. Next, a second dialog appears
328 which is used to select where to write the resulting
329 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
330 suitable for import into a spreadsheet or other
331 external data analysis tool. The first few lines of
332 the file contain the version and configuration
333 information from the altimeter, then there is a single
334 header line which labels all of the fields. All of
335 these lines start with a <span class="emphasis"><em>#</em></span> character which many
336 tools can be configured to skip over.</p><p>The remaining lines of the file contain the data, with
337 each field separated by a comma and at least one
338 space. All of the sensor values are converted to
339 standard units, with the barometric data reported in
340 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="idm471"></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
341 connected device, including the product name,
342 software version and hardware serial number. Below that are the
343 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">
346 This writes any changes to the configuration parameter
347 block in flash memory. If you don’t press this button,
348 any changes you make will be lost.
349 </dd><dt><span class="term">
352 This resets the dialog to the most recently saved
353 values, erasing any changes you have made.
354 </dd><dt><span class="term">
357 This reboots the device. Use this to switch from idle
358 to pad mode by rebooting once the rocket is oriented
359 for flight, or to confirm changes you think you saved
361 </dd><dt><span class="term">
364 This closes the dialog. Any unsaved changes will be
366 </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
367 altitude) at which the <span class="emphasis"><em>main</em></span> igniter will fire. The
368 drop-down menu shows some common values, but you can
369 edit the text directly and choose whatever you
370 like. If the apogee charge fires below this altitude,
371 then the main charge will fire two seconds after the
372 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
373 important to ensure that multiple apogee charges don’t
374 fire at precisely the same time, as that can over
375 pressurize the apogee deployment bay and cause a
376 structural failure of the air-frame. The Apogee Delay
377 parameter tells the flight computer to fire the apogee
378 charge a certain number of seconds after apogee has
379 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 boost
380 where the flight computer will not fire the apogee
381 charge, even if the rocket appears to be at
382 apogee. This is often called <span class="emphasis"><em>Mach Delay</em></span>, as it is
383 intended to prevent a flight computer from
384 unintentionally firing apogee charges due to the
385 pressure spike that occurrs across a mach
386 transition. Altus Metrum flight computers include a
387 Kalman filter which is not fooled by this sharp
388 pressure increase, and so this setting should be left
389 at the default value of zero to disable it.</p></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
390 for each flight log. The available space will
391 be divided into chunks of this size. A smaller
392 value will allow more flights to be stored, a
393 larger value will record data from longer
394 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
395 channels (Apogee and Main) to be used in different
396 configurations.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
399 This is the usual mode of operation; the
400 <span class="emphasis"><em>apogee</em></span> channel is fired at apogee and the
401 <span class="emphasis"><em>main</em></span> channel at the height above ground
402 specified by the <span class="emphasis"><em>Main Deploy Altitude</em></span> during
404 </dd><dt><span class="term">
407 This fires both channels at apogee, the
408 <span class="emphasis"><em>apogee</em></span> channel first followed after a two
409 second delay by the <span class="emphasis"><em>main</em></span> channel.
410 </dd><dt><span class="term">
413 This fires both channels at the height above
414 ground specified by the Main Deploy Altitude
415 setting during descent. The <span class="emphasis"><em>apogee</em></span> channel
416 is fired first, followed after a two second
417 delay by the <span class="emphasis"><em>main</em></span> channel.
418 </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
419 computers works best at 4000Hz, however if you
420 have more than one flight computer in a single
421 airframe, having all of them sound at the same
422 frequency can be confusing. This parameter
423 lets you adjust the base beeper frequency
424 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="idm541"></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
425 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
426 flash data to this directory. This
427 directory is also used as the staring point
428 when selecting data files for display or
429 export.</p><p>Click on the directory name to bring up a
430 directory choosing dialog, select a new
431 directory and click <span class="emphasis"><em>Select Directory</em></span> to
432 change where AltosUI reads and writes data
433 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)
434 and imperial units (feet and miles). This
435 affects the display of values use during
436 flight monitoring, configuration, data
437 graphing and all of the voice
438 announcements. It does not change the units
439 used when exporting to CSV files, those are
440 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
441 device to be dumped to the console from which
442 AltosUI was started. If you’ve started it from
443 an icon or menu entry, the output will simply
444 be discarded. This mode can be useful to debug
445 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
446 monitor window. Choose between the small,
447 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
448 interface appearances. The default selection
449 is supposed to match the native window system
450 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
451 AltosUI window that includes all of the
452 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
456 over USB (self programming). Please read
457 the directions for flashing devices in
458 <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="idm575"></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
459 computer to help test recovery systems
460 deployment.</p><p>Selecting the <span class="emphasis"><em>Fire Igniter</em></span> button brings up the
461 usual device selection dialog. Pick the desired
462 device. This brings up another window which shows the
463 current continuity test status for all of the pyro
464 channels.</p><p>Next, select the desired igniter to fire. This will
465 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>
466 button. The word <span class="emphasis"><em>Arm</em></span> is replaced by a countdown
467 timer indicating that you have 10 seconds to press the
468 <span class="emphasis"><em>Fire</em></span> button or the system will deactivate, at which
469 point you start over again at selecting the desired
470 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
471 fundamental modes, “idle” and “flight”. Which of these modes
472 the firmware operates in is determined at start up
477 accelerometer we can use to determine orientation, “idle” mode
478 is selected if the board is connected via USB to a computer,
479 otherwise the board enters “flight” mode.</p><p>At power on, the altimeter will beep out the battery voltage
480 to the nearest tenth of a volt. Each digit is represented by
481 a sequence of short “dit” beeps, with a pause between
482 digits. A zero digit is represented with one long “dah”
483 beep. Then there will be a short pause while the altimeter
484 completes initialization and self test, and decides which mode
485 to enter next.</p><p>In flight or “pad” mode, the altimeter engages the flight
486 state machine, goes into transmit-only mode to send telemetry,
487 and waits for launch to be detected. Flight mode is indicated
488 by an “di-dah-dah-dit” (“P” for pad) on the beeper or lights,
489 followed by beeps or flashes indicating the state of the
490 pyrotechnic igniter continuity. One beep/flash indicates
491 apogee continuity, two beeps/flashes indicate main continuity,
492 three beeps/flashes indicate both apogee and main continuity,
493 and one longer “brap” sound which is made by rapidly
494 alternating between two tones indicates no continuity. For a
495 dual deploy flight, make sure you’re getting three beeps or
496 flashes before launching! For apogee-only or motor eject
497 flights, do what makes sense.</p><p>If idle mode is entered, you will hear an audible “di-dit” or
498 see two short flashes (“I” for idle), and the flight state
499 machine is disengaged, thus no ejection charges will fire.
500 Idle mode is useful for configuring the altimeter, for
501 extracting data from the on-board storage chip after
502 flight, and for ground testing pyro charges.</p><p>In “Idle” and “Pad” modes, once the mode indication
503 beeps/flashes and continuity indication has been sent, if
504 there is no space available to log the flight in on-board
505 memory, the flight computer will emit a warbling tone (much
506 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
507 the audio signals used.</p><p>Once landed, the flight computer will signal that by emitting
508 the “Landed” sound described above, after which it will beep
509 out the apogee height (in meters). Each digit is represented
510 by a sequence of short “dit” beeps, with a pause between
511 digits. A zero digit is represented with one long “dah”
512 beep. The flight computer will continue to report landed mode
513 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
514 for flight is ground testing the recovery system.</p><p>Just prep the rocket for flight, then power up the altimeter
517 You can now command the altimeter to fire the apogee
518 or main charges from a safe distance using your
519 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
520 very simple. Even on our baro-only TeleMini and
521 EasyMini boards, the use of a Kalman filter means
522 there is no need to set a “mach delay”. All of the
523 configurable parameters can be set using AltosUI. Read
524 <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.
525 When handled gently and properly installed in an air-frame, they
526 will deliver impressive results. However, as with all electronic
527 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
528 extraordinary power density. This is great because we can fly with
529 much less battery mass than if we used alkaline batteries or previous
530 generation rechargeable batteries… but if they are punctured
531 or their leads are allowed to short, they can and will release their
533 Thus we recommend that you take some care when handling our batteries
534 and consider giving them some extra protection in your air-frame. We
535 often wrap them in suitable scraps of closed-cell packing foam before
536 strapping them down, for example.</p></div><p>The barometric sensors used on all of our flight computers are
537 sensitive to sunlight. In normal mounting situations, the baro sensor
538 and all of the other surface mount components
539 are “down” towards whatever the underlying mounting surface is, so
540 this is not normally a problem. Please consider this when designing an
541 installation in an air-frame with a see-through plastic payload bay. It
542 is particularly important to
543 consider this with TeleMini v1.0, both because the baro sensor is on the
544 “top” of the board, and because many model rockets with payload bays
545 use clear plastic for the payload bay! Replacing these with an opaque
546 cardboard tube, painting them, or wrapping them with a layer of masking
547 tape are all reasonable approaches to keep the sensor out of direct
548 sunlight.</p><p>The barometric sensor sampling port must be able to “breathe”,
549 both by not being covered by foam or tape or other materials that might
550 directly block the hole on the top of the sensor, and also by having a
551 suitable static vent to outside air.</p><p>As with all other rocketry electronics, Altus Metrum altimeters must
552 be protected from exposure to corrosive motor exhaust and ejection
553 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
554 programmed directly over their USB connectors (self
555 programming).</p><p>You may wish to begin by ensuring you have current firmware
556 images. These are distributed as part of the AltOS software
557 bundle that also includes the AltosUI ground station program.
558 Newer ground station versions typically work fine with older
559 firmware versions, so you don’t need to update your devices
560 just to try out new software features. You can always
561 download the most recent version from
562 <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
563 connecting them to your computer over USB.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
564 Attach a battery if necessary and power switch to
565 the target device. Power up the device.
566 </li><li class="listitem">
567 Using a Micro USB cable, connect the target device to your
568 computer’s USB socket.
569 </li><li class="listitem">
570 Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from the File menu.
571 </li><li class="listitem">
572 Select the target device in the Device Selection dialog.
573 </li><li class="listitem">
574 Select the image you want to flash to the device,
575 which should have a name in the form
576 <product>-v<product-version>-<software-version>.ihx,
577 such as EasyMini-v1.0-1.6.0.ihx.
578 </li><li class="listitem">
579 Make sure the configuration parameters are
580 reasonable looking. If the serial number and/or RF
581 configuration values aren’t right, you’ll need to
583 </li><li class="listitem">
584 Hit the <span class="emphasis"><em>OK</em></span> button and the software should proceed
585 to flash the device with new firmware, showing a
587 </li><li class="listitem">
588 Verify that the device is working by using the
589 <span class="emphasis"><em>Configure Altimeter</em></span> or <span class="emphasis"><em>Configure Groundstation</em></span>
590 item to check over the configuration.
591 </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
592 unable to boot. Not to worry, you can force the device to
593 start the boot loader instead, which will let you try to
594 flash the device again.</p><p>On each device, connecting two pins from one of the exposed
595 connectors will force the boot loader to start, even if the
596 regular operating system has been corrupted in some way.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
599 Connect pin 6 and pin 1 of the debug connector, which
600 is the six holes next to the beeper. Pin 1 can be
601 identified by the square pad around it, and then the
602 pins could sequentially across the board, making Pin 6
603 the one on the other end of the row.
604 </dd></dl></div><p>Once you’ve located the right pins:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
605 Turn the altimeter power off.
606 </li><li class="listitem">
608 </li><li class="listitem">
609 Connect the indicated terminals together with a
610 short piece of wire. Take care not to accidentally
611 connect anything else.
612 </li><li class="listitem">
614 </li><li class="listitem">
615 Turn the board power on.
616 </li></ol></div><p>The board should now be visible over USB as
617 <span class="emphasis"><em>AltosFlash</em></span> and be ready to receive firmware. Once
618 the board has been powered up, you can remove the
619 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
620 during ascent and 10 samples per second during
623 an on-board flash memory part, which can be partitioned into
624 several equal-sized blocks, one for each flight.</p><div class="table"><a id="idm675"></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,
625 each of a fixed maximum size. Increase the maximum size of
626 each log and you reduce the number of flights that can be
627 stored. Decrease the size and you can store more flights.</p><p>Configuration data is also stored in the flash memory on
630 of flash space. This configuration space is not available
631 for storing flight log data.</p><p>To compute the amount of space needed for a single flight, you
632 can multiply the expected ascent time (in seconds) by 100
633 times bytes-per-sample, multiply the expected descent time (in
634 seconds) by 10 times the bytes per sample and add the two
635 together. That will slightly under-estimate the storage (in
636 bytes) needed for the flight.</p><p>The default size allows for several flights on each flight
638 You can adjust the size.</p><p>Altus Metrum flight computers will not overwrite existing
639 flight data, so be sure to download flight data and erase it
640 from the flight computer before it fills up. The flight
641 computer will still successfully control the flight even if it
642 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
643 production and retired.</p><div class="table"><a id="idm706"></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; " align="left" valign="top"><p>EasyMini v1.0</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>MS5607 30km (100k')</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>-</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="idm746"></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_6_3"></a>F.1. 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
644 for our host software on desktops, laptops an android devices
645 along with BlueTooth support for Windows.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos"></a>F.1.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
646 Fix hardware flow control on TeleBT v3.0. RTS/CTS is
647 wired backwards on this board, switch from using the
648 hardware to driving these pins with software.
649 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications"></a>F.1.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
650 Add BlueTooth support for Windows operating system. This
651 supports connections to TeleBT over BlueTooth rather than
653 </li></ul></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
654 Change Java detection and install on Windows. Detection is
655 now done by looking for the <span class="emphasis"><em>javaw.exe</em></span> program, and
656 installation by opening a browser on the java.com web site.
657 </li><li class="listitem">
658 Delay polling while the Fire Igniters is visible to allow
659 for TeleMega to report back complete status over the radio.
660 </li><li class="listitem">
661 Disallow changing RF calibration numbers in the
662 configuration UI. There’s no good reason to change this from
663 the field, and recovering is really hard if you haven’t
664 written down the right number.
665 </li><li class="listitem">
666 Fix USB device discovery on Mac OS X El Capitan. This makes
667 the connected Altus Metrum USB devices appear again.
668 </li><li class="listitem">
669 Fix acceleration data presented in MonitorIdle mode for
670 TeleMetrum v2.0 flight computers.
671 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosdroid"></a>F.1.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">
672 Monitor Idle mode. Check state of flight computer while in
673 idle mode over the radio link
674 </li><li class="listitem">
675 Fire Igniters. Remotely fire ignires for recovery system
677 </li><li class="listitem">
678 Remote reboot. Cause the flight computer to reboot over the
679 radio link. This provides a method for switching the flight
680 computer from idle to flight mode without needing to reach
682 </li><li class="listitem">
683 Configurable frequency menu. Change the set of available
684 frequencies and provide more descriptive names.
685 </li></ul></div><p>AltosDroid bug fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
686 Don’t set target location if GPS hasn’t locked yet.
687 </li><li class="listitem">
688 Fix saving target states so they can be reloaded when the
689 application restarts. When the application is shut down and
690 restarted, all previous target state information will be
691 restored (including GPS position if available).
692 </li><li class="listitem">
693 Fix crash on some Android devices for offline maps when
694 changing the map scale or location.
695 </li><li class="listitem">
696 Don’t require USB OTG support. This kept the latest
697 AltosDroid from being offered on devices without USB device
698 support, although it can work without that just fine using
700 </li><li class="listitem">
701 Don’t require bluetooth to be enabled. This allows the
702 application to operate with USB devices or just show old
703 data without turning on the bluetooth radio.
704 </li><li class="listitem">
705 Recover old tracker positions when restarting
706 application. This finally allows you to safely stop and
707 restart the application without losing the last known
708 location of any tracker.
709 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation"></a>F.1.4. Documentation</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
710 Document TeleMega and EasyMega additional pyro channel
711 continuity audio alert pattern.
712 </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.2. Release Notes for Version 1.6.2</h2></div></div></div><p>Version 1.6.2 includes support for our updated TeleMega v2.0
713 product and bug fixes in in the flight software for all our boards
714 and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_2"></a>F.2.1. AltOS</h3></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
715 Add support for TeleMega v2.0 boards.
716 </li><li class="listitem">
717 Add PWM servo driver. There’s no higher level code using
718 this yet, but the driver allows testing of the TeleMega v2.0
719 servo output connector.
720 </li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
721 Slow down telemetry packets to allow receiver to keep
723 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_2"></a>F.2.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
724 Fix post-flight orientation computation when processing
725 TeleMega and EasyMega eeprom data files.
726 </li><li class="listitem">
727 Capture complete eeprom data even when there are invalid
728 entries in the data. This keeps reading eeprom contents and
729 writing the associated .eeprom file when an error is detected.
730 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation_2"></a>F.2.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">
731 HTML versions now have a table of contents on the left side.
732 </li><li class="listitem">
733 EasyMini now has its own shorter manual.
734 </li><li class="listitem">
735 Provide links between sections in each document.
736 </li><li class="listitem">
737 Lots of minor rewriting and restructuring to avoid
738 duplication of information
739 </li></ul></div></div></div></div></div></body></html>
projects / web / altusmetrum / blob