The Range–Data-Rate–Power Triangle

Every wireless link lives in a triangle with three corners: range, data rate, and power. You cannot maximize all three at once — a link that goes far and sends lots of data burns lots of power; a link that sips power either goes short or sends little. Every protocol is just a particular point inside this triangle.

The mistake most teams make is picking a protocol by reputation — “LoRa is the long-range standard” — instead of by asking what their device actually needs from the triangle. That’s how you end up with a link that’s wrong for the application.

LoRa: Long Range, Low Power, Low Data Rate

LoRa (and LoRaWAN) is engineered for exactly one thing: sending small amounts of data over long distances at very low power. Its range can reach kilometers in open terrain, and its power draw is tiny — which is why it dominates agricultural, industrial, and asset-tracking applications.

The cost is data rate. LoRa sends tens of bytes per transmission, not video or rich telemetry. For a tracker that only needs to report its position occasionally, that’s perfect. For a device that needs to stream continuous data, it’s a poor fit. LoRa’s other consideration is that LoRaWAN depends on network infrastructure — gateways — unless you run point-to-point.

ELRS: Long Range, Low Latency — But a Different Use Profile

ExpressLRS (ELRS) is a different animal. It’s an open-source radio link built for drone pilots, and it delivers remarkable range and very low latency at low power. In many ways it outperforms LoRa on the raw radio link.

The difference is what it’s designed around. ELRS is optimized for a continuous control-and-telemetry link between a pilot and a vehicle — not for a device that wakes up, sends a tiny position packet, and sleeps. Its data model, latency characteristics, and ecosystem are tuned to a real-time control loop, not a low-duty-cycle tracking pattern. That doesn’t make it wrong for tracking — but it makes it a decision, not a default.

Plain RF and Proprietary Links

Below the named protocols is plain RF — raw sub-GHz or 2.4 GHz transceivers with a custom protocol. This gives you full control over the link: you can tune the data rate, the duty cycle, the packet size, and the power precisely to your application, with no dependency on any external network or ecosystem.

The cost is that you own the protocol — its reliability, its error handling, its interference behavior. That’s engineering effort, and it’s only worth it when the off-the-shelf protocols genuinely don’t fit. For a device with unusual requirements, a custom link can be the right answer; for a standard tracker, it’s usually overkill.

What a Falcon Tracker Actually Needs From Its Link

Let’s ground this in a concrete case. A falcon tracking device needs to report position occasionally — not continuously — over a long range, from a device with a tiny battery and a tight weight budget. It doesn’t need low latency. It doesn’t need high data rate. It needs to send a small position packet, reliably, over distance, without draining the battery.

Read that against the triangle and the answer starts to clarify itself: a low-data-rate, long-range, low-power link — which is precisely LoRa’s home territory. But the choice still depends on specifics: does the user have a gateway infrastructure, or is this point-to-point to a handheld receiver? The application’s answer determines the protocol, not the protocol’s marketing.

Matching the Link to the Real Usage Pattern

The way to choose a link correctly is to start from the usage pattern, not the protocol. Ask:

• How much data per transmission? A position packet, or rich telemetry?
• How often does it transmit? Once an hour, or ten times a second?
• What range is actually needed? Meters, kilometers, or tens of kilometers?
• What latency is acceptable? Seconds, or milliseconds?
• What infrastructure exists? A network, a handheld receiver, or a phone?

Answer these honestly and the right protocol usually falls out. Skip them and you get a link that’s wrong for reasons you’ll discover in the field.

Conclusion

The right radio link is a three-way trade between range, data rate, and power — and “LoRa is best” is a lazy answer. The correct choice depends on what the device actually does, how often it talks, and what infrastructure it talks to.

Match the link to the usage pattern, not the protocol to the reputation. That’s the difference between a tracker that communicates reliably for months and one that’s technically long-range but practically useless.

I Work FOR YOU, Not Factories.

Choosing the Right Wireless Link for Your Device?

If you’re weighing radio protocols against a real usage pattern — range, duty cycle, data needs, infrastructure — that’s the kind of RF and firmware decision I help with, on the ground in Shenzhen.

• Email: [email protected]
• WhatsApp / WeChat: +86 130 4084 3518
• Website: www.easelinktech.com

Your Trusted Local Insider For 3C Sourcing In Shenzhen, China.