Hardware

KO | EN

gitlite — search

#python #hacktoberfest #react #ai #typescript #llm #go #android #deep-learning #linux #macos #kubernetes #ios #openai

(★ 1,368)

PX4 Hardware designs

파일 탐색기

최종 버전 다운로드 (.zip)

- PX4AIRSPEEDv1.1.brd
- PX4AIRSPEEDv1.1.sch
- PX4FLOW1.3.1.brd
- PX4FLOW1.3.1.sch
- PX4FMUv1.6.brd
- PX4FMUv1.6.sch
- PX4FMUv1.7.1.brd
- PX4FMUv1.7.1.sch
- PX4FMUv1.7.brd
- PX4FMUv1.7.sch
- README.md
- PX4FMUv2.3.brd
- PX4FMUv2.3.sch
- PX4FMUv2.4.3.brd
- PX4FMUv2.4.3.sch
- PX4FMUv2.4.5.brd
- PX4FMUv2.4.5.pdf
- PX4FMUv2.4.5.sch
- PX4FMUv2.4.6.brd
- PX4FMUv2.4.6.sch
- PX4FMUv2.4.brd
- PX4FMUv2.4.sch
- README.md
- - 80PIN_FMU3_REV_C.SchDocPreview
  - CHANGE_FMU3_REV_D.SchDocPreview
  - FMU3_REV_D.PcbDocPreview
  - FMU_FMU3_REV_C.SchDocPreview
  - FMU_Power_FMU3_REV_C.SchDocPreview
  - IO_FMU3_REV_C.SchDocPreview
  - IO_PWR_FMU3_REV_C.SchDocPreview
  - LEDs_FMU3_REV_C.SchDocPreview
  - PCA_0004_80PIN_FMU3_REV_C.SchDocPreview
  - PWM_PPM_FMU3_REV_C.SchDocPreview
  - SD_USB_FMU3_REV_C.SchDocPreview
  - SENSORS_FMU3_REV_C.SchDocPreview
  - SERIAL_FMU3_REV_C.SchDocPreview
- - Bill of Materials-FMU3_REV_D(FMU3_REV_D).xlsx
- - FMU3_REV_D.~(1).PcbDoc.Zip
  - FMU3_REV_D.~(1).PrjPcb.Zip
  - FMU3_REV_D.~(2).PcbDoc.Zip
- - PCB 3D Print from Above.PDF
  - PCB 3D Print from below.PDF
- - Assembly.PDF
- - Report Board Stack.PDF
- - Schematic Prints.PDF
- 80PIN_FMU3_REV_C.SchDoc
- CHANGE_FMU3_REV_C.SchDoc
- CHANGE_FMU3_REV_D.SchDoc
- FMU.OutJob
- FMU3_REV_D.PcbDoc
- FMU3_REV_D.PcbLib
- FMU3_REV_D.PrjPcb
- FMU3_REV_D.PrjPcbStructure
- FMU3_REV_D.SCHLIB
- FMU_FMU3_REV_C.SchDoc
- FMU_Power_FMU3_REV_C.SchDoc
- IO_FMU3_REV_C.SchDoc
- IO_PWR_FMU3_REV_C.SchDoc
- LEDs_FMU3_REV_C.SchDoc
- PWM_PPM_FMU3_REV_C.SchDoc
- README.md
- SD_USB_FMU3_REV_C.SchDoc
- SENSORS_FMU3_REV_C.SchDoc
- SERIAL_FMU3_REV_C.SchDoc
- README.md
- FMUv5_stm32_pinout.md
- Pixhawk4-Data-Sheet.pdf
- Pixhawk4-Pinouts.pdf
- README.md
- - IMU_REV_C.PcbDocPreview
  - IMU_REV_C.SchDocPreview
- - IMU.~(1).OutJob.Zip
  - IMU_REV_C.~(1).PcbLib.Zip
  - IMU_REV_C.~(1).PrjPcb.Zip
  - IMU_REV_C.~(2).PrjPcb.Zip
  - IMU_REV_C.~(3).PrjPcb.Zip
  - IMU_REV_C.~(4).PrjPcb.Zip
- - PCB 3D Print from Above.PDF
  - PCB 3D Print from below.PDF
- - Assembly.PDF
- - IMU_REV_C.xlsx
- - Report Board Stack.PDF
- - Schematic Prints.PDF
- IMU.OutJob
- IMU_REV_C.Dat
- IMU_REV_C.PcbDoc
- IMU_REV_C.PcbLib
- IMU_REV_C.PrjPcb
- IMU_REV_C.PrjPcbStructure
- IMU_REV_C.SchDoc
- IMU_REV_C.SCHLIB
- PX4IOARMTv1.0.brd
- PX4IOARMTv1.0.sch
- PX4IOARv1.2.brd
- PX4IOARv1.2.sch
- PX4IOv1.3.brd
- PX4IOv1.3.sch
- IMU.pdf
- imu.SchDoc
- MINDPX V2.8 SCH.pdf
- MindPX V2.8 SCH.SchDoc
- MindPX2.2.SchDoc
- MINDPX22.pdf
- MINDRACER V12 SCH.pdf
- MINDRACER-V12.DSN
- README.md
- - pixhawk_debug_adapter_mini_Fab.PDF
  - pixhawk_debug_adapter_mini_Schem.PDF
- 01_cover_page.SchDoc
- 02_main.SchDoc
- pixhawk_debug_adapter_mini.BomDoc
- pixhawk_debug_adapter_mini.OutJob
- pixhawk_debug_adapter_mini.PcbDoc
- pixhawk_debug_adapter_mini.PCBDwf
- pixhawk_debug_adapter_mini.PrjPcb
- pixhawk_debug_adapter_mini.PrjPcbVariants
- - PCB Fab Documentation.PDF
- - Assembly Documentation.PDF
- - .SpecialStrings
  - 830-00011 Microhard Module Breakout Board Assembly.OutJob
  - 830-00011 Microhard Module Breakout Board Assembly.PCBDwf
  - 830-00011 Microhard Module Breakout Board PCB Fab.OutJob
  - 830-00011 Microhard Module Breakout Board PCB Fab.PCBDwf
  - 830-00011 Microhard Module Breakout Board.BomDoc
  - 830-00011 Microhard Module Breakout Board.OutJob
  - 830-00011 Microhard Module Breakout Board.PcbDoc
  - 830-00011 Microhard Module Breakout Board.PrjPcb
  - 830-00011 Microhard Module Breakout Board.SchDoc
- README.md
- - PSM_components_REV_C.SchDocPreview
  - PSM_footprint_REV_C.SchDocPreview
  - PSM_REV_C.PcbDocPreview
- - Bill of Materials-PSM_REV_C(PCA_0007_PSM).xlsx
- - PCA_0007_PSM_REV_C.~(1).PrjPcb.Zip
  - PCA_0007_PSM_REV_C.~(2).PrjPcb.Zip
  - PSM.~(1).OutJob.Zip
  - PSM_REV_C.~(1).PcbDoc.Zip
  - PSM_REV_C.~(1).PcbLib.Zip
  - PSM_REV_C.~(1).PrjPcb.Zip
  - PSM_REV_C.~(2).PrjPcb.Zip
- - PCB 3D Print from Above.PDF
  - PCB 3D Print from below.PDF
- - Assembly.PDF
- - Report Board Stack.PDF
- - Schematic Prints.PDF
- PCA_0007_PSM_REV_C.PrjPcb
- PSM.OutJob
- PSM_components_REV_C.SchDoc
- PSM_footprint_REV_C.SchDoc
- PSM_REV_C.Dat
- PSM_REV_C.PcbDoc
- PSM_REV_C.PcbLib
- PSM_REV_C.PrjPcb
- PSM_REV_C.PrjPcbStructure
- PSM_REV_C.SCHLIB
- Status Report.Txt
- README.md
- sapog_reference_hardware.brd
- sapog_reference_hardware.lbr
- sapog_reference_hardware.sch
.gitignore
A_PX4_PARTS_DATABASE.csv
Installing_Altium_Viewer.txt
pixhawk2.lbr
README.md

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Pixhawk Hardware Designs

[![Join the chat at https://gitter.im/PX4/Hardware](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/PX4/Hardware?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)

[Pixhawk](http://pixhawk.org) is an independent open-hardware project that aims to provide "the gold standard" for readily-available, hiqh-quality and low-cost autopilot hardware designs for the academic, hobby and developer communities.
Pixhawk supports multiple flight stacks: PX4 ® and ArduPilot ®.

> **Note** Designs are provided for a number of components used in unmanned vehicles, including: Autopilots (Flight Management Units - FMUs), ESCs (electronic speed controllers), optical flow sensors, etc.

## What are Open Hardware Designs?

The [Pixhawk project](https://pixhawk.org/) provides open hardware designs following the [OSHW 1.1 definition](https://www.oshwa.org/definition/).

In essence, this definition allows anyone to freely study, modify, distribute, make, and sell the designs (or hardware based on the designs) under the terms of a particular [open source licence](#licensing).

## Hardware Designs

Hardware designs delivered by the project are listed below.

### FMU (Autopilot) Designs

Pixhawk FMU open designs include all information required to create an autopilot hardware product that is *firmware compatible* with other hardware created from the same design.
Manufacturers are encouraged to take the designs and create products that are best suited to a particular market or use case (e.g. for very small vehicles, or those that operate at environmental extremes).

> **Note** While a physical connector standard is not mandated, newer products generally follow the [Pixhawk Connector Standard](https://pixhawk.org/pixhawk-connector-standard/).

#### Design Specifications

Designs are *usually* specified in the form of *schematics* that show all included components (CPU, sensors, etc.), how they are connected, and their pin mappings.
They may also include a BOM (bill of materials).

> **Note** Not all designs deliver schematics.
  A minimal design needs to contain enough information for manufacturers to create a compatible products; this can also be achieved using a precise pinout definition and information about connections of internal/external busses, etc.

#### Open Reference Hardware

The project provides *open reference hardware/layouts* for **some** open designs, in some versions.
These are provided in the form of PCB layout files.

The reference hardware files are shared under the same [license](#licenses) as the associated open design, and hence may be used in the same way(s).

#### FMU Versions

The Pixhawk project has evolved the FMU design through a number of verisons.

These are named using the designation: FMUvX (e.g.: FMUv1, FMUv2, FMUv3, FMUv4, etc.).
Higher FMU numbers indicate that the board is more recent, but may not indicate increased capability (versions can be almost identical - differing only in connector wiring).

The versions are listed below (with a high level overview of the main differences).

Version | Year | Lead Product | CPU | Other
--- | --- | --- | --- | ---
[FMUv1](FMUv1/README.md) & [IOv1](IOv1) | 2012 | None | 168 MHz M4 | (Discontinued) Original Flight Management Unit and Separate I/O board.
[FMUv2](FMUv2/README.md) | 2013 | Pixhawk 1 | 168 MHz M4 | Single board with STM32427VI processor.
[FMUv3](FMUv3_REV_D/README.md) | 2015 | Pixhawk 2 | 168 MHz M4 | Redundant sensors. Identical to FMUv2, but usable flash doubled to 2MB.
[FMUv4](FMUv4/README.md) | 2015 | Pixracer | 168 MHz M4 | Increased RAM. Faster CPU. More serial ports. No IO processor.
FMUv4X | 2017 | Pixhawk 3 Pro | 168 MHz M4 | Slightly increased RAM. More serial ports. IO processor. Redundant sensors.
[FMUv5](FMUv5/README.md) | 2018 | Pixhawk 4 | 200 MHz M7 | New processor (F7). Much faster. More RAM. More CAN busses. Much more configurable. > **Note** Minimum specification provided (pinout info, but no schematics).
FMUv5X | 2019 | Pixhawk 5X | 200 MHz M7 | Temp-calibrated, redundant sensors.

> **Note** Products based on Pixhawk designs are listed here: [PX4 User Guide > Pixhawk Series]( https://docs.px4.io/master/en/flight_controller/pixhawk_series.html#pixhawk-series).

#### Derived FMU Products

Commercial products that are *derived* (under the terms of the open source license) from the Pixhawk FMU designs must provide their schematics and other information.

Relevant products are listed below:

- [MindPX V2 Hardware](MindPXv2/README.md)

### Sapog ESC

- [Sapog ESC](https://github.com/PX4/sapog) Hardware - The directory [sapog_reference_hardware](sapog_reference_hardware/README.md) contains the reference hardware design for the Sapog ESC firmware.

### Other

- [AIRSPEEDv1](AIRSPEEDv1) - 
- [FLOWv1](FLOWv1)
- [IMUv3_REV_C](IMUv3_REV_C)
- [PSMv3_REV_C](PSMv3_REV_C)

## Dev Call

Pixhawk standards are developed in a weekly public developer call.

The call is shown in the [Dronecode calendar](https://www.dronecode.org/calendar/) as: *Pixhawk Hardware Standards Weekly Call* (all call details are in the entry).

## Licensing and Trademarks

Pixhawk project schematics and reference designs are licensed under [CC BY-SA 3](https://creativecommons.org/licenses/by-sa/3.0/legalcode).

The license allows you to use, sell, share, modify and build on the files in almost any way you like - provided that you give credit/attribution, and that you share any changes that you make under the same open source license (see the [human readable version of the license](https://creativecommons.org/licenses/by-sa/3.0/) for a concise summary of the rights and obligations).

> **Note** Boards that are *derived directly* from Pixhawk schematic files (or reference boards) must be open sourced.
  They can't be commercially licensed as proprietary products.

Manufacturers can create (compatible) *fully independent products* by first generating fresh schematic files that have the same pin mapping/components as the FMU designs.
Products that are based on independently created schematics are considered original works, and can be licensed as required.

## Trademarks

The term *Pixhawk* is a trademark, and may not be used in product names without explicit permission from the trademark owner.

Typically this trademark is granted to the first board based on a particular FMU design and/or boards that use Pixhawk open reference hardware layouts.

> **Note** A "Pixhawk" is an autopilot that has been been given permission to use the Pixhawk trademark in its name.
  While other boards are based on the "Pixhawk FMU Standard", the are not *strictly speaking* "Pixhawks".

Hardware

파일 탐색기

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Hardware

파일 탐색기

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README