From 054f696fedf7799e005e8f06208c3aa4086b0cb4 Mon Sep 17 00:00:00 2001 From: Bdale Garbee Date: Mon, 11 Dec 2017 22:02:13 -0700 Subject: update docs --- AltOS/doc/telegps.html | 247 +++++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 206 insertions(+), 41 deletions(-) (limited to 'AltOS/doc/telegps.html') diff --git a/AltOS/doc/telegps.html b/AltOS/doc/telegps.html index 752a998..67b36ca 100644 --- a/AltOS/doc/telegps.html +++ b/AltOS/doc/telegps.html @@ -14,7 +14,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. TeleGPS Quick Start Guide
2. Using TeleGPS Hardware
2.1. Hooking Up Lithium Polymer Batteries
2.2. On-board Data Recording
2.3. Installation
3. TeleGPS Application
3.1. Telemetry Monitoring
3.1.1. Map
3.1.2. Location
3.1.3. Status
3.1.4. Table
3.2. TeleGPS Menus
3.2.1. New Window
3.3. Graph Data
3.3.1. Data Graph
3.3.2. Graph Configuration
3.3.3. Statistics
3.3.4. Map
3.4. Export Data
3.4.1. Comma Separated Value Format
3.4.2. Keyhole Markup Language (for Google Earth)
3.5. Load Maps
3.6. Preferences
3.6.1. Voice Settings
3.6.2. Log Directory
3.6.3. Callsign
3.6.4. Imperial Units
3.6.5. Serial Debug
3.6.6. Font size
3.6.7. Look & feel
3.6.8. Menu position
3.6.9. Map Cache Size
3.6.10. Manage Frequencies
3.7. Close
3.8. Exit
3.9. Connect Device
3.10. Disconnect
3.11. Scan Channels
3.12. Download Data
3.13. Configure Device
3.13.1. Frequency
3.13.2. RF Calibration
3.13.3. Telemetry/RDF/APRS Enable
3.13.4. Telemetry baud rate
3.13.5. APRS Interval
3.13.6. APRS SSID
3.13.7. APRS Format
3.13.8. Callsign
3.13.9. Logging Trigger Motion
3.13.10. Position Reporting Interval
3.14. Flash Device
A. TeleGPS System Operation
A.1. GFSK Telemetry
A.2. APRS
A.3. Configurable Parameters
B. Handling Precautions
C. Technical Information
C.1. GPS Receiver
C.2. 70cm Transmitter
C.3. Micro-controller
C.4. Lithium Polymer Battery
C.5. Mechanical Considerations
C.6. On-board data storage
D. Updating Device Firmware
D.1. Updating TeleGPS Firmware
E. Release Notes
E.1. Release Notes for Version 1.6.3
E.1.1. AltOS
E.1.2. AltosUI and TeleGPS Applications
E.1.3. AltosDroid
E.1.4. Documentation
E.2. Release Notes for Version 1.6.2
E.2.1. AltOS
E.2.2. AltosUI and TeleGPS Applications
E.2.3. Documentation
E.3. Release Notes for Version 1.6.1
E.3.1. AltOS
E.3.2. AltosUI and TeleGPS Applications
E.3.3. AltosDroid
E.4. Release Notes for Version 1.6
E.4.1. AltOS
E.4.2. AltosUI and TeleGPS Applications
E.5. Release Notes for Version 1.5
E.5.1. AltOS
E.5.2. AltosUI and TeleGPS Applications
E.6. Release Notes for Version 1.4.2
E.6.1. AltosUI and TeleGPS Applications
E.7. Release Notes for Version 1.4.1
E.7.1. AltosUI and TeleGPS Applications:
E.8. Release Notes for Version 1.4
E.8.1. AltOS
E.8.2. AltosUI Application
E.8.3. TeleGPS Application
E.8.4. Documentation

List of Figures

3.1. TeleGPS Map View
3.2. TeleGPS Location View
3.3. TeleGPS Status View
3.4. TeleGPS Information Table
3.5. TeleGPS Graph
3.6. TeleGPS Graph Configuration
3.7. TeleGPS Statistics
3.8. TeleGPS Map
3.9. Load Maps Window
3.10. TeleGPS Preferences Window
3.11. Device Selection Dialog
3.12. Radio Scanning Dialog
3.13. TeleGPS Configuration Dialog

List of Tables

A.1. Altus Metrum APRS Comments

Chapter 1. TeleGPS Quick Start Guide

TeleGPS is designed to be easy to use. Requiring no external +NAR #88757, TRA #12200

Table of Contents

1. TeleGPS Quick Start Guide
2. Using TeleGPS Hardware
2.1. Hooking Up Lithium Polymer Batteries
2.2. On-board Data Recording
2.3. Installation
3. TeleGPS Application
3.1. Telemetry Monitoring
3.1.1. Map
3.1.2. Location
3.1.3. Status
3.1.4. Table
3.2. TeleGPS Menus
3.2.1. New Window
3.3. Graph Data
3.3.1. Data Graph
3.3.2. Graph Configuration
3.3.3. Statistics
3.3.4. Map
3.4. Export Data
3.4.1. Comma Separated Value Format
3.4.2. Keyhole Markup Language (for Google Earth)
3.5. Load Maps
3.6. Preferences
3.6.1. Voice Settings
3.6.2. Log Directory
3.6.3. Callsign
3.6.4. Imperial Units
3.6.5. Serial Debug
3.6.6. Font size
3.6.7. Look & feel
3.6.8. Menu position
3.6.9. Map Cache Size
3.6.10. Manage Frequencies
3.7. Close
3.8. Exit
3.9. Connect Device
3.10. Disconnect
3.11. Scan Channels
3.12. Download Data
3.13. Configure Device
3.13.1. Frequency
3.13.2. RF Calibration
3.13.3. Telemetry/RDF/APRS Enable
3.13.4. Telemetry baud rate
3.13.5. APRS Interval
3.13.6. APRS SSID
3.13.7. APRS Format
3.13.8. Callsign
3.13.9. Logging Trigger Motion
3.13.10. Position Reporting Interval
3.14. Flash Device
A. TeleGPS System Operation
A.1. GFSK Telemetry
A.2. APRS
A.3. Configurable Parameters
B. Handling Precautions
C. Technical Information
C.1. GPS Receiver
C.2. 70cm Transmitter
C.3. Micro-controller
C.4. Lithium Polymer Battery
C.5. Mechanical Considerations
C.6. On-board data storage
D. Updating Device Firmware
D.1. Updating TeleGPS Firmware
E. Release Notes
E.1. Release Notes for Version 1.8.3
E.1.1. AltOS
E.1.2. AltosUI and TeleGPS Applications
E.2. Release Notes for Version 1.8.2
E.2.1. AltOS
E.2.2. AltosUI and TeleGPS Applications
E.3. Release Notes for Version 1.8.1
E.3.1. AltOS
E.3.2. AltosUI and TeleGPS Applications
E.4. Release Notes for Version 1.8
E.4.1. AltOS
E.4.2. AltosUI and TeleGPS Applications
E.5. Release Notes for Version 1.7
E.5.1. AltOS
E.5.2. AltosUI and TeleGPS Applications
E.6. Release Notes for Version 1.6.8
E.6.1. AltOS
E.6.2. AltosUI, TeleGPS and AltosDroid Applications
E.7. Release Notes for Version 1.6.5
E.7.1. AltOS
E.7.2. AltosUI, TeleGPS and AltosDroid Applications
E.8. Release Notes for Version 1.6.4
E.8.1. AltOS
E.8.2. AltosUI, TeleGPS and AltosDroid Applications
E.8.3. Documentation
E.9. Release Notes for Version 1.6.3
E.9.1. AltOS
E.9.2. AltosUI and TeleGPS Applications
E.9.3. AltosDroid
E.9.4. Documentation
E.10. Release Notes for Version 1.6.2
E.10.1. AltOS
E.10.2. AltosUI and TeleGPS Applications
E.10.3. Documentation
E.11. Release Notes for Version 1.6.1
E.11.1. AltOS
E.11.2. AltosUI and TeleGPS Applications
E.11.3. AltosDroid
E.12. Release Notes for Version 1.6
E.12.1. AltOS
E.12.2. AltosUI and TeleGPS Applications
E.13. Release Notes for Version 1.5
E.13.1. AltOS
E.13.2. AltosUI and TeleGPS Applications
E.14. Release Notes for Version 1.4.2
E.14.1. AltosUI and TeleGPS Applications
E.15. Release Notes for Version 1.4.1
E.15.1. AltosUI and TeleGPS Applications:
E.16. Release Notes for Version 1.4
E.16.1. AltOS
E.16.2. AltosUI Application
E.16.3. TeleGPS Application
E.16.4. Documentation

List of Figures

3.1. TeleGPS Map View
3.2. TeleGPS Location View
3.3. TeleGPS Status View
3.4. TeleGPS Information Table
3.5. TeleGPS Graph
3.6. TeleGPS Graph Configuration
3.7. TeleGPS Statistics
3.8. TeleGPS Map
3.9. Load Maps Window
3.10. TeleGPS Preferences Window
3.11. Device Selection Dialog
3.12. Radio Scanning Dialog
3.13. TeleGPS Configuration Dialog

List of Tables

A.1. Altus Metrum APRS Comments

Chapter 1. TeleGPS Quick Start Guide

TeleGPS is designed to be easy to use. Requiring no external components, flying takes just a few steps.

  1. First, download and install the software from http://altusmetrum.org/AltOS. This will make sure that @@ -131,7 +131,7 @@ tabs, each of which contain some information about the TeleGPS board. The final table tab displays many of the raw telemetry values in one place in a spreadsheet-like format.

    3.1.1. Map

    The Map tab shows the TeleGPS track over time on top of map data making it easy to locate -the device.

    Figure 3.1. TeleGPS Map View

    telegps-map.png

    The map’s default scale is approximately 3m +the device.

    Figure 3.1. TeleGPS Map View

    telegps-map.png

    The map’s default scale is approximately 3m (10ft) per pixel. The map can be dragged using the left mouse button. The map will attempt to keep the rocket roughly centered while data is @@ -150,10 +150,10 @@ 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 3.5, “Load Maps”.

    3.1.2. Location

    The Location tab shows the raw GPS data -received from TeleGPS.

    Figure 3.2. TeleGPS Location View

    telegps-location.png

    3.1.3. Status

    The Status tab shows data relative to the +received from TeleGPS.

    Figure 3.2. TeleGPS Location View

    telegps-location.png

    3.1.3. Status

    The Status tab shows data relative to the location of TeleGPS when the application first -received telemetry from it.

    Figure 3.3. TeleGPS Status View

    telegps-status.png

    3.1.4. Table

    The Table tab shows detailed information about -the GPS receiver

    Figure 3.4. TeleGPS Information Table

    telegps-table.png

3.2. TeleGPS Menus

TeleGPS has three or four menus at the top of +received telemetry from it.

Figure 3.3. TeleGPS Status View

telegps-status.png

3.1.4. Table

The Table tab shows detailed information about +the GPS receiver

Figure 3.4. TeleGPS Information Table

telegps-table.png

3.2. TeleGPS Menus

TeleGPS has three or four menus at the top of the window:

File
@@ -183,9 +183,9 @@ collected. The X axis is time in seconds; there are a variety of Y axes available for different kinds of data. This window also allows you to see some statistics computed from the data, and an overall map -of the entire data record.

3.3.1. Data Graph

Figure 3.5. TeleGPS Graph

telegps-graph-graph.png

3.3.2. Graph Configuration

Figure 3.6. TeleGPS Graph Configuration

telegps-graph-configure.png

This selects which graph elements to show, and, at the +of the entire data record.

3.3.1. Data Graph

Figure 3.5. TeleGPS Graph

telegps-graph-graph.png

3.3.2. Graph Configuration

Figure 3.6. TeleGPS Graph Configuration

telegps-graph-configure.png

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

3.3.3. Statistics

Figure 3.7. TeleGPS Statistics

telegps-graph-stats.png

Shows overall data computed from the flight.

3.3.4. Map

Figure 3.8. TeleGPS Map

telegps-graph-map.png

Shows a map of the area overlaid with the GPS track. As with +units

3.3.3. Statistics

Figure 3.7. TeleGPS Statistics

telegps-graph-stats.png

Shows overall data computed from the flight.

3.3.4. Map

Figure 3.8. TeleGPS Map

telegps-graph-map.png

Shows a map of the area overlaid with the GPS track. As with the telemetry monitoring window, you can select the style of map and zoom level using buttons along the side; you can scroll the map by dragging within the map pressing @@ -215,7 +215,7 @@ are converted to standard units, with the barometric data reported in both pressure, altitude and height above pad units.

3.4.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 path in 3D.

3.5. Load Maps

Figure 3.9. Load Maps Window

load-maps.png

Before heading out to a new launch site, you can use +see the whole path in 3D.

3.5. Load Maps

Figure 3.9. Load Maps Window

load-maps.png

Before heading out to a new launch site, you can use this to load satellite images in case you don’t have internet connectivity at the site.

There’s a drop-down menu of launch sites we know about; if your favorites aren’t there, please let us @@ -263,7 +263,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.

3.6. Preferences

Figure 3.10. TeleGPS Preferences Window

telegps-preferences.png

3.6.1. Voice Settings

TeleGPS provides voice announcements during +you. Try again later.

3.6. Preferences

Figure 3.10. TeleGPS Preferences Window

telegps-preferences.png

3.6.1. Voice Settings

TeleGPS provides voice announcements during flight so that you can keep your eyes on the sky and still get information about the current flight status. However, sometimes you @@ -332,8 +332,8 @@ open and the application running.

3.9. Connect Device

Selecting this item brings up a dialog box listing all of the connected TeleDongle devices. When you choose one of these, AltosUI will display telemetry data as -received by the selected TeleDongle device.

Figure 3.11. Device Selection Dialog

device-selection.png

3.10. Disconnect

Disconnects the currently connected TeleDongle or -TeleBT

3.11. Scan Channels

Figure 3.12. Radio Scanning Dialog

telegps-scan.png

Scans the configured set of frequencies looking for +received by the selected TeleDongle device.

Figure 3.11. Device Selection Dialog

device-selection.png

3.10. Disconnect

Disconnects the currently connected TeleDongle or +TeleBT

3.11. Scan Channels

Figure 3.12. Radio Scanning Dialog

telegps-scan.png

Scans the configured set of frequencies looking for telemetry signals. A list of all of the discovered signals is show; selecting one of those and clicking on Monitor will select that frequency in the @@ -354,7 +354,7 @@ starting TeleGPS again. Note that if there is no more space available in the device, then no data will be recorded.

The file name for each data log is computed automatically from the recorded date, altimeter serial -number and flight number information.

3.13. Configure Device

Figure 3.13. TeleGPS Configuration Dialog

telegps-configure.png

Select this button and then select any connected TeleGPS +number and flight number information.

3.13. Configure Device

Figure 3.13. TeleGPS Configuration Dialog

telegps-configure.png

Select this button and then select any connected TeleGPS 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 @@ -469,7 +469,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

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

1286

Device Serial Number


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 and GPS is locked with at least 5 or 6 satellites in view before flying. If GPS is switching between L and @@ -554,13 +554,178 @@ progress bar. Verify that the device is working by using the 'Configure Device item to check over the configuration. -

Appendix E. Release Notes

E.1. Release Notes for Version 1.6.3

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

Appendix E. Release Notes

E.1. 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.

E.1.1. AltOS

AltOS New Features

  • +Support for TeleMega version 3.0 hardware. +

AltOS Bug Fixes

  • +Ground testing EasyMega and TeleMega additional pyro +channels could result in a sticky fired status which would +prevent these channels from firing on future flights. +
  • +Corrupted flight log records could prevent future flights +from capturing log data. +
  • +Fixed saving of pyro configuration that ended with +Descending. +

E.1.2. AltosUI and TeleGPS Applications

AltosUI New Features

  • +Support for TeleMega version 3.0. +
  • +Graph lines have improved appearance to make them easier to +distinguish. Markers may be placed at data points to show +captured recorded data values. +
  • +Graphing offers the ability to adjust the smoothing of +computed speed and acceleration data. +
  • +The download dialog now offers to graph new flights, checks +for existing files to avoid overwriting data and reports if +there are checksum errors in the downloaded data. +

AltosUI/TeleGPS Bug Fixes

  • +Restore TeleGPS tracking behavior. +
  • +Display flight computer call sign and serial number in +Monitor Idle mode instead of ground station values. +

AltosUI and TeleGPS Changes

  • +KML export now reports both barometric and GPS altitude data +to make it more useful for Tripoli record reporting. +
  • +CSV export now includes TeleMega/EasyMega pyro voltages and +tilt angle. +

E.2. 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.

E.2.1. AltOS

AltOS New Features

  • +Support for TeleGPS version 2.0 hardware. +

E.2.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. +

E.3. 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 +1. In previous versions, the flight computer would completely +disregard the barometric sensor above 330m/s (around Mach +1). Now, the data from the barometric sensor is reduced in +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.

E.3.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. +
  • +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. +

E.3.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

  • +Prevent some crashes when reading older saved flight data +for graphing or KML export. +
  • +Load frequency preference at startup. The loading code was +broken, so you’d see only the default frequencies. +

E.4. 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.

E.4.1. AltOS

AltOS New Features

  • +Add support for TeleBT v4.0 boards. +

E.4.2. AltosUI and TeleGPS Applications

AltosUI New Features

  • +Add support for TeleBT v4.0 hardware +
  • +Rewrite graphing and export functions. This code now handles +each data series separately so that graphs are drawn +correctly. Smoothing now uses a filter that looks both +forward and backwards in time to make computed speed and +acceleration data more accurate. +

AltosUI Bug Fixes

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

E.5. 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.

E.5.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. +

E.5.2. AltosUI and TeleGPS Applications

AltosUI New Features

  • +Add support for TeleMini v3.0 hardware +

E.6. 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.

E.6.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. +
  • +Avoid having TeleBT battery status values smash telemetry +packet data by holding a lock during both operations. +
  • +Don’t start reporting flight 0 when the log fills in +flight. +

AltOS changes:

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

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

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

E.7.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. +

E.7.2. AltosUI, TeleGPS and AltosDroid Applications

AltosUI fixes:

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

E.8. 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.

E.8.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. +
  • +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. +

E.8.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. +
  • +Add Monitor Idle mode to TeleGPS application. +

AltosUI, TeleGPS and AltosDroid Fixes:

  • +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. +

E.8.3. Documentation

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

E.9. 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.

E.1.1. AltOS

AltOS fixes:

  • +along with BlueTooth support for Windows.

    E.9.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. -

    E.1.2. AltosUI and TeleGPS Applications

    AltosUI and TeleGPS New Features:

    • +

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

    E.1.3. AltosDroid

    AltosDroid new features:

    • +

    E.9.3. AltosDroid

    AltosDroid new features:

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

    E.1.4. Documentation

    • +

    E.9.4. Documentation

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

E.2. Release Notes for Version 1.6.2

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

E.10. 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.

E.2.1. AltOS

AltOS New Features:

  • +and ground station interfaces.

    E.10.1. AltOS

    AltOS New Features:

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

    AltOS Fixes:

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

    E.2.2. AltosUI and TeleGPS Applications

    AltosUI and TeleGPS Fixes:

    • +

    E.10.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. -

    E.2.3. Documentation

    We spent a bunch of time trying to improve our documentation

    • +

    E.10.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. @@ -650,9 +815,9 @@ Provide links between sections in each document.
    • Lots of minor rewriting and restructuring to avoid duplication of information -

E.3. Release Notes for Version 1.6.1

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

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

E.3.1. AltOS

AltOS New Features:

  • +and ground station interfaces.

    E.11.1. AltOS

    AltOS New Features:

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

    AltOS Fixes:

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

    E.3.2. AltosUI and TeleGPS Applications

    AltosUI and TeleGPS New Features:

    • +

    E.11.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. @@ -700,7 +865,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. -

    E.3.3. AltosDroid

    AltosDroid New Features:

    • +

    E.11.3. AltosDroid

    AltosDroid New Features:

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

E.4. Release Notes for Version 1.6

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

E.12. 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.

E.4.1. AltOS

AltOS New Features

  • +and ground station interfaces.

    E.12.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. @@ -750,7 +915,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. -

    E.4.2. AltosUI and TeleGPS Applications

    AltosUI and TeleGPS New Features

    • +

    E.12.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 @@ -796,9 +961,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. -

E.5. Release Notes for Version 1.5

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

E.13. 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

E.5.1. AltOS

AltOS New Features

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

    E.13.1. AltOS

    AltOS New Features

    • Add support for EasyMega boards.
    • Make the APRS SSID be configurable. This lets you track @@ -832,7 +997,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. -

    E.5.2. AltosUI and TeleGPS Applications

    AltosUI and TeleGPS New Features

    • +

    E.13.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. @@ -849,18 +1014,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. -

E.6. Release Notes for Version 1.4.2

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

E.6.1. AltosUI and TeleGPS Applications

Windows Install Fixes

  • +

E.14. Release Notes for Version 1.4.2

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

E.14.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. -

E.7. Release Notes for Version 1.4.1

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

E.15. 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.

E.7.1. AltosUI and TeleGPS Applications:

Windows Install Fixes

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

    E.15.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.
    • @@ -878,9 +1043,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. -

E.8. Release Notes for Version 1.4

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

E.16. 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

E.8.1. AltOS

AltOS new features:

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

    E.16.1. AltOS

    AltOS new features:

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

    E.8.2. AltosUI Application

    AltosUI new features:

    • +

    E.16.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 @@ -967,12 +1132,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. -

    E.8.3. TeleGPS Application

    • +

    E.16.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. -

    E.8.4. Documentation

    Documentation changes:

    • +

    E.16.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. -- cgit v1.2.3