tmoerel
Well-Known Member
Flew away 2.8kms (9186 feet for the metrically challenged) in a straight line yesterday without a hitch. And that is with the lower power emission we are forced to in Europe!Anyone did a range test?
Flew away 2.8kms (9186 feet for the metrically challenged) in a straight line yesterday without a hitch. And that is with the lower power emission we are forced to in Europe!Anyone did a range test?
Oh, ok. Thanks for the reply. Now I wonder how I didn't see it before.The blinking means there is interference detected. The RC signal can do the same. Normal behaviour and not related to this update, it was always there.
How do you use the "Find My Drone" feature.....I didn't see any mention of it in the latest users manual?
I'm going to assume here it transmits the best quality based on the connection. So instead of losing feed from camera it can lower quality yet continue to provide images without it being spotty or jumping/skipping images.
I remember reading earlier in an firmware update thread that the beeping volume for a controller low battery warning could be adjusted, (turned down).
I also read someone suggesting that the beeping volume for the aircraft RTH warning, (sounded by the controller), could also be turned down.
However yesterday when I initiated a loss of connection and allowed a RTH to begin, I couldn't find any way to adjust the RTH beeping volume
within the GO app or the on the controller.
Has anyone found a button or setting to adjust the RTH beeping volume in v01.03.0600 and GO 4.0.7?
Flew away 2.8kms (9186 feet for the metrically challenged) in a straight line yesterday without a hitch. And that is with the lower power emission we are forced to in Europe!
Thanks...I didn't think to look there for it......will do so when I get home tonight.
I have not tried it yet. It's similar to find my iPhone. It points on map last known location for the drone.
Again.... I haven't tried it yet. So I can speak much about it.
Mike
Mine was manufactured on 12/01/2016 and no major issues to-date (knock on wood) with functionality or during updates. The only issue I seem to have is related to DJI assistant 2 on my I-Mac where I can't perform a sensor calibration. The screen never displays the grid patterns so I have to abort out. However, I can do it on my Windows laptop.....so I do have a work around but an issue none the less.Those having problems with the upgrade check the manufacturing date of your mavic: DJI Mavic Pro Serial Number Decoder
We might see a pattern showing us that a certain manufacturing date range causes trouble indicating there might be some hardware revision with problems.
Mine was manufactured on February 28th 2017 and never had any problems. Upgrades go smooth, it flies well.
Adding the manufacturing date to your signature might also be a good idea so others can see when eventual trouble drones were built.
how did you come to the conclusion that the firmware update has anything to do with the gimble getting stuck on the arm during calibration? It sounds like a hardware issue to me as there must be some free play in the joints or something that is bent/broken that is allowing it to contact the arm as it goes thru it's movements. Not sure how a firmware update could result in a hardware issue such as this.Against my own advice I updated to this new firmware and right away it bites me in the butt. after the firmware update the gimble wouldn't calibrate correctly on start up, it would actually get stuck on the arm of the gimble. and gave me gimble overload, gimble obstruction warnings. I had to physically move the camera off the arm. That and when it does its starting calibration it seems to slam into something when it calibrates downwards. I finally got the gimble to stop getting stuck on the arm but it still slams into something on the downward calibration.
Against my own advice I updated to this new firmware and right away it bites me in the butt. after the firmware update the gimble wouldn't calibrate correctly on start up, it would actually get stuck on the arm of the gimble. and gave me gimble overload, gimble obstruction warnings. I had to physically move the camera off the arm. That and when it does its starting calibration it seems to slam into something when it calibrates downwards. I finally got the gimble to stop getting stuck on the arm but it still slams into something on the downward calibration.
Did you have an ND filter on at the time? This happened to me once when I did not have the ND filter fully seated. It caused the edge to get stuck on the arm during calibration. Once I fully seated the filter, all was good.Against my own advice I updated to this new firmware and right away it bites me in the butt. after the firmware update the gimble wouldn't calibrate correctly on start up, it would actually get stuck on the arm of the gimble. and gave me gimble overload, gimble obstruction warnings. I had to physically move the camera off the arm. That and when it does its starting calibration it seems to slam into something when it calibrates downwards. I finally got the gimble to stop getting stuck on the arm but it still slams into something on the downward calibration.
Because its never done it before. I just turned it on before the firmware update and it didn't do it.how did you come to the conclusion that the firmware update has anything to do with the gimble getting stuck on the arm during calibration? It sounds like a hardware issue to me as there must be some free play in the joints or something that is bent/broken that is allowing it to contact the arm as it goes thru it's movements. Not sure how a firmware update could result in a hardware issue such as this.