Install_Test_Configure_RTLdongle

A page compiled from test and installation fault reports in the SDR#, SDR-Radio and other groups concerning the RTL dongle from 2012 to 2016. With links to more information. Page modified January 2016.


Zadig Driver installation notes. Alternative drivers

Faults/ Support/ Extras

Testing the Dongle

RTL_Eeprom
write different identification information to the dongles so HDSDR and other software will differentiate between two or more dongles.


Zadig.   http://zadig.akeo.ie/
Note Zadig does not install itself on your computer. It is just an inactive file. It does not conflict with other drivers or software. The only problems are created by it's users assigning the wrong driver to the wrong device.
It only does what you tell it. If you are careless, do something you are not REALLY certain of then it will obey you and offer no "undo".
If noticed quickly maybe a System Restore might be the easiest answer.
As in all cases when you are installing something creating a Restore Point first is a very good idea.

In the drop-down menu:- Options - List All. "Advanced Mode" shows you the log, maybe useful if any errors occur. Help best look at the link on the Zadig site.

Widows Defender or any anti-virus/security program may have to be disabled to get Zadig to work.


Not sure of which device Zadig is showing? Later versions of Windows may use different names. Windows 10 says "RTL2838UHDIR".  Look for the USB ID, the VID/PID indicated by my cursor. The list here https://uk.groups.yahoo.com/neo/groups/SDRSharp/conversations/messages/16854 is reputedly up to date January 2015. Ignore the 0x in front of the figures in the list. There is a list on the Osmocom site. http://sdr.osmocom.org/trac/wiki/rtl-sdr
Look at Joannes's post here before you use Zadig.

My picture shows I have already  used Zadig, the WinUSB driver is assigned. Note WinUSB is a Windows driver, it is already present in a Windows computer, Zadig associates the RTL to it. But the latest Zadig may incorporate a later driver which would then replace it. Note libusbK is an alternative driver for the RTL, try that if you have problems.

If you are careless it is possible to assign a driver to another USB device, look here for the solution. In Windows XP you may need to go further, like here.



Installing other drivers with Zadig. This section also applies to other devices as well as the RTL dongle.

 Example libusb for Softrock control among other uses.

Also libusbK an alternative for the RTL dongles.
Always make a Restore Point first.
As above. List all devices, select the correct one. Note the USB ID, I think all Softrocks will be 16C0 05DC BUT this ID is used by other devices. Remove everything else if you are not certain. Normally the "Driver" box will be blank. Select the libusb-win32 driver in the drop-down box, and click "Install Driver". 
This picture shows Zadig after installation.
Sometimes in Device Manager I see one of the the Softrock identities is "LibUSB-Win32" and/or "USBasp". This is because I do use a USBasp, this has the same USB ID as the Softrock so it looks the same and uses the same driver.
Note, Before installing a tick in the "Edit" box enables you to give a device a unique name that will show different names in Device Manager for different devices.

Here is a Zadig alternative go to Documentation - Installation - It tells you where to find 
the "InfWizard"


Some notes and links about installing the RTL Dongle. 
RTL Dongle ONLY:- CAREFULLY READ http://rtlsdr.org/softwarewindows for instructions for obtaining the support files. Note this is an old page, recently (June 2015) many think HDSDR uses less CPU resources but it is difficult to be sure as this depends upon the various settings.
SUMMARY:- All links and instructions on above page. Do  everything in the order described.

Windows Security.
You should always set up your own user account in Windows and make yourself an administrator.

Do not install programs in "Program Files" if you need to alter them, or if they are old and want to write to "Program Files". Use another folder, make something like C:\SDR Programs.
This post  https://uk.groups.yahoo.com/neo/groups/SDRSharp/conversations/messages/18509   and the following one in the thread tells how to avoid Windows Security features like "Access Denied".

Windows 10:-
Using the "Windows Security" method above the RTL dongle should work.



=============
Notes and links from reports in various groups, like rtlsdr, SDR# and SDR-Radio

“No compatible devices found”
“1 compatible devices have been found but are all busy”/
And other faults look here http://www.rtl-sdr.com/rtl-sdr-quick-start-guide

THE RTL Site everything here. New users:- Look at "Quick Start Guide".
RTL DLLs for SDR-Radio M3GHE has full instructions to get the RTL dongle working with "SDR-Radio" software.  SDR-Radio home http://v2.sdr-radio.com/Home.aspx Using a converter with SDR-Radio
RTL2832U_Support.rar DLLs 32 and 64 bit https://groups.yahoo.com/neo/groups/sdr-radio-com/files/RTL%20DDL/32%20bits/

May 2016 Support for SDR-Radio v3 Instructions and download link. Note also JDow's RTLTool

Dongle not found in SDR-Radio:- "I remember i had to get a more recent version of libusb for my few of my PCs for similar symptoms, especially with USB 3.0.  My libusb-1.0 version is 1.0.15.10644-rc3."
To find the latest  get RelWithDebInfo.zip   Unzip, inside you will find it. Copy it over the older file.

Reset/reinstall SDR-Radio. http://v2.sdr-radio.com/Support/Full-Reset One user reported success.

Alternative Driver:- If after installing the libsub-Win32 driver it does not work try the libusbK driver. You may use Zadig as above on this page. This has twice been reported as solving an issue. I confirm that libusbK works with the RTL dongle.

USB3:- The dongles may not work with USB3. Dave in the SDR# group says:-A USB3 hub will cause the PC to use its USB3 device driver even if it has a USB2 device plugged into the hub.  Plugging a USB2 device directly into the PC's USB3 port will however usually cause the PC to use its USB2 device driver (so long as the PC is not driving the port via an inbuilt secondary hub).
Maybe the alternative driver will overcome this problem?

Dongle stops working after an automatic Widows update. The dongle is identified as a TV receiver. If you just let Windows update automatically it may replace the driver with TV drivers. Zadig will have to be used to reinstall the WinUSB driver.

Device Manager should show the dongle as a "Libusb (WinUSB) device" and show the drivers to include WinUSB.sys. Or, if you use the alternative driver a "LibusbK USB Device". The unused, irrelevant infra red detector will be listed as a USB Human Interface Device.

And, look out for security! Windows, anti-virus or similar software can disable downloaded files, sometimes without your knowledge. Right click - "Unblock" might work. Digging into antivirus quarantined files might find something.


A DLL for SDR# that can make the RTL tune to 15MHz or below. Relatively low sensitivity but said to be better than the direct conversion mod. May work with other software?? October 2015, does this work with the latest updated SDR#?



Testing the dongle
Testing the RTL Dongle Independently of any SDR Software:-
This involves simple command prompt entries. See here for a page that explains some basics.
I use xplorer2lite an alternative Windows file manager which makes command windows easy to open in any folder.

RTL_Test This will test the driver installation and the dongle.  If these results confirm basic operation then look for configuration or DLL problems.

Inside the x32 or x64 as appropriate you will find rtl_test.exe. (RTL_Eeprom also here) Run it, as Administrator.  [Text with this background copied from command window.]

Open a command window, navigate to the folder containing the RTL utilities, for example:- D:\MoreProgramFiles\RTL=Test>

Type RTL_Test    [press Enter (Return)]

You should get something like:-

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

Using device 0: Generic RTL2832U OEM
Found Elonics E4000 tuner
Supported gain values (14): -1.0 1.5 4.0 6.5 9.0 11.5 14.0 16.5 19.0 21.5 24.0 2
9.0 34.0 42.0
Sampling at 2048000 S/s.

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... +++++++++++++++++++++

Ctrl-C stops the test.

If RTL_test closes without a message then it may have a driver problem or a faulty or incompatible dongle.

Or, maybe a USB problem, try another socket. On some devices USB3 might give trouble.
Try removing ALL USB devices, plug in the dongle, wait, then put in anything else you need.

Check Zadig again. List all devices.
Be sure it is Bulk Interface 0 with the correct VID/PID, see "Zadig" lower down this page. What driver does it it have?
It should show Win USB.

Windows Device Manager will also show which driver is assigned to the dongle. (Bulk Interface 1 is the infra red detector and is irrelevant.) Later versions of Windows may give different names, RTL 2832 for example. 

============================

RTL_Test gives a strange message if the dongle is in use by another program:-

Open a command window, navigate to the folder containing the RTL utilities, for example:- D:\MoreProgramFiles\RTL=Test>

Type RTL_Test    [press Enter (Return)]

Found 1 device(s):
  0:  Generic RTL2832U

Using device 0: Generic RTL2832U
usb_open error -3
Please fix the device permissions, e.g. by installing the udev rules file rtl-sd
r.rules
Failed to open rtlsdr device #0.


For more information regarding problems try typing this in the command window 

Command:-

set LIBUSB_DEBUG=6   [press Enter (Return)]
# then #
RTL_Test    [press Enter (Return)]

If there is a problem a lot of information is given. It might just give a clue about the solution.
If there is no problem then the utility does not stop, just repeats the same message showing it is delivering data...

( For more options D:\MoreProgramFiles\sdrsharp>rtl_test -h)


Eeprom

NOT DIAGNOSIS! RTL_Eeprom will write to the eeprom. Use with CARE! For most the only use is to change the identification. HDSDR, see lower, change product and manufacturer.

See above Testing the Dongle to get the utility.

D:\MoreProgramFiles\RTL=Test>rtl_eeprom -h
rtl_eeprom, an EEPROM programming tool for RTL2832 based DVB-T receivers

Usage:
        [-d device_index (default: 0)]
        [-m <str> set manufacturer string]
        [-p <str> set product string]
        [-s <str> set serial number string]
        [-i <0,1> disable/enable IR-endpoint]
        [-g <conf> generate default config and write to device]
        [   <conf> can be one of:]
        [   realtek             Realtek default (as without EEPROM)]
        [   realtek_oem         Realtek default OEM with EEPROM]
        [   noxon               Terratec NOXON DAB Stick]
        [   terratec_black      Terratec T Stick Black]
        [   terratec_plus       Terratec T Stick+ (DVB-T/DAB)]
        [-w <filename> write dumped file to device]
        [-r <filename> dump EEPROM to file]
        [-h display this help text]

Use on your own risk, especially -w!

D:\MoreProgramFiles\RTL=Test>




Example:- Replacing original Serial Number  here 5 (or whatever characters you wish to use).

D:\MoreProgramFiles\RTL=Test>rtl_eeprom -s 5
Found 1 device(s):
  0:  Generic RTL2832U OEM

Using device 0: Generic RTL2832U OEM
Found Rafael Micro R820T tuner

Current configuration:
__________________________________________
Vendor ID:              0x0bda
Product ID:             0x2838
Manufacturer:           Realtek
Product:                RTL2838UHIDIR
Serial number:          00000070

Serial number enabled:  yes
IR endpoint enabled:    yes
Remote wakeup enabled:  no
__________________________________________

New configuration:
__________________________________________
Vendor ID:              0x0bda
Product ID:             0x2838
Manufacturer:           Realtek
Product:               
RTL2838UHIDIR
Serial number:          5
Serial number enabled:  yes
IR endpoint enabled:    yes
Remote wakeup enabled:  no
__________________________________________
Write new configuration to device [y/n]? y

Configuration successfully written.
Please replug the device for changes to take effect.


Then Windows will ask for drivers. I have always found it is not necessary to use Zadig. I just let Windows do it automatically. But maybe yours will not, then use Zadig.





THE HDSDR DLL DOES NOT REPORT A SERIAL NUMBER TO GET HDSDR TO SEE TWO OR MORE DONGLES AS SEPARATE ITEMS I DID THIS:_
==================================================================
HDSDR shows "Product" "Manufacturer" in  the RTL ExtIO drop-down. So write new Product/Manufacturer names.

[My device] RTL in tin 100MHz converter:-

D:\MoreProgramFiles\RTL=Test>rtl_eeprom -p +64ppm (Change product name.)
Found 1 device(s):
  0:  Generic RTL2832U OEM

Using device 0: Generic RTL2832U OEM
Found Rafael Micro R820T tuner

Current configuration:
__________________________________________
Vendor ID:              0x0bda
Product ID:             0x2838
Manufacturer:           Realtek
Product:                RTL2838UHIDIR
Serial number:          00000070

Serial number enabled:  yes
IR endpoint enabled:    yes
Remote wakeup enabled:  no
__________________________________________

New configuration:
__________________________________________
Vendor ID:              0x0bda
Product ID:             0x2838
Manufacturer:          Realtek
Product:                +64ppm
Serial number:          00000070
Serial number enabled:  yes
IR endpoint enabled:    yes
Remote wakeup enabled:  no
__________________________________________
Write new configuration to device [y/n]? y [press "y" Enter (Return)]

Configuration successfully written.
Please replug the device for changes to take effect.

Windows asks for the driver, let it do it automatically. Windows should know what to do from your original Zadig installation. Cancel the second offer, Bulk Interface 1 is the unused IR detector. 
If Windows does not do this satisfactorily Zadig will be required.


D:\MoreProgramFiles\RTL=Test>rtl_eeprom -m HF-100MHz (Change manufacturer name.)
Found 1 device(s):
  0:  Generic RTL2832U

Using device 0: Generic RTL2832U
Found Rafael Micro R820T tuner

Current configuration:
Error: invalid RTL2832 EEPROM header!
__________________________________________
Vendor ID:              0x0bda
Product ID:             0x2838
Manufacturer:           Realtek
Product:                +64ppm
Serial number:          00000070
Serial number enabled:  yes
IR endpoint enabled:    yes
Remote wakeup enabled:  no
__________________________________________

New configuration:
__________________________________________
Vendor ID:              0x0bda
Product ID:             0x2838
Manufacturer:           HF-100MHz
Product:                +64ppm
Serial number:          00000070
Serial number enabled:  yes
IR endpoint enabled:    yes
Remote wakeup enabled:  no
__________________________________________
Write new configuration to device [y/n]? y  [press "y" Enter (Return)]

Configuration successfully written.
Please replug the device for changes to take effect.

Windows asks for the driver.
If Windows does not do this satisfactorily Zadig will be required.

Check:-
D:\MoreProgramFiles\RTL=Test>rtl_eeprom
Found 1 device(s):
  0:  Generic RTL2832U OEM

Using device 0: Generic RTL2832U OEM
Found Rafael Micro R820T tuner

Current configuration:
__________________________________________
Vendor ID:              0x0bda
Product ID:             0x2838
Manufacturer:           HF-100MHz
Product:                +64ppm
Serial number:          00000070
Serial number enabled:  yes
IR endpoint enabled:    yes
Remote wakeup enabled:  no
__________________________________________

D:\MoreProgramFiles\RTL=Test>

NOW HDSDR says +64ppm HF-100....

[Maybe this can be done in one go, for example:- D:\MoreProgramFiles\RTL=Test>rtl_eeprom -p +64ppm -m HF-100MHz But not tried.]

[I once got the "Error: invalid RTL2832 EEPROM header!" message.But it did not appear after I had written to it I only saw this on this one dongle.]

SDR# says Generic RTL2382 OEM 

Here is  Another way to change just the serial number.  May be useful for SDR-Radio and other software that uses the serial number. This also requires command prompt entries as described above.


Comments