Aloha,
For two days now, I have been running DJI Go 2.6.1 and the most noticeable change has been the battery warning levels. My normal warning levels are 10 percent for critical and 30 percent for initial warning as used to be the default for the P3 Professional. That was workable. Yesterday, in the midst of a 400 foot altitude survey of my country neighborhood, I had my driver go on to Kahekili highway (35 mph) and then through to Kamehameha Highway (35 mph) and on down to Wailehua Road to turn Mauka (toward the mountain) when suddenly I started to get a battery warning (RTH!) while waiting to turn left (American style lanes). WTF! Somehow, my standard settings, that were the default of DJI, had been changed to a 35 percent RTH. Well, after we turned and I was able to step out of my soiled chair in the back of the truck, the P3, still at 400 feet, announced the standard 30 percent warning. (It was a long wait to turn left.) I landed the P3 in my friends parking lot and swapped batteries and took off again to head home (we were on a schedule).
Aside from the fact that we had descended -158 feet from my home launch spot to the parking lot and returned to a comparably lower altitude at home (163 foot above the controller for 400 feet - I do not know how this math works out - just telling it like it was), everything else was normal until it again gave me the RTH warning at 35 percent. Fortunately I was already at home - except it wanted to go back to the parking lot a mile and a half down hill where the last home point was declared! Well, if you know how to handle RTH warnings, you know it was duck soup to clear the warnings, burn some more battery and finally land at a respectable battery percentage. But, still! BTW, a big mahalo to this forum so I could do that!
That evening / night, I studied the problem while I was charging my batteries. The events of the day were strange so I checked my software versions and learned my DJI Go had been updated to 2.6.1. It turns out that my battery settings using only the DJI GO app (2.6.1) have a 20 percent Critical Warning and a 35 percent initial warning threatening RTH. Strange, but there it was!
OK now, sorry to throw in another variable, but we tried "Follow Me" for the same mission the next day after enabling an Android feature that would have allowed me to use Follow Me for the initial survey the day before. Follow Me worked great when we enabled my device to discuss location data with a nearby device! First day I had to drive my P3, the second day "Follow Me" flew my P3.
So, for the second day we start everything up and my P3 registers the standard 10 percent Critical Warning and 30 percent initial warning. (OK, we are all doing better after a good night's sleep.) We travel the back-roads at 400 feet with the amazing Follow Me driving and probably doing a better job than I did the day before. We cover areas missed the previous day and turn for home when again I get this off-the-wall RTH battery warning at 35 percent. But now I am stuck between high power lines and large, tall trees and trying to figure out how to land. This time the RTH Home Point is still at my house, so I figure trying to land between high power lines and large, tall trees is worth the attempt. There were almost no problems. The only thing out of ordinary was my video downlink feed was distorted a few times. Love my P3! We packed everything up and drove home.
So now, I have two sets of battery warnings that will require sorting out. Anyone else getting this strange brew?
Aloha and Drone On!
|