AirNav Systems Forum
AirNav RadarBox and RadarBox24.com => AirNav RadarBox and RadarBox24.com Discussion => Topic started by: richk107 on January 17, 2019, 10:30:25 PM
-
I posted this question to Amazon looking for assistance. "Where can I find drivers, software and documentation for this dongle? The Radarbox website doesn't provide any support information." Someone from AirNav responded that I should look to this site for more info. https://www.radarbox24.com/tracking-with-your-flightstick While this page does contain information regarding the FlghtStick, it still doesn't provide links to Windows drivers. Another user posted a more direct question regarding the drivers which AirNav responded that they would be ready later this month. Call me crazy but the first link implies that there is available software for this dongle as it does mention those wishing to configure the hardware for Windows should visit the AirNav Radarbox page. While I generally don't mind being on the bleeding edge of tech, selling hardware before a driver is even ready is too much.
Is there a beta driver available? I'd be more then happy to test.
-Rich
-
Try this one from the page you mention, don't see why it shouldn't work. Install it after the V6 software http://www.airnavsystems.com/Download/ANRB/Drivers/ANRB-Drivers-20161222.zip
Alan
-
I've tried that driver package as well. I was able to confirm my legacy RadarBox does work from my laptop.
AirNav's response on Amazon has been removed but the answer for another user remains that Windows drivers are not yet available. The FlightStick page https://www.radarbox24.com/tracking-with-your-flightstick has been updated with a spectrum analysis chart and support for Windows is no longer shown. Thanks AirNav team for that. The Radarbox page now points those looking for FlightStick drivers to the MicroRadarbox drivers. These don't work.
-
I will contact them and get back to you. I presume you have the V6 Software to go with it.
Alan
-
I am advised that they are waiting on an update to the driver package by 31st January. I am advised that it works with the existing drivers but some users are having difficulties with it, you being one of them by the looks of it
I presume that you used both the driver packages including http://www.airnavsystems.com/Download/ANRB/Drivers/microRadarbox-Drivers-20150411.exe in addition to the one I mentioned earlier. This one operated the previous stick
Alan
-
Yes - I've installed all three on two system. I'll try another separate device later tonight. On one system, a Surface Laptop, I even reloaded Windows and the software with no change.
Could you talk about the expected experience? I've had the original RadarBox for almost 10 years and very much like the interface. I made some assumptions when I purchased the dongle. First assumption was that I would be able to use the RadarBox app. Is this possible?
-
If you are feeding into the nextwork with any receiver you get a Business Subscription on Radarbox24 including the app. Just need to link your unit to your RB24 account
Alan
-
No luck in getting the dongle to work with RadarBox on 3 devices. One was a fresh load of Windows 10 Pro.
Any further suggestions? Support?
-
AAs has been stated the dedicated drivers will be out within 14 days. [email protected]
Alan
-
Yes unfortunately we will need to wait for the specific Flight Stick Drivers which fingers crossed could be with us by the end of the month. Apologies for the inconvenience caused.
-
Is this discussion about the Flight Stick in the photo below? If so, then most likely driver zadig (https://zadig.akeo.ie) should work.
With Air Nav RadarBox ver 6.01.001, I could successfully used DVB-T with driver zadig.
I have ordered Radarbox FlightStick, and waiting delivery. Will try with driver zadig when it is delivered.
(https://i.postimg.cc/7LFPWMyh/radarbox-flightstick.jpg)
.
DVB-T + driver zadig, with Air Nav Radar Box ver 6.01.001
The DVB-T was detected by AirNav Software as "MicroRB"
(please see bottom-left corner of the screenshot)
(https://i.postimg.cc/wjzXpQ37/AirNav_RadarBox_-_6.01.001.png)
-
For me and after install zadig drivers, the RadarBox Flightstick don't work with V6.02.003 and is not detect by rtl1090 (jetvision) over Silex Wireless USB Hub (SX-DS-3000WAN).
Before that Radarbox Flightstick shutdown RB application.
With airnav drivers I hope that this will work like RadarBox 2009 or Xrange2.
Best regards
-
Is this discussion about the Flight Stick in the photo below? If so, then most likely driver zadig (https://zadig.akeo.ie) should work.
With Air Nav RadarBox ver 6.01.001, I could successfully used DVB-T with driver zadig.
I have ordered Radarbox FlightStick, and waiting delivery. Will try with driver zadig when it is delivered.
(https://i.postimg.cc/7LFPWMyh/radarbox-flightstick.jpg)
.
DVB-T + driver zadig, with Air Nav Radar Box ver 6.01.001
The DVB-T was detected by AirNav Software as "MicroRB"
(please see bottom-left corner of the screenshot)
(https://i.postimg.cc/wjzXpQ37/AirNav_RadarBox_-_6.01.001.png)
Tried allready for a couple of hours with these drivers and programs.
Computer recognizes the stick, zadig worked always in the feature for my other SDR dongles.
No result with this one.
I can't even open the help or find a setup hardware in the program....
No much help on these online...
-
allright.
Will defenitly need some help.
tried so far:
*installed all drivers i could find or get suggested
*zadig always worked for me in the past, al my other RTL2832 stick are still happy chooching while i plug and unplug them
*Installing (2 times) the latest version of airnav (extreme slow download, btw) 6.02.003
*tried other computer
The computer seems to recognize the stick as RTL2838UHIDIR but software doesn't
Tried with SDR sharp and also no device found.
Need some help, living in a flightlane hearing the planes mocking ;-)
thx in advance
-
See reply No 9 above
Alan
-
I received my Flightstick yesterday, plugged it into my laptop and it worked straight away with no need to do anything
I have the normal radarbox drivers, the microradarbox and Zadig drivers installed so don't know which ones do for it but the stick declared itself s a microRB on the start up splash screen so presumably it needs the micro radarbox driver or Flightstick drivers as they are now named on the software page http://www.airnavsystems.com/Download/ANRB/Drivers/microRadarbox-Drivers-20150411.exe
Alan
-
Alan,
was the Zadig drivers, I have tried with all of them and only zadig works.
But today is 31 of January, the day of drivers release from airnav.
Lets see....
Regards
-
All I know is that I plugged the Flightstick in and it worked with no problems. I have the Radarbox, MicroRadarbox and Zadig drivers in my drivers folder to allow my different receivers to work with V6.
As for dedicated Flightstick drivers from Airnav today, lets see!!
Alan
-
Could you take a look in Device Manager and report back which drivers are being used? Right-click on the device and choose Properties Then choose the Driver tab and finally click the Driver Details button, I've attached an image of how my system reports the device, basically a Realtec 2832U device
-
As far as I am aware its the micro RB drivers in use,see attached. Its the same as my main computer which has the MicroRB plugged in
Alan
-
@richk107
You should run Zadig and replace driver for USB stick. Your drivers were installed by Windows and are incompatible with ADSB apps
-
DRIVER
No special driver installed
Only Zadig was existing (was previously installed for DVB-T)
(https://i.postimg.cc/zfymwtR2/Flight-Stick-1.png)
SETUP
(https://i.postimg.cc/3RrvbGYq/Flight-Stick-2-R.jpg)
Detected As MicroRB
(https://i.postimg.cc/7LdFK33H/Flight-Stick-3.png)
STATUS As on February 01, 2019 at 03:41 AM Local Time (08:41 UTC)
(https://i.postimg.cc/yYWNxHV2/Flight-Stick-5.png)
-
Anyone heard a new ETA for the Windows driver?
Thanks
M
-
Suggest you ask support, but the Flightstick is working ok without them as you can see above
Alan
-
Thanks Alan - unfortunately one of my systems is not recognizing the stick and I'd rather have the real deal than futz about with it any longer!
Mark
-
Do you have the Zadig drivers installed?
Airnav are the only ones who can advise so suggest you drop them an email to try and find out
Alan
-
Yup - I have two Win10 machines; Zadig works fine on one but on the other the stick is ot appearing
Have pinged Support and will share response here
Thanks again Alan
M
-
TEST FOR DRIVER
Windows 10 often detects two dongles:
(1) A false dongle as device 0
(2) The real dongle as device 1
The false dongle causes the problem which many user are facing on Win 10
To see what dongle your Win 10 detects, carryout following test:
STEP-1
Download RelWithDebInfo.zip from here:
Download Link: http://osmocom.org/attachments/download/2242/RelWithDebInfo.zip (http://osmocom.org/attachments/download/2242/RelWithDebInfo.zip)
Web Page: https://osmocom.org/projects/sdr/wiki/rtl-sdr (https://osmocom.org/projects/sdr/wiki/rtl-sdr)
(scroll down to bottom of page to find download link)
STEP-2
Unzip the downloaded folder and move in the un-zipped folder "RelWithDebInfo/rtl-sdr-release/x64"
In this folder you will see many files. Please see screenshot below.
(https://i.postimg.cc/k5fgCkfg/Flight-Stick-Windows-Test-1.png)
STEP-3
When inside folder "RelWithDebInfo/rtl-sdr-release/x64", double-click file "rtl_test.exe"
(a) If Windows has picked only the real dongle, you will see following
Tested in Win 8
(https://i.postimg.cc/mDwBfDWn/Flight-Stick-Windows-Test-2.png)
(b) If it has picked false dongle, you will see following:
Found 2 device(s):
0: T■, ©■, SN: T (currently selected)
1: Realtek, RTL2838UHIDIR, SN: 00000001
usb_open error -12
Error opening the RTLSDR device: No error
EDIT:
Tested in Win10 home
(1) In Win10, in STEP-3, got error message "Missing MSVCR100.dll".
Solved by method given here:
https://social.technet.microsoft.com/Forums/en-US/a38df7a2-7b9f-4db5-bc15-be8b700b3636/windows-10-msvcr100dll-missing?forum=win10itproapps (https://social.technet.microsoft.com/Forums/en-US/a38df7a2-7b9f-4db5-bc15-be8b700b3636/windows-10-msvcr100dll-missing?forum=win10itproapps)
(2) Opened Command prompt
- Change to folder "Downloads/RelWithDebInfo/rtl-sdr-release/x64".
- Gave command "rtl_test -t".
- Got error.
Please see screenshot below:
(https://i.postimg.cc/4yxZJgJx/Flight-Stick-Windows-10-Test.png)
-
Just had an email from the developer, they are still working on the dedicated drivers
Alan
-
Yesterday I received FlightStick
First tested on Win8 then later on Win10
- Win 8 has no problem of driver
- Win 10 has problem of driver
See my post above (Reply #27 (https://www.airnavsystems.com/forum/index.php?topic=20981.msg344571#msg344571))
-
Mines is working on Windows 10!!!
Alan
-
Mines is working on Windows 10!!!
Alan
Seems Windows 10 has erratic behaviour.
Works Ok in some installs and fails in some installs. :(
-
Appears to be the case
Alan
-
I got another idea:
May be Win10 does not treats all USB ports equally.
To test this, on my PC, I will plugin the FlightStick in all the USB ports one by one and see if Win10 can pick the FlightStick on any of the USB ports.
I am not at home now, so cannot test it. Will test tonight:
-
I have this.
(http://)
-
Ok, I think I have this nailed down.
On my one system I was able to very easily switch to the WinUSB driver using ZADIG but on my other two system I completely failed. ABCD567’s post reminded me that these RTL devices should be treated as a composite devices and the ZADIG needs to replace the driver for the composite, not the two individual devices.
Normally, the FlightStick will show as two devices in Device Manager. If the automatically downloaded drivers from Microsoft are used the Flightstick will be seen as a HID Infrared Remote Receiver under Human Interface Devices and as a Realtek 2832U device under Sound, video and game controllers.
(https://i.postimg.cc/njzLVLss/Device-Man1.png) (https://postimg.cc/njzLVLss)
(https://i.postimg.cc/0rzNLbRF/Device-Man2.png) (https://postimg.cc/0rzNLbRF)
The trick to getting this to work is of course ZADIG.
1. Download Zadig. https://zadig.akeo.ie/
2. Run ZADIG as Administrator
3. IN Options -- Check "List all Devices" , UNCHECK "Hide Hubs or Composite Devices"
(https://i.postimg.cc/gxHcvh8X/Zadig-settings1.png) (https://postimg.cc/gxHcvh8X)
4. From the drop down, look for the composite device RTL2838UHIDIR (Composite Parent)
(https://i.postimg.cc/75kYG9Gr/Zadig-settings2.png) (https://postimg.cc/75kYG9Gr)
5. Change the Driver of the COMPOSITE Driver to WINUSB, press the “Replace Driver” button
(https://i.postimg.cc/3yLKqHL3/Zadig-settings3.png) (https://postimg.cc/3yLKqHL3)
(https://i.postimg.cc/5jDt1bf0/Zadig-settings4.png) (https://postimg.cc/5jDt1bf0)
(https://i.postimg.cc/WDpNS4w9/Zadig-settings5.png) (https://postimg.cc/WDpNS4w9)
(https://i.postimg.cc/ZBCTtDgp/Zadig-settings6.png) (https://postimg.cc/ZBCTtDgp)
6. The 2 previously mentioned devices will disappear from Device manager and the new RTL2838UHIDIR device will appear under Universal Serial Bus Devices
(https://i.postimg.cc/k6pg2d8T/Device-Man3.png) (https://postimg.cc/k6pg2d8T)
7. Reboot.
8. Start RadarBox and your FlightStick should be discovered.
(https://i.postimg.cc/3dpxxVwZ/RB1.png) (https://postimg.cc/3dpxxVwZ)
(https://i.postimg.cc/ZvvK3Dx4/RB2.png) (https://postimg.cc/ZvvK3Dx4)
-
@Runway 31
@richk107
You two have succeeded with zadig on Win10.
I and many others have failed.
I have Win10 Home, and failed.
Which version of Win10 you have?
Win10 comes in 3 versions
(1) Win10 Home
(2) Win10 Pro
(3) Win10 Enterprise.
-
Win10 home. As stated I plugged in the stick started up V6 and away it went. I already had the software and drivers installed for use with my Micro RB and NooElec dongles
Alan
-
2 with Win10 Pro - 1 Desktop and the other a Surface Laptop. The other is running Win10 Home, Surface Go. All three recognize the dongle now along with RB6
-
@abcd567 - Do you see the composite device when you uncheckmark "Ignore Hubs or Composite devices" in ZADIG? What happens when you try to apply the WinUSB driver to that device? Keep in mind that if you tried to apply WinUSB to the bulk devices, you should first uninstall the drivers for each device, the ones I listed in my previous post, and have Windows rediscover the devices after a reboot
-
@richk107
Thanks for providing detailed guide with screenshots.
(1) I uninstalled all the USB Hub devices, then rebooted Win10, then installed Zadig.
(1) When I uncheckmarked "Ignore Hubs or Composite devices" in Zadig, I could see Composite USB device RTL2838UHIDIR, and I selected it for driver installation in Zadig.
I tried your method several times, but Windows 10 is extremely stubborn, and all my attempts failed.
-
@richk107:
SCREENSHOT 1 of 2
(https://i.postimg.cc/L5MDJkp4/Flight-Stick-Win10-Zadig-6.png)
.
SCREENSHOT 2 of 2
(https://i.postimg.cc/Y0f3Y4r6/Flight-Stick-Win10-Zadig-9.png)
-
Here is what the Zadig installer is showing with my stick
-
Here is what the Zadig installer is showing with my stick
After I clicked "Replace driver"in zadig installer, WinUSB driver was installed and my zadig display became exactly like yours, but in the "Windows Device Manager" there is a caution mark besides the dongle (see 2nd screenshot I have posted), and the AN software does not detect the dongle.
-
What shows when you right click it
Alan
-
What shows when you right click it
When I clicked the icon of "RTL2838UHIDIR" in "Device Manager", and selected "Properties", I get what is shown in attached screenshots
-
Did you contact support for advice and if so what was their advice
Alan
-
Did you contact support for advice and if so what was their advice
Alan
No, I did not, and dont plan to do so. The problem is not specific to FlightStick. On Win10 I tried to install Zadig for Flightaware Pro Stick, and that also failed, exactly same error for both. It is Windows10 which is rejecting installation of driver by Zadig.
I have tried FlightStick, ProStick, and DVB-T on Win8, and zadig successfully installs driver, and no error messages are there.
-
OK, wonder why it is accepted on some W10 systems and not others.
I suppose the next issue will be the next W10 update and all the USB drivers are overwritten again as usual
Alan
-
abcd567 - Can you provide more info about your Window install? Can you can supply this: (https://i.postimg.cc/MGkrG0zJ/Capture.png) (https://postimages.org/)
which is found by accessing Settings >> System >> About. Please cross out the same information from your screenshot.
Just a check list of what I did to get it to work:
- When you run ZADIG, do you run it with Administrator rights?
- When you uninstalled the Flightstick thru Device Manger, you uninstalled both devices. HID Infrared Remote Receiver under Human Interface Devices and as a Realtek 2832U device under Sound, video and game controllers.
- When uninstalling, you checked off "Delete the driver software for this device"
- If you device is displayed as a Bulk-In device" I would recommend deleting both devices it twice. Delete the Bulk-in, have Windows rediscover as HID Infrared Remote Receiver and Realtek 2832U ad then delete this two again. I had to do this step on my Surface.
-
@richk107
Please see attachment for info you requested.
-
@abcd567 - can you run Windows update and bring you up to the latest build? 1709 is over a year old.
-
@abcd567 - can you run Windows update and bring you up to the latest build? 1709 is over a year old.
When I made my last post, I have already realized that mine is 1709 & yours is 1809 :), and have already run updates thrice. Every time Win10 downloads few updates, run "restart", and the few downloaded updates are installed.
I think I have to repeat this process several times more till there are no more updates left to download & install
-
Depending on how many updates behind you install has, I believe you might need a minimum amount of fixes applied before 1809 is installed. You might want to note the KB numbers being installed to verify that they are being applied and not some generated internal error isn't cancelling the install.
-
this has been like a car sales man selling me a car with out the wheels...… why would you sell something that you would have to go to the crap yard to get the wheels..... the majority of people who buy this should not have to frig about to get it to work...… poor
-
this has been like a car sales man selling me a car with out the wheels...… why would you sell something that you would have to go to the crap yard to get the wheels..... the majority of people who buy this should not have to frig about to get it to work...… poor
The problem is NOT with FlightStick.
The root case of problem is Windows 10.
I concluded this after I tried 3 different dongles on Windows 10, and all 3 were showing driver problem.
RadarBox24's FlightStick
FlightAware's Pro Stick
Generic DVB-T
It is also NOT software problem. I tried AirNav, dump1090-win32, and rtl1090. None picked any of the above 3 dongles.
On the other hand, all the 3 dongles mentioned above work perfectly well with all the 3 software mentioned above on Windows 8
Conclusion:
Source of problem is Windows10, and not any of the dongles or any of the softwares.
-
Due to failure of Windows 10 to let dongle driver Zadig do its job, I have started using FlightStick on Raspberry Pi and feed RadarBox24 using linux feeder software "rbfeeder". The FlightStick is performing excellent with RPi.
I also tried FlightStick on Ubuntu 18.01 on my PC, and FlightStick gave excellent performance, though I cannot feed RadarBox24 as they dont have linux x86 software (only arm for Pi). I however could feed Flightaware & Flightradar24 from Ubuntu 18 on x86 PC.
-
I will have to disagree. While not the optimal solution to this problem, AirNav should have had a driver ready for the product, this isn't a Windows problem. I suggest that this is an issue with Zadig and its inability to install the driver or the copy of the WinUSB driver on your system. You proved this by not being able to utilize 3 different DVB-T type dongles, all that rely on the WinUSB generic driver. Windows is installing the driver for the chipset it sees, the Realtek 2832U chip. The drivers that everyone uses for SDR, in our case for ADS-B, is not exactly what the chip was designed to do. Windows installs the Realtek drivers, we are trying to substitute a generic driver in its place. If that driver is failing to load, then blame the driver.
-
Agree with Rick to a certain extent. Zadig drivers are used to convert capable television sticks, the main use for the Realtek chips to 1090Mhz use and the drivers should have been ready and tried and tested before releasing the stick
What I cannot understand is why some users cannot get the Zadig drivers to load. I have been using the Zadig drivers with my NooElec stick for some time and have not had any issues and all I had to do with the Flightstick was plug it in and away it went.
Alan