discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] benchmark_tx and rx : too many FALSE packet


From: Nikos Balkanas
Subject: Re: [Discuss-gnuradio] benchmark_tx and rx : too many FALSE packet
Date: Mon, 14 Mar 2016 04:16:33 +0200

Hi,

Seems to me you have to tune in to a qam transmission to run your tests. The difficulty is finding one in your area....

BR,
Nikos

On Mon, Mar 14, 2016 at 4:05 AM, Nikos Balkanas <address@hidden> wrote:
Hi,

The narrowband gave me nothing of statistics or your messages, just messages for connecting to x300 and RFNoC. Let it run for ~5':

No gain specified.
Setting gain to 18.750000 (from [0.000000, 37.500000])
-- [0/Radio_0] _resolve_port_def()
-- [0/Radio_0] item type: sc16
-- [0/Radio_0] vector length: 0
-- [0/Radio_0] packet size: 0
-- [RX Streamer] creating rx stream recv_buff_size=33554432
-- [RX Streamer] data_sid = 00:08>02:30 actual recv_buff_size = 33554432
-- [0/Radio_0] radio_ctrl::set_destination()
-- Setting sid to 2.48>0.8
-- [RX Streamer] spp == 364
-- [RX Streamer] Flow Control Window = 20515, Flow Control Handler Window = 641
-- [0/Radio_0] radio_ctrl::configure_flow_control_out()20515
-- [RX Terminator 0] rx_stream_terminator::set_rx_streamer() 1
-- [0/Radio_0] radio_ctrl::set_rx_streamer() 1
-- [Device3] updating RX streamer to RX Terminator 0
-- New tick_rate == 2e+08 New samp_rate == 200000 New scaling == 3.05187e-05


^C-- [RX Terminator 0] rx_stream_terminator::~rx_stream_terminator()
-- [RX Terminator 0] rx_stream_terminator::set_rx_streamer() 0
-- [0/Radio_0] radio_ctrl::set_rx_streamer() 0

The ofdm complained about the S 8 argument and then erred on unknown key "qam"

BR,
Nikos

On Mon, Mar 14, 2016 at 3:51 AM, SangHyuk Kim <address@hidden> wrote:
Dear, Nikos.

I want to check both of them.

Thanks!

2016-03-14 10:45 GMT+09:00 Nikos Balkanas <address@hidden>:
Hi Kim,

I can only test the benchmark_rx.py with my X300 (don't have transmitters connected)
I can find 2 benchmark_rx.py in my gnuradio-3.7.9.1:
The first is under examples/ofdm and the other under examples/narrowband
Which one do you need tested?

BR,
Nikos

On Mon, Mar 14, 2016 at 2:04 AM, SangHyuk Kim <address@hidden> wrote:
Could anyone try to this example commend ?

example code location = gnuradio/gr-digital/example/narrowband
Tx)
./benchmark_tx.py -f 1.5G -m qam -S 8
Rx)
./benchmark_rx.py -f 1.5G -m qam -S 8

Thanks.

2016-03-13 18:57 GMT+09:00 SangHyuk Kim <address@hidden>:
Dear Nikos.

the value 'ok' returns 'FALSE' as results of crc_check.

so, I think packet was corrupted.

It happened only some modulation using high bits per symbol (QAM, PSK)

Thanks

2016-03-13 18:41 GMT+09:00 Nikos Balkanas <address@hidden>:
Have you inspected the packets and verified them to be corrupt?

BR
Nikos​

On Sun, Mar 13, 2016 at 10:22 AM, SangHyuk Kim <address@hidden> wrote:
Hi all.

I'm using benchmark_tx(rx).py example

I experimented variety modulation schemes and GMSK, BPSK, QPSK modulation worked well

However, when I used QAM modulation, most of received packet were corrupted (FALSE)

ENV)
both TX and RX uses USRP N210 with ANT500 and CBX 40MHz
distance between TX and RX is shorter than 3m

TX)
./benchmark_tx.py -f 1.5G -m qam -S 8 --tx-gain=30

RX)
./benchmark_rx.py -f 1.5G -m qam -S 8

RESULTS ON RX)
ok = FALSE  pktno = 1  n_rcvd = 1  n_right = 0
ok = FALSE  pktno = 2  n_rcvd = 2  n_right = 0
ok = FALSE  pktno = 3  n_rcvd = 3  n_right = 0
...
ok = TRUE  pktno = N  n_rcvd = N  n_right = 1
...

Is this normal case of qam modulation ?
How can I get more TRUE packet using QAM modulation ?

Thanks.

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





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






reply via email to

[Prev in Thread] Current Thread [Next in Thread]