DroneLabs.AI

Understanding Drone Components and Their Variations

Arya Aggarwal — Tue, 25 Aug 2026 15:03:26 GMT

Understanding the role of each drone component makes it easier to troubleshoot problems and choose the right parts for a specific build. Different types of drones can also require very different components. An FPV drone, for example, may use a battery with a high C-rating to provide the current needed for rapid acceleration, while a development-focused drone may prioritize battery capacity and efficiency instead.

In this article, I break down the purpose of the main components found in a drone build and explain some of the variations you may encounter. Keep in mind that these are general categories, and the specific components you need will depend on the type of drone you are building.

1. Frame

The frame provides the structure of the drone and gives the other components a place to mount. Frame design has a major effect on what hardware can be installed and how the drone behaves in flight.

Holds the motors, flight controller, battery, and other components in place
Determines the available mounting space for equipment and payloads
Helps determine which propeller sizes can be used
Smaller, lighter frames are common on agile FPV drones, while larger frames such as the X500 provide more room for batteries, sensors, cameras, and companion computers

Frame size does not determine propeller size by itself, but the two are closely related. A larger frame can generally accommodate larger propellers, while the motor and power system must also be capable of turning those propellers efficiently.

^Source:^{Image 1}^,^{Image 2}

2. Propulsion System

The propulsion system is responsible for producing the thrust that keeps the drone in the air and allows it to move. The motors, propellers, and ESCs have to work together, so changing one often requires changes to the others.

Motors

Motors convert electrical energy into mechanical rotation that spins the propellers. On a typical multirotor, the flight controller constantly changes the speed of individual motors to control the aircraft’s movement.

Spin the propellers to produce thrust
Increase or decrease speed independently to control the drone’s attitude and movement
Usually installed in alternating clockwise and counter-clockwise directions so that the drone’s rotational forces balance each other
Need to be matched with the propellers, battery voltage, and ESCs being used

A motor spinning faster produces more thrust, while changing the relative speed between motors allows the flight controller to control roll, pitch, and yaw.

Propellers

Propellers convert the motor’s rotation into thrust. Their diameter, pitch, and design have a major effect on how efficiently the drone produces lift.

Larger propellers can generally produce more thrust and can be efficient for lifting heavier aircraft
Smaller propellers tend to be easier to accelerate and are common on lightweight, agile drones
Higher-pitch propellers can increase the amount of air moved per revolution but also require more torque and power
Propellers must be selected to match the motors and the rest of the power system

Because propellers affect motor load, motors, propellers, and ESCs should be treated as a system rather than selected independently.

^Source:^{Image 1}^,^{Image 2}

ESCs (Electronic Speed Controllers)

The ESC sits between the power system and the motor. It receives commands from the flight controller and controls how much electrical power is delivered to the motor.

Controls the speed of an individual motor
Converts the flight controller’s motor command into electrical switching that drives the motor
Must be rated for the motor, battery voltage, and expected current
Can use different communication protocols, such as PWM, OneShot, or DShot

The specific protocol depends on the flight controller and ESCs. PX4, for example, supports several ESC protocols, including PWM, OneShot, DShot, and DroneCAN. DShot is a digital protocol that also avoids the traditional throttle calibration required by PWM-based ESCs.

Motor Control Signal

The flight controller needs a way to communicate the desired motor output to each ESC. This is not a separate physical component, but rather the communication link between the flight controller and ESC.

Common protocols include PWM, OneShot, and DShot. The choice depends on the hardware and flight-control software being used.

3. Power System

The power system supplies electricity to the motors, flight controller, and other electronics. Choosing the correct battery and power hardware is especially important because the electrical requirements of the propulsion system can vary significantly between drones.

Battery

The battery stores the electrical energy used by the drone. LiPo batteries are commonly used in RC aircraft because they provide a high amount of power while remaining relatively lightweight.

Three battery specifications are especially important when choosing a battery:

Capacity (mAh): Measured in milliamp-hours, this indicates how much electrical charge the battery can store. A higher-capacity battery can generally provide more energy, but it is also heavier, so there is a tradeoff between flight time and weight.
C-rating: The C-rating represents how much current a battery is designed to deliver relative to its capacity. A rough way to calculate the rated maximum discharge current is to multiply the battery’s capacity in amp-hours by its C-rating. For example, a 5 Ah battery rated at 40C would have a theoretical rating of 200 A. Actual performance depends on the battery and its manufacturer.
Cell count (S): The S-rating describes how many individual LiPo cells are connected in series. More cells increase the pack’s voltage. For example, a 4S LiPo has four cells connected in series and a nominal voltage of about 14.8 V.

A higher C-rating is not automatically better. The battery should be chosen based on the current required by the motors and the rest of the electrical system, while also considering its weight and capacity.

Charger

A charger replenishes the battery’s energy after a flight. LiPo batteries require chargers designed for lithium-polymer batteries, and multi-cell packs are normally charged using a balance connection so that the individual cells remain at the correct voltage relative to one another.

The charger must be configured for the battery’s cell count and charging requirements. Using the wrong settings can damage the battery.

Power Module

The power module connects the battery’s electrical system to the flight controller. It provides regulated power for the flight controller and can measure battery voltage and current.

This information is sent to the flight controller so the software can estimate how much battery capacity remains and trigger low-battery warnings or other failsafes. It is therefore more accurate to think of the power module as providing the measurements used to estimate remaining battery capacity rather than directly measuring a simple “battery percentage.”

Power Distribution Board (PDB)

A power distribution board takes the battery’s main power connection and distributes it to the components that need it, particularly the ESCs and motors.

Splits the battery connection into multiple power outputs
Helps simplify the drone’s wiring
Some PDBs also include additional power regulation or battery-monitoring circuitry

Not every modern drone needs a separate PDB. Some systems combine power distribution with other electronics, while certain flight controllers or ESC setups have different power architectures.

4. Flight Control & Navigation

Flight Controller

The flight controller is the central computer responsible for stabilizing and controlling the drone. It receives information from sensors and other systems, determines what the aircraft needs to do, and sends commands to the motors.

Processes sensor data to determine the drone’s orientation and movement
Controls the motors through the ESCs
Connects to peripherals such as GPS receivers, radio receivers, telemetry radios, and companion computers
Different flight controllers have different processors, sensor configurations, memory, and numbers and types of ports

The flight controller is the part that ties the rest of the system together. Even though the motors provide the thrust, the flight controller determines how that thrust is distributed to keep the drone stable and make it move as commanded.

GPS Module

A GPS module provides the flight controller with information about the drone’s position and movement. GPS is especially useful for drones that need navigation features beyond basic manual stabilization.

Provides position information
Enables features such as GPS-assisted position hold
Can be used for waypoint missions and other autonomous navigation features
Provides important information for features such as GPS-based return-to-home

GPS is not necessary for every type of drone. Many small FPV drones, for example, can fly without it, while autonomous and development-focused platforms often benefit greatly from having a GPS module.

5. Communication Systems

Drones commonly have multiple communication links. One connects the pilot to the aircraft, while another can connect the flight controller to a ground station or computer.

Transmitter and Receiver

The transmitter is the controller used by the pilot to send commands to the drone. The receiver is installed on the drone and passes those commands to the flight controller.

The exact protocols used depend on the equipment. For example, ExpressLRS is a radio-control system, while an ExpressLRS receiver commonly communicates with the flight controller over the CRSF serial protocol. Other receivers may use protocols such as SBUS.

When selecting a transmitter and receiver, make sure they are compatible with each other and that the receiver can communicate with your flight controller using a supported protocol.

^Source:^{Image 1}^,^{Image 2}

Telemetry Radio

A telemetry radio provides a separate wireless connection between the drone and a ground station.

Instead of carrying the pilot’s stick commands, this link can be used to send information such as flight status, position, battery data, and other telemetry between the aircraft and a computer. It can also allow a ground station to send commands to the flight controller.

This type of connection is particularly useful for development and autonomous drones because it allows you to monitor and interact with the vehicle from a computer without requiring the computer itself to be mounted on the drone.

If you would like to read more about using code to fly a drone, you can read about it here: Testing Autonomous Drone Movement with PX4 Python Scripts.

6. Regulatory Compliance

Remote ID Broadcast Module

Remote ID is a regulatory requirement that applies to many drones in the United States. Rather than being a flight component, a Remote ID module is part of the system used to meet FAA identification requdddddddirements.

A Remote ID broadcast module broadcasts identification and location information while the drone is flying. The FAA describes it as a way for other parties to receive information about the drone and, depending on the type of Remote ID system, the control station or takeoff location.

In the United States, drones that are required to be registered or are registered generally must comply with Remote ID. There are different ways to comply, including using a Standard Remote ID drone, attaching an approved broadcast module, or operating within an FAA-Recognized Identification Area (FRIA) when the applicable requirements are met.

Because drone regulations can change and may differ by location and type of operation, always check the current rules before flying.

Here Are the Parts I Used

The following are the main components I used for my development-focused drone build:

Frame: Holybro X500 V2 ARF Kit
Battery: Tattu 5200mAh 14.8V 35C 4S
Flight controller: Holybro Pixhawk 6C
Power module: Holybro PM02 V3
Battery: Tattu 5200mAh 14.8V 35C 4S LiPo
GPS: Holybro M10 GPS
Transmitter: RadioMaster Boxer
Receiver: RadioMaster RP3-H ExpressLRS 2.4GHz Nano Receiver
Telemetry radio: Holybro SiK Telemetry Radio V3
Remote ID module: Holy Stone Remote ID Broadcast Module

Testing Autonomous Drone Movement with PX4 Python Scripts

Arya Aggarwal — Sat, 25 Jul 2026 21:40:30 GMT

Previously, I had only used one basic Python script to fly my drone: take off, hover, and land.

My next goal was to understand how to control each axis of movement in a controlled way: pitch (tilting the drone forward and backward), roll (tilting the drone left and right), and yaw (rotating clockwise and counterclockwise about its vertical axis), before combining them into more complex flight paths.

First, I started with pitch. To test it, I simply added a forward pitch maneuver to the first script. Once that worked reliably, I was ready to build on it with more complex movements.

With pitch working, I decided to move on to something a little more challenging by introducing roll. I expanded the pitch test so the drone flew in a square path and moved diagonally twice using both pitch and roll. This let me verify both roll and the drone’s ability to execute several movements together in a single mission.

The third axis of movement I focused on was yaw. To test it, I modified the first program so that the drone rotated to a heading of 180 degrees after takeoff. The program worked perfectly in simulation, so I loaded it onto the drone expecting similar results. However, after attempting to change its heading, it struggled to stay airborne and slowly descended back to the ground. I still haven’t determined the exact cause—stay tuned to find out.

It was my first reminder that simulation doesn’t always reflect what happens in the real world and that it is crucial to experiment on actual hardware. The simulator is great for developing and verifying code, but it can’t perfectly capture every behavior of the actual drone.

Building My Holybro X500 V2 Drone: 5 Unexpected Problems I Had to Solve

Arya Aggarwal — Mon, 20 Jul 2026 22:18:36 GMT

About two weeks ago, I finished building my Holybro X500 V2 drone. Even though I had done thorough research before buying the parts, the build itself was much more challenging than I expected. Several unexpected issues came up along the way, and there weren’t many resources covering the specific problems I ran into. That meant I had to troubleshoot and figure out most of them on my own. Here are some of the biggest challenges I encountered and how I solved them.

1. The Wrong Power Module

The first issue came before I could even power the drone. I had purchased my power module in a bundle with the Pixhawk 6C flight controller and GPS, assuming everything would be compatible. However, when I started wiring everything together, I realized the included power module only had one female XT60 port and a JST-GH connector. It was missing the male XT60 output needed to connect to the power distribution board, making it impossible to wire the system correctly.

To solve this, I purchased the Pixhawk PM02 V3 12S Power Module separately. Unlike the bundled version, it included the necessary battery, power distribution board, and flight controller connections, allowing me to continue with the build.

2. Only Two Motors Would Spin

Once I had power flowing to both the flight controller and the motors, I connected the Pixhawk to QGroundControl to verify the motor configuration. QGroundControl also allowed me to spin up each motor individually, but I quickly noticed that only two of the four motors responded.

At first, I assumed two of the motors or ESCs were defective. After inspecting the PWM module more closely, I noticed that two of the ESC connectors had their wire colors facing the opposite direction from the other two. I flipped those two connectors around, plugged them back in, and all four motors immediately started working.

3. Choosing the Wrong Receiver

The next challenge came when setting up my radio system. My RadioMaster Boxer transmitter has built-in ExpressLRS support, but instead of buying an ELRS receiver, I had purchased a Lemon RX DSMX receiver. Although it technically worked, using an external DSMX module with a Pixhawk made the setup much more complicated than it needed to be.

Rather than continuing down that path, I switched to a RadioMaster RP3-H ExpressLRS receiver, which is designed for ELRS and includes a JST-GH connector compatible with Pixhawk systems.

4. The Receiver Cable Didn’t Fit

Unfortunately, installing the new receiver revealed another issue. The RP3-H uses a 4-pin JST-GH connector, while the Pixhawk receiver port uses a 5-pin JST-GH connector. The cable included with the receiver therefore couldn’t connect directly to the flight controller.

To work around this, I bought a JST-GH connector kit with spare housings and wires. Using a needle, I carefully removed each wire from the original 4-pin housing and transferred them into a new 5-pin housing in the correct order. After repinning the connector, I was finally able to connect the rec eiver to the Pixhawk.

5. A Test Flight Mistake

With everything finally assembled, I was ready for my first test flight. The flight itself went well, but I made one mistake that quickly became obvious afterward. I hadn’t secured the two thin receiver antennas, and during the flight one of them swung into a propeller and was cut.

Since a damaged receiver antenna can reduce range and lead to inconsistent signal quality, I replaced the receiver with another RP3-H and made sure to secure both antennas to the front arms of the drone before flying again.

Final Thoughts

Although each of these issues slowed down the build, solving them taught me much more about how the different components of a Pixhawk-based drone work together. Hopefully, documenting these problems and their solutions will save someone else building a similar drone some time and frustration.

If you want to see the full list of parts I used, along with the alternative components I considered before making each purchase, you can check out my other article here:

Getting My Drone to Fly Autonomously with Code

Arya Aggarwal — Mon, 20 Jul 2026 03:31:17 GMT

I’ve built many kinds of AI agents for social media data gathering, but I’ve recently become interested in flying drones using AI. While building AI agents was rewarding, I found myself wanting to move beyond software and explore how AI could interact with the physical world. My interest sparked after reading about counter drones. What fascinated me was how these autonomous systems could navigate, identify, and intercept with minimal human intervention. As I researched further, I realized drones have countless applications, and many industries are only beginning to explore what autonomous drones can do. So I decided to try building one of my own.

I had no idea where to begin, but I figured there must be an open-source platform for writing code for autonomous drones. After a few Google searches, I identified ArduPilot and PX4 as two of the leading platforms for drone development. ArduPilot seemed easier to get started with, but its GPLv3 license requires companies distributing modified versions to make the relevant source code available. PX4, on the other hand, uses the more permissive BSD 3-Clause license, which is better suited to proprietary commercial development. I wanted to stay aligned with industry practices, so I zeroed in on PX4.

With that decision made, I started looking for a drone that would work well with PX4. After comparing many different frame options, I chose the Holybro X500 V2 ARF drone kit because it’s well documented, officially supported by PX4, and leaves plenty of room for future expansion. The next step was finding the right flight hardware (flight controller, GPS module, etc.). This was quite a tedious process, and if you want to see all the parts I considered or build a drone of your own, you can check out that post here: https://www.linkedin.com/posts/arya-aggarwal-906789283_building-my-holybro-x500-v2-every-part-share-7483796222412103680-DSZK/.

Once I had built the drone, I began figuring out how I could fly it autonomously using code. I was about to start coding when I realized I still needed a way to test it. Of course, I could have just tried it directly on the drone, but I had spent around $1,000 building it and wasn’t thrilled about risking a crash. So I started looking for ways to simulate flying the drone with code, which led me to QGroundControl. QGroundControl is a drone planning and simulation program that can run programs with realistic drone behavior and physics.

Now that I had testing covered, I wrote my first program, which simply armed the drone, took off to around 3 feet, hovered for 10 seconds, and then landed. This was just to ensure the simulator was running properly and that there would be no surprises when moving from the simulator to the actual drone.

Testing and programming this script taught me some important lessons. First, I learned how to use QGroundControl to simulate running code, how to set it up, and how to read crucial flight data like speed and altitude. I also learned how to run programs on my drone using my telemetry radio and computer, so I don’t need an onboard companion computer for development.

Building My Holybro X500 V2: Every Part — and the Alternatives I Considered

Arya Aggarwal — Fri, 17 Jul 2026 02:07:44 GMT

A breakdown of every component in my X500 V2 build: what each part actually does, and a look at the other options I considered for each one.

1. The Frame — Holybro X500 V2 ARF Kit

The frame is the physical skeleton of the drone — it holds the motors, electronics, and battery together and gives the aircraft its shape and rigidity. An ARF (”Almost Ready-to-Fly”) kit takes this a step further by including the motors, propellers, speed controllers, and wiring already installed, so you’re not starting from a pile of raw parts. I used the Holybro X500 V2 ARF kit, which gave me a ready-to-fly foundation right out of the box aside from adding the flight controller and other electronics. It’s built specifically to work well with the kind of open flight-control hardware used elsewhere in this build.