3 LPWAN Link Budget and Range

Overview: Link Budget Is Signal Accounting

An LPWAN link budget is a review record, not a range promise. It adds the useful signal contributions, subtracts losses, compares the expected received signal with receiver sensitivity, and keeps margin for fading, clutter, antenna placement, enclosure loss, and measurement uncertainty.

The result is not "this device reaches ten kilometers." The result is a bounded statement: under these assumptions, this link has enough or not enough remaining margin to justify a pilot.

Suppose a farm water-monitoring project wants one gateway to cover hill tanks, buried meter pits, and a shed-mounted pressure sensor. The radio ledger may begin with a healthy raw budget, but the buried pits need enclosure and ground-level penalties, the shed sensor needs wall-loss allowance, and the hill tanks need wind-driven antenna alignment checks. If the raw budget is 149 dB and the review reserves 10 dB for fading, 12 dB for obstruction, and 4 dB for installation uncertainty, only 123 dB remains for path loss. A model estimate of 118 dB is a pilot candidate; an estimate of 128 dB is not a "maybe" range claim. It is a design gap unless the team changes antenna placement, gateway density, radio settings, or the device location.

The overview record should therefore state the acceptance rule before field work starts. A pass might mean every representative location keeps at least the reserved margin while using an allowed data rate and legal transmit setting. A conditional pass might allow the hill tanks but require a second gateway for buried pits. A fail should name the design change, not leave a vague note that the range was shorter than expected.

The claim that A defensible range claim starts with a ledger and ends with field evidence needs “settings” as a concrete check beside “Gains”. Inspect Figure 3.1 before continuing the “settings”–“gains” decision, especially “settings” beside “Gains”.

Trace the review path across Figure 3.1 from “settings” to “Gains”. From “antennas”, it arrives at “Losses”. That path is evidence for A defensible range claim starts with a ledger and ends with field evidence; retain it when revisiting the “settings”–“gains” decision.

Practitioner: Turn the Ledger into a Margin Decision

Start by calculating raw link budget, then remove the margins and allowances that should not be spent by normal path loss. What remains is maximum allowable path loss. That value can be compared with a model estimate or measured field result.

To ground the “transmitter”–“+14 dbm tx” decision through “+2 dBi Ant” in visible evidence about “Transmitter”, inspect Figure 3.2. Its named elements “Transmitter” and “+14 dBm TX” frame the claim that The estate link-budget example keeps the accounting visible instead of hiding it inside a single range number.

The first useful contrast in Figure 3.2 is “Transmitter” versus “+14 dBm TX”. After resolving it, move from “+2 dBi Ant” to “= +16 dBm EIRP”. This is how the visual substantiates The estate link-budget example keeps the accounting visible instead of hiding it inside a single range number and reconnects it to the “transmitter”–“+14 dbm tx” decision.

To ground the “healthy”–“pilot” decision through “Redesign” in visible evidence about “Healthy”, inspect Figure 3.3. Its named elements “Healthy” and “Pilot” frame the claim that The margin gate turns a calculation into an engineering decision.

Read Figure 3.3 with “Healthy” as the anchor; treat “Pilot” as the first comparison. Then connect “Redesign” with “Unsuitable”. Those labels make The margin gate turns a calculation into an engineering decision a traceable part of the “healthy”–“pilot” decision, not an unsupported assertion.

The practitioner decision should also name the evidence owner. If the gateway is moved from a mast to a building wall, the link-budget owner must rerun the allowance, not simply reuse the earlier pass result. If a product team adds confirmed messages or a larger payload, the margin gate should be reopened because retry behavior and airtime can turn a coverage pass into an operations failure. The ledger is strongest when it records both the numeric answer and the condition that would make that answer stale.

Under the Hood: Models Need Field Evidence

Path-loss models translate distance and environment assumptions into estimated loss. A free-space estimate is a clean baseline, while log-distance and clutter-aware models add assumptions about terrain, buildings, foliage, antenna height, and indoor penetration. The model is useful only when its assumptions are documented and tested.

Start the evidence review for the “+14 dbm”–“antenna gain” decision: inspect Figure 3.4. Two labels deserve attention—“+14 dBm” and “Antenna gain”—because they bound Path-loss evidence matters only after margins and allowances have been reserved.

Inspect “+14 dBm” on Figure 3.4, compare “Antenna gain”, then ask what carries “+2 dBi” into “Cable loss”. Their answers support Path-loss evidence matters only after margins and allowances have been reserved while keeping the “+14 dbm”–“antenna gain” decision connected to observable evidence.

Treat every model output as a hypothesis to challenge. If the model assumes antennas several metres above ground but the real device is bolted inside a metal cabinet, the path-loss estimate is optimistic even when the arithmetic is correct. If the model assumes clear outdoor terrain but the deployment has wet foliage, reinforced concrete, or a service vehicle parked beside the enclosure, the field record must either measure those conditions or reserve enough margin to survive them. Gateway density is the same kind of under-the-hood question. One gateway may satisfy a coverage model yet still create weak receive diversity, high channel load, poor downlink opportunity, or fragile incident response. The release evidence should connect path-loss samples, gateway count, traffic pattern, and retest triggers into one decision.

Make the acceptance threshold explicit in the same record. For a rollout gate, the team might require each representative device class to keep reserved margin, join without repeated retries, avoid spending most traffic at the slowest data rate, and show at least one retest trigger for seasonal or installation change. Those criteria keep the model, the measurement, and the release decision tied together.

The reason to inspect “Gateway” in Figure 3.5 now is to verify Gateway count is not only a coverage radius choice; it also affects diversity, load, downlink pressure, and the quality of field evidence. In the “gateway”–“count” decision, that verification begins by separating “Gateway” from “count”.

Use “Gateway” as the entry point to Figure 3.5. Read “count” next, with “shapes six effects” as the bridge to “Coverage radius”. This route gives practical meaning to Gateway count is not only a coverage radius choice; it also affects diversity, load, downlink pressure, and the quality of field evidence and supplies the review sequence for the “gateway”–“count” decision.

A field team should therefore test the awkward cases on purpose. Put one device in the lowest meter pit, one behind the metal shed wall, one at the edge of the service area, and one near the busiest reporting cluster. Record received signal, noise margin, spreading factor or data-rate distribution, retries, join behavior, gateway identity, and whether a second gateway also heard the packet. If every easy point passes but the low pit consumes all reserved margin, the correct result is not "range proven"; it is "coverage depends on installation constraints." If many edge devices pass only at the slowest rate, the team should also check airtime and downlink pressure before approving the gateway count.

The reason to inspect “Locations” in Figure 3.6 now is to verify The field record should test the assumptions most likely to fail. In the “locations”–“open, indoor, edge, obstructed” decision, that verification begins by separating “Locations” from “open, indoor, edge, obstructed”.

Trace Figure 3.6 by asking what “Locations” establishes and what “open, indoor, edge, obstructed” changes. Check “Signal” next, ending at “received power and noise margin”. That progression is the mechanism behind The field record should test the assumptions most likely to fail and the evidence order needed for the “locations”–“open, indoor, edge, obstructed” decision.