Datalogs are generated locally on the autopilot while armed and can be downloaded after flight from the the GCS.

The authoritative source for the datalogs (including details about each type of log entry) is available ​here

Here is a list of log entries to check after a flight:

• first check the log for errors (search for ERR in the text file). If any found, check ​this page for the codes.

• GPS:
  • check GPS number of satellites (!NSats under GPS) - ideally not under 9
  • if GPS number of satellites <9 check the Dilution of precision (!HDop) ideally under 2 - if larger, it may be the cause of GPS errors

• Barometer:
  • Check the barometric altitude (BarAlt in CTUN) - compare with GPS altitude (RelAlt under GPS) - if very different, possible GPS precision loss.

• Voltage:
  • Check the battery voltage (Volt under CURR) - make sure it's larger than 3.2*cells (9.6V for 3S)
  • Check the VCC voltage (Vcc under CURR) - make sure it's larger than 4.8V
  • Check the current (Curr under CURR) ( readings - likely incorrect in absolute value due to impossibility of calibration, but potentially interesting in relative values).

• Stability Issues:
  • Check the Roll vs RollIn (ATT Roll and ATT RollIn) - should be tracking each other closely.
  • Repeat for Pitch and PitchIn (ATT Pitch and ATT PitchIn)
  • Can check against Accelerations from the IMU (ATT/Roll vs IMU/AccY and ATT/Pitch/AccX) for oscillations - each pair should have the same phase

• Navigation:
  • If Navigation (Auto, Loiter, RTL) seems to be a problem - check INAV entries as well as NTUN.

• Performance Monitoring:
  • Check PM/RenCnt - should be 0 throughout
  • Check PM/RenBLW:DCM - should be 0 throughout
  • Check PM/NLon: should be... no more than 50 - 200
  • Check PM/NLoop: should be >900