Hi,
I am referring the built in example of gnuradio companion ( rx_ofdm.grc).
In which I replace random source with usrp source.
on Transmetter side I am sending some bits and in receiver flow graph
(rx_ofdm ) I am facing problem where I have to attach file sink to get
these bits.
I attached *
Hi Muhammad,
sadly, it's not very clear what you're asking about.
* Which flow graph are you referring to?
* What is your precise problem, and what have you tried to solve it so
far? How can we help you with that?
Best regards,
Marcus
On 02/22/2017 02:05 PM, MUHAMMAD AHMAD wrote:
> How can I r
How can I receive bits using file sink in ofdm receiver.
where I have to connect file sink in flow graph of ofdm receiver?
either bits repack block output can give bits?
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/ma
Hi, thank you for your response.
In fact, I still have the same error:
FATAL: Missing a required length tag on port 0 at item #0
thread[thread-per-block[21]: ]: Missing length
tag.
and UOO
I put the usrp sink and usrp source 's sample rate to 1M.
What is the suitable sampling rate t
On 06/30/2014 03:20 PM, Wafa Elhajhmida wrote:
> FATAL: Missing a required length tag on port 0 at item #0
> thread[thread-per-block[21]: ]: Missing length tag.
Add a stream to tagged stream converter.
M
___
Discuss-gnuradio mailing list
Discuss-gnu
On 06/30/2014 09:20 AM, Wafa Elhajhmida wrote:
> Hi,
>
> I implemented OFDM receiver on USRP E110 using the OFDM receiver in
> examples in gnuradio's files 3.7
>
> and I added to it a chain to create OFDM transmitter: random source, OFDM
> transmitter, channel model, throttle, USRP sink
>
> But
Hi,
I implemented OFDM receiver on USRP E110 using the OFDM receiver in
examples in gnuradio's files 3.7
and I added to it a chain to create OFDM transmitter: random source, OFDM
transmitter, channel model, throttle, USRP sink
But when I executed the flow graph. It generated "UO
On Mon, Jan 17, 2011 at 7:58 PM, Guanbo wrote:
>
> Hi,
>
> I feel like the output of coarse frequency offset is very inaccurate. Or
> probably it is not directly related.
>
> For best test, I tried higher resolution of subcarrier bandwidth by
> selecting the large FFT length, high Interp/decim rat
Hi,
I feel like the output of coarse frequency offset is very inaccurate. Or
probably it is not directly related.
For best test, I tried higher resolution of subcarrier bandwidth by
selecting the large FFT length, high Interp/decim rate,
as follows:
@TX: $ sudo python benchmark_ofdm_tx_new.py
Thanks Tom. I tried to see how much the carrier frequency offset would be.
As you suggested above, I output the coarse freq offset bins, which was
similar as Srinivas's result. It is constant "-2".
Does it means the carrier offset can be computed as: ADC rate /( Decim_rate
* FFT_len) * 2 ?
If
On Wed, Jan 12, 2011 at 7:36 PM, Guanbo wrote:
>
> Hi, Tom
>
> I am not quite understand the ofdm_sync_xx.cc in python/gnuradio/blks2impl/.
>
> What is the difference between frequency synchronization and carrier
> frequency offset.
> Why we have to do the timing and frequency synchronization befo
Hi, Tom
I am not quite understand the ofdm_sync_xx.cc in python/gnuradio/blks2impl/.
What is the difference between frequency synchronization and carrier
frequency offset.
Why we have to do the timing and frequency synchronization before it?
Also,
Thanks,
Guanbo
Tom Rondeau wrote:
>
> On
Hi, Tom
I am not quite understand the ofdm_sync_xx.cc in python/gnuradio/blks2impl/.
What is the difference between frequency synchronization and carrier
frequency offset.
Why we have to do the timing and frequency synchronization before it?
Thanks,
Guanbo
Tom Rondeau wrote:
>
> On Tue, Feb
Sorry for bringing up an old thread. I was having the same problem of not
receiving packets using benchmark_ofdm_* and changing the receiver frequency
to tune to the transmitter frequency indeed solved the problem.
However, if I have to manually do it every time, I don't see how I can get
ofdm tun
On 2/20/2010 7:43 PM, Srinivas wrote:
Hi Tom,
I tried increasing the bandwidth of the filter and also tried changing
the window type to KAISER, but it didn't improve on the offset error.
I am getting a constant frequency offset value "-10". Currently, I am
just compensating for the offset at
Hi Tom,
I tried increasing the bandwidth of the filter and also tried changing the
window type to KAISER, but it didn't improve on the offset error. I am
getting a constant frequency offset value "-10". Currently, I am just
compensating for the offset at the receiver or specifying a minimum BW to
On Thu, Feb 18, 2010 at 12:49 AM, Srinivas wrote:
> Hi Tom, Matt
>
> replied inline:
>
> On Wed, Feb 17, 2010 at 10:26 AM, Tom Rondeau
> wrote:
>>
>> On Tue, Feb 16, 2010 at 5:45 PM, Srinivas wrote:
>> > Matt,
>> >
>> > Thanks for verifying the data rate calculation!
>> >
>> > I tried the other
Hi Tom, Matt
replied inline:
On Wed, Feb 17, 2010 at 10:26 AM, Tom Rondeau wrote:
> On Tue, Feb 16, 2010 at 5:45 PM, Srinivas wrote:
> > Matt,
> >
> > Thanks for verifying the data rate calculation!
> >
> > I tried the other solutions that you suggested, namely,
> >
> > - increasing the data ra
On Tue, Feb 16, 2010 at 5:45 PM, Srinivas wrote:
> Matt,
>
> Thanks for verifying the data rate calculation!
>
> I tried the other solutions that you suggested, namely,
>
> - increasing the data rate by a factor of 2 or 4
> It works.
>
> - modifying the OFDM code to widen the search range - How do
On 02/16/2010 02:45 PM, Srinivas wrote:
Matt,
Thanks for verifying the data rate calculation!
I tried the other solutions that you suggested, namely,
*- increasing the data rate by a factor of 2 or 4
*It works.
*
- modifying the OFDM code to widen the search range* - How do I widen
the search
Matt,
Thanks for verifying the data rate calculation!
I tried the other solutions that you suggested, namely,
*- increasing the data rate by a factor of 2 or 4
*It works.
*
- modifying the OFDM code to widen the search range* - How do I widen the
search range ?
Should I be looking in the "ofdm_s
That formula will give you the number of occupied tones per second. You
need to multiply by the number of bits per tone to get bps. If you are
using BPSK, multiply by 1. If using QPSK, you'll need to multiply by 3,
8PSK by 3, etc.
I meant to say:
BPSK - multiply by 1
QPSK - mult by 2 (not 3
On 02/12/2010 03:53 PM, Srinivas wrote:
Matt,
There was a frequency offset of ~30 KHz at the Rx w.r.t Tx so I
compensated for it and it worked!.
The settings I am using is as follows:
./benchmark_ofdm_tx.py -f 2.45G --tx-amplitude 0.9 -M 8 -s 200 -m bpsk
--fft-length=512 --occupied-tones=80 -i
Matt,
There was a frequency offset of ~30 KHz at the Rx w.r.t Tx so I compensated
for it and it worked!.
The settings I am using is as follows:
./benchmark_ofdm_tx.py -f 2.45G --tx-amplitude 0.9 -M 8 -s 200 -m bpsk
--fft-length=512 --occupied-tones=80 -i 64 --tx-gain=10 --cp-length=128
./benchma
On 02/11/2010 04:45 PM, Srinivas wrote:
Hi All,
I have 2 pairs of USRP2s with GNURadio-3.2 installed on their hosts. On
one pair I am able to successfully run OFDM (benchmark_ofdm_tx & rx)
with almost 95+% packet success rate. However on the other pair I am not
receiving even 1 packet!
I am usi
25 matches
Mail list logo
