]> git.gag.com Git - web/altusmetrum/commitdiff
1.1.1 release
authorBdale Garbee <bdale@gag.com>
Sun, 16 Sep 2012 20:23:12 +0000 (14:23 -0600)
committerBdale Garbee <bdale@gag.com>
Sun, 16 Sep 2012 20:23:12 +0000 (14:23 -0600)
AltOS/releases/1.1.1.mdwn [new file with mode: 0644]
AltOS/releases/1.1.1/Altos-Linux-1.1.1.tar.bz2 [new file with mode: 0644]
AltOS/releases/1.1.1/Altos-Mac-1.1.1.zip [new file with mode: 0644]
AltOS/releases/1.1.1/Altos-Windows-1-1-1.exe [new file with mode: 0644]
AltOS/releases/1.1.1/release-notes-1.1.1.html [new file with mode: 0644]

diff --git a/AltOS/releases/1.1.1.mdwn b/AltOS/releases/1.1.1.mdwn
new file mode 100644 (file)
index 0000000..d87aee0
--- /dev/null
@@ -0,0 +1,8 @@
+[[!inline pages="./1.1.1/release-notes-1.1.1.html" rss="no" raw="yes" ]]
+
+- Available Files:
+       - [Windows Installer](/AltOS/releases/1.1.1/Altos-Windows-1-1-1.exe)
+       - [Mac OS X Package](/AltOS/releases/1.1.1/Altos-Mac-1.1.1.zip)
+       - [Linux](/AltOS/releases/1.1.1/Altos-Linux-1.1.1.tar.bz2)
+       - [Source Snapshot](http://git.gag.com/?p=fw/altos;a=snapshot;h=refs/tags/1.1.1;sf=tgz)
+
diff --git a/AltOS/releases/1.1.1/Altos-Linux-1.1.1.tar.bz2 b/AltOS/releases/1.1.1/Altos-Linux-1.1.1.tar.bz2
new file mode 100644 (file)
index 0000000..23d489a
Binary files /dev/null and b/AltOS/releases/1.1.1/Altos-Linux-1.1.1.tar.bz2 differ
diff --git a/AltOS/releases/1.1.1/Altos-Mac-1.1.1.zip b/AltOS/releases/1.1.1/Altos-Mac-1.1.1.zip
new file mode 100644 (file)
index 0000000..d636aab
Binary files /dev/null and b/AltOS/releases/1.1.1/Altos-Mac-1.1.1.zip differ
diff --git a/AltOS/releases/1.1.1/Altos-Windows-1-1-1.exe b/AltOS/releases/1.1.1/Altos-Windows-1-1-1.exe
new file mode 100644 (file)
index 0000000..1c602a6
Binary files /dev/null and b/AltOS/releases/1.1.1/Altos-Windows-1-1-1.exe differ
diff --git a/AltOS/releases/1.1.1/release-notes-1.1.1.html b/AltOS/releases/1.1.1/release-notes-1.1.1.html
new file mode 100644 (file)
index 0000000..4e33c11
--- /dev/null
@@ -0,0 +1,46 @@
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></title><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="article"><div class="titlepage"><hr></div><p>
+    Version 1.1.1 is a bug-fix release. It fixes a couple of bugs in
+    AltosUI and one firmware bug that affects TeleMetrum version 1.0
+    boards. Thanks to Bob Brown for help diagnosing the Google Earth
+    file export issue, and for suggesting the addition of the Ground
+    Distance value in the Descent tab.
+  </p><p>
+    AltOS Firmware Changes
+    </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+       TeleMetrum v1.0 boards use the AT45DB081D flash memory part to
+       store flight data, which is different from later TeleMetrum
+       boards. The AltOS v1.1 driver for this chip couldn't erase
+       memory, leaving it impossible to delete flight data or update
+       configuration values. This bug doesn't affect newer TeleMetrum
+       boards, and it doesn't affect the safety of rockets flying
+       version 1.1 firmware.
+      </li></ul></div><p>
+  </p><p>
+    AltosUI Changes
+    </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">
+       Creating a Google Earth file (KML) from on-board flight data
+       (EEPROM) would generate an empty file. The code responsible
+       for reading the EEPROM file wasn't ever setting the GPS valid
+       bits, and so the KML export code thought there was no GPS data
+       in the file.
+      </li><li class="listitem">
+       The &#8220;Landed&#8221; tab was displaying all values in metric units,
+       even when AltosUI was configured to display imperial
+       units. Somehow I just missed this tab when doing the units stuff.
+      </li><li class="listitem">
+       The &#8220;Descent&#8221; tab displays the range to the rocket, which is a
+       combination of the over-the-ground distance to the rockets
+       current latitude/longitude and the height of the rocket. As
+       such, it's useful for knowing how far away the rocket is, but
+       difficult to use when estimating where the rocket might
+       eventually land. A new &#8220;Ground Distance&#8221; field has been added
+       which displays the distance to a spot right underneath the
+       rocket.
+      </li><li class="listitem">
+       Sensor data wasn't being displayed for TeleMini flight
+       computers in Monitor Idle mode, including things like battery
+       voltage. The code that picked which kinds of data to fetch
+       from the flight computer was missing a check for TeleMini when
+       deciding whether to fetch the analog sensor data.
+      </li></ul></div><p>
+  </p></div></body></html>