I have the latest firmware installed on my Drone, Remote and all 3 batteries. Firmware: Phantom 3 Advanced Firmware v1.11.20. Released on 2017-07-06. I can fly with no limits till battery is exhausted but after I change the battery and take off again I am limited to 30 meters in distance and height. I am aware of the need to log out and log in to the application and I did that after installing the new firmware. I have also uninstalled an re installed the application on my iphone but to no avail. I have even loged out and loged in during flight but again to no avail. Any ideas why I get still have limitation even though I did logged out and in after firmware update?

Do you actually have the limitation, or just the warning?

This is a begginer mode limit, strange...

allyssongemelli Posted at 2017-10-3 10:24
This is a begginer mode limit, strange...

DJI has input an altitude limit (and I think distance limit) with the latest firmware (or at least that is when I think it started.  Supposedly you have to register your product (mine was registered when  I bought it in 2016. I too have the same issue as it only goes to 100 Feet and you get an audible warning that you have reached the limit. Beginner mode is NOT activated on mine for over 18 months. Not sure of the work around as I just ran into after the upgrade.

ALABAMA Posted at 2017-10-3 08:30
Do you actually have the limitation, or just the warning?

Actual. Drone is "stuck" and will not proceed beyond limits.

fans268f4dd5 Posted at 2017-10-3 18:36
DJI has input an altitude limit (and I think distance limit) with the latest firmware (or at least that is when I think it started.  Supposedly you have to register your product (mine was registered when  I bought it in 2016. I too have the same issue as it only goes to 100 Feet and you get an audible warning that you have reached the limit. Beginner mode is NOT activated on mine for over 18 months. Not sure of the work around as I just ran into after the upgrade.

At least I am not alone.
Strange thing is that it happenes only after battery swap.

Planning to put the firmware on the sd card and replace batteries one after the other to see if any is (re)updated.

Please make sue the drone and APP both have been restarted after you changing the battery.

DJI Susan Posted at 2017-10-4 03:05
Please make sue the drone and APP both have been restarted after you changing the battery.

Thank you for your reply.

Is that a workaround or a normal operation?
18 months with my drone, pretty sure I never needed to do that before.

For whatever reason, this is happening a lot.  Just restart everything and you can fly.

Appreciate all for your efforts in helping. Guess this is the only way to workaround this.


In any way,
As planned I have copied the firmware bin file to the sd card and swapped batteries to see if any will update.
If you can identify any issue in the update log then would be happy to hear. If not, this thread can be closed.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.09.0060.bin
Upgrading ...
Result: Success.

========== 2016.06.25 11:17:47 =====================
Packet: P3S_FW_V01.09.0060.bin

========== 2016.06.25 11:18:22 =====================
Packet: P3S_FW_V01.09.0060.bin
Upgrading ...
Result: Success.

========== 2016.07.01 15:54:09 =====================
Packet: P3S_FW_V01.09.0060.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.10.0090.bin
Upgrading ...

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.10.0090.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.10.0090.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2017.08.12 12:18:06 =====================
Packet: P3S_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2017.08.12 12:39:47 =====================
Packet: P3S_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2017.08.12 12:40:34 =====================
Packet: P3S_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2017.08.12 12:42:58 =====================
Packet: P3S_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2017.08.16 06:32:19 =====================
Packet: P3S_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2017.08.26 12:19:42 =====================
Packet: P3S_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3S_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3S_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2017.10.04 14:27:28 =====================
Packet: P3S_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2017.10.04 14:29:34 =====================
Packet: P3S_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

After an update the settings are normally reset, so you may have to get out of beginner mode...

Antonio76 Posted at 2017-10-4 04:20
After an update the settings are normally reset, so you may have to get out of beginner mode...

Just to add to your comment. You should double check "ALL" of your settings in the app. Especially the RTH height. Glad you pointed this out to him. You can't assume that any of the settings are what they were before hand.

RicardoGray Posted at 2017-10-4 07:21
Just to add to your comment. You should double check "ALL" of your settings in the app. Especially the RTH height. Glad you pointed this out to him. You can't assume that any of the settings are what they were before hand.

Yes, you are right. ALL the settings should be checked after an update.

Ziv.ishshalom@g Posted at 2017-10-4 03:15
Thank you for your reply.

Is that a workaround or a normal operation?

Restriction of 30 meters high and 50 meters distance is a feature of new APP. Generally, the issue may appear if your DJI account was not write in the Main Control properly. Restart will figure it out.

Hello all!
I'm new here although I have my Phantom 3 Standard for almost 5 months.
As far as I know, I never flew higher then 30 m. I red I have to login on my App, so I did it. And it didn't help :/
When I'm around 30 m alt, I get messages  "signal lost" and then "return to home" beeping and blinking red.
Did I missed some adjustments or the antenna isn't working properly?
I also had an episode when I flew my drone 50 meters away and then tried to get higher then 30 meters. It went on 130 meters without me controlling it.
Finally, RTH drove it back to me.
Can anybody help me with advice?
Do I have to fly away so it can climb on a altitude I want?
I also couldn't take any photos on that height.
I don't fly "beginners mode". (although I feel like one)

Generally speaking directly above you is the worst place for the signal quality, you want the side of the antenna faceing the drone not the tip.

When you said the drone went on 130m was this height or distance, could it have gone to RTH height, what RTH altitude do you have set.

AlanHd Posted at 2017-10-11 08:51
Generally speaking directly above you is the worst place for the signal quality, you want the side of the antenna faceing the drone not the tip.

When you said the drone went on 130m was this height or distance, could it have gone to RTH height, what RTH altitude do you have set.

It was height.
Maybe you're right. But I was same as  it was before.

I have encountered this and it happens after updating IOS to V11, .1 and again with .2 - I deleted the app and reinstalled then refreshed the firmware which triggered the NFZ update again - works fine since.