Drone-Lab
Drone-Lab
Thank you for your advice. > it is checked again before the mission is executed and a geofence violation is caught at that time (though you don't have immediate feedback...
> but then you should reflect this evaluation in the mission result uorb topic as its done here https://github.com/Drone-Lab/PX4-Autopilot/blob/5490f8913bd26ac04d59908271ce9c5e6a1bd414/src/modules/navigator/mission_base.cpp#L702-L707 such that it is not run again by the mission feasibility...
> So with your approach you would now get the warning in QGC but you could execute the mission and it would fly out of the geofence, if i'm understanding...
If you are interested in "the mission always before the geofence," you can obtain more details here. ### Details 1. When the ground control station upload mission or geofence to...
Alternatively, add a check after successful upload?
what's the further plans? making geofence sync read and adding locks or semaphores?
I agree with your opinion. Do you need me to further modify the pull request according to this requirement?