Re: [USRP-users] two X310s in one RFNoC flowgraph

2019-02-04 Thread Jason Matusiak via USRP-users
To: Rob Kossler Cc: Ettus Mail List Subject: Re: [USRP-users] two X310s in one RFNoC flowgraph I just realized that the order of IP addresses in Device3 matters for boxes that aren't TwinRX as well. So this isn't a multi_usrp twinrx problem, but a more generic one. ___

Re: [USRP-users] two X310s in one RFNoC flowgraph

2019-02-04 Thread Jason Matusiak via USRP-users
Ettus Mail List Subject: Re: [USRP-users] two X310s in one RFNoC flowgraph One more piece of information. If in my device address list in Device3, I put my 52.2 ip before the 42.2 ip, it seems to not die like before. This again makes me think that it is grabbing things and randomly assigning wh

Re: [USRP-users] two X310s in one RFNoC flowgraph

2019-02-01 Thread Jason Matusiak via USRP-users
Kossler Sent: Friday, February 1, 2019 2:19 PM To: Jason Matusiak Cc: Ettus Mail List Subject: Re: [USRP-users] two X310s in one RFNoC flowgraph Not sure.. This may be irrelevant, but I noticed that you only have 2 FFT and 2 fosphor blocks per device, whereas the TwinRx has 4 channels since the

Re: [USRP-users] two X310s in one RFNoC flowgraph

2019-02-01 Thread Rob Kossler via USRP-users
to which IP, yet something else has already the IPs, so > it is a crap-shoot. > > -- > *From:* Jason Matusiak > *Sent:* Friday, February 1, 2019 1:53 PM > *To:* Rob Kossler > *Cc:* Ettus Mail List > *Subject:* Re: [USRP-users] two X310s in one

Re: [USRP-users] two X310s in one RFNoC flowgraph

2019-02-01 Thread Jason Matusiak via USRP-users
it is a crap-shoot. From: Jason Matusiak Sent: Friday, February 1, 2019 1:53 PM To: Rob Kossler Cc: Ettus Mail List Subject: Re: [USRP-users] two X310s in one RFNoC flowgraph I needed to make some mods to your command, but it seems to have worked. Not sure why it

Re: [USRP-users] two X310s in one RFNoC flowgraph

2019-02-01 Thread Rob Kossler via USRP-users
notes in the manual for instructions. > EnvironmentError: OSError: error in pthread_setschedparam > [00:00:06.656038] Testing receive rate 25.000000 Msps on 8 channels > [00:00:17.357375] Benchmark complete. > > > Benchmark rate summary: > Num received samples: 198981

Re: [USRP-users] two X310s in one RFNoC flowgraph

2019-02-01 Thread Jason Matusiak via USRP-users
the two devices, and then there is a race condition with which one responds first ____________ From: Rob Kossler mailto:rkoss...@nd.edu>> Sent: Friday, February 1, 2019 1:28 PM To: Jason Matusiak Cc: Ettus Mail List Subject: Re: [USRP-users] two X310s in one RFNoC flowg

Re: [USRP-users] two X310s in one RFNoC flowgraph

2019-02-01 Thread Rob Kossler via USRP-users
- > *From:* Rob Kossler > *Sent:* Friday, February 1, 2019 1:28 PM > *To:* Jason Matusiak > *Cc:* Ettus Mail List > *Subject:* Re: [USRP-users] two X310s in one RFNoC flowgraph > > If you use 2 X310 with non-TwinRx daughterboards, it can work with the > same flowgra

Re: [USRP-users] two X310s in one RFNoC flowgraph

2019-02-01 Thread Jason Matusiak via USRP-users
of issue where it assigns IP addresses to the two devices, and then there is a race condition with which one responds first From: Rob Kossler Sent: Friday, February 1, 2019 1:28 PM To: Jason Matusiak Cc: Ettus Mail List Subject: Re: [USRP-users] two X310s in one

Re: [USRP-users] two X310s in one RFNoC flowgraph

2019-02-01 Thread Rob Kossler via USRP-users
h device, it thinks that there is only one device > > > ------------------ > *From:* Rob Kossler > *Sent:* Friday, February 1, 2019 1:14 PM > *To:* Jason Matusiak > *Cc:* Ettus Mail List > *Subject:* Re: [USRP-users] two X310s in one RFNoC flowgraph > > How

Re: [USRP-users] two X310s in one RFNoC flowgraph

2019-02-01 Thread Jason Matusiak via USRP-users
t feels like it only tries to talk to the first one it sees. From: Rob Kossler mailto:rkoss...@nd.edu>> Sent: Friday, February 1, 2019 1:08 PM To: Jason Matusiak Cc: Ettus Mail List Subject: Re: [USRP-users] two X310s in one RFNoC flowgraph Perhaps run uhd_

Re: [USRP-users] two X310s in one RFNoC flowgraph

2019-02-01 Thread Rob Kossler via USRP-users
--- > *From:* Rob Kossler > *Sent:* Friday, February 1, 2019 1:08 PM > *To:* Jason Matusiak > *Cc:* Ettus Mail List > *Subject:* Re: [USRP-users] two X310s in one RFNoC flowgraph > > Perhaps run uhd_usrp_probe with > --args="addr0=192.168.30.2,addr1=192.168.40.2&quo

Re: [USRP-users] two X310s in one RFNoC flowgraph

2019-02-01 Thread Jason Matusiak via USRP-users
Mail List Subject: Re: [USRP-users] two X310s in one RFNoC flowgraph Perhaps run uhd_usrp_probe with --args="addr0=192.168.30.2,addr1=192.168.40.2" and make sure that it is happy and shows you all of the blocks. Rob On Fri, Feb 1, 2019 at 12:17 PM Jason Matusiak

Re: [USRP-users] two X310s in one RFNoC flowgraph

2019-02-01 Thread Rob Kossler via USRP-users
- > *From:* Jason Matusiak > *Sent:* Friday, February 1, 2019 9:43 AM > *To:* Rob Kossler > *Cc:* Ettus Mail List > *Subject:* Re: [USRP-users] two X310s in one RFNoC flowgraph > > > Rob, > > > I just figured it out (I found lots of people asking the ques

Re: [USRP-users] two X310s in one RFNoC flowgraph

2019-02-01 Thread Jason Matusiak via USRP-users
hings. From: Jason Matusiak Sent: Friday, February 1, 2019 9:43 AM To: Rob Kossler Cc: Ettus Mail List Subject: Re: [USRP-users] two X310s in one RFNoC flowgraph Rob, I just figured it out (I found lots of people asking the question, but no answers, so hopefully thi

Re: [USRP-users] two X310s in one RFNoC flowgraph

2019-02-01 Thread Jason Matusiak via USRP-users
w, Device 0 will get associated with addr0, and device 1 will get associates with addr1. I hope that makes sense and helps someone. From: Rob Kossler Sent: Friday, February 1, 2019 9:23 AM To: Jason Matusiak Cc: Ettus Mail List Subject: Re: [USRP-users] tw

Re: [USRP-users] two X310s in one RFNoC flowgraph

2019-02-01 Thread Rob Kossler via USRP-users
Hi Jason, Given that under the hood, the stock multi_usrp (along with legacy_compat) implements an RFNoC graph, it must be possible. I have run multiple X310s with the stock multi_usrp. I have looked at legacy_compat pretty thoroughly and it keeps track of blocks as a function of device number (m