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>The Altus Metrum System</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>The Altus Metrum System</h1></div><div><h2 class="subtitle">An Owner's Manual for Altus Metrum Rocketry Electronics</h2></div><div><h3 class="corpauthor">
3 <span class="inlinemediaobject"><img src="altusmetrum-oneline.svg" width="360" /></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><div class="author"><h3 class="author"><span class="firstname">Bob</span> <span class="surname">Finch</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Anthony</span> <span class="surname">Towns</span></h3></div></div><div><p class="copyright">Copyright © 2016 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm29"></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="altusmetrum-revhistory.html">Revision History</a></div></div><hr /></div><div class="dedication"><div class="titlepage"><div><div><h1 class="title"><a id="_acknowledgments"></a>Acknowledgments</h1></div></div></div><p>Thanks to Bob Finch, W9YA, NAR 12965, TRA 12350 for writing “The
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="#_ground_station_hardware">2.2. Ground Station Hardware</a></span></dt><dt><span class="section"><a href="#_linux_mac_windows_ground_station_software">2.3. Linux/Mac/Windows Ground Station Software</a></span></dt><dt><span class="section"><a href="#_android_ground_station_software">2.4. Android Ground Station Software</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_using_altus_metrum_hardware">3. Using Altus Metrum Hardware</a></span></dt><dd><dl><dt><span class="section"><a href="#_wiring_and_electrical_interference">3.1. Wiring and Electrical Interference</a></span></dt><dt><span class="section"><a href="#_hooking_up_lithium_polymer_batteries">3.2. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#_hooking_up_pyro_charges">3.3. Hooking Up Pyro Charges</a></span></dt><dt><span class="section"><a href="#_hooking_up_a_power_switch">3.4. Hooking Up a Power Switch</a></span></dt><dt><span class="section"><a href="#_understanding_beeps">3.5. Understanding Beeps</a></span></dt><dt><span class="section"><a href="#_turning_on_the_power">3.6. Turning On the Power</a></span></dt><dt><span class="section"><a href="#_using_an_external_active_switch_circuit">3.7. Using an External Active Switch Circuit</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery">3.8. Using a Separate Pyro Battery</a></span></dt><dt><span class="section"><a href="#_using_a_different_kind_of_battery">3.9. Using a Different Kind of Battery</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_telemetrum">4. TeleMetrum</a></span></dt><dd><dl><dt><span class="section"><a href="#_telemetrum_screw_terminals">4.1. TeleMetrum Screw Terminals</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery_with_telemetrum">4.2. Using a Separate Pyro Battery with TeleMetrum</a></span></dt><dt><span class="section"><a href="#_using_an_active_switch_with_telemetrum">4.3. Using an Active Switch with TeleMetrum</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_telemini_v1_0">5. TeleMini v1.0</a></span></dt><dd><dl><dt><span class="section"><a href="#_telemini_v1_0_screw_terminals">5.1. TeleMini v1.0 Screw Terminals</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery_with_telemini_v1_0">5.2. Using a Separate Pyro Battery with TeleMini v1.0</a></span></dt><dt><span class="section"><a href="#_using_an_active_switch_with_telemini_v1_0">5.3. Using an Active Switch with TeleMini v1.0</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_easymini">6. EasyMini</a></span></dt><dd><dl><dt><span class="section"><a href="#_easymini_screw_terminals">6.1. EasyMini Screw Terminals</a></span></dt><dt><span class="section"><a href="#_connecting_a_battery_to_easymini">6.2. Connecting A Battery To EasyMini</a></span></dt><dt><span class="section"><a href="#_charging_lithium_batteries">6.3. Charging Lithium Batteries</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery_with_easymini">6.4. Using a Separate Pyro Battery with EasyMini</a></span></dt><dt><span class="section"><a href="#_using_an_active_switch_with_easymini">6.5. Using an Active Switch with EasyMini</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_telemega">7. TeleMega</a></span></dt><dd><dl><dt><span class="section"><a href="#_telemega_screw_terminals">7.1. TeleMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery_with_telemega">7.2. Using a Separate Pyro Battery with TeleMega</a></span></dt><dt><span class="section"><a href="#_using_only_one_battery_with_telemega">7.3. Using Only One Battery With TeleMega</a></span></dt><dt><span class="section"><a href="#_using_an_active_switch_with_telemega">7.4. Using an Active Switch with TeleMega</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_easymega">8. EasyMega</a></span></dt><dd><dl><dt><span class="section"><a href="#_easymega_screw_terminals">8.1. EasyMega Screw Terminals</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery_with_easymega">8.2. Using a Separate Pyro Battery with EasyMega</a></span></dt><dt><span class="section"><a href="#_using_only_one_battery_with_easymega">8.3. Using Only One Battery With EasyMega</a></span></dt><dt><span class="section"><a href="#_using_an_active_switch_with_easymega">8.4. Using an Active Switch with EasyMega</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_installation">9. Installation</a></span></dt><dt><span class="chapter"><a href="#_using_altus_metrum_products">10. Using Altus Metrum Products</a></span></dt><dd><dl><dt><span class="section"><a href="#_being_legal">10.1. Being Legal</a></span></dt><dt><span class="section"><a href="#_in_the_rocket">10.2. In the Rocket</a></span></dt><dt><span class="section"><a href="#_on_the_ground">10.3. On the Ground</a></span></dt><dt><span class="section"><a href="#_data_analysis">10.4. Data Analysis</a></span></dt><dt><span class="section"><a href="#_future_plans">10.5. Future Plans</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_altosui">11. AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#_monitor_flight">11.1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#_launch_pad">11.1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#_ascent">11.1.2. Ascent</a></span></dt><dt><span class="section"><a href="#_descent">11.1.3. Descent</a></span></dt><dt><span class="section"><a href="#_landed">11.1.4. Landed</a></span></dt><dt><span class="section"><a href="#_table">11.1.5. Table</a></span></dt><dt><span class="section"><a href="#_site_map">11.1.6. Site Map</a></span></dt><dt><span class="section"><a href="#_igniter">11.1.7. Igniter</a></span></dt></dl></dd><dt><span class="section"><a href="#_save_flight_data">11.2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#_replay_flight">11.3. Replay Flight</a></span></dt><dt><span class="section"><a href="#_graph_data">11.4. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#_flight_graph">11.4.1. Flight Graph</a></span></dt><dt><span class="section"><a href="#_configure_graph">11.4.2. Configure Graph</a></span></dt><dt><span class="section"><a href="#_flight_statistics">11.4.3. Flight Statistics</a></span></dt><dt><span class="section"><a href="#_map">11.4.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#_export_data">11.5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#_comma_separated_value_format">11.5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#_keyhole_markup_language_for_google_earth">11.5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#_configure_altimeter">11.6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#_main_deploy_altitude">11.6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#_apogee_delay">11.6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#_apogee_lockout">11.6.3. Apogee Lockout</a></span></dt><dt><span class="section"><a href="#_frequency">11.6.4. Frequency</a></span></dt><dt><span class="section"><a href="#_rf_calibration">11.6.5. RF Calibration</a></span></dt><dt><span class="section"><a href="#_telemetry_rdf_aprs_enable">11.6.6. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#_telemetry_baud_rate">11.6.7. Telemetry baud rate</a></span></dt><dt><span class="section"><a href="#_aprs_interval">11.6.8. APRS Interval</a></span></dt><dt><span class="section"><a href="#_aprs_ssid">11.6.9. APRS SSID</a></span></dt><dt><span class="section"><a href="#_aprs_format">11.6.10. APRS Format</a></span></dt><dt><span class="section"><a href="#_callsign">11.6.11. Callsign</a></span></dt><dt><span class="section"><a href="#_maximum_flight_log_size">11.6.12. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#_ignitor_firing_mode">11.6.13. Ignitor Firing Mode</a></span></dt><dt><span class="section"><a href="#_pad_orientation">11.6.14. Pad Orientation</a></span></dt><dt><span class="section"><a href="#_beeper_frequency">11.6.15. Beeper Frequency</a></span></dt><dt><span class="section"><a href="#_logging_trigger_motion">11.6.16. Logging Trigger Motion</a></span></dt><dt><span class="section"><a href="#_position_reporting_interval">11.6.17. Position Reporting Interval</a></span></dt><dt><span class="section"><a href="#_configure_pyro_channels">11.6.18. Configure Pyro Channels</a></span></dt></dl></dd><dt><span class="section"><a href="#_configure_altosui">11.7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#_voice_settings">11.7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#_log_directory">11.7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#_callsign_2">11.7.3. Callsign</a></span></dt><dt><span class="section"><a href="#_imperial_units">11.7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#_serial_debug">11.7.5. Serial Debug</a></span></dt><dt><span class="section"><a href="#_font_size">11.7.6. Font size</a></span></dt><dt><span class="section"><a href="#_look_amp_feel">11.7.7. Look & feel</a></span></dt><dt><span class="section"><a href="#_menu_position">11.7.8. Menu position</a></span></dt><dt><span class="section"><a href="#_map_cache_size">11.7.9. Map Cache Size</a></span></dt><dt><span class="section"><a href="#_manage_frequencies">11.7.10. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#_configure_groundstation">11.8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#_frequency_2">11.8.1. Frequency</a></span></dt><dt><span class="section"><a href="#_rf_calibration_2">11.8.2. RF Calibration</a></span></dt><dt><span class="section"><a href="#_telemetry_rate">11.8.3. Telemetry Rate</a></span></dt></dl></dd><dt><span class="section"><a href="#_flash_image">11.9. Flash Image</a></span></dt><dt><span class="section"><a href="#_fire_igniter">11.10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#_scan_channels">11.11. Scan Channels</a></span></dt><dt><span class="section"><a href="#_load_maps">11.12. Load Maps</a></span></dt><dt><span class="section"><a href="#_monitor_idle">11.13. Monitor Idle</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_altosdroid">12. AltosDroid</a></span></dt><dd><dl><dt><span class="section"><a href="#_installing_altosdroid">12.1. Installing AltosDroid</a></span></dt><dt><span class="section"><a href="#_charging_telebt_battery">12.2. Charging TeleBT Battery</a></span></dt><dt><span class="section"><a href="#_connecting_to_telebt_over_bluetooth">12.3. Connecting to TeleBT over Bluetooth™</a></span></dt><dt><span class="section"><a href="#_connecting_to_teledongle_or_telebt_over_usb">12.4. Connecting to TeleDongle or TeleBT over USB</a></span></dt><dt><span class="section"><a href="#_altosdroid_menu">12.5. AltosDroid Menu</a></span></dt><dt><span class="section"><a href="#_setup">12.6. Setup</a></span></dt><dt><span class="section"><a href="#_idle_mode">12.7. Idle Mode</a></span></dt><dt><span class="section"><a href="#_altosdroid_flight_monitoring">12.8. AltosDroid Flight Monitoring</a></span></dt><dt><span class="section"><a href="#_pad">12.9. Pad</a></span></dt><dt><span class="section"><a href="#_flight">12.10. Flight</a></span></dt><dt><span class="section"><a href="#_recover">12.11. Recover</a></span></dt><dt><span class="section"><a href="#_map_2">12.12. Map</a></span></dt><dt><span class="section"><a href="#_downloading_flight_logs">12.13. Downloading Flight Logs</a></span></dt></dl></dd><dt><span class="appendix"><a href="#_system_operation">A. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#_firmware_modes">A.1. Firmware Modes</a></span></dt><dt><span class="section"><a href="#_gps">A.2. GPS</a></span></dt><dt><span class="section"><a href="#_controlling_an_altimeter_over_the_radio_link">A.3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#_ground_testing">A.4. Ground Testing</a></span></dt><dt><span class="section"><a href="#_radio_link">A.5. Radio Link</a></span></dt><dt><span class="section"><a href="#_aprs">A.6. APRS</a></span></dt><dt><span class="section"><a href="#_configurable_parameters">A.7. Configurable Parameters</a></span></dt></dl></dd><dt><span class="appendix"><a href="#_handling_precautions">B. Handling Precautions</a></span></dt><dt><span class="appendix"><a href="#_updating_device_firmware">C. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#_updating_telemega_telemetrum_v2_easymega_easymini_or_teledongle_v3_firmware">C.1. Updating TeleMega, TeleMetrum v2, EasyMega, EasyMini or TeleDongle v3 Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#_recovering_from_self_flashing_failure">C.1.1. Recovering From Self-Flashing Failure</a></span></dt></dl></dd><dt><span class="section"><a href="#_pair_programming">C.2. Pair Programming</a></span></dt><dd><dl><dt><span class="section"><a href="#_updating_telemetrum_v1_x_firmware">C.2.1. Updating TeleMetrum v1.x Firmware</a></span></dt><dt><span class="section"><a href="#_updating_telemini_firmware">C.2.2. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#_updating_teledongle_v0_2_firmware">C.2.3. Updating TeleDongle v0.2 Firmware</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#_flight_data_recording">D. Flight Data Recording</a></span></dt><dt><span class="appendix"><a href="#_altus_metrum_hardware_specifications">E. Altus Metrum Hardware Specifications</a></span></dt><dt><span class="appendix"><a href="#_release_notes">F. Release Notes</a></span></dt><dd><dl><dt><span class="section"><a href="#_release_notes_for_version_1_6_5">F.1. Release Notes for Version 1.6.5</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_and_altosdroid_applications">F.1.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.2. Release Notes for Version 1.6.4</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_and_altosdroid_applications_2">F.2.2. AltosUI, TeleGPS and AltosDroid Applications</a></span></dt><dt><span class="section"><a href="#_documentation">F.2.3. Documentation</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_3">F.3. Release Notes for Version 1.6.3</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_3">F.3.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications">F.3.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_altosdroid_2">F.3.3. AltosDroid</a></span></dt><dt><span class="section"><a href="#_documentation_2">F.3.4. Documentation</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_2">F.4. Release Notes for Version 1.6.2</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_2">F.4.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_documentation_3">F.4.3. Documentation</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_1">F.5. Release Notes for Version 1.6.1</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_3">F.5.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_altosdroid_3">F.5.3. AltosDroid</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6">F.6. Release Notes for Version 1.6</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_4">F.6.2. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_5">F.7. Release Notes for Version 1.5</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_5">F.7.2. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_4_2">F.8. Release Notes for Version 1.4.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_and_telegps_applications_6">F.8.1. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_4_1">F.9. Release Notes for Version 1.4.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_and_telegps_applications_7">F.9.1. AltosUI and TeleGPS Applications:</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_4">F.10. Release Notes for Version 1.4</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_8">F.10.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application">F.10.2. AltosUI Application</a></span></dt><dt><span class="section"><a href="#_telegps_application">F.10.3. TeleGPS Application</a></span></dt><dt><span class="section"><a href="#_documentation_4">F.10.4. Documentation</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_3_2">F.11. Release Notes for Version 1.3.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_9">F.11.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_2">F.11.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_3_1">F.12. Release Notes for Version 1.3.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_10">F.12.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_3">F.12.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_3">F.13. Release Notes for Version 1.3</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_11">F.13.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_4">F.13.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_2_1">F.14. Release Notes for Version 1.2.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_12">F.14.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_5">F.14.2. AltosUI Application</a></span></dt><dt><span class="section"><a href="#_altosdroid_4">F.14.3. AltosDroid</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_2">F.15. Release Notes for Version 1.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_13">F.15.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_micropeak_application">F.15.2. AltosUI and MicroPeak Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_1">F.16. Release Notes for Version 1.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_14">F.16.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_2">F.16.2. AltosUI</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_1_2">F.17. Release Notes for Version 1.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_15">F.17.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_3">F.17.2. AltosUI</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_0_1">F.18. Release Notes for Version 1.0.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_16">F.18.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_6">F.18.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_0_9_2">F.19. Release Notes for Version 0.9.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_4">F.19.1. AltosUI</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_0_9">F.20. Release Notes for Version 0.9</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_17">F.20.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_7">F.20.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_0_8">F.21. Release Notes for Version 0.8</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_application_8">F.21.1. AltosUI Application:</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_0_7_1">F.22. Release Notes for Version 0.7.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_application_9">F.22.1. AltosUI Application</a></span></dt></dl></dd></dl></dd></dl></div><div class="list-of-figures"><p><strong>List of Figures</strong></p><dl><dt>4.1. <a href="#idm422">TeleMetrum v2 Board</a></dt><dt>4.2. <a href="#idm429">TeleMetrum v1 Board</a></dt><dt>5.1. <a href="#idm515">TeleMini v1.0 Board</a></dt><dt>6.1. <a href="#idm592">EasyMini Board</a></dt><dt>7.1. <a href="#idm694">TeleMega Board</a></dt><dt>8.1. <a href="#idm864">EasyMega Board</a></dt><dt>11.1. <a href="#idm1082">AltosUI Main Window</a></dt><dt>11.2. <a href="#idm1093">Device Selection Dialog</a></dt><dt>11.3. <a href="#idm1121">Monitor Flight Launch Pad View</a></dt><dt>11.4. <a href="#idm1161">Monitor Flight Ascent View</a></dt><dt>11.5. <a href="#idm1174">Monitor Flight Descent View</a></dt><dt>11.6. <a href="#idm1187">Monitor Flight Landed View</a></dt><dt>11.7. <a href="#idm1202">Monitor Flight Table View</a></dt><dt>11.8. <a href="#idm1212">Monitor Flight Site Map View</a></dt><dt>11.9. <a href="#idm1227">Monitor Flight Additional Igniter View</a></dt><dt>11.10. <a href="#idm1257">Flight Data Graph</a></dt><dt>11.11. <a href="#idm1268">Flight Graph Configuration</a></dt><dt>11.12. <a href="#idm1278">Flight Statistics</a></dt><dt>11.13. <a href="#idm1288">Flight Map</a></dt><dt>11.14. <a href="#idm1309">Altimeter Configuration</a></dt><dt>11.15. <a href="#idm1421">Additional Pyro Channel Configuration</a></dt><dt>11.16. <a href="#idm1498">Configure AltosUI Dialog</a></dt><dt>11.17. <a href="#idm1551">Configure Groundstation Dialog</a></dt><dt>11.18. <a href="#idm1591">Fire Igniter Window</a></dt><dt>11.19. <a href="#idm1610">Scan Channels Window</a></dt><dt>11.20. <a href="#idm1620">Load Maps Window</a></dt><dt>11.21. <a href="#idm1653">Monitor Idle Window</a></dt></dl></div><div class="list-of-tables"><p><strong>List of Tables</strong></p><dl><dt>3.1. <a href="#idm184">AltOS Modes</a></dt><dt>3.2. <a href="#idm292">Pad/Idle Indications</a></dt><dt>3.3. <a href="#idm347">Pad Radio Indications</a></dt><dt>4.1. <a href="#idm449">TeleMetrum Screw Terminals</a></dt><dt>5.1. <a href="#idm526">TeleMini v1.0 Screw Terminals</a></dt><dt>6.1. <a href="#idm604">EasyMini Screw Terminals</a></dt><dt>7.1. <a href="#idm714">TeleMega Screw Terminals</a></dt><dt>8.1. <a href="#idm875">EasyMega Screw Terminals</a></dt><dt>A.1. <a href="#idm1989">Altus Metrum APRS Comments</a></dt><dt>D.1. <a href="#idm2240">Data Storage on Altus Metrum altimeters</a></dt><dt>E.1. <a href="#idm2326">Altus Metrum Flight Computer Electronics</a></dt><dt>E.2. <a href="#idm2502">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, v2.0,
36 includes a beeper, USB data download and extended on-board
37 flight logging, along with 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>For TeleMetrum, TeleMega and EasyMega, the battery can be charged by plugging it into the
59 corresponding socket of the device and then using the USB
60 cable to plug the flight computer into your computer’s USB socket. The
61 on-board circuitry will charge the battery whenever it is plugged
62 in, because the on-off switch does NOT control the
66 EasyMini battery can be charged by disconnecting it
67 from the board and plugging it into a standalone
68 battery charger such as <a class="ulink" href="http://altusmetrum.org/LipoCharger" target="_top">LipoCharger</a>, and
69 connecting that via a USB cable to a laptop or other
70 USB power source.</p><p>You can also choose to use another battery with
71 EasyMini, anything supplying between 4 and 12 volts should
72 work fine (like a standard 9V battery), but if you are planning
73 to fire pyro charges, ground testing is required to verify that
74 the battery supplies enough current to fire your chosen e-matches.</p><div class="note" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Note</h3><p>On TeleMetrum v1 boards, when the GPS chip is initially
75 searching for satellites, TeleMetrum will consume more current
76 than it pulls from the USB port, so the battery must be
77 attached in order to get satellite lock. Once GPS is locked,
78 the current consumption goes back down enough to enable charging
79 while running. So it’s a good idea to fully charge the battery
80 as your first item of business so there is no issue getting and
81 maintaining satellite lock. The yellow charge indicator led
82 will go out when the battery is nearly full and the charger goes
83 to trickle charge. It can take several hours to fully recharge a
84 deeply discharged battery.</p><p>TeleMetrum v2.0, TeleMega and EasyMega use a higher power battery charger,
85 allowing them to charge the battery while running the board at
86 maximum power. When the battery is charging, or when the board
87 is consuming a lot of power, the red LED will be lit. When the
88 battery is fully charged, the green LED will be lit. When the
89 battery is damaged or missing, both LEDs will be lit, which
90 appears yellow.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_ground_station_hardware"></a>2.2. Ground Station Hardware</h2></div></div></div><p>There are two ground stations available, the TeleDongle USB to
91 RF interface and the TeleBT Bluetooth/USB to RF interface. If
92 you plug either of these in to your Mac or Linux computer it should
93 “just work”, showing up as a serial port device. Windows systems need
94 driver information that is part of the AltOS download to know that the
95 existing USB modem driver will work. We therefore recommend installing
96 our software before plugging in TeleDongle if you are using a Windows
97 computer. If you are using an older version of Linux and are having
98 problems, try moving to a fresher kernel (2.6.33 or
99 newer).</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_linux_mac_windows_ground_station_software"></a>2.3. Linux/Mac/Windows Ground Station Software</h2></div></div></div><p>Next you should obtain and install the AltOS software.
100 The AltOS distribution includes the AltosUI ground
101 station program, current firmware images for all of
102 the hardware, and a number of standalone utilities
103 that are rarely needed. Pre-built binary packages are
104 available for Linux, Microsoft Windows, Mac OSX. Full
105 source code and build instructions are also
106 available. The latest version may always be downloaded
107 from <a class="ulink" href="http://altusmetrum.org/AltOS" target="_top">http://altusmetrum.org/AltOS</a></p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_android_ground_station_software"></a>2.4. Android Ground Station Software</h2></div></div></div><p>TeleBT can also connect to an Android device over
108 BlueTooth or USB. The
109 <a class="ulink" href="https://play.google.com/store/apps/details?id=org.altusmetrum.AltosDroid" target="_top">AltosDroid
110 Android application</a> is available from the
111 <a class="ulink" href="https://play.google.com" target="_top">Google Play system</a>.</p><p>You don’t need a data plan to use AltosDroid, but
112 without network access, you’ll want to download
113 offline map data before wandering away from the
114 network.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_using_altus_metrum_hardware"></a>Chapter 3. Using Altus Metrum Hardware</h1></div></div></div><p>Here are general instructions for hooking up an Altus Metrum
115 flight computer. Instructions specific to each model will be
116 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
117 operation of the flight computer, it’s important to always
118 twist pairs of wires connected to the board. Twist the switch
119 leads, the pyro leads and the battery leads. This reduces
120 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
121 series connector to connect up a single-cell Lithium Polymer
122 cell (3.7V nominal). You can purchase matching batteries
123 from the Altus Metrum store, or other vendors, or you can
124 make your own. Pin 1 of the connector is positive, pin 2 is
125 negative. Spark Fun sells a cable with the connector
126 attached, which they call a
127 <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
128 this same connector. All that we have found use the opposite
129 polarity, and if you use them that way, you will damage or
130 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
131 each pyro charge. This means you shouldn’t need to put two
132 wires into a screw terminal or connect leads from pyro
133 charges together externally.</p><p>On the flight computer, one lead from each charge is hooked
134 to the positive battery terminal through the power switch.
135 The other lead is connected through the pyro circuit, which
136 is connected to the negative battery terminal when the pyro
137 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
138 to turn them on. This disconnects both the computer and the
139 pyro charges from the battery, preventing the charges from
140 firing when in the Off position. The switch is in-line with
141 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
142 provide information about the state of the system.
143 TeleMini doesn’t have room for a beeper, so instead it
144 uses an LED, which works the same, except for every
145 beep is replaced with the flash of the LED.</p><p>Here’s a short summary of all of the modes and the
147 (or flashing, in the case of TeleMini v1)
148 that accompanies each mode. In the description of the
149 beeping pattern, “dit” means a short beep while "dah"
150 means a long beep (three times as long). “Brap” means
151 a long dissonant tone.</p><div class="table"><a id="idm184"></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
152 or radio link.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Pad</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>P</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dah dah dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Waiting for launch. Not listening for commands.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Boost</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dah dit dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Accelerating upwards.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Fast</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>F</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dit dah dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Decelerating, but moving faster than 200m/s.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Coast</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>C</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dah dit dah dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Decelerating, moving slower than 200m/s</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Drogue</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dah dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Descending after apogee. Above main height.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>M</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dah dah</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Descending. Below main height.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Landed</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>L</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dah dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Stable altitude for at least ten seconds.</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Sensor error</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>X</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>dah dit dit dah</p></td><td style="" align="left" valign="top"><p>Error detected during sensor calibration.</p></td></tr></tbody></table></div></div><br class="table-break" /><p>Here’s a summary of all of the Pad and Idle mode
153 indications. In Idle mode, you’ll hear one of these
154 just once after the two short dits indicating idle
155 mode. In Pad mode, after the dit dah dah dit
156 indicating Pad mode, you’ll hear these once every five
157 seconds.</p><div class="table"><a id="idm292"></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; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Storage Full</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>warble</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>On-board data logging storage is full. This will
158 not prevent the flight computer from safely
159 controlling the flight or transmitting telemetry
160 signals, but no record of the flight will be
161 stored in on-board flash.</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Additional Igniters</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>four very short beeps</p></td><td style="" align="left" valign="top"><p>Continuity indication for the four additional pyro
162 channels on TeleMega and EasyMega. One high tone for
163 no continuity, one low tone for continuity. These are
164 produced after the continuity indicators for the two
165 primary igniter channels.</p></td></tr></tbody></table></div></div><br class="table-break" /><p>For devices with a radio transmitter, in addition to
166 the digital and APRS telemetry signals, you can also
167 receive audio tones with a standard amateur
168 70cm FM receiver. While on the pad, you will hear
169 igniter status once every five seconds.</p><div class="table"><a id="idm347"></a><p class="title"><strong>Table 3.3. Pad Radio Indications</strong></p><div class="table-contents"><table class="table" summary="Pad Radio Indications" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Name </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Beeps </th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Neither</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>½ second tone</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>No continuity detected on either apogee or main igniters.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Continuity detected only on apogee igniter.</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>dit dit</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Continuity detected only on main igniter.</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Both</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>dit dit dit</p></td><td style="" align="left" valign="top"><p>Continuity detected on both igniters.</p></td></tr></tbody></table></div></div><br class="table-break" /><p>During ascent, the tones will be muted to allow the
170 telemetry data to consume the full radio bandwidth.</p><p>During descent and after landing, a ½ second tone will
171 be transmitted every five seconds. This can be used to
172 find the rocket using RDF techniques when the signal
173 is too weak to receive GPS information via telemetry
174 or APRS.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_turning_on_the_power"></a>3.6. Turning On the Power</h2></div></div></div><p>Connect a battery and power switch and turn the switch
175 to "on". The flight computer will signal power on by
176 reporting the battery voltage and then perform an internal self
177 test and sensor calibration.</p><p>Once the self test and calibration are complete, there
178 are two modes that an Altus Metrum flight computer can
179 operate in:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
182 The flight computer is waiting to detect
183 launch and then fly the rocket. In this mode, the USB
185 disabled, and the radio goes into transmit-only mode.
186 The only way to get out of this
187 mode is to power the flight computer down.
188 </dd><dt><span class="term">
191 The flight computer is ready to communicate over USB
192 and in packet mode over the radio.
194 the flight computer, download data or display
196 </dd></dl></div><p>For flight computers with accelerometers (TeleMetrum,
197 EasyMega and TeleMega), the mode is selected by the
198 orientation of the board during the self test
199 interval. If the board is pointing upwards as if ready
200 to fly, it will enter Flight/Pad mode. Otherwise, it will
201 enter Idle mode.</p><p>For EasyMini, if the USB cable is connected to a
202 computer, it will enter Idle mode. Otherwise, it will
203 enter Flight/Pad mode.</p><p>For TeleMini v1.0, if a packet link is waiting to
204 connect when the device is powered on, it will enter
205 Idle mode, otherwise it will enter Flight/Pad mode.</p><p>You can see in <a class="xref" href="#_understanding_beeps" title="3.5. Understanding Beeps">Section 3.5, “Understanding Beeps”</a>
206 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
207 Featherweight Magnetic Switch, with any Altus Metrum
208 flight computer. These require three connections, one to
209 the battery, one to the positive power input on the flight
210 computer and one to ground. Find instructions on how to
211 hook these up for each flight computer below. Then follow
212 the instructions that come with your active switch to
213 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
214 lead for each of the pyro charges is connected through
215 the power switch directly to the positive battery
216 terminal. The other lead is connected to the pyro
217 circuit, which connects it to the negative battery
218 terminal when the pyro circuit is fired. The pyro
219 circuit on all of the flight computers is designed to
220 handle up to 16V.</p><p>To use a separate pyro battery, connect the negative pyro
221 battery terminal to the flight computer ground terminal,
222 the positive battery terminal to the igniter and the other
223 igniter lead to the negative pyro terminal on the flight
224 computer. When the pyro channel fires, it will complete the
225 circuit between the negative pyro terminal and the ground
226 terminal, firing the igniter. Specific instructions on how
227 to hook this up for each flight computer will be found
228 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
230 designed to use either a
231 lithium polymer battery or any other battery producing
232 between 4 and 12 volts, such as a rectangular 9V
233 battery.</p><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>TeleMega, EasyMega and TeleMetrum are only designed to
234 operate off a single-cell Lithium Polymer battery and
235 cannot be used with any other kind. Connecting a
236 different kind of battery to any of these will destroy
237 the board.</p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_telemetrum"></a>Chapter 4. TeleMetrum</h1></div></div></div><div class="figure"><a id="idm422"></a><p class="title"><strong>Figure 4.1. TeleMetrum v2 Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telemetrum-v2.0-th.jpg" width="495" alt="telemetrum-v2.0-th.jpg" /></div></div></div><br class="figure-break" /><div class="figure"><a id="idm429"></a><p class="title"><strong>Figure 4.2. TeleMetrum v1 Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telemetrum-v1.1-thside.jpg" width="495" alt="telemetrum-v1.1-thside.jpg" /></div></div></div><br class="figure-break" /><p>TeleMetrum is a 1 inch by 2¾ inch circuit board. It was designed to
238 fit inside coupler for 29mm air-frame tubing, but using it in a tube that
239 small in diameter may require some creativity in mounting and wiring
240 to succeed! The presence of an accelerometer means TeleMetrum should
241 be aligned along the flight axis of the airframe, and by default the ¼
242 wave UHF wire antenna should be on the nose-cone end of the board. The
243 antenna wire is about 7 inches long, and wiring for a power switch and
244 the e-matches for apogee and main ejection charges depart from the
245 fin can end of the board, meaning an ideal “simple” avionics
246 bay for TeleMetrum should have at least 10 inches of interior length.</p><p>There are two generations of the TeleMetrum design. The
247 major changes in the v2 generation are:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
248 uBlox GPS chip certified for altitude records
249 </li><li class="listitem">
250 Higher power radio (40mW vs 10mW)
251 </li><li class="listitem">
253 </li></ul></div><p>Otherwise, they’re the same size, with mounting holes and
254 screw terminals in the same position.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_telemetrum_screw_terminals"></a>4.1. TeleMetrum Screw Terminals</h2></div></div></div><p>TeleMetrum has six screw terminals on the end of the board
255 opposite the telemetry antenna. Two are for the power
256 switch, and two each for the apogee and main igniter
257 circuits. Using the picture above and starting from the top,
258 the terminals are as follows:</p><div class="table"><a id="idm449"></a><p class="title"><strong>Table 4.1. TeleMetrum Screw Terminals</strong></p><div class="table-contents"><table class="table" summary="TeleMetrum Screw Terminals" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal #</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal Name</th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Output</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to flight computer</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Input</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to positive battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main +</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>5</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee +</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>6</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Apogee -</p></td><td style="" align="left" valign="top"><p>Apogee pyro channel connection to pyro circuit</p></td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_a_separate_pyro_battery_with_telemetrum"></a>4.2. Using a Separate Pyro Battery with TeleMetrum</h2></div></div></div><p>As described above, using an external pyro battery involves
259 connecting the negative battery terminal to the flight
260 computer ground, connecting the positive battery terminal to
261 one of the igniter leads and connecting the other igniter
262 lead to the per-channel pyro circuit connection.</p><p>To connect the negative battery terminal to the TeleMetrum
263 ground, insert a small piece of wire, 24 to 28 gauge
264 stranded, into the GND hole just above the screw terminal
265 strip and solder it in place.</p><p>Connecting the positive battery terminal to the pyro
266 charges must be done separate from TeleMetrum, by soldering
267 them together or using some other connector.</p><p>The other lead from each pyro charge is then inserted into
268 the appropriate per-pyro channel screw terminal (terminal 4 for the
269 Main charge, terminal 6 for the Apogee charge).</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_an_active_switch_with_telemetrum"></a>4.3. Using an Active Switch with TeleMetrum</h2></div></div></div><p>As explained above, an external active switch requires three
270 connections, one to the positive battery terminal, one to
271 the flight computer positive input and one to ground.</p><p>The positive battery terminal is available on screw terminal
272 2, the positive flight computer input is on terminal 1. To
273 hook a lead to ground, solder a piece of wire, 24 to 28
274 gauge stranded, to the GND hole just above terminal 1.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_telemini_v1_0"></a>Chapter 5. TeleMini v1.0</h1></div></div></div><div class="figure"><a id="idm515"></a><p class="title"><strong>Figure 5.1. TeleMini v1.0 Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telemini-v1-top.jpg" width="495" alt="telemini-v1-top.jpg" /></div></div></div><br class="figure-break" /><p>TeleMini v1.0 is ½ inches by 1½ inches. It was
275 designed to fit inside an 18mm air-frame tube, but using it in
276 a tube that small in diameter may require some creativity in
277 mounting and wiring to succeed! Since there is no
278 accelerometer, TeleMini can be mounted in any convenient
279 orientation. The default ¼ wave UHF wire antenna attached to
280 the center of one end of the board is about 7 inches long. Two
281 wires for the power switch are connected to holes in the
282 middle of the board. Screw terminals for the e-matches for
283 apogee and main ejection charges depart from the other end of
284 the board, meaning an ideal “simple” avionics bay for TeleMini
285 should have at least 9 inches of interior length.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_telemini_v1_0_screw_terminals"></a>5.1. TeleMini v1.0 Screw Terminals</h2></div></div></div><p>TeleMini v1.0 has four screw terminals on the end of the
286 board opposite the telemetry antenna. Two are for the apogee
287 and two are for main igniter circuits. There are also wires
288 soldered to the board for the power switch. Using the
289 picture above and starting from the top for the terminals
290 and from the left for the power switch wires, the
291 connections are as follows:</p><div class="table"><a id="idm526"></a><p class="title"><strong>Table 5.1. TeleMini v1.0 Screw Terminals</strong></p><div class="table-contents"><table class="table" summary="TeleMini v1.0 Screw Terminals" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal #</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal Name</th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Left</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Output</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to flight computer</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Right</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Switch Input</p></td><td style="" align="left" valign="top"><p>Switch connection to positive battery terminal</p></td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_a_separate_pyro_battery_with_telemini_v1_0"></a>5.2. Using a Separate Pyro Battery with TeleMini v1.0</h2></div></div></div><p>As described above, using an external pyro battery involves
292 connecting the negative battery terminal to the flight
293 computer ground, connecting the positive battery terminal to
294 one of the igniter leads and connecting the other igniter
295 lead to the per-channel pyro circuit connection. Because
296 there is no solid ground connection to use on TeleMini, this
297 is not recommended.</p><p>The only available ground connection on TeleMini v1.0 are
298 the two mounting holes next to the telemetry
299 antenna. Somehow connect a small piece of wire to one of
300 those holes and hook it to the negative pyro battery terminal.</p><p>Connecting the positive battery terminal to the pyro
301 charges must be done separate from TeleMini v1.0, by soldering
302 them together or using some other connector.</p><p>The other lead from each pyro charge is then inserted into
303 the appropriate per-pyro channel screw terminal (terminal 3 for the
304 Main charge, terminal 1 for the Apogee charge).</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_an_active_switch_with_telemini_v1_0"></a>5.3. Using an Active Switch with TeleMini v1.0</h2></div></div></div><p>As explained above, an external active switch requires three
305 connections, one to the positive battery terminal, one to
306 the flight computer positive input and one to ground. Again,
307 because TeleMini doesn’t have any good ground connection,
308 this is not recommended.</p><p>The positive battery terminal is available on the Right
309 power switch wire, the positive flight computer input is on
310 the left power switch wire. Hook a lead to either of the
311 mounting holes for a ground connection.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_easymini"></a>Chapter 6. EasyMini</h1></div></div></div><div class="figure"><a id="idm592"></a><p class="title"><strong>Figure 6.1. EasyMini Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="easymini-top.jpg" width="495" alt="easymini-top.jpg" /></div></div></div><br class="figure-break" /><p>EasyMini is built on a 0.8 inch by 1½ inch circuit board. It’s
312 designed to fit in a 24mm coupler tube.</p><p>You usually don’t need to configure EasyMini at all; it’s set
313 up to do dual-deployment with an event at apogee to separate
314 the airframe and deploy a drogue and another event at 250m
315 (820ft) to deploy the main. Install EasyMini in your airframe,
316 hook up a battery, igniters and a power switch and you’re
317 ready to fly.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_easymini_screw_terminals"></a>6.1. EasyMini Screw Terminals</h2></div></div></div><p>EasyMini has two sets of four screw terminals near one end of the
318 board. Using the picture
319 above, the top four have connections for the main pyro
320 circuit and an external battery and the bottom four have
321 connections for the apogee pyro circuit and the power
322 switch. Counting from the left, the connections are as follows:</p><div class="table"><a id="idm604"></a><p class="title"><strong>Table 6.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>6.2. Connecting A Battery To EasyMini</h2></div></div></div><p>There are two possible battery connections on
323 EasyMini. You can use either method; both feed
324 through the power switch terminals.</p><p>One battery connection is the standard Altus Metrum
325 white JST plug. This mates with single-cell Lithium
326 Polymer batteries sold by Altus Metrum.</p><p>The other is a pair of screw terminals marked <span class="emphasis"><em>Battery
327 +</em></span> and <span class="emphasis"><em>Battery -</em></span>. Connect a battery from 4 to 12
328 volts to these terminals, being careful to match polarity.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_charging_lithium_batteries"></a>6.3. Charging Lithium Batteries</h2></div></div></div><p>Because EasyMini allows for batteries other than the
329 standard Altus Metrum Lithium Polymer cells, it cannot
330 incorporate a battery charger circuit. Therefore, when
331 using a Litium Polymer cell, you’ll need an external
332 charger. These are available from Altus Metrum, or
333 from Spark Fun.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_a_separate_pyro_battery_with_easymini"></a>6.4. Using a Separate Pyro Battery with EasyMini</h2></div></div></div><p>As described above, using an external pyro battery involves
334 connecting the negative battery terminal to the flight
335 computer ground, connecting the positive battery terminal to
336 one of the igniter leads and connecting the other igniter
337 lead to the per-channel pyro circuit connection.</p><p>To connect the negative pyro battery terminal to EasyMini
338 ground, connect it to the negative external battery
339 connection, top terminal 4.</p><p>Connecting the positive battery terminal to the pyro
340 charges must be done separate from EasyMini, by soldering
341 them together or using some other connector.</p><p>The other lead from each pyro charge is then inserted into
342 the appropriate per-pyro channel screw terminal (top
343 terminal 1 for the Main charge, bottom terminal 1 for the
344 Apogee charge).</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_an_active_switch_with_easymini"></a>6.5. Using an Active Switch with EasyMini</h2></div></div></div><p>As explained above, an external active switch requires three
345 connections, one to the positive battery terminal, one to
346 the flight computer positive input and one to ground. Use
347 the negative external battery connection, top terminal 4 for
348 ground.</p><p>The positive battery terminal is available on bottom
349 terminal 4, the positive flight computer input is on the
350 bottom terminal 3.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_telemega"></a>Chapter 7. TeleMega</h1></div></div></div><div class="figure"><a id="idm694"></a><p class="title"><strong>Figure 7.1. TeleMega Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telemega-v1.0-top.jpg" width="495" alt="telemega-v1.0-top.jpg" /></div></div></div><br class="figure-break" /><p>TeleMega is a 1¼ inch by 3¼ inch circuit board. It was
351 designed to easily fit in a 38mm coupler. Like TeleMetrum,
352 TeleMega has an accelerometer and so it must be mounted so that
353 the board is aligned with the flight axis. It can be mounted
354 either antenna up or down.</p><p>TeleMega v2.0 has a few minor changes from v1.0:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
355 Companion connector matches EasyMega functions
356 </li><li class="listitem">
357 Serial port connector replaced with servo connector with
358 support for up to 4 PWM channels.
359 </li><li class="listitem">
360 Radio switched from cc1120 to cc1200.
361 </li></ul></div><p>None of these affect operation using the stock firmware, but
362 they do mean that the device needs different firmware to
363 operate correctly, so make sure you load the right firmware
364 when reflashing the device.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_telemega_screw_terminals"></a>7.1. TeleMega Screw Terminals</h2></div></div></div><p>TeleMega has two sets of nine screw terminals on the end of
365 the board opposite the telemetry antenna. They are as follows:</p><div class="table"><a id="idm714"></a><p class="title"><strong>Table 7.1. TeleMega Screw Terminals</strong></p><div class="table-contents"><table class="table" summary="TeleMega Screw Terminals" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal #</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal Name</th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Input</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to positive battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Output</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to flight computer</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>GND</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Ground connection for use with external active switch</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 5</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 6</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 7</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 8</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 9</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>GND</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Ground connection for negative pyro battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Pyro</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Positive pyro battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Lipo</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Power switch output. Use to connect main battery to pyro battery input</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 5</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 6</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 7</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 8</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>C -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>C pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Bottom 9</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>C</p></td><td style="" align="left" valign="top"><p>C pyro channel common connection to battery</p></td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_a_separate_pyro_battery_with_telemega"></a>7.2. Using a Separate Pyro Battery with TeleMega</h2></div></div></div><p>TeleMega provides explicit support for an external pyro
366 battery. All that is required is to remove the jumper
367 between the lipo terminal (Bottom 3) and the pyro terminal
368 (Bottom 2). Then hook the negative pyro battery terminal to ground
369 (Bottom 1) and the positive pyro battery to the pyro battery
370 input (Bottom 2). You can then use the existing pyro screw
371 terminals to hook up all of the pyro charges.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_only_one_battery_with_telemega"></a>7.3. Using Only One Battery With TeleMega</h2></div></div></div><p>Because TeleMega has built-in support for a separate pyro
372 battery, if you want to fly with just one battery running
373 both the computer and firing the charges, you need to
374 connect the flight computer battery to the pyro
375 circuit. TeleMega has two screw terminals for this—hook a
376 wire from the Lipo terminal (Bottom 3) to the Pyro terminal
377 (Bottom 2).</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_an_active_switch_with_telemega"></a>7.4. Using an Active Switch with TeleMega</h2></div></div></div><p>As explained above, an external active switch requires three
378 connections, one to the positive battery terminal, one to
379 the flight computer positive input and one to ground.</p><p>The positive battery terminal is available on Top terminal
380 1, the positive flight computer input is on Top terminal
381 2. Ground is on Top terminal 3.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_easymega"></a>Chapter 8. EasyMega</h1></div></div></div><div class="figure"><a id="idm864"></a><p class="title"><strong>Figure 8.1. EasyMega Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="easymega-v1.0-top.jpg" width="405" alt="easymega-v1.0-top.jpg" /></div></div></div><br class="figure-break" /><p>EasyMega is a 1¼ inch by 2¼ inch circuit board. It was
382 designed to easily fit in a 38mm coupler. Like TeleMetrum,
383 EasyMega has an accelerometer and so it must be mounted so that
384 the board is aligned with the flight axis. It can be mounted
385 either antenna up or down.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_easymega_screw_terminals"></a>8.1. EasyMega Screw Terminals</h2></div></div></div><p>EasyMega has two sets of nine screw terminals on the end of
386 the board opposite the telemetry antenna. They are as follows:</p><div class="table"><a id="idm875"></a><p class="title"><strong>Table 8.1. EasyMega Screw Terminals</strong></p><div class="table-contents"><table class="table" summary="EasyMega Screw Terminals" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal #</th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Terminal Name</th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Input</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to positive battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch Output</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Switch connection to flight computer</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>GND</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Ground connection for use with external active switch</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 5</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 6</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 7</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 8</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Top 9</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>D pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>GND</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Ground connection for negative pyro battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Pyro</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Positive pyro battery terminal</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Lipo</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Power switch output. Use to connect main battery to pyro battery input</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 5</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 6</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 7</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B pyro channel common connection to battery</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Bottom 8</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>C -</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>C pyro channel connection to pyro circuit</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Bottom 9</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>C</p></td><td style="" align="left" valign="top"><p>C pyro channel common connection to battery</p></td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_a_separate_pyro_battery_with_easymega"></a>8.2. Using a Separate Pyro Battery with EasyMega</h2></div></div></div><p>EasyMega provides explicit support for an external pyro
387 battery. All that is required is to remove the jumper
388 between the lipo terminal (Bottom 3) and the pyro terminal
389 (Bottom 2). Then hook the negative pyro battery terminal to ground
390 (Bottom 1) and the positive pyro battery to the pyro battery
391 input (Bottom 2). You can then use the existing pyro screw
392 terminals to hook up all of the pyro charges.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_only_one_battery_with_easymega"></a>8.3. Using Only One Battery With EasyMega</h2></div></div></div><p>Because EasyMega has built-in support for a separate pyro
393 battery, if you want to fly with just one battery running
394 both the computer and firing the charges, you need to
395 connect the flight computer battery to the pyro
396 circuit. EasyMega has two screw terminals for this—hook a
397 wire from the Lipo terminal (Bottom 3) to the Pyro terminal
398 (Bottom 2).</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_using_an_active_switch_with_easymega"></a>8.4. Using an Active Switch with EasyMega</h2></div></div></div><p>As explained above, an external active switch requires three
399 connections, one to the positive battery terminal, one to
400 the flight computer positive input and one to ground.</p><p>The positive battery terminal is available on Top terminal
401 1, the positive flight computer input is on Top terminal
402 2. Ground is on Top terminal 3.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_installation"></a>Chapter 9. Installation</h1></div></div></div><p>A typical installation involves attaching
403 only a suitable battery, a single pole switch for
404 power on/off, and two pairs of wires connecting e-matches for the
405 apogee and main ejection charges. All Altus Metrum products are
406 designed for use with single-cell batteries with 3.7 volts
409 EasyMini may also be used with other
410 batteries as long as they supply between 4 and 12 volts.</p><p>The battery connectors are a standard 2-pin JST connector; you
411 can purchase suitable batteries from the any vendor selling
412 Altus Metrum products. These batteries are
413 single-cell Lithium Polymer batteries that nominally provide 3.7
414 volts. Other vendors sell similar batteries for RC aircraft
415 using mating connectors, however the polarity for those is
416 generally reversed from the batteries used by Altus Metrum
417 products. In particular, the Tenergy batteries supplied for use
418 in Featherweight flight computers are not compatible with Altus
419 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
420 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
421 the correct polarity. However, these batteries include an
422 integrated current limiting circuit. That circuit will cause
423 the battery to shut down when firing the igniter circuit. Do
424 not use these batteries unless you remove the current limiting
425 circuit.</p></div><p>By default, we use the unregulated output of the battery
426 directly to fire ejection charges. This works marvelously
427 with standard low-current e-matches like the J-Tek from MJG
428 Technologies, and with Quest Q2G2 igniters. However, if you
429 want or need to use a separate pyro battery, check out
430 <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
431 that up. The altimeters are designed to work with an external
432 pyro battery of no more than 15 volts.</p><p>Ejection charges are wired directly to the screw terminal block
433 at the aft end of the altimeter. You’ll need a very small straight
434 blade screwdriver for these screws, such as you might find in a
435 jeweler’s screwdriver set.</p><p>Except for TeleMini v1.0, the flight computers also use the
436 screw terminal block for the power switch leads. On TeleMini v1.0,
437 the power switch leads are soldered directly to the board and
438 can be connected directly to a switch.</p><p>For most air-frames, the integrated antennas are more than
439 adequate. However, if you are installing in a carbon-fiber or
440 metal electronics bay which is opaque to RF signals, you may need to
441 use off-board external antennas instead. In this case, you can
442 replace the stock UHF antenna wire with an edge-launched SMA connector,
443 and, on TeleMetrum v1, you can unplug the integrated GPS
444 antenna and select an appropriate off-board GPS antenna with
445 cable terminating in a U.FL connector.</p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_using_altus_metrum_products"></a>Chapter 10. Using Altus Metrum Products</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_being_legal"></a>10.1. Being Legal</h2></div></div></div><p>In the US, you need an
446 <a class="ulink" href="http://www.altusmetrum.org/Radio/" target="_top">amateur radio license</a>
447 or other authorization to legally operate the radio
448 transmitters that are part of our products.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_in_the_rocket"></a>10.2. In the Rocket</h2></div></div></div><p>In the rocket itself, you just need a flight computer
449 and a single-cell, 3.7 volt nominal Li-Po rechargeable
451 An 850mAh battery weighs less than a 9V
452 alkaline battery, and will run a TeleMetrum, TeleMega
453 or EasyMega for hours.
454 A 110mAh battery weighs less
455 than a triple A battery and is a good choice for use
458 EasyMini.</p><p>By default, we ship TeleMini, TeleMetrum and TeleMega
459 flight computers with a simple wire antenna. If your
460 electronics bay or the air-frame it resides within is
461 made of carbon fiber, which is opaque to RF signals,
462 you may prefer to install an SMA connector so that you
463 can run a coaxial cable to an antenna mounted
464 elsewhere in the rocket. However, note that the GPS
465 antenna is fixed on all current products, so you
466 really want to install the flight computer in a bay
467 made of RF-transparent materials if at all possible.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_on_the_ground"></a>10.3. On the Ground</h2></div></div></div><p>To receive the data stream from the rocket, you need
468 an antenna and short feed-line connected to one of our
469 <a class="ulink" href="http://www.altusmetrum.org/TeleDongle/" target="_top">TeleDongle</a>
470 units. If possible, use an SMA to BNC adapter instead
471 of feedline between the antenna feedpoint and
472 TeleDongle, as this will give you the best
473 performance. The TeleDongle in turn plugs directly
474 into the USB port on a notebook computer. Because
475 TeleDongle looks like a simple serial port, your
476 computer does not require special device
477 drivers… just plug it in.</p><p>The GUI tool, AltosUI, is written in Java and runs
478 across Linux, Mac OS and Windows. There’s also a suite
479 of C tools for Linux which can perform most of the
480 same tasks.</p><p>Alternatively, a TeleBT attached with an SMA to BNC
481 adapter at the feed point of a hand-held yagi used in
482 conjunction with an Android device running AltosDroid
483 makes an outstanding ground station.</p><p>After the flight,
484 you can use the radio link to
485 extract the more detailed data logged in either
486 TeleMetrum or TeleMini devices, or
488 USB cable to plug into the flight computer board directly.
489 A USB cable is also how you
490 charge the Li-Po battery, so you’ll want one of those
491 anyway. The same cable used by lots of digital
492 cameras and other modern electronic stuff will work
493 fine.</p><p>If your rocket lands out of sight, you may enjoy
494 having a hand-held GPS receiver, so that you can put
495 in a way-point for the last reported rocket position
496 before touch-down. This makes looking for your rocket
497 a lot like Geo-Caching… just go to the way-point and
498 look around starting from there. AltosDroid on an
499 Android device with GPS receiver works great for this,
500 too!</p><p>You may also enjoy having a ham radio “HT” that covers
501 the 70cm band… you can use that with your antenna to
502 direction-find the rocket on the ground the same way
503 you can use a Walston or Beeline tracker. This can be
504 handy if the rocket is hiding in sage brush or a tree,
505 or if the last GPS position doesn’t get you close
506 enough because the rocket dropped into a canyon, or
507 the wind is blowing it across a dry lake bed, or
508 something like that… Keith currently uses a Yaesu
509 FT1D, Bdale has a Yaesu VX-7R, which is a nicer radio
510 in most ways but doesn’t support APRS.</p><p>So, to recap, on the ground the hardware you’ll need includes:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
511 an antenna and feed-line or adapter
512 </li><li class="listitem">
514 </li><li class="listitem">
516 </li><li class="listitem">
517 optionally, a hand-held GPS receiver
518 </li><li class="listitem">
519 optionally, an HT or receiver covering 435 MHz
520 </li></ol></div><p>The best hand-held commercial directional antennas we’ve found for radio
521 direction finding rockets are from
522 <a class="ulink" href="http://www.arrowantennas.com/" target="_top">Arrow Antennas</a>.</p><p>The 440-3 and 440-5 are both good choices for finding
523 a TeleMetrum- or TeleMini- equipped rocket when used
524 with a suitable 70cm HT. TeleDongle and an SMA to BNC
525 adapter fit perfectly between the driven element and
526 reflector of Arrow antennas.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_data_analysis"></a>10.4. Data Analysis</h2></div></div></div><p>Our software makes it easy to log the data from each
527 flight, both the telemetry received during the flight
528 itself, and the more complete data log recorded in the
529 flash memory on the altimeter board. Once this data
530 is on your computer, our post-flight tools make it
531 easy to quickly get to the numbers everyone wants,
532 like apogee altitude, max acceleration, and max
533 velocity. You can also generate and view a standard
534 set of plots showing the altitude, acceleration, and
535 velocity of the rocket during flight. And you can
536 even export a flight log in a format usable with Google
537 Maps and Google Earth for visualizing the flight path
538 in two or three dimensions!</p><p>Our ultimate goal is to emit a set of files for each
539 flight that can be published as a web page per flight,
540 or just viewed on your local disk with a web browser.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_future_plans"></a>10.5. Future Plans</h2></div></div></div><p>We have designed and prototyped several “companion
541 boards” that can attach to the companion connector on
542 TeleMetrum, TeleMega and EasyMega flight computers to
543 collect more data, provide more pyro channels, and so
544 forth. We do not yet know if or when any of these
545 boards will be produced in enough quantity to sell.
546 If you have specific interests for data collection or
547 control of events in your rockets beyond the
548 capabilities of our existing productions, please let
549 us know!</p><p>Because all of our work is open, both the hardware
550 designs and the software, if you have some great idea
551 for an addition to the current Altus Metrum family,
552 feel free to dive in and help! Or let us know what
553 you’d like to see that we aren’t already working on,
554 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
555 more news and information as our family of products
556 evolves!</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_altosui"></a>Chapter 11. AltosUI</h1></div></div></div><div class="figure"><a id="idm1082"></a><p class="title"><strong>Figure 11.1. AltosUI Main Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="altosui.png" width="414" alt="altosui.png" /></div></div></div><br class="figure-break" /><p>The AltosUI program provides a graphical user interface for
557 interacting with the Altus Metrum product family. AltosUI can
558 monitor telemetry data, configure devices and many other
559 tasks. The primary interface window provides a selection of
560 buttons, one for each major activity in the system. This
561 chapter is split into sections, each of which documents one of
562 the tasks provided from the top-level toolbar.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_monitor_flight"></a>11.1. Monitor Flight</h2></div></div></div><p>Selecting this item brings up a dialog box listing all
563 of the connected TeleDongle devices. When you choose
564 one of these, AltosUI will create a window to display
565 telemetry data as received by the selected TeleDongle
566 device.</p><div class="figure"><a id="idm1093"></a><p class="title"><strong>Figure 11.2. Device Selection Dialog</strong></p><div class="figure-contents"><div class="mediaobject"><img src="device-selection.png" width="279" alt="device-selection.png" /></div></div></div><br class="figure-break" /><p>All telemetry data received are automatically recorded
567 in suitable log files. The name of the files includes
568 the current date and rocket serial and flight numbers.</p><p>The radio frequency being monitored by the TeleDongle
569 device is displayed at the top of the window. You can
570 configure the frequency by clicking on the frequency
571 box and selecting the desired frequency. AltosUI
572 remembers the last frequency selected for each
573 TeleDongle and selects that automatically the next
574 time you use that device.</p><p>Below the TeleDongle frequency selector, the window
575 contains a few significant pieces of information about
576 the altimeter providing the telemetry data stream:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
577 The configured call-sign
578 </li><li class="listitem">
579 The device serial number
580 </li><li class="listitem">
581 The flight number. Each altimeter remembers how
582 many times it has flown.
583 </li><li class="listitem">
584 The rocket flight state. Each flight passes through
585 several states including Pad, Boost, Fast, Coast,
586 Drogue, Main and Landed.
587 </li><li class="listitem">
588 The Received Signal Strength Indicator value. This
589 lets you know how strong a signal TeleDongle is
590 receiving. At the default data rate, 38400 bps, in
591 bench testing, the radio inside TeleDongle v0.2
592 operates down to about -106dBm, while the v3 radio
593 works down to about -111dBm. Weaker signals, or an
594 environment with radio noise may cause the data to
595 not be received. The packet link uses error
596 detection and correction techniques which prevent
597 incorrect data from being reported.
598 </li><li class="listitem">
599 The age of the displayed data, in seconds since the
600 last successfully received telemetry packet. In
601 normal operation this will stay in the low single
602 digits. If the number starts counting up, then you
603 are no longer receiving data over the radio link
604 from the flight computer.
605 </li></ul></div><p>Finally, the largest portion of the window contains a
606 set of tabs, each of which contain some information
607 about the rocket. They’re arranged in <span class="emphasis"><em>flight order</em></span>
608 so that as the flight progresses, the selected tab
609 automatically switches to display data relevant to the
610 current state of the flight. You can select other tabs
611 at any time. The final <span class="emphasis"><em>table</em></span> tab displays all of the
612 raw telemetry values in one place in a
613 spreadsheet-like format.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_launch_pad"></a>11.1.1. Launch Pad</h3></div></div></div><div class="figure"><a id="idm1121"></a><p class="title"><strong>Figure 11.3. Monitor Flight Launch Pad View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="launch-pad.png" width="495" alt="launch-pad.png" /></div></div></div><br class="figure-break" /><p>The <span class="emphasis"><em>Launch Pad</em></span> tab shows information used to decide when the
614 rocket is ready for flight. The first elements include red/green
615 indicators, if any of these is red, you’ll want to evaluate
616 whether the rocket is ready to launch:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
619 This indicates whether the Li-Po battery powering the
620 flight computer has sufficient charge to last for
621 the duration of the flight. A value of more than
622 3.8V is required for a <span class="emphasis"><em>GO</em></span> status.
623 </dd><dt><span class="term">
624 Apogee Igniter Voltage
626 This indicates whether the apogee
627 igniter has continuity. If the igniter has a low
628 resistance, then the voltage measured here will be close
629 to the Li-Po battery voltage. A value greater than 3.2V is
630 required for a <span class="emphasis"><em>GO</em></span> status.
631 </dd><dt><span class="term">
634 This indicates whether the main
635 igniter has continuity. If the igniter has a low
636 resistance, then the voltage measured here will be close
637 to the Li-Po battery voltage. A value greater than 3.2V is
638 required for a <span class="emphasis"><em>GO</em></span> status.
639 </dd><dt><span class="term">
640 On-board Data Logging
642 This indicates whether there is space remaining
643 on-board to store flight data for the upcoming
644 flight. If you’ve downloaded data, but failed to erase
645 flights, there may not be any space left. Most of our
646 flight computers can store multiple flights, depending
647 on the configured maximum flight log size. TeleMini
648 v1.0 stores only a single flight, so it will need to
649 be downloaded and erased after each flight to capture
650 data. This only affects on-board flight logging; the
651 altimeter will still transmit telemetry and fire
652 ejection charges at the proper times even if the
653 flight data storage is full.
654 </dd><dt><span class="term">
657 For a TeleMetrum or TeleMega device, this indicates
658 whether the GPS receiver is currently able to compute
659 position information. GPS requires at least 4
660 satellites to compute an accurate position.
661 </dd><dt><span class="term">
664 For a TeleMetrum or TeleMega device, this indicates
665 whether GPS has reported at least 10 consecutive
666 positions without losing lock. This ensures that the
667 GPS receiver has reliable reception from the
669 </dd></dl></div><p>The Launchpad tab also shows the computed launch pad
670 position and altitude, averaging many reported
671 positions to improve the accuracy of the fix.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_ascent"></a>11.1.2. Ascent</h3></div></div></div><div class="figure"><a id="idm1161"></a><p class="title"><strong>Figure 11.4. Monitor Flight Ascent View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="ascent.png" width="495" alt="ascent.png" /></div></div></div><br class="figure-break" /><p>This tab is shown during Boost, Fast and Coast
672 phases. The information displayed here helps monitor the
673 rocket as it heads towards apogee.</p><p>The height, speed, acceleration and tilt are shown along
674 with the maximum values for each of them. This allows you to
675 quickly answer the most commonly asked questions you’ll hear
676 during flight.</p><p>The current latitude and longitude reported by the GPS are
677 also shown. Note that under high acceleration, these values
678 may not get updated as the GPS receiver loses position
679 fix. Once the rocket starts coasting, the receiver should
680 start reporting position again.</p><p>Finally, the current igniter voltages are reported as in the
681 Launch Pad tab. This can help diagnose deployment failures
682 caused by wiring which comes loose under high acceleration.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_descent"></a>11.1.3. Descent</h3></div></div></div><div class="figure"><a id="idm1174"></a><p class="title"><strong>Figure 11.5. Monitor Flight Descent View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="descent.png" width="495" alt="descent.png" /></div></div></div><br class="figure-break" /><p>Once the rocket has reached apogee and (we hope)
683 activated the apogee charge, attention switches to
684 tracking the rocket on the way back to the ground, and
685 for dual-deploy flights, waiting for the main charge
686 to fire.</p><p>To monitor whether the apogee charge operated
687 correctly, the current descent rate is reported along
688 with the current height. Good descent rates vary based
689 on the choice of recovery components, but generally
690 range from 15-30m/s on drogue and should be below
691 10m/s when under the main parachute in a dual-deploy
692 flight.</p><p>With GPS-equipped flight computers, you can locate the
693 rocket in the sky using the elevation and bearing
694 information to figure out where to look. Elevation is
695 in degrees above the horizon. Bearing is reported in
696 degrees relative to true north. Range can help figure
697 out how big the rocket will appear. Ground Distance
698 shows how far it is to a point directly under the
699 rocket and can help figure out where the rocket is
700 likely to land. Note that all of these values are
701 relative to the pad location. If the elevation is near
702 90°, the rocket is over the pad, not over you.</p><p>Finally, the igniter voltages are reported in this tab
703 as well, both to monitor the main charge as well as to
704 see what the status of the apogee charge is. Note
705 that some commercial e-matches are designed to retain
706 continuity even after being fired, and will continue
707 to show as green or return from red to green after
708 firing.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_landed"></a>11.1.4. Landed</h3></div></div></div><div class="figure"><a id="idm1187"></a><p class="title"><strong>Figure 11.6. Monitor Flight Landed View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="landed.png" width="495" alt="landed.png" /></div></div></div><br class="figure-break" /><p>Once the rocket is on the ground, attention switches
709 to recovery. While the radio signal is often lost once
710 the rocket is on the ground, the last reported GPS
711 position is generally within a short distance of the
712 actual landing location.</p><p>The last reported GPS position is reported both by
713 latitude and longitude as well as a bearing and
714 distance from the launch pad. The distance should give
715 you a good idea of whether to walk or hitch a ride.
716 Take the reported latitude and longitude and enter
717 them into your hand-held GPS unit and have that
718 compute a track to the landing location.</p><p>Our flight computers will continue to transmit RDF
719 tones after landing, allowing you to locate the rocket
720 by following the radio signal if necessary. You may
721 need to get away from the clutter of the flight line,
722 or even get up on a hill (or your neighbor’s RV roof)
723 to receive the RDF signal.</p><p>The maximum height, speed and acceleration reported
724 during the flight are displayed for your admiring
725 observers. The accuracy of these immediate values
726 depends on the quality of your radio link and how many
727 packets were received. Recovering the on-board data
728 after flight may yield more precise results.</p><p>To get more detailed information about the flight, you
729 can click on the <span class="emphasis"><em>Graph Flight</em></span> button which will
730 bring up a graph window for the current flight.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_table"></a>11.1.5. Table</h3></div></div></div><div class="figure"><a id="idm1202"></a><p class="title"><strong>Figure 11.7. Monitor Flight Table View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="table.png" width="495" alt="table.png" /></div></div></div><br class="figure-break" /><p>The table view shows all of the data available from the
731 flight computer. Probably the most useful data on
732 this tab is the detailed GPS information, which includes
733 horizontal dilution of precision information, and
734 information about the signal being received from the satellites.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_site_map"></a>11.1.6. Site Map</h3></div></div></div><div class="figure"><a id="idm1212"></a><p class="title"><strong>Figure 11.8. Monitor Flight Site Map View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="site-map.png" width="495" alt="site-map.png" /></div></div></div><br class="figure-break" /><p>When the TeleMetrum has a GPS fix, the Site Map tab
735 will map the rocket’s position to make it easier for
736 you to locate the rocket, both while it is in the air,
737 and when it has landed. The rocket’s state is
738 indicated by color: white for pad, red for boost, pink
739 for fast, yellow for coast, light blue for drogue,
740 dark blue for main, and black for landed.</p><p>The map’s default scale is approximately 3m (10ft) per
741 pixel. The map can be dragged using the left mouse
742 button. The map will attempt to keep the rocket
743 roughly centered while data is being received.</p><p>You can adjust the style of map and the zoom level
744 with buttons on the right side of the map window. You
745 can draw a line on the map by moving the mouse over
746 the map with a button other than the left one pressed,
747 or by pressing the left button while also holding down
748 the shift key. The length of the line in real-world
749 units will be shown at the start of the line.</p><p>Images are fetched automatically via the Google Maps
750 Static API, and cached on disk for reuse. If map
751 images cannot be downloaded, the rocket’s path will be
752 traced on a dark gray background instead.</p><p>You can pre-load images for your favorite launch sites
753 before you leave home; check out <a class="xref" href="#_load_maps" title="11.12. Load Maps">Section 11.12, “Load Maps”</a>.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_igniter"></a>11.1.7. Igniter</h3></div></div></div><div class="figure"><a id="idm1227"></a><p class="title"><strong>Figure 11.9. Monitor Flight Additional Igniter View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="ignitor.png" width="495" alt="ignitor.png" /></div></div></div><br class="figure-break" /><p>TeleMega includes four additional programmable pyro
754 channels. The Ignitor tab shows whether each of them has
755 continuity. If an ignitor has a low resistance, then the
756 voltage measured here will be close to the pyro battery
757 voltage. A value greater than 3.2V is required for a <span class="emphasis"><em>GO</em></span>
758 status.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_save_flight_data"></a>11.2. Save Flight Data</h2></div></div></div><p>The altimeter records flight data to its internal
760 Data logged on board is recorded at a much
761 higher rate than the telemetry system can handle, and
762 is not subject to radio drop-outs. As such, it
763 provides a more complete and precise record of the
765 The <span class="emphasis"><em>Save Flight Data</em></span> button allows you to
766 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
767 list of connected flight computers and TeleDongle
768 devices. If you select a flight computer, the flight
769 data will be downloaded from that device directly.
770 If you select a TeleDongle device, flight data will be
771 downloaded from a flight computer over radio link via
772 the specified TeleDongle. See
773 <a class="xref" href="#_controlling_an_altimeter_over_the_radio_link" title="A.3. Controlling An Altimeter Over The Radio Link">Section A.3, “Controlling An Altimeter Over The Radio Link”</a> for
774 more information.</p><p>After the device has been selected, a dialog showing
775 the flight data saved in the device will be shown
776 allowing you to select which flights to download and
777 which to delete. With version 0.9 or newer firmware,
778 you must erase flights in order for the space they
779 consume to be reused by another flight. This prevents
780 accidentally losing flight data if you neglect to
781 download data before flying again. Note that if there
782 is no more space available in the device, then no data
783 will be recorded during the next flight.</p><p>The file name for each flight log is computed
784 automatically from the recorded flight date, altimeter
785 serial number and flight number information.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_replay_flight"></a>11.3. Replay Flight</h2></div></div></div><p>Select this button and you are prompted to select a flight
786 record file, either a .telem file recording telemetry data or a
787 .eeprom file containing flight data saved from the altimeter
788 flash memory.</p><p>Once a flight record is selected, the flight monitor interface
789 is displayed and the flight is re-enacted in real
792 <a class="xref" href="#_monitor_flight" title="11.1. Monitor Flight">Section 11.1, “Monitor Flight”</a> to learn how this window operates.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_graph_data"></a>11.4. Graph Data</h2></div></div></div><p>Select this button and you are prompted to select a flight
793 record file, either a .telem file recording telemetry data or a
794 .eeprom file containing flight data saved from
795 flash memory.</p><p>Note that telemetry files will generally produce poor graphs
796 due to the lower sampling rate and missed telemetry packets.
797 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
798 opened.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_flight_graph"></a>11.4.1. Flight Graph</h3></div></div></div><div class="figure"><a id="idm1257"></a><p class="title"><strong>Figure 11.10. Flight Data Graph</strong></p><div class="figure-contents"><div class="mediaobject"><img src="graph.png" width="495" alt="graph.png" /></div></div></div><br class="figure-break" /><p>By default, the graph contains acceleration (blue),
799 velocity (green) and altitude (red).</p><p>The graph can be zoomed into a particular area by
800 clicking and dragging down and to the right. Once
801 zoomed, the graph can be reset by clicking and
802 dragging up and to the left. Holding down control and
803 clicking and dragging allows the graph to be panned.
804 The right mouse button causes a pop-up menu to be
805 displayed, giving you the option save or print the
806 plot.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_configure_graph"></a>11.4.2. Configure Graph</h3></div></div></div><div class="figure"><a id="idm1268"></a><p class="title"><strong>Figure 11.11. Flight Graph Configuration</strong></p><div class="figure-contents"><div class="mediaobject"><img src="graph-configure.png" width="495" alt="graph-configure.png" /></div></div></div><br class="figure-break" /><p>This selects which graph elements to show, and, at the
807 very bottom, lets you switch between metric and
808 imperial units</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_flight_statistics"></a>11.4.3. Flight Statistics</h3></div></div></div><div class="figure"><a id="idm1278"></a><p class="title"><strong>Figure 11.12. Flight Statistics</strong></p><div class="figure-contents"><div class="mediaobject"><img src="graph-stats.png" width="495" alt="graph-stats.png" /></div></div></div><br class="figure-break" /><p>Shows overall data computed from the flight.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_map"></a>11.4.4. Map</h3></div></div></div><div class="figure"><a id="idm1288"></a><p class="title"><strong>Figure 11.13. Flight Map</strong></p><div class="figure-contents"><div class="mediaobject"><img src="graph-map.png" width="495" alt="graph-map.png" /></div></div></div><br class="figure-break" /><p>Shows a satellite image of the flight area overlaid
809 with the path of the flight. The red concentric
810 circles mark the launch pad, the black concentric
811 circles mark the landing location.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_export_data"></a>11.5. Export Data</h2></div></div></div><p>This tool takes the raw data files and makes them
812 available for external analysis. When you select this
813 button, you are prompted to select a flight data file,
814 which can be either a .eeprom or .telem. The .eeprom
815 files contain higher resolution and more continuous
816 data, while .telem files contain receiver signal
817 strength information. Next, a second dialog appears
818 which is used to select where to write the resulting
820 It has a selector to choose between CSV and KML
821 file formats.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_comma_separated_value_format"></a>11.5.1. Comma Separated Value Format</h3></div></div></div><p>This is a text file containing the data in a form
822 suitable for import into a spreadsheet or other
823 external data analysis tool. The first few lines of
824 the file contain the version and configuration
825 information from the altimeter, then there is a single
826 header line which labels all of the fields. All of
827 these lines start with a <span class="emphasis"><em>#</em></span> character which many
828 tools can be configured to skip over.</p><p>The remaining lines of the file contain the data, with
829 each field separated by a comma and at least one
830 space. All of the sensor values are converted to
831 standard units, with the barometric data reported in
832 both pressure, altitude and height above pad units.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_keyhole_markup_language_for_google_earth"></a>11.5.2. Keyhole Markup Language (for Google Earth)</h3></div></div></div><p>This is the format used by Google Earth to provide an
833 overlay within that application. With this, you can
834 use Google Earth to see the whole flight path
835 in 3D.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_configure_altimeter"></a>11.6. Configure Altimeter</h2></div></div></div><div class="figure"><a id="idm1309"></a><p class="title"><strong>Figure 11.14. Altimeter Configuration</strong></p><div class="figure-contents"><div class="mediaobject"><img src="configure-altimeter.png" width="324" alt="configure-altimeter.png" /></div></div></div><br class="figure-break" /><p>Select this button and then select either an altimeter or
836 TeleDongle Device from the list provided. Selecting a TeleDongle
837 device will use the radio link to configure a remote
838 altimeter.</p><p>The first few lines of the dialog provide information about the
839 connected device, including the product name,
840 software version and hardware serial number. Below that are the
841 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">
844 This writes any changes to the configuration parameter
845 block in flash memory. If you don’t press this button,
846 any changes you make will be lost.
847 </dd><dt><span class="term">
850 This resets the dialog to the most recently saved
851 values, erasing any changes you have made.
852 </dd><dt><span class="term">
855 This reboots the device. Use this to switch from idle
856 to pad mode by rebooting once the rocket is oriented
857 for flight, or to confirm changes you think you saved
859 </dd><dt><span class="term">
862 This closes the dialog. Any unsaved changes will be
864 </dd></dl></div><p>The rest of the dialog contains the parameters to be configured.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_main_deploy_altitude"></a>11.6.1. Main Deploy Altitude</h3></div></div></div><p>This sets the altitude (above the recorded pad
865 altitude) at which the <span class="emphasis"><em>main</em></span> igniter will fire. The
866 drop-down menu shows some common values, but you can
867 edit the text directly and choose whatever you
868 like. If the apogee charge fires below this altitude,
869 then the main charge will fire two seconds after the
870 apogee charge fires.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_apogee_delay"></a>11.6.2. Apogee Delay</h3></div></div></div><p>When flying redundant electronics, it’s often
871 important to ensure that multiple apogee charges don’t
872 fire at precisely the same time, as that can over
873 pressurize the apogee deployment bay and cause a
874 structural failure of the air-frame. The Apogee Delay
875 parameter tells the flight computer to fire the apogee
876 charge a certain number of seconds after apogee has
877 been detected.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_apogee_lockout"></a>11.6.3. Apogee Lockout</h3></div></div></div><p>Apogee lockout is the number of seconds after boost
878 where the flight computer will not fire the apogee
879 charge, even if the rocket appears to be at
880 apogee. This is often called <span class="emphasis"><em>Mach Delay</em></span>, as it is
881 intended to prevent a flight computer from
882 unintentionally firing apogee charges due to the
883 pressure spike that occurrs across a mach
884 transition. Altus Metrum flight computers include a
885 Kalman filter which is not fooled by this sharp
886 pressure increase, and so this setting should be left
887 at the default value of zero to disable it.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_frequency"></a>11.6.4. Frequency</h3></div></div></div><p>This configures which of the frequencies to use for
888 both telemetry and packet command mode. Note that if
889 you set this value via packet command mode, the
890 TeleDongle frequency will also be automatically
891 reconfigured to match so that communication will
892 continue afterwards.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_rf_calibration"></a>11.6.5. RF Calibration</h3></div></div></div><p>The radios in every Altus Metrum device are calibrated
893 at the factory to ensure that they transmit and
894 receive on the specified frequency. If you need to
895 you can adjust the calibration by changing this value.
896 Do not do this without understanding what the value
897 means, read the appendix on calibration and/or the
898 source code for more information. To change a
899 TeleDongle’s calibration, you must reprogram the unit
900 completely.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_telemetry_rdf_aprs_enable"></a>11.6.6. Telemetry/RDF/APRS Enable</h3></div></div></div><p>Enables the radio for transmission during
901 flight. When disabled, the radio will not
902 transmit anything during flight at all.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_telemetry_baud_rate"></a>11.6.7. Telemetry baud rate</h3></div></div></div><p>This sets the modulation bit rate for data
903 transmission for both telemetry and packet
904 link mode. Lower bit rates will increase range
905 while reducing the amount of data that can be
906 sent and increasing battery consumption. All
907 telemetry is done using a rate 1/2 constraint
908 4 convolution code, so the actual data
909 transmission rate is 1/2 of the modulation bit
910 rate specified here.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_aprs_interval"></a>11.6.8. APRS Interval</h3></div></div></div><p>How often to transmit GPS information via APRS
911 (in seconds). When set to zero, APRS
912 transmission is disabled.
914 available on TeleMetrum v2 and TeleMega
915 boards. TeleMetrum v1 boards cannot transmit
917 Note that a single APRS packet
918 takes nearly a full second to transmit, so
919 enabling this option will prevent sending any
920 other telemetry during that time.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_aprs_ssid"></a>11.6.9. APRS SSID</h3></div></div></div><p>Which SSID to report in APRS packets. By
921 default, this is set to the last digit of the
922 serial number, but can be configured to any
923 value from 0 to 9.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_aprs_format"></a>11.6.10. APRS Format</h3></div></div></div><p>Whether to send APRS data in Compressed or
924 Uncompressed format. Compressed format is
925 smaller and more precise. Uncompressed
926 format is older, but may work better with your
927 device. The Kenwood TH-D72 only displays
928 altitude information with Uncompressed
929 format, while the Yaesu FT1D only displays
930 altitude with Compressed format. Test before
931 you fly to see which to use.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_callsign"></a>11.6.11. Callsign</h3></div></div></div><p>This sets the call sign included in each
932 telemetry packet. Set this as needed to
933 conform to your local radio regulations.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_maximum_flight_log_size"></a>11.6.12. Maximum Flight Log Size</h3></div></div></div><p>This sets the space (in kilobytes) allocated
934 for each flight log. The available space will
935 be divided into chunks of this size. A smaller
936 value will allow more flights to be stored, a
937 larger value will record data from longer
938 flights.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_ignitor_firing_mode"></a>11.6.13. Ignitor Firing Mode</h3></div></div></div><p>This configuration parameter allows the two standard ignitor
939 channels (Apogee and Main) to be used in different
940 configurations.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
943 This is the usual mode of operation; the
944 <span class="emphasis"><em>apogee</em></span> channel is fired at apogee and the
945 <span class="emphasis"><em>main</em></span> channel at the height above ground
946 specified by the <span class="emphasis"><em>Main Deploy Altitude</em></span> during
948 </dd><dt><span class="term">
951 This fires both channels at apogee, the
952 <span class="emphasis"><em>apogee</em></span> channel first followed after a two
953 second delay by the <span class="emphasis"><em>main</em></span> channel.
954 </dd><dt><span class="term">
957 This fires both channels at the height above
958 ground specified by the Main Deploy Altitude
959 setting during descent. The <span class="emphasis"><em>apogee</em></span> channel
960 is fired first, followed after a two second
961 delay by the <span class="emphasis"><em>main</em></span> channel.
962 </dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_pad_orientation"></a>11.6.14. Pad Orientation</h3></div></div></div><p>Because they include accelerometers,
963 TeleMetrum, TeleMega and EasyMega are
964 sensitive to the orientation of the board. By
965 default, they expect the antenna end to point
966 forward. This parameter allows that default to
967 be changed, permitting the board to be mounted
968 with the antenna pointing aft instead.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
971 In this mode, the antenna end of the flight
972 computer must point forward, in line with the
973 expected flight path.
974 </dd><dt><span class="term">
977 In this mode, the antenna end of the flight
978 computer must point aft, in line with the
979 expected flight path.
980 </dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_beeper_frequency"></a>11.6.15. Beeper Frequency</h3></div></div></div><p>The beeper on all Altus Metrum flight
981 computers works best at 4000Hz, however if you
982 have more than one flight computer in a single
983 airframe, having all of them sound at the same
984 frequency can be confusing. This parameter
985 lets you adjust the base beeper frequency
986 value.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_logging_trigger_motion"></a>11.6.16. Logging Trigger Motion</h3></div></div></div><p>This sets the amount of motion that TeleGPS
987 needs to see before logging the new
988 position. Motions smaller than this are
989 skipped, which saves storage space.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_position_reporting_interval"></a>11.6.17. Position Reporting Interval</h3></div></div></div><p>The interval between TeleGPS position reports,
990 both over the air and in the log. Increase
991 this to reduce the frequency of radio
992 transmissions and the length of time available
993 in the log.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_configure_pyro_channels"></a>11.6.18. Configure Pyro Channels</h3></div></div></div><div class="figure"><a id="idm1421"></a><p class="title"><strong>Figure 11.15. Additional Pyro Channel Configuration</strong></p><div class="figure-contents"><div class="mediaobject"><img src="configure-pyro.png" width="495" alt="configure-pyro.png" /></div></div></div><br class="figure-break" /><p>This opens a separate window to configure the
994 additional pyro channels available on TeleMega
995 and EasyMega. One column is presented for
996 each channel. Each row represents a single
997 parameter, if enabled the parameter must meet
998 the specified test for the pyro channel to be
999 fired.</p><p>Select conditions and set the related value;
1000 the pyro channel will be activated when <span class="strong"><strong>all</strong></span>
1001 of the conditions are met. Each pyro channel
1002 has a separate set of configuration values, so
1003 you can use different values for the same
1004 condition with different channels.</p><p>At the bottom of the window, the <span class="emphasis"><em>Pyro Firing
1005 Time</em></span> configuration sets the length of time
1006 (in seconds) which each of these pyro channels
1007 will fire for.</p><p>Once you have selected the appropriate
1008 configuration for all of the necessary pyro
1009 channels, you can save the pyro configuration
1010 along with the rest of the flight computer
1011 configuration by pressing the <span class="emphasis"><em>Save</em></span> button in
1012 the main Configure Flight Computer window.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1015 Select a value, and then choose
1016 whether acceleration should be above or below
1017 that value. Acceleration is positive upwards,
1018 so accelerating towards the ground would
1019 produce negative numbers. Acceleration during
1020 descent is noisy and inaccurate, so be careful
1021 when using it during these phases of the
1023 </dd><dt><span class="term">
1026 Select a value, and then
1027 choose whether vertical speed should be above
1028 or below that value. Speed is positive
1029 upwards, so moving towards the ground would
1030 produce negative numbers. Speed during descent
1031 is a bit noisy and so be careful when using it
1032 during these phases of the flight.
1033 </dd><dt><span class="term">
1036 Select a value, and then choose
1037 whether the height above the launch pad should
1038 be above or below that value.
1039 </dd><dt><span class="term">
1042 TeleMega and EasyMega contain a
1043 3-axis gyroscope and accelerometer which is
1044 used to measure the current angle. Note that
1045 this angle is not the change in angle from the
1046 launch pad, but rather absolute relative to
1047 gravity; the 3-axis accelerometer is used to
1048 compute the angle of the rocket on the launch
1049 pad and initialize the system.
1050 </dd></dl></div><div class="note" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Note</h3><p>Because this value is computed by integrating
1051 rate gyros, it gets progressively less
1052 accurate as the flight goes on. It should have
1053 an accumulated error of less than 0.2°/second
1054 (after 10 seconds of flight, the error should
1055 be less than 2°).</p><p>The usual use of the orientation configuration
1056 is to ensure that the rocket is traveling
1057 mostly upwards when deciding whether to ignite
1058 air starts or additional stages. For that,
1059 choose a reasonable maximum angle (like 20°)
1060 and set the motor igniter to require an angle
1061 of less than that value.</p></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1064 Time since boost was detected. Select a value and choose
1065 whether to activate the pyro channel before or after that amount of
1067 </dd><dt><span class="term">
1070 A simple test saying whether the rocket is going up or
1071 not. This is exactly equivalent to testing whether the speed is > 0.
1072 </dd><dt><span class="term">
1075 A simple test saying whether the rocket is going down or
1076 not. This is exactly equivalent to testing whether the speed is < 0.
1077 </dd><dt><span class="term">
1080 The flight software counts each time the rocket starts
1081 accelerating and then decelerating (presumably due to a motor or
1082 motors burning). Use this value for multi-staged or multi-airstart
1084 </dd><dt><span class="term">
1087 This value doesn’t perform any checks, instead it inserts a
1088 delay between the time when the other parameters become true and when
1089 the pyro channel is activated.
1090 </dd><dt><span class="term">
1092 </span></dt><dd><p class="simpara">
1093 The flight software tracks the flight
1094 through a sequence of states:
1095 </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
1096 Boost. The motor has lit and the rocket is
1097 accelerating upwards.
1098 </li><li class="listitem">
1099 Fast. The motor has burned out and the
1100 rocket is decelerating, but it is going
1102 </li><li class="listitem">
1103 Coast. The rocket is still moving upwards
1104 and decelerating, but the speed is less
1106 </li><li class="listitem">
1107 Drogue. The rocket has reached apogee and
1108 is heading back down, but is above the
1109 configured Main altitude.
1110 </li><li class="listitem">
1111 Main. The rocket is still descending, and
1112 is below the Main altitude
1113 </li><li class="listitem">
1114 Landed. The rocket is no longer moving.
1115 </li></ul></div></dd></dl></div><p>You can select a state to limit when the pyro channel may activate;
1116 note that the check is based on when the rocket transitions <span class="strong"><strong>into</strong></span> the
1117 state, and so checking for “greater than Boost” means that the rocket
1118 is currently in boost or some later state.</p><p>When a motor burns out, the rocket enters either Fast or Coast state
1119 (depending on how fast it is moving). If the computer detects upwards
1120 acceleration again, it will move back to Boost state.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_configure_altosui"></a>11.7. Configure AltosUI</h2></div></div></div><div class="figure"><a id="idm1498"></a><p class="title"><strong>Figure 11.16. Configure AltosUI Dialog</strong></p><div class="figure-contents"><div class="mediaobject"><img src="configure-altosui.png" width="216" alt="configure-altosui.png" /></div></div></div><br class="figure-break" /><p>This button presents a dialog so that you can
1121 configure the AltosUI global settings.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_voice_settings"></a>11.7.1. Voice Settings</h3></div></div></div><p>AltosUI provides voice announcements during
1122 flight so that you can keep your eyes on the
1123 sky and still get information about the
1124 current flight status. However, sometimes you
1125 don’t want to hear them.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1128 Turns all voice announcements on and off
1129 </dd><dt><span class="term">
1132 Plays a short message allowing you to verify
1133 that the audio system is working and the volume settings
1135 </dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_log_directory"></a>11.7.2. Log Directory</h3></div></div></div><p>AltosUI logs all telemetry data and saves all
1136 flash data to this directory. This
1137 directory is also used as the staring point
1138 when selecting data files for display or
1139 export.</p><p>Click on the directory name to bring up a
1140 directory choosing dialog, select a new
1141 directory and click <span class="emphasis"><em>Select Directory</em></span> to
1142 change where AltosUI reads and writes data
1143 files.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_callsign_2"></a>11.7.3. Callsign</h3></div></div></div><p>This value is transmitted in each command
1144 packet sent from TeleDongle and received from
1145 an altimeter. It is not used in telemetry
1146 mode, as the callsign configured in the
1147 altimeter board is included in all telemetry
1148 packets. Configure this with the AltosUI
1149 operators call sign as needed to comply with
1150 your local radio regulations.</p><p>Note that to successfully command a flight
1151 computer over the radio (to configure the
1152 altimeter, monitor idle, or fire pyro
1153 charges), the callsign configured here must
1154 exactly match the callsign configured in the
1155 flight computer. This matching is case
1156 sensitive.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_imperial_units"></a>11.7.4. Imperial Units</h3></div></div></div><p>This switches between metric units (meters)
1157 and imperial units (feet and miles). This
1158 affects the display of values use during
1159 flight monitoring, configuration, data
1160 graphing and all of the voice
1161 announcements. It does not change the units
1162 used when exporting to CSV files, those are
1163 always produced in metric units.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_serial_debug"></a>11.7.5. Serial Debug</h3></div></div></div><p>This causes all communication with a connected
1164 device to be dumped to the console from which
1165 AltosUI was started. If you’ve started it from
1166 an icon or menu entry, the output will simply
1167 be discarded. This mode can be useful to debug
1168 various serial communication issues.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_font_size"></a>11.7.6. Font size</h3></div></div></div><p>Selects the set of fonts used in the flight
1169 monitor window. Choose between the small,
1170 medium and large sets.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_look_amp_feel"></a>11.7.7. Look & feel</h3></div></div></div><p>Switches between the available Java user
1171 interface appearances. The default selection
1172 is supposed to match the native window system
1173 appearance for the target platform.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_menu_position"></a>11.7.8. Menu position</h3></div></div></div><p>Selects the initial position for the main
1174 AltosUI window that includes all of the
1175 command buttons.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_map_cache_size"></a>11.7.9. Map Cache Size</h3></div></div></div><p>Sets the number of map <span class="emphasis"><em>tiles</em></span> kept in memory
1176 while the application is running. More tiles
1177 consume more memory, but will make panning
1178 around the map faster.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_manage_frequencies"></a>11.7.10. Manage Frequencies</h3></div></div></div><p>This brings up a dialog where you can
1179 configure the set of frequencies shown in the
1180 various frequency menus. You can add as many
1181 as you like, or even reconfigure the default
1182 set. Changing this list does not affect the
1183 frequency settings of any devices, it only
1184 changes the set of frequencies shown in the
1185 menus.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_configure_groundstation"></a>11.8. Configure Groundstation</h2></div></div></div><div class="figure"><a id="idm1551"></a><p class="title"><strong>Figure 11.17. Configure Groundstation Dialog</strong></p><div class="figure-contents"><div class="mediaobject"><img src="configure-groundstation.png" width="279" alt="configure-groundstation.png" /></div></div></div><br class="figure-break" /><p>Select this button and then select a TeleDongle or
1186 TeleBT Device from the list provided.</p><p>The first few lines of the dialog provide information
1187 about the connected device, including the product
1188 name, software version and hardware serial
1189 number. Below that are the individual configuration
1190 entries.</p><p>Note that TeleDongle and TeleBT don’t save any
1191 configuration data, the settings here are recorded on
1192 the local machine in the Java preferences
1193 database. Moving the device to another machine, or
1194 using a different user account on the same machine
1195 will cause settings made here to have no effect.</p><p>At the bottom of the dialog, there are three
1196 buttons:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1199 This writes any changes to the local Java
1200 preferences file. If you don’t press this
1201 button, any changes you make will be lost.
1202 </dd><dt><span class="term">
1205 This resets the dialog to the most recently
1206 saved values, erasing any changes you have
1208 </dd><dt><span class="term">
1211 This closes the dialog. Any unsaved changes
1213 </dd></dl></div><p>The rest of the dialog contains the parameters
1214 to be configured.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_frequency_2"></a>11.8.1. Frequency</h3></div></div></div><p>This configures the frequency to use for both
1215 telemetry and packet command mode. Set this
1216 before starting any operation involving packet
1217 command mode so that it will use the right
1218 frequency. Telemetry monitoring mode also
1219 provides a menu to change the frequency, and
1220 that menu also sets the same Java preference
1221 value used here.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_rf_calibration_2"></a>11.8.2. RF Calibration</h3></div></div></div><p>The radios in every Altus Metrum device are
1222 calibrated at the factory to ensure that they
1223 transmit and receive on the specified
1224 frequency. To change a TeleDongle or TeleBT’s
1225 calibration, you must reprogram the unit
1226 completely, so this entry simply shows the
1227 current value and doesn’t allow any changes.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_telemetry_rate"></a>11.8.3. Telemetry Rate</h3></div></div></div><p>This lets you match the telemetry and packet
1228 link rate from the transmitter. If they don’t
1229 match, the device won’t receive any data.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_flash_image"></a>11.9. Flash Image</h2></div></div></div><p>This reprograms Altus Metrum devices with new
1231 TeleMetrum v1.x, TeleDongle v0.2, TeleMini
1232 and TeleBT are all reprogrammed by using another
1233 similar unit as a programming dongle (pair
1235 TeleMega, EasyMega, TeleMetrum v2,
1236 EasyMini and TeleDongle v3 are all
1238 over USB (self programming). Please read
1239 the directions for flashing devices in
1240 <a class="xref" href="#_updating_device_firmware" title="Appendix C. Updating Device Firmware">Appendix C, <em>Updating Device Firmware</em></a>.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_fire_igniter"></a>11.10. Fire Igniter</h2></div></div></div><div class="figure"><a id="idm1591"></a><p class="title"><strong>Figure 11.18. Fire Igniter Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="fire-igniter.png" width="108" alt="fire-igniter.png" /></div></div></div><br class="figure-break" /><p>This activates the igniter circuits in the flight
1241 computer to help test recovery systems
1243 Because this command can operate over the
1244 Packet Command Link, you can prepare the rocket as for
1245 flight and then test the recovery system without
1246 needing to snake wires inside the air-frame.</p><p>Selecting the <span class="emphasis"><em>Fire Igniter</em></span> button brings up the
1247 usual device selection dialog. Pick the desired
1248 device. This brings up another window which shows the
1249 current continuity test status for all of the pyro
1250 channels.</p><p>Next, select the desired igniter to fire. This will
1251 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>
1252 button. The word <span class="emphasis"><em>Arm</em></span> is replaced by a countdown
1253 timer indicating that you have 10 seconds to press the
1254 <span class="emphasis"><em>Fire</em></span> button or the system will deactivate, at which
1255 point you start over again at selecting the desired
1256 igniter.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_scan_channels"></a>11.11. Scan Channels</h2></div></div></div><div class="figure"><a id="idm1610"></a><p class="title"><strong>Figure 11.19. Scan Channels Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="scan-channels.png" width="288" alt="scan-channels.png" /></div></div></div><br class="figure-break" /><p>This listens for telemetry packets on all of the
1257 configured frequencies, displaying information about
1258 each device it receives a packet from. You can select
1259 which of the baud rates and telemetry formats should
1260 be tried; by default, it only listens at 38400 baud
1261 with the standard telemetry format used in v1.0 and
1262 later firmware.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_load_maps"></a>11.12. Load Maps</h2></div></div></div><div class="figure"><a id="idm1620"></a><p class="title"><strong>Figure 11.20. Load Maps Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="load-maps.png" width="468" alt="load-maps.png" /></div></div></div><br class="figure-break" /><p>Before heading out to a new launch site, you can use
1263 this to load satellite images in case you don’t have
1264 internet connectivity at the site.</p><p>There’s a drop-down menu of launch sites we know
1265 about; if your favorites aren’t there, please let us
1266 know the lat/lon and name of the site. The contents of
1267 this list are actually downloaded from our server at
1268 run-time, so as new sites are sent in, they’ll get
1269 automatically added to this list. If the launch site
1270 isn’t in the list, you can manually enter the lat/lon
1271 values</p><p>There are four different kinds of maps you can view;
1272 you can select which to download by selecting as many
1273 as you like from the available types:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1276 A combination of satellite imagery and road data. This
1277 is the default view.
1278 </dd><dt><span class="term">
1281 Just the satellite imagery without any annotation.
1282 </dd><dt><span class="term">
1285 Roads, political boundaries and a few geographic
1287 </dd><dt><span class="term">
1290 Contour intervals and shading that show hills and
1292 </dd></dl></div><p>You can specify the range of zoom levels to download;
1293 smaller numbers show more area with less
1294 resolution. The default level, 0, shows about
1295 3m/pixel. One zoom level change doubles or halves that
1296 number. Larger zoom levels show more detail, smaller
1297 zoom levels less.</p><p>The Map Radius value sets how large an area around the
1298 center point to download. Select a value large enough
1299 to cover any plausible flight from that site. Be aware
1300 that loading a large area with a high maximum zoom
1301 level can attempt to download a lot of data. Loading
1302 hybrid maps with a 10km radius at a minimum zoom of -2
1303 and a maximum zoom of 2 consumes about 120MB of
1304 space. Terrain and road maps consume about 1/10 as
1305 much space as satellite or hybrid maps.</p><p>Clicking the <span class="emphasis"><em>Load Map</em></span> button will fetch images from
1306 Google Maps; note that Google limits how many images
1307 you can fetch at once, so if you load more than one
1308 launch site, you may get some gray areas in the map
1309 which indicate that Google is tired of sending data to
1310 you. Try again later.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_monitor_idle"></a>11.13. Monitor Idle</h2></div></div></div><div class="figure"><a id="idm1653"></a><p class="title"><strong>Figure 11.21. Monitor Idle Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="monitor-idle.png" width="468" alt="monitor-idle.png" /></div></div></div><br class="figure-break" /><p>This brings up a dialog similar to the Monitor Flight
1311 UI, except it works with the altimeter in “idle” mode
1312 by sending query commands to discover the current
1313 state rather than listening for telemetry
1314 packets. Because this uses command mode, it needs to
1315 have the TeleDongle and flight computer callsigns
1316 match exactly. If you can receive telemetry, but
1317 cannot manage to run Monitor Idle, then it’s very
1318 likely that your callsigns are different in some way.</p><p>You can change the frequency and callsign used to
1319 communicate with the flight computer; they must both
1320 match the configuration in the flight computer
1321 exactly.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_altosdroid"></a>Chapter 12. AltosDroid</h1></div></div></div><p>AltosDroid provides the same flight monitoring capabilities as
1322 AltosUI, but runs on Android devices. AltosDroid is designed
1323 to connect to a TeleBT receiver over Bluetooth™ and (on
1324 Android devices supporting USB On-the-go) TeleDongle and
1325 TeleBT devices over USB. AltosDroid monitors telemetry data,
1326 logging it to internal storage in the Android device, and
1327 presents that data in a UI similar to the <span class="emphasis"><em>Monitor Flight</em></span>
1328 window in AltosUI.</p><p>This manual will explain how to configure AltosDroid, connect
1329 to TeleBT or TeleDongle, operate the flight monitoring
1330 interface and describe what the displayed data means.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_installing_altosdroid"></a>12.1. Installing AltosDroid</h2></div></div></div><p>AltosDroid is available from the Google Play store. To
1331 install it on your Android device, open the Google
1332 Play Store application and search for
1333 “altosdroid”. Make sure you don’t have a space between
1334 “altos” and “droid” or you probably won’t find what
1335 you want. That should bring you to the right page from
1336 which you can download and install the application.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_charging_telebt_battery"></a>12.2. Charging TeleBT Battery</h2></div></div></div><p>Before using TeleBT with AltosDroid, make sure the
1337 internal TeleBT battery is charged. To do this,
1338 attach a micro USB cable from a computer or other USB
1339 power source to TeleBT. A dual LED on the circuit
1340 board should illuminate, showing red while the battery
1341 is charging, green when charging is completed, and
1342 both red and green on at the same time if there is a
1343 battery fault.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_connecting_to_telebt_over_bluetooth"></a>12.3. Connecting to TeleBT over Bluetooth™</h2></div></div></div><p>Press the Android <span class="emphasis"><em>Menu</em></span> button or soft-key to see the
1344 configuration options available. Select the <span class="emphasis"><em>Connect a
1345 device</em></span> option and then the <span class="emphasis"><em>Scan for devices</em></span> entry
1346 at the bottom to look for your TeleBT device. Select
1347 your device, and when it asks for the code, enter
1348 <span class="emphasis"><em>1234</em></span>.</p><p>Subsequent connections will not require you to enter
1349 that code, and your <span class="emphasis"><em>paired</em></span> device will appear in the
1350 list without scanning.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_connecting_to_teledongle_or_telebt_over_usb"></a>12.4. Connecting to TeleDongle or TeleBT over USB</h2></div></div></div><p>Get a special USB On-the-go adapter cable. These
1351 cables have a USB micro-B male connector on one end
1352 and a standard A female connector on the other
1353 end. Plug in your TeleDongle or TeleBT device to the
1354 adapter cable and the adapter cable into your phone
1355 and AltosDroid should automatically start up. If it
1356 doesn’t, the most likely reason is that your Android
1357 device doesn’t support USB On-the-go.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosdroid_menu"></a>12.5. AltosDroid Menu</h2></div></div></div><p>The main AltosDroid menu has a selection of operation
1358 and configuration options.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1361 Offers a menu of available TeleBT devices, and an
1362 option to scan for additional devices.
1363 </dd><dt><span class="term">
1366 Disconnects the current TeleBT or TeleDongle
1367 device. You can reconnect TeleBT over bluetooth by
1368 using Connect a Device. You can reconnect a USB device
1369 by unplugging it and then plugging it back in.
1370 </dd><dt><span class="term">
1371 Select radio frequency
1373 This selects which frequency to listen on by bringing
1374 up a menu of pre-set radio frequencies. Pick the one
1375 which matches your altimeter.
1376 </dd><dt><span class="term">
1379 Switches the information displays to show data for a
1380 different transmitting device. The map will always
1381 show all of the devices in view. Trackers are shown
1382 and selected by serial number, so make sure you note
1383 the serial number of devices in each airframe.
1384 </dd><dt><span class="term">
1387 Deletes all information about a transmitting device.
1388 </dd><dt><span class="term">
1391 Offers additional configuration operations. See
1392 <a class="xref" href="#_setup" title="12.6. Setup">Section 12.6, “Setup”</a>.
1393 </dd><dt><span class="term">
1396 Communicate with an altimeter in Idle mode. See <a class="xref" href="#_idle_mode" title="12.7. Idle Mode">Section 12.7, “Idle Mode”</a>
1397 </dd><dt><span class="term">
1400 Shuts down AltosDroid.
1401 </dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_setup"></a>12.6. Setup</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1404 Altus Metrum transmitters can be configured to operate
1405 at lower data rates to improve transmission range. If
1406 you have configured your device to do this, this menu
1407 item allows you to change the receiver to match.
1408 </dd><dt><span class="term">
1411 Selects which units used to report values.
1412 </dd><dt><span class="term">
1415 Displays a menu of map types and lets you select
1416 one. Hybrid maps include satellite images with a
1417 roadmap overlaid. Satellite maps dispense with the
1418 roadmap overlay. Roadmap shows just the roads. Terrain
1419 includes roads along with shadows indicating changes
1420 in elevation, and other geographical features.
1421 </dd><dt><span class="term">
1424 Select between online and offline maps. Online maps
1425 will show a <span class="emphasis"><em>move to current position</em></span> icon in the
1426 upper right corner, while offline maps will have
1427 copyright information all over the map. Otherwise,
1428 they’re pretty similar.
1429 </dd><dt><span class="term">
1432 Brings up a dialog allowing you to download offline
1433 map tiles so that you can have maps available even if
1434 you have no network connectivity at the launch site.
1435 </dd><dt><span class="term">
1438 This presents a dialog containing the current list of
1439 frequencies that will be show in the <span class="emphasis"><em>Select radio
1440 frequency</em></span> menu. You can change the label for existing
1441 frequencies, delete or add new frequencies.
1442 </dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_idle_mode"></a>12.7. Idle Mode</h2></div></div></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1445 Lets you configure the callsign used by AltosDroid to
1446 communicate with the flight computer. The callsign on
1447 the two devices must match or the communication will
1448 fail. This provides a modest amount of protection
1449 against accidentally controlling another persons
1451 </dd><dt><span class="term">
1454 This provides similar information to monitoring the
1455 telemetry stream from a flight computer in flight
1456 mode. The title of the application will change to
1457 include (idle) so you can tell this mode is active.
1458 </dd><dt><span class="term">
1461 Remotely reboots the flight computer. This is useful
1462 when the flight computers turned on while the airframe
1463 is horizontal and you want to restart the flight
1464 computers in pad mode after raising the airframe to
1466 </dd><dt><span class="term">
1469 Remotely control igniters for ground testing recovery
1471 </dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosdroid_flight_monitoring"></a>12.8. AltosDroid Flight Monitoring</h2></div></div></div><p>AltosDroid is designed to mimic the AltosUI flight
1472 monitoring display, providing separate tabs for each
1473 stage of your rocket flight along with a tab
1474 containing a map of the local area with icons marking
1475 the current location of the altimeter and the Android
1476 device.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_pad"></a>12.9. Pad</h2></div></div></div><p>The <span class="emphasis"><em>Pad</em></span> tab shows information used to decide when
1477 the rocket is ready for flight. The first elements
1478 include red/green indicators, if any of these is red,
1479 you’ll want to evaluate whether the rocket is ready to
1480 launch.</p><p>When the pad tab is selected, the voice responses will
1481 include status changes to the igniters and GPS
1482 reception, letting you know if the rocket is still
1483 ready for launch.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1486 This indicates whether the Li-Po battery powering the
1487 transmitter has sufficient charge to last for the
1488 duration of the flight. A value of more than 3.8V is
1489 required for a <span class="emphasis"><em>GO</em></span> status.
1490 </dd><dt><span class="term">
1493 This indicates whether the Li-Po battery powering the
1494 TeleBT has sufficient charge to last for the duration
1495 of the flight. A value of more than 3.8V is required
1496 for a <span class="emphasis"><em>GO</em></span> status.
1497 </dd><dt><span class="term">
1500 This indicates whether there is space remaining
1501 on-board to store flight data for the upcoming
1502 flight. If you’ve downloaded data, but failed to erase
1503 flights, there may not be any space left. TeleMetrum
1504 and TeleMega can store multiple flights, depending on
1505 the configured maximum flight log size. TeleGPS logs
1506 data continuously. TeleMini stores only a single
1507 flight, so it will need to be downloaded and erased
1508 after each flight to capture data. This only affects
1509 on-board flight logging; the altimeter will still
1510 transmit telemetry and fire ejection charges at the
1512 </dd><dt><span class="term">
1515 For a TeleMetrum or TeleMega device, this indicates
1516 whether the GPS receiver is currently able to compute
1517 position information. GPS requires at least 4
1518 satellites to compute an accurate position.
1519 </dd><dt><span class="term">
1522 For a TeleMetrum or TeleMega device, this indicates
1523 whether GPS has reported at least 10 consecutive
1524 positions without losing lock. This ensures that the
1525 GPS receiver has reliable reception from the
1527 </dd><dt><span class="term">
1530 This indicates whether the apogee igniter has
1531 continuity. If the igniter has a low resistance, then
1532 the voltage measured here will be close to the Li-Po
1533 battery voltage. A value greater than 3.2V is required
1534 for a <span class="emphasis"><em>GO</em></span> status.
1535 </dd><dt><span class="term">
1538 This indicates whether the main igniter has
1539 continuity. If the igniter has a low resistance, then
1540 the voltage measured here will be close to the Li-Po
1541 battery voltage. A value greater than 3.2V is required
1542 for a <span class="emphasis"><em>GO</em></span> status.
1543 </dd><dt><span class="term">
1546 This indicates whether the indicated additional pyro
1547 channel igniter has continuity. If the igniter has a
1548 low resistance, then the voltage measured here will be
1549 close to the Li-Po battery voltage. A value greater
1550 than 3.2V is required for a <span class="emphasis"><em>GO</em></span> status.
1551 </dd></dl></div><p>The Pad tab also shows the location of the Android
1552 device.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_flight"></a>12.10. Flight</h2></div></div></div><p>The <span class="emphasis"><em>Flight</em></span> tab shows information used to evaluate
1553 and spot a rocket while in flight. It displays speed
1554 and height data to monitor the health of the rocket,
1555 along with elevation, range and bearing to help locate
1556 the rocket in the sky.</p><p>While the Flight tab is displayed, the voice
1557 announcements will include current speed, height,
1558 elevation and bearing information.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1561 Shows current vertical speed. During descent, the
1562 speed values are averaged over a fairly long time to
1563 try and make them steadier.
1564 </dd><dt><span class="term">
1567 Shows the current height above the launch pad.
1568 </dd><dt><span class="term">
1571 Shows the maximum vertical speed seen during the
1573 </dd><dt><span class="term">
1576 Shows the maximum height above launch pad.
1577 </dd><dt><span class="term">
1580 This is the angle above the horizon from the android
1581 devices current position.
1582 </dd><dt><span class="term">
1585 The total distance from the android device to the
1586 rocket, including both ground distance and difference
1587 in altitude. Use this to gauge how large the rocket is
1588 likely to appear in the sky.
1589 </dd><dt><span class="term">
1592 This is the azimuth from true north for the rocket
1593 from the android device. Use this in combination with
1594 the Elevation value to help locate the rocket in the
1595 sky, or at least to help point the antenna in the
1596 general direction. This is provided in both degrees
1597 and a compass point (like West South West). You’ll
1598 want to know which direction is true north before
1599 launching your rocket.
1600 </dd><dt><span class="term">
1603 This shows the distance across the ground to the
1604 lat/lon where the rocket is located. Use this to
1605 estimate what is currently under the rocket.
1606 </dd><dt><span class="term">
1609 Displays the last known location of the rocket.
1610 </dd><dt><span class="term">
1613 This indicates whether the apogee igniter has
1614 continuity. If the igniter has a low resistance, then
1615 the voltage measured here will be close to the Li-Po
1616 battery voltage. A value greater than 3.2V is required
1617 for a <span class="emphasis"><em>GO</em></span> status.
1618 </dd><dt><span class="term">
1621 This indicates whether the main igniter has
1622 continuity. If the igniter has a low resistance, then
1623 the voltage measured here will be close to the Li-Po
1624 battery voltage. A value greater than 3.2V is required
1625 for a <span class="emphasis"><em>GO</em></span> status.
1626 </dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_recover"></a>12.11. Recover</h2></div></div></div><p>The <span class="emphasis"><em>Recover</em></span> tab shows information used while
1627 recovering the rocket on the ground after flight.</p><p>While the Recover tab is displayed, the voice
1628 announcements will include distance along with either
1629 bearing or direction, depending on whether you are
1630 moving.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1633 This is the azimuth from true north for the rocket
1634 from the android device. Use this in combination with
1635 the Elevation value to help locate the rocket in the
1636 sky, or at least to help point the antenna in the
1637 general direction. This is provided in both degrees
1638 and a compass point (like West South West). You’ll
1639 want to know which direction is true north before
1640 launching your rocket.
1641 </dd><dt><span class="term">
1644 When you are in motion, this provides the angle from
1645 your current direction of motion towards the rocket.
1646 </dd><dt><span class="term">
1649 Distance over the ground to the rocket.
1650 </dd><dt><span class="term">
1653 Displays the last known location of the rocket.
1654 </dd><dt><span class="term">
1657 Displays the location of the Android device.
1658 </dd><dt><span class="term">
1661 Shows the maximum height above launch pad seen during
1663 </dd><dt><span class="term">
1666 Shows the maximum vertical speed seen during the
1668 </dd><dt><span class="term">
1671 Shows the maximum vertical acceleration seen during
1673 </dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_map_2"></a>12.12. Map</h2></div></div></div><p>The <span class="emphasis"><em>Map</em></span> tab shows a map of the area around the
1674 rocket being tracked along with information needed to
1675 recover it.</p><p>On the map itself, icons showing the location of the
1676 android device along with the last known location of
1677 each tracker. A blue line is drawn from the android
1678 device location to the currently selected tracker.</p><p>Below the map, the distance and either bearing or
1679 direction along with the lat/lon of the target and the
1680 android device are shown</p><p>The Map tab provides the same voice announcements as
1681 the Recover tab.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_downloading_flight_logs"></a>12.13. Downloading Flight Logs</h2></div></div></div><p>AltosDroid always saves every bit of telemetry data it
1682 receives. To download that to a computer for use with
1683 AltosUI, remove the SD card from your Android device,
1684 or connect your device to your computer’s USB port and
1685 browse the files on that device. You will find
1686 <span class="emphasis"><em>.telem</em></span> files in the TeleMetrum directory that will
1687 work with AltosUI directly.</p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_system_operation"></a>Appendix A. System Operation</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_firmware_modes"></a>A.1. Firmware Modes</h2></div></div></div><p>The AltOS firmware build for the altimeters has two
1688 fundamental modes, “idle” and “flight”. Which of these modes
1689 the firmware operates in is determined at start up
1692 TeleMetrum, TeleMega and EasyMega, which have accelerometers, the mode is
1693 controlled by the orientation of the
1694 rocket (well, actually the board, of course…) at the time
1695 power is switched on. If the rocket is “nose up”, then
1696 the flight computer assumes it’s on a rail or rod being prepared for
1697 launch, so the firmware chooses flight mode. However, if the
1698 rocket is more or less horizontal, the firmware instead enters
1703 accelerometer we can use to determine orientation, “idle” mode
1704 is selected if the board is connected via USB to a computer,
1705 otherwise the board enters “flight” mode.
1707 selects “idle” mode if it receives a command packet within the
1708 first five seconds of operation.</p><p>At power on, the altimeter will beep out the battery voltage
1709 to the nearest tenth of a volt. Each digit is represented by
1710 a sequence of short “dit” beeps, with a pause between
1711 digits. A zero digit is represented with one long “dah”
1712 beep. Then there will be a short pause while the altimeter
1713 completes initialization and self test, and decides which mode
1714 to enter next.</p><p>In flight or “pad” mode, the altimeter engages the flight
1715 state machine, goes into transmit-only mode to send telemetry,
1716 and waits for launch to be detected. Flight mode is indicated
1717 by an “di-dah-dah-dit” (“P” for pad) on the beeper or lights,
1718 followed by beeps or flashes indicating the state of the
1719 pyrotechnic igniter continuity. One beep/flash indicates
1720 apogee continuity, two beeps/flashes indicate main continuity,
1721 three beeps/flashes indicate both apogee and main continuity,
1722 and one longer “brap” sound which is made by rapidly
1723 alternating between two tones indicates no continuity. For a
1724 dual deploy flight, make sure you’re getting three beeps or
1725 flashes before launching! For apogee-only or motor eject
1726 flights, do what makes sense.</p><p>If idle mode is entered, you will hear an audible “di-dit” or
1727 see two short flashes (“I” for idle), and the flight state
1728 machine is disengaged, thus no ejection charges will fire.
1729 The altimeters also listen for the radio link when in idle
1730 mode for requests sent via TeleDongle. Commands can be issued
1731 in idle mode over either USB or the radio link
1733 TeleMini v1.0 only has the radio link.
1734 Idle mode is useful for configuring the altimeter, for
1735 extracting data from the on-board storage chip after
1736 flight, and for ground testing pyro charges.</p><p>In “Idle” and “Pad” modes, once the mode indication
1737 beeps/flashes and continuity indication has been sent, if
1738 there is no space available to log the flight in on-board
1739 memory, the flight computer will emit a warbling tone (much
1740 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
1741 the audio signals used.</p><p>Once landed, the flight computer will signal that by emitting
1742 the “Landed” sound described above, after which it will beep
1743 out the apogee height (in meters). Each digit is represented
1744 by a sequence of short “dit” beeps, with a pause between
1745 digits. A zero digit is represented with one long “dah”
1746 beep. The flight computer will continue to report landed mode
1747 and beep out the maximum height until turned off.</p><p>One “neat trick” of particular value when TeleMetrum, TeleMega
1748 or EasyMega are used with
1749 very large air-frames, is that you can power the board up while the
1750 rocket is horizontal, such that it comes up in idle mode. Then you can
1751 raise the air-frame to launch position, and issue a <span class="emphasis"><em>reset</em></span> command
1752 via TeleDongle over the radio link to cause the altimeter to reboot and
1753 come up in flight mode. This is much safer than standing on the top
1754 step of a rickety step-ladder or hanging off the side of a launch
1755 tower with a screw-driver trying to turn on your avionics before
1756 installing igniters!</p><p>TeleMini v1.0 is configured solely via the radio link. Of course, that
1757 means you need to know the TeleMini radio configuration values
1758 or you won’t be able to communicate with it. For situations
1759 when you don’t have the radio configuration values, TeleMini v1.0
1760 offers an <span class="emphasis"><em>emergency recovery</em></span> mode. In this mode, TeleMini is
1761 configured as follows:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
1762 Sets the radio frequency to 434.550MHz
1763 </li><li class="listitem">
1764 Sets the radio calibration back to the factory value.
1765 </li><li class="listitem">
1766 Sets the callsign to N0CALL
1767 </li><li class="listitem">
1768 Does not go to <span class="emphasis"><em>pad</em></span> mode after five seconds.
1769 </li></ul></div><p>To get into <span class="emphasis"><em>emergency recovery</em></span> mode, first find the row of
1770 four small holes opposite the switch wiring. Using a short
1771 piece of small gauge wire, connect the outer two holes
1772 together, then power TeleMini up. Once the red LED is lit,
1773 disconnect the wire and the board should signal that it’s in
1774 <span class="emphasis"><em>idle</em></span> mode after the initial five second startup
1775 period.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_gps"></a>A.2. GPS</h2></div></div></div><p>TeleMetrum and TeleMega include a complete GPS receiver. A
1776 complete explanation of how GPS works is beyond the scope of
1777 this manual, but the bottom line is that the GPS receiver
1778 needs to lock onto at least four satellites to obtain a solid
1779 3 dimensional position fix and know what time it is.</p><p>The flight computers provide backup power to the GPS chip any time a
1780 battery is connected. This allows the receiver to “warm start” on
1781 the launch rail much faster than if every power-on were a GPS
1782 “cold start”. In typical operations, powering up
1783 on the flight line in idle mode while performing final air-frame
1784 preparation will be sufficient to allow the GPS receiver to cold
1785 start and acquire lock. Then the board can be powered down during
1786 RSO review and installation on a launch rod or rail. When the board
1787 is turned back on, the GPS system should lock very quickly, typically
1788 long before igniter installation and return to the flight line are
1789 complete.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_controlling_an_altimeter_over_the_radio_link"></a>A.3. Controlling An Altimeter Over The Radio Link</h2></div></div></div><p>One of the unique features of the Altus Metrum system is the
1790 ability to create a two way command link between TeleDongle
1791 and an altimeter using the digital radio transceivers
1792 built into each device. This allows you to interact with the
1793 altimeter from afar, as if it were directly connected to the
1794 computer.</p><p>Any operation which can be performed with a flight computer can
1795 either be done with the device directly connected to the
1796 computer via the USB cable, or through the radio
1797 link. TeleMini v1.0 doesn’t provide a USB connector and so it is
1798 always communicated with over radio. Select the appropriate
1799 TeleDongle device when the list of devices is presented and
1800 AltosUI will interact with an altimeter over the radio link.</p><p>One oddity in the current interface is how AltosUI selects the
1801 frequency for radio communications. Instead of providing
1802 an interface to specifically configure the frequency, it uses
1803 whatever frequency was most recently selected for the target
1804 TeleDongle device in Monitor Flight mode. If you haven’t ever
1805 used that mode with the TeleDongle in question, select the
1806 Monitor Flight button from the top level UI, and pick the
1807 appropriate TeleDongle device. Once the flight monitoring
1808 window is open, select the desired frequency and then close it
1809 down again. All radio communications will now use that frequency.</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
1810 Save Flight Data—Recover flight data from the
1811 rocket without opening it up.
1812 </li><li class="listitem">
1813 Configure altimeter apogee delays, main deploy
1814 heights and additional pyro event conditions to
1815 respond to changing launch conditions. You can also
1816 <span class="emphasis"><em>reboot</em></span> the altimeter. Use this to remotely enable
1817 the flight computer by turning TeleMetrum or
1818 TeleMega on in “idle” mode, then once the air-frame
1819 is oriented for launch, you can reboot the
1820 altimeter and have it restart in pad mode without
1821 having to climb the scary ladder.
1822 </li><li class="listitem">
1823 Fire Igniters—Test your deployment charges without snaking
1824 wires out through holes in the air-frame. Simply assemble the
1825 rocket as if for flight with the apogee and main charges
1826 loaded, then remotely command the altimeter to fire the
1828 </li></ul></div><p>Operation over the radio link for configuring an
1829 altimeter, ground testing igniters, and so forth uses
1830 the same RF frequencies as flight telemetry. To
1831 configure the desired TeleDongle frequency, select the
1832 monitor flight tab, then use the frequency selector
1833 and close the window before performing other desired
1834 radio operations.</p><p>The flight computers only enable radio commanding in
1835 <span class="emphasis"><em>idle</em></span> mode. TeleMetrum and TeleMega use the
1836 accelerometer to detect which orientation they start
1837 up in, so make sure you have the flight computer lying
1838 horizontally when you turn it on. Otherwise, it will
1839 start in <span class="emphasis"><em>pad</em></span> mode ready for flight, and will not be
1840 listening for command packets from TeleDongle.</p><p>TeleMini listens for a command packet for five seconds
1841 after first being turned on, if it doesn’t hear
1842 anything, it enters <span class="emphasis"><em>pad</em></span> mode, ready for flight and
1843 will no longer listen for command packets. The easiest
1844 way to connect to TeleMini is to initiate the command
1845 and select the TeleDongle device. At this point, the
1846 TeleDongle will be attempting to communicate with the
1847 TeleMini. Now turn TeleMini on, and it should
1848 immediately start communicating with the TeleDongle
1849 and the desired operation can be performed.</p><p>You can monitor the operation of the radio link by watching the
1850 lights on the devices. The red LED will flash each time a packet
1851 is transmitted, while the green LED will light up on TeleDongle when
1852 it is waiting to receive a packet from the altimeter.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_ground_testing"></a>A.4. Ground Testing</h2></div></div></div><p>An important aspect of preparing a rocket using electronic deployment
1853 for flight is ground testing the recovery system.
1855 to the bi-directional radio link central to the Altus Metrum system,
1856 this can be accomplished in a TeleMega, TeleMetrum or TeleMini equipped rocket
1857 with less work than you may be accustomed to with other systems. It
1858 can even be fun!</p><p>Just prep the rocket for flight, then power up the altimeter
1860 mode (placing air-frame horizontal for TeleMetrum or TeleMega, or
1861 selecting the Configure Altimeter tab for TeleMini).
1863 the firmware to go into “idle” mode, in which the normal flight
1864 state machine is disabled and charges will not fire without
1866 You can now command the altimeter to fire the apogee
1867 or main charges from a safe distance using your
1868 computer and the Fire Igniter tab to complete ejection testing.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_radio_link"></a>A.5. Radio Link</h2></div></div></div><p>TeleMetrum, TeleMini and TeleMega all incorporate an
1869 RF transceiver, but it’s not a full duplex system;
1870 each end can only be transmitting or receiving at any
1871 given moment. So we had to decide how to manage the
1872 link.</p><p>By design, the altimeter firmware listens for the
1873 radio link when it’s in “idle mode”, which allows us
1874 to use the radio link to configure the rocket, do
1875 things like ejection tests, and extract data after a
1876 flight without having to crack open the air-frame.
1877 However, when the board is in “flight mode”, the
1878 altimeter only transmits and doesn’t listen at all.
1879 That’s because we want to put ultimate priority on
1880 event detection and getting telemetry out of the
1881 rocket through the radio in case the rocket crashes
1882 and we aren’t able to extract data later.</p><p>We don’t generally use a <span class="emphasis"><em>normal packet radio</em></span> mode
1883 like APRS because they’re just too inefficient. The
1884 GFSK modulation we use is FSK with the base-band
1885 pulses passed through a Gaussian filter before they go
1886 into the modulator to limit the transmitted bandwidth.
1887 When combined with forward error correction and
1888 interleaving, this allows us to have a very robust
1889 19.2 kilobit data link with only 10-40 milliwatts of
1890 transmit power, a whip antenna in the rocket, and a
1891 hand-held Yagi on the ground. We’ve had flights to
1892 above 21k feet AGL with great reception, and
1893 calculations suggest we should be good to well over
1894 40k feet AGL with a 5-element yagi on the ground with
1895 our 10mW units and over 100k feet AGL with the 40mW
1896 devices. We hope to fly boards to higher altitudes
1897 over time, and would of course appreciate customer
1898 feedback on performance in higher altitude flights!</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_aprs"></a>A.6. APRS</h2></div></div></div><p>TeleMetrum v2.0 and TeleMega can send APRS if desired, and the
1899 interval between APRS packets can be configured. As each APRS
1900 packet takes a full second to transmit, we recommend an
1901 interval of at least 5 seconds to avoid consuming too much
1902 battery power or radio channel bandwidth. You can configure
1903 the APRS interval using AltosUI; that process is described in
1904 <a class="xref" href="#_configure_altimeter" title="11.6. Configure Altimeter">Section 11.6, “Configure Altimeter”</a>.</p><p>AltOS supports both compressed and uncompressed APRS
1905 position report data formats. The compressed format
1906 provides for higher position precision and shorter
1907 packets than the uncompressed APRS format. We’ve found
1908 some older APRS receivers that do not handle the
1909 compressed format. The Kenwood TH-72A requires the use
1910 of uncompressed format to display altitude information
1911 correctly. The Yaesu FT1D requires the use of
1912 compressed format to display altitude information.</p><p>APRS packets include an SSID (Secondary Station Identifier)
1913 field that allows one operator to have multiple
1914 transmitters. AltOS allows you to set this to a single digit
1915 from 0 to 9, allowing you to fly multiple transmitters at the
1916 same time while keeping the identify of each one separate in
1917 the receiver. By default, the SSID is set to the last digit of
1918 the device serial number.</p><p>The APRS packet format includes a comment field that
1919 can have arbitrary text in it. AltOS uses this to send
1920 status information as shown in the following table.</p><div class="table"><a id="idm1989"></a><p class="title"><strong>Table A.1. Altus Metrum APRS Comments</strong></p><div class="table-contents"><table class="table" summary="Altus Metrum APRS Comments" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Field </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Example </th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>L</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>GPS Status U for unlocked, L for locked</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>6</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Number of Satellites in View</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B4.0</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Altimeter Battery Voltage</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>4</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>A3.7</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee Igniter Voltage</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>5</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>M3.7</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Main Igniter Voltage</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>6</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1286</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Device Serial Number</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>4</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>1286</p></td><td style="" align="left" valign="top"><p>Device Serial Number</p></td></tr></tbody></table></div></div><br class="table-break" /><p>Here’s an example of an APRS comment showing GPS lock with 6
1921 satellites in view, a primary battery at 4.0V, and
1922 apogee and main igniters both at 3.7V from device 1286.</p><pre class="literallayout">L6 B4.0 A3.7 M3.7 1286</pre><p>Here’s an example of an APRS comment showing GPS lock with 6
1923 satellites in view and a primary battery at 4.0V from device 1876.</p><pre class="literallayout">L6 B4.0 1876</pre><p>Make sure your primary battery is above 3.8V
1924 any connected igniters are above 3.5V
1925 and GPS is locked with at least 5 or 6 satellites in
1926 view before flying. If GPS is switching between L and
1927 U regularly, then it doesn’t have a good lock and you
1928 should wait until it becomes stable.</p><p>If the GPS receiver loses lock, the APRS data
1929 transmitted will contain the last position for which
1930 GPS lock was available. You can tell that this has
1931 happened by noticing that the GPS status character
1932 switches from <span class="emphasis"><em>L</em></span> to <span class="emphasis"><em>U</em></span>. Before GPS has locked, APRS
1933 will transmit zero for latitude, longitude and
1934 altitude.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_configurable_parameters"></a>A.7. Configurable Parameters</h2></div></div></div><p>Configuring an Altus Metrum altimeter for flight is
1935 very simple. Even on our baro-only TeleMini and
1936 EasyMini boards, the use of a Kalman filter means
1937 there is no need to set a “mach delay”. All of the
1938 configurable parameters can be set using AltosUI. Read
1939 <a class="xref" href="#_configure_altimeter" title="11.6. Configure Altimeter">Section 11.6, “Configure Altimeter”</a> for more information.</p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_handling_precautions"></a>Appendix B. Handling Precautions</h1></div></div></div><p>All Altus Metrum products are sophisticated electronic devices.
1940 When handled gently and properly installed in an air-frame, they
1941 will deliver impressive results. However, as with all electronic
1942 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
1943 extraordinary power density. This is great because we can fly with
1944 much less battery mass than if we used alkaline batteries or previous
1945 generation rechargeable batteries… but if they are punctured
1946 or their leads are allowed to short, they can and will release their
1947 energy very rapidly!
1948 Thus we recommend that you take some care when handling our batteries
1949 and consider giving them some extra protection in your air-frame. We
1950 often wrap them in suitable scraps of closed-cell packing foam before
1951 strapping them down, for example.</p></div><p>The barometric sensors used on all of our flight computers are
1952 sensitive to sunlight. In normal mounting situations, the baro sensor
1953 and all of the other surface mount components
1954 are “down” towards whatever the underlying mounting surface is, so
1955 this is not normally a problem. Please consider this when designing an
1956 installation in an air-frame with a see-through plastic payload bay. It
1957 is particularly important to
1958 consider this with TeleMini v1.0, both because the baro sensor is on the
1959 “top” of the board, and because many model rockets with payload bays
1960 use clear plastic for the payload bay! Replacing these with an opaque
1961 cardboard tube, painting them, or wrapping them with a layer of masking
1962 tape are all reasonable approaches to keep the sensor out of direct
1963 sunlight.</p><p>The barometric sensor sampling port must be able to “breathe”,
1964 both by not being covered by foam or tape or other materials that might
1965 directly block the hole on the top of the sensor, and also by having a
1966 suitable static vent to outside air.</p><p>As with all other rocketry electronics, Altus Metrum altimeters must
1967 be protected from exposure to corrosive motor exhaust and ejection
1968 charge gasses.</p></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_updating_device_firmware"></a>Appendix C. Updating Device Firmware</h1></div></div></div><p>TeleMega, TeleMetrum v2, EasyMega, EasyMini and TeleDongle v3
1970 programmed directly over their USB connectors (self
1972 TeleMetrum v1, TeleMini and TeleDongle v0.2 are
1973 all programmed by using another device as a programmer (pair
1974 programming). It’s important to recognize which kind of devices
1975 you have before trying to reprogram them.</p><p>You may wish to begin by ensuring you have current firmware
1976 images. These are distributed as part of the AltOS software
1977 bundle that also includes the AltosUI ground station program.
1978 Newer ground station versions typically work fine with older
1979 firmware versions, so you don’t need to update your devices
1980 just to try out new software features. You can always
1981 download the most recent version from
1982 <a class="ulink" href="http://www.altusmetrum.org/AltOS/" target="_top">http://www.altusmetrum.org/AltOS/</a></p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_updating_telemega_telemetrum_v2_easymega_easymini_or_teledongle_v3_firmware"></a>C.1. Updating TeleMega, TeleMetrum v2, EasyMega, EasyMini or TeleDongle v3 Firmware</h2></div></div></div><p>Self-programmable devices are reprogrammed by
1983 connecting them to your computer over USB.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
1984 Attach a battery if necessary and power switch to
1985 the target device. Power up the device.
1986 </li><li class="listitem">
1987 Using a Micro USB cable, connect the target device to your
1988 computer’s USB socket.
1989 </li><li class="listitem">
1990 Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from the File menu.
1991 </li><li class="listitem">
1992 Select the target device in the Device Selection dialog.
1993 </li><li class="listitem">
1994 Select the image you want to flash to the device,
1995 which should have a name in the form
1996 <product>-v<product-version>-<software-version>.ihx,
1997 such as EasyMini-v1.0-1.6.0.ihx.
1998 </li><li class="listitem">
1999 Make sure the configuration parameters are
2000 reasonable looking. If the serial number and/or RF
2001 configuration values aren’t right, you’ll need to
2003 </li><li class="listitem">
2004 Hit the <span class="emphasis"><em>OK</em></span> button and the software should proceed
2005 to flash the device with new firmware, showing a
2007 </li><li class="listitem">
2008 Verify that the device is working by using the
2009 <span class="emphasis"><em>Configure Altimeter</em></span> or <span class="emphasis"><em>Configure Groundstation</em></span>
2010 item to check over the configuration.
2011 </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
2012 unable to boot. Not to worry, you can force the device to
2013 start the boot loader instead, which will let you try to
2014 flash the device again.</p><p>On each device, connecting two pins from one of the exposed
2015 connectors will force the boot loader to start, even if the
2016 regular operating system has been corrupted in some way.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
2019 Connect pin 6 and pin 1 of the companion
2020 connector. Pin 1 can be identified by the square pad
2021 around it, and then the pins could sequentially across
2022 the board. Be very careful to <span class="strong"><strong>not</strong></span> short pin 8 to
2023 anything as that is connected directly to the
2024 battery. Pin 7 carries 3.3V and the board will crash
2025 if that is connected to pin 1, but shouldn’t damage
2027 </dd><dt><span class="term">
2030 Connect pin 6 and pin 1 of the companion
2031 connector. Pin 1 can be identified by the square pad
2032 around it, and then the pins could sequentially across
2033 the board. Be very careful to <span class="strong"><strong>not</strong></span> short pin 8 to
2034 anything as that is connected directly to the
2035 battery. Pin 7 carries 3.3V and the board will crash
2036 if that is connected to pin 1, but shouldn’t damage
2038 </dd><dt><span class="term">
2041 Connect pin 6 and pin 1 of the companion
2042 connector. Pin 1 can be identified by the square pad
2043 around it, and then the pins could sequentially across
2044 the board. Be very careful to <span class="strong"><strong>not</strong></span> short pin 8 to
2045 anything as that is connected directly to the
2046 battery. Pin 7 carries 3.3V and the board will crash
2047 if that is connected to pin 1, but shouldn’t damage
2049 </dd><dt><span class="term">
2052 Connect pin 6 and pin 1 of the debug connector, which
2053 is the six holes next to the beeper. Pin 1 can be
2054 identified by the square pad around it, and then the
2055 pins could sequentially across the board, making Pin 6
2056 the one on the other end of the row.
2057 </dd><dt><span class="term">
2060 Connect pin 32 on the CPU to ground. Pin 32 is closest
2061 to the USB wires on the row of pins towards the center
2062 of the board. Ground is available on the capacitor
2063 next to it, on the end towards the USB wires.
2064 </dd></dl></div><p>Once you’ve located the right pins:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
2065 Turn the altimeter power off.
2066 </li><li class="listitem">
2068 </li><li class="listitem">
2069 Connect the indicated terminals together with a
2070 short piece of wire. Take care not to accidentally
2071 connect anything else.
2072 </li><li class="listitem">
2074 </li><li class="listitem">
2075 Turn the board power on.
2076 </li></ol></div><p>The board should now be visible over USB as
2077 <span class="emphasis"><em>AltosFlash</em></span> and be ready to receive firmware. Once
2078 the board has been powered up, you can remove the
2079 piece of wire.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_pair_programming"></a>C.2. Pair Programming</h2></div></div></div><p>The big concept to understand is that you have to use
2080 a TeleMetrum v1.0, TeleBT v1.0 or TeleDongle v0.2 as a
2081 programmer to update a pair programmed device. Due to
2082 limited memory resources in the cc1111, we don’t
2083 support programming directly over USB for these
2084 devices.</p><p>If you need to update the firmware on a TeleDongle
2085 v0.2, we recommend updating the altimeter first,
2086 before updating TeleDongle. However, note that
2087 TeleDongle rarely need to be updated. Any firmware
2088 version 1.0.1 or later will work, version 1.2.1 may
2089 have improved receiver performance slightly.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_updating_telemetrum_v1_x_firmware"></a>C.2.1. Updating TeleMetrum v1.x Firmware</h3></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
2090 Find the <span class="emphasis"><em>programming cable</em></span> that you got as
2091 part of the starter kit, that has a red
2092 8-pin MicroMaTch connector on one end and a
2093 red 4-pin MicroMaTch connector on the other
2095 </li><li class="listitem">
2096 Take the 2 screws out of the TeleDongle v0.2
2097 or TeleBT v1.0 case to get access to the
2099 </li><li class="listitem">
2100 Plug the 8-pin end of the programming cable
2101 to the matching connector on the TeleDongle
2102 v0.2 or TeleBT v1.0, and the 4-pin end to
2103 the matching connector on the TeleMetrum.
2104 Note that each MicroMaTch connector has an
2105 alignment pin that goes through a hole in
2106 the PC board when you have the cable
2108 </li><li class="listitem">
2109 Attach a battery to the TeleMetrum board.
2110 </li><li class="listitem">
2111 Plug the TeleDongle v0.2 or TeleBT v1.0 into
2112 your computer’s USB port, and power up the
2114 </li><li class="listitem">
2115 Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from
2117 </li><li class="listitem">
2118 Pick the TeleDongle v0.2 or TeleBT v1.0
2119 device from the list, identifying it as the
2121 </li><li class="listitem">
2122 Select the image you want put on the
2123 TeleMetrum, which should have a name in the
2124 form telemetrum-v1.2-1.0.0.ihx. It should
2125 be visible in the default directory, if not
2126 you may have to poke around your system to
2128 </li><li class="listitem">
2129 Make sure the configuration parameters are
2130 reasonable looking. If the serial number
2131 and/or RF configuration values aren’t right,
2132 you’ll need to change them.
2133 </li><li class="listitem">
2134 Hit the <span class="emphasis"><em>OK</em></span> button and the software should
2135 proceed to flash the TeleMetrum with new
2136 firmware, showing a progress bar.
2137 </li><li class="listitem">
2138 Confirm that the TeleMetrum board seems to
2139 have updated OK, which you can do by
2140 plugging in to it over USB and using a
2141 terminal program to connect to the board and
2142 issue the <span class="emphasis"><em>v</em></span> command to check the version,
2144 </li></ol></div><p>If something goes wrong, give it another try.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_updating_telemini_firmware"></a>C.2.2. Updating TeleMini Firmware</h3></div></div></div><p>You’ll need a special <span class="emphasis"><em>programming cable</em></span> to
2145 reprogram the TeleMini. You can make your own
2146 using an 8-pin MicroMaTch connector on one end
2147 and a set of four pins on the other.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
2148 Take the 2 screws out of the TeleDongle v0.2
2149 or TeleBT v1.0 case to get access to the
2151 </li><li class="listitem">
2152 Plug the 8-pin end of the programming cable
2153 to the matching connector on the TeleDongle
2154 v0.2 or TeleBT v1.0, and the 4-pins into the
2155 holes in the TeleMini circuit board. Note
2156 that the MicroMaTch connector has an
2157 alignment pin that goes through a hole in
2158 the PC board when you have the cable
2159 oriented correctly, and that pin 1 on the
2160 TeleMini board is marked with a square pad
2161 while the other pins have round pads.
2162 </li><li class="listitem">
2163 Attach a battery to the TeleMini board.
2164 </li><li class="listitem">
2165 Plug the TeleDongle v0.2 or TeleBT v1.0 into
2166 your computer’s USB port, and power up the
2168 </li><li class="listitem">
2169 Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from
2171 </li><li class="listitem">
2172 Pick the TeleDongle v0.2 or TeleBT v1.0
2173 device from the list, identifying it as the
2175 </li><li class="listitem">
2176 Select the image you want put on the
2177 TeleMini, which should have a name in the
2178 form telemini-v1.0-1.0.0.ihx. It should be
2179 visible in the default directory, if not you
2180 may have to poke around your system to find
2182 </li><li class="listitem">
2183 Make sure the configuration parameters are
2184 reasonable looking. If the serial number
2185 and/or RF configuration values aren’t right,
2186 you’ll need to change them.
2187 </li><li class="listitem">
2188 Hit the <span class="emphasis"><em>OK</em></span> button and the software should
2189 proceed to flash the TeleMini with new
2190 firmware, showing a progress bar.
2191 </li><li class="listitem">
2192 Confirm that the TeleMini board seems to
2193 have updated OK, which you can do by
2194 configuring it over the radio link through
2195 the TeleDongle, or letting it come up in
2196 “flight” mode and listening for telemetry.
2197 </li></ol></div><p>If something goes wrong, give it another try.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_updating_teledongle_v0_2_firmware"></a>C.2.3. Updating TeleDongle v0.2 Firmware</h3></div></div></div><p>Updating TeleDongle v0.2 firmware is just like
2198 updating TeleMetrum v1.x or TeleMini firmware, but you
2199 use either a TeleMetrum v1.x, TeleDongle v0.2 or
2200 TeleBT v1.0 as the programmer.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
2201 Find the <span class="emphasis"><em>programming cable</em></span> that you got as part of
2202 the starter kit, that has a red 8-pin MicroMaTch
2203 connector on one end and a red 4-pin MicroMaTch
2204 connector on the other end.
2205 </li><li class="listitem">
2206 Find the USB cable that you got as part of the
2207 starter kit, and plug the “mini” end in to the
2208 mating connector on TeleMetrum v1.x, TeleDongle v0.2
2210 </li><li class="listitem">
2211 Take the 2 screws out of the TeleDongle v0.2 or
2212 TeleBT v1.0 case to get access to the circuit board.
2213 </li><li class="listitem">
2214 Plug the 8-pin end of the programming cable to the
2215 matching connector on the programmer, and the 4-pin
2216 end to the matching connector on the TeleDongle
2217 v0.2. Note that each MicroMaTch connector has an
2218 alignment pin that goes through a hole in the PC
2219 board when you have the cable oriented correctly.
2220 </li><li class="listitem">
2221 Attach a battery to the TeleMetrum v1.x board if
2223 </li><li class="listitem">
2224 Plug both the programmer and the TeleDongle into
2225 your computer’s USB ports, and power up the
2227 </li><li class="listitem">
2228 Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from the File
2230 </li><li class="listitem">
2231 Pick the programmer device from the list,
2232 identifying it as the programming device.
2233 </li><li class="listitem">
2234 Select the image you want put on the TeleDongle
2235 v0.2, which should have a name in the form
2236 teledongle-v0.2-1.0.0.ihx. It should be visible in
2237 the default directory, if not you may have to poke
2238 around your system to find it.
2239 </li><li class="listitem">
2240 Make sure the configuration parameters are
2241 reasonable looking. If the serial number and/or RF
2242 configuration values aren’t right, you’ll need to
2243 change them. The TeleDongle v0.2 serial number is
2244 on the “bottom” of the circuit board, and can
2245 usually be read through the translucent blue plastic
2246 case without needing to remove the board from the
2248 </li><li class="listitem">
2249 Hit the <span class="emphasis"><em>OK</em></span> button and the software should proceed
2250 to flash the TeleDongle v0.2 with new firmware,
2251 showing a progress bar.
2252 </li><li class="listitem">
2253 Confirm that the TeleDongle v0.2 board seems to have
2254 updated OK, which you can do by plugging in to it
2255 over USB and using a terminal program to connect to
2256 the board and issue the <span class="emphasis"><em>v</em></span> command to check the
2257 version, etc. Once you’re happy, remove the
2258 programming cable and put the cover back on the
2260 </li></ol></div><p>If something goes wrong, give it another try.</p><p>Be careful removing the programming cable from the
2261 locking 8-pin connector on TeleMetrum. You’ll need a
2262 fingernail or perhaps a thin screwdriver or knife
2263 blade to gently pry the locking ears out slightly to
2264 extract the connector. We used a locking connector on
2265 TeleMetrum to help ensure that the cabling to
2266 companion boards used in a rocket don’t ever come
2267 loose accidentally in flight.</p></div></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_flight_data_recording"></a>Appendix D. Flight Data Recording</h1></div></div></div><p>Each flight computer logs data at 100 samples per second
2268 during ascent and 10 samples per second during
2269 descent, except for TeleMini v1.0, which records ascent at 10 samples
2270 per second and descent at 1 sample per second.
2272 an on-board flash memory part, which can be partitioned into
2273 several equal-sized blocks, one for each flight.</p><div class="table"><a id="idm2240"></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; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1MB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>20</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v1.1 v1.2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2MB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>40</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v2.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>16</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>80</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMini v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>5kB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>4</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>EasyMini</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>16</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1MB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>10</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMega</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>32</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>40</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>EasyMega</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>32</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="" align="left" valign="top"><p>40</p></td></tr></tbody></table></div></div><br class="table-break" /><p>The on-board flash is partitioned into separate flight logs,
2274 each of a fixed maximum size. Increase the maximum size of
2275 each log and you reduce the number of flights that can be
2276 stored. Decrease the size and you can store more flights.</p><p>Configuration data is also stored in the flash memory on
2281 of flash space. This configuration space is not available
2282 for storing flight log data.</p><p>TeleMetrum v2.0, TeleMega and EasyMega
2283 store configuration data in a bit of eeprom available within
2284 the processor chip, leaving that space available in flash for
2285 more flight data.</p><p>To compute the amount of space needed for a single flight, you
2286 can multiply the expected ascent time (in seconds) by 100
2287 times bytes-per-sample, multiply the expected descent time (in
2288 seconds) by 10 times the bytes per sample and add the two
2289 together. That will slightly under-estimate the storage (in
2290 bytes) needed for the flight.
2291 For instance, a TeleMetrum v2.0 flight spending
2292 20 seconds in ascent and 150 seconds in descent will take
2293 about (20 * 1600) + (150 * 160) = 56000 bytes of storage. You
2294 could store dozens of these flights in the on-board flash.</p><p>The default size allows for several flights on each flight
2295 computer, except for TeleMini v1.0, which
2296 only holds data for a single flight.
2297 You can adjust the size.</p><p>Altus Metrum flight computers will not overwrite existing
2298 flight data, so be sure to download flight data and erase it
2299 from the flight computer before it fills up. The flight
2300 computer will still successfully control the flight even if it
2301 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
2302 production and retired.</p><div class="table"><a id="idm2326"></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>TeleMetrum v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MP3H6115 10km (33k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MMA2202 50g</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>SkyTraq</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>10mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v1.1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MP3H6115 10km (33k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MMA2202 50g</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>SkyTraq</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>10mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v1.2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MP3H6115 10km (33k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>ADXL78 70g</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>SkyTraq</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>10mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum v2.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MS5607 30km (100k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MMA6555 102g</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>uBlox Max-7Q</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>40mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMini v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MP3H6115 10km (33k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>5kB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>10mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>EasyMini v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MS5607 30km (100k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7-12V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMega v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MS5607 30km (100k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MMA6555 102g</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>uBlox Max-7Q</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MPU6000 HMC5883</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>40mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMega v2.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MS5607 30km (100k')</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MMA6555 102g</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>uBlox Max-7Q</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>MPU6000 HMC5883</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>40mW</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3.7V</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>EasyMega v1.0</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>MS5607 30km (100k')</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>MMA6555 102g</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>MPU6000 HMC5883</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>8MB</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>-</p></td><td style="" align="left" valign="top"><p>3.7V</p></td></tr></tbody></table></div></div><br class="table-break" /><p></p><div class="table"><a id="idm2502"></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; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMetrum</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Antenna Debug Companion USB Battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro Switch</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1 inch (2.54cm)</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2 ¾ inch (6.99cm)</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>29mm coupler</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMini v1.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Antenna Debug Battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>½ inch (1.27cm)</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1½ inch (3.81cm)</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>18mm coupler</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMini v2.0</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Antenna Debug USB Battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro Battery Switch</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>0.8 inch (2.03cm)</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1½ inch (3.81cm)</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>24mm coupler</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>EasyMini</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Debug USB Battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro Battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>0.8 inch (2.03cm)</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1½ inch (3.81cm)</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>24mm coupler</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>TeleMega</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Antenna Debug Companion USB Battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro Pyro A-D Switch Pyro battery</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1¼ inch (3.18cm)</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3¼ inch (8.26cm)</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>38mm coupler</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>EasyMega</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Debug Companion USB Battery</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>Apogee pyro Main pyro Pyro A-D Switch Pyro battery</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>1¼ inch (3.18cm)</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>2¼ inch (5.62cm)</p></td><td style="" align="left" valign="top"><p>38mm coupler</p></td></tr></tbody></table></div></div><br class="table-break" /></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_release_notes"></a>Appendix F. Release Notes</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6_5"></a>F.1. 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
2303 the device would often stop logging data and transmitting
2304 telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum
2305 v2.0 users should update their flight firmware.</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">
2306 Fix STM32L SPI driver to prevent lock-up in the logging or
2307 radio code, either of which could stop data logging and
2308 telemetry. Found and characterized by Chuck Haskin, who also
2309 tested the new firmware before release.
2310 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_telegps_and_altosdroid_applications"></a>F.1.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">
2311 Deliver firmward for TeleMega v2.0 and TeleBT v3.0 with
2313 </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.2. Release Notes for Version 1.6.4</h2></div></div></div><p>Version 1.6.4 fixes a bluetooth communication problem with
2314 TeleBT v1.0 devices, along with some altosui and altosdroid
2315 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_2"></a>F.2.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2316 Fix hardware flow control on TeleBT v1.0. Hardware RTS/CTS
2317 doesn’t seem to work, switch from using the hardware to
2318 driving these pins with software.
2319 </li><li class="listitem">
2320 Fix ARM USB drivers to deal with OS restarts. Needed to
2321 reset all USB-related state when the USB bus is reset. These
2322 fixes affect all STM32L, STM32F0 and LPC11U14 based devices.
2323 </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.2.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">
2324 Automatically switch from meters or feet to kilometers or
2325 miles for distance units.
2326 </li><li class="listitem">
2327 Add Monitor Idle mode to TeleGPS application.
2328 </li></ul></div><p>AltosUI, TeleGPS and AltosDroid Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2329 Abort map preloading when the preload map dialog is closed.
2330 </li><li class="listitem">
2331 In AltosDroid, Don’t reconnect to last device if the user
2332 had disconnected it the last time the application was
2334 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation"></a>F.2.3. Documentation</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2335 Mention TeleMega v2.0 in hardware specs table.
2336 </li><li class="listitem">
2337 Document TeleGPS RF output in telegps manual.
2338 </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_3"></a>F.3. 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
2339 for our host software on desktops, laptops an android devices
2340 along with BlueTooth support for Windows.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_3"></a>F.3.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2341 Fix hardware flow control on TeleBT v3.0. RTS/CTS is
2342 wired backwards on this board, switch from using the
2343 hardware to driving these pins with software.
2344 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications"></a>F.3.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2345 Add BlueTooth support for Windows operating system. This
2346 supports connections to TeleBT over BlueTooth rather than
2348 </li></ul></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2349 Change Java detection and install on Windows. Detection is
2350 now done by looking for the <span class="emphasis"><em>javaw.exe</em></span> program, and
2351 installation by opening a browser on the java.com web site.
2352 </li><li class="listitem">
2353 Delay polling while the Fire Igniters is visible to allow
2354 for TeleMega to report back complete status over the radio.
2355 </li><li class="listitem">
2356 Disallow changing RF calibration numbers in the
2357 configuration UI. There’s no good reason to change this from
2358 the field, and recovering is really hard if you haven’t
2359 written down the right number.
2360 </li><li class="listitem">
2361 Fix USB device discovery on Mac OS X El Capitan. This makes
2362 the connected Altus Metrum USB devices appear again.
2363 </li><li class="listitem">
2364 Fix acceleration data presented in MonitorIdle mode for
2365 TeleMetrum v2.0 flight computers.
2366 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosdroid_2"></a>F.3.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">
2367 Monitor Idle mode. Check state of flight computer while in
2368 idle mode over the radio link
2369 </li><li class="listitem">
2370 Fire Igniters. Remotely fire ignires for recovery system
2372 </li><li class="listitem">
2373 Remote reboot. Cause the flight computer to reboot over the
2374 radio link. This provides a method for switching the flight
2375 computer from idle to flight mode without needing to reach
2377 </li><li class="listitem">
2378 Configurable frequency menu. Change the set of available
2379 frequencies and provide more descriptive names.
2380 </li></ul></div><p>AltosDroid bug fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2381 Don’t set target location if GPS hasn’t locked yet.
2382 </li><li class="listitem">
2383 Fix saving target states so they can be reloaded when the
2384 application restarts. When the application is shut down and
2385 restarted, all previous target state information will be
2386 restored (including GPS position if available).
2387 </li><li class="listitem">
2388 Fix crash on some Android devices for offline maps when
2389 changing the map scale or location.
2390 </li><li class="listitem">
2391 Don’t require USB OTG support. This kept the latest
2392 AltosDroid from being offered on devices without USB device
2393 support, although it can work without that just fine using
2395 </li><li class="listitem">
2396 Don’t require bluetooth to be enabled. This allows the
2397 application to operate with USB devices or just show old
2398 data without turning on the bluetooth radio.
2399 </li><li class="listitem">
2400 Recover old tracker positions when restarting
2401 application. This finally allows you to safely stop and
2402 restart the application without losing the last known
2403 location of any tracker.
2404 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation_2"></a>F.3.4. Documentation</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2405 Document TeleMega and EasyMega additional pyro channel
2406 continuity audio alert pattern.
2407 </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.4. Release Notes for Version 1.6.2</h2></div></div></div><p>Version 1.6.2 includes support for our updated TeleMega v2.0
2408 product and bug fixes in in the flight software for all our boards
2409 and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_4"></a>F.4.1. AltOS</h3></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2410 Add support for TeleMega v2.0 boards.
2411 </li><li class="listitem">
2412 Add PWM servo driver. There’s no higher level code using
2413 this yet, but the driver allows testing of the TeleMega v2.0
2414 servo output connector.
2415 </li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2416 Slow down telemetry packets to allow receiver to keep
2418 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_2"></a>F.4.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">
2419 Fix post-flight orientation computation when processing
2420 TeleMega and EasyMega eeprom data files.
2421 </li><li class="listitem">
2422 Capture complete eeprom data even when there are invalid
2423 entries in the data. This keeps reading eeprom contents and
2424 writing the associated .eeprom file when an error is detected.
2425 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation_3"></a>F.4.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">
2426 HTML versions now have a table of contents on the left side.
2427 </li><li class="listitem">
2428 EasyMini now has its own shorter manual.
2429 </li><li class="listitem">
2430 Provide links between sections in each document.
2431 </li><li class="listitem">
2432 Lots of minor rewriting and restructuring to avoid
2433 duplication of information
2434 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6_1"></a>F.5. Release Notes for Version 1.6.1</h2></div></div></div><p>Version 1.6.1 includes support for our updated TeleBT v3.0
2435 product and bug fixes in in the flight software for all our boards
2436 and ground station interfaces.</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">
2437 Add support for TeleBT v3.0 boards.
2438 </li><li class="listitem">
2439 Add support for uncompressed APRS data, providing support
2440 for older APRS receivers. Uncompressed APRS data is less
2441 precise, takes more bandwidth and doesn’t have integrated
2443 </li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2444 Make TeleDongle and TeleBT more tolerant of data rate
2445 variations from transmitting devices.
2446 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_3"></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">
2447 Add map to Monitor Idle display. It’s nice to be able to
2448 verify that maps are working, instead of needing to use
2450 </li></ul></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2451 Fix frequency configuration to round values instead of
2452 truncate them, avoiding a common 1kHz error in the setting.
2453 </li><li class="listitem">
2454 Turn the Windows stub into a more useful program that can
2455 launch the application with parameters so that file manager
2456 icons work more reliably.
2457 </li><li class="listitem">
2458 Force KML export to use a C locale so that numbers are
2459 formatted with <span class="emphasis"><em>.</em></span> instead of <span class="emphasis"><em>,</em></span> for a decimal separator in
2461 </li><li class="listitem">
2462 Preload map tiles based on distance rather than number of
2463 tiles; this means you get the same resolution covering the
2464 entire area, rather than having high resolution near the
2465 center and low resolution further away.
2466 </li><li class="listitem">
2467 Allow configuration of frequency and callsign in Monitor
2469 </li><li class="listitem">
2470 Fix layout weirdness when resizing windows on
2471 Windows. Windows shouldn’t have giant blank spaces around
2472 the useful content anymore.
2473 </li><li class="listitem">
2474 Fix layout weirdness when resizing windows on
2475 Windows. Windows shouldn’t have giant blank spaces around
2476 the useful content anymore.
2477 </li><li class="listitem">
2478 Use a longer filter for descent speed values. This should
2479 provide something more useful on the display, although it
2480 will take longer to respond to changes now.
2481 </li><li class="listitem">
2482 Make Replay Flight run in realtime again. It had been set to
2483 run at 10x speed by mistake.
2484 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosdroid_3"></a>F.5.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">
2485 Add offline map support using mapping code from AltosUI.
2486 </li><li class="listitem">
2487 Support TeleDongle (and TeleBT via USB) on devices
2488 supporting USB On-The-Go.
2489 </li><li class="listitem">
2490 Display additional TeleMega pyro channel status in Pad tab.
2491 </li><li class="listitem">
2492 Switch between metric and imperial units.
2493 </li><li class="listitem">
2494 Monitor TeleBT battery voltage.
2495 </li><li class="listitem">
2496 Track multiple devices at the same time, selecting between
2497 them with a menu or using the map.
2498 </li><li class="listitem">
2499 Add hybrid, satellite and terrain map types.
2500 </li></ul></div><p>AltosDroid Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2501 Use standard Android display conventions so that a menu
2502 button is available in the application title bar.
2503 </li><li class="listitem">
2504 Adjust layout to work on large and small screens; shrinking
2505 the go/no-go lights in smaller environments to try and make
2507 </li><li class="listitem">
2508 Make voice announcements depend on current tab.
2509 </li><li class="listitem">
2510 Compute adjustment to current travel direction while in
2511 motion towards rocket.
2512 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6"></a>F.6. Release Notes for Version 1.6</h2></div></div></div><p>Version 1.6 includes support for our updated TeleDongle v3.0
2513 product and bug fixes in in the flight software for all our boards
2514 and ground station interfaces.</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 New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2515 Add support for TeleDongle v3.0 boards.
2516 </li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2517 Don’t beep out the continuity twice by accident in idle mode.
2518 If the battery voltage report takes longer than the initialiation
2519 sequence, the igniter continuity would get reported twice.
2520 </li><li class="listitem">
2521 Record all 32 bits of gyro calibration data in TeleMega and
2522 EasyMega log files. This fixes computation of the gyro rates
2524 </li><li class="listitem">
2525 Change TeleDongle LED usage. Green LED flashes when valid
2526 packet is received. Red LED flashes when invalid packet is
2528 </li><li class="listitem">
2529 Replace LPC11U14 SPI driver with non-interrupt version. The
2530 interrupt code would occasionally wedge on long transfers
2531 if interrupts were blocked for too long. This affects all
2532 released TeleGPS products; if you have a TeleGPS device,
2533 you’ll want to reflash the firmware.
2534 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_4"></a>F.6.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">
2535 Compute tilt angle from TeleMega and EasyMega log
2536 files. This duplicates the quaternion-based angle tracking
2537 code from the flight firmware inside the ground station
2538 software so that post-flight analysis can include evaluation
2540 </li><li class="listitem">
2541 Shows the tool button window when starting with a data file
2542 specified. This means that opening a data file from the file
2543 manager will now bring up the main window to let you operate
2544 the whole application.
2545 </li></ul></div><p>AltosUI Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2546 Show the <span class="emphasis"><em>Connecting</em></span> dialog when using Monitor Idle. Lets
2547 you cancel the Monitor Idle startup when connecting over the
2549 </li><li class="listitem">
2550 Make <span class="emphasis"><em>Monitor Idle</em></span> work for TeleGPS devices when connected
2551 over USB. It’s nice for testing without needing to broadcast
2553 </li><li class="listitem">
2554 Use different Windows API to discover USB devices. This
2555 works better on my Windows 7 box, and will be used if the
2556 older API fails to provide the necessary information.
2557 </li><li class="listitem">
2558 Look in more places in the registry to try and identify the
2559 installed Java version on Windows. If you install the
2560 default 32-bit version of Windows on a 64-bit OS, the Java
2561 registry information is hiding \SOFTWARE\Wow6432Node for
2563 </li><li class="listitem">
2564 Fix file association on Windows by searching for the
2565 javaw.exe program instead of assuming it is in
2566 %SYSTEMROOT%. This makes double-clicking on Altus Metrum
2567 data files in the file manager work correctly.
2568 </li><li class="listitem">
2569 When replaying a file, put <span class="emphasis"><em>done</em></span> in the Age field when we
2570 reach the end of the file, instead of continuing to count forever.
2571 </li><li class="listitem">
2572 In the Scan Channels code, wait for five seconds if we see
2573 any packet. This is needed because AltOS now sends the
2574 callsign, serial number and flight number only once every
2575 five seconds these days.
2576 </li><li class="listitem">
2577 In the Scan Channels code, reset pending flight state
2578 information each time we change channels. This avoids having
2579 flight computers appear on multiple frequencies by accident.
2580 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_5"></a>F.7. Release Notes for Version 1.5</h2></div></div></div><p>Version 1.5 is a major release. It includes support for our new
2581 EasyMega product, new features and bug fixes in in the flight
2582 software for all our boards and the AltosUI ground station</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_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">
2583 Add support for EasyMega boards.
2584 </li><li class="listitem">
2585 Make the APRS SSID be configurable. This lets you track
2586 different rockets on the same receiver without getting
2588 </li><li class="listitem">
2589 Report extra pyro channel continuity state on EasyMega and
2590 TeleMega via the beeper. This lets you easily verify flight
2591 readiness on these boards after powering up the electronics
2593 </li><li class="listitem">
2594 Add lower telemetry data rates (2400 and 9600 bps) to
2595 increase telemetry radio range. This reduces the amount of
2596 data received as well as increasing battery consumption in
2598 </li><li class="listitem">
2599 Change TeleGPS to have only a single log, and append new
2600 data to it rather than using seperate per-flight logs. This
2601 avoids accidentally filling up log storage by turning
2602 TeleGPS on/off several times.
2603 </li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2604 Increase the maximum range for altitude values from +/-32767m
2605 to +/-2147483647m, allowing the flight computers to function
2606 correctly above the 32km level.
2607 </li><li class="listitem">
2608 Continuously test pyro firing conditions during delay stage,
2609 inhibiting the pyro channel if the test fails. This prevents
2610 firing pyro charges where the conditions were good before
2611 the delay, but become bad before the delay expires.
2612 </li><li class="listitem">
2613 Allow negative numbers in pyro configuration values. This
2614 lets you specify things like descending speed or
2616 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_5"></a>F.7.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">
2617 Support telemetry baud rate selection. Adds menus to
2618 the flight monitoring and configuration for baud rate
2620 </li><li class="listitem">
2621 Support APRS SSID configuration.
2622 </li><li class="listitem">
2623 Integrate with file managers. This provides icons for all of
2624 our file types and associates our application with the files
2625 so that using a file manager to open a AltOS data file
2626 results in launching our application.
2627 </li></ul></div><p>AltosUI Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2628 Make the <span class="emphasis"><em>Graph</em></span> button on the landed tab work again.
2629 </li><li class="listitem">
2630 Make tests for Java on Windows a bit smarter, and also
2631 provide the user with the option to skip installing Java for
2632 cases where we just can’t figure out what version is installed.
2633 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_4_2"></a>F.8. Release Notes for Version 1.4.2</h2></div></div></div><p>Version 1.4.2 is a minor release. It fixes Java-related install issues on
2634 Windows</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_6"></a>F.8.1. AltosUI and TeleGPS Applications</h3></div></div></div><p>Windows Install Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2635 Checks for Java installation data in more registry locations.
2636 </li><li class="listitem">
2637 Allows user to bypass Java installation in case the
2639 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_4_1"></a>F.9. Release Notes for Version 1.4.1</h2></div></div></div><p>Version 1.4.1 is a minor release. It fixes install issues on
2640 Windows and provides the missing TeleMetrum V2.0 firmware. There
2641 aren’t any changes to the firmware or host applications at
2642 all. All Windows users will want to upgrade to get the signed
2643 driver, but Mac and Linux users who do not need the TeleMetrum
2644 V2.0 firmware image will not need to upgrade.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_7"></a>F.9.1. AltosUI and TeleGPS Applications:</h3></div></div></div><p>Windows Install Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2645 Provide signed Windows driver files. This should avoid any need to
2646 disable driver signature checking on Windows 7 or 8.
2647 </li><li class="listitem">
2648 Fix Java version detection and download. Previously, the
2649 installer would only look for Java 6 or 7 and insist on
2650 downloading its own Java bits if there was something else
2651 installed. Furthermore, the 64-bit Java link provided didn’t
2652 work for anyone other than Keith, making it impossible to
2653 install AltOS on any machine with Java SE 8 installed.
2654 </li></ul></div><p>Other Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2655 Include 1.4 firmware for TeleMetrum V2.0. None of the
2656 installers shipped this file. Now it’s included in the AltOS
2657 packages for Linux, Mac and Windows.
2658 </li><li class="listitem">
2659 Include Google Application Key for map downloading. The 1.4
2660 release didn’t have this key in the released version of the
2661 software, making map downloading fail for most people.
2662 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_4"></a>F.10. Release Notes for Version 1.4</h2></div></div></div><p>Version 1.4 is a major release. It includes support for our new
2663 TeleGPS product, new features and bug fixes in in the flight
2664 software for all our boards and the AltosUI ground station</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_8"></a>F.10.1. AltOS</h3></div></div></div><p>AltOS new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2665 Add support for TeleGPS boards.
2666 </li><li class="listitem">
2667 Make the beeper tone configurable, making it
2668 possible to distinguish between two Altus Metrum
2669 products in the same ebay.
2670 </li><li class="listitem">
2671 Make the firing time for extra pyro channels
2672 configurable, allowing longer (or shorter) than the
2673 default 50ms. Only relevant for TeleMega at this
2675 </li></ul></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2676 Replace the <span class="emphasis"><em>dit dit dit</em></span> tones at startup with the
2677 current battery voltage, measured in tenths of a
2678 volt. This lets you check the battery voltage
2679 without needing telemetry, which is especially
2681 </li><li class="listitem">
2682 Change state beeping to "Farnsworth spacing", which
2683 means they’re quite a bit faster than before, and so
2684 they take less time to send.
2685 </li><li class="listitem">
2686 Fix bug preventing the selection of the <span class="emphasis"><em>Flight
2687 State After</em></span> mode in pyro configuration.
2688 </li><li class="listitem">
2689 Fix bug where erasing flights would reset the flight
2690 number to 2 on TeleMega and TeleMetrum v2.
2691 </li><li class="listitem">
2692 Fix u-Blox GPS driver to mark course and speed data
2694 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application"></a>F.10.2. AltosUI Application</h3></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2695 Add zooming and new content types (terrain and road
2696 maps) to map view. Change map storage format from
2697 PNG to Jpeg, which saves a huge amount of disk
2698 space. You will need to re-download all of your
2699 pre-loaded map images.
2700 </li><li class="listitem">
2701 Add a distance measuring device to the maps
2702 view. Select this by using any button other than the
2703 left one, or by pressing shift or control on the
2704 keyboard while using the left button.
2705 </li><li class="listitem">
2706 Add new <span class="emphasis"><em>Ignitor</em></span> tab to the flight monitor display
2707 for TeleMega’s extra ignitors.
2708 </li><li class="listitem">
2709 Add additional ignitor firing marks and voltages to
2710 the graph so you can see when the ignitors fired,
2711 along with the ignitor voltages.
2712 </li><li class="listitem">
2713 Add GPS course, ground speed and climb rate as
2714 optional graph elements.
2715 </li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2716 When flashing new firmware, re-try opening the
2717 device as sometimes it takes a while for the
2718 underlying operating system to recognize that the
2719 device has rebooted in preparation for the flashing
2721 </li><li class="listitem">
2722 Hide Tilt Angle in ascent tab for devices that don’t
2724 </li><li class="listitem">
2725 Increase the width of data lines in the graphs to
2726 make them easier to read.
2727 </li><li class="listitem">
2728 Filter out speed and acceleration spikes caused by
2729 ejection charge firing when computing the maximum
2730 values. This provides a more accurate reading of
2732 </li><li class="listitem">
2733 Fix EasyMini voltage displays. Early EasyMini
2734 prototypes used a 3.0V regulator, and AltosUI still
2735 used that value as the basis of the
2736 computation. Production EasyMini boards have always
2737 shipped with a 3.3V regulator. Also, purple EasyMini
2738 boards sensed the battery voltage past the blocking
2739 diode, resulting in a drop of about 150mV from the
2740 true battery voltage. Compensate for that when
2741 displaying the value.
2742 </li><li class="listitem">
2743 Display error message when trying to configure
2744 maximum flight log size while the flight computer
2745 still has flight data stored.
2746 </li><li class="listitem">
2747 Handle TeleMetrum and TeleMini eeprom files
2748 generated with pre-1.0 firmware. Those ancient
2749 versions didn’t report the log format, so just use
2750 the product name instead.
2751 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_telegps_application"></a>F.10.3. TeleGPS Application</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2752 New application designed for use with TeleGPS boards.
2753 </li><li class="listitem">
2754 Shares code with AltosUI, mostly just trimmed down
2755 to focus on TeleGPS-related functions.
2756 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation_4"></a>F.10.4. Documentation</h3></div></div></div><p>Documentation changes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2757 Re-create the drill template images; they should
2758 print correctly from Firefox at least. Ship these as
2759 individual PDF files so they’re easy to print.
2760 </li><li class="listitem">
2761 Add a description of the <span class="emphasis"><em>Apogee Lockout</em></span> setting,
2762 which prevents the apogee charge from firing for a
2763 configurable amount of time after boost.
2764 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_3_2"></a>F.11. Release Notes for Version 1.3.2</h2></div></div></div><p>Version 1.3.2 is a minor release. It includes small bug fixes for
2765 the TeleMega flight software and AltosUI ground station</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_9"></a>F.11.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2766 On TeleMega, limit number of logged GPS status
2767 information to 12 satellites. That’s all there is
2768 room for in the log structure.
2769 </li><li class="listitem">
2770 Improve APRS behavior. Remembers last known GPS
2771 position and keeps sending that if we lose GPS
2772 lock. Marks locked/unlocked by sending L/U in the
2773 APRS comment field along with the number of sats in
2775 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_2"></a>F.11.2. AltosUI Application</h3></div></div></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2776 If the TeleMega flight firmware reports that it has
2777 logged information about more than 12 satellites,
2778 don’t believe it as the log only holds 12 satellite
2780 </li><li class="listitem">
2781 Track the maximum height as computed from GPS
2782 altitude data and report that in the flight summary
2784 </li><li class="listitem">
2785 Use letters (A, B, C, D) for alternate pyro channel
2786 names instead of numbers (0, 1, 2, 3) in the Fire
2788 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_3_1"></a>F.12. Release Notes for Version 1.3.1</h2></div></div></div><p>Version 1.3.1 is a minor release. It improves support for
2789 TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_10"></a>F.12.1. AltOS</h3></div></div></div><p>AltOS new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2790 Improved APRS mode. Now uses compressed position
2791 format for smaller data size, improved precision and
2792 to include altitude data as well as latitude and
2793 longitude. Also added battery and pyro voltage
2794 reports in the APRS comment field so you can confirm
2795 that the unit is ready for launch.
2796 </li></ul></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2797 Improve sensor boot code. If sensors fail to
2798 self-test, the device will still boot up and check
2799 for pad/idle modes. If in idle mode, the device will
2800 warn the user with a distinct beep, if in Pad mode,
2801 the unit will operate as best it can. Also, the
2802 Z-axis accelerometer now uses the factory
2803 calibration values instead of re-calibrating on the
2804 pad each time. This avoids accidental boost detect
2805 when moving the device around while in Pad mode.
2806 </li><li class="listitem">
2807 Fix antenna-down mode accelerometer
2808 configuration. Antenna down mode wasn’t working
2809 because the accelerometer calibration values were
2810 getting re-computed incorrectly in inverted mode.
2811 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_3"></a>F.12.2. AltosUI Application</h3></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2812 Display additional TeleMega sensor values in real
2813 units. Make all of these values available for
2814 plotting. Display TeleMega orientation value in the
2815 Ascent and Table tabs.
2816 </li><li class="listitem">
2817 Support additional TeleMega pyro channels in the
2818 Fire Igniter dialog. This lets you do remote testing
2819 of all of the channels, rather than just Apogee and
2821 </li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2822 Limit data rate when downloading satellite images
2823 from Google to make sure we stay within their limits
2824 so that all of the map tiles download successfully.
2825 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_3"></a>F.13. Release Notes for Version 1.3</h2></div></div></div><p>Version 1.3 is a major release. It adds support for TeleMega,
2826 TeleMetrum v2.0, TeleMini v2.0 and EasyMini.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_11"></a>F.13.1. AltOS</h3></div></div></div><p>AltOS new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2827 Add STM32L processor support. This includes
2828 enhancements to the scheduler to support products
2830 </li><li class="listitem">
2831 Add NXP LPC11U14 processor support.
2832 </li><li class="listitem">
2833 Support additional pyro channels. These are
2834 configurable through the UI to handle air starts,
2835 staging, additional recovery events and external
2836 devices such as cameras.
2837 </li><li class="listitem">
2838 Add 3-axis gyro support for orientation
2839 tracking. This integrates the gyros to compute the
2840 angle from vertical during flight, allowing the
2841 additional pyro events to be controlled by this
2843 </li><li class="listitem">
2844 Many more device drivers, including u-Blox Max 7Q
2845 GPS, Freescale MMA6555 digital single-axis
2846 accelerometer, Invensense MPU6000 3-axis
2847 accelerometer + 3 axis gyro, Honeywell HMC5883
2848 3-axis magnetic sensor and the TI CC1120 and CC115L
2849 digital FM transceivers
2850 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_4"></a>F.13.2. AltosUI Application</h3></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2851 Support TeleMega, TeleMetrum v2.0, TeleMini v2.0 and
2852 EasyMini telemetry and log formats.
2853 </li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2854 Use preferred units for main deployment height
2855 configuration, instead of always doing configuration in
2857 == MicroPeak Application
2858 </li><li class="listitem">
2859 Add <span class="emphasis"><em>Download</em></span> button to menu bar.
2860 </li><li class="listitem">
2861 Save the last log directory and offer that as the
2862 default for new downloads
2863 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_2_1"></a>F.14. Release Notes for Version 1.2.1</h2></div></div></div><p>Version 1.2.1 is a minor release. It adds support for TeleBT and
2864 the AltosDroid application, provides several new features in
2865 AltosUI and fixes some bugs in the AltOS firmware.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_12"></a>F.14.1. AltOS</h3></div></div></div><p>AltOS new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2866 Add support for TeleBT
2867 </li></ul></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2868 In TeleMini recovery mode (when booted with the
2869 outer two debug pins connected together), the radio
2870 parameters are also set back to defaults
2871 (434.550MHz, N0CALL, factory radio cal).
2872 </li><li class="listitem">
2873 Correct Kalman filter model error covariance
2874 matrix. The values used previously assumed
2875 continuous measurements instead of discrete
2877 </li><li class="listitem">
2878 Fix some bugs in the USB driver for TeleMetrum and
2879 TeleDongle that affected Windows users.
2880 </li><li class="listitem">
2881 Adjusted the automatic gain control parameters that
2882 affect receive performance for TeleDongle. Field
2883 tests indicate that this may improve receive
2884 performance somewhat.
2885 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_5"></a>F.14.2. AltosUI Application</h3></div></div></div><p>AltosUI application new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2886 Make the initial position of the AltosUI top level
2887 window configurable. Along with this change, the
2888 other windows will pop up at <span class="emphasis"><em>sensible</em></span> places now,
2889 instead of on top of one another.
2890 </li><li class="listitem">
2891 Add GPS data and a map to the graph window. This
2892 lets you see a complete summary of the flight
2893 without needing to <span class="emphasis"><em>replay</em></span> the whole thing.
2894 </li></ul></div><p>AltosUI application fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2895 Handle missing GPS lock in <span class="emphasis"><em>Descent</em></span>
2896 tab. Previously, if the GPS position of the pad was
2897 unknown, an exception would be raised, breaking the
2898 Descent tab contents.
2899 </li><li class="listitem">
2900 Improve the graph, adding tool-tips to show values
2901 near the cursor and making the displayed set of
2902 values configurable, adding all of the flight data
2903 as options while leaving the default settings alone
2904 so that the graph starts by showing height, speed
2906 </li><li class="listitem">
2907 Add callsign to Monitor idle window and connecting
2908 dialogs. This makes it clear which callsign is being
2909 used so that the operator will be aware that it must
2910 match the flight computer value or no communication
2912 </li><li class="listitem">
2913 When downloading flight data, display the block
2914 number so that the user has some sense of
2915 progress. Unfortunately, we don’t know how many
2916 blocks will need to be downloaded, but at least it
2917 isn’t just sitting there doing nothing for a long
2919 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosdroid_4"></a>F.14.3. AltosDroid</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2920 First version of this application
2921 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_2"></a>F.15. Release Notes for Version 1.2</h2></div></div></div><p>Version 1.2 is a major release. It adds support for MicroPeak
2922 and the MicroPeak USB adapter.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_13"></a>F.15.1. AltOS</h3></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2923 Add MicroPeak support. This includes support for the
2924 ATtiny85 processor and adaptations to the core code
2925 to allow for devices too small to run the
2926 multi-tasking scheduler.
2927 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_micropeak_application"></a>F.15.2. AltosUI and MicroPeak Application</h3></div></div></div><p>New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2928 Added MicroPeak application
2929 </li></ul></div><p>AltosUI and MicroPeak fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2930 Distribute Mac OS X packages in disk image (<span class="emphasis"><em>.dmg</em></span>)
2931 format to greatly simplify installation.
2932 </li><li class="listitem">
2933 Provide version numbers for the shared Java
2934 libraries to ensure that upgrades work properly, and
2935 to allow for multiple Altus Metrum software packages
2936 to be installed in the same directory at the same
2938 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_1"></a>F.16. Release Notes for Version 1.1</h2></div></div></div><p>Version 1.1.1 is a bug-fix release. It fixes a couple of bugs
2939 in AltosUI and one firmware bug that affects TeleMetrum
2940 version 1.0 boards. Thanks to Bob Brown for help diagnosing
2941 the Google Earth file export issue, and for suggesting the
2942 addition of the Ground Distance value in the Descent tab.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_14"></a>F.16.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2943 TeleMetrum v1.0 boards use the AT45DB081D flash
2944 memory part to store flight data, which is different
2945 from later TeleMetrum boards. The AltOS v1.1 driver
2946 for this chip couldn’t erase memory, leaving it
2947 impossible to delete flight data or update
2948 configuration values. This bug doesn’t affect newer
2949 TeleMetrum boards, and it doesn’t affect the safety
2950 of rockets flying version 1.1 firmware.
2951 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_2"></a>F.16.2. AltosUI</h3></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2952 The “Descent” tab displays the range to the rocket,
2953 which is a combination of the over-the-ground
2954 distance to the rockets current latitude/longitude
2955 and the height of the rocket. As such, it’s useful
2956 for knowing how far away the rocket is, but
2957 difficult to use when estimating where the rocket
2958 might eventually land. A new “Ground Distance” field
2959 has been added which displays the distance to a spot
2960 right underneath the rocket.
2961 </li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2962 Creating a Google Earth file (KML) from on-board
2963 flight data (EEPROM) would generate an empty
2964 file. The code responsible for reading the EEPROM
2965 file wasn’t ever setting the GPS valid bits, and so
2966 the KML export code thought there was no GPS data in
2968 </li><li class="listitem">
2969 The “Landed” tab was displaying all values in metric
2970 units, even when AltosUI was configured to display
2971 imperial units. Somehow I just missed this tab when
2972 doing the units stuff.
2973 </li><li class="listitem">
2974 Sensor data wasn’t being displayed for TeleMini
2975 flight computers in Monitor Idle mode, including
2976 things like battery voltage. The code that picked
2977 which kinds of data to fetch from the flight
2978 computer was missing a check for TeleMini when
2979 deciding whether to fetch the analog sensor data.
2980 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_1_2"></a>F.17. Release Notes for Version 1.1</h2></div></div></div><p>Version 1.1 is a minor release. It provides a few new features
2981 in AltosUI and the AltOS firmware and fixes bugs.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_15"></a>F.17.1. AltOS</h3></div></div></div><p>AltOS Firmware New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2982 Add apogee-lockout value. Overrides the apogee
2983 detection logic to prevent incorrect apogee charge
2985 </li><li class="listitem">
2986 Force the radio frequency to 434.550MHz when the
2987 debug clock pin is connected to ground at boot
2988 time. This provides a way to talk to a TeleMini
2989 which is configured to some unknown frequency.
2990 </li><li class="listitem">
2991 Provide RSSI values for Monitor Idle mode. This
2992 makes it easy to check radio range without needing
2993 to go to flight mode.
2994 </li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2995 Fix a bug where the data reported in telemetry
2996 packets was from 320ms ago.
2997 </li><li class="listitem">
2998 Fix a bug which caused the old received telemetry
2999 packets to be retransmitted over the USB link when
3000 the radio was turned off and back on.
3001 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_3"></a>F.17.2. AltosUI</h3></div></div></div><p>AltosUI New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3002 Make the look-n-feel configurable, providing a choice from
3003 the available options.
3004 </li><li class="listitem">
3005 Add an <span class="emphasis"><em>Age</em></span> element to mark how long since a
3006 telemetry packet has been received. Useful to
3007 quickly gauge whether communications with the rocket
3009 </li><li class="listitem">
3010 Add <span class="emphasis"><em>Configure Ground Station</em></span> dialog to set the
3011 radio frequency used by a particular TeleDongle
3012 without having to go through the flight monitor UI.
3013 </li><li class="listitem">
3014 Add configuration for the new apogee-lockout
3015 value. A menu provides a list of reasonable values,
3016 or the value can be set by hand.
3017 </li><li class="listitem">
3018 Add Imperial units mode to present data in feet
3020 </li></ul></div><p>AltosUI Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3021 Fix a bug that caused GPS ready to happen too
3022 quickly. The software was using every telemetry
3023 packet to signal new GPS data, which caused GPS
3024 ready to be signalled after 10 packets instead of 10
3026 </li><li class="listitem">
3027 Fix Google Earth data export to work with recent
3028 versions. The google earth file loading code got a
3029 lot pickier, requiring some minor white space
3030 changes in the export code.
3031 </li><li class="listitem">
3032 Changed how flight data are downloaded. Now there’s
3033 an initial dialog asking which flights to download,
3034 and after that finishes, a second dialog comes up
3035 asking which flights to delete.
3036 </li><li class="listitem">
3037 Re-compute time spent in each state for the flight
3038 graph; this figures out the actual boost and landing
3039 times instead of using the conservative values
3040 provide by the flight electronics. This improves the
3041 accuracy of the boost acceleration and main descent
3043 </li><li class="listitem">
3044 Make AltosUI run on Mac OS Lion. The default Java
3045 heap space was dramatically reduced for this release
3046 causing much of the UI to fail randomly. This most
3047 often affected the satellite mapping download and
3049 </li><li class="listitem">
3050 Change how data are displayed in the <span class="emphasis"><em>table</em></span> tab of
3051 the flight monitoring window. This eliminates
3052 entries duplicated from the header and adds both
3053 current altitude and pad altitude, which are useful
3054 in <span class="emphasis"><em>Monitor Idle</em></span> mode.
3055 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_0_1"></a>F.18. Release Notes for Version 1.0.1</h2></div></div></div><p>Version 1.0.1 is a major release, adding support for the
3056 TeleMini device and lots of new AltosUI features</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_16"></a>F.18.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">
3057 Add TeleMini v1.0 support.
3058 </li><li class="listitem">
3059 Support operation of TeleMetrum with the antenna pointing
3060 aft. Previous firmware versions required the antenna to be
3061 pointing upwards, now there is a configuration option
3062 allowing the antenna to point aft, to aid installation in
3064 </li><li class="listitem">
3065 Ability to disable telemetry. For airframes where an antenna
3066 just isn’t possible, or where radio transmissions might
3067 cause trouble with other electronics, there’s a
3068 configuration option to disable all telemetry. Note that the
3069 board will still enable the radio link in idle mode.
3070 </li><li class="listitem">
3071 Arbitrary frequency selection. The radios in Altus Metrum
3072 devices can be programmed to a wide range of frequencies, so
3073 instead of limiting devices to 10 pre-selected <span class="emphasis"><em>channels</em></span>,
3074 the new firmware allows the user to choose any frequency in
3075 the 70cm band. Note that the RF matching circuit on the
3076 boards is tuned for around 435MHz, so frequencies far from
3077 that may reduce the available range.
3078 </li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3079 Change telemetry to be encoded in multiple 32-byte
3080 packets. This enables support for TeleMini and other devices
3081 without requiring further updates to the TeleDongle
3083 </li><li class="listitem">
3084 Kalman-filter based flight-tracking. The model based sensor
3085 fusion approach of a Kalman filter means that AltOS now
3086 computes apogee much more accurately than before, generally
3087 within a fraction of a second. In addition, this approach
3088 allows the baro-only TeleMini device to correctly identify
3089 Mach transitions, avoiding the error-prone selection of a
3091 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_6"></a>F.18.2. AltosUI Application</h3></div></div></div><p>AltosUI New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3092 Add main/apogee voltage graphs to the data
3093 plot. This provides a visual indication if the
3094 igniters fail before being fired.
3095 </li><li class="listitem">
3096 Scan for altimeter devices by watching the defined
3097 telemetry frequencies. This avoids the problem of
3098 remembering what frequency a device was configured
3099 to use, which is especially important with TeleMini
3100 which does not include a USB connection.
3101 </li><li class="listitem">
3102 Monitor altimeter state in "Idle" mode. This
3103 provides much of the information presented in the
3104 "Pad" dialog from the Monitor Flight command,
3105 monitoring the igniters, battery and GPS status
3106 withing requiring the flight computer to be armed
3107 and ready for flight.
3108 </li><li class="listitem">
3109 Pre-load map images from home. For those launch
3110 sites which don’t provide free Wi-Fi, this allows
3111 you to download the necessary satellite images
3112 given the location of the launch site. A list of
3113 known launch sites is maintained at altusmetrum.org
3114 which AltosUI downloads to populate a menu; if
3115 you’ve got a launch site not on that list, please
3116 send the name of it, latitude and longitude along
3117 with a link to the web site of the controlling club
3118 to the altusmetrum mailing list.
3119 </li><li class="listitem">
3120 Flight statistics are now displayed in the Graph
3121 data window. These include max height/speed/accel,
3122 average descent rates and a few other bits of
3123 information. The Graph Data window can now be
3124 reached from the <span class="emphasis"><em>Landed</em></span> tab in the Monitor Flight
3125 window so you can immediately see the results of a
3127 </li></ul></div><p>AltosUI Changes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3128 Wait for altimeter when using packet mode. Instead
3129 of quicly timing out when trying to initialize a
3130 packet mode configuration connection, AltosUI now
3131 waits indefinitely for the remote device to appear,
3132 providing a cancel button should the user get
3133 bored. This is necessary as the TeleMini can only be
3134 placed in "Idle" mode if AltosUI is polling it.
3135 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_0_9_2"></a>F.19. Release Notes for Version 0.9.2</h2></div></div></div><p>Version 0.9.2 is an AltosUI bug-fix release, with no firmware
3136 changes.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_4"></a>F.19.1. AltosUI</h3></div></div></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3137 Fix plotting problems due to missing file in the Mac
3139 </li><li class="listitem">
3140 Always read whole eeprom blocks, mark empty records
3141 invalid, display parsing errors to user.
3142 </li><li class="listitem">
3143 Add software version to Configure AltosUI dialog
3144 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_0_9"></a>F.20. Release Notes for Version 0.9</h2></div></div></div><p>Version 0.9 adds a few new firmware features and accompanying
3145 AltosUI changes, along with new hardware support.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_17"></a>F.20.1. AltOS</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3146 Support for TeleMetrum v1.1 hardware. Sources for the flash
3147 memory part used in v1.0 dried up, so v1.1 uses a different
3148 part which required a new driver and support for explicit
3150 </li><li class="listitem">
3151 Multiple flight log support. This stores more than one
3152 flight log in the on-board flash memory. It also requires
3153 the user to explicitly erase flights so that you won’t lose
3154 flight logs just because you fly the same board twice in one
3156 </li><li class="listitem">
3157 Telemetry support for devices with serial number >= 256.
3158 Previous versions used a telemetry packet format that
3159 provided only 8 bits for the device serial number. This
3160 change requires that both ends of the telemetry link be
3161 running the 0.9 firmware or they will not communicate.
3162 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_7"></a>F.20.2. AltosUI Application</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3163 Support for telemetry format changes.
3164 </li><li class="listitem">
3165 Support for multiple flight logs.
3166 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_0_8"></a>F.21. Release Notes for Version 0.8</h2></div></div></div><p>Version 0.8 offers a major upgrade in the AltosUI
3167 interface.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_8"></a>F.21.1. AltosUI Application:</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3168 Post-flight graphing tool. This lets you explore the
3169 behaviour of your rocket after flight with a scroll-able and
3170 zoom-able chart showing the altitude, speed and acceleration
3171 of the airframe along with events recorded by the flight
3172 computer. You can export graphs to PNG files, or print them
3174 </li><li class="listitem">
3175 Real-time moving map which overlays the in-progress flight
3176 on satellite imagery fetched from Google Maps. This lets you
3177 see in pictures where your rocket has landed, allowing you
3178 to plan recovery activities more accurately.
3179 </li><li class="listitem">
3180 Wireless recovery system testing. Prep your rocket for
3181 flight and test fire the deployment charges to make sure
3182 things work as expected. All without threading wires through
3183 holes in your airframe.
3184 </li><li class="listitem">
3185 Optimized flight status displays. Each flight state now has
3186 it’s own custom <span class="emphasis"><em>tab</em></span> in the flight monitoring window so you
3187 can focus on the most important details. Pre-flight, the
3188 system shows a set of red/green status indicators for
3189 battery voltage, apogee/main igniter continutity and GPS
3190 reception. Wait until they’re all green and your rocket is
3191 ready for flight. There are also tabs for ascent, descent
3192 and landing along with the original tabular view of the
3194 </li><li class="listitem">
3195 Monitor multiple flights simultaneously. If you have more
3196 than one TeleDongle, you can monitor a flight with each one
3197 on the same computer.
3198 </li><li class="listitem">
3199 Automatic flight monitoring at startup. Plug TeleDongle into
3200 the machine before starting AltosUI and it will
3201 automatically connect to it and prepare to monitor a flight.
3202 </li><li class="listitem">
3203 Exports Google Earth flight tracks. Using the Keyhole Markup
3204 Language (.kml) file format, this provides a 3D view of your
3205 rocket flight through the Google Earth program.
3206 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_0_7_1"></a>F.22. Release Notes for Version 0.7.1</h2></div></div></div><p>Version 0.7.1 is the first release containing our new
3207 cross-platform Java-based user interface.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_9"></a>F.22.1. AltosUI Application</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3208 Receive and log telemetry from a connected TeleDongle
3209 device. All data received is saved to log files named with
3210 the current date and the connected rocket serial and flight
3211 numbers. There is no mode in which telemetry data will not
3213 </li><li class="listitem">
3214 Download logged data from TeleMetrum devices, either through
3215 a direct USB connection or over the air through a TeleDongle
3217 </li><li class="listitem">
3218 Configure a TeleMetrum device, setting the radio channel,
3219 callsign, apogee delay and main deploy height. This can be
3220 done through either a USB connection or over a radio link
3221 via a TeleDongle device.
3222 </li><li class="listitem">
3223 Replay a flight in real-time. This takes a saved telemetry
3224 log or eeprom download and replays it through the user
3225 interface so you can relive your favorite rocket flights.
3226 </li><li class="listitem">
3227 Reprogram Altus Metrum devices. Using an Altus Metrum device
3228 connected via USB, another Altus Metrum device can be
3229 reprogrammed using the supplied programming cable between
3231 </li><li class="listitem">
3232 Export Flight data to a comma-separated-values file. This
3233 takes either telemetry or on-board flight data and generates
3234 data suitable for use in external applications. All data is
3235 exported using standard units so that no device-specific
3236 knowledge is needed to handle the data.
3237 </li><li class="listitem">
3238 Speak to you during the flight. Instead of spending the
3239 flight hunched over your laptop looking at the screen, enjoy
3240 the view while the computer tells you what’s going on up
3241 there. During ascent, you hear the current flight state and
3242 altitude information. During descent, you get azimuth,
3243 elevation and range information to try and help you find
3244 your rocket in the air. Once on the ground, the direction
3245 and distance are reported.
3246 </li></ul></div></div></div></div></div></body></html>
projects / web / altusmetrum / blob