Skip to content
RFrftools.io
RF

ISM Band Wireless Coexistence Calculator

Analyze collision probability and throughput impact when WiFi, Bluetooth, Zigbee, or LoRa share ISM bands. Enter duty cycles and channels. Free, instant results.

Loading calculator...

Formula

Pcollision=DC1100×DC2100×FsharedP_{collision} = \frac{DC_1}{100} \times \frac{DC_2}{100} \times F_{shared}
DC₁, DC₂Duty cycles of each protocol (%)
F_sharedFraction of shared channel bandwidth

How It Works

ISM band coexistence analysis evaluates interference between unlicensed wireless systems sharing spectrum — IoT engineers, wireless network architects, and EMC specialists use collision probability models to design robust systems in crowded bands. The 2.4 GHz ISM band hosts WiFi (802.11b/g/n/ax), Bluetooth/BLE, Zigbee (802.15.4), Thread, and microwave ovens, each with different channel plans, modulations, and duty cycles per IEEE 802.15.2 coexistence guidelines.

Collision probability P_collision = DC_1 DC_2 F_overlap captures the fundamental tradeoff: duty cycle (DC) determines time-domain overlap, while frequency overlap (F_overlap) captures spectral intersection. WiFi with 40% duty cycle and Zigbee at 2% duty cycle on overlapping channels yields P_collision = 0.4 * 0.02 = 0.8% raw collision rate. However, power asymmetry enables capture effect: when signals differ by > 10 dB, the stronger signal dominates — WiFi at 20 dBm overwhelms Zigbee at 0 dBm by 20 dB.

ETSI EN 300 328 and FCC Part 15.247 regulate 2.4 GHz ISM operations: maximum 100 mW EIRP (20 dBm) for WiFi, 4 W (36 dBm) for point-to-point with directional antennas. Zigbee channels 15, 20, 25, and 26 (2.405-2.480 GHz) fall between WiFi channels 1, 6, and 11, minimizing but not eliminating overlap. Sub-GHz bands (868 MHz EU, 915 MHz US per ETSI EN 300 220 and FCC Part 15.247) offer 10-15 dB less path loss and far less congestion — preferred for range-critical IoT.

Worked Example

Problem: Analyze coexistence for a smart building with 50 WiFi access points (802.11ax) and 200 Zigbee sensors on the same floor.

System parameters:

  • WiFi: 20 dBm EIRP, 40% duty cycle (heavy usage), channels 1/6/11 (3 non-overlapping)
  • Zigbee: 0 dBm EIRP, 1% duty cycle (periodic reporting), 16 channels (11-26)
  • Floor area: 2000 m^2, average device spacing: 6 m
Collision analysis per IEEE 802.15.2:
  1. Frequency overlap: WiFi channel bandwidth = 22 MHz, Zigbee = 2 MHz
- WiFi Ch 1 (2401-2423) overlaps Zigbee Ch 11-15 - WiFi Ch 6 (2426-2448) overlaps Zigbee Ch 16-20 - WiFi Ch 11 (2451-2473) overlaps Zigbee Ch 21-25 - Zigbee Ch 26 (2480 MHz): minimal overlap with any WiFi channel

  1. Time-domain collision probability (worst case, same channel):
P_collision = 0.40 * 0.01 = 0.4% per transmission attempt
  1. Power asymmetry impact:
- WiFi 20 dBm vs Zigbee 0 dBm = 20 dB difference - At 6 m separation: path loss approximately 50 dB at 2.4 GHz - Received WiFi at Zigbee node: 20 - 50 = -30 dBm (if AP is 6 m away) - Zigbee receiver sensitivity: -100 dBm - Interference margin: -30 - (-100) = 70 dB above sensitivity — BLOCKED
  1. Zigbee packet error rate estimation:
- During WiFi transmission: PER approximately 50-80% (interference >> signal) - Effective PER with 40% WiFi duty cycle: 0.4 * 0.7 = 28% - With Zigbee retry (up to 3 attempts): successful delivery > 99%
  1. Mitigation recommendations:
a) Move Zigbee to channel 25 or 26 (outside WiFi Ch 11) b) Implement IEEE 802.15.4 CSMA-CA with extended backoff during WiFi presence c) Use PTA (Packet Traffic Arbitration) if gateway has both radios d) Consider Thread/OpenThread with channel hopping

Result: With channel 26 for Zigbee and proper CSMA, expected PER < 1%.

Practical Tips

  • Use Zigbee channels 25 and 26 (2.475-2.480 GHz) for best WiFi coexistence — outside the 2.401-2.473 GHz WiFi band edge even with spectral regrowth
  • Implement adaptive frequency hopping when available — BLE AFH monitors channel quality and avoids congested frequencies; Thread/OpenThread provides similar capability for 802.15.4
  • For industrial IoT with reliability requirements, migrate to sub-GHz (LoRa 915 MHz, Sigfox 868 MHz) — 15 dB less path loss than 2.4 GHz and minimal interference from WiFi

Common Mistakes

  • Assuming different channels means no interference — WiFi 22 MHz channels overlap Zigbee 2 MHz channels; WiFi channel 6 affects Zigbee channels 16-20 even when 'on different channels'
  • Ignoring near-far problem — a WiFi AP 3 m away produces -40 dBm at Zigbee receiver; a Zigbee coordinator 30 m away produces -70 dBm; the 30 dB power difference causes WiFi to dominate even off-channel
  • Not accounting for receiver blocking/desensitization — strong out-of-band signal saturates LNA, raising noise floor 10-20 dB for ALL signals including those on different channels
  • Treating duty cycle as constant — WiFi traffic is bursty; idle network may show 5% duty cycle but video streaming drives 60-80%; design for peak, not average

Frequently Asked Questions

Zigbee channels 15, 20, 25, and 26 fall in the gaps between WiFi channels 1, 6, and 11 (US/EU common deployment). Channel 26 (2480 MHz center) provides best isolation — completely outside WiFi channel 11 (2462 MHz center, 22 MHz wide). Channel 25 (2475 MHz) has slight overlap with WiFi channel 11 spectral tails but is generally safe. For maximum reliability, use channel 26 as primary and channel 25 as secondary. Avoid channels 11-14, 16-19, and 21-24 which fall within WiFi channel passbands.
Sub-GHz (915 MHz Americas, 868 MHz Europe) is preferred for industrial IoT per ETSI TR 103 526 coexistence analysis: (1) Path loss is 10-15 dB lower at 915 MHz versus 2.4 GHz — 3-4x range improvement for same power. (2) Far less congestion — no WiFi, Bluetooth, or microwave ovens in sub-GHz ISM. (3) Better penetration through walls and industrial equipment. (4) Regulatory duty cycle limits (1% in EU 868 MHz) prevent channel saturation. The only 2.4 GHz LoRa advantage is global spectrum availability without regional variants. For range-critical or interference-prone environments, sub-GHz wins decisively.
Bluetooth uses frequency hopping spread spectrum (FHSS) across 79 channels (2402-2480 MHz, 1 MHz spacing), changing channels 1600 times/second. Adaptive Frequency Hopping (AFH) in Bluetooth 1.2+ detects and avoids congested channels — typically excluding 20-30 channels overlapping active WiFi. WiFi uses direct-sequence spread spectrum (DSSS/OFDM) on fixed channels. Coexistence techniques: (1) AFH avoidance of WiFi channels. (2) Time-domain multiplexing via PTA (Packet Traffic Arbitration) in combo chips. (3) Spatial separation — different antennas with 20+ dB isolation. Modern combo chips (Qualcomm, Broadcom) achieve < 1% Bluetooth packet loss during WiFi activity through integrated coexistence protocols.
Capture effect allows a receiver to decode the stronger of two overlapping signals when their power difference exceeds a threshold (typically 3-10 dB for FM/FSK, 10-20 dB for OFDM). In coexistence scenarios: WiFi at -40 dBm versus Zigbee at -70 dBm (30 dB difference) — WiFi captures. This helps strong local signals overcome weak interferers but hurts weak desired signals. For Zigbee sensors: transmissions close to the coordinator succeed despite WiFi; distant sensors struggle. Design implication: keep Zigbee coordinator near sensors, use mesh networking to reduce hop distance, increase transmit power where regulations allow.

Shop Components

As an Amazon Associate we earn from qualifying purchases.

SMA Connectors

Standard SMA RF connectors for board-to-cable connections

RF Coaxial Cables

Coaxial cable assemblies for RF signal routing

TinySA Spectrum Analyzer

Compact handheld spectrum analyzer for RF measurement up to 960 MHz

Related Calculators