On Tue, Nov 06, 2007 at 08:20:17PM -0500, Josh Blum wrote:
> Hello,
>
> I was thinking of an interesting feature for gnuradio: Suppose that the
> gnuradio framework could also support blocks written in python. Not
> hier-blocks, but actual data processing done in python. Meaning, one
> would wr
Hi All,
Does the architecture of Universal Software Radio Peripheral for GNU radio
support
frequency hopping? How easy is it, if not already supported, to customize GNU
radio to
support frequency hopping. What is involved in implementing it. Has anyone
implemented frequency hopping? If
Hello,
I was thinking of an interesting feature for gnuradio: Suppose that the
gnuradio framework could also support blocks written in python. Not
hier-blocks, but actual data processing done in python. Meaning, one
would write a python class. The class would have an io signature, and a
funct
As another data point: Sometimes this happens on OSX, and sometimes
it doesn't. On otherwise identical computers (Intel-iMac, 10.4.10,
latest updates, MacPorts for background libraries, includes, and
apps), with the only difference being the version of Python and
related python stuff (2.4
I am using 32-bit machine using Ubuntu. Thanks for your further
investigation.
Ruby
Eric Blossom wrote:
>
> On Tue, Nov 06, 2007 at 01:35:17PM -0800, Ruby Lin wrote:
>>
>> Hi all,
>>
>> I updated my gnuradio to gnuradio-3.1.0. And when I run
>> usrp_spectrum_sense.py, it gives the output li
On Tue, Nov 06, 2007 at 03:00:19PM -0800, Eric Blossom wrote:
> On Tue, Nov 06, 2007 at 01:35:17PM -0800, Ruby Lin wrote:
> >
> > Hi all,
> >
> > I updated my gnuradio to gnuradio-3.1.0. And when I run
> > usrp_spectrum_sense.py, it gives the output like:
> >
> > ==
>
Keith,
I just had the same thing happen about a month ago. Pretty much the same
error messages you report. I ended up sending it in to Matt. I would
email him directly to see if this is a possibility. On a bright note: I
just got it back and it works great. Matt was very straight about the
pos
On Tue, Nov 06, 2007 at 01:35:17PM -0800, Ruby Lin wrote:
>
> Hi all,
>
> I updated my gnuradio to gnuradio-3.1.0. And when I run
> usrp_spectrum_sense.py, it gives the output like:
>
> ==
> $ sudo ./usrp_spectrum_sense.py 400M 450M
> Using RX d'board A: TV Rx Rev 2
>
On Tue, Nov 06, 2007 at 11:45:59PM +0200, Aadil Volkwin wrote:
> Hi,
>
> Thanks for taking the time to answer my questions.
>
> I'd like to seek clarity on your first point, how am I losing the quadrature
> component?
You're using gr.complex_to_float, and then only using one of the two
output st
Hi all,
I updated my gnuradio to gnuradio-3.1.0. And when I run
usrp_spectrum_sense.py, it gives the output like:
==
$ sudo ./usrp_spectrum_sense.py 400M 450M
Using RX d'board A: TV Rx Rev 2
gain = 57.5
Segmentation fault
==
Could anyone g
On 11/6/07, Nirali Patel <[EMAIL PROTECTED]> wrote:
> If I use
>
> u._write_fpga_reg(FR_DEBUG_EN, bmFR_DEBUG_EN_RX_A | bmFR_DEBUG_EN_TX_A)
>
> it does not enable the Basic TX on side A.
You haven't enabled TX_A debug pins as outputs.
--
Johnathan Corgan
Corgan Enterprises LLC
http://corganenter
On Tue, Nov 06, 2007 at 12:46:02PM +0200, Aadil Volkwin wrote:
> Hi
>
> Attached is code i've used to write a signal to file and subsequently to
> plot the samples.
> additionally i've attached the plot.
>
> Can anyone tell me what may be causing the huge spike at the beginning of
> the data set?
Message: 2
Date: Wed, 17 Oct 2007 18:45:15 -0700
From: Eric Blossom <[EMAIL PROTECTED]>
Subject: Re: [Discuss-gnuradio] Help:How to print the payload in
benchmark_ofdm_tx.py
To: Archana Ragothaman <[EMAIL PROTECTED]>
Cc: discuss-gnuradio@gnu.org, Johnathan Corgan <[EMAIL PROTECTED]>
Message-
Jonathan,
Thanks for your response. I can see the ch0rx signal toggling on my Basic RX
in slot A using the following command
u = usrp.source_c(0,decim_rate=8,fpga_filename="mytestfile.rbf")
u._write_oe(0,0x,ox)# for enabling A side Basic RX
u._write_fpga_reg(FR_DEBUG_EN, bmFR_D
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please don't send attachments to the GNU radio mailing list.
It's a known issue that the USRP sends some spurious large amplitude
samples right after it is enabled. You can safely ignore them.
- -Dan
Aadil Volkwin wrote:
> Hi
>
> Attached is code i
15 matches
Mail list logo