[Discuss-gnuradio] Failed to set RF frequency

2008-11-14 Thread Bruhtesfa Ebrahim
Hey all,

I am still checking out whether my USRP is working correctly in both
transmit and receive modes or not.

The problem is sometimes when i run the transmitter or receiver codes, the
USRP fails to set the RF frequency of my transceivers, and at other times it
works. I don't know what is causing this error.

Could somebody suggest me a solution? -Tks

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


[Discuss-gnuradio] GNU-Radio API

2008-11-14 Thread Pedro Sánchez Canal

I'm starting with GNU-Radio in order to do my final thesis and I've been 
working with some of the examples of the lastest version. I have some problems 
finding information about certain classes that doesn't appear in Doxygen 
GNU-Radio API. Do you know a newer API??? What example do yo think is going to 
be better for a newbie in order to try to connect two computers through USRP??

Thanx in advance

Ptr


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


[Discuss-gnuradio] Eric's schedule

2008-11-14 Thread Eric Blossom
FYI, I'll be off-list and mostly out of communication for the next 
4 weeks.  If any administrative issues come up while I'm gone, please
contact Johnathan Corgan [EMAIL PROTECTED].  

Have fun!
Eric


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


[Discuss-gnuradio] firmware update of usrp2, wiki- update?

2008-11-14 Thread Mattias Kjellsson

Hi list,

I finally got my hands on an sd-card reader/writer, and as I have been 
trying to get a hold of one for some time I was eager to update my 
firmware I jumped straight at the FAQ. Where I was discouraged by the 
fact that I have no idea about what device I'm using. Anyway, an answer 
is almost always a google away, so I found this link 
http://vic.gedris.org/linux-UsbMassStorage/ which tells you to do the 
following steps to determine which device you would like to flash.


1. Install sg3-utils package
$sudo apt-get update
$sudo apt-get install sg3-utils

2. List the raw scsi- devices on your system
$sg_scan -i

3. Have a look at the list printed out, and determine which SCSI- device 
is most likely your USB- card reader/writer.


4. Run sg_map to see what SCSI- device is associated with the USB sdcard 
r/w- device.

$sg_map


Thought this might be something for the wiki- page... Instead of having 
just a warning, there could be a warning and a solution  =;o]. But since I


Cheers!
Mattias Kjellsson



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


Re: [Discuss-gnuradio] Re: Soft-DVB DVB-T transmitter

2008-11-14 Thread Martin DvH

On Tue, 2008-11-11 at 08:26 +0100, Vincenzo Pellegrini wrote:
 Martin ,
 sorry for the delay. My exams seem to have gone well even if it's not
 official yet.
Great
  I also had to do a demo for a company I have a temporary
 contract with for developing some gnuradio based gsm-r security
 sentinels. Also the demo was smooth. (i already listed the project on
 the gnuradio wiki)
Good work.
 so i really hope i'll be able to prepare the 8Mhz stream for you
 within the next 2/3 days. Would this still be useful?
Yes it really would.

I am also really looking forward for the sources.
One of the things I am planning to do is use the structure of your code
as a basis for a DVB-T receiver.
It is always easier debugging a receiver when you can make a full loop.
(transmitter and receiver back-to-back)

Greetings,
Martin
 2008/11/3, Martin DvH [EMAIL PROTECTED]:
 
  On Mon, 2008-11-03 at 14:13 +0100, Martin DvH wrote:
 
 
 
  
 
Van: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]
  Namens Vincenzo Pellegrini
Verzonden: maandag 3 november 2008 0:16
Aan: Martin DvH
CC: discuss-gnuradio
Onderwerp: [Discuss-gnuradio] Re: Soft-DVB DVB-T transmitter


This is Great... :)

Yup, the playback cannot be smooth because of the wrong throughput,
  definitely.
Did you use the USRP1 with interpolation factor = 16 ?
  Yes I did.

I can prepare a modulated signal with the correct throughput for
  you.. this is not a problem... :)

  Please do, this would be great.
what hard disc are you playing your signal back from?
 
  Internal 2.5 harddisk of my acer 6930 notebook (Aspire 6930G-734G32BN
  LX.AVB0X.135)
  2.5 320GB HDD 5400rpm, SATA
  I checked now. It is a:
  Western digital Scorpio 320 GB SATA (WDC WD3200BEVT-22ZCT0)
  2.5-inch SATA Hard Drive 320 GB, 3 Gb/s, 8 MB Cache, 5400 RPM
 
  Benchmark from tomshardware (h2benchw 3.6):
  http://www.tomshardware.com/charts/2-5-hard-drive-charts/Minimum-Read-Transfer-Performance,687.html
  minimum read transfer rate 33.5 MB/sec
  average read transfer rate 52.2 MB/sec
  maximum read transfer rate 68.2 MB/sec
 
 
 
  I am not at home right now So I can't check the exact brand and model of
  the
  harddisk.
  It can do around 38 MB/sec so this is just enough (required 32 MB/sec)
 
  I also have 4GB of memory in this notebook, so I think it will buffer the
  complete file.
 
  I had to use my notebook because with my desktop PC (ASrock
  939-DUAL-SATA2)
  The USB TX bandwidth is less then 32 MB/sec.
  (Which is strange because I CAN receive 32 MB/sec)
  I get UuUuUu on this machine when useing interpolation 16, so unusable.
 
  Regards,
  Martin
 

regards

vincenzo


2008/11/3 Martin DvH [EMAIL PROTECTED]
 
 
 
 Hi,
 
   In fact: 8 complex Msps implement a 7 MHz channel while
  9.142857143
   complex Msps implement an 8 MHz channel.
   Just try to go as close as possible to such sampling
  frequency by
   using USRP2 and let me know what happens... it could
  turn out that we
   need a resampler block.
  So if I use a fractional rate resampler with interpolation
  factor
  10/8=1.25 I get a 7 Mhz channel with 10 Msps samplerate.
  If I use a fractional rate resampler with interpolation
  factor
  10/9.142857143=1.09375 I get a 8 Mhz channel with 10 Msps
  samplerate
 
  If I use a fractional rate resampler with DECIMATION
  factor
  9.142857143/8=8/7=1.142857143 I get a 8 Mhz channel with 8
  Msps
  samplerate with the out-of-band skirts folded back at the
  sides.
 
  Would be interesting to see if this last one works with a
  USRP1.
 
  I'll let you know how the experiments go.
 
 I resampled and scaled your ofdm_40.dump file so it now will
  use 8 Mhz bandwidth with a 8 Msps samplerate.
 The reception never can be perfect this way but it seems
  good enough for
 tests.
 
 My USB DVB-T receiver receives the transport stream without
  problems.
 Mplayer playes the stream without problem for two loops and
  then crashes
 with a broken frame.
 My standalone settopbox DVB-T receiver now also receives the
  stream.
 (8 MHz channel on UHF)
 It has big problems displaying it. Sound is only a chop of
  sound now and
 then and video stops, then runs for a second, then stops
  again.
 
 I think this is because the timestamps and framerate
  (playout speed)
 don't match the data throughput of the MPEG stream anymore.
 (It is getting the stream too fast)
 
 I put my resampled RF file at:
 
  

[Discuss-gnuradio] Jack 1.9 official release

2008-11-14 Thread Bob McGwier
“

Future Jack2 will be based on C++ jackdmp code base. Jack 1.90 is the  
renaming of jackdmp and the result of a lot of developments started  
after LAC 2008.
 
What is new:
 
- waf based build system : Nedko Arnaudov, Grame for preliminary OSX  
support
- control API, dbus based server control access : Nedko Arnaudov, Grame
- NetJack2 components (in progress)  : jack_net backend, netmanager,  
audioadapter, netadapter : Romain Moret, Grame
- code restructuring to help port on other architectures : Michael Voigt
- code cleanup/optimization : Tim Blechmann
- improve handling of server internal clients that can now be loaded/ 
unloaded using the new server control API : Grame
- a lot of bug fix and improvements
 
Jack 1.90 (API compatible with Jack 0.109.2) is now distributed in 2  
different versions:
 
Source code only:
 
http://www.grame.fr/~letz/jack-1.9.0.tar.bz2
http://www.grame.fr/%7Eletz/jack-1.9.0.tar.bz2 
 
Source code with OSX 32/64bits and Windows binaries:
 
http://www.grame.fr/~letz/jack-1.9.0.tgz
http://www.grame.fr/%7Eletz/jack-1.9.0.tgz 
 
Stéphane 

 

“

 

 

ARRL SDR Working Group Chair

Member: ARRL, AMSAT, AMSAT-DL, TAPR, Packrats,

NJQRP, QRP ARCI, QCWA, FRC.

 Don't despair, not even over the fact that you don't despair. , Kafka

 

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


Re: [Discuss-gnuradio] Can't transmit from USRP2

2008-11-14 Thread Mattias Kjellsson
Today I updated gnuradio to current svn9988. And while doing that I also 
downloaded the binary package of mb-gcc and built the firmware- files, 
successfully thanks to the wiki and a well known search- engine.


The new firmware was loaded onto the sd- card successfully(?) is there 
supposed to be some output from u2_flash_tool, I can't locate the source 
for it, so I can't check for myself. But since I could run find_usrps 
with the (probably) new firmware, I guess it went fine.


I then tried all the test- programs, and they ran fine (find_usrps, 
tx_sample, ... from usrp2/host/apps/), before lunch, but when I got back 
from lunch they didn't.


I simply can't transmit according to my hardware oscilloscope. Although 
I see packages flowing on my eth0- device (using wireshark).


And when I try rx_streaming_samples (with a signal- generator as source, 
generating a 100kHz sine) I suddenly receive a lot of noise. Looking at 
the fft of the received signal one could say that it _might_ be a 
sinusoid in there, but very weak. But only after lunch, before lunch the 
received signal was a noise free sinus of 100kHz...


The only thing that is working as expected after I got back is 
find_usrps. I think I'll never eat lunch again ;)


I'm out of ideas of how to solve this. Suggestions of things to try 
and/or check for, no matter how simple would be appreciated.


BR
//Mattias Kjellsson




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


[Discuss-gnuradio] When will the WBX be available?

2008-11-14 Thread hanwen
Hello Matt,

I didn't see the WBX0510 board on the Orde Page of your website. Is it
avalable for order now?

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


Re: [Discuss-gnuradio] Can't transmit from USRP2, version2.

2008-11-14 Thread Mattias Kjellsson


Today I updated gnuradio to current svn9988. And while doing that I also 
downloaded the binary package of mb-gcc and built the firmware- files, 
successfully thanks to the wiki and a well known search- engine.


The new firmware was loaded onto the sd- card successfully(?) is there 
supposed to be some output from u2_flash_tool, I can't locate the source 
for it, so I can't check for myself. But since I could run find_usrps 
with the (probably) new firmware, I guess it went fine.


I then tried all the test- programs, and they ran fine (find_usrps, 
tx_sample, ... from usrp2/host/apps/), before lunch, but when I got back 
from lunch they didn't.


I simply can't transmit according to my hardware oscilloscope. Although 
I see packages flowing on my eth0- device (using wireshark).


And when I try rx_streaming_samples (with a signal- generator as source, 
generating a 100kHz sine) I suddenly receive a lot of noise. Looking at 
the fft of the received signal one could say that it _might_ be a 
sinusoid in there, but very weak. But only after lunch, before lunch the 
received signal was a noise free sinus of 100kHz...


The only thing that is working as expected after I got back is 
find_usrps.  Althoug, I need to run it twice to make it find my usrp2... 
I think I'll never eat lunch again ;)


I'm out of ideas of how to solve this. Suggestions of things to try 
and/or check for, no matter how simple would be appreciated.


BR
//Mattias Kjellsson




___
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


Re: [Discuss-gnuradio] Failed to set RF frequency

2008-11-14 Thread Johnathan Corgan
On Fri, 2008-11-14 at 10:27 +0100, Bruhtesfa Ebrahim wrote:

 I am still checking out whether my USRP is working correctly in both
 transmit and receive modes or not.
 
 The problem is sometimes when i run the transmitter or receiver codes,
 the USRP fails to set the RF frequency of my transceivers, and at
 other times it works. I don't know what is causing this error.
 
 Could somebody suggest me a solution? -Tks

You'll need to be a lot more specific about your problem for anyone to
be able to help you.

-Johnathan




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


Re: [Discuss-gnuradio] Running usrp2_wfm_rcv.py

2008-11-14 Thread Catalin Lacatus

Hello,

I attached the results of svn info for:

gnuradio
usrp2_wfm_rcv.py
usrp2_fft.py

The reversions are below.


gnuradio

Repository Root: http://gnuradio.org/svn

Repository UUID: 221aa14e-8319-0410-a670-987f0aec2ac5

Revision: 9900

Node Kind: directory

Schedule: normal

Last Changed Author: jcorgan

Last Changed Rev: 9863

Last Changed Date: 2008-10-26 23:09:27 -0400 (Sun, 26 Oct 2008)


usrp2_wfm_rcv.py

[EMAIL PROTECTED]:/home/gnuradio/gnuradio# svn info

Path: .

URL: http://gnuradio.org/svn/gnuradio/trunk

Repository Root: http://gnuradio.org/svn

Repository UUID: 221aa14e-8319-0410-a670-987f0aec2ac5

Revision: 9900

Node Kind: directory

Schedule: normal

Last Changed Author: eb

Last Changed Rev: 9878

Last Changed Date: 2008-10-27 12:36:52 -0400 (Mon, 27 Oct 2008)



usrp2_fft.py

[EMAIL PROTECTED]:/home/gnuradio/gnuradio/gr-utils/src/python# svn info

Path: .

URL: http://gnuradio.org/svn/gnuradio/trunk/gr-utils/src/python

Repository Root: http://gnuradio.org/svn

Repository UUID: 221aa14e-8319-0410-a670-987f0aec2ac5

Revision: 9900

Node Kind: directory

Schedule: normal

Last Changed Author: jcorgan

Last Changed Rev: 9864

Last Changed Date: 2008-10-26 23:32:36 -0400 (Sun, 26 Oct 2008)


Please let me know how I can solve this problem.

Thank you,

Catalin

Johnathan Corgan wrote:

On Thu, Nov 13, 2008 at 5:48 AM, Catalin LACATUS
[EMAIL PROTECTED] wrote:

  

-I tried to run usrp2_wfm_rcv.py to test my USRP2 with a BasicRX board and I
got the following error.
¨AttributeError: 'usrp2_source_32fc_sptr' object has no attribute
'adc_rate'¨



Could you please confirm which repository revision of software you are
using?  Change into the top level directory that you checked out the
source code into, and type:

$ svn info

On the surface, this looks like a version mismatch between the
usrp2_fft.py script and the rest of GNU Radio.  It could be other
things as well, however.

-Johnathan
  




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


Re: [Discuss-gnuradio] GNU-Radio API

2008-11-14 Thread Johnathan Corgan
On Fri, Nov 14, 2008 at 1:50 AM, Pedro Sánchez Canal
[EMAIL PROTECTED] wrote:

 I'm starting with GNU-Radio in order to do my final thesis and I've been 
 working with some of the examples of the lastest version. I have some 
 problems finding information about certain classes that doesn't appear in 
 Doxygen GNU-Radio API. Do you know a newer API??? What example do yo think is 
 going to be better for a newbie in order to try to connect two computers 
 through USRP??

You can create fresh docs on your own system by adding
--enable-doxygen --enable-html-docs to the configure command during
compile.

Not sure what you mean by connect two computers.  You can do TCP/IP
networking between two computers with the tunnel.py application in the
examples/python/digital directory.  For a simple one way demonstration
of BPSK with bit error rate testing, you can try the scripts in
examples/python/digital-bert

-Johnathan


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


Re: [Discuss-gnuradio] firmware update of usrp2, wiki- update?

2008-11-14 Thread Johnathan Corgan
On Fri, Nov 14, 2008 at 2:00 AM, Mattias Kjellsson [EMAIL PROTECTED] wrote:

 Thought this might be something for the wiki- page... Instead of having just
 a warning, there could be a warning and a solution  =;o]. But since I

Go ahead and update it, that's what wikis are for.

login: guest
password: gnuradio

-Johnathan


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


Re: [Discuss-gnuradio] Can't transmit from USRP2

2008-11-14 Thread Johnathan Corgan
On Fri, Nov 14, 2008 at 7:14 AM, Mattias Kjellsson [EMAIL PROTECTED] wrote:

 Today I updated gnuradio to current svn9988. And while doing that I also
 downloaded the binary package of mb-gcc and built the firmware- files,
 successfully thanks to the wiki and a well known search- engine.

You will also need to either build or download the FPGA firmware.

 The new firmware was loaded onto the sd- card successfully(?) is there
 supposed to be some output from u2_flash_tool, I can't locate the source for
 it, so I can't check for myself.

There is no output upon success.  You can re-run the same command, but
use -v instead of -w to verify the SD card contents match the file you
copied into it.

-Johnathan


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


Re: [Discuss-gnuradio] Running usrp2_wfm_rcv.py

2008-11-14 Thread Johnathan Corgan
On Fri, Nov 14, 2008 at 7:53 AM, Catalin Lacatus
[EMAIL PROTECTED] wrote:

 I attached the results of svn info for:

Thanks.  While it looks like your repository is in order, the version
of the Python script you are running doesn't appear to match the
version of the USRP2 library that is actually installed on the system.

Other people who have recently reported similar issues as you have
solved it by doing a fresh rebuild and reinstallation of the code.
You can do this either by checking out a fresh version of the trunk,
or, by running 'make distclean', then repeating the usual steps for
configuration and installation.

-Johnathan


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


[Discuss-gnuradio] Problems with the usrp_rx_cfile.py, usrp_fft.py and usrp_oscope.py and RFID signals

2008-11-14 Thread Marco Bottino
Hello,
I am a student and I am doing my thesis project on the RFID protocols.
At the present time, with the USRP, I am trying to catch the signal between a
reader and a tag RFID.
As reader I am using an OpendPCD (using the firmware for the Mifare Classic
protocol) and as card a Mifare Classic Card.

Because of I am a very beginner of USRP and all the rest, I am using the
programs usrp_fft.py and usrp_oscope.py and the usrp_rx_cfile.py program with
another program called Baudline to analyse the spectrum.

My problem is that I can easily see in the frequency domain, using usrp_fft, the
carrier at 13.561Mhz, but not the subcarrier that should be a 847KHz modulation
of the carrier (probably covered by noise) even if I try to use a baseRX
daughterboard instead of the LFRX. Moreover, in the time domain (with the
usrp_oscope), I cannot recognize anything interesting.

As it isn't enough, with the usrp_rx_cfile and the program baudline I cannot
recognize neither the carrier: my opinion is that it is caused by a wrongly
interpretation of the bit-length of the samples (and for this I should need a
confirmation that the output samples are 16 bit-length). That program supports
these formats: alaw ulaw s8 u8 le16 be16 le32f be32f. Does anybody know wich is
the format I should use?

Probably I'm using wrongly the hardware and the software I have...

Could somebody suggest me a solution? Any kind of help will be absolutely well
appreciated!

thank you,

Marco


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


[Discuss-gnuradio] Failed make check on gr_top_block_sptr_connect

2008-11-14 Thread Petzold, Mark C.
I am attempting to install GNU radio on Ubuntu 8.10, 2.6.27-7 kernel on an i686 
computer.  I get the following error (4 times).

How do I get around this, and will it still run properly?

==
ERROR: test_loopback_003 (__main__.qa_atsc)
--
Traceback (most recent call last):
  File ./qa_atsc.py, line 209, in test_loopback_003
self.tb.connect(src, rand, rs_enc, inter, trellis, softds, viterbi, 
deinter, rs_dec, derand, dst)
  File 
/home/mcpetzold/gnuradio/gnuradio-core/src/python/gnuradio/gr/top_block.py, 
line 99, in connect
self._connect(points[i-1], points[i])
  File 
/home/mcpetzold/gnuradio/gnuradio-core/src/python/gnuradio/gr/top_block.py, 
line 105, in _connect
dst_block.basic_block(), dst_port)
  File 
/home/mcpetzold/gnuradio/gnuradio-core/src/lib/swig/gnuradio_swig_py_runtime.py,
 line 1469, in connect
return _gnuradio_swig_py_runtime.gr_top_block_sptr_connect(*args)
NotImplementedError: Wrong number of arguments for overloaded function 
'gr_top_block_sptr_connect'.
  Possible C/C++ prototypes are:
connect(boost::shared_ptr gr_top_block  *,gr_basic_block_sptr)
connect(boost::shared_ptr gr_top_block  
*,gr_basic_block_sptr,int,gr_basic_block_sptr,int)


--
Ran 4 tests in 1.761s

FAILED (errors=4)
FAIL: run_tests
===
1 of 1 tests failed
===
make[4]: *** [check-TESTS] Error 1
make[4]: Leaving directory `/home/mcpetzold/gnuradio/gr-atsc/src/python'
make[3]: *** [check-am] Error 2
make[3]: Leaving directory `/home/mcpetzold/gnuradio/gr-atsc/src/python'
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory `/home/mcpetzold/gnuradio/gr-atsc/src'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/home/mcpetzold/gnuradio/gr-atsc'
make: *** [check-recursive] Error 1

Thanks,

Mark C. Petzold, Ph.D.
Associate Professor
Department of Electrical and Computer Engineering, ECC 211
St. Cloud State University
720 Fourth Ave. South
St. Cloud, MN  56301
(320) 308-4182
[EMAIL PROTECTED]


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


Re: [Discuss-gnuradio] Failed make check on gr_top_block_sptr_connect

2008-11-14 Thread Johnathan Corgan
On Fri, 2008-11-14 at 12:19 -0600, Petzold, Mark C. wrote:

 I am attempting to install GNU radio on Ubuntu 8.10, 2.6.27-7 kernel on an 
 i686 computer.  I get the following error (4 times).

Which version of the software are you trying to install?

 How do I get around this, and will it still run properly?

Recompile, but add --disable-gr-atsc to the configure command.

-Johnathan




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


Re: [Discuss-gnuradio] When will the WBX be available?

2008-11-14 Thread Matt Ettus

hanwen wrote:

Hello Matt,
 
I didn't see the WBX0510 board on the Orde Page of your website. Is it 
avalable for order now?



The WBX0510 has been delayed due to a problem with IQ balance and 
because of the need to get the USRP2 out the door.


I promise that when it is ready, it will be added to the ordering page 
of the website. 
I promise that when it is ready, there will be an announcement.


Thus, if it is not on the order page and it is has not been announced, 
you can safely assume that it is not ready.  Nobody wants it to be ready 
more than me, but I won't ship it before it is 100%.


Thanks,
Matt




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


[Discuss-gnuradio] RSSI value in inband code

2008-11-14 Thread Stefan Brüns
Hi

after looking at the verilog code for some time, these are my results:

in module usrp_inband_usb, for each of the four aux adcs, the signal level is 
read from the adc and an gliding average of the rssi and an saturation 
indicator is is calculated. The rssi value is put but into the lower 16 bits 
of an 32 bit bus, which is passed on through the module rx_buffer_inband and 
reaches the module packet_builder.

In packet_builder, the rssi bus of the adc corresponding with the channel 
which is transmitted is selected. Until here, everything is fine.

As said before, the rssi value is in the 16 lower bits of the rssi bus. When 
looking at the calculation of the rssi value, it is apparent that it is a IIR 
filter with output value in the range [0..0x7ff] (max value is determined by 
the max absolute value of the aux adc, which is 0x7ff).

Now, the packet_builder takes the lower 6 bits of the 16 bit register with an 
value range corresponding to 11 bits and puts it into the usb packet. So as 
soon as the average value of the adc is higher than 0x3f (63), the rssi value 
in the usb packet will be just noise.

Proposal:
Change the rssi value to a logarithmic encoding. With a 3.3 split, 10 bits can 
be encoded, which is almost the range of the aux adc (11bit). Step size is 
about 0.1dB.

A verilog module for encoding the rssi value is attached. I have no tools for 
verilog, so I did not test it. Dont know if it works, and if the the changes 
in the packet_builder for getting the log value from the linear value is 
correct.

Would be nice if anyone could test this and pass an fpga firmware on to me.

Thanks,

Stefan
-- 
Stefan Brüns  /  Bergstraße 21  /  52062 Aachen
mailto:lurch at gmx.li  http://www.kawo1.rwth-aachen.de/~lurchi/
   phone: +49 241 53809034 mobile: +49 151 50412019
module rssi_lin_law (
input [9:0] lin,
output [5:0] law );

always @(lin)
case(lin)
10'b1x  : law = {3b'111,lin[8:6]};
10'b01  : law = {3b'110,lin[7:5]};
10'b001xxx  : law = {3b'101,lin[6:4]};
10'b0001xx  : law = {3b'100,lin[5:3]};
10'b1x  : law = {3b'011,lin[4:2]};
10'b01  : law = {3b'010,lin[3:1]};
10'b001xxx  : law = {3b'001,lin[2:0]};
 // 10'b000xxx  : law = {3b'000,lin[2:0]};
default : law = {3b'000,lin[2:0]};
endcase

endmodule
--- packet_builder.v_orig	2008-11-14 17:18:11.0 +0100
+++ packet_builder.v	2008-11-14 17:39:28.0 +0100
@@ -47,6 +47,7 @@
 reg [3:0] check_next;
 	
 wire [31:0] true_rssi;
+wire [5:0] true_rssi_law;
 wire [4:0] true_channel;
 wire ready_to_send;
 
@@ -109,8 +110,10 @@
 end
 
 `HEADER2: begin
+rssi_lin_law (
+			.lin(true_rssi[10:1]), .law(true_rssi_law );
 fifodata[`CHAN] = #1 true_channel;
-fifodata[`RSSI] = #1 true_rssi[5:0];
+fifodata[`RSSI] = #1 true_rssi_law;
 fifodata[`BURST] = #1 0;
 fifodata[`DROPPED] = #1 0;
 fifodata[`UNDERRUN] = #1 (check_next == 0) ? 1'b0 : underrun[true_channel];
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio


RE: [Discuss-gnuradio] Problems with the usrp_rx_cfile.py, usrp_fft.py and usrp_oscope.py and RFID signals

2008-11-14 Thread Paul Mathews
I am a student and I am doing my thesis project on the RFID protocols. At
the present time, with the USRP, I am trying to catch the signal between a
reader and a tag RFID. As reader I am using an OpendPCD (using the firmware
for the Mifare Classic
protocol) and as card a Mifare Classic Card.

Because of I am a very beginner of USRP and all the rest, I am using the
programs usrp_fft.py and usrp_oscope.py and the usrp_rx_cfile.py program
with another program called Baudline to analyse the spectrum.

My problem is that I can easily see in the frequency domain, using usrp_fft,
the carrier at 13.561Mhz, but not the subcarrier that should be a 847KHz
modulation of the carrier (probably covered by noise) even if I try to use a
baseRX daughterboard instead of the LFRX. Moreover, in the time domain (with
the usrp_oscope), I cannot recognize anything interesting.

As it isn't enough, with the usrp_rx_cfile and the program baudline I cannot
recognize neither the carrier: my opinion is that it is caused by a wrongly
interpretation of the bit-length of the samples (and for this I should need
a confirmation that the output samples are 16 bit-length). That program
supports these formats: alaw ulaw s8 u8 le16 be16 le32f be32f. Does anybody
know wich is the format I should use?

Probably I'm using wrongly the hardware and the software I have...

Could somebody suggest me a solution? Any kind of help will be absolutely
well appreciated!

thank you,

Marco

RFID modulation can be either AM or FM. For AM, modulation depth can be
anywhere between 10% and 100%. If your system is AM and your receiver is
overdriven, you will not see anything like 10% modulation depth. Try
increasing the distance between transmitter (RFID reader) and receiver
antenna, thus weakening the signal, and see if the modulation sidebands
appear. Using usrp_oscope.py, you should be able to clearly see the
modulation notches if you have an AM system, although it can be difficult to
trigger properly.
Note that the RFID transmissions have a low duty factor, so that the
modulation content represents a small portion of the total energy. So,
analyzing the RFID transmissions sometimes means you must first find a way
to synchronize your fft sampling to the packet bursts.
Paul Mathews




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


[Discuss-gnuradio] GnuRadio and CUDA

2008-11-14 Thread Bob Keyes
I've just been given a Nvidia Quadro 5600 and I am thinking of using it for 
DSP. Has anyone experimented with USRP  gnuradio  cuda?


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


[Discuss-gnuradio] Question about USRP2

2008-11-14 Thread Yabo Li
Hi,

I am quite new to the GNU radio. We just got the USRP2. I am wondering if
the steps in the GettingStart in 
http://gnuradio.org/trac/wiki/GettingStarted; are applicable to USRP2, or
they are for USRP only. Thanks.

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


Re: [Discuss-gnuradio] Question about USRP2

2008-11-14 Thread Brian Padalino
On Fri, Nov 14, 2008 at 8:56 PM, Yabo Li [EMAIL PROTECTED] wrote:
 Hi,

 I am quite new to the GNU radio. We just got the USRP2. I am wondering if
 the steps in the GettingStart in
 http://gnuradio.org/trac/wiki/GettingStarted; are applicable to USRP2, or
 they are for USRP only. Thanks.

Yes.

As a note, the code for the USRP2 is still being developed feverishly
so make sure to stay up to date.

Brian


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


Re: [Discuss-gnuradio] how to change the channel width when data is transmitting

2008-11-14 Thread Firas A.

Hi, 

 Matt Ettus wrote :


 I checked in a fix to the verilog to allow this.  However, the released 
 rbf files haven't been updated yet, so you will need to compile it
 yourself.

 Matt


I compiled your changes today. The rbf is given on the link below. I will
try to test it and give you a report.

http://rapidshare.com/files/163918423/std_2rxhb_2tx.rbf


Best Regards,


Firas
-- 
View this message in context: 
http://www.nabble.com/how-to-change-the-channel-width-when-data-is-transmitting-tp20471587p20512914.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