RTLSDR Scanner



Manual (EN) (FR)

Frequently Asked Questions

Screenshot 1

Screenshot 2

Screenshot 3

Screenshot 4

Screenshot 5

Screenshot 6

A cross platform Python frequency scanning GUI for USB TV dongles, using the OsmoSDR rtl-sdr library.

In other words a cheap, simple Spectrum Analyser.

The scanner attempts to overcome the tuner's frequency response by averaging scans from both the positive and negative frequency offsets of the baseband data.

Tested on:

  • Windows 7 (x86 and x64)
  • Ubuntu 12.04 (x86), 12.10 (x64), 13.04 (x64) and 14.04 (x64)
  • OS X Snow Leopard (10.6) and Mountain Lion (10.8)


Download the installer or stand-alone Windows executables from GitHub.

Download the latest source from GitHub.


Installation instructions are here.

The following dependencies are needed:

Linux and Mac users will need to manually install these,  Windows users can use the installer.


A basic manual is available in Portable Document Format.

Quick start

Run 'python -m rtlsdr_scanner'.

To start a scan simple enter the range at the bottom of the window and click 'Start', after a while a plot of signal strengths should be displayed.

'Dwell' controls how long each step is sampled for, longer times will result in more averaging of the signal.

'Continuous update' updates the display on each step. Caution only use this with small scans and low dwell times, otherwise it will become unresponsive.

'Grid' displays a grid on the scan plot.

Auto Calibration

Scans around the frequency specified for the strongest signal and then calculates the error correction of the dongle.

To get the best out of it you really need a continuous signal peak that stands out from the background noise.  If you live near an airport RADAR signals are great for this. Mobile phone signals also work well but you need to know the channel frequencies, making it tricky.  I have had some luck with commercial FM radio but you'll have to set the dwell time to the highest setting to get a usable offset.

Main Window

  • Start - Scan start frequency
  • Stop - Scan stop frequency
  • Mode - Sing or continuous scanning
  • Dwell - Sampling time spent on each step
  • FFT Size - FFT size, greater values result in higher analysis precision (with higher sizes dwell should be increased)
  • Live update - Update the display on each step (caution this can be slow and unpredictable)
  • Grid - Show a grid on the scan
  • Display - Change the plot type

File Menu

  • Open... - Open a saved scan
  • Save As... - Save a scan
  • Export... - Export a scan to a CSV file
  • Properties ... - Scan information

Edit Menu

  • Preferences - Set dongle gain, calibration, Local Oscillator (positive offset for upconverters) and sample bands (see below)

Scan Menu

  • Start - Start a scan
  • Stop - Stop the scan
  • Stop at end - Stop the scan when the current sweep is finished (only in continuous mode)

Tools Menu

  • Compare - Compare two previously saved scans
  • Auto Calibration - Perform a crude calibration of the dongle to a known signal (this should be a continuous, unwavering signal)


Dongles will differ depending on the tuner and circuit that's used, the software allows you to pick the best range that is sampled to give improved results.

Click on View -> Preferences and select the 'Band Offset' for you tuner, next detach the aerial or even better terminate it with a 50 ohm load.  Now click refresh to show the noise floor of the tuner, adjust the offset so the marked bands overlay the flattest areas of the plot and click OK.

I find the following offsets work well (click the offsets for images):

Tuner Offset (kHz)
Elonics E4000 250
Fitipower FC0012 140
Rafael Micro R820T 100

Note the large peak in the middle, this is at 0Hz (i.e. its the DC offset).  On the R820T it is much narrower, this is because it uses an intermediate frequency away from the low frequencies.  In this case the resulting spike is due to the sample length not being infinitely long (imagine taking a complete cycle of a sine wave then chopping the end off, this leaves it unbalanced and its average value is no longer 0, in other words it looks like it has a DC offset), the sample is windowed to reduce this but it's a trade-off between accuracy and frequency response.


Run 'rtlsdr_scan_diag.py', this tests if the correct modules are installed.




Click to view comments

Thanks for the information!
I've ordered a hamitup up converter. I'm going to try to use your scanner with my rtl to monitor Jupiter Radio bursts.
they occur around 18-23 mhz and your scanner will be perfect for sweeping the frequency band to see if it's possible to see them!
I'll share anything I happen to catch!

Al's picture

Now that sounds really interesting, radio astronomy is on the long list of experiments I want to perform!

Hello again,
I've got my Hamitup downconverter and after some playing around I was wondering how hard it would be to add the ability to save the sprectrograph as a png or jpg at a specified interval? Or even maybe have it scroll horizontally?
So far I havent seen any Jupiter Radio activity. But it's also a low time in the probability table. Should be some radio action soon and I'd like to be able to have it auto save so I dont have to it up all night watching and doing grabs.
I feel like I'm being pushy but I guess it never hurts to ask. =)


Hello again,
I've got my Hamitup downconverter and after some playing around I was wondering how hard it would be to add the ability to save the sprectrograph as a png or jpg at a specified interval? Or even maybe have it scroll horizontally?
So far I havent seen any Jupiter Radio activity. But it's also a low time in the probability table. Should be some radio action soon and I'd like to be able to have it auto save so I dont have to it up all night watching and doing grabs.
I feel like I'm being pushy but I guess it never hurts to ask. =)


Al's picture


Don't worry, I don't see constructive suggestions as pushy, it's good to know what people are doing with the software and how it could be improved.

At some point I was thinking of adding a control which would allow the viewing of specified sweeps or ranges of sweeps, although I'm still thinking of the best way to do this.

If you want to leave it over night try setting the 'Max scans' in the preferences window to a high value to retain a longer period of data.

I hope this is the right way to start RTLSDR Scanner. First I load “IDLE (Python GUI)” from the Start, Python 2.7 menu. Then I paste “rtlsdr_scan.py” or “rtlsdr_scan” next to the “>>>” prompt and hit enter. That results in the following being displayed:

Python 2.7.6 (default, Nov 10 2013, 19:24:18) [MSC v.1500 32 bit (Intel)] on win32
Type "copyright", "credits" or "license()" for more information.
>>> rtlsdr_scan

Traceback (most recent call last):
File "", line 1, in
NameError: name 'rtlsdr_scan' is not defined
I used the “rtlsdr_scanner-setup-win32.exe” script to install everything into a Windows 7 (64 Bit) partition and a Windows XP MCE (32 Bit) partition. I get exactly the same error message from each operating system.

Is this the correct way to start RTLSDR Scanner?
Is there an error in the script?
Is there a way to fix this error?

Al's picture


If you've used the installer you can start the program from 'Start -> Programs -> RTLSDR Scanner -> RTLSDR Scanner'.

Alternatively you can start a command prompt (on Windows 7 press 'Start' then type 'Command'). First change to the install directory then run it:
cd "C:\Program Files (x86)\RTLSDR Scanner"
python rtlsdr_scan.py


Thanks for your timely reply. The “RTLSDR Scanner” prompt didn’t appear in my Windows 7 Start Programs list. I did a complete re-install and now I have the prompt but when I click on it, it opens a command window that says RTL Scanner, writes some code and closes the window –but nothing else happens.

Tomorrow I’ll do a fresh Windows 7 install and try again. My RTL hardware isn’t due to arrive from China until the 19th – 26th of Feb. so I have time to get this installed. I have SDR# installed and it may be interfering with your program. I’m in touch with Bill (who posted on 02/08/2014) and he has offered to help me with an Ubuntu install. His preference for RTLSDR Scanner is what led me here.

I reinstalled under XP and now I get an error message “msvcr100.dll was not found”. I’ll re-image that partition tomorrow and try again. I’ll post back if I’m successful.

The command prompt approach didn't work for me either.

Again, thanks for getting back so quickly.

Al's picture

Hi Pete, I'm not sure why the installer is not creating the link, I'll see if I can replicate the problem.

SDR# shouldn't cause you any problems as my installer should copy the required rtlsdr libraries to it's own directory to overcome any problems with clashing installs.

To fix the XP problem try installing the Microsoft Visual C++ 2010 Service Pack 1, when prompted select 'vcredist_x86.exe'.


I reinstalled XPMCE w/SP-3 and updates. I then installed Microsoft Visual C++ 2010 Service Pack 1 from your link and rebooted. I used the “rtlsdr_scanner-setup-win32.exe” script to install RTLSDR Scanner. When I run the application I now get the RTLSDR Scanner command window briefly and then nothing happens. I did a screen capture of the XPMCE command window. It says:

RTLSDR Scanner

Traceback :
File “C:\Program Files\RTLSDR Scanner\rtlsdr_scan.py”, line 105, in frame =
FrameMain<”RTLSDR Scanner”, pool
File “C:\Program Files\RTLSDR Scanner\main_window.py”, line 135, in _init_
File “C:\Program Files\RTLSDR Scanner\main_window.py”, line 240, in create_wid
File “C:\Program Files\RTLSDR Scanner\main_window.py”, line 755, in set_contro
device = self.devices[self.settings.index]
IndexError: list index out of range

I installed the 64 bit version of Microsoft Visual C++ in Windows 7 but still get almost the same error message when I run RTLSDR Scanner. The Windows 7 command window says:

RTLSDR Scanner

Traceback :
File “C:\Program Files \RTLSDR Scanner\rtlsdr_scan.py”, line 105, in
frame =FrameMain<”RTLSDR Scanner”, pool
File “C:\Program Files \\RTLSDR Scanner\main_window.py”, line 135, in _in
File “C:\Program Files \\RTLSDR Scanner\main_window.py”, line 240, in crea
File “C:\Program Files \\RTLSDR Scanner\main_window.py”, line 755, in set_
device = self.devices[self.settings.index]
IndexError: list index out of range

Sorry to make all this work for you but I hope this information helps. The good news is I got the adapter cable for the tuner today and since they were both ordered at the same time I should get the tuner in the next few days.

Thanks for all the timely feedback.



All the Windows 7 paths have x86 after program files and should read "File “C:\Program Files \RTLSDR Scanner\..." Not sure why it changed when I pasted it in?

Al's picture

Probably the website editor stripping out what it thinks are tags, I'll look into it.

Al's picture

Hi Pete,

Thanks for the info, there was a bug when the program was first run without any devices attached. I've just committed the fixes which will download when you run the setup program again.


You must be one hell of a Software Engineer! I “updated” Windows 7 and XP MCE and your fixes worked for both. Now I’m really anxious to get my tuner.

Is it necessary to install Microsoft Visual C++ or does your new script install everything that’s necessary?


Pete (KB6YPT)

Al's picture

Thanks Pete,

I'm not sure about the Visual C++ runtime, did you need to install it on both XPMCE and Windows 7?

What has happened to the nice src/demo_waterfall.py script? I didn't find it in the git-repo.

Should it work w/o change in this last version? I haven't tried it with live data from my RTL-stick since my Zadig installation is busted at the moment. (drivers argh!!) It would be nice to have some spectrum/waterfall demos running just from a .rfs file just to tempt more people getting RTL-sticks and giving more attention to this very nice program.

Al's picture


The demo_waterfall.py script isn't part of this software, are you thinking of the one in pyrtlsdr?

I liked the idea of adding a demo capture and have added one to the repository, thanks. You can update it by running the installer again which will add a link to the start menu.

> The demo_waterfall.py script isn't part of this software, are you thinking of the one in pyrtlsdr?

Yes that's the one. Forgot why it was placed among your 'src/' files.

Thank you for your work


I downloaded your updated script (Released on 2014-02-21) tonight and ran it on a brand new install of Windows XP MCE with all of the Microsoft updates through 19 Feb 2014. It ran flawlessly. I did not install Visual C++ runtime unless Microsoft pushed it as a part of the Windows Update process.

I ordered my adapter cable and tuner on the same night. The cable arrived on Wednesday but I still haven’t received my tuner. I’m really getting anxious! If “what’s-her-name” doesn’t have a long honey-do list, I’ll probably tackle a Ubuntu 12.04 install this weekend.

Thank you for all your hard work and creativity.

Windows XP MCE
I had to install and ran “zadig_xp_2.1.0.exe” V for your program to detect the USB dongle.

RTLSDR Scanner
Found Rafael Micro R820T tuner

After starting the program, the Starting prompt in the lower left corner of the display says:
Error: [Errno 10061] No connection could be made because the target machine actively refused it

Windows 7
I had to install and ran “zadig_2.1.0.exe” V for your program to detect the USB dongle.

RTLSDR Scanner
Found Rafael Micro R820T tuner
Found Rafael Micro R820T tuner
Found Rafael Micro R820T tuner
Exact sample rate is: 2000000.052982 Hz
rtlsdr_demod_write_reg failed with -9
r82xx_write: i2c wr failed=-9 reg=06 len=1

The Starting prompt in the lower left corner of the display just continuously says “Starting”.
If I click the Stop button the top banner says “RTLSDR Scanner (Not Responding)”.


I received my tuner yesterday afternoon. I couldn’t get anything to happen when I plugged it into the computer under either Win 7 or XP. I discovered I had to install zadig for RTLSDR Scanner to recognize the tuner. I have reimaged WIN XP several times and tried different install approaches. The one outlined below shows the most promise. I hope I’m not overlooking something obvious. I have the supplied antenna hooked up but have also used the input from my 10 element Yagi and verified numerous channels are present.

Fresh install of Windows XP MCE w/all updates through 19 Feb. 2014.
Inserted DVB-T dongle and closed new hardware found pop-up.
Ran “zadig_xp_2.1.0.exe” V” for “Bulk-In, Interface (Interface 0)”
Driver WinUSB (v6.1.7600.16385) installed successfully.
Ran “rtlsdr_scanner-setup-win32.exe” script. After it installed I ran “Setup” from the Start>All Programs>RTLSDR Scanner program group. On reboot Windows XP found and installed the driver for “Bulk-In, Interface (Interface 0)”
File>Scan Properties showed Unknown in all fields except the description field.
The RTLSDR Scanner Command prompt that opened said “Found Rafael Micro R820T tuner”
Edit>Preferences showed a black dot under “Select”, Generic RTL2832U OEM under “Device”, Unknown under “Tuner”, 00000001 under “Serial Number”, 0.0 under “Gain (dB)”, 0.000 under “Calibration (ppm)” and 0.000 under “LO (MHz)”. Advanced was blank.
As soon as I started a scan I got a long list of “failed with -99” messages.
The second time I attempted a scan the scan properties Scan area filled in with:
Description: Blank
Start: 87
Stop: 108
Dwell: 0.1
FFT Size: 1024
First Scan: Unknown
Last Scan: Unknown
Latitude: Unknown
Longitude: Unknown

The Device area filled in with:
Name: Generic RTL2832U OEM
Tuner: Rafael Micro R820T
Gain: 0.0
LO: 0.0
Calibration: 0.0
But no signals were displayed.

The RTLSDR Scanner Command prompt window displayed a whole series of failed with -99 error messages.
rtlsdr_demod_read_reg failed with -99
r82xx_write: i2c wr failed=-99 reg=17 len=1
R82xx_set_freq: failed -99
rtlsdr_demod_write_reg failed with -99

I also get “Program not responding” when I attempt to close it.

Al's picture


Could you try running 'rtl_test' from the Osmocom RTLSDR library? The output should look something like:

Found 1 device(s):
  0:  Generic RTL2832U OEM

Using device 0: Generic RTL2832U OEM
Found Rafael Micro R820T tuner
Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6

Info: This tool will continuously read from the device, and report if
samples get lost. If you observe no further output, everything is fine.

Reading samples in async mode...
lost at least 80 bytes

If you get any '-99' errors or similar I suspect that the driver isn't installed properly or the dongle is not initialising fully. There's a good guide here (start at 8), please note there is a different Zadig version for XP.  It's also worth checking it's plugged into a USB 2.0 port.

The various errors you are getting from my software is all due to the problems communicating with the dongle.  In the first case (before you ran Zadig) it's trying to communicate with a server as it can't find any dongles.  Further down you mention it hangs, this is because it's getting no data from the dongle.

Personally I'd ignore XPMCE for the moment and concentrate on Windows 7.  If you have no luck with this try installing the software that came with you dongle and see if you can tune into an FM radio station (or digital TV, DVB-T, for most countries outside the USA, China or South America), if this doesn't work the dongle may be faulty.  A few times when I've plugged my R802T dongle into my Windows 7 machine it's complained that it will run faster if I plug it into a USB 2.0 port, I've just unplugged it for at least 10 seconds and plugged it back in to get it to work.

Good luck!



Please disregard my last post. I have your program working. The problems I was having were not with your software. I did all my testing using a front USB port on my computer that is apparently not working correctly. Last night I moved the USB dongle to a rear (Motherboard installed) USB port, re-imaged Windows XP and installed zadig. This morning I ran a fresh install of RTLSDR Scanner and was able to scan and see results in the FM Band and on channel 26 (542 – 548 MHz). Sorry for putting you through this.

Al's picture

Don't worry, good to hear it's working.


After a fresh installing, run the rtlsdr scanner, I have got an error message:

Import error: matplotlib requires pyparsing
Error importing libraries
Press [Return] to exit

What's wrong?

On my another PC, I use Debian Wheezy.
The setup totally having no chance, the descriptions incomplete, something is missing always.
Using this superb program on that computer would be good though...

I use the rtlsdr stick for a long time with the SDR#, works perfectly with it on Debian Wheezy (x64).

Following your setup instructions step by step, after the command "sudo setup.py" I have got a strange error message, something like this: "bash: setup.py: command not found". (I'm not sure).
I began the setup with this: "sudo apt-get install python python-wxgtk2.8 python-matplotlib python-numpy"
I think, something is missing for it yet, there would not be an error message otherwise in order for the python to work well.
Sorry, but I do not know the python altogether, I was never useful...

Excuse me my folly, but helps something else possibly:

In Debian, the command: python setup.py install
And the program starts so only: python rtlsdr_scan.py

And now, I'll try this awesome program... :)

"rtl_test -t" results:

Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001

Using device 0: Generic RTL2832U OEM
Found Rafael Micro R820T tuner
Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
Sampling at 2048000 S/s.
No E4000 tuner found, aborting.

Okay, with SDR# the device is working well.

Start the scanner, I experienced the same ones, than Pete:

In terminal, after the start:

RTLSDR Scanner

Found Rafael Micro R820T tuner
Found Rafael Micro R820T tuner
Found Rafael Micro R820T tuner
Exact sample rate is: 2000000,052982 Hz
rtlsdr_demod_write_reg failed with -9
r82xx_write: i2c wr failed=-9 reg=06 len=1

I'm confused!
Please, help me anybody!

Al's picture

I've just updated the code, I'm interested to know if this helps.

Hi Al!

I don't know, what you changed, but the program works perfectly now on the Debian.
I did not try all functions yet, but handles the sdr without an error already.

Thank you!

Al's picture

I'm glad to hear it's working for you, it caused me quite a bit of head scratching!

You changed anything, please do not handle this part hence! :-)

Thank you again!

Al's picture

Thanks, I've updated the install page.

I pulled the latest code from git a couple days ago and regardless of settings, the app core dumps when I click "start". I'm running Ubuntu 13.10. Going back through the commit history, the core dumps start at commit 653b3b1d88d132fc931566ef49736447fd170841, "Finer dwell control". I haven't tracked down the cause of the core dump yet.

If I revert back to the commit prior, it does run, however the update mode used for the chart makes it unusable for a scan of any real size. It seems to gather a full scan and then update the plot in small chunks, replotting and re-scaling the entire chart each time. Even for the default FM band scan, this makes the program unresponsive for minutes between each scan.

One other thing I have found, even in the version that was working for me is that the local oscilator value is not interpreted correctly. I'm trying to determine the delta, but it looks like it may be off by about 1000Mhz. If I set the LO value at 1998Mhz, it looks like it may use 998Mhz for the actual frequency calculation.

Al's picture

Hi Patrick,

There seems to be a bit of a problem between the driver and libusb, although it worked on Windows and OS X. At some point I'll try and look into the issue, but for the moment I've reverted the changes to the dwell and sample rate settings. Give the latest commit a try and see if it works for you.

The local oscillator is positive for up-converters, for example with a 100MHz up-converter scanning 30-40MHz the dongle would scan from 130-140MHz. 1998MHz sounds very high and I think the dongle frequency may be wrapping around somewhere. If you're scanning above 2GHz with a down-converter the LO should be negative. I'll update the documentation to make this clearer.

I'll pull the new commits this evening and give it a shot. I'm afraid I'm not a python person so my debugging help is somewhat limited.

The LO value being negative for downconverters makes sense and also explains exactly what I was seeing. The value is stored internally as a 32 bit signed number. I had found that an LO value of +2297MHz would give be pretty close to the correct frequency. Turns out that is 2^32-1998000000Hz. Thanks for the pointer.

BTW, I wanted to complement you on the very useful application. Nitpicking and rough edges aside, it is exactly what I need. Thanks for all the effort.

Al's picture

Thanks Patrick, do you have any suggestions to improve it?

Here are a few things I have noticed.

1) The drawing of the plot is a very cpu intesive process and as you have noted elsewhere, running with "live update" enable is painful on anything except small plots. My assumption is that it is inherent in the python library used to do the plotting. I assume it simply plots all the points each time it is called. Not sure this is easily fixable. While "live update" is cool, this certainly isn't a necessity.

2) Turning off autoranging turns it off not only for signal strength, but also for the frequency scale. Again, I assume this is a function of the python graphing library, but resetting the frequency to match the scan range when you press the start button might be nice. I don't know if this is one of the changes that came in later updates.

3) For better or worse, auto ranging must be enabled in spectrogram mode. If I remember correctly, clicking on the "set range" button gives you signal strength ranges. However the graph doesn't update the time steps on the Y axis unless autoranging is enabled. Probably also a side effect of the python graphing library.

4) It would be useful when switching to spectogram mode if you didn't have to switch the configuration from "average scans" to "retain last scans", or if histogram mode had a separate setting for the number of scans to plot.

Like I said, mostly nitpicky things. Nothing that really impacts functionality.

Al's picture

Thanks for the comments, it's good to know what users are thinking.

1) It uses matplotlib which is very flexible but was never intended for real-time data.  Hopefully someday a hardware accelerated version will be available.

2) and 3) I need play with the auto ranging, I've not had time to improve it since I added the spectrogram plots.

4) Good idea, I'd add it to the list.

To give a bit of feedback on the code you reverted, it appears that it fixed the crashing problem i was seeing. Things are quite stable on the top of tree code now. When I get some free time, I'll look at the changes and see if I can figure out what was causing so much grief.

Al's picture

It looks like something in the rtlsdr driver, a few users that haven't kept the driver up to date did not have problems with libusb seg-faulting and it works fine on Windows. At some point I'll try some of the older rtlsdr commits to see if I can get any further.

Al's picture

3) You can now toggle the autorange on each axis.

with the updated version. If I set the dwell time to anything less than 16ms it crashes with the following error .
rtlsdr_demod_write_reg failed with -9
r82xx_write: i2c wr failed=-9 reg=06 len=1
Segmentation fault (core dumped)

I'm trying to scan a range from 16mhz to 32mhz with an upconverter attached. *trying to scan for solar activity and jovian radio burst so I'm not worried about it missing anything on one frequency. I'm interested in seeing the overall spectrum with sweeps as fast as possible. The faster the better! =)

Any idea what might be causing it to crash?
My machine specs are..
Release 12.04 (precise) 64-bit
Kernel Linux 3.8.0-35-generic
Memory: 4 gig
Intel Core I5 2520m 2.50ghz X4
300 gig hd with 225 free.
Would it help if I set up a second machine and let it handle the rtlsdr and send the data via rtl_tcp?
Take some processing load off the scanner machine itself?

Al's picture


I've reverted the changes to the dwell and sample rate settings which seemed to break libusb on some distros. You should have a bit more luck with the latest changes.

I would be very happy if there's a compiled exe-version for Windows again...
Any news??

Al's picture

Hi Martin,

I used PyInstaller to create the executables, but unfortunately I can't get it working with current versions due to a problem with multiprocessing. I'll keep trying though.

Hi Al,
thanks; ...awaiting ...


I did a fresh install of Windows 7 Home Premium and when I install RTLSDR Scanner and try to run it I get the following error message:
"Import error: matplotlib requires pyparsing

Error importing libraries
Press [Return] to exit"

I tried a normal install from the 'D' drive, from the desktop and "Run as Administrator" from the desktop. The same script worked on my other computer. Any ideas on what I could be doing wrong?

Al's picture

Hi Pete,
A couple of people have had the same problem but I haven't been able to replicate it myself. I'll keep looking into it. In the meantime have you tried running the installer again?

Thanks Al,

Yes I’ve tried reinstalling numerous times, reimaged my fresh install and tried again with the same result. rtlsdr_scan_diag reports:


Tests for missing libraries

librtlsdr not found in path
Download from ‘http://sdr.osmocom.org/trac/wiki/rtl-sdr

Press [Return]”

But when I check, the path statement on a machine that works matches the path statement on the machine that doesn’t. They both have C:\Python27\ appended after …\WindowsPowerShell\v1.0\;

For what it’s worth, I have an RTLSDR Scanner installation on a different hard drive that I can plug into this computer that works perfectly and I installed SDR# on the partition that is giving me the error messages and it works normally so I don’t believe it’s a hardware issue. I sure hope I’m not doing something dumb!


Click to add a comment