The video of my v3.06 FW crash is below.
Recap of earlier comments: Following the upgrade to v3.06 a week prior to the crash, I did full calibrations in Assistant, including IMU, and compass calibration. I had flown v3.06 a dozen times prior to the crash, with no issues whatsoever. The site where the crash occurred I have flown and filmed at least 50+ times since my first Phantom 1.0 almost a year ago. This P2 and H3-3D and accessories had been flying just fine several times a week on 3.04 since early April, including dozens of flights on the site of the crash. The setup was new in box in early April, and had never been crashed until this fateful day. On the day of this crash, I had lock on 7 sats at takeoff, then home point set, and 10 sats once stabilized in the air. The only change between the fatal outing August 11th and ~50+ prior flights on the exact same hardware is 3.06 versus 3.04. And the departure behavior is so indicative of a flight controller than suddenly decides it should be somewhere else. My current theory is that GPS / NAZA are badly confused all of a sudden. Also, FWIW, I have had GPS go out on multiple occasions on previous P2's running v3.04. The behavior in those cases was much more benign than in this case: the flight mode on OSD suddenly switches from GPS to ATTI, and the # sats shows zero. However, in the case of v3.04 losing GPS, there is a graceful transition from GPS to ATTI, not a sudden departure to an unknown coordinate system. Also, having had battery premature auto-landing experiences, power subsystem failures, and bad ESC's, I don't see indications of any of those symptoms in this crash.
HAL lives on in v3.06 in my opinion.
Kelly
[youtube]https://www.youtube.com/watch?v=fkmvUfC0Ov0[/youtube]