@evranch wrote:
I just updated to 3.9.6 yesterday.
I was attempting a survey pattern over my farm with Arduplane today, when suddenly my plane cut throttle and began gliding for the ground. A couple panicked slaps at the switches later, and I was back in FBWA and pulled out. I switched to LOITER which worked fine for a round. I then attempted AUTO again to no avail and decided to land.
Upon recovering the logs, this appears to be the problem - POS.Alt snapped from relative to absolute GPS altitude, totally ignoring the baro. What happened? In fact, why is POS.Alt somewhere between GPS and baro altitude? I’ve been flying with Arduplane for years and have never seen this kind of altitude mishap.
The site says the logs are too large to upload, so here’s a screenshot of the event.
Posts: 4
Participants: 2