Hello M.Munir,
By default, USRP gives you data in 16bit integer format (x2, for I and Q).
GNU Radio's complex data type uses IEEE754 single precision (x2, for I and
Q). The data type is converted by UHD (the USRP driver). Each IEEE754 data
point requires 32bit of storage (or memory, bandwidth,
Dear All,
I am confused to understand a behavior of GNURADIO USRP Source block. The
problem is,
1. I connected USRP N200 with my PC.
2. I set both the cahnnels of USRP
3. I set the sampling rate of both as 5MHz
4. I connected one channel directly to the Frequency Sink Block
5. I connected the 2nd
Have just looked at your code from my mobile.
You want to check numpy.log10 and numpy.greater (there will be other ways
to do the same thing).
On Tue, Jan 2, 2018, 20:18 Gilad Beeri (ApolloShield) <
gi...@apolloshield.com> wrote:
> This is related to Python, not GNU Radio per se. It seems that
This is related to Python, not GNU Radio per se. It seems that you pass in1
to math.log10().
I assume that you define in1 as input_items[1], which is a list of items to
process (not a single item), while the log function expects to get a float,
not a list.
Something like:
for item in in1:
c =
Hello Guys
I'm creating a customized block in the GNU Radio framework using python
that takes in a number of input items and once that number of input items
surpasses a certain number, 1024 of the input items are taken and stored
into an array, and then those items are converted to dB and lastly
Hello,
I am trying to wrap my head around a project, and I have a bunch of
question I am not able to find an answer for. Hopefully someone can point
me in the right direction.
I am trying to decode an EPIRB signal [1] with gnuradio. The signal (400
bps) is phase modulated +/- 1.1 rad with the
If one uses gr::block and ::general_work, then I believe that there are no
constraints on the I/O streams & one can have generalized ninput and noutput
items on each stream.
It's when one moves to specialized blocks (e.g., gr::sync_block,
gr::sync_interpolator, gr::tagged_stream, etc), that
Correction: sync_block guarantees number of inputs (on each port) to be
equal to number of outputs. The sync_decimator and sync_interpolator
allow number of inputs (on each port) a 1:N or N:1 relationship between
input and output. Sorry for the confusion.
On 01/02/2018 08:07 AM, Jeff Long
Yes, you'll get the same number of samples on both inputs if you derive
from sync_block. For example, here is the code from the "add" block:
add_ff_impl::work(int noutput_items,
gr_vector_const_void_star _items,
gr_vector_void_star _items)
{
float *out = (float *) output_items[0];
Hi Michael,
Thank you very much for the detailed explanation. I have one more query -
If a block has two input streams, will the no of items be same in both
streams? say for example I build a block that takes I and Q samples as
input and the algorithm demands I sample and its corresponding Q
10 matches
Mail list logo
