Re: [USRP-users] Getting different rate Rx streams working on a B210

On 04/02/2018 08:05 PM, Martin Braun via USRP-users wrote: On 03/16/2018 11:49 AM, Reinhold Frederick William Hollender via USRP-users wrote: I just wanted to share my experience getting two Rx streams at different rates working with the B210 in case someone else tries to do the same thing in

Re: [USRP-users] Getting different rate Rx streams working on a B210

On 03/16/2018 11:49 AM, Reinhold Frederick William Hollender via USRP-users wrote: > I just wanted to share my experience getting two Rx streams at different > rates working with the B210 in case someone else tries to do the same > thing in the future. > > The only other resource I found on this

Re: [USRP-users] Problem of Octoclock

On 03/09/2018 10:30 AM, 賴明煊 via USRP-users wrote: > Hi > > Here is the situation of my Octoclock-G. > When I connect the power cable to it, four LEDs of "INTERNAL", > "EXTERNAL", "STATUS" and "POWER" lit for about 5 seconds and then only > "POWER" remains on , others become off. It seems there is

Re: [USRP-users] Synchronization between two USRPs and processing latency between USRP and host PC

On 03/07/2018 06:51 PM, Inkyu Bang via USRP-users wrote: > Hi, I am inkyu. > I am interested in synchronizing two USRP (each of them connected to a > different laptop) using pre-defined signals. > > Let's we have USRP A and B. > We want to send the signal from USRP A and B which should arrive the

Re: [USRP-users] The daughterboard manager encountered a recoverable error in init.-USRP2

On 03/09/2018 04:07 AM, Anouar Chahbouni via USRP-users wrote: > Hello, > > > I am using the USRP2/N-Series and trying to receive a simply signal with > Gnuradio. > I have this error but I don't know how to resolve it. Which daughterboard are you connecting to your USRP? -- M

Re: [USRP-users] x310 ZPU firmware

On 02/19/2018 04:11 AM, Ana Svirčić via USRP-users wrote: > The file udp_uart.cdoes exist in the mentioned directory. Don't know how > to proceed.  Can anybody help with this issue? Ana, did you get anywhere with this? Do you have access to a Linux system maybe that you could use for building

Re: [USRP-users] FPGA and Firmware Development Platform

On 03/08/2018 12:51 PM, Zhongyuan Zhao via USRP-users wrote: > Hi Derek, > > After some homework, I found that RFNoC might be quite good for my > development.  > > Could you introduce a little bit more about the time stamping in RFNoC?  > My project need to handle many well-aligned streams, do

Re: [USRP-users] RFNoC Support for TwinRX

On 03/22/2018 12:07 PM, Derek Kozel via USRP-users wrote: > Hello Adams, > > Yes, the TwinRX Rev A and B work with RFNoC, but the rfnoc-devel branch > may currently have some regressions. We are in the process of updating > the rfnoc-devel branch with many changes from the master branch >

Re: [USRP-users] RFNoC Radio TX/RX vs USRP Sink/Source

On 03/15/2018 08:15 PM, Dang tien Vo-Huu via USRP-users wrote: > Hi all, > Recently I have some doubt about the difference between USRP Sink/Source > and the RFNoC Radio TX/RX. I found the answer in the knowledge > base https://kb.ettus.com/RFNoC but when I tried the RFNoC TX and RX > flow

Re: [USRP-users] UHD possible bugs

Lucas, I've confirmed there's some issues with the B200/AD9361 code. I've added a ticket on our internal issue tracker; I have no timeline for a resolution though. -- M On 03/19/2018 04:47 AM, Lucas Val Terrón via USRP-users wrote: > Hi all, > > Related to old questions I have previously asked 

Re: [USRP-users] Streaming 8-bit (sc8) samples from RFNoC

On 03/19/2018 07:23 PM, Dan CaJacob via USRP-users wrote: > I seem to recall that the 8-bit OTW format isn't implemented for RFNoC > yet... I could use that too. We currently support u8 and sc8 modes for OTW. If your block can do 8-bit samples, UHD will know how to handle that. We also have s8

Re: [USRP-users] Accessing the device tree through the UHD C API

Hi Janos, I assume that by 'device tree' you mean the property tree, and not the actual device tree (e.g., on embedded N310). 1. You're correct that there's no functions in the C API to query the property tree. That said, the vast majority of properties are queried by via API calls that do

Re: [USRP-users] E320 support in UHD_4.0.0.rfnoc-devel

On 03/19/2018 08:48 AM, Marcus D. Leech via USRP-users wrote: > On 03/19/2018 05:30 AM, Mark Luscombe via USRP-users wrote: >> Hi, >> >> The USRP E320 was announced in September 2017, does anybody know when >> it will be supported for RFNoC development. >> >> Cheers, Mark. >> >> >> > The E320

Re: [USRP-users] Waveform Files

On 03/23/2018 03:36 PM, Patterson, Seth S via USRP-users wrote: > Does anyone have examples of how to generate waveform IQ files in matlab > or python for use in tx_samples_from_file? I’m using an x300. The GNU Radio FAQ does:

Re: [USRP-users] X300 new user

On 03/23/2018 10:41 AM, Marcus D. Leech via USRP-users wrote: > On 03/23/2018 01:30 PM, Rob Kossler wrote: >> I had the same issue today.  but, I had done a "make install" >> previously.  I fixed by setting the environment variable UHD_RFNOC_DIR >> to point to the correct install folder, in my

Re: [USRP-users] UHD version for RFNoC

We've updated rfnoc-devel to track master, and thus, use Vivado 2017.4. -- M On 03/27/2018 12:00 AM, Derek Kozel via USRP-users wrote: > Hello Juan, > > Right now RFNoC development requires Vivado 2015.4 and the rfnoc-devel > branch. We are in the process of updating the rfnoc-devel branch to >

Re: [USRP-users] customize processing of U and L messages

If you're on 3.11.* or later, then you can use -DUHD_LOG_FASTPATH_DISABLE to disable the printing of UOSDL. If you want to know about U, S and L events, then use recv_async_msg() as you're already doing. If you want to know about O and D events, then check the rx_metadata from recv(). Cheers,

Re: [USRP-users] N310 and get_usrp_rx_info()

On 03/29/2018 09:12 AM, Rob Kossler via USRP-users wrote: > There seems to be a bug with the multi_usrp function get_usrp_rx_info() > (and also for tx_info) when used with the N310 as indicated below. > > If I include the line... >    uhd::dict rx_info =

Re: [USRP-users] X310 PCIe Error enumerating NI-RIO devices

On 04/02/2018 11:24 AM, Антон Заболотский via USRP-users wrote: > I am trying to connect, but I can do it only via Moxa converter > (https://www.moxa.com/product/IMC-101.htm) and host doesn't see X310. > I think it is because : The USRP-X Series only supports Gigabit and Ten > Gigabit Ethernet and

[USRP-users] UHD 3.11.0.1 Release Announcement

Hello all, UHD 3.11.0.1 is now available. This is an update to the main series of releases. The tag for this release is located here: https://github.com/EttusResearch/uhd/releases/tag/v3.11.0.1 Installers for Windows and Fedora are available here:

Re: [USRP-users] X310 PCIe Error enumerating NI-RIO devices

I am trying to connect, but I can do it only via Moxa converter (https://www.moxa.com/product/IMC-101.htm) and host doesn't see X310. I think it is because : The USRP-X Series only supports Gigabit and Ten Gigabit Ethernet and will not work with a 10/100 Mbps interface. Am I right? I was able

Re: [USRP-users] B210 lock problem to external 10 MHz

On 04/02/2018 01:04 PM, Sailor Jerry wrote: Great thanks Marcus, will try cleanup the input. Would is still work with 2 Vpp AC coupled input? The spec says max +15dBm, which in a 50ohm system is 3.5V P-P. I suspect the main issue is that your waveforms are quite nasty, and likely contain

Re: [USRP-users] B210 lock problem to external 10 MHz

Great thanks Marcus, will try cleanup the input. Would is still work with 2 Vpp AC coupled input? On Mon, Apr 2, 2018 at 9:33 AM Marcus D. Leech via USRP-users < usrp-users@lists.ettus.com> wrote: > On 04/02/2018 12:17 PM, Sailor Jerry via USRP-users wrote: > > I'm using the external 10 MHz

Re: [USRP-users] B210 lock problem to external 10 MHz

On 04/02/2018 12:17 PM, Sailor Jerry via USRP-users wrote: I'm using the external 10 MHz input to my B210 and getting the following lock status messages: Waiting for "lo_locked": locked. Waiting for "ref_locked": _++++___++ Here is the waveform of my 10 MHz

[USRP-users] B210 lock problem to external 10 MHz

I'm using the external 10 MHz input to my B210 and getting the following lock status messages: Waiting for "lo_locked": locked. Waiting for "ref_locked": _++++___++ Here is the waveform of my 10 MHz clock ( I tried both AC coupled (yellow) and DC coupled (blue) )

Re: [USRP-users] X310 PCIe Error enumerating NI-RIO devices

On 04/02/2018 03:18 AM, Антон Заболотский via USRP-users wrote: Hi everyone, I have USRP 2955 and it works under Labview 2017 Windows 7. Now I need to convert it to X310. I can use only PCIe. But unfortunately I have the following errors: I used default image burned by National Instruments