I wonder if there is any one successfully running OFDM on USRP2, what
are
the command parameters you are using and if there is any modification in
the
code, can you let me know.
I have gnuradio 3.2.2 installed on Ubintu 9.10 and I’m using USRP2s
with XCVR2450 daughterboards.
I tried your example but I changed the interpolation to correspond to
the decimation at the receiver:
Thanks Veljko, Did you do any modification on the gnuradio 3.2.2 code?
(Because at my side the interpolation/decimation was not the problem, I
forgot to change the value in the email)
Unfortunately, I can’t offer a solution at this stage. However, I had
similar error messages a few days ago. I thought perhaps these python
scripts were to be used exclusively for the original USRPs, though I
think in one or two posts I have seen, people mentioned successfully
running them for USRP2s.
You can try with the transmitter only first and usrp2_fft.py on the
other end, just to see if there’s something getting transmitted and if
it looks like OFDM.
Actually, the problems I had were not with the OFDM case, but just
benchmark_tx.py and benchmark_rx.py. Are similar modifications necessary
for those scripts?
Ian.
Hi,
The example provided with the gnuradio codebase requires small
modifications in order to work with USRP2. You can try with the
modifications I made:
You can try with the transmitter only first and usrp2_fft.py on the
other end, just to see if there’s something getting transmitted and if
it looks like OFDM.
Hi,
We did try the below command on two USRP2s coneected via a SMA Cable
(Tx-Rx)
with freq = 25M however it returned the following error on both sides
At Rx side it shows like the below -
[root@GNURADIO1 ofdm]# ./benchmark_ofdm_rx.py -f 25M -d 256
–fft-length=64
–occupied-tones=32 --cp-length=4
usrp: failed to find usrp[0]
Traceback (most recent call last):
File “./benchmark_ofdm_rx.py”, line 210, in
main()
File “./benchmark_ofdm_rx.py”, line 199, in main
tb = my_top_block(rx_callback, options)
File “./benchmark_ofdm_rx.py”, line 51, in init
self._setup_usrp_source()
File “./benchmark_ofdm_rx.py”, line 70, in _setup_usrp_source
fusb_nblocks=self._fusb_nblocks)
File “/usr/lib/python2.6/site-packages/gnuradio/usrp/usrp_swig.py”,
line
1699, in source_c
return _usrp_swig.source_c(*args, **kwargs)
RuntimeError: can’t open usrp
At Tx side -
root@gnu2 ofdm]# ./benchmark_ofdm_tx.py -f 25M -i 512 --fft-length=64
–occupied-tones=32 --cp-length=4
usrp: failed to find usrp[0]
Traceback (most recent call last):
File “./benchmark_ofdm_tx.py”, line 217, in
main()
File “./benchmark_ofdm_tx.py”, line 190, in main
tb = my_top_block(options)
File “./benchmark_ofdm_tx.py”, line 51, in init
self._setup_usrp_sink()
File “./benchmark_ofdm_tx.py”, line 66, in _setup_usrp_sink
fusb_nblocks=self._fusb_nblocks)
File
“/usr/local/lib/python2.5/site-packages/gnuradio/usrp/usrp_swig.py”,
line 2415, in sink_c
return _usrp_swig.sink_c(*args, **kwargs)
RuntimeError: can’t open usrp
May we request somebody to support us at the earliest to resolve the
above
issue with either software or hardware .
Traceback (most recent call last):
return _usrp_swig.source_c(*args, **kwargs)
tb = my_top_block(options)
issue with either software or hardware .
Thanks again,
Anupama
This is because you do not have the right permissions set to talk to
the USRP2 as a non-root user. See the USRP2 FAQs on the GNU Radio web
page for how to fix this.
Hi Tom ,
Thanks , we did try the updated script from Veljko . It works though we
have
missing packets after a while ( as suggested in the forum we would play
with
the interpolation and decimation ) though the 2 USRP2s are directly
connected .
We are still probing into the permissions issue as indicated though we
ran
with root permissions
( may be not in totality) , would keep posted on the later if we find
something on the same
Hi Tom,
In our case, even with script from Veljko, the OFDM receiver doesn’t
show
any thing. And we always see “usrp2: failed to enable realtime
scheduling”.
Do you think that will cause problem?
the command parameters you are using and if there is any modification in the
code, can you let me know.
Thanks,
Bin
The ‘S’ appear because you’re missing packets. Using the interpolation
and decimation rates you specified shouldn’t be taxi/ng your CPU,
which is a common cause of these problems. Are you running the USRP2
through a switch or is it directly connected?
The “time out” occurs when the receiver sees the preamble symbol of
the OFDM stream but nothing else. So what is probably happening is
that you get some of the symbols through, including the preamble
symbol, but you’re dropping other packets (causing the Ses), which
will trigger the “time out” message.
On Thu, Feb 04, 2010 at 07:25:47AM -0600, Tom R. wrote:
No, that message is just telling you that you don’t have permissions
to run it at the highest priority. It means you won’t be able to run
as fast, but that shouldn’t be the cause of your problems.
Tom
To enable real-time scheduling (highly recommended), do this:
Ensure that you are in the “usrp” group, and then add
this line to the end of /etc/security/limits.conf:
@usrp - rtprio 50
Log out, then back in, and the message should go away.
I have been inactive on this for some time due to other issues with my
USRP2s. However, I have been able to look into this again now, with
Veljko’s modified code. I run as root, and also had the realtime
scheduling enabled, however on the receive side I see nothing until the
transmitter stops transmitting, at which time I see timeout.
This seems to be the same problem that Bin had (except without the
realtime scheduling issue). Bin, did you end up resolving this issue?
Hi Tom,
In our case, even with script from Veljko, the OFDM receiver doesn’t show
any thing. And we always see “usrp2: failed to enable realtime scheduling”.
Do you think that will cause problem?
Thanks,
Bin
No, that message is just telling you that you don’t have permissions
to run it at the highest priority. It means you won’t be able to run
as fast, but that shouldn’t be the cause of your problems.
Tom
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.