Implementing VNAV support in FlightGear: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 25: Line 25:


== Background ==
== Background ==
{{cquote|Altitude constraints are a mess - in the short term, they are best avoided. Keep in mind the GPS code doesn't really do proper vertical 
navigation - it computes some data like the altitude change and climb/ descent rate for a leg, but I'm not sure if any real aircraft is 
driving the VNAV mode of an autopilot from it.
It's definitely something I will look at, but it's tied up with some  other features. At some point I want to support GPS precision 
approaches and then obviously all the VNAV logic will need to be  properly cleaned up - right now it's been copied mostly unchanged from 
the original gps code.
As always, user stories are good - what do you expect the behaviour to  be from the route-manager? Just to track valid altitudes? For the 
autopilot VNAV to follow the altitude profile exactly? Something in  between?
This is also tied up with accurate enroute time calculations and  calculating top-of-climb / top-of-descent information, it's quite a 
mess to unpick.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg23986.html
|title=New route manager?
|author=James Turner |date= Thu, 08 Oct 2009 15:17:18 -0700}}</ref>|James Turner}}
{{cquote| I don't think any aircraft AP supports vertical route navigation yet - and the route-manage itself only has partial support for editing waypoint altitude. There's no real obstacle - waypoints store an altitude (and speed), and the AP can read it, but nobody spent time making it work yet. Vertical modes (VNAV) also tend to depend more on fuel/load and engine performance data from the FMS, which is an area that's been lacking in FlightGear,  
{{cquote| I don't think any aircraft AP supports vertical route navigation yet - and the route-manage itself only has partial support for editing waypoint altitude. There's no real obstacle - waypoints store an altitude (and speed), and the AP can read it, but nobody spent time making it work yet. Vertical modes (VNAV) also tend to depend more on fuel/load and engine performance data from the FMS, which is an area that's been lacking in FlightGear,  
so hard to model the climb and descent profiles meaningfully. <ref>{{cite web |url=http://forum.flightgear.org/viewtopic.php?f=40&t=13777&hilit=performance+vnav#p140230  
so hard to model the climb and descent profiles meaningfully. <ref>{{cite web |url=http://forum.flightgear.org/viewtopic.php?f=40&t=13777&hilit=performance+vnav#p140230  

Navigation menu