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