P3S - Maybe a paperweight?

[amrth]

Hi All – Been following this forum since long, just got a chance to post up my P3S problem..


Long story short – The drone crashed, the battery popped out and the gimbal base plate broke.. No body damage, I opened the body to inspect if anything was broken inside and as far as I could tell, everything seems to be in place.. Finally got some time over this weekend to put back everything together and now I’m have these below issues

1. Downloaded the latest DJI app and it connects to the RC wifi
   1. The Video feed from the camera is showing up in my android, but the status of the drone shows disconnected
2. Red, Green & Yellow lights blink on the drone
   1. Link button on the drone is green
3. Tried Re-linking the Drone to RC, multiple attempts and it just times out both through the app, as well as manual .. In manual mode its just keeps beeping till I turn it off
4. The app at once showed firmware upgrade needed and I was able to download it through the app and when I went on to install it the error showed up as device disconnected
5. Tried upgrading through the Memory card mode, the first time it started upgrading for few mins and then it failed, the gimbal light became constant red with a continuous Beep
   1. Tried this multiple times, with mmc reload, flash and just by removing the .txt file.. nothing seems to work..

Need some advice to revive my drone, what should I do next?

 

[Fly Dawg]

Tried this multiple times, with mmc reload, flash and just by removing the .txt file

What .txt file are you referring to? The firmware file should be .bin.......

 

[amrth]

What .txt file are you referring to? The firmware file should be .bin.......

The .txt file that gets created when P3 identifies the bin file and starts installing it from MMC..

 

[Fly Dawg]

And what does the install log .txt file tell you? It should tell you any installation or hardware errors.

 

[amrth]

The first text showed exactly like this....

Packet: P3S_FW_V01.09.0200.bin

Upgrading ...

Result: Success.

========== 2014.01.01 00:00:12 remo-con disconnect======

Packet: P3S_FW_V01.09.0200.bin

Upgrading ...

Result: Failed.

Reboot the aircraft and try to upgrade the firmware again.


-----------------------------------------------------------------------------------------------------------------
Subsequent logs shows this

Packet: P3S_FW_V01.09.0200.bin

Upgrading ...

Result: Failed.

Reboot the aircraft and try to upgrade the firmware again.

 

[Oso]

I'm curious about something. Please don't be offended. We just want to help you and other readers.

Your P3S was working fine, but a crash caused some damage. Before you had it working well as it was prior to the crash, you introduced new troubleshooting variables with FW changes and a new app. That seems counterintuitive to me. To help others in the future, what led to that decision?

As for your logs. From reading the forum, have you seen how to access your hidden LOG_AB text file? If so, would you mind also posting that file?

 

[Fly Dawg]

Before you had it back to working well as it was prior to the crash, you introduced new troubleshooting variables with FW changes and a new app.

I was going to mention that myself.......BTW

 

[Fly Dawg]

The log file posted is not the detailed one, as @Oso mentioned.

 

[amrth]

I'm curious about something. Please don't be offended. We just want to help you and other readers.

You're P3S was working fine, but a crash caused some damage. Before you had it working well as it was prior to the crash, you introduced new troubleshooting variables with FW changes and a new app. That seems counterintuitive to me. To help others in the future, what led to that decision?

As for your logs. From reading the forum, have you seen how to access your hidden LOG_AB text file? If so, would you mind also posting that file?

No sir I wouldn't be offended at all..

The crash happened in October 17, after that I just took the drone and put it back in the box .. We moved and also I changed my handset from iPhone to a driod.. So 10 days ago I looked up to get the drone to fly and this is where I am now ..

I'm not understanding when you say "introduced new troubleshooting variables with FW changes.. Can you please let me know what are you asking me about in specific?

No I don't know how to access the LOG_AB text file.. If you could guide me to it I shall post it as soon as I get home today...

Very little knowledge on this.. So please pardon the ignorance

 

[amrth]

The log file posted is not the detailed one, as @Oso mentioned.

I copied a couple of texts and then deleted those text files.. I can redo the steps today evening and capture the log and post it up here..

Something in my head was telling me I shouldn't delete the text file.. Should have listened and stored it separate.. Really hope it's in the trash on my mac..

 

[Fly Dawg]

I'm not understanding when you say "introduced new troubleshooting variables with FW changes.. Can you please let me know what are you asking me about in specific?

I can answer that question. When you have an issue of any kind, you should never change anything that would add to the troubleshooting steps. If everything were the same when last flown, primarily speaking of firmware in this case, it could be easier to locate your issue. You introduced a new issue by changing the firmware. Now, it could be firmware related as well as hardware related. That's what @Oso was referring to.

 

[amrth]

I can answer that question. When you have an issue of any kind, you should never change anything that would add to the troubleshooting steps. If everything were the same when last flown, primarily speaking of firmware in this case, it could be easier to locate your issue. You introduced a new issue by changing the firmware. Now, it could be firmware related as well as hardware related. That's what @Oso was referring to.

oh I got it.. Thanks.. Actually my intentions was not to do that. Since the dji app showed it need a firmware upgrade I followed that path.. Wrong move as usual!!

I was just trying to re link the RC to drone and ended up thinking the app might be right on firmware upgrade to link it back..

 

[Fly Dawg]

Just for info, your install log should look something like this: ( Note: This is only a clip from a log)

[00011942]========== remo-con disconnect. boot(15) ============
[00012059]Packet [C:\P3S_FW_V01.11.0020.bin] detected, card sn [0x20b80b96].
[00012095]Packet upgrade start...

[00012132]Packet checking...
[00012162]Packet vlink 01.11.0020 <-> 01.11.0020.
[00012224]Done.

[00012261]Version checking[1]...
[00012340][03 06][00] v2.1.6.18 -> v2.4.20.50 need upgrade.
[00012423][03 05][00] v34.2.0.8 -> v34.2.0.9 need upgrade.
[00012464][04 00][00] v1.44.0.0 -> v1.48.0.0 need upgrade.
[00012778][11 00][00] v1.8.0.0 -> v1.8.0.0
[00012898][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00012937][11 01][00] v1.8.0.0 -> v2.0.0.33
[00013031][12 00][00] v1.8.0.0 -> v1.12.0.0 need upgrade.
[00013107][12 01][00] v1.8.0.0 -> v1.12.0.0 need upgrade.
[00013207][12 02][00] v1.8.0.0 -> v1.12.0.0 need upgrade.
[00013281][12 03][00] v1.8.0.0 -> v1.12.0.0 need upgrade.
[00017813][15 00][00] v1.1.2.0 -> v1.1.2.0
[00017886][17 00][00] v1.1.1.7 -> v1.1.1.7
[00018006][17 01][00] v1.0.2.7 -> v1.0.2.7
[00018058][19 00][00] v255.255.255.254 -> v1.0.8.96
[00018087][01 00][00] v1.23.4920 -> v1.25.5432 need upgrade
[00018133][01 01][00] v1.23.4920 -> v1.25.5432 need upgrade
[00018177][09 00][00] v3.0.0.10 -> v4.1.0.0 need upgrade.

 

[Fly Dawg]

Sorry for the color change......my typo......

 

[amrth]

Sorry for the color change......my typo......

Ha ha.. That's dint alert me much.. This is the same .txt file that you are referring to which would be in the memory card once I get the bin file in there and start the installation process?

Reason I ask is as far as I remember the texts in the file wasn't as you posted .. Surely will look it back up tonight

 

[Fly Dawg]

The AB.txt file is hidden in the "Misc" directory of the card, if I am not mistaken.

 

[RodPad]

My thoughts, if his remote is green, the Phantom status link light is green, he is already linked.
He should beable to start the motors, try it without props.

He has one channel, the video is making it back to the remote and mobile, he is missing the second channel or the (telemetry) that is sent on the second channel which is giving him a link error.
If his remote wasn't already linked from the past, he would never get what he has now, meaning if he tries another remote, he would never get live video or green lights, and be able to start the motors.

When the link fails, both the Phantom and the Remote are returning to the last configuration.

Rod

 

[amrth]

My thoughts, if his remote is green, the Phantom status link light is green, he is already linked.

Hi Rod - The remote isn't green.. you mean the light next to the power button right? That's red..
The link led on the drone is green..

 

[RodPad]

Hum, yes.
Link led on the Phantom is green, does it go red when you power off the remote?

Rod

 

[amrth]

Hum, yes.
Link led on the Phantom is green, does it go red when you power off the remote?

Rod

I did not make that observation, I shall do that tonight and post back a reply.. anything other indications that I should be looking out for?