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. Rx and Tx questuions ([email protected])
2. Audio_oss_sink issue with rx_voice.py (Daniel Artis)
3. Re: Rx and Tx questuions (Josh Blum)
4. Signal Strength by USRP2 (xvrs)
5. Re: Signal Strength by USRP2 (Tom Rondeau)
6. [ANN] UHD support for the Bitshark USRP RX daughterboard
(John Orlando)
----------------------------------------------------------------------
Message: 1
Date: Wed, 23 Feb 2011 21:52:02 +0000
From: [email protected]
To: [email protected]
Subject: [USRP-users] Rx and Tx questuions
Message-ID: <W9758317354238191298497922@webmail39>
Content-Type: text/plain; charset="utf-8"
Hi, I use USRP with FLEX900 daughterboard, and I want to build the basic Tx and
Rx block. Do you know how I?can switch Tx to Rx automaticly? or there have a
function or flag told me the Tx have done and I?can change the flag then to Rx
mode. If anyone have the answer I will be appreciate!
Best Regards!
USRP2-Poly
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20110223/291639ee/attachment-0001.html>
------------------------------
Message: 2
Date: Wed, 23 Feb 2011 13:55:04 -0800 (PST)
From: Daniel Artis <[email protected]>
To: USRP <[email protected]>
Cc: John Oliver <[email protected]>
Subject: [USRP-users] Audio_oss_sink issue with rx_voice.py
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Hi All,
So I can successfully use the tx_voice.py file with a USRP1 and a single RFX400
board. I verified this by using a spectrum analyzer and I saw a signal pulsing
at the frequency I input. When I try to use the rx_voice.py file though, I get
a runtimeerror in audio_oss.py.
When I run:
python rx_voice.py -f 400M -O hw:0,0 --rx-gain=5 -u1
or
python rx_voice.py -f 400M -O plughw:0,0 --rx-gain=5 -u1
I get this as my last lines:
File "/usr/lib/python2.6/site-packages/gnuradio/audio_oss.py", line 241, in snk
return _audio_oss.sink(*args, **kwargs)
RuntimeError: audio_oss_sink
Does this mean that audio_oss was never built? I can play the dial tone file
from my speakers just fine, so isn't that confirmation that audio_oss was built?
when I run
python rx_voice.py -f 400M --rx-gain=5 -u1
I get:
usrp_basic_rx: usrp_check_rx_overrun failed
uOread: usb_reap_async: usb_reap: reaping request failed, win error: The I/O
operation has been aborted because of either a thread exit or an application
request.
usrp_basic_rx: set_rx_enable(false) failed
I read that it's best to set the audio output, so it knows to play through the
speakers, is this correct? Does the results I got from not setting the audio
output mean that it's expecting the basic rx board? How should I resolve these
issues? Thanks for the help everyone.
Sincerely,
Daniel K. Artis
[email protected]
(310) 686-4134
------------------------------
Message: 3
Date: Wed, 23 Feb 2011 14:00:28 -0800
From: Josh Blum <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Rx and Tx questuions
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8
It should be automatic.
This link may be of use, see the rules regarding the antenna:
http://www.ettus.com/uhd_docs/manual/html/dboards.html#rfx-series
-josh
On 02/23/2011 01:52 PM, [email protected] wrote:
> Hi, I use USRP with FLEX900 daughterboard, and I want to build the basic Tx
> and Rx block. Do you know how I?can switch Tx to Rx automaticly? or there
> have a function or flag told me the Tx have done and I?can change the flag
> then to Rx mode. If anyone have the answer I will be appreciate!
>
> Best Regards!
>
> USRP2-Poly
>
>
>
>
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
Message: 4
Date: Fri, 25 Feb 2011 01:48:19 +1100
From: xvrs <[email protected]>
To: [email protected]
Subject: [USRP-users] Signal Strength by USRP2
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Dear all,
I have two quick questions:
1) How could I get the strength of the signal at a particular frequency?
Is that the amplitude of what we can get from usrp2_fft.py, or from
gr_plot_fft.py, or gr_plot_psd.py?
2) I am also wondering why these three fft plots show different amplitudes with
the same fft size of 1024?
Thanks all
Regards,
Xvrs
------------------------------
Message: 5
Date: Thu, 24 Feb 2011 11:20:58 -0500
From: Tom Rondeau <[email protected]>
To: xvrs <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] Signal Strength by USRP2
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On Thu, Feb 24, 2011 at 9:48 AM, xvrs <[email protected]> wrote:
> Dear all,
>
> I have two quick questions:
> 1) How could I get the strength of the signal at a particular frequency?
> Is that the amplitude of what we can get from usrp2_fft.py, or from
> gr_plot_fft.py, or gr_plot_psd.py?
By far the easiest way is to calibrate it against a known signal. If
you have a siggen, set it up to transmit a frequency at some amplitude
and see what amplitude you get out of it.
> 2) I am also wondering why these three fft plots show different amplitudes
> with the same fft size of 1024?
Mostly, different windows, but also because the gr_plot_fft is just
doing a full FFT of the signal whereas the usrp_fft and gr_plot_psd
are taking the actual PSDs, which are time-windowed (and overlapping)
segments of spectrum (to put it loosely...). The windows are also
different. The gr_plot_fft does not use a window, and the window in
gr_plot_psd is, IIRC, a Blackman window (not changeable without
editing the code in the current version). I can't remember what the
usrp_fft.py uses. Different windows have different properties and
result in different peak amplitudes.
Tom
> Thanks all
> Regards,
> Xvrs
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
------------------------------
Message: 6
Date: Thu, 24 Feb 2011 11:43:46 -0600
From: John Orlando <[email protected]>
To: [email protected], gnu <[email protected]>
Subject: [USRP-users] [ANN] UHD support for the Bitshark USRP RX
daughterboard
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
Epiq Solutions is pleased to announce that their Bitshark USRP RX
(BURX) daughterboard is now supported by the UHD. Similar to other
hardware supported by the UHD, this will provide a common PC-based
driver controlling the BURX daughterboard, and should work across the
entire suite of USRP platforms.
The BURX driver support in the UHD is currently part of a separate git
repo hosted at github. This repo is a clone of the UHD main repo from
2/22/2011, with a burx_support branch added in containing the BURX
support updates. Full details on cloning and setting up the
burx_support branch can be found on our wiki:
http://www.epiq-solutions.com/twiki/bin/view/Main/WebHome
Lastly, additional details of the BURX daughterboard can be found here:
http://www.epiq-solutions.com/product_detail.php?line=Bitshark&product=Bitshark%20USRP
Comments and testing feedback is welcome. We appreciate the patience
of everyone who has been waiting for this support to be added in, and
stay tuned for additional hardware and software announcements
throughout 2011.
--
John Orlando
CEO/System Architect
Epiq Solutions
www.epiq-solutions.com
------------------------------
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
End of USRP-users Digest, Vol 6, Issue 40
*****************************************
