[Discuss-gnuradio] preamble and simple framer and correlator

[Songsong Gee]

Continueing with http://www.ruby-forum.com/topic/1983866, and
http://www.ruby-forum.com/topic/1991680

I am trying to append preamble to a signal so that RX can recognize it and
see a start position of data exactly.
I roughly draw what I thought.
[image: desired_signal.jpg]
(
http://dl.dropbox.com/u/11382666/for_gnuradio_mailinglist/desired_signal.jpg
)

I learned that there is gr_simple_framer and gr_simple_correlator in
gnuradio.
I guess that gr_simple_framer appends sync field and other files, and
gr_simple_correlator removes additional fields by gr_simple_framer

To verify this guess, I make a flow graph and run it.
[image: framer_correlator_test.png]
(
http://dl.dropbox.com/u/11382666/for_gnuradio_mailinglist/framer_correlator_test.png
)

As a flow graph runs, file size of framer_sink goes large, but that of
correlator_sink remains 0 forever.

I have tried to figure out how I can use these blocks from doxygen (
http://gnuradio.org/doc/doxygen/)
But I cannot figure out it easily.
Does anyone know what value should be in Payload Byte Size for framer and
correlator
and where I can find some examples of these two blocks?

--
Seokseong Jeon (aka Songsong Gee)
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Re g : Building gr-uhd and usrp2-firmware

[sumitstop]

Hi Marcus I have used your script.Its superb! I just wanted to build step
by step :)
Btw I just got all things build properly.Actually I put mb-gcc in the home
folder and set the path variables accordingly.And it worked :) 

Marcus D. Leech wrote:
> 
> On 06/23/2011 06:50 PM, sumitstop wrote:
>> I am using ubuntu Lucid 10.04 LTS.
>>
>> Did the following thing
>>
>> Step-1 Installed all the dependencies for ubuntu Lucid 10.04 from the
>> script
>> given here
>> http://gnuradio.org/redmine/projects/gnuradio/wiki/UbuntuInstall
>>
>> step-2 git clone http://gnuradio.org/git/gnuradio.git
>> then
>>
>> step-3 git clone http://github.com/EttusResearch/UHD-Mirror.git
>> after that
>>
>> step-4 cd gnuradio
>> step-5 ./bootstrap
>> step-6 ./configure
>>
>> I got following messages
>> *
>> The following components were skipped either because you asked not
>> to build them or they didn't pass configuration checks:
>>
>> usrp2-firmware
>>
>> These components will not be built.
>>
>>
>> *
>> The following GNU Radio components have been successfully configured:
>>
>> config
>> gruel
>> volk
>> gnuradio-core
>> usrp
>> usrp2
>> gr-usrp
>> gr-usrp2
>> gr-msdd6000
>> gr-audio
>> gr-atsc
>> gr-cvsd-vocoder
>> gr-gpio
>> gr-gsm-fr-vocoder
>> gr-noaa
>> gr-pager
>> gr-radar-mono
>> gr-radio-astronomy
>> gr-trellis
>> gr-video-sdl
>> gr-wxgui
>> gr-qtgui
>> gr-sounder
>> gr-utils
>> gnuradio-examples
>> grc
>> docs
>>
>> You my now run the make command to build these components.
>>
>> *
>> The following components were skipped either because you asked not
>> to build them or they didn't pass configuration checks:
>>
>> gcell
>> gr-gcell
>> gr-comedi
>> gr-uhd
>>
>> These components will not be built.
>>
>> Configured GNU Radio release v3.4.0-2-g081497e7 for build.
>>
>> **
>>
>> I searched a lot and found answer to many of questions
>>
>> > From the following link(in the summary) i found that no need to build
>> gr-comedi
>> http://lists.gnu.org/archive/html/discuss-gnuradio/2006-06/msg00225.html
>>
>> Also in the following link I read that gcell and gr-gcell are needed only
>> for IBM cell processor.
>> http://www.ruby-forum.com/topic/201112
>>
>> So I want to ask what should I do to build
>>
>> gr-uhd and usrp2-firmware
>>
>> I also did
>>
>> ./configure --enable-gr-uhd
>>
>> but it shows following message
>>
>> checking for UHD... no
>> gr-uhd requires libuhd 3.x.x
>> configure: error: Component gr-uhd has errors; stopping.
>>
>> I also did
>>
>> ./configure --enable-usrp2-firmware
>>
>> and got following message
>>
>> checking whether byte ordering is bigendian... no
>> checking for mb-gcc... no
>> usrp2 firmware requires mb-gcc.  Not found
>> configure: error: Component usrp2-firmware has errors; stopping.
>> configure: error: ./configure.gnu failed for usrp2/firmware
>>
>> I saw several posts with the same problem but honestly I couldn't
>> understand
>> what to do next.
>>
>> Regards
>>
>>
>>
>>
>> -
>> Sumit Kr.
>> Research Assistant
>> Communication Research center
>> IIIT Hyderabad
>> India
> I'll once again do some personal horn-tooting, if y'all can stand it:
> 
> http://www.sbrac.org/files/build-gnuradio
> 
> 
> It takes care of downloading/building UHD+Gnu Radio, including 
> downloading the latest firmware, installing pre-requisites, and
> uninstalling
>any installed-from-binary-packages "stuff" that might interfere with 
> a "built from source" build of Gnu Radio.
> 
> It works for Ubuntu and Fedora recent releases.
> 
> It's a shell script.  It takes quite a while to run, and generally 
> operates as silently as is practical.
> 
> 
> 
> -- 
> Marcus Leech
> Principal Investigator
> Shirleys Bay Radio Astronomy Consortium
> http://www.sbrac.org
> 
> 
> 
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
> 


-
Sumit Kr.
Research Assistant
Communication Research center
IIIT Hyderabad
India
-- 
View this message in context: 
http://old.nabble.com/Reg-%3A-Building-gr-uhd-and-usrp2-firmware-tp31915462p31917569.html
Sent from the GnuRadio mailing list archive at Nabble.com.


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Re g : Building gr-uhd and usrp2-firmware

[sumitstop]

Hi Morgan...actually I din't installed UHD before gnuradio.Now when I
installed UHD ,my problem seems to be solved now :) gr-uhd is built now.
Thanks 

Morgan Redfield-2 wrote:
> 
> Did you install UHD before you built gnuradio?
> 
> You can follow the build guide here:
> http://www.ettus.com/uhd_docs/manual/html/build.html
> 
> Morgan
> 
> On Thu, Jun 23, 2011 at 3:50 PM, sumitstop
>  wrote:
>>
>> I am using ubuntu Lucid 10.04 LTS.
>>
>> Did the following thing
>>
>> Step-1 Installed all the dependencies for ubuntu Lucid 10.04 from the
>> script
>> given here
>> http://gnuradio.org/redmine/projects/gnuradio/wiki/UbuntuInstall
>>
>> step-2 git clone http://gnuradio.org/git/gnuradio.git
>> then
>>
>> step-3 git clone http://github.com/EttusResearch/UHD-Mirror.git
>> after that
>>
>> step-4 cd gnuradio
>> step-5 ./bootstrap
>> step-6 ./configure
>>
>> I got following messages
>> *
>> The following components were skipped either because you asked not
>> to build them or they didn't pass configuration checks:
>>
>> usrp2-firmware
>>
>> These components will not be built.
>>
>>
>> *
>> The following GNU Radio components have been successfully configured:
>>
>> config
>> gruel
>> volk
>> gnuradio-core
>> usrp
>> usrp2
>> gr-usrp
>> gr-usrp2
>> gr-msdd6000
>> gr-audio
>> gr-atsc
>> gr-cvsd-vocoder
>> gr-gpio
>> gr-gsm-fr-vocoder
>> gr-noaa
>> gr-pager
>> gr-radar-mono
>> gr-radio-astronomy
>> gr-trellis
>> gr-video-sdl
>> gr-wxgui
>> gr-qtgui
>> gr-sounder
>> gr-utils
>> gnuradio-examples
>> grc
>> docs
>>
>> You my now run the make command to build these components.
>>
>> *
>> The following components were skipped either because you asked not
>> to build them or they didn't pass configuration checks:
>>
>> gcell
>> gr-gcell
>> gr-comedi
>> gr-uhd
>>
>> These components will not be built.
>>
>> Configured GNU Radio release v3.4.0-2-g081497e7 for build.
>>
>> **
>>
>> I searched a lot and found answer to many of questions
>>
>> From the following link(in the summary) i found that no need to build
>> gr-comedi
>> http://lists.gnu.org/archive/html/discuss-gnuradio/2006-06/msg00225.html
>>
>> Also in the following link I read that gcell and gr-gcell are needed only
>> for IBM cell processor.
>> http://www.ruby-forum.com/topic/201112
>>
>> So I want to ask what should I do to build
>>
>> gr-uhd and usrp2-firmware
>>
>> I also did
>>
>> ./configure --enable-gr-uhd
>>
>> but it shows following message
>>
>> checking for UHD... no
>> gr-uhd requires libuhd 3.x.x
>> configure: error: Component gr-uhd has errors; stopping.
>>
>> I also did
>>
>> ./configure --enable-usrp2-firmware
>>
>> and got following message
>>
>> checking whether byte ordering is bigendian... no
>> checking for mb-gcc... no
>> usrp2 firmware requires mb-gcc.  Not found
>> configure: error: Component usrp2-firmware has errors; stopping.
>> configure: error: ./configure.gnu failed for usrp2/firmware
>>
>> I saw several posts with the same problem but honestly I couldn't
>> understand
>> what to do next.
>>
>> Regards
>>
>>
>>
>>
>> -
>> Sumit Kr.
>> Research Assistant
>> Communication Research center
>> IIIT Hyderabad
>> India
>> --
>> View this message in context:
>> http://old.nabble.com/Reg-%3A-Building-gr-uhd-and-usrp2-firmware-tp31915462p31915462.html
>> Sent from the GnuRadio mailing list archive at Nabble.com.
>>
>>
>> ___
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
> 
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
> 


-
Sumit Kr.
Research Assistant
Communication Research center
IIIT Hyderabad
India
-- 
View this message in context: 
http://old.nabble.com/Reg-%3A-Building-gr-uhd-and-usrp2-firmware-tp31915462p31917580.html
Sent from the GnuRadio mailing list archive at Nabble.com.


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Channelizing

[dave k]

back when i had a usrp i setup an adjustable dual channel fm tuner with freq 
translating filters in grc. its setup for usrp1 so i could not capture the 
20mhz wide broadcast band. hope it helps

Sent from Yahoo! Mail on Android

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Channelizing

[dave k]

oops heres the aatchment


Sent from Yahoo! Mail on Android



usrp_wbfm_94-102_dual.grc
Description: Binary data
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Channelizing

[Colby Boyer]

On Thu, Jun 23, 2011 at 8:32 PM, Marcus D. Leech  wrote:

> I'm working on a multi-channel radiometer, based on USRP2 with the
> dual-DDC feature.
>
> I'm trying to come up with channelizing structure that won't overwhelm
> my CPU--I'm using
>  a 6-core Phenom II 1055T, with 4GB of 1333MHz memory.
>
> I need to be able to carve-off 4 channels, with widths between 100KHz
> and 500Khz, anywhere within
>  25MHz of the center frequency.
>
> I've tried a single 25MHz input channel, then carving it up with 4 FIR
> filters.  That produces massive
>  'O', no matter how sloppy I make the channel filters.
>
> I've tried a pair of 12.5MHz channels (using the dual-DDC feature that's
> relatively new). That produces
>  massive 'O'.
>
> Since ultimately, I'm mostly interesting in channel power estimates, I
> might just FFT it, and pick off
>  the bin(s) that correspond to my channels.
>
> Is one or two polyphase filter banks going to be cheaper?  And how do I
> compute the taps?  There
>  doesn't appear to be a helper function for that in GRC :-(
>
>
> --
> Principal Investigator
> Shirleys Bay Radio Astronomy Consortium
> http://www.sbrac.org
>
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>


Hi Marcus,

Check out a pfb channelizer!

gnuradio-core/src/python/gnuradio/blks2impl/pfb_channelizer.py is a nice
python wrapper for the class and gr_pfb_channelizer_ccf is the C++ name.

Also if you need to carve out a a shifted part of the spectrum, use the
gr_freq_xlating_fir_filter_*** block.

These are polyphase implementations so they should be computationally
efficient. Lastly, if you need even more efficiency you can see if they are
doing the fft implementation of filtering (not sure if they are vs standard
computation). As you know, there is the difference between NlogN and N^2

--Colby
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] pci composite / tv tuner cards as gnuradio source?

[dave k]

anyone?? :)

--- On Wed, 6/22/11, dave k  wrote:

> From: dave k 
> Subject: pci composite / tv tuner cards as gnuradio source?
> To: "gnuradio" 
> Date: Wednesday, June 22, 2011, 4:22 AM
> I searched and read about bt878 and
> possibly the pcHdtv card being used as a gnuradio
> source.  Can anyone add or comment as to the status of
> this ?
> 

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Unusual low pressure in Scandinavia

[Tom Rondeau]

On Thu, Jun 23, 2011 at 12:44 PM, Patrik Tast wrote:

> **
> FYI
>
> A snip of as seen from space of severe weather over Scandinvia.
> Using USRP1 + TVRX and 1.7 GHz downconverter LO 1557 MHz, 1.2 m dish
> (primefocus f/D=0.40) + tracking support.
> All stuff are lowcost and homebrew (alpha-proto). We can only improve
>
>
> http://www.poes-weather.com/~patrik/1.7GHz/HRPT/2011-06-23T144216-NOAA-19-snip-text.jpg
>
> Happy midsummer all,
> Patrik
>


I love this kind of stuff. Thanks for posting it!

Tom
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Channelizing

[Marcus D. Leech]

I'm working on a multi-channel radiometer, based on USRP2 with the
dual-DDC feature.

I'm trying to come up with channelizing structure that won't overwhelm
my CPU--I'm using
  a 6-core Phenom II 1055T, with 4GB of 1333MHz memory.

I need to be able to carve-off 4 channels, with widths between 100KHz 
and 500Khz, anywhere within
  25MHz of the center frequency.

I've tried a single 25MHz input channel, then carving it up with 4 FIR
filters.  That produces massive
  'O', no matter how sloppy I make the channel filters.

I've tried a pair of 12.5MHz channels (using the dual-DDC feature that's
relatively new). That produces
  massive 'O'.

Since ultimately, I'm mostly interesting in channel power estimates, I
might just FFT it, and pick off
  the bin(s) that correspond to my channels.

Is one or two polyphase filter banks going to be cheaper?  And how do I
compute the taps?  There
  doesn't appear to be a helper function for that in GRC :-(


-- 
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] uhd patch (valgrind happy)

[Philip Balister]

On 06/23/2011 02:48 PM, Gaetano Mendola wrote:

Hi all,
running my application with valgrind it complained about some
uninitialized values.

Patch attached.


Is it possible these are false positives from Valgrind? It looks like it 
is possible the variales you are writing zeros to are filled out in a 
function call that does not care about their initial values. SO filling 
them with zeros is not necessary.


Philip



Regards
Gaetano Mendola




___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Re g : Building gr-uhd and usrp2-firmware

[Marcus D. Leech]

On 06/23/2011 06:50 PM, sumitstop wrote:

I am using ubuntu Lucid 10.04 LTS.

Did the following thing

Step-1 Installed all the dependencies for ubuntu Lucid 10.04 from the script
given here
http://gnuradio.org/redmine/projects/gnuradio/wiki/UbuntuInstall

step-2 git clone http://gnuradio.org/git/gnuradio.git
then

step-3 git clone http://github.com/EttusResearch/UHD-Mirror.git
after that

step-4 cd gnuradio
step-5 ./bootstrap
step-6 ./configure

I got following messages
*
The following components were skipped either because you asked not
to build them or they didn't pass configuration checks:

usrp2-firmware

These components will not be built.


*
The following GNU Radio components have been successfully configured:

config
gruel
volk
gnuradio-core
usrp
usrp2
gr-usrp
gr-usrp2
gr-msdd6000
gr-audio
gr-atsc
gr-cvsd-vocoder
gr-gpio
gr-gsm-fr-vocoder
gr-noaa
gr-pager
gr-radar-mono
gr-radio-astronomy
gr-trellis
gr-video-sdl
gr-wxgui
gr-qtgui
gr-sounder
gr-utils
gnuradio-examples
grc
docs

You my now run the make command to build these components.

*
The following components were skipped either because you asked not
to build them or they didn't pass configuration checks:

gcell
gr-gcell
gr-comedi
gr-uhd

These components will not be built.

Configured GNU Radio release v3.4.0-2-g081497e7 for build.

**

I searched a lot and found answer to many of questions

> From the following link(in the summary) i found that no need to build
gr-comedi
http://lists.gnu.org/archive/html/discuss-gnuradio/2006-06/msg00225.html

Also in the following link I read that gcell and gr-gcell are needed only
for IBM cell processor.
http://www.ruby-forum.com/topic/201112

So I want to ask what should I do to build

gr-uhd and usrp2-firmware

I also did

./configure --enable-gr-uhd

but it shows following message

checking for UHD... no
gr-uhd requires libuhd 3.x.x
configure: error: Component gr-uhd has errors; stopping.

I also did

./configure --enable-usrp2-firmware

and got following message

checking whether byte ordering is bigendian... no
checking for mb-gcc... no
usrp2 firmware requires mb-gcc.  Not found
configure: error: Component usrp2-firmware has errors; stopping.
configure: error: ./configure.gnu failed for usrp2/firmware

I saw several posts with the same problem but honestly I couldn't understand
what to do next.

Regards




-
Sumit Kr.
Research Assistant
Communication Research center
IIIT Hyderabad
India

I'll once again do some personal horn-tooting, if y'all can stand it:

http://www.sbrac.org/files/build-gnuradio


It takes care of downloading/building UHD+Gnu Radio, including 
downloading the latest firmware, installing pre-requisites, and uninstalling
  any installed-from-binary-packages "stuff" that might interfere with 
a "built from source" build of Gnu Radio.


It works for Ubuntu and Fedora recent releases.

It's a shell script.  It takes quite a while to run, and generally 
operates as silently as is practical.




--
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] [USRP-users] Possible to use stream tagging features to implement RX sample bursts after a TX burst?

[Colby Boyer]

On Thu, Jun 23, 2011 at 4:11 PM, Nick Foster  wrote:

>
> >
> >
> >
> >
> > Where should I look for the API to tag samples on the USRP?
>
> Tagging in this case has nothing to do with the USRP and everything to
> do with Gnuradio. Take a look at the burst_tagger in
> gnuradio-core/src/lib/general/gr_burst_tagger.cc for an example.
>
> The Mode S decoder I wrote also uses tags throughout for preamble
> tagging and framing, and can be found at
> git://github.com/bistromath/gr-air-modes.git.
>
> --n
>
> >
> >
> > --Colby
>
>
>
I think it does have something to do with the USRP. I need to know at what
time my TX sampled got processed by the USRP, as this is the trigger for an
RX burst.

--Colby
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] [USRP-users] Possible to use stream tagging features to implement RX sample bursts after a TX burst?

[Nick Foster]

> 
> 
> 
> 
> Where should I look for the API to tag samples on the USRP?

Tagging in this case has nothing to do with the USRP and everything to
do with Gnuradio. Take a look at the burst_tagger in
gnuradio-core/src/lib/general/gr_burst_tagger.cc for an example. 

The Mode S decoder I wrote also uses tags throughout for preamble
tagging and framing, and can be found at
git://github.com/bistromath/gr-air-modes.git.

--n

> 
> 
> --Colby



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Re g : Building gr-uhd and usrp2-firmware

[Morgan Redfield]

Did you install UHD before you built gnuradio?

You can follow the build guide here:
http://www.ettus.com/uhd_docs/manual/html/build.html

Morgan

On Thu, Jun 23, 2011 at 3:50 PM, sumitstop
 wrote:
>
> I am using ubuntu Lucid 10.04 LTS.
>
> Did the following thing
>
> Step-1 Installed all the dependencies for ubuntu Lucid 10.04 from the script
> given here
> http://gnuradio.org/redmine/projects/gnuradio/wiki/UbuntuInstall
>
> step-2 git clone http://gnuradio.org/git/gnuradio.git
> then
>
> step-3 git clone http://github.com/EttusResearch/UHD-Mirror.git
> after that
>
> step-4 cd gnuradio
> step-5 ./bootstrap
> step-6 ./configure
>
> I got following messages
> *
> The following components were skipped either because you asked not
> to build them or they didn't pass configuration checks:
>
> usrp2-firmware
>
> These components will not be built.
>
>
> *
> The following GNU Radio components have been successfully configured:
>
> config
> gruel
> volk
> gnuradio-core
> usrp
> usrp2
> gr-usrp
> gr-usrp2
> gr-msdd6000
> gr-audio
> gr-atsc
> gr-cvsd-vocoder
> gr-gpio
> gr-gsm-fr-vocoder
> gr-noaa
> gr-pager
> gr-radar-mono
> gr-radio-astronomy
> gr-trellis
> gr-video-sdl
> gr-wxgui
> gr-qtgui
> gr-sounder
> gr-utils
> gnuradio-examples
> grc
> docs
>
> You my now run the make command to build these components.
>
> *
> The following components were skipped either because you asked not
> to build them or they didn't pass configuration checks:
>
> gcell
> gr-gcell
> gr-comedi
> gr-uhd
>
> These components will not be built.
>
> Configured GNU Radio release v3.4.0-2-g081497e7 for build.
>
> **
>
> I searched a lot and found answer to many of questions
>
> From the following link(in the summary) i found that no need to build
> gr-comedi
> http://lists.gnu.org/archive/html/discuss-gnuradio/2006-06/msg00225.html
>
> Also in the following link I read that gcell and gr-gcell are needed only
> for IBM cell processor.
> http://www.ruby-forum.com/topic/201112
>
> So I want to ask what should I do to build
>
> gr-uhd and usrp2-firmware
>
> I also did
>
> ./configure --enable-gr-uhd
>
> but it shows following message
>
> checking for UHD... no
> gr-uhd requires libuhd 3.x.x
> configure: error: Component gr-uhd has errors; stopping.
>
> I also did
>
> ./configure --enable-usrp2-firmware
>
> and got following message
>
> checking whether byte ordering is bigendian... no
> checking for mb-gcc... no
> usrp2 firmware requires mb-gcc.  Not found
> configure: error: Component usrp2-firmware has errors; stopping.
> configure: error: ./configure.gnu failed for usrp2/firmware
>
> I saw several posts with the same problem but honestly I couldn't understand
> what to do next.
>
> Regards
>
>
>
>
> -
> Sumit Kr.
> Research Assistant
> Communication Research center
> IIIT Hyderabad
> India
> --
> View this message in context: 
> http://old.nabble.com/Reg-%3A-Building-gr-uhd-and-usrp2-firmware-tp31915462p31915462.html
> Sent from the GnuRadio mailing list archive at Nabble.com.
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Re g : Building gr-uhd and usrp2-firmware

[sumitstop]

I am using ubuntu Lucid 10.04 LTS.

Did the following thing

Step-1 Installed all the dependencies for ubuntu Lucid 10.04 from the script
given here
http://gnuradio.org/redmine/projects/gnuradio/wiki/UbuntuInstall

step-2 git clone http://gnuradio.org/git/gnuradio.git
then

step-3 git clone http://github.com/EttusResearch/UHD-Mirror.git
after that

step-4 cd gnuradio
step-5 ./bootstrap
step-6 ./configure

I got following messages 
*
The following components were skipped either because you asked not
to build them or they didn't pass configuration checks:

usrp2-firmware

These components will not be built.


*
The following GNU Radio components have been successfully configured:

config
gruel
volk
gnuradio-core
usrp
usrp2
gr-usrp
gr-usrp2
gr-msdd6000
gr-audio
gr-atsc
gr-cvsd-vocoder
gr-gpio
gr-gsm-fr-vocoder
gr-noaa
gr-pager
gr-radar-mono
gr-radio-astronomy
gr-trellis
gr-video-sdl
gr-wxgui
gr-qtgui
gr-sounder
gr-utils
gnuradio-examples
grc
docs

You my now run the make command to build these components.

*
The following components were skipped either because you asked not
to build them or they didn't pass configuration checks:

gcell
gr-gcell
gr-comedi
gr-uhd

These components will not be built.

Configured GNU Radio release v3.4.0-2-g081497e7 for build.

**

I searched a lot and found answer to many of questions

>From the following link(in the summary) i found that no need to build
gr-comedi
http://lists.gnu.org/archive/html/discuss-gnuradio/2006-06/msg00225.html

Also in the following link I read that gcell and gr-gcell are needed only
for IBM cell processor.
http://www.ruby-forum.com/topic/201112

So I want to ask what should I do to build 

gr-uhd and usrp2-firmware

I also did
 
./configure --enable-gr-uhd

but it shows following message

checking for UHD... no
gr-uhd requires libuhd 3.x.x
configure: error: Component gr-uhd has errors; stopping.

I also did 

./configure --enable-usrp2-firmware

and got following message

checking whether byte ordering is bigendian... no
checking for mb-gcc... no
usrp2 firmware requires mb-gcc.  Not found
configure: error: Component usrp2-firmware has errors; stopping.
configure: error: ./configure.gnu failed for usrp2/firmware

I saw several posts with the same problem but honestly I couldn't understand
what to do next.

Regards




-
Sumit Kr.
Research Assistant
Communication Research center
IIIT Hyderabad
India
-- 
View this message in context: 
http://old.nabble.com/Reg-%3A-Building-gr-uhd-and-usrp2-firmware-tp31915462p31915462.html
Sent from the GnuRadio mailing list archive at Nabble.com.


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] appending preamble with different power

[Songsong Gee]

Continueing with http://www.ruby-forum.com/topic/1983866,

I have planned to append a preamble before an actual signal and turn RX on
earlier than TX.

Then RX will receive a signal like below:

|---RX turn on--|---TX turn on-
(---trash signal---)(---preamble---)(---actual signal---)

And this signal is demodulated and stored into a sink file.
After that, I run a program that extracts an actual data only and compare it
to the original.

My concern is that this preamble should be assumed to be perfect i.e. no
errors
Of course, there isn't no error. However if I set an amplitude to maximum
value, it can be said to be no error.
I have a pre-defined preamble sequence with length n (n = around 100-200,
can be changed)

Thus, I am trying to change amplitude of modulated signal for preamble and
actual signal
But I have problem with some quadrature modulation. Flow graphs are in
below:

http://dl.dropbox.com/u/11382666/for_gnuradio_mailinglist/M-DPSK.png
http://dl.dropbox.com/u/11382666/for_gnuradio_mailinglist/M-FSK.png

My question is that, how many samples after DPSK mod or frequency mod block
corresponds to each sample from file source?
I have to solve this problem in order to figure out how many samples are
generated from preamble with length n.
If I know that information, I can set a duration for Multiply const block
having large value for preamble and normal value for actual signal

And second question is that, although I know that information, I don't know
how I can control value.
For example, preamble with length 200, then I want to set large value for
duration 200 * x (number of samples generated after DPSK, Frequency mod),
and after that I want to set normal value for remaining duration.

Is it too complex for gnuradio-companion flow graph to make? And is python
hard coding possible?

-- 
Seokseong Jeon (aka Songsong Gee)
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] appending preamble with different power

[Marcus D. Leech]

On 23/06/2011 3:03 PM, Colby Boyer wrote:

Or operate your receiver at absolute zero so there is no thermal noise? :D

Infinite SNR.  Must have :-)



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] appending preamble with different power

[Nick Foster]

On Fri, 2011-06-24 at 04:00 +0900, Songsong Gee wrote:
> Ok. First of all, I'd like to run a code like below (pseudo):
> for i = 1 to 200 // preamble duration
>   amp = 32767
> end for
> amp = 100

Like I said earlier, this is unlikely to be a good approach to
synchronizing with a preamble.

> 
> Next, how many baseband samples are generated by DPSK or Frequency mod
> block for a single symbol input

Did you read the email you just replied to?

> 
> Composed with Android (Galaxys)
> 
> 2011. 6. 24. 오전 3:31에 "Nick Foster" 님이 작성:
> > On Fri, 2011-06-24 at 01:17 +0900, Songsong Gee wrote:
> >> Continueing with http://www.ruby-forum.com/topic/1983866,
> >> 
> >> 
> >> I have planned to append a preamble before an actual signal and
> turn
> >> RX on earlier than TX.
> >> 
> >> 
> >> Then RX will receive a signal like below:
> >> |---RX turn on--|---TX turn
> >> on-
> >> (---trash signal---)(---preamble---)(---actual signal---)
> >> 
> >> 
> >> And this signal is demodulated and stored into a sink file.
> >> After that, I run a program that extracts an actual data only and
> >> compare it to the original.
> >> 
> >> 
> >> My concern is that this preamble should be assumed to be perfect
> i.e.
> >> no errors
> >> Of course, there isn't no error. However if I set an amplitude to
> >> maximum value, it can be said to be no error.
> > 
> > I don't understand what you mean here. You can find an "imperfect"
> > preamble sequence using a correlator.
> > 
> >> I have a pre-defined preamble sequence with length n (n = around
> >> 100-200, can be changed)
> >> 
> >> 
> >> Thus, I am trying to change amplitude of modulated signal for
> preamble
> >> and actual signal
> >> But I have problem with some quadrature modulation. Flow graphs are
> in
> >> below:
> >>
> http://dl.dropbox.com/u/11382666/for_gnuradio_mailinglist/M-DPSK.png
> >> http://dl.dropbox.com/u/11382666/for_gnuradio_mailinglist/M-FSK.png
> >> 
> >> 
> >> My question is that, how many samples after DPSK mod or frequency
> mod
> >> block corresponds to each sample from file source?
> > 
> > It's right there in the block, where it says "samples/symbol".
> > 
> >> I have to solve this problem in order to figure out how many
> samples
> >> are generated from preamble with length n.
> >> If I know that information, I can set a duration for Multiply const
> >> block having large value for preamble and normal value for actual
> >> signal
> > 
> > Why would you set the amplitude of the preamble differently than the
> > actual data?
> > 
> > --n
> > 
> >> 
> >> 
> >> And second question is that, although I know that information, I
> don't
> >> know how I can control value.
> >> For example, preamble with length 200, then I want to set large
> value
> >> for duration 200 * x (number of samples generated after DPSK,
> >> Frequency mod), and after that I want to set normal value for
> >> remaining duration.
> >> 
> >> 
> >> Is it too complex for gnuradio-companion flow graph to make? And is
> >> python hard coding possible?
> >> 
> >> 
> >> -- 
> >> Seokseong Jeon (aka Songsong Gee)
> >> 
> >> 
> >> ___
> >> Discuss-gnuradio mailing list
> >> Discuss-gnuradio@gnu.org
> >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> > 
> > 
> 



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] appending preamble with different power

[Colby Boyer]

Or operate your receiver at absolute zero so there is no thermal noise? :D

On a more serious note, how I do preamble detection is the following:

* Figure out the sample sequence of your TX'ed preamble sequence, use this
as a match filter.
* Tag the magnitude of the match filter and run through the peak detector
block, which should locate the spike in energy from the preamble.
* When this happens, your packet frame begins one sample in the future (post
preamble).

>From me, this seems to work pretty wellall things considered.

On Thu, Jun 23, 2011 at 11:48 AM, Marcus D. Leech  wrote:

> On 23/06/2011 2:31 PM, Nick Foster wrote:
>
>>
>> Why would you set the amplitude of the preamble differently than the
>> actual data?
>>
>> --n
>>
> In the hopelessly-naive assumption that the preamble can be made to be
> "perfect" through brute-force transmit power.
>
> Like you observed earlier, correlation is the correct way to detect a
> preamble.
>
>
>
> __**_
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/**listinfo/discuss-gnuradio
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] appending preamble with different power

[Songsong Gee]

Ok. First of all, I'd like to run a code like below (pseudo):
for i = 1 to 200 // preamble duration
  amp = 32767
end for
amp = 100

Next, how many baseband samples are generated by DPSK or Frequency mod block
for a single symbol input

Composed with Android (Galaxys)
2011. 6. 24. 오전 3:31에 "Nick Foster" 님이 작성:
> On Fri, 2011-06-24 at 01:17 +0900, Songsong Gee wrote:
>> Continueing with http://www.ruby-forum.com/topic/1983866,
>>
>>
>> I have planned to append a preamble before an actual signal and turn
>> RX on earlier than TX.
>>
>>
>> Then RX will receive a signal like below:
>> |---RX turn on--|---TX turn
>> on-
>> (---trash signal---)(---preamble---)(---actual signal---)
>>
>>
>> And this signal is demodulated and stored into a sink file.
>> After that, I run a program that extracts an actual data only and
>> compare it to the original.
>>
>>
>> My concern is that this preamble should be assumed to be perfect i.e.
>> no errors
>> Of course, there isn't no error. However if I set an amplitude to
>> maximum value, it can be said to be no error.
>
> I don't understand what you mean here. You can find an "imperfect"
> preamble sequence using a correlator.
>
>> I have a pre-defined preamble sequence with length n (n = around
>> 100-200, can be changed)
>>
>>
>> Thus, I am trying to change amplitude of modulated signal for preamble
>> and actual signal
>> But I have problem with some quadrature modulation. Flow graphs are in
>> below:
>> http://dl.dropbox.com/u/11382666/for_gnuradio_mailinglist/M-DPSK.png
>> http://dl.dropbox.com/u/11382666/for_gnuradio_mailinglist/M-FSK.png
>>
>>
>> My question is that, how many samples after DPSK mod or frequency mod
>> block corresponds to each sample from file source?
>
> It's right there in the block, where it says "samples/symbol".
>
>> I have to solve this problem in order to figure out how many samples
>> are generated from preamble with length n.
>> If I know that information, I can set a duration for Multiply const
>> block having large value for preamble and normal value for actual
>> signal
>
> Why would you set the amplitude of the preamble differently than the
> actual data?
>
> --n
>
>>
>>
>> And second question is that, although I know that information, I don't
>> know how I can control value.
>> For example, preamble with length 200, then I want to set large value
>> for duration 200 * x (number of samples generated after DPSK,
>> Frequency mod), and after that I want to set normal value for
>> remaining duration.
>>
>>
>> Is it too complex for gnuradio-companion flow graph to make? And is
>> python hard coding possible?
>>
>>
>> --
>> Seokseong Jeon (aka Songsong Gee)
>>
>>
>> ___
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] appending preamble with different power

[Marcus D. Leech]

On 23/06/2011 2:31 PM, Nick Foster wrote:


Why would you set the amplitude of the preamble differently than the
actual data?

--n
In the hopelessly-naive assumption that the preamble can be made to be 
"perfect" through brute-force transmit power.


Like you observed earlier, correlation is the correct way to detect a 
preamble.



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] appending preamble with different power

[Nick Foster]

On Fri, 2011-06-24 at 01:17 +0900, Songsong Gee wrote:
> Continueing with http://www.ruby-forum.com/topic/1983866,
> 
> 
> I have planned to append a preamble before an actual signal and turn
> RX on earlier than TX.
> 
> 
> Then RX will receive a signal like below:
> |---RX turn on--|---TX turn
> on-
> (---trash signal---)(---preamble---)(---actual signal---)
> 
> 
> And this signal is demodulated and stored into a sink file.
> After that, I run a program that extracts an actual data only and
> compare it to the original.
> 
> 
> My concern is that this preamble should be assumed to be perfect i.e.
> no errors
> Of course, there isn't no error. However if I set an amplitude to
> maximum value, it can be said to be no error.

I don't understand what you mean here. You can find an "imperfect"
preamble sequence using a correlator.

> I have a pre-defined preamble sequence with length n (n = around
> 100-200, can be changed)
> 
> 
> Thus, I am trying to change amplitude of modulated signal for preamble
> and actual signal
> But I have problem with some quadrature modulation. Flow graphs are in
> below:
> http://dl.dropbox.com/u/11382666/for_gnuradio_mailinglist/M-DPSK.png
> http://dl.dropbox.com/u/11382666/for_gnuradio_mailinglist/M-FSK.png
> 
> 
> My question is that, how many samples after DPSK mod or frequency mod
> block corresponds to each sample from file source?

It's right there in the block, where it says "samples/symbol".

> I have to solve this problem in order to figure out how many samples
> are generated from preamble with length n.
> If I know that information, I can set a duration for Multiply const
> block having large value for preamble and normal value for actual
> signal

Why would you set the amplitude of the preamble differently than the
actual data?

--n

> 
> 
> And second question is that, although I know that information, I don't
> know how I can control value.
> For example, preamble with length 200, then I want to set large value
> for duration 200 * x (number of samples generated after DPSK,
> Frequency mod), and after that I want to set normal value for
> remaining duration.
> 
> 
> Is it too complex for gnuradio-companion flow graph to make? And is
> python hard coding possible?
> 
> 
> -- 
> Seokseong Jeon (aka Songsong Gee)
> 
> 
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] appending preamble with different power

[Colby Boyer]

I'm a bit confused. What exactly are you trying to do?

On Thu, Jun 23, 2011 at 9:17 AM, Songsong Gee wrote:

> Continueing with http://www.ruby-forum.com/topic/1983866,
>
> I have planned to append a preamble before an actual signal and turn RX on
> earlier than TX.
>
> Then RX will receive a signal like below:
>
> |---RX turn on--|---TX turn on-
> (---trash signal---)(---preamble---)(---actual signal---)
>
> And this signal is demodulated and stored into a sink file.
> After that, I run a program that extracts an actual data only and compare
> it to the original.
>
> My concern is that this preamble should be assumed to be perfect i.e. no
> errors
> Of course, there isn't no error. However if I set an amplitude to maximum
> value, it can be said to be no error.
> I have a pre-defined preamble sequence with length n (n = around 100-200,
> can be changed)
>
> Thus, I am trying to change amplitude of modulated signal for preamble and
> actual signal
> But I have problem with some quadrature modulation. Flow graphs are in
> below:
>
> http://dl.dropbox.com/u/11382666/for_gnuradio_mailinglist/M-DPSK.png
> http://dl.dropbox.com/u/11382666/for_gnuradio_mailinglist/M-FSK.png
>
> My question is that, how many samples after DPSK mod or frequency mod block
> corresponds to each sample from file source?
> I have to solve this problem in order to figure out how many samples are
> generated from preamble with length n.
> If I know that information, I can set a duration for Multiply const block
> having large value for preamble and normal value for actual signal
>
> And second question is that, although I know that information, I don't know
> how I can control value.
> For example, preamble with length 200, then I want to set large value for
> duration 200 * x (number of samples generated after DPSK, Frequency mod),
> and after that I want to set normal value for remaining duration.
>
> Is it too complex for gnuradio-companion flow graph to make? And is python
> hard coding possible?
>
> --
> Seokseong Jeon (aka Songsong Gee)
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Unusual low pressure in Scandinavia

[Patrik Tast]

FYI

A snip of as seen from space of severe weather over Scandinvia. 
Using USRP1 + TVRX and 1.7 GHz downconverter LO 1557 MHz, 1.2 m dish 
(primefocus f/D=0.40) + tracking support.
All stuff are lowcost and homebrew (alpha-proto). We can only improve

http://www.poes-weather.com/~patrik/1.7GHz/HRPT/2011-06-23T144216-NOAA-19-snip-text.jpg

Happy midsummer all,
Patrik___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Feasibility study of Porting GNU Radio on experimental processor

[Colby Boyer]

The first thing to look at is the list of the GNU Radio dependencies (check
the wiki). All the ones related to the gnuradio core would need to be
ported. . .It probably will not be a trivial task.

--Colby

On Thu, Jun 23, 2011 at 1:36 AM, Amanullah  wrote:

> Hi
>
> ** **
>
> I want to port the GNU radio code base to TTA processor architecture. The
> processor is programmed on an FPGA.  The compiler for TTA is TCE which
> supports C and C++.
>
> I have some initial questions about feasibility of such project. Is it
> possible to port GNU radio code to an embedded processor with no OS support?
> GNU Radio uses Boost Shared Library. Is Boost library portable and can it
> work without an Operating system??
>
> GNU build system also do not seem to support TCE compiler (CFLAGS=tcecc
> gives error). Is there any project where GNU radio have been used without
> any OS support as standalone system??
>
> ** **
>
> Details of TCE compiler and TTA can be found at http://tce.cs.tut.fi/
>
> ** **
>
> Please reply me as soon as possible.
>
> ** **
>
> Thanks and Regards
>
> Amanullah Ghazi
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] USRP2 Error

[Josh Blum]

On 06/23/2011 07:56 AM, Jide Julius wrote:
> Hi All,
> I am using 3 USRP2. The 3 FPGA and firmware were installed using the same
> procedures. The installation was successful and I was able to ping the 3
> USRP2 devices. However, when I run the GNU Radio Companion, it was able to
> identify only one of them. The other 2 were not recognised. The warning
> error I received is: "Expected protocol compatibility number 9, but got 10.
> The firmware build is not compatible with the host code build". Also, on one
> of the unidentified USRP2 device, the B light was on. Please, I want some to
> assist me on what I need to do.
> 

Update the images on your SD card :-)

http://code.ettus.com/redmine/ettus/projects/uhd/wiki#Binary-downloads

http://www.ettus.com/uhd_docs/manual/html/usrp2.html#load-the-images-onto-the-sd-card-usrp2-only

-josh

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] E100 - No devices found for ----->

[Jason Abele]

On Thu, Jun 23, 2011 at 5:32 AM, Ralf Wierse  wrote:
>> -Original Message-
>> From: Jason Abele [mailto:ja...@ettus.com]
>> Sent: Thursday, June 23, 2011 1:04 PM
>> To: Ralf Wierse
>> Cc: discuss-gnuradio Discussion Group
>> Subject: Re: [Discuss-gnuradio] E100 - No devices found for ->
>>
>>
>> On Thu, Jun 23, 2011 at 3:16 AM, Ralf Wierse
>>  wrote:
>> > OK, first simple reason discovered.
>> > UHD can only be used for one device - either UHD_usrp_sink
>> or source.
>> >
>> > How can UHD be used for both devices in parallel?
>>
>> You have to access both source and sink from the same process, but
>> then it is possible to use both at the same time.
>>
>> Jason
>
>
> Hi Jason,
> thanks but I am a little confused.
> I would say it is in the same process since I have sink and source in the same
> GRC setup. The failure shows up when the generated python script instantiates 
> an
> UHD devices the second time as far as I understand.
> Is there any combined UHD_usrp_sink/source block for GRC or how is this to
> be done practically?

Can you send the simplest .grc file which causes this issue?

Jason

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] E100 - No devices found for ----->

[Josh Blum]

On 06/23/2011 03:16 AM, Ralf Wierse wrote:
> OK, first simple reason discovered.
> UHD can only be used for one device - either UHD_usrp_sink or source.
> 
> How can UHD be used for both devices in parallel?
> 

Sorry, Its a known bug related to opening twice. Its fixed on the next
branch. Solution w/ instructions:
http://comments.gmane.org/gmane.comp.hardware.usrp.e100/754

-Josh

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] E100 - No devices found for ----->

[Marcus D. Leech]

On 23/06/2011 8:32 AM, Ralf Wierse wrote:


Hi Jason,
thanks but I am a little confused.
I would say it is in the same process since I have sink and source in the same
GRC setup. The failure shows up when the generated python script instantiates an
UHD devices the second time as far as I understand.
Is there any combined UHD_usrp_sink/source block for GRC or how is this to
be done practically?

Thanks
Ralf



This should "Just Work(tm)".  Make sure you have the latest UHD and Gnu 
Radio.  If it continues to not work, then there's a problem

  with the code, and Josh/Phil should look into it.





___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] USRP2 Error

[Jide Julius]

Hi All,
I am using 3 USRP2. The 3 FPGA and firmware were installed using the same
procedures. The installation was successful and I was able to ping the 3
USRP2 devices. However, when I run the GNU Radio Companion, it was able to
identify only one of them. The other 2 were not recognised. The warning
error I received is: "Expected protocol compatibility number 9, but got 10.
The firmware build is not compatible with the host code build". Also, on one
of the unidentified USRP2 device, the B light was on. Please, I want some to
assist me on what I need to do.

Thanks

Julius.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] uhd patch (valgrind happy)

[Gaetano Mendola]

Hi all,
running my application with valgrind it complained about some
uninitialized values.

Patch attached.

Regards
Gaetano Mendola

-- 
cpp-today.blogspot.com
diff --git a/host/lib/transport/super_send_packet_handler.hpp 
b/host/lib/transport/super_send_packet_handler.hpp
index 8ebc264..2aedd75 100644
--- a/host/lib/transport/super_send_packet_handler.hpp
+++ b/host/lib/transport/super_send_packet_handler.hpp
@@ -149,6 +149,7 @@ public:
 
 //translate the metadata to vrt if packet info
 vrt::if_packet_info_t if_packet_info;
+memset(&if_packet_info, 0, sizeof(if_packet_info));
 if_packet_info.has_sid = false;
 if_packet_info.has_cid = false;
 if_packet_info.has_tlr = false;
diff --git a/host/lib/usrp/usrp2/usrp2_iface.cpp 
b/host/lib/usrp/usrp2/usrp2_iface.cpp
index ec1a2e9..e734211 100644
--- a/host/lib/usrp/usrp2/usrp2_iface.cpp
+++ b/host/lib/usrp/usrp2/usrp2_iface.cpp
@@ -91,6 +91,7 @@ public:
 //Save the response compat number for communication.
 //TODO can choose to reject certain older compat numbers
 usrp2_ctrl_data_t ctrl_data;
+memset(&ctrl_data, 0, sizeof(ctrl_data));
 ctrl_data.id = htonl(USRP2_CTRL_ID_WAZZUP_BRO);
 ctrl_data = ctrl_send_and_recv(ctrl_data, 0, ~0);
 if (ntohl(ctrl_data.id) != USRP2_CTRL_ID_WAZZUP_DUDE)
@@ -180,6 +181,7 @@ public:
 T get_reg(boost::uint32_t addr, T data = 0){
 //setup the out data
 usrp2_ctrl_data_t out_data;
+memset(&out_data, 0, sizeof(out_data));
 out_data.id = htonl(USRP2_CTRL_ID_GET_THIS_REGISTER_FOR_ME_BRO);
 out_data.data.reg_args.addr = htonl(addr);
 out_data.data.reg_args.data = htonl(boost::uint32_t(data));
@@ -208,6 +210,7 @@ public:
 
 //setup the out data
 usrp2_ctrl_data_t out_data;
+memset(&out_data, 0, sizeof(out_data));
 out_data.id = htonl(USRP2_CTRL_ID_TRANSACT_ME_SOME_SPI_BRO);
 out_data.data.spi_args.dev = htonl(which_slave);
 out_data.data.spi_args.miso_edge = spi_edge_to_otw[config.miso_edge];
@@ -229,6 +232,7 @@ public:
 void write_i2c(boost::uint8_t addr, const byte_vector_t &buf){
 //setup the out data
 usrp2_ctrl_data_t out_data;
+memset(&out_data, 0, sizeof(out_data));
 out_data.id = htonl(USRP2_CTRL_ID_WRITE_THESE_I2C_VALUES_BRO);
 out_data.data.i2c_args.addr = addr;
 out_data.data.i2c_args.bytes = buf.size();
@@ -247,6 +251,7 @@ public:
 byte_vector_t read_i2c(boost::uint8_t addr, size_t num_bytes){
 //setup the out data
 usrp2_ctrl_data_t out_data;
+memset(&out_data, 0, sizeof(out_data));
 out_data.id = htonl(USRP2_CTRL_ID_DO_AN_I2C_READ_FOR_ME_BRO);
 out_data.data.i2c_args.addr = addr;
 out_data.data.i2c_args.bytes = num_bytes;
diff --git a/host/lib/usrp/usrp2/usrp2_impl.cpp 
b/host/lib/usrp/usrp2/usrp2_impl.cpp
index b5e5050..e8f9e89 100644
--- a/host/lib/usrp/usrp2/usrp2_impl.cpp
+++ b/host/lib/usrp/usrp2/usrp2_impl.cpp
@@ -94,6 +94,7 @@ static device_addrs_t usrp2_find(const device_addr_t &hint_){
 
 //send a hello control packet
 usrp2_ctrl_data_t ctrl_data_out;
+memset(&ctrl_data_out, 0, sizeof(ctrl_data_out));
 ctrl_data_out.proto_ver = uhd::htonx(USRP2_FW_COMPAT_NUM);
 ctrl_data_out.id = uhd::htonx(USRP2_CTRL_ID_WAZZUP_BRO);
 udp_transport->send(boost::asio::buffer(&ctrl_data_out, 
sizeof(ctrl_data_out)));
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] E100 - No devices found for ----->

[Ralf Wierse]

> -Original Message-
> From: Jason Abele [mailto:ja...@ettus.com] 
> Sent: Thursday, June 23, 2011 1:04 PM
> To: Ralf Wierse
> Cc: discuss-gnuradio Discussion Group
> Subject: Re: [Discuss-gnuradio] E100 - No devices found for ->
> 
> 
> On Thu, Jun 23, 2011 at 3:16 AM, Ralf Wierse 
>  wrote:
> > OK, first simple reason discovered.
> > UHD can only be used for one device - either UHD_usrp_sink 
> or source.
> >
> > How can UHD be used for both devices in parallel?
> 
> You have to access both source and sink from the same process, but
> then it is possible to use both at the same time.
> 
> Jason


Hi Jason,
thanks but I am a little confused.
I would say it is in the same process since I have sink and source in the same
GRC setup. The failure shows up when the generated python script instantiates an
UHD devices the second time as far as I understand.
Is there any combined UHD_usrp_sink/source block for GRC or how is this to 
be done practically?

Thanks
Ralf


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] E100 - No devices found for ----->

[Ralf Wierse]

> -Original Message-
> From: Jason Abele [mailto:ja...@ettus.com] 
> Sent: Thursday, June 23, 2011 1:04 PM
> To: Ralf Wierse
> Cc: discuss-gnuradio Discussion Group
> Subject: Re: [Discuss-gnuradio] E100 - No devices found for ->
> 
> 
> On Thu, Jun 23, 2011 at 3:16 AM, Ralf Wierse 
>  wrote:
> > OK, first simple reason discovered.
> > UHD can only be used for one device - either UHD_usrp_sink 
> or source.
> >
> > How can UHD be used for both devices in parallel?
> 
> You have to access both source and sink from the same process, but
> then it is possible to use both at the same time.
> 
> Jason


Hi Jason,
thanks but I am a little confused.
I would say it is in the same process since I have sink and source in the same
GRC setup. The failure shows up when the generated python script instantiates an
UHD devices the second time as far as I understand.
Is there any combined UHD_usrp_sink/source block for GRC or how is this to 
be done practically?

Thanks
Ralf


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Installng GNURadio from git repository

[Tom Rondeau]

On Thu, Jun 23, 2011 at 12:18 AM, sumitstop  wrote:

>
> Hi Tom It worked finally.After 2-3 link failure messages it got installed.
> I saw some posts in the forum that gnuradio.org is down hence thought that
> it might be relate to that.


The website has been continually up and functioning since we set up the new
server last weekend. The reports of it being down are due to caching issues
in switching from the old server to the new one. I hope those are resolved
quickly. But the server itself looks very stable!

Tom




> Tom Rondeau wrote:
> >
> > On Wed, Jun 22, 2011 at 1:58 PM, sumitstop
> > wrote:
> >
> >>
> >> I was trying to install GNURadio with the following commands
> >> # Install GNU Radio from git
> >>
> >> git clone http://gnuradio.org/git/gnuradio.git
> >>
> >> cd gnuradio
> >> ./bootstrap
> >> ./configure
> >> make
> >>
> >> after typing this in the terminal  it displays
> >>
> >> Initialized empty Git repository in /home/cogwsn/gnuradio/.git/
> >>
> >> and then nothing happens for long time.
> >> need some help.
> >> a few months back I installed using the same process and it worked well.
> >> Thanks
> >> Sumit.
> >>
> >> -
> >> Sumit Kr.
> >> Research Assistant
> >> Communication Research center
> >> IIIT Hyderabad
> >> India
> >>
> >
> >
> > Sumit,
> > Just let go for a while; it does take a long time.
> >
> > If you can (that is, if your firewall settings will let you), use the git
> > protocol:
> >  git clone git://gnuradio.org/gnuradio
> >
> > It has the nice property of telling you what its doing and is a lot
> > faster.
> >
> > Tom
> >
> > ___
> > Discuss-gnuradio mailing list
> > Discuss-gnuradio@gnu.org
> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> >
> >
>
>
> -
> Sumit Kr.
> Research Assistant
> Communication Research center
> IIIT Hyderabad
> India
> --
> View this message in context:
> http://old.nabble.com/Installng-GNURadio-from-git-repository-tp31905566p31908590.html
> Sent from the GnuRadio mailing list archive at Nabble.com.
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] E100 - No devices found for ----->

[Jason Abele]

On Thu, Jun 23, 2011 at 3:16 AM, Ralf Wierse  wrote:
> OK, first simple reason discovered.
> UHD can only be used for one device - either UHD_usrp_sink or source.
>
> How can UHD be used for both devices in parallel?

You have to access both source and sink from the same process, but
then it is possible to use both at the same time.

Jason

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] E100 - No devices found for ----->

[Ralf Wierse]

OK, first simple reason discovered.
UHD can only be used for one device - either UHD_usrp_sink or source.

How can UHD be used for both devices in parallel?

Thanks,
Ralf

> -Original Message-
> From: discuss-gnuradio-bounces+r.wierse=brunel...@gnu.org 
> [mailto:discuss-gnuradio-bounces+r.wierse=brunel...@gnu.org] 
> On Behalf Of Ralf Wierse
> Sent: Thursday, June 23, 2011 10:29 AM
> To: 'discuss-gnuradio Discussion Group'
> Subject: [Discuss-gnuradio] E100 - No devices found for ->
> 
> 
> Hi all,
> 
> we are new with E100.
> 
> we managed to use UHD:USRP_Source without further 
> configuration and display
> it on QT_GUI_SINK.
> 
> we don't manage with UHD:USRP_Sink without further configuration:
> 
> File 
> "/usr/local/lib/python2.6/site-packages/gnuradio/uhd/uhd_swig.
> py", line 1854, in usrp_sink
> return _uhd_swig.usrp_sink(*args, **kwargs)
> RuntimeError: LookupError: KeyError: No devices found for ->
> Empty Device Address
> 
> How to configure the sink address?
> 
> Any help appreciated!
> thanks!
> Ralf
> 
> uhd_usrp_probe output:
> 
> linux; GNU C++ version 4.5.3 20110311 (prerelease); 
> Boost_104500; UHD_003.000.001-
> 
> Opening USRP-E on /dev/usrp_e0
> Loading FPGA image: 
> /usr/share/uhd/images/usrp_e100_fpga.bin... done = 1
> Configuration complete.
> re-Opening USRP-E on /dev/usrp_e0
> USRP-E100 clock control: 6
>   r_counter: 1
>   a_counter: 0
>   b_counter: 12
>   prescaler: 8
>   vco_divider: 2
>   chan_divider: 15
>   vco_rate: 1920.00MHz
>   chan_rate: 960.00MHz
>   out_rate: 64.00MHz
> 
>   _
>  /
> |   Device: usrp-e device
> | _
> |/
> |   |   Mboard: usrp-e mboard
> |   |   vendor: 3
> |   |   device: 1
> |   |   revision: 3
> |   |   content: 0
> |   |   model: E100
> |   |   serial: EAR10ZFE1
> |   | _
> |   |/
> |   |   |   RX DSP: usrp-e ddc0
> |   |   |   Codec Rate: 64.00 Msps
> |   | _
> |   |/
> |   |   |   TX DSP: usrp-e duc0
> |   |   |   Codec Rate: 64.00 Msps
> |   | _
> |   |/
> |   |   |   RX Dboard: usrp-e dboard (rx unit)
> |   |   | _
> |   |   |/
> |   |   |   |   RX Subdev: LF RX (0x000f) - AB
> |   |   |   |   Antennas: 
> |   |   |   |   Freq range: -32.000 to 32.000 Mhz
> |   |   |   |   Gain Elements: None
> |   |   |   |   Connection Type: C
> |   |   |   |   Uses LO offset: No
> |   |   | _
> |   |   |/
> |   |   |   |   RX Subdev: LF RX (0x000f) - BA
> |   |   |   |   Antennas: 
> |   |   |   |   Freq range: -32.000 to 32.000 Mhz
> |   |   |   |   Gain Elements: None
> |   |   |   |   Connection Type: c
> |   |   |   |   Uses LO offset: No
> |   |   | _
> |   |   |/
> |   |   |   |   RX Subdev: LF RX (0x000f) - A
> |   |   |   |   Antennas: 
> |   |   |   |   Freq range: -32.000 to 32.000 Mhz
> |   |   |   |   Gain Elements: None
> |   |   |   |   Connection Type: R
> |   |   |   |   Uses LO offset: No
> |   |   | _
> |   |   |/
> |   |   |   |   RX Subdev: LF RX (0x000f) - B
> |   |   |   |   Antennas: 
> |   |   |   |   Freq range: -32.000 to 32.000 Mhz
> |   |   |   |   Gain Elements: None
> |   |   |   |   Connection Type: r
> |   |   |   |   Uses LO offset: No
> |   |   | _
> |   |   |/
> |   |   |   |   RX Codec: usrp-e adc - ad9522
> |   |   |   |   Gain range ad9862 pga: 0.0 to 20.0 step 1.0 dB
> |   | _
> |   |/
> |   |   |   TX Dboard: usrp-e dboard (tx unit)
> |   |   | _
> |   |   |/
> |   |   |   |   TX Subdev: LF TX (0x000e) - AB
> |   |   |   |   Antennas: 
> |   |   |   |   Freq range: -32.000 to 32.000 Mhz
> |   |   |   |   Gain Elements: None
> |   |   |   |   Connection Type: C
> |   |   |   |   Uses LO offset: No
> |   |   | _
> |   |   |/
> |   |   |   |   TX Subdev: LF TX (0x000e) - BA
> |   |   |   |   Antennas: 
> |   |   |   |   Freq range: -32.000 to 32.000 Mhz
> |   |   |   |   Gain Elements: None
> |   |   |   |   Connection Type: c
> |   |   |   |   Uses LO offset: No
> |   |   | _
> |   |   |/
> |   |   |   |   TX Subdev: LF TX (0x000e) - A
> |   |   |   |   Antennas: 
> |   |   |   |   Freq range: -32.000 to 32.000 Mhz
> |   |   |   |   Gain Elements: None
> |   |   |   |   Connection Type: R
> |   |   |  

[Discuss-gnuradio] Feasibility study of Porting GNU Radio on experimental processor

[Amanullah]

Hi

 

I want to port the GNU radio code base to TTA processor architecture. The
processor is programmed on an FPGA.  The compiler for TTA is TCE which
supports C and C++. 

I have some initial questions about feasibility of such project. Is it
possible to port GNU radio code to an embedded processor with no OS support?
GNU Radio uses Boost Shared Library. Is Boost library portable and can it
work without an Operating system??

GNU build system also do not seem to support TCE compiler (CFLAGS=tcecc
gives error). Is there any project where GNU radio have been used without
any OS support as standalone system??

 

Details of TCE compiler and TTA can be found at  
http://tce.cs.tut.fi/

 

Please reply me as soon as possible.

 

Thanks and Regards

Amanullah Ghazi

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] E100 - No devices found for ----->

[Ralf Wierse]

Hi all,

we are new with E100.

we managed to use UHD:USRP_Source without further configuration and display
it on QT_GUI_SINK.

we don't manage with UHD:USRP_Sink without further configuration:

File "/usr/local/lib/python2.6/site-packages/gnuradio/uhd/uhd_swig.py", line 
1854, in usrp_sink
return _uhd_swig.usrp_sink(*args, **kwargs)
RuntimeError: LookupError: KeyError: No devices found for ->
Empty Device Address

How to configure the sink address?

Any help appreciated!
thanks!
Ralf

uhd_usrp_probe output:

linux; GNU C++ version 4.5.3 20110311 (prerelease); Boost_104500; 
UHD_003.000.001-

Opening USRP-E on /dev/usrp_e0
Loading FPGA image: /usr/share/uhd/images/usrp_e100_fpga.bin... done = 1
Configuration complete.
re-Opening USRP-E on /dev/usrp_e0
USRP-E100 clock control: 6
  r_counter: 1
  a_counter: 0
  b_counter: 12
  prescaler: 8
  vco_divider: 2
  chan_divider: 15
  vco_rate: 1920.00MHz
  chan_rate: 960.00MHz
  out_rate: 64.00MHz

  _
 /
|   Device: usrp-e device
| _
|/
|   |   Mboard: usrp-e mboard
|   |   vendor: 3
|   |   device: 1
|   |   revision: 3
|   |   content: 0
|   |   model: E100
|   |   serial: EAR10ZFE1
|   | _
|   |/
|   |   |   RX DSP: usrp-e ddc0
|   |   |   Codec Rate: 64.00 Msps
|   | _
|   |/
|   |   |   TX DSP: usrp-e duc0
|   |   |   Codec Rate: 64.00 Msps
|   | _
|   |/
|   |   |   RX Dboard: usrp-e dboard (rx unit)
|   |   | _
|   |   |/
|   |   |   |   RX Subdev: LF RX (0x000f) - AB
|   |   |   |   Antennas: 
|   |   |   |   Freq range: -32.000 to 32.000 Mhz
|   |   |   |   Gain Elements: None
|   |   |   |   Connection Type: C
|   |   |   |   Uses LO offset: No
|   |   | _
|   |   |/
|   |   |   |   RX Subdev: LF RX (0x000f) - BA
|   |   |   |   Antennas: 
|   |   |   |   Freq range: -32.000 to 32.000 Mhz
|   |   |   |   Gain Elements: None
|   |   |   |   Connection Type: c
|   |   |   |   Uses LO offset: No
|   |   | _
|   |   |/
|   |   |   |   RX Subdev: LF RX (0x000f) - A
|   |   |   |   Antennas: 
|   |   |   |   Freq range: -32.000 to 32.000 Mhz
|   |   |   |   Gain Elements: None
|   |   |   |   Connection Type: R
|   |   |   |   Uses LO offset: No
|   |   | _
|   |   |/
|   |   |   |   RX Subdev: LF RX (0x000f) - B
|   |   |   |   Antennas: 
|   |   |   |   Freq range: -32.000 to 32.000 Mhz
|   |   |   |   Gain Elements: None
|   |   |   |   Connection Type: r
|   |   |   |   Uses LO offset: No
|   |   | _
|   |   |/
|   |   |   |   RX Codec: usrp-e adc - ad9522
|   |   |   |   Gain range ad9862 pga: 0.0 to 20.0 step 1.0 dB
|   | _
|   |/
|   |   |   TX Dboard: usrp-e dboard (tx unit)
|   |   | _
|   |   |/
|   |   |   |   TX Subdev: LF TX (0x000e) - AB
|   |   |   |   Antennas: 
|   |   |   |   Freq range: -32.000 to 32.000 Mhz
|   |   |   |   Gain Elements: None
|   |   |   |   Connection Type: C
|   |   |   |   Uses LO offset: No
|   |   | _
|   |   |/
|   |   |   |   TX Subdev: LF TX (0x000e) - BA
|   |   |   |   Antennas: 
|   |   |   |   Freq range: -32.000 to 32.000 Mhz
|   |   |   |   Gain Elements: None
|   |   |   |   Connection Type: c
|   |   |   |   Uses LO offset: No
|   |   | _
|   |   |/
|   |   |   |   TX Subdev: LF TX (0x000e) - A
|   |   |   |   Antennas: 
|   |   |   |   Freq range: -32.000 to 32.000 Mhz
|   |   |   |   Gain Elements: None
|   |   |   |   Connection Type: R
|   |   |   |   Uses LO offset: No
|   |   | _
|   |   |/
|   |   |   |   TX Subdev: LF TX (0x000e) - B
|   |   |   |   Antennas: 
|   |   |   |   Freq range: -32.000 to 32.000 Mhz
|   |   |   |   Gain Elements: None
|   |   |   |   Connection Type: r
|   |   |   |   Uses LO offset: No
|   |   | _
|   |   |/
|   |   |   |   TX Codec: usrp-e dac - ad9522
|   |   |   |   Gain range ad9862 pga: -20.0 to 0.0 step 0.1 dB
 



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio