Battery cells not reporting properly

Flight Reader
1

Recently my flight logs for one of my Phantom 3 batteries have been reporting 6 cells rather than the normal 4 cells in the battery. Also, the 6th cell is reporting high deviations. The flight was flown on Litchi on an Android tablet and the flight log was uploaded manually. The flight is a light painting mission so that is why the waypoints are in the vertical plane. I am running the latest version of Flight Reader.

Here is the most recent flight log.

2024-06-11_22-31-44_v2.csv (1.7 MB)

Chris

2

Did you try contacting Litchi for help? Their app actually recorded 6 battery cells as shown here:

image
image1238Ă—461 38.9 KB

3

No I haven’t because it is just a recent thing, but I will try them and see what happens they say.

Thanks, Chris

1 Like
4

I checked the flight in question in AirData and it is reporting the battery information correctly. I wasn’t able to check right away as their servers are overloaded due to the new US DJI Flight Log policy, so it took awhile for my log to show up.

I am wondering if this is due to Flight Reader using the serial number on batteries because the battery in question is a PowerExtra P3 battery. I have had 3 other PowerExtra batteries that are now retired but two of them and this current one all have the same serial number probably because they are cloned. AirData allows me to rename the battery and separate them and doesn’t rely on the serial number but Flight Reader does not. Do you think this is what is causing the problem since AirData is displaying the battery info correctly.

I will contact Litchi but want to be sure first that it is not due to the generic battery that has a serial number the same as previous ones.

Chris

5

Nope. You can see the problem in my screenshot above – Litchi is populating battery cells that don’t exist. I cannot speak on behalf of Airdata, but I think it would be safe to say they aren’t using Litchi’s log data as-is.

This Flight Reader build will filter out the extra battery cells.

6

Ok, thanks for the reply. I will contact Litchi and see what they have to say.

Right now I am using both Flight Reader and AirData for my logs but once my subscription to AirData runs out in November, I will not be using it any more and will use Flight Reader exclusively.

Chris

1 Like
7

I ran the new build that you linked to above and reprocessed the logs that had battery cells that didn’t exist and it worked. Thank you very much.

In addition to your excellent Flight Reader software, the quick response to problems (that are not even due to the software) and solutions is another reason why I am going to be letting my AirData subscription lapse when it comes time to renew.

Chris

1 Like