X-Git-Url: https://git.gag.com/?a=blobdiff_plain;f=AltOS%2Fdoc%2Feasymini.html;h=91a326f011e4ce6a4b4e8af750b6cdd712bc806d;hb=821aac6888b80a89548b7ab7b9cbfa46f44ca1c3;hp=b52ea7efad375dcb14f6f4bded8ee65beca342ac;hpb=40609b89d9e4101858ec9f0d42b7ecc223dfcaf8;p=web%2Faltusmetrum diff --git a/AltOS/doc/easymini.html b/AltOS/doc/easymini.html index b52ea7e..91a326f 100644 --- a/AltOS/doc/easymini.html +++ b/AltOS/doc/easymini.html @@ -1,7 +1,7 @@ -EasyMini Owner’s Manual

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

Keith Packard

+

Bdale Garbee

Keith Packard

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

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

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.

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 +stored in on-board flash.


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-top.jpg

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

Chapter 4. EasyMini

Figure 4.1. EasyMini Board

easymini-top.jpg

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

You usually don’t need to configure EasyMini at all; it’s set up to do dual-deployment with an event at apogee to separate the airframe and deploy a drogue and another event at 250m @@ -176,7 +176,7 @@ board. Using the picture above, the top four have connections for the main pyro circuit and an external battery and the bottom four have connections for the apogee pyro circuit and the power -switch. Counting from the left, the connections are as follows:

Table 4.1. EasyMini Screw Terminals

Terminal #Terminal NameDescription

Top 1

Main -

Main pyro channel connection to pyro circuit

Top 2

Main

Main pyro channel common connection to battery

Top 3

Battery

Positive external battery terminal

Top 4

Battery -

Negative external battery terminal

Bottom 1

Apogee -

Apogee pyro channel connection to pyro circuit

Bottom 2

Apogee

Apogee pyro channel common connection to battery

Bottom 3

Switch Output

Switch connection to flight computer

Bottom 4

Switch Input

Switch connection to positive battery terminal


4.2. Connecting A Battery To EasyMini

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

Table 4.1. EasyMini Screw Terminals

Terminal #Terminal NameDescription

Top 1

Main -

Main pyro channel connection to pyro circuit

Top 2

Main

Main pyro channel common connection to battery

Top 3

Battery

Positive external battery terminal

Top 4

Battery -

Negative external battery terminal

Bottom 1

Apogee -

Apogee pyro channel connection to pyro circuit

Bottom 2

Apogee

Apogee pyro channel common connection to battery

Bottom 3

Switch Output

Switch connection to flight computer

Bottom 4

Switch Input

Switch connection to positive battery terminal


4.2. Connecting A Battery To EasyMini

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

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

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

Chapter 7. AltosUI

Figure 7.1. AltosUI Main Window

altosui.png

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

Chapter 7. AltosUI

Figure 7.1. AltosUI Main Window

altosui.png

The AltosUI program provides a graphical user interface for interacting with the Altus Metrum product family. AltosUI can monitor telemetry data, configure devices and many other tasks. The primary interface window provides a selection of @@ -308,7 +308,7 @@ record file, either a .telem file recording telemetry data or a flash memory.

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

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

7.3.1. Flight Graph

Figure 7.2. Flight Data Graph

graph.png

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

7.3.1. Flight Graph

Figure 7.2. Flight Data Graph

graph.png

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

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

7.3.2. Configure Graph

Figure 7.3. Flight Graph Configuration

graph-configure.png

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

7.3.2. Configure Graph

Figure 7.3. Flight Graph Configuration

graph-configure.png

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

7.3.3. Flight Statistics

Figure 7.4. Flight Statistics

graph-stats.png

Shows overall data computed from the flight.

7.4. Export Data

This tool takes the raw data files and makes them +imperial units

7.3.3. Flight Statistics

Figure 7.4. Flight Statistics

graph-stats.png

Shows overall data computed from the flight.

7.4. Export Data

This tool takes the raw data files and makes them available for external analysis. When you select this button, you are prompted to select a flight data file, which can be either a .eeprom or .telem. The .eeprom @@ -337,7 +337,7 @@ tools can be configured to skip over.

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

7.5. Configure Altimeter

Figure 7.5. Altimeter Configuration

configure-altimeter.png

Select this button and then select an altimeter.

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

7.5. Configure Altimeter

Figure 7.5. Altimeter Configuration

configure-altimeter.png

Select this button and then select an altimeter.

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

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

@@ -421,7 +421,7 @@ have more than one flight computer in a single airframe, having all of them sound at the same frequency can be confusing. This parameter lets you adjust the base beeper frequency -value.

7.6. Configure AltosUI

Figure 7.6. Configure AltosUI Dialog

configure-altosui.png

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

7.6. Configure AltosUI

Figure 7.6. Configure AltosUI Dialog

configure-altosui.png

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

7.6.1. Log Directory

AltosUI logs all telemetry data and saves all flash data to this directory. This directory is also used as the staring point @@ -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

fire-igniter.png

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

7.8. Fire Igniter

Figure 7.7. Fire Igniter Window

fire-igniter.png

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

Selecting the Fire Igniter button brings up the usual device selection dialog. Pick the desired @@ -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,7 +640,7 @@ flight data, so be sure to download flight data and erase it from the flight computer before it fills up. The flight computer will still successfully control the flight even if it cannot log data, so the only thing you will lose is the data.

Appendix E. Altus Metrum Hardware Specifications

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

Table E.1. Altus Metrum Flight Computer Electronics

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

EasyMini v1.0

MS5607 30km (100k')

-

-

-

1MB

-

3.7-12V


Table E.2. Altus Metrum Flight Computer Mechanical Components

DeviceConnectorsScrew TerminalsWidthLengthTube Size

EasyMini

Debug USB Battery

Apogee pyro Main pyro Battery

0.8 inch (2.03cm)

1½ inch (3.81cm)

24mm coupler


Appendix F. Release Notes

F.1. Release Notes for Version 1.6.3

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

Table E.1. Altus Metrum Flight Computer Electronics

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

EasyMini v1.0

MS5607 30km (100k')

-

-

-

1MB

-

3.7-12V


Table E.2. Altus Metrum Flight Computer Mechanical Components

DeviceConnectorsScrew TerminalsWidthLengthTube Size

EasyMini

Debug USB Battery

Apogee pyro Main pyro Battery

0.8 inch (2.03cm)

1½ inch (3.81cm)

24mm coupler


Appendix F. Release Notes

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