Dongguan Chenyi Electronics Co., Ltd.
Dongguan Chenyi Electronics Co., Ltd.
Gold Verified Supplier
1Yr
Verified Business License Business License
Main Products: Real-time spectrum analyzer & monitoring receiver, Vector Signal Generator, Scalar network analyzer, RF recorder
Home > Blog > The Signal Hound BB60D's IQ Stream Bandwidth Goes All the Way Down to 4 kHz, Far Below the BB60C's 250 kHz

Contact Us

Ms. JIANG
Chat Now

Your inquiry content must be between 10 to 5000 characters

Please enter Your valid email address

Please enter a correct verification code.

The Signal Hound BB60D's IQ Stream Bandwidth Goes All the Way Down to 4 kHz, Far Below the BB60C's 250 kHz

Signal Hound BB60D real-time spectrum analyzer supplier


The Signal Hound BB60D's IQ Stream Bandwidth Goes All the Way Down to 4 kHz, Far Below the BB60C's 250 kHz — Correct Use of Narrowband Capture and Phase-Noise Measurement


Symptom

① A user migrating from a BB60C to a BB60D reuses the old program / IQ recording configuration unchanged. They want to measure radio sub-audible tones, narrowband power-line communication signals, or observe close-in phase noise, and when they set the IQ sample rate to 10 kHz / 20 kHz the legacy code errors out or the data read back is "a screenful of garbage." ② Some users do not know the BB60D supports ultra-slow IQ down to the 4 kHz class and still capture at 27 MHz wide bandwidth, then "digitally downconvert and decimate in software," wasting disk space and compute for nothing. ③ Measuring phase noise with narrowband IQ, the low-offset data does not agree with the spectrum-analyzer trace.

Root-Cause Analysis

Published specification comparison: the BB60C's IQ acquisition bandwidth is 250 kHz–27 MHz; the BB60D's is 4 kHz–27 MHz (per official distributor spec wording; defer to the manual shipped with the unit). Pulling that floor down to 4 kHz is precisely one of the BB60D's less-advertised upgrades over the C model, and combined with the LO phase-noise improvement it enables direct close-in phase-noise observation at very narrow IQ bandwidth, plus long-duration recording of low-rate data streams. Common misuses:

  1. Out-of-range parameters inherited from old code: legacy code hard-codes the BB60C's minimum legal sample rate (250 kHz), so on the BB60D the problem reverses — requesting anything below 250 kHz is rejected by the old enumeration table. Some in-house programs add custom validation such as "sample rate must be a power of two," which kills off the new 4 kHz–250 kHz range entirely.

  2. Wrong display scaling on narrowband capture: at a 4 kHz IQ bandwidth the per-bin frequency-axis resolution differs from spectrum mode, yet the program still computes the scale using wideband assumptions, so every spectral line lands in the wrong place.

  3. Confusing two different phase-noise conventions: the phase-noise spectral density derived from IQ data (computed in the time domain) versus Spike's spectrum-analyzer reading in dBc/Hz involves RBW / window function / sample-rate normalisation — mismatched conventions guarantee that the numbers "do not agree."

  4. DC and flicker regions at low rates: extremely low offsets (<10 Hz to a few hundred Hz) are dominated by record length and 1/f statistics; short records cannot produce credible low-frequency data, which gets misread as "poor close-in phase noise on the device."

Correct Usage

  1. Unit-test the new range first: capture 60 s of IQ at each of 4 k / 10 k / 50 k / 100 k / 250 kHz, checking sample-count rate, spectral scaling, and phase continuity. If all pass, hardware and driver are healthy and the problem is back in your own code's parameter validation.

  2. Code-modification checklist: replace the hard-coded legal sample-rate table with a capability query against the device (enumerate capability parameters via the API) and delete the fixed lower limit; confirm bit width / interleaving format matches the C model before reusing existing parsers.

  3. Validate phase-noise work with two parallel methods: solve phase noise over the 100 Hz–5 kHz offset region from narrowband IQ (e.g. 20 kHz) and compare against Spike's built-in phase-noise measurement on the same carrier and same DUT — a deviation ≤2–3 dB means the chain is trustworthy (for the closest-in offsets, still follow the instrument manual's method).

  4. Save space on long low-rate recordings: when monitoring narrowband signals or slowly changing spectra, use the low-rate IQ stream directly (disk write volume drops by two orders of magnitude) instead of "capture wide, then decimate."

  5. Budget record length for low offsets: to look at offsets <100 Hz, single record lengths need to reach tens of seconds to minutes; configure "long record + low rate" and ensure the clock source is disciplined (an external 10 MHz reference is better), otherwise the low-frequency region's statistics are distorted.

Acceptance Criteria

Spot verification passes across the entire 4 kHz–27 MHz range; the in-house program switches to capability querying so one code base serves both old and new devices; for the low-offset phase-noise region the deliverable includes a "record length / statistical confidence" note rather than a bare curve.

(Based on Signal Hound BB60D published specifications (IQ bandwidth 4 kHz–27 MHz) compared with the BB60C (250 kHz–27 MHz); defer to the datasheet shipped with the unit.)



BB60D (20)BB60D (19)BB60D (18)BB60D (17)BB60D (16)

Share

Contact Us

Send Inquiry to Us
* Message
0/5000

Want the best price? Post an RFQ now!

Recommended Products