1 <?xml version="1.0" encoding="utf-8" ?>
2 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "/usr/share/xml/docbook/schema/dtd/4.5/docbookx.dtd">
7 Version 1.2.1 is a minor release. It adds support for TeleBT and
8 the AltosDroid application, provides several new features in
9 AltosUI and fixes some bugs in the AltOS firmware.
12 AltOS Firmware Changes
15 Add support for TeleBT
18 In TeleMini recovery mode (when booted with the outer two
19 debug pins connected together), the radio parameters are also
20 set back to defaults (434.550MHz, N0CALL, factory radio cal).
23 Add support for reflashing the SkyTraq GPS chips. This
24 requires special host-side code which currently only exists
28 Correct Kalman filter model error covariance matrix. The
29 values used previously assumed continuous measurements instead
30 of discrete measurements.
33 Fix some bugs in the USB driver for TeleMetrum and TeleDongle
34 that affected Windows users.
37 Adjusted the automatic gain control parameters that affect
38 receive performance for TeleDongle. Field tests indicate that this
39 may improve receive performance somewhat.
47 Handle missing GPS lock in 'Descent' tab. Previously, if the
48 GPS position of the pad was unknown, an exception would be
49 raised, breaking the Descent tab contents.
52 Improve the graph, adding tool-tips to show values near the
53 cursor and making the displayed set of values configurable,
54 adding all of the flight data as options while leaving the
55 default settings alone so that the graph starts by showing
56 height, speed and acceleration.
59 Make the initial position of the AltosUI top level window
60 configurable. Along with this change, the other windows will
61 pop up at 'sensible' places now, instead of on top of one
65 Add callsign to Monitor idle window and connecting
66 dialogs. This makes it clear which callsign is being used so
67 that the operator will be aware that it must match the flight
68 computer value or no communication will work.
71 When downloading flight data, display the block number so that
72 the user has some sense of progress. Unfortunately, we don't
73 know how many blocks will need to be downloaded, but at least
74 it isn't just sitting there doing nothing for a long time.
77 Add GPS data and a map to the graph window. This lets you see
78 a complete summary of the flight without needing to 'replay'