Closed dbrll closed 1 year ago
Its not a known issue. Just making calls into libairspy shouldnt disconnect the device from the USB bus as far as I know. I can only imagine driver issues or flakey usb cables, power supplies.
Thank you for your answer. I can rule out dubious hardware as I can replicate the problem on two machines. This could be a driver issue though. I notice that after acquiring some samples with Soapy, the Airspy appears as disconnected but runs warm as it if it was still streaming and its DSP working.
I'm not sure how to move forward with this issue. This is an Airspy R2 with firmware 1.0.0-rc10 (latest). I guess I will call libairspy directly from Python as a workaround, since it works fine with libairspy and airspy_rx.
Hello,
I'm trying SoapySDR with an Airspy R2 through its Python interface.
The Airspy is properly connected:
Now if I try to run the sample code available here under "Basic example": https://github.com/pothosware/SoapySDR/wiki/PythonSupport
It works great also and I get some samples. However, I cannot re-run it because the device gets unbound, as shown with
udevadm monitor
:Sometimes the device doesn't get disconnected, but every sample received afterward is NULL. The solution is to unplug and plug back the device, it then resumes working.
Is this a known issue? How can I help troubleshoot this?