doc: Update docs to reference TeleMetrum v3 where appropriate

[fw/altos] / doc / flight-data-recording.inc

diff --git a/doc/flight-data-recording.inc b/doc/flight-data-recording.inc
index 32e44840fc86bbd9a7ad2e3292e6670c794f0910..af79d532d05608bbd65bc27b0cd21c7f16c0f514 100644 (file)
--- a/doc/flight-data-recording.inc
+++ b/doc/flight-data-recording.inc
@@ -22,9 +22,11 @@
        |TeleMetrum v1.0        |8      |1MB    |20
        |TeleMetrum v1.1 v1.2   |8      |2MB    |40
        |TeleMetrum v2.0        |16     |8MB    |80
+       |TeleMetrum v3.0        |16     |8MB    |80
        endif::telemetrum[]
        ifdef::telemini[]
        |TeleMini v1.0          |2      |5kB    |4
+       |TeleMini v3.0          |16     |512kB  |5
        endif::telemini[]
        ifdef::easymini[]
        |EasyMini               |16     |1MB    |10
@@ -44,14 +46,14 @@
             
        Configuration data is also stored in the flash memory on
        ifdef::telemetrum[TeleMetrum v1.x,]
-       ifdef::telemini[TeleMini and]
+       ifdef::telemini[TeleMini v3.0 and]
        ifdef::easymini[EasyMini.]
        This consumes 64kB
        of flash space.  This configuration space is not available
        for storing flight log data.
 
        ifdef::telemetrum,telemega,easymega[]
-       TeleMetrum v2.0, TeleMega and EasyMega
+       TeleMetrum v2 or newer, TeleMega and EasyMega
        store configuration data in a bit of eeprom available within
        the processor chip, leaving that space available in flash for
        more flight data.
@@ -64,7 +66,7 @@
        together. That will slightly under-estimate the storage (in
        bytes) needed for the flight.
        ifdef::telemetrum[]
-       For instance, a TeleMetrum v2.0 flight spending
+       For instance, a TeleMetrum v2 or newer flight spending
        20 seconds in ascent and 150 seconds in descent will take
        about (20 * 1600) + (150 * 160) = 56000 bytes of storage. You
        could store dozens of these flights in the on-board flash.