Implement the F_TAKEOFF flag

[GoogleCodeExporter]

Setting this flag on the first waypoint will have the following effect:

Navigation is disabled for this waypoint leg.  The plane will remain in 
stabilized mode until a 
configurable number of seconds has passed.  A timer will start when the 
throttle value rises above 0.  
When the timer hits the configured duration, we will move on to the next 
waypoint which will then 
perform navigation.

This will allow cleaner autonomous takeoffs.

Original issue reported on code.google.com by benjie on 20 Apr 2010 at 11:23

[GoogleCodeExporter]

Original comment by benjie on 20 Apr 2010 at 11:28

• Added labels: Type-Enhancement
• Removed labels: Type-Task

[GoogleCodeExporter]

I'm not sure about the thinking on this one. I would think that we do want 
navigation (to 'track' the plane 
towards the end of the runway). The feature I would want (and lamented about in 
Boulder) is to force 
navigation durring takeoff to be only with the rudder (you don't want the plane 
to start banking too early).

Ideally, the goal for this waypoint would be altitude, but since we don't have 
the best altitude accuracy yet, I 
agree a timer is probably the safest. Either that, or a combination of timer or 
position (for example, I set the 
waypoint to the far end of my flying field along the line that is my runway; if 
the plane reaches that point 
before the set timer, then it starts to navigate -- I've run out of field).

Perhaps this should be discussed on the group list? I'm not sure that we've 
thought it out enough.

Original comment by adam.bar...@gmail.com on 22 Apr 2010 at 12:03

[GoogleCodeExporter]

Maybe we should hold off on this one, and just make sure that the future flight 
language can do this for us.  :)

Original comment by benjie on 22 Apr 2010 at 5:37

• Removed labels: Milestone-Release2.5

[GoogleCodeExporter]

We're now using Bill's takeoff method instead.

Original comment by benjie on 30 Oct 2010 at 8:22

• Changed state: WontFix