Automate Log Collection for Your ArduPilot Drone Fleet
ArduPilotdrone loggingUAV automationdata analysis

Automate Log Collection for Your ArduPilot Drone Fleet

LogHat Engineering TeamJune 14, 20265 min read

Key Takeaway

Automate log collection for your ArduPilot drone fleet to enhance flight analysis.

TL;DR: To automate log collection for your ArduPilot drone fleet, ensure your logs are configured correctly with BATT_FS_LOW_ACT=1 for battery failsafe or FS_THR_ENABLE=1 for throttle failsafe. This setup allows seamless data logging and retrieval for flight analysis.

What ArduPilot Log Collection Automation Actually Is

ArduPilot log collection automation involves the systematic gathering of flight data from your UAVs without manual intervention. This process is crucial for effective flight analysis and troubleshooting. The primary log message categories include:

ERR Subsys  ECode  TimeUS  LogType  Message
  • ERR Subsys: Indicates the error subsystem (e.g., 18 for barometer issues).
  • ECode: The specific error code associated with the subsystem.
  • TimeUS: Timestamp of the log entry in microseconds.
  • LogType: Type of log message (e.g., error, message).
  • Message: Descriptive text detailing the log entry.
Understanding log collection is vital for effective drone fleet management.

Confirming It in Mission Planner

To confirm log collection settings in Mission Planner, follow this sequence:

  1. Open Mission Planner and connect to your drone.
  2. Navigate to Flight DataDataFlash LogsReview a Log.

In the log review window, consider plotting the following fields for comprehensive analysis:

  • ERR: To identify any logged errors.
  • GPS.Status: To check for GPS fix quality.
  • BAT: To monitor battery levels during flight.
Utilizing Mission Planner allows for a detailed inspection of flight logs to streamline troubleshooting.

Confirming It in MAVExplorer

MAVExplorer provides a powerful interface for analyzing flight logs. To visualize log data, you can run the following command:

MAV> graph ERR.Subsys GPS.Status

This command generates a plot that shows the relationship between error subsystems and GPS status, helping to identify any correlation between data quality and logged errors.

MAVExplorer enhances log analysis with effective visualizations, aiding in prompt issue detection.

Why Automation of Log Collection Is Needed — Ranked by What We See Most Often

  1. Manual errors in data collection: Reliance on manual log retrieval often leads to missed or incomplete data. Automating this process ensures consistency.
  2. Increased operational scale: As drone fleets grow, managing logs manually becomes impractical. Automation scales seamlessly with fleet size.
  3. Timeliness of data analysis: Automated logs can be collected and analyzed quickly, allowing for immediate troubleshooting of issues as they arise.
Understanding the reasons for automation helps justify the implementation of effective log collection systems.

Fixes for Log Collection Issues

  1. Set BATT_FS_LOW_ACT=1 to enable battery failsafe actions.
  2. Enable throttle failsafe by configuring FS_THR_ENABLE=1.
  3. Utilize sd2log for storing logs on an SD card for easy retrieval.
Specific parameter adjustments can significantly improve log collection reliability and functionality.

When This Isn't Actually Log Collection Automation

  • Logs may not be collected if the drone is not powered on or connected properly.
  • Issues with SD card formatting can prevent logs from being stored correctly.
  • Faulty hardware may lead to inaccurate log data being collected.
By understanding these conditions, you can better troubleshoot issues that may arise outside of log collection automation.

When LogHat Helps — and When It Doesn't

LogHat excels in providing a comprehensive analysis of the flight logs collected, highlighting errors and trends based on real data. However, it does not handle the initial collection of logs from the drone itself. For effective use, ensure your log collection systems are fully operational before analysis.

Using LogHat in conjunction with robust log collection mechanisms enhances overall flight operation efficiency.
``` ```json { "seo_meta": { "faq": [ { "q": "How do I access the logs from my ArduPilot?", "a": "Connect via Mission Planner and navigate to the Data Flash Logs tab to download your logs." }, { "q": "What types of data can I log with ArduPilot?", "a": "You can log various telemetry data, including sensor readings and error messages, by configuring the logging settings." }, { "q": "What is the purpose of automated log collection?", "a": "Automated log collection ensures consistent data retrieval, reducing manual errors and improving fleet management." }, { "q": "How can I troubleshoot log collection failures?", "a": "Check the drone's power status, SD card formatting, and hardware connections to ensure logs are collected properly." }, { "q": "Can I use LogHat for log analysis?", "a": "Yes, LogHat provides tools for analyzing flight logs, identifying errors, and optimizing performance." } ] } }

About the author

LE

LogHat Engineering Team

The LogHat engineering team — drone-systems engineers who build and operate the LogHat flight analytics platform. Posts in this byline are written and reviewed by team members working on the parsers, analysis engine, and Vector AI that the post describes.

Tagged

ArduPilotdrone loggingUAV automationdata analysis

Try LogHat

Analyze your flight logs in seconds

Upload a .bin, .tlog, .log, or .ulg file. Get AI crash analysis, 3D replay, and forensic PDF reports instantly.

Try LogHat Free