Make five checks before you pay
Work through control, video, power, mechanical fit, and software support. Give each area its own line in a worksheet. Do not let one confident match—such as the right frame size—stand in for all the other checks.
Record exact model names and relevant versions. “The little receiver from that bundle” is not enough information for the next firmware update, repair, or secondhand sale.
Control and video are separate purchases
For control, verify the radio module and receiver system, band, firmware requirements, and the flight controller’s supported interface. For video, verify the camera/transmitter/receiver/display combination against the manufacturer’s compatibility information.
Be especially careful with ecosystem names that cover several generations. Familiar branding is a place to start looking, not the final answer. An official model-specific compatibility statement is better evidence than a forum comment about a vaguely similar setup.
Check power and physical fit together
Verify supported battery chemistry and voltage range, connector type and polarity, component limits, mounting patterns, and clearances. Read the hardware’s own documentation. Do not assume that a plug which physically fits is electrically appropriate.
Include antennas, battery straps, camera clearance, wire routing, and access for maintenance in the physical plan. The part you forgot to leave space for is usually the one you need to reach later.
Save the evidence, including the unknowns
Give every uncertain combination a question mark and write the question in ordinary language. “Does this exact receiver support this radio module and firmware?” is a question a manufacturer or knowledgeable helper can answer.
A worksheet that reveals one unresolved question has done its job. It has stopped you paying to discover the answer. Once the setup is working, keep that record as the starting point for future changes.
MAKE IT USEFUL
Your next small job.
Fill in all five categories in the kit planner. Leave uncertain items marked unresolved until you have documentation.
Go straight to the source.
These official resources support the next step. Hardware, firmware, and local requirements can differ.