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

HackRF keeps receiving (Python2 branch) #24

Open
cpoore1 opened this issue Sep 4, 2022 · 0 comments
Open

HackRF keeps receiving (Python2 branch) #24

cpoore1 opened this issue Sep 4, 2022 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@cpoore1
Copy link
Collaborator

cpoore1 commented Sep 4, 2022

Expected Behavior

Upon completing a receive flow graph (Inspection, Record, Attack) using the HackRF the RX light turns off and the flow graph ends. The threads in fg_executor.py complete when the flow graph is over following the .wait() calls.

Current Behavior

HackRF flow graphs with a head block or GUI keep the resources busy on the HackRF even after collecting enough samples or closing the GUI. The RX light remains on and overruns are still printed to the terminal. This only impacts the Python2 branch and a similar issue was observed with the PlutoSDR (but likely has a different cause). Running a new flow graph will stop all previous flow graphs of the same type but it will stay running.

Steps to Reproduce

  1. Click the IQ hardware button and select HackRF
  2. Click the Record button in the IQ Data tab
  3. Observe the light on the HackRF

Context

This may have to do with the osmocom source block and the version of gr-osmosdr as discussed here: greatscottgadgets/hackrf#354

Potential solutions include installing a different version of gr-osmosdr or adding a "Force Stop" button to the Dashboard. The Stop button for the Inspection flow graphs could detect when a HackRF is selected and trigger the necessary commands.

Version Information

gr-osmosdr 0.1.4-14build1
GNU Radio 3.7.11

@cpoore1 cpoore1 added the bug Something isn't working label Sep 4, 2022
@cpoore1 cpoore1 self-assigned this Sep 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant