-
Notifications
You must be signed in to change notification settings - Fork 22
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
Crash of Cubic/Ubuntu and not able to use from SdrAngel/Win10? #75
Comments
The failure message on the server may just be the result of the client application dying. Do you have a backtrace for the client application crash, that may help point in the right direction? Also what does SoapySDRUtil --info say on the client side? |
Thank you for prompt response 👍 Soapy Server -- Use any Soapy SDR remotely###################################################### Server version: 0.5.2-g6d9bd820 // Ubuntu side Soapy SDR -- the SDR abstraction library###################################################### linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.002.000-3-g122bfae1 Found device 0 q@q-X756UX:~/Dev/CubicSDR/build/x64$ |
Can you share the output of I didnt expect to see 0.6, its a little old. I figure you would have compiled this soapysdr and friends from source recently. I'm just wondering if this is an ABI issue, you may just need to clean and recompile the software. |
Here it is: /usr/include/SoapySDR: /usr/local/include/SoapySDR: |
Just to notice that I have the same problem on Win10 machine running SDRAngel. Soapy Server -- Use any Soapy SDR remotely###################################################### Server version: 0.5.2-g6d9bd820 |
theres at least 3 versions of SoapySDR on that one machine. I recommend reading this: https://github.com/pothosware/SoapySDR/wiki/ConfigGuide#avoid-simultaneous-installs |
OK, thank you, let's go from scratch, starting with clean Ubuntu 18.04 LTS. |
All is up and running. New 18.04 installation is able to see remote devices. |
Now Ubuntu 18.04 story, clean installation: q@q-X756UX:/opt/build/sdrangel/build$ ls /usr/lib/x86_64-linux-gnu/libSoapy* /usr/local/lib/libSoapy* /usr/include/Soapy* /usr/local/include/Soapy* /usr/include/SoapySDR: /usr/local/include/SoapySDR: q@q-X756UX:~$ SoapySDRUtil --find Soapy SDR -- the SDR abstraction library###################################################### q@q-X756UX: Crash on selection of any of present remote devices, my guess is that trouble may |
Please advise?
SoapySDRUtil reporting all god but not able to
reach unit from Win10/SDRAngel or Ubuntu 16.04/CubicSDR
Regards
Djani
// Terminal copy from RPI side
pi@raspberrypi:~ $ SoapySDRServer --bind
######################################################
Soapy Server -- Use any Soapy SDR remotely
######################################################
Server version: 0.5.2-g6d9bd820
Server UUID: bc79164c-028a-15e4-8567-7c40007f0101
Launching the server... tcp://[::]:55132
Server bound to [::]:55132
Launching discovery server...
Connecting to DNS-SD daemon...
[INFO] Avahi version: avahi 0.7
[INFO] Avahi hostname: raspberrypi-2
[INFO] Avahi domain: local
[INFO] Avahi FQDN: raspberrypi-2.local
[INFO] avahi_entry_group_add_service(raspberrypi-2._soapy._tcp)
Press Ctrl+C to stop the server
// Win10 SDRAngel request, API 192.168.10.106: 55132
SoapyServerListener::accept([::ffff:192.168.10.103]:64711)
SoapyServerListener::handlerLoop() FAIL: SoapyRPCUnpacker::recv() FAIL: header word
SoapyServerListener::close()
// Testing from Ubuntu, Cubic SDR, crash
SoapyServerListener::accept([::ffff:192.168.10.197]:37350)
SoapyServerListener::accept([::ffff:192.168.10.197]:37352)
SoapyServerListener::close()
SoapyServerListener::close()
SoapyServerListener::accept([::ffff:192.168.10.197]:37356)
SoapyServerListener::accept([::ffff:192.168.10.197]:37358)
SoapyServerListener::accept([::ffff:192.168.10.197]:37360)
SoapyServerListener::close()
SoapyServerListener::close()
SoapyServerListener::accept([::ffff:192.168.10.197]:37362)
SoapyServerListener::close()
SoapyServerListener::close()
SoapyServerListener::accept([::ffff:192.168.10.197]:37368)
SoapyServerListener::accept([::ffff:192.168.10.197]:37370)
SoapyServerListener::accept([::ffff:192.168.10.197]:37372)
SoapyServerListener::close()
SoapyServerListener::close()
SoapyServerListener::accept([::ffff:192.168.10.197]:37374)
SoapyServerListener::handlerLoop() FAIL: SoapyRPCUnpacker::recv(header) FAIL:
// After that testing with SoapySDRUtil from Ubuntu, terminal copy of RPI side
SoapyServerListener::close()
SoapyServerListener::close()
SoapyServerListener::accept([::ffff:192.168.10.197]:37410)
SoapyServerListener::accept([::ffff:192.168.10.197]:37412)
SoapyServerListener::close()
SoapyServerListener::close()
// Ubuntu side
/Dev/CubicSDR/build/x64$ SoapySDRUtil --find="192.168.10.106=raspberrypi-2, driver=remote"
######################################################
Soapy SDR -- the SDR abstraction library
######################################################
linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.002.000-3-g122bfae1
Found device 0
addr = 24607:1027
driver = remote
label = LimeNET-Micro [USB 2.0] 58399D024CE9
media = USB 2.0
module = FT601
name = LimeNET-Micro
remote = tcp://192.168.10.106:55132
remote:driver = lime
serial = 0058399D024CE9
q@q-X756UX:~/Dev/CubicSDR/build/x64$
The text was updated successfully, but these errors were encountered: