Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

Gain, dynamic range and antennas: why does the same SDR look fine on one band and overloaded on another?

ci_cover.jpg

This is a technical discussion starter for anyone using an RTL-SDR, HackRF, SDRplay, Airspy or LimeSDR. A common pattern: an SDR looks clean on 2 m or the airband, then the FM broadcast band, a local pager transmitter or a nearby ham station produces ghost signals, a lifted noise floor or "birdies" that move when you change gain. The waterfall looks busy, but not all of it is real.

The first thing to separate is the noise floor you see from the noise floor you have. The ADC resolution matters (an RTL-SDR uses an 8-bit converter, the HackRF One also 8 bits, while SDRplay, Airspy R2 and LimeSDR use 12-bit class converters), but so does where the gain sits. A wideband front end sees everything inside its tuner range, not just the slice you are displaying. A strong FM broadcast signal can overload the tuner or ADC even if you are watching 145 MHz at 2 MHz bandwidth.

The second thing is that the display lies a little. The FFT size and resolution bandwidth change the apparent noise floor, since narrower bins show a lower floor per bin. Comparing SDR# at one FFT setting with SDRuno or GQRX at another is not a fair test of receiver sensitivity unless you account for bin width.

A few questions to get the discussion going:

1. How do you set gain in practice? Maximum gain, AGC, or a manual method based on the band and antenna?

2. When do you reach for a notch or bandpass filter (FM bandstop, airband filter, 1090 MHz filter, HF low-pass) instead of changing receivers?

3. For HF, do you prefer direct sampling, an upconverter, or a dedicated HF receiver such as an Airspy HF+ type? How does that interact with your antenna and local noise?

4. If you use an SDR as a panadapter or bandscope next to a transceiver, how do you protect the SDR input and keep CAT/frequency tracking reliable?

  • Replies 2
  • Views 39
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

For gain, the most reliable method is the same on any SDR: start low and raise gain until the noise floor in your passband rises by a few dB, then stop. Past that point you are mostly amplifying noise and stronger signals, and eating headroom. On an RTL-SDR with an R820T2-type tuner, maximum gain is rarely the best setting in a city. Something in the middle often gives a better picture, especially if you have a strong signal outside your band of interest.

A quick overload check is to insert an attenuator or drop the gain by 6 to 10 dB and watch the suspect signals. A real signal drops roughly in step with the attenuation, and the noise floor changes little once you are above the receiver's own noise. Intermodulation products and images usually fall much faster than the real signal, because third-order products change about 3 dB for every 1 dB of input change. If a ghost signal disappears or shifts when you add a bandstop filter on the broadcast FM band, you have found your cause.

On SDRplay, the gain control is split into RF gain reduction and IF gain reduction, and the broadcast notch options are handy for MW, FM and DAB. In SDRuno you can watch both the spectrum and the overload indicator while adjusting. Airspy hardware and SDR# work similarly, with different gain modes (linearity, sensitivity) that are really preset compromises between noise figure and intercept point. HackRF has separate RX amp, LNA and VGA stages. The usual advice is to leave the RX amp off unless you need it, because that extra 14 dB is easy to overload with.

One caveat on the 8-bit devices: they are excellent value for exploration, decoding and monitoring, but their dynamic range is limited, so a good filter often does more than a better antenna. A wideband antenna plus a sensitive LNA at the receiver is exactly what makes overload worse.

  • Moderators

On HF, the antenna and the noise environment usually decide the outcome more than the SDR's noise figure. Below roughly 20 to 30 MHz, external noise (atmospheric, and especially man-made noise from switch-mode supplies, LED lighting and powerline hardware) often sits well above the receiver's own noise. A very sensitive front end does not help you hear a weak signal if the antenna is picking up household noise. What matters is signal-to-noise ratio, plus enough dynamic range that strong broadcasters do not generate spurs.

For an RTL-SDR, the options are direct sampling or an upconverter. Direct sampling on dongles that support it (the RTL-SDR Blog V3 uses the Q branch) is simple and cheap, but there is no proper preselection, so you get aliasing and the 8-bit converter must handle everything from LF through the shortwave broadcast bands. An upconverter mixes HF up to VHF. With a 125 MHz local oscillator, a 7.1 MHz signal appears at 132.1 MHz, and in SDR# or HDSDR you set a frequency offset (shift) so the displayed frequency matches the real one. Look for a low-pass filter ahead of the mixer, a stable oscillator, and good shielding. Cheap converters can add their own spurs and drift.

If HF is your main interest, an Airspy HF+ type or an SDRplay RSP with its HF input is designed for the job, with better filtering and a lower chance of strong stations folding into your band. SDR software choices follow the platform: SDR# and HDSDR are common on Windows, SDRuno pairs naturally with SDRplay, and GQRX is a good Linux or macOS option through the osmosdr or Soapy driver layers. CubicSDR is useful when you want a Soapy-based cross-platform viewer that can work with several devices.

For panadapter use, feed the SDR from a splitter or from a dedicated receive output or IF tap, never directly from the transmit path. Use a proper TX protection scheme such as a relay or attenuator chain, and make sure there is no DC on the coax from a bias tee into your transceiver. For frequency tracking, CAT control with OmniRig, hamlib or the vendor's own interface lets the SDR follow the radio, which is more reliable than eyeballing the spectrum. Finally, for portable setups, a common-mode choke on the feedline and a few metres of distance from the computer and power supplies can reduce noise more than any software setting.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.