[USRP-users] Re: Fir Filter RFNoC

Just a typo, I used firS in the file, and I change the first occurrence while pasting the file, considering my use of fir0 in my explanations. There it is, with only fir0 (even if it does not change the initial issue): # General parameters # - schema: rfno

[USRP-users] Re: N321 LO sharing between RF 0/1

Hi Paul, Based on the block diagram , I think I would set both LOs to use an external source. I would set the Tx0 export the LO on Tx Output 0 and then route it directly back into Tx Input 1 which then goes to a 1:2 splitter to

[USRP-users] Re: N321 LO sharing between RF 0/1

Forgot to mention, there are some nice LEDs on the LO Tx Outputs that will tell you if you have a given port enabled. On Fri, Jan 14, 2022 at 9:25 AM Rob Kossler wrote: > Hi Paul, > Based on the block diagram > , > I think I

[USRP-users] Re: N321 LO sharing between RF 0/1

On 2022-01-14 01:11, Paul Atreides wrote: I am trying to configure the N321 to take some TX phase measurements between RF0 and RF1 I have updated the file system to the latest release using the KB guidance. My host/software side is: GNURadio 3.9.5 UHD 4.1.0.5 Ubuntu 20.04 My gr-uhd block has t

[USRP-users] Re: X310 based programs cannot run stably for a long time

Hi Jason, hm, if *I* had to make I wild guess (and it's really only that), something in the network stack reordered or dropped packets, and now the firmware running on the softcpu can't reconcile that - or just the host UHD. I bet this is hard to debug, so let's plan this a bit; I honestly d

[USRP-users] Re: N321 LO sharing between RF 0/1

Thanks Marcus, I’ve been scouring the Rubiks cube that is the knowledge base for about a week now. I’ve also watched the Dan Baker GRCON2019 talk and followed the references there as well. The reference you linked is very helpful in a lot of cases, but in this one it doesnt address (anywhere I’

[USRP-users] Re: N321 LO sharing between RF 0/1

I see what you’re saying. Are you recommending setting both to external so the paths are equal? > On Jan 14, 2022, at 09:25, Rob Kossler wrote: > >  > Hi Paul, > Based on the block diagram, I think I would set both LOs to use an external > source. I would set the Tx0 export the LO on Tx Out

[USRP-users] Re: N321 LO sharing between RF 0/1

Thanks Rob, I was actually wondering that! > On Jan 14, 2022, at 09:26, Rob Kossler wrote: > >  > Forgot to mention, there are some nice LEDs on the LO Tx Outputs that will > tell you if you have a given port enabled. > >> On Fri, Jan 14, 2022 at 9:25 AM Rob Kossler wrote: >> Hi Paul, >> B

[USRP-users] Re: N321 LO sharing between RF 0/1

On 2022-01-14 10:07, Paul Atreides wrote: Thanks Marcus, I’ve been scouring the Rubiks cube that is the knowledge base for about a week now. I’ve also watched the Dan Baker GRCON2019 talk and followed the references there as well. The reference you linked is very helpful in a lot of cases, but

[USRP-users] Re: N321 LO sharing between RF 0/1

Oh OK, I can see that possibly working for my application. Do you happen to Have any insight on what Rob was talking about, if gr-uhd Will automatically turn on the TX0 output when the export is ‘True’ Or do you know if that should instead be passed in a Device argument? I can also just test

[USRP-users] Re: N321 LO sharing between RF 0/1

On 2022-01-14 10:40, Paul Atreides wrote: Oh OK, I can see that possibly working for my application. Do you happen to Have any insight on what Rob was talking about, if gr-uhd Will automatically turn on the TX0 output when the export is ‘True’ Or do you know if that should instead be passe

[USRP-users] Enabling fast lock USRP N210.

Hello. I need to simulate a heavy RF environment. It is necessary to generate a chirp signal in a 100 MHz band with a total speed of one run of about 300 µs. But I only have USRP N210. In this regard, I have several questions. 1. Is it possible to enable fast lock using uhd 4 drivers? 2. Is it pos

[USRP-users] Re: N321 LO sharing between RF 0/1

On 2022-01-14 17:00, Paul Atreides wrote: That's what I had originally. i've Changed back to this and still getting no LED on the TX LO OUT0: RF0 LO Source internal LO export True RF1 LO Source external LO export False the generated flowgraph code looks to be reflecting  is:     self.uhd_usr

[USRP-users] Re: N321 LO sharing between RF 0/1

doing it now. is the LO frequency the carrier freq or is it 1/2 or 2x? On Fri, Jan 14, 2022 at 5:03 PM Marcus D. Leech wrote: > On 2022-01-14 17:00, Paul Atreides wrote: > > That's what I had originally. > > i've Changed back to this and still getting no LED on the TX LO OUT0: > > RF0 > > LO Sou

[USRP-users] Re: N321 LO sharing between RF 0/1

Just 1x, I believe. On Fri, Jan 14, 2022 at 5:27 PM Paul Atreides wrote: > doing it now. is the LO frequency the carrier freq or is it 1/2 or 2x? > > On Fri, Jan 14, 2022 at 5:03 PM Marcus D. Leech > wrote: > >> On 2022-01-14 17:00, Paul Atreides wrote: >> > That's what I had originally. >> > i

[USRP-users] Re: N321 LO sharing between RF 0/1

On 2022-01-14 17:30, Rob Kossler wrote: These thare the UHD commands. I don't know how these translate to gnuradio. % set both LO sources to use external set_tx_lo_source(“external”, “lo1”, 0) set_tx_lo_source(“external”, “lo1”, 1) % export the internal LO to the 1:4 splitter set_tx_lo_export_

[USRP-users] Re: N321 LO sharing between RF 0/1

Using a B210 at f_c of the N321. TX LO OUT0 is plugged into RX2 of the B210 [image: image.png] On Fri, Jan 14, 2022 at 5:32 PM Marcus D. Leech wrote: > On 2022-01-14 17:30, Rob Kossler wrote: > > These thare the UHD commands. I don't know how these translate to gnuradio. > > % set both LO sour

[USRP-users] Re: N321 LO sharing between RF 0/1

On 2022-01-14 17:35, Paul Atreides wrote: Using a B210 at f_c of the N321. TX LO OUT0 is plugged into RX2 of the  B210 You might want to put an attenuator inline, since the LO output is a couple of dBm, which is   "loud as a heavy metal concert" from the perspective of a receiver input. If the

[USRP-users] Re: N321 LO sharing between RF 0/1

so, the LO export is confirmed to be going out of TX OUT0 from the screenshot i sent before. I think i need to come back to this on monday On Fri, Jan 14, 2022 at 5:32 PM Marcus D. Leech wrote: > On 2022-01-14 17:30, Rob Kossler wrote: > > These thare the UHD commands. I don't know how thes

[USRP-users] Re: N321 LO sharing between RF 0/1

Ok thanks. In my haste I was mistaken in assuming that the LO gain would track with the RF output gain. Silly mistake. I’m still getting used to separating out the LO. I can put this on a SpectrumAnalyzer (with an attenuator in line) on Monday. I’m trying to take channel to channel phase measu

[USRP-users] Re: N321 LO sharing between RF 0/1

On 2022-01-14 18:10, Paul Atreides wrote: Ok thanks. In my haste I was mistaken in assuming that the LO gain would track with the RF output gain. Silly mistake. I’m still getting used to separating out the LO. I can put this on a SpectrumAnalyzer (with an attenuator in line) on Monday. I’m

[USRP-users] Re: N321 LO sharing between RF 0/1

Agreed on all parts. I already have the loopback cables as same type, same length. The plan is to tweak the phase offset to 0 using some high precision equipment, then see what degree of control can be obtained once the channels are phase aligned. Gonna look and see if the Python API supports t