X-Git-Url: https://git.gag.com/?a=blobdiff_plain;f=doc%2Faltusmetrum.xsl;h=5c18fec35bb26f1e3e0eaa29386d27ab97cd6c24;hb=d8ebb83e64d66fa159e75aa560d39d80bb6d9d04;hp=66c2b339feb24013633c2b0a0fb614d11e80d923;hpb=1bd781da934c738e0c9294197c7eb622b0710a9a;p=fw%2Faltos
diff --git a/doc/altusmetrum.xsl b/doc/altusmetrum.xsl
index 66c2b339..5c18fec3 100644
--- a/doc/altusmetrum.xsl
+++ b/doc/altusmetrum.xsl
@@ -536,7 +536,7 @@ NAR #88757, TRA #12200
or radio link via TeleDongle.
- Radio Frequencies
+ Radio Frequency
Altus Metrum boards support radio frequencies in the 70cm
band. By default, the configuration interface provides a
@@ -583,6 +583,90 @@ NAR #88757, TRA #12200
simultaneously.
+
+ Maximum Flight Log
+
+ TeleMetrum version 1.1 and 1.2 have 2MB of on-board flash storage,
+ enough to hold over 40 minutes of data at full data rate
+ (100 samples/second). TeleMetrum 1.0 has 1MB of on-board
+ storage. As data are stored at a reduced rate during descent
+ (10 samples/second), there's plenty of space to store many
+ flights worth of data.
+
+
+ The on-board flash is partitioned into separate flight logs,
+ each of a fixed maximum size. Increase the maximum size of
+ each log and you reduce the number of flights that can be
+ stored. Decrease the size and TeleMetrum can store more
+ flights.
+
+
+ All of the configuration data is also stored in the flash
+ memory, which consumes 64kB on TeleMetrum v1.1/v1.2 and 256B on
+ TeleMetrum v1.0. This configuration space is not available
+ for storing flight log data.
+
+
+ To compute the amount of space needed for a single flight,
+ you can multiply the expected ascent time (in seconds) by
+ 800, multiply the expected descent time (in seconds) by 80
+ and add the two together. That will slightly under-estimate
+ the storage (in bytes) needed for the flight. For instance,
+ a flight spending 20 seconds in ascent and 150 seconds in
+ descent will take about (20 * 800) + (150 * 80) = 28000
+ bytes of storage. You could store dozens of these flights in
+ the on-board flash.
+
+
+ The default size, 192kB, allows for 10 flights of storage on
+ TeleMetrum v1.1/v1.2 and 5 flights on TeleMetrum v1.0. This
+ ensures that you won't need to erase the memory before
+ flying each time while still allowing more than sufficient
+ storage for each flight.
+
+
+ As TeleMini does not contain an accelerometer, it stores
+ data at 10 samples per second during ascent and one sample
+ per second during descent. Each sample is a two byte reading
+ from the barometer. These are stored in 5kB of
+ on-chip flash memory which can hold 256 seconds at the
+ ascent rate or 2560 seconds at the descent rate. Because of
+ the limited storage, TeleMini cannot hold data for more than
+ one flight, and so must be erased after each flight or it
+ will not capture data for subsequent flights.
+
+
+
+ Ignite Mode
+
+ Instead of firing one charge at apogee and another charge at
+ a fixed height above the ground, you can configure the
+ altimeter to fire both at apogee or both during
+ descent. This was added to support an airframe that has two
+ TeleMetrum computers, one in the fin can and one in the
+ nose.
+
+
+ Providing the ability to use both igniters for apogee or
+ main allows some level of redundancy without needing two
+ flight computers. In Redundant Apogee or Redundant Main
+ mode, the two charges will be fired two seconds apart.
+
+
+
+ Pad Orientation
+
+ TeleMetrum measures acceleration along the axis of the
+ board. Which way the board is oriented affects the sign of
+ the acceleration value. Instead of trying to guess which way
+ the board is mounted in the air frame, TeleMetrum must be
+ explicitly configured for either Antenna Up or Antenna
+ Down. The default, Antenna Up, expects the end of the
+ TeleMetrum board connected to the 70cm antenna to be nearest
+ the nose of the rocket, with the end containing the screw
+ terminals nearest the tail.
+
+
@@ -1093,31 +1177,6 @@ NAR #88757, TRA #12200
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 1MB systems, or 10 flights in 2MB
- systems.
-
-
- 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.
-
-
- TeleMini has 5kB of on-board storage, which is plenty for a
- single flight. Make sure you download and delete the data
- before subsequent flights, or TeleMini will not log any data.
-
Ignite Mode
@@ -1783,7 +1842,7 @@ NAR #88757, TRA #12200
Select the image you want put on the TeleMetrum, which should have a
- name in the form telemetrum-v1.1-1.0.0.ihx. It should be visible
+ 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.
@@ -2421,7 +2480,7 @@ NAR #88757, TRA #12200
Release Notes
-
+