-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title></title><meta name="generator" content="DocBook XSL Stylesheets V1.78.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" style="list-style-type: disc; "><li class="listitem"><p>
- 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.
- </p></li></ul></div><p>
- </p><p>
- AltosUI Changes
- </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
- 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.
- </p></li><li class="listitem"><p>
- The “Landed” 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.
- </p></li><li class="listitem"><p>
- The “Descent” 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 “Ground Distance” field has been added
- which displays the distance to a spot right underneath the
- rocket.
- </p></li><li class="listitem"><p>
- 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.
- </p></li></ul></div><p>
- </p></div></body></html>
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><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.78.1" /></head><body><div xml:lang="en" class="article" lang="en"><div class="titlepage"><div><div><h2 class="title"><a id="idm45495557658240"></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="idm45495557772624"></a><p>
+ This document is released under the terms of the
+ <a class="ulink" href="http://creativecommons.org/licenses/by-sa/3.0/" target="_top">
+ Creative Commons ShareAlike 3.0
+ </a>
+ license.
+ </p></div></div></div><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><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">
+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></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">
+The “Descent” 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 “Ground Distance” field
+has been added which displays the distance to a spot
+right underneath the rocket.
+</li></ul></div><p>AltosUI fixes:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-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 “Landed” 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">
+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></div></div></body></html>
\ No newline at end of file
projects / web / altusmetrum / blobdiff