Wishlist for the next IFD software release

When I am on the map page, I see category flags and I touch an airport to see information. I would find it very helpful if the pop up window had an icon for the full airport info and wx. This seems a more intuitive way rather than have to find a nearest or other key to press.   

I  would like the boundaries of an airport's circling approach areas (Cat A - E)  to be depicted on the map when a specific approach procedure for that airport is entered into the Flight Plan.  The radii defining the circling approach area are determined by the both the approach category (i.e., airspeed) and MDA of the selected approach procedure.  Avidyne could depict all 5 areas, or, better, could give the pilot the option to specify the approach category.  The approach category could be set by a Setup User Option.

Yes my installer and Avidyne had several discussions, during the MLB100 installation, and I insisted Avidyne provide a wiring diagram to the installer, which they did.  The installer wired it as per Avidyne instructions.  Yes I want the 10'precision and not the gray code.

It's in the candidate database. No specific release tagged to it at this time.

Where do I look for the Cyan message?
In the bottom right corner where the rest of the alerts show up?

Any chance of allowing a user activated audible alarm?

ronl wrote: For "Rubber-banded" waypoints the ability to rename them and save them as "User" waypoints would be nice. I know I can write down the Lat/Long shown for a RB waypoint and then use that to create a user waypoint but it could be a lot easier.

LarryPetro wrote: I  would like the boundaries of an airport's circling approach areas (Cat A - E)  to be depicted on the map when a specific approach procedure for that airport is entered into the Flight Plan.  The radii defining the circling approach area are determined by the both the approach category (i.e., airspeed) and MDA of the selected approach procedure.  Avidyne could depict all 5 areas, or, better, could give the pilot the option to specify the approach category.  The approach category could be set by a Setup User Option.

Paul wrote: As I understand it the IFD radios are actually software-defined.  Are there enough unused DSP cycles to create a receiver instance which simply monitors 121.5 and alerts if it detects a carrier?  This would work nicely with the new quick guard frequency selection feature.

I started a new thread:

http://forums.avidyne.com/forum_posts.asp?TID=1053&title=hours-and-minutes

And then thought that I could have just added it to this one.  Sorry for the duplicate.

David

I've got a new one.  I'd like to have a timer that will work off of fuel used and fuel remaining.  On the longer trips, I manage fuel this way:  

Geoffrey, yours was added the other day to the candidate list.

Peter, the best process is to send me crisp $100 bills to my home address. But when that doesn't happen, we have internal review sessions where we evaluate the candidate list and rack/stack them. It's usually my call where the line gets drawn. We have been toying with online voting efforts but that hasn't proven to be a viable approach yet.

Banana, Banana, Banana ...

Edited by oskrypuch - 01 May 2016 at 6:56pm

Put an audible alarm on the count down timer for tank switch. 

Here Ya go Steve...My request list will follow.  :) :)

I prefer the traffic representation on Foreflight, i.e. arrow with line extending to indicate relative speed, to the diamond that does not indicate direction, nor speed currently displayed on the IFD. Any chance to change to a Traffic Icon similar to Foreflight?

Appendix 2 of AC 20-172A specifies the symbol formats for traffic in certified ADS-B systems. I remember seeing a similar document that outlined the symbology for METARs (thus explaining why a cyan flag means "VFR" rather than a green one, as we see in Foreflight et al) but a quick search didn't turn that up.

I'm trying to understand why anyone would prefer a generic diamond to an arrow representation that implies direction of travel and relative speed at a glance. Orest infers that he prefers the diamond, and Avidyne Engineers also seems to prefer the diamond. Everyone referenced is smarter than I am.  What am I missing?

Nice to see that we have a female in the center of that hunk of paper currency!

Right.  This is not an Avidyne preference.  The original traffic we supported was pure TAS and we strictly adhered to the regs governing exactly how they were/are presented.

I likey!

Nice pictures, Steve!

The traffic symbology study I ran across was from Lincoln Labs, iirc.  (I know I saved it somewhere, but I can't currently find it.)   But I don't think it used the symbols on a map with relief or a sectional, which I suspect might have altered the outcome, at least wrt colors.

The results are the basis of AC20-172B.  And that, btw, does not include the velocity vectors on the traffic symbols, which I find *really* useful.   That deviation from AC20-172B will probably cost Avidyne some time with the FAA...

The open source app Avare uses the diamond symbols, but with the vector for directionality and velocity, the "Asteroids ship" symbol in AC20-172 becomes superfluous.

I would speculate that the diamond symbols of TAS (and I think TIS-A) were  selected because the directional information in the messaging was too coarse.