R
Member
Not every lab has a dedicated phase noise test set, but a decent spectrum analyzer can still get you useful close-in spur measurements — if you know where it lies to you.
The analyzer's own local oscillator phase noise is the first limit. Close to the carrier, what you see is mostly the analyzer's LO, not the DUT. A quick sanity check: switch the analyzer to a different RBW and see if the close-in skirt changes. If the skirt shape follows the RBW, you are measuring the analyzer, not the device. The fix is to use the narrowest RBW that still gives a stable trace, and to average heavily — 50 to 100 averages is a reasonable starting point for close-in work.
Second, the detector matters. Sample detection with averaging is what you want for noise-like spurs; peak detection will inflate the noise floor and hide the real spur level. I also turn off any auto-attenuation and set the attenuator manually: too much attenuation raises the displayed noise floor, too little risks overloading the front end. Watch the mixer level, not just the reference level.
Third, external reference. If your analyzer accepts an external 10 MHz reference, feed it from a clean source. The analyzer's internal reference is often the dominant close-in noise contributor, and a good external OCXO can buy you 5 to 10 dB of margin at 1 kHz offset.
Practical flow I use: 1. Warm up the analyzer for at least 30 minutes; LO drift during warm-up masquerades as close-in spurs. 2. Measure the analyzer's own noise floor with the input terminated, at the same settings, and subtract it mentally from the DUT result. 3. Use a marker with noise-marker mode for spur levels, and always quote the offset frequency and RBW alongside the number — a spur level without offset and RBW is meaningless.
The results won't match a dedicated phase noise analyzer, but for go/no-go checks and comparing two DUTs side by side, this approach is good enough and saves a board spin.
What tricks do you use to push a spectrum analyzer below its own phase noise floor?
The analyzer's own local oscillator phase noise is the first limit. Close to the carrier, what you see is mostly the analyzer's LO, not the DUT. A quick sanity check: switch the analyzer to a different RBW and see if the close-in skirt changes. If the skirt shape follows the RBW, you are measuring the analyzer, not the device. The fix is to use the narrowest RBW that still gives a stable trace, and to average heavily — 50 to 100 averages is a reasonable starting point for close-in work.
Second, the detector matters. Sample detection with averaging is what you want for noise-like spurs; peak detection will inflate the noise floor and hide the real spur level. I also turn off any auto-attenuation and set the attenuator manually: too much attenuation raises the displayed noise floor, too little risks overloading the front end. Watch the mixer level, not just the reference level.
Third, external reference. If your analyzer accepts an external 10 MHz reference, feed it from a clean source. The analyzer's internal reference is often the dominant close-in noise contributor, and a good external OCXO can buy you 5 to 10 dB of margin at 1 kHz offset.
Practical flow I use: 1. Warm up the analyzer for at least 30 minutes; LO drift during warm-up masquerades as close-in spurs. 2. Measure the analyzer's own noise floor with the input terminated, at the same settings, and subtract it mentally from the DUT result. 3. Use a marker with noise-marker mode for spur levels, and always quote the offset frequency and RBW alongside the number — a spur level without offset and RBW is meaningless.
The results won't match a dedicated phase noise analyzer, but for go/no-go checks and comparing two DUTs side by side, this approach is good enough and saves a board spin.
What tricks do you use to push a spectrum analyzer below its own phase noise floor?
