What Is Licensed Radio Telemetry?

Back to Blog

How Licensed Radio Telemetry Works

A licensed radio network is usually built as point-to-multipoint: a master radio at a central or elevated location polls many remote radios at the field sites, often through repeaters that extend coverage over terrain. Each remote radio connects to an RTU or PLC and carries its serial or IP data over the air on the licensed channel. In North America these systems commonly use narrowband VHF and UHF allocations, including Multiple Address System (MAS) frequencies set aside for exactly this purpose.

The word licensed is the whole point. The operator applies for and holds an FCC (or national regulator) license to a specific frequency in a specific area, which gives that channel legal protection from interference. That exclusivity is what makes the link predictable enough to trust with critical telemetry.

Licensed vs Unlicensed, and Where It Fits

Unlicensed spread-spectrum radios (for example in the 900 MHz or 2.4 GHz ISM bands) need no license and are cheap to deploy, but they share the band with everyone else and can suffer interference. Licensed narrowband radios cost more and require paperwork, yet deliver protected, longer-range links - a worthwhile trade for a pipeline or gathering system that must not drop data.

Licensed radio's advantages are no recurring airtime cost, no dependence on a carrier, and full operator control. Its limits are lower bandwidth and the effort of owning the infrastructure. Many operators now run radio for the field backbone and hand off to cellular or satellite for the trip to the cloud, where a platform such as Merobix reads the aggregated RTU data over DNP3 or Modbus.

Getting a Channel: Licensing and Path Planning

A licensed link starts on paper, not on a tower. The workflow runs: identify candidate frequencies through a frequency coordinator, submit the application to the regulator with the proposed master, repeater, and operating area, and receive a grant that specifies the frequency, transmit power, emission type, and locations. Change any of those materially and the license must be modified, not just the radio. Before committing to the paperwork, run a path study for every hop - terrain profile, tower heights, and clearance along the whole route - and verify the path with Fresnel zone math rather than assuming that visual line of sight is good enough. A path that barely works on the survey day will not survive wet foliage and ice loading.

Treat the grant as a living asset. Licenses run for a fixed term and lapse if nobody renews them, and regulators have periodically tightened channel-width rules over the years, forcing equipment swaps on older systems. Keep the license record, the authorized coordinates, and the as-built power settings filed with the radio documentation, because a mismatch between what the license says and what the field actually transmits is a compliance problem that tends to surface at the worst possible moment - usually in the middle of an interference dispute you would otherwise have won.

A Side-by-Side Selection Table

Criterion	Licensed narrowband	Unlicensed spread spectrum
Regulatory effort	Coordination and license application	None
Interference protection	Legal exclusivity on the channel	Shared band, best effort
Channel capacity	Narrow channel, modest data rate	Wider channels, more throughput
Recourse if disrupted	Regulator enforcement against the interferer	Change frequency or hardware and hope
Long-term ownership	Operator owns channel and infrastructure	Operator owns hardware only

The rows worth weighting most are the last two. Exclusivity is not just a technical property - it is legal standing, and it matters precisely when something goes wrong. Licensed narrowband earns its paperwork on backbone links that must run for decades through a crowding RF environment; unlicensed earns its simplicity on short hops, temporary pads, and links you can afford to re-engineer if the neighborhood gets noisy. The full decision process is covered in choosing between licensed and unlicensed radio.

Sizing the Poll Cycle on a Narrowband Channel

Narrowband channels are half duplex and shared by every site on the frequency, so the poll cycle is arithmetic, not preference. If the master polls N remotes and one complete transaction - request, radio turnaround, response - takes t seconds, a full sweep of the system takes roughly N x t. Every hop through a repeater roughly doubles the airtime for that site's transaction, because the message is transmitted twice. Add ten sites to a network and the update interval for every existing site stretches accordingly; the channel does not get wider because the field got bigger.

That arithmetic drives design choices. Critical sites can be polled more often by giving them multiple slots per sweep, at the cost of everyone else's update rate. Alarms at a remote normally wait for that site's next slot unless the system supports unsolicited or exception reporting, which is worth enabling where the radios and protocol allow it. Working through the numbers for a real system is the subject of setting the poll cycle for a radio SCADA network - the point here is that on licensed narrowband, cycle time is a budget you spend deliberately.

Failure Modes and Field Diagnostics

Radio networks rarely die suddenly; they erode. Received signal strength drifts down seasonally as foliage fills in, water works into a feedline and shows up as rising reflected power, connectors corrode, and a path that had comfortable margin at commissioning starts dropping polls in rain. The defense is to historize the radio diagnostics themselves - signal strength and poll success rate per remote - as SCADA tags, so degradation is a visible trend long before it becomes an outage and a truck roll.

Interference can still happen despite the license: a distant co-channel licensee can arrive on unusual propagation, and co-located transmitters at a shared tower site can mix into intermodulation products. Pattern is the diagnostic - errors clustered by time of day or weather point at propagation, errors clustered by repeater branch point at infrastructure. Map which remotes depend on which repeater, because a repeater power or battery failure takes out its whole branch at once, and that signature reads as topology, not as radio trouble at each individual site.

Frequently Asked Questions