PX4 logs detailed aircraft state and sensor data, which can be used to analyze performance issues. This topic explains how you can download and analyse logs, and share them with the development team for review.
Keeping flight logs is a legal requirement in some jurisdictions.
Upload the log file to the online Flight Review tool (http://logs.px4.io). After upload you'll emailed a link to the analysis page for the log.
Log Analysis using Flight Review explains how to interpret the plots, and can help you to verify/reject the causes of common problems: excessive vibration, poor PID tuning, saturated controllers, imbalanced vehicles, GPS noise, etc.
There are many other great tools for visualising and analysing PX4 Logs. For more information see: Flight Analysis.
If you have a constant high-rate MAVLink connection to the vehicle (not just a telemetry link) then you can use QGroundControl to automatically upload logs directly to Flight Review. For more information see Settings > MAVLink Settings > MAVLink 2 Logging (PX4 only).
The logging system is configured by default to collect sensible logs for use with Flight Review.
Logging may further be configured using the SD Logging parameters. The parameters you are most likely to change are listed below.
|Logging Mode defines when logging starts and stops.
0: log when armed until disarm (default).
1: log from boot until disarm.
2: log from boot until shutdown.
|Logging profile. Use this to enable less common logging/analysis (e.g. for EKF2 replay, high rate logging for PID & filter tuning, thermal temperature calibration).
|Create very small additional "Mission Log".
This log can not be used with Flight Review, but is useful when you need a small log for geotagging or regulatory compliance.