sanity check for nav_wp_safe_distance should be only performed when activating the WP Mission, not when arming #4832
when more than 650m (max value allowed) away from my 1st WP, I'm unable to arm, not sure if this is desirable behaviour because I may even decide not to fly the mission, and I want to be able to arm.
sanity check for nav_wp_safe_distance should be only performed when activating the WP Mission, meaning once in the air, then and only then when I flip my switch to activate the WP Mission should the sanity check be performed and simply not execute the mission if my model is more than nav_wp_safe_distance away from 1st WP
allow to arm the model regardless of the 1st WP distance from the launch site, because it is not necessary to do the sanity/safety check unless the pilot decides to activate the mission once in the air. pilot may even decide not to activate the mission.
I also suggest to increase the maximum allowed value for nav_wp_safe_distance, currently 650m is way too restrictive and I found myself in situation where I could not arm and I could not relocate closer because the terrain did not allow me to.
Who does this impact? Who is this for?
for pilots flying in unknown terrain, unknown location, for example in remote desert area. in these locations the mission planning is difficult because there is no internet. I plan the missions days ahead with no final knowledge of the terrain and not knowing local conditions, sometimes I find myself only 1km away from my intended launch site but I cannot get there due to terrain restriction, in this case I cannot arm my model.
there is no sanity check (restriction) when creating 2nd WP, it can be many kilometers away from 1st WP, so why is there such a severe restriction on 1st WP ?
when I forget to load my mission from EEPROM before arming and then try to execute mission once in the air, nothing happens because I'm trying to execute invalid mission.
sometimes I want to fly manual as far as I can (while I'm LOS) and only once entering a terrain where I know I would lose video and radio link (for example when entering canyon) I would like to switch to WP Mission only then (ie. assuming my 1st WP is at the entry of the canyon), but then my 1st WP might be several kilometres away from my actual launch site, under this scenario I wouldn't be even able to arm the model because my 1st WP is too far away.
normally I want to fly model as far as I can in manual mode because still as a pilot I want to have the joy of controlling the plane and also I can get more usable footage out of manually controlled flight, but then once I reach a point in terrain where I know I would lose my video and radio link I would still be happy for the model to continue autonomous mission.
I've been now travelling for 4 weeks in deserts and remote locations around Australia and came across many situations where this requested feature is desirable. for example on my recent flight where I planned to fly through a canyon in autonomous flight and I had to launch and land outside of the national park but the canyon entry was 1.5km away - normally I would've preferred to fly first part of the flight manually and activate WP Mission only at the entry to the canyon, video of the terrain and situation below, incl. the loss of video and radio signal for reference to also show that WP Mission in iNav 2.2 works pretty well even when there is failsafe :