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
As far as I experienced, the results provided by kalibrate-hackrf -s are always wrong (at least on recent host/firmware/CPLD). I get wrong ARFCN numbers and their advertised center frequencies correction is way to high (and on top of that, are contradictory, sometimes positive and sometimes negative), for example
Similar behaviour can be seen on various online tutorials here and there. The frequency correction does not make any sense on those reports either.
This issue is very much related to #16 and #23. As for the latter, I had indeed to go up to gains 32/32 to actually get some output, which should not be necessary as the BTS signals are supposedly strong enough.
Maybe this is all about HackRF One's DC spike? Is this what -E manual frequency offset in hz is made for? If so, how far away am I supposed to peak around? In what direction, -200Khz +200Khz? In short, how to use -E?
Hi
As far as I experienced, the results provided by
kalibrate-hackrf -s
are always wrong (at least on recent host/firmware/CPLD). I get wrong ARFCN numbers and their advertised center frequencies correction is way to high (and on top of that, are contradictory, sometimes positive and sometimes negative), for exampleSimilar behaviour can be seen on various online tutorials here and there. The frequency correction does not make any sense on those reports either.
This issue is very much related to #16 and #23. As for the latter, I had indeed to go up to gains
32/32
to actually get some output, which should not be necessary as the BTS signals are supposedly strong enough.Maybe this is all about HackRF One's DC spike? Is this what
-E manual frequency offset in hz
is made for? If so, how far away am I supposed to peak around? In what direction, -200Khz +200Khz? In short, how to use-E
?Thanks
update: and this is a duplicate of #6.
The text was updated successfully, but these errors were encountered: