Serial vs Cellular vs Licensed Radio Backhaul
Every remote site needs a way to move its data to the master, and the physical link you choose - a wired serial run, a cellular modem, or a licensed radio - sets your monthly cost, your latency, and how much of the path you control. This page is for the engineer specifying backhaul at a well pad, a lift station, or a tank battery. It compares the three on reach, ownership, and recurring cost, then gives a rule for choosing.
Serial vs Cellular vs Licensed Radio in one line: Choose serial when the master or a gateway is within a short wired run and you want no recurring cost or airtime dependency. Choose cellular where carrier coverage exists and you want fast deployment with no tower to license, accepting a monthly plan and dependence on the carrier. Choose licensed radio for many sites in one area with no coverage or where you must own the link, trading upfront infrastructure for zero airtime fees and full control.
Compare Reach, Ownership, and Cost
These three options differ less in what data they carry and more in who owns the path and what it costs to keep running. Serial is a short wired link you own outright. Cellular rents a carrier's network by the month. Licensed radio is infrastructure you build and license once, then run with no per-message fee.
| Attribute | Wired serial | Cellular | Licensed radio |
|---|---|---|---|
| Reach | Short cable run | Anywhere with carrier coverage | Line-of-sight over an owned area |
| Who owns the path | You | The carrier | You, under a license |
| Recurring cost | None | Monthly data plan | License fees, no airtime |
| Upfront effort | Cabling | Modem and SIM | Towers, antennas, licensing |
| Deployment speed | Fast if close | Fast | Slow - survey and license |
| Best fit | Nearby devices | Scattered sites in coverage | Site clusters, no coverage |
The comparison maps closely to the wireless-only tradeoffs in cellular vs satellite vs radio telemetry, but here the deciding axis is ownership and recurring cost across wired and wireless together.
None of these is universally best; each optimizes a different constraint. Serial minimizes cost and dependency but demands proximity. Cellular minimizes deployment friction but rents the path forever. Licensed radio minimizes recurring cost and maximizes control but front-loads a real project. Pick by which constraint dominates your site: distance, speed to deploy, or long-run cost and ownership.
When Each One Wins
Serial wins on proximity and simplicity. Where a device is within a modest cable run of the RTU or gateway - a transmitter to a nearby panel, a skid to a control building - an RS-485 serial link carries the data with no modem, no plan, and no airtime. It is the cheapest and most reliable option when the geometry allows it, and it often sits underneath the wireless hop, feeding a local gateway that then backhauls.
Cellular wins on speed and spread. For sites scattered across a region that all sit inside carrier coverage, a cellular modem gets each one online in an afternoon with no infrastructure to build. You accept a monthly plan per site and a dependency on the carrier's network, but you skip tower surveys and licensing entirely. It is the default for a handful of remote sites where coverage exists and time-to-deploy matters.
Licensed radio wins when you have many sites in one area, poor or no cellular coverage, or a hard requirement to own the communications path. Once the towers and licenses are in place there is no per-message cost, and you control the link's availability rather than relying on a carrier. The math favors it as site count in a cluster rises, because the fixed infrastructure amortizes across many nodes that would each otherwise carry a monthly bill. The technology is covered in licensed radio telemetry.
Backhaul Selection Pitfalls
The serial pitfall is stretching it past its distance and noise limits, then blaming the protocol for errors that are really cable problems. Serial is superb within its range and unforgiving beyond it, so respect the physical limits and treat a long, noisy run as a reason to move the gateway closer, not to push harder. Its role is usually the last local hop, not the wide-area backhaul itself.
The cellular pitfall is treating the monthly plan as free and polling as if bandwidth were unlimited. A site that full-polls over cellular racks up cost for unchanged data, so pair the link with report-by-exception and store-and-forward so it sends only what changed and rides out outages. The recurring bill, not the hardware, is the real cost of cellular at fleet scale. Buffering through dropouts is covered in store-and-forward telemetry.
The licensed-radio pitfall is underestimating the project: path surveys, licensing, fade margin, and tower access are real work, and a link engineered without margin drops in weather. The upside is that once it is right you own it. Whichever backhaul you choose, a cloud SCADA such as Merobix simply reads the data once it arrives, so the decision is about getting bytes home affordably and reliably - by proximity, by coverage, or by ownership - not about the platform on the other end.
Frequently Asked Questions
When is licensed radio worth the upfront cost over cellular?
When you have many sites clustered in one area, when cellular coverage is poor or absent, or when you must own the communications path. Licensed radio front-loads towers and licensing but then carries no per-message airtime fee, so the fixed cost amortizes across many nodes that would each otherwise pay a monthly cellular plan. As site count in a cluster rises and where you need control over availability, the radio math wins.
Can I mix serial with a wireless backhaul?
Yes, and it is common. Serial usually serves as the last local hop - a transmitter or skid wired to a nearby gateway over RS-485 - while the gateway then backhauls the aggregated data over cellular or licensed radio to the master. You are choosing per hop: serial for proximity where cabling is cheap, wireless for the wide-area distance the cable cannot cross. The layers complement rather than compete.
Why does report-by-exception matter for cellular backhaul?
Because cellular charges by data, and full polling sends unchanged values every cycle, turning a quiet site into a steady monthly bill. Report-by-exception sends a value only when it moves past a deadband, so the link carries meaningful change instead of repetition. Combined with store-and-forward buffering to ride out coverage dropouts, it makes cellular backhaul both cheaper and more resilient at fleet scale.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.