Skip to content
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

WARNING: SoapySDR::Device::readStream timeout! #223

Closed
alexFab opened this issue Mar 6, 2021 · 3 comments
Closed

WARNING: SoapySDR::Device::readStream timeout! #223

alexFab opened this issue Mar 6, 2021 · 3 comments

Comments

@alexFab
Copy link

alexFab commented Mar 6, 2021

Describe the bug
waterfall in web-gui stops.

SDR-Hardware
USRP B210

To Reproduce
It happens after 10 - 60 min. At a sample rate of 4Msps and much earlier using 8Msps .

Installation method

Versions
latest master branch

Log messages
WARNING: Soapy overflow
WARNING: SoapySDR::Device::readStream timeout!
WARNING: SoapySDR::Device::readStream timeout!
WARNING: SoapySDR::Device::readStream timeout!
WARNING: SoapySDR::Device::readStream timeout!
WARNING: SoapySDR::Device::readStream timeout!
WARNING: SoapySDR::Device::readStream timeout!
WARNING: SoapySDR::Device::readStream timeout!
WARNING: SoapySDR::Device::readStream timeout!

Additional context
I'm not sure where the error is coming from. SoapySDR? SoapyUHD? owrx_connector? openwebrx? Or just some miss configuration?

thx a lot!

@jketterl
Copy link
Owner

jketterl commented Mar 6, 2021

That's an error reported by the SoapySDR API, nothing OpenWebRX can handle. Please contact the developers of the SoapyUHD module.

@n1zzo
Copy link

n1zzo commented Mar 7, 2021

Hi @jketterl,
sorry for bringing this up again, but I believe that although the timeout is caused by the soapy library,
openwebrx is currently unable to recover after such an error.
Even in my issue: #219 , restarting soapyremote has no effect, and waterfall resumes only when openwebrx is restarted.
I believe that the issue should be solved by both sides, investigating the timeout cause, but also properly recovering from them on the openwebrx side.

@jketterl
Copy link
Owner

jketterl commented Mar 7, 2021

Funny story, but the fact that the waterfall just stops without the device going into the "failed" state is because that already is a workaround that allows airspyhf devices to recover. They run into timeouts whenever certain parameters are changes. If that workaround wasn't in place, they would fail on profile switches.

Other than that, OpenWebRX is currently not designed to recover any device after a critical failure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants