Skip to main content

Troubleshooting

Troubleshooting​

This section lists common issues encountered during setup and operation of JTA-01, along with likely causes and recommended corrective actions. Most problems can be resolved through systematic checks rather than hardware replacement.

JTA-01 Does Not Power On​

Symptoms​

  • No LEDs illuminate
  • No buzzer tones
  • Board not detected over USB

Possible Causes​

  • No power applied
  • Incorrect polarity
  • Faulty power source or cable

Corrective Actions​

  • Verify power source voltage and polarity
  • Check power connector seating
  • Try powering via USB for verification
  • Replace power cable if necessary

⚠️ Warning
If the board does not power on via USB, discontinue use and inspect wiring.

USB Not Detected by Computer​

Symptoms​

  • No new device appears when USB is connected
  • Ground control software cannot find JTA-01

Possible Causes​

  • Faulty USB cable
  • Insufficient power
  • USB port issue

Corrective Actions​

  • Try a known good USB cable
  • Use a different USB port
  • Power JTA-01 through the primary power input and retry
  • Restart the ground control software

ℹ️ Note
Avoid using USB hubs during troubleshooting.

Firmware Flashing Fails​

Symptoms​

  • Firmware upload does not complete
  • Board enters recovery mode repeatedly

Possible Causes​

  • Interrupted power or USB connection
  • Incompatible firmware selection

Corrective Actions​

  • Power-cycle JTA-01
  • Retry flashing using USB
  • Use bootloader recovery method
  • Ensure firmware supports Pixhawk FMU v6x RT

⚠️ Warning
Do not interrupt power during firmware flashing.

Sensors Will Not Calibrate​

Symptoms​

  • Calibration fails repeatedly
  • Calibration results are inconsistent

Possible Causes​

  • Board not mounted securely
  • Movement during calibration
  • Excessive vibration or magnetic interference

Corrective Actions​

  • Secure the vehicle on a stable surface
  • Keep the system completely still during calibration
  • Move to a low-interference environment
  • Reboot and retry calibration

GPS Not Detected or No Fix​

Symptoms​

  • GPS not recognized
  • Satellite count remains low
  • No 3D fix achieved

Possible Causes​

  • Incorrect wiring
  • Poor GPS placement
  • Electromagnetic interference

Corrective Actions​

  • Verify GPS connector and pinout
  • Relocate GPS away from power electronics
  • Allow additional time for first fix
  • Perform test outdoors with clear sky view

Compass Errors or Unstable Heading​

Symptoms​

  • Yaw instability
  • Compass warnings
  • Incorrect heading

Possible Causes​

  • Magnetic interference
  • Incorrect compass orientation
  • Improper calibration

Corrective Actions​

  • Recalibrate compass in a clean environment
  • Move compass away from power wiring
  • Verify compass orientation settings

ℹ️ Note
Compass issues are often caused by wiring changes made after calibration.

Motors Do Not Spin When Armed​

Symptoms​

  • Vehicle arms but motors do not respond
  • Output test shows no movement

Possible Causes​

  • ESCs not powered
  • Incorrect output configuration
  • Safety switch or kill switch active

Corrective Actions​

  • Verify ESC power supply
  • Check motor output assignments
  • Confirm no safety or emergency stop is engaged
  • Re-test outputs without propellers

Vehicle Will Not Arm (Arming Denied)​

Symptoms​

  • “Arming denied” message in ground control software

Common Causes​

  • Sensors not calibrated
  • RC signal missing
  • Battery voltage below threshold
  • GPS required but not available

Corrective Actions​

  • Review pre-arm messages carefully
  • Resolve each reported issue
  • Do not bypass arming checks unless necessary

ℹ️ Note
Pre-arm messages are diagnostic tools—always address them directly.

Unexpected Failsafe Activation​

Symptoms​

  • Sudden mode change
  • Automatic landing or RTL

Possible Causes​

  • RC signal loss
  • Battery voltage drop
  • GPS loss

Corrective Actions​

  • Review flight logs
  • Verify failsafe thresholds
  • Inspect power delivery system

ℹ️ Note
Failsafe behaviour should always be reviewed using logs.

When to Stop and Inspect Hardware​

Discontinue operation and inspect hardware if:

  • Board overheats
  • Smell of burnt electronics is detected
  • Physical damage is visible
  • Repeated unexplained failures occur

⚠️ Warning
Do not continue testing if hardware damage is suspected.

Troubleshooting Philosophy​

Effective troubleshooting with JTA-01 follows three principles:

  • Change only one variable at a time
  • Verify with logs whenever possible
  • Do not ignore warnings

Most issues are configuration or integration related rather than hardware failures.