Gap in route
Printed From: Avidyne
Category: Avidyne General
Forum Name: IFD 5 Series & IFD 4 Series Touch Screen GPS/NAV/COM
Forum Description: Topics on Avidyne's IFD 5 Series and IFD 4 Series Touch Screen GPS/NAV/COM
URL: http://forums.avidyne.com/forum_posts.asp?TID=2362
Printed Date: 19 Apr 2024 at 9:11pm
Software Version: Web Wiz Forums 12.01 - http://www.webwizforums.com
Topic: Gap in route
Posted By: frankbell
Subject: Gap in route
Date Posted: 10 May 2022 at 7:57am
| What is the design logic for “gap in route”? Why not just assume that you’ll want to go direct from the point prior to the “gap” to the next point (which is what you’d almost always want to do)? Seems like it’s just an extra step to have to eliminate the gap. |
Replies:
Posted By: AviSteve
Date Posted: 10 May 2022 at 8:50am
|
You hit the nail on the head when you said "almost always". The FMS doesn't want to assume a path. It wants the pilot to define that. There may be an obstacle or terrain that would conflict with a direct leg. It's best just to involve the pilot to make sure it's OK to go direct. ------------- Steve Lindsley Avidyne Engineering |
Posted By: frankbell
Date Posted: 10 May 2022 at 1:25pm
|
I do understand that making assumptions can be dangerous, but it seems to me that adding button pushes to an otherwise simple operation (i.e. adding waypoints to a route) is a step backwards. I don’t think any other box (i.e. the “G” boxes) do that… my 530 didn’t, and never caused a problem. Not a big issue, just a small irritant.
|
Posted By: oskrypuch
Date Posted: 10 May 2022 at 9:55pm
Personally, I see that as one of many failings of the UI on G* stuff. Give it some time, and you may agree. Logical GAPs in a flight strip are a standard feature in any FMS. * Orest
|
frankbell wrote: