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