Dear Forum,

This is a mission I executed 7 times for several months. The only new thing I did was a firmware upgrade. The home point was updated, Over 15 satellites were active during takeoff an even more in flight. I tried running it even closer to the starting point but all the times I received the same error.

As a test I tried a different mission not too far away from the one I wanted and the same error appeared.

Any ideas, thoughs?

Thanks,

V

Possibly ring-fencing of a NFZ somewhere in the upgrade, which wasn't present in the older version?

Yeah, sounds like the geo fencing has updated

Blériot53 Posted at 9-5 14:48
Possibly ring-fencing of a NFZ somewhere in the upgrade, which wasn't present in the older version?

I was able to fly without any issues, no restricted areas. Nevertheless, I did self unlock just in case. Same routine with the exception of the waypoint error. But yes, I recall the famous database was also updated.

A J Posted at 9-5 23:17
Yeah, sounds like the geo fencing has updated

Very frustrating!

Vidjcb Posted at 9-6 17:20
Very frustrating!

TBH that is in the hands of your national aviation authority rather than DJI

A J Posted at 9-6 23:27
TBH that is in the hands of your national aviation authority rather than DJI

I found the solution. It was because after a firmware update, the maximum altitude is reset. The mission had a slightly higher one. I updated it in the mission and it worked perfectly.

A J Posted at 9-6 23:27
TBH that is in the hands of your national aviation authority rather than DJI

I found the solution. It was because after a firmware update, the maximum altitude is reset. The mission had a slightly higher one. I updated it in the mission and it worked perfectly.

A J Posted at 9-6 23:27
TBH that is in the hands of your national aviation authority rather than DJI

I found the solution. It was because after a firmware update, the maximum altitude is reset. The mission had a slightly higher one. I updated it in the mission and it worked perfectly.

Vidjcb Posted at 12-20 00:18
I found the solution. It was because after a firmware update, the maximum altitude is reset. The mission had a slightly higher one. I updated it in the mission and it worked perfectly.

noticed that the other day that the altitude, RTH and distance settings revert back to default after a FW update - glad you got it sorted.

A J Posted at 12-20 04:31
noticed that the other day that the altitude, RTH and distance settings revert back to default after a FW update - glad you got it sorted.

Well It also happened to me too before, but somehow all other times I had changed the limits before I run my mission.

Thanks for comment.

Cheers

VIDJCB

Vidjcb Posted at 2020-12-20 06:39
Well It also happened to me too before, but somehow all other times I had changed the limits before I run my mission.

Thanks for comment.

You're welcome