[Discuss-gnuradio] Re: Discuss-gnuradio Digest, Vol 48, Issue 18

On 11/7/06, address@hidden <address@hidden > wrote:

Send Discuss-gnuradio mailing list submissions to
       address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
       http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
or, via email, send a message with subject or body 'help' to
       address@hidden

You can reach the person managing the list at
       address@hidden

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Discuss-gnuradio digest..."

Today's Topics:

  1. Re: Sampling rate of USRP and data rate through USB (Eric Blossom)
  2. Re: HDTV Receiver and additional hardware (Eric Blossom)
  3. RE: HDTV Receiver and additional hardware (Berkley, Antwong L.)
  4. Re: Sampling rate of USRP and data rate through USB (Ryan Seal)
  5. Re: HDTV Receiver and additional hardware (Charles Swiger)
  6. Re: HDTV Receiver and additional hardware (Eric Blossom)
  7. Fedora Core x86_64 lib problems. (Trond Danielsen)
  8. Reg: Gnu build. (address@hidden )

----------------------------------------------------------------------

Message: 1
Date: Mon, 6 Nov 2006 09:29:00 -0800
From: Eric Blossom <address@hidden>
Subject: Re: [Discuss-gnuradio] Sampling rate of USRP and data rate
       through USB
To: Lin Ji <address@hidden>
Cc: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii

On Mon, Nov 06, 2006 at 05:43:18PM +0100, Lin Ji wrote:
> Hi,
>  So you mean that it is not possible to save all 64M samples to file?

This is correct, unless you need only a small snapshot.

> (Reason I want that is my work depends on sampling time resolution,
> down-convertion by a factor 2 will give me dubble sampling time error).
> /Lin

Eric

------------------------------

Message: 2
Date: Mon, 6 Nov 2006 09:34:50 -0800
From: Eric Blossom < address@hidden>
Subject: Re: [Discuss-gnuradio] HDTV Receiver and additional hardware
To: "Berkley, Antwong L." <address@hidden >
Cc: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii

On Mon, Nov 06, 2006 at 11:43:54AM -0500, Berkley, Antwong L. wrote:
> Chuck,
>

> Thank you for the offer, I would like the help.  I want to explain
> what I am trying to do.  I am currently enrolled in a Software
> Defined Radios course at Virginia Tech.  For my semester project I
> want to demonstrate the flexibility of SDR.  I want to receive a
> HDTV or alternate frequency and transmit it on 802.11 using the USR

The HDTV receiver is far from real time.  I suggest starting with a
less computationally demanding waveform.

> In order to do my project I plan to use gnuradio and ossie (Virginia
> Tech middleware). I want to make some the gnuradio modules or
> functions compatible with ossie.

That sounds interesting.

> Here are few questions: I have compiled the latest version of
> gnuradio but not a legacy version.  Are the the old atsc_rx scripts
> not compatible with the latest version of gunradio?

> Can I view some of your scripts?
>
> Regards,
> Antwong

Chuck,

Can you please remind me where the ATSC Rx porting effort got stuck?
What's the immediate problem that needs to be solved?

Eric

------------------------------

Message: 3
Date: Mon, 6 Nov 2006 12:46:53 -0500
From: "Berkley, Antwong L." < address@hidden>
Subject: RE: [Discuss-gnuradio] HDTV Receiver and additional hardware
To: <address@hidden>
Cc: address@hidden
Message-ID:
       <address@hidden >
Content-Type: text/plain;       charset="us-ascii"

Chuck,

I am not really concerned about a real tine signal. I just want to
capture the signal on one frequency and transmit on a different
frequency. Capturing an image is enough and a follow-on would include
the capture a real time signal.

Antwong

-----Original Message-----
From: address@hidden [mailto: address@hidden]
Sent: Monday, November 06, 2006 12:35 PM
To: Berkley, Antwong L.
Cc: address@hidden; address@hidden
Subject: Re: [Discuss-gnuradio] HDTV Receiver and additional hardware

On Mon, Nov 06, 2006 at 11:43:54AM -0500, Berkley, Antwong L. wrote:
> Chuck,
>

> Thank you for the offer, I would like the help.  I want to explain
> what I am trying to do.  I am currently enrolled in a Software
> Defined Radios course at Virginia Tech.  For my semester project I
> want to demonstrate the flexibility of SDR.  I want to receive a
> HDTV or alternate frequency and transmit it on 802.11 using the USR

The HDTV receiver is far from real time.  I suggest starting with a
less computationally demanding waveform.

> In order to do my project I plan to use gnuradio and ossie (Virginia
> Tech middleware). I want to make some the gnuradio modules or
> functions compatible with ossie.

That sounds interesting.

> Here are few questions: I have compiled the latest version of
> gnuradio but not a legacy version.  Are the the old atsc_rx scripts
> not compatible with the latest version of gunradio?

> Can I view some of your scripts?
>
> Regards,
> Antwong

Chuck,

Can you please remind me where the ATSC Rx porting effort got stuck?
What's the immediate problem that needs to be solved?

Eric

------------------------------

Message: 4
Date: Mon, 06 Nov 2006 19:04:07 -0400
From: Ryan Seal <address@hidden>
Subject: Re: [Discuss-gnuradio] Sampling rate of USRP and data rate
       through USB
To: Lin Ji < address@hidden>, address@hidden
Message-ID: <address@hidden >
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Lin Ji wrote:
> Hi,
>   There is one thing that I can not figure out:
>   The ADC on the USRP has a sampling rate at 64Msps, that is, for a
> data at 1Mbps, for every incoming bit there will be 64 samples.
> Suppose every sample is 16bits, the bit rate is 1024Mbps,that is a
> huge amount of data flow. Now if a user want to same these samples to
> file through USB, even though the USB 2.0 interface has a high
> throughput at 480Mbps, it's not enough. If there is a buffer(like a
> FIFO or something) that is handling the ADC to USB tranfer, sooner or
> later this buffer will get full, how is this situation been handled?
>   Thanks.
> /Lin
>
Data is decimated using a CIC filter implemented in the FPGA. Data is
sampled on the front-end at 64MSPS and then the signal is filtered and
decimated (sample rate is reduced by dropping a number of samples) to
point that can be handled by the USB 2.0 bus (32 MBytes/Sec). If you
have a complex 16-bit data stream, you have 16-bit In-phase, 16-bit
Quadrature; therefore, you have 4 bytes per complex sample. It is stated
that only 8 MSPS (complex samples) can be sent across the USB bus and
this corresponds to 8 MSPS * 4 bytes = 32 MBytes/Sec. In other words,
you have to decimate you front-end 64 MSPS signal by a minimum of 8and
this gives you 8 MHz of bandwidth; of that, it is stated that only 6 MHz
or so is usable due to wrapping/aliasing from the filter roll-off.

32 MBPS becomes 32 MBPS * 8 bits/byte = 256Mbps ; which is little more
than 50% of the theoretical max.

--Ryan

> ------------------------------------------------------------------------
>
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>

------------------------------

Message: 5
Date: Mon, 06 Nov 2006 15:14:44 -0500
From: Charles Swiger <address@hidden >
Subject: Re: [Discuss-gnuradio] HDTV Receiver and additional hardware
To: Eric Blossom <address@hidden>
Cc: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain

On Mon, 2006-11-06 at 09:34 -0800, Eric Blossom wrote:
> Chuck,
>
> Can you please remind me where the ATSC Rx porting effort got stuck?
> What's the immediate problem that needs to be solved?
>

Everything from antenna to the "bit timing loop" can be done in
2.x, including fpll.  The bit timing loop, field sync checker,
equalizer and demultiplexor do not work in 2.x, altho a vain attempt
at porting has been checked in. Those "compile and run" but are broken.
The "grind on the data" modules that don't really have anything
to do with signal processing are all ported to 2.x: de/randomizer,
rs-de/encoder, de/interleaver and trellis/viterbi all qa test and
work great.

On the transmit side, field sync mux, symbol mapper and weaver
modulator head/tail are not ported.

So the immediate issue is getting bit-timing-loop finished, or
starting over on it correctly.

--Chuck

------------------------------

Message: 6
Date: Mon, 6 Nov 2006 12:37:24 -0800
From: Eric Blossom <address@hidden>
Subject: Re: [Discuss-gnuradio] HDTV Receiver and additional hardware
To: Charles Swiger < address@hidden>
Cc: address@hidden
Message-ID: < address@hidden>
Content-Type: text/plain; charset=us-ascii

On Mon, Nov 06, 2006 at 03:14:44PM -0500, Chuck Swiger wrote:
> On Mon, 2006-11-06 at 09:34 -0800, Eric Blossom wrote:
> > Chuck,
> >
> > Can you please remind me where the ATSC Rx porting effort got stuck?
> > What's the immediate problem that needs to be solved?
>
> Everything from antenna to the "bit timing loop" can be done in
> 2.x, including fpll.  The bit timing loop, field sync checker,
> equalizer and demultiplexor do not work in 2.x, altho a vain attempt
> at porting has been checked in. Those "compile and run" but are broken.
> The "grind on the data" modules that don't really have anything
> to do with signal processing are all ported to 2.x: de/randomizer,
> rs-de/encoder, de/interleaver and trellis/viterbi all qa test and
> work great.
>
> On the transmit side, field sync mux, symbol mapper and weaver
> modulator head/tail are not ported.
>
> So the immediate issue is getting bit-timing-loop finished, or
> starting over on it correctly.
>
> --Chuck

Thanks!

------------------------------

Message: 7
Date: Tue, 7 Nov 2006 12:03:34 +0100
From: "Trond Danielsen" < address@hidden>
Subject: [Discuss-gnuradio] Fedora Core x86_64 lib problems.
To: address@hidden
Message-ID:
       <address@hidden>
Content-Type: text/plain; charset="utf-8"

Hi everyone,

I have been looking into the problem with installing gnuradio on
Fedora Core (FC) x86_64, and just wanted to summarize what I found.
For reference this mail is based on previous discussions in:
http://lists.gnu.org/archive/html/discuss-gnuradio/2006-07/msg00117.html
and http://lists.gnu.org/archive/html/discuss-gnuradio/2006-11/msg00042.html

1. On a x86_64, FC installs arch-independent libraries into
$PREFIX/lib/python2.4/site-packages, and arch-depended into
$PREFIX/lib64/python2.4/site-packages, which is silly, because python
does not support this. It has already been discussed on the python-dev
mailing list (http://mail.python.org/pipermail/python-dev/2006-March/062462.html ),
but no solution has been found. There is also a bugreport in FC
bugzilla (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185948).
The problem relates back to pythons module loading algorithm.

2. As mentioned earlier, the install path for python scripts are
obtained from this automake macro: /usr/share/aclocal-1.9/python.m4. I
copied the macro to the config directory in gnuradio, modified it to
use the arch dependent path for both scripts and  extension modules.
This way both the scripts and the modules are installed in
$PREFIX/lib64 on x86_64. A patch for the aclocal file is included in
this mail.

Hope someone might find this useful.
--
Trond Danielsen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: python.m4.patch
Type: text/x-patch
Size: 683 bytes
Desc: not available
Url : http://lists.gnu.org/pipermail/discuss-gnuradio/attachments/20061107/37071f2e/python.m4.bin

------------------------------

Message: 8
Date: Tue, 7 Nov 2006 17:02:36 +0530
From: <address@hidden>
Subject: [Discuss-gnuradio] Reg: Gnu build.
To: < address@hidden>
Cc: address@hidden, address@hidden,
       address@hidden
Message-ID:
       <address@hidden>
Content-Type: text/plain; charset="iso-8859-1"

Hi!

   My problem with minimal gnubuild was finally solved and things went well. From what happened in the past few weeks, I guess the problem was with the outdated cygwin package and a conflict between the built in cpp unit of cygwin and the third party cppunit installed. So once I updated my cygwin package and did not install the built in cppunit with cygwin, the build of minimal gnuradio went successfully and the example program ran well.

Hence I proceeded with the build of a full gnuradio system with all components enabled. But the ./configure produced an error with the gr-trellis module as indicated below..

make[5]: Leaving directory `/cygdrive/c/gnuradio/gr-trellis/src/lib'
make[4]: Leaving directory `/cygdrive/c/gnuradio/gr-trellis/src/lib'
Making all in python
make[4]: Entering directory `/cygdrive/c/gnuradio/gr-trellis/src/python'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory `/cygdrive/c/gnuradio/gr-trellis/src/python'
make[4]: Entering directory `/cygdrive/c/gnuradio/gr-trellis/src'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory `/cygdrive/c/gnuradio/gr-trellis/src'
make[3]: Leaving directory `/cygdrive/c/gnuradio/gr-trellis/src'
Making all in doc
make[3]: Entering directory `/cygdrive/c/gnuradio/gr-trellis/doc'
xmlto html-nochunks gr-trellis.xml
xmlto: input does not validate (status 3)
error : Operation in progress
/cygdrive/c/gnuradio/gr-trellis/doc/gr- trellis.xml:6: warning: failed to load external entity "/cygd
rive/c/gnuradio/gr-trellis/doc/docbookx.dtd"
]>
^
error : Operation in progress
warning: failed to load external entity "/cygdrive/c/gnuradio/gr-trellis/doc/docbookx.dtd"
Could not load the external subset "docbookx.dtd"
Document /cygdrive/c/gnuradio/gr-trellis/doc/gr-trellis.xml does not validate
make[3]: *** [gr-trellis.html] Error 3
make[3]: Leaving directory `/cygdrive/c/gnuradio/gr-trellis/doc'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/cygdrive/c/gnuradio/gr-trellis'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/cygdrive/c/gnuradio'
make: *** [all] Error 2
address@hidden /cygdrive/c/gnuradio
$

However when I disable this gr-trellis component alone in the ./configure, all other modules were built successfully and the example programs were working.

Thnx & Regards,

Shriram K V
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gnu.org/pipermail/discuss-gnuradio/attachments/20061107/c69d5cc9/attachment.html

------------------------------

_______________________________________________
Discuss-gnuradio mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio

End of Discuss-gnuradio Digest, Vol 48, Issue 18
************************************************

From:	Ram
Subject:	[Discuss-gnuradio] Re: Discuss-gnuradio Digest, Vol 48, Issue 18
Date:	Tue, 7 Nov 2006 10:56:37 -0500