SoapySDRUtil doesn't detect SDRPlay RSP2 about soapysdrplay2 HOT 15 CLOSED

https://github.com/pothosware/SoapySDRPlay - Requires the API from SDRPlay, you have that installed already? "Get SDR Play driver binaries 'API/HW driver v2.x' (not v3.x) from - http://sdrplay.com/downloads"
HTH
PS - best place for questions like this would be https://groups.google.com/d/forum/pothos-users

from soapysdrplay2.

Yes, those drivers are installed. It wouldn't even build without them. Happy to post in the group - I was told to log an issue in #pothos on freenode...

from soapysdrplay2.

@rich0 I was under the impression that SoapySDRUtil --probe was printing the output for the sdr play, its basically just calling into the null device and printing diddly. Ex, if you SoapySDRUtil --probe="driver=sdrplay", I think you will get a error message. That doesnt help much, but its consistently not working, rather than ambiguously instantiating/not enumerating like I thought. So something must be up with the binaries.

from soapysdrplay2.

Here is the output of --probe with the driver. I don't think it is actually enumerating the device, but just displaying the capabilities of the driver itself?

SoapySDRUtil --probe="driver=sdrplay"
######################################################

Soapy SDR -- the SDR abstraction library

######################################################

Probe device driver=sdrplay

-- Device identification

driver=SDRPlay
hardware=SDRPlay
mir_sdr_version=2.130000

-- Peripheral summary

Channels: 1 Rx, 0 Tx
Timestamps: NO
Other Settings:
* Low IF (when available) - Use low IF when available: 0.5MHz SR with 200 and 300khz BW, 1MHz SR with 600kHz BW, 2048kHz SR with 1536kHz BW
[key=use_low_if, default=true, type=bool]
* IF Mode - IF frequency in kHz
[key=if_mode, default=Zero-IF, type=string, options=(Zero-IF, 450kHz, 1620kHz, 2048kHz)]

-- RX Channel 0

Full-duplex: YES
Supports AGC: YES
Stream formats: CS16, CF32
Native format: CS16 [full-scale=2048]
Antennas: RX
Corrections: DC removal, DC offset
Full gain range: [0, 204] dB
TUNER gain range: [0, 102] dB
LNAT gain range: [0, 102] dB
Full freq range: [0.01, 2000] MHz
RF freq range: [0.01, 2000] MHz
Sample rates: 0.222222, 0.333333, 0.428571, 0.5, 0.571429, ..., 8, 9, 10, 11, 12 MSps
Filter bandwidths: 0.2, 0.3, 0.6, 1.536, 5, 6, 7, 8 MHz

If I detach the RSP2 and run the command, I get the same output, though there is a pause of about a second at the start which doesn't happen when the device is attached.

from soapysdrplay2.

Oh there you go, nice output. @SDRplay what would cause the device instantiation to work, but enumeration shows no devices?

from soapysdrplay2.

Can I see the output of lsusb - i.e. what does the system think is connected? The command should be SoapySDRUtil --probe=sdrplay or SoapySDRUtil --find=sdrplay

from soapysdrplay2.

lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 1df7:3010
Bus 003 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

SoapySDRUtil --find=sdrplay
######################################################

Soapy SDR -- the SDR abstraction library

######################################################

No devices found!

SoapySDRUtil --probe=sdrplay
######################################################

Soapy SDR -- the SDR abstraction library

######################################################

Probe device sdrplay

-- Device identification

driver=null
hardware=null

-- Peripheral summary

Channels: 0 Rx, 0 Tx
Timestamps: NO

from soapysdrplay2.

Something doesn't seem right there - I would... "sudo service udev restart" and then disconnect and reconnect the RSP2 - then try again please.

from soapysdrplay2.

I ran (as root) systemctl restart systemd-udevd

There was no change in behavior for --find=sdrplay or --probe=sdrplay

from soapysdrplay2.

and you physically disconnected and reconnected the RSP?

from soapysdrplay2.

Yes - other than the output in dmesg nothing changed:

[ 4748.741722] usb 3-3: USB disconnect, device number 4
[ 4751.173600] usb 3-3: new high-speed USB device number 5 using xhci_hcd
[ 4751.300581] usb 3-3: New USB device found, idVendor=1df7, idProduct=3010, bcdDevice= 2.00
[ 4751.300587] usb 3-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0

from soapysdrplay2.

Actually, one second - that's version 0.6 - that's pretty old - where did you get that from? 0.6 probably only works with 2.11 of the API - have you tried building from the latest published source?

from soapysdrplay2.

I'm using the Gentoo package for soapysdr-0.6.1. It should be using the tagged tarball from github for that version. Do you want me to build from master?

from soapysdrplay2.

I'm pretty sure 0.6 will only work with 2.11 API - 2.13 API will require the latest version of SoapySDRPlay master

from soapysdrplay2.

Indeed, that was it. Built against master for both sdrplay and soapysdrplay, and got this output:

SoapySDRUtil --find
######################################################

Soapy SDR -- the SDR abstraction library

######################################################

libusb: error [udev_hotplug_event] ignoring udev action bind
Found device 0
driver = sdrplay
label = SDRplay Dev0 RSP2 1717021021

I'm not sure if that libusb error matters. It looks like cubicsdr is doing something also - will do some testing but I'm not anticipating further issues. Sounds like we just need another release. :)

from soapysdrplay2.