Support for non default 192.168.2.1 IP-address.

[i4cy]

SoapyPlutoSDR currently only works when PlutoSDR is set to its default factory setting. Can this be made more flexible to allow for other IP-addresses or hostnames?

Many thanks.

[unixpunk]

I don't have this issue. Can you explain how you're using it? I just changed my IP and hostname in config.txt, committed the change, rebooted and I'm still able to use it through CubicSDR, which is using SoapyPlutoSDR as far as I can tell. My plutosdr is v0.28.

[i4cy]

I don't have this issue. Can you explain how you're using it?

The issue I'm experiencing is while using SoapyPlutoSDR with Pothos Flow, explained more in this thread... pothosware/PothosSDR#57

Running CubicSDR with PlutoSDR also works for me also with a non default IP address. I believe CubicSDR uses SoapySDR, but there's no mention of it using SoapyPlutoSDR.

[unixpunk]

I can confirm it does indeed use SoapyPlutoSDR. This is the plugin to SoapySDR that allows the Pluto to work. You'd find that in removing SoapyPlutoSDR that CubicSDR will not show the Pluto anymore. There must be a difference in how the device is being accessed. @jocover will likely need to confirm further. i.e., does SoapyPlutoSDR use the network or usb methods for IIO device access? (Maybe that's completely off base? Maybe it can do both?) I don't use Pothos Flow so I won't be of much help on that.

[guruofquality]

I have this open issue about the timeout: #3

And this is currently the patch I have build PothosSDR with, it resolves the timeout issue, and uses hostname key to specify the ip/hostname which must be specified: https://github.com/pothosware/PothosSDR/blob/master/patches/soapy_plutosdr_network.diff

I dont know what the libiio api looks like to actually enumerate the PlutoSDR if its on the network to discover devices. So the only solution seems to be what the current codebase does, which is to assume its at the default IP and try to talk to it with a timeout.