Hi there!
I am having problems when connecting the USRP X310 to my PC via a switch
(I am doing this as I would like to connect several USRPs
simultaneously). The connection between the PC and the USRP via direct
Ethernet connection works perfectly but not when I connect a switch in
between. I
Hi Xavier,
Thank you very much for your answer!
I was just using the command uhd_find_devices from the terminal and the
PC did not detect anything. Sending a ping did not work either. When I
did the same by connecting just the PC without the switch, everything
worked properly.
Do you think
Hey Maria,
If I'm not wrong, USRPs have default static IP addresses, which are
specific to the FPGA image you've loaded onto them. Perhaps if you're using
more than one in the same network domain there's being a collision and you
need to change one of the board's IP default IP addresses first? Jus
Hi Leandro,
Thank you very much for your answer!
I think that might not be the problem as I was using just one USRP (I
was basically checking if it was working with the switch before
connecting more of them).
Best regards,
Maria Jesus
On 12/02/2019 12:13, Leandro Echevarría wrote:
Hey Mar
On 02/12/2019 05:55 AM, Maria Jesus Cañavate Sanchez via USRP-users wrote:
Hi there!
I am having problems when connecting the USRP X310 to my PC via a
switch (I am doing this as I would like to connect several USRPs
simultaneously). The connection between the PC and the USRP via direct
Ethern
Hello,
I am using a USRP B205mini-i radio and keep receiving the following error from
version 3.12 of the UHD API:
terminate called after throwing 'uhd::io_error'
what(): EnvironmentError: IOError: usb tx2 transfer status:
LIBUSB_TRANSFER_ERROR
Sometimes the error will say "usb rx2 transf
On 02/12/2019 10:24 AM, Jimmy Uhing via USRP-users wrote:
Hello,
I am using a USRP B205mini-i radio and keep receiving the following
error from version 3.12 of the UHD API:
terminate called after throwing 'uhd::io_error'
what(): EnvironmentError: IOError: usb tx2 transfer status:
LIBUSB
This happened to me as well after upgrading from 3.10 to either 3.12 or
3.13 (forget which).
It will run normally, but in various gnuradio flowgraph terminate
situations, it has this error
and does not seem to recover without a device reinitialization.
-- Tom, N5EG
On Tue, Feb 12, 2019 at 7:25
Here you go:
Sample rate: 5e6
Supplied usb cable: yes
Computer: i7 running Ubuntu 14.04
USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI
(rev 04)
USB 2/3: 3
Some additional output from syslog:
kernel: [ 424.298759] usb 1-1: new high-speed USB device number 6 using
On 02/12/2019 11:04 AM, Jimmy Uhing via USRP-users wrote:
Here you go:
Sample rate: 5e6
Supplied usb cable: yes
Computer: i7 running Ubuntu 14.04
USB controller: Intel Corporation 8 Series/C220 Series Chipset Family
USB xHCI (rev 04)
USB 2/3: 3
Some additional output from syslog:
kernel: [ 4
How much current can the X300 REF OUT port drive? I have another device that
has a reference input with a relatively low input impedance, and I want to
ensure that it can source enough current to properly drive it.
Thanks.
Jason
___
USRP-users mailing
On 02/12/2019 11:14 AM, Jason Roehm via USRP-users wrote:
How much current can the X300 REF OUT port drive? I have another device that
has a reference input with a relatively low input impedance, and I want to
ensure that it can source enough current to properly drive it.
Thanks.
Jason
__
Check U530 on page 11, A1:
https://files.ettus.com/schematics/x300/x3xx.pdf
It's a FIN1002 LVDS receiver. Datasheet says 16mA max:
http://www.mouser.com/ds/2/149/FIN1002-108110.pdf
Brian
On Tue, Feb 12, 2019 at 11:16 AM Jason Roehm via USRP-users <
usrp-users@lists.ettus.com> wrote:
> Ho
On 02/12/2019 11:25 AM, Brian Padalino via USRP-users wrote:
Check U530 on page 11, A1:
https://files.ettus.com/schematics/x300/x3xx.pdf
It's a FIN1002 LVDS receiver. Datasheet says 16mA max:
http://www.mouser.com/ds/2/149/FIN1002-108110.pdf
Brian
Hmm, yes. I had read the part-number inco
14 matches
Mail list logo
