Its clearly trying to. But is it doing it right? I have no idea. I do know that in GnuRadio it SEEMS that you have to tell it one of the discrete published values from the chip data sheet or it seems not to work. One would have to look at lots of obscure source code, use some sort of debugging, or experiment, to know. And we don't know if that round down routine is in fact making it narrow enough. In my opinion the bandwidth should be user settable.
Doug ________________________________ From: Marcus Watson [[email protected]] Sent: Tuesday, September 30, 2014 3:15 PM To: McDonald, J Douglas; [email protected] Subject: Re: [Hackrf-dev] HackRF in SDR# Caveat: I know more about developing/reverse engineering than I do about SDR. I reverse engineered the SDRSharp.HackRF.dll - in looking for more info I then found a year old repository on Github for HackRF and the code hasn't changed significantly: https://github.com/cgommel/sdrsharp/blob/master/HackRF/HackRFDevice.cs var baseband_filter_bw_hz = NativeMethods.hackrf_compute_baseband_filter_bw_round_down_lt((uint)_sampleRate); r = NativeMethods.hackrf_set_baseband_filter_bandwidth(_dev, baseband_filter_bw_hz); Does this mean it's using the sample rate to set the baseband filter bandwidth? Marcus On 30/09/2014 16:19, McDonald, J Douglas wrote: >From my experience with SDR# and HackRf, it seems that whoever wrote the code to use HackRF is sending the wrong bandwidth option to the chip of the HackRF that limits it before Mr. Nyquist can have a fit. Its far far too wide. This is a trivial fix in the code attaching HackRF to SDR#.. It would be better to add a box so the user could set the bandwidth. Doug McDonald _______________________________________________ HackRF-dev mailing list [email protected]<mailto:[email protected]> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
_______________________________________________ HackRF-dev mailing list [email protected] https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
