WARP Project Forums - Wireless Open-Access Research Platform

You are not logged in.

#1 2014-Aug-27 20:39:16

nudu
Member
Registered: 2010-Jun-25
Posts: 51

Support wider bandwidth for WARPLAB

https://warpproject.org/forums/viewtopic.php?id=2255

As mentioned in the above thread: "The 40MHz bandwidth limit comes from the MAX2829 transceiver bandwidth".



The current design only support 20 MHz bandwidth, does it means doubling the bandwidth to 40MHz is still possible but not to 80Mhz?

My objective is to have one WARP transmit at 40MHz bandwidth (current design is on 20MHz) and another WARP listen at this 40MHz.

1. The current ADC/DAC seems to be at 40MHz, do I need to change it to sampling rate of 80MHz to support this 40MHz bandwidth?

2. What other places I need to change?

Thanks a lot!

Offline

 

#2 2014-Aug-27 21:04:57

murphpo
Administrator
From: Mango Communications
Registered: 2006-Jul-03
Posts: 5159

Re: Support wider bandwidth for WARPLAB

The WARPLab Reference Design runs the ADCs and DACs at 40MSps. There are separate analog converters for the I and Q paths of the complex baseband Tx/Rx signals. This design gives 40MHz bandwidth centered at 0Hz (-20MHz to +20MHz), the full analog bandwidth of the MAX2829.

Offline

 

#3 2014-Aug-27 21:26:54

nudu
Member
Registered: 2010-Jun-25
Posts: 51

Re: Support wider bandwidth for WARPLAB

Thanks.

Do you mean that I don't need to change anything and the current design (7.40) already supports 40MHz bandwidth transmission  and reception?


murphpo wrote:

The WARPLab Reference Design runs the ADCs and DACs at 40MSps. There are separate analog converters for the I and Q paths of the complex baseband Tx/Rx signals. This design gives 40MHz bandwidth centered at 0Hz (-20MHz to +20MHz), the full analog bandwidth of the MAX2829.

Offline

 

#4 2014-Aug-28 08:31:28

welsh
Administrator
From: Mango Communications
Registered: 2013-May-15
Posts: 612

Re: Support wider bandwidth for WARPLAB

Correct.  See complex sampling for more information on the theory behind this.

Offline

 

#5 2014-Aug-29 16:01:51

nudu
Member
Registered: 2010-Jun-25
Posts: 51

Re: Support wider bandwidth for WARPLAB

I still have two questions here. I can found several other threads talking about using 40MHz bandwidth but there is no detail how to do this.

1. wl_interfaceCmd(nodes,'RF_ALL','channel',2.4,11); 

In warplab 7.4 matlab code, there is the above line to set channel. Once I select the channel, only 20Mhz is used (Am I correct?). What should I change here to enable the receiver to listen on 40MHz??
Can I listen on two channels like 10, 11 at the same time?


2. At the transmitter side, I also need to built the packet which occupys all the 40Mhz bandwidth, right?
In wl_example_siso_txrx_nodeSync.m, there is a packet built with short training symbol +  sine-wave payload.

Does this short preamble occupy 20MHz or 40MHz? If it only occupy 20MHz, is it because the two 'zeros(32,1)' before and after 'shortSymbol_freq'? 
If I make 'zeros(32,1)' no-zero , then the short preamble occupys  the whole 40Mhz now?

Thanks and please help!

matlab code from WARPLAB example:

shortSymbol_freq = [0 0 0 0 0 0 0 0 1+1i 0 0 0 -1+1i 0  0 0 -1-1i 0 0 0 1-1i 0 0 0 -1-1i 0 0 0 1-1i 0 0 0 0 0 0 0 1-1i 0 0 0 -1-1i 0 0 0 1-1i 0 0 0 -1-1i 0 0 0 -1+1i 0 0 0 1+1i 0 0 0 0 0 0 0].';
shortSymbol_freq = [zeros(32,1);shortSymbol_freq;zeros(32,1)];
shortSymbol_time = ifft(fftshift(shortSymbol_freq));


welsh wrote:

Correct.  See complex sampling for more information on the theory behind this.

Offline

 

#6 2014-Aug-31 10:53:24

murphpo
Administrator
From: Mango Communications
Registered: 2006-Jul-03
Posts: 5159

Re: Support wider bandwidth for WARPLAB

In warplab 7.4 matlab code, there is the above line to set channel. Once I select the channel, only 20Mhz is used (Am I correct?). What should I change here to enable the receiver to listen on 40MHz??

Setting the channel only sets the center frequency of the Tx/Rx mixers. The bandwidth used at that center frequency is defined by:
  -Tx: your baseband waveform -> Tx LPF (configured via the tx_lpf_corn_freq command)
  -Rx: Rx LPF (configured via the rx_lpf_corn_freq command)

Offline

 

#7 2014-Sep-01 19:58:33

nudu
Member
Registered: 2010-Jun-25
Posts: 51

Re: Support wider bandwidth for WARPLAB

Thanks a lot. I have another question:

In the matlab example, short training symbol is made as below:

Does this short training symbol occupy the whole 20Mhz? How can I know this?
If I want to make a new one occupies 40Mhz, I should change the zeros(32,1) to no-zero values?

shortSymbol_freq = [0 0 0 0 0 0 0 0 1+1i 0 0 0 -1+1i 0  0 0 -1-1i 0 0 0 1-1i 0 0 0 -1-1i 0 0 0 1-1i 0 0 0 0 0 0 0 1-1i 0 0 0 -1-1i 0 0 0 1-1i 0 0 0 -1-1i 0 0 0 -1+1i 0 0 0 1+1i 0 0 0 0 0 0 0].';
shortSymbol_freq = [zeros(32,1);shortSymbol_freq;zeros(32,1)];
shortSymbol_time = ifft(fftshift(shortSymbol_freq));



murphpo wrote:

In warplab 7.4 matlab code, there is the above line to set channel. Once I select the channel, only 20Mhz is used (Am I correct?). What should I change here to enable the receiver to listen on 40MHz??

Setting the channel only sets the center frequency of the Tx/Rx mixers. The bandwidth used at that center frequency is defined by:
  -Tx: your baseband waveform -> Tx LPF (configured via the tx_lpf_corn_freq command)
  -Rx: Rx LPF (configured via the rx_lpf_corn_freq command)

Last edited by nudu (2014-Sep-02 19:04:42)

Offline

 

#8 2014-Sep-02 22:10:57

murphpo
Administrator
From: Mango Communications
Registered: 2006-Jul-03
Posts: 5159

Re: Support wider bandwidth for WARPLAB

The code above defines a signal in the frequency domain, then translates it into the time domain. This particular signal is the STS from the 802.11 spec, which is defined by 12 (of 64) non-zero subcarriers in 20MHz. The code here sets 12 values, then pads the frequency domain representation with 64 extra zeros before taking the IFFT. This is a shortcut to 2x interpolation, resulting in a time series that, when sampled at 40MSps, will be the 802.11 STS.

The occupied bandwidth is determined by the time series representation of your signal and the actual sampling rate. It's important you understand the basic operations above - this is pure DSP, not WARPLab-specific processing. You will have much better success using WARPLab with a solid signal processing foundation.

Offline

 

Board footer