Difference between revisions of "Category:Autopilots"

From PaparazziUAV
Jump to navigation Jump to search
 
(2 intermediate revisions by 2 users not shown)
Line 7: Line 7:
|{{P Header Box|ico=Autopilot.png|Paparazzi Autopilots}}
|{{P Header Box|ico=Autopilot.png|Paparazzi Autopilots}}


Hardware support for Autopilot versions currently in use.
One of the great advantages of Paparazzi is support for many hardware designs. There is autopilot hardware that is specifically designed to work with Paparazzi from the start, but Paparazzi has also been ported to other popular autopilots.  
 
[[Image:tiny13_family_top_sm.jpg|center|400px|Tiny 1.1 autopilots on the "assembly line"]]
[[Image:tiny13_family_top_sm.jpg|center|400px|Tiny 1.1 autopilots on the "assembly line"]]
One of the great advantages of Paparazzi is support for many hardware designs. There is autopilot hardware that is specifically designed to work with Paparazzi from the start, but Paparazzi has also been ported to popular autopilots from external parties.


<h3> Paparazzi designed hardware </h3>
<h3> Paparazzi designed hardware </h3>
Line 33: Line 30:


<h3> Other popular autopilot hardware support </h3>
<h3> Other popular autopilot hardware support </h3>
Using existing hardware is great to get you started, as sometimes it just involves buying a stock drone, and uploading paparazzi to it. Currently, Paparazzi supports many of the popular Parrot drones, such as the [[AR Drone 2]], [[Bebop]] and [[Rolling Spider]] airframes. These come with built in embedded Linux computers as their autopilot hardware, and Paparazzi runs as a Linux process interfacing at the lowest level possible with the hardware.
Using existing hardware is great to get started, as sometimes it just involves buying a stock drone and uploading paparazzi to it. Currently, Paparazzi supports many of the popular Parrot drones, such as the [[AR Drone 2]], [[Bebop]] and [[Rolling Spider]] airframes. These come with built in embedded Linux computers as their autopilot hardware, and Paparazzi runs as a Linux process interfacing at the lowest level possible with the hardware.
 
Secondly, Paparazzi supports the [[Pixhawk]] autopilot, of which an example can be found in the [[Iris]] airframe. The Pixhawk is a duo processor board, with an autopilot chip and a separated Fly By Wire chip for safety.  


Secondly, Paparazzi supports the [[Pixhawk]] autopilot, of which an example can be found in the [[Iris]] airframe.
Also the [[Pixracer]] board is flyable by Paparazzi. The cryptic name is px4fmu 4.0, that means all designs based on the open pxfmu 4.0 schematic design can be used.


<h2>Schematics, CAD files, Gerber files, BOM release strategy</h2>
<h2>Schematics, CAD files, Gerber files, BOM release strategy</h2>

Latest revision as of 00:20, 13 December 2019



Autopilot.png Autopilots

STM32H7 based boards
STM32H7 32-bit ARM Cortex™-M7 MCU based autopilot:

  • Tawaki v2.01 New!
    Improved MCU, Sensors and Power supply. Small, lightweight and versatile Autopilot, 9 DOF IMU, microSD, Baro, USB-C, ready for Rotorcraft, Fixed Wing and Hybrid applications...

STM32F7 based boards
STM32F7 32-bit ARM Cortex™-M7 based autopilot:

  • Tawaki v1.10
    Small, lightweight and versatile Autopilot, 9 DOF IMU, microSD, Baro, ready for Rotorcraft, Fixed Wing and Hybrid applications...
  • Chimera v1.00
    Versatile Autopilot for fixed wing, 9 DOF IMU, Baro, microSD, Pitot, Modem, ready for Companion Computer...

STM32F1 based boards

STM32F4 based boards

  • Apogee
    STM32F4 (ARM Cortex™-M4) based autopilot for fixed wing:
    • Apogee v1.00
      Super small and lightweight autopilot, 9 DOF IMU, microSD high speed, Baro, ,...
  • Elle
    STM32F4 autopilot system:
  • Lisa
    STM32F4 based autopilots:
    • Lisa/MX
      STM32F4 versatile autopilot with crypto support
    • Lisa/MX-Small
      STM32F4 versatile autopilot with crypto support
  • Krooz
    STM32F4 Cortex™-M4 high integrated Rotorcraft autopilot
    • Krooz
      STM32F4 Cortex™-M4 high integrated Rotorcraft autopilot
    • KroozSD
      STM32F4 Cortex™-M4 high integrated autopilot, w. microSD slot, XBee conn.
  • Pixhawk
    Duo processor with Autopilot core on a STM32F4 Cortex™-M4 and Fly By Wire core on a STM32F1 Cortex™-M1

LPC2148 based boards

  • Booz
    Quadrotor autopilot
  • NavGo
    Multirotor autopilot
    • NavGo v3
      Small and lightweight multirotor autopilot
  • Umarim
    LPC based embedded IMU autopilot designed for small fixed wing:
  • Tiny
    GPS integrated lightweight autopilots:
    • Tiny v0.99
      Tiny autopilot
    • Tiny v1.1
      Integrated GPS and 5V/2A supply
    • Tiny v2.11
      Two layers PCB, 0603 components, big GPS groundplane, improved connectivity.
  • TWOG v1.0
    8 grams Tiny WithOut GPS autopilot, with external GPS option.
  • YAPA
    Yet Another Paparazzi Autopilot:
    • YAPA v1.0
      Same as TWOG, but bigger with XBee, 100mil headers, mounting holes, rs232
    • YAPA v2.0 Reduced component cost
  • HB
    Autopilots built in Bremen:
    • HB v1.0
      Four layers PCB, no GPS, JTAG with IMU
    • HB mini
      Four layers planar PCB, JTAG, 10 sevos, 12g, no GPS, with IMU

Aircraft With Embedded Autopilots

Archive

Autopilot.png Paparazzi Autopilots


One of the great advantages of Paparazzi is support for many hardware designs. There is autopilot hardware that is specifically designed to work with Paparazzi from the start, but Paparazzi has also been ported to other popular autopilots.

Tiny 1.1 autopilots on the "assembly line"

Paparazzi designed hardware

Most current autopilots are designed around two primary processors:

  • STM32 series microcontrollers
  • LPC21xx series microcontrollers

There are active and current autopilots designs using both architectures. Not all autopilots have the same capabilities, peripherals or features, but each has advantages in different applications.

Currently, boards are designed around the STM32 microcontollers. Some of the autopilots use the STM32F1 and others the STM32F4 microcontrollers. This provides a wide range of choices resulting in a large variety of peripherals and speeds. Architecture-dependent firmware code is supported in part by libopencm3, as well as Chibi OS through the Paparazzi RT branch.

The LPC21xx based boards use the LPC2148 and have been flying fixed wing and multi-rotors for many years. This architecture is more mature but at the expense of speed and extra ports available on the newer STM32 series processors. The Tiny series, Booz, TWOG, YAPA, Umarim and NavGo autopilots all use the LPC2148.

Newer autopilots use either the STM32F1 or STM32F4 microcontrollers. You can choose from Lisa/M(X), Elle0, Krooz or Apogee autopilots, depending on your processing and IO needs.

Some autopilots have also been designed for close integration with small single-board computers, particularly those based on OMAP processors such as the Gumstix Overo series. The Lisa/L and Classix boards are designed with this in mind, though other autopilots can be easily interfaced. Further information can be found here.

A basic feature comparison table is presented to help in the autopilot hardware selection process.

For information regarding architecture and firmware compatibility of various subsystems and modules, please see the appropriate Subsystems overview and Modules List pages.


Other popular autopilot hardware support

Using existing hardware is great to get started, as sometimes it just involves buying a stock drone and uploading paparazzi to it. Currently, Paparazzi supports many of the popular Parrot drones, such as the AR Drone 2, Bebop and Rolling Spider airframes. These come with built in embedded Linux computers as their autopilot hardware, and Paparazzi runs as a Linux process interfacing at the lowest level possible with the hardware.

Secondly, Paparazzi supports the Pixhawk autopilot, of which an example can be found in the Iris airframe. The Pixhawk is a duo processor board, with an autopilot chip and a separated Fly By Wire chip for safety.

Also the Pixracer board is flyable by Paparazzi. The cryptic name is px4fmu 4.0, that means all designs based on the open pxfmu 4.0 schematic design can be used.

Schematics, CAD files, Gerber files, BOM release strategy

About the hardware development and release process.

Files needed to create the hardware can be found here. It is always good to remind oneself of the email Antoine once wrote in the mailing list before you want to start producing your own PCB's.

8 June 2011 13:25:47 Antoine Drouin wrote on the mailing list:

I've started this project together with Pascal 8 years ago and since then I have dedicated my time to try and make it successful. I'm utterly convinced of the benefits of open source, but observing how Paparazzi grew over time, I came to the conclusion that hardware is a bit different than software... "gcc tiny.brd" is not going to make a board magically appear on your desktop.

I'll list here some of my arguments in favor of releasing CAD files after the board is mature.

  1. Unlike software, where an unskilled user can type make and get a piece of complex software to successfully build, assembling hardware requires tools and skills. Providing gerbers and BOM have lured a bunch of new users into believing otherwise and has created tons of frustration. I've myself fixed a number of badly assembled boards and I even recall that while helping debugging a board (so after assembly), discovering that the person had manufactured two layers PCBs instead of four layers. As the technology of the autopilot increases, this problem becomes more and more important.
  2. The success of the project depends on the availability of affordable hardware. The price of hardware is directly and exponentially dependent on the number of manufactured units. If ten persons manufacture 10 boards each, the cost will be much higher than if one person manufactures 100.
  3. Last and not least, the quality of assembly also depends very much on the number of manufactured units. Good quality can only be achieved through the use of automated placing and soldering, and those processes can only be used if the number of units reach a certain amount.

For the autopilot comparison table see below.



NOTE: This list contains only mature and fully supported autopilots designed specifically for the Paparazzi UAV project.

Avail MCU Sensors IO/Comm Periph Program/Debug Power Mechanical Release/Version
Name Version Active Buy Part Clock Flash RAM IMU Mag Baro Diff GPS UART I2C SPI ADC PWM PPM out PPM in R/C serial GPIO LED USB CAN MODEM SD RTC Other Input Output Switch Size Weight Connectors PCB Type Mounting Date Introduced Previous Version
Apogee V1.00 Y Buy STM32F405RGT6 168MHz 1024kB 128 & 64kB Y Y Y N N 3 & 1Rx 2 1 0 + 3 (12bit) 6 + 1 N 1 + 15 1 (std & S.BUS) 0 + 4 4 DFU bootloader + USB storage Y N SDIO + USB storage yes + backup cap mini-USB B USB(DFU) + SWD 5.5V - 17V 1A@3.3V, 1.5A@5V 1 (5V) 53 x 25 x 9mm 10g Picoblade 4-layer 4 x M2 Summer 2013
Elle0 V1.2 Y Pre-Order STM32F415RCT6 168MHz 1024kB 192kB Y Y Y N N 2 & 2RX/TX 1 0 2 8 N 1-8 2 4 DFU bootloader 110 N N N micro-USB B, JTAG USB (DFU) + JTAG 5V 2x299mA@3.3V 1 36mm x 36mm JST9 + 0.1" pin header 4-layer 4 x M3 Winter 2015 v1.1
Lisa/S V1.1 Y Buy STM32F103REY6 72MHz 512kB 64kB Y Y Y N Y 1 & 1RX 18 0 0 6 N 1 1 0 4 N 1 N N N 4 x brushed motor drivers SWD + UART 2.3V - 5.5V 1A@3.3V 1 20mm x 20mm x 5mm 2g 0.05" header 6-layer 4 x M2 Summer 2013 v1.0
Lisa/M V2.1 Y Buy STM32F105RCT6 72MHz 256kB 64kB Y Y Y N N 2 & 2RX 1 + 15 1 3 + 2 (12bit)5 6 + 25 N 0 + 15 2 1 5 DFU bootloader 1 N N N JTAG USB (luftboot)+ JTAG + UART 5V - 16V 500mA@3.3V, 250mA@5V N 34mm x 60mm x 10mm 9.9g - 10.8g Picoblade & 0.1" Servo 4-layer 4 x M3 Winter 2012 v2.0
Lisa/L v1.1 N STM32F103RE 72MHz 512kB 64kB N N Y Y N 3 & 1RX 2 2 3 (12bit) 6 N 1 8 JTAG + UART 1 N N N Overo Gumstix JTAG + UART 6.1V - 18V 2.25@5V, 2.25A@3.3V, Other 2 ~100mm x ~50mm Picoblade 4-layer 4 x M3 Summer 2010 v1.0
KroozSD Y Buy STM32F405RGT6 168MHz 1024kB 128 & 64kB krooz/ext Y Y N N 3 2 1 4 + 1 (12bit)5 10 + 15 N 1 2 + 15 3 bootloader Y Xbee SPI N micro-USB B 7V - 32V 1.5A@3.3V, 5A@5V N 50mm x 60mm x 10mm 20g - 40g Picoblade & 0.1" Servo 2-layer 4 x M3 Spring 2013 Krooz
Umarim Lite V2 Y Buy LPC2148 60MHz 512kB 32kB & 8kB Y N N N N 2 1 1 86 6 N 1 + 15 0 + 46 2 bootloader Y N N N mini-USB B USB (pprz bootloader) 5.5V - 17V 1A@3.3V, 1.5A@5V N 53mm x 25mm 8g Picoblade 4-layer 4 x M2 Summer 2012
Umarim V1.0 N LPC2148 60MHz 512kB 32kB & 8kB Y N Y N N 2 2 1 0 + 4 (10bit) 6 N 1 + 15 0 + 46 2 bootloader Y N N N USB (pprz bootloader) 5.5V - 17V 1A@3.3V, 1.5A@5V N 56mm x 25mm 9g Picoblade 4-layer 4 x M2 Fall 2011
NavGo V3 Y Buy LPC2148 60MHz 512kB 32kB & 8kB Y Y Y N N 2 2 1 0 + 4 (10bit)6 0 + 15 N 1 0 + 26 4 bootloader Y N N N USB (pprz bootloader) 5.5V - 16V 1A@3.3V, 1.5A@5V N 35mm x 35mm Picoblade 4-layer 4 x M2 Summer 2012
Tiny v2.11 Y Buy LPC2148 60MHz 512kB 32kB & 8kB N N N N Y 1 1 1 0 + 1 (10bit)6 8 1 1 2 3 bootloader Y N N N USB (pprz bootloader) 6.1V - 18V 1A@3.3V, 2.25A@5V 1 70.8mm x 40mm 24g Picoblade 2-layer no Fall 2007 v1.1
TWOG v1.0 N LPC2148 60MHz 512kB 32kB & 8kB N N N N N 2 1 1 8 (10bit) 8 1 1 2 3 bootloader Y N N N USB (pprz bootloader) 6.1V - 18V 1A@3.3V, 2.25A@5V 1 40.2mm x 30.5mm 8g Picoblade 2-layer no Spring 2008
YAPA v2.0 N LPC2148 60MHz 512kB 32kB & 8kB N N N N N 2 1 1 6 (10bit) 10 N 1 1 3 bootloader Y Xbee N N RS232 USB (pprz bootloader) 6.1V - 18V 2x 1A@3.3V, 2.25A@5V 1 80.0mm x 40.0mm? 23g w/ XBee? 0.1" Headers 2-layer 4x M3 Spring 2011 v1.0
HBmini v2.0 N LPC2148 60MHz 512kB 32kB & 8kB Y Y Y N N 2 2 1 8 (10bit)(16bit) 10 11 2 bootlader N N N N Buzzer JTAG 6.1-18V 1A@3.3V, 2.25A@5V 4 57x30mm 30 Picoblade & 0.1" Servo 4-layer 4 x M2 Winter 2012

Notes:

This table was created using a google document spreadsheet. If you want to add or improve anything in the table, please contact Esden to get write access to the spreadsheet. This makes editing and maintaining of the table much easier!

1. Only the newest revisions of the more commonly used autopilots are listed

2. The extra 8kB of RAM on the LPC2148 shared with the USB DMA

3. The onboard sensors are almost always supplemented with external sensors. For example, TWOG can use an external IMU or IR sensors, and also needs an external GPS.

4. Input/Outputs listed are generally those easily accessible on regular autopilot connectors, customization/hacks can modify available I/O, for example free an extra I2C on Tiny and TWOG

5., 6. Some features use shared resources - denoted by X + Y where Y is shared - and cannot be used simultaneously

5. Lisa/M v2.0 shared resources include: one I2C is shared with 2 PWM outputs, two ADCs are shared with LEDs, one RX only UART is shared with the PPM capture

6. Umarim v1.0 shared resources include: 4 ADCs are shared with 4 GPIOs

7. Usually other unused pins can be used for additional GPIO with some code modifications

8. Many of the pins have multiple purposes. Servo 5&6 can be used for i2c even though there is no dedicated connector.

9. The two JST connectors, provide a combined RX and TX connection. The RX & TX lines are combined through a 100Ohm resistor. The GPS and Telemetry connectors are full TTL UARTs.

10. Only the CAN RX&TX lines are exposed, no transceiver included on board.

Subcategories

This category has the following 5 subcategories, out of 5 total.

B

H

L

T

Y

Retrieved from "http://wiki.paparazziuav.org/w/index.php?title=Category:Autopilots&oldid=24357"