-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>The Altus Metrum System</title><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" title="The Altus Metrum System"><div class="titlepage"><div><div><h1 class="title"><a name="idm14881448"></a>The Altus Metrum System</h1></div><div><h2 class="subtitle">An Owner's Manual for TeleMetrum, TeleMini and TeleDongle Devices</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3></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 © 2011 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice" title="Legal Notice"><a name="idp1633264"></a><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>The Altus Metrum System</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book"><div class="titlepage"><div><div><h1 class="title"><a name="idm15749952"></a>The Altus Metrum System</h1></div><div><h2 class="subtitle">An Owner's Manual for TeleMetrum, TeleMini, TeleDongle and TeleBT Devices</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3></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 © 2013 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a name="idp111792"></a><p>
This document is released under the terms of the
<a class="ulink" href="http://creativecommons.org/licenses/by-sa/3.0/" target="_top">
Creative Commons ShareAlike 3.0
</a>
license.
- </p></div></div><div><div class="revhistory"><table border="1" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="2"><b>Revision History</b></th></tr><tr><td align="left">Revision 1.0</td><td align="left">24 August 2011</td></tr><tr><td align="left" colspan="2">
+ </p></div></div><div><div class="revhistory"><table style="border-style:solid; width:100%;" summary="Revision History"><tr><th align="left" valign="top" colspan="2"><b>Revision History</b></th></tr><tr><td align="left">Revision 1.2.1</td><td align="left">21 May 2013</td></tr><tr><td align="left" colspan="2">
+ Updated for software version 1.2. Version 1.2 adds support
+ for TeleBT and AltosDroid. It also adds a few minor features
+ and fixes bugs in AltosUI and the AltOS firmware.
+ </td></tr><tr><td align="left">Revision 1.2</td><td align="left">18 April 2013</td></tr><tr><td align="left" colspan="2">
+ Updated for software version 1.2. Version 1.2 adds support
+ for MicroPeak and the MicroPeak USB interface.
+ </td></tr><tr><td align="left">Revision 1.1.1</td><td align="left">16 September 2012</td></tr><tr><td align="left" colspan="2">
+ Updated for software version 1.1.1 Version 1.1.1 fixes a few
+ bugs found in version 1.1.
+ </td></tr><tr><td align="left">Revision 1.1</td><td align="left">13 September 2012</td></tr><tr><td align="left" colspan="2">
+ Updated for software version 1.1. Version 1.1 has new
+ features but is otherwise compatible with version 1.0.
+ </td></tr><tr><td align="left">Revision 1.0</td><td align="left">24 August 2011</td></tr><tr><td align="left" colspan="2">
Updated for software version 1.0. Note that 1.0 represents a
telemetry format change, meaning both ends of a link
(TeleMetrum/TeleMini and TeleDongle) must be updated or
Updated for software version 0.9. Note that 0.9 represents a
telemetry format change, meaning both ends of a link (TeleMetrum and
TeleDongle) must be updated or communications will fail.
- </td></tr><tr><td align="left">Revision 0.8</td><td align="left">24 November 2010</td></tr><tr><td align="left" colspan="2">Updated for software version 0.8 </td></tr></table></div></div></div><hr></div><div class="acknowledgements" title="Acknowledgements"><div class="titlepage"><div><div><h2 class="title"><a name="idp2861168"></a>Acknowledgements</h2></div></div></div>
+ </td></tr><tr><td align="left">Revision 0.8</td><td align="left">24 November 2010</td></tr><tr><td align="left" colspan="2">Updated for software version 0.8 </td></tr></table></div></div></div><hr></div><div class="acknowledgements"><div class="titlepage"><div><div><h1 class="title"><a name="idp84128"></a>Acknowledgements</h1></div></div></div>
<p>
Thanks to Bob Finch, W9YA, NAR 12965, TRA 12350 for writing "The
Mere-Mortals Quick Start/Usage Guide to the Altus Metrum Starter
NAR #88757, TRA #12200<br>
</p></div><p>
</p>
- </div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#idp127360">1. Introduction and Overview</a></span></dt><dt><span class="chapter"><a href="#idp130344">2. Getting Started</a></span></dt><dt><span class="chapter"><a href="#idp2651808">3. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idp3378840">4. Hardware Overview</a></span></dt><dt><span class="chapter"><a href="#idp3276128">5. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3062368">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idp2460120">2. GPS </a></span></dt><dt><span class="section"><a href="#idp2052200">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idp2662856">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idp3396632">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idp2696208">6. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2397232">6.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp2441424">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp1908928">6.3. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idp3092808">6.4. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp1888288">6.5. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp2487664">6.6. Pad Orientation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp3525088">6. AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2539464">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2507712">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idp2116736">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idp3192912">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idp3341456">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idp2011184">1.5. Site Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3564984">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idp3039048">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idp2169992">4. Graph Data</a></span></dt><dt><span class="section"><a href="#idp1875096">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2578272">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idp2875944">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idp2810064">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp1391912">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idp3569008">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp3546448">6.3. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp2106808">6.4. Radio Calibration</a></span></dt><dt><span class="section"><a href="#idp2727816">6.5. Callsign</a></span></dt><dt><span class="section"><a href="#idp2159880">6.6. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idp2199304">6.7. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp3176768">6.8. Pad Orientation</a></span></dt></dl></dd><dt><span class="section"><a href="#idp1614816">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp1522712">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idp2951344">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idp2704448">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idp2434112">7.4. Font Size</a></span></dt><dt><span class="section"><a href="#idp2866200">7.5. Serial Debug</a></span></dt><dt><span class="section"><a href="#idp2341272">7.6. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idp2198928">8. Flash Image</a></span></dt><dt><span class="section"><a href="#idp3268008">9. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idp2748912">10. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp2545000">11. Load Maps</a></span></dt><dt><span class="section"><a href="#idp2376832">12. Monitor Idle</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp1384336">7. Using Altus Metrum Products</a></span></dt><dd><dl><dt><span class="section"><a href="#idp1372064">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idp2120808">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idp2111736">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idp2590104">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idp916736">5. Future Plans</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp1877664">8. Altimeter Installation Recommendations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2776168">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idp3422920">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idp2493216">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idp2097000">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idp3092536">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp3323072">6. Ground Testing</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp2657144">9. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2722712">1. Updating TeleMetrum Firmware</a></span></dt><dt><span class="section"><a href="#idp1268600">2. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idp1444904">3. Updating TeleDongle Firmware</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3431816">10. Hardware Specifications</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2831496">1. TeleMetrum Specifications</a></span></dt><dt><span class="section"><a href="#idp3455400">2. TeleMini Specifications</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3104824">11. FAQ</a></span></dt><dt><span class="appendix"><a href="#idp2639136">A. Notes for Older Software</a></span></dt><dt><span class="appendix"><a href="#idp2228272">B. Calibration</a></span></dt><dd><dl><dt><span class="section"><a href="#idp1912752">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp2744568">2. TeleMetrum Accelerometer</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp1711112">C. Release Notes</a></span></dt></dl></div><div class="chapter" title="Chapter 1. Introduction and Overview"><div class="titlepage"><div><div><h2 class="title"><a name="idp127360"></a>Chapter 1. Introduction and Overview</h2></div></div></div><p>
+ </div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="#idp45792">1. Introduction and Overview</a></span></dt><dt><span class="chapter"><a href="#idp49504">2. Getting Started</a></span></dt><dt><span class="chapter"><a href="#idp2493720">3. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idp2765656">4. Hardware Overview</a></span></dt><dt><span class="chapter"><a href="#idp2919872">5. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2375600">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idp2284648">2. GPS </a></span></dt><dt><span class="section"><a href="#idp753536">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idp760992">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idp762792">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idp55640">6. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp56488">6.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp57656">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp59488">6.3. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idp61128">6.4. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp64904">6.5. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp66248">6.6. Pad Orientation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp67528">6. AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp68608">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idp75208">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idp3850840">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idp3852992">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idp3856520">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idp3859448">1.5. Site Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3861728">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idp3864648">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idp3865896">4. Graph Data</a></span></dt><dt><span class="section"><a href="#idp3869184">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3870192">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idp3871768">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3872600">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3876776">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idp3877760">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp3878800">6.3. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp3879712">6.4. Radio Calibration</a></span></dt><dt><span class="section"><a href="#idp3880776">6.5. Callsign</a></span></dt><dt><span class="section"><a href="#idp3881512">6.6. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idp3882376">6.7. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp3885216">6.8. Pad Orientation</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3887440">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3888064">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idp3890336">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idp3891560">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idp3892528">7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#idp3893432">7.5. Font Size</a></span></dt><dt><span class="section"><a href="#idp3894136">7.6. Serial Debug</a></span></dt><dt><span class="section"><a href="#idp3895048">7.7. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3896032">8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3899952">8.1. Frequency</a></span></dt><dt><span class="section"><a href="#idp3900936">8.2. Radio Calibration</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3901928">9. Flash Image</a></span></dt><dt><span class="section"><a href="#idp3905000">10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idp3907104">11. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp3908008">12. Load Maps</a></span></dt><dt><span class="section"><a href="#idp3910136">13. Monitor Idle</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3911008">7. AltosDroid</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3912688">1. Installing AltosDroid</a></span></dt><dt><span class="section"><a href="#idp3913648">2. Connecting to TeleBT</a></span></dt><dt><span class="section"><a href="#idp3914864">3. Configuring AltosDroid</a></span></dt><dt><span class="section"><a href="#idp3915736">4. Altos Droid Flight Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3916536">4.1. Pad</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3922504">5. Downloading Flight Logs</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3923520">8. Using Altus Metrum Products</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3923840">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idp3924800">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idp3926904">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idp3934536">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idp3936288">5. Future Plans</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3939448">9. Altimeter Installation Recommendations</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3940432">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idp3942768">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idp3946752">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idp3949136">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idp3953208">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp3955048">6. Ground Testing</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3957184">10. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3959184">1. Updating TeleMetrum Firmware</a></span></dt><dt><span class="section"><a href="#idp3964528">2. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idp3969944">3. Updating TeleDongle Firmware</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3977040">11. Hardware Specifications</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3977360">1. TeleMetrum Specifications</a></span></dt><dt><span class="section"><a href="#idp3983088">2. TeleMini Specifications</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp3987896">12. FAQ</a></span></dt><dt><span class="appendix"><a href="#idp3991640">A. Notes for Older Software</a></span></dt><dt><span class="appendix"><a href="#idp4008072">B. Drill Templates</a></span></dt><dd><dl><dt><span class="section"><a href="#idp4008720">1. TeleMetrum template</a></span></dt><dt><span class="section"><a href="#idp4016464">2. TeleMini template</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp4018112">C. Calibration</a></span></dt><dd><dl><dt><span class="section"><a href="#idp4019088">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp4022408">2. TeleMetrum Accelerometer</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp4027304">D. Release Notes</a></span></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp45792"></a>Chapter 1. Introduction and Overview</h1></div></div></div><p>
Welcome to the Altus Metrum community! Our circuits and software reflect
our passion for both hobby rocketry and Free Software. We hope their
capabilities and performance will delight you in every way, but by
as standard features, and a "companion interface" that will
support optional capabilities in the future.
</p><p>
- The newest device is TeleMini, a dual deploy altimeter with
+ Our second device was TeleMini, a dual deploy altimeter with
radio telemetry and radio direction finding. This device is only
13mm by 38mm (½ inch by 1½ inches) and can fit easily in an 18mm
air-frame.
</p><p>
- Complementing TeleMetrum and TeleMini is TeleDongle, a USB to RF
- interface for communicating with the altimeters. Combined with your
- choice of antenna and
- notebook computer, TeleDongle and our associated user interface software
- form a complete ground station capable of logging and displaying in-flight
- telemetry, aiding rocket recovery, then processing and archiving flight
+ TeleDongle was our first ground station, providing a USB to RF
+ interfaces for communicating with the altimeters. Combined with
+ your choice of antenna and notebook computer, TeleDongle and our
+ associated user interface software form a complete ground
+ station capable of logging and displaying in-flight telemetry,
+ aiding rocket recovery, then processing and archiving flight
data for analysis and review.
+ </p><p>
+ For a slightly more portable ground station experience that also
+ provides direct rocket recovery support, TeleBT offers flight
+ monitoring and data logging using a Bluetooth connection between
+ the receiver and an Android device that has the Altos Droid
+ application installed from the Google Play store.
</p><p>
More products will be added to the Altus Metrum family over time, and
we currently envision that this will be a single, comprehensive manual
for the entire product family.
- </p></div><div class="chapter" title="Chapter 2. Getting Started"><div class="titlepage"><div><div><h2 class="title"><a name="idp130344"></a>Chapter 2. Getting Started</h2></div></div></div><p>
+ </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp49504"></a>Chapter 2. Getting Started</h1></div></div></div><p>
The first thing to do after you check the inventory of parts in your
"starter kit" is to charge the battery.
</p><p>
</p><p>
The TeleMini battery can be charged by disconnecting it from the
TeleMini board and plugging it into a standalone battery charger
- board, and connecting that via a USB cable to a laptop or other USB
- power source
+ such as the LipoCharger product included in TeleMini Starter Kits,
+ and connecting that via a USB cable to a laptop or other USB
+ power source.
</p><p>
The other active device in the starter kit is the TeleDongle USB to
RF interface. If you plug it in to your Mac or Linux computer it should
Full source code and build instructions are also available.
The latest version may always be downloaded from
<a class="ulink" href="http://altusmetrum.org/AltOS" target="_top">http://altusmetrum.org/AltOS</a>.
- </p></div><div class="chapter" title="Chapter 3. Handling Precautions"><div class="titlepage"><div><div><h2 class="title"><a name="idp2651808"></a>Chapter 3. Handling Precautions</h2></div></div></div><p>
+ </p><p>
+ If you're using a TeleBT instead of the TeleDongle, you'll want
+ to go install the Altos Droid application from the Google Play
+ store. You don't need a data plan to use Altos Droid, but
+ without network access, the Map view will be less useful as it
+ won't contain any map data. You can also use TeleBT connected
+ over USB with your laptop computer; it acts exactly like a
+ TeleDongle. Anywhere this manual talks about TeleDongle, you can
+ also read that as 'and TeleBT when connected via USB'.
+ </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp2493720"></a>Chapter 3. Handling Precautions</h1></div></div></div><p>
All Altus Metrum products are sophisticated electronic devices.
When handled gently and properly installed in an air-frame, they
will deliver impressive results. However, as with all electronic
As with all other rocketry electronics, Altus Metrum altimeters must
be protected from exposure to corrosive motor exhaust and ejection
charge gasses.
- </p></div><div class="chapter" title="Chapter 4. Hardware Overview"><div class="titlepage"><div><div><h2 class="title"><a name="idp3378840"></a>Chapter 4. Hardware Overview</h2></div></div></div><p>
+ </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp2765656"></a>Chapter 4. Hardware Overview</h1></div></div></div><p>
TeleMetrum is a 1 inch by 2.75 inch circuit board. It was designed to
fit inside coupler for 29mm air-frame tubing, but using it in a tube that
small in diameter may require some creativity in mounting and wiring
A typical TeleMetrum or TeleMini installation involves attaching
only a suitable Lithium Polymer battery, a single pole switch for
power on/off, and two pairs of wires connecting e-matches for the
- apogee and main ejection charges.
+ apogee and main ejection charges. All Altus Metrum products are
+ designed for use with single-cell batteries with 3.7 volts nominal.
+ </p><p>
+ The battery connectors are a standard 2-pin JST connector and
+ match batteries sold by Spark Fun. These batteries are
+ single-cell Lithium Polymer batteries that nominally provide 3.7
+ volts. Other vendors sell similar batteries for RC aircraft
+ using mating connectors, however the polarity for those is
+ generally reversed from the batteries used by Altus Metrum
+ products. In particular, the Tenergy batteries supplied for use
+ in Featherweight flight computers are not compatible with Altus
+ Metrum flight computers or battery chargers. <span class="emphasis"><em>Check
+ polarity and voltage before connecting any battery not purchased
+ from Altus Metrum or Spark Fun.</em></span>
</p><p>
By default, we use the unregulated output of the Li-Po battery directly
to fire ejection charges. This works marvelously with standard
connection, and, on TeleMetrum, you can unplug the integrated GPS
antenna and select an appropriate off-board GPS antenna with
cable terminating in a U.FL connector.
- </p></div><div class="chapter" title="Chapter 5. System Operation"><div class="titlepage"><div><div><h2 class="title"><a name="idp3276128"></a>Chapter 5. System Operation</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp3062368">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idp2460120">2. GPS </a></span></dt><dt><span class="section"><a href="#idp2052200">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idp2662856">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idp3396632">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idp2696208">6. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2397232">6.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp2441424">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp1908928">6.3. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idp3092808">6.4. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp1888288">6.5. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp2487664">6.6. Pad Orientation</a></span></dt></dl></dd></dl></div><div class="section" title="1. Firmware Modes"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3062368"></a>1. Firmware Modes </h2></div></div></div><p>
+ </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp2919872"></a>Chapter 5. System Operation</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp2375600">1. Firmware Modes </a></span></dt><dt><span class="section"><a href="#idp2284648">2. GPS </a></span></dt><dt><span class="section"><a href="#idp753536">3. Controlling An Altimeter Over The Radio Link</a></span></dt><dt><span class="section"><a href="#idp760992">4. Ground Testing </a></span></dt><dt><span class="section"><a href="#idp762792">5. Radio Link </a></span></dt><dt><span class="section"><a href="#idp55640">6. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp56488">6.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp57656">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp59488">6.3. Main Deployment Altitude</a></span></dt><dt><span class="section"><a href="#idp61128">6.4. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp64904">6.5. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp66248">6.6. Pad Orientation</a></span></dt></dl></dd></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2375600"></a>1. Firmware Modes </h2></div></div></div><p>
The AltOS firmware build for the altimeters has two
fundamental modes, "idle" and "flight". Which of these modes
the firmware operates in is determined at start up time. For
flashes before launching! For apogee-only or motor eject
flights, do what makes sense.
</p><p>
- If idle mode is entered, you will hear an audible "di-dit" or see
- two short flashes ("I" for idle), and the flight state machine is
- disengaged, thus no ejection charges will fire. The altimeters also
- listen for the radio link when in idle mode for requests sent via
- TeleDongle. Commands can be issued to a TeleMetrum in idle mode
- over either
- USB or the radio link equivalently. TeleMini only has the radio link.
- Idle mode is useful for configuring the altimeter, for extracting data
- from the on-board storage chip after flight, and for ground testing
+ If idle mode is entered, you will hear an audible "di-dit" or
+ see two short flashes ("I" for idle), and the flight state
+ machine is disengaged, thus no ejection charges will fire.
+ The altimeters also listen for the radio link when in idle
+ mode for requests sent via TeleDongle. Commands can be issued
+ to a TeleMetrum in idle mode over either USB or the radio link
+ equivalently. TeleMini only has the radio link. Idle mode is
+ useful for configuring the altimeter, for extracting data from
+ the on-board storage chip after flight, and for ground testing
pyro charges.
</p><p>
One "neat trick" of particular value when TeleMetrum is used with
step of a rickety step-ladder or hanging off the side of a launch
tower with a screw-driver trying to turn on your avionics before
installing igniters!
- </p></div><div class="section" title="2. GPS"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2460120"></a>2. GPS </h2></div></div></div><p>
+ </p><p>
+ TeleMini is configured via the radio link. Of course, that
+ means you need to know the TeleMini radio configuration values
+ or you won't be able to communicate with it. For situations
+ when you don't have the radio configuration values, TeleMini
+ offers an 'emergency recovery' mode. In this mode, TeleMini is
+ configured as follows:
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
+ Sets the radio frequency to 434.550MHz
+ </li><li class="listitem">
+ Sets the radio calibration back to the factory value.
+ </li><li class="listitem">
+ Sets the callsign to N0CALL
+ </li><li class="listitem">
+ Does not go to 'pad' mode after five seconds.
+ </li></ul></div><p>
+ </p><p>
+ To get into 'emergency recovery' mode, first find the row of
+ four small holes opposite the switch wiring. Using a short
+ piece of small gauge wire, connect the outer two holes
+ together, then power TeleMini up. Once the red LED is lit,
+ disconnect the wire and the board should signal that it's in
+ 'idle' mode after the initial five second startup period.
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2284648"></a>2. GPS </h2></div></div></div><p>
TeleMetrum includes a complete GPS receiver. A complete explanation
of how GPS works is beyond the scope of this manual, but the bottom
line is that the TeleMetrum GPS receiver needs to lock onto at least
is turned back on, the GPS system should lock very quickly, typically
long before igniter installation and return to the flight line are
complete.
- </p></div><div class="section" title="3. Controlling An Altimeter Over The Radio Link"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2052200"></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 ability to create a two way command link between TeleDongle
- and an altimeter using the digital radio transceivers built into
- each device. This allows you to interact with the altimeter from
- afar, as if it were directly connected to the computer.
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp753536"></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
+ ability to create a two way command link between TeleDongle
+ and an altimeter using the digital radio transceivers
+ built into each device. This allows you to interact with the
+ altimeter from afar, as if it were directly connected to the
+ computer.
</p><p>
Any operation which can be performed with TeleMetrum can
either be done with TeleMetrum directly connected to the
appropriate TeleDongle device. Once the flight monitoring
window is open, select the desired frequency and then close it
down again. All radio communications will now use that frequency.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Save Flight Data—Recover flight data from the rocket without
opening it up.
</p></li><li class="listitem"><p>
</p><p>
You can monitor the operation of the radio link by watching the
lights on the devices. The red LED will flash each time a packet
- is tramsitted, while the green LED will light up on TeleDongle when
+ is transmitted, while the green LED will light up on TeleDongle when
it is waiting to receive a packet from the altimeter.
- </p></div><div class="section" title="4. Ground Testing"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2662856"></a>4. Ground Testing </h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp760992"></a>4. Ground Testing </h2></div></div></div><p>
An important aspect of preparing a rocket using electronic deployment
for flight is ground testing the recovery system. Thanks
to the bi-directional radio link central to the Altus Metrum system,
manual command. You can now command the altimeter to fire the apogee
or main charges from a safe distance using your computer and
TeleDongle and the Fire Igniter tab to complete ejection testing.
- </p></div><div class="section" title="5. Radio Link"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3396632"></a>5. Radio Link </h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp762792"></a>5. Radio Link </h2></div></div></div><p>
The chip our boards are based on incorporates an RF transceiver, but
it's not a full duplex system... each end can only be transmitting or
receiving at any given moment. So we had to decide how to manage the
with a 5-element yagi on the ground. We hope to fly boards to higher
altitudes over time, and would of course appreciate customer feedback
on performance in higher altitude flights!
- </p></div><div class="section" title="6. Configurable Parameters"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2696208"></a>6. Configurable Parameters</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp55640"></a>6. Configurable Parameters</h2></div></div></div><p>
Configuring an Altus Metrum altimeter for flight is very
simple. Even on our baro-only TeleMini board, the use of a Kalman
filter means there is no need to set a "mach delay". The few
configurable parameters can all be set using AltosUI over USB or
or radio link via TeleDongle.
- </p><div class="section" title="6.1. Radio Frequency"><div class="titlepage"><div><div><h3 class="title"><a name="idp2397232"></a>6.1. Radio Frequency</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp56488"></a>6.1. Radio Frequency</h3></div></div></div><p>
Altus Metrum boards support radio frequencies in the 70cm
band. By default, the configuration interface provides a
list of 10 "standard" frequencies in 100kHz channels starting at
frequency will be used to avoid interference. And of course, both
altimeter and TeleDongle must be configured to the same
frequency to successfully communicate with each other.
- </p></div><div class="section" title="6.2. Apogee Delay"><div class="titlepage"><div><div><h3 class="title"><a name="idp2441424"></a>6.2. Apogee Delay</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp57656"></a>6.2. Apogee Delay</h3></div></div></div><p>
Apogee delay is the number of seconds after the altimeter detects flight
apogee that the drogue charge should be fired. In most cases, this
should be left at the default of 0. However, if you are flying
or 3 seconds later to avoid any chance of both charges
firing simultaneously. We've flown several air-frames this
way quite happily, including Keith's successful L3 cert.
- </p></div><div class="section" title="6.3. Main Deployment Altitude"><div class="titlepage"><div><div><h3 class="title"><a name="idp1908928"></a>6.3. Main Deployment Altitude</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp59488"></a>6.3. Main Deployment Altitude</h3></div></div></div><p>
By default, the altimeter will fire the main deployment charge at an
elevation of 250 meters (about 820 feet) above ground. We think this
is a good elevation for most air-frames, but feel free to change this
deployment elevation for the backup altimeter to be something lower
than the primary so that both pyrotechnic charges don't fire
simultaneously.
- </p></div><div class="section" title="6.4. Maximum Flight Log"><div class="titlepage"><div><div><h3 class="title"><a name="idp3092808"></a>6.4. Maximum Flight Log</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp61128"></a>6.4. Maximum Flight Log</h3></div></div></div><p>
TeleMetrum version 1.1 and 1.2 have 2MB of on-board flash storage,
enough to hold over 40 minutes of data at full data rate
(100 samples/second). TeleMetrum 1.0 has 1MB of on-board
the limited storage, TeleMini cannot hold data for more than
one flight, and so must be erased after each flight or it
will not capture data for subsequent flights.
- </p></div><div class="section" title="6.5. Ignite Mode"><div class="titlepage"><div><div><h3 class="title"><a name="idp1888288"></a>6.5. Ignite Mode</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp64904"></a>6.5. Ignite Mode</h3></div></div></div><p>
Instead of firing one charge at apogee and another charge at
a fixed height above the ground, you can configure the
altimeter to fire both at apogee or both during
main allows some level of redundancy without needing two
flight computers. In Redundant Apogee or Redundant Main
mode, the two charges will be fired two seconds apart.
- </p></div><div class="section" title="6.6. Pad Orientation"><div class="titlepage"><div><div><h3 class="title"><a name="idp2487664"></a>6.6. Pad Orientation</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66248"></a>6.6. Pad Orientation</h3></div></div></div><p>
TeleMetrum measures acceleration along the axis of the
board. Which way the board is oriented affects the sign of
the acceleration value. Instead of trying to guess which way
TeleMetrum board connected to the 70cm antenna to be nearest
the nose of the rocket, with the end containing the screw
terminals nearest the tail.
- </p></div></div></div><div class="chapter" title="Chapter 6. AltosUI"><div class="titlepage"><div><div><h2 class="title"><a name="idp3525088"></a>Chapter 6. AltosUI</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp2539464">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2507712">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idp2116736">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idp3192912">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idp3341456">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idp2011184">1.5. Site Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3564984">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idp3039048">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idp2169992">4. Graph Data</a></span></dt><dt><span class="section"><a href="#idp1875096">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp2578272">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idp2875944">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idp2810064">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp1391912">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idp3569008">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp3546448">6.3. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp2106808">6.4. Radio Calibration</a></span></dt><dt><span class="section"><a href="#idp2727816">6.5. Callsign</a></span></dt><dt><span class="section"><a href="#idp2159880">6.6. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idp2199304">6.7. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp3176768">6.8. Pad Orientation</a></span></dt></dl></dd><dt><span class="section"><a href="#idp1614816">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp1522712">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idp2951344">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idp2704448">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idp2434112">7.4. Font Size</a></span></dt><dt><span class="section"><a href="#idp2866200">7.5. Serial Debug</a></span></dt><dt><span class="section"><a href="#idp2341272">7.6. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idp2198928">8. Flash Image</a></span></dt><dt><span class="section"><a href="#idp3268008">9. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idp2748912">10. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp2545000">11. Load Maps</a></span></dt><dt><span class="section"><a href="#idp2376832">12. Monitor Idle</a></span></dt></dl></div><p>
+ </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp67528"></a>Chapter 6. AltosUI</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp68608">1. Monitor Flight</a></span></dt><dd><dl><dt><span class="section"><a href="#idp75208">1.1. Launch Pad</a></span></dt><dt><span class="section"><a href="#idp3850840">1.2. Ascent</a></span></dt><dt><span class="section"><a href="#idp3852992">1.3. Descent</a></span></dt><dt><span class="section"><a href="#idp3856520">1.4. Landed</a></span></dt><dt><span class="section"><a href="#idp3859448">1.5. Site Map</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3861728">2. Save Flight Data</a></span></dt><dt><span class="section"><a href="#idp3864648">3. Replay Flight</a></span></dt><dt><span class="section"><a href="#idp3865896">4. Graph Data</a></span></dt><dt><span class="section"><a href="#idp3869184">5. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3870192">5.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#idp3871768">5.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3872600">6. Configure Altimeter</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3876776">6.1. Main Deploy Altitude</a></span></dt><dt><span class="section"><a href="#idp3877760">6.2. Apogee Delay</a></span></dt><dt><span class="section"><a href="#idp3878800">6.3. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp3879712">6.4. Radio Calibration</a></span></dt><dt><span class="section"><a href="#idp3880776">6.5. Callsign</a></span></dt><dt><span class="section"><a href="#idp3881512">6.6. Maximum Flight Log Size</a></span></dt><dt><span class="section"><a href="#idp3882376">6.7. Ignite Mode</a></span></dt><dt><span class="section"><a href="#idp3885216">6.8. Pad Orientation</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3887440">7. Configure AltosUI</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3888064">7.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#idp3890336">7.2. Log Directory</a></span></dt><dt><span class="section"><a href="#idp3891560">7.3. Callsign</a></span></dt><dt><span class="section"><a href="#idp3892528">7.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#idp3893432">7.5. Font Size</a></span></dt><dt><span class="section"><a href="#idp3894136">7.6. Serial Debug</a></span></dt><dt><span class="section"><a href="#idp3895048">7.7. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3896032">8. Configure Groundstation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3899952">8.1. Frequency</a></span></dt><dt><span class="section"><a href="#idp3900936">8.2. Radio Calibration</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3901928">9. Flash Image</a></span></dt><dt><span class="section"><a href="#idp3905000">10. Fire Igniter</a></span></dt><dt><span class="section"><a href="#idp3907104">11. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp3908008">12. Load Maps</a></span></dt><dt><span class="section"><a href="#idp3910136">13. Monitor Idle</a></span></dt></dl></div><p>
The AltosUI program provides a graphical user interface for
interacting with the Altus Metrum product family, including
TeleMetrum, TeleMini and TeleDongle. AltosUI can monitor telemetry data,
buttons, one for each major activity in the system. This manual
is split into chapters, each of which documents one of the tasks
provided from the top-level toolbar.
- </p><div class="section" title="1. Monitor Flight"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2539464"></a>1. Monitor Flight</h2></div><div><h3 class="subtitle">Receive, Record and Display Telemetry Data</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp68608"></a>1. Monitor Flight</h2></div><div><h3 class="subtitle">Receive, Record and Display Telemetry Data</h3></div></div></div><p>
Selecting this item brings up a dialog box listing all of the
connected TeleDongle devices. When you choose one of these,
AltosUI will create a window to display telemetry data as
Below the TeleDongle frequency selector, the window contains a few
significant pieces of information about the altimeter providing
the telemetry data stream:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>The configured call-sign</p></li><li class="listitem"><p>The device serial number</p></li><li class="listitem"><p>The flight number. Each altimeter remembers how many
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>The configured call-sign</p></li><li class="listitem"><p>The device serial number</p></li><li class="listitem"><p>The flight number. Each altimeter remembers how many
times it has flown.
</p></li><li class="listitem"><p>
The rocket flight state. Each flight passes through several
weaker signals may not be receivable. The packet link uses
error detection and correction techniques which prevent
incorrect data from being reported.
+ </p></li><li class="listitem"><p>
+ The age of the displayed data, in seconds since the last
+ successfully received telemetry packet. In normal operation
+ this will stay in the low single digits. If the number starts
+ counting up, then you are no longer receiving data over the radio
+ link from the flight computer.
</p></li></ul></div><p>
Finally, the largest portion of the window contains a set of
tabs, each of which contain some information about the rocket.
data relevant to the current state of the flight. You can select
other tabs at any time. The final 'table' tab displays all of
the raw telemetry values in one place in a spreadsheet-like format.
- </p><div class="section" title="1.1. Launch Pad"><div class="titlepage"><div><div><h3 class="title"><a name="idp2507712"></a>1.1. Launch Pad</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp75208"></a>1.1. Launch Pad</h3></div></div></div><p>
The 'Launch Pad' tab shows information used to decide when the
rocket is ready for flight. The first elements include red/green
indicators, if any of these is red, you'll want to evaluate
whether the rocket is ready to launch:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Battery Voltage. This indicates whether the Li-Po battery
powering the TeleMetrum has sufficient charge to last for
the duration of the flight. A value of more than
and altitude, averaging many reported positions to improve the
accuracy of the fix.
</p><p>
- </p></div><div class="section" title="1.2. Ascent"><div class="titlepage"><div><div><h3 class="title"><a name="idp2116736"></a>1.2. Ascent</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3850840"></a>1.2. Ascent</h3></div></div></div><p>
This tab is shown during Boost, Fast and Coast
phases. The information displayed here helps monitor the
rocket as it heads towards apogee.
Finally, the current igniter voltages are reported as in the
Launch Pad tab. This can help diagnose deployment failures
caused by wiring which comes loose under high acceleration.
- </p></div><div class="section" title="1.3. Descent"><div class="titlepage"><div><div><h3 class="title"><a name="idp3192912"></a>1.3. Descent</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3852992"></a>1.3. Descent</h3></div></div></div><p>
Once the rocket has reached apogee and (we hope) activated the
apogee charge, attention switches to tracking the rocket on
the way back to the ground, and for dual-deploy flights,
components, but generally range from 15-30m/s on drogue and should
be below 10m/s when under the main parachute in a dual-deploy flight.
</p><p>
- For TeleMetrum altimeters, you can locate the rocket in the sky
- using the elevation and
- bearing information to figure out where to look. Elevation is
- in degrees above the horizon. Bearing is reported in degrees
- relative to true north. Range can help figure out how big the
- rocket will appear. Note that all of these values are relative
- to the pad location. If the elevation is near 90°, the rocket
- is over the pad, not over you.
+ For TeleMetrum altimeters, you can locate the rocket in the
+ sky using the elevation and bearing information to figure
+ out where to look. Elevation is in degrees above the
+ horizon. Bearing is reported in degrees relative to true
+ north. Range can help figure out how big the rocket will
+ appear. Ground Distance shows how far it is to a point
+ directly under the rocket and can help figure out where the
+ rocket is likely to land. Note that all of these values are
+ relative to the pad location. If the elevation is near 90°,
+ the rocket is over the pad, not over you.
</p><p>
Finally, the igniter voltages are reported in this tab as
well, both to monitor the main charge as well as to see what
e-matches are designed to retain continuity even after being
fired, and will continue to show as green or return from red to
green after firing.
- </p></div><div class="section" title="1.4. Landed"><div class="titlepage"><div><div><h3 class="title"><a name="idp3341456"></a>1.4. Landed</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3856520"></a>1.4. Landed</h3></div></div></div><p>
Once the rocket is on the ground, attention switches to
recovery. While the radio signal is often lost once the
rocket is on the ground, the last reported GPS position is
To get more detailed information about the flight, you can
click on the 'Graph Flight' button which will bring up a
graph window for the current flight.
- </p></div><div class="section" title="1.5. Site Map"><div class="titlepage"><div><div><h3 class="title"><a name="idp2011184"></a>1.5. Site Map</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3859448"></a>1.5. Site Map</h3></div></div></div><p>
When the TeleMetrum has a GPS fix, the Site Map tab will map
the rocket's position to make it easier for you to locate the
rocket, both while it is in the air, and when it has landed. The
</p><p>
You can pre-load images for your favorite launch sites
before you leave home; check out the 'Preload Maps' section below.
- </p></div></div><div class="section" title="2. Save Flight Data"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3564984"></a>2. Save Flight Data</h2></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3861728"></a>2. Save Flight Data</h2></div></div></div><p>
The altimeter records flight data to its internal flash memory.
TeleMetrum data is recorded at a much higher rate than the telemetry
system can handle, and is not subject to radio drop-outs. As
The file name for each flight log is computed automatically
from the recorded flight date, altimeter serial number and
flight number information.
- </p></div><div class="section" title="3. Replay Flight"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3039048"></a>3. Replay Flight</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3864648"></a>3. Replay Flight</h2></div></div></div><p>
Select this button and you are prompted to select a flight
record file, either a .telem file recording telemetry data or a
.eeprom file containing flight data saved from the altimeter
Once a flight record is selected, the flight monitor interface
is displayed and the flight is re-enacted in real time. Check
the Monitor Flight chapter above to learn how this window operates.
- </p></div><div class="section" title="4. Graph Data"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2169992"></a>4. Graph Data</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3865896"></a>4. Graph Data</h2></div></div></div><p>
Select this button and you are prompted to select a flight
record file, either a .telem file recording telemetry data or a
.eeprom file containing flight data saved from
flash memory.
</p><p>
- Once a flight record is selected, a window with two tabs is
+ Once a flight record is selected, a window with four tabs is
opened. The first tab contains a graph with acceleration
(blue), velocity (green) and altitude (red) of the flight,
- measured in metric units. The
- apogee(yellow) and main(magenta) igniter voltages are also
- displayed; high voltages indicate continuity, low voltages
- indicate open circuits. The second tab contains some basic
- flight statistics.
+ measured in metric units. The apogee(yellow) and main(magenta)
+ igniter voltages are also displayed; high voltages indicate
+ continuity, low voltages indicate open circuits. The second
+ tab lets you configure which data to show in the graph. The
+ third contains some basic flight statistics while the fourth
+ has a map with the ground track of the flight displayed.
</p><p>
The graph can be zoomed into a particular area by clicking and
dragging down and to the right. Once zoomed, the graph can be
Note that telemetry files will generally produce poor graphs
due to the lower sampling rate and missed telemetry packets.
Use saved flight data in .eeprom files for graphing where possible.
- </p></div><div class="section" title="5. Export Data"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp1875096"></a>5. Export Data</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3869184"></a>5. Export Data</h2></div></div></div><p>
This tool takes the raw data files and makes them available for
external analysis. When you select this button, you are prompted to
select a flight
data). Next, a second dialog appears which is used to select
where to write the resulting file. It has a selector to choose
between CSV and KML file formats.
- </p><div class="section" title="5.1. Comma Separated Value Format"><div class="titlepage"><div><div><h3 class="title"><a name="idp2578272"></a>5.1. Comma Separated Value Format</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3870192"></a>5.1. Comma Separated Value Format</h3></div></div></div><p>
This is a text file containing the data in a form suitable for
import into a spreadsheet or other external data analysis
tool. The first few lines of the file contain the version and
the sensor values are converted to standard units, with the
barometric data reported in both pressure, altitude and
height above pad units.
- </p></div><div class="section" title="5.2. Keyhole Markup Language (for Google Earth)"><div class="titlepage"><div><div><h3 class="title"><a name="idp2875944"></a>5.2. Keyhole Markup Language (for Google Earth)</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3871768"></a>5.2. Keyhole Markup Language (for Google Earth)</h3></div></div></div><p>
This is the format used by Google Earth to provide an overlay
within that application. With this, you can use Google Earth to
see the whole flight path in 3D.
- </p></div></div><div class="section" title="6. Configure Altimeter"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2810064"></a>6. Configure Altimeter</h2></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3872600"></a>6. Configure Altimeter</h2></div></div></div><p>
Select this button and then select either a TeleMetrum or
TeleDongle Device from the list provided. Selecting a TeleDongle
device will use the radio link to configure a remote altimeter.
individual configuration entries.
</p><p>
At the bottom of the dialog, there are four buttons:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Save. This writes any changes to the
configuration parameter block in flash memory. If you don't
press this button, any changes you make will be lost.
lost.
</p></li></ul></div><p>
The rest of the dialog contains the parameters to be configured.
- </p><div class="section" title="6.1. Main Deploy Altitude"><div class="titlepage"><div><div><h3 class="title"><a name="idp1391912"></a>6.1. Main Deploy Altitude</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3876776"></a>6.1. Main Deploy Altitude</h3></div></div></div><p>
This sets the altitude (above the recorded pad altitude) at
which the 'main' igniter will fire. The drop-down menu shows
some common values, but you can edit the text directly and
choose whatever you like. If the apogee charge fires below
this altitude, then the main charge will fire two seconds
after the apogee charge fires.
- </p></div><div class="section" title="6.2. Apogee Delay"><div class="titlepage"><div><div><h3 class="title"><a name="idp3569008"></a>6.2. Apogee Delay</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3877760"></a>6.2. Apogee Delay</h3></div></div></div><p>
When flying redundant electronics, it's often important to
ensure that multiple apogee charges don't fire at precisely
the same time, as that can over pressurize the apogee deployment
Delay parameter tells the flight computer to fire the apogee
charge a certain number of seconds after apogee has been
detected.
- </p></div><div class="section" title="6.3. Radio Frequency"><div class="titlepage"><div><div><h3 class="title"><a name="idp3546448"></a>6.3. Radio Frequency</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3878800"></a>6.3. Radio Frequency</h3></div></div></div><p>
This configures which of the configured frequencies to use for both
telemetry and packet command mode. Note that if you set this
value via packet command mode, you will have to reconfigure
the TeleDongle frequency before you will be able to use packet
command mode again.
- </p></div><div class="section" title="6.4. Radio Calibration"><div class="titlepage"><div><div><h3 class="title"><a name="idp2106808"></a>6.4. Radio Calibration</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3879712"></a>6.4. Radio Calibration</h3></div></div></div><p>
The radios in every Altus Metrum device are calibrated at the
factory to ensure that they transmit and receive on the
specified frequency. If you need to you can adjust the calibration
the value means, read the appendix on calibration and/or the source
code for more information. To change a TeleDongle's calibration,
you must reprogram the unit completely.
- </p></div><div class="section" title="6.5. Callsign"><div class="titlepage"><div><div><h3 class="title"><a name="idp2727816"></a>6.5. Callsign</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3880776"></a>6.5. Callsign</h3></div></div></div><p>
This sets the call sign included in each telemetry packet. Set this
as needed to conform to your local radio regulations.
- </p></div><div class="section" title="6.6. Maximum Flight Log Size"><div class="titlepage"><div><div><h3 class="title"><a name="idp2159880"></a>6.6. Maximum Flight Log Size</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3881512"></a>6.6. Maximum Flight Log Size</h3></div></div></div><p>
This sets the space (in kilobytes) allocated for each flight
log. The available space will be divided into chunks of this
size. A smaller value will allow more flights to be stored,
a larger value will record data from longer flights.
- </p></div><div class="section" title="6.7. Ignite Mode"><div class="titlepage"><div><div><h3 class="title"><a name="idp2199304"></a>6.7. Ignite Mode</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3882376"></a>6.7. Ignite Mode</h3></div></div></div><p>
TeleMetrum and TeleMini provide two igniter channels as they
were originally designed as dual-deploy flight
computers. This configuration parameter allows the two
channels to be used in different configurations.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Dual Deploy. This is the usual mode of operation; the
'apogee' channel is fired at apogee and the 'main'
channel at the height above ground specified by the
Altitude setting during descent. The 'apogee'
channel is fired first, followed after a two second
delay by the 'main' channel.
- </p></li></ul></div></div><div class="section" title="6.8. Pad Orientation"><div class="titlepage"><div><div><h3 class="title"><a name="idp3176768"></a>6.8. Pad Orientation</h3></div></div></div><p>
+ </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3885216"></a>6.8. Pad Orientation</h3></div></div></div><p>
Because it includes an accelerometer, TeleMetrum is
sensitive to the orientation of the board. By default, it
expects the antenna end to point forward. This parameter
allows that default to be changed, permitting the board to
be mounted with the antenna pointing aft instead.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Antenna Up. In this mode, the antenna end of the
TeleMetrum board must point forward, in line with the
expected flight path.
Antenna Down. In this mode, the antenna end of the
TeleMetrum board must point aft, in line with the
expected flight path.
- </p></li></ul></div></div></div><div class="section" title="7. Configure AltosUI"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp1614816"></a>7. Configure AltosUI</h2></div></div></div><p>
+ </p></li></ul></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3887440"></a>7. Configure AltosUI</h2></div></div></div><p>
This button presents a dialog so that you can configure the AltosUI global settings.
- </p><div class="section" title="7.1. Voice Settings"><div class="titlepage"><div><div><h3 class="title"><a name="idp1522712"></a>7.1. Voice Settings</h3></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3888064"></a>7.1. Voice Settings</h3></div></div></div><p>
AltosUI provides voice announcements during flight so that you
can keep your eyes on the sky and still get information about
the current flight status. However, sometimes you don't want
to hear them.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Enable—turns all voice announcements on and off</p></li><li class="listitem"><p>
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Enable—turns all voice announcements on and off</p></li><li class="listitem"><p>
Test Voice—Plays a short message allowing you to verify
that the audio system is working and the volume settings
are reasonable
- </p></li></ul></div></div><div class="section" title="7.2. Log Directory"><div class="titlepage"><div><div><h3 class="title"><a name="idp2951344"></a>7.2. Log Directory</h3></div></div></div><p>
+ </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3890336"></a>7.2. Log Directory</h3></div></div></div><p>
AltosUI logs all telemetry data and saves all TeleMetrum flash
data to this directory. This directory is also used as the
staring point when selecting data files for display or export.
Click on the directory name to bring up a directory choosing
dialog, select a new directory and click 'Select Directory' to
change where AltosUI reads and writes data files.
- </p></div><div class="section" title="7.3. Callsign"><div class="titlepage"><div><div><h3 class="title"><a name="idp2704448"></a>7.3. Callsign</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3891560"></a>7.3. Callsign</h3></div></div></div><p>
This value is transmitted in each command packet sent from
TeleDongle and received from an altimeter. It is not used in
telemetry mode, as the callsign configured in the altimeter board
is included in all telemetry packets. Configure this
with the AltosUI operators call sign as needed to comply with
your local radio regulations.
- </p></div><div class="section" title="7.4. Font Size"><div class="titlepage"><div><div><h3 class="title"><a name="idp2434112"></a>7.4. Font Size</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3892528"></a>7.4. Imperial Units</h3></div></div></div><p>
+ This switches between metric units (meters) and imperial
+ units (feet and miles). This affects the display of values
+ use during flight monitoring, data graphing and all of the
+ voice announcements. It does not change the units used when
+ exporting to CSV files, those are always produced in metric units.
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3893432"></a>7.5. Font Size</h3></div></div></div><p>
Selects the set of fonts used in the flight monitor
window. Choose between the small, medium and large sets.
- </p></div><div class="section" title="7.5. Serial Debug"><div class="titlepage"><div><div><h3 class="title"><a name="idp2866200"></a>7.5. Serial Debug</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3894136"></a>7.6. Serial Debug</h3></div></div></div><p>
This causes all communication with a connected device to be
dumped to the console from which AltosUI was started. If
you've started it from an icon or menu entry, the output
will simply be discarded. This mode can be useful to debug
various serial communication issues.
- </p></div><div class="section" title="7.6. Manage Frequencies"><div class="titlepage"><div><div><h3 class="title"><a name="idp2341272"></a>7.6. Manage Frequencies</h3></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3895048"></a>7.7. Manage Frequencies</h3></div></div></div><p>
This brings up a dialog where you can configure the set of
frequencies shown in the various frequency menus. You can
add as many as you like, or even reconfigure the default
set. Changing this list does not affect the frequency
settings of any devices, it only changes the set of
frequencies shown in the menus.
- </p></div></div><div class="section" title="8. Flash Image"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2198928"></a>8. Flash Image</h2></div></div></div><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3896032"></a>8. Configure Groundstation</h2></div></div></div><p>
+ Select this button and then select a TeleDongle Device from the list provided.
+ </p><p>
+ The first few lines of the dialog provide information about the
+ connected device, including the product name,
+ software version and hardware serial number. Below that are the
+ individual configuration entries.
+ </p><p>
+ Note that the TeleDongle itself doesn't save any configuration
+ data, the settings here are recorded on the local machine in
+ the Java preferences database. Moving the TeleDongle to
+ another machine, or using a different user account on the same
+ machine will cause settings made here to have no effect.
+ </p><p>
+ At the bottom of the dialog, there are three buttons:
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
+ Save. This writes any changes to the
+ local Java preferences file. If you don't
+ press this button, any changes you make will be lost.
+ </p></li><li class="listitem"><p>
+ Reset. This resets the dialog to the most recently saved values,
+ erasing any changes you have made.
+ </p></li><li class="listitem"><p>
+ Close. This closes the dialog. Any unsaved changes will be
+ lost.
+ </p></li></ul></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 name="idp3899952"></a>8.1. Frequency</h3></div></div></div><p>
+ This configures the frequency to use for both telemetry and
+ packet command mode. Set this before starting any operation
+ involving packet command mode so that it will use the right
+ frequency. Telemetry monitoring mode also provides a menu to
+ change the frequency, and that menu also sets the same Java
+ preference value used here.
+ </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3900936"></a>8.2. Radio Calibration</h3></div></div></div><p>
+ The radios in every Altus Metrum device are calibrated at the
+ factory to ensure that they transmit and receive on the
+ specified frequency. To change a TeleDongle's calibration,
+ you must reprogram the unit completely, so this entry simply
+ shows the current value and doesn't allow any changes.
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3901928"></a>9. Flash Image</h2></div></div></div><p>
This reprograms any Altus Metrum device by using a TeleMetrum
or TeleDongle as a programming dongle. Please read the
directions for flashing devices in the Updating Device
will have to unplug it and then plug it back in for the USB
connection to reset so that you can communicate with the device
again.
- </p></div><div class="section" title="9. Fire Igniter"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3268008"></a>9. Fire Igniter</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3905000"></a>10. Fire Igniter</h2></div></div></div><p>
This activates the igniter circuits in TeleMetrum to help test
recovery systems deployment. Because this command can operate
over the Packet Command Link, you can prepare the rocket as
you have 10 seconds to press the 'Fire' button or the system
will deactivate, at which point you start over again at
selecting the desired igniter.
- </p></div><div class="section" title="10. Scan Channels"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2748912"></a>10. Scan Channels</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3907104"></a>11. Scan Channels</h2></div></div></div><p>
This listens for telemetry packets on all of the configured
frequencies, displaying information about each device it
receives a packet from. You can select which of the three
telemetry formats should be tried; by default, it only listens
for the standard telemetry packets used in v1.0 and later
firmware.
- </p></div><div class="section" title="11. Load Maps"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2545000"></a>11. Load Maps</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3908008"></a>12. Load Maps</h2></div></div></div><p>
Before heading out to a new launch site, you can use this to
load satellite images in case you don't have internet
connectivity at the site. This loads a fairly large area
once, so if you load more than one launch site, you may get
some gray areas in the map which indicate that Google is tired
of sending data to you. Try again later.
- </p></div><div class="section" title="12. Monitor Idle"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2376832"></a>12. Monitor Idle</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3910136"></a>13. Monitor Idle</h2></div></div></div><p>
This brings up a dialog similar to the Monitor Flight UI,
except it works with the altimeter in "idle" mode by sending
query commands to discover the current state rather than
listening for telemetry packets.
- </p></div></div><div class="chapter" title="Chapter 7. Using Altus Metrum Products"><div class="titlepage"><div><div><h2 class="title"><a name="idp1384336"></a>Chapter 7. Using Altus Metrum Products</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp1372064">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idp2120808">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idp2111736">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idp2590104">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idp916736">5. Future Plans</a></span></dt></dl></div><div class="section" title="1. Being Legal"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp1372064"></a>1. Being Legal</h2></div></div></div><p>
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp3911008"></a>Chapter 7. AltosDroid</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp3912688">1. Installing AltosDroid</a></span></dt><dt><span class="section"><a href="#idp3913648">2. Connecting to TeleBT</a></span></dt><dt><span class="section"><a href="#idp3914864">3. Configuring AltosDroid</a></span></dt><dt><span class="section"><a href="#idp3915736">4. Altos Droid Flight Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp3916536">4.1. Pad</a></span></dt></dl></dd><dt><span class="section"><a href="#idp3922504">5. Downloading Flight Logs</a></span></dt></dl></div><p>
+ AltosDroid provides the same flight monitoring capabilities as
+ AltosUI, but runs on Android devices and is designed to connect
+ to a TeleBT receiver over Bluetooth™. Altos Droid monitors
+ telemetry data, logging it to internal storage in the Android
+ device, and presents that data in a UI the same way the 'Monitor
+ Flight' window does in AltosUI.
+ </p><p>
+ This manual will explain how to configure AltosDroid, connect
+ to TeleBT, operate the flight monitoring interface and describe
+ what the displayed data means.
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3912688"></a>1. Installing AltosDroid</h2></div></div></div><p>
+ AltosDroid is included in the Google Play store. To install
+ it on your Android device, open open the Google Play Store
+ application and search for "altosdroid". Make sure you don't
+ have a space between "altos" and "droid" or you probably won't
+ find what you want. That should bring you to the right page
+ from 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 name="idp3913648"></a>2. Connecting to TeleBT</h2></div></div></div><p>
+ Press the Android 'Menu' button or soft-key to see the
+ configuration options available. Select the 'Connect a device'
+ option and then the 'Scan for devices' entry at the bottom to
+ look for your TeleBT device. Select your device, and when it
+ asks for the code, enter '1234'.
+ </p><p>
+ Subsequent connections will not require you to enter that
+ code, and your 'paired' device will appear in the list without
+ scanning.
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3914864"></a>3. Configuring AltosDroid</h2></div></div></div><p>
+ The only configuration option available for AltosDroid is
+ which frequency to listen on. Press the Android 'Menu' button
+ or soft-key and pick the 'Select radio frequency' entry. That
+ brings up a menu of pre-set radio frequencies; pick the one
+ which matches your altimeter.
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3915736"></a>4. Altos Droid Flight Monitoring</h2></div></div></div><p>
+ Altos Droid is designed to mimic the AltosUI flight monitoring
+ display, providing separate tabs for each stage of your rocket
+ flight along with a tab containing a map of the local area
+ with icons marking the current location of the altimeter and
+ the Android device.
+ </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp3916536"></a>4.1. Pad</h3></div></div></div><p>
+ The 'Launch Pad' tab shows information used to decide when the
+ rocket is ready for flight. The first elements include red/green
+ indicators, if any of these is red, you'll want to evaluate
+ whether the rocket is ready to launch:
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
+ Battery Voltage. This indicates whether the Li-Po battery
+ powering the TeleMetrum has sufficient charge to last for
+ the duration of the flight. A value of more than
+ 3.7V is required for a 'GO' status.
+ </p></li><li class="listitem"><p>
+ Apogee Igniter Voltage. This indicates whether the apogee
+ igniter has continuity. If the igniter has a low
+ resistance, then the voltage measured here will be close
+ to the Li-Po battery voltage. A value greater than 3.2V is
+ required for a 'GO' status.
+ </p></li><li class="listitem"><p>
+ Main Igniter Voltage. This indicates whether the main
+ igniter has continuity. If the igniter has a low
+ resistance, then the voltage measured here will be close
+ to the Li-Po battery voltage. A value greater than 3.2V is
+ required for a 'GO' status.
+ </p></li><li class="listitem"><p>
+ On-board Data Logging. This indicates whether there is
+ space remaining on-board to store flight data for the
+ upcoming flight. If you've downloaded data, but failed
+ to erase flights, there may not be any space
+ left. TeleMetrum can store multiple flights, depending
+ on the configured maximum flight log size. TeleMini
+ stores only a single flight, so it will need to be
+ downloaded and erased after each flight to capture
+ data. This only affects on-board flight logging; the
+ altimeter will still transmit telemetry and fire
+ ejection charges at the proper times.
+ </p></li><li class="listitem"><p>
+ GPS Locked. For a TeleMetrum device, this indicates whether the GPS receiver is
+ currently able to compute position information. GPS requires
+ at least 4 satellites to compute an accurate position.
+ </p></li><li class="listitem"><p>
+ GPS Ready. For a TeleMetrum device, this indicates whether GPS has reported at least
+ 10 consecutive positions without losing lock. This ensures
+ that the GPS receiver has reliable reception from the
+ satellites.
+ </p></li></ul></div><p>
+ </p><p>
+ The Launchpad tab also shows the computed launch pad position
+ and altitude, averaging many reported positions to improve the
+ accuracy of the fix.
+ </p><p>
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3922504"></a>5. Downloading Flight Logs</h2></div></div></div><p>
+ Altos Droid always saves every bit of telemetry data it
+ receives. To download that to a computer for use with AltosUI,
+ simply remove the SD card from your Android device, or connect
+ your device to your computer's USB port and browse the files
+ on that device. You will find '.telem' files in the TeleMetrum
+ directory that will work with AltosUI directly.
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp3923520"></a>Chapter 8. Using Altus Metrum Products</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp3923840">1. Being Legal</a></span></dt><dt><span class="section"><a href="#idp3924800">2. In the Rocket</a></span></dt><dt><span class="section"><a href="#idp3926904">3. On the Ground</a></span></dt><dt><span class="section"><a href="#idp3934536">4. Data Analysis</a></span></dt><dt><span class="section"><a href="#idp3936288">5. Future Plans</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3923840"></a>1. Being Legal</h2></div></div></div><p>
First off, in the US, you need an <a class="ulink" href="http://www.altusmetrum.org/Radio/" target="_top">amateur radio license</a> or
other authorization to legally operate the radio transmitters that are part
of our products.
- </p></div><div class="section" title="2. In the Rocket"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2120808"></a>2. In the Rocket</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3924800"></a>2. In the Rocket</h2></div></div></div><p>
In the rocket itself, you just need a <a class="ulink" href="http://www.altusmetrum.org/TeleMetrum/" target="_top">TeleMetrum</a> or
<a class="ulink" href="http://www.altusmetrum.org/TeleMini/" target="_top">TeleMini</a> board and
- a Li-Po rechargeable battery. An 860mAh battery weighs less than a 9V
- alkaline battery, and will run a TeleMetrum for hours.
+ a single-cell, 3.7 volt nominal Li-Po rechargeable battery. An
+ 850mAh battery weighs less than a 9V alkaline battery, and will
+ run a TeleMetrum for hours.
A 110mAh battery weighs less than a triple A battery and will run a TeleMetrum for
a few hours, or a TeleMini for much (much) longer.
</p><p>
which is opaque to RF signals, you may choose to have an SMA connector
installed so that you can run a coaxial cable to an antenna mounted
elsewhere in the rocket.
- </p></div><div class="section" title="3. On the Ground"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2111736"></a>3. On the Ground</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3926904"></a>3. On the Ground</h2></div></div></div><p>
To receive the data stream from the rocket, you need an antenna and short
- feed-line connected to one of our <a class="ulink" href="http://www.altusmetrum.org/TeleDongle/" target="_top">TeleDongle</a> units. The
+ feed-line connected to one of our <a class="ulink" href="http://www.altusmetrum.org/TeleDongle/" target="_top">TeleDongle</a> units. If possible, use an SMA to BNC
+ adapter instead of feedline between the antenna feedpoint and
+ TeleDongle, as this will give you the best performance. The
TeleDongle in turn plugs directly into the USB port on a notebook
computer. Because TeleDongle looks like a simple serial port, your computer
does not require special device drivers... just plug it in.
</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">
- an antenna and feed-line
+ an antenna and feed-line or adapter
</li><li class="listitem">
a TeleDongle
</li><li class="listitem">
Arrow Antennas.
</a>
The 440-3 and 440-5 are both good choices for finding a
- TeleMetrum- or TeleMini- equipped rocket when used with a suitable 70cm HT.
- </p></div><div class="section" title="4. Data Analysis"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2590104"></a>4. Data Analysis</h2></div></div></div><p>
+ TeleMetrum- or TeleMini- equipped rocket when used with a suitable
+ 70cm HT. TeleDongle and an SMA to BNC adapter fit perfectly
+ between the driven element and reflector of Arrow antennas.
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3934536"></a>4. Data Analysis</h2></div></div></div><p>
Our software makes it easy to log the data from each flight, both the
telemetry received during the flight itself, and the more
complete data log recorded in the flash memory on the altimeter
Our ultimate goal is to emit a set of files for each flight that can be
published as a web page per flight, or just viewed on your local disk with
a web browser.
- </p></div><div class="section" title="5. Future Plans"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp916736"></a>5. Future Plans</h2></div></div></div><p>
- In the future, we intend to offer "companion boards" for the rocket that will
- plug in to TeleMetrum to collect additional data, provide more pyro channels,
- and so forth.
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3936288"></a>5. Future Plans</h2></div></div></div><p>
+ In the future, we intend to offer "companion boards" for the rocket
+ that will plug in to TeleMetrum to collect additional data, provide
+ more pyro channels, and so forth.
+ </p><p>
+ Also under design is a new flight computer with more sensors, more
+ pyro channels, and a more powerful radio system designed for use
+ in multi-stage, complex, and extreme altitude projects.
+ </p><p>
+ We are also working on alternatives to TeleDongle. One is a
+ a stand-alone, hand-held ground terminal that will allow monitoring
+ the rocket's status, collecting data during flight, and logging data
+ after flight without the need for a notebook computer on the
+ flight line. Particularly since it is so difficult to read most
+ notebook screens in direct sunlight, we think this will be a great
+ thing to have. We are also working on a TeleDongle variant with
+ Bluetooth that will work with Android phones and tablets.
</p><p>
- We are also working on the design of a hand-held ground terminal that will
- allow monitoring the rocket's status, collecting data during flight, and
- logging data after flight without the need for a notebook computer on the
- flight line. Particularly since it is so difficult to read most notebook
- screens in direct sunlight, we think this will be a great thing to have.
+ Because all of our work is open, both the hardware designs and the
+ software, if you have some great idea for an addition to the current
+ Altus Metrum family, feel free to dive in and help! Or let us know
+ what you'd like to see that we aren't already working on, and maybe
+ we'll get excited about it too...
</p><p>
- Because all of our work is open, both the hardware designs and the software,
- if you have some great idea for an addition to the current Altus Metrum family,
- feel free to dive in and help! Or let us know what you'd like to see that
- we aren't already working on, and maybe we'll get excited about it too...
- </p></div></div><div class="chapter" title="Chapter 8. Altimeter Installation Recommendations"><div class="titlepage"><div><div><h2 class="title"><a name="idp1877664"></a>Chapter 8. Altimeter Installation Recommendations</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp2776168">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idp3422920">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idp2493216">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idp2097000">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idp3092536">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp3323072">6. Ground Testing</a></span></dt></dl></div><p>
+ Watch our
+ <a class="ulink" href="http://altusmetrum.org/" target="_top">web site</a> for more news
+ and information as our family of products evolves!
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp3939448"></a>Chapter 9. Altimeter Installation Recommendations</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp3940432">1. Mounting the Altimeter</a></span></dt><dt><span class="section"><a href="#idp3942768">2. Dealing with the Antenna</a></span></dt><dt><span class="section"><a href="#idp3946752">3. Preserving GPS Reception</a></span></dt><dt><span class="section"><a href="#idp3949136">4. Radio Frequency Interference</a></span></dt><dt><span class="section"><a href="#idp3953208">5. The Barometric Sensor</a></span></dt><dt><span class="section"><a href="#idp3955048">6. Ground Testing</a></span></dt></dl></div><p>
Building high-power rockets that fly safely is hard enough. Mix
in some sophisticated electronics and a bunch of radio energy
and oftentimes you find few perfect solutions. This chapter
contains some suggestions about how to install Altus Metrum
products into the rocket air-frame, including how to safely and
reliably mix a variety of electronics into the same air-frame.
- </p><div class="section" title="1. Mounting the Altimeter"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2776168"></a>1. Mounting the Altimeter</h2></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3940432"></a>1. Mounting the Altimeter</h2></div></div></div><p>
The first consideration is to ensure that the altimeter is
securely fastened to the air-frame. For TeleMetrum, we use
nylon standoffs and nylon screws; they're good to at least 50G
Watch for any metal touching components on the
board. Shorting out connections on the bottom of the board
can cause the altimeter to fail during flight.
- </li></ol></div></div><div class="section" title="2. Dealing with the Antenna"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3422920"></a>2. Dealing with the Antenna</h2></div></div></div><p>
+ </li></ol></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3942768"></a>2. Dealing with the Antenna</h2></div></div></div><p>
The antenna supplied is just a piece of solid, insulated,
wire. If it gets damaged or broken, it can be easily
replaced. It should be kept straight and not cut; bending or
SMA connector, and then run 50Ω coax from the board to the
antenna. Building a remote antenna is beyond the scope of this
manual.
- </p></div><div class="section" title="3. Preserving GPS Reception"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2493216"></a>3. Preserving GPS Reception</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3946752"></a>3. Preserving GPS Reception</h2></div></div></div><p>
The GPS antenna and receiver in TeleMetrum are highly
sensitive and normally have no trouble tracking enough
satellites to provide accurate position information for
antenna as that's covered with a ground plane. But, keep
wires and metal out from above the patch antenna.
</li></ol></div><p>
- </p></div><div class="section" title="4. Radio Frequency Interference"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2097000"></a>4. Radio Frequency Interference</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3949136"></a>4. Radio Frequency Interference</h2></div></div></div><p>
Any altimeter will generate RFI; the digital circuits use
high-frequency clocks that spray radio interference across a
wide band. Altus Metrum altimeters generate intentional radio
Voltages are induced when radio frequency energy is
transmitted from one circuit to another. Here are things that
influence the induced voltage and current:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
Keep wires from different circuits apart. Moving circuits
further apart will reduce RFI.
</li><li class="listitem">
70cm amateur band, so you should avoid lengths that are a
simple ratio of that length; essentially any multiple of 1/4
of the wavelength (17.5cm).
- </li></ul></div></div><div class="section" title="5. The Barometric Sensor"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3092536"></a>5. The Barometric Sensor</h2></div></div></div><p>
+ </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3953208"></a>5. The Barometric Sensor</h2></div></div></div><p>
Altusmetrum altimeters measure altitude with a barometric
sensor, essentially measuring the amount of air above the
rocket to figure out how high it is. A large number of
chemical damage from the products of APCP or BP combustion, so
make sure the ebay is carefully sealed from any compartment
which contains ejection charges or motors.
- </p></div><div class="section" title="6. Ground Testing"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3323072"></a>6. Ground Testing</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3955048"></a>6. Ground Testing</h2></div></div></div><p>
The most important aspect of any installation is careful
ground testing. Bringing an air-frame up to the LCO table which
hasn't been ground tested can lead to delays or ejection
interface through a TeleDongle to command each charge to
fire. Make sure the charge is sufficient to robustly separate
the air-frame and deploy the recovery system.
- </p></div></div><div class="chapter" title="Chapter 9. Updating Device Firmware"><div class="titlepage"><div><div><h2 class="title"><a name="idp2657144"></a>Chapter 9. Updating Device Firmware</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp2722712">1. Updating TeleMetrum Firmware</a></span></dt><dt><span class="section"><a href="#idp1268600">2. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idp1444904">3. Updating TeleDongle Firmware</a></span></dt></dl></div><p>
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp3957184"></a>Chapter 10. Updating Device Firmware</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp3959184">1. Updating TeleMetrum Firmware</a></span></dt><dt><span class="section"><a href="#idp3964528">2. Updating TeleMini Firmware</a></span></dt><dt><span class="section"><a href="#idp3969944">3. Updating TeleDongle Firmware</a></span></dt></dl></div><p>
The big concept to understand is that you have to use a
TeleDongle as a programmer to update a TeleMetrum or TeleMini,
and a TeleMetrum or other TeleDongle to program the TeleDongle
version from <a class="ulink" href="http://www.altusmetrum.org/AltOS/" target="_top">http://www.altusmetrum.org/AltOS/</a>.
</p><p>
We recommend updating the altimeter first, before updating TeleDongle.
- </p><div class="section" title="1. Updating TeleMetrum Firmware"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2722712"></a>1. Updating TeleMetrum Firmware</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3959184"></a>1. Updating TeleMetrum Firmware</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
Find the 'programming cable' that you got as part of the starter
kit, that has a red 8-pin MicroMaTch connector on one end and a
red 4-pin MicroMaTch connector on the other end.
the version, etc.
</li><li class="listitem">
If something goes wrong, give it another try.
- </li></ol></div></div><div class="section" title="2. Updating TeleMini Firmware"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp1268600"></a>2. Updating TeleMini Firmware</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
+ </li></ol></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3964528"></a>2. Updating TeleMini Firmware</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
You'll need a special 'programming cable' to reprogram the
TeleMini. It's available on the Altus Metrum web store, or
you can make your own using an 8-pin MicroMaTch connector on
letting it come up in "flight" mode and listening for telemetry.
</li><li class="listitem">
If something goes wrong, give it another try.
- </li></ol></div></div><div class="section" title="3. Updating TeleDongle Firmware"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp1444904"></a>3. Updating TeleDongle Firmware</h2></div></div></div><p>
+ </li></ol></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3969944"></a>3. Updating TeleDongle Firmware</h2></div></div></div><p>
Updating TeleDongle's firmware is just like updating TeleMetrum or TeleMini
firmware, but you use either a TeleMetrum or another TeleDongle as the programmer.
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
slightly to extract the connector. We used a locking connector on
TeleMetrum to help ensure that the cabling to companion boards
used in a rocket don't ever come loose accidentally in flight.
- </p></div></div><div class="chapter" title="Chapter 10. Hardware Specifications"><div class="titlepage"><div><div><h2 class="title"><a name="idp3431816"></a>Chapter 10. Hardware Specifications</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp2831496">1. TeleMetrum Specifications</a></span></dt><dt><span class="section"><a href="#idp3455400">2. TeleMini Specifications</a></span></dt></dl></div><div class="section" title="1. TeleMetrum Specifications"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2831496"></a>1. TeleMetrum Specifications</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
+ </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp3977040"></a>Chapter 11. Hardware Specifications</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp3977360">1. TeleMetrum Specifications</a></span></dt><dt><span class="section"><a href="#idp3983088">2. TeleMini Specifications</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3977360"></a>1. TeleMetrum Specifications</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Recording altimeter for model rocketry.
</p></li><li class="listitem"><p>
Supports dual deployment (can fire 2 ejection charges).
optional separate pyro battery if needed.
</p></li><li class="listitem"><p>
2.75 x 1 inch board designed to fit inside 29mm air-frame coupler tube.
- </p></li></ul></div></div><div class="section" title="2. TeleMini Specifications"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3455400"></a>2. TeleMini Specifications</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
+ </p></li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp3983088"></a>2. TeleMini Specifications</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
Recording altimeter for model rocketry.
</p></li><li class="listitem"><p>
Supports dual deployment (can fire 2 ejection charges).
</p></li><li class="listitem"><p>
On-board 5 kilobyte non-volatile memory for flight data storage.
</p></li><li class="listitem"><p>
- RF interface for battery charging, configuration, and data recovery.
+ RF interface for configuration, and data recovery.
</p></li><li class="listitem"><p>
Support for Li-Po rechargeable batteries, using an external charger.
</p></li><li class="listitem"><p>
optional separate pyro battery if needed.
</p></li><li class="listitem"><p>
1.5 x .5 inch board designed to fit inside 18mm air-frame coupler tube.
- </p></li></ul></div></div></div><div class="chapter" title="Chapter 11. FAQ"><div class="titlepage"><div><div><h2 class="title"><a name="idp3104824"></a>Chapter 11. FAQ</h2></div></div></div><p>
+ </p></li></ul></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp3987896"></a>Chapter 12. FAQ</h1></div></div></div><p>
TeleMetrum seems to shut off when disconnected from the
computer. Make sure the battery is adequately charged. Remember the
unit will pull more power than the USB port can deliver before the
data after physically retrieving your altimeter. Make sure to save
the on-board data after each flight; while the TeleMetrum can store
multiple flights, you never know when you'll lose the altimeter...
- </p></div><div class="appendix" title="Appendix A. Notes for Older Software"><div class="titlepage"><div><div><h2 class="title"><a name="idp2639136"></a>Appendix A. Notes for Older Software</h2></div></div></div><p>
+ </p></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp3991640"></a>Appendix A. Notes for Older Software</h1></div></div></div><p>
<span class="emphasis"><em>
Before AltosUI was written, using Altus Metrum devices required
some finesse with the Linux command line. There was a limited
the Log and Device menus. It has a wonderful display of the incoming
flight data and I am sure you will enjoy what it has to say to you
once you enable the voice output!
- </p></div><div class="appendix" title="Appendix B. Calibration"><div class="titlepage"><div><div><h2 class="title"><a name="idp2228272"></a>Appendix B. Calibration</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="#idp1912752">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp2744568">2. TeleMetrum Accelerometer</a></span></dt></dl></div><p>
+ </p></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp4008072"></a>Appendix B. Drill Templates</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp4008720">1. TeleMetrum template</a></span></dt><dt><span class="section"><a href="#idp4016464">2. TeleMini template</a></span></dt></dl></div><p>
+ These images, when printed, provide precise templates for the
+ mounting holes in Altus Metrum flight computers
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp4008720"></a>1. TeleMetrum template</h2></div></div></div><p>
+ TeleMetrum has overall dimensions of 1.000 x 2.750 inches, and the
+ mounting holes are sized for use with 4-40 or M3 screws.
+ </p><div class="mediaobject"><a name="TeleMetrumTemplate"></a><object type="image/svg+xml" data="telemetrum.svg"></object></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp4016464"></a>2. TeleMini template</h2></div></div></div><p>
+ TeleMini has overall dimensions of 0.500 x 1.500 inches, and the
+ mounting holes are sized for use with 2-56 or M2 screws.
+ </p><div class="mediaobject"><a name="TeleMiniTemplate"></a><object type="image/svg+xml" data="telemini.svg"></object></div></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp4018112"></a>Appendix C. Calibration</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp4019088">1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp4022408">2. TeleMetrum Accelerometer</a></span></dt></dl></div><p>
There are only two calibrations required for a TeleMetrum board, and
only one for TeleDongle and TeleMini. All boards are shipped from
the factory pre-calibrated, but the procedures are documented here
AltosUI, you must connect to the board with a serial terminal program
and interact directly with the on-board command interpreter to effect
calibration.
- </p><div class="section" title="1. Radio Frequency"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp1912752"></a>1. Radio Frequency</h2></div></div></div><p>
+ </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp4019088"></a>1. Radio Frequency</h2></div></div></div><p>
The radio frequency is synthesized from a clock based on the 48 MHz
crystal on the board. The actual frequency of this oscillator
must be measured to generate a calibration constant. While our
radio frequency is reset to the default 434.550 Mhz. If you want
to use another frequency, you will have to set that again after
calibration is completed.
- </p></div><div class="section" title="2. TeleMetrum Accelerometer"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp2744568"></a>2. TeleMetrum Accelerometer</h2></div></div></div><p>
+ </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp4022408"></a>2. TeleMetrum Accelerometer</h2></div></div></div><p>
The TeleMetrum accelerometer we use has its own 5 volt power
supply and
the output must be passed through a resistive voltage divider to match
to the index post on the 4-pin end of the programming cable, and
power up the board. It should come up in 'idle mode' (two beeps),
allowing a re-cal.
- </p></div></div><div class="appendix" title="Appendix C. Release Notes"><div class="titlepage"><div><div><h2 class="title"><a name="idp1711112"></a>Appendix C. Release Notes</h2></div></div></div><p>
- Version 1.0.3 is a minor release adding support for TeleMetrum v1.2 boards
+ </p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp4027304"></a>Appendix D. Release Notes</h1></div></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp4027664"></a>Version 1.21</h2></div></div></div><p>
+ Version 1.2.1 is a minor release. It adds support for TeleBT and
+ the AltosDroid application, provides several new features in
+ AltosUI and fixes some bugs in the AltOS firmware.
+ </p><p>
+ AltOS Firmware Changes
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
+ Add support for TeleBT
+ </li><li class="listitem">
+ In TeleMini recovery mode (when booted with the outer two
+ debug pins connected together), the radio parameters are also
+ set back to defaults (434.550MHz, N0CALL, factory radio cal).
+ </li><li class="listitem">
+ Add support for reflashing the SkyTraq GPS chips. This
+ requires special host-side code which currently only exists
+ for Linux.
+ </li><li class="listitem">
+ Correct Kalman filter model error covariance matrix. The
+ values used previously assumed continuous measurements instead
+ of discrete measurements.
+ </li><li class="listitem">
+ Fix some bugs in the USB driver for TeleMetrum and TeleDongle
+ that affected Windows users.
+ </li><li class="listitem">
+ Adjusted the automatic gain control parameters that affect
+ receive performance for TeleDongle. Field tests indicate that this
+ may improve receive performance somewhat.
+ </li></ul></div><p>
+ </p><p>
+ AltosUI Changes
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
+ Handle missing GPS lock in 'Descent' tab. Previously, if the
+ GPS position of the pad was unknown, an exception would be
+ raised, breaking the Descent tab contents.
+ </li><li class="listitem">
+ Improve the graph, adding tool-tips to show values near the
+ cursor and making the displayed set of values configurable,
+ adding all of the flight data as options while leaving the
+ default settings alone so that the graph starts by showing
+ height, speed and acceleration.
+ </li><li class="listitem">
+ Make the initial position of the AltosUI top level window
+ configurable. Along with this change, the other windows will
+ pop up at 'sensible' places now, instead of on top of one
+ another.
+ </li><li class="listitem">
+ Add callsign to Monitor idle window and connecting
+ dialogs. This makes it clear which callsign is being used so
+ that the operator will be aware that it must match the flight
+ computer value or no communication will work.
+ </li><li class="listitem">
+ When downloading flight data, display the block number so that
+ the user has some sense of progress. Unfortunately, we don't
+ know how many blocks will need to be downloaded, but at least
+ it isn't just sitting there doing nothing for a long time.
+ </li><li class="listitem">
+ Add GPS data and a map to the graph window. This lets you see
+ a complete summary of the flight without needing to 'replay'
+ the whole thing.
+ </li></ul></div><p>
+ </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp4028224"></a>Version 1.2</h2></div></div></div><p>
+ Version 1.2 is a major release. It adds support for MicroPeak and
+ the MicroPeak USB adapter.
</p><p>
AltOS Firmware Changes
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
- TeleMetrum version 1.2 is functionally identical to version 1.1, the
- only change required in the firmware was to adjust the product name reported
- over the USB link.
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
+ Add MicroPeak support. This includes support for the ATtiny85
+ processor and adaptations to the core code to allow for
+ devices too small to run the multi-tasking scheduler.
+ </li></ul></div><p>
+ </p><p>
+ MicroPeak UI changes
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
+ Added this new application
</li></ul></div><p>
</p><p>
- Version 1.0.2 is a bugfix release, addressing a minor issue
- found in version 1.0.1
+ Distribution Changes
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
+ Distribute Mac OS X packages in disk image ('.dmg') format to
+ greatly simplify installation.
+ </li><li class="listitem">
+ Provide version numbers for the shared Java libraries to
+ ensure that upgrades work properly, and to allow for multiple
+ Altus Metrum software packages to be installed in the same
+ directory at the same time.
+ </li></ul></div><p>
+ </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp4028784"></a>Version 1.1.1</h2></div></div></div><p>
+ Version 1.1.1 is a bug-fix release. It fixes a couple of bugs in
+ AltosUI and one firmware bug that affects TeleMetrum version 1.0
+ boards. Thanks to Bob Brown for help diagnosing the Google Earth
+ file export issue, and for suggesting the addition of the Ground
+ Distance value in the Descent tab.
</p><p>
AltOS Firmware Changes
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
- On TeleMetrum, wait to enable the radio link for remote command operations
- until the device enters either idle or invalid mode. Ticket #26.
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
+ TeleMetrum v1.0 boards use the AT45DB081D flash memory part to
+ store flight data, which is different from later TeleMetrum
+ boards. The AltOS v1.1 driver for this chip couldn't erase
+ memory, leaving it impossible to delete flight data or update
+ configuration values. This bug doesn't affect newer TeleMetrum
+ boards, and it doesn't affect the safety of rockets flying
+ version 1.1 firmware.
+ </li></ul></div><p>
+ </p><p>
+ AltosUI Changes
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
+ Creating a Google Earth file (KML) from on-board flight data
+ (EEPROM) would generate an empty file. The code responsible
+ for reading the EEPROM file wasn't ever setting the GPS valid
+ bits, and so the KML export code thought there was no GPS data
+ in the file.
+ </li><li class="listitem">
+ The “Landed” tab was displaying all values in metric units,
+ even when AltosUI was configured to display imperial
+ units. Somehow I just missed this tab when doing the units stuff.
+ </li><li class="listitem">
+ The “Descent” tab displays the range to the rocket, which is a
+ combination of the over-the-ground distance to the rockets
+ current latitude/longitude and the height of the rocket. As
+ such, it's useful for knowing how far away the rocket is, but
+ difficult to use when estimating where the rocket might
+ eventually land. A new “Ground Distance” field has been added
+ which displays the distance to a spot right underneath the
+ rocket.
+ </li><li class="listitem">
+ Sensor data wasn't being displayed for TeleMini flight
+ computers in Monitor Idle mode, including things like battery
+ voltage. The code that picked which kinds of data to fetch
+ from the flight computer was missing a check for TeleMini when
+ deciding whether to fetch the analog sensor data.
+ </li></ul></div><p>
+ </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp4029344"></a>Version 1.1</h2></div></div></div><p>
+ Version 1.1 is a minor release. It provides a few new features in AltosUI
+ and the AltOS firmware and fixes bugs.
+ </p><p>
+ AltOS Firmware Changes
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
+ Add apogee-lockout value. Overrides the apogee detection logic to
+ prevent incorrect apogee charge firing.
+ </li><li class="listitem">
+ Fix a bug where the data reported in telemetry packets was
+ from 320ms ago.
</li><li class="listitem">
- On TeleMini, delay during reboot for one second to give the
- TeleDongle time to leave radio link mode. Otherwise, the
- TeleDongle would send another radio link packet out while the
- TeleMini was rebooting, sending TeleMini right back to idle
- mode. Ticket #27.
+ Force the radio frequency to 434.550MHz when the debug clock
+ pin is connected to ground at boot time. This provides a way
+ to talk to a TeleMini which is configured to some unknown frequency.
+ </li><li class="listitem">
+ Provide RSSI values for Monitor Idle mode. This makes it easy to check radio
+ range without needing to go to flight mode.
+ </li><li class="listitem">
+ Fix a bug which caused the old received telemetry packets to
+ be retransmitted over the USB link when the radio was turned
+ off and back on.
</li></ul></div><p>
</p><p>
+ AltosUI Changes
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
+ Fix a bug that caused GPS ready to happen too quickly. The
+ software was using every telemetry packet to signal new GPS
+ data, which caused GPS ready to be signalled after 10 packets
+ instead of 10 GPS updates.
+ </li><li class="listitem">
+ Fix Google Earth data export to work with recent versions. The
+ google earth file loading code got a lot pickier, requiring
+ some minor white space changes in the export code.
+ </li><li class="listitem">
+ Make the look-n-feel configurable, providing a choice from
+ the available options.
+ </li><li class="listitem">
+ Add an 'Age' element to mark how long since a telemetry packet
+ has been received. Useful to quickly gauge whether
+ communications with the rocket are still active.
+ </li><li class="listitem">
+ Add 'Configure Ground Station' dialog to set the radio
+ frequency used by a particular TeleDongle without having to go
+ through the flight monitor UI.
+ </li><li class="listitem">
+ Add configuration for the new apogee-lockout value. A menu provides a list of
+ reasonable values, or the value can be set by hand.
+ </li><li class="listitem">
+ Changed how flight data are downloaded. Now there's an initial
+ dialog asking which flights to download, and after that
+ finishes, a second dialog comes up asking which flights to delete.
+ </li><li class="listitem">
+ Re-compute time spent in each state for the flight graph; this
+ figures out the actual boost and landing times instead of
+ using the conservative values provide by the flight
+ electronics. This improves the accuracy of the boost
+ acceleration and main descent rate computations.
+ </li><li class="listitem">
+ Make AltosUI run on Mac OS Lion. The default Java heap space
+ was dramatically reduced for this release causing much of the
+ UI to fail randomly. This most often affected the satellite
+ mapping download and displays.
+ </li><li class="listitem">
+ Change how data are displayed in the 'table' tab of the flight
+ monitoring window. This eliminates entries duplicated from the
+ header and adds both current altitude and pad altitude, which
+ are useful in 'Monitor Idle' mode.
+ </li><li class="listitem">
+ Add Imperial units mode to present data in feet instead of
+ meters.
+ </li></ul></div><p>
+ </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp4029904"></a>Version 1.0.1</h2></div></div></div><p>
Version 1.0.1 is a major release, adding support for the TeleMini
device and lots of new AltosUI features
</p><p>
AltOS Firmware Changes
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
Add TeleMini v1.0 support. Firmware images for TeleMini are
included in AltOS releases.
</li><li class="listitem">
</li></ul></div><p>
</p><p>
AltosUI Changes
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
Wait for altimeter when using packet mode. Instead of quicly
timing out when trying to initialize a packet mode
configuration connection, AltosUI now waits indefinitely for
Flight window so you can immediately see the results of a
flight.
</li></ul></div><p>
- </p><p>
+ </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp4030464"></a>Version 0.9.2</h2></div></div></div><p>
Version 0.9.2 is an AltosUI bug-fix release, with no firmware changes.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
Fix plotting problems due to missing file in the Mac OS install image.
</li><li class="listitem">
Always read whole eeprom blocks, mark empty records invalid, display parsing errors to user.
</li><li class="listitem">
Add software version to Configure AltosUI dialog
- </li></ul></div><p>
+ </li></ul></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp4031024"></a>Version 0.9</h2></div></div></div><p>
Version 0.9 adds a few new firmware features and accompanying
AltosUI changes, along with new hardware support.
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
Support for TeleMetrum v1.1 hardware. Sources for the flash
memory part used in v1.0 dried up, so v1.1 uses a different part
which required a new driver and support for explicit flight log
provided only 8 bits for the device serial number. This change
requires that both ends of the telemetry link be running the 0.9
firmware or they will not communicate.
- </li></ul></div><p>
+ </li></ul></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp4031584"></a>Version 0.8</h2></div></div></div><p>
Version 0.8 offers a major upgrade in the AltosUI
interface. Significant new features include:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
Post-flight graphing tool. This lets you explore the behaviour
of your rocket after flight with a scroll-able and zoom-able
chart showing the altitude, speed and acceleration of the
Exports Google Earth flight tracks. Using the Keyhole Markup
Language (.kml) file format, this provides a 3D view of your
rocket flight through the Google Earth program.
- </li></ul></div><p>
+ </li></ul></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp4032144"></a>Version 0.7.1</h2></div></div></div><p>
Version 0.7.1 is the first release containing our new cross-platform Java-based user interface. AltosUI can:
- </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+ </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
Receive and log telemetry from a connected TeleDongle
device. All data received is saved to log files named with the
current date and the connected rocket serial and flight
range information to try and help you find your rocket in the
air. Once on the ground, the direction and distance are
reported.
- </li></ul></div></div></div></body></html>
+ </li></ul></div></div></div></div></body></html>