Thanks, but there is one small problem.
The .txt isn't the right one. There are two .txts for today's .DAT. During that flight the Mavic went through a motorStop/motorStart sequence which starts a new .txt.. DJIFlightRecord_2016-12-27_[11-58-31].txt is the second of the two .txts. and it starts at time 256. You referenced time 2 mins 33 secs which has to be in the first .txt.Bottom line is I was unable to find anything in the .DAT or .txt that coincides with the event you described. I'm using this .txt DJIFlightRecord_2016-12-27_[11-53-28].txt At time 153 (i..e 2 mins 33 secs) the Mavic was in GoHome mode travelling at 10 m/s or 36 kph. I thought you had said this event had occurred after a speed of 63 kph.
I'm not sure what you're looking for. Since @germ s first flight did not use the back compass there is no evidence that the noisy back compass was the cause of the compass error.
But, that's from HealthyDrones where the change from Sport to GPS_ATTI was made. That time was 7 mins 16 secs not 2 mins 33 secs
Oh ok - makes sense. Hopefully somebody else who has had the rear compass issue and has been fixed would be kind enough to upload their before and after logs to compare against mine. Would really like to try and work out if this is hardware or firmware.
Sounds like a totally different problem. Could you provide the .DAT from one of these flights? Go here to see how to retrieve the .DAT file. It'll be large so you'll need to Dropbox it and post the link.
Here is my dat file let me know what you find
Am I right that you posted your .DAT in response to a request that someone else provide their .DAT? I took me a couple of minutes to figure out that this (your) .DAT didn't exhibit any of the symptoms that @dsd317 described.
Not more than me. But, alas, with a middle name of Murphy's Law, it wasn't to be. They shipped it on Monday (12/26) from Carson, CA (to FL). The outbound took 5 days. But with the New Year's holiday, it's now scheduled to arrive on 1/4/17. Oh well...
