• Home
    • Copter
    • Plane
    • Rover
    • Blimp
    • Sub
    • AntennaTracker
    • Mission Planner
    • APM Planner 2
    • MAVProxy
    • Companion Computers
    • Developer
  • Downloads
    • Mission Planner
    • APM Planner 2
    • Advanced User Tools
    • Developer Tools
    • Firmware
  • Community
    • Support Forums
    • Facebook
    • Developer Chat (Discord)
    • Developer Voice (Discord)
    • Contact us
    • Getting involved
    • Commercial Support
    • Development Team
    • UAS Training Centers
  • Stores
  • About
    • History
    • License
    • Trademark
    • Acknowledgments
    • Wiki Editing Guide
    • Partners Program
Rover Logo
  • Introduction
  • Autopilot Hardware Options
    • Open hardware
    • Closed hardware
      • Aerotenna Ocpoc-Zynq
      • Airvolute DroneCore
      • AtomRC F405-NAVI
      • Emlid NAVIO2 (Linux)
        • Specifications
        • What’s new compared to Navio+
        • For more details and purchase
      • Flywoo F745 AIO BL_32/ Nano
      • Foxeer Reaper F745-AIO V2
      • Furious FPV F-35 Lightning and Wing FC-10
      • Holybro Kakute F4*
      • Holybro Kakute F4 Mini*
      • Holybro Kakute F7 AIO*
      • Holybro Kakute F7 Mini* (only V1 and V2 are compatible)
      • Holybro Kakute H7 V2
      • Holybro Kakute H7 Mini v1.3
      • Holybro Pixhawk 4 Mini
      • Holybro Pixhawk5X
      • Horizon31 PixC4-Jetson
      • IFlight Beast F7 45A AIO
      • IFlight BeastH7 AIO
      • Mamba F405 MK2*
      • Mamba Basic F405 mk3
      • Mamba H743 v4
      • MakeFlyEasy PixSurveyA1
      • MakeFlyEasy PixPilot-V6
      • Mateksys F405 TE Family
      • Mateksys H743-Wing/MINI/SLIM/WLITE
      • ModalAI Flight core
      • mRo ControlZero F7
      • mRo Pixracer Pro (H7)
      • mRo Nexus
      • Omnibus F4 AIO/Pro*
      • OmnibusNanoV6
      • Omnibus F7V2*
      • Parrot C.H.U.C.K
      • RadioLink MiniPix
      • QioTek Zealot F427
      • QioTek Zealot H743
      • Sky-Drones AIRLink
      • SkystarsH7HD
      • SPRacing H7 Extreme
      • Swan-K1
      • SpeedyBee F4 (this board currently is non-verified)
      • SpeedyBee F4 V3
      • VR Brain 5
      • VR uBrain 5.1
    • Linux Based Autopilots
    • Firmware Limitations
    • Discontinued boards
    • Schematics
  • First Time Setup
  • First Drive and Tuning
  • If A Problem Arises
  • Rover Features
  • Advanced Configuration
  • Mission Planning
  • Logs
  • Peripheral Hardware
  • OEM Customization
  • Boats
  • Balance Bots
  • Sailboats
  • Walking Robots
  • Reference Frames
  • Use-Cases and Applications
  • Antenna Tracking
  • Simulation
  • User Alerts
  • Upcoming Features
  • Appendix
  • Full Table of Contents


Individual Partners SWAG Shop
Rover
  • »
  • Autopilot Hardware Options »
  • NAVIO2 Overview
  • Edit on GitHub

NAVIO2 Overview¶

This page presents Navio2 - Raspberry Pi autopilot, which runs well proven ArduPilot flight stack and supports all its features.

../_images/Navio2-features.jpg

Specifications¶

  • Processor (Raspberry PI 3)

    • 1.2GHz 64-bit quad-core ARMv8 CPU

    • 1GB RAM

  • Sensors

    • MPU9250 9DOF IMU

    • LSM9DS1 9DOF IMU

    • MS5611 Barometer

    • U-blox M8N Glonass/GPS/Beidou

    • RC I/O co-processor

  • Power

    • Triple redundant power supply

  • Interfaces

    • UART, I2C, ADC for extensions

    • PPM/S.Bus input

    • 14 PWM servo outputs

  • Dimensions

    • Weight 23g (shield) + 54g (RPi2)

    • Size: 55x65mm (shield only)

What’s new compared to Navio+¶

Dual IMU. Navio2 has two IMU chips to improve flight experience and for redundancy.

Improved MS5611 performance. Transactions from other chips on the bus, which MS5611 is connected to, can produce noise during the conversion. That’s why MS5611 was left the only sensor on the I2C bus to overcome this.

PCA9685 PWM generator replaced with a microcontroller. On previous Navio version PWM generation was handled by PCA9685 chip. Main limitation of this chip is the inability to control frequencies for separate channels. This leads to problems with motors and servos that work on different frequencies. To eliminate that problem a microcontroller is used. It allows to set frequencies for output channels by groups.

PPM/SBUS decoding done by microcontroller instead of DMA. Navio+ used DMA to sample PPM signal which was quite heavy on system resources. On Navio2 a microcontroller handles PPM/SBUS sampling leaving processor cores of Raspberry Pi 2 for your tasks.

AUX SPI. Navio2 is the first HAT to utilize AUX SPI controller on Raspberry Pi. Using two SPI controllers allows to distribute sensors more efficiently.

ADC port. Using additional ADC channels on Navio+ was not user friendly due to ADC channels being only available on pads at the bottom of the board. On Navio2 these channels are easily accessible on a DF13 port.

Better Linux integration. PWM, ADC, SBUS and PPM are integrated in Linux sysfs allowing for easy access from any programming language. Even deeper integration is coming in the future.

For more details and purchase¶

  • Emlid website

  • Navio2 documentation

  • Purchase page

Previous Next

Questions, issues, and suggestions about this page can be raised on the forums. Issues and suggestions may be posted on the forums or the Github Issue Tracker.

Creative Commons License© Copyright 2023, ArduPilot Dev Team.