Hi,
great you got it working. AFAIK, there is not *the* XBee module, but
very different modules are sold as XBee. Some of them support standard
compliant IEEE 802.15.4/ZigBee (O-QPSK in 2.4GHz). They will work with
the OOT.
Best,
Bastian
On 8/31/19 8:29 PM, Tellrell White wrote:
> Thanks
> pybombs prefix init ~/gnuradio -R gnuradio-default
gnuradio-default.lwr recipe is 3.7. Edit the recipe in
.pybombs/recipes/gr-recipes
and replace gnuradio with (in order to call gnuradio38.lwr)
depends:
- gnuradio38
and in gnuradio38.lwr
gitbranch: master -> gitrev: v3.8.0.0
(since
This is my first time using GNU radio.
The 3.8 release is what I wish to use as it supports PyQt5.
I am follow the instructions from the Wiki.
But it seems that I ended up with a 3.7 install after some issues
that I'll describe.
Specifically:
pip3 install --user pybombs
pybombs auto-config
On Sun, Sep 1, 2019 at 3:15 AM Adrian Musceac wrote:
> I'd like to know what happens if the block's work function does not finish
> within the time allotted to it.
> Is part of the input/output buffer dropped, or does it interfere with the
> sample rate of the next blocks?
>
GNU Radio's flow
Anyone has experience with the real world impact of using gcc -ffast-math
with SDR in general, and GNURadio/Volk in particular?
--Albin SM6WJM
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
Hi,
I found this thread very useful, and I have another question regarding the
scheduler internals.
It is my understanding from reading documentation that each block's *work*
or *general_work* function
will be called at the highest sample rate that the block will see, whether
that is on the input
