My top 3:

1) Remote TXP support (even if it just the normal Trig/Avidyne that can be remotely controlled, just allows the TXP to be out of immediate reach)

2) MLX770 support. Especially as the touch screen will really make the messaging function useful!

3) Best EX600/5000 integration

Vince

 

FIS-B data

A FIX page, being able to direct the IFD540 to draw on the moving map, user specified circles and radials, relative to given waypoints. For example one could direct the IFD540 to draw a 10nm and 20nm circle, with a radial matching the expected LOC, around your destination. Outstanding for quick orientation.

* Orest

 

Tony,

There are two different kinds of predictions. One is predictive based on aircraft performance parameters and supplied wind data, would be used to calculate a full VNAV path, and is typically used in a full FMS to predict a full climb/descent profile. Cool, but probably not practical.

The other is just a simple dynamic calculation based on your current rate of climb/descent (with perhaps a bit of buffering), that paints where you will reach the altitude, that is specified in the next defined altitude constraint. That is the Boeing Banana, and works much the same in the Boeings, as I would like to see implemented in the IFD540. It is available in the R9 gear, and from what I understand implementing this in the IFD540 would not be difficult.

* Orest

* Orest

Remote Transponder driven by IFD (like the GTN 750 does).  A headless Trig TT22 would work admirably.

Dynon supports this with their SkyView system.

Routes:

1) Can you consider softening the Barber pole (alternating 50% length magenta/ 50% white) depiction of the next leg? To me at a glance it suggests that the Barber pole is the active, not the straight magenta. I might suggest making the next leg depiction Barber pole 90% white and only 10% magenta length stripes.

2) Can you allow wind entry at waypoints, and have it assist ETE calculations? Punching in the forecast wind vectors along the route as an option, at the expected altitudes would be cool. That( might be a bit beyond what you'll do, but I throw it in just for fun.

* Orest

There were two checklist ideas I thought of that I mentioned there but figured I should capture here.

First, I think it would be nice to be able to configure checklist triggers.  For example, I could create a GAMPS checklist (I have A/C that has to be off for takeoff/landing and fixed gear so my GUMPS is GAMPS) that would trigger within 3 miles of the destination descending through 1000 feet AGL where the range and altitude could be configurable.  Ideally I could have a list of and/or triggers where I could use range or time and or altitude and or ground speed etc.  This may sound complicated, but you could use a similar interface to the vertical guidance or holding where you say cross 2.0 nm before XYX at or above xxxx 2 min legs and you can configure each of the fields.  When you meet the criteria for a triggered checklist, it could give you a pop up warning in the lower right similar to SUA alarts.

Second, I didn't find an easy way to reset the checklists inflight without having to uncheck each item.  An example would be flying multiple practice approaches.  I don't want to clear each checklist item so that I can go through my approach and pre-landing checklists prior to each approach.  I don't remember the functionality at this time, but maybe holding the clr button when selecting a checklist when not in the edit mode would clear it and holding the clr at the top level clears all checklists.  Either that or any time you go back into a completed checklist, it automatically clears it.

I had assumed that the IFD would have the same degree of support for the Connected Pilot as the Garmin 530 does, since this is a slide-in replacement product.  I'm quite unhappy that it does not, as this support was a factor when I chose the IFD over the KSN-770.  I am optimistic that this support will be forthcoming.

Here are the highest-priority Connected Pilot features that I would want to see:

* Orest

* Orest

If there was a universal standard that would allow boxes to share their flight plan data, and I could update one device and push that to the other two, that sure would be neat.

Regardless of how easy the data input is, 1x vs. 3x is an improvement.

Depending on the GPS and portable units, you can generally setup crossfill. This not only saves a ton of time, but also will add the approach waypoints into the portable units, normally you will only get FAF inwards if you add a procedure.

I have a GNS that crossfills to a 796. The 540 will do the same thing. The flightplan populates onto the EHSI of the ASPEN automatically as well.

To me, the benefit of Connected panel might be to overcome the need to enter a flight plan twice, but even more so to make up for the antiquated and non-airway-smart flight plan entry of the GNS units. That will largely disappear as an issue, once the 540 is installed.

Perhaps Avidyne will come up with something like Connected Panel, to allow non-panel mount instruments to interface.

* Orest

Gring: I agree that the 770's UI is not up to the standard of the 540.  I found it a bit cluttered and hard to interpret, although I think they've made some improvements.  

I also agree that the 540's method for entering data is vastly superior to the 530's, and probably to the iPad, and you do have a good point about amended clearances for IFR.  However, not all flights are IFR, and some flights certainly are cleared as filed.  There's a lot to be said for being able to sit inside (perhaps at home) in peace and quiet and plan out the flight, then upload that straight to the panel.  It eliminates a potential source for error.

With GPS data sent to the iPad, you essentially gain an additional MFD that you can configure as you wish.  Perhaps the iPad's screen is more suitable for displaying a chart with the airplane's position depicted, for example, while you use the IFD to look at traffic or terrain.

And being able to nominate frequencies from an app on the iPad just makes things that much nicer when you're looking something up in the A/FD, etc.

Orest notes that Avidyne may come up with their own Connected Panel-like solution.  That's certainly possible, and might even be a good idea.  I'd be completely in favor of their doing that if they also support Connected Panel.  Otherwise, the problem you may end up with there is a sort of Balkanization, where the Avidyne is able to supply some information over its connectivity, but other devices might still only work on Connected Panel. (JPI is an announced partner for Connected Panel, for example, so you could get up to date fuel information to your flight planning app on the iPad.)   So if some devices support Avidyne and others support Connected Panel, then how do you make that work?  Switch back and forth between the two?  Use one on Wi-Fi and one on Bluetooth?  Better to have all the information available through one connection to the iPad.

In closing, I just want to reiterate that I think the IFD has the best interface out there, with the possible exception of the full R9.  I flew a G1000 this morning, and I was struck by how much I prefer Avidyne's approach.  But I think that there is a lot to offer on the iPad, and being able to smoothly exchange data between the two worlds is a feature that I really look forward to.

As to Connected Panel, it only supports Ipads at the moment, so it is a non-starter for me and many others. It needs support for the now more widely used android devices. CP also requires a 2 unit (PFD+MFD) ASPEN setup, so that reduces the number of candidate installs as well.

If Avidyne came up with some sort of direct connection, by wifi preferably, with support for android (and iOS), it could feed all the other panel devices, and would be a better and more general solution. 

* Orest

Second, while Connected Panel is a good idea I suspect it won't last long in practice.  That's because it requires an Aspen MFD (won't work with just their PFD) and is already somewhat obsolete.  As Orest suggests, Avidyne probably will be better off incorporating some form of wifi connection to handheld and other panel devices.

Mike

Agree, be able to rubberband the active leg.  The IFD should be able to add a current location waypoint and rubberband from there.

Regards,

Bob

Do you want to go missed?

YES (or do nothing for 10 seconds)

NO

Also, "go missed" should always be a button available after FAF

Thanks for pointing out the other conversation. I had skimmed over it, as it didn't really register before I started playing with the sim. I continue to think that this is an important issue, and I would like to see some capability for enabling the missed approach after the missed approach point, or perhaps a user setup selection to always enable the missed approach. If you are assigned a route other than the published missed approach procedure, I can't see that having the published procedure loaded causes any problems for setting up to fly whatever clearance you are given.

Regards,

Bob

The Heads Up unit in the Citation has the audio items recorded into it by Heads Up, it costs to change the checklists, etc.  For a unit like the IFD series, I would think a user could record their own checklist audio.

Anyway, probably a pipe dream, but can't hurt to mention it. :)

I agree that the 540 is IFR-centric, and FPL entry so much easier than with the Garmin that the feature is not really necessary for that.

However, I also fly VFR and I'm not holding my breath waiting for Avidyne to add the hundreds of VRP (VFR Reporting Points) that are associated with VFR approach/departure to/from airports here in Europe, especially since Jepp is involved. I've spent many many many hours just entering these into the Garmin as user WPT in preparation for trips... and need to be careful that they haven't changed since last entered. I have VFR flight planning software (PocketFMS) that includes all these VRP in the db and on the map (and most others do too). It would be really useful if I could transfer flight plans created with this software to the 540.

2) A FIX menu function -- custom pilot specified radials and circles, shown on the display, around pilot specified waypoints, 

WX500 strike test

Application for editing checklists on a PC (and Mac!)

Too many features can be as vexing a problem as too few, but I think in what you outlined, it takes a basketful of features and makes them one.

Good suggestion.

I will provide some background behind this request, as there may be a better way of accomplishing my goal. We were navigating on a victor airway that was in the IFD540 flight plan. Ahead of us in the flight plan were several intersections, followed by the next VOR. Due to a radar outage, we were asked to report x miles from that VOR, but the VOR was neither the next waypoint (due to all of the intervening intersections) nor the destination, so the distance to it did not display in one of the datablocks. I tried the Nearest VOR function, which brought up a nice list of VORs, but the distance did not seem to be updating. At that point, I dialed up the desired VOR as a second waypoint in our old Trimble GPS, which has the ability to display information from a second selected waypoint in addition to the next waypoint in the flight plan, but it would be nice to be able to accomplish this task with the 540 only. 

I tried replicating this scenario in the iPad simulator, and the distances for VORs displayed using the Nearest function seemed to be updated about every 20 seconds, which is a little slow for giving a precise position report. I suggest that the update rate be increased, or perhaps someone can enlighten me about an alternative way to easily display distance information for a waypoint that is not the destination or the next waypoint in the flight plan.

Regards,

Bob Siegfried, II

You can configure a datablock to display the VOR, Distace, Radial to the tuned and identified VOR in the NAV radio.  That would have given you the information you requested, updated real time.  Another way is to use the range rings on the MFD to estimate distance which should be accurate enough for ATC position reporting (remember time/speed/distance calcuations?).  A third way, although not an IFD, could be a two finger tap in Foreflight to measure the distance from your position to the VOR on the sectional.

In addition to push/twist capability and north up 240 arc view, it would be nice to be able to "direct to" a map pop-up box.  More specifically, I'd like to be able to pan the map around and select airports getting the pop-up boxes, then be able to hit the direct to button from there and have it populate the direct to menu with the pop-up box location.  I understand I can rubberband to an airport, but I may be looking at the weather at multiple airports before I find the one I like.  I'd like to be able to hit direct to instead of going back to add it to the flight plan or rubberbanding the route.  This would also allow me to divert for weather or airspace easier.  I could press a point I want to fly to and hit direct to, which would also avoid the issue of modifying the active leg.

Hi Geoffrey-

Thanks for the reminder about the VOR datablock. That is obviously the best solution for the situation I described, as long as the VOR is transmitting. I have found the feature in the Trimble to display information for an arbitrarily selected waypoint (outside of the flight plan) very useful at times, and it would be nice if the more advanced sets had a similar capability. However, I can see why such a capability may not blend well with the FMS architecture of the newer units.

I have been very impressed flying the IFD540 in my Dad's plane. I find it much easier to use than either of the simulators. It is amazing how well those lower right knobs work for entering data. 

Regards,

Bob

Could you also add an ability to go to the FULL info page on a pop-up item?

Also, you could get it from the info page, but being able to quick-load the NAV freq for a VOR from a pop-up page would be nice.

* Orest

... with the METAR broken off screen?

* Orest

Intelligently formating it would be a bit of work, but even just a line-break for space substitution after so many characters would help.

In any case, there are far more important things to work on, but please leave it on the list.

* Orest

Avidyne has identified this already and we have the change coming in R10.1.

I'd like to be able to create a waypoint from the map not rubber banding and not the present position.  I think ideal way to do this would be to touch the screen and have an option to be able to create a waypoint at that location.  There are a lot of waypoints I'd like to create for mountain passes or weaving through restricted airspace where I'd like to create permanent waypoints, but I don't really know a rad/bearing or lat/long.

Also, it would be nice to NOT HAVE fuel on each waypoint datablock.  I'd like to know my fuel remaining at my destination long my route, but I don't need to know it at the current waypoint or the next waypoint.  That seems to be more fuel information than I need and it takes up screen space.  That may not be a big issue with the upcoming ability to scroll datablocks, but I think it would be nice to free up those lines to have more datablocks on the screen at once.

2: When searching for an airport, allow to search by the identifier.  I'd rather dial in IYK instead of INYOKERN although I realize it does find it if I type INYO, but it seems like there could be other better examples.  I bet there are a lot of Madison's, but only one MSN.

I really miss this on the main page.  Putting it in the data blocks would solve this.

I like your suggesting of switching at 9:59, that gives more time with seconds resolved.  I seem to miss the few second countdown timers and having a seconds counter would be much easier to anticipate.

Just entered it into the future feature database.

Also, a dedicated screen for traffic and strikes would still be nice but I want to try removing all the LAND and clutter from the Map view to see how close that comes to giving me a similar view.  It's probably good enough for now.  

Discovered this was missing the other day, you need to add it.

* Orest

I use often Direct to re-center the CDI after a deviation while VFR when my exact course doesn't matter, to avoid a pointless excursion back to the old course. Using the direct button requires the expected button presses but further (1) undesirably sequences the FMS to the next waypoint (so that the default direct-to waypoint is no longer the current waypoint but the one after) and  (2) undesirably leaves it in FMS/map mode instead of the map mode.  I'd rather these didn't happen.

More than that, what you really want is to have a TOD "point" as a data block but right in the flight plan strip logically placed where it occurs! This is a common FMS feature.

Of course the item would not be editable (or perhaps the planned VSR could be set here), but would list all the other factors, time, distance etc. I requested that some time ago, don't know if it was ever logged as a request.

http://forums.avidyne.com/forum_posts.asp?TID=481&PID=6921&#6921

*Orest

VSR (KHPN): -800

+1

* Orest