Heio SDR people,
on https://twitch.tv/gnuradio, the GNU Radio dev call is about to start.
I'd like to remind everyone that asking questions there, in our #gnuradio:gnuradio.org
Matrix room, or on the bridged #gnuradio on the libera IRC network, and also on Discord,
is heavily encouraged!
Right. Of course you can just use one loop of noutput_items * vlen
iterations.
Technically noutput_items says how many items you may write, not how many
the scheduler is delivering (implying input). In a sync block, they are the
same though, unless you overwritten forecast().
On Thu, Apr 21,
Hi Jeff,
Thanks for your reply!
So let me make certain that I understand correctly your response where you
said there were 16*512 samples (8192 samples). So I take it that noutput_items
(which has alternating values of 15 and 16 when printed to the screen) tells
me the number of vectors of vlen
Hi Marcus,
Thanks for offering to assist me.
The OOT signal processing blocks I have designed so far worked with
streaming data. For this project, I wish to pass the data in as vectors
(which is new to me). I am writing this OOT block to accept a vector
of 100 floating point elements on each
Hi Jeff,
Thank you very much!
George
On Thu, Apr 21, 2022 at 12:21 PM Jeff Long wrote:
> Right. Of course you can just use one loop of noutput_items * vlen
> iterations.
>
> Technically noutput_items says how many items you may write, not how many
> the scheduler is delivering (implying
You'll have to tell us what you do with that `data` and what the io_signature of your
block is.
On 20.04.22 17:22, George Edwards wrote:
Hello GNURadio Community,
In an OOT QA testing of a signal processing block designed to accept an input vector of 4
elements, I am having problems passing
Hello GNU Radio community and friends of UHD,
On behalf of everyone at NI/Ettus Research, I am pleased to announce the
release of UHD 4.2[1], the latest version of the USRP Hardware Driver! UHD
4.2 brings new enhancements to the USRP X410, notably:
* A new shipping bitfile, X410_CG_400, enabling
