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_transfer replay failure #91
Comments
I'm pretty sure there is no actual bug here, but I'm leaving it open just in case anyone else wants to comment. |
this is very important, when i test my hackrf one transmitter i can't find any signal at RTL-SDR. |
Seem to have a similar problem. Recording is done via: test samples are transmitted via third party transmitter on 433.525 and 433.625 MHz Replay is done with: some transmitted samples can be found at app 431.965 MHz. |
NeuerUser: two samples per second (-s 2) is not supported. The minimum supported sample rate is 2000000. Additionally, you would probably need to increase the gain settings for rx and/or tx. |
I've had multiple reports from people in recent months who have done successful replay with hackrf_transfer. |
Hi Michael Thanks. Maybe a small example for hackrf_transfer is needed. I followed exactly the following procedure on youtube: https://www.youtube.com/watch?v=vHHRGOxcc-0 |
OK, played around with the options a bit and I got it working with: (I am still wondering why it worked for alaindecarolis in the youtube video. Has the syntax maybe been changed in hackrf_transfer at one time? Which version of the hackrf_tools should we use anyway with the KS hackrf one? I am currently using git-31c82a87.) |
Hi, I have observed similar behavior. I'm running Ubuntu 18.04 and I have an RTL-SDR and the HackrF One both in separate USB ports. Using gnuRadio-companion to receive the signal, and the Hackrf_One to transmit the signal (file) either an .s8 or .f32 format. |
Waveforms captured with hackrf_transfer (RX) don't seem to be reproduced properly when replayed by hackrf_transfer (TX). See http://nine.pairlist.net/pipermail/hackrf-dev/2013-July/000110.html
The text was updated successfully, but these errors were encountered: