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 > BB60C Code Errors Out on a Signal Hound BB60D, or the "Preselector Switch" Is Nowhere to Be Found supplier

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.

BB60C Code Errors Out on a Signal Hound BB60D, or the "Preselector Switch" Is Nowhere to Be Found supplier


Signal Hound BB60D real-time spectrum analyzer supplier


BB60C Code Errors Out on a Signal Hound BB60D, or the "Preselector Switch" Is Nowhere to Be Found — Capability Matrix Differences Between Sibling Devices


Symptom

A lab has both a BB60C and a BB60D, and one in-house acquisition/monitoring program is meant to serve both: ① running on the D, setting the IQ sample rate to 10 kHz returns "invalid parameter"; ② calling the preselector configuration function on the C reports an unknown option; ③ Spike works fine manually on both units, yet the API keeps tripping over each other; ④ someone uninstalled the C's driver and reinstalled a supposed "D-only driver" (confusion while searching and downloading), after which the BB60C stopped enumerating altogether.

Root-Cause Analysis

The BB60C and BB60D share the Spike software and USB driver stack (the official download page offers a single unified "BB60D/C/A driver"), but the API capability surface is two different matrices:

  1. Capabilities added on the D do not exist on the C: preselector enable/state related options, and the IQ bandwidth floor (the D goes down to 4 kHz, the C starts at 250 kHz). Calling a preselector function on the C naturally yields "no such option."

  2. Everything legal on the C is accepted by the D, but the reverse does not hold: passing the D's extended parameter domain (ultra-slow IQ) into legacy validation code gets rejected by your own program.

  3. There is actually only one driver package: what the official site provides is a unified Spike installer plus driver covering BB60D/C/A. The widely circulated tutorials about "installing a separate driver for the D" are mostly misleading, and reinstall churn ends up breaking the C's environment instead.

  4. Capability detection by guessing the model: programs that enable preselector features only when the device name contains "BB60D" break as soon as new firmware renames things or serial-number prefixes change — query the capability parameters instead of guessing the model.

Correct Approach

  1. Query capabilities per device, then configure: after opening a handle, read the model / capability fields returned by the device (legal IQ sample-rate range, whether preselector options are supported) and decide what to send at run time — one code base then adapts automatically to both models.

  2. Externalise the parameter validation table: express "legal sample rate / bandwidth / preselector combinations" as a loadable configuration table, so adding a new model means editing the table rather than the code.

  3. Unify driver and software: use only the current official combined Spike/driver package. When both models coexist, first enumerate the device list to confirm the target handle (with several units, open explicitly by serial number).

  4. Run regression on both machines: before each release, execute the full feature checklist on both the C and the D, paying particular attention to IQ extremes and the preselector on/off branches.

  5. Triage errors properly: "invalid parameter" → check the parameter domain (capability matrix) first; "device busy / not enumerated" → check occupancy and drivers first. These are different failure paths, so don't respond by reinstalling the whole system for both.

Acceptance Criteria

One program auto-adapts to all functions across both C and D units (capability-query logs archived); the C never receives a preselector command, and the D can acquire at 4 kHz-class sample rates; with several units mixed together, addressing by serial number never opens the wrong device.

(Based on published specification differences between Signal Hound BB60D and BB60C (IQ bandwidth floor, preselector) and the official unified download page (one driver/software package for BB60D/C/A); API field names defer to the official SDK documentation.)



BB60D (21)BB60D (20)BB60D (19)BB60D (18)BB60D (17)

Share

Contact Us

Send Inquiry to Us
* Message
0/5000

Want the best price? Post an RFQ now!

Recommended Products