Closed cdbrinker closed 2 years ago
The soapy source doesn't support bias-t remote or not. SoapySDR doesn't have a standard way of enabling bias-t.
Also I'll add that his sounds more like a gain issue, I doubt any SDR would have trouble receiving broadcast FM with its gain set correctly
The soapy source doesn't support bias-t remote or not. SoapySDR doesn't have a standard way of enabling bias-t.
Not sure I understand. I can enable bias-t (or FM notch, DAB notch, etc) on CubicSDR via a remote Soapy server. So is there specific support in CubicSDR for my RSP1a that is not present in SDR++?
Just to clarify, the reception in SDR++ via Soapy remote is exactly the same on all bands as with bias-t disabled in CubicSDR via Soapy remote. So, in my situation, without bias-t, I basically only receive FM stations.
I suspect cubic has a list of SDRs and their option name to enable bias-t, then it uses that to enable or disable it. The soapy source in SDR++ is completely device agnostic. Not sure what I can do without manually checking for every device type which would defeat the purpose of the soapy source.
I think I might be able to add a custom device arg field to the soapy source, but you'll have to type in the right soapy args for it to turn on the bias-t
I don't think Cubic has a list of SDRs, everything is dynamic.
In Soapy driver, there is function to get device options (if avaliable), it's called getSettingInfo() For SoapySDRPlay3 driver, line 1085 https://github.com/pothosware/SoapySDRPlay3/blob/master/Settings.cpp But other drivers may have too with other options, depending of the hardware specifications, driver implementation.
And there is a writeSetting() line 1343 and readSetting() line 1533. The issue I think is to generate device settings dynamically to provide it on the GUI.
Hope this can help
Checked SoapyAirspy driver, https://github.com/pothosware/SoapyAirspy/blob/master/Settings.cpp line 363, there is a getSettingInfo() too and writeSetting() line 390 + readSetting() line 408.
So it seems there is a standard way to get device options from a soapy driver.
Connects to remote computer hosting the rsp1a and pipes in the signal just fine but no way to enable bias-t. I can get strong FM stations poorly, the rest of the bands are just white noise. Did I build incorrectly? When running on the rsp++ machine with the SDRPlay source, no problems. CubicSDR has no trouble with Soapy on these two machines and even enables the bias-t by default.