iGlide update for iPhone 6 (4.7 inch) and iPhone 6 plus (5.5 inch)

The iPhone 6+ with iGlide (updated to use the new screen and hardware, barometric pressure, etc) would definitely be an economical and easy to use solution for cross country or racing navigation for pilots of all experience levels. I find the screen on my iPhone 5 to be bright enough. Hopefully the 6+ will be even brighter. The new barometric pressure sensor is probably very, very smart (perhaps better than what we have in existing loggers?) as it is mainly intended for the health app and in particular accurately measuring stair climbs and daily activity (it will also be important for health apps on the new Apple watch). Apple is under great pressure to catch up with and compete with Android phones in this area. I wonder if XC Soar has taken advantage of the barometric pressure sensors in the Android phones?

In terms of MATs I have been using an SN10 and an Oudie backup or iGlide (Perry). In terms of US rules 2 min under max start height, I simply use a stop watch and mechanical altimeter (cross referenced with SN10 altitude) with lots of buffer (2:30 to 3 min and usually 200 extra feet) to be safe from a penalty.

For MAT task "management" I have not learned of a flight computer that does a good job of automating the decision making process for choosing the right extra turnpoints (what do you recommend?). I simply estimate the choices manually and make the best choice I can based on key indicators. Choosing extra MAT turns is a very complex thing from a programming perspective. The computer can't see the clouds, other gliders (markers), can't see the terrain, towns, fields, etc. I would be skeptical of how a flight computer can support a MAT decision making process effectively. I would not trust or value the timing information or turnpoints recommendations said flight computer provides (I'm assuming one does this) in most cases. Anyway, for me, MAT tasks (not my favorite, I would much prefer pure Assigned Tasking with no complex time/distance "hocus pocus") are just about considering the key variables and making the "best guess" I can manually, often with a paper map. I'll add the turn(s) into the computer once I have made the general decision manually.

SIDENOTE: This guess we all make at the end of a MAT task (say we arrive at the last turn with 20 min to "kill") is a huge decision and can make or break the task for any given pilot. Perhaps this is "too huge" of a decision. This moment in a MAT can easily and drastically change the results (up to that point in the task) if the leaders make the wrong decision or the distance to the next available turnpoints does not work out as "cleanly" as it might for others behind. Just a few minutes or the nature of the nearby turnpoints (distance, terrain, cloud situation, etc) can make a massive difference in the final MAT task result. Of course the reverse can be true and it may work out perfectly for the leader and not for the trailers. I have actually won two task days I probably should not have for this very reason. Because of this, again, I would much prefer pure Assigned Tasks and think we need to fly a higher proportion of them (ATs not MATs) in the future. I feel ATs are are simply better tests. -END OF RANT

So, what am I missing? Have I set myself up for a ClearNav feature review :-)? Does the CN or perhaps the LX9000 handle MATs better? I'm guessing the LX 9000 does not support US rules?

Sean
7T

On Tuesday, September 16, 2014 10:01:59 AM UTC-5, Sean Fidler wrote:


In terms of MATs I have been using an SN10 and an Oudie backup or iGlide (Perry). In terms of US rules 2 min under max start height, I simply use a stop watch and mechanical altimeter (cross referenced with SN10 altitude) with lots of buffer (2:30 to 3 min and usually 200 extra feet) to be safe from a penalty.

You do realize that the Oudie (SYM) has a nice little 2 minute below MSH before starting countdown timer? Makes the process hands off and painless...

Kirk
66

I have a problem getting reliable altitude with the Oudie for some reason. It seems to drift up or down compared to mechanical altimeter and the SN10. The SN10 is fairly spot on so I trust it more than the Oudie. I need to do so e research on this problem for sure.

On Tuesday, September 16, 2014 7:39:48 PM UTC-7, Sean Fidler wrote:
I have a problem getting reliable altitude with the Oudie for some reason.. It seems to drift up or down compared to mechanical altimeter and the SN10. The SN10 is fairly spot on so I trust it more than the Oudie. I need to do so e research on this problem for sure.

Sean,

Don't you have a V7? It can output directly to an Oudie with Baro data.

The XCSoar program is able to use the Android Baro data in all of the one's I've tried. I used to have a Samsung Note II that was great for XCS and had a Baro sensor. Seemed to match the in-aircraft altimeter pretty well.

Mike

Thanks. I had a V7 in my Lak17a, but that has been sold and now I have an ASG29 with an SN10. Considering options......

On Wednesday, September 17, 2014 5:12:00 PM UTC-5, Sean Fidler wrote:
Thanks. I had a V7 in my Lak17a, but that has been sold and now I have an ASG29 with an SN10. Considering options......

I assume you have a PFlarm core? One cable hooks up the PF, SN10, and Oudie - you get flarm warnings on your SN10 and Oudie, and air data (vario, winds, altitude) from the SN10 to the Oudie. And the PFlarm GPS drives the SN10 and Oudie.

Works beautifully, totally plug and play. Cable from Cumulus.

Kirk

Thanks Evan and Kirk!

On Tue, 16 Sep 2014 08:01:59 -0700, Sean Fidler wrote:

I wonder if XC Soar has taken advantage of
the barometric pressure sensors in the Android phones?

I would be surprised if it hasn't.

At the start of this season I switched PNAs and moved LK8000 (originally
an XCSoar clone) onto a new Medion S3747, which has a trans-reflective
screen and a pressure sensor. As soon as I configured LK8000 to use the
pressure sensor it 'just used it' and has continued to do so ever since.


--
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |

On Tuesday, September 16, 2014 4:01:59 PM UTC+1, Sean Fidler wrote:
The new barometric pressure sensor is probably very, very smart (perhaps better than what we have in existing loggers?)

Not really 'better', since cost and size has priority in this application, but the accuracy should certainly be good enough for logging purposes. Minimum pressure is 300hpa (~30,000ft).

http://www.bosch-sensortec.com/en_GB.../bmp280/bmp280

The reported sensor in the iPhone 6 is the BMP282. The performance is unlikely to be different from the above sensor.

I wonder if XC Soar has taken advantage of the barometric pressure sensors in the Android phones?

Yes, if the device has a pressure sensor the pressure altitude will be recorded in the IGC file. There's also an audio variometer function (uncompensated), which is reportedly very good with recent Samsung phones.

On Tuesday, September 16, 2014 11:01:59 AM UTC-4, Sean Fidler wrote:

So, what am I missing? Have I set myself up for a ClearNav feature review :-)? Does the CN or perhaps the LX9000 handle MATs better?

CN plots a blue ellipse on the map that becomes visible during the later stages of a MAT. What the ellipse means is this: if you fly to any turnpoint inside the ellipse, then to the finish, you will be early. The ellipse updates continuously and accounts for wind, altitude, predicted thermal climb rate.

Evan Ludeman for CNi