On Wed, Dec 11, 2013 at 06:52:30PM -0500, Marcus Leech wrote:
Just for fun I uninstalled everything and tried installing with
pybombs. However when it got to the step which builds
filter_swigPYTHON_wrap there was an issue:
[ 78%] Building CXX object
On Wed, Dec 11, 2013 at 04:15:11PM -0700, Henry Jin wrote:
I tried to use digital_bert_tx.py and digital_bert_rx.py to test the BER
performance of different modulations. The command I use is
./digital_bert_tx.py
--tx-freq=5.1e9 --tx-gain=30 -S 8 --mod-code=gray -m bpsk. The results for
BPSK
Dear All,
I need your help. May be any of you had such a problem before:
I use 'IEEE 802.11 a/g/p OFDM Transceiver' project, Ubuntu 13.04, GNURADIO 3.7
and (USRP N200 + XCVR 2450 + VERT2450 antenna).
I start the transmission using the first laptop and USRP N200 device by running
the
GNU Radio Companion v3.6.4-43-g6e5dfe1a
linux; GNU C++ version 4.6.3; Boost_104800; UHD_003.005.001-37-g21311276
USRP N210
Hello All !
I am observing following 3 cases for same transmitter. I ran each case
multiple times and reach to conclusion that only CASE 1 is working fine.
CASE 1:
First i
On Thu, Dec 12, 2013 at 03:54:29PM +0500, Maria Stevens wrote:
So, Only case 1 is working for me. I am not using any custom gnuradio-block in
my receiver. Major blocks in my demodulator chain consists of FIR filters,
gr_pfb_clock_sync_ccf and packet decoder along with some adders subtractors
On 12 Dec 2013, at 11:31, Nasi nesaz...@mail.ru wrote:
Meanwhile I use the second laptop and USRP N200 device as the receiver by
running the ./ofdm_rx.py. The error rate is very high.
So you receive some packets or none?
The problem is that when I change gain in the USRP sink nothing
Dear all,
In OFDM transmitter example there is Stream to Tagged Stream block with
packet length value 96. What it's mean? And whether the value claim specific
standard?
Thanks,
Ahmad___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
Meanwhile I use the second laptop and USRP N200 device as the receiver by
running the ./ofdm_rx.py. The error rate is very high.
So you receive some packets or none? Yes, I receive hopefully. But the packer
error rate is too high. I went through different configurations and gains. And
On Thu, Dec 12, 2013 at 08:27:19PM +0800, ZaInzAiN Jj wrote:
This is OFDM transmitter grc file
On Thursday, December 12, 2013 7:22 PM, ZaInzAiN Jj zain_zain...@yahoo.com
wrote:
Dear all,
In OFDM transmitter example there is Stream to Tagged Stream block with
packet length value 96.
On 12 Dec 2013, at 15:26, Nasi nesaz...@mail.ru wrote:
Yes, I receive hopefully. But the packer error rate is too high. I went
through different configurations and gains. And finally I see that the
problem is the transmission side. The gain does not have any influence on the
error rate.
Just to be sure: do you have the current version? (some weeks ago I normalized
the signal power to 1 without pushing updates of the flow graphs. That lead to
distorted signals. In that case, changing the gain does not help.) I
reinstalled it previous week, I guess on Saturday. Before it was
Hi,
I am trying to transmit 2x1 MISO OFDM. The two transmit USRPs are connected by
MIMO cable, and the USRP sink section of the .py file is:
self.uhd_usrp_sink_0_0_0 = uhd.usrp_sink(
device_addr=addr0=192.168.10.2,addr1=192.168.10.7,
stream_args=uhd.stream_args(
The VOLK working group had a call earlier today. Agenda and summary
are here: http://gnuradio.org/redmine/projects/gnuradio/wiki/Call20131212
We'll likely have our next call late January or February time-frame.
There's a semi-open question about what kind of stats we should
collect. Tim added
The trigger of scope sink is not for XY mode.
If you want to view two complex signal simultaneous, then it seems you need
two scope sinks.
If you dont see anything, maybe you have a block driving it that doesnt
output anything until some condition is met.
On Wed, Dec 11, 2013 at 10:53 AM,
On Thu, Dec 12, 2013 at 3:11 PM, West, Nathan
n...@ostatemail.okstate.eduwrote:
The VOLK working group had a call earlier today. Agenda and summary
are here: http://gnuradio.org/redmine/projects/gnuradio/wiki/Call20131212
We'll likely have our next call late January or February time-frame.
On 12/12/2013 04:01 PM, Douglas Geiger wrote:
On Thu, Dec 12, 2013 at 3:11 PM, West, Nathan
n...@ostatemail.okstate.edu mailto:n...@ostatemail.okstate.edu wrote:
The VOLK working group had a call earlier today. Agenda and summary
are here:
On Thu, Dec 12, 2013 at 4:07 PM, Tim tim.oshea...@gmail.com wrote:
On 12/12/2013 04:01 PM, Douglas Geiger wrote:
On Thu, Dec 12, 2013 at 3:11 PM, West, Nathan n...@ostatemail.okstate.edu
wrote:
The VOLK working group had a call earlier today. Agenda and summary
are here:
Thanks for your reply, Martin.
I can understand your point that the estimated SNR in the script
corresponds to ES/N0, which should be twice of Eb/N0 in the case of qpsk.
You do raise a good question: why the BER is shown as 10^(-11)? I rechecked
the script. The default bit rate is 250e3, which
18 matches
Mail list logo
