45 Link Budget and Coverage Planning

Key Concepts

Link Budget: A calculation that sums all gains and subtracts all losses in a radio link to determine the received signal power and link margin
Link Margin: The difference between received signal power and receiver sensitivity; positive margin means the link works, higher margin means more headroom
Receiver Sensitivity: The minimum signal power (in dBm) at which a receiver can correctly decode a packet at a specified error rate
Antenna Gain: The increase in radiated power in the antenna’s preferred direction relative to an isotropic radiator, measured in dBi
Cable Loss: Attenuation in coaxial cable and connectors between the radio and antenna; often 0.5–3 dB per metre for coax at 2.4 GHz
Fade Margin: Extra link margin reserved to absorb temporary signal level drops due to multipath, rain, or obstruction
System Operating Margin: Total link margin after accounting for all losses and including the required fade margin; must be positive for reliable operation

45.1 In 60 Seconds

A link budget determines whether a wireless link will work by summing all gains (transmit power, antenna gains) and subtracting all losses (path loss, cable loss, obstacle attenuation, fade margin). If the received power exceeds the receiver sensitivity, the link succeeds. This calculation is essential for planning BLE beacon spacing, LoRa gateway placement, and Wi-Fi access point coverage in IoT deployments.

45.2 Learning Objectives

By the end of this chapter, you will be able to:

Calculate complete link budgets including all gains and losses
Apply the link success criterion to determine if wireless links will work
Compare protocol ranges for indoor, urban, and rural environments
Design BLE beacon deployments with proper coverage overlap
Plan LoRa gateway placement for urban and rural scenarios

For Beginners: Link Budget

A link budget is like a financial budget, but for signal strength instead of money. You start with how much signal power your transmitter sends out, then subtract losses (distance, obstacles, cable connections) and add gains (antenna boosts). If the signal that arrives is strong enough for the receiver to understand, your link works.

Sensor Squad: The Signal Budget!

“Time to plan our link budget!” announced Max the Microcontroller. “Think of it like counting your pocket money. We start with what we have and subtract what we spend.”

“I start with 14 dBm of transmit power – that is my pocket money,” said Sammy the Sensor. “Then the antenna boosts it by 2 dBi – like finding extra coins! But then I lose signal to the cable, the distance through the air, walls in the building, and we need a safety margin too.”

Lila the LED did the math. “So we add up all the gains and subtract all the losses. If the signal that arrives at the gateway is stronger than its receiver sensitivity – the minimum it can detect – then our link works! If not, we need to move closer, use a better antenna, or remove obstacles.”

“I love link budgets because they prevent surprises,” said Bella the Battery. “Instead of installing 200 sensors and discovering 40% cannot reach the gateway, we calculate BEFORE we deploy. It is like checking if you have enough money BEFORE you go shopping. A good link budget saves time, money, and my precious energy!”

45.3 Introduction

Deploying IoT devices without a link budget is like wiring a building without checking voltage ratings – you might get lucky, or you might waste weeks troubleshooting failed connections. A link budget systematically accounts for every gain and loss between transmitter and receiver, giving you a clear yes-or-no answer before a single device is installed. This chapter walks through the formula, worked examples for LoRa and BLE, and a real-world case study that shows what happens when link budgets are skipped.

Time: ~20 min | Difficulty: Intermediate | P07.C15.U05c

45.4 Link Budget Formula

The link budget sums all gains and subtracts all losses to predict received power:

\[P_{RX} = P_{TX} + G_{TX} - L_{TX} - L_{FSPL} - L_{margin} - L_{obstacles} + G_{RX} - L_{RX}\]

Where:

P_RX = Received power (dBm)
P_TX = Transmit power (dBm)
G_TX = Transmit antenna gain (dBi)
L_TX = Transmit cable/connector loss (dB)
L_FSPL = Free space path loss (dB)
L_margin = Fade margin for reliability (dB)
L_obstacles = Attenuation through materials (dB)
G_RX = Receive antenna gain (dBi)
L_RX = Receive cable/connector loss (dB)

The free space path loss (FSPL) itself depends on distance and frequency:

\[L_{FSPL} = 20\log_{10}(d_{km}) + 20\log_{10}(f_{MHz}) + 32.45\]

where $d_{km}$ is the distance in kilometres and $f_{MHz}$ is the frequency in MHz.

Link Success Criterion:

\[P_{RX} > P_{sensitivity}\]

If received power exceeds receiver sensitivity, the link works. The difference $P_{RX} - P_{sensitivity}$ is the link margin – extra headroom that absorbs real-world fading, rain, and seasonal vegetation changes.

45.5 Worked Example: Long-Range LoRaWAN Link Budget

Scenario: Agricultural sensor 5 km from gateway. Will the link work?

Transmitter (Sensor):

TX power: 14 dBm (25 mW, US 915 MHz limit)
Antenna gain: 2 dBi (small whip antenna)
Cable loss: 0.5 dB

Receiver (Gateway):

Sensitivity: -137 dBm (LoRa SF12, BW 125 kHz)
Antenna gain: 6 dBi (outdoor Yagi)
Cable loss: 2 dB (longer run to rooftop antenna)

Path:

Distance: 5 km
Frequency: 915 MHz
Environment: Rural farmland (n = 2.2)
Required fade margin: 10 dB

Step 1: Calculate FSPL

Calculation	Result	Meaning
Substitute distance and frequency	L_FSPL = 20log10(5) + 20log10(915) + 32.45	Use km and MHz for the 32.45 constant.
Evaluate log terms	L_FSPL = 13.98 + 59.23 + 32.45	Frequency loss dominates this 5 km example.
Free-space path loss	L_FSPL = 105.66 dB	Ideal line-of-sight loss before terrain and fade margin.

Step 2: Calculate environmental loss (rural farmland, n=2.2 vs free space n=2.0)

Calculation	Result	Meaning
Extra exponent above free space	n - 2.0 = 0.2	Rural farmland is close to free space, but not perfect.
Environmental penalty	10 x 0.2 x log10(5000)	Apply the penalty over the full 5 km path.
Added environmental loss	7.4 dB	Reserve this loss before calculating the final margin.

Step 3: Link budget calculation

Link Budget Term	Value	Running Meaning
Transmit power	+14.0 dBm	Radio output power
TX antenna gain	+2.0 dBi	Antenna focuses some energy toward the gateway
TX cable loss	-0.5 dB	Small loss before the signal reaches the antenna
Effective TX power	+15.5 dBm	Power effectively launched into the path
Free-space path loss	-105.66 dB	Distance and frequency loss over 5 km
Environmental loss	-7.4 dB	Rural farmland loss beyond ideal free space
Fade margin	-10.0 dB	Reserve for rain, foliage, and seasonal variation
RX antenna gain	+6.0 dBi	Gateway antenna gain
RX cable loss	-2.0 dB	Loss between gateway antenna and receiver
Received power	-103.56 dBm	Predicted signal at the receiver
Receiver sensitivity	-137.00 dBm	Weakest signal the radio can decode
Link margin	+33.44 dB	Robust link with comfortable reserve

Conclusion: Link works with 33.4 dB of margin – a robust connection that will remain reliable through rain, foliage growth, and seasonal fading.

Putting Numbers to It

Link margin determines reliability under varying conditions.

Margin check	Result
Received power	-103.56 dBm
Receiver sensitivity	-137 dBm
Link margin	-103.56 - (-137) = 33.44 dB

This 33 dB margin means the signal can degrade by 33 dB before the link fails. Real-world degradation sources include:

Degradation source	Example loss	Remaining margin
Moderate rain over 5 km	5 x 0.2 dB/km = 1 dB	About 32 dB
20 m dense foliage	20 x 0.35 dB/m = 7 dB	About 25 dB
Rain plus foliage	1 + 7 = 8 dB	Still more than 25 dB reserve

This is why the example link remains reliable year-round: normal seasonal losses do not consume the full 33 dB margin.

Try It: Link Budget Calculator

Adjust the parameters below to explore how transmit power, antenna gains, distance, and frequency affect the link budget.

Show code

viewof txPower = Inputs.range([0, 30], {value: 14, step: 1, label: "TX Power (dBm)"})
viewof txAntennaGain = Inputs.range([0, 10], {value: 2, step: 0.5, label: "TX Antenna Gain (dBi)"})
viewof txCableLoss = Inputs.range([0, 5], {value: 0.5, step: 0.1, label: "TX Cable Loss (dB)"})
viewof rxAntennaGain = Inputs.range([0, 15], {value: 6, step: 0.5, label: "RX Antenna Gain (dBi)"})
viewof rxCableLoss = Inputs.range([0, 5], {value: 2.0, step: 0.1, label: "RX Cable Loss (dB)"})
viewof distanceKm = Inputs.range([0.1, 50], {value: 5, step: 0.1, label: "Distance (km)"})
viewof freqMHz = Inputs.select([433, 868, 915, 2400, 5000], {value: 915, label: "Frequency (MHz)"})
viewof fadeMargin = Inputs.range([0, 20], {value: 10, step: 1, label: "Fade Margin (dB)"})
viewof envLoss = Inputs.range([0, 30], {value: 7.4, step: 0.5, label: "Environmental Loss (dB)"})
viewof rxSensitivity = Inputs.range([-150, -60], {value: -137, step: 1, label: "RX Sensitivity (dBm)"})

Show code

lbFSPL = 20 * Math.log10(distanceKm) + 20 * Math.log10(freqMHz) + 32.45
lbEffTx = txPower + txAntennaGain - txCableLoss
lbTotalPathLoss = lbFSPL + envLoss + fadeMargin
lbEffRxGain = rxAntennaGain - rxCableLoss
lbReceivedPower = lbEffTx - lbTotalPathLoss + lbEffRxGain
lbLinkMargin = lbReceivedPower - rxSensitivity
lbLinkWorks = lbLinkMargin > 0

html`<div style="background: ${lbLinkWorks ? '#e8f5e9' : '#ffebee'}; border-left: 4px solid ${lbLinkWorks ? '#16A085' : '#E74C3C'}; padding: 12px 16px; border-radius: 4px; margin-top: 8px; font-family: monospace; font-size: 0.95em;">
<strong>Effective TX Power:</strong> ${lbEffTx.toFixed(1)} dBm<br/>
<strong>FSPL:</strong> ${lbFSPL.toFixed(1)} dB<br/>
<strong>Total Path Loss:</strong> ${lbTotalPathLoss.toFixed(1)} dB<br/>
<strong>Effective RX Gain:</strong> ${lbEffRxGain.toFixed(1)} dBi<br/>
<hr style="border-color: ${lbLinkWorks ? '#16A085' : '#E74C3C'}; margin: 6px 0;"/>
<strong>Received Power:</strong> ${lbReceivedPower.toFixed(1)} dBm<br/>
<strong>RX Sensitivity:</strong> ${rxSensitivity.toFixed(1)} dBm<br/>
<strong>Link Margin:</strong> ${lbLinkMargin.toFixed(1)} dB
<span style="font-size: 1.1em; margin-left: 8px;">${lbLinkWorks ? 'Link works' : 'Link fails'}</span>
</div>`

45.6 Protocol Range Comparison

Using link budget and propagation models, we can compare realistic ranges for different IoT protocols across three common environments.

45.6.1 Indoor Office Environment (n=3.0, concrete/drywall)

Protocol	Frequency	TX Power	Sensitivity	Typical Range	Penetration
Wi-Fi 2.4 GHz	2.4 GHz	20 dBm	-90 dBm	50-100 m	2-3 floors
Wi-Fi 5 GHz	5 GHz	23 dBm	-85 dBm	30-50 m	1-2 floors
Bluetooth LE	2.4 GHz	0-10 dBm	-95 dBm	10-50 m	1-2 floors
Zigbee	2.4 GHz	0-10 dBm	-100 dBm	10-100 m	2-3 floors
LoRa 915 MHz	915 MHz	14 dBm	-137 dBm	200-500 m	5+ floors

45.6.2 Urban Outdoor Environment (n=3.5, buildings/reflections)

Protocol	Frequency	TX Power	Sensitivity	Typical Range	Use Case
Wi-Fi	2.4/5 GHz	20-23 dBm	-85 to -90 dBm	100-300 m	Smart city Wi-Fi mesh
BLE	2.4 GHz	0-10 dBm	-95 dBm	50-200 m	Beacon proximity
Zigbee	2.4 GHz	0-10 dBm	-100 dBm	100-300 m	Streetlight mesh
LoRaWAN	868/915 MHz	14 dBm	-137 dBm	2-5 km	City-wide sensors
NB-IoT	700-2100 MHz	23 dBm	-141 dBm	1-10 km	Cellular IoT
Sigfox	868/915 MHz	14 dBm	-142 dBm	3-10 km	Ultra-long range

45.6.3 Rural Open Field (n=2.2, minimal obstacles)

Protocol	Frequency	TX Power	Sensitivity	Maximum Range	Application
LoRaWAN	868/915 MHz	14 dBm	-137 dBm	10-15 km	Farm sensors
Sigfox	868/915 MHz	14 dBm	-142 dBm	15-30 km	Remote monitoring
NB-IoT	700-2100 MHz	23 dBm	-141 dBm	10-35 km	Agricultural IoT

45.7 BLE Beacon Placement Example

Scenario: Retail store wants to deploy BLE beacons for customer proximity detection. Store is 50 m x 30 m with concrete walls, metal shelving, and merchandise.

Requirements:

Detect customers within 3-5 metre radius of beacon
Coverage for entire store
Minimise beacon count (cost)

Link Budget Analysis:

Input	Value
Beacon transmit power	0 dBm, or 1 mW typical iBeacon power
Beacon antenna	0 dBi chip antenna
Frequency	2.4 GHz
Smartphone sensitivity	-95 dBm typical
Indoor environment	Path-loss exponent n = 3.5, with metal shelving
Required detection distance	5 m

Calculation Step	Result
Free-space path loss at 5 m	54.03 dB
Indoor excess loss	10.5 dB
Total path loss	54.03 + 10.5 = 64.53 dB
Received power	0 - 64.53 = -64.53 dBm
Link margin	-64.53 - (-95) = 30.47 dB, good for a short-range beacon

The 30 dB margin accounts for metal shelving attenuation, customer body blocking, and smartphone orientation variability – all significant in a retail environment.

Beacon Placement Grid:

Figure 45.1: Retail store BLE beacon placement with six 5-metre coverage zones

Beacon Spacing Calculation:

Step	Result
Coverage radius per beacon	5 m, conservative for obstacles
Coverage area per beacon	pi x 5² = 78.5 sq m
Store area	50 x 30 = 1,500 sq m
Minimum beacon count	1,500 / 78.5 = 19.1, rounded to 20
Count with 30% overlap	20 x 1.3 = 26 beacons

Recommended deployment: 24-26 beacons in grid pattern with 8-10 metre spacing.

Try It: BLE Beacon Coverage Estimator

Estimate how many BLE beacons you need for a given store area and detection radius.

Show code

viewof storeLength = Inputs.range([10, 200], {value: 50, step: 5, label: "Store Length (m)"})
viewof storeWidth = Inputs.range([10, 100], {value: 30, step: 5, label: "Store Width (m)"})
viewof beaconRadius = Inputs.range([1, 15], {value: 5, step: 0.5, label: "Coverage Radius (m)"})
viewof overlapPct = Inputs.range([0, 50], {value: 30, step: 5, label: "Overlap Percentage (%)"})

Show code

storeArea = storeLength * storeWidth
beaconCoverageArea = Math.PI * beaconRadius * beaconRadius
minBeacons = Math.ceil(storeArea / beaconCoverageArea)
beaconsWithOverlap = Math.ceil(minBeacons * (1 + overlapPct / 100))

html`<div style="background: #e3f2fd; border-left: 4px solid #3498DB; padding: 12px 16px; border-radius: 4px; margin-top: 8px; font-family: monospace; font-size: 0.95em;">
<strong>Store Area:</strong> ${storeArea.toLocaleString()} sq m<br/>
<strong>Coverage per Beacon:</strong> ${beaconCoverageArea.toFixed(1)} sq m<br/>
<strong>Minimum Beacons:</strong> ${minBeacons}<br/>
<strong>With ${overlapPct}% Overlap:</strong> ${beaconsWithOverlap} beacons<br/>
<strong>Approx. Grid Spacing:</strong> ${(beaconRadius * 2 * 0.85).toFixed(1)} m (centre-to-centre)
</div>`

45.8 LoRa Urban vs Rural Coverage Comparison

45.8.1 Urban Deployment (Dense City, n=4.0)

Urban Link Term	Value
Gateway	Rooftop, 30 m height
Sensor	Street level, 2 m height
Frequency and spreading factor	915 MHz, SF12
TX power and sensitivity	14 dBm TX, -137 dBm RX sensitivity
Path-loss model	Dense urban, n = 4.0 plus 15 dB building penetration
Loss at 2 km	31.7 + 40 log(2000) + 15 = 178.7 dB
Received power	14 - 178.7 = -164.7 dBm
Margin	-164.7 - (-137) = -27.7 dB, so the link fails
Realistic range	About 1-2 km in dense city conditions

45.8.2 Rural Deployment (Open Field, n=2.2)

Rural Link Term	Value
Gateway	10 m mast
Sensor	Ground level
Frequency and spreading factor	915 MHz, SF12
TX power and sensitivity	14 dBm TX, -137 dBm RX sensitivity
Path-loss model	Open field, n = 2.2 plus 5 dB foliage/ground-reflection allowance
Loss at 10 km	31.7 + 22 log(10000) + 5 = 124.7 dB
Received power	14 - 124.7 = -110.7 dBm
Margin	-110.7 - (-137) = +26.3 dB, so the link works
Realistic range	About 10-15 km in open rural conditions

45.8.3 Coverage Comparison Visualization

Comparison diagram showing LoRaWAN coverage in urban versus rural environments, with urban gateway reaching 1-2 km through buildings versus rural gateway achieving 10-15 km over open terrain, illustrating the significant range difference caused by different propagation environments — Figure 45.2: LoRaWAN urban vs rural coverage showing 5-10x range difference

Key Insight: Same hardware, 5-10x range difference based purely on propagation environment!

Alternative View: Link Budget Waterfall

This variant shows the same propagation concepts as a link budget waterfall diagram – how signal strength diminishes step-by-step from transmitter to receiver.

Figure 45.3: Link budget waterfall showing how signal power changes from transmitter through path losses to receiver

Reading the Waterfall: Start at +14 dBm TX power, add antenna gains (green), subtract all losses (orange), and check if received signal exceeds sensitivity. Positive link margin means a reliable link.

45.9 Real-World Case Study: LoRaWAN Gateway Placement for Smart Agriculture

A precision agriculture company needed to cover 2,000 acres (8.1 km²) of mixed terrain – flat cropland, rolling hills, and a tree-lined river corridor – with LoRaWAN soil sensors reporting every 15 minutes.

Initial Design (Desktop Calculation Only)

The engineering team used free-space path loss to estimate that two gateways at 10-metre mast height would cover the entire area (5 km radius each at SF12). They deployed 800 sensors and two gateways.

Result After 3 Months

68% of sensors connected reliably (544 of 800)
22% had intermittent connectivity, losing 30-50% of readings
10% never connected at all (80 sensors in the river corridor)

Root Cause: Terrain and Vegetation Effects Not Modelled

Model	Calculation	Lesson
Desktop free-space estimate	27 dBm TX - 103.7 dB FSPL = -76.7 dBm received, giving 60.3 dB margin	Looks excellent because it ignores terrain and vegetation.
Actual rural vegetation model	Add 28.8 dB path-loss-exponent penalty, 15 dB tree corridor loss, and 8 dB hill diffraction loss	Received power drops to -128.5 dBm.
Final margin	-128.5 - (-137) = 8.5 dB	Marginal, and worst-case summer foliage causes riverside sensors to fail.

Corrected Design (Field-Validated)

The team added three more gateways at strategic locations – one on a grain elevator near the river, one on an existing barn, and one on a hilltop utility pole. They also raised mast heights from 10 m to 15 m.

Metric	Original (2 GW)	Corrected (5 GW)
Sensor connectivity	68%	99.2%
Average link margin	12 dB	22 dB
Message delivery rate	71%	98.5%
Infrastructure cost	$4,000	$10,000
Lost crop data (annual cost)	$45,000	$2,000

Lesson: Never rely solely on free-space path loss. Field surveys with a test transmitter at multiple locations take one day but prevent months of troubleshooting. The additional $6,000 in gateway infrastructure saved $43,000 annually in lost data value. For every $1 spent on proper link budget analysis, this deployment saved $7 in remediation costs.

Common Pitfalls

1. Omitting Cable and Connector Losses From the Link Budget

A 5 m run of LMR-400 coax at 2.4 GHz loses about 1.5 dB. Multiple connectors add another 0.5 dB. Ignoring these losses overestimates received power by 2 dB. Fix: measure or calculate all cable and connector losses and include them explicitly in the link budget.

2. Not Adding a Fade Margin

A link budget that gives exactly 0 dB margin will fail whenever the channel fades slightly. Fix: add 10–20 dB fade margin depending on the link criticality and environment; more for outdoor LOS links in rain-prone areas.

3. Using Antenna Gain Figures From the Wrong Plane

A directional antenna may have 10 dBi in the boresight direction but 0 dBi off-axis. If the antenna is not perfectly aligned, the actual gain could be much lower than the datasheet maximum. Fix: use the antenna’s gain at the expected pointing error angle, not the maximum boresight gain.

Label the Diagram

Code Challenge

45.10 Summary

Link budget calculation accounts for all gains (antennas) and losses (path, cables, obstacles) to predict if a link works
FSPL formula: $L = 20\log_{10}(d_{km}) + 20\log_{10}(f_{MHz}) + 32.45$ – always verify whether distance is in km or metres before applying
Link success criterion: Received power must exceed receiver sensitivity; the difference is your link margin
Urban vs rural coverage differs by 5-10x for the same LoRa hardware due to path loss exponent differences
BLE beacon deployments require 20-30% coverage overlap for reliable handoffs
Always validate with field measurements – desktop calculations can overestimate range by 2-5x if terrain and vegetation are not modelled

45.11 What’s Next

Topic	Chapter	Description
Fresnel Zones	Fresnel Zones and Practical Deployment	Learn why antenna height and line-of-sight clearance matter for reliable outdoor wireless links
Collision Planning	Collision Design Strategies	Apply link-budget thinking alongside channel contention planning for shared wireless networks
Material Attenuation	Material Attenuation and RSSI	Understand how walls, glass, metal, and indoor structure influence real link budget outcomes
LoRaWAN Deployment	LoRaWAN Topology and Components	Apply link budget principles to plan LoRaWAN gateway coverage for agricultural and smart city deployments
LPWAN and Cellular	LPWAN and Cellular Physical Layer	Compare long-range radio options and the trade-offs between range, throughput, power, and network ownership