Gonzalo José Carracedo Carballal

There is, indeed. It is a trick that exists for scenarios like these, in which you want to operate one or more devices remotely, without having to deliver samples at...

Damn I completely forgot about this issue. Please check this video: https://www.youtube.com/watch?v=2fJXc9m9SGg It basically explains how to set up the device server in the remote computer, set the access password,...

Have in mind that this trick does not only work for SDR devices, but for IQ-based file sources as well.

Hi @hvegh Did this solution work for you? Cheers,

This looks like a driver issue to me. Can you reproduce this crash with other applications too?

Yes, SoapyUHD. I am asking because, if you see here: ``` 0x00007ffff7d66e68 in SoapySDRDevice_setupStream () from /usr/local/lib/libSoapySDR.so.0.8-2 ``` The crash happens inside SoapySDR, when the device was already initialized, and...

Okay, what happens when you run this? (The full path is important) ``` /usr/local/bin/SoapySDRUtil --probe --args 'driver=uhd' ```

This is quite interesting. If you see, the driver used SoapySDRUtil is not UHD, but x300 instead. Let's try this: in the source config dialog, in the device tweaks button,...

Actually, you can do it from the GUI, there's a button named "device specific tweaks" for this purpose in the config dialog. If you prefer to edit config files directly,...

Try setting these keys too: ``` driver=x300 hardware=X310 fpga_version=39.0 fw_version=6.0 mboard_id=X310 mboard_name= mboard_serial=3253FAC ```