Re: [Discuss-gnuradio] Error in my first USRP test

[Alaelddin Mohammed]

I found that I am using libusb-win32  version  0.1.12.0-1,  I change it 
to version 0.1.10.1-3. I plugged TX and RX in my USRP device. but I got 
this error.

$ python test_counting.py
found 5 busses
found 5 busses
usrp_open_interface:usb_claim_interface: failed interface 2
could not claim interface 2, interface invalid
usrp_basic_rx: can't open rx interface
Traceback (most recent call last):
 File "test_counting.py", line 53, in ?
   main ()
 File "test_counting.py", line 46, in main
   fg = build_graph ()
 File "test_counting.py", line 36, in build_graph
   usrp_rx = usrp.source_s (0, rx_decim, 1, 0x32103210, 
usrp.FPGA_MODE_COUNTING)
 File "/usr/local/lib/python2.4/site-packages/gnuradio/usrp.py", line 
266, in __init__
   fpga_filename, firmware_filename)
 File "/usr/local/lib/python2.4/site-packages/gnuradio/usrp1.py", line 
1502, in source_s
   return _usrp1.source_s(*args)
RuntimeError: can't open usrp1

What shall I do now please
--Alaelddin


Don Ward wrote:
> ----- Original Message ----- From: "Alaelddin Mohammed" 
> <address@hidden>
> To: <address@hidden>
> Sent: Tuesday, June 19, 2007 7:18 PM
> Subject: [Discuss-gnuradio] Error in my first USRP test
>
>
> > Hi
> > I tried to run test_counting.py , I got the folloing message
> >
> > $ python test_counting.py
> > usb_control_msg failed: usb_control_msg: sending control message 
> > failed, win err
> > or: A device attached to the system is not functioning.
> > usb_control_msg failed: usb_control_msg: sending control message 
> > failed, win err
> > or: A device attached to the system is not functioning.
>
> As far as I can tell, one occurrence of this error each time you start 
> GNU Radio is normal when using Windows libusb 0.1.12.  I don't know 
> why you get two of them.
>
> > gr_check_counting: enter_SEARCHING at offset        0 (0x00000000)
> > gr_check_counting: expected     0 (0x0000) got     2 (0x0002) offset 
> > 0 (0x00000000)
> > gr_check_counting: expected     3 (0x0003) got     3 (0x0003) offset 
> > 1 (0x00000001)
> > gr_check_counting: expected     4 (0x0004) got     4 (0x0004) offset 
> > 2 (0x00000002)
> > gr_check_counting: expected     5 (0x0005) got     5 (0x0005) offset 
> > 3 (0x00000003)
> > gr_check_counting: enter_LOCKED at offset        3 (0x00000003)
>
> This is also what I get.  I have assumed it is normal.
>
> -- Don W.
>
>
> > Could you please what is wrong
>
> > --Alaelddin