Hi Annie, first of all:
> When replying, please edit your Subject line so it is more specific > than "Re: Contents of Discuss-gnuradio digest..." So I did that for you :) It's easier for you if you just directly subscribe to the full mailing list and not just the Digests. Mail clients can automatically sort mailing list emails, so you don't have to worry about the mailing list cluttering your inbox. > Are benchmark_tx and benchmark_rx both deprecated ? yes, both are deprecated. > And is there any example flowgraph which uses the ofdm_transmitter > which I can use to send the data. For examples, you might want to look into /usr[/local]/share/gnuradio/examples/digital/ofdm (or wherever your GNU Radio examples were installed to) and look at tx_ofdm.grc and rx_ofdm.grc Best regards, Marcus On 12/12/2016 07:14 PM, Qurat-Ul-Ann Akbar wrote: > Hi Martin, > > Thanks for your response. Are benchmark_tx and benchmark_rx both > deprecated ? And is there any example flowgraph which uses the > ofdm_transmitter which I can use to send the data. I have a CS > background and I do not know much about the signal processing at PHY > layer in great detail. > > Best, > Annie > > On Mon, Dec 12, 2016 at 11:00 AM, <[email protected] > <mailto:[email protected]>> wrote: > > Send Discuss-gnuradio mailing list submissions to > [email protected] <mailto:[email protected]> > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> > or, via email, send a message with subject or body 'help' to > [email protected] > <mailto:[email protected]> > > You can reach the person managing the list at > [email protected] > <mailto:[email protected]> > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Discuss-gnuradio digest..." > > > Today's Topics: > > 1. Re: [USRP-users] Deadline extended: FOSDEM 2017: SDR Track > CfP (Martin Braun) > 2. Re: Difference between examples/ofdm/benchmark_tx.py and > examples/ofdm/tx_ofdm.py (Martin Braun) > 3. RFNoC blocks in GRC (Vishwesh Rege) > 4. reading uhd_rx_cfile data (Nikita Airee) > 5. Re: RFNoC blocks in GRC (Nicolas Cuervo) > 6. Re: RFNoC blocks in GRC (Vishwesh Rege) > 7. Re: RFNoC blocks in GRC (Nicolas Cuervo) > 8. Re: RFNoC blocks in GRC (Vishwesh Rege) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 11 Dec 2016 11:29:37 -0800 > From: Martin Braun <[email protected] <mailto:[email protected]>> > To: "[email protected] <mailto:[email protected]>" > <[email protected] <mailto:[email protected]>>, > "'[email protected] > <mailto:[email protected]>'" <[email protected] > <mailto:[email protected]>>, > [email protected] <mailto:[email protected]> > Subject: Re: [Discuss-gnuradio] [USRP-users] Deadline extended: FOSDEM > 2017: SDR Track CfP > Message-ID: <[email protected] > <mailto:[email protected]>> > Content-Type: text/plain; charset=windows-1252 > > Apologies for the double-post, but I completely forgot to give the new > dates: We have extended the CfP by one week, until December 16th. > However, we are alrady rating prior submissions, so early > submitters get > a preference. There are still some slots available though! > > Cheers, > Martin > > > On 12/10/2016 11:25 AM, Martin Braun via USRP-users wrote: > > Dear friends and fans of software defined radio, > > > > the SDR track at next year's FOSDEM still has some slots left! We > > already have a good mix of topics, but we still have some time > for YOUR > > presentation! > > > > If you have anything related to field of free software radio, please > > head to: > > > > https://penta.fosdem.org/submission/FOSDEM17 > <https://penta.fosdem.org/submission/FOSDEM17> > > > > and submit your short abstract! We're looking very much forward > to your > > submission. > > > > For the committee, > > > > Martin Braun > > > > On 10/18/2016 03:27 PM, Martin Braun wrote: > >> Dear friends and fans of software defined radio, > >> > >> next year's FOSDEM (the free and open source developer's meeting in > >> Brussels, Europe) will, once again, feature a track on > Software Defined > >> Radio. > >> Therefore, we invite developers and users from the free > software radio > >> community to join us for this track and present your talks or > demos. > >> > >> Software Radio has become an important tool to allow anyone > access the > >> EM spectrum. Using free software radio libraries and > applications and > >> cheap hardware, anyone can now start hacking on wireless > >> communications, remote sensing, radar or other applications. At > FOSDEM, > >> we hope to network all these projects and improve > collaboration, bring > >> new ideas forward and get more people involved. > >> > >> The track's web site resides at: > >> http://gnuradio.org/redmine/projects/gnuradio/wiki/FOSDEM > <http://gnuradio.org/redmine/projects/gnuradio/wiki/FOSDEM> > >> > >> Here, we will publish updates and announcements. The final > schedule will > >> be available through Pentabarf and the official FOSDEM website. > >> > >> ** Submit your presentations > >> > >> To suggest a talk, go to > https://penta.fosdem.org/submission/FOSDEM16 > <https://penta.fosdem.org/submission/FOSDEM16> > >> and follow the instructions (you need an account, but can use your > >> account from last year if you have one). You need to create an > 'Event'; > >> make sure it's in the Software Defined Radio track! Lengths aren't > >> fixed, but give a realistic estimate and please don't exceed 30 > minutes > >> unless you have something special planned (in that case, > contact one of > >> us). Also, don't forget to include time for Q&A. > >> > >> You aren't limited to slide presentations, of course. Be creative. > >> However, FOSDEM is an open source conference, therefore we ask > you to > >> stay clear of marketing presentations. Of course, we like > nitty-gritty > >> technical stuff. > >> > >> Here's a list of topics that will most likely be included: > >> - SDR Frameworks + Tools > >> - Wireless security > >> - Radio hardware > >> - Telecommunications > >> - Random fun wireless hacks > >> > >> We will reserve time for interactiveness, it won't all be talks. > >> > >> ** Important Dates > >> > >> FOSDEM is February 4th and 5th, 2017. > >> > >> * December 9th 2016: Submission Deadline > >> * January 2nd 2017: Announcement of final schedule > >> * February 4th 2017: SDR Track (Saturday) > >> > >> These dates are not set in stone. However, the least years we were > >> always full to the brim with presentations, so if you want to > present, > >> please make sure to submit your abstracts soon! > >> > >> ** Steering Committee > >> > >> The track committee consists of: > >> * Phil "catvideos" Balister (OpenEmbedded / OpenSDR) > >> * Martin "mbr0wn" Braun (GNU Radio) > >> * Sylvain "tnt" Munaut (OsmoCom) > >> > >> Hope to hear from you soon! And please forward this announcement. > >> > >> Martin > >> > > > > > > _______________________________________________ > > USRP-users mailing list > > [email protected] <mailto:[email protected]> > > > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > <http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com> > > > > > > > ------------------------------ > > Message: 2 > Date: Sun, 11 Dec 2016 11:31:07 -0800 > From: Martin Braun <[email protected] > <mailto:[email protected]>> > To: [email protected] <mailto:[email protected]> > Subject: Re: [Discuss-gnuradio] Difference between > examples/ofdm/benchmark_tx.py and examples/ofdm/tx_ofdm.py > Message-ID: <[email protected] > <mailto:[email protected]>> > Content-Type: text/plain; charset=windows-1252 > > You can basically ignore benchmark_tx.py, it's deprecated, will be > removed soon and uses old APIs. > > However, in an nutshell, benchmark_tx.py is a transmitter application, > whereas tx_ofdm.grc is a GRC flowgraph that demonstrates the internals > of the OFDM transmitter. > > Cheers, > Martin > > On 12/09/2016 11:37 AM, Qurat-Ul-Ann Akbar wrote: > > Hi, > > > > I am new to GNU Radio and I want to use OFDM to send signals at > > frequency of around 2.4 GHz using USRP N210 with daughter board > RFX2400. > > I do not really understand the difference between > benchmark_tx.py and > > tx_ofdm.py. I know that benchmark runs with the USRP as well > because it > > has an option to transmit through USRP and tx_ofdm doesn't have a > > uhd_block. But if I add the uhd_block as a sink in tx_ofdm.grc > what is > > the difference then between the two files ? And which one should > I use ? > > > > Thank you, > > Annie > > > > > > _______________________________________________ > > Discuss-gnuradio mailing list > > [email protected] <mailto:[email protected]> > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> > > > > > > > ------------------------------ > > Message: 3 > Date: Sun, 11 Dec 2016 23:16:39 -0800 > From: Vishwesh Rege <[email protected] <mailto:[email protected]>> > To: [email protected] <mailto:[email protected]> > Subject: [Discuss-gnuradio] RFNoC blocks in GRC > Message-ID: > > <calq8fdjjffmym-eseernvoelkylozclrs0p53hqciw3cbah...@mail.gmail.com > > <mailto:calq8fdjjffmym-eseernvoelkylozclrs0p53hqciw3cbah...@mail.gmail.com>> > Content-Type: text/plain; charset="utf-8" > > Hi, > > I'm unable to view RFNoC blocks in gnuradio-companion (in the > block list on > the right side). Sometimes I can view them, under (unspecified) ? > uhd ? > rfnoc but sometimes I can't for some reason. I have sourced > rfnoc/setup_env.sh which I believe had solved the problem > previously. Does > anyone know the solution? > > Any suggestions appreciated. Thanks. > > Vishwesh > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20161211/643f4fa7/attachment.html > > <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20161211/643f4fa7/attachment.html>> > > ------------------------------ > > Message: 4 > Date: Mon, 12 Dec 2016 14:44:47 +0530 > From: Nikita Airee <[email protected] > <mailto:[email protected]>> > To: [email protected] <mailto:[email protected]> > Subject: [Discuss-gnuradio] reading uhd_rx_cfile data > Message-ID: > > <CAOT=STnUaf=9ytuhenjytoxga+b-tydr28-vroywtm99nsa...@mail.gmail.com > <mailto:9ytuhenjytoxga%[email protected]>> > Content-Type: text/plain; charset="utf-8" > > Hello everyone! > > I am tryning to capure the IQ samples over the air to determine > the noise > floor at the given frequency. > > However, I have not been able to read the files uhd_rx_cfile > creates. Is > there a special utility/program in gnuradio or otherwise that I > could use > to read this data and separate the I and Q samples? > > Bests, > Nikita > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20161212/c3670772/attachment.html > > <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20161212/c3670772/attachment.html>> > > ------------------------------ > > Message: 5 > Date: Mon, 12 Dec 2016 10:26:54 +0100 > From: Nicolas Cuervo <[email protected] > <mailto:[email protected]>> > To: Vishwesh Rege <[email protected] <mailto:[email protected]>> > Cc: GNURadio Discussion List <[email protected] > <mailto:[email protected]>> > Subject: Re: [Discuss-gnuradio] RFNoC blocks in GRC > Message-ID: > > <caoupcvh+7i3qvxdr5mx78+46rmb4ctuz92kzr90kbfo1sxu...@mail.gmail.com > > <mailto:caoupcvh%2b7i3qvxdr5mx78%[email protected]>> > Content-Type: text/plain; charset="utf-8" > > Hello Vishwesh, > > I believe that in this case it is only a matter of where the > blocks are > installed, and where grc is looking for them. When you install OOT > modules > (gr-ettus is itself an OOT module for RFNoC) it also has an > installation > path, where GRC is going to be looking for the blocks that are > available, > and the ones that are found are going to be listed there. I > believe, from > what you wrote in your email, that you are using PyBOMBS, and the > PyBOMBS > environment is really helpful in cases lake this one. Before > setting up the > environment it would be expected that the blocks are not found, as the > enviromental variables that describe their location haven't been > set. By > sourcing the env, all the things that where installed with PyBOMBS are > described with the environmental variables, and the the RFNoC > blocks can be > found. > > That is, you have to source your setup_env.sh every time that you > want to > use something from that given prefix. The reason why this is not done > automatically (which is also the reason why it is not recommended > to do > so), is because you can set up multiple prefixes, each with a > completely > different configuration, which you can pull just by sourcing the > setup_env.sh file. > > I hope this answers your question. Please let us know if further > clarification is required. > > Cheers, > -N > > On Mon, Dec 12, 2016 at 8:16 AM, Vishwesh Rege > <[email protected] <mailto:[email protected]>> wrote: > > > Hi, > > > > I'm unable to view RFNoC blocks in gnuradio-companion (in the > block list > > on the right side). Sometimes I can view them, under > (unspecified) ? uhd ? > > rfnoc but sometimes I can't for some reason. I have sourced > > rfnoc/setup_env.sh which I believe had solved the problem > previously. Does > > anyone know the solution? > > > > Any suggestions appreciated. Thanks. > > > > Vishwesh > > > > > > _______________________________________________ > > Discuss-gnuradio mailing list > > [email protected] <mailto:[email protected]> > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20161212/93630152/attachment.html > > <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20161212/93630152/attachment.html>> > > ------------------------------ > > Message: 6 > Date: Mon, 12 Dec 2016 01:44:31 -0800 > From: Vishwesh Rege <[email protected] <mailto:[email protected]>> > To: Nicolas Cuervo <[email protected] > <mailto:[email protected]>> > Cc: GNURadio Discussion List <[email protected] > <mailto:[email protected]>> > Subject: Re: [Discuss-gnuradio] RFNoC blocks in GRC > Message-ID: > > <CALq8fDK1zWEyJ5an958bicL7ypQ1bO=sttpic4dokprhjhv...@mail.gmail.com > <mailto:[email protected]>> > Content-Type: text/plain; charset="utf-8" > > Hi, > > I understand but sourcing the setup_env.sh file isn't working for me > unfortunately at this time. Previously on a different machine this > was what > seemed to have solved the issue. > I did use PyBOMBS for installation, this is the exact sequence of > commands: > sudo pip install PyBOMBS > pybombs recipes add gr-recipes git+https://github.com/ > gnuradio/gr-recipes.git > pybombs recipes add ettus git+https://github.com/ > EttusResearch/ettus-pybombs.git > pybombs prefix init ~/rfnoc -R rfnoc > source ~/rfnoc/setup_env.sh > > and gnuradio using apt-get install... > > Thanks, > Vishwesh > > > > On Mon, Dec 12, 2016 at 1:26 AM, Nicolas Cuervo > <[email protected] <mailto:[email protected]>> > wrote: > > > Hello Vishwesh, > > > > I believe that in this case it is only a matter of where the > blocks are > > installed, and where grc is looking for them. When you install > OOT modules > > (gr-ettus is itself an OOT module for RFNoC) it also has an > installation > > path, where GRC is going to be looking for the blocks that are > available, > > and the ones that are found are going to be listed there. I > believe, from > > what you wrote in your email, that you are using PyBOMBS, and > the PyBOMBS > > environment is really helpful in cases lake this one. Before > setting up the > > environment it would be expected that the blocks are not found, > as the > > enviromental variables that describe their location haven't been > set. By > > sourcing the env, all the things that where installed with > PyBOMBS are > > described with the environmental variables, and the the RFNoC > blocks can be > > found. > > > > That is, you have to source your setup_env.sh every time that > you want to > > use something from that given prefix. The reason why this is not > done > > automatically (which is also the reason why it is not > recommended to do > > so), is because you can set up multiple prefixes, each with a > completely > > different configuration, which you can pull just by sourcing the > > setup_env.sh file. > > > > I hope this answers your question. Please let us know if further > > clarification is required. > > > > Cheers, > > -N > > > > On Mon, Dec 12, 2016 at 8:16 AM, Vishwesh Rege > <[email protected] <mailto:[email protected]>> > > wrote: > > > >> Hi, > >> > >> I'm unable to view RFNoC blocks in gnuradio-companion (in the > block list > >> on the right side). Sometimes I can view them, under > (unspecified) ? uhd ? > >> rfnoc but sometimes I can't for some reason. I have sourced > >> rfnoc/setup_env.sh which I believe had solved the problem > previously. Does > >> anyone know the solution? > >> > >> Any suggestions appreciated. Thanks. > >> > >> Vishwesh > >> > >> > >> _______________________________________________ > >> Discuss-gnuradio mailing list > >> [email protected] <mailto:[email protected]> > >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> > >> > >> > > > > > -- > Vishwesh Rege > +1 (858) 729-4157 > <tel:%2B1%20%28858%29%20729-4157> <(858)%20729-4157> | > [email protected] <mailto:[email protected]> | > https://sites.google.com/site/vishweshrege > <https://sites.google.com/site/vishweshrege> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20161212/50e4b8c0/attachment.html > > <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20161212/50e4b8c0/attachment.html>> > > ------------------------------ > > Message: 7 > Date: Mon, 12 Dec 2016 11:04:12 +0100 > From: Nicolas Cuervo <[email protected] > <mailto:[email protected]>> > To: Vishwesh Rege <[email protected] <mailto:[email protected]>> > Cc: GNURadio Discussion List <[email protected] > <mailto:[email protected]>> > Subject: Re: [Discuss-gnuradio] RFNoC blocks in GRC > Message-ID: > > <CAOuPCvgF1huD+30-Xh5=OyV15t=qfvsgmso7-xaxocqz_od...@mail.gmail.com > <mailto:[email protected]>> > Content-Type: text/plain; charset="utf-8" > > Hello Vishwesh, > > that recipe installs gnuradio in your path too. I believe that if > you run > grc from from that prefix, your blocks will be picked up. The > gnuradio from > the prefix has the env_var GRC_BLOCKS_DIR setup so that it is included > within the PyBOMBS prefix. > > On the other hand, when you open the GRC that you installed via > apt-get, at > the top of your output, I would suspect that you get something like: > > Block paths: > /usr/local/share/gnuradio/grc/blocks > > (or something alike), which is a system location and the stuff > that you > install and configure via PyBOMBS are not supposed to be installed > there, > but only in the prefix. If that is so, you'd have to reconfigure > your grc > to look for the path where your blocks are, or reconfigure your block > installation path to install at the location where gnuradio is > looking for > them. Or use the grc that you installed with that recipe, which > should just > work. > > Is there a reason why you separately installed gnuradio from the > package > manager? As I said, you could use all the resources from the rfnoc.lwr > recipe that you are using (which are UHD, GNURadio, gr-ettus and > the fpga > repo) > > Cheers, > - N > > On Mon, Dec 12, 2016 at 10:44 AM, Vishwesh Rege > <[email protected] <mailto:[email protected]>> wrote: > > > Hi, > > > > I understand but sourcing the setup_env.sh file isn't working for me > > unfortunately at this time. Previously on a different machine > this was what > > seemed to have solved the issue. > > I did use PyBOMBS for installation, this is the exact sequence of > > commands: > > sudo pip install PyBOMBS > > pybombs recipes add gr-recipes git+https://github.com/gnuradi > > o/gr-recipes.git > > pybombs recipes add ettus git+https://github.com/EttusRe > > search/ettus-pybombs.git > > pybombs prefix init ~/rfnoc -R rfnoc > > source ~/rfnoc/setup_env.sh > > > > and gnuradio using apt-get install... > > > > Thanks, > > Vishwesh > > > > > > > > On Mon, Dec 12, 2016 at 1:26 AM, Nicolas Cuervo > <[email protected] <mailto:[email protected]>> > > wrote: > > > >> Hello Vishwesh, > >> > >> I believe that in this case it is only a matter of where the > blocks are > >> installed, and where grc is looking for them. When you install > OOT modules > >> (gr-ettus is itself an OOT module for RFNoC) it also has an > installation > >> path, where GRC is going to be looking for the blocks that are > available, > >> and the ones that are found are going to be listed there. I > believe, from > >> what you wrote in your email, that you are using PyBOMBS, and > the PyBOMBS > >> environment is really helpful in cases lake this one. Before > setting up the > >> environment it would be expected that the blocks are not found, > as the > >> enviromental variables that describe their location haven't > been set. By > >> sourcing the env, all the things that where installed with > PyBOMBS are > >> described with the environmental variables, and the the RFNoC > blocks can be > >> found. > >> > >> That is, you have to source your setup_env.sh every time that > you want to > >> use something from that given prefix. The reason why this is > not done > >> automatically (which is also the reason why it is not > recommended to do > >> so), is because you can set up multiple prefixes, each with a > completely > >> different configuration, which you can pull just by sourcing the > >> setup_env.sh file. > >> > >> I hope this answers your question. Please let us know if further > >> clarification is required. > >> > >> Cheers, > >> -N > >> > >> On Mon, Dec 12, 2016 at 8:16 AM, Vishwesh Rege > <[email protected] <mailto:[email protected]>> > >> wrote: > >> > >>> Hi, > >>> > >>> I'm unable to view RFNoC blocks in gnuradio-companion (in the > block list > >>> on the right side). Sometimes I can view them, under > (unspecified) ? uhd ? > >>> rfnoc but sometimes I can't for some reason. I have sourced > >>> rfnoc/setup_env.sh which I believe had solved the problem > previously. Does > >>> anyone know the solution? > >>> > >>> Any suggestions appreciated. Thanks. > >>> > >>> Vishwesh > >>> > >>> > >>> _______________________________________________ > >>> Discuss-gnuradio mailing list > >>> [email protected] <mailto:[email protected]> > >>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> > >>> > >>> > >> > > > > > > -- > > Vishwesh Rege > > +1 (858) 729-4157 <tel:%2B1%20%28858%29%20729-4157> > <(858)%20729-4157> | [email protected] <mailto:[email protected]> | > > https://sites.google.com/site/vishweshrege > <https://sites.google.com/site/vishweshrege> > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20161212/c3d43786/attachment.html > > <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20161212/c3d43786/attachment.html>> > > ------------------------------ > > Message: 8 > Date: Mon, 12 Dec 2016 02:42:42 -0800 > From: Vishwesh Rege <[email protected] <mailto:[email protected]>> > To: Nicolas Cuervo <[email protected] > <mailto:[email protected]>> > Cc: GNURadio Discussion List <[email protected] > <mailto:[email protected]>> > Subject: Re: [Discuss-gnuradio] RFNoC blocks in GRC > Message-ID: > > <CALq8fD+cW8OzvCO8WEieLKVadsxZNW8DSA6fpvSw0L-P=wd...@mail.gmail.com > <mailto:[email protected]>> > Content-Type: text/plain; charset="utf-8" > > Hi, > > Sorry but I don't know what you mean by "reconfigure your grc to > look for > the path where your blocks are, or reconfigure your block > installation path > to install at the location where gnuradio is looking for them. Or > use the > grc that you installed with that recipe"... as in the steps to do > that? > > I installed gnuradio separately because gnuradio-companion wasn't > running > (command not found error) when I tried to execute it from the > command line. > > Thanks, > Vishwesh > > > > On Mon, Dec 12, 2016 at 2:04 AM, Nicolas Cuervo > <[email protected] <mailto:[email protected]>> > wrote: > > > Hello Vishwesh, > > > > that recipe installs gnuradio in your path too. I believe that > if you run > > grc from from that prefix, your blocks will be picked up. The > gnuradio from > > the prefix has the env_var GRC_BLOCKS_DIR setup so that it is > included > > within the PyBOMBS prefix. > > > > On the other hand, when you open the GRC that you installed via > apt-get, > > at the top of your output, I would suspect that you get > something like: > > > > Block paths: > > /usr/local/share/gnuradio/grc/blocks > > > > (or something alike), which is a system location and the stuff > that you > > install and configure via PyBOMBS are not supposed to be > installed there, > > but only in the prefix. If that is so, you'd have to reconfigure > your grc > > to look for the path where your blocks are, or reconfigure your > block > > installation path to install at the location where gnuradio is > looking for > > them. Or use the grc that you installed with that recipe, which > should just > > work. > > > > Is there a reason why you separately installed gnuradio from the > package > > manager? As I said, you could use all the resources from the > rfnoc.lwr > > recipe that you are using (which are UHD, GNURadio, gr-ettus and > the fpga > > repo) > > > > Cheers, > > - N > > > > On Mon, Dec 12, 2016 at 10:44 AM, Vishwesh Rege > <[email protected] <mailto:[email protected]>> > > wrote: > > > >> Hi, > >> > >> I understand but sourcing the setup_env.sh file isn't working > for me > >> unfortunately at this time. Previously on a different machine > this was what > >> seemed to have solved the issue. > >> I did use PyBOMBS for installation, this is the exact sequence of > >> commands: > >> sudo pip install PyBOMBS > >> pybombs recipes add gr-recipes git+https://github.com/gnuradi > >> o/gr-recipes.git > >> pybombs recipes add ettus git+https://github.com/EttusRe > >> search/ettus-pybombs.git > >> pybombs prefix init ~/rfnoc -R rfnoc > >> source ~/rfnoc/setup_env.sh > >> > >> and gnuradio using apt-get install... > >> > >> Thanks, > >> Vishwesh > >> > >> > >> > >> On Mon, Dec 12, 2016 at 1:26 AM, Nicolas Cuervo > <[email protected] <mailto:[email protected]> > >> > wrote: > >> > >>> Hello Vishwesh, > >>> > >>> I believe that in this case it is only a matter of where the > blocks are > >>> installed, and where grc is looking for them. When you install > OOT modules > >>> (gr-ettus is itself an OOT module for RFNoC) it also has an > installation > >>> path, where GRC is going to be looking for the blocks that are > available, > >>> and the ones that are found are going to be listed there. I > believe, from > >>> what you wrote in your email, that you are using PyBOMBS, and > the PyBOMBS > >>> environment is really helpful in cases lake this one. Before > setting up the > >>> environment it would be expected that the blocks are not > found, as the > >>> enviromental variables that describe their location haven't > been set. By > >>> sourcing the env, all the things that where installed with > PyBOMBS are > >>> described with the environmental variables, and the the RFNoC > blocks can be > >>> found. > >>> > >>> That is, you have to source your setup_env.sh every time that > you want > >>> to use something from that given prefix. The reason why this > is not done > >>> automatically (which is also the reason why it is not > recommended to do > >>> so), is because you can set up multiple prefixes, each with a > completely > >>> different configuration, which you can pull just by sourcing the > >>> setup_env.sh file. > >>> > >>> I hope this answers your question. Please let us know if further > >>> clarification is required. > >>> > >>> Cheers, > >>> -N > >>> > >>> On Mon, Dec 12, 2016 at 8:16 AM, Vishwesh Rege > <[email protected] <mailto:[email protected]>> > >>> wrote: > >>> > >>>> Hi, > >>>> > >>>> I'm unable to view RFNoC blocks in gnuradio-companion (in the > block > >>>> list on the right side). Sometimes I can view them, under > (unspecified) ? > >>>> uhd ? rfnoc but sometimes I can't for some reason. I have sourced > >>>> rfnoc/setup_env.sh which I believe had solved the problem > previously. Does > >>>> anyone know the solution? > >>>> > >>>> Any suggestions appreciated. Thanks. > >>>> > >>>> Vishwesh > >>>> > >>>> > >>>> _______________________________________________ > >>>> Discuss-gnuradio mailing list > >>>> [email protected] <mailto:[email protected]> > >>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> > >>>> > >>>> > >>> > >> > >> > >> -- > >> Vishwesh Rege > >> +1 (858) 729-4157 <tel:%2B1%20%28858%29%20729-4157> > <(858)%20729-4157> | [email protected] <mailto:[email protected]> | > >> https://sites.google.com/site/vishweshrege > <https://sites.google.com/site/vishweshrege> > >> > > > > > > > -- > Vishwesh Rege > +1 (858) 729-4157 <tel:%2B1%20%28858%29%20729-4157> | > [email protected] <mailto:[email protected]> | > https://sites.google.com/site/vishweshrege > <https://sites.google.com/site/vishweshrege> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20161212/ced45a0b/attachment.html > > <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20161212/ced45a0b/attachment.html>> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Discuss-gnuradio mailing list > [email protected] <mailto:[email protected]> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> > > > ------------------------------ > > End of Discuss-gnuradio Digest, Vol 169, Issue 13 > ************************************************* > > > > > _______________________________________________ > Discuss-gnuradio mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
