[Hackrf-dev] not so good experience for my first SDR
Cinaed Simson
cinaed.simson at gmail.com
Tue Apr 18 20:32:15 EDT 2017
On 04/18/2017 12:28 PM, mohammed hamoud alkindy wrote:
> Million thanks, it works for me too and I am a happy man☺ even though I have allot to understand like the rational resampler and how the decimation is equal to the sampling rate!!! And the quadrature rate!!!!! Is this the original digitizing sampling rate? I still get some Ua’s every now and then. But for now I will just experiment with the different parameter after I understand their significants
>
> Thanks you ag
Glad it works for you!
In general, decimation is not equal to the sampling rate - it's only
true in the case of your flow graph.
Typically, one puts a low pass filter immediately after the source at
the highest sampling rate - and let the low pass filter do the first
decimation.
Decimation is down sampling and interpolation is up sampling.
As you move through your flow graph, you need to down sample the 10 Msps
to 48 Msps for the audio card.
The WBFM needs a sampling rate of 192 kHz in general so you need to use
the resampler to drop sampling rate from 10 Mps to 192 kHz for WBFM,
i.e., you need to decimate by the sampling rate and interpolate by the
quad rate.
Then WBFM decimates or down samples again by a factor of 4 to the
sampling rate of the audio card.
There's a difference between the interpolation/decimation by rational
resampler and the WBRM - the ratio of the up sampling to down sampling
needs to be a rational number for the rational resampler - whereas the
down sampling in the WBFM needs to be an INEGER multiple of the audio
sampling rate.
You really need to add a low pass filter and avoid the DC offset for the
center frequency in our flow graph.
In any case, you need to spend time on the tutorials - he'll walk
through how to do it. You'll learn a lot.
And I removed hackrf=0 device in the source properties in your flow
graph. If you only have 1 USB RF device plugged into the computer, then
leave it blank.
If you add another RF device use the serial number, e.g,
hackrf=423226e1
Using hackrf=0 is the old way.
-- Cinaed
ain
>
> Mohammed alkindy
>
>
> On 4/18/17, 6:33 AM, "Cinaed Simson" <cinaed.simson at gmail.com> wrote:
>
> Okay, this works on my system.
>
> Note, the sampling rate of the source is 10 MHz and quadrature rate is
> 192 kHz.
>
> Hence, I set the resampler to 10 MHz Decimation and 192 kHz Interpolation.
>
> I added another slider for the bb_gain and renamed the gain slider to
> if_gain.
>
> RF gain should be set to 0 for receiving.
>
> I also added your slider variables to the source properties and a volume
> control because the sound was to loud for me.
>
> Use the frequency slider to approximately locate the station and then
> use the fine control on the right to fine tune it.
>
> I changed the range of frequencies to 80 MHz to 116 MHz which is
> slightly over the WBFM range in the US. Regardless of where you live,
> it's usually only about 20 MHz wide - Google it.
>
> You should get to know your hardware by going through the tutorials so
> you don't end up smoking the RF amplifiers on your HackRF.
>
> And the tutorials will show you how to build a WBFM receiver correctly.
>
> -- Cinaed
>
> On 04/17/2017 09:51 AM, mohammed hamoud alkindy wrote:
> > Hello again, here is the .grc file for what I want to play with there are so many variable to play with and with my limited experience on sdr !!!!
> >
> > On 4/16/17, 12:29 AM, "Cinaed Simson" <cinaed.simson at gmail.com> wrote:
> >
> > On 04/15/2017 12:59 AM, mohammed hamoud alkindy wrote:
> > > Thank you Cinaed for taking me to this so far, I did the tests you suggested, there is only one hackrf_info file and the hackrf_transfer works fine. But for the libhackrf.so.0.5.0 or x could not find any of that format but found the following files:
> > >
> > > /opt/local/include/libhackrf
> > > /opt/local/lib/libhackrf.0.5.0.dylib
> > > /opt/local/lib/libhackrf.0.dylib
> > > /opt/local/lib/libhackrf.a
> > > /opt/local/lib/libhackrf.dylib
> > > /opt/local/lib/pkgconfig/hackrf.pc
> > >
> > > not sure if this Mac os because I did not created those manually but relied on macport to do that is required. I will try to take from here as it seems the libhackrf could be the issue with me
> >
> > Good - everything is there!
> >
> > Evidently, libhackrf.0.5.0.dylib is equivalent to libhackrf.0.5.0.so -
> > rhw .dylib extension for dynamic library or shared library on the Mac
> > and .so extension is for the dynamic or shared library on Debian.
> >
> > I'm assuming you're running the MacOS on bare metal and not inside a
> > virtual machine - like VMware or VirtualBox - correct?
> >
> > Please post your flow graph - the text XML version. Send it as an email
> > attachment.
> >
> > The file ends with
> >
> > .grc
> >
> > The "OOOO" indicates an overflow which can be something as simple as
> > improper plumbing between the osomcom source and the audio sink in the
> > flow graph - and the "aUaUaUaU" ia typical of the so-called "two clock
> > problem".
> >
> >
> > -- Cinaed
> >
> > >
> > > regards
> > >
> > >
> > >
> > >
> > >
> > > On 4/15/17, 12:37 AM, "Cinaed Simson" <cinaed.simson at gmail.com> wrote:
> > >
> > > On 04/14/2017 03:45 AM, mohammed hamoud alkindy wrote:
> > > > Thanks for spoting this, the strange thing is that when I display the version from my mac utility port “sudo port installed hackrf” it shows me the right ver which is 2017.2.1 but I do not know how to check for the libhackrf !!!!!! as I left all this to be taken care by the pakage utitity PORT
> > > >
> > > >
> > >
> > > I don't know how port chops up the programs.
> > >
> > > Try
> > >
> > > hackrf_transfer --help
> > >
> > > If it exists it will spit out a bunch of help commands, then try
> > >
> > > hackrf_transfer -r /dev/null
> > >
> > > and see if that works.
> > >
> > > If it does, see
> > >
> > > https://greatscottgadgets.com/sdr
> > >
> > > for an explanation of the output.
> > >
> > > And make sure there's only one copy of the hackrf_info installed - use
> > >
> > > find / -name hackrf_info
> > >
> > > and see if the latest version of libhackrf is installed
> > >
> > > find / -name libhackrf.so.0.5.0
> > >
> > > - at least that's the version I have installed building from the latest
> > > source code.
> > >
> > > It's possible the libhackrf version may be libhackrf.so.0.5.x where x is
> > > some number.
> > >
> > > Otherwise, try
> > >
> > > sudo port install gr-osmosdr +full
> > >
> > > which will take a while and then
> > >
> > > sudo port install gqrx
> > >
> > > assuming you haven't already do so - you're going to need them anyway.
> > >
> > > Otherwise, I can't help you - I don't understand the problem and I've
> > > never used a Mac.
> > >
> > > -- Cinaed
> > >
> > >
> > >
> > > >
> > > > On 4/13/17, 2:39 AM, "HackRF-dev on behalf of Cinaed Simson" <hackrf-dev-bounces at greatscottgadgets.com on behalf of cinaed.simson at gmail.com> wrote:
> > > >
> > > > On 04/10/2017 11:32 AM, mohammed hamoud alkindy wrote:
> > > > > Here are some shots I get some times the error msg but I then I reset
> > > > > the hackrf
> > > >
> > > > Please don't send binary images - just copy the output text into your
> > > > email.
> > > >
> > > > You don't have the correct version of libhackrf and utilities to match
> > > > the installed firmware on the HackRF.
> > > >
> > > > The installed firmware is 2017.2.1.
> > > >
> > > > The libhackrf version is: "unknown".
> > > >
> > > > The hackrf_info version is: "unknown".
> > > >
> > > > You need to install the 2017.2.1 version of the libhackrf and utilities from
> > > >
> > > > https://github.com/mossmann/hackrf/releases
> > > >
> > > > When both the version of hackrf_info and libhackrf match the firmware
> > > > version of 2017.02.1 then it will work.
> > > >
> > > > -- Cinaed
> > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > *From: *Dominic Spill <dominicgs at gmail.com>
> > > > > *Date: *Monday, April 10, 2017 at 10:27 PM
> > > > > *To: *Mohammed AlKindy <mohammed at omantel.net.om>
> > > > > *Cc: *"hackrf-dev at greatscottgadgets.com >> hackrf-dev"
> > > > > <HackRF-dev at greatscottgadgets.com>
> > > > > *Subject: *Re: [Hackrf-dev] not so good experience for my first SDR
> > > > >
> > > > >
> > > > >
> > > > > Do you have any ouput from it? Any error messages? Could we also have
> > > > > the output from hackrf_info?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Dominic
> > > > >
> > > > >
> > > > >
> > > > > On 10 April 2017 at 12:16, mohammed hamoud alkindy
> > > > > <mohammed at omantel.net.om <mailto:mohammed at omantel.net.om>> wrote:
> > > > >
> > > > > Got it now thanks, but yet to make it work, do not know what I do
> > > > > wrong see attached
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > *From: *Dominic Spill <dominicgs at gmail.com <mailto:dominicgs at gmail.com>>
> > > > > *Date: *Monday, April 10, 2017 at 9:38 PM
> > > > >
> > > > >
> > > > > *To: *Mohammed AlKindy <mohammed at omantel.net.om
> > > > > <mailto:mohammed at omantel.net.om>>
> > > > > *Cc: *"hackrf-dev at greatscottgadgets.com
> > > > > <mailto:hackrf-dev at greatscottgadgets.com> >> hackrf-dev"
> > > > > <HackRF-dev at greatscottgadgets.com
> > > > > <mailto:HackRF-dev at greatscottgadgets.com>>
> > > > > *Subject: *Re: [Hackrf-dev] not so good experience for my first SDR
> > > > >
> > > > >
> > > > >
> > > > > On 10 April 2017 at 11:25, mohammed hamoud alkindy
> > > > > <mohammed at omantel.net.om <mailto:mohammed at omantel.net.om>> wrote:
> > > > > >
> > > > > > Thank for quick response, I can see that with gqrx but what about
> > > > > when you execute the block from gnuradio-companion I could not see
> > > > > a field for that!!!!
> > > > >
> > > > > It's a setting on the osmocom source block. See the attached image.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Dominic
> > > > >
> > > > > > From: Dominic Spill <dominicgs at gmail.com <mailto:dominicgs at gmail.com>>
> > > > > > Date: Monday, April 10, 2017 at 9:21 PM
> > > > > >
> > > > > > To: Mohammed AlKindy <mohammed at omantel.net.om
> > > > > <mailto:mohammed at omantel.net.om>>
> > > > > > Cc: "hackrf-dev at greatscottgadgets.com
> > > > > <mailto:hackrf-dev at greatscottgadgets.com> >> hackrf-dev"
> > > > > <HackRF-dev at greatscottgadgets.com
> > > > > <mailto:HackRF-dev at greatscottgadgets.com>>
> > > > > > Subject: Re: [Hackrf-dev] not so good experience for my first SDR
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 10 April 2017 at 10:47, mohammed hamoud alkindy
> > > > > <mohammed at omantel.net.om <mailto:mohammed at omantel.net.om>> wrote:
> > > > > > >
> > > > > > > Still trying to make my Hackrf work with gnu-companion but I
> > > > > have stupid question, how does the osmocom source block know that I
> > > > > am using hackrf-one?
> > > > > >
> > > > > > You can specify the HackRF that you wish to use in the "device
> > > > > arguments" field of the osmocom source block. If you set it to
> > > > > "hackrf=0" it will use the first HackRF that it finds. To specify a
> > > > > particular HackRF, replace the 0 with the serial number of the
> > > > > HackRF (found from hackrf_info).
> > > > > >
> > > > > > With no device arguments set, osmocom searches for devices that it
> > > > > supports in turn. However, this currently triggers a segfault in
> > > > > libuhd on my system, so I always specify the HackRF in the device
> > > > > arguments field.
> > > > > >
> > > > > > cheers,
> > > > > >
> > > > > > Dominic
> > > > > >
> > > > > >
> > > > > > > From: Dominic Spill <dominicgs at gmail.com
> > > > > <mailto:dominicgs at gmail.com>>
> > > > > > > Date: Monday, March 13, 2017 at 11:11 PM
> > > > > > > To: Mohammed AlKindy <mohammed at omantel.net.om
> > > > > <mailto:mohammed at omantel.net.om>>
> > > > > > > Cc: "n0p [Luis Bernal]" <lbernal at gmail.com
> > > > > <mailto:lbernal at gmail.com>>, "hackrf-dev at greatscottgadgets.com
> > > > > <mailto:hackrf-dev at greatscottgadgets.com> >> hackrf-dev"
> > > > > <HackRF-dev at greatscottgadgets.com
> > > > > <mailto:HackRF-dev at greatscottgadgets.com>>
> > > > > > > Subject: Re: [Hackrf-dev] not so good experience for my first SDR
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 13 March 2017 at 13:09, mohammed hamoud alkindy
> > > > > <mohammed at omantel.net.om <mailto:mohammed at omantel.net.om>> wrote:
> > > > > > > >
> > > > > > > > Yes I use gqrx and watched the lessons from greatscottgadgets.
> > > > > if gqrx could allow to introduce throttling I would hsve test it but
> > > > > could not see such feature
> > > > > > >
> > > > > > > What sample rate are you using? Overruns are caused by the host
> > > > > system not keeping up with the amount of data being passed to it by
> > > > > the HackRF. Try reducing the sample rate to see if things improve.
> > > > > > >
> > > > > > >
> > > > > > > > From: "n0p [Luis Bernal]" <lbernal at gmail.com
> > > > > <mailto:lbernal at gmail.com>>
> > > > > > > > Date: Monday, March 13, 2017 at 9:33 PM
> > > > > > > > To: Mohammed AlKindy <mohammed at omantel.net.om
> > > > > <mailto:mohammed at omantel.net.om>>
> > > > > > > > Cc: "hackrf-dev at greatscottgadgets.com
> > > > > <mailto:hackrf-dev at greatscottgadgets.com> >> hackrf-dev"
> > > > > <HackRF-dev at greatscottgadgets.com
> > > > > <mailto:HackRF-dev at greatscottgadgets.com>>
> > > > > > > > Subject: Re: [Hackrf-dev] not so good experience for my first SDR
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > What software are you using? gqrx is a good choice to start
> > > > > playing with SDRs
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > I also suggest you start by watching the GNURadio tutorial
> > > > > series by Mike Ossman:
> > > > > > > >
> > > > > > > > https://greatscottgadgets.com/sdr/
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > 2017-03-13 17:50 GMT+01:00 mohammed hamoud alkindy
> > > > > <mohammed at omantel.net.om <mailto:mohammed at omantel.net.om>>:
> > > > > > > >
> > > > > > > > Hello SDR world, not so nice to start my posting in this
> > > > > mailing list with is kind of post, but when I got introduced to SDR
> > > > > I thought I will spend exciting evening to explore this new
> > > > > interest. But my experience is just ending with allot of
> > > > > OOOOOOOOOOOO or !!!! I read allot about what could be the
> > > > > reasons that is either the double clock or my sound card is not able
> > > > > to handle the sampling rates , etc…..but so far not able to solve
> > > > > the challenge. I just got my new MacBook Pro with good
> > > > > configurations and the sound card is configured to handle 44.1Khz. I
> > > > > did upgrade the Hackrf firmware to 2017-02-1 package. I am using
> > > > > gnuradio and my macport should take care of the updating to the
> > > > > latest ver. But again I do not seem to be able to hear even a simple
> > > > > FM station just noisy rains ☹
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Deeper insights will be really appreciated
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Mohammed alkindy
> > > > > > > >
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > HackRF-dev mailing list
> > > > > > > > HackRF-dev at greatscottgadgets.com
> > > > > <mailto:HackRF-dev at greatscottgadgets.com>
> > > > > > > > https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > _______________________________________________
> > > > > > > > HackRF-dev mailing list
> > > > > > > > HackRF-dev at greatscottgadgets.com
> > > > > <mailto:HackRF-dev at greatscottgadgets.com>
> > > > > > > > https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
> > > > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > HackRF-dev mailing list
> > > > > HackRF-dev at greatscottgadgets.com
> > > > > https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
> > > > >
> > > >
> > > > _______________________________________________
> > > > HackRF-dev mailing list
> > > > HackRF-dev at greatscottgadgets.com
> > > > https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
>
>
>
>
>
More information about the HackRF-dev
mailing list