34  Path Loss and Link Budgets

In 60 Seconds

Path loss is the price a wireless link pays to cross distance, walls, and clutter. In free space, every doubling of distance costs about 6 dB, and higher frequencies pay even more loss at the same range. A link budget turns that physics into a deployment decision: start with transmit power, add antenna gains, subtract path loss and fade margin, and compare the result to receiver sensitivity. If the remaining margin is weak, the design will fail in the field long before it fails in the lab.

34.1 Learning Objectives

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

• Calculate free-space path loss (FSPL) using the Friis transmission equation for different frequencies and distances
• Apply the log-distance path loss model to predict signal attenuation in indoor and outdoor environments
• Construct a complete link budget for an IoT wireless system by summing gains and subtracting losses
• Compare signal strength measurements (dBm, RSSI) across different wireless technologies and interpret their practical meaning
• Evaluate whether a proposed wireless link meets reliability thresholds before deployment
• Predict maximum achievable range for a given set of transmitter, receiver, and environmental parameters

Key Concepts

• Free-space path loss (FSPL) is the baseline attenuation for a clear line-of-sight link; every distance doubling adds about 6 dB.
• Frequency matters twice: higher bands allow more throughput, but they also lose more signal over the same path.
• The path loss exponent n captures the environment: free space behaves near 2, offices and factories push the effective loss much higher.
• A link budget is just gains minus losses compared against receiver sensitivity.
• Fade margin is mandatory, not optional, because real links see interference, orientation changes, weather, and installation error.
• RSSI is not universal across radios; always compare measurements against the sensitivity and thresholds of the specific technology in use.

For Beginners: Path Loss and Link Budgets

Path loss is how much weaker a radio signal gets as it travels through space. Think of it like a flashlight beam - it gets dimmer the farther you shine it. The same happens with wireless signals from your IoT sensors.

Link budget is a simple calculation that predicts whether your wireless system will work before you build it. You start with transmit power, add antenna gains, subtract all the losses (distance, walls, fading), and check if enough signal reaches the receiver. It’s like checking if you have enough fuel before a road trip - but for wireless signals.

This is the single most important calculation to do before deploying any wireless IoT system. It prevents expensive failures in the field.

34.2 Prerequisites

Before diving into this chapter, you should be comfortable with:

• Radio wave basics: Radio Wave Basics for IoT
• Basic algebra and logarithms (dB math): Mathematical Foundations

MVU: IoT Deployment Link Budget

Core Concept: A link budget is a simple equation that predicts whether your wireless IoT system will work: Received Power = Transmit Power + Antenna Gains - Path Loss - Fading Margin. If received power exceeds receiver sensitivity, communication succeeds.

Why It Matters: Link budgets prevent expensive field failures. Industry data shows that 40% of IoT pilot failures are due to connectivity issues that could have been predicted with a 5-minute link budget calculation. The FCC and ETSI define regulatory transmit power limits (14 dBm EU, 30 dBm US for ISM bands), so you cannot simply “turn up the power” when deployments fail.

Key Takeaway: Always include a 20 dB fading margin for outdoor deployments and 15 dB for indoor. The difference between a “working” lab demo and a reliable production system is margin. Sub-GHz frequencies (LoRa at 868/915 MHz) provide approximately 9 dB better path loss than 2.4 GHz at the same distance - equivalent to 3x the range with identical hardware.

---

34.3 Path Loss: Signal Attenuation Over Distance

Minimum Viable Understanding: Path Loss Fundamentals

Core Concept: Path loss is the reduction in radio signal strength as it travels through space, following the inverse-square law where signal power decreases proportionally to the square of the distance - doubling distance reduces power by 6 dB (a factor of 4).

Why It Matters: Path loss determines whether your IoT devices can communicate at all. Every wireless link budget calculation starts with path loss, and underestimating it is the most common cause of IoT deployment failures. A sensor that works perfectly at 100m in the lab may fail completely at 200m in the field because path loss increased by 6 dB - and that is free-space loss only, before accounting for walls, terrain, or interference.

Key Takeaway: Use the “6-20 rule” for quick mental calculations: every doubling of distance adds 6 dB loss, and every doubling of frequency adds another 6 dB. For real-world deployments, multiply free-space loss by the path loss exponent (n=2 for free space, n=3-4 for indoor, n=4-5 for obstructed urban). Always add 15-25 dB fading margin to your calculations - if your link budget is exactly zero, your system will fail half the time.

34.3.1 Free Space Path Loss (FSPL)

In perfect conditions (no obstacles, no reflections), signal strength decreases with distance following the inverse square law. This means doubling the distance quadruples the path loss (adds 6 dB).

The formula:

\[FSPL_{dB} = 20\log_{10}(d) + 20\log_{10}(f) + 20\log_{10}\left(\frac{4\pi}{c}\right)\]

Simplified for practical use (distance in km, frequency in MHz):

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

What this means: Path loss increases with both distance and frequency. For the same distance, higher frequencies suffer more loss.

Quick reference:

• 868 MHz (LoRa): about 31 dB at 1 m, 51 dB at 10 m, 71 dB at 100 m, 91 dB at 1 km, and 111 dB at 10 km.
• 2.4 GHz (Wi-Fi/BLE/Zigbee): about 40 dB at 1 m, 60 dB at 10 m, 80 dB at 100 m, 100 dB at 1 km, and 120 dB at 10 km.
• 5 GHz (Wi-Fi): about 47 dB at 1 m, 67 dB at 10 m, 87 dB at 100 m, 107 dB at 1 km, and 127 dB at 10 km.

Putting Numbers to It

Let’s verify the 9 dB advantage of sub-GHz versus 2.4 GHz at the same distance.

Calculate path loss for both frequencies at 1 km:

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

For 868 MHz (LoRa): \[FSPL = 20\log_{10}(1) + 20\log_{10}(868) + 32.45\] \[= 0 + 58.77 + 32.45 = 91.2 \text{ dB}\]

For 2.4 GHz (Wi-Fi): \[FSPL = 20\log_{10}(1) + 20\log_{10}(2400) + 32.45\] \[= 0 + 67.6 + 32.45 = 100.05 \text{ dB}\]

Difference: \(100.05 - 91.2 = 8.85 \approx 9\) dB advantage for 868 MHz!

What does this mean? With identical TX power and antennas, the 868 MHz link has 9 dB more link margin. Using the 6 dB rule, 9 dB ≈ \(10^{9/20} = 2.8\times\) longer range. This is why LoRa reaches 10-15 km while Wi-Fi reaches only 50-200m outdoors.

Key Insight

At 2.4 GHz, you lose an additional 9 dB compared to 868 MHz at the same distance. That’s why LoRa and Sigfox (sub-GHz) achieve much longer ranges than Wi-Fi and Bluetooth.

34.3.2 Real-World Path Loss Models

Free space is ideal; real environments add extra loss. The log-distance path loss model accounts for this:

\[PL(d) = PL(d_0) + 10n\log_{10}\left(\frac{d}{d_0}\right) + X_\sigma\]

Where: - \(PL(d_0)\) = path loss at reference distance (usually 1m) - \(n\) = path loss exponent (environment-dependent) - \(X_\sigma\) = random variable for shadowing (obstacles)

Typical path loss exponents:

• Free space (n = 2.0): ideal line-of-sight with essentially no obstacles.
• Urban cellular (n = 2.7-3.5): reflections and partial blockage from buildings raise loss above free-space behavior.
• Urban obstructed (n = 4-5): non-line-of-sight paths are heavily penalized.
• Indoor open office (n = 2.5-3.0): furniture and light partitions add moderate loss.
• Indoor partitioned (n = 3.5-4.5): cubicles, walls, and clutter degrade coverage rapidly.
• Indoor through walls (n = 4-6): each extra wall can burn a large chunk of the budget.
• Factory or industrial (n = 3.0-4.0): metal surfaces and machinery drive reflection, shadowing, and blockage.

Figure 34.1: Overview comparing the two 6 dB rules, baseline FSPL at 1 km for 868 MHz, 2.4 GHz, and 5 GHz, and how harsher environments push the path loss exponent above the free-space case.

---

34.4 Link Budget: Will Your System Work?

A link budget calculates whether a wireless link will function by comparing transmitted power to receiver sensitivity.

34.4.1 The Link Budget Equation

\[P_{rx} = P_{tx} + G_{tx} - L_{cable,tx} - L_{path} - L_{other} + G_{rx} - L_{cable,rx}\]

Where: - \(P_{tx}\) = Transmitter output power (dBm) - \(G_{tx}\), \(G_{rx}\) = Antenna gains (dBi) - \(L_{path}\) = Path loss (dB) - \(L_{other}\) = Other losses (fading margin, body loss, etc.) - \(P_{rx}\) = Received power (dBm)

Figure 34.2: Link budget flow showing transmit power and antenna gains on the input side, path loss and fade margin as the major deductions, and the final received power compared against receiver sensitivity to determine the final margin.

Alternative view: Link Budget as Waterfall Calculation - This diagram shows the link budget as a step-by-step waterfall calculation. Start with transmit power (+14 dBm), add antenna gains (teal, positive contributions), then subtract losses (orange, negative contributions) including path loss, fading margin, and cable losses. The final received power (-94 dBm) is compared against receiver sensitivity (-137 dBm) to determine link margin (+43 dB). A positive link margin means the link will work; larger margins mean more reliable connections.

Figure 34.3

34.4.2 Link Budget Example: LoRaWAN Sensor

34.4.2.1 Hardware Assumptions

• Transmit power: +14 dBm, matching the EU LoRaWAN limit.
• Transmit antenna gain: +2 dBi for a simple dipole.
• Transmit cable loss: -1 dB for a short run.
• Receive antenna gain: +3 dBi at the gateway.
• Receive cable loss: -2 dB for the longer gateway cable.
• Receiver sensitivity: -137 dBm at SF12 / 125 kHz.

34.4.2.2 Budget Snapshot

• Available EIRP: +15 dBm after including transmitter antenna gain and cable loss.
• Required receive power: about -138 dBm after accounting for receiver-side gain and cable loss.
• Resulting link budget: about 153 dB, before fade margin and environment-specific penalties.

Maximum range calculation:

Using log-distance path loss model for urban environment (n=3.5, reference at 1 km): \[153 = 91.2 + 35\log_{10}(d_{km})\] \[d_{km} = 10^{(153-91.2)/35} \approx 59 \text{ km (theoretical)}\]

With 20 dB fading margin (allowable path loss = 133 dB): \[d_{km} = 10^{(133-91.2)/35} \approx 16 \text{ km}\]

Practical urban range: 2-5 km (accounting for buildings, interference, and real-world conditions beyond the model)

34.4.3 Link Margin

Link margin is the difference between received power and receiver sensitivity: \[\text{Link Margin} = P_{rx} - P_{sensitivity}\]

• < 0 dB: Link will not work
• 0-10 dB: Unreliable, occasional dropouts
• 10-20 dB: Acceptable for most applications
• > 20 dB: Very reliable, robust link

Worked Example: Outdoor Sensor Link Budget Calculation

Scenario: You are deploying a LoRa sensor on a farm to monitor soil moisture. The sensor is 3 km from the gateway, with a clear line of sight across open fields.

Given:

• Frequency: 915 MHz (US ISM band)
• Sensor transmit power: +20 dBm
• Sensor antenna gain: +2 dBi (simple dipole)
• Gateway antenna gain: +6 dBi (fiberglass omnidirectional)
• Gateway receiver sensitivity: -137 dBm (SF12, 125 kHz bandwidth)
• Environment: Rural open field (path loss exponent n = 2.2)
• Required fading margin: 15 dB (outdoor, rural)

Solution:

Step 1: Calculate Free Space Path Loss (FSPL)

Using the simplified formula for FSPL: \[FSPL_{dB} = 20\log_{10}(d_{km}) + 20\log_{10}(f_{MHz}) + 32.45\]

\[FSPL = 20\log_{10}(3) + 20\log_{10}(915) + 32.45\] \[FSPL = 9.54 + 59.23 + 32.45 = 101.22 \text{ dB}\]

Step 2: Adjust for Real Environment

For rural open field with n = 2.2 (slightly worse than free space n = 2.0): \[PL_{real} = FSPL \times \frac{n}{2.0} = 101.22 \times \frac{2.2}{2.0} = 111.34 \text{ dB}\]

Step 3: Calculate Received Power

\[P_{rx} = P_{tx} + G_{tx} + G_{rx} - PL_{real}\] \[P_{rx} = 20 + 2 + 6 - 111.34 = -83.34 \text{ dBm}\]

Step 4: Calculate Link Margin

\[\text{Link Margin} = P_{rx} - P_{sensitivity}\] \[\text{Link Margin} = -83.34 - (-137) = 53.66 \text{ dB}\]

Step 5: Apply Fading Margin

\[\text{Available Margin} = \text{Link Margin} - \text{Fading Margin}\] \[\text{Available Margin} = 53.66 - 15 = 38.66 \text{ dB}\]

Result: The link has 38.66 dB of margin after accounting for fading. This is excellent - the system will work reliably even in adverse conditions.

Maximum Range Estimate: With 38.66 dB of available margin remaining, the link can tolerate substantially more path loss. In practice, LoRaWAN deployments in rural line-of-sight conditions routinely achieve 10-15 km, and the 53.66 dB raw link margin at 3 km confirms this sensor has ample headroom for much greater distances.

Key Insight: LoRa’s exceptional receiver sensitivity (-137 dBm) combined with sub-GHz frequencies creates massive link budgets. This is why LoRaWAN achieves 10-15 km ranges in rural areas. However, always design for 15-25 dB fading margin to handle weather variations, vegetation growth, and seasonal changes.

---

34.5 Understanding Signal Strength Measurements

34.5.1 dBm: Absolute Power

dBm measures absolute power in milliwatts on a logarithmic scale: \[P_{dBm} = 10\log_{10}(P_{mW})\]

Useful dBm anchors:

• +30 dBm = 1000 mW: upper-end Wi-Fi EIRP in permissive regulatory scenarios.
• +20 dBm = 100 mW: common high-power Wi-Fi transmit level.
• +14 dBm = 25 mW: familiar LoRaWAN EU transmit ceiling.
• +4 dBm = 2.5 mW: common Bluetooth Class 2 scale.
• 0 dBm = 1 mW: the absolute reference point.
• -70 dBm: often a comfortable Wi-Fi signal.
• -90 dBm: weak but sometimes usable Wi-Fi territory.
• -120 dBm: near the noise floor for many systems.
• -137 dBm: LoRa SF12 sensitivity region.

34.5.2 RSSI: Received Signal Strength Indicator

RSSI is a vendor-specific measurement of signal strength. It’s often (but not always) related to dBm:

Figure 34.4: Comparison showing that RSSI must be interpreted against technology-specific sensitivity: Wi-Fi needs much stronger absolute power than LoRa, even when the same dBm number is shown on screen.

Alternative view: RSSI Levels with Application Requirements - Instead of abstract quality labels, this diagram shows what applications work at each signal strength level. Excellent signal (-40 to -50 dBm) supports demanding apps like video streaming and VoIP. Good signal (-50 to -67 dBm) handles normal browsing and most IoT sensors. Fair signal (-67 to -80 dBm) still works for basic web and sensor data. Even poor signal (-80 to -90 dBm) works for LoRa, which is designed for weak signals. Key insight: IoT protocols like LoRa work at signal levels where Wi-Fi fails.

Figure 34.5

RSSI vs SNR

RSSI only tells you signal strength, not quality. A strong signal can still be useless if there’s strong interference.

SNR (Signal-to-Noise Ratio) tells you how much your signal stands out from the noise: \[SNR_{dB} = P_{signal,dBm} - P_{noise,dBm}\]

For reliable communication, you typically need SNR > 10-20 dB, depending on the modulation scheme.

Quick Check: Link Budget Fundamentals

---

34.6 Understanding Check

Test Your Understanding

Scenario: You’re designing a smart agriculture system. Soil moisture sensors are deployed across a 500-acre (2 km squared) field. A gateway is placed at the farm building in the center.

Given:

• Sensors transmit at +14 dBm with 2 dBi antenna
• Gateway has sensitivity of -137 dBm with 6 dBi antenna
• Environment is rural/open (path loss exponent n approximately 2.5)
• Frequency: 915 MHz

Questions:

1. What is the maximum theoretical range in free space?
2. What is the practical range with the real environment?
3. Will sensors at the field edges (1 km away) work reliably?
4. What fading margin would you recommend?

Solution

1. Maximum theoretical range (free space):

Link budget: +14 + 2 - 1 (cable) + 6 - 1 (cable) - (-137) = 157 dB

Free space path loss: 157 = 32.45 + 20log(915) + 20log(d_km) 157 = 32.45 + 59.2 + 20log(d) 65.35 = 20log(d) d = 10^(65.35/20) = 1850 km (theoretical!)

Note: This is a mathematical upper bound in an idealized free-space model. In practice, line-of-sight/horizon limits, Fresnel clearance, interference, and regulations dominate long before this distance.

2. Practical range (n=2.5):

Using log-distance model with n=2.5: 157 = 91.65 + 25log(d_km) 65.35 = 25log(d) d = 10^(65.35/25) = 10^{2.61} = 411 km (theoretical, without fading margin)

Note: Like the free-space result, this far exceeds practical limits imposed by the radio horizon (~50 km for ground-level antennas), terrain, and interference.

3. Sensors at 1 km:

Path loss at 1 km: 91.65 + 25log(1) = 91.65 dB Received power: +14 + 2 + 6 - 91.65 = -69.65 dBm Link margin: -69.65 - (-137) = 67.35 dB

Yes! Sensors at 1 km will work very reliably.

4. Recommended fading margin:

For outdoor agriculture: 15 dB is typically sufficient With 67 dB margin, you have excellent reliability even in adverse conditions.

---

Common Mistake: Confusing RSSI Values Across Different Radio Technologies

The Mistake: Assuming an RSSI of -70 dBm means the same thing for all wireless technologies, leading to incorrect threshold settings and link quality misinterpretation.

Why This Happens: RSSI (Received Signal Strength Indicator) is often displayed as a single dBm number, making it seem like a universal measurement. However, different technologies use different modulation schemes, coding rates, and noise floors, so the same RSSI value results in vastly different link quality.

Real-World Examples:

Technology-specific examples:

• LoRa SF12 at -130 dBm: often still excellent because the modulation and coding are designed for extremely weak signals.
• Wi-Fi 802.11n at -130 dBm: completely unusable; the signal is far below normal receive thresholds.
• Bluetooth 5.0 at -70 dBm: generally a healthy short-range link.
• Zigbee at -70 dBm: typically excellent because the protocol tolerates weaker absolute signal levels than Wi-Fi.

Common Failure Mode: An engineer sets LoRa gateway alerts to trigger at RSSI < -70 dBm (copying Wi-Fi thresholds), resulting in thousands of false “weak signal” warnings when sensors at -90 to -110 dBm are actually performing perfectly.

The Fix:

LoRa/LoRaWAN Thresholds:

• Excellent: > -100 dBm
• Good: -100 to -115 dBm
• Acceptable: -115 to -125 dBm
• Poor: -125 to -137 dBm (still works with SF12)

Wi-Fi Thresholds:

• Excellent: > -50 dBm
• Good: -50 to -67 dBm
• Fair: -67 to -80 dBm
• Poor: -80 to -90 dBm
• Unusable: < -90 dBm

Zigbee/BLE Thresholds:

• Excellent: > -60 dBm
• Good: -60 to -75 dBm
• Fair: -75 to -85 dBm
• Poor: < -85 dBm

Key Principle: Always check receiver sensitivity specifications for your specific radio module and modulation settings. LoRa at SF12 can decode signals at -137 dBm (near the noise floor), while Wi-Fi requires signals 40-50 dB stronger for basic connectivity.

Prevention: Document technology-specific RSSI thresholds in your system design. Use link quality metrics (LQI, SNR) in addition to raw RSSI values for more accurate assessment.

34.7 Concept Relationships

This chapter connects to other IoT topics:

• Fading Margin -> Fading and Interference: path loss alone is never the whole story; the fade reserve is what keeps the link stable when the channel moves.
• LoRa Range -> LoRaWAN Overview: very low receiver sensitivity is the main reason LPWAN links close over kilometer-scale paths.
• Antenna Gain -> Antenna Fundamentals: a few dB of antenna gain can materially change the range budget.
• Wireless Design -> RF Design Fundamentals: the link budget is the first serious filter for any candidate architecture.

34.8 Try It Yourself

Interactive Link Budget Calculator

Experiment with different wireless link parameters to see how they affect link margin. Try adjusting transmit power, antenna gains, distance, and environment to understand what it takes to create a reliable IoT wireless link.

colors = ({
  navy: "#2C3E50",
  teal: "#16A085",
  orange: "#E67E22",
  blue: "#3498DB",
  gray: "#7F8C8D",
  purple: "#9B59B6",
  red: "#E74C3C",
  green: "#27AE60"
})

// Input controls
viewof txPower = Inputs.range([0, 30], {
  value: 14,
  step: 1,
  label: "TX Power (dBm):"
})

viewof txGain = Inputs.range([0, 10], {
  value: 2,
  step: 1,
  label: "TX Antenna Gain (dBi):"
})

viewof rxGain = Inputs.range([0, 10], {
  value: 3,
  step: 1,
  label: "RX Antenna Gain (dBi):"
})

viewof distance = Inputs.range([0.01, 100], {
  value: 1,
  step: 0.1,
  label: "Distance (km):"
})

viewof frequency = Inputs.select(
  [[868, "868 MHz (LoRa EU)"], [915, "915 MHz (LoRa US)"], [2400, "2.4 GHz (Wi-Fi/BLE)"], [5000, "5 GHz (Wi-Fi)"]],
  {
    value: 868,
    label: "Frequency:",
    format: ([freq, name]) => name
  }
)

viewof pathLossExp = Inputs.range([2.0, 5.0], {
  value: 2.0,
  step: 0.1,
  label: "Path Loss Exponent (n):"
})

viewof rxSensitivity = Inputs.range([-140, -60], {
  value: -137,
  step: 1,
  label: "RX Sensitivity (dBm):"
})

viewof fadingMargin = Inputs.range([0, 30], {
  value: 15,
  step: 1,
  label: "Fading Margin (dB):"
})

// Calculations
fspl = 20 * Math.log10(distance) + 20 * Math.log10(frequency) + 32.45

realPathLoss = fspl * (pathLossExp / 2.0)

rxPower = txPower + txGain + rxGain - realPathLoss

linkMargin = rxPower - rxSensitivity

availableMargin = linkMargin - fadingMargin

// Link status
linkStatus = availableMargin > 20 ? {text: "Excellent", color: colors.green} :
             availableMargin > 10 ? {text: "Good", color: colors.teal} :
             availableMargin > 0 ? {text: "Marginal", color: colors.orange} :
             {text: "FAIL", color: colors.red}

// Environment description
envDescription = pathLossExp === 2.0 ? "Free space" :
                pathLossExp < 2.5 ? "Rural open" :
                pathLossExp < 3.0 ? "Suburban" :
                pathLossExp < 3.5 ? "Indoor (open)" :
                pathLossExp < 4.5 ? "Indoor (partitioned)" :
                "Indoor (heavy obstruction)"

// Display results
html`
<div style="font-family: Arial, sans-serif; padding: 20px; background: linear-gradient(135deg, ${colors.navy}15, ${colors.teal}15); border-radius: 8px; margin-top: 20px;">

  <h3 style="color: ${colors.navy}; margin-top: 0;">Link Budget Results</h3>

  <div style="display: grid; grid-template-columns: 1fr 1fr; gap: 15px; margin-bottom: 20px;">

    <div style="background: white; padding: 15px; border-radius: 6px; border-left: 4px solid ${colors.teal};">
      <div style="font-size: 12px; color: ${colors.gray}; text-transform: uppercase; margin-bottom: 5px;">Environment</div>
      <div style="font-size: 18px; font-weight: bold; color: ${colors.navy};">${envDescription}</div>
      <div style="font-size: 12px; color: ${colors.gray}; margin-top: 5px;">Path Loss Exponent: ${pathLossExp.toFixed(1)}</div>
    </div>

    <div style="background: white; padding: 15px; border-radius: 6px; border-left: 4px solid ${colors.orange};">
      <div style="font-size: 12px; color: ${colors.gray}; text-transform: uppercase; margin-bottom: 5px;">Path Loss</div>
      <div style="font-size: 18px; font-weight: bold; color: ${colors.navy};">${realPathLoss.toFixed(1)} dB</div>
      <div style="font-size: 12px; color: ${colors.gray}; margin-top: 5px;">Free space: ${fspl.toFixed(1)} dB</div>
    </div>

    <div style="background: white; padding: 15px; border-radius: 6px; border-left: 4px solid ${colors.blue};">
      <div style="font-size: 12px; color: ${colors.gray}; text-transform: uppercase; margin-bottom: 5px;">Received Power</div>
      <div style="font-size: 18px; font-weight: bold; color: ${colors.navy};">${rxPower.toFixed(1)} dBm</div>
      <div style="font-size: 12px; color: ${colors.gray}; margin-top: 5px;">Raw link margin: ${linkMargin.toFixed(1)} dB</div>
    </div>

    <div style="background: white; padding: 15px; border-radius: 6px; border-left: 4px solid ${linkStatus.color};">
      <div style="font-size: 12px; color: ${colors.gray}; text-transform: uppercase; margin-bottom: 5px;">Link Status</div>
      <div style="font-size: 24px; font-weight: bold; color: ${linkStatus.color};">${linkStatus.text}</div>
      <div style="font-size: 12px; color: ${colors.gray}; margin-top: 5px;">Available margin: ${availableMargin.toFixed(1)} dB</div>
    </div>

  </div>

  <div style="background: white; padding: 15px; border-radius: 6px; border: 2px solid ${colors.navy};">
    <h4 style="margin-top: 0; color: ${colors.navy};">Calculation Breakdown</h4>
    <table style="width: 100%; font-size: 14px;">
      <tr style="border-bottom: 1px solid #eee;">
        <td style="padding: 8px; color: ${colors.gray};">TX Power + TX Gain + RX Gain</td>
        <td style="padding: 8px; text-align: right; font-weight: bold; color: ${colors.teal};">
          ${txPower} + ${txGain} + ${rxGain} = +${(txPower + txGain + rxGain).toFixed(1)} dBm
        </td>
      </tr>
      <tr style="border-bottom: 1px solid #eee;">
        <td style="padding: 8px; color: ${colors.gray};">Path Loss</td>
        <td style="padding: 8px; text-align: right; font-weight: bold; color: ${colors.orange};">
          -${realPathLoss.toFixed(1)} dB
        </td>
      </tr>
      <tr style="border-bottom: 1px solid #eee;">
        <td style="padding: 8px; color: ${colors.gray};">Received Power</td>
        <td style="padding: 8px; text-align: right; font-weight: bold; color: ${colors.navy};">
          ${rxPower.toFixed(1)} dBm
        </td>
      </tr>
      <tr style="border-bottom: 1px solid #eee;">
        <td style="padding: 8px; color: ${colors.gray};">RX Sensitivity</td>
        <td style="padding: 8px; text-align: right; font-weight: bold;">
          ${rxSensitivity} dBm
        </td>
      </tr>
      <tr style="border-bottom: 1px solid #eee;">
        <td style="padding: 8px; color: ${colors.gray};">Link Margin (before fading)</td>
        <td style="padding: 8px; text-align: right; font-weight: bold; color: ${colors.teal};">
          ${linkMargin.toFixed(1)} dB
        </td>
      </tr>
      <tr style="border-bottom: 1px solid #eee;">
        <td style="padding: 8px; color: ${colors.gray};">Fading Margin</td>
        <td style="padding: 8px; text-align: right; font-weight: bold; color: ${colors.orange};">
          -${fadingMargin} dB
        </td>
      </tr>
      <tr>
        <td style="padding: 8px; color: ${colors.gray}; font-weight: bold;">Available Margin</td>
        <td style="padding: 8px; text-align: right; font-weight: bold; font-size: 16px; color: ${linkStatus.color};">
          ${availableMargin.toFixed(1)} dB
        </td>
      </tr>
    </table>
  </div>

  <div style="margin-top: 15px; padding: 12px; background: ${colors.blue}15; border-radius: 6px; border-left: 4px solid ${colors.blue};">
    <strong style="color: ${colors.navy};">Design Guidelines:</strong>
    <ul style="margin: 10px 0 0 0; padding-left: 20px; color: ${colors.gray};">
      <li>Target > 20 dB available margin for reliable links</li>
      <li>10-20 dB is acceptable for most applications</li>
      <li>0-10 dB means unreliable, occasional dropouts</li>
      <li>< 0 dB means the link will fail</li>
    </ul>
  </div>

</div>
`

Experiments to Try:

1. Frequency comparison: Switch between 868 MHz and 2.4 GHz at 1 km distance. Notice the ~9 dB difference in path loss.

2. Indoor vs outdoor: Start with n=2.0 (free space) at 1 km, then increase to n=4.0 (indoor). See how path loss more than doubles.

3. Margin importance: Set distance to achieve exactly 0 dB available margin. Then increase distance by just 10% - the link fails. This shows why you need safety margin.

4. Antenna gains: Start with 0 dBi antennas for both TX and RX. Add 3 dB to each. Notice how 6 dB total gain approximately doubles your achievable range.

Challenge: Calculate Link Budget for Your IoT Deployment

Objective: Design a reliable wireless link using real component specifications and environment parameters.

Scenario: ESP32 sensor node transmitting to gateway in office building: - ESP32 TX power: +20 dBm - ESP32 antenna gain: +2 dBi (chip antenna) - Gateway antenna gain: +5 dBi (external dipole) - Distance: 30 meters - Environment: Indoor office (n=3.5) - Frequency: 2.4 GHz - Gateway sensitivity: -95 dBm

Steps:

1. Calculate free-space path loss at 30m, 2.4 GHz
2. Adjust for indoor environment (multiply by n/2.0)
3. Calculate received power: TX power + antenna gains - path loss
4. Determine link margin: received power - sensitivity
5. Compare to 20 dB reliability threshold

Solution:

1. FSPL = 20log(0.03) + 20log(2400) + 32.45 = -30.5 + 67.6 + 32.45 = 69.55 dB
2. Indoor adjustment: 69.55 × (3.5/2.0) = 121.7 dB actual path loss
3. RX power = 20 + 2 + 5 - 121.7 = -94.7 dBm
4. Link margin = -94.7 - (-95) = 0.3 dB
5. Result: FAIL - Only 0.3 dB margin, need 20 dB minimum!

Fix: Add 6 dBi gateway antenna (9 dB total gain) → Link margin = 6.3 dB. Still marginal! Reduce distance to 20m OR use sub-GHz frequency.

Expected Observation: Indoor deployments require much higher link budgets than outdoor due to higher path loss exponent. Always test at maximum expected distance.

Common Pitfalls

1. Treating Free-Space Numbers as Real Deployment Numbers

FSPL is only the starting point. Walls, people, metal shelving, humidity, and installation mistakes all burn margin beyond the ideal equation. If you deploy to the free-space budget, you are deploying to fail.

2. Spending the Entire Budget on Distance

A link that closes with 0 dB spare margin is not a robust link. You still need reserve for fading, antenna detuning, seasonal vegetation, battery sag, and interference from neighboring systems.

3. Reusing Wi-Fi RSSI Thresholds for Every Radio

An RSSI alarm that makes sense for Wi-Fi can be meaningless for LoRa, Zigbee, or BLE. Always anchor your thresholds to the receiver sensitivity and modulation of the actual radio in the design.

🏷️ Label the Diagram

Code Challenge

34.9 Summary

• Path loss grows with distance and frequency: farther links and higher bands both consume more of the budget.
• FSPL gives the clean-air baseline: \(FSPL = 20\log(d) + 20\log(f) + 32.45\).
• The path loss exponent tells you how hostile the environment is: near 2 in free space, often 3-4 indoors, and higher in heavy obstruction.
• The link budget is a gain-loss ledger that must still beat receiver sensitivity after reserving margin.
• dBm is absolute power, while RSSI is only meaningful in the context of a specific radio.
• A good design keeps 10-20+ dB of real margin, not merely a mathematically positive answer.

34.10 See Also

Related Wireless Topics:

• Radio Wave Basics - Electromagnetic spectrum fundamentals
• Fading and Interference - Real-world signal variations
• Practical Wireless Lab - Hands-on RSSI experiments

Advanced Link Analysis:

• Antenna Theory - Gain, directivity, polarization
• RF Link Planning - Fresnel zones, line-of-sight
• LoRaWAN Range - Long-range link budget examples

Key Takeaway

A link budget is the “financial statement” of a wireless system: transmit power + antenna gains - path loss - fading margin must exceed receiver sensitivity. The free-space path loss formula (FSPL = 20log(d) + 20log(f) + 32.45) shows that doubling distance costs 6 dB and doubling frequency costs 6 dB. For reliable IoT links, maintain at least 20 dB link margin after accounting for all losses and fading. Always calculate your link budget BEFORE deployment – it predicts whether your system will work without installing a single device.

For Kids: Meet the Sensor Squad!

Sammy the Sensor needed to shout a message to a gateway far away, and Max the Microcontroller was helping with the math!

“Let’s do a link budget – it’s like counting your money before going shopping!” Max explained.

“You START with your voice power: +14 dBm (that’s how loud Sammy can shout).” “ADD the antenna gain: +3 dBi (that’s like using a megaphone – it focuses your voice).” “SUBTRACT path loss: -100 dB (that’s how much the signal weakens traveling 1 kilometer at 868 MHz).” “SUBTRACT fading margin: -15 dB (extra buffer for bad weather and obstacles).”

Lila the LED did the math: “14 + 3 - 100 - 15 = -98 dBm at the receiver!”

“And the gateway can hear signals down to -137 dBm,” said Bella the Battery. “So we have 39 dB of link margin – plenty of room!”

“But if I move to 10 kilometers away,” Sammy worried, “path loss jumps by 20 dB to 120 dB total. Then we’d have only 19 dB margin. Still workable, but tighter!”

The lesson: Link budgets predict whether your wireless signal will reach its destination BEFORE you install anything. It’s like checking if you have enough fuel before a road trip!

---

34.11 Knowledge Check

Quiz: Path Loss and Link Budgets

Interactive: Wireless Range Calculator

34.12 What’s Next

With path loss and link budget fundamentals in hand, explore these related topics to deepen your wireless design skills:

• Fading, Multipath, and Interference: see why fade margin is not optional once the channel becomes real.
• Practical Wireless Lab: validate link-budget predictions with measured RSSI, packet loss, and placement changes.
• Radio Wave Basics for IoT: revisit why wavelength and frequency start the entire budget conversation.
• LPWAN Introduction: apply the budget logic to LoRa, Sigfox, and NB-IoT choices.
• LoRaWAN Overview: connect large LPWAN link budgets to real network architecture.
• Antenna Fundamentals: extend the model with gain, antenna placement, and Fresnel clearance.