<surname>Towns</surname>
</author>
<copyright>
- <year>2010</year>
+ <year>2011</year>
<holder>Bdale Garbee and Keith Packard</holder>
</copyright>
<legalnotice>
license.
</para>
</legalnotice>
+ <revhistory>
+ <revision>
+ <revnumber>0.9</revnumber>
+ <date>18 January 2011</date>
+ <revremark>
+ 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.
+ </revremark>
+ </revision>
+ </revhistory>
<revhistory>
<revision>
<revnumber>0.8</revnumber>
</listitem>
<listitem>
<para>
- 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.
</para>
</listitem>
<listitem>
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.
</para>
<para>
We offer two choices of pyro and power switch connector, or you can
<title>Packet Command Mode</title>
<subtitle>Controlling TeleMetrum Over The Radio Link</subtitle>
<para>
- 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
on Packet Command Mode for more information about this.
</para>
<para>
- 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.
+ </para>
+ <para>
+ The filename for each flight log is computed automatically
+ from the recorded flight date, TeleMetrum serial number and
+ flight number information.
</para>
</section>
<section>
as needed to conform to your local radio regulations.
</para>
</section>
+ <section>
+ <title>Maximum Flight Log Size</title>
+ <para>
+ 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.
+ </para>
+ <para>
+ 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.
+ </para>
+ <para>
+ 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.
+ </para>
+ <para>
+ 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.
+ </para>
+ </section>
</section>
<section>
<title>Configure AltosUI</title>
your local radio regulations.
</para>
</section>
+ <section>
+ <title>Serial Debug</title>
+ <para>
+ 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.
+ </para>
+ </section>
</section>
<section>
<title>Flash Image</title>
other authorization to legally operate the radio transmitters that are part
of our products.
</para>
+ </section>
<section>
<title>In the Rocket</title>
<para>
feel free to dive in and help! Or let us know what you'd like to see that
we aren't already working on, and maybe we'll get excited about it too...
</para>
- </section>
</section>
</chapter>
</book>
projects / fw / altos / blobdiff