remove HackRF anti-freeze timeouts in places that do not require them #890
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The HackRF device has a freeze-bug when stopping sending or receiving data. As a workaround, there is a 0.2 second timeout in hackrf.pyx.
As far as I can tell, this timeout is only required in
stop_rx_mode
andstop_tx_mode
. The additional timeouts in theset_*
methods are an issue because they cause a combined delay of one complete second whenever something is supposed to be sent (e. g. using cli).I have been running the following code without issues for a while in an application, that sends some data every couple of minutes.
I did some manual testing in the urh gui, too.