From ca803b4be4627bdd1dc1f225ea16f610855f3dea Mon Sep 17 00:00:00 2001 From: Bdale Garbee Date: Thu, 16 Jul 2015 14:46:05 -0600 Subject: update docs --- AltOS/doc/altusmetrum.html | 802 ++++++++++++++++++++++++++++++--------------- 1 file changed, 531 insertions(+), 271 deletions(-) (limited to 'AltOS/doc/altusmetrum.html') diff --git a/AltOS/doc/altusmetrum.html b/AltOS/doc/altusmetrum.html index bbf73d4..df2f2b3 100644 --- a/AltOS/doc/altusmetrum.html +++ b/AltOS/doc/altusmetrum.html @@ -1,10 +1,12 @@ -The Altus Metrum System

The Altus Metrum System

An Owner's Manual for Altus Metrum Rocketry Electronics

Bdale Garbee

Keith Packard

Bob Finch

Anthony Towns

Copyright © 2015 Bdale Garbee and Keith Packard

+The Altus Metrum System

The Altus Metrum System

An Owner's Manual for Altus Metrum Rocketry Electronics

Bdale Garbee

Keith Packard

Bob Finch

Anthony Towns

Copyright © 2015 Bdale Garbee and Keith Packard

This document is released under the terms of the Creative Commons ShareAlike 3.0 license. -

Revision History
Revision 1.68 January 2015
+

Revision History
Revision 1.6.115 July 2015
+ Minor release adding TeleBT v3.0 support. +
Revision 1.68 January 2015
Major release adding TeleDongle v3.0 support.
Revision 1.56 September 2014
Major release adding EasyMega support. @@ -43,7 +45,7 @@ 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. -
Revision 0.824 November 2010
Updated for software version 0.8

Acknowledgments

+

Revision 0.824 November 2010
Updated for software version 0.8

Acknowledgments

Thanks to Bob Finch, W9YA, NAR 12965, TRA 12350 for writing “The Mere-Mortals Quick Start/Usage Guide to the Altus Metrum Starter Kit” which formed the basis of the original Getting Started chapter @@ -66,22 +68,22 @@ NAR Keith Packard, KD7SQG
NAR #88757, TRA #12200
      

-

Table of Contents

1. Introduction and Overview
2. Getting Started
3. Handling Precautions
4. Altus Metrum Hardware
1. General Usage Instructions
1.1. Hooking Up Lithium Polymer Batteries
1.2. Hooking Up Pyro Charges
1.3. Hooking Up a Power Switch
1.4. Using a Separate Pyro Battery
1.5. Using a Different Kind of Battery
2. Specifications
3. TeleMetrum
3.1. TeleMetrum Screw Terminals
3.2. Using a Separate Pyro Battery with TeleMetrum
3.3. Using an Active Switch with TeleMetrum
4. TeleMini v1.0
4.1. TeleMini v1.0 Screw Terminals
4.2. Using a Separate Pyro Battery with TeleMini v1.0
4.3. Using an Active Switch with TeleMini v1.0
5. TeleMini v2.0
5.1. TeleMini v2.0 Screw Terminals
5.2. Using a Separate Pyro Battery with TeleMini v2.0
5.3. Using an Active Switch with TeleMini v2.0
6. EasyMini
6.1. EasyMini Screw Terminals
6.2. Using a Separate Pyro Battery with EasyMini
6.3. Using an Active Switch with EasyMini
7. TeleMega
7.1. TeleMega Screw Terminals
7.2. Using a Separate Pyro Battery with TeleMega
7.3. Using Only One Battery With TeleMega
7.4. Using an Active Switch with TeleMega
8. EasyMega
8.1. EasyMega Screw Terminals
8.2. Using a Separate Pyro Battery with EasyMega
8.3. Using Only One Battery With EasyMega
8.4. Using an Active Switch with EasyMega
9. Flight Data Recording
10. Installation
5. System Operation
1. Firmware Modes
2. GPS
3. Controlling An Altimeter Over The Radio Link
4. Ground Testing
5. Radio Link
6. APRS
7. Configurable Parameters
7.1. Radio Frequency
7.2. Callsign
7.3. Telemetry/RDF/APRS Enable
7.4. Telemetry baud rate
7.5. APRS Interval
7.6. APRS SSID
7.7. Apogee Delay
7.8. Apogee Lockout
7.9. Main Deployment Altitude
7.10. Maximum Flight Log
7.11. Ignite Mode
7.12. Pad Orientation
7.13. Configurable Pyro Channels
6. AltosUI
1. Monitor Flight
1.1. Launch Pad
1.2. Ascent
1.3. Descent
1.4. Landed
1.5. Table
1.6. Site Map
1.7. Ignitor
2. Save Flight Data
3. Replay Flight
4. Graph Data
4.1. Flight Graph
4.2. Configure Graph
4.3. Flight Statistics
4.4. Map
5. Export Data
5.1. Comma Separated Value Format
5.2. Keyhole Markup Language (for Google Earth)
6. Configure Altimeter
6.1. Main Deploy Altitude
6.2. Apogee Delay
6.3. Apogee Lockoug
6.4. Frequency
6.5. RF Calibration
6.6. Telemetry/RDF/APRS Enable
6.7. Telemetry baud rate
6.8. APRS Interval
6.9. APRS SSID
6.10. Callsign
6.11. Maximum Flight Log Size
6.12. Ignitor Firing Mode
6.13. Pad Orientation
6.14. Beeper Frequency
6.15. Configure Pyro Channels
7. Configure AltosUI
7.1. Voice Settings
7.2. Log Directory
7.3. Callsign
7.4. Imperial Units
7.5. Font Size
7.6. Serial Debug
7.7. Manage Frequencies
8. Configure Groundstation
8.1. Frequency
8.2. RF Calibration
8.3. Telemetry Rate
9. Flash Image
10. Fire Igniter
11. Scan Channels
12. Load Maps
13. Monitor Idle
7. AltosDroid
1. Installing AltosDroid
2. Connecting to TeleBT
3. Configuring AltosDroid
4. AltosDroid Flight Monitoring
4.1. Pad
5. Downloading Flight Logs
8. Using Altus Metrum Products
1. Being Legal
2. In the Rocket
3. On the Ground
4. Data Analysis
5. Future Plans
9. Altimeter Installation Recommendations
1. Mounting the Altimeter
2. Dealing with the Antenna
3. Preserving GPS Reception
4. Radio Frequency Interference
5. The Barometric Sensor
6. Ground Testing
10. Updating Device Firmware
1. +

Table of Contents

1. Introduction and Overview
2. Getting Started
3. Handling Precautions
4. Altus Metrum Hardware
1. General Usage Instructions
1.1. Hooking Up Lithium Polymer Batteries
1.2. Hooking Up Pyro Charges
1.3. Hooking Up a Power Switch
1.4. Using a Separate Pyro Battery
1.5. Using a Different Kind of Battery
2. Specifications
3. TeleMetrum
3.1. TeleMetrum Screw Terminals
3.2. Using a Separate Pyro Battery with TeleMetrum
3.3. Using an Active Switch with TeleMetrum
4. TeleMini v1.0
4.1. TeleMini v1.0 Screw Terminals
4.2. Using a Separate Pyro Battery with TeleMini v1.0
4.3. Using an Active Switch with TeleMini v1.0
5. TeleMini v2.0
5.1. TeleMini v2.0 Screw Terminals
5.2. Using a Separate Pyro Battery with TeleMini v2.0
5.3. Using an Active Switch with TeleMini v2.0
6. EasyMini
6.1. EasyMini Screw Terminals
6.2. Using a Separate Pyro Battery with EasyMini
6.3. Using an Active Switch with EasyMini
7. TeleMega
7.1. TeleMega Screw Terminals
7.2. Using a Separate Pyro Battery with TeleMega
7.3. Using Only One Battery With TeleMega
7.4. Using an Active Switch with TeleMega
8. EasyMega
8.1. EasyMega Screw Terminals
8.2. Using a Separate Pyro Battery with EasyMega
8.3. Using Only One Battery With EasyMega
8.4. Using an Active Switch with EasyMega
9. Flight Data Recording
10. Installation
5. System Operation
1. Firmware Modes
2. GPS
3. Controlling An Altimeter Over The Radio Link
4. Ground Testing
5. Radio Link
6. APRS
7. Configurable Parameters
7.1. Radio Frequency
7.2. Callsign
7.3. Telemetry/RDF/APRS Enable
7.4. Telemetry baud rate
7.5. APRS Interval
7.6. APRS SSID
7.7. Apogee Delay
7.8. Apogee Lockout
7.9. Main Deployment Altitude
7.10. Maximum Flight Log
7.11. Ignite Mode
7.12. Pad Orientation
7.13. Configurable Pyro Channels
6. AltosUI
1. Monitor Flight
1.1. Launch Pad
1.2. Ascent
1.3. Descent
1.4. Landed
1.5. Table
1.6. Site Map
1.7. Ignitor
2. Save Flight Data
3. Replay Flight
4. Graph Data
4.1. Flight Graph
4.2. Configure Graph
4.3. Flight Statistics
4.4. Map
5. Export Data
5.1. Comma Separated Value Format
5.2. Keyhole Markup Language (for Google Earth)
6. Configure Altimeter
6.1. Main Deploy Altitude
6.2. Apogee Delay
6.3. Apogee Lockoug
6.4. Frequency
6.5. RF Calibration
6.6. Telemetry/RDF/APRS Enable
6.7. Telemetry baud rate
6.8. APRS Interval
6.9. APRS SSID
6.10. Callsign
6.11. Maximum Flight Log Size
6.12. Ignitor Firing Mode
6.13. Pad Orientation
6.14. Beeper Frequency
6.15. Configure Pyro Channels
7. Configure AltosUI
7.1. Voice Settings
7.2. Log Directory
7.3. Callsign
7.4. Imperial Units
7.5. Font Size
7.6. Serial Debug
7.7. Manage Frequencies
8. Configure Groundstation
8.1. Frequency
8.2. RF Calibration
8.3. Telemetry Rate
9. Flash Image
10. Fire Igniter
11. Scan Channels
12. Load Maps
13. Monitor Idle
7. AltosDroid
1. Installing AltosDroid
2. Connecting to TeleBT over Bluetooth™
3. Connecting to TeleDongle or TeleBT over USB
4. Configuring AltosDroid
4.1. Select radio frequency
4.2. Select data rate
4.3. Change units
4.4. Load maps
4.5. Map type
4.6. Toggle Online/Offline maps
4.7. Select Tracker
4.8. Delete Track
5. AltosDroid Flight Monitoring
5.1. Pad
5.2. Flight
5.3. Recover
5.4. Map
6. Downloading Flight Logs
8. Using Altus Metrum Products
1. Being Legal
2. In the Rocket
3. On the Ground
4. Data Analysis
5. Future Plans
9. Altimeter Installation Recommendations
1. Mounting the Altimeter
2. Dealing with the Antenna
3. Preserving GPS Reception
4. Radio Frequency Interference
5. The Barometric Sensor
6. Ground Testing
10. Updating Device Firmware
1. Updating TeleMega, TeleMetrum v2, EasyMega, EasyMini or TeleDongle v3 Firmware -
1.1. Recovering From Self-Flashing Failure
2. Pair Programming
3. Updating TeleMetrum v1.x Firmware
4. Updating TeleMini Firmware
5. Updating TeleDongle v0.2 Firmware
11. Hardware Specifications
1. +
1.1. Recovering From Self-Flashing Failure
2. Pair Programming
3. Updating TeleMetrum v1.x Firmware
4. Updating TeleMini Firmware
5. Updating TeleDongle v0.2 Firmware
11. Hardware Specifications
1. TeleMega Specifications -
2. +
2. EasyMega Specifications -
3. +
3. TeleMetrum v2 Specifications -
4. TeleMetrum v1 Specifications
5. +
4. TeleMetrum v1 Specifications
5. TeleMini v2.0 Specifications -
6. +
6. TeleMini v1.0 Specifications -
7. +
7. EasyMini Specifications -
12. FAQ
A. Notes for Older Software
B. Drill Templates
1. TeleMega template
2. EasyMega template
3. TeleMetrum template
4. TeleMini v2/EasyMini template
5. TeleMini v1 template
C. Calibration
1. Radio Frequency
2. TeleMetrum, TeleMega and EasyMega Accelerometers
D. Igniter Current
1. Current Products
2. Version 1 Products
E. Release Notes

List of Tables

4.1. Altus Metrum Electronics
4.2. Altus Metrum Boards
4.3. TeleMetrum Screw Terminals
4.4. TeleMini v1.0 Connections
4.5. TeleMini v2.0 Connections
4.6. EasyMini Connections
4.7. TeleMega Screw Terminals
4.8. EasyMega Screw Terminals
4.9. Data Storage on Altus Metrum altimeters
5.1. AltOS Modes
5.2. Pad/Idle Indications
5.3. Altus Metrum APRS Comments

Chapter 1. Introduction and Overview

+

12. FAQ
A. Notes for Older Software
B. Drill Templates
1. TeleMega template
2. EasyMega template
3. TeleMetrum template
4. TeleMini v2/EasyMini template
5. TeleMini v1 template
C. Calibration
1. Radio Frequency
2. TeleMetrum, TeleMega and EasyMega Accelerometers
D. Igniter Current
1. Current Products
2. Version 1 Products
E. Release Notes

List of Tables

4.1. Altus Metrum Electronics
4.2. Altus Metrum Boards
4.3. TeleMetrum Screw Terminals
4.4. TeleMini v1.0 Connections
4.5. TeleMini v2.0 Connections
4.6. EasyMini Connections
4.7. TeleMega Screw Terminals
4.8. EasyMega Screw Terminals
4.9. Data Storage on Altus Metrum altimeters
5.1. AltOS Modes
5.2. Pad/Idle Indications
5.3. Altus Metrum APRS Comments

Chapter 1. Introduction and Overview

Welcome to the Altus Metrum community! Our circuits and software reflect our passion for both hobby rocketry and Free Software. We hope their capabilities and performance will delight you in every way, but by @@ -134,7 +136,7 @@ NAR More products will be added to the Altus Metrum family over time, and we currently envision that this will be a single, comprehensive manual for the entire product family. -

Chapter 2. Getting Started

+

Chapter 2. Getting Started

The first thing to do after you check the inventory of parts in your “starter kit” is to charge the battery.

@@ -204,7 +206,7 @@ NAR over USB with your laptop computer; it acts exactly like a TeleDongle. Anywhere this manual talks about TeleDongle, you can also read that as 'and TeleBT when connected via USB'. -

Chapter 3. Handling Precautions

+

Chapter 3. Handling Precautions

All Altus Metrum products are sophisticated electronic devices. When handled gently and properly installed in an air-frame, they will deliver impressive results. However, as with all electronic @@ -243,7 +245,7 @@ NAR As with all other rocketry electronics, Altus Metrum altimeters must be protected from exposure to corrosive motor exhaust and ejection charge gasses. -

Chapter 4. Altus Metrum Hardware

Table of Contents

1. General Usage Instructions
1.1. Hooking Up Lithium Polymer Batteries
1.2. Hooking Up Pyro Charges
1.3. Hooking Up a Power Switch
1.4. Using a Separate Pyro Battery
1.5. Using a Different Kind of Battery
2. Specifications
3. TeleMetrum
3.1. TeleMetrum Screw Terminals
3.2. Using a Separate Pyro Battery with TeleMetrum
3.3. Using an Active Switch with TeleMetrum
4. TeleMini v1.0
4.1. TeleMini v1.0 Screw Terminals
4.2. Using a Separate Pyro Battery with TeleMini v1.0
4.3. Using an Active Switch with TeleMini v1.0
5. TeleMini v2.0
5.1. TeleMini v2.0 Screw Terminals
5.2. Using a Separate Pyro Battery with TeleMini v2.0
5.3. Using an Active Switch with TeleMini v2.0
6. EasyMini
6.1. EasyMini Screw Terminals
6.2. Using a Separate Pyro Battery with EasyMini
6.3. Using an Active Switch with EasyMini
7. TeleMega
7.1. TeleMega Screw Terminals
7.2. Using a Separate Pyro Battery with TeleMega
7.3. Using Only One Battery With TeleMega
7.4. Using an Active Switch with TeleMega
8. EasyMega
8.1. EasyMega Screw Terminals
8.2. Using a Separate Pyro Battery with EasyMega
8.3. Using Only One Battery With EasyMega
8.4. Using an Active Switch with EasyMega
9. Flight Data Recording
10. Installation

1. General Usage Instructions

+

Chapter 4. Altus Metrum Hardware

Table of Contents

1. General Usage Instructions
1.1. Hooking Up Lithium Polymer Batteries
1.2. Hooking Up Pyro Charges
1.3. Hooking Up a Power Switch
1.4. Using a Separate Pyro Battery
1.5. Using a Different Kind of Battery
2. Specifications
3. TeleMetrum
3.1. TeleMetrum Screw Terminals
3.2. Using a Separate Pyro Battery with TeleMetrum
3.3. Using an Active Switch with TeleMetrum
4. TeleMini v1.0
4.1. TeleMini v1.0 Screw Terminals
4.2. Using a Separate Pyro Battery with TeleMini v1.0
4.3. Using an Active Switch with TeleMini v1.0
5. TeleMini v2.0
5.1. TeleMini v2.0 Screw Terminals
5.2. Using a Separate Pyro Battery with TeleMini v2.0
5.3. Using an Active Switch with TeleMini v2.0
6. EasyMini
6.1. EasyMini Screw Terminals
6.2. Using a Separate Pyro Battery with EasyMini
6.3. Using an Active Switch with EasyMini
7. TeleMega
7.1. TeleMega Screw Terminals
7.2. Using a Separate Pyro Battery with TeleMega
7.3. Using Only One Battery With TeleMega
7.4. Using an Active Switch with TeleMega
8. EasyMega
8.1. EasyMega Screw Terminals
8.2. Using a Separate Pyro Battery with EasyMega
8.3. Using Only One Battery With EasyMega
8.4. Using an Active Switch with EasyMega
9. Flight Data Recording
10. Installation

1. General Usage Instructions

Here are general instructions for hooking up an Altus Metrum flight computer. Instructions specific to each model will be found in the section devoted to that model below. @@ -253,7 +255,7 @@ NAR twist pairs of wires connected to the board. Twist the switch leads, the pyro leads and the battery leads. This reduces interference through a mechanism called common mode rejection. -

1.1. Hooking Up Lithium Polymer Batteries

+

1.1. Hooking Up Lithium Polymer Batteries

All Altus Metrum flight computers have a two pin JST PH series connector to connect up a single-cell Lithium Polymer cell (3.7V nominal). You can purchase matching batteries @@ -267,7 +269,7 @@ NAR this same connector. All that we have found use the opposite polarity, and if you use them that way, you will damage or destroy the flight computer. -

1.2. Hooking Up Pyro Charges

+

1.2. Hooking Up Pyro Charges

Altus Metrum flight computers always have two screws for each pyro charge. This means you shouldn't need to put two wires into a screw terminal or connect leads from pyro @@ -278,13 +280,13 @@ NAR The other lead is connected through the pyro circuit, which is connected to the negative battery terminal when the pyro circuit is fired. -

1.3. Hooking Up a Power Switch

+

1.3. Hooking Up a Power Switch

Altus Metrum flight computers need an external power switch to turn them on. This disconnects both the computer and the pyro charges from the battery, preventing the charges from firing when in the Off position. The switch is in-line with the positive battery terminal. -

1.3.1. Using an External Active Switch Circuit

+

1.3.1. Using an External Active Switch Circuit

You can use an active switch circuit, such as the Featherweight Magnetic Switch, with any Altus Metrum flight computer. These require three connections, one to @@ -293,7 +295,7 @@ NAR hook these up for each flight computer below. The follow the instructions that come with your active switch to connect it up. -

1.4. Using a Separate Pyro Battery

+

1.4. Using a Separate Pyro Battery

As mentioned above in the section on hooking up pyro charges, one lead for each of the pyro charges is connected through the power switch directly to the positive battery @@ -310,7 +312,7 @@ NAR circuit between the negative pyro terminal and the ground terminal, firing the igniter. Specific instructions on how to hook this up will be found in each section below. -

1.5. Using a Different Kind of Battery

+

1.5. Using a Different Kind of Battery

EasyMini and TeleMini v2 are designed to use either a lithium polymer battery or any other battery producing between 4 and 12 volts, such as a rectangular 9V @@ -318,10 +320,10 @@ NAR and must only be powered by a lithium polymer battery. Find instructions on how to use other batteries in the EasyMini and TeleMini sections below. -

2. Specifications

+

2. Specifications

Here's the full set of Altus Metrum products, both in production and retired. -

Table 4.1. Altus Metrum Electronics

DeviceBarometerZ-axis accelerometerGPS3D sensorsStorageRF OutputBattery
TeleMetrum v1.0

MP3H6115 10km (33k')

MMA2202 50g

SkyTraq-1MB10mW3.7V
TeleMetrum v1.1

MP3H6115 10km (33k')

MMA2202 50g

SkyTraq-2MB10mW3.7V
TeleMetrum v1.2

MP3H6115 10km (33k')

ADXL78 70g

SkyTraq-2MB10mW3.7V
TeleMetrum v2.0

MS5607 30km (100k')

MMA6555 102g

uBlox Max-7Q-8MB40mW3.7V

TeleMini v1.0

MP3H6115 10km (33k')

---5kB10mW3.7V
TeleMini v2.0

MS5607 30km (100k')

---1MB10mW3.7-12V
EasyMini v1.0

MS5607 30km (100k')

---1MB-3.7-12V
TeleMega v1.0

MS5607 30km (100k')

MMA6555 102g

uBlox Max-7Q

MPU6000 HMC5883

8MB40mW3.7V
EasyMega v1.0

MS5607 30km (100k')

MMA6555 102g

-

MPU6000 HMC5883

8MB-3.7V

Table 4.2. Altus Metrum Boards

DeviceConnectorsScrew TerminalsWidthLengthTube Size
TeleMetrum

+

Table 4.1. Altus Metrum Electronics

DeviceBarometerZ-axis accelerometerGPS3D sensorsStorageRF OutputBattery
TeleMetrum v1.0

MP3H6115 10km (33k')

MMA2202 50g

SkyTraq-1MB10mW3.7V
TeleMetrum v1.1

MP3H6115 10km (33k')

MMA2202 50g

SkyTraq-2MB10mW3.7V
TeleMetrum v1.2

MP3H6115 10km (33k')

ADXL78 70g

SkyTraq-2MB10mW3.7V
TeleMetrum v2.0

MS5607 30km (100k')

MMA6555 102g

uBlox Max-7Q-8MB40mW3.7V

TeleMini v1.0

MP3H6115 10km (33k')

---5kB10mW3.7V
TeleMini v2.0

MS5607 30km (100k')

---1MB10mW3.7-12V
EasyMini v1.0

MS5607 30km (100k')

---1MB-3.7-12V
TeleMega v1.0

MS5607 30km (100k')

MMA6555 102g

uBlox Max-7Q

MPU6000 HMC5883

8MB40mW3.7V
EasyMega v1.0

MS5607 30km (100k')

MMA6555 102g

-

MPU6000 HMC5883

8MB-3.7V

Table 4.2. Altus Metrum Boards

DeviceConnectorsScrew TerminalsWidthLengthTube Size
TeleMetrum

Antenna Debug Companion @@ -376,7 +378,7 @@ NAR Pyro A-D Switch Pyro battery -

1¼ inch (3.18cm)2¼ inch (5.62cm)38mm coupler

3. TeleMetrum

+

1¼ inch (3.18cm)2¼ inch (5.62cm)38mm coupler

3. TeleMetrum

TeleMetrum is a 1 inch by 2¾ inch circuit board. It was designed to fit inside coupler for 29mm air-frame tubing, but using it in a tube that small in diameter may require some creativity in mounting and wiring @@ -387,13 +389,13 @@ NAR the e-matches for apogee and main ejection charges depart from the fin can end of the board, meaning an ideal “simple” avionics bay for TeleMetrum should have at least 10 inches of interior length. -

3.1. TeleMetrum Screw Terminals

+

3.1. TeleMetrum Screw Terminals

TeleMetrum has six screw terminals on the end of the board opposite the telemetry antenna. Two are for the power switch, and two each for the apogee and main igniter circuits. Using the picture above and starting from the top, the terminals are as follows: -

Table 4.3. TeleMetrum Screw Terminals

Terminal #Terminal NameDescription
1Switch OutputSwitch connection to flight computer
2Switch InputSwitch connection to positive battery terminal
3Main +Main pyro channel common connection to battery +
4Main -Main pyro channel connection to pyro circuit
5Apogee +Apogee pyro channel common connection to battery +
6Apogee -Apogee pyro channel connection to pyro circuit

3.2. Using a Separate Pyro Battery with TeleMetrum

+

Table 4.3. TeleMetrum Screw Terminals

Terminal #Terminal NameDescription
1Switch OutputSwitch connection to flight computer
2Switch InputSwitch connection to positive battery terminal
3Main +Main pyro channel common connection to battery +
4Main -Main pyro channel connection to pyro circuit
5Apogee +Apogee pyro channel common connection to battery +
6Apogee -Apogee pyro channel connection to pyro circuit

3.2. Using a Separate Pyro Battery with TeleMetrum

As described above, using an external pyro battery involves connecting the negative battery terminal to the flight computer ground, connecting the positive battery terminal to @@ -412,7 +414,7 @@ NAR The other lead from each pyro charge is then inserted into the appropriate per-pyro channel screw terminal (terminal 4 for the Main charge, terminal 6 for the Apogee charge). -

3.3. Using an Active Switch with TeleMetrum

+

3.3. Using an Active Switch with TeleMetrum

As explained above, an external active switch requires three connections, one to the positive battery terminal, one to the flight computer positive input and one to ground. @@ -421,7 +423,7 @@ NAR 2, the positive flight computer input is on terminal 1. To hook a lead to ground, solder a piece of wire, 24 to 28 gauge stranded, to the GND hole just above terminal 1. -

4. TeleMini v1.0

+

4. TeleMini v1.0

TeleMini v1.0 is ½ inches by 1½ inches. It was designed to fit inside an 18mm air-frame tube, but using it in a tube that small in diameter may require some creativity in @@ -434,7 +436,7 @@ NAR apogee and main ejection charges depart from the other end of the board, meaning an ideal “simple” avionics bay for TeleMini should have at least 9 inches of interior length. -

4.1. TeleMini v1.0 Screw Terminals

+

4.1. TeleMini v1.0 Screw Terminals

TeleMini v1.0 has four screw terminals on the end of the board opposite the telemetry antenna. Two are for the apogee and two are for main igniter circuits. There are also wires @@ -442,7 +444,7 @@ NAR picture above and starting from the top for the terminals and from the left for the power switch wires, the connections are as follows: -

Table 4.4. TeleMini v1.0 Connections

Terminal #Terminal NameDescription
1Apogee -Apogee pyro channel connection to pyro circuit
2Apogee +Apogee pyro channel common connection to battery +
3Main -Main pyro channel connection to pyro circuit
4Main +Main pyro channel common connection to battery +
LeftSwitch OutputSwitch connection to flight computer
RightSwitch InputSwitch connection to positive battery terminal

4.2. Using a Separate Pyro Battery with TeleMini v1.0

+

Table 4.4. TeleMini v1.0 Connections

Terminal #Terminal NameDescription
1Apogee -Apogee pyro channel connection to pyro circuit
2Apogee +Apogee pyro channel common connection to battery +
3Main -Main pyro channel connection to pyro circuit
4Main +Main pyro channel common connection to battery +
LeftSwitch OutputSwitch connection to flight computer
RightSwitch InputSwitch connection to positive battery terminal

4.2. Using a Separate Pyro Battery with TeleMini v1.0

As described above, using an external pyro battery involves connecting the negative battery terminal to the flight computer ground, connecting the positive battery terminal to @@ -463,7 +465,7 @@ NAR The other lead from each pyro charge is then inserted into the appropriate per-pyro channel screw terminal (terminal 3 for the Main charge, terminal 1 for the Apogee charge). -

4.3. Using an Active Switch with TeleMini v1.0

+

4.3. Using an Active Switch with TeleMini v1.0

As explained above, an external active switch requires three connections, one to the positive battery terminal, one to the flight computer positive input and one to ground. Again, @@ -474,21 +476,21 @@ NAR power switch wire, the positive flight computer input is on the left power switch wire. Hook a lead to either of the mounting holes for a ground connection. -

5. TeleMini v2.0

+

5. TeleMini v2.0

TeleMini v2.0 is 0.8 inches by 1½ inches. It adds more on-board data logging memory, a built-in USB connector and screw terminals for the battery and power switch. The larger board fits in a 24mm coupler. There's also a battery connector for a LiPo battery if you want to use one of those. -

5.1. TeleMini v2.0 Screw Terminals

+

5.1. TeleMini v2.0 Screw Terminals

TeleMini v2.0 has two sets of four screw terminals on the end of the board opposite the telemetry antenna. Using the picture above, the top four have connections for the main pyro circuit and an external battery and the bottom four have connections for the apogee pyro circuit and the power switch. Counting from the left, the connections are as follows: -

Table 4.5. TeleMini v2.0 Connections

Terminal #Terminal NameDescription
Top 1Main -Main pyro channel connection to pyro circuit
Top 2Main +Main pyro channel common connection to battery +
Top 3Battery +Positive external battery terminal
Top 4Battery -Negative external battery terminal
Bottom 1Apogee -Apogee pyro channel connection to pyro circuit
Bottom 2Apogee +Apogee pyro channel common connection to - battery +
Bottom 3Switch OutputSwitch connection to flight computer
Bottom 4Switch InputSwitch connection to positive battery terminal

5.2. Using a Separate Pyro Battery with TeleMini v2.0

+

Table 4.5. TeleMini v2.0 Connections

Terminal #Terminal NameDescription
Top 1Main -Main pyro channel connection to pyro circuit
Top 2Main +Main pyro channel common connection to battery +
Top 3Battery +Positive external battery terminal
Top 4Battery -Negative external battery terminal
Bottom 1Apogee -Apogee pyro channel connection to pyro circuit
Bottom 2Apogee +Apogee pyro channel common connection to + battery +
Bottom 3Switch OutputSwitch connection to flight computer
Bottom 4Switch InputSwitch connection to positive battery terminal

5.2. Using a Separate Pyro Battery with TeleMini v2.0

As described above, using an external pyro battery involves connecting the negative battery terminal to the flight computer ground, connecting the positive battery terminal to @@ -507,7 +509,7 @@ NAR the appropriate per-pyro channel screw terminal (top terminal 1 for the Main charge, bottom terminal 1 for the Apogee charge). -

5.3. Using an Active Switch with TeleMini v2.0

+

5.3. Using an Active Switch with TeleMini v2.0

As explained above, an external active switch requires three connections, one to the positive battery terminal, one to the flight computer positive input and one to ground. Use @@ -517,20 +519,20 @@ NAR The positive battery terminal is available on bottom terminal 4, the positive flight computer input is on the bottom terminal 3. -

6. EasyMini

+

6. EasyMini

EasyMini is built on a 0.8 inch by 1½ inch circuit board. It's designed to fit in a 24mm coupler tube. The connectors and screw terminals match TeleMini v2.0, so you can easily swap between EasyMini and TeleMini. -

6.1. EasyMini Screw Terminals

+

6.1. EasyMini Screw Terminals

EasyMini has two sets of four screw terminals on the end of the board opposite the telemetry antenna. Using the picture above, the top four have connections for the main pyro circuit and an external battery and the bottom four have connections for the apogee pyro circuit and the power switch. Counting from the left, the connections are as follows: -

Table 4.6. EasyMini Connections

Terminal #Terminal NameDescription
Top 1Main -Main pyro channel connection to pyro circuit
Top 2Main +Main pyro channel common connection to battery +
Top 3Battery +Positive external battery terminal
Top 4Battery -Negative external battery terminal
Bottom 1Apogee -Apogee pyro channel connection to pyro circuit
Bottom 2Apogee +Apogee pyro channel common connection to - battery +
Bottom 3Switch OutputSwitch connection to flight computer
Bottom 4Switch InputSwitch connection to positive battery terminal

6.2. Using a Separate Pyro Battery with EasyMini

+

Table 4.6. EasyMini Connections

Terminal #Terminal NameDescription
Top 1Main -Main pyro channel connection to pyro circuit
Top 2Main +Main pyro channel common connection to battery +
Top 3Battery +Positive external battery terminal
Top 4Battery -Negative external battery terminal
Bottom 1Apogee -Apogee pyro channel connection to pyro circuit
Bottom 2Apogee +Apogee pyro channel common connection to + battery +
Bottom 3Switch OutputSwitch connection to flight computer
Bottom 4Switch InputSwitch connection to positive battery terminal

6.2. Using a Separate Pyro Battery with EasyMini

As described above, using an external pyro battery involves connecting the negative battery terminal to the flight computer ground, connecting the positive battery terminal to @@ -549,7 +551,7 @@ NAR the appropriate per-pyro channel screw terminal (top terminal 1 for the Main charge, bottom terminal 1 for the Apogee charge). -

6.3. Using an Active Switch with EasyMini

+

6.3. Using an Active Switch with EasyMini

As explained above, an external active switch requires three connections, one to the positive battery terminal, one to the flight computer positive input and one to ground. Use @@ -559,19 +561,19 @@ NAR The positive battery terminal is available on bottom terminal 4, the positive flight computer input is on the bottom terminal 3. -

7. TeleMega

+

7. TeleMega

TeleMega is a 1¼ inch by 3¼ inch circuit board. It was designed to easily fit in a 38mm coupler. Like TeleMetrum, TeleMega has an accelerometer and so it must be mounted so that the board is aligned with the flight axis. It can be mounted either antenna up or down. -

7.1. TeleMega Screw Terminals

+

7.1. TeleMega Screw Terminals

TeleMega has two sets of nine screw terminals on the end of the board opposite the telemetry antenna. They are as follows: -

Table 4.7. TeleMega Screw Terminals

Terminal #Terminal NameDescription
Top 1Switch InputSwitch connection to positive battery terminal
Top 2Switch OutputSwitch connection to flight computer
Top 3GNDGround connection for use with external active switch
Top 4Main -Main pyro channel connection to pyro circuit
Top 5Main +Main pyro channel common connection to battery +
Top 6Apogee -Apogee pyro channel connection to pyro circuit
Top 7Apogee +Apogee pyro channel common connection to battery +
Top 8D -D pyro channel connection to pyro circuit
Top 9D +D pyro channel common connection to battery +
Bottom 1GNDGround connection for negative pyro battery terminal
Bottom 2PyroPositive pyro battery terminal
Bottom 3Lipo +

Table 4.7. TeleMega Screw Terminals

Terminal #Terminal NameDescription
Top 1Switch InputSwitch connection to positive battery terminal
Top 2Switch OutputSwitch connection to flight computer
Top 3GNDGround connection for use with external active switch
Top 4Main -Main pyro channel connection to pyro circuit
Top 5Main +Main pyro channel common connection to battery +
Top 6Apogee -Apogee pyro channel connection to pyro circuit
Top 7Apogee +Apogee pyro channel common connection to battery +
Top 8D -D pyro channel connection to pyro circuit
Top 9D +D pyro channel common connection to battery +
Bottom 1GNDGround connection for negative pyro battery terminal
Bottom 2PyroPositive pyro battery terminal
Bottom 3Lipo Power switch output. Use to connect main battery to pyro battery input -
Bottom 4A -A pyro channel connection to pyro circuit
Bottom 5A +A pyro channel common connection to battery +
Bottom 6B -B pyro channel connection to pyro circuit
Bottom 7B +B pyro channel common connection to battery +
Bottom 8C -C pyro channel connection to pyro circuit
Bottom 9C +C pyro channel common connection to battery +

7.2. Using a Separate Pyro Battery with TeleMega

+

Bottom 4A -A pyro channel connection to pyro circuit
Bottom 5A +A pyro channel common connection to battery +
Bottom 6B -B pyro channel connection to pyro circuit
Bottom 7B +B pyro channel common connection to battery +
Bottom 8C -C pyro channel connection to pyro circuit
Bottom 9C +C pyro channel common connection to battery +

7.2. Using a Separate Pyro Battery with TeleMega

TeleMega provides explicit support for an external pyro battery. All that is required is to remove the jumper between the lipo terminal (Bottom 3) and the pyro terminal @@ -579,7 +581,7 @@ NAR (Bottom 1) and the positive pyro battery to the pyro battery input (Bottom 2). You can then use the existing pyro screw terminals to hook up all of the pyro charges. -

7.3. Using Only One Battery With TeleMega

+

7.3. Using Only One Battery With TeleMega

Because TeleMega has built-in support for a separate pyro battery, if you want to fly with just one battery running both the computer and firing the charges, you need to @@ -587,7 +589,7 @@ NAR circuit. TeleMega has two screw terminals for this—hook a wire from the Lipo terminal (Bottom 3) to the Pyro terminal (Bottom 2). -

7.4. Using an Active Switch with TeleMega

+

7.4. Using an Active Switch with TeleMega

As explained above, an external active switch requires three connections, one to the positive battery terminal, one to the flight computer positive input and one to ground. @@ -595,19 +597,19 @@ NAR The positive battery terminal is available on Top terminal 1, the positive flight computer input is on Top terminal 2. Ground is on Top terminal 3. -

8. EasyMega

+

8. EasyMega

EasyMega is a 1¼ inch by 2¼ inch circuit board. It was designed to easily fit in a 38mm coupler. Like TeleMetrum, EasyMega has an accelerometer and so it must be mounted so that the board is aligned with the flight axis. It can be mounted either antenna up or down. -

8.1. EasyMega Screw Terminals

+

8.1. EasyMega Screw Terminals

EasyMega has two sets of nine screw terminals on the end of the board opposite the telemetry antenna. They are as follows: -

Table 4.8. EasyMega Screw Terminals

Terminal #Terminal NameDescription
Top 1Switch InputSwitch connection to positive battery terminal
Top 2Switch OutputSwitch connection to flight computer
Top 3GNDGround connection for use with external active switch
Top 4Main -Main pyro channel connection to pyro circuit
Top 5Main +Main pyro channel common connection to battery +
Top 6Apogee -Apogee pyro channel connection to pyro circuit
Top 7Apogee +Apogee pyro channel common connection to battery +
Top 8D -D pyro channel connection to pyro circuit
Top 9D +D pyro channel common connection to battery +
Bottom 1GNDGround connection for negative pyro battery terminal
Bottom 2PyroPositive pyro battery terminal
Bottom 3Lipo +

Table 4.8. EasyMega Screw Terminals

Terminal #Terminal NameDescription
Top 1Switch InputSwitch connection to positive battery terminal
Top 2Switch OutputSwitch connection to flight computer
Top 3GNDGround connection for use with external active switch
Top 4Main -Main pyro channel connection to pyro circuit
Top 5Main +Main pyro channel common connection to battery +
Top 6Apogee -Apogee pyro channel connection to pyro circuit
Top 7Apogee +Apogee pyro channel common connection to battery +
Top 8D -D pyro channel connection to pyro circuit
Top 9D +D pyro channel common connection to battery +
Bottom 1GNDGround connection for negative pyro battery terminal
Bottom 2PyroPositive pyro battery terminal
Bottom 3Lipo Power switch output. Use to connect main battery to pyro battery input -
Bottom 4A -A pyro channel connection to pyro circuit
Bottom 5A +A pyro channel common connection to battery +
Bottom 6B -B pyro channel connection to pyro circuit
Bottom 7B +B pyro channel common connection to battery +
Bottom 8C -C pyro channel connection to pyro circuit
Bottom 9C +C pyro channel common connection to battery +

8.2. Using a Separate Pyro Battery with EasyMega

+

Bottom 4A -A pyro channel connection to pyro circuit
Bottom 5A +A pyro channel common connection to battery +
Bottom 6B -B pyro channel connection to pyro circuit
Bottom 7B +B pyro channel common connection to battery +
Bottom 8C -C pyro channel connection to pyro circuit
Bottom 9C +C pyro channel common connection to battery +

8.2. Using a Separate Pyro Battery with EasyMega

EasyMega provides explicit support for an external pyro battery. All that is required is to remove the jumper between the lipo terminal (Bottom 3) and the pyro terminal @@ -615,7 +617,7 @@ NAR (Bottom 1) and the positive pyro battery to the pyro battery input (Bottom 2). You can then use the existing pyro screw terminals to hook up all of the pyro charges. -

8.3. Using Only One Battery With EasyMega

+

8.3. Using Only One Battery With EasyMega

Because EasyMega has built-in support for a separate pyro battery, if you want to fly with just one battery running both the computer and firing the charges, you need to @@ -623,7 +625,7 @@ NAR circuit. EasyMega has two screw terminals for this—hook a wire from the Lipo terminal (Bottom 3) to the Pyro terminal (Bottom 2). -

8.4. Using an Active Switch with EasyMega

+

8.4. Using an Active Switch with EasyMega

As explained above, an external active switch requires three connections, one to the positive battery terminal, one to the flight computer positive input and one to ground. @@ -631,14 +633,14 @@ NAR The positive battery terminal is available on Top terminal 1, the positive flight computer input is on Top terminal 2. Ground is on Top terminal 3. -

9. Flight Data Recording

+

9. Flight Data Recording

Each flight computer logs data at 100 samples per second during ascent and 10 samples per second during descent, except for TeleMini v1.0, which records ascent at 10 samples per second and descent at 1 sample per second. Data are logged to an on-board flash memory part, which can be partitioned into several equal-sized blocks, one for each flight. -

Table 4.9. Data Storage on Altus Metrum altimeters

DeviceBytes per SampleTotal StorageMinutes at Full Rate
TeleMetrum v1.081MB20
TeleMetrum v1.1 v1.282MB40
TeleMetrum v2.0168MB80
TeleMini v1.025kB4
TeleMini v2.0161MB10
EasyMini161MB10
TeleMega328MB40
EasyMega328MB40

+

Table 4.9. Data Storage on Altus Metrum altimeters

DeviceBytes per SampleTotal StorageMinutes at Full Rate
TeleMetrum v1.081MB20
TeleMetrum v1.1 v1.282MB40
TeleMetrum v2.0168MB80
TeleMini v1.025kB4
TeleMini v2.0161MB10
EasyMini161MB10
TeleMega328MB40
EasyMega328MB40

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 @@ -671,7 +673,7 @@ NAR from the flight computer before it fills up. The flight computer will still successfully control the flight even if it cannot log data, so the only thing you will lose is the data. -

10. Installation

+

10. Installation

A typical installation involves attaching only a suitable battery, a single pole switch for power on/off, and two pairs of wires connecting e-matches for the @@ -718,7 +720,7 @@ NAR and, on TeleMetrum v1, you can unplug the integrated GPS antenna and select an appropriate off-board GPS antenna with cable terminating in a U.FL connector. -

Chapter 5. System Operation

Table of Contents

1. Firmware Modes
2. GPS
3. Controlling An Altimeter Over The Radio Link
4. Ground Testing
5. Radio Link
6. APRS
7. Configurable Parameters
7.1. Radio Frequency
7.2. Callsign
7.3. Telemetry/RDF/APRS Enable
7.4. Telemetry baud rate
7.5. APRS Interval
7.6. APRS SSID
7.7. Apogee Delay
7.8. Apogee Lockout
7.9. Main Deployment Altitude
7.10. Maximum Flight Log
7.11. Ignite Mode
7.12. Pad Orientation
7.13. Configurable Pyro Channels

1. Firmware Modes

+

Chapter 5. System Operation

Table of Contents

1. Firmware Modes
2. GPS
3. Controlling An Altimeter Over The Radio Link
4. Ground Testing
5. Radio Link
6. APRS
7. Configurable Parameters
7.1. Radio Frequency
7.2. Callsign
7.3. Telemetry/RDF/APRS Enable
7.4. Telemetry baud rate
7.5. APRS Interval
7.6. APRS SSID
7.7. Apogee Delay
7.8. Apogee Lockout
7.9. Main Deployment Altitude
7.10. Maximum Flight Log
7.11. Ignite Mode
7.12. Pad Orientation
7.13. Configurable Pyro Channels

1. Firmware Modes

The AltOS firmware build for the altimeters has two fundamental modes, “idle” and “flight”. Which of these modes the firmware operates in is determined at start up time. For @@ -749,7 +751,7 @@ NAR mode. In the description of the beeping pattern, “dit” means a short beep while "dah" means a long beep (three times as long). “Brap” means a long dissonant tone. -

Table 5.1. AltOS Modes

Mode NameAbbreviationBeepsDescription
StartupSbattery voltage in decivolts +

Table 5.1. AltOS Modes

Mode NameAbbreviationBeepsDescription
StartupSbattery voltage in decivolts

Calibrating sensors, detecting orientation.

@@ -823,7 +825,7 @@ NAR slower than the “no continuity tone”)

Here's a summary of all of the “pad” and “idle” mode indications. -

Table 5.2. Pad/Idle Indications

NameBeepsDescription
Neitherbrap +

Table 5.2. Pad/Idle Indications

NameBeepsDescription
Neitherbrap

No continuity detected on either apogee or main igniters. @@ -891,7 +893,7 @@ NAR together, then power TeleMini up. Once the red LED is lit, disconnect the wire and the board should signal that it's in 'idle' mode after the initial five second startup period. -

2. GPS

+

2. GPS

TeleMetrum and TeleMega include a complete GPS receiver. A complete explanation of how GPS works is beyond the scope of this manual, but the bottom line is that the GPS receiver @@ -909,7 +911,7 @@ NAR is turned back on, the GPS system should lock very quickly, typically long before igniter installation and return to the flight line are complete. -

3. Controlling An Altimeter Over The Radio Link

+

3. Controlling An Altimeter Over The Radio Link

One of the unique features of the Altus Metrum system is the ability to create a two way command link between TeleDongle and an altimeter using the digital radio transceivers @@ -980,7 +982,7 @@ NAR lights on the devices. The red LED will flash each time a packet is transmitted, while the green LED will light up on TeleDongle when it is waiting to receive a packet from the altimeter. -

4. Ground Testing

+

4. Ground Testing

An important aspect of preparing a rocket using electronic deployment for flight is ground testing the recovery system. Thanks to the bi-directional radio link central to the Altus Metrum system, @@ -996,7 +998,7 @@ NAR manual command. You can now command the altimeter to fire the apogee or main charges from a safe distance using your computer and TeleDongle and the Fire Igniter tab to complete ejection testing. -

5. Radio Link

+

5. Radio Link

Our flight computers all incorporate an RF transceiver, but it's not a full duplex system... each end can only be transmitting or receiving at any given moment. So we had to decide how to manage the @@ -1029,7 +1031,7 @@ NAR 40mW devices. We hope to fly boards to higher altitudes over time, and would of course appreciate customer feedback on performance in higher altitude flights! -

6. APRS

+

6. APRS

TeleMetrum v2.0 and TeleMega can send APRS if desired, and the interval between APRS packets can be configured. As each APRS packet takes a full second to transmit, we recommend an @@ -1060,7 +1062,7 @@ NAR arbitrary text in it. AltOS uses this to send status information about the flight computer. It sends four fields as shown in the following table. -

Table 5.3. Altus Metrum APRS Comments

FieldExampleDescription
1LGPS Status U for unlocked, L for locked
26Number of Satellites in View
3B4.0Altimeter Battery Voltage
4A3.7Apogee Igniter Voltage
5M3.7Main Igniter Voltage
61286Device Serial Number

+

Table 5.3. Altus Metrum APRS Comments

FieldExampleDescription
1LGPS Status U for unlocked, L for locked
26Number of Satellites in View
3B4.0Altimeter Battery Voltage
4A3.7Apogee Igniter Voltage
5M3.7Main Igniter Voltage
61286Device Serial Number

Here's an example of an APRS comment showing GPS lock with 6 satellites in view, a primary battery at 4.0V, and apogee and main igniters both at 3.7V from device 1286. @@ -1080,7 +1082,7 @@ NAR that the GPS status character switches from 'L' to 'U'. Before GPS has locked, APRS will transmit zero for latitude, longitude and altitude. -

7. Configurable Parameters

+

7. Configurable Parameters

Configuring an Altus Metrum altimeter for flight is very simple. Even on our baro-only TeleMini and EasyMini boards, the use of a Kalman filter means there is no need to set a @@ -1088,7 +1090,7 @@ NAR using AltosUI over USB or or radio link via TeleDongle. Read the Configure Altimeter section in the AltosUI chapter below for more information. -

7.1. Radio Frequency

+

7.1. Radio Frequency

Altus Metrum boards support radio frequencies in the 70cm band. By default, the configuration interface provides a list of 10 “standard” frequencies in 100kHz channels starting at @@ -1098,18 +1100,18 @@ NAR frequency will be used to avoid interference. And of course, both altimeter and TeleDongle must be configured to the same frequency to successfully communicate with each other. -

7.2. Callsign

+

7.2. Callsign

This sets the callsign used for telemetry, APRS and the packet link. For telemetry and APRS, this is used to identify the device. For the packet link, the callsign must match that configured in AltosUI or the link will not work. This is to prevent accidental configuration of another Altus Metrum flight computer operating on the same frequency nearby. -

7.3. Telemetry/RDF/APRS Enable

+

7.3. Telemetry/RDF/APRS Enable

You can completely disable the radio while in flight, if necessary. This doesn't disable the packet link in idle mode. -

7.4. Telemetry baud rate

+

7.4. Telemetry baud rate

This sets the modulation bit rate for data transmission for both telemetry and packet link mode. Lower bit rates will increase range while reducing the amount of data @@ -1117,17 +1119,17 @@ NAR telemetry is done using a rate 1/2 constraint 4 convolution code, so the actual data transmission rate is 1/2 of the modulation bit rate specified here. -

7.5. APRS Interval

+

7.5. APRS Interval

This selects how often APRS packets are transmitted. Set this to zero to disable APRS without also disabling the regular telemetry and RDF transmissions. As APRS takes a full second to transmit a single position report, we recommend sending packets no more than once every 5 seconds. -

7.6. APRS SSID

+

7.6. APRS SSID

This selects the SSID reported in APRS packets. By default, it is set to the last digit of the serial number, but you can change this to any value from 0 to 9. -

7.7. Apogee Delay

+

7.7. Apogee Delay

Apogee delay is the number of seconds after the altimeter detects flight apogee that the drogue charge should be fired. In most cases, this should be left at the default of 0. However, if you are flying @@ -1143,7 +1145,7 @@ NAR or 3 seconds later to avoid any chance of both charges firing simultaneously. We've flown several air-frames this way quite happily, including Keith's successful L3 cert. -

7.8. Apogee Lockout

+

7.8. Apogee Lockout

Apogee lockout is the number of seconds after boost where the flight computer will not fire the apogee charge, even if the rocket appears to be at apogee. This is often called @@ -1153,7 +1155,7 @@ NAR flight computers include a Kalman filter which is not fooled by this sharp pressure increase, and so this setting should be left at the default value of zero to disable it. -

7.9. Main Deployment Altitude

+

7.9. Main Deployment Altitude

By default, the altimeter will fire the main deployment charge at an elevation of 250 meters (about 820 feet) above ground. We think this is a good elevation for most air-frames, but feel free to change this @@ -1162,7 +1164,7 @@ NAR deployment elevation for the backup altimeter to be something lower than the primary so that both pyrotechnic charges don't fire simultaneously. -

7.10. Maximum Flight Log

+

7.10. Maximum Flight Log

Changing this value will set the maximum amount of flight log storage that an individual flight will use. The available storage is divided into as many flights of the @@ -1174,7 +1176,7 @@ NAR Even though our flight computers (except TeleMini v1.0) can store multiple flights, we strongly recommend downloading and saving flight data after each flight. -

7.11. Ignite Mode

+

7.11. 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 @@ -1185,7 +1187,7 @@ NAR 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. -

7.12. Pad Orientation

+

7.12. Pad Orientation

TeleMetrum, TeleMega and EasyMega measure 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 @@ -1195,7 +1197,7 @@ NAR of the board connected to the 70cm antenna to be nearest the nose of the rocket, with the end containing the screw terminals nearest the tail. -

7.13. Configurable Pyro Channels

+

7.13. Configurable Pyro Channels

In addition to the usual Apogee and Main pyro channels, TeleMega and EasyMega have four additional channels that can be configured to activate when various flight conditions are @@ -1254,9 +1256,9 @@ NAR whether the speed is < 0.

  • After Motor. The flight software counts each time the - rocket starts accelerating (presumably due to a motor or - motors igniting). Use this value to count ignitions for - multi-staged or multi-airstart launches. + rocket starts accelerating and then decelerating + (presumably due to a motor or motors burning). Use this + value for multi-staged or multi-airstart launches.

  • Delay. This value doesn't perform any checks, instead it inserts a delay between the time when the other @@ -1295,7 +1297,7 @@ NAR Coast state (depending on how fast it is moving). If the computer detects upwards acceleration again, it will move back to Boost state. -

    • Chapter 6. AltosUI

    Table of Contents

    1. Monitor Flight
    1.1. Launch Pad
    1.2. Ascent
    1.3. Descent
    1.4. Landed
    1.5. Table
    1.6. Site Map
    1.7. Ignitor
    2. Save Flight Data
    3. Replay Flight
    4. Graph Data
    4.1. Flight Graph
    4.2. Configure Graph
    4.3. Flight Statistics
    4.4. Map
    5. Export Data
    5.1. Comma Separated Value Format
    5.2. Keyhole Markup Language (for Google Earth)
    6. Configure Altimeter
    6.1. Main Deploy Altitude
    6.2. Apogee Delay
    6.3. Apogee Lockoug
    6.4. Frequency
    6.5. RF Calibration
    6.6. Telemetry/RDF/APRS Enable
    6.7. Telemetry baud rate
    6.8. APRS Interval
    6.9. APRS SSID
    6.10. Callsign
    6.11. Maximum Flight Log Size
    6.12. Ignitor Firing Mode
    6.13. Pad Orientation
    6.14. Beeper Frequency
    6.15. Configure Pyro Channels
    7. Configure AltosUI
    7.1. Voice Settings
    7.2. Log Directory
    7.3. Callsign
    7.4. Imperial Units
    7.5. Font Size
    7.6. Serial Debug
    7.7. Manage Frequencies
    8. Configure Groundstation
    8.1. Frequency
    8.2. RF Calibration
    8.3. Telemetry Rate
    9. Flash Image
    10. Fire Igniter
    11. Scan Channels
    12. Load Maps
    13. Monitor Idle

    +

    Chapter 6. AltosUI

    Table of Contents

    1. Monitor Flight
    1.1. Launch Pad
    1.2. Ascent
    1.3. Descent
    1.4. Landed
    1.5. Table
    1.6. Site Map
    1.7. Ignitor
    2. Save Flight Data
    3. Replay Flight
    4. Graph Data
    4.1. Flight Graph
    4.2. Configure Graph
    4.3. Flight Statistics
    4.4. Map
    5. Export Data
    5.1. Comma Separated Value Format
    5.2. Keyhole Markup Language (for Google Earth)
    6. Configure Altimeter
    6.1. Main Deploy Altitude
    6.2. Apogee Delay
    6.3. Apogee Lockoug
    6.4. Frequency
    6.5. RF Calibration
    6.6. Telemetry/RDF/APRS Enable
    6.7. Telemetry baud rate
    6.8. APRS Interval
    6.9. APRS SSID
    6.10. Callsign
    6.11. Maximum Flight Log Size
    6.12. Ignitor Firing Mode
    6.13. Pad Orientation
    6.14. Beeper Frequency
    6.15. Configure Pyro Channels
    7. Configure AltosUI
    7.1. Voice Settings
    7.2. Log Directory
    7.3. Callsign
    7.4. Imperial Units
    7.5. Font Size
    7.6. Serial Debug
    7.7. Manage Frequencies
    8. Configure Groundstation
    8.1. Frequency
    8.2. RF Calibration
    8.3. Telemetry Rate
    9. Flash Image
    10. Fire Igniter
    11. Scan Channels
    12. Load Maps
    13. Monitor Idle

    The AltosUI program provides a graphical user interface for interacting with the Altus Metrum product family. AltosUI can monitor telemetry data, configure devices and many other @@ -1303,7 +1305,7 @@ NAR buttons, one for each major activity in the system. This chapter is split into sections, each of which documents one of the tasks provided from the top-level toolbar. -

    1. Monitor Flight

    Receive, Record and Display Telemetry Data

    +

    1. Monitor Flight

    Receive, Record and Display Telemetry Data

    Selecting this item brings up a dialog box listing all of the connected TeleDongle devices. When you choose one of these, AltosUI will create a window to display telemetry data as @@ -1353,7 +1355,7 @@ NAR data relevant to the current state of the flight. You can select other tabs at any time. The final 'table' tab displays all of the raw telemetry values in one place in a spreadsheet-like format. -

    1.1. Launch Pad

    +

    1.1. Launch Pad

    The 'Launch Pad' tab shows information used to decide when the rocket is ready for flight. The first elements include red/green indicators, if any of these is red, you'll want to evaluate @@ -1403,7 +1405,7 @@ NAR The Launchpad tab also shows the computed launch pad position and altitude, averaging many reported positions to improve the accuracy of the fix. -

    1.2. Ascent

    +

    1.2. Ascent

    This tab is shown during Boost, Fast and Coast phases. The information displayed here helps monitor the rocket as it heads towards apogee. @@ -1422,7 +1424,7 @@ NAR Finally, the current igniter voltages are reported as in the Launch Pad tab. This can help diagnose deployment failures caused by wiring which comes loose under high acceleration. -

    1.3. Descent

    +

    1.3. Descent

    Once the rocket has reached apogee and (we hope) activated the apogee charge, attention switches to tracking the rocket on the way back to the ground, and for dual-deploy flights, @@ -1451,7 +1453,7 @@ NAR e-matches are designed to retain continuity even after being fired, and will continue to show as green or return from red to green after firing. -

    1.4. Landed

    +

    1.4. Landed

    Once the rocket is on the ground, attention switches to recovery. While the radio signal is often lost once the rocket is on the ground, the last reported GPS position is @@ -1480,13 +1482,13 @@ NAR To get more detailed information about the flight, you can click on the 'Graph Flight' button which will bring up a graph window for the current flight. -

    1.5. Table

    +

    1.5. Table

    The table view shows all of the data available from the flight computer. Probably the most useful data on this tab is the detailed GPS information, which includes horizontal dilution of precision information, and information about the signal being received from the satellites. -

    1.6. Site Map

    +

    1.6. Site Map

    When the TeleMetrum has a GPS fix, the Site Map tab will map the rocket's position to make it easier for you to locate the rocket, both while it is in the air, and when it has landed. The @@ -1513,14 +1515,14 @@ NAR

    You can pre-load images for your favorite launch sites before you leave home; check out the 'Preload Maps' section below. -

    1.7. Ignitor

    +

    1.7. Ignitor

    TeleMega includes four additional programmable pyro channels. The Ignitor tab shows whether each of them has continuity. If an ignitor has a low resistance, then the voltage measured here will be close to the pyro battery voltage. A value greater than 3.2V is required for a 'GO' status. -

    2. Save Flight Data

    +

    2. Save Flight Data

    The altimeter records flight data to its internal flash memory. TeleMetrum data is recorded at a much higher rate than the telemetry system can handle, and is not subject to radio drop-outs. As @@ -1549,7 +1551,7 @@ NAR The file name for each flight log is computed automatically from the recorded flight date, altimeter serial number and flight number information. -

    3. Replay Flight

    +

    3. Replay Flight

    Select this button and you are prompted to select a flight record file, either a .telem file recording telemetry data or a .eeprom file containing flight data saved from the altimeter @@ -1558,7 +1560,7 @@ NAR Once a flight record is selected, the flight monitor interface is displayed and the flight is re-enacted in real time. Check the Monitor Flight chapter above to learn how this window operates. -

    4. Graph Data

    +

    4. Graph Data

    Select this button and you are prompted to select a flight record file, either a .telem file recording telemetry data or a .eeprom file containing flight data saved from @@ -1570,7 +1572,7 @@ NAR

    Once a flight record is selected, a window with multiple tabs is opened. -

    4.1. Flight Graph

    +

    4.1. Flight Graph

    By default, the graph contains acceleration (blue), velocity (green) and altitude (red).

    @@ -1580,18 +1582,18 @@ NAR control and clicking and dragging allows the graph to be panned. The right mouse button causes a pop-up menu to be displayed, giving you the option save or print the plot. -

    4.2. Configure Graph

    +

    4.2. Configure Graph

    This selects which graph elements to show, and, at the very bottom, lets you switch between metric and imperial units -

    4.3. Flight Statistics

    +

    4.3. Flight Statistics

    Shows overall data computed from the flight. -

    4.4. Map

    +

    4.4. Map

    Shows a satellite image of the flight area overlaid with the path of the flight. The red concentric circles mark the launch pad, the black concentric circles mark the landing location. -

    5. Export Data

    +

    5. Export Data

    This tool takes the raw data files and makes them available for external analysis. When you select this button, you are prompted to select a flight data file, which can be either a .eeprom or .telem. @@ -1600,7 +1602,7 @@ NAR Next, a second dialog appears which is used to select where to write the resulting file. It has a selector to choose between CSV and KML file formats. -

    5.1. Comma Separated Value Format

    +

    5.1. Comma Separated Value Format

    This is a text file containing the data in a form suitable for import into a spreadsheet or other external data analysis tool. The first few lines of the file contain the version and @@ -1614,11 +1616,11 @@ NAR the sensor values are converted to standard units, with the barometric data reported in both pressure, altitude and height above pad units. -

    5.2. Keyhole Markup Language (for Google Earth)

    +

    5.2. Keyhole Markup Language (for Google Earth)

    This is the format used by Google Earth to provide an overlay within that application. With this, you can use Google Earth to see the whole flight path in 3D. -

    6. Configure Altimeter

    +

    6. Configure Altimeter

    Select this button and then select either an altimeter or TeleDongle Device from the list provided. Selecting a TeleDongle device will use the radio link to configure a remote altimeter. @@ -1646,14 +1648,14 @@ NAR lost.

    The rest of the dialog contains the parameters to be configured. -

    6.1. Main Deploy Altitude

    +

    6.1. Main Deploy Altitude

    This sets the altitude (above the recorded pad altitude) at which the 'main' igniter will fire. The drop-down menu shows some common values, but you can edit the text directly and choose whatever you like. If the apogee charge fires below this altitude, then the main charge will fire two seconds after the apogee charge fires. -

    6.2. Apogee Delay

    +

    6.2. Apogee Delay

    When flying redundant electronics, it's often important to ensure that multiple apogee charges don't fire at precisely the same time, as that can over pressurize the apogee deployment @@ -1661,7 +1663,7 @@ NAR Delay parameter tells the flight computer to fire the apogee charge a certain number of seconds after apogee has been detected. -

    6.3. Apogee Lockoug

    +

    6.3. Apogee Lockoug

    Apogee lockout is the number of seconds after boost where the flight computer will not fire the apogee charge, even if the rocket appears to be at apogee. This is often called @@ -1671,13 +1673,13 @@ NAR flight computers include a Kalman filter which is not fooled by this sharp pressure increase, and so this setting should be left at the default value of zero to disable it. -

    6.4. Frequency

    +

    6.4. Frequency

    This configures which of the frequencies to use for both telemetry and packet command mode. Note that if you set this value via packet command mode, the TeleDongle frequency will also be automatically reconfigured to match so that communication will continue afterwards. -

    6.5. RF Calibration

    +

    6.5. RF Calibration

    The radios in every Altus Metrum device are calibrated at the factory to ensure that they transmit and receive on the specified frequency. If you need to you can adjust the calibration @@ -1685,11 +1687,11 @@ NAR the value means, read the appendix on calibration and/or the source code for more information. To change a TeleDongle's calibration, you must reprogram the unit completely. -

    6.6. Telemetry/RDF/APRS Enable

    +

    6.6. Telemetry/RDF/APRS Enable

    Enables the radio for transmission during flight. When disabled, the radio will not transmit anything during flight at all. -

    6.7. Telemetry baud rate

    +

    6.7. Telemetry baud rate

    This sets the modulation bit rate for data transmission for both telemetry and packet link mode. Lower bit rates will increase range while reducing the amount of data @@ -1697,7 +1699,7 @@ NAR telemetry is done using a rate 1/2 constraint 4 convolution code, so the actual data transmission rate is 1/2 of the modulation bit rate specified here. -

    6.8. APRS Interval

    +

    6.8. APRS Interval

    How often to transmit GPS information via APRS (in seconds). When set to zero, APRS transmission is disabled. This option is available on TeleMetrum v2 and @@ -1705,19 +1707,19 @@ NAR packets. Note that a single APRS packet takes nearly a full second to transmit, so enabling this option will prevent sending any other telemetry during that time. -

    6.9. APRS SSID

    +

    6.9. APRS SSID

    Which SSID to report in APRS packets. By default, this is set to the last digit of the serial number, but can be configured to any value from 0 to 9. -

    6.10. Callsign

    +

    6.10. Callsign

    This sets the call sign included in each telemetry packet. Set this as needed to conform to your local radio regulations. -

    6.11. Maximum Flight Log Size

    +

    6.11. 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. -

    6.12. Ignitor Firing Mode

    +

    6.12. Ignitor Firing Mode

    This configuration parameter allows the two standard ignitor channels (Apogee and Main) to be used in different configurations. @@ -1736,7 +1738,7 @@ NAR Altitude setting during descent. The 'apogee' channel is fired first, followed after a two second delay by the 'main' channel. -

    6.13. Pad Orientation

    +

    6.13. Pad Orientation

    Because they include accelerometers, TeleMetrum, TeleMega and EasyMega are sensitive to the orientation of the board. By default, they expect the antenna end to point forward. This @@ -1750,13 +1752,13 @@ NAR In this mode, the antenna end of the flight computer must point aft, in line with the expected flight path. -

    6.14. Beeper Frequency

    +

    6.14. Beeper Frequency

    The beeper on all Altus Metrum flight computers works best at 4000Hz, however if you have more than one flight computer in a single airframe, having all of them sound at the same frequency can be confusing. This parameter lets you adjust the base beeper frequency value. -

    6.15. Configure Pyro Channels

    +

    6.15. Configure Pyro Channels

    This opens a separate window to configure the additional pyro channels available on TeleMega and EasyMega. One column is presented for each channel. Each row represents a single @@ -1780,9 +1782,9 @@ NAR configuration along with the rest of the flight computer configuration by pressing the 'Save' button in the main Configure Flight Computer window. -

    7. Configure AltosUI

    +

    7. Configure AltosUI

    This button presents a dialog so that you can configure the AltosUI global settings. -

    7.1. Voice Settings

    +

    7.1. Voice Settings

    AltosUI provides voice announcements during flight so that you can keep your eyes on the sky and still get information about the current flight status. However, sometimes you don't want @@ -1791,7 +1793,7 @@ NAR Plays a short message allowing you to verify that the audio system is working and the volume settings are reasonable -

    7.2. Log Directory

    +

    7.2. Log Directory

    AltosUI logs all telemetry data and saves all TeleMetrum flash data to this directory. This directory is also used as the staring point when selecting data files for display or export. @@ -1799,7 +1801,7 @@ NAR Click on the directory name to bring up a directory choosing dialog, select a new directory and click 'Select Directory' to change where AltosUI reads and writes data files. -

    7.3. Callsign

    +

    7.3. Callsign

    This value is transmitted in each command packet sent from TeleDongle and received from an altimeter. It is not used in telemetry mode, as the callsign configured in the altimeter board @@ -1812,30 +1814,30 @@ NAR the callsign configured here must exactly match the callsign configured in the flight computer. This matching is case sensitive. -

    7.4. Imperial Units

    +

    7.4. Imperial Units

    This switches between metric units (meters) and imperial units (feet and miles). This affects the display of values use during flight monitoring, configuration, data graphing and all of the voice announcements. It does not change the units used when exporting to CSV files, those are always produced in metric units. -

    7.5. Font Size

    +

    7.5. Font Size

    Selects the set of fonts used in the flight monitor window. Choose between the small, medium and large sets. -

    7.6. Serial Debug

    +

    7.6. 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. -

    7.7. Manage Frequencies

    +

    7.7. Manage Frequencies

    This brings up a dialog where you can configure the set of frequencies shown in the various frequency menus. You can add as many as you like, or even reconfigure the default set. Changing this list does not affect the frequency settings of any devices, it only changes the set of frequencies shown in the menus. -

    8. Configure Groundstation

    +

    8. Configure Groundstation

    Select this button and then select a TeleDongle or TeleBT Device from the list provided.

    The first few lines of the dialog provide information about the @@ -1862,24 +1864,24 @@ NAR lost.

    The rest of the dialog contains the parameters to be configured. -

    8.1. Frequency

    +

    8.1. Frequency

    This configures the frequency to use for both telemetry and packet command mode. Set this before starting any operation involving packet command mode so that it will use the right frequency. Telemetry monitoring mode also provides a menu to change the frequency, and that menu also sets the same Java preference value used here. -

    8.2. RF Calibration

    +

    8.2. RF Calibration

    The radios in every Altus Metrum device are calibrated at the factory to ensure that they transmit and receive on the specified frequency. To change a TeleDongle or TeleBT's calibration, you must reprogram the unit completely, so this entry simply shows the current value and doesn't allow any changes. -

    8.3. Telemetry Rate

    +

    8.3. Telemetry Rate

    This lets you match the telemetry and packet link rate from the transmitter. If they don't match, the device won't receive any data. -

    9. Flash Image

    +

    9. Flash Image

    This reprograms Altus Metrum devices with new firmware. TeleMetrum v1.x, TeleDongle v0.2, TeleMini and TeleBT are all reprogrammed by using another similar unit as a @@ -1888,7 +1890,7 @@ NAR directly over their USB ports (self programming). Please read the directions for flashing devices in the Updating Device Firmware chapter below. -

    10. Fire Igniter

    +

    10. Fire Igniter

    This activates the igniter circuits in the flight computer to help test recovery systems deployment. Because this command can operate over the Packet Command Link, you can prepare the rocket as @@ -1908,18 +1910,17 @@ NAR you have 10 seconds to press the 'Fire' button or the system will deactivate, at which point you start over again at selecting the desired igniter. -

    11. Scan Channels

    +

    11. Scan Channels

    This listens for telemetry packets on all of the configured frequencies, displaying information about each device it receives a packet from. You can select which of the baud rates and telemetry formats should be tried; by default, it only listens at 38400 baud with the standard telemetry format used in v1.0 and later firmware. -

    12. Load Maps

    +

    12. Load Maps

    Before heading out to a new launch site, you can use this to load satellite images in case you don't have internet - connectivity at the site. This loads a fairly large area - around the launch site, which should cover any flight you're likely to make. + connectivity at the site.

    There's a drop-down menu of launch sites we know about; if your favorites aren't there, please let us know the lat/lon @@ -1946,21 +1947,24 @@ NAR You can specify the range of zoom levels to download; smaller numbers show more area with less resolution. The default level, 0, shows about 3m/pixel. One zoom level change - doubles or halves that number. + doubles or halves that number. Larger zoom levels show more + detail, smaller zoom levels less.

    - The Tile Radius value sets how large an area around the center - point to download. Each tile is 512x512 pixels, and the - 'radius' value specifies how many tiles away from the center - will be downloaded. Specify a radius of 0 and you get only the - center tile. A radius of 1 loads a 3x3 grid, centered on the - specified location. + The Map Radius value sets how large an area around the center + point to download. Select a value large enough to cover any + plausible flight from that site. Be aware that loading a large + area with a high maximum zoom level can attempt to download a + lot of data. Loading hybrid maps with a 10km radius at a + minimum zoom of -2 and a maximum zoom of 2 consumes about + 120MB of space. Terrain and road maps consume about 1/10 as + much space as satellite or hybrid maps.

    Clicking the 'Load Map' button will fetch images from Google Maps; note that Google limits how many images you can fetch at once, so if you load more than one launch site, you may get some gray areas in the map which indicate that Google is tired of sending data to you. Try again later. -

    13. Monitor Idle

    +

    13. Monitor Idle

    This brings up a dialog similar to the Monitor Flight UI, except it works with the altimeter in “idle” mode by sending query commands to discover the current state rather than @@ -1969,25 +1973,30 @@ NAR callsigns match exactly. If you can receive telemetry, but cannot manage to run Monitor Idle, then it's very likely that your callsigns are different in some way. -

    Chapter 7. AltosDroid

    Table of Contents

    1. Installing AltosDroid
    2. Connecting to TeleBT
    3. Configuring AltosDroid
    4. AltosDroid Flight Monitoring
    4.1. Pad
    5. Downloading Flight Logs

    +

    + You can change the frequency and callsign used to communicate + with the flight computer; they must both match the + configuration in the flight computer exactly. +

    Chapter 7. AltosDroid

    Table of Contents

    1. Installing AltosDroid
    2. Connecting to TeleBT over Bluetooth™
    3. Connecting to TeleDongle or TeleBT over USB
    4. Configuring AltosDroid
    4.1. Select radio frequency
    4.2. Select data rate
    4.3. Change units
    4.4. Load maps
    4.5. Map type
    4.6. Toggle Online/Offline maps
    4.7. Select Tracker
    4.8. Delete Track
    5. AltosDroid Flight Monitoring
    5.1. Pad
    5.2. Flight
    5.3. Recover
    5.4. Map
    6. Downloading Flight Logs

    AltosDroid provides the same flight monitoring capabilities as - AltosUI, but runs on Android devices and is designed to connect - to a TeleBT receiver over Bluetooth™. AltosDroid monitors + AltosUI, but runs on Android devices. AltosDroid is designed to connect + to a TeleBT receiver over Bluetooth™ and (on Android devices supporting + USB On-the-go) TeleDongle and TeleBT devices over USB. AltosDroid monitors telemetry data, logging it to internal storage in the Android - device, and presents that data in a UI the same way the 'Monitor - Flight' window does in AltosUI. + device, and presents that data in a UI similar to the 'Monitor + Flight' window in AltosUI.

    - This manual will explain how to configure AltosDroid, connect - to TeleBT, operate the flight monitoring interface and describe - what the displayed data means. -

    1. Installing AltosDroid

    + This manual will explain how to configure AltosDroid, connect to + TeleBT or TeleDongle, operate the flight monitoring interface + and describe what the displayed data means. +

    1. Installing AltosDroid

    AltosDroid is available from the Google Play store. To install it on your Android device, open the Google Play Store application and search for “altosdroid”. Make sure you don't have a space between “altos” and “droid” or you probably won't find what you want. That should bring you to the right page from which you can download and install the application. -

    2. Connecting to TeleBT

    +

    2. Connecting to TeleBT over Bluetooth™

    Press the Android 'Menu' button or soft-key to see the configuration options available. Select the 'Connect a device' option and then the 'Scan for devices' entry at the bottom to @@ -1997,78 +2006,231 @@ NAR Subsequent connections will not require you to enter that code, and your 'paired' device will appear in the list without scanning. -

    3. Configuring AltosDroid

    - The only configuration option available for AltosDroid is - which frequency to listen on. Press the Android 'Menu' button - or soft-key and pick the 'Select radio frequency' entry. That - brings up a menu of pre-set radio frequencies; pick the one - which matches your altimeter. -

    4. AltosDroid Flight Monitoring

    +

    3. Connecting to TeleDongle or TeleBT over USB

    + Get a special USB On-the-go adapter cable. These cables have a USB + micro-B male connector on one end and a standard A female + connector on the other end. Plug in your TeleDongle or TeleBT + device to the adapter cable and the adapter cable into your + phone and AltosDroid should automatically start up. If it + doesn't, the most likely reason is that your Android device + doesn't support USB On-the-go. +

    4. Configuring AltosDroid

    + There are several configuration and operation parameters + available in the AltosDroid menu. +

    4.1. Select radio frequency

    + This selects which frequency to listen on by bringing up a + menu of pre-set radio frequencies. Pick the one which matches + your altimeter. +

    4.2. Select data rate

    + Altus Metrum transmitters can be configured to operate at + lower data rates to improve transmission range. If you have + configured your device to do this, this menu item allows you + to change the receiver to match. +

    4.3. Change units

    + This toggles between metric and imperial units. +

    4.4. Load maps

    + Brings up a dialog allowing you to download offline map + tiles so that you can have maps available even if you have + no network connectivity at the launch site. +

    4.5. Map type

    + Displays a menu of map types and lets you select one. Hybrid + maps include satellite images with a roadmap + overlaid. Satellite maps dispense with the roadmap + overlay. Roadmap shows just the roads. Terrain includes + roads along with shadows indicating changes in elevation, + and other geographical features. +

    4.6. Toggle Online/Offline maps

    + Switches between online and offline maps. Online maps will + show a 'move to current position' icon in the upper right + corner, while offline maps will have copyright information + all over the map. Otherwise, they're pretty similar. +

    4.7. Select Tracker

    + Switches the information displays to show data for a + different transmitting device. The map will always show all + of the devices in view. Trackers are shown and selected by + serial number, so make sure you note the serial number of + devices in each airframe. +

    4.8. Delete Track

    + Deletes all information about a transmitting device. +

    5. AltosDroid Flight Monitoring

    AltosDroid is designed to mimic the AltosUI flight monitoring display, providing separate tabs for each stage of your rocket flight along with a tab containing a map of the local area with icons marking the current location of the altimeter and the Android device. -

    4.1. Pad

    - The 'Launch Pad' tab shows information used to decide when the +

    5.1. Pad

    + The 'Pad' tab shows information used to decide when the rocket is ready for flight. The first elements include red/green indicators, if any of these is red, you'll want to evaluate - whether the rocket is ready to launch: -

    Battery Voltage

    - This indicates whether the Li-Po battery - powering the TeleMetrum has sufficient charge to last for - the duration of the flight. A value of more than - 3.8V is required for a 'GO' status. -

    Apogee Igniter Voltage

    - This indicates whether the apogee - igniter has continuity. If the igniter has a low - resistance, then the voltage measured here will be close - to the Li-Po battery voltage. A value greater than 3.2V is - required for a 'GO' status. -

    Main Igniter Voltage

    - This indicates whether the main - igniter has continuity. If the igniter has a low - resistance, then the voltage measured here will be close - to the Li-Po battery voltage. A value greater than 3.2V is - required for a 'GO' status. -

    On-board Data Logging

    - This indicates whether there is - space remaining on-board to store flight data for the - upcoming flight. If you've downloaded data, but failed - to erase flights, there may not be any space - left. TeleMetrum can store multiple flights, depending - on the configured maximum flight log size. TeleMini - stores only a single flight, so it will need to be - downloaded and erased after each flight to capture - data. This only affects on-board flight logging; the - altimeter will still transmit telemetry and fire - ejection charges at the proper times. -

    GPS Locked

    - For a TeleMetrum or TeleMega device, this indicates whether the GPS receiver is - currently able to compute position information. GPS requires - at least 4 satellites to compute an accurate position. -

    GPS Ready

    - For a TeleMetrum or TeleMega device, this indicates whether GPS has reported at least - 10 consecutive positions without losing lock. This ensures - that the GPS receiver has reliable reception from the - satellites. -

    + whether the rocket is ready to launch.

    - The Launchpad tab also shows the computed launch pad position - and altitude, averaging many reported positions to improve the - accuracy of the fix. -

    5. Downloading Flight Logs

    + When the pad tab is selected, the voice responses will + include status changes to the igniters and GPS reception, + letting you know if the rocket is still ready for launch. +

    Battery

    + This indicates whether the Li-Po battery + powering the transmitter has sufficient charge to last for + the duration of the flight. A value of more than + 3.8V is required for a 'GO' status. +

    Receiver Battery

    + This indicates whether the Li-Po battery + powering the TeleBT has sufficient charge to last for + the duration of the flight. A value of more than + 3.8V is required for a 'GO' status. +

    Data Logging

    + This indicates whether there is space remaining + on-board to store flight data for the upcoming + flight. If you've downloaded data, but failed to + erase flights, there may not be any space + left. TeleMetrum and TeleMega can store multiple + flights, depending on the configured maximum flight + log size. TeleGPS logs data continuously. TeleMini + stores only a single flight, so it will need to be + downloaded and erased after each flight to capture + data. This only affects on-board flight logging; the + altimeter will still transmit telemetry and fire + ejection charges at the proper times. +

    GPS Locked

    + For a TeleMetrum or TeleMega device, this indicates whether the GPS receiver is + currently able to compute position information. GPS requires + at least 4 satellites to compute an accurate position. +

    GPS Ready

    + For a TeleMetrum or TeleMega device, this indicates whether GPS has reported at least + 10 consecutive positions without losing lock. This ensures + that the GPS receiver has reliable reception from the + satellites. +

    Apogee Igniter

    + This indicates whether the apogee + igniter has continuity. If the igniter has a low + resistance, then the voltage measured here will be close + to the Li-Po battery voltage. A value greater than 3.2V is + required for a 'GO' status. +

    Main Igniter

    + This indicates whether the main + igniter has continuity. If the igniter has a low + resistance, then the voltage measured here will be close + to the Li-Po battery voltage. A value greater than 3.2V is + required for a 'GO' status. +

    Igniter A-D

    + This indicates whether the indicated additional pyro + channel igniter has continuity. If the igniter has a + low resistance, then the voltage measured here will + be close to the Li-Po battery voltage. A value + greater than 3.2V is required for a 'GO' status. +

    + The Pad tab also shows the location of the Android device. +

    5.2. Flight

    + The 'Flight' tab shows information used to evaluate and spot + a rocket while in flight. It displays speed and height data + to monitor the health of the rocket, along with elevation, + range and bearing to help locate the rocket in the sky. +

    + While the Flight tab is displayed, the voice announcements + will include current speed, height, elevation and bearing + information. +

    Speed

    + Shows current vertical speed. During descent, the + speed values are averaged over a fairly long time to + try and make them steadier. +

    Height

    + Shows the current height above the launch pad. +

    Max Speed

    + Shows the maximum vertical speed seen during the flight. +

    Max Height

    + Shows the maximum height above launch pad. +

    Elevation

    + This is the angle above the horizon from the android + devices current position. +

    Range

    + The total distance from the android device to the + rocket, including both ground distance and + difference in altitude. Use this to gauge how large + the rocket is likely to appear in the sky. +

    Bearing

    + This is the aziumuth from true north for the rocket + from the android device. Use this in combination + with the Elevation value to help locate the rocket + in the sky, or at least to help point the antenna in + the general direction. This is provided in both + degrees and a compass point (like West South + West). You'll want to know which direction is true + north before launching your rocket. +

    Ground Distance

    + This shows the distance across the ground to the + lat/lon where the rocket is located. Use this to + estimate what is currently under the rocket. +

    Latitude/Longitude

    + Displays the last known location of the rocket. +

    Apogee Igniter

    + This indicates whether the apogee + igniter has continuity. If the igniter has a low + resistance, then the voltage measured here will be close + to the Li-Po battery voltage. A value greater than 3.2V is + required for a 'GO' status. +

    Main Igniter

    + This indicates whether the main + igniter has continuity. If the igniter has a low + resistance, then the voltage measured here will be close + to the Li-Po battery voltage. A value greater than 3.2V is + required for a 'GO' status. +

    5.3. Recover

    + The 'Recover' tab shows information used while recovering the + rocket on the ground after flight. +

    + While the Recover tab is displayed, the voice announcements + will include distance along with either bearing or + direction, depending on whether you are moving. +

    Bearing

    + This is the aziumuth from true north for the rocket + from the android device. Use this in combination + with the Elevation value to help locate the rocket + in the sky, or at least to help point the antenna in + the general direction. This is provided in both + degrees and a compass point (like West South + West). You'll want to know which direction is true + north before launching your rocket. +

    Direction

    + When you are in motion, this provides the angle from + your current direction of motion towards the rocket. +

    Distance

    + Distance over the ground to the rocket. +

    Tar Lat/Tar Lon

    + Displays the last known location of the rocket. +

    My Lat/My Lon

    + Displays the location of the Android device. +

    Max Height

    + Shows the maximum height above launch pad. +

    Max Speed

    + Shows the maximum vertical speed seen during the flight. +

    Max Accel

    + Shows the maximum vertical acceleration seen during the flight. +

    5.4. Map

    + The 'Map' tab shows a map of the area around the rocket + being tracked along with information needed to recover it. +

    + On the map itself, icons showing the location of the android + device along with the last known location of each tracker. A + blue line is drawn from the android device location to the + currently selected tracker. +

    + Below the map, the distance and either bearing or direction + along with the lat/lon of the target and the android device + are shown +

    + The Map tab provides the same voice announcements as the + Recover tab. +

    6. Downloading Flight Logs

    AltosDroid always saves every bit of telemetry data it receives. To download that to a computer for use with AltosUI, - simply remove the SD card from your Android device, or connect - your device to your computer's USB port and browse the files - on that device. You will find '.telem' files in the TeleMetrum + remove the SD card from your Android device, or connect your + device to your computer's USB port and browse the files on + that device. You will find '.telem' files in the TeleMetrum directory that will work with AltosUI directly. -

    Chapter 8. Using Altus Metrum Products

    Table of Contents

    1. Being Legal
    2. In the Rocket
    3. On the Ground
    4. Data Analysis
    5. Future Plans

    1. Being Legal

    +

    Chapter 8. Using Altus Metrum Products

    Table of Contents

    1. Being Legal
    2. In the Rocket
    3. On the Ground
    4. Data Analysis
    5. Future Plans

    1. Being Legal

    First off, in the US, you need an amateur radio license or other authorization to legally operate the radio transmitters that are part of our products. -

    2. In the Rocket

    +

    2. In the Rocket

    In the rocket itself, you just need a flight computer and a single-cell, 3.7 volt nominal Li-Po rechargeable battery. An 850mAh battery weighs less than a 9V alkaline battery, and will @@ -2084,7 +2246,7 @@ NAR GPS antenna is fixed on all current products, so you really want to install the flight computer in a bay made of RF-transparent materials if at all possible. -

    3. On the Ground

    +

    3. On the Ground

    To receive the data stream from the rocket, you need an antenna and short feed-line connected to one of our TeleDongle units. If possible, use an SMA to BNC adapter instead of feedline between the antenna feedpoint and @@ -2146,7 +2308,7 @@ NAR TeleMetrum- or TeleMini- equipped rocket when used with a suitable 70cm HT. TeleDongle and an SMA to BNC adapter fit perfectly between the driven element and reflector of Arrow antennas. -

    4. Data Analysis

    +

    4. Data Analysis

    Our software makes it easy to log the data from each flight, both the telemetry received during the flight itself, and the more complete data log recorded in the flash memory on the altimeter @@ -2161,7 +2323,7 @@ NAR Our ultimate goal is to emit a set of files for each flight that can be published as a web page per flight, or just viewed on your local disk with a web browser. -

    5. Future Plans

    +

    5. Future Plans

    We have designed and prototyped several “companion boards” that can attach to the companion connector on TeleMetrum, TeleMega and EasyMega @@ -2181,14 +2343,14 @@ NAR Watch our web site for more news and information as our family of products evolves! -

    Chapter 9. Altimeter Installation Recommendations

    Table of Contents

    1. Mounting the Altimeter
    2. Dealing with the Antenna
    3. Preserving GPS Reception
    4. Radio Frequency Interference
    5. The Barometric Sensor
    6. Ground Testing

    +

    Chapter 9. Altimeter Installation Recommendations

    Table of Contents

    1. Mounting the Altimeter
    2. Dealing with the Antenna
    3. Preserving GPS Reception
    4. Radio Frequency Interference
    5. The Barometric Sensor
    6. Ground Testing

    Building high-power rockets that fly safely is hard enough. Mix in some sophisticated electronics and a bunch of radio energy and some creativity and/or compromise may be required. This chapter contains some suggestions about how to install Altus Metrum products into a rocket air-frame, including how to safely and reliably mix a variety of electronics into the same air-frame. -

    1. Mounting the Altimeter

    +

    1. Mounting the Altimeter

    The first consideration is to ensure that the altimeter is securely fastened to the air-frame. For most of our products, we prefer nylon standoffs and nylon screws; they're good to at least 50G @@ -2208,7 +2370,7 @@ NAR Watch for any metal touching components on the board. Shorting out connections on the bottom of the board can cause the altimeter to fail during flight. -

    2. Dealing with the Antenna

    +

    2. Dealing with the Antenna

    The antenna supplied is just a piece of solid, insulated, wire. If it gets damaged or broken, it can be easily replaced. It should be kept straight and not cut; bending or @@ -2251,7 +2413,7 @@ NAR SMA connector, and then run 50Ω coax from the board to the antenna. Building a remote antenna is beyond the scope of this manual. -

    3. Preserving GPS Reception

    +

    3. Preserving GPS Reception

    The GPS antenna and receiver used in TeleMetrum and TeleMega is highly sensitive and normally have no trouble tracking enough satellites to provide accurate position information for @@ -2270,7 +2432,7 @@ NAR antenna as that's covered with a ground plane. But, keep wires and metal out from above the patch antenna.

    -

    4. Radio Frequency Interference

    +

    4. Radio Frequency Interference

    Any altimeter will generate RFI; the digital circuits use high-frequency clocks that spray radio interference across a wide band. Altus Metrum altimeters generate intentional radio @@ -2308,7 +2470,7 @@ NAR 70cm amateur band, so you should avoid lengths that are a simple ratio of that length; essentially any multiple of ¼ of the wavelength (17.5cm). -

    5. The Barometric Sensor

    +

    5. The Barometric Sensor

    Altusmetrum altimeters measure altitude with a barometric sensor, essentially measuring the amount of air above the rocket to figure out how high it is. A large number of @@ -2326,7 +2488,7 @@ NAR the products of APCP or BP combustion, so make sure the ebay is carefully sealed from any compartment which contains ejection charges or motors. -

    6. Ground Testing

    +

    6. Ground Testing

    The most important aspect of any installation is careful ground testing. Bringing an air-frame up to the LCO table which hasn't been ground tested can lead to delays or ejection @@ -2348,10 +2510,10 @@ NAR interface through a TeleDongle to command each charge to fire. Make sure the charge is sufficient to robustly separate the air-frame and deploy the recovery system. -

    Chapter 10. Updating Device Firmware

    Table of Contents

    1. +

    Chapter 10. Updating Device Firmware

    Table of Contents

    1. Updating TeleMega, TeleMetrum v2, EasyMega, EasyMini or TeleDongle v3 Firmware -
    1.1. Recovering From Self-Flashing Failure
    2. Pair Programming
    3. Updating TeleMetrum v1.x Firmware
    4. Updating TeleMini Firmware
    5. Updating TeleDongle v0.2 Firmware

    +

    1.1. Recovering From Self-Flashing Failure
    2. Pair Programming
    3. Updating TeleMetrum v1.x Firmware
    4. Updating TeleMini Firmware
    5. Updating TeleDongle v0.2 Firmware

    TeleMega, TeleMetrum v2, EasyMega, EasyMini and TeleDongle v3 are all programmed directly over their USB connectors (self programming). TeleMetrum v1, TeleMini and TeleDongle v0.2 are @@ -2375,7 +2537,7 @@ NAR

    Self-programmable devices (TeleMega, TeleMetrum v2, EasyMega and EasyMini) are reprogrammed by connecting them to your computer over USB -

    1.  +

    1.  Updating TeleMega, TeleMetrum v2, EasyMega, EasyMini or TeleDongle v3 Firmware

    1. @@ -2404,7 +2566,7 @@ NAR Verify that the device is working by using the 'Configure Altimeter' or 'Configure Groundstation' item to check over the configuration. -

    1.1. Recovering From Self-Flashing Failure

    +

    1.1. Recovering From Self-Flashing Failure

    If the firmware loading fails, it can leave the device unable to boot. Not to worry, you can force the device to start the boot loader instead, which will let you try to @@ -2468,13 +2630,13 @@ NAR

  • Once the board has been powered up, you can remove the piece of wire. -

    • 2. Pair Programming

    +

    2. Pair Programming

    The big concept to understand is that you have to use a TeleMetrum v1.0, TeleBT v1.0 or TeleDongle v0.2 as a programmer to update a pair programmed device. Due to limited memory resources in the cc1111, we don't support programming directly over USB for these devices. -

    3. Updating TeleMetrum v1.x Firmware

    1. +

    3. Updating TeleMetrum v1.x Firmware

    1. Find the 'programming cable' that you got as part of the starter kit, that has a red 8-pin MicroMaTch connector on one end and a red 4-pin MicroMaTch connector on the other end. @@ -2517,7 +2679,7 @@ NAR the version, etc.

    2. If something goes wrong, give it another try. -

    4. Updating TeleMini Firmware

    1. +

    4. Updating TeleMini Firmware

    1. You'll need a special 'programming cable' to reprogram the TeleMini. You can make your own using an 8-pin MicroMaTch connector on one end and a set of four pins on the other. @@ -2560,7 +2722,7 @@ NAR letting it come up in “flight” mode and listening for telemetry.

    2. If something goes wrong, give it another try. -

    5. Updating TeleDongle v0.2 Firmware

    +

    5. Updating TeleDongle v0.2 Firmware

    Updating TeleDongle v0.2 firmware is just like updating TeleMetrum v1.x or TeleMini firmware, but you use either a TeleMetrum v1.x, TeleDongle @@ -2624,19 +2786,19 @@ NAR slightly to extract the connector. We used a locking connector on TeleMetrum to help ensure that the cabling to companion boards used in a rocket don't ever come loose accidentally in flight. -

    Chapter 11. Hardware Specifications

    Table of Contents

    1. +

    Chapter 11. Hardware Specifications

    Table of Contents

    1. TeleMega Specifications -
    2. +
    2. EasyMega Specifications -
    3. +
    3. TeleMetrum v2 Specifications -
    4. TeleMetrum v1 Specifications
    5. +
    4. TeleMetrum v1 Specifications
    5. TeleMini v2.0 Specifications -
    6. +
    6. TeleMini v1.0 Specifications -
    7. +
    7. EasyMini Specifications -

    1.  +

    1.  TeleMega Specifications

    • Recording altimeter for model rocketry. @@ -2666,7 +2828,7 @@ NAR to fire e-matches.

    • 3.25 x 1.25 inch board designed to fit inside 38mm air-frame coupler tube. -

    2.  +

    2.  EasyMega Specifications

    • Recording altimeter for model rocketry. @@ -2692,7 +2854,7 @@ NAR to fire e-matches.

    • 1.25 x 1.25 inch board designed to fit inside 38mm air-frame coupler tube. -

    3.  +

    3.  TeleMetrum v2 Specifications

    • Recording altimeter for model rocketry. @@ -2718,7 +2880,7 @@ NAR optional separate pyro battery if needed.

    • 2.75 x 1 inch board designed to fit inside 29mm air-frame coupler tube. -

    4. TeleMetrum v1 Specifications

    • +

    4. TeleMetrum v1 Specifications

    • Recording altimeter for model rocketry.

    • Supports dual deployment (can fire 2 ejection charges). @@ -2742,7 +2904,7 @@ NAR optional separate pyro battery if needed.

    • 2.75 x 1 inch board designed to fit inside 29mm air-frame coupler tube. -

    5.  +

    5.  TeleMini v2.0 Specifications

    • Recording altimeter for model rocketry. @@ -2764,7 +2926,7 @@ NAR optional separate pyro battery if needed.

    • 1.5 x .8 inch board designed to fit inside 24mm air-frame coupler tube. -

    6.  +

    6.  TeleMini v1.0 Specifications

    • Recording altimeter for model rocketry. @@ -2785,7 +2947,7 @@ NAR optional separate pyro battery if needed.

    • 1.5 x .5 inch board designed to fit inside 18mm air-frame coupler tube. -

    7.  +

    7.  EasyMini Specifications

    • Recording altimeter for model rocketry. @@ -2805,7 +2967,7 @@ NAR optional separate pyro battery if needed.

    • 1.5 x .8 inch board designed to fit inside 24mm air-frame coupler tube. -

    Chapter 12. FAQ

    +

    Chapter 12. FAQ

    TeleMetrum seems to shut off when disconnected from the computer. Make sure the battery is adequately charged. Remember the @@ -2850,7 +3012,7 @@ NAR data after physically retrieving your altimeter. Make sure to save the on-board data after each flight; while the TeleMetrum can store multiple flights, you never know when you'll lose the altimeter... -

    Appendix A. Notes for Older Software

    +

    Appendix A. Notes for Older Software

    Before AltosUI was written, using Altus Metrum devices required some finesse with the Linux command line. There was a limited @@ -3027,25 +3189,25 @@ NAR the Log and Device menus. It has a wonderful display of the incoming flight data and I am sure you will enjoy what it has to say to you once you enable the voice output! -

    Appendix B. Drill Templates

    Table of Contents

    1. TeleMega template
    2. EasyMega template
    3. TeleMetrum template
    4. TeleMini v2/EasyMini template
    5. TeleMini v1 template

    +

    Appendix B. Drill Templates

    Table of Contents

    1. TeleMega template
    2. EasyMega template
    3. TeleMetrum template
    4. TeleMini v2/EasyMini template
    5. TeleMini v1 template

    These images, when printed, provide precise templates for the mounting holes in Altus Metrum flight computers -

    1. TeleMega template

    +

    1. TeleMega template

    TeleMega has overall dimensions of 1.250 x 3.250 inches, and the mounting holes are sized for use with 4-40 or M3 screws. -

    2. EasyMega template

    +

    2. EasyMega template

    EasyMega has overall dimensions of 1.250 x 2.250 inches, and the mounting holes are sized for use with 4-40 or M3 screws. -

    3. TeleMetrum template

    +

    3. TeleMetrum template

    TeleMetrum has overall dimensions of 1.000 x 2.750 inches, and the mounting holes are sized for use with 4-40 or M3 screws. -

    4. TeleMini v2/EasyMini template

    +

    4. TeleMini v2/EasyMini template

    TeleMini v2 and EasyMini have overall dimensions of 0.800 x 1.500 inches, and the mounting holes are sized for use with 4-40 or M3 screws. -

    5. TeleMini v1 template

    +

    5. TeleMini v1 template

    TeleMini has overall dimensions of 0.500 x 1.500 inches, and the mounting holes are sized for use with 2-56 or M2 screws. -

    Appendix C. Calibration

    Table of Contents

    1. Radio Frequency
    2. TeleMetrum, TeleMega and EasyMega Accelerometers

    +

    Appendix C. Calibration

    Table of Contents

    1. Radio Frequency
    2. TeleMetrum, TeleMega and EasyMega Accelerometers

    There are only two calibrations required for TeleMetrum and TeleMega, and only one for EasyMega, TeleDongle, TeleMini and EasyMini. All boards are shipped from the factory pre-calibrated, but @@ -3054,7 +3216,7 @@ NAR connect to the board with a serial terminal program and interact directly with the on-board command interpreter to effect calibration. -

    1. Radio Frequency

    +

    1. Radio Frequency

    The radio frequency is synthesized from a clock based on the crystal on the board. The actual frequency of this oscillator must be measured to generate a calibration constant. While our @@ -3090,7 +3252,7 @@ NAR radio frequency is reset to the default 434.550 Mhz. If you want to use another frequency, you will have to set that again after calibration is completed. -

    2. TeleMetrum, TeleMega and EasyMega Accelerometers

    +

    2. TeleMetrum, TeleMega and EasyMega Accelerometers

    While barometric sensors are factory-calibrated, accelerometers are not, and so each must be calibrated once installed in a flight computer. Explicitly calibrating the @@ -3127,12 +3289,12 @@ NAR to the index post on the 4-pin end of the programming cable, and power up the board. It should come up in 'idle mode' (two beeps), allowing a re-cal. -

    Appendix D. Igniter Current

    Table of Contents

    1. Current Products
    2. Version 1 Products

    +

    Appendix D. Igniter Current

    Table of Contents

    1. Current Products
    2. Version 1 Products

    The question "how much igniter current can Altus Metrum products handle?" comes up fairly frequently. The short answer is "more than you're likely to need", the remainder of this appendix provides a longer answer. -

    1. Current Products

    +

    1. Current Products

    The FET switches we're using on all of our current products that have pyro channels are the Vishay Siliconix Si7232DN. These parts have exceptionally low Rds(on) values, better than 0.02 ohms! That @@ -3152,7 +3314,7 @@ NAR and build up pyrogen(s) as required to actually light what you're trying to light... But if you want to use a high-current igniter, we can probably handle it! -

    2. Version 1 Products

    +

    2. Version 1 Products

    The FET switches used on TeleMetrum v1 and TeleMini v1 products were Fairchild FDS9926A. The Rds(on) values under our operating conditions are on the order of 0.04 ohms. These parts were rated @@ -3164,7 +3326,105 @@ NAR specs on these parts aren't as good as the ones we use on current products, they were still great, and we never had a complaint about current carrying capacity with any of our v1 boards. -

    Appendix E. Release Notes

    Version 1.6

    +

    Appendix E. Release Notes

    Version 1.6.1

    + Version 1.6.1 includes support for our updated TeleBT v3.0 + product and bug fixes in in the flight software for all our boards + and ground station interfaces. +

    + AltOS New Features +

    • + Add support for TeleBT v3.0 boards. +

    • + Add support for uncompressed APRS data, providing support + for older APRS receivers. Uncompressed APRS data is less + precise, takes more bandwidth and doesn't have integrated + altitude data. +

    +

    + AltOS Fixes +

    • + Make TeleDongle and TeleBT more tolerant of data rate + variations from transmitting devices. +

    +

    + AltosUI and TeleGPS New Features +

    • + Add map to Monitor Idle display. It's nice to be able to + verify that maps are working, instead of needing to use + Monitor Flight. +

    +

    + AltosUI Fixes +

    • + Fix frequency configuration to round values instead of + truncate them, avoiding a common 1kHz error in the setting. +

    • + Turn the Windows stub into a more useful program that can + launch the application with parameters so that file manager + icons work more reliably. +

    • + Force KML export to use a C locale so that numbers are + formatted with '.' instead of ',' for a decimal separator in + non-US locales. +

    • + Preload map tiles based on distance rather than number of + tiles; this means you get the same resolution covering the + entire area, rather than having high resolution near the + center and low resolution further away. +

    • + Allow configuration of frequency and callsign in Monitor + Idle mode. +

    • + Fix layout weirdness when resizing windows on + Windows. Windows shouldn't have giant blank spaces around + the useful content anymore. +

    • + Fix layout weirdness when resizing windows on + Windows. Windows shouldn't have giant blank spaces around + the useful content anymore. +

    • + Use a longer filter for descent speed values. This should + provide something more useful on the display, although it + will take longer to respond to changes now. +

    • + Make Replay Flight run in realtime again. It had been set to + run at 10x speed by mistake. +

    +

    + AltosDroid New Features +

    • + Add offline map support using mapping code from AltosUI. +

    • + Support TeleDongle (and TeleBT via USB) on devices + supporting USB On-The-Go. +

    • + Display additional TeleMega pyro channel status in Pad tab. +

    • + Switch between metric and imperial units. +

    • + Monitor TeleBT battery voltage. +

    • + Track multiple devices at the same time, selecting between + them with a menu or using the map. +

    • + Add hybrid, satellite and terrain map types. +

    +

    + AltosDroid Fixes +

    • + Use standard Android display conventions so that a menu + button is available in the application title bar. +

    • + Adjust layout to work on large and small screens; shrinking + the go/no-go lights in smaller environments to try and make + everything visible. +

    • + Make voice announcements depend on current tab. +

    • + Compute adjustment to current travel direction while in + motion towards rocket. +

    +

    Version 1.6

    Version 1.6 includes support for our updated TeleDongle v3.0 product and bug fixes in in the flight software for all our boards and ground station interfaces. @@ -3246,7 +3506,7 @@ NAR information each time we change channels. This avoids having flight computers appear on multiple frequencies by accident.

    -

    Version 1.5

    +

    Version 1.5

    Version 1.5 is a major release. It includes support for our new EasyMega product, new features and bug fixes in in the flight software for all our boards and the AltosUI ground station @@ -3313,7 +3573,7 @@ NAR provide the user with the option to skip installing Java for cases where we just can't figure out what version is installed.

    -

    Version 1.4.1

    +

    Version 1.4.1

    Version 1.4.1 is a minor release. It fixes install issues on Windows and provides the missing TeleMetrum V2.0 firmware. There aren't any changes to the firmware or host applications at @@ -3344,7 +3604,7 @@ NAR release didn't have this key in the released version of the software, making map downloading fail for most people.

    -

    Version 1.4

    +

    Version 1.4

    Version 1.4 is a major release. It includes support for our new TeleGPS product, new features and bug fixes in in the flight software for all our boards and the AltosUI ground station @@ -3457,7 +3717,7 @@ NAR prevents the apogee charge from firing for a configurable amount of time after boost.

    -

    Version 1.3.2

    +

    Version 1.3.2

    Version 1.3.2 is a minor release. It includes small bug fixes for the TeleMega flight software and AltosUI ground station

    @@ -3485,7 +3745,7 @@ NAR Use letters (A, B, C, D) for alternate pyro channel names instead of numbers (0, 1, 2, 3) in the Fire Igniter dialog.

    -

    Version 1.3.1

    +

    Version 1.3.1

    Version 1.3.1 is a minor release. It improves support for TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini.

    @@ -3527,7 +3787,7 @@ NAR Google to make sure we stay within their limits so that all of the map tiles download successfully.

    -

    Version 1.3

    +

    Version 1.3

    Version 1.3 is a major release. It adds support for TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini.

    @@ -3568,7 +3828,7 @@ NAR

  • Save the last log directory and offer that as the default for new downloads

    • -

    Version 1.2.1

    +

    Version 1.2.1

    Version 1.2.1 is a minor release. It adds support for TeleBT and the AltosDroid application, provides several new features in AltosUI and fixes some bugs in the AltOS firmware. @@ -3628,7 +3888,7 @@ NAR a complete summary of the flight without needing to 'replay' the whole thing.

    -

    Version 1.2

    +

    Version 1.2

    Version 1.2 is a major release. It adds support for MicroPeak and the MicroPeak USB adapter.

    @@ -3654,7 +3914,7 @@ NAR Altus Metrum software packages to be installed in the same directory at the same time.

    -

    Version 1.1.1

    +

    Version 1.1.1

    Version 1.1.1 is a bug-fix release. It fixes a couple of bugs in AltosUI and one firmware bug that affects TeleMetrum version 1.0 boards. Thanks to Bob Brown for help diagnosing the Google Earth @@ -3699,7 +3959,7 @@ NAR from the flight computer was missing a check for TeleMini when deciding whether to fetch the analog sensor data.

    -

    Version 1.1

    +

    Version 1.1

    Version 1.1 is a minor release. It provides a few new features in AltosUI and the AltOS firmware and fixes bugs.

    @@ -3771,7 +4031,7 @@ NAR Add Imperial units mode to present data in feet instead of meters.

    -

    Version 1.0.1

    +

    Version 1.0.1

    Version 1.0.1 is a major release, adding support for the TeleMini device and lots of new AltosUI features

    @@ -3851,7 +4111,7 @@ NAR Flight window so you can immediately see the results of a flight.

    -

    Version 0.9.2

    +

    Version 0.9.2

    Version 0.9.2 is an AltosUI bug-fix release, with no firmware changes.

    • Fix plotting problems due to missing file in the Mac OS install image. @@ -3859,7 +4119,7 @@ NAR Always read whole eeprom blocks, mark empty records invalid, display parsing errors to user.

    • Add software version to Configure AltosUI dialog -

    Version 0.9

    +

    Version 0.9

    Version 0.9 adds a few new firmware features and accompanying AltosUI changes, along with new hardware support.

    • @@ -3878,7 +4138,7 @@ NAR provided only 8 bits for the device serial number. This change requires that both ends of the telemetry link be running the 0.9 firmware or they will not communicate. -

    Version 0.8

    +

    Version 0.8

    Version 0.8 offers a major upgrade in the AltosUI interface. Significant new features include:

    • @@ -3918,7 +4178,7 @@ NAR Exports Google Earth flight tracks. Using the Keyhole Markup Language (.kml) file format, this provides a 3D view of your rocket flight through the Google Earth program. -

    Version 0.7.1

    +

    Version 0.7.1

    Version 0.7.1 is the first release containing our new cross-platform Java-based user interface. AltosUI can:

    • Receive and log telemetry from a connected TeleDongle -- cgit v1.2.3