Flight-controller hardware
Procurement starts with an autopilot ecosystem and supported board revision. Processor names alone do not establish peripheral or firmware compatibility.
Component library
Control & interfaces
Browse control & interfaces by interface and service requirement. Open an individual reference for the information needed to evaluate a sourcing request.
BECs and voltage regulators
Auxiliary equipment needs a regulated rail matched to its input and transients. Separate continuous demand from startup demand.
Control and telemetry harnesses
Cable assemblies connect named interfaces. A connector family and wire count do not identify the signal assignment or operating voltage.
CAN interface accessories
A CAN accessory is purchased for a specific electrical network and device implementation. Protocol support and physical connectors should be evaluated separately.
Related buying decisions
Prevent a connector match from becoming a wiring error
Physical compatibility is not electrical compatibility. Two harnesses with the same connector family may assign power and signals differently.
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.
When a custom harness needs a drawing review
Cable length and connector selection are only part of a custom assembly. Branches, shielding, terminations and labels determine how it installs and how it is checked.
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.