Hi people - please help
I'm trying to install a dongle to feed Flightradar24. I'm following the instructions as given by Gonic Goose http://sonicgoose.com/using-a-rtlsdr-dongle-for-ads-b/ and the Dongle is the exact same as he is using.
When I first pluged in the device window 7 installed some drivers, and didn't manage to stop it.
My problen now is with the zadig.exe driver installation. First time around, it came up alright but only had the option "Bulk-In Interface 1". Maybe I should not have chosen that, but stupid me.
Then I installed RTL1090, and it reconizes that the dongle is there but gets no data. One line reads "Cannot set freq:-1" I guees because the driver is not there.
Second time around with zadig.exe, there is no select options at all and it says "0 devices found". when I go to menu "Options->List all devises" it simply stops with the message "Zadig stopped working"
In the device manager the dongle does not show. Instead it show a keyboard device when I plug in the dongle (because of the "Bulk-In Interface 1" ??) .
So how do I clean up my act (and PC) and get back on the right track?
Thanks in advance. Enjoy your Sunday
Knud
[Attachment deleted by Admin to save file space]
My dongles are in the loft so can't check exactly.
My initial suggestion is remove the dongle and reboot the PC.
If you have a choice of USB ports, try a different one and then run zadig. If not, use the same one again.
From Sonic Goose (the vital bits are in red:
Uncompress the Zadig drivers you downloaded and run Zadig.exe.
In the drop-down menu select Bulk-In Interface 0.
If that isn't available then go to the Options menu and select List All Devices. Then try again.) Don't change anything else; just click Replace Drivers.
Now see if RTL1090 works.
Thanks Ian
No luck so far
I managed to roll back the initial installation and start over.
BUT, when I start zadig it only gives the option "Bulk-In Interface 1", not "0"
AND when I go to the Options menu and List all Devices, the program terminates with i generic windows message to that effect.
Is there and other way I can sneak the drive into places?
Knud
[Attachment deleted by Admin to save file space]
Also found various attempts to fix similar problem:
https://groups.google.com/forum/?fromgroups=#!topic/ultra-cheap-sdr/ejWrX4LHaeY
Probably the most relevant are:
make sure you are using the correct version of zadig - there is a separate version for WinXP
find the dongle in Device Manager (might be in sound, video controllers) and uninstall it (right click on it for the option) - suggest reboot after that
try running zadig as administrator
Ian
When you start RTL1090 does it find the dongle? In your first screenshot it did.
There are some settings for feeding FR24 which I can explain later but let's get RTL1090 seeing the device first.
Quote from: Anmer on April 21, 2013, 12:56:36 PM
When you start RTL1090 does it find the dongle? In your first screenshot it did.
There are some settings for feeding FR24 which I can explain later but let's get RTL1090 seeing the device first.
Now I have been back and forth a few time and it is hard to keep track of the consequences of each step I have taken.
At the moment the device does not show up in zadig. TRL1090 sees it but different message nowFor some reason Windows has installed keyboard drivers for the devices.
If I remove all the drivers,it has then shown up in zadig but not any more
If I choose Options->List all devices Zadig terminates
I have been round the above a few times. Last time around windows did not install the keyboard drivers but instead a "Unknown device #1 (Interface 1)" (sorry screen shot is in danish)
[Attachment deleted by Admin to save file space]
Zadig is a only utility to load drivers that already exist on your PC.
If you start RTL1090 does it find the DVB-T USB device?
Quote from: Anmer on April 21, 2013, 01:37:47 PM
Zadig is a only utility to load drivers that already exist on your PC.
If you start RTL1090 does it find the DVB-T USB device?
Just updated my post. yes it sees it but different message
[Attachment deleted by Admin to save file space]
Sorry Anmer
Have to run away for an hour. But realy appreciate the help!!
Knud
That suggests the wrong drivers are installed.
Or not all drivers are installed?
http://tech.groups.yahoo.com/group/rtl1090_english/message/155
In my RTL1090 folder I have the following files:
rtl1090.exe
rtl1090.ini
msvcr100.dll
libusb-1.0dll
rtlsdr.dll
Quote from: IanH on April 21, 2013, 01:55:20 PM
Or not all drivers are installed?
I don't think so.
If any of the folder files are missing RTL1090 won't load, but it does.
It can't find the Bulk Interface driver. And having spent many days trying to fix a wrong driver and failing, I have seen that error message more times than I care to remember.
I think the core problem is that Zadig is not working correctly on my laptop. When I choose Options->List all devices it terminates no matter if the dongle is attached or not.
The "Go and look what devices are there" part doesn't work, and from that follows that no drivers are replaced.
Would there be another way than zadig to pick the drivers?
What version of Zadig are you using?
zadig names/detects the rtl as bulkinterface 1, and also bulkinterface 0, so you started of right, you have to install twice, one for each.
if the install went wrong(or you used the cd) You can also use the option "Extract files only don't install", extract to a folder on your PC, then go into the device manager and find the dongle, update driver- have disk and navigate to where you extracted the driver to and select it, you'll have to do it twice one for each bulkinterface or whatever it was named by windows.
That was how i sorted it on Smudgers lappy as he had used the cd that came with the dongle. Then for good measure i rebooted and reinstalled again just to make sure.
I grabbed a dongle and tried to re-install on this PC. Then I remembered it wouldn't work previously and unsurprisingly I got the Error -12.
Spent some time trying to fix without success. I'll try the suggestion.
For info this is on 64 bit Win7. Not had any problems on 32bit WinXP.
Found a comment that perhaps Win7 updates have killed the Zadig install. But most people reporting this error get no joy from the replies - NOBODY KNOWS is my impression.
Error -12 seems to mean that something else already has claimed the dongle. Ok but what?
knudp has reminded me how frustrated I am by this.
Ian
My system is W7 x64, when i plugged in my second dongle i just asumed that it would select the zadig driver but it didn't so i had to go through the rigmarole again and do it the way mentioned in my last post.
Quote from: kered on April 21, 2013, 08:52:49 PM
zadig names/detects the rtl as bulkinterface 1, and also bulkinterface 0, so you started of right, you have to install twice, one for each.
if the install went wrong(or you used the cd) You can also use the option "Extract files only don't install", extract to a folder on your PC, then go into the device manager and find the dongle, update driver- have disk and navigate to where you extracted the driver to and select it, you'll have to do it twice one for each bulkinterface or whatever it was named by windows.
That was how i sorted it on Smudgers lappy as he had used the cd that came with the dongle. Then for good measure i rebooted and reinstalled again just to make sure.
I want to do what you suggest, but when I start zadig now there is absolutely nothing detected. No selection options in the pull down box, and if I go to List all devices the program terminates.
One thing i have tried is to add a new device which I called "ADS-B" by keying in the USB ID "0BDA 2838 01". That creates a file in a folder 'USB_driver". But I have not been able to associate the file with the device. I might give it another try.
I really appriciate all your suggestions, but it is frustrating resetting the system again and again >:(
I the end it may work and I wound't know why ???
UPDATE: this is the drives I've got now (sorry for the danish)
[Attachment deleted by Admin to save file space]
Right, so I just realised that I got a 64bit Windows 7. That is maybe part of the problem. Do I need a special version of Zadig or do I have to do something special in Zadig to generate a 64bit driver?
Bloody hell!
Yes, i bet you are using the xp one
Quote from: kered on April 21, 2013, 10:30:43 PM
Yes, i bet you are using the xp one
Nope, I got that part right. The version is 2.0.1 (build 160)
Tried everything suggested by Derek (kered). No joy.
Beein in to safe mode to add drivers - no success
And in case it is of interest, this is the link I found earlier. If nothing else it may show your dongle as a "Composite parent" so you know where it went. I tried the method suggested without success. Look at last post in thread.
https://groups.google.com/forum/#!msg/ultra-cheap-sdr/CNnWetfFPq0/7T1BL233zdsJ
Not sure if it matters, but in "driver file details" for the dongle,
winusb.sys is version "6.1.7601.17514" - not 16385
WdfCoInstaller01011.dll is version "winmain_win8rc.120518-423" - Win8!!!
WinUSBCoInstaller2.dll is version "6.1.7600.16385" - wow the correct version
Interested to see what a working version has.
If any of those has changed the internal addressing compared to the 16385 version, it is never going to work. But who knows?
Looked at my working WinXP version - all have 16385 in the description. I need to set up some test 32 bit and 64 bit Win7 versions.
working w7 x64 driver details
[Attachment deleted by Admin to save file space]
Quote from: kered on April 21, 2013, 08:52:49 PM
zadig names/detects the rtl as bulkinterface 1, and also bulkinterface 0, so you started of right, you have to install twice, one for each.
My problem is I see the bulkinterface being "installed" in the Windows task bar when I insert the DVB-T USB stick but Zadig doesn't see them listed. It lists the device name and reinstalling the drivers doesn't help. RTL1090 can't find the device.
Removing the device drivers makes no difference.
Anmer, open device manager and then plug in the dongle and watch for the new addition, windows sometimes uses other names, once you know the name given to the device that same name should appear in zadig(list all devices) and is the one to install the drivers for.
Bugger - Dereks's screen shot looks like my set up, so should work. Head hurts from banging on desk.
Ian
Try getting sdr# or sdr-console to work first then go from there, or even adsbsharp as no aditional files are needed. That way you know its not the dongle at fault
Probably a stupid question but you did put rtlsdr.dll, libusb-1.0.dll into the rtl1090 folder?
Am I right when I deduct this:
- The driver that zadig is supposed to install is what RTL1090 will use to manipulate the dongle (set freq.) and retrive data.
- However the RTL1090 software can detect the dongle directly regardless (via device manager?). It sees a ezcap device but can not set frequency (see screen shot above)
- Because of missing/wrong driver freq. can not be set and data cannot be read.
As I have shown above I have some strange drivers including a REALTEK drive.
I have managed to let Zadig generate new files, but when I try ´to replace drivers, Windows claims that I slready have the best drivers available.
Hi ..........
Tried one more time with some input from SonicGoose. No luck
- I removed the drivers and thereby the device in device manager, then restarted the the laptop
- Inserted the stick and let it install drivers. Funny enogh it now installed one drive I had defined prviously with Zadig - Gave me some false hope. (see shot 1, 2, 3)
- Then started zadig, but the program seems oblivious to any USB devices. (shot 4)
- Started RLT1090 to see if it got anything. First it claims to see one ezcap device, but ends up saying Device 0; Cannot open:-12 (shot 5)
Grrrrrrr!
[Attachment deleted by Admin to save file space]
In Zadig, did you choose Options->List all devices?
See:
http://www.flightradar24.com/dvbt-stick
Quote from: Anmer on April 23, 2013, 04:28:37 PM
In Zadig, did you choose Options->List all devices?
See:
http://www.flightradar24.com/dvbt-stick
Yes, and no. Whenever I choose "List all devices" zadig terminates saying "the program stopped". So I never got to see that list. It makes no difference if the stick is inserted or not - the program terminates
I also ran the program as administrator. No difference.