calidoug
New
United States
Offline
|
I had a similar issue this morning, which resulted in a catastrophic crash. My aircraft is destroyed. 100'+ fall directly onto concrete.
I was on an ad agency shoot in Los Angeles very early this morning. (6:30am) I had prepped last night, by discharging and recharging all three batteries, and both remotes fully. I conducted a full preflight, and flew the aircraft for a systems check. Everything was behaving nominally, and checked out. I packed up for the next morning. Once I arrived and got my master iPad hooked up to the master remote, and powered it on, I then inserted the battery into the aircraft and turned it on.
The normal pairing sequence did not finish, and I was forced to update to the new firmware. I followed the procedure for both the aircraft, and both remotes. All finished normally. (Proper lights, sounds and sequences.)
I turned the aircraft off. I turned both remotes off. I reconnected the iPads and turned the master remote on. I then turned the aircraft on and it paired properly with the master remote. Then I turned the slave remote on. It paired properly with the master, and so I continued preflight checks.
I calibrated the compass. I calibrated the IMU. I also made the necessary adjustments to the gimbal wheel speed, and video and still settings for my cameraman on the slave remote app.
Preflight completed, and our shoot planning finished, we readied for our first test run. I verified the 'Safe to Fly (GPS)" lock, verified that I was in P-GPS flight mode, and readied for take off. We made our first run no problem, so we started shooting. We made a few passes following and passing our subject, then moved location about 250 south. I landed the craft and reestablished home position.
We had about 45% battery left, so we were good for a few more shooting runs. Our subject repositioned, and we readied for takeoff. I verified the 'Safe to Fly (GPS)" lock, verified that I was in P-GPS flight mode, and readied for take off. Take off was just fine. We made a couple passes, and received the "low battery warning" (set at 35%) during the middle of a run. As we finished the run, we received the "critical battery warning", and an audio warning that Return to Home would activate in 10 seconds. At this point we were about 25' high, and about 25' horizontally from the currently set home point. No obstructions in between, and flat level ground.
At this point, we were notified that Return to Home was activated, and then aircraft raced straight up another 75', hovered for about half a second, shut off completely, and dropped to the ground like a stone!!
It crashed apart into a hundred pieces. Everything that could have broken did. Both sides of both arms, both support struts, all four landing gear, 3 out of 4 rotors, the camera gimbal arm, camera gimbal ribbon, camera housing, and on and on. Even the battery looked like it was going to pop. About the only thing not very damaged was the airframe covers.
I am on the phone with DJI right now. I've been asked to send it in for evaluation. We'll see how they handle it.
If you're asking, my advice is: DO NOT FLY WITH THIS FIRMWARE. |
|