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

SoapyRemote Timeout #219

Closed
n1zzo opened this issue Feb 26, 2021 · 1 comment
Closed

SoapyRemote Timeout #219

n1zzo opened this issue Feb 26, 2021 · 1 comment

Comments

@n1zzo
Copy link

n1zzo commented Feb 26, 2021

Describe the bug
When using OpenWebRx with SoapyRemote, after some time the stream stops, no waterfall is visible and logs show:

openwebrx    | WARNING: SoapySDR::Device::readStream timeout!
openwebrx    | WARNING: SoapySDR::Device::readStream timeout!
openwebrx    | WARNING: SoapySDR::Device::readStream timeout!

Restarting SoapyRemote does not solve the issue, restarting openwebrx does.

To Reproduce
Configure OpenWebRx with SoapyRemote and leave a protocol decoder to be active while no user is active, then wait.

Expected behavior
The stream from the SDR should not stop.

Installation method
Official Docker image jketterl/openwebrx-soapyremote:latest-aarch64 on Arch Linux ARM on Rock64,
SoapyRemote is running at system level, on Arch Linux ARM on a Raspberry Pi 2.

Versions
OpenWebRX version v0.21.0-dev

Log messages
openwebrx | WARNING: SoapySDR::Device::readStream timeout!

Additional context
No additional context.

@jketterl
Copy link
Owner

I'm sorry, but this is not an OpenWebRX error. As you can probably tell, a timeout is reported from the SoapySDR API, indicating that something has gone wrong. OpenWebRX has no means of keeping the stream running at this point, nor does it have any information as to what actually happened.

If you believe this timeout is unjustified, you should bring this up with SoapyRemote or SoapySDR.

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

2 participants