AirNav Systems Forum
AirNav RadarBox and RadarBox24.com => AirNav RadarBox and RadarBox24.com Discussion => Topic started by: Michel on November 08, 2016, 01:46:01 PM
-
Today I've received a dongle (NooElec Nesdr Mini 2+), which I want to use for my Radarbox. I've updated to version 6, installed Zadig and started Radarbox. For some reason, Radarbox doesn't recognise my dongle (hardware not connected), and I really don't know why.
Attached a screen from zadig.
Is there something I've forgot or doing wrong?
Thanks!
-
It looks like you have installed the drivers to the integrated web cam. Use the down arrow to show the dongle then reinstall the drivers
Alan
-
It might be necessary to go to options and then click on list all devices before the donlge is listed in zadig.
The dongle should be displayed as RTL2838UHIDIR. In some cases it is displayed as Bulk-In, Interface (Interface 0) plus Bulk-In, Interface (Interface 1). In that case install the WinUSB driver to both Bulk-In Interfaces.
Ingo
-
Sorry Alan, posted the wrong screenshot.
Ingo, Zadig doesn't see my dongle. See the first screenshot for the options I've got. So I've updated bulk in interface 0 and 1, but still Radarbox doesn't see my dongle.
-
Have you restarted your PC 1-2 times before you have tried to start ANRB software?
Ingo
-
I would pull the stick out of its socket and then put it back in as well again before starting V6
Alan
-
I've restarted several times Ingo.
Unfortunately no luck on your option Alan.
Don't know if it matters, but I'm running W8.1 64bit and I've only got USB3 ports.
-
I have two of those sticks and have had no problems
No other ideas I am afraid
Alan
-
32 or 64 bit it doesn't matter. I presume that you are using the Vista or later version?
Alan
-
Have you tried dump1090 to see if the alternative drivers for the dongle are installed correctly?
Additionally you can try to copy all .dll files from dump1090 folder to ANRB folder.
I've used USB3.X and USB2 Ports. No difference noticed.
Ingo
-
USB3 Ports should be backwards compatible
Alan
-
Ingo, what's dump1090?
-
dump1090 is an ADS-B mode s decoder, which is usually used to feed plane plotter and several other ADS-B related software tools. Dump1090 opens in a comand window and is usually configurated & started via a batch file.
http://www.satsignal.eu/software/dump1090-win.1.10.3010.14.zip
If the drivers of the dongle are installed correctly: just unzip the above folder and double click on the dump1090.bat file. A command window shall open showing ADS-B data of received airframes: hex, flight id, altitude, position,
Ingo
-
note dump1090 is not required for the dongle
Alan
-
Yes Alan, I know, but it is a quick and easy way to check the alternate drivers of the dongle, as it works out of the zip, if the drivers are installed correctly. Further ANRB.EXE uses the same dll files to operate with the dongle. If one of the dll is missing in ANRB folder or somehow got corrupted it is possible to replace them with the ones from dump1090 folder. If I remember correctly I did this "ages" ago to get my setup running.
Ingo
-
Ingo, this is what I've got:
-
I am sure you have already done it but is the stick inserted in the port when you start up V6
Alan
-
The stick is already used by another software instance. ANRB V6 sometimes doesn't set hardware free if it is closed evenue uf it wasen't able to get the dongel fully operational.
Try the following:
Close ANRB.EXETER
Disconnect dongle
Reboot system
Reconnect dongle
Start dump1090 to see if the drivers are installed correctly and the hardware is free for access.
If dump1090 worked close it and try ANRB again.
Ingo
-
I took a closer look to the screen shot and it seems that dump1090 tries to connect to an unusable device. In the beginning you accidentally installed the alternate drivers to your Webcam ( see your first zadig related post ). Have you installed the correct drivers for the webcam again?
Ingo
-
Another way to get dump1090 workIng is to edit the dump1090.bat file by adding the following: --device-index 1
Unfortunately that will not solve the ANRB.exe problem.
Ingo
-
With close ANRB.EXETER do you mean; just close the Radarbox software, or some particular file?
Before I've started all this, I've made a recovery point. When I noticed the mistake with the webcam drivers, I've returned to this recovery point. So I guess this shouldn't be a problem anymore.
-
I think it should read ANRB EXE, i.e. close down V6
Alan
-
That's what I've tried Alan. Closed ANRB, restart, reconnect dongle, checked dump1090, but I've got the same screen as before.
-
EXETER was caused by the stupid auto complete function of my tablet. It shall read ANRB.EXE.
Yes, that should have set back the webcam driver. Anyway, have you checked the webcam driver while
using zadig to install the alternate drivers of the dongle during the second attempt?
Ingo
-
Is there other receiver hardware connected to your PC?
Ingo
-
Hmm I guess there still is something wrong with my webcam, as zadig doesn't mention it anymore in List all devices. The only other hardware connected to my pc is an USB mouse.
But I'll check another time, as it's getting late. Thanks both for your help so far.
-
Just to let you know, I got this thing working now. Looking good!
-
Great Michel what did you do, put the web cam drivers back in?
Alan
-
Indeed Alan, they've caused the problem. Well actually it was me who caused the problem, but never mind... ;)
-
As long as it worked out ok in the end Michel
Alan
-
Are you using airnav software from the download with or with out the password etc, My dongle is on a Pi ver1 uploading to flightware.
-
Siddy,
Michel is using V6 software downloaded from the support page. Non Airnav dongles normally use the Zadig drivers to work with V6
Alan