RTLSDR Scanner Binaries

Al's picture

Update:
I no longer use SourceForge to host content due to complaints. Take a look at the latest releases on GitHub instead.

As installing RTLSDR Scanner is a bit of a pain I've upload some test Linux and Windows executable binaries to SourceForge.

You'll still need the rtlsdr library in your path and Windows users may have to search for the 'Microsoft Visual C++ 2010 Redistributable Package'.

I'd like to hear about your experiences with these in the comments below.

Downloads

Linux 32 bit rtlsdr_scan-linux-32bit
Windows 32 bit rtlsdr_scan-windows-32bit
Windows 64 bit rtlsdr_scan-windows-64bit

 

Categories: 

Comments

4

Click to view comments

I am running Xubuntu 12.04. Have followed your Linux installation instructions but when I try to launch the scanner in the src directory, I get the following:
[email protected]:~/RTLSDR-Scanner-master/src$ python rtlsdr_scan.py
Traceback (most recent call last):
File "rtlsdr_scan.py", line 54, in
from cli import Cli
File "/home/john/RTLSDR-Scanner-master/src/cli.py", line 36, in
from file import save_plot, export_plot, ScanInfo, File
File "/home/john/RTLSDR-Scanner-master/src/file.py", line 43, in
from misc import format_iso_time
File "/home/john/RTLSDR-Scanner-master/src/misc.py", line 37, in
import serial.tools.list_ports
ImportError: No module named tools.list_ports

I have used the rtlsdr_diag script to check and all dependencies are on board OK, including pyserial (2.5)

I would be glad of some help. Thanks.

Al's picture

pyserial is a bit out of date, you'll need 2.6 for it to work.
Try running a system update - on Ubuntu 12.04 version 2.6 is installed. If you used pip to install pyserial try:
sudo pip install pyserial --upgrade

didnt know where to post but for those who have the usb error -12 , i had this , sdrsharp was working fine but the scanner gave me this error , i thought it was the installation or soft problem but i discover that rtl_tcp gave me the same error ...
i just unplugged my smartphone from the pc ... the error is gone in both...

Al's picture

Thanks ben, that's a strange one.

The mailing list for the driver is here, they might be interested in a bug report if you have time.

Click to add a comment