Every ArduPilot flight records a detailed log: what the pilot commanded, what the drone did, what every sensor measured and how the battery behaved. Learning to read these logs is the fastest way to find problems, tune your drone and understand crashes. In this beginner’s guide we explain how to read ArduPilot logs, which messages to check first and what normal and abnormal values look like.
Two kinds of logs
- Dataflash logs (.bin files): recorded on the flight controller’s SD card or flash chip. These are the detailed logs you will use most.
- Telemetry logs (.tlog files): recorded by the ground station from the telemetry link. They contain less detail and depend on the radio link quality.
For troubleshooting, always use the .bin dataflash log when you can.
How to download a log
- Connect the flight controller to Mission Planner by USB.
- Open the Data screen and the DataFlash Logs tab.
- Click Download DataFlash Log Via Mavlink and choose the flight you want (usually the latest).
- Click Review a Log and open the downloaded .bin file.
Other tools can also open ArduPilot logs, including web-based log viewers and plotting tools. The messages are the same whichever tool you use.
How logs are organized
A log is a list of messages, each with several fields. For example, the BAT message contains fields such as Volt (voltage) and Curr (current). In the log viewer you tick the fields you want and they appear as lines on a graph over time.
The first five things to check
1. Vibration (VIBE)
Plot VIBE.VibeX, VibeY and VibeZ. These show vibration on each axis. Low, steady values are good. Also check VIBE.Clip fields: they count how often vibration was so strong it exceeded the accelerometer’s range. Clipping that keeps increasing is a serious warning. The ArduPilot documentation lists recommended limits. If vibration is high, see our guide Drone Vibration: Causes and Fixes.
2. Attitude tracking (ATT)
Plot ATT.DesRoll against ATT.Roll, and the same for pitch and yaw. “Des” is what the flight controller wanted; the other is what actually happened. On a well-tuned drone the two lines follow each other closely. Large or growing differences point to tuning, motor or mechanical problems.
3. Battery (BAT)
Plot BAT.Volt and BAT.Curr. Voltage should fall smoothly during the flight, with small dips when you add throttle. Deep, sudden voltage sag under load suggests a weak or undersized battery. The average current helps you calculate flight time: see How Long Can a Drone Fly?
4. Motor outputs (RCOU)
Plot the motor output channels, for example RCOU.C1 to C4 on a quad. In a steady hover they should be at similar levels. If one motor is always much higher or lower than the others, the drone may be unbalanced, have a weak motor or a twisted motor mount. Outputs hitting maximum mean the drone is running out of power.
5. GPS and position (GPS)
Check GPS.NSats (number of satellites) and GPS.HDop (a measure of position quality; lower is better). A sudden drop in satellites or jump in HDop often explains poor position hold. See our GPS module guide for mounting tips.
Other useful messages
| Message | What it shows | Use it to check |
|---|---|---|
| MODE | Flight mode changes | When the pilot or a failsafe changed mode |
| ERR | Errors and failsafe events | Radio loss, battery failsafe, sensor errors |
| EV | Events such as arming and disarming | The timeline of the flight |
| CTUN | Altitude and throttle control | Altitude hold and climb behaviour |
| RCIN | Pilot stick inputs | What the pilot actually commanded |
| MAG | Compass readings | Interference from motors and power wires |
| BARO | Barometric altitude | Altitude noise from prop wash or wind |
| XKF / NKF messages | EKF (position estimator) data | Estimator health and innovations |
A simple crash investigation routine
- Find the moment of the problem using
MODE,ERRandEVmessages. - Check the pilot inputs (
RCIN) to see if the drone did what it was told. - Compare desired and actual attitude (
ATT). If they separate suddenly, something mechanical or electrical probably failed. - Check motor outputs (
RCOU). One motor going to maximum while the drone still tilts often means that motor, its ESC or its propeller failed. - Check battery voltage and current for sudden drops or brownouts.
- Check vibration and GPS for anything unusual just before the event.
Tips for better logs
- Use a good-quality SD card if your board has one, and format it occasionally.
- Keep logging enabled while disarmed only if you need it; it creates many large files.
- Write down what happened in each flight so you can match notes with the logs.
- Save logs from good flights too. Comparing a good log with a bad one makes problems easier to see.
Frequently asked questions
Where are ArduPilot logs stored?
On the flight controller’s SD card or onboard flash chip, as .bin files. You can download them over USB with Mission Planner or another ground station.
What is the most important thing to check in a log?
Vibration. High vibration causes many other problems, so check the VIBE message first after any unusual flight.
Why does my drone not have any logs?
Logging may be disabled, the SD card may be missing or faulty, or the board may log only while armed. Check the logging parameters and the SD card.
Can logs tell me why my drone crashed?
Very often, yes. Comparing desired and actual attitude, motor outputs, battery voltage and error messages usually shows whether the cause was mechanical, electrical, a setting or a pilot input.