the windows zip includes SoapySDR.dll (the core SoapySDR 0.8.1 library) but no radio driver modules, so -i soapy can't find any devices until you install a module for your radio. SoapySDR loads modules from <extracted-zip>\lib\SoapySDR\modules0.8\ (create that folder next to bin\ and drop the module DLL in), or from any folder you list in the SOAPY_SDR_PLUGIN_PATH environment variable.
the "module version" you're seeing is the SoapySDR ABI: our DLL is the 0.8.1 release (ABI 0.8), so the module must be built against a 0.8.x release too. modules from bundles built off SoapySDR git master (e.g. PothosSDR, which uses modules0.8-3) won't load against it - SoapySDR skips them with an ABI-mismatch warning. also note the module's own dependencies must be installed (e.g. SDRplay's API/service for sdrplay_api.dll).
i've added a Windows section to the SoapySDR guide with the full details: docs/soapysdr.md, section 0a. general usage (-i soapy, soapy_args, device settings) is in the same doc.
dsd-neo/docs/soapysdr.md at main · arancormonk/dsd-neo
eventually i should just include native support for the popular sdrs, but all i have is an rtl-sdr right now... but might be able to leverage sdrpp or others and just copy and pray it works until someone complains...
Didn't mean to abandon your helpful info. A bit overwhelming not speaking 'programmerese' fluently. And didn;t want to ask a bunch of seemingly stupid questions. So been reading and researching here and there.
I never have found a clear explanation of what the "Module <version>" actually is. Python? Something else?
And would a 0.8 version also be compatible with 0.8.1? I see several SDR applications that not only include SoapySDR.dll. But also a modules 0.8 directory (folder). In the Windows version of Neo I don't believe see a modules folder. And the included .dll drivers reside in the root of the program. It was your mention of SoapySDR ABI and thought it was a typo. Until I saw API also. Going through your reply paragraph-by-paragraph trying to digest the info.
And at this point, not so sure another thread would be a better place to keep from cluttering this one.
The dev. of SDR++ made a soapy 0.8 module from a 0.7 older one. Partially functional with my radio. But full of glitches and program crashes.
Good concept. And a busy guy too. I didn't want to bug him. Older versions of the program worked.
And other SDR apps that do use compiled 0.7 and 0.8 modules seem blind to my drivers.
I'm almost 100% positive that I'm not using SoapySDR correctly. I was under the assumption that having it and a driver "just works".
That is because in some instances where the driver is not included in the modules (or program root) folder, it works.
Is it possible that the main SDR program is hard coded to use only a certain set of drivers and ignore anything else?
I waited to reply so as to not sound dumb. But definitely a kindergartener probably trying to dive into college level subjects.
I see that AOR receivers are now implemented in some SDR programs that didn't, couldn't use them previously.
Pothos linked a Soapy forum that for years is filled with spam. Not actually looking how to clean a sink or build muscles or 'keep the xyl happy'.
And not looking for a fish to be given to me. I want to learn how to fish. If that makes sense.
I looked for online and installable .dll decompilers. Opened a RTL SDR driver alongside of my factory one and saw many, many similarities.
Revealing that my radio is an Icom IC-R8600 now. Was told I need an API. Icom responded with a blank stare in support emails.
Not sure how SDR drivers function over USB. But If I have (do) the programming manual with all of the various commands that the radio uses in the I/Q port. Which is what I suspect that any other SDR radio uses even though most just consider it "The USB Port".
Why couldn't a person plug those commands into a program and puke out a working .dll?
Heard of a SoapySDR "constructor". Haven't found one. Nor am sure what using one would entail. Four years of college?
Good reply and questions? Hope so.
Unless I'm doing something not documented. I see even SDR# won't any longer let me use my SDRPlay RSP2 with newer versions.
I'll keep reading and trying to learn what I can. So much is just way over my head. A "SoapySDR Constructor" would have me believing there is a console or GUI with places to enter (or prompts) what is the baud rate command string, what is tune up/down string, etc.
Press make and start debugging in the SDR application.
I even have some SoapySDR source code for my radio. If Icom didn't release it. Where would that have come from? And if it's source code, what would prevent any modules version being built from it? Yaaaaa! haha
