Flight-controller hardware
Procurement starts with an autopilot ecosystem and supported board revision. Processor names alone do not establish peripheral or firmware compatibility.
What to specify
Use these fields to describe your requirement. Values are supplied by the buyer or the responsible integrator; this reference does not list an in-stock SKU or a universally compatible replacement.
| Requirement | Information to include |
|---|---|
| Platform | Aircraft type and integration scope |
| Firmware | Supported software and board target |
| Ports | UART, CAN, PWM and required counts |
| Sensors | Onboard sensor configuration |
| Power | Input and backup-supply interfaces |
| Mount | Envelope and connector orientation |
Sample and acceptance review
Request manufacturer documentation, board revision and supported firmware information. Keep the acceptance configuration reproducible.
A common purchasing mistake
A connector or pin count shared with another board is not proof of a drop-in replacement.
Related purchasing decisions
Receiving checks for UAV electronics
Receiving should establish identity and conformity before equipment enters the serviceable inventory. A box arriving intact does not resolve board revision or missing documents.
Keep firmware compatibility in the hardware purchase
A board can be physically unchanged while the supported firmware or peripheral behavior changes. The purchase record should identify the intended software environment.
Technical reading
The following independent resource provides technical context. The request fields and review notes on this page are AVDORS editorial procurement guidance, not a quotation of product specifications or a claim of manufacturer authorization.
Holybro hardware documentation