I second this problem. The Wiki has no correlation to reality in Mission Planner!
Discussion is ongoing at the following link as well.
Really no response? Someone in another thread has already crashed their plane as a result of this.
Does anyone from 3drobotics monitor these forums?
There's an obvious bug in APM.
I've been looking at code and I cannot see how it would handle two LAND commands. It seems to work that you set the landing coordinates and altitude where you want to land, and when the plane is within 3m Alt or 2 secs to this location it cuts throttle and makes sure the plane does not roll. The pitch is held positive if you have no airspeed sensor.
When you say:
It seems to work that you set the landing coordinates and altitude where you want to land, and when the plane is within 3m Alt or 2 secs to this location it cuts throttle and makes sure the plane does not roll
You mean, get manual flight node control, and just land the aricraft?
I have APM2, and I haven't airspeed sensor, yet.
I reaaly intended to try autoland and auto takeofff, but it seems not work properly, at moment.
Cheers from Brazil and thanks for any help!
I'm not sure what mode changes happen, I couldn't see any. I would guess you would be in the same mode, just the target land location is close to the ground and throttle is 0%. You will land shortly after, with a glide. With an airspeed sensor it would just help to avoid a stall, but it's not far to drop.
I will try set in autoland a sequence of WP decreasing altitude to ground. I let you know how it works.
Autoland with Arduplane - has anyone got any definitive instructions, as the wiki mentions two waypoints, but this point blank doesn't work - the MissionpPlanner doesn't even have the labelled boxes to enter the values.
2 land commands, it doesn't make any sense, has anyone actually got it to work?
I was able to successfully auto land several times yesterday. My setup is SkySurfer with APM 2.5, firmware 2.72, airspeed sensor, MediaTek GPS, Mission Planner 1.2.48. The mission planner waypoint setup I am using is much the same as used for Arducopter.
Here is what I did...
Setup a waypoint that is aligned with the runway and 200 meters out from touchdown.
Change the altitude of this waypoint to about 10 meters (relative).
(Make sure this altitude will clear obstructions on final approach. If this altitude is too low, you might hit an obstruction. If it is too high, the plane will not be able to descend fast enough. 200m/10m gives about a 3 degree descent angle.)
Make another waypoint 30 meters or so past the beginning of the runway.
Change the altitude on the runway waypoint to 0.
While the last waypoint is highlighted, click "add below".
Change the new blank waypoint entry command field to "land"
(The "land" command line will have zero's in the LAT, LONG and ALT fields)
I have been adding another waypoint, after the land command, that is at the end of the runway to possibly help with staying on the runway, although I believe it may not help.
Here is a video of autoland on a gusty day at a different airfield.
More testing today revealed that any waypoint after the land command appears to be ignored.
When the land command reduces the throttle to idle, the SkySurfer pitches up slightly and then back down for the landing. I had better luck descending a little more steeply. This reduces the amount of power applied on final approach and the pitch up.
I made a dozen successful autolandings today with 10mph winds. It looks to be pretty reliable now.