Implementing VNAV support in FlightGear: Difference between revisions

Jump to navigation Jump to search
Line 26: Line 26:


== 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   
{{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.
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   
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.
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
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?
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   
This is also tied up with accurate enroute time calculations and  calculating top-of-climb / top-of-descent information, it's quite a   

Navigation menu