airspyone_host VS libwdi

As far as assembling an SDR from discrete parts, you can check out the MCHF kit or Asher Farhan's sbitx. Great radios, but nothing like the value prop of the RTL-SDR. If you're just looking for a cheap radio to listen with, I'd recommend Airspy.

I am not sure whic library is good for your R2, but it should be tthis one: https://github.com/airspy/airspyone_host

SPY Server v2.0.1822 Copyright (C) 2016-2021 Youssef Touil - https://airspy.com Reading the configuration file: spyserver.config Listening for connections on 192.168.1.52:5555 Accepted client 192.168.1.2:62918 running SDR# v1.0.0.1909 on Microsoft Windows NT 10.0.22621.0 Device was sleeping. Wake up! Could not find any suitable device Accepted client 192.168.1.2:62919 running SDR# v1.0.0.1909 on Microsoft Windows NT 10.0.22621.0 Device was sleeping. Wake up! Could not find any suitable device

But look, rtl_sdrs are not a great choice for HF. I would recommend looking at Airspy or SDRPlay if you want to receive HF.

Then there are non-RTL-SDR devices, like devices from AirSpy, some of which use RTL receivers, and some that don't, but present themselves to the computer as a unique device that requires separate drivers and software.

I would try the instructions from https://github.com/airspy/airspyone_host/wiki/Troubleshooting but obviously you're looking for 6msps rather than 10

They probably use WCID, which is a mechanism for devices to tell Windows that they are compatible with the generic WinUSB driver. Zadig is useful for older versions of windows, non-WCID devices, and when you want to override that auto-specified driver.

Here's more information from the author of Zadig: https://github.com/pbatard/libwdi/wiki/WCID-Devices

If you do that'll bring you here where you'll find everything you ever wanted to know about WCID.

Using this config files from zadig's github page, it (in my case) got all the correct settings from the start and all I need to do is click replace driver. Place the zadig.ini files in the same directory as your zadig.exe. You might have to choose the correct device.

USB descriptors are supported only up to 8.1 according to your link. And libwdi/zadig is useful links for me, thank you very much! I'll be used ones in my other projects. But I don't need to new USB driver in Windows due to I'll get much more problems with put all together in LabView. I want to use standard WIndows USB-Serial that always present and directly supported via VISA. The NI-VISA isn't using specific protocols for USB. The VISA is just an intermediate level for most of the serial protocols in the NI ecosystem. I'm operating low-level USB packets, commands, responses in the same manner as in C for example but from LabView. But I have to generate the specific INF file which needs for recognition of VISA for each one of the specific instances with a unique USB PID/UID. The problem is mandatory signing such INF files in Windows10 and I'm looking for any way to avoid this.