You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Click the IQ hardware button and select HackRF
Click the Record button in the IQ Data tab
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
The text was updated successfully, but these errors were encountered:
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
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
The text was updated successfully, but these errors were encountered: