Suggestions for 10.3

Develop IFD X40 display capability of TASA 1090-ADSB IN using UAT Format

Thanks.  It would be nice to be able to use the runway fix as the MDA waypoint and have the altitude and miles before options available as with other nonapproach waypoints.  I did get the banana by putting the MDA in the destination airport, so at least that is there.

Edited by AZ Flyer - 22 Sep 2018 at 8:25pm

oskrypuch wrote: - "Along Track" WPT, before or after a named waypoint, and set an Altitude or Level there. So if you are given "...to be level x miles before..." That has been available for a long time, just select the waypoint, and set so many miles before (after), and an altitude restraint. The additional waypoint, and VNav guidance will appear, together with the Boeing Banana when applicable. * Orest

I like #2 a lot too!

I most want improvements in VNAV handling - which is already a strength of the 540.

Edited by jhbehrens - 20 Sep 2018 at 6:41am

Edited by Bob H - 13 Sep 2018 at 7:43pm

Just flew after upgrading from 540 v10.2.0 to v10.2.2.0 and playing with the "Boeing Banana" - Way cool.

Add a Nearby VFR Waypoints category to the INFO tab data for an airfield, showing both name, id, coord, etc, with dct to capability just like the Nearby Navaids category. Or the VFR waypoints could just be added to the nearby navaids list.

I have another request.

I would like to second Oliver Bucher, I have exactly the same issue: Visual approach guidance (please also for user airfields, cause I am flying on a small glider airfield in Germany)

Secondly I would want to be able to calculate sunset/sunrise for those smaller user airfields / user waypoints as well, currently it does that only for database airports. Many thanks

And one more, this should be easy ...

OK, I'm a little out of control, but here is another one, from 2014.

Edited by oskrypuch - 20 Jul 2018 at 10:17pm

There there is this one, would really like to see this. This is from 2012!

Edited by oskrypuch - 20 Jul 2018 at 10:11pm

palmjet wrote: Here are some suggestions for features I'm presently missing: 1. A Present position Hold. 2. Oceanic waypoint entry. 3. Abeam Points

Here are some suggestions for features I'm presently missing:

1. A Present position Hold.

If you want to program a hold at the Present Position, this cannot be reasonably achieved. It does not happen often that this occurs, certainly not in the USA, but it does happen sometimes as I experienced.
Most bigger plane FMS's can do this.
First a Waypoint has to be defined at the Present Position after which it is possible to program a holding at that point. By the time you fill in the box with the holding data and then execute it, the aircraft will make a 180 back to the point where the waypoint was created.
The right procedure would be to provide an option "PPHOLD" after which a box should open to enter data (a standard hold as default), then after entering and verifying the data the holding waypoint can be created and executed immediately. This would be also great for orbiting.

2. Oceanic waypoint entry.

Kind of same problem here. When trying to enter for example N50W035 as a waypoint, the box comes back with "please enter a valid identifier or value", because after entering a few digits it cannot find something in the database. In an oceanic database there are nowadays preprogrammed waypoints like "H5250" (= N52.30W050), but if it is desired to enter the point N50W035, first a waypoint has to be defined, where after the coordinates can be entered and only then that waypoint can be used.
This is of course very time consuming in flight. On top of that the defined waypoint can have any given name and therefore has no direct indication for what it stands for.
The solution is to have it accept coordinates and then provide a software generated identifier, which must not collide with predefined waypoints, this in line with other FMS systems

3. Abeam Points

Suppose you are flying a flightplan with multiple points to a destination: a-b-c-d-e-f-g
Flying from "b" to "c" ATC clears direct to "f" so direct to "f" is entered and executed. The IFD then shows a direct line to "f", but the intermediate points "c" "d" and "e" are lost (they are still visible on the FMS page by scrolling back). What really is wanted by the pilot is a perpendicular projection of the previous waypoints on the now direct track to "f", with software generated points on that direct track with names like "Cxxxx" and "Dxxxx" where the x's stand for a distance from the original fix or another value. Now it's possible to follow the progress of the flight better with fuel consumption and time over waypoint. Suggest to program a "soft default" when entering a direct in the flight plan if there will be waypoints skipped, which says "ABM points?". If not touched or pressed, but the 'ENTR" button is pressed, then a direct without abeam points will be executed, otherwise the abeam points will show up after pressing "ENTR".

I am aware that these options are not so interesting for VFR use, but as these IFD's are so well designed they can and will be used for advanced operations.

Regards,

Andre

Jimmyz80, you could set the user preference that makes the tabs retract after, say, 5 seconds.

In the IFD wifi setup, change the names that indicate what wifi mode the IFD is programmed for.  

Suggestion:

Edited by DH82FLYER - 10 Jul 2018 at 10:01am

I only had IFD440 for a short while so these suggestions might already be in 10.2 if so please excuse my ignorance.

Please add a User Selectable FIRST Chart View to 10.3.  Right now, the ALL view comes up last requiring me to push the VIEW button 4 times, which is annoying.  Given the great slewing features of the 540, I'd prefer to see the whole chart (ALL) as the FIRST view that comes up so I can quickly  look at what I want to see, be it the minimums sections, or the profile, etc.  After the ALL view, then, you can rotate through the other options.  If this is user selectable, then everyone is happy.  

Traffic and obstacles look too similar on the map with the same blue colour and the same font for altitude. Close to airports they often overlap and I can’t see which is which.  Can the fonts be made thinner/smaller? Can the colours be made even slightly different?

I discovered this quick KB waypoint entry as well, quite by accident, and love it. Use it all the time.

oskrypuch wrote: I use the remote keyboard for 95% of my entries. I'm surprised more folks don't use it. I have it mounted on my yoke.