EasyMini Owner’s Manual

A Dual-Deploy Rocketry Flight Computer

+EasyMini Owner’s Manual
EasyMini Owner’s Manual
A Dual-Deploy Rocketry Flight Computer
-
Bdale Garbee
`<bdale@gag.com>`
Keith Packard
`<keithp@keithp.com>`
Copyright © 2016 Bdale Garbee and Keith Packard
+

Bdale Garbee

<bdale@gag.com>

Keith Packard

<keithp@keithp.com>

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. Linux/Mac/Windows Ground Station Software

3. Using Altus Metrum Hardware

3.1. Wiring and Electrical Interference
3.2. Hooking Up Lithium Polymer Batteries
3.3. Hooking Up Pyro Charges
3.4. Hooking Up a Power Switch
3.5. Understanding Beeps
3.6. Turning On the Power
3.7. Using an External Active Switch Circuit
3.8. Using a Separate Pyro Battery
3.9. Using a Different Kind of Battery

4. EasyMini

4.1. EasyMini Screw Terminals
4.2. Connecting A Battery To EasyMini
4.3. Charging Lithium Batteries
4.4. Using a Separate Pyro Battery with EasyMini
4.5. Using an Active Switch with EasyMini

5. Installation

6. Using Altus Metrum Products

6.1. In the Rocket
6.2. On the Ground
6.3. Data Analysis
6.4. Future Plans

7. AltosUI

7.1. Save Flight Data

7.2. Replay Flight

7.3. Graph Data

7.3.1. Flight Graph
7.3.2. Configure Graph
7.3.3. Flight Statistics

7.4. Export Data

7.4.1. Comma Separated Value Format

7.5. Configure Altimeter

7.5.1. Main Deploy Altitude
7.5.2. Apogee Delay
7.5.3. Apogee Lockout
7.5.4. Maximum Flight Log Size
7.5.5. Ignitor Firing Mode
7.5.6. Beeper Frequency

7.6. Configure AltosUI

7.6.1. Log Directory
7.6.2. Imperial Units
7.6.3. Serial Debug
7.6.4. Font size
7.6.5. Look & feel
7.6.6. Menu position

7.7. Flash Image

7.8. Fire Igniter

A. System Operation

A.1. Firmware Modes
A.2. Ground Testing
A.3. Configurable Parameters

B. Handling Precautions

C. Updating Device Firmware

C.1. Updating EasyMini Firmware

C.1.1. Recovering From Self-Flashing Failure

D. Flight Data Recording

E. Altus Metrum Hardware Specifications

F. Release Notes

F.1. Release Notes for Version 1.6.2

F.1.1. AltOS
F.1.2. AltosUI and TeleGPS Applications
F.1.3. Documentation

List of Figures

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

List of Tables

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

Chapter 1. Introduction and Overview

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

Table of Contents

1. Introduction and Overview

2. Getting Started

2.1. Batteries
2.2. Linux/Mac/Windows Ground Station Software

3. Using Altus Metrum Hardware

3.1. Wiring and Electrical Interference
3.2. Hooking Up Lithium Polymer Batteries
3.3. Hooking Up Pyro Charges
3.4. Hooking Up a Power Switch
3.5. Understanding Beeps
3.6. Turning On the Power
3.7. Using an External Active Switch Circuit
3.8. Using a Separate Pyro Battery
3.9. Using a Different Kind of Battery

4. EasyMini

4.1. EasyMini Screw Terminals
4.2. Connecting A Battery To EasyMini
4.3. Charging Lithium Batteries
4.4. Using a Separate Pyro Battery with EasyMini
4.5. Using an Active Switch with EasyMini

5. Installation

6. Using Altus Metrum Products

6.1. In the Rocket
6.2. On the Ground
6.3. Data Analysis
6.4. Future Plans

7. AltosUI

7.1. Save Flight Data

7.2. Replay Flight

7.3. Graph Data

7.3.1. Flight Graph
7.3.2. Configure Graph
7.3.3. Flight Statistics

7.4. Export Data

7.4.1. Comma Separated Value Format

7.5. Configure Altimeter

7.5.1. Main Deploy Altitude
7.5.2. Apogee Delay
7.5.3. Apogee Lockout
7.5.4. Maximum Flight Log Size
7.5.5. Ignitor Firing Mode
7.5.6. Beeper Frequency

7.6. Configure AltosUI

7.6.1. Log Directory
7.6.2. Imperial Units
7.6.3. Serial Debug
7.6.4. Font size
7.6.5. Look & feel
7.6.6. Menu position

7.7. Flash Image

7.8. Fire Igniter

A. System Operation

A.1. Firmware Modes
A.2. Ground Testing
A.3. Configurable Parameters

B. Handling Precautions

C. Updating Device Firmware

C.1. Updating EasyMini Firmware

C.1.1. Recovering From Self-Flashing Failure

D. Flight Data Recording

E. Altus Metrum Hardware Specifications

F. Release Notes

F.1. Release Notes for Version 1.6.3

F.1.1. AltOS
F.1.2. AltosUI and TeleGPS Applications
F.1.3. AltosDroid
F.1.4. Documentation

F.2. Release Notes for Version 1.6.2

F.2.1. AltOS
F.2.2. AltosUI and TeleGPS Applications
F.2.3. Documentation

List of Figures

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

List of Tables

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

Chapter 1. Introduction and Overview

Welcome to the Altus Metrum community! Our circuits and software reflect our passion for both hobby rocketry and Free Software. We hope their capabilities and performance will delight you in every way, but by releasing all of our hardware and software designs under open licenses, @@ -105,16 +105,16 @@ beeping that accompanies each mode. In the description of the beeping pattern, “dit” means a short beep while "dah" means a long beep (three times as long). “Brap” means -a long dissonant tone.

Table 3.1. AltOS Modes

Mode Name	Abbreviation	Beeps	Description
Startup	S	battery voltage in decivolts	Calibrating sensors, detecting orientation.
Idle	I	dit dit	Ready to accept commands over USB
Pad	P	dit dah dah dit	Waiting for launch. Not listening for commands.
Boost	B	dah dit dit dit	Accelerating upwards.
Fast	F	dit dit dah dit	Decelerating, but moving faster than 200m/s.
Coast	C	dah dit dah dit	Decelerating, moving slower than 200m/s
Drogue	D	dah dit dit	Descending after apogee. Above main height.
Main	M	dah dah	Descending. Below main height.
Landed	L	dit dah dit dit	Stable altitude for at least ten seconds.
Sensor error	X	dah dit dit dah	Error detected during sensor calibration.

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

Table 3.1. AltOS Modes

Mode Name	Abbreviation	Beeps	Description
Startup	S	battery voltage in decivolts	Calibrating sensors, detecting orientation.
Idle	I	dit dit	Ready to accept commands over USB
Pad	P	dit dah dah dit	Waiting for launch. Not listening for commands.
Boost	B	dah dit dit dit	Accelerating upwards.
Fast	F	dit dit dah dit	Decelerating, but moving faster than 200m/s.
Coast	C	dah dit dah dit	Decelerating, moving slower than 200m/s
Drogue	D	dah dit dit	Descending after apogee. Above main height.
Main	M	dah dah	Descending. Below main height.
Landed	L	dit dah dit dit	Stable altitude for at least ten seconds.
Sensor error	X	dah dit dit dah	Error detected during sensor calibration.

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

Table 3.2. Pad/Idle Indications

Name

Beeps

Description

Neither

brap

No continuity detected on either apogee or main igniters.

Apogee

dit

Continuity detected only on apogee igniter.

Main

dit dit

Continuity detected only on main igniter.

Both

dit dit dit

Continuity detected on both igniters.

Storage Full

warble

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

Table 3.2. Pad/Idle Indications

Name	Beeps	Description
Neither	brap	No continuity detected on either apogee or main igniters.
Apogee	dit	Continuity detected only on apogee igniter.
Main	dit dit	Continuity detected only on main igniter.
Both	dit dit dit	Continuity detected on both igniters.
Storage Full	warble	On-board data logging storage is full. This will not prevent the flight computer from safely controlling the flight or transmitting telemetry signals, but no record of the flight will be -stored in on-board flash.

3.6. Turning On the Power

Connect a battery and power switch and turn the switch +stored in on-board flash.

Additional Igniters

four very short beeps

Continuity indication for the four additional pyro

channels on TeleMega and EasyMega. One high tone for

no continuity, one low tone for continuity. These are

produced after the continuity indicators for the two

3.6. Turning On the Power

Connect a battery and power switch and turn the switch to "on". The flight computer will signal power on by reporting the battery voltage and then perform an internal self test and sensor calibration.

Once the self test and calibration are complete, there @@ -165,7 +165,7 @@ is designed to use either a lithium polymer battery or any other battery producing between 4 and 12 volts, such as a rectangular 9V -battery.

Chapter 4. EasyMini

Figure 4.1. EasyMini Board

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

Terminal #	Terminal Name	Description
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

Terminal #	Terminal Name	Description
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

7.6. Configure AltosUI

Figure 7.6. Configure AltosUI Dialog

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

7.6.1. Log Directory

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

7.8. Fire Igniter

Figure 7.7. Fire Igniter Window

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

7.8. Fire Igniter

Figure 7.7. Fire Igniter Window

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

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

Table D.1. Data Storage on Altus Metrum altimeters

Device	Bytes per Sample	Total Storage	Minutes at Full Rate
EasyMini	16	1MB	10

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

Table D.1. Data Storage on Altus Metrum altimeters

Device	Bytes per Sample	Total Storage	Minutes at Full Rate
EasyMini	16	1MB	10

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

Configuration data is also stored in the flash memory on @@ -640,9 +640,78 @@ flight data, so be sure to download flight data and erase it from the flight computer before it fills up. The flight computer will still successfully control the flight even if it cannot log data, so the only thing you will lose is the data.

Appendix E. Altus Metrum Hardware Specifications

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

Table E.1. Altus Metrum Flight Computer Electronics

Device	Barometer	Z-axis accel	GPS	3D sensors	Storage	RF Output	Battery
EasyMini v1.0	MS5607 30km (100k')	-	-	-	1MB	-	3.7-12V

Table E.2. Altus Metrum Flight Computer Mechanical Components

Device	Connectors	Screw Terminals	Width	Length	Tube Size
EasyMini	Debug USB Battery	Apogee pyro Main pyro Battery	0.8 inch (2.03cm)	1½ inch (3.81cm)	24mm coupler

Appendix F. Release Notes

F.1. Release Notes for Version 1.6.2

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

Table E.1. Altus Metrum Flight Computer Electronics

Device	Barometer	Z-axis accel	GPS	3D sensors	Storage	RF Output	Battery
EasyMini v1.0	MS5607 30km (100k')	-	-	-	1MB	-	3.7-12V

Table E.2. Altus Metrum Flight Computer Mechanical Components

Device	Connectors	Screw Terminals	Width	Length	Tube Size
EasyMini	Debug USB Battery	Apogee pyro Main pyro Battery	0.8 inch (2.03cm)	1½ inch (3.81cm)	24mm coupler

Appendix F. Release Notes

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

AltosUI and TeleGPS Fixes:

+Change Java detection and install on Windows. Detection is +now done by looking for the javaw.exe program, and +installation by opening a browser on the java.com web site. +
+Delay polling while the Fire Igniters is visible to allow +for TeleMega to report back complete status over the radio. +
+Disallow changing RF calibration numbers in the +configuration UI. There’s no good reason to change this from +the field, and recovering is really hard if you haven’t +written down the right number. +
+Fix USB device discovery on Mac OS X El Capitan. This makes +the connected Altus Metrum USB devices appear again. +
+Fix acceleration data presented in MonitorIdle mode for +TeleMetrum v2.0 flight computers. +

F.1.3. AltosDroid

AltosDroid new features:

+Monitor Idle mode. Check state of flight computer while in +idle mode over the radio link +
+Fire Igniters. Remotely fire ignires for recovery system +ground tests. +
+Remote reboot. Cause the flight computer to reboot over the +radio link. This provides a method for switching the flight +computer from idle to flight mode without needing to reach +the power switch. +
+Configurable frequency menu. Change the set of available +frequencies and provide more descriptive names. +

AltosDroid bug fixes:

+Don’t set target location if GPS hasn’t locked yet. +
+Fix saving target states so they can be reloaded when the +application restarts. When the application is shut down and +restarted, all previous target state information will be +restored (including GPS position if available). +
+Fix crash on some Android devices for offline maps when +changing the map scale or location. +
+Don’t require USB OTG support. This kept the latest +AltosDroid from being offered on devices without USB device +support, although it can work without that just fine using +BlueTooth. +
+Don’t require bluetooth to be enabled. This allows the +application to operate with USB devices or just show old +data without turning on the bluetooth radio. +
+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.1.4. Documentation

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

F.2. 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.1.1. AltOS

AltOS New Features:

+and ground station interfaces.
F.2.1. AltOS
AltOS New Features:
- Add support for TeleMega v2.0 boards.
- Add PWM servo driver. There’s no higher level code using @@ -651,14 +720,14 @@ servo output connector.
AltOS Fixes:
- Slow down telemetry packets to allow receiver to keep up. -
F.1.2. AltosUI and TeleGPS Applications
AltosUI and TeleGPS Fixes:
- +
F.2.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.1.3. Documentation
We spent a bunch of time trying to improve our documentation
- +
F.2.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. -- cgit v1.2.3

EasyMini Owner’s Manual

A Dual-Deploy Rocketry Flight Computer