usrp-users@lists.ettus.com

Discussion and technical support related to USRP, UHD, RFNoC

View all threads

B200 isn't officially supported under Windows

MW
Mike Willis
Sun, Jan 26, 2014 6:46 PM

Marcus - I understand you are trying to help but you keep asking everyone
this same questions - have you considered that people might not know? They
are not experts and download what is on the Ettus site. Would it not be more
helpful to point everyone to a version that does actually work?

In the meantime, I am also rather fed up and wondering if anyone is
interested in a second hand B200 because after 5 months it's still a useless
peripheral under windows and I don't see that changing any time soon.

Mike


The B200 isn't, yet, officially supported under Windows, to be honest.

But it should work.  What UHD version are you using?

--
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org

Marcus - I understand you are trying to help but you keep asking everyone this same questions - have you considered that people might not know? They are not experts and download what is on the Ettus site. Would it not be more helpful to point everyone to a version that does actually work? In the meantime, I am also rather fed up and wondering if anyone is interested in a second hand B200 because after 5 months it's still a useless peripheral under windows and I don't see that changing any time soon. Mike > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com The B200 isn't, yet, officially supported under Windows, to be honest. But it should work. What UHD version are you using? -- Marcus Leech Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org
MD
Marcus D. Leech
Sun, Jan 26, 2014 7:13 PM

On 01/26/2014 01:46 PM, Mike Willis wrote:

Marcus - I understand you are trying to help but you keep asking everyone
this same questions - have you considered that people might not know? They
are not experts and download what is on the Ettus site. Would it not be more
helpful to point everyone to a version that does actually work?

The thing is, the B200 does work under Windows, but it hasn't been
thoroughly tested.  The reason I ask about UHD version numbers
is that, well, if you're running a version of UHD that was released
prior to the release of the B200, it can't possibly have support
in it for B200. That's why I ask people what version of UHD they're
running.

Granted, if the end-user is running some "turn-key" application, they
may not know what version of UHD they're using, particularly if the
"turn-key" application doesn't expose the UHD library startup output
when their application starts up.  So, in those cases, simply
run:

<install-path>\bin\uhd_usrp_probe.exe --args "type=b200"

In a command window to find out, it will produce a log like this (this
is from a Linux install, but similar output).  Note that it shows the UHD
version number.

linux; GNU C++ version 4.5.1 20100924 (Red Hat 4.5.1-4); Boost_104400;
UHD_003.006.002-1-g9fd308b3
^^^^^^^^^^^^^^^^^^^^

-- Operating over USB 2.
-- Initialize CODEC control...
-- Initialize Radio control...
-- Performing register loopback test... pass
-- Performing register loopback test... pass
-- Performing CODEC loopback test... pass
-- Performing CODEC loopback test... pass
-- Asking for clock rate 32 MHz
-- Actually got clock rate 32 MHz
-- Performing timer loopback test... pass
-- Performing timer loopback test... pass


/
|      Device: B-Series Device
|    _____________________________________________________
|    /
|  |      Mboard: B210
|  |  revision: 4
|  |  product: 2
|  |  serial: EAR04Z1BT
|  |  FW Version: 4.0
|  |  FPGA Version: 3.0
|  |
|  |  Time sources: none, external, gpsdo
|  |  Clock sources: internal, external, gpsdo
|  |  Sensors: ref_locked
|  |    _____________________________________________________
|  |    /
|  |  |      RX DSP: 0
|  |  |  Freq range: -16.000 to 16.000 Mhz
|  |    _____________________________________________________
|  |    /
|  |  |      RX DSP: 1
|  |  |  Freq range: -16.000 to 16.000 Mhz
|  |    _____________________________________________________
|  |    /
|  |  |      RX Dboard: A
|  |  |    _____________________________________________________
|  |  |    /
|  |  |  |      RX Frontend: A
|  |  |  |  Name: FE-RX2
|  |  |  |  Antennas: TX/RX, RX2
|  |  |  |  Sensors:
|  |  |  |  Freq range: 50.000 to 6000.000 Mhz
|  |  |  |  Gain range PGA: 0.0 to 73.0 step 1.0 dB
|  |  |  |  Connection Type: IQ
|  |  |  |  Uses LO offset: No
|  |  |    _____________________________________________________
|  |  |    /
|  |  |  |      RX Frontend: B
|  |  |  |  Name: FE-RX1
|  |  |  |  Antennas: TX/RX, RX2
|  |  |  |  Sensors:
|  |  |  |  Freq range: 50.000 to 6000.000 Mhz
|  |  |  |  Gain range PGA: 0.0 to 73.0 step 1.0 dB
|  |  |  |  Connection Type: IQ
|  |  |  |  Uses LO offset: No
|  |  |    _____________________________________________________
|  |  |    /
|  |  |  |      RX Codec: A
|  |  |  |  Name: B210 RX dual ADC
|  |  |  |  Gain Elements: None
|  |    _____________________________________________________
|  |    /
|  |  |      TX DSP: 0
|  |  |  Freq range: -16.000 to 16.000 Mhz
|  |    _____________________________________________________
|  |    /
|  |  |      TX DSP: 1
|  |  |  Freq range: -16.000 to 16.000 Mhz
|  |    _____________________________________________________
|  |    /
|  |  |      TX Dboard: A
|  |  |    _____________________________________________________
|  |  |    /
|  |  |  |      TX Frontend: A
|  |  |  |  Name: FE-TX2
|  |  |  |  Antennas: TX/RX
|  |  |  |  Sensors:
|  |  |  |  Freq range: 50.000 to 6000.000 Mhz
|  |  |  |  Gain range PGA: 0.0 to 89.8 step 0.2 dB
|  |  |  |  Connection Type: IQ
|  |  |  |  Uses LO offset: No
|  |  |    _____________________________________________________
|  |  |    /
|  |  |  |      TX Frontend: B
|  |  |  |  Name: FE-TX1
|  |  |  |  Antennas: TX/RX
|  |  |  |  Sensors:
|  |  |  |  Freq range: 50.000 to 6000.000 Mhz
|  |  |  |  Gain range PGA: 0.0 to 89.8 step 0.2 dB
|  |  |  |  Connection Type: IQ
|  |  |  |  Uses LO offset: No
|  |  |    _____________________________________________________
|  |  |    /
|  |  |  |      TX Codec: A
|  |  |  |  Name: B210 TX dual DAC
|  |  |  |  Gain Elements: None

But I can't diagnose remotely without knowing a few things, like the UHD
library version number.  If people are running UHD prior to
3.5.4, there'll be no B200 support at all, and with 3.5.4, it's
very preliminary, and almost certainly doesn't work on Windows.
I ask questions not to be annoying, but, rather, to try to get data
to help me diagnose and hopefully solve, issues.

The 3.6.2-rc2 release should work better on Windows, but again, Ettus
hasn't done extensive testing yet on Windows for the B200.
It's coming, and the only thing Ettus tests on is XP, Vista, and Win7
at the moment.

http://files.ettus.com/binaries/uhd_stable/uhd_003.006.002-rc2/uhd_003.006.002-rc2_Win64.exe

--
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org

On 01/26/2014 01:46 PM, Mike Willis wrote: > Marcus - I understand you are trying to help but you keep asking everyone > this same questions - have you considered that people might not know? They > are not experts and download what is on the Ettus site. Would it not be more > helpful to point everyone to a version that does actually work? The thing is, the B200 *does* work under Windows, but it hasn't been thoroughly tested. The reason I ask about UHD version numbers is that, well, if you're running a version of UHD that was released prior to the release of the B200, it can't possibly have support in it for B200. That's why I ask people what version of UHD they're running. Granted, if the end-user is running some "turn-key" application, they may not know what version of UHD they're using, particularly if the "turn-key" application doesn't expose the UHD library startup output when their application starts up. So, in those cases, simply run: <install-path>\bin\uhd_usrp_probe.exe --args "type=b200" In a command window to find out, it will produce a log like this (this is from a Linux install, but similar output). Note that it shows the UHD version number. linux; GNU C++ version 4.5.1 20100924 (Red Hat 4.5.1-4); Boost_104400; UHD_003.006.002-1-g9fd308b3 ^^^^^^^^^^^^^^^^^^^^ -- Operating over USB 2. -- Initialize CODEC control... -- Initialize Radio control... -- Performing register loopback test... pass -- Performing register loopback test... pass -- Performing CODEC loopback test... pass -- Performing CODEC loopback test... pass -- Asking for clock rate 32 MHz -- Actually got clock rate 32 MHz -- Performing timer loopback test... pass -- Performing timer loopback test... pass _____________________________________________________ / | Device: B-Series Device | _____________________________________________________ | / | | Mboard: B210 | | revision: 4 | | product: 2 | | serial: EAR04Z1BT | | FW Version: 4.0 | | FPGA Version: 3.0 | | | | Time sources: none, external, gpsdo | | Clock sources: internal, external, gpsdo | | Sensors: ref_locked | | _____________________________________________________ | | / | | | RX DSP: 0 | | | Freq range: -16.000 to 16.000 Mhz | | _____________________________________________________ | | / | | | RX DSP: 1 | | | Freq range: -16.000 to 16.000 Mhz | | _____________________________________________________ | | / | | | RX Dboard: A | | | _____________________________________________________ | | | / | | | | RX Frontend: A | | | | Name: FE-RX2 | | | | Antennas: TX/RX, RX2 | | | | Sensors: | | | | Freq range: 50.000 to 6000.000 Mhz | | | | Gain range PGA: 0.0 to 73.0 step 1.0 dB | | | | Connection Type: IQ | | | | Uses LO offset: No | | | _____________________________________________________ | | | / | | | | RX Frontend: B | | | | Name: FE-RX1 | | | | Antennas: TX/RX, RX2 | | | | Sensors: | | | | Freq range: 50.000 to 6000.000 Mhz | | | | Gain range PGA: 0.0 to 73.0 step 1.0 dB | | | | Connection Type: IQ | | | | Uses LO offset: No | | | _____________________________________________________ | | | / | | | | RX Codec: A | | | | Name: B210 RX dual ADC | | | | Gain Elements: None | | _____________________________________________________ | | / | | | TX DSP: 0 | | | Freq range: -16.000 to 16.000 Mhz | | _____________________________________________________ | | / | | | TX DSP: 1 | | | Freq range: -16.000 to 16.000 Mhz | | _____________________________________________________ | | / | | | TX Dboard: A | | | _____________________________________________________ | | | / | | | | TX Frontend: A | | | | Name: FE-TX2 | | | | Antennas: TX/RX | | | | Sensors: | | | | Freq range: 50.000 to 6000.000 Mhz | | | | Gain range PGA: 0.0 to 89.8 step 0.2 dB | | | | Connection Type: IQ | | | | Uses LO offset: No | | | _____________________________________________________ | | | / | | | | TX Frontend: B | | | | Name: FE-TX1 | | | | Antennas: TX/RX | | | | Sensors: | | | | Freq range: 50.000 to 6000.000 Mhz | | | | Gain range PGA: 0.0 to 89.8 step 0.2 dB | | | | Connection Type: IQ | | | | Uses LO offset: No | | | _____________________________________________________ | | | / | | | | TX Codec: A | | | | Name: B210 TX dual DAC | | | | Gain Elements: None But I can't diagnose remotely without knowing a few things, like the UHD library version number. If people are running UHD prior to 3.5.4, there'll be no B200 support *at all*, and with 3.5.4, it's very *preliminary*, and almost certainly doesn't work on Windows. I ask questions not to be annoying, but, rather, to try to get data to help me diagnose and hopefully solve, issues. The 3.6.2-rc2 release should work *better* on Windows, but again, Ettus hasn't done extensive testing yet on Windows for the B200. It's coming, and the only thing Ettus tests on is XP, Vista, and Win7 at the moment. http://files.ettus.com/binaries/uhd_stable/uhd_003.006.002-rc2/uhd_003.006.002-rc2_Win64.exe -- Marcus Leech Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org
MS
Marcin Stolarski
Thu, Jan 30, 2014 11:28 AM

Try to connect to USB2.0 connector. UHD has some problems with USB 3.0,
sometime it work sometime don't.

73
MS

Try to connect to USB2.0 connector. UHD has some problems with USB 3.0, sometime it work sometime don't. 73 MS