Thanks rob! <end transmission>
> On Jan 19, 2022, at 09:41, Rob Kossler <rkoss...@nd.edu> wrote: > > On Wed, Jan 19, 2022 at 1:00 AM Paul Atreides <maud.dib1...@gmail.com> 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 AND >> exported? making the settings: >> TX 0: >> LO source = external >> LO Exported = true >> TX 1: >> LO source = external >> LO Exported = true > Yes, except as you pointed out below, LO Exported for Tx1 is not > needed and likely does nothing. > >> >> Radio #0 TX LO OUT 0 = enabled >> Radio #1 TX LO OUT 1 = enabled (for debug) >> (When I set These they turn on the lights for the LO outs) >> >> The front panel cable should connect TX LO output 0 to TX LO Input 1 > Yes > >> >> Like you said, According to the block diagram, the TX LO input 1 should >> connect both channels to the 1x2 splitter so I should only need 1 LO output >> turned on. Id like to point out that in the block diagram it also doesn’t >> look like it’s possible to export channel 1’s LO. The only connection in the >> diagram is internal. > > Yes, Somewhere in the Ettus documentation, it indicates that this is > the case (I've forgotten where). > >> >> Am I missing something? Have you gotten this to work? > Yes, I have been using this in a 16x16 system with 8 N321 devices all > connected by a single LO (arbitrarily chosen LO export channel > distributed to both Tx and Rx LO inputs). I've also tested it on > smaller systems as small as 4x4 (and possibly 2x2 like your case, but > not positive on this). _______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
