Good day,

I haven't notice that My IPad updated to the latest 3.00 version. So Obviously, when I connected the Ipad to the remote, I believe that it updated the remote accordingly. ( correct my If I am wrong ).

I tried to fly the bird without any issue for the first minute or so, after this short period, the drone started a descent on a not so friendly area and one prop hit a branch. Of course, you know the outcome.  Fortunately it landed on tall grass. not destroying anything.

The first message I did get, was '' No signal'' even though i was seeing everything BEFORE.

Once I got home, I tried to update the drone the first time but, as I did read somewhere, I did not wait enough and when I repowered the drone, I got LOUD BEEP. So I restarted the update process but ever since this event, The gimball seems to react to a glitch. There is a '' NO SIGAL '' on the ipad display. I paired the remote with the drone successefully but still no signal. When I connect the USB wire to the gimball OR the drone, there is NO indication ( no drive added to the PC ) as it was before the update.

H E L P !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Hello Dompie, please help clarify the aircraft model, please.
On the "Aircraft Status" page of DJI GO APP, any error message shows up?
Have you tried to format the SD card and upgrade it again? during the upgrading, what is the status of the LED on gimbal?

DJI Natalia Posted at 2016-10-11 00:24
Hello Dompie, please help clarify the aircraft model, please.
On the "Aircraft Status" page of DJI G ...

The aircraftmodel is an Phantom 3 Pro with the HDMI interface. I use a 32Go SD card that was formatted previous to the update. The firmware that I use comes from DJI site.

The LED on the gimball start well for the upgrade but after about 1 minute, it stops the '' beep beep.......beep beep,,,,,'' process and it turns to red.

The status says '' No signal ''.   On the Global status, there is a red triangle that says Firmware requires upgrade '' and it also tells me that the upgrade failled.

The text file says the same thing even though I tried it more than 5 times so far.

Dompie Posted at 2016-10-11 12:54
The aircraftmodel is an Phantom 3 Pro with the HDMI interface. I use a 32Go SD card that was format ...

If in that case, would you please check the upgrading log for me? maybe some modules were not upgraded successfully.
Here is the instructions:
1. Enable Viewing hidden files in your OS. Below are the websites where you can check how to show the hidden files in your PC. For The Windows System: http://windows.microsoft.com/en- ... den-files=windows-7 For The Mac System: http://ianlunn.co.uk/articles/qu ... mac-os-x-mavericks/
2.Enter the root directory of the SD card, then find the hidden folder MISC and enter it. There is LOG folder in it.
3.The LOG txt file is under the LOG folder.

DJI Natalia Posted at 2016-10-11 02:21
If in that case, would you please check the upgrading log for me? maybe some modules were not upgr ...

Here is the last text info's on the LOG file ( hidden )


[00015633]========== remo-con disconnect. boot(15) ============
[00015709]Packet [C:\P3X_FW_V01.09.0060.bin] detected, card sn [0x41410a6e].
[00015783]Packet upgrade start...

[00015867]Packet checking...
[00015943]Packet vlink 01.09.0060 <-> 01.08.0080.
[00016019]Record vlink 01.09.0060 <-> 01.08.0080 (flow = 0).
[00016091]Done.

[00016168]Version checking[1]...
[00016279][03 05][00] v34.2.0.9 -> v34.2.0.9
[00016401][03 06][00] v2.4.20.18 -> v2.4.20.18
[00016480][04 00][00] v1.44.0.0 -> v1.44.0.0
[00016639][11 00][00] v1.8.0.0 -> v1.8.0.0
[00016799][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00016876][11 01][00] v1.8.0.0 -> v2.0.0.33
[00017007][12 00][00] v1.10.0.0 -> v1.10.0.0
[00017133][12 01][00] v1.10.0.0 -> v1.10.0.0
[00017243][12 02][00] v1.10.0.0 -> v1.10.0.0
[00017367][12 03][00] v1.10.0.0 -> v1.10.0.0
[00029941][15 00][00] device not detected.
[00030071][17 00][00] v1.1.1.7 -> v1.1.1.7
[00030244][17 01][00] v1.0.2.7 -> v1.0.2.7
[00030325][19 00][00] v1.0.8.96 -> v1.0.8.96
[00030401][01 00][00] v1.30.5036 -> v1.30.5036
[00030472][01 01][00] v1.30.5036 -> v1.30.5036
[00043127][08 00][00] device not detected.
[00043224][09 00][00] v3.0.0.10 -> v3.0.0.10
[00043296]Packet upgrade failed at version checking.


hoe this helps

Dompie Posted at 2016-10-11 14:31
Here is the last text info's on the LOG file ( hidden )

Thanks Dompie, according to your log, two modules cannot be upgraded successfully, it needs to be fixed by our engineers. Please feel free to contact our tech support at support.us@dji.com for further help.

DJI Natalia Posted at 2016-10-11 02:44
Thanks Dompie, according to your log, two modules cannot be upgraded successfully, it needs to be  ...

OK,  can I know what modules we are talking about ???

Dompie Posted at 2016-10-11 19:19
OK,  can I know what modules we are talking about ???

It shows "device not detected" for 08 and 15. And 08 stands for "Air encoder" and 15 stands for "Air USB transmission".

DJI Natalia Posted at 2016-10-11 07:24
It shows "device not detected" for 08 and 15. And 08 stands for "Air encoder" and 15 stands for "A ...

okay.
Are these modules located on the Gimball/cam support section or in the bird itself ??

I am really not sure, but can you do a full Factor y Reset and Start over?

MGR57 Posted at 2016-10-11 22:49
I am really not sure, but can you do a full Factor y Reset and Start over?

I do not know BUT it would be awsome to be able to do just that,  RESET to Factory default

Dompie Posted at 2016-10-11 20:24
okay.
Are these modules located on the Gimball/cam support section or in the bird itself ??

They are located on the gimbal camera, phantom 3 pro cannot be factory reset.

DJI Natalia Posted at 2016-10-12 10:22
They are located on the gimbal camera, phantom 3 pro cannot be factory reset.

so, in other words, the unit decided to land beyond my decision may be due to an update decided by the remote control, it landed on wires, broke one prop so obviously, it crashed on the ground BUT in tall grass so the fall was not so brutal, it was at approximately 20 feet in the air. Now, I had to proceed to an upgrade because the remote decided otherwise, I had to buy flex cable between the camera and the bird  due to the '' modules 08 and 15 not detected ', and it's gonna be MY FAULT  ???   are we serious here ??.....

May I remind everyone that this BIRD was working wonderfully BEFORE this unwanted update.  The Ipad became on version 3.00 the remote NOW is at Version 1.8, and the bird is ( if I am not mistaking ) at version 1.80,

Here is the LOG of the Hidden file ..

[00148008]========== 2016.10.14 15:34:18. boot(15) ============
[00148079]Packet [C:\P3X_FW_V01.09.0060.bin] detected, card sn [0x41410a6e].
[00148164]Packet upgrade start...
[00148239]Packet checking...
[00148316]Packet vlink 01.09.0060 <-> 01.08.0080.
[00148388]Record vlink 01.09.0060 <-> 01.08.0080 (flow = 0).
[00148464]Done.
[00148537]Version checking[1]...
[00148639][03 05][00] v34.2.0.9 -> v34.2.0.9
[00148738][03 06][00] v2.4.20.18 -> v2.4.20.18
[00148820][04 00][00] v1.44.0.0 -> v1.44.0.0
[00148977][11 00][00] v1.8.0.0 -> v1.8.0.0
[00149262][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00149340][11 01][00] v1.8.0.0 -> v2.0.0.33
[00149441][12 00][00] v1.10.0.0 -> v1.10.0.0
[00149546][12 01][00] v1.10.0.0 -> v1.10.0.0
[00149646][12 02][00] v1.10.0.0 -> v1.10.0.0
[00149749][12 03][00] v1.10.0.0 -> v1.10.0.0
[00162333][15 00][00] device not detected.
[00162452][17 00][00] v1.1.1.7 -> v1.1.1.7
[00162622][17 01][00] v1.0.2.7 -> v1.0.2.7
[00162707][19 00][00] v1.0.8.96 -> v1.0.8.96
[00162781][01 00][00] v1.30.5036 -> v1.30.5036
[00162857][01 01][00] v1.30.5036 -> v1.30.5036
[00175430][08 00][00] device not detected.
[00175527][09 00][00] v3.0.0.10 -> v3.0.0.10
[00175598]Packet upgrade failed at version checking.

And on top ove everything, when the red/green LED on the gimball turns to STEADY RED, we could hear a crackling noise comming from the gimball motors but mostly from the left right horizon motor.......  It IS very sad.......but I am very disapointed at the way it's turning out.

can you reset the standard??

rr@jensen.mail. Posted at 2016-10-15 19:44
can you reset the standard??

apparently NOT. I searched all over the web to find out Where I could reset the bird and it seems it's a state secret. DJI has a monopoly on their equipment and I do understand this issue. but when it involves a weird behavior that, to my deepest feelings, is unacceptable when we're dealing with an Aircraft, even so ministure in size as it could be, and this BIRD could jeopardize the safety of people in an aircraft when this bird looses it.  I strongly believe that countermeasures should be taken in order to validate the update process, prohibit the bird to even lift off in such a condition and/or, show a warning sign in the tablet that the bird will land due to a firmware mismatch. This way, many $$$$$$$ would be saved on the owner of the birds as broken props, broken landing gears, broken gimball, and may be more, injuried people because the bird has decided that LANDING is THE only option. Les us manages the bird to a safe site, a safe landing site and a SAFE LANDING period.  To me it would be a lot more responsible and respectfull of the owners of those '' expensive toys ''.

Dompie Posted at 2016-10-15 20:28
apparently NOT. I searched all over the web to find out Where I could reset the bird and it seems  ...

BUMP to the beginning

Dompie Posted at 2016-10-16 05:54
BUMP to the beginning

UPDATE:

I can't update the firmware BUT the DJI GO app on my tablet shows that the BIRD is at 1.9.60 version, the remote is at 1.8.0 and the DJI Go app is at 3.00.  
Now when I lower the camera it does it,  I can start the motors when I use both joysticks together. When I press the button to point the camera down, I get the following message :   DJI GO    DJI GO wishes to communicate with DJI C1  I have to chose between IGNORE or AUTHORISE.   ...And OH by the way, there is NO VIDEO but when I ask the software to take a picture or a video, it's doing it and I can view it on the sim Card. Also, I have the '' NO SIGNAL '' on the top left corner ( red ).  The gimbal is also working. I replaced the ribbon flat cable and '' to my knowledge '' the connections are working and the drone gimbal LED is not blinking but a steady green.

{:4_154:}

Dompie Posted at 2016-10-16 08:16
UPDATE:

I can't update the firmware BUT the DJI GO app on my tablet shows that the BIRD is at 1.9. ...

Hi, for this case about C1, please close the DJI Go app, then connect your aircraft with the RC and press the C1 button.
The notification saying "DJI Go would like to communicate with the C1 Button" will appear. Click "allow" and the DJI Go app will open automatically. After that, you will no longer get the popup.

For the upgrading issue, and no image, it needs to be sent in for further evaluation and get it fixed by the engineers.

DJI Natalia Posted at 2016-10-17 12:09
Hi, for this case about C1, please close the DJI Go app, then connect your aircraft with the RC an ...

Good day Nathalia,

Obviously, there will be charges applied to this '' evaluatin '' by youyr engineers AND I do not feel confortable to assume FEES that should not be assumed by the end user since, over the web, there is a LOT of people complaining about this UPGRADE that had perfectly operating drones that became completely inoperable.

What is your options at DJI about this misfortune ??

Dompie Posted at 2016-10-18 01:04
Good day Nathalia,

Obviously, there will be charges applied to this '' evaluatin '' by youyr engi ...

Hi Dompie, After you send it in, our engineers will evaluate what caused the issue, if it's the product faulty, and accord with DJI warranty policy, it will be free of charge. While it needs to be paid.
Because one prop hit a branch, then aircraft landed on grass, maybe that caused the problem, it's better to get it evaluated firstly.
Hope your kindly understanding, thanks.

DJI Natalia Posted at 2016-10-18 10:54
Hi Dompie, After you send it in, our engineers will evaluate what caused the issue, if it's the pr ...

OK here is a major correction to your affirmation.  The drone crashed because I could not take control of it, it wanted to go downward beyond my decision to NOT TO, It was near electrical wires of which it strucked because of HIS tendancy not to listen to the end user. So the prop broken was caused by the bird not by the end user. If you refer to this in the evaluation, I will definitely loose my temper.  More so, you told me in another thread that The video module got corrupted with the update. And may be the batteries did not have the proper firmware so the drone decided to go down due to wrong reading and I will have to suffer the loss ???   I really think DJI and I should have a phone talk.

Dompie Posted at 2016-10-18 20:24
OK here is a major correction to your affirmation.  The drone crashed because I could not take con ...

dump this topic to a front row.

Two threads now..
You were flying near "electrical wires"  - probably what caused the loss of control which caused your phantom's prop to "hit a branch"
Sync your flight records and contact support
you "fixed" your phantom by replacing a cable, not realizing that there was damage to other components that you can't see, (the #8 and #15) modules not appearing in your firmware update log.
Your phantom is DAMAGED, and needs repair, if your flight logs indicate the loss of signal was caused by faulty product, and it is still under warranty then there should be no problem with DJI customer support.

You may have to pay shipping charges, if the determination is that operator error caused the damage, you will have to pay for the repairs.
That all seems pretty straight forward doesn't it?
Hope you get flying again soon..

Two things.

1:  The drone suffered a dislocated gimbal arm ( left/right arm swivel ) that I fixed and repaired without any problems. I retested the gimball and it worked properly after. I replaced the cable AFTER an UPDATE request which went wrong, with very LOUD BEEEEEEPPPSSSS . I repowered the drone to complete the update  after finding out that it could not update module 08 and module 15.
The picture was working on the Ipad after the crash ( May I remind you ) and It was just a swivel arm issue.
The flight log was extracted soon after the crash. Unfortunately, I will check it tonight to find out what does it says.
As for the '' operator's issue '' comment, I was way above electric wires when I flew over them, I noticed that the drone was not responding anymore, it started to go downward beyond my request to get away from this location so, I had no other choices but to let it go downward to it's prop destruction issue and it landed in Tall grass. fortunately.

My strong belief is that DJI should be accountable for this WRONG going update as I am sure not beeing the only one that this situation happened.

But hey again, it's only my evaluation of this.