Cookie settings

Choose which cookies ATS Mini Controller may use. Necessary ones are always on, because the app cannot work without them. Analytics stays off until you switch it on.

Controller: WebUncle Grzegorz Zając, Katowice, Poland · contact@atsminiradio.com. Your rights and everything we store: Privacy policy (opens in a new tab)

Necessary

Run the app and keep it safe

Always on

Your language, theme and panel layout, your logbook and favourite stations, files for offline use, and Cloudflare’s protection against abuse. They don’t track you, so they need no consent.

Analytics

Help us improve the app

Count visits, show which features get used and where errors happen, so we know what to fix first. Google processes this data for us, and error details go to Cloudflare logs for 3 days. We build no advertising profile.

We remember your choice in this browser: a consent until you change it or clear your browser data, a refusal for 6 months, then we ask again. When you allow something, we also keep a record of that choice, without your IP address, as proof of consent. Withdrawing consent does not affect what was processed before.

Skip to content
ATS Mini Controller
Offline
RTL-SDRApp featureRTL-SDR: getting started3 min read

RTL-SDR troubleshooting: busy sticks, dropped samples and overload

Fix the common RTL-SDR problems in the browser: the stick does not show up or cannot be opened, the stream drops samples, signals overload, the stick disconnects, or an unknown tuner opens in basic mode.

Most RTL-SDR trouble falls into a few groups. The app’s messages name the group; here is what to do about each.

The stick is not in the browser’s list

  • Check the browser: Chrome, Edge or Opera on a computer, Chrome on Android. Safari and Firefox have no WebUSB and say so on the connect card.
  • Try another USB port and cable, without a hub. On Android, check the OTG adapter and try a powered hub.
  • The list only shows RTL2832U sticks with the usual USB IDs. A stick that reports something else will not appear.

“Windows is using its TV driver for this stick”

The browser can see the stick but cannot open it. Install WinUSB with Zadig as described in getting started, then plug the stick back in.

“The stick is busy”

Another program, or on Linux the dvb_usb_rtl28xxu kernel driver, has the stick open. Close rtl_tcp, GQRX, SDR++ or any other SDR program, or blacklist the kernel driver (the error offers to copy the command), then try again. Only one program can use the stick at a time, and that includes a second browser tab.

Dropped samples

If the stick or the USB link cannot keep up, the stream loses samples: audio stutters, the status strip shows how much is lost, and a message offers a lower sample rate. Run Device info and USB test to see which rates your stick and port really manage. Above 2.56 MS/s many sticks drop data; 1.8 to 2.4 MS/s is safe on most. A busy computer, a slow hub, a long passive extension or a USB isolator can all cause it. Note that USB isolators built on the common ADuM3160 chip are full-speed only and cannot carry the stream at all.

Overload

The Overload badge means the stick’s converter is clipping. Lower the gain, or set it to Auto. If one strong source keeps doing it, usually FM broadcast or a nearby transmitter, a band-stop filter for that band works better than less gain everywhere. Moving the antenna away from the source helps too.

The stick disconnected

A loose cable, a hub that runs out of power or a revoked permission stops the stream. The app shows when it happened and keeps your settings and bookmarks; a recording that was running is saved up to that moment. Plug the stick back in and press Reconnect: the app looks for the same stick and opens it in the same mode.

“RTL2832U found, tuner not recognised”

The stick answered but its tuner is not an R820T, R820T2 or R828D. Continue with basic mode gives you the spectrum and recording at a fixed gain, without tuning or gain control. Sticks with an E4000, FC0012, FC0013 or FC2580 tuner end up here. Copy details collects what the app saw if you want to report it.

Noise everywhere

A raised noise floor across the whole spectrum is usually local interference, not the stick. Put the stick on a USB extension, away from the computer and its power supply, try a ferrite on the USB lead, and move the antenna outdoors or at least away from screens and chargers. Turn on Remove DC spike under Source if a spike sits at the centre of the spectrum.

Recommended gear

More

Device

Explore

Settings

Theme

Welcome to ATS Mini Controller

This web app connects to your ATS Mini radio over USB or Bluetooth LE and lets you control it directly from a computer or phone. It adds remote tuning, memory slot management, screenshot capture, audio streaming, spectrum scanning, theme editing and other features on top of the device's built-in firmware.

Firmware 2.34+: pick a connection method

Starting with firmware 2.34 the radio accepts remote control over USB or Bluetooth LE. Pick by what matters more for you: fast screenshots (USB) or clean audio from the radio’s 3.5 mm output (Bluetooth) — the two transports trade off in opposite directions.

  • USB Serial

    Settings USB Port change Off to Ad hoc

    Works in any Chromium-based browser. Requires a data-capable USB-C cable (opens in a new tab).

    Best for screenshots and theme work. Transfers complete in a second or two. Audio capture is noisy while the cable is connected — the radio lacks the filtering needed to isolate its 3.5 mm output from the USB power rail, so hum and switching noise bleed into the audio path.

  • Bluetooth LE

    Settings Bluetooth set mode to Ad hoc

    Chrome / Edge / Opera on desktop or Android. BLE is experimental in firmware 2.34.

    Best for clean audio. Bluetooth LE carries the remote control only, never sound: the audio still travels by cable from the radio’s 3.5 mm output to your computer. With no USB cable attached the radio runs on its battery, so that output stays free of the USB power-rail noise that bleeds through on a wired connection. Screenshots are much slower (~30 s) because of the firmware's BLE throughput cap.

More than one firmware

Besides the official firmware, the app carries profiles for the Monster fork and for H. J. Berndt's firmware. It works out which one your radio runs from the replies it gets, so there is nothing to pick. When nothing matches, it says so instead of guessing.

  • Berndt firmware is never assumed. It reuses some of the official firmware's keys and what they do there is not established, so the app asks you before switching to it.
  • Missing controls are deliberate. Whatever a firmware cannot do is left off the page rather than greyed out, and on Berndt firmware, commands go out one at a time, a few seconds apart.
How the app handles other firmwares (opens in a new tab)

Keyboard shortcuts

Single keys control the radio on the Controller page, except while you type in a field.

←→
Tune one step
↑↓
Volume up / down
Enter
OK
BN
Next / previous band
MV
Next / previous mode
SA
Next / previous step
WQ
Next / previous bandwidth
GF
AGC up / down
LK
Backlight up / down
IU
Calibration up / down
OP
Sleep on / off
T
Toggle status log
C
Screenshot
H
Log reception
D
Cockpit view
⌘K
Search pages & stations