Compatibility
Define compatibility by electrical, firmware, protocol, and capability behavior—not by appearance.
ESPFlight Docs · v1 • Validated v1 documentation path
# What compatibility depends on
ESP microcontroller/module behavior supported by the firmware.
Sensor support and orientation.
Electrical connections and power architecture.
Motor outputs and pin assignments.
Firmware configuration or required code changes.
Application / Firmware protocol compatibility.
Capabilities actually supported by the hardware + firmware combination.
# Custom hardware
A compatible board does not need to look identical to the Hardware Reference. If you change pins, sensors, power design, or other hardware-facing behavior, document the variant and update firmware configuration/code where required.
IDENTITY DIRECTION
As the ecosystem grows, explicit maker, product, revision, firmware, protocol, and capability metadata can reduce guesswork. Treat such metadata as a formal requirement only when it is specified and versioned.
# Practical compatibility checklist
This checklist is not an official certification scheme; it is the minimum set of questions a custom board should answer before you describe that specific revision as ESPFlight-compatible.
The ESP target/module is supported by the Firmware, or the required port/code changes are documented.
Required sensors are present, their orientation is known, and the matching Firmware support exists.
Four motor outputs map to the intended physical corners and the real output stage is compatible with the selected motors.
Power architecture, polarity, and required module supply behavior have been verified on the real board.
Pin mapping and Firmware configuration match the PCB, or every difference is implemented and documented.
Firmware/Application use a compatible Protocol version and only genuinely supported capabilities are advertised.
The new board passes the relevant Hardware Check, Bench Test, failsafe, and preflight validation path.
NAMING BOUNDARY
Passing this checklist does not turn a derivative/custom board into the official ESPFlight Hardware Reference. Keep independent branding and follow the Brand Policy when describing compatibility.