funemnx

I can confirm that TheMalkavien's suggested changes to the variant.h for rp2040 lora resolved this issue. Thanks!

I have a similar inav 8.0.1 issue with a fast fixed wing. Thought at first it was due to poor altitude fix with gps so switched to using the barometer...

I see navTgtPos[2] only sets to the requested 50m altitude after the crash. Before that the values just drop. I will attach the blackbox log and the diff all showing...

The 50m I referred to was incorrect. That was the RTH altitude. I had actually set an above ground height of between 50 and 100m for the WPs and the...

Perhaps I should try something like this to eliminate the sea level reference and see how I go: # Mission Control Waypoints [wp] #wp 4 valid wp 0 1 457914670...

_"WP missions use a linear climb/descent between waypoints so the target altitude is the incrementing altitude required to achieve the linear flight path rather than just the altitude at the...

I am attaching another blackbox flight where I switched off the WP mission before it went the same way of the previous one. Another rapid drop!!! [LOG00003.TXT](https://github.com/user-attachments/files/22805473/LOG00003.TXT)

GPS interference? And yet there were plenty of satellites. I did swap out the GPS for a new one (HGLRC m100 pro) after this happened in previous attempts.

Stronnag, You might want to map the log3.txt to that waypoint mission. I think after the first failure I may (though memory fails) have modified the mission. Any other data...

Just finished another 2 test flights. This time using relative altitude. The first (log11) was crazy! GPS interference galore. Shortly after the start WP mission, 0 satellites and emergency landing...