Suggestions for 10.2.1.0

Now that software 10.2 is released, perhaps a thread on suggestions for the next minor software would be in order?

In my humble opinion this is one of the exciting aspects of the IFD100. Avidyne can use that app to play UI elements without having to go through the FAA. They can post all different UI ideas there like "Boeing Banana" and get real feedback from product users. The IFD100 being free to IFD customers is a brilliant move.

There is the IFD100 for flight and the IFD100 for research and development.

While there's nothing stopping Avidyne from creating a non-certified software app to run on tablets, I don't think that's the intent of the IFD100.  As ddgates mentioned, I'm pretty sure there's a common codebase between the IFD 440/540/100 with minimal exceptions.

Or maybe they could release the IFD100 first. Based on my experience as an iOS developer, it seems less and less likely that the app is still awaiting App Store release if it was truly submitted weeks ago. Even first-time approvals don't normally take that long. I hope there are no snags holding up release.

Awesome! I'm leaving on a flight to Tucson in about an hour - I will try it out

I would like to have an option make the 500' callout to say "500 feet, check gear down"    BH

Wookie, the 500' callout is per the TAWS specification.  I don't think they can change it.  But isn't the callout itself enough of a reminder to check your gear?

I too missed the datablocks in SVS mode, but I suspect the utility of the mode decreases as the view window decreases.  You keep the datablocks across the top, so perhaps some more options for that top block, and an ability to optionally setup the blocks differently for the SVS screen.

Another nice feature would be to update panel IFD's navdata from the IFD100 via wifi. That would allow updating the IFD100 at home with fast internet and be an alternative to using USB.

chflyer wrote: It would really be nice if two IFD's could sync databases, especially navdata. Would save a lot of issues reported here with loading Jepp updates into 2x boxes. Sounds like Garmin GTN nav boxes can now do this, but not sure.

 Alternative to Jeppeson.  (hint:  Seattle)   $1K / year for updates is Crazy. 

Did someone say something about Seattle Avionics?

- Datablocks on the SVS (long press on the map rocker could hide/show the datablock just like the MAP page does now)

Include DA or minimums on FMS.

DavidBunin wrote: I have my Destination ETA as one of my top datablocks, and I have noticed that in 10.2 the AM or PM value is riding over top of the time value.  Can this be fixed in 10.2.1?

A suggestion for the exocentric SVS page would be to have the distance rings around the aircraft.  Its possible to scroll in and out but without distance rings, it is not possible to know how far the indicated traffic or obstacles are as far as I can tell.

Very helpful. I did not realize that

Rather than call out arbitrary heights, how about calling out the MAP itself?

I would really like the ability to import an ICAO format flight plan (via an IFD100 if need be) into a format flyable by the IFD. I dare say other EU/IFPS region operators would like this too
e.g. parse in
(FPL-N2125K-IG
-M20T/L
-SYBDGR/ESB1
-HEGN0825
-N0182F200 HGD V608 AST UP751 KATAB B12 DBA M872 PLH/N0169F110 M872 KFN N732 RIPID
-LGKR0617 LGIR LYTV
-CODE/A1C401 DOF/170512  TOW:1528 TOC:D77F200T0032 TOD:D778F200T0423 BOD:D816F110T0435 TOD:D1066F110T0604 BOD:D1069F110T0605 TOD:D1069F110T0605 DAL:D1103ADLGKR TAXI:5 RVR/550 PBN/A1B2C2D2O2S1
-E/0904 P/002 R/VE J/L D/01 004 C YELLOW A/WHITE AND BLACK)
and strip out the irrelevant stuff (CODE/RVR etc) but process the origin, route, climbs, descents and destination.

Another wish would be to use/publish a standard for "User defined" charts, which would be used when either Jepp doesn't provide one but it is loaded and made available from another source (eg Skydemon uses the AIP charts and manages to geo-reference them) or when there is no Jepp sub for the area

- When you hit the FREQ button after being on the MAP page, MAP tab, when you hit the MAP button to go back to the MAP page/tab you left off from, it swipes the tab left or right depending on what side of the rocker you hit, but it won't go back to where you left off.  It would be nice to default to going back to where you left off.

Ah, I see what is going on.  The data for the airports may be as you stated, current position on first press and then destination on second, but the map view is based on the FPL tab view setting.  So although you may get the correct data, if you have the FPL view set to CURSOR, the map jumps to the cursor so unless your cursor is near your current position, you won't see any airports highlighted when you hit the NRST button.  I still suggest having the MAP view default to your current position when you hit the NRST button (and to your destination when you hit it a second time) so that the highlighted airports are visible on the map.

As an update to the above request for RF leg support, I've seen a quote from Garmin indicating that RF legs are supported with Software 6.0 (I assume this is for GTN boxes, but that wasn't mentioned).

chflyer wrote: Since 10.2.1.0 is now out, perhaps time to take the items on this list that didn't make it and start a new one. Before doing that, perhaps one of the new Avidyne team members can comment on the status of my pet peeve, being RF leg support. See previous posts above for the discussion. In a first instance, it would be nice to have an explanation from Steve of why this is a big deal. The IFD540 AFM indicates that RNAV 1 is supported, and I seem to recall that the issues getting New Zealand RNAV 1 approaches into the navdata were resolved. There are a number of approaches and departures in Europe that require RF but are NOT AR. A couple examples are Zurich LSZH VEBIT1K RWY 34 RNAV 1 SID and Strasbourg LFST RNAV(GNSS) RWY 05 neither of which are in the IFD540 navdata. I have more. And as mentioned, apparently the GTN's do support this.