Ph65
lvl.2
Flight distance : 314199 ft
United States
Offline
|
Hi DJI Mindy,
From the threads I have read you are very helpful with with helping DJI owners resolving issues and concerns. Hoping you can assist me as well with eval of logs to determine issue, if user error and to keep from happening again.
I have a phantom 4 pro obsidian which experienced a compass error shortly after takeoff. I submitted a bug report including flight logs and pictures however I received no response so I submitted support ticket. They claim the drone needs to be sent in to determine issue. However I have and can submit flight logs. It would be appreciated if you could have the data examined the data and provide analysis without shipment of the drone.
Details.
Support number: Your request (1070157)
Drone Crash – Compass Error After Take Off – Phantom 4 Pro Obsidian
Shortly after takeoff, Phantom 4 Pro Drone (herein referred to as Drone) became unresponsive and started to drift like it was in ATTI mode. However, Drone appeared to be unresponsive to control commands. The Drone continued to drift toward obstacle (6-foot fence). Tried to lower Drone altitude to force land into grass area. However, Drone continued to drift with little or no change in altitude and collided with obstacle 18 seconds into flight. At all times, control display stated flight mode was P-GPS, and there was no indication the compass error had occurred (see flight log DJIFlightRecord_2018-03-30_[18-17-26].txt and see attached picture AerialPathOfCrash.JPG for path to crash (flight path skewed by 10’ or so)).
Text Log of Flight:
[["2018-03-30 18:17:26","","Your aircraft has entered a Warning Zone (Unpaved Airports). Please fly with caution."]],[["2018-03-30 18:17:35","","Home Point Recorded. RTH Altitude: 30m."],["2018-03-30 18:17:43","","Obstacle Avoided. Revise Flight Route"]]
The "Obstacle Avoided. Revise Flight Route" is a fallacy as the Drone collided with obstacle.
There have been many flights from this specific location as it is used for practice takeoff for tight locations over water. Nothing observed in sight that would cause magnetic interference.
At practice locations different from crash flight location, there have been compass redundancy warning or a similar warning prior to the ready for takeoff display which has increased in frequency recently (last month). When compass redundancy warnings occur, instructions stated and displayed are followed and moved Drone over five feet or cycle power which resolves the compass redundancy warning or similar warning. After the crash, relocated Drone to a large practice field and similar compass redundancy warning occurred (see attached DJIFlightRecord_2018-03-30_[19-21-54].txt flight log (no takeoff) for compass warning and see picture CompassRedunWarnNoTakeOff.JPG and that was uploaded with report).
Is this Drone experiencing hardware or firmware faults? How is this issue resolved?
Looking forward to your analysis of what occurred, how to resolve, repair, and instructions to how to land Drone when such compass errors occur.
See attach pictures AerialPathOfCrash.JPG, CrashTakeOffAndCompassError.JPG, CrashEndOfLog.JPG for information on crash
See attached picture of example of compass redundancy warning: CompassRedunWarnNoTakeOff.JPG
Regards,
Thanks
|
|