Hey everyone,
I'm on a USRP doing some prototyping of a simple packet radio. I wanted to
ask the best method for detecting bursts. GNU Radio seems to support both a
'probe' e.g.
probe = gr.probe_avg_mag_sqrd_c(thresh,alpha)
detected = probe.unmuted()
from tunnel.py, and a 'file sink burst tagger
On 08/03/2012 02:16 PM, Alexander Olihovik wrote:
> Ideally, I'd like to have 1 items on each port every time work() is
> called, since my sink will be sending 10k snapshots of data to another
> algorithm.
> Right now, since I don't have that many items on each port, I'm looking for
> the min
> I checked the archives and someone mention it could be related to the
> version of libusb? Is there any particular versions of libusb i should
> be using?
>
hmm... can you try the uhd's next branch? There was some bus work to
add a feature, in case there was a bus issue, this will do the tric
Ideally, I'd like to have 1 items on each port every time work() is
called, since my sink will be sending 10k snapshots of data to another
algorithm.
Right now, since I don't have that many items on each port, I'm looking for
the minimum number of items on all ports, saving that number of items
Mark this one resolved. I was just missing something from my XML file.
On Tue, Jul 31, 2012 at 4:59 PM, Jonathan Fox <31...@cardinalmail.cua.edu>wrote:
> Thanks. I completely forgot about the filters in the front of the
> flowgraph. Removing them fixed the problem.
>
> I still have not figured ou
I run benchmark_tx in USRP A, and benchmark_rx in USRP B:
A: ./benchmark_tx.py -f 2.46G -r 0.5M --tx-gain=-30
B: ./benchmark_rx.py -f 2.46G -r 0.5M
The n_right/n_recvd is 549/628.
But when I rx in USRP A and tx in USRP B with the same parameters, the
n_right/n_recvd is always pretty bad: 0/275.
Wha
On Fri, Aug 03, 2012 at 02:23:39PM -0400, Alexander Olihovik wrote:
> It seems as if the gr_sync_block is close to what Josh Blum refers to as an
> Arbitrary Ratio Block in his Blocks Coding Guide.
Read the guide again :)
that's not at all what it is.
This might also help:
http://gnuradio.org/red
It seems as if the gr_sync_block is close to what Josh Blum refers to as an
Arbitrary Ratio Block in his Blocks Coding Guide.
Do you think if I were to use the forecast() function and make all
ninput_items_required[i] to be the same set amount, I would always have the
same number of input_items[i]
On Fri, Aug 03, 2012 at 01:38:38PM -0400, Alexander Olihovik wrote:
> There are a few cases when input_items[0] doesn't equal input_items[1]. If
> say,
> len(input_items[0]) = 1000 and len(input_items[1]) = 1500, and I returned the
> smaller of the two values, 1000, what would happen to the other
There are a few cases when input_items[0] doesn't equal input_items[1]. If
say, len(input_items[0]) = 1000 and len(input_items[1]) = 1500, and I
returned the smaller of the two values, 1000, what would happen to the
other 500 samples on port 1? Would they be buffered somewhere and then used
the nex
Dear all,
we are trying to use the block digital_mpsk_snr_est in an OFDM flowgraph.
We think that the right place for the snr_est is after the ofdm_frame_sink
however we have the following error:
itemsize mismatch: ofdm_frame_sink(27):0 using 1600, mpsk_snr_est_cc(28):0
using 8
(consider that we
Hi,
Is anyone successfully using a B100 with Ubuntu 12.04? I rebuilt a
system recently and now I am continually getting seg faults and "Got a
data packet with unknown SID" errors on my Z77 based Ubuntu system.
I'm using the build-gnu-radio script and it's grabbed the latest uhd
images. I have a r
12 matches
Mail list logo
