|
From: | Marcus Müller |
Subject: | Re: [Discuss-gnuradio] usrp_spectrum_sense.py input parameters in USRP B200 |
Date: | Mon, 16 Jan 2017 12:28:44 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 |
Hi Soumaya, while tuning, there will simply be transients, mostly of oscillator energy leaking into the receiver. You cannot use the data that you get while tuning. You might want to define "strange power values"; 2.4 GHz is an
ISM band, so a lot of traffic is to be expected there, and that
traffic is also probably very bursty, so that your observed values
might temporarily vary a lot, since your observation time is much
longer than the bursts in e.g. WiFi, your observed power is
basically the product of number of burst, burst energy of the
individual transmitter, and path loss between your receiver and
the transmitter. Still, why are you using such small sampling rates as 8 MS/s? With a good USB3 controller and a reasonably fast computer, you should easily be able to do 40 MS/s with the usrp_spectrum_sense program. In fact, on my throttled thinkpad X240, I'm currently doing ./usrp_spectrum_sense.py -s 40e6 -g 76 -F $((2**16)) 2.4e9 2.5e9 and it works just fine. Best regards, Marcus On 01/16/2017 10:32 AM, Soumaya el
barrak wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |