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