Re: [USRP-users] Device still not found

[Marcus D. Leech via USRP-users]

On 04/12/2019 12:30 AM, VINAYAK KARANDIKAR via USRP-users wrote:

Hello everyone,
 MATLAB still cannot find my USRP 
connected to the laptop. I have built an interface called 
'uhdinterface' which I use to issue commands to the USRP. But I 
received an error message saying:

"Unexpected standard exception from MEX file"

What do I do?
Thanks a lot,
Vinayak Anant Karandikar


Most people on this list are not MatLab users.

If your install includes the standard UHD utilities, what does:

uhd_usrp_probe --args "addr=192.168.10.2"

Return?



___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

[USRP-users] Device still not found

[VINAYAK KARANDIKAR via USRP-users]

Hello everyone,
 MATLAB still cannot find my USRP connected to
the laptop. I have built an interface called 'uhdinterface' which I use to
issue commands to the USRP. But I received an error message saying:
"Unexpected standard exception from MEX file"

What do I do?
Thanks a lot,
Vinayak Anant Karandikar
___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] Running two N310 radios independently

[Marcus D. Leech via USRP-users]

On 04/11/2019 04:18 PM, Kuldeep Gill wrote:


Hello Marcus,

Two radios on a single N310, there was similar question on mailing 
list which is somewhat related to my issue and was asked in 2015. 
Please find it attached below.


I'm not sure that you can have a configuration where you have multi_usrp 
objects pointing to different IP addresses within separate
  processes.  I don't think that the "housekeeping" (both that 
maintained by the OS kernel and UHD itself) can be split in this way.


But there's nothing that prevents you from having a single process with 
multiple threads, or even a single process that "owns"
  the multi_usrp object(s), and then uses any one of a number of Linux 
IPC mechanisms to communicate to other processes.




Hi LTP,
Ben just told me that yes, Ettus has tested things, and they work as
expected: you can have arbitrary combinations of sampling rates on both
Streamers, but if you do that, you can't use a single multi_usrp object
to handle things -- you'll need to use two multi_usrp, but that's not
really a problem, since you don't lose any relevant functionality this way.
  
Best regards,

Marcus
  
On 04/22/2015 12:28 PM, Marcus Müller wrote:

>/  Hi LTP,/
>/  /
>/  have a look at what RF NoC can do; it's still beta, but maybe it/
>/  enables you to solve your problems!/
>/  /
>/  Generally, you must use the same master clock rate on both/
>/  Daughterboards, but I don't think you must use the same sampling rate/
>/  on both channels on X300 -- but I'm not totally sure. Maybe someone/
>/  else could confirm, but since on the FPGA side, both radio units are/
>/  rather independent, you should be able to request one streamer with/
>/  rate X for your first channel, and one streamer with rate Y for your/
>/  second channel./
>/  /
>/  I did not really understand the error you mentioned; is it something/
>/  that UHD says? Where? Would you please paste the whole error?/
>/  /
>/  Best regards,/
>/  Marcus/
>/  /
>/  /
>/  On 04/22/2015 12:20 PM, Luong Tan Phong via USRP-users wrote:/
>>/  Hi list,/
>>/  /
>>/  I desire to  use X310 as a base platform for my application so I must/
>>/  add my HDL routine signal processing module after DDC module in two/
>>/  radio modules. So that, the data rate output from two radios are not/
>>/  the same, and I can't receive them on PC (because the data not align/
>>/  error)./
>>/  /
>>/  /
>>/  Could you please point out a solution ( about fpga, host, firmware)/
>>/  for me?/
>>/  /
>>/  I look forward to hearing from you./
>>/  /
>>/  With best regards,/
>>/  /
>>/  LTP/
>>/  /
>>/  /
>>/  ___/
>>/  USRP-users mailing list/
>>/  USRP-users at lists.ettus.com  
/
>>/  http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com/
>  

*From:*USRP-users  *On Behalf Of 
*Marcus D. Leech via USRP-users

*Sent:* Thursday, April 11, 2019 2:47 PM
*To:* usrp-users@lists.ettus.com
*Subject:* Re: [USRP-users] Running two N310 radios independently

On 04/11/2019 03:18 PM, Kuldeep Gill via USRP-users wrote:

Hello everyone,

I want to run two separate uhd programs accessing N310 using sfp:0
(1 gb) and sfp:1 (10 gb) independently of each other, one using
cpp and other python. Is it possible to get this kind of setup
running? If not, can I at least run two instances of
uhd::rx_streamer::recv() in different threads without one blocking
another? Please let me know if you have any suggestions.

-Kuldeep




___

USRP-users mailing list

USRP-users@lists.ettus.com  

http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Do you mean two independent N310 units, or the two radios on an N310?



___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] Running two N310 radios independently

[Kuldeep Gill via USRP-users]

Hello Marcus,
Two radios on a single N310, there was similar question on mailing list which 
is somewhat related to my issue and was asked in 2015. Please find it attached 
below.


Hi LTP,

Ben just told me that yes, Ettus has tested things, and they work as

expected: you can have arbitrary combinations of sampling rates on both

Streamers, but if you do that, you can't use a single multi_usrp object

to handle things -- you'll need to use two multi_usrp, but that's not

really a problem, since you don't lose any relevant functionality this way.



Best regards,

Marcus



On 04/22/2015 12:28 PM, Marcus Müller wrote:

> Hi LTP,

>

> have a look at what RF NoC can do; it's still beta, but maybe it

> enables you to solve your problems!

>

> Generally, you must use the same master clock rate on both

> Daughterboards, but I don't think you must use the same sampling rate

> on both channels on X300 -- but I'm not totally sure. Maybe someone

> else could confirm, but since on the FPGA side, both radio units are

> rather independent, you should be able to request one streamer with

> rate X for your first channel, and one streamer with rate Y for your

> second channel.

>

> I did not really understand the error you mentioned; is it something

> that UHD says? Where? Would you please paste the whole error?

>

> Best regards,

> Marcus

>

>

> On 04/22/2015 12:20 PM, Luong Tan Phong via USRP-users wrote:

>> Hi list,

>>

>> I desire to  use X310 as a base platform for my application so I must

>> add my HDL routine signal processing module after DDC module in two

>> radio modules. So that, the data rate output from two radios are not

>> the same, and I can't receive them on PC (because the data not align

>> error).

>>

>>

>> Could you please point out a solution ( about fpga, host, firmware)

>> for me?

>>

>> I look forward to hearing from you.

>>

>> With best regards,

>>

>> LTP

>>

>>

>> ___

>> USRP-users mailing list

>> USRP-users at 
>> lists.ettus.com

>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

>


From: USRP-users  On Behalf Of Marcus D. 
Leech via USRP-users
Sent: Thursday, April 11, 2019 2:47 PM
To: usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Running two N310 radios independently

On 04/11/2019 03:18 PM, Kuldeep Gill via USRP-users wrote:

Hello everyone,
I want to run two separate uhd programs accessing N310 using sfp:0 (1 gb) and 
sfp:1 (10 gb) independently of each other, one using cpp and other python. Is 
it possible to get this kind of setup running? If not, can I at least run two 
instances of uhd::rx_streamer::recv() in different threads without one blocking 
another? Please let me know if you have any suggestions.

-Kuldeep




___

USRP-users mailing list

USRP-users@lists.ettus.com

http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
Do you mean two independent N310 units, or the two radios on an N310?

___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] Strange result from uhd_usrp_proble for UBX-160 v2

[Serge Malo via USRP-users]

Hello Marcus,

Thanks for your answer.
Unless anybody else from Ettus has another suggestion today, I will contact
 orders@ettus.comto get a RMA number


Serge



Le jeu. 11 avr. 2019, à 13 h 12, Marcus D. Leech 
a écrit :

> On 04/11/2019 01:09 PM, Serge Malo wrote:
>
> Hello Marcus,
>
> We swapepd the d/b of our X300, and the problem followed the d/b.
> See below the results of uhd_usrp_probe.
>
> Could it "simply" be a corrupted or badly programmed eeprom?
>
> Thanks,
> Serge
>
> My inclination would be to return it under RMA.
>
>
>
>
> inux; GNU C++ version 7.3.0; Boost_106501;
> UHD_003.010.003.v3.10.3.0-0-gef157678
>
> -- X300 initialization sequence...
> -- Determining maximum frame size... 8000 bytes.
> -- Setup basic communication...
> -- Loading values from EEPROM...
> -- Setup RF frontend clocking...
> -- Radio 1x clock:200
> -- Detecting internal GPSDO No GPSDO found
> -- [DMA FIFO] Running BIST for FIFO 0... pass (Throughput: 1298.9MB/s)
> -- [DMA FIFO] Running BIST for FIFO 1... pass (Throughput: 1301.2MB/s)
> -- [RFNoC Radio] Performing register loopback test... pass
> -- [RFNoC Radio] Performing register loopback test... pass
> -- [RFNoC Radio] Performing register loopback test... pass
> -- [RFNoC Radio] Performing register loopback test... pass
> -- Performing timer loopback test... pass
> -- Performing timer loopback test... pass
>   _
>  /
> |   Device: X-Series Device
> | _
> |/
> |   |   Mboard: X300
> |   |   revision: 11
> |   |   revision_compat: 7
> |   |   product: 30817
> |   |   mac-addr0: 00:80:2f:24:a1:ee
> |   |   mac-addr1: 00:80:2f:24:a1:ef
> |   |   gateway: 192.168.10.1
> |   |   ip-addr0: 192.168.10.2
> |   |   subnet0: 255.255.255.0
> |   |   ip-addr1: 192.168.20.2
> |   |   subnet1: 255.255.255.0
> |   |   ip-addr2: 192.168.30.2
> |   |   subnet2: 255.255.255.0
> |   |   ip-addr3: 192.168.40.2
> |   |   subnet3: 255.255.255.0
> |   |   serial: 3185E4E
> |   |   FW Version: 5.1
> |   |   FPGA Version: 33.0
> |   |   RFNoC capable: Yes
> |   |
> |   |   Time sources:  internal, external, gpsdo
> |   |   Clock sources: internal, external, gpsdo
> |   |   Sensors: ref_locked
> |   | _
> |   |/
> *|   |   |   RX Dboard: A*
> *|   |   | _*
> *|   |   |/*
> *|   |   |   |   RX Frontend: 0*
> *|   |   |   |   Name: Unknown (0x) - 0*
> *|   |   |   |   Antennas: *
> *|   |   |   |   Sensors: *
> *|   |   |   |   Freq range: 0.000 to 0.000 MHz*
> *|   |   |   |   Gain Elements: None*
> *|   |   |   |   Bandwidth range: 0.0 to 0.0 step 0.0 Hz*
> *|   |   |   |   Connection Type: IQ*
> *|   |   |   |   Uses LO offset: No*
> *|   |   | _*
> *|   |   |/*
> *|   |   |   |   RX Codec: A*
> *|   |   |   |   Name: ads62p48*
> *|   |   |   |   Gain range digital: 0.0 to 6.0 step 0.5 dB*
> |   | _
> |   |/
> |   |   |   RX Dboard: B
> |   |   |   ID: UBX-160 v2 (0x007e)
> |   |   |   Serial: 31853D5
> |   |   | _
> |   |   |/
> |   |   |   |   RX Frontend: 0
> |   |   |   |   Name: UBX RX
> |   |   |   |   Antennas: TX/RX, RX2, CAL
> |   |   |   |   Sensors: lo_locked
> |   |   |   |   Freq range: 10.000 to 6000.000 MHz
> |   |   |   |   Gain range PGA0: 0.0 to 31.5 step 0.5 dB
> |   |   |   |   Bandwidth range: 16000.0 to 16000.0 step 0.0 Hz
> |   |   |   |   Connection Type: IQ
> |   |   |   |   Uses LO offset: No
> |   |   | _
> |   |   |/
> |   |   |   |   RX Codec: B
> |   |   |   |   Name: ads62p48
> |   |   |   |   Gain range digital: 0.0 to 6.0 step 0.5 dB
> |   | _
> |   |/
> *|   |   |   TX Dboard: A*
> *|   |   |   ID: UBX-160 v2 (0x007d)*
> *|   |   |   Serial: 31853CC*
> *|   |   | _*
> *|   |   |/*
> *|   |   |   |   TX Frontend: 0*
> *|   |   |   |   Name: UBX-160 v2 (0x007d) - 0*
> *|   |   |   |   Antennas: *
> *|   |   |   |   Sensors: *
> *|   |   |   |   Freq range: 0.000 to 0.000 MHz*
> *|   |   |   |   Gain Elements: None*
> *|   |   |   |   Bandwidth range: 0.0 to 0.0 step 0.0 Hz*
> *|   |   |   |   Connection Type: IQ*
> *|   |   |   |   Uses LO offset: No*
> *|   |   | _*
> *|   |   |/*
> *|   |   |   |   TX Codec: A*
> *|   |   |   |   Name: ad9146*
> *|   |   |   |   Gain Elements: None*
> |   | _
> |   |/
> |   |   |   TX Dboard: B
> |   |   |   ID: UBX-160 v2 (0x007d)
> |   |   |   Serial: 31853D5
>

Re: [USRP-users] Running two N310 radios independently

[Marcus D. Leech via USRP-users]

On 04/11/2019 03:18 PM, Kuldeep Gill via USRP-users wrote:


Hello everyone,

I want to run two separate uhd programs accessing N310 using sfp:0 (1 
gb) and sfp:1 (10 gb) independently of each other, one using cpp and 
other python. Is it possible to get this kind of setup running? If 
not, can I at least run two instances of uhd::rx_streamer::recv() in 
different threads without one blocking another? Please let me know if 
you have any suggestions.


-Kuldeep



___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Do you mean two independent N310 units, or the two radios on an N310?


___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

[USRP-users] Running two N310 radios independently

[Kuldeep Gill via USRP-users]

Hello everyone,
I want to run two separate uhd programs accessing N310 using sfp:0 (1 gb) and 
sfp:1 (10 gb) independently of each other, one using cpp and other python. Is 
it possible to get this kind of setup running? If not, can I at least run two 
instances of uhd::rx_streamer::recv() in different threads without one blocking 
another? Please let me know if you have any suggestions.

-Kuldeep
___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

[USRP-users] Device not detected

[VINAYAK KARANDIKAR via USRP-users]

Hello everyone,
  I have connected USRP NI 2954 R to my laptop
with a yellow LAN cable that came with the kit.

In matlab, I type the following command at the prompt:

dev = uhdinterface('init')

the following then takes place:

Unexpected Standard exception from MEX file.
What() is:LookupError: KeyError: No devices found for ->
Empty Device Address

What do i do?

Thanks a lot,
Vinayak Anant Karandikar
___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] RFNoC RX -> TX loopback

[Nick Foster via USRP-users]

Should still work just fine. I'm using the same approach with a UHD version
from within the last few months.

On Thu, Apr 11, 2019 at 8:00 AM Ryan Marlow via USRP-users <
usrp-users@lists.ettus.com> wrote:

> Hey Jason,
> That post seemed to be exactly what I was looking for.
> Thanks!
> Ryan
>
> On Thu, Apr 11, 2019 at 10:55 AM Jason Matusiak <
> ja...@gardettoengineering.com> wrote:
>
>> I haven't tried it yet, but have you looked at this blog post (I
>> //think// it is still relevant today)?
>> https://corvid.io/2017/04/22/stupid-rfnoc-tricks-loopback/
>>
>>
>> --
>> *From:* USRP-users  on behalf of
>> Ryan Marlow via USRP-users 
>> *Sent:* Thursday, April 11, 2019 10:51 AM
>> *To:* USRP-users@lists.ettus.com
>> *Subject:* [USRP-users] RFNoC RX -> TX loopback
>>
>> Hello all,
>> Quick question on a RX -> TX loopback application. Say I have a rfnoc
>> graph that has been connected as Radio RX -> processing block -> Radio TX
>> so there is no data samples streaming to/from the host. Can I just issue
>> the "start streaming" command to the Radio block itself or do I need to use
>> a
>> uhd::rx_streamer to issue the command? Is there any other gotcha that I
>> am overlooking?
>> Thanks,
>> Ryan
>> --
>> Ryan L. Marlow
>> R L Marlow Consulting LLC
>> rlmarlow.com
>>
>
>
> --
> Ryan L. Marlow
> R L Marlow Consulting LLC
> rlmarlow.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

Re: [USRP-users] Signal is not stable from N210 and WBX daughterboard

[Marcus D. Leech via USRP-users]

On 04/11/2019 01:29 PM, Peng Xie wrote:

Yes, it is a brand new device that I just got three weeks ago.

So where is this out band interference came from? which kind of filter 
I need to consider? And where to put this filter, e.g. between 
motherboard and daughter board, or between RF in and daughterboard?


Thanks,

Peng
I cannot tell you where RFI is coming from -- that's something you'd 
need to determine for yourself, in your own environment.


The WBX "front end" is fairly broad, and the only analog filtering 
happens at the baseband output.  What that means is that
  there's some probability of out-of-band signals being strong enough 
to drive the LNA in the WBX into non-linear operation.


You'd filter between your antenna and the RX input of the device. The 
particular attributes of the filter would depend on your
  application goals, where the interfering signals (if any) are, etc.  
That's standard RF systems engineering stuff that you'd have to

  do whether using an SDR or a strictly-analog system.






On Thu, Apr 11, 2019, 10:19 Marcus D. Leech via USRP-users 
mailto:usrp-users@lists.ettus.com>> wrote:


On 04/11/2019 10:30 AM, Peng Xie via USRP-users wrote:
> Hi,
>
> Recently I bought a N210 and WBX daughterboard, but found the
signal
> is not stable when I receive signal from 1.575GHz. I had a B200mini
> before but has data lost issue, this is why I bought a N210.
>
> I have confirmed that data does not loss in N210, just signal is
not
> stable. I set frequency to 1575MHz, and sampling rate to 2MHz,
signal
> gain to 30 dB. Every around 8 to 10 seconds, signal power dropped
> around 12 dB then I have to reacquire signal. I did not see this
> phenomenon from B200mini (B200mini has data lost or overflow issue).
>
> Anyone has some thoughts on this?
>
> Thanks,
>
> Peng
>
Was this a brand-new device?

It may be the case that some strong out-of-band signal is causing
so-called "de-sense".   You might try putting in a filter.


___
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

Re: [USRP-users] Signal is not stable from N210 and WBX daughterboard

[Peng Xie via USRP-users]

Yes, it is a brand new device that I just got three weeks ago.

So where is this out band interference came from? which kind of filter I
need to consider? And where to put this filter, e.g. between motherboard
and daughter board, or between RF in and daughterboard?

Thanks,

Peng

On Thu, Apr 11, 2019, 10:19 Marcus D. Leech via USRP-users <
usrp-users@lists.ettus.com> wrote:

> On 04/11/2019 10:30 AM, Peng Xie via USRP-users wrote:
> > Hi,
> >
> > Recently I bought a N210 and WBX daughterboard, but found the signal
> > is not stable when I receive signal from 1.575GHz. I had a B200mini
> > before but has data lost issue, this is why I bought a N210.
> >
> > I have confirmed that data does not loss in N210, just signal is not
> > stable. I set frequency to 1575MHz, and sampling rate to 2MHz, signal
> > gain to 30 dB. Every around 8 to 10 seconds, signal power dropped
> > around 12 dB then I have to reacquire signal. I did not see this
> > phenomenon from B200mini (B200mini has data lost or overflow issue).
> >
> > Anyone has some thoughts on this?
> >
> > Thanks,
> >
> > Peng
> >
> Was this a brand-new device?
>
> It may be the case that some strong out-of-band signal is causing
> so-called "de-sense".   You might try putting in a filter.
>
>
> ___
> 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

Re: [USRP-users] Signal is not stable from N210 and WBX daughterboard

[Marcus D. Leech via USRP-users]

On 04/11/2019 10:30 AM, Peng Xie via USRP-users wrote:

Hi,

Recently I bought a N210 and WBX daughterboard, but found the signal 
is not stable when I receive signal from 1.575GHz. I had a B200mini 
before but has data lost issue, this is why I bought a N210.


I have confirmed that data does not loss in N210, just signal is not 
stable. I set frequency to 1575MHz, and sampling rate to 2MHz, signal 
gain to 30 dB. Every around 8 to 10 seconds, signal power dropped 
around 12 dB then I have to reacquire signal. I did not see this 
phenomenon from B200mini (B200mini has data lost or overflow issue).


Anyone has some thoughts on this?

Thanks,

Peng


Was this a brand-new device?

It may be the case that some strong out-of-band signal is causing 
so-called "de-sense".   You might try putting in a filter.



___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] Strange result from uhd_usrp_proble for UBX-160 v2

[Marcus D. Leech via USRP-users]

On 04/11/2019 01:09 PM, Serge Malo wrote:

Hello Marcus,

We swapepd the d/b of our X300, and the problem followed the d/b.
See below the results of uhd_usrp_probe.

Could it "simply" be a corrupted or badly programmed eeprom?

Thanks,
Serge

My inclination would be to return it under RMA.





inux; GNU C++ version 7.3.0; Boost_106501; 
UHD_003.010.003.v3.10.3.0-0-gef157678


-- X300 initialization sequence...
-- Determining maximum frame size... 8000 bytes.
-- Setup basic communication...
-- Loading values from EEPROM...
-- Setup RF frontend clocking...
-- Radio 1x clock:200
-- Detecting internal GPSDO No GPSDO found
-- [DMA FIFO] Running BIST for FIFO 0... pass (Throughput: 1298.9MB/s)
-- [DMA FIFO] Running BIST for FIFO 1... pass (Throughput: 1301.2MB/s)
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- Performing timer loopback test... pass
-- Performing timer loopback test... pass
  _
 /
|   Device: X-Series Device
|  _
|/
|   |   Mboard: X300
|   |   revision: 11
|   |   revision_compat: 7
|   |   product: 30817
|   |   mac-addr0: 00:80:2f:24:a1:ee
|   |   mac-addr1: 00:80:2f:24:a1:ef
|   |   gateway: 192.168.10.1
|   |   ip-addr0: 192.168.10.2
|   |   subnet0: 255.255.255.0
|   |   ip-addr1: 192.168.20.2
|   |   subnet1: 255.255.255.0
|   |   ip-addr2: 192.168.30.2
|   |   subnet2: 255.255.255.0
|   |   ip-addr3: 192.168.40.2
|   |   subnet3: 255.255.255.0
|   |   serial: 3185E4E
|   |   FW Version: 5.1
|   |   FPGA Version: 33.0
|   |   RFNoC capable: Yes
|   |
|   |   Time sources:  internal, external, gpsdo
|   |   Clock sources: internal, external, gpsdo
|   |   Sensors: ref_locked
|   |  _
|   |/
*|   |   |   RX Dboard: A*
*|   |   |  _*
*|   |   |/*
*|   |   |   |   RX Frontend: 0*
*|   |   |   |   Name: Unknown (0x) - 0*
*|   |   |   |   Antennas: *
*|   |   |   |   Sensors: *
*|   |   |   |   Freq range: 0.000 to 0.000 MHz*
*|   |   |   |   Gain Elements: None*
*|   |   |   |   Bandwidth range: 0.0 to 0.0 step 0.0 Hz*
*|   |   |   |   Connection Type: IQ*
*|   |   |   |   Uses LO offset: No*
*|   |   |  _*
*|   |   |/*
*|   |   |   |   RX Codec: A*
*|   |   |   |   Name: ads62p48*
*|   |   |   |   Gain range digital: 0.0 to 6.0 step 0.5 dB*
|   |  _
|   |/
|   |   |   RX Dboard: B
|   |   |   ID: UBX-160 v2 (0x007e)
|   |   |   Serial: 31853D5
|   |   |  _
|   |   |/
|   |   |   |   RX Frontend: 0
|   |   |   |   Name: UBX RX
|   |   |   |   Antennas: TX/RX, RX2, CAL
|   |   |   |   Sensors: lo_locked
|   |   |   |   Freq range: 10.000 to 6000.000 MHz
|   |   |   |   Gain range PGA0: 0.0 to 31.5 step 0.5 dB
|   |   |   |   Bandwidth range: 16000.0 to 16000.0 step 0.0 Hz
|   |   |   |   Connection Type: IQ
|   |   |   |   Uses LO offset: No
|   |   |  _
|   |   |/
|   |   |   |   RX Codec: B
|   |   |   |   Name: ads62p48
|   |   |   |   Gain range digital: 0.0 to 6.0 step 0.5 dB
|   |  _
|   |/
*|   |   |   TX Dboard: A*
*|   |   |   ID: UBX-160 v2 (0x007d)*
*|   |   |   Serial: 31853CC*
*|   |   |  _*
*|   |   |/*
*|   |   |   |   TX Frontend: 0*
*|   |   |   |   Name: UBX-160 v2 (0x007d) - 0*
*|   |   |   |   Antennas: *
*|   |   |   |   Sensors: *
*|   |   |   |   Freq range: 0.000 to 0.000 MHz*
*|   |   |   |   Gain Elements: None*
*|   |   |   |   Bandwidth range: 0.0 to 0.0 step 0.0 Hz*
*|   |   |   |   Connection Type: IQ*
*|   |   |   |   Uses LO offset: No*
*|   |   |  _*
*|   |   |/*
*|   |   |   |   TX Codec: A*
*|   |   |   |   Name: ad9146*
*|   |   |   |   Gain Elements: None*
|   |  _
|   |/
|   |   |   TX Dboard: B
|   |   |   ID: UBX-160 v2 (0x007d)
|   |   |   Serial: 31853D5
|   |   |  _
|   |   |/
|   |   |   |   TX Frontend: 0
|   |   |   |   Name: UBX TX
|   |   |   |   Antennas: TX/RX, CAL
|   |   |   |   Sensors: lo_locked
|   |   |   |   Freq range: 10.000 to 6000.000 MHz
|   |   |   |   Gain range PGA0: 0.0 to 31.5 step 0.5 dB
|   |   |   |   Bandwidth range: 16000.0 to 16000.0 step 0.0 Hz
|   |   |   |   Connection Type: QI
|   |   |   |   Uses LO offset: No
|   |   |  

Re: [USRP-users] Strange result from uhd_usrp_proble for UBX-160 v2

[Serge Malo via USRP-users]

Hello Marcus,

We swapepd the d/b of our X300, and the problem followed the d/b.
See below the results of uhd_usrp_probe.

Could it "simply" be a corrupted or badly programmed eeprom?

Thanks,
Serge


inux; GNU C++ version 7.3.0; Boost_106501;
UHD_003.010.003.v3.10.3.0-0-gef157678

-- X300 initialization sequence...
-- Determining maximum frame size... 8000 bytes.
-- Setup basic communication...
-- Loading values from EEPROM...
-- Setup RF frontend clocking...
-- Radio 1x clock:200
-- Detecting internal GPSDO No GPSDO found
-- [DMA FIFO] Running BIST for FIFO 0... pass (Throughput: 1298.9MB/s)
-- [DMA FIFO] Running BIST for FIFO 1... pass (Throughput: 1301.2MB/s)
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- Performing timer loopback test... pass
-- Performing timer loopback test... pass
  _
 /
|   Device: X-Series Device
| _
|/
|   |   Mboard: X300
|   |   revision: 11
|   |   revision_compat: 7
|   |   product: 30817
|   |   mac-addr0: 00:80:2f:24:a1:ee
|   |   mac-addr1: 00:80:2f:24:a1:ef
|   |   gateway: 192.168.10.1
|   |   ip-addr0: 192.168.10.2
|   |   subnet0: 255.255.255.0
|   |   ip-addr1: 192.168.20.2
|   |   subnet1: 255.255.255.0
|   |   ip-addr2: 192.168.30.2
|   |   subnet2: 255.255.255.0
|   |   ip-addr3: 192.168.40.2
|   |   subnet3: 255.255.255.0
|   |   serial: 3185E4E
|   |   FW Version: 5.1
|   |   FPGA Version: 33.0
|   |   RFNoC capable: Yes
|   |
|   |   Time sources:  internal, external, gpsdo
|   |   Clock sources: internal, external, gpsdo
|   |   Sensors: ref_locked
|   | _
|   |/
*|   |   |   RX Dboard: A*
*|   |   | _*
*|   |   |/*
*|   |   |   |   RX Frontend: 0*
*|   |   |   |   Name: Unknown (0x) - 0*
*|   |   |   |   Antennas: *
*|   |   |   |   Sensors: *
*|   |   |   |   Freq range: 0.000 to 0.000 MHz*
*|   |   |   |   Gain Elements: None*
*|   |   |   |   Bandwidth range: 0.0 to 0.0 step 0.0 Hz*
*|   |   |   |   Connection Type: IQ*
*|   |   |   |   Uses LO offset: No*
*|   |   | _*
*|   |   |/*
*|   |   |   |   RX Codec: A*
*|   |   |   |   Name: ads62p48*
*|   |   |   |   Gain range digital: 0.0 to 6.0 step 0.5 dB*
|   | _
|   |/
|   |   |   RX Dboard: B
|   |   |   ID: UBX-160 v2 (0x007e)
|   |   |   Serial: 31853D5
|   |   | _
|   |   |/
|   |   |   |   RX Frontend: 0
|   |   |   |   Name: UBX RX
|   |   |   |   Antennas: TX/RX, RX2, CAL
|   |   |   |   Sensors: lo_locked
|   |   |   |   Freq range: 10.000 to 6000.000 MHz
|   |   |   |   Gain range PGA0: 0.0 to 31.5 step 0.5 dB
|   |   |   |   Bandwidth range: 16000.0 to 16000.0 step 0.0 Hz
|   |   |   |   Connection Type: IQ
|   |   |   |   Uses LO offset: No
|   |   | _
|   |   |/
|   |   |   |   RX Codec: B
|   |   |   |   Name: ads62p48
|   |   |   |   Gain range digital: 0.0 to 6.0 step 0.5 dB
|   | _
|   |/
*|   |   |   TX Dboard: A*
*|   |   |   ID: UBX-160 v2 (0x007d)*
*|   |   |   Serial: 31853CC*
*|   |   | _*
*|   |   |/*
*|   |   |   |   TX Frontend: 0*
*|   |   |   |   Name: UBX-160 v2 (0x007d) - 0*
*|   |   |   |   Antennas: *
*|   |   |   |   Sensors: *
*|   |   |   |   Freq range: 0.000 to 0.000 MHz*
*|   |   |   |   Gain Elements: None*
*|   |   |   |   Bandwidth range: 0.0 to 0.0 step 0.0 Hz*
*|   |   |   |   Connection Type: IQ*
*|   |   |   |   Uses LO offset: No*
*|   |   | _*
*|   |   |/*
*|   |   |   |   TX Codec: A*
*|   |   |   |   Name: ad9146*
*|   |   |   |   Gain Elements: None*
|   | _
|   |/
|   |   |   TX Dboard: B
|   |   |   ID: UBX-160 v2 (0x007d)
|   |   |   Serial: 31853D5
|   |   | _
|   |   |/
|   |   |   |   TX Frontend: 0
|   |   |   |   Name: UBX TX
|   |   |   |   Antennas: TX/RX, CAL
|   |   |   |   Sensors: lo_locked
|   |   |   |   Freq range: 10.000 to 6000.000 MHz
|   |   |   |   Gain range PGA0: 0.0 to 31.5 step 0.5 dB
|   |   |   |   Bandwidth range: 16000.0 to 16000.0 step 0.0 Hz
|   |   |   |   Connection Type: QI
|   |   |   |   Uses LO offset: No
|   |   | _
|   |   |/
|   |   |   | 

Re: [USRP-users] Strange result from uhd_usrp_proble for UBX-160 v2

[Marcus D. Leech via USRP-users]

On 04/11/2019 10:40 AM, Serge Malo via USRP-users wrote:

Hi all,

I am assembling a few X300s with UBX-160 d/b. One of them is giving me 
troubles with a UBX-160 v2 d/b. The result from uhd_usrp_probe can be 
found below.

Results from other X300s are normal.
We have physically disconnected and reconnected the problematic d/b, 
but we still have the same results.
Is there something else I can try, or should I send the board back for 
RMA?


Thanks,
Serge

If you use one of the other, known-to-work DBs in this "problematic" 
X310, does it work?


Just trying to distinguish the case where the slot in the X310 is bad, 
vs bad daughterboard.


linux; GNU C++ version 7.3.0; Boost_106501; 
UHD_003.010.003.v3.10.3.0-0-gef157678


-- X300 initialization sequence...
-- Determining maximum frame size... 8000 bytes.
-- Setup basic communication...
-- Loading values from EEPROM...
-- Setup RF frontend clocking...
-- Radio 1x clock:200
-- [DMA FIFO] Running BIST for FIFO 0... pass (Throughput: 1300.1MB/s)
-- [DMA FIFO] Running BIST for FIFO 1... pass (Throughput: 1309.8MB/s)
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- Performing timer loopback test... pass
-- Performing timer loopback test... pass
  _
 /
|   Device: X-Series Device
|  _
|/
|   |   Mboard: X300
|   |   revision: 11
|   |   revision_compat: 7
|   |   product: 30817
|   |   mac-addr0: 00:80:2f:24:a1:ee
|   |   mac-addr1: 00:80:2f:24:a1:ef
|   |   gateway: 192.168.10.1
|   |   ip-addr0: 192.168.10.2
|   |   subnet0: 255.255.255.0
|   |   ip-addr1: 192.168.20.2
|   |   subnet1: 255.255.255.0
|   |   ip-addr2: 192.168.30.2
|   |   subnet2: 255.255.255.0
|   |   ip-addr3: 192.168.40.2
|   |   subnet3: 255.255.255.0
|   |   serial: 3185E4E
|   |   FW Version: 5.1
|   |   FPGA Version: 33.0
|   |   RFNoC capable: Yes
|   |
|   |   Time sources:  internal, external, gpsdo
|   |   Clock sources: internal, external, gpsdo
|   |   Sensors: ref_locked
|   |  _
|   |/
|   |   |   RX Dboard: A
|   |   |   ID: UBX-160 v2 (0x007e)
|   |   |   Serial: 31853D5
|   |   |  _
|   |   |/
|   |   |   |   RX Frontend: 0
|   |   |   |   Name: UBX RX
|   |   |   |   Antennas: TX/RX, RX2, CAL
|   |   |   |   Sensors: lo_locked
|   |   |   |   Freq range: 10.000 to 6000.000 MHz
|   |   |   |   Gain range PGA0: 0.0 to 31.5 step 0.5 dB
|   |   |   |   Bandwidth range: 16000.0 to 16000.0 step 0.0 Hz
|   |   |   |   Connection Type: IQ
|   |   |   |   Uses LO offset: No
|   |   |  _
|   |   |/
|   |   |   |   RX Codec: A
|   |   |   |   Name: ads62p48
|   |   |   |   Gain range digital: 0.0 to 6.0 step 0.5 dB
|   |  _
|   |/
*|   |   |   RX Dboard: B*
*|   |   |  _*
*|   |   |/*
*|   |   |   |   RX Frontend: 0*
*|   |   |   |   Name: Unknown (0x) - 0*
*|   |   |   |   Antennas: *
*|   |   |   |   Sensors: *
*|   |   |   |   Freq range: 0.000 to 0.000 MHz*
*|   |   |   |   Gain Elements: None*
*|   |   |   |   Bandwidth range: 0.0 to 0.0 step 0.0 Hz*
*|   |   |   |   Connection Type: IQ*
*|   |   |   |   Uses LO offset: No*
*|   |   |  _*
*|   |   |/*
*|   |   |   |   RX Codec: B*
*|   |   |   |   Name: ads62p48*
*|   |   |   |   Gain range digital: 0.0 to 6.0 step 0.5 dB*
|   |  _
|   |/
|   |   |   TX Dboard: A
|   |   |   ID: UBX-160 v2 (0x007d)
|   |   |   Serial: 31853D5
|   |   |  _
|   |   |/
|   |   |   |   TX Frontend: 0
|   |   |   |   Name: UBX TX
|   |   |   |   Antennas: TX/RX, CAL
|   |   |   |   Sensors: lo_locked
|   |   |   |   Freq range: 10.000 to 6000.000 MHz
|   |   |   |   Gain range PGA0: 0.0 to 31.5 step 0.5 dB
|   |   |   |   Bandwidth range: 16000.0 to 16000.0 step 0.0 Hz
|   |   |   |   Connection Type: QI
|   |   |   |   Uses LO offset: No
|   |   |  _
|   |   |/
|   |   |   |   TX Codec: A
|   |   |   |   Name: ad9146
|   |   |   |   Gain Elements: None
|   |  _
|   |/
*|   |   |   TX Dboard: B*
*|   |   |   ID: UBX-160 v2 (0x007d)*
*|   |   |   Serial: 31853CC*
*|   |   |  _*
*|   |   |/*
*|   |   |   |   TX Frontend: 0*
*|   |   |   |   Name: UBX-160 v2 (0x007d) - 0*
*|   |   |   | 

Re: [USRP-users] RFNoC RX -> TX loopback

[Ryan Marlow via USRP-users]

Hey Jason,
That post seemed to be exactly what I was looking for.
Thanks!
Ryan

On Thu, Apr 11, 2019 at 10:55 AM Jason Matusiak <
ja...@gardettoengineering.com> wrote:

> I haven't tried it yet, but have you looked at this blog post (I //think//
> it is still relevant today)?
> https://corvid.io/2017/04/22/stupid-rfnoc-tricks-loopback/
>
>
> --
> *From:* USRP-users  on behalf of Ryan
> Marlow via USRP-users 
> *Sent:* Thursday, April 11, 2019 10:51 AM
> *To:* USRP-users@lists.ettus.com
> *Subject:* [USRP-users] RFNoC RX -> TX loopback
>
> Hello all,
> Quick question on a RX -> TX loopback application. Say I have a rfnoc
> graph that has been connected as Radio RX -> processing block -> Radio TX
> so there is no data samples streaming to/from the host. Can I just issue
> the "start streaming" command to the Radio block itself or do I need to use
> a
> uhd::rx_streamer to issue the command? Is there any other gotcha that I am
> overlooking?
> Thanks,
> Ryan
> --
> Ryan L. Marlow
> R L Marlow Consulting LLC
> rlmarlow.com
>


-- 
Ryan L. Marlow
R L Marlow Consulting LLC
rlmarlow.com
___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Re: [USRP-users] RFNoC RX -> TX loopback

[Jason Matusiak via USRP-users]

I haven't tried it yet, but have you looked at this blog post (I //think// it 
is still relevant today)?
https://corvid.io/2017/04/22/stupid-rfnoc-tricks-loopback/



From: USRP-users  on behalf of Ryan Marlow 
via USRP-users 
Sent: Thursday, April 11, 2019 10:51 AM
To: USRP-users@lists.ettus.com
Subject: [USRP-users] RFNoC RX -> TX loopback

Hello all,
Quick question on a RX -> TX loopback application. Say I have a rfnoc graph 
that has been connected as Radio RX -> processing block -> Radio TX so there is 
no data samples streaming to/from the host. Can I just issue the "start 
streaming" command to the Radio block itself or do I need to use a
uhd::rx_streamer to issue the command? Is there any other gotcha that I am 
overlooking?
Thanks,
Ryan
--
Ryan L. Marlow
R L Marlow Consulting LLC
rlmarlow.com
___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

[USRP-users] RFNoC RX -> TX loopback

[Ryan Marlow via USRP-users]

Hello all,
Quick question on a RX -> TX loopback application. Say I have a rfnoc graph
that has been connected as Radio RX -> processing block -> Radio TX so
there is no data samples streaming to/from the host. Can I just issue the
"start streaming" command to the Radio block itself or do I need to use a
uhd::rx_streamer to issue the command? Is there any other gotcha that I am
overlooking?
Thanks,
Ryan
-- 
Ryan L. Marlow
R L Marlow Consulting LLC
rlmarlow.com
___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

[USRP-users] Strange result from uhd_usrp_proble for UBX-160 v2

[Serge Malo via USRP-users]

Hi all,

I am assembling a few X300s with UBX-160 d/b. One of them is giving me
troubles with a UBX-160 v2 d/b. The result from uhd_usrp_probe can be found
below.
Results from other X300s are normal.
We have physically disconnected and reconnected the problematic d/b, but we
still have the same results.
Is there something else I can try, or should I send the board back for RMA?

Thanks,
Serge

linux; GNU C++ version 7.3.0; Boost_106501;
UHD_003.010.003.v3.10.3.0-0-gef157678

-- X300 initialization sequence...
-- Determining maximum frame size... 8000 bytes.
-- Setup basic communication...
-- Loading values from EEPROM...
-- Setup RF frontend clocking...
-- Radio 1x clock:200
-- [DMA FIFO] Running BIST for FIFO 0... pass (Throughput: 1300.1MB/s)
-- [DMA FIFO] Running BIST for FIFO 1... pass (Throughput: 1309.8MB/s)
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- [RFNoC Radio] Performing register loopback test... pass
-- Performing timer loopback test... pass
-- Performing timer loopback test... pass
  _
 /
|   Device: X-Series Device
| _
|/
|   |   Mboard: X300
|   |   revision: 11
|   |   revision_compat: 7
|   |   product: 30817
|   |   mac-addr0: 00:80:2f:24:a1:ee
|   |   mac-addr1: 00:80:2f:24:a1:ef
|   |   gateway: 192.168.10.1
|   |   ip-addr0: 192.168.10.2
|   |   subnet0: 255.255.255.0
|   |   ip-addr1: 192.168.20.2
|   |   subnet1: 255.255.255.0
|   |   ip-addr2: 192.168.30.2
|   |   subnet2: 255.255.255.0
|   |   ip-addr3: 192.168.40.2
|   |   subnet3: 255.255.255.0
|   |   serial: 3185E4E
|   |   FW Version: 5.1
|   |   FPGA Version: 33.0
|   |   RFNoC capable: Yes
|   |
|   |   Time sources:  internal, external, gpsdo
|   |   Clock sources: internal, external, gpsdo
|   |   Sensors: ref_locked
|   | _
|   |/
|   |   |   RX Dboard: A
|   |   |   ID: UBX-160 v2 (0x007e)
|   |   |   Serial: 31853D5
|   |   | _
|   |   |/
|   |   |   |   RX Frontend: 0
|   |   |   |   Name: UBX RX
|   |   |   |   Antennas: TX/RX, RX2, CAL
|   |   |   |   Sensors: lo_locked
|   |   |   |   Freq range: 10.000 to 6000.000 MHz
|   |   |   |   Gain range PGA0: 0.0 to 31.5 step 0.5 dB
|   |   |   |   Bandwidth range: 16000.0 to 16000.0 step 0.0 Hz
|   |   |   |   Connection Type: IQ
|   |   |   |   Uses LO offset: No
|   |   | _
|   |   |/
|   |   |   |   RX Codec: A
|   |   |   |   Name: ads62p48
|   |   |   |   Gain range digital: 0.0 to 6.0 step 0.5 dB
|   | _
|   |/
*|   |   |   RX Dboard: B*
*|   |   | _*
*|   |   |/*
*|   |   |   |   RX Frontend: 0*
*|   |   |   |   Name: Unknown (0x) - 0*
*|   |   |   |   Antennas: *
*|   |   |   |   Sensors: *
*|   |   |   |   Freq range: 0.000 to 0.000 MHz*
*|   |   |   |   Gain Elements: None*
*|   |   |   |   Bandwidth range: 0.0 to 0.0 step 0.0 Hz*
*|   |   |   |   Connection Type: IQ*
*|   |   |   |   Uses LO offset: No*
*|   |   | _*
*|   |   |/*
*|   |   |   |   RX Codec: B*
*|   |   |   |   Name: ads62p48*
*|   |   |   |   Gain range digital: 0.0 to 6.0 step 0.5 dB*
|   | _
|   |/
|   |   |   TX Dboard: A
|   |   |   ID: UBX-160 v2 (0x007d)
|   |   |   Serial: 31853D5
|   |   | _
|   |   |/
|   |   |   |   TX Frontend: 0
|   |   |   |   Name: UBX TX
|   |   |   |   Antennas: TX/RX, CAL
|   |   |   |   Sensors: lo_locked
|   |   |   |   Freq range: 10.000 to 6000.000 MHz
|   |   |   |   Gain range PGA0: 0.0 to 31.5 step 0.5 dB
|   |   |   |   Bandwidth range: 16000.0 to 16000.0 step 0.0 Hz
|   |   |   |   Connection Type: QI
|   |   |   |   Uses LO offset: No
|   |   | _
|   |   |/
|   |   |   |   TX Codec: A
|   |   |   |   Name: ad9146
|   |   |   |   Gain Elements: None
|   | _
|   |/
*|   |   |   TX Dboard: B*
*|   |   |   ID: UBX-160 v2 (0x007d)*
*|   |   |   Serial: 31853CC*
*|   |   | _*
*|   |   |/*
*|   |   |   |   TX Frontend: 0*
*|   |   |   |   Name: UBX-160 v2 (0x007d) - 0*
*|   |   |   |   Antennas: *
*|   |   |   |   Sensors: *
*|   |   |   |   Freq range: 0.000 to 0.000 MHz*
*|   |   |   |   Gain Elements: None*
*|   |   |   |   Bandwidth range: 0.0 to 0.0 step 0.0 Hz*
*|   |   |   |   Connection Type

[USRP-users] Signal is not stable from N210 and WBX daughterboard

[Peng Xie via USRP-users]

Hi,

Recently I bought a N210 and WBX daughterboard, but found the signal is not
stable when I receive signal from 1.575GHz. I had a B200mini before but has
data lost issue, this is why I bought a N210.

I have confirmed that data does not loss in N210, just signal is not
stable. I set frequency to 1575MHz, and sampling rate to 2MHz, signal gain
to 30 dB. Every around 8 to 10 seconds, signal power dropped around 12 dB
then I have to reacquire signal. I did not see this phenomenon from
B200mini (B200mini has data lost or overflow issue).

Anyone has some thoughts on this?

Thanks,

Peng
___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com