Hello List, I just re-installed UHD and GNURadio and now even the basic UHD commands don´t work anymore. I have built uhd_003.004.000-71810ad and also used the latest firmware and fpga image (also 003.004...). Ping to the device´s default address works fine. Also burning the new firmware and fpga image worked alright. But when I try to use uhd_find_devices I get "No UHD Devices Found" and uhd_usrp_probe returns ""Error: LookupError: KeyError: No devices found for -----> Empty Device Address". Does anybody here have an idea why I get this error? Thanks in advance! Regards Sebastian

Yes it does. Thanks for that. Sebastian On Wed, 23 Nov 2011 08:10:11 -0800 Josh Blum wrote: > > > On 11/23/2011 06:04 AM, Sebastian Döring wrote: >> Hello List, >> >> I just re-installed UHD and GNURadio and now even the >>basic UHD commands >> don´t work anymore. >> I have built uhd_003.004.000-71810ad and also used the >>latest firmware >> and fpga image (also 003.004...). >> >> Ping to the device´s default address works fine. Also >>burning the new >> firmware and fpga image worked alright. >> >> But when I try to use uhd_find_devices I get "No UHD >>Devices Found" and >> uhd_usrp_probe returns ""Error: LookupError: KeyError: >>No devices found >> for -----> Empty Device Address". >> >> Does anybody here have an idea why I get this error? >> > > This looks like a firewall issue with broadcast packets. > http://files.ettus.com/uhd_docs/manual/html/usrp2.html#firewall-issues > Does uhd_find_devices --args="addr=192.168.10.2" work? > > -josh > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Hello list, I am using Octave to process time-series samples from my USRP N210. When I compute the periodogram of these time samples, I always get strange peaks at the edges of my PSD and I can definetly count out that they belong to the actual spectrum. Does anybody know what causes those peaks? (I dont think that this problem is caused by Octave, and this is why I am posting this question to the usrp-list and not to tho octave-list.) Regards Sebastian

On Mon, 05 Dec 2011 07:41:15 -0800 Josh Blum wrote: > > > On 12/05/2011 04:50 AM, Sebastian Döring wrote: >> Hello list, >> >> I am using Octave to process time-series samples from my >>USRP N210. >> >> When I compute the periodogram of these time samples, I >>always get >> strange peaks at the edges of my PSD and I can definetly >>count out that >> they belong to the actual spectrum. >> Does anybody know what causes those peaks? >> >> (I dont think that this problem is caused by Octave, and >>this is why I >> am posting this question to the usrp-list and not to tho >>octave-list.) >> > > At the start of burst, there will be 20 samples or so of >transients due > to the filters in the decimation chain. Are you perhaps >seeing that? > > -josh > This could be an explanation, although there are rather less than 10 samples that form the peak and there´s also a smaller peak at the end of the spectrum. Thanks Sebastian > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Hello, I have been doing some spectrum sensing with the USRP N210 and the XCVR2450. Today I tried the same stuff with the SBX daughterboard and suddenly the signal level at the output seems to have an offset of around +20dB. With the XCVR I usually measure a noise level around -100dB and with the SBX I get something around -80dB (both with gain tuned to "0"). My question is, if there's some other gain parameter in the SBX that I can´t control? I used the same antenna and the same USRP. Any hints highly appreciated! Regards Sebastian

Thanks for the answer Jason, the output of uhd_fft.py is the same for both boards and I no longer think that I am having problems with the gain calibration. I realized the offset when I was estimating the noise power using uhd_rx_cfile.py and afterwards processing the samples with octave. What I do is simply reading the complex binary data, performing fft and magnitude squaring. I found out that the data comming from the SBX seems to be corrupted by some sine or sine^2. I am not talking about an unexpected peak somewhere in the spectrum but about the whole spectrum looking like a sine^2 instead of a rather flat white noise floor (that's what I see using the XCVR and what it is supposed to look like, since I checked it with some other spectrum analyzer too). The output of uhd_usrp_probe is the following: _____________________________________________________ / | Device: USRP2 / N-Series Device | _____________________________________________________ | / | | Mboard: USRP-N210 | | hardware: 2561 | | mac-addr: a0:36:fa:25:32:f2 | | ip-addr: 192.168.10.2 | | gpsdo: none | | serial: EFR12W2UP | | | | Time sources: none, external, _external_, mimo | | Clock sources: internal, external, mimo | | Sensors: mimo_locked, ref_locked | | _____________________________________________________ | | / | | | RX DSP: 0 | | | Freq range: -50.000 to 50.000 Mhz | | _____________________________________________________ | | / | | | RX DSP: 1 | | | Freq range: -50.000 to 50.000 Mhz | | _____________________________________________________ | | / | | | RX Dboard: A | | | ID: SBX (0x0054) | | | Serial: E8R12X9XS | | | _____________________________________________________ | | | / | | | | RX Subdev: 0 | | | | Name: SBX RX | | | | Antennas: TX/RX, RX2, CAL | | | | Sensors: lo_locked | | | | Freq range: 400.000 to 4400.000 Mhz | | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB | | | | Connection Type: IQ | | | | Uses LO offset: No | | | _____________________________________________________ | | | / | | | | RX Codec: A | | | | Name: ads62p44 | | | | Gain range digital: 0.0 to 6.0 step 0.5 dB | | | | Gain range fine: 0.0 to 0.5 step 0.1 dB | | _____________________________________________________ | | / | | | TX DSP: 0 | | | Freq range: -250.000 to 250.000 Mhz | | _____________________________________________________ | | / | | | TX Dboard: A | | | ID: SBX (0x0055) | | | Serial: E8R12X9XS | | | _____________________________________________________ | | | / | | | | TX Subdev: 0 | | | | Name: SBX TX | | | | Antennas: TX/RX, CAL | | | | Sensors: lo_locked | | | | Freq range: 400.000 to 4400.000 Mhz | | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB | | | | Connection Type: QI | | | | Uses LO offset: No | | | _____________________________________________________ | | | / | | | | TX Codec: A | | | | Name: ad9777 | | | | Gain Elements: None I really appreciate any further information. Regards Sebastian On Mon, 12 Mar 2012 11:07:39 -0700 Jason Abele wrote: > Sebastian, > > The units displayed in uhd_fft.py are not absolute and >the XCVR and SBX > have vastly different absolute gain at a setting of >"0dB". Thus, they > are not really comparable at the same gain setting. > > If you want to compare them, apply a sine wave of known >power (say > -50dBm) and use it to "calibrate" the units in >uhd_fft.py into dBm. > > Then you can compare SBX to XCVR. > > Also note that the implicit scale factor in the >"calibration" performed > above will vary with gain setting. > > If you send your uhd_ffy.py command, it will be easier >to comment on the > expected SBX behavior. > > It is also helpful to provide the output of >uhd_usrp_probe such that we > can see the UHD and hardware versions you are using. > > Thanks > Jason > > On Mon, Mar 12, 2012 at 01:51:51PM +0100, Sebastian >Döring wrote: >> Hello, >> >> I have been doing some spectrum sensing with the USRP >>N210 and the >> XCVR2450. >> Today I tried the same stuff with the SBX daughterboard >>and suddenly >> the signal level at the output seems to have an offset >>of around >> +20dB. >> With the XCVR I usually measure a noise level around >>-100dB and with >> the SBX I get something around -80dB (both with gain >>tuned to "0"). >> >> My question is, if there's some other gain parameter in >>the SBX that >> I can´t control? >> I used the same antenna and the same USRP. >> >> Any hints highly appreciated! >> >> Regards >> Sebastian >> >> _______________________________________________ >> USRP-users mailing list >> USRP-users@lists.ettus.com >> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

@ steam: UHD version is "UHD_003.004.000-b8e41cb" and FPGA image is the corresponding one for revision number R2. @ Nick: I attached 2 figures. The supposed-to-look-like case I get with XCVR and independent spectrum analyzer and the one I get using the SBX. Both data sets have been recorded using "uhd_rx_cfile.py -f 2.4G -N 1024". I processed the samples with octave performing fft, square magnitude and translated them to dB level scaled with 20*log10(x). -Sebastian On Tue, 13 Mar 2012 18:25:34 +0100 "steam2009@t-online.de" wrote: > Out of curiousity what FPGA / UHD version are you using. > > > Von: "Sebastian Döring" > Datum: Tue, 13 Mar 2012 10:11:22 +0100 > >> The output of uhd_usrp_probe is the following: > > _____________________________________________________ > / > | Device: USRP2 / N-Series Device > | > _____________________________________________________ > | / > | | Mboard: USRP-N210 > | | hardware: 2561 > | | mac-addr: a0:36:fa:25:32:f2 > | | ip-addr: 192.168.10.2 > | | gpsdo: none > | | serial: EFR12W2UP > | | > | | Time sources: none, external, _external_, mimo > | | Clock sources: internal, external, mimo > | | Sensors: mimo_locked, ref_locked > | | > _____________________________________________________ > | | / > | | | RX DSP: 0 > | | | Freq range: -50.000 to 50.000 Mhz > | | > _____________________________________________________ > | | / > | | | RX DSP: 1 > | | | Freq range: -50.000 to 50.000 Mhz > | | > _____________________________________________________ > | | / > | | | RX Dboard: A > | | | ID: SBX (0x0054) > | | | Serial: E8R12X9XS > | | | > _____________________________________________________ > | | | / > | | | | RX Subdev: 0 > | | | | Name: SBX RX > | | | | Antennas: TX/RX, RX2, CAL > | | | | Sensors: lo_locked > | | | | Freq range: 400.000 to 4400.000 Mhz > | | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB > | | | | Connection Type: IQ > | | | | Uses LO offset: No > | | | > _____________________________________________________ > | | | / > | | | | RX Codec: A > | | | | Name: ads62p44 > | | | | Gain range digital: 0.0 to 6.0 step 0.5 >dB > | | | | Gain range fine: 0.0 to 0.5 step 0.1 dB > | | > _____________________________________________________ > | | / > | | | TX DSP: 0 > | | | Freq range: -250.000 to 250.000 Mhz > | | > _____________________________________________________ > | | / > | | | TX Dboard: A > | | | ID: SBX (0x0055) > | | | Serial: E8R12X9XS > | | | > _____________________________________________________ > | | | / > | | | | TX Subdev: 0 > | | | | Name: SBX TX > | | | | Antennas: TX/RX, CAL > | | | | Sensors: lo_locked > | | | | Freq range: 400.000 to 4400.000 Mhz > | | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB > | | | | Connection Type: QI > | | | | Uses LO offset: No > | | | > _____________________________________________________ > | | | / > | | | | TX Codec: A > | | | | Name: ad9777 > | | | | Gain Elements: None > > > > I really appreciate any further information. > > Regards > Sebastian > > > On Mon, 12 Mar 2012 11:07:39 -0700 > Jason Abele wrote: >> Sebastian, >> >> The units displayed in uhd_fft.py are not absolute and >>the XCVR and SBX >> have vastly different absolute gain at a setting of >>"0dB". Thus, they >> are not really comparable at the same gain setting. >> >> If you want to compare them, apply a sine wave of known >>power (say >> -50dBm) and use it to "calibrate" the units in >>uhd_fft.py into dBm. >> >> Then you can compare SBX to XCVR. >> >> Also note that the implicit scale factor in the >>"calibration" performed >> above will vary with gain setting. >> >> If you send your uhd_ffy.py command, it will be easier >>to comment on the >> expected SBX behavior. >> >> It is also helpful to provide the output of >>uhd_usrp_probe such that we >> can see the UHD and hardware versions you are using. >> >> Thanks >> Jason >> >> On Mon, Mar 12, 2012 at 01:51:51PM +0100, Sebastian >>Döring wrote: >>> Hello, >>> >>> I have been doing some spectrum sensing with the USRP >>>N210 and the >>> XCVR2450. >>> Today I tried the same stuff with the SBX daughterboard >>>and suddenly >>> the signal level at the output seems to have an offset >>>of around >>> +20dB. >>> With the XCVR I usually measure a noise level around >>>-100dB and with >>> the SBX I get something around -80dB (both with gain >>>tuned to "0"). >>> >>> My question is, if there's some other gain parameter in >>>the SBX that >>> I can´t control? >>> I used the same antenna and the same USRP. >>> >>> Any hints highly appreciated! >>> >>> Regards >>> Sebastian >>> >>> _______________________________________________ >>> USRP-users mailing list >>> USRP-users@lists.ettus.com >>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > > > > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Hello, I discovered that uhd_rx_cfile.py is giving me different data depending on the number of samples I take from a certain constant bandwidth of noise only samples. In theory the noise power calculated from these samples is supposed to get more accurate the more samples I take, but the more samples I take, the higher the noise power value gets ( for example several dB after doubling the number of samples). Any hints are highly appreciated. Thanks. -Sebastian

On Wed, 28 Mar 2012 09:59:48 -0400 mleech@ripnet.com wrote: > > > On Wed, 28 Mar 2012 15:18:42 +0200, Sebastian Döring >wrote: > >> > Hello, >> >> I discovered that uhd_rx_cfile.py is giving me different >> > data depending on the number of samples I take from a >> certain > constant bandwidth of noise only samples. >> In theory the noise power > calculated from these samples is >> supposed to get more accurate the > more samples I take, >> but the more samples I take, the higher the noise > power >> value gets ( for example several dB after doubling the >> > number of samples). >> >> Any hints are highly appreciated. >> Thanks. >> > >> -Sebastian >> >> _______________________________________________ >> > USRP-users mailing list >> USRP-users@lists.ettus.com [1] >> > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > [2] > > uhd_rx_cfile.py by default writes complex-float samples, >so that's > the first thing you need to make sure you're handling >correctly. > > > Secondly, how are you computing the noise power across >the bandwidth > represented by the samples? > > Since they're complex samples, you should > be calculating, roughly: > > power = AVG(I**2 + Q**2) > That´s exactly what I am doing except I am also computing the FFT before computing the suared magnitude to get the spectral power. > > > > Links: > ------ > [1] mailto:USRP-users@lists.ettus.com > [2] > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

On Thu, 29 Mar 2012 14:40:33 +0900 Haris KREMO wrote: > Sebastian, > > Are you sure that the bandwidth is not changed when you >change the sample rate? I am not talking about the sample rate but number of samples taken (N). The sample rate stays the same. It's just the resolution of the spectrum that changes. > > I hope I am looking into a proper version here, but note >the parentheses below: > > http://gnuradio.org/redmine/projects/gnuradio/repository/revisions/50646fa13731ce8dd6382a0f54766d839e634fc5/entry/gr-uhd/apps/uhd_rx_cfile.py#L113 > > parser.add_option("", "--samp-rate", type="eng_float", >default=1e6, > help="set sample rate (bandwidth) >[default=%default]") > > In any case, is there any consistency in the increase? >If the noise power grows by 3 dB when you double the >sampling rate (kTB formula) than the bandwidth is somehow >doubled as well. > > Hope it helps, > > H. > > On 3/29/2012 1:33 AM, mleech@ripnet.com wrote: >> >> If you're averaging, (like with a single-pole IIR >>filter), then it takes a while for the average to "grow" >>to a stable value before it stabilizes. >> >> I do received-power calculations all the time, and they >>don't grow without bound. You're just processing >>something incorrectly. >> >> -Marcus >> >> On Wed, 28 Mar 2012 18:30:24 +0200, Sebastian Döring >>wrote: >> >>> On Wed, 28 Mar 2012 09:59:48 -0400 >>> mleech@ripnet.com wrote: >>>> On Wed, 28 Mar 2012 15:18:42 +0200, Sebastian Döring >>>>wrote: >>>> Hello, >>>>> I discovered that uhd_rx_cfile.py is giving me different >>>> data depending on the number of samples I take from a >>>>> certain >>>> constant bandwidth of noise only samples. >>>>> In theory the noise power >>>> calculated from these samples is >>>>> supposed to get more accurate the >>>> more samples I take, >>>>> but the more samples I take, the higher the noise >>>> power >>>>> value gets ( for example several dB after doubling the >>>> number of samples). >>>>> Any hints are highly appreciated. Thanks. -Sebastian >>>>>_______________________________________________ >>>> USRP-users mailing list >>>>> USRP-users@lists.ettus.com >>>>> [1] >>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >>>>[2] uhd_rx_cfile.py by default writes complex-float >>>>samples, so that's the first thing you need to make sure >>>>you're handling correctly. Secondly, how are you >>>>computing the noise power across the bandwidth >>>>represented by the samples? Since they're complex >>>>samples, you should be calculating, roughly: power = >>>>AVG(I**2 + Q**2) >>> >>> That´s exactly what I am doing except I am also >>>computing >>> the FFT before computing the suared magnitude to get the >>> spectral power. >>> >>>> Links: ------ [1] mailto:USRP-users@lists.ettus.com >>>> [2] >>>>http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >>> >>> >> >> >> _______________________________________________ >> USRP-users mailing list >> USRP-users@lists.ettus.com >> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >> >