Which Wireless Links Do Drones Use for Commands and Data?

• Controller, left
• Drone, right
• Outbound command, upper arrow

What you will learn

• Trace command and telemetry paths between system components.
• Compare telemetry radios, Wi-Fi and cellular service using shared criteria.
• Recognize why a drone design may need to consider more than one link.

Before you start

No flight experience is needed. Telemetry means status data, such as position, sent back for an operator or software to observe.

A link has several endpoints

A command travels from ground software to a receiver or onboard computer and then to the flight controller; status travels back along the corresponding path. In a documented PX4 setup, a telemetry radio can provide a wireless MAVLink connection between a ground station and the vehicle. If a companion computer is present, it can also route data toward a ground station or another network. These are logical roles; one product may combine several roles in one device.

MAVLink specifies message encoding, not a radio wave. The endpoints need a compatible protocol, while the transport layer determines whether messages travel over a serial cable, telemetry radio, Wi-Fi or a route through cellular service. So “MAVLink works” does not tell you whether the link has enough coverage or capacity for a task.

How should you compare link types?

No single option wins on every criterion. PX4 documentation describes dedicated telemetry radios and Wi-Fi telemetry; Wi-Fi typically has shorter range but higher data rates, making it more suitable when video also needs transport. The guide also describes an LTE module attached to a companion computer to route MAVLink over the internet, rather than plugging that module directly into the flight controller.

This is a qualitative comparison, not a promise about distance or throughput. Latency also depends on network load, configuration and routing; one modem's figures cannot represent every location. Useful coverage can differ from advertised coverage because obstacles, interference and antenna placement change the real link.

Why do commands and telemetry need different delivery patterns?

Telemetry is often a stream of changing values. If an old position sample arrives late after a newer one is available, an application may care more about the newer sample. By contrast, when changing configuration or synchronizing a mission list, the sender needs to know whether the operation was received; the MAVLink protocol describes point-to-point exchanges with retransmission for transactions that need guaranteed delivery.

That does not mean every control message has been confirmed just because a link is active. An application should distinguish “packet arrived,” “command accepted” and “request completed.” Each state answers a different question. If a reply is missing, software should report an unknown outcome instead of assuming success.

A worked scenario

Imagine a simulator where a laptop displays position over a telemetry radio while an onboard companion computer sends images over Wi-Fi. Trace the two flows: the application creates a request, a message crosses its selected connection to the controller, telemetry returns to update the interface, and video reaches the viewer. If the picture freezes while position keeps updating, the fault may be in the video path; if both stop, inspect components shared by the paths or the data source. This is fault-isolation reasoning for a model, not a test result from a drone.

A fallback design should state which information remains available if one path fails. Two radios that share a power supply, sit next to each other or depend on the same computer do not provide independent redundancy.

Common misunderstandings

MAVLink is not the name of a radio. It defines messages and communication rules; a radio is one transport choice.

Signal bars do not prove a command ran. Signal strength does not replace a reply or the controller's reported state.

Frequently asked questions

Do drones use Wi-Fi to receive commands?

A setup can use Wi-Fi telemetry, but a particular drone's link depends on its hardware and implementation.

Does cellular service connect directly to the flight controller?

The PX4 guide describes an LTE module connected to a companion computer to route MAVLink; it does not describe plugging that module directly into the flight controller.

How do I choose a link?

First identify the data, coverage, bandwidth, latency, available infrastructure and loss-detection needs; then confirm that the actual equipment meets those requirements.

Summary

• Commands and status pass between ground software, vehicle and controller through defined endpoints.
• Telemetry radios, Wi-Fi and cellular service trade off coverage, data capacity and infrastructure differently.
• A message protocol cannot guarantee that a wireless link has suitable quality.