Thank you for the reply! After reading through the RFNoC spec I think the feature we’re talking about is what I would casually call “transport selection” Transport blocks (Ethernet, aurora, SFP) have their own callouts in the low-level source code, but don’t have exposure at the GNURadio-block level. If you run say benchmark_rx with the —“channels=0,1” flag, on my machine that DOES produce streams on both SFP’s.
It would be very helpful if someone from Ettus Research could write up a quick list of the following args in their current valid syntax: -stream arguments -block arguments -graph/device arguments A brief description and whether or not they can be accessed in GNURadio via RFNoC blocks/Python API/C++ API would also help. I’ve been digging through the source code and it’s been difficult to find the valid arguments and their syntax. For example, for device address is it ip-addr0, addr0 or addr? Thanks <end transmission> > On May 18, 2021, at 02:34, Paolo Palana <[email protected]> wrote: > > Hi, > > I never used UHD4, but at least in UHD3.15 and previous versions, for the > best of my knowledge, there is now way to explicitly assign a given stream to > a given sfp+ (and let me say this is a sin). As far as I can understand the > assignment is, in some way static, the first channel is streamed on sfp+0, > the second on sfp+1, the third again on sfp+0 and so on. > > Hope this can be helpful > > >> On 5/14/21 8:33 AM, Paul Atreides wrote: >> >> Hi there: >> Im trying to wrap my head around using RFNoC/UHD4 and the X310. Ive gotten >> basic flowgraphs working and I’m building custom images in Vivado. Right now >> I’m working on the default XG image. >> I would like to send the received samples from one UBX160 to 2 different >> physical outputs on the x310. The streams will be decimated to different >> rates (i.e. stream0=high-rate/stream1=low-rate). Is there a way in >> GNURadio/rfnoc to route rx stream0 to SFP+ Port 0 and rx stream1 to SFP+ >> Port 1? I can’t seem to find any relevant documents on assigning radio ID, >> address or ports. Can you help? >> >> Thanks! >> >> <end transmission> >> _______________________________________________ >> USRP-users mailing list -- [email protected] >> To unsubscribe send an email to [email protected] > _______________________________________________ > USRP-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ USRP-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
