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.20">
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.18,</span>
22 <span id="revdate">28 Apr 2024</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_18">E.1. Release Notes for Version 1.9.18</a></li>
82 <li><a href="#_release_notes_for_version_1_9_17">E.2. Release Notes for Version 1.9.17</a></li>
83 <li><a href="#_release_notes_for_version_1_9_16">E.3. Release Notes for Version 1.9.16</a></li>
84 <li><a href="#_release_notes_for_version_1_9_15">E.4. Release Notes for Version 1.9.15</a></li>
85 <li><a href="#_release_notes_for_version_1_9_14">E.5. Release Notes for Version 1.9.14</a></li>
86 <li><a href="#_release_notes_for_version_1_9_13">E.6. Release Notes for Version 1.9.13</a></li>
87 <li><a href="#_release_notes_for_version_1_9_12">E.7. Release Notes for Version 1.9.12</a></li>
88 <li><a href="#_release_notes_for_version_1_9_11">E.8. Release Notes for Version 1.9.11</a></li>
89 <li><a href="#_release_notes_for_version_1_9_10">E.9. Release Notes for Version 1.9.10</a></li>
90 <li><a href="#_release_notes_for_version_1_9_9">E.10. Release Notes for Version 1.9.9</a></li>
91 <li><a href="#_release_notes_for_version_1_9_8">E.11. Release Notes for Version 1.9.8</a></li>
92 <li><a href="#_release_notes_for_version_1_9_7">E.12. Release Notes for Version 1.9.7</a></li>
93 <li><a href="#_release_notes_for_version_1_9_6">E.13. Release Notes for Version 1.9.6</a></li>
94 <li><a href="#_release_notes_for_version_1_9_5">E.14. Release Notes for Version 1.9.5</a></li>
95 <li><a href="#_release_notes_for_version_1_9_4">E.15. Release Notes for Version 1.9.4</a></li>
96 <li><a href="#_release_notes_for_version_1_9_3">E.16. Release Notes for Version 1.9.3</a></li>
97 <li><a href="#_release_notes_for_version_1_9_1">E.17. Release Notes for Version 1.9.1</a></li>
98 <li><a href="#_release_notes_for_version_1_9">E.18. Release Notes for Version 1.9</a></li>
99 <li><a href="#_release_notes_for_version_1_8_7">E.19. Release Notes for Version 1.8.7</a></li>
100 <li><a href="#_release_notes_for_version_1_8_6">E.20. Release Notes for Version 1.8.6</a></li>
101 <li><a href="#_release_notes_for_version_1_8_5">E.21. Release Notes for Version 1.8.5</a></li>
102 <li><a href="#_release_notes_for_version_1_8_4">E.22. Release Notes for Version 1.8.4</a></li>
103 <li><a href="#_release_notes_for_version_1_8_3">E.23. Release Notes for Version 1.8.3</a></li>
104 <li><a href="#_release_notes_for_version_1_8_2">E.24. Release Notes for Version 1.8.2</a></li>
105 <li><a href="#_release_notes_for_version_1_8_1">E.25. Release Notes for Version 1.8.1</a></li>
106 <li><a href="#_release_notes_for_version_1_8">E.26. Release Notes for Version 1.8</a></li>
107 <li><a href="#_release_notes_for_version_1_7">E.27. Release Notes for Version 1.7</a></li>
108 <li><a href="#_release_notes_for_version_1_6_8">E.28. Release Notes for Version 1.6.8</a></li>
109 <li><a href="#_release_notes_for_version_1_6_5">E.29. Release Notes for Version 1.6.5</a></li>
110 <li><a href="#_release_notes_for_version_1_6_4">E.30. Release Notes for Version 1.6.4</a></li>
111 <li><a href="#_release_notes_for_version_1_6_3">E.31. Release Notes for Version 1.6.3</a></li>
112 <li><a href="#_release_notes_for_version_1_6_2">E.32. Release Notes for Version 1.6.2</a></li>
113 <li><a href="#_release_notes_for_version_1_6_1">E.33. Release Notes for Version 1.6.1</a></li>
114 <li><a href="#_release_notes_for_version_1_6">E.34. Release Notes for Version 1.6</a></li>
115 <li><a href="#_release_notes_for_version_1_5">E.35. Release Notes for Version 1.5</a></li>
116 <li><a href="#_release_notes_for_version_1_4_2">E.36. Release Notes for Version 1.4.2</a></li>
117 <li><a href="#_release_notes_for_version_1_4_1">E.37. Release Notes for Version 1.4.1</a></li>
118 <li><a href="#_release_notes_for_version_1_4">E.38. Release Notes for Version 1.4</a></li>
126 <div class="sectionbody">
127 <div id="logo" class="imageblock">
128 <div class="content">
129 <a class="image" href="https://altusmetrum.org"><img src="altusmetrum-oneline.svg" alt="Altus Metrum"></a>
135 <h2 id="_license">License</h2>
136 <div class="sectionbody">
137 <div class="paragraph">
138 <p>Copyright © 2024 Bdale Garbee and Keith Packard</p>
140 <div class="paragraph">
141 <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>
146 <h2 id="_acknowledgments">Acknowledgments</h2>
147 <div class="sectionbody">
148 <div class="paragraph">
149 <p>Thanks to Anthony (AJ) Towns for major contributions including
150 the TeleGPS graphing and site map code and associated documentation.
151 Free software means that our customers and friends can become our
152 collaborators, and we certainly appreciate this level of
155 <div class="paragraph">
156 <p>Have fun using these products, and we hope to meet all of you
157 out on the rocket flight line somewhere.</p>
159 <div class="verseblock">
160 <pre class="content">Bdale Garbee, KB0G
161 NAR #87103, TRA #12201</pre>
163 <div class="verseblock">
164 <pre class="content">Keith Packard, K7WQ
165 NAR #88757, TRA #12200</pre>
170 <h2 id="_telegps_quick_start_guide">1. TeleGPS Quick Start Guide</h2>
171 <div class="sectionbody">
172 <div class="paragraph">
173 <p>TeleGPS is designed to be easy to use. Requiring no external
174 components, flying takes just a few steps.</p>
176 <div class="olist arabic">
179 <p>First, download and install the software from
180 <a href="http://altusmetrum.org/AltOS" class="bare">http://altusmetrum.org/AltOS</a>. This will make sure that
181 you have the right device drivers installed.</p>
184 <p>Next, plug in the battery and USB cable and connect TeleGPS to
185 your computer. This will charge the battery and allow you to
186 configure the device.</p>
189 <p>Start the TeleGPS application and set the callsign and frequency
190 on your TeleGPS device; refer to <a href="#_configure_device">Configure Device</a> for instructions.</p>
193 <p>Unplug TeleGPS when the battery charger light goes green. This
194 will enable the radio and logging portions of the TeleGPS
198 <p>Connect TeleDongle to your computer and start TeleGPS or start
199 AltosDroid on your android device and connect to TeleBT. Set the
200 frequency to match the TeleGPS and you should be receiving telemetry.</p>
207 <h2 id="_using_telegps_hardware">2. Using TeleGPS Hardware</h2>
208 <div class="sectionbody">
210 <h3 id="_hooking_up_lithium_polymer_batteries">2.1. Hooking Up Lithium Polymer Batteries</h3>
211 <div class="paragraph">
212 <p>TeleGPS has a two pin JST PH series connector to connect up
213 a single-cell Lithium Polymer cell (3.7V nominal). You can
214 purchase matching batteries from the Altus Metrum store, or
215 other vendors, or you can make your own. Pin 1 of the
216 connector is positive, pin 2 is negative. Spark Fun sells a
217 cable with the connector attached, which they call a
218 <a href="https://www.sparkfun.com/products/9914">JST Jumper 2 Wire Assembly</a></p>
220 <div class="admonitionblock warning">
224 <div class="title">Warning</div>
227 Many RC vendors also sell lithium polymer batteries with
228 this same connector. All that we have found use the opposite
229 polarity, and if you use them that way, you will damage or
237 <h3 id="_on_board_data_recording">2.2. On-board Data Recording</h3>
238 <div class="paragraph">
239 <p>TeleGPS logs GPS data at a user-configurable
240 rate. Data are logged to a 2MB on-board flash memory
241 part, which can be partitioned into several
242 equal-sized blocks, one for each flight. 64kB of this
243 storage are reserved to hold configuration data,
244 leaving 1984kB for flight data.</p>
246 <div class="paragraph">
247 <p>The on-board flash is partitioned into separate flight
248 logs, each of a fixed maximum size. Increase the
249 maximum size of each log and you reduce the number of
250 flights that can be stored. Decrease the size and you
251 can store more flights.</p>
253 <div class="paragraph">
254 <p>To compute the amount of space needed for a single
255 log, you can divide the expected time (in seconds) by
256 the sample period (by default, 1 second per sample)
257 and then multiply the result by 32 bytes per
258 sample. For instance, a sample period of 1 second and
259 a flight lasting one hour will take 32 * 3600 = 115200
260 bytes. TeleGPS does try to reduce log space used by
261 not recording position information when it isn’t
262 moving, so actual space consumed may be less than
265 <div class="paragraph">
266 <p>The default size allows for four flights of 496kB
267 each, which provides over four hours of logging at 1
268 sample per second.</p>
270 <div class="paragraph">
271 <p>TeleGPS will not overwrite existing flight data, so be
272 sure to download flight data and erase it from the
273 onboard flash before it fills up. TeleGPS will still
274 report telemetry even if memory is full, so the only
275 thing you will lose is the on-board data log.</p>
279 <h3 id="_leds">2.3. LEDs</h3>
280 <div class="paragraph">
281 <p>TeleGPS v1.0 has a dual greed/red LED along the edge
282 towards the USB connector end of the board. This
283 indicates battery charging status while connected to
284 power over USB. When the red LED is lit, the battery
285 is charging. Once the battery is fully charged, the
286 red LED goes out and the green LED turns on. If both
287 LEDs are lit, something is probably wrong with the battery.</p>
289 <div class="paragraph">
290 <p>TeleGPS v2.0 has the same green/red battery charging
291 status LED and adds another green LED along the same
292 edge, towards end of the board with the 70cm
293 antenna. This green LED indicates GPS lock status — it
294 blinks once every three seconds when the GPS receiver
295 is locked and tracking position.</p>
299 <h3 id="_installation">2.4. Installation</h3>
300 <div class="paragraph">
301 <p>The battery connectors are a standard 2-pin JST
302 connector and match batteries sold by Spark Fun. These
303 batteries are single-cell Lithium Polymer batteries
304 that nominally provide 3.7 volts. Other vendors sell
305 similar batteries for RC aircraft using mating
306 connectors, however the polarity for those is
307 generally reversed from the batteries used by Altus
308 Metrum products. In particular, the Tenergy batteries
309 supplied for use in Featherweight flight computers are
310 not compatible with Altus Metrum flight computers or
311 battery chargers.</p>
313 <div class="admonitionblock warning">
317 <div class="title">Warning</div>
320 Check polarity and voltage before connecting any
321 battery not purchased from Altus Metrum or Spark
327 <div class="paragraph">
328 <p>TeleGPS uses an integrate GPS patch antenna and won’t
329 receive GPS signals if installed inside a metal or
330 carbon fiber compartment. Test GPS reception and
331 telemetry transmission with the system installed and
332 all other electronics powered up to verify signal
333 reception and make sure there isn’t any interference
334 from other systems.</p>
340 <h2 id="_telegps_application">3. TeleGPS Application</h2>
341 <div class="sectionbody">
342 <div class="paragraph">
343 <p>The TeleGPS application provides a graphical user interface for
344 interacting with the Altus Metrum product family. TeleGPS can
345 monitor telemetry data, configure devices and many other
346 tasks. The primary interface window is for displaying data
347 received over the telemetry link. There are additional
348 tasks available from the main window menu bar.</p>
351 <h3 id="_telemetry_monitoring">3.1. Telemetry Monitoring</h3>
352 <div class="paragraph">
353 <p>This is the window brought up when you start the
354 application. If you have a TeleDongle device connected
355 to the computer, it will automatically be selected for
356 telemetry monitoring</p>
358 <div class="paragraph">
359 <p>All telemetry data received are automatically recorded
360 in suitable log files. The name of the files includes
361 the current date and TeleGPS serial and flight
364 <div class="paragraph">
365 <p>The radio frequency being monitored by the TeleDongle
366 device is displayed at the top of the window. You can
367 configure the frequency by clicking on the frequency
368 box and selecting the desired frequency. The TeleGPS
369 application remembers the last frequency selected for
370 each TeleDongle and selects that automatically the
371 next time you use that device.</p>
373 <div class="paragraph">
374 <p>Below the TeleDongle frequency selector, the window
375 contains a few significant pieces of information about
376 the altimeter providing the telemetry data stream:</p>
381 <p>The configured call-sign</p>
384 <p>The device serial number</p>
387 <p>The flight number. TeleGPS remembers how many times
391 <p>The Received Signal Strength Indicator value. This
392 lets you know how strong a signal TeleDongle is
393 receiving. The radio inside TeleDongle operates down
394 to about -100dBm; weaker signals may not be
395 receivable. The packet link uses error detection and
396 correction techniques which prevent incorrect data
397 from being reported.</p>
400 <p>The age of the displayed data, in seconds since the
401 last successfully received telemetry packet. In
402 normal operation this will stay in the low single
403 digits. If the number starts counting up, then you
404 are no longer receiving data over the radio link
405 from the flight computer.</p>
409 <div class="paragraph">
410 <p>Finally, the largest portion of the window contains a set of
411 tabs, each of which contain some information about the TeleGPS
412 board. The final 'table' tab displays many of the raw telemetry
413 values in one place in a spreadsheet-like format.</p>
416 <h4 id="_map">3.1.1. Map</h4>
417 <div class="paragraph">
418 <p>The Map tab shows the TeleGPS track over time
419 on top of map data making it easy to locate
422 <div class="imageblock">
423 <div class="content">
424 <img src="telegps-map.png" alt="telegps map" width="400">
426 <div class="title">Figure 1. TeleGPS Map View</div>
428 <div class="paragraph">
429 <p>The map’s default scale is approximately 3m
430 (10ft) per pixel. The map can be dragged using
431 the left mouse button. The map will attempt to
432 keep the rocket roughly centered while data is
435 <div class="paragraph">
436 <p>You can adjust the style of map and the zoom
437 level with buttons on the right side of the
438 map window. You can draw a line on the map by
439 moving the mouse over the map with a button
440 other than the left one pressed, or by
441 pressing the left button while also holding
442 down the shift key. The length of the line in
443 real-world units will be shown at the start of
446 <div class="paragraph">
447 <p>Images are fetched automatically via the
448 Google Maps Static API, and cached on disk for
449 reuse. If map images cannot be downloaded, the
450 rocket’s path will be traced on a dark gray
451 background instead.</p>
453 <div class="paragraph">
454 <p>You can pre-load images for your favorite
455 launch sites before you leave home; check out
456 <a href="#_load_maps">Load Maps</a>.</p>
460 <h4 id="_location">3.1.2. Location</h4>
461 <div class="paragraph">
462 <p>The Location tab shows the raw GPS data
463 received from TeleGPS.</p>
465 <div class="imageblock">
466 <div class="content">
467 <img src="telegps-location.png" alt="telegps location" width="400">
469 <div class="title">Figure 2. TeleGPS Location View</div>
473 <h4 id="_status">3.1.3. Status</h4>
474 <div class="paragraph">
475 <p>The Status tab shows data relative to the
476 location of TeleGPS when the application first
477 received telemetry from it.</p>
479 <div class="imageblock">
480 <div class="content">
481 <img src="telegps-status.png" alt="telegps status" width="400">
483 <div class="title">Figure 3. TeleGPS Status View</div>
487 <h4 id="_table">3.1.4. Table</h4>
488 <div class="paragraph">
489 <p>The Table tab shows detailed information about
492 <div class="imageblock">
493 <div class="content">
494 <img src="telegps-table.png" alt="telegps table" width="400">
496 <div class="title">Figure 4. TeleGPS Information Table</div>
501 <h3 id="_telegps_menus">3.2. TeleGPS Menus</h3>
502 <div class="paragraph">
503 <p>TeleGPS has three or four menus at the top of
508 <dt class="hdlist1">File</dt>
510 <p>New Window, Graph Data, Export Data, Load Maps,
511 Preferences, Close and Exit</p>
513 <dt class="hdlist1">Monitor</dt>
515 <p>Connect Device, Disconnect and Scan Channels</p>
517 <dt class="hdlist1">Device</dt>
519 <p>Download Data, Configure Device and Flash Device</p>
521 <dt class="hdlist1">Frequency</dt>
523 <p>This shows the current monitoring frequency with a
524 drop-down menu listing other configured
525 frequencies. You can change the set of frequencies
526 shown here from the Preferences dialog. This menu is
527 only shown when the TeleGPS application is connected
528 to a TeleDongle or TeleBT device.</p>
533 <h4 id="_new_window">3.2.1. New Window</h4>
534 <div class="paragraph">
535 <p>This creates another telemetry monitoring window, in case
536 you have multiple TeleDongle devices connected to the
542 <h3 id="_graph_data">3.3. Graph Data</h3>
543 <div class="paragraph">
544 <p>The Graph tab shows a plot of the the GPS data
545 collected. The X axis is time in seconds; there are a
546 variety of Y axes available for different kinds of
547 data. This window also allows you to see some
548 statistics computed from the data, and an overall map
549 of the entire data record.</p>
552 <h4 id="_data_graph">3.3.1. Data Graph</h4>
553 <div class="imageblock">
554 <div class="content">
555 <img src="telegps-graph-graph.png" alt="telegps graph graph" width="400">
557 <div class="title">Figure 5. TeleGPS Graph</div>
561 <h4 id="_graph_configuration">3.3.2. Graph Configuration</h4>
562 <div class="imageblock">
563 <div class="content">
564 <img src="telegps-graph-configure.png" alt="telegps graph configure" width="400">
566 <div class="title">Figure 6. TeleGPS Graph Configuration</div>
568 <div class="paragraph">
569 <p>This selects which graph elements to show, and, at the
570 bottom, lets you switch between metric and imperial
575 <h4 id="_statistics">3.3.3. Statistics</h4>
576 <div class="imageblock">
577 <div class="content">
578 <img src="telegps-graph-stats.png" alt="telegps graph stats" width="400">
580 <div class="title">Figure 7. TeleGPS Statistics</div>
582 <div class="paragraph">
583 <p>Shows overall data computed from the flight.</p>
587 <h4 id="_map_2">3.3.4. Map</h4>
588 <div class="imageblock">
589 <div class="content">
590 <img src="telegps-graph-map.png" alt="telegps graph map" width="450">
592 <div class="title">Figure 8. TeleGPS Map</div>
594 <div class="paragraph">
595 <p>Shows a map of the area overlaid with the GPS track. As with
596 the telemetry monitoring window, you can select the style
597 of map and zoom level using buttons along the side;
598 you can scroll the map by dragging within the map pressing
599 the left button and you can draw a line to measure
600 distances using either the left button with the shift key,
601 or any other button.</p>
606 <h3 id="_export_data">3.4. Export Data</h3>
607 <div class="paragraph">
608 <p>This tool takes the raw data files and makes them
609 available for external analysis. When you select this
610 button, you are prompted to select a data file, which
611 can be either a .eeprom or .telem. The .eeprom files
612 contain higher resolution and more continuous data,
613 while .telem files contain receiver signal strength
614 information. Next, a second dialog appears which is
615 used to select where to write the resulting file. It
616 has a selector to choose between CSV and KML file
620 <h4 id="_comma_separated_value_format">3.4.1. Comma Separated Value Format</h4>
621 <div class="paragraph">
622 <p>This is a text file containing the data in a
623 form suitable for import into a spreadsheet or
624 other external data analysis tool. The first
625 few lines of the file contain the version and
626 configuration information from TeleGPS, then
627 there is a single header line which labels all
628 of the fields. All of these lines start with a
629 '#' character which many tools can be
630 configured to skip over.</p>
632 <div class="paragraph">
633 <p>The remaining lines of the file contain the
634 data, with each field separated by a comma and
635 at least one space. All of the sensor values
636 are converted to standard units, with the
637 barometric data reported in both pressure,
638 altitude and height above pad units.</p>
642 <h4 id="_keyhole_markup_language_for_google_earth">3.4.2. Keyhole Markup Language (for Google Earth)</h4>
643 <div class="paragraph">
644 <p>This is the format used by Google Earth to provide an overlay
645 within that application. With this, you can use Google Earth to
646 see the whole path in 3D.</p>
651 <h3 id="_load_maps">3.5. Load Maps</h3>
652 <div class="imageblock">
653 <div class="content">
654 <img src="load-maps.png" alt="load maps" width="500">
656 <div class="title">Figure 9. Load Maps Window</div>
658 <div class="paragraph">
659 <p>Before heading out to a new launch site, you can use
660 this to load satellite images in case you don’t have
661 internet connectivity at the site. Try not to wait
662 until the last minute, though, particularly if you’re
663 heading to a major launch. If too many people are
664 all trying to download map data at once, Google may
665 limit access until the next day.</p>
667 <div class="paragraph">
668 <p>There’s a drop-down menu of launch sites we know
669 about; if your favorites aren’t there, please let us
670 know the lat/lon and name of the site. The contents of
671 this list are actually downloaded from our server at
672 run-time, so as new sites are sent in, they’ll get
673 automatically added to this list. If the launch site
674 isn’t in the list, you can manually enter the lat/lon
677 <div class="paragraph">
678 <p>There are four different kinds of maps you can view;
679 you can select which to download by selecting as many
680 as you like from the available types:</p>
684 <dt class="hdlist1">Hybrid</dt>
686 <p>A combination of satellite imagery and road data. This
687 is the default view.</p>
689 <dt class="hdlist1">Satellite</dt>
691 <p>Just the satellite imagery without any annotation.</p>
693 <dt class="hdlist1">Roadmap</dt>
695 <p>Roads, political boundaries and a few geographic
698 <dt class="hdlist1">Terrain</dt>
700 <p>Contour intervals and shading that show hills and
705 <div class="paragraph">
706 <p>You can specify the range of zoom levels to download;
707 smaller numbers show more area with less
708 resolution. The default level, 0, shows about
709 3m/pixel. One zoom level change doubles or halves that
710 number. Larger zoom levels show more detail, smaller
711 zoom levels less.</p>
713 <div class="paragraph">
714 <p>The Map Radius value sets how large an area around the
715 center point to download. Select a value large enough
716 to cover any plausible flight from that site. Be aware
717 that loading a large area with a high maximum zoom
718 level can attempt to download a lot of data. Loading
719 hybrid maps with a 10km radius at a minimum zoom of -2
720 and a maximum zoom of 2 consumes about 120MB of
721 space. Terrain and road maps consume about 1/10 as
722 much space as satellite or hybrid maps.</p>
724 <div class="paragraph">
725 <p>Clicking the 'Load Map' button will fetch images from
726 Google Maps; note that Google limits how many images
727 you can fetch at once, so if you load more than one
728 launch site, you may get some gray areas in the map
729 which indicate that Google is tired of sending data to
730 you. Try again later.</p>
734 <h3 id="_preferences">3.6. Preferences</h3>
735 <div class="imageblock">
736 <div class="content">
737 <img src="telegps-preferences.png" alt="telegps preferences" width="230">
739 <div class="title">Figure 10. TeleGPS Preferences Window</div>
742 <h4 id="_voice_settings">3.6.1. Voice Settings</h4>
743 <div class="paragraph">
744 <p>TeleGPS provides voice announcements during
745 flight so that you can keep your eyes on the
746 sky and still get information about the
747 current flight status. However, sometimes you
748 don’t want to hear them.</p>
752 <dt class="hdlist1">Enable</dt>
754 <p>Turns all voice announcements on and off</p>
756 <dt class="hdlist1">Test Voice</dt>
758 <p>Plays a short message allowing you to verify
759 that the audio system is working and the volume settings
766 <h4 id="_log_directory">3.6.2. Log Directory</h4>
767 <div class="paragraph">
768 <p>TeleGPS logs all telemetry data and saves all
769 flash data to this directory. This
770 directory is also used as the staring point
771 when selecting data files for display or
774 <div class="paragraph">
775 <p>Click on the directory name to bring up a
776 directory choosing dialog, select a new
777 directory and click 'Select Directory' to
778 change where TeleGPS reads and writes data
783 <h4 id="_callsign">3.6.3. Callsign</h4>
784 <div class="paragraph">
785 <p>This value is transmitted in each command
786 packet sent from TeleDongle and received from
787 an altimeter. It is not used in telemetry
788 mode, as the callsign configured in the
789 altimeter board is included in all telemetry
790 packets. Configure this with the TeleGPS
791 operators call sign as needed to comply with
792 your local radio regulations.</p>
794 <div class="paragraph">
795 <p>Note that to successfully command a flight
796 computer over the radio (to configure the
797 altimeter, monitor idle, or fire pyro
798 charges), the callsign configured here must
799 exactly match the callsign configured in the
800 flight computer. This matching is case
805 <h4 id="_imperial_units">3.6.4. Imperial Units</h4>
806 <div class="paragraph">
807 <p>This switches between metric units (meters)
808 and imperial units (feet and miles). This
809 affects the display of values use during
810 flight monitoring, configuration, data
811 graphing and all of the voice
812 announcements. It does not change the units
813 used when exporting to CSV files, those are
814 always produced in metric units.</p>
818 <h4 id="_serial_debug">3.6.5. Serial Debug</h4>
819 <div class="paragraph">
820 <p>This causes all communication with a connected
821 device to be dumped to the console from which
822 TeleGPS was started. If you’ve started it from
823 an icon or menu entry, the output will simply
824 be discarded. This mode can be useful to debug
825 various serial communication issues.</p>
829 <h4 id="_font_size">3.6.6. Font size</h4>
830 <div class="paragraph">
831 <p>Selects the set of fonts used in the flight
832 monitor window. Choose between the small,
833 medium and large sets.</p>
837 <h4 id="_look_feel">3.6.7. Look & feel</h4>
838 <div class="paragraph">
839 <p>Switches between the available Java user
840 interface appearances. The default selection
841 is supposed to match the native window system
842 appearance for the target platform.</p>
846 <h4 id="_menu_position">3.6.8. Menu position</h4>
847 <div class="paragraph">
848 <p>Selects the initial position for the main
849 TeleGPS window that includes all of the
854 <h4 id="_map_cache_size">3.6.9. Map Cache Size</h4>
855 <div class="paragraph">
856 <p>Sets the number of map 'tiles' kept in memory
857 while the application is running. More tiles
858 consume more memory, but will make panning
859 around the map faster.</p>
863 <h4 id="_manage_frequencies">3.6.10. Manage Frequencies</h4>
864 <div class="paragraph">
865 <p>This brings up a dialog where you can
866 configure the set of frequencies shown in the
867 various frequency menus. You can add as many
868 as you like, or even reconfigure the default
869 set. Changing this list does not affect the
870 frequency settings of any devices, it only
871 changes the set of frequencies shown in the
877 <h3 id="_close">3.7. Close</h3>
878 <div class="paragraph">
879 <p>This closes the current window, leaving any other windows
880 open and the application running.</p>
884 <h3 id="_exit">3.8. Exit</h3>
885 <div class="paragraph">
886 <p>This closes all TeleGPS windows and terminates the
891 <h3 id="_connect_device">3.9. Connect Device</h3>
892 <div class="paragraph">
893 <p>Selecting this item brings up a dialog box listing all
894 of the connected TeleDongle devices. When you choose
895 one of these, AltosUI will display telemetry data as
896 received by the selected TeleDongle device.</p>
898 <div class="imageblock">
899 <div class="content">
900 <img src="device-selection.png" alt="device selection" width="300">
902 <div class="title">Figure 11. Device Selection Dialog</div>
906 <h3 id="_disconnect">3.10. Disconnect</h3>
907 <div class="paragraph">
908 <p>Disconnects the currently connected TeleDongle or
913 <h3 id="_scan_channels">3.11. Scan Channels</h3>
914 <div class="imageblock">
915 <div class="content">
916 <img src="telegps-scan.png" alt="telegps scan" width="300">
918 <div class="title">Figure 12. Radio Scanning Dialog</div>
920 <div class="paragraph">
921 <p>Scans the configured set of frequencies looking for
922 telemetry signals. A list of all of the discovered
923 signals is show; selecting one of those and clicking
924 on 'Monitor' will select that frequency in the
925 associated TeleGPS application window.</p>
929 <h3 id="_download_data">3.12. Download Data</h3>
930 <div class="paragraph">
931 <p>TeleGPS records data to its internal flash memory.
932 On-board data is recorded at the same rate as
933 telemetry but is not subject to radio drop-outs. As
934 such, it generally provides a more complete and
935 precise record. The 'Download Data' menu entry allows
936 you to read the flash memory and write it to disk.</p>
938 <div class="paragraph">
939 <p>Select the 'Download Data' menu entry to bring up a
940 list of connected TeleGPS devices. After the device
941 has been selected, a dialog showing the data stored in
942 the device will be shown allowing you to select which
943 entries to download and which to delete. You must
944 erase flights in order for the space they consume to
945 be reused by another track. This prevents accidentally
946 losing data if you neglect to download data before
947 starting TeleGPS again. Note that if there is no more
948 space available in the device, then no data will be
951 <div class="paragraph">
952 <p>The file name for each data log is computed
953 automatically from the recorded date, altimeter serial
954 number and flight number information.</p>
958 <h3 id="_configure_device">3.13. Configure Device</h3>
959 <div class="imageblock">
960 <div class="content">
961 <img src="telegps-configure.png" alt="telegps configure" width="350">
963 <div class="title">Figure 13. TeleGPS Configuration Dialog</div>
965 <div class="paragraph">
966 <p>Select this button and then select any connected TeleGPS
967 device from the list provided.</p>
969 <div class="paragraph">
970 <p>The first few lines of the dialog provide information
971 about the connected device, including the product
972 name, software version and hardware serial
973 number. Below that are the individual configuration
976 <div class="paragraph">
977 <p>At the bottom of the dialog, there are four buttons:</p>
981 <dt class="hdlist1">Save</dt>
983 <p>This writes any changes to the configuration parameter
984 block in flash memory. If you don’t press this button,
985 any changes you make will be lost.</p>
987 <dt class="hdlist1">Reset</dt>
989 <p>This resets the dialog to the most recently saved
990 values, erasing any changes you have made.</p>
992 <dt class="hdlist1">Reboot</dt>
994 <p>This reboots the device. Use this to switch from idle
995 to pad mode by rebooting once the rocket is oriented
996 for flight, or to confirm changes you think you saved
997 are really saved.</p>
999 <dt class="hdlist1">Close</dt>
1001 <p>This closes the dialog. Any unsaved changes will be
1006 <div class="paragraph">
1007 <p>The rest of the dialog contains the parameters to be configured.</p>
1010 <h4 id="_frequency">3.13.1. Frequency</h4>
1011 <div class="paragraph">
1012 <p>This configures which of the frequencies to use for
1013 both telemetry and packet command mode. Note that if
1014 you set this value via packet command mode, the
1015 TeleDongle frequency will also be automatically
1016 reconfigured to match so that communication will
1017 continue afterwards.</p>
1021 <h4 id="_rf_calibration">3.13.2. RF Calibration</h4>
1022 <div class="paragraph">
1023 <p>The radios in every Altus Metrum device are calibrated
1024 at the factory to ensure that they transmit and
1025 receive on the specified frequency. If you need to
1026 you can adjust the calibration by changing this value.
1027 Do not do this without understanding what the value
1028 means, read the appendix on calibration and/or the
1029 source code for more information. To change a
1030 TeleDongle’s calibration, you must reprogram the unit
1035 <h4 id="_telemetryrdfaprs_enable">3.13.3. Telemetry/RDF/APRS Enable</h4>
1036 <div class="paragraph">
1037 <p>Enables the radio for transmission during
1038 flight. When disabled, the radio will not
1039 transmit anything during flight at all.</p>
1043 <h4 id="_limit_transmit_to_10mw">3.13.4. Limit transmit to 10mW</h4>
1044 <div class="paragraph">
1045 <p>Reduces transmit power to no more than 10mW. This is
1046 useful when operating under some UK radio regulations.</p>
1050 <h4 id="_telemetry_baud_rate">3.13.5. Telemetry baud rate</h4>
1051 <div class="paragraph">
1052 <p>This sets the modulation bit rate for data
1053 transmission for both telemetry and packet
1054 link mode. Lower bit rates will increase range
1055 while reducing the amount of data that can be
1056 sent and increasing battery consumption. All
1057 telemetry is done using a rate 1/2 constraint
1058 4 convolution code, so the actual data
1059 transmission rate is 1/2 of the modulation bit
1060 rate specified here.</p>
1064 <h4 id="_aprs_interval">3.13.6. APRS Interval</h4>
1065 <div class="paragraph">
1066 <p>How often to transmit GPS information via APRS
1067 (in seconds). When set to zero, APRS
1068 transmission is disabled.
1069 Note that a single APRS packet
1070 takes nearly a full second to transmit, so
1071 enabling this option will prevent sending any
1072 other telemetry during that time.</p>
1076 <h4 id="_aprs_ssid">3.13.7. APRS SSID</h4>
1077 <div class="paragraph">
1078 <p>Which SSID to report in APRS packets. By
1079 default, this is set to the last digit of the
1080 serial number, but can be configured to any
1081 value from 0 to 9.</p>
1085 <h4 id="_aprs_format">3.13.8. APRS Format</h4>
1086 <div class="paragraph">
1087 <p>Whether to send APRS data in Compressed or
1088 Uncompressed format. Compressed format is
1089 smaller and more precise. Uncompressed
1090 format is older, but may work better with your
1091 device. The Kenwood TH-D72 only displays
1092 altitude information with Uncompressed
1093 format, while the Yaesu FT1D only displays
1094 altitude with Compressed format. Test before
1095 you fly to see which to use.</p>
1099 <h4 id="_aprs_offset">3.13.9. APRS Offset</h4>
1100 <div class="paragraph">
1101 <p>The delay from the top of the minute before sending
1102 the first APRS packet of the minute. Coordinating
1103 values for this parameter between multiple devices can
1104 allow a single receiver to reliably receive APRS
1105 packets from multiple devices. Note that this offset only
1106 takes effect while the GPS signal is locked so that the
1107 transmitting device knows the current time.</p>
1111 <h4 id="_callsign_2">3.13.10. Callsign</h4>
1112 <div class="paragraph">
1113 <p>This sets the call sign included in each
1114 telemetry packet. Set this as needed to
1115 conform to your local radio regulations.</p>
1119 <h4 id="_logging_trigger_motion">3.13.11. Logging Trigger Motion</h4>
1120 <div class="paragraph">
1121 <p>This sets the amount of motion that TeleGPS
1122 needs to see before logging the new
1123 position. Motions smaller than this are
1124 skipped, which saves storage space.</p>
1128 <h4 id="_position_reporting_interval">3.13.12. Position Reporting Interval</h4>
1129 <div class="paragraph">
1130 <p>The interval between TeleGPS position reports,
1131 both over the air and in the log. Increase
1132 this to reduce the frequency of radio
1133 transmissions and the length of time available
1139 <h3 id="_flash_device">3.14. Flash Device</h3>
1140 <div class="paragraph">
1141 <p>This reprograms TeleGPS devices with new
1142 firmware. Please read the directions for flashing
1143 devices in <a href="#_updating_device_firmware">Updating Device Firmware</a>.</p>
1149 <h2 id="_telegps_system_operation">Appendix A: TeleGPS System Operation</h2>
1150 <div class="sectionbody">
1152 <h3 id="_gfsk_telemetry">A.1. GFSK Telemetry</h3>
1153 <div class="paragraph">
1154 <p>TeleGPS’s native telemetry system doesn’t use a
1155 'normal packet radio' mode like APRS because it’s not
1156 very efficient. The GFSK modulation we use is FSK
1157 with the base-band pulses passed through a Gaussian
1158 filter before they go into the modulator to limit the
1159 transmitted bandwidth. When combined with forward
1160 error correction and interleaving, this allows us to
1161 have a very robust 19.2 kilobit data link with only
1162 10-40 milliwatts of transmit power, a whip antenna in
1163 the rocket, and a hand-held Yagi on the ground. We’ve
1164 had flights to above 21k feet AGL with great
1165 reception, and calculations suggest we should be good
1166 to well over 40k feet AGL with a 5-element yagi on the
1167 ground with our 10mW units and over 100k feet AGL with
1168 the 40mW devices.</p>
1172 <h3 id="_aprs">A.2. APRS</h3>
1173 <div class="paragraph">
1174 <p>TeleGPS can send APRS if desired, and the
1175 interval between APRS packets can be configured. As
1176 each APRS packet takes a full second to transmit, we
1177 recommend an interval of at least 5 seconds to avoid
1178 consuming too much battery power or radio channel
1179 bandwidth. You can configure the time within each
1180 minute that APRS transmits by changing the APRS offset
1181 value. When the GPS signal is locked and knows the
1182 current time, the APRS offset selects the time with
1183 each minute for the first APRS transmission;
1184 subsequent transmissions occur each APRS interval
1185 seconds thereafter. You can configure the APRS
1186 interval and APRS offset using TeleGPS; that
1187 process is described in <a href="#_configure_device">Configure Device</a>.</p>
1189 <div class="paragraph">
1190 <p>AltOS supports both compressed and uncompressed APRS
1191 position report data formats. The compressed format
1192 provides for higher position precision and shorter
1193 packets than the uncompressed APRS format. We’ve found
1194 some older APRS receivers that do not handle the
1195 compressed format. The Kenwood TH-72A requires the use
1196 of uncompressed format to display altitude information
1197 correctly. The Yaesu FT1D requires the use of
1198 compressed format to display altitude information.</p>
1200 <div class="paragraph">
1201 <p>APRS packets include an SSID (Secondary Station Identifier)
1202 field that allows one operator to have multiple
1203 transmitters. AltOS allows you to set this to a single digit
1204 from 0 to 9, allowing you to fly multiple transmitters at the
1205 same time while keeping the identify of each one separate in
1206 the receiver. By default, the SSID is set to the last digit of
1207 the device serial number.</p>
1209 <div class="paragraph">
1210 <p>The APRS packet format includes a comment field that
1211 can have arbitrary text in it. AltOS uses this to send
1212 status information as shown in the following table.</p>
1214 <table class="tableblock frame-all grid-all stretch">
1215 <caption class="title">Table 1. Altus Metrum APRS Comments</caption>
1217 <col style="width: 20%;">
1218 <col style="width: 20%;">
1219 <col style="width: 60%;">
1223 <th class="tableblock halign-left valign-top">Field</th>
1224 <th class="tableblock halign-left valign-top">Example</th>
1225 <th class="tableblock halign-left valign-top">Description</th>
1230 <td class="tableblock halign-left valign-top"><p class="tableblock">1</p></td>
1231 <td class="tableblock halign-left valign-top"><p class="tableblock">L</p></td>
1232 <td class="tableblock halign-left valign-top"><p class="tableblock">GPS Status U for unlocked, L for locked</p></td>
1235 <td class="tableblock halign-left valign-top"><p class="tableblock">2</p></td>
1236 <td class="tableblock halign-left valign-top"><p class="tableblock">6</p></td>
1237 <td class="tableblock halign-left valign-top"><p class="tableblock">Number of Satellites in View</p></td>
1240 <td class="tableblock halign-left valign-top"><p class="tableblock">3</p></td>
1241 <td class="tableblock halign-left valign-top"><p class="tableblock">B4.0</p></td>
1242 <td class="tableblock halign-left valign-top"><p class="tableblock">Altimeter Battery Voltage</p></td>
1245 <td class="tableblock halign-left valign-top"><p class="tableblock">4</p></td>
1246 <td class="tableblock halign-left valign-top"><p class="tableblock">1286</p></td>
1247 <td class="tableblock halign-left valign-top"><p class="tableblock">Device Serial Number</p></td>
1251 <div class="paragraph">
1252 <p>Here’s an example of an APRS comment showing GPS lock with 6
1253 satellites in view and a primary battery at 4.0V from device 1876.</p>
1255 <div class="literalblock">
1256 <div class="content">
1257 <pre>L6 B4.0 1876</pre>
1260 <div class="paragraph">
1261 <p>Make sure your primary battery is above 3.8V
1262 and GPS is locked with at least 5 or 6 satellites in
1263 view before flying. If GPS is switching between L and
1264 U regularly, then it doesn’t have a good lock and you
1265 should wait until it becomes stable.</p>
1267 <div class="paragraph">
1268 <p>If the GPS receiver loses lock, the APRS data
1269 transmitted will contain the last position for which
1270 GPS lock was available. You can tell that this has
1271 happened by noticing that the GPS status character
1272 switches from 'L' to 'U'. Before GPS has locked, APRS
1273 will transmit zero for latitude, longitude and
1278 <h3 id="_configurable_parameters">A.3. Configurable Parameters</h3>
1279 <div class="paragraph">
1280 <p>Configuring TeleGPS is very simple; the few configurable
1281 parameters can all be set using the TeleGPS application over
1282 USB. Check out <a href="#_configure_device">Configure Device</a>.</p>
1288 <h2 id="_handling_precautions">Appendix B: Handling Precautions</h2>
1289 <div class="sectionbody">
1290 <div class="paragraph">
1291 <p>All Altus Metrum products are sophisticated electronic devices.
1292 When handled gently and properly installed in an air-frame, they
1293 will deliver impressive results. However, as with all electronic
1294 devices, there are some precautions you must take.</p>
1296 <div class="admonitionblock warning">
1300 <div class="title">Warning</div>
1302 <td class="content">
1303 The Lithium Polymer rechargeable batteries have an
1304 extraordinary power density. This is great because we can fly with
1305 much less battery mass than if we used alkaline batteries or previous
1306 generation rechargeable batteries…​ but if they are punctured
1307 or their leads are allowed to short, they can and will release their
1308 energy very rapidly!
1309 Thus we recommend that you take some care when handling our batteries
1310 and consider giving them some extra protection in your air-frame. We
1311 often wrap them in suitable scraps of closed-cell packing foam before
1312 strapping them down, for example.
1317 <div class="paragraph">
1318 <p>The barometric sensors used on all of our flight computers are
1319 sensitive to sunlight. In normal mounting situations, the baro sensor
1320 and all of the other surface mount components
1321 are “down” towards whatever the underlying mounting surface is, so
1322 this is not normally a problem. Please consider this when designing an
1323 installation in an air-frame with a see-through plastic payload bay. It
1324 is particularly important to
1325 consider this with TeleMini v1.0, both because the baro sensor is on the
1326 “top” of the board, and because many model rockets with payload bays
1327 use clear plastic for the payload bay! Replacing these with an opaque
1328 cardboard tube, painting them, or wrapping them with a layer of masking
1329 tape are all reasonable approaches to keep the sensor out of direct
1332 <div class="paragraph">
1333 <p>The barometric sensor sampling port must be able to “breathe”,
1334 both by not being covered by foam or tape or other materials that might
1335 directly block the hole on the top of the sensor, and also by having a
1336 suitable static vent to outside air.</p>
1338 <div class="paragraph">
1339 <p>As with all other rocketry electronics, Altus Metrum altimeters must
1340 be protected from exposure to corrosive motor exhaust and ejection
1346 <h2 id="_technical_information">Appendix C: Technical Information</h2>
1347 <div class="sectionbody">
1349 <h3 id="_gps_receiver">C.1. GPS Receiver</h3>
1350 <div class="paragraph">
1351 <p>TeleGPS uses the u-Blox Max-7Q GPS receiver.</p>
1355 <h3 id="_70cm_transmitter">C.2. 70cm Transmitter</h3>
1356 <div class="paragraph">
1357 <p>TeleGPS uses a TI CC115L transmitter. This radio
1358 produces 10mW of RF output.</p>
1362 <h3 id="_micro_controller">C.3. Micro-controller</h3>
1363 <div class="paragraph">
1364 <p>TeleGPS uses an NXP LPC11U14 micro-controller. This
1365 tiny CPU contains 32kB of flash for the application
1366 and 4kB of RAM for temporary data storage.</p>
1370 <h3 id="_lithium_polymer_battery">C.4. Lithium Polymer Battery</h3>
1371 <div class="paragraph">
1372 <p>Shipping restrictions may prevent us from including a
1373 battery battery with TeleGPS.</p>
1377 <h3 id="_mechanical_considerations">C.5. Mechanical Considerations</h3>
1378 <div class="paragraph">
1379 <p>TeleGPS is designed to be rugged enough for typical
1380 rocketry applications. The 4 mounting holes on the
1381 board are sized for use with 4-40 or M3 screws.</p>
1385 <h3 id="_on_board_data_storage">C.6. On-board data storage</h3>
1386 <div class="paragraph">
1387 <p>TeleGPS has 2MB of non-volatile storage, separate from
1388 the code storage memory. The TeleGPS firmware uses
1389 this to log information during flight.</p>
1395 <h2 id="_updating_device_firmware">Appendix D: Updating Device Firmware</h2>
1396 <div class="sectionbody">
1397 <div class="paragraph">
1398 <p>TeleGPS is programmed directly over its USB connectors.</p>
1400 <div class="paragraph">
1401 <p>You may wish to begin by ensuring you have current firmware images.
1402 These are distributed as part of the TeleGPS software bundle that
1403 also includes the TeleGPS ground station program. Newer ground
1404 station versions typically work fine with older firmware versions,
1405 so you don’t need to update your devices just to try out new
1406 software features. You can always download the most recent
1407 version from <a href="http://www.altusmetrum.org/AltOS/" class="bare">http://www.altusmetrum.org/AltOS/</a></p>
1410 <h3 id="_updating_telegps_firmware">D.1. Updating TeleGPS Firmware</h3>
1411 <div class="olist arabic">
1414 <p>Attach a battery and power switch to the target
1415 device. Power up the device.</p>
1418 <p>Using a Micro USB cable, connect the target device to
1419 your computer’s USB socket.</p>
1422 <p>Run TeleGPS, and select 'Flash Device' from the
1426 <p>Select the target device in the Device Selection
1430 <p>Select the image you want to flash to the device,
1431 which should have a name in the form
1432 <product>-v<product-version>-<software-version>.ihx,
1433 such as TeleGPS-v1.0-1.4.0.ihx.</p>
1436 <p>Make sure the configuration parameters are reasonable
1437 looking. If the serial number and/or RF configuration
1438 values aren’t right, you’ll need to change them.</p>
1441 <p>Hit the 'OK' button and the software should proceed
1442 to flash the device with new firmware, showing a
1446 <p>Verify that the device is working by using the
1447 'Configure Device item to check over the
1456 <h2 id="_release_notes">Appendix E: Release Notes</h2>
1457 <div class="sectionbody">
1459 <h3 id="_release_notes_for_version_1_9_18">E.1. Release Notes for Version 1.9.18</h3>
1460 <div class="paragraph">
1461 <p>Version 1.9.18</p>
1464 <h4 id="_altos">E.1.1. AltOS</h4>
1468 <p>Add support for EasyTimer V2. The new version of this
1469 product has on-board storage to log data during flight.</p>
1475 <h4 id="_altosui_telegps_application">E.1.2. AltosUI & TeleGPS application</h4>
1479 <p>Add support for EasyTimer V2. This includes support for
1480 analyizing flight data from the on-board logs.</p>
1483 <p>Allow on-board beepers to be disabled by setting the
1488 <div style="page-break-after: always;"></div>
1492 <h3 id="_release_notes_for_version_1_9_17">E.2. Release Notes for Version 1.9.17</h3>
1493 <div class="paragraph">
1494 <p>Version 1.9.17</p>
1497 <h4 id="_altos_2">E.2.1. AltOS</h4>
1501 <p>Fix TeleMini v3 Monitor Idle support</p>
1504 <p>Support TeleMetrum v4.0 with uBlox-10 GPS module</p>
1507 <p>Improve igniter reporting via the beeper.</p>
1513 <h4 id="_altosui_telegps_application_2">E.2.2. AltosUI & TeleGPS application</h4>
1517 <p>Add support for EasyMini v3 Monitor Idle</p>
1521 <div style="page-break-after: always;"></div>
1525 <h3 id="_release_notes_for_version_1_9_16">E.3. Release Notes for Version 1.9.16</h3>
1526 <div class="paragraph">
1527 <p>Version 1.9.16</p>
1530 <h4 id="_altos_3">E.3.1. AltOS</h4>
1534 <p>Add TeleGPS v3.0 support</p>
1540 <h4 id="_altosui_telegps_application_3">E.3.2. AltosUI & TeleGPS application</h4>
1544 <p>Add TeleGPS v3.0 support</p>
1548 <div style="page-break-after: always;"></div>
1552 <h3 id="_release_notes_for_version_1_9_15">E.4. Release Notes for Version 1.9.15</h3>
1553 <div class="paragraph">
1554 <p>Version 1.9.15</p>
1557 <h4 id="_altos_4">E.4.1. AltOS</h4>
1561 <p>Add TeleMega v6.0 support</p>
1564 <p>Add TeleMetrum v4.0 support</p>
1567 <p>Fix sign of IMU values for TeleMega v5 boards in the
1568 'across' axis. This affects IMU acceleration and gyro reports
1569 for that axis, but has no effect on in-flight operation of
1570 the tilt computation.</p>
1574 <div style="page-break-after: always;"></div>
1578 <h3 id="_release_notes_for_version_1_9_14">E.5. Release Notes for Version 1.9.14</h3>
1579 <div class="paragraph">
1580 <p>Version 1.9.14</p>
1583 <h4 id="_altos_5">E.5.1. AltOS</h4>
1587 <p>Fix 1.9.13 regression in TeleLCO startup sequence that
1588 detects available TeleFire units.</p>
1592 <div style="page-break-after: always;"></div>
1596 <h3 id="_release_notes_for_version_1_9_13">E.6. Release Notes for Version 1.9.13</h3>
1597 <div class="paragraph">
1598 <p>Version 1.9.13</p>
1601 <h4 id="_altos_6">E.6.1. AltOS</h4>
1605 <p>Add option to beep max height in feet after landing</p>
1608 <p>Fix APRS reports to be sent at the correct time and spacing.</p>
1611 <p>Fix possible barometric sensor communication failure when
1612 the CPU is busy talking to the radio at the same time. This
1613 would cause loss of telemetry and failure to track the state
1614 of the rocket during flight. This was aggrevated by the APRS
1615 reports getting sent more often than they should.</p>
1618 <p>Change EasyMotor v3 code to base logging on motor pressure
1619 rather than the accelerometer. This allows use of EasyMotor
1620 v3 in a static test stand.</p>
1626 <h4 id="_altosui">E.6.2. AltosUI</h4>
1630 <p>Add support for configuring the units used to report height
1631 after landing on the beeper.</p>
1635 <div style="page-break-after: always;"></div>
1639 <h3 id="_release_notes_for_version_1_9_12">E.7. Release Notes for Version 1.9.12</h3>
1640 <div class="paragraph">
1641 <p>Version 1.9.12</p>
1644 <h4 id="_altos_7">E.7.1. AltOS</h4>
1648 <p>Add EasyMini v3.0 and EasyMotor v3.0 support</p>
1651 <p>Fix TeleMetrum v2.0 configuration. Saving config would
1652 crash the board.</p>
1658 <h4 id="_altosui_2">E.7.2. AltosUI</h4>
1662 <p>Add EasyMotor log parsing and graphing.</p>
1666 <div style="page-break-after: always;"></div>
1670 <h3 id="_release_notes_for_version_1_9_11">E.8. Release Notes for Version 1.9.11</h3>
1671 <div class="paragraph">
1672 <p>Version 1.9.11</p>
1675 <h4 id="_altos_8">E.8.1. AltOS</h4>
1679 <p>Make Apogee Delay work again.</p>
1682 <p>Allow TX power to be limited to 10mW for compliance with
1683 some uses under UK regulations.</p>
1686 <p>Fix numerous minor issues with 16- vs 32- bit time values.</p>
1692 <h4 id="_altosui_3">E.8.2. AltosUI</h4>
1696 <p>Support M1-based Macs, follow AdoptOpenJDK to Adoptium</p>
1702 <h4 id="_altosdroid">E.8.3. AltosDroid</h4>
1706 <p>Handle Bluetooth permissions reliably.</p>
1709 <p>Fix some screen rotation bugs.</p>
1713 <div style="page-break-after: always;"></div>
1717 <h3 id="_release_notes_for_version_1_9_10">E.9. Release Notes for Version 1.9.10</h3>
1718 <div class="paragraph">
1719 <p>Version 1.9.10</p>
1721 <div class="paragraph">
1722 <p>This release contains a couple of bug fixes for ground station software.</p>
1725 <h4 id="_altosui_4">E.9.1. AltosUI</h4>
1729 <p>Rework the windows DLL build to make AltosUI run on more
1730 instances of Windows 10.</p>
1736 <h4 id="_altosdroid_2">E.9.2. AltosDroid</h4>
1740 <p>Adapt to Android security changes which prevent AltosDroid
1741 from storing flights in
1742 /storage/emulated/0/AltusMetrum. Now, flights are stored in
1743 /storage/emulated/0/media/org.altusmetrum.AltosDroid/AltusMetrum
1744 instead. Also, AltosDroid will display an error message if
1745 flight data cannot be logged.</p>
1749 <div style="page-break-after: always;"></div>
1753 <h3 id="_release_notes_for_version_1_9_9">E.10. Release Notes for Version 1.9.9</h3>
1754 <div class="paragraph">
1755 <p>Version 1.9.9</p>
1757 <div class="paragraph">
1758 <p>This release contains a critical bug fix for a problem
1759 introduced in version 1.9.8 for TeleMega and EasyMega
1760 boards. This problem occurs when using the stored
1761 configuration from 1.9.7 or earlier.</p>
1763 <div class="paragraph">
1764 <p>If you are running 1.9.8 or are upgrading from 1.9.8 on any
1765 version of TeleMega or EasyMega, you must reconfigure all pyro
1766 channels, recalibrate accelerometers, reset the APRS interval,
1767 adjust the beep tone and reset the pyro time.</p>
1770 <h4 id="_altos_9">E.10.1. AltOS</h4>
1774 <p>Fix EasyMega and TeleMega upgrade process from 1.9.7 or
1775 earlier. 1.9.8 introduced larger delay values, which
1776 required modifying the configuration in-place, and the 1.9.8
1777 version had a flaw which broke the pyro channel config and
1778 all of the config values beyond that in memory, including
1779 APRS interval, IMU accel calibation, beep tone and pyro
1783 <p>Fix TeleMega v5.0 mag sensor driver. This driver was quite
1784 broken due to developing it in the presence of the magnetic
1785 beeper on the board. Because of that beeper, the values this
1786 sensor records are not accurate. Fortunately, they are not
1787 used for controlling the flight.</p>
1793 <h4 id="_altosui_5">E.10.2. AltosUI</h4>
1797 <p>Parse TeleMega v5.0 log files. A missing check in the code
1798 meant that the TeleMega v5.0 log files would cause an error
1799 when attempting to load them. Logs saved with AltosUI
1800 1.9.8 were not affected, only the presentation of the data
1805 <div style="page-break-after: always;"></div>
1809 <h3 id="_release_notes_for_version_1_9_8">E.11. Release Notes for Version 1.9.8</h3>
1810 <div class="paragraph">
1811 <p>Version 1.9.8</p>
1814 <h4 id="_altos_10">E.11.1. AltOS</h4>
1818 <p>Add support for TeleMega v5.0</p>
1821 <p>Extend extra pyro channel times to support delay > 327 seconds</p>
1827 <h4 id="_altosui_6">E.11.2. AltosUI</h4>
1831 <p>Support ARM devices in Linux binary release</p>
1834 <p>Add support for TeleMega v5.0</p>
1840 <h4 id="_altosdroid_3">E.11.3. AltosDroid</h4>
1844 <p>Show tilt angle in pad and flight tabs</p>
1847 <p>Show altitude as well as height (useful for TeleGPS)</p>
1850 <p>Support devices without GPS receivers</p>
1856 <h4 id="_micropeak_gui">E.11.4. MicroPeak GUI</h4>
1860 <p>Show error dialog if device open fails</p>
1864 <div style="page-break-after: always;"></div>
1868 <h3 id="_release_notes_for_version_1_9_7">E.12. Release Notes for Version 1.9.7</h3>
1869 <div class="paragraph">
1870 <p>Version 1.9.7</p>
1873 <h4 id="_altos_11">E.12.1. AltOS</h4>
1877 <p>Fix TeleGPS logging so that new data are appended to an existing log correctly</p>
1883 <h4 id="_altosui_7">E.12.2. AltosUI</h4>
1887 <p>Support Mac OS X 11 (Big Sur)</p>
1890 <p>Support Monitor Idle on Easy Timer</p>
1893 <p>Fix TeleMega v4.0 and TeleMetrum v3.0 configuration in Antenna Down mode</p>
1896 <p>Show launch sites in Load Maps view</p>
1899 <p>Add IMU header names to CSV files</p>
1902 <p>Clean up TeleGPS log corruption due to firmware bugs during firmware update</p>
1908 <h4 id="_altosdroid_4">E.12.3. AltosDroid</h4>
1912 <p>Support older devices back to Android version 5.1</p>
1915 <p>Fix a number of issues that could result in app crashes</p>
1919 <div style="page-break-after: always;"></div>
1923 <h3 id="_release_notes_for_version_1_9_6">E.13. Release Notes for Version 1.9.6</h3>
1924 <div class="paragraph">
1925 <p>Version 1.9.6</p>
1928 <h4 id="_altos_12">E.13.1. AltOS</h4>
1932 <p>Fix EasyTimer bug where it might mis-detect boost (either
1933 detect it early or not at all) due to small errors in
1934 accelerometer calibration leading to large accumulated error
1938 <p>Adjust self-test of new 9-axis IMU (BMX-160) so that it
1939 doesn’t think the part has a failure when tested sitting
1944 <div style="page-break-after: always;"></div>
1948 <h3 id="_release_notes_for_version_1_9_5">E.14. Release Notes for Version 1.9.5</h3>
1949 <div class="paragraph">
1950 <p>Version 1.9.5</p>
1953 <h4 id="_altos_13">E.14.1. AltOS</h4>
1957 <p>Add Booster mode for all dual-deploy altimeters. Select
1958 "Separation & Apogee" mode in AltosUI to fire the 'main'
1959 channel at first motor burnout and the 'apogee' channel at
1963 <p>Improve reliability of stm32l firmware under heavy
1964 load. This was found using Monitor Idle on TeleMega with all
1965 flash slots full of data which would occasionally lock up.</p>
1968 <p>Fix orientation label in AltosUI for devices with
1969 radios. This makes the orientation say 'Antenna up' and
1970 'Antenna Down' for TeleMetrum and TeleMega again.</p>
1973 <p>Fix log data for pyro channels which were inhibited (often
1974 because of a tilt limit). They used to report 'fired' as
1975 soon as they were inhibited, which was misleading. Now they
1976 never report as having been fired.</p>
1979 <p>Allow Igniter Test to fire each igniter more than once.</p>
1985 <h4 id="_altosui_8">E.14.2. AltosUI</h4>
1989 <p>Improve performance of Monitor Idle mode by sending less data for each
1993 <p>Improve Mac OS X install scripts so that they work on
1994 Catalina. This involves sending the user to get Java from
1995 the AdoptOpenJDK project which provides a version that works
1996 with Java applications.</p>
1999 <p>Make larger dialogs scrollable for use on smaller screens.</p>
2002 <p>Fix troubles re-flashing EasyMega boards running older
2006 <p>Add TeleMetrum v3.0 firmware to the Windows
2007 AltosUI packages.</p>
2011 <div style="page-break-after: always;"></div>
2015 <h3 id="_release_notes_for_version_1_9_4">E.15. Release Notes for Version 1.9.4</h3>
2016 <div class="paragraph">
2017 <p>Version 1.9.4</p>
2020 <h4 id="_altos_14">E.15.1. AltOS</h4>
2024 <p>Fixed firmware for TeleDongle v3.0 and TeleBT v4.0. Version 1.9.3 bricked those
2025 devices requiring them to be opened up to get them working again.</p>
2028 <p>Fixed firmware for EasyMini v1.0. Changes in the storage
2029 code caused it to use significantly more RAM which made the
2030 interrupt stack smash into other data structures and cause
2031 the device to panic at startup time.</p>
2037 <h4 id="_altosui_9">E.15.2. AltosUI</h4>
2041 <p>Add TeleMetrum v3.0 firmware to the Linux and Mac OSX
2042 AltosUI packages.</p>
2046 <div style="page-break-after: always;"></div>
2050 <h3 id="_release_notes_for_version_1_9_3">E.16. Release Notes for Version 1.9.3</h3>
2051 <div class="paragraph">
2052 <p>Version 1.9.3</p>
2055 <h4 id="_altos_15">E.16.1. AltOS</h4>
2059 <p>Add APRS offset. Allows multiple APRS transmitters to coordinate when
2060 transmission occurs to allow them to share a frequency.</p>
2063 <p>Fix max log size. Flight computer storage is erased in 64kB chunks. Adjust max
2064 log size to be a multiple of this size.</p>
2067 <p>Check flight erasing more carefully. Handle interrupting erasing in the
2071 <p>Add EasyTimer support.</p>
2077 <h4 id="_altosui_telegps_micropeak">E.16.2. AltosUI, TeleGPS, MicroPeak</h4>
2081 <p>Add configuration support for APRS offset.</p>
2084 <p>Adjust flight log sizes to be a multiple of the flight
2085 computer erase block size.</p>
2088 <p>Report barometric pad altitude in Pad tab for TeleMini.</p>
2092 <div style="page-break-after: always;"></div>
2096 <h3 id="_release_notes_for_version_1_9_1">E.17. Release Notes for Version 1.9.1</h3>
2097 <div class="paragraph">
2098 <p>Version 1.9.1</p>
2101 <h4 id="_altos_16">E.17.1. AltOS</h4>
2105 <p>Add support for TeleMetrum v3.0</p>
2108 <p>Fix accel cal value when changing EasyMega v2.0 pad orientation</p>
2111 <p>Correct EasyMega v2.0 magnetometer data axes</p>
2114 <p>Fix EasyMega v2.0 idle monitor display of IMU data</p>
2117 <p>Report all sensor failures at power-up time.</p>
2123 <h4 id="_altosui_telegps_micropeak_2">E.17.2. AltosUI, TeleGPS, MicroPeak</h4>
2127 <p>Display error message when attempting to graph unknown format file.</p>
2130 <p>Make it possible to disable APRS once enabled.</p>
2133 <p>Display some data for point near cursor in map tab.</p>
2136 <p>Support upgrading devices from pre-1.8 firmware</p>
2139 <p>Wait for Windows to prepare new devices during firmware
2140 upgrade. This should avoid the “COMxx: open failed” message.</p>
2144 <div style="page-break-after: always;"></div>
2148 <h3 id="_release_notes_for_version_1_9">E.18. Release Notes for Version 1.9</h3>
2149 <div class="paragraph">
2153 <h4 id="_altos_17">E.18.1. AltOS</h4>
2157 <p>Add support for EasyMega v2.0</p>
2160 <p>Replace C library for ARM devices</p>
2163 <p>Remove support for 8051-based devices and SDCC compiler</p>
2169 <h4 id="_altosui_telegps_micropeak_3">E.18.2. AltosUI, TeleGPS, MicroPeak</h4>
2173 <p>Select ROM images based on product name when reflashing</p>
2176 <p>Fix TeleGPS v2 battery voltage display</p>
2180 <div style="page-break-after: always;"></div>
2184 <h3 id="_release_notes_for_version_1_8_7">E.19. Release Notes for Version 1.8.7</h3>
2185 <div class="paragraph">
2186 <p>Version 1.8.7</p>
2189 <h4 id="_altos_18">E.19.1. AltOS</h4>
2193 <p>Include TeleMega v3.0 firmware</p>
2199 <h4 id="_altosui_telegps_micropeak_4">E.19.2. AltosUI, TeleGPS, MicroPeak</h4>
2203 <p>Poll for new devices while Device dialog is displayed</p>
2206 <p>Wait for device to re-appear when flashing new firmware</p>
2209 <p>Fetch correct TeleBT v4.0 RF calibration values from web
2210 site when reflashing.</p>
2213 <p>Change gyro headings in .csv files from x/y/z to
2217 <p>Add documentation about Packet Link mode</p>
2220 <p>Add documentation about forcing TeleMini RF parameters to
2224 <p>Create a proxy server for Google Maps to re-enable map
2228 <p>Fix Java version info in all distributed jar files so that
2229 applications will run with standard Mac OS X Java.</p>
2232 <p>Replace JavaApplicationStub for Mac OS X so that
2233 applications will run with Oracle Java.</p>
2237 <div style="page-break-after: always;"></div>
2241 <h3 id="_release_notes_for_version_1_8_6">E.20. Release Notes for Version 1.8.6</h3>
2242 <div class="paragraph">
2243 <p>Version 1.8.6</p>
2246 <h4 id="_altos_19">E.20.1. AltOS</h4>
2250 <p>Use maximum of 64 previous tilt values in pyro tilt tests</p>
2253 <p>Eliminate 100m height requirement for coast detection</p>
2256 <p>Change After Motor pyro check to be >= instead of ==</p>
2259 <p>Change Time since Boost to be Time since launch.</p>
2265 <h4 id="_altosui_telegps">E.20.2. AltosUI, TeleGPS</h4>
2269 <p>Clarify pyro test phrasing</p>
2272 <p>Remove ascending/descending from pyro config UI</p>
2275 <p>Fix accel calibration in Antenna Down mode</p>
2278 <p>Add mag sensor reporting for TeleMega v3 idle monitoring.</p>
2281 <p>Fix radio parameter saving at 2400 bps telmetry rate.</p>
2287 <h4 id="_micropeak">E.20.3. MicroPeak</h4>
2291 <p>Report altimeter-recorded maximum height value</p>
2295 <div style="page-break-after: always;"></div>
2299 <h3 id="_release_notes_for_version_1_8_5">E.21. Release Notes for Version 1.8.5</h3>
2300 <div class="paragraph">
2301 <p>Version 1.8.5 includes fixes to the ground software support
2302 for TeleBT v4, along with a few other minor updates.</p>
2305 <h4 id="_altos_20">E.21.1. AltOS</h4>
2309 <p>Fix startup beeps that indicate sensor failures.</p>
2315 <h4 id="_altosui_telegps_2">E.21.2. AltosUI, TeleGPS</h4>
2319 <p>When updating device firmware, make sure selected firmware
2320 matches target device.</p>
2323 <p>Correct Bluetooth device matching when looking for TeleBT
2328 <div style="page-break-after: always;"></div>
2332 <h3 id="_release_notes_for_version_1_8_4">E.22. Release Notes for Version 1.8.4</h3>
2333 <div class="paragraph">
2334 <p>Version 1.8.4 includes support for EasyMini version 2.0</p>
2337 <h4 id="_altos_21">E.22.1. AltOS</h4>
2341 <p>Support for EasyMini version 2.0 hardware.</p>
2345 <div style="page-break-after: always;"></div>
2349 <h3 id="_release_notes_for_version_1_8_3">E.23. Release Notes for Version 1.8.3</h3>
2350 <div class="paragraph">
2351 <p>Version 1.8.3 includes support for TeleMega version 3.0 along
2352 with two important flight computer fixes. This version also
2353 changes KML export data to make Tripoli Record reporting
2354 better and some updates to graph presentation and data
2358 <h4 id="_altos_22">E.23.1. AltOS</h4>
2360 <h5 id="_altos_new_features">AltOS New Features</h5>
2364 <p>Support for TeleMega version 3.0 hardware.</p>
2370 <h5 id="_altos_bug_fixes">AltOS Bug Fixes</h5>
2374 <p>Ground testing EasyMega and TeleMega additional pyro
2375 channels could result in a sticky 'fired' status which would
2376 prevent these channels from firing on future flights.</p>
2379 <p>Corrupted flight log records could prevent future flights
2380 from capturing log data.</p>
2383 <p>Fixed saving of pyro configuration that ended with
2391 <h4 id="_altosui_and_telegps_applications">E.23.2. AltosUI and TeleGPS Applications</h4>
2393 <h5 id="_altosui_new_features">AltosUI New Features</h5>
2397 <p>Support for TeleMega version 3.0.</p>
2400 <p>Graph lines have improved appearance to make them easier to
2401 distinguish. Markers may be placed at data points to show
2402 captured recorded data values.</p>
2405 <p>Graphing offers the ability to adjust the smoothing of
2406 computed speed and acceleration data.</p>
2409 <p>The download dialog now offers to graph new flights, checks
2410 for existing files to avoid overwriting data and reports if
2411 there are checksum errors in the downloaded data.</p>
2417 <h5 id="_altosuitelegps_bug_fixes">AltosUI/TeleGPS Bug Fixes</h5>
2421 <p>Restore TeleGPS tracking behavior.</p>
2424 <p>Display flight computer call sign and serial number in
2425 Monitor Idle mode instead of ground station values.</p>
2431 <h5 id="_altosui_and_telegps_changes">AltosUI and TeleGPS Changes</h5>
2435 <p>KML export now reports both barometric and GPS altitude data
2436 to make it more useful for Tripoli record reporting.</p>
2439 <p>CSV export now includes TeleMega/EasyMega pyro voltages and
2444 <div style="page-break-after: always;"></div>
2449 <h3 id="_release_notes_for_version_1_8_2">E.24. Release Notes for Version 1.8.2</h3>
2450 <div class="paragraph">
2451 <p>Version 1.8.2 includes support for TeleGPS version 2.0 along
2452 with accelerometer recalibration support in AltosUI.</p>
2454 <div class="paragraph">
2455 <p>1.8.2 also contains a couple of minor fixes for AltosUI when
2456 analyzing saved data files.</p>
2459 <h4 id="_altos_23">E.24.1. AltOS</h4>
2460 <div class="paragraph">
2461 <p>AltOS New Features</p>
2466 <p>Support for TeleGPS version 2.0 hardware.</p>
2472 <h4 id="_altosui_and_telegps_applications_2">E.24.2. AltosUI and TeleGPS Applications</h4>
2473 <div class="paragraph">
2474 <p>AltosUI and TeleGPS New Features</p>
2479 <p>Support for TeleGPS version 2.0.</p>
2482 <p>Accelerometer re-calibration user interface.</p>
2486 <div class="paragraph">
2487 <p>AltosUI and TeleGPS Bug Fixes</p>
2492 <p>Prevent some crashes when reading older saved flight data
2493 for graphing or KML export.</p>
2497 <div style="page-break-after: always;"></div>
2501 <h3 id="_release_notes_for_version_1_8_1">E.25. Release Notes for Version 1.8.1</h3>
2502 <div class="paragraph">
2503 <p>Version 1.8.1 includes an important bug fix for Apogee Lockout
2504 operation in all flight computers. Anyone using this option
2505 must update firmware.</p>
2507 <div class="paragraph">
2508 <p>This release also contains a change in how flight computers
2509 with accelerometers deal with speeds around and above Mach
2510 1. In previous versions, the flight computer would completely
2511 disregard the barometric sensor above 330m/s (around Mach
2512 1). Now, the data from the barometric sensor is reduced in
2513 effect without ever going away entirely. This prevents early
2514 drogue deployment for flights which spend considerable time
2517 <div class="paragraph">
2518 <p>1.8.1 also contains a couple of minor fixes for AltosUI when
2519 analyzing saved data files.</p>
2522 <h4 id="_altos_24">E.25.1. AltOS</h4>
2523 <div class="paragraph">
2524 <p>AltOS Bug Fixes</p>
2529 <p>Handle time value wrapping in Apogee Lockout
2530 correctly. Without this, apogee lockout would sometimes
2531 prevent any drogue charge from firing.</p>
2534 <p>Change Kalman filter on flight computers with accelerometer
2535 to continue using the barometric sensor even at high speeds
2536 to avoid unintentional drogue deployment during
2543 <h4 id="_altosui_and_telegps_applications_3">E.25.2. AltosUI and TeleGPS Applications</h4>
2544 <div class="paragraph">
2545 <p>AltosUI New Features</p>
2550 <p>Add new 'Huge' font size to make text even bigger on high
2551 resolution monitors.</p>
2555 <div class="paragraph">
2556 <p>AltosUI Bug Fixes</p>
2561 <p>Prevent some crashes when reading older saved flight data
2562 for graphing or KML export.</p>
2565 <p>Load frequency preference at startup. The loading code was
2566 broken, so you’d see only the default frequencies.</p>
2570 <div style="page-break-after: always;"></div>
2574 <h3 id="_release_notes_for_version_1_8">E.26. Release Notes for Version 1.8</h3>
2575 <div class="paragraph">
2576 <p>Version 1.8 includes support for our new TeleBT v4.0 ground
2577 station, updates for data analysis in our ground station
2578 software and bug fixes in in the flight software for all our
2579 boards and ground station interfaces.</p>
2582 <h4 id="_altos_25">E.26.1. AltOS</h4>
2583 <div class="paragraph">
2584 <p>AltOS New Features</p>
2589 <p>Add support for TeleBT v4.0 boards.</p>
2595 <h4 id="_altosui_and_telegps_applications_4">E.26.2. AltosUI and TeleGPS Applications</h4>
2596 <div class="paragraph">
2597 <p>AltosUI New Features</p>
2602 <p>Add support for TeleBT v4.0 hardware</p>
2605 <p>Rewrite graphing and export functions. This code now handles
2606 each data series separately so that graphs are drawn
2607 correctly. Smoothing now uses a filter that looks both
2608 forward and backwards in time to make computed speed and
2609 acceleration data more accurate.</p>
2613 <div class="paragraph">
2614 <p>AltosUI Bug Fixes</p>
2619 <p>Correct axis labeling of magnetic sensor in TeleMega and
2620 EasyMega. The Y and Z axes were flipped.</p>
2624 <div style="page-break-after: always;"></div>
2628 <h3 id="_release_notes_for_version_1_7">E.27. Release Notes for Version 1.7</h3>
2629 <div class="paragraph">
2630 <p>Version 1.7 includes support for our new TeleMini v3.0
2631 flight computer and bug fixes in in the flight software for all our boards
2632 and ground station interfaces.</p>
2635 <h4 id="_altos_26">E.27.1. AltOS</h4>
2636 <div class="paragraph">
2637 <p>AltOS New Features</p>
2642 <p>Add support for TeleMini v3.0 boards.</p>
2646 <div class="paragraph">
2652 <p>Fix interrupt priorities on STM32L processors. Run timer
2653 interrupt at lowest priority so that device interrupts get
2660 <h4 id="_altosui_and_telegps_applications_5">E.27.2. AltosUI and TeleGPS Applications</h4>
2661 <div class="paragraph">
2662 <p>AltosUI New Features</p>
2667 <p>Add support for TeleMini v3.0 hardware</p>
2671 <div style="page-break-after: always;"></div>
2675 <h3 id="_release_notes_for_version_1_6_8">E.28. Release Notes for Version 1.6.8</h3>
2676 <div class="paragraph">
2677 <p>Version 1.6.8 fixes a TeleMega and TeleMetrum v2.0 bug where
2678 the device could stop logging data and transmitting
2679 telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum
2680 v2.0 users should update their flight firmware.</p>
2683 <h4 id="_altos_27">E.28.1. AltOS</h4>
2684 <div class="paragraph">
2690 <p>Fix STM32L DMA driver to work around STM32L SoC DMA priority
2691 issue t lock-up in the logging or radio code, either of
2692 which could stop data logging and telemetry.</p>
2695 <p>Avoid having TeleBT battery status values smash telemetry
2696 packet data by holding a lock during both operations.</p>
2699 <p>Don’t start reporting 'flight 0' when the log fills in
2704 <div class="paragraph">
2705 <p>AltOS changes:</p>
2710 <p>Flash LEDS on all products briefly during power up so that
2711 they can be tested during production.</p>
2717 <h4 id="_altosui_telegps_and_altosdroid_applications">E.28.2. AltosUI, TeleGPS and AltosDroid Applications</h4>
2718 <div class="paragraph">
2719 <p>AltosUI fixes:</p>
2724 <p>Re-enable go/no-go entries after they’ve been disabled due
2725 to lack of data. If telemetry information is delayed when
2726 the Ui starts up, sometimes important fields would get
2727 disabled to never re-appear.</p>
2730 <p>Deal with ground station failure better during Configure
2731 Ground Station operation by cleaning up pending operations.</p>
2735 <div style="page-break-after: always;"></div>
2739 <h3 id="_release_notes_for_version_1_6_5">E.29. Release Notes for Version 1.6.5</h3>
2740 <div class="paragraph">
2741 <p>Version 1.6.5 fixes a TeleMega and TeleMetrum v2.0 bug where
2742 the device would often stop logging data and transmitting
2743 telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum
2744 v2.0 users should update their flight firmware.</p>
2747 <h4 id="_altos_28">E.29.1. AltOS</h4>
2748 <div class="paragraph">
2754 <p>Fix STM32L SPI driver to prevent lock-up in the logging or
2755 radio code, either of which could stop data logging and
2756 telemetry. Found and characterized by Chuck Haskin, who also
2757 tested the new firmware before release.</p>
2763 <h4 id="_altosui_telegps_and_altosdroid_applications_2">E.29.2. AltosUI, TeleGPS and AltosDroid Applications</h4>
2764 <div class="paragraph">
2765 <p>AltosUI fixes:</p>
2770 <p>Deliver firmward for TeleMega v2.0 and TeleBT v3.0 with
2771 Windows package.</p>
2775 <div style="page-break-after: always;"></div>
2779 <h3 id="_release_notes_for_version_1_6_4">E.30. Release Notes for Version 1.6.4</h3>
2780 <div class="paragraph">
2781 <p>Version 1.6.4 fixes a bluetooth communication problem with
2782 TeleBT v1.0 devices, along with some altosui and altosdroid
2783 minor nits. It also now ships firmware for some newer devices.</p>
2786 <h4 id="_altos_29">E.30.1. AltOS</h4>
2787 <div class="paragraph">
2793 <p>Fix hardware flow control on TeleBT v1.0. Hardware RTS/CTS
2794 doesn’t seem to work, switch from using the hardware to
2795 driving these pins with software.</p>
2798 <p>Fix ARM USB drivers to deal with OS restarts. Needed to
2799 reset all USB-related state when the USB bus is reset. These
2800 fixes affect all STM32L, STM32F0 and LPC11U14 based devices.</p>
2806 <h4 id="_altosui_telegps_and_altosdroid_applications_3">E.30.2. AltosUI, TeleGPS and AltosDroid Applications</h4>
2807 <div class="paragraph">
2808 <p>AltosUI, TeleGPS and AltosDroid New Features:</p>
2813 <p>Automatically switch from meters or feet to kilometers or
2814 miles for distance units.</p>
2817 <p>Add Monitor Idle mode to TeleGPS application.</p>
2821 <div class="paragraph">
2822 <p>AltosUI, TeleGPS and AltosDroid Fixes:</p>
2827 <p>Abort map preloading when the preload map dialog is closed.</p>
2830 <p>In AltosDroid, Don’t reconnect to last device if the user
2831 had disconnected it the last time the application was
2838 <h4 id="_documentation">E.30.3. Documentation</h4>
2842 <p>Mention TeleMega v2.0 in hardware specs table.</p>
2845 <p>Document TeleGPS RF output in telegps manual.</p>
2852 <h3 id="_release_notes_for_version_1_6_3">E.31. Release Notes for Version 1.6.3</h3>
2853 <div class="paragraph">
2854 <p>Version 1.6.3 adds idle mode to AltosDroid and has bug fixes
2855 for our host software on desktops, laptops an android devices
2856 along with BlueTooth support for Windows.</p>
2859 <h4 id="_altos_30">E.31.1. AltOS</h4>
2860 <div class="paragraph">
2866 <p>Fix hardware flow control on TeleBT v3.0. RTS/CTS is
2867 wired backwards on this board, switch from using the
2868 hardware to driving these pins with software.</p>
2874 <h4 id="_altosui_and_telegps_applications_6">E.31.2. AltosUI and TeleGPS Applications</h4>
2875 <div class="paragraph">
2876 <p>AltosUI and TeleGPS New Features:</p>
2881 <p>Add BlueTooth support for Windows operating system. This
2882 supports connections to TeleBT over BlueTooth rather than
2887 <div class="paragraph">
2888 <p>AltosUI and TeleGPS Fixes:</p>
2893 <p>Change Java detection and install on Windows. Detection is
2894 now done by looking for the 'javaw.exe' program, and
2895 installation by opening a browser on the java.com web site.</p>
2898 <p>Delay polling while the Fire Igniters is visible to allow
2899 for TeleMega to report back complete status over the radio.</p>
2902 <p>Disallow changing RF calibration numbers in the
2903 configuration UI. There’s no good reason to change this from
2904 the field, and recovering is really hard if you haven’t
2905 written down the right number.</p>
2908 <p>Fix USB device discovery on Mac OS X El Capitan. This makes
2909 the connected Altus Metrum USB devices appear again.</p>
2912 <p>Fix acceleration data presented in MonitorIdle mode for
2913 TeleMetrum v2.0 flight computers.</p>
2919 <h4 id="_altosdroid_5">E.31.3. AltosDroid</h4>
2920 <div class="paragraph">
2921 <p>AltosDroid new features:</p>
2926 <p>Monitor Idle mode. Check state of flight computer while in
2927 idle mode over the radio link</p>
2930 <p>Fire Igniters. Remotely fire ignires for recovery system
2934 <p>Remote reboot. Cause the flight computer to reboot over the
2935 radio link. This provides a method for switching the flight
2936 computer from idle to flight mode without needing to reach
2937 the power switch.</p>
2940 <p>Configurable frequency menu. Change the set of available
2941 frequencies and provide more descriptive names.</p>
2945 <div class="paragraph">
2946 <p>AltosDroid bug fixes:</p>
2951 <p>Don’t set target location if GPS hasn’t locked yet.</p>
2954 <p>Fix saving target states so they can be reloaded when the
2955 application restarts. When the application is shut down and
2956 restarted, all previous target state information will be
2957 restored (including GPS position if available).</p>
2960 <p>Fix crash on some Android devices for offline maps when
2961 changing the map scale or location.</p>
2964 <p>Don’t require USB OTG support. This kept the latest
2965 AltosDroid from being offered on devices without USB device
2966 support, although it can work without that just fine using
2970 <p>Don’t require bluetooth to be enabled. This allows the
2971 application to operate with USB devices or just show old
2972 data without turning on the bluetooth radio.</p>
2975 <p>Recover old tracker positions when restarting
2976 application. This finally allows you to safely stop and
2977 restart the application without losing the last known
2978 location of any tracker.</p>
2984 <h4 id="_documentation_2">E.31.4. Documentation</h4>
2988 <p>Document TeleMega and EasyMega additional pyro channel
2989 continuity audio alert pattern.</p>
2993 <div style="page-break-after: always;"></div>
2997 <h3 id="_release_notes_for_version_1_6_2">E.32. Release Notes for Version 1.6.2</h3>
2998 <div class="paragraph">
2999 <p>Version 1.6.2 includes support for our updated TeleMega v2.0
3000 product and bug fixes in in the flight software for all our boards
3001 and ground station interfaces.</p>
3004 <h4 id="_altos_31">E.32.1. AltOS</h4>
3005 <div class="paragraph">
3006 <p>AltOS New Features:</p>
3011 <p>Add support for TeleMega v2.0 boards.</p>
3014 <p>Add PWM servo driver. There’s no higher level code using
3015 this yet, but the driver allows testing of the TeleMega v2.0
3016 servo output connector.</p>
3020 <div class="paragraph">
3026 <p>Slow down telemetry packets to allow receiver to keep
3033 <h4 id="_altosui_and_telegps_applications_7">E.32.2. AltosUI and TeleGPS Applications</h4>
3034 <div class="paragraph">
3035 <p>AltosUI and TeleGPS Fixes:</p>
3040 <p>Fix post-flight orientation computation when processing
3041 TeleMega and EasyMega eeprom data files.</p>
3044 <p>Capture complete eeprom data even when there are invalid
3045 entries in the data. This keeps reading eeprom contents and
3046 writing the associated .eeprom file when an error is detected.</p>
3052 <h4 id="_documentation_3">E.32.3. Documentation</h4>
3053 <div class="paragraph">
3054 <p>We spent a bunch of time trying to improve our documentation</p>
3059 <p>HTML versions now have a table of contents on the left side.</p>
3062 <p>EasyMini now has its own shorter manual.</p>
3065 <p>Provide links between sections in each document.</p>
3068 <p>Lots of minor rewriting and restructuring to avoid
3069 duplication of information</p>
3073 <div style="page-break-after: always;"></div>
3077 <h3 id="_release_notes_for_version_1_6_1">E.33. Release Notes for Version 1.6.1</h3>
3078 <div class="paragraph">
3079 <p>Version 1.6.1 includes support for our updated TeleBT v3.0
3080 product and bug fixes in in the flight software for all our boards
3081 and ground station interfaces.</p>
3084 <h4 id="_altos_32">E.33.1. AltOS</h4>
3085 <div class="paragraph">
3086 <p>AltOS New Features:</p>
3091 <p>Add support for TeleBT v3.0 boards.</p>
3094 <p>Add support for uncompressed APRS data, providing support
3095 for older APRS receivers. Uncompressed APRS data is less
3096 precise, takes more bandwidth and doesn’t have integrated
3101 <div class="paragraph">
3107 <p>Make TeleDongle and TeleBT more tolerant of data rate
3108 variations from transmitting devices.</p>
3114 <h4 id="_altosui_and_telegps_applications_8">E.33.2. AltosUI and TeleGPS Applications</h4>
3115 <div class="paragraph">
3116 <p>AltosUI and TeleGPS New Features:</p>
3121 <p>Add map to Monitor Idle display. It’s nice to be able to
3122 verify that maps are working, instead of needing to use
3127 <div class="paragraph">
3128 <p>AltosUI and TeleGPS Fixes:</p>
3133 <p>Fix frequency configuration to round values instead of
3134 truncate them, avoiding a common 1kHz error in the setting.</p>
3137 <p>Turn the Windows stub into a more useful program that can
3138 launch the application with parameters so that file manager
3139 icons work more reliably.</p>
3142 <p>Force KML export to use a C locale so that numbers are
3143 formatted with '.' instead of ',' for a decimal separator in
3147 <p>Preload map tiles based on distance rather than number of
3148 tiles; this means you get the same resolution covering the
3149 entire area, rather than having high resolution near the
3150 center and low resolution further away.</p>
3153 <p>Allow configuration of frequency and callsign in Monitor
3157 <p>Fix layout weirdness when resizing windows on
3158 Windows. Windows shouldn’t have giant blank spaces around
3159 the useful content anymore.</p>
3162 <p>Fix layout weirdness when resizing windows on
3163 Windows. Windows shouldn’t have giant blank spaces around
3164 the useful content anymore.</p>
3167 <p>Use a longer filter for descent speed values. This should
3168 provide something more useful on the display, although it
3169 will take longer to respond to changes now.</p>
3172 <p>Make Replay Flight run in realtime again. It had been set to
3173 run at 10x speed by mistake.</p>
3179 <h4 id="_altosdroid_6">E.33.3. AltosDroid</h4>
3180 <div class="paragraph">
3181 <p>AltosDroid New Features:</p>
3186 <p>Add offline map support using mapping code from AltosUI.</p>
3189 <p>Support TeleDongle (and TeleBT via USB) on devices
3190 supporting USB On-The-Go.</p>
3193 <p>Display additional TeleMega pyro channel status in Pad tab.</p>
3196 <p>Switch between metric and imperial units.</p>
3199 <p>Monitor TeleBT battery voltage.</p>
3202 <p>Track multiple devices at the same time, selecting between
3203 them with a menu or using the map.</p>
3206 <p>Add hybrid, satellite and terrain map types.</p>
3210 <div class="paragraph">
3211 <p>AltosDroid Fixes:</p>
3216 <p>Use standard Android display conventions so that a menu
3217 button is available in the application title bar.</p>
3220 <p>Adjust layout to work on large and small screens; shrinking
3221 the go/no-go lights in smaller environments to try and make
3222 everything visible.</p>
3225 <p>Make voice announcements depend on current tab.</p>
3228 <p>Compute adjustment to current travel direction while in
3229 motion towards rocket.</p>
3233 <div style="page-break-after: always;"></div>
3237 <h3 id="_release_notes_for_version_1_6">E.34. Release Notes for Version 1.6</h3>
3238 <div class="paragraph">
3239 <p>Version 1.6 includes support for our updated TeleDongle v3.0
3240 product and bug fixes in in the flight software for all our boards
3241 and ground station interfaces.</p>
3244 <h4 id="_altos_33">E.34.1. AltOS</h4>
3245 <div class="paragraph">
3246 <p>AltOS New Features</p>
3251 <p>Add support for TeleDongle v3.0 boards.</p>
3255 <div class="paragraph">
3261 <p>Don’t beep out the continuity twice by accident in idle mode.
3262 If the battery voltage report takes longer than the initialiation
3263 sequence, the igniter continuity would get reported twice.</p>
3266 <p>Record all 32 bits of gyro calibration data in TeleMega and
3267 EasyMega log files. This fixes computation of the gyro rates
3271 <p>Change TeleDongle LED usage. Green LED flashes when valid
3272 packet is received. Red LED flashes when invalid packet is
3276 <p>Replace LPC11U14 SPI driver with non-interrupt version. The
3277 interrupt code would occasionally wedge on long transfers
3278 if interrupts were blocked for too long. This affects all
3279 released TeleGPS products; if you have a TeleGPS device,
3280 you’ll want to reflash the firmware.</p>
3286 <h4 id="_altosui_and_telegps_applications_9">E.34.2. AltosUI and TeleGPS Applications</h4>
3287 <div class="paragraph">
3288 <p>AltosUI and TeleGPS New Features</p>
3293 <p>Compute tilt angle from TeleMega and EasyMega log
3294 files. This duplicates the quaternion-based angle tracking
3295 code from the flight firmware inside the ground station
3296 software so that post-flight analysis can include evaluation
3297 of the tilt angle.</p>
3300 <p>Shows the tool button window when starting with a data file
3301 specified. This means that opening a data file from the file
3302 manager will now bring up the main window to let you operate
3303 the whole application.</p>
3307 <div class="paragraph">
3308 <p>AltosUI Fixes</p>
3313 <p>Show the 'Connecting' dialog when using Monitor Idle. Lets
3314 you cancel the Monitor Idle startup when connecting over the
3318 <p>Make 'Monitor Idle' work for TeleGPS devices when connected
3319 over USB. It’s nice for testing without needing to broadcast
3323 <p>Use different Windows API to discover USB devices. This
3324 works better on my Windows 7 box, and will be used if the
3325 older API fails to provide the necessary information.</p>
3328 <p>Look in more places in the registry to try and identify the
3329 installed Java version on Windows. If you install the
3330 default 32-bit version of Windows on a 64-bit OS, the Java
3331 registry information is hiding \SOFTWARE\Wow6432Node for
3335 <p>Fix file association on Windows by searching for the
3336 javaw.exe program instead of assuming it is in
3337 %SYSTEMROOT%. This makes double-clicking on Altus Metrum
3338 data files in the file manager work correctly.</p>
3341 <p>When replaying a file, put 'done' in the Age field when we
3342 reach the end of the file, instead of continuing to count forever.</p>
3345 <p>In the Scan Channels code, wait for five seconds if we see
3346 any packet. This is needed because AltOS now sends the
3347 callsign, serial number and flight number only once every
3348 five seconds these days.</p>
3351 <p>In the Scan Channels code, reset pending flight state
3352 information each time we change channels. This avoids having
3353 flight computers appear on multiple frequencies by accident.</p>
3357 <div style="page-break-after: always;"></div>
3361 <h3 id="_release_notes_for_version_1_5">E.35. Release Notes for Version 1.5</h3>
3362 <div class="paragraph">
3363 <p>Version 1.5 is a major release. It includes support for our new
3364 EasyMega product, new features and bug fixes in in the flight
3365 software for all our boards and the AltosUI ground station</p>
3368 <h4 id="_altos_34">E.35.1. AltOS</h4>
3369 <div class="paragraph">
3370 <p>AltOS New Features</p>
3375 <p>Add support for EasyMega boards.</p>
3378 <p>Make the APRS SSID be configurable. This lets you track
3379 different rockets on the same receiver without getting
3380 things mixed up.</p>
3383 <p>Report extra pyro channel continuity state on EasyMega and
3384 TeleMega via the beeper. This lets you easily verify flight
3385 readiness on these boards after powering up the electronics
3389 <p>Add lower telemetry data rates (2400 and 9600 bps) to
3390 increase telemetry radio range. This reduces the amount of
3391 data received as well as increasing battery consumption in
3392 the transmitter.</p>
3395 <p>Change TeleGPS to have only a single log, and append new
3396 data to it rather than using seperate per-flight logs. This
3397 avoids accidentally filling up log storage by turning
3398 TeleGPS on/off several times.</p>
3402 <div class="paragraph">
3408 <p>Increase the maximum range for altitude values from +/-32767m
3409 to +/-2147483647m, allowing the flight computers to function
3410 correctly above the 32km level.</p>
3413 <p>Continuously test pyro firing conditions during delay stage,
3414 inhibiting the pyro channel if the test fails. This prevents
3415 firing pyro charges where the conditions were good before
3416 the delay, but become bad before the delay expires.</p>
3419 <p>Allow negative numbers in pyro configuration values. This
3420 lets you specify things like descending speed or
3427 <h4 id="_altosui_and_telegps_applications_10">E.35.2. AltosUI and TeleGPS Applications</h4>
3428 <div class="paragraph">
3429 <p>AltosUI and TeleGPS New Features</p>
3434 <p>Support telemetry baud rate selection. Adds menus to
3435 the flight monitoring and configuration for baud rate
3439 <p>Support APRS SSID configuration.</p>
3442 <p>Integrate with file managers. This provides icons for all of
3443 our file types and associates our application with the files
3444 so that using a file manager to open a AltOS data file
3445 results in launching our application.</p>
3449 <div class="paragraph">
3450 <p>AltosUI Fixes</p>
3455 <p>Make the 'Graph' button on the landed tab work again.</p>
3458 <p>Make tests for Java on Windows a bit smarter, and also
3459 provide the user with the option to skip installing Java for
3460 cases where we just can’t figure out what version is installed.</p>
3464 <div style="page-break-after: always;"></div>
3468 <h3 id="_release_notes_for_version_1_4_2">E.36. Release Notes for Version 1.4.2</h3>
3469 <div class="paragraph">
3470 <p>Version 1.4.2 is a minor release. It fixes Java-related install issues on
3474 <h4 id="_altosui_and_telegps_applications_11">E.36.1. AltosUI and TeleGPS Applications</h4>
3475 <div class="paragraph">
3476 <p>Windows Install Fixes</p>
3481 <p>Checks for Java installation data in more registry locations.</p>
3484 <p>Allows user to bypass Java installation in case the
3485 detection fails.</p>
3489 <div style="page-break-after: always;"></div>
3493 <h3 id="_release_notes_for_version_1_4_1">E.37. Release Notes for Version 1.4.1</h3>
3494 <div class="paragraph">
3495 <p>Version 1.4.1 is a minor release. It fixes install issues on
3496 Windows and provides the missing TeleMetrum V2.0 firmware. There
3497 aren’t any changes to the firmware or host applications at
3498 all. All Windows users will want to upgrade to get the signed
3499 driver, but Mac and Linux users who do not need the TeleMetrum
3500 V2.0 firmware image will not need to upgrade.</p>
3503 <h4 id="_altosui_and_telegps_applications_12">E.37.1. AltosUI and TeleGPS Applications:</h4>
3504 <div class="paragraph">
3505 <p>Windows Install Fixes</p>
3510 <p>Provide signed Windows driver files. This should avoid any need to
3511 disable driver signature checking on Windows 7 or 8.</p>
3514 <p>Fix Java version detection and download. Previously, the
3515 installer would only look for Java 6 or 7 and insist on
3516 downloading its own Java bits if there was something else
3517 installed. Furthermore, the 64-bit Java link provided didn’t
3518 work for anyone other than Keith, making it impossible to
3519 install AltOS on any machine with Java SE 8 installed.</p>
3523 <div class="paragraph">
3529 <p>Include 1.4 firmware for TeleMetrum V2.0. None of the
3530 installers shipped this file. Now it’s included in the AltOS
3531 packages for Linux, Mac and Windows.</p>
3534 <p>Include Google Application Key for map downloading. The 1.4
3535 release didn’t have this key in the released version of the
3536 software, making map downloading fail for most people.</p>
3540 <div style="page-break-after: always;"></div>
3544 <h3 id="_release_notes_for_version_1_4">E.38. Release Notes for Version 1.4</h3>
3545 <div class="paragraph">
3546 <p>Version 1.4 is a major release. It includes support for our new
3547 TeleGPS product, new features and bug fixes in in the flight
3548 software for all our boards and the AltosUI ground station</p>
3551 <h4 id="_altos_35">E.38.1. AltOS</h4>
3552 <div class="paragraph">
3553 <p>AltOS new features:</p>
3558 <p>Add support for TeleGPS boards.</p>
3561 <p>Make the beeper tone configurable, making it
3562 possible to distinguish between two Altus Metrum
3563 products in the same ebay.</p>
3566 <p>Make the firing time for extra pyro channels
3567 configurable, allowing longer (or shorter) than the
3568 default 50ms. Only relevant for TeleMega at this
3573 <div class="paragraph">
3579 <p>Replace the 'dit dit dit' tones at startup with the
3580 current battery voltage, measured in tenths of a
3581 volt. This lets you check the battery voltage
3582 without needing telemetry, which is especially
3583 useful on EasyMini.</p>
3586 <p>Change state beeping to "Farnsworth spacing", which
3587 means they’re quite a bit faster than before, and so
3588 they take less time to send.</p>
3591 <p>Fix bug preventing the selection of the 'Flight
3592 State After' mode in pyro configuration.</p>
3595 <p>Fix bug where erasing flights would reset the flight
3596 number to 2 on TeleMega and TeleMetrum v2.</p>
3599 <p>Fix u-Blox GPS driver to mark course and speed data
3600 as being present.</p>
3606 <h4 id="_altosui_application">E.38.2. AltosUI Application</h4>
3607 <div class="paragraph">
3608 <p>AltosUI new features:</p>
3613 <p>Add zooming and new content types (terrain and road
3614 maps) to map view. Change map storage format from
3615 PNG to Jpeg, which saves a huge amount of disk
3616 space. You will need to re-download all of your
3617 pre-loaded map images.</p>
3620 <p>Add a distance measuring device to the maps
3621 view. Select this by using any button other than the
3622 left one, or by pressing shift or control on the
3623 keyboard while using the left button.</p>
3626 <p>Add new 'Ignitor' tab to the flight monitor display
3627 for TeleMega’s extra ignitors.</p>
3630 <p>Add additional ignitor firing marks and voltages to
3631 the graph so you can see when the ignitors fired,
3632 along with the ignitor voltages.</p>
3635 <p>Add GPS course, ground speed and climb rate as
3636 optional graph elements.</p>
3640 <div class="paragraph">
3641 <p>AltosUI fixes:</p>
3646 <p>When flashing new firmware, re-try opening the
3647 device as sometimes it takes a while for the
3648 underlying operating system to recognize that the
3649 device has rebooted in preparation for the flashing
3653 <p>Hide Tilt Angle in ascent tab for devices that don’t
3657 <p>Increase the width of data lines in the graphs to
3658 make them easier to read.</p>
3661 <p>Filter out speed and acceleration spikes caused by
3662 ejection charge firing when computing the maximum
3663 values. This provides a more accurate reading of
3667 <p>Fix EasyMini voltage displays. Early EasyMini
3668 prototypes used a 3.0V regulator, and AltosUI still
3669 used that value as the basis of the
3670 computation. Production EasyMini boards have always
3671 shipped with a 3.3V regulator. Also, purple EasyMini
3672 boards sensed the battery voltage past the blocking
3673 diode, resulting in a drop of about 150mV from the
3674 true battery voltage. Compensate for that when
3675 displaying the value.</p>
3678 <p>Display error message when trying to configure
3679 maximum flight log size while the flight computer
3680 still has flight data stored.</p>
3683 <p>Handle TeleMetrum and TeleMini eeprom files
3684 generated with pre-1.0 firmware. Those ancient
3685 versions didn’t report the log format, so just use
3686 the product name instead.</p>
3692 <h4 id="_telegps_application_2">E.38.3. TeleGPS Application</h4>
3696 <p>New application designed for use with TeleGPS boards.</p>
3699 <p>Shares code with AltosUI, mostly just trimmed down
3700 to focus on TeleGPS-related functions.</p>
3706 <h4 id="_documentation_4">E.38.4. Documentation</h4>
3707 <div class="paragraph">
3708 <p>Documentation changes:</p>
3713 <p>Re-create the drill template images; they should
3714 print correctly from Firefox at least. Ship these as
3715 individual PDF files so they’re easy to print.</p>
3718 <p>Add a description of the 'Apogee Lockout' setting,
3719 which prevents the apogee charge from firing for a
3720 configurable amount of time after boost.</p>
3730 <div id="footer-text">
3732 Last updated 2024-04-28 20:36:09 -0600
projects / web / altusmetrum / blob