Wishlist for the next IFD software release

Both good ideas.  Just entered them in the candidate database.  Thanks.

That really depends on what you are flying and where you are flying... If you are flying turbine aircraft fuel planning is pretty critical as you aren't generally tankering fuel as you can with a piston. So, for range flights, knowing your fuel at each waypoint is critical to in flight decision making. 

brou0040 wrote: DavidBunin wrote: brou0040 wrote: the screens shouldnt assume that they are hiding. I'll go out on a limb and guess that it is an unavoidable side-affect of the 540 and 440 sharing the same software.  On the 440 I think it is safe to assume that owners will hide the tabs.  You would really need the screen real estate on that unit. I can't believe this, these units should be smart enough to know "if tabs hidden, have scroll set to xxx, if tabs not hidden, set scroll to yyy."

Edited by brou0040 - 18 Jul 2015 at 11:05am

AviJake wrote: comancheguy wrote: Thanks for the reply.   I'll try to get into that habit.   However, ideally,  the box shouldn't throw away what I was doing and start over.  I agree that's a neat feature and a "Recent" access method for that is in our future feature candidate database.

brou0040 wrote: the screens shouldnt assume that they are hiding.

I'll go out on a limb and guess that it is an unavoidable side-affect of the 540 and 440 sharing the same software.  On the 440 I think it is safe to assume that owners will hide the tabs.  You would really need the screen real estate on that unit.

comancheguy wrote: I want my FP or route to stay in the box across a power cycle.   I land someplace and power up to depart and I have to start all over.  If the Flight plan was still in the route, I could just reverse it.   Ken

+1

comancheguy wrote: My wish list: 1) PCL - click issue resolution. I just posted this issue today, so...  I can't complain (yet)...   2)  XM weather - Nexrad - animate the weather.    You can do this on the 496 (Can't recall on the 530).  Ken

1.  We're on it.  Replied on that same thread.

2.  Looping weather radar is on the to-do list but pretty far down it.   Can't do on a 530 and Garmin just announced today that a Q3 upgrade to the 750 will support it.

My wish list:

I want my FP or route to stay in the box across a power cycle.  

brou0040 wrote: it is assuming the tabs would be hidden and the XXX is hidden behind them.

I have found this to be true of most of the screens/views since 10.1.0.0.  I see it on the GPS Status screen where the SV numbers are hidden behind the tabs, and on the Map view where the radar age or other items that reside across the bottom are hidden behind the tabs.

I decided that the tab hiding isn't optional (I don't have it set to "never").  I haven't decided on what delay time I want for it yet, but you get used to hiding them pretty quickly.  I'll probably end up with one of the shorter hiding intervals.

David

brou0040 wrote: I see there is a decoded VLOC IDENT datablock that shows the ID, radial, and distance, but I was wondering if the distance could be shown in the footer of the VOR frequency box.  Right now the left hand shows the identifier and the right hand shows a blue box with ID in white writing the VOR is identified.  There is plenty of room in the middle to put the distance to the VOR.  Seems like it would be a convenient way to add more info to the display without having to add datablocks.

+1

I see there is a decoded VLOC IDENT datablock that shows the ID, radial, and distance, but I was wondering if the distance could be shown in the footer of the VOR frequency box.  Right now the left hand shows the identifier and the right hand shows a blue box with ID in white writing the VOR is identified.  There is plenty of room in the middle to put the distance to the VOR.  Seems like it would be a convenient way to add more info to the display without having to add datablocks.

Agree -

The simple iPad apps have extended center lines.

David

Would it be possible to add more detail to the FSS frequencies when you hit the FREQ button?  Around here, a lot of the FSS radios are RCOs and you just dial up the freq.  That's been working pretty well using the FREQ key until it gave me one that was based off a VOR.  There was nothing indicating I needed to be listening on a VOR freq to hear back.  Guess I should have looked at the map sooner.

Orest,
Do you have any idea what the conditions were or why the TOD may not have displayed properly.  I've seen it a few times but can't seem to duplicate it at will.  BTW, as of now the TOD does NOT display at the actual spot where descent should begin but rather at the fix the spot is associated with. ie if descent were to begin 20 miles BEFORE XYZ, then the TOD descent shows at XYZ now.  That will change in 10.1

I know there will be a change to TOD in 10.1 to show the marking at the actual spot rather than the fix the spot is associated with.  Has anyone seen, up to now, a situation where the TOD does not display or give the CAS message?  I cannot associate it with any event yet, but there are times, I will put in a crossing altitude at a fix on my plan, and no TOD appears and no CAS message ever appears. It happened today when I put in a crossing altitude below my cruise altitude at a fix further in my plan.  I was not yet past the point where the TOD should have been so I was confused as to why it never appeared.

My two key requests relate to IFR operations.
1: Today's IFR arrivals are getting longer and longer. Very frequently I enter somewhere along the arrival path and then have a number of useless waypoints upstream cluttering my interface. On my Garmin 530 I could highlight the not wanted waypoints and delete them. Not so on the IFD 540! This is a real pain, especially when getting a new arrival procedure due to a runway change that shares common arrival waypoints.
If Garmin can do it I am sure Avidyne can too.

2: When entering an ILS approach the frequency stays in the standby location until near the FAF. It is especially painful when cleared for VTF from an intermediate approach waypoint that is not in line with the final approach course.
To get to straight ILS mode takes a lot of acrobatics at the wrong time when single pilot in icing and lots of traffic.
Again, not an issue with the Garmin 530.
Please fix these shortcomings!

I have no interest in fuel to waypoint information.

Fuel remaining at destination is the most desirable bit of information. When that figure drops below my desired minimum level I make adjustments. Range can often be extended by simply slowing down (indicated airspeed).

If one is doing a maximum range flight in IMC they should have appropriate reserves for an alternate. BTDT.

I agree with reducing information clutter.

Not so sure.

Most of the time, perhaps, but not always. When weather is bad and fuel is becoming an issue, having fuel handy at various wpts would help with decision-making and save grey cells for other work.

I would tend to rather think that this should stay once the scrollable data block arrives.

Another alternative might be to have a user option of fuel in wpt blocks yes/no.

Good naturedly, some of us have traffic on the IFD.

Through all the bizz mumble, don't forget the dedicated traffic page!   Doesn't matter where you are if you run into someone.   BH

ptlevine wrote: VSR with a little reminder of what it is referencing: I have VSR as data block on the top of my maps screen. It would be nice to have the VSR show with the identifier it is referencing. When you have a lot of crossing restrictions, it is nice to know exactly what this is keying off such as:  VSR (WHITE): -1,200 VSR (KHPN): -800

Royski wrote: ... but also to include a datablock showing estimated time to TOD and then advised altitude at the current time.  As I've mentioned here before, it's one feature I miss from my KLN-94 GPS.

Edited by oskrypuch - 06 May 2015 at 10:26am

The VNAV feature relies on the default descent rate in the AUX section.  Would be nice to be able to change that descent rate from the VNAV input on the FMS screen.

I agree 100% Direct to should not return to the FMS+ page.  Lots of extra button pushes and doesn't add any value that I can see.