Thanks, Marcus for the info link. I’ve reviewed that information and
understand how RF0 is A:0 and RF1 is B:0 for the N320. I’ve reviewed the
utility benchmark_rate.py to see how the arguments are used to change the
channel. I guess what I’m missing is how GRC initializes the USRP. The python
code generated from GRC is pretty different from benchmark_rate.py. I don’t
know where to put the “subdev=B:0” command within the GRC flowgraph. I was
trying to do it in the “Device Args” of “RFNoC Graph (Device)” block. I also
tried to do it in the “RFNoC RX Radio”. But not having any luck.
I think that most people with complicated configurations don’t use GRC and so I
didn’t know if GRC simply did not support the capability to send subdev
commands to UHD.
Anyway, I appreciate the help,
Mike
From: Marcus D. Leech <patchvonbr...@gmail.com>
Sent: Wednesday, January 25, 2023 10:29 PM
To: usrp-users@lists.ettus.com
Subject: [USRP-users] Re: Did anyone else need to do this?
On 25/01/2023 22:25, Mike via USRP-users wrote:
All,
This is an update from a previous thread. I also found another error in the
yaml file, ettus_rfnoc_graph.block.yml. I’m running GNU Radio 3.8 and UHD 4.2.
The file is located in:
“gr-ettus/grc/ettus_rfnoc_graph.block.yml”. I found this because the commands
in the “Device Args” parameter were not being processed correctly.
The line is associated with the following “if” statement (line 19):
If dev_args_s:
graph_args += f”,{clock_source_s}”
The “clock_source_s” should be “dev_args_s”.
I found this because I’m trying to send specific initialization commands to my
N320. As a side note, can anyone explain how to configure “subdev” from a GRC
flow graph so that I can enable the RF1 side of the N320?
https://kb.ettus.com/USRP_N300/N310/N320/N321_Getting_Started_Guide#Subdevice_Specification_Mapping
Thanks,
Mike
From: Mike <mailto:mike...@verizon.net> <mike...@verizon.net>
Sent: Friday, December 16, 2022 10:54 AM
To: 'Jim Palladino' <mailto:j...@gardettoengineering.com>
<j...@gardettoengineering.com>; 'usrp-users@lists.ettus.com
<mailto:usrp-users@lists.ettus.com> ' <mailto:usrp-users@lists.ettus.com>
<usrp-users@lists.ettus.com>
Subject: RE: [USRP-users] Re: Did anyone else need to do this?
Jim,
Thanks for taking care of this. I’ll just fix it on my end and wait for the
eventual updates in the repository.
Thanks,
Mike
From: Jim Palladino <j...@gardettoengineering.com
<mailto:j...@gardettoengineering.com> >
Sent: Friday, December 16, 2022 10:04 AM
To: usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com> ; Mike
<mike...@verizon.net <mailto:mike...@verizon.net> >
Subject: Re: [USRP-users] Re: Did anyone else need to do this?
Mike,
My last comment was related to gr-ettus (ettus_rfnoc_graph.block.yml), which I
installed with gnuradio 3.8 / uhd 4.1. But I do see that gnuradio 3.10 has the
exact same issue (as you found) in uhd_rfnoc_graph.block.yml:
https://github.com/gnuradio/gnuradio/blob/maint-3.10/gr-uhd/grc/uhd_rfnoc_graph.block.yml
<https://github.com/gnuradio/gnuradio/blob/maint-3.10/gr-uhd/grc/uhd_rfnoc_graph.block.yml>
<https://github.com/gnuradio/gnuradio/blob/maint-3.10/gr-uhd/grc/uhd_rfnoc_graph.block.yml>
gnuradio/uhd_rfnoc_graph.block.yml at maint-3.10 · gnuradio/gnuradio
GNU Radio – the Free and Open Software Radio Ecosystem -
gnuradio/uhd_rfnoc_graph.block.yml at maint-3.10 · gnuradio/gnuradio
github.com
So, it looks like we've run into the same issue in different implementations. I
can post and issue on the gnuradio github page as well.
Jim
_____
From: Jim Palladino <j...@gardettoengineering.com
<mailto:j...@gardettoengineering.com> >
Sent: Friday, December 16, 2022 9:38 AM
To: usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com>
<usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com> >; Mike
<mike...@verizon.net <mailto:mike...@verizon.net> >
Subject: [USRP-users] Re: Did anyone else need to do this?
Hi Mike,
Yes, I've run into that. I posted an issue last week here:
https://github.com/EttusResearch/gr-ettus/issues/69
<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_EttusResearch_gr-2Dettus_issues_69&d=DwMF-g&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=XUEEtUEfpaAEGxRI-WGuqHauOvsPdD2NZkfwDnwpYx0&m=8R8d8AptGNR6pvwu09qYQOqR4yaqR90_EK56v2z-xLM&s=xyYFrqtOxluB0Ad4jIxBJj7J_5ArRlIAu8Sx0l3QxaM&e=>
<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_EttusResearch_gr-2Dettus_issues_69&d=DwMF-g&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=XUEEtUEfpaAEGxRI-WGuqHauOvsPdD2NZkfwDnwpYx0&m=8R8d8AptGNR6pvwu09qYQOqR4yaqR90_EK56v2z-xLM&s=xyYFrqtOxluB0Ad4jIxBJj7J_5ArRlIAu8Sx0l3QxaM&e=>
<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_EttusResearch_gr-2Dettus_issues_69&d=DwMF-g&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=XUEEtUEfpaAEGxRI-WGuqHauOvsPdD2NZkfwDnwpYx0&m=8R8d8AptGNR6pvwu09qYQOqR4yaqR90_EK56v2z-xLM&s=xyYFrqtOxluB0Ad4jIxBJj7J_5ArRlIAu8Sx0l3QxaM&e=>
syntax error in ettus_rfnoc_graph.block.yml · Issue #69 ·
EttusResearch/gr-ettus
Line 25 of ettus_rfnoc_graph.block.yml in the maint-3.8-uhd4.0 branch (and
possibly others) looks like: self.rfnoc_graph = ${id} =
ettus.rfnoc_graph(uhd.device_addr("${graph_args}"))) You...
github.com
I ended up just modifying the yml file in source and then reinstalling gr-ettus.
Jim
_____
From: Mike via USRP-users <usrp-users@lists.ettus.com
<mailto:usrp-users@lists.ettus.com> >
Sent: Friday, December 16, 2022 9:33 AM
To: usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com>
<usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com> >
Subject: [USRP-users] Did anyone else need to do this?
Hi all,
This goes in the category of “Did anyone else need to do this?”.
I’m running Ubuntu 20.04.5 LTS with GNURadio 3.8 (Maint) and UHD 4.0. I
recently upgraded UHD to 4.2. I ran into a gnuradio issue starting a “RFNoC”
flow graph with a syntax error for an unmatched ‘)’:
Self.rfnoc_graph=ettus_rfnoc_graph_0 =
ettus.rfnoc_graph(uhd.device_addr(“addr=xxx,type-n3xx”)))
I was able to manually edit the generated python code to remove one of the
parentheses and see the code work.
I then upgraded gnuradio to 3.10 which had the same issue.
I then compared the “uhd_rfnoc_graph.block.yml” block files between UHD4.0 and
4.2. It’s significantly different as 4.0 uses python .join to build the
argument list and UHD 4.2 uses the python module “ast” to generate the argument
list. But the final line on the 4.2 version had the syntax error of the extra
‘)’:
self.rfnoc_graph = ${id} =
uhd.rfnoc_graph(uhd.device_addr(“${graph_args}”)))
I removed one ‘)’ then reinstalled gnuradio (make install) from the build
directory and everything seemed to work after that.
So, it seems like it is a simple syntax error. But normally something like
this (in my experience) indicates that I might have missed some configuration
step somewhere and have yet to see the other errors.
So, has anyone seen something like this?
Thanks,
Mike
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
<mailto:usrp-users@lists.ettus.com>
To unsubscribe send an email to usrp-users-le...@lists.ettus.com
<mailto:usrp-users-le...@lists.ettus.com>
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com
