DJI Go 2.50 iOS is available today.
Do you see anything new for Phantom 3?
------------------------------Latest Summary---------
Lots of posts have been made on this topic, let me summarize (Jan 16, 2016)
1. All later App versions such as 2.42, 2.43, 2.50, 2.51 are infected with NFZs
It is claimed that Combination GO- 2.4.1, FW- 1.4.10 and RC- 1.4.30...works like a charm with no NFZs.
One of the iOS devices with App 2.4.0 also exhibited capability to fetch and display NFZs
2. NFZs are stored on a separate DJI's server. DJI go app has ability to fetch and display NFZs. We don't know when exactly was this capability added. Tests are showing that it was added some time around the release of 2.4.0
3. NFZ server is active since release of app version 2.5. Initially it was restricting flying even in the vicinity of helipads, hospitals etc but now it is showing only airports as NFZs this is a relief to all drone fliers
4. There have been multiple reports of unusual GPS behavior with app 2.5 release. Taking longer to get to SAFE TO FLY, dropping in and out of GPS when it was always stable before, less satellites than normal.
5. DJI has revised NFZ data on their servers. Red areas have shrunk in sizes, yellow areas are disappearing. This is a changing temp phase.
6. No difference so far found between 2.50 and 2.51. DJIs text for the fix is unclear.
7. RC stores last map with NFZs.
8. DJI app 2.5.1 crashes if NFZs servers have issues. Too risky to work with server based solution.
9. It may be advisable to keep your device in "airplane" mode when flying to avoid servers interference.
10. Many have flown successfully with 2.5.1 App, few are still stuck because of NFZs in their zones.
11. DJI Go App 2.5.1 is functionally ok to use. Do not fly in your NFZs.
I will summarize again when new facts emerge out.
Do you see anything new for Phantom 3?
------------------------------Latest Summary---------
Lots of posts have been made on this topic, let me summarize (Jan 16, 2016)
1. All later App versions such as 2.42, 2.43, 2.50, 2.51 are infected with NFZs
It is claimed that Combination GO- 2.4.1, FW- 1.4.10 and RC- 1.4.30...works like a charm with no NFZs.
One of the iOS devices with App 2.4.0 also exhibited capability to fetch and display NFZs
2. NFZs are stored on a separate DJI's server. DJI go app has ability to fetch and display NFZs. We don't know when exactly was this capability added. Tests are showing that it was added some time around the release of 2.4.0
3. NFZ server is active since release of app version 2.5. Initially it was restricting flying even in the vicinity of helipads, hospitals etc but now it is showing only airports as NFZs this is a relief to all drone fliers
4. There have been multiple reports of unusual GPS behavior with app 2.5 release. Taking longer to get to SAFE TO FLY, dropping in and out of GPS when it was always stable before, less satellites than normal.
5. DJI has revised NFZ data on their servers. Red areas have shrunk in sizes, yellow areas are disappearing. This is a changing temp phase.
6. No difference so far found between 2.50 and 2.51. DJIs text for the fix is unclear.
7. RC stores last map with NFZs.
8. DJI app 2.5.1 crashes if NFZs servers have issues. Too risky to work with server based solution.
9. It may be advisable to keep your device in "airplane" mode when flying to avoid servers interference.
10. Many have flown successfully with 2.5.1 App, few are still stuck because of NFZs in their zones.
11. DJI Go App 2.5.1 is functionally ok to use. Do not fly in your NFZs.
I will summarize again when new facts emerge out.
Last edited:
