Owne / ardupilot-mega

Automatically exported from code.google.com/p/ardupilot-mega
0 stars 0 forks source link

Auto-landing #330

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.In APM 2.0x Planner Mavlink does not accept NAV_LAND_OPTIONS command
2.In APM 1.0x Planner accepts CMD_LAND_OPTIONS 

What is the expected output? What do you see instead?
the following secquence does not produce the espected result:
{CMD_LAND,0, 0.00, 44.48664760, 25.96348271},
{CMD_LAND_OPTIONS,  150, 7.00, 20.00, -3.00},
{CMD_LAND_OPTIONS,  100, 7.00, 10.00,  0.00},
{CMD_LAND_OPTIONS,   50, 7.00, 0.00,  3.00},
in hilsim the plane overshoots the point in CMD_LAND (same behaviour in real 
flight), second CMD_LAND_OPTIONS command is executed immediately after the 
first one, before reaching the distance to waypoint

What version of the product are you using? On what operating system?

APM1.02/APM2.012/Windows 7 x64
Please provide any additional information below.

Original issue reported on code.google.com by parv...@gmail.com on 27 Apr 2011 at 10:54

GoogleCodeExporter commented 8 years ago
NAV_LAND_OPTIONS has been deprecated and is not supported in APM 2.X.  

We have been successfully flying auto landings using the supported command set. 
 You can substitute other commands for NAV_LAND_OPTIONS.

Original comment by dewei...@gmail.com on 30 Apr 2011 at 8:23