I apologize if this has been discussed here on the forum. I did a search and could not find an article that exactly matches what I am experiencing. I have a Mavic Pro, CS & Goggles that I've had for two years that has been an absolute dream to fly. Never had any problems. Never had a crash. Just 400+ miles of pure fun.
When I upgraded my rig to V01.04.0400, I noticed that my MP started acting strange. Where I could normally fly 14,000+ feet out/back with no issues, it would start streaming all sorts of disconnect messages from 3,000 feet on and I couldn't get past 5,000 feet before it would completely disconnect and RTH. My goggles started acting up too. Lots of messages about interference and they too would disconnect at a diminished range. I spent several months trying to sort out what had happened. Did all the usual calibrations, changed where I always fly from to out in the middle of a 400 acre field, factory reset, multiple flashes, etc. Nothing seemed to help.
Then along came the V01.04.0500 FW and when I flashed my rig to that, my trusty MP acted like it was possessed. Just a sample of the odd behavior:
* After takeoff, it would fly like it was in sport mode (40 MPH instead of 20 MPH). Manually switching between S/P mode would make no difference. If I just kept flying at full speed, it would gradually slow down to P mode speed over about 30 seconds and then fly fine for the rest of the battery. Next battery, same problem.
* Beyond about 1,000 feet out, the drone would log RC disconnects about every second. Beyond 2,000 feet it would just disconnect permanently and RTH.
* RTH stopped working altogether. When you would RTH, the MP would turn, head back home, stop over the landing pad and simply descend, landing 10'-20' off the pad. Note that I realize that if you RTH close to the pad it will do this. I'm talking about 1,000 feet out. Also would not climb to preset altitude before coming home, would not align itself with takeoff position when it got home and no messages about precision landing while descending. Also would not get the "The home point has been set..." message when taking off. Yes, I do a precision takeoff everytime.
* Would not hover. If you took off and just didn't touch the sticks, it would "wobble" around over the pad. Sometimes to the left, sometimes to the right, sometimes up, sometimes down. Again, have done the IMU and compass calibrations about a half dozen times and it never made a difference. I could never find any type of pattern and I did several RC calibrations to see if the sticks were off.
Now if I flashed my rig down to V01.04.0300 everything would go back to normal. No disconnects, no speed issues, RTH hits the center of the pad every time. I've tried 3 different times to flash from 300 to 400 and/or 500 and get the same results every time.
So right now, I'm just thankful that I've gotten my trusty friend back and if I have to stay with the 300 FW that's probably not going to be an issue for me. But I was wondering if a) anybody else has had this experience or anything like it and b) if so what did you do to resolve the issue? Sorry for the long post but trying to be detailed with describing the problem.
All thoughtful comments/suggestions are appreciated.
When I upgraded my rig to V01.04.0400, I noticed that my MP started acting strange. Where I could normally fly 14,000+ feet out/back with no issues, it would start streaming all sorts of disconnect messages from 3,000 feet on and I couldn't get past 5,000 feet before it would completely disconnect and RTH. My goggles started acting up too. Lots of messages about interference and they too would disconnect at a diminished range. I spent several months trying to sort out what had happened. Did all the usual calibrations, changed where I always fly from to out in the middle of a 400 acre field, factory reset, multiple flashes, etc. Nothing seemed to help.
Then along came the V01.04.0500 FW and when I flashed my rig to that, my trusty MP acted like it was possessed. Just a sample of the odd behavior:
* After takeoff, it would fly like it was in sport mode (40 MPH instead of 20 MPH). Manually switching between S/P mode would make no difference. If I just kept flying at full speed, it would gradually slow down to P mode speed over about 30 seconds and then fly fine for the rest of the battery. Next battery, same problem.
* Beyond about 1,000 feet out, the drone would log RC disconnects about every second. Beyond 2,000 feet it would just disconnect permanently and RTH.
* RTH stopped working altogether. When you would RTH, the MP would turn, head back home, stop over the landing pad and simply descend, landing 10'-20' off the pad. Note that I realize that if you RTH close to the pad it will do this. I'm talking about 1,000 feet out. Also would not climb to preset altitude before coming home, would not align itself with takeoff position when it got home and no messages about precision landing while descending. Also would not get the "The home point has been set..." message when taking off. Yes, I do a precision takeoff everytime.
* Would not hover. If you took off and just didn't touch the sticks, it would "wobble" around over the pad. Sometimes to the left, sometimes to the right, sometimes up, sometimes down. Again, have done the IMU and compass calibrations about a half dozen times and it never made a difference. I could never find any type of pattern and I did several RC calibrations to see if the sticks were off.
Now if I flashed my rig down to V01.04.0300 everything would go back to normal. No disconnects, no speed issues, RTH hits the center of the pad every time. I've tried 3 different times to flash from 300 to 400 and/or 500 and get the same results every time.
So right now, I'm just thankful that I've gotten my trusty friend back and if I have to stay with the 300 FW that's probably not going to be an issue for me. But I was wondering if a) anybody else has had this experience or anything like it and b) if so what did you do to resolve the issue? Sorry for the long post but trying to be detailed with describing the problem.
All thoughtful comments/suggestions are appreciated.
Last edited:
