Pixhawk

Pixhawk is an open-source project that develops standards for flight-controller hardware used in unmanned aerial and other autonomous vehicles. The name refers both to the project and, in common industry usage, to hardware products designed to meet one or more Pixhawk specifications. A Pixhawk-standardized controller typically serves as the onboard flight-management computer, connecting sensors, motors, servos, communications equipment, navigation systems, and other vehicle peripherals. Products based on the standards are used in multirotors, fixed-wing aircraft, helicopters, vertical-takeoff-and-landing aircraft, rovers, and boats. The project originated in 2008 when Lorenz Meier, then a master's student at ETH Zurich, sought to build an indoor drone capable of navigating autonomously with computer vision and avoiding obstacles. The required combination of hardware, firmware, and high-level software was not readily available, so Meier and a team assembled a custom system for a European Micro Air Vehicle competition. The team, which worked with Professor Marc Pollefeys and included 14 members, spent approximately nine months developing the platform. In 2009, it won the indoor-autonomy category and became the first competitor in that category to demonstrate computer-vision-based obstacle avoidance successfully. After the competition, the team released the project as open source. Its publicly developed components included flight-controller hardware, the PX4 autopilot, the MAVLink telemetry and communication protocol, and ground-control software. This release allowed universities, researchers, companies, and hobbyists to build on a platform that previously would have required substantial proprietary engineering. MAVLink was subsequently adopted by the open-source ArduPilot ecosystem, while QGroundControl became an important ground-station interface for MAVLink-based vehicles. Pixhawk hardware therefore became part of a broader open-source flight stack rather than a self-contained commercial product. Commercial availability expanded in 2013, when 3D Robotics became the first manufacturer of commercial Pixhawk flight controllers. The move helped lower the cost and complexity of autonomous-flight experimentation by making capable hardware available for purchase and allowing users to load free PX4 or ArduPilot firmware. Other manufacturers, including Holybro and CubePilot, later produced controllers based on different generations or partial implementations of the standard. Pixhawk's principal role is standards coordination. Its specifications describe mechanical and electrical requirements for flight-management units, including board dimensions, sensor selection and placement, processor interfaces, connectors, and peripheral buses. Related specifications cover system-on-module designs, payload integration, radio interfaces, and smart batteries. The standards are designed primarily to support PX4 but are also widely used with ArduPilot. The project does not operate like a conventional single-brand hardware company: products are made by multiple manufacturers, and compatibility can vary by implementation and generation. Dronecode, established in 2014 and later organized as a Linux Foundation non-profit, has helped coordinate discussions around open-source flight-control development and Pixhawk standardization.

Pixhawk began in 2008 as an ETH Zurich-associated effort led by master's student Lorenz Meier. Meier wanted to create an indoor drone that could use computer vision to understand its surroundings, avoid obstacles, and fly autonomously. The necessary combination of sensors, embedded computing, control software, and ground-station tools was not readily accessible, so he recruited a team of 14 people with support from Professor Marc Pollefeys. Over roughly nine months, the group built a complete experimental platform for the indoor-autonomy category of a European Micro Air Vehicle competition. In 2009, the team won its category and demonstrated computer-vision obstacle avoidance, an achievement that helped validate the project technically. The work also exposed a lack of broadly available tools for researchers and developers who wanted to build autonomous aircraft. In response, the team made the project open source. The release covered not only a flight-controller board but also the PX4 autopilot software, the MAVLink protocol used to exchange telemetry and commands, and software for operating the vehicle from the ground. The open-source release enabled outside developers to reuse and modify the system. MAVLink was adopted by the ArduPilot project, creating an additional software path for Pixhawk-compatible hardware. QGroundControl became a major ground-control application for MAVLink systems. As the codebases were revised and the hardware went through successive development cycles, the project moved from an academic prototype toward a reusable platform that could be manufactured by third parties. In 2013, 3D Robotics became the first manufacturer to produce commercial Pixhawk flight controllers. This was a significant transition because users could buy a relatively capable autonomous-flight computer, install open-source PX4 or ArduPilot firmware, and use it for research, education, commercial development, or recreation. The availability of standardized hardware reduced the need for every project to design its own flight-management board. As the ecosystem expanded, the need for coordinated technical specifications became more important. Dronecode was founded in 2014 to help organize open-source drone development and discussions around compatible hardware and software. It later operated as a Linux Foundation non-profit. Pixhawk standards developed beyond a single board design to cover successive flight-management-unit generations, connector conventions, system-on-module architectures, payload interfaces, radio connections, and planned smart-battery integration. The project is now best understood as an open hardware-standard ecosystem rather than a conventional manufacturer. Companies such as Holybro and CubePilot have produced hardware implementing various Pixhawk generations, while PX4 and ArduPilot remain the principal autopilot software options associated with the platform. Pixhawk-standardized controllers are used across aircraft and other unmanned vehicles, including multirotors, fixed-wing aircraft, helicopters, VTOL vehicles, rovers, and boats. The open nature of the specifications supports interoperability, although implementation details and the degree of compliance can differ between manufacturers and product generations.

• 2014

  Dronecode founded

  [1]Pixhawken.wikipedia.org

  Dronecode was established to help coordinate open-source drone development and discussions surrounding the Pixhawk ecosystem.

• 2013

  First commercial Pixhawk flight controllers

  [1]Pixhawken.wikipedia.org

  3D Robotics became the first manufacturer to produce commercial flight controllers based on the Pixhawk project.

• 2009

  Indoor-autonomy competition victory

  [1]Pixhawken.wikipedia.org

  The Pixhawk team won its European Micro Air Vehicle competition category and demonstrated computer-vision-based obstacle avoidance.

• 2008

  Project initiated at ETH Zurich

  [1]Pixhawken.wikipedia.org

  Lorenz Meier began developing an indoor autonomous-drone platform with a team associated with ETH Zurich and Professor Marc Pollefeys.

• Project released as open source

  [1]Pixhawken.wikipedia.org

  The team opened the flight hardware, PX4 autopilot, MAVLink communications protocol, and ground-control software for public development.

An open, interoperable flight-control hardware standard that enables manufacturers and developers to build capable unmanned-vehicle autopilots compatible with open-source PX4 and ArduPilot software.

• Flight-controller hardware standard

  Pixhawk Autopilot Reference Standard

  The core Pixhawk specification defines the mechanical and electrical characteristics of compatible flight-management units. It covers board dimensions, sensor types and placement, provisions for heat dissipation, processor pin assignments, and communication interfaces. Released generations include Pixhawk 1, 2, 3, 4, 4X, 5, 5X, 6X, 6U, and 6C. The standard is intended to support PX4 and is also commonly used with ArduPilot.

• Modular flight-computer interface

  Pixhawk Autopilot Bus Standard

  The autopilot bus specification extends the reference standard for newer system-on-module flight computers, including the 5X and 6X families. It describes the relationship between a removable computing module and its baseboard, including high-density connectors, PCB layout guidance, and reference interface schematics for motors, servos, radios, and other peripherals.

• Hardware connector and pinout standard

  Pixhawk Connector Standard

  The connector standard promotes JST GH connectors for many flight-controller and peripheral connections. It also establishes user-facing pinout conventions for telemetry, GPS, CAN bus, SPI, power, and debugging ports, helping manufacturers and users connect compatible components consistently.

• Payload integration standard

  Pixhawk Payload Bus Standard

  The payload bus guidance describes ways to make vehicle payloads compatible with Pixhawk-operated systems. It is intended to improve the ability to combine payload equipment and flight controllers from different manufacturers, although the specification is not uniformly enforced across all payload products.

• Radio communications interface

  Pixhawk Radio Interface Standard

  The radio interface work defines mechanical, electrical, and software concepts for Pixhawk-specific communications. It contemplates USB or Ethernet links between ground stations and radio modules, with radio-frequency or LTE links available for communication between local and remote units.

• Battery-management interface

  Pixhawk Smart Battery Standard

  The smart-battery specification is intended to define how a battery-management system communicates with a Pixhawk flight-management unit, including communication protocols, connectors, and supported capabilities. The referenced material describes it as not yet published.

• 2014

  Coordination through DronecodeStrategy

  Background

  The expanding open-source drone ecosystem required a more structured forum for coordinating software, hardware, and standards work.

  Action taken

  Dronecode was founded to facilitate collaboration and standards discussions across the open-source drone community.

  Aftermath

  Dronecode became a Linux Foundation non-profit associated with coordination of the broader Pixhawk and PX4 development environment.

  Source

• 2013

  Commercialization through 3D RoboticsProduct launch

  Background

  The project had evolved through multiple hardware and software development cycles and was ready for manufacture by an outside company.

  Action taken

  3D Robotics became the first manufacturer to sell commercial Pixhawk flight controllers.

  Aftermath

  Users could obtain standardized flight hardware and pair it with open-source PX4 or ArduPilot firmware, reducing the barrier to autonomous-flight development.

  Source

• 2008

  Open-source release of the flight-control stackStrategy

  Background

  The original team found that researchers and developers lacked accessible tools comparable to the system created for the indoor-autonomy competition.

  Action taken

  The project released its flight-controller hardware, PX4 autopilot, MAVLink communications protocol, and ground-control software for public use and development.

  Aftermath

  The release enabled wider experimentation, encouraged integration with ArduPilot and QGroundControl, and established the open ecosystem that later supported commercial Pixhawk hardware.

  Source

1. 1Pixhawken.wikipedia.org
2. 2Pixhawk official websitepixhawk.org