Re: [Discuss-gnuradio] Delay block controlled by input

OK !! Thank you very much for the tips. Next week I will use it in my PC of the lab. ;) The delay is in the data, not in the modulated signal. And I insert the average between the previous and the next sample. Greetings 2014-10-08 14:53 GMT+02:00 Marcus Müller : > Hi, > > On 08.10.2014 14:38, C

Re: [Discuss-gnuradio] Delay block controlled by input

And a question. In: uint64_t gr::block::nitems_read ( unsigned int *which_input*) How I know wich_input? 2014-10-08 15:08 GMT+02:00 Carlos Alberto Ruiz Naranjo < carlosruiznara...@gmail.com>: > OK !! Thank you v

Re: [Discuss-gnuradio] GRC 3.6 / 802.11 a/g test signal

Ok fixed. Now giving correct results :) Ill try with your frame once more and hit you up later. Thanks for your amazing feedback Bastian. Best, Ernest -- View this message in context: http://gnuradio.4.n7.nabble.com/GRC-3-6-802-11-a-g-test-signal-tp50585p50690.html Sent from the GnuRadio m

Re: [Discuss-gnuradio] Using volk

On Tue, Oct 7, 2014 at 3:49 PM, Mostafa Alizadeh wrote: > Hello all, > > I wondered about volk. I want it to compute mean to peak value of a > complex array. How could I do this? > Besides, I really need to know is there any example of using volk? The > code itself, doesn't reflect input and outp

Re: [Discuss-gnuradio] Delay block controlled by input

Really the question is: How can I call gr::block::nitems_read (unsigned int *which_input*) from a block to know the nitems_read of another block? 2014-10-08 15:10 GMT+02:00 Carlos Alberto Ruiz Naranjo < carlosruiznara...@gmail.com>: > And a question. In: > > uint64_t >

Re: [Discuss-gnuradio] Delay block controlled by input

You call another_block->nitems_read(number) with number being the number of the input stream (ie. 0 for the first, 1 for the second and so on). Remember, GNU Radio is C++, and blocks are built as classes. Greetings, Marcus On 08.10.2014 15:24, Carlos Alberto Ruiz Naranjo wrote: > Really the quest

Re: [Discuss-gnuradio] Delay block controlled by input

On 10/08/2014 03:24 PM, Carlos Alberto Ruiz Naranjo wrote: > Really the question is: > > How can I call > gr::block::nitems_read( unsigned int/which_input/ ) > > from a block to know the nitems_read of another block? You call 'nitems_read()'? Not sure you should be ca

[Discuss-gnuradio] How to access UHD from within my own OOT block?

Dear all, In the Companion GUI I use the UHD source- and sink-blocks, together with my own OOT blocks. Now I want to control the UHD blocks from within my own blocks, for example changing the center frequency. So in my own block I would like to write something like: usrp->set_center_freq(w

Re: [Discuss-gnuradio] How to access UHD from within my own OOT block?

Hi Jeroen, the usrp blocks have public methods to do exactly that. It really looks like what you've proposed :) Not so long ago, Martin added support for doing things like that by sending messages or stream tags to the block, too. As you haven't found a starting point yet: Here's GNU Radio's off

Re: [Discuss-gnuradio] How to access UHD from within my own OOT block?

Regardless of the application, UHD or otherwise, this is not what you should be doing. Use the message interface for this, it is described on the gr-uhd manual page. M On 8 Oct 2014 16:02, "Boschma, J.J. (Jeroen)" wrote: > Dear all, > > > > In the Companion GUI I use the UHD source- and sink-bl

[Discuss-gnuradio] GNURadio Installation with Hydra

Dear all, I'm a beginner of GNURadio but I'm familiar with some basis of Linux when I use C++ & IT++. Currently I'm trying to test the Hydra-0.4 package for evaluation under the last ubuntu ver 14.04.1 32bit. During the installation of gnuradio-3.2.2, there is an error which I cannot find the solu

Re: [Discuss-gnuradio] GNURadio Installation with Hydra

Hello Jiayi, 3.2.2 is *very* ancient. In fact, it's older than my involvement with GNU Radio, and I think it will be very hard to find someone how's still using it, so asking for experience, I'm afraid, is not going to yield a lot of responses in 2014. Therefore, it will be nearly impossible to re

Re: [Discuss-gnuradio] CC encoder definition (variable_cc_encoder_def)

On Tue, Oct 7, 2014 at 12:08 PM, David Halls wrote: > > > From: trond...@trondeau.com [trond...@trondeau.com] on behalf of Tom > Rondeau [t...@trondeau.com] > Sent: 07 October 2014 16:27 > To: David Halls > Cc: discuss-gnuradio@gnu.org > Subject: Re: [Disc

Re: [Discuss-gnuradio] Packet Encoder-Decoder

I am seeing the same problem here while running some tests. Anyone else has any thoughts? Running gnuradio 3.7.5, installed with the build-gnuradio script on Ubuntu 14.04. Gnuradio On Tue, Oct 7, 2014 at 6:18 AM, Thanasis Balafoutis wrote: > Hi, > In the followning basic setup: > File Source (

Re: [Discuss-gnuradio] Packet Encoder-Decoder

Hi Thanasis, 1. The flow you showed could not have worked because Packet Decoder takes unpacked bytes. The graph should be: File Source -> Encoder -> Packed-to-Unpacked -> Decoder -> File Sink 2. The payload length defaults to 512 if you leave it at 0, so a short file won't fill a packet.

[Discuss-gnuradio] Saving PMTs as Python Dictionaries to .Mat File

I have a series of collected metadata files. I have taken both the gr_read_file_metadata.py and parse_file_metadata.py scripts and hacked them to my own needs. What I would like to do is convert the PMT to python dictionary (already done in the vanilla files) and save the dicitonary as a Matlab .ma

[Discuss-gnuradio] FEC gnuradio 3.7.6 error

Dear all, I am checking FEC Extended Encoder/Decoder in gnuradio-3.7.6 and would like to embed it in my OFDM transmission. First, I run the flowgraph below. It works and I can see how FEC improve the results. However, when I change some blocks, for example, using BPSK Mapper (as b

Re: [Discuss-gnuradio] Delay block controlled by input

I generate the signal from a file (1023 samples/s) to a file. My sampling clock drifts significantly :S - Picture one: Counter Clock 2 is correct but Counter Clock 1 no. Then I should use the second configuration, but it is not allowed because I have a loop, right? ​ I'll try the method you

Re: [Discuss-gnuradio] GRC 3.6 / 802.11 a/g test signal

On 10/07/2014 04:57 PM, Ernest Szczepaniak wrote: Nope, Any way to get it? Is it downloadable? Should be helpfull indeed. As far as I know it is not downloadable. You would have to extract (copy - paste) the data from the pdf. Bastian ___ Disc

Re: [Discuss-gnuradio] Gnuradio DCS Module

On 10/07/2014 07:16 PM, Jeff Long wrote: Martin, Some ideas inline ... hope some of this is useful. On 10/07/2014 03:30 PM, Martin Holst Swende wrote: Hi list, I am pretty new to Gnuradio / SDR, experimenting with a HackRF. As a startup experiment, I wanted to communicate with simple handheld

Re: [Discuss-gnuradio] GRC 3.6 / 802.11 a/g test signal

Ok. After couple of days trying to decode your frame i decided to check my receiver with real samples. Could it be possible that after demodulation (de-interleaving, de-convolutional, de-scrambling) im getting over 40x0's in correct positions (9 reserved bits, 16x0s in duration, correct pads) and s

Re: [Discuss-gnuradio] Using volk

Hi Mostafa, VOLK is but an accelerated Library of Vector Optimized Kernels. What you want is basically three operations: a) finding maximum absolute b) finding average absolute c) dividing these two values Now, looking closer at a) and b), one notices that both require the samples to be converted

Re: [Discuss-gnuradio] GRC 3.6 / 802.11 a/g test signal

On 10/08/2014 11:54 AM, Ernest Szczepaniak wrote: Ok. After couple of days trying to decode your frame i decided to check my receiver with real samples. Could it be possible that after demodulation (de-interleaving, de-convolutional, de-scrambling) im getting over 40x0's in correct positions (9 r

Re: [Discuss-gnuradio] Delay block controlled by input

Hello Carlos, On 08.10.2014 09:10, Carlos Alberto Ruiz Naranjo wrote: > I generate the signal from a file (1023 samples/s) to a file. My > sampling clock drifts significantly :S No. Unless I misunderstood you, you have a big misconception: "sampling clock" is *not* the rate at which your sample

Re: [Discuss-gnuradio] GRC 3.6 / 802.11 a/g test signal

On 10/08/2014 11:54 AM, Ernest Szczepaniak wrote: Ok. After couple of days trying to decode your frame i decided to check my receiver with real samples. Could it be possible that after demodulation (de-interleaving, de-convolutional, de-scrambling) im getting over 40x0's in correct positions (9 r

Re: [Discuss-gnuradio] GRC 3.6 / 802.11 a/g test signal

Got the pilot sequence but ill check it once more. I also got Annex L so not neccesary to post it but thanks. Ill check everything once more, according to L. -- View this message in context: http://gnuradio.4.n7.nabble.com/GRC-3-6-802-11-a-g-test-signal-tp50585p50678.html Sent from the GnuRadio

Re: [Discuss-gnuradio] Delay block controlled by input

Sorry, I have explained bad: S I have the signal saved in a file and 1023 samples are one second (in the real world). In the first graph I have two clocks (counters samples). When passing 102300 samples it increase 0.01 seconds. In the first watch this time controls the position of the satelli

Re: [Discuss-gnuradio] Delay block controlled by input

If you don't have hardware involved, you have no 'clock'. And as such, it can't drift. M On 10/08/2014 12:29 PM, Carlos Alberto Ruiz Naranjo wrote: > Sorry, I have explained bad: S > I have the signal saved in a file and 1023 samples are one second > (in the real world). > > In the first gra

Re: [Discuss-gnuradio] Delay block controlled by input

See also http://gnuradio.org/redmine/projects/gnuradio/wiki/FAQ#What-does-sample-rate-mean-in-GNU-Radio. M On 10/08/2014 01:18 PM, Martin Braun wrote: > If you don't have hardware involved, you have no 'clock'. And as such, > it can't drift. > > M > > On 10/08/2014 12:29 PM, Carlos Alberto Ruiz

Re: [Discuss-gnuradio] Delay block controlled by input

Yes, it is not a real time clock. This "clock" tracks the current time of the signal in GNURadio. clock2 and clock1 have a drift because the number of counted samples are different. For example, if it pass 1023 samples the delay block is entering the delay in signal time = 1 second. 1 second i

Re: [Discuss-gnuradio] Delay block controlled by input

In that case, just use nitems_read() [1] in your delay block to inherently calculate "simulated time". However, I'm a bit curious about the effects of using delay to do this: Because, as long as the satellite is approaching you, you're occasionally dropping samples, whereas you're inserting zeros

Re: [Discuss-gnuradio] Delay block controlled by input

If you're comparing real time (system clock) to your sample stream, you'll get jitter, not drift, using a throttle. Throttle maintains a sample rate over time, but operates on blocks, and also is running under a non-realtime operating system. If you're talking about drift between the clock on

Re: [Discuss-gnuradio] GRC 3.6 / 802.11 a/g test signal

So... After going deep into Annex L i found that my scrambler fails. Also MATLAB built-in scrambler gives wrong results. Could you pls check this code fragment? Asumme that we have 20 data bits to scramble. Initial scrambler state is [1 0 1 1 1 0 1] (bit nr 7 left side). scrambler_register=[1 0 1

Re: [Discuss-gnuradio] GRC 3.6 / 802.11 a/g test signal

On 08 Oct 2014, at 14:23, Ernest Szczepaniak wrote: > So... After going deep into Annex L i found that my scrambler fails. Also > MATLAB built-in scrambler gives wrong results. Could you pls check this code > fragment? > > Asumme that we have 20 data bits to scramble. Initial scrambler state is

Re: [Discuss-gnuradio] Delay block controlled by input

Delay Block is controlled by Satellite Orbit and Satellite Orbit by "simulated clock". The output of Satellite Orbit is the delay (samples). Can I know the nitems_read of Delay Block from other block (Satellite Orbit)? Maybe a solution is to introduce Orbit Satellite in Delay block, but this is re

Re: [Discuss-gnuradio] Delay block controlled by input

Hi, On 08.10.2014 14:38, Carlos Alberto Ruiz Naranjo wrote: > Delay Block is controlled by Satellite Orbit and Satellite Orbit by > "simulated clock". The output of Satellite Orbit is the delay (samples). > Can I know the nitems_read of Delay Block from other block (Satellite > Orbit)? Yes. It's a