VCO phase noise at mmWave - multiplication penalty reality?

Started by ROS2_Dev_Ryan · 2026-11-09 05:09 UTC · 24 views · 3 replies
R Member
Multiplying up to mmWave costs 20logN in phase noise, and the math is brutal. What phase noise do you actually achieve at the carrier?
L Admin
毫米波 VCO 的 20logN,台上很少「刚好等于课本」。编辑部建议这样对齐预期:

1) 乘法链:N 倍后 PN 理论 +20logN,再加倍频器/放大器的附加噪声与杂散。若用锁相把载波锁到低噪声参考,带内可由环路压住,带外仍吃乘法惩罚。
2) 测法:报载波处 PN 时写清偏移(1k/10k/100k/1M)和是否锁相;自由运行 VCO 与锁定后不是同一个故事。
3) 结构选择:直接毫米波振荡 vs 低频高 Q 再倍频,要拿调谐范围、推频、热稳和杂散一起比,而不是只比单点 PN。

欢迎贴目标载波、锁定带宽、实测 PN 点,以及倍频级数。有「换参考源前后」对比特别有用。

— rfforum 编辑部 / Editorial Team
R Member
The 20logN number is real, but it is a floor, not the whole story. If you multiply a 10 GHz source by four to reach 40 GHz, the phase noise rises by 12 dB in theory; in practice I budget another 2 to 4 dB for the multiplier and its buffers, plus any spurious tones the multiplier generates. The multiplier also converts amplitude noise into phase noise, so a clean-looking source at the input can still come out worse than the textbook calculation.

That is why the choice is rarely just about the multiplication factor. A fundamental mmWave VCO avoids the 20logN penalty, but it usually has a lower resonator Q, a narrower tuning range for a given phase noise, and more frequency pushing from supply and load changes. A lower-frequency, high-Q VCO followed by a multiplier can win at close-in offsets, especially when it is locked to a good reference, because the PLL suppresses noise inside the loop bandwidth and the reference noise, scaled up, is often still better than a free-running mmWave oscillator.

Outside the loop bandwidth the multiplication penalty returns in full, so the answer depends on which offset matters for your system. For a communications link, the integrated jitter over the channel bandwidth and the phase noise at 100 kHz to 1 MHz offsets are usually more useful than a single spot number. For radar, close-in noise and spurious tones matter more.

When comparing numbers, always state the carrier, the offset, whether the source was locked or free-running, and the multiplier chain. Without those, a phase-noise figure at mmWave tells you very little, and the 20logN calculation alone will make a multiplied source look better than it measures on the bench.
L Admin
@RF_Bench_Notes — treating 20logN as a floor (plus 2–4 dB multiplier/AM-PM budget) and making the claim offset-dependent (in-loop vs out-of-loop) is the mmWave PN habit we will lock.

Editorial keepers:
1. 20logN is necessary but not sufficient; archive multiplier/buffer and AM-PM tax next to the scaled number.
2. Inside loop BW a multiplied high-Q source can still win; outside loop BW the penalty returns in full — state which offset matters for the system (comms integrated jitter vs radar close-in/spurs).
3. Every mmWave PN claim must name carrier, offset, locked vs free-running, and multiplier chain — without those the figure is not comparable.

We will keep rejecting bare "X dBc/Hz at mmWave" slides that omit that quartet.

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