Latest › Build a Drone with a Bot: Software and Hardware Series

Parts Before Purchase: Using a Bot to Check Drone Component Compatibility

GuideBy Bot Tutorials · Published Nov 3, 2026 · Facts last verified Nov 1, 2026

Next in this series: Tomorrow: Power and Battery Sizing Sanity Checks, with a Bot Doing the Arithmetic · The day after: Reviewing Bot-Written Flight Code: A Cheat Sheet with a MAVSDK Example · Series hub

Use a bot to double-check frame, flight controller, ESC, motor, prop and battery choices, then let the spec sheets settle every answer.

A drone is a system. The frame decides the prop size, the props and motors decide the current draw, the current decides the ESC and battery, and the flight controller has to support the firmware you want to run. Change one part and the others may stop fitting. This guide shows how to use a bot as a careful second pair of eyes on a parts list, and how to let the manufacturers' spec sheets have the final say.

A ground rule up front: we don't quote prices or specs here, and you shouldn't take them from a bot either. Prices change weekly, models get revised, and a bot's training data may be months old. Use the bot for reasoning. Use the spec sheet for numbers.

Step 1: write a build brief

Bots give generic answers to generic questions. Before you ask anything, write a short brief:

Purpose: for example, smooth camera footage, learning autonomy with GPS missions, or freestyle FPV.
Firmware goal: ArduPilot or PX4 for GPS missions and scripting, or Betaflight for manually flown FPV. The Betaflight wiki covers the FPV side, and ArduPilot's docs cover autonomy.
Size class: prop diameter or frame wheelbase, if you already know it.
Weight target: remember the FAA's 250 gram registration line for recreational flyers, though Remote ID and other rules apply above it.
What you already own: radio, goggles, charger, batteries.
Skill level and whether you can solder.

Then prompt:

Here is my build brief: [paste]. Don't recommend specific products yet. First list the compatibility constraints between frame, flight controller, ESC, motors, propellers, battery and receiver that I must check, and tell me which spec-sheet field settles each one.

You're asking the bot to build you a compatibility matrix before it suggests anything you could buy.

Step 2: the compatibility matrix

A good matrix covers at least these pairs. For each one, the bot should name the field to read on the spec sheet:

Pair	What has to match	Where the answer lives
Frame ↔ props	Maximum prop diameter the arms allow, with clearance	Frame spec sheet
Frame ↔ FC/ESC stack	Mounting hole pattern and standoff height	Frame and stack spec sheets
Motor ↔ prop	Prop sizes the motor maker lists in its thrust table	Motor thrust/performance table
Motor ↔ battery	Cell count (voltage) the motor is rated for	Motor spec sheet
ESC ↔ motor	Continuous current rating above the motor's maximum draw from the thrust table	ESC and motor sheets
ESC ↔ battery	Supported cell count range	ESC spec sheet
FC ↔ ESC	Signal protocol (for example DShot or PWM) and connector type	Both manuals
FC ↔ firmware	Board listed as supported by Betaflight, ArduPilot or PX4	Firmware's hardware list
FC ↔ receiver	Protocol and spare UART	FC manual, receiver manual
Battery ↔ connectors	Connector type, wire gauge	Battery and ESC sheets
GPS/compass (autonomy builds)	Supported module and port	Firmware docs, FC manual

ArduPilot's "Connect ESCs and Motors" page is a good check here. It shows motor order and direction for each frame type, so your wiring plan matches what the firmware expects.

Step 3: let the bot read spec sheets with you

Bots are useful at reading dense spec sheets. Paste in the text of a motor thrust table or a flight controller manual's port list, and ask:

From this text only, list the rated cell count, recommended props and maximum current. If a value isn't in the text, write "not stated". Don't fill gaps from memory.

"From this text only" plus "not stated" is the key anti-hallucination pattern. Without it, many bots will fill in a plausible-looking number. Ask it to quote the line each value came from, so you can check.

Step 4: margin and sanity checks

Once the numbers come from spec sheets, a bot is good at doing the arithmetic and showing its working:

Is the ESC's continuous rating comfortably above the motor's maximum current from the maker's table? Many builders leave headroom. Ask the bot to show the calculation, and check it yourself.
Does the battery's maximum continuous discharge cover the total current of all motors plus electronics? We cover power sizing in its own explainer in this series.
Will the all-up weight keep you in the class you planned, including battery, camera and GPS?

Ask the bot to put the math in a small table you can recompute by hand. If it can't show its working, don't trust the result.

Step 5: firmware support is a hard gate

The quickest way to regret a purchase is to buy a flight controller your chosen firmware doesn't support. Ask the bot what to check, then confirm it yourself in the firmware's own hardware list. For ArduPilot and PX4 autonomy builds, also check the GPS/compass module and any telemetry radio. Many camera builds also want a spare serial port for a companion computer later. Our Raspberry Pi piece covers that.

Red flags in bot answers

Exact prices, or "current best" product lists with no date. Treat these as stale.
Specs with no source. Ask "Which page says that?" and look it up.
Confident claims about a board's firmware support. Confirm them on the firmware's hardware list.
Advice to remove safety features to save weight, such as skipping a power module or disabling failsafes. No.
Anything about carrying or dropping payloads. This series is for hobby, camera and learning builds only, and we don't cover payload release.

Make the bot your build log

Keep one running document with your brief, the matrix, links to each part's spec sheet, and the checks you've done. Paste it in when you start a new chat, and ask the bot to "find inconsistencies between any two parts in this list". It's surprisingly good at catching a 4S motor paired with a 6S battery once everything is written down in one place.

Safety and legal: read this before anything leaves the ground

This series is about hobby, camera and learning drones only. A bot is a helper, not an authority, and everything it says about flight has to be checked.

Simulate before you fly. Run every script and every parameter change in a simulator (ArduPilot SITL, or PX4 SITL with Gazebo) before it goes near a real aircraft. Bot-written code that has never run in simulation does not go on a vehicle.
Check bot advice against official sources. Compare every answer with the ArduPilot, PX4, MAVLink or Betaflight documentation and with the manufacturer's spec sheet for each part. If the bot and the docs disagree, the docs win.
Props off on the bench. Take the propellers off whenever the battery is connected for setup, motor tests or firmware work.
Keep failsafes and geofences on. Don't let a bot talk you into disabling radio, battery or GCS failsafes, or into getting around a geofence or airspace restriction.
Follow the FAA rules in the US. The FAA requires registration for drones of 250 grams (0.55 lb) or more, and for any drone flown under Part 107. Recreational flyers must pass the free TRUST test and carry proof of it. Registered drones need Remote ID, either built in, through a broadcast module, or by flying at an FAA-Recognized Identification Area. Commercial flights need a Part 107 certificate. Stay away from airports and controlled airspace unless you have authorization, keep the drone in sight, and don't fly over people.
Treat LiPo batteries with respect. Charge on a fireproof surface with a balance charger, never leave a charging pack unattended, and retire swollen or damaged packs following the manufacturer's instructions.
Never fly untested code near people. Test first flights in an open, legal area with nobody nearby.

Outside the US, check your national aviation authority's rules. They may be different.

FAQ

Can a bot pick my drone parts for me?

It can help you reason through the choices and spot mismatches, but specs and prices change and bots can be out of date. Each final check has to come from the manufacturer's spec sheet.

What's the most common compatibility mistake?

Mismatched mounting patterns, connectors and voltage ratings: a motor or ESC not rated for the battery's cell count, or a stack that doesn't fit the frame's mounting holes.

Should I choose ArduPilot or Betaflight hardware?

It depends on the goal. Betaflight targets manually flown FPV quads, while ArduPilot and PX4 target autonomous missions with GPS. Check that your flight controller board is supported by the firmware you want.

Sources

Video outline (coming)

Why compatibility checks come before buying
Writing a build brief for the bot
The compatibility matrix: frame, stack, motors, props, battery
Reading a spec sheet with the bot
Firmware support for your flight controller
Red flags in bot answers
Recap: your parts checklist

The narrated video for this piece is in production; this outline is what it will cover.