Download the patchfile and git apply it. Or you can just disable gr-trellis
since you probably don't really need it anyway.
Nathan
On Tue, Jul 21, 2015 at 10:22 AM, shaunwang
wrote:
> Hello Nathan
>
> I read through this github, but I do not know how to use this patch. Can
> you
> give me some
I’ve been testing the Correlation Estimator block (corr_est_cc) and it’s a really nice block overall. However, I’ve noticed the time_est tag for estimating the fractional (sub-sample) delay doesn’t appear to be very accurate. I’ve attached my example configuration (pnseq_sim_corrsync.grc) although
Hi Andy,
yeah, that should work well, too.
In fact, it's pretty common to use IIRs for DC killing -- maybe even the
single-tap IIR GNU Radio has is sufficient. I just wanted to come up
with something that is signal-wise as good as the CPU hungry DC blocker.
By the way, the theory behind that DC
On Tue, 2015-07-21 at 12:01 -0400, discuss-gnuradio-requ...@gnu.org
wrote:
> Message: 11
> Date: Tue, 21 Jul 2015 11:47:40 +0200
> From: Marcus M?ller
> To: discuss-gnuradio@gnu.org
> Subject: Re: [Discuss-gnuradio] Run graph/ scheduler overhead
> Message-ID: <55ae153c.9050...@ettus.com>
> Content
On Tue, Jul 21, 2015 at 3:00 PM, Marcus Müller
wrote:
> That would be extremely awesome. Especially for people with some DSP
> filter experience, the Polyphase filterbanks are somewhat hard to
> understand, and I think Tom's article / presentation (which I can't seem to
> find right now) on the P
On Tue, Jul 21, 2015 at 3:24 PM, Richard Bell
wrote:
> Oh, I forgot about the Head block. That should do perfectly.
>
> Thanks guys
>
> Rich
>
The logger might also be useful. You can point the output to a file easily
enough.
http://gnuradio.org/doc/doxygen/page_logger.html
Tom
> On Tue, Ju
Oh, I forgot about the Head block. That should do perfectly.
Thanks guys
Rich
On Tue, Jul 21, 2015 at 12:21 PM, Nowlan, Sean
wrote:
> Neither of these are C++ commands, but they may do what you want:
>
>
>
> To limit output to 100 lines, you could do the following:
>
>
>
> $ ./my_flowgraph.py
Neither of these are C++ commands, but they may do what you want:
To limit output to 100 lines, you could do the following:
$ ./my_flowgraph.py | head -n 100
Or insert a "head" block in your flowgraph and choose an appropriate number of
samples to process.
Sean
From: discuss-gnuradio-bounces+
Hi Rich
Best approach is very probable running your flow graph in gdb and
specifying a break point:
gdb --args python /path/to/flow_graph.py
...
>break source_code.cc:121
blablabla not loaded, do you want to add it as soon as blabla? Y
>run
if you really want to enforce this in the source code
I agree an illustrated example would be extremely useful to all of us.
Rich
On Tue, Jul 21, 2015 at 12:00 PM, Marcus Müller
wrote:
> That would be extremely awesome. Especially for people with some DSP
> filter experience, the Polyphase filterbanks are somewhat hard to
> understand, and I think
That would be extremely awesome. Especially for people with some DSP
filter experience, the Polyphase filterbanks are somewhat hard to
understand, and I think Tom's article / presentation (which I can't seem
to find right now) on the PFBs can only profit from a real-world example
accompanying t
Maybe I'll do up an illustrated example on this using NOAA weather
radio, or the pager band
On Tue, Jul 21, 2015 at 11:42 AM, wrote:
> I just use the built-in firdes stuff, rather than using an external
> designer.
>
>
>
>
>
>
>
> On 2015-07-21 14:38, Marcus Müller wrote:
>
> Hi Rich, hello Mark
I'm looking for a way to stop my flowgraph through a C++ command just so I
can see a few std::cout debug statements without freezing my console due to
massive std::couts.
Is there a way of doing this?
Rich
___
Discuss-gnuradio mailing list
Discuss-gnura
I just use the built-in firdes stuff, rather than using an external
designer.
On 2015-07-21 14:38, Marcus Müller wrote:
> Hi Rich, hello Markus,
>
> On 21.07.2015 19:51, Richard Bell wrote:
>
>> GNU Radio has channelizers built-in, but I've not used them yet, so I don't
>> know how far th
Hi Rich, hello Markus,
On 21.07.2015 19:51, Richard Bell wrote:
GNU Radio has channelizers built-in, but I've not used them yet, so I
don't know how far they take you into this kind of task.
the Polyphase channelizer is actually an implementation derived from
that school of thought, and it work
I seem to have the gr-cdma OOT module installed and working properly.
If on the TX side I create a vector source of 50 zeroes and then include
a vector insert of the numbers 1-10, repeated every 10 times, I can see
that coming through the receive chain, so I think I have a slight grasp
of what is
I use the PFB channelizer for incoherent de-dispersion for pulsar
monitoring in radio astronomy. It's quite efficient for producing N
equally-spaced channels.
For randomly-spaced, individual frequency-xlating FFT filters might be
better.
On 2015-07-21 13:51, Richard Bell wrote:
> I would a
I would add, this task you are trying to do is an advanced DSP topic. What
you're looking for is a channelizer and this is optimally implemented using
a polyphase filter bank. If you need a good reference on this, fred harris'
book on Multirate Signal Processing for Comms Systems is a good.
http:/
Or, given a regular channel spacing, you can use a polyphase filterbank
to split it into multiple narrow-band channels.
Cheers,
Martin
On 21.07.2015 09:10, Stephen Harrison wrote:
> A simple way in GNURadio is to use the frequency xlating fir filter to
> select individual channels.
>
> On Tue,
A simple way in GNURadio is to use the frequency xlating fir filter to
select individual channels.
On Tue, Jul 21, 2015 at 8:39 AM, Markus Heller wrote:
> Dear list,
>
> I'd like to understand how to receive the 2m band as one wideband input
> (144-146 MHz) and afterwards split the sample stream
Dear list,
I'd like to understand how to receive the 2m band as one wideband input
(144-146 MHz) and afterwards split the sample stream into various
channels (relay inputs, relay outputs for various relay frequencies).
I do know how to receive all of the 2m band, but I don't know how to do
the sp
Hello Nathan
I read through this github, but I do not know how to use this patch. Can you
give me some instructions.
Do you know any good way to fix this problem?
Also, when i compile another version of GNURadio source files, it gave me
different error, shown here
http://gnuradio.4.n7.nabble.com
Hi,
I had a peek inside the S&C block, it's a hier block, so I simply
rebuilt it with the single blocks it composed of. And it works. But
I did not see anything wrong in the hier block. Maybe it could be
because of buffers, which get flushed or some do and some do not or
something like th
On Mon, Jul 20, 2015 at 4:58 PM, Nowlan, Sean
wrote:
> First, there may be multiple tags per sample. Use “get_tags_in_range” or
> “get_tags_in_window” to get all the tags you need. Using
> “get_tags_in_window(0, noutput_items, …)” will get you all the tags
> associated with samples passed as you
Hi Dennis,
if I read Fig 4 of [1] correctly, then you 32-delay DC blocker has a
passband starting at let's say 0.025 * f_sample.
I've gone ahead and clicked together a FIR filter that theoretically
should perform as well; its CPU consumption is... tolerable :)
Compare [2]; taps are in the PNG c
Hiii
I did following :
build% make
build% make test
gr-digital% gr-modtool makexml ofdm_chanestMMSE_vcvc
build% make install
everything seemed successful but WHEN opening GRC one block pop ups with :
" Cannot import gnuradio.
Is the python path environment variable set correctly?
All OS:
On Mon, 2015-07-13 at 21:43 -0400, Tom Rondeau wrote:
> On Mon, Jul 13, 2015 at 12:30 AM, West, Nathan
> wrote:
> This is a lot of information, and I'm just going to pick out
> one statement to comment on.
>
> On Sun, Jul 12, 2015 at 6:13 PM, Dennis Glatting
>
27 matches
Mail list logo
