-
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
Set label when PlutoSDR is USB-connected #48
Conversation
I had a look through other modules, and the commonality seems to be "label" and "serial". The key "device" is used in HackRF, but specifically to identify the hardware type. |
"ADALM Pluto" sounds good to me. I'll update it to that. |
Done. I also updated the PR description with the new output. |
I like it. Let's give this a few days for other users to maybe offer feedback. |
Actually, it looks like the official name is "ADALM-PLUTO", with "PlutoSDR" being the short version: https://wiki.analog.com/university/tools/pluto The
So it would seem that either "PlutoSDR" or "ADALM-PLUTO" would be best. Which of those do you prefer? |
Oops, sorry. That's confusing. I guess "PlutoSDR" would be nicer than "ADALM-PLUTO", if those are the options of "official" names for the hardware. |
Agreed, I like "PlutoSDR" better as well. I'll switch it back. |
10 days have passed with no other feedback. Can this be merged now? |
Thanks! |
No need. It's not my project, just lots of community effort! |
When a PlutoSDR device is connected by USB, SoapyPlutoSDR calculates a label but fails to assign it to the
options
object. This results in PlutoSDR devices being displayed as "Unknown" in Gqrx.I also noticed that the label is generated using a fixed-length buffer and
sprintf
, which is dangerous. I've replaced this withstd::ostringstream
.Finally, I changed the device name to
PlutoSDR
instead ofplutosdr
to match how other devices are displayed.Before:
After: