-
Notifications
You must be signed in to change notification settings - Fork 23
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
SoapySDR Enumerate still finds Pluto after being unplugged #66
Comments
The code is here: https://github.com/pothosware/SoapyPlutoSDR/blob/master/PlutoSDR_Registration.cpp#L10 Not great at all. I imagine newly added devices will also not show up if at least one device was discovered once. Can you try to remove The caching was added with a3dcbd3 and we should also check if the |
Removing those lines did not work, that is I still see the device after being unplugged.
|
Sorry, one more line of changes is required: |
That did the trick!
For reference, the code looks like this now:
Thanks for the pointers! |
Thanks for testing! Let's keep this open as it really needs to be fixed, the behaviour right only works for one fixed device. |
I am testing some code to detect when a Soapy-compatible SDR is physically unplugged and to remove it from an internal list. This works for an RTLSDR and HackRF, but the Pluto continues to be recognized by the
SoapySDR.Device.enumerate()
call.Host: BeagleBone Black
Debian 9 (I know it's old, but our stack is locked to this)
dmesg
output:Here is code that replicates the problem:
Code output (showing the RTL being detected, then removed, then the pluto being detected but not removed). Newlines were added to distinguish physical events.
The text was updated successfully, but these errors were encountered: