Recent content by Krag

The problem is if you calibrate it too often you run the risk of calibrating it in a bad spot. You can't always tell just by looking if there is magnetic interference in an area. I set my Mavic down in a field once and the compass went nuts. Turns out there was a big steel plate under the ground...

I ordered from DJI on 10/30/2019 at 23:06:41 (UTC-5) and as of Nov 12 it had not shipped. I canceled the order with DJI and ordered from Amazon and it should be here Friday Nov 15.

There is already a good thread on this: The NAS; The FAA makes a stand.

The Mavic launch was about usual for DJI in that it was months before it was easy to get one. Announced in Sept 16 shipping in Oct it was Jan/Feb before most of the preorders were done. But it was spring 2017 before you could order and get one in less than a week. When they started shipping it...

Ah, I am very glad to hear that. I hated the idea of someone with 1300 posts flying like a noob. :-)

as I said. What exactly were you trying to do there anyway?

Relax. No one ever does the CSC by mistake. You would have to be flying full backwards, down, strafing and turning max speed all at the same time. If you fly like that you are going to loose the bird anyway.

I can still read the release notes and decide I don't need "optimized startup music" more than my freedom to fly up a 700m cliffside. And I use Litchi so I don't have to deal with DJI spying. In my experience the folks who always upgrade haven't been around long enough to be burned by an...

I am sorry to say there is no way to use Fatsharks with a Mavic. FatShark uses 5.8ghz and Mavic uses Ocusync and they are not compatible. If your FS have HDMI in (not sure) you could use a tablet that has also has HDMI out like Nvidia Shield.

Mine locked once when I accidentally used a mixed module firmware with the newest DJI Go. But the same PC program that does the firmware rollback will unlock it no problem.

I don't think temp was a factor. The battery was kept at room temp (home and then car) from the time it was charged until it was used. It was mid 50's at the bottom and mid 40's at the top. I got the logs late last night and haven't had time to analyze yet. I did see a "smart battery error" but...

Alright! Now we are getting somewhere. Half of the mystery is solved. I just check the drone that made it and it had the battery parameter changes and the other one did not. That's probably why one didn't made it and the other didn't. I am still not sure why it would try to land at all though...

Ah! What parameters specifically?

We might have been able to stop the autoland but we were surprised and didn't even try until it was too late.

Surprisingly the Mavic has already been recovered. Once it is down off the mountain and dried out I'll take a look at the logs and see if I find out anything.