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

On 2022-01-28 18:11, Paul Atreides wrote: yes, set to 1.0 I suspect anything that's long enough to allow the streams to all arrive at a notional "synchronization point" is enough. On Fri, Jan 28, 2022 at 5:59 PM Rob Kossler wrote: Did Marcus' suggestion below about setting the start t

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

yes, set to 1.0 On Fri, Jan 28, 2022 at 5:59 PM Rob Kossler wrote: > Did Marcus' suggestion below about setting the start time fix the issue? > > On Fri, Jan 28, 2022 at 11:31 AM Paul Atreides > wrote: > >> single >> >> On Fri, Jan 28, 2022 at 11:18 AM Marcus D. Leech >> wrote: >> >>> On 2022-

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

Did Marcus' suggestion below about setting the start time fix the issue? On Fri, Jan 28, 2022 at 11:31 AM Paul Atreides wrote: > single > > On Fri, Jan 28, 2022 at 11:18 AM Marcus D. Leech > wrote: > >> On 2022-01-28 10:38, Paul Atreides wrote: >> >> Rob, I’ve been able to extend the functional

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

single On Fri, Jan 28, 2022 at 11:18 AM Marcus D. Leech wrote: > On 2022-01-28 10:38, Paul Atreides wrote: > > Rob, I’ve been able to extend the functionality of gr-uhd to include the > enable switch for each LO distribution port. Thank you for the information. > > I am now having synchronizatio

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

On 2022-01-28 10:38, Paul Atreides wrote: Rob, I’ve been able to extend the functionality of gr-uhd to include the enable switch for each LO distribution port. Thank you for the information. I am now having synchronization issues with the transmit stream in the GNURadio. It appears as though

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

Rob, I’ve been able to extend the functionality of gr-uhd to include the enable switch for each LO distribution port. Thank you for the information. I am now having synchronization issues with the transmit stream in the GNURadio. It appears as though the radio channels are not starting at the sa

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

We’re in the same boat there for sure! Yeah, I saw there was some pretty bold things happening in there (rounding and such). I had wondered about sending a 2-D array. I will try to do more with the Python next week. Good news is, At the moment i have observed only a very small amount of insta

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

On 2022-01-21 16:52, Paul Atreides wrote: ok. is that just setting up 2 streamers to start at the same time? From looking at the code, I *THINK* that if you send it a 2D numpy array the rows represent the channels. The "send_waveform" API is Python-API only, and does a fair amount of dancing

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

On 2022-01-21 16:52, Paul Atreides wrote: ok. is that just setting up 2 streamers to start at the same time? Single sreamer, containing all your channels interleaved.   At least, that's how the C++ API works. I1Q1I2Q2    etc On Fri, Jan 21, 2022 at 4:50 PM Marcus D. Leech wrote: On

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

ok. is that just setting up 2 streamers to start at the same time? On Fri, Jan 21, 2022 at 4:50 PM Marcus D. Leech wrote: > On 2022-01-21 16:46, Paul Atreides wrote: > > is there a way to incur a phase shift on one of the streams from the > in-built UHD examples? > the python API allows has > >

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

On 2022-01-21 16:46, Paul Atreides wrote: is there a way to incur a phase shift on one of the streams from the in-built UHD examples? the python API allows has usrp.send_waveform(samples, duration, center_freq, sample_rate, [0,1],gain) but this sends the same samples to both outputs. I've us

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

is there a way to incur a phase shift on one of the streams from the in-built UHD examples? the python API allows has usrp.send_waveform(samples, duration, center_freq, sample_rate, [0,1],gain) but this sends the same samples to both outputs. I've used this icommand in conjunction with the LO sha

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

Thanks rob! > On Jan 19, 2022, at 09:41, Rob Kossler wrote: > > On Wed, Jan 19, 2022 at 1:00 AM Paul Atreides wrote: >> >> Ok, so just circling back on this. Ive got a decent handle on the Python >> API. I’ve confirmed the LO signal comes out of the port once the splitter >> output is ena

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

On Wed, Jan 19, 2022 at 1:00 AM Paul Atreides wrote: > > Ok, so just circling back on this. Ive got a decent handle on the Python API. > I’ve confirmed the LO signal comes out of the port once the splitter output > is enabled. > > Rob you’re saying that for sure both channels need to be external

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

ok, so uhd_usrp_probe --tree that's helpful. I see what you were saying. ___ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com

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

On 2022-01-18 15:19, Paul Atreides wrote: not exactly. so i'm trying to use the python API to run the equivalent of get_device()->get_tree()->access("mboards/0/dboards/A/tx_frontends/0/los/lo1/lo_distribution/LO_OUT_0/export").set(true) in python: import uhd import numpy as np usrp = uhd.usrp.Mu

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

not exactly. so i'm trying to use the python API to run the equivalent of get_device()->get_tree()->access("mboards/0/dboards/A/tx_frontends/0/los/lo1/lo_distribution/LO_OUT_0/export").set(true) in python: import uhd import numpy as np usrp = uhd.usrp.MultiUSRP() usrp.get_tree().access_bool("mboar

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

On 2022-01-18 14:49, Paul Atreides wrote: working on this now. where do i get the path mentioned above? You can use: uhd_usrp_probe to get the entire property tree of the device, if that's what you're asking. On Tue, Jan 18, 2022 at 12:02 AM Marcus D. Leech wrote: On 2022-01-17 23

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

working on this now. where do i get the path mentioned above? On Tue, Jan 18, 2022 at 12:02 AM Marcus D. Leech wrote: > On 2022-01-17 23:34, Paul Atreides wrote: > > Posting on both GNURadio and USRP lists here, since my application > > overlaps both gr-uhd/GNURadio and the UHD API. > > The top-

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

On 2022-01-17 23:34, Paul Atreides wrote: Posting on both GNURadio and USRP lists here, since my application overlaps both gr-uhd/GNURadio and the UHD API. The top-level question is, can gr-uhd support all the necessary N321-specific commands necessary to export the TX LO from RF0 to RF1? That

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

Posting on both GNURadio and USRP lists here, since my application overlaps both gr-uhd/GNURadio and the UHD API. The top-level question is, can gr-uhd support all the necessary N321-specific commands necessary to export the TX LO from RF0 to RF1? That would include running the command to set the 1

[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

[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

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

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

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

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: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

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

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

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

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] 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: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

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

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 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

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: 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

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