Altus Metrum boards support radio frequencies in the 70cm band. By default, the configuration interface provides a list of 10 “standard” frequencies in 100kHz channels starting at 434.550MHz. However, the firmware supports use of any 50kHz multiple within the 70cm band. At any given launch, we highly recommend coordinating when and by whom each frequency will be used to avoid interference. And of course, both TeleGPS and the receiver must be configured to the same frequency to successfully communicate with each other.

This sets the callsign used for telemetry and APRS to identify the device.

You can completely disable the radio, if necessary, leaving TeleGPS only logging data to internal memory.

This selects how often APRS packets are transmitted. Set this to zero to disable APRS without also disabling the regular telemetry and RDF transmissions. As APRS takes a full second to transmit a single position report, we recommend sending packets no more than once every 5 seconds.

Changing this value will set the maximum amount of flight log storage that an individual flight will use. The available storage is divided into as many flights of the specified size as can fit in the available space. You can download and erase individual flight logs. If you fill up the available storage, future flights will not get logged until you erase some of the stored ones.

If TeleGPS moves less than this distance over a long period of time, it will not log that location, saving storage space.

This sets how often TeleGPS reports position information via telemetry and to the on-board log. Reducing this value will save power and logging memory consumption.

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

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 being received.

You can adjust the style of map and the zoom level with buttons on the right side of the map window. You can draw a line on the map by moving the mouse over the map with a button other than the left one pressed, or by pressing the left button while also holding down the shift key. The length of the line in real-world units will be shown at the start of the line.

Images are fetched automatically via the Google Maps Static API, and cached on disk for reuse. If map images cannot be downloaded, the 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 the 'Preload Maps' section below.

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

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

The Table tab shows detailed information about the GPS receiver

This creates another telemetry monitoring window, in case you have multiple TeleDongle devices connected to the computer.

This brings up a file dialog to load a saved log, either a .telem file of recorded telemetry or .eeprom of saved data from on-board memory. It looks a bit like the flight monitoring window, using a selection of tabs to show different views of the saved data.

2.2.1. Graph

The Graph tab shows a plot of the the GPS data collected. The X axis is time in seconds; there are a variety of Y axes available for different kinds of data.

2.2.2. Configure Graph

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

2.2.3. Statistics

Shows overall data computed from the flight.

2.2.4. 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 the left button and you can draw a line to measure distances using either the left button with the shift key, or any other button.

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 data file, which can be either a .eeprom or .telem. The .eeprom files contain higher resolution and more continuous data, while .telem files contain receiver signal strength information. Next, a second dialog appears which is used to select where to write the resulting file. It has a selector to choose between CSV and KML file formats.

Before using TeleGPS, you can use Load Maps to load map data in case you don't have access to the internet while receiving telemetry.

There's a drop-down menu of rocket launch sites we know about; if your favorites aren't there, please let us know the lat/lon and name of the site. The contents of this list are actually downloaded from our server at run-time, so as new sites are sent in, they'll get automatically added to this list. If the launch site isn't in the list, you can manually enter the lat/lon values

There are four different kinds of maps you can view; you can select which to download by selecting as many as you like from the available types:

You can specify the range of zoom levels to download; smaller numbers show more area with less resolution. The default level, 0, shows about 3m/pixel. One zoom level change doubles or halves that number.

The Tile Radius value sets how large an area around the center point to download. Each tile is 512x512 pixels, and the 'radius' value specifies how many tiles away from the center will be downloaded. Specify a radius of 0 and you get only the center tile. A radius of 1 loads a 3x3 grid, centered on the specified location.

Clicking the 'Load Map' button will fetch images from 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.

This closes the current window, leaving any other windows open and the application running.

This closes all TeleGPS windows and terminates the application.

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.

Disconnects the currently connected TeleDongle or TeleBT

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 associated TeleGPS application window.

TeleGPS records data to its internal flash memory. On-board data is recorded at the same rate as telemetry but is not subject to radio drop-outs. As such, it generally provides a more complete and precise record. The 'Download Data' menu entry allows you to read the flash memory and write it to disk.

Select the 'Download Data' menu entry to bring up a list of connected TeleGPS devices. After the device has been selected, a dialog showing the data stored in the device will be shown allowing you to select which entries to download and which to delete. You must erase flights in order for the space they consume to be reused by another track. This prevents accidentally losing data if you neglect to download data before 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.

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 number. Below that are the individual configuration entries.

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

The rest of the dialog contains the parameters to be configured.

This reprograms TeleGPS devices with new firmware. Please read the directions for flashing devices in the Updating Device Firmware chapter below.