9  Lab: Wi-Fi Spectrum Analysis

Keywords

Wi-Fi spectrum analysis, Wi-Fi channel planning, IoT Wi-Fi survey, Wi-Fi coexistence, RSSI evidence

9.1 Start With the Wireless Story

A spectrum lab turns invisible contention into evidence. Start by scanning who is using each channel, how strong those signals are, where congestion appears, and what channel plan or retest note follows from the measurements.

9.2 In 60 Seconds

A Wi-Fi spectrum lab turns scans into a defensible channel and coexistence decision. The useful output is not a long scanner program. It is a clear record of where scans were taken, which networks were observed, which channels and bands are crowded, whether the intended device can attach in the installed form, and what must be retested after access point, antenna, enclosure, channel, firmware, or site changes.

This lab keeps the review practical:

• define the Wi-Fi service claim and device locations
• scan from representative points, not only from the desk
• record channel, band, signal, and AP identity where available
• separate weak signal from channel crowding, adjacent-channel overlap, authentication, DHCP, backhaul, and power problems
• make one bounded channel, placement, or band decision at a time
• save the decision and retest triggers

Phoebe’s Field Notes: Why Channel 165 Loses 7.66 dB That Channel 1 Doesn’t

Phoebe’s Why

Every channel this lab scans is a wavelength in disguise. A radio wave’s speed is fixed at \(c\), so frequency and wavelength are locked together – name the channel and the wavelength follows automatically. That wavelength decides two things a channel-occupancy survey never shows directly: how big the antenna wants to be, and how much power a fixed-size receive antenna collects from a fixed distance, since its effective aperture shrinks with the square of frequency. Climbing from the crowded 2.4 GHz band to a quiet 5 GHz channel does not just move the survey to less contested spectrum – it also spends real decibels of range and wall penetration to get there, before a single AP is counted.

The Derivation

The speed lock fixes wavelength once the channel is chosen:

\[\lambda = \frac{c}{f}\]

A fixed-size receive antenna collects power over an aperture that shrinks with wavelength squared, so free-space loss between two channels at the same distance depends only on their frequency ratio:

\[\Delta\mathrm{FSPL} = 20\log_{10}\frac{f_2}{f_1}\]

Worked Numbers: This Lab’s Own Channels

• Channel 1 (2412 MHz): \(\lambda = 3.00\times10^{8}/2.412\times10^{9} = 0.1244\) m \(= 12.4\) cm; quarter-wave element \(\approx 3.11\) cm
• Channel 165 (5825 MHz): \(\lambda = 3.00\times10^{8}/5.825\times10^{9} = 0.0515\) m \(= 5.15\) cm; quarter-wave element \(\approx 1.29\) cm – less than half the size, which is exactly why 5 GHz radios shrink so easily onto a small board
• Same-distance frequency penalty, channel 1 to channel 165: \(20\log_{10}(5825/2412) = 7.66\) dB, a \(10^{7.66/10} \approx 5.83\times\) drop in received power before either band’s wall loss or channel congestion is even measured
• What this buys the survey: the three non-overlapping 2.4 GHz channels (1, 6, 11) trade capacity for range; the UNII-3 channels (149-165) this chapter lists trade that same 7.66 dB of range for a quieter, wider band – “move to 5 GHz to dodge congestion” is a coverage trade, not a free upgrade, and the survey should record which one the deployment actually needs

9.3 Learning Objectives

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

• create a Wi-Fi survey record that separates observation from recommendation
• classify channel crowding, overlap, weak signal, and non-spectrum failures
• connect scan points to real IoT device locations, enclosure states, and access point placement
• explain why channel choice differs between 2.4 GHz, 5 GHz, and 6 GHz deployments
• produce a retest plan after channel, AP, antenna, enclosure, firmware, or site changes

Quick Check: Wi-Fi Spectrum Lab

9.4 Lab Scope

Use this lab when Wi-Fi is a candidate or selected radio for an IoT deployment. It is useful before installation, during troubleshooting, and after a site or network change.

The lab should answer five questions:

• What Wi-Fi service area or device locations are being reviewed?
• Which band, channel width, security mode, and AP or controller context are in scope?
• What do scans show at the real device locations?
• Is the first failing layer signal, congestion, overlap, authentication, addressing, roaming, backhaul, power, or application behavior?
• What channel, placement, band, or retest decision follows from the evidence?

9.5 Survey Evidence Flow

Wi-Fi spectrum review should move from claim to scan evidence before changing the channel plan.

Figure 9.1: Wi-Fi spectrum survey evidence flow

9.6 Equipment And Setup

Use tools that match the decision you need to make:

• a Wi-Fi scanner, controller view, access point logs, or managed-network dashboard
• the target IoT device or a representative client
• the intended antenna, enclosure, power state, and mounting position
• a floor plan, route sketch, photo set, or named point list
• a record sheet for point name, band, channel, AP identity, signal, and symptom notes

If a phone or laptop scanner is used instead of the target IoT device, record that substitution. Different antennas, drivers, roaming behavior, and power states can produce different observations.

9.7 Define The Survey Claim

Start by writing the claim that the survey must support. Examples:

• “These sensors must attach to the warehouse Wi-Fi from their installed shelves.”
• “The commissioning tablet must stay connected along this maintenance route.”
• “The AP channel plan should reduce overlap for the 2.4 GHz IoT network.”
• “The device should use the selected band without moving to an unreliable AP.”

Do not survey the entire building by default if the design only needs a set of devices, cabinets, shelves, or routes. A narrower claim usually creates better evidence.

9.8 Mark Scan Points

Choose scan points that represent the deployment:

• planned IoT device locations
• route edges and handoff areas
• corners, cabinets, metal structures, and shielded rooms
• locations near microwave ovens, machinery, dense shelving, water, or crowds
• places where the device will be enclosed, wall mounted, battery powered, or low to the floor
• locations that previously showed weak coverage or unstable service

For each point, record the device orientation, height, enclosure state, and whether the point is final or exploratory.

9.9 Collect Wi-Fi Observations

Run it: Reproduce the scan in the channel analyzer below before you walk the site. Watch which APs land on each channel and how much airtime each channel is using, so you can tell a genuinely crowded channel from a merely busy one and see where 2.4 GHz neighbors overlap. Read the band, channel, neighbor, and utilization evidence off the analyzer and record it against each scan point below.

At each point, capture the fields available from your tool:

• band and channel
• AP or BSSID identity when visible
• SSID or network role, without recording secrets
• signal quality from the scanner or client
• visible neighboring networks and their channel use
• noise, retries, channel utilization, or airtime clues when the tool provides them
• association, authentication, addressing, and application symptom notes
• time, site activity, doors, people movement, and equipment state

For 2.4 GHz plans using 20 MHz channels in common channel sets, channels 1, 6, and 11 are often used to avoid overlap. Do not apply that rule blindly to every region, channel width, or 5/6 GHz plan. The survey record should say which band and channel plan it is reviewing.

9.10 Classify The First Symptom

Keep the diagnosis tied to the first failing layer.

• Weak signal: the intended AP is visible but the client has low or unstable signal evidence at the installed point.
• Crowded channel: many strong neighboring APs share the same channel or tool evidence shows airtime pressure.
• Adjacent overlap: nearby channels overlap a 2.4 GHz plan and can cause avoidable contention.
• Wrong AP or roaming: the client attaches to an unexpected AP or switches at the wrong location.
• Authentication or addressing: the radio can see the AP, but security, DHCP, VLAN, or policy setup fails.
• Backhaul or application: Wi-Fi attachment is clean, but the network path or application test fails.
• Power or enclosure: the device changes behavior when the final enclosure, antenna, or transmit state is used.

Only the first three are primarily spectrum or channel-plan findings. The others must be recorded so they are not incorrectly fixed with channel changes.

9.11 Coexistence Review Map

Use the survey map to separate signal problems from overlap and non-spectrum failures.

Figure 9.2: Wi-Fi and Zigbee Channel Interference

9.12 Decision Options

Each finding should lead to one bounded decision:

• Change channel when evidence shows avoidable overlap or strong same-channel contention.
• Change band when the device, AP, and deployment policy support another band and the survey evidence justifies it.
• Adjust AP placement or power when several scan points show a shared boundary or roaming problem.
• Change device placement or antenna orientation when only one installed point is weak and the device location is flexible.
• Review security or addressing when the client sees the AP but cannot complete network attachment.
• Review backhaul or application path when Wi-Fi attachment is clean but the service still fails.
• Retest installed form when open-bench evidence differs from enclosure, mounting, or battery-powered evidence.

Record one change at a time when the goal is diagnosis. If several changes are made together, mark the result as exploratory rather than accepted evidence.

9.13 Lab Record Template

For each scan point, record:

• point name and map reference
• device, firmware, enclosure, antenna, mounting, and power state
• scanner or client tool used
• band, channel, channel width if known, SSID role, and AP identity when visible
• signal observation and scan timestamp
• neighboring channel pressure or overlap clues
• association, authentication, addressing, roaming, backhaul, and application notes
• first failing layer
• decision and next action
• retest trigger

Redact secrets, private identifiers, credentials, and network names that should not be shared.

9.14 Worked Review: Crowded Channel

Scenario: an IoT device attaches to the intended AP, but scans at several nearby points show strong neighboring networks sharing the same 2.4 GHz channel.

Good review sequence:

1. Confirm the device, AP identity, band, channel, and installed point.
2. Compare scan points near the device and near the AP.
3. Check whether the symptom is weak signal, same-channel pressure, adjacent-channel overlap, or wrong AP attachment.
4. Change only the channel plan or only the AP placement for the next test.
5. Retest the same points and record whether the symptom changed.

Accepted answer: “This is a channel-plan finding only if the evidence points to channel pressure or overlap. If the client is failing authentication or addressing, changing channels is the wrong fix.”

9.15 Worked Review: Strong Signal But No Data

Scenario: a scanner shows strong signal from the intended AP at the device location, but the IoT application cannot publish data.

Good review sequence:

1. Do not mark the location as a weak coverage point.
2. Check association, authentication, addressing, and policy evidence.
3. Check backhaul reachability or gateway logs if Wi-Fi attachment is clean.
4. Check power behavior during active transmit if the device resets or disappears.
5. Record the first failing layer and retest that layer.

Accepted answer: “Strong signal with failed data is ambiguous until network attachment, backhaul, and application layers are checked.”

9.16 Common Mistakes

• scanning only from a laptop at a desk instead of the installed device locations
• treating a phone scan as final evidence for a different IoT antenna and enclosure
• changing AP channel, AP placement, and device antenna in the same retest
• applying a 2.4 GHz channel rule to every band or channel width
• ignoring wrong-AP attachment or roaming behavior
• treating authentication, addressing, backhaul, or application failures as spectrum failures
• recording only screenshots without point names, timestamps, and device state
• leaving private SSIDs, credentials, or identifiers in shared reports
• failing to retest after AP, channel, firmware, antenna, enclosure, mounting, or site changes

9.17 Knowledge Check: Wi-Fi Spectrum Analysis

9.18 Match The Evidence To The Survey Decision

9.19 Order The Wi-Fi Spectrum Lab

9.20 Review Checklist

Before accepting the Wi-Fi spectrum lab, confirm that the record includes:

• bounded Wi-Fi service claim
• representative scan points and skipped areas, if any
• target device, firmware, antenna, enclosure, mounting, and power state
• scanner or client tool used
• band, channel, AP identity, and signal observations
• neighboring channel pressure or overlap clues
• association, authentication, addressing, roaming, backhaul, and application notes
• first failing layer for weak or failed points
• one-variable retest evidence where changes were made
• redaction of secrets and private identifiers
• retest triggers after AP, channel, band, firmware, antenna, enclosure, mounting, power, or site changes

9.21 See Who Is on Each Channel, and How Busy It Is

A Wi-Fi spectrum analysis answers two questions a ping never can: which access points sit on which channels, and how much of each channel’s airtime is already consumed. In the 2.4 GHz band this matters intensely, because although channels are numbered 1–11 (US) or 1–13 (EU), each is 20 MHz wide on a 5 MHz grid — so only channels 1, 6, and 11 do not overlap.

The practical takeaway is that 2.4 GHz has effectively three usable channels. Any AP placed on 3, 8, or 9 does not gain a “new” channel; it smears energy across the neighbours of 1, 6, and 11 and raises the noise floor for everyone.

The evidence record should therefore list more than SSID and signal strength. For each scan point, capture the band, channel width, AP or BSSID identity where visible, neighboring channels, and whether the target client actually attached from its installed orientation. A clean-looking scan from a laptop at desk height can still be weak evidence for a low-power sensor inside a metal enclosure.

For a multi-AP site, channel planning is a small graph-colouring problem: APs that can hear or interfere with each other are adjacent vertices, and the available non-overlapping channels are the colours. The useful plan keeps adjacent APs on different colours where possible, reuses a channel only where distance and walls make airtime sharing acceptable, and then verifies the result with scans from the target device locations.

When several APs are visible, avoid treating “strongest AP” as the decision. Strong signal on a crowded or overlapping channel may perform worse than a slightly weaker AP on a cleaner channel. The survey should preserve the reason for the recommendation so a later firmware, AP, or site change can be retested against the same channel evidence.

The 2.4 GHz rule every survey confirms: use only 1, 6, and 11. Three non-overlapping channels is all the band offers at 20 MHz.

9.21.1 Overview Knowledge Check

9.22 Read a Scan and Judge Interference

A Wi-Fi scanner lists each visible AP with its SSID, channel, width, and RSSI; better tools add channel utilization (percent of airtime busy). Interpreting a scan means separating two kinds of interference:

• Co-channel : two APs on the same channel. They hear each other and take turns via CSMA/CA — graceful, but they share airtime, so throughput divides.
• Adjacent-channel overlap : APs on partially overlapping channels (e.g. 1 and 3). They cannot decode each other, so they do not defer — each just raises the other’s noise floor, which is worse than co-channel.

That distinction changes the repair. Co-channel crowding may be acceptable if the airtime is low, or it may require AP power changes, client steering, narrower channels, or a 5/6 GHz move. Adjacent overlap is usually a channel-plan hygiene issue: move the offending APs back to a non-overlapping plan before blaming propagation, antenna placement, or the IoT device.

Deployment heuristics are only starting points. A shared SSID can make roaming possible across APs, and modest cell overlap helps a moving client see the next AP before the old one disappears, but too much overlap creates co-channel pressure. Treat rules such as “place same-channel APs far apart” and “keep enough overlap for roaming” as hypotheses that must survive the scan, roaming log, and application-latency evidence.

Worked example. A 2.4 GHz scan shows APs on channels 1, 3, 6, 8, and 11. The APs on 3 and 8 are the problem: channel 3 overlaps both 1 and 6, and channel 8 overlaps both 6 and 11, so they inject non-decodable interference into four otherwise-clean deployments. The fix is to move every AP onto 1, 6, or 11 — converting harmful adjacent-channel overlap into manageable co-channel sharing. If channel 6 then shows 80% utilization, that is a capacity problem to solve by spacing APs or moving clients to 5 GHz, not by inventing a fourth channel.

For a defensible lab result, make the next test one-variable. If the record changes channel, AP placement, transmit power, and client band preference together, the retest may prove that something improved but not why. A good practitioner note says which channel symptom was observed, which single change addresses it, and which scan points must be repeated.

9.22.1 Practitioner Knowledge Check

9.23 5 GHz Channels, Width, and DFS

The 5 GHz band solves 2.4 GHz’s scarcity by offering many more 20 MHz channels, grouped into UNII sub-bands (UNII-1 ch 36–48, UNII-2A ch 52–64, UNII-2C ch 100–144, UNII-3 ch 149–165). But two levers complicate the analysis. Channel width can bond channels to 40/80/160 MHz for more throughput — at the cost of consuming more of the band and leaving fewer non-overlapping choices for reuse. An 80 MHz channel is four times the spectrum of a 20 MHz one, so in dense areas wider is not better.

DFS (Dynamic Frequency Selection) governs the UNII-2 channels (52–144), which are shared with radar. Before using a DFS channel an AP must perform a channel-availability check (about 60 seconds of listening) and then keep monitoring; if it detects radar it must vacate within seconds. DFS channels add lots of clean spectrum but carry the risk of a radar-triggered channel change mid-service.

That is why under-the-hood review should record the channel set, width, and DFS policy together. A survey that only says “5 GHz available” hides whether the plan has four 20 MHz reuse options, two 40 MHz options, one 80 MHz option, or a larger pool that depends on DFS channels staying usable at that site.

Worked example. A dense office keeps stuttering on 80 MHz channels because only two 80 MHz slots fit before they collide. Narrowing to 40 MHz doubles the number of non-overlapping channels, letting neighbouring APs reuse spectrum without interfering — more aggregate capacity from narrower channels. Enabling vetted DFS channels adds even more reuse, accepting the occasional radar-driven move. Spectrum analysis is what reveals that width, not raw speed rating, was the real bottleneck.

For IoT, the hidden constraint is often reliability rather than peak throughput. A low-rate device may benefit more from a stable 20 or 40 MHz plan with predictable roaming than from a wide channel that looks fast in a client speed test but collapses reuse for neighboring APs. The lab decision should match the device’s traffic, not a generic maximum-rate target.

9.23.1 Under-the-Hood Knowledge Check

9.24 Summary

Wi-Fi spectrum analysis should produce a survey record that explains why a channel, band, placement, or retest decision is justified. A clean record ties each observation to a real device point, separates channel pressure from weak signal and non-spectrum failures, and preserves the conditions that would make the decision invalid later.

9.25 Key Takeaway

Lab: Wi-Fi Spectrum Analysis should produce deployment evidence for spectrum assumptions, coverage, antenna placement, link budget, modem behavior, fallback paths, and validation limits.

9.26 Concept Relationships

• Wi-Fi fundamentals explains the channel, band, association, and management-frame context behind the survey.
• Coverage planning labs turn Wi-Fi scan points into a broader deployment acceptance record.
• Propagation design explains why enclosures, mounting, obstacles, and multipath change observed Wi-Fi behavior.
• Frequency bands explains why 2.4 GHz, 5 GHz, and 6 GHz channel decisions are not interchangeable.
• Mobile wireless review compares Wi-Fi survey evidence against cellular and low-power wireless choices.

9.27 What’s Next

• Wi-Fi Fundamentals and Standards reviews the protocol context behind Wi-Fi survey evidence.
• Lab: Coverage Planning turns scan evidence into a deployment coverage record.
• Wireless Propagation and Design explains obstacle, enclosure, and multipath effects.
• Frequency Bands and Licensing reviews band and channel context.
• Mobile Wireless Comprehensive Review compares Wi-Fi evidence with other wireless options.