From: Bdale Garbee Date: Thu, 7 Oct 2021 06:20:24 +0000 (-0600) Subject: Release 1.9.9 X-Git-Url: https://git.gag.com/?p=web%2Faltusmetrum;a=commitdiff_plain;h=6267545e6a8bfd816166c5035f67e82d34d87bf1 Release 1.9.9 --- diff --git a/AltOS/releases/1.9.9.mdwn b/AltOS/releases/1.9.9.mdwn new file mode 100644 index 0000000..b54ea38 --- /dev/null +++ b/AltOS/releases/1.9.9.mdwn @@ -0,0 +1,7 @@ +[[!inline pages="./1.9.9/release-notes-1.9.9.html" rss="no" raw="yes" ]] + +- Available Files: + - [Windows Installer](/AltOS/releases/1.9.9/Altos-Windows-1-9-9.exe) + - [Mac OS X Package](/AltOS/releases/1.9.9/Altos-Mac-1.9.9.dmg) + - [Linux](/AltOS/releases/1.9.9/Altos-Linux-1.9.9.sh) + - [Source Snapshot](http://git.gag.com/?p=fw/altos;a=snapshot;h=refs/tags/1.9.9;sf=tgz) diff --git a/AltOS/releases/1.9.9/Altos-Linux-1.9.9.sh b/AltOS/releases/1.9.9/Altos-Linux-1.9.9.sh new file mode 100755 index 0000000..214e76d Binary files /dev/null and b/AltOS/releases/1.9.9/Altos-Linux-1.9.9.sh differ diff --git a/AltOS/releases/1.9.9/Altos-Mac-1.9.9.dmg b/AltOS/releases/1.9.9/Altos-Mac-1.9.9.dmg new file mode 100644 index 0000000..e15c5f3 Binary files /dev/null and b/AltOS/releases/1.9.9/Altos-Mac-1.9.9.dmg differ diff --git a/AltOS/releases/1.9.9/Altos-Windows-1-9-9.exe b/AltOS/releases/1.9.9/Altos-Windows-1-9-9.exe new file mode 100644 index 0000000..8dff5bd Binary files /dev/null and b/AltOS/releases/1.9.9/Altos-Windows-1-9-9.exe differ diff --git a/AltOS/releases/1.9.9/release-notes-1.9.9.html b/AltOS/releases/1.9.9/release-notes-1.9.9.html new file mode 100644 index 0000000..f3a6190 --- /dev/null +++ b/AltOS/releases/1.9.9/release-notes-1.9.9.html @@ -0,0 +1,86 @@ + + + + + + + +Release Notes for Version 1.9.9 + + + + +
+
+
+
+

Version 1.9.9

+
+
+

This release contains a critical bug fix for a problem +introduced in version 1.9.8 for TeleMega and EasyMega +boards. This problem occurs when using the stored +configuration from 1.9.7 or earlier.

+
+
+

If you are running 1.9.8 or are upgrading from 1.9.8 on any +version of TeleMega or EasyMega, you must reconfigure all pyro +channels, recalibrate accelerometers, reset the APRS interval, +adjust the beep tone and reset the pyro time.

+
+
+
+
+

AltOS

+
+
+
    +
  • +

    Fix EasyMega and TeleMega upgrade process from 1.9.7 or +earlier. 1.9.8 introduced larger delay values, which +required modifying the configuration in-place, and the 1.9.8 +version had a flaw which broke the pyro channel config and +all of the config values beyond that in memory, including +APRS interval, IMU accel calibation, beep tone and pyro +time.

    +
  • +
  • +

    Fix TeleMega v5.0 mag sensor driver. This driver was quite +broken due to developing it in the presence of the magnetic +beeper on the board. Because of that beeper, the values this +sensor records are not accurate. Fortunately, they are not +used for controlling the flight.

    +
  • +
+
+
+
+
+

AltosUI

+
+
+
    +
  • +

    Parse TeleMega v5.0 log files. A missing check in the code +meant that the TeleMega v5.0 log files would cause an error +when attempting to load them. Logs saved with AltosUI +1.9.8 were not affected, only the presentation of the data +was broken.

    +
  • +
+
+
+
+
+ + + \ No newline at end of file diff --git a/MicroPeak/releases/1.9.9.mdwn b/MicroPeak/releases/1.9.9.mdwn new file mode 100644 index 0000000..4d9df17 --- /dev/null +++ b/MicroPeak/releases/1.9.9.mdwn @@ -0,0 +1,7 @@ +[[!inline pages="./1.9.9/release-notes-1.9.9.html" rss="no" raw="yes" ]] + +- Available Files: + - [Windows Installer](/MicroPeak/releases/1.9.9/MicroPeak-Windows-1-9-9.exe) + - [Mac OS X Package](/MicroPeak/releases/1.9.9/MicroPeak-Mac-1.9.9.dmg) + - [Linux](/MicroPeak/releases/1.9.9/MicroPeak-Linux-1.9.9.sh) + - [Source Snapshot](http://git.gag.com/?p=fw/altos;a=snapshot;h=refs/tags/1.9.9;sf=tgz) diff --git a/MicroPeak/releases/1.9.9/MicroPeak-Linux-1.9.9.sh b/MicroPeak/releases/1.9.9/MicroPeak-Linux-1.9.9.sh new file mode 100755 index 0000000..04830a0 Binary files /dev/null and b/MicroPeak/releases/1.9.9/MicroPeak-Linux-1.9.9.sh differ diff --git a/MicroPeak/releases/1.9.9/MicroPeak-Mac-1.9.9.dmg b/MicroPeak/releases/1.9.9/MicroPeak-Mac-1.9.9.dmg new file mode 100644 index 0000000..9a93167 Binary files /dev/null and b/MicroPeak/releases/1.9.9/MicroPeak-Mac-1.9.9.dmg differ diff --git a/MicroPeak/releases/1.9.9/MicroPeak-Windows-1-9-9.exe b/MicroPeak/releases/1.9.9/MicroPeak-Windows-1-9-9.exe new file mode 100644 index 0000000..bab744d Binary files /dev/null and b/MicroPeak/releases/1.9.9/MicroPeak-Windows-1-9-9.exe differ diff --git a/MicroPeak/releases/1.9.9/release-notes-1.9.9.html b/MicroPeak/releases/1.9.9/release-notes-1.9.9.html new file mode 100644 index 0000000..f3a6190 --- /dev/null +++ b/MicroPeak/releases/1.9.9/release-notes-1.9.9.html @@ -0,0 +1,86 @@ + + + + + + + +Release Notes for Version 1.9.9 + + + + +
+
+
+
+

Version 1.9.9

+
+
+

This release contains a critical bug fix for a problem +introduced in version 1.9.8 for TeleMega and EasyMega +boards. This problem occurs when using the stored +configuration from 1.9.7 or earlier.

+
+
+

If you are running 1.9.8 or are upgrading from 1.9.8 on any +version of TeleMega or EasyMega, you must reconfigure all pyro +channels, recalibrate accelerometers, reset the APRS interval, +adjust the beep tone and reset the pyro time.

+
+
+
+
+

AltOS

+
+
+
    +
  • +

    Fix EasyMega and TeleMega upgrade process from 1.9.7 or +earlier. 1.9.8 introduced larger delay values, which +required modifying the configuration in-place, and the 1.9.8 +version had a flaw which broke the pyro channel config and +all of the config values beyond that in memory, including +APRS interval, IMU accel calibation, beep tone and pyro +time.

    +
  • +
  • +

    Fix TeleMega v5.0 mag sensor driver. This driver was quite +broken due to developing it in the presence of the magnetic +beeper on the board. Because of that beeper, the values this +sensor records are not accurate. Fortunately, they are not +used for controlling the flight.

    +
  • +
+
+
+
+
+

AltosUI

+
+
+
    +
  • +

    Parse TeleMega v5.0 log files. A missing check in the code +meant that the TeleMega v5.0 log files would cause an error +when attempting to load them. Logs saved with AltosUI +1.9.8 were not affected, only the presentation of the data +was broken.

    +
  • +
+
+
+
+
+ + + \ No newline at end of file diff --git a/TeleGPS/releases/1.9.9.mdwn b/TeleGPS/releases/1.9.9.mdwn new file mode 100644 index 0000000..1ce7253 --- /dev/null +++ b/TeleGPS/releases/1.9.9.mdwn @@ -0,0 +1,7 @@ +[[!inline pages="./1.9.9/release-notes-1.9.9.html" rss="no" raw="yes" ]] + +- Available Files: + - [Windows Installer](/TeleGPS/releases/1.9.9/TeleGPS-Windows-1-9-9.exe) + - [Mac OS X Package](/TeleGPS/releases/1.9.9/TeleGPS-Mac-1.9.9.dmg) + - [Linux](/TeleGPS/releases/1.9.9/TeleGPS-Linux-1.9.9.sh) + - [Source Snapshot](http://git.gag.com/?p=fw/altos;a=snapshot;h=refs/tags/1.9.9;sf=tgz) diff --git a/TeleGPS/releases/1.9.9/TeleGPS-Linux-1.9.9.sh b/TeleGPS/releases/1.9.9/TeleGPS-Linux-1.9.9.sh new file mode 100755 index 0000000..7fcfffd Binary files /dev/null and b/TeleGPS/releases/1.9.9/TeleGPS-Linux-1.9.9.sh differ diff --git a/TeleGPS/releases/1.9.9/TeleGPS-Mac-1.9.9.dmg b/TeleGPS/releases/1.9.9/TeleGPS-Mac-1.9.9.dmg new file mode 100644 index 0000000..710f1c8 Binary files /dev/null and b/TeleGPS/releases/1.9.9/TeleGPS-Mac-1.9.9.dmg differ diff --git a/TeleGPS/releases/1.9.9/TeleGPS-Windows-1-9-9.exe b/TeleGPS/releases/1.9.9/TeleGPS-Windows-1-9-9.exe new file mode 100644 index 0000000..d6d799e Binary files /dev/null and b/TeleGPS/releases/1.9.9/TeleGPS-Windows-1-9-9.exe differ diff --git a/TeleGPS/releases/1.9.9/release-notes-1.9.9.html b/TeleGPS/releases/1.9.9/release-notes-1.9.9.html new file mode 100644 index 0000000..f3a6190 --- /dev/null +++ b/TeleGPS/releases/1.9.9/release-notes-1.9.9.html @@ -0,0 +1,86 @@ + + + + + + + +Release Notes for Version 1.9.9 + + + + +
+
+
+
+

Version 1.9.9

+
+
+

This release contains a critical bug fix for a problem +introduced in version 1.9.8 for TeleMega and EasyMega +boards. This problem occurs when using the stored +configuration from 1.9.7 or earlier.

+
+
+

If you are running 1.9.8 or are upgrading from 1.9.8 on any +version of TeleMega or EasyMega, you must reconfigure all pyro +channels, recalibrate accelerometers, reset the APRS interval, +adjust the beep tone and reset the pyro time.

+
+
+
+
+

AltOS

+
+
+
    +
  • +

    Fix EasyMega and TeleMega upgrade process from 1.9.7 or +earlier. 1.9.8 introduced larger delay values, which +required modifying the configuration in-place, and the 1.9.8 +version had a flaw which broke the pyro channel config and +all of the config values beyond that in memory, including +APRS interval, IMU accel calibation, beep tone and pyro +time.

    +
  • +
  • +

    Fix TeleMega v5.0 mag sensor driver. This driver was quite +broken due to developing it in the presence of the magnetic +beeper on the board. Because of that beeper, the values this +sensor records are not accurate. Fortunately, they are not +used for controlling the flight.

    +
  • +
+
+
+
+
+

AltosUI

+
+
+
    +
  • +

    Parse TeleMega v5.0 log files. A missing check in the code +meant that the TeleMega v5.0 log files would cause an error +when attempting to load them. Logs saved with AltosUI +1.9.8 were not affected, only the presentation of the data +was broken.

    +
  • +
+
+
+
+
+ + + \ No newline at end of file