Recent content by h-elsner

The program shows only that what is in the JSON files provided by the drone. I thing Vx, Vy, Vz and the angles come from Accelerometer/Gyro chip. You will see axis movement indirectly from the acc/gyro output values (on the Attitude tab), not the input in the AHRs system from the GPS/compass...

The project has moved from GitHub to Codeberg: https://codeberg.org/h-elsner/showanafilog The latest release is here: showanafilog

I think it is a bad (aged) battery that causes this incident. This 50% is not very telling. If the battery is aged it could have a higher internal resistance. This means the voltage is good (and so the display of the % capacity) but if higher current starts to flow the voltage breaks down and...

Filezilla and WinSCP uses FTP with TLS by default. You must select FTP without encryption (which is labeled with 'insecure'). Did you?

I would check what was the reason for this behavior before I start a new try. In the JSON flight logs we could see if it was a battery drop down or something else. There is also an information about the battery health in the FDR files. Also I would inspect the area for mobile network antennas...

If Parrot uses the same rules for battery serial number as it is used for drone serial then the dat is coded in the serial. The last 6 digits are serial, then there should be character than indicates the month (A=Jan to L=12). The digit left of that character shows the year 9 --> 2019, 0-->2020...

This not true. It's only valid for common RAM modules not for flash memory. Drones do have flash memory as well as the sensors like GPS. If power was off for a long time the calibration values and sensor BIAS are still there. I don't know if a true factory reset (which is a SW reset, done by...

Sorry, but the file you sent with #1 started with 65% Battery level and the first timestamp is 13:18:40.149. What you show in pictures is a later file we don't have. That's why I asked. This is from begin: And this is most important part: Here we can see the voltage drop I'm talking about...

If the file "drohneMontBlancchrash.json" that you provided in #1 is the one that shows the crash then it is different from that you have shown in the table in #6. Do you know which one is the relevant file? What I can see from the file in #1 is that there was a voltage drop shortly before there...

I don't have an Anafi. I do not exactly know where are the logs. I know the file names and maybe locations are different depending on firmware and app versions and the file names and locations are different depending on OS (Android or iOS) of the controller device. The FDR logs are on the SD...

The LINUX Version is also updated to V2.0 now. LINUX 64bit: http://h-elsner.mooo.com/downloads/ShowAnafiLog.tar.gz br HE

To solve confusion with log files I tried to sort it out. Comments / corrections are welcome.

Open your log files with a text editor to check. It has to be plain text in JSON format. Example: {"datas_1Hz":[{"product_battery_voltage":8309," ... and so on. I guess the files you are using are FDR log files. Those have another format. The file magic (the first 4 bytes in the file) of FDR...

Please give more information. What is not working? Which files? BlackBox or the old JSON files? Can I get an example file? For me it is working. br HE

It's still the same as #2. Windows64bit: http://h-elsner.mooo.com/downloads/ShowAnafiLog.zip More info of the project is here: https://github.com/h-elsner/showanafilog br HE