5 <meta http-equiv="X-UA-Compatible" content="IE=edge">
6 <meta name="viewport" content="width=device-width, initial-scale=1.0">
7 <meta name="generator" content="Asciidoctor 2.0.18">
8 <meta name="author" content="Keith Packard, Bdale Garbee">
9 <meta name="copyright" content="Bdale Garbee and Keith Packard 2022">
10 <title>TeleGPS Owner’s Manual</title>
11 <link rel="stylesheet" href="./am.css">
15 <h1>TeleGPS Owner’s Manual</h1>
17 <span id="author" class="author">Keith Packard</span><br>
18 <span id="email" class="email"><a href="mailto:keithp@keithp.com">keithp@keithp.com</a></span><br>
19 <span id="author2" class="author">Bdale Garbee</span><br>
20 <span id="email2" class="email"><a href="mailto:bdale@gag.com">bdale@gag.com</a></span><br>
21 <span id="revnumber">version v1.9.14,</span>
22 <span id="revdate">02 Feb 2023</span>
24 <div id="toc" class="toc">
25 <div id="toctitle">Table of Contents</div>
26 <ul class="sectlevel1">
27 <li><a href="#_license">License</a></li>
28 <li><a href="#_acknowledgments">Acknowledgments</a></li>
29 <li><a href="#_telegps_quick_start_guide">1. TeleGPS Quick Start Guide</a></li>
30 <li><a href="#_using_telegps_hardware">2. Using TeleGPS Hardware</a>
31 <ul class="sectlevel2">
32 <li><a href="#_hooking_up_lithium_polymer_batteries">2.1. Hooking Up Lithium Polymer Batteries</a></li>
33 <li><a href="#_on_board_data_recording">2.2. On-board Data Recording</a></li>
34 <li><a href="#_leds">2.3. LEDs</a></li>
35 <li><a href="#_installation">2.4. Installation</a></li>
38 <li><a href="#_telegps_application">3. TeleGPS Application</a>
39 <ul class="sectlevel2">
40 <li><a href="#_telemetry_monitoring">3.1. Telemetry Monitoring</a></li>
41 <li><a href="#_telegps_menus">3.2. TeleGPS Menus</a></li>
42 <li><a href="#_graph_data">3.3. Graph Data</a></li>
43 <li><a href="#_export_data">3.4. Export Data</a></li>
44 <li><a href="#_load_maps">3.5. Load Maps</a></li>
45 <li><a href="#_preferences">3.6. Preferences</a></li>
46 <li><a href="#_close">3.7. Close</a></li>
47 <li><a href="#_exit">3.8. Exit</a></li>
48 <li><a href="#_connect_device">3.9. Connect Device</a></li>
49 <li><a href="#_disconnect">3.10. Disconnect</a></li>
50 <li><a href="#_scan_channels">3.11. Scan Channels</a></li>
51 <li><a href="#_download_data">3.12. Download Data</a></li>
52 <li><a href="#_configure_device">3.13. Configure Device</a></li>
53 <li><a href="#_flash_device">3.14. Flash Device</a></li>
56 <li><a href="#_telegps_system_operation">Appendix A: TeleGPS System Operation</a>
57 <ul class="sectlevel2">
58 <li><a href="#_gfsk_telemetry">A.1. GFSK Telemetry</a></li>
59 <li><a href="#_aprs">A.2. APRS</a></li>
60 <li><a href="#_configurable_parameters">A.3. Configurable Parameters</a></li>
63 <li><a href="#_handling_precautions">Appendix B: Handling Precautions</a></li>
64 <li><a href="#_technical_information">Appendix C: Technical Information</a>
65 <ul class="sectlevel2">
66 <li><a href="#_gps_receiver">C.1. GPS Receiver</a></li>
67 <li><a href="#_70cm_transmitter">C.2. 70cm Transmitter</a></li>
68 <li><a href="#_micro_controller">C.3. Micro-controller</a></li>
69 <li><a href="#_lithium_polymer_battery">C.4. Lithium Polymer Battery</a></li>
70 <li><a href="#_mechanical_considerations">C.5. Mechanical Considerations</a></li>
71 <li><a href="#_on_board_data_storage">C.6. On-board data storage</a></li>
74 <li><a href="#_updating_device_firmware">Appendix D: Updating Device Firmware</a>
75 <ul class="sectlevel2">
76 <li><a href="#_updating_telegps_firmware">D.1. Updating TeleGPS Firmware</a></li>
79 <li><a href="#_release_notes">Appendix E: Release Notes</a>
80 <ul class="sectlevel2">
81 <li><a href="#_release_notes_for_version_1_9_14">E.1. Release Notes for Version 1.9.14</a></li>
82 <li><a href="#_release_notes_for_version_1_9_13">E.2. Release Notes for Version 1.9.13</a></li>
83 <li><a href="#_release_notes_for_version_1_9_12">E.3. Release Notes for Version 1.9.12</a></li>
84 <li><a href="#_release_notes_for_version_1_9_11">E.4. Release Notes for Version 1.9.11</a></li>
85 <li><a href="#_release_notes_for_version_1_9_10">E.5. Release Notes for Version 1.9.10</a></li>
86 <li><a href="#_release_notes_for_version_1_9_9">E.6. Release Notes for Version 1.9.9</a></li>
87 <li><a href="#_release_notes_for_version_1_9_8">E.7. Release Notes for Version 1.9.8</a></li>
88 <li><a href="#_release_notes_for_version_1_9_7">E.8. Release Notes for Version 1.9.7</a></li>
89 <li><a href="#_release_notes_for_version_1_9_6">E.9. Release Notes for Version 1.9.6</a></li>
90 <li><a href="#_release_notes_for_version_1_9_5">E.10. Release Notes for Version 1.9.5</a></li>
91 <li><a href="#_release_notes_for_version_1_9_4">E.11. Release Notes for Version 1.9.4</a></li>
92 <li><a href="#_release_notes_for_version_1_9_3">E.12. Release Notes for Version 1.9.3</a></li>
93 <li><a href="#_release_notes_for_version_1_9_1">E.13. Release Notes for Version 1.9.1</a></li>
94 <li><a href="#_release_notes_for_version_1_9">E.14. Release Notes for Version 1.9</a></li>
95 <li><a href="#_release_notes_for_version_1_8_7">E.15. Release Notes for Version 1.8.7</a></li>
96 <li><a href="#_release_notes_for_version_1_8_6">E.16. Release Notes for Version 1.8.6</a></li>
97 <li><a href="#_release_notes_for_version_1_8_5">E.17. Release Notes for Version 1.8.5</a></li>
98 <li><a href="#_release_notes_for_version_1_8_4">E.18. Release Notes for Version 1.8.4</a></li>
99 <li><a href="#_release_notes_for_version_1_8_3">E.19. Release Notes for Version 1.8.3</a></li>
100 <li><a href="#_release_notes_for_version_1_8_2">E.20. Release Notes for Version 1.8.2</a></li>
101 <li><a href="#_release_notes_for_version_1_8_1">E.21. Release Notes for Version 1.8.1</a></li>
102 <li><a href="#_release_notes_for_version_1_8">E.22. Release Notes for Version 1.8</a></li>
103 <li><a href="#_release_notes_for_version_1_7">E.23. Release Notes for Version 1.7</a></li>
104 <li><a href="#_release_notes_for_version_1_6_8">E.24. Release Notes for Version 1.6.8</a></li>
105 <li><a href="#_release_notes_for_version_1_6_5">E.25. Release Notes for Version 1.6.5</a></li>
106 <li><a href="#_release_notes_for_version_1_6_4">E.26. Release Notes for Version 1.6.4</a></li>
107 <li><a href="#_release_notes_for_version_1_6_3">E.27. Release Notes for Version 1.6.3</a></li>
108 <li><a href="#_release_notes_for_version_1_6_2">E.28. Release Notes for Version 1.6.2</a></li>
109 <li><a href="#_release_notes_for_version_1_6_1">E.29. Release Notes for Version 1.6.1</a></li>
110 <li><a href="#_release_notes_for_version_1_6">E.30. Release Notes for Version 1.6</a></li>
111 <li><a href="#_release_notes_for_version_1_5">E.31. Release Notes for Version 1.5</a></li>
112 <li><a href="#_release_notes_for_version_1_4_2">E.32. Release Notes for Version 1.4.2</a></li>
113 <li><a href="#_release_notes_for_version_1_4_1">E.33. Release Notes for Version 1.4.1</a></li>
114 <li><a href="#_release_notes_for_version_1_4">E.34. Release Notes for Version 1.4</a></li>
122 <div class="sectionbody">
123 <div id="logo" class="imageblock">
124 <div class="content">
125 <a class="image" href="https://altusmetrum.org"><img src="altusmetrum-oneline.svg" alt="Altus Metrum"></a>
131 <h2 id="_license">License</h2>
132 <div class="sectionbody">
133 <div class="paragraph">
134 <p>Copyright © 2023 Bdale Garbee and Keith Packard</p>
136 <div class="paragraph">
137 <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>
142 <h2 id="_acknowledgments">Acknowledgments</h2>
143 <div class="sectionbody">
144 <div class="paragraph">
145 <p>Thanks to Anthony (AJ) Towns for major contributions including
146 the TeleGPS graphing and site map code and associated documentation.
147 Free software means that our customers and friends can become our
148 collaborators, and we certainly appreciate this level of
151 <div class="paragraph">
152 <p>Have fun using these products, and we hope to meet all of you
153 out on the rocket flight line somewhere.</p>
155 <div class="verseblock">
156 <pre class="content">Bdale Garbee, KB0G
157 NAR #87103, TRA #12201</pre>
159 <div class="verseblock">
160 <pre class="content">Keith Packard, K7WQ
161 NAR #88757, TRA #12200</pre>
166 <h2 id="_telegps_quick_start_guide">1. TeleGPS Quick Start Guide</h2>
167 <div class="sectionbody">
168 <div class="paragraph">
169 <p>TeleGPS is designed to be easy to use. Requiring no external
170 components, flying takes just a few steps.</p>
172 <div class="olist arabic">
175 <p>First, download and install the software from
176 <a href="http://altusmetrum.org/AltOS" class="bare">http://altusmetrum.org/AltOS</a>. This will make sure that
177 you have the right device drivers installed.</p>
180 <p>Next, plug in the battery and USB cable and connect TeleGPS to
181 your computer. This will charge the battery and allow you to
182 configure the device.</p>
185 <p>Start the TeleGPS application and set the callsign and frequency
186 on your TeleGPS device; refer to <a href="#_configure_device">Configure Device</a> for instructions.</p>
189 <p>Unplug TeleGPS when the battery charger light goes green. This
190 will enable the radio and logging portions of the TeleGPS
194 <p>Connect TeleDongle to your computer and start TeleGPS or start
195 AltosDroid on your android device and connect to TeleBT. Set the
196 frequency to match the TeleGPS and you should be receiving telemetry.</p>
203 <h2 id="_using_telegps_hardware">2. Using TeleGPS Hardware</h2>
204 <div class="sectionbody">
206 <h3 id="_hooking_up_lithium_polymer_batteries">2.1. Hooking Up Lithium Polymer Batteries</h3>
207 <div class="paragraph">
208 <p>TeleGPS has a two pin JST PH series connector to connect up
209 a single-cell Lithium Polymer cell (3.7V nominal). You can
210 purchase matching batteries from the Altus Metrum store, or
211 other vendors, or you can make your own. Pin 1 of the
212 connector is positive, pin 2 is negative. Spark Fun sells a
213 cable with the connector attached, which they call a
214 <a href="https://www.sparkfun.com/products/9914">JST Jumper 2 Wire Assembly</a></p>
216 <div class="admonitionblock warning">
220 <div class="title">Warning</div>
223 Many RC vendors also sell lithium polymer batteries with
224 this same connector. All that we have found use the opposite
225 polarity, and if you use them that way, you will damage or
233 <h3 id="_on_board_data_recording">2.2. On-board Data Recording</h3>
234 <div class="paragraph">
235 <p>TeleGPS logs GPS data at a user-configurable
236 rate. Data are logged to a 2MB on-board flash memory
237 part, which can be partitioned into several
238 equal-sized blocks, one for each flight. 64kB of this
239 storage are reserved to hold configuration data,
240 leaving 1984kB for flight data.</p>
242 <div class="paragraph">
243 <p>The on-board flash is partitioned into separate flight
244 logs, each of a fixed maximum size. Increase the
245 maximum size of each log and you reduce the number of
246 flights that can be stored. Decrease the size and you
247 can store more flights.</p>
249 <div class="paragraph">
250 <p>To compute the amount of space needed for a single
251 log, you can divide the expected time (in seconds) by
252 the sample period (by default, 1 second per sample)
253 and then multiply the result by 32 bytes per
254 sample. For instance, a sample period of 1 second and
255 a flight lasting one hour will take 32 * 3600 = 115200
256 bytes. TeleGPS does try to reduce log space used by
257 not recording position information when it isn’t
258 moving, so actual space consumed may be less than
261 <div class="paragraph">
262 <p>The default size allows for four flights of 496kB
263 each, which provides over four hours of logging at 1
264 sample per second.</p>
266 <div class="paragraph">
267 <p>TeleGPS will not overwrite existing flight data, so be
268 sure to download flight data and erase it from the
269 onboard flash before it fills up. TeleGPS will still
270 report telemetry even if memory is full, so the only
271 thing you will lose is the on-board data log.</p>
275 <h3 id="_leds">2.3. LEDs</h3>
276 <div class="paragraph">
277 <p>TeleGPS v1.0 has a dual greed/red LED along the edge
278 towards the USB connector end of the board. This
279 indicates battery charging status while connected to
280 power over USB. When the red LED is lit, the battery
281 is charging. Once the battery is fully charged, the
282 red LED goes out and the green LED turns on. If both
283 LEDs are lit, something is probably wrong with the battery.</p>
285 <div class="paragraph">
286 <p>TeleGPS v2.0 has the same green/red battery charging
287 status LED and adds another green LED along the same
288 edge, towards end of the board with the 70cm
289 antenna. This green LED indicates GPS lock status — it
290 blinks once every three seconds when the GPS receiver
291 is locked and tracking position.</p>
295 <h3 id="_installation">2.4. Installation</h3>
296 <div class="paragraph">
297 <p>The battery connectors are a standard 2-pin JST
298 connector and match batteries sold by Spark Fun. These
299 batteries are single-cell Lithium Polymer batteries
300 that nominally provide 3.7 volts. Other vendors sell
301 similar batteries for RC aircraft using mating
302 connectors, however the polarity for those is
303 generally reversed from the batteries used by Altus
304 Metrum products. In particular, the Tenergy batteries
305 supplied for use in Featherweight flight computers are
306 not compatible with Altus Metrum flight computers or
307 battery chargers.</p>
309 <div class="admonitionblock warning">
313 <div class="title">Warning</div>
316 Check polarity and voltage before connecting any
317 battery not purchased from Altus Metrum or Spark
323 <div class="paragraph">
324 <p>TeleGPS uses an integrate GPS patch antenna and won’t
325 receive GPS signals if installed inside a metal or
326 carbon fiber compartment. Test GPS reception and
327 telemetry transmission with the system installed and
328 all other electronics powered up to verify signal
329 reception and make sure there isn’t any interference
330 from other systems.</p>
336 <h2 id="_telegps_application">3. TeleGPS Application</h2>
337 <div class="sectionbody">
338 <div class="paragraph">
339 <p>The TeleGPS application provides a graphical user interface for
340 interacting with the Altus Metrum product family. TeleGPS can
341 monitor telemetry data, configure devices and many other
342 tasks. The primary interface window is for displaying data
343 received over the telemetry link. There are additional
344 tasks available from the main window menu bar.</p>
347 <h3 id="_telemetry_monitoring">3.1. Telemetry Monitoring</h3>
348 <div class="paragraph">
349 <p>This is the window brought up when you start the
350 application. If you have a TeleDongle device connected
351 to the computer, it will automatically be selected for
352 telemetry monitoring</p>
354 <div class="paragraph">
355 <p>All telemetry data received are automatically recorded
356 in suitable log files. The name of the files includes
357 the current date and TeleGPS serial and flight
360 <div class="paragraph">
361 <p>The radio frequency being monitored by the TeleDongle
362 device is displayed at the top of the window. You can
363 configure the frequency by clicking on the frequency
364 box and selecting the desired frequency. The TeleGPS
365 application remembers the last frequency selected for
366 each TeleDongle and selects that automatically the
367 next time you use that device.</p>
369 <div class="paragraph">
370 <p>Below the TeleDongle frequency selector, the window
371 contains a few significant pieces of information about
372 the altimeter providing the telemetry data stream:</p>
377 <p>The configured call-sign</p>
380 <p>The device serial number</p>
383 <p>The flight number. TeleGPS remembers how many times
387 <p>The Received Signal Strength Indicator value. This
388 lets you know how strong a signal TeleDongle is
389 receiving. The radio inside TeleDongle operates down
390 to about -100dBm; weaker signals may not be
391 receivable. The packet link uses error detection and
392 correction techniques which prevent incorrect data
393 from being reported.</p>
396 <p>The age of the displayed data, in seconds since the
397 last successfully received telemetry packet. In
398 normal operation this will stay in the low single
399 digits. If the number starts counting up, then you
400 are no longer receiving data over the radio link
401 from the flight computer.</p>
405 <div class="paragraph">
406 <p>Finally, the largest portion of the window contains a set of
407 tabs, each of which contain some information about the TeleGPS
408 board. The final 'table' tab displays many of the raw telemetry
409 values in one place in a spreadsheet-like format.</p>
412 <h4 id="_map">3.1.1. Map</h4>
413 <div class="paragraph">
414 <p>The Map tab shows the TeleGPS track over time
415 on top of map data making it easy to locate
418 <div class="imageblock">
419 <div class="content">
420 <img src="telegps-map.png" alt="telegps map" width="400">
422 <div class="title">Figure 1. TeleGPS Map View</div>
424 <div class="paragraph">
425 <p>The map’s default scale is approximately 3m
426 (10ft) per pixel. The map can be dragged using
427 the left mouse button. The map will attempt to
428 keep the rocket roughly centered while data is
431 <div class="paragraph">
432 <p>You can adjust the style of map and the zoom
433 level with buttons on the right side of the
434 map window. You can draw a line on the map by
435 moving the mouse over the map with a button
436 other than the left one pressed, or by
437 pressing the left button while also holding
438 down the shift key. The length of the line in
439 real-world units will be shown at the start of
442 <div class="paragraph">
443 <p>Images are fetched automatically via the
444 Google Maps Static API, and cached on disk for
445 reuse. If map images cannot be downloaded, the
446 rocket’s path will be traced on a dark gray
447 background instead.</p>
449 <div class="paragraph">
450 <p>You can pre-load images for your favorite
451 launch sites before you leave home; check out
452 <a href="#_load_maps">Load Maps</a>.</p>
456 <h4 id="_location">3.1.2. Location</h4>
457 <div class="paragraph">
458 <p>The Location tab shows the raw GPS data
459 received from TeleGPS.</p>
461 <div class="imageblock">
462 <div class="content">
463 <img src="telegps-location.png" alt="telegps location" width="400">
465 <div class="title">Figure 2. TeleGPS Location View</div>
469 <h4 id="_status">3.1.3. Status</h4>
470 <div class="paragraph">
471 <p>The Status tab shows data relative to the
472 location of TeleGPS when the application first
473 received telemetry from it.</p>
475 <div class="imageblock">
476 <div class="content">
477 <img src="telegps-status.png" alt="telegps status" width="400">
479 <div class="title">Figure 3. TeleGPS Status View</div>
483 <h4 id="_table">3.1.4. Table</h4>
484 <div class="paragraph">
485 <p>The Table tab shows detailed information about
488 <div class="imageblock">
489 <div class="content">
490 <img src="telegps-table.png" alt="telegps table" width="400">
492 <div class="title">Figure 4. TeleGPS Information Table</div>
497 <h3 id="_telegps_menus">3.2. TeleGPS Menus</h3>
498 <div class="paragraph">
499 <p>TeleGPS has three or four menus at the top of
504 <dt class="hdlist1">File</dt>
506 <p>New Window, Graph Data, Export Data, Load Maps,
507 Preferences, Close and Exit</p>
509 <dt class="hdlist1">Monitor</dt>
511 <p>Connect Device, Disconnect and Scan Channels</p>
513 <dt class="hdlist1">Device</dt>
515 <p>Download Data, Configure Device and Flash Device</p>
517 <dt class="hdlist1">Frequency</dt>
519 <p>This shows the current monitoring frequency with a
520 drop-down menu listing other configured
521 frequencies. You can change the set of frequencies
522 shown here from the Preferences dialog. This menu is
523 only shown when the TeleGPS application is connected
524 to a TeleDongle or TeleBT device.</p>
529 <h4 id="_new_window">3.2.1. New Window</h4>
530 <div class="paragraph">
531 <p>This creates another telemetry monitoring window, in case
532 you have multiple TeleDongle devices connected to the
538 <h3 id="_graph_data">3.3. Graph Data</h3>
539 <div class="paragraph">
540 <p>The Graph tab shows a plot of the the GPS data
541 collected. The X axis is time in seconds; there are a
542 variety of Y axes available for different kinds of
543 data. This window also allows you to see some
544 statistics computed from the data, and an overall map
545 of the entire data record.</p>
548 <h4 id="_data_graph">3.3.1. Data Graph</h4>
549 <div class="imageblock">
550 <div class="content">
551 <img src="telegps-graph-graph.png" alt="telegps graph graph" width="400">
553 <div class="title">Figure 5. TeleGPS Graph</div>
557 <h4 id="_graph_configuration">3.3.2. Graph Configuration</h4>
558 <div class="imageblock">
559 <div class="content">
560 <img src="telegps-graph-configure.png" alt="telegps graph configure" width="400">
562 <div class="title">Figure 6. TeleGPS Graph Configuration</div>
564 <div class="paragraph">
565 <p>This selects which graph elements to show, and, at the
566 bottom, lets you switch between metric and imperial
571 <h4 id="_statistics">3.3.3. Statistics</h4>
572 <div class="imageblock">
573 <div class="content">
574 <img src="telegps-graph-stats.png" alt="telegps graph stats" width="400">
576 <div class="title">Figure 7. TeleGPS Statistics</div>
578 <div class="paragraph">
579 <p>Shows overall data computed from the flight.</p>
583 <h4 id="_map_2">3.3.4. Map</h4>
584 <div class="imageblock">
585 <div class="content">
586 <img src="telegps-graph-map.png" alt="telegps graph map" width="450">
588 <div class="title">Figure 8. TeleGPS Map</div>
590 <div class="paragraph">
591 <p>Shows a map of the area overlaid with the GPS track. As with
592 the telemetry monitoring window, you can select the style
593 of map and zoom level using buttons along the side;
594 you can scroll the map by dragging within the map pressing
595 the left button and you can draw a line to measure
596 distances using either the left button with the shift key,
597 or any other button.</p>
602 <h3 id="_export_data">3.4. Export Data</h3>
603 <div class="paragraph">
604 <p>This tool takes the raw data files and makes them
605 available for external analysis. When you select this
606 button, you are prompted to select a data file, which
607 can be either a .eeprom or .telem. The .eeprom files
608 contain higher resolution and more continuous data,
609 while .telem files contain receiver signal strength
610 information. Next, a second dialog appears which is
611 used to select where to write the resulting file. It
612 has a selector to choose between CSV and KML file
616 <h4 id="_comma_separated_value_format">3.4.1. Comma Separated Value Format</h4>
617 <div class="paragraph">
618 <p>This is a text file containing the data in a
619 form suitable for import into a spreadsheet or
620 other external data analysis tool. The first
621 few lines of the file contain the version and
622 configuration information from TeleGPS, then
623 there is a single header line which labels all
624 of the fields. All of these lines start with a
625 '#' character which many tools can be
626 configured to skip over.</p>
628 <div class="paragraph">
629 <p>The remaining lines of the file contain the
630 data, with each field separated by a comma and
631 at least one space. All of the sensor values
632 are converted to standard units, with the
633 barometric data reported in both pressure,
634 altitude and height above pad units.</p>
638 <h4 id="_keyhole_markup_language_for_google_earth">3.4.2. Keyhole Markup Language (for Google Earth)</h4>
639 <div class="paragraph">
640 <p>This is the format used by Google Earth to provide an overlay
641 within that application. With this, you can use Google Earth to
642 see the whole path in 3D.</p>
647 <h3 id="_load_maps">3.5. Load Maps</h3>
648 <div class="imageblock">
649 <div class="content">
650 <img src="load-maps.png" alt="load maps" width="500">
652 <div class="title">Figure 9. Load Maps Window</div>
654 <div class="paragraph">
655 <p>Before heading out to a new launch site, you can use
656 this to load satellite images in case you don’t have
657 internet connectivity at the site. Try not to wait
658 until the last minute, though, particularly if you’re
659 heading to a major launch. If too many people are
660 all trying to download map data at once, Google may
661 limit access until the next day.</p>
663 <div class="paragraph">
664 <p>There’s a drop-down menu of launch sites we know
665 about; if your favorites aren’t there, please let us
666 know the lat/lon and name of the site. The contents of
667 this list are actually downloaded from our server at
668 run-time, so as new sites are sent in, they’ll get
669 automatically added to this list. If the launch site
670 isn’t in the list, you can manually enter the lat/lon
673 <div class="paragraph">
674 <p>There are four different kinds of maps you can view;
675 you can select which to download by selecting as many
676 as you like from the available types:</p>
680 <dt class="hdlist1">Hybrid</dt>
682 <p>A combination of satellite imagery and road data. This
683 is the default view.</p>
685 <dt class="hdlist1">Satellite</dt>
687 <p>Just the satellite imagery without any annotation.</p>
689 <dt class="hdlist1">Roadmap</dt>
691 <p>Roads, political boundaries and a few geographic
694 <dt class="hdlist1">Terrain</dt>
696 <p>Contour intervals and shading that show hills and
701 <div class="paragraph">
702 <p>You can specify the range of zoom levels to download;
703 smaller numbers show more area with less
704 resolution. The default level, 0, shows about
705 3m/pixel. One zoom level change doubles or halves that
706 number. Larger zoom levels show more detail, smaller
707 zoom levels less.</p>
709 <div class="paragraph">
710 <p>The Map Radius value sets how large an area around the
711 center point to download. Select a value large enough
712 to cover any plausible flight from that site. Be aware
713 that loading a large area with a high maximum zoom
714 level can attempt to download a lot of data. Loading
715 hybrid maps with a 10km radius at a minimum zoom of -2
716 and a maximum zoom of 2 consumes about 120MB of
717 space. Terrain and road maps consume about 1/10 as
718 much space as satellite or hybrid maps.</p>
720 <div class="paragraph">
721 <p>Clicking the 'Load Map' button will fetch images from
722 Google Maps; note that Google limits how many images
723 you can fetch at once, so if you load more than one
724 launch site, you may get some gray areas in the map
725 which indicate that Google is tired of sending data to
726 you. Try again later.</p>
730 <h3 id="_preferences">3.6. Preferences</h3>
731 <div class="imageblock">
732 <div class="content">
733 <img src="telegps-preferences.png" alt="telegps preferences" width="230">
735 <div class="title">Figure 10. TeleGPS Preferences Window</div>
738 <h4 id="_voice_settings">3.6.1. Voice Settings</h4>
739 <div class="paragraph">
740 <p>TeleGPS provides voice announcements during
741 flight so that you can keep your eyes on the
742 sky and still get information about the
743 current flight status. However, sometimes you
744 don’t want to hear them.</p>
748 <dt class="hdlist1">Enable</dt>
750 <p>Turns all voice announcements on and off</p>
752 <dt class="hdlist1">Test Voice</dt>
754 <p>Plays a short message allowing you to verify
755 that the audio system is working and the volume settings
762 <h4 id="_log_directory">3.6.2. Log Directory</h4>
763 <div class="paragraph">
764 <p>TeleGPS logs all telemetry data and saves all
765 flash data to this directory. This
766 directory is also used as the staring point
767 when selecting data files for display or
770 <div class="paragraph">
771 <p>Click on the directory name to bring up a
772 directory choosing dialog, select a new
773 directory and click 'Select Directory' to
774 change where TeleGPS reads and writes data
779 <h4 id="_callsign">3.6.3. Callsign</h4>
780 <div class="paragraph">
781 <p>This value is transmitted in each command
782 packet sent from TeleDongle and received from
783 an altimeter. It is not used in telemetry
784 mode, as the callsign configured in the
785 altimeter board is included in all telemetry
786 packets. Configure this with the TeleGPS
787 operators call sign as needed to comply with
788 your local radio regulations.</p>
790 <div class="paragraph">
791 <p>Note that to successfully command a flight
792 computer over the radio (to configure the
793 altimeter, monitor idle, or fire pyro
794 charges), the callsign configured here must
795 exactly match the callsign configured in the
796 flight computer. This matching is case
801 <h4 id="_imperial_units">3.6.4. Imperial Units</h4>
802 <div class="paragraph">
803 <p>This switches between metric units (meters)
804 and imperial units (feet and miles). This
805 affects the display of values use during
806 flight monitoring, configuration, data
807 graphing and all of the voice
808 announcements. It does not change the units
809 used when exporting to CSV files, those are
810 always produced in metric units.</p>
814 <h4 id="_serial_debug">3.6.5. Serial Debug</h4>
815 <div class="paragraph">
816 <p>This causes all communication with a connected
817 device to be dumped to the console from which
818 TeleGPS was started. If you’ve started it from
819 an icon or menu entry, the output will simply
820 be discarded. This mode can be useful to debug
821 various serial communication issues.</p>
825 <h4 id="_font_size">3.6.6. Font size</h4>
826 <div class="paragraph">
827 <p>Selects the set of fonts used in the flight
828 monitor window. Choose between the small,
829 medium and large sets.</p>
833 <h4 id="_look_feel">3.6.7. Look & feel</h4>
834 <div class="paragraph">
835 <p>Switches between the available Java user
836 interface appearances. The default selection
837 is supposed to match the native window system
838 appearance for the target platform.</p>
842 <h4 id="_menu_position">3.6.8. Menu position</h4>
843 <div class="paragraph">
844 <p>Selects the initial position for the main
845 TeleGPS window that includes all of the
850 <h4 id="_map_cache_size">3.6.9. Map Cache Size</h4>
851 <div class="paragraph">
852 <p>Sets the number of map 'tiles' kept in memory
853 while the application is running. More tiles
854 consume more memory, but will make panning
855 around the map faster.</p>
859 <h4 id="_manage_frequencies">3.6.10. Manage Frequencies</h4>
860 <div class="paragraph">
861 <p>This brings up a dialog where you can
862 configure the set of frequencies shown in the
863 various frequency menus. You can add as many
864 as you like, or even reconfigure the default
865 set. Changing this list does not affect the
866 frequency settings of any devices, it only
867 changes the set of frequencies shown in the
873 <h3 id="_close">3.7. Close</h3>
874 <div class="paragraph">
875 <p>This closes the current window, leaving any other windows
876 open and the application running.</p>
880 <h3 id="_exit">3.8. Exit</h3>
881 <div class="paragraph">
882 <p>This closes all TeleGPS windows and terminates the
887 <h3 id="_connect_device">3.9. Connect Device</h3>
888 <div class="paragraph">
889 <p>Selecting this item brings up a dialog box listing all
890 of the connected TeleDongle devices. When you choose
891 one of these, AltosUI will display telemetry data as
892 received by the selected TeleDongle device.</p>
894 <div class="imageblock">
895 <div class="content">
896 <img src="device-selection.png" alt="device selection" width="300">
898 <div class="title">Figure 11. Device Selection Dialog</div>
902 <h3 id="_disconnect">3.10. Disconnect</h3>
903 <div class="paragraph">
904 <p>Disconnects the currently connected TeleDongle or
909 <h3 id="_scan_channels">3.11. Scan Channels</h3>
910 <div class="imageblock">
911 <div class="content">
912 <img src="telegps-scan.png" alt="telegps scan" width="300">
914 <div class="title">Figure 12. Radio Scanning Dialog</div>
916 <div class="paragraph">
917 <p>Scans the configured set of frequencies looking for
918 telemetry signals. A list of all of the discovered
919 signals is show; selecting one of those and clicking
920 on 'Monitor' will select that frequency in the
921 associated TeleGPS application window.</p>
925 <h3 id="_download_data">3.12. Download Data</h3>
926 <div class="paragraph">
927 <p>TeleGPS records data to its internal flash memory.
928 On-board data is recorded at the same rate as
929 telemetry but is not subject to radio drop-outs. As
930 such, it generally provides a more complete and
931 precise record. The 'Download Data' menu entry allows
932 you to read the flash memory and write it to disk.</p>
934 <div class="paragraph">
935 <p>Select the 'Download Data' menu entry to bring up a
936 list of connected TeleGPS devices. After the device
937 has been selected, a dialog showing the data stored in
938 the device will be shown allowing you to select which
939 entries to download and which to delete. You must
940 erase flights in order for the space they consume to
941 be reused by another track. This prevents accidentally
942 losing data if you neglect to download data before
943 starting TeleGPS again. Note that if there is no more
944 space available in the device, then no data will be
947 <div class="paragraph">
948 <p>The file name for each data log is computed
949 automatically from the recorded date, altimeter serial
950 number and flight number information.</p>
954 <h3 id="_configure_device">3.13. Configure Device</h3>
955 <div class="imageblock">
956 <div class="content">
957 <img src="telegps-configure.png" alt="telegps configure" width="350">
959 <div class="title">Figure 13. TeleGPS Configuration Dialog</div>
961 <div class="paragraph">
962 <p>Select this button and then select any connected TeleGPS
963 device from the list provided.</p>
965 <div class="paragraph">
966 <p>The first few lines of the dialog provide information
967 about the connected device, including the product
968 name, software version and hardware serial
969 number. Below that are the individual configuration
972 <div class="paragraph">
973 <p>At the bottom of the dialog, there are four buttons:</p>
977 <dt class="hdlist1">Save</dt>
979 <p>This writes any changes to the configuration parameter
980 block in flash memory. If you don’t press this button,
981 any changes you make will be lost.</p>
983 <dt class="hdlist1">Reset</dt>
985 <p>This resets the dialog to the most recently saved
986 values, erasing any changes you have made.</p>
988 <dt class="hdlist1">Reboot</dt>
990 <p>This reboots the device. Use this to switch from idle
991 to pad mode by rebooting once the rocket is oriented
992 for flight, or to confirm changes you think you saved
993 are really saved.</p>
995 <dt class="hdlist1">Close</dt>
997 <p>This closes the dialog. Any unsaved changes will be
1002 <div class="paragraph">
1003 <p>The rest of the dialog contains the parameters to be configured.</p>
1006 <h4 id="_frequency">3.13.1. Frequency</h4>
1007 <div class="paragraph">
1008 <p>This configures which of the frequencies to use for
1009 both telemetry and packet command mode. Note that if
1010 you set this value via packet command mode, the
1011 TeleDongle frequency will also be automatically
1012 reconfigured to match so that communication will
1013 continue afterwards.</p>
1017 <h4 id="_rf_calibration">3.13.2. RF Calibration</h4>
1018 <div class="paragraph">
1019 <p>The radios in every Altus Metrum device are calibrated
1020 at the factory to ensure that they transmit and
1021 receive on the specified frequency. If you need to
1022 you can adjust the calibration by changing this value.
1023 Do not do this without understanding what the value
1024 means, read the appendix on calibration and/or the
1025 source code for more information. To change a
1026 TeleDongle’s calibration, you must reprogram the unit
1031 <h4 id="_telemetryrdfaprs_enable">3.13.3. Telemetry/RDF/APRS Enable</h4>
1032 <div class="paragraph">
1033 <p>Enables the radio for transmission during
1034 flight. When disabled, the radio will not
1035 transmit anything during flight at all.</p>
1039 <h4 id="_limit_transmit_to_10mw">3.13.4. Limit transmit to 10mW</h4>
1040 <div class="paragraph">
1041 <p>Reduces transmit power to no more than 10mW. This is
1042 useful when operating under some UK radio regulations.</p>
1046 <h4 id="_telemetry_baud_rate">3.13.5. Telemetry baud rate</h4>
1047 <div class="paragraph">
1048 <p>This sets the modulation bit rate for data
1049 transmission for both telemetry and packet
1050 link mode. Lower bit rates will increase range
1051 while reducing the amount of data that can be
1052 sent and increasing battery consumption. All
1053 telemetry is done using a rate 1/2 constraint
1054 4 convolution code, so the actual data
1055 transmission rate is 1/2 of the modulation bit
1056 rate specified here.</p>
1060 <h4 id="_aprs_interval">3.13.6. APRS Interval</h4>
1061 <div class="paragraph">
1062 <p>How often to transmit GPS information via APRS
1063 (in seconds). When set to zero, APRS
1064 transmission is disabled.
1065 Note that a single APRS packet
1066 takes nearly a full second to transmit, so
1067 enabling this option will prevent sending any
1068 other telemetry during that time.</p>
1072 <h4 id="_aprs_ssid">3.13.7. APRS SSID</h4>
1073 <div class="paragraph">
1074 <p>Which SSID to report in APRS packets. By
1075 default, this is set to the last digit of the
1076 serial number, but can be configured to any
1077 value from 0 to 9.</p>
1081 <h4 id="_aprs_format">3.13.8. APRS Format</h4>
1082 <div class="paragraph">
1083 <p>Whether to send APRS data in Compressed or
1084 Uncompressed format. Compressed format is
1085 smaller and more precise. Uncompressed
1086 format is older, but may work better with your
1087 device. The Kenwood TH-D72 only displays
1088 altitude information with Uncompressed
1089 format, while the Yaesu FT1D only displays
1090 altitude with Compressed format. Test before
1091 you fly to see which to use.</p>
1095 <h4 id="_aprs_offset">3.13.9. APRS Offset</h4>
1096 <div class="paragraph">
1097 <p>The delay from the top of the minute before sending
1098 the first APRS packet of the minute. Coordinating
1099 values for this parameter between multiple devices can
1100 allow a single receiver to reliably receive APRS
1101 packets from multiple devices. Note that this offset only
1102 takes effect while the GPS signal is locked so that the
1103 transmitting device knows the current time.</p>
1107 <h4 id="_callsign_2">3.13.10. Callsign</h4>
1108 <div class="paragraph">
1109 <p>This sets the call sign included in each
1110 telemetry packet. Set this as needed to
1111 conform to your local radio regulations.</p>
1115 <h4 id="_logging_trigger_motion">3.13.11. Logging Trigger Motion</h4>
1116 <div class="paragraph">
1117 <p>This sets the amount of motion that TeleGPS
1118 needs to see before logging the new
1119 position. Motions smaller than this are
1120 skipped, which saves storage space.</p>
1124 <h4 id="_position_reporting_interval">3.13.12. Position Reporting Interval</h4>
1125 <div class="paragraph">
1126 <p>The interval between TeleGPS position reports,
1127 both over the air and in the log. Increase
1128 this to reduce the frequency of radio
1129 transmissions and the length of time available
1135 <h3 id="_flash_device">3.14. Flash Device</h3>
1136 <div class="paragraph">
1137 <p>This reprograms TeleGPS devices with new
1138 firmware. Please read the directions for flashing
1139 devices in <a href="#_updating_device_firmware">Updating Device Firmware</a>.</p>
1145 <h2 id="_telegps_system_operation">Appendix A: TeleGPS System Operation</h2>
1146 <div class="sectionbody">
1148 <h3 id="_gfsk_telemetry">A.1. GFSK Telemetry</h3>
1149 <div class="paragraph">
1150 <p>TeleGPS’s native telemetry system doesn’t use a
1151 'normal packet radio' mode like APRS because it’s not
1152 very efficient. The GFSK modulation we use is FSK
1153 with the base-band pulses passed through a Gaussian
1154 filter before they go into the modulator to limit the
1155 transmitted bandwidth. When combined with forward
1156 error correction and interleaving, this allows us to
1157 have a very robust 19.2 kilobit data link with only
1158 10-40 milliwatts of transmit power, a whip antenna in
1159 the rocket, and a hand-held Yagi on the ground. We’ve
1160 had flights to above 21k feet AGL with great
1161 reception, and calculations suggest we should be good
1162 to well over 40k feet AGL with a 5-element yagi on the
1163 ground with our 10mW units and over 100k feet AGL with
1164 the 40mW devices.</p>
1168 <h3 id="_aprs">A.2. APRS</h3>
1169 <div class="paragraph">
1170 <p>TeleGPS can send APRS if desired, and the
1171 interval between APRS packets can be configured. As
1172 each APRS packet takes a full second to transmit, we
1173 recommend an interval of at least 5 seconds to avoid
1174 consuming too much battery power or radio channel
1175 bandwidth. You can configure the time within each
1176 minute that APRS transmits by changing the APRS offset
1177 value. When the GPS signal is locked and knows the
1178 current time, the APRS offset selects the time with
1179 each minute for the first APRS transmission;
1180 subsequent transmissions occur each APRS interval
1181 seconds thereafter. You can configure the APRS
1182 interval and APRS offset using TeleGPS; that
1183 process is described in <a href="#_configure_device">Configure Device</a>.</p>
1185 <div class="paragraph">
1186 <p>AltOS supports both compressed and uncompressed APRS
1187 position report data formats. The compressed format
1188 provides for higher position precision and shorter
1189 packets than the uncompressed APRS format. We’ve found
1190 some older APRS receivers that do not handle the
1191 compressed format. The Kenwood TH-72A requires the use
1192 of uncompressed format to display altitude information
1193 correctly. The Yaesu FT1D requires the use of
1194 compressed format to display altitude information.</p>
1196 <div class="paragraph">
1197 <p>APRS packets include an SSID (Secondary Station Identifier)
1198 field that allows one operator to have multiple
1199 transmitters. AltOS allows you to set this to a single digit
1200 from 0 to 9, allowing you to fly multiple transmitters at the
1201 same time while keeping the identify of each one separate in
1202 the receiver. By default, the SSID is set to the last digit of
1203 the device serial number.</p>
1205 <div class="paragraph">
1206 <p>The APRS packet format includes a comment field that
1207 can have arbitrary text in it. AltOS uses this to send
1208 status information as shown in the following table.</p>
1210 <table class="tableblock frame-all grid-all stretch">
1211 <caption class="title">Table 1. Altus Metrum APRS Comments</caption>
1213 <col style="width: 20%;">
1214 <col style="width: 20%;">
1215 <col style="width: 60%;">
1219 <th class="tableblock halign-left valign-top">Field</th>
1220 <th class="tableblock halign-left valign-top">Example</th>
1221 <th class="tableblock halign-left valign-top">Description</th>
1226 <td class="tableblock halign-left valign-top"><p class="tableblock">1</p></td>
1227 <td class="tableblock halign-left valign-top"><p class="tableblock">L</p></td>
1228 <td class="tableblock halign-left valign-top"><p class="tableblock">GPS Status U for unlocked, L for locked</p></td>
1231 <td class="tableblock halign-left valign-top"><p class="tableblock">2</p></td>
1232 <td class="tableblock halign-left valign-top"><p class="tableblock">6</p></td>
1233 <td class="tableblock halign-left valign-top"><p class="tableblock">Number of Satellites in View</p></td>
1236 <td class="tableblock halign-left valign-top"><p class="tableblock">3</p></td>
1237 <td class="tableblock halign-left valign-top"><p class="tableblock">B4.0</p></td>
1238 <td class="tableblock halign-left valign-top"><p class="tableblock">Altimeter Battery Voltage</p></td>
1241 <td class="tableblock halign-left valign-top"><p class="tableblock">4</p></td>
1242 <td class="tableblock halign-left valign-top"><p class="tableblock">1286</p></td>
1243 <td class="tableblock halign-left valign-top"><p class="tableblock">Device Serial Number</p></td>
1247 <div class="paragraph">
1248 <p>Here’s an example of an APRS comment showing GPS lock with 6
1249 satellites in view and a primary battery at 4.0V from device 1876.</p>
1251 <div class="literalblock">
1252 <div class="content">
1253 <pre>L6 B4.0 1876</pre>
1256 <div class="paragraph">
1257 <p>Make sure your primary battery is above 3.8V
1258 and GPS is locked with at least 5 or 6 satellites in
1259 view before flying. If GPS is switching between L and
1260 U regularly, then it doesn’t have a good lock and you
1261 should wait until it becomes stable.</p>
1263 <div class="paragraph">
1264 <p>If the GPS receiver loses lock, the APRS data
1265 transmitted will contain the last position for which
1266 GPS lock was available. You can tell that this has
1267 happened by noticing that the GPS status character
1268 switches from 'L' to 'U'. Before GPS has locked, APRS
1269 will transmit zero for latitude, longitude and
1274 <h3 id="_configurable_parameters">A.3. Configurable Parameters</h3>
1275 <div class="paragraph">
1276 <p>Configuring TeleGPS is very simple; the few configurable
1277 parameters can all be set using the TeleGPS application over
1278 USB. Check out <a href="#_configure_device">Configure Device</a>.</p>
1284 <h2 id="_handling_precautions">Appendix B: Handling Precautions</h2>
1285 <div class="sectionbody">
1286 <div class="paragraph">
1287 <p>All Altus Metrum products are sophisticated electronic devices.
1288 When handled gently and properly installed in an air-frame, they
1289 will deliver impressive results. However, as with all electronic
1290 devices, there are some precautions you must take.</p>
1292 <div class="admonitionblock warning">
1296 <div class="title">Warning</div>
1298 <td class="content">
1299 The Lithium Polymer rechargeable batteries have an
1300 extraordinary power density. This is great because we can fly with
1301 much less battery mass than if we used alkaline batteries or previous
1302 generation rechargeable batteries…​ but if they are punctured
1303 or their leads are allowed to short, they can and will release their
1304 energy very rapidly!
1305 Thus we recommend that you take some care when handling our batteries
1306 and consider giving them some extra protection in your air-frame. We
1307 often wrap them in suitable scraps of closed-cell packing foam before
1308 strapping them down, for example.
1313 <div class="paragraph">
1314 <p>The barometric sensors used on all of our flight computers are
1315 sensitive to sunlight. In normal mounting situations, the baro sensor
1316 and all of the other surface mount components
1317 are “down” towards whatever the underlying mounting surface is, so
1318 this is not normally a problem. Please consider this when designing an
1319 installation in an air-frame with a see-through plastic payload bay. It
1320 is particularly important to
1321 consider this with TeleMini v1.0, both because the baro sensor is on the
1322 “top” of the board, and because many model rockets with payload bays
1323 use clear plastic for the payload bay! Replacing these with an opaque
1324 cardboard tube, painting them, or wrapping them with a layer of masking
1325 tape are all reasonable approaches to keep the sensor out of direct
1328 <div class="paragraph">
1329 <p>The barometric sensor sampling port must be able to “breathe”,
1330 both by not being covered by foam or tape or other materials that might
1331 directly block the hole on the top of the sensor, and also by having a
1332 suitable static vent to outside air.</p>
1334 <div class="paragraph">
1335 <p>As with all other rocketry electronics, Altus Metrum altimeters must
1336 be protected from exposure to corrosive motor exhaust and ejection
1342 <h2 id="_technical_information">Appendix C: Technical Information</h2>
1343 <div class="sectionbody">
1345 <h3 id="_gps_receiver">C.1. GPS Receiver</h3>
1346 <div class="paragraph">
1347 <p>TeleGPS uses the u-Blox Max-7Q GPS receiver.</p>
1351 <h3 id="_70cm_transmitter">C.2. 70cm Transmitter</h3>
1352 <div class="paragraph">
1353 <p>TeleGPS uses a TI CC115L transmitter. This radio
1354 produces 10mW of RF output.</p>
1358 <h3 id="_micro_controller">C.3. Micro-controller</h3>
1359 <div class="paragraph">
1360 <p>TeleGPS uses an NXP LPC11U14 micro-controller. This
1361 tiny CPU contains 32kB of flash for the application
1362 and 4kB of RAM for temporary data storage.</p>
1366 <h3 id="_lithium_polymer_battery">C.4. Lithium Polymer Battery</h3>
1367 <div class="paragraph">
1368 <p>Shipping restrictions may prevent us from including a
1369 battery battery with TeleGPS.</p>
1373 <h3 id="_mechanical_considerations">C.5. Mechanical Considerations</h3>
1374 <div class="paragraph">
1375 <p>TeleGPS is designed to be rugged enough for typical
1376 rocketry applications. The 4 mounting holes on the
1377 board are sized for use with 4-40 or M3 screws.</p>
1381 <h3 id="_on_board_data_storage">C.6. On-board data storage</h3>
1382 <div class="paragraph">
1383 <p>TeleGPS has 2MB of non-volatile storage, separate from
1384 the code storage memory. The TeleGPS firmware uses
1385 this to log information during flight.</p>
1391 <h2 id="_updating_device_firmware">Appendix D: Updating Device Firmware</h2>
1392 <div class="sectionbody">
1393 <div class="paragraph">
1394 <p>TeleGPS is programmed directly over its USB connectors.</p>
1396 <div class="paragraph">
1397 <p>You may wish to begin by ensuring you have current firmware images.
1398 These are distributed as part of the TeleGPS software bundle that
1399 also includes the TeleGPS ground station program. Newer ground
1400 station versions typically work fine with older firmware versions,
1401 so you don’t need to update your devices just to try out new
1402 software features. You can always download the most recent
1403 version from <a href="http://www.altusmetrum.org/AltOS/" class="bare">http://www.altusmetrum.org/AltOS/</a></p>
1406 <h3 id="_updating_telegps_firmware">D.1. Updating TeleGPS Firmware</h3>
1407 <div class="olist arabic">
1410 <p>Attach a battery and power switch to the target
1411 device. Power up the device.</p>
1414 <p>Using a Micro USB cable, connect the target device to
1415 your computer’s USB socket.</p>
1418 <p>Run TeleGPS, and select 'Flash Device' from the
1422 <p>Select the target device in the Device Selection
1426 <p>Select the image you want to flash to the device,
1427 which should have a name in the form
1428 <product>-v<product-version>-<software-version>.ihx,
1429 such as TeleGPS-v1.0-1.4.0.ihx.</p>
1432 <p>Make sure the configuration parameters are reasonable
1433 looking. If the serial number and/or RF configuration
1434 values aren’t right, you’ll need to change them.</p>
1437 <p>Hit the 'OK' button and the software should proceed
1438 to flash the device with new firmware, showing a
1442 <p>Verify that the device is working by using the
1443 'Configure Device item to check over the
1452 <h2 id="_release_notes">Appendix E: Release Notes</h2>
1453 <div class="sectionbody">
1455 <h3 id="_release_notes_for_version_1_9_14">E.1. Release Notes for Version 1.9.14</h3>
1456 <div class="paragraph">
1457 <p>Version 1.9.14</p>
1460 <h4 id="_altos">E.1.1. AltOS</h4>
1464 <p>Fix 1.9.13 regression in TeleLCO startup sequence that
1465 detects available TeleFire units.</p>
1469 <div style="page-break-after: always;"></div>
1473 <h3 id="_release_notes_for_version_1_9_13">E.2. Release Notes for Version 1.9.13</h3>
1474 <div class="paragraph">
1475 <p>Version 1.9.13</p>
1478 <h4 id="_altos_2">E.2.1. AltOS</h4>
1482 <p>Add option to beep max height in feet after landing</p>
1485 <p>Fix APRS reports to be sent at the correct time and spacing.</p>
1488 <p>Fix possible barometric sensor communication failure when
1489 the CPU is busy talking to the radio at the same time. This
1490 would cause loss of telemetry and failure to track the state
1491 of the rocket during flight. This was aggrevated by the APRS
1492 reports getting sent more often than they should.</p>
1495 <p>Change EasyMotor v3 code to base logging on motor pressure
1496 rather than the accelerometer. This allows use of EasyMotor
1497 v3 in a static test stand.</p>
1503 <h4 id="_altosui">E.2.2. AltosUI</h4>
1507 <p>Add support for configuring the units used to report height
1508 after landing on the beeper.</p>
1512 <div style="page-break-after: always;"></div>
1516 <h3 id="_release_notes_for_version_1_9_12">E.3. Release Notes for Version 1.9.12</h3>
1517 <div class="paragraph">
1518 <p>Version 1.9.12</p>
1521 <h4 id="_altos_3">E.3.1. AltOS</h4>
1525 <p>Add EasyMini v3.0 and EasyMotor v3.0 support</p>
1528 <p>Fix TeleMetrum v2.0 configuration. Saving config would
1529 crash the board.</p>
1535 <h4 id="_altosui_2">E.3.2. AltosUI</h4>
1539 <p>Add EasyMotor log parsing and graphing.</p>
1543 <div style="page-break-after: always;"></div>
1547 <h3 id="_release_notes_for_version_1_9_11">E.4. Release Notes for Version 1.9.11</h3>
1548 <div class="paragraph">
1549 <p>Version 1.9.11</p>
1552 <h4 id="_altos_4">E.4.1. AltOS</h4>
1556 <p>Make Apogee Delay work again.</p>
1559 <p>Allow TX power to be limited to 10mW for compliance with
1560 some uses under UK regulations.</p>
1563 <p>Fix numerous minor issues with 16- vs 32- bit time values.</p>
1569 <h4 id="_altosui_3">E.4.2. AltosUI</h4>
1573 <p>Support M1-based Macs, follow AdoptOpenJDK to Adoptium</p>
1579 <h4 id="_altosdroid">E.4.3. AltosDroid</h4>
1583 <p>Handle Bluetooth permissions reliably.</p>
1586 <p>Fix some screen rotation bugs.</p>
1590 <div style="page-break-after: always;"></div>
1594 <h3 id="_release_notes_for_version_1_9_10">E.5. Release Notes for Version 1.9.10</h3>
1595 <div class="paragraph">
1596 <p>Version 1.9.10</p>
1598 <div class="paragraph">
1599 <p>This release contains a couple of bug fixes for ground station software.</p>
1602 <h4 id="_altosui_4">E.5.1. AltosUI</h4>
1606 <p>Rework the windows DLL build to make AltosUI run on more
1607 instances of Windows 10.</p>
1613 <h4 id="_altosdroid_2">E.5.2. AltosDroid</h4>
1617 <p>Adapt to Android security changes which prevent AltosDroid
1618 from storing flights in
1619 /storage/emulated/0/AltusMetrum. Now, flights are stored in
1620 /storage/emulated/0/media/org.altusmetrum.AltosDroid/AltusMetrum
1621 instead. Also, AltosDroid will display an error message if
1622 flight data cannot be logged.</p>
1626 <div style="page-break-after: always;"></div>
1630 <h3 id="_release_notes_for_version_1_9_9">E.6. Release Notes for Version 1.9.9</h3>
1631 <div class="paragraph">
1632 <p>Version 1.9.9</p>
1634 <div class="paragraph">
1635 <p>This release contains a critical bug fix for a problem
1636 introduced in version 1.9.8 for TeleMega and EasyMega
1637 boards. This problem occurs when using the stored
1638 configuration from 1.9.7 or earlier.</p>
1640 <div class="paragraph">
1641 <p>If you are running 1.9.8 or are upgrading from 1.9.8 on any
1642 version of TeleMega or EasyMega, you must reconfigure all pyro
1643 channels, recalibrate accelerometers, reset the APRS interval,
1644 adjust the beep tone and reset the pyro time.</p>
1647 <h4 id="_altos_5">E.6.1. AltOS</h4>
1651 <p>Fix EasyMega and TeleMega upgrade process from 1.9.7 or
1652 earlier. 1.9.8 introduced larger delay values, which
1653 required modifying the configuration in-place, and the 1.9.8
1654 version had a flaw which broke the pyro channel config and
1655 all of the config values beyond that in memory, including
1656 APRS interval, IMU accel calibation, beep tone and pyro
1660 <p>Fix TeleMega v5.0 mag sensor driver. This driver was quite
1661 broken due to developing it in the presence of the magnetic
1662 beeper on the board. Because of that beeper, the values this
1663 sensor records are not accurate. Fortunately, they are not
1664 used for controlling the flight.</p>
1670 <h4 id="_altosui_5">E.6.2. AltosUI</h4>
1674 <p>Parse TeleMega v5.0 log files. A missing check in the code
1675 meant that the TeleMega v5.0 log files would cause an error
1676 when attempting to load them. Logs saved with AltosUI
1677 1.9.8 were not affected, only the presentation of the data
1682 <div style="page-break-after: always;"></div>
1686 <h3 id="_release_notes_for_version_1_9_8">E.7. Release Notes for Version 1.9.8</h3>
1687 <div class="paragraph">
1688 <p>Version 1.9.8</p>
1691 <h4 id="_altos_6">E.7.1. AltOS</h4>
1695 <p>Add support for TeleMega v5.0</p>
1698 <p>Extend extra pyro channel times to support delay > 327 seconds</p>
1704 <h4 id="_altosui_6">E.7.2. AltosUI</h4>
1708 <p>Support ARM devices in Linux binary release</p>
1711 <p>Add support for TeleMega v5.0</p>
1717 <h4 id="_altosdroid_3">E.7.3. AltosDroid</h4>
1721 <p>Show tilt angle in pad and flight tabs</p>
1724 <p>Show altitude as well as height (useful for TeleGPS)</p>
1727 <p>Support devices without GPS receivers</p>
1733 <h4 id="_micropeak_gui">E.7.4. MicroPeak GUI</h4>
1737 <p>Show error dialog if device open fails</p>
1741 <div style="page-break-after: always;"></div>
1745 <h3 id="_release_notes_for_version_1_9_7">E.8. Release Notes for Version 1.9.7</h3>
1746 <div class="paragraph">
1747 <p>Version 1.9.7</p>
1750 <h4 id="_altos_7">E.8.1. AltOS</h4>
1754 <p>Fix TeleGPS logging so that new data are appended to an existing log correctly</p>
1760 <h4 id="_altosui_7">E.8.2. AltosUI</h4>
1764 <p>Support Mac OS X 11 (Big Sur)</p>
1767 <p>Support Monitor Idle on Easy Timer</p>
1770 <p>Fix TeleMega v4.0 and TeleMetrum v3.0 configuration in Antenna Down mode</p>
1773 <p>Show launch sites in Load Maps view</p>
1776 <p>Add IMU header names to CSV files</p>
1779 <p>Clean up TeleGPS log corruption due to firmware bugs during firmware update</p>
1785 <h4 id="_altosdroid_4">E.8.3. AltosDroid</h4>
1789 <p>Support older devices back to Android version 5.1</p>
1792 <p>Fix a number of issues that could result in app crashes</p>
1796 <div style="page-break-after: always;"></div>
1800 <h3 id="_release_notes_for_version_1_9_6">E.9. Release Notes for Version 1.9.6</h3>
1801 <div class="paragraph">
1802 <p>Version 1.9.6</p>
1805 <h4 id="_altos_8">E.9.1. AltOS</h4>
1809 <p>Fix EasyTimer bug where it might mis-detect boost (either
1810 detect it early or not at all) due to small errors in
1811 accelerometer calibration leading to large accumulated error
1815 <p>Adjust self-test of new 9-axis IMU (BMX-160) so that it
1816 doesn’t think the part has a failure when tested sitting
1821 <div style="page-break-after: always;"></div>
1825 <h3 id="_release_notes_for_version_1_9_5">E.10. Release Notes for Version 1.9.5</h3>
1826 <div class="paragraph">
1827 <p>Version 1.9.5</p>
1830 <h4 id="_altos_9">E.10.1. AltOS</h4>
1834 <p>Add Booster mode for all dual-deploy altimeters. Select
1835 "Separation & Apogee" mode in AltosUI to fire the 'main'
1836 channel at first motor burnout and the 'apogee' channel at
1840 <p>Improve reliability of stm32l firmware under heavy
1841 load. This was found using Monitor Idle on TeleMega with all
1842 flash slots full of data which would occasionally lock up.</p>
1845 <p>Fix orientation label in AltosUI for devices with
1846 radios. This makes the orientation say 'Antenna up' and
1847 'Antenna Down' for TeleMetrum and TeleMega again.</p>
1850 <p>Fix log data for pyro channels which were inhibited (often
1851 because of a tilt limit). They used to report 'fired' as
1852 soon as they were inhibited, which was misleading. Now they
1853 never report as having been fired.</p>
1856 <p>Allow Igniter Test to fire each igniter more than once.</p>
1862 <h4 id="_altosui_8">E.10.2. AltosUI</h4>
1866 <p>Improve performance of Monitor Idle mode by sending less data for each
1870 <p>Improve Mac OS X install scripts so that they work on
1871 Catalina. This involves sending the user to get Java from
1872 the AdoptOpenJDK project which provides a version that works
1873 with Java applications.</p>
1876 <p>Make larger dialogs scrollable for use on smaller screens.</p>
1879 <p>Fix troubles re-flashing EasyMega boards running older
1883 <p>Add TeleMetrum v3.0 firmware to the Windows
1884 AltosUI packages.</p>
1888 <div style="page-break-after: always;"></div>
1892 <h3 id="_release_notes_for_version_1_9_4">E.11. Release Notes for Version 1.9.4</h3>
1893 <div class="paragraph">
1894 <p>Version 1.9.4</p>
1897 <h4 id="_altos_10">E.11.1. AltOS</h4>
1901 <p>Fixed firmware for TeleDongle v3.0 and TeleBT v4.0. Version 1.9.3 bricked those
1902 devices requiring them to be opened up to get them working again.</p>
1905 <p>Fixed firmware for EasyMini v1.0. Changes in the storage
1906 code caused it to use significantly more RAM which made the
1907 interrupt stack smash into other data structures and cause
1908 the device to panic at startup time.</p>
1914 <h4 id="_altosui_9">E.11.2. AltosUI</h4>
1918 <p>Add TeleMetrum v3.0 firmware to the Linux and Mac OSX
1919 AltosUI packages.</p>
1923 <div style="page-break-after: always;"></div>
1927 <h3 id="_release_notes_for_version_1_9_3">E.12. Release Notes for Version 1.9.3</h3>
1928 <div class="paragraph">
1929 <p>Version 1.9.3</p>
1932 <h4 id="_altos_11">E.12.1. AltOS</h4>
1936 <p>Add APRS offset. Allows multiple APRS transmitters to coordinate when
1937 transmission occurs to allow them to share a frequency.</p>
1940 <p>Fix max log size. Flight computer storage is erased in 64kB chunks. Adjust max
1941 log size to be a multiple of this size.</p>
1944 <p>Check flight erasing more carefully. Handle interrupting erasing in the
1948 <p>Add EasyTimer support.</p>
1954 <h4 id="_altosui_telegps_micropeak">E.12.2. AltosUI, TeleGPS, MicroPeak</h4>
1958 <p>Add configuration support for APRS offset.</p>
1961 <p>Adjust flight log sizes to be a multiple of the flight
1962 computer erase block size.</p>
1965 <p>Report barometric pad altitude in Pad tab for TeleMini.</p>
1969 <div style="page-break-after: always;"></div>
1973 <h3 id="_release_notes_for_version_1_9_1">E.13. Release Notes for Version 1.9.1</h3>
1974 <div class="paragraph">
1975 <p>Version 1.9.1</p>
1978 <h4 id="_altos_12">E.13.1. AltOS</h4>
1982 <p>Add support for TeleMetrum v3.0</p>
1985 <p>Fix accel cal value when changing EasyMega v2.0 pad orientation</p>
1988 <p>Correct EasyMega v2.0 magnetometer data axes</p>
1991 <p>Fix EasyMega v2.0 idle monitor display of IMU data</p>
1994 <p>Report all sensor failures at power-up time.</p>
2000 <h4 id="_altosui_telegps_micropeak_2">E.13.2. AltosUI, TeleGPS, MicroPeak</h4>
2004 <p>Display error message when attempting to graph unknown format file.</p>
2007 <p>Make it possible to disable APRS once enabled.</p>
2010 <p>Display some data for point near cursor in map tab.</p>
2013 <p>Support upgrading devices from pre-1.8 firmware</p>
2016 <p>Wait for Windows to prepare new devices during firmware
2017 upgrade. This should avoid the “COMxx: open failed” message.</p>
2021 <div style="page-break-after: always;"></div>
2025 <h3 id="_release_notes_for_version_1_9">E.14. Release Notes for Version 1.9</h3>
2026 <div class="paragraph">
2030 <h4 id="_altos_13">E.14.1. AltOS</h4>
2034 <p>Add support for EasyMega v2.0</p>
2037 <p>Replace C library for ARM devices</p>
2040 <p>Remove support for 8051-based devices and SDCC compiler</p>
2046 <h4 id="_altosui_telegps_micropeak_3">E.14.2. AltosUI, TeleGPS, MicroPeak</h4>
2050 <p>Select ROM images based on product name when reflashing</p>
2053 <p>Fix TeleGPS v2 battery voltage display</p>
2057 <div style="page-break-after: always;"></div>
2061 <h3 id="_release_notes_for_version_1_8_7">E.15. Release Notes for Version 1.8.7</h3>
2062 <div class="paragraph">
2063 <p>Version 1.8.7</p>
2066 <h4 id="_altos_14">E.15.1. AltOS</h4>
2070 <p>Include TeleMega v3.0 firmware</p>
2076 <h4 id="_altosui_telegps_micropeak_4">E.15.2. AltosUI, TeleGPS, MicroPeak</h4>
2080 <p>Poll for new devices while Device dialog is displayed</p>
2083 <p>Wait for device to re-appear when flashing new firmware</p>
2086 <p>Fetch correct TeleBT v4.0 RF calibration values from web
2087 site when reflashing.</p>
2090 <p>Change gyro headings in .csv files from x/y/z to
2094 <p>Add documentation about Packet Link mode</p>
2097 <p>Add documentation about forcing TeleMini RF parameters to
2101 <p>Create a proxy server for Google Maps to re-enable map
2105 <p>Fix Java version info in all distributed jar files so that
2106 applications will run with standard Mac OS X Java.</p>
2109 <p>Replace JavaApplicationStub for Mac OS X so that
2110 applications will run with Oracle Java.</p>
2114 <div style="page-break-after: always;"></div>
2118 <h3 id="_release_notes_for_version_1_8_6">E.16. Release Notes for Version 1.8.6</h3>
2119 <div class="paragraph">
2120 <p>Version 1.8.6</p>
2123 <h4 id="_altos_15">E.16.1. AltOS</h4>
2127 <p>Use maximum of 64 previous tilt values in pyro tilt tests</p>
2130 <p>Eliminate 100m height requirement for coast detection</p>
2133 <p>Change After Motor pyro check to be >= instead of ==</p>
2136 <p>Change Time since Boost to be Time since launch.</p>
2142 <h4 id="_altosui_telegps">E.16.2. AltosUI, TeleGPS</h4>
2146 <p>Clarify pyro test phrasing</p>
2149 <p>Remove ascending/descending from pyro config UI</p>
2152 <p>Fix accel calibration in Antenna Down mode</p>
2155 <p>Add mag sensor reporting for TeleMega v3 idle monitoring.</p>
2158 <p>Fix radio parameter saving at 2400 bps telmetry rate.</p>
2164 <h4 id="_micropeak">E.16.3. MicroPeak</h4>
2168 <p>Report altimeter-recorded maximum height value</p>
2172 <div style="page-break-after: always;"></div>
2176 <h3 id="_release_notes_for_version_1_8_5">E.17. Release Notes for Version 1.8.5</h3>
2177 <div class="paragraph">
2178 <p>Version 1.8.5 includes fixes to the ground software support
2179 for TeleBT v4, along with a few other minor updates.</p>
2182 <h4 id="_altos_16">E.17.1. AltOS</h4>
2186 <p>Fix startup beeps that indicate sensor failures.</p>
2192 <h4 id="_altosui_telegps_2">E.17.2. AltosUI, TeleGPS</h4>
2196 <p>When updating device firmware, make sure selected firmware
2197 matches target device.</p>
2200 <p>Correct Bluetooth device matching when looking for TeleBT
2205 <div style="page-break-after: always;"></div>
2209 <h3 id="_release_notes_for_version_1_8_4">E.18. Release Notes for Version 1.8.4</h3>
2210 <div class="paragraph">
2211 <p>Version 1.8.4 includes support for EasyMini version 2.0</p>
2214 <h4 id="_altos_17">E.18.1. AltOS</h4>
2218 <p>Support for EasyMini version 2.0 hardware.</p>
2222 <div style="page-break-after: always;"></div>
2226 <h3 id="_release_notes_for_version_1_8_3">E.19. Release Notes for Version 1.8.3</h3>
2227 <div class="paragraph">
2228 <p>Version 1.8.3 includes support for TeleMega version 3.0 along
2229 with two important flight computer fixes. This version also
2230 changes KML export data to make Tripoli Record reporting
2231 better and some updates to graph presentation and data
2235 <h4 id="_altos_18">E.19.1. AltOS</h4>
2237 <h5 id="_altos_new_features">AltOS New Features</h5>
2241 <p>Support for TeleMega version 3.0 hardware.</p>
2247 <h5 id="_altos_bug_fixes">AltOS Bug Fixes</h5>
2251 <p>Ground testing EasyMega and TeleMega additional pyro
2252 channels could result in a sticky 'fired' status which would
2253 prevent these channels from firing on future flights.</p>
2256 <p>Corrupted flight log records could prevent future flights
2257 from capturing log data.</p>
2260 <p>Fixed saving of pyro configuration that ended with
2268 <h4 id="_altosui_and_telegps_applications">E.19.2. AltosUI and TeleGPS Applications</h4>
2270 <h5 id="_altosui_new_features">AltosUI New Features</h5>
2274 <p>Support for TeleMega version 3.0.</p>
2277 <p>Graph lines have improved appearance to make them easier to
2278 distinguish. Markers may be placed at data points to show
2279 captured recorded data values.</p>
2282 <p>Graphing offers the ability to adjust the smoothing of
2283 computed speed and acceleration data.</p>
2286 <p>The download dialog now offers to graph new flights, checks
2287 for existing files to avoid overwriting data and reports if
2288 there are checksum errors in the downloaded data.</p>
2294 <h5 id="_altosuitelegps_bug_fixes">AltosUI/TeleGPS Bug Fixes</h5>
2298 <p>Restore TeleGPS tracking behavior.</p>
2301 <p>Display flight computer call sign and serial number in
2302 Monitor Idle mode instead of ground station values.</p>
2308 <h5 id="_altosui_and_telegps_changes">AltosUI and TeleGPS Changes</h5>
2312 <p>KML export now reports both barometric and GPS altitude data
2313 to make it more useful for Tripoli record reporting.</p>
2316 <p>CSV export now includes TeleMega/EasyMega pyro voltages and
2321 <div style="page-break-after: always;"></div>
2326 <h3 id="_release_notes_for_version_1_8_2">E.20. Release Notes for Version 1.8.2</h3>
2327 <div class="paragraph">
2328 <p>Version 1.8.2 includes support for TeleGPS version 2.0 along
2329 with accelerometer recalibration support in AltosUI.</p>
2331 <div class="paragraph">
2332 <p>1.8.2 also contains a couple of minor fixes for AltosUI when
2333 analyzing saved data files.</p>
2336 <h4 id="_altos_19">E.20.1. AltOS</h4>
2337 <div class="paragraph">
2338 <p>AltOS New Features</p>
2343 <p>Support for TeleGPS version 2.0 hardware.</p>
2349 <h4 id="_altosui_and_telegps_applications_2">E.20.2. AltosUI and TeleGPS Applications</h4>
2350 <div class="paragraph">
2351 <p>AltosUI and TeleGPS New Features</p>
2356 <p>Support for TeleGPS version 2.0.</p>
2359 <p>Accelerometer re-calibration user interface.</p>
2363 <div class="paragraph">
2364 <p>AltosUI and TeleGPS Bug Fixes</p>
2369 <p>Prevent some crashes when reading older saved flight data
2370 for graphing or KML export.</p>
2374 <div style="page-break-after: always;"></div>
2378 <h3 id="_release_notes_for_version_1_8_1">E.21. Release Notes for Version 1.8.1</h3>
2379 <div class="paragraph">
2380 <p>Version 1.8.1 includes an important bug fix for Apogee Lockout
2381 operation in all flight computers. Anyone using this option
2382 must update firmware.</p>
2384 <div class="paragraph">
2385 <p>This release also contains a change in how flight computers
2386 with accelerometers deal with speeds around and above Mach
2387 1. In previous versions, the flight computer would completely
2388 disregard the barometric sensor above 330m/s (around Mach
2389 1). Now, the data from the barometric sensor is reduced in
2390 effect without ever going away entirely. This prevents early
2391 drogue deployment for flights which spend considerable time
2394 <div class="paragraph">
2395 <p>1.8.1 also contains a couple of minor fixes for AltosUI when
2396 analyzing saved data files.</p>
2399 <h4 id="_altos_20">E.21.1. AltOS</h4>
2400 <div class="paragraph">
2401 <p>AltOS Bug Fixes</p>
2406 <p>Handle time value wrapping in Apogee Lockout
2407 correctly. Without this, apogee lockout would sometimes
2408 prevent any drogue charge from firing.</p>
2411 <p>Change Kalman filter on flight computers with accelerometer
2412 to continue using the barometric sensor even at high speeds
2413 to avoid unintentional drogue deployment during
2420 <h4 id="_altosui_and_telegps_applications_3">E.21.2. AltosUI and TeleGPS Applications</h4>
2421 <div class="paragraph">
2422 <p>AltosUI New Features</p>
2427 <p>Add new 'Huge' font size to make text even bigger on high
2428 resolution monitors.</p>
2432 <div class="paragraph">
2433 <p>AltosUI Bug Fixes</p>
2438 <p>Prevent some crashes when reading older saved flight data
2439 for graphing or KML export.</p>
2442 <p>Load frequency preference at startup. The loading code was
2443 broken, so you’d see only the default frequencies.</p>
2447 <div style="page-break-after: always;"></div>
2451 <h3 id="_release_notes_for_version_1_8">E.22. Release Notes for Version 1.8</h3>
2452 <div class="paragraph">
2453 <p>Version 1.8 includes support for our new TeleBT v4.0 ground
2454 station, updates for data analysis in our ground station
2455 software and bug fixes in in the flight software for all our
2456 boards and ground station interfaces.</p>
2459 <h4 id="_altos_21">E.22.1. AltOS</h4>
2460 <div class="paragraph">
2461 <p>AltOS New Features</p>
2466 <p>Add support for TeleBT v4.0 boards.</p>
2472 <h4 id="_altosui_and_telegps_applications_4">E.22.2. AltosUI and TeleGPS Applications</h4>
2473 <div class="paragraph">
2474 <p>AltosUI New Features</p>
2479 <p>Add support for TeleBT v4.0 hardware</p>
2482 <p>Rewrite graphing and export functions. This code now handles
2483 each data series separately so that graphs are drawn
2484 correctly. Smoothing now uses a filter that looks both
2485 forward and backwards in time to make computed speed and
2486 acceleration data more accurate.</p>
2490 <div class="paragraph">
2491 <p>AltosUI Bug Fixes</p>
2496 <p>Correct axis labeling of magnetic sensor in TeleMega and
2497 EasyMega. The Y and Z axes were flipped.</p>
2501 <div style="page-break-after: always;"></div>
2505 <h3 id="_release_notes_for_version_1_7">E.23. Release Notes for Version 1.7</h3>
2506 <div class="paragraph">
2507 <p>Version 1.7 includes support for our new TeleMini v3.0
2508 flight computer and bug fixes in in the flight software for all our boards
2509 and ground station interfaces.</p>
2512 <h4 id="_altos_22">E.23.1. AltOS</h4>
2513 <div class="paragraph">
2514 <p>AltOS New Features</p>
2519 <p>Add support for TeleMini v3.0 boards.</p>
2523 <div class="paragraph">
2529 <p>Fix interrupt priorities on STM32L processors. Run timer
2530 interrupt at lowest priority so that device interrupts get
2537 <h4 id="_altosui_and_telegps_applications_5">E.23.2. AltosUI and TeleGPS Applications</h4>
2538 <div class="paragraph">
2539 <p>AltosUI New Features</p>
2544 <p>Add support for TeleMini v3.0 hardware</p>
2548 <div style="page-break-after: always;"></div>
2552 <h3 id="_release_notes_for_version_1_6_8">E.24. Release Notes for Version 1.6.8</h3>
2553 <div class="paragraph">
2554 <p>Version 1.6.8 fixes a TeleMega and TeleMetrum v2.0 bug where
2555 the device could stop logging data and transmitting
2556 telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum
2557 v2.0 users should update their flight firmware.</p>
2560 <h4 id="_altos_23">E.24.1. AltOS</h4>
2561 <div class="paragraph">
2567 <p>Fix STM32L DMA driver to work around STM32L SoC DMA priority
2568 issue t lock-up in the logging or radio code, either of
2569 which could stop data logging and telemetry.</p>
2572 <p>Avoid having TeleBT battery status values smash telemetry
2573 packet data by holding a lock during both operations.</p>
2576 <p>Don’t start reporting 'flight 0' when the log fills in
2581 <div class="paragraph">
2582 <p>AltOS changes:</p>
2587 <p>Flash LEDS on all products briefly during power up so that
2588 they can be tested during production.</p>
2594 <h4 id="_altosui_telegps_and_altosdroid_applications">E.24.2. AltosUI, TeleGPS and AltosDroid Applications</h4>
2595 <div class="paragraph">
2596 <p>AltosUI fixes:</p>
2601 <p>Re-enable go/no-go entries after they’ve been disabled due
2602 to lack of data. If telemetry information is delayed when
2603 the Ui starts up, sometimes important fields would get
2604 disabled to never re-appear.</p>
2607 <p>Deal with ground station failure better during Configure
2608 Ground Station operation by cleaning up pending operations.</p>
2612 <div style="page-break-after: always;"></div>
2616 <h3 id="_release_notes_for_version_1_6_5">E.25. Release Notes for Version 1.6.5</h3>
2617 <div class="paragraph">
2618 <p>Version 1.6.5 fixes a TeleMega and TeleMetrum v2.0 bug where
2619 the device would often stop logging data and transmitting
2620 telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum
2621 v2.0 users should update their flight firmware.</p>
2624 <h4 id="_altos_24">E.25.1. AltOS</h4>
2625 <div class="paragraph">
2631 <p>Fix STM32L SPI driver to prevent lock-up in the logging or
2632 radio code, either of which could stop data logging and
2633 telemetry. Found and characterized by Chuck Haskin, who also
2634 tested the new firmware before release.</p>
2640 <h4 id="_altosui_telegps_and_altosdroid_applications_2">E.25.2. AltosUI, TeleGPS and AltosDroid Applications</h4>
2641 <div class="paragraph">
2642 <p>AltosUI fixes:</p>
2647 <p>Deliver firmward for TeleMega v2.0 and TeleBT v3.0 with
2648 Windows package.</p>
2652 <div style="page-break-after: always;"></div>
2656 <h3 id="_release_notes_for_version_1_6_4">E.26. Release Notes for Version 1.6.4</h3>
2657 <div class="paragraph">
2658 <p>Version 1.6.4 fixes a bluetooth communication problem with
2659 TeleBT v1.0 devices, along with some altosui and altosdroid
2660 minor nits. It also now ships firmware for some newer devices.</p>
2663 <h4 id="_altos_25">E.26.1. AltOS</h4>
2664 <div class="paragraph">
2670 <p>Fix hardware flow control on TeleBT v1.0. Hardware RTS/CTS
2671 doesn’t seem to work, switch from using the hardware to
2672 driving these pins with software.</p>
2675 <p>Fix ARM USB drivers to deal with OS restarts. Needed to
2676 reset all USB-related state when the USB bus is reset. These
2677 fixes affect all STM32L, STM32F0 and LPC11U14 based devices.</p>
2683 <h4 id="_altosui_telegps_and_altosdroid_applications_3">E.26.2. AltosUI, TeleGPS and AltosDroid Applications</h4>
2684 <div class="paragraph">
2685 <p>AltosUI, TeleGPS and AltosDroid New Features:</p>
2690 <p>Automatically switch from meters or feet to kilometers or
2691 miles for distance units.</p>
2694 <p>Add Monitor Idle mode to TeleGPS application.</p>
2698 <div class="paragraph">
2699 <p>AltosUI, TeleGPS and AltosDroid Fixes:</p>
2704 <p>Abort map preloading when the preload map dialog is closed.</p>
2707 <p>In AltosDroid, Don’t reconnect to last device if the user
2708 had disconnected it the last time the application was
2715 <h4 id="_documentation">E.26.3. Documentation</h4>
2719 <p>Mention TeleMega v2.0 in hardware specs table.</p>
2722 <p>Document TeleGPS RF output in telegps manual.</p>
2729 <h3 id="_release_notes_for_version_1_6_3">E.27. Release Notes for Version 1.6.3</h3>
2730 <div class="paragraph">
2731 <p>Version 1.6.3 adds idle mode to AltosDroid and has bug fixes
2732 for our host software on desktops, laptops an android devices
2733 along with BlueTooth support for Windows.</p>
2736 <h4 id="_altos_26">E.27.1. AltOS</h4>
2737 <div class="paragraph">
2743 <p>Fix hardware flow control on TeleBT v3.0. RTS/CTS is
2744 wired backwards on this board, switch from using the
2745 hardware to driving these pins with software.</p>
2751 <h4 id="_altosui_and_telegps_applications_6">E.27.2. AltosUI and TeleGPS Applications</h4>
2752 <div class="paragraph">
2753 <p>AltosUI and TeleGPS New Features:</p>
2758 <p>Add BlueTooth support for Windows operating system. This
2759 supports connections to TeleBT over BlueTooth rather than
2764 <div class="paragraph">
2765 <p>AltosUI and TeleGPS Fixes:</p>
2770 <p>Change Java detection and install on Windows. Detection is
2771 now done by looking for the 'javaw.exe' program, and
2772 installation by opening a browser on the java.com web site.</p>
2775 <p>Delay polling while the Fire Igniters is visible to allow
2776 for TeleMega to report back complete status over the radio.</p>
2779 <p>Disallow changing RF calibration numbers in the
2780 configuration UI. There’s no good reason to change this from
2781 the field, and recovering is really hard if you haven’t
2782 written down the right number.</p>
2785 <p>Fix USB device discovery on Mac OS X El Capitan. This makes
2786 the connected Altus Metrum USB devices appear again.</p>
2789 <p>Fix acceleration data presented in MonitorIdle mode for
2790 TeleMetrum v2.0 flight computers.</p>
2796 <h4 id="_altosdroid_5">E.27.3. AltosDroid</h4>
2797 <div class="paragraph">
2798 <p>AltosDroid new features:</p>
2803 <p>Monitor Idle mode. Check state of flight computer while in
2804 idle mode over the radio link</p>
2807 <p>Fire Igniters. Remotely fire ignires for recovery system
2811 <p>Remote reboot. Cause the flight computer to reboot over the
2812 radio link. This provides a method for switching the flight
2813 computer from idle to flight mode without needing to reach
2814 the power switch.</p>
2817 <p>Configurable frequency menu. Change the set of available
2818 frequencies and provide more descriptive names.</p>
2822 <div class="paragraph">
2823 <p>AltosDroid bug fixes:</p>
2828 <p>Don’t set target location if GPS hasn’t locked yet.</p>
2831 <p>Fix saving target states so they can be reloaded when the
2832 application restarts. When the application is shut down and
2833 restarted, all previous target state information will be
2834 restored (including GPS position if available).</p>
2837 <p>Fix crash on some Android devices for offline maps when
2838 changing the map scale or location.</p>
2841 <p>Don’t require USB OTG support. This kept the latest
2842 AltosDroid from being offered on devices without USB device
2843 support, although it can work without that just fine using
2847 <p>Don’t require bluetooth to be enabled. This allows the
2848 application to operate with USB devices or just show old
2849 data without turning on the bluetooth radio.</p>
2852 <p>Recover old tracker positions when restarting
2853 application. This finally allows you to safely stop and
2854 restart the application without losing the last known
2855 location of any tracker.</p>
2861 <h4 id="_documentation_2">E.27.4. Documentation</h4>
2865 <p>Document TeleMega and EasyMega additional pyro channel
2866 continuity audio alert pattern.</p>
2870 <div style="page-break-after: always;"></div>
2874 <h3 id="_release_notes_for_version_1_6_2">E.28. Release Notes for Version 1.6.2</h3>
2875 <div class="paragraph">
2876 <p>Version 1.6.2 includes support for our updated TeleMega v2.0
2877 product and bug fixes in in the flight software for all our boards
2878 and ground station interfaces.</p>
2881 <h4 id="_altos_27">E.28.1. AltOS</h4>
2882 <div class="paragraph">
2883 <p>AltOS New Features:</p>
2888 <p>Add support for TeleMega v2.0 boards.</p>
2891 <p>Add PWM servo driver. There’s no higher level code using
2892 this yet, but the driver allows testing of the TeleMega v2.0
2893 servo output connector.</p>
2897 <div class="paragraph">
2903 <p>Slow down telemetry packets to allow receiver to keep
2910 <h4 id="_altosui_and_telegps_applications_7">E.28.2. AltosUI and TeleGPS Applications</h4>
2911 <div class="paragraph">
2912 <p>AltosUI and TeleGPS Fixes:</p>
2917 <p>Fix post-flight orientation computation when processing
2918 TeleMega and EasyMega eeprom data files.</p>
2921 <p>Capture complete eeprom data even when there are invalid
2922 entries in the data. This keeps reading eeprom contents and
2923 writing the associated .eeprom file when an error is detected.</p>
2929 <h4 id="_documentation_3">E.28.3. Documentation</h4>
2930 <div class="paragraph">
2931 <p>We spent a bunch of time trying to improve our documentation</p>
2936 <p>HTML versions now have a table of contents on the left side.</p>
2939 <p>EasyMini now has its own shorter manual.</p>
2942 <p>Provide links between sections in each document.</p>
2945 <p>Lots of minor rewriting and restructuring to avoid
2946 duplication of information</p>
2950 <div style="page-break-after: always;"></div>
2954 <h3 id="_release_notes_for_version_1_6_1">E.29. Release Notes for Version 1.6.1</h3>
2955 <div class="paragraph">
2956 <p>Version 1.6.1 includes support for our updated TeleBT v3.0
2957 product and bug fixes in in the flight software for all our boards
2958 and ground station interfaces.</p>
2961 <h4 id="_altos_28">E.29.1. AltOS</h4>
2962 <div class="paragraph">
2963 <p>AltOS New Features:</p>
2968 <p>Add support for TeleBT v3.0 boards.</p>
2971 <p>Add support for uncompressed APRS data, providing support
2972 for older APRS receivers. Uncompressed APRS data is less
2973 precise, takes more bandwidth and doesn’t have integrated
2978 <div class="paragraph">
2984 <p>Make TeleDongle and TeleBT more tolerant of data rate
2985 variations from transmitting devices.</p>
2991 <h4 id="_altosui_and_telegps_applications_8">E.29.2. AltosUI and TeleGPS Applications</h4>
2992 <div class="paragraph">
2993 <p>AltosUI and TeleGPS New Features:</p>
2998 <p>Add map to Monitor Idle display. It’s nice to be able to
2999 verify that maps are working, instead of needing to use
3004 <div class="paragraph">
3005 <p>AltosUI and TeleGPS Fixes:</p>
3010 <p>Fix frequency configuration to round values instead of
3011 truncate them, avoiding a common 1kHz error in the setting.</p>
3014 <p>Turn the Windows stub into a more useful program that can
3015 launch the application with parameters so that file manager
3016 icons work more reliably.</p>
3019 <p>Force KML export to use a C locale so that numbers are
3020 formatted with '.' instead of ',' for a decimal separator in
3024 <p>Preload map tiles based on distance rather than number of
3025 tiles; this means you get the same resolution covering the
3026 entire area, rather than having high resolution near the
3027 center and low resolution further away.</p>
3030 <p>Allow configuration of frequency and callsign in Monitor
3034 <p>Fix layout weirdness when resizing windows on
3035 Windows. Windows shouldn’t have giant blank spaces around
3036 the useful content anymore.</p>
3039 <p>Fix layout weirdness when resizing windows on
3040 Windows. Windows shouldn’t have giant blank spaces around
3041 the useful content anymore.</p>
3044 <p>Use a longer filter for descent speed values. This should
3045 provide something more useful on the display, although it
3046 will take longer to respond to changes now.</p>
3049 <p>Make Replay Flight run in realtime again. It had been set to
3050 run at 10x speed by mistake.</p>
3056 <h4 id="_altosdroid_6">E.29.3. AltosDroid</h4>
3057 <div class="paragraph">
3058 <p>AltosDroid New Features:</p>
3063 <p>Add offline map support using mapping code from AltosUI.</p>
3066 <p>Support TeleDongle (and TeleBT via USB) on devices
3067 supporting USB On-The-Go.</p>
3070 <p>Display additional TeleMega pyro channel status in Pad tab.</p>
3073 <p>Switch between metric and imperial units.</p>
3076 <p>Monitor TeleBT battery voltage.</p>
3079 <p>Track multiple devices at the same time, selecting between
3080 them with a menu or using the map.</p>
3083 <p>Add hybrid, satellite and terrain map types.</p>
3087 <div class="paragraph">
3088 <p>AltosDroid Fixes:</p>
3093 <p>Use standard Android display conventions so that a menu
3094 button is available in the application title bar.</p>
3097 <p>Adjust layout to work on large and small screens; shrinking
3098 the go/no-go lights in smaller environments to try and make
3099 everything visible.</p>
3102 <p>Make voice announcements depend on current tab.</p>
3105 <p>Compute adjustment to current travel direction while in
3106 motion towards rocket.</p>
3110 <div style="page-break-after: always;"></div>
3114 <h3 id="_release_notes_for_version_1_6">E.30. Release Notes for Version 1.6</h3>
3115 <div class="paragraph">
3116 <p>Version 1.6 includes support for our updated TeleDongle v3.0
3117 product and bug fixes in in the flight software for all our boards
3118 and ground station interfaces.</p>
3121 <h4 id="_altos_29">E.30.1. AltOS</h4>
3122 <div class="paragraph">
3123 <p>AltOS New Features</p>
3128 <p>Add support for TeleDongle v3.0 boards.</p>
3132 <div class="paragraph">
3138 <p>Don’t beep out the continuity twice by accident in idle mode.
3139 If the battery voltage report takes longer than the initialiation
3140 sequence, the igniter continuity would get reported twice.</p>
3143 <p>Record all 32 bits of gyro calibration data in TeleMega and
3144 EasyMega log files. This fixes computation of the gyro rates
3148 <p>Change TeleDongle LED usage. Green LED flashes when valid
3149 packet is received. Red LED flashes when invalid packet is
3153 <p>Replace LPC11U14 SPI driver with non-interrupt version. The
3154 interrupt code would occasionally wedge on long transfers
3155 if interrupts were blocked for too long. This affects all
3156 released TeleGPS products; if you have a TeleGPS device,
3157 you’ll want to reflash the firmware.</p>
3163 <h4 id="_altosui_and_telegps_applications_9">E.30.2. AltosUI and TeleGPS Applications</h4>
3164 <div class="paragraph">
3165 <p>AltosUI and TeleGPS New Features</p>
3170 <p>Compute tilt angle from TeleMega and EasyMega log
3171 files. This duplicates the quaternion-based angle tracking
3172 code from the flight firmware inside the ground station
3173 software so that post-flight analysis can include evaluation
3174 of the tilt angle.</p>
3177 <p>Shows the tool button window when starting with a data file
3178 specified. This means that opening a data file from the file
3179 manager will now bring up the main window to let you operate
3180 the whole application.</p>
3184 <div class="paragraph">
3185 <p>AltosUI Fixes</p>
3190 <p>Show the 'Connecting' dialog when using Monitor Idle. Lets
3191 you cancel the Monitor Idle startup when connecting over the
3195 <p>Make 'Monitor Idle' work for TeleGPS devices when connected
3196 over USB. It’s nice for testing without needing to broadcast
3200 <p>Use different Windows API to discover USB devices. This
3201 works better on my Windows 7 box, and will be used if the
3202 older API fails to provide the necessary information.</p>
3205 <p>Look in more places in the registry to try and identify the
3206 installed Java version on Windows. If you install the
3207 default 32-bit version of Windows on a 64-bit OS, the Java
3208 registry information is hiding \SOFTWARE\Wow6432Node for
3212 <p>Fix file association on Windows by searching for the
3213 javaw.exe program instead of assuming it is in
3214 %SYSTEMROOT%. This makes double-clicking on Altus Metrum
3215 data files in the file manager work correctly.</p>
3218 <p>When replaying a file, put 'done' in the Age field when we
3219 reach the end of the file, instead of continuing to count forever.</p>
3222 <p>In the Scan Channels code, wait for five seconds if we see
3223 any packet. This is needed because AltOS now sends the
3224 callsign, serial number and flight number only once every
3225 five seconds these days.</p>
3228 <p>In the Scan Channels code, reset pending flight state
3229 information each time we change channels. This avoids having
3230 flight computers appear on multiple frequencies by accident.</p>
3234 <div style="page-break-after: always;"></div>
3238 <h3 id="_release_notes_for_version_1_5">E.31. Release Notes for Version 1.5</h3>
3239 <div class="paragraph">
3240 <p>Version 1.5 is a major release. It includes support for our new
3241 EasyMega product, new features and bug fixes in in the flight
3242 software for all our boards and the AltosUI ground station</p>
3245 <h4 id="_altos_30">E.31.1. AltOS</h4>
3246 <div class="paragraph">
3247 <p>AltOS New Features</p>
3252 <p>Add support for EasyMega boards.</p>
3255 <p>Make the APRS SSID be configurable. This lets you track
3256 different rockets on the same receiver without getting
3257 things mixed up.</p>
3260 <p>Report extra pyro channel continuity state on EasyMega and
3261 TeleMega via the beeper. This lets you easily verify flight
3262 readiness on these boards after powering up the electronics
3266 <p>Add lower telemetry data rates (2400 and 9600 bps) to
3267 increase telemetry radio range. This reduces the amount of
3268 data received as well as increasing battery consumption in
3269 the transmitter.</p>
3272 <p>Change TeleGPS to have only a single log, and append new
3273 data to it rather than using seperate per-flight logs. This
3274 avoids accidentally filling up log storage by turning
3275 TeleGPS on/off several times.</p>
3279 <div class="paragraph">
3285 <p>Increase the maximum range for altitude values from +/-32767m
3286 to +/-2147483647m, allowing the flight computers to function
3287 correctly above the 32km level.</p>
3290 <p>Continuously test pyro firing conditions during delay stage,
3291 inhibiting the pyro channel if the test fails. This prevents
3292 firing pyro charges where the conditions were good before
3293 the delay, but become bad before the delay expires.</p>
3296 <p>Allow negative numbers in pyro configuration values. This
3297 lets you specify things like descending speed or
3304 <h4 id="_altosui_and_telegps_applications_10">E.31.2. AltosUI and TeleGPS Applications</h4>
3305 <div class="paragraph">
3306 <p>AltosUI and TeleGPS New Features</p>
3311 <p>Support telemetry baud rate selection. Adds menus to
3312 the flight monitoring and configuration for baud rate
3316 <p>Support APRS SSID configuration.</p>
3319 <p>Integrate with file managers. This provides icons for all of
3320 our file types and associates our application with the files
3321 so that using a file manager to open a AltOS data file
3322 results in launching our application.</p>
3326 <div class="paragraph">
3327 <p>AltosUI Fixes</p>
3332 <p>Make the 'Graph' button on the landed tab work again.</p>
3335 <p>Make tests for Java on Windows a bit smarter, and also
3336 provide the user with the option to skip installing Java for
3337 cases where we just can’t figure out what version is installed.</p>
3341 <div style="page-break-after: always;"></div>
3345 <h3 id="_release_notes_for_version_1_4_2">E.32. Release Notes for Version 1.4.2</h3>
3346 <div class="paragraph">
3347 <p>Version 1.4.2 is a minor release. It fixes Java-related install issues on
3351 <h4 id="_altosui_and_telegps_applications_11">E.32.1. AltosUI and TeleGPS Applications</h4>
3352 <div class="paragraph">
3353 <p>Windows Install Fixes</p>
3358 <p>Checks for Java installation data in more registry locations.</p>
3361 <p>Allows user to bypass Java installation in case the
3362 detection fails.</p>
3366 <div style="page-break-after: always;"></div>
3370 <h3 id="_release_notes_for_version_1_4_1">E.33. Release Notes for Version 1.4.1</h3>
3371 <div class="paragraph">
3372 <p>Version 1.4.1 is a minor release. It fixes install issues on
3373 Windows and provides the missing TeleMetrum V2.0 firmware. There
3374 aren’t any changes to the firmware or host applications at
3375 all. All Windows users will want to upgrade to get the signed
3376 driver, but Mac and Linux users who do not need the TeleMetrum
3377 V2.0 firmware image will not need to upgrade.</p>
3380 <h4 id="_altosui_and_telegps_applications_12">E.33.1. AltosUI and TeleGPS Applications:</h4>
3381 <div class="paragraph">
3382 <p>Windows Install Fixes</p>
3387 <p>Provide signed Windows driver files. This should avoid any need to
3388 disable driver signature checking on Windows 7 or 8.</p>
3391 <p>Fix Java version detection and download. Previously, the
3392 installer would only look for Java 6 or 7 and insist on
3393 downloading its own Java bits if there was something else
3394 installed. Furthermore, the 64-bit Java link provided didn’t
3395 work for anyone other than Keith, making it impossible to
3396 install AltOS on any machine with Java SE 8 installed.</p>
3400 <div class="paragraph">
3406 <p>Include 1.4 firmware for TeleMetrum V2.0. None of the
3407 installers shipped this file. Now it’s included in the AltOS
3408 packages for Linux, Mac and Windows.</p>
3411 <p>Include Google Application Key for map downloading. The 1.4
3412 release didn’t have this key in the released version of the
3413 software, making map downloading fail for most people.</p>
3417 <div style="page-break-after: always;"></div>
3421 <h3 id="_release_notes_for_version_1_4">E.34. Release Notes for Version 1.4</h3>
3422 <div class="paragraph">
3423 <p>Version 1.4 is a major release. It includes support for our new
3424 TeleGPS product, new features and bug fixes in in the flight
3425 software for all our boards and the AltosUI ground station</p>
3428 <h4 id="_altos_31">E.34.1. AltOS</h4>
3429 <div class="paragraph">
3430 <p>AltOS new features:</p>
3435 <p>Add support for TeleGPS boards.</p>
3438 <p>Make the beeper tone configurable, making it
3439 possible to distinguish between two Altus Metrum
3440 products in the same ebay.</p>
3443 <p>Make the firing time for extra pyro channels
3444 configurable, allowing longer (or shorter) than the
3445 default 50ms. Only relevant for TeleMega at this
3450 <div class="paragraph">
3456 <p>Replace the 'dit dit dit' tones at startup with the
3457 current battery voltage, measured in tenths of a
3458 volt. This lets you check the battery voltage
3459 without needing telemetry, which is especially
3460 useful on EasyMini.</p>
3463 <p>Change state beeping to "Farnsworth spacing", which
3464 means they’re quite a bit faster than before, and so
3465 they take less time to send.</p>
3468 <p>Fix bug preventing the selection of the 'Flight
3469 State After' mode in pyro configuration.</p>
3472 <p>Fix bug where erasing flights would reset the flight
3473 number to 2 on TeleMega and TeleMetrum v2.</p>
3476 <p>Fix u-Blox GPS driver to mark course and speed data
3477 as being present.</p>
3483 <h4 id="_altosui_application">E.34.2. AltosUI Application</h4>
3484 <div class="paragraph">
3485 <p>AltosUI new features:</p>
3490 <p>Add zooming and new content types (terrain and road
3491 maps) to map view. Change map storage format from
3492 PNG to Jpeg, which saves a huge amount of disk
3493 space. You will need to re-download all of your
3494 pre-loaded map images.</p>
3497 <p>Add a distance measuring device to the maps
3498 view. Select this by using any button other than the
3499 left one, or by pressing shift or control on the
3500 keyboard while using the left button.</p>
3503 <p>Add new 'Ignitor' tab to the flight monitor display
3504 for TeleMega’s extra ignitors.</p>
3507 <p>Add additional ignitor firing marks and voltages to
3508 the graph so you can see when the ignitors fired,
3509 along with the ignitor voltages.</p>
3512 <p>Add GPS course, ground speed and climb rate as
3513 optional graph elements.</p>
3517 <div class="paragraph">
3518 <p>AltosUI fixes:</p>
3523 <p>When flashing new firmware, re-try opening the
3524 device as sometimes it takes a while for the
3525 underlying operating system to recognize that the
3526 device has rebooted in preparation for the flashing
3530 <p>Hide Tilt Angle in ascent tab for devices that don’t
3534 <p>Increase the width of data lines in the graphs to
3535 make them easier to read.</p>
3538 <p>Filter out speed and acceleration spikes caused by
3539 ejection charge firing when computing the maximum
3540 values. This provides a more accurate reading of
3544 <p>Fix EasyMini voltage displays. Early EasyMini
3545 prototypes used a 3.0V regulator, and AltosUI still
3546 used that value as the basis of the
3547 computation. Production EasyMini boards have always
3548 shipped with a 3.3V regulator. Also, purple EasyMini
3549 boards sensed the battery voltage past the blocking
3550 diode, resulting in a drop of about 150mV from the
3551 true battery voltage. Compensate for that when
3552 displaying the value.</p>
3555 <p>Display error message when trying to configure
3556 maximum flight log size while the flight computer
3557 still has flight data stored.</p>
3560 <p>Handle TeleMetrum and TeleMini eeprom files
3561 generated with pre-1.0 firmware. Those ancient
3562 versions didn’t report the log format, so just use
3563 the product name instead.</p>
3569 <h4 id="_telegps_application_2">E.34.3. TeleGPS Application</h4>
3573 <p>New application designed for use with TeleGPS boards.</p>
3576 <p>Shares code with AltosUI, mostly just trimmed down
3577 to focus on TeleGPS-related functions.</p>
3583 <h4 id="_documentation_4">E.34.4. Documentation</h4>
3584 <div class="paragraph">
3585 <p>Documentation changes:</p>
3590 <p>Re-create the drill template images; they should
3591 print correctly from Firefox at least. Ship these as
3592 individual PDF files so they’re easy to print.</p>
3595 <p>Add a description of the 'Apogee Lockout' setting,
3596 which prevents the apogee charge from firing for a
3597 configurable amount of time after boost.</p>
3607 <div id="footer-text">
3609 Last updated 2023-02-02 13:06:56 -0700
projects / web / altusmetrum / blob