VNA IF bandwidth vs noise floor: the filter rejection that only exists at a slow sweep

Started by LunaWei · 2026-11-14 01:52 UTC · 31 views · 1 replies
L Admin
[Technical article / FAQ, rfforum Editorial Team]

A 90 dB stopband that appears on a slow VNA sweep can vanish when the same filter is re-measured with a wider IF bandwidth or a faster point rate. The DUT did not change; the instrument noise floor and averaging did. Rejection claims that omit IFBW and averaging are not portable.

1. What the IFBW actually buys
- Narrower IF bandwidth lowers the noise floor roughly as 10 log(IFBW), at the cost of dwell time and sensitivity to source drift.
- A stopband that sits only a few dB above the noise floor is an instrument-limited number, not a filter number. Widening IFBW by 10x can erase 10 dB of "rejection" that was never there.
- Averaging and smoothing hide the same problem: they paint a clean floor over a noisy one without changing the DUT.

2. Freeze list before you ship a rejection spec
- IFBW, point count, sweep time, averaging, and whether the floor was verified with a known thru or a shielded open
- Whether the stopband stays ≥10 dB above the measured noise floor at that IFBW
- A repeat at 10x wider IFBW: if rejection collapses to the floor, the first number was instrument-limited
- Cable leakage and fixture radiation: a "rejection" that moves when you flex the cable is a radiation path, not a filter pole

3. Habit
Never freeze "≥90 dB rejection" from a single slow sweep. Archive IFBW, averaging, and a noise-floor screenshot next to every stopband claim. If a 10x wider IFBW kills the margin to the floor, stop quoting the slow-sweep number as the DUT.

4. Practical five-minute gate
- Note IFBW and averaging on the plot title or traveler
- Compare floor with a shielded load or thru at the same settings
- Re-sweep stopband at 10x IFBW; keep only what survives with ≥10 dB margin to the floor

Discussion: on your last stopband fight, did the fix land in IFBW, leakage, or a real filter redesign — and do you require IFBW on every rejection traveler?

— rfforum 编辑部 / Editorial Team
L Admin
Addendum — stopband traveler we will keep: IFBW, point count, sweep time, averaging, and a noise-floor check (shielded load or thru at the same settings) on the same sheet as any rejection claim. A 90 dB number taken only a few dB above the instrument floor is not a filter number.

A cheap gate: re-sweep the stopband at 10× IFBW. If the “rejection” collapses to the floor, stop quoting the slow-sweep figure as the DUT. A number that moves when you flex the cable is leakage, not a pole — write that on the traveler too, then fix the radiation path before a filter ECO.

Open: on your last stopband fight, did the fix land in IFBW, leakage, or a real redesign — and do you require IFBW on every rejection traveler?

— 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.