Re: [Discuss-gnuradio] Problems with the examples

2008-02-11 Thread Johnathan Corgan
To clarify, there was one missing line.  Here is the snippet again,
with comments:

if __name__ == '__main__': # Execute if script invoked
as program
 tb = my_top_block()  # Create an instance
of a custom top block
 tb.start()  # Start
the flowgraph running in background thread
 raw_input("Press Enter to stop.")# Wait for user to hit enter
in foreground thread
 tb.stop()  # Tell
flowgraph to gracefully exit
 tb.wait()  # Wait for
it to do so

-- 
Johnathan Corgan
Corgan Enterprises LLC
http://corganenterprises.com/


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] Problems with the examples

2008-02-11 Thread Johnathan Corgan
On 2/11/08, Jose Emilio Gervilla Rega <[EMAIL PROTECTED]> wrote:

>  if __name__ == '__main__':
>try:
>my_top_block().run()
>except KeyboardInterrupt:
>pass
>
>  I think that it is ok and with these lines the program should stop by
> pushing ENTER but it doesn't.

In Python, a KeyboardInterrupt is caused by Ctrl-C, not by hitting any
key.  The above code snippet is acting as it should.

If you want the flowgraph to end with an Enter key:

if __name__ == '__main__':
tb.start()
raw_input("Press Enter to stop.")
tb.stop()
tb.wait()

-- 
Johnathan Corgan
Corgan Enterprises LLC
http://corganenterprises.com/


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] third party daughterboards

2008-02-11 Thread TomasOMaille

Hello,

I noticed that the guys at Open PCD have built a RFID sniffer for use with
GNU Radio

http://www.openpcd.org/rfiddump.0.html

I was wondering if there much third party hardware out there?

Tomas O'Maille
-- 
View this message in context: 
http://www.nabble.com/third-party-daughterboards-tp15413168p15413168.html
Sent from the GnuRadio mailing list archive at Nabble.com.



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] abs_top_srcdir?

2008-02-11 Thread Michael Dickens
I just checked in a fix for this issue, so please try updating to the  
latest SVN trunk.


"abs_top_YYY" -is- used internally in older autoconf such as found in  
Ubuntu 6.06 or 6.10, but it isn't placed in the list of substitution  
variables (i.e. for external use).  Adding these variables to the list  
of substitutions is simple, and "just doing it" (even twice) is OK  
because autoconf checks for duplicates. "make" and "make check" work  
(for me) on Ubuntu 6.10, 7.10, and OSX 10.5. - MLD



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


RE: [Discuss-gnuradio] abs_top_srcdir?

2008-02-11 Thread Clark Pope

> CC: [EMAIL PROTECTED]; discuss-gnuradio@gnu.org> From: [EMAIL PROTECTED]> To: 
> [EMAIL PROTECTED]> Subject: Re: [Discuss-gnuradio] abs_top_srcdir?> Date: 
> Sun, 10 Feb 2008 21:38:43 -0500> > On Feb 10, 2008, at 6:46 PM, Johnathan 
> Corgan wrote:> > We (well, I) recently checked in a fairly significant update 
> to our> > build system, which *should* have had no impact on existing> > 
> functionality.> > Yup. That's what it was. autotools in 6.06 does not define 
> > "abs_top_YYY", as does autotools for 7.10. Go figure. I'll find > another 
> way to do this, robustly. - MLD
 
Thanks, I've worked around for now by manually defining these. 
_
Need to know the score, the latest news, or you need your Hotmail®-get your 
"fix".
http://www.msnmobilefix.com/Default.aspx___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] Transmitting a file (txt,

2008-02-11 Thread Juha Vierinen
Hi,

Here is the quick hack that I wrote a while ago. It probably only
works with linux, and be sure that you have all the necessary programs
installed (check out README). Just stick some random wire antenna in
the sma port and you should hear music.

http://mep.fi/viewcvs/fmradio/?root=cvs

The original idea was to create a super WFM radio that would
simultaneously broadcast _many_ stations (you can probably fit about
35-70 music streams in a 8 MHz bandwidth), so that you could chose
what mp3 playlist you want to listen to by tuning your fm radio. But I
have lost interest in doing this, as I rarely listen to even one
stream of music :) I suspect that a very fast disk, plenty of
processors and a buffered and queued filesource block would be needed
to make the super mp3 broadcast system possible. I am planning to
write the filesource block soon, but I will use it for another
project.

juha

On Feb 11, 2008 1:30 PM,  <[EMAIL PROTECTED]> wrote:
> Juha, you said you have built wfm broadcasting system. I am trying to build 
> one myself and would really appreciate some guidlines. I am new to python and 
> would like to use some built-in python modules and scripts that gnuradio 
> already has. If you could please give a start up point I'll be grateful.
>
> Thank you
>
> --
> This message was sent on behalf of [EMAIL PROTECTED] at openSubscriber.com
> http://www.opensubscriber.com/message/discuss-gnuradio@gnu.org/8445716.html
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] enabling RX-A & RX-B on single daughterboard

2008-02-11 Thread Jason
Have you found the answer to your question? Is it now possible to enable
both RX-A and RX-B so that you could use them simultaneously?

Thanks!



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] Problems with the examples

2008-02-11 Thread Jose Emilio Gervilla Rega

Hello all!
 
I'm working on OFDM synchronization for GNURadio and we need a file to simulate 
the OFDM. I thought it would be a good way use the audio_to_file.py of the 
examples, but it doesn´t work. I speak to the microphone but when I run 
audio_play.py nothing is listened. I think the problem might be because when I 
push ENTER the execution of these examples should finish and it doesn't, it 
continue running until I kill the process (ctrl+c). It occurs with all the 
examples and I don't know what can be the problem because I've checked the code 
on the website and it is the same... The lines which should do it are:
 
if __name__ == '__main__':
  try:
  my_top_block().run()
  except KeyboardInterrupt:
  pass
 
I think that it is ok and with these lines the program should stop by pushing 
ENTER but it doesn't. The microphone problem must be other one but i`m starting 
to suspect that the file doesn't record fine because of this mistake. Can be 
useful for you that when I run audio_to_play.py it finishes when the file 
finishes(last a little of time) although it doesn't sound anything, and it 
doesn't stop if pushing ENTER.
 
I know these are very elemental doubts and problems but are stopping us of 
going on with our work and we are not able to solve it.
 
Thank you very much
_
Tecnología, moda, motor, viajes,…suscríbete a nuestros boletines para estar 
siempre a la última
http://newsletters.msn.com/hm/maintenanceeses.asp?L=ES&C=ES&P=WCMaintenance&Brand=WL&RU=http%3a%2f%2fmail.live.com___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] ninput_items from demodulator

2008-02-11 Thread Johnathan Corgan
On 2/11/08, Fasika Alemayehu <[EMAIL PROTECTED]> wrote:

> I have a module to demodulate packets received from a
> file source, and it works fine. I want to have a fixed
> number of inputs (1024) coming from the demodulator.

> But the problem is that evenif i dont get less than
> 1024 items, the input varies with the differenc calls
> to the method.

As your numbers show, using forecast will ensure that the GNU Radio
scheduler calls your work function with at least that many pending
input items to process.  You may get more than than, but you don't
have to process them.   Be sure to return from the work function with
the proper exit value indicating how many samples you actually did
process.  If you are using general_work(), also be sure you are
calling the consume function properly.

-- 
Johnathan Corgan
Corgan Enterprises LLC
http://corganenterprises.com/


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] Problem: Accessing RX-B of the basic Rx daughterboard

2008-02-11 Thread Jason Anders
Hi! Thanks for your reply. It was helpful!

However, I have another follow-up question. So, basically I won't be able to
access RX-A and RX-B simultaneously since I have to set the MUX everytime?
Is this correct?

Thanks!
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] Problem: Accessing RX-B of the basic Rx daughterboard

2008-02-11 Thread Karthik Vijayraghavan
Ah this is exactly what I have been grappling with as well. Basically
you need to set the MUX _such that_ you can access the two setting
simultaneously. If you have the gnuradio source you, look at the file
gnuradio-examples/multi-antenna/multi_scope.py

For more than one signal, you can no longer use the
usrp.determine_rx_mux_value(u,rx_subdev_spec) method. Instead you have
to set the MUX by hand. The crucial line is

self.u.set_mux(gru.hexint(0xf3f2f1f0))

This sets all the Q channels to zero (because of 0xf) and routes ADC1
to I1, ADC2 to I2 etc. To seperate them



On Feb 11, 2008 9:05 PM, Jason Anders <[EMAIL PROTECTED]> wrote:
>
> Hi! Thanks for your reply. It was helpful!
>
>  However, I have another follow-up question. So, basically I won't be able
> to access RX-A and RX-B simultaneously since I have to set the MUX
> everytime? Is this correct?
>
>  Thanks!
>



-- 
www.stanford.edu/~karthikv


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] Problem: Accessing RX-B of the basic Rx daughterboard

2008-02-11 Thread Karthik Vijayraghavan
Jason,

Ah this is exactly what I have been grappling with as well. Basically
you need to set the MUX _such that_ you can access the two setting
simultaneously. If you have the gnuradio source you, look at the file
gnuradio-examples/multi-antenna/multi_scope.py which tells you how you
can look at 4 signals at the same time using two BASIC-RX boards.For
more than one signal, you can no longer use the
usrp.determine_rx_mux_value(u,rx_subdev_spec) method. Instead you have
to set the MUX by hand. The crucial line in the example code is.

self.u.set_mux(gru.hexint(0xf3f2f1f0))

This sets all the Q channels to zero (because of 0xf) and routes ADC0
to I0, ADC1 to I1 etc. To separate them  you have the line

gr.deinterleave(gr.sizeof_gr_complex)

I have yet to try this out on my own program, but that is as far as I
understand it. I believe If you want to get 4 signals simultaneously
you need load a special FPGA image file, the details of which are
shown in the example. However for getting only 2 signals the standard
FGPA config is good enough (there is an earlier post on this somewhere
in the archive). Maybe others can correct me if I am wrong.

Karthik



On Feb 11, 2008 9:05 PM, Jason Anders <[EMAIL PROTECTED]> wrote:
>
> Hi! Thanks for your reply. It was helpful!
>
>  However, I have another follow-up question. So, basically I won't be able
> to access RX-A and RX-B simultaneously since I have to set the MUX
> everytime? Is this correct?
>
>  Thanks!
>



-- 
www.stanford.edu/~karthikv


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] minimizing interference with usrp

2008-02-11 Thread Matt Ettus

Juha Vierinen wrote:

Hi,

I have been doing some radio astronomy experiments with USRP using a
30 MHz dipole antenna (actually it is more of a riometer experiment).
I am running into various interference issues. E.g., at one point I
noticed that if my laptop power supply is too close to my USRP I get
switching power supply harmonics in my signal. At other times I have
been pretty sure that the inteference comes through my antenna.

  


I have found huge differences between laptop power supplies from the 
manufacturer of the laptop (like Lenovo, HP, etc.), and cheap 
replacement supplies made to look like the originals.  Once I was 
testing something on the USRP while the computer was attached to one of 
these supplies and I saw a huge mess on the spectrum analyzer.  I spent 
an hour trying to figure out what was happening, only to find that it 
was there even if there was no USRP hooked up at all -- it was all 
radiating from the power supply.


If you really need low noise, run the laptop off of its internal battery 
only.


Matt



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] minimizing interference with usrp

2008-02-11 Thread Juha Vierinen
Hi,

I have been doing some radio astronomy experiments with USRP using a
30 MHz dipole antenna (actually it is more of a riometer experiment).
I am running into various interference issues. E.g., at one point I
noticed that if my laptop power supply is too close to my USRP I get
switching power supply harmonics in my signal. At other times I have
been pretty sure that the inteference comes through my antenna.

Here is what I have been thinking to combat the interference problems:

1. Locate antenna at about 100-200 m away from any electronic devices
(except for the antenna preamp)
2. Locate USRP as far as possible from electronic devices (is 5m
really the maximum distance, or is there some other trick?)
3. Obviously filter and amplify signal properly before putting it in
4. Use well regulated and filtered power supplies for amplifiers and USRP

Anything else that I should take into account? I don't have that much
experience with minimizing interference, except for the things that I
have learned during the last couple of weeks while experimenting.

juha


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] ninput_items from demodulator

2008-02-11 Thread Fasika Alemayehu
Hi all,

I have a module to demodulate packets received from a
file source, and it works fine. I want to have a fixed
number of inputs (1024) coming from the demodulator.
What i did is i override the forcast method of
gr_block.
void
  usbm::forecast (int noutput_items,
  gr_vector_int
ninput_items_required)
  {
unsigned ninputs = ninput_items_required.size ();
for (unsigned i = 0; i < ninputs; i++)
  ninput_items_required[i] =1024 ;
  }

But the problem is that evenif i dont get less than
1024 items, the input varies with the differenc calls
to the method. 
Here is a sample of the input items from a demod
block.

number of items: 1027
--


number of items: 2047 
--


number of items: 1025 
--


number of items: 1024 
--


number of items: 2047 
--


number of items: 1024
--


number of items: 1026 
--


number of items: 2047 
--


number of items: 1025 
--


number of items: 2053 
--


Does this mean that the size of the output from the
demodulator block varies ? 

Fasika


  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 



___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] wfm_rcv_file.py?

2008-02-11 Thread Clark Pope

I saw in the archive that this file no longer works with the new coding 
standard. Before I embark on it, has anybody rewritten it yet? 
 
Thanks,
Clark
_
Climb to the top of the charts! Play the word scramble challenge with star 
power.
http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_jan___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] Transmitting a file (txt,

2008-02-11 Thread meggahertz
Juha, you said you have built wfm broadcasting system. I am trying to build one 
myself and would really appreciate some guidlines. I am new to python and would 
like to use some built-in python modules and scripts that gnuradio already has. 
If you could please give a start up point I'll be grateful. 

Thank you

--
This message was sent on behalf of [EMAIL PROTECTED] at openSubscriber.com
http://www.opensubscriber.com/message/discuss-gnuradio@gnu.org/8445716.html


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] Problem: Accessing RX-B of the basic Rx daughterboard

2008-02-11 Thread Jason Anders
Hi!

What command should I use when I want to access the received signals at port
RX-B of the Basix Rx daughterboard?
I have tried using usrp.source_c(1,my_block) but then an error results
saying that I cannot find usrp 1.

What I intended with that command was to access RX-B of the BASIC Rx
Daughterboard.

Your replies are greatly appreciated.

Thanks!
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


RE: [Discuss-gnuradio] Problems with the examples

2008-02-11 Thread Jose Emilio Gervilla Rega

So, my problem must be with the microphone used in the notebook. I use the 
integrated microphone and it doesn't record anything, might be I should use the 
command -I to let the program know that the source is the microphone, but how 
is it called in Linux? I mean, the line to call the program would be:
 
./audio_to_file.py -I (here how do I define the microphone in linux??) test.dat
 
Might be also linux configuration for the microphone, can anyone tell me what 
is the right one?
 
Thank you very much! > Date: Mon, 11 Feb 2008 10:16:47 -0800> From: [EMAIL 
PROTECTED]> To: [EMAIL PROTECTED]> Subject: Re: [Discuss-gnuradio] Problems 
with the examples> CC: discuss-gnuradio@gnu.org> > On 2/11/08, Jose Emilio 
Gervilla Rega <[EMAIL PROTECTED]> wrote:> > > if __name__ == '__main__':> > 
try:> > my_top_block().run()> > except KeyboardInterrupt:> > pass> >> > I think 
that it is ok and with these lines the program should stop by> > pushing ENTER 
but it doesn't.> > In Python, a KeyboardInterrupt is caused by Ctrl-C, not by 
hitting any> key. The above code snippet is acting as it should.> > If you want 
the flowgraph to end with an Enter key:> > if __name__ == '__main__':> 
tb.start()> raw_input("Press Enter to stop.")> tb.stop()> tb.wait()> > -- > 
Johnathan Corgan> Corgan Enterprises LLC> http://corganenterprises.com/
_
MSN Video. 
http://video.msn.com/?mkt=es-es___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio