Re: [Discuss-gnuradio] OFDM TX/RX PAPR

2018-03-29 Thread guillaume.tochou

How do you reduce the PAPR with existing block in GRC ?

I've tried with Scrambler->Encoder CCSDS->Interleaver but it doesn't 
seems to work. I'm still not having any signal at the output of the OFDM 
receiver.


Guillaume


Le 27/03/2018 à 11:58, Ron Economos a écrit :
Yes, I think the whitener does the trick. If you plot the PAPR of band 
limited white noise, it's pretty much the same curve.


Ron

On 03/27/2018 02:36 AM, Müller, Marcus (CEL) wrote:

Oooh, that's a nice plot!
This is way better than I would have anticipated. Can I attribute that
to awesome whitening properties of the code itself and following
scramblers/interleavers?

Marcus
On Tue, 2018-03-27 at 02:31 -0700, Ron Economos wrote:
CCDF (Complementary Cumulative Distribution Function) is often used 
to show PAPR probability. Here's what the GNU Radio DVB-T2 
transmitter looks like at 32K (27841 active) carriers with an 
without tone reservation PAPR reduction.


Ron
On 03/27/2018 02:09 AM, Müller, Marcus (CEL) wrote:

On Fri, 2018-03-23 at 14:21 -0700, Martin Braun wrote:

If you've
increased the number of carriers, PAPR also goes up (a bit).

Yep, by the same factor as you increase the number of carriers (proof
idea: time-symbol with worst PAPR is the discrete dirac over the 
vector
of FFT length N. That has a PAPR of N/1 = N if freq domain samples 
were

amplitude-limited to 1.)

The probability to hit a PAPR that bad is, however, limited.
Considering an M-PSK modulation on the N subcarriers. Then there's a
total of M^N possible time-domain OFDM symbols, but only M·N of these
are worst-PAPR, so
P(worst PAPR for N carriers) = M·N/M^N = N / M^(N-1)
assuming equally likely symbols. Since M^N pretty certainly grows
faster than N, your likelihood of ending up in the "worst PAPR"
scenario actually drops with N.

The story looks a bit different if you're not interested in the worst-
PAPR-symbol, but in all symbols that have a PAPR worse than some
threshold, e.g. 20dB. Especially for LTE, there's a lot of
simulative/monte carlo PAPR>threshold curves, as things like trading
clipping for amplifier efficiency plays a very commercially relevant
role there.

Best regards,

Marcus


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio



_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.



tx_ofdm.grc
Description: application/gnuradio-grc
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] OFDM TX/RX

2018-03-16 Thread guillaume.tochou

Hello all,

I want to make a flow graph for transmitting and receiving OFDM 
modulated data. To be precise, I want to do a LTE-M "like" 
transmission/reception, so I am trying to transmit data with a BW of 
1.08 MHz OFDM.
To do so, I use the following configuration : samp_rate = 1.92 MHz, fft 
length = 128, number of sub carriers = 72 , cp = 32


I modified the tx_ofdm.grc example file 
(/gnuradio/gr-digital/examples/ofdm/tx_ofdm.grc)
To summary, I change the occupied carriers : range(-36, -21) + 
range(-20, -7) + range(-6, 0) + range(1, 7) + range(8, 21) + range(22, 
37),) ; pilot carriers and symbols unchanged ; double the sync words to 
be equal to fft length.


The problem is at the output of the "Tag debug" I have just those 
messages :

INFO: Parser returned #f
INFO: Detected an invalid packet at item 1496
..
INFO: Parser returned #f
INFO: Detected an invalid packet at item 681901

And the spectrum isn't "stable" at 1.08 MHz BW.

What am I doing wrong ? How the sync words are determine ? Should I add 
pilot/symbol carriers ?



Best Regards and thanks by advance,

Guillaume Tochou





_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.



tx_ofdm.grc
Description: application/gnuradio-grc
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio