iFly GPS Forum

We have a new Forum!  Go here to get started: https://adventurepilot.community.forum.  
The new forum is easier to use and much more capable than the old, we hope you will join our community! 

Below is a copy of the old forum. This will remain available for a short period so you can access and review the information contained here. To continue a conversation, or start a new one, please register and create a post at our new forum location.
HomeHomeDiscussionsDiscussionsiFly General Di...iFly General Di...Altimeter instrument (aka "Ind.Alt") -- is showing what exactly?Altimeter instrument (aka "Ind.Alt") -- is showing what exactly?
Previous
 
Next
New Post
6/19/2020 12:48 AM
 

A quick, hopefully not dumb, question: what does this instrument display?  I can't find an explanation in the manual.  There are lots of altitudes, including GPS (which this is not), barometric ("corrected" or not), geometric, etc.

I basically want to know if it's showing me what ATC is likely seeing on their display as my aircraft's altitude, which I believe is my Mode C barometric altitude (pressure altitude I think) corrected by some nearby airport's barometer reading.  That (pressure?) altitude is obatined by the transponder from the "blind" altitude encoder, which in my plane is very old and subject to "drift".

The iFly Ind.Alt instrument is consistently showing an altitude that is about 250' higher than the iFly GPS Altitude instrument (which it is obtaining from my SkyRadar ADS-B In unit with WAAS, so I trust that it's pretty accurate). My "real" instrument panel altimeter is indicating altitudes reasonably close to that GPS altitude.  But this iFly Ind.Alt instrument is considerably higher.  I'm just trying to figure out what it's telling me.


Powrachute PC 2000; Aventura II; Cherokee 180
 
New Post
6/19/2020 5:46 AM
 

Some ADSB-In devices, like a Stratux built to include the optional AHRS board, have barometric sensors on them and report pressure data in their datastream to iFly.  iFly can automatically pick up local pressure corrections from nearby METARs and apply that to the barometric reading from the ADSB-In device to present an "Indicated Altitude".  However, when in flight the pressure inside the cabin is lower than the static pressure sensed outside the aircraft, which results in a higher-than-actual altimeter reading.

Other ADSB-In devices can "sniff" the encoded altitude being output by your transponder, and include that in the datastream feeding iFly.  iFly can also use that to generate an Indicated Altitdue.  In that case, your transponder should have a static pressure input, so it should not be subject to the error from sensing cabin pressure, but may have other errors (like rounding off to the nearest 100').

So if you had said "Stratux" as your ADSB-In device, this would be a good explanation.  If you can confirm your SkyRadar device also includes barometric pressure sensor support like the Stratux, then it may still be a good explanation, but if not, then this probably isn't the answer.

 

 
New Post
6/19/2020 9:24 AM
 

If I can put an underline on what you were saying: if the SkyRadar is supplying its own barometric altitude in the data stream to iFly, then iFly is likely showing that, and it has no certain relationship with what ATC would see as my altitude.  But if it's coming from my transponder (via SkyBeacon's sniffing of my transponder output, and then SkyRadar pulling it out of the ADS-B Out stream) then it possibly would. 

I am making an assumption here that ATC does not use altitude from my ADS-B output, but instead still uses Mode C transponder data. If ATC does use ADS-B data to display my altitude, then I'm concerned that this Ind.Alt I'm seeing is in fact what ATC is seeing, in which case it is very wrong.  I should probably contact ATC and ask what they're seeing for my altitude, huh?

It could also be that there's a bug in iFly and it's applying an incorrect pressure correction, or where none is needed (e.g. SkyRadar is supplying an altitude number that does not need it).  Does anyone else out there use this Altitude instrument (aka "Ind.Alt" in it's title box) and does it agree more or less with GPS altitude in your aircraft?

It would be good if someone from iFly would weigh in on this.


Powrachute PC 2000; Aventura II; Cherokee 180
 
New Post
6/19/2020 1:15 PM
 
Hook wrote:

I am making an assumption here that ATC does not use altitude from my ADS-B output, but instead still uses Mode C transponder data. If ATC does use ADS-B data to display my altitude, then I'm concerned that this Ind.Alt I'm seeing is in fact what ATC is seeing, in which case it is very wrong.  I should probably contact ATC and ask what they're seeing for my altitude, huh?

It could also be that there's a bug in iFly and it's applying an incorrect pressure correction, or where none is needed (e.g. SkyRadar is supplying an altitude number that does not need it).  Does anyone else out there use this Altitude instrument (aka "Ind.Alt" in it's title box) and does it agree more or less with GPS altitude in your aircraft?

I don't know for sure which data is being presented to ATC, but I would also guess it's your Mode C data, and agree a call to ATC might clear that right up.  At any rate, it's almost certain that iFly's "Indicated altitude" is NOT what ATC's seeing:  ATC's either seeing your ADSB-out GPS-based altitude, or else they're seeing your Mode C altitude (pressure altitude, aka "Indicated altitude when Kollsman window shows 29.92") and applying their own Kollsman correction at their console, which is not necessarily the same Kollsman correction that iFly has selected from the nearby METARs.

I have the iFly indicated altitude displayed on my device, but in general I simply ignore it because it doesn't really give me anything I need.  I maintain altitude by what I read off my altimeter, and until the FAA tells me I should do something different, all the rest of the altitude indications in my plane are extraneous and I don't worry much about them.  The devices I have that provide collision warnings with terrain or other aircraft will catch my attention if I'm within 1000' vertically of a collision hazard, so if worst-case it's only alerting when I get within 700 or 800' (because of "errors" / different ways of measuring altitude), that's still good enough for me.

The baro sensor on my Stratux is part of a simple $15 AHRS board riding on a Raspberri Pi, so I don't expect it to be perfect.  Plus, it's sensing the cabin pressure, not what's in my static pressure system lines.  Plus, iFly is making its own choice of Kollsman correction, which I don't religiously hawk to make sure it agrees with what I've selected (or been instructed by ATC to use).  So there are lots of opportunities for iFly's Indicated altitude to diverge from what I see on my instrument...

 
New Post
6/19/2020 1:37 PM
 

Yeah, I'm beginning to wonder what this instrument is good for and whether I should have it displayed.  But I'd like to hear from iFly what goes into that number.

[Update: as I sit here at home, I brought up iFly on my phone to ponder my instrument layout and possibly removing the Ind.Alt instrument.  It currently displays "unavail" in that box.  I tapped on it to see what would happen and it brought up a dialog box that says "No Pressure Altitude (PA).  The Altimeter's Indicated Altitude requires ownship 'Pressure Altitude' (PA), fed from an ADS-B device that provides this reading.  Not all ADS-B devices provide PA."  It further says that it will "flash current GPS Altitude for reference", which I assume is what it does while it waits for an ADS-B PA source.

So, based on this tidbit of info, it seems to me that either SkyRadar is sending an incorrect PA, or iFly is applying too big a correction to it.  Also, this PA that SkyRadar is sending to iFly: is it self-derived or is it coming from the transponder?  If the latter, then that was what is/was causing me worry. ...And now that I look on the SkyRadar website and in the very thin manual, nowhere does it mention altitude sensing, so it must be getting it from the SkyBeacon, which is getting it from the transponder.  It seems to me then that it's more likely that the PA being given to iFly is off because of this daisy-chain of encoder-to-transponder-to-SkyBeacon-to-SkyRadar-to-iFly.]


Powrachute PC 2000; Aventura II; Cherokee 180
 
Previous
 
Next
HomeHomeDiscussionsDiscussionsiFly General Di...iFly General Di...Altimeter instrument (aka "Ind.Alt") -- is showing what exactly?Altimeter instrument (aka "Ind.Alt") -- is showing what exactly?