From the docs, my understanding is that if I specify Lat=Lon=0 for LOITER_TO_ALT, the plane should start orbiting where it is. But it seems that Mission Planner wants to send me to the actual 0N0W in the middle of the East Atlantic. Is it a display issue or am I misunderstanding the documentation?
Begin loiter at the specified Latitude and Longitude. If Lat=Lon=0, then loiter at the current position.
It is just a display anomaly in MP, the plane will loiter at the actual coordinates.
Thank you, @Eosbandi
what version of MP are you using
Here’s the same flight plan, zoomed out to show version 1.3.74.
Here’s the mission file:
QGC WPL 110
0 1 0 16 0 0 0 0 33.227554 -96.953411 173.160000 1
1 0 3 31 0.00000000 30.00000000 0.00000000 0.00000000 33.22679680 -96.95166350 100.000000 1
2 0 3 16 0.00000000 0.00000000 0.00000000 0.00000000 33.22906740 -96.95166350 100.000000 1
3 0 3 31 0.00000000 30.00000000 0.00000000 0.00000000 0.00000000 0.00000000 150.000000 1
4 0 3 16 0.00000000 0.00000000 0.00000000 0.00000000 33.22669810 -96.95142750 150.000000 1
5 0 3 31 0.00000000 30.00000000 0.00000000 0.00000000 0.00000000 0.00000000 100.000000 1
6 0 3 17 0.00000000 0.00000000 -30.00000000 0.00000000 33.22793660 -96.95194240 100.000000 1
There’s another place where this apparently happens. When I go to review a log from this flight[1], I get a map that includes 0N0W:
[1]https://github.com/arikrupnik/ardupilot-config/blob/master/logs/FIXED_WING/2/2020-12-25%2011-29-19.speed-runs-change-speed-questions.bin?raw=true
its already fixed in beta MP. i might need to do a new release soon
