1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>TeleGPS Owner's Manual</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="idp34092416"></a>TeleGPS Owner's Manual</h1></div><div><h2 class="subtitle">A recording GPS tracker</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3></div></div><div><p class="copyright">Copyright © 2014 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a name="idp60435168"></a><p>
2 This document is released under the terms of the
3 <a class="ulink" href="http://creativecommons.org/licenses/by-sa/3.0/" target="_top">
4 Creative Commons ShareAlike 3.0
7 </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.4.1</td><td align="left">20 June 2014</td></tr><tr><td align="left" colspan="2">
8 Minor release fixing some installation bugs.
9 </td></tr><tr><td align="left">Revision 1.4</td><td align="left">13 June 2014</td></tr><tr><td align="left" colspan="2">
11 </td></tr></table></div></div></div><hr></div><div class="dedication"><div class="titlepage"><div><div><h1 class="title"><a name="idp60440208"></a>Acknowledgements</h1></div></div></div><p>
12 Have fun using these products, and we hope to meet all of you
13 out on the rocket flight line somewhere.
14 </p><div class="literallayout"><p><br>
15 Bdale Garbee, KB0G<br>
16 NAR #87103, TRA #12201<br>
18 Keith Packard, KD7SQG<br>
19 NAR #88757, TRA #12200<br>
21 </p></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="#idp60442576">1. Quick Start Guide</a></span></dt><dt><span class="chapter"><a href="#idp61322976">2. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idp61325872">3. TeleGPS Hardware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp61326544">1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idp61329472">2. On-board Data Recording</a></span></dt><dt><span class="section"><a href="#idp61333680">3. Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp60611120">4. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp60611792">1. GFSK Telemetry</a></span></dt><dt><span class="section"><a href="#idp60614720">2. APRS</a></span></dt><dt><span class="section"><a href="#idp60452976">3. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp60454304">3.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp60456432">3.2. Callsign</a></span></dt><dt><span class="section"><a href="#idp60457616">3.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp60458944">3.4. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp60460448">3.5. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp60462048">3.6. Logging Trigger Motion</a></span></dt><dt><span class="section"><a href="#idp60463376">3.7. Position Reporting Interval</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp60465024">5. TeleGPS Application</a></span></dt><dd><dl><dt><span class="section"><a href="#idp60466608">1. Telemetry Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp65947584">1.1. Map</a></span></dt><dt><span class="section"><a href="#idp65953616">1.2. Location</a></span></dt><dt><span class="section"><a href="#idp65956928">1.3. Status</a></span></dt><dt><span class="section"><a href="#idp65960480">1.4. Table</a></span></dt></dl></dd><dt><span class="section"><a href="#idp65964528">2. TeleGPS Menus</a></span></dt><dd><dl><dt><span class="section"><a href="#idp65972624">2.1. New Window</a></span></dt><dt><span class="section"><a href="#idp65973952">2.2. Graph Data</a></span></dt><dt><span class="section"><a href="#idp65990624">2.3. Export Data</a></span></dt><dt><span class="section"><a href="#idp65996688">2.4. Load Maps</a></span></dt><dt><span class="section"><a href="#idp66010688">2.5. Preferences</a></span></dt><dt><span class="section"><a href="#idp66031072">2.6. Close</a></span></dt><dt><span class="section"><a href="#idp66032368">2.7. Exit</a></span></dt><dt><span class="section"><a href="#idp66033632">2.8. Connect Device</a></span></dt><dt><span class="section"><a href="#idp66037296">2.9. Disconnect</a></span></dt><dt><span class="section"><a href="#idp66038560">2.10. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp66042240">2.11. Download Data</a></span></dt><dt><span class="section"><a href="#idp66045408">2.12. Configure Device</a></span></dt><dt><span class="section"><a href="#idp64831824">2.13. Flash Device</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp63308272">6. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp66058400">1.
22 Updating TeleGPS Firmware
23 </a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp66067760">7. Technical Information</a></span></dt><dd><dl><dt><span class="section"><a href="#idp66068432">1. GPS Receiver</a></span></dt><dt><span class="section"><a href="#idp66071744">2. Micro-controller</a></span></dt><dt><span class="section"><a href="#idp66073072">3. Lithium Polymer Battery</a></span></dt><dt><span class="section"><a href="#idp66074336">4. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#idp66075664">5. On-board data storage</a></span></dt></dl></dd><dt><span class="appendix"><a href="#idp66077120">A. Release Notes</a></span></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>4.1. <a href="#idp60617744">Altus Metrum APRS Comments</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp60442576"></a>Chapter 1. Quick Start Guide</h1></div></div></div><p>
24 TeleGPS is designed to be easy to use. Requiring no external
25 components, flying takes just a few steps.
27 First, download and install the software from <a class="ulink" href="http://altusmetrum.org/AltOS" target="_top">http://altusmetrum.org/AltOS</a>. This will make sure that
28 you have the right device drivers installed.
30 Next, plug in the battery and USB cable and connect TeleGPS to
31 your computer. This will charge the battery and allow you to
34 Start the TeleGPS application and set the callsign and frequency
35 on your TeleGPS device; refer to the Configure TeleGPS section
36 in the TeleGPS Application chapter for instructions.
38 Unplug TeleGPS when the battery charger light goes green. This
39 will enable the radio and logging portions of the TeleGPS
42 Connect TeleDongle to your computer and start TeleGPS or start
43 AltosDroid on your android device and connect to TeleBT. Set the
44 frequency to match the TeleGPS and you should be receiving telemetry.
45 </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp61322976"></a>Chapter 2. Handling Precautions</h1></div></div></div><p>
46 All Altus Metrum products are sophisticated electronic devices.
47 When handled gently and properly installed in an air-frame, they
48 will deliver impressive results. However, as with all electronic
49 devices, there are some precautions you must take.
51 The Lithium polymer batteries have an
52 extraordinary power density. This is great because we can fly with
53 much less battery mass... but if they are punctured
54 or their contacts are allowed to short, they can and will release their
56 Thus we recommend that you take some care when handling TeleGPS
57 to keep conductive material from coming in contact with the exposed metal elements.
59 As with all other rocketry electronics, Altus Metrum devices must
60 be protected from exposure to corrosive motor exhaust and ejection
62 </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp61325872"></a>Chapter 3. TeleGPS Hardware</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp61326544">1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idp61329472">2. On-board Data Recording</a></span></dt><dt><span class="section"><a href="#idp61333680">3. Installation</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp61326544"></a>1. Hooking Up Lithium Polymer Batteries</h2></div></div></div><p>
63 TeleGPS has a two pin JST PH series connector to connect up
64 a single-cell Lithium Polymer cell (3.7V nominal). You can
65 purchase matching batteries from the Altus Metrum store, or
66 other vendors, or you can make your own. Pin 1 of the
67 connector is positive, pin 2 is negative. Spark Fun sells a
68 cable with the connector attached, which they call a <a class="ulink" href="https://www.sparkfun.com/products/9914" target="_top">JST Jumper 2
71 Many RC vendors also sell lithium polymer batteries with
72 this same connector. All that we have found use the opposite
73 polarity, and if you use them that way, you will damage or
75 </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp61329472"></a>2. On-board Data Recording</h2></div></div></div><p>
76 TeleGPS logs GPS data at a user-configurable rate. Data are
77 logged to a 2MB on-board flash memory part, which can be
78 partitioned into several equal-sized blocks, one for each
79 flight. 64kB of this storage are reserved to hold
80 configuration data, leaving 1984kB for flight data.
82 The on-board flash is partitioned into separate flight logs,
83 each of a fixed maximum size. Increase the maximum size of
84 each log and you reduce the number of flights that can be
85 stored. Decrease the size and you can store more flights.
87 To compute the amount of space needed for a single log, you
88 can divide the expected time (in seconds) by the sample period
89 (by default, 1 second per sample) and then multiply the result
90 by 32 bytes per sample. For instance, a sample period of 1
91 second and a flight lasting one hour will take 32 * 3600 =
92 115200 bytes. TeleGPS does try to reduce log space used by not
93 recording position information when it isn't moving, so actual
94 space consumed may be less than this.
96 The default size allows for four flights of 496kB each, which
97 provides over four hours of logging at 1 sample per second.
99 TeleGPS will not overwrite existing flight data, so be sure to
100 download flight data and erase it from the onboard flash
101 before it fills up. TeleGPS will still report telemetry even
102 if memory is full, so the only thing you will lose is the
104 </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp61333680"></a>3. Installation</h2></div></div></div><p>
105 The battery connectors are a standard 2-pin JST connector and
106 match batteries sold by Spark Fun. These batteries are
107 single-cell Lithium Polymer batteries that nominally provide 3.7
108 volts. Other vendors sell similar batteries for RC aircraft
109 using mating connectors, however the polarity for those is
110 generally reversed from the batteries used by Altus Metrum
111 products. In particular, the Tenergy batteries supplied for use
112 in Featherweight flight computers are not compatible with Altus
113 Metrum flight computers or battery chargers. <span class="emphasis"><em>Check
114 polarity and voltage before connecting any battery not purchased
115 from Altus Metrum or Spark Fun.</em></span>
117 TeleGPS uses an integrate GPS patch antenna and won't
118 receive GPS signals if installed inside a metal or carbon
119 fiber compartment. Test GPS reception and telemetry
120 transmission with the system installed and all other
121 electronics powered up to verify signal reception and make
122 sure there isn't any interference from other systems.
123 </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp60611120"></a>Chapter 4. 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="#idp60611792">1. GFSK Telemetry</a></span></dt><dt><span class="section"><a href="#idp60614720">2. APRS</a></span></dt><dt><span class="section"><a href="#idp60452976">3. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp60454304">3.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp60456432">3.2. Callsign</a></span></dt><dt><span class="section"><a href="#idp60457616">3.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp60458944">3.4. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp60460448">3.5. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp60462048">3.6. Logging Trigger Motion</a></span></dt><dt><span class="section"><a href="#idp60463376">3.7. Position Reporting Interval</a></span></dt></dl></dd></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp60611792"></a>1. GFSK Telemetry</h2></div></div></div><p>
124 TeleGPS's native telemetry system doesn't use a 'normal packet
125 radio' mode like APRS because it's not very efficient. The
126 GFSK modulation we use is FSK with the base-band pulses passed
127 through a Gaussian filter before they go into the modulator to
128 limit the transmitted bandwidth. When combined with forward
129 error correction and interleaving, this allows us to have a
130 very robust 19.2 kilobit data link with only 10-40 milliwatts
131 of transmit power, a whip antenna in the rocket, and a
132 hand-held Yagi on the ground. We've had flights to above 21k
133 feet AGL with great reception, and calculations suggest we
134 should be good to well over 40k feet AGL with a 5-element yagi
135 on the ground with our 10mW units and over 100k feet AGL with
137 </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp60614720"></a>2. APRS</h2></div></div></div><p>
138 TeleGPS can send APRS if desired, and the
139 interval between APRS packets can be configured. As each APRS
140 packet takes a full second to transmit, we recommend an
141 interval of at least 5 seconds to avoid consuming too much
142 battery power or radio channel bandwidth. You can configure
143 the APRS interval using AltosUI; that process is described in
144 the Configure Altimeter section of the AltosUI chapter.
146 AltOS uses the APRS compressed position report data format,
147 which provides for higher position precision and shorter
148 packets than the original APRS format. It also includes
149 altitude data, which is invaluable when tracking rockets. We
150 haven't found a receiver which doesn't handle compressed
151 positions, but it's just possible that you have one, so if you
152 have an older device that can receive the raw packets but
153 isn't displaying position information, it's possible that this
156 The APRS packet format includes a comment field that can have
157 arbitrary text in it. AltOS uses this to send status
158 information about the flight computer. It sends four fields as
159 shown in the following table.
160 </p><div class="table"><a name="idp60617744"></a><p class="title"><b>Table 4.1. Altus Metrum APRS Comments</b></p><div class="table-contents"><table summary="Altus Metrum APRS Comments" border="1"><colgroup><col align="center" class="Field"><col align="center" class="Example"><col align="center" class="Description"></colgroup><thead><tr><th align="center">Field</th><th align="center">Example</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">1</td><td align="center">L</td><td align="center">GPS Status U for unlocked, L for locked</td></tr><tr><td align="center">2</td><td align="center">6</td><td align="center">Number of Satellites in View</td></tr><tr><td align="center">3</td><td align="center">B4.0</td><td align="center">Battery Voltage</td></tr></tbody></table></div></div><br class="table-break"><p>
161 Here's an example of an APRS comment showing GPS lock with 6
162 satellites in view and a battery at 4.0V.
163 </p><pre class="screen">
167 Make sure your primary battery is above 3.8V and GPS is locked
168 with at least 5 or 6 satellites in view before starting. If GPS
169 is switching between L and U regularly, then it doesn't have a
170 good lock and you should wait until it becomes stable.
172 If the GPS receiver loses lock, the APRS data transmitted will
173 contain the last position for which GPS lock was
174 available. You can tell that this has happened by noticing
175 that the GPS status character switches from 'L' to 'U'. Before
176 GPS has locked, APRS will transmit zero for latitude,
177 longitude and altitude.
178 </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp60452976"></a>3. Configurable Parameters</h2></div></div></div><p>
179 Configuring TeleGPS is very
180 simple; the few configurable parameters can all be set
181 using the TeleGPS application over USB. Read
182 the Configure TeleGPS section in the TeleGPS Software chapter below
183 for more information.
184 </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60454304"></a>3.1. Radio Frequency</h3></div></div></div><p>
185 Altus Metrum boards support radio frequencies in the 70cm
186 band. By default, the configuration interface provides a
187 list of 10 “standard” frequencies in 100kHz channels starting at
188 434.550MHz. However, the firmware supports use of
189 any 50kHz multiple within the 70cm band. At any given
190 launch, we highly recommend coordinating when and by whom each
191 frequency will be used to avoid interference. And of course, both
192 TeleGPS and the receiver must be configured to the same
193 frequency to successfully communicate with each other.
194 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60456432"></a>3.2. Callsign</h3></div></div></div><p>
195 This sets the callsign used for telemetry and APRS to
197 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60457616"></a>3.3. Telemetry/RDF/APRS Enable</h3></div></div></div><p>
198 You can completely disable the radio, if necessary, leaving
199 TeleGPS only logging data to internal memory.
200 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60458944"></a>3.4. APRS Interval</h3></div></div></div><p>
201 This selects how often APRS packets are transmitted. Set
202 this to zero to disable APRS without also disabling the
203 regular telemetry and RDF transmissions. As APRS takes a
204 full second to transmit a single position report, we
205 recommend sending packets no more than once every 5 seconds.
206 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60460448"></a>3.5. Maximum Flight Log</h3></div></div></div><p>
207 Changing this value will set the maximum amount of flight
208 log storage that an individual flight will use. The
209 available storage is divided into as many flights of the
210 specified size as can fit in the available space. You can
211 download and erase individual flight logs. If you fill up
212 the available storage, future flights will not get logged
213 until you erase some of the stored ones.
214 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60462048"></a>3.6. Logging Trigger Motion</h3></div></div></div><p>
215 If TeleGPS moves less than this distance over a long period
216 of time, it will not log that location, saving storage space.
217 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp60463376"></a>3.7. Position Reporting Interval</h3></div></div></div><p>
218 This sets how often TeleGPS reports position information via
219 telemetry and to the on-board log. Reducing this value will
220 save power and logging memory consumption.
221 </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp60465024"></a>Chapter 5. TeleGPS Application</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp60466608">1. Telemetry Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp65947584">1.1. Map</a></span></dt><dt><span class="section"><a href="#idp65953616">1.2. Location</a></span></dt><dt><span class="section"><a href="#idp65956928">1.3. Status</a></span></dt><dt><span class="section"><a href="#idp65960480">1.4. Table</a></span></dt></dl></dd><dt><span class="section"><a href="#idp65964528">2. TeleGPS Menus</a></span></dt><dd><dl><dt><span class="section"><a href="#idp65972624">2.1. New Window</a></span></dt><dt><span class="section"><a href="#idp65973952">2.2. Graph Data</a></span></dt><dt><span class="section"><a href="#idp65990624">2.3. Export Data</a></span></dt><dt><span class="section"><a href="#idp65996688">2.4. Load Maps</a></span></dt><dt><span class="section"><a href="#idp66010688">2.5. Preferences</a></span></dt><dt><span class="section"><a href="#idp66031072">2.6. Close</a></span></dt><dt><span class="section"><a href="#idp66032368">2.7. Exit</a></span></dt><dt><span class="section"><a href="#idp66033632">2.8. Connect Device</a></span></dt><dt><span class="section"><a href="#idp66037296">2.9. Disconnect</a></span></dt><dt><span class="section"><a href="#idp66038560">2.10. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp66042240">2.11. Download Data</a></span></dt><dt><span class="section"><a href="#idp66045408">2.12. Configure Device</a></span></dt><dt><span class="section"><a href="#idp64831824">2.13. Flash Device</a></span></dt></dl></dd></dl></div><p>
222 The TeleGPS application provides a graphical user interface for
223 interacting with the Altus Metrum product family. TeleGPS can
224 monitor telemetry data, configure devices and many other
225 tasks. The primary interface window is for displaying data
226 received over the telemetry link. There are additional
227 tasks available from the main window menu bar. This chapter
228 is split into sections, each of which documents one of the tasks
229 provided from the top-level toolbar.
230 </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp60466608"></a>1. Telemetry Monitoring</h2></div></div></div><p>
231 This is the window brought up when you start the
232 application. If you have a TeleDongle device connected to the
233 computer, it will automatically be selected for telemetry monitoring
235 All telemetry data received are automatically recorded in
236 suitable log files. The name of the files includes the current
237 date and TeleGPS serial and flight numbers.
239 The radio frequency being monitored by the TeleDongle device
240 is displayed at the top of the window. You can configure the
241 frequency by clicking on the frequency box and selecting the
242 desired frequency. The TeleGPS application remembers the last
243 frequency selected for each TeleDongle and selects that
244 automatically the next time you use that device.
246 Below the TeleDongle frequency selector, the window contains a few
247 significant pieces of information about the altimeter providing
248 the telemetry data stream:
249 </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. TeleGPS remembers how many
251 </p></li><li class="listitem"><p>
252 The Received Signal Strength Indicator value. This lets
253 you know how strong a signal TeleDongle is receiving. The
254 radio inside TeleDongle operates down to about -100dBm;
255 weaker signals may not be receivable. The packet link uses
256 error detection and correction techniques which prevent
257 incorrect data from being reported.
258 </p></li><li class="listitem"><p>
259 The age of the displayed data, in seconds since the last
260 successfully received telemetry packet. In normal operation
261 this will stay in the low single digits. If the number starts
262 counting up, then you are no longer receiving data over the radio
263 link from the flight computer.
264 </p></li></ul></div><p>
265 Finally, the largest portion of the window contains a set of
266 tabs, each of which contain some information about the TeleGPS
267 board. The final 'table' tab displays many of the raw telemetry
268 values in one place in a spreadsheet-like format.
269 </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65947584"></a>1.1. Map</h3></div></div></div><p>
270 The Map tab shows the TeleGPS track over time on top of map
271 data making it easy to locate the device.
272 </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-map.png" width="495"></td></tr></table></div></div><p>
273 The map's default scale is approximately 3m (10ft) per pixel. The map
274 can be dragged using the left mouse button. The map will attempt
275 to keep the rocket roughly centered while data is being received.
277 You can adjust the style of map and the zoom level with
278 buttons on the right side of the map window. You can draw a
279 line on the map by moving the mouse over the map with a
280 button other than the left one pressed, or by pressing the
281 left button while also holding down the shift key. The
282 length of the line in real-world units will be shown at the
285 Images are fetched automatically via the Google Maps Static API,
286 and cached on disk for reuse. If map images cannot be downloaded,
287 the rocket's path will be traced on a dark gray background
290 You can pre-load images for your favorite launch sites
291 before you leave home; check out the 'Preload Maps' section below.
292 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65953616"></a>1.2. Location</h3></div></div></div><p>
293 The Location tab shows the raw GPS data received from TeleGPS.
294 </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-location.png" width="495"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65956928"></a>1.3. Status</h3></div></div></div><p>
295 The Status tab shows data relative to the location of
296 TeleGPS when the application first received telemetry from
298 </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-status.png" width="495"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65960480"></a>1.4. Table</h3></div></div></div><p>
299 The Table tab shows detailed information about the GPS
301 </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="495"><tr><td><img src="telegps-table.png" width="495"></td></tr></table></div></div></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp65964528"></a>2. TeleGPS Menus</h2></div></div></div><p>
302 TeleGPS has three or four menus at the top of the window:
303 </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">File</span></dt><dd><p>
304 New Window, Graph Data, Export Data, Load Maps, Preferences, Close and Exit
305 </p></dd><dt><span class="term">Monitor</span></dt><dd><p>
306 Connect Device, Disconnect and Scan Channels
307 </p></dd><dt><span class="term">Device</span></dt><dd><p>
308 Download Data, Configure Device and Flash Device
309 </p></dd><dt><span class="term">Frequency</span></dt><dd><p>
310 This shows the current monitoring frequency with a
311 drop-down menu listing other configured
312 frequencies. You can change the set of frequencies
313 shown here from the Preferences dialog. This menu is
314 only shown when the TeleGPS application is connected
315 to a TeleDongle or TeleBT device.
316 </p></dd></dl></div><p>
317 </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65972624"></a>2.1. New Window</h3></div></div></div><p>
318 This creates another telemetry monitoring window, in case
319 you have multiple TeleDongle devices connected to the
321 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65973952"></a>2.2. Graph Data</h3></div></div></div><p>
322 This brings up a file dialog to load a saved log, either
323 a .telem file of recorded telemetry or .eeprom of saved
324 data from on-board memory. It looks a bit like the flight
325 monitoring window, using a selection of tabs to show
326 different views of the saved data.
327 </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp65975296"></a>2.2.1. Graph</h4></div></div></div><p>
328 The Graph tab shows a plot of the the GPS data
329 collected. The X axis is time in seconds; there are a
330 variety of Y axes available for different kinds of data.
331 </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="telegps-graph-graph.png" width="540"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp65979104"></a>2.2.2. Configure Graph</h4></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="telegps-graph-configure.png" width="540"></td></tr></table></div></div><p>
332 This selects which graph elements to show, and, at the
333 bottom, lets you switch between metric and imperial units
334 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp65982880"></a>2.2.3. Statistics</h4></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="telegps-graph-stats.png" width="540"></td></tr></table></div></div><p>
335 Shows overall data computed from the flight.
336 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp65986496"></a>2.2.4. Map</h4></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="540"><tr><td><img src="telegps-graph-map.png" width="540"></td></tr></table></div></div><p>
337 Shows a map of the area overlaid with the GPS track. As with
338 the telemetry monitoring window, you can select the style
339 of map and zoom level using buttons along the side;
340 you can scroll the map by dragging within the map pressing
341 the left button and you can draw a line to measure
342 distances using either the left button with the shift key,
344 </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65990624"></a>2.3. Export Data</h3></div></div></div><p>
345 This tool takes the raw data files and makes them available for
346 external analysis. When you select this button, you are prompted to
347 select a data file, which can be either a .eeprom or .telem.
348 The .eeprom files contain higher resolution and more continuous data,
349 while .telem files contain receiver signal strength information.
350 Next, a second dialog appears which is used to select
351 where to write the resulting file. It has a selector to choose
352 between CSV and KML file formats.
353 </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp65992768"></a>2.3.1. Comma Separated Value Format</h4></div></div></div><p>
354 This is a text file containing the data in a form suitable for
355 import into a spreadsheet or other external data analysis
356 tool. The first few lines of the file contain the version and
357 configuration information from TeleGPS, then
358 there is a single header line which labels all of the
359 fields. All of these lines start with a '#' character which
360 many tools can be configured to skip over.
362 The remaining lines of the file contain the data, with each
363 field separated by a comma and at least one space. All of
364 the sensor values are converted to standard units, with the
365 barometric data reported in both pressure, altitude and
366 height above pad units.
367 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp65995200"></a>2.3.2. Keyhole Markup Language (for Google Earth)</h4></div></div></div><p>
368 This is the format used by Google Earth to provide an overlay
369 within that application. With this, you can use Google Earth to
370 see the whole flight path in 3D.
371 </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp65996688"></a>2.4. Load Maps</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="468"><tr><td><img src="load-maps.png" width="468"></td></tr></table></div></div><p>
372 Before using TeleGPS, you can use Load Maps to load map data
373 in case you don't have access to the internet while
376 There's a drop-down menu of rocket launch sites we know
377 about; if your favorites aren't there, please let us know
378 the lat/lon and name of the site. The contents of this list
379 are actually downloaded from our server at run-time, so as
380 new sites are sent in, they'll get automatically added to
381 this list. If the launch site isn't in the list, you can
382 manually enter the lat/lon values
384 There are four different kinds of maps you can view; you can
385 select which to download by selecting as many as you like from
387 </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Hybrid</span></dt><dd><p>
388 A combination of satellite imagery and road data. This
390 </p></dd><dt><span class="term">Satellite</span></dt><dd><p>
391 Just the satellite imagery without any annotation.
392 </p></dd><dt><span class="term">Roadmap</span></dt><dd><p>
393 Roads, political boundaries and a few geographic features.
394 </p></dd><dt><span class="term">Terrain</span></dt><dd><p>
395 Contour intervals and shading that show hills and
397 </p></dd></dl></div><p>
399 You can specify the range of zoom levels to download; smaller
400 numbers show more area with less resolution. The default
401 level, 0, shows about 3m/pixel. One zoom level change
402 doubles or halves that number.
404 The Tile Radius value sets how large an area around the center
405 point to download. Each tile is 512x512 pixels, and the
406 'radius' value specifies how many tiles away from the center
407 will be downloaded. Specify a radius of 0 and you get only the
408 center tile. A radius of 1 loads a 3x3 grid, centered on the
411 Clicking the 'Load Map' button will fetch images from Google
412 Maps; note that Google limits how many images you can fetch at
413 once, so if you load more than one launch site, you may get
414 some gray areas in the map which indicate that Google is tired
415 of sending data to you. Try again later.
416 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66010688"></a>2.5. Preferences</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="216"><tr><td><img src="telegps-preferences.png" width="216"></td></tr></table></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66013824"></a>2.5.1. Voice Settings</h4></div></div></div><p>
417 AltosUI provides voice announcements during flight so that you
418 can keep your eyes on the sky and still get information about
419 the current flight status. However, sometimes you don't want
421 </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Enable</span></dt><dd><p>Turns all voice announcements on and off</p></dd><dt><span class="term">Test Voice</span></dt><dd><p>
422 Plays a short message allowing you to verify
423 that the audio system is working and the volume settings
425 </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66018944"></a>2.5.2. Log Directory</h4></div></div></div><p>
426 AltosUI logs all telemetry data and saves all TeleMetrum flash
427 data to this directory. This directory is also used as the
428 staring point when selecting data files for display or export.
430 Click on the directory name to bring up a directory choosing
431 dialog, select a new directory and click 'Select Directory' to
432 change where AltosUI reads and writes data files.
433 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66021008"></a>2.5.3. Callsign</h4></div></div></div><p>
434 This value is transmitted in each command packet sent from
435 TeleDongle and received from an altimeter. It is not used in
436 telemetry mode, as the callsign configured in the altimeter board
437 is included in all telemetry packets. Configure this
438 with the AltosUI operators call sign as needed to comply with
439 your local radio regulations.
441 Note that to successfully command a flight computer over the radio
442 (to configure the altimeter, monitor idle, or fire pyro charges),
443 the callsign configured here must exactly match the callsign
444 configured in the flight computer. This matching is case
446 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66023312"></a>2.5.4. Imperial Units</h4></div></div></div><p>
447 This switches between metric units (meters) and imperial
448 units (feet and miles). This affects the display of values
449 use during flight monitoring, configuration, data graphing
450 and all of the voice announcements. It does not change the
451 units used when exporting to CSV files, those are always
452 produced in metric units.
453 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66024864"></a>2.5.5. Serial Debug</h4></div></div></div><p>
454 This causes all communication with a connected device to be
455 dumped to the console from which AltosUI was started. If
456 you've started it from an icon or menu entry, the output
457 will simply be discarded. This mode can be useful to debug
458 various serial communication issues.
459 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66026400"></a>2.5.6. Font Size</h4></div></div></div><p>
460 Selects the set of fonts used in the flight monitor
461 window. Choose between the small, medium and large sets.
462 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66027728"></a>2.5.7. Look & Feel</h4></div></div></div><p>
463 Adjust the style of the windows. By default, the TeleGPS
464 application attempts to blend in with the native style.
465 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp66029056"></a>2.5.8. Manage Frequencies</h4></div></div></div><p>
466 This brings up a dialog where you can configure the set of
467 frequencies shown in the various frequency menus. You can
468 add as many as you like, or even reconfigure the default
469 set. Changing this list does not affect the frequency
470 settings of any devices, it only changes the set of
471 frequencies shown in the menus.
472 </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66031072"></a>2.6. Close</h3></div></div></div><p>
473 This closes the current window, leaving any other windows
474 open and the application running.
475 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66032368"></a>2.7. Exit</h3></div></div></div><p>
476 This closes all TeleGPS windows and terminates the application.
477 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66033632"></a>2.8. Connect Device</h3></div></div></div><p>
478 Selecting this item brings up a dialog box listing all of
479 the connected TeleDongle devices. When you choose one of
480 these, AltosUI will display telemetry data as received by
481 the selected TeleDongle device.
482 </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="279"><tr><td><img src="device-selection.png" width="279"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66037296"></a>2.9. Disconnect</h3></div></div></div><p>
483 Disconnects the currently connected TeleDongle or TeleBT
484 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66038560"></a>2.10. Scan Channels</h3></div></div></div><p>
485 Scans the configured set of frequencies looking for
486 telemetry signals. A list of all of the discovered signals
487 is show; selecting one of those and clicking on 'Monitor'
488 will select that frequency in the associated TeleGPS
490 </p><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="279"><tr><td><img src="telegps-scan.png" width="279"></td></tr></table></div></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66042240"></a>2.11. Download Data</h3></div></div></div><p>
491 TeleGPS records data to its internal flash memory.
492 On-board data is recorded at the same rate as telemetry
493 but is not subject to radio drop-outs. As
494 such, it generally provides a more complete and precise record.
495 The 'Download Data' menu entry allows you to read the
496 flash memory and write it to disk.
498 Select the 'Download Data' menu entry to bring up a list of
499 connected TeleGPS devices. After the device has been
500 selected, a dialog showing the data stored in the
501 device will be shown allowing you to select which entries to
502 download and which to delete. You must erase flights in order for the space they
503 consume to be reused by another track. This prevents
504 accidentally losing data if you neglect to download
505 data before starting TeleGPS again. Note that if there is no more
506 space available in the device, then no data will be recorded.
508 The file name for each data log is computed automatically
509 from the recorded date, altimeter serial number and flight
511 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp66045408"></a>2.12. Configure Device</h3></div></div></div><div class="informalfigure"><div class="mediaobject"><table border="0" summary="manufactured viewport for HTML img" style="cellpadding: 0; cellspacing: 0;" width="324"><tr><td><img src="telegps-configure.png" width="324"></td></tr></table></div></div><p>
512 Select this button and then select any connected TeleGPS
513 device from the list provided.
515 The first few lines of the dialog provide information about the
516 connected device, including the product name,
517 software version and hardware serial number. Below that are the
518 individual configuration entries.
520 At the bottom of the dialog, there are four buttons:
521 </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Save</span></dt><dd><p>
522 This writes any changes to the
523 configuration parameter block in flash memory. If you don't
524 press this button, any changes you make will be lost.
525 </p></dd><dt><span class="term">Reset</span></dt><dd><p>
526 This resets the dialog to the most recently saved values,
527 erasing any changes you have made.
528 </p></dd><dt><span class="term">Reboot</span></dt><dd><p>
529 This reboots the device. This will restart logging for
530 a new flight number, if any log information has been
531 saved for the current flight.
532 </p></dd><dt><span class="term">Close</span></dt><dd><p>
533 This closes the dialog. Any unsaved changes will be
535 </p></dd></dl></div><p>
536 The rest of the dialog contains the parameters to be configured.
537 </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp63831792"></a>2.12.1. Frequency</h4></div></div></div><p>
538 This configures which of the frequencies to use for both
539 telemetry and packet command mode. Note that if you set this
540 value via packet command mode, the TeleDongle frequency will
541 also be automatically reconfigured to match so that
542 communication will continue afterwards.
543 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp63587264"></a>2.12.2. RF Calibration</h4></div></div></div><p>
544 The radios in every Altus Metrum device are calibrated at the
545 factory to ensure that they transmit and receive on the
546 specified frequency. If you need to you can adjust the calibration
547 by changing this value. Do not do this without understanding what
548 the value means, read the appendix on calibration and/or the source
549 code for more information. To change a TeleDongle's calibration,
550 you must reprogram the unit completely.
551 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp64336224"></a>2.12.3. Telemetry/RDF/APRS Enable</h4></div></div></div><p>
552 Enables the radio for transmission during flight. When
553 disabled, the radio will not transmit anything during flight
555 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp62178976"></a>2.12.4. APRS Interval</h4></div></div></div><p>
556 How often to transmit GPS information via APRS (in
557 seconds). When set to zero, APRS transmission is
558 disabled. This option is available on TeleMetrum v2 and
559 TeleMega boards. TeleMetrum v1 boards cannot transmit APRS
560 packets. Note that a single APRS packet takes nearly a full
561 second to transmit, so enabling this option will prevent
562 sending any other telemetry during that time.
563 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp63605184"></a>2.12.5. Callsign</h4></div></div></div><p>
564 This sets the call sign included in each telemetry packet. Set this
565 as needed to conform to your local radio regulations.
566 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp64195792"></a>2.12.6. Maximum Log Size</h4></div></div></div><p>
567 This sets the space (in kilobytes) allocated for each data
568 log. The available space will be divided into chunks of this
569 size. A smaller value will allow more logs to be stored,
570 a larger value will record data for longer times.
571 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp63537840"></a>2.12.7. Logging Trigger Motion</h4></div></div></div><p>
572 If TeleGPS moves less than this distance over a long period
573 of time, it will not log that location, saving storage space.
574 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp63009520"></a>2.12.8. Position Reporting Interval</h4></div></div></div><p>
575 This sets how often TeleGPS reports position information via
576 telemetry and to the on-board log. Reducing this value will
577 save power and logging memory consumption.
578 </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp64831824"></a>2.13. Flash Device</h3></div></div></div><p>
579 This reprograms TeleGPS devices with new firmware. Please
580 read the directions for flashing devices in the Updating
581 Device Firmware chapter below.
582 </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp63308272"></a>Chapter 6. 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="#idp66058400">1.
583 Updating TeleGPS Firmware
584 </a></span></dt></dl></div><p>
585 TeleGPS is programmed directly over its USB connectors.
587 You may wish to begin by ensuring you have current firmware images.
588 These are distributed as part of the TeleGPS software bundle that
589 also includes the TeleGPS ground station program. Newer ground
590 station versions typically work fine with older firmware versions,
591 so you don't need to update your devices just to try out new
592 software features. You can always download the most recent
593 version from <a class="ulink" href="http://www.altusmetrum.org/AltOS/" target="_top">http://www.altusmetrum.org/AltOS/</a>.
594 </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66058400"></a>1.
595 Updating TeleGPS Firmware
596 </h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
597 Attach a battery and power switch to the target
598 device. Power up the device.
599 </p></li><li class="listitem"><p>
600 Using a Micro USB cable, connect the target device to your
601 computer's USB socket.
602 </p></li><li class="listitem"><p>
603 Run TeleGPS, and select 'Flash Device' from the Device menu.
604 </p></li><li class="listitem"><p>
605 Select the target device in the Device Selection dialog.
606 </p></li><li class="listitem"><p>
607 Select the image you want to flash to the device, which
608 should have a name in the form
609 <product>-v<product-version>-<software-version>.ihx, such
610 as TeleGPS-v1.0-1.4.0.ihx.
611 </p></li><li class="listitem"><p>
612 Make sure the configuration parameters are reasonable
613 looking. If the serial number and/or RF configuration
614 values aren't right, you'll need to change them.
615 </p></li><li class="listitem"><p>
616 Hit the 'OK' button and the software should proceed to flash
617 the device with new firmware, showing a progress bar.
618 </p></li><li class="listitem"><p>
619 Verify that the device is working by using the 'Configure
620 Altimeter' item to check over the configuration.
621 </p></li></ol></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp66067760"></a>Chapter 7. Technical Information</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="#idp66068432">1. GPS Receiver</a></span></dt><dt><span class="section"><a href="#idp66071744">2. Micro-controller</a></span></dt><dt><span class="section"><a href="#idp66073072">3. Lithium Polymer Battery</a></span></dt><dt><span class="section"><a href="#idp66074336">4. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#idp66075664">5. On-board data storage</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66068432"></a>1. GPS Receiver</h2></div></div></div><p>
622 TeleGPS uses the u-Blox Max-7Q GPS receiver.
623 </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66071744"></a>2. Micro-controller</h2></div></div></div><p>
624 TeleGPS uses an NXP LPC11U14 micro-controller. This tiny
625 CPU contains 32kB of flash for the application and 4kB of RAM for
626 temporary data storage.
627 </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66073072"></a>3. Lithium Polymer Battery</h2></div></div></div><p>
628 Shipping restrictions may prevent us from including a battery
629 battery with TeleGPS.
630 </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66074336"></a>4. Mechanical Considerations</h2></div></div></div><p>
631 TeleGPS is designed to be rugged enough for typical rocketry
632 applications. The 4 mounting holes on the board are sized for
633 use with 4-40 or M3 screws.
634 </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66075664"></a>5. On-board data storage</h2></div></div></div><p>
635 TeleGPS has 2MB of non-volatile storage, separate from the
636 code storage memory. The TeleGPS firmware uses this to log
637 information during flight.
638 </p></div></div><div class="appendix"><div class="titlepage"><div><div><h1 class="title"><a name="idp66077120"></a>Appendix A. Release Notes</h1></div></div></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66077760"></a>Version 1.41</h2></div></div></div><p>
639 Version 1.4.1 is a minor release. It fixes install issues on
640 Windows and provides the missing TeleMetrum V2.0 firmware. There
641 aren't any changes to the firmware or host applications at
642 all. All Windows users will want to upgrade to get the signed
643 driver, but Mac and Linux users who do not need the TeleMetrum
644 V2.0 firmware image will not need to upgrade.
646 Windows Install Fixes
647 </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
648 Provide signed Windows driver files. This should avoid any need to
649 disable driver signature checking on Windows 7 or 8.
650 </p></li><li class="listitem"><p>
651 Fix Java version detection and download. Previously, the
652 installer would only look for Java 6 or 7 and insist on
653 downloading its own Java bits if there was something else
654 installed. Furthermore, the 64-bit Java link provided didn't
655 work for anyone other than Keith, making it impossible to
656 install AltOS on any machine with Java SE 8 installed.
657 </p></li></ul></div><p>
660 </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
661 Include 1.4 firmware for TeleMetrum V2.0. None of the
662 installers shipped this file. Now it's included in the AltOS
663 packages for Linux, Mac and Windows.
664 </p></li><li class="listitem"><p>
665 Include Google Application Key for map downloading. The 1.4
666 release didn't have this key in the released version of the
667 software, making map downloading fail for most people.
668 </p></li></ul></div><p>
669 </p></div><div class="simplesect"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp66079360"></a>Version 1.4</h2></div></div></div><p>
670 Version 1.4 is a major release. It includes support for our new
671 TeleGPS product, new features and bug fixes in in the flight
672 software for all our boards and the AltosUI ground station
675 </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
676 Add support for TeleGPS boards.
677 </p></li><li class="listitem"><p>
678 Replace the 'dit dit dit' tones at startup with the current
679 battery voltage, measured in tenths of a volt. This lets you
680 check the battery voltage without needing telemetry, which
681 is especially useful on EasyMini.
682 </p></li><li class="listitem"><p>
683 Change state beeping to "Farnsworth spacing", which means
684 they're quite a bit faster than before, and so they take
686 </p></li><li class="listitem"><p>
687 Make the beeper tone configurable, making it possible to
688 distinguish between two Altus Metrum products in the same ebay.
689 </p></li><li class="listitem"><p>
690 Make the firing time for extra pyro channels configurable,
691 allowing longer (or shorter) than the default 50ms. Only relevant
692 for TeleMega at this time.
693 </p></li></ul></div><p>
696 </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
697 Fix bug preventing the selection of the 'Flight State After'
698 mode in pyro configuration.
699 </p></li><li class="listitem"><p>
700 Fix bug where erasing flights would reset the flight number
701 to 2 on TeleMega and TeleMetrum v2.
702 </p></li><li class="listitem"><p>
703 Fix u-Blox GPS driver to mark course and speed data as being
705 </p></li></ul></div><p>
708 </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
709 Add zooming and new content types (terrain and road maps) to
710 map view. Change map storage format from PNG to Jpeg, which
711 saves a huge amount of disk space. You will need to
712 re-download all of your pre-loaded map images.
713 </p></li><li class="listitem"><p>
714 Add a distance measuring device to the maps view. Select
715 this by using any button other than the left one, or by
716 pressing shift or control on the keyboard while using the
718 </p></li><li class="listitem"><p>
719 Add new 'Ignitor' tab to the flight monitor display for
720 TeleMega's extra ignitors.
721 </p></li><li class="listitem"><p>
722 Increase the width of data lines in the graphs to make them
724 </p></li><li class="listitem"><p>
725 Add additional ignitor firing marks and voltages to the
726 graph so you can see when the ignitors fired, along with
727 the ignitor voltages.
728 </p></li><li class="listitem"><p>
729 Add GPS course, ground speed and climb rate as optional
731 </p></li></ul></div><p>
734 </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
735 When flashing new firmware, re-try opening the device as
736 sometimes it takes a while for the underlying operating
737 system to recognize that the device has rebooted in
738 preparation for the flashing operation.
739 </p></li><li class="listitem"><p>
740 Hide Tilt Angle in ascent tab for devices that don't have a gyro.
741 </p></li><li class="listitem"><p>
742 Filter out speed and acceleration spikes caused by ejection
743 charge firing when computing the maximum values. This
744 provides a more accurate reading of those maximums.
745 </p></li><li class="listitem"><p>
746 Fix EasyMini voltage displays. Early EasyMini prototypes
747 used a 3.0V regulator, and AltosUI still used that value as
748 the basis of the computation. Production EasyMini boards
749 have always shipped with a 3.3V regulator. Also, purple
750 EasyMini boards sensed the battery voltage past the blocking
751 diode, resulting in a drop of about 150mV from the true
752 battery voltage. Compensate for that when displaying the
754 </p></li><li class="listitem"><p>
755 Display error message when trying to configure maximum
756 flight log size while the flight computer still has flight
758 </p></li><li class="listitem"><p>
759 Handle TeleMetrum and TeleMini eeprom files generated with
760 pre-1.0 firmware. Those ancient versions didn't report the
761 log format, so just use the product name instead.
762 </p></li></ul></div><p>
765 </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
766 New application designed for use with TeleGPS boards.
767 </p></li><li class="listitem"><p>
768 Shares code with AltosUI, mostly just trimmed down to focus
769 on TeleGPS-related functions.
770 </p></li></ul></div><p>
772 Documentation changes
773 </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
774 Re-create the drill template images; they should print
775 correctly from Firefox at least. Ship these as individual
776 PDF files so they're easy to print.
777 </p></li><li class="listitem"><p>
778 Add a description of the 'Apogee Lockout' setting, which
779 prevents the apogee charge from firing for a configurable
780 amount of time after boost.
781 </p></li></ul></div><p>
782 </p></div></div></div></body></html>
projects / web / altusmetrum / blob