Chapters

31 Path Loss and Link Budgets

fundamentals
wireless
prop
path

31.1 In 60 Seconds

This section: In 60 Seconds — Picture a loading-bay sensor that works with the door open but loses reports when a truck parks nearby.

Prove One Installed Radio Link

Picture a loading-bay sensor that works with the door open but loses reports when a truck parks nearby. A range claim alone cannot tell the operator whether the installed path is safe to use.

A gateway means the boundary system that joins local devices to another network or service. Received signal strength means the radio power that arrives at a receiver. RSSI means received signal strength indicator, the radio’s reported estimate of that power.

Send marked packets over the real route, then change the door, vehicle position, channel, and antenna angle. Keep place, time, radio settings, RSSI, retries, delivery, and remaining margin so another person can repeat the test.

This check covers one route and set of conditions, not every season or obstruction. The deeper sections build the loss model, link-budget ledger, fade margin, and field validation plan.

A wireless range claim is only useful when the budget behind it can be inspected. Path-loss and link-budget work turns radio terms into an auditable decision: what the link must achieve, what each gain or loss contributes, how much margin remains, and what site evidence proves it.

31.2 Start With the Story

This section: Start With the Story — You will estimate received power and margin, then compare the calculation with delivery evidence from the site.

You will estimate received power and margin, then compare the calculation with delivery evidence from the site. Start by recording the radio terms, path assumptions, and reliability requirement.

Follow one link-budget promise across four beats to see how every gain, loss, and reserve must survive field measurement.

  1. Remi and Test Tessa measure a strong close-range baseline between a wireless sensor and gateway.

    Remi: “The baseline shows what the link can deliver before the path spends its margin.”

  2. Remi and Test Tessa see distance and a concrete wall weaken the radio signal and trigger packet retries.

    Test Tessa: “Distance and obstruction have consumed the margin the bench concealed.”

  3. Remi and Test Tessa balance transmitter and antenna gains against distance, wall, and fade losses in a complete ledger.

    The team: “Count every gain and loss, then keep a reserve for fading.”

  4. Remi and Test Tessa field-check the predicted link margin and packet delivery at the real obstructed location.

    Test Tessa: “The field result now supports the ledger and its retained reserve.”

A link budget is a testable promise whose predicted margin must agree with measured delivery at the real site.

Read the story panels from the close-range baseline to the obstructed field check. Distance and concrete consume margin that the bench result could not expose, producing retries before the budget is complete. The ledger then balances transmitter and antenna gains against path, wall, and fade losses while retaining a reserve. Measured delivery at the real location tests both the prediction and that reserve, making the budget an auditable promise.

31.5 Under the Hood: Path-Loss Math and Failure Modes

This section: Under the Hood: Path-Loss Math and Failure Modes — The deeper layer explains where the ledger numbers come from and how each one fails.

The deeper layer explains where the ledger numbers come from and how each one fails. Path loss is the row most often estimated wrongly, so it gets the most attention here.

The formulas are useful only when the assumptions are visible. Record the units, reference distance, receiver mode, antenna context, and environment class beside the number, because those choices decide whether another engineer can reproduce the estimate or find the mistake.

Free-Space Path Loss

Free-space path loss (FSPL) is the clean-air baseline: a clear line of sight, no walls, no reflectors, no people, and no detuning. For distance in kilometers and frequency in megahertz:

FSPL_dB = 20 log10(d_km) + 20 log10(f_MHz) + 32.45

Useful reference points at 1 km:

  • A 900 MHz-class signal: about 91.5 dB.
  • A 2.4 GHz signal: about 100 dB.
  • A 5 GHz signal: about 107 dB.

These are not range promises. They are clean-air reference points used before adding environment, antenna, installation, and reliability terms. The 20 log10 terms are exactly why doubling either distance or frequency adds about 6 dB.

Unit check. The constant 32.45 assumes kilometers and megahertz. If distance is in meters, convert first (30 m = 0.03 km). A correct equation with inconsistent units produces a wrong budget that still looks reasonable.

The Log-Distance Model (and the n/2 Trap)

Real environments grow loss faster than free space. The path-loss exponent n describes how quickly loss grows after a reference point. It does not mean "multiply the whole free-space loss by n / 2." The safe review model is:

PL(d) = PL(d0) + 10 n log10(d / d0) + X_sigma
  • PL(d0) is measured or calculated loss at a reference distance such as 1 m.
  • n is the environment's path-loss exponent.
  • X_sigma is shadowing variation from walls, people, vehicles, shelves, terrain, and layout changes.

Clear or Outdoor LOS

Use n near 2 only with a credible line-of-sight path and a mostly clear Fresnel region.

Office or Light Indoor

Use a larger exponent when furniture, partitions, people, and reflections make the path worse than clean air.

Obstructed or Industrial

Metal, dense walls, equipment, vehicles, and non-line-of-sight routes consume margin quickly and must be measured.

Example at 2.4 GHz, where free-space loss at 1 m is about 40 dB, evaluated at 30 m:

PL_free = 40 + 10(2.0) log10(30) = 69.5 dB PL_indoor = 40 + 10(3.2) log10(30) = 87.3 dB

The environment changes the distance-growth term. It does not turn 69.5 dB into 111 dB by multiplying the whole free-space result by 3.2 / 2.

Inspect Figure 31.3 and ask why a positive raw link margin is insufficient for deployment approval.

Read Figure 31.3 from predicted receive power to receiver need. Their gap, Prx−PsensitivityP_{rx}-P_{sensitivity}, is raw margin in decibels. It is the headroom before doubt is covered. Next subtract a set reserve for fade, site change, install error, and measure error. A positive release margin is still just a model result. The last stage must test hard places and real work states. Compute the normal headroom, protect a clear reserve, and test the installed path. A vendor range claim or one good RSSI value cannot replace any of those steps.

RSSI Is Not a Universal Grade

dBm is an absolute power unit. RSSI is a receiver-reported strength indicator that may be calibrated differently across chipsets and radio families, so the same RSSI can be healthy for one link and unusable for another.

  • Compare RSSI with the sensitivity of the exact receiver mode.
  • Compare RSSI with SNR, retry count, packet delivery, and time-of-day behavior.
  • Do not copy alert thresholds from a different radio technology.
  • Treat a single RSSI reading as a clue, not a deployment proof.

Example: -85 dBm means very different things at sensitivity -92 dBm (raw margin 7 dB) versus -120 dBm (raw margin 35 dB). High RSSI with poor delivery often points to interference or receiver overload; low RSSI with poor delivery points toward path loss, antenna, placement, or sensitivity.

Before RSSI Is Not a Universal Grade, inspect the figure Figure 31.4. Compare Link-budget review record with Requirement; their difference reveals The link-budget review record ties the requirement to reviewed radio terms, a path estimate, site validation, and an explicit release decision. This gives RSSI Is Not a Universal Grade evidence to revisit.

Read Figure 31.4 downward from the requirement through the radio terms and predicted margin to site validation. The final branch accepts or redesigns the link using measured conditions; the calculation alone does not approve deployment.

Interactive Review

Log-Distance Knowledge Check

Common Pitfalls

  1. Multiplying FSPL by the path-loss exponent. Use the log-distance model from a reference point; multiplying the whole FSPL result by n / 2 greatly overstates loss and hides the assumption.
  2. Treating a closed spreadsheet as a released link. A spreadsheet shows the link might close; it does not prove mounting, clutter, interference, delivery, or seasonal variation.
  3. Forgetting receiver mode. Sensitivity changes with data rate, bandwidth, coding, and error target. Use the mode that ships.
  4. Copying RSSI thresholds across radios. A value that is weak for one link can be healthy for another with different sensitivity, bandwidth, modulation, and SNR.

At this depth, a link is a chain of limits: transmit power, antenna gain, path loss, environment, receiver sensitivity, reserved margin, and measured evidence. A trustworthy decision records each limit instead of trusting one optimistic range number.

31.6 Checkpoint: Summary

This section: Checkpoint: Summary

  • Path loss is the baseline cost of distance, frequency, and environment; free-space loss is the clean-air reference and doubling distance or frequency each adds about 6 dB.
  • The log-distance model describes how loss grows from a reference distance in a real site; the exponent belongs in the distance term, never as an n / 2 multiplier on total FSPL.
  • A link budget adds gains, subtracts path and installation losses, compares the result with receiver sensitivity, and reserves margin for variation.
  • Margin has three layers: raw, reserved, and verified; only verified margin reflects real site evidence.
  • RSSI is meaningful only against the specific receiver’s sensitivity, SNR, and delivery, not as a universal grade.

31.7 Key Takeaway

This section: Key Takeaway — A link budget connects transmit power, antenna gain, path loss, receiver sensitivity, and fade margin into one auditable decision.

A link budget connects transmit power, antenna gain, path loss, receiver sensitivity, and fade margin into one auditable decision. It is the first sanity check before promising wireless range, and the site measurement is the proof.

31.8 See Also

This section: See Also

Radio Wave Basics for IoT

Review frequency, wavelength, and antennas before calculating loss.

Fading and RF Interference

See why reserved margin can disappear in the field and how to tell coverage from coexistence problems.

Practical Wireless Lab

Validate path-loss and margin assumptions against measured evidence.

Find help

3 reviewed answers.

Where should I start in a module?

Open the module page from the sidebar to see its chapters in order. Use the module map to return to a topic you need.

Modules and paths

Reviewed

What can I try when a project does not work?

Check the symptom, then work through the diagnostic steps. Keep the error message and the smallest example that reproduces it.

When you are stuck

Reviewed

How do interactive examples work?

Use the interactive guide to check how examples and simulations work before changing your project.

Interactive examples guide

Reviewed