Another clue ... May not be the battery after all.
The first pic is a color key for the fields to be addressed in the 2nd pic and the 3rd pic. The 4th pic varies from this scheme but should be self explanatory.
The second pic is the ending portion of the flight log from the 29 second flight that ended up with the Anafi falling to the ground. Notice everything appears fine, and the log abruptly ends showing the bird still in the air (and climbing). No crash is reported as having occurred. At this point, I cleaned it up and replaced the battery. (I think I briefly left it on, convulsing a bit, then removed the battery. However, this is not reflected in the log.)
The third pic is from the beginning portion of the log from the flight immediately after the Anafi was cleaned and the battery replaced. (Crashed flight began at 16:39; subsequent flight at 16:57.) (Note the color key is also shown at the top of this page, where certain fields of the lines of text I’ve highlighted.) Notice the “product gps” field is set to “false” for the beginning portion of the flight showing in the log. This is the gps on the Anafi itself, not the controller. While false, the “controller_gps_latitude” and the “controller_gps_longitude” both show unchanging values of 500. Also note the “product_gps_latitude” and the “product_gps_longitude” both show unchanging values of 500. But the altitude begins changing from 0 as the Anafi takes off. I do remember one of the gps indicators was green, then changed to red, then back to greeen, cycling like that for a short period of time. I think it was the Anafi gps, but the controller gps stayed green if memory serves correctly. (But can’t swear by it.) I can say when I lifted off both fields were green. I always check for that. But I think it cycled back to red right after takeoff. The log makes it appear as if gps was never acquired.
Finally, the 4th pic shows the section of the log where the “product_gps_available” field changes to “true.” This occurs at 6.045 seconds. (The “time” field, while not highlighted, indicates “6045”) The flight seemed to go without incident after that, including my first attempt with the dolly zoom function, and a climb to 400 feet. (Total flight time of 16:57.)
Given this subsequent flight had some trouble with gps, I wonder if there was a gps problem 29 seconds into the flight that crashed. I was taking off from an asphalt walkway next to a grassy field in a park, and on the other side of the walkway was a tree line. So maybe it had a problem with gps because of the trees? But the first flight went without incident and had no issue acquiring gps.
I also wonder if the software or firmware isn’t properly handling situations where gps is lost, even if momentarily. Not really sure ...
View attachment 960
View attachment 961
View attachment 963
View attachment 964