2 <html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Release Notes for Version 1.1</title><link rel="stylesheet" type="text/css" href="am.css" /><meta name="generator" content="DocBook XSL Stylesheets V1.79.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm1"></a>Release Notes for Version 1.1</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Bdale</span> <span class="surname">Garbee</span></h3><code class="email"><<a class="email" href="mailto:bdale@gag.com">bdale@gag.com</a>></code></div></div><div><div class="author"><h3 class="author"><span class="firstname">Keith</span> <span class="surname">Packard</span></h3><code class="email"><<a class="email" href="mailto:keithp@keithp.com">keithp@keithp.com</a>></code></div></div><div><p class="copyright">Copyright © 2012 Bdale Garbee and Keith Packard</p></div><div><div class="legalnotice"><a id="idm19"></a><p>
3 This document is released under the terms of the
4 <a class="ulink" href="http://creativecommons.org/licenses/by-sa/3.0/" target="_top">
5 Creative Commons ShareAlike 3.0
8 </p></div></div></div><hr /></div><p>Version 1.1.1 is a bug-fix release. It fixes a couple of bugs
9 in AltosUI and one firmware bug that affects TeleMetrum
10 version 1.0 boards. Thanks to Bob Brown for help diagnosing
11 the Google Earth file export issue, and for suggesting the
12 addition of the Ground Distance value in the Descent tab.</p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altos"></a>1. AltOS</h2></div></div></div><p>AltOS fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
13 TeleMetrum v1.0 boards use the AT45DB081D flash
14 memory part to store flight data, which is different
15 from later TeleMetrum boards. The AltOS v1.1 driver
16 for this chip couldn’t erase memory, leaving it
17 impossible to delete flight data or update
18 configuration values. This bug doesn’t affect newer
19 TeleMetrum boards, and it doesn’t affect the safety
20 of rockets flying version 1.1 firmware.
21 </li></ul></div></div><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="_altosui"></a>2. AltosUI</h2></div></div></div><p>AltosUI new features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
22 The “Descent” tab displays the range to the rocket,
23 which is a combination of the over-the-ground
24 distance to the rockets current latitude/longitude
25 and the height of the rocket. As such, it’s useful
26 for knowing how far away the rocket is, but
27 difficult to use when estimating where the rocket
28 might eventually land. A new “Ground Distance” field
29 has been added which displays the distance to a spot
30 right underneath the rocket.
31 </li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
32 Creating a Google Earth file (KML) from on-board
33 flight data (EEPROM) would generate an empty
34 file. The code responsible for reading the EEPROM
35 file wasn’t ever setting the GPS valid bits, and so
36 the KML export code thought there was no GPS data in
38 </li><li class="listitem">
39 The “Landed” tab was displaying all values in metric
40 units, even when AltosUI was configured to display
41 imperial units. Somehow I just missed this tab when
42 doing the units stuff.
43 </li><li class="listitem">
44 Sensor data wasn’t being displayed for TeleMini
45 flight computers in Monitor Idle mode, including
46 things like battery voltage. The code that picked
47 which kinds of data to fetch from the flight
48 computer was missing a check for TeleMini when
49 deciding whether to fetch the analog sensor data.
50 </li></ul></div></div></div></body></html>
projects / web / altusmetrum / blob