Issues with Controller not connecting to P3P

Joined
Dec 18, 2016
Messages
13
Reaction score
1
Age
74
I am having a major issue that I can not figure out with my controller not connecting to my P3P. Both controller and drone are at 1.10.0090 FW. Connecting my Apple Mini Air2 via USB on back of controller and using the lightning connector to connect to Air2. After powering all devices on, I get a solid green light on Controller as well as what appears to be connection to drone. I am able to rotate the gimbal using the controller gimbal but I am not able to get a connection to the drone thus no camera view. I am not able to arm the drone (props removed). Nothing but gimball appears to work.. I have removed and re-installed the DJI Go app on my tablet, but when I bring up the app, it indicates that it is not connected and steps me back thru how to enable my connection. This is driving me crazy. Anybody else have any experience with this issue. All was working previously, but I installed HDMI module (correctly) and then this started. After re-checking all connections, I have come to the conclusion I received a bad HDMI module from Amazon. Removed the HDMI module, re-installed the original USB module, and am still not able to connect via the GO app. HELP!!
 
K. Batteries fully charged. Air2 connected to controller via usb/lightning, controller power on, drone powered on, dji go app launched, immediately comes up with screen to select what my drone is (P3P), never goes to connect, only show how to connect over and over. Can't re-link as this has to be done from the Go app. Is there anyway to re-link drone to controller other than thru the GO app?
 
I get a solid green light on Controller as well as what appears to be connection to drone.

Is there anyway to re-link drone to controller other than thru the GO app?
As you noted, you do already have the solid green light which indicates a connection. If you still want to try a manual binding anyway, here is how:

P3-Adv controller usb problem

or check out the video, but skip the first minute:

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
  • Like
Reactions: JoBe
hi yes i have had a similar problem the usb board was not compatible with my RC and fried something inside.i could still fly it but no cam or telemetry.so i bought another P3A and am using that remote now all is fine .i cant say 4 sure that what ur experiencing is what happened to me.if u know someone with a remote try that see if it will bind and u have cam then u will know if it is the RC or the p3.good luck .
 
Thanks. Did use special process to re-link rc. Yet, still no connection. Bind process went exactly as expected, but still no connection. Can't fall back from 1.10.0090 FW without being able to connect to drone with GO App. Spoke to Dronenerds yesterday and guess I will have to send unit in for them to figure out what is wrong. All this because I wanted to install HDMI module to use FPV with my Headplays!
 
Can't fall back from 1.10.0090 FW without being able to connect to drone with GO App.
Why do you think you need the app to downgrade your AC? Is that something new?
 
yes, if you have 1.10.0090 FW on drone you cannot fall back on FW without using the GO app. If this is not true, can anyone tell me how I can fall back from 1.10.0090 FW?
 
Last edited:
  • Like
Reactions: JoBe
Oso, tried this process and successfully downgraded with no problems to 1.8.0080. Then tried to downgrade to 1.7.0060 and got this:
========== 2014.01.01 00:02:44 remo-con disconnect======
Packet: P3X_FW_V01.11.0010.bin
Upgrading ...
Result: Success.

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

========== 2017.05.16 14:25:19 =====================
Packet: P3X_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.05.16 14:28:05 =====================
Packet: P3X_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.05.16 14:31:46 =====================
Packet: P3X_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.05.16 14:39:38 =====================
Packet: P3X_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.05.16 19:28:53 =====================
Packet: P3X_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.05.16 20:03:34 =====================
Packet: P3X_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.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_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.05.17 05:12:22 =====================
Packet: P3X_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.05.18 19:58:13 =====================
Packet: P3X_FW_V01.09.0060.bin
Upgrading ...

========== 2017.05.18 20:43:43 =====================
Packet: P3X_FW_V01.08.0080.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:14 remo-con disconnect======
Packet: P3X_FW_V01.07.0060.bin
Upgrading ...

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.07.0060.bin
Upgrading ...


Looks like it did not downgrade to 1.7.0060. Also now my RC firmware I think is at 1.6 (not really sure as can't get DJI GO app to tell me anything as it indicates not connected) and after trying to downgrade AC to 1.7.0060, now am unable to Link RC to AC using the manual Link process. IS this to be expected since I read in your post that RC FW 1.6 is only compatible with AC FW 1.8 or newer. I have tried to do the RC FW Manual method described in your post and when I hold down the tutorial button, I get a message that controller is not connected and does not offer any downgrades for it to download. Man, I have never had so much problems with FW. Prior to trying to downgrade AC FW to 1.7.0060, I was at least linking to the AC as both AC and RC lights were solid green and I was able to at least move the camera gimbal. But now, am not able to make the camera move at all as it now is not linked. I am almost ready to just send this thing in for repair. Thanks to all for trying. I really appreciate all the effort, but think I am at my wits end.
 
Had the same problem had to turn off quad and controller and restart 2 times before it would connect and not sure why by worked fine no problems
 
Oso, tried this process and successfully downgraded with no problems to 1.8.0080. Then tried to downgrade to 1.7.0060 and got this:
========== 2014.01.01 00:02:44 remo-con disconnect======
Packet: P3X_FW_V01.11.0010.bin
Upgrading ...
Result: Success.

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

========== 2017.05.16 14:25:19 =====================
Packet: P3X_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.05.16 14:28:05 =====================
Packet: P3X_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.05.16 14:31:46 =====================
Packet: P3X_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.05.16 14:39:38 =====================
Packet: P3X_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.05.16 19:28:53 =====================
Packet: P3X_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.05.16 20:03:34 =====================
Packet: P3X_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.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_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.05.17 05:12:22 =====================
Packet: P3X_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.05.18 19:58:13 =====================
Packet: P3X_FW_V01.09.0060.bin
Upgrading ...

========== 2017.05.18 20:43:43 =====================
Packet: P3X_FW_V01.08.0080.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:14 remo-con disconnect======
Packet: P3X_FW_V01.07.0060.bin
Upgrading ...

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.07.0060.bin
Upgrading ...


Looks like it did not downgrade to 1.7.0060. Also now my RC firmware I think is at 1.6 (not really sure as can't get DJI GO app to tell me anything as it indicates not connected) and after trying to downgrade AC to 1.7.0060, now am unable to Link RC to AC using the manual Link process. IS this to be expected since I read in your post that RC FW 1.6 is only compatible with AC FW 1.8 or newer. I have tried to do the RC FW Manual method described in your post and when I hold down the tutorial button, I get a message that controller is not connected and does not offer any downgrades for it to download. Man, I have never had so much problems with FW. Prior to trying to downgrade AC FW to 1.7.0060, I was at least linking to the AC as both AC and RC lights were solid green and I was able to at least move the camera gimbal. But now, am not able to make the camera move at all as it now is not linked. I am almost ready to just send this thing in for repair. Thanks to all for trying. I really appreciate all the effort, but think I am at my wits end.
Wow, I'm so surprised that you just kept going down in FW versions when all you said earlier was that you wanted to go down from 1.10. Not sure why you didn't stop when you got to 1.9. Anyway, if you do have 1.6 on your RC then you may have now created an encryption mismatch if some of the modules went below 1.8 on your AC. All I can suggest is to try to install 1.8 or 1.9 on your AC so that it has the same encryption as your RC and then link them again. As noted, that's assuming you do have 1.6 or higher on your RC as you were speculating.
 
Thanks Oso. Guess I mis-understood the post. Thought I needed to go all the way back. My Bad! Now trying to reload back to 1.8.0080. At least my RC was still connecting (somewhat) before going down to 1.7.0060. Hopefully I can get back at least to that level. If not, definetly going to send it in. Thanks again for all your assistance. Will let you know results.
 
Of course, "unofficial" also means at your own risk but it does sound relatively easy to get to 1.9.

tried this process and successfully downgraded with no problems to 1.8.0080.

Aside from the fact that you continued downward, was it easy to get to 1.9 and 1.8? I mean did you just follow the instructions and all was good?
 
JoBe, yes it worked as expected. Text file shows that AC downgraded successfully. Went back up on AC to 1.8. Re-linked RC to AC and now am able to move gimbal again, but still no camera view as GO app still says no connection. I am giving up on this and packing up to send in for repair. Thanks to all for trying to help. Will let you know what repair techs find with this as soon as I know. Once I was back at 1.8 on AC I went back and changed USB module to new HDMI module. No Joy. SO not sure what went on with this, but the 99.00 HDMI module now seems to be a very expensive mod. SJould have been simple, but turned out to be my worst nightmare. Should have just left P3P alone.
 
  • Like
Reactions: JoBe

Recent Posts

Members online

Forum statistics

Threads
143,066
Messages
1,467,352
Members
104,933
Latest member
mactechnic