f4exb / sdrangel

SDR Rx/Tx software for Airspy, Airspy HF+, BladeRF, HackRF, LimeSDR, PlutoSDR, RTL-SDR, SDRplay and FunCube
GNU General Public License v3.0
2.83k stars 429 forks source link

How to connect to remote Soapy server? #1003

Closed synthead closed 2 years ago

synthead commented 2 years ago

I am having a hard time figuring out how to connect to my remote Soapy server. I have SDRangel compiled with Soapy support on Arch Linux, linked to the lib provided by the soapysdr package.

On the client side, I can query the Soapy server just fine:

$ SoapySDRUtil --find="remote=<host>"
######################################################
##     Soapy SDR -- the SDR abstraction library     ##
######################################################

18:06:04.015390 WARN:   xtrxllpciev0_discovery:243 [PCIE] XTRX PCIe driver isn't loaded
Found device 0
  driver = remote
  label = SDRplay Dev0 RSP1A <serial>
  remote = tcp://<host>:55132
  remote:driver = sdrplay
  serial = <serial>

I can also connect to this Soapy server with gqrx without issues. On gqrx, I am using this device string:

soapy=0,driver=remote,remote=tcp://<host>:55132

However, I can't seem to get SDRangel to connect to this server. SoapySDR doesn't show up in the hardware list from Preferences > Devices > User arguments:

image

I can kind of "force" it to use SoapySDR by typing "SoapySDR" into the "HwID" text field, clicking the "+" on the right, then changing the Arg string, like so:

image

From here, after restarting SDRangel, I see this in the sampling device list:

image

However, I get this dialog box when clicking the "play" button with this source:

image

When I click the play button, this line is displayed from the console that I started SDRangel:

2021-09-18 19:14:27.692 (W) FileInput::start: file not open. not starting

What am I doing wrong?

synthead commented 2 years ago

Related to https://github.com/f4exb/sdrangel/issues/583 Related to https://github.com/f4exb/sdrangel/issues/255 Related to https://github.com/f4exb/sdrangel/issues/298

github-actions[bot] commented 2 years ago

This issue is going to be closed due to inactivity

kevinelliott commented 2 years ago

I can't get this to work either.

synthead commented 2 years ago

Any thoughts? I am trying the software again in case this is fixed, and I'm still running into trouble.