[Discuss-gnuradio] forecast and set history function for haar decomposition

2013-10-22 Thread Bharat Mukkala
I am creating a new gnu radio block for decomposing the signal using haar wavelet decompostion and includes the option of number of levels of decompostion. In order to write the code, how should i set the set_history or forecast function because in order to produce output the input signal should b

Re: [Discuss-gnuradio] Misc questions, regarding Interrupt coalescing

2013-10-22 Thread Johannes Demel
Unfortunately last nights mail didn't get to the mailing list. But here it is. Hi, first of all you might be interested in [1]. Depending on the actual setup of your NIC latency depends a lot on interrupt coalescing. There is also some further reading on this page. Have fun [1] http://code.ett

[Discuss-gnuradio] QT GUI Range - broken in GRC 3.7.2git-107-g636140af ??

2013-10-22 Thread Tom McDermott
Have updated to the latest git, been a month or two since the last update here. Previous 3.7.2git (a little back) ran fine. With the latest, flowgraphs seem to start but immediately exit ('done') when there is a QT GUI Range control on them.  If the QT GUI Range is deleted and replaced with a

Re: [Discuss-gnuradio] Code re-use in blocks / C++ inheritance with gr::sync_block

2013-10-22 Thread Johnathan Corgan
On Tue, Oct 22, 2013 at 6:40 AM, Sylvain Munaut <246...@gmail.com> wrote: > > I think that's the point of private and protected members, you shouldn't > > have to go to the total extreme of hiding everything away in an impl, if > you > > plan to inherit from that impl later > > Well it's most

[Discuss-gnuradio] GRCon13 Presentations

2013-10-22 Thread Tom Rondeau
Hi everyone, I just wanted to make sure everyone was aware that the all* of the GRCon13 presentation slides have been uploaded to the website. Enjoy! http://www.trondeau.com/grcon2013-presentations/ Tom *Almost all. Missing Balint's slides, but I did link to his YouTube video of The Balint Show

Re: [Discuss-gnuradio] ATSC decoder example in GR 3.7.1

2013-10-22 Thread Tom Rondeau
On Tue, Oct 15, 2013 at 10:01 PM, Ethan Trewhitt wrote: > As a part of my quest to understand some of the examples in GR (and > eventually contribute some well-commented GRC examples of my own), > I've been messing around with the atsc_rx.py script. Unfortunately, > since I have a USRP2, I can't s

Re: [Discuss-gnuradio] Carrier Phase Measurement

2013-10-22 Thread Raydel Abreu (CM2ESP)
Yes, you are right Marcus. Well, what other method can I use to compensate a drifting receiver while conserving the carrier's phase changes? Someone else wants to jump in and give any thoughs??? Raydel 2013/10/22, Marcus Müller : > PLL stands for phase locked loop. It eliminates phase variations

[Discuss-gnuradio] Fwd: Carrier Phase Measurement

2013-10-22 Thread Raydel Abreu (CM2ESP)
One more thing The Quadrature Demodulator produces a stream of floats. I used as previously recommended Keep One in N for sample only 5 times by second. However, which method can I use to save the Float Stream into a plain text file. The File Sink Block outputs a binary file? Best wishes, Ra

Re: [Discuss-gnuradio] Carrier Phase Measurement

2013-10-22 Thread Marcus Müller
PLL stands for phase locked loop. It eliminates phase variations. On 10/22/2013 06:21 PM, Raydel Abreu (CM2ESP) wrote: Hi Marcus, Thanks for the tip. In a previous e-mail Marcus D. Leech recommend me to use the Quadrature Demodulator Block as something not perfect, but usable to check for pha

Re: [Discuss-gnuradio] Carrier Phase Measurement

2013-10-22 Thread Raydel Abreu (CM2ESP)
Hi Marcus, Thanks for the tip. In a previous e-mail Marcus D. Leech recommend me to use the Quadrature Demodulator Block as something not perfect, but usable to check for phase changes. It works for me, as long as there is a pure carrier without phase changes, and without care the amplitude, the

Re: [Discuss-gnuradio] Carrier Phase Measurement

2013-10-22 Thread Marcus Müller
Hi Raydel, try Keep N in M (keep 1 in N) for the "sampling". However, if you correctly employ a PLL, your phase will be static; if it's not, than the PLL is not doing it's job well. Greetings, Marcus On 10/22/2013 05:21 PM, Raydel Abreu (CM2ESP) wrote: Hello all, I am new to GNU Radio and I a

[Discuss-gnuradio] Carrier Phase Measurement

2013-10-22 Thread Raydel Abreu (CM2ESP)
Hello all, I am new to GNU Radio and I am still learning the basic. I have a quick question. What blocks and which way can I use in order to "sample" and know the phase of a tuned carrier at regular intervals. General idea: Let's suppose there is a carrier, after applying proper tuning (Freq Xlat

Re: [Discuss-gnuradio] BladRF

2013-10-22 Thread Ralph A. Schmid, dk5ras
Yes, I had this problem. As far as I remember I uninstalled bladerf and gr-osmosdr, then manually deleted all remains of it and of hackrf (what I never used) from my system, compiled and installed again bladerf, compiled a fresh version of gr-osmosdr with the cmake-option not to build hackrf suppor

[Discuss-gnuradio] BladRF

2013-10-22 Thread Muhammad JUNAID
I am working on bladeRF, dose anyone working on it and facing this error? Ubuntu 13.04 linux; GNU C++ version 4.7.3; Boost_105300; UHD_003.005.004-140-gfb32ed16 <<< Welcome to GNU Radio Companion 3.7.1 >>> i got this error while running osmocom_fft. junaid@Junaid:~/gnuradio/gr-osmosdr$ osmocom_f

Re: [Discuss-gnuradio] zero ninput_items_required[0]

2013-10-22 Thread Marcus Müller
To be completely clear: In your original post you stated that your block really behaves like a sync_interpolator/decimator. Yet, you're reinventing the wheel by copying the wheel into your code. DO NOT just copy code to you not-sync block from sync_block if you

Re: [Discuss-gnuradio] zero ninput_items_required[0]

2013-10-22 Thread Nemanja Savic
Well, I still didn't try with interpolator, cause it seems that it will work. I'd rather try to make it with general block and also learn more about how the stuff work. That's why I said that I used principles used for interpolator. Ok, I am now tracking number of produces items and it works ok, fr

Re: [Discuss-gnuradio] zero ninput_items_required[0]

2013-10-22 Thread Martin Braun (CEL)
On Tue, Oct 22, 2013 at 02:20:04PM +0200, Nemanja Savic wrote: > Hello guys again! > > > Based on Martins suggestion and Marucs' explanation I copied some principles > from sync_interpolator and situation looks much better. I used function > set_output_multiple and set_relative rate and now the o

Re: [Discuss-gnuradio] zero ninput_items_required[0]

2013-10-22 Thread Martin Braun (CEL)
On Tue, Oct 22, 2013 at 02:22:20PM +0200, Nemanja Savic wrote: > Or maybe the question should be like this: on which parameter to rely when > making general work function, number of iput items or number of output items? As I just said, in a sync_interpolator, you're not using general_work(), and y

Re: [Discuss-gnuradio] zero ninput_items_required[0]

2013-10-22 Thread Nemanja Savic
Or maybe the question should be like this: on which parameter to rely when making general work function, number of iput items or number of output items? On Tue, Oct 22, 2013 at 2:20 PM, Nemanja Savic wrote: > Hello guys again! > > Based on Martins suggestion and Marucs' explanation I copied som

Re: [Discuss-gnuradio] zero ninput_items_required[0]

2013-10-22 Thread Nemanja Savic
Hello guys again! Based on Martins suggestion and Marucs' explanation I copied some principles from sync_interpolator and situation looks much better. I used function set_output_multiple and set_relative rate and now the outcome of calling forecast function is much better. For example, for symbol

Re: [Discuss-gnuradio] Using USRP to transmit and receive samples

2013-10-22 Thread lingeswar
hi, i tried connecting a file sink at the tag debug place and i found o's and 1's coming. we may have to pack them back like opposite operation in transmitter GRC. i used REPACK Bits block and tested that the actual data (1 to 96) is not coming back.. and we have to use the "check CRC" in the strea

Re: [Discuss-gnuradio] Code re-use in blocks / C++ inheritance with gr::sync_block

2013-10-22 Thread Sylvain Munaut
Hi Marcus, > If you correctly called the chain of superconstructors, that shouldn't > happen if you correctly set your io_signatures. Yup, that was the issue. I was defining the call to gr::sync_block constructor as part of the base_sink_c_impl class constructor since it seemed the most logical

Re: [Discuss-gnuradio] Code re-use in blocks / C++ inheritance with gr::sync_block

2013-10-22 Thread Marcus Müller
Hi Sylvain, this is getting really interesting :) On 10/22/2013 11:55 AM, Sylvain Munaut wrote: Yeah and that's what the 'virtual' are for in the inheritance tree. And if you look at the resulting tree according to C++, http://pastebin.com/raw.php?i=cDWQQwHn I totally agree! So, only one basic_

Re: [Discuss-gnuradio] Code re-use in blocks / C++ inheritance with gr::sync_block

2013-10-22 Thread Sylvain Munaut
Hi, > this is yet another incarnation of the diamond problem I discussed with > Nemanja: > http://lists.gnu.org/archive/html/discuss-gnuradio/2013-09/msg00150.html > > Your glfw_.._impl is a double indirect subclass to base_sink_c: > glfw_sink_c_impl->glfw_sink_c->base_sink_c > glfw_sink_c_impl->b

Re: [Discuss-gnuradio] Code re-use in blocks / C++ inheritance with gr::sync_block

2013-10-22 Thread Marcus Müller
Hi Sylvain, this is yet another incarnation of the diamond problem I discussed with Nemanja: http://lists.gnu.org/archive/html/discuss-gnuradio/2013-09/msg00150.html Your glfw_.._impl is a double indirect subclass to base_sink_c: glfw_sink_c_impl->glfw_sink_c->base_sink_c glfw_sink_c_impl->base_

Re: [Discuss-gnuradio] error code 0xf

2013-10-22 Thread Marcus Müller
Hello A.B.! For the error code, I shall refer you to the UHD source code: http://files.ettus.com/uhd_docs/doxygen/html/metadata_8hpp_source.html And thus I saw: Apparently, you receive bad packets. A quick "git grep 'vrt packet offset'" led to host/lib/transport/super_recv_packet_handler.hpp in t

Re: [Discuss-gnuradio] Misc questions, regarding Interrupt coalescing

2013-10-22 Thread Marcus Müller
Hi Naceur, while questions 1 and 2 definitely are more of material for usrp-users, I'll try to answer them as briefly as possible, and puit usrp-users into the CC:. On 10/21/2013 10:19 PM, Naceur wrote: 1/ Did anyone already tested the effect of Interrupt coalescing on reducing the latency when

[Discuss-gnuradio] Code re-use in blocks / C++ inheritance with gr::sync_block

2013-10-22 Thread Sylvain Munaut
Hi, So what I'm trying to achieve is to share a lot of code (including the gr::sync_block implementation for work/start/stop) and a common interface between several gnuradio blocks. What I have currently come up with is (short version, see bottom for more complete version) : --- class API base_s

Re: [Discuss-gnuradio] Using USRP to transmit and receive samples

2013-10-22 Thread Martin Braun (CEL)
On Mon, Oct 21, 2013 at 09:06:24PM -0500, JPL wrote: > Hello, Martin > > > 1. Would you please tell me where the "manual page" is? It's in the manual. You go to gnuradio.org, click 'C++ manual', then 'Related Pages', then 'Tagged Stream Blocks'. > Because I cannot understand  > > How the Vecto

[Discuss-gnuradio] error code 0xf

2013-10-22 Thread Baier
Dear all, I have increased the buffer frame size from 1472 to 4096 bytes. Than I started my grc application and got the following message: recv buffer smaller than vrt packet offset. UHD source block got error code 0xf. Can somebody help me? Thanks A.B. ___