vincenzo,
Regarding the inter/deinterleaver addition you have to:
instantiate an interleaver object of size K
where K is the length of the data you want to interleave.
There are different ways to do this. The simplest is a random interleaver:
int_object=trellis.interleaver(K,666) # last paramet
Dan,
thanks for the info you provided; it was ver helpful!
I think I got the basic understanding of the message_source/sink.
I wrote my first toy code based on this:
The Tx queues 100 packets and the Rx waits until
it receives everything (broken into different number of packets)
The Rx does
vincenzo,
this is NOT correct:
what is the purpose of the repacker?
the encoder in your case outputs bytes with values in {0,1,2,3}
these need to be mapped to your constellation (QPSK), not to be packet
into bytes.
I am surprised that this does not result in an error
within the chunk_to_symb
On Fri, Feb 23, 2007 at 01:16:38AM +0100, Vincenzo Pellegrini wrote:
>
> Hi,
>
> I think I got the point , I was doing twice the same thing.
> It was not clear to me that symbol demodulation is already included in
> viterbi block.
>
> so now I've got the convolutional code working, and would lik
Hi,
I think I got the point , I was doing twice the same thing.
It was not clear to me that symbol demodulation is already included in
viterbi block.
so now I've got the convolutional code working, and would like to add
interleaving and an outer Reed-Solomon block encoder.
can somebody show me
Eric Blossom wrote:
> Any chance there's a ' ' in any of the path names?
I fixed this (well, since I was the one who broke it in the first place :-)
I used $PYTHON instead of $(PYTHON). The $P evaluated to null and left
YTHON. See my later email to you.
--
Johnathan Corgan
Corgan Enterprises
On Thu, Feb 22, 2007 at 04:02:11PM -0500, Michael Dickens wrote:
> Initially, for some unknown reason to me, with the 3.0 release I get
> during "make":
>
> (cd .libs && rm -f libfilter-qa.la && ln -s ../libfilter-qa.la
> libfilter-qa.la)
> Making all in general
> PYTHONPATH=../../../../gnurad
Anastasopoulos Achilleas wrote:
What I don't know how to do is to enqueue a message every time
I press a button.
Can someone point to the right direction as to how this event driven
behavior is implemented.
Look in the gnuradio-examples/python/digital/tunnel.py and subfiles.
transmit_path.py
Hi, thanks again Achilleas for suggestions and help,
so far I've tried this for the convolutional 1,2 code.
this is the file for setting up the finite state machine
2 4 4
0 2
0 2
1 3
1 3
0 3
3 0
2 1
1 2
does it make sense?
and this is the code for connecting the encoder into the flow grpah
Hi,
I am trying to understand how the message source works
and how I can use it from within my python code.
So I wrote a simple script with a message source and a null sink.
I wanted the following behavior:
every time I press a button on my keybord to send a constant message in
the queue and ver
On Thu, Feb 22, 2007 at 02:17:30PM -0500, Michael Dickens wrote:
> On Feb 22, 2007, at 11:30 AM, Johnathan Corgan wrote:
> >please update to trunk revision 4588 and retest ticket:140.
> >I'll need to do an equivalent fix in the release 3.0 branch if this
> >works for you.
>
> Johnathan - Yes, that
Michael Dickens wrote:
> Johnathan - Yes, that works; thank you. BTW> The change that you
> made also renders the PATH in gr-usrp's run_tests.in redundant.
Okay.
> Might it not be better instead for run_tests.in in gr-usrp to specify
> the USRP libraries to include in the DYLD path instead of
On Feb 22, 2007, at 11:30 AM, Johnathan Corgan wrote:
please update to trunk revision 4588 and retest ticket:140.
I'll need to do an equivalent fix in the release 3.0 branch if this
works for you.
Johnathan - Yes, that works; thank you. BTW> The change that you
made also renders the PATH in
Eric Blossom wrote:
> Johnathan or Michael, can you take a look at ticket:140.
> I suspect that run_tests.sh is missing the usrp directory when it sets
> DYLD_LIBRARY_PATH
Michael--please update to trunk revision 4588 and retest ticket:140.
I'll need to do an equivalent fix in the release 3.0 bra
Berndt Josef Wulf wrote:
> Is usrp_spectrum_sense.py suppose to work with 3.0.3RC1?
No.
> I suspect that it isn't part of this release yet.
It only works on the trunk, which will eventually become the release 3.1
branch. The release 3.0x branch is only receiving bug fix and very
minor enhancem
On Feb 21, 2007, at 11:19 PM, Eric Blossom wrote:
Johnathan or Michael, can you take a look at ticket:140.
I suspect that run_tests.sh is missing the usrp directory when it sets
DYLD_LIBRARY_PATH
I don't have much time today, but I'll try to take a look mid-day or
this evening when I have a f
On Thursday 22 February 2007 15:18, Eric Blossom wrote:
> On Thu, Feb 22, 2007 at 02:43:09PM +1030, Berndt Josef Wulf wrote:
> > G'day,
> >
> > RC1 built fine, but I'm seeing a number of these errors during "gmake
> > check".
> >
> >
> > =
2007/2/22, Marcus Leech <[EMAIL PROTECTED]>:
I'm thinking about upgrading either to a Pentium D 9XX system, or an
Athlon 64 X2 3800+ dual-core system.
What do I need to know for Gnu Radio purposes--which version of Fedora
Core should I run--will my 32-bit
FC5 still run, or do I need an x86_64
G'day,
Is usrp_spectrum_sense.py suppose to work with 3.0.3RC1?
It's failing with -
Using RX d'board A: TV Rx
Traceback (most recent call last):
File "./usrp_spectrum_sense.py", line 236, in ?
fg = my_graph()
File "./usrp_spectrum_sense.py", line 169, in __init__
stats = gr.bin_stat
19 matches
Mail list logo
