Coexistence - Bluetooth and WiFi sharing one antenna?

Started by PowerPC_Dev_Reed · 2026-11-14 03:37 UTC · 28 views · 4 replies
P Member
Sharing one antenna between BT and WiFi saves space but invites coexistence pain. How do you manage arbitration in practice?
L Admin
单天线共存,编辑部更认「仲裁时间线 + 接收保护」一起写,而不是只开一个开关优先级。常见拆法:

1) 仲裁: 明确 BT SCO/A2DP 与 Wi-Fi TXOP 谁先占天线、最长占用多久、以及切换空白期。很多「Wi-Fi 掉吞吐」其实是蓝牙语音窗把天线抢走,而不是射频匹配坏了。
2) 保护: 同口收发时看对方泄漏进 LNA 的功率与阻塞;必要时加时分空白、功率回退或滤波,而不是只拧共存算法参数。
3) 验收: 报共存开/关两套吞吐与重传,并写清语音/扫描占空比。对比「共享天线」与「双天线」更能说明仲裁是否够用。

欢迎贴芯片/前端方案、你们锁的仲裁表,以及一次蓝牙通话把 Wi-Fi 打崩的案例。有时序图更好。

— rfforum 编辑部 / Editorial Team
R Member
Sharing one antenna works, but only if you verify the switch and the arbitration on the bench rather than trusting the datasheet timing diagram. The failure I see most often is not the arbitration logic itself — it is the RF switch and the desense it causes.

First, measure the switch where it actually operates. Put the switch on a VNA and check insertion loss and isolation across both bands with the real control voltages applied, not just at the nominal state. Isolation from the Bluetooth transmit path into the Wi-Fi receive path matters most: if the Bluetooth transmitter leaks even -20 dBm into the Wi-Fi LNA while Wi-Fi is receiving, the Wi-Fi sensitivity collapses and no amount of arbitration tuning will fix it. A good acceptance test is Wi-Fi sensitivity measured with the Bluetooth transmitter running a continuous SCO link, compared against Bluetooth idle. If sensitivity degrades by more than a couple of dB, you have a leakage problem, not an arbitration problem.

Second, check the switch timing itself. Use a scope on the switch control lines alongside a spectrum analyser on the antenna port and confirm the switch actually moves within the blanking window the arbitration assumes. I have seen arbitration tables that assume a 2 microsecond switch time while the hardware took 10, so every handover clipped the start of the Wi-Fi packet. The fix was a longer guard interval in the arbitration table, not a new switch.

Third, check the antenna match in both switch states. The antenna sees a different load depending on which radio is connected, so measure return loss with each radio's matching network switched in. A shared antenna tuned for Wi-Fi can be several dB worse for Bluetooth, and the result looks like poor Bluetooth range when it is really a matching problem.

My practical order: measure switch isolation and loss, then desense with the other radio transmitting, then timing, then the arbitration table. If the first three pass and throughput still drops, only then tune the arbitration.
P Member
Agreed, this is the key point. We did the same and it worked well.
L Admin
@RF_Bench_Notes 共享天线的顺序很对:先量开关隔离/插损(真实控制电压)、再用 BT 连续 SCO 测 Wi-Fi 灵敏度相对 BT 空闲(降 >约 2 dB 先当泄漏)、示波器+频谱确认开关落在仲裁空白窗内、最后才改仲裁表;两态分别看天线回波,避免「Wi-Fi 调好、BT 其实失配」。编辑部验收三联:开关 IL/隔离、对端发射脱敏、控制沿 vs 空白窗时序。

欢迎补:你们实测开关切换要多久、以及脱敏门限最终定在几 dB。

— rfforum 编辑部 / Editorial Team
广告 AdRenesas 瑞萨微控制器芯片产品照片Renesas Electronics微控制器、模拟与射频/时钟方案 · MCUs, analog, RF and timing访问官网 →免费展示 · 资料来自公开信息 · 如需撤下请联系 ads@rfforum.com
广告 Ad广告位招商 / Advertise hereads@rfforum.com · 刊例 Rate cardT2 · 728×90
Log in or register to reply.