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. Re: tx_time tag accuraccy (bob wole)
   2. (no subject) (Roland Awusie)
   3. Re: (no subject) (Roland Awusie)
   4. time_spec (???)
   5. Re: Inquiries on Ettus USRP E110 Hardware Driver (Thierry Guichon)
   6. UHD support for National Instruments DAQ hardware (GW)
   7. B210 as standalone transmitter? (Metso Mikko)
   8. B200 GPSDO Dimensions (Garver, Paul W)


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

Message: 1
Date: Mon, 9 Jun 2014 09:05:21 +0500
From: bob wole <[email protected]>
To: "[email protected]" <[email protected]>,
        "[email protected]" <[email protected]>
Subject: Re: [USRP-users] tx_time tag accuraccy
Message-ID:
        <cagd3ozwobu0b2z2dr-rjbmfxk2sfeq1vgy51mjjsvao_ttq...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Can I have  a comment on it?


--
Bob

On Thu, Jun 5, 2014 at 11:02 AM, bob wole <[email protected]> wrote:

> Sorry for not stating the hardware earlier. I am using USRP N210, with
> RFX2400 and WBX boards.
>
> --
> Bob
>
> On Wed, Jun 4, 2014 at 11:07 PM, Marcus Leech <[email protected]> wrote:
>
>> I don't know the detailed answer, but any such answer will depend very
>> much on which USRP hardware you're talking about.
>>
>> One of the R&D people who deals with the FPGA codebase may be able to
>> give a precise answer, given stated hardware.
>>
>>
>>
>>  on Jun 04, 2014, *bob wole* <[email protected]> wrote:
>>
>>  Marcus! Thanks for you comment.
>>
>> I think that USRP transmit FIFO is at the start of the DSP chain in FPGA
>> i.e it is prior to both of the interpolation filters? right?  I am not
>> talking about when the burst will be over the air, I want to know when the
>> first sample of the burst will leave the transmit FIFO if it has been
>> tagged as tx_time=X.
>>
>>
>>
>> --
>> Bob
>>
>>
>> On Wed, Jun 4, 2014 at 10:51 PM, Marcus Leech <[email protected]> wrote:
>>
>>> It will depend some on the effective group delay of both the
>>> interpolation filters in the the FPGA and the analog group delay of the
>>> analog bits of whatever daughtercard you're using.
>>>
>>> The only way to be sure is to measure...
>>>
>>>
>>>   on Jun 04, 2014, *bob wole via USRP-users* <[email protected]>
>>> wrote:
>>>
>>>  I am using stream tags for the transmission control. I want to know
>>> what is the accuracy/precision of the tx_time tag? E.g if I tag a burst A
>>> with tx_time=X, then the burst A will come out of the USRP transmit FIFO at
>>> X+delta, how large the value of delta could be?
>>>
>>>
>>> --
>>> Bob
>>>   ------------------------------
>>>
>>> _______________________________________________
>>> USRP-users mailing list
>>> [email protected]
>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>>
>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140609/14c53e67/attachment-0001.html>

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

Message: 2
Date: Thu, 5 Jun 2014 21:06:31 -0600
From: Roland Awusie <[email protected]>
To: [email protected]
Subject: [USRP-users] (no subject)
Message-ID:
        <CAGdF4G6Y8=TcLy+FW_PtZmPk8fTRkyKYRs5kjkD+jn1QkuYb=w...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi All,

I had installed gnuradio on Fedora 20 on Lenovo ideadpad U430 laptop few
months ago and now want to re-install it using the gnuradio build script to
get the latest updates.I got the following error on the terminal either by
using home or usr directory.

I would be very grateful if anyone has seen this error before and can point
me in the rigth direction.













*[roland@localhost home]$ sudo wget
http://www.sbrac.org/files/build-gnuradio
<http://www.sbrac.org/files/build-gnuradio> && chmod a+x ./build-gnuradio
&& ./build-gnuradio --2014-06-05 00:03:11--
http://www.sbrac.org/files/build-gnuradio
<http://www.sbrac.org/files/build-gnuradio>Resolving www.sbrac.org
<http://www.sbrac.org> (www.sbrac.org <http://www.sbrac.org>)...
67.212.80.242 Connecting to www.sbrac.org <http://www.sbrac.org>
(www.sbrac.org <http://www.sbrac.org>)|67.212.80.242|:80... connected.HTTP
request sent, awaiting response... 200 OKLength: 37394 (37K) [text/plain]
Saving to:
?build-gnuradio?100%[======================================================================================================>]
37,394      --.-K/s   in 0.09s   2014-06-05 00:03:11 (401 KB/s) -
?build-gnuradio? saved [37394/37394] chmod: changing permissions of
?./build-gnuradio?: Operation not permitted*

Thank you,
Roland
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140605/2a37ccdd/attachment-0001.html>

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

Message: 3
Date: Thu, 5 Jun 2014 23:04:39 -0600
From: Roland Awusie <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] (no subject)
Message-ID:
        <cagdf4g52xqday-s1oj7nehc15oye03mq__vfsvc2i1cux8+...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

All,

I mixed my paswd with root pwd when using build-gnuradio script on my
earlier post. Now that I have it figured out, I ran into the following
error.

Is 'build-gnuradio' folder corrupting/preventing my download?

[rawusie@localhost ~]$ wget http://www.sbrac.org/files/build-gnuradio &&
chmod a+x ./build-gnuradio && ./build-gnuradio
--2014-06-05 22:24:49--  http://www.sbrac.org/files/build-gnuradio
Resolving www.sbrac.org (www.sbrac.org)... 67.212.80.242
Connecting to www.sbrac.org (www.sbrac.org)|67.212.80.242|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 37394 (37K) [text/plain]
Saving to: ?build-gnuradio?

100%[======================================================================================================================>]
37,394       176KB/s   in 0.2s

2014-06-05 22:24:50 (176 KB/s) - ?build-gnuradio? saved [37394/37394]

This script will install Gnu Radio from current GIT sources
You will require Internet access from the computer on which this
script runs. You will also require SUDO access. You will require
approximately 500MB of free disk space to perform the build.

This script will, as a side-effect, remove any existing Gnu Radio
installation that was installed from your Linux distribution packages.
It must do this to prevent problems due to interference between
a linux-distribution-installed Gnu Radio/UHD and one installed from GIT
source.

The whole process may take up to two hours to complete, depending on the
capabilities of your system.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
NOTE: if you run into problems while running this script, you can re-run it
with
the --verbose option to produce lots of diagnostic output to help debug
problems.
This script has been written to anticipate some of the more common problems
one might
encounter building ANY large, complex software package. But it is not
pefect, and
there are certainly some situations it could encounter that it cannot deal
with
gracefully. Altering the system configuration from something reasonably
standard,
removing parts of the filesystem, moving system libraries around
arbitrarily, etc,
it likely cannot cope with. It is just a script. It isn't intuitive or
artificially
intelligent. It tries to make life a little easier for you, but at the end
of the day
if it runs into trouble, a certain amount of knowledge on your part about
system configuration and idiosyncrasies will inevitably be necessary.


Proceed?y
Starting all functions at: Thu Jun 5 22:24:56 MDT 2014
SUDO privileges are required
Do you have SUDO privileges?y
Continuing with script
[sudo] password for rawusie:
Sorry, try again.
[sudo] password for rawusie:
Installing prerequisites.
====> THIS MAY TAKE QUITE SOME TIME <=====
Checking for library libusb-0 ...Found library libusb-0
Checking for library libusb-1 ...Found library libusb-1
Checking for library libboost ...Found library libboost
Checking for library libcppunit ...Found library libcppunit
Checking for library libfftw ...Found library libfftw
Checking for library libgsl ...Found library libgsl
Done
This script will fetch Gnu Radio version 3.7/maint from the repositories,
along with compatible
extras.
Is this OK?y
Fetching various packages (Gnu Radio, UHD, gr-osmosdr, gr-iqbal, etc)
via the Internet
=======> THIS MAY TAKE QUITE SOME TIME <=========

*Fetching Gnu Radio via GIT...Could not find
gnuradio/gnuradio-{core,runtime} after GIT checkoutGIT checkout of Gnu
Radio failed!*

I would be grateful for any help in this direction.

Thank you,
Roland


On Thu, Jun 5, 2014 at 9:06 PM, Roland Awusie <[email protected]>
wrote:

> Hi All,
>
> I had installed gnuradio on Fedora 20 on Lenovo ideadpad U430 laptop few
> months ago and now want to re-install it using the gnuradio build script to
> get the latest updates.I got the following error on the terminal either by
> using home or usr directory.
>
> I would be very grateful if anyone has seen this error before and can
> point me in the rigth direction.
>
>
>
>
>
>
>
>
>
>
>
>
>
> *[roland@localhost home]$ sudo wget
> http://www.sbrac.org/files/build-gnuradio
> <http://www.sbrac.org/files/build-gnuradio> && chmod a+x ./build-gnuradio
> && ./build-gnuradio --2014-06-05 00:03:11--
> http://www.sbrac.org/files/build-gnuradio
> <http://www.sbrac.org/files/build-gnuradio>Resolving www.sbrac.org
> <http://www.sbrac.org> (www.sbrac.org <http://www.sbrac.org>)...
> 67.212.80.242 Connecting to www.sbrac.org <http://www.sbrac.org>
> (www.sbrac.org <http://www.sbrac.org>)|67.212.80.242|:80... connected.HTTP
> request sent, awaiting response... 200 OK Length: 37394 (37K) [text/plain]
> Saving to:
> ?build-gnuradio?100%[======================================================================================================>]
> 37,394      --.-K/s   in 0.09s   2014-06-05 00:03:11 (401 KB/s) -
> ?build-gnuradio? saved [37394/37394] chmod: changing permissions of
> ?./build-gnuradio?: Operation not permitted*
>
> Thank you,
> Roland
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140605/804f4bec/attachment-0001.html>

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

Message: 4
Date: Sat, 7 Jun 2014 09:56:28 +0800 (GMT+08:00)
From: ??? <[email protected]>
To: [email protected]
Subject: [USRP-users] time_spec
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset=UTF-8

Hi everyone:
            Now i use the uhd api to write a program.I want to realize:
           
            ---------->(master usrpN210)send
            ---------->(slave usrpN210)send
Namely.two usrp send the first sample simultaneously after some times.
So,i use the command like this:
            uhd::tx_metadata_t md[tx_ant];
            md[i].has_time_spec=true;
            md[i].start_of_burst=true;
            md[i].end_of_burst=false;
            md[i].time_spec = uhd::time_spec_t(time_to_send);
But i find a phenomenon:if i set the time_to_send too small,when the program 
run,it will display so many "LLLLLLL".If i set the time_to_send too large,my 
program can't run normally.
            Can someone tell me what is the relationship between the 
time_to_send and the number of samples which to be send.Or others?
            Thanks.
Best regards,
W








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

Message: 5
Date: Sun, 8 Jun 2014 21:06:58 -0400
From: "Thierry Guichon" <[email protected]>
To: <[email protected]>
Subject: Re: [USRP-users] Inquiries on Ettus USRP E110 Hardware Driver
Message-ID: <56ABFD3B4EBB42E0868C5CF69A052F00@Tristan>
Content-Type: text/plain; charset="us-ascii"

As a matter of fact, everything is already pre-installed in  the E100/E110.
Not the latest version though.

I suggest to become  familiar with the way it works before trying to update
anything.

 

A serial port connection, an SSH connection or connecting the E110 directly
to a display and keyboard will work.

 

Sincerely

 

Thierry

 

  _____  

From: USRP-users [mailto:[email protected]] On Behalf Of
Hacker Fantastic via USRP-users
Sent: Sunday, June 08, 2014 5:51 AM
To: Chun Mein Soon
Cc: [email protected]; ahmad zuri sha'ameri
Subject: Re: [USRP-users] Inquiries on Ettus USRP E110 Hardware Driver

 

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>
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/b5f420a1/attachment-0001.html>

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

Message: 6
Date: Sun, 8 Jun 2014 20:11:43 -0500
From: GW <[email protected]>
To: [email protected]
Subject: [USRP-users] UHD support for National Instruments DAQ
        hardware
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"


I would like to configure GNU Radio to support a new source and sink device 
such as a National Instruments DAQ device.  Sort of like the audio sink except 
with faster sample rates.  Has anyone looked at developing a UHD driver for a 
general purpose DAQ device?  Is UHD even the right framework to developing such 
a driver?

If not, I would like to look into developing one.  I welcome any advice or 
pointers.

Thanks,
        
Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20140608/06f5a95e/attachment-0001.html>

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

Message: 7
Date: Mon, 9 Jun 2014 11:30:51 +0000
From: Metso Mikko <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] B210 as standalone transmitter?
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="us-ascii"

hi,

I am fairly new to gnuradio and we recently got an Ettus B210 to try with it. 
It seems to work ok , for example I can now generate an arbitrary data stream 
that is then read in a loop to be transferred from PC -> USB -> B210 -> RF.

As an FPGA designer I would like to have the arbitrary transmit baseband data 
stream be generated by the FPGA on B210, instead of a PC. Then it would be up 
converted and transmitted just as the current data originating from PC. This 
way after initial configuration, the B210 would be acting as a highly 
configurable, standalone signal generator, without a need for the USB 
connection (until we want to change some run-time parameters). Is this doable?

The Verilog source files for the current FPGA implementation are short of 
comments which makes it fairly difficult to follow. And I have not bumped into 
any documents regarding to the FPGA codes.

What might be the best transmit interface inside the FPGA to de-attach data 
source side and replace it with a self-made signal source instead? Any 
directions and/or instructions would be highly welcome.

Regards
mikko




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

Message: 8
Date: Mon, 9 Jun 2014 11:23:35 -0400 (EDT)
From: "Garver, Paul W" <[email protected]>
To: [email protected]
Subject: [USRP-users] B200 GPSDO Dimensions
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset=utf-8

What is the height of the B200 + GPSDO stack?  I can't find the dimensions of 
the GPSDO (P/N 783454-01) for the B200 and want to ensure it will clear my 
enclosure.

PWG



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

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 9
*****************************************

Reply via email to