From e28ff195f95038471b14a8d1dc641b65ea365f5a Mon Sep 17 00:00:00 2001 From: Bdale Garbee Date: Thu, 21 Dec 2017 19:50:56 -0700 Subject: update docs --- AltOS/doc/easymini.html | 96 +++++++++++++++++++++++++------------------------ 1 file changed, 49 insertions(+), 47 deletions(-) (limited to 'AltOS/doc/easymini.html') diff --git a/AltOS/doc/easymini.html b/AltOS/doc/easymini.html index 82f5b44..03820f4 100644 --- a/AltOS/doc/easymini.html +++ b/AltOS/doc/easymini.html @@ -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.8.3
F.1.1. AltOS
F.1.2. AltosUI and TeleGPS Applications
F.2. Release Notes for Version 1.8.2
F.2.1. AltOS
F.2.2. AltosUI and TeleGPS Applications
F.3. Release Notes for Version 1.8.1
F.3.1. AltOS
F.3.2. AltosUI and TeleGPS Applications
F.4. Release Notes for Version 1.8
F.4.1. AltOS
F.4.2. AltosUI and TeleGPS Applications
F.5. Release Notes for Version 1.7
F.5.1. AltOS
F.5.2. AltosUI and TeleGPS Applications
F.6. Release Notes for Version 1.6.8
F.6.1. AltOS
F.6.2. AltosUI, TeleGPS and AltosDroid Applications
F.7. Release Notes for Version 1.6.5
F.7.1. AltOS
F.7.2. AltosUI, TeleGPS and AltosDroid Applications
F.8. Release Notes for Version 1.6.4
F.8.1. AltOS
F.8.2. AltosUI, TeleGPS and AltosDroid Applications
F.8.3. Documentation
F.9. Release Notes for Version 1.6.3
F.9.1. AltOS
F.9.2. AltosUI and TeleGPS Applications
F.9.3. AltosDroid
F.9.4. Documentation
F.10. Release Notes for Version 1.6.2
F.10.1. AltOS
F.10.2. AltosUI and TeleGPS Applications
F.10.3. Documentation

List of Figures

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

List of Tables

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

Chapter 1. Introduction and Overview

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

Table of Contents

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

Table 3.1. AltOS Modes

Mode Name

Abbreviation

Beeps

Description

Startup

S

battery voltage in decivolts

Calibrating sensors, detecting orientation.

Idle

I

dit dit

Ready to accept commands over USB

Pad

P

dit dah dah dit

Waiting for launch. Not listening for commands.

Boost

B

dah dit dit dit

Accelerating upwards.

Fast

F

dit dit dah dit

Decelerating, but moving faster than 200m/s.

Coast

C

dah dit dah dit

Decelerating, moving slower than 200m/s

Drogue

D

dah dit dit

Descending after apogee. Above main height.

Main

M

dah dah

Descending. Below main height.

Landed

L

dit dah dit dit

Stable altitude for at least ten seconds.

Sensor error

X

dah dit dit dah

Error detected during sensor calibration.


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

Table 3.1. AltOS Modes

Mode Name

Abbreviation

Beeps

Description

Startup

S

battery voltage in decivolts

Calibrating sensors, detecting orientation.

Idle

I

dit dit

Ready to accept commands over USB

Pad

P

dit dah dah dit

Waiting for launch. Not listening for commands.

Boost

B

dah dit dit dit

Accelerating upwards.

Fast

F

dit dit dah dit

Decelerating, but moving faster than 200m/s.

Coast

C

dah dit dah dit

Decelerating, moving slower than 200m/s

Drogue

D

dah dit dit

Descending after apogee. Above main height.

Main

M

dah dah

Descending. Below main height.

Landed

L

dit dah dit dit

Stable altitude for at least ten seconds.

Sensor error

X

dah dit dit dah

Error detected during sensor calibration.


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

Table 3.2. Pad/Idle Indications

Name Beeps Description

Neither

brap

No continuity detected on either apogee or main igniters.

Apogee

dit

Continuity detected only on apogee igniter.

Main

dit dit

Continuity detected only on main igniter.

Both

dit dit dit

Continuity detected on both igniters.

Storage Full

warble

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

Table 3.2. Pad/Idle Indications

Name Beeps Description

Neither

brap

No continuity detected on either apogee or main igniters.

Apogee

dit

Continuity detected only on apogee igniter.

Main

dit dit

Continuity detected only on main igniter.

Both

dit dit dit

Continuity detected on both igniters.

Storage Full

warble

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

Chapter 4. EasyMini

Figure 4.1. EasyMini Board

easymini-top.jpg

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

Chapter 4. EasyMini

Figure 4.1. EasyMini Board

easymini-top.jpg

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

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

Table 4.1. EasyMini Screw Terminals

Terminal #Terminal NameDescription

Top 1

Main -

Main pyro channel connection to pyro circuit

Top 2

Main

Main pyro channel common connection to battery

Top 3

Battery

Positive external battery terminal

Top 4

Battery -

Negative external battery terminal

Bottom 1

Apogee -

Apogee pyro channel connection to pyro circuit

Bottom 2

Apogee

Apogee pyro channel common connection to battery

Bottom 3

Switch Output

Switch connection to flight computer

Bottom 4

Switch Input

Switch connection to positive battery terminal


4.2. Connecting A Battery To EasyMini

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

Table 4.1. EasyMini Screw Terminals

Terminal #Terminal NameDescription

Top 1

Main -

Main pyro channel connection to pyro circuit

Top 2

Main

Main pyro channel common connection to battery

Top 3

Battery

Positive external battery terminal

Top 4

Battery -

Negative external battery terminal

Bottom 1

Apogee -

Apogee pyro channel connection to pyro circuit

Bottom 2

Apogee

Apogee pyro channel common connection to battery

Bottom 3

Switch Output

Switch connection to flight computer

Bottom 4

Switch Input

Switch connection to positive battery terminal


4.2. Connecting A Battery To EasyMini

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

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

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

Chapter 7. AltosUI

Figure 7.1. AltosUI Main Window

altosui.png

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

Chapter 7. AltosUI

Figure 7.1. AltosUI Main Window

altosui.png

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

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

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

7.3.1. Flight Graph

Figure 7.2. Flight Data Graph

graph.png

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

7.3.1. Flight Graph

Figure 7.2. Flight Data Graph

graph.png

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

The graph can be zoomed into a particular area by clicking and dragging down and to the right. Once zoomed, the graph can be reset by clicking and @@ -318,7 +318,7 @@ dragging up and to the left. Holding down control and clicking and dragging allows the graph to be panned. The right mouse button causes a pop-up menu to be displayed, giving you the option save or print the -plot.

7.3.2. Configure Graph

Figure 7.3. Flight Graph Configuration

graph-configure.png

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

7.3.2. Configure Graph

Figure 7.3. Flight Graph Configuration

graph-configure.png

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

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

7.3.3. Flight Statistics

Figure 7.4. Flight Statistics

graph-stats.png

Shows overall data computed from the flight.

7.4. Export Data

This tool takes the raw data files and makes them +

7.3.3. Flight Statistics

Figure 7.4. Flight Statistics

graph-stats.png

Shows overall data computed from the flight.

7.4. Export Data

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

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

7.5. Configure Altimeter

Figure 7.5. Altimeter Configuration

configure-altimeter.png

Select this button and then select an altimeter.

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

7.5. Configure Altimeter

Figure 7.5. Altimeter Configuration

configure-altimeter.png

Select this button and then select an altimeter.

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

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

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

7.6. Configure AltosUI

Figure 7.6. Configure AltosUI Dialog

configure-altosui.png

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

7.6. Configure AltosUI

Figure 7.6. Configure AltosUI Dialog

configure-altosui.png

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

7.6.1. Log Directory

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

7.8. Fire Igniter

Figure 7.7. Fire Igniter Window

fire-igniter.png

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

7.8. Fire Igniter

Figure 7.7. Fire Igniter Window

fire-igniter.png

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

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

Table D.1. Data Storage on Altus Metrum altimeters

Device Bytes per Sample Total Storage Minutes at Full Rate

EasyMini

16

1MB

10


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

Table D.1. Data Storage on Altus Metrum altimeters

Device Bytes per Sample Total Storage Minutes at Full Rate

EasyMini

16

1MB

10


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

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

Appendix E. Altus Metrum Hardware Specifications

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

Table E.1. Altus Metrum Flight Computer Electronics

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

EasyMini v1.0

MS5607 30km (100k')

-

-

-

1MB

-

3.7-12V


Table E.2. Altus Metrum Flight Computer Mechanical Components

DeviceConnectorsScrew TerminalsWidthLengthTube Size

EasyMini

Debug USB Battery

Apogee pyro Main pyro Battery

0.8 inch (2.03cm)

1½ inch (3.81cm)

24mm coupler


Appendix F. Release Notes

F.1. Release Notes for Version 1.8.3

Version 1.8.3 includes support for TeleMega version 3.0 along +production and retired.

Table E.1. Altus Metrum Flight Computer Electronics

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

EasyMini v1.0

MS5607 30km (100k')

-

-

-

1MB

-

3.7-12V


Table E.2. Altus Metrum Flight Computer Mechanical Components

DeviceConnectorsScrew TerminalsWidthLengthTube Size

EasyMini

Debug USB Battery

Apogee pyro Main pyro Battery

0.8 inch (2.03cm)

1½ inch (3.81cm)

24mm coupler


Appendix F. Release Notes

F.1. Release Notes for Version 1.8.4

Version 1.8.4 includes support for EasyMini version 2.0

F.1.1. AltOS

  • +Support for EasyMini version 2.0 hardware. +

F.2. Release Notes for Version 1.8.3

Version 1.8.3 includes support for TeleMega version 3.0 along with two important flight computer fixes. This version also changes KML export data to make Tripoli Record reporting better and some updates to graph presentation and data -downloading.

F.1.1. AltOS

AltOS New Features

  • +downloading.

    F.2.1. AltOS

    AltOS New Features

    • Support for TeleMega version 3.0 hardware.

    AltOS Bug Fixes

    • Ground testing EasyMega and TeleMega additional pyro @@ -677,7 +679,7 @@ from capturing log data.
    • Fixed saving of pyro configuration that ended with Descending. -

    F.1.2. AltosUI and TeleGPS Applications

    AltosUI New Features

    • +

    F.2.2. AltosUI and TeleGPS Applications

    AltosUI New Features

    • Support for TeleMega version 3.0.
    • Graph lines have improved appearance to make them easier to @@ -701,18 +703,18 @@ to make it more useful for Tripoli record reporting.
    • CSV export now includes TeleMega/EasyMega pyro voltages and tilt angle. -

F.2. Release Notes for Version 1.8.2

Version 1.8.2 includes support for TeleGPS version 2.0 along +

F.3. Release Notes for Version 1.8.2

Version 1.8.2 includes support for TeleGPS version 2.0 along with accelerometer recalibration support in AltosUI.

1.8.2 also contains a couple of minor fixes for AltosUI when -analyzing saved data files.

F.2.1. AltOS

AltOS New Features

  • +analyzing saved data files.

    F.3.1. AltOS

    AltOS New Features

    • Support for TeleGPS version 2.0 hardware. -

    F.2.2. AltosUI and TeleGPS Applications

    AltosUI and TeleGPS New Features

    • +

    F.3.2. AltosUI and TeleGPS Applications

    AltosUI and TeleGPS New Features

    • Support for TeleGPS version 2.0.
    • Accelerometer re-calibration user interface.

    AltosUI and TeleGPS Bug Fixes

    • Prevent some crashes when reading older saved flight data for graphing or KML export. -

F.3. Release Notes for Version 1.8.1

Version 1.8.1 includes an important bug fix for Apogee Lockout +

F.4. Release Notes for Version 1.8.1

Version 1.8.1 includes an important bug fix for Apogee Lockout operation in all flight computers. Anyone using this option must update firmware.

This release also contains a change in how flight computers with accelerometers deal with speeds around and above Mach @@ -722,7 +724,7 @@ disregard the barometric sensor above 330m/s (around Mach effect without ever going away entirely. This prevents early drogue deployment for flights which spend considerable time above Mach 1.

1.8.1 also contains a couple of minor fixes for AltosUI when -analyzing saved data files.

F.3.1. AltOS

AltOS Bug Fixes

  • +analyzing saved data files.

    F.4.1. AltOS

    AltOS Bug Fixes

    • Handle time value wrapping in Apogee Lockout correctly. Without this, apogee lockout would sometimes prevent any drogue charge from firing. @@ -731,7 +733,7 @@ Change Kalman filter on flight computers with accelerometer to continue using the barometric sensor even at high speeds to avoid unintentional drogue deployment during deceleration. -

    F.3.2. AltosUI and TeleGPS Applications

    AltosUI New Features

    • +

    F.4.2. AltosUI and TeleGPS Applications

    AltosUI New Features

    • Add new Huge font size to make text even bigger on high resolution monitors.

    AltosUI Bug Fixes

    • @@ -740,12 +742,12 @@ for graphing or KML export.
    • Load frequency preference at startup. The loading code was broken, so you’d see only the default frequencies. -

F.4. Release Notes for Version 1.8

Version 1.8 includes support for our new TeleBT v4.0 ground +

F.5. Release Notes for Version 1.8

Version 1.8 includes support for our new TeleBT v4.0 ground station, updates for data analysis in our ground station software and bug fixes in in the flight software for all our -boards and ground station interfaces.

F.4.1. AltOS

AltOS New Features

  • +boards and ground station interfaces.

    F.5.1. AltOS

    AltOS New Features

    • Add support for TeleBT v4.0 boards. -

    F.4.2. AltosUI and TeleGPS Applications

    AltosUI New Features

    • +

    F.5.2. AltosUI and TeleGPS Applications

    AltosUI New Features

    • Add support for TeleBT v4.0 hardware
    • Rewrite graphing and export functions. This code now handles @@ -756,20 +758,20 @@ acceleration data more accurate.

    AltosUI Bug Fixes

    • Correct axis labeling of magnetic sensor in TeleMega and EasyMega. The Y and Z axes were flipped. -

F.5. Release Notes for Version 1.7

Version 1.7 includes support for our new TeleMini v3.0 +

F.6. 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.5.1. AltOS

AltOS New Features

  • +and ground station interfaces.

    F.6.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.5.2. AltosUI and TeleGPS Applications

    AltosUI New Features

    • +

    F.6.2. AltosUI and TeleGPS Applications

    AltosUI New Features

    • Add support for TeleMini v3.0 hardware -

F.6. Release Notes for Version 1.6.8

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

F.7. 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.6.1. AltOS

AltOS fixes:

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

    F.7.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. @@ -782,7 +784,7 @@ flight.

    AltOS changes:

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

    F.6.2. AltosUI, TeleGPS and AltosDroid Applications

    AltosUI fixes:

    • +

    F.7.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 @@ -790,20 +792,20 @@ disabled to never re-appear.
    • Deal with ground station failure better during Configure Ground Station operation by cleaning up pending operations. -

F.7. Release Notes for Version 1.6.5

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

F.8. 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.7.1. AltOS

AltOS fixes:

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

    F.8.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.7.2. AltosUI, TeleGPS and AltosDroid Applications

    AltosUI fixes:

    • +

    F.8.2. AltosUI, TeleGPS and AltosDroid Applications

    AltosUI fixes:

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

F.8. Release Notes for Version 1.6.4

Version 1.6.4 fixes a bluetooth communication problem with +

F.9. 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.8.1. AltOS

AltOS fixes:

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

    F.9.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. @@ -811,7 +813,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.8.2. AltosUI, TeleGPS and AltosDroid Applications

    AltosUI, TeleGPS and AltosDroid New Features:

    • +

    F.9.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.
    • @@ -822,17 +824,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.8.3. Documentation

    • +

    F.9.3. Documentation

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

F.9. Release Notes for Version 1.6.3

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

F.10. 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.9.1. AltOS

AltOS fixes:

  • +along with BlueTooth support for Windows.

    F.10.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.9.2. AltosUI and TeleGPS Applications

    AltosUI and TeleGPS New Features:

    • +

    F.10.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. @@ -854,7 +856,7 @@ the connected Altus Metrum USB devices appear again.
    • Fix acceleration data presented in MonitorIdle mode for TeleMetrum v2.0 flight computers. -

    F.9.3. AltosDroid

    AltosDroid new features:

    • +

    F.10.3. AltosDroid

    AltosDroid new features:

    • Monitor Idle mode. Check state of flight computer while in idle mode over the radio link
    • @@ -892,12 +894,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.9.4. Documentation

    • +

    F.10.4. Documentation

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

F.10. Release Notes for Version 1.6.2

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

F.11. 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.10.1. AltOS

AltOS New Features:

  • +and ground station interfaces.

    F.11.1. AltOS

    AltOS New Features:

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

    AltOS Fixes:

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

    F.10.2. AltosUI and TeleGPS Applications

    AltosUI and TeleGPS Fixes:

    • +

    F.11.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.10.3. Documentation

    We spent a bunch of time trying to improve our documentation

    • +

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