On 2021-10-13 4:20 p.m., Jeff Long wrote:
This is a LimeSDR Mini.
I think the complaint is about the fact that auto-discovery
of Lime doesn't work? Not sure.
To me, auto-discovery is fraught with issues, and I have
*NEVER* in the 17 years I've been
using Gnu Radio relied on it.
But more disturbing to ME is that the attached screen-cap
seems to indicate that the Soapy blocks
are all *device* specific. This seems wayyyy broken to
me. It means you cannot have an application that
is device agnostic. We have had device-agnostic apps for
a LONG time--ever since gr-osmosdr came onto the
scene and then again when SoapySDR showed up. We're going
back to device-specific source blocks? WHY????
Hail,
My rtl-sdr soapy source block runs with attached
hardware but
running the flow graph with the lime source block
throws out the
unpleasant response:
File "./test39_lime-sdr.py", line 88, in __init__
stream_args, tune_args, settings)
RuntimeError: SoapySDR::Device::make() no match
> SoapySDRUtil --find="driver=lime"
######################################################
## Soapy SDR -- the SDR abstraction library ##
######################################################
Found device 0
addr = 1d50:6108
driver = lime
label = LimeSDR-USB [USB 3.0] 9081C05C4212E
media = USB 3.0
module = FX3
name = LimeSDR-USB
serial = 0009081C05C4212E
--init--
self.soapy_limesdr_source_0 = None
dev = 'driver=lime'
stream_args = ''
tune_args = ['']
settings = ['']
self.soapy_limesdr_source_0 =
soapy.source(dev, "fc32", 1,
"driver='lime'",stream_args, tune_args, settings)
I don't know why the dev_args input of "driver='lime'"
is required.
git branch gnuradio 3.9-maint
built with PyBOMBS (on 2021-10-09)
opensuse Leap 15.2.
The web page https://wiki.gnuradio.org/index.php/Soapy
was informative
but didn't tell me where to go next with this. Before
I begin the
daunting (for a non-developer) task of exploring more
deeply, I thought
to query this forum for obvious suggestions or known
solution (or bug
status).
Rick