Hello,
For my current problem I also searched through the net and found this
one here:
http://ettus.80997.x6.nabble.com/USRP-users-Sequence-Errors-N200-td13041.html
Somehow, after a lot of communicating and also adapting the steps
recommended their, the problem was not solved. So maybe I start with
explaining what my problem is and what I have done maybe wrong:
I'm observing strange behaviour on transmission with USRP N200 in
combination with Daughterboards Basic-Tx and Basic-Rx. First I would
like to share some basic information:
Operating System : Ubuntu 18.04LTS (64bit)
Kernel Version : 4.15.0-55-generic
GnuRadio : 3.7.11
UHD : 003.010.003.000
Network-Cards : Realtek RTL8111/8168/8411 PCI Express Gigabit
Ethernet Controller
Intel I219-LM
I was using the following commands for installing uhd and gnuradio:
$ sudo apt install gnuradio
$ sudo apt install uhd-host
$ uhd_images_downloader
I'll start with the steps I've done so far:
- using a USRP-N200 REV D (bought in 2016/17) (was working fine on
Ubuntu 16.04 LTS, with same network cards)
- upgraded my system to Ubuntu 18.04LTS
- try using my USRP-N200 with this new operating system adn
gnuradio (as expected, some compat_num problem)
- then using the command listet by gnuradio console with the specified IP
- when running the uhd_image_loader some happend during the
process, because it was not able to
verify the FPGA image
- then reading the section of device recovery from ettus
- I've done the S2 button safe-mode thing and the usrp was found
with the default 192.168.10.2 ip address
using uhd_find_devices
- then I retried the uhd_image_loader and it does all steps without
problems and I changed the ip
also to another one "192.168.20.2" with usrp2_recovery.py
- after using uhd_find_devices it appers with the new ip
- now I was doing the following:
$ ./benchmark_rate --args="type=usrp2,addr=192.168.20.2" --tx_rate
200e3 --rx_rate 200e3 --duration 60
linux; GNU C++ version 7.3.0; Boost_106501; UHD_003.010.003.000-0-unknown
Creating the usrp device with: type=usrp2,addr=192.168.20.2...
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N200r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: BasicRX (AB)
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: BasicTX (AB)
Setting device timestamp to 0...
Testing receive rate 0.200000 Msps on 1 channels
Testing transmit rate 0.200000 Msps on 1 channels
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
Benchmark rate summary:
Num received samples: 12002270
Num dropped samples: 0
Num overflows detected: 0
Num transmitted samples: 12325665
Num sequence errors: 115
Num underflows detected: 0
Num late commands: 0
Num timeouts: 0
Done!
As you can see, I've used 200kHz for both sides which is nothing in
sense to 5MHz I've used before with the same network card. I was also
following the recommendation of net.core.wmem/rmem , user thread
priority and ethtool -G options to increase the performances.
Best regards, Nico
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
