Let's go back and look at some of the previous Oz Report articles
about the AltAir flight instrument/vario/pod.

http://ozreport.com/21.28#0

http://ozreport.com/21.097#0

Home for the software, by Evgen Lysenko:
http://altair.no-ip.org/index.html

Pod and flight instrument:
https://www.facebook.com/altairvario/

This is the AltAir software running on the AltAir hardware that is inside the
pods from Oleg Matvieiev:

I have a pod from Oleg. It includes a battery for charging the phone in flight,
but does not include the AltAir vario/flight computer or pitot tube as I have an
external vario (XCTracer) that I would like to hook up to the AltAir software.

I have created three screens for my AltAir configuration. I'll no doubt change
them as I get used to the device.

Each of the fields displayed on the screens below, referred to as widgets by the
software, can be moved, resized, color changed, text border color changed, a box
around the widget added (it is the default),  the title size changed, you
can choose whether there is a title or not, the level of transparency changed,
deleted, and a lot more. There are over 70 widgets to choose from.

The widget sizing is very incremental with snap to a fine grained visible grid.

Some widgets are action oriented. You touch them and an action takes place, for
example, switching to the next screen or zooming in on the map.

The inside the Start Cylinder screen:

Most of the top half of each of the three screens starting with the value for my
current "Direction" of travel field and going up the right side are exactly the
same. The values displayed in the fields are as follows from the top right hand
side on down:

Barometric/pressure "Altitude, ft" set equal to GPS altitude at launch.

Wind speed, "Wind Spd, mph" and wind direction arrow overlaying each other.

Direction arrow to the "Next Waypoint," with the name of the waypoint right
below the direction arrow.

Distance to the next waypoint, "Dist WP, km".

On the left hand side of the upper half of the screen I have:

"Next Screen," which means tap here to switch to the next screen.

"+" and "-" i.e., zoom in on the map and zoom out.

The "Vertical Speed, fpm," which is the 20 second average of my climb rate.

Below the averaged "Vertical Speed,fpm" but not visible, are my analog varios
showing graphically my instantaneous and averaged rate of climb (or sink). These
two elements are also displayed on the next screen, the one used for flying on
the course line. They are not displayed on the third screen, the final glide
screen.

The bottom half of this screen is dedicated to information useful when waiting
in the start cylinder for the task to start.

Right below the  "Direction" widget is the current time.

My current total air speed, "TAS" and ground speed, "Speed."

The ground speed that I need to fly at to get to the edge of the start cylinder in
time for the window to just open, "Speed Start Cyl, mph."

How much time is left before the start gate opens, "time st cyl."

The distance to the edge of the start cylinder, "Dist Cyl, km."

The task screen for thermaling and gliding around the course:

This is the same as the start screen, but without the two fields that were only
needed for the start. I have the distance to the waypoint and the distance to
the waypoint cylinder.

The map will show the task and my position along the task. I can zoom in and out
and see more closely whether I'm about to tag the next turnpoint.

The final glide screen:

The key fields for final glide are the bottom five.

"Altitude at Goal, ft" displays the altitude that I will arrive at goal at given
your current speed under the standard assumptions about what lies ahead of me
with respect to lift, sink and wind.

"Alt BG Goal, ft" displays my altitude above the best glide line to goal, or
equivalently the altitude I will arrive at goal at if I fly at my best glide
speed, i.e. my Speed-To-Fly assuming a McCready value of 0 fpm.

"Dist Goal, km" is pretty obvious.

L/D ground is my current glide ratio over the ground (not just relative to the
air).

L/D goal is my required L/D over the ground in order to make goal.

As you can see these variables are similar to the ones displayed on the Flytec
6030. All the discussion that I presented in the previous article about the
Flytec 6030 applies to these variables,
http://ozreport.com/22.137#0.

I have not used the AltAir hardware vario. Greg Dinauer found that the volume
setting was too low on the original hardware. They are replacing that for him.
Here is his comparison with the Flytec 6030:
http://ozreport.com/pub/images/altairgreg.mp4.

I originally tried out the AltAir software on my Samsung Galaxy S4. I couldn't
see the screen in bright sunlight, like we have in Florida, Texas, and Arizona.
I will check it out on a Samsung Galaxy S6. Oleg states that it is visible on
phones with phones with amoled screens or IPS screens with OGS (one glass
screen) technology. He says that some pilots are experimenting with white digits
on black backgrounds.

As you can see from my screens, the AltAir software can configured to be very
much like the Flytec 6030. Since many pilots use this hardware it is a great
idea to build in the same functionality into your software. This makes the
transition a lot easier. Missing, but coming in the future are: wind component
and Speed-to-Fly speed widgets.

My configuration is found in this file which you can import into AltAir (after
you export your existing one):
http://ozreport.com/data/davisstraub_settings.xml. This includes all the
screen/page configurations. If you just want to copy the screen configurations
over existing or onto new pages you can find them here:
http://ozreport.com/data/start2.cfg,
http://ozreport.com/data/thermal2.cfg, and
http://ozreport.com/data/final2.cfg.

I have since copied the USA OpenAir-formatted airspace into the AltAir airspace
folder. It works perfectly. You'll find it here:
http://www.maddyhome.com/hangglide/airspace.html.