-
Notifications
You must be signed in to change notification settings - Fork 86
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
Receiver goes deaf after some time #29
Comments
I would argue that it's always worthwhile to make a PR, even for changes that may not be immediately integrated. Anyhoo, I haven't seen this issue but I'll run your patch on my system to regression test it. |
You should do up a PR. your patch doesn't break my system after about 28hrs of operation |
Created pull request #32. |
So, sometime complexity is not better. No more Mska, no more problems. @dev-zzo could you try y last commit ? |
Would this change impact BER in a negative way? |
Don't think so. There is theory and practice... |
So this is an issue I have seen quite often on my setup: the receiver goes deaf after running for random period of time, no messages are decoded even though the signal strength has not changed. It seems hard to provide a reproducer though. :-/
After some staring at the code I seem to have managed to come up with a patch that, when applied, appears to mitigate the issue; at least, my systems now do not exhibit deafness any more.
dev-zzo@dfbd30b
Please let me know if I should make a pull request for you to integrate the changes.
The text was updated successfully, but these errors were encountered: