Convert your flight logs with Litchi

It's saved to the internal storage, so you should still have them, you don't need an external sdcard.
 
  • Like
Reactions: JeffDV50
It's saved to the internal storage, so you should still have them, you don't need an external sdcard.
I found flight record within the DJI Pilot app. It shows a photo with the moving arrow icon going until where the P3 crashed on the roof. I uploaded to Dropbox - the files show as .jpg... What am I doing wrong here as surely you can't get anything off of a .jpg
 
This s a great way to analyse your flights , battery performance, aging etc. But as it stands too many parameters are still missing. Hopefully they are in the txt log.
There is a LOT more data, but I need time to add it!
 
There is a LOT more data, but I need time to add it!

Kaehn, you are my new best friend. I'm a flight logger dashware freak.

If it's not too much trouble, can you toss up a list of all the possible Data Categories the P3 has the ability to log? Or.. Please explain where I can find that info as well as a possible brief description of what each data category is associated with?

*My definition of "Data Categories" below.

(Data Categories are the names above each column of rows. Some examples are: longitude, latitude, speed mph, distance, and so on...)
 
Luap, you don't know anything about dashware, do you.

Good to see you in the mix........


You can also do some fun stuff in Dashware.
That was flying my P2V (using another conversion app).
 
Battery Common:
  • part voltages x6
  • product date
  • ConnStatus
  • current
  • currentcapacity
  • currentPV
  • errorType
  • fullCapacity
  • life
  • loopNum
  • relativeCapacity
  • serialNo
  • temperature
  • lastStudyCycle
  • totalStudyCycle
Deform Status:
  • deformMode
  • deformStatus
  • isDeformProtected
Smart Battery:
  • goHomeBattery
  • goHomeCountDown
  • goHomeStatus
  • goHomeTime
  • landBattery
  • landTime
  • lowWarning
  • lowWarningGoHome
  • safeFlyRadius
  • seriousLowWarning
  • seriousLowWarningLanding
  • status
  • usefulTime
  • voltage
  • volumeConsume
Gimbal Params:
  • pitch
  • roll
  • rollAdjust
  • version
  • yaw
  • yawAngle
  • isAutoCalibration
  • autoCalibrationResult
OSD Common:
  • canIOCWork
  • compassError
  • flightAction
  • flyTime
  • flycState
  • flycVersion
  • gohomeStatus
  • gpsLevel
  • gpsNum
  • height
  • imu_initfail_reason
  • latitude
  • longitude
  • modeChannel
  • motorStartFailedCause
  • motorRevolution
  • nonGpsCause
  • pitch
  • rcState
  • roll
  • swaveHeight
  • voltageWarning
  • waveError
  • xSpeed
  • ySpeed
  • yaw
  • zSpeed
  • groundOrSky
  • isAcceletorOverRange
  • isBarometerDeadInAir
  • isImuPreheatd
  • isMotorUp
  • isSwaveWork
  • isVibrating
  • isVisionUsed
OSD Home:
  • aircraftHeadDirection
  • compassCeleStatus
  • dataRecorderStatus
  • gohomeHeight
  • gohomeMode
  • gohomeStatus
  • height
  • IOC mode
  • latitude
  • longitude
  • hasGoHome
  • isBeginnerMode
  • isCompassCeleing
  • isDynamicHomePointEnable
  • isHomeRecord
  • isIOCEnabled
  • isMultipleModeOpen
  • isReachLimitDistance
  • isReachLimitHeight
RC GPS:
  • gpsNum
  • gpsStatus
  • latitude
  • longitude
  • xSpeed
  • ySpeed
RC Params:
  • aileron
  • custom1
  • custom2
  • elevator
  • gyroValue
  • recordStatus
  • rudder
  • shutterStatus
  • throttle

There is also some summary data about the flight (e.g. city, street, substreet, appVersion, firmware versions and more).
 
Battery Common:
  • part voltages x6
  • product date
  • ConnStatus
  • current
  • currentcapacity
  • currentPV
  • errorType
  • fullCapacity
  • life
  • loopNum
  • relativeCapacity
  • serialNo
  • temperature
  • lastStudyCycle
  • totalStudyCycle
Deform Status:
  • deformMode
  • deformStatus
  • isDeformProtected
Smart Battery:
  • goHomeBattery
  • goHomeCountDown
  • goHomeStatus
  • goHomeTime
  • landBattery
  • landTime
  • lowWarning
  • lowWarningGoHome
  • safeFlyRadius
  • seriousLowWarning
  • seriousLowWarningLanding
  • status
  • usefulTime
  • voltage
  • volumeConsume
Gimbal Params:
  • pitch
  • roll
  • rollAdjust
  • version
  • yaw
  • yawAngle
  • isAutoCalibration
  • autoCalibrationResult
OSD Common:
  • canIOCWork
  • compassError
  • flightAction
  • flyTime
  • flycState
  • flycVersion
  • gohomeStatus
  • gpsLevel
  • gpsNum
  • height
  • imu_initfail_reason
  • latitude
  • longitude
  • modeChannel
  • motorStartFailedCause
  • motorRevolution
  • nonGpsCause
  • pitch
  • rcState
  • roll
  • swaveHeight
  • voltageWarning
  • waveError
  • xSpeed
  • ySpeed
  • yaw
  • zSpeed
  • groundOrSky
  • isAcceletorOverRange
  • isBarometerDeadInAir
  • isImuPreheatd
  • isMotorUp
  • isSwaveWork
  • isVibrating
  • isVisionUsed
OSD Home:
  • aircraftHeadDirection
  • compassCeleStatus
  • dataRecorderStatus
  • gohomeHeight
  • gohomeMode
  • gohomeStatus
  • height
  • IOC mode
  • latitude
  • longitude
  • hasGoHome
  • isBeginnerMode
  • isCompassCeleing
  • isDynamicHomePointEnable
  • isHomeRecord
  • isIOCEnabled
  • isMultipleModeOpen
  • isReachLimitDistance
  • isReachLimitHeight
RC GPS:
  • gpsNum
  • gpsStatus
  • latitude
  • longitude
  • xSpeed
  • ySpeed
RC Params:
  • aileron
  • custom1
  • custom2
  • elevator
  • gyroValue
  • recordStatus
  • rudder
  • shutterStatus
  • throttle

There is also some summary data about the flight (e.g. city, street, substreet, appVersion, firmware versions and more).
Yep, gonna need a glossary. Good to have info.
 
My suggestion would be to set this current logger at 250 milliseconds. Most that use it would be satisfied with 1000ms. I'm personally into High Speed Flights where I attempt to set personal records at moment. Plans are to put something together worldwide eventually. But I'm content with 250ms.

Right now I'd say this data is coming straight off the phantom and for my device it was at 100ms which as you know is 10 lines of data for every 1 second.

One thing that concerns me is when we begin adding additional Categories of data, it will surely begin to have some effect on the software(sdk) being used, such as your app. Pilots may begin reporting missing data, or small sections of 0's.

Btw, I'd be glad to help support you in this or any other similar area should you need it.
 
Last edited:
Kaehn, just curious but did you take that info from the new DJI version 2.0 SDK?
 
Yes
 
Do you think all the those data categories are stored in the txt file and are you using the SDK to extract them?
Some sound quite interesting like motor revolution (wonder if that's per motor) the Battery Common as well as the RC Params.
 
They are all in the DJI Pilot logs.
 
Kaehn, will you be beta testing for the P3 anytime soon?

Btw, I have your current app but with the P3 here now I have no interest in P2.
 
anyone find the log files in iOS yet? P3 is coming tomorrow and I'm just looking for something to occupy my mind in the mean time...
 
  • Like
Reactions: Thibodaux Man
Hey guys!
ps: we renamed our P2 app, hope you like the new name!

Curious why would you rename a radio controlled, multi-rotor, quadcopter app to a name of a fruit? If I was looking for apps to use with my quad I sure wouldn't plug in a name of a fruit.
 
  • Like
Reactions: F6Rider

Recent Posts

Members online

No members online now.

Forum statistics

Threads
143,086
Messages
1,467,527
Members
104,965
Latest member
Fimaj