The BB60C Noise Floor Looks Raised and Weak Signals Vanished — Is the Instrument Broken? Check in This Order

The BB60C Noise Floor Looks Raised and Weak Signals Vanished — Is the Instrument Broken? Check in This Order

Symptom

Signals that used to sit comfortably above the baseline now disappear into noise. With a 50Ω dummy load on the input, the displayed noise floor sits well above the factory value or above historical screenshots — and the whole trace jitters violently.

Root Cause

Displayed Average Noise Level (DANL) is the instrument's own "breathing sound," and it is extremely sensitive to the settings you choose. Most "lost sensitivity" complaints are configuration or environment problems, not hardware failures — so run through the settings layer before suspecting damage.

Self-Check Sequence

1. Lock the attenuation step. In auto-ranging mode the instrument shifts internal attenuation and gain between steps; a trace taken at a different step looks like a different noise floor. Set RF attenuation manually (a common starting point is 0 dB step / preamp configuration appropriate to your signal) and compare against itself, not against a memory of last week's Auto settings.

2. Check RBW, not just the baseline. Narrowing resolution bandwidth lowers the displayed noise floor; widening it raises the floor. Compare screenshots only with identical RBW, detector and averaging settings.

3. Verify the detector and averaging mode. Peak, RMS and sample detectors render noise differently. Switching display modes alone can fake a 5–10 dB noise change.

4. Remove the environment variable. Disconnect everything, attach a known-good 50Ω terminator (not an open or unterminated cable — an unterminated input receives broadcast, cellular and switching-supply noise and will look like raised noise). If the jittery comb patterns disappear with the terminator, your problem was the cabling and environment, not the analyzer.

5. Reboot the whole chain. Power-cycle the instrument (unplug USB 30 s, reconnect) and restart Spike. A stuck digital state can hold the front end in a wrong configuration.

6. Compare against the published DANL curve in the datasheet with terminator attached, at defined attenuation/RBW. A trace sitting within a couple of dB of the curve across 9 kHz–6 GHz is healthy.

7. Localize genuine hardware degradation. If the noise floor is uniformly raised with correct settings and a good terminator, or raised only in a specific band, two suspects remain: front-end damage (overload or ESD — see those articles) or internal connection degradation. Note which band and record a baseline screenshot.

Escalation Point

A raised noise floor that survives steps 1–6 is hardware. There is no user-serviceable calibration to "reset" it; capture the DANL screenshots, the serial number, and the configuration used, and send the unit for evaluation. For critical work, schedule periodic instrument verification against a known reference rather than waiting for sensitivity complaints.

*(Based on publicly available Signal Hound BB60C user manual and datasheet specifications.)

WhatsApp：+85268839563

WeChat    ：13728300615