I was wondering if anyone had seen a similar behavior with the Air2S and the RC Controller (1).
A couple of weeks ago I was flying around a deforested area with my Air2S, it was a pretty clear day if a tiny bit breezy. I had flown in this area a week prior with no problems and was generally capturing some footage of the forestry management of the area.
I had been flying for about 10 minutes and decided to return to home and land while I decided where to fly to next (in the same area). The drone was at about 150ft when it arrived above me. I tried to command the drone to start descending, but it just hovered in place. I tried a number of times and still it did nothing.
Believing that it might be some kind of signal interference I tested moving off a short distance and then coming back to nearly the same position. The drones ability to do this was unaffected and it successfully maneuvered as requested. So I started to try and descend again. At first, the drone started to comply and it did indeed descend, but only by about 20 ft, were it stopped and refused to descend any further. I found that by leaving it for a moment and then trying another descent command it would again descend only to stop and hover in place.
Using the command, wait, command approach I finally got the drone to land successfully. There was no sign of anything untoward. The sensors were clean, there was no sign of damage. The RC Controller had maintained about 24 satellites throughout and there had been no drop in signal.
I decided to pack up and move to another of my favorite locations for some (very cautious) testing. All the height and maneuverability tests at the alternative location were fine and there was no repeat of the original problem with descending.
When I got home I uploaded the logs to AirData but that showed nothing but strong signals and sensor reading and there was no sign of a problem according to the logs.
I was just wondering if anyone else recognized this behavior?