23 Link Budget and Coverage Planning

A link budget is the radio range ledger for an IoT deployment. It starts with transmit power, adds antenna gains, subtracts cable, path, obstacle, and reserve losses, then compares the predicted received power with receiver sensitivity. The useful output is not a single optimistic range number. It is the remaining margin and the assumptions that created it.

Use the record before choosing gateway spacing, antenna placement, enclosure location, or battery targets. If the ledger has no named environment, no reserve margin, or no field measurement plan, the design is still a guess.

The ledger matters because every term answers a different review question. Transmit power and antenna gain describe how much useful signal leaves the device. Cable loss, connector loss, and antenna orientation describe how much of that launch power actually reaches the path. Path loss, material attenuation, Fresnel clearance, foliage, and body blocking describe what the site does to the signal. Receiver sensitivity and the required packet success target describe how weak the signal can be before the application stops meeting its requirement.

A simple budget also makes trade-offs visible. Suppose a device launches 14 dBm, gains 2 dB from its antenna path, loses 96 dB to distance, and loses another 15 dB to the site. The predicted received power is -95 dBm. If the deployed receiver mode is sensitive to -118 dBm and the design requires 10 dB of reserve, the remaining release margin is 13 dB. That is a reviewable decision. If any input changes, the team can recompute the same ledger instead of debating a vague range claim.

Ground overview: a link budget turns range into a checkable record with the visual at Figure 23.1. Start from Link Budget Decision Process, but keep Turn radio choices into a pass/fail engineering decision visible while evaluating the decision is a chain: radio settings create launched power, deployment losses reduce it, and the remaining margin decides whether the link is.

Trace the visual from Link Budget Decision Process to Turn radio choices into a pass/fail engineering decision in Figure 23.1; verify Start with before concluding. Together those labels make the decision is a chain: radio settings create launched power, deployment losses reduce it, and the remaining margin decides whether the link is testable. Apply their boundary when working through overview: a link budget turns range into a checkable record.

A useful link budget is traceable. Each number should have a source, a location, and an owner: radio configuration, antenna datasheet, cable length, path model, measured RSSI, or field survey. Keep the calculation simple enough that a field engineer can update it when gateway height, antenna alignment, enclosure material, or sensor location changes.

Build the record in the same order the signal experiences the path. Start with the transmitter and antenna system, then the open-air or log-distance path estimate, then installation losses, then receiver sensitivity, then reserve. Add a short evidence note beside each uncertain term. For example, wall loss may come from a site survey, a conservative design allowance, or an early RSSI walk test. The review should be able to tell which terms are measured, which are data-sheet values, and which are deliberate safety allowances.

After installation, keep the budget alive. Field measurements should not replace the record; they should calibrate it. If measured RSSI is weaker than predicted, update the loss assumption and check whether similar paths are also at risk. If measured RSSI is stronger than predicted, keep the conservative reserve unless the team has enough representative samples to reduce it. That habit turns the link budget into an operating document for gateway moves, enclosure changes, seasonal foliage, and radio-mode updates.

Use Figure 23.2 to prepare the decision in practitioner: build the budget as a deployment ledger. The diagram names LPWAN Link Budget and Understanding Maximum Coupling Loss (MCL), the two anchors needed to assess lpwan coverage planning depends on a ledger of radio terms, path assumptions, installation losses, and the margin required for reliable reporting.

Trace the visual from LPWAN Link Budget to Understanding Maximum Coupling Loss (MCL) in Figure 23.2; verify Transmitter before concluding. Together those labels make lpwan coverage planning depends on a ledger of radio terms, path assumptions, installation losses, and the margin required for reliable reporting testable. Apply their boundary when working through practitioner: build the budget as a deployment ledger.

Where The Antenna-Gain Line Actually Comes From

The ledger's antenna-gain line is not a number to look up once and forget. It is a choice between antenna types that trade directionality for reach, and that choice decides how much of the launched power actually lands where the deployment needs it. An omnidirectional antenna radiates in all directions around one plane, spreading a fixed amount of power over the widest area and giving the least gain of the common choices. A Yagi antenna lines up several parallel elements to concentrate that same power into a narrower beam, trading coverage angle for a substantial gain increase. A parabolic reflector antenna goes further, using a dish or mesh reflector built larger than the wavelength it focuses to concentrate power into a tight beam with the highest gain of the three, at the cost of needing the far end to stay inside that narrow beam.

Selecting between them is a directionality, gain, and bandwidth decision made together, not a single spec copied from a datasheet: how tightly can the deployment predict where the far end will be, how much gain does the remaining margin actually need, and does the antenna's usable bandwidth cover the intended band. The same decision should also record polarization. A receiver's orientation is rarely known in advance -- a handheld device, a vehicle-mounted sensor, or a tag on a rotating asset can present any polarization to the antenna. Some access points answer this by propagating both vertical and horizontal polarization, or by using a configurable or diversity antenna, so an unknown receiver orientation does not silently turn into an unrecorded polarization-mismatch loss. Treat polarization the same way the ledger already treats cable loss: name it in the record, or budget an explicit mismatch allowance for it.

Before practitioner: build the budget as a deployment ledger, inspect Figure 23.3: Link Budget Waterfall must be considered with TX power. That visual pairing grounds a waterfall view helps review every gain and loss in order, especially when a design looks good on path loss alone but weak after installation losses in named evidence.

Within the diagram, Link Budget Waterfall opens Figure 23.3; TX power provides the counterpoint, and +14 dBm closes the inspection. This reading constrains a waterfall view helps review every gain and loss in order, especially when a design looks good on path loss alone but weak after installation losses and supplies the visual evidence for practitioner: build the budget as a deployment ledger.

Once the ledger fields are named, the fastest way to see how they trade off is to move them. Try the range calculator below to estimate wireless range from link budget, path loss, receiver sensitivity, and fade margin, and to compare that estimate across common IoT protocols under the same deployment assumptions.

The budget is arithmetic, but the risk is in the assumptions. Free-space path loss is a baseline, not a site guarantee. Receiver sensitivity depends on data rate, bandwidth, coding, and required error behavior. Antenna gain depends on orientation and mounting. A clean design keeps those assumptions visible instead of hiding them inside one range claim.

dB arithmetic is useful because gains and losses can be added in one chain, but it can also hide weak evidence. A 6 dB antenna gain only helps when the antenna pattern points toward the receiver and is mounted away from detuning surfaces. A receiver sensitivity number only applies to the bandwidth, coding, spreading, data rate, packet error target, and interference assumptions used to measure it. A path-loss number only applies to the environment model and distance convention recorded with it.

Margin is therefore not spare decoration at the end of the spreadsheet. It is the buffer between an assumed world and the deployed world. Fade, multipath, human movement, wet foliage, antenna tilt, component tolerance, enclosure changes, and measurement error all consume that buffer. When the reserve is too small, the system may work during commissioning and fail later under normal site variation. When the reserve is visible, engineers can decide whether the right fix is more gateway density, a different mounting point, a slower radio mode, or a field survey.

For review, separate nominal margin from release margin. Nominal margin is predicted received power minus receiver sensitivity. Release margin subtracts the reserves the team promised to protect: fade allowance, installation uncertainty, site-change allowance, and measurement uncertainty. That second number is the one that should drive approval because it says what headroom remains after known risk has been paid for.

Use Figure 23.4 to prepare the decision in under the hood: margin is where assumptions become risk. The diagram names Link Budget Calculator and End-to-End Power Analysis, the two anchors needed to assess the calculation is additive in db units: add gains, subtract losses, then compare the result with receiver sensitivity.

Compare Link Budget Calculator with End-to-End Power Analysis inside the visual at Figure 23.4. Next find TX Power, which completes the scope of the calculation is additive in db units: add gains, subtract losses, then compare the result with receiver sensitivity. The decision in under the hood: margin is where assumptions become risk must preserve that labelled boundary.

The visual evidence for under the hood: margin is where assumptions become risk sits in Figure 23.5. Find Raw margin is not the release decision beside stronger before interpreting margin is the gap between the predicted received power and the receiver threshold after deployment losses and reserve have been accounted for.

At Raw margin is not the release decision in Figure 23.5, compare the diagram with stronger; then locate weaker. That labelled check bounds margin is the gap between the predicted received power and the receiver threshold after deployment losses and reserve have been accounted for. For under the hood: margin is where assumptions become risk, retain weaker as evidence for the resulting choice.

Before under the hood: margin is where assumptions become risk, inspect Figure 23.6: LoRaWAN Urban vs Rural Coverage must be considered with Same Hardware, 5–10x Range Difference. That visual pairing grounds the same radio can behave very differently in dense urban, indoor, and open rural paths because the environment changes the loss terms in named evidence.

Begin Figure 23.6 with LoRaWAN Urban vs Rural Coverage, then distinguish Same Hardware, 5–10x Range Difference and URBAN. The diagram separates LoRaWAN Urban vs Rural Coverage from Same Hardware, 5–10x Range Difference within the same radio can behave very differently in dense urban, indoor, and open rural paths because the environment changes the loss terms. Keep both distinctions explicit in under the hood: margin is where assumptions become risk.