New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get wrong SDR when specifying serial #191
Comments
You should be fine with specifying only driver, and one unique identifier like serial. "driver" is special in that it actually is used inside of SoapySDR to filter out specific support modules. The rest of the keys are just passed on to be interpreted as the support module pleases. You are right in that you should be able to do this with only serial, but some of the support modules wont respect that, and they will not be filtered out. But in the case of only installing support modules with serial, then this should work. So I suspect there is an issue in SoapyBladeRF in regards to filtering based on serial: https://github.com/pothosware/SoapyBladeRF/blob/master/bladeRF_Registation.cpp#L81 Or libbladerf itself has a bug in the bladerf_devinfo_matches() implementation. |
Thanks Josh, so I'll just specify the I confirm I can get each board properly like that. |
I left an open bug on soapybladerf since it sounds like there is a problem: pothosware/SoapyBladeRF#23 |
I'm not sure how much info we're supposed to provide when trying to connect to an SDR. Simply passing the
index
ordriver
andindex
may not be convenient if you have several boards.I would have expected to be able to just specify the
serial
and get the proper board, but that's not the case.With several Lime SDR connected, everything works as expected.
But then if I connect a Lime Mini, it seems I always end up getting the Lime Mini, even when specifying the serial of a Lime SDR. Using the
driver
andindex
also always returns the Lime Mini.Specifying both the
serial
andmodule
fixes the problem:But then if I plug a Blade RF 2, I can properly get 2 of my Lime SDR, but when trying to access the 3rd one with both
module
andserial
, I'm getting the Blade RF 2 (this was tested with a very recent version of Pothos).Adding the
driver
fixes the problem:I would expect the
serial
to be pretty unique, even between brands, so it would be nice to be able to just specify that.The text was updated successfully, but these errors were encountered: