Note - this post is specific to the P3A and P3P, though some of it applies to P3S FW 1.9.20 as well.
With the release of FW v1.11.20, two things in particular need close attention. The need for Re-linking is expected to be common following this update, and this update introduces forced flight distance restrictions (height of 30M / distance of 50M) unless specific steps are followed.
If you don't remove the flight restrictions, it will feel as if you are stuck in beginner mode.
Re-linking
The release notes (
see below) this time specifically suggest
relinking if the RC and AC are disconnected post updating. It may not always be needed, but since DJI called it out ahead of time they clearly expect a disconnect will be relatively common. This has proven to be true since we have seen
many disconnects reported here on the forum even though the release notes
already suggest a fix.
Note: some have reported general connection and video issues which have also been corrected with relinking after this update. Some have also reported that relinking has helped after updating to the latest AC FW even when they
already had a green "linked" light on their RC.
To do a relink (some say rebind),
see the video below for the normal relink process. If you don't have access to the app, you can try the
manual relink process.
Flight Distance Restrictions
The release notes (see below) specifically mention the flight restrictions (height of 30M / distance of 50M) originally announced in May 2017. If you don't remove the restrictions, it will feel as if you are stuck in beginner mode.
Also introduced with this FW but not mentioned in the release notes (though also announced in May) is the
disabling of live streaming your FPV video to the internet.
Removing the forced flight restrictions:
The forced restrictions (Distance limits and Live Streaming) can be removed by following specific steps.
Once you have the RC and the AC updates installed (
instructions here), then open the app,
sign out and sign in again (while online) to "register" the app which will
remove the flight restrictions.
This is supposed to be a one time thing, so do it ahead of time before you go out to fly. Note however that many people have now reported the restrictions return even after registering the app. Watch for that so you're not surprised. Along with signing out and signing in, some have also had to delete and reinstall the app to remove the restrictions. Don't forget to
sync flight records before deleting the app or they will be lost. Once reinstalled, resync and your records will be back.
Note: The release notes call out specific app versions as well. Also, as always you should check your settings as some may revert to default during the FW update process.
Additional important notes:
If
only your app is updated but
not the FW, you should expect to see a 30m/50m flight restriction
warning. We have had several reports by people noting that they get a
warning about the limits, they are
not enforced and they fly
right through the warned distances without issue.
Here is an example of someone on FW 1.8, but gets the warning message.
Again, these are people who have updated only their app but not the FW.
Be sure to check your batteries to see if they need a FW update. Mismatches with batteries have been known to keep the flight restrictions in place. If your batteries have different FW versions, restrictions may be gone for one battery but back for another battery. Avoid doubt by checking all of your batteries before you’re surprised with flight restrictions at a job site!
Enough people had sudden
ESC Error issues with v1.11.20 that DJI created a
v1.11.30 which they have
not made widely available but
can be found rather easily if anyone cares to look for it.
Now it seems that DJI has been using v1.11.30 when refurbishing units and not letting buyers know about it, so if you buy a refurb it may come with v1.11.30 already installed.
Relink video:
Info about the new restrictions. It's not a Phantom, but the concepts are the same:
P3P release notes for 1.11. The P3A notes are the same:
Screen shot of the announcement in May: