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 © 2018 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">5. TeleMini</a></span></dt><dd><dl><dt><span class="section"><a href="#_telemini_v3_screw_terminals">5.1. TeleMini v3 Screw Terminals</a></span></dt><dt><span class="section"><a href="#_using_a_separate_pyro_battery_with_telemini_v3">5.2. Using a Separate Pyro Battery with TeleMini v3</a></span></dt><dt><span class="section"><a href="#_using_an_active_switch_with_telemini_v3">5.3. Using an Active Switch with TeleMini v3</a></span></dt><dt><span class="section"><a href="#_telemini_v1">5.4. TeleMini v1</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="#_calibrate_accelerometer">11.6.18. Calibrate Accelerometer</a></span></dt><dt><span class="section"><a href="#_configure_pyro_channels">11.6.19. 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_v1_0_firmware">C.2.2. Updating TeleMini v1.0 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_8_5">F.1. Release Notes for Version 1.8.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">F.1.2. AltosUI, TeleGPS</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_8_4">F.2. Release Notes for Version 1.8.4</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_2">F.2.1. AltOS</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_8_3">F.3. Release Notes for Version 1.8.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></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_8_2">F.4. Release Notes for Version 1.8.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></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_8_1">F.5. Release Notes for Version 1.8.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></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_8">F.6. Release Notes for Version 1.8</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_7">F.7. Release Notes for Version 1.7</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_6_8">F.8. Release Notes for Version 1.6.8</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_8">F.8.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_telegps_and_altosdroid_applications">F.8.2. AltosUI, TeleGPS and AltosDroid Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_5">F.9. Release Notes for Version 1.6.5</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_9">F.9.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_telegps_and_altosdroid_applications_2">F.9.2. AltosUI, TeleGPS and AltosDroid Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_4">F.10. Release Notes for Version 1.6.4</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_10">F.10.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_telegps_and_altosdroid_applications_3">F.10.2. AltosUI, TeleGPS and AltosDroid Applications</a></span></dt><dt><span class="section"><a href="#_documentation">F.10.3. Documentation</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_3">F.11. Release Notes for Version 1.6.3</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_11">F.11.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_6">F.11.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_altosdroid_2">F.11.3. AltosDroid</a></span></dt><dt><span class="section"><a href="#_documentation_2">F.11.4. Documentation</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_2">F.12. Release Notes for Version 1.6.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_12">F.12.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_7">F.12.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_documentation_3">F.12.3. Documentation</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_1">F.13. Release Notes for Version 1.6.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_13">F.13.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_8">F.13.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_altosdroid_3">F.13.3. AltosDroid</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6">F.14. Release Notes for Version 1.6</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_14">F.14.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_9">F.14.2. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_5">F.15. Release Notes for Version 1.5</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_15">F.15.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_10">F.15.2. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_4_2">F.16. Release Notes for Version 1.4.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_and_telegps_applications_11">F.16.1. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_4_1">F.17. Release Notes for Version 1.4.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_and_telegps_applications_12">F.17.1. AltosUI and TeleGPS Applications:</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_4">F.18. Release Notes for Version 1.4</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">F.18.2. AltosUI Application</a></span></dt><dt><span class="section"><a href="#_telegps_application">F.18.3. TeleGPS Application</a></span></dt><dt><span class="section"><a href="#_documentation_4">F.18.4. Documentation</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_3_2">F.19. Release Notes for Version 1.3.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_17">F.19.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_2">F.19.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_3_1">F.20. Release Notes for Version 1.3.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_18">F.20.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_3">F.20.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_3">F.21. Release Notes for Version 1.3</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_19">F.21.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_4">F.21.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_2_1">F.22. Release Notes for Version 1.2.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_20">F.22.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_5">F.22.2. AltosUI Application</a></span></dt><dt><span class="section"><a href="#_altosdroid_4">F.22.3. AltosDroid</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_2">F.23. Release Notes for Version 1.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_21">F.23.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_micropeak_application">F.23.2. AltosUI and MicroPeak Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_1">F.24. Release Notes for Version 1.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_22">F.24.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_2">F.24.2. AltosUI</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_1_2">F.25. Release Notes for Version 1.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_23">F.25.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_3">F.25.2. AltosUI</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_0_1">F.26. Release Notes for Version 1.0.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_24">F.26.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_6">F.26.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_0_9_2">F.27. Release Notes for Version 0.9.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_4">F.27.1. AltosUI</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_0_9">F.28. Release Notes for Version 0.9</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_25">F.28.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application_7">F.28.2. AltosUI Application</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_0_8">F.29. Release Notes for Version 0.8</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_application_8">F.29.1. AltosUI Application:</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_0_7_1">F.30. Release Notes for Version 0.7.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_application_9">F.30.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="#idm452">TeleMetrum v2 Board</a></dt><dt>4.2. <a href="#idm459">TeleMetrum v1 Board</a></dt><dt>5.1. <a href="#idm545">TeleMini v3 Board</a></dt><dt>5.2. <a href="#idm629">TeleMini v1 Board</a></dt><dt>6.1. <a href="#idm638">EasyMini Board</a></dt><dt>7.1. <a href="#idm740">TeleMega Board</a></dt><dt>8.1. <a href="#idm910">EasyMega Board</a></dt><dt>11.1. <a href="#idm1128">AltosUI Main Window</a></dt><dt>11.2. <a href="#idm1139">Device Selection Dialog</a></dt><dt>11.3. <a href="#idm1167">Monitor Flight Launch Pad View</a></dt><dt>11.4. <a href="#idm1207">Monitor Flight Ascent View</a></dt><dt>11.5. <a href="#idm1220">Monitor Flight Descent View</a></dt><dt>11.6. <a href="#idm1233">Monitor Flight Landed View</a></dt><dt>11.7. <a href="#idm1248">Monitor Flight Table View</a></dt><dt>11.8. <a href="#idm1258">Monitor Flight Site Map View</a></dt><dt>11.9. <a href="#idm1273">Monitor Flight Additional Igniter View</a></dt><dt>11.10. <a href="#idm1303">Flight Data Graph</a></dt><dt>11.11. <a href="#idm1314">Flight Graph Configuration</a></dt><dt>11.12. <a href="#idm1333">Flight Statistics</a></dt><dt>11.13. <a href="#idm1343">Flight Map</a></dt><dt>11.14. <a href="#idm1364">Altimeter Configuration</a></dt><dt>11.15. <a href="#idm1480">Additional Pyro Channel Configuration</a></dt><dt>11.16. <a href="#idm1557">Configure AltosUI Dialog</a></dt><dt>11.17. <a href="#idm1610">Configure Groundstation Dialog</a></dt><dt>11.18. <a href="#idm1650">Fire Igniter Window</a></dt><dt>11.19. <a href="#idm1669">Scan Channels Window</a></dt><dt>11.20. <a href="#idm1679">Load Maps Window</a></dt><dt>11.21. <a href="#idm1712">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="#idm214">AltOS Modes</a></dt><dt>3.2. <a href="#idm322">Pad/Idle Indications</a></dt><dt>3.3. <a href="#idm377">Pad Radio Indications</a></dt><dt>4.1. <a href="#idm479">TeleMetrum Screw Terminals</a></dt><dt>5.1. <a href="#idm562">TeleMini v3 Screw Terminals</a></dt><dt>6.1. <a href="#idm650">EasyMini Screw Terminals</a></dt><dt>7.1. <a href="#idm760">TeleMega Screw Terminals</a></dt><dt>8.1. <a href="#idm921">EasyMega Screw Terminals</a></dt><dt>A.1. <a href="#idm2048">Altus Metrum APRS Comments</a></dt><dt>D.1. <a href="#idm2299">Data Storage on Altus Metrum altimeters</a></dt><dt>E.1. <a href="#idm2394">Altus Metrum Flight Computer Electronics</a></dt><dt>E.2. <a href="#idm2587">Altus Metrum Flight Computer Mechanical Components</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_introduction_and_overview"></a>Chapter 1. Introduction and Overview</h1></div></div></div><p>Welcome to the Altus Metrum community! Our circuits and software reflect
23 our passion for both hobby rocketry and Free Software. We hope their
24 capabilities and performance will delight you in every way, but by
25 releasing all of our hardware and software designs under open licenses,
26 we also hope to empower you to take as active a role in our collective
27 future as you wish!</p><p>Our goal is to include in this document all of the information required
28 to successfully configure and use Altus Metrum products. But
29 documentation is a lot like software in that it can contain "bugs",
30 and can probably always be improved! If you have questions that
31 aren’t answered in this manual, or just need a little help figuring
32 things out, we strongly suggest joining the Altus Metrum user email
33 list, which you can do by visiting
34 <a class="ulink" href="https://lists.gag.com/mailman/listinfo/altusmetrum" target="_top">https://lists.gag.com/mailman/listinfo/altusmetrum</a>. There’s a lot
35 of useful information in the mailing list archives!</p><p>The first device created for our community was TeleMetrum, a dual
36 deploy altimeter with fully integrated GPS and radio telemetry
37 as standard features, and a “companion interface” that will
38 support optional capabilities in the future. The latest version
39 of TeleMetrum, v2.0, has all of the same features but with
40 improved sensors and radio to offer increased performance.</p><p>Our second device was TeleMini, a dual deploy altimeter with
41 radio telemetry and radio direction finding. The first version
42 of this device was only 13mm by 38mm (½ inch by 1½ inches) and
43 could fit easily in an 18mm air-frame. The latest version, v3.0,
44 includes a beeper, higher power radio, extended on-board
45 flight logging and an improved barometric sensor.</p><p>TeleMega is our most sophisticated device, including six pyro
46 channels (four of which are fully programmable), integrated GPS,
47 integrated gyroscopes for staging/air-start inhibit and high
48 performance telemetry.</p><p>EasyMini is a dual-deploy altimeter with logging and built-in
49 USB data download.</p><p>EasyMega is essentially a TeleMega board with the GPS receiver
50 and telemetry transmitter removed. It offers the same 6 pyro
51 channels and integrated gyroscopes for staging/air-start inhibit.</p><p>TeleDongle v0.2 was our first ground station, providing a USB to RF
52 interfaces for communicating with the altimeters. Combined with
53 your choice of antenna and notebook computer, TeleDongle and our
54 associated user interface software form a complete ground
55 station capable of logging and displaying in-flight telemetry,
56 aiding rocket recovery, then processing and archiving flight
57 data for analysis and review. The latest version, TeleDongle
58 v3, has all new electronics with a higher performance radio
59 for improved range.</p><p>For a slightly more portable ground station experience that also
60 provides direct rocket recovery support, TeleBT offers flight
61 monitoring and data logging using a Bluetooth™ connection between
62 the receiver and an Android device that has the AltosDroid
63 application installed from the Google Play store.</p><p>More products will be added to the Altus Metrum family over time, and
64 we currently envision that this will be a single, comprehensive manual
65 for the entire product family.</p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_getting_started"></a>Chapter 2. Getting Started</h1></div></div></div><p>The first thing to do after you open the box is to hook up a
66 battery and charge it if necessary.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_batteries"></a>2.1. Batteries</h2></div></div></div><p>For TeleMetrum, TeleMega and EasyMega, the battery can be charged by plugging it into the
67 corresponding socket of the device and then using the USB
68 cable to plug the flight computer into your computer’s USB socket. The
69 on-board circuitry will charge the battery whenever it is plugged
70 in, because the on-off switch does NOT control the
74 EasyMini battery can be charged by disconnecting it
75 from the board and plugging it into a standalone
76 battery charger such as <a class="ulink" href="http://altusmetrum.org/LipoCharger" target="_top">LipoCharger</a>, and
77 connecting that via a USB cable to a laptop or other
78 USB power source.</p><p>You can also choose to use another battery with
79 EasyMini, anything supplying between 4 and 12 volts should
80 work fine (like a standard 9V battery), but if you are planning
81 to fire pyro charges, ground testing is required to verify that
82 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
83 searching for satellites, TeleMetrum will consume more current
84 than it pulls from the USB port, so the battery must be
85 attached in order to get satellite lock. Once GPS is locked,
86 the current consumption goes back down enough to enable charging
87 while running. So it’s a good idea to fully charge the battery
88 as your first item of business so there is no issue getting and
89 maintaining satellite lock. The yellow charge indicator led
90 will go out when the battery is nearly full and the charger goes
91 to trickle charge. It can take several hours to fully recharge a
92 deeply discharged battery.</p><p>TeleMetrum v2.0, TeleMega and EasyMega use a higher power battery charger,
93 allowing them to charge the battery while running the board at
94 maximum power. When the battery is charging, or when the board
95 is consuming a lot of power, the red LED will be lit. When the
96 battery is fully charged, the green LED will be lit. When the
97 battery is damaged or missing, both LEDs will be lit, which
98 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
99 RF interface and the TeleBT Bluetooth/USB to RF interface. If
100 you plug either of these in to your Mac or Linux computer it should
101 “just work”, showing up as a serial port device. Windows systems need
102 driver information that is part of the AltOS download to know that the
103 existing USB modem driver will work. We therefore recommend installing
104 our software before plugging in TeleDongle if you are using a Windows
105 computer. If you are using an older version of Linux and are having
106 problems, try moving to a fresher kernel (2.6.33 or
107 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.
108 The AltOS distribution includes the AltosUI ground
109 station program, current firmware images for all of
110 the hardware, and a number of standalone utilities
111 that are rarely needed. Pre-built binary packages are
112 available for Linux, Microsoft Windows, Mac OSX. Full
113 source code and build instructions are also
114 available. The latest version may always be downloaded
115 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
116 BlueTooth or USB. The
117 <a class="ulink" href="https://play.google.com/store/apps/details?id=org.altusmetrum.AltosDroid" target="_top">AltosDroid
118 Android application</a> is available from the
119 <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
120 without network access, you’ll want to download
121 offline map data before wandering away from the
122 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
123 flight computer. Instructions specific to each model will be
124 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
125 operation of the flight computer, it’s important to always
126 twist pairs of wires connected to the board. Twist the switch
127 leads, the pyro leads and the battery leads. This reduces
128 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
129 series connector to connect up a single-cell Lithium Polymer
130 cell (3.7V nominal). You can purchase matching batteries
131 from the Altus Metrum store, or other vendors, or you can
132 make your own. Pin 1 of the connector is positive, pin 2 is
133 negative. Spark Fun sells a cable with the connector
134 attached, which they call a
135 <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
136 this same connector. All that we have found use the opposite
137 polarity, and if you use them that way, you will damage or
138 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
139 each pyro charge. This means you shouldn’t need to put two
140 wires into a screw terminal or connect leads from pyro
141 charges together externally.</p><p>On the flight computer, one lead from each charge is hooked
142 to the positive battery terminal through the power switch.
143 The other lead is connected through the pyro circuit, which
144 is connected to the negative battery terminal when the pyro
145 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
146 to turn them on. This disconnects both the computer and the
147 pyro charges from the battery, preventing the charges from
148 firing when in the Off position. The switch is in-line with
149 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
150 provide information about the state of the system.
151 TeleMini doesn’t have room for a beeper, so instead it
152 uses an LED, which works the same, except for every
153 beep is replaced with the flash of the LED.</p><p>Here’s a short summary of all of the modes and the
155 (or flashing, in the case of TeleMini v1)
156 that accompanies each mode. In the description of the
157 beeping pattern, “dit” means a short beep while "dah"
158 means a long beep (three times as long). “Brap” means
159 a long dissonant tone.</p><div class="table"><a id="idm214"></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
160 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
161 indications. In Idle mode, you’ll hear one of these
162 just once after the two short dits indicating idle
163 mode. In Pad mode, after the dit dah dah dit
164 indicating Pad mode, you’ll hear these once every five
165 seconds.</p><div class="table"><a id="idm322"></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
166 not prevent the flight computer from safely
167 controlling the flight or transmitting telemetry
168 signals, but no record of the flight will be
169 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
170 channels on TeleMega and EasyMega. One high tone for
171 no continuity, one low tone for continuity. These are
172 produced after the continuity indicators for the two
173 primary igniter channels.</p></td></tr></tbody></table></div></div><br class="table-break" /><p>For devices with a radio transmitter, in addition to
174 the digital and APRS telemetry signals, you can also
175 receive audio tones with a standard amateur
176 70cm FM receiver. While on the pad, you will hear
177 igniter status once every five seconds.</p><div class="table"><a id="idm377"></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
178 telemetry data to consume the full radio bandwidth.</p><p>During descent and after landing, a ½ second tone will
179 be transmitted every five seconds. This can be used to
180 find the rocket using RDF techniques when the signal
181 is too weak to receive GPS information via telemetry
182 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
183 to "on". The flight computer will signal power on by
184 reporting the battery voltage and then perform an internal self
185 test and sensor calibration.</p><p>Once the self test and calibration are complete, there
186 are two modes that an Altus Metrum flight computer can
187 operate in:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
190 The flight computer is waiting to detect
191 launch and then fly the rocket. In this mode, the USB
193 disabled, and the radio goes into transmit-only mode.
194 The only way to get out of this
195 mode is to power the flight computer down. See below for how to get the flight
196 computer to come up in Flight/Pad mode at power on.
197 </dd><dt><span class="term">
200 The flight computer is ready to communicate over USB
201 and in packet mode over the radio.
203 the flight computer, download data or display
204 the current state. See below for how to get the flight
205 computer to come up in Idle mode at power on.
206 </dd></dl></div><p>For flight computers with accelerometers (TeleMetrum,
207 EasyMega and TeleMega), the mode is selected by the
208 orientation of the board during the self test
209 interval. If the board is pointing upwards as if ready
210 to fly, it will enter Flight/Pad mode. Otherwise, it will
211 enter Idle mode.</p><p>For EasyMini, if the USB cable is connected to a
212 computer, it will enter Idle mode. Otherwise, it will
213 enter Flight/Pad mode.</p><p>For TeleMini v1.0, if a packet link is waiting to
214 connect when the device is powered on, it will enter
215 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>
216 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
217 Featherweight Magnetic Switch, with any Altus Metrum
218 flight computer. These require three connections, one to
219 the battery, one to the positive power input on the flight
220 computer and one to ground. Find instructions on how to
221 hook these up for each flight computer below. Then follow
222 the instructions that come with your active switch to
223 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
224 lead for each of the pyro charges is connected through
225 the power switch directly to the positive battery
226 terminal. The other lead is connected to the pyro
227 circuit, which connects it to the negative battery
228 terminal when the pyro circuit is fired. The pyro
229 circuit on all of the flight computers is designed to
230 handle up to 16V.</p><p>To use a separate pyro battery, connect the negative pyro
231 battery terminal to the flight computer ground terminal,
232 the positive battery terminal to the igniter and the other
233 igniter lead to the negative pyro terminal on the flight
234 computer. When the pyro channel fires, it will complete the
235 circuit between the negative pyro terminal and the ground
236 terminal, firing the igniter. Specific instructions on how
237 to hook this up for each flight computer will be found
238 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
240 designed to use either a
241 lithium polymer battery or any other battery producing
242 between 4 and 12 volts, such as a rectangular 9V
243 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
244 operate off a single-cell Lithium Polymer battery and
245 cannot be used with any other kind. Connecting a
246 different kind of battery to any of these will destroy
247 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="idm452"></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="idm459"></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
248 fit inside coupler for 29mm air-frame tubing, but using it in a tube that
249 small in diameter may require some creativity in mounting and wiring
250 to succeed! The presence of an accelerometer means TeleMetrum should
251 be aligned along the flight axis of the airframe, and by default the ¼
252 wave UHF wire antenna should be on the nose-cone end of the board. The
253 antenna wire is about 7 inches long, and wiring for a power switch and
254 the e-matches for apogee and main ejection charges depart from the
255 fin can end of the board, meaning an ideal “simple” avionics
256 bay for TeleMetrum should have at least 10 inches of interior length.</p><p>There are two generations of the TeleMetrum design. The
257 major changes in the v2 generation are:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
258 uBlox GPS chip certified for altitude records
259 </li><li class="listitem">
260 Higher power radio (40mW vs 10mW)
261 </li><li class="listitem">
263 </li></ul></div><p>Otherwise, they’re the same size, with mounting holes and
264 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
265 opposite the telemetry antenna. Two are for the power
266 switch, and two each for the apogee and main igniter
267 circuits. Using the picture above and starting from the top,
268 the terminals are as follows:</p><div class="table"><a id="idm479"></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
269 connecting the negative battery terminal to the flight
270 computer ground, connecting the positive battery terminal to
271 one of the igniter leads and connecting the other igniter
272 lead to the per-channel pyro circuit connection.</p><p>To connect the negative battery terminal to the TeleMetrum
273 ground, insert a small piece of wire, 24 to 28 gauge
274 stranded, into the GND hole just above the screw terminal
275 strip and solder it in place.</p><p>Connecting the positive battery terminal to the pyro
276 charges must be done separate from TeleMetrum, by soldering
277 them together or using some other connector.</p><p>The other lead from each pyro charge is then inserted into
278 the appropriate per-pyro channel screw terminal (terminal 4 for the
279 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
280 connections, one to the positive battery terminal, one to
281 the flight computer positive input and one to ground.</p><p>The positive battery terminal is available on screw terminal
282 2, the positive flight computer input is on terminal 1. To
283 hook a lead to ground, solder a piece of wire, 24 to 28
284 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"></a>Chapter 5. TeleMini</h1></div></div></div><div class="figure"><a id="idm545"></a><p class="title"><strong>Figure 5.1. TeleMini v3 Board</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telemini-v3.0-top.jpg" width="495" alt="telemini-v3.0-top.jpg" /></div></div></div><br class="figure-break" /><div class="informalfigure"><div class="mediaobject"><img src="telemini-v3.0-bottom.jpg" width="495" alt="telemini-v3.0-bottom.jpg" /></div></div><p>TeleMini v3 is 0.5 inches by 1.67 inches. It was
285 designed to fit inside an 18mm air-frame tube, but using it in
286 a tube that small in diameter may require some creativity in
287 mounting and wiring to succeed! Since there is no
288 accelerometer, TeleMini can be mounted in any convenient
289 orientation. The default ¼ wave UHF wire antenna attached to
290 the center of one end of the board is about 7 inches long. Screw
291 terminals for the power switch are located in the
292 middle of the board. Screw terminals for the e-matches for
293 apogee and main ejection charges depart from the other end of
294 the board, meaning an ideal “simple” avionics bay for TeleMini
295 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_v3_screw_terminals"></a>5.1. TeleMini v3 Screw Terminals</h2></div></div></div><p>TeleMini v3 has four screw terminals on the end of the
296 board opposite the telemetry antenna. Two are for the apogee
297 and two are for main igniter circuits. Another two
298 screw terminals are located in the middle of the board
299 for the power switch. Using the
300 picture above and starting from the top for the pyro terminals
301 and from the left for the power switch terminals, the
302 connections are as follows:</p><div class="table"><a id="idm562"></a><p class="title"><strong>Table 5.1. TeleMini v3 Screw Terminals</strong></p><div class="table-contents"><table class="table" summary="TeleMini v3 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_v3"></a>5.2. Using a Separate Pyro Battery with TeleMini v3</h2></div></div></div><p>As described above, using an external pyro battery involves
303 connecting the negative battery terminal to the flight
304 computer ground, connecting the positive battery terminal to
305 one of the igniter leads and connecting the other igniter
306 lead to the per-channel pyro circuit connection. Because
307 there is no solid ground connection to use on TeleMini, this
308 is not recommended.</p><p>The only available ground connection on TeleMini v3 are
309 the two mounting holes next to the telemetry
310 antenna. Somehow connect a small piece of wire to one of
311 those holes and hook it to the negative pyro battery terminal.</p><p>Connecting the positive battery terminal to the pyro
312 charges must be done separate from TeleMini v3, by soldering
313 them together or using some other connector.</p><p>The other lead from each pyro charge is then inserted into
314 the appropriate per-pyro channel screw terminal (terminal 3 for the
315 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_v3"></a>5.3. Using an Active Switch with TeleMini v3</h2></div></div></div><p>As explained above, an external active switch requires three
316 connections, one to the positive battery terminal, one to
317 the flight computer positive input and one to ground. Again,
318 because TeleMini doesn’t have any good ground connection,
319 this is not recommended.</p><p>The positive battery terminal is available on the Right
320 power switch wire, the positive flight computer input is on
321 the left power switch wire. Hook a lead to either of the
322 mounting holes for a ground connection.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_telemini_v1"></a>5.4. TeleMini v1</h2></div></div></div><p>TeleMini v1 is the earlier version of this product. It
323 has a lower-power radio, less storage, no beeper and
324 soldered-in wires instead of screw terminals for the
325 power switch.</p><div class="figure"><a id="idm629"></a><p class="title"><strong>Figure 5.2. TeleMini v1 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" /></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="idm638"></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
326 designed to fit in a 24mm coupler tube.</p><p>You usually don’t need to configure EasyMini at all; it’s set
327 up to do dual-deployment with an event at apogee to separate
328 the airframe and deploy a drogue and another event at 250m
329 (820ft) to deploy the main. Install EasyMini in your airframe,
330 hook up a battery, igniters and a power switch and you’re
331 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
332 board. Using the picture
333 above, the top four have connections for the main pyro
334 circuit and an external battery and the bottom four have
335 connections for the apogee pyro circuit and the power
336 switch. Counting from the left, the connections are as follows:</p><div class="table"><a id="idm650"></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
337 EasyMini. You can use either method; both feed
338 through the power switch terminals.</p><p>One battery connection is the standard Altus Metrum
339 white JST plug. This mates with single-cell Lithium
340 Polymer batteries sold by Altus Metrum.</p><p>The other is a pair of screw terminals marked <span class="emphasis"><em>Battery
341 +</em></span> and <span class="emphasis"><em>Battery -</em></span>. Connect a battery from 4 to 12
342 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
343 standard Altus Metrum Lithium Polymer cells, it cannot
344 incorporate a battery charger circuit. Therefore, when
345 using a Litium Polymer cell, you’ll need an external
346 charger. These are available from Altus Metrum, or
347 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
348 connecting the negative battery terminal to the flight
349 computer ground, connecting the positive battery terminal to
350 one of the igniter leads and connecting the other igniter
351 lead to the per-channel pyro circuit connection.</p><p>To connect the negative pyro battery terminal to EasyMini
352 ground, connect it to the negative external battery
353 connection, top terminal 4.</p><p>Connecting the positive battery terminal to the pyro
354 charges must be done separate from EasyMini, by soldering
355 them together or using some other connector.</p><p>The other lead from each pyro charge is then inserted into
356 the appropriate per-pyro channel screw terminal (top
357 terminal 1 for the Main charge, bottom terminal 1 for the
358 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
359 connections, one to the positive battery terminal, one to
360 the flight computer positive input and one to ground. Use
361 the negative external battery connection, top terminal 4 for
362 ground.</p><p>The positive battery terminal is available on bottom
363 terminal 4, the positive flight computer input is on the
364 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="idm740"></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
365 designed to easily fit in a 38mm coupler. Like TeleMetrum,
366 TeleMega has an accelerometer and so it must be mounted so that
367 the board is aligned with the flight axis. It can be mounted
368 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">
369 Companion connector matches EasyMega functions
370 </li><li class="listitem">
371 Serial port connector replaced with servo connector with
372 support for up to 4 PWM channels.
373 </li><li class="listitem">
374 Radio switched from cc1120 to cc1200.
375 </li></ul></div><p>None of these affect operation using the stock firmware, but
376 they do mean that the device needs different firmware to
377 operate correctly, so make sure you load the right firmware
378 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
379 the board opposite the telemetry antenna. They are as follows:</p><div class="table"><a id="idm760"></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
380 battery. All that is required is to remove the jumper
381 between the lipo terminal (Bottom 3) and the pyro terminal
382 (Bottom 2). Then hook the negative pyro battery terminal to ground
383 (Bottom 1) and the positive pyro battery to the pyro battery
384 input (Bottom 2). You can then use the existing pyro screw
385 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
386 battery, if you want to fly with just one battery running
387 both the computer and firing the charges, you need to
388 connect the flight computer battery to the pyro
389 circuit. TeleMega has two screw terminals for this—hook a
390 wire from the Lipo terminal (Bottom 3) to the Pyro terminal
391 (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
392 connections, one to the positive battery terminal, one to
393 the flight computer positive input and one to ground.</p><p>The positive battery terminal is available on Top terminal
394 1, the positive flight computer input is on Top terminal
395 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="idm910"></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
396 designed to easily fit in a 38mm coupler. Like TeleMetrum,
397 EasyMega has an accelerometer and so it must be mounted so that
398 the board is aligned with the flight axis. It can be mounted
399 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
400 the board opposite the telemetry antenna. They are as follows:</p><div class="table"><a id="idm921"></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
401 battery. All that is required is to remove the jumper
402 between the lipo terminal (Bottom 3) and the pyro terminal
403 (Bottom 2). Then hook the negative pyro battery terminal to ground
404 (Bottom 1) and the positive pyro battery to the pyro battery
405 input (Bottom 2). You can then use the existing pyro screw
406 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
407 battery, if you want to fly with just one battery running
408 both the computer and firing the charges, you need to
409 connect the flight computer battery to the pyro
410 circuit. EasyMega has two screw terminals for this—hook a
411 wire from the Lipo terminal (Bottom 3) to the Pyro terminal
412 (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
413 connections, one to the positive battery terminal, one to
414 the flight computer positive input and one to ground.</p><p>The positive battery terminal is available on Top terminal
415 1, the positive flight computer input is on Top terminal
416 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
417 only a suitable battery, a single pole switch for
418 power on/off, and two pairs of wires connecting e-matches for the
419 apogee and main ejection charges. All Altus Metrum products are
420 designed for use with single-cell batteries with 3.7 volts
422 EasyMini may also be used with other
423 batteries as long as they supply between 4 and 12 volts.</p><p>The battery connectors are a standard 2-pin JST connector; you
424 can purchase suitable batteries from the any vendor selling
425 Altus Metrum products. These batteries are
426 single-cell Lithium Polymer batteries that nominally provide 3.7
427 volts. Other vendors sell similar batteries for RC aircraft
428 using mating connectors, however the polarity for those is
429 generally reversed from the batteries used by Altus Metrum
430 products. In particular, the Tenergy batteries supplied for use
431 in Featherweight flight computers are not compatible with Altus
432 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
433 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
434 the correct polarity. However, these batteries include an
435 integrated current limiting circuit. That circuit will cause
436 the battery to shut down when firing the igniter circuit. Do
437 not use these batteries unless you remove the current limiting
438 circuit.</p></div><p>By default, we use the unregulated output of the battery
439 directly to fire ejection charges. This works marvelously
440 with standard low-current e-matches like the J-Tek from MJG
441 Technologies, and with Quest Q2G2 igniters. However, if you
442 want or need to use a separate pyro battery, check out
443 <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
444 that up. The altimeters are designed to work with an external
445 pyro battery of no more than 15 volts.</p><p>Ejection charges are wired directly to the screw terminal block
446 at the aft end of the altimeter. You’ll need a very small straight
447 blade screwdriver for these screws, such as you might find in a
448 jeweler’s screwdriver set.</p><p>Except for TeleMini v1.0, the flight computers also use the
449 screw terminal block for the power switch leads. On TeleMini v1.0,
450 the power switch leads are soldered directly to the board and
451 can be connected directly to a switch.</p><p>For most air-frames, the integrated antennas are more than
452 adequate. However, if you are installing in a carbon-fiber or
453 metal electronics bay which is opaque to RF signals, you may need to
454 use off-board external antennas instead. In this case, you can
455 replace the stock UHF antenna wire with an edge-launched SMA connector,
456 and, on TeleMetrum v1, you can unplug the integrated GPS
457 antenna and select an appropriate off-board GPS antenna with
458 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
459 <a class="ulink" href="http://www.altusmetrum.org/Radio/" target="_top">amateur radio license</a>
460 or other authorization to legally operate the radio
461 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
462 and a single-cell, 3.7 volt nominal Li-Po rechargeable
464 An 850mAh battery weighs less than a 9V
465 alkaline battery, and will run a TeleMetrum, TeleMega
466 or EasyMega for hours.
467 A 110mAh battery weighs less
468 than a triple A battery and is a good choice for use
471 EasyMini.</p><p>By default, we ship TeleMini, TeleMetrum and TeleMega
472 flight computers with a simple wire antenna. If your
473 electronics bay or the air-frame it resides within is
474 made of carbon fiber, which is opaque to RF signals,
475 you may prefer to install an SMA connector so that you
476 can run a coaxial cable to an antenna mounted
477 elsewhere in the rocket. However, note that the GPS
478 antenna is fixed on all current products, so you
479 really want to install the flight computer in a bay
480 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
481 an antenna and short feed-line connected to one of our
482 <a class="ulink" href="http://www.altusmetrum.org/TeleDongle/" target="_top">TeleDongle</a>
483 units. If possible, use an SMA to BNC adapter instead
484 of feedline between the antenna feedpoint and
485 TeleDongle, as this will give you the best
486 performance. The TeleDongle in turn plugs directly
487 into the USB port on a notebook computer. Because
488 TeleDongle looks like a simple serial port, your
489 computer does not require special device
490 drivers… just plug it in.</p><p>The GUI tool, AltosUI, is written in Java and runs
491 across Linux, Mac OS and Windows. There’s also a suite
492 of C tools for Linux which can perform most of the
493 same tasks.</p><p>Alternatively, a TeleBT attached with an SMA to BNC
494 adapter at the feed point of a hand-held yagi used in
495 conjunction with an Android device running AltosDroid
496 makes an outstanding ground station.</p><p>After the flight,
497 you can use the radio link to
498 extract the more detailed data logged in either
499 TeleMetrum or TeleMini devices, or
501 USB cable to plug into the flight computer board directly.
502 A USB cable is also how you
503 charge the Li-Po battery, so you’ll want one of those
504 anyway. The same cable used by lots of digital
505 cameras and other modern electronic stuff will work
506 fine.</p><p>If your rocket lands out of sight, you may enjoy
507 having a hand-held GPS receiver, so that you can put
508 in a way-point for the last reported rocket position
509 before touch-down. This makes looking for your rocket
510 a lot like Geo-Caching… just go to the way-point and
511 look around starting from there. AltosDroid on an
512 Android device with GPS receiver works great for this,
513 too!</p><p>You may also enjoy having a ham radio “HT” that covers
514 the 70cm band… you can use that with your antenna to
515 direction-find the rocket on the ground the same way
516 you can use a Walston or Beeline tracker. This can be
517 handy if the rocket is hiding in sage brush or a tree,
518 or if the last GPS position doesn’t get you close
519 enough because the rocket dropped into a canyon, or
520 the wind is blowing it across a dry lake bed, or
521 something like that… Keith currently uses a Yaesu
522 FT1D, Bdale has a Yaesu VX-7R, which is a nicer radio
523 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">
524 an antenna and feed-line or adapter
525 </li><li class="listitem">
527 </li><li class="listitem">
529 </li><li class="listitem">
530 optionally, a hand-held GPS receiver
531 </li><li class="listitem">
532 optionally, an HT or receiver covering 435 MHz
533 </li></ol></div><p>The best hand-held commercial directional antennas we’ve found for radio
534 direction finding rockets are from
535 <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
536 a TeleMetrum- or TeleMini- equipped rocket when used
537 with a suitable 70cm HT. TeleDongle and an SMA to BNC
538 adapter fit perfectly between the driven element and
539 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
540 flight, both the telemetry received during the flight
541 itself, and the more complete data log recorded in the
542 flash memory on the altimeter board. Once this data
543 is on your computer, our post-flight tools make it
544 easy to quickly get to the numbers everyone wants,
545 like apogee altitude, max acceleration, and max
546 velocity. You can also generate and view a standard
547 set of plots showing the altitude, acceleration, and
548 velocity of the rocket during flight. And you can
549 even export a flight log in a format usable with Google
550 Maps and Google Earth for visualizing the flight path
551 in two or three dimensions!</p><p>Our ultimate goal is to emit a set of files for each
552 flight that can be published as a web page per flight,
553 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
554 boards” that can attach to the companion connector on
555 TeleMetrum, TeleMega and EasyMega flight computers to
556 collect more data, provide more pyro channels, and so
557 forth. We do not yet know if or when any of these
558 boards will be produced in enough quantity to sell.
559 If you have specific interests for data collection or
560 control of events in your rockets beyond the
561 capabilities of our existing productions, please let
562 us know!</p><p>Because all of our work is open, both the hardware
563 designs and the software, if you have some great idea
564 for an addition to the current Altus Metrum family,
565 feel free to dive in and help! Or let us know what
566 you’d like to see that we aren’t already working on,
567 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
568 more news and information as our family of products
569 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="idm1128"></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
570 interacting with the Altus Metrum product family. AltosUI can
571 monitor telemetry data, configure devices and many other
572 tasks. The primary interface window provides a selection of
573 buttons, one for each major activity in the system. This
574 chapter is split into sections, each of which documents one of
575 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
576 of the connected TeleDongle devices. When you choose
577 one of these, AltosUI will create a window to display
578 telemetry data as received by the selected TeleDongle
579 device.</p><div class="figure"><a id="idm1139"></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
580 in suitable log files. The name of the files includes
581 the current date and rocket serial and flight numbers.</p><p>The radio frequency being monitored by the TeleDongle
582 device is displayed at the top of the window. You can
583 configure the frequency by clicking on the frequency
584 box and selecting the desired frequency. AltosUI
585 remembers the last frequency selected for each
586 TeleDongle and selects that automatically the next
587 time you use that device.</p><p>Below the TeleDongle frequency selector, the window
588 contains a few significant pieces of information about
589 the altimeter providing the telemetry data stream:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
590 The configured call-sign
591 </li><li class="listitem">
592 The device serial number
593 </li><li class="listitem">
594 The flight number. Each altimeter remembers how
595 many times it has flown.
596 </li><li class="listitem">
597 The rocket flight state. Each flight passes through
598 several states including Pad, Boost, Fast, Coast,
599 Drogue, Main and Landed.
600 </li><li class="listitem">
601 The Received Signal Strength Indicator value. This
602 lets you know how strong a signal TeleDongle is
603 receiving. At the default data rate, 38400 bps, in
604 bench testing, the radio inside TeleDongle v0.2
605 operates down to about -106dBm, while the v3 radio
606 works down to about -111dBm. Weaker signals, or an
607 environment with radio noise may cause the data to
608 not be received. The packet link uses error
609 detection and correction techniques which prevent
610 incorrect data from being reported.
611 </li><li class="listitem">
612 The age of the displayed data, in seconds since the
613 last successfully received telemetry packet. In
614 normal operation this will stay in the low single
615 digits. If the number starts counting up, then you
616 are no longer receiving data over the radio link
617 from the flight computer.
618 </li></ul></div><p>Finally, the largest portion of the window contains a
619 set of tabs, each of which contain some information
620 about the rocket. They’re arranged in <span class="emphasis"><em>flight order</em></span>
621 so that as the flight progresses, the selected tab
622 automatically switches to display data relevant to the
623 current state of the flight. You can select other tabs
624 at any time. The final <span class="emphasis"><em>table</em></span> tab displays all of the
625 raw telemetry values in one place in a
626 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="idm1167"></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
627 rocket is ready for flight. The first elements include red/green
628 indicators, if any of these is red, you’ll want to evaluate
629 whether the rocket is ready to launch:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
632 This indicates whether the Li-Po battery powering the
633 flight computer has sufficient charge to last for
634 the duration of the flight. A value of more than
635 3.8V is required for a <span class="emphasis"><em>GO</em></span> status.
636 </dd><dt><span class="term">
637 Apogee Igniter Voltage
639 This indicates whether the apogee
640 igniter has continuity. If the igniter has a low
641 resistance, then the voltage measured here will be close
642 to the Li-Po battery voltage. A value greater than 3.2V is
643 required for a <span class="emphasis"><em>GO</em></span> status.
644 </dd><dt><span class="term">
647 This indicates whether the main
648 igniter has continuity. If the igniter has a low
649 resistance, then the voltage measured here will be close
650 to the Li-Po battery voltage. A value greater than 3.2V is
651 required for a <span class="emphasis"><em>GO</em></span> status.
652 </dd><dt><span class="term">
653 On-board Data Logging
655 This indicates whether there is space remaining
656 on-board to store flight data for the upcoming
657 flight. If you’ve downloaded data, but failed to erase
658 flights, there may not be any space left. Most of our
659 flight computers can store multiple flights, depending
660 on the configured maximum flight log size. TeleMini
661 v1.0 stores only a single flight, so it will need to
662 be downloaded and erased after each flight to capture
663 data. This only affects on-board flight logging; the
664 altimeter will still transmit telemetry and fire
665 ejection charges at the proper times even if the
666 flight data storage is full.
667 </dd><dt><span class="term">
670 For a TeleMetrum or TeleMega device, this indicates
671 whether the GPS receiver is currently able to compute
672 position information. GPS requires at least 4
673 satellites to compute an accurate position.
674 </dd><dt><span class="term">
677 For a TeleMetrum or TeleMega device, this indicates
678 whether GPS has reported at least 10 consecutive
679 positions without losing lock. This ensures that the
680 GPS receiver has reliable reception from the
682 </dd></dl></div><p>The Launchpad tab also shows the computed launch pad
683 position and altitude, averaging many reported
684 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="idm1207"></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
685 phases. The information displayed here helps monitor the
686 rocket as it heads towards apogee.</p><p>The height, speed, acceleration and tilt are shown along
687 with the maximum values for each of them. This allows you to
688 quickly answer the most commonly asked questions you’ll hear
689 during flight.</p><p>The current latitude and longitude reported by the GPS are
690 also shown. Note that under high acceleration, these values
691 may not get updated as the GPS receiver loses position
692 fix. Once the rocket starts coasting, the receiver should
693 start reporting position again.</p><p>Finally, the current igniter voltages are reported as in the
694 Launch Pad tab. This can help diagnose deployment failures
695 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="idm1220"></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)
696 activated the apogee charge, attention switches to
697 tracking the rocket on the way back to the ground, and
698 for dual-deploy flights, waiting for the main charge
699 to fire.</p><p>To monitor whether the apogee charge operated
700 correctly, the current descent rate is reported along
701 with the current height. Good descent rates vary based
702 on the choice of recovery components, but generally
703 range from 15-30m/s on drogue and should be below
704 10m/s when under the main parachute in a dual-deploy
705 flight.</p><p>With GPS-equipped flight computers, you can locate the
706 rocket in the sky using the elevation and bearing
707 information to figure out where to look. Elevation is
708 in degrees above the horizon. Bearing is reported in
709 degrees relative to true north. Range can help figure
710 out how big the rocket will appear. Ground Distance
711 shows how far it is to a point directly under the
712 rocket and can help figure out where the rocket is
713 likely to land. Note that all of these values are
714 relative to the pad location. If the elevation is near
715 90°, the rocket is over the pad, not over you.</p><p>Finally, the igniter voltages are reported in this tab
716 as well, both to monitor the main charge as well as to
717 see what the status of the apogee charge is. Note
718 that some commercial e-matches are designed to retain
719 continuity even after being fired, and will continue
720 to show as green or return from red to green after
721 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="idm1233"></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
722 to recovery. While the radio signal is often lost once
723 the rocket is on the ground, the last reported GPS
724 position is generally within a short distance of the
725 actual landing location.</p><p>The last reported GPS position is reported both by
726 latitude and longitude as well as a bearing and
727 distance from the launch pad. The distance should give
728 you a good idea of whether to walk or hitch a ride.
729 Take the reported latitude and longitude and enter
730 them into your hand-held GPS unit and have that
731 compute a track to the landing location.</p><p>Our flight computers will continue to transmit RDF
732 tones after landing, allowing you to locate the rocket
733 by following the radio signal if necessary. You may
734 need to get away from the clutter of the flight line,
735 or even get up on a hill (or your neighbor’s RV roof)
736 to receive the RDF signal.</p><p>The maximum height, speed and acceleration reported
737 during the flight are displayed for your admiring
738 observers. The accuracy of these immediate values
739 depends on the quality of your radio link and how many
740 packets were received. Recovering the on-board data
741 after flight may yield more precise results.</p><p>To get more detailed information about the flight, you
742 can click on the <span class="emphasis"><em>Graph Flight</em></span> button which will
743 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="idm1248"></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
744 flight computer. Probably the most useful data on
745 this tab is the detailed GPS information, which includes
746 horizontal dilution of precision information, and
747 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="idm1258"></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
748 will map the rocket’s position to make it easier for
749 you to locate the rocket, both while it is in the air,
750 and when it has landed. The rocket’s state is
751 indicated by color: white for pad, red for boost, pink
752 for fast, yellow for coast, light blue for drogue,
753 dark blue for main, and black for landed.</p><p>The map’s default scale is approximately 3m (10ft) per
754 pixel. The map can be dragged using the left mouse
755 button. The map will attempt to keep the rocket
756 roughly centered while data is being received.</p><p>You can adjust the style of map and the zoom level
757 with buttons on the right side of the map window. You
758 can draw a line on the map by moving the mouse over
759 the map with a button other than the left one pressed,
760 or by pressing the left button while also holding down
761 the shift key. The length of the line in real-world
762 units will be shown at the start of the line.</p><p>Images are fetched automatically via the Google Maps
763 Static API, and cached on disk for reuse. If map
764 images cannot be downloaded, the rocket’s path will be
765 traced on a dark gray background instead.</p><p>You can pre-load images for your favorite launch sites
766 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="idm1273"></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
767 channels. The Ignitor tab shows whether each of them has
768 continuity. If an ignitor has a low resistance, then the
769 voltage measured here will be close to the pyro battery
770 voltage. A value greater than 3.2V is required for a <span class="emphasis"><em>GO</em></span>
771 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
773 Data logged on board is recorded at a much
774 higher rate than the telemetry system can handle, and
775 is not subject to radio drop-outs. As such, it
776 provides a more complete and precise record of the
778 The <span class="emphasis"><em>Save Flight Data</em></span> button allows you to
779 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
780 list of connected flight computers and TeleDongle
781 devices. If you select a flight computer, the flight
782 data will be downloaded from that device directly.
783 If you select a TeleDongle device, flight data will be
784 downloaded from a flight computer over radio link via
785 the specified TeleDongle. See
786 <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
787 more information.</p><p>After the device has been selected, a dialog showing
788 the flight data saved in the device will be shown
789 allowing you to select which flights to download and
790 which to delete. With version 0.9 or newer firmware,
791 you must erase flights in order for the space they
792 consume to be reused by another flight. This prevents
793 accidentally losing flight data if you neglect to
794 download data before flying again. Note that if there
795 is no more space available in the device, then no data
796 will be recorded during the next flight.</p><p>The file name for each flight log is computed
797 automatically from the recorded flight date, altimeter
798 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
799 record file, either a .telem file recording telemetry data or a
800 .eeprom file containing flight data saved from the altimeter
801 flash memory.</p><p>Once a flight record is selected, the flight monitor interface
802 is displayed and the flight is re-enacted in real
805 <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
806 record file, either a .telem file recording telemetry data or a
807 .eeprom file containing flight data saved from
808 flash memory.</p><p>Note that telemetry files will generally produce poor graphs
809 due to the lower sampling rate and missed telemetry packets.
810 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
811 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="idm1303"></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),
812 velocity (green) and altitude (red).</p><p>The graph can be zoomed into a particular area by
813 clicking and dragging down and to the right. Once
814 zoomed, the graph can be reset by clicking and
815 dragging up and to the left. Holding down control and
816 clicking and dragging allows the graph to be panned.
817 The right mouse button causes a pop-up menu to be
818 displayed, giving you the option save or print the
819 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="idm1314"></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
820 very bottom. It also lets you configure how
821 the graph is drawn:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
822 Whether to use metric or imperial units
823 </li><li class="listitem">
824 Whether to show a marker at each data
825 point. When displaying a small section of
826 the graph, these can be useful to know what
827 data values were recorded.
828 </li><li class="listitem">
829 How wide to draw the lines in the graph
830 </li><li class="listitem">
831 How to filter speed and acceleration data
832 computed from barometric data. Flight
833 computers with accelerometers never display
834 computed acceleration data, and only use
835 barometric data to compute speed during
836 descent. Flight computers without
837 accelerometers always compute both speed and
838 acceleration from barometric data. A larger
839 value smooths the data more.
840 </li></ul></div></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="idm1333"></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="idm1343"></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
841 with the path of the flight. The red concentric
842 circles mark the launch pad, the black concentric
843 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
844 available for external analysis. When you select this
845 button, you are prompted to select a flight data file,
846 which can be either a .eeprom or .telem. The .eeprom
847 files contain higher resolution and more continuous
848 data, while .telem files contain receiver signal
849 strength information. Next, a second dialog appears
850 which is used to select where to write the resulting
852 It has a selector to choose between CSV and KML
853 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
854 suitable for import into a spreadsheet or other
855 external data analysis tool. The first few lines of
856 the file contain the version and configuration
857 information from the altimeter, then there is a single
858 header line which labels all of the fields. All of
859 these lines start with a <span class="emphasis"><em>#</em></span> character which many
860 tools can be configured to skip over.</p><p>The remaining lines of the file contain the data, with
861 each field separated by a comma and at least one
862 space. All of the sensor values are converted to
863 standard units, with the barometric data reported in
864 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
865 overlay within that application. With this, you can
866 use Google Earth to see the whole flight path
867 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="idm1364"></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
868 TeleDongle Device from the list provided. Selecting a TeleDongle
869 device will use the radio link to configure a remote
870 altimeter.</p><p>The first few lines of the dialog provide information about the
871 connected device, including the product name,
872 software version and hardware serial number. Below that are the
873 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">
876 This writes any changes to the configuration parameter
877 block in flash memory. If you don’t press this button,
878 any changes you make will be lost.
879 </dd><dt><span class="term">
882 This resets the dialog to the most recently saved
883 values, erasing any changes you have made.
884 </dd><dt><span class="term">
887 This reboots the device. Use this to switch from idle
888 to pad mode by rebooting once the rocket is oriented
889 for flight, or to confirm changes you think you saved
891 </dd><dt><span class="term">
894 This closes the dialog. Any unsaved changes will be
896 </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
897 altitude) at which the <span class="emphasis"><em>main</em></span> igniter will fire. The
898 drop-down menu shows some common values, but you can
899 edit the text directly and choose whatever you
900 like. If the apogee charge fires below this altitude,
901 then the main charge will fire two seconds after the
902 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
903 important to ensure that multiple apogee charges don’t
904 fire at precisely the same time, as that can over
905 pressurize the apogee deployment bay and cause a
906 structural failure of the air-frame. The Apogee Delay
907 parameter tells the flight computer to fire the apogee
908 charge a certain number of seconds after apogee has
909 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
910 where the flight computer will not fire the apogee
911 charge, even if the rocket appears to be at
912 apogee. This is often called <span class="emphasis"><em>Mach Delay</em></span>, as it is
913 intended to prevent a flight computer from
914 unintentionally firing apogee charges due to the
915 pressure spike that occurrs across a mach
916 transition. Altus Metrum flight computers include a
917 Kalman filter which is not fooled by this sharp
918 pressure increase, and so this setting should be left
919 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
920 both telemetry and packet command mode. Note that if
921 you set this value via packet command mode, the
922 TeleDongle frequency will also be automatically
923 reconfigured to match so that communication will
924 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
925 at the factory to ensure that they transmit and
926 receive on the specified frequency. If you need to
927 you can adjust the calibration by changing this value.
928 Do not do this without understanding what the value
929 means, read the appendix on calibration and/or the
930 source code for more information. To change a
931 TeleDongle’s calibration, you must reprogram the unit
932 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
933 flight. When disabled, the radio will not
934 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
935 transmission for both telemetry and packet
936 link mode. Lower bit rates will increase range
937 while reducing the amount of data that can be
938 sent and increasing battery consumption. All
939 telemetry is done using a rate 1/2 constraint
940 4 convolution code, so the actual data
941 transmission rate is 1/2 of the modulation bit
942 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
943 (in seconds). When set to zero, APRS
944 transmission is disabled.
946 available on TeleMetrum v2 and TeleMega
947 boards. TeleMetrum v1 boards cannot transmit
949 Note that a single APRS packet
950 takes nearly a full second to transmit, so
951 enabling this option will prevent sending any
952 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
953 default, this is set to the last digit of the
954 serial number, but can be configured to any
955 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
956 Uncompressed format. Compressed format is
957 smaller and more precise. Uncompressed
958 format is older, but may work better with your
959 device. The Kenwood TH-D72 only displays
960 altitude information with Uncompressed
961 format, while the Yaesu FT1D only displays
962 altitude with Compressed format. Test before
963 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
964 telemetry packet. Set this as needed to
965 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
966 for each flight log. The available space will
967 be divided into chunks of this size. A smaller
968 value will allow more flights to be stored, a
969 larger value will record data from longer
970 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
971 channels (Apogee and Main) to be used in different
972 configurations.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
975 This is the usual mode of operation; the
976 <span class="emphasis"><em>apogee</em></span> channel is fired at apogee and the
977 <span class="emphasis"><em>main</em></span> channel at the height above ground
978 specified by the <span class="emphasis"><em>Main Deploy Altitude</em></span> during
980 </dd><dt><span class="term">
983 This fires both channels at apogee, the
984 <span class="emphasis"><em>apogee</em></span> channel first followed after a two
985 second delay by the <span class="emphasis"><em>main</em></span> channel.
986 </dd><dt><span class="term">
989 This fires both channels at the height above
990 ground specified by the Main Deploy Altitude
991 setting during descent. The <span class="emphasis"><em>apogee</em></span> channel
992 is fired first, followed after a two second
993 delay by the <span class="emphasis"><em>main</em></span> channel.
994 </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,
995 TeleMetrum, TeleMega and EasyMega are
996 sensitive to the orientation of the board. By
997 default, they expect the antenna end to point
998 forward. This parameter allows that default to
999 be changed, permitting the board to be mounted
1000 with the antenna pointing aft instead.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1003 In this mode, the antenna end of the flight
1004 computer must point forward, in line with the
1005 expected flight path.
1006 </dd><dt><span class="term">
1009 In this mode, the antenna end of the flight
1010 computer must point aft, in line with the
1011 expected flight path.
1012 </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
1013 computers works best at 4000Hz, however if you
1014 have more than one flight computer in a single
1015 airframe, having all of them sound at the same
1016 frequency can be confusing. This parameter
1017 lets you adjust the base beeper frequency
1018 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
1019 needs to see before logging the new
1020 position. Motions smaller than this are
1021 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,
1022 both over the air and in the log. Increase
1023 this to reduce the frequency of radio
1024 transmissions and the length of time available
1025 in the log.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_calibrate_accelerometer"></a>11.6.18. Calibrate Accelerometer</h3></div></div></div><p>This opens a separate window to recalibrate the
1026 accelerometers. Follow the instructions, orienting the
1027 flight computer with the antenna end, or end opposite
1028 the screw terminals, in the case of EasyMega, first up
1029 and then down.</p><p>When the calibration is complete, return to the
1030 Configure Altimeter window and save the new
1031 calibration values.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_configure_pyro_channels"></a>11.6.19. Configure Pyro Channels</h3></div></div></div><div class="figure"><a id="idm1480"></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
1032 additional pyro channels available on TeleMega
1033 and EasyMega. One column is presented for
1034 each channel. Each row represents a single
1035 parameter, if enabled the parameter must meet
1036 the specified test for the pyro channel to be
1037 fired.</p><p>Select conditions and set the related value;
1038 the pyro channel will be activated when <span class="strong"><strong>all</strong></span>
1039 of the conditions are met. Each pyro channel
1040 has a separate set of configuration values, so
1041 you can use different values for the same
1042 condition with different channels.</p><p>At the bottom of the window, the <span class="emphasis"><em>Pyro Firing
1043 Time</em></span> configuration sets the length of time
1044 (in seconds) which each of these pyro channels
1045 will fire for.</p><p>Once you have selected the appropriate
1046 configuration for all of the necessary pyro
1047 channels, you can save the pyro configuration
1048 along with the rest of the flight computer
1049 configuration by pressing the <span class="emphasis"><em>Save</em></span> button in
1050 the main Configure Flight Computer window.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1051 Vertical Acceleration
1053 Select a value, and then choose whether
1054 acceleration away from the ground should be above or below that
1055 value. Acceleration is positive upwards, so accelerating towards the
1056 ground would produce negative numbers. Acceleration during descent is
1057 noisy and inaccurate, so be careful when using it during these phases
1059 </dd><dt><span class="term">
1062 Select a value, and then choose whether ascent rate
1063 should be above or below that value. Ascent rate is positive upwards,
1064 so moving towards the ground would produce negative numbers. Ascent
1065 rate during descent is a bit noisy and so be careful when using it
1066 during these phases of the flight.
1067 </dd><dt><span class="term">
1070 Select a value, and then choose whether the height
1071 above the launch pad should be above or below that value.
1072 </dd><dt><span class="term">
1075 TeleMega and EasyMega contain a 3-axis gyroscope and
1076 accelerometer which is used to compute the orientation of the
1077 rocket. A record of orientations over the last 0.64 seconds is kept
1078 and the largest value within this period is compared with the
1079 specified value. Note that the tilt angle is not the change in angle
1080 from the launch pad, but rather absolute relative to gravity—the
1081 3-axis accelerometer is used to compute the angle of the rocket on the
1082 launch pad and initialize the system.
1083 </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
1084 rate gyros, it gets progressively less
1085 accurate as the flight goes on. It should have
1086 an accumulated error of less than 0.2°/second
1087 (after 10 seconds of flight, the error should
1088 be less than 2°).</p><p>The usual use of the orientation configuration
1089 is to ensure that the rocket is traveling
1090 mostly upwards when deciding whether to ignite
1091 air starts or additional stages. For that,
1092 choose a reasonable maximum angle (like 20°)
1093 and set the motor igniter to require an angle
1094 of less than that value.</p></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1097 Time since boost was detected. Select a value and choose
1098 whether to activate the pyro channel before or after that amount of
1100 </dd><dt><span class="term">
1103 A deprecated configuration value which was the same as
1104 setting Ascent rate > 0. Existing configurations using this will be
1105 cleared and must be reconfigured by the user.
1106 </dd><dt><span class="term">
1109 A deprecated configuration value which was the same as
1110 setting Ascent rate < 0. Existing configurations using this will be
1111 cleared and must be reconfigured by the user.
1112 </dd><dt><span class="term">
1115 The flight software counts each time the rocket starts
1116 accelerating and then decelerating (presumably due to a motor or
1117 motors burning). Use this value for multi-staged or multi-airstart
1119 </dd><dt><span class="term">
1122 Once the other parameters all become true, a timer is
1123 started for the specified amount of time. While the timer is running,
1124 the other parameters are checked repeatedly and if any of them become
1125 false, then the pyro channel is disabled and will not fire. If the
1126 timer expires and all of the other parameters have remained true for
1127 the entire time, then the pyro channel is fired.
1128 </dd><dt><span class="term">
1130 </span></dt><dd><p class="simpara">
1131 The flight software tracks the flight
1132 through a sequence of states:
1133 </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
1134 Boost. The motor has lit and the rocket is
1135 accelerating upwards. Ascent rate will be greater than zero.
1136 Vertical acceleration will be greater than zero.
1137 </li><li class="listitem">
1138 Fast. The motor has burned out and the
1139 rocket is decelerating, but it is going
1140 faster than 200m/s. Ascent rate will be greater than zero. Vertical
1141 acceleration will be less than zero.
1142 </li><li class="listitem">
1143 Coast. The rocket is still moving upwards
1144 and decelerating, but the Ascent rate is less
1145 than 200m/s. Ascent rate will greater than zero. Vertical
1146 acceleration will be less than zero.
1147 </li><li class="listitem">
1148 Drogue. The rocket has reached apogee and
1149 is heading back down, but is above the
1150 configured Main altitude. Ascent rate will be less than zero during
1151 this state. Vertical acceleration will be negative until the rocket
1152 reaches a terminal descent rate, at which point Vertical
1153 acceleration will be zero. Both Ascent rate and Vertical
1154 acceleration are very noisy in this state, so be careful when
1155 trying to use them to control pyro channels.
1156 </li><li class="listitem">
1157 Main. The rocket is still descending, and
1158 is below the Main altitude. Ascent rate will be less than zero
1159 during this state. Vertical acceleration may be briefly less than
1160 zero as the rocket slows from drogue descent to main descent, but
1161 it will settle down to a zero value once the rocket has reached the
1162 terminal velocity under the main chute. Ascent rate and Vertical
1163 acceleration should be much less noisy once the main chute has
1165 </li><li class="listitem">
1166 Landed. The rocket is no longer moving.
1167 </li></ul></div></dd></dl></div><p>You can select a state to limit when the pyro channel may activate;
1168 note that the check is based on when the rocket transitions <span class="strong"><strong>into</strong></span> the
1169 state, and so checking for “greater than Boost” means that the rocket
1170 is currently in boost or some later state.</p><p>When a motor burns out, the rocket enters either Fast or Coast state
1171 (depending on how fast it is moving). If the computer detects upwards
1172 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="idm1557"></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
1173 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
1174 flight so that you can keep your eyes on the
1175 sky and still get information about the
1176 current flight status. However, sometimes you
1177 don’t want to hear them.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1180 Turns all voice announcements on and off
1181 </dd><dt><span class="term">
1184 Plays a short message allowing you to verify
1185 that the audio system is working and the volume settings
1187 </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
1188 flash data to this directory. This
1189 directory is also used as the staring point
1190 when selecting data files for display or
1191 export.</p><p>Click on the directory name to bring up a
1192 directory choosing dialog, select a new
1193 directory and click <span class="emphasis"><em>Select Directory</em></span> to
1194 change where AltosUI reads and writes data
1195 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
1196 packet sent from TeleDongle and received from
1197 an altimeter. It is not used in telemetry
1198 mode, as the callsign configured in the
1199 altimeter board is included in all telemetry
1200 packets. Configure this with the AltosUI
1201 operators call sign as needed to comply with
1202 your local radio regulations.</p><p>Note that to successfully command a flight
1203 computer over the radio (to configure the
1204 altimeter, monitor idle, or fire pyro
1205 charges), the callsign configured here must
1206 exactly match the callsign configured in the
1207 flight computer. This matching is case
1208 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)
1209 and imperial units (feet and miles). This
1210 affects the display of values use during
1211 flight monitoring, configuration, data
1212 graphing and all of the voice
1213 announcements. It does not change the units
1214 used when exporting to CSV files, those are
1215 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
1216 device to be dumped to the console from which
1217 AltosUI was started. If you’ve started it from
1218 an icon or menu entry, the output will simply
1219 be discarded. This mode can be useful to debug
1220 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
1221 monitor window. Choose between the small,
1222 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
1223 interface appearances. The default selection
1224 is supposed to match the native window system
1225 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
1226 AltosUI window that includes all of the
1227 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
1228 while the application is running. More tiles
1229 consume more memory, but will make panning
1230 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
1231 configure the set of frequencies shown in the
1232 various frequency menus. You can add as many
1233 as you like, or even reconfigure the default
1234 set. Changing this list does not affect the
1235 frequency settings of any devices, it only
1236 changes the set of frequencies shown in the
1237 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="idm1610"></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
1238 TeleBT Device from the list provided.</p><p>The first few lines of the dialog provide information
1239 about the connected device, including the product
1240 name, software version and hardware serial
1241 number. Below that are the individual configuration
1242 entries.</p><p>Note that TeleDongle and TeleBT don’t save any
1243 configuration data, the settings here are recorded on
1244 the local machine in the Java preferences
1245 database. Moving the device to another machine, or
1246 using a different user account on the same machine
1247 will cause settings made here to have no effect.</p><p>At the bottom of the dialog, there are three
1248 buttons:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1251 This writes any changes to the local Java
1252 preferences file. If you don’t press this
1253 button, any changes you make will be lost.
1254 </dd><dt><span class="term">
1257 This resets the dialog to the most recently
1258 saved values, erasing any changes you have
1260 </dd><dt><span class="term">
1263 This closes the dialog. Any unsaved changes
1265 </dd></dl></div><p>The rest of the dialog contains the parameters
1266 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
1267 telemetry and packet command mode. Set this
1268 before starting any operation involving packet
1269 command mode so that it will use the right
1270 frequency. Telemetry monitoring mode also
1271 provides a menu to change the frequency, and
1272 that menu also sets the same Java preference
1273 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
1274 calibrated at the factory to ensure that they
1275 transmit and receive on the specified
1276 frequency. To change a TeleDongle or TeleBT’s
1277 calibration, you must reprogram the unit
1278 completely, so this entry simply shows the
1279 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
1280 link rate from the transmitter. If they don’t
1281 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
1283 TeleMetrum v1.x, TeleDongle v0.2, TeleMini v1.0
1284 and TeleBT v1.0 are all reprogrammed by using another
1285 similar unit as a programming dongle (pair
1287 TeleMega, EasyMega, TeleMetrum v2,
1288 EasyMini and TeleDongle v3 are all
1290 over USB (self programming). Please read
1291 the directions for flashing devices in
1292 <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="idm1650"></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
1293 computer to help test recovery systems
1295 Because this command can operate over the
1296 Packet Command Link, you can prepare the rocket as for
1297 flight and then test the recovery system without
1298 needing to snake wires inside the air-frame.</p><p>Selecting the <span class="emphasis"><em>Fire Igniter</em></span> button brings up the
1299 usual device selection dialog. Pick the desired
1300 device. This brings up another window which shows the
1301 current continuity test status for all of the pyro
1302 channels.</p><p>Next, select the desired igniter to fire. This will
1303 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>
1304 button. The word <span class="emphasis"><em>Arm</em></span> is replaced by a countdown
1305 timer indicating that you have 10 seconds to press the
1306 <span class="emphasis"><em>Fire</em></span> button or the system will deactivate, at which
1307 point you start over again at selecting the desired
1308 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="idm1669"></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
1309 configured frequencies, displaying information about
1310 each device it receives a packet from. You can select
1311 which of the baud rates and telemetry formats should
1312 be tried; by default, it only listens at 38400 baud
1313 with the standard telemetry format used in v1.0 and
1314 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="idm1679"></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
1315 this to load satellite images in case you don’t have
1316 internet connectivity at the site. Try not to wait
1317 until the last minute, though, particularly if you’re
1318 heading to a major launch. If too many people are
1319 all trying to download map data at once, Google may
1320 limit access until the next day.</p><p>There’s a drop-down menu of launch sites we know
1321 about; if your favorites aren’t there, please let us
1322 know the lat/lon and name of the site. The contents of
1323 this list are actually downloaded from our server at
1324 run-time, so as new sites are sent in, they’ll get
1325 automatically added to this list. If the launch site
1326 isn’t in the list, you can manually enter the lat/lon
1327 values</p><p>There are four different kinds of maps you can view;
1328 you can select which to download by selecting as many
1329 as you like from the available types:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1332 A combination of satellite imagery and road data. This
1333 is the default view.
1334 </dd><dt><span class="term">
1337 Just the satellite imagery without any annotation.
1338 </dd><dt><span class="term">
1341 Roads, political boundaries and a few geographic
1343 </dd><dt><span class="term">
1346 Contour intervals and shading that show hills and
1348 </dd></dl></div><p>You can specify the range of zoom levels to download;
1349 smaller numbers show more area with less
1350 resolution. The default level, 0, shows about
1351 3m/pixel. One zoom level change doubles or halves that
1352 number. Larger zoom levels show more detail, smaller
1353 zoom levels less.</p><p>The Map Radius value sets how large an area around the
1354 center point to download. Select a value large enough
1355 to cover any plausible flight from that site. Be aware
1356 that loading a large area with a high maximum zoom
1357 level can attempt to download a lot of data. Loading
1358 hybrid maps with a 10km radius at a minimum zoom of -2
1359 and a maximum zoom of 2 consumes about 120MB of
1360 space. Terrain and road maps consume about 1/10 as
1361 much space as satellite or hybrid maps.</p><p>Clicking the <span class="emphasis"><em>Load Map</em></span> button will fetch images from
1362 Google Maps; note that Google limits how many images
1363 you can fetch at once, so if you load more than one
1364 launch site, you may get some gray areas in the map
1365 which indicate that Google is tired of sending data to
1366 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="idm1712"></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
1367 UI, except it works with the altimeter in “idle” mode
1368 by sending query commands to discover the current
1369 state rather than listening for telemetry
1370 packets. Because this uses command mode, it needs to
1371 have the TeleDongle and flight computer callsigns
1372 match exactly. If you can receive telemetry, but
1373 cannot manage to run Monitor Idle, then it’s very
1374 likely that your callsigns are different in some way.</p><p>You can change the frequency and callsign used to
1375 communicate with the flight computer; they must both
1376 match the configuration in the flight computer
1377 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
1378 AltosUI, but runs on Android devices. AltosDroid is designed
1379 to connect to a TeleBT receiver over Bluetooth™ and (on
1380 Android devices supporting USB On-the-go) TeleDongle and
1381 TeleBT devices over USB. AltosDroid monitors telemetry data,
1382 logging it to internal storage in the Android device, and
1383 presents that data in a UI similar to the <span class="emphasis"><em>Monitor Flight</em></span>
1384 window in AltosUI.</p><p>This manual will explain how to configure AltosDroid, connect
1385 to TeleBT or TeleDongle, operate the flight monitoring
1386 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
1387 install it on your Android device, open the Google
1388 Play Store application and search for
1389 “altosdroid”. Make sure you don’t have a space between
1390 “altos” and “droid” or you probably won’t find what
1391 you want. That should bring you to the right page from
1392 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
1393 internal TeleBT battery is charged. To do this,
1394 attach a micro USB cable from a computer or other USB
1395 power source to TeleBT. A dual LED on the circuit
1396 board should illuminate, showing red while the battery
1397 is charging, green when charging is completed, and
1398 both red and green on at the same time if there is a
1399 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
1400 configuration options available. Select the <span class="emphasis"><em>Connect a
1401 device</em></span> option and then the <span class="emphasis"><em>Scan for devices</em></span> entry
1402 at the bottom to look for your TeleBT device. Select
1403 your device, and when it asks for the code, enter
1404 <span class="emphasis"><em>1234</em></span>.</p><p>Subsequent connections will not require you to enter
1405 that code, and your <span class="emphasis"><em>paired</em></span> device will appear in the
1406 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
1407 cables have a USB micro-B male connector on one end
1408 and a standard A female connector on the other
1409 end. Plug in your TeleDongle or TeleBT device to the
1410 adapter cable and the adapter cable into your phone
1411 and AltosDroid should automatically start up. If it
1412 doesn’t, the most likely reason is that your Android
1413 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
1414 and configuration options.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1417 Offers a menu of available TeleBT devices, and an
1418 option to scan for additional devices.
1419 </dd><dt><span class="term">
1422 Disconnects the current TeleBT or TeleDongle
1423 device. You can reconnect TeleBT over bluetooth by
1424 using Connect a Device. You can reconnect a USB device
1425 by unplugging it and then plugging it back in.
1426 </dd><dt><span class="term">
1427 Select radio frequency
1429 This selects which frequency to listen on by bringing
1430 up a menu of pre-set radio frequencies. Pick the one
1431 which matches your altimeter.
1432 </dd><dt><span class="term">
1435 Switches the information displays to show data for a
1436 different transmitting device. The map will always
1437 show all of the devices in view. Trackers are shown
1438 and selected by serial number, so make sure you note
1439 the serial number of devices in each airframe.
1440 </dd><dt><span class="term">
1443 Deletes all information about a transmitting device.
1444 </dd><dt><span class="term">
1447 Offers additional configuration operations. See
1448 <a class="xref" href="#_setup" title="12.6. Setup">Section 12.6, “Setup”</a>.
1449 </dd><dt><span class="term">
1452 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>
1453 </dd><dt><span class="term">
1456 Shuts down AltosDroid.
1457 </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">
1460 Altus Metrum transmitters can be configured to operate
1461 at lower data rates to improve transmission range. If
1462 you have configured your device to do this, this menu
1463 item allows you to change the receiver to match.
1464 </dd><dt><span class="term">
1467 Selects which units used to report values.
1468 </dd><dt><span class="term">
1471 Displays a menu of map types and lets you select
1472 one. Hybrid maps include satellite images with a
1473 roadmap overlaid. Satellite maps dispense with the
1474 roadmap overlay. Roadmap shows just the roads. Terrain
1475 includes roads along with shadows indicating changes
1476 in elevation, and other geographical features.
1477 </dd><dt><span class="term">
1480 Select between online and offline maps. Online maps
1481 will show a <span class="emphasis"><em>move to current position</em></span> icon in the
1482 upper right corner, while offline maps will have
1483 copyright information all over the map. Otherwise,
1484 they’re pretty similar.
1485 </dd><dt><span class="term">
1488 Brings up a dialog allowing you to download offline
1489 map tiles so that you can have maps available even if
1490 you have no network connectivity at the launch site.
1491 </dd><dt><span class="term">
1494 This presents a dialog containing the current list of
1495 frequencies that will be show in the <span class="emphasis"><em>Select radio
1496 frequency</em></span> menu. You can change the label for existing
1497 frequencies, delete or add new frequencies.
1498 </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">
1501 Lets you configure the callsign used by AltosDroid to
1502 communicate with the flight computer. The callsign on
1503 the two devices must match or the communication will
1504 fail. This provides a modest amount of protection
1505 against accidentally controlling another persons
1507 </dd><dt><span class="term">
1510 This provides similar information to monitoring the
1511 telemetry stream from a flight computer in flight
1512 mode. The title of the application will change to
1513 include (idle) so you can tell this mode is active.
1514 </dd><dt><span class="term">
1517 Remotely reboots the flight computer. This is useful
1518 when the flight computers turned on while the airframe
1519 is horizontal and you want to restart the flight
1520 computers in pad mode after raising the airframe to
1522 </dd><dt><span class="term">
1525 Remotely control igniters for ground testing recovery
1527 </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
1528 monitoring display, providing separate tabs for each
1529 stage of your rocket flight along with a tab
1530 containing a map of the local area with icons marking
1531 the current location of the altimeter and the Android
1532 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
1533 the rocket is ready for flight. The first elements
1534 include red/green indicators, if any of these is red,
1535 you’ll want to evaluate whether the rocket is ready to
1536 launch.</p><p>When the pad tab is selected, the voice responses will
1537 include status changes to the igniters and GPS
1538 reception, letting you know if the rocket is still
1539 ready for launch.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1542 This indicates whether the Li-Po battery powering the
1543 transmitter has sufficient charge to last for the
1544 duration of the flight. A value of more than 3.8V is
1545 required for a <span class="emphasis"><em>GO</em></span> status.
1546 </dd><dt><span class="term">
1549 This indicates whether the Li-Po battery powering the
1550 TeleBT has sufficient charge to last for the duration
1551 of the flight. A value of more than 3.8V is required
1552 for a <span class="emphasis"><em>GO</em></span> status.
1553 </dd><dt><span class="term">
1556 This indicates whether there is space remaining
1557 on-board to store flight data for the upcoming
1558 flight. If you’ve downloaded data, but failed to erase
1559 flights, there may not be any space left. TeleMetrum
1560 and TeleMega can store multiple flights, depending on
1561 the configured maximum flight log size. TeleGPS logs
1562 data continuously. TeleMini v1.0 stores only a single
1563 flight, so it will need to be downloaded and erased
1564 after each flight to capture data. This only affects
1565 on-board flight logging; the altimeter will still
1566 transmit telemetry and fire ejection charges at the
1568 </dd><dt><span class="term">
1571 For a TeleMetrum or TeleMega device, this indicates
1572 whether the GPS receiver is currently able to compute
1573 position information. GPS requires at least 4
1574 satellites to compute an accurate position.
1575 </dd><dt><span class="term">
1578 For a TeleMetrum or TeleMega device, this indicates
1579 whether GPS has reported at least 10 consecutive
1580 positions without losing lock. This ensures that the
1581 GPS receiver has reliable reception from the
1583 </dd><dt><span class="term">
1586 This indicates whether the apogee igniter has
1587 continuity. If the igniter has a low resistance, then
1588 the voltage measured here will be close to the Li-Po
1589 battery voltage. A value greater than 3.2V is required
1590 for a <span class="emphasis"><em>GO</em></span> status.
1591 </dd><dt><span class="term">
1594 This indicates whether the main igniter has
1595 continuity. If the igniter has a low resistance, then
1596 the voltage measured here will be close to the Li-Po
1597 battery voltage. A value greater than 3.2V is required
1598 for a <span class="emphasis"><em>GO</em></span> status.
1599 </dd><dt><span class="term">
1602 This indicates whether the indicated additional pyro
1603 channel igniter has continuity. If the igniter has a
1604 low resistance, then the voltage measured here will be
1605 close to the Li-Po battery voltage. A value greater
1606 than 3.2V is required for a <span class="emphasis"><em>GO</em></span> status.
1607 </dd></dl></div><p>The Pad tab also shows the location of the Android
1608 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
1609 and spot a rocket while in flight. It displays speed
1610 and height data to monitor the health of the rocket,
1611 along with elevation, range and bearing to help locate
1612 the rocket in the sky.</p><p>While the Flight tab is displayed, the voice
1613 announcements will include current speed, height,
1614 elevation and bearing information.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1617 Shows current vertical speed. During descent, the
1618 speed values are averaged over a fairly long time to
1619 try and make them steadier.
1620 </dd><dt><span class="term">
1623 Shows the current height above the launch pad.
1624 </dd><dt><span class="term">
1627 Shows the maximum vertical speed seen during the
1629 </dd><dt><span class="term">
1632 Shows the maximum height above launch pad.
1633 </dd><dt><span class="term">
1636 This is the angle above the horizon from the android
1637 devices current position.
1638 </dd><dt><span class="term">
1641 The total distance from the android device to the
1642 rocket, including both ground distance and difference
1643 in altitude. Use this to gauge how large the rocket is
1644 likely to appear in the sky.
1645 </dd><dt><span class="term">
1648 This is the azimuth from true north for the rocket
1649 from the android device. Use this in combination with
1650 the Elevation value to help locate the rocket in the
1651 sky, or at least to help point the antenna in the
1652 general direction. This is provided in both degrees
1653 and a compass point (like West South West). You’ll
1654 want to know which direction is true north before
1655 launching your rocket.
1656 </dd><dt><span class="term">
1659 This shows the distance across the ground to the
1660 lat/lon where the rocket is located. Use this to
1661 estimate what is currently under the rocket.
1662 </dd><dt><span class="term">
1665 Displays the last known location of the rocket.
1666 </dd><dt><span class="term">
1669 This indicates whether the apogee igniter has
1670 continuity. If the igniter has a low resistance, then
1671 the voltage measured here will be close to the Li-Po
1672 battery voltage. A value greater than 3.2V is required
1673 for a <span class="emphasis"><em>GO</em></span> status.
1674 </dd><dt><span class="term">
1677 This indicates whether the main igniter has
1678 continuity. If the igniter has a low resistance, then
1679 the voltage measured here will be close to the Li-Po
1680 battery voltage. A value greater than 3.2V is required
1681 for a <span class="emphasis"><em>GO</em></span> status.
1682 </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
1683 recovering the rocket on the ground after flight.</p><p>While the Recover tab is displayed, the voice
1684 announcements will include distance along with either
1685 bearing or direction, depending on whether you are
1686 moving.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
1689 This is the azimuth from true north for the rocket
1690 from the android device. Use this in combination with
1691 the Elevation value to help locate the rocket in the
1692 sky, or at least to help point the antenna in the
1693 general direction. This is provided in both degrees
1694 and a compass point (like West South West). You’ll
1695 want to know which direction is true north before
1696 launching your rocket.
1697 </dd><dt><span class="term">
1700 When you are in motion, this provides the angle from
1701 your current direction of motion towards the rocket.
1702 </dd><dt><span class="term">
1705 Distance over the ground to the rocket.
1706 </dd><dt><span class="term">
1709 Displays the last known location of the rocket.
1710 </dd><dt><span class="term">
1713 Displays the location of the Android device.
1714 </dd><dt><span class="term">
1717 Shows the maximum height above launch pad seen during
1719 </dd><dt><span class="term">
1722 Shows the maximum vertical speed seen during the
1724 </dd><dt><span class="term">
1727 Shows the maximum vertical acceleration seen during
1729 </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
1730 rocket being tracked along with information needed to
1731 recover it.</p><p>On the map itself, icons showing the location of the
1732 android device along with the last known location of
1733 each tracker. A blue line is drawn from the android
1734 device location to the currently selected tracker.</p><p>Below the map, the distance and either bearing or
1735 direction along with the lat/lon of the target and the
1736 android device are shown</p><p>The Map tab provides the same voice announcements as
1737 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
1738 receives. To download that to a computer for use with
1739 AltosUI, remove the SD card from your Android device,
1740 or connect your device to your computer’s USB port and
1741 browse the files on that device. You will find
1742 <span class="emphasis"><em>.telem</em></span> files in the TeleMetrum directory that will
1743 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
1744 fundamental modes, “idle” and “flight”. Which of these modes
1745 the firmware operates in is determined at start up
1748 TeleMetrum, TeleMega and EasyMega, which have accelerometers, the mode is
1749 controlled by the orientation of the
1750 rocket (well, actually the board, of course…) at the time
1751 power is switched on. If the rocket is “nose up”, then
1752 the flight computer assumes it’s on a rail or rod being prepared for
1753 launch, so the firmware chooses flight mode. However, if the
1754 rocket is more or less horizontal, the firmware instead enters
1759 accelerometer we can use to determine orientation, “idle” mode
1760 is selected if the board is connected via USB to a computer,
1761 otherwise the board enters “flight” mode.
1763 selects “idle” mode if it receives a command packet
1765 first five seconds of operation.</p><p>At power on, the altimeter will beep out the battery voltage
1766 to the nearest tenth of a volt. Each digit is represented by
1767 a sequence of short “dit” beeps, with a pause between
1768 digits. A zero digit is represented with one long “dah”
1769 beep. Then there will be a short pause while the altimeter
1770 completes initialization and self test, and decides which mode
1771 to enter next.</p><p>In flight or “pad” mode, the altimeter engages the flight
1772 state machine, goes into transmit-only mode to send telemetry,
1773 and waits for launch to be detected. Flight mode is indicated
1774 by an “di-dah-dah-dit” (“P” for pad) on the beeper or lights,
1775 followed by beeps or flashes indicating the state of the
1776 pyrotechnic igniter continuity. One beep/flash indicates
1777 apogee continuity, two beeps/flashes indicate main continuity,
1778 three beeps/flashes indicate both apogee and main continuity,
1779 and one longer “brap” sound which is made by rapidly
1780 alternating between two tones indicates no continuity. For a
1781 dual deploy flight, make sure you’re getting three beeps or
1782 flashes before launching! For apogee-only or motor eject
1783 flights, do what makes sense.</p><p>If idle mode is entered, you will hear an audible “di-dit” or
1784 see two short flashes (“I” for idle), and the flight state
1785 machine is disengaged, thus no ejection charges will fire.
1786 The altimeters also listen for the radio link when in idle
1787 mode for requests sent via TeleDongle. Commands can be issued
1788 in idle mode over either USB or the radio link
1790 TeleMini only has the radio link.
1791 Idle mode is useful for configuring the altimeter, for
1792 extracting data from the on-board storage chip after
1793 flight, and for ground testing pyro charges.</p><p>In “Idle” and “Pad” modes, once the mode indication
1794 beeps/flashes and continuity indication has been sent, if
1795 there is no space available to log the flight in on-board
1796 memory, the flight computer will emit a warbling tone (much
1797 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
1798 the audio signals used.</p><p>Once landed, the flight computer will signal that by emitting
1799 the “Landed” sound described above, after which it will beep
1800 out the apogee height (in meters). Each digit is represented
1801 by a sequence of short “dit” beeps, with a pause between
1802 digits. A zero digit is represented with one long “dah”
1803 beep. The flight computer will continue to report landed mode
1804 and beep out the maximum height until turned off.</p><p>One “neat trick” of particular value when TeleMetrum, TeleMega
1805 or EasyMega are used with
1806 very large air-frames, is that you can power the board up while the
1807 rocket is horizontal, such that it comes up in idle mode. Then you can
1808 raise the air-frame to launch position, and issue a <span class="emphasis"><em>reset</em></span> command
1809 via TeleDongle over the radio link to cause the altimeter to reboot and
1810 come up in flight mode. This is much safer than standing on the top
1811 step of a rickety step-ladder or hanging off the side of a launch
1812 tower with a screw-driver trying to turn on your avionics before
1813 installing igniters!</p><p>TeleMini is configured solely via the radio link. Of course, that
1814 means you need to know the TeleMini radio configuration values
1815 or you won’t be able to communicate with it. For situations
1816 when you don’t have the radio configuration values,
1818 offers an <span class="emphasis"><em>emergency recovery</em></span> mode. In this mode,
1820 configured as follows:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
1821 Sets the radio frequency to 434.550MHz
1822 </li><li class="listitem">
1823 Sets the radio calibration back to the factory value.
1824 </li><li class="listitem">
1825 Sets the callsign to N0CALL
1826 </li><li class="listitem">
1827 Does not go to <span class="emphasis"><em>pad</em></span> mode after five seconds.
1828 </li></ul></div><p>To get into <span class="emphasis"><em>emergency recovery</em></span> mode, first find the row of
1829 four small holes opposite the switch wiring. Using a short
1830 piece of small gauge wire, connect the outer two holes
1831 together, then power TeleMini up. Once the red LED is lit,
1832 disconnect the wire and the board should signal that it’s in
1833 <span class="emphasis"><em>idle</em></span> mode after the initial five second startup
1834 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
1835 complete explanation of how GPS works is beyond the scope of
1836 this manual, but the bottom line is that the GPS receiver
1837 needs to lock onto at least four satellites to obtain a solid
1838 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
1839 battery is connected. This allows the receiver to “warm start” on
1840 the launch rail much faster than if every power-on were a GPS
1841 “cold start”. In typical operations, powering up
1842 on the flight line in idle mode while performing final air-frame
1843 preparation will be sufficient to allow the GPS receiver to cold
1844 start and acquire lock. Then the board can be powered down during
1845 RSO review and installation on a launch rod or rail. When the board
1846 is turned back on, the GPS system should lock very quickly, typically
1847 long before igniter installation and return to the flight line are
1848 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
1849 ability to create a two way command link between TeleDongle
1850 and an altimeter using the digital radio transceivers
1851 built into each device. This allows you to interact with the
1852 altimeter from afar, as if it were directly connected to the
1853 computer.</p><p>Any operation which can be performed with a flight computer can
1854 either be done with the device directly connected to the
1855 computer via the USB cable, or through the radio
1856 link. TeleMini doesn’t provide a USB connector and so it is
1857 always communicated with over radio. Select the appropriate
1858 TeleDongle device when the list of devices is presented and
1859 AltosUI will interact with an altimeter over the radio link.</p><p>One oddity in the current interface is how AltosUI selects the
1860 frequency for radio communications. Instead of providing
1861 an interface to specifically configure the frequency, it uses
1862 whatever frequency was most recently selected for the target
1863 TeleDongle device in Monitor Flight mode. If you haven’t ever
1864 used that mode with the TeleDongle in question, select the
1865 Monitor Flight button from the top level UI, and pick the
1866 appropriate TeleDongle device. Once the flight monitoring
1867 window is open, select the desired frequency and then close it
1868 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">
1869 Save Flight Data—Recover flight data from the
1870 rocket without opening it up.
1871 </li><li class="listitem">
1872 Configure altimeter apogee delays, main deploy
1873 heights and additional pyro event conditions to
1874 respond to changing launch conditions. You can also
1875 <span class="emphasis"><em>reboot</em></span> the altimeter. Use this to remotely enable
1876 the flight computer by turning TeleMetrum or
1877 TeleMega on in “idle” mode, then once the air-frame
1878 is oriented for launch, you can reboot the
1879 altimeter and have it restart in pad mode without
1880 having to climb the scary ladder.
1881 </li><li class="listitem">
1882 Fire Igniters—Test your deployment charges without snaking
1883 wires out through holes in the air-frame. Simply assemble the
1884 rocket as if for flight with the apogee and main charges
1885 loaded, then remotely command the altimeter to fire the
1887 </li></ul></div><p>Operation over the radio link for configuring an
1888 altimeter, ground testing igniters, and so forth uses
1889 the same RF frequencies as flight telemetry. To
1890 configure the desired TeleDongle frequency, select the
1891 monitor flight tab, then use the frequency selector
1892 and close the window before performing other desired
1893 radio operations.</p><p>The flight computers only enable radio commanding in
1894 <span class="emphasis"><em>idle</em></span> mode. TeleMetrum and TeleMega use the
1895 accelerometer to detect which orientation they start
1896 up in, so make sure you have the flight computer lying
1897 horizontally when you turn it on. Otherwise, it will
1898 start in <span class="emphasis"><em>pad</em></span> mode ready for flight, and will not be
1899 listening for command packets from TeleDongle.</p><p>TeleMini listens for a command packet for five seconds
1900 after first being turned on, if it doesn’t hear
1901 anything, it enters <span class="emphasis"><em>pad</em></span> mode, ready for flight and
1902 will no longer listen for command packets. The easiest
1903 way to connect to TeleMini is to initiate the command
1904 and select the TeleDongle device. At this point, the
1905 TeleDongle will be attempting to communicate with the
1906 TeleMini. Now turn TeleMini on, and it should
1907 immediately start communicating with the TeleDongle
1908 and the desired operation can be performed.</p><p>You can monitor the operation of the radio link by watching the
1909 lights on the devices. The red LED will flash each time a packet
1910 is transmitted, while the green LED will light up on TeleDongle when
1911 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
1912 for flight is ground testing the recovery system.
1914 to the bi-directional radio link central to the Altus Metrum system,
1915 this can be accomplished in a TeleMega, TeleMetrum or TeleMini equipped rocket
1916 with less work than you may be accustomed to with other systems. It
1917 can even be fun!</p><p>Just prep the rocket for flight, then power up the altimeter
1919 mode (placing air-frame horizontal for TeleMetrum or TeleMega, or
1920 selecting the Configure Altimeter tab for TeleMini).
1922 the firmware to go into “idle” mode, in which the normal flight
1923 state machine is disabled and charges will not fire without
1925 You can now command the altimeter to fire the apogee
1926 or main charges from a safe distance using your
1927 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
1928 RF transceiver, but it’s not a full duplex system;
1929 each end can only be transmitting or receiving at any
1930 given moment. So we had to decide how to manage the
1931 link.</p><p>By design, the altimeter firmware listens for the
1932 radio link when it’s in “idle mode”, which allows us
1933 to use the radio link to configure the rocket, do
1934 things like ejection tests, and extract data after a
1935 flight without having to crack open the air-frame.
1936 However, when the board is in “flight mode”, the
1937 altimeter only transmits and doesn’t listen at all.
1938 That’s because we want to put ultimate priority on
1939 event detection and getting telemetry out of the
1940 rocket through the radio in case the rocket crashes
1941 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
1942 like APRS because they’re just too inefficient. The
1943 GFSK modulation we use is FSK with the base-band
1944 pulses passed through a Gaussian filter before they go
1945 into the modulator to limit the transmitted bandwidth.
1946 When combined with forward error correction and
1947 interleaving, this allows us to have a very robust
1948 19.2 kilobit data link with only 10-40 milliwatts of
1949 transmit power, a whip antenna in the rocket, and a
1950 hand-held Yagi on the ground. We’ve had flights to
1951 above 21k feet AGL with great reception, and
1952 calculations suggest we should be good to well over
1953 40k feet AGL with a 5-element yagi on the ground with
1954 our 10mW units and over 100k feet AGL with the 40mW
1955 devices. We hope to fly boards to higher altitudes
1956 over time, and would of course appreciate customer
1957 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
1958 interval between APRS packets can be configured. As each APRS
1959 packet takes a full second to transmit, we recommend an
1960 interval of at least 5 seconds to avoid consuming too much
1961 battery power or radio channel bandwidth. You can configure
1962 the APRS interval using AltosUI; that process is described in
1963 <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
1964 position report data formats. The compressed format
1965 provides for higher position precision and shorter
1966 packets than the uncompressed APRS format. We’ve found
1967 some older APRS receivers that do not handle the
1968 compressed format. The Kenwood TH-72A requires the use
1969 of uncompressed format to display altitude information
1970 correctly. The Yaesu FT1D requires the use of
1971 compressed format to display altitude information.</p><p>APRS packets include an SSID (Secondary Station Identifier)
1972 field that allows one operator to have multiple
1973 transmitters. AltOS allows you to set this to a single digit
1974 from 0 to 9, allowing you to fly multiple transmitters at the
1975 same time while keeping the identify of each one separate in
1976 the receiver. By default, the SSID is set to the last digit of
1977 the device serial number.</p><p>The APRS packet format includes a comment field that
1978 can have arbitrary text in it. AltOS uses this to send
1979 status information as shown in the following table.</p><div class="table"><a id="idm2048"></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
1980 satellites in view, a primary battery at 4.0V, and
1981 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
1982 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
1983 any connected igniters are above 3.5V
1984 and GPS is locked with at least 5 or 6 satellites in
1985 view before flying. If GPS is switching between L and
1986 U regularly, then it doesn’t have a good lock and you
1987 should wait until it becomes stable.</p><p>If the GPS receiver loses lock, the APRS data
1988 transmitted will contain the last position for which
1989 GPS lock was available. You can tell that this has
1990 happened by noticing that the GPS status character
1991 switches from <span class="emphasis"><em>L</em></span> to <span class="emphasis"><em>U</em></span>. Before GPS has locked, APRS
1992 will transmit zero for latitude, longitude and
1993 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
1994 very simple. Even on our baro-only TeleMini and
1995 EasyMini boards, the use of a Kalman filter means
1996 there is no need to set a “mach delay”. All of the
1997 configurable parameters can be set using AltosUI. Read
1998 <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.
1999 When handled gently and properly installed in an air-frame, they
2000 will deliver impressive results. However, as with all electronic
2001 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
2002 extraordinary power density. This is great because we can fly with
2003 much less battery mass than if we used alkaline batteries or previous
2004 generation rechargeable batteries… but if they are punctured
2005 or their leads are allowed to short, they can and will release their
2006 energy very rapidly!
2007 Thus we recommend that you take some care when handling our batteries
2008 and consider giving them some extra protection in your air-frame. We
2009 often wrap them in suitable scraps of closed-cell packing foam before
2010 strapping them down, for example.</p></div><p>The barometric sensors used on all of our flight computers are
2011 sensitive to sunlight. In normal mounting situations, the baro sensor
2012 and all of the other surface mount components
2013 are “down” towards whatever the underlying mounting surface is, so
2014 this is not normally a problem. Please consider this when designing an
2015 installation in an air-frame with a see-through plastic payload bay. It
2016 is particularly important to
2017 consider this with TeleMini v1.0, both because the baro sensor is on the
2018 “top” of the board, and because many model rockets with payload bays
2019 use clear plastic for the payload bay! Replacing these with an opaque
2020 cardboard tube, painting them, or wrapping them with a layer of masking
2021 tape are all reasonable approaches to keep the sensor out of direct
2022 sunlight.</p><p>The barometric sensor sampling port must be able to “breathe”,
2023 both by not being covered by foam or tape or other materials that might
2024 directly block the hole on the top of the sensor, and also by having a
2025 suitable static vent to outside air.</p><p>As with all other rocketry electronics, Altus Metrum altimeters must
2026 be protected from exposure to corrosive motor exhaust and ejection
2027 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
2029 programmed directly over their USB connectors (self
2031 TeleMetrum v1, TeleMini v1.0 and TeleDongle v0.2 are
2032 all programmed by using another device as a programmer (pair
2033 programming). It’s important to recognize which kind of devices
2034 you have before trying to reprogram them.</p><p>You may wish to begin by ensuring you have current firmware
2035 images. These are distributed as part of the AltOS software
2036 bundle that also includes the AltosUI ground station program.
2037 Newer ground station versions typically work fine with older
2038 firmware versions, so you don’t need to update your devices
2039 just to try out new software features. You can always
2040 download the most recent version from
2041 <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
2042 connecting them to your computer over USB.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
2043 Attach a battery if necessary and power switch to
2044 the target device. Power up the device.
2045 </li><li class="listitem">
2046 Using a Micro USB cable, connect the target device to your
2047 computer’s USB socket.
2048 </li><li class="listitem">
2049 Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from the File menu.
2050 </li><li class="listitem">
2051 Select the target device in the Device Selection dialog.
2052 </li><li class="listitem">
2053 Select the image you want to flash to the device,
2054 which should have a name in the form
2055 <product>-v<product-version>-<software-version>.ihx,
2056 such as EasyMini-v1.0-1.6.0.ihx.
2057 </li><li class="listitem">
2058 Make sure the configuration parameters are
2059 reasonable looking. If the serial number and/or RF
2060 configuration values aren’t right, you’ll need to
2062 </li><li class="listitem">
2063 Hit the <span class="emphasis"><em>OK</em></span> button and the software should proceed
2064 to flash the device with new firmware, showing a
2066 </li><li class="listitem">
2067 Verify that the device is working by using the
2068 <span class="emphasis"><em>Configure Altimeter</em></span> or <span class="emphasis"><em>Configure Groundstation</em></span>
2069 item to check over the configuration.
2070 </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
2071 unable to boot. Not to worry, you can force the device to
2072 start the boot loader instead, which will let you try to
2073 flash the device again.</p><p>On each device, connecting two pins from one of the exposed
2074 connectors will force the boot loader to start, even if the
2075 regular operating system has been corrupted in some way.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
2078 Connect pin 6 and pin 1 of the companion
2079 connector. Pin 1 can be identified by the square pad
2080 around it, and then the pins could sequentially across
2081 the board. Be very careful to <span class="strong"><strong>not</strong></span> short pin 8 to
2082 anything as that is connected directly to the
2083 battery. Pin 7 carries 3.3V and the board will crash
2084 if that is connected to pin 1, but shouldn’t damage
2086 </dd><dt><span class="term">
2089 Connect pin 6 and pin 1 of the companion
2090 connector. Pin 1 can be identified by the square pad
2091 around it, and then the pins could sequentially across
2092 the board. Be very careful to <span class="strong"><strong>not</strong></span> short pin 8 to
2093 anything as that is connected directly to the
2094 battery. Pin 7 carries 3.3V and the board will crash
2095 if that is connected to pin 1, but shouldn’t damage
2097 </dd><dt><span class="term">
2100 Connect pin 6 and pin 1 of the companion
2101 connector. Pin 1 can be identified by the square pad
2102 around it, and then the pins could sequentially across
2103 the board. Be very careful to <span class="strong"><strong>not</strong></span> short pin 8 to
2104 anything as that is connected directly to the
2105 battery. Pin 7 carries 3.3V and the board will crash
2106 if that is connected to pin 1, but shouldn’t damage
2108 </dd><dt><span class="term">
2111 Connect pin 6 and pin 1 of the debug connector, which
2112 is the six holes next to the beeper. Pin 1 can be
2113 identified by the square pad around it, and then the
2114 pins could sequentially across the board, making Pin 6
2115 the one on the other end of the row.
2116 </dd><dt><span class="term">
2119 Connect pin 32 on the CPU to ground. Pin 32 is closest
2120 to the USB wires on the row of pins towards the center
2121 of the board. Ground is available on the capacitor
2122 next to it, on the end towards the USB wires.
2123 </dd></dl></div><p>Once you’ve located the right pins:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
2124 Turn the altimeter power off.
2125 </li><li class="listitem">
2127 </li><li class="listitem">
2128 Connect the indicated terminals together with a
2129 short piece of wire. Take care not to accidentally
2130 connect anything else.
2131 </li><li class="listitem">
2133 </li><li class="listitem">
2134 Turn the board power on.
2135 </li></ol></div><p>The board should now be visible over USB as
2136 <span class="emphasis"><em>AltosFlash</em></span> and be ready to receive firmware. Once
2137 the board has been powered up, you can remove the
2138 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
2139 a TeleMetrum v1.0, TeleBT v1.0 or TeleDongle v0.2 as a
2140 programmer to update a pair programmed device. Due to
2141 limited memory resources in the cc1111, we don’t
2142 support programming directly over USB for these
2143 devices.</p><p>If you need to update the firmware on a TeleDongle
2144 v0.2, we recommend updating the altimeter first,
2145 before updating TeleDongle. However, note that
2146 TeleDongle rarely need to be updated. Any firmware
2147 version 1.0.1 or later will work, version 1.2.1 may
2148 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">
2149 Find the <span class="emphasis"><em>programming cable</em></span> that you got as
2150 part of the starter kit, that has a red
2151 8-pin MicroMaTch connector on one end and a
2152 red 4-pin MicroMaTch connector on the other
2154 </li><li class="listitem">
2155 Take the 2 screws out of the TeleDongle v0.2
2156 or TeleBT v1.0 case to get access to the
2158 </li><li class="listitem">
2159 Plug the 8-pin end of the programming cable
2160 to the matching connector on the TeleDongle
2161 v0.2 or TeleBT v1.0, and the 4-pin end to
2162 the matching connector on the TeleMetrum.
2163 Note that each MicroMaTch connector has an
2164 alignment pin that goes through a hole in
2165 the PC board when you have the cable
2167 </li><li class="listitem">
2168 Attach a battery to the TeleMetrum board.
2169 </li><li class="listitem">
2170 Plug the TeleDongle v0.2 or TeleBT v1.0 into
2171 your computer’s USB port, and power up the
2173 </li><li class="listitem">
2174 Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from
2176 </li><li class="listitem">
2177 Pick the TeleDongle v0.2 or TeleBT v1.0
2178 device from the list, identifying it as the
2180 </li><li class="listitem">
2181 Select the image you want put on the
2182 TeleMetrum, which should have a name in the
2183 form telemetrum-v1.2-1.0.0.ihx. It should
2184 be visible in the default directory, if not
2185 you may have to poke around your system to
2187 </li><li class="listitem">
2188 Make sure the configuration parameters are
2189 reasonable looking. If the serial number
2190 and/or RF configuration values aren’t right,
2191 you’ll need to change them.
2192 </li><li class="listitem">
2193 Hit the <span class="emphasis"><em>OK</em></span> button and the software should
2194 proceed to flash the TeleMetrum with new
2195 firmware, showing a progress bar.
2196 </li><li class="listitem">
2197 Confirm that the TeleMetrum board seems to
2198 have updated OK, which you can do by
2199 plugging in to it over USB and using a
2200 terminal program to connect to the board and
2201 issue the <span class="emphasis"><em>v</em></span> command to check the version,
2203 </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_v1_0_firmware"></a>C.2.2. Updating TeleMini v1.0 Firmware</h3></div></div></div><p>You’ll need a special <span class="emphasis"><em>programming cable</em></span> to
2204 reprogram the TeleMini v1.0. You can make your own
2205 using an 8-pin MicroMaTch connector on one end
2206 and a set of four pins on the other.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
2207 Take the 2 screws out of the TeleDongle v0.2
2208 or TeleBT v1.0 case to get access to the
2210 </li><li class="listitem">
2211 Plug the 8-pin end of the programming cable
2212 to the matching connector on the TeleDongle
2213 v0.2 or TeleBT v1.0, and the 4-pins into the
2214 holes in the TeleMini v1.0 circuit board. Note
2215 that the MicroMaTch connector has an
2216 alignment pin that goes through a hole in
2217 the PC board when you have the cable
2218 oriented correctly, and that pin 1 on the
2219 TeleMini v1.0 board is marked with a square pad
2220 while the other pins have round pads.
2221 </li><li class="listitem">
2222 Attach a battery to the TeleMini v1.0 board.
2223 </li><li class="listitem">
2224 Plug the TeleDongle v0.2 or TeleBT v1.0 into
2225 your computer’s USB port, and power up the
2227 </li><li class="listitem">
2228 Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from
2230 </li><li class="listitem">
2231 Pick the TeleDongle v0.2 or TeleBT v1.0
2232 device from the list, identifying it as the
2234 </li><li class="listitem">
2235 Select the image you want put on the
2236 TeleMini v1.0, which should have a name in the
2237 form telemini-v1.0-1.0.0.ihx. It should be
2238 visible in the default directory, if not you
2239 may have to poke around your system to find
2241 </li><li class="listitem">
2242 Make sure the configuration parameters are
2243 reasonable looking. If the serial number
2244 and/or RF configuration values aren’t right,
2245 you’ll need to change them.
2246 </li><li class="listitem">
2247 Hit the <span class="emphasis"><em>OK</em></span> button and the software should
2248 proceed to flash the TeleMini v1.0 with new
2249 firmware, showing a progress bar.
2250 </li><li class="listitem">
2251 Confirm that the TeleMini v1.0 board seems to
2252 have updated OK, which you can do by
2253 configuring it over the radio link through
2254 the TeleDongle, or letting it come up in
2255 “flight” mode and listening for telemetry.
2256 </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
2257 updating TeleMetrum v1.x or TeleMini v1.0 firmware, but you
2258 use either a TeleMetrum v1.x, TeleDongle v0.2 or
2259 TeleBT v1.0 as the programmer.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
2260 Find the <span class="emphasis"><em>programming cable</em></span> that you got as part of
2261 the starter kit, that has a red 8-pin MicroMaTch
2262 connector on one end and a red 4-pin MicroMaTch
2263 connector on the other end.
2264 </li><li class="listitem">
2265 Find the USB cable that you got as part of the
2266 starter kit, and plug the “mini” end in to the
2267 mating connector on TeleMetrum v1.x, TeleDongle v0.2
2269 </li><li class="listitem">
2270 Take the 2 screws out of the TeleDongle v0.2 or
2271 TeleBT v1.0 case to get access to the circuit board.
2272 </li><li class="listitem">
2273 Plug the 8-pin end of the programming cable to the
2274 matching connector on the programmer, and the 4-pin
2275 end to the matching connector on the TeleDongle
2276 v0.2. Note that each MicroMaTch connector has an
2277 alignment pin that goes through a hole in the PC
2278 board when you have the cable oriented correctly.
2279 </li><li class="listitem">
2280 Attach a battery to the TeleMetrum v1.x board if
2282 </li><li class="listitem">
2283 Plug both the programmer and the TeleDongle into
2284 your computer’s USB ports, and power up the
2286 </li><li class="listitem">
2287 Run AltosUI, and select <span class="emphasis"><em>Flash Image</em></span> from the File
2289 </li><li class="listitem">
2290 Pick the programmer device from the list,
2291 identifying it as the programming device.
2292 </li><li class="listitem">
2293 Select the image you want put on the TeleDongle
2294 v0.2, which should have a name in the form
2295 teledongle-v0.2-1.0.0.ihx. It should be visible in
2296 the default directory, if not you may have to poke
2297 around your system to find it.
2298 </li><li class="listitem">
2299 Make sure the configuration parameters are
2300 reasonable looking. If the serial number and/or RF
2301 configuration values aren’t right, you’ll need to
2302 change them. The TeleDongle v0.2 serial number is
2303 on the “bottom” of the circuit board, and can
2304 usually be read through the translucent blue plastic
2305 case without needing to remove the board from the
2307 </li><li class="listitem">
2308 Hit the <span class="emphasis"><em>OK</em></span> button and the software should proceed
2309 to flash the TeleDongle v0.2 with new firmware,
2310 showing a progress bar.
2311 </li><li class="listitem">
2312 Confirm that the TeleDongle v0.2 board seems to have
2313 updated OK, which you can do by plugging in to it
2314 over USB and using a terminal program to connect to
2315 the board and issue the <span class="emphasis"><em>v</em></span> command to check the
2316 version, etc. Once you’re happy, remove the
2317 programming cable and put the cover back on the
2319 </li></ol></div><p>If something goes wrong, give it another try.</p><p>Be careful removing the programming cable from the
2320 locking 8-pin connector on TeleMetrum. You’ll need a
2321 fingernail or perhaps a thin screwdriver or knife
2322 blade to gently pry the locking ears out slightly to
2323 extract the connector. We used a locking connector on
2324 TeleMetrum to help ensure that the cabling to
2325 companion boards used in a rocket don’t ever come
2326 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
2327 during ascent and 10 samples per second during
2328 descent, except for TeleMini v1.0, which records ascent at 10 samples
2329 per second and descent at 1 sample per second.
2331 an on-board flash memory part, which can be partitioned into
2332 several equal-sized blocks, one for each flight.</p><div class="table"><a id="idm2299"></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>TeleMini v3.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>512kB</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>5</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,
2333 each of a fixed maximum size. Increase the maximum size of
2334 each log and you reduce the number of flights that can be
2335 stored. Decrease the size and you can store more flights.</p><p>Configuration data is also stored in the flash memory on
2340 of flash space. This configuration space is not available
2341 for storing flight log data.</p><p>TeleMetrum v2.0, TeleMega and EasyMega
2342 store configuration data in a bit of eeprom available within
2343 the processor chip, leaving that space available in flash for
2344 more flight data.</p><p>To compute the amount of space needed for a single flight, you
2345 can multiply the expected ascent time (in seconds) by 100
2346 times bytes-per-sample, multiply the expected descent time (in
2347 seconds) by 10 times the bytes per sample and add the two
2348 together. That will slightly under-estimate the storage (in
2349 bytes) needed for the flight.
2350 For instance, a TeleMetrum v2.0 flight spending
2351 20 seconds in ascent and 150 seconds in descent will take
2352 about (20 * 1600) + (150 * 160) = 56000 bytes of storage. You
2353 could store dozens of these flights in the on-board flash.</p><p>The default size allows for several flights on each flight
2354 computer, except for TeleMini v1.0, which
2355 only holds data for a single flight.
2356 You can adjust the size.</p><p>Altus Metrum flight computers will not overwrite existing
2357 flight data, so be sure to download flight data and erase it
2358 from the flight computer before it fills up. The flight
2359 computer will still successfully control the flight even if it
2360 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
2361 production and retired.</p><div class="table"><a id="idm2394"></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>TeleMini v3.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>512kB</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>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="idm2587"></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_8_5"></a>F.1. Release Notes for Version 1.8.5</h2></div></div></div><p>Version 1.8.5 includes fixes to the ground software support
2362 for TeleBT v4, along with a few other minor updates.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos"></a>F.1.1. AltOS</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2363 Fix startup beeps that indicate sensor failures.
2364 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_telegps"></a>F.1.2. AltosUI, TeleGPS</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2365 When updating device firmware, make sure selected firmware
2366 matches target device.
2367 </li><li class="listitem">
2368 Correct Bluetooth device matching when looking for TeleBT
2370 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_8_4"></a>F.2. Release Notes for Version 1.8.4</h2></div></div></div><p>Version 1.8.4 includes support for EasyMini version 2.0</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_2"></a>F.2.1. AltOS</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2371 Support for EasyMini version 2.0 hardware.
2372 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_8_3"></a>F.3. Release Notes for Version 1.8.3</h2></div></div></div><p>Version 1.8.3 includes support for TeleMega version 3.0 along
2373 with two important flight computer fixes. This version also
2374 changes KML export data to make Tripoli Record reporting
2375 better and some updates to graph presentation and data
2376 downloading.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_3"></a>F.3.1. AltOS</h3></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_altos_new_features"></a>AltOS New Features</h4></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2377 Support for TeleMega version 3.0 hardware.
2378 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_altos_bug_fixes"></a>AltOS Bug Fixes</h4></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2379 Ground testing EasyMega and TeleMega additional pyro
2380 channels could result in a sticky <span class="emphasis"><em>fired</em></span> status which would
2381 prevent these channels from firing on future flights.
2382 </li><li class="listitem">
2383 Corrupted flight log records could prevent future flights
2384 from capturing log data.
2385 </li><li class="listitem">
2386 Fixed saving of pyro configuration that ended with
2387 <span class="emphasis"><em>Descending</em></span>.
2388 </li></ul></div></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><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_altosui_new_features"></a>AltosUI New Features</h4></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2389 Support for TeleMega version 3.0.
2390 </li><li class="listitem">
2391 Graph lines have improved appearance to make them easier to
2392 distinguish. Markers may be placed at data points to show
2393 captured recorded data values.
2394 </li><li class="listitem">
2395 Graphing offers the ability to adjust the smoothing of
2396 computed speed and acceleration data.
2397 </li><li class="listitem">
2398 The download dialog now offers to graph new flights, checks
2399 for existing files to avoid overwriting data and reports if
2400 there are checksum errors in the downloaded data.
2401 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_altosui_telegps_bug_fixes"></a>AltosUI/TeleGPS Bug Fixes</h4></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2402 Restore TeleGPS tracking behavior.
2403 </li><li class="listitem">
2404 Display flight computer call sign and serial number in
2405 Monitor Idle mode instead of ground station values.
2406 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a id="_altosui_and_telegps_changes"></a>AltosUI and TeleGPS Changes</h4></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2407 KML export now reports both barometric and GPS altitude data
2408 to make it more useful for Tripoli record reporting.
2409 </li><li class="listitem">
2410 CSV export now includes TeleMega/EasyMega pyro voltages and
2412 </li></ul></div><p></p></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_8_2"></a>F.4. Release Notes for Version 1.8.2</h2></div></div></div><p>Version 1.8.2 includes support for TeleGPS version 2.0 along
2413 with accelerometer recalibration support in AltosUI.</p><p>1.8.2 also contains a couple of minor fixes for AltosUI when
2414 analyzing saved data files.</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">
2415 Support for TeleGPS version 2.0 hardware.
2416 </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 New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2417 Support for TeleGPS version 2.0.
2418 </li><li class="listitem">
2419 Accelerometer re-calibration user interface.
2420 </li></ul></div><p>AltosUI and TeleGPS Bug Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2421 Prevent some crashes when reading older saved flight data
2422 for graphing or KML export.
2423 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_8_1"></a>F.5. Release Notes for Version 1.8.1</h2></div></div></div><p>Version 1.8.1 includes an important bug fix for Apogee Lockout
2424 operation in all flight computers. Anyone using this option
2425 must update firmware.</p><p>This release also contains a change in how flight computers
2426 with accelerometers deal with speeds around and above Mach
2427 1. In previous versions, the flight computer would completely
2428 disregard the barometric sensor above 330m/s (around Mach
2429 1). Now, the data from the barometric sensor is reduced in
2430 effect without ever going away entirely. This prevents early
2431 drogue deployment for flights which spend considerable time
2432 above Mach 1.</p><p>1.8.1 also contains a couple of minor fixes for AltosUI when
2433 analyzing saved data files.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_5"></a>F.5.1. AltOS</h3></div></div></div><p>AltOS Bug Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2434 Handle time value wrapping in Apogee Lockout
2435 correctly. Without this, apogee lockout would sometimes
2436 prevent any drogue charge from firing.
2437 </li><li class="listitem">
2438 Change Kalman filter on flight computers with accelerometer
2439 to continue using the barometric sensor even at high speeds
2440 to avoid unintentional drogue deployment during
2442 </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 New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2443 Add new <span class="emphasis"><em>Huge</em></span> font size to make text even bigger on high
2444 resolution monitors.
2445 </li></ul></div><p>AltosUI Bug Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2446 Prevent some crashes when reading older saved flight data
2447 for graphing or KML export.
2448 </li><li class="listitem">
2449 Load frequency preference at startup. The loading code was
2450 broken, so you’d see only the default frequencies.
2451 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_8"></a>F.6. Release Notes for Version 1.8</h2></div></div></div><p>Version 1.8 includes support for our new TeleBT v4.0 ground
2452 station, updates for data analysis in our ground station
2453 software and bug fixes in in the flight software for all our
2454 boards 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">
2455 Add support for TeleBT v4.0 boards.
2456 </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 New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2457 Add support for TeleBT v4.0 hardware
2458 </li><li class="listitem">
2459 Rewrite graphing and export functions. This code now handles
2460 each data series separately so that graphs are drawn
2461 correctly. Smoothing now uses a filter that looks both
2462 forward and backwards in time to make computed speed and
2463 acceleration data more accurate.
2464 </li></ul></div><p>AltosUI Bug Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2465 Correct axis labeling of magnetic sensor in TeleMega and
2466 EasyMega. The Y and Z axes were flipped.
2467 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_7"></a>F.7. Release Notes for Version 1.7</h2></div></div></div><p>Version 1.7 includes support for our new TeleMini v3.0
2468 flight computer and bug fixes in in the flight software for all our boards
2469 and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_7"></a>F.7.1. AltOS</h3></div></div></div><p>AltOS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2470 Add support for TeleMini v3.0 boards.
2471 </li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2472 Fix interrupt priorities on STM32L processors. Run timer
2473 interrupt at lowest priority so that device interrupts get
2475 </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 New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2476 Add support for TeleMini v3.0 hardware
2477 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6_8"></a>F.8. Release Notes for Version 1.6.8</h2></div></div></div><p>Version 1.6.8 fixes a TeleMega and TeleMetrum v2.0 bug where
2478 the device could stop logging data and transmitting
2479 telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum
2480 v2.0 users should update their flight firmware.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_8"></a>F.8.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2481 Fix STM32L DMA driver to work around STM32L SoC DMA priority
2482 issue t lock-up in the logging or radio code, either of
2483 which could stop data logging and telemetry.
2484 </li><li class="listitem">
2485 Avoid having TeleBT battery status values smash telemetry
2486 packet data by holding a lock during both operations.
2487 </li><li class="listitem">
2488 Don’t start reporting <span class="emphasis"><em>flight 0</em></span> when the log fills in
2490 </li></ul></div><p>AltOS changes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2491 Flash LEDS on all products briefly during power up so that
2492 they can be tested during production.
2493 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_telegps_and_altosdroid_applications"></a>F.8.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">
2494 Re-enable go/no-go entries after they’ve been disabled due
2495 to lack of data. If telemetry information is delayed when
2496 the Ui starts up, sometimes important fields would get
2497 disabled to never re-appear.
2498 </li><li class="listitem">
2499 Deal with ground station failure better during Configure
2500 Ground Station operation by cleaning up pending operations.
2501 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6_5"></a>F.9. 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
2502 the device would often stop logging data and transmitting
2503 telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum
2504 v2.0 users should update their flight firmware.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_9"></a>F.9.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2505 Fix STM32L SPI driver to prevent lock-up in the logging or
2506 radio code, either of which could stop data logging and
2507 telemetry. Found and characterized by Chuck Haskin, who also
2508 tested the new firmware before release.
2509 </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.9.2. AltosUI, TeleGPS and AltosDroid Applications</h3></div></div></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2510 Deliver firmward for TeleMega v2.0 and TeleBT v3.0 with
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_4"></a>F.10. Release Notes for Version 1.6.4</h2></div></div></div><p>Version 1.6.4 fixes a bluetooth communication problem with
2513 TeleBT v1.0 devices, along with some altosui and altosdroid
2514 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_10"></a>F.10.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2515 Fix hardware flow control on TeleBT v1.0. Hardware RTS/CTS
2516 doesn’t seem to work, switch from using the hardware to
2517 driving these pins with software.
2518 </li><li class="listitem">
2519 Fix ARM USB drivers to deal with OS restarts. Needed to
2520 reset all USB-related state when the USB bus is reset. These
2521 fixes affect all STM32L, STM32F0 and LPC11U14 based devices.
2522 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_telegps_and_altosdroid_applications_3"></a>F.10.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">
2523 Automatically switch from meters or feet to kilometers or
2524 miles for distance units.
2525 </li><li class="listitem">
2526 Add Monitor Idle mode to TeleGPS application.
2527 </li></ul></div><p>AltosUI, TeleGPS and AltosDroid Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2528 Abort map preloading when the preload map dialog is closed.
2529 </li><li class="listitem">
2530 In AltosDroid, Don’t reconnect to last device if the user
2531 had disconnected it the last time the application was
2533 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation"></a>F.10.3. Documentation</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2534 Mention TeleMega v2.0 in hardware specs table.
2535 </li><li class="listitem">
2536 Document TeleGPS RF output in telegps manual.
2537 </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.11. 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
2538 for our host software on desktops, laptops an android devices
2539 along with BlueTooth support for Windows.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_11"></a>F.11.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2540 Fix hardware flow control on TeleBT v3.0. RTS/CTS is
2541 wired backwards on this board, switch from using the
2542 hardware to driving these pins with software.
2543 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_6"></a>F.11.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">
2544 Add BlueTooth support for Windows operating system. This
2545 supports connections to TeleBT over BlueTooth rather than
2547 </li></ul></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2548 Change Java detection and install on Windows. Detection is
2549 now done by looking for the <span class="emphasis"><em>javaw.exe</em></span> program, and
2550 installation by opening a browser on the java.com web site.
2551 </li><li class="listitem">
2552 Delay polling while the Fire Igniters is visible to allow
2553 for TeleMega to report back complete status over the radio.
2554 </li><li class="listitem">
2555 Disallow changing RF calibration numbers in the
2556 configuration UI. There’s no good reason to change this from
2557 the field, and recovering is really hard if you haven’t
2558 written down the right number.
2559 </li><li class="listitem">
2560 Fix USB device discovery on Mac OS X El Capitan. This makes
2561 the connected Altus Metrum USB devices appear again.
2562 </li><li class="listitem">
2563 Fix acceleration data presented in MonitorIdle mode for
2564 TeleMetrum v2.0 flight computers.
2565 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosdroid_2"></a>F.11.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">
2566 Monitor Idle mode. Check state of flight computer while in
2567 idle mode over the radio link
2568 </li><li class="listitem">
2569 Fire Igniters. Remotely fire ignires for recovery system
2571 </li><li class="listitem">
2572 Remote reboot. Cause the flight computer to reboot over the
2573 radio link. This provides a method for switching the flight
2574 computer from idle to flight mode without needing to reach
2576 </li><li class="listitem">
2577 Configurable frequency menu. Change the set of available
2578 frequencies and provide more descriptive names.
2579 </li></ul></div><p>AltosDroid bug fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2580 Don’t set target location if GPS hasn’t locked yet.
2581 </li><li class="listitem">
2582 Fix saving target states so they can be reloaded when the
2583 application restarts. When the application is shut down and
2584 restarted, all previous target state information will be
2585 restored (including GPS position if available).
2586 </li><li class="listitem">
2587 Fix crash on some Android devices for offline maps when
2588 changing the map scale or location.
2589 </li><li class="listitem">
2590 Don’t require USB OTG support. This kept the latest
2591 AltosDroid from being offered on devices without USB device
2592 support, although it can work without that just fine using
2594 </li><li class="listitem">
2595 Don’t require bluetooth to be enabled. This allows the
2596 application to operate with USB devices or just show old
2597 data without turning on the bluetooth radio.
2598 </li><li class="listitem">
2599 Recover old tracker positions when restarting
2600 application. This finally allows you to safely stop and
2601 restart the application without losing the last known
2602 location of any tracker.
2603 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation_2"></a>F.11.4. Documentation</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2604 Document TeleMega and EasyMega additional pyro channel
2605 continuity audio alert pattern.
2606 </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.12. Release Notes for Version 1.6.2</h2></div></div></div><p>Version 1.6.2 includes support for our updated TeleMega v2.0
2607 product and bug fixes in in the flight software for all our boards
2608 and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_12"></a>F.12.1. AltOS</h3></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2609 Add support for TeleMega v2.0 boards.
2610 </li><li class="listitem">
2611 Add PWM servo driver. There’s no higher level code using
2612 this yet, but the driver allows testing of the TeleMega v2.0
2613 servo output connector.
2614 </li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2615 Slow down telemetry packets to allow receiver to keep
2617 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_7"></a>F.12.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">
2618 Fix post-flight orientation computation when processing
2619 TeleMega and EasyMega eeprom data files.
2620 </li><li class="listitem">
2621 Capture complete eeprom data even when there are invalid
2622 entries in the data. This keeps reading eeprom contents and
2623 writing the associated .eeprom file when an error is detected.
2624 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation_3"></a>F.12.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">
2625 HTML versions now have a table of contents on the left side.
2626 </li><li class="listitem">
2627 EasyMini now has its own shorter manual.
2628 </li><li class="listitem">
2629 Provide links between sections in each document.
2630 </li><li class="listitem">
2631 Lots of minor rewriting and restructuring to avoid
2632 duplication of information
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_6_1"></a>F.13. Release Notes for Version 1.6.1</h2></div></div></div><p>Version 1.6.1 includes support for our updated TeleBT v3.0
2634 product and bug fixes in in the flight software for all our boards
2635 and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_13"></a>F.13.1. AltOS</h3></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2636 Add support for TeleBT v3.0 boards.
2637 </li><li class="listitem">
2638 Add support for uncompressed APRS data, providing support
2639 for older APRS receivers. Uncompressed APRS data is less
2640 precise, takes more bandwidth and doesn’t have integrated
2642 </li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2643 Make TeleDongle and TeleBT more tolerant of data rate
2644 variations from transmitting devices.
2645 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_8"></a>F.13.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">
2646 Add map to Monitor Idle display. It’s nice to be able to
2647 verify that maps are working, instead of needing to use
2649 </li></ul></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2650 Fix frequency configuration to round values instead of
2651 truncate them, avoiding a common 1kHz error in the setting.
2652 </li><li class="listitem">
2653 Turn the Windows stub into a more useful program that can
2654 launch the application with parameters so that file manager
2655 icons work more reliably.
2656 </li><li class="listitem">
2657 Force KML export to use a C locale so that numbers are
2658 formatted with <span class="emphasis"><em>.</em></span> instead of <span class="emphasis"><em>,</em></span> for a decimal separator in
2660 </li><li class="listitem">
2661 Preload map tiles based on distance rather than number of
2662 tiles; this means you get the same resolution covering the
2663 entire area, rather than having high resolution near the
2664 center and low resolution further away.
2665 </li><li class="listitem">
2666 Allow configuration of frequency and callsign in Monitor
2668 </li><li class="listitem">
2669 Fix layout weirdness when resizing windows on
2670 Windows. Windows shouldn’t have giant blank spaces around
2671 the useful content anymore.
2672 </li><li class="listitem">
2673 Fix layout weirdness when resizing windows on
2674 Windows. Windows shouldn’t have giant blank spaces around
2675 the useful content anymore.
2676 </li><li class="listitem">
2677 Use a longer filter for descent speed values. This should
2678 provide something more useful on the display, although it
2679 will take longer to respond to changes now.
2680 </li><li class="listitem">
2681 Make Replay Flight run in realtime again. It had been set to
2682 run at 10x speed by mistake.
2683 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosdroid_3"></a>F.13.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">
2684 Add offline map support using mapping code from AltosUI.
2685 </li><li class="listitem">
2686 Support TeleDongle (and TeleBT via USB) on devices
2687 supporting USB On-The-Go.
2688 </li><li class="listitem">
2689 Display additional TeleMega pyro channel status in Pad tab.
2690 </li><li class="listitem">
2691 Switch between metric and imperial units.
2692 </li><li class="listitem">
2693 Monitor TeleBT battery voltage.
2694 </li><li class="listitem">
2695 Track multiple devices at the same time, selecting between
2696 them with a menu or using the map.
2697 </li><li class="listitem">
2698 Add hybrid, satellite and terrain map types.
2699 </li></ul></div><p>AltosDroid Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2700 Use standard Android display conventions so that a menu
2701 button is available in the application title bar.
2702 </li><li class="listitem">
2703 Adjust layout to work on large and small screens; shrinking
2704 the go/no-go lights in smaller environments to try and make
2706 </li><li class="listitem">
2707 Make voice announcements depend on current tab.
2708 </li><li class="listitem">
2709 Compute adjustment to current travel direction while in
2710 motion towards rocket.
2711 </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.14. Release Notes for Version 1.6</h2></div></div></div><p>Version 1.6 includes support for our updated TeleDongle v3.0
2712 product and bug fixes in in the flight software for all our boards
2713 and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_14"></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">
2714 Add support for TeleDongle v3.0 boards.
2715 </li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2716 Don’t beep out the continuity twice by accident in idle mode.
2717 If the battery voltage report takes longer than the initialiation
2718 sequence, the igniter continuity would get reported twice.
2719 </li><li class="listitem">
2720 Record all 32 bits of gyro calibration data in TeleMega and
2721 EasyMega log files. This fixes computation of the gyro rates
2723 </li><li class="listitem">
2724 Change TeleDongle LED usage. Green LED flashes when valid
2725 packet is received. Red LED flashes when invalid packet is
2727 </li><li class="listitem">
2728 Replace LPC11U14 SPI driver with non-interrupt version. The
2729 interrupt code would occasionally wedge on long transfers
2730 if interrupts were blocked for too long. This affects all
2731 released TeleGPS products; if you have a TeleGPS device,
2732 you’ll want to reflash the firmware.
2733 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_9"></a>F.14.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">
2734 Compute tilt angle from TeleMega and EasyMega log
2735 files. This duplicates the quaternion-based angle tracking
2736 code from the flight firmware inside the ground station
2737 software so that post-flight analysis can include evaluation
2739 </li><li class="listitem">
2740 Shows the tool button window when starting with a data file
2741 specified. This means that opening a data file from the file
2742 manager will now bring up the main window to let you operate
2743 the whole application.
2744 </li></ul></div><p>AltosUI Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2745 Show the <span class="emphasis"><em>Connecting</em></span> dialog when using Monitor Idle. Lets
2746 you cancel the Monitor Idle startup when connecting over the
2748 </li><li class="listitem">
2749 Make <span class="emphasis"><em>Monitor Idle</em></span> work for TeleGPS devices when connected
2750 over USB. It’s nice for testing without needing to broadcast
2752 </li><li class="listitem">
2753 Use different Windows API to discover USB devices. This
2754 works better on my Windows 7 box, and will be used if the
2755 older API fails to provide the necessary information.
2756 </li><li class="listitem">
2757 Look in more places in the registry to try and identify the
2758 installed Java version on Windows. If you install the
2759 default 32-bit version of Windows on a 64-bit OS, the Java
2760 registry information is hiding \SOFTWARE\Wow6432Node for
2762 </li><li class="listitem">
2763 Fix file association on Windows by searching for the
2764 javaw.exe program instead of assuming it is in
2765 %SYSTEMROOT%. This makes double-clicking on Altus Metrum
2766 data files in the file manager work correctly.
2767 </li><li class="listitem">
2768 When replaying a file, put <span class="emphasis"><em>done</em></span> in the Age field when we
2769 reach the end of the file, instead of continuing to count forever.
2770 </li><li class="listitem">
2771 In the Scan Channels code, wait for five seconds if we see
2772 any packet. This is needed because AltOS now sends the
2773 callsign, serial number and flight number only once every
2774 five seconds these days.
2775 </li><li class="listitem">
2776 In the Scan Channels code, reset pending flight state
2777 information each time we change channels. This avoids having
2778 flight computers appear on multiple frequencies by accident.
2779 </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.15. Release Notes for Version 1.5</h2></div></div></div><p>Version 1.5 is a major release. It includes support for our new
2780 EasyMega product, new features and bug fixes in in the flight
2781 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_15"></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">
2782 Add support for EasyMega boards.
2783 </li><li class="listitem">
2784 Make the APRS SSID be configurable. This lets you track
2785 different rockets on the same receiver without getting
2787 </li><li class="listitem">
2788 Report extra pyro channel continuity state on EasyMega and
2789 TeleMega via the beeper. This lets you easily verify flight
2790 readiness on these boards after powering up the electronics
2792 </li><li class="listitem">
2793 Add lower telemetry data rates (2400 and 9600 bps) to
2794 increase telemetry radio range. This reduces the amount of
2795 data received as well as increasing battery consumption in
2797 </li><li class="listitem">
2798 Change TeleGPS to have only a single log, and append new
2799 data to it rather than using seperate per-flight logs. This
2800 avoids accidentally filling up log storage by turning
2801 TeleGPS on/off several times.
2802 </li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2803 Increase the maximum range for altitude values from +/-32767m
2804 to +/-2147483647m, allowing the flight computers to function
2805 correctly above the 32km level.
2806 </li><li class="listitem">
2807 Continuously test pyro firing conditions during delay stage,
2808 inhibiting the pyro channel if the test fails. This prevents
2809 firing pyro charges where the conditions were good before
2810 the delay, but become bad before the delay expires.
2811 </li><li class="listitem">
2812 Allow negative numbers in pyro configuration values. This
2813 lets you specify things like descending speed or
2815 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_10"></a>F.15.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">
2816 Support telemetry baud rate selection. Adds menus to
2817 the flight monitoring and configuration for baud rate
2819 </li><li class="listitem">
2820 Support APRS SSID configuration.
2821 </li><li class="listitem">
2822 Integrate with file managers. This provides icons for all of
2823 our file types and associates our application with the files
2824 so that using a file manager to open a AltOS data file
2825 results in launching our application.
2826 </li></ul></div><p>AltosUI Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2827 Make the <span class="emphasis"><em>Graph</em></span> button on the landed tab work again.
2828 </li><li class="listitem">
2829 Make tests for Java on Windows a bit smarter, and also
2830 provide the user with the option to skip installing Java for
2831 cases where we just can’t figure out what version is installed.
2832 </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.16. 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
2833 Windows</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_11"></a>F.16.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">
2834 Checks for Java installation data in more registry locations.
2835 </li><li class="listitem">
2836 Allows user to bypass Java installation in case the
2838 </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.17. 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
2839 Windows and provides the missing TeleMetrum V2.0 firmware. There
2840 aren’t any changes to the firmware or host applications at
2841 all. All Windows users will want to upgrade to get the signed
2842 driver, but Mac and Linux users who do not need the TeleMetrum
2843 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_12"></a>F.17.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">
2844 Provide signed Windows driver files. This should avoid any need to
2845 disable driver signature checking on Windows 7 or 8.
2846 </li><li class="listitem">
2847 Fix Java version detection and download. Previously, the
2848 installer would only look for Java 6 or 7 and insist on
2849 downloading its own Java bits if there was something else
2850 installed. Furthermore, the 64-bit Java link provided didn’t
2851 work for anyone other than Keith, making it impossible to
2852 install AltOS on any machine with Java SE 8 installed.
2853 </li></ul></div><p>Other Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2854 Include 1.4 firmware for TeleMetrum V2.0. None of the
2855 installers shipped this file. Now it’s included in the AltOS
2856 packages for Linux, Mac and Windows.
2857 </li><li class="listitem">
2858 Include Google Application Key for map downloading. The 1.4
2859 release didn’t have this key in the released version of the
2860 software, making map downloading fail for most people.
2861 </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.18. Release Notes for Version 1.4</h2></div></div></div><p>Version 1.4 is a major release. It includes support for our new
2862 TeleGPS product, new features and bug fixes in in the flight
2863 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_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">
2864 Add support for TeleGPS boards.
2865 </li><li class="listitem">
2866 Make the beeper tone configurable, making it
2867 possible to distinguish between two Altus Metrum
2868 products in the same ebay.
2869 </li><li class="listitem">
2870 Make the firing time for extra pyro channels
2871 configurable, allowing longer (or shorter) than the
2872 default 50ms. Only relevant for TeleMega at this
2874 </li></ul></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2875 Replace the <span class="emphasis"><em>dit dit dit</em></span> tones at startup with the
2876 current battery voltage, measured in tenths of a
2877 volt. This lets you check the battery voltage
2878 without needing telemetry, which is especially
2880 </li><li class="listitem">
2881 Change state beeping to "Farnsworth spacing", which
2882 means they’re quite a bit faster than before, and so
2883 they take less time to send.
2884 </li><li class="listitem">
2885 Fix bug preventing the selection of the <span class="emphasis"><em>Flight
2886 State After</em></span> mode in pyro configuration.
2887 </li><li class="listitem">
2888 Fix bug where erasing flights would reset the flight
2889 number to 2 on TeleMega and TeleMetrum v2.
2890 </li><li class="listitem">
2891 Fix u-Blox GPS driver to mark course and speed data
2893 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application"></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">
2894 Add zooming and new content types (terrain and road
2895 maps) to map view. Change map storage format from
2896 PNG to Jpeg, which saves a huge amount of disk
2897 space. You will need to re-download all of your
2898 pre-loaded map images.
2899 </li><li class="listitem">
2900 Add a distance measuring device to the maps
2901 view. Select this by using any button other than the
2902 left one, or by pressing shift or control on the
2903 keyboard while using the left button.
2904 </li><li class="listitem">
2905 Add new <span class="emphasis"><em>Ignitor</em></span> tab to the flight monitor display
2906 for TeleMega’s extra ignitors.
2907 </li><li class="listitem">
2908 Add additional ignitor firing marks and voltages to
2909 the graph so you can see when the ignitors fired,
2910 along with the ignitor voltages.
2911 </li><li class="listitem">
2912 Add GPS course, ground speed and climb rate as
2913 optional graph elements.
2914 </li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2915 When flashing new firmware, re-try opening the
2916 device as sometimes it takes a while for the
2917 underlying operating system to recognize that the
2918 device has rebooted in preparation for the flashing
2920 </li><li class="listitem">
2921 Hide Tilt Angle in ascent tab for devices that don’t
2923 </li><li class="listitem">
2924 Increase the width of data lines in the graphs to
2925 make them easier to read.
2926 </li><li class="listitem">
2927 Filter out speed and acceleration spikes caused by
2928 ejection charge firing when computing the maximum
2929 values. This provides a more accurate reading of
2931 </li><li class="listitem">
2932 Fix EasyMini voltage displays. Early EasyMini
2933 prototypes used a 3.0V regulator, and AltosUI still
2934 used that value as the basis of the
2935 computation. Production EasyMini boards have always
2936 shipped with a 3.3V regulator. Also, purple EasyMini
2937 boards sensed the battery voltage past the blocking
2938 diode, resulting in a drop of about 150mV from the
2939 true battery voltage. Compensate for that when
2940 displaying the value.
2941 </li><li class="listitem">
2942 Display error message when trying to configure
2943 maximum flight log size while the flight computer
2944 still has flight data stored.
2945 </li><li class="listitem">
2946 Handle TeleMetrum and TeleMini eeprom files
2947 generated with pre-1.0 firmware. Those ancient
2948 versions didn’t report the log format, so just use
2949 the product name instead.
2950 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_telegps_application"></a>F.18.3. TeleGPS Application</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2951 New application designed for use with TeleGPS boards.
2952 </li><li class="listitem">
2953 Shares code with AltosUI, mostly just trimmed down
2954 to focus on TeleGPS-related functions.
2955 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation_4"></a>F.18.4. Documentation</h3></div></div></div><p>Documentation changes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2956 Re-create the drill template images; they should
2957 print correctly from Firefox at least. Ship these as
2958 individual PDF files so they’re easy to print.
2959 </li><li class="listitem">
2960 Add a description of the <span class="emphasis"><em>Apogee Lockout</em></span> setting,
2961 which prevents the apogee charge from firing for a
2962 configurable amount of time after boost.
2963 </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.19. 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
2964 the TeleMega flight software and AltosUI ground station</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_17"></a>F.19.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2965 On TeleMega, limit number of logged GPS status
2966 information to 12 satellites. That’s all there is
2967 room for in the log structure.
2968 </li><li class="listitem">
2969 Improve APRS behavior. Remembers last known GPS
2970 position and keeps sending that if we lose GPS
2971 lock. Marks locked/unlocked by sending L/U in the
2972 APRS comment field along with the number of sats in
2974 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_2"></a>F.19.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">
2975 If the TeleMega flight firmware reports that it has
2976 logged information about more than 12 satellites,
2977 don’t believe it as the log only holds 12 satellite
2979 </li><li class="listitem">
2980 Track the maximum height as computed from GPS
2981 altitude data and report that in the flight summary
2983 </li><li class="listitem">
2984 Use letters (A, B, C, D) for alternate pyro channel
2985 names instead of numbers (0, 1, 2, 3) in the Fire
2987 </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.20. Release Notes for Version 1.3.1</h2></div></div></div><p>Version 1.3.1 is a minor release. It improves support for
2988 TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_18"></a>F.20.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">
2989 Improved APRS mode. Now uses compressed position
2990 format for smaller data size, improved precision and
2991 to include altitude data as well as latitude and
2992 longitude. Also added battery and pyro voltage
2993 reports in the APRS comment field so you can confirm
2994 that the unit is ready for launch.
2995 </li></ul></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
2996 Improve sensor boot code. If sensors fail to
2997 self-test, the device will still boot up and check
2998 for pad/idle modes. If in idle mode, the device will
2999 warn the user with a distinct beep, if in Pad mode,
3000 the unit will operate as best it can. Also, the
3001 Z-axis accelerometer now uses the factory
3002 calibration values instead of re-calibrating on the
3003 pad each time. This avoids accidental boost detect
3004 when moving the device around while in Pad mode.
3005 </li><li class="listitem">
3006 Fix antenna-down mode accelerometer
3007 configuration. Antenna down mode wasn’t working
3008 because the accelerometer calibration values were
3009 getting re-computed incorrectly in inverted mode.
3010 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_3"></a>F.20.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">
3011 Display additional TeleMega sensor values in real
3012 units. Make all of these values available for
3013 plotting. Display TeleMega orientation value in the
3014 Ascent and Table tabs.
3015 </li><li class="listitem">
3016 Support additional TeleMega pyro channels in the
3017 Fire Igniter dialog. This lets you do remote testing
3018 of all of the channels, rather than just Apogee and
3020 </li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3021 Limit data rate when downloading satellite images
3022 from Google to make sure we stay within their limits
3023 so that all of the map tiles download successfully.
3024 </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.21. Release Notes for Version 1.3</h2></div></div></div><p>Version 1.3 is a major release. It adds support for TeleMega,
3025 TeleMetrum v2.0, TeleMini v2.0 and EasyMini.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_19"></a>F.21.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">
3026 Add STM32L processor support. This includes
3027 enhancements to the scheduler to support products
3029 </li><li class="listitem">
3030 Add NXP LPC11U14 processor support.
3031 </li><li class="listitem">
3032 Support additional pyro channels. These are
3033 configurable through the UI to handle air starts,
3034 staging, additional recovery events and external
3035 devices such as cameras.
3036 </li><li class="listitem">
3037 Add 3-axis gyro support for orientation
3038 tracking. This integrates the gyros to compute the
3039 angle from vertical during flight, allowing the
3040 additional pyro events to be controlled by this
3042 </li><li class="listitem">
3043 Many more device drivers, including u-Blox Max 7Q
3044 GPS, Freescale MMA6555 digital single-axis
3045 accelerometer, Invensense MPU6000 3-axis
3046 accelerometer + 3 axis gyro, Honeywell HMC5883
3047 3-axis magnetic sensor and the TI CC1120 and CC115L
3048 digital FM transceivers
3049 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_4"></a>F.21.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">
3050 Support TeleMega, TeleMetrum v2.0, TeleMini v2.0 and
3051 EasyMini telemetry and log formats.
3052 </li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3053 Use preferred units for main deployment height
3054 configuration, instead of always doing configuration in
3056 == MicroPeak Application
3057 </li><li class="listitem">
3058 Add <span class="emphasis"><em>Download</em></span> button to menu bar.
3059 </li><li class="listitem">
3060 Save the last log directory and offer that as the
3061 default for new downloads
3062 </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.22. 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
3063 the AltosDroid application, provides several new features in
3064 AltosUI and fixes some bugs in the AltOS firmware.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_20"></a>F.22.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">
3065 Add support for TeleBT
3066 </li></ul></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3067 In TeleMini recovery mode (when booted with the
3068 outer two debug pins connected together), the radio
3069 parameters are also set back to defaults
3070 (434.550MHz, N0CALL, factory radio cal).
3071 </li><li class="listitem">
3072 Correct Kalman filter model error covariance
3073 matrix. The values used previously assumed
3074 continuous measurements instead of discrete
3076 </li><li class="listitem">
3077 Fix some bugs in the USB driver for TeleMetrum and
3078 TeleDongle that affected Windows users.
3079 </li><li class="listitem">
3080 Adjusted the automatic gain control parameters that
3081 affect receive performance for TeleDongle. Field
3082 tests indicate that this may improve receive
3083 performance somewhat.
3084 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_5"></a>F.22.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">
3085 Make the initial position of the AltosUI top level
3086 window configurable. Along with this change, the
3087 other windows will pop up at <span class="emphasis"><em>sensible</em></span> places now,
3088 instead of on top of one another.
3089 </li><li class="listitem">
3090 Add GPS data and a map to the graph window. This
3091 lets you see a complete summary of the flight
3092 without needing to <span class="emphasis"><em>replay</em></span> the whole thing.
3093 </li></ul></div><p>AltosUI application fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3094 Handle missing GPS lock in <span class="emphasis"><em>Descent</em></span>
3095 tab. Previously, if the GPS position of the pad was
3096 unknown, an exception would be raised, breaking the
3097 Descent tab contents.
3098 </li><li class="listitem">
3099 Improve the graph, adding tool-tips to show values
3100 near the cursor and making the displayed set of
3101 values configurable, adding all of the flight data
3102 as options while leaving the default settings alone
3103 so that the graph starts by showing height, speed
3105 </li><li class="listitem">
3106 Add callsign to Monitor idle window and connecting
3107 dialogs. This makes it clear which callsign is being
3108 used so that the operator will be aware that it must
3109 match the flight computer value or no communication
3111 </li><li class="listitem">
3112 When downloading flight data, display the block
3113 number so that the user has some sense of
3114 progress. Unfortunately, we don’t know how many
3115 blocks will need to be downloaded, but at least it
3116 isn’t just sitting there doing nothing for a long
3118 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosdroid_4"></a>F.22.3. AltosDroid</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3119 First version of this application
3120 </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.23. Release Notes for Version 1.2</h2></div></div></div><p>Version 1.2 is a major release. It adds support for MicroPeak
3121 and the MicroPeak USB adapter.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_21"></a>F.23.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">
3122 Add MicroPeak support. This includes support for the
3123 ATtiny85 processor and adaptations to the core code
3124 to allow for devices too small to run the
3125 multi-tasking scheduler.
3126 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_micropeak_application"></a>F.23.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">
3127 Added MicroPeak application
3128 </li></ul></div><p>AltosUI and MicroPeak fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3129 Distribute Mac OS X packages in disk image (<span class="emphasis"><em>.dmg</em></span>)
3130 format to greatly simplify installation.
3131 </li><li class="listitem">
3132 Provide version numbers for the shared Java
3133 libraries to ensure that upgrades work properly, and
3134 to allow for multiple Altus Metrum software packages
3135 to be installed in the same directory at the same
3137 </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.24. 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
3138 in AltosUI and one firmware bug that affects TeleMetrum
3139 version 1.0 boards. Thanks to Bob Brown for help diagnosing
3140 the Google Earth file export issue, and for suggesting the
3141 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_22"></a>F.24.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3142 TeleMetrum v1.0 boards use the AT45DB081D flash
3143 memory part to store flight data, which is different
3144 from later TeleMetrum boards. The AltOS v1.1 driver
3145 for this chip couldn’t erase memory, leaving it
3146 impossible to delete flight data or update
3147 configuration values. This bug doesn’t affect newer
3148 TeleMetrum boards, and it doesn’t affect the safety
3149 of rockets flying version 1.1 firmware.
3150 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_2"></a>F.24.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">
3151 The “Descent” tab displays the range to the rocket,
3152 which is a combination of the over-the-ground
3153 distance to the rockets current latitude/longitude
3154 and the height of the rocket. As such, it’s useful
3155 for knowing how far away the rocket is, but
3156 difficult to use when estimating where the rocket
3157 might eventually land. A new “Ground Distance” field
3158 has been added which displays the distance to a spot
3159 right underneath the rocket.
3160 </li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3161 Creating a Google Earth file (KML) from on-board
3162 flight data (EEPROM) would generate an empty
3163 file. The code responsible for reading the EEPROM
3164 file wasn’t ever setting the GPS valid bits, and so
3165 the KML export code thought there was no GPS data in
3167 </li><li class="listitem">
3168 The “Landed” tab was displaying all values in metric
3169 units, even when AltosUI was configured to display
3170 imperial units. Somehow I just missed this tab when
3171 doing the units stuff.
3172 </li><li class="listitem">
3173 Sensor data wasn’t being displayed for TeleMini
3174 flight computers in Monitor Idle mode, including
3175 things like battery voltage. The code that picked
3176 which kinds of data to fetch from the flight
3177 computer was missing a check for TeleMini when
3178 deciding whether to fetch the analog sensor data.
3179 </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.25. Release Notes for Version 1.1</h2></div></div></div><p>Version 1.1 is a minor release. It provides a few new features
3180 in AltosUI and the AltOS firmware and fixes bugs.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_23"></a>F.25.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">
3181 Add apogee-lockout value. Overrides the apogee
3182 detection logic to prevent incorrect apogee charge
3184 </li><li class="listitem">
3185 Force the radio frequency to 434.550MHz when the
3186 debug clock pin is connected to ground at boot
3187 time. This provides a way to talk to a TeleMini
3188 which is configured to some unknown frequency.
3189 </li><li class="listitem">
3190 Provide RSSI values for Monitor Idle mode. This
3191 makes it easy to check radio range without needing
3192 to go to flight mode.
3193 </li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3194 Fix a bug where the data reported in telemetry
3195 packets was from 320ms ago.
3196 </li><li class="listitem">
3197 Fix a bug which caused the old received telemetry
3198 packets to be retransmitted over the USB link when
3199 the radio was turned off and back on.
3200 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_3"></a>F.25.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">
3201 Make the look-n-feel configurable, providing a choice from
3202 the available options.
3203 </li><li class="listitem">
3204 Add an <span class="emphasis"><em>Age</em></span> element to mark how long since a
3205 telemetry packet has been received. Useful to
3206 quickly gauge whether communications with the rocket
3208 </li><li class="listitem">
3209 Add <span class="emphasis"><em>Configure Ground Station</em></span> dialog to set the
3210 radio frequency used by a particular TeleDongle
3211 without having to go through the flight monitor UI.
3212 </li><li class="listitem">
3213 Add configuration for the new apogee-lockout
3214 value. A menu provides a list of reasonable values,
3215 or the value can be set by hand.
3216 </li><li class="listitem">
3217 Add Imperial units mode to present data in feet
3219 </li></ul></div><p>AltosUI Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3220 Fix a bug that caused GPS ready to happen too
3221 quickly. The software was using every telemetry
3222 packet to signal new GPS data, which caused GPS
3223 ready to be signalled after 10 packets instead of 10
3225 </li><li class="listitem">
3226 Fix Google Earth data export to work with recent
3227 versions. The google earth file loading code got a
3228 lot pickier, requiring some minor white space
3229 changes in the export code.
3230 </li><li class="listitem">
3231 Changed how flight data are downloaded. Now there’s
3232 an initial dialog asking which flights to download,
3233 and after that finishes, a second dialog comes up
3234 asking which flights to delete.
3235 </li><li class="listitem">
3236 Re-compute time spent in each state for the flight
3237 graph; this figures out the actual boost and landing
3238 times instead of using the conservative values
3239 provide by the flight electronics. This improves the
3240 accuracy of the boost acceleration and main descent
3242 </li><li class="listitem">
3243 Make AltosUI run on Mac OS Lion. The default Java
3244 heap space was dramatically reduced for this release
3245 causing much of the UI to fail randomly. This most
3246 often affected the satellite mapping download and
3248 </li><li class="listitem">
3249 Change how data are displayed in the <span class="emphasis"><em>table</em></span> tab of
3250 the flight monitoring window. This eliminates
3251 entries duplicated from the header and adds both
3252 current altitude and pad altitude, which are useful
3253 in <span class="emphasis"><em>Monitor Idle</em></span> mode.
3254 </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.26. Release Notes for Version 1.0.1</h2></div></div></div><p>Version 1.0.1 is a major release, adding support for the
3255 TeleMini device and lots of new AltosUI features</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_24"></a>F.26.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">
3256 Add TeleMini v1.0 support.
3257 </li><li class="listitem">
3258 Support operation of TeleMetrum with the antenna pointing
3259 aft. Previous firmware versions required the antenna to be
3260 pointing upwards, now there is a configuration option
3261 allowing the antenna to point aft, to aid installation in
3263 </li><li class="listitem">
3264 Ability to disable telemetry. For airframes where an antenna
3265 just isn’t possible, or where radio transmissions might
3266 cause trouble with other electronics, there’s a
3267 configuration option to disable all telemetry. Note that the
3268 board will still enable the radio link in idle mode.
3269 </li><li class="listitem">
3270 Arbitrary frequency selection. The radios in Altus Metrum
3271 devices can be programmed to a wide range of frequencies, so
3272 instead of limiting devices to 10 pre-selected <span class="emphasis"><em>channels</em></span>,
3273 the new firmware allows the user to choose any frequency in
3274 the 70cm band. Note that the RF matching circuit on the
3275 boards is tuned for around 435MHz, so frequencies far from
3276 that may reduce the available range.
3277 </li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3278 Change telemetry to be encoded in multiple 32-byte
3279 packets. This enables support for TeleMini and other devices
3280 without requiring further updates to the TeleDongle
3282 </li><li class="listitem">
3283 Kalman-filter based flight-tracking. The model based sensor
3284 fusion approach of a Kalman filter means that AltOS now
3285 computes apogee much more accurately than before, generally
3286 within a fraction of a second. In addition, this approach
3287 allows the baro-only TeleMini device to correctly identify
3288 Mach transitions, avoiding the error-prone selection of a
3290 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_6"></a>F.26.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">
3291 Add main/apogee voltage graphs to the data
3292 plot. This provides a visual indication if the
3293 igniters fail before being fired.
3294 </li><li class="listitem">
3295 Scan for altimeter devices by watching the defined
3296 telemetry frequencies. This avoids the problem of
3297 remembering what frequency a device was configured
3298 to use, which is especially important with TeleMini
3299 which does not include a USB connection.
3300 </li><li class="listitem">
3301 Monitor altimeter state in "Idle" mode. This
3302 provides much of the information presented in the
3303 "Pad" dialog from the Monitor Flight command,
3304 monitoring the igniters, battery and GPS status
3305 withing requiring the flight computer to be armed
3306 and ready for flight.
3307 </li><li class="listitem">
3308 Pre-load map images from home. For those launch
3309 sites which don’t provide free Wi-Fi, this allows
3310 you to download the necessary satellite images
3311 given the location of the launch site. A list of
3312 known launch sites is maintained at altusmetrum.org
3313 which AltosUI downloads to populate a menu; if
3314 you’ve got a launch site not on that list, please
3315 send the name of it, latitude and longitude along
3316 with a link to the web site of the controlling club
3317 to the altusmetrum mailing list.
3318 </li><li class="listitem">
3319 Flight statistics are now displayed in the Graph
3320 data window. These include max height/speed/accel,
3321 average descent rates and a few other bits of
3322 information. The Graph Data window can now be
3323 reached from the <span class="emphasis"><em>Landed</em></span> tab in the Monitor Flight
3324 window so you can immediately see the results of a
3326 </li></ul></div><p>AltosUI Changes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3327 Wait for altimeter when using packet mode. Instead
3328 of quicly timing out when trying to initialize a
3329 packet mode configuration connection, AltosUI now
3330 waits indefinitely for the remote device to appear,
3331 providing a cancel button should the user get
3332 bored. This is necessary as the TeleMini can only be
3333 placed in "Idle" mode if AltosUI is polling it.
3334 </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.27. 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
3335 changes.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_4"></a>F.27.1. AltosUI</h3></div></div></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3336 Fix plotting problems due to missing file in the Mac
3338 </li><li class="listitem">
3339 Always read whole eeprom blocks, mark empty records
3340 invalid, display parsing errors to user.
3341 </li><li class="listitem">
3342 Add software version to Configure AltosUI dialog
3343 </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.28. Release Notes for Version 0.9</h2></div></div></div><p>Version 0.9 adds a few new firmware features and accompanying
3344 AltosUI changes, along with new hardware support.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_25"></a>F.28.1. AltOS</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3345 Support for TeleMetrum v1.1 hardware. Sources for the flash
3346 memory part used in v1.0 dried up, so v1.1 uses a different
3347 part which required a new driver and support for explicit
3349 </li><li class="listitem">
3350 Multiple flight log support. This stores more than one
3351 flight log in the on-board flash memory. It also requires
3352 the user to explicitly erase flights so that you won’t lose
3353 flight logs just because you fly the same board twice in one
3355 </li><li class="listitem">
3356 Telemetry support for devices with serial number >= 256.
3357 Previous versions used a telemetry packet format that
3358 provided only 8 bits for the device serial number. This
3359 change requires that both ends of the telemetry link be
3360 running the 0.9 firmware or they will not communicate.
3361 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_7"></a>F.28.2. AltosUI Application</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3362 Support for telemetry format changes.
3363 </li><li class="listitem">
3364 Support for multiple flight logs.
3365 </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.29. Release Notes for Version 0.8</h2></div></div></div><p>Version 0.8 offers a major upgrade in the AltosUI
3366 interface.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application_8"></a>F.29.1. AltosUI Application:</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3367 Post-flight graphing tool. This lets you explore the
3368 behaviour of your rocket after flight with a scroll-able and
3369 zoom-able chart showing the altitude, speed and acceleration
3370 of the airframe along with events recorded by the flight
3371 computer. You can export graphs to PNG files, or print them
3373 </li><li class="listitem">
3374 Real-time moving map which overlays the in-progress flight
3375 on satellite imagery fetched from Google Maps. This lets you
3376 see in pictures where your rocket has landed, allowing you
3377 to plan recovery activities more accurately.
3378 </li><li class="listitem">
3379 Wireless recovery system testing. Prep your rocket for
3380 flight and test fire the deployment charges to make sure
3381 things work as expected. All without threading wires through
3382 holes in your airframe.
3383 </li><li class="listitem">
3384 Optimized flight status displays. Each flight state now has
3385 it’s own custom <span class="emphasis"><em>tab</em></span> in the flight monitoring window so you
3386 can focus on the most important details. Pre-flight, the
3387 system shows a set of red/green status indicators for
3388 battery voltage, apogee/main igniter continutity and GPS
3389 reception. Wait until they’re all green and your rocket is
3390 ready for flight. There are also tabs for ascent, descent
3391 and landing along with the original tabular view of the
3393 </li><li class="listitem">
3394 Monitor multiple flights simultaneously. If you have more
3395 than one TeleDongle, you can monitor a flight with each one
3396 on the same computer.
3397 </li><li class="listitem">
3398 Automatic flight monitoring at startup. Plug TeleDongle into
3399 the machine before starting AltosUI and it will
3400 automatically connect to it and prepare to monitor a flight.
3401 </li><li class="listitem">
3402 Exports Google Earth flight tracks. Using the Keyhole Markup
3403 Language (.kml) file format, this provides a 3D view of your
3404 rocket flight through the Google Earth program.
3405 </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.30. Release Notes for Version 0.7.1</h2></div></div></div><p>Version 0.7.1 is the first release containing our new
3406 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.30.1. AltosUI Application</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
3407 Receive and log telemetry from a connected TeleDongle
3408 device. All data received is saved to log files named with
3409 the current date and the connected rocket serial and flight
3410 numbers. There is no mode in which telemetry data will not
3412 </li><li class="listitem">
3413 Download logged data from TeleMetrum devices, either through
3414 a direct USB connection or over the air through a TeleDongle
3416 </li><li class="listitem">
3417 Configure a TeleMetrum device, setting the radio channel,
3418 callsign, apogee delay and main deploy height. This can be
3419 done through either a USB connection or over a radio link
3420 via a TeleDongle device.
3421 </li><li class="listitem">
3422 Replay a flight in real-time. This takes a saved telemetry
3423 log or eeprom download and replays it through the user
3424 interface so you can relive your favorite rocket flights.
3425 </li><li class="listitem">
3426 Reprogram Altus Metrum devices. Using an Altus Metrum device
3427 connected via USB, another Altus Metrum device can be
3428 reprogrammed using the supplied programming cable between
3430 </li><li class="listitem">
3431 Export Flight data to a comma-separated-values file. This
3432 takes either telemetry or on-board flight data and generates
3433 data suitable for use in external applications. All data is
3434 exported using standard units so that no device-specific
3435 knowledge is needed to handle the data.
3436 </li><li class="listitem">
3437 Speak to you during the flight. Instead of spending the
3438 flight hunched over your laptop looking at the screen, enjoy
3439 the view while the computer tells you what’s going on up
3440 there. During ascent, you hear the current flight state and
3441 altitude information. During descent, you get azimuth,
3442 elevation and range information to try and help you find
3443 your rocket in the air. Once on the ground, the direction
3444 and distance are reported.
3445 </li></ul></div></div></div></div></div></body></html>
projects / web / altusmetrum / blob