Send USRP-users mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of USRP-users digest..."


Today's Topics:

   1. Ver 3.7 stable? (Mamoru Yamamoto)
   2. Re: Ver 3.7 stable? (Marcus D. Leech)
   3. Inquiries on Ettus USRP E110 Hardware Driver? (Chun Mein Soon)
   4. Re: Inquiries on Ettus USRP E110 Hardware Driver
      (Hacker Fantastic)


----------------------------------------------------------------------

Message: 1
Date: Sun, 08 Jun 2014 01:05:07 +0900
From: Mamoru Yamamoto <[email protected]>
To: gnuradio mailing list <[email protected]>,
        [email protected]
Subject: [USRP-users] Ver 3.7 stable?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-2022-JP

Dear experts,

<I send this question to both GNU radio and USRP mailing lists. I do not
know which is better place for this discussion.>

(1) Introduction
I am Mamoru Yamamoto from Kyoto Univ.
Some may know that I am doing satellite-beacon experiment
by using USRP1 + GNU Radio.  We call the receiver as
GRBR (GNU Radio Beacon Receiver).
http://www.rish.kyoto-u.ac.jp/digitalbeacon/
Sorry this web site is very old.  Now I am using
USRP1 + uhd + GNU Radio from python script
Also I am using Ubuntu 12.04LTS.
My application is a very simple dual-channel receiver
recording IQ time-series on two files.
The system is VERY stable and useful.  I like it very much.

(2) Current situation
Now I try to move to Ver 3.7.
(I installed the software by "build-gnuradio script".)
Necessary small changes for me were
-- "optfir.low_pass" location change
-- "freq_xlating_fir_filter_ccf" location change & centerfrequency
setting from negative to positive
-- "file_sink" location change

(3) Questions
These changes were done.  I now start running the system,
but have problems.  I have 2 questions.

Q1: I run the modified code with Ubuntu-32bit 12.04LTS.  My code worked
for several times, but after that, it created only "0-byte" files
(=immediate stop), and then no files were created.  I checked the uhd
status, and found that "uhd_find_devices" was successful while
"uhd_usrp_probe" failed (see below).  I now connect USRP1 to USB3 port.
 Is this wrong?

Q2: I also tried to use the same V3.7 code with Ubuntu-64bit 12.04LTS.
But output file from my code is always 0-bytes (=immediate stop).
Please tell me if 64bit OS is useless.

=== Check after the problem (Q1) ===
beacon@Beacon-36:~/beaconRX$ uhd_find_devices
linux; GNU C++ version 4.6.3; Boost_104800; UHD_003.007.001-72-g383061d8

--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
    type: usrp1
    name:
    serial: 2R24X5U1


beacon@Beacon-36:~/beaconRX$ uhd_usrp_probe
linux; GNU C++ version 4.6.3; Boost_104800; UHD_003.007.001-72-g383061d8

-- Opening a USRP1 device...
Error: RuntimeError: usb rx6 submit failed: LIBUSB_ERROR_IO

==============================

Thanks for your help and suggestions.

-- 
Mamoru Yamamoto / RISH, Kyoto University
[email protected]
Phone +81-774-38-3814, Cell +81-90-5653-7555



------------------------------

Message: 2
Date: Sat, 07 Jun 2014 12:11:32 -0400
From: "Marcus D. Leech" <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Ver 3.7 stable?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 06/07/2014 12:05 PM, Mamoru Yamamoto via USRP-users wrote:
> Dear experts,
>
> <I send this question to both GNU radio and USRP mailing lists. I do not
> know which is better place for this discussion.>
>
> (1) Introduction
> I am Mamoru Yamamoto from Kyoto Univ.
> Some may know that I am doing satellite-beacon experiment
> by using USRP1 + GNU Radio.  We call the receiver as
> GRBR (GNU Radio Beacon Receiver).
> http://www.rish.kyoto-u.ac.jp/digitalbeacon/
> Sorry this web site is very old.  Now I am using
> USRP1 + uhd + GNU Radio from python script
> Also I am using Ubuntu 12.04LTS.
> My application is a very simple dual-channel receiver
> recording IQ time-series on two files.
> The system is VERY stable and useful.  I like it very much.
>
> (2) Current situation
> Now I try to move to Ver 3.7.
> (I installed the software by "build-gnuradio script".)
> Necessary small changes for me were
> -- "optfir.low_pass" location change
> -- "freq_xlating_fir_filter_ccf" location change&  centerfrequency
> setting from negative to positive
> -- "file_sink" location change
>
> (3) Questions
> These changes were done.  I now start running the system,
> but have problems.  I have 2 questions.
>
> Q1: I run the modified code with Ubuntu-32bit 12.04LTS.  My code worked
> for several times, but after that, it created only "0-byte" files
> (=immediate stop), and then no files were created.  I checked the uhd
> status, and found that "uhd_find_devices" was successful while
> "uhd_usrp_probe" failed (see below).  I now connect USRP1 to USB3 port.
>   Is this wrong?
>
> Q2: I also tried to use the same V3.7 code with Ubuntu-64bit 12.04LTS.
> But output file from my code is always 0-bytes (=immediate stop).
> Please tell me if 64bit OS is useless.
>
> === Check after the problem (Q1) ===
> beacon@Beacon-36:~/beaconRX$ uhd_find_devices
> linux; GNU C++ version 4.6.3; Boost_104800; UHD_003.007.001-72-g383061d8
>
> --------------------------------------------------
> -- UHD Device 0
> --------------------------------------------------
> Device Address:
>      type: usrp1
>      name:
>      serial: 2R24X5U1
>
>
> beacon@Beacon-36:~/beaconRX$ uhd_usrp_probe
> linux; GNU C++ version 4.6.3; Boost_104800; UHD_003.007.001-72-g383061d8
>
> -- Opening a USRP1 device...
> Error: RuntimeError: usb rx6 submit failed: LIBUSB_ERROR_IO
>
> ==============================
>
> Thanks for your help and suggestions.
>
Many USB-3.0 controller and USB-2.0 device combinations don't work very 
well-the USB-2.0 "downshifting" doesn't happen correctly.
   Try your USRP1 on a USB-2.0 port instead.



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




------------------------------

Message: 3
Date: Sun, 8 Jun 2014 11:18:13 +0800
From: Chun Mein Soon <[email protected]>
To: "[email protected]" <[email protected]>
Cc: ahmad zuri sha'ameri <[email protected]>
Subject: [USRP-users] Inquiries on Ettus USRP E110 Hardware Driver?
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1256"

Hi,
I have encountered issue with of finding suitable driver of this device  (Ettus 
USRP E110). 
Device: Ettus Research USRP E110 S/N No: E9R 12X6E2Daugtherboards: SBXSoftware: 
Visual Studio 2010 C++Installed Software Dependencies: 1) CMake 2.6             
                                          2) Boost 1.55                         
                              3) LibUSB                                         
              4) Python 2.6                                                     
  5) Cheetah 2.0Installed Driver: 1) UHD Driver version 003.007.001(Stable) 
Report Issue: 1) Driver not detected in system device manager (Refer to 
Attachment Picture No Driver.jpg)
                       2) Inappropriate driver(Refer to Attachment Picture 
Driver From Ettus.jpg)
                             - Driver Link Source: 
http://files.ettus.com/binaries/misc/erllc_uhd_winusb_driver.zip
                             - Supported Device in the zip package doesn't 
include E110                      
Summary: What I was trying to do is just to run a simple example software that 
come from the UHD folder after the driver installation(e.g. tx_waveforms.exe).  
However, it won't run because my computer can't detect the USRP device. I 
connect the USB console to my PC and run uhd_find_devices.exe file which show 
that my PC does not detect the device. 
Could you kindly send me a tutorials for using this device?
Thank you 
RegardsSoon Chun Mein                                     
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140608/fee4f10c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Driver From Ettus.png
Type: image/png
Size: 145655 bytes
Desc: not available
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140608/fee4f10c/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: no driver.jpg
Type: image/jpeg
Size: 265974 bytes
Desc: not available
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140608/fee4f10c/attachment-0001.jpg>

------------------------------

Message: 4
Date: Sun, 8 Jun 2014 10:50:57 +0100
From: Hacker Fantastic <[email protected]>
To: Chun Mein Soon <[email protected]>
Cc: "[email protected]" <[email protected]>,  ahmad
        zuri sha'ameri <[email protected]>
Subject: Re: [USRP-users] Inquiries on Ettus USRP E110 Hardware Driver
Message-ID:
        <CAG-OieMF45GL7BxxPpPBSMgupBLcDw8TrU=dgprygxvpgnw...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Hi Chun,
              The E110 series is an embedded platform and not accessible
from your computer via the UHD driver. You will need to use the CONSOLE
connection with a USB cable to access the embedded Linux platform. You copy
your GNU/Radio applications from your computer and run it on the E110.

Kind Regards,
Matthew



On Sun, Jun 8, 2014 at 4:18 AM, Chun Mein Soon via USRP-users <
[email protected]> wrote:

> Hi,
>
> I have encountered issue with of finding suitable driver of this device
>  (Ettus USRP E110).
>
> Device: Ettus Research USRP E110 S/N No: E9R 12X6E2
> Daugtherboards: SBX
> Software: Visual Studio 2010 C++
> Installed Software Dependencies: 1) CMake 2.6
>                                                        2) Boost 1.55
>                                                        3) LibUSB
>                                                        4) Python 2.6
>                                                        5) Cheetah 2.0
> Installed Driver: 1) UHD Driver version *003.007.001(Stable) *
> Report Issue: 1) Driver not detected in system device manager (Refer to
> Attachment Picture No Driver.jpg)
>                        2) Inappropriate driver(Refer to Attachment Picture
> Driver From Ettus.jpg)
>                              - Driver Link Source:
> http://files.ettus.com/binaries/misc/erllc_uhd_winusb_driver.zip
>                              - Supported Device in the zip package doesn't
> include E110
>
>
> Summary: What I was trying to do is just to run a simple example software
> that come from the UHD folder after the driver installation(e.g.
> tx_waveforms.exe).  However, it won't run because my computer can't detect
> the USRP device. I connect the USB console to my PC and
> run uhd_find_devices.exe file which show that my PC does not detect the
> device.
>
> Could you kindly send me a tutorials for using this device?
>
> Thank you
>
> Regards
> Soon Chun Mein
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>


-- 
Matthew Hickey
Tel: +44 7543 661237
Web: http://blog.hackerfantastic.com

Please visit my website for blog postings, status updates and project
information.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140608/42f6f2f9/attachment-0001.html>

------------------------------

Subject: Digest Footer

_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com


------------------------------

End of USRP-users Digest, Vol 46, Issue 8
*****************************************

Reply via email to