-
Notifications
You must be signed in to change notification settings - Fork 1.6k
hackrf_sweep_spectrum_analyzer not working with 2021.03.1 firmware? #1010
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
Comments
my guess is pretty much this being the problem. this combines 2017 userland/libhackrf with 2021 firmware. |
First line in the release notes, don't know how I missed that!! Thanks for pointing it out. Next adventure is to find out how to update libhackrf. I'd be grateful for any any pointers. I'm at the bad end of the learning curve on this sadly. |
No worries, this should be easy one to fix: The Pothos folks have handily bundled the latest hackrf tools and libraries as part of their project. If you download the latest Pothos SDR software, it will come with the latest versions of the hackrf libraries and tools. The documentation on the process is here: https://hackrf.readthedocs.io/en/latest/installing_hackrf_software.html#windows-binaries And the download area is here: https://downloads.myriadrf.org/builds/PothosSDR/ just select the top/latest version. There is the option of compiling/building from source code as well, but I'm assuming here you're looking for just a download link to the latest version. |
I have the latest PothosSDR stuff from that link already installed in C:\PothosSDR (it was not working when installed in the Program Files folder....). However I also had GNU radio 3.8 installed & it seems the libhackrf was being picked up from there maybe? I uninstalled GNU radio & now hackrf_info gives me: hackrf_info version: git-7047252 The hackrf_sweep_spectrum_analyzer is still not working though. I should have mentioned earlier that in the hackrf_sweep_spectrum_analyzer GUI, I see a message saying that HackRF is disconnected even thouhg starting that caused the RX LED to light. Thanks for the help! I'm at least making some progress. |
not sure that is going to work. edit ... it seems the newest working firmware is 2018.01.1 ... see pavsa/hackrf-spectrum-analyzer#40 |
Yes, hackrf_sweep_spectrum_analyzer seems to work with the 2018 firmware. However its not necessairly recommended to update to that version as the only difference between it and the 2017 version is improvements when using the DFU bootloader. The 2021 firmware seems to have more updates and bugfixes. Aside from that I see that using hackrf_sweep with the older firmware does not produce output! When I issue "hackrf_sweep.exe -f 10:110 -w 8192", I get an error as follows: I could be stuck with the 2017 firmware if I want to use the GUI. |
Throwing this out there: if you're goal is just to visualize the hackrf_sweep output, I have tested that https://github.com/xmikos/qspectrumanalyzer works on Windows 10 (as well as MacOS) with the latest firmware and libraries. It may be worth exploring rather than fighting with hackrf_sweep_spectrum_analyzer. |
I'll give that a try, thanks. If hackrf_sweep_spectrum_analyzer operates in some sort of non-standard way as suggested, it's unlikely to be any use to me. It's useful for a quick look and has a nice UI, but there is no way to dump the data to disk which was going to be the next problem. |
qspecturmanalyzer just calls the hackrf_sweep process under the covers. You can call this process directly if you want to get at the raw data. It has a couple modes of operation including one that writes to a CSV file for processing the data later, and one mode that operates in a binary format which is intended more for inter-process communication (such as between qspecturmanalyzer and hackrf_sweep.exe for real-time visualziation.) So one options would be to use the GUI to verify things are working as expected, then craft your own command line to write the data you need to disk.
Cheers, DM |
@pmcculey , I'm following up on this issue. Has it been resolved? |
I've had to park it due to pressures of other work. I was able to get an
executable version that worked, but would like to get the python code
operational so I could customise it for my needs. I want to build an
autonomous RFI monitor for our radio observatory.
Is it OK for me to contact you when I can get back at it?
Thanks,
Joe
…On Fri, 28 Jan 2022 at 07:21, Straithe ***@***.***> wrote:
@pmcculey <https://github.com/pmcculey> , I'm following up on this issue.
Has it been resolved?
—
Reply to this email directly, view it on GitHub
<#1010 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC5WS72H2JKWAOV5SN44UG3UYI7VXANCNFSM5JPZSGIA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yes, please feel free to re-open this issue or open another when you are able to return to this project. |
Steps to reproduce
Expected behaviour
Works with 2017.02.1 firmware but not with the newest version.
Actual behaviour
hackrf_sweep_spectrum_analyzer loads, the RX LED on the board lights, but no spectra are displayed on PC. Re-flashing the 2017.02.1 firmware restores functionality as far as hackrf_sweep_spectrum_analyzer operation is concerned
Version information
Operating system: Win10x64
hackrf_info output:
hackrf_info version: git-cc7f599
libhackrf version: git-cc7f599 (0.5)
Found HackRF
Index: 0
Serial number: 0000000000000000f77c60dc27746ec3
Board ID Number: 2 (HackRF One)
Firmware Version: 2021.03.1 (API:1.04)
Part ID Number: 0xa000cb3c 0x008f474e
If you are reporting a problem that involves third party software
(GNU Radio, Gqrx, etc), please report the version here.
Output
The text was updated successfully, but these errors were encountered: