Phantom 4 Pro V2 Fell out of the sky...
- Thread starter russellk
- Start date
I really think you are onto something there. Im going to go out and do a flight in T mode and see how the uncommanded yaw is physically affected, and then post the dat file
Ya that is quite terrible. Mine is the same. Wasn't it you who posted early on (in a different thread) that your v2.0 was flawless? I ask because it hints that if a firmware caused it to go bad, then another firmware could fix it. But if it has always been bad I suppose there is the possibility of bad hardware? SAR104, did you ever get a chance to see DKG's flight log?
I did report that it was flawless, the first few flights didnt show issue. But i started to notice the drift before my first FW update. My bird is worthless for video, photos take a lot of playing with it to get a good shot at low shutter speed (sunrises, sunsets; the whole point I ought the drone)
@sar104
@BudWalker
As an update, this unit is currently at DJI for assesment. DJI refuses to recognize the problem, and tells me “everything is normal”. They called yesterday and I gave your guys’ explanation of the issue from the logs. They sent an email today, again, saying no issue. The drone is already on its way back to me. I opened a thread with tech support and sent all the graphs, flight log, and video to them. They are sending all this info to their “product engineers”. Im a bit irritated, but lets see what happens
@BudWalker
As an update, this unit is currently at DJI for assesment. DJI refuses to recognize the problem, and tells me “everything is normal”. They called yesterday and I gave your guys’ explanation of the issue from the logs. They sent an email today, again, saying no issue. The drone is already on its way back to me. I opened a thread with tech support and sent all the graphs, flight log, and video to them. They are sending all this info to their “product engineers”. Im a bit irritated, but lets see what happens
- Joined
- Nov 28, 2015
- Messages
- 33
- Reaction score
- 12
- Age
- 54
My 4th V2 fell from the sky today. Posting flight records tomorrow.
I read somewhere here that if bottom ultrasonic sensors are blocked, the drone thinks it hasn't gained enough altitude and will just keep going up. Were the sensors blocked by any chance? In an event like this, a suggestion from what i wrote above was to switch it to ATTI mode
WELL!! Ladies and Gentlemen, here I am again in this same thread... for the THIRD TIME. That's right. My P4P V2.0 suffered catastrophic failure and fell out of the sky for the third time. I am requesting help from the one and only @sar104.
I was just over 200 feet toward the end of a flight with 42% battery remaining. Then as I pushed the right stick down and to the right and gave slight throttle up on the left, I saw the dreaded washing machine roll before "aircraft disconnected. I had power from the battery up until impact. This was only the second flight on a refurb sent to me after I sent mine in for repairs. SECOND FLIGHT after receiving this bird from DJI on 9.5.19. On my last v2.0 I managed 267 flights and over 1.8 million feet distance traveled before guiding my trusty money maker into some power lines on 8.15. After waiting patiently (and after paying $380) I am sad to be relying on my P3s yet again... I will upload the flight log in the next few minutes.
Thanks!
I was just over 200 feet toward the end of a flight with 42% battery remaining. Then as I pushed the right stick down and to the right and gave slight throttle up on the left, I saw the dreaded washing machine roll before "aircraft disconnected. I had power from the battery up until impact. This was only the second flight on a refurb sent to me after I sent mine in for repairs. SECOND FLIGHT after receiving this bird from DJI on 9.5.19. On my last v2.0 I managed 267 flights and over 1.8 million feet distance traveled before guiding my trusty money maker into some power lines on 8.15. After waiting patiently (and after paying $380) I am sad to be relying on my P3s yet again... I will upload the flight log in the next few minutes.
Thanks!
That's unusual - several things went wrong almost simultaneously, but I cannot see a causal connection. At 766.3 seconds the uplink was lost. That resulted in a sudden motor adjustment with the lack of stick input. No flight control problem there, but at 769.0 seconds the left ESCs both failed. That didn't go well, as you would expect. And then at 771.2 seconds the right ESCs failed.
766.337 : 38288 [L-RC]rc_connect:1=>0
766.337 : 38288 [L-SYS]app lost connection!
766.337 : 38288 [L-GEO]lost app, clear app_pos_info
766.337 : 38288 [L-RC]rc_func_disable @ [771194 ms]
766.339 : 38288 [L-SEND DATA]app connect changed:last(1) != current(0)
766.443 : 38293 [L-RC]rc_connect:0=>1
766.443 : 38293 [L-SYS]app connected!
766.443 : 38293 [L-RC]rc_resume @ [771296 ms]
766.443 : 38293 [L-RC]set rc_resume_lock
766.443 : 38293 [L-SEND DATA]app connect changed:last(0) != current(1)
766.984 : 38319 [L-RC]clr rc_resume_lock
769.022 : 38417 [L-FMU/MOTOR]esc err, status:0
769.022 : 38417 [L-FMU/MOTOR]fault on , esc(2) self test error
769.022 : 38417 [L-FMU/MOTOR]fault on , esc(3) self test error
769.088 : 38420 [L-FDI][CTRL]: fault on , tilt_ctrl_fail
769.108 : 38421 [L-RC]craft ctrl failed!!!
769.151 : 38423 [L-FMU/LED]action changed. sys error:esc error!(18)
769.421 : 38436 [L-FDI][CTRL]: fault off, tilt_ctrl_fail
769.609 : 38445 [L-FDI][CTRL]: fault on , tilt_ctrl_fail
769.817 : 38455 [L-FDI][CTRL]: fault off, tilt_ctrl_fail
769.941 : 38461 [L-FDI][CTRL]: fault on , tilt_ctrl_fail
770.150 : 38471 [L-FDI][CTRL]: fault off, tilt_ctrl_fail
770.234 : 38475 [L-FDI][CTRL]: fault on , tilt_ctrl_fail
770.318 : 38479 [L-FDI][CTRL]: fault on , height_ctrl_fail
770.422 : 38484 [L-FDI][CTRL]: fault off, tilt_ctrl_fail
770.422 : 38484 [L-FDI][CTRL]: fault on , head_ctrl_fail
770.483 : 38487 [L-FDI][CTRL]: fault on , tilt_ctrl_fail
771.063 : 38515 [L-GIMBAL]The 1st gimbal 0 disconnect
771.209 : 38522 [L-FMU/MOTOR]fault on , esc(1) self test error
771.209 : 38522 [L-FMU/MOTOR]fault on , esc(4) self test error
771.212 : 38522 [L-RC]craft ctrl failed!!!
771.892 : 38554 [L-ESC]ESC1 link down||
771.897 : 38555 [L-FMU/MOTOR]fault on , esc(2) is disconnect
771.897 : 38555 [L-FMU/MOTOR]fault off, esc(2) self test error
771.897 : 38555 [L-ESC]ESC2 link down||
771.917 : 38556 [L-FMU/MOTOR]fault on , esc(3) is disconnect
771.917 : 38556 [L-FMU/MOTOR]fault off, esc(3) self test error
772.172 : 38568 [L-RC]rc_connect:1=>0
772.172 : 38568 [L-SYS]app lost connection!
And here is the result:
That looks like simple hardware failure, except for the strange coincidence (?) of the RC disconnect. @BudWalker ?
There also seems to be some kind of failure with the MC. The values mc_dev, mc_err, mc_act and mc_fault all changed from 0 at 769.738 secs.
Remind me not to go flying with this guy @Dallas Drone Guy
I guess fc means flight controller…
Lose connection should rth not DROP, correct?
This is the 2nd flight! They just sent this pos to me a week ago !! I need this to be not my fault, fix for free!!!!
Lose connection should rth not DROP, correct?
This is the 2nd flight! They just sent this pos to me a week ago !! I need this to be not my fault, fix for free!!!!
Send them the log, describe what happened, and point out the errors. You are welcome to use the graphs and event stream listed above.
WOW! My Phantom 4 Pro, just dropped like a rock while doing a POI shot at about 200' No issues with the battery, and no error on the controller. After reading through this forum, it doesn't appear to be an isolated incident.
- Joined
- Aug 7, 2016
- Messages
- 1,611
- Reaction score
- 973
So ya'll won't belive this but. IT HAPPENED AGAIN. That's right. my FOURTH time that the v 2.0 fell out of the sky at no fault of my own. This time I was beyond the 12 month mark so I had to pay for the repairs myself. It happened on 8.22 of 2021.
For me it has been the V2. I remember them all well. 1st it hit an empty sidewalk from 120' up, 2nd bounced off a roof and barely missed a man cleaning his high-dollar sports car, 3rd it hit a random house roof from 200' and bounced to the front yard, and 4th just in August, it again hit a residential roof and fell to the grass. It is wild to think that I am on my SIXTH bird (one because of power lines, my fault) but still on the original RC, lol. Maybe I should sell now while I still can!?!
Edit - for all the doubters out there, the proof is in the flight logs. All three were replaced FREE OF CHARGE because of data showing ESC failure. The only reason the 4th wasn't replaced for free is because it had been more than a year since I received that bird, so DJI was off the hook.
Last edited:
- Joined
- Aug 7, 2016
- Messages
- 1,611
- Reaction score
- 973
I was looking at the first post of this thread again. Something was very unusual. If you look at the end of the flight, just before the fall, you can see fast and extensive movements of sticks in every direction. Very unlikely during a normal flight. As you couldn't decide which way to go. Such chaotic movements of sticks can be seen during the whole flight.
But what could be important is that a few seconds before the fall down in one moment both sticks happened to be in the low inner corners which is the position for shut off the motors when the drone is on the ground. Maybe it could have affected the motors during the flight. This is only speculation but the DAT file showed that two motors suddenly stopped which caused the fall.
But what could be important is that a few seconds before the fall down in one moment both sticks happened to be in the low inner corners which is the position for shut off the motors when the drone is on the ground. Maybe it could have affected the motors during the flight. This is only speculation but the DAT file showed that two motors suddenly stopped which caused the fall.
