There are a thousand ways to screw up and I stumbled upon one yesterday. Fortunately I avoided any kind of a problem but it could have been bad. The RTH feature has worked flawlessly for me many times but this time I discovered a way it could trap my MP in limbo indefinitely (I think). Here is what happened:
1) I flew a few hundred feet away in an open field and decided to RTH (no emergency, I just wanted to return to home quickly and with little effort on my part). I initiated the RTH.
2) My MP spun around and ascended to the 80M (260 feet or so) my RTH height was set to. It was now facing west into the sun at 5pm.
3) It moved toward home for 5-10 ft and then stopped as if it had hit a wall. It then backed up 15 feet and ascended 20 ft.
4) It then repeated # 3) above until it was 20 feet or so further away and at a height of 380 ft.
5) I hit the pause button and flew it home.
6) I immediately relaunched the MP and tried it again and the same exact thing happened upon initiating a RTH...lurch forward...step back...ascend...repeat...repeat...repeat.
7) I hit pause, flew it home, turned it off, restarted, and tried it again...this time the RTH worked flawlessly.
At this point I had no idea what the issue was and was uneasily writing it off as a glitch. I slept on it and this morning it came to me after reviewing the flight log...my final and successful RTH was with the MP facing south while the first two problematic RTH's were facing west into the setting sun. It was no glitch but rather the MP reacting to a perceived obstacle as the "RTH Obstacle Check" mode is supposed to. How long it would have carried on like this, I don't know but I can imagine a scenario where the MP really needs to come home (lost signal plus low battery) and it can't because it is trying to return into the sun and the RTH Obstacle Check algorithm won't let it.
The RTH Obstacle Check can be turned off in the advanced settings section of the Visual Navigation Settings menu. Mine will be off from now on and assuming I have my RTH height set appropriately I should have no problem.
If I'm wrong on this one someone let me know. I tried uploading a phone video of the flight path log but it was too big but it shows just what I described above.
1) I flew a few hundred feet away in an open field and decided to RTH (no emergency, I just wanted to return to home quickly and with little effort on my part). I initiated the RTH.
2) My MP spun around and ascended to the 80M (260 feet or so) my RTH height was set to. It was now facing west into the sun at 5pm.
3) It moved toward home for 5-10 ft and then stopped as if it had hit a wall. It then backed up 15 feet and ascended 20 ft.
4) It then repeated # 3) above until it was 20 feet or so further away and at a height of 380 ft.
5) I hit the pause button and flew it home.
6) I immediately relaunched the MP and tried it again and the same exact thing happened upon initiating a RTH...lurch forward...step back...ascend...repeat...repeat...repeat.
7) I hit pause, flew it home, turned it off, restarted, and tried it again...this time the RTH worked flawlessly.
At this point I had no idea what the issue was and was uneasily writing it off as a glitch. I slept on it and this morning it came to me after reviewing the flight log...my final and successful RTH was with the MP facing south while the first two problematic RTH's were facing west into the setting sun. It was no glitch but rather the MP reacting to a perceived obstacle as the "RTH Obstacle Check" mode is supposed to. How long it would have carried on like this, I don't know but I can imagine a scenario where the MP really needs to come home (lost signal plus low battery) and it can't because it is trying to return into the sun and the RTH Obstacle Check algorithm won't let it.
The RTH Obstacle Check can be turned off in the advanced settings section of the Visual Navigation Settings menu. Mine will be off from now on and assuming I have my RTH height set appropriately I should have no problem.
If I'm wrong on this one someone let me know. I tried uploading a phone video of the flight path log but it was too big but it shows just what I described above.