how can I check a throughput between Pluto and my PC. I would like to know how efficient is my USB connection?
You can test throughput using iio_readdev: ADALM-PLUTO Performance Metrics [Analog Devices Wiki]
Thank You for answer. If I understand it correctly I have to type it on the PC side (with linux installed). Unfortunately I am using Windows 10. How can Icheck it on Windows?
I would use Windows Subsystem for Linux (WSL). To install WLS follow the instructions from Microsoft here: https://docs.microsoft.com/en-us/windows/wsl/install-win10 .
Please install Ubuntu when selecting an operating system, this will also allow you to use Gnu Radio.
I installed Ubuntu WSL. Currently I don't know how to detect appropriate USB port? On the example there is usb:1.100.5. Lsusb doesn't work on WSL.
try #iio_info -s
Pluto receives me: 0: Local devices [local:]
On PC it returns: iio_info: invalid option -- 's'
USB contexts do not work on WSL yet without some hackery. However, you can still use the networking one that works over the USB port.
iio_readdev -u ip:192.168.2.1 -b 100000 cf-ad9361-lpc | pv /dev/null
I still have a problem, returns "Invalid VID/PID"
I tried: iio_readdev -n 192.168.2.1 -b 100000 cf-ad9361-lpc | pv > /dev/null
but returns error: Unable to create IIO context
Did you install the windows drivers?
Yes, I can connect to Pluto with SSH, COM port and I can see html page under 192.168.2.1
Did you build libiio from source, or did you install it from the repo?
If yes which version is installed?
There was this issue: LIBIIO access via network on Windows Subsystem for Linux · Issue #158 · analogdevicesinc/libiio · GitHub
However it was fixed some time ago, please try to build and install libiio from source.
I've got the latest version(0.7) from this site: Releases · analogdevicesinc/plutosdr-m2k-drivers-win · GitHub
What should I install or build and install? Maybe libiio version 0.15 from this github: Release v0.15: Version 0.15 · analogdevicesinc/libiio · GitHub ? Which version is newer 0.7 for pluto or 0.15?
These are two different things. You need both the drivers and libiio.
For libiio use v0.15.
Still the same error. Maybe it won't work on WSL?
I've testing the throughput with Pluto to do this very thing with WSL and it does work fine.
First, does "iio_info -n 192.168.2.1" return anything?
Retrieving data ...