5 <meta http-equiv="X-UA-Compatible" content="IE=edge">
6 <meta name="viewport" content="width=device-width, initial-scale=1.0">
7 <meta name="generator" content="Asciidoctor 2.0.18">
8 <meta name="author" content="Keith Packard, Bdale Garbee">
9 <meta name="copyright" content="Bdale Garbee and Keith Packard 2022">
10 <title>TeleGPS Owner’s Manual</title>
11 <link rel="stylesheet" href="./am.css">
15 <h1>TeleGPS Owner’s Manual</h1>
17 <span id="author" class="author">Keith Packard</span><br>
18 <span id="email" class="email"><a href="mailto:keithp@keithp.com">keithp@keithp.com</a></span><br>
19 <span id="author2" class="author">Bdale Garbee</span><br>
20 <span id="email2" class="email"><a href="mailto:bdale@gag.com">bdale@gag.com</a></span><br>
21 <span id="revnumber">version v1.9.13,</span>
22 <span id="revdate">19 Jan 2023</span>
24 <div id="toc" class="toc">
25 <div id="toctitle">Table of Contents</div>
26 <ul class="sectlevel1">
27 <li><a href="#_license">License</a></li>
28 <li><a href="#_acknowledgments">Acknowledgments</a></li>
29 <li><a href="#_telegps_quick_start_guide">1. TeleGPS Quick Start Guide</a></li>
30 <li><a href="#_using_telegps_hardware">2. Using TeleGPS Hardware</a>
31 <ul class="sectlevel2">
32 <li><a href="#_hooking_up_lithium_polymer_batteries">2.1. Hooking Up Lithium Polymer Batteries</a></li>
33 <li><a href="#_on_board_data_recording">2.2. On-board Data Recording</a></li>
34 <li><a href="#_leds">2.3. LEDs</a></li>
35 <li><a href="#_installation">2.4. Installation</a></li>
38 <li><a href="#_telegps_application">3. TeleGPS Application</a>
39 <ul class="sectlevel2">
40 <li><a href="#_telemetry_monitoring">3.1. Telemetry Monitoring</a></li>
41 <li><a href="#_telegps_menus">3.2. TeleGPS Menus</a></li>
42 <li><a href="#_graph_data">3.3. Graph Data</a></li>
43 <li><a href="#_export_data">3.4. Export Data</a></li>
44 <li><a href="#_load_maps">3.5. Load Maps</a></li>
45 <li><a href="#_preferences">3.6. Preferences</a></li>
46 <li><a href="#_close">3.7. Close</a></li>
47 <li><a href="#_exit">3.8. Exit</a></li>
48 <li><a href="#_connect_device">3.9. Connect Device</a></li>
49 <li><a href="#_disconnect">3.10. Disconnect</a></li>
50 <li><a href="#_scan_channels">3.11. Scan Channels</a></li>
51 <li><a href="#_download_data">3.12. Download Data</a></li>
52 <li><a href="#_configure_device">3.13. Configure Device</a></li>
53 <li><a href="#_flash_device">3.14. Flash Device</a></li>
56 <li><a href="#_telegps_system_operation">Appendix A: TeleGPS System Operation</a>
57 <ul class="sectlevel2">
58 <li><a href="#_gfsk_telemetry">A.1. GFSK Telemetry</a></li>
59 <li><a href="#_aprs">A.2. APRS</a></li>
60 <li><a href="#_configurable_parameters">A.3. Configurable Parameters</a></li>
63 <li><a href="#_handling_precautions">Appendix B: Handling Precautions</a></li>
64 <li><a href="#_technical_information">Appendix C: Technical Information</a>
65 <ul class="sectlevel2">
66 <li><a href="#_gps_receiver">C.1. GPS Receiver</a></li>
67 <li><a href="#_70cm_transmitter">C.2. 70cm Transmitter</a></li>
68 <li><a href="#_micro_controller">C.3. Micro-controller</a></li>
69 <li><a href="#_lithium_polymer_battery">C.4. Lithium Polymer Battery</a></li>
70 <li><a href="#_mechanical_considerations">C.5. Mechanical Considerations</a></li>
71 <li><a href="#_on_board_data_storage">C.6. On-board data storage</a></li>
74 <li><a href="#_updating_device_firmware">Appendix D: Updating Device Firmware</a>
75 <ul class="sectlevel2">
76 <li><a href="#_updating_telegps_firmware">D.1. Updating TeleGPS Firmware</a></li>
79 <li><a href="#_release_notes">Appendix E: Release Notes</a>
80 <ul class="sectlevel2">
81 <li><a href="#_release_notes_for_version_1_9_13">E.1. Release Notes for Version 1.9.13</a></li>
82 <li><a href="#_release_notes_for_version_1_9_12">E.2. Release Notes for Version 1.9.12</a></li>
83 <li><a href="#_release_notes_for_version_1_9_11">E.3. Release Notes for Version 1.9.11</a></li>
84 <li><a href="#_release_notes_for_version_1_9_10">E.4. Release Notes for Version 1.9.10</a></li>
85 <li><a href="#_release_notes_for_version_1_9_9">E.5. Release Notes for Version 1.9.9</a></li>
86 <li><a href="#_release_notes_for_version_1_9_8">E.6. Release Notes for Version 1.9.8</a></li>
87 <li><a href="#_release_notes_for_version_1_9_7">E.7. Release Notes for Version 1.9.7</a></li>
88 <li><a href="#_release_notes_for_version_1_9_6">E.8. Release Notes for Version 1.9.6</a></li>
89 <li><a href="#_release_notes_for_version_1_9_5">E.9. Release Notes for Version 1.9.5</a></li>
90 <li><a href="#_release_notes_for_version_1_9_4">E.10. Release Notes for Version 1.9.4</a></li>
91 <li><a href="#_release_notes_for_version_1_9_3">E.11. Release Notes for Version 1.9.3</a></li>
92 <li><a href="#_release_notes_for_version_1_9_1">E.12. Release Notes for Version 1.9.1</a></li>
93 <li><a href="#_release_notes_for_version_1_9">E.13. Release Notes for Version 1.9</a></li>
94 <li><a href="#_release_notes_for_version_1_8_7">E.14. Release Notes for Version 1.8.7</a></li>
95 <li><a href="#_release_notes_for_version_1_8_6">E.15. Release Notes for Version 1.8.6</a></li>
96 <li><a href="#_release_notes_for_version_1_8_5">E.16. Release Notes for Version 1.8.5</a></li>
97 <li><a href="#_release_notes_for_version_1_8_4">E.17. Release Notes for Version 1.8.4</a></li>
98 <li><a href="#_release_notes_for_version_1_8_3">E.18. Release Notes for Version 1.8.3</a></li>
99 <li><a href="#_release_notes_for_version_1_8_2">E.19. Release Notes for Version 1.8.2</a></li>
100 <li><a href="#_release_notes_for_version_1_8_1">E.20. Release Notes for Version 1.8.1</a></li>
101 <li><a href="#_release_notes_for_version_1_8">E.21. Release Notes for Version 1.8</a></li>
102 <li><a href="#_release_notes_for_version_1_7">E.22. Release Notes for Version 1.7</a></li>
103 <li><a href="#_release_notes_for_version_1_6_8">E.23. Release Notes for Version 1.6.8</a></li>
104 <li><a href="#_release_notes_for_version_1_6_5">E.24. Release Notes for Version 1.6.5</a></li>
105 <li><a href="#_release_notes_for_version_1_6_4">E.25. Release Notes for Version 1.6.4</a></li>
106 <li><a href="#_release_notes_for_version_1_6_3">E.26. Release Notes for Version 1.6.3</a></li>
107 <li><a href="#_release_notes_for_version_1_6_2">E.27. Release Notes for Version 1.6.2</a></li>
108 <li><a href="#_release_notes_for_version_1_6_1">E.28. Release Notes for Version 1.6.1</a></li>
109 <li><a href="#_release_notes_for_version_1_6">E.29. Release Notes for Version 1.6</a></li>
110 <li><a href="#_release_notes_for_version_1_5">E.30. Release Notes for Version 1.5</a></li>
111 <li><a href="#_release_notes_for_version_1_4_2">E.31. Release Notes for Version 1.4.2</a></li>
112 <li><a href="#_release_notes_for_version_1_4_1">E.32. Release Notes for Version 1.4.1</a></li>
113 <li><a href="#_release_notes_for_version_1_4">E.33. Release Notes for Version 1.4</a></li>
121 <div class="sectionbody">
122 <div id="logo" class="imageblock">
123 <div class="content">
124 <a class="image" href="https://altusmetrum.org"><img src="altusmetrum-oneline.svg" alt="Altus Metrum"></a>
130 <h2 id="_license">License</h2>
131 <div class="sectionbody">
132 <div class="paragraph">
133 <p>Copyright © 2023 Bdale Garbee and Keith Packard</p>
135 <div class="paragraph">
136 <p>This document is released under the terms of the <a href="http://creativecommons.org/licenses/by-sa/3.0/">Creative Commons ShareAlike 3.0 License</a></p>
141 <h2 id="_acknowledgments">Acknowledgments</h2>
142 <div class="sectionbody">
143 <div class="paragraph">
144 <p>Thanks to Anthony (AJ) Towns for major contributions including
145 the TeleGPS graphing and site map code and associated documentation.
146 Free software means that our customers and friends can become our
147 collaborators, and we certainly appreciate this level of
150 <div class="paragraph">
151 <p>Have fun using these products, and we hope to meet all of you
152 out on the rocket flight line somewhere.</p>
154 <div class="verseblock">
155 <pre class="content">Bdale Garbee, KB0G
156 NAR #87103, TRA #12201</pre>
158 <div class="verseblock">
159 <pre class="content">Keith Packard, K7WQ
160 NAR #88757, TRA #12200</pre>
165 <h2 id="_telegps_quick_start_guide">1. TeleGPS Quick Start Guide</h2>
166 <div class="sectionbody">
167 <div class="paragraph">
168 <p>TeleGPS is designed to be easy to use. Requiring no external
169 components, flying takes just a few steps.</p>
171 <div class="olist arabic">
174 <p>First, download and install the software from
175 <a href="http://altusmetrum.org/AltOS" class="bare">http://altusmetrum.org/AltOS</a>. This will make sure that
176 you have the right device drivers installed.</p>
179 <p>Next, plug in the battery and USB cable and connect TeleGPS to
180 your computer. This will charge the battery and allow you to
181 configure the device.</p>
184 <p>Start the TeleGPS application and set the callsign and frequency
185 on your TeleGPS device; refer to <a href="#_configure_device">Configure Device</a> for instructions.</p>
188 <p>Unplug TeleGPS when the battery charger light goes green. This
189 will enable the radio and logging portions of the TeleGPS
193 <p>Connect TeleDongle to your computer and start TeleGPS or start
194 AltosDroid on your android device and connect to TeleBT. Set the
195 frequency to match the TeleGPS and you should be receiving telemetry.</p>
202 <h2 id="_using_telegps_hardware">2. Using TeleGPS Hardware</h2>
203 <div class="sectionbody">
205 <h3 id="_hooking_up_lithium_polymer_batteries">2.1. Hooking Up Lithium Polymer Batteries</h3>
206 <div class="paragraph">
207 <p>TeleGPS has a two pin JST PH series connector to connect up
208 a single-cell Lithium Polymer cell (3.7V nominal). You can
209 purchase matching batteries from the Altus Metrum store, or
210 other vendors, or you can make your own. Pin 1 of the
211 connector is positive, pin 2 is negative. Spark Fun sells a
212 cable with the connector attached, which they call a
213 <a href="https://www.sparkfun.com/products/9914">JST Jumper 2 Wire Assembly</a></p>
215 <div class="admonitionblock warning">
219 <div class="title">Warning</div>
222 Many RC vendors also sell lithium polymer batteries with
223 this same connector. All that we have found use the opposite
224 polarity, and if you use them that way, you will damage or
232 <h3 id="_on_board_data_recording">2.2. On-board Data Recording</h3>
233 <div class="paragraph">
234 <p>TeleGPS logs GPS data at a user-configurable
235 rate. Data are logged to a 2MB on-board flash memory
236 part, which can be partitioned into several
237 equal-sized blocks, one for each flight. 64kB of this
238 storage are reserved to hold configuration data,
239 leaving 1984kB for flight data.</p>
241 <div class="paragraph">
242 <p>The on-board flash is partitioned into separate flight
243 logs, each of a fixed maximum size. Increase the
244 maximum size of each log and you reduce the number of
245 flights that can be stored. Decrease the size and you
246 can store more flights.</p>
248 <div class="paragraph">
249 <p>To compute the amount of space needed for a single
250 log, you can divide the expected time (in seconds) by
251 the sample period (by default, 1 second per sample)
252 and then multiply the result by 32 bytes per
253 sample. For instance, a sample period of 1 second and
254 a flight lasting one hour will take 32 * 3600 = 115200
255 bytes. TeleGPS does try to reduce log space used by
256 not recording position information when it isn’t
257 moving, so actual space consumed may be less than
260 <div class="paragraph">
261 <p>The default size allows for four flights of 496kB
262 each, which provides over four hours of logging at 1
263 sample per second.</p>
265 <div class="paragraph">
266 <p>TeleGPS will not overwrite existing flight data, so be
267 sure to download flight data and erase it from the
268 onboard flash before it fills up. TeleGPS will still
269 report telemetry even if memory is full, so the only
270 thing you will lose is the on-board data log.</p>
274 <h3 id="_leds">2.3. LEDs</h3>
275 <div class="paragraph">
276 <p>TeleGPS v1.0 has a dual greed/red LED along the edge
277 towards the USB connector end of the board. This
278 indicates battery charging status while connected to
279 power over USB. When the red LED is lit, the battery
280 is charging. Once the battery is fully charged, the
281 red LED goes out and the green LED turns on. If both
282 LEDs are lit, something is probably wrong with the battery.</p>
284 <div class="paragraph">
285 <p>TeleGPS v2.0 has the same green/red battery charging
286 status LED and adds another green LED along the same
287 edge, towards end of the board with the 70cm
288 antenna. This green LED indicates GPS lock status — it
289 blinks once every three seconds when the GPS receiver
290 is locked and tracking position.</p>
294 <h3 id="_installation">2.4. Installation</h3>
295 <div class="paragraph">
296 <p>The battery connectors are a standard 2-pin JST
297 connector and match batteries sold by Spark Fun. These
298 batteries are single-cell Lithium Polymer batteries
299 that nominally provide 3.7 volts. Other vendors sell
300 similar batteries for RC aircraft using mating
301 connectors, however the polarity for those is
302 generally reversed from the batteries used by Altus
303 Metrum products. In particular, the Tenergy batteries
304 supplied for use in Featherweight flight computers are
305 not compatible with Altus Metrum flight computers or
306 battery chargers.</p>
308 <div class="admonitionblock warning">
312 <div class="title">Warning</div>
315 Check polarity and voltage before connecting any
316 battery not purchased from Altus Metrum or Spark
322 <div class="paragraph">
323 <p>TeleGPS uses an integrate GPS patch antenna and won’t
324 receive GPS signals if installed inside a metal or
325 carbon fiber compartment. Test GPS reception and
326 telemetry transmission with the system installed and
327 all other electronics powered up to verify signal
328 reception and make sure there isn’t any interference
329 from other systems.</p>
335 <h2 id="_telegps_application">3. TeleGPS Application</h2>
336 <div class="sectionbody">
337 <div class="paragraph">
338 <p>The TeleGPS application provides a graphical user interface for
339 interacting with the Altus Metrum product family. TeleGPS can
340 monitor telemetry data, configure devices and many other
341 tasks. The primary interface window is for displaying data
342 received over the telemetry link. There are additional
343 tasks available from the main window menu bar.</p>
346 <h3 id="_telemetry_monitoring">3.1. Telemetry Monitoring</h3>
347 <div class="paragraph">
348 <p>This is the window brought up when you start the
349 application. If you have a TeleDongle device connected
350 to the computer, it will automatically be selected for
351 telemetry monitoring</p>
353 <div class="paragraph">
354 <p>All telemetry data received are automatically recorded
355 in suitable log files. The name of the files includes
356 the current date and TeleGPS serial and flight
359 <div class="paragraph">
360 <p>The radio frequency being monitored by the TeleDongle
361 device is displayed at the top of the window. You can
362 configure the frequency by clicking on the frequency
363 box and selecting the desired frequency. The TeleGPS
364 application remembers the last frequency selected for
365 each TeleDongle and selects that automatically the
366 next time you use that device.</p>
368 <div class="paragraph">
369 <p>Below the TeleDongle frequency selector, the window
370 contains a few significant pieces of information about
371 the altimeter providing the telemetry data stream:</p>
376 <p>The configured call-sign</p>
379 <p>The device serial number</p>
382 <p>The flight number. TeleGPS remembers how many times
386 <p>The Received Signal Strength Indicator value. This
387 lets you know how strong a signal TeleDongle is
388 receiving. The radio inside TeleDongle operates down
389 to about -100dBm; weaker signals may not be
390 receivable. The packet link uses error detection and
391 correction techniques which prevent incorrect data
392 from being reported.</p>
395 <p>The age of the displayed data, in seconds since the
396 last successfully received telemetry packet. In
397 normal operation this will stay in the low single
398 digits. If the number starts counting up, then you
399 are no longer receiving data over the radio link
400 from the flight computer.</p>
404 <div class="paragraph">
405 <p>Finally, the largest portion of the window contains a set of
406 tabs, each of which contain some information about the TeleGPS
407 board. The final 'table' tab displays many of the raw telemetry
408 values in one place in a spreadsheet-like format.</p>
411 <h4 id="_map">3.1.1. Map</h4>
412 <div class="paragraph">
413 <p>The Map tab shows the TeleGPS track over time
414 on top of map data making it easy to locate
417 <div class="imageblock">
418 <div class="content">
419 <img src="telegps-map.png" alt="telegps map" width="400">
421 <div class="title">Figure 1. TeleGPS Map View</div>
423 <div class="paragraph">
424 <p>The map’s default scale is approximately 3m
425 (10ft) per pixel. The map can be dragged using
426 the left mouse button. The map will attempt to
427 keep the rocket roughly centered while data is
430 <div class="paragraph">
431 <p>You can adjust the style of map and the zoom
432 level with buttons on the right side of the
433 map window. You can draw a line on the map by
434 moving the mouse over the map with a button
435 other than the left one pressed, or by
436 pressing the left button while also holding
437 down the shift key. The length of the line in
438 real-world units will be shown at the start of
441 <div class="paragraph">
442 <p>Images are fetched automatically via the
443 Google Maps Static API, and cached on disk for
444 reuse. If map images cannot be downloaded, the
445 rocket’s path will be traced on a dark gray
446 background instead.</p>
448 <div class="paragraph">
449 <p>You can pre-load images for your favorite
450 launch sites before you leave home; check out
451 <a href="#_load_maps">Load Maps</a>.</p>
455 <h4 id="_location">3.1.2. Location</h4>
456 <div class="paragraph">
457 <p>The Location tab shows the raw GPS data
458 received from TeleGPS.</p>
460 <div class="imageblock">
461 <div class="content">
462 <img src="telegps-location.png" alt="telegps location" width="400">
464 <div class="title">Figure 2. TeleGPS Location View</div>
468 <h4 id="_status">3.1.3. Status</h4>
469 <div class="paragraph">
470 <p>The Status tab shows data relative to the
471 location of TeleGPS when the application first
472 received telemetry from it.</p>
474 <div class="imageblock">
475 <div class="content">
476 <img src="telegps-status.png" alt="telegps status" width="400">
478 <div class="title">Figure 3. TeleGPS Status View</div>
482 <h4 id="_table">3.1.4. Table</h4>
483 <div class="paragraph">
484 <p>The Table tab shows detailed information about
487 <div class="imageblock">
488 <div class="content">
489 <img src="telegps-table.png" alt="telegps table" width="400">
491 <div class="title">Figure 4. TeleGPS Information Table</div>
496 <h3 id="_telegps_menus">3.2. TeleGPS Menus</h3>
497 <div class="paragraph">
498 <p>TeleGPS has three or four menus at the top of
503 <dt class="hdlist1">File</dt>
505 <p>New Window, Graph Data, Export Data, Load Maps,
506 Preferences, Close and Exit</p>
508 <dt class="hdlist1">Monitor</dt>
510 <p>Connect Device, Disconnect and Scan Channels</p>
512 <dt class="hdlist1">Device</dt>
514 <p>Download Data, Configure Device and Flash Device</p>
516 <dt class="hdlist1">Frequency</dt>
518 <p>This shows the current monitoring frequency with a
519 drop-down menu listing other configured
520 frequencies. You can change the set of frequencies
521 shown here from the Preferences dialog. This menu is
522 only shown when the TeleGPS application is connected
523 to a TeleDongle or TeleBT device.</p>
528 <h4 id="_new_window">3.2.1. New Window</h4>
529 <div class="paragraph">
530 <p>This creates another telemetry monitoring window, in case
531 you have multiple TeleDongle devices connected to the
537 <h3 id="_graph_data">3.3. Graph Data</h3>
538 <div class="paragraph">
539 <p>The Graph tab shows a plot of the the GPS data
540 collected. The X axis is time in seconds; there are a
541 variety of Y axes available for different kinds of
542 data. This window also allows you to see some
543 statistics computed from the data, and an overall map
544 of the entire data record.</p>
547 <h4 id="_data_graph">3.3.1. Data Graph</h4>
548 <div class="imageblock">
549 <div class="content">
550 <img src="telegps-graph-graph.png" alt="telegps graph graph" width="400">
552 <div class="title">Figure 5. TeleGPS Graph</div>
556 <h4 id="_graph_configuration">3.3.2. Graph Configuration</h4>
557 <div class="imageblock">
558 <div class="content">
559 <img src="telegps-graph-configure.png" alt="telegps graph configure" width="400">
561 <div class="title">Figure 6. TeleGPS Graph Configuration</div>
563 <div class="paragraph">
564 <p>This selects which graph elements to show, and, at the
565 bottom, lets you switch between metric and imperial
570 <h4 id="_statistics">3.3.3. Statistics</h4>
571 <div class="imageblock">
572 <div class="content">
573 <img src="telegps-graph-stats.png" alt="telegps graph stats" width="400">
575 <div class="title">Figure 7. TeleGPS Statistics</div>
577 <div class="paragraph">
578 <p>Shows overall data computed from the flight.</p>
582 <h4 id="_map_2">3.3.4. Map</h4>
583 <div class="imageblock">
584 <div class="content">
585 <img src="telegps-graph-map.png" alt="telegps graph map" width="450">
587 <div class="title">Figure 8. TeleGPS Map</div>
589 <div class="paragraph">
590 <p>Shows a map of the area overlaid with the GPS track. As with
591 the telemetry monitoring window, you can select the style
592 of map and zoom level using buttons along the side;
593 you can scroll the map by dragging within the map pressing
594 the left button and you can draw a line to measure
595 distances using either the left button with the shift key,
596 or any other button.</p>
601 <h3 id="_export_data">3.4. Export Data</h3>
602 <div class="paragraph">
603 <p>This tool takes the raw data files and makes them
604 available for external analysis. When you select this
605 button, you are prompted to select a data file, which
606 can be either a .eeprom or .telem. The .eeprom files
607 contain higher resolution and more continuous data,
608 while .telem files contain receiver signal strength
609 information. Next, a second dialog appears which is
610 used to select where to write the resulting file. It
611 has a selector to choose between CSV and KML file
615 <h4 id="_comma_separated_value_format">3.4.1. Comma Separated Value Format</h4>
616 <div class="paragraph">
617 <p>This is a text file containing the data in a
618 form suitable for import into a spreadsheet or
619 other external data analysis tool. The first
620 few lines of the file contain the version and
621 configuration information from TeleGPS, then
622 there is a single header line which labels all
623 of the fields. All of these lines start with a
624 '#' character which many tools can be
625 configured to skip over.</p>
627 <div class="paragraph">
628 <p>The remaining lines of the file contain the
629 data, with each field separated by a comma and
630 at least one space. All of the sensor values
631 are converted to standard units, with the
632 barometric data reported in both pressure,
633 altitude and height above pad units.</p>
637 <h4 id="_keyhole_markup_language_for_google_earth">3.4.2. Keyhole Markup Language (for Google Earth)</h4>
638 <div class="paragraph">
639 <p>This is the format used by Google Earth to provide an overlay
640 within that application. With this, you can use Google Earth to
641 see the whole path in 3D.</p>
646 <h3 id="_load_maps">3.5. Load Maps</h3>
647 <div class="imageblock">
648 <div class="content">
649 <img src="load-maps.png" alt="load maps" width="500">
651 <div class="title">Figure 9. Load Maps Window</div>
653 <div class="paragraph">
654 <p>Before heading out to a new launch site, you can use
655 this to load satellite images in case you don’t have
656 internet connectivity at the site. Try not to wait
657 until the last minute, though, particularly if you’re
658 heading to a major launch. If too many people are
659 all trying to download map data at once, Google may
660 limit access until the next day.</p>
662 <div class="paragraph">
663 <p>There’s a drop-down menu of launch sites we know
664 about; if your favorites aren’t there, please let us
665 know the lat/lon and name of the site. The contents of
666 this list are actually downloaded from our server at
667 run-time, so as new sites are sent in, they’ll get
668 automatically added to this list. If the launch site
669 isn’t in the list, you can manually enter the lat/lon
672 <div class="paragraph">
673 <p>There are four different kinds of maps you can view;
674 you can select which to download by selecting as many
675 as you like from the available types:</p>
679 <dt class="hdlist1">Hybrid</dt>
681 <p>A combination of satellite imagery and road data. This
682 is the default view.</p>
684 <dt class="hdlist1">Satellite</dt>
686 <p>Just the satellite imagery without any annotation.</p>
688 <dt class="hdlist1">Roadmap</dt>
690 <p>Roads, political boundaries and a few geographic
693 <dt class="hdlist1">Terrain</dt>
695 <p>Contour intervals and shading that show hills and
700 <div class="paragraph">
701 <p>You can specify the range of zoom levels to download;
702 smaller numbers show more area with less
703 resolution. The default level, 0, shows about
704 3m/pixel. One zoom level change doubles or halves that
705 number. Larger zoom levels show more detail, smaller
706 zoom levels less.</p>
708 <div class="paragraph">
709 <p>The Map Radius value sets how large an area around the
710 center point to download. Select a value large enough
711 to cover any plausible flight from that site. Be aware
712 that loading a large area with a high maximum zoom
713 level can attempt to download a lot of data. Loading
714 hybrid maps with a 10km radius at a minimum zoom of -2
715 and a maximum zoom of 2 consumes about 120MB of
716 space. Terrain and road maps consume about 1/10 as
717 much space as satellite or hybrid maps.</p>
719 <div class="paragraph">
720 <p>Clicking the 'Load Map' button will fetch images from
721 Google Maps; note that Google limits how many images
722 you can fetch at once, so if you load more than one
723 launch site, you may get some gray areas in the map
724 which indicate that Google is tired of sending data to
725 you. Try again later.</p>
729 <h3 id="_preferences">3.6. Preferences</h3>
730 <div class="imageblock">
731 <div class="content">
732 <img src="telegps-preferences.png" alt="telegps preferences" width="230">
734 <div class="title">Figure 10. TeleGPS Preferences Window</div>
737 <h4 id="_voice_settings">3.6.1. Voice Settings</h4>
738 <div class="paragraph">
739 <p>TeleGPS provides voice announcements during
740 flight so that you can keep your eyes on the
741 sky and still get information about the
742 current flight status. However, sometimes you
743 don’t want to hear them.</p>
747 <dt class="hdlist1">Enable</dt>
749 <p>Turns all voice announcements on and off</p>
751 <dt class="hdlist1">Test Voice</dt>
753 <p>Plays a short message allowing you to verify
754 that the audio system is working and the volume settings
761 <h4 id="_log_directory">3.6.2. Log Directory</h4>
762 <div class="paragraph">
763 <p>TeleGPS logs all telemetry data and saves all
764 flash data to this directory. This
765 directory is also used as the staring point
766 when selecting data files for display or
769 <div class="paragraph">
770 <p>Click on the directory name to bring up a
771 directory choosing dialog, select a new
772 directory and click 'Select Directory' to
773 change where TeleGPS reads and writes data
778 <h4 id="_callsign">3.6.3. Callsign</h4>
779 <div class="paragraph">
780 <p>This value is transmitted in each command
781 packet sent from TeleDongle and received from
782 an altimeter. It is not used in telemetry
783 mode, as the callsign configured in the
784 altimeter board is included in all telemetry
785 packets. Configure this with the TeleGPS
786 operators call sign as needed to comply with
787 your local radio regulations.</p>
789 <div class="paragraph">
790 <p>Note that to successfully command a flight
791 computer over the radio (to configure the
792 altimeter, monitor idle, or fire pyro
793 charges), the callsign configured here must
794 exactly match the callsign configured in the
795 flight computer. This matching is case
800 <h4 id="_imperial_units">3.6.4. Imperial Units</h4>
801 <div class="paragraph">
802 <p>This switches between metric units (meters)
803 and imperial units (feet and miles). This
804 affects the display of values use during
805 flight monitoring, configuration, data
806 graphing and all of the voice
807 announcements. It does not change the units
808 used when exporting to CSV files, those are
809 always produced in metric units.</p>
813 <h4 id="_serial_debug">3.6.5. Serial Debug</h4>
814 <div class="paragraph">
815 <p>This causes all communication with a connected
816 device to be dumped to the console from which
817 TeleGPS was started. If you’ve started it from
818 an icon or menu entry, the output will simply
819 be discarded. This mode can be useful to debug
820 various serial communication issues.</p>
824 <h4 id="_font_size">3.6.6. Font size</h4>
825 <div class="paragraph">
826 <p>Selects the set of fonts used in the flight
827 monitor window. Choose between the small,
828 medium and large sets.</p>
832 <h4 id="_look_feel">3.6.7. Look & feel</h4>
833 <div class="paragraph">
834 <p>Switches between the available Java user
835 interface appearances. The default selection
836 is supposed to match the native window system
837 appearance for the target platform.</p>
841 <h4 id="_menu_position">3.6.8. Menu position</h4>
842 <div class="paragraph">
843 <p>Selects the initial position for the main
844 TeleGPS window that includes all of the
849 <h4 id="_map_cache_size">3.6.9. Map Cache Size</h4>
850 <div class="paragraph">
851 <p>Sets the number of map 'tiles' kept in memory
852 while the application is running. More tiles
853 consume more memory, but will make panning
854 around the map faster.</p>
858 <h4 id="_manage_frequencies">3.6.10. Manage Frequencies</h4>
859 <div class="paragraph">
860 <p>This brings up a dialog where you can
861 configure the set of frequencies shown in the
862 various frequency menus. You can add as many
863 as you like, or even reconfigure the default
864 set. Changing this list does not affect the
865 frequency settings of any devices, it only
866 changes the set of frequencies shown in the
872 <h3 id="_close">3.7. Close</h3>
873 <div class="paragraph">
874 <p>This closes the current window, leaving any other windows
875 open and the application running.</p>
879 <h3 id="_exit">3.8. Exit</h3>
880 <div class="paragraph">
881 <p>This closes all TeleGPS windows and terminates the
886 <h3 id="_connect_device">3.9. Connect Device</h3>
887 <div class="paragraph">
888 <p>Selecting this item brings up a dialog box listing all
889 of the connected TeleDongle devices. When you choose
890 one of these, AltosUI will display telemetry data as
891 received by the selected TeleDongle device.</p>
893 <div class="imageblock">
894 <div class="content">
895 <img src="device-selection.png" alt="device selection" width="300">
897 <div class="title">Figure 11. Device Selection Dialog</div>
901 <h3 id="_disconnect">3.10. Disconnect</h3>
902 <div class="paragraph">
903 <p>Disconnects the currently connected TeleDongle or
908 <h3 id="_scan_channels">3.11. Scan Channels</h3>
909 <div class="imageblock">
910 <div class="content">
911 <img src="telegps-scan.png" alt="telegps scan" width="300">
913 <div class="title">Figure 12. Radio Scanning Dialog</div>
915 <div class="paragraph">
916 <p>Scans the configured set of frequencies looking for
917 telemetry signals. A list of all of the discovered
918 signals is show; selecting one of those and clicking
919 on 'Monitor' will select that frequency in the
920 associated TeleGPS application window.</p>
924 <h3 id="_download_data">3.12. Download Data</h3>
925 <div class="paragraph">
926 <p>TeleGPS records data to its internal flash memory.
927 On-board data is recorded at the same rate as
928 telemetry but is not subject to radio drop-outs. As
929 such, it generally provides a more complete and
930 precise record. The 'Download Data' menu entry allows
931 you to read the flash memory and write it to disk.</p>
933 <div class="paragraph">
934 <p>Select the 'Download Data' menu entry to bring up a
935 list of connected TeleGPS devices. After the device
936 has been selected, a dialog showing the data stored in
937 the device will be shown allowing you to select which
938 entries to download and which to delete. You must
939 erase flights in order for the space they consume to
940 be reused by another track. This prevents accidentally
941 losing data if you neglect to download data before
942 starting TeleGPS again. Note that if there is no more
943 space available in the device, then no data will be
946 <div class="paragraph">
947 <p>The file name for each data log is computed
948 automatically from the recorded date, altimeter serial
949 number and flight number information.</p>
953 <h3 id="_configure_device">3.13. Configure Device</h3>
954 <div class="imageblock">
955 <div class="content">
956 <img src="telegps-configure.png" alt="telegps configure" width="350">
958 <div class="title">Figure 13. TeleGPS Configuration Dialog</div>
960 <div class="paragraph">
961 <p>Select this button and then select any connected TeleGPS
962 device from the list provided.</p>
964 <div class="paragraph">
965 <p>The first few lines of the dialog provide information
966 about the connected device, including the product
967 name, software version and hardware serial
968 number. Below that are the individual configuration
971 <div class="paragraph">
972 <p>At the bottom of the dialog, there are four buttons:</p>
976 <dt class="hdlist1">Save</dt>
978 <p>This writes any changes to the configuration parameter
979 block in flash memory. If you don’t press this button,
980 any changes you make will be lost.</p>
982 <dt class="hdlist1">Reset</dt>
984 <p>This resets the dialog to the most recently saved
985 values, erasing any changes you have made.</p>
987 <dt class="hdlist1">Reboot</dt>
989 <p>This reboots the device. Use this to switch from idle
990 to pad mode by rebooting once the rocket is oriented
991 for flight, or to confirm changes you think you saved
992 are really saved.</p>
994 <dt class="hdlist1">Close</dt>
996 <p>This closes the dialog. Any unsaved changes will be
1001 <div class="paragraph">
1002 <p>The rest of the dialog contains the parameters to be configured.</p>
1005 <h4 id="_frequency">3.13.1. Frequency</h4>
1006 <div class="paragraph">
1007 <p>This configures which of the frequencies to use for
1008 both telemetry and packet command mode. Note that if
1009 you set this value via packet command mode, the
1010 TeleDongle frequency will also be automatically
1011 reconfigured to match so that communication will
1012 continue afterwards.</p>
1016 <h4 id="_rf_calibration">3.13.2. RF Calibration</h4>
1017 <div class="paragraph">
1018 <p>The radios in every Altus Metrum device are calibrated
1019 at the factory to ensure that they transmit and
1020 receive on the specified frequency. If you need to
1021 you can adjust the calibration by changing this value.
1022 Do not do this without understanding what the value
1023 means, read the appendix on calibration and/or the
1024 source code for more information. To change a
1025 TeleDongle’s calibration, you must reprogram the unit
1030 <h4 id="_telemetryrdfaprs_enable">3.13.3. Telemetry/RDF/APRS Enable</h4>
1031 <div class="paragraph">
1032 <p>Enables the radio for transmission during
1033 flight. When disabled, the radio will not
1034 transmit anything during flight at all.</p>
1038 <h4 id="_limit_transmit_to_10mw">3.13.4. Limit transmit to 10mW</h4>
1039 <div class="paragraph">
1040 <p>Reduces transmit power to no more than 10mW. This is
1041 useful when operating under some UK radio regulations.</p>
1045 <h4 id="_telemetry_baud_rate">3.13.5. Telemetry baud rate</h4>
1046 <div class="paragraph">
1047 <p>This sets the modulation bit rate for data
1048 transmission for both telemetry and packet
1049 link mode. Lower bit rates will increase range
1050 while reducing the amount of data that can be
1051 sent and increasing battery consumption. All
1052 telemetry is done using a rate 1/2 constraint
1053 4 convolution code, so the actual data
1054 transmission rate is 1/2 of the modulation bit
1055 rate specified here.</p>
1059 <h4 id="_aprs_interval">3.13.6. APRS Interval</h4>
1060 <div class="paragraph">
1061 <p>How often to transmit GPS information via APRS
1062 (in seconds). When set to zero, APRS
1063 transmission is disabled.
1064 Note that a single APRS packet
1065 takes nearly a full second to transmit, so
1066 enabling this option will prevent sending any
1067 other telemetry during that time.</p>
1071 <h4 id="_aprs_ssid">3.13.7. APRS SSID</h4>
1072 <div class="paragraph">
1073 <p>Which SSID to report in APRS packets. By
1074 default, this is set to the last digit of the
1075 serial number, but can be configured to any
1076 value from 0 to 9.</p>
1080 <h4 id="_aprs_format">3.13.8. APRS Format</h4>
1081 <div class="paragraph">
1082 <p>Whether to send APRS data in Compressed or
1083 Uncompressed format. Compressed format is
1084 smaller and more precise. Uncompressed
1085 format is older, but may work better with your
1086 device. The Kenwood TH-D72 only displays
1087 altitude information with Uncompressed
1088 format, while the Yaesu FT1D only displays
1089 altitude with Compressed format. Test before
1090 you fly to see which to use.</p>
1094 <h4 id="_aprs_offset">3.13.9. APRS Offset</h4>
1095 <div class="paragraph">
1096 <p>The delay from the top of the minute before sending
1097 the first APRS packet of the minute. Coordinating
1098 values for this parameter between multiple devices can
1099 allow a single receiver to reliably receive APRS
1100 packets from multiple devices. Note that this offset only
1101 takes effect while the GPS signal is locked so that the
1102 transmitting device knows the current time.</p>
1106 <h4 id="_callsign_2">3.13.10. Callsign</h4>
1107 <div class="paragraph">
1108 <p>This sets the call sign included in each
1109 telemetry packet. Set this as needed to
1110 conform to your local radio regulations.</p>
1114 <h4 id="_logging_trigger_motion">3.13.11. Logging Trigger Motion</h4>
1115 <div class="paragraph">
1116 <p>This sets the amount of motion that TeleGPS
1117 needs to see before logging the new
1118 position. Motions smaller than this are
1119 skipped, which saves storage space.</p>
1123 <h4 id="_position_reporting_interval">3.13.12. Position Reporting Interval</h4>
1124 <div class="paragraph">
1125 <p>The interval between TeleGPS position reports,
1126 both over the air and in the log. Increase
1127 this to reduce the frequency of radio
1128 transmissions and the length of time available
1134 <h3 id="_flash_device">3.14. Flash Device</h3>
1135 <div class="paragraph">
1136 <p>This reprograms TeleGPS devices with new
1137 firmware. Please read the directions for flashing
1138 devices in <a href="#_updating_device_firmware">Updating Device Firmware</a>.</p>
1144 <h2 id="_telegps_system_operation">Appendix A: TeleGPS System Operation</h2>
1145 <div class="sectionbody">
1147 <h3 id="_gfsk_telemetry">A.1. GFSK Telemetry</h3>
1148 <div class="paragraph">
1149 <p>TeleGPS’s native telemetry system doesn’t use a
1150 'normal packet radio' mode like APRS because it’s not
1151 very efficient. The GFSK modulation we use is FSK
1152 with the base-band pulses passed through a Gaussian
1153 filter before they go into the modulator to limit the
1154 transmitted bandwidth. When combined with forward
1155 error correction and interleaving, this allows us to
1156 have a very robust 19.2 kilobit data link with only
1157 10-40 milliwatts of transmit power, a whip antenna in
1158 the rocket, and a hand-held Yagi on the ground. We’ve
1159 had flights to above 21k feet AGL with great
1160 reception, and calculations suggest we should be good
1161 to well over 40k feet AGL with a 5-element yagi on the
1162 ground with our 10mW units and over 100k feet AGL with
1163 the 40mW devices.</p>
1167 <h3 id="_aprs">A.2. APRS</h3>
1168 <div class="paragraph">
1169 <p>TeleGPS can send APRS if desired, and the
1170 interval between APRS packets can be configured. As
1171 each APRS packet takes a full second to transmit, we
1172 recommend an interval of at least 5 seconds to avoid
1173 consuming too much battery power or radio channel
1174 bandwidth. You can configure the time within each
1175 minute that APRS transmits by changing the APRS offset
1176 value. When the GPS signal is locked and knows the
1177 current time, the APRS offset selects the time with
1178 each minute for the first APRS transmission;
1179 subsequent transmissions occur each APRS interval
1180 seconds thereafter. You can configure the APRS
1181 interval and APRS offset using TeleGPS; that
1182 process is described in <a href="#_configure_device">Configure Device</a>.</p>
1184 <div class="paragraph">
1185 <p>AltOS supports both compressed and uncompressed APRS
1186 position report data formats. The compressed format
1187 provides for higher position precision and shorter
1188 packets than the uncompressed APRS format. We’ve found
1189 some older APRS receivers that do not handle the
1190 compressed format. The Kenwood TH-72A requires the use
1191 of uncompressed format to display altitude information
1192 correctly. The Yaesu FT1D requires the use of
1193 compressed format to display altitude information.</p>
1195 <div class="paragraph">
1196 <p>APRS packets include an SSID (Secondary Station Identifier)
1197 field that allows one operator to have multiple
1198 transmitters. AltOS allows you to set this to a single digit
1199 from 0 to 9, allowing you to fly multiple transmitters at the
1200 same time while keeping the identify of each one separate in
1201 the receiver. By default, the SSID is set to the last digit of
1202 the device serial number.</p>
1204 <div class="paragraph">
1205 <p>The APRS packet format includes a comment field that
1206 can have arbitrary text in it. AltOS uses this to send
1207 status information as shown in the following table.</p>
1209 <table class="tableblock frame-all grid-all stretch">
1210 <caption class="title">Table 1. Altus Metrum APRS Comments</caption>
1212 <col style="width: 20%;">
1213 <col style="width: 20%;">
1214 <col style="width: 60%;">
1218 <th class="tableblock halign-left valign-top">Field</th>
1219 <th class="tableblock halign-left valign-top">Example</th>
1220 <th class="tableblock halign-left valign-top">Description</th>
1225 <td class="tableblock halign-left valign-top"><p class="tableblock">1</p></td>
1226 <td class="tableblock halign-left valign-top"><p class="tableblock">L</p></td>
1227 <td class="tableblock halign-left valign-top"><p class="tableblock">GPS Status U for unlocked, L for locked</p></td>
1230 <td class="tableblock halign-left valign-top"><p class="tableblock">2</p></td>
1231 <td class="tableblock halign-left valign-top"><p class="tableblock">6</p></td>
1232 <td class="tableblock halign-left valign-top"><p class="tableblock">Number of Satellites in View</p></td>
1235 <td class="tableblock halign-left valign-top"><p class="tableblock">3</p></td>
1236 <td class="tableblock halign-left valign-top"><p class="tableblock">B4.0</p></td>
1237 <td class="tableblock halign-left valign-top"><p class="tableblock">Altimeter Battery Voltage</p></td>
1240 <td class="tableblock halign-left valign-top"><p class="tableblock">4</p></td>
1241 <td class="tableblock halign-left valign-top"><p class="tableblock">1286</p></td>
1242 <td class="tableblock halign-left valign-top"><p class="tableblock">Device Serial Number</p></td>
1246 <div class="paragraph">
1247 <p>Here’s an example of an APRS comment showing GPS lock with 6
1248 satellites in view and a primary battery at 4.0V from device 1876.</p>
1250 <div class="literalblock">
1251 <div class="content">
1252 <pre>L6 B4.0 1876</pre>
1255 <div class="paragraph">
1256 <p>Make sure your primary battery is above 3.8V
1257 and GPS is locked with at least 5 or 6 satellites in
1258 view before flying. If GPS is switching between L and
1259 U regularly, then it doesn’t have a good lock and you
1260 should wait until it becomes stable.</p>
1262 <div class="paragraph">
1263 <p>If the GPS receiver loses lock, the APRS data
1264 transmitted will contain the last position for which
1265 GPS lock was available. You can tell that this has
1266 happened by noticing that the GPS status character
1267 switches from 'L' to 'U'. Before GPS has locked, APRS
1268 will transmit zero for latitude, longitude and
1273 <h3 id="_configurable_parameters">A.3. Configurable Parameters</h3>
1274 <div class="paragraph">
1275 <p>Configuring TeleGPS is very simple; the few configurable
1276 parameters can all be set using the TeleGPS application over
1277 USB. Check out <a href="#_configure_device">Configure Device</a>.</p>
1283 <h2 id="_handling_precautions">Appendix B: Handling Precautions</h2>
1284 <div class="sectionbody">
1285 <div class="paragraph">
1286 <p>All Altus Metrum products are sophisticated electronic devices.
1287 When handled gently and properly installed in an air-frame, they
1288 will deliver impressive results. However, as with all electronic
1289 devices, there are some precautions you must take.</p>
1291 <div class="admonitionblock warning">
1295 <div class="title">Warning</div>
1297 <td class="content">
1298 The Lithium Polymer rechargeable batteries have an
1299 extraordinary power density. This is great because we can fly with
1300 much less battery mass than if we used alkaline batteries or previous
1301 generation rechargeable batteries…​ but if they are punctured
1302 or their leads are allowed to short, they can and will release their
1303 energy very rapidly!
1304 Thus we recommend that you take some care when handling our batteries
1305 and consider giving them some extra protection in your air-frame. We
1306 often wrap them in suitable scraps of closed-cell packing foam before
1307 strapping them down, for example.
1312 <div class="paragraph">
1313 <p>The barometric sensors used on all of our flight computers are
1314 sensitive to sunlight. In normal mounting situations, the baro sensor
1315 and all of the other surface mount components
1316 are “down” towards whatever the underlying mounting surface is, so
1317 this is not normally a problem. Please consider this when designing an
1318 installation in an air-frame with a see-through plastic payload bay. It
1319 is particularly important to
1320 consider this with TeleMini v1.0, both because the baro sensor is on the
1321 “top” of the board, and because many model rockets with payload bays
1322 use clear plastic for the payload bay! Replacing these with an opaque
1323 cardboard tube, painting them, or wrapping them with a layer of masking
1324 tape are all reasonable approaches to keep the sensor out of direct
1327 <div class="paragraph">
1328 <p>The barometric sensor sampling port must be able to “breathe”,
1329 both by not being covered by foam or tape or other materials that might
1330 directly block the hole on the top of the sensor, and also by having a
1331 suitable static vent to outside air.</p>
1333 <div class="paragraph">
1334 <p>As with all other rocketry electronics, Altus Metrum altimeters must
1335 be protected from exposure to corrosive motor exhaust and ejection
1341 <h2 id="_technical_information">Appendix C: Technical Information</h2>
1342 <div class="sectionbody">
1344 <h3 id="_gps_receiver">C.1. GPS Receiver</h3>
1345 <div class="paragraph">
1346 <p>TeleGPS uses the u-Blox Max-7Q GPS receiver.</p>
1350 <h3 id="_70cm_transmitter">C.2. 70cm Transmitter</h3>
1351 <div class="paragraph">
1352 <p>TeleGPS uses a TI CC115L transmitter. This radio
1353 produces 10mW of RF output.</p>
1357 <h3 id="_micro_controller">C.3. Micro-controller</h3>
1358 <div class="paragraph">
1359 <p>TeleGPS uses an NXP LPC11U14 micro-controller. This
1360 tiny CPU contains 32kB of flash for the application
1361 and 4kB of RAM for temporary data storage.</p>
1365 <h3 id="_lithium_polymer_battery">C.4. Lithium Polymer Battery</h3>
1366 <div class="paragraph">
1367 <p>Shipping restrictions may prevent us from including a
1368 battery battery with TeleGPS.</p>
1372 <h3 id="_mechanical_considerations">C.5. Mechanical Considerations</h3>
1373 <div class="paragraph">
1374 <p>TeleGPS is designed to be rugged enough for typical
1375 rocketry applications. The 4 mounting holes on the
1376 board are sized for use with 4-40 or M3 screws.</p>
1380 <h3 id="_on_board_data_storage">C.6. On-board data storage</h3>
1381 <div class="paragraph">
1382 <p>TeleGPS has 2MB of non-volatile storage, separate from
1383 the code storage memory. The TeleGPS firmware uses
1384 this to log information during flight.</p>
1390 <h2 id="_updating_device_firmware">Appendix D: Updating Device Firmware</h2>
1391 <div class="sectionbody">
1392 <div class="paragraph">
1393 <p>TeleGPS is programmed directly over its USB connectors.</p>
1395 <div class="paragraph">
1396 <p>You may wish to begin by ensuring you have current firmware images.
1397 These are distributed as part of the TeleGPS software bundle that
1398 also includes the TeleGPS ground station program. Newer ground
1399 station versions typically work fine with older firmware versions,
1400 so you don’t need to update your devices just to try out new
1401 software features. You can always download the most recent
1402 version from <a href="http://www.altusmetrum.org/AltOS/" class="bare">http://www.altusmetrum.org/AltOS/</a></p>
1405 <h3 id="_updating_telegps_firmware">D.1. Updating TeleGPS Firmware</h3>
1406 <div class="olist arabic">
1409 <p>Attach a battery and power switch to the target
1410 device. Power up the device.</p>
1413 <p>Using a Micro USB cable, connect the target device to
1414 your computer’s USB socket.</p>
1417 <p>Run TeleGPS, and select 'Flash Device' from the
1421 <p>Select the target device in the Device Selection
1425 <p>Select the image you want to flash to the device,
1426 which should have a name in the form
1427 <product>-v<product-version>-<software-version>.ihx,
1428 such as TeleGPS-v1.0-1.4.0.ihx.</p>
1431 <p>Make sure the configuration parameters are reasonable
1432 looking. If the serial number and/or RF configuration
1433 values aren’t right, you’ll need to change them.</p>
1436 <p>Hit the 'OK' button and the software should proceed
1437 to flash the device with new firmware, showing a
1441 <p>Verify that the device is working by using the
1442 'Configure Device item to check over the
1451 <h2 id="_release_notes">Appendix E: Release Notes</h2>
1452 <div class="sectionbody">
1454 <h3 id="_release_notes_for_version_1_9_13">E.1. Release Notes for Version 1.9.13</h3>
1455 <div class="paragraph">
1456 <p>Version 1.9.13</p>
1459 <h4 id="_altos">E.1.1. AltOS</h4>
1463 <p>Add option to beep max height in feet after landing</p>
1466 <p>Fix APRS reports to be sent at the correct time and spacing.</p>
1469 <p>Fix possible barometric sensor communication failure when
1470 the CPU is busy talking to the radio at the same time. This
1471 would cause loss of telemetry and failure to track the state
1472 of the rocket during flight. This was aggrevated by the APRS
1473 reports getting sent more often than they should.</p>
1476 <p>Change EasyMotor v3 code to base logging on motor pressure
1477 rather than the accelerometer. This allows use of EasyMotor
1478 v3 in a static test stand.</p>
1484 <h4 id="_altosui">E.1.2. AltosUI</h4>
1488 <p>Add support for configuring the units used to report height
1489 after landing on the beeper.</p>
1493 <div style="page-break-after: always;"></div>
1497 <h3 id="_release_notes_for_version_1_9_12">E.2. Release Notes for Version 1.9.12</h3>
1498 <div class="paragraph">
1499 <p>Version 1.9.12</p>
1502 <h4 id="_altos_2">E.2.1. AltOS</h4>
1506 <p>Add EasyMini v3.0 and EasyMotor v3.0 support</p>
1509 <p>Fix TeleMetrum v2.0 configuration. Saving config would
1510 crash the board.</p>
1516 <h4 id="_altosui_2">E.2.2. AltosUI</h4>
1520 <p>Add EasyMotor log parsing and graphing.</p>
1524 <div style="page-break-after: always;"></div>
1528 <h3 id="_release_notes_for_version_1_9_11">E.3. Release Notes for Version 1.9.11</h3>
1529 <div class="paragraph">
1530 <p>Version 1.9.11</p>
1533 <h4 id="_altos_3">E.3.1. AltOS</h4>
1537 <p>Make Apogee Delay work again.</p>
1540 <p>Allow TX power to be limited to 10mW for compliance with
1541 some uses under UK regulations.</p>
1544 <p>Fix numerous minor issues with 16- vs 32- bit time values.</p>
1550 <h4 id="_altosui_3">E.3.2. AltosUI</h4>
1554 <p>Support M1-based Macs, follow AdoptOpenJDK to Adoptium</p>
1560 <h4 id="_altosdroid">E.3.3. AltosDroid</h4>
1564 <p>Handle Bluetooth permissions reliably.</p>
1567 <p>Fix some screen rotation bugs.</p>
1571 <div style="page-break-after: always;"></div>
1575 <h3 id="_release_notes_for_version_1_9_10">E.4. Release Notes for Version 1.9.10</h3>
1576 <div class="paragraph">
1577 <p>Version 1.9.10</p>
1579 <div class="paragraph">
1580 <p>This release contains a couple of bug fixes for ground station software.</p>
1583 <h4 id="_altosui_4">E.4.1. AltosUI</h4>
1587 <p>Rework the windows DLL build to make AltosUI run on more
1588 instances of Windows 10.</p>
1594 <h4 id="_altosdroid_2">E.4.2. AltosDroid</h4>
1598 <p>Adapt to Android security changes which prevent AltosDroid
1599 from storing flights in
1600 /storage/emulated/0/AltusMetrum. Now, flights are stored in
1601 /storage/emulated/0/media/org.altusmetrum.AltosDroid/AltusMetrum
1602 instead. Also, AltosDroid will display an error message if
1603 flight data cannot be logged.</p>
1607 <div style="page-break-after: always;"></div>
1611 <h3 id="_release_notes_for_version_1_9_9">E.5. Release Notes for Version 1.9.9</h3>
1612 <div class="paragraph">
1613 <p>Version 1.9.9</p>
1615 <div class="paragraph">
1616 <p>This release contains a critical bug fix for a problem
1617 introduced in version 1.9.8 for TeleMega and EasyMega
1618 boards. This problem occurs when using the stored
1619 configuration from 1.9.7 or earlier.</p>
1621 <div class="paragraph">
1622 <p>If you are running 1.9.8 or are upgrading from 1.9.8 on any
1623 version of TeleMega or EasyMega, you must reconfigure all pyro
1624 channels, recalibrate accelerometers, reset the APRS interval,
1625 adjust the beep tone and reset the pyro time.</p>
1628 <h4 id="_altos_4">E.5.1. AltOS</h4>
1632 <p>Fix EasyMega and TeleMega upgrade process from 1.9.7 or
1633 earlier. 1.9.8 introduced larger delay values, which
1634 required modifying the configuration in-place, and the 1.9.8
1635 version had a flaw which broke the pyro channel config and
1636 all of the config values beyond that in memory, including
1637 APRS interval, IMU accel calibation, beep tone and pyro
1641 <p>Fix TeleMega v5.0 mag sensor driver. This driver was quite
1642 broken due to developing it in the presence of the magnetic
1643 beeper on the board. Because of that beeper, the values this
1644 sensor records are not accurate. Fortunately, they are not
1645 used for controlling the flight.</p>
1651 <h4 id="_altosui_5">E.5.2. AltosUI</h4>
1655 <p>Parse TeleMega v5.0 log files. A missing check in the code
1656 meant that the TeleMega v5.0 log files would cause an error
1657 when attempting to load them. Logs saved with AltosUI
1658 1.9.8 were not affected, only the presentation of the data
1663 <div style="page-break-after: always;"></div>
1667 <h3 id="_release_notes_for_version_1_9_8">E.6. Release Notes for Version 1.9.8</h3>
1668 <div class="paragraph">
1669 <p>Version 1.9.8</p>
1672 <h4 id="_altos_5">E.6.1. AltOS</h4>
1676 <p>Add support for TeleMega v5.0</p>
1679 <p>Extend extra pyro channel times to support delay > 327 seconds</p>
1685 <h4 id="_altosui_6">E.6.2. AltosUI</h4>
1689 <p>Support ARM devices in Linux binary release</p>
1692 <p>Add support for TeleMega v5.0</p>
1698 <h4 id="_altosdroid_3">E.6.3. AltosDroid</h4>
1702 <p>Show tilt angle in pad and flight tabs</p>
1705 <p>Show altitude as well as height (useful for TeleGPS)</p>
1708 <p>Support devices without GPS receivers</p>
1714 <h4 id="_micropeak_gui">E.6.4. MicroPeak GUI</h4>
1718 <p>Show error dialog if device open fails</p>
1722 <div style="page-break-after: always;"></div>
1726 <h3 id="_release_notes_for_version_1_9_7">E.7. Release Notes for Version 1.9.7</h3>
1727 <div class="paragraph">
1728 <p>Version 1.9.7</p>
1731 <h4 id="_altos_6">E.7.1. AltOS</h4>
1735 <p>Fix TeleGPS logging so that new data are appended to an existing log correctly</p>
1741 <h4 id="_altosui_7">E.7.2. AltosUI</h4>
1745 <p>Support Mac OS X 11 (Big Sur)</p>
1748 <p>Support Monitor Idle on Easy Timer</p>
1751 <p>Fix TeleMega v4.0 and TeleMetrum v3.0 configuration in Antenna Down mode</p>
1754 <p>Show launch sites in Load Maps view</p>
1757 <p>Add IMU header names to CSV files</p>
1760 <p>Clean up TeleGPS log corruption due to firmware bugs during firmware update</p>
1766 <h4 id="_altosdroid_4">E.7.3. AltosDroid</h4>
1770 <p>Support older devices back to Android version 5.1</p>
1773 <p>Fix a number of issues that could result in app crashes</p>
1777 <div style="page-break-after: always;"></div>
1781 <h3 id="_release_notes_for_version_1_9_6">E.8. Release Notes for Version 1.9.6</h3>
1782 <div class="paragraph">
1783 <p>Version 1.9.6</p>
1786 <h4 id="_altos_7">E.8.1. AltOS</h4>
1790 <p>Fix EasyTimer bug where it might mis-detect boost (either
1791 detect it early or not at all) due to small errors in
1792 accelerometer calibration leading to large accumulated error
1796 <p>Adjust self-test of new 9-axis IMU (BMX-160) so that it
1797 doesn’t think the part has a failure when tested sitting
1802 <div style="page-break-after: always;"></div>
1806 <h3 id="_release_notes_for_version_1_9_5">E.9. Release Notes for Version 1.9.5</h3>
1807 <div class="paragraph">
1808 <p>Version 1.9.5</p>
1811 <h4 id="_altos_8">E.9.1. AltOS</h4>
1815 <p>Add Booster mode for all dual-deploy altimeters. Select
1816 "Separation & Apogee" mode in AltosUI to fire the 'main'
1817 channel at first motor burnout and the 'apogee' channel at
1821 <p>Improve reliability of stm32l firmware under heavy
1822 load. This was found using Monitor Idle on TeleMega with all
1823 flash slots full of data which would occasionally lock up.</p>
1826 <p>Fix orientation label in AltosUI for devices with
1827 radios. This makes the orientation say 'Antenna up' and
1828 'Antenna Down' for TeleMetrum and TeleMega again.</p>
1831 <p>Fix log data for pyro channels which were inhibited (often
1832 because of a tilt limit). They used to report 'fired' as
1833 soon as they were inhibited, which was misleading. Now they
1834 never report as having been fired.</p>
1837 <p>Allow Igniter Test to fire each igniter more than once.</p>
1843 <h4 id="_altosui_8">E.9.2. AltosUI</h4>
1847 <p>Improve performance of Monitor Idle mode by sending less data for each
1851 <p>Improve Mac OS X install scripts so that they work on
1852 Catalina. This involves sending the user to get Java from
1853 the AdoptOpenJDK project which provides a version that works
1854 with Java applications.</p>
1857 <p>Make larger dialogs scrollable for use on smaller screens.</p>
1860 <p>Fix troubles re-flashing EasyMega boards running older
1864 <p>Add TeleMetrum v3.0 firmware to the Windows
1865 AltosUI packages.</p>
1869 <div style="page-break-after: always;"></div>
1873 <h3 id="_release_notes_for_version_1_9_4">E.10. Release Notes for Version 1.9.4</h3>
1874 <div class="paragraph">
1875 <p>Version 1.9.4</p>
1878 <h4 id="_altos_9">E.10.1. AltOS</h4>
1882 <p>Fixed firmware for TeleDongle v3.0 and TeleBT v4.0. Version 1.9.3 bricked those
1883 devices requiring them to be opened up to get them working again.</p>
1886 <p>Fixed firmware for EasyMini v1.0. Changes in the storage
1887 code caused it to use significantly more RAM which made the
1888 interrupt stack smash into other data structures and cause
1889 the device to panic at startup time.</p>
1895 <h4 id="_altosui_9">E.10.2. AltosUI</h4>
1899 <p>Add TeleMetrum v3.0 firmware to the Linux and Mac OSX
1900 AltosUI packages.</p>
1904 <div style="page-break-after: always;"></div>
1908 <h3 id="_release_notes_for_version_1_9_3">E.11. Release Notes for Version 1.9.3</h3>
1909 <div class="paragraph">
1910 <p>Version 1.9.3</p>
1913 <h4 id="_altos_10">E.11.1. AltOS</h4>
1917 <p>Add APRS offset. Allows multiple APRS transmitters to coordinate when
1918 transmission occurs to allow them to share a frequency.</p>
1921 <p>Fix max log size. Flight computer storage is erased in 64kB chunks. Adjust max
1922 log size to be a multiple of this size.</p>
1925 <p>Check flight erasing more carefully. Handle interrupting erasing in the
1929 <p>Add EasyTimer support.</p>
1935 <h4 id="_altosui_telegps_micropeak">E.11.2. AltosUI, TeleGPS, MicroPeak</h4>
1939 <p>Add configuration support for APRS offset.</p>
1942 <p>Adjust flight log sizes to be a multiple of the flight
1943 computer erase block size.</p>
1946 <p>Report barometric pad altitude in Pad tab for TeleMini.</p>
1950 <div style="page-break-after: always;"></div>
1954 <h3 id="_release_notes_for_version_1_9_1">E.12. Release Notes for Version 1.9.1</h3>
1955 <div class="paragraph">
1956 <p>Version 1.9.1</p>
1959 <h4 id="_altos_11">E.12.1. AltOS</h4>
1963 <p>Add support for TeleMetrum v3.0</p>
1966 <p>Fix accel cal value when changing EasyMega v2.0 pad orientation</p>
1969 <p>Correct EasyMega v2.0 magnetometer data axes</p>
1972 <p>Fix EasyMega v2.0 idle monitor display of IMU data</p>
1975 <p>Report all sensor failures at power-up time.</p>
1981 <h4 id="_altosui_telegps_micropeak_2">E.12.2. AltosUI, TeleGPS, MicroPeak</h4>
1985 <p>Display error message when attempting to graph unknown format file.</p>
1988 <p>Make it possible to disable APRS once enabled.</p>
1991 <p>Display some data for point near cursor in map tab.</p>
1994 <p>Support upgrading devices from pre-1.8 firmware</p>
1997 <p>Wait for Windows to prepare new devices during firmware
1998 upgrade. This should avoid the “COMxx: open failed” message.</p>
2002 <div style="page-break-after: always;"></div>
2006 <h3 id="_release_notes_for_version_1_9">E.13. Release Notes for Version 1.9</h3>
2007 <div class="paragraph">
2011 <h4 id="_altos_12">E.13.1. AltOS</h4>
2015 <p>Add support for EasyMega v2.0</p>
2018 <p>Replace C library for ARM devices</p>
2021 <p>Remove support for 8051-based devices and SDCC compiler</p>
2027 <h4 id="_altosui_telegps_micropeak_3">E.13.2. AltosUI, TeleGPS, MicroPeak</h4>
2031 <p>Select ROM images based on product name when reflashing</p>
2034 <p>Fix TeleGPS v2 battery voltage display</p>
2038 <div style="page-break-after: always;"></div>
2042 <h3 id="_release_notes_for_version_1_8_7">E.14. Release Notes for Version 1.8.7</h3>
2043 <div class="paragraph">
2044 <p>Version 1.8.7</p>
2047 <h4 id="_altos_13">E.14.1. AltOS</h4>
2051 <p>Include TeleMega v3.0 firmware</p>
2057 <h4 id="_altosui_telegps_micropeak_4">E.14.2. AltosUI, TeleGPS, MicroPeak</h4>
2061 <p>Poll for new devices while Device dialog is displayed</p>
2064 <p>Wait for device to re-appear when flashing new firmware</p>
2067 <p>Fetch correct TeleBT v4.0 RF calibration values from web
2068 site when reflashing.</p>
2071 <p>Change gyro headings in .csv files from x/y/z to
2075 <p>Add documentation about Packet Link mode</p>
2078 <p>Add documentation about forcing TeleMini RF parameters to
2082 <p>Create a proxy server for Google Maps to re-enable map
2086 <p>Fix Java version info in all distributed jar files so that
2087 applications will run with standard Mac OS X Java.</p>
2090 <p>Replace JavaApplicationStub for Mac OS X so that
2091 applications will run with Oracle Java.</p>
2095 <div style="page-break-after: always;"></div>
2099 <h3 id="_release_notes_for_version_1_8_6">E.15. Release Notes for Version 1.8.6</h3>
2100 <div class="paragraph">
2101 <p>Version 1.8.6</p>
2104 <h4 id="_altos_14">E.15.1. AltOS</h4>
2108 <p>Use maximum of 64 previous tilt values in pyro tilt tests</p>
2111 <p>Eliminate 100m height requirement for coast detection</p>
2114 <p>Change After Motor pyro check to be >= instead of ==</p>
2117 <p>Change Time since Boost to be Time since launch.</p>
2123 <h4 id="_altosui_telegps">E.15.2. AltosUI, TeleGPS</h4>
2127 <p>Clarify pyro test phrasing</p>
2130 <p>Remove ascending/descending from pyro config UI</p>
2133 <p>Fix accel calibration in Antenna Down mode</p>
2136 <p>Add mag sensor reporting for TeleMega v3 idle monitoring.</p>
2139 <p>Fix radio parameter saving at 2400 bps telmetry rate.</p>
2145 <h4 id="_micropeak">E.15.3. MicroPeak</h4>
2149 <p>Report altimeter-recorded maximum height value</p>
2153 <div style="page-break-after: always;"></div>
2157 <h3 id="_release_notes_for_version_1_8_5">E.16. Release Notes for Version 1.8.5</h3>
2158 <div class="paragraph">
2159 <p>Version 1.8.5 includes fixes to the ground software support
2160 for TeleBT v4, along with a few other minor updates.</p>
2163 <h4 id="_altos_15">E.16.1. AltOS</h4>
2167 <p>Fix startup beeps that indicate sensor failures.</p>
2173 <h4 id="_altosui_telegps_2">E.16.2. AltosUI, TeleGPS</h4>
2177 <p>When updating device firmware, make sure selected firmware
2178 matches target device.</p>
2181 <p>Correct Bluetooth device matching when looking for TeleBT
2186 <div style="page-break-after: always;"></div>
2190 <h3 id="_release_notes_for_version_1_8_4">E.17. Release Notes for Version 1.8.4</h3>
2191 <div class="paragraph">
2192 <p>Version 1.8.4 includes support for EasyMini version 2.0</p>
2195 <h4 id="_altos_16">E.17.1. AltOS</h4>
2199 <p>Support for EasyMini version 2.0 hardware.</p>
2203 <div style="page-break-after: always;"></div>
2207 <h3 id="_release_notes_for_version_1_8_3">E.18. Release Notes for Version 1.8.3</h3>
2208 <div class="paragraph">
2209 <p>Version 1.8.3 includes support for TeleMega version 3.0 along
2210 with two important flight computer fixes. This version also
2211 changes KML export data to make Tripoli Record reporting
2212 better and some updates to graph presentation and data
2216 <h4 id="_altos_17">E.18.1. AltOS</h4>
2218 <h5 id="_altos_new_features">AltOS New Features</h5>
2222 <p>Support for TeleMega version 3.0 hardware.</p>
2228 <h5 id="_altos_bug_fixes">AltOS Bug Fixes</h5>
2232 <p>Ground testing EasyMega and TeleMega additional pyro
2233 channels could result in a sticky 'fired' status which would
2234 prevent these channels from firing on future flights.</p>
2237 <p>Corrupted flight log records could prevent future flights
2238 from capturing log data.</p>
2241 <p>Fixed saving of pyro configuration that ended with
2249 <h4 id="_altosui_and_telegps_applications">E.18.2. AltosUI and TeleGPS Applications</h4>
2251 <h5 id="_altosui_new_features">AltosUI New Features</h5>
2255 <p>Support for TeleMega version 3.0.</p>
2258 <p>Graph lines have improved appearance to make them easier to
2259 distinguish. Markers may be placed at data points to show
2260 captured recorded data values.</p>
2263 <p>Graphing offers the ability to adjust the smoothing of
2264 computed speed and acceleration data.</p>
2267 <p>The download dialog now offers to graph new flights, checks
2268 for existing files to avoid overwriting data and reports if
2269 there are checksum errors in the downloaded data.</p>
2275 <h5 id="_altosuitelegps_bug_fixes">AltosUI/TeleGPS Bug Fixes</h5>
2279 <p>Restore TeleGPS tracking behavior.</p>
2282 <p>Display flight computer call sign and serial number in
2283 Monitor Idle mode instead of ground station values.</p>
2289 <h5 id="_altosui_and_telegps_changes">AltosUI and TeleGPS Changes</h5>
2293 <p>KML export now reports both barometric and GPS altitude data
2294 to make it more useful for Tripoli record reporting.</p>
2297 <p>CSV export now includes TeleMega/EasyMega pyro voltages and
2302 <div style="page-break-after: always;"></div>
2307 <h3 id="_release_notes_for_version_1_8_2">E.19. Release Notes for Version 1.8.2</h3>
2308 <div class="paragraph">
2309 <p>Version 1.8.2 includes support for TeleGPS version 2.0 along
2310 with accelerometer recalibration support in AltosUI.</p>
2312 <div class="paragraph">
2313 <p>1.8.2 also contains a couple of minor fixes for AltosUI when
2314 analyzing saved data files.</p>
2317 <h4 id="_altos_18">E.19.1. AltOS</h4>
2318 <div class="paragraph">
2319 <p>AltOS New Features</p>
2324 <p>Support for TeleGPS version 2.0 hardware.</p>
2330 <h4 id="_altosui_and_telegps_applications_2">E.19.2. AltosUI and TeleGPS Applications</h4>
2331 <div class="paragraph">
2332 <p>AltosUI and TeleGPS New Features</p>
2337 <p>Support for TeleGPS version 2.0.</p>
2340 <p>Accelerometer re-calibration user interface.</p>
2344 <div class="paragraph">
2345 <p>AltosUI and TeleGPS Bug Fixes</p>
2350 <p>Prevent some crashes when reading older saved flight data
2351 for graphing or KML export.</p>
2355 <div style="page-break-after: always;"></div>
2359 <h3 id="_release_notes_for_version_1_8_1">E.20. Release Notes for Version 1.8.1</h3>
2360 <div class="paragraph">
2361 <p>Version 1.8.1 includes an important bug fix for Apogee Lockout
2362 operation in all flight computers. Anyone using this option
2363 must update firmware.</p>
2365 <div class="paragraph">
2366 <p>This release also contains a change in how flight computers
2367 with accelerometers deal with speeds around and above Mach
2368 1. In previous versions, the flight computer would completely
2369 disregard the barometric sensor above 330m/s (around Mach
2370 1). Now, the data from the barometric sensor is reduced in
2371 effect without ever going away entirely. This prevents early
2372 drogue deployment for flights which spend considerable time
2375 <div class="paragraph">
2376 <p>1.8.1 also contains a couple of minor fixes for AltosUI when
2377 analyzing saved data files.</p>
2380 <h4 id="_altos_19">E.20.1. AltOS</h4>
2381 <div class="paragraph">
2382 <p>AltOS Bug Fixes</p>
2387 <p>Handle time value wrapping in Apogee Lockout
2388 correctly. Without this, apogee lockout would sometimes
2389 prevent any drogue charge from firing.</p>
2392 <p>Change Kalman filter on flight computers with accelerometer
2393 to continue using the barometric sensor even at high speeds
2394 to avoid unintentional drogue deployment during
2401 <h4 id="_altosui_and_telegps_applications_3">E.20.2. AltosUI and TeleGPS Applications</h4>
2402 <div class="paragraph">
2403 <p>AltosUI New Features</p>
2408 <p>Add new 'Huge' font size to make text even bigger on high
2409 resolution monitors.</p>
2413 <div class="paragraph">
2414 <p>AltosUI Bug Fixes</p>
2419 <p>Prevent some crashes when reading older saved flight data
2420 for graphing or KML export.</p>
2423 <p>Load frequency preference at startup. The loading code was
2424 broken, so you’d see only the default frequencies.</p>
2428 <div style="page-break-after: always;"></div>
2432 <h3 id="_release_notes_for_version_1_8">E.21. Release Notes for Version 1.8</h3>
2433 <div class="paragraph">
2434 <p>Version 1.8 includes support for our new TeleBT v4.0 ground
2435 station, updates for data analysis in our ground station
2436 software and bug fixes in in the flight software for all our
2437 boards and ground station interfaces.</p>
2440 <h4 id="_altos_20">E.21.1. AltOS</h4>
2441 <div class="paragraph">
2442 <p>AltOS New Features</p>
2447 <p>Add support for TeleBT v4.0 boards.</p>
2453 <h4 id="_altosui_and_telegps_applications_4">E.21.2. AltosUI and TeleGPS Applications</h4>
2454 <div class="paragraph">
2455 <p>AltosUI New Features</p>
2460 <p>Add support for TeleBT v4.0 hardware</p>
2463 <p>Rewrite graphing and export functions. This code now handles
2464 each data series separately so that graphs are drawn
2465 correctly. Smoothing now uses a filter that looks both
2466 forward and backwards in time to make computed speed and
2467 acceleration data more accurate.</p>
2471 <div class="paragraph">
2472 <p>AltosUI Bug Fixes</p>
2477 <p>Correct axis labeling of magnetic sensor in TeleMega and
2478 EasyMega. The Y and Z axes were flipped.</p>
2482 <div style="page-break-after: always;"></div>
2486 <h3 id="_release_notes_for_version_1_7">E.22. Release Notes for Version 1.7</h3>
2487 <div class="paragraph">
2488 <p>Version 1.7 includes support for our new TeleMini v3.0
2489 flight computer and bug fixes in in the flight software for all our boards
2490 and ground station interfaces.</p>
2493 <h4 id="_altos_21">E.22.1. AltOS</h4>
2494 <div class="paragraph">
2495 <p>AltOS New Features</p>
2500 <p>Add support for TeleMini v3.0 boards.</p>
2504 <div class="paragraph">
2510 <p>Fix interrupt priorities on STM32L processors. Run timer
2511 interrupt at lowest priority so that device interrupts get
2518 <h4 id="_altosui_and_telegps_applications_5">E.22.2. AltosUI and TeleGPS Applications</h4>
2519 <div class="paragraph">
2520 <p>AltosUI New Features</p>
2525 <p>Add support for TeleMini v3.0 hardware</p>
2529 <div style="page-break-after: always;"></div>
2533 <h3 id="_release_notes_for_version_1_6_8">E.23. Release Notes for Version 1.6.8</h3>
2534 <div class="paragraph">
2535 <p>Version 1.6.8 fixes a TeleMega and TeleMetrum v2.0 bug where
2536 the device could stop logging data and transmitting
2537 telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum
2538 v2.0 users should update their flight firmware.</p>
2541 <h4 id="_altos_22">E.23.1. AltOS</h4>
2542 <div class="paragraph">
2548 <p>Fix STM32L DMA driver to work around STM32L SoC DMA priority
2549 issue t lock-up in the logging or radio code, either of
2550 which could stop data logging and telemetry.</p>
2553 <p>Avoid having TeleBT battery status values smash telemetry
2554 packet data by holding a lock during both operations.</p>
2557 <p>Don’t start reporting 'flight 0' when the log fills in
2562 <div class="paragraph">
2563 <p>AltOS changes:</p>
2568 <p>Flash LEDS on all products briefly during power up so that
2569 they can be tested during production.</p>
2575 <h4 id="_altosui_telegps_and_altosdroid_applications">E.23.2. AltosUI, TeleGPS and AltosDroid Applications</h4>
2576 <div class="paragraph">
2577 <p>AltosUI fixes:</p>
2582 <p>Re-enable go/no-go entries after they’ve been disabled due
2583 to lack of data. If telemetry information is delayed when
2584 the Ui starts up, sometimes important fields would get
2585 disabled to never re-appear.</p>
2588 <p>Deal with ground station failure better during Configure
2589 Ground Station operation by cleaning up pending operations.</p>
2593 <div style="page-break-after: always;"></div>
2597 <h3 id="_release_notes_for_version_1_6_5">E.24. Release Notes for Version 1.6.5</h3>
2598 <div class="paragraph">
2599 <p>Version 1.6.5 fixes a TeleMega and TeleMetrum v2.0 bug where
2600 the device would often stop logging data and transmitting
2601 telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum
2602 v2.0 users should update their flight firmware.</p>
2605 <h4 id="_altos_23">E.24.1. AltOS</h4>
2606 <div class="paragraph">
2612 <p>Fix STM32L SPI driver to prevent lock-up in the logging or
2613 radio code, either of which could stop data logging and
2614 telemetry. Found and characterized by Chuck Haskin, who also
2615 tested the new firmware before release.</p>
2621 <h4 id="_altosui_telegps_and_altosdroid_applications_2">E.24.2. AltosUI, TeleGPS and AltosDroid Applications</h4>
2622 <div class="paragraph">
2623 <p>AltosUI fixes:</p>
2628 <p>Deliver firmward for TeleMega v2.0 and TeleBT v3.0 with
2629 Windows package.</p>
2633 <div style="page-break-after: always;"></div>
2637 <h3 id="_release_notes_for_version_1_6_4">E.25. Release Notes for Version 1.6.4</h3>
2638 <div class="paragraph">
2639 <p>Version 1.6.4 fixes a bluetooth communication problem with
2640 TeleBT v1.0 devices, along with some altosui and altosdroid
2641 minor nits. It also now ships firmware for some newer devices.</p>
2644 <h4 id="_altos_24">E.25.1. AltOS</h4>
2645 <div class="paragraph">
2651 <p>Fix hardware flow control on TeleBT v1.0. Hardware RTS/CTS
2652 doesn’t seem to work, switch from using the hardware to
2653 driving these pins with software.</p>
2656 <p>Fix ARM USB drivers to deal with OS restarts. Needed to
2657 reset all USB-related state when the USB bus is reset. These
2658 fixes affect all STM32L, STM32F0 and LPC11U14 based devices.</p>
2664 <h4 id="_altosui_telegps_and_altosdroid_applications_3">E.25.2. AltosUI, TeleGPS and AltosDroid Applications</h4>
2665 <div class="paragraph">
2666 <p>AltosUI, TeleGPS and AltosDroid New Features:</p>
2671 <p>Automatically switch from meters or feet to kilometers or
2672 miles for distance units.</p>
2675 <p>Add Monitor Idle mode to TeleGPS application.</p>
2679 <div class="paragraph">
2680 <p>AltosUI, TeleGPS and AltosDroid Fixes:</p>
2685 <p>Abort map preloading when the preload map dialog is closed.</p>
2688 <p>In AltosDroid, Don’t reconnect to last device if the user
2689 had disconnected it the last time the application was
2696 <h4 id="_documentation">E.25.3. Documentation</h4>
2700 <p>Mention TeleMega v2.0 in hardware specs table.</p>
2703 <p>Document TeleGPS RF output in telegps manual.</p>
2710 <h3 id="_release_notes_for_version_1_6_3">E.26. Release Notes for Version 1.6.3</h3>
2711 <div class="paragraph">
2712 <p>Version 1.6.3 adds idle mode to AltosDroid and has bug fixes
2713 for our host software on desktops, laptops an android devices
2714 along with BlueTooth support for Windows.</p>
2717 <h4 id="_altos_25">E.26.1. AltOS</h4>
2718 <div class="paragraph">
2724 <p>Fix hardware flow control on TeleBT v3.0. RTS/CTS is
2725 wired backwards on this board, switch from using the
2726 hardware to driving these pins with software.</p>
2732 <h4 id="_altosui_and_telegps_applications_6">E.26.2. AltosUI and TeleGPS Applications</h4>
2733 <div class="paragraph">
2734 <p>AltosUI and TeleGPS New Features:</p>
2739 <p>Add BlueTooth support for Windows operating system. This
2740 supports connections to TeleBT over BlueTooth rather than
2745 <div class="paragraph">
2746 <p>AltosUI and TeleGPS Fixes:</p>
2751 <p>Change Java detection and install on Windows. Detection is
2752 now done by looking for the 'javaw.exe' program, and
2753 installation by opening a browser on the java.com web site.</p>
2756 <p>Delay polling while the Fire Igniters is visible to allow
2757 for TeleMega to report back complete status over the radio.</p>
2760 <p>Disallow changing RF calibration numbers in the
2761 configuration UI. There’s no good reason to change this from
2762 the field, and recovering is really hard if you haven’t
2763 written down the right number.</p>
2766 <p>Fix USB device discovery on Mac OS X El Capitan. This makes
2767 the connected Altus Metrum USB devices appear again.</p>
2770 <p>Fix acceleration data presented in MonitorIdle mode for
2771 TeleMetrum v2.0 flight computers.</p>
2777 <h4 id="_altosdroid_5">E.26.3. AltosDroid</h4>
2778 <div class="paragraph">
2779 <p>AltosDroid new features:</p>
2784 <p>Monitor Idle mode. Check state of flight computer while in
2785 idle mode over the radio link</p>
2788 <p>Fire Igniters. Remotely fire ignires for recovery system
2792 <p>Remote reboot. Cause the flight computer to reboot over the
2793 radio link. This provides a method for switching the flight
2794 computer from idle to flight mode without needing to reach
2795 the power switch.</p>
2798 <p>Configurable frequency menu. Change the set of available
2799 frequencies and provide more descriptive names.</p>
2803 <div class="paragraph">
2804 <p>AltosDroid bug fixes:</p>
2809 <p>Don’t set target location if GPS hasn’t locked yet.</p>
2812 <p>Fix saving target states so they can be reloaded when the
2813 application restarts. When the application is shut down and
2814 restarted, all previous target state information will be
2815 restored (including GPS position if available).</p>
2818 <p>Fix crash on some Android devices for offline maps when
2819 changing the map scale or location.</p>
2822 <p>Don’t require USB OTG support. This kept the latest
2823 AltosDroid from being offered on devices without USB device
2824 support, although it can work without that just fine using
2828 <p>Don’t require bluetooth to be enabled. This allows the
2829 application to operate with USB devices or just show old
2830 data without turning on the bluetooth radio.</p>
2833 <p>Recover old tracker positions when restarting
2834 application. This finally allows you to safely stop and
2835 restart the application without losing the last known
2836 location of any tracker.</p>
2842 <h4 id="_documentation_2">E.26.4. Documentation</h4>
2846 <p>Document TeleMega and EasyMega additional pyro channel
2847 continuity audio alert pattern.</p>
2851 <div style="page-break-after: always;"></div>
2855 <h3 id="_release_notes_for_version_1_6_2">E.27. Release Notes for Version 1.6.2</h3>
2856 <div class="paragraph">
2857 <p>Version 1.6.2 includes support for our updated TeleMega v2.0
2858 product and bug fixes in in the flight software for all our boards
2859 and ground station interfaces.</p>
2862 <h4 id="_altos_26">E.27.1. AltOS</h4>
2863 <div class="paragraph">
2864 <p>AltOS New Features:</p>
2869 <p>Add support for TeleMega v2.0 boards.</p>
2872 <p>Add PWM servo driver. There’s no higher level code using
2873 this yet, but the driver allows testing of the TeleMega v2.0
2874 servo output connector.</p>
2878 <div class="paragraph">
2884 <p>Slow down telemetry packets to allow receiver to keep
2891 <h4 id="_altosui_and_telegps_applications_7">E.27.2. AltosUI and TeleGPS Applications</h4>
2892 <div class="paragraph">
2893 <p>AltosUI and TeleGPS Fixes:</p>
2898 <p>Fix post-flight orientation computation when processing
2899 TeleMega and EasyMega eeprom data files.</p>
2902 <p>Capture complete eeprom data even when there are invalid
2903 entries in the data. This keeps reading eeprom contents and
2904 writing the associated .eeprom file when an error is detected.</p>
2910 <h4 id="_documentation_3">E.27.3. Documentation</h4>
2911 <div class="paragraph">
2912 <p>We spent a bunch of time trying to improve our documentation</p>
2917 <p>HTML versions now have a table of contents on the left side.</p>
2920 <p>EasyMini now has its own shorter manual.</p>
2923 <p>Provide links between sections in each document.</p>
2926 <p>Lots of minor rewriting and restructuring to avoid
2927 duplication of information</p>
2931 <div style="page-break-after: always;"></div>
2935 <h3 id="_release_notes_for_version_1_6_1">E.28. Release Notes for Version 1.6.1</h3>
2936 <div class="paragraph">
2937 <p>Version 1.6.1 includes support for our updated TeleBT v3.0
2938 product and bug fixes in in the flight software for all our boards
2939 and ground station interfaces.</p>
2942 <h4 id="_altos_27">E.28.1. AltOS</h4>
2943 <div class="paragraph">
2944 <p>AltOS New Features:</p>
2949 <p>Add support for TeleBT v3.0 boards.</p>
2952 <p>Add support for uncompressed APRS data, providing support
2953 for older APRS receivers. Uncompressed APRS data is less
2954 precise, takes more bandwidth and doesn’t have integrated
2959 <div class="paragraph">
2965 <p>Make TeleDongle and TeleBT more tolerant of data rate
2966 variations from transmitting devices.</p>
2972 <h4 id="_altosui_and_telegps_applications_8">E.28.2. AltosUI and TeleGPS Applications</h4>
2973 <div class="paragraph">
2974 <p>AltosUI and TeleGPS New Features:</p>
2979 <p>Add map to Monitor Idle display. It’s nice to be able to
2980 verify that maps are working, instead of needing to use
2985 <div class="paragraph">
2986 <p>AltosUI and TeleGPS Fixes:</p>
2991 <p>Fix frequency configuration to round values instead of
2992 truncate them, avoiding a common 1kHz error in the setting.</p>
2995 <p>Turn the Windows stub into a more useful program that can
2996 launch the application with parameters so that file manager
2997 icons work more reliably.</p>
3000 <p>Force KML export to use a C locale so that numbers are
3001 formatted with '.' instead of ',' for a decimal separator in
3005 <p>Preload map tiles based on distance rather than number of
3006 tiles; this means you get the same resolution covering the
3007 entire area, rather than having high resolution near the
3008 center and low resolution further away.</p>
3011 <p>Allow configuration of frequency and callsign in Monitor
3015 <p>Fix layout weirdness when resizing windows on
3016 Windows. Windows shouldn’t have giant blank spaces around
3017 the useful content anymore.</p>
3020 <p>Fix layout weirdness when resizing windows on
3021 Windows. Windows shouldn’t have giant blank spaces around
3022 the useful content anymore.</p>
3025 <p>Use a longer filter for descent speed values. This should
3026 provide something more useful on the display, although it
3027 will take longer to respond to changes now.</p>
3030 <p>Make Replay Flight run in realtime again. It had been set to
3031 run at 10x speed by mistake.</p>
3037 <h4 id="_altosdroid_6">E.28.3. AltosDroid</h4>
3038 <div class="paragraph">
3039 <p>AltosDroid New Features:</p>
3044 <p>Add offline map support using mapping code from AltosUI.</p>
3047 <p>Support TeleDongle (and TeleBT via USB) on devices
3048 supporting USB On-The-Go.</p>
3051 <p>Display additional TeleMega pyro channel status in Pad tab.</p>
3054 <p>Switch between metric and imperial units.</p>
3057 <p>Monitor TeleBT battery voltage.</p>
3060 <p>Track multiple devices at the same time, selecting between
3061 them with a menu or using the map.</p>
3064 <p>Add hybrid, satellite and terrain map types.</p>
3068 <div class="paragraph">
3069 <p>AltosDroid Fixes:</p>
3074 <p>Use standard Android display conventions so that a menu
3075 button is available in the application title bar.</p>
3078 <p>Adjust layout to work on large and small screens; shrinking
3079 the go/no-go lights in smaller environments to try and make
3080 everything visible.</p>
3083 <p>Make voice announcements depend on current tab.</p>
3086 <p>Compute adjustment to current travel direction while in
3087 motion towards rocket.</p>
3091 <div style="page-break-after: always;"></div>
3095 <h3 id="_release_notes_for_version_1_6">E.29. Release Notes for Version 1.6</h3>
3096 <div class="paragraph">
3097 <p>Version 1.6 includes support for our updated TeleDongle v3.0
3098 product and bug fixes in in the flight software for all our boards
3099 and ground station interfaces.</p>
3102 <h4 id="_altos_28">E.29.1. AltOS</h4>
3103 <div class="paragraph">
3104 <p>AltOS New Features</p>
3109 <p>Add support for TeleDongle v3.0 boards.</p>
3113 <div class="paragraph">
3119 <p>Don’t beep out the continuity twice by accident in idle mode.
3120 If the battery voltage report takes longer than the initialiation
3121 sequence, the igniter continuity would get reported twice.</p>
3124 <p>Record all 32 bits of gyro calibration data in TeleMega and
3125 EasyMega log files. This fixes computation of the gyro rates
3129 <p>Change TeleDongle LED usage. Green LED flashes when valid
3130 packet is received. Red LED flashes when invalid packet is
3134 <p>Replace LPC11U14 SPI driver with non-interrupt version. The
3135 interrupt code would occasionally wedge on long transfers
3136 if interrupts were blocked for too long. This affects all
3137 released TeleGPS products; if you have a TeleGPS device,
3138 you’ll want to reflash the firmware.</p>
3144 <h4 id="_altosui_and_telegps_applications_9">E.29.2. AltosUI and TeleGPS Applications</h4>
3145 <div class="paragraph">
3146 <p>AltosUI and TeleGPS New Features</p>
3151 <p>Compute tilt angle from TeleMega and EasyMega log
3152 files. This duplicates the quaternion-based angle tracking
3153 code from the flight firmware inside the ground station
3154 software so that post-flight analysis can include evaluation
3155 of the tilt angle.</p>
3158 <p>Shows the tool button window when starting with a data file
3159 specified. This means that opening a data file from the file
3160 manager will now bring up the main window to let you operate
3161 the whole application.</p>
3165 <div class="paragraph">
3166 <p>AltosUI Fixes</p>
3171 <p>Show the 'Connecting' dialog when using Monitor Idle. Lets
3172 you cancel the Monitor Idle startup when connecting over the
3176 <p>Make 'Monitor Idle' work for TeleGPS devices when connected
3177 over USB. It’s nice for testing without needing to broadcast
3181 <p>Use different Windows API to discover USB devices. This
3182 works better on my Windows 7 box, and will be used if the
3183 older API fails to provide the necessary information.</p>
3186 <p>Look in more places in the registry to try and identify the
3187 installed Java version on Windows. If you install the
3188 default 32-bit version of Windows on a 64-bit OS, the Java
3189 registry information is hiding \SOFTWARE\Wow6432Node for
3193 <p>Fix file association on Windows by searching for the
3194 javaw.exe program instead of assuming it is in
3195 %SYSTEMROOT%. This makes double-clicking on Altus Metrum
3196 data files in the file manager work correctly.</p>
3199 <p>When replaying a file, put 'done' in the Age field when we
3200 reach the end of the file, instead of continuing to count forever.</p>
3203 <p>In the Scan Channels code, wait for five seconds if we see
3204 any packet. This is needed because AltOS now sends the
3205 callsign, serial number and flight number only once every
3206 five seconds these days.</p>
3209 <p>In the Scan Channels code, reset pending flight state
3210 information each time we change channels. This avoids having
3211 flight computers appear on multiple frequencies by accident.</p>
3215 <div style="page-break-after: always;"></div>
3219 <h3 id="_release_notes_for_version_1_5">E.30. Release Notes for Version 1.5</h3>
3220 <div class="paragraph">
3221 <p>Version 1.5 is a major release. It includes support for our new
3222 EasyMega product, new features and bug fixes in in the flight
3223 software for all our boards and the AltosUI ground station</p>
3226 <h4 id="_altos_29">E.30.1. AltOS</h4>
3227 <div class="paragraph">
3228 <p>AltOS New Features</p>
3233 <p>Add support for EasyMega boards.</p>
3236 <p>Make the APRS SSID be configurable. This lets you track
3237 different rockets on the same receiver without getting
3238 things mixed up.</p>
3241 <p>Report extra pyro channel continuity state on EasyMega and
3242 TeleMega via the beeper. This lets you easily verify flight
3243 readiness on these boards after powering up the electronics
3247 <p>Add lower telemetry data rates (2400 and 9600 bps) to
3248 increase telemetry radio range. This reduces the amount of
3249 data received as well as increasing battery consumption in
3250 the transmitter.</p>
3253 <p>Change TeleGPS to have only a single log, and append new
3254 data to it rather than using seperate per-flight logs. This
3255 avoids accidentally filling up log storage by turning
3256 TeleGPS on/off several times.</p>
3260 <div class="paragraph">
3266 <p>Increase the maximum range for altitude values from +/-32767m
3267 to +/-2147483647m, allowing the flight computers to function
3268 correctly above the 32km level.</p>
3271 <p>Continuously test pyro firing conditions during delay stage,
3272 inhibiting the pyro channel if the test fails. This prevents
3273 firing pyro charges where the conditions were good before
3274 the delay, but become bad before the delay expires.</p>
3277 <p>Allow negative numbers in pyro configuration values. This
3278 lets you specify things like descending speed or
3285 <h4 id="_altosui_and_telegps_applications_10">E.30.2. AltosUI and TeleGPS Applications</h4>
3286 <div class="paragraph">
3287 <p>AltosUI and TeleGPS New Features</p>
3292 <p>Support telemetry baud rate selection. Adds menus to
3293 the flight monitoring and configuration for baud rate
3297 <p>Support APRS SSID configuration.</p>
3300 <p>Integrate with file managers. This provides icons for all of
3301 our file types and associates our application with the files
3302 so that using a file manager to open a AltOS data file
3303 results in launching our application.</p>
3307 <div class="paragraph">
3308 <p>AltosUI Fixes</p>
3313 <p>Make the 'Graph' button on the landed tab work again.</p>
3316 <p>Make tests for Java on Windows a bit smarter, and also
3317 provide the user with the option to skip installing Java for
3318 cases where we just can’t figure out what version is installed.</p>
3322 <div style="page-break-after: always;"></div>
3326 <h3 id="_release_notes_for_version_1_4_2">E.31. Release Notes for Version 1.4.2</h3>
3327 <div class="paragraph">
3328 <p>Version 1.4.2 is a minor release. It fixes Java-related install issues on
3332 <h4 id="_altosui_and_telegps_applications_11">E.31.1. AltosUI and TeleGPS Applications</h4>
3333 <div class="paragraph">
3334 <p>Windows Install Fixes</p>
3339 <p>Checks for Java installation data in more registry locations.</p>
3342 <p>Allows user to bypass Java installation in case the
3343 detection fails.</p>
3347 <div style="page-break-after: always;"></div>
3351 <h3 id="_release_notes_for_version_1_4_1">E.32. Release Notes for Version 1.4.1</h3>
3352 <div class="paragraph">
3353 <p>Version 1.4.1 is a minor release. It fixes install issues on
3354 Windows and provides the missing TeleMetrum V2.0 firmware. There
3355 aren’t any changes to the firmware or host applications at
3356 all. All Windows users will want to upgrade to get the signed
3357 driver, but Mac and Linux users who do not need the TeleMetrum
3358 V2.0 firmware image will not need to upgrade.</p>
3361 <h4 id="_altosui_and_telegps_applications_12">E.32.1. AltosUI and TeleGPS Applications:</h4>
3362 <div class="paragraph">
3363 <p>Windows Install Fixes</p>
3368 <p>Provide signed Windows driver files. This should avoid any need to
3369 disable driver signature checking on Windows 7 or 8.</p>
3372 <p>Fix Java version detection and download. Previously, the
3373 installer would only look for Java 6 or 7 and insist on
3374 downloading its own Java bits if there was something else
3375 installed. Furthermore, the 64-bit Java link provided didn’t
3376 work for anyone other than Keith, making it impossible to
3377 install AltOS on any machine with Java SE 8 installed.</p>
3381 <div class="paragraph">
3387 <p>Include 1.4 firmware for TeleMetrum V2.0. None of the
3388 installers shipped this file. Now it’s included in the AltOS
3389 packages for Linux, Mac and Windows.</p>
3392 <p>Include Google Application Key for map downloading. The 1.4
3393 release didn’t have this key in the released version of the
3394 software, making map downloading fail for most people.</p>
3398 <div style="page-break-after: always;"></div>
3402 <h3 id="_release_notes_for_version_1_4">E.33. Release Notes for Version 1.4</h3>
3403 <div class="paragraph">
3404 <p>Version 1.4 is a major release. It includes support for our new
3405 TeleGPS product, new features and bug fixes in in the flight
3406 software for all our boards and the AltosUI ground station</p>
3409 <h4 id="_altos_30">E.33.1. AltOS</h4>
3410 <div class="paragraph">
3411 <p>AltOS new features:</p>
3416 <p>Add support for TeleGPS boards.</p>
3419 <p>Make the beeper tone configurable, making it
3420 possible to distinguish between two Altus Metrum
3421 products in the same ebay.</p>
3424 <p>Make the firing time for extra pyro channels
3425 configurable, allowing longer (or shorter) than the
3426 default 50ms. Only relevant for TeleMega at this
3431 <div class="paragraph">
3437 <p>Replace the 'dit dit dit' tones at startup with the
3438 current battery voltage, measured in tenths of a
3439 volt. This lets you check the battery voltage
3440 without needing telemetry, which is especially
3441 useful on EasyMini.</p>
3444 <p>Change state beeping to "Farnsworth spacing", which
3445 means they’re quite a bit faster than before, and so
3446 they take less time to send.</p>
3449 <p>Fix bug preventing the selection of the 'Flight
3450 State After' mode in pyro configuration.</p>
3453 <p>Fix bug where erasing flights would reset the flight
3454 number to 2 on TeleMega and TeleMetrum v2.</p>
3457 <p>Fix u-Blox GPS driver to mark course and speed data
3458 as being present.</p>
3464 <h4 id="_altosui_application">E.33.2. AltosUI Application</h4>
3465 <div class="paragraph">
3466 <p>AltosUI new features:</p>
3471 <p>Add zooming and new content types (terrain and road
3472 maps) to map view. Change map storage format from
3473 PNG to Jpeg, which saves a huge amount of disk
3474 space. You will need to re-download all of your
3475 pre-loaded map images.</p>
3478 <p>Add a distance measuring device to the maps
3479 view. Select this by using any button other than the
3480 left one, or by pressing shift or control on the
3481 keyboard while using the left button.</p>
3484 <p>Add new 'Ignitor' tab to the flight monitor display
3485 for TeleMega’s extra ignitors.</p>
3488 <p>Add additional ignitor firing marks and voltages to
3489 the graph so you can see when the ignitors fired,
3490 along with the ignitor voltages.</p>
3493 <p>Add GPS course, ground speed and climb rate as
3494 optional graph elements.</p>
3498 <div class="paragraph">
3499 <p>AltosUI fixes:</p>
3504 <p>When flashing new firmware, re-try opening the
3505 device as sometimes it takes a while for the
3506 underlying operating system to recognize that the
3507 device has rebooted in preparation for the flashing
3511 <p>Hide Tilt Angle in ascent tab for devices that don’t
3515 <p>Increase the width of data lines in the graphs to
3516 make them easier to read.</p>
3519 <p>Filter out speed and acceleration spikes caused by
3520 ejection charge firing when computing the maximum
3521 values. This provides a more accurate reading of
3525 <p>Fix EasyMini voltage displays. Early EasyMini
3526 prototypes used a 3.0V regulator, and AltosUI still
3527 used that value as the basis of the
3528 computation. Production EasyMini boards have always
3529 shipped with a 3.3V regulator. Also, purple EasyMini
3530 boards sensed the battery voltage past the blocking
3531 diode, resulting in a drop of about 150mV from the
3532 true battery voltage. Compensate for that when
3533 displaying the value.</p>
3536 <p>Display error message when trying to configure
3537 maximum flight log size while the flight computer
3538 still has flight data stored.</p>
3541 <p>Handle TeleMetrum and TeleMini eeprom files
3542 generated with pre-1.0 firmware. Those ancient
3543 versions didn’t report the log format, so just use
3544 the product name instead.</p>
3550 <h4 id="_telegps_application_2">E.33.3. TeleGPS Application</h4>
3554 <p>New application designed for use with TeleGPS boards.</p>
3557 <p>Shares code with AltosUI, mostly just trimmed down
3558 to focus on TeleGPS-related functions.</p>
3564 <h4 id="_documentation_4">E.33.4. Documentation</h4>
3565 <div class="paragraph">
3566 <p>Documentation changes:</p>
3571 <p>Re-create the drill template images; they should
3572 print correctly from Firefox at least. Ship these as
3573 individual PDF files so they’re easy to print.</p>
3576 <p>Add a description of the 'Apogee Lockout' setting,
3577 which prevents the apogee charge from firing for a
3578 configurable amount of time after boost.</p>
3588 <div id="footer-text">
3590 Last updated 2023-01-19 23:18:22 -0700
projects / web / altusmetrum / blob