-
-
Notifications
You must be signed in to change notification settings - Fork 194
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
Transition from RTLSDR "bundle" to a HackRF One - Decode Rate 1/sec #173
Comments
I'm an idiot... didn't apply the error correct right. Should've been +12000 and not -12000. Can be marked as resolved. :) Time to see how much of a workhorse this HackRF One really is! |
There appears to be a bug with the driver "unlatching" when trunk-recorder is CTRL C'd or when its SIGTERM'd. There's previous bug reports regarding this as well. Workaround for the time being: Reboot of the physical machine, be it button or terminal reboot. |
@bctrainers try compiling and using this executable to reset the HackRF, I've had success with it: https://gist.github.com/x2q/5124616 Usage: You can find what path your HackRF is at (the argument to usbreset) with a command like this: |
I too am having this problem. Seems that the HackRF is actually at fault from what I can tell. If you watch it in GQRX you can see the device actually freeze after a certain amount of time. Looks like the clock can't handle the long term heat that the HackRF makes. |
@Dygear what i did on my HackRF One was open up the case cover and apply a few heatsinks on all of the chips. It's kept the excessive heat generation at bay, and the drift isn't too bad after 6 hours of run time. |
Just want to note my experience here in case any others have the same issue: In summary, HackRF users take note:
Cheers, |
Am hitting this daily too. Going to install the tiny temperature controlled oscillator (tiny tcxo) add-on and see what happens. |
@robotastic I think this issue can be closed. There are two conversations here, a smaller one on HackRFs and recycling USB ports (which probably isn't within scope), and a more generalized one on SDRs with drifting timers. If there's interest, there's This is also just as easy of a problem to fix by hardware, or manual software compensation, which we already have. |
Agreed. And apologies for not returning with results. The txco was a solid fix. |
Agreed - Also adding that using a fan like this: https://www.amazon.com/AC-Infinity-MULTIFAN-Receiver-Playstation/dp/B00G05A2MU can be helpful no matter what SDR you use to help keep the temperatures stable. |
Hey,
My HackRF One came in the other day, got it hooked up this evening with everything configured with what i believe is correct.
Gave it a good spin on my windows machine with SDR#, didn't notice notable drift - even after six hours of running.
However, with the latest trunk-recorder revision, this is the result....
The config.json file...
Some of the config.json variables may have residual from the tree-house-man trunk-recorder fork.
The text output from running ./recorder...
The text was updated successfully, but these errors were encountered: