Re: [Discuss-gnuradio] Burg spectral estimation
Hi Bob, On Fri, 26 Mar 2010 21:02:19 -0400, Robert McGwier wrote: > Jens: > > Have you considered and rejected Pisarenko estimtion techniques or just not > tried them yet? The original application was narrow band interference suppression in DSSS systems. Burg's method works quite well as it automatically gives one the filter coefficients for the suppression filter. Eigenspace based methods are of course very another interesting thing to make available in GNU Radio - if we find students willing to implement this as part of their course work in Karlsruhe, Martin and I will gladly support them (anyone reading this? :). Jens ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] packet loss during carrier-sensing (as a transceiver node)
Dear all, Thanks for your reading in advance. I met a problem when I attempt to use USRP as a transciever node. I try to realize a transceiver by constructing two python threadings, one is "sender" and the other one is "listener". The sender is responsible for sending packets to USRP for transmission into the air, after ensuring the medium is idle. The listener is to receive packets from USRP. However, when "the sender" tried to run continuous "carrier sense" until busy medium becomes idle, I discovered that the "listener" couldn't work to receive the packets that should arrive during the period of carrier sensing. In the meanwhile, the listener was not conscious of any packet arrival, even "corrupted" packets. My preliminary conjecture is the "sender" occupies all of the resources, so the listener is unable to perform packet reception. p.s. My pseudo code to implement continuous carrier sense: while medium_busy() print "carrier sensed" sleep for a period of time, "DIFS" send packet >From the condition I described above, I want to ask: 1. I guess the problem results from a bad scheduling between listener and sender threadings. Is there any other possibility to cause the problem ? If yes, what is it? 2. Does anyone know some other way to implement a transceiver on USRP? If yes, please briefly describe it. My operation environments: 1. Ubuntu 9.04 2. Gnuradio 3.2.0 3. USRP1 + XCVR2450 Thank you again! Sincerely, Larsson ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] How to add c++ modules after gnuradio-3.2.2. binary installation?
Hi I installed gnuradio-3.2.2. Binary package in Ubuntu 9.04. It was not flexible to include new c++ files (I could not find bootstrap, configure.ac files etc in usr/share/gnuradio installation directory). I then downloaded gnuradio-3.2.2.tar.gz and gr-howto-write-a-block-3.2.2.tar.gz files and unzipped them in my home folder, and gr-howto-write-a-block-3.2.2 was included as a subdirectory in the gnuradio-3.2.2 directory. I used installation commands ./bootstrap, ./configure, make, sudo make install in gnuradio-3.2.2 directory, and no error was reported. I then tried to run file qa_howto.py (after chmod +x qa* ) in directory gr-howto-write-a-block-3.2.2/src/python, as follows: ./qa_howto.py Error was reported that "in import howto", "howto" module could not be recognized. I tried many other means, including modifying makefile.am in several directories, and using installation ./bootstrap, ./configure, make, sudo make install in gr-howto-write-a-block-3.2.2 directory. No error was reported. But still ./qa_howto.py could not work. Questions: 1) How can I make this work? 2) How can I add new functions and modules using c++ files based on gnuradio-3.2.2 binary installation? Thank you. Jack -- View this message in context: http://old.nabble.com/How-to-add-c%2B%2B-modules-after-gnuradio-3.2.2.-binary-installation--tp28036932p28036932.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Receiving ATSC using USRP2
Hi all, I've got a USRP2 with a WBX attempting to receive ATSC signals. I'm using the latest (git HEAD on 27 March 2010) version of everything (firmware and software). usrp2_fft.py shows a strong signal for a local tv transmitter (680 - 686 MHz). It looks like the ATSC code is written for the original USRP, using a decimation of 10 to get 6.4 Msps, interpolated by three to get 19.2 Msps. Since I have a USRP2, I can't get exactly 6.4 Msps. Has anyone gotten this to work using a USRP2? I've tried using 5, 10, and 20 Msps, interpolating up to 20 Msps (I've also tried various gains). In addition to changing the interpolation rate in interp_short.py, I've gone through the code and changed 19.2e6 to 20e6 in interp_short.py, fpll.py, xlate.py, atsc_fpll.cc, and atsc_bit_timing_loop.cc. However, nothing is output from ./btl-fsd.py (a symptom seen a few times in this list with no obvious solutions). None of the programs output any error messages, just that they are using SSE, and fpll.py reports setting initial_freq to 3065000. I've sanity checked the logged data in matlab and verified a signal exists from -3 MHz to +3 MHz. Any hints as to what I am missing or next steps to debug the issue? Thanks, Jared Casper ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] How to add c++ modules after gnuradio-3.2.2. binary installation?
Hi, 1) I don't think gr-howto-write-a-block is part of the normal build environment -- there's a separate one within this directory. Try running: ./bootstrap ./configure make make check sudo make install from inside this directory (i.e gnuradio/gr-howto-write-a-block) You might run into some weird issues if you've installed the binary packages before compiling from source (unless youve changed the prefix) as it's possible you've got two copies of gnuradio - Make sure you've removed the old binary installs. 2) I add new C++ blocks into my own module by following the instructions at http://www.mail-archive.com/patch-gnura...@gnu.org/msg00123.html (and a bit of trial and error whilst I got the hang of automake etc) There might be an easier way than this however! Cheers, Tim On Sat, Mar 27, 2010 at 8:18 PM, Yao Jack wrote: > > > Hi > > I installed gnuradio-3.2.2. Binary package in Ubuntu 9.04. > It was not flexible to include new c++ files > (I could not find bootstrap, configure.ac files etc in > usr/share/gnuradio > installation directory). > > I then downloaded gnuradio-3.2.2.tar.gz and > gr-howto-write-a-block-3.2.2.tar.gz files and unzipped them in my home > folder, > and > gr-howto-write-a-block-3.2.2 was included as a subdirectory in the > gnuradio-3.2.2 directory. > > I used installation commands ./bootstrap, ./configure, make, sudo make > install > in gnuradio-3.2.2 directory, and no error was reported. I then tried to > run > file > qa_howto.py (after chmod +x qa* ) in directory > gr-howto-write-a-block-3.2.2/src/python, as follows: > > ./qa_howto.py > > Error was reported that "in import howto", "howto" module could not be > recognized. > I tried many other means, including modifying makefile.am in several > directories, > and > using installation ./bootstrap, ./configure, make, sudo make install > in gr-howto-write-a-block-3.2.2 directory. No error was reported. > > But still > ./qa_howto.py > could not work. > > Questions: > > 1) How can I make this work? > 2) How can I add new functions and modules using c++ files based on > gnuradio-3.2.2 binary installation? > > Thank you. > > Jack > -- > View this message in context: > http://old.nabble.com/How-to-add-c%2B%2B-modules-after-gnuradio-3.2.2.-binary-installation--tp28036932p28036932.html > Sent from the GnuRadio mailing list archive at Nabble.com. > > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] USRP 1 Enclosure
Does anyone have an extra USRP 1 Enclosure for sale? One of mine is from the pre-enclosure era. Thanks ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP 1 Enclosure
Hi Ryan, See below... Mike -- Forwarded message -- From: Matt Ettus Date: 18 June 2008 05:27 Subject: Re: [Discuss-gnuradio] USRP enclosure To: Chris Stankevitz Cc: "discuss-gnuradio@gnu.org" Chris Stankevitz wrote: > Where can I buy a USRP enclosure? I don't see it listed at > http://www.ettus.com/custom.html > I took it off the main page because most of the people who tried to buy them were doing it by mistake -- meaning they didn't realize that new USRPs include the enclosures. If you want to purchase one, they are $150 apiece. Just buy a DBSRX on the form (which costs the same), and IMMEDIATELY send an email to BOTH sa...@ettus.com and m...@ettus.com saying that you actually want an enclosure and not a DBSRX. Matt ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio On 27 March 2010 23:47, Ryan Pape wrote: > Does anyone have an extra USRP 1 Enclosure for sale? One of mine is > from the pre-enclosure era. > > Thanks > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] An Idea for rx_c_file
Hi, this is just an idea for an improvement to rx_c_file. When it outputs a file, there is no information about frequency, decimation, sample type etc... If you forget how you sampled it the information is useless. What if the rx_c_file program could output a file with this info automatically? Or could it be included in a header? This could also be read by the corresponding tx program. I'm no programmer (ie. I don't know how to implement this), and this could be a stupid idea, what do you think? Matt ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
