From 23d7a60a20365d6c9b3e6f2a58f6a353de8dd593 Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 11 Dec 2017 22:22:04 -0800 Subject: Remove release notes from AltOS/doc. Update 1.8.3 release notes without header Signed-off-by: Keith Packard --- AltOS/doc/release-notes-1.1.1.html | 50 -------------------------------------- 1 file changed, 50 deletions(-) delete mode 100644 AltOS/doc/release-notes-1.1.1.html (limited to 'AltOS/doc/release-notes-1.1.1.html') diff --git a/AltOS/doc/release-notes-1.1.1.html b/AltOS/doc/release-notes-1.1.1.html deleted file mode 100644 index 8cf5f24..0000000 --- a/AltOS/doc/release-notes-1.1.1.html +++ /dev/null @@ -1,50 +0,0 @@ - -Release Notes for Version 1.1

Release Notes for Version 1.1

Bdale Garbee

Keith Packard

- This document is released under the terms of the - - Creative Commons ShareAlike 3.0 - - license. -


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.

1. AltOS

AltOS fixes:

  • -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. -

2. AltosUI

AltosUI new features:

  • -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. -

AltosUI fixes:

  • -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. -
  • -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. -
  • -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. -
\ No newline at end of file -- cgit v1.2.3