Wi-Fi & 802.11 · Study deck

802.15.4 Deployment Practices

IEEE 802.15.4 is a low-power radio and link standard.

Radio Remi is your guide for this deck.

ieee-802-15-4deploymentsite-survey

Radio Remi, the module guide, in a scene from this chapter.

After studying this chapter

Learning objectives

You will be able to:

Explain: The core relationship is the link budget: received power = transmit power + antenna gains − path loss, and the link margin is how far that received power sits above the receiver's sensitivity.
Explain: That retry pattern can make a plausible bench battery estimate wrong after installation, so the deployment record should include the measured retry count used by the power calculation.
Explain: Deployment turns the radio's numbers into a real link: how much signal actually reaches the receiver, and how much margin is left before the link drops.
plan 802.15.4 deployment evidence loops

Major section

Begin With One Installed Link

IEEE 802.15.4 is a low-power radio and link standard.

Firmware is the code that runs on a device.
A range claim from a data sheet is not the field result.
More link margin can aid repair, but a louder or busier design may use more power and disturb peers.

Major section

Begin With One Installed Link (continued)

A map of real misses is worth more than one best range.

More relays can add paths, but they add upkeep and air use.
One site pass does not prove all seasons or loads.
If a relay is part of the claim, remove it once.

Major section

Deployment Evidence Loop

The loop connects planning assumptions to repeatable acceptance evidence.

A deployment decision should move from observation to a bounded test, then to commissioning and monitoring.
If the site changes, the loop reopens.

Deployment evidence loop from site survey through topology, channel choice, link validation, power measurement, commissioning, monitoring, and retest.

Major section

Acceptance Record

The record joins radio planning to installed measurements, commissioning, and future change control.

Finish at the retest trigger: it connects today's acceptance to the conditions under which the deployment must be measured again.
The record should make the decision reviewable months later when a wall moves, an access point changes, firmware is updated, or more devices are added.

Deployment acceptance record showing site baseline, role plan, channel evidence, link results, power evidence, commissioning record, and retest trigger.

Major section

Worked Review Examples

A lighting retrofit adds 802.15.4 wall sensors to an office with existing Wi-Fi.

The acceptable answer is not a single channel number.
Failures cluster near metal racks and during shift changes.
The fix may combine placement, topology, and traffic shaping.
A channel change alone may not address the real cause.

Major section

Deployment Is a Link-Budget Question

An 802.15.4 device may pass every bench test and still fail once it is bolted to a wall.

Deployment turns the radio's numbers into a real link: how much signal actually reaches the receiver, and how much margin is left before the link drops.
The same loop should connect RF, power, and maintenance.

A link budget is a waterfall: add gains, subtract losses, and confirm the received power stays above receiver sensitivity after a reserved fade margin.

Major section

Deployment Is a Link-Budget Question (continued)

The core relationship is the link budget: received power = transmit power + antenna gains − path loss, and the link margin is how far that received power sits above the receiver's sensitivity.

This connects calculation to placement, fading, and the deployment acceptance record.
A frame can arrive with strong RSSI but poor LQI when interference harms reception — so both matter.
That difference tells the reviewer where to move a router, change channel, rotate an antenna, or reject the location before sign-off.

Major section

Work a Real Link Budget

Free-space path loss at 10 m and 2.44 GHz is about 60 dB ( FSPL = 20 log₁₀d + 20 log₁₀f − 27.55 ).

If Parent B also reports steadier LQI and fewer retries, it is the better commissioning parent even if Parent A is physically closer.
If a marginal link causes three retries per report, the radio is awake for more attempts, channel access, acknowledgments, and backoff time.
That retry pattern can make a plausible bench battery estimate wrong after installation, so the deployment record should include the measured retry count used by the power calculation.

Major section

Fade Margin, Multipath, and LQI-Driven Routing

The hidden failure is that every layer can look acceptable in isolation.

2.4 GHz waves are ~12 cm long, so they reflect off metal shelving and reinforced walls and arrive via multiple paths that can add or cancel.
A device that reads a healthy −70 dBm today may drop 15 dB when a metal cart parks in the Fresnel zone.
RSSI can be above sensitivity, but interference can still lower LQI.

Major section

Fade Margin, Multipath, and LQI-Driven Routing (continued)

That variability is why deployers budget a fade margin — commonly 10–20 dB of headroom — rather than installing at the edge of sensitivity.

LQI can inform routing, but the chosen stack may use link cost, estimated transmission count, or other metrics rather than raw LQI.
Mesh stacks built on 802.15.4 can prefer neighbours with consistently good links over merely nearby ones.
A poor-quality neighbour that happens to be one hop away can be a worse parent than a slightly farther neighbour with a clean link.

Major section

Fade Margin, Multipath, and LQI-Driven Routing (continued)

Worked example: A warehouse sensor installs against a steel column and shows −88 dBm / low LQI with occasional retries.

No firmware or power change was needed — only respecting the link budget and the physics of the band.
LQI can look acceptable during a quiet test, but a burst of application traffic can expose collisions and backoff delay.
Packet success can look fine near the coordinator, but the same device may churn between parents when a powered router is unplugged for maintenance.

Deck summary

Key takeaways

IEEE 802.15.4 is a low-power radio and link standard.

A map of real misses is worth more than one best range.
The loop connects planning assumptions to repeatable acceptance evidence.
The record joins radio planning to installed measurements, commissioning, and future change control.
A lighting retrofit adds 802.15.4 wall sensors to an office with existing Wi-Fi.

Retrieval practice

Recall check 1 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q1A replacement 802.15.4 sensor joins at its installed location but does not resume reporting after its parent changes. What commissioning evidence should be checked?

AIts location, assigned role and parent path, rejoin trace, application outcome, and recovery owner.

BOnly the raw PHY rate listed in the device specification.

CWhether every device in the fleet has a full-function radio.

DA generic channel map from another deployment.

Show answer

Answer: A Commissioning records must tie location, role, rejoin, delivered service, owner and retest trigger to a replacement.

Retrieval practice

Recall check 2 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q2A battery sensor claims long life from its radio label. Which test supports the claim?

AUse the battery rating because nominal capacity alone determines this device's operating life.

BModel sleep current as zero for the battery-life estimate

CMeasure sleep, wake, radio, retries and recovery on site

DMultiply only the transmit current by payload bytes

Show answer

Answer: C The whole operating cycle sets energy use.

Q3An installer replaces a failed node but cannot recover its join settings. What record was missing?

AIdentity, location, parent, key custody, reset and rejoin record.

BOnly the vendor brochure and default join instructions.

COnly the first successful packet after installation.

DOnly the network drawing from the original deployment.

Show answer

Answer: A Commissioning records make replacement and diagnosis repeatable.

Retrieval practice

Recall check 3 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q4What is the 'link margin' for an 802.15.4 deployment?

AThe signal exceeds receiver sensitivity by a margin in dB.

BThe number of hops between a device and the coordinator.

CThe percentage of the 127-byte frame used by payload.

DThe difference between 2.4 GHz and 868 MHz data rates.

Show answer

Answer: A Margin = received power - sensitivity; it is the headroom before fading drops the link.

Retrieval practice

Recall check 4 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q5A node reads RSSI = -84 dBm with sensitivity -95 dBm. What does the ~11 dB margin tell a deployer?

AIt works now, but fade headroom is thin.

BThe link has failed, since -84 dBm is below -95 dBm.

CMargin is irrelevant because LQI is the only trustworthy metric.

DIt means the data rate has dropped to 20 kbit/s.

Show answer

Answer: A About 11 dB of headroom is vulnerable to moving obstacles or interference, so the deployer should seek a steadier parent, placement, or router position.

Retrieval practice

Recall check 5 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q6Why may an 802.15.4 mesh stack weigh link quality rather than always choosing the physically nearest neighbour?

ANearest may be noisy; a farther parent can have a steadier link.

BBecause LQI estimates physical distance without requiring node coordinates.

CBecause LQI increases the transmit power on the chosen link.

DBecause the strongest local LQI identifies the route with the fewest hops.

Show answer

Answer: A Link quality can reveal a more reliable parent than distance alone.

Print reference

Answers 1 of 2

Answer key.

A · Commissioning records must tie location, role, rejoin, delivered service, owner and retest trigger to a replacement.
C · The whole operating cycle sets energy use.
A · Commissioning records make replacement and diagnosis repeatable.
A · Margin = received power - sensitivity; it is the headroom before fading drops the link.
A · About 11 dB of headroom is vulnerable to moving obstacles or interference, so the deployer should seek a steadier parent, placement, or router position.

Print reference

Answers 2 of 2

Answer key.

A · Link quality can reveal a more reliable parent than distance alone.