From: Bdale Garbee Date: Wed, 11 Jul 2018 03:13:20 +0000 (-0600) Subject: update docs X-Git-Url: https://git.gag.com/?a=commitdiff_plain;h=a31cca9c2dc51fed37213e2dda1b16370c6c09b8;p=web%2Faltusmetrum update docs --- diff --git a/AltOS/doc/altos.pdf b/AltOS/doc/altos.pdf index bb19b78..9516d83 100644 Binary files a/AltOS/doc/altos.pdf and b/AltOS/doc/altos.pdf differ diff --git a/AltOS/doc/altusmetrum.html b/AltOS/doc/altusmetrum.html index ca41d4c..4fff799 100644 --- a/AltOS/doc/altusmetrum.html +++ b/AltOS/doc/altusmetrum.html @@ -19,12 +19,20 @@ collaborators, and we certainly appreciate this level of contribution!

Have fun using these products, and we hope to meet all of you out on the rocket flight line somewhere.

Bdale Garbee, KB0G
NAR #87103, TRA #12201

Keith Packard, KD7SQG
-NAR #88757, TRA #12200

Table of Contents

1. Introduction and Overview
2. Getting Started
2.1. Batteries
2.2. Ground Station Hardware
2.3. Linux/Mac/Windows Ground Station Software
2.4. Android Ground Station Software
3. Using Altus Metrum Hardware
3.1. Wiring and Electrical Interference
3.2. Hooking Up Lithium Polymer Batteries
3.3. Hooking Up Pyro Charges
3.4. Hooking Up a Power Switch
3.5. Understanding Beeps
3.6. Turning On the Power
3.7. Using an External Active Switch Circuit
3.8. Using a Separate Pyro Battery
3.9. Using a Different Kind of Battery
4. TeleMetrum
4.1. TeleMetrum Screw Terminals
4.2. Using a Separate Pyro Battery with TeleMetrum
4.3. Using an Active Switch with TeleMetrum
5. TeleMini
5.1. TeleMini v3 Screw Terminals
5.2. Using a Separate Pyro Battery with TeleMini v3
5.3. Using an Active Switch with TeleMini v3
5.4. TeleMini v1
6. EasyMini
6.1. EasyMini Screw Terminals
6.2. Connecting A Battery To EasyMini
6.3. Charging Lithium Batteries
6.4. Using a Separate Pyro Battery with EasyMini
6.5. 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. Installation
10. Using Altus Metrum Products
10.1. Being Legal
10.2. In the Rocket
10.3. On the Ground
10.4. Data Analysis
10.5. Future Plans
11. AltosUI
11.1. Monitor Flight
11.1.1. Launch Pad
11.1.2. Ascent
11.1.3. Descent
11.1.4. Landed
11.1.5. Table
11.1.6. Site Map
11.1.7. Igniter
11.2. Save Flight Data
11.3. Replay Flight
11.4. Graph Data
11.4.1. Flight Graph
11.4.2. Configure Graph
11.4.3. Flight Statistics
11.4.4. Map
11.5. Export Data
11.5.1. Comma Separated Value Format
11.5.2. Keyhole Markup Language (for Google Earth)
11.6. Configure Altimeter
11.6.1. Main Deploy Altitude
11.6.2. Apogee Delay
11.6.3. Apogee Lockout
11.6.4. Frequency
11.6.5. RF Calibration
11.6.6. Telemetry/RDF/APRS Enable
11.6.7. Telemetry baud rate
11.6.8. APRS Interval
11.6.9. APRS SSID
11.6.10. APRS Format
11.6.11. Callsign
11.6.12. Maximum Flight Log Size
11.6.13. Ignitor Firing Mode
11.6.14. Pad Orientation
11.6.15. Beeper Frequency
11.6.16. Logging Trigger Motion
11.6.17. Position Reporting Interval
11.6.18. Calibrate Accelerometer
11.6.19. Configure Pyro Channels
11.7. Configure AltosUI
11.7.1. Voice Settings
11.7.2. Log Directory
11.7.3. Callsign
11.7.4. Imperial Units
11.7.5. Serial Debug
11.7.6. Font size
11.7.7. Look & feel
11.7.8. Menu position
11.7.9. Map Cache Size
11.7.10. Manage Frequencies
11.8. Configure Groundstation
11.8.1. Frequency
11.8.2. RF Calibration
11.8.3. Telemetry Rate
11.9. Flash Image
11.10. Fire Igniter
11.11. Scan Channels
11.12. Load Maps
11.13. Monitor Idle
12. AltosDroid
12.1. Installing AltosDroid
12.2. Charging TeleBT Battery
12.3. Connecting to TeleBT over Bluetooth™
12.4. Connecting to TeleDongle or TeleBT over USB
12.5. AltosDroid Menu
12.6. Setup
12.7. Idle Mode
12.8. AltosDroid Flight Monitoring
12.9. Pad
12.10. Flight
12.11. Recover
12.12. Map
12.13. Downloading Flight Logs
A. System Operation
A.1. Firmware Modes
A.2. GPS
A.3. Controlling An Altimeter Over The Radio Link
A.4. Ground Testing
A.5. Radio Link
A.6. APRS
A.7. Configurable Parameters
B. Handling Precautions
C. Updating Device Firmware
C.1. Updating TeleMega, TeleMetrum v2, EasyMega, EasyMini or TeleDongle v3 Firmware
C.1.1. Recovering From Self-Flashing Failure
C.2. Pair Programming
C.2.1. Updating TeleMetrum v1.x Firmware
C.2.2. Updating TeleMini v1.0 Firmware
C.2.3. Updating TeleDongle v0.2 Firmware
D. Flight Data Recording
E. Altus Metrum Hardware Specifications
F. Release Notes
F.1. Release Notes for Version 1.8.5
F.1.1. AltOS
F.1.2. AltosUI, TeleGPS
F.2. Release Notes for Version 1.8.4
F.2.1. AltOS
F.3. Release Notes for Version 1.8.3
F.3.1. AltOS
F.3.2. AltosUI and TeleGPS Applications
F.4. Release Notes for Version 1.8.2
F.4.1. AltOS
F.4.2. AltosUI and TeleGPS Applications
F.5. Release Notes for Version 1.8.1
F.5.1. AltOS
F.5.2. AltosUI and TeleGPS Applications
F.6. Release Notes for Version 1.8
F.6.1. AltOS
F.6.2. AltosUI and TeleGPS Applications
F.7. Release Notes for Version 1.7
F.7.1. AltOS
F.7.2. AltosUI and TeleGPS Applications
F.8. Release Notes for Version 1.6.8
F.8.1. AltOS
F.8.2. AltosUI, TeleGPS and AltosDroid Applications
F.9. Release Notes for Version 1.6.5
F.9.1. AltOS
F.9.2. AltosUI, TeleGPS and AltosDroid Applications
F.10. Release Notes for Version 1.6.4
F.10.1. AltOS
F.10.2. AltosUI, TeleGPS and AltosDroid Applications
F.10.3. Documentation
F.11. Release Notes for Version 1.6.3
F.11.1. AltOS
F.11.2. AltosUI and TeleGPS Applications
F.11.3. AltosDroid
F.11.4. Documentation
F.12. Release Notes for Version 1.6.2
F.12.1. AltOS
F.12.2. AltosUI and TeleGPS Applications
F.12.3. Documentation
F.13. Release Notes for Version 1.6.1
F.13.1. AltOS
F.13.2. AltosUI and TeleGPS Applications
F.13.3. AltosDroid
F.14. Release Notes for Version 1.6
F.14.1. AltOS
F.14.2. AltosUI and TeleGPS Applications
F.15. Release Notes for Version 1.5
F.15.1. AltOS
F.15.2. AltosUI and TeleGPS Applications
F.16. Release Notes for Version 1.4.2
F.16.1. AltosUI and TeleGPS Applications
F.17. Release Notes for Version 1.4.1
F.17.1. AltosUI and TeleGPS Applications:
F.18. Release Notes for Version 1.4
F.18.1. AltOS
F.18.2. AltosUI Application
F.18.3. TeleGPS Application
F.18.4. Documentation
F.19. Release Notes for Version 1.3.2
F.19.1. AltOS
F.19.2. AltosUI Application
F.20. Release Notes for Version 1.3.1
F.20.1. AltOS
F.20.2. AltosUI Application
F.21. Release Notes for Version 1.3
F.21.1. AltOS
F.21.2. AltosUI Application
F.22. Release Notes for Version 1.2.1
F.22.1. AltOS
F.22.2. AltosUI Application
F.22.3. AltosDroid
F.23. Release Notes for Version 1.2
F.23.1. AltOS
F.23.2. AltosUI and MicroPeak Application
F.24. Release Notes for Version 1.1
F.24.1. AltOS
F.24.2. AltosUI
F.25. Release Notes for Version 1.1
F.25.1. AltOS
F.25.2. AltosUI
F.26. Release Notes for Version 1.0.1
F.26.1. AltOS
F.26.2. AltosUI Application
F.27. Release Notes for Version 0.9.2
F.27.1. AltosUI
F.28. Release Notes for Version 0.9
F.28.1. AltOS
F.28.2. AltosUI Application
F.29. Release Notes for Version 0.8
F.29.1. AltosUI Application:
F.30. Release Notes for Version 0.7.1
F.30.1. AltosUI Application

List of Figures

4.1. TeleMetrum v2 Board
4.2. TeleMetrum v1 Board
5.1. TeleMini v3 Board
5.2. TeleMini v1 Board
6.1. EasyMini Board
7.1. TeleMega Board
8.1. EasyMega Board
11.1. AltosUI Main Window
11.2. Device Selection Dialog
11.3. Monitor Flight Launch Pad View
11.4. Monitor Flight Ascent View
11.5. Monitor Flight Descent View
11.6. Monitor Flight Landed View
11.7. Monitor Flight Table View
11.8. Monitor Flight Site Map View
11.9. Monitor Flight Additional Igniter View
11.10. Flight Data Graph
11.11. Flight Graph Configuration
11.12. Flight Statistics
11.13. Flight Map
11.14. Altimeter Configuration
11.15. Additional Pyro Channel Configuration
11.16. Configure AltosUI Dialog
11.17. Configure Groundstation Dialog
11.18. Fire Igniter Window
11.19. Scan Channels Window
11.20. Load Maps Window
11.21. Monitor Idle Window

List of Tables

3.1. AltOS Modes
3.2. Pad/Idle Indications
3.3. Pad Radio Indications
4.1. TeleMetrum Screw Terminals
5.1. TeleMini v3 Screw Terminals
6.1. EasyMini Screw Terminals
7.1. TeleMega Screw Terminals
8.1. EasyMega Screw Terminals
A.1. Altus Metrum APRS Comments
D.1. Data Storage on Altus Metrum altimeters
E.1. Altus Metrum Flight Computer Electronics
E.2. Altus Metrum Flight Computer Mechanical Components

Chapter 1. Introduction and Overview

Welcome to the Altus Metrum community! Our circuits and software reflect +NAR #88757, TRA #12200

Table of Contents

1. Introduction and Overview
2. Getting Started
2.1. Batteries
2.2. Ground Station Hardware
2.3. Linux/Mac/Windows Ground Station Software
2.4. Android Ground Station Software
3. Using Altus Metrum Hardware
3.1. Wiring and Electrical Interference
3.2. Hooking Up Lithium Polymer Batteries
3.3. Hooking Up Pyro Charges
3.4. Hooking Up a Power Switch
3.5. Understanding Beeps
3.6. Turning On the Power
3.7. Using an External Active Switch Circuit
3.8. Using a Separate Pyro Battery
3.9. Using a Different Kind of Battery
4. TeleMetrum
4.1. TeleMetrum Screw Terminals
4.2. Using a Separate Pyro Battery with TeleMetrum
4.3. Using an Active Switch with TeleMetrum
5. TeleMini
5.1. TeleMini v3 Screw Terminals
5.2. Using a Separate Pyro Battery with TeleMini v3
5.3. Using an Active Switch with TeleMini v3
5.4. TeleMini v1
6. EasyMini
6.1. EasyMini Screw Terminals
6.2. Connecting A Battery To EasyMini
6.3. Charging Lithium Batteries
6.4. Using a Separate Pyro Battery with EasyMini
6.5. 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. Installation
10. Using Altus Metrum Products
10.1. Being Legal
10.2. In the Rocket
10.3. On the Ground
10.4. Data Analysis
10.5. Future Plans
11. AltosUI
11.1. Monitor Flight
11.1.1. Launch Pad
11.1.2. Ascent
11.1.3. Descent
11.1.4. Landed
11.1.5. Table
11.1.6. Site Map
11.1.7. Igniter
11.2. Save Flight Data
11.3. Replay Flight
11.4. Graph Data
11.4.1. Flight Graph
11.4.2. Configure Graph
11.4.3. Flight Statistics
11.4.4. Map
11.5. Export Data
11.5.1. Comma Separated Value Format
11.5.2. Keyhole Markup Language (for Google Earth)
11.6. Configure Altimeter
11.6.1. Main Deploy Altitude
11.6.2. Apogee Delay
11.6.3. Apogee Lockout
11.6.4. Frequency
11.6.5. RF Calibration
11.6.6. Telemetry/RDF/APRS Enable
11.6.7. Telemetry baud rate
11.6.8. APRS Interval
11.6.9. APRS SSID
11.6.10. APRS Format
11.6.11. Callsign
11.6.12. Maximum Flight Log Size
11.6.13. Ignitor Firing Mode
11.6.14. Pad Orientation
11.6.15. Beeper Frequency
11.6.16. Logging Trigger Motion
11.6.17. Position Reporting Interval
11.6.18. Calibrate Accelerometer
11.6.19. Configure Pyro Channels
11.7. Configure AltosUI
11.7.1. Voice Settings
11.7.2. Log Directory
11.7.3. Callsign
11.7.4. Imperial Units
11.7.5. Serial Debug
11.7.6. Font size
11.7.7. Look & feel
11.7.8. Menu position
11.7.9. Map Cache Size
11.7.10. Manage Frequencies
11.8. Configure Groundstation
11.8.1. Frequency
11.8.2. RF Calibration
11.8.3. Telemetry Rate
11.9. Flash Image
11.10. Fire Igniter
11.11. Scan Channels
11.12. Load Maps
11.13. Monitor Idle
12. AltosDroid
12.1. Installing AltosDroid
12.2. Charging TeleBT Battery
12.3. Connecting to TeleBT over Bluetooth™
12.4. Connecting to TeleDongle or TeleBT over USB
12.5. AltosDroid Menu
12.6. Setup
12.7. Idle Mode
12.8. AltosDroid Flight Monitoring
12.9. Pad
12.10. Flight
12.11. Recover
12.12. Map
12.13. Downloading Flight Logs
A. System Operation
A.1. Firmware Modes
A.2. GPS
A.3. Controlling An Altimeter Over The Radio Link
A.4. Ground Testing
A.5. Radio Link
A.6. APRS
A.7. Configurable Parameters
B. Handling Precautions
C. Updating Device Firmware
C.1. Updating TeleMega, TeleMetrum v2, EasyMega, EasyMini or TeleDongle v3 Firmware
C.1.1. Recovering From Self-Flashing Failure
C.2. Pair Programming
C.2.1. Updating TeleMetrum v1.x Firmware
C.2.2. Updating TeleMini v1.0 Firmware
C.2.3. Updating TeleDongle v0.2 Firmware
D. Flight Data Recording
E. Altus Metrum Hardware Specifications
F. Release Notes
F.1. Release Notes for Version 1.8.5
F.1.1. AltOS
F.1.2. AltosUI, TeleGPS
F.2. Release Notes for Version 1.8.4
F.2.1. AltOS
F.3. Release Notes for Version 1.8.3
F.3.1. AltOS
F.3.2. AltosUI and TeleGPS Applications
F.4. Release Notes for Version 1.8.2
F.4.1. AltOS
F.4.2. AltosUI and TeleGPS Applications
F.5. Release Notes for Version 1.8.1
F.5.1. AltOS
F.5.2. AltosUI and TeleGPS Applications
F.6. Release Notes for Version 1.8
F.6.1. AltOS
F.6.2. AltosUI and TeleGPS Applications
F.7. Release Notes for Version 1.7
F.7.1. AltOS
F.7.2. AltosUI and TeleGPS Applications
F.8. Release Notes for Version 1.6.8
F.8.1. AltOS
F.8.2. AltosUI, TeleGPS and AltosDroid Applications
F.9. Release Notes for Version 1.6.5
F.9.1. AltOS
F.9.2. AltosUI, TeleGPS and AltosDroid Applications
F.10. Release Notes for Version 1.6.4
F.10.1. AltOS
F.10.2. AltosUI, TeleGPS and AltosDroid Applications
F.10.3. Documentation
F.11. Release Notes for Version 1.6.3
F.11.1. AltOS
F.11.2. AltosUI and TeleGPS Applications
F.11.3. AltosDroid
F.11.4. Documentation
F.12. Release Notes for Version 1.6.2
F.12.1. AltOS
F.12.2. AltosUI and TeleGPS Applications
F.12.3. Documentation
F.13. Release Notes for Version 1.6.1
F.13.1. AltOS
F.13.2. AltosUI and TeleGPS Applications
F.13.3. AltosDroid
F.14. Release Notes for Version 1.6
F.14.1. AltOS
F.14.2. AltosUI and TeleGPS Applications
F.15. Release Notes for Version 1.5
F.15.1. AltOS
F.15.2. AltosUI and TeleGPS Applications
F.16. Release Notes for Version 1.4.2
F.16.1. AltosUI and TeleGPS Applications
F.17. Release Notes for Version 1.4.1
F.17.1. AltosUI and TeleGPS Applications:
F.18. Release Notes for Version 1.4
F.18.1. AltOS
F.18.2. AltosUI Application
F.18.3. TeleGPS Application
F.18.4. Documentation
F.19. Release Notes for Version 1.3.2
F.19.1. AltOS
F.19.2. AltosUI Application
F.20. Release Notes for Version 1.3.1
F.20.1. AltOS
F.20.2. AltosUI Application
F.21. Release Notes for Version 1.3
F.21.1. AltOS
F.21.2. AltosUI Application
F.22. Release Notes for Version 1.2.1
F.22.1. AltOS
F.22.2. AltosUI Application
F.22.3. AltosDroid
F.23. Release Notes for Version 1.2
F.23.1. AltOS
F.23.2. AltosUI and MicroPeak Application
F.24. Release Notes for Version 1.1
F.24.1. AltOS
F.24.2. AltosUI
F.25. Release Notes for Version 1.1
F.25.1. AltOS
F.25.2. AltosUI
F.26. Release Notes for Version 1.0.1
F.26.1. AltOS
F.26.2. AltosUI Application
F.27. Release Notes for Version 0.9.2
F.27.1. AltosUI
F.28. Release Notes for Version 0.9
F.28.1. AltOS
F.28.2. AltosUI Application
F.29. Release Notes for Version 0.8
F.29.1. AltosUI Application:
F.30. Release Notes for Version 0.7.1
F.30.1. AltosUI Application

List of Figures

4.1. TeleMetrum v2 Board
4.2. TeleMetrum v1 Board
5.1. TeleMini v3 Board
5.2. TeleMini v1 Board
6.1. EasyMini Board
7.1. TeleMega Board
8.1. EasyMega Board
11.1. AltosUI Main Window
11.2. Device Selection Dialog
11.3. Monitor Flight Launch Pad View
11.4. Monitor Flight Ascent View
11.5. Monitor Flight Descent View
11.6. Monitor Flight Landed View
11.7. Monitor Flight Table View
11.8. Monitor Flight Site Map View
11.9. Monitor Flight Additional Igniter View
11.10. Flight Data Graph
11.11. Flight Graph Configuration
11.12. Flight Statistics
11.13. Flight Map
11.14. Altimeter Configuration
11.15. Additional Pyro Channel Configuration
11.16. Configure AltosUI Dialog
11.17. Configure Groundstation Dialog
11.18. Fire Igniter Window
11.19. Scan Channels Window
11.20. Load Maps Window
11.21. Monitor Idle Window

List of Tables

3.1. AltOS Modes
3.2. Pad/Idle Indications
3.3. Pad Radio Indications
4.1. TeleMetrum Screw Terminals
5.1. TeleMini v3 Screw Terminals
6.1. EasyMini Screw Terminals
7.1. TeleMega Screw Terminals
8.1. EasyMega Screw Terminals
A.1. Altus Metrum APRS Comments
D.1. Data Storage on Altus Metrum altimeters
E.1. Altus Metrum Flight Computer Electronics
E.2. Altus Metrum Flight Computer Mechanical Components

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 releasing all of our hardware and software designs under open licenses, we also hope to empower you to take as active a role in our collective -future as you wish!

The first device created for our community was TeleMetrum, a dual +future as you wish!

Our goal is to include in this document all of the information required +to successfully configure and use Altus Metrum products. But +documentation is a lot like software in that it can contain "bugs", +and can probably always be improved! If you have questions that +aren’t answered in this manual, or just need a little help figuring +things out, we strongly suggest joining the Altus Metrum user email +list, which you can do by visiting +https://lists.gag.com/mailman/listinfo/altusmetrum. There’s a lot +of useful information in the mailing list archives!

The first device created for our community was TeleMetrum, a dual deploy altimeter with fully integrated GPS and radio telemetry as standard features, and a “companion interface” that will support optional capabilities in the future. The latest version @@ -148,13 +156,13 @@ beeping that accompanies each 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 3.1. AltOS Modes

Mode Name

Abbreviation

Beeps

Description

Startup

S

battery voltage in decivolts

Calibrating sensors, detecting orientation.

Idle

I

dit dit

Ready to accept commands over USB +a long dissonant tone.

Table 3.1. AltOS Modes

Mode Name

Abbreviation

Beeps

Description

Startup

S

battery voltage in decivolts

Calibrating sensors, detecting orientation.

Idle

I

dit dit

Ready to accept commands over USB or radio link.

Pad

P

dit dah dah dit

Waiting for launch. Not listening for commands.

Boost

B

dah dit dit dit

Accelerating upwards.

Fast

F

dit dit dah dit

Decelerating, but moving faster than 200m/s.

Coast

C

dah dit dah dit

Decelerating, moving slower than 200m/s

Drogue

D

dah dit dit

Descending after apogee. Above main height.

Main

M

dah dah

Descending. Below main height.

Landed

L

dit dah dit dit

Stable altitude for at least ten seconds.

Sensor error

X

dah dit dit dah

Error detected during sensor calibration.


Here’s a summary of all of the Pad and Idle mode indications. In Idle mode, you’ll hear one of these just once after the two short dits indicating idle mode. In Pad mode, after the dit dah dah dit indicating Pad mode, you’ll hear these once every five -seconds.

Table 3.2. Pad/Idle Indications

Name Beeps Description

Neither

brap

No continuity detected on either apogee or main igniters.

Apogee

dit

Continuity detected only on apogee igniter.

Main

dit dit

Continuity detected only on main igniter.

Both

dit dit dit

Continuity detected on both igniters.

Storage Full

warble

On-board data logging storage is full. This will +seconds.

Table 3.2. Pad/Idle Indications

Name Beeps Description

Neither

brap

No continuity detected on either apogee or main igniters.

Apogee

dit

Continuity detected only on apogee igniter.

Main

dit dit

Continuity detected only on main igniter.

Both

dit dit dit

Continuity detected on both igniters.

Storage Full

warble

On-board data logging storage is full. This will not prevent the flight computer from safely controlling the flight or transmitting telemetry signals, but no record of the flight will be @@ -166,7 +174,7 @@ primary igniter channels.


Table 3.3. Pad Radio Indications

Name Beeps Description

Neither

½ second tone

No continuity detected on either apogee or main igniters.

Apogee

dit

Continuity detected only on apogee igniter.

Main

dit dit

Continuity detected only on main igniter.

Both

dit dit dit

Continuity detected on both igniters.


During ascent, the tones will be muted to allow the +igniter status once every five seconds.

Table 3.3. Pad Radio Indications

Name Beeps Description

Neither

½ second tone

No continuity detected on either apogee or main igniters.

Apogee

dit

Continuity detected only on apogee igniter.

Main

dit dit

Continuity detected only on main igniter.

Both

dit dit dit

Continuity detected on both igniters.


During ascent, the tones will be muted to allow the telemetry data to consume the full radio bandwidth.

During descent and after landing, a ½ second tone will be transmitted every five seconds. This can be used to find the rocket using RDF techniques when the signal @@ -236,7 +244,7 @@ battery.

Chapter 4. TeleMetrum

Figure 4.1. TeleMetrum v2 Board

telemetrum-v2.0-th.jpg

Figure 4.2. TeleMetrum v1 Board

telemetrum-v1.1-thside.jpg

TeleMetrum is a 1 inch by 2¾ inch circuit board. It was designed to +the board.

Chapter 4. TeleMetrum

Figure 4.1. TeleMetrum v2 Board

telemetrum-v2.0-th.jpg

Figure 4.2. TeleMetrum v1 Board

telemetrum-v1.1-thside.jpg

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 to succeed! The presence of an accelerometer means TeleMetrum should @@ -257,7 +265,7 @@ screw terminals in the same position.

Table 4.1. TeleMetrum Screw Terminals

Terminal #Terminal NameDescription

1

Switch Output

Switch connection to flight computer

2

Switch Input

Switch connection to positive battery terminal

3

Main +

Main pyro channel common connection to battery

4

Main -

Main pyro channel connection to pyro circuit

5

Apogee +

Apogee pyro channel common connection to battery

6

Apogee -

Apogee pyro channel connection to pyro circuit


4.2. Using a Separate Pyro Battery with TeleMetrum

As described above, using an external pyro battery involves +the terminals are as follows:

Table 4.1. TeleMetrum Screw Terminals

Terminal #Terminal NameDescription

1

Switch Output

Switch connection to flight computer

2

Switch Input

Switch connection to positive battery terminal

3

Main +

Main pyro channel common connection to battery

4

Main -

Main pyro channel connection to pyro circuit

5

Apogee +

Apogee pyro channel common connection to battery

6

Apogee -

Apogee pyro channel connection to pyro circuit


4.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 one of the igniter leads and connecting the other igniter @@ -273,7 +281,7 @@ connections, one to the positive battery terminal, one to the flight computer positive input and one to ground.

The positive battery terminal is available on screw terminal 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.

Chapter 5. TeleMini

Figure 5.1. TeleMini v3 Board

telemini-v3.0-top.jpg

telemini-v3.0-bottom.jpg

TeleMini v3 is 0.5 inches by 1.67 inches. It was +gauge stranded, to the GND hole just above terminal 1.

Chapter 5. TeleMini

Figure 5.1. TeleMini v3 Board

telemini-v3.0-top.jpg

telemini-v3.0-bottom.jpg

TeleMini v3 is 0.5 inches by 1.67 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 mounting and wiring to succeed! Since there is no @@ -291,7 +299,7 @@ screw terminals are located in the middle of the board for the power switch. Using the picture above and starting from the top for the pyro terminals and from the left for the power switch terminals, the -connections are as follows:

Table 5.1. TeleMini v3 Screw Terminals

Terminal #Terminal NameDescription

1

Apogee -

Apogee pyro channel connection to pyro circuit

2

Apogee

Apogee pyro channel common connection to battery

3

Main -

Main pyro channel connection to pyro circuit

4

Main

Main pyro channel common connection to battery

Left

Switch Output

Switch connection to flight computer

Right

Switch Input

Switch connection to positive battery terminal


5.2. Using a Separate Pyro Battery with TeleMini v3

As described above, using an external pyro battery involves +connections are as follows:

Table 5.1. TeleMini v3 Screw Terminals

Terminal #Terminal NameDescription

1

Apogee -

Apogee pyro channel connection to pyro circuit

2

Apogee

Apogee pyro channel common connection to battery

3

Main -

Main pyro channel connection to pyro circuit

4

Main

Main pyro channel common connection to battery

Left

Switch Output

Switch connection to flight computer

Right

Switch Input

Switch connection to positive battery terminal


5.2. Using a Separate Pyro Battery with TeleMini v3

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 one of the igniter leads and connecting the other igniter @@ -314,7 +322,7 @@ the left power switch wire. Hook a lead to either of the mounting holes for a ground connection.

5.4. TeleMini v1

TeleMini v1 is the earlier version of this product. It has a lower-power radio, less storage, no beeper and soldered-in wires instead of screw terminals for the -power switch.

Figure 5.2. TeleMini v1 Board

telemini-v1-top.jpg

Chapter 6. EasyMini

Figure 6.1. EasyMini Board

easymini-top.jpg

EasyMini is built on a 0.8 inch by 1½ inch circuit board. It’s +power switch.

Figure 5.2. TeleMini v1 Board

telemini-v1-top.jpg

Chapter 6. EasyMini

Figure 6.1. EasyMini Board

easymini-top.jpg

EasyMini is built on a 0.8 inch by 1½ inch circuit board. It’s designed to fit in a 24mm coupler tube.

You usually don’t need to configure EasyMini at all; it’s set up to do dual-deployment with an event at apogee to separate the airframe and deploy a drogue and another event at 250m @@ -325,7 +333,7 @@ board. 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 6.1. EasyMini Screw Terminals

Terminal #Terminal NameDescription

Top 1

Main -

Main pyro channel connection to pyro circuit

Top 2

Main

Main pyro channel common connection to battery

Top 3

Battery

Positive external battery terminal

Top 4

Battery -

Negative external battery terminal

Bottom 1

Apogee -

Apogee pyro channel connection to pyro circuit

Bottom 2

Apogee

Apogee pyro channel common connection to battery

Bottom 3

Switch Output

Switch connection to flight computer

Bottom 4

Switch Input

Switch connection to positive battery terminal


6.2. Connecting A Battery To EasyMini

There are two possible battery connections on +switch. Counting from the left, the connections are as follows:

Table 6.1. EasyMini Screw Terminals

Terminal #Terminal NameDescription

Top 1

Main -

Main pyro channel connection to pyro circuit

Top 2

Main

Main pyro channel common connection to battery

Top 3

Battery

Positive external battery terminal

Top 4

Battery -

Negative external battery terminal

Bottom 1

Apogee -

Apogee pyro channel connection to pyro circuit

Bottom 2

Apogee

Apogee pyro channel common connection to battery

Bottom 3

Switch Output

Switch connection to flight computer

Bottom 4

Switch Input

Switch connection to positive battery terminal


6.2. Connecting A Battery To EasyMini

There are two possible battery connections on EasyMini. You can use either method; both feed through the power switch terminals.

One battery connection is the standard Altus Metrum white JST plug. This mates with single-cell Lithium @@ -353,7 +361,7 @@ the flight computer positive input and one to ground. Use the negative external battery connection, top terminal 4 for ground.

The positive battery terminal is available on bottom terminal 4, the positive flight computer input is on the -bottom terminal 3.

Chapter 7. TeleMega

Figure 7.1. TeleMega Board

telemega-v1.0-top.jpg

TeleMega is a 1¼ inch by 3¼ inch circuit board. It was +bottom terminal 3.

Chapter 7. TeleMega

Figure 7.1. TeleMega Board

telemega-v1.0-top.jpg

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 @@ -368,7 +376,7 @@ Radio switched from cc1120 to cc1200. they do mean that the device needs different firmware to operate correctly, so make sure you load the right firmware when reflashing the device.

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 7.1. TeleMega Screw Terminals

Terminal #Terminal NameDescription

Top 1

Switch Input

Switch connection to positive battery terminal

Top 2

Switch Output

Switch connection to flight computer

Top 3

GND

Ground connection for use with external active switch

Top 4

Main -

Main pyro channel connection to pyro circuit

Top 5

Main

Main pyro channel common connection to battery

Top 6

Apogee -

Apogee pyro channel connection to pyro circuit

Top 7

Apogee

Apogee pyro channel common connection to battery

Top 8

D -

D pyro channel connection to pyro circuit

Top 9

D

D pyro channel common connection to battery

Bottom 1

GND

Ground connection for negative pyro battery terminal

Bottom 2

Pyro

Positive pyro battery terminal

Bottom 3

Lipo

Power switch output. Use to connect main battery to pyro battery input

Bottom 4

A -

A pyro channel connection to pyro circuit

Bottom 5

A

A pyro channel common connection to battery

Bottom 6

B -

B pyro channel connection to pyro circuit

Bottom 7

B

B pyro channel common connection to battery

Bottom 8

C -

C pyro channel connection to pyro circuit

Bottom 9

C

C pyro channel common connection to battery


7.2. Using a Separate Pyro Battery with TeleMega

TeleMega provides explicit support for an external pyro +the board opposite the telemetry antenna. They are as follows:

Table 7.1. TeleMega Screw Terminals

Terminal #Terminal NameDescription

Top 1

Switch Input

Switch connection to positive battery terminal

Top 2

Switch Output

Switch connection to flight computer

Top 3

GND

Ground connection for use with external active switch

Top 4

Main -

Main pyro channel connection to pyro circuit

Top 5

Main

Main pyro channel common connection to battery

Top 6

Apogee -

Apogee pyro channel connection to pyro circuit

Top 7

Apogee

Apogee pyro channel common connection to battery

Top 8

D -

D pyro channel connection to pyro circuit

Top 9

D

D pyro channel common connection to battery

Bottom 1

GND

Ground connection for negative pyro battery terminal

Bottom 2

Pyro

Positive pyro battery terminal

Bottom 3

Lipo

Power switch output. Use to connect main battery to pyro battery input

Bottom 4

A -

A pyro channel connection to pyro circuit

Bottom 5

A

A pyro channel common connection to battery

Bottom 6

B -

B pyro channel connection to pyro circuit

Bottom 7

B

B pyro channel common connection to battery

Bottom 8

C -

C pyro channel connection to pyro circuit

Bottom 9

C

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 (Bottom 2). Then hook the negative pyro battery terminal to ground @@ -384,12 +392,12 @@ wire from the Lipo terminal (Bottom 3) to the Pyro terminal connections, one to the positive battery terminal, one to the flight computer positive input and one to ground.

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.

Chapter 8. EasyMega

Figure 8.1. EasyMega Board

easymega-v1.0-top.jpg

EasyMega is a 1¼ inch by 2¼ inch circuit board. It was +2. Ground is on Top terminal 3.

Chapter 8. EasyMega

Figure 8.1. EasyMega Board

easymega-v1.0-top.jpg

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

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

Table 8.1. EasyMega Screw Terminals

Terminal #Terminal NameDescription

Top 1

Switch Input

Switch connection to positive battery terminal

Top 2

Switch Output

Switch connection to flight computer

Top 3

GND

Ground connection for use with external active switch

Top 4

Main -

Main pyro channel connection to pyro circuit

Top 5

Main

Main pyro channel common connection to battery

Top 6

Apogee -

Apogee pyro channel connection to pyro circuit

Top 7

Apogee

Apogee pyro channel common connection to battery

Top 8

D -

D pyro channel connection to pyro circuit

Top 9

D

D pyro channel common connection to battery

Bottom 1

GND

Ground connection for negative pyro battery terminal

Bottom 2

Pyro

Positive pyro battery terminal

Bottom 3

Lipo

Power switch output. Use to connect main battery to pyro battery input

Bottom 4

A -

A pyro channel connection to pyro circuit

Bottom 5

A

A pyro channel common connection to battery

Bottom 6

B -

B pyro channel connection to pyro circuit

Bottom 7

B

B pyro channel common connection to battery

Bottom 8

C -

C pyro channel connection to pyro circuit

Bottom 9

C

C pyro channel common connection to battery


8.2. Using a Separate Pyro Battery with EasyMega

EasyMega provides explicit support for an external pyro +the board opposite the telemetry antenna. They are as follows:

Table 8.1. EasyMega Screw Terminals

Terminal #Terminal NameDescription

Top 1

Switch Input

Switch connection to positive battery terminal

Top 2

Switch Output

Switch connection to flight computer

Top 3

GND

Ground connection for use with external active switch

Top 4

Main -

Main pyro channel connection to pyro circuit

Top 5

Main

Main pyro channel common connection to battery

Top 6

Apogee -

Apogee pyro channel connection to pyro circuit

Top 7

Apogee

Apogee pyro channel common connection to battery

Top 8

D -

D pyro channel connection to pyro circuit

Top 9

D

D pyro channel common connection to battery

Bottom 1

GND

Ground connection for negative pyro battery terminal

Bottom 2

Pyro

Positive pyro battery terminal

Bottom 3

Lipo

Power switch output. Use to connect main battery to pyro battery input

Bottom 4

A -

A pyro channel connection to pyro circuit

Bottom 5

A

A pyro channel common connection to battery

Bottom 6

B -

B pyro channel connection to pyro circuit

Bottom 7

B

B pyro channel common connection to battery

Bottom 8

C -

C pyro channel connection to pyro circuit

Bottom 9

C

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 (Bottom 2). Then hook the negative pyro battery terminal to ground @@ -558,7 +566,7 @@ feel free to dive in and help! Or let us know what you’d like to see that we aren’t already working on, and maybe we’ll get excited about it too…

Watch our web site for more news and information as our family of products -evolves!

Chapter 11. AltosUI

Figure 11.1. AltosUI Main Window

altosui.png

The AltosUI program provides a graphical user interface for +evolves!

Chapter 11. AltosUI

Figure 11.1. AltosUI Main Window

altosui.png

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 tasks. The primary interface window provides a selection of @@ -568,7 +576,7 @@ the tasks provided from the top-level toolbar.

Figure 11.2. Device Selection Dialog

device-selection.png

All telemetry data received are automatically recorded +device.

Figure 11.2. Device Selection Dialog

device-selection.png

All telemetry data received are automatically recorded in suitable log files. The name of the files includes the current date and rocket serial and flight numbers.

The radio frequency being monitored by the TeleDongle device is displayed at the top of the window. You can @@ -615,7 +623,7 @@ automatically switches to display 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.

11.1.1. Launch Pad

Figure 11.3. Monitor Flight Launch Pad View

launch-pad.png

The Launch Pad tab shows information used to decide when the +spreadsheet-like format.

11.1.1. Launch Pad

Figure 11.3. Monitor Flight Launch Pad View

launch-pad.png

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 whether the rocket is ready to launch:

@@ -673,7 +681,7 @@ GPS receiver has reliable reception from the satellites.

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

11.1.2. Ascent

Figure 11.4. Monitor Flight Ascent View

ascent.png

This tab is shown during Boost, Fast and Coast +positions to improve the accuracy of the fix.

11.1.2. Ascent

Figure 11.4. Monitor Flight Ascent View

ascent.png

This tab is shown during Boost, Fast and Coast phases. The information displayed here helps monitor the rocket as it heads towards apogee.

The height, speed, acceleration and tilt are shown along with the maximum values for each of them. This allows you to @@ -684,7 +692,7 @@ may not get updated as the GPS receiver loses position fix. Once the rocket starts coasting, the receiver should start reporting position again.

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.

11.1.3. Descent

Figure 11.5. Monitor Flight Descent View

descent.png

Once the rocket has reached apogee and (we hope) +caused by wiring which comes loose under high acceleration.

11.1.3. Descent

Figure 11.5. Monitor Flight Descent View

descent.png

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, waiting for the main charge @@ -710,7 +718,7 @@ see what the status of the apogee charge is. Note that some commercial 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.

11.1.4. Landed

Figure 11.6. Monitor Flight Landed View

landed.png

Once the rocket is on the ground, attention switches +firing.

11.1.4. Landed

Figure 11.6. Monitor Flight Landed View

landed.png

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 generally within a short distance of the @@ -732,11 +740,11 @@ depends on the quality of your radio link and how many packets were received. Recovering the on-board data after flight may yield more precise results.

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.

11.1.5. Table

Figure 11.7. Monitor Flight Table View

table.png

The table view shows all of the data available from the +bring up a graph window for the current flight.

11.1.5. Table

Figure 11.7. Monitor Flight Table View

table.png

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.

11.1.6. Site Map

Figure 11.8. Monitor Flight Site Map View

site-map.png

When the TeleMetrum has a GPS fix, the Site Map tab +information about the signal being received from the satellites.

11.1.6. Site Map

Figure 11.8. Monitor Flight Site Map View

site-map.png

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 rocket’s state is @@ -755,7 +763,7 @@ units will be shown at the start of the line.

Images are fetched automatic Static API, and cached on disk for reuse. If map images cannot be downloaded, the rocket’s path will be traced on a dark gray background instead.

You can pre-load images for your favorite launch sites -before you leave home; check out Section 11.12, “Load Maps”.

11.1.7. Igniter

Figure 11.9. Monitor Flight Additional Igniter View

ignitor.png

TeleMega includes four additional programmable pyro +before you leave home; check out Section 11.12, “Load Maps”.

11.1.7. Igniter

Figure 11.9. Monitor Flight Additional Igniter View

ignitor.png

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 @@ -800,7 +808,7 @@ record file, either a .telem file recording telemetry data or a flash memory.

Note that telemetry files will generally produce poor graphs due to the lower sampling rate and missed telemetry packets. Use saved flight data in .eeprom files for graphing where possible.

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

11.4.1. Flight Graph

Figure 11.10. Flight Data Graph

graph.png

By default, the graph contains acceleration (blue), +opened.

11.4.1. Flight Graph

Figure 11.10. Flight Data Graph

graph.png

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

The graph can be zoomed into a particular area by clicking and dragging down and to the right. Once zoomed, the graph can be reset by clicking and @@ -808,7 +816,7 @@ dragging up and to the left. Holding down 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.

11.4.2. Configure Graph

Figure 11.11. Flight Graph Configuration

graph-configure.png

This selects which graph elements to show, and, at the +plot.

11.4.2. Configure Graph

Figure 11.11. Flight Graph Configuration

graph-configure.png

This selects which graph elements to show, and, at the very bottom. It also lets you configure how the graph is drawn:

  • Whether to use metric or imperial units @@ -829,7 +837,7 @@ descent. Flight computers without accelerometers always compute both speed and acceleration from barometric data. A larger value smooths the data more. -

11.4.3. Flight Statistics

Figure 11.12. Flight Statistics

graph-stats.png

Shows overall data computed from the flight.

11.4.4. Map

Figure 11.13. Flight Map

graph-map.png

Shows a satellite image of the flight area overlaid +

11.4.3. Flight Statistics

Figure 11.12. Flight Statistics

graph-stats.png

Shows overall data computed from the flight.

11.4.4. Map

Figure 11.13. Flight Map

graph-map.png

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.

11.5. Export Data

This tool takes the raw data files and makes them @@ -856,7 +864,7 @@ standard units, with the barometric data reported in both pressure, altitude and height above pad units.

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

11.6. Configure Altimeter

Figure 11.14. Altimeter Configuration

configure-altimeter.png

Select this button and then select either an altimeter or +in 3D.

11.6. Configure Altimeter

Figure 11.14. Altimeter Configuration

configure-altimeter.png

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.

The first few lines of the dialog provide information about the @@ -1020,7 +1028,7 @@ flight computer with the antenna end, or end opposite the screw terminals, in the case of EasyMega, first up and then down.

When the calibration is complete, return to the Configure Altimeter window and save the new -calibration values.

11.6.19. Configure Pyro Channels

Figure 11.15. Additional Pyro Channel Configuration

configure-pyro.png

This opens a separate window to configure the +calibration values.

11.6.19. Configure Pyro Channels

Figure 11.15. Additional Pyro Channel Configuration

configure-pyro.png

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 @@ -1040,43 +1048,38 @@ channels, you can save the pyro configuration along with the rest of the flight computer configuration by pressing the Save button in the main Configure Flight Computer window.

-Acceleration -
-Select a value, and then choose -whether acceleration should be above or below -that value. Acceleration is positive upwards, -so accelerating towards the ground would -produce negative numbers. Acceleration during -descent is noisy and inaccurate, so be careful -when using it during these phases of the -flight. +Vertical Acceleration +
+Select a value, and then choose whether +acceleration away from the ground should be above or below that +value. Acceleration is positive upwards, so accelerating towards the +ground would produce negative numbers. Acceleration during descent is +noisy and inaccurate, so be careful when using it during these phases +of the flight.
-Vertical speed +Ascent rate
-Select a value, and then -choose whether vertical speed should be above -or below that value. Speed is positive -upwards, so moving towards the ground would -produce negative numbers. Speed during descent -is a bit noisy and so be careful when using it +Select a value, and then choose whether ascent rate +should be above or below that value. Ascent rate is positive upwards, +so moving towards the ground would produce negative numbers. Ascent +rate during descent is a bit noisy and so be careful when using it during these phases of the flight.
-Height +Height above pad
-Select a value, and then choose -whether the height above the launch pad should -be above or below that value. +Select a value, and then choose whether the height +above the launch pad should be above or below that value.
Orientation
-TeleMega and EasyMega contain a -3-axis gyroscope and accelerometer which is -used to measure the current angle. Note that -this angle is not the change in angle from the -launch pad, but rather absolute relative to -gravity; the 3-axis accelerometer is used to -compute the angle of the rocket on the launch -pad and initialize the system. +TeleMega and EasyMega contain a 3-axis gyroscope and +accelerometer which is used to compute the orientation of the +rocket. A record of orientations over the last 0.64 seconds is kept +and the largest value within this period is compared with the +specified value. Note that the tilt angle is not the change in angle +from the launch pad, but rather absolute relative to gravity—the +3-axis accelerometer is used to compute the angle of the rocket on the +launch pad and initialize the system.

Note

Because this value is computed by integrating rate gyros, it gets progressively less accurate as the flight goes on. It should have @@ -1097,13 +1100,15 @@ time.

Ascending
-A simple test saying whether the rocket is going up or -not. This is exactly equivalent to testing whether the speed is > 0. +A deprecated configuration value which was the same as +setting Ascent rate > 0. Existing configurations using this will be +cleared and must be reconfigured by the user.
Descending
-A simple test saying whether the rocket is going down or -not. This is exactly equivalent to testing whether the speed is < 0. +A deprecated configuration value which was the same as +setting Ascent rate < 0. Existing configurations using this will be +cleared and must be reconfigured by the user.
After Motor
@@ -1114,9 +1119,12 @@ launches.
Delay
-This value doesn’t perform any checks, instead it inserts a -delay between the time when the other parameters become true and when -the pyro channel is activated. +Once the other parameters all become true, a timer is +started for the specified amount of time. While the timer is running, +the other parameters are checked repeatedly and if any of them become +false, then the pyro channel is disabled and will not fire. If the +timer expires and all of the other parameters have remained true for +the entire time, then the pyro channel is fired.
Flight State

@@ -1124,22 +1132,36 @@ The flight software tracks the flight through a sequence of states:

  • Boost. The motor has lit and the rocket is -accelerating upwards. +accelerating upwards. Ascent rate will be greater than zero. +Vertical acceleration will be greater than zero.
  • Fast. The motor has burned out and the rocket is decelerating, but it is going -faster than 200m/s. +faster than 200m/s. Ascent rate will be greater than zero. Vertical +acceleration will be less than zero.
  • Coast. The rocket is still moving upwards -and decelerating, but the speed is less -than 200m/s. +and decelerating, but the Ascent rate is less +than 200m/s. Ascent rate will greater than zero. Vertical +acceleration will be less than zero.
  • Drogue. The rocket has reached apogee and is heading back down, but is above the -configured Main altitude. +configured Main altitude. Ascent rate will be less than zero during +this state. Vertical acceleration will be negative until the rocket +reaches a terminal descent rate, at which point Vertical +acceleration will be zero. Both Ascent rate and Vertical +acceleration are very noisy in this state, so be careful when +trying to use them to control pyro channels.
  • Main. The rocket is still descending, and -is below the Main altitude +is below the Main altitude. Ascent rate will be less than zero +during this state. Vertical acceleration may be briefly less than +zero as the rocket slows from drogue descent to main descent, but +it will settle down to a zero value once the rocket has reached the +terminal velocity under the main chute. Ascent rate and Vertical +acceleration should be much less noisy once the main chute has +deployed.
  • Landed. The rocket is no longer moving.

You can select a state to limit when the pyro channel may activate; @@ -1147,7 +1169,7 @@ note that the check is based on when the rocket transitions

When a motor burns out, the rocket enters either Fast or Coast state (depending on how fast it is moving). If the computer detects upwards -acceleration again, it will move back to Boost state.

11.7. Configure AltosUI

Figure 11.16. Configure AltosUI Dialog

configure-altosui.png

This button presents a dialog so that you can +acceleration again, it will move back to Boost state.

11.7. Configure AltosUI

Figure 11.16. Configure AltosUI Dialog

configure-altosui.png

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

11.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 @@ -1212,7 +1234,7 @@ 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.

11.8. Configure Groundstation

Figure 11.17. Configure Groundstation Dialog

configure-groundstation.png

Select this button and then select a TeleDongle or +menus.

11.8. Configure Groundstation

Figure 11.17. Configure Groundstation Dialog

configure-groundstation.png

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 connected device, including the product name, software version and hardware serial @@ -1267,7 +1289,7 @@ EasyMini and TeleDongle v3 are all programmed directly over USB (self programming). Please read the directions for flashing devices in -Appendix C, Updating Device Firmware.

11.10. Fire Igniter

Figure 11.18. Fire Igniter Window

fire-igniter.png

This activates the igniter circuits in the flight +Appendix C, Updating Device Firmware.

11.10. Fire Igniter

Figure 11.18. Fire Igniter Window

fire-igniter.png

This activates the igniter circuits in the flight computer to help test recovery systems deployment. Because this command can operate over the @@ -1283,15 +1305,19 @@ button. The word Arm is replaced by a cou timer indicating that 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.11. Scan Channels

Figure 11.19. Scan Channels Window

scan-channels.png

This listens for telemetry packets on all of the +igniter.

11.11. Scan Channels

Figure 11.19. Scan Channels Window

scan-channels.png

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.

11.12. Load Maps

Figure 11.20. Load Maps Window

load-maps.png

Before heading out to a new launch site, you can use +later firmware.

11.12. Load Maps

Figure 11.20. Load Maps Window

load-maps.png

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.

There’s a drop-down menu of launch sites we know +internet connectivity at the site. Try not to wait +until the last minute, though, particularly if you’re +heading to a major launch. If too many people are +all trying to download map data at once, Google may +limit access until the next day.

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 and name of the site. The contents of this list are actually downloaded from our server at @@ -1337,7 +1363,7 @@ 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.

11.13. Monitor Idle

Figure 11.21. Monitor Idle Window

monitor-idle.png

This brings up a dialog similar to the Monitor Flight +you. Try again later.

11.13. Monitor Idle

Figure 11.21. Monitor Idle Window

monitor-idle.png

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 listening for telemetry @@ -1950,7 +1976,7 @@ same time while keeping the identify of each one separate in the receiver. By default, the SSID is set to the last digit of the device serial number.

The APRS packet format includes a comment field that can have arbitrary text in it. AltOS uses this to send -status information as shown in the following table.

Table A.1. Altus Metrum APRS Comments

Field Example Description

1

L

GPS Status U for unlocked, L for locked

2

6

Number of Satellites in View

3

B4.0

Altimeter Battery Voltage

4

A3.7

Apogee Igniter Voltage

5

M3.7

Main Igniter Voltage

6

1286

Device Serial Number

4

1286

Device Serial Number


Here’s an example of an APRS comment showing GPS lock with 6 +status information as shown in the following table.

Table A.1. Altus Metrum APRS Comments

Field Example Description

1

L

GPS Status U for unlocked, L for locked

2

6

Number of Satellites in View

3

B4.0

Altimeter Battery Voltage

4

A3.7

Apogee Igniter Voltage

5

M3.7

Main Igniter Voltage

6

1286

Device Serial Number

4

1286

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

L6 B4.0 A3.7 M3.7 1286

Here’s an example of an APRS comment showing GPS lock with 6 satellites in view and a primary battery at 4.0V from device 1876.

L6 B4.0 1876

Make sure your primary battery is above 3.8V @@ -2303,7 +2329,7 @@ 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 D.1. Data Storage on Altus Metrum altimeters

Device Bytes per Sample Total Storage Minutes at Full Rate

TeleMetrum v1.0

8

1MB

20

TeleMetrum v1.1 v1.2

8

2MB

40

TeleMetrum v2.0

16

8MB

80

TeleMini v1.0

2

5kB

4

TeleMini v3.0

16

512kB

5

EasyMini

16

1MB

10

TeleMega

32

8MB

40

EasyMega

32

8MB

40


The on-board flash is partitioned into separate flight logs, +several equal-sized blocks, one for each flight.

Table D.1. Data Storage on Altus Metrum altimeters

Device Bytes per Sample Total Storage Minutes at Full Rate

TeleMetrum v1.0

8

1MB

20

TeleMetrum v1.1 v1.2

8

2MB

40

TeleMetrum v2.0

16

8MB

80

TeleMini v1.0

2

5kB

4

TeleMini v3.0

16

512kB

5

EasyMini

16

1MB

10

TeleMega

32

8MB

40

EasyMega

32

8MB

40


The on-board flash is partitioned into separate flight logs, each of a fixed maximum size. Increase the maximum size of each log and you reduce the number of flights that can be stored. Decrease the size and you can store more flights.

Configuration data is also stored in the flash memory on @@ -2332,7 +2358,7 @@ flight data, so be sure to download flight data and erase it 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.

Appendix E. Altus Metrum Hardware Specifications

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

Table E.1. Altus Metrum Flight Computer Electronics

Device Barometer Z-axis accel GPS 3D sensors Storage RF Output Battery

TeleMetrum v1.0

MP3H6115 10km (33k')

MMA2202 50g

SkyTraq

-

1MB

10mW

3.7V

TeleMetrum v1.1

MP3H6115 10km (33k')

MMA2202 50g

SkyTraq

-

2MB

10mW

3.7V

TeleMetrum v1.2

MP3H6115 10km (33k')

ADXL78 70g

SkyTraq

-

2MB

10mW

3.7V

TeleMetrum v2.0

MS5607 30km (100k')

MMA6555 102g

uBlox Max-7Q

-

8MB

40mW

3.7V

TeleMini v1.0

MP3H6115 10km (33k')

-

-

-

5kB

10mW

3.7V

TeleMini v3.0

MS5607 30km (100k')

-

-

-

512kB

40mW

3.7V

EasyMini v1.0

MS5607 30km (100k')

-

-

-

1MB

-

3.7-12V

TeleMega v1.0

MS5607 30km (100k')

MMA6555 102g

uBlox Max-7Q

MPU6000 HMC5883

8MB

40mW

3.7V

TeleMega v2.0

MS5607 30km (100k')

MMA6555 102g

uBlox Max-7Q

MPU6000 HMC5883

8MB

40mW

3.7V

EasyMega v1.0

MS5607 30km (100k')

MMA6555 102g

-

MPU6000 HMC5883

8MB

-

3.7V


Table E.2. Altus Metrum Flight Computer Mechanical Components

DeviceConnectorsScrew TerminalsWidthLengthTube Size

TeleMetrum

Antenna Debug Companion USB Battery

Apogee pyro Main pyro Switch

1 inch (2.54cm)

2 ¾ inch (6.99cm)

29mm coupler

TeleMini v1.0

Antenna Debug Battery

Apogee pyro Main pyro

½ inch (1.27cm)

1½ inch (3.81cm)

18mm coupler

TeleMini v2.0

Antenna Debug USB Battery

Apogee pyro Main pyro Battery Switch

0.8 inch (2.03cm)

1½ inch (3.81cm)

24mm coupler

EasyMini

Debug USB Battery

Apogee pyro Main pyro Battery

0.8 inch (2.03cm)

1½ inch (3.81cm)

24mm coupler

TeleMega

Antenna Debug Companion USB Battery

Apogee pyro Main pyro Pyro A-D Switch Pyro battery

1¼ inch (3.18cm)

3¼ inch (8.26cm)

38mm coupler

EasyMega

Debug Companion USB Battery

Apogee pyro Main pyro Pyro A-D Switch Pyro battery

1¼ inch (3.18cm)

2¼ inch (5.62cm)

38mm coupler


Appendix F. Release Notes

F.1. Release Notes for Version 1.8.5

Version 1.8.5 includes fixes to the ground software support +production and retired.

Table E.1. Altus Metrum Flight Computer Electronics

Device Barometer Z-axis accel GPS 3D sensors Storage RF Output Battery

TeleMetrum v1.0

MP3H6115 10km (33k')

MMA2202 50g

SkyTraq

-

1MB

10mW

3.7V

TeleMetrum v1.1

MP3H6115 10km (33k')

MMA2202 50g

SkyTraq

-

2MB

10mW

3.7V

TeleMetrum v1.2

MP3H6115 10km (33k')

ADXL78 70g

SkyTraq

-

2MB

10mW

3.7V

TeleMetrum v2.0

MS5607 30km (100k')

MMA6555 102g

uBlox Max-7Q

-

8MB

40mW

3.7V

TeleMini v1.0

MP3H6115 10km (33k')

-

-

-

5kB

10mW

3.7V

TeleMini v3.0

MS5607 30km (100k')

-

-

-

512kB

40mW

3.7V

EasyMini v1.0

MS5607 30km (100k')

-

-

-

1MB

-

3.7-12V

TeleMega v1.0

MS5607 30km (100k')

MMA6555 102g

uBlox Max-7Q

MPU6000 HMC5883

8MB

40mW

3.7V

TeleMega v2.0

MS5607 30km (100k')

MMA6555 102g

uBlox Max-7Q

MPU6000 HMC5883

8MB

40mW

3.7V

EasyMega v1.0

MS5607 30km (100k')

MMA6555 102g

-

MPU6000 HMC5883

8MB

-

3.7V


Table E.2. Altus Metrum Flight Computer Mechanical Components

DeviceConnectorsScrew TerminalsWidthLengthTube Size

TeleMetrum

Antenna Debug Companion USB Battery

Apogee pyro Main pyro Switch

1 inch (2.54cm)

2 ¾ inch (6.99cm)

29mm coupler

TeleMini v1.0

Antenna Debug Battery

Apogee pyro Main pyro

½ inch (1.27cm)

1½ inch (3.81cm)

18mm coupler

TeleMini v2.0

Antenna Debug USB Battery

Apogee pyro Main pyro Battery Switch

0.8 inch (2.03cm)

1½ inch (3.81cm)

24mm coupler

EasyMini

Debug USB Battery

Apogee pyro Main pyro Battery

0.8 inch (2.03cm)

1½ inch (3.81cm)

24mm coupler

TeleMega

Antenna Debug Companion USB Battery

Apogee pyro Main pyro Pyro A-D Switch Pyro battery

1¼ inch (3.18cm)

3¼ inch (8.26cm)

38mm coupler

EasyMega

Debug Companion USB Battery

Apogee pyro Main pyro Pyro A-D Switch Pyro battery

1¼ inch (3.18cm)

2¼ inch (5.62cm)

38mm coupler


Appendix F. Release Notes

F.1. Release Notes for Version 1.8.5

Version 1.8.5 includes fixes to the ground software support for TeleBT v4, along with a few other minor updates.

F.1.1. AltOS

  • Fix startup beeps that indicate sensor failures.

F.1.2. AltosUI, TeleGPS

  • diff --git a/AltOS/doc/altusmetrum.pdf b/AltOS/doc/altusmetrum.pdf index 92fcd23..ac8409b 100644 Binary files a/AltOS/doc/altusmetrum.pdf and b/AltOS/doc/altusmetrum.pdf differ diff --git a/AltOS/doc/companion.pdf b/AltOS/doc/companion.pdf index f9f728c..aa6db3c 100644 Binary files a/AltOS/doc/companion.pdf and b/AltOS/doc/companion.pdf differ diff --git a/AltOS/doc/easymega-outline.pdf b/AltOS/doc/easymega-outline.pdf index e69de29..d25de2f 100644 Binary files a/AltOS/doc/easymega-outline.pdf and b/AltOS/doc/easymega-outline.pdf differ diff --git a/AltOS/doc/easymini-outline.pdf b/AltOS/doc/easymini-outline.pdf index e69de29..a51ce35 100644 Binary files a/AltOS/doc/easymini-outline.pdf and b/AltOS/doc/easymini-outline.pdf differ diff --git a/AltOS/doc/easymini.html b/AltOS/doc/easymini.html index f1079cc..ce70029 100644 --- a/AltOS/doc/easymini.html +++ b/AltOS/doc/easymini.html @@ -19,12 +19,20 @@ collaborators, and we certainly appreciate this level of contribution!

    Have fun using these products, and we hope to meet all of you out on the rocket flight line somewhere.

    Bdale Garbee, KB0G
    NAR #87103, TRA #12201

    Keith Packard, KD7SQG
    -NAR #88757, TRA #12200

Table of Contents

1. Introduction and Overview
2. Getting Started
2.1. Batteries
2.2. Linux/Mac/Windows Ground Station Software
3. Using Altus Metrum Hardware
3.1. Wiring and Electrical Interference
3.2. Hooking Up Lithium Polymer Batteries
3.3. Hooking Up Pyro Charges
3.4. Hooking Up a Power Switch
3.5. Understanding Beeps
3.6. Turning On the Power
3.7. Using an External Active Switch Circuit
3.8. Using a Separate Pyro Battery
3.9. Using a Different Kind of Battery
4. EasyMini
4.1. EasyMini Screw Terminals
4.2. Connecting A Battery To EasyMini
4.3. Charging Lithium Batteries
4.4. Using a Separate Pyro Battery with EasyMini
4.5. Using an Active Switch with EasyMini
5. Installation
6. Using Altus Metrum Products
6.1. In the Rocket
6.2. On the Ground
6.3. Data Analysis
6.4. Future Plans
7. AltosUI
7.1. Save Flight Data
7.2. Replay Flight
7.3. Graph Data
7.3.1. Flight Graph
7.3.2. Configure Graph
7.3.3. Flight Statistics
7.4. Export Data
7.4.1. Comma Separated Value Format
7.5. Configure Altimeter
7.5.1. Main Deploy Altitude
7.5.2. Apogee Delay
7.5.3. Apogee Lockout
7.5.4. Maximum Flight Log Size
7.5.5. Ignitor Firing Mode
7.5.6. Beeper Frequency
7.6. Configure AltosUI
7.6.1. Log Directory
7.6.2. Imperial Units
7.6.3. Serial Debug
7.6.4. Font size
7.6.5. Look & feel
7.6.6. Menu position
7.7. Flash Image
7.8. Fire Igniter
A. System Operation
A.1. Firmware Modes
A.2. Ground Testing
A.3. Configurable Parameters
B. Handling Precautions
C. Updating Device Firmware
C.1. Updating EasyMini Firmware
C.1.1. Recovering From Self-Flashing Failure
D. Flight Data Recording
E. Altus Metrum Hardware Specifications
F. Release Notes
F.1. Release Notes for Version 1.8.5
F.1.1. AltOS
F.1.2. AltosUI, TeleGPS
F.2. Release Notes for Version 1.8.4
F.2.1. AltOS
F.3. Release Notes for Version 1.8.3
F.3.1. AltOS
F.3.2. AltosUI and TeleGPS Applications
F.4. Release Notes for Version 1.8.2
F.4.1. AltOS
F.4.2. AltosUI and TeleGPS Applications
F.5. Release Notes for Version 1.8.1
F.5.1. AltOS
F.5.2. AltosUI and TeleGPS Applications
F.6. Release Notes for Version 1.8
F.6.1. AltOS
F.6.2. AltosUI and TeleGPS Applications
F.7. Release Notes for Version 1.7
F.7.1. AltOS
F.7.2. AltosUI and TeleGPS Applications
F.8. Release Notes for Version 1.6.8
F.8.1. AltOS
F.8.2. AltosUI, TeleGPS and AltosDroid Applications
F.9. Release Notes for Version 1.6.5
F.9.1. AltOS
F.9.2. AltosUI, TeleGPS and AltosDroid Applications
F.10. Release Notes for Version 1.6.4
F.10.1. AltOS
F.10.2. AltosUI, TeleGPS and AltosDroid Applications
F.10.3. Documentation
F.11. Release Notes for Version 1.6.3
F.11.1. AltOS
F.11.2. AltosUI and TeleGPS Applications
F.11.3. AltosDroid
F.11.4. Documentation
F.12. Release Notes for Version 1.6.2
F.12.1. AltOS
F.12.2. AltosUI and TeleGPS Applications
F.12.3. Documentation

List of Figures

4.1. EasyMini Board
7.1. AltosUI Main Window
7.2. Flight Data Graph
7.3. Flight Graph Configuration
7.4. Flight Statistics
7.5. Altimeter Configuration
7.6. Configure AltosUI Dialog
7.7. Fire Igniter Window

List of Tables

3.1. AltOS Modes
3.2. Pad/Idle Indications
4.1. EasyMini Screw Terminals
D.1. Data Storage on Altus Metrum altimeters
E.1. Altus Metrum Flight Computer Electronics
E.2. Altus Metrum Flight Computer Mechanical Components

Chapter 1. Introduction and Overview

Welcome to the Altus Metrum community! Our circuits and software reflect +NAR #88757, TRA #12200

Table of Contents

1. Introduction and Overview
2. Getting Started
2.1. Batteries
2.2. Linux/Mac/Windows Ground Station Software
3. Using Altus Metrum Hardware
3.1. Wiring and Electrical Interference
3.2. Hooking Up Lithium Polymer Batteries
3.3. Hooking Up Pyro Charges
3.4. Hooking Up a Power Switch
3.5. Understanding Beeps
3.6. Turning On the Power
3.7. Using an External Active Switch Circuit
3.8. Using a Separate Pyro Battery
3.9. Using a Different Kind of Battery
4. EasyMini
4.1. EasyMini Screw Terminals
4.2. Connecting A Battery To EasyMini
4.3. Charging Lithium Batteries
4.4. Using a Separate Pyro Battery with EasyMini
4.5. Using an Active Switch with EasyMini
5. Installation
6. Using Altus Metrum Products
6.1. In the Rocket
6.2. On the Ground
6.3. Data Analysis
6.4. Future Plans
7. AltosUI
7.1. Save Flight Data
7.2. Replay Flight
7.3. Graph Data
7.3.1. Flight Graph
7.3.2. Configure Graph
7.3.3. Flight Statistics
7.4. Export Data
7.4.1. Comma Separated Value Format
7.5. Configure Altimeter
7.5.1. Main Deploy Altitude
7.5.2. Apogee Delay
7.5.3. Apogee Lockout
7.5.4. Maximum Flight Log Size
7.5.5. Ignitor Firing Mode
7.5.6. Beeper Frequency
7.6. Configure AltosUI
7.6.1. Log Directory
7.6.2. Imperial Units
7.6.3. Serial Debug
7.6.4. Font size
7.6.5. Look & feel
7.6.6. Menu position
7.7. Flash Image
7.8. Fire Igniter
A. System Operation
A.1. Firmware Modes
A.2. Ground Testing
A.3. Configurable Parameters
B. Handling Precautions
C. Updating Device Firmware
C.1. Updating EasyMini Firmware
C.1.1. Recovering From Self-Flashing Failure
D. Flight Data Recording
E. Altus Metrum Hardware Specifications
F. Release Notes
F.1. Release Notes for Version 1.8.5
F.1.1. AltOS
F.1.2. AltosUI, TeleGPS
F.2. Release Notes for Version 1.8.4
F.2.1. AltOS
F.3. Release Notes for Version 1.8.3
F.3.1. AltOS
F.3.2. AltosUI and TeleGPS Applications
F.4. Release Notes for Version 1.8.2
F.4.1. AltOS
F.4.2. AltosUI and TeleGPS Applications
F.5. Release Notes for Version 1.8.1
F.5.1. AltOS
F.5.2. AltosUI and TeleGPS Applications
F.6. Release Notes for Version 1.8
F.6.1. AltOS
F.6.2. AltosUI and TeleGPS Applications
F.7. Release Notes for Version 1.7
F.7.1. AltOS
F.7.2. AltosUI and TeleGPS Applications
F.8. Release Notes for Version 1.6.8
F.8.1. AltOS
F.8.2. AltosUI, TeleGPS and AltosDroid Applications
F.9. Release Notes for Version 1.6.5
F.9.1. AltOS
F.9.2. AltosUI, TeleGPS and AltosDroid Applications
F.10. Release Notes for Version 1.6.4
F.10.1. AltOS
F.10.2. AltosUI, TeleGPS and AltosDroid Applications
F.10.3. Documentation
F.11. Release Notes for Version 1.6.3
F.11.1. AltOS
F.11.2. AltosUI and TeleGPS Applications
F.11.3. AltosDroid
F.11.4. Documentation
F.12. Release Notes for Version 1.6.2
F.12.1. AltOS
F.12.2. AltosUI and TeleGPS Applications
F.12.3. Documentation

List of Figures

4.1. EasyMini Board
7.1. AltosUI Main Window
7.2. Flight Data Graph
7.3. Flight Graph Configuration
7.4. Flight Statistics
7.5. Altimeter Configuration
7.6. Configure AltosUI Dialog
7.7. Fire Igniter Window

List of Tables

3.1. AltOS Modes
3.2. Pad/Idle Indications
4.1. EasyMini Screw Terminals
D.1. Data Storage on Altus Metrum altimeters
E.1. Altus Metrum Flight Computer Electronics
E.2. Altus Metrum Flight Computer Mechanical Components

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 releasing all of our hardware and software designs under open licenses, we also hope to empower you to take as active a role in our collective -future as you wish!

The first device created for our community was TeleMetrum, a dual +future as you wish!

Our goal is to include in this document all of the information required +to successfully configure and use Altus Metrum products. But +documentation is a lot like software in that it can contain "bugs", +and can probably always be improved! If you have questions that +aren’t answered in this manual, or just need a little help figuring +things out, we strongly suggest joining the Altus Metrum user email +list, which you can do by visiting +https://lists.gag.com/mailman/listinfo/altusmetrum. There’s a lot +of useful information in the mailing list archives!

The first device created for our community was TeleMetrum, a dual deploy altimeter with fully integrated GPS and radio telemetry as standard features, and a “companion interface” that will support optional capabilities in the future. The latest version @@ -105,12 +113,12 @@ beeping that accompanies each 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 3.1. AltOS Modes

Mode Name

Abbreviation

Beeps

Description

Startup

S

battery voltage in decivolts

Calibrating sensors, detecting orientation.

Idle

I

dit dit

Ready to accept commands over USB

Pad

P

dit dah dah dit

Waiting for launch. Not listening for commands.

Boost

B

dah dit dit dit

Accelerating upwards.

Fast

F

dit dit dah dit

Decelerating, but moving faster than 200m/s.

Coast

C

dah dit dah dit

Decelerating, moving slower than 200m/s

Drogue

D

dah dit dit

Descending after apogee. Above main height.

Main

M

dah dah

Descending. Below main height.

Landed

L

dit dah dit dit

Stable altitude for at least ten seconds.

Sensor error

X

dah dit dit dah

Error detected during sensor calibration.


Here’s a summary of all of the Pad and Idle mode +a long dissonant tone.

Table 3.1. AltOS Modes

Mode Name

Abbreviation

Beeps

Description

Startup

S

battery voltage in decivolts

Calibrating sensors, detecting orientation.

Idle

I

dit dit

Ready to accept commands over USB

Pad

P

dit dah dah dit

Waiting for launch. Not listening for commands.

Boost

B

dah dit dit dit

Accelerating upwards.

Fast

F

dit dit dah dit

Decelerating, but moving faster than 200m/s.

Coast

C

dah dit dah dit

Decelerating, moving slower than 200m/s

Drogue

D

dah dit dit

Descending after apogee. Above main height.

Main

M

dah dah

Descending. Below main height.

Landed

L

dit dah dit dit

Stable altitude for at least ten seconds.

Sensor error

X

dah dit dit dah

Error detected during sensor calibration.


Here’s a summary of all of the Pad and Idle mode indications. In Idle mode, you’ll hear one of these just once after the two short dits indicating idle mode. In Pad mode, after the dit dah dah dit indicating Pad mode, you’ll hear these once every five -seconds.

Table 3.2. Pad/Idle Indications

Name Beeps Description

Neither

brap

No continuity detected on either apogee or main igniters.

Apogee

dit

Continuity detected only on apogee igniter.

Main

dit dit

Continuity detected only on main igniter.

Both

dit dit dit

Continuity detected on both igniters.

Storage Full

warble

On-board data logging storage is full. This will +seconds.

Table 3.2. Pad/Idle Indications

Name Beeps Description

Neither

brap

No continuity detected on either apogee or main igniters.

Apogee

dit

Continuity detected only on apogee igniter.

Main

dit dit

Continuity detected only on main igniter.

Both

dit dit dit

Continuity detected on both igniters.

Storage Full

warble

On-board data logging storage is full. This will not prevent the flight computer from safely controlling the flight or transmitting telemetry signals, but no record of the flight will be @@ -167,7 +175,7 @@ is designed to use either a lithium polymer battery or any other battery producing between 4 and 12 volts, such as a rectangular 9V -battery.

Chapter 4. EasyMini

Figure 4.1. EasyMini Board

easymini-top.jpg

EasyMini is built on a 0.8 inch by 1½ inch circuit board. It’s +battery.

Chapter 4. EasyMini

Figure 4.1. EasyMini Board

easymini-top.jpg

EasyMini is built on a 0.8 inch by 1½ inch circuit board. It’s designed to fit in a 24mm coupler tube.

You usually don’t need to configure EasyMini at all; it’s set up to do dual-deployment with an event at apogee to separate the airframe and deploy a drogue and another event at 250m @@ -178,7 +186,7 @@ board. 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.1. EasyMini Screw Terminals

Terminal #Terminal NameDescription

Top 1

Main -

Main pyro channel connection to pyro circuit

Top 2

Main

Main pyro channel common connection to battery

Top 3

Battery

Positive external battery terminal

Top 4

Battery -

Negative external battery terminal

Bottom 1

Apogee -

Apogee pyro channel connection to pyro circuit

Bottom 2

Apogee

Apogee pyro channel common connection to battery

Bottom 3

Switch Output

Switch connection to flight computer

Bottom 4

Switch Input

Switch connection to positive battery terminal


4.2. Connecting A Battery To EasyMini

There are two possible battery connections on +switch. Counting from the left, the connections are as follows:

Table 4.1. EasyMini Screw Terminals

Terminal #Terminal NameDescription

Top 1

Main -

Main pyro channel connection to pyro circuit

Top 2

Main

Main pyro channel common connection to battery

Top 3

Battery

Positive external battery terminal

Top 4

Battery -

Negative external battery terminal

Bottom 1

Apogee -

Apogee pyro channel connection to pyro circuit

Bottom 2

Apogee

Apogee pyro channel common connection to battery

Bottom 3

Switch Output

Switch connection to flight computer

Bottom 4

Switch Input

Switch connection to positive battery terminal


4.2. Connecting A Battery To EasyMini

There are two possible battery connections on EasyMini. You can use either method; both feed through the power switch terminals.

One battery connection is the standard Altus Metrum white JST plug. This mates with single-cell Lithium @@ -276,7 +284,7 @@ feel free to dive in and help! Or let us know what you’d like to see that we aren’t already working on, and maybe we’ll get excited about it too…

Watch our web site for more news and information as our family of products -evolves!

Chapter 7. AltosUI

Figure 7.1. AltosUI Main Window

altosui.png

The AltosUI program provides a graphical user interface for +evolves!

Chapter 7. AltosUI

Figure 7.1. AltosUI Main Window

altosui.png

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 tasks. The primary interface window provides a selection of @@ -310,7 +318,7 @@ record file, either a .telem file recording telemetry data or a flash memory.

Note that telemetry files will generally produce poor graphs due to the lower sampling rate and missed telemetry packets. Use saved flight data in .eeprom files for graphing where possible.

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

7.3.1. Flight Graph

Figure 7.2. Flight Data Graph

graph.png

By default, the graph contains acceleration (blue), +opened.

7.3.1. Flight Graph

Figure 7.2. Flight Data Graph

graph.png

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

The graph can be zoomed into a particular area by clicking and dragging down and to the right. Once zoomed, the graph can be reset by clicking and @@ -318,7 +326,7 @@ dragging up and to the left. Holding down 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.

7.3.2. Configure Graph

Figure 7.3. Flight Graph Configuration

graph-configure.png

This selects which graph elements to show, and, at the +plot.

7.3.2. Configure Graph

Figure 7.3. Flight Graph Configuration

graph-configure.png

This selects which graph elements to show, and, at the very bottom. It also lets you configure how the graph is drawn:

  • Whether to use metric or imperial units @@ -339,7 +347,7 @@ descent. Flight computers without accelerometers always compute both speed and acceleration from barometric data. A larger value smooths the data more. -

7.3.3. Flight Statistics

Figure 7.4. Flight Statistics

graph-stats.png

Shows overall data computed from the flight.

7.4. Export Data

This tool takes the raw data files and makes them +

7.3.3. Flight Statistics

Figure 7.4. Flight Statistics

graph-stats.png

Shows overall data computed from the flight.

7.4. 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. The .eeprom @@ -358,7 +366,7 @@ tools can be configured to skip over.

The remaining lines of the file cont each field separated by a comma and at least one space. All of the sensor values are converted to standard units, with the barometric data reported in -both pressure, altitude and height above pad units.

7.5. Configure Altimeter

Figure 7.5. Altimeter Configuration

configure-altimeter.png

Select this button and then select an altimeter.

The first few lines of the dialog provide information about the +both pressure, altitude and height above pad units.

7.5. Configure Altimeter

Figure 7.5. Altimeter Configuration

configure-altimeter.png

Select this button and then select an altimeter.

The first few lines of the dialog provide information about the connected device, including the product name, software version and hardware serial number. Below that are the individual configuration entries.

At the bottom of the dialog, there are four buttons:

@@ -442,7 +450,7 @@ 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.

7.6. Configure AltosUI

Figure 7.6. Configure AltosUI Dialog

configure-altosui.png

This button presents a dialog so that you can +value.

7.6. Configure AltosUI

Figure 7.6. Configure AltosUI Dialog

configure-altosui.png

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

7.6.1. Log Directory

AltosUI logs all telemetry data and saves all flash data to this directory. This directory is also used as the staring point @@ -476,7 +484,7 @@ EasyMini is programmed directly over USB (self programming). Please read the directions for flashing devices in -Appendix C, Updating Device Firmware.

7.8. Fire Igniter

Figure 7.7. Fire Igniter Window

fire-igniter.png

This activates the igniter circuits in the flight +Appendix C, Updating Device Firmware.

7.8. Fire Igniter

Figure 7.7. Fire Igniter Window

fire-igniter.png

This activates the igniter circuits in the flight computer to help test recovery systems deployment.

Selecting the Fire Igniter button brings up the usual device selection dialog. Pick the desired @@ -642,7 +650,7 @@ during ascent and 10 samples per second during descent. Data are logged to an on-board flash memory part, which can be partitioned into -several equal-sized blocks, one for each flight.

Table D.1. Data Storage on Altus Metrum altimeters

Device Bytes per Sample Total Storage Minutes at Full Rate

EasyMini

16

1MB

10


The on-board flash is partitioned into separate flight logs, +several equal-sized blocks, one for each flight.

Table D.1. Data Storage on Altus Metrum altimeters

Device Bytes per Sample Total Storage Minutes at Full Rate

EasyMini

16

1MB

10


The on-board flash is partitioned into separate flight logs, each of a fixed maximum size. Increase the maximum size of each log and you reduce the number of flights that can be stored. Decrease the size and you can store more flights.

Configuration data is also stored in the flash memory on @@ -661,7 +669,7 @@ flight data, so be sure to download flight data and erase it 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.

Appendix E. Altus Metrum Hardware Specifications

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

Table E.1. Altus Metrum Flight Computer Electronics

Device Barometer Z-axis accel GPS 3D sensors Storage RF Output Battery

EasyMini v1.0

MS5607 30km (100k')

-

-

-

1MB

-

3.7-12V


Table E.2. Altus Metrum Flight Computer Mechanical Components

DeviceConnectorsScrew TerminalsWidthLengthTube Size

EasyMini

Debug USB Battery

Apogee pyro Main pyro Battery

0.8 inch (2.03cm)

1½ inch (3.81cm)

24mm coupler


Appendix F. Release Notes

F.1. Release Notes for Version 1.8.5

Version 1.8.5 includes fixes to the ground software support +production and retired.

Table E.1. Altus Metrum Flight Computer Electronics

Device Barometer Z-axis accel GPS 3D sensors Storage RF Output Battery

EasyMini v1.0

MS5607 30km (100k')

-

-

-

1MB

-

3.7-12V


Table E.2. Altus Metrum Flight Computer Mechanical Components

DeviceConnectorsScrew TerminalsWidthLengthTube Size

EasyMini

Debug USB Battery

Apogee pyro Main pyro Battery

0.8 inch (2.03cm)

1½ inch (3.81cm)

24mm coupler


Appendix F. Release Notes

F.1. Release Notes for Version 1.8.5

Version 1.8.5 includes fixes to the ground software support for TeleBT v4, along with a few other minor updates.

F.1.1. AltOS

  • Fix startup beeps that indicate sensor failures.

F.1.2. AltosUI, TeleGPS

  • diff --git a/AltOS/doc/easymini.pdf b/AltOS/doc/easymini.pdf index 204587b..370be21 100644 Binary files a/AltOS/doc/easymini.pdf and b/AltOS/doc/easymini.pdf differ diff --git a/AltOS/doc/micropeak.pdf b/AltOS/doc/micropeak.pdf index 24691bc..8f83b59 100644 Binary files a/AltOS/doc/micropeak.pdf and b/AltOS/doc/micropeak.pdf differ diff --git a/AltOS/doc/telegps-outline.pdf b/AltOS/doc/telegps-outline.pdf index e69de29..95b1fc3 100644 Binary files a/AltOS/doc/telegps-outline.pdf and b/AltOS/doc/telegps-outline.pdf differ diff --git a/AltOS/doc/telegps.html b/AltOS/doc/telegps.html index 760358f..034c33c 100644 --- a/AltOS/doc/telegps.html +++ b/AltOS/doc/telegps.html @@ -217,7 +217,11 @@ altitude and height above pad units.

3.5. Load Maps

Figure 3.9. Load Maps Window

load-maps.png

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.

There’s a drop-down menu of launch sites we know +internet connectivity at the site. Try not to wait +until the last minute, though, particularly if you’re +heading to a major launch. If too many people are +all trying to download map data at once, Google may +limit access until the next day.

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 and name of the site. The contents of this list are actually downloaded from our server at diff --git a/AltOS/doc/telegps.pdf b/AltOS/doc/telegps.pdf index 2348133..97b0782 100644 Binary files a/AltOS/doc/telegps.pdf and b/AltOS/doc/telegps.pdf differ diff --git a/AltOS/doc/telemega-outline.pdf b/AltOS/doc/telemega-outline.pdf index e69de29..812f9cd 100644 Binary files a/AltOS/doc/telemega-outline.pdf and b/AltOS/doc/telemega-outline.pdf differ diff --git a/AltOS/doc/telemetrum-outline.pdf b/AltOS/doc/telemetrum-outline.pdf index e69de29..a24ef49 100644 Binary files a/AltOS/doc/telemetrum-outline.pdf and b/AltOS/doc/telemetrum-outline.pdf differ diff --git a/AltOS/doc/telemetry.pdf b/AltOS/doc/telemetry.pdf index 0976d17..ded6a2c 100644 Binary files a/AltOS/doc/telemetry.pdf and b/AltOS/doc/telemetry.pdf differ diff --git a/AltOS/doc/telemini-v1-outline.pdf b/AltOS/doc/telemini-v1-outline.pdf index e69de29..744168a 100644 Binary files a/AltOS/doc/telemini-v1-outline.pdf and b/AltOS/doc/telemini-v1-outline.pdf differ diff --git a/AltOS/doc/telemini-v3-outline.pdf b/AltOS/doc/telemini-v3-outline.pdf index e69de29..2d00aa4 100644 Binary files a/AltOS/doc/telemini-v3-outline.pdf and b/AltOS/doc/telemini-v3-outline.pdf differ