From: Bdale Garbee Date: Tue, 25 Apr 2017 01:55:24 +0000 (-0600) Subject: update docs X-Git-Url: https://git.gag.com/?a=commitdiff_plain;ds=sidebyside;h=2faa092c66bbc47e6833e56a4ab0b91c254d9adb;p=web%2Faltusmetrum update docs --- diff --git a/AltOS/doc/altos.pdf b/AltOS/doc/altos.pdf index 9541203..bf1400f 100644 Binary files a/AltOS/doc/altos.pdf and b/AltOS/doc/altos.pdf differ diff --git a/AltOS/doc/altusmetrum-revhistory.html b/AltOS/doc/altusmetrum-revhistory.html index 91948f3..f5e0dd7 100644 --- a/AltOS/doc/altusmetrum-revhistory.html +++ b/AltOS/doc/altusmetrum-revhistory.html @@ -1,5 +1,7 @@ -Revision History
Revision History
Revision 1.6.84 Sep 2016
+Revision History
Revision History
Revision 1.721 Apr 2017
+ Add support for TeleMini v3.0 in firmware, AltosUI and AltosDroid +
Revision 1.6.84 Sep 2016
Minor release fixing another TeleMega and TeleMetrum v2.0 bug which could result in loss of data logging and telemetry in flight. Also fixed an AltosUI bug which would hide some pad diff --git a/AltOS/doc/altusmetrum.html b/AltOS/doc/altusmetrum.html index e18e5fb..e4b8ff0 100644 --- a/AltOS/doc/altusmetrum.html +++ b/AltOS/doc/altusmetrum.html @@ -1,7 +1,7 @@ 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 © 2016 Bdale Garbee and Keith Packard

+

Bdale Garbee

Keith Packard

Bob Finch

Anthony Towns

Copyright © 2017 Bdale Garbee and Keith Packard

This document is released under the terms of the Creative Commons ShareAlike 3.0 @@ -19,7 +19,7 @@ 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 v1.0
5.1. TeleMini v1.0 Screw Terminals
5.2. Using a Separate Pyro Battery with TeleMini v1.0
5.3. Using an Active Switch with TeleMini v1.0
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. 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 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.6.8
F.1.1. AltOS
F.1.2. AltosUI, TeleGPS and AltosDroid Applications
F.2. Release Notes for Version 1.6.5
F.2.1. AltOS
F.2.2. AltosUI, TeleGPS and AltosDroid Applications
F.3. Release Notes for Version 1.6.4
F.3.1. AltOS
F.3.2. AltosUI, TeleGPS and AltosDroid Applications
F.3.3. Documentation
F.4. Release Notes for Version 1.6.3
F.4.1. AltOS
F.4.2. AltosUI and TeleGPS Applications
F.4.3. AltosDroid
F.4.4. Documentation
F.5. Release Notes for Version 1.6.2
F.5.1. AltOS
F.5.2. AltosUI and TeleGPS Applications
F.5.3. Documentation
F.6. Release Notes for Version 1.6.1
F.6.1. AltOS
F.6.2. AltosUI and TeleGPS Applications
F.6.3. AltosDroid
F.7. Release Notes for Version 1.6
F.7.1. AltOS
F.7.2. AltosUI and TeleGPS Applications
F.8. Release Notes for Version 1.5
F.8.1. AltOS
F.8.2. AltosUI and TeleGPS Applications
F.9. Release Notes for Version 1.4.2
F.9.1. AltosUI and TeleGPS Applications
F.10. Release Notes for Version 1.4.1
F.10.1. AltosUI and TeleGPS Applications:
F.11. Release Notes for Version 1.4
F.11.1. AltOS
F.11.2. AltosUI Application
F.11.3. TeleGPS Application
F.11.4. Documentation
F.12. Release Notes for Version 1.3.2
F.12.1. AltOS
F.12.2. AltosUI Application
F.13. Release Notes for Version 1.3.1
F.13.1. AltOS
F.13.2. AltosUI Application
F.14. Release Notes for Version 1.3
F.14.1. AltOS
F.14.2. AltosUI Application
F.15. Release Notes for Version 1.2.1
F.15.1. AltOS
F.15.2. AltosUI Application
F.15.3. AltosDroid
F.16. Release Notes for Version 1.2
F.16.1. AltOS
F.16.2. AltosUI and MicroPeak Application
F.17. Release Notes for Version 1.1
F.17.1. AltOS
F.17.2. AltosUI
F.18. Release Notes for Version 1.1
F.18.1. AltOS
F.18.2. AltosUI
F.19. Release Notes for Version 1.0.1
F.19.1. AltOS
F.19.2. AltosUI Application
F.20. Release Notes for Version 0.9.2
F.20.1. AltosUI
F.21. Release Notes for Version 0.9
F.21.1. AltOS
F.21.2. AltosUI Application
F.22. Release Notes for Version 0.8
F.22.1. AltosUI Application:
F.23. Release Notes for Version 0.7.1
F.23.1. AltosUI Application

List of Figures

4.1. TeleMetrum v2 Board
4.2. TeleMetrum v1 Board
5.1. TeleMini v1.0 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 v1.0 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. 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.7
F.1.1. AltOS
F.1.2. AltosUI and TeleGPS Applications
F.2. Release Notes for Version 1.6.8
F.2.1. AltOS
F.2.2. AltosUI, TeleGPS and AltosDroid Applications
F.3. Release Notes for Version 1.6.5
F.3.1. AltOS
F.3.2. AltosUI, TeleGPS and AltosDroid Applications
F.4. Release Notes for Version 1.6.4
F.4.1. AltOS
F.4.2. AltosUI, TeleGPS and AltosDroid Applications
F.4.3. Documentation
F.5. Release Notes for Version 1.6.3
F.5.1. AltOS
F.5.2. AltosUI and TeleGPS Applications
F.5.3. AltosDroid
F.5.4. Documentation
F.6. Release Notes for Version 1.6.2
F.6.1. AltOS
F.6.2. AltosUI and TeleGPS Applications
F.6.3. Documentation
F.7. Release Notes for Version 1.6.1
F.7.1. AltOS
F.7.2. AltosUI and TeleGPS Applications
F.7.3. AltosDroid
F.8. Release Notes for Version 1.6
F.8.1. AltOS
F.8.2. AltosUI and TeleGPS Applications
F.9. Release Notes for Version 1.5
F.9.1. AltOS
F.9.2. AltosUI and TeleGPS Applications
F.10. Release Notes for Version 1.4.2
F.10.1. AltosUI and TeleGPS Applications
F.11. Release Notes for Version 1.4.1
F.11.1. AltosUI and TeleGPS Applications:
F.12. Release Notes for Version 1.4
F.12.1. AltOS
F.12.2. AltosUI Application
F.12.3. TeleGPS Application
F.12.4. Documentation
F.13. Release Notes for Version 1.3.2
F.13.1. AltOS
F.13.2. AltosUI Application
F.14. Release Notes for Version 1.3.1
F.14.1. AltOS
F.14.2. AltosUI Application
F.15. Release Notes for Version 1.3
F.15.1. AltOS
F.15.2. AltosUI Application
F.16. Release Notes for Version 1.2.1
F.16.1. AltOS
F.16.2. AltosUI Application
F.16.3. AltosDroid
F.17. Release Notes for Version 1.2
F.17.1. AltOS
F.17.2. AltosUI and MicroPeak Application
F.18. Release Notes for Version 1.1
F.18.1. AltOS
F.18.2. AltosUI
F.19. Release Notes for Version 1.1
F.19.1. AltOS
F.19.2. AltosUI
F.20. Release Notes for Version 1.0.1
F.20.1. AltOS
F.20.2. AltosUI Application
F.21. Release Notes for Version 0.9.2
F.21.1. AltosUI
F.22. Release Notes for Version 0.9
F.22.1. AltOS
F.22.2. AltosUI Application
F.23. Release Notes for Version 0.8
F.23.1. AltosUI Application:
F.24. Release Notes for Version 0.7.1
F.24.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, @@ -32,9 +32,9 @@ of TeleMetrum, v2.0, has all of the same features but with improved sensors and radio to offer increased performance.

Our second device was TeleMini, a dual deploy altimeter with radio telemetry and radio direction finding. The first version of this device was only 13mm by 38mm (½ inch by 1½ inches) and -could fit easily in an 18mm air-frame. The latest version, v2.0, -includes a beeper, USB data download and extended on-board -flight logging, along with an improved barometric sensor.

TeleMega is our most sophisticated device, including six pyro +could fit easily in an 18mm air-frame. The latest version, v3.0, +includes a beeper, higher power radio, extended on-board +flight logging and an improved barometric sensor.

TeleMega is our most sophisticated device, including six pyro channels (four of which are fully programmable), integrated GPS, integrated gyroscopes for staging/air-start inhibit and high performance telemetry.

EasyMini is a dual-deploy altimeter with logging and built-in @@ -148,13 +148,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 +166,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 @@ -234,7 +234,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 @@ -255,7 +255,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 @@ -271,44 +271,48 @@ 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 v1.0

Figure 5.1. TeleMini v1.0 Board

telemini-v1-top.jpg

TeleMini v1.0 is ½ inches by 1½ 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 accelerometer, TeleMini can be mounted in any convenient orientation. The default ¼ wave UHF wire antenna attached to -the center of one end of the board is about 7 inches long. Two -wires for the power switch are connected to holes in the +the center of one end of the board is about 7 inches long. Screw +terminals for the power switch are located in the middle of the board. Screw terminals for the e-matches for 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.

5.1. TeleMini v1.0 Screw Terminals

TeleMini v1.0 has four screw terminals on the end of the +should have at least 9 inches of interior length.

5.1. TeleMini v3 Screw Terminals

TeleMini v3 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 -soldered to the board for the power switch. Using the -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 5.1. TeleMini v1.0 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 v1.0

As described above, using an external pyro battery involves +and two are for main igniter circuits. Another two +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 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 lead to the per-channel pyro circuit connection. Because there is no solid ground connection to use on TeleMini, this -is not recommended.

The only available ground connection on TeleMini v1.0 are +is not recommended.

The only available ground connection on TeleMini v3 are the two mounting holes next to the telemetry antenna. Somehow connect a small piece of wire to one of those holes and hook it to the negative pyro battery terminal.

Connecting the positive battery terminal to the pyro -charges must be done separate from TeleMini v1.0, by soldering +charges must be done separate from TeleMini v3, by soldering them together or using some other connector.

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

5.3. Using an Active Switch with TeleMini v1.0

As explained above, an external active switch requires three +Main charge, terminal 1 for the Apogee charge).

5.3. Using an Active Switch with TeleMini v3

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, because TeleMini doesn’t have any good ground connection, this is not recommended.

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

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 +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 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 @@ -319,7 +323,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 @@ -347,7 +351,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 @@ -362,7 +366,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 @@ -378,12 +382,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 @@ -405,7 +409,6 @@ power on/off, and two pairs of wires connecting e-matches for the apogee and main ejection charges. All Altus Metrum products are designed for use with single-cell batteries with 3.7 volts nominal. -TeleMini v2.0 and EasyMini may also be used with other batteries as long as they supply between 4 and 12 volts.

The battery connectors are a standard 2-pin JST connector; you can purchase suitable batteries from the any vendor selling @@ -553,7 +556,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 @@ -563,7 +566,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 @@ -610,7 +613,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:

@@ -668,7 +671,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 @@ -679,7 +682,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 @@ -705,7 +708,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 @@ -727,11 +730,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 @@ -750,7 +753,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 @@ -795,7 +798,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 @@ -803,9 +806,9 @@ 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, lets you switch between metric and -imperial units

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 +imperial units

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 @@ -832,7 +835,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 @@ -990,7 +993,7 @@ skipped, which saves storage space.

11.6.18. Configure Pyro Channels

Figure 11.15. Additional Pyro Channel Configuration

configure-pyro.png

This opens a separate window to configure the +in the log.

11.6.18. 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 @@ -1117,7 +1120,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 @@ -1182,7 +1185,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 @@ -1228,8 +1231,8 @@ current value and doesn’t allow any changes.

11.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 +TeleMetrum v1.x, TeleDongle v0.2, TeleMini v1.0 +and TeleBT v1.0 are all reprogrammed by using another similar unit as a programming dongle (pair programming). TeleMega, EasyMega, TeleMetrum v2, @@ -1237,7 +1240,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 @@ -1253,13 +1256,13 @@ 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 about; if your favorites aren’t there, please let us @@ -1307,7 +1310,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 @@ -1503,7 +1506,7 @@ 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 +data continuously. TeleMini v1.0 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 @@ -1703,8 +1706,9 @@ have an accelerometer we can use to determine orientation, “idle” mode is selected if the board is connected via USB to a computer, otherwise the board enters “flight” mode. -TeleMini v1.0 -selects “idle” mode if it receives a command packet within the +TeleMini +selects “idle” mode if it receives a command packet +within the first five seconds of operation.

At power on, the altimeter will beep out the battery voltage to the nearest tenth of a volt. Each digit is represented by a sequence of short “dit” beeps, with a pause between @@ -1730,7 +1734,7 @@ The altimeters also listen for the radio link when in idle mode for requests sent via TeleDongle. Commands can be issued in idle mode over either USB or the radio link equivalently. -TeleMini v1.0 only has the radio link. +TeleMini only has the radio link. Idle mode is useful for configuring the altimeter, for extracting data from the on-board storage chip after flight, and for ground testing pyro charges.

In “Idle” and “Pad” modes, once the mode indication @@ -1753,11 +1757,13 @@ via TeleDongle over the radio link to cause the altimeter to reboot and come up in flight mode. This is much safer than standing on the top step of a rickety step-ladder or hanging off the side of a launch tower with a screw-driver trying to turn on your avionics before -installing igniters!

TeleMini v1.0 is configured solely via the radio link. Of course, that +installing igniters!

TeleMini is configured solely via the radio link. Of course, that means you need to know the TeleMini radio configuration values or you won’t be able to communicate with it. For situations -when you don’t have the radio configuration values, TeleMini v1.0 -offers an emergency recovery mode. In this mode, TeleMini is +when you don’t have the radio configuration values, +TeleMini v1.0 +offers an emergency recovery mode. In this mode, +TeleMini v1.0 is configured as follows:

  • Sets the radio frequency to 434.550MHz
  • @@ -1794,7 +1800,7 @@ altimeter from afar, as if it were directly connected to the computer.

    Any operation which can be performed with a flight computer can either be done with the device directly connected to the computer via the USB cable, or through the radio -link. TeleMini v1.0 doesn’t provide a USB connector and so it is +link. TeleMini doesn’t provide a USB connector and so it is always communicated with over radio. Select the appropriate TeleDongle device when the list of devices is presented and AltosUI will interact with an altimeter over the radio link.

    One oddity in the current interface is how AltosUI selects the @@ -1917,7 +1923,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 @@ -1969,7 +1975,7 @@ charge gasses.

< are all programmed directly over their USB connectors (self programming). -TeleMetrum v1, TeleMini and TeleDongle v0.2 are +TeleMetrum v1, TeleMini v1.0 and TeleDongle v0.2 are all programmed by using another device as a programmer (pair programming). It’s important to recognize which kind of devices you have before trying to reprogram them.

You may wish to begin by ensuring you have current firmware @@ -2141,8 +2147,8 @@ plugging in to it over USB and using a terminal program to connect to the board and issue the v command to check the version, etc. -

If something goes wrong, give it another try.

C.2.2. Updating TeleMini Firmware

You’ll need a special programming cable to -reprogram the TeleMini. You can make your own +

If something goes wrong, give it another try.

C.2.2. Updating TeleMini v1.0 Firmware

You’ll need a special programming cable to +reprogram the TeleMini v1.0. You can make your own using an 8-pin MicroMaTch connector on one end and a set of four pins on the other.

  1. Take the 2 screws out of the TeleDongle v0.2 @@ -2152,19 +2158,19 @@ circuit board. Plug the 8-pin end of the programming cable to the matching connector on the TeleDongle v0.2 or TeleBT v1.0, and the 4-pins into the -holes in the TeleMini circuit board. Note +holes in the TeleMini v1.0 circuit board. Note that the MicroMaTch connector has an alignment pin that goes through a hole in the PC board when you have the cable oriented correctly, and that pin 1 on the -TeleMini board is marked with a square pad +TeleMini v1.0 board is marked with a square pad while the other pins have round pads.
  2. -Attach a battery to the TeleMini board. +Attach a battery to the TeleMini v1.0 board.
  3. Plug the TeleDongle v0.2 or TeleBT v1.0 into your computer’s USB port, and power up the -TeleMini +TeleMini v1.0
  4. Run AltosUI, and select Flash Image from the File menu. @@ -2174,7 +2180,7 @@ device from the list, identifying it as the programming device.
  5. Select the image you want put on the -TeleMini, which should have a name in the +TeleMini v1.0, which should have a name in the form telemini-v1.0-1.0.0.ihx. It should be visible in the default directory, if not you may have to poke around your system to find @@ -2186,16 +2192,16 @@ and/or RF configuration values aren’t right, you’ll need to change them.
  6. Hit the OK button and the software should -proceed to flash the TeleMini with new +proceed to flash the TeleMini v1.0 with new firmware, showing a progress bar.
  7. -Confirm that the TeleMini board seems to +Confirm that the TeleMini v1.0 board seems to have updated OK, which you can do by configuring it over the radio link through the TeleDongle, or letting it come up in “flight” mode and listening for telemetry.

If something goes wrong, give it another try.

C.2.3. Updating TeleDongle v0.2 Firmware

Updating TeleDongle v0.2 firmware is just like -updating TeleMetrum v1.x or TeleMini firmware, but you +updating TeleMetrum v1.x or TeleMini v1.0 firmware, but you use either a TeleMetrum v1.x, TeleDongle v0.2 or TeleBT v1.0 as the programmer.

  1. Find the programming cable that you got as part of @@ -2270,12 +2276,12 @@ 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

    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 TeleMetrum v1.x, -TeleMini and +TeleMini v3.0 and EasyMini. This consumes 64kB of flash space. This configuration space is not available @@ -2299,10 +2305,20 @@ 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

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

Version 1.6.8 fixes a TeleMega and TeleMetrum v2.0 bug where +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.7

Version 1.7 includes support for our new TeleMini v3.0 +flight computer and bug fixes in in the flight software for all our boards +and ground station interfaces.

F.1.1. AltOS

AltOS New Features

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

AltOS Fixes

  • +Fix interrupt priorities on STM32L processors. Run timer +interrupt at lowest priority so that device interrupts get +serviced first. +

F.1.2. AltosUI and TeleGPS Applications

AltosUI New Features

  • +Add support for TeleMini v3.0 hardware +

F.2. Release Notes for Version 1.6.8

Version 1.6.8 fixes a TeleMega and TeleMetrum v2.0 bug where the device could stop logging data and transmitting telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum -v2.0 users should update their flight firmware.

F.1.1. AltOS

AltOS fixes:

  • +v2.0 users should update their flight firmware.

    F.2.1. AltOS

    AltOS fixes:

    • Fix STM32L DMA driver to work around STM32L SoC DMA priority issue t lock-up in the logging or radio code, either of which could stop data logging and telemetry. @@ -2315,7 +2331,7 @@ flight.

    AltOS changes:

    • Flash LEDS on all products briefly during power up so that they can be tested during production. -

    F.1.2. AltosUI, TeleGPS and AltosDroid Applications

    AltosUI fixes:

    • +

    F.2.2. AltosUI, TeleGPS and AltosDroid Applications

    AltosUI fixes:

    • Re-enable go/no-go entries after they’ve been disabled due to lack of data. If telemetry information is delayed when the Ui starts up, sometimes important fields would get @@ -2323,20 +2339,20 @@ disabled to never re-appear.
    • Deal with ground station failure better during Configure Ground Station operation by cleaning up pending operations. -

F.2. Release Notes for Version 1.6.5

Version 1.6.5 fixes a TeleMega and TeleMetrum v2.0 bug where +

F.3. Release Notes for Version 1.6.5

Version 1.6.5 fixes a TeleMega and TeleMetrum v2.0 bug where the device would often stop logging data and transmitting telemetry in flight. All TeleMega v1.0, v2.0 and TeleMetrum -v2.0 users should update their flight firmware.

F.2.1. AltOS

AltOS fixes:

  • +v2.0 users should update their flight firmware.

    F.3.1. AltOS

    AltOS fixes:

    • Fix STM32L SPI driver to prevent lock-up in the logging or radio code, either of which could stop data logging and telemetry. Found and characterized by Chuck Haskin, who also tested the new firmware before release. -

    F.2.2. AltosUI, TeleGPS and AltosDroid Applications

    AltosUI fixes:

    • +

    F.3.2. AltosUI, TeleGPS and AltosDroid Applications

    AltosUI fixes:

    • Deliver firmward for TeleMega v2.0 and TeleBT v3.0 with Windows package. -

F.3. Release Notes for Version 1.6.4

Version 1.6.4 fixes a bluetooth communication problem with +

F.4. Release Notes for Version 1.6.4

Version 1.6.4 fixes a bluetooth communication problem with TeleBT v1.0 devices, along with some altosui and altosdroid -minor nits. It also now ships firmware for some newer devices.

F.3.1. AltOS

AltOS fixes:

  • +minor nits. It also now ships firmware for some newer devices.

    F.4.1. AltOS

    AltOS fixes:

    • Fix hardware flow control on TeleBT v1.0. Hardware RTS/CTS doesn’t seem to work, switch from using the hardware to driving these pins with software. @@ -2344,7 +2360,7 @@ driving these pins with software. Fix ARM USB drivers to deal with OS restarts. Needed to reset all USB-related state when the USB bus is reset. These fixes affect all STM32L, STM32F0 and LPC11U14 based devices. -

    F.3.2. AltosUI, TeleGPS and AltosDroid Applications

    AltosUI, TeleGPS and AltosDroid New Features:

    • +

    F.4.2. AltosUI, TeleGPS and AltosDroid Applications

    AltosUI, TeleGPS and AltosDroid New Features:

    • Automatically switch from meters or feet to kilometers or miles for distance units.
    • @@ -2355,17 +2371,17 @@ Abort map preloading when the preload map dialog is closed. In AltosDroid, Don’t reconnect to last device if the user had disconnected it the last time the application was active. -

    F.3.3. Documentation

    • +

    F.4.3. Documentation

    • Mention TeleMega v2.0 in hardware specs table.
    • Document TeleGPS RF output in telegps manual. -

F.4. Release Notes for Version 1.6.3

Version 1.6.3 adds idle mode to AltosDroid and has bug fixes +

F.5. Release Notes for Version 1.6.3

Version 1.6.3 adds idle mode to AltosDroid and has bug fixes for our host software on desktops, laptops an android devices -along with BlueTooth support for Windows.

F.4.1. AltOS

AltOS fixes:

  • +along with BlueTooth support for Windows.

    F.5.1. AltOS

    AltOS fixes:

    • Fix hardware flow control on TeleBT v3.0. RTS/CTS is wired backwards on this board, switch from using the hardware to driving these pins with software. -

    F.4.2. AltosUI and TeleGPS Applications

    AltosUI and TeleGPS New Features:

    • +

    F.5.2. AltosUI and TeleGPS Applications

    AltosUI and TeleGPS New Features:

    • Add BlueTooth support for Windows operating system. This supports connections to TeleBT over BlueTooth rather than just USB. @@ -2387,7 +2403,7 @@ the connected Altus Metrum USB devices appear again.
    • Fix acceleration data presented in MonitorIdle mode for TeleMetrum v2.0 flight computers. -

    F.4.3. AltosDroid

    AltosDroid new features:

    • +

    F.5.3. AltosDroid

    AltosDroid new features:

    • Monitor Idle mode. Check state of flight computer while in idle mode over the radio link
    • @@ -2425,12 +2441,12 @@ Recover old tracker positions when restarting application. This finally allows you to safely stop and restart the application without losing the last known location of any tracker. -

    F.4.4. Documentation

    • +

    F.5.4. Documentation

    • Document TeleMega and EasyMega additional pyro channel continuity audio alert pattern. -

F.5. Release Notes for Version 1.6.2

Version 1.6.2 includes support for our updated TeleMega v2.0 +

F.6. Release Notes for Version 1.6.2

Version 1.6.2 includes support for our updated TeleMega v2.0 product and bug fixes in in the flight software for all our boards -and ground station interfaces.

F.5.1. AltOS

AltOS New Features:

  • +and ground station interfaces.

    F.6.1. AltOS

    AltOS New Features:

    • Add support for TeleMega v2.0 boards.
    • Add PWM servo driver. There’s no higher level code using @@ -2439,14 +2455,14 @@ servo output connector.

    AltOS Fixes:

    • Slow down telemetry packets to allow receiver to keep up. -

    F.5.2. AltosUI and TeleGPS Applications

    AltosUI and TeleGPS Fixes:

    • +

    F.6.2. AltosUI and TeleGPS Applications

    AltosUI and TeleGPS Fixes:

    • Fix post-flight orientation computation when processing TeleMega and EasyMega eeprom data files.
    • Capture complete eeprom data even when there are invalid entries in the data. This keeps reading eeprom contents and writing the associated .eeprom file when an error is detected. -

    F.5.3. Documentation

    We spent a bunch of time trying to improve our documentation

    • +

    F.6.3. Documentation

    We spent a bunch of time trying to improve our documentation

    • HTML versions now have a table of contents on the left side.
    • EasyMini now has its own shorter manual. @@ -2455,9 +2471,9 @@ Provide links between sections in each document.
    • Lots of minor rewriting and restructuring to avoid duplication of information -

F.6. Release Notes for Version 1.6.1

Version 1.6.1 includes support for our updated TeleBT v3.0 +

F.7. Release Notes for 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.

F.6.1. AltOS

AltOS New Features:

  • +and ground station interfaces.

    F.7.1. AltOS

    AltOS New Features:

    • Add support for TeleBT v3.0 boards.
    • Add support for uncompressed APRS data, providing support @@ -2467,7 +2483,7 @@ altitude data.

    AltOS Fixes:

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

    F.6.2. AltosUI and TeleGPS Applications

    AltosUI and TeleGPS New Features:

    • +

    F.7.2. AltosUI and TeleGPS Applications

    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. @@ -2505,7 +2521,7 @@ 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. -

    F.6.3. AltosDroid

    AltosDroid New Features:

    • +

    F.7.3. AltosDroid

    AltosDroid New Features:

    • Add offline map support using mapping code from AltosUI.
    • Support TeleDongle (and TeleBT via USB) on devices @@ -2533,9 +2549,9 @@ Make voice announcements depend on current tab.
    • Compute adjustment to current travel direction while in motion towards rocket. -

F.7. Release Notes for Version 1.6

Version 1.6 includes support for our updated TeleDongle v3.0 +

F.8. Release Notes for 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.

F.7.1. AltOS

AltOS New Features

  • +and ground station interfaces.

    F.8.1. AltOS

    AltOS New Features

    • Add support for TeleDongle v3.0 boards.

    AltOS Fixes

    • Don’t beep out the continuity twice by accident in idle mode. @@ -2555,7 +2571,7 @@ interrupt code would occasionally wedge on long transfers if interrupts were blocked for too long. This affects all released TeleGPS products; if you have a TeleGPS device, you’ll want to reflash the firmware. -

    F.7.2. AltosUI and TeleGPS Applications

    AltosUI and TeleGPS New Features

    • +

    F.8.2. AltosUI and TeleGPS Applications

    AltosUI and TeleGPS New Features

    • Compute tilt angle from TeleMega and EasyMega log files. This duplicates the quaternion-based angle tracking code from the flight firmware inside the ground station @@ -2601,9 +2617,9 @@ five seconds these days. In the Scan Channels code, reset pending flight state information each time we change channels. This avoids having flight computers appear on multiple frequencies by accident. -

F.8. Release Notes for Version 1.5

Version 1.5 is a major release. It includes support for our new +

F.9. Release Notes for 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

F.8.1. AltOS

AltOS New Features

  • +software for all our boards and the AltosUI ground station

    F.9.1. AltOS

    AltOS New Features

    • Add support for EasyMega boards.
    • Make the APRS SSID be configurable. This lets you track @@ -2637,7 +2653,7 @@ the delay, but become bad before the delay expires. Allow negative numbers in pyro configuration values. This lets you specify things like descending speed or deceleration. -

    F.8.2. AltosUI and TeleGPS Applications

    AltosUI and TeleGPS New Features

    • +

    F.9.2. AltosUI and TeleGPS Applications

    AltosUI and TeleGPS New Features

    • Support telemetry baud rate selection. Adds menus to the flight monitoring and configuration for baud rate selection. @@ -2654,18 +2670,18 @@ Make the Graph button on the landed tab w Make tests for Java on Windows a bit smarter, and also provide the user with the option to skip installing Java for cases where we just can’t figure out what version is installed. -

F.9. Release Notes for Version 1.4.2

Version 1.4.2 is a minor release. It fixes Java-related install issues on -Windows

F.9.1. AltosUI and TeleGPS Applications

Windows Install Fixes

  • +

F.10. Release Notes for Version 1.4.2

Version 1.4.2 is a minor release. It fixes Java-related install issues on +Windows

F.10.1. AltosUI and TeleGPS Applications

Windows Install Fixes

  • Checks for Java installation data in more registry locations.
  • Allows user to bypass Java installation in case the detection fails. -

F.10. Release Notes for Version 1.4.1

Version 1.4.1 is a minor release. It fixes install issues on +

F.11. Release Notes for 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 all. All Windows users will want to upgrade to get the signed driver, but Mac and Linux users who do not need the TeleMetrum -V2.0 firmware image will not need to upgrade.

F.10.1. AltosUI and TeleGPS Applications:

Windows Install Fixes

  • +V2.0 firmware image will not need to upgrade.

    F.11.1. AltosUI and TeleGPS Applications:

    Windows Install Fixes

    • Provide signed Windows driver files. This should avoid any need to disable driver signature checking on Windows 7 or 8.
    • @@ -2683,9 +2699,9 @@ packages for Linux, Mac and Windows. Include Google Application Key for map downloading. The 1.4 release didn’t have this key in the released version of the software, making map downloading fail for most people. -

F.11. Release Notes for Version 1.4

Version 1.4 is a major release. It includes support for our new +

F.12. Release Notes for 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

F.11.1. AltOS

AltOS new features:

  • +software for all our boards and the AltosUI ground station

    F.12.1. AltOS

    AltOS new features:

    • Add support for TeleGPS boards.
    • Make the beeper tone configurable, making it @@ -2715,7 +2731,7 @@ number to 2 on TeleMega and TeleMetrum v2.
    • Fix u-Blox GPS driver to mark course and speed data as being present. -

    F.11.2. AltosUI Application

    AltosUI new features:

    • +

    F.12.2. AltosUI Application

    AltosUI new features:

    • Add zooming and new content types (terrain and road maps) to map view. Change map storage format from PNG to Jpeg, which saves a huge amount of disk @@ -2772,12 +2788,12 @@ Handle TeleMetrum and TeleMini eeprom files generated with pre-1.0 firmware. Those ancient versions didn’t report the log format, so just use the product name instead. -

    F.11.3. TeleGPS Application

    • +

    F.12.3. TeleGPS Application

    • New application designed for use with TeleGPS boards.
    • Shares code with AltosUI, mostly just trimmed down to focus on TeleGPS-related functions. -

    F.11.4. Documentation

    Documentation changes:

    • +

    F.12.4. Documentation

    Documentation changes:

    • Re-create the drill template images; they should print correctly from Firefox at least. Ship these as individual PDF files so they’re easy to print. @@ -2785,8 +2801,8 @@ individual PDF files so they’re easy to print. Add a description of the Apogee Lockout setting, which prevents the apogee charge from firing for a configurable amount of time after boost. -

F.12. Release Notes for 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

F.12.1. AltOS

AltOS fixes:

  • +

F.13. Release Notes for 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

F.13.1. AltOS

AltOS fixes:

  • On TeleMega, limit number of logged GPS status information to 12 satellites. That’s all there is room for in the log structure. @@ -2796,7 +2812,7 @@ position and keeps sending that if we lose GPS lock. Marks locked/unlocked by sending L/U in the APRS comment field along with the number of sats in view and voltages. -

F.12.2. AltosUI Application

AltosUI fixes:

  • +

F.13.2. AltosUI Application

AltosUI fixes:

  • If the TeleMega flight firmware reports that it has logged information about more than 12 satellites, don’t believe it as the log only holds 12 satellite @@ -2809,8 +2825,8 @@ data. Use letters (A, B, C, D) for alternate pyro channel names instead of numbers (0, 1, 2, 3) in the Fire Igniter dialog. -

F.13. Release Notes for 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.

F.13.1. AltOS

AltOS new features:

  • +

F.14. Release Notes for 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.

F.14.1. AltOS

AltOS new features:

  • Improved APRS mode. Now uses compressed position format for smaller data size, improved precision and to include altitude data as well as latitude and @@ -2832,7 +2848,7 @@ Fix antenna-down mode accelerometer configuration. Antenna down mode wasn’t working because the accelerometer calibration values were getting re-computed incorrectly in inverted mode. -

F.13.2. AltosUI Application

AltosUI new features:

  • +

F.14.2. AltosUI Application

AltosUI new features:

  • Display additional TeleMega sensor values in real units. Make all of these values available for plotting. Display TeleMega orientation value in the @@ -2846,8 +2862,8 @@ Main. Limit data rate when downloading satellite images from Google to make sure we stay within their limits so that all of the map tiles download successfully. -

F.14. Release Notes for Version 1.3

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

F.14.1. AltOS

AltOS new features:

  • +

F.15. Release Notes for Version 1.3

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

F.15.1. AltOS

AltOS new features:

  • Add STM32L processor support. This includes enhancements to the scheduler to support products with many threads. @@ -2871,7 +2887,7 @@ accelerometer, Invensense MPU6000 3-axis accelerometer + 3 axis gyro, Honeywell HMC5883 3-axis magnetic sensor and the TI CC1120 and CC115L digital FM transceivers -

F.14.2. AltosUI Application

AltosUI new features:

  • +

F.15.2. AltosUI Application

AltosUI new features:

  • Support TeleMega, TeleMetrum v2.0, TeleMini v2.0 and EasyMini telemetry and log formats.

AltosUI fixes:

  • @@ -2884,9 +2900,9 @@ Add Download button to menu bar.
  • Save the last log directory and offer that as the default for new downloads -

F.15. Release Notes for Version 1.2.1

Version 1.2.1 is a minor release. It adds support for TeleBT and +

F.16. Release Notes for 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.

F.15.1. AltOS

AltOS new features:

  • +AltosUI and fixes some bugs in the AltOS firmware.

    F.16.1. AltOS

    AltOS new features:

    • Add support for TeleBT

    AltOS fixes:

    • In TeleMini recovery mode (when booted with the @@ -2906,7 +2922,7 @@ Adjusted the automatic gain control parameters that affect receive performance for TeleDongle. Field tests indicate that this may improve receive performance somewhat. -

    F.15.2. AltosUI Application

    AltosUI application new features:

    • +

    F.16.2. AltosUI Application

    AltosUI application new features:

    • Make the initial position of the AltosUI top level window configurable. Along with this change, the other windows will pop up at sensible places now, @@ -2940,15 +2956,15 @@ progress. Unfortunately, we don’t know how many blocks will need to be downloaded, but at least it isn’t just sitting there doing nothing for a long time. -

    F.15.3. AltosDroid

    • +

    F.16.3. AltosDroid

    • First version of this application -

F.16. Release Notes for Version 1.2

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

F.16.1. AltOS

AltOS New Features:

  • +

F.17. Release Notes for Version 1.2

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

F.17.1. AltOS

AltOS New Features:

  • Add MicroPeak support. This includes support for the ATtiny85 processor and adaptations to the core code to allow for devices too small to run the multi-tasking scheduler. -

F.16.2. AltosUI and MicroPeak Application

New Features:

  • +

F.17.2. AltosUI and MicroPeak Application

New Features:

  • Added MicroPeak application

AltosUI and MicroPeak fixes:

  • Distribute Mac OS X packages in disk image (.dmg) @@ -2959,11 +2975,11 @@ libraries to ensure that upgrades work properly, and to allow for multiple Altus Metrum software packages to be installed in the same directory at the same time. -

F.17. Release Notes for Version 1.1

Version 1.1.1 is a bug-fix release. It fixes a couple of bugs +

F.18. Release Notes for Version 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 file export issue, and for suggesting the -addition of the Ground Distance value in the Descent tab.

F.17.1. AltOS

AltOS fixes:

  • +addition of the Ground Distance value in the Descent tab.

    F.18.1. AltOS

    AltOS fixes:

    • TeleMetrum v1.0 boards use the AT45DB081D flash memory part to store flight data, which is different from later TeleMetrum boards. The AltOS v1.1 driver @@ -2972,7 +2988,7 @@ impossible to delete flight data or update configuration values. This bug doesn’t affect newer TeleMetrum boards, and it doesn’t affect the safety of rockets flying version 1.1 firmware. -

    F.17.2. AltosUI

    AltosUI new features:

    • +

    F.18.2. AltosUI

    AltosUI new features:

    • The “Descent” tab displays the range to the rocket, which is a combination of the over-the-ground distance to the rockets current latitude/longitude @@ -3001,8 +3017,8 @@ things like battery voltage. The code that picked which kinds of data to fetch from the flight computer was missing a check for TeleMini when deciding whether to fetch the analog sensor data. -

F.18. Release Notes for 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.

F.18.1. AltOS

AltOS Firmware New Features:

  • +

F.19. Release Notes for 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.

F.19.1. AltOS

AltOS Firmware New Features:

  • Add apogee-lockout value. Overrides the apogee detection logic to prevent incorrect apogee charge firing. @@ -3022,7 +3038,7 @@ packets was from 320ms ago. Fix a bug which caused the old received telemetry packets to be retransmitted over the USB link when the radio was turned off and back on. -

F.18.2. AltosUI

AltosUI New Features:

  • +

F.19.2. AltosUI

AltosUI New Features:

  • Make the look-n-feel configurable, providing a choice from the available options.
  • @@ -3076,8 +3092,8 @@ the flight monitoring window. This eliminates entries duplicated from the header and adds both current altitude and pad altitude, which are useful in Monitor Idle mode. -

F.19. Release Notes for Version 1.0.1

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

F.19.1. AltOS

AltOS New Features

  • +

F.20. Release Notes for Version 1.0.1

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

F.20.1. AltOS

AltOS New Features

  • Add TeleMini v1.0 support.
  • Support operation of TeleMetrum with the antenna pointing @@ -3112,7 +3128,7 @@ within a fraction of a second. In addition, this approach allows the baro-only TeleMini device to correctly identify Mach transitions, avoiding the error-prone selection of a Mach delay. -

F.19.2. AltosUI Application

AltosUI New Features

  • +

F.20.2. AltosUI Application

AltosUI New Features

  • Add main/apogee voltage graphs to the data plot. This provides a visual indication if the igniters fail before being fired. @@ -3156,8 +3172,8 @@ waits indefinitely for the remote device to appear, providing a cancel button should the user get bored. This is necessary as the TeleMini can only be placed in "Idle" mode if AltosUI is polling it. -

F.20. Release Notes for Version 0.9.2

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

F.20.1. AltosUI

AltosUI fixes:

  • +

F.21. Release Notes for Version 0.9.2

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

F.21.1. AltosUI

AltosUI fixes:

  • Fix plotting problems due to missing file in the Mac OS install image.
  • @@ -3165,8 +3181,8 @@ Always read whole eeprom blocks, mark empty records invalid, display parsing errors to user.
  • Add software version to Configure AltosUI dialog -

F.21. Release Notes for Version 0.9

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

F.21.1. AltOS

  • +

F.22. Release Notes for Version 0.9

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

F.22.1. AltOS

  • Support for TeleMetrum v1.1 hardware. Sources for the flash memory part used in v1.0 dried up, so v1.1 uses a different part which required a new driver and support for explicit @@ -3183,12 +3199,12 @@ Previous versions used a telemetry packet format that 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. -

F.21.2. AltosUI Application

  • +

F.22.2. AltosUI Application

  • Support for telemetry format changes.
  • Support for multiple flight logs. -

F.22. Release Notes for Version 0.8

Version 0.8 offers a major upgrade in the AltosUI -interface.

F.22.1. AltosUI Application:

  • +

F.23. Release Notes for Version 0.8

Version 0.8 offers a major upgrade in the AltosUI +interface.

F.23.1. AltosUI Application:

  • Post-flight graphing tool. This lets you explore the behaviour of your rocket after flight with a scroll-able and zoom-able chart showing the altitude, speed and acceleration @@ -3227,8 +3243,8 @@ automatically connect to it and prepare to monitor a flight. 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. -

F.23. Release Notes for Version 0.7.1

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

F.23.1. AltosUI Application

  • +

F.24. Release Notes for Version 0.7.1

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

F.24.1. AltosUI Application

  • Receive and log telemetry from a connected TeleDongle device. All data received is saved to log files named with the current date and the connected rocket serial and flight diff --git a/AltOS/doc/altusmetrum.pdf b/AltOS/doc/altusmetrum.pdf index e4c07ee..71d5329 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 cdf3fdb..3334316 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 0a44748..b071fa6 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 0bd955d..5327a61 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 91a326f..4c33823 100644 --- a/AltOS/doc/easymini.html +++ b/AltOS/doc/easymini.html @@ -32,9 +32,9 @@ of TeleMetrum, v2.0, has all of the same features but with improved sensors and radio to offer increased performance.

    Our second device was TeleMini, a dual deploy altimeter with radio telemetry and radio direction finding. The first version of this device was only 13mm by 38mm (½ inch by 1½ inches) and -could fit easily in an 18mm air-frame. The latest version, v2.0, -includes a beeper, USB data download and extended on-board -flight logging, along with an improved barometric sensor.

    TeleMega is our most sophisticated device, including six pyro +could fit easily in an 18mm air-frame. The latest version, v3.0, +includes a beeper, higher power radio, extended on-board +flight logging and an improved barometric sensor.

    TeleMega is our most sophisticated device, including six pyro channels (four of which are fully programmable), integrated GPS, integrated gyroscopes for staging/air-start inhibit and high performance telemetry.

    EasyMini is a dual-deploy altimeter with logging and built-in diff --git a/AltOS/doc/easymini.pdf b/AltOS/doc/easymini.pdf index e28c7fe..f20c97a 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 cbd8036..a27428d 100644 Binary files a/AltOS/doc/micropeak.pdf and b/AltOS/doc/micropeak.pdf differ diff --git a/AltOS/doc/release-notes-0.7.1.pdf b/AltOS/doc/release-notes-0.7.1.pdf index f8298bb..4f7fcd2 100644 Binary files a/AltOS/doc/release-notes-0.7.1.pdf and b/AltOS/doc/release-notes-0.7.1.pdf differ diff --git a/AltOS/doc/release-notes-0.8.pdf b/AltOS/doc/release-notes-0.8.pdf index c088b2a..b510432 100644 Binary files a/AltOS/doc/release-notes-0.8.pdf and b/AltOS/doc/release-notes-0.8.pdf differ diff --git a/AltOS/doc/release-notes-0.9.2.pdf b/AltOS/doc/release-notes-0.9.2.pdf index 3eb70f2..0ba616a 100644 Binary files a/AltOS/doc/release-notes-0.9.2.pdf and b/AltOS/doc/release-notes-0.9.2.pdf differ diff --git a/AltOS/doc/release-notes-0.9.pdf b/AltOS/doc/release-notes-0.9.pdf index 576b947..f179905 100644 Binary files a/AltOS/doc/release-notes-0.9.pdf and b/AltOS/doc/release-notes-0.9.pdf differ diff --git a/AltOS/doc/release-notes-1.0.1.pdf b/AltOS/doc/release-notes-1.0.1.pdf index 41831af..11fe658 100644 Binary files a/AltOS/doc/release-notes-1.0.1.pdf and b/AltOS/doc/release-notes-1.0.1.pdf differ diff --git a/AltOS/doc/release-notes-1.1.1.pdf b/AltOS/doc/release-notes-1.1.1.pdf index 0af741a..ac98a0d 100644 Binary files a/AltOS/doc/release-notes-1.1.1.pdf and b/AltOS/doc/release-notes-1.1.1.pdf differ diff --git a/AltOS/doc/release-notes-1.1.pdf b/AltOS/doc/release-notes-1.1.pdf index 8375b5c..e6c1595 100644 Binary files a/AltOS/doc/release-notes-1.1.pdf and b/AltOS/doc/release-notes-1.1.pdf differ diff --git a/AltOS/doc/release-notes-1.2.1.pdf b/AltOS/doc/release-notes-1.2.1.pdf index a4c193d..191c3cc 100644 Binary files a/AltOS/doc/release-notes-1.2.1.pdf and b/AltOS/doc/release-notes-1.2.1.pdf differ diff --git a/AltOS/doc/release-notes-1.2.pdf b/AltOS/doc/release-notes-1.2.pdf index c8554f5..b2ab14b 100644 Binary files a/AltOS/doc/release-notes-1.2.pdf and b/AltOS/doc/release-notes-1.2.pdf differ diff --git a/AltOS/doc/release-notes-1.3.1.pdf b/AltOS/doc/release-notes-1.3.1.pdf index 5e4125b..48ec6d0 100644 Binary files a/AltOS/doc/release-notes-1.3.1.pdf and b/AltOS/doc/release-notes-1.3.1.pdf differ diff --git a/AltOS/doc/release-notes-1.3.2.pdf b/AltOS/doc/release-notes-1.3.2.pdf index 03bfd82..4c36d3f 100644 Binary files a/AltOS/doc/release-notes-1.3.2.pdf and b/AltOS/doc/release-notes-1.3.2.pdf differ diff --git a/AltOS/doc/release-notes-1.3.pdf b/AltOS/doc/release-notes-1.3.pdf index 5308a5a..1995d36 100644 Binary files a/AltOS/doc/release-notes-1.3.pdf and b/AltOS/doc/release-notes-1.3.pdf differ diff --git a/AltOS/doc/release-notes-1.4.1.pdf b/AltOS/doc/release-notes-1.4.1.pdf index 9a9553e..a78c9c4 100644 Binary files a/AltOS/doc/release-notes-1.4.1.pdf and b/AltOS/doc/release-notes-1.4.1.pdf differ diff --git a/AltOS/doc/release-notes-1.4.2.pdf b/AltOS/doc/release-notes-1.4.2.pdf index 8a130de..e1e215f 100644 Binary files a/AltOS/doc/release-notes-1.4.2.pdf and b/AltOS/doc/release-notes-1.4.2.pdf differ diff --git a/AltOS/doc/release-notes-1.4.pdf b/AltOS/doc/release-notes-1.4.pdf index 50276e8..03c32c8 100644 Binary files a/AltOS/doc/release-notes-1.4.pdf and b/AltOS/doc/release-notes-1.4.pdf differ diff --git a/AltOS/doc/release-notes-1.5.pdf b/AltOS/doc/release-notes-1.5.pdf index 4d48ca0..14700c4 100644 Binary files a/AltOS/doc/release-notes-1.5.pdf and b/AltOS/doc/release-notes-1.5.pdf differ diff --git a/AltOS/doc/release-notes-1.6.1.pdf b/AltOS/doc/release-notes-1.6.1.pdf index 98bf3f5..4e0f731 100644 Binary files a/AltOS/doc/release-notes-1.6.1.pdf and b/AltOS/doc/release-notes-1.6.1.pdf differ diff --git a/AltOS/doc/release-notes-1.6.2.pdf b/AltOS/doc/release-notes-1.6.2.pdf index 8758057..de5c91e 100644 Binary files a/AltOS/doc/release-notes-1.6.2.pdf and b/AltOS/doc/release-notes-1.6.2.pdf differ diff --git a/AltOS/doc/release-notes-1.6.3.pdf b/AltOS/doc/release-notes-1.6.3.pdf index 0f702b2..246b2ec 100644 Binary files a/AltOS/doc/release-notes-1.6.3.pdf and b/AltOS/doc/release-notes-1.6.3.pdf differ diff --git a/AltOS/doc/release-notes-1.6.4.pdf b/AltOS/doc/release-notes-1.6.4.pdf index 5fdc953..0afe18f 100644 Binary files a/AltOS/doc/release-notes-1.6.4.pdf and b/AltOS/doc/release-notes-1.6.4.pdf differ diff --git a/AltOS/doc/release-notes-1.6.5.pdf b/AltOS/doc/release-notes-1.6.5.pdf index fb333f2..86f5733 100644 Binary files a/AltOS/doc/release-notes-1.6.5.pdf and b/AltOS/doc/release-notes-1.6.5.pdf differ diff --git a/AltOS/doc/release-notes-1.6.8.pdf b/AltOS/doc/release-notes-1.6.8.pdf index 54474c9..0080e7a 100644 Binary files a/AltOS/doc/release-notes-1.6.8.pdf and b/AltOS/doc/release-notes-1.6.8.pdf differ diff --git a/AltOS/doc/release-notes-1.6.pdf b/AltOS/doc/release-notes-1.6.pdf index 503bdb9..e2661ad 100644 Binary files a/AltOS/doc/release-notes-1.6.pdf and b/AltOS/doc/release-notes-1.6.pdf differ diff --git a/AltOS/doc/release-notes-1.7.html b/AltOS/doc/release-notes-1.7.html new file mode 100644 index 0000000..5e6c548 --- /dev/null +++ b/AltOS/doc/release-notes-1.7.html @@ -0,0 +1,12 @@ + +Release Notes for Version 1.7

    Release Notes for Version 1.7

    Version 1.7 includes support for our new TeleMini v3.0 +flight computer and bug fixes in in the flight software for all our boards +and ground station interfaces.

    1. AltOS

    AltOS New Features

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

    AltOS Fixes

    • +Fix interrupt priorities on STM32L processors. Run timer +interrupt at lowest priority so that device interrupts get +serviced first. +

    2. AltosUI and TeleGPS Applications

    AltosUI New Features

    • +Add support for TeleMini v3.0 hardware +
    \ No newline at end of file diff --git a/AltOS/doc/release-notes-1.7.pdf b/AltOS/doc/release-notes-1.7.pdf new file mode 100644 index 0000000..9570b16 Binary files /dev/null and b/AltOS/doc/release-notes-1.7.pdf differ diff --git a/AltOS/doc/telegps.pdf b/AltOS/doc/telegps.pdf index c2a5f63..c26a9e3 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 9d9b569..9caf849 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 6f3e054..8aca946 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 0d0659f..52b7c9c 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 new file mode 100644 index 0000000..9683c1b Binary files /dev/null and b/AltOS/doc/telemini-v1-outline.pdf differ diff --git a/AltOS/doc/telemini-v1.svg b/AltOS/doc/telemini-v1.svg new file mode 100644 index 0000000..b2e21e3 --- /dev/null +++ b/AltOS/doc/telemini-v1.svg @@ -0,0 +1,31 @@ + + + + + + + + + + + + + + TeleMini + + UP + + + \ No newline at end of file diff --git a/AltOS/doc/telemini-v3-outline.pdf b/AltOS/doc/telemini-v3-outline.pdf new file mode 100644 index 0000000..e98ac7f Binary files /dev/null and b/AltOS/doc/telemini-v3-outline.pdf differ diff --git a/AltOS/doc/telemini-v3.0-bottom.jpg b/AltOS/doc/telemini-v3.0-bottom.jpg new file mode 100644 index 0000000..e4e4744 Binary files /dev/null and b/AltOS/doc/telemini-v3.0-bottom.jpg differ diff --git a/AltOS/doc/telemini-v3.0-top.jpg b/AltOS/doc/telemini-v3.0-top.jpg new file mode 100644 index 0000000..1539902 Binary files /dev/null and b/AltOS/doc/telemini-v3.0-top.jpg differ diff --git a/AltOS/doc/telemini-v3.svg b/AltOS/doc/telemini-v3.svg new file mode 100644 index 0000000..8835a2b --- /dev/null +++ b/AltOS/doc/telemini-v3.svg @@ -0,0 +1,33 @@ + + + + + + + + + + + + + + + + TeleMini v3 + + UP + + +