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.0.1 is a major release, adding support for the TeleMini
8 device and lots of new AltosUI features
11 AltOS Firmware Changes
15 Add TeleMini v1.0 support. Firmware images for TeleMini are
16 included in AltOS releases.
21 Change telemetry to be encoded in multiple 32-byte packets. This
22 enables support for TeleMini and other devices without requiring
23 further updates to the TeleDongle firmware.
28 Support operation of TeleMetrum with the antenna pointing
29 aft. Previous firmware versions required the antenna to be
30 pointing upwards, now there is a configuration option allowing
31 the antenna to point aft, to aid installation in some airframes.
36 Ability to disable telemetry. For airframes where an antenna
37 just isn't possible, or where radio transmissions might cause
38 trouble with other electronics, there's a configuration option
39 to disable all telemetry. Note that the board will still
40 enable the radio link in idle mode.
45 Arbitrary frequency selection. The radios in Altus Metrum
46 devices can be programmed to a wide range of frequencies, so
47 instead of limiting devices to 10 pre-selected 'channels', the
48 new firmware allows the user to choose any frequency in the
49 70cm band. Note that the RF matching circuit on the boards is
50 tuned for around 435MHz, so frequencies far from that may
51 reduce the available range.
56 Kalman-filter based flight-tracking. The model based sensor
57 fusion approach of a Kalman filter means that AltOS now
58 computes apogee much more accurately than before, generally
59 within a fraction of a second. In addition, this approach
60 allows the baro-only TeleMini device to correctly identify
61 Mach transitions, avoiding the error-prone selection of a Mach
72 Wait for altimeter when using packet mode. Instead of quicly
73 timing out when trying to initialize a packet mode
74 configuration connection, AltosUI now waits indefinitely for
75 the remote device to appear, providing a cancel button should
76 the user get bored. This is necessary as the TeleMini can only
77 be placed in "Idle" mode if AltosUI is polling it.
82 Add main/apogee voltage graphs to the data plot. This provides
83 a visual indication if the igniters fail before being fired.
88 Scan for altimeter devices by watching the defined telemetry
89 frequencies. This avoids the problem of remembering what
90 frequency a device was configured to use, which is especially
91 important with TeleMini which does not include a USB connection.
96 Monitor altimeter state in "Idle" mode. This provides much of
97 the information presented in the "Pad" dialog from the Monitor
98 Flight command, monitoring the igniters, battery and GPS
99 status withing requiring the flight computer to be armed and
105 Pre-load map images from home. For those launch sites which
106 don't provide free Wi-Fi, this allows you to download the
107 necessary satellite images given the location of the launch
108 site. A list of known launch sites is maintained at
109 altusmetrum.org which AltosUI downloads to populate a menu; if
110 you've got a launch site not on that list, please send the
111 name of it, latitude and longitude along with a link to the
112 web site of the controlling club to the altusmetrum mailing list.
117 Flight statistics are now displayed in the Graph data
118 window. These include max height/speed/accel, average descent
119 rates and a few other bits of information. The Graph Data
120 window can now be reached from the 'Landed' tab in the Monitor
121 Flight window so you can immediately see the results of a