1 <?xml version="1.0" encoding="UTF-8"?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>TeleGPS Owner’s Manual</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.79.1" /></head><body><div xml:lang="en" class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a id="idm45939748492560"></a>TeleGPS Owner’s Manual</h1></div><div><h2 class="subtitle">An Owner's Manual for the TeleGPS recording GPS tracker</h2></div><div><h3 class="corpauthor">
3 <span class="inlinemediaobject"><img src="telegps-oneline.svg" width="270" /></span>
4 </h3></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2015 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm45939748441456"></a><p>
5 This document is released under the terms of the
6 <a class="ulink" href="http://creativecommons.org/licenses/by-sa/3.0/" target="_top">
7 Creative Commons ShareAlike 3.0
10 </p></div></div><div><a href="telegps-revhistory.html">Revision History</a></div></div><hr /></div><div class="dedication"><div class="titlepage"><div><div><h1 class="title"><a id="_acknowledgments"></a>Acknowledgments</h1></div></div></div><p>Thanks to Anthony (AJ) Towns for major contributions including
11 the TeleGPS graphing and site map code and associated documentation.
12 Free software means that our customers and friends can become our
13 collaborators, and we certainly appreciate this level of
14 contribution!</p><p>Have fun using these products, and we hope to meet all of you
15 out on the rocket flight line somewhere.</p><div class="blockquote"><blockquote class="blockquote"><div class="literallayout"><p>Bdale Garbee, KB0G<br />
16 NAR #87103, TRA #12201</p></div></blockquote></div><div class="blockquote"><blockquote class="blockquote"><div class="literallayout"><p>Keith Packard, KD7SQG<br />
17 NAR #88757, TRA #12200</p></div></blockquote></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#_telegps_quick_start_guide">1. TeleGPS Quick Start Guide</a></span></dt><dt><span class="chapter"><a href="#_using_telegps_hardware">2. Using TeleGPS Hardware</a></span></dt><dd><dl><dt><span class="section"><a href="#_hooking_up_lithium_polymer_batteries">2.1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#_on_board_data_recording">2.2. On-board Data Recording</a></span></dt><dt><span class="section"><a href="#_installation">2.3. Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#_telegps_application">3. TeleGPS Application</a></span></dt><dd><dl><dt><span class="section"><a href="#_telemetry_monitoring">3.1. Telemetry Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#_map">3.1.1. Map</a></span></dt><dt><span class="section"><a href="#_location">3.1.2. Location</a></span></dt><dt><span class="section"><a href="#_status">3.1.3. Status</a></span></dt><dt><span class="section"><a href="#_table">3.1.4. Table</a></span></dt></dl></dd><dt><span class="section"><a href="#_telegps_menus">3.2. TeleGPS Menus</a></span></dt><dd><dl><dt><span class="section"><a href="#_new_window">3.2.1. New Window</a></span></dt></dl></dd><dt><span class="section"><a href="#_graph_data">3.3. Graph Data</a></span></dt><dd><dl><dt><span class="section"><a href="#_data_graph">3.3.1. Data Graph</a></span></dt><dt><span class="section"><a href="#_graph_configuration">3.3.2. Graph Configuration</a></span></dt><dt><span class="section"><a href="#_statistics">3.3.3. Statistics</a></span></dt><dt><span class="section"><a href="#_map_2">3.3.4. Map</a></span></dt></dl></dd><dt><span class="section"><a href="#_export_data">3.4. Export Data</a></span></dt><dd><dl><dt><span class="section"><a href="#_comma_separated_value_format">3.4.1. Comma Separated Value Format</a></span></dt><dt><span class="section"><a href="#_keyhole_markup_language_for_google_earth">3.4.2. Keyhole Markup Language (for Google Earth)</a></span></dt></dl></dd><dt><span class="section"><a href="#_load_maps">3.5. Load Maps</a></span></dt><dt><span class="section"><a href="#_preferences">3.6. Preferences</a></span></dt><dd><dl><dt><span class="section"><a href="#_voice_settings">3.6.1. Voice Settings</a></span></dt><dt><span class="section"><a href="#_log_directory">3.6.2. Log Directory</a></span></dt><dt><span class="section"><a href="#_callsign">3.6.3. Callsign</a></span></dt><dt><span class="section"><a href="#_imperial_units">3.6.4. Imperial Units</a></span></dt><dt><span class="section"><a href="#_serial_debug">3.6.5. Serial Debug</a></span></dt><dt><span class="section"><a href="#_font_size">3.6.6. Font size</a></span></dt><dt><span class="section"><a href="#_look_amp_feel">3.6.7. Look & feel</a></span></dt><dt><span class="section"><a href="#_menu_position">3.6.8. Menu position</a></span></dt><dt><span class="section"><a href="#_map_cache_size">3.6.9. Map Cache Size</a></span></dt><dt><span class="section"><a href="#_manage_frequencies">3.6.10. Manage Frequencies</a></span></dt></dl></dd><dt><span class="section"><a href="#_close">3.7. Close</a></span></dt><dt><span class="section"><a href="#_exit">3.8. Exit</a></span></dt><dt><span class="section"><a href="#_connect_device">3.9. Connect Device</a></span></dt><dt><span class="section"><a href="#_disconnect">3.10. Disconnect</a></span></dt><dt><span class="section"><a href="#_scan_channels">3.11. Scan Channels</a></span></dt><dt><span class="section"><a href="#_download_data">3.12. Download Data</a></span></dt><dt><span class="section"><a href="#_configure_device">3.13. Configure Device</a></span></dt><dd><dl><dt><span class="section"><a href="#_frequency">3.13.1. Frequency</a></span></dt><dt><span class="section"><a href="#_rf_calibration">3.13.2. RF Calibration</a></span></dt><dt><span class="section"><a href="#_telemetry_rdf_aprs_enable">3.13.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#_telemetry_baud_rate">3.13.4. Telemetry baud rate</a></span></dt><dt><span class="section"><a href="#_aprs_interval">3.13.5. APRS Interval</a></span></dt><dt><span class="section"><a href="#_aprs_ssid">3.13.6. APRS SSID</a></span></dt><dt><span class="section"><a href="#_aprs_format">3.13.7. APRS Format</a></span></dt><dt><span class="section"><a href="#_callsign_2">3.13.8. Callsign</a></span></dt><dt><span class="section"><a href="#_logging_trigger_motion">3.13.9. Logging Trigger Motion</a></span></dt><dt><span class="section"><a href="#_position_reporting_interval">3.13.10. Position Reporting Interval</a></span></dt></dl></dd><dt><span class="section"><a href="#_flash_device">3.14. Flash Device</a></span></dt></dl></dd><dt><span class="appendix"><a href="#_telegps_system_operation">A. TeleGPS System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#_gfsk_telemetry">A.1. GFSK Telemetry</a></span></dt><dt><span class="section"><a href="#_aprs">A.2. APRS</a></span></dt><dt><span class="section"><a href="#_configurable_parameters">A.3. Configurable Parameters</a></span></dt></dl></dd><dt><span class="appendix"><a href="#_handling_precautions">B. Handling Precautions</a></span></dt><dt><span class="appendix"><a href="#_technical_information">C. Technical Information</a></span></dt><dd><dl><dt><span class="section"><a href="#_gps_receiver">C.1. GPS Receiver</a></span></dt><dt><span class="section"><a href="#_micro_controller">C.2. Micro-controller</a></span></dt><dt><span class="section"><a href="#_lithium_polymer_battery">C.3. Lithium Polymer Battery</a></span></dt><dt><span class="section"><a href="#_mechanical_considerations">C.4. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#_on_board_data_storage">C.5. On-board data storage</a></span></dt></dl></dd><dt><span class="appendix"><a href="#_updating_device_firmware">D. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#_updating_telegps_firmware">D.1. Updating TeleGPS Firmware</a></span></dt></dl></dd><dt><span class="appendix"><a href="#_release_notes">E. Release Notes</a></span></dt><dd><dl><dt><span class="section"><a href="#_release_notes_for_version_1_6_3">E.1. Release Notes for Version 1.6.3</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos">E.1.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications">E.1.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_altosdroid">E.1.3. AltosDroid</a></span></dt><dt><span class="section"><a href="#_documentation">E.1.4. Documentation</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_2">E.2. Release Notes for Version 1.6.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_2">E.2.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_2">E.2.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_documentation_2">E.2.3. Documentation</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6_1">E.3. Release Notes for Version 1.6.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_3">E.3.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_3">E.3.2. AltosUI and TeleGPS Applications</a></span></dt><dt><span class="section"><a href="#_altosdroid_2">E.3.3. AltosDroid</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_6">E.4. Release Notes for Version 1.6</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_4">E.4.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_4">E.4.2. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_5">E.5. Release Notes for Version 1.5</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_5">E.5.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_and_telegps_applications_5">E.5.2. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_4_2">E.6. Release Notes for Version 1.4.2</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_and_telegps_applications_6">E.6.1. AltosUI and TeleGPS Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_4_1">E.7. Release Notes for Version 1.4.1</a></span></dt><dd><dl><dt><span class="section"><a href="#_altosui_and_telegps_applications_7">E.7.1. AltosUI and TeleGPS Applications:</a></span></dt></dl></dd><dt><span class="section"><a href="#_release_notes_for_version_1_4">E.8. Release Notes for Version 1.4</a></span></dt><dd><dl><dt><span class="section"><a href="#_altos_6">E.8.1. AltOS</a></span></dt><dt><span class="section"><a href="#_altosui_application">E.8.2. AltosUI Application</a></span></dt><dt><span class="section"><a href="#_telegps_application_2">E.8.3. TeleGPS Application</a></span></dt><dt><span class="section"><a href="#_documentation_3">E.8.4. Documentation</a></span></dt></dl></dd></dl></dd></dl></div><div class="list-of-figures"><p><strong>List of Figures</strong></p><dl><dt>3.1. <a href="#idm45939748402432">TeleGPS Map View</a></dt><dt>3.2. <a href="#idm45939748530720">TeleGPS Location View</a></dt><dt>3.3. <a href="#idm45939742929312">TeleGPS Status View</a></dt><dt>3.4. <a href="#idm45939742924880">TeleGPS Information Table</a></dt><dt>3.5. <a href="#idm45939742908480">TeleGPS Graph</a></dt><dt>3.6. <a href="#idm45939742904576">TeleGPS Graph Configuration</a></dt><dt>3.7. <a href="#idm45939742900064">TeleGPS Statistics</a></dt><dt>3.8. <a href="#idm45939742895776">TeleGPS Map</a></dt><dt>3.9. <a href="#idm45939742883936">Load Maps Window</a></dt><dt>3.10. <a href="#idm45939742867488">TeleGPS Preferences Window</a></dt><dt>3.11. <a href="#idm45939742836512">Device Selection Dialog</a></dt><dt>3.12. <a href="#idm45939742831088">Radio Scanning Dialog</a></dt><dt>3.13. <a href="#idm45939742821280">TeleGPS Configuration Dialog</a></dt></dl></div><div class="list-of-tables"><p><strong>List of Tables</strong></p><dl><dt>A.1. <a href="#idm45939742780128">Altus Metrum APRS Comments</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_telegps_quick_start_guide"></a>Chapter 1. TeleGPS Quick Start Guide</h1></div></div></div><p>TeleGPS is designed to be easy to use. Requiring no external
18 components, flying takes just a few steps.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
19 First, download and install the software from
20 <a class="ulink" href="http://altusmetrum.org/AltOS" target="_top">http://altusmetrum.org/AltOS</a>. This will make sure that
21 you have the right device drivers installed.
22 </li><li class="listitem">
23 Next, plug in the battery and USB cable and connect TeleGPS to
24 your computer. This will charge the battery and allow you to
26 </li><li class="listitem">
27 Start the TeleGPS application and set the callsign and frequency
28 on your TeleGPS device; refer to <a class="xref" href="#_configure_device" title="3.13. Configure Device">Section 3.13, “Configure Device”</a> for instructions.
29 </li><li class="listitem">
30 Unplug TeleGPS when the battery charger light goes green. This
31 will enable the radio and logging portions of the TeleGPS
33 </li><li class="listitem">
34 Connect TeleDongle to your computer and start TeleGPS or start
35 AltosDroid on your android device and connect to TeleBT. Set the
36 frequency to match the TeleGPS and you should be receiving telemetry.
37 </li></ol></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_using_telegps_hardware"></a>Chapter 2. Using TeleGPS Hardware</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_hooking_up_lithium_polymer_batteries"></a>2.1. Hooking Up Lithium Polymer Batteries</h2></div></div></div><p>TeleGPS has a two pin JST PH series connector to connect up
38 a single-cell Lithium Polymer cell (3.7V nominal). You can
39 purchase matching batteries from the Altus Metrum store, or
40 other vendors, or you can make your own. Pin 1 of the
41 connector is positive, pin 2 is negative. Spark Fun sells a
42 cable with the connector attached, which they call a
43 <a class="ulink" href="https://www.sparkfun.com/products/9914" target="_top">JST Jumper 2 Wire Assembly</a></p><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>Many RC vendors also sell lithium polymer batteries with
44 this same connector. All that we have found use the opposite
45 polarity, and if you use them that way, you will damage or
46 destroy TeleGPS.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_on_board_data_recording"></a>2.2. On-board Data Recording</h2></div></div></div><p>TeleGPS logs GPS data at a user-configurable
47 rate. Data are logged to a 2MB on-board flash memory
48 part, which can be partitioned into several
49 equal-sized blocks, one for each flight. 64kB of this
50 storage are reserved to hold configuration data,
51 leaving 1984kB for flight data.</p><p>The on-board flash is partitioned into separate flight
52 logs, each of a fixed maximum size. Increase the
53 maximum size of each log and you reduce the number of
54 flights that can be stored. Decrease the size and you
55 can store more flights.</p><p>To compute the amount of space needed for a single
56 log, you can divide the expected time (in seconds) by
57 the sample period (by default, 1 second per sample)
58 and then multiply the result by 32 bytes per
59 sample. For instance, a sample period of 1 second and
60 a flight lasting one hour will take 32 * 3600 = 115200
61 bytes. TeleGPS does try to reduce log space used by
62 not recording position information when it isn’t
63 moving, so actual space consumed may be less than
64 this.</p><p>The default size allows for four flights of 496kB
65 each, which provides over four hours of logging at 1
66 sample per second.</p><p>TeleGPS will not overwrite existing flight data, so be
67 sure to download flight data and erase it from the
68 onboard flash before it fills up. TeleGPS will still
69 report telemetry even if memory is full, so the only
70 thing you will lose is the on-board data log.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_installation"></a>2.3. Installation</h2></div></div></div><p>The battery connectors are a standard 2-pin JST
71 connector and match batteries sold by Spark Fun. These
72 batteries are single-cell Lithium Polymer batteries
73 that nominally provide 3.7 volts. Other vendors sell
74 similar batteries for RC aircraft using mating
75 connectors, however the polarity for those is
76 generally reversed from the batteries used by Altus
77 Metrum products. In particular, the Tenergy batteries
78 supplied for use in Featherweight flight computers are
79 not compatible with Altus Metrum flight computers or
80 battery chargers.</p><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>Check polarity and voltage before connecting any
81 battery not purchased from Altus Metrum or Spark
82 Fun.</p></div><p>TeleGPS uses an integrate GPS patch antenna and won’t
83 receive GPS signals if installed inside a metal or
84 carbon fiber compartment. Test GPS reception and
85 telemetry transmission with the system installed and
86 all other electronics powered up to verify signal
87 reception and make sure there isn’t any interference
88 from other systems.</p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a id="_telegps_application"></a>Chapter 3. TeleGPS Application</h1></div></div></div><p>The TeleGPS application provides a graphical user interface for
89 interacting with the Altus Metrum product family. TeleGPS can
90 monitor telemetry data, configure devices and many other
91 tasks. The primary interface window is for displaying data
92 received over the telemetry link. There are additional
93 tasks available from the main window menu bar.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_telemetry_monitoring"></a>3.1. Telemetry Monitoring</h2></div></div></div><p>This is the window brought up when you start the
94 application. If you have a TeleDongle device connected
95 to the computer, it will automatically be selected for
96 telemetry monitoring</p><p>All telemetry data received are automatically recorded
97 in suitable log files. The name of the files includes
98 the current date and TeleGPS serial and flight
99 numbers.</p><p>The radio frequency being monitored by the TeleDongle
100 device is displayed at the top of the window. You can
101 configure the frequency by clicking on the frequency
102 box and selecting the desired frequency. The TeleGPS
103 application remembers the last frequency selected for
104 each TeleDongle and selects that automatically the
105 next time you use that device.</p><p>Below the TeleDongle frequency selector, the window
106 contains a few significant pieces of information about
107 the altimeter providing the telemetry data stream:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
108 The configured call-sign
109 </li><li class="listitem">
110 The device serial number
111 </li><li class="listitem">
112 The flight number. TeleGPS remembers how many times
114 </li><li class="listitem">
115 The Received Signal Strength Indicator value. This
116 lets you know how strong a signal TeleDongle is
117 receiving. The radio inside TeleDongle operates down
118 to about -100dBm; weaker signals may not be
119 receivable. The packet link uses error detection and
120 correction techniques which prevent incorrect data
122 </li><li class="listitem">
123 The age of the displayed data, in seconds since the
124 last successfully received telemetry packet. In
125 normal operation this will stay in the low single
126 digits. If the number starts counting up, then you
127 are no longer receiving data over the radio link
128 from the flight computer.
129 </li></ul></div><p>Finally, the largest portion of the window contains a set of
130 tabs, each of which contain some information about the TeleGPS
131 board. The final <span class="emphasis"><em>table</em></span> tab displays many of the raw telemetry
132 values in one place in a spreadsheet-like format.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_map"></a>3.1.1. Map</h3></div></div></div><p>The Map tab shows the TeleGPS track over time
133 on top of map data making it easy to locate
134 the device.</p><div class="figure"><a id="idm45939748402432"></a><p class="title"><strong>Figure 3.1. TeleGPS Map View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-map.png" width="495" alt="telegps-map.png" /></div></div></div><br class="figure-break" /><p>The map’s default scale is approximately 3m
135 (10ft) per pixel. The map can be dragged using
136 the left mouse button. The map will attempt to
137 keep the rocket roughly centered while data is
138 being received.</p><p>You can adjust the style of map and the zoom
139 level with buttons on the right side of the
140 map window. You can draw a line on the map by
141 moving the mouse over the map with a button
142 other than the left one pressed, or by
143 pressing the left button while also holding
144 down the shift key. The length of the line in
145 real-world units will be shown at the start of
146 the line.</p><p>Images are fetched automatically via the
147 Google Maps Static API, and cached on disk for
148 reuse. If map images cannot be downloaded, the
149 rocket’s path will be traced on a dark gray
150 background instead.</p><p>You can pre-load images for your favorite
151 launch sites before you leave home; check out
152 <a class="xref" href="#_load_maps" title="3.5. Load Maps">Section 3.5, “Load Maps”</a>.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_location"></a>3.1.2. Location</h3></div></div></div><p>The Location tab shows the raw GPS data
153 received from TeleGPS.</p><div class="figure"><a id="idm45939748530720"></a><p class="title"><strong>Figure 3.2. TeleGPS Location View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-location.png" width="495" alt="telegps-location.png" /></div></div></div><br class="figure-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_status"></a>3.1.3. Status</h3></div></div></div><p>The Status tab shows data relative to the
154 location of TeleGPS when the application first
155 received telemetry from it.</p><div class="figure"><a id="idm45939742929312"></a><p class="title"><strong>Figure 3.3. TeleGPS Status View</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-status.png" width="495" alt="telegps-status.png" /></div></div></div><br class="figure-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_table"></a>3.1.4. Table</h3></div></div></div><p>The Table tab shows detailed information about
156 the GPS receiver</p><div class="figure"><a id="idm45939742924880"></a><p class="title"><strong>Figure 3.4. TeleGPS Information Table</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-table.png" width="495" alt="telegps-table.png" /></div></div></div><br class="figure-break" /></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_telegps_menus"></a>3.2. TeleGPS Menus</h2></div></div></div><p>TeleGPS has three or four menus at the top of
157 the window:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
160 New Window, Graph Data, Export Data, Load Maps,
161 Preferences, Close and Exit
162 </dd><dt><span class="term">
165 Connect Device, Disconnect and Scan Channels
166 </dd><dt><span class="term">
169 Download Data, Configure Device and Flash Device
170 </dd><dt><span class="term">
173 This shows the current monitoring frequency with a
174 drop-down menu listing other configured
175 frequencies. You can change the set of frequencies
176 shown here from the Preferences dialog. This menu is
177 only shown when the TeleGPS application is connected
178 to a TeleDongle or TeleBT device.
179 </dd></dl></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_new_window"></a>3.2.1. New Window</h3></div></div></div><p>This creates another telemetry monitoring window, in case
180 you have multiple TeleDongle devices connected to the
181 computer.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_graph_data"></a>3.3. Graph Data</h2></div></div></div><p>The Graph tab shows a plot of the the GPS data
182 collected. The X axis is time in seconds; there are a
183 variety of Y axes available for different kinds of
184 data. This window also allows you to see some
185 statistics computed from the data, and an overall map
186 of the entire data record.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_data_graph"></a>3.3.1. Data Graph</h3></div></div></div><div class="figure"><a id="idm45939742908480"></a><p class="title"><strong>Figure 3.5. TeleGPS Graph</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-graph-graph.png" width="495" alt="telegps-graph-graph.png" /></div></div></div><br class="figure-break" /></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_graph_configuration"></a>3.3.2. Graph Configuration</h3></div></div></div><div class="figure"><a id="idm45939742904576"></a><p class="title"><strong>Figure 3.6. TeleGPS Graph Configuration</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-graph-configure.png" width="495" alt="telegps-graph-configure.png" /></div></div></div><br class="figure-break" /><p>This selects which graph elements to show, and, at the
187 bottom, lets you switch between metric and imperial
188 units</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_statistics"></a>3.3.3. Statistics</h3></div></div></div><div class="figure"><a id="idm45939742900064"></a><p class="title"><strong>Figure 3.7. TeleGPS Statistics</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-graph-stats.png" width="495" alt="telegps-graph-stats.png" /></div></div></div><br class="figure-break" /><p>Shows overall data computed from the flight.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_map_2"></a>3.3.4. Map</h3></div></div></div><div class="figure"><a id="idm45939742895776"></a><p class="title"><strong>Figure 3.8. TeleGPS Map</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-graph-map.png" width="540" alt="telegps-graph-map.png" /></div></div></div><br class="figure-break" /><p>Shows a map of the area overlaid with the GPS track. As with
189 the telemetry monitoring window, you can select the style
190 of map and zoom level using buttons along the side;
191 you can scroll the map by dragging within the map pressing
192 the left button and you can draw a line to measure
193 distances using either the left button with the shift key,
194 or any other button.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_export_data"></a>3.4. Export Data</h2></div></div></div><p>This tool takes the raw data files and makes them
195 available for external analysis. When you select this
196 button, you are prompted to select a data file, which
197 can be either a .eeprom or .telem. The .eeprom files
198 contain higher resolution and more continuous data,
199 while .telem files contain receiver signal strength
200 information. Next, a second dialog appears which is
201 used to select where to write the resulting file. It
202 has a selector to choose between CSV and KML file
203 formats.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_comma_separated_value_format"></a>3.4.1. Comma Separated Value Format</h3></div></div></div><p>This is a text file containing the data in a
204 form suitable for import into a spreadsheet or
205 other external data analysis tool. The first
206 few lines of the file contain the version and
207 configuration information from TeleGPS, then
208 there is a single header line which labels all
209 of the fields. All of these lines start with a
210 <span class="emphasis"><em>#</em></span> character which many tools can be
211 configured to skip over.</p><p>The remaining lines of the file contain the
212 data, with each field separated by a comma and
213 at least one space. All of the sensor values
214 are converted to standard units, with the
215 barometric data reported in both pressure,
216 altitude and height above pad units.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_keyhole_markup_language_for_google_earth"></a>3.4.2. Keyhole Markup Language (for Google Earth)</h3></div></div></div><p>This is the format used by Google Earth to provide an overlay
217 within that application. With this, you can use Google Earth to
218 see the whole path in 3D.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_load_maps"></a>3.5. Load Maps</h2></div></div></div><div class="figure"><a id="idm45939742883936"></a><p class="title"><strong>Figure 3.9. Load Maps Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="load-maps.png" width="468" alt="load-maps.png" /></div></div></div><br class="figure-break" /><p>Before heading out to a new launch site, you can use
219 this to load satellite images in case you don’t have
220 internet connectivity at the site.</p><p>There’s a drop-down menu of launch sites we know
221 about; if your favorites aren’t there, please let us
222 know the lat/lon and name of the site. The contents of
223 this list are actually downloaded from our server at
224 run-time, so as new sites are sent in, they’ll get
225 automatically added to this list. If the launch site
226 isn’t in the list, you can manually enter the lat/lon
227 values</p><p>There are four different kinds of maps you can view;
228 you can select which to download by selecting as many
229 as you like from the available types:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
232 A combination of satellite imagery and road data. This
234 </dd><dt><span class="term">
237 Just the satellite imagery without any annotation.
238 </dd><dt><span class="term">
241 Roads, political boundaries and a few geographic
243 </dd><dt><span class="term">
246 Contour intervals and shading that show hills and
248 </dd></dl></div><p>You can specify the range of zoom levels to download;
249 smaller numbers show more area with less
250 resolution. The default level, 0, shows about
251 3m/pixel. One zoom level change doubles or halves that
252 number. Larger zoom levels show more detail, smaller
253 zoom levels less.</p><p>The Map Radius value sets how large an area around the
254 center point to download. Select a value large enough
255 to cover any plausible flight from that site. Be aware
256 that loading a large area with a high maximum zoom
257 level can attempt to download a lot of data. Loading
258 hybrid maps with a 10km radius at a minimum zoom of -2
259 and a maximum zoom of 2 consumes about 120MB of
260 space. Terrain and road maps consume about 1/10 as
261 much space as satellite or hybrid maps.</p><p>Clicking the <span class="emphasis"><em>Load Map</em></span> button will fetch images from
262 Google Maps; note that Google limits how many images
263 you can fetch at once, so if you load more than one
264 launch site, you may get some gray areas in the map
265 which indicate that Google is tired of sending data to
266 you. Try again later.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_preferences"></a>3.6. Preferences</h2></div></div></div><div class="figure"><a id="idm45939742867488"></a><p class="title"><strong>Figure 3.10. TeleGPS Preferences Window</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-preferences.png" width="216" alt="telegps-preferences.png" /></div></div></div><br class="figure-break" /><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_voice_settings"></a>3.6.1. Voice Settings</h3></div></div></div><p>TeleGPS provides voice announcements during
267 flight so that you can keep your eyes on the
268 sky and still get information about the
269 current flight status. However, sometimes you
270 don’t want to hear them.</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
273 Turns all voice announcements on and off
274 </dd><dt><span class="term">
277 Plays a short message allowing you to verify
278 that the audio system is working and the volume settings
280 </dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_log_directory"></a>3.6.2. Log Directory</h3></div></div></div><p>TeleGPS logs all telemetry data and saves all
281 flash data to this directory. This
282 directory is also used as the staring point
283 when selecting data files for display or
284 export.</p><p>Click on the directory name to bring up a
285 directory choosing dialog, select a new
286 directory and click <span class="emphasis"><em>Select Directory</em></span> to
287 change where TeleGPS reads and writes data
288 files.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_callsign"></a>3.6.3. Callsign</h3></div></div></div><p>This value is transmitted in each command
289 packet sent from TeleDongle and received from
290 an altimeter. It is not used in telemetry
291 mode, as the callsign configured in the
292 altimeter board is included in all telemetry
293 packets. Configure this with the TeleGPS
294 operators call sign as needed to comply with
295 your local radio regulations.</p><p>Note that to successfully command a flight
296 computer over the radio (to configure the
297 altimeter, monitor idle, or fire pyro
298 charges), the callsign configured here must
299 exactly match the callsign configured in the
300 flight computer. This matching is case
301 sensitive.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_imperial_units"></a>3.6.4. Imperial Units</h3></div></div></div><p>This switches between metric units (meters)
302 and imperial units (feet and miles). This
303 affects the display of values use during
304 flight monitoring, configuration, data
305 graphing and all of the voice
306 announcements. It does not change the units
307 used when exporting to CSV files, those are
308 always produced in metric units.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_serial_debug"></a>3.6.5. Serial Debug</h3></div></div></div><p>This causes all communication with a connected
309 device to be dumped to the console from which
310 TeleGPS was started. If you’ve started it from
311 an icon or menu entry, the output will simply
312 be discarded. This mode can be useful to debug
313 various serial communication issues.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_font_size"></a>3.6.6. Font size</h3></div></div></div><p>Selects the set of fonts used in the flight
314 monitor window. Choose between the small,
315 medium and large sets.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_look_amp_feel"></a>3.6.7. Look & feel</h3></div></div></div><p>Switches between the available Java user
316 interface appearances. The default selection
317 is supposed to match the native window system
318 appearance for the target platform.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_menu_position"></a>3.6.8. Menu position</h3></div></div></div><p>Selects the initial position for the main
319 TeleGPS window that includes all of the
320 command buttons.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_map_cache_size"></a>3.6.9. Map Cache Size</h3></div></div></div><p>Sets the number of map <span class="emphasis"><em>tiles</em></span> kept in memory
321 while the application is running. More tiles
322 consume more memory, but will make panning
323 around the map faster.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_manage_frequencies"></a>3.6.10. Manage Frequencies</h3></div></div></div><p>This brings up a dialog where you can
324 configure the set of frequencies shown in the
325 various frequency menus. You can add as many
326 as you like, or even reconfigure the default
327 set. Changing this list does not affect the
328 frequency settings of any devices, it only
329 changes the set of frequencies shown in the
330 menus.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_close"></a>3.7. Close</h2></div></div></div><p>This closes the current window, leaving any other windows
331 open and the application running.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_exit"></a>3.8. Exit</h2></div></div></div><p>This closes all TeleGPS windows and terminates the
332 application.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_connect_device"></a>3.9. Connect Device</h2></div></div></div><p>Selecting this item brings up a dialog box listing all
333 of the connected TeleDongle devices. When you choose
334 one of these, AltosUI will display telemetry data as
335 received by the selected TeleDongle device.</p><div class="figure"><a id="idm45939742836512"></a><p class="title"><strong>Figure 3.11. Device Selection Dialog</strong></p><div class="figure-contents"><div class="mediaobject"><img src="device-selection.png" width="279" alt="device-selection.png" /></div></div></div><br class="figure-break" /></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_disconnect"></a>3.10. Disconnect</h2></div></div></div><p>Disconnects the currently connected TeleDongle or
336 TeleBT</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_scan_channels"></a>3.11. Scan Channels</h2></div></div></div><div class="figure"><a id="idm45939742831088"></a><p class="title"><strong>Figure 3.12. Radio Scanning Dialog</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-scan.png" width="279" alt="telegps-scan.png" /></div></div></div><br class="figure-break" /><p>Scans the configured set of frequencies looking for
337 telemetry signals. A list of all of the discovered
338 signals is show; selecting one of those and clicking
339 on <span class="emphasis"><em>Monitor</em></span> will select that frequency in the
340 associated TeleGPS application window.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_download_data"></a>3.12. Download Data</h2></div></div></div><p>TeleGPS records data to its internal flash memory.
341 On-board data is recorded at the same rate as
342 telemetry but is not subject to radio drop-outs. As
343 such, it generally provides a more complete and
344 precise record. The <span class="emphasis"><em>Download Data</em></span> menu entry allows
345 you to read the flash memory and write it to disk.</p><p>Select the <span class="emphasis"><em>Download Data</em></span> menu entry to bring up a
346 list of connected TeleGPS devices. After the device
347 has been selected, a dialog showing the data stored in
348 the device will be shown allowing you to select which
349 entries to download and which to delete. You must
350 erase flights in order for the space they consume to
351 be reused by another track. This prevents accidentally
352 losing data if you neglect to download data before
353 starting TeleGPS again. Note that if there is no more
354 space available in the device, then no data will be
355 recorded.</p><p>The file name for each data log is computed
356 automatically from the recorded date, altimeter serial
357 number and flight number information.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_configure_device"></a>3.13. Configure Device</h2></div></div></div><div class="figure"><a id="idm45939742821280"></a><p class="title"><strong>Figure 3.13. TeleGPS Configuration Dialog</strong></p><div class="figure-contents"><div class="mediaobject"><img src="telegps-configure.png" width="324" alt="telegps-configure.png" /></div></div></div><br class="figure-break" /><p>Select this button and then select any connected TeleGPS
358 device from the list provided.</p><p>The first few lines of the dialog provide information
359 about the connected device, including the product
360 name, software version and hardware serial
361 number. Below that are the individual configuration
362 entries.</p><p>At the bottom of the dialog, there are four buttons:</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">
365 This writes any changes to the configuration parameter
366 block in flash memory. If you don’t press this button,
367 any changes you make will be lost.
368 </dd><dt><span class="term">
371 This resets the dialog to the most recently saved
372 values, erasing any changes you have made.
373 </dd><dt><span class="term">
376 This reboots the device. Use this to switch from idle
377 to pad mode by rebooting once the rocket is oriented
378 for flight, or to confirm changes you think you saved
380 </dd><dt><span class="term">
383 This closes the dialog. Any unsaved changes will be
385 </dd></dl></div><p>The rest of the dialog contains the parameters to be configured.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_frequency"></a>3.13.1. Frequency</h3></div></div></div><p>This configures which of the frequencies to use for
386 both telemetry and packet command mode. Note that if
387 you set this value via packet command mode, the
388 TeleDongle frequency will also be automatically
389 reconfigured to match so that communication will
390 continue afterwards.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_rf_calibration"></a>3.13.2. RF Calibration</h3></div></div></div><p>The radios in every Altus Metrum device are calibrated
391 at the factory to ensure that they transmit and
392 receive on the specified frequency. If you need to
393 you can adjust the calibration by changing this value.
394 Do not do this without understanding what the value
395 means, read the appendix on calibration and/or the
396 source code for more information. To change a
397 TeleDongle’s calibration, you must reprogram the unit
398 completely.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_telemetry_rdf_aprs_enable"></a>3.13.3. Telemetry/RDF/APRS Enable</h3></div></div></div><p>Enables the radio for transmission during
399 flight. When disabled, the radio will not
400 transmit anything during flight at all.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_telemetry_baud_rate"></a>3.13.4. Telemetry baud rate</h3></div></div></div><p>This sets the modulation bit rate for data
401 transmission for both telemetry and packet
402 link mode. Lower bit rates will increase range
403 while reducing the amount of data that can be
404 sent and increasing battery consumption. All
405 telemetry is done using a rate 1/2 constraint
406 4 convolution code, so the actual data
407 transmission rate is 1/2 of the modulation bit
408 rate specified here.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_aprs_interval"></a>3.13.5. APRS Interval</h3></div></div></div><p>How often to transmit GPS information via APRS
409 (in seconds). When set to zero, APRS
410 transmission is disabled.
411 Note that a single APRS packet
412 takes nearly a full second to transmit, so
413 enabling this option will prevent sending any
414 other telemetry during that time.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_aprs_ssid"></a>3.13.6. APRS SSID</h3></div></div></div><p>Which SSID to report in APRS packets. By
415 default, this is set to the last digit of the
416 serial number, but can be configured to any
417 value from 0 to 9.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_aprs_format"></a>3.13.7. APRS Format</h3></div></div></div><p>Whether to send APRS data in Compressed or
418 Uncompressed format. Compressed format is
419 smaller and more precise. Uncompressed
420 format is older, but may work better with your
421 device. The Kenwood TH-D72 only displays
422 altitude information with Uncompressed
423 format, while the Yaesu FT1D only displays
424 altitude with Compressed format. Test before
425 you fly to see which to use.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_callsign_2"></a>3.13.8. Callsign</h3></div></div></div><p>This sets the call sign included in each
426 telemetry packet. Set this as needed to
427 conform to your local radio regulations.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_logging_trigger_motion"></a>3.13.9. Logging Trigger Motion</h3></div></div></div><p>This sets the amount of motion that TeleGPS
428 needs to see before logging the new
429 position. Motions smaller than this are
430 skipped, which saves storage space.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_position_reporting_interval"></a>3.13.10. Position Reporting Interval</h3></div></div></div><p>The interval between TeleGPS position reports,
431 both over the air and in the log. Increase
432 this to reduce the frequency of radio
433 transmissions and the length of time available
434 in the log.</p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_flash_device"></a>3.14. Flash Device</h2></div></div></div><p>This reprograms TeleGPS devices with new
435 firmware. Please read the directions for flashing
436 devices in <a class="xref" href="#_updating_device_firmware" title="Appendix D. Updating Device Firmware">Appendix D, <em>Updating Device Firmware</em></a>.</p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_telegps_system_operation"></a>Appendix A. TeleGPS System Operation</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_gfsk_telemetry"></a>A.1. GFSK Telemetry</h2></div></div></div><p>TeleGPS’s native telemetry system doesn’t use a
437 <span class="emphasis"><em>normal packet radio</em></span> mode like APRS because it’s not
438 very efficient. The GFSK modulation we use is FSK
439 with the base-band pulses passed through a Gaussian
440 filter before they go into the modulator to limit the
441 transmitted bandwidth. When combined with forward
442 error correction and interleaving, this allows us to
443 have a very robust 19.2 kilobit data link with only
444 10-40 milliwatts of transmit power, a whip antenna in
445 the rocket, and a hand-held Yagi on the ground. We’ve
446 had flights to above 21k feet AGL with great
447 reception, and calculations suggest we should be good
448 to well over 40k feet AGL with a 5-element yagi on the
449 ground with our 10mW units and over 100k feet AGL with
450 the 40mW devices.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_aprs"></a>A.2. APRS</h2></div></div></div><p>TeleGPS can send APRS if desired, and the
451 interval between APRS packets can be configured. As each APRS
452 packet takes a full second to transmit, we recommend an
453 interval of at least 5 seconds to avoid consuming too much
454 battery power or radio channel bandwidth. You can configure
455 the APRS interval using TeleGPS; that process is described in
456 <a class="xref" href="#_configure_device" title="3.13. Configure Device">Section 3.13, “Configure Device”</a>.</p><p>AltOS supports both compressed and uncompressed APRS
457 position report data formats. The compressed format
458 provides for higher position precision and shorter
459 packets than the uncompressed APRS format. We’ve found
460 some older APRS receivers that do not handle the
461 compressed format. The Kenwood TH-72A requires the use
462 of uncompressed format to display altitude information
463 correctly. The Yaesu FT1D requires the use of
464 compressed format to display altitude information.</p><p>APRS packets include an SSID (Secondary Station Identifier)
465 field that allows one operator to have multiple
466 transmitters. AltOS allows you to set this to a single digit
467 from 0 to 9, allowing you to fly multiple transmitters at the
468 same time while keeping the identify of each one separate in
469 the receiver. By default, the SSID is set to the last digit of
470 the device serial number.</p><p>The APRS packet format includes a comment field that
471 can have arbitrary text in it. AltOS uses this to send
472 status information as shown in the following table.</p><div class="table"><a id="idm45939742780128"></a><p class="title"><strong>Table A.1. Altus Metrum APRS Comments</strong></p><div class="table-contents"><table class="table" summary="Altus Metrum APRS Comments" cellpadding="4px" style="border-collapse: collapse;border-top: 1px solid #78079a; border-bottom: 1px solid #78079a; border-left: 1px solid #78079a; border-right: 1px solid #78079a; "><colgroup><col class="col_1" /><col class="col_2" /><col class="col_3" /></colgroup><thead><tr><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Field </th><th style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top">Example </th><th style="border-bottom: 1px solid #78079a; " align="left" valign="top">Description</th></tr></thead><tbody><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>1</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>L</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>GPS Status U for unlocked, L for locked</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>2</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>6</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Number of Satellites in View</p></td></tr><tr><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>3</p></td><td style="border-right: 1px solid #78079a; border-bottom: 1px solid #78079a; " align="left" valign="top"><p>B4.0</p></td><td style="border-bottom: 1px solid #78079a; " align="left" valign="top"><p>Altimeter Battery Voltage</p></td></tr><tr><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>4</p></td><td style="border-right: 1px solid #78079a; " align="left" valign="top"><p>1286</p></td><td style="" align="left" valign="top"><p>Device Serial Number</p></td></tr></tbody></table></div></div><br class="table-break" /><p>Here’s an example of an APRS comment showing GPS lock with 6
473 satellites in view and a primary battery at 4.0V from device 1876.</p><pre class="literallayout">L6 B4.0 1876</pre><p>Make sure your primary battery is above 3.8V
474 and GPS is locked with at least 5 or 6 satellites in
475 view before flying. If GPS is switching between L and
476 U regularly, then it doesn’t have a good lock and you
477 should wait until it becomes stable.</p><p>If the GPS receiver loses lock, the APRS data
478 transmitted will contain the last position for which
479 GPS lock was available. You can tell that this has
480 happened by noticing that the GPS status character
481 switches from <span class="emphasis"><em>L</em></span> to <span class="emphasis"><em>U</em></span>. Before GPS has locked, APRS
482 will transmit zero for latitude, longitude and
483 altitude.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_configurable_parameters"></a>A.3. Configurable Parameters</h2></div></div></div><p>Configuring TeleGPS is very simple; the few configurable
484 parameters can all be set using the TeleGPS application over
485 USB. Check out <a class="xref" href="#_configure_device" title="3.13. Configure Device">Section 3.13, “Configure Device”</a>.</p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_handling_precautions"></a>Appendix B. Handling Precautions</h1></div></div></div><p>All Altus Metrum products are sophisticated electronic devices.
486 When handled gently and properly installed in an air-frame, they
487 will deliver impressive results. However, as with all electronic
488 devices, there are some precautions you must take.</p><div class="warning" style="margin-left: 0; margin-right: 10%;"><h3 class="title">Warning</h3><p>The Lithium Polymer rechargeable batteries have an
489 extraordinary power density. This is great because we can fly with
490 much less battery mass than if we used alkaline batteries or previous
491 generation rechargeable batteries… but if they are punctured
492 or their leads are allowed to short, they can and will release their
494 Thus we recommend that you take some care when handling our batteries
495 and consider giving them some extra protection in your air-frame. We
496 often wrap them in suitable scraps of closed-cell packing foam before
497 strapping them down, for example.</p></div><p>The barometric sensors used on all of our flight computers are
498 sensitive to sunlight. In normal mounting situations, the baro sensor
499 and all of the other surface mount components
500 are “down” towards whatever the underlying mounting surface is, so
501 this is not normally a problem. Please consider this when designing an
502 installation in an air-frame with a see-through plastic payload bay. It
503 is particularly important to
504 consider this with TeleMini v1.0, both because the baro sensor is on the
505 “top” of the board, and because many model rockets with payload bays
506 use clear plastic for the payload bay! Replacing these with an opaque
507 cardboard tube, painting them, or wrapping them with a layer of masking
508 tape are all reasonable approaches to keep the sensor out of direct
509 sunlight.</p><p>The barometric sensor sampling port must be able to “breathe”,
510 both by not being covered by foam or tape or other materials that might
511 directly block the hole on the top of the sensor, and also by having a
512 suitable static vent to outside air.</p><p>As with all other rocketry electronics, Altus Metrum altimeters must
513 be protected from exposure to corrosive motor exhaust and ejection
514 charge gasses.</p></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_technical_information"></a>Appendix C. Technical Information</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_gps_receiver"></a>C.1. GPS Receiver</h2></div></div></div><p>TeleGPS uses the u-Blox Max-7Q GPS receiver.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_micro_controller"></a>C.2. Micro-controller</h2></div></div></div><p>TeleGPS uses an NXP LPC11U14 micro-controller. This
515 tiny CPU contains 32kB of flash for the application
516 and 4kB of RAM for temporary data storage.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_lithium_polymer_battery"></a>C.3. Lithium Polymer Battery</h2></div></div></div><p>Shipping restrictions may prevent us from including a
517 battery battery with TeleGPS.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_mechanical_considerations"></a>C.4. Mechanical Considerations</h2></div></div></div><p>TeleGPS is designed to be rugged enough for typical
518 rocketry applications. The 4 mounting holes on the
519 board are sized for use with 4-40 or M3 screws.</p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_on_board_data_storage"></a>C.5. On-board data storage</h2></div></div></div><p>TeleGPS has 2MB of non-volatile storage, separate from
520 the code storage memory. The TeleGPS firmware uses
521 this to log information during flight.</p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_updating_device_firmware"></a>Appendix D. Updating Device Firmware</h1></div></div></div><p>TeleGPS is programmed directly over its USB connectors.</p><p>You may wish to begin by ensuring you have current firmware images.
522 These are distributed as part of the TeleGPS software bundle that
523 also includes the TeleGPS ground station program. Newer ground
524 station versions typically work fine with older firmware versions,
525 so you don’t need to update your devices just to try out new
526 software features. You can always download the most recent
527 version from <a class="ulink" href="http://www.altusmetrum.org/AltOS/" target="_top">http://www.altusmetrum.org/AltOS/</a></p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_updating_telegps_firmware"></a>D.1. Updating TeleGPS Firmware</h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
528 Attach a battery and power switch to the target
529 device. Power up the device.
530 </li><li class="listitem">
531 Using a Micro USB cable, connect the target device to
532 your computer’s USB socket.
533 </li><li class="listitem">
534 Run TeleGPS, and select <span class="emphasis"><em>Flash Device</em></span> from the
536 </li><li class="listitem">
537 Select the target device in the Device Selection
539 </li><li class="listitem">
540 Select the image you want to flash to the device,
541 which should have a name in the form
542 <product>-v<product-version>-<software-version>.ihx,
543 such as TeleGPS-v1.0-1.4.0.ihx.
544 </li><li class="listitem">
545 Make sure the configuration parameters are reasonable
546 looking. If the serial number and/or RF configuration
547 values aren’t right, you’ll need to change them.
548 </li><li class="listitem">
549 Hit the <span class="emphasis"><em>OK</em></span> button and the software should proceed
550 to flash the device with new firmware, showing a
552 </li><li class="listitem">
553 Verify that the device is working by using the
554 'Configure Device item to check over the
556 </li></ol></div></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a id="_release_notes"></a>Appendix E. Release Notes</h1></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6_3"></a>E.1. Release Notes for Version 1.6.3</h2></div></div></div><p>Version 1.6.3 adds idle mode to AltosDroid and has bug fixes
557 for our host software on desktops, laptops an android devices
558 along with BlueTooth support for Windows.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos"></a>E.1.1. AltOS</h3></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
559 Fix hardware flow control on TeleBT v3.0. RTS/CTS is
560 wired backwards on this board, switch from using the
561 hardware to driving these pins with software.
562 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications"></a>E.1.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
563 Add BlueTooth support for Windows operating system. This
564 supports connections to TeleBT over BlueTooth rather than
566 </li></ul></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
567 Change Java detection and install on Windows. Detection is
568 now done by looking for the <span class="emphasis"><em>javaw.exe</em></span> program, and
569 installation by opening a browser on the java.com web site.
570 </li><li class="listitem">
571 Delay polling while the Fire Igniters is visible to allow
572 for TeleMega to report back complete status over the radio.
573 </li><li class="listitem">
574 Disallow changing RF calibration numbers in the
575 configuration UI. There’s no good reason to change this from
576 the field, and recovering is really hard if you haven’t
577 written down the right number.
578 </li><li class="listitem">
579 Fix USB device discovery on Mac OS X El Capitan. This makes
580 the connected Altus Metrum USB devices appear again.
581 </li><li class="listitem">
582 Fix acceleration data presented in MonitorIdle mode for
583 TeleMetrum v2.0 flight computers.
584 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosdroid"></a>E.1.3. AltosDroid</h3></div></div></div><p>AltosDroid new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
585 Monitor Idle mode. Check state of flight computer while in
586 idle mode over the radio link
587 </li><li class="listitem">
588 Fire Igniters. Remotely fire ignires for recovery system
590 </li><li class="listitem">
591 Remote reboot. Cause the flight computer to reboot over the
592 radio link. This provides a method for switching the flight
593 computer from idle to flight mode without needing to reach
595 </li><li class="listitem">
596 Configurable frequency menu. Change the set of available
597 frequencies and provide more descriptive names.
598 </li></ul></div><p>AltosDroid bug fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
599 Don’t set target location if GPS hasn’t locked yet.
600 </li><li class="listitem">
601 Fix saving target states so they can be reloaded when the
602 application restarts. When the application is shut down and
603 restarted, all previous target state information will be
604 restored (including GPS position if available).
605 </li><li class="listitem">
606 Fix crash on some Android devices for offline maps when
607 changing the map scale or location.
608 </li><li class="listitem">
609 Don’t require USB OTG support. This kept the latest
610 AltosDroid from being offered on devices without USB device
611 support, although it can work without that just fine using
613 </li><li class="listitem">
614 Don’t require bluetooth to be enabled. This allows the
615 application to operate with USB devices or just show old
616 data without turning on the bluetooth radio.
617 </li><li class="listitem">
618 Recover old tracker positions when restarting
619 application. This finally allows you to safely stop and
620 restart the application without losing the last known
621 location of any tracker.
622 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation"></a>E.1.4. Documentation</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
623 Document TeleMega and EasyMega additional pyro channel
624 continuity audio alert pattern.
625 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6_2"></a>E.2. Release Notes for Version 1.6.2</h2></div></div></div><p>Version 1.6.2 includes support for our updated TeleMega v2.0
626 product and bug fixes in in the flight software for all our boards
627 and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_2"></a>E.2.1. AltOS</h3></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
628 Add support for TeleMega v2.0 boards.
629 </li><li class="listitem">
630 Add PWM servo driver. There’s no higher level code using
631 this yet, but the driver allows testing of the TeleMega v2.0
632 servo output connector.
633 </li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
634 Slow down telemetry packets to allow receiver to keep
636 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_2"></a>E.2.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
637 Fix post-flight orientation computation when processing
638 TeleMega and EasyMega eeprom data files.
639 </li><li class="listitem">
640 Capture complete eeprom data even when there are invalid
641 entries in the data. This keeps reading eeprom contents and
642 writing the associated .eeprom file when an error is detected.
643 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation_2"></a>E.2.3. Documentation</h3></div></div></div><p>We spent a bunch of time trying to improve our documentation</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
644 HTML versions now have a table of contents on the left side.
645 </li><li class="listitem">
646 EasyMini now has its own shorter manual.
647 </li><li class="listitem">
648 Provide links between sections in each document.
649 </li><li class="listitem">
650 Lots of minor rewriting and restructuring to avoid
651 duplication of information
652 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6_1"></a>E.3. Release Notes for Version 1.6.1</h2></div></div></div><p>Version 1.6.1 includes support for our updated TeleBT v3.0
653 product and bug fixes in in the flight software for all our boards
654 and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_3"></a>E.3.1. AltOS</h3></div></div></div><p>AltOS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
655 Add support for TeleBT v3.0 boards.
656 </li><li class="listitem">
657 Add support for uncompressed APRS data, providing support
658 for older APRS receivers. Uncompressed APRS data is less
659 precise, takes more bandwidth and doesn’t have integrated
661 </li></ul></div><p>AltOS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
662 Make TeleDongle and TeleBT more tolerant of data rate
663 variations from transmitting devices.
664 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_3"></a>E.3.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
665 Add map to Monitor Idle display. It’s nice to be able to
666 verify that maps are working, instead of needing to use
668 </li></ul></div><p>AltosUI and TeleGPS Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
669 Fix frequency configuration to round values instead of
670 truncate them, avoiding a common 1kHz error in the setting.
671 </li><li class="listitem">
672 Turn the Windows stub into a more useful program that can
673 launch the application with parameters so that file manager
674 icons work more reliably.
675 </li><li class="listitem">
676 Force KML export to use a C locale so that numbers are
677 formatted with <span class="emphasis"><em>.</em></span> instead of <span class="emphasis"><em>,</em></span> for a decimal separator in
679 </li><li class="listitem">
680 Preload map tiles based on distance rather than number of
681 tiles; this means you get the same resolution covering the
682 entire area, rather than having high resolution near the
683 center and low resolution further away.
684 </li><li class="listitem">
685 Allow configuration of frequency and callsign in Monitor
687 </li><li class="listitem">
688 Fix layout weirdness when resizing windows on
689 Windows. Windows shouldn’t have giant blank spaces around
690 the useful content anymore.
691 </li><li class="listitem">
692 Fix layout weirdness when resizing windows on
693 Windows. Windows shouldn’t have giant blank spaces around
694 the useful content anymore.
695 </li><li class="listitem">
696 Use a longer filter for descent speed values. This should
697 provide something more useful on the display, although it
698 will take longer to respond to changes now.
699 </li><li class="listitem">
700 Make Replay Flight run in realtime again. It had been set to
701 run at 10x speed by mistake.
702 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosdroid_2"></a>E.3.3. AltosDroid</h3></div></div></div><p>AltosDroid New Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
703 Add offline map support using mapping code from AltosUI.
704 </li><li class="listitem">
705 Support TeleDongle (and TeleBT via USB) on devices
706 supporting USB On-The-Go.
707 </li><li class="listitem">
708 Display additional TeleMega pyro channel status in Pad tab.
709 </li><li class="listitem">
710 Switch between metric and imperial units.
711 </li><li class="listitem">
712 Monitor TeleBT battery voltage.
713 </li><li class="listitem">
714 Track multiple devices at the same time, selecting between
715 them with a menu or using the map.
716 </li><li class="listitem">
717 Add hybrid, satellite and terrain map types.
718 </li></ul></div><p>AltosDroid Fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
719 Use standard Android display conventions so that a menu
720 button is available in the application title bar.
721 </li><li class="listitem">
722 Adjust layout to work on large and small screens; shrinking
723 the go/no-go lights in smaller environments to try and make
725 </li><li class="listitem">
726 Make voice announcements depend on current tab.
727 </li><li class="listitem">
728 Compute adjustment to current travel direction while in
729 motion towards rocket.
730 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_6"></a>E.4. Release Notes for Version 1.6</h2></div></div></div><p>Version 1.6 includes support for our updated TeleDongle v3.0
731 product and bug fixes in in the flight software for all our boards
732 and ground station interfaces.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_4"></a>E.4.1. AltOS</h3></div></div></div><p>AltOS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
733 Add support for TeleDongle v3.0 boards.
734 </li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
735 Don’t beep out the continuity twice by accident in idle mode.
736 If the battery voltage report takes longer than the initialiation
737 sequence, the igniter continuity would get reported twice.
738 </li><li class="listitem">
739 Record all 32 bits of gyro calibration data in TeleMega and
740 EasyMega log files. This fixes computation of the gyro rates
742 </li><li class="listitem">
743 Change TeleDongle LED usage. Green LED flashes when valid
744 packet is received. Red LED flashes when invalid packet is
746 </li><li class="listitem">
747 Replace LPC11U14 SPI driver with non-interrupt version. The
748 interrupt code would occasionally wedge on long transfers
749 if interrupts were blocked for too long. This affects all
750 released TeleGPS products; if you have a TeleGPS device,
751 you’ll want to reflash the firmware.
752 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_4"></a>E.4.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
753 Compute tilt angle from TeleMega and EasyMega log
754 files. This duplicates the quaternion-based angle tracking
755 code from the flight firmware inside the ground station
756 software so that post-flight analysis can include evaluation
758 </li><li class="listitem">
759 Shows the tool button window when starting with a data file
760 specified. This means that opening a data file from the file
761 manager will now bring up the main window to let you operate
762 the whole application.
763 </li></ul></div><p>AltosUI Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
764 Show the <span class="emphasis"><em>Connecting</em></span> dialog when using Monitor Idle. Lets
765 you cancel the Monitor Idle startup when connecting over the
767 </li><li class="listitem">
768 Make <span class="emphasis"><em>Monitor Idle</em></span> work for TeleGPS devices when connected
769 over USB. It’s nice for testing without needing to broadcast
771 </li><li class="listitem">
772 Use different Windows API to discover USB devices. This
773 works better on my Windows 7 box, and will be used if the
774 older API fails to provide the necessary information.
775 </li><li class="listitem">
776 Look in more places in the registry to try and identify the
777 installed Java version on Windows. If you install the
778 default 32-bit version of Windows on a 64-bit OS, the Java
779 registry information is hiding \SOFTWARE\Wow6432Node for
781 </li><li class="listitem">
782 Fix file association on Windows by searching for the
783 javaw.exe program instead of assuming it is in
784 %SYSTEMROOT%. This makes double-clicking on Altus Metrum
785 data files in the file manager work correctly.
786 </li><li class="listitem">
787 When replaying a file, put <span class="emphasis"><em>done</em></span> in the Age field when we
788 reach the end of the file, instead of continuing to count forever.
789 </li><li class="listitem">
790 In the Scan Channels code, wait for five seconds if we see
791 any packet. This is needed because AltOS now sends the
792 callsign, serial number and flight number only once every
793 five seconds these days.
794 </li><li class="listitem">
795 In the Scan Channels code, reset pending flight state
796 information each time we change channels. This avoids having
797 flight computers appear on multiple frequencies by accident.
798 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_5"></a>E.5. Release Notes for Version 1.5</h2></div></div></div><p>Version 1.5 is a major release. It includes support for our new
799 EasyMega product, new features and bug fixes in in the flight
800 software for all our boards and the AltosUI ground station</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_5"></a>E.5.1. AltOS</h3></div></div></div><p>AltOS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
801 Add support for EasyMega boards.
802 </li><li class="listitem">
803 Make the APRS SSID be configurable. This lets you track
804 different rockets on the same receiver without getting
806 </li><li class="listitem">
807 Report extra pyro channel continuity state on EasyMega and
808 TeleMega via the beeper. This lets you easily verify flight
809 readiness on these boards after powering up the electronics
811 </li><li class="listitem">
812 Add lower telemetry data rates (2400 and 9600 bps) to
813 increase telemetry radio range. This reduces the amount of
814 data received as well as increasing battery consumption in
816 </li><li class="listitem">
817 Change TeleGPS to have only a single log, and append new
818 data to it rather than using seperate per-flight logs. This
819 avoids accidentally filling up log storage by turning
820 TeleGPS on/off several times.
821 </li></ul></div><p>AltOS Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
822 Increase the maximum range for altitude values from +/-32767m
823 to +/-2147483647m, allowing the flight computers to function
824 correctly above the 32km level.
825 </li><li class="listitem">
826 Continuously test pyro firing conditions during delay stage,
827 inhibiting the pyro channel if the test fails. This prevents
828 firing pyro charges where the conditions were good before
829 the delay, but become bad before the delay expires.
830 </li><li class="listitem">
831 Allow negative numbers in pyro configuration values. This
832 lets you specify things like descending speed or
834 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_5"></a>E.5.2. AltosUI and TeleGPS Applications</h3></div></div></div><p>AltosUI and TeleGPS New Features</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
835 Support telemetry baud rate selection. Adds menus to
836 the flight monitoring and configuration for baud rate
838 </li><li class="listitem">
839 Support APRS SSID configuration.
840 </li><li class="listitem">
841 Integrate with file managers. This provides icons for all of
842 our file types and associates our application with the files
843 so that using a file manager to open a AltOS data file
844 results in launching our application.
845 </li></ul></div><p>AltosUI Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
846 Make the <span class="emphasis"><em>Graph</em></span> button on the landed tab work again.
847 </li><li class="listitem">
848 Make tests for Java on Windows a bit smarter, and also
849 provide the user with the option to skip installing Java for
850 cases where we just can’t figure out what version is installed.
851 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_4_2"></a>E.6. Release Notes for Version 1.4.2</h2></div></div></div><p>Version 1.4.2 is a minor release. It fixes Java-related install issues on
852 Windows</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_6"></a>E.6.1. AltosUI and TeleGPS Applications</h3></div></div></div><p>Windows Install Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
853 Checks for Java installation data in more registry locations.
854 </li><li class="listitem">
855 Allows user to bypass Java installation in case the
857 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_4_1"></a>E.7. Release Notes for Version 1.4.1</h2></div></div></div><p>Version 1.4.1 is a minor release. It fixes install issues on
858 Windows and provides the missing TeleMetrum V2.0 firmware. There
859 aren’t any changes to the firmware or host applications at
860 all. All Windows users will want to upgrade to get the signed
861 driver, but Mac and Linux users who do not need the TeleMetrum
862 V2.0 firmware image will not need to upgrade.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_and_telegps_applications_7"></a>E.7.1. AltosUI and TeleGPS Applications:</h3></div></div></div><p>Windows Install Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
863 Provide signed Windows driver files. This should avoid any need to
864 disable driver signature checking on Windows 7 or 8.
865 </li><li class="listitem">
866 Fix Java version detection and download. Previously, the
867 installer would only look for Java 6 or 7 and insist on
868 downloading its own Java bits if there was something else
869 installed. Furthermore, the 64-bit Java link provided didn’t
870 work for anyone other than Keith, making it impossible to
871 install AltOS on any machine with Java SE 8 installed.
872 </li></ul></div><p>Other Fixes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
873 Include 1.4 firmware for TeleMetrum V2.0. None of the
874 installers shipped this file. Now it’s included in the AltOS
875 packages for Linux, Mac and Windows.
876 </li><li class="listitem">
877 Include Google Application Key for map downloading. The 1.4
878 release didn’t have this key in the released version of the
879 software, making map downloading fail for most people.
880 </li></ul></div><p></p></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_release_notes_for_version_1_4"></a>E.8. Release Notes for Version 1.4</h2></div></div></div><p>Version 1.4 is a major release. It includes support for our new
881 TeleGPS product, new features and bug fixes in in the flight
882 software for all our boards and the AltosUI ground station</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altos_6"></a>E.8.1. AltOS</h3></div></div></div><p>AltOS new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
883 Add support for TeleGPS boards.
884 </li><li class="listitem">
885 Make the beeper tone configurable, making it
886 possible to distinguish between two Altus Metrum
887 products in the same ebay.
888 </li><li class="listitem">
889 Make the firing time for extra pyro channels
890 configurable, allowing longer (or shorter) than the
891 default 50ms. Only relevant for TeleMega at this
893 </li></ul></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
894 Replace the <span class="emphasis"><em>dit dit dit</em></span> tones at startup with the
895 current battery voltage, measured in tenths of a
896 volt. This lets you check the battery voltage
897 without needing telemetry, which is especially
899 </li><li class="listitem">
900 Change state beeping to "Farnsworth spacing", which
901 means they’re quite a bit faster than before, and so
902 they take less time to send.
903 </li><li class="listitem">
904 Fix bug preventing the selection of the <span class="emphasis"><em>Flight
905 State After</em></span> mode in pyro configuration.
906 </li><li class="listitem">
907 Fix bug where erasing flights would reset the flight
908 number to 2 on TeleMega and TeleMetrum v2.
909 </li><li class="listitem">
910 Fix u-Blox GPS driver to mark course and speed data
912 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_altosui_application"></a>E.8.2. AltosUI Application</h3></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
913 Add zooming and new content types (terrain and road
914 maps) to map view. Change map storage format from
915 PNG to Jpeg, which saves a huge amount of disk
916 space. You will need to re-download all of your
917 pre-loaded map images.
918 </li><li class="listitem">
919 Add a distance measuring device to the maps
920 view. Select this by using any button other than the
921 left one, or by pressing shift or control on the
922 keyboard while using the left button.
923 </li><li class="listitem">
924 Add new <span class="emphasis"><em>Ignitor</em></span> tab to the flight monitor display
925 for TeleMega’s extra ignitors.
926 </li><li class="listitem">
927 Add additional ignitor firing marks and voltages to
928 the graph so you can see when the ignitors fired,
929 along with the ignitor voltages.
930 </li><li class="listitem">
931 Add GPS course, ground speed and climb rate as
932 optional graph elements.
933 </li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
934 When flashing new firmware, re-try opening the
935 device as sometimes it takes a while for the
936 underlying operating system to recognize that the
937 device has rebooted in preparation for the flashing
939 </li><li class="listitem">
940 Hide Tilt Angle in ascent tab for devices that don’t
942 </li><li class="listitem">
943 Increase the width of data lines in the graphs to
944 make them easier to read.
945 </li><li class="listitem">
946 Filter out speed and acceleration spikes caused by
947 ejection charge firing when computing the maximum
948 values. This provides a more accurate reading of
950 </li><li class="listitem">
951 Fix EasyMini voltage displays. Early EasyMini
952 prototypes used a 3.0V regulator, and AltosUI still
953 used that value as the basis of the
954 computation. Production EasyMini boards have always
955 shipped with a 3.3V regulator. Also, purple EasyMini
956 boards sensed the battery voltage past the blocking
957 diode, resulting in a drop of about 150mV from the
958 true battery voltage. Compensate for that when
959 displaying the value.
960 </li><li class="listitem">
961 Display error message when trying to configure
962 maximum flight log size while the flight computer
963 still has flight data stored.
964 </li><li class="listitem">
965 Handle TeleMetrum and TeleMini eeprom files
966 generated with pre-1.0 firmware. Those ancient
967 versions didn’t report the log format, so just use
968 the product name instead.
969 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_telegps_application_2"></a>E.8.3. TeleGPS Application</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
970 New application designed for use with TeleGPS boards.
971 </li><li class="listitem">
972 Shares code with AltosUI, mostly just trimmed down
973 to focus on TeleGPS-related functions.
974 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="_documentation_3"></a>E.8.4. Documentation</h3></div></div></div><p>Documentation changes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
975 Re-create the drill template images; they should
976 print correctly from Firefox at least. Ship these as
977 individual PDF files so they’re easy to print.
978 </li><li class="listitem">
979 Add a description of the <span class="emphasis"><em>Apogee Lockout</em></span> setting,
980 which prevents the apogee charge from firing for a
981 configurable amount of time after boost.
982 </li></ul></div></div></div></div></div></body></html>
projects / web / altusmetrum / blob