X-Git-Url: https://git.gag.com/?p=fw%2Faltos;a=blobdiff_plain;f=doc%2Faltusmetrum.xsl;h=25f245936c51a3d27f3f19dec6c9a9173c0279af;hp=d90f331c22855d097b5c9d34d63ad39757248635;hb=26c4cc3054b1c7c9ed6ce3c2f21f6254b3245718;hpb=e840b6594b8a939f148fa7231e1b06a280d94074
diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl
index d90f331c..25f24593 100644
--- a/doc/altusmetrum.xsl
+++ b/doc/altusmetrum.xsl
@@ -22,7 +22,7 @@
Towns
- 2010
+ 2011
Bdale Garbee and Keith Packard
@@ -34,6 +34,17 @@
license.
+
+
+ 0.9
+ 18 January 2011
+
+ Updated for software version 0.9. Note that 0.9 represents a
+ telemetry format change, meaning both ends of a link (TeleMetrum and
+ TeleDongle) must be updated or communications will fail.
+
+
+
0.8
@@ -373,8 +384,8 @@ NAR #88757, TRA #12200
- Uses LiPo to fire e-matches, support for optional separate pyro
- battery if needed.
+ Uses LiPo to fire e-matches, can be modiied to support
+ optional separate pyro battery if needed.
@@ -449,11 +460,10 @@ NAR #88757, TRA #12200
to fire ejection charges. This works marvelously with standard
low-current e-matches like the J-Tek from MJG Technologies, and with
Quest Q2G2 igniters. However, if you
- want or need to use a separate pyro battery, you can do so by adding
- a second 2mm connector to position B2 on the board and cutting the
- thick pcb trace connecting the LiPo battery to the pyro circuit between
- the two silk screen marks on the surface mount side of the board shown
- here [insert photo]
+ want or need to use a separate pyro battery, the board can be factory
+ modified to do so. This involves cutting two traces and adding a jumper
+ in a densely populated part of the board on TeleMetrum v1.0 and v1.1,
+ along with installation of a pyro battery connector at location B2.
We offer two choices of pyro and power switch connector, or you can
@@ -973,7 +983,7 @@ NAR #88757, TRA #12200
Packet Command Mode
Controlling TeleMetrum Over The Radio Link
- One of the unique features of the Altos Metrum environment is
+ One of the unique features of the Altus Metrum environment is
the ability to create a two way command link between TeleDongle
and TeleMetrum using the digital radio transceivers built into
each device. This allows you to interact with TeleMetrum from
@@ -1290,9 +1300,20 @@ NAR #88757, TRA #12200
on Packet Command Mode for more information about this.
- The filename for the data is computed automatically from the recorded
- flight date, TeleMetrum serial number and flight number
- information.
+ After the device has been selected, a dialog showing the
+ flight data saved in the device will be shown allowing you to
+ select which flights to download and which to delete. With
+ version 0.9 or newer firmware, you must erase flights in order
+ for the space they consume to be reused by another
+ flight. This prevents you from accidentally losing flight data
+ if you neglect to download data before flying again. Note that
+ if there is no more space available in the device, then no
+ data will be recorded for a flight.
+
+
+ The filename for each flight log is computed automatically
+ from the recorded flight date, TeleMetrum serial number and
+ flight number information.
@@ -1477,6 +1498,35 @@ NAR #88757, TRA #12200
as needed to conform to your local radio regulations.
+
+ Maximum Flight Log Size
+
+ This sets the space (in kilobytes) allocated for each flight
+ log. The available space will be divided into chunks of this
+ size. A smaller value will allow more flights to be stored,
+ a larger value will record data from longer flights.
+
+
+ During ascent, TeleMetrum records barometer and
+ accelerometer values 100 times per second, other analog
+ information (voltages and temperature) 6 times per second
+ and GPS data once per second. During descent, the non-GPS
+ data is recorded 1/10th as often. Each barometer +
+ accelerometer record takes 8 bytes.
+
+
+ The default, 192kB, will store over 200 seconds of data at
+ the ascent rate, or over 2000 seconds of data at the descent
+ rate. That's plenty for most flights. This leaves enough
+ storage for five flights in a 1MB system, or 10 flights in a
+ 2MB system.
+
+
+ The configuration block takes the last available block of
+ memory, on v1.0 boards that's just 256 bytes. However, the
+ flash part on the v1.1 boards uses 64kB for each block.
+
+
Configure AltosUI
@@ -1528,6 +1578,16 @@ NAR #88757, TRA #12200
your local radio regulations.
+
+ Serial Debug
+
+ This causes all communication with a connected device to be
+ dumped to the console from which AltosUI was started. If
+ you've started it from an icon or menu entry, the output
+ will simply be discarded. This mode can be useful to debug
+ various serial communication issues.
+
+