[Discuss-gnuradio] Re: Discuss-gnuradio Digest, Vol 30, Issue 24

[Spencer Chirume]

Can anyone provide me the 'building blocks' of a basic and or
intermidiate digital radio for general reception>Looking at the
Component parts the physical parts(a/d & other components) the
software for demodulation & stages preceding and past the demod stage
nescesary for building it from scratch using widely available parts
from companies like RS components and the likes.

On 5/25/05, address@hidden
<address@hidden> wrote:
> Send Discuss-gnuradio mailing list submissions to
>       address@hidden
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>       http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> or, via email, send a message with subject or body 'help' to
>       address@hidden
> 
> You can reach the person managing the list at
>       address@hidden
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Discuss-gnuradio digest..."
> 
> 
> Today's Topics:
> 
>    1. newbie cant get wxPy to work (jmdaniel)
>    2. USRP DDC usage (Philip Balister)
>    3. Error in building GNU radio core 2.5 (Ahmad Sheikh)
>    4. DBSRX status (Matt Ettus)
>    5. ALSA audio source not working---why? (Henry Gernhardt III)
>    6. DSP based SDR (Darrell Harmon)
>    7. Re: Error in building GNU radio core 2.5 (LRK)
>    8. Re: DBSRX status (Lamar Owen)
>    9. Re: USRP DDC usage (Eric Blossom)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 25 May 2005 13:19:42 -0400
> From: jmdaniel <address@hidden>
> Subject: [Discuss-gnuradio] newbie cant get wxPy to work
> To: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset="ISO-8859-1"
> 
> Hello,
> 
> I'm fairly new to gnuradio/unix/linux and have seemed to gotten through much
> 
> of the installation of gnuradio (thanks to this discussion) except for wxPy
> 
> which is giving me trouble.  Heres what happens when I try to import wx.
> 
> % python
> Python 2.4 (#1, Apr 19 2005, 15:47:38)
> [GCC 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import Numeric
> >>> import wx
> Traceback (most recent call last):
>   File "<stdin>", line 1, in ?
>   File "/usr/lib/python2.4/site-packages/wx-2.6-gtk2-ansi/wx/__init__.py", 
> line 42, in ?
>     from wx._core import *
>   File "/usr/lib/python2.4/site-packages/wx-2.6-gtk2-ansi/wx/_core.py", line
> 
> 4, in ?
>     import _core_
> ImportError: /usr/lib/python2.4/site-packages/wx/_core_.so: undefined
> symbol: 
> PyUnicodeUCS4_AsEncodedString
> 
> I have looked over the "No module named wx" thread and seem to have a 
> different problem. I'm pretty certain that there is only one installation of
> 
> wx on my machine but I've been working on this off and on so that may be the
> 
> source of my wx headache.  Has anyone run into this error before that knows
> a 
> quick fix? if not how can I check to see if there are multiple installations
> 
> on my machine? Let me know if more information is needed.
> 
> Thanks,
> John Daniel 
> Virginia Tech
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Wed, 25 May 2005 14:54:05 -0400
> From: Philip Balister <address@hidden>
> Subject: [Discuss-gnuradio] USRP DDC usage
> To: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain
> 
> I'm working on making a SCA component for the usrp based on the usrp
> standard interface. I've got a few questions on how to use the DDC's and
> the input mux.
> 
> If I set the mux word to 0x33221100 (and the number of channels to four)
> I believe I will have 4 channels of complex data from each A2D.
> 
> If I set the mux word to 0xf3f2f1f0 I will have four channels of real
> data, interleaved with the zeros from the Q channel.
> 
> Is this correct?
> 
> Thanks,
> 
> Philip
> 
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Thu, 26 May 2005 04:08:01 +0500
> From: "Ahmad Sheikh" <address@hidden>
> Subject: [Discuss-gnuradio] Error in building GNU radio core 2.5
> To: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> I get the following error when I enter ./bootstrap in building 
> gnu-radio-core-2.5 on Redhat Linux v3.
> 
> /usr/local/share/aclocal/pkg.m4:5: warning: underquoted definition of
> PKG_CHECK_MODULES
>   run info '(automake)Extending aclocal'
>   or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
> /usr/local/share/aclocal/cppunit.m4:4: warning: underquoted definition of
> AM_PATH_CPPUNIT
> 
> and this error when I enter make.
> 
> In file included from
> /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../include/c++/3.4.4/istream:771,
>                  from
> /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../include/c++/3.4.4/sstream:45,
>                  from
> /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../include/c++/3.4.4/complex:51,
>                  from ./gr_complex.h:25,
>                  from ./gr_types.h:30,
>                  from ./gr_runtime.h:26,
>                  from ./gr_block.h:26,
>                  from gr_block.cc:27:
> /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../include/c++/3.4.4/bits/istream.tcc:186:
> error: redefinition of `std::basic_istream<_CharT, _Traits>&
> std::basic_istream<_CharT, _Traits>::operator>>(int&)'
> /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../include/c++/3.4.4/bits/istream.tcc:111:
> error: `std::basic_istream<_CharT, _Traits>& std::basic_istream<_CharT,
> _Traits>::operator>>(int&)' previously declared here
> /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../include/c++/3.4.4/istream:
> In instantiation of `std::basic_istream<char, std::char_traits<char> >':
> /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../include/c++/3.4.4/bits/istream.tcc:1170:
>    instantiated from here
> /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../include/c++/3.4.4/bits/istream.tcc:111:
> error: `std::basic_istream<_CharT, _Traits>& std::basic_istream<_CharT,
> _Traits>::operator>>(int&) [with _CharT = char, _Traits =
> std::char_traits<char>]' and `std::basic_istream<_CharT, _Traits>&
> std::basic_istream<_CharT, _Traits>::operator>>(int&) [with _CharT = char,
> _Traits = std::char_traits<char>]' cannot be overloaded
> /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../include/c++/3.4.4/istream:
> In instantiation of `std::basic_istream<wchar_t, std::char_traits<wchar_t>
>  >':
> /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../include/c++/3.4.4/bits/istream.tcc:1182:
>    instantiated from here
> /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.4/../../../../include/c++/3.4.4/bits/istream.tcc:111:
> error: `std::basic_istream<_CharT, _Traits>& std::basic_istream<_CharT,
> _Traits>::operator>>(int&) [with _CharT = wchar_t, _Traits =
> std::char_traits<wchar_t>]' and `std::basic_istream<_CharT, _Traits>&
> std::basic_istream<_CharT, _Traits>::operator>>(int&) [with _CharT =
> wchar_t, _Traits = std::char_traits<wchar_t>]' cannot be overloaded
> make[4]: *** [gr_block.lo] Error 1
> make[4]: Leaving directory `/home/ahmad/gnuradio-core-2.5/src/lib/runtime'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory `/home/ahmad/gnuradio-core-2.5/src/lib'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/home/ahmad/gnuradio-core-2.5/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/ahmad/gnuradio-core-2.5'
> make: *** [all] Error 2
> 
> How do I fix it?
> Thanks,
> 
> Ahmad
> 
> 
> -- 
> ___________________________________________________________
> Sign-up for Ads Free at Mail.com
> http://promo.mail.com/adsfreejump.htm
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Wed, 25 May 2005 16:03:34 -0700
> From: Matt Ettus <address@hidden>
> Subject: [Discuss-gnuradio] DBSRX status
> To: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> 
> 
> I am almost ready to declare the DBSRX board done.  Just to let you know
> how it's going, check out this picture:
> 
>       http://home.ettus.com/dbsrx-screen.png
> 
> What you are seeing there is an fft of a -100 dBm carrier at 2001.6 MHz.
>  You'll notice that there is over 30 dB of image rejection (about 35 dB
> actually) and the carrier is almost 30 dB stronger than noise in a 4kHz
> bandwidth.  If you do the math, this gives us a noise figure of less
> than 8 dB, before you account for the loss in my cables.
> 
> Matt
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Wed, 25 May 2005 23:45:11 +0000
> From: "Henry Gernhardt III" <address@hidden>
> Subject: [Discuss-gnuradio] ALSA audio source not working---why?
> To: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; format=flowed
> 
> Folks---
> 
> I just successfuly compiled GnuRadio and its dependencies.  (YAY!!)  I have,
> 
> however, run into a slight snag with audio.source().  When running anything
> 
> using this little gem, I get the following (example output from 
> spectrum_inversion.py):
> 
> audio_alsa_source[hw:0,0]: set_channels failed: Invalid argument
> Traceback (most recent call last):
>   File "spectrum_inversion.py", line 37, in ?
>     main ()
>   File "spectrum_inversion.py", line 32, in main
>     fg.start ()
>   File 
> "/home/henry/gnuradio/lib/python2.4/site-packages/gnuradio/gr/flow_graph.py",
> 
> line 69, in start
>     self._setup_connections ()
>   File 
> "/home/henry/gnuradio/lib/python2.4/site-packages/gnuradio/gr/flow_graph.py",
> 
> line 98, in _setup_connections
>     self.validate ()
>   File 
> "/home/henry/gnuradio/lib/python2.4/site-packages/gnuradio/gr/basic_flow_graph.py",
> 
> line 164, in validate
>     raise ValueError, ("%s::check_topology (%d, %d) failed" % (m, ninputs, 
> noutputs))
> ValueError: <gr_block audio_alsa_source (0)>::check_topology (0, 1) failed
> 
> Any ideas as to what may be causing this?
> 
> TIA,
> 
>         Henry C. Gernhardt, III
>         KE4PIB
> 
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 6
> Date: Wed, 25 May 2005 18:57:34 -0500
> From: Darrell Harmon <address@hidden>
> Subject: [Discuss-gnuradio] DSP based SDR
> To: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> I am planning to build a DSP based SDR board.  I will be using the 
> Analog Devices Blackfin DSP (ADSP-BF532) and the PLX NET2272 USB 2.0 
> interface.  The DSP has a PPI interface for a high speed parallel ADC 
> which can accept 16 bit input at up to 65MHz.  I doubt that much data 
> could be processed, but 20MHz samping should be possible.  The PPI 
> supports DMA to L1 memory or SDRAM.  The Blackfin is a 16bit 400MHz dual 
> MAC fixed point DSP.  There is a port of GCC for the Blackin and no FPGA 
> will be used, so only free software will be needed for development.  The 
> board will be able to operate without a PC attatched.  The board will be 
> 4 layers and about the size of a credit card.  I intend to release the 
> schematics (both pdf and gSchem formats).
> 
> I am considering the ADS5520 ($20, 12 bit) and the LTC2227 ($11, 12 
> bit). The LTC part has the advantage of pin compatible 12 and 14 bit 
> versions.  Does anyone have ADC suggestions?  Low power is important as 
> I would like to power the board from USB.  I may be able to get a dual 
> LTC229x ADC to multiplex the data onto the PPI, but that would result in 
> a lower data rate.
> 
> The PPI will be used for the ADC, so adding a high speed DAC will not be 
> possible.  A slower DAC could be attatched to the I2S serial ports.  
> Would a 192KHz 24 bit audio DAC such as the PCM1753 be useful to 
> anyone?  I could also interface a 24 bit 192KHz audio ADC such as the 
> PCM1804 for weak signal recieve.
> 
> I am still unsure how I will handle the analog input.  I had considered 
> putting a transformer on the board and providing a SMA or Hirose U.FL 
> connector.  I don't like this option because it eliminates the option of 
> DC coupling.  I could use a differential amplifier, but that will 
> introduce distortion.  The THS4509 is expensive but low distortion.  
> Another option is to use a surface mount connector and provide 
> differential connections to the ADC as well as SPI and GPIO.  This would 
> require an additional board, but would be the most flexible.
> 
> Also any advice on how to interface this with gnuradio would be welcome.
> 
> -- 
> Darrell Harmon
> 100x100mm SBC running GNU/Linux:
> http://dlharmon.com/sbc.html
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 7
> Date: Wed, 25 May 2005 19:03:46 -0500
> From: LRK <address@hidden>
> Subject: Re: [Discuss-gnuradio] Error in building GNU radio core 2.5
> To: Ahmad Sheikh <address@hidden>
> Cc: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
> 
> On Thu, May 26, 2005 at 04:08:01AM +0500, Ahmad Sheikh wrote:
> > I get the following error when I enter ./bootstrap in building 
> > gnu-radio-core-2.5 on Redhat Linux v3.
> > 
> > /usr/local/share/aclocal/pkg.m4:5: warning: underquoted definition of
> > PKG_CHECK_MODULES
> >   run info '(automake)Extending aclocal'
> >   or see
> http://sources.redhat.com/automake/automake.html#Extending-aclocal
> > /usr/local/share/aclocal/cppunit.m4:4: warning: underquoted definition of
> > AM_PATH_CPPUNIT
> 
> The "underquoted definition" means the name does not have the brackets [..]
> so it could be misinterpreted. You can add those by editing the pkg.m4 and
> cppunit.m4 files but they should not be a problem unless they are actually
> being misinterpreted.
> 
>  
> > and this error when I enter make.
>  
> I haven't seen that one.
> 
> 
> -- 
> LRK
> address@hidden
> 
> 
> 
> 
> ------------------------------
> 
> Message: 8
> Date: Wed, 25 May 2005 21:34:13 -0400
> From: Lamar Owen <address@hidden>
> Subject: Re: [Discuss-gnuradio] DBSRX status
> To: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain;  charset="iso-8859-1"
> 
> On Wednesday 25 May 2005 19:03, Matt Ettus wrote:
> > I am almost ready to declare the DBSRX board done.  Just to let you know
> > how it's going, check out this picture:
> >
> >     http://home.ettus.com/dbsrx-screen.png
> >
> > What you are seeing there is an fft of a -100 dBm carrier at 2001.6 MHz.
> >  You'll notice that there is over 30 dB of image rejection (about 35 dB
> > actually) and the carrier is almost 30 dB stronger than noise in a 4kHz
> > bandwidth.  If you do the math, this gives us a noise figure of less
> > than 8 dB, before you account for the loss in my cables.
> 
> Good.
> 
> Now, where can I get the code for that version of USRP-FFT? :-)  Lots of
> nice 
> sliders there.
> -- 
> Lamar Owen
> Director of Information Technology
> Pisgah Astronomical Research Institute
> 1 PARI Drive
> Rosman, NC  28772
> (828)862-5554
> www.pari.edu
> 
> 
> 
> 
> ------------------------------
> 
> Message: 9
> Date: Wed, 25 May 2005 19:13:43 -0700
> From: Eric Blossom <address@hidden>
> Subject: Re: [Discuss-gnuradio] USRP DDC usage
> To: Philip Balister <address@hidden>
> Cc: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
> 
> On Wed, May 25, 2005 at 02:54:05PM -0400, Philip Balister wrote:
> > I'm working on making a SCA component for the usrp based on the usrp
> > standard interface. I've got a few questions on how to use the DDC's and
> > the input mux.
> > 
> > If I set the mux word to 0x33221100 (and the number of channels to four)
> > I believe I will have 4 channels of complex data from each A2D.
> 
> FYI, the current fpga image only support two DDCs.
> 
> You always get complex data out of the DDCs.  The question is what are
> you putting in?
> 
> If you want two DDCs with a different pair of A/Ds to each one
> the mux should == 0x00003210
> 
> > If I set the mux word to 0xf3f2f1f0 I will have four channels of real
> > data, interleaved with the zeros from the Q channel.
> 
> Yes.  This will feed a zero to the Q input of each DDC and will feed
> ADC's 3, 2, 1, 0 to the I inputs.  Note that there are only two
> channels available in the current FPGA build.
> 
> Eric
> 
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
> 
> End of Discuss-gnuradio Digest, Vol 30, Issue 24
> ************************************************
>