Multi-Wireless Module (WiFi/BT/4G) Resource Competition & Anti-Interference Deployment
I. Industry Pain Points: The "Full Signal Lag" Paradox

In industrial IoT, devices like the E90-DTU or P31 Gateway often use "Multi-mode Redundancy" (WiFi + BT + 4G) to ensure "never-offline" connectivity. However, simply stacking modules leads to a hidden bottleneck where signals are strong but data won't flow.

Core Challenges

  1. Ghost Lag: RSSI shows -50dBm (Full Signal), but ping latency spikes from 20ms to 500ms+ with packet loss $\ge 5\%$.

  2. Performance Regression: A standalone WiFi module hits 11Mbps; adding Bluetooth and 4G drops total throughput to $< 3Mbps$—a 70% performance loss.

  3. Battery Drainage: Multi-module contention spikes standby currents on low-power nodes like the PN1 or E22 from $10\mu A$ to $1mA+$, cutting battery life from 1 year to 1 month.

II. Technical Analysis: The Root of Competition

The resource struggle occurs across four distinct layers:

1. Spectrum & RF Interference

  • Co-Channel Interference (CCI): WiFi and Bluetooth both operate on the 2.4GHz ISM band. A 20dBm WiFi transmission can raise the Bluetooth noise floor by 30dB, "blinding" the receiver.

  • Desensitization (Desense): High-power 4G transmissions (peak currents up to 2A) create near-field coupling that saturates the WiFi receiver, causing high packet loss even at full signal.

2. Hardware & Bus Contention

On compact devices like the P31 or E90-DTU, modules often share the same SPI/USB bus or power rails.

  • Bus Congestion: Simultaneous data bursts cause DMA conflicts, increasing serial data latency from 10ms to 50ms+.

  • Power Ripples: Peak current draws cause voltage dips, leading to digital bit errors and analog PLL unlocks.

3. Protocol & Timing Conflicts

WiFi (CSMA/CA), Bluetooth (AFH/TDM), and 4G (Scheduled) have no unified coordinator. Without an Arbitration Mechanism, they suffer from "Air Collisions," where multiple radios transmit at the exact same microsecond.

III. Measured Performance Comparison Table

Environment: Industrial workshop with heavy EMI, RSSI = -60dBm. Tested on E90-DTU, E22, P31, and PN1.

Scenario Throughput (UDP) Avg. Latency Packet Loss System Power (Standby/TX)
Single WiFi 2.4G (E22) 11.2 Mbps 18 ms 0.1% 60 mW / 800 mW
WiFi + BT (No Optimization) 3.5 Mbps 160 ms 5.8% 180 mW / 1400 mW
WiFi + BT + 4G (Stacked) 1.8 Mbps 420 ms 12.3% 320 mW / 2100 mW
WiFi + BT + 4G (Optimized) 9.1 Mbps 24 ms 0.3% 90 mW / 1100 mW
Degradation (Standard) ↓ 77% ↑ 833% ↑ 1220% ↑ 162% (TX Power)

IV. Engineering Solutions & Deployment Strategies

Solution 1: Industrial Multi-mode Gateway (P31 / E90-DTU)

For high-density workshops, use a Four-Layer Coordination strategy:

  1. Spectrum Shifting: Move WiFi to the 5GHz band to vacate the 2.4GHz space for Bluetooth. Lock 4G to the 900MHz (B8) band to minimize near-band leakage.

  2. Physical Isolation: Maintain antenna spacing $\ge 20cm$. Install SAW filters on the LNA front-end to suppress out-of-band interference.

  3. TDM Scheduling: Use a built-in Coexistence Arbiter to ensure only one radio transmits at a specific time-slot, preventing air collisions.

  4. Priority Routing: Assign PLC control commands to the high-priority 4G link, while offloading non-real-time sensor data to WiFi/BT.

Solution 2: Low-Power Node Optimization (PN1 / E22)

For outdoor or battery-powered monitoring:

  • On-Demand Wake-up: Keep 4G as the primary heartbeat link. Keep WiFi/BT off by default, triggering them only for local data exports or debugging.

  • Staggered Heartbeats: Offset heartbeat intervals (e.g., 4G every 30s, WiFi every 60s) to prevent simultaneous current peaks and radio collisions.

V. Best Practices: The Expert "Avoid-Pitfall" Guide

1. Hardware Selection: SoC vs. Stacked

  • Do: Choose modules with integrated "Coexistence Engines" (like the E22 or P31). These feature internal logic to sync time-slots between WiFi and BT.

  • Don't: Use separate, cheap modules pieced together on a single PCB without RF isolation shields ($\ge 25dB$).

2. Antenna Layout

  • External: Keep 4G and WiFi antennas at least 20cm apart.

  • Internal (PCB): Maintain a 5cm gap between traces. Use a grounded copper pour to isolate RF signal paths.

  • Orientation: Use directional antennas for 4G (pointing to the base station) and omni-directional for local WiFi/BT coverage.

3. Software Configuration

  • Dynamic Power Control: If RSSI is $>-70dBm$, reduce TX power by 6-12dB. This drastically reduces self-interference and saves power.

  • Retry Limits: Limit retransmissions to $\le 3$ times. Beyond this, trigger a rate-drop or link-switch to prevent a "Retry Avalanche" that chokes the CPU.

VI. FAQ: Direct Answers for Engineers

Q: Why does the device disconnect more often near VFDs/Motors?

A: Variable Frequency Drives (VFDs) generate significant broadband noise. This noise lowers the SINR (Signal-to-Interference-plus-Noise Ratio). Even if your signal is "Full," the interference makes the data unreadable. High-quality modules like the E90-DTU with SAW filters are required here.

Q: Can I use one antenna for WiFi and Bluetooth?

A: Yes, but only with a high-speed RF Switch and a coordination protocol. Switching latency must be $< 1ms$ to avoid real-time packet loss. For industrial reliability, dual antennas are always preferred.

Q: Why did my battery life drop from 1 year to 1 month?

A: Most likely due to "Resource Contention." If WiFi and 4G interfere, the modules stay in high-power "Retry Mode" longer. On the PN1, ensure the 4G DRX (Discontinuous Reception) is configured to offset WiFi wake-up cycles.