Re: [Discuss-gnuradio] gnuradio-companion-3.8.0 fails to run

On 30/10/2019 00:09, Barry Jackson wrote: On 27/10/2019 11:58, Marcus Müller wrote: ah! I missed the part where you said you're not used to Python. In Python, indentation is structure-defining, and  the error message sadly doesn't really give context, but it looks like the most probable

Re: [Discuss-gnuradio] gnuradio-companion-3.8.0 fails to run

On 27/10/2019 11:58, Marcus Müller wrote: ah! I missed the part where you said you're not used to Python. In Python, indentation is structure-defining, and the error message sadly doesn't really give context, but it looks like the most probable explanation is that the line you've inserted is

Re: [Discuss-gnuradio] gnuradio-companion-3.8.0 fails to run

ah! I missed the part where you said you're not used to Python. In Python, indentation is structure-defining, and the error message sadly doesn't really give context, but it looks like the most probable explanation is that the line you've inserted is not correctly indented. Make sure you're

Re: [Discuss-gnuradio] gnuradio-companion-3.8.0 fails to run

On 24/10/2019 21:18, Håkon Vågsether wrote: This error message also occurs in one of the GRC tests: https://github.com/gnuradio/gnuradio/issues/2678 Best regards Håkon Vågsether Strange that there has been no response to your bug report since July. Any other suggestions as to how to work

Re: [Discuss-gnuradio] gnuradio-companion-3.8.0 fails to run

Update: Since last night I have re-created the patch and re-built and this time the package built with: self._docstring_extractor.finish() # self._docstring_extractor.wait() try: utils.hide_bokeh_gui_options_if_not_installed(self.blocks['options'])

Re: [Discuss-gnuradio] gnuradio-companion-3.8.0 fails to run

On 24/10/2019 20:36, Müller, Marcus (CEL) wrote: Hi Barry, neat, haven't seen that one before, specifically :) But I've seen a test fail: https://github.com/gnuradio/gnuradio/issues/2678 Mageia is RPM-based, right? Never used it before, but could you point me to the .SPEC file you're using to

Re: [Discuss-gnuradio] gnuradio-companion-3.8.0 fails to run

This error message also occurs in one of the GRC tests: https://github.com/gnuradio/gnuradio/issues/2678 Best regards Håkon Vågsether tor. 24. okt. 2019, 12:41 skrev Müller, Marcus (CEL) : > Hi Barry, > > neat, haven't seen that one before, specifically :) > But I've seen a test fail: >

Re: [Discuss-gnuradio] gnuradio-companion-3.8.0 fails to run

Hi Barry, neat, haven't seen that one before, specifically :) But I've seen a test fail: https://github.com/gnuradio/gnuradio/issues/2678 Mageia is RPM-based, right? Never used it before, but could you point me to the .SPEC file you're using to build that package? Hunch: replace

Re: [Discuss-gnuradio] gnuradio-companion : File Descriptor Source module usage

On Tue, 23 Jul 2019, Kevin Reid wrote: On Tue, Jul 23, 2019 at 8:33 PM Tom Crane wrote: Can anyone explain how to use the File Descriptor Source module in gnuradio-companion? I am trying to write a flow-graph to read data from an arbitrary file, chosen via the GUI at

Re: [Discuss-gnuradio] gnuradio-companion : File Descriptor Source module usage

On Tue, Jul 23, 2019 at 8:33 PM Tom Crane wrote: > Can anyone explain how to use the File Descriptor Source module in > gnuradio-companion? > > I am trying to write a flow-graph to read data from an arbitrary file, > chosen via the GUI at run time? This must be possible, right? I can't > see

Re: [Discuss-gnuradio] GNUradio companion error message

Hi John_w_g - The error you're encountering indicates that the version of UHD isn't compatible with the version of gr-uhd -- which is part of the overall GNU Radio install. I'd guess that GNU Radio was installed, and then UHD was updated. Generally the solution is to reinstall GNU Radio while

Re: [Discuss-gnuradio] GNURadio-Companion: Selected drop down option stays "red"

Hi engineerpcp, I'm not aware of any problems with that block. The most likely explanation is that you have conflicting installations of GRC block files. Please make sure that GRC doesn't try to load GRC blocks from a path you have older versions of GNU Radio installed in. GRC prints the block

Re: [Discuss-gnuradio] GNURadio Companion LPF

s affect my results? Sorry I am still trying to learn all these. > > > > Thank you in advanced! > > > > *From:* Marcus D. Leech [mailto:mle...@ripnet.com] > *Sent:* Tuesday, 22 May 2018 11:32 AM > > *To:* Yeo Jin Kuang Alvin (IA); discuss-gnuradio@gnu.or

Re: [Discuss-gnuradio] GNURadio Companion LPF

...@ripnet.com] Sent: Tuesday, 22 May 2018 11:32 AM To: Yeo Jin Kuang Alvin (IA); discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] GNURadio Companion LPF On 05/21/2018 11:28 PM, Yeo Jin Kuang Alvin (IA) wrote: Hi all, Thank you! I've noticed my mistake. Now I've tried both 5000 and 100e3, instead

Re: [Discuss-gnuradio] GNURadio Companion LPF

IA); discuss-gnuradio@gnu.org<mailto:discuss-gnuradio@gnu.org> Subject: Re: [Discuss-gnuradio] GNURadio Companion LPF On 05/21/2018 11:14 PM, Yeo Jin Kuang Alvin (IA) wrote: Hi Marcus, Thank you for the quick reply! Is there any block in GRC that works with the FPGA in the USRP B210? And I

Re: [Discuss-gnuradio] GNURadio Companion LPF

s-gnuradio [mailto:discuss-gnuradio-bounces+yjinkuan=dso.org...@gnu.org] *On Behalf Of *Marcus D. Leech *Sent:* Tuesday, 22 May 2018 11:02 AM *To:* discuss-gnuradio@gnu.org <mailto:discuss-gnuradio@gnu.org> *Subject:* Re: [Discuss-gnuradio] GNURadio Companion LPF On 05/21/2018 10:54 PM, Yeo Jin

Re: [Discuss-gnuradio] GNURadio Companion LPF

Alvin (IA); discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] GNURadio Companion LPF On 05/21/2018 11:14 PM, Yeo Jin Kuang Alvin (IA) wrote: Hi Marcus, Thank you for the quick reply! Is there any block in GRC that works with the FPGA in the USRP B210? And I have tried lowering the transi

Re: [Discuss-gnuradio] GNURadio Companion LPF

at the only solution to it is to get a faster > computer? > > Thank you in advanced! > > From: Discuss-gnuradio > [mailto:discuss-gnuradio-bounces+yjinkuan=dso.org...@gnu.org] On Behalf Of > Marcus D. Leech > Sent: Tuesday, 22 May 2018 11:02 AM > To: discuss-gnuradio@g

Re: [Discuss-gnuradio] GNURadio Companion LPF

an=dso.org...@gnu.org] *On Behalf Of *Marcus D. Leech *Sent:* Tuesday, 22 May 2018 11:02 AM *To:* discuss-gnuradio@gnu.org *Subject:* Re: [Discuss-gnuradio] GNURadio Companion LPF On 05/21/2018 10:54 PM, Yeo Jin Kuang Alvin (IA) wrote: Hi all, Apparently, I tried connecting the U

Re: [Discuss-gnuradio] GNURadio Companion LPF

in advanced! From: Discuss-gnuradio [mailto:discuss-gnuradio-bounces+yjinkuan=dso.org...@gnu.org] On Behalf Of Marcus D. Leech Sent: Tuesday, 22 May 2018 11:02 AM To: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] GNURadio Companion LPF On 05/21/2018 10:54 PM, Yeo Jin Kuang Alvin (IA) wrote

Re: [Discuss-gnuradio] GNURadio Companion LPF

On 05/21/2018 10:54 PM, Yeo Jin Kuang Alvin (IA) wrote: Hi all, Apparently, I tried connecting the USRP Source to a Low Pass Filter and to a File Sink, I get overflows “OO”. However, when I removed the LPF, there is no overflow. The question is, why is this happening? Is the Low Pass

Re: [Discuss-gnuradio] gnuradio-companion -c is documented but not working

Hello Markus, yep, that's a documentation bug. I'll look up how the manpages are generated. Possibly, GRC *used* to have this feature (or it *will* have that feature). What you want to achieve can be achieved with a different command line utility: grcc [-d target_directory,

Re: [Discuss-gnuradio] gnuradio-companion swig error?

Hi xlf, On 26.02.2017 20:38, x...@gmx.com wrote: > did i do something wrong that my post was never authorized? i've been > watching it for days not knowing what else to do . . . I can't see anything. Anyway, just don't use nabble but sign up directly with your GMX address to the list – it's

Re: [Discuss-gnuradio] gnuradio-companion swig error?

I don't know why your post didn't go through. The gr-osmosdr port contents look correct. Your script works for me on my OS X box (admittedly, 10.12 latest). Let's take the discussion on-list, and I'll help you debug this & if there's something relevant I'll reply back to the GR list. -

Re: [Discuss-gnuradio] gnuradio-companion swig error?

did i do something wrong that my post was never authorized? i've been watching it for days not knowing what else to do . . . that's what i did regarding SoapySDR. i must be reading something wrong, because doing "port contents gr-osmosdr | grep_osmosdr_swig returns "command not found" "port

Re: [Discuss-gnuradio] gnuradio-companion swig error?

According to nabble, your original post has yet to be authorized. I'll append it for completion. So you're running on an older OS X box (10.8), using the libc++ hack for older systems. That should be OK. Most folks I know who use it do it with 10.6 or 10.7, but it should work on 10.8 too. If you

Re: [Discuss-gnuradio] gnuradio-companion swig error?

anyone?? -- View this message in context: http://gnuradio.4.n7.nabble.com/gnuradio-companion-swig-error-tp62829p62964.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org

Re: [Discuss-gnuradio] gnuradio-companion binary not getting installed

I think you need a python-devel package installed. Exact name will be distro dependent. Philip On 11/29/2016 09:34 AM, Jason Matusiak wrote: > This was really good information Seth, thanks. I tried the steps > Nicolas previously mentioned and I had the same problem. I ran your > commands and I

Re: [Discuss-gnuradio] gnuradio-companion binary not getting installed

This was really good information Seth, thanks. I tried the steps Nicolas previously mentioned and I had the same problem. I ran your commands and I see gnuradio-companion under the "disabled components" list. Looking further up in the output, the thing I see different from your list is that

Re: [Discuss-gnuradio] gnuradio-companion binary not getting installed

Something may have disabled gnuradio-companion in cmake. Can you run: *"cd ~/gnuradio/src/gnuradio/build; cmake .."*? Towards the end of the output you should see: -- ## -- # Gnuradio enabled components --

Re: [Discuss-gnuradio] gnuradio-companion binary not getting installed

Hello Jason, I just ran the same line that you ran and I see gnuradio-companio in prefix/bin/ and I can also run it after setting up the environment. Could you please update the recipes and see if this solves this: pybombs recipes update Also, you can also update pybombs to see if it also

Re: [Discuss-gnuradio] gnuradio companion Options block ID

Hey Wayne, You are right, a check would be good. The same issue can occur for variable blocks. Thanks, Sebastian Sent from BlueMail On Jun 14, 2016, 15:28, at 15:28, Wayne Roberts wrote: >It would seem that the ID entered into options block of gnuradio >companion

Re: [Discuss-gnuradio] gnuradio Companion and Ettus E310, passing parameters

On Thu, Jan 7, 2016 at 11:25 AM, Mike Gilmer wrote: > I'm running gnuradio companion on Fedora. I can make the Ettus device UDP > to gnuradio Companion and display RF. Great. > > Now, if possible, I'd like to be able to use the Companion GUI to pass, in > real-time,

Re: [Discuss-gnuradio] gnuradio Companion and Ettus E310, passing parameters

I'm going to publish a test image with control port for the e310 next week. I'm upstreaming the changes to OE now and and should be possible to build GNU Radio with control easily "soon". Philip On 01/07/2016 03:30 PM, Tom Rondeau wrote: > On Thu, Jan 7, 2016 at 11:25 AM, Mike Gilmer

Re: [Discuss-gnuradio] Gnuradio-companion

> To: Sumit Saluja; discuss-gnuradio@gnu.org > Subject: Re: [Discuss-gnuradio] Gnuradio-companion > > On Wed, 2015-11-18 at 19:54 -0500, Marcus D. Leech wrote: >> On 11/18/2015 07:16 PM, Sumit Saluja wrote: >>> Hi Marcus, >>> >>> I am trying to instal

Re: [Discuss-gnuradio] Gnuradio-companion

If I am building gnuradio manually Iam getting following message ## -- # Gnuradio disabled components -- ## -- * gr-ctrlport -- * gnuradio-companion -- * gr-comedi -- * gr-uhd -- *

Re: [Discuss-gnuradio] Gnuradio-companion

On 11/18/2015 03:45 PM, Sumit Saluja wrote: If I am building gnuradio manually Iam getting following message ## -- # Gnuradio disabled components -- ## -- * gr-ctrlport -- *

Re: [Discuss-gnuradio] Gnuradio-companion

gt; > > > > > From: discuss-gnuradio-bounces+ssaluja=princeton@gnu.org [mailt > > o:discuss-gnuradio-bounces+ssaluja=princeton@gnu.org] On Behalf > > Of Marcus Müller > > Sent: Wednesday, November 18, 2015 6:09 PM > > To: discuss-gnuradio@gnu.

Re: [Discuss-gnuradio] Gnuradio-companion

saluja=princeton@gnu.org] *On Behalf Of *Marcus Müller *Sent:* Wednesday, November 18, 2015 6:09 PM *To:* discuss-gnuradio@gnu.org <mailto:discuss-gnuradio@gnu.org> *Subject:* Re: [Discuss-gnuradio] Gnuradio-companion Dear Sumit. I just noticed this thread: you're using RHEL 6, which onl

Re: [Discuss-gnuradio] Gnuradio-companion

: Re: [Discuss-gnuradio] Gnuradio-companion On Wed, 2015-11-18 at 19:54 -0500, Marcus D. Leech wrote: > On 11/18/2015 07:16 PM, Sumit Saluja wrote: > > Hi Marcus, > > > > I am trying to install it on Our departmental cluster which is > > RHEL6.7. Right now we can’t u

Re: [Discuss-gnuradio] Gnuradio-companion

@gnu.org *Subject:* Re: [Discuss-gnuradio] Gnuradio-companion Dear Sumit. I just noticed this thread: you're using RHEL 6, which only hast Boost 1.41; UHD cannot build with anything below Boost 1.46. Is there a particular reason for sticking with this very old version, or can you upgrade

Re: [Discuss-gnuradio] Gnuradio-companion

-gnuradio-bounces+ssaluja=princeton@gnu.org] On Behalf Of Marcus D. Leech Sent: Wednesday, November 18, 2015 7:54 PM To: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] Gnuradio-companion On 11/18/2015 07:16 PM, Sumit Saluja wrote: Hi Marcus, I am trying to install it on Our departmental

Re: [Discuss-gnuradio] Gnuradio-companion

rom:* discuss-gnuradio-bounces+ssaluja=princeton@gnu.org [discuss-gnuradio-bounces+ssaluja=princeton@gnu.org] on behalf of Marcus D. Leech [mle...@ripnet.com] *Sent:* Wednesday, November 18, 2015 3:58 PM *To:* discuss-gnuradio@gnu.org *Subject:* Re: [Discuss-gnuradio] Gnuradio-companion On 1

Re: [Discuss-gnuradio] Gnuradio-companion

Of Marcus Müller Sent: Wednesday, November 18, 2015 6:09 PM To: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] Gnuradio-companion Dear Sumit. I just noticed this thread: you're using RHEL 6, which only hast Boost 1.41; UHD cannot build with anything below Boost 1.46. Is there a particular

Re: [Discuss-gnuradio] Gnuradio-companion

RUE > CMake Error at cmake/Modules/UHDComponent.cmake:51 (MESSAGE): > Dependencies for required component LibUHD not met. > Call Stack (most recent call first): > CMakeLists.txt:279 (LIBUHD_REGISTER_COMPONENT) > > > -- Configuring incomplete, errors occ

Re: [Discuss-gnuradio] Gnuradio-companion

ch [mle...@ripnet.com] Sent: Wednesday, November 18, 2015 3:58 PM To: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] Gnuradio-companion On 11/18/2015 03:45 PM, Sumit Saluja wrote: If I am building gnuradio manually Iam getting following message ###

Re: [Discuss-gnuradio] Gnuradio-companion

I'd like to emphasize on the possibilities for self-debug, in this case. GNU Radio's cmake run closely describes which dependencies were missing and which components therefore got disabled. GRC needs python > 2.5 (I strongly recommend using 2.7 for compatibility with out of tree modules),

Re: [Discuss-gnuradio] Gnuradio-companion

On Mon, Nov 16, 2015 at 12:47 PM, Sumit Saluja wrote: > Hi, > > I am building gnuradio on RHEL 6 and gnuradio-companion is not enabling > . How I Should enable gnuradio-companion > > And UHD is not compiling on RHEL6. > > > > > > Thanks > > > > Sumit Saluja > Install

Re: [Discuss-gnuradio] Gnuradio-companion

To amplify what Tom said, if PyBOMBS fails to compile, please increase its log level by adding "-v -v -v", capture the full output, upload it to something like pastebin and post a link. I don't have any RHEL6 machines handy but my F22 machine is able to build enough pieces to get

Re: [Discuss-gnuradio] gnuradio-companion development

Albin, it's all here. There's a working group for GRC development, headed by Sebastian Koslowski. There's also issues on our issue tracker and a roadmap on the wiki http://gnuradio.org/redmine/projects/gnuradio/wiki/GRCroadmap. M On 07/30/2015 08:11 AM, Albin Stigö wrote: Hi, Is there a

Re: [Discuss-gnuradio] gnuradio-companion development

Ok, great to know there are some other mac users... I have reimplemented some blocks using Apples Accelerate framework.. theoretically they should perform better on apple hardware although I havn't done any benchmarks. I will try to release those... Also knowing there are other mac users will

Re: [Discuss-gnuradio] gnuradio-companion development

On Thu, Jul 30, 2015 at 1:21 PM, Albin Stigö albin.st...@gmail.com wrote: Hi Seth, I'm fairly new to gnuradio but I've spent the last couple of weeks digging through the code of the runtime and grc. GRC doesn't work that well on my macbook because of issues with qt and gtk2 (especially

Re: [Discuss-gnuradio] gnuradio-companion development

Albin, What part are you looking to work on? I think there are a few new features being worked on for the current version, and Hopefully we are going to start ramping up on the qt port again soon. -- Seth Sent from my iPhone On Jul 30, 2015, at 11:11 AM, Albin Stigö albin.st...@gmail.com

Re: [Discuss-gnuradio] gnuradio-companion development

Hi Seth, I'm fairly new to gnuradio but I've spent the last couple of weeks digging through the code of the runtime and grc. GRC doesn't work that well on my macbook because of issues with qt and gtk2 (especially hidpi retina displays)... I suspect there are very few gnuradio users on mac but I

Re: [Discuss-gnuradio] gnuradio-companion-3.7.7.1 debian package

Hi Marcus, I used a new installation of 12.04. I got the sources for 3.7.7.1 instead of 3.7.7 this time. The generated debian package works fine. My previous environment could have been wrong or maybe it was something in 3.7.7. In any case, thanks a lot for your help. Cheers, Murray 2015-06-19

Re: [Discuss-gnuradio] gnuradio-companion-3.7.7.1 debian package

Hi! user@pc:~$ gnuradio-config-info ImportError: libboost_system.so.1.58.0: cannot open shared object file: No such file or directory This means that the gnuradio-config-info was definitely built with another version of boost (1.58) than what is found at the moment you start it. The point

Re: [Discuss-gnuradio] gnuradio-companion-3.7.7.1 debian package

Thanks for that Marcus, I got around that first step. My computer runs Ubuntu 12.04 with libboost 1.48 and it has a working gnuradio installation v3.7.7.1-120-g67463e74 from the script in the web. I used that computer to create the debian package based on https://github.com/gnuradio/gnuradio.git

Re: [Discuss-gnuradio] gnuradio-companion-3.7.7.1 debian package

Hi Murray, you'd typically do something like: cmake -DCMAKE_INSTALL_PREFIX=/usr .. to match what debian expects. Then, instead of simply installing stuff there, you install into your fake root directory using make make install DESTDIR=/home/murray/fake_root/whatever That will only bend around

Re: [Discuss-gnuradio] gnuradio-companion-3.7.7.1 debian package

Hello again 2015-06-19 14:35 GMT+01:00 Marcus Müller marcus.muel...@ettus.com: Hi! user@pc:~$ gnuradio-config-info ImportError: libboost_system.so.1.58.0: cannot open shared object file: No such file or directory This means that the gnuradio-config-info was definitely built with

Re: [Discuss-gnuradio] gnuradio-companion-3.7.7.1 debian package

Hi Murray, that's strange: ImportError: libboost_system.so.1.58.0: cannot open shared object file: No such file or directory contradicts libboost_system.so.1.48.0 = /usr/lib/libboost_system.so.1.48.0 (0xb71d8000) There's something seriously wrong about this situation. If not

Re: [Discuss-gnuradio] gnuradio-companion and multithreading

Hi Andreas, If i stop the drawing of all the graphs in the compiled GNU Radio application, i could change parameters like the volume or gain with the sliders/text boxes now. That was to be expected :) Calculating a 512-point FFT is somewhat ressource-consuming, but drawing and updating a graph

Re: [Discuss-gnuradio] gnuradio-companion and multithreading

Hi Marcus, Hi Andreas, GRC is already as multithreaded as GTK applications can generally be -- I think the bottleneck here is really your Bananapi's CPU, its RAM and its graphics card driver. If i stop the drawing of all the graphs in the compiled GNU Radio application, i could change

Re: [Discuss-gnuradio] gnuradio-companion and multithreading

Hi Andreas, GRC is already as multithreaded as GTK applications can generally be -- I think the bottleneck here is really your Bananapi's CPU, its RAM and its graphics card driver. To be honest, I generally consider the Raspberry Pi and similar devices to be embedded ones with hardware that

Re: [Discuss-gnuradio] gnuradio-companion and multithreading

That would require wholesale reworking of GRC. You *really, really, really* shouldn't think of a lowly banana-pi as your *development* environment. The .py files that are generated by GRC can be generated on a real machine, and executed on the banana-pi, provided that you have identical GR

Re: [Discuss-gnuradio] Gnuradio Companion Blocks missing property tabs

On Thu, Aug 7, 2014 at 5:41 PM, Richard Bell richard.be...@gmail.com wrote: Hello all, I noticed today that, for example, my 'QT GUI Time Sink' blocks properties window is missing the config tab. This means I cannot change the label of my time sink plots. In general, all of my grc blocks

Re: [Discuss-gnuradio] gnuradio companion core dump

These can be a bit annoying. You can inspect the core dump (http://gnuradio.org/redmine/projects/gnuradio/wiki/TutorialsDebugging) to see where this happens. Chances are you rebuilt GNU Radio and this is some OOT module that is acting up. M On 08/04/2014 12:14 AM, Tom McDermott wrote: I had

Re: [Discuss-gnuradio] gnuradio-companion segfaults with latest gnuradio master and gr-osmosdr

On Thu, Dec 19, 2013 at 1:50 PM, Nowlan, Sean sean.now...@gtri.gatech.edu wrote: When I run gnuradio-companion with the latest gnuradio master and gr-osmosdr master, it segfaults. A backtrace reveals that there’s a problem when Python tries to load _osmosdr_swig. If I uninstall gr-osmosdr,

Re: [Discuss-gnuradio] GNURadio Companion PAUSE

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Paul, couldn't let that comment sit around long. Though, if I put two and two togehter, I'd say since you've been asking what error 28 indicates, it has even nothing much to do with computing capabilities of your computer. Just a shortage of

Re: [Discuss-gnuradio] GNURadio Companion PAUSE

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Paul, use a valve together with some input widget. There has been great discussion over how to build a valve system the last month, you might need to read multiple threads to find the solution that suits you best. Greetings, Marcus On

Re: [Discuss-gnuradio] GNURadio Companion PAUSE

Thanks! Got that working with a valve and a button. However, my flow now uses Volk machine, again, which doesn't record my data as well as it was recording before the valve (and without Volk machine). Any way to keep it from doing this? Paul B. Huter On Dec 5, 2013 11:11 AM, Marcus Müller

Re: [Discuss-gnuradio] GNURadio Companion PAUSE

Again, Volk has nothing to do with it. All that printout means is that your flowgraph is now using a block which uses a Volk function for acceleration. It has nothing to do with the problem you're seeing. --n On Thu, Dec 5, 2013 at 1:11 PM, Paul B. Huter paul.b.hu...@gmail.comwrote: Thanks!

Re: [Discuss-gnuradio] GNURadio Companion PAUSE

How do I resolve this problem, then? Is it an issue with my computing capability? On Thu, Dec 5, 2013 at 3:13 PM, Nick Foster bistrom...@gmail.com wrote: Again, Volk has nothing to do with it. All that printout means is that your flowgraph is now using a block which uses a Volk function for

Re: [Discuss-gnuradio] GNURadio Companion PAUSE

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Well, this is just guessing in the blue, but: It might be the computing capability of your computer. Not necessarily of yourself. :D SCNR, Greetings, Marcus On 05.12.2013 22:22, Paul B. Huter wrote: How do I resolve this problem, then? Is it an

Re: [Discuss-gnuradio] Gnuradio-Companion Documentation.

On Thu, Sep 19, 2013 at 10:45 AM, Tim tim.oshea...@gmail.com wrote: Docs can take a long time to build, so when doing multiple builds a day during testing you really don't want to have this turned on. Likewise if you are building on slow machine or an older machine without sufficient

Re: [Discuss-gnuradio] Gnuradio-Companion Documentation.

On Wed, Sep 18, 2013 at 3:48 PM, M Dammer i...@mdammer.net wrote: May I then suggest to enable the docs in the pybombs recipe by default as well ? You may suggest. Sorry for being glib. I also think it's a good idea to enable the documentation by default. If Tim agrees and there wasn't a

Re: [Discuss-gnuradio] Gnuradio-Companion Documentation.

Docs can take a long time to build, so when doing multiple builds a day during testing you really don't want to have this turned on. Likewise if you are building on slow machine or an older machine without sufficient doxygen. But obviously they are valuable for users doing their primary build

Re: [Discuss-gnuradio] Gnuradio-Companion Documentation.

I just had the experience of how much the documentation build process can slow down the build in general. So I think a flag that can be set/unset during the pybombs configuration / reconfiguration process is a good idea. And it would make it easier for new users who a: most likely want

Re: [Discuss-gnuradio] Gnuradio-Companion Documentation.

Kevin, are you building gnuradio via PyBombs ? In this case you must have doxygen installed on your system. Then you have to edit the build recipe for gnuradio to enable doxygen: open the file gnuradio.lwr in your pybombs/recipes folder. in the line starting with var config_opt change

Re: [Discuss-gnuradio] Gnuradio-Companion Documentation.

On Wed, Sep 18, 2013 at 3:13 PM, Kevin jplscan...@gmail.com wrote: Hello, I built Gnuradio using $ wget http://www.sbrac.org/files/build-gnuradio chmod a+x ./build-gnuradio ./build-gnuradio Which means I don't need to worry about this? ./configure --enable-doxygen make sudo make

Re: [Discuss-gnuradio] Gnuradio-Companion Documentation.

Hello, I built Gnuradio using $ wget http://www.sbrac.org/files/build-gnuradio chmod a+x ./build-gnuradio ./build-gnuradio Which means I don't need to worry about this? ./configure --enable-doxygen make sudo make install On Wed, Sep 18, 2013 at 1:49 PM, M Dammer i...@mdammer.net wrote:

Re: [Discuss-gnuradio] Gnuradio-Companion Documentation.

May I then suggest to enable the docs in the pybombs recipe by default as well ? On 18/09/13 20:22, Tom Rondeau wrote: On Wed, Sep 18, 2013 at 3:13 PM, Kevin jplscan...@gmail.com wrote: Hello, I built Gnuradio using $ wget http://www.sbrac.org/files/build-gnuradio chmod a+x

Re: [Discuss-gnuradio] Gnuradio-Companion Documentation.

Thank you, So those documentation will be shown when I click block Properties ? That's the description below Documentation section? Sincerely, On Wed, Sep 18, 2013 at 2:22 PM, Tom Rondeau t...@trondeau.com wrote: On Wed, Sep 18, 2013 at 3:13 PM, Kevin jplscan...@gmail.com wrote: Hello,

Re: [Discuss-gnuradio] gnuradio-companion

On Mon, Jun 10, 2013 at 11:50 AM, Pratik Kumar pratikkumar2...@gmail.com wrote: I am new to gnuradio. Can i get this channel as a block in gnuradio-companion. Depends on what version you are using, but most likely, yes. In the Blocks list on the right hand side of gnuradio-companion you can

Re: [Discuss-gnuradio] gnuradio-companion

Assuming you're using a recent version of GRC, just start typing in the blocks window which enables a search. So typing "channel model" here will take you to the channel model. on Jun 10, 2013, Pratik Kumar pratikkumar2...@gmail.com wrote: I am new to gnuradio. Can i get this channel as a block

Re: [Discuss-gnuradio] gnuradio-companion problem

Hi Dan - Make sure you've installed both the gnuradio and gr-osmosdr ports with the +swig variant. Without it, you do not get the *_swig import libraries. If this is not the case, then email me off list and I'll help you debug the issue. - MLD On May 21, 2013, at 11:11 AM, Dan Aldrich

Re: [Discuss-gnuradio] gnuradio companion: wrong ELF class

Hello, I am trying to run gnuradio-companion under Suse 12.3 I get the following error-message: gnuradio-companion Traceback (most recent call last): File /usr/bin/gnuradio-companion, line 67, inmodule from gnuradio.grc.python.Platform import Platform File

Re: [Discuss-gnuradio] gnuradio-companion does not find block-ids

I started gnuradio-companion after doing all this and I get errors like this: line 198, in import_data raise LookupError('source block id %s not in block ids'%source_block_id) Is there an environment variable I am missing? There is another thing to consider, which is where are

Re: [Discuss-gnuradio] gnuradio-companion

On 23/04/13 14:46, Sid Boyce wrote: # gnuradio-config-info -v v3.6.4.1-106-gf1dbf510 On bot x86_64 and ARM gnuradio used to work now I get a pop-up complaining about PYTHONPATH. export PYTHONPATH=/usr/lib/python2.7 on ARM and export PYTHONPATH=/usr/lib64/python2.7 on openSUSE doesn't help.

Re: [Discuss-gnuradio] gnuradio-companion

On 23/04/13 14:46, Sid Boyce wrote: # gnuradio-config-info -v v3.6.4.1-106-gf1dbf510 On bot x86_64 and ARM gnuradio used to work now I get a pop-up complaining about PYTHONPATH. export PYTHONPATH=/usr/lib/python2.7 on ARM and export PYTHONPATH=/usr/lib64/python2.7 on openSUSE doesn't help.

Re: [Discuss-gnuradio] gnuradio-companion

On 06/05/13 00:34, Marcus D. Leech wrote: On 23/04/13 14:46, Sid Boyce wrote: # gnuradio-config-info -v v3.6.4.1-106-gf1dbf510 On bot x86_64 and ARM gnuradio used to work now I get a pop-up complaining about PYTHONPATH. export PYTHONPATH=/usr/lib/python2.7 on ARM and export

Re: [Discuss-gnuradio] gnuradio-companion

On 06/05/13 00:39, Marcus D. Leech wrote: On 23/04/13 14:46, Sid Boyce wrote: # gnuradio-config-info -v v3.6.4.1-106-gf1dbf510 On bot x86_64 and ARM gnuradio used to work now I get a pop-up complaining about PYTHONPATH. export PYTHONPATH=/usr/lib/python2.7 on ARM and export

Re: [Discuss-gnuradio] gnuradio-companion

Thanks again Marcus, The problem with the build-gnuradio script is that it is set up to build on Ubuntu and Fedora but no good for openSUSE. 73 ... Sid. When somebody sends me a reliable recipe for building on OpenSuse (and detecting that it's an OpenSuse system), I'll be happy to update

Re: [Discuss-gnuradio] gnuradio-companion

On 06/05/13 02:09, Marcus D. Leech wrote: Thanks again Marcus, The problem with the build-gnuradio script is that it is set up to build on Ubuntu and Fedora but no good for openSUSE. 73 ... Sid. When somebody sends me a reliable recipe for building on OpenSuse (and detecting that it's an

Re: [Discuss-gnuradio] gnuradio-companion

Try a sudo ldconfig. Ralph. -Original Message- From: discuss-gnuradio-bounces+ralph=schmid@gnu.org [mailto:discuss-gnuradio-bounces+ralph=schmid@gnu.org] On Behalf Of Sid Boyce Sent: Tuesday, 23 April, 2013 15:47 To: discuss-gnuradio@gnu.org Subject: [Discuss-gnuradio]

Re: [Discuss-gnuradio] gnuradio-companion

On 23/04/13 14:51, Bastian Bloessl wrote: Hello Sid, On 04/23/2013 03:46 PM, Sid Boyce wrote: # gnuradio-config-info -v v3.6.4.1-106-gf1dbf510 On bot x86_64 and ARM gnuradio used to work now I get a pop-up complaining about PYTHONPATH. export PYTHONPATH=/usr/lib/python2.7 on ARM and export

Re: [Discuss-gnuradio] gnuradio-companion

On 23 Apr 2013 10:51, Sid Boyce wrote: On 23/04/13 14:51, Bastian Bloessl wrote: Hello Sid, On 04/23/2013 03:46 PM, Sid Boyce wrote: # gnuradio-config-info -v v3.6.4.1-106-gf1dbf510 On bot x86_64 and ARM gnuradio used to work now I get a pop-up complaining about PYTHONPATH. export

Re: [Discuss-gnuradio] gnuradio-companion

I always build from source as there are some additions from dl2stg needed for HiQSDR support. I think I'll ask him to submit them upstream. # cat /usr/src/gnuradio_audio.diff diff --git a/gr-audio/lib/alsa/audio_alsa_source.cc b/gr-audio/lib/alsa/audio_alsa_source.cc index 4f0042b..fe41e43

Re: [Discuss-gnuradio] gnuradio-companion hamlib bodging

On Sun, Oct 28, 2012 at 5:36 PM, Darren Long darren.l...@mac.com wrote: Hi again, I've got my gnuradio 'pan-adapter' for my KX3 transceiver pretty much working now: http://www.g0hww.net/2012/10/gnuradio-hamlib-and-kx3.html but there seems to be a memory leak occurring when I call

Re: [Discuss-gnuradio] gnuradio-companion hamlib bodging

Never mind. I've bodged it directly in the generated python. Darren On 28/10/12 14:35, Darren Long wrote: Hi, In gnuradio-companion, I'm tring to control my KX3 transceiver using hamlib's rigctl utility. I've bodged a call to: float(pexpect.run(rigctl -m 229 -r /dev/ttyUSB0 -s 38400

Re: [Discuss-gnuradio] gnuradio-companion hamlib bodging

Hi again, I've got my gnuradio 'pan-adapter' for my KX3 transceiver pretty much working now: http://www.g0hww.net/2012/10/gnuradio-hamlib-and-kx3.html but there seems to be a memory leak occurring when I call self.wxgui_waterfallsink2_0.set_baseband_freq(self.rig_freq) to update the

  1   2   >