Automate Log Collection for Your ArduPilot Fleet in Minutes

TL;DR: For effective ArduPilot log collection automation, monitor ERR Subsys=18 for EKF primary changes and set the LOG_BACKEND_TYPE parameter to 1 for SD logging. This setup ensures you can quickly collect and analyze flight logs across your fleet.

What ArduPilot Log Collection Automation Actually Is in the Log

ArduPilot log collection involves capturing flight data to analyze performance and troubleshoot issues. The log messages provide insights into various parameters affecting the drone's behavior.

LOG  TimeUS  Instance  Altitude  Speed  Throttle  Battery

• TimeUS: Timestamp of the log entry in microseconds.
• Instance: The logging instance number.
• Altitude: Current altitude above sea level.
• Speed: Horizontal speed of the drone.
• Throttle: Throttle output as a percentage.
• Battery: Remaining battery percentage.

Confirming It in Mission Planner

To confirm logging settings in Mission Planner, follow these steps:

• Open Mission Planner.
• Navigate to Initial Setup → Optional Hardware → Log Config.
• Ensure LOG_BACKEND_TYPE is set to 1 for SD logging.
• Go to Flight Data → DataFlash Logs → Review a Log to view collected logs.

When reviewing logs, plot the following fields for better visibility:

• Alt: To observe altitude changes during the flight.
• Throttle: To evaluate throttle management.
• Battery: To monitor battery performance.

Confirming It in MAVExplorer

To analyze logs in MAVExplorer, use the following command:

MAV> graph LOG.Altitude LOG.Throttle

This command will plot altitude against throttle output, helping you visualize the relationship between these critical parameters during flight.

Why Log Collection Automation Happens — Ranked by What We See Most Often

1. Insufficient storage: Logs may not be collected if the SD card is full. Ensure ample space is available for new logs.
2. Configuration errors: Incorrect settings in LOG_BACKEND_TYPE prevent logs from being saved. Verify that it's set to 1 for SD logging.
3. Power interruptions: Power loss during flight can cause incomplete logs. Ensure battery health is monitored and maintained.
4. Firmware issues: Bugs in specific ArduPilot versions may affect logging. Keeping firmware updated can mitigate this risk.
5. Hardware incompatibility: Some logging hardware may not be compatible with ArduPilot. Always check compatibility before deployment.

Fixes for Log Collection Issues

1. Set LOG_BACKEND_TYPE = 1 to enable SD card logging.
2. Ensure the SD card is formatted correctly and has sufficient space.
3. Regularly check battery health to avoid power interruptions.
4. Update to the latest ArduPilot firmware to avoid known bugs.
5. Double-check the compatibility of logging hardware with ArduPilot.

When This Isn't Actually Log Collection Automation

• Log loss may not indicate configuration issues; it can also stem from physical damage to logging hardware.
• Incomplete logs can occur due to firmware bugs, but this does not always reflect a setup issue.
• Battery-related issues may cause log collection interruptions, but they can be unrelated to the logging setup itself.

When LogHat Helps — and When It Doesn't

LogHat excels in analyzing logs from your ArduPilot fleet, identifying patterns, and providing insights based on historical data. However, it does not automate the initial collection process; maintaining proper logging settings and hardware setup remains your responsibility.