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
Adalm pluto via ethernet not found #1317
Comments
Show logs |
Libresdr is a derivative of plutosdr. Even it is compatible with PlutoSDR, its signature is different : for example, model is ""LibreSDR Rev.5 (Z7020/AD9363)"" and not "Analog Devices PlutoSDR Rev.B (Z7010-AD9364)" . Same behaviour with Antsdr. Propose solution is to be less strict and just show a warning here :
|
@F5OEO It's why I'm asking for logs to check if it was being rejected, But no, you can't just put a warning there. PlutoSDR & derivatives aren't the only thing that use IIO, here is a concrete example of the wrong device being shown when this check was not in place: |
I've got an AntSDR on the way, should get it thursday, will experiment with things like that and see what works best. |
Ok so it looks like iio itself isn't even finding the device, You can check that by running
There is not, the point of switching to auto discovery is to fix the hack that was to force users to manually specify an IP and have proper support for per-device settings. |
Alright it seems the issue is the version of IIO shipped with the windows build is missing network autodetection for some reason. I guess this will only be fixed once I move to my own build of it... Stay tuned I guess |
Hi, I'm using LibreSDR (aka PlutoSDR) and I'm seeing the same error - SDR++ doesn't find the device Debian 12 log:
The same thing happens in Win10 Version 1.0.4 finds the device well |
First, version 1.0.4 doesn't "find" anything because it doesn't search for devices in the first place, your pluto just has the default IP. Secondly, the issue is completely different to this one. Yours is that SDR++ expects "PlutoSDR" devices, not "LibreSDR". I'm not sure yet how to best handle this and I suggest you open a separate bug report. |
WARNING: Filling out the template below is NOT optional. Issues not filling out this template will be closed without review.
FIRST: Before reporting any bug, make sure that the bug you are reporting has not been reported before. Also, try to use the nightly version if possible in case I've already fixed the bug.
Hardware
Software
Windows 10 x64
SDR++ v1.1.0 build 02 feb 2024
Bug Description
Adalm pluto via ethernet(LibreSDR) not found in current nightly versiot at windows.
But in old version sdrpp i can it is possible to specify the IP address of the pluto, but it not avaible in current version sdrpp.
Steps To Reproduce
Only If SDR++ fails to lauch or the SDR fails to start:
Run SDR++ from a command line window with special parameters:
cd
to SDR++'s directory and run.\sdrpp.exe -c
(if running SDR++ version 1.0.4 or older, use-s
instead, though you should probably update SDR++ instead...)sdrpp -c
/path/to/the/SDR++.app/Contents/MacOS/sdrpp -c
Then, post the entire logs from start to after the issue. DOT NOT truncate to where you think the error is...
Screenshots
Add any screenshot that is relevant to the bug (GUI error messages, strange behavior, graphics glitch, etc...).
Additional info
Add any other relevant information.
The text was updated successfully, but these errors were encountered: