Manufacturer’s PX4 Board Support Guide
The PX4 development and test teams fully support and maintain boards that are compliant with the Pixhawk Standard. Manufacturers who wish to deviate from the standard or create completely new boards can do so, but will need to support any resulting compatibility differences.
This guide outlines the general requirements for board support, along with the additional requirements for the different board support categories.
Note: Boards that are not compliant with the requirements are unsupported; they will not be listed on the PX4 website hardware list and will be removed from the codebase.
The general requirements for all supported boards are:
- The hardware must be available in the market.
- The boards may not have blocking hardware bugs or unacceptable quality that make it impossible or dangerous to use the board with PX4 on a UAV. Board needs to pass acceptance criteria to ensure quality of parts and assembly.
- A clear and easy way to contact customer support for customers. One or more of the following is accepted:
- Slack channel presence
- Support email
- Phone number
For more information on bootloaders see: PX4 Nuttx Porting Guide > Bootloader.
- A complete pinout made available publicly that maps PX4 pin definitions to:
- Microcontroller pins
- Physical external connectors
Board Support Categories
The board support categories are listed below. The autopilot boards in each category are listed at: https://px4.io/autopilots/.
Note: Manufacturer supported boards may be as well/better supported than Pixhawk boards (for example through economies of scale).
A Pixhawk board is one that conforms to the Pixhawk standards. These standards are laid out on http://pixhawk.org, but at high-level require that the board passes electrical tests mandated by the standard and the manufacturer has signed the Pixhawk adopter and trademark agreement.
PX4 generally only supports boards that are commercially available, which typically means that board standards released within the last five years are supported.
VER and REV ID (Hardware Revision and Version Sensing)
FMUv5 and onwards have a sensing mechanism by the use of a 2 pin interface. One digital output and one analog input is used for each sensing block. The blocks may be optionally populated but the 2 X 2 pins are always reserved for these functions. This sensing coupled with optional configuration data will be used to define hardware’s configuration with respect to a mandatory device and power supply configuration. For example determining if there is a sensor fault (IC not responding) or power supply is not valid for a given configuration where neither of the two components are optional.
Because these boards are 100% compliant with the Pixhawk standard, the values assigned for Hardware Version and Revision sensing namely the VER and REV ID are the defaults for that FMUv Version.
For example on FMUv5, the values are
These boards are supported by the manufacturer. To qualify for this category the board must work with the latest stable PX4 release within 4 months of that release.
- Manufacture owns the support
- Manufacturer must supply at least 2 boards to the core-dev team (for use on test rack and by test team)
Tip: While there is no commitment from the PX4 maintainers and the flight test team to support and test boards in this category, we strongly recommended PX4 and manufacturer teams build close working relationships. This will result in a better result for all parties.
VER and REV ID
These boards will be assigned VER and REV ID based on compatibility. A special assignment will be made by PX4 if the board is a variant of an FMU specification and capable of running the same binary, with minor differences supported by the manufacturer. Contact the PX4 maintainer at firstname.lastname@example.org to request more information.
These boards are all boards that don’t fall in the above categories, or don’t fall in those categories anymore. The following requirements apply:
- The board must be working with at least one PX4 release for a defined vehicle type, but not necessarily the latest release.
VER and REV ID
Experimental boards are allocated IDs based on compatibility, in the same way as Manufacturer Supported boards.
Note: Experimental boards that were previously Pixhawk or Manufacturer supported will have/retain their original IDs.
This category includes all boards that aren’t supported by the PX4 project or a manufacturer, and that fall outside the “experimental” support.
- Board is somewhat compatible on paper with something we already support, and it would take minimal effort to raise it to “experimental”, but neither the dev-team or the manufacturer are currently pursuing this
- Manufacturer/Owner of hardware violates our Code of Conduct
- Closed source, where any of the necessary tools/libs/drivers/etc needed to add support for a board is deemed incompatible due to licensing restrictions
- Board doesn’t meet minimum requirements outlined in the General requirements
VER and REV ID
These boards will NOT be assigned VER and REV ID (and cannot run PX4 FMUvX firmware).
It is assumed that when a manufacturer declares that a board falls in a certain category, that the board is compliant with the requirements for that category and the general requirements.
When a new board is brought to market that falls into the manufacturer supported or experimental category, the manufacturer is responsible for updating the PX4 documentation and doing the board release process in PX4. We recommend the following steps:
Contact PX4 board maintainers at email@example.com and request the following:
- The assignment of a ‘board id’ for bootloader and firmware selection in QGC.
- The assignment of REV and VER ID resistor values.
- If the board supports USB: Either request the assignment of a USB VID and PID or provide the USB VID and PID.
Integrate the board according to the board porting release process described in the PX4 dev guide here: https://dev.px4.io/master/en/hardware/porting_guide.html
Disclaimer: The board support process may be changed and improved over time. Hardware manufacturers are encouraged to contribute to this process through the regular hardware call, the Discuss forum or Slack.
If parts of the board support guide/process are not clear:
- Ask the community for help on Slack channel #hardware or on the discuss forums
- Attend the regular hardware call
- Consultancy options are listed here: https://px4.io/community/consultants/