Hi Josh,
I have an USRP1 working on USB therefore it shouldn’t give such kind
of
errors like “Error: An existing connection was forcibly closed by the
remote
host”?
It has nothing to do with firewalls (I’m not opening UDP sockets, it’s
not a
USRP2 or newer device) therefore the big question is why it’s not
working as
intended. It recognized my USRP1, but nothing more. What is the order of
finding
devices. I suppose it starts to look around for USB devices after that
other
devices on other interfaces, so when running uhd_usrp_probe it should
start to
do it’s job with USB devices, NO? therefore I should see results from
uhd_usrp_probe and after thet this error. I’ll have to check the source
code for
these examples.
Thank you very much.
Best regards,
Mark.
On 04/26/2011 04:59 PM, Mark Colin wrote:
Hi Josh,
I have an USRP1 working on USB therefore it shouldn’t give such kind of
errors like “Error: An existing connection was forcibly closed by the remote
host”?
Sorry, I missed that it was a USB based USRP. Even though its USB, the
discovery logic still tries to send out broadcast packets to your
network interfaces. (I am assuming that this error is a network issue.)
I think if you add these arguments, the discovery logic wont attempt to
search the network.
uhd_find_devices --args=“type=usrp1”
uhd_usrp_probe --args=“type=usrp1”
It still might be worth it to fix the issue. Maybe disable a few extra
network interfaces (or virtual ones like VPN). I have no idea, so I am
curious as to what might cause this.
-josh
I assume you did do this:
http://code.ettus.com/redmine/ettus/projects/uhd/wiki#Windows-USB-driver