Mostly involved getting the listitem contents into para elements.
Signed-off-by: Keith Packard <keithp@keithp.com>
-<?xml version="1.0" encoding="utf-8" ?>
+<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"/usr/share/xml/docbook/schema/dtd/4.5/docbookx.dtd">
<book>
</revision>
</revhistory>
</bookinfo>
- <acknowledgements>
+ <dedication>
+ <title>Acknowledgements</title>
<para>
Thanks to Bob Finch, W9YA, NAR 12965, TRA 12350 for writing "The
Mere-Mortals Quick Start/Usage Guide to the Altus Metrum Starter
NAR #88757, TRA #12200
</literallayout>
</para>
- </acknowledgements>
+ </dedication>
<chapter>
<title>Introduction and Overview</title>
<para>
configured as follows:
<itemizedlist>
<listitem>
+ <para>
Sets the radio frequency to 434.550MHz
+ </para>
</listitem>
<listitem>
+ <para>
Sets the radio calibration back to the factory value.
+ </para>
</listitem>
<listitem>
+ <para>
Sets the callsign to N0CALL
+ </para>
</listitem>
<listitem>
+ <para>
Does not go to 'pad' mode after five seconds.
+ </para>
</listitem>
</itemizedlist>
</para>
</para>
</listitem>
</itemizedlist>
- <para>
- The Launchpad tab also shows the computed launch pad position
- and altitude, averaging many reported positions to improve the
- accuracy of the fix.
- </para>
</para>
+ <para>
+ The Launchpad tab also shows the computed launch pad position
+ and altitude, averaging many reported positions to improve the
+ accuracy of the fix.
+ </para>
</section>
<section>
<title>Ascent</title>
</para>
</listitem>
</itemizedlist>
- <para>
- The Launchpad tab also shows the computed launch pad position
- and altitude, averaging many reported positions to improve the
- accuracy of the fix.
- </para>
- </para>
+ </para>
+ <para>
+ The Launchpad tab also shows the computed launch pad position
+ and altitude, averaging many reported positions to improve the
+ accuracy of the fix.
+ </para>
</section>
</section>
<section>
So, to recap, on the ground the hardware you'll need includes:
<orderedlist inheritnum='inherit' numeration='arabic'>
<listitem>
- an antenna and feed-line or adapter
+ <para>
+ an antenna and feed-line or adapter
+ </para>
</listitem>
<listitem>
- a TeleDongle
+ <para>
+ a TeleDongle
+ </para>
</listitem>
<listitem>
- a notebook computer
+ <para>
+ a notebook computer
+ </para>
</listitem>
<listitem>
- optionally, a hand-held GPS receiver
+ <para>
+ optionally, a hand-held GPS receiver
+ </para>
</listitem>
<listitem>
- optionally, an HT or receiver covering 435 MHz
+ <para>
+ optionally, an HT or receiver covering 435 MHz
+ </para>
</listitem>
</orderedlist>
</para>
</para>
<orderedlist inheritnum='inherit' numeration='arabic'>
<listitem>
- Make sure TeleMetrum is aligned precisely along the axis of
- acceleration so that the accelerometer can accurately
- capture data during the flight.
+ <para>
+ Make sure TeleMetrum is aligned precisely along the axis of
+ acceleration so that the accelerometer can accurately
+ capture data during the flight.
+ </para>
</listitem>
<listitem>
- Watch for any metal touching components on the
- board. Shorting out connections on the bottom of the board
- can cause the altimeter to fail during flight.
+ <para>
+ Watch for any metal touching components on the
+ board. Shorting out connections on the bottom of the board
+ can cause the altimeter to fail during flight.
+ </para>
</listitem>
</orderedlist>
</section>
attenuate the GPS signal.
<orderedlist inheritnum='inherit' numeration='arabic'>
<listitem>
- Conductive tubing or coatings. Carbon fiber and metal
- tubing, or metallic paint will all dramatically attenuate the
- GPS signal. We've never heard of anyone successfully
- receiving GPS from inside these materials.
+ <para>
+ Conductive tubing or coatings. Carbon fiber and metal
+ tubing, or metallic paint will all dramatically attenuate the
+ GPS signal. We've never heard of anyone successfully
+ receiving GPS from inside these materials.
+ </para>
</listitem>
<listitem>
- Metal components near the GPS patch antenna. These will
- de-tune the patch antenna, changing the resonant frequency
- away from the L1 carrier and reduce the effectiveness of the
- antenna. You can place as much stuff as you like beneath the
- antenna as that's covered with a ground plane. But, keep
- wires and metal out from above the patch antenna.
+ <para>
+ Metal components near the GPS patch antenna. These will
+ de-tune the patch antenna, changing the resonant frequency
+ away from the L1 carrier and reduce the effectiveness of the
+ antenna. You can place as much stuff as you like beneath the
+ antenna as that's covered with a ground plane. But, keep
+ wires and metal out from above the patch antenna.
+ </para>
</listitem>
</orderedlist>
</para>
</para>
<itemizedlist>
<listitem>
- Keep wires from different circuits apart. Moving circuits
- further apart will reduce RFI.
+ <para>
+ Keep wires from different circuits apart. Moving circuits
+ further apart will reduce RFI.
+ </para>
</listitem>
<listitem>
+ <para>
Avoid parallel wires from different circuits. The longer two
wires run parallel to one another, the larger the amount of
transferred energy. Cross wires at right angles to reduce
RFI.
+ </para>
</listitem>
<listitem>
+ <para>
Twist wires from the same circuits. Two wires the same
distance from the transmitter will get the same amount of
induced energy which will then cancel out. Any time you have
even out distances and reduce RFI. For altimeters, this
includes battery leads, switch hookups and igniter
circuits.
+ </para>
</listitem>
<listitem>
+ <para>
Avoid resonant lengths. Know what frequencies are present
in the environment and avoid having wire lengths near a
natural resonant length. Altusmetrum products transmit on the
70cm amateur band, so you should avoid lengths that are a
simple ratio of that length; essentially any multiple of 1/4
of the wavelength (17.5cm).
+ </para>
</listitem>
</itemizedlist>
</section>
<title>Updating TeleMetrum Firmware</title>
<orderedlist inheritnum='inherit' numeration='arabic'>
<listitem>
+ <para>
Find the 'programming cable' that you got as part of the starter
kit, that has a red 8-pin MicroMaTch connector on one end and a
red 4-pin MicroMaTch connector on the other end.
+ </para>
</listitem>
<listitem>
+ <para>
Take the 2 screws out of the TeleDongle case to get access
to the circuit board.
+ </para>
</listitem>
<listitem>
+ <para>
Plug the 8-pin end of the programming cable to the
matching connector on the TeleDongle, and the 4-pin end to the
matching connector on the TeleMetrum.
Note that each MicroMaTch connector has an alignment pin that
goes through a hole in the PC board when you have the cable
oriented correctly.
+ </para>
</listitem>
<listitem>
+ <para>
Attach a battery to the TeleMetrum board.
+ </para>
</listitem>
<listitem>
+ <para>
Plug the TeleDongle into your computer's USB port, and power
up the TeleMetrum.
+ </para>
</listitem>
<listitem>
+ <para>
Run AltosUI, and select 'Flash Image' from the File menu.
+ </para>
</listitem>
<listitem>
+ <para>
Pick the TeleDongle device from the list, identifying it as the
programming device.
+ </para>
</listitem>
<listitem>
+ <para>
Select the image you want put on the TeleMetrum, which should have a
name in the form telemetrum-v1.2-1.0.0.ihx. It should be visible
in the default directory, if not you may have to poke around
your system to find it.
+ </para>
</listitem>
<listitem>
+ <para>
Make sure the configuration parameters are reasonable
looking. If the serial number and/or RF configuration
values aren't right, you'll need to change them.
+ </para>
</listitem>
<listitem>
+ <para>
Hit the 'OK' button and the software should proceed to flash
the TeleMetrum with new firmware, showing a progress bar.
+ </para>
</listitem>
<listitem>
+ <para>
Confirm that the TeleMetrum board seems to have updated OK, which you
can do by plugging in to it over USB and using a terminal program
to connect to the board and issue the 'v' command to check
the version, etc.
+ </para>
</listitem>
<listitem>
+ <para>
If something goes wrong, give it another try.
+ </para>
</listitem>
</orderedlist>
</section>
<title>Updating TeleMini Firmware</title>
<orderedlist inheritnum='inherit' numeration='arabic'>
<listitem>
+<para>
You'll need a special 'programming cable' to reprogram the
TeleMini. It's available on the Altus Metrum web store, or
you can make your own using an 8-pin MicroMaTch connector on
one end and a set of four pins on the other.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Take the 2 screws out of the TeleDongle case to get access
to the circuit board.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Plug the 8-pin end of the programming cable to the matching
connector on the TeleDongle, and the 4-pins into the holes
in the TeleMini circuit board. Note that the MicroMaTch
the PC board when you have the cable oriented correctly, and
that pin 1 on the TeleMini board is marked with a square pad
while the other pins have round pads.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Attach a battery to the TeleMini board.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Plug the TeleDongle into your computer's USB port, and power
up the TeleMini
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Run AltosUI, and select 'Flash Image' from the File menu.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Pick the TeleDongle device from the list, identifying it as the
programming device.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Select the image you want put on the TeleMini, which should have a
name in the form telemini-v1.0-1.0.0.ihx. It should be visible
in the default directory, if not you may have to poke around
your system to find it.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Make sure the configuration parameters are reasonable
looking. If the serial number and/or RF configuration
values aren't right, you'll need to change them.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Hit the 'OK' button and the software should proceed to flash
the TeleMini with new firmware, showing a progress bar.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Confirm that the TeleMini board seems to have updated OK, which you
can do by configuring it over the radio link through the TeleDongle, or
letting it come up in "flight" mode and listening for telemetry.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
If something goes wrong, give it another try.
- </listitem>
+ </para>
+</listitem>
</orderedlist>
</section>
<section>
</para>
<orderedlist inheritnum='inherit' numeration='arabic'>
<listitem>
+<para>
Find the 'programming cable' that you got as part of the starter
kit, that has a red 8-pin MicroMaTch connector on one end and a
red 4-pin MicroMaTch connector on the other end.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Find the USB cable that you got as part of the starter kit, and
plug the "mini" end in to the mating connector on TeleMetrum or TeleDongle.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Take the 2 screws out of the TeleDongle case to get access
to the circuit board.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Plug the 8-pin end of the programming cable to the
matching connector on the programmer, and the 4-pin end to the
matching connector on the TeleDongle.
Note that each MicroMaTch connector has an alignment pin that
goes through a hole in the PC board when you have the cable
oriented correctly.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Attach a battery to the TeleMetrum board if you're using one.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Plug both the programmer and the TeleDongle into your computer's USB
ports, and power up the programmer.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Run AltosUI, and select 'Flash Image' from the File menu.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Pick the programmer device from the list, identifying it as the
programming device.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Select the image you want put on the TeleDongle, which should have a
name in the form teledongle-v0.2-1.0.0.ihx. It should be visible
in the default directory, if not you may have to poke around
your system to find it.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Make sure the configuration parameters are reasonable
looking. If the serial number and/or RF configuration
values aren't right, you'll need to change them. The TeleDongle
serial number is on the "bottom" of the circuit board, and can
usually be read through the translucent blue plastic case without
needing to remove the board from the case.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Hit the 'OK' button and the software should proceed to flash
the TeleDongle with new firmware, showing a progress bar.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Confirm that the TeleDongle board seems to have updated OK, which you
can do by plugging in to it over USB and using a terminal program
to connect to the board and issue the 'v' command to check
the version, etc. Once you're happy, remove the programming cable
and put the cover back on the TeleDongle.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
If something goes wrong, give it another try.
- </listitem>
+ </para>
+</listitem>
</orderedlist>
<para>
Be careful removing the programming cable from the locking 8-pin
</para>
</section>
</appendix>
- <appendix
- xmlns:xi="http://www.w3.org/2001/XInclude">
+ <appendix>
<title>Release Notes</title>
- <simplesect><title>Version 1.3</title><xi:include href="release-notes-1.3.xsl" xpointer="xpointer(/article/*)"/></simplesect>
- <simplesect><title>Version 1.2.1</title><xi:include href="release-notes-1.2.1.xsl" xpointer="xpointer(/article/*)"/></simplesect>
- <simplesect><title>Version 1.2</title><xi:include href="release-notes-1.2.xsl" xpointer="xpointer(/article/*)"/></simplesect>
- <simplesect><title>Version 1.1.1</title><xi:include href="release-notes-1.1.1.xsl" xpointer="xpointer(/article/*)"/></simplesect>
- <simplesect><title>Version 1.1</title><xi:include href="release-notes-1.1.xsl" xpointer="xpointer(/article/*)"/></simplesect>
- <simplesect><title>Version 1.0.1</title><xi:include href="release-notes-1.0.1.xsl" xpointer="xpointer(/article/*)"/></simplesect>
- <simplesect><title>Version 0.9.2</title><xi:include href="release-notes-0.9.2.xsl" xpointer="xpointer(/article/*)"/></simplesect>
- <simplesect><title>Version 0.9</title><xi:include href="release-notes-0.9.xsl" xpointer="xpointer(/article/*)"/></simplesect>
- <simplesect><title>Version 0.8</title><xi:include href="release-notes-0.8.xsl" xpointer="xpointer(/article/*)"/></simplesect>
- <simplesect><title>Version 0.7.1</title><xi:include href="release-notes-0.7.1.xsl" xpointer="xpointer(/article/*)"/></simplesect>
+ <simplesect>
+ <title>Version 1.3</title>
+ <xi:include
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="release-notes-1.3.xsl"
+ xpointer="xpointer(/article/*)"/>
+ </simplesect>
+ <simplesect>
+ <title>Version 1.2.1</title>
+ <xi:include
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="release-notes-1.2.1.xsl"
+ xpointer="xpointer(/article/*)"/>
+ </simplesect>
+ <simplesect>
+ <title>Version 1.2</title>
+ <xi:include
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="release-notes-1.2.xsl"
+ xpointer="xpointer(/article/*)"/>
+ </simplesect>
+ <simplesect>
+ <title>Version 1.1.1</title>
+ <xi:include
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="release-notes-1.1.1.xsl"
+ xpointer="xpointer(/article/*)"/>
+ </simplesect>
+ <simplesect>
+ <title>Version 1.1</title>
+ <xi:include
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="release-notes-1.1.xsl"
+ xpointer="xpointer(/article/*)"/>
+ </simplesect>
+ <simplesect>
+ <title>Version 1.0.1</title>
+ <xi:include
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="release-notes-1.0.1.xsl"
+ xpointer="xpointer(/article/*)"/>
+ </simplesect>
+ <simplesect>
+ <title>Version 0.9.2</title>
+ <xi:include
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="release-notes-0.9.2.xsl"
+ xpointer="xpointer(/article/*)"/>
+ </simplesect>
+ <simplesect>
+ <title>Version 0.9</title>
+ <xi:include
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="release-notes-0.9.xsl"
+ xpointer="xpointer(/article/*)"/>
+ </simplesect>
+ <simplesect>
+ <title>Version 0.8</title>
+ <xi:include
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="release-notes-0.8.xsl"
+ xpointer="xpointer(/article/*)"/>
+ </simplesect>
+ <simplesect>
+ <title>Version 0.7.1</title>
+ <xi:include
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="release-notes-0.7.1.xsl"
+ xpointer="xpointer(/article/*)"/>
+ </simplesect>
</appendix>
</book>
-<!-- LocalWords: Altusmetrum
--->
+<!-- LocalWords: Altusmetrum
+-->
\ No newline at end of file
</para>
<itemizedlist>
<listitem>
+<para>
Receive and log telemetry from a connected TeleDongle
device. All data received is saved to log files named with the
current date and the connected rocket serial and flight
numbers. There is no mode in which telemetry data will not be
saved.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Download logged data from TeleMetrum devices, either through a
direct USB connection or over the air through a TeleDongle
device.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Configure a TeleMetrum device, setting the radio channel,
callsign, apogee delay and main deploy height. This can be done
through either a USB connection or over a radio link via a
TeleDongle device.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Replay a flight in real-time. This takes a saved telemetry log
or eeprom download and replays it through the user interface so
you can relive your favorite rocket flights.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Reprogram Altus Metrum devices. Using an Altus Metrum device
connected via USB, another Altus Metrum device can be
reprogrammed using the supplied programming cable between the
two devices.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Export Flight data to a comma-separated-values file. This takes
either telemetry or on-board flight data and generates data
suitable for use in external applications. All data is exported
using standard units so that no device-specific knowledge is
needed to handle the data.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Speak to you during the flight. Instead of spending the flight
hunched over your laptop looking at the screen, enjoy the view
while the computer tells you what’s going on up there. During
range information to try and help you find your rocket in the
air. Once on the ground, the direction and distance are
reported.
- </listitem>
+ </para>
+</listitem>
</itemizedlist>
</article>
</para>
<itemizedlist>
<listitem>
+<para>
Post-flight graphing tool. This lets you explore the behaviour
of your rocket after flight with a scroll-able and zoom-able
chart showing the altitude, speed and acceleration of the
airframe along with events recorded by the flight computer. You
can export graphs to PNG files, or print them directly.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Real-time moving map which overlays the in-progress flight on
satellite imagery fetched from Google Maps. This lets you see in
pictures where your rocket has landed, allowing you to plan
recovery activities more accurately.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Wireless recovery system testing. Prep your rocket for flight
and test fire the deployment charges to make sure things work as
expected. All without threading wires through holes in your
airframe.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Optimized flight status displays. Each flight state now has it's
own custom 'tab' in the flight monitoring window so you can
focus on the most important details. Pre-flight, the system
they're all green and your rocket is ready for flight. There are
also tabs for ascent, descent and landing along with the
original tabular view of the data.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Monitor multiple flights simultaneously. If you have more than
one TeleDongle, you can monitor a flight with each one on the
same computer.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Automatic flight monitoring at startup. Plug TeleDongle into the
machine before starting AltosUI and it will automatically
connect to it and prepare to monitor a flight.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Exports Google Earth flight tracks. Using the Keyhole Markup
Language (.kml) file format, this provides a 3D view of your
rocket flight through the Google Earth program.
- </listitem>
+ </para>
+</listitem>
</itemizedlist>
</article>
</para>
<itemizedlist>
<listitem>
+<para>
Fix plotting problems due to missing file in the Mac OS install image.
+</para>
</listitem>
<listitem>
+<para>
Always read whole eeprom blocks, mark empty records invalid, display parsing errors to user.
+</para>
</listitem>
<listitem>
+ <para>
Add software version to Configure AltosUI dialog
+</para>
</listitem>
</itemizedlist>
</article>
</para>
<itemizedlist>
<listitem>
+ <para>
Support for TeleMetrum v1.1 hardware. Sources for the flash
memory part used in v1.0 dried up, so v1.1 uses a different part
which required a new driver and support for explicit flight log
erasing.
+</para>
</listitem>
<listitem>
+ <para>
Multiple flight log support. This stores more than one flight
log in the on-board flash memory. It also requires the user to
explicitly erase flights so that you won't lose flight logs just
because you fly the same board twice in one day.
+</para>
</listitem>
<listitem>
+ <para>
Telemetry support for devices with serial number >=
256. Previous versions used a telemetry packet format that
provided only 8 bits for the device serial number. This change
requires that both ends of the telemetry link be running the 0.9
firmware or they will not communicate.
+</para>
</listitem>
</itemizedlist>
</article>
AltOS Firmware Changes
<itemizedlist>
<listitem>
+<para>
Add TeleMini v1.0 support. Firmware images for TeleMini are
included in AltOS releases.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Change telemetry to be encoded in multiple 32-byte packets. This
enables support for TeleMini and other devices without requiring
further updates to the TeleDongle firmware.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Support operation of TeleMetrum with the antenna pointing
aft. Previous firmware versions required the antenna to be
pointing upwards, now there is a configuration option allowing
the antenna to point aft, to aid installation in some airframes.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Ability to disable telemetry. For airframes where an antenna
just isn't possible, or where radio transmissions might cause
trouble with other electronics, there's a configuration option
to disable all telemetry. Note that the board will still
enable the radio link in idle mode.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Arbitrary frequency selection. The radios in Altus Metrum
devices can be programmed to a wide range of frequencies, so
instead of limiting devices to 10 pre-selected 'channels', the
70cm band. Note that the RF matching circuit on the boards is
tuned for around 435MHz, so frequencies far from that may
reduce the available range.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Kalman-filter based flight-tracking. The model based sensor
fusion approach of a Kalman filter means that AltOS now
computes apogee much more accurately than before, generally
allows the baro-only TeleMini device to correctly identify
Mach transitions, avoiding the error-prone selection of a Mach
delay.
- </listitem>
+ </para>
+</listitem>
</itemizedlist>
</para>
<para>
AltosUI Changes
<itemizedlist>
<listitem>
+<para>
Wait for altimeter when using packet mode. Instead of quicly
timing out when trying to initialize a packet mode
configuration connection, AltosUI now waits indefinitely for
the remote device to appear, providing a cancel button should
the user get bored. This is necessary as the TeleMini can only
be placed in "Idle" mode if AltosUI is polling it.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Add main/apogee voltage graphs to the data plot. This provides
a visual indication if the igniters fail before being fired.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Scan for altimeter devices by watching the defined telemetry
frequencies. This avoids the problem of remembering what
frequency a device was configured to use, which is especially
important with TeleMini which does not include a USB connection.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Monitor altimeter state in "Idle" mode. This provides much of
the information presented in the "Pad" dialog from the Monitor
Flight command, monitoring the igniters, battery and GPS
status withing requiring the flight computer to be armed and
ready for flight.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Pre-load map images from home. For those launch sites which
don't provide free Wi-Fi, this allows you to download the
necessary satellite images given the location of the launch
you've got a launch site not on that list, please send the
name of it, latitude and longitude along with a link to the
web site of the controlling club to the altusmetrum mailing list.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Flight statistics are now displayed in the Graph data
window. These include max height/speed/accel, average descent
rates and a few other bits of information. The Graph Data
window can now be reached from the 'Landed' tab in the Monitor
Flight window so you can immediately see the results of a
flight.
- </listitem>
+ </para>
+</listitem>
</itemizedlist>
</para>
</article>
AltOS Firmware Changes
<itemizedlist>
<listitem>
+<para>
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
configuration values. This bug doesn't affect newer TeleMetrum
boards, and it doesn't affect the safety of rockets flying
version 1.1 firmware.
- </listitem>
+ </para>
+</listitem>
</itemizedlist>
</para>
<para>
AltosUI Changes
<itemizedlist>
<listitem>
+<para>
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.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
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.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
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
eventually land. A new “Ground Distance” field has been added
which displays the distance to a spot right underneath the
rocket.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
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.
- </listitem>
+ </para>
+</listitem>
</itemizedlist>
</para>
</article>
AltOS Firmware Changes
<itemizedlist>
<listitem>
+<para>
Add apogee-lockout value. Overrides the apogee detection logic to
prevent incorrect apogee charge firing.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Fix a bug where the data reported in telemetry packets was
from 320ms ago.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Force the radio frequency to 434.550MHz when the debug clock
pin is connected to ground at boot time. This provides a way
to talk to a TeleMini which is configured to some unknown frequency.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Provide RSSI values for Monitor Idle mode. This makes it easy to check radio
range without needing to go to flight mode.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Fix a bug which caused the old received telemetry packets to
be retransmitted over the USB link when the radio was turned
off and back on.
- </listitem>
+ </para>
+</listitem>
</itemizedlist>
</para>
<para>
AltosUI Changes
<itemizedlist>
<listitem>
+<para>
Fix a bug that caused GPS ready to happen too quickly. The
software was using every telemetry packet to signal new GPS
data, which caused GPS ready to be signalled after 10 packets
instead of 10 GPS updates.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Fix Google Earth data export to work with recent versions. The
google earth file loading code got a lot pickier, requiring
some minor white space changes in the export code.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Make the look-n-feel configurable, providing a choice from
the available options.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Add an 'Age' element to mark how long since a telemetry packet
has been received. Useful to quickly gauge whether
communications with the rocket are still active.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Add 'Configure Ground Station' dialog to set the radio
frequency used by a particular TeleDongle without having to go
through the flight monitor UI.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Add configuration for the new apogee-lockout value. A menu provides a list of
reasonable values, or the value can be set by hand.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Changed how flight data are downloaded. Now there's an initial
dialog asking which flights to download, and after that
finishes, a second dialog comes up asking which flights to delete.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Re-compute time spent in each state for the flight graph; this
figures out the actual boost and landing times instead of
using the conservative values provide by the flight
electronics. This improves the accuracy of the boost
acceleration and main descent rate computations.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Make AltosUI run on Mac OS Lion. The default Java heap space
was dramatically reduced for this release causing much of the
UI to fail randomly. This most often affected the satellite
mapping download and displays.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Change how data are displayed in the 'table' tab of the flight
monitoring window. This eliminates entries duplicated from the
header and adds both current altitude and pad altitude, which
are useful in 'Monitor Idle' mode.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Add Imperial units mode to present data in feet instead of
meters.
- </listitem>
+ </para>
+</listitem>
</itemizedlist>
</para>
</article>
AltOS Firmware Changes
<itemizedlist>
<listitem>
+<para>
Add support for TeleBT
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
In TeleMini recovery mode (when booted with the outer two
debug pins connected together), the radio parameters are also
set back to defaults (434.550MHz, N0CALL, factory radio cal).
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Add support for reflashing the SkyTraq GPS chips. This
requires special host-side code which currently only exists
for Linux.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Correct Kalman filter model error covariance matrix. The
values used previously assumed continuous measurements instead
of discrete measurements.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Fix some bugs in the USB driver for TeleMetrum and TeleDongle
that affected Windows users.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Adjusted the automatic gain control parameters that affect
receive performance for TeleDongle. Field tests indicate that this
may improve receive performance somewhat.
- </listitem>
+ </para>
+</listitem>
</itemizedlist>
</para>
<para>
AltosUI Changes
<itemizedlist>
<listitem>
+<para>
Handle missing GPS lock in 'Descent' tab. Previously, if the
GPS position of the pad was unknown, an exception would be
raised, breaking the Descent tab contents.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Improve the graph, adding tool-tips to show values near the
cursor and making the displayed set of values configurable,
adding all of the flight data as options while leaving the
default settings alone so that the graph starts by showing
height, speed and acceleration.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Make the initial position of the AltosUI top level window
configurable. Along with this change, the other windows will
pop up at 'sensible' places now, instead of on top of one
another.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Add callsign to Monitor idle window and connecting
dialogs. This makes it clear which callsign is being used so
that the operator will be aware that it must match the flight
computer value or no communication will work.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
When downloading flight data, display the block number so that
the user has some sense of progress. Unfortunately, we don't
know how many blocks will need to be downloaded, but at least
it isn't just sitting there doing nothing for a long time.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Add GPS data and a map to the graph window. This lets you see
a complete summary of the flight without needing to 'replay'
the whole thing.
- </listitem>
+ </para>
+</listitem>
</itemizedlist>
</para>
</article>
AltOS Firmware Changes
<itemizedlist>
<listitem>
+<para>
Add MicroPeak support. This includes support for the ATtiny85
processor and adaptations to the core code to allow for
devices too small to run the multi-tasking scheduler.
- </listitem>
+ </para>
+</listitem>
</itemizedlist>
</para>
<para>
MicroPeak UI changes
<itemizedlist>
<listitem>
+<para>
Added this new application
- </listitem>
+ </para>
+</listitem>
</itemizedlist>
</para>
<para>
Distribution Changes
<itemizedlist>
<listitem>
+<para>
Distribute Mac OS X packages in disk image ('.dmg') format to
greatly simplify installation.
- </listitem>
+ </para>
+</listitem>
<listitem>
+<para>
Provide version numbers for the shared Java libraries to
ensure that upgrades work properly, and to allow for multiple
Altus Metrum software packages to be installed in the same
directory at the same time.
- </listitem>
+ </para>
+</listitem>
</itemizedlist>
</para>
</article>
AltOS Firmware Changes
<itemizedlist>
<listitem>
- Add STM32L processor support. This includes enhancements to
- the scheduler to support products with many threads.
+ <para>
+ Add STM32L processor support. This includes enhancements to
+ the scheduler to support products with many threads.
+ </para>
</listitem>
<listitem>
- Add NXP LPC11U14 processor support.
+ <para>
+ Add NXP LPC11U14 processor support.
+ </para>
</listitem>
<listitem>
- Support additional pyro channels. These are configurable
- through the UI to handle air starts, staging, additional
- recovery events and external devices such as cameras.
+ <para>
+ Support additional pyro channels. These are configurable
+ through the UI to handle air starts, staging, additional
+ recovery events and external devices such as cameras.
+ </para>
</listitem>
<listitem>
- Add 3-axis gyro support for orientation tracking. This
- integrates the gyros to compute the angle from vertical during
- flight, allowing the additional pyro events to be controlled
- by this value.
+ <para>
+ Add 3-axis gyro support for orientation tracking. This
+ integrates the gyros to compute the angle from vertical during
+ flight, allowing the additional pyro events to be controlled
+ by this value.
+ </para>
</listitem>
<listitem>
- Many more device drivers, including u-Blox Max 7Q GPS,
- Freescale MMA6555 digital single-axis accelerometer,
- Invensense MPU6000 3-axis accelerometer + 3 axis gyro,
- Honeywell HMC5883 3-axis magnetic sensor and the TI CC1120 and
- CC115L digital FM transceivers
+ <para>
+ Many more device drivers, including u-Blox Max 7Q GPS,
+ Freescale MMA6555 digital single-axis accelerometer,
+ Invensense MPU6000 3-axis accelerometer + 3 axis gyro,
+ Honeywell HMC5883 3-axis magnetic sensor and the TI CC1120 and
+ CC115L digital FM transceivers
+ </para>
</listitem>
</itemizedlist>
</para>
AltosUI changes
<itemizedlist>
<listitem>
- Support TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini telemetry and log formats.
+ <para>
+ Support TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini telemetry and log formats.
+ </para>
</listitem>
<listitem>
- Use preferred units for main deployment height configuration,
- instead of always doing configuration in meters.
+ <para>
+ Use preferred units for main deployment height configuration,
+ instead of always doing configuration in meters.
+ </para>
</listitem>
</itemizedlist>
</para>
MicroPeak UI changes
<itemizedlist>
<listitem>
- Add 'Download' button to menu bar.
+ <para>
+ Add 'Download' button to menu bar.
+ </para>
</listitem>
<listitem>
- Save the last log directory and offer that as the default for new downloads
+ <para>
+ Save the last log directory and offer that as the default for new downloads
+ </para>
</listitem>
</itemizedlist>
</para>
projects / fw / altos / commitdiff