Re: [Discuss-gnuradio] error while making detector

Hi Yan, > If I want to add more functions can I add them to existing blocks? You could do that; often, functionality is cleaner implemented by adding further blocks, but if you need something that needs a modified block, creating your own might really be the best way. I'd really recommend doing

Re: [Discuss-gnuradio] gr-lte Receiver Framework

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Ali, Please don't post so many files on the mailing list. Use a website which offers free hosting and post the link. Also, please don't send mails twice. Actually, I can't spot the issue at the moment. Just to confirm this, it always detects the

Re: [Discuss-gnuradio] error while making detector

There's already blocks that do energy calculation, so you really don't have to implement this yourself. In fact, I wrote a short answer on a similar question just yesterday. The question there was how to add a method "get_bandpower" to a C++ block, so here's the excerpt from

Re: [Discuss-gnuradio] error while making detector

Hi Marcus, Actually, I need to do the spectrum management and interference identification using GNU radio and USRP, and I’ve read some articles about them, but I still don’t know how to realize them, so I want to find some examples about this area. Unfortunately, I first find was an energy

[Discuss-gnuradio] Import Error

Hi, I am trying to compile a file namely usrp_spectrum_sense_tx.py but it says the following error message: Traceback (most recent call last): File "./usrp_spectrum_sense_tx.py", line 180, in from gnuradio import gr, gru, eng_notation, optfir, window ImportError: cannot import name optfir

Re: [Discuss-gnuradio] error while making detector

As examples the guided tutorials are really the go-to place. Doing energy detection is pretty straightforward, as mentioned in the quoted stackoverflow answer: simply calculate some kind of instantaneous energy of your samples stream, which in the simplest case really is just applying the

Re: [Discuss-gnuradio] QT Time Raster in OSX 10.10.4 Not Rastering

Tom, Thanks for the info. I could see a reimplementation as a good project for some CS undergrads here at GT. Is there a particular way the QT time raster should be rewritten (e.g. using particular libraries, QT versions, etc) to be OS X compatible and align with the future direction of QT

[Discuss-gnuradio] QT Time Raster in OSX 10.10.4 Not Rastering

The QT Time Raster GUI doesn’t appear to function in the latest gnuradio-devel macports. The plot appears all a single color although the bits into the graph are not constant. I run the same flow graph on my Ubuntu setup and I get the rastered bits plotted as expected. I’m using:

Re: [Discuss-gnuradio] error while making detector

Hi Yan, which tutorial exactly where you following (URL)? I recommend using the Guided Tutorials for beginners; they are much better illustrated, and they don't need the sometimes broken howto infrastructure. https://gnuradio.org/redmine/projects/gnuradio/wiki/Guided_Tutorials Best regards,

Re: [Discuss-gnuradio] QT Time Raster in OSX 10.10.4 Not Rastering

On Wed, Nov 25, 2015 at 10:08 AM, Paul Garver wrote: > The QT Time Raster GUI doesn’t appear to function in the latest > gnuradio-devel macports. The plot appears all a single color although the > bits into the graph are not constant. I run the same flow graph on my > Ubuntu

Re: [Discuss-gnuradio] USRP connection problem

Hi Vinay, I'm taking the freedom to CC: the usrp-users mailing list here, as this is not a GNU Radio problem. I think you should follow up there. The E310, by default, doesn't have a static IP address, but gets one from a DHCP server. So, in order to talk to it, you should have a DHCP server

[Discuss-gnuradio] USRP connection problem

hi, First time I am using USRP E310.I am not able to connect to host computer how to solve the problem.How to find out IP adress of USRP ubuntu@ubuntu:~$ ping 192.168.10.2 PING 192.168.10.2 (192.168.10.2) 56(84) bytes of data. >From 192.168.10.1 icmp_seq=1 Destination Host Unreachable >From

Re: [Discuss-gnuradio] gr-lte Receiver Framework

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Ali, I assume you pulled the latest gr-lte Version this week and you're using the _siso.grc flowgraph. Does your file source repeat the frames you generated? Maybe the flowgraph gets stuck before the PBCH path receives any samples. While PBCH,

Re: [Discuss-gnuradio] Fwd: Crash some time after running 2 channel full duplex B210

Hi Marcus, Setting them to 256 is taking much longer before I get the error. I'll try playing with them and other parameters. Thank you Marcus. On 24 November 2015 at 21:59, Marcus D. Leech wrote: > On 11/24/2015 04:54 PM, Saulo Queiroz wrote: > >> >> Hi, >> >> I got the

Re: [Discuss-gnuradio] Bug with set_taps in pfb_clock_sync

On Tue, Nov 24, 2015 at 3:42 PM, Richard Bell wrote: > I think I've come across a bug with the pfb_clock_sync blocks set_taps > implementation. If I change a parameter in python that causes a change to > the filter tap variable being fed to the pfb_clock_sync block,

[Discuss-gnuradio] error while making detector

Hey, I’m a new to use gnuradio and USRP B210, now I want to generate my OOT module start with the example ‘howto_detect’, and I followed guided tutorial in gnuradio.org. But there are still some problems as follows. [ 6%] Building CXX object