Dynamic range vs. noise floor on budget SDRs: gain staging, upconverters and antenna choices for HF through VHF
- Replies 2
- Views 36
- Created
- Last Reply
Top Posters In This Topic
-
Mod_Tom 1 post
-
Mod_Chrissy 1 post
A lot of SDR troubleshooting threads come down to the same confusion: people blame the dongle's sensitivity when the real problem is dynamic range, or the reverse. This thread is meant to separate the two and compare how the common hardware and software tools handle them.
Sensitivity and dynamic range are different problems. Sensitivity is how weak a signal you can pull out of the noise. Dynamic range is the span between the weakest signal you can see and the strongest one the front end can handle before it distorts. A strong FM broadcast or pager signal can overload the tuner or ADC and produce images and intermod products across the spectrum, including on frequencies where nothing is transmitting. Turning the gain up on an overloaded front end makes the display look busier, not better.
The hardware in rough terms. The RTL-SDR family uses an 8-bit ADC with a tuner chip such as the R820T2. It is cheap and good for VHF/UHF monitoring, ADS-B, and similar jobs, but its dynamic range is limited. Stable sample rates are typically around 2.4 MS/s. The V3-style dongles add a direct sampling mode for HF, which is basic and usually works best with filtering and a sensible antenna. The HackRF is also 8-bit, but it covers a very wide tuning range, can transmit (half duplex), and is flexible for experimenting. It is not usually the first choice for weak-signal HF listening. The SDRplay RSP line uses a higher-resolution ADC, has built-in filtering and notches on several models, and is mainly used with SDRuno, though it also works with other software through the API. Airspy products use higher-resolution ADCs and are generally aimed at better linearity and wider bandwidth. The LimeSDR is a transceiver aimed more at experimentation and wideband work than at a plug-and-play receiver. Check each model's current specifications, because tuning range, bandwidth, and ADC bits differ between revisions.
Gain staging. A practical method that works on most receivers: disconnect the antenna or terminate the input, note the noise floor, then connect the antenna and raise gain only until the noise floor rises by a few dB. If a further gain increase raises the noise floor and the strong signals together, you are probably just amplifying into overload. Watch for ADC overload indicators where the software provides them, and try turning AGC off and setting gain manually for decoding. Narrowing the displayed or processed bandwidth also helps. Decimating from a wide sample rate gives some processing gain, but it does not fix overload that happens before the ADC.
Upconverters and HF. Many tuner-based dongles do not tune below the VHF range in normal mode, so options for HF are direct sampling or an upconverter. An upconverter mixes HF up by a fixed offset, such as 100 or 125 MHz, so the dongle can tune it. In the software you either set a frequency offset or use a plugin or setting for the converter's local oscillator. If the tuned frequency is off by exactly the oscillator value, the offset is probably missing or has the wrong sign. Oscillator accuracy matters too: a few ppm error at a 100 MHz LO shifts the display by hundreds of hertz, which matters for narrow digital modes.
Antennas and noise. Antenna choice often matters more than the dongle. A discone or similar wideband antenna is convenient for scanning, but it also brings in every strong local signal. Band-specific filters, such as an FM broadcast notch or a bandpass filter, often improve the display more than extra gain. For HF, local noise from switching supplies, LED lighting, chargers, and the computer itself can set the noise floor well above what the receiver generates. Common-mode chokes on the coax, ferrites on USB cables, moving the dongle away from the PC on a USB extension, and powering it from a clean source can all help. Active loops and short active whips are popular for compact HF reception, but they can overload in the presence of strong signals, so a bit of attenuation may help.
Software. SDR# is a common Windows choice with a large plugin ecosystem. SDRuno is tied to SDRplay hardware and has detailed controls for it. HDSDR is a long-standing Windows program that works through ExtIO drivers and is often used with upconverter setups and CAT-linked radios. GQRX runs on Linux and macOS and relies on the SoapySDR or osmosdr layer for many devices. CubicSDR is cross-platform and also uses SoapySDR. For decoding, audio is often routed via virtual cables or pipes into programs such as WSJT-X or fldigi, while others read the IQ or demodulated stream directly, such as rtl_433, dump1090-style ADS-B decoders, and multimon-ng for pager-type data.
Panadapters and bandscopes. Besides standalone reception, an SDR can serve as a panadapter by tapping the IF output of a transceiver, or the RF through a suitable splitter or sampler, to show band activity around the rig's frequency. This requires protecting the SDR input from transmit power and keeping the tuning offset aligned. Some current transceivers have built-in bandscopes, but an external SDR still helps with wider views, recording, and software integration.
Questions to get discussion going: what front-end filtering do people consider essential for broadband SDR listening, and how do you check whether a spur or image is real or generated by overload?
Link to comment
https://www.hamradiobase.com/forums/topic/10999-dynamic-range-vs-noise-floor-on-budget-sdrs-gain-staging-upconverters-and-antenna-choices-for-hf-through-vhf/Share on other sites