Need assistance review dji log file to determine root cause of errors

[EagkeOneUp]

The fly...csv is 56,757KB and wont upload to viewer here

I dont want to make public by attaching here

Would like help reviewing to see what root cause of the errors were ,

Automated waypoint type flight aborted and went to atti mode and was drifting

the error that aborted the flight was but seems other errors were happening before this

34612 [L-FDI]ns req:fdi.0to0.reason:fusion.gps_yaw_err.result:fail for same index

 

[msinger]

Which application did you use to generate that CSV file?

 

[EagkeOneUp]

Which application did you use to generate that CSV file?

log file extracted direct from drone using dji assistant

then used csvview to read the dat file and export as fly###.csv

I have the mappilot version of the logfile but its error info does not really contain what is being shown in the actual dji fly log file

 

[msinger]

then used csvview to read the dat file and export as fly###.csv

I don't know of any applications that can read those CSV files.

You can upload and view your TXT flight log online here. If you're familiar with reading flight logs, you might be able to find enough details in it to figure out what happened.

 

[EagkeOneUp]

I don't know of any applications that can read those CSV files.

You can upload and view your TXT flight log online here. If you're familiar with reading flight logs, you might be able to find enough details in it to figure out what happened.

not sure where I get the txt log file from

the dji error messages that mappilot provides are generic and do not show when uploaded to the phantom help viewer

Looking for someone that can review the dji log to determine what started the errors
( many years agio had someone do this to find a motor issue

 

[Meta4]

not sure where I get the txt log file from

1. Go to DJI Flight Log Viewer | Phantom Help
Follow the instructions there to upload your flight record from your phone or tablet.
That will give you a detailed report on the flight data.
Come back and post a link to the report it provides and someone might be able to analyse it and give you an understanding of the cause of the incident.
or
2. Just post the .txt file here

 

[EagkeOneUp]

Even when zipped , logfile is too large to attach here

1. Go to DJI Flight Log Viewer | Phantom Help
Follow the instructions there to upload your flight record from your phone or tablet.
That will give you a detailed report on the flight data.
Come back and post a link to the report it provides and someone might be able to analyse it and give you an understanding of the cause of the incident.
or
2. Just post the .txt file here

 

[EagkeOneUp]

1. Go to DJI Flight Log Viewer | Phantom Help
Follow the instructions there to upload your flight record from your phone or tablet.
That will give you a detailed report on the flight data.
Come back and post a link to the report it provides and someone might be able to analyse it and give you an understanding of the cause of the incident.
or
2. Just post the .txt file here

A One drive folder has been shared and visible for a few weeks
MapPilot log file
and
Fly141.csv direct from drone

can be viewed here

Microsoft OneDrive

1drv.ms

 

[EagkeOneUp]

Maybe this will be easier attached is the event log only

 

[EagkeOneUp]

I spent some time with an ai engine to analyze the flights logs that came from the drone itself, and had all available flights analyzed and got this report , about 26 flights

Flight 143 was the main concerned and it seems drone was not fully ready to fly , too much interference combined with batteries voltage drop

fly143.csv is the standout with 138 events of notEnoughForce

The peak heating was when I flew some flights in the upper 90's degrees F

previous flights were generating compass errors

An interesting call out in the attached report

The explicit osd_data:lowVoltage bit never tripped, yet we still observed deep sag in the raw pack values—so don’t rely solely on that flag; watch actual voltages and percentage.

 

[Oso]

I spent some time with an ai engine to analyze the flights logs that came from the drone itself, and had all available flights analyzed and got this report , about 26 flights

Flight 143 was the main concerned and it seems drone was not fully ready to fly , too much interference combined with batteries voltage drop

fly143.csv is the standout with 138 events of notEnoughForce

The peak heating was when I flew some flights in the upper 90's degrees F

previous flights were generating compass errors

An interesting call out in the attached report

The explicit osd_data:lowVoltage bit never tripped, yet we still observed deep sag in the raw pack values—so don’t rely solely on that flag; watch actual voltages and percentage.

It will be much easier and far more likely for you to get meaningful help if you would upload the correct flight log text file either here or to the viewer in the link provided earlier by msinger and meta4. As noted, the link also has instructions for finding the correct text file to get any help.

If you upload the txt file here, someone will then upload it to the viewer for analysis to help you.

If you upload the txt file directly to the viewer, simply post a link back here so people can see it and help you.

Cheers!

 

[EagkeOneUp]

It will be much easier and far more likely for you to get meaningful help if you would upload the correct flight log text file either here or to the viewer in the link provided earlier by msinger and meta4. As noted, the link also has instructions for finding the correct text file to get any help.

If you upload the txt file here, someone will then upload it to the viewer for analysis to help you.

If you upload the txt file directly to the viewer, simply post a link back here so people can see it and help you.

Cheers!

The map pilot pro log is at the one drive link but the errors mostly lost "Unknown" which is really useful
that is why I resorted to the full flight log from the drone it self , map pilot reviewed their log and didnt provide much help except the error cause the mission to abort and left drone in atti mode drifting

map pilot log and the full log form drone are here
uploading the map pilot log to the viewer here does not shows the errors map pilot was recording
there are no other logs available to retrieve for this flight , I have the down load from air data but is the same log as the map pilot pro log file
dji app was not used for this flight so there is no log to extract there
Map pilot pro has not produced the SDK log files for a few years now

I have gotten all the log files available that the link (PhantomHelp ) advises of
This flight log viewer is able to decrypt and view flight data inside of the following types of flight logs:

• TXT flight logs created by DJI GO/Fly/Pilot or other apps that use the DJI SDK *** APP NOT USED **
• CSV flight logs created by Drone Harmony, Litchi, or Map Pilot ** THE MAP PILOT LOG FILES HAS BEEN PUBLISHED HERE *** and does not upload without timeouts to the log viewer here at phantom help this is way it is available at the onedrive link - The main error in this logfile states *** Unknown *** which uis why I reverted to the fly143.dat / csv file
  
  

Microsoft OneDrive

1drv.ms

 

[Meta4]

Would like help reviewing to see what root cause of the errors were ,
Automated waypoint type flight aborted and went to atti mode and was drifting

Sorry, I can't help much.
The data doesn't have enough information to tell what was going on with GPS.
What's there is confusing.

The Map Pilot CSV file has the data that would usually be used to investigate flight incidents.
When opened in the Phantomhelp log viewer, it shows most of the flight details, but it's hard to make sense of the GPS data.
It shows that a sufficient number of satellites have been acquired with no abnormal reductions in number of sats during the flight.
But it also shows the GPS reliability as zero for the whole flight and the flight mode as Atti Hover - a flight mode that I've never seen before.

But the drone cannot have been in Atti Mode as it's managed to fly the precise grid pattern as programmed and the location of the drone has been continuously updated throughout the flight.
This would be impossible without GPS.

After 10 minutes of flying the automated mission there is a message saying: transitioned to ManualMission / Switched PSA. Exited Programmed Flight.
After that the drone is brought back and landed about 100 ft north of the start point.

 

[EagkeOneUp]

Sorry, I can't help much.
The data doesn't have enough information to tell what was going on with GPS.
What's there is confusing.

The Map Pilot CSV file has the data that would usually be used to investigate flight incidents.
When opened in the Phantomhelp log viewer, it shows most of the flight details, but it's hard to make sense of the GPS data.
It shows that a sufficient number of satellites have been acquired with no abnormal reductions in number of sats during the flight.
But it also shows the GPS reliability as zero for the whole flight and the flight mode as Atti Hover - a flight mode that I've never seen before.

But the drone cannot have been in Atti Mode as it's managed to fly the precise grid pattern as programmed and the location of the drone has been continuously updated throughout the flight.
This would be impossible without GPS.

After 10 minutes of flying the automated mission there is a message saying: transitioned to ManualMission / Switched PSA. Exited Programmed Flight.
After that the drone is brought back and landed about 100 ft north of the start point.

Something did happen not sure what it was able to fly with gps but then aborted mission and went into atti mode

right before the abort the drone did a weird maneuver, not sure of that was gps or compass related

seems something was not quite right at takeoff that just compounded until the mission aborted , the low battery voltage may have contributed to the the worsening

but some tool I used show the IMU thought is was at a different position that what gps was showing for the beginning of the flight but later caught up to match

I always power on and review the dji app before going to map pilot but nothing was showing amiss , unless it was something minor that is difficult to notice .

I appreciate you taking the time to review.

The data available in the map pilot log was not enough thats why I reverted to the "complex" dji flight log from the drone
reviewing previous flights I think this battery with it cell dropping to quickly compounds the issue, as the last couple of flights with the same battery had lots of errors but the drone was able to complete the mission and return home properly

needless to say that battery will not be used for flight anymore

 

[BudWalker]

@EagkeOneUp if you want help determining the cause of the incident please provide the original .DAT via a public sharing site. I've had some experience looking at .DAT log files and may be able to help.