Re: [Hackrf-dev] is there a hackrf_tcp app ??

[Chuck McManis]

On Sun, Dec 20, 2020 at 7:00 PM Chris Kuethe  wrote:

> I'd say OP is asking about something like rtl_tcp, but for hackrf.
> https://manpages.ubuntu.com/manpages/trusty/man1/rtl_tcp.1.html
>

That is what I expected as well. It is a pretty trivial program to write. I
have found however that for tcp IQ sources it is helpful to keep timestamp
metadata along (ala VITA 87.2) which helps in the DSP processing of said
data correctly in the face of network congestion.
--Chuck


>
> Or maybe USB-IP. https://wiki.archlinux.org/index.php/USB/IP
>
> On Wed, Dec 16, 2020 at 6:32 AM Jonathan Guthrie 
> wrote:
>
>> I don't  understand what you're trying to do.  Could you describe it in
>> more detail?  What are you trying to pass USB through?
>>
>> I have given some thought to doing something that could translate
>> between, say, the protocol that the Hermes Lite 2 users to the USB
>> signals used by the HackRF, but I usually lie down until the feeling
>> passes.
>>
>> On 12/14/2020 2:55 PM, G2 wrote:
>> > i've  tried  unsuccessfully trying to get hackrf to be passed through
>> > on USB 2.0 to either parrotsec os or kali2020 to no avail.
>> >
>> > so, is there a type hackrf_tcp app for win or linux that can have
>> hackrf like a
>> > server on the lan?
>> >
>> > ___
>> > HackRF-dev mailing list
>> > HackRF-dev@greatscottgadgets.com
>> > https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>> ___
>> HackRF-dev mailing list
>> HackRF-dev@greatscottgadgets.com
>> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>>
>
>
> --
> GDB has a 'break' feature; why doesn't it have 'fix' too?
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Transmitting test signals

[Chuck McManis]

Hi Doug,

The simplest way to do this is to generate an IQ data file with your C code
and then set up a GRC flowgraph which uses that file as a source and the
HackRF as a sink.

If you look at the web site where Mike talks about recording a signal and
then playing it back, it has all the elements (except you're generating the
signal not recording it)

As for the receiver side being 8 bits only, that is ~ 48dB of SNR. That is
fine for many many receivers. I'd say don't knock it until you try it :-).

--Chuck


On Fri, Oct 30, 2020 at 5:57 AM McDonald, J Douglas 
wrote:

>
> Right at the first I bought a HackRF. It sort of worked.
>
> But I never succeeded in getting it to, usefully, do what I bought it for,
> transmitting test signals of my own design.
>
> What I want to do is trivial: generate an array in memory using a
> straightforward C (hopefully NOT the cumbersome C++) program, then either
> repeatedly and seamlessly send it to the
> HackRF. Seamlessly means that to runs over and over forever, the end
> connecting seamlessly
> to the start of the file. I would like to get at least 8 MHz of unaliased
> spectrum, though 10 would be better.
>
> I never got it to work seamlessly.
>
> This would NOT use any oddball stuff like Python or Linux, just plain
> ordinary C on a plain ordinary Windows 10 PC.  I tried on Linux with the
> sort of "system" that uses Python and its hoplelessly klunky. Especially
> since there is no documentation.
> If I am forced to communicate with a "driver" I need good documentation,
> otherwise, its magic which I don't seem adept at.
>
> It tried lots of things including a Windows device driver I found, but
> while it sort of worked,
> for a while, it always started stuttering.  I can get receive to work in
> the same bandwidth
> no problem. But I never expected the HackRF to work as a receiver with
> only
> 8 bits ... not enough dynamic range. 8 bits is of course perfectly fine
> for test signals.
>
> Its been a while since I sent a message like this. Advice is needed in
> email, at least how to
> contact this help group and its archives if there are answers already.
>
> Doug McDonald
> jdmcd...@illinois.edu
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Two Channel Receiver

[Chuck McManis]

Hi Nicolas,

Assuming the two radio stations are within 20MHz of each other in terms of
frequency, the way to do this is to use the HackRF to grab one wide channel
that covers both of them, and then to create two tuners in your graph that
pull the stations out of that wide spectrum chunk. To see how to do this
inefficiently (but it works!) Do the HackRF tutorial to receive an FM radio
station, and then duplicate the blocks for the first mixer, the
downsampler, and the wideband demodulator. That will tune a "second"
channel from the same 20MHz input spectrum. You can then run the audio out
to a mixer block with a slider to adjust the mix between the two stations.
Slide left for station 1, slide right for station 2, in the middle you get
both mixed together :-).
--Chuck


On Thu, Oct 29, 2020 at 10:38 AM Nicolas Araújo  wrote:

> Hi, everyone!
>
> I am trying to design a receiver able to record two radio stations on the
> same time. I am setting the number of channels equals to two and putting as
> device arguments "hackrf=0,nchan=2". However, I am receiving the following
> error message:
>
> File "/usr/lib/python3.7/site-packages/gnuradio/gr/top_block.py", line
> 111, in start
> top_block_start_unlocked(self._impl, max_noutput_items)
> File "/usr/lib/python3.7/site-packages/gnuradio/gr/runtime_swig.py", line
> 4534, in top_block_start_unlocked
> return _runtime_swig.top_block_start_unlocked(r, max_noutput_items)
> RuntimeError: resolve_port: hierarchical block 'source_impl': output 1 is
> not connected internally
>
> Any suggestions, ideas, solutions, corrections?
>
> Thank you!
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] How to tell if antenna is faulty

[Chuck McManis]

Technically there is only *one* SMA connector, it is defined in MIL-STD-348.
There is also "RP-SMA" which has the same mechanical dimensions but swaps
the pin and socket locations from the outer threaded version to the inner
threaded version.

That said, a vendor might confuse them and call some random connector "SMA"
(I have seen TV types refer to the  75 ohm "F" connector as an SMA
connector incorrectly)
--Chuck

On Tue, Feb 5, 2019 at 8:53 AM cliff palmer  wrote:

> I tried to order a multimeter test lead that fits SMA connectors so I can
> have an easier time testing antennas.
> It turns out that "SMA Connector" can mean a lot of different sizes and
> types.
> Does anyone have the male and female core diameter for the SMA connectors
> used by the HackRF One?
> Thanks!
>
> On Thu, Jan 31, 2019 at 6:22 PM Michael Ossmann  wrote:
>
>> Cliff,
>>
>> That sounds like a faulty ANT500.  Please contact your reseller for a
>> replacement.  Send a private email to me and i...@greatscottgadgets.com
>> if you run into any problems with that.
>>
>> The two most common faults of ANT500 and ANT700 are a short between the
>> center pin and shield ground or a break in continuity between the center
>> pin and the antenna element.  Both of these conditions can be tested
>> with a continuity tester.
>>
>> The DC resistance between the center pin and the antenna element is
>> unspecified, but I think it should be stable and low enough to cause a
>> continuity tester to beep.
>>
>> Michael
>>
>>
>> On Thu, Jan 31, 2019 at 09:45:58AM -0500, cliff palmer wrote:
>> >
>> > Jake, the reading between the tip of the antenna and the center pin
>> varied
>> > wildly - so much that I borrowed another multi-meter to confirm them.
>> The
>> > readings went from zero to 160+ and back.  I did secure the antenna and
>> the
>> > multi-meter leads to make sure my hands weren't the cause of the
>> variation.
>> > It looks like the antenna is faulty.
>> > Thanks for the hint on CQRX.
>> >
>> > I am using the Hackrf with the Ant500 as a starting place to learn
>> enough
>> > about SDR to tap RF data feeds from NOAA Buoys.  These buoys measure
>> water
>> > temp, wind speed and direction, wave direction, height and frequency.
>> The
>> > buoy data will be fed into an FPGA/RISC board to calculate and display
>> > marine navigation conditions, much like your local weather forecast
>> > includes a wind speed and direction display.
>> > There's no way that the Ant500 will be the right antenna for this.  I
>> got
>> > it because I needed a starting place and a number of YouTube tutorials
>> on
>> > SDR used it with the Hackrf.  Once I know more about what I am doing
>> I'll
>> > be pestering you all again for advice on antennas.
>> >
>> > Thanks again
>> > Cliff
>> >
>> > On Wed, Jan 30, 2019 at 11:24 PM Gavin Jacobs > >
>> > wrote:
>> >
>> > > Cliff,
>> > > I have a hackrf and an Ant500. With the antenna fully extended, you
>> should
>> > > measure a very low resistance between the tip of the antenna and the
>> center
>> > > pin of the connector. Mine was about 2 ohms. If you have 75 ohms, then
>> > > there is a problem. Try again between the center pin and the elbow
>> (where
>> > > the extensions start) - it should be very low < 1 ohm.
>> > >
>> > > You should be able to use GQRX to receive an FM radio station, with
>> almost
>> > > any antenna. Most common rookie mistake is forgetting to turn up the
>> IF
>> > > gain.
>> > >
>> > > Tell us more about your setup and we can help you get started.
>> > >
>> > > Jake
>> > >
>> > > --
>> > > *From:* HackRF-dev  on
>> behalf
>> > > of cliff palmer 
>> > > *Sent:* January 30, 2019 3:15 PM
>> > > *To:* hackrf-dev@greatscottgadgets.com
>> > > *Subject:* [Hackrf-dev] How to tell if antenna is faulty
>> > >
>> > > I have a Hackrf One with an Ant500 Antenna and I am having no luck
>> with
>> > > multiple tutorials found on YouTube, including the ones at Great Scott
>> > > Gadgets.  I measured the resistance on the (disconnected but fully
>> > > extended) Ant500 Antenna using a multimeter (one lead on the metal
>> part of
>> > > the antenna and the other on the male lead in the connector.  The
>> > > multi-meter measured up to 75 Ohm resistance.
>> > > I'm really new to SDR and so I don't know if resistance should
>> concern me,
>> > > but it seems like an antenna should not have resistance.
>> > > I would appreciate some advice about how to determine if this is
>> really a
>> > > problem (and the antenna is faulty) or if I am making a typical
>> new-to-SDR
>> > > mistake.
>> > > Thanks
>> > > ___
>> > > HackRF-dev mailing list
>> > > HackRF-dev@greatscottgadgets.com
>> > > https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>> > >
>>
>> > ___
>> > HackRF-dev mailing list
>> > HackRF-dev@greatscottgadgets.com
>> > https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>>
>> 

Re: [Hackrf-dev] Hey, everybody

[Chuck McManis]

Hi Jonathan,

Be aware that the 8 bit resolution of the DAC on the HackRF means that you
get quite a bit of quantization noise in the output. You can build a filter
bank to reduce those spurs but the end result is that the HackRF's use as a
signal generator is not as high as you might like. I ended up getting one
of the EraSynth ones off CrowdSupply when they ran their first campaign and
it has much lower phase noise and (in my case) a wider range. I have used
it as an LO with a mini-circuits mixer to tune the entire amateur band for
the HackRF (it also extended the range of my HackRF to the 10Ghz bands as I
can downconvert 10Ghz to 1Ghz that the HackRF can handle nicely. While the
Minicircuits mixer is good to at least 10dBm I have not tried trancieving
with it yet.  I also picked up a Morpheus (cheap at $125) which has the
mixer built in, but it doesn't have the range that the Erasynth does.

73,
--Chuck
(AI6ZR)




On Sat, Jan 12, 2019 at 8:38 AM Jonathan Guthrie  wrote:

> Please allow me to introduce myself.  I'm Jonathan and I just bought a
> HackRF One with the intention of turning it into a software-defined
> transceiver for amateur radio use.  I figure that a power amplifier and
> T/R switch can't be all that hard (yeah, I know, "famous last words")
> and I'm a computer programmer at my day job so the software part is at
> least do-able.  The upshot is that I'm hoping that for a little bit (or
> a lot) of sweat equity, I can get an HF transceiver that is similar to
> commercial transceivers for a fraction of the cost.  That's the plan,
> anyway.  I'm certain it'll be educational.
>
> By looking over the recent archives, I see that other people have tried
> to do similar things, which is good because it means that I don't have
> to start from complete scratch.
>
> For a long time, I been using one of those TV dongles as a
> software-defined receiver to receive FM broadcast, 2m FM, and some 2m
> and 70cm SSB/CW signals from satellites, so I don't have to climb (much
> of) a learning curve to work with GRC.
>
> So far, I've plugged my HackRF One in to my Linux laptop and have
> listened to some FM radio, and it seems to work.
>
> At some point, I'm probably going to get another one so I can use it as
> a signal generator.  Lots of useful things you can do with a signal
> generator.
>
> Anyway, that's me.  If I have any questions about how to proceed, I'll
> let you know.
>
> --
> Jonathan Guthrie
> ARS KA8KPN
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Two Dead Hacks

[Chuck McManis]

Just out of curiosity (and a desire not to step into something) do you
know *how
*you killed the HackRFs? I've seen people who killed the input or output RF
amps because they weren't thinking about RF stages, and I've seen a couple
of reports of people killing them by using poorly regulated battery based
power supplies.


On Mon, Sep 3, 2018 at 12:20 AM James Brown  wrote:

> I managed to kill both my Hacks. Neither one will enumerate on the USB.
> Tried several machines. No Luck.
> Is there a service for repair of these machines?
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Still hoping for PTT

[Chuck McManis]

It is a bit more complicated Giuseppe than that. You see there are systems
which have active antennas (powered) for receiving. In such a system you
can use the antenna bias to provide power to the active antenna elements
(typically a filter bank and an LNA). Those are typically receive only
systems. Systems that have a dedicated transmit port can "hard code" the
bias-T on that port and switch on or off bias on the receive port. But if
you only have one port there are times when you want the bias on all the
time (operations with an active antenna) and times when you want it only
during transmit (PTT / bias-t applications). A software option that lets
you choose how it behaves is the best overall solution.

--Chuck

On Wed, Jun 27, 2018 at 3:13 AM Giuseppe Marullo 
wrote:

> > Or to put it differently, :-) If the HackRF would enable the ANT bias
> > when it was transmitting then it would "just work" as they say.
> Definitely I would vote for this. Maybe we could "link" the TX LED
> signal with the BIAS using a little hw "bridge" so not to rely on any
> sw change.
>
> Giuseppe Marullo
> IW2JWW - JN45RQ
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Still hoping for PTT

[Chuck McManis]

Or to put it differently, :-) If the HackRF would enable the ANT bias when
it was transmitting then it would "just work" as they say.

On Tue, Jun 26, 2018 at 11:18 AM Gavin Jacobs 
wrote:

> Dominic
> Thanks for that offer/suggestion, but it’s already done! I found the TX
> mode signal that drives the TX LED, and it was already brought out to P5.
> So All I had to do was solder some ribbon cable to P5 socket (which is not
> populated). I have it connected to my power amp such that it energizes
> whenever the Hackrf is in transmit mode.
>
> Jake
>
>
> On Jun 26, 2018, at 10:59 AM, Dominic Spill  wrote:
>
> I'm not certain, because I don't want to break portapack or other add on
> boards, but it may be possible for us to toggle a GPIO pin on one of the
> headers when we switch to TX mode, if that would help?
>
> Dominic
>
> On 20 June 2018 at 17:55, Gavin Jacobs  wrote:
>
>> Chuck,
>> I have used the bias-t voltage on the hackrf to power an upconverter but
>> it isn’t easy to turn it on and off. The only method I know is to use
>> hackrf-transfer - but that doesn’t work when switching to/from rx & tx.
>>
>> Meanwhile I have brought the tx LED signal out from P5, and it is
>> switching the power amp on and off just fine.
>>
>> Jake
>>
>> On Jun 19, 2018, at 7:02 PM, Chuck McManis 
>> wrote:
>>
>> FWIW the idiomatic way to achieve this as far as I can tell is to send a
>> bias-T signal on the RF cable, basically its a DC offset on the cable which
>> the PA picks up and switches on. This lets you have short cables between
>> the PA and the antenna and its only one line to hook up (the antenna coax)
>>
>> On Tue, Jun 19, 2018 at 5:04 PM Gavin Jacobs 
>> wrote:
>>
>>> Bernie
>>> That’s a great idea! I looked on the hackrf schematic and the signal for
>>> the TX LED is brought out to a (DNP) header - all I have todo is bring that
>>> signal out to my PTT circuit. Thanks for the suggestion!
>>>
>>> Jake
>>>
>>>
>>> On Jun 15, 2018, at 5:32 AM, Bernard Kobier 
>>> wrote:
>>>
>>> I admit I have not tried this but what about using the TX LED to drive
>>> an optocoupler to switch the amp?
>>>
>>> Bernie
>>>
>>>
>>>
>>> On 11 Jun 2018, at 00:53, CJ Hicks 
>>> wrote:
>>>
>>> Why not leave your exciter on and only PTT your power amplifier (PA)?
>>> Or use an RF to shunt your exciter signal into a dummy load.  Just a couple
>>> of random thoughts.
>>>
>>> CJH
>>>
>>> *From:* HackRF-dev [mailto:hackrf-dev-boun...@greatscottgadgets.com
>>> ] *On Behalf Of *Gavin Jacobs
>>> *Sent:* Saturday, June 09, 2018 5:57 PM
>>> *To:* hackrf-dev@greatscottgadgets.com
>>> *Subject:* [Hackrf-dev] Still hoping for PTT
>>>
>>> Has there been any progress on implementing digital i/o from/to the
>>> hackrf One. I'm hoping that someday the hackrf can supply a PTT signal to
>>> an external amplifier.
>>>
>>> Jake
>>>
>>> ___
>>> HackRF-dev mailing list
>>> HackRF-dev@greatscottgadgets.com
>>> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>>>
>>>
>>> ___
>>> HackRF-dev mailing list
>>> HackRF-dev@greatscottgadgets.com
>>> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>>>
>>
>> ___
>> HackRF-dev mailing list
>> HackRF-dev@greatscottgadgets.com
>> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>>
>>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Determining exact tuning frequency

[Chuck McManis]

Hi Phil,

What I've done is that I center tune into the neighborhood of where I want
to tune, and then use either a DDC or a soft mixer function (in GRC or
another module) to tune exactly where I want. If you're trying to homodyne
to the precise frequency then I agree you'll not always be successful.

The other advantage of doing the tuning after you've got your pass band is
that you can run multiple receivers off the same pass band data if they are
all within range. One of my examples I show people is an FM radio with 5
different tuners. The HackRF is tuned to the center of the FM band and then
I can move the 5 tuners anywhere within that band, demodulate them, and mix
and match the audio. Nothing like having a bit of Classic Rock 98.5 in the
background when listening to KFRC (KCBS FM) 106.9.

--Chuck


On Fri, Jun 22, 2018 at 10:22 PM Phil Karn  wrote:

> Since the HackRF One (like most SDRs) uses fractional-N synthesizers, it
> can't always give you the exact tuner frequency you ask for. I would
> like to write a function to determine the actual frequency from the one
> I ask for so I can compensate for the difference in a later point in my
> processing chain. (I'm using a GPSDO clock so these small frequency
> offsets are actually quite noticeable.)
>
> I'm looking at the spec sheets and firmware for the various PLL
> constants but I'd like to know if anyone has already done this. Thanks.
>
> Phil
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Still hoping for PTT

[Chuck McManis]

FWIW the idiomatic way to achieve this as far as I can tell is to send a
bias-T signal on the RF cable, basically its a DC offset on the cable which
the PA picks up and switches on. This lets you have short cables between
the PA and the antenna and its only one line to hook up (the antenna coax)

On Tue, Jun 19, 2018 at 5:04 PM Gavin Jacobs 
wrote:

> Bernie
> That’s a great idea! I looked on the hackrf schematic and the signal for
> the TX LED is brought out to a (DNP) header - all I have todo is bring that
> signal out to my PTT circuit. Thanks for the suggestion!
>
> Jake
>
>
> On Jun 15, 2018, at 5:32 AM, Bernard Kobier 
> wrote:
>
> I admit I have not tried this but what about using the TX LED to drive an
> optocoupler to switch the amp?
>
> Bernie
>
>
>
> On 11 Jun 2018, at 00:53, CJ Hicks 
> wrote:
>
> Why not leave your exciter on and only PTT your power amplifier (PA)?  Or
> use an RF to shunt your exciter signal into a dummy load.  Just a couple of
> random thoughts.
>
> CJH
>
> *From:* HackRF-dev [mailto:hackrf-dev-boun...@greatscottgadgets.com
> ] *On Behalf Of *Gavin Jacobs
> *Sent:* Saturday, June 09, 2018 5:57 PM
> *To:* hackrf-dev@greatscottgadgets.com
> *Subject:* [Hackrf-dev] Still hoping for PTT
>
> Has there been any progress on implementing digital i/o from/to the hackrf
> One. I'm hoping that someday the hackrf can supply a PTT signal to an
> external amplifier.
>
> Jake
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] advice on a txco to buy?

[Chuck McManis]

Orrin,

I expect that if you continue in your journey in software radio you will
find that a solid 10Mhz reference to be a good thing to have in general.
(which you can use to drive the HackRF). I ended up getting an RF signal
generator from Crowd Supply (
https://www.crowdsupply.com/era-instruments/erasynth) which works really
well for this and I can use it with all of my SDRs in addtiion to the
HackRF.  A friend of mine recommended this one (
https://www.tindie.com/products/AnalysIR/10mhz-ocxo-frequency-standard-module-or-kit/)
which is basically $77 when you get all the parts and it is assembled) so
lower cost but equally movable from SDR to SDR.

Cheers,
--Chuck




On Tue, Jun 12, 2018 at 3:33 PM, Orrin Winton 
wrote:

> Hello folks, have had my HackRF for about a week and am going thru
> Michael's tutorials & other tutorials. Love this device.
>
> Are the eBay items described as "New External TCXO clock PPM 0.1 for
> HackRF One GPS Applications GSM/WCDMA/LTE" for $10-12 the appropriate part
> to buy? (noob here)
>
> Or can some similar item be bought that has SMA jacks on it and can be
> connected via cable to the jack on the rear of the HackRF?
>
> The $10 clock looks like it'll require leaving the top half of the case
> off, is why i ask.
>
> At 434 MHz doing hackrf_transfer i'm getting 700 to 1000 hz drift
> (downwards in freq) on a replayed CW signal, in ten minutes, which (if i'm
> calculating this correctly) is 1.6 to 2.3 ppm.
>
> I'm being careful to use the correct antenna on the HackRF, keep gains
> low, and use low xmit power (2W) on my amateur transceiver across the room
> (to record an rf_transfer). Possibly i should put an attenuator on the 2W
> radio.
>
> Thanks for comments.
>
> Orrin in NE Calif.
>
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Max TX power

[Chuck McManis]

Have you considered a separate power amplifier ? While the HackRF can
transmit a few milliwatts of power if you're actually going to use it to
transmit something "for real" (rather than just use it for experiments) you
might consider getting a filter for the band of interest and a separate
power amplifier. That does two things for you, first it prevents the
transmissions of spurious signals (harmonics, overtones, etc) that arise
from the nature of how the signal is created. Second it lets you accurately
control the effective radiated power of your antenna and power amplifier
set up and stay within any transmission restrictions for the spectrum on
which you are transmitting. As a bonus it protects the output stage of your
HackRF from reflected transmission signals coming from mismatched
transmission lines.

On Thu, May 31, 2018 at 1:35 AM, Matteo Terzi 
wrote:

> Hi all,
> how can I set the maximum TX power of the HackRF?
> On gnu radio I'm using a "multiply const=6" and the parameter "IF Gain=47"
> (of the osmocom sink). Any other method or strategies??
> Thanks
>
> Matteo
>
> --
> Matteo TERZI
> Google Gmail Member
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Disturb a RF signal

[Chuck McManis]

Hi Matteo,

Interfering or intentionally disturbing another RF transmission (even in
the unlicensed bands)  is illegal in pretty much every country in the
world. Thus any help someone might offer for you to interfere with a signal
would make them an accessory to that offense.

Typically such interference has occurred during times of war or during
espionage. Because of that the places where you might go to learn about how
governments have historically interfered with radio signals is a book on
Electronic Warfare available at your library or amazon.

--Chuck


On Thu, May 10, 2018 at 3:03 AM, Matteo Terzi 
wrote:

> Hi all,
> anybody know how can I disturb radio signal with hackrf?
> I'd like to eliminate a certain value of frequency. I read something about
> the radio signal noise and I know that I should use the same frequency,
> same modulation and with a power higher or equal. Is it correct?
> Thanks
>
> Matteo
>
> --
> Matteo TERZI
> Google Gmail Member
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Low pass filter lesson 1

[Chuck McManis]

Hi Matteo,

It is the difference between "baseband" and "RF". If you take an RF signal
that is at 100Mhz and has a bandwidth of 2.5Khz,  you can mix it with
another signal at 100Mhz and that will produce two outputs, one at 200Mhz,
and one at 0Mhz. It will still have a 2.5Khz bandwidth so on the low end it
will be between 0 and 2.5kHz so a low pass filter is needed.

This is the fundamental principle behind radios.

--Chuck


On Tue, May 8, 2018 at 5:59 AM, Matteo Terzi 
wrote:

> Hi all,
> I'd like to know why does Micheal Ossmann use a Low Pass Filter in the
> Lesson 1 (https://greatscottgadgets.com/sdr/1/ --> minute 22:00).
> He says that in that way just frequencies near to the zero Hz can pass but
> it doesn't make sensehow radio frequencies can pass if they have a
> value of MHz??
> Thanks
>
> Matteo
>
> --
> Matteo TERZI
> Google Gmail Member
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Filter questions

[Chuck McManis]

FWIW, minicircuits is a pretty common place to go for filters, lnas, etc.
You can get a well characterized unit and be confident it will work the way
you expect. If you have enough RF gear to characterize stuff then you can
find things on tindie and AliExpress which are cost effective. But
consistency and quality can be highly variable.

On Thu, Apr 26, 2018, 9:46 AM Dominic Spill  wrote:

> On 26 April 2018 at 07:50, Brian Gieryk  wrote:
> >
> > What design programs or suppliers are folks using for RF filtering,
> external to the HackRF?
> >
> > Looking for band pass specifically, multi band, electronically
> switchable and capable of TX (HackRF output power level only).
> >
> > Thanks in advance for any and all ideas and direction!
>
> I'm sure others will have more useful suggestions, especially if you're
> planning to design your own, but I wanted to mention that I've had some
> success with filters from Mini Circuits -
> https://www.minicircuits.com/WebStore/Filters.html
>
> My experience/knowledge tends to end as soon as we hit the analog domain,
> so I have no idea how they perform compared to other suppliers or if they
> offer products for your more complex requirements.
>
> Thanks,
>   Dominic
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Building a HackRF

[Chuck McManis]

I applaud your effort!

Some things to note however, the HackRF design is a bit 'old' in the terms
of chips it uses. Some have already have end-of-life notices (which often
has the general meaning that production has stopped of new parts). AFAICT
all of the parts are still available but they are getting scarcer. That
said, if you're just building a 2 or 3 boards you can often request a
manufacturer to sample you up to 10 pieces for this sort of
prototype/exploratory work. They will ask questions like "when do you
expect to go into production" and "what sort of run rate will you be
requiring (units per month/year))" I typically answer those questions with
"this is exploratory work to test component compatibility for our design
target, in the event that we decide to go to production with this design it
would be several thousands of units a year." All of those statements are
true but the probability of that particular future might be quite low. I
got there after talking with a field representative for Analog devices who
was anxious to give me parts to play with but he had to "check the box"
with respect to sizing the opportunity. He suggested much of the wording as
something he could pass along and check the box, but would not be construed
as an obligation by his management to call this a design "win". So when
they came back later and said "What did that FizzBuzz Electronics product
turn into?" He could say "They've gone a different way" and not catch any
flack for giving me samples (which the FAEs know getting out into builders
hands creates word of mouth buzz) from a corporate bean counter that might
want to compare sample numbers to unit sales. Generally its in the noise so
hard to draw any specific conclusions.

Building SDRs is a fairly nichey but lucrative target for these guys so
they want to keep themselves in front of the engineers who are actually
building hardware.

--Chuck


On Thu, Mar 1, 2018 at 7:39 AM, Munson, Jonathan (Jon) (MAJ) <
jvmun...@nps.edu> wrote:

> Ladies and Gentlemen,
> I am planning to build one or two HackRF Ones based on the BOM and stuff
> already provided at github.
>
> My initial survey of DigiKey, Mouser and Newark/Farnell yielded some
> requirements not yet met. One chip basically requires a min 2500 order, and
> several I need to request quotes (which I've done, simply waiting on that).
>
> I would appreciate any guidance and pointers from anyone who has recently
> acquired the parts and assembled a HackRF. Especially helpful also would be
> an updated BOM or even equivalent parts lists that are known to work.
>
> Respectfully,
>
> Jon
>
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] I only get flat noise in gnuradio

[Chuck McManis]

Hi Juan,

That is great, because the other software works fine with the HackRF and
hackrf_info finds it and it is up to date, it means that your hackrf
hardware works and the drivers are all correctly installed and recognizing
it. The problem is in the set up or configuration gnuradio. I have found
the #gnuradio IRC channel on freenode to be helpful for configuration
issues like these.

--Chuck


On Thu, Feb 22, 2018 at 12:25 AM, Juan Antonio 
wrote:

> I can not get the hackrf to work well with gnuradio, the only thing that
> comes out in qtgui_freq_sink or in qtgui_sink_ is flat noise with the peak
> of the offset dc in the center.
>
> He intentado diferentes  niveles de ganancia pero no hay cambios en el
> spectro
>
>
> however with gqrx or in windows with the analyzer of pavsa the hackrf
> behaves perfectly
>
> This is my hackrf.
>
> hackrf_info version: 2018.01.1
> libhackrf version: 2018.01.1 (0.5)
> Found HackRF
> Index: 0
> Serial number: a06063c82566ad5f
> Board ID Number: 2 (HackRF One)
> Firmware Version: 2018.01.1 (API: 1.02)
> Part ID Number: 0xa000cb3c 0x00474f57
>
>
> Thank you
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Hack RF One - Ok or not?

[Chuck McManis]

A good source of info on this is the hackrf wiki :
https://github.com/mossmann/hackrf/wiki/Updating-Firmware

The latest releases are here: https://github.com/mossmann/hackrf/releases

Updating the firmware requires no coding, just running the tools.
--Chuck


On Sun, Feb 18, 2018 at 12:27 PM, Robert Edwards  wrote:

> A  question I would like advice on please. I have some basic C and Fortran
> but no python.
>
> I have bought a Hack Rf One. I might buy more if I can this one working.
>
> From hackers_info on my terminal I get
>
> hackrf_info version: unknown
> libhackrf version: unknown (0.5)
> Found HackRF
> Index: 0
> Serial number: a06063c82520485f
> Board ID Number: 2 (HackRF One)
> Firmware Version: 2015.07.2 (API:1.00)
> Part ID Number: 0xa000cb3c 0x00504764
>
> on my iMac.
>
> Is this ok or is my Firmware and librhackrf out of date and how do I fix
> that?
>
> Many thanks.
>
>
>
>
>
>
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Replacing the LNA/PA

[Chuck McManis]

Robert, are you looking to fix a broken HackRF or are you re-designing it
to eliminate the use of an obsolete part? If its the former, the part is
still available and if history is any guide it will continue to be
available in piece parts and lots of various sizes for several years.
--Chuck


On Sat, Feb 17, 2018 at 10:18 PM, Robert Chadwick via HackRF-dev <
hackrf-dev@greatscottgadgets.com> wrote:

> Sorry if this is a duplicate.
>
> Looking at the schematic, it appears the HackRF uses a MGA-81563 for the
> LNA and PA. As these appear to be EOL, and there appear to be many
> complaints about the RX performance of the HackRF, has anyone replaced
> these with something better? While I haven't yet looked closely at
> datasheets to check compatibility and pinout, looking through Digikey
> there appears to be a number of possibilities. Might it be possible to
> fit in a PSA4-5043+ in place of the MGA-81563?
>
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] What kind of antenna to use?

[Chuck McManis]

To add to what Paul said, there are many books written about antennas
because they vary significantly from application to application. Most
people start with the frequency range they want to cover, then directional
or not, then how much gain they hope to get from the antenna, active or
passive, and what sort of bandwidth they are going to be looking at.

That said, pretty much any antenna can see any signal at least a little
bit, so something like the ANT500 is fine when your just noodling around
the various parts of the spectrum.

--Chuck

On Mon, Feb 5, 2018 at 12:41 PM, Jahn  wrote:

> Can you please recommend an antenna for HackRF?
> What kind of antenna do YOU use?
> Thanks
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] What kind of SMA connector

[Chuck McManis]

There is only one 'size' of SMA connector. There is also "RP-SMA" which
stands for "Reverse Polarity SMA" and that gets people sometimes, its the
same diameter and thread pitch so you can connect two connectors together
without any signal going through them.

On Fri, Feb 2, 2018 at 10:36 AM, Jahn  wrote:

> I expected  more  SMA connectors to be there and they differs in diameter.
> Or SMA connectors have the only ONE diameter?
> Thanks
>
>
>
> > Male SMA
> >
> >
> > http://www.wellshow.com/technical-support/connector-
> support/what-is-an-sma-connector/
> >
> >
> > [http://www.wellshow.com/wp-content/uploads/2011/08/
> 2011EQA_logo_400x185.jpg] technical-support/connector-support/what-is-an-sma-connector/>
> >
> > What is an SMA Connector? | Wellshow -RF Connector, RF ...<
> http://www.wellshow.com/technical-support/connector-
> support/what-is-an-sma-connector/>
> > www.wellshow.com
> > SMA connector are coaxial RF connectors developed in 1960s and SMA is
> the abbreviation of SubMiniature version A. SMA connector has a 50ohm
> impedance, 1/4-36
> >
> >
> >
> >
> >
> > 
> > De : HackRF-dev  de la part
> de Jahn 
> > Envoyé : 2 février 2018 13:02
> > `A : hackrf-dev@greatscottgadgets.com
> > Objet : [Hackrf-dev] What kind of SMA connector
> >
> > I would like to use HackRF with my own antenna.What kind of SMA
> connector I must use
> > with my antena so that it will fit together with HackRF device?
> > Thanks
> >
> >
> > ---
> > This email has been checked for viruses by Avast antivirus software.
> > https://eur02.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwww.avast.com%2Fantivirus=02%7C01%7C%
> 7C142211c5d36b43e051f208d56a671aaa%7C84df9e7fe9f640afb435
> %7C1%7C0%7C636531913416697993=5k6GwRAckJowUPYQiDEK8gcTm5%
> 2B9h1J0zX9G1YnhMBk%3D=0
> >
> > ___
> > HackRF-dev mailing list
> > HackRF-dev@greatscottgadgets.com
> > https://eur02.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fpairlist9.pair.net%2Fmailman%2Flistinfo%
> 2Fhackrf-dev=02%7C01%7C%7C142211c5d36b43e051f208d56a671aaa%
> 7C84df9e7fe9f640afb435%7C1%7C0%7C636531913416697993=
> zBVaP8ZMxwSC%2Fcbqm3JSpY9fSBnGmdk5l0k2gyz7Wq0%3D=0
> >
>
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] generate a dvb-t channel

[Chuck McManis]

No it cannot. (generate a DVB-T channel). However, if you generate the
base band data for a DVB-T channel on your PC you could send it to the
HackRF for transmission. The bandwidth requirements are 6.82Mhz which
is well within the 20Mhz BW the HackRF can transmit.

--Chuck

On Wed, Jan 31, 2018 at 4:31 AM, Juan Antonio  wrote:
> Hi, I was thinking about buying a hackrf. One of the utilities that I wanted
> to give was to generate a dvb-t channel. I have read everything I could
> about it but it is not clear to me whether it can be done or not. I would
> appreciate your help in this theme
>
> Best  regards
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Domain Regulatory update

[Chuck McManis]

It is the WiFi driver (cfg80211 is "configure 802.11" and ath is the
Atheros driver). Wifi runs in different bands in different countries.
You should not run the US profile in Irelend (IE), in the UK you get 2
more channels[1]. So with a US config it won't work with a IE router
that is using channel 12 or 13.

[1] 
https://www.juniper.net/documentation/hardware/netscreen-appliances/5gtwireless/wireless_channels.pdf


On Tue, Sep 12, 2017 at 11:47 AM, Srinivasan via HackRF-dev
 wrote:
> Hi There,
>
> I received following message in dmesg :
> [  149.072914] ath: EEPROM regdomain: 0x8348
> [  149.072917] ath: EEPROM indicates we should expect a country code
> [  149.072919] ath: doing EEPROM country->regdmn map search
> [  149.072921] ath: country maps to regdmn code: 0x3a
> [  149.072923] ath: Country alpha2 being used: US
> [  149.072924] ath: Regpair used: 0x3a
> [  149.072926] ath: regdomain 0x8348 dynamically updated by country IE
> [  149.072958] cfg80211: Regulatory domain changed to country: US
> [  149.072959] cfg80211:  DFS Master region: FCC
> [  149.072961] cfg80211:   (start_freq - end_freq @ bandwidth),
> (max_antenna_gain, max_eirp), (dfs_cac_time)
> [  149.072964] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A,
> 3000 mBm), (N/A)
> [  149.072967] cfg80211:   (517 KHz - 525 KHz @ 8 KHz, 16
> KHz AUTO), (N/A, 1700 mBm), (N/A)
> [  149.072969] cfg80211:   (525 KHz - 533 KHz @ 8 KHz, 16
> KHz AUTO), (N/A, 2300 mBm), (0 s)
> [  149.072971] cfg80211:   (549 KHz - 573 KHz @ 16 KHz), (N/A,
> 2300 mBm), (0 s)
> [  149.072973] cfg80211:   (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A,
> 3000 mBm), (N/A)
> [  149.072975] cfg80211:   (5724 KHz - 6372 KHz @ 216 KHz),
> (N/A, 4000 mBm), (N/A)
>
> Is this is something to do with HackRf or something else.
> Please see screen shot at : http://imgur.com/a/8Z0bd
>
> Regards
>
> Srinivasan
>
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

[Hackrf-dev] Performance tuning under virtual box

[Chuck McManis]

For reasons that are sad, I have been trying to re-create my previous
HackRF set up under virtual box. But if I try to use the ALSA Audio sink
under virtual box it goes nuts (in a bad way) stuttering, gui hangs, lots
of aUaUaUaUaU in the console. If I put it to a WAV file then go back and
play the wave file its mostly fine (an occasional stutter but otherwise
solid). So that suggests to me there is some 'trick' to using audio sinks
in virtual box. Has anyone tweaked this to work for them? (I did slow the
audio stream to 16kHz to see if that helps, and at least it doesn't hang
the gui but it doesn't actually reproduce acceptable audio either. And yes
I've got the all the Vbox helper extensions installed)

--Chuck
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Fwd: HackRF for preliminary FCC home test?

[Chuck McManis]

I am not sure exactly what you are asking.

If you want to get FCC certification for your device, there is a process it
is documented at the FCC web site here:
https://www.fcc.gov/engineering-technology/laboratory-division/general/equipment-authorization

That pretty much outlines the steps. If you are using a manufacturer
supplied radio stack you may be able to leverage their certification but if
you wrote your own stack you will need to do the authorization
independently. There are a number of consultancies in the US who will
handle the process for you (for a fee of course). A long time ago (2006) I
was on a project that needed such certification and the vendor hired
charged $50,000 and it took four months to complete. They did all the
required paperwork and followed up on all of the questions the FCC had,
they also flew out an engineer to an FCC certified test facility to get the
verification tests done. (I live in the San Francisco bay area and the FCC
testing facilities around here are typically reserved months, if not years,
in advance it seems).

--Chuck

On Fri, Aug 4, 2017 at 1:00 PM, Sergey Ivanov  wrote:

> Is there someone who did this or similar task before?
> Any specific suggestions?
>
>
>
> On 4 August 2017 at 21:57, Andrew Rich  wrote:
>
>>
>> You can do what ever you like as long as you understand the rules for a
>> licence and GNU Radio
>>
>> Andrew
>>
>>
>>
>>
>> On 5 Aug 2017, at 4:26 am, Sergey Ivanov  wrote:
>>
>> Hi All!
>>
>> I have a product which uses nRF24L01+  2.4 GHz modules for communication.
>> Now we have plans to go to North America market, and I am not sure if my
>> Chinese nRF modules can pass FCC test. If they can't, then I need to
>> re-design my PCB (now I use 2 layers logic board and nRF on a socket).
>>
>> Can I use HackRF to imitate FCC test on my workbench?
>>
>>
>> ___
>> HackRF-dev mailing list
>> HackRF-dev@greatscottgadgets.com
>> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>>
>>
>>
>
>
> --
> Best Regards,
>
> Sergey Ivanov
> +7 910 424 9895 <+7%20910%20424-98-95>
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Need a hand

[Chuck McManis]

Well I've been rebuilding everything from source with pybombs because of my
other issue. That said, what does 'can't get osmocom source to come up in
Mac OS' mean? Are you running gnuradio-companion? If so did you scroll all
the way to the bottom of the module list on the right hand side, and open
up the "no module specified" group, and look in there for osmosdr_source ?

--Chuck


On Tue, Aug 1, 2017 at 10:28 PM, Andrew Rich 
wrote:

> I can't  get osmocom source to come up in Mac OS X so I can use my hack rf
>
> I have issued
>
> sudo port install gnuradio +full
> sudo port install gr-osmosdr +full
> sudo port install hackrf
>
> What am I missing ?
>
> Andrew
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] what is the story with gr-osmosdr not building?

[Chuck McManis]

Okay, that was funny.
--Chuck

On Mon, Jul 31, 2017 at 11:49 PM, Anon Lister <listera...@gmail.com> wrote:
> Builds fine for me. I suggest you try posting on discuss-gnuradio (if that
> is your end goal, see below,) however I suggest you first read [1] and [2].
> Specifically, list your goal(you mention gr-osmosdr, then the LimeSDR, on
> the hackrf mailing list, with no mention of your end goal), what you have
> tried sofar(did you build any other pieces of code first? What was the
> result of that?), and any error messages you encountered. This will help
> people better understand what your trying to do and explain the meaning of
> any error messages you are getting.
>
> The LimeSDR is a fairly new device, and the best place to ask questions
> about it seems to be the discourse page from myriadrf, found at [3] or you
> can visit their wiki found at [4] (However, once again, read [1] first.) It
> sounds like your new to Linux, if you just want to listen to radio, perhaps
> look at SDRConsole for a native windows program, which has a lower learning
> curve, and is closed source.)
>
> [1] http://www.catb.org/esr/faqs/smart-questions.html
> [2] http://xyproblem.info
> [3] https://discourse.myriadrf.org/c/projects/limesdr
> [4] https://wiki.myriadrf.org/Lime_Suite
>
> Cheers,
> -Anon
>
> On Aug 1, 2017 1:50 AM, "Chuck McManis" <chuck.mcma...@gmail.com> wrote:
>
> Hi Dominic,
>
>> We're not in a position to support LimeSDR on this mailing list,
>
> I know, I much prefer my HackRF :-). Up to now I've "gotten away" with
> just using the packages rather than go into the FOSS dungeon to smelt
> metal to cast parts for a lathe so that I can create the tools that I
> need to get something done. Consider it an expression of my
> frustration. So begins my entry into the third level of hell, perhaps
> I'll blog about it :-). It does surprise me that HEAD on a 'major'
> package like gr-osmosdr would not even be buildable, (because that is
> typically the first test prior to merge a commit, does it still build)
> but as I've been digging into it, some of the inter-relationships
> between gnuradio, what Ettus started with (aka the uhd API) and the
> current state of affairs (about a half dozen SDRs bodged into the
> framework in one way or another) that the situation is far from
> "simple."
>
> Since the HackRF stuff seems to be the most effectively integrated SDR
> I just assume all the pros are here who already know all this stuff.
>
> --Chuck
>
> On Mon, Jul 31, 2017 at 10:22 PM, Dominic Spill <domini...@gmail.com> wrote:
>> On 30 July 2017 at 22:51, Chuck McManis <chuck.mcma...@gmail.com> wrote:
>>>
>>> Every day I regret spending money on this LimeSDR unit, and the only way
>>> to talk to it is with 'SoapSDR' driving it through gr-osmosdr. Now why
>>> gr-osmosdr can't drive it directly? Who knows but still I thought I would
>>> rebuild gr-osmosdr from source and it dies horribly trying to build RTL
>>> stuff.
>>
>> Hi Chuck,
>>
>> We're not in a position to support LimeSDR on this mailing list, there's
>> no
>> link between the projects and I don't have access to the hardware.  I
>> don't
>> know if LimeSDR has a support channel, but I would recommend contacting
>> them
>> or other LimeSDR users as they will likely have experience with building
>> LimeSDR support for GNU Radio.
>>
>> Thanks,
>>   Dominic
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] what is the story with gr-osmosdr not building?

[Chuck McManis]

Hi Dominic,

> We're not in a position to support LimeSDR on this mailing list,

I know, I much prefer my HackRF :-). Up to now I've "gotten away" with
just using the packages rather than go into the FOSS dungeon to smelt
metal to cast parts for a lathe so that I can create the tools that I
need to get something done. Consider it an expression of my
frustration. So begins my entry into the third level of hell, perhaps
I'll blog about it :-). It does surprise me that HEAD on a 'major'
package like gr-osmosdr would not even be buildable, (because that is
typically the first test prior to merge a commit, does it still build)
but as I've been digging into it, some of the inter-relationships
between gnuradio, what Ettus started with (aka the uhd API) and the
current state of affairs (about a half dozen SDRs bodged into the
framework in one way or another) that the situation is far from
"simple."

Since the HackRF stuff seems to be the most effectively integrated SDR
I just assume all the pros are here who already know all this stuff.

--Chuck

On Mon, Jul 31, 2017 at 10:22 PM, Dominic Spill <domini...@gmail.com> wrote:
> On 30 July 2017 at 22:51, Chuck McManis <chuck.mcma...@gmail.com> wrote:
>>
>> Every day I regret spending money on this LimeSDR unit, and the only way
>> to talk to it is with 'SoapSDR' driving it through gr-osmosdr. Now why
>> gr-osmosdr can't drive it directly? Who knows but still I thought I would
>> rebuild gr-osmosdr from source and it dies horribly trying to build RTL
>> stuff.
>
> Hi Chuck,
>
> We're not in a position to support LimeSDR on this mailing list, there's no
> link between the projects and I don't have access to the hardware.  I don't
> know if LimeSDR has a support channel, but I would recommend contacting them
> or other LimeSDR users as they will likely have experience with building
> LimeSDR support for GNU Radio.
>
> Thanks,
>   Dominic
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

[Hackrf-dev] what is the story with gr-osmosdr not building?

[Chuck McManis]

Every day I regret spending money on this LimeSDR unit, and the only way to
talk to it is with 'SoapSDR' driving it through gr-osmosdr. Now why
gr-osmosdr can't drive it directly? Who knows but still I thought I would
rebuild gr-osmosdr from source and it dies horribly trying to build RTL
stuff.

---Chuck
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Visualising 1090 MHz ADS-B

[Chuck McManis]

Hi Andrew,

I don't know if you're coming at this from the Software side or the Radio
side but here is a good start:
https://www.elttam.com.au/blog/intro-sdr-and-rf-analysis/
That and watch *all* of the videos on the GreatScott Gadgets site

--Chuck


On Sat, Jul 8, 2017 at 6:17 PM, Andrew Rich 
wrote:

> Ok I have just watched a video
>
> I is an amplitude sample in time
> Q is an amplitude sample in time
>
> They are just a little bit apart
>
> So what does an SDR program do with the I and Q ?
>
> How does it know when to start sweeping across the screen ?
>
> Sent from my iPhone
>
> > On 9 Jul 2017, at 11:01 am, Andrew Rich 
> wrote:
> >
> > Ok my center frequency is 1090 MHz
> >
> > The on off rate is 1 MB/s I think from memory
> >
> > I have noticed the sampling rate determines the frequency span 10 MHz =
> 10 MHz
> >
> > So there is a stream of I and Q coming out
> >
> > What is I and Q telling me ?
> >
> > Is I how far along the scan it is ?
> >
> > And is Q telling me how big the signal
> > Is ?
> >
> > Would an IQ file contain a whole heap of scans ?
> >
> > I = X axis
> > Q = Y axis
> >
> > I would need to sample fast enough as to not miss an amplitude change I
> want to see
> >
> > I guess an IQ file is not plain text but 8 bit numbers packed ?
> >
> > Does it go IQIQIQIQ ?
> >
> > What relationship is I and Q to the center frequency ?
> >
> > I think the signal amplitude resolution is described as 8 or 12 bits ?
> >
> > So as the ADC is pumping out numbers, which it has no control over , it
> is just sampling the signal.
> >
> > Why does it not just out put values of amplitude ? Or is that what the I
> is about ?
> >
> > I am just trying to work out if I record 1090 MHz which is basically OOK
> on off keying, what would be contained in the file ?
> >
> > Am I right with the 8 bits , IQIQIQ ?
> >
> > Andy
> >
> > Sent from my iPhone
> >
> >>> On 9 Jul 2017, at 5:18 am, Cinaed Simson 
> wrote:
> >>>
> >>> On 07/08/2017 06:44 AM, Gregory Ratcliff wrote:
> >>> Great request!  I would like to see this also.
> >>>
> >>> Greg
> >>> Nz8r
> >>>
> >>> Sent from my iPad
> >>
> >> A flowgraph as in gnuradio?
> >>
> >> Don't know.
> >>
> >> How about a python script using qt and gnuradio?
> >>
> >> Try
> >>
> >>  https://github.com/bistromath/gr-air-modes
> >>
> >> You'll need to build it - might need a development environment.
> >>
> >> If you know what you're doing then you could probably build a flow graph
> >> from gr-air-modes python scripts.
> >>
> >> -- Cinaed
> >>
> >>
> >>
> >>
> >>
> >>
> >>>
> >>> On Jul 8, 2017, at 6:23 AM,  >>> >  >>> > wrote:
> >>>
>  Hello Guys
> 
> 
> 
>  I have a hack rf, GNURadio and MacBook Pro
> 
> 
> 
>  Can someone point me towards a flow graph that would show me the
>  pulses on 1090 MHz
> 
> 
> 
>  Showing the preamble and 56 and 112 bits please
> 
> 
> 
>  Andrew
> 
> 
> 
> 
> 
>  ___
>  HackRF-dev mailing list
>  HackRF-dev@greatscottgadgets.com  greatscottgadgets.com>
>  https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
> >>>
> >>>
> >>> ___
> >>> HackRF-dev mailing list
> >>> HackRF-dev@greatscottgadgets.com
> >>> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
> >>>
> >>
> >> ___
> >> HackRF-dev mailing list
> >> HackRF-dev@greatscottgadgets.com
> >> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
> >
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] not so good experience for my first SDR

[Chuck McManis]

Based on that picture, are you really trying to set the HackRF to a 32Mhz
sample rate? That won't work, but 10Mhz would (as would 20Mhz on relatively
modern computers).

--Chuck


On Mon, Apr 10, 2017 at 11:16 AM, mohammed hamoud alkindy <
moham...@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 
> *Date: *Monday, April 10, 2017 at 9:38 PM
>
> *To: *Mohammed AlKindy 
> *Cc: *"hackrf-dev@greatscottgadgets.com >> hackrf-dev" <
> HackRF-dev@greatscottgadgets.com>
> *Subject: *Re: [Hackrf-dev] not so good experience for my first SDR
>
>
>
> On 10 April 2017 at 11:25, mohammed hamoud alkindy <
> moham...@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 
> > Date: Monday, April 10, 2017 at 9:21 PM
> >
> > To: Mohammed AlKindy 
> > Cc: "hackrf-dev@greatscottgadgets.com >> hackrf-dev" <
> HackRF-dev@greatscottgadgets.com>
> > Subject: Re: [Hackrf-dev] not so good experience for my first SDR
> >
> >
> >
> > On 10 April 2017 at 10:47, mohammed hamoud alkindy <
> moham...@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 
> > > Date: Monday, March 13, 2017 at 11:11 PM
> > > To: Mohammed AlKindy 
> > > Cc: "n0p [Luis Bernal]" , "
> hackrf-dev@greatscottgadgets.com >> hackrf-dev" <
> HackRF-dev@greatscottgadgets.com>
> > > Subject: Re: [Hackrf-dev] not so good experience for my first SDR
> > >
> > >
> > >
> > > On 13 March 2017 at 13:09, mohammed hamoud alkindy <
> moham...@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]" 
> > > > Date: Monday, March 13, 2017 at 9:33 PM
> > > > To: Mohammed AlKindy 
> > > > Cc: "hackrf-dev@greatscottgadgets.com >> hackrf-dev" <
> HackRF-dev@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 <
> moham...@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  or aUaUaUaU  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@greatscottgadgets.com
> > > > https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
> > > >
> > > >
> > > >
> > > 

Re: [Hackrf-dev] HackRF and Raspberry Pi

[Chuck McManis]

I don't think this question, as asked, can be answered. Is the HackRF
and Raspberry Pi signal compatble? Yes they are. Can you plug a HackRF
into the Raspberry Pi and have it recoginize it and talk to it? Yes
you can. Can you do all the things that people do with HackRFs when
using a Raspberry Pi, no you cannot.

You can start that question from the other side though, like "I do 
with my HackRF and my current machine, can I swap in a Pi and still do
that?" (probably the answer is "no" unless you are just tuning in FM
radio stations).

So here is my recommendation, you will not be able to do anything
other than tune a wider range of frequencies with a HackRF/Pi
combination than you would with a RTL Dongle/Raspberry Pi. The latter
is about $80 total cost US, the former nearly $500. If you want to
tune ranges outside the RTL dongle's tunable range then build an RF
mixer so that you can use to upconvert (or downconvert) signals
outside of the RTL dongle's range into a frequency it can tune to.
Even a mixer/RTL/Pi combo is going to be cheaper than the HackRF.

On Thu, Feb 23, 2017 at 11:05 AM, Marc Pàmies Massip
 wrote:
> Hello,
>
> I wanted to ask if it is feasible to use a HackRF with a Raspberry Pi. I
> have seen that some people use both hardware together, but it sounds strange
> to me considering that the minimum sample rate recommended for the HackRF is
> 8 MHz. A Raspberry Pi can support such a high sample rate? Are there any
> other drawbacks to consider if this combination was to be done?
>
> Thank you in advance.
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] FATAL: No supported devices found to pick from.

[Chuck McManis]

Since you are running in a VM anyway, consider downloading the Pentoo image
as referenced by the GreatScottGadgets site. That is very plug and play
with the HackRF-1. A long shot would be to look for is whether or not you
are a member of group 'plugdev' since your ls of the dev tree showed that
the hackrf is owned by root and only gives  access to root or members of
group plugdev. I don't think hackrf_info would work though if you weren't.




On Wed, Jan 11, 2017 at 10:22 AM, Marc Pàmies Massip 
wrote:

> Hi,
>
> I am having some problems trying to use GNUradio together with a
> HackRF-One. The hardware seems to be fine as the LED lights turned ON and
> it works with SDR# on Windows.
>
> After running command "hackrf_info" on a Linux distro it returns this:
>
> Found HackRF board 0:
> Board ID Number: 2 (HackRF One)
> Firmware Version: 2014.08.1
> Part ID Number: 0xa000cb3c 0x00554743
> Serial Number: 0x 0x 0x466c64c8 0x278a43c7
>
> I can see the device when running the "lsusb" command:
> Bus 002 Device 006: ID 1d50:6089 OpenMoko, Inc.
>
> And that's the output to "ls -l /dev/bus/usb/002/006" (I don't know if it
> will be useful for you)
> crw-rw+ 1 root plugdev 189, 133 ene 11 16:38 /dev/bus/usb/002/006
>
> Until here everything seems to work as expected. The problem comes when I
> execute a flowgraph with an osmocom source on it, then the program displays
> the following message:
>
> gr-osmosdr v0.1.4-75-gae686c46 (0.1.5git) gnuradio 3.7.10
> built-in source types: file fcd rtl_tcp rfspace redpitaya
>
> FATAL: No supported devices found to pick from.
>
> Trying to fill up 1 missing channel(s) with null source(s).
> This is being done to prevent the application from crashing
> due to gnuradio bug #528.
>
> I am running a Kali Linux as a virtual machine (with VMware), which is
> supposed to include multiple sdr tools. I think that the problem has to do
> with some libraries or tools for HackRF, but when I try to install or
> upgrade libhackrf or hackrf-tools the followin message appears in the
> terminal:
>
> root@kali247:~# apt-get install hackrf-tools
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> E: Unable to locate package hackrf-tools
>
> The same message appears for libhackrf. Any idea of what could be wrong? I
> am a bit lost right now, any help is welcome. I don't know if I am
> missing something, if you need further information just ask.
>
> Thank you for your time,
>
> Marc.
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Ok, this is weird

[Chuck McManis]

And still more additional data, I booted pentoo on my system (gotta love
liveCD boots) and ran the lesson1 config from there, same hardware same USB
setup and no glitching (or underruns) in the audio. So clearly something
changed. Unfortunately there isn't any way I find to audit what Anaconda
did to my system.

Differences in the GRC log between Pentoo system image vs my currently
booting Ubuntu 16.04 image:

Pentoo>  linux; GNU C++ version 4.9.3; Boost_105600;
UHD_003.008.005-0-unknown
Ubuntu> linux; GNU C++ version 5.3.1 20151219; Boost_105800;
UHD_003.009.002-0-unknown

Pentoo> (this line doesn't appear)
Ubuntu> Using Volk machine: avx2_64_mmx_orc

Pentoo> gr-osmosdr v0.1.4-48-g86ad5842 (0.1.5git) gnuradio 3.7.10
Ubuntu> gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.9

Pentoo> Generating: '/home/pentoo/gnu-radio/top_block.py'
 Executing: /usr/bin/python2.7 -u
/home/pentoo/gnu-radio/top_block.py
Ubuntu> Generating: '/freenas/home/cmcmanis/gnu-radio/top_block.py'
 Executing: /usr/bin/python2 -u
/freenas/home/cmcmanis/gnu-radio/top_block.py

Pentoo> (this line doesn't appear)
Ubuntu> gr::log :INFO: audio source - Audio sink arch: alsa



On Mon, Jan 9, 2017 at 9:09 PM, Chuck McManis <chuck.mcma...@gmail.com>
wrote:

> Additional data, if I just queue up three signal sources running at 48K
> and feed a chord into my audio sink at 48khz it doesn't under run and it
> works as expected. (I hear a chord coming out of the audio card). Per the
> FAQ that suggests that sampling from the hackrf to the audio card is losing
> samples somewhere. (and yes it has the two clock problem and yes it
> "occasionally" would dump an aU on the console but this new behavior is a
> constant stream of aU's and really broken up audio) Now to figure out if
> the hackf is dropping data.
>
> --Chuck
>
>
> On Mon, Jan 9, 2017 at 8:31 PM, Chuck McManis <chuck.mcma...@gmail.com>
> wrote:
>
>> One thing that is different is that I installed Jupyter because I wanted
>> to do some of the interactive stuff that was being done in various
>> discussions and tutorials. The Jupyter folks recommend using Anaconda for
>> installing the various dependencies that Jupyter has and now I'm wondering
>> if I've got a library problem.
>>
>> --Chuck
>>
>>
>> On Mon, Jan 9, 2017 at 7:54 PM, Chuck McManis <chuck.mcma...@gmail.com>
>> wrote:
>>
>>> So after setting aside my HackRF for a bit while I worked on other
>>> things, I picked it up today and started working on my FM experiments. I
>>> got a bazillion analog underruns. I went back to the original class version
>>> of an FM receiver and its giving me underruns now as well.
>>>
>>> The underruns make the system continually burp which is not good. I do
>>> regular system updates but there isn't anything pending that requires a
>>> reboot. I've unplugged and replugged the HackRF 1,  It is running 2015.07.2
>>> firmware. I'm pretty sure I updated the CPLD at the same time and tested it
>>> afterwards and it was fine then.
>>>
>>> So what I'm wondering is the process to use to start narrowing down the
>>> issue.
>>>
>>> --Chuck
>>>
>>>
>>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Ok, this is weird

[Chuck McManis]

Additional data, if I just queue up three signal sources running at 48K and
feed a chord into my audio sink at 48khz it doesn't under run and it works
as expected. (I hear a chord coming out of the audio card). Per the FAQ
that suggests that sampling from the hackrf to the audio card is losing
samples somewhere. (and yes it has the two clock problem and yes it
"occasionally" would dump an aU on the console but this new behavior is a
constant stream of aU's and really broken up audio) Now to figure out if
the hackf is dropping data.

--Chuck


On Mon, Jan 9, 2017 at 8:31 PM, Chuck McManis <chuck.mcma...@gmail.com>
wrote:

> One thing that is different is that I installed Jupyter because I wanted
> to do some of the interactive stuff that was being done in various
> discussions and tutorials. The Jupyter folks recommend using Anaconda for
> installing the various dependencies that Jupyter has and now I'm wondering
> if I've got a library problem.
>
> --Chuck
>
>
> On Mon, Jan 9, 2017 at 7:54 PM, Chuck McManis <chuck.mcma...@gmail.com>
> wrote:
>
>> So after setting aside my HackRF for a bit while I worked on other
>> things, I picked it up today and started working on my FM experiments. I
>> got a bazillion analog underruns. I went back to the original class version
>> of an FM receiver and its giving me underruns now as well.
>>
>> The underruns make the system continually burp which is not good. I do
>> regular system updates but there isn't anything pending that requires a
>> reboot. I've unplugged and replugged the HackRF 1,  It is running 2015.07.2
>> firmware. I'm pretty sure I updated the CPLD at the same time and tested it
>> afterwards and it was fine then.
>>
>> So what I'm wondering is the process to use to start narrowing down the
>> issue.
>>
>> --Chuck
>>
>>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

[Hackrf-dev] Ok, this is weird

[Chuck McManis]

So after setting aside my HackRF for a bit while I worked on other things,
I picked it up today and started working on my FM experiments. I got a
bazillion analog underruns. I went back to the original class version of an
FM receiver and its giving me underruns now as well.

The underruns make the system continually burp which is not good. I do
regular system updates but there isn't anything pending that requires a
reboot. I've unplugged and replugged the HackRF 1,  It is running 2015.07.2
firmware. I'm pretty sure I updated the CPLD at the same time and tested it
afterwards and it was fine then.

So what I'm wondering is the process to use to start narrowing down the
issue.

--Chuck
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] source MAX2837

[Chuck McManis]

You could presumably order 50 and become that "extras" supplier :-) I know
that is a pain though.

If you're wondering the LimeSDR which got funded on CrowdSupply uses that
part and they are building like 3K units so they probably sucked the supply
chain dry. One of the reasons I don't like designing in Maxim parts is that
they only run parts when the supply chain is empty so you get big part
availability gaps waiting for the next wafer start.

--Chuck


On Mon, Jan 9, 2017 at 3:01 PM, Juris L  wrote:

> Is there any source for couple of MAX2837, cant find it available from
> usual chip distributors, only 50 pc (factory?) orders ...
> Or maybe someone want to sell some excess ones ?
> Want to build some boards to make experiments with available microwave
> modules with 2.5G IF ...
>
> wbr
>
> Juris
> yl3cb
>
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

[Hackrf-dev] sources of audio underrun?

[Chuck McManis]

Hi all,

I'm building a more sophisticated FM receiver in grc and I find I'm getting
regular audio underruns (aUaUaU ... ) they come in bursts. My CPU
utilization is like 33 - 40% for 3 of the 4 cores, maybe 70% for the fourth
one. What techniques can I use to avoid audio underruns?

--Chuck
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Finding the Interference with directional antenna?

[Chuck McManis]

In the US there is a company called Dish Network (satellite TV) they
use a small dish antenna to talk to the satellites, it also makes a
great starting point for a directional WiFi antenna. Remove the LNB
that is normally in the antenna and tape a WiFi chip antenna at the
focal point. You can then point quite accurately at various WiFi
sources.


is a picture of one of these antennas.

--Chuck

On Tue, Dec 6, 2016 at 5:20 PM, Tamer Çelik  wrote:
> Hello,
> I am having a strange interference issue on my 2.4GHz WiFi network while
> 5GHz band works perfect.
> This might be coming from one of my neighbours.
> Just wanted to ask if its possible to use a "directional" antenna with
> HackRF and explore the area for possible source of interference?
> I am pretty sure on that something jamming 2.4GHz for random intervals.
> Any suggestions?
> Thanks!
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] FM 96.5MHz rx works but 70cm 441.1MHz rx does not?

[Chuck McManis]

Just to check off the obvious question, you are sure the antennae is the
right sex right?

On Nov 9, 2016 6:23 AM, "David Hubbard" 
wrote:

> On Wed, Nov 9, 2016 at 6:10 AM, John Ostrander  wrote:
>
>> David,
>>
>> You're likely receiving it, but 70cm is nbfm not wbfm so you're probably
>> getting loads of noise around the signal you're trying to get at. Try a
>> flowgraph like the one attached, but with the osmocom source of course.
>>
>> regards,
>>
>>
> Thanks, John! I ran your flowgraph tuned to 443.000 and looked for a
> 443.700 signal that was coming in at S9 on my handheld ham radio.
>
> I have attached the flowgraph with my modifications and the screenshot. I
> believe there's no signal. What do you think?
>
>
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] HackRF Win7 64bit

[Chuck McManis]

First, always check your antenna. The whole SMA/SMA-RP thing bites a
lot of people. Connecting an SMA-RP antenna to the Hack-RF will look
like its connected but there will be no signal connection.

Second it is useful to know how effective your antenna is for the
frequencies you are trying to receive. Using a 2.4Ghz "rubber duck"
antenna and trying to pick up FM (< 108Mhz) radio stations won't work.

Third look for sources of noise nearby, radio interference is governed
by the inverse square rule, meaning that if you move a bit away from
an interfering source you reduce interference by the square of the
distance. Sources of interference are things like unshielded computer
boards (a Raspberry Pi sitting out running some application for
example hanging off a USB cable)

--Chuck


On Mon, Apr 25, 2016 at 1:47 PM, David Goldstein
 wrote:
> Hi, I have HackRF in Windows 7 64bit running with SDR#, however, the audio
> is mostly static even with local stations.
>
> Any tips?
>
> It's not reception...
>
> Thanks.
>
> David
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

[Hackrf-dev] useful adapter from Amazon

[Chuck McManis]

Got a couple of these: http://www.amazon.com/dp/B005H488Y4 which are RP-SMA
to SMA adapters which are generally the thing you want to use one of the
zillion GPS/WiFi anntenna's with the HackRF. Since a lot of antennas show
up in surplus shops this was an inexpensive way to make sure they would
talk with the unit. I use a 1/4" drill to remove some of the foam from the
"holder" for the HackRF1 in the box and drop one of these into that hole,
so it is always nearby.

--Chuck
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Help and Support

[Chuck McManis]

Srini, you have remarked about this several times over the last year and
while appreciate your enthusiasm I think this comment:

   > It seems , they don't understand about Radio and 2.4 GHz
Might hit a bit closer to home.  It would suffice it to say that *YOU*
don't understand about Radio and 2.4Ghz and that is why you don't see the
obvious way to answer your own questions, and why we cannot answer them.

2.4Ghz is absorbed by water, because the water molecule forms a small
dipole antenna of the correct length. That is why it is used in microwaves
because it heats the water and that hot water heats the rest of the food.
It is also why it is rarely used for long range communication, as the air
has moisture in it which absorbs the signal, so not only are you fighting
the inverse square law you're fighting atmospheric absorption. When it *is*
used to send a signal more than a mile it is done so with a highly
directional antenna pointing at another highly directional antenna on the
receiving end.

If you are seeing *any* sort of bump in the 2.4Ghz band, the source has to
be less than a mile away and probably less than 1000 meters (or 1km). So
what ever it is you're worried about, it is literally right next to you.
Second 2.4Ghz is *HIGHLY* directional, it doesn't bounce much and bounces
get double absorption so using any sort of directional antenna and a bit of
geometry you could exactly pin point any *SOURCE* of 2.4 ghz power. And in
my experience once you look at the thing sending out the RF energy you now
exactly what it is trying to do.

So build one  using a potato chip can

(or buy
)
a directional WiFi antenna, hook it up, and rotate it around until your
mystery signal peaks. Note your GPS coordinates and the angle with a good
compass. Then drive 500 meters in any direction and do that again, then 500
meters in a *different* direction and do it a third time. (the protects
against you accidentally picking a direction that is in line with the
transmitter). Now take a map, and put your protractor on it, mark your tree
measurement points and the angle. Draw lines out from the point. They will
cross at the point where the transmitter is, go there. Look at the
transmitter and what ever it is will be clear. If it is moving then that
would be another good clue for you.

But here is the thing, you will never figure out what this is just by
observing a signal, you have to go look at it.

--Chuck


On Fri, Jan 1, 2016 at 12:23 AM, Srinivasan T  wrote:

> Hi There,
>
>
>
> I detected unknown RF at 2.4 GHz which is not Wi-Fi.
>
> This RF is not Wi-Fi, Bluetooth or Microwave, It has different FFT
> pattern, waterfall, and sound signature.
>
> This signal also deliver Wi-Fi packets to make people believe it is Wi-Fi
> packets.
>
>
>
> I use AirMagnet XT - 2.4 GHz  and the software also detected unknown
> interference.
>
> Attached my analysis document.
>
> *https://mega.nz/#!YwplVCCT!Acbe00paHk3dLJuf04B5zSBifSw0-bHz5IciiNLgQwY
> *
>
>
>
> *Please see following pages for quick understanding :*
>
> 1. Page 18-19 :  Conclusions
>
> 2. Page 43-46 :  This page contains analysis of Radio
> Sound from 3 aspects : Sound Track, Sound Wave Form,
>
>  Sound WaterFall pattern.
> We can see that huge difference between Wi-Fi 2.4 GHz sound and unknown
> Radio Signal
>
> 3. Page 47-51  : This external signal cause wifi
> fluctuations. Page 47 contains sample Wi-Fi signal from US which is really
> normal.
>
>   Page 50, using AirMagnet
> XT ( 2.4 GHx spectrum analyzer ) we can see that the external interference
> cause nearly 10 channels
>
>   affected. This is
> abnormal interference.
>
> 4. Page 52:  *Relation of RF to human brain
> frequency*
>
> 5. Page 61:  Video as reference, one of video
> :
>
>
>
> *Unknown RF at 2.4 GHz reaction with human body with EEG *
>
> http://sendvid.com/dofuepqn
>
> Details : This video shows the waterfall images. Each time
> we see set lines, the individual
>
> will feel the reaction to body which not able to show to
> any other people. Please see EEG
>
> window at right side at time 6.20 - 6.25 , 6.30-6.40, 6.50
> - 6.55. The spike on EEG is
>
> trigger by external factor and the individual can feel it.
>
>( other pages
> as supporting analysis )
>
>
>
> I reported this issue to 3 RF spectrum managers :
>
> 1. iDA- Singapore
>
> 2. 

Re: [Hackrf-dev] Installation issue libosmo-dsp is empty

[Chuck McManis]

Git clone --recursive will pull the submodules associated with a git repo
as well.

On Mon, Dec 21, 2015 at 11:43 AM, Jon B  wrote:

> I'm working to get an original HackRF One with the old Kickstarter vintage
> firmware up and running an new Mint install.  I'm using pybombs to build
> each piece.
>
> It has been a bit of puzzle but I've finally got it working.
>
> The last problem was the libosmo-dsp directory in the gr_iqbal was empty.
> I'm not that familiar with git but it looks like something might be
> disconnected.  Ultimately I did the get for that directory manually and got
> pybomb to work.
>
> Did I miss something?  Was I supposed to manually pull libosmo-dsp?
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Install GNURadio on Windows

[Chuck McManis]

For what its worth, I started down this road briefly and then gave up
and installed the free VMWare player on my windows machine, and inside
that ran ubuntu and brought up the tools that way. Not sure what that
says about the Windows development environment but it got me up and
running more quickly.

On Sun, Nov 15, 2015 at 8:55 AM, Dominic Spill  wrote:
> On 14 November 2015 at 19:59, Mitja kocjančič  wrote:
>> Hi to all I am trying to install GNU Radio on Windows with osmocom source
>> and sink and HackRF Support So I've tried installing it via this method:
>> https://gnuradio.org/redmine/projects/gnuradio/wiki/WindowsInstall#Chocolatey
>> (after installing lxml and Cheetah manualy) I finaly fired GNU Radio but (as
>> I thougt) it was missing SDR Source and Sink (only UHD stuff were there
>
> It looks like the GNU Radio install from chocolatey uses the binaries
> published by the GNU Radio project [1].
>
>> Is there any way I can manualy add osmocom source and sink into GNU Radio on
>> windows?
>
> You will need to build the HackRF library and tools on your Windows
> system.  You will need libusb [2] and cmake [3], both of which are
> available for Windows, and a compiler such as MinGW.  Instructions for
> building HackRF with MinGW are available [4], or for MSVC[5] which
> should help with building the HackRF and osmocom tools[6].
>
> [1] http://files.ettus.com/binaries/gnuradio/gnuradio_v3.7.3/
> [2] 
> http://sourceforge.net/projects/libusb/files/libusb-1.0/libusb-1.0.20/libusb-1.0.20.7z/download
> [3] https://cmake.org/download/
> [4] https://gnuradio.org/redmine/projects/gnuradio/wiki/MingwInstallMain
> [5] https://lists.gnu.org/archive/html/discuss-gnuradio/2013-08/msg00284.html
> [6] http://sdr.osmocom.org/trac/wiki/GrOsmoSDR
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] HackRF DX 100Km on 1296.1

[Chuck McManis]

On Wed, Sep 23, 2015 at 2:39 PM, C Crane  wrote:
> Unfortunately, nobody seems too interesting in transmitting.

I think that is unfair. Perhaps it is more accurate that the Majority
of HackRF owners are not licensed to transmit, and so they don't.
Because there is tremendous value and fun to be had just on the
receiving side.
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Amateur radio with HackRF One and gnuradio

[Chuck McManis]

You want a ham-it-up adapter if you are doing sub 10 mhz bands
On Sep 8, 2015 6:47 PM, "R. Niles Vaught"  wrote:

> Hello all,
>
> I am looking for either previously constructed or very generous hints on
> how to construct gnu radio blocks to receive and transmit FM signals on the
> VHF UHF amateur radio bands using HackRF One.  I have completed the
> available tutorials from Michael with success, but my personal attempts to
> use HackRF One and gnu radio on the ham bands have resulted in *very*
> poor audio.
>
> Thanks in advance
>
> Niles
> K4RNV
>
> ___
> HackRF-dev mailing list
> HackRF-dev@greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
>
>
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev

Re: [Hackrf-dev] Air relay ADS-B to BTLE: How to add UART LCD and build

[Chuck McManis]

The arm-none-eabi compiler in the packages repo is an abomination :-)
get the one from launchpad, be sure to apt-get add gcc-multilib and
put the compiler in your path, done! Bonus because it is maintained by
ARM and comes with both newlib and newlib-nano specs for really small
code size.

--Chuck


On Tue, Sep 1, 2015 at 11:44 AM, Jiao Xianjun  wrote:
> Hi,
>
> I am planing to open my firmware in several steps. Here is the first step.
>
> (See detailed introduction here: http://sdr-x.github.io/UART1602LCD/ )
>
> When modifying firmware of HACKRF, debugging method is important. Actually
> you may add 1602LCD module and UART to hackrf board without changing
> anything of the board itself. Here are introduction and demo.
>
> 1. Hardware connection
>
> You should have 1602 LCD module and/or USB-UART dongle in your hand. The two
> things are very popular, you may google their information easily.
>
> 1602LCD HACKRF pin connection:
>
>   HACKRF P20 20 -- 1602LCD pin11
>   HACKRF P20 18 -- 1602LCD pin12
>   HACKRF P20 16 -- 1602LCD pin13
>   HACKRF P20 14 -- 1602LCD pin14
>   HACKRF P20 11 -- 1602LCD pin6
>   HACKRF P20  9 -- 1602LCD pin5
>   HACKRF P20  7 -- 1602LCD pin4
>   HACKRFVCC -- 1602LCD pin2 pin15
>   HACKRFGND -- 1602LCD pin1 pin3 pin16
>
> UART HACKRF pin connection:
>
>   HACKRF P25 1 GND-- GND of computer or USB-uart dongle
>   HACKRF P25 4 UART0 RXD  -- TXD of computer or USB-uart dongle
>   HACKRF P25 5 UART0 TXD  -- RXD of computer or USB-uart dongle
>
> For HACKRF P20 and P25 location and definition, you can refer to
> hackrf-one-assembly.pdf and hackrf-one-schematic.pdf in original HACKRF
> github repo.
>
> Photo of my 1602 LCD module connection
>
> Photo of my USB-UART dongle connection
>
> 2. Code example and demo
>
> After some struggling in dark, I finally can present you quite simple code
> to output information via UART or 1602 LCD screen.
>
> All you need are two files: CMakeLists.txt and hackrf_uart_1602lcd.c
>
> Put them in a new created directory hackrf_uart_1602lcd in firmware
> directory of original hackrf github repo, and build the hackrf_uart_1602lcd
> project (See part 3 for build method).
>
> I already put a workable code example here: hackrf-UART-1602LCD
>
> A firmware hackrf_uart_1602lcd.dfu is also put into
> firmware/hackrf_uart_1602lcd/build/ of above repo in case someone want to
> try it in RAM via DFU mode without building firmware.
>
> Here is a demo photo of the firmware running
>
> 3. Build firmware of above code by yourself
>
> Basically you can follow instructions in README of firmware directory in
> original HACKRF github repo to build firmware. For example:
>
>   cd firmware/hackrf_uart_1602lcd
>   mkdir build
>   cd build
>   cmake .. -DRUN_FROM=RAM
>   make
>   dfu-util --device 1fc9:000c --alt 0 --download hackrf_uart_1602lcd.dfu
>   (before dfu-util, make sure set your board into DFU mode)
>
> But somehow I need to do following things to make sure build go smoothly. If
> you can't build firmware, maybe you can give it a shot.
>
> remove "-s 0" in the line of hackrf-common.cmake: (here is a
> hackrf-common.cmake which is already modified)
>
>   COMMAND dfu-suffix --vid=0x1fc9 --pid=0x000c --did=0x0 -s 0 -a _tmp.dfu
>
> add "COMMAND dfu-prefix -s 0 -a _tmp.dfu" after above line in
> hackrf-common.cmake.
>
> Maybe you need to install this: git://gitorious.org/dfu-util/dfu-util.git (I
> already put one here dfu-util.tar.gz)
>
> Maybe you need this: sudo apt-get install python-yaml
>
> sudo apt-get install gcc-arm-none-eabi -- This compiler NOT WORK!!!
>
> USE THIS compiler!!! -->
> https://launchpad.net/~terry.guo/+archive/ubuntu/gcc-arm-embedded
>
> !!! If you are using Ubuntu 14.04 and later, please be careful because there
> are packages with same name but produced by Debian and inherited by Ubuntu.
> Simply follow the above 3 steps, you may end up with gcc-arm-none-eabi from
> Ubuntu. So to install gcc-arm-none-eabi from ARM, steps are:
>
>   1). sudo apt-get remove binutils-arm-none-eabi gcc-arm-none-eabi
>   2). sudo add-apt-repository ppa:terry.guo/gcc-arm-embedded
>   3). sudo apt-get update
>   4). sudo apt-get install gcc-arm-none-eabi=4.9.3.2015q1-0trusty13
>   or
>   sudo apt-get install gcc-arm-none-eabi=4.9.3.2015q1-0utopic14
>
> If you encounter some command not found error, maybe you need:
>
>   cd /usr/lib/arm-none-eabi
>   sudo ln -s /usr/arm-none-eabi/bin bin
>
>
>
> On Sun, Jul 12, 2015 at 10:03 AM, Michael Ossmann  wrote:
>>
>> On Sun, Jul 12, 2015 at 01:00:53AM +, Jason Cooper wrote:
>> >
>> > I should clarify:  I know about the various AIS SDR implementations
>> > out there.  I'm interested in running code on the hackrf with just a
>> > battery pack.  UI being my $mobile_device.
>>
>> That's why I mentioned the PortaPack implementation.  It runs on the
>> ARM.
>>
>> Mike
>
>
>
> ___
> HackRF-dev mailing list
> 

[Hackrf-dev] Questions on the hackrf One

[Chuck McManis]

Very cool gizmo. I've got gnuradio installed and gqrx running and
playing with that (fun to listen to ATC traffic around the Bay Area).
I tried to install gr-bluetooth with pybombs but that blew up on the
lack of a libtbb and in hunting that down it seems that really
gr-bluetooh is more about the Ubertooth than the HackRF, I'm wondering
if that is a structural problem or what? Can I use the HackRF at
Bluetooh/Zigbee frequencies? (they are all 2.4Ghz range) Does the
Ubertooth do more? less? about the same?

My target is that I'm developing beacon software that will be using
both BTLE and Zigbee. For a variety of reasons I'm using a soft radio
and would like to be able to validate its signals beyond simply having
at least one other non-soft radio receive the signal.

--Chuck
___
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev