[Discuss-gnuradio] Re: 'BoxSizer' object has no attribute 'AddStretchSpacer'

2009-03-19 Thread Jay Kumar
Hello Sir, Actually i was trying to install python-wxPython-2.8.9.1-1.el4.pp.src.rpm but somehow it could not be build.So i had to go with the wx-2.5.3-gtk2-ansi.Even i had tried with the wx-2.8.3-gtk2-ansi but python 2.4 (abi) is required.Can u just tell me what should i do??In which direct

[Discuss-gnuradio] Using one USRP

2009-03-19 Thread ali siddiqi
Hi I am trying to implement a cognitive radio system for dynamic spectrum access. I am trying to implement it in GNU radio. But the problem is that i have only one USRP at the moment with Basic RX and TX daughterboards. The setup consists of Station A transmitting to Station B. In order to be able

Re: [Discuss-gnuradio] Simple USRP Interface Code

2009-03-19 Thread Eric Blossom
On Wed, Mar 18, 2009 at 10:12:06AM -0700, isaacgerg wrote: > > Hi everyone, > I was wondering if anyone has written a small C++ application which is the > bare bones required to interface with the URSP. > > Thanks in advanced, > Isaac Isaac, Take a look at the version of usrp/host/apps/test_u

Re: [Discuss-gnuradio] tunnel.py buffer crash

2009-03-19 Thread Eric Blossom
On Thu, Mar 19, 2009 at 08:50:13PM -0700, yyzhuang wrote: > > I'm sorry. > > If we do ./tunnel and ping between two boxes over the air, both tx and rx > breaks after a few ICMP packets exchange. They don't break at the same time > though, but it does happen every time. If we do over channel emul

Re: [Discuss-gnuradio] tunnel.py buffer crash

2009-03-19 Thread yyzhuang
I'm sorry. If we do ./tunnel and ping between two boxes over the air, both tx and rx breaks right after a few ping. They don't break at the same time though, but it does happen every time. If we do over channel emulator (by connecting the antenna of USRP to the emulator), we can ping the two mac

Re: [Discuss-gnuradio] tunnel.py buffer crash

2009-03-19 Thread Eric Blossom
On Thu, Mar 19, 2009 at 08:21:43PM -0700, yyzhuang wrote: > > Is it possible a GNU Radio distribution problem? In the new lab we installed > the whole GNU Radio again. Thanks. > > Yanyan Can you more-or-less-reliably reproduce the problem? If so, how often does it occur? Every time? Once every

Re: OMAP3 (was Re: [Discuss-gnuradio] Discuss)

2009-03-19 Thread Eric Blossom
On Thu, Mar 19, 2009 at 06:18:53PM -0400, Philip Balister wrote: > Eric Blossom wrote: >>> >>> Philip mentioned in a previous post that Angstrom can be built with >>> libusb-1.12 as a workaround so we can look into some sort of kernel hacking >>> as well. But if there were a better approach than t

Re: [Discuss-gnuradio] tunnel.py buffer crash

2009-03-19 Thread yyzhuang
Is it possible a GNU Radio distribution problem? In the new lab we installed the whole GNU Radio again. Thanks. Yanyan Eric Blossom wrote: > > On Wed, Mar 18, 2009 at 10:36:17PM -0700, yyzhuang wrote: >> >> Hi Eric, >> >> We read through the code. gr_buffer is a circular/ring buffer, so when

Re: [Discuss-gnuradio] USRP Input Calibration / CIC Filter Response

2009-03-19 Thread Eric Blossom
On Thu, Mar 19, 2009 at 05:43:56PM -0400, Erich Stuntebeck wrote: > Hi, > > I'm trying to calibrate the USRP so I can get true dBm readings out of > it. I'm using an LFRX card with 16 decimation and a center frequency > of 2 MHz so I can look at the range from DC - 4 MHz. I hooked up a > signal ge

Re: [Discuss-gnuradio] USRP Input Calibration / CIC Filter Response

2009-03-19 Thread Stefan Bruens
On Thursday 19 March 2009 22:43:56 Erich Stuntebeck wrote: > Hi, > > I'm trying to calibrate the USRP so I can get true dBm readings out of > it. I'm using an LFRX card with 16 decimation and a center frequency > of 2 MHz so I can look at the range from DC - 4 MHz. I hooked up a > signal generator

OMAP3 (was Re: [Discuss-gnuradio] Discuss)

2009-03-19 Thread Philip Balister
Eric Blossom wrote: On Thu, Mar 19, 2009 at 03:49:14PM -0400, Dan wrote: 2009/3/16 Philip Balister phi...@balister.org So maybe there is a way to code libusrp to use the libusb1 interface without >directly accessing the file descriptor. The other approach is to try to extract the file descr

[Discuss-gnuradio] ATSC decode

2009-03-19 Thread Burak TUYSUZ
Hi all, I am new with GNUradio and USRP. I am using the atsc to decode hdtv but I have no luck.I get some sync errors from btl-fds.py >>> gr_fir_fff: using SSE atsc_field_sync_demux: synced (FIELD-1) at 426606 [delta = 426606] !!! atsci_equalizer: expected field sync, didn't find one atsc_field_sy

[Discuss-gnuradio] USRP Input Calibration / CIC Filter Response

2009-03-19 Thread Erich Stuntebeck
Hi, I'm trying to calibrate the USRP so I can get true dBm readings out of it. I'm using an LFRX card with 16 decimation and a center frequency of 2 MHz so I can look at the range from DC - 4 MHz. I hooked up a signal generator and swept it through the DC - 4 MHz range at 100 kHz intervals and gen

Re: [Discuss-gnuradio] Discuss

2009-03-19 Thread Eric Blossom
On Thu, Mar 19, 2009 at 03:49:14PM -0400, Dan wrote: > 2009/3/16 Philip Balister phi...@balister.org > > > > > >So maybe there is a way to code libusrp to use the libusb1 interface > > without >directly accessing the file descriptor. > > > > >The other approach is to try to extract the file descri

Re: [Discuss-gnuradio] /gnuradio-examples/python/digital/transmit_path.py and bitrate Question?

2009-03-19 Thread Eric Blossom
On Thu, Mar 19, 2009 at 02:28:08PM -0400, w w wrote: > What's confusing for me is that I see the bitrate variable (it seems to have > a profound importantance) but it looks to me like it never gets assigned to > a block. The following is line 119 from transmit_path.py. In my mind the > function

Re: [Discuss-gnuradio] Discuss

2009-03-19 Thread Dan
2009/3/16 Philip Balister phi...@balister.org > > >So maybe there is a way to code libusrp to use the libusb1 interface > without >directly accessing the file descriptor. > > >The other approach is to try to extract the file descriptor from > libusb-compat. > > >Finally, it looks like you can omit

Re: [Discuss-gnuradio] Constant carrier digital transmission

2009-03-19 Thread Ed Criscuolo
William Harding wrote: I would like to implement a module which keeps a constant carrier running and transfers packets of data at different times. In other words, using ASK (or OOK) modulation, I would like to always be transmitting ones (carrier is at full amplitude) except for certain perio

Re: [Discuss-gnuradio] /gnuradio-examples/python/digital/transmit_path.py and bitrate Question?

2009-03-19 Thread w w
What's confusing for me is that I see the bitrate variable (it seems to have a profound importantance) but it looks to me like it never gets assigned to a block. The following is line 119 from transmit_path.py. In my mind the function of lines 119-121, is to assign/derive values for bitrate, in

Re: [Discuss-gnuradio] starting with usrp2_fft.py

2009-03-19 Thread Eric Blossom
On Thu, Mar 19, 2009 at 09:28:36AM -0700, leferman wrote: > > I am having a similar problem. I used ethtool to disable the pause > parameters for this interface; here is the output: > sudo ethtool -a eth1 > Pause parameters for eth1: > Autonegotiate:off > RX: off > TX:

Re: [Discuss-gnuradio] /gnuradio-examples/python/digital/transmit_path.py and bitrate Question?

2009-03-19 Thread Eric Blossom
On Thu, Mar 19, 2009 at 09:27:03AM -0700, Johnathan Corgan wrote: > 2009/3/19 w w : > > > I've been trying to analyse the transmit_path.py script and stumped with the > > bitrate value.   I see bitrate being brought in from the options and also > > derived from pick_bitrate but I don't see where s

[Discuss-gnuradio] Constant carrier digital transmission

2009-03-19 Thread William Harding
I would like to implement a module which keeps a constant carrier running and transfers packets of data at different times. In other words, using ASK (or OOK) modulation, I would like to always be transmitting ones (carrier is at full amplitude) except for certain periods where I will "pause" the

RE: [Discuss-gnuradio] starting with usrp2_fft.py

2009-03-19 Thread leferman
I am having a similar problem. I used ethtool to disable the pause parameters for this interface; here is the output: sudo ethtool -a eth1 Pause parameters for eth1: Autonegotiate: off RX: off TX: off But I still get this error when i run tx_samples: sudo ./tx_samples -

Re: [Discuss-gnuradio] /gnuradio-examples/python/digital/transmit_path.py and bitrate Question?

2009-03-19 Thread Johnathan Corgan
2009/3/19 w w : > I've been trying to analyse the transmit_path.py script and stumped with the > bitrate value.   I see bitrate being brought in from the options and also > derived from pick_bitrate but I don't see where somthing is being done with > it. It is assigned in transmit_path.py, line 1

Re: [Discuss-gnuradio] bad usrp followup 2

2009-03-19 Thread ematlis
Thanks! eric On Wed, 18 Mar 2009, Eric Blossom wrote: On Wed, Mar 18, 2009 at 06:12:22PM -0400, emat...@nd.edu wrote: I discovered that F501 is measuring as an open; I take it that this is a fuse, and probably it has blown. Can anybody supply me with the part specification so I can replace i

Re: [Discuss-gnuradio] tunnel.py buffer crash

2009-03-19 Thread Eric Blossom
On Wed, Mar 18, 2009 at 10:36:17PM -0700, yyzhuang wrote: > > Hi Eric, > > We read through the code. gr_buffer is a circular/ring buffer, so when > reading/writing through it, we need to take modular into account. The assert > error, it's line 125 in gr_buffer.h > (gnuradio/gnuradio-core/src/lib/

Re: [Discuss-gnuradio] some results about D8PSK (problems)

2009-03-19 Thread Bill Stevenson
Hi Stefan, Please give me sometime and I will try that program for sure! Do you know where the bug is located in mpsk block? Thanks! Bill From: Stefan Brüns To: discuss-gnuradio@gnu.org Sent: Thursday, March 19, 2009 7:18:28 AM Subject: Re: [Discuss-gnuradio

Fwd: [Discuss-gnuradio] Re: linkedin group

2009-03-19 Thread Steve Totaro
Forgot to send to list. -- Forwarded message -- From: Steve Totaro Date: Thu, Mar 19, 2009 at 10:00 AM Subject: Re: [Discuss-gnuradio] Re: linkedin group To: Angela Kahealani On Thu, Mar 19, 2009 at 7:47 AM, Angela Kahealani wrote: > Dimitris Symeonidis wrote: > >> I just

[Discuss-gnuradio] /gnuradio-examples/python/digital/transmit_path.py and bitrate Question?

2009-03-19 Thread w w
I've been trying to analyse the transmit_path.py script and stumped with the bitrate value. I see bitrate being brought in from the options and also derived from pick_bitrate but I don't see where somthing is being done with it. I know that the bitrate is being used but for the life of me I can

Re: [Discuss-gnuradio] linkedin group

2009-03-19 Thread Philip Balister
Dimitris Symeonidis wrote: I just created a group called "GNU Radio Users" in LinkedIn. The URL is: http://www.linkedin.com/groups?gid=1852751 Users can join without a permission. I hope you like it Dimitris Symeonidis There seems to be some confusion about the linkedin group. Linkedin as

Re: [Discuss-gnuradio] Can threading disturb sensing continuety

2009-03-19 Thread Ed Criscuolo
kaleem ahmad wrote: 3- Can you suggest some different way to solve this problem, The problem is simply to calculate the cycle time of some system which is already working in the environment Since your unknown FSK signal has a regular cycle time, it should be relatively easy to detect. Fo

Re: [Discuss-gnuradio] Re: linkedin group

2009-03-19 Thread Jason
Angela Kahealani wrote: Dimitris Symeonidis wrote: I just created a group called "GNU Radio Users" in LinkedIn. The URL is: http://www.linkedin.com/groups?gid=1852751 Users can join without a permission. I hope you like it Not in the least. The LAST thing ANYone needs is to have to agree to

[Discuss-gnuradio] Can threading disturb sensing continuety

2009-03-19 Thread kaleem ahmad
Hello every one, I am using USRP1 with RFX2400 daughter card. I have a system (any state of the art system, let say Atmel's narroband FSK which works in 2.4 GHz band) transmitting a fixed packet cyclically (let say cycle time = T ms). I want to use USRP system to sense the spectrum and calcu

Re: [Discuss-gnuradio] some results about D8PSK (problems)

2009-03-19 Thread Stefan Brüns
Hi Bill, I mentioned some problems with carrier offsets between different USRPs (or daughterboards, for RFX non-MIMO boards) when you reported on DBPSK. I found that error rate vastly improved when I factored the offset directly into the frequency arguments of the benchmark_{rx,tx}.py programs.