DJI Air 2S P-GPS Error

Nick Skinner
I'm running into an issue with my Air 2S stopping in the middle of mapping missions and giving an error stating that the drone needs to stay in P-GPS mode. It seems to only error out once it is ~500ft away from the controllers position. The last time it errored out was a few weeks ago and at the time the drone was on the latest firmware and the dronelink app was the current version with the elite plan. I've been working within the constraints since then with no error.
0

Comments

5 comments

  • Comment author
    Mike (Arizona Wyldwest) Dronelink Expert Dronelink Expert

    Generally due to either the switch was changed from Normal speed mode during mission, temporary loss of signal even if brief or any of the other ones which is listed in the link below. A ton of other post regarding this question. The link below has a lot of other helpful articles for a whole slew of things. I’d bookmark the page so you can look through some of the other helpful tutorials and videos. DL has Great support. Good luck. 

    https://support.dronelink.com/hc/en-us/articles/360056104694-Why-do-I-see-Unable-to-Take-Control-or-Automatic-Control-Interrupted-during-missions-

    1
  • Comment author
    Barry Houldsworth Dronelink Expert Dronelink Expert

    The most likely scenario is (as Mike said) loss of signal, which would stop the mission.

    If you have flights logged in something like Airdata, you can go and view all of the error messages and warnings and that might give a clue as to why this is happening.

    0
  • Comment author
    stéphane GARNIER

    I never tested it but in case of loss of signal the drone is supposed to start rth procedure provided that the option has been set adequately.
    (Just to confirm that it is the root cause).

    0
  • Comment author
    Martin Reading Dronelink Expert Dronelink Expert

    I never tested it but in case of loss of signal the drone is supposed to start rth procedure provided that the option has been set adequately. 

    I can confirm that this does work

    0
  • Comment author
    Nick Skinner

    Thank you for pointing me in the right direction Mike. In my case it was the Max Distance setting in the firmware being set at 550ft, preventing it from traveling any further in automated flight. I set it higher and flew a couple mapping missions with no issues at all.

    0

Please sign in to leave a comment.