Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Air 3 JSON results report bad coordinates #34

Open
mattman86 opened this issue Jan 7, 2025 · 4 comments
Open

Air 3 JSON results report bad coordinates #34

mattman86 opened this issue Jan 7, 2025 · 4 comments

Comments

@mattman86
Copy link

When trying to use the JSON results after decrypting a log file from an Air 3, the latitude and longitude values for some records are corrupted.

For example, instead of showing the correct latitude coordinate which should be around "39.157490424949813", it reports "-5.7972448339365584e+148".

@dji-dev
Copy link

dji-dev commented Jan 7, 2025

Agent comment from SHENRONG.LE in Zendesk ticket #126290:

Dear developers,

Hello, thank you for contacting DJI Innovation.

What log files are parsed? How did it happen?

Thank you for your email and have a nice life!

Best Regards,

DJI innovation SDK technical support

°°°

@mattman86
Copy link
Author

DJIFlightRecord_2025-01-06_[14-41-33].txt

Here is one of the logs that has the issue. It's from the latest DJI Fly app. Drone and controller firmwares are up to date.

@dji-dev
Copy link

dji-dev commented Jan 10, 2025

Agent comment from SHENRONG.LE in Zendesk ticket #126290:

Dear developers,

Hello, thank you for contacting DJI Innovation.

How did you parse this log? By what means is it analyzed?

Thank you for your email and have a nice life!

Best Regards,

DJI innovation SDK technical support

°°°

@mattman86
Copy link
Author

Hi, I ran the FlightRecordParser in Docker and opened the resulting json file in a text editor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants