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="idp46686976"></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="idp46615152"></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</td><td align="left">13 June 2014</td></tr><tr><td align="left" colspan="2">
9 </td></tr></table></div></div></div><hr></div><div class="dedication"><div class="titlepage"><div><div><h1 class="title"><a name="idp46618640"></a>Acknowledgements</h1></div></div></div><p>
10 Have fun using these products, and we hope to meet all of you
11 out on the rocket flight line somewhere.
12 </p><div class="literallayout"><p><br>
13 Bdale Garbee, KB0G<br>
14 NAR #87103, TRA #12201<br>
16 Keith Packard, KD7SQG<br>
17 NAR #88757, TRA #12200<br>
19 </p></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="chapter"><a href="#idp46621008">1. Quick Start Guide</a></span></dt><dt><span class="chapter"><a href="#idp47548032">2. Handling Precautions</a></span></dt><dt><span class="chapter"><a href="#idp47550928">3. TeleGPS Hardware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp47551600">1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idp47554528">2. On-board Data Recording</a></span></dt><dt><span class="section"><a href="#idp47558736">3. Installation</a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp51049792">4. System Operation</a></span></dt><dd><dl><dt><span class="section"><a href="#idp51050464">1. GFSK Telemetry</a></span></dt><dt><span class="section"><a href="#idp51053392">2. APRS</a></span></dt><dt><span class="section"><a href="#idp46630992">3. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp46632320">3.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp46634400">3.2. Callsign</a></span></dt><dt><span class="section"><a href="#idp46635584">3.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp46636912">3.4. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp46638416">3.5. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp46640016">3.6. Logging Trigger Motion</a></span></dt><dt><span class="section"><a href="#idp46641344">3.7. Position Reporting Interval</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp46642992">5. TeleGPS Application</a></span></dt><dd><dl><dt><span class="section"><a href="#idp46644576">1. Telemetry Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp46653568">1.1. Map</a></span></dt><dt><span class="section"><a href="#idp52185504">1.2. Location</a></span></dt><dt><span class="section"><a href="#idp52188784">1.3. Status</a></span></dt><dt><span class="section"><a href="#idp52192208">1.4. Table</a></span></dt></dl></dd><dt><span class="section"><a href="#idp52196256">2. TeleGPS Menus</a></span></dt><dd><dl><dt><span class="section"><a href="#idp52204352">2.1. New Window</a></span></dt><dt><span class="section"><a href="#idp52205680">2.2. Graph Data</a></span></dt><dt><span class="section"><a href="#idp52222448">2.3. Export Data</a></span></dt><dt><span class="section"><a href="#idp49177968">2.4. Load Maps</a></span></dt><dt><span class="section"><a href="#idp46577104">2.5. Preferences</a></span></dt><dt><span class="section"><a href="#idp52256288">2.6. Close</a></span></dt><dt><span class="section"><a href="#idp52257552">2.7. Exit</a></span></dt><dt><span class="section"><a href="#idp52258704">2.8. Connect Device</a></span></dt><dt><span class="section"><a href="#idp52262240">2.9. Disconnect</a></span></dt><dt><span class="section"><a href="#idp52263392">2.10. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp52266944">2.11. Download Data</a></span></dt><dt><span class="section"><a href="#idp52270080">2.12. Configure Device</a></span></dt><dt><span class="section"><a href="#idp52293648">2.13. Flash Device</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#idp52295248">6. Updating Device Firmware</a></span></dt><dd><dl><dt><span class="section"><a href="#idp52298048">1.
20 Updating TeleGPS Firmware
21 </a></span></dt></dl></dd><dt><span class="chapter"><a href="#idp52307248">7. Technical Information</a></span></dt><dd><dl><dt><span class="section"><a href="#idp52307888">1. GPS Receiver</a></span></dt><dt><span class="section"><a href="#idp52311232">2. Micro-controller</a></span></dt><dt><span class="section"><a href="#idp52312560">3. Lithium Polymer Battery</a></span></dt><dt><span class="section"><a href="#idp52313824">4. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#idp52315152">5. On-board data storage</a></span></dt></dl></dd></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>4.1. <a href="#idp51056416">Altus Metrum APRS Comments</a></dt></dl></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp46621008"></a>Chapter 1. Quick Start Guide</h1></div></div></div><p>
22 TeleGPS is designed to be easy to use. Requiring no external
23 components, flying takes just a few steps.
25 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
26 you have the right device drivers installed.
28 Next, plug in the battery and USB cable and connect TeleGPS to
29 your computer. This will charge the battery and allow you to
32 Start the TeleGPS application and set the callsign and frequency
33 on your TeleGPS device; refer to the Configure TeleGPS section
34 in the TeleGPS Application chapter for instructions.
36 Unplug TeleGPS when the battery charger light goes green. This
37 will enable the radio and logging portions of the TeleGPS
40 Connect TeleDongle to your computer and start TeleGPS or start
41 AltosDroid on your android device and connect to TeleBT. Set the
42 frequency to match the TeleGPS and you should be receiving telemetry.
43 </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp47548032"></a>Chapter 2. Handling Precautions</h1></div></div></div><p>
44 All Altus Metrum products are sophisticated electronic devices.
45 When handled gently and properly installed in an air-frame, they
46 will deliver impressive results. However, as with all electronic
47 devices, there are some precautions you must take.
49 The Lithium polymer batteries have an
50 extraordinary power density. This is great because we can fly with
51 much less battery mass... but if they are punctured
52 or their contacts are allowed to short, they can and will release their
54 Thus we recommend that you take some care when handling TeleGPS
55 to keep conductive material from coming in contact with the exposed metal elements.
57 As with all other rocketry electronics, Altus Metrum devices must
58 be protected from exposure to corrosive motor exhaust and ejection
60 </p></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp47550928"></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="#idp47551600">1. Hooking Up Lithium Polymer Batteries</a></span></dt><dt><span class="section"><a href="#idp47554528">2. On-board Data Recording</a></span></dt><dt><span class="section"><a href="#idp47558736">3. Installation</a></span></dt></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp47551600"></a>1. Hooking Up Lithium Polymer Batteries</h2></div></div></div><p>
61 TeleGPS has a two pin JST PH series connector to connect up
62 a single-cell Lithium Polymer cell (3.7V nominal). You can
63 purchase matching batteries from the Altus Metrum store, or
64 other vendors, or you can make your own. Pin 1 of the
65 connector is positive, pin 2 is negative. Spark Fun sells a
66 cable with the connector attached, which they call a <a class="ulink" href="https://www.sparkfun.com/products/9914" target="_top">JST Jumper 2
69 Many RC vendors also sell lithium polymer batteries with
70 this same connector. All that we have found use the opposite
71 polarity, and if you use them that way, you will damage or
73 </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp47554528"></a>2. On-board Data Recording</h2></div></div></div><p>
74 TeleGPS logs GPS data at a user-configurable rate. Data are
75 logged to a 2MB on-board flash memory part, which can be
76 partitioned into several equal-sized blocks, one for each
77 flight. 64kB of this storage are reserved to hold
78 configuration data, leaving 1984kB for flight data.
80 The on-board flash is partitioned into separate flight logs,
81 each of a fixed maximum size. Increase the maximum size of
82 each log and you reduce the number of flights that can be
83 stored. Decrease the size and you can store more flights.
85 To compute the amount of space needed for a single log, you
86 can divide the expected time (in seconds) by the sample period
87 (by default, 1 second per sample) and then multiply the result
88 by 32 bytes per sample. For instance, a sample period of 1
89 second and a flight lasting one hour will take 32 * 3600 =
90 115200 bytes. TeleGPS does try to reduce log space used by not
91 recording position information when it isn't moving, so actual
92 space consumed may be less than this.
94 The default size allows for four flights of 496kB each, which
95 provides over four hours of logging at 1 sample per second.
97 TeleGPS will not overwrite existing flight data, so be sure to
98 download flight data and erase it from the onboard flash
99 before it fills up. TeleGPS will still report telemetry even
100 if memory is full, so the only thing you will lose is the
102 </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp47558736"></a>3. Installation</h2></div></div></div><p>
103 The battery connectors are a standard 2-pin JST connector and
104 match batteries sold by Spark Fun. These batteries are
105 single-cell Lithium Polymer batteries that nominally provide 3.7
106 volts. Other vendors sell similar batteries for RC aircraft
107 using mating connectors, however the polarity for those is
108 generally reversed from the batteries used by Altus Metrum
109 products. In particular, the Tenergy batteries supplied for use
110 in Featherweight flight computers are not compatible with Altus
111 Metrum flight computers or battery chargers. <span class="emphasis"><em>Check
112 polarity and voltage before connecting any battery not purchased
113 from Altus Metrum or Spark Fun.</em></span>
115 TeleGPS uses an integrate GPS patch antenna and won't
116 receive GPS signals if installed inside a metal or carbon
117 fiber compartment. Test GPS reception and telemetry
118 transmission with the system installed and all other
119 electronics powered up to verify signal reception and make
120 sure there isn't any interference from other systems.
121 </p></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp51049792"></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="#idp51050464">1. GFSK Telemetry</a></span></dt><dt><span class="section"><a href="#idp51053392">2. APRS</a></span></dt><dt><span class="section"><a href="#idp46630992">3. Configurable Parameters</a></span></dt><dd><dl><dt><span class="section"><a href="#idp46632320">3.1. Radio Frequency</a></span></dt><dt><span class="section"><a href="#idp46634400">3.2. Callsign</a></span></dt><dt><span class="section"><a href="#idp46635584">3.3. Telemetry/RDF/APRS Enable</a></span></dt><dt><span class="section"><a href="#idp46636912">3.4. APRS Interval</a></span></dt><dt><span class="section"><a href="#idp46638416">3.5. Maximum Flight Log</a></span></dt><dt><span class="section"><a href="#idp46640016">3.6. Logging Trigger Motion</a></span></dt><dt><span class="section"><a href="#idp46641344">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="idp51050464"></a>1. GFSK Telemetry</h2></div></div></div><p>
122 TeleGPS's native telemetry system doesn't use a 'normal packet
123 radio' mode like APRS because it's not very efficient. The
124 GFSK modulation we use is FSK with the base-band pulses passed
125 through a Gaussian filter before they go into the modulator to
126 limit the transmitted bandwidth. When combined with forward
127 error correction and interleaving, this allows us to have a
128 very robust 19.2 kilobit data link with only 10-40 milliwatts
129 of transmit power, a whip antenna in the rocket, and a
130 hand-held Yagi on the ground. We've had flights to above 21k
131 feet AGL with great reception, and calculations suggest we
132 should be good to well over 40k feet AGL with a 5-element yagi
133 on the ground with our 10mW units and over 100k feet AGL with
135 </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp51053392"></a>2. APRS</h2></div></div></div><p>
136 TeleGPS can send APRS if desired, and the
137 interval between APRS packets can be configured. As each APRS
138 packet takes a full second to transmit, we recommend an
139 interval of at least 5 seconds to avoid consuming too much
140 battery power or radio channel bandwidth. You can configure
141 the APRS interval using AltosUI; that process is described in
142 the Configure Altimeter section of the AltosUI chapter.
144 AltOS uses the APRS compressed position report data format,
145 which provides for higher position precision and shorter
146 packets than the original APRS format. It also includes
147 altitude data, which is invaluable when tracking rockets. We
148 haven't found a receiver which doesn't handle compressed
149 positions, but it's just possible that you have one, so if you
150 have an older device that can receive the raw packets but
151 isn't displaying position information, it's possible that this
154 The APRS packet format includes a comment field that can have
155 arbitrary text in it. AltOS uses this to send status
156 information about the flight computer. It sends four fields as
157 shown in the following table.
158 </p><div class="table"><a name="idp51056416"></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>
159 Here's an example of an APRS comment showing GPS lock with 6
160 satellites in view and a battery at 4.0V.
161 </p><pre class="screen">
165 Make sure your primary battery is above 3.8V and GPS is locked
166 with at least 5 or 6 satellites in view before starting. If GPS
167 is switching between L and U regularly, then it doesn't have a
168 good lock and you should wait until it becomes stable.
170 If the GPS receiver loses lock, the APRS data transmitted will
171 contain the last position for which GPS lock was
172 available. You can tell that this has happened by noticing
173 that the GPS status character switches from 'L' to 'U'. Before
174 GPS has locked, APRS will transmit zero for latitude,
175 longitude and altitude.
176 </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp46630992"></a>3. Configurable Parameters</h2></div></div></div><p>
177 Configuring TeleGPS is very
178 simple; the few configurable parameters can all be set
179 using the TeleGPS application over USB. Read
180 the Configure TeleGPS section in the TeleGPS Software chapter below
181 for more information.
182 </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp46632320"></a>3.1. Radio Frequency</h3></div></div></div><p>
183 Altus Metrum boards support radio frequencies in the 70cm
184 band. By default, the configuration interface provides a
185 list of 10 “standard” frequencies in 100kHz channels starting at
186 434.550MHz. However, the firmware supports use of
187 any 50kHz multiple within the 70cm band. At any given
188 launch, we highly recommend coordinating when and by whom each
189 frequency will be used to avoid interference. And of course, both
190 TeleGPS and the receiver must be configured to the same
191 frequency to successfully communicate with each other.
192 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp46634400"></a>3.2. Callsign</h3></div></div></div><p>
193 This sets the callsign used for telemetry and APRS to
195 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp46635584"></a>3.3. Telemetry/RDF/APRS Enable</h3></div></div></div><p>
196 You can completely disable the radio, if necessary, leaving
197 TeleGPS only logging data to internal memory.
198 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp46636912"></a>3.4. APRS Interval</h3></div></div></div><p>
199 This selects how often APRS packets are transmitted. Set
200 this to zero to disable APRS without also disabling the
201 regular telemetry and RDF transmissions. As APRS takes a
202 full second to transmit a single position report, we
203 recommend sending packets no more than once every 5 seconds.
204 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp46638416"></a>3.5. Maximum Flight Log</h3></div></div></div><p>
205 Changing this value will set the maximum amount of flight
206 log storage that an individual flight will use. The
207 available storage is divided into as many flights of the
208 specified size as can fit in the available space. You can
209 download and erase individual flight logs. If you fill up
210 the available storage, future flights will not get logged
211 until you erase some of the stored ones.
212 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp46640016"></a>3.6. Logging Trigger Motion</h3></div></div></div><p>
213 If TeleGPS moves less than this distance over a long period
214 of time, it will not log that location, saving storage space.
215 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp46641344"></a>3.7. Position Reporting Interval</h3></div></div></div><p>
216 This sets how often TeleGPS reports position information via
217 telemetry and to the on-board log. Reducing this value will
218 save power and logging memory consumption.
219 </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp46642992"></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="#idp46644576">1. Telemetry Monitoring</a></span></dt><dd><dl><dt><span class="section"><a href="#idp46653568">1.1. Map</a></span></dt><dt><span class="section"><a href="#idp52185504">1.2. Location</a></span></dt><dt><span class="section"><a href="#idp52188784">1.3. Status</a></span></dt><dt><span class="section"><a href="#idp52192208">1.4. Table</a></span></dt></dl></dd><dt><span class="section"><a href="#idp52196256">2. TeleGPS Menus</a></span></dt><dd><dl><dt><span class="section"><a href="#idp52204352">2.1. New Window</a></span></dt><dt><span class="section"><a href="#idp52205680">2.2. Graph Data</a></span></dt><dt><span class="section"><a href="#idp52222448">2.3. Export Data</a></span></dt><dt><span class="section"><a href="#idp49177968">2.4. Load Maps</a></span></dt><dt><span class="section"><a href="#idp46577104">2.5. Preferences</a></span></dt><dt><span class="section"><a href="#idp52256288">2.6. Close</a></span></dt><dt><span class="section"><a href="#idp52257552">2.7. Exit</a></span></dt><dt><span class="section"><a href="#idp52258704">2.8. Connect Device</a></span></dt><dt><span class="section"><a href="#idp52262240">2.9. Disconnect</a></span></dt><dt><span class="section"><a href="#idp52263392">2.10. Scan Channels</a></span></dt><dt><span class="section"><a href="#idp52266944">2.11. Download Data</a></span></dt><dt><span class="section"><a href="#idp52270080">2.12. Configure Device</a></span></dt><dt><span class="section"><a href="#idp52293648">2.13. Flash Device</a></span></dt></dl></dd></dl></div><p>
220 The TeleGPS application provides a graphical user interface for
221 interacting with the Altus Metrum product family. TeleGPS can
222 monitor telemetry data, configure devices and many other
223 tasks. The primary interface window is for displaying data
224 received over the telemetry link. There are additional
225 tasks available from the main window menu bar. This chapter
226 is split into sections, each of which documents one of the tasks
227 provided from the top-level toolbar.
228 </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp46644576"></a>1. Telemetry Monitoring</h2></div></div></div><p>
229 This is the window brought up when you start the
230 application. If you have a TeleDongle device connected to the
231 computer, it will automatically be selected for telemetry monitoring
233 All telemetry data received are automatically recorded in
234 suitable log files. The name of the files includes the current
235 date and TeleGPS serial and flight numbers.
237 The radio frequency being monitored by the TeleDongle device
238 is displayed at the top of the window. You can configure the
239 frequency by clicking on the frequency box and selecting the
240 desired frequency. The TeleGPS application remembers the last
241 frequency selected for each TeleDongle and selects that
242 automatically the next time you use that device.
244 Below the TeleDongle frequency selector, the window contains a few
245 significant pieces of information about the altimeter providing
246 the telemetry data stream:
247 </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
249 </p></li><li class="listitem"><p>
250 The Received Signal Strength Indicator value. This lets
251 you know how strong a signal TeleDongle is receiving. The
252 radio inside TeleDongle operates down to about -100dBm;
253 weaker signals may not be receivable. The packet link uses
254 error detection and correction techniques which prevent
255 incorrect data from being reported.
256 </p></li><li class="listitem"><p>
257 The age of the displayed data, in seconds since the last
258 successfully received telemetry packet. In normal operation
259 this will stay in the low single digits. If the number starts
260 counting up, then you are no longer receiving data over the radio
261 link from the flight computer.
262 </p></li></ul></div><p>
263 Finally, the largest portion of the window contains a set of
264 tabs, each of which contain some information about the TeleGPS
265 board. The final 'table' tab displays many of the raw telemetry
266 values in one place in a spreadsheet-like format.
267 </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp46653568"></a>1.1. Map</h3></div></div></div><p>
268 The Map tab shows the TeleGPS track over time on top of map
269 data making it easy to locate the device.
270 </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>
271 The map's default scale is approximately 3m (10ft) per pixel. The map
272 can be dragged using the left mouse button. The map will attempt
273 to keep the rocket roughly centered while data is being received.
275 You can adjust the style of map and the zoom level with
276 buttons on the right side of the map window. You can draw a
277 line on the map by moving the mouse over the map with a
278 button other than the left one pressed, or by pressing the
279 left button while also holding down the shift key. The
280 length of the line in real-world units will be shown at the
283 Images are fetched automatically via the Google Maps Static API,
284 and cached on disk for reuse. If map images cannot be downloaded,
285 the rocket's path will be traced on a dark gray background
288 You can pre-load images for your favorite launch sites
289 before you leave home; check out the 'Preload Maps' section below.
290 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp52185504"></a>1.2. Location</h3></div></div></div><p>
291 The Location tab shows the raw GPS data received from TeleGPS.
292 </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="idp52188784"></a>1.3. Status</h3></div></div></div><p>
293 The Status tab shows data relative to the location of
294 TeleGPS when the application first received telemetry from
296 </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="idp52192208"></a>1.4. Table</h3></div></div></div><p>
297 The Table tab shows detailed information about the GPS
299 </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="idp52196256"></a>2. TeleGPS Menus</h2></div></div></div><p>
300 TeleGPS has three or four menus at the top of the window:
301 </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">File</span></dt><dd><p>
302 New Window, Graph Data, Export Data, Load Maps, Preferences, Close and Exit
303 </p></dd><dt><span class="term">Monitor</span></dt><dd><p>
304 Connect Device, Disconnect and Scan Channels
305 </p></dd><dt><span class="term">Device</span></dt><dd><p>
306 Download Data, Configure Device and Flash Device
307 </p></dd><dt><span class="term">Frequency</span></dt><dd><p>
308 This shows the current monitoring frequency with a
309 drop-down menu listing other configured
310 frequencies. You can change the set of frequencies
311 shown here from the Preferences dialog. This menu is
312 only shown when the TeleGPS application is connected
313 to a TeleDongle or TeleBT device.
314 </p></dd></dl></div><p>
315 </p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp52204352"></a>2.1. New Window</h3></div></div></div><p>
316 This creates another telemetry monitoring window, in case
317 you have multiple TeleDongle devices connected to the
319 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp52205680"></a>2.2. Graph Data</h3></div></div></div><p>
320 This brings up a file dialog to load a saved log, either
321 a .telem file of recorded telemetry or .eeprom of saved
322 data from on-board memory. It looks a bit like the flight
323 monitoring window, using a selection of tabs to show
324 different views of the saved data.
325 </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp52207024"></a>2.2.1. Graph</h4></div></div></div><p>
326 The Graph tab shows a plot of the the GPS data
327 collected. The X axis is time in seconds; there are a
328 variety of Y axes available for different kinds of data.
329 </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="idp52210928"></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>
330 This selects which graph elements to show, and, at the
331 bottom, lets you switch between metric and imperial units
332 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp52214704"></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>
333 Shows overall data computed from the flight.
334 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp52218320"></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>
335 Shows a map of the area overlaid with the GPS track. As with
336 the telemetry monitoring window, you can select the style
337 of map and zoom level using buttons along the side;
338 you can scroll the map by dragging within the map pressing
339 the left button and you can draw a line to measure
340 distances using either the left button with the shift key,
342 </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp52222448"></a>2.3. Export Data</h3></div></div></div><p>
343 This tool takes the raw data files and makes them available for
344 external analysis. When you select this button, you are prompted to
345 select a data file, which can be either a .eeprom or .telem.
346 The .eeprom files contain higher resolution and more continuous data,
347 while .telem files contain receiver signal strength information.
348 Next, a second dialog appears which is used to select
349 where to write the resulting file. It has a selector to choose
350 between CSV and KML file formats.
351 </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp50348192"></a>2.3.1. Comma Separated Value Format</h4></div></div></div><p>
352 This is a text file containing the data in a form suitable for
353 import into a spreadsheet or other external data analysis
354 tool. The first few lines of the file contain the version and
355 configuration information from TeleGPS, then
356 there is a single header line which labels all of the
357 fields. All of these lines start with a '#' character which
358 many tools can be configured to skip over.
360 The remaining lines of the file contain the data, with each
361 field separated by a comma and at least one space. All of
362 the sensor values are converted to standard units, with the
363 barometric data reported in both pressure, altitude and
364 height above pad units.
365 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp49665296"></a>2.3.2. Keyhole Markup Language (for Google Earth)</h4></div></div></div><p>
366 This is the format used by Google Earth to provide an overlay
367 within that application. With this, you can use Google Earth to
368 see the whole flight path in 3D.
369 </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp49177968"></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>
370 Before using TeleGPS, you can use Load Maps to load map data
371 in case you don't have access to the internet while
374 There's a drop-down menu of rocket launch sites we know
375 about; if your favorites aren't there, please let us know
376 the lat/lon and name of the site. The contents of this list
377 are actually downloaded from our server at run-time, so as
378 new sites are sent in, they'll get automatically added to
379 this list. If the launch site isn't in the list, you can
380 manually enter the lat/lon values
382 There are four different kinds of maps you can view; you can
383 select which to download by selecting as many as you like from
385 </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Hybrid</span></dt><dd><p>
386 A combination of satellite imagery and road data. This
388 </p></dd><dt><span class="term">Satellite</span></dt><dd><p>
389 Just the satellite imagery without any annotation.
390 </p></dd><dt><span class="term">Roadmap</span></dt><dd><p>
391 Roads, political boundaries and a few geographic features.
392 </p></dd><dt><span class="term">Terrain</span></dt><dd><p>
393 Contour intervals and shading that show hills and
395 </p></dd></dl></div><p>
397 You can specify the range of zoom levels to download; smaller
398 numbers show more area with less resolution. The default
399 level, 0, shows about 3m/pixel. One zoom level change
400 doubles or halves that number.
402 The Tile Radius value sets how large an area around the center
403 point to download. Each tile is 512x512 pixels, and the
404 'radius' value specifies how many tiles away from the center
405 will be downloaded. Specify a radius of 0 and you get only the
406 center tile. A radius of 1 loads a 3x3 grid, centered on the
409 Clicking the 'Load Map' button will fetch images from Google
410 Maps; note that Google limits how many images you can fetch at
411 once, so if you load more than one launch site, you may get
412 some gray areas in the map which indicate that Google is tired
413 of sending data to you. Try again later.
414 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp46577104"></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="idp46580240"></a>2.5.1. Voice Settings</h4></div></div></div><p>
415 AltosUI provides voice announcements during flight so that you
416 can keep your eyes on the sky and still get information about
417 the current flight status. However, sometimes you don't want
419 </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>
420 Plays a short message allowing you to verify
421 that the audio system is working and the volume settings
423 </p></dd></dl></div></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp52244720"></a>2.5.2. Log Directory</h4></div></div></div><p>
424 AltosUI logs all telemetry data and saves all TeleMetrum flash
425 data to this directory. This directory is also used as the
426 staring point when selecting data files for display or export.
428 Click on the directory name to bring up a directory choosing
429 dialog, select a new directory and click 'Select Directory' to
430 change where AltosUI reads and writes data files.
431 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp52246752"></a>2.5.3. Callsign</h4></div></div></div><p>
432 This value is transmitted in each command packet sent from
433 TeleDongle and received from an altimeter. It is not used in
434 telemetry mode, as the callsign configured in the altimeter board
435 is included in all telemetry packets. Configure this
436 with the AltosUI operators call sign as needed to comply with
437 your local radio regulations.
439 Note that to successfully command a flight computer over the radio
440 (to configure the altimeter, monitor idle, or fire pyro charges),
441 the callsign configured here must exactly match the callsign
442 configured in the flight computer. This matching is case
444 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp52249024"></a>2.5.4. Imperial Units</h4></div></div></div><p>
445 This switches between metric units (meters) and imperial
446 units (feet and miles). This affects the display of values
447 use during flight monitoring, configuration, data graphing
448 and all of the voice announcements. It does not change the
449 units used when exporting to CSV files, those are always
450 produced in metric units.
451 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp52250544"></a>2.5.5. Serial Debug</h4></div></div></div><p>
452 This causes all communication with a connected device to be
453 dumped to the console from which AltosUI was started. If
454 you've started it from an icon or menu entry, the output
455 will simply be discarded. This mode can be useful to debug
456 various serial communication issues.
457 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp52252048"></a>2.5.6. Font Size</h4></div></div></div><p>
458 Selects the set of fonts used in the flight monitor
459 window. Choose between the small, medium and large sets.
460 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp52253344"></a>2.5.7. Look & Feel</h4></div></div></div><p>
461 Adjust the style of the windows. By default, the TeleGPS
462 application attempts to blend in with the native style.
463 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp52254640"></a>2.5.8. Manage Frequencies</h4></div></div></div><p>
464 This brings up a dialog where you can configure the set of
465 frequencies shown in the various frequency menus. You can
466 add as many as you like, or even reconfigure the default
467 set. Changing this list does not affect the frequency
468 settings of any devices, it only changes the set of
469 frequencies shown in the menus.
470 </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp52256288"></a>2.6. Close</h3></div></div></div><p>
471 This closes the current window, leaving any other windows
472 open and the application running.
473 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp52257552"></a>2.7. Exit</h3></div></div></div><p>
474 This closes all TeleGPS windows and terminates the application.
475 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp52258704"></a>2.8. Connect Device</h3></div></div></div><p>
476 Selecting this item brings up a dialog box listing all of
477 the connected TeleDongle devices. When you choose one of
478 these, AltosUI will display telemetry data as received by
479 the selected TeleDongle device.
480 </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="idp52262240"></a>2.9. Disconnect</h3></div></div></div><p>
481 Disconnects the currently connected TeleDongle or TeleBT
482 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp52263392"></a>2.10. Scan Channels</h3></div></div></div><p>
483 Scans the configured set of frequencies looking for
484 telemetry signals. A list of all of the discovered signals
485 is show; selecting one of those and clicking on 'Monitor'
486 will select that frequency in the associated TeleGPS
488 </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="idp52266944"></a>2.11. Download Data</h3></div></div></div><p>
489 TeleGPS records data to its internal flash memory.
490 On-board data is recorded at the same rate as telemetry
491 but is not subject to radio drop-outs. As
492 such, it generally provides a more complete and precise record.
493 The 'Download Data' menu entry allows you to read the
494 flash memory and write it to disk.
496 Select the 'Download Data' menu entry to bring up a list of
497 connected TeleGPS devices. After the device has been
498 selected, a dialog showing the data stored in the
499 device will be shown allowing you to select which entries to
500 download and which to delete. You must erase flights in order for the space they
501 consume to be reused by another track. This prevents
502 accidentally losing data if you neglect to download
503 data before starting TeleGPS again. Note that if there is no more
504 space available in the device, then no data will be recorded.
506 The file name for each data log is computed automatically
507 from the recorded date, altimeter serial number and flight
509 </p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp52270080"></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>
510 Select this button and then select any connected TeleGPS
511 device from the list provided.
513 The first few lines of the dialog provide information about the
514 connected device, including the product name,
515 software version and hardware serial number. Below that are the
516 individual configuration entries.
518 At the bottom of the dialog, there are four buttons:
519 </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Save</span></dt><dd><p>
520 This writes any changes to the
521 configuration parameter block in flash memory. If you don't
522 press this button, any changes you make will be lost.
523 </p></dd><dt><span class="term">Reset</span></dt><dd><p>
524 This resets the dialog to the most recently saved values,
525 erasing any changes you have made.
526 </p></dd><dt><span class="term">Reboot</span></dt><dd><p>
527 This reboots the device. This will restart logging for
528 a new flight number, if any log information has been
529 saved for the current flight.
530 </p></dd><dt><span class="term">Close</span></dt><dd><p>
531 This closes the dialog. Any unsaved changes will be
533 </p></dd></dl></div><p>
534 The rest of the dialog contains the parameters to be configured.
535 </p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp52282032"></a>2.12.1. Frequency</h4></div></div></div><p>
536 This configures which of the frequencies to use for both
537 telemetry and packet command mode. Note that if you set this
538 value via packet command mode, the TeleDongle frequency will
539 also be automatically reconfigured to match so that
540 communication will continue afterwards.
541 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp52283536"></a>2.12.2. RF Calibration</h4></div></div></div><p>
542 The radios in every Altus Metrum device are calibrated at the
543 factory to ensure that they transmit and receive on the
544 specified frequency. If you need to you can adjust the calibration
545 by changing this value. Do not do this without understanding what
546 the value means, read the appendix on calibration and/or the source
547 code for more information. To change a TeleDongle's calibration,
548 you must reprogram the unit completely.
549 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp52285200"></a>2.12.3. Telemetry/RDF/APRS Enable</h4></div></div></div><p>
550 Enables the radio for transmission during flight. When
551 disabled, the radio will not transmit anything during flight
553 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp52286512"></a>2.12.4. APRS Interval</h4></div></div></div><p>
554 How often to transmit GPS information via APRS (in
555 seconds). When set to zero, APRS transmission is
556 disabled. This option is available on TeleMetrum v2 and
557 TeleMega boards. TeleMetrum v1 boards cannot transmit APRS
558 packets. Note that a single APRS packet takes nearly a full
559 second to transmit, so enabling this option will prevent
560 sending any other telemetry during that time.
561 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp52288096"></a>2.12.5. Callsign</h4></div></div></div><p>
562 This sets the call sign included in each telemetry packet. Set this
563 as needed to conform to your local radio regulations.
564 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp52289424"></a>2.12.6. Maximum Log Size</h4></div></div></div><p>
565 This sets the space (in kilobytes) allocated for each data
566 log. The available space will be divided into chunks of this
567 size. A smaller value will allow more logs to be stored,
568 a larger value will record data for longer times.
569 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp52290864"></a>2.12.7. Logging Trigger Motion</h4></div></div></div><p>
570 If TeleGPS moves less than this distance over a long period
571 of time, it will not log that location, saving storage space.
572 </p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="idp52292176"></a>2.12.8. Position Reporting Interval</h4></div></div></div><p>
573 This sets how often TeleGPS reports position information via
574 telemetry and to the on-board log. Reducing this value will
575 save power and logging memory consumption.
576 </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="idp52293648"></a>2.13. Flash Device</h3></div></div></div><p>
577 This reprograms TeleGPS devices with new firmware. Please
578 read the directions for flashing devices in the Updating
579 Device Firmware chapter below.
580 </p></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp52295248"></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="#idp52298048">1.
581 Updating TeleGPS Firmware
582 </a></span></dt></dl></div><p>
583 TeleGPS is programmed directly over its USB connectors.
585 You may wish to begin by ensuring you have current firmware images.
586 These are distributed as part of the TeleGPS software bundle that
587 also includes the TeleGPS ground station program. Newer ground
588 station versions typically work fine with older firmware versions,
589 so you don't need to update your devices just to try out new
590 software features. You can always download the most recent
591 version from <a class="ulink" href="http://www.altusmetrum.org/AltOS/" target="_top">http://www.altusmetrum.org/AltOS/</a>.
592 </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp52298048"></a>1.
593 Updating TeleGPS Firmware
594 </h2></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
595 Attach a battery and power switch to the target
596 device. Power up the device.
597 </p></li><li class="listitem"><p>
598 Using a Micro USB cable, connect the target device to your
599 computer's USB socket.
600 </p></li><li class="listitem"><p>
601 Run TeleGPS, and select 'Flash Device' from the Device menu.
602 </p></li><li class="listitem"><p>
603 Select the target device in the Device Selection dialog.
604 </p></li><li class="listitem"><p>
605 Select the image you want to flash to the device, which
606 should have a name in the form
607 <product>-v<product-version>-<software-version>.ihx, such
608 as TeleGPS-v1.0-1.4.0.ihx.
609 </p></li><li class="listitem"><p>
610 Make sure the configuration parameters are reasonable
611 looking. If the serial number and/or RF configuration
612 values aren't right, you'll need to change them.
613 </p></li><li class="listitem"><p>
614 Hit the 'OK' button and the software should proceed to flash
615 the device with new firmware, showing a progress bar.
616 </p></li><li class="listitem"><p>
617 Verify that the device is working by using the 'Configure
618 Altimeter' item to check over the configuration.
619 </p></li></ol></div></div></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="idp52307248"></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="#idp52307888">1. GPS Receiver</a></span></dt><dt><span class="section"><a href="#idp52311232">2. Micro-controller</a></span></dt><dt><span class="section"><a href="#idp52312560">3. Lithium Polymer Battery</a></span></dt><dt><span class="section"><a href="#idp52313824">4. Mechanical Considerations</a></span></dt><dt><span class="section"><a href="#idp52315152">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="idp52307888"></a>1. GPS Receiver</h2></div></div></div><p>
620 TeleGPS uses the u-Blox Max-7Q GPS receiver.
621 </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp52311232"></a>2. Micro-controller</h2></div></div></div><p>
622 TeleGPS uses an NXP LPC11U14 micro-controller. This tiny
623 CPU contains 32kB of flash for the application and 4kB of RAM for
624 temporary data storage.
625 </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp52312560"></a>3. Lithium Polymer Battery</h2></div></div></div><p>
626 Shipping restrictions may prevent us from including a battery
627 battery with TeleGPS.
628 </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp52313824"></a>4. Mechanical Considerations</h2></div></div></div><p>
629 TeleGPS is designed to be rugged enough for typical rocketry
630 applications. The 4 mounting holes on the board are sized for
631 use with 4-40 or M3 screws.
632 </p></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="idp52315152"></a>5. On-board data storage</h2></div></div></div><p>
633 TeleGPS has 2MB of non-volatile storage, separate from the
634 code storage memory. The TeleGPS firmware uses this to log
635 information during flight.
636 </p></div></div></div></body></html>
projects / web / altusmetrum / blob