Re: [Discuss-gnuradio] Question regarding correlating output and IQ samples in a reciever

2016-01-31 Thread Marcus Müller
Hi Abhinav, as I said: a transmission with only "on" symbols will have much power, but one with only "offs" will have very little. So I'd propose you just measure things that have as many ons as offs. Be a little creative :) Best regards, Marcus On 01/30/2016 07:39 PM, abhinav narain wrote: > Hi

Re: [Discuss-gnuradio] Question regarding correlating output and IQ samples in a reciever

2016-01-30 Thread abhinav narain
Hi Marcus, > > It applies, but you must be aware of the fact that transmissions have a > different ratio of "on" symbols and "off" symbols have different > energy/power. So without knowing how many ons and offs you were sending, > that number is pretty meaningless. > Thanks for pointing out this

Re: [Discuss-gnuradio] Question regarding correlating output and IQ samples in a reciever

2016-01-30 Thread Marcus Müller
Hi Abhinav, > I don't think OOK is constant power modulation, but I suppose S+N/N should still apply on it. It applies, but you must be aware of the fact that transmissions have a different ratio of "on" symbols and "off" symbols have different energy/power. So without knowing how many ons and off

Re: [Discuss-gnuradio] Question regarding correlating output and IQ samples in a reciever

2016-01-29 Thread abhinav narain
Hi Marcus, > >> > I am simply doing OOK. > > >> Generally, [image: $\frac{S+N}{N}$] is only really a useful measure if >> you either have >> >>1. a constant power modulation (e.g. PSK), or >>2. whiten your over-the-air bits sufficiently (using *coding*), so >>that for (stochastically s

Re: [Discuss-gnuradio] Question regarding correlating output and IQ samples in a reciever

2016-01-28 Thread Marcus Müller
Hi Abhinav, On 01/28/2016 04:32 AM, abhinav narain wrote: > Hi Marcus, > > timing offset estimate) that your symbols have duration of > 2.236472 samples and start with a sample offset of 114.060072; I > don't see how knowing that would map the end of a preamble to any > "exact" sa

Re: [Discuss-gnuradio] Question regarding correlating output and IQ samples in a reciever

2016-01-27 Thread abhinav narain
Hi Marcus, timing offset estimate) that your symbols have duration of 2.236472 samples > and start with a sample offset of 114.060072; I don't see how knowing that > would map the end of a preamble to any "exact" sample. > If I understand this, it is not straightforward to find the end of the pre

Re: [Discuss-gnuradio] Question regarding correlating output and IQ samples in a reciever

2016-01-27 Thread Marcus Müller
Hi Abhinav, On 01/27/2016 03:17 AM, abhinav narain wrote: > Hi Marcus, > I want the exact end of the preambles IQ samples, so that I can chop > it off from my trace and also find the exact locations where my bits > (transmitted sparsely) are. I want to calculate the SNR for the > decoder. So, if

Re: [Discuss-gnuradio] Question regarding correlating output and IQ samples in a reciever

2016-01-26 Thread abhinav narain
Hi Marcus, I want the exact end of the preambles IQ samples, so that I can chop it off from my trace and also find the exact locations where my bits (transmitted sparsely) are. I want to calculate the SNR for the decoder. So, if I know the samples exactly corresponding to data bits, I can extract t

Re: [Discuss-gnuradio] Question regarding correlating output and IQ samples in a reciever

2016-01-26 Thread Marcus Müller
Hi Abhinav, point of timing recovery like you do it is that there's no IQ samples that *exactly and reliably* correspond to the symbol timing; that's why you need timing recovery. The question here is: what do you actually need? The IQ samples before timing recovery aren't useful to the decoder.

Re: [Discuss-gnuradio] Question regarding correlating output and IQ samples in a reciever

2016-01-25 Thread abhinav narain
Hi All, My problem is that above calculation sort of works, and isn't it exact. I have the following preable of 32 bits [1,0,1,0,1,1,0,0,1,1,0,1,1,1,0,1,1,0,1,0,0,1,1,0,0,1,1,1,0,1,0,1]. This can be seen in badpreamble.png, where for some reason I have trailing 0s or noise and the start of preambl