[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] USRP2 printing of character "S" bothersome!!

From: Marcus D. Leech
Subject: Re: [Discuss-gnuradio] USRP2 printing of character "S" bothersome!!
Date: Thu, 11 Nov 2010 18:53:55 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20101027 Fedora/3.0.10-1.fc12 Thunderbird/3.0.10

On 11/11/2010 05:59 PM, Bishal Thapa wrote:
Thank you Eric, Josh and Marcus,
  I had edited it to print "" nothing. Now, I am shunting it to /dev/null.

My main reason to ask this question was exactly was Marcus pointed out. I am seeing lots and lots of "S". When I switch channels to 7 or 3, I do see fewer compared to 6 or 11.
However, I believe something is wrong here.

here is my bbn_80211_rx.py command execution:

"sudo ./bbn_80211b_rx-B.py -f 2.442G -b"

this should mean using barker code and default decimation rate (of 4) and samples per baud (25). I am worried now? Could it be just that there are lots of APs broadcasting few too many beacons?

Thank you once again.

On Thu, Nov 11, 2010 at 5:47 PM, Eric Blossom <address@hidden> wrote:
On Thu, Nov 11, 2010 at 04:57:56PM -0500, Bishal Thapa wrote:
> Hello,
>   I am using USRP2 version of BBN code to look at AP beacons as seen by the
> USRP2 host. There is lots of "S" printing going on, which keeps me from
> reading AP beacon information from STDOUT (unless I save the output to a
> file, which I prefer not to). Is there anyway to enforce the printing of "S"
> character to go away. Here is my node's specification:
>    - BBN Code Location:
>    https://www.cgran.org/cgran/projects/bbn_80211/branches/usrp2_version
>    - CPU: Intel(R) Core(TM) 2 CPU E8400 @ 3GHz
>    - Memory: 4GB
>    - Hard Disk: 1TB
> My ubuntu version = 10.04
> GNuradio version = 3.3.0
> Thank you in advance for your help.

One of the joys of Free Software is you have the freedom to study how
the program works, and change it to make it do what you wish.  We
provide the source code to enable this freedom.

The "S" is written out on line 454 of usrp2_impl.cc

FWIW, it's written to stderr, not stdout, so you could just shunt
stderr into /dev/null:

 $ my-program 2>/dev/null


_______________________________________________ Discuss-gnuradio mailing list address@hidden http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
I don't know anything about the BBN code, but simply switching channels (frequencies) should have
  *zero* effect on the amount of overruns you are seeing, unless the BBN code is doing something
  different, depending on which channel you're using, which is possible, but I don't know what
  it does internally.

Principal Investigator
Shirleys Bay Radio Astronomy Consortium

reply via email to

[Prev in Thread] Current Thread [Next in Thread]