PothosSDR with Ettus B200

[hb9...@vtxnet.ch]

Bonjour,

Today, I have installed the Pothos environment on WIndows 7 with the goal to run it with an Ettus B200. Once the installation was finished, I have downloaded the images with the tool uhd_images_downloader.py and installed the winusb driver found in the directory images.

My B200 is recognized by windows. But when I check with:

C:\PothosSDR\bin>SoapySDRUtil --probe="driver=uhd,type=b200"
######################################################
## Soapy SDR -- the SDR abstraction library
######################################################

Probe device driver=uhd,type=b200
Win32; Microsoft Visual C++ version 14.0; Boost_106000; UHD_003.009.004-0-g2b5a88bb

Error probing device: LookupError: KeyError: No devices found for ----->
Device Address:
    driver: uhd
    type: b200

or

C:\PothosSDR\bin>uhd_find_devices
Win32; Microsoft Visual C++ version 14.0; Boost_106000; UHD_003.009.004-0-g2b5a88bb

--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
    driver: s9c
    type: soapy


I made a simple graph with a SDR Source with Device Args: "driver":"uhd" connected to a Spectrogram with an expected error msg as previous check was not succesful...


[22:03:29.899124] PothosGui.MainWindow: Welcome to Pothos v0.3.3-PothosSDR-2016.05.13-vc14-x64

[22:03:29.949124] PothosGui.MainWindow: Initialization complete

[22:03:29.949124] PothosGui.GraphEditor.load: Loading C:/Users/hb9dug/Documents/- a pothossdr/b200-test.pth from file

[22:03:30.269000] : Win32; Microsoft Visual C++ version 14.0; Boost_106000; UHD_003.009.004-0-g2b5a88bb

[22:03:38.787181] PothosGui.TopologyEval.commit:

Framework Topology Connect Error: Pothos::Topology::commit(): Framework Topology Connect Error: SDRSource0.activate(): Exception: LookupError: KeyError: No devices found for ----->

Device Address:

    driver: uhd

Help will be appreciated  :-)    and please don't hesitate to tell if I am at the wrong place to ask such beginner issue...

Rgds.
Michel

[Josh Blum]

Hi Michel,

Can you check that the device shows up in the device manager without any
question marks or error indicators. I see it under Universal serial bus
devices -> USRP B200.

FWIW. I am testing with windows 8, and I used the included zadig tool to
install the usb driver support -- this is what makes the device
available through libusb. I don't know how this compares to the winusb
driver found in the directory images, but I suspect its the same.

And the following command lines worked for me if that helps:
uhd_find_devices --args="type=b200"
uhd_usrp_probe --args="type=b200"
SoapySDRUtil --probe="driver=uhd,type=b200"

I think its a usb device driver issue. So I hope this helps!
Thanks,
-Josh

On 05/15/2016 03:14 PM, hb9...@vtxnet.ch wrote:
> Bonjour,
>
> Today, I have installed the Pothos environment on WIndows 7 with the goal
> to run it with an Ettus B200. Once the installation was finished, I have
> downloaded the images with the tool uhd_images_downloader.py and installed
> the winusb driver found in the directory images.
>
> My B200 is recognized by windows. But when I check with:
>

> *C:\PothosSDR\bin>SoapySDRUtil --probe="driver=uhd,type=b200"*

> ######################################################
> ## Soapy SDR -- the SDR abstraction library
> ######################################################
>
> Probe device driver=uhd,type=b200
> Win32; Microsoft Visual C++ version 14.0; Boost_106000;
> UHD_003.009.004-0-g2b5a88bb
>
> Error probing device: LookupError: KeyError: No devices found for ----->
> Device Address:
> driver: uhd
> type: b200
>
> or
>

> *C:\PothosSDR\bin>uhd_find_devices*

[hb9...@vtxnet.ch]

Progress report....

I have an issue with my USB 3.0 ports on my pc.  I checked with a NooElec USB key and I had the same issue as with the B200. The device shows up in the device manager without any errors but no success to use it with PothosSDR, HDSDR or SDR# . Moving the NooElec to a USB 2.0 port resolved the issue !  PothosSDR works fine with the DAB key.

Hope to find the issue with the USB 3.0 port this wk !

Cordialement.
Michel