SDRplay Community Forum

Hi,

Arch Linux - SoapySDR cannot find sdrplay modules.

Press y and RETURN to accept the license agreement and continue with
the installation, or press n and RETURN to exit the installer [y/n] y
Architecture: x86_64
API Version: 2.11
Remove old libraries...
Install /usr/local/lib/libmirsdrapi-rsp.so.2.11
Remove old header files...
Install /usr/local/include/mirsdrapi-rsp.h
Udev rules directory found, adding rules...
Libusb found, continuing...
Finished.
[djringjr@n1ea-laptop Downloads]$ SoapySDRUtil --find=sdrplay
######################################################
## Soapy SDR -- the SDR abstraction library
######################################################

[ERROR] SoapySDR::loadModule(/usr/lib/SoapySDR/modules0.7/libsdrPlaySupport.so)
dlopen() failed: libmirsdrapi-rsp.so.2.11: cannot open shared object file: No such file or directory
[ERROR] SoapySDR::loadModule(/usr/local/lib/SoapySDR/modules0.7/libsdrPlaySupport.so)
dlopen() failed: libmirsdrapi-rsp.so.2.11: cannot open shared object file: No such file or directory
No devices found!

l am using libusb 1.0.19-1 the regular version for my Linux is 1.0.21-2.

Can anyone be of help?

Thanks
djringjr

Try this...

export LD_LIBRARY_PATH=/usr/local/lib

and then run SoapySDRUtil again.

Best regards,

SDRplay Support

After running the command you supplied I get:

######################################################
## Soapy SDR -- the SDR abstraction library
######################################################

Found device 0
driver = sdrplay
label = SDRplay Dev0 RSP2 1710072010

Also when I was downloading the drivers, I reached a screen asking me the serial number of my device and it presented me with a list of choices, none of which were even close to the serial number on my box.

The serial number sticker came off so I stuck it back on with tape.

In any event this was the file I installed:
SDRplay_RSP_API-Linux-2.11.1

Thanks for helping but something is still wrong.

David djringjr

I also downgraded lib32-liblsb.

multilib/lib32-libusb 1.0.21-1 [installed: 1.0.19-1]

So now libusb and lib32-libusb are both 1.0.19-1 and no longer 1.0.21-1.

I get the same results.

$ SoapySDRUtil --find=sdrplay
######################################################
## Soapy SDR -- the SDR abstraction library
######################################################

Found device 0
driver = sdrplay
label = SDRplay Dev0 RSP2 17100720


Found driver but no device.

The device is plugged in.

David

I'm not sure why you think this isn't working? Looks ok for a --find output to me. Try...

SoapySDRUtil --probe=sdrplay

to get more info about your device.

Best regards,

SDRplay Support

$ SoapySDRUtil --probe=sdrplay
######################################################
## Soapy SDR -- the SDR abstraction library
######################################################

Probe device sdrplay

----------------------------------------------------
-- Device identification
----------------------------------------------------
driver=SDRplay
hardware=1710072010
mir_sdr_api_version=2.110000
mir_sdr_hw_version=2

----------------------------------------------------
-- Peripheral summary
----------------------------------------------------
Channels: 1 Rx, 0 Tx
Timestamps: NO
Other Settings:
* RF Gain Select - RF Gain Select
[key=rfgain_sel, default=4, type=string, options=(0, 1, 2, 3, 4, 5, 6, 7, 8)]
* IF Mode - IF frequency in kHz
[key=if_mode, default=Zero-IF, type=string, options=(Zero-IF, 450kHz, 1620kHz, 2048kHz)]
* IQ Correction - IQ Correction Control
[key=iqcorr_ctrl, default=true, type=bool]
* AGC Setpoint - AGC Setpoint (dBfs)
[key=agc_setpoint, default=-30, type=int, range=[-60, 0]]
* ExtRef Enable - External Reference Control
[key=extref_ctrl, default=true, type=bool]
* BiasT Enable - BiasT Control
[key=biasT_ctrl, default=true, type=bool]
* RfNotch Enable - RF Notch Filter Control
[key=rfnotch_ctrl, default=true, type=bool]

----------------------------------------------------
-- RX Channel 0
----------------------------------------------------
Full-duplex: YES
Supports AGC: YES
Stream formats: CS16, CF32
Native format: CS16 [full-scale=32767]
Antennas: Antenna A, Antenna B, Hi-Z
Corrections: DC removal
Full gain range: [0, 47] dB
IFGR gain range: [20, 59] dB
RFGR gain range: [0, 8] dB
Full freq range: [0.01, 2000] MHz
RF freq range: [0.01, 2000] MHz
CORR freq range: MHz
Sample rates: 0.25, 0.5, 1, 2, 2.048, 6, 7, 8, 9, 10 MSps
Filter bandwidths: 0.2, 0.3, 0.6, 1.536, 5, 6, 7, 8 MHz

But when I do this:

SoapySDRUtil --find=sdrplay
######################################################
## Soapy SDR -- the SDR abstraction library
######################################################

Found device 0
driver = sdrplay
label = SDRplay Dev0 RSP2 1710072010

It doesn't find a device.

By the way, what is the SDR program I should be using?

I Installed CubicSDR from Arch Linux sources.

Regards,

djringjr

--probe and --find have both reported exactly what they should and the device has been found in both instances. As I said before, I'm not sure what you are seeing to make you think this isn't working?

Yes, CubicSDR works with SoapySDR devices.

Best regards,

SDRplay Support

Found device 0
Means that it found instance 0 (the first device) NOT that it didn't find any device. It does find the device and assigns it instance 0. I realise that this can be a bit confusing.

All is good here

Sincerely

SDRplay Tech_Support

Thank you, yes, I did misunderstand that. I also tried to run cubicsdr and it would not work but I continued to follow the non-Windows Flow documeent and rebuilt wxwidgets - that was what was needed.

There are quite a few errors in that document.

One thing that would help many would be to have the flags for wxwidgets restated like this:

./configure --with-opengl --disable-shared --enable-monolithic --with-libjpeg --with-libtiff --with-libpng --with-zlib --disable-sdltest --enable-unicode --enable-display --enable-propgrid --disable-webkit --disable-webview --disable-webviewwebkit --prefix=`echo ~/Dev/wxWidgets-staticlib` CXXFLAGS="-std=c++0x"


Also there are some errors that we call tend to make like "make install" instead of "sudo make install" but this would cause a new comer to fail when it's important to have clear instructions.

I now wish I had kept track of the errors that I found - one was that when descending to the build subfolder, either the configure or make command had ./ instead of ../ or vice versa. I forget which.

Thank you for the help, it's working and now I won't have to return this excellent piece of hardware!

Regards,

David J. Ring, Jr., N1EA

Where can I put:

export LD_LIBRARY_PATH=/usr/local/lib

so that not only commands issued from a terminal will know where to look but also when I click on CubicSDR in the graphical menu (I am running KDE).

I have the above line in my ~/.bashrc file.

There have been so many changes recently with Linux start up files I don't know where to put it for global use on startup.

Thanks again, I'm 99.999 percent there.

This answer will put me over the goal post.

Best to you,
David