programming).
endif::telemetrum,telemini[]
ifdef::telemega,easymega,telemetrum[]
- TeleMega, EasyMega, TeleMetrum v2,
- EasyMini and TeleDongle v3 are all
+ TeleMega, EasyMega, TeleMetrum v2 or newer,
+ EasyMini, TeleBT v3 or newer and TeleDongle v3
+ or newer are all
endif::telemega,easymega,telemetrum[]
ifndef::telemega,easymega,telemetrum[]
EasyMini is
transmission is disabled.
ifdef::altusmetrum[]
This option is
- available on TeleMetrum v2 and TeleMega
+ available on TeleMetrum v2 or newer and TeleMega
boards. TeleMetrum v1 boards cannot transmit
APRS packets.
endif::altusmetrum[]
|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
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.
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.
to trickle charge. It can take several hours to fully recharge a
deeply discharged battery.
- TeleMetrum v2.0, TeleMega and EasyMega use a higher power battery charger,
- allowing them to charge the battery while running the board at
- maximum power. When the battery is charging, or when the board
- is consuming a lot of power, the red LED will be lit. When the
- battery is fully charged, the green LED will be lit. When the
- battery is damaged or missing, both LEDs will be lit, which
- appears yellow.
+ TeleMetrum v2 or newer, TeleMega and EasyMega use a
+ higher power battery charger, allowing them to charge
+ the battery while running the board at maximum
+ power. When the battery is charging, or when the board
+ is consuming a lot of power, the red LED will be
+ lit. When the battery is fully charged, the green LED
+ will be lit. When the battery is damaged or missing,
+ both LEDs will be lit, which appears yellow.
====
endif::telemetrum,telemega,easymega[]
The first device created for our community was TeleMetrum, a dual
deploy altimeter with fully integrated GPS and radio telemetry
as standard features, and a “companion interface” that will
- support optional capabilities in the future. The latest version
- of TeleMetrum, v2.0, has all of the same features but with
+ support optional capabilities in the future. The later versions
+ of TeleMetrum, v2 and newer, have all of the same features but with
improved sensors and radio to offer increased performance.
Our second device was TeleMini, a dual deploy altimeter with
|40mW
|3.7V
+ |TeleMetrum v3.0
+ |MS5607 30km (100k')
+ |ADXL375 200g
+ |uBlox Max-8Q
+ |-
+ |8MB
+ |40mW
+ |3.7V
+
endif::telemetrum[]
ifdef::telemini[]
|TeleMini v1.0
endif::radio[]
ifdef::gps+radio[]
- :aprsdevices: TeleMetrum v2.0 and TeleMega
+ :aprsdevices: TeleMetrum v2 and newer and TeleMega
:configure_section: _configure_altimeter
include::aprs-operation.adoc[]
endif::gps+radio[]
bay for TeleMetrum should have at least 10 inches of interior length.
There are two generations of the TeleMetrum design. The
- major changes in the v2 generation are:
+ major changes after v1 generation are:
* uBlox GPS chip certified for altitude records
|32
|====
- === TeleMetrum v2 Sensor Data
+ === TeleMetrum v2 and newer Sensor Data
.TeleMetrum v2 Packet Type
[options="border",cols="1,3"]
|0x0B |TeleMetrum v2 Calibration Data
|====
- TeleMetrum v2 has higher resolution barometric data than
+ TeleMetrum v2 and newer have higher resolution barometric data than
TeleMetrum v1, and so the constant calibration data is
split out into a separate packet.
- TeleMetrum v2 Sensor Data packets are transmitted once per second on the
+ TeleMetrum v2 and newer Sensor Data packets are transmitted once per second on the
ground, 10 times per second during ascent and once per second
during descent and landing
- TeleMetrum v2 Calibration Data packets are always transmitted once per second.
+ TeleMetrum v2 and newer Calibration Data packets are always transmitted once per second.
- .TeleMetrum v2 Sensor Packet Contents
+ .TeleMetrum v2 and newer Sensor Packet Contents
[options="border",cols="2,3,3,9"]
|====
|Offset |Data Type |Name |Description
|32
|====
- .TeleMetrum v2 Calibration Data Packet Contents
+ .TeleMetrum v2 and newer Calibration Data Packet Contents
[options="border",cols="2,3,3,9"]
|====
|Offset |Data Type |Name |Description
|CC1111
|10mW transceiver with integrated SoC
- |TeleDongle v0.2, TeleBT v1.0, TeleMetrum v1.x, TeleMini
+ |TeleDongle v0.2, TeleBT v1.0, TeleMetrum v1.x, TeleMini v1
|CC1120
|35mW transceiver with SW FEC
- |TeleMetrum v2, TeleMega
+ |TeleMetrum v2, TeleMega v1
|CC1200
|35mW transceiver with HW FEC
- |TeleDongle v3.0, TeleBT v3.0
+ |TeleMetrum v3, TeleMega v2, TeleDongle v3.0, TeleMini v3, TeleBT v3.0, TeleGPS v2
|CC115L
|14mW transmitter with SW FEC
- |TeleGPS
+ |TeleGPS v1
|====
== Updating Device Firmware
ifdef::telemega[]
- TeleMega, TeleMetrum v2, EasyMega, EasyMini and TeleDongle v3
+ TeleMega, TeleMetrum v2 and newer, EasyMega, EasyMini and TeleDongle v3
are all
endif::telemega[]
ifndef::telemega[]
ifdef::telemega[]
- === Updating TeleMega, TeleMetrum v2, EasyMega, EasyMini or TeleDongle v3 Firmware
+ === Updating TeleMega, TeleMetrum v2 or newer, EasyMega, EasyMini, TeleDongle v3 or TeleBT v3 Firmware
endif::telemega[]
ifndef::telemega[]
endif::easymega[]
ifdef::telemetrum[]
- TeleMetrum v2::
+ TeleMetrum v2 and newer::
Connect pin 6 and pin 1 of the companion
connector. Pin 1 can be identified by the square pad
projects / fw / altos / commitdiff