Re: [Discuss-gnuradio] GnuRadio: Clock Recovery MM: imu out of bounds

Hi Michael, so, this having sat on my "what the hell, I need to look at this" list for the weekend: I can't reproduce the behaviour, but that might simply have the cause of me using white noise instead of your recording. Could you share that? I have two hypotheses and one observation so far: The

Re: [Discuss-gnuradio] Noob question 1

Hi Jan Believe me, I am reading the tutorials, also the youtube lessons https://www.youtube.com/watch?v=N9SLAnGlGQs But for me it is easier to understand basics when there is a basic working layout available. There is so much about GNURADIO out there that a noob also needs some help with the

[Discuss-gnuradio] Noob question 1

Hello all 4 weeks ago did my first steps into Linux Ubuntu. I am trying to get the RTL-Dongel to work but still not succeded in that, Time to ask some help. There is a image with pre-installed drivers and GNU-Radio companion, http://gnuradio.org/redmine/projects/gnuradio/wiki/GNURadioLiveDVD I

Re: [Discuss-gnuradio] Noob question 1

Hi Henk, the problem is that the RTL dongle (and any SDR peripheral) just gives you the signal as it is in the air -- you will still have to demodulate it to get audio! Now, wild assumption: you want to listen to FM Radio for a start. So: * configure your audio sink to 44100 Hz sample rate * use

Re: [Discuss-gnuradio] Display Problem with QT GUI Vector Sink

The example is running without errors. Is it possible, that the way my music_cf function is outputting the data, might cause some trouble? Simon Am 2015-09-04 21:45, schrieb Martin Braun: There's an example for the vector sink, which doesn't seem to have that issue. Can you confirm that?

Re: [Discuss-gnuradio] Display Problem with QT GUI Vector Sink

Hi Simon, > Is it possible, that the way my music_cf function is outputting the data, might cause some trouble? 181 floats isn't really a "round" itemsize, and since GNU Radio can only build buffers that are multiple of 4KB (==4096B), I assume that you get a large buffer (probably 4096 items of

Re: [Discuss-gnuradio] Noob question 1

Hooking in on the discussion here. I struggle with something similar. I know how to work gnuradio, that’s simple enough. What i want to learn more about is how to configure my own SDR using gnuradio. So what the various blocks are used for, when to use what block, etc. I have experience LISTENING

[Discuss-gnuradio] Volk: __cpuid_count() for MSVC

I noticed since last time (a year ago) I tried building Volk using MSVC v16, the volk_cpu.tmp.c now uses the gcc-centric function '__cpuid_count()' which MSVC doesn't have. I'm not really sure if the below patch is correct. But I assume (from looking at gcc 5.1's source) that the ECX should be

[Discuss-gnuradio] Running flowgraphs from command line

Hi everybody, I installed GNURadio on a fresh machine with Mac OS X 10.10.5 via MacPorts. I now have 2 Python installs in /usr/bin, python2.6 and python2.7. Running flowgraphs with GRC is no problem. However, when trying to run a .py-file from the terminal, as suggested in the guided tutorial

Re: [Discuss-gnuradio] Throttle block form wav files

On 7 September 2015 at 15:32, Kevin Reid wrote: > On Sep 7, 2015, at 5:42, Murray Thomson > wrote: > > >> 1. Using some method to force the wav source and audio source to match > sample rates. Specifically, you could use a “Multiply by Matrix”

Re: [Discuss-gnuradio] Throttle block form wav files

On Sep 7, 2015, at 5:42, Murray Thomson wrote: >> 1. Using some method to force the wav source and audio source to match >> sample rates. Specifically, you could use a “Multiply by Matrix” block to >> replace the function of the Selector entirely: give it a matrix

Re: [Discuss-gnuradio] Running flowgraphs from command line

Hi Patrick, I think I might have the answer, although Michael Dickens could certainly provide better explanations and all that. You need to check your environment variables. You can do that in the command line by typing "env". Normally you should see something like "

Re: [Discuss-gnuradio] Noob question 1

My thoughts Ton, I just made the FM receiver Marcus advised and as discribed in tutorial 6. This week I will ask a few questions about the configuration of these blocks. Understanding is the key word for me. Thanks Henk Op 7-9-2015 om 13:38 schreef Ton Machielsen: Hooking in on the

Re: [Discuss-gnuradio] A small error in benchmark_tx file

Dave, this might look strange to the afterworld, but: Are you Ravi? Best regards, Marcus On 08.09.2015 00:05, Dave Allen wrote: > Yes, I tried that. Regarding the former question, I guess I have kept > all the files in that manner but I changed benchmark_tx.py and > uhd_interface.py files as

Re: [Discuss-gnuradio] A small error in benchmark_tx file

I am sorry. No -- Posted via http://www.ruby-forum.com/. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Pybombs recipes submodule pointer update policy

http://www.cgran.org/ isn't up to date either. Ron On 09/07/2015 07:29 PM, Chris Kuethe wrote: I don't think there is an official policy. I do see that Tim updated the recipes pointer a couple of days ago (https://github.com/gnuradio/pybombs/commit/97fe3b3846dc1e10123fdc1c218ed94fa8dba63c). ..

Re: [Discuss-gnuradio] A small error in benchmark_tx file

Thanks for the reply. I really appreciate it. I have subscribed to the mailing list. And in regard to my question, I have given the command and it has popped up this line gnuradio-config-info --version v3.7.7.1-198-g9e133ccb I am not sure of what version the GNU Radio it can be? The command I

Re: [Discuss-gnuradio] Running flowgraphs from command line

Hi Patrick - So what's happening is that with GRC, because it was installed via MacPorts the MP version of Python is used. The terminal only knows what you tell it via environment variables such as PYTHONPATH (already suggested by Kevin Hofschröer) and PATH. In your case right now, I'll bet that

Re: [Discuss-gnuradio] A small error in benchmark_tx file

Yes, I tried that. Regarding the former question, I guess I have kept all the files in that manner but I changed benchmark_tx.py and uhd_interface.py files as far as I remember. Regarding the latter, I was not able to give manually because I did not know as to exactly what sampling rate and

Re: [Discuss-gnuradio] A small error in benchmark_tx file

Ravi, I don't understand -- are you Dave Allen? Best regards, Marcus On 07.09.2015 23:59, Ravi Vemuri wrote: > Hi all, > I have been trying to send data between 2 USRP's from the benchmark_tx > file only to observe that I have been receiving this error. > > Traceback (most recent call last): >

[Discuss-gnuradio] Why cant I increase signal by 1 hz at a time with high frequencies?

It seems that when I create a signal source block and try and view the signal on a waterfall plot or FFT plot, I can not increase the signal by a granularity of 1 Hz at higher starting frequencies. Example: If I create a signal source block with a starting frequency of 1.2 GHz, and in the block

[Discuss-gnuradio] How can I separate and count the IQ samples stored

How can I separate and count the IQ samples stored ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] A small error in benchmark_tx file

Hi all, I have been trying to send data between 2 USRP's from the benchmark_tx file only to observe that I have been receiving this error. Traceback (most recent call last): File "./benchmark_tx.py", line 147, in main() File "./benchmark_tx.py", line 111, in main tb =

Re: [Discuss-gnuradio] A small error in benchmark_tx file

Ha, ok, so I was mistaken regarding the version 3.7.7 is relatively recent! Sanity check: the benchmark_tx and all other files in that directory came with your version GNU Radio, and you did not download them elsewhere, right? Have you tried "./benchmark_tx --help", and then specifying things

[Discuss-gnuradio] ATSC decode successful on SDRPlay RSP

Hi everyone. With help from Ron Economos, I managed to make ATSC decoding work using the SDRPlay RSP. The big issue was that the RSP has a DC bar in the middle of the waterfall. Canceling it in the SDR program isn't enough; you have to get the latest driver and use the EXTIO options *in

Re: [Discuss-gnuradio] Pybombs recipes submodule pointer update policy

I don't think there is an official policy. I do see that Tim updated the recipes pointer a couple of days ago (https://github.com/gnuradio/pybombs/commit/97fe3b3846dc1e10123fdc1c218ed94fa8dba63c). .. I suppose I could write a tool to automate bugging people if the pointer is more than a week

Re: [Discuss-gnuradio] Why cant I increase signal by 1 hz at a time with high frequencies?

On 09/07/2015 10:33 PM, Douglas Beonkey wrote: It seems that when I create a signal source block and try and view the signal on a waterfall plot or FFT plot, I can not increase the signal by a granularity of 1 Hz at higher starting frequencies. Example: If I create a signal source block with a

Re: [Discuss-gnuradio] Why cant I increase signal by 1 hz at a time with high frequencies?

On Tue, Sep 08, 2015 at 04:33:38AM +0200, Douglas Beonkey wrote: > > If I create a signal source block with a starting frequency of 1.2 > GHz, and in the block have a variable slider added to the frequency > (assume the variable can slide between 0 and 1000), i must move the > slider 120 or more

Re: [Discuss-gnuradio] A small error in benchmark_tx file

Hi Dave, Don't be sorry :) However, of you've modified the scripts yourself, there's no way for anyone but you to find out what goes wrong. Can you save your modifications somewhere else, and overwrite all potentially modified scripts with their original version? Ravi has a very similar case,

[Discuss-gnuradio] Linking .so files to OOT module

Hello everyone, I'm trying to create a source and sink block which will connect to a database to fetch and drop data. The interface to the database is created using shared libraries (.so files) that were defined by someone else, not us. I have included the header file, which contains all the

Re: [Discuss-gnuradio] A small error in benchmark_tx file

Hi Dave, it's monday, and most of us haven't gotten around answering emails from the weekend, so please accept my apologies for not having exploding enthusiasm when I saw your first reminder five hours after you posted your question ;) So, first of all: thanks for the bug report! It's always

Re: [Discuss-gnuradio] A small error in benchmark_tx file

Hi Dave, Firstly, please sign up and post to the GNU Radio mailing list via the official method, not the Ruby forum. GNU Radio has nothing to do with Ruby! Official GNU Radio mailing list sign-up link: https://lists.gnu.org/mailman/listinfo/discuss-gnuradio In regard to your question, make

Re: [Discuss-gnuradio] Throttle block form wav files

On 3 September 2015 at 17:04, Murray Thomson wrote: > > On 3 September 2015 at 16:43, Kevin Reid wrote: > >> On Sep 3, 2015, at 8:24, Murray Thomson >> wrote: >> >> > Even selecting source and sink from the audio card,

Re: [Discuss-gnuradio] Noob question 1

On 09/07/2015 02:19 PM, Henk wrote: My thoughts Ton, I just made the FM receiver Marcus advised and as discribed in tutorial 6. This week I will ask a few questions about the configuration of these blocks. Understanding is the key word for me. Thanks Henk It boils down to having an

Re: [Discuss-gnuradio] A small error in benchmark_tx file

Can anyone please give an answer for the above error? Thanks, Dave -- Posted via http://www.ruby-forum.com/. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio