Also posted this on the DJI forum:
Ok, so this is the strangest thing.
As I was packing up my Mavic to get ready to ship back, I replaced the 32GB microsd card that I had in there with the card that came with the Mavic....and it started working again. WTF?
I checked the 32gb card in my pc, and it seemed to be fine. Even ran a scan on it. To see if that was really the cause, I put the 32gb card back in the Mavic, and the gimbal became non-responsive again.
I put the 16gb card back in, it started working again.
WTH? Should I still send it back? Should I just not use that card? I'm not sure what to do at this point.
This was also my experience this morning. I have been using a 64 GB card very successfully. This morning, I got the "gimbal disconnected" message in my "status" when turning the MP on. I think I found my issue. Maybe it will help others. (I was dreading having to send in for a gimbal repair).
It was the SD card. Through reading this thread and a couple of others I did some testing.
My camera had power and the gimbal did it's normal thing during startup. There was video on my iphone, but the camera was continually trying to focus. There was also no camera control.
Replacing the SD card worked. All is back to normal. Here's what I think was the problem.
I had used the card very successfully. I usually pop it out of the MP and using an adapter, plug into a USB port on my laptop (PC) to copy them off of the card. While doing this, I changed the name of a couple of files on the SD card to make them more meaningful. It's after doing this and inserting the card back into the MP that I experienced the problem.
The MP would no longer recognize the card. Another card would work fine. (so would leaving the card slot empty). I popped the SD card back into my laptop and simply deleted the files that I changed the names of. Once done, the card was fine in the MP and I was able to "format" it again. I believe that it would have been fine without the formatting, but wanted to start fresh.
I am fairly confident that this has been fixed.
I think the "gimbal disconnected" message is misleading in this case.