Closed thehose closed 6 years ago
Will try to take a look at it for the 2.7 release. Any more info and data is of course welcome :-)
Absolutely, I’ll keep poking around and if anything comes from that I’ll let you know. I’m expecting a LimeSDR at the end of this year (?) and then I’ll switch to that device and put the dongle to eternal rest.
On Sep 8, 2016, at 3:28 PM, Alexandru Csete notifications@github.com wrote:
Will try to take a look at it for the 2.7 release. Any more info and data is of course welcome :-)
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/csete/gqrx/issues/406#issuecomment-245761794, or mute the thread https://github.com/notifications/unsubscribe-auth/ALn1T9pTXdxfwYEUE_MNvCWCOucPp3I_ks5qoIwWgaJpZM4J4f2K.
Hi,
I just tried using SoapySDRServer with the LimeSDR and RTL-SDR and it works. The device string I used was:
soapy=0,driver=remote,remote:driver=lime
and
soapy=0,driver=remote,remote:driver=rtlsdr
respectively.
So, it appears to be working with the latest software.
How can i specify the address of the soapyRemoteServer?
soapy=0,driver=remote,remote=<ip_address_or_hostname>,remote:driver=<remote_driver_name>
I'm attempting to connect to a remote rtl_sdr dongle running on a SopySDRServer. It works well when using osmocom_fft with these device strings:
"soapy=0,driver=remote,remote=sdr" "soapy=0,driver=remote,remote=sdr,remote:driver=rtlsdr"
When I try with gqrx (2.5.3) I does not connect and the server shows no connection attempted. Attached is the conf file used. Soapy_RTL_SDR.txt
PS: I have the SoapySDRServer installed and working. I would be glad to run any test's you may need in order to debug this issue.
Hose