TeleGPS Owner’s Manual

An Owner's Manual for the TeleGPS recording GPS tracker

+TeleGPS Owner’s Manual
TeleGPS Owner’s Manual
An Owner's Manual for the TeleGPS recording GPS tracker
-
Bdale Garbee
`<bdale@gag.com>`
Keith Packard
`<keithp@keithp.com>`
Copyright © 2015 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 @@ -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. Micro-controller
C.3. Lithium Polymer Battery
C.4. Mechanical Considerations
C.5. On-board data storage

D. Updating Device Firmware

D.1. Updating TeleGPS Firmware

E. Release Notes

E.1. Release Notes for Version 1.6.2

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

E.2. Release Notes for Version 1.6.1

E.2.1. AltOS
E.2.2. AltosUI and TeleGPS Applications
E.2.3. AltosDroid

E.3. Release Notes for Version 1.6

E.3.1. AltOS
E.3.2. AltosUI and TeleGPS Applications

E.4. Release Notes for Version 1.5

E.4.1. AltOS
E.4.2. AltosUI and TeleGPS Applications

E.5. Release Notes for Version 1.4.2

E.5.1. AltosUI and TeleGPS Applications

E.6. Release Notes for Version 1.4.1

E.6.1. AltosUI and TeleGPS Applications:

E.7. Release Notes for Version 1.4

E.7.1. AltOS
E.7.2. AltosUI Application
E.7.3. TeleGPS Application
E.7.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. Micro-controller
C.3. Lithium Polymer Battery
C.4. Mechanical Considerations
C.5. 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 components, flying takes just a few steps.

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

The map’s default scale is approximately 3m +the device.
Figure 3.1. TeleGPS Map View

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

3.1.3. Status
The Status tab shows data relative to the +received from TeleGPS.
Figure 3.2. TeleGPS Location View

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

3.1.4. Table
The Table tab shows detailed information about -the GPS receiver
Figure 3.4. TeleGPS Information Table

3.2. TeleGPS Menus

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

Figure 3.3. TeleGPS Status View

3.1.4. Table

The Table tab shows detailed information about +the GPS receiver

Figure 3.4. TeleGPS Information Table

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

3.3.2. Graph Configuration
Figure 3.6. TeleGPS Graph Configuration

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

3.3.2. Graph Configuration
Figure 3.6. TeleGPS Graph Configuration

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

Shows overall data computed from the flight.
3.3.4. Map
Figure 3.8. TeleGPS Map

Shows a map of the area overlaid with the GPS track. As with +units
3.3.3. Statistics
Figure 3.7. TeleGPS Statistics

Shows overall data computed from the flight.
3.3.4. Map
Figure 3.8. TeleGPS Map

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

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

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

3.6.1. Voice Settings

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

3.6. Preferences

Figure 3.10. TeleGPS Preferences Window

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

3.10. Disconnect

Disconnects the currently connected TeleDongle or -TeleBT

3.11. Scan Channels

Figure 3.12. Radio Scanning Dialog

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

Figure 3.11. Device Selection Dialog

3.10. Disconnect

Disconnects the currently connected TeleDongle or +TeleBT

3.11. Scan Channels

Figure 3.12. Radio Scanning Dialog

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

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

3.13. Configure Device

Figure 3.13. TeleGPS Configuration Dialog

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 @@ -553,9 +553,78 @@ 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.2

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

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 +for our host software on desktops, laptops an android devices +along with BlueTooth support for Windows.

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

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

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

E.1.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 product and bug fixes in in the flight software for all our boards -and ground station interfaces.

E.1.1. AltOS

AltOS New Features:

+and ground station interfaces.
E.2.1. AltOS
AltOS New Features:
- Add support for TeleMega v2.0 boards.
- Add PWM servo driver. There’s no higher level code using @@ -564,14 +633,14 @@ servo output connector.
AltOS Fixes:
- Slow down telemetry packets to allow receiver to keep up. -
E.1.2. AltosUI and TeleGPS Applications
AltosUI and TeleGPS Fixes:
- +
E.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. -
E.1.3. Documentation
We spent a bunch of time trying to improve our documentation
- +
E.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. @@ -580,9 +649,9 @@ Provide links between sections in each document.
- Lots of minor rewriting and restructuring to avoid duplication of information -

E.2. Release Notes for Version 1.6.1

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

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

AltOS New Features:

+and ground station interfaces.
E.3.1. AltOS
AltOS New Features:
- Add support for TeleBT v3.0 boards.
- Add support for uncompressed APRS data, providing support @@ -592,7 +661,7 @@ altitude data.
AltOS Fixes:
- Make TeleDongle and TeleBT more tolerant of data rate variations from transmitting devices. -
E.2.2. AltosUI and TeleGPS Applications
AltosUI and TeleGPS New Features:
- +
E.3.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. @@ -630,7 +699,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.2.3. AltosDroid
AltosDroid New Features:
- +
E.3.3. AltosDroid
AltosDroid New Features:
- Add offline map support using mapping code from AltosUI.
- Support TeleDongle (and TeleBT via USB) on devices @@ -658,9 +727,9 @@ Make voice announcements depend on current tab.
- Compute adjustment to current travel direction while in motion towards rocket. -

E.3. Release Notes for Version 1.6

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

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

AltOS New Features

+and ground station interfaces.
E.4.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. @@ -680,7 +749,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.3.2. AltosUI and TeleGPS Applications
AltosUI and TeleGPS New Features
- +
E.4.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 @@ -726,9 +795,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.4. Release Notes for Version 1.5

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

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

AltOS New Features

+software for all our boards and the AltosUI ground station
E.5.1. AltOS
AltOS New Features
- Add support for EasyMega boards.
- Make the APRS SSID be configurable. This lets you track @@ -762,7 +831,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.4.2. AltosUI and TeleGPS Applications
AltosUI and TeleGPS New Features
- +
E.5.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. @@ -779,18 +848,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.5. Release Notes for Version 1.4.2

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

E.5.1. AltosUI and TeleGPS Applications

Windows Install Fixes

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

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

E.6. Release Notes for Version 1.4.1

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

E.7. 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.6.1. AltosUI and TeleGPS Applications:

Windows Install Fixes

+V2.0 firmware image will not need to upgrade.
E.7.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.
- @@ -808,9 +877,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.7. Release Notes for Version 1.4

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

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

AltOS new features:

+software for all our boards and the AltosUI ground station
E.8.1. AltOS
AltOS new features:
- Add support for TeleGPS boards.
- Make the beeper tone configurable, making it @@ -840,7 +909,7 @@ number to 2 on TeleMega and TeleMetrum v2.
- Fix u-Blox GPS driver to mark course and speed data as being present. -
E.7.2. AltosUI Application
AltosUI new features:
- +
E.8.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 @@ -897,12 +966,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.7.3. TeleGPS Application
- +
E.8.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.7.4. Documentation
Documentation changes:
- +
E.8.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

TeleGPS Owner’s Manual

An Owner's Manual for the TeleGPS recording GPS tracker