Skip to main content

Logging and Diagnostics

This section explains how flight logs and diagnostic data are generated, retrieved, and interpreted on JTA-01. Logging is essential for validating system health, analysing flight behaviour, and troubleshooting issues.

Purpose of Logging​

JTA-01 continuously records internal system data to enable:

  • Post-flight analysis
  • Detection of sensor or power issues
  • Verification of failsafe behaviour
  • Performance tuning

Logs provide objective data and should always be reviewed after:

  • First flight
  • Hardware or configuration changes
  • Unexpected flight behaviour

Logging Mechanism​

JTA-01 supports onboard data logging using removable or internal storage, depending on configuration.

Typical Logged Data Includes​

  • IMU sensor data
  • Attitude and position estimates
  • RC input values
  • Actuator outputs
  • Battery voltage and current
  • Failsafe and system events

Logging begins automatically when:

  • The system is armed, or
  • As defined by firmware configuration

Enabling and Verifying Logs​

In most configurations, logging is enabled by default.

Verification Steps​

  • Insert the supported storage medium (if required)
  • Power up JTA-01
  • Arm and disarm the system
  • Power down and remove storage
  • Verify log files are present

If logs are not created:

  • Check storage formatting
  • Verify logging parameters
  • Ensure storage is fully seated

Retrieving Logs​

Logs can be retrieved using one of the following methods.

Via Ground Control Software​

  • Connect JTA-01 via USB or telemetry
  • Navigate to the log download section
  • Select and download the required logs

Via Storage Medium​

  • Power down JTA-01
  • Remove the storage medium
  • Insert it into a computer
  • Copy log files for analysis

Log Review and Analysis​

Logs should be reviewed using compatible analysis tools.

Key Items to Review​

  • Sensor consistency and noise levels
  • Vibration indicators
  • Battery voltage sag under load
  • RC input stability
  • Failsafe triggers

ℹ️ Note
Regular log review helps identify issues before they become critical failures.

System Health Indicators​

Ground control software provides real-time system health information.

Common Health Indicators​

  • Sensor status (OK / warning / error)
  • GPS fix and accuracy
  • Battery status
  • Communication link quality

⚠️ Warning
Warnings should never be ignored, even if flight appears normal.

Vibration Monitoring​

Excessive vibration affects:

  • IMU accuracy
  • Control stability
  • Navigation performance

Diagnostic Indicators​

  • High-frequency noise in IMU data
  • Elevated vibration metrics in logs
  • Oscillatory attitude behaviour

Corrective Actions​

  • Improve vibration isolation
  • Balance propellers
  • Secure cables and components

Using Logs for Troubleshooting​

Logs are the primary tool for diagnosing:

  • Unexpected arming failures
  • Unstable flight behaviour
  • Power-related shutdowns
  • Sensor dropouts

Troubleshooting Guidelines​

  • Analyse logs immediately after the event
  • Avoid making multiple changes at once
  • Re-test after each correction

Logging Best Practices​

To maximize diagnostic value:

  • Keep logging enabled at all times
  • Label and archive logs by date and configuration
  • Review logs regularly, not only after failures
  • Compare logs across flights to detect trends

ℹ️ Note
Consistent logging practices significantly improve system reliability and safety.