GRC + N210 + RFX2200 + UHD not working

GNU Radio
1

I’m using grc to generate some extremely simple flowgraphs but I’m
seeing
very odd performance. Any idea why I can’t seem to get this combination
to
work? I have had success with a GRC + USRP2 + WBX + UHD, anybody know
why
I’m having issues here?

When I create a flowgraph directly to a null sink (null.png) I receive
the
following error:

Generating: “/home/pwilliams/gnuradio_test/video_tx/top_block.py”

Executing: “/home/pwilliams/gnuradio_test/video_tx/top_block.py”

linux; GNU C++ version 4.4.1; Boost_103800;
UHD_002.20110219191607.c912463

Current recv sock buff size: 50000000 bytes

Warning:
error in pthread_setschedparam
Failed to set thread priority 0.5 (realtime):
Performance may be negatively affected.
See the general application notes.

Warning:
error in pthread_setschedparam
Failed to set thread priority 0.5 (realtime):
Performance may be negatively affected.
See the general application notes.
mboard0 MIMO master

Warning:
error in pthread_setschedparam
Failed to set thread priority 0.5 (realtime):
Performance may be negatively affected.
See the general application notes.
UHD source block got error code 0x1
gr_block_executor: source <gr_block uhd single_usrp source (2)> produced
no
output. We’re marking it DONE.

When I create a flowgraph directly to a fftp sink (fft.png) it just
silently
exits with no errors:

Generating: “/home/pwilliams/gnuradio_test/video_tx/top_block.py”

Executing: “/home/pwilliams/gnuradio_test/video_tx/top_block.py”

linux; GNU C++ version 4.4.1; Boost_103800;
UHD_002.20110219191607.c912463

Current recv sock buff size: 50000000 bytes

Warning:
error in pthread_setschedparam
Failed to set thread priority 0.5 (realtime):
Performance may be negatively affected.
See the general application notes.

Warning:
error in pthread_setschedparam
Failed to set thread priority 0.5 (realtime):
Performance may be negatively affected.
See the general application notes.
mboard0 MIMO master

Warning:
error in pthread_setschedparam
Failed to set thread priority 0.5 (realtime):
Performance may be negatively affected.
See the general application notes.

2

On 02/24/2011 09:43 PM, Phelps W. wrote:

I’m using grc to generate some extremely simple flowgraphs but I’m seeing
very odd performance. Any idea why I can’t seem to get this combination to
work? I have had success with a GRC + USRP2 + WBX + UHD, anybody know why
I’m having issues here?

Are you saying that if you run the same flow graph, host pc, ethernet
port, and software install on the USRP2 + WBX, you do not see this
problem?

I am confused about the one hardware not working while the other does,
because its functionally identical. Just wondering if we can isolate
this problem to a particular machine, software install, etc… instead.

UHD source block got error code 0x1
gr_block_executor: source <gr_block uhd single_usrp source (2)> produced no
output. We’re marking it DONE.

This is the call to recv() on the udp socket timing out. Either data
isnt coming over the ethernet cable for some reason recv()/select()
error-ed.

In any case, do you mind trying the next branch?

In the uhd repo:
git remote update
git branch --track next origin/next
git checkout next
cd host/build && make install…

and for gnuradio
git remote add jblum git://gnuradio.org/jblum.git
git remote update
git branch --track gr_uhd_next jblum/gr_uhd_next
git checkout gr_uhd_next
make install…

-josh

3

Just a thought: I see the same warnings, when I “forget” to run grc with
correct priviliges (sudo).

John

Fra: [email protected]
[[email protected]] På vegne af Phelps
Williams [[email protected]]
Sendt: 25. februar 2011 06:43
Til: [email protected]
Emne: [Discuss-gnuradio] GRC + N210 + RFX2200 + UHD not working

I’m using grc to generate some extremely simple flowgraphs but I’m
seeing very odd performance. Any idea why I can’t seem to get this
combination to work? I have had success with a GRC + USRP2 + WBX + UHD,
anybody know why I’m having issues here?

When I create a flowgraph directly to a null sink (null.png) I receive
the following error:

Generating: “/home/pwilliams/gnuradio_test/video_tx/top_block.py”

Executing: “/home/pwilliams/gnuradio_test/video_tx/top_block.py”

linux; GNU C++ version 4.4.1; Boost_103800;
UHD_002.20110219191607.c912463

Current recv sock buff size: 50000000 bytes

Warning:
error in pthread_setschedparam
Failed to set thread priority 0.5 (realtime):
Performance may be negatively affected.
See the general application notes.

Warning:
error in pthread_setschedparam
Failed to set thread priority 0.5 (realtime):
Performance may be negatively affected.
See the general application notes.
mboard0 MIMO master

Warning:
error in pthread_setschedparam
Failed to set thread priority 0.5 (realtime):
Performance may be negatively affected.
See the general application notes.
UHD source block got error code 0x1
gr_block_executor: source <gr_block uhd single_usrp source (2)> produced
no output. We’re marking it DONE.

When I create a flowgraph directly to a fftp sink (fft.png) it just
silently exits with no errors:

Generating: “/home/pwilliams/gnuradio_test/video_tx/top_block.py”

Executing: “/home/pwilliams/gnuradio_test/video_tx/top_block.py”

linux; GNU C++ version 4.4.1; Boost_103800;
UHD_002.20110219191607.c912463

Current recv sock buff size: 50000000 bytes

Warning:
error in pthread_setschedparam
Failed to set thread priority 0.5 (realtime):
Performance may be negatively affected.
See the general application notes.

Warning:
error in pthread_setschedparam
Failed to set thread priority 0.5 (realtime):
Performance may be negatively affected.
See the general application notes.
mboard0 MIMO master

Warning:
error in pthread_setschedparam
Failed to set thread priority 0.5 (realtime):
Performance may be negatively affected.
See the general application notes.

4

Hmm, when running git branch --track gr_uhd_next jblum/gr_uhd_next

I get the error fatal: Not a valid object name: ‘jblum/gr_uhd_next’.

Has something changed within the past few days?

-Phelps

5

On 03/01/2011 12:50 PM, Phelps W. wrote:

Hmm, when running git branch --track gr_uhd_next jblum/gr_uhd_next

I get the error fatal: Not a valid object name: ‘jblum/gr_uhd_next’.

Has something changed within the past few days?

It has been merged into gnuradio.git/next branch.

Thanks,
-josh

6

I think I have isolated the issue to uhd. I used the following
procedure
and the benchmark_rx_rate test program appears to show the issue I’ve
been
experiencing. I have performed the same test with a USRP2 and a WBX
daughterboard and no errors occurred.

git clone git://code.ettus.com/ettus/uhd.git
cd {UHD_ROOT}
git remote update
git branch --track next origin/next
git checkout next
cd {UHD_ROOT}/host
mkdir build
cd build
cmake …/
make
make test
sudo make install
sudo ldconfig

cd /usr/local/share/uhd/examples
./benchmark_rx_rate
linux; GNU C++ version 4.4.1; Boost_103800;
UHD_003.20110226000831.77641c6

Creating the usrp device with: …
Current recv sock buff size: 50000000 bytes
mboard0 MIMO master
Using Device: Single USRP:
Device: USRP2/N Series device
Mboard 0: USRP-N210 mboard
RX DSP 0: USRP-N210 ddc0
RX Channel: 0
RX Dboard: USRP-N210 dboard (rx unit)
RX Subdev: RFX2200 (0x002c)
TX DSP 0: USRP-N210 duc0
TX Channel: 0
TX Dboard: USRP-N210 dboard (tx unit)
TX Subdev: RFX2200 (0x002d)

Testing receive rate 0.500000 Msps (10.000000 second run)
Error code: 1
Unexpected error on recv, exit test…
Testing receive rate 1.000000 Msps (10.000000 second run)
Error code: 1
Unexpected error on recv, exit test…
Testing receive rate 2.000000 Msps (10.000000 second run)
Error code: 1
Unexpected error on recv, exit test…
Testing receive rate 4.000000 Msps (10.000000 second run)
Error code: 1
Unexpected error on recv, exit test…

Warning:
The hardware does not support the requested RX sample rate:
Target sample rate: 8.000000 MSps
Actual sample rate: 8.333333 MSps
Testing receive rate 8.333333 Msps (10.000000 second run)
Error code: 1
Unexpected error on recv, exit test…
Testing receive rate 16.666667 Msps (10.000000 second run)
Error code: 1
Unexpected error on recv, exit test…

Warning:
The hardware does not support the requested RX sample rate:
Target sample rate: 33.333333 MSps
Actual sample rate: 25.000000 MSps
Testing receive rate 25.000000 Msps (10.000000 second run)
Error code: 1
Unexpected error on recv, exit test…

Warning:
The hardware does not support the requested RX sample rate:
Target sample rate: 50.000000 MSps
Actual sample rate: 25.000000 MSps

Done!

7

Phelps W. wrote in post #984830:

I think I have isolated the issue to uhd. I used the following
procedure
and the benchmark_rx_rate test program appears to show the issue I’ve
been
experiencing. I have performed the same test with a USRP2 and a WBX
daughterboard and no errors occurred.

git clone git://code.ettus.com/ettus/uhd.git
cd {UHD_ROOT}
git …
cd /usr/local/share/uhd/examples
./benchmark_rx_rate
linux; GNU C++ version 4.4.1; Boost_103800;
UHD_003.20110226000831.77641c6

Creating the usrp device with: …
Current recv sock buff size: 50000000 bytes
mboard0 MIMO master
…

Testing receive rate 0.500000 Msps (10.000000 second run)
Error code: 1
Unexpected error on recv, exit test…
Testing receive rate 1.000000 Msps (10.000000 second run)
Error code: 1
Unexpected error on recv, exit test…
Testing receive rate 2.000000 Msps (10.000000 second run)
Error code: 1
Unexpected error on recv, exit test…
Testing receive rate 4.000000 Msps (10.000000 second run)
Error code: 1
Unexpected error on recv, exit test…

Warning:
The hardware does not support the requested RX sample rate:
Target sample rate: 8.000000 MSps
Actual sample rate: 8.333333 MSps
Testing receive rate 8.333333 Msps (10.000000 second run)
Error code: 1
Unexpected error on recv, exit test…
Testing receive rate 16.666667 Msps (10.000000 second run)
Error code: 1
Unexpected error on recv, exit test…

Warning:
The hardware does not support the requested RX sample rate:
Target sample rate: 33.333333 MSps
Actual sample rate: 25.000000 MSps
Testing receive rate 25.000000 Msps (10.000000 second run)
Error code: 1
Unexpected error on recv, exit test…

Warning:
The hardware does not support the requested RX sample rate:
Target sample rate: 50.000000 MSps
Actual sample rate: 25.000000 MSps

Done!

Hello Phelps,

I had similar problem with the N210 and I tried the step you have
mentioned above and facing with teh same results with the
benchmark_rx_rate.

Is there any turnaround for this issue, if so could you please let me
know about the same.

Thanks in advance

Cheers,
Nishin

8

I have a similar problem.
Pulled down the GIT version of UHD a couple days ago, and "
./benchmark_rx_rate" behaves strangely.

It always looses packets, even at 0.5 Msps, and when it tries 16 Msps it
goes:

Testing receive rate 16.000000 Msps (10.000000 second run)
OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
Received packets: 19934
Received samples: 81649664
Lost samples: 79144386
Lost packets: 19322 (approximate)
Sustained receive rate: 8.124645 Msps

Decimation must be even and between 4 and 256

Warning:
The hardware does not support the requested RX sample rate:
Target sample rate: 32.000000 MSps
Actual sample rate: 16.000000 MSps

Done!

The strange thing is, that the number of lost packets is always almost
the same for each speed (5 for 0.5 Msps, 14 for 1 Msps, 75 for 2
Msps…) regardless of whether I run it as a normal user or super user.
In the first case it complains about not being able to set scheduling,
but the final result is the same. Also, the number of lost packets
barely changes between the runs.

Any idea what to do? I would really like to run at least 8 Msps without
lost packets.

BTW I hava an USRP1 and run Opensuse 11.3 on an AMD Athlon™ 64 X2
Dual Core Processor 4400+, cca 2k bogomips per core.

regards, Marko Cebokli

9

P.S.

since these are complex samples, I could live with 4Msps, but any lost
packets are a big problem…

“latency_test” goes like this:

Interpolation rate must be even and between 8 and 512

Warning:
The hardware does not support the requested TX sample rate:
Target sample rate: 25.000000 MSps
Actual sample rate: 4.000000 MSps
Actual TX Rate: 4.000000 Msps…
Decimation must be even and between 4 and 256

Warning:
The hardware does not support the requested RX sample rate:
Target sample rate: 25.000000 MSps
Actual sample rate: 4.000000 MSps
Actual RX Rate: 4.000000 Msps…
failed:
Async message recv timed out.

failed:
Async message recv timed out.
…
until it finishes with
ACK 0, UNDERFLOW 0, TIME_ERR 0, other 0