Andrew,
I have this issue all the time. To get around it, I go into properties of the
block (double click on it in the GRC), go to the the RFNoC Config tab, and
change the Device Select to 0 for one of them, and 1 for the other. There is
some sort of issue (I don't recall why, but it was explained to me a few years
back) with -1 not causing the code generation to be smart enough to
auto-populate the values (which is the point of it).
--------- Original Message --------- Subject: [USRP-users] Multiple instances
of RFNOC block in single flow graph
From: "Andrew Danowitz via USRP-users" <usrp-users@lists.ettus.com>
Date: 8/28/18 5:34 pm
To: "shachar J. brown via USRP-users" <usrp-users@lists.ettus.com>
Hi all,
Has anyone used multiple instances of an RFNOC block in a single flow graph? I
Built an image with my block, mAvgFilter, twice in the build args. When I try
to use both in a flow graph, though, I get:
File "/home/root/e300/src/test_code/top_block.py", line 255, in __init__
self.device3.connect(self.wf_delay_0.get_block_id(), 0,
self.wf_mAvgFilter_1.get_block_id(), 0)
File "/home/root/e300/usr/lib/python2.7/site-packages/ettus/ettus_swig.py",
line 1267, in connect
return _ettus_swig.device3_sptr_connect(self, *args)
RuntimeError: RuntimeError: On node 0/mAvgFilter_0, input port 0 is already
connected.
As you can see, the python is properly using instance _1, but somehow the C is
defaulting to instance _0.
I'm running UHD_3.13
Thanks,
Andrew
Information contained, linked, or attached to this email and all verbal
communications from WhiteFox Defense to your entity in the prior 30 days
constitute proprietary and confidential information unless otherwise indicated
and is therefore subject to obligations in any executed confidentiality
agreements. Further, this email is intended solely for the use of the
individual or entity to whom they are addressed. If you are not the intended
recipient and this message has been addressed to you in error, please promptly
notify i...@whitefoxdefense.com and destroy all copies of the message and any
attachments. This email and attachments may contain technical data as defined
in the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10 or the
Export Administration Regulations (EAR) 15 CFR Parts 730 - 780. Export of this
material may be controlled by these regulations and may not be exported or
transferred to non-U.S. persons without prior written approval from the U.S.
government.
_______________________________________________ USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
