Gain structure, overload and HF options on budget SDRs: RTL-SDR vs SDRplay vs Airspy vs HackRF, and what the software changes
- Replies 2
- Views 26
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
I'd like to collect some practical notes on a question that comes up constantly: which SDR hardware and software combination makes sense once you move past the first weekend of plugging in a dongle? Most of the confusion seems to come from three things: ADC resolution versus real-world dynamic range, how HF gets into the receiver, and how much of what you see on the waterfall is the radio and how much is your own station noise.
On hardware, the RTL-SDR family (RTL2832U with an R820T2-type tuner) has an 8-bit ADC and is usable at roughly 2.4 MS/s without dropping samples. It is excellent value for VHF/UHF work such as ADS-B, airband, FM, NOAA/Meteor satellite reception, pagers and ISM-band telemetry. The weakness is instantaneous dynamic range. A strong FM broadcast station or a nearby paging transmitter can raise the noise floor or produce images and intermod products that look like real signals. HackRF One has wide frequency coverage (about 1 MHz to 6 GHz) and can transmit, but it is also an 8-bit design, so the same caution applies. It is a flexible lab tool rather than a sensitive receiver.
SDRplay RSP units and Airspy models are usually chosen when overload resistance and cleaner front-end filtering matter. The RSP line has selectable filtering and notches, which are useful against broadcast FM and AM in strong-signal areas. The Airspy HF+ type receivers are aimed at HF and low VHF, where large-signal handling matters more than raw bandwidth. LimeSDR is in a different category: wide tuning range and full-duplex transceiver capability, which suits experimenters building their own signal chains more than people who just want a bandscope.
For HF on an RTL-SDR there are two common routes. One is direct sampling mode, which is available on some dongles, such as those with a modified input path. It is simple, but the ADC sees everything with little filtering, so overload and aliasing are real problems. The other is an upconverter. It mixes HF up to a frequency the tuner can handle. A common arrangement uses a local oscillator around 100 to 125 MHz, so you tune the SDR to HF plus that offset. Many programs let you enter an offset so the displayed frequency stays correct. An upconverter is generally cleaner than direct sampling, but check for LO leakage, image response and spurs. Put a suitable low-pass or band-pass filter ahead of it.
On software, the practical differences matter more than the feature lists suggest. SDR# is popular on Windows and has a large plugin ecosystem. SDRuno is the natural choice for SDRplay hardware and has good tools for multiple receivers and spectrum display. HDSDR is old but still useful with ExtIO drivers and for traditional HF operating. GQRX is the usual option on Linux and macOS and is built on GNU Radio. CubicSDR is cross-platform and relies on SoapySDR, which helps when you have a mixed set of devices. For decoding, many digital modes are handled outside the SDR program. You route audio through a virtual cable or loopback device to tools such as WSJT-X, fldigi, multimon-ng or DSD-type decoders, or you use dedicated tools such as rtl_433, dump1090 or SatDump for specific signals.
My question for the group: what is your workflow for separating a genuinely strong-signal problem from an antenna or noise problem? And what would you recommend as the first thing to fix for someone who sees a messy, noisy waterfall: the antenna, filtering, USB cabling and power, or gain settings?
Link to comment
https://www.hamradiobase.com/forums/topic/11406-gain-structure-overload-and-hf-options-on-budget-sdrs-rtl-sdr-vs-sdrplay-vs-airspy-vs-hackrf-and-what-the-software-changes/Share on other sites