Hi,
I have been away from my work Gnu Radio and Click, but
now I am back to work.
Well, I was trying out some simple programs to make
sure I can use the GNU Radio libraries smoothly. I
wrote a very simple test program just to see if I can
link correctly with the GNU Radio libraries.
I wrote a C++ program that calls the
gr_make_buffer(int,size_t) function, but some how when
I use g++ to compile, it does not link properly. The
path to the libraries have been set in LD_LIBRAY_PATH.
This is a sample of what i did.
#include<gr_buffer.h>
int main()
{
gr_buffer)sptr g = gr_make_buffer(2,3);
--- [EMAIL PROTECTED] wrote:
> Send Discuss-gnuradio mailing list submissions to
> discuss-gnuradio@gnu.org
>
> 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
> [EMAIL PROTECTED]
>
> You can reach the person managing the list at
> [EMAIL PROTECTED]
>
> When replying, please edit your Subject line so it
> is more specific
> than "Re: Contents of Discuss-gnuradio digest..."
>
>
> Today's Topics:
>
> 1. FFT-based feature extensions, fixes, etc.
> (Weber, Michael J. (US SSA))
> 2. Re: Installatin of USRP - many question
> related to sudo maybe
> (Eric Blossom)
> 3. TVRX flatness + USRP gain setting? (Weber,
> Michael J. (US SSA))
> 4. Re: FFT-based feature extensions, fixes, etc.
> (Eric Blossom)
> 5. Re: TVRX flatness + USRP gain setting? (Eric
> Blossom)
> 6. 2.6 release coming RSN (Eric Blossom)
> 7. Re: 2.6 release coming RSN ([EMAIL PROTECTED])
> 8. N1Bt software board and front end design
> (Gituma Nturibi)
> 9. (no subject) (Robitaille, Michael)
>
>
>
----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 21 Oct 2005 17:22:23 -0400
> From: "Weber, Michael J. \(US SSA\)"
> <[EMAIL PROTECTED]>
> Subject: [Discuss-gnuradio] FFT-based feature
> extensions, fixes, etc.
> To: <discuss-gnuradio@gnu.org>
> Message-ID:
>
>
<[EMAIL PROTECTED]>
> Content-Type: text/plain; charset="us-ascii"
>
> Has anyone done any work on creating some
> intelligent behaviors based on
> the FFT outputs? I'm thinking of things like
> autotuning to new strong
> signals, autoconfiguring demodulator bandwidths
> (wide or narrow FM, for
> example), drawing a vertical indicator line in the
> plot to indicate
> various things, etc. If nothing's been done, I'll
> plow ahead slowly...
> but no since recreating the wheel.
>
> On a related note, is there a way to calm the
> auto-scaling behavior of
> the FFT plots? I've created a narrow-band version of
> the usrp_wfm demo,
> but the frequency increment is 5KHz instead of
> 100Khz, and the plot
> moves from left to right across the graph before the
> automatic scaling
> switches ranges. Sometimes the total range of X
> values shifts as well,
> from 4 to 5 MHz and back. I suppose what I'm looking
> for is more control
> of the scale/range of the plots, the grid lines,
> everything. What's the
> best way to proceed?
>
> I'm working with a TVRX board at the moment, but I
> suspect that doesn't
> matter.
>
> Thanks for any hints and tips!
>
> Best,
> Mike
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 21 Oct 2005 14:26:23 -0700
> From: Eric Blossom <[EMAIL PROTECTED]>
> Subject: Re: [Discuss-gnuradio] Installatin of USRP
> - many question
> related to sudo maybe
> To: "Robitaille, Michael"
> <[EMAIL PROTECTED]>
> Cc: discuss-gnuradio@gnu.org
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, Oct 21, 2005 at 03:09:21PM -0600,
> Robitaille, Michael wrote:
> > Hello all and thanks for your.
> >
> > I finally got all the baseline and gnuradio
> software installed per
> > KD7LMO.net with some modification and still some
> question, for instance:
> >
> > 1- In the install_baseline.sh there is
> the installation of
> > xerces-c-src-2_6_0 but not in the baseline build
> shell or in the list of
> > items needed. I did not install this package, is
> this ok?
>
> You don't need xerces. This is OK
>
> > 2- Is the Octave/Octave-forge package
> needed? I did build and
> > installed these packages.
>
> Not required for GNU Radio, but nice to have.
>
> > 3- Should any of these packages,
> including gnuradio, be
> > installed with sudo?
>
>
> Depends on your setup. I don't install with sudo
> (being generally
> paranoid), and have arranged things so that I'm in a
> group that has
> write access to everything under /usr/local.
> Judicious use of
> chmod g+s on directories under there is useful.
>
> > I then tried to do install my brand new USRP, =),
> based on the wiki
> > UsrpInstall. Here are the problems I have
> encountered and need help with:
>
>
> > 1- The directory /usr/local/share/usrp/rev2
> was not created with the
> > required files (firmware). I created the
> directory and added the files as
> > root manually. Running the program
> test_usrp_standard_tx does not seem to
> > install the firmware file in the directory. Most
> likely related to #3 above
> > but not I did try to do gnuradio install with sudo
> and it did not put the
> > fillies. I did use CVS and per the instruction, I
> manually copied the file
> > usrp_fpga.rbf to the directory.
>
> I think this was a permissions problem. Unless
> you're setup to write
> /usr/local and below, you will want to "sudo make
> install".
>
> > 2- When I run test_usrp_standard_tx I get
> the error - can't find
> > usrp_fpga.rbf. The LED on the USRP does change
> from 2Hz to 1Hz, so the
> > firmware did get loaded.
>
> If you're building from CVS, you need to install the
> .rbf file manually.
> Grab
> http://comsec.com/usrp/usrp_fpga_rev2_2005_10_20.rbf
> and install
> it as /usr/local/share/usrp/rev2/usrp_fpga.rbf
>
> > 3- I do have hotplug running and seem to
> have permission to access the
> > USRP device (when I had a camera to the USB port,
> it loaded automatically).
> > When I check the /etc/hotplub/usb, I do not see
> usrp or usrp.usremap.
>
> We don't use the hotplug stuff. Our library loads
> the firmware and fpga
> bitstream when you first open the device.
>
> There's lots of variation on usb device permissions
> depending on your
> distribution. Under SuSE 9.3 it "just works". Not
> sure why!
> Under Mandrake 10.1 I made myself a member of group
> usb, which is the
> group that owns everything under /proc/bus/usb/*
> FWIW, the gid and perms used by usbfs can be set
> with a mount command
> option. E.g.,
>
> [EMAIL PROTECTED] ~]$ grep usbfs /etc/rc.d/init.d/usb
> action "Mount USB filesystem" mount -t usbfs
> -o devmode=0664,devgid=43 none /proc/bus/usb
>
> >
> > 4- When I run the example usrp_oscope.py I
> get the error No module
> > named gnuradio.
>
> Did you make install? Did it work?
> You might try "sudo ldconfig"
> Is your PYTHONPATH set? Should be something like:
>
> /usr/local/lib/python2.3/site-packages
>
>
> > Please help.
>
> OK!
>
> Eric
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 21 Oct 2005 17:33:22 -0400
> From: "Weber, Michael J. \(US SSA\)"
> <[EMAIL PROTECTED]>
> Subject: [Discuss-gnuradio] TVRX flatness + USRP
> gain setting?
> To: <discuss-gnuradio@gnu.org>
> Message-ID:
>
>
<[EMAIL PROTECTED]>
> Content-Type: text/plain; charset="us-ascii"
>
> What is the recommended position of the USRP gain
> setting when using the
> TVRX daughtercard?
>
> Looking at the FFT plots, if the gain is maxed out
> it appears that the
> signal drops about 13dB from center to edge,
> regardless of the bandwidth
> of the decimated signal. I.E, if the signal is
> 640KHz wide, the edges
> are 13dB down from the center, and if the signal is
> 4MHz wide, the edges
> are still 13dB down from the center. At minimum
> gain, the edges seems to
> drop about 6dB, but the input from the TVRX goes
> deaf at that setting.
>
> Is there a way to have a flatter signal response
> across the bandwidth
> and still have gain?
>
> Thanks!
>
> Mike
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 21 Oct 2005 14:35:08 -0700
> From: Eric Blossom <[EMAIL PROTECTED]>
> Subject: Re: [Discuss-gnuradio] FFT-based feature
> extensions, fixes,
> etc.
> To: "Weber, Michael J. (US SSA)"
> <[EMAIL PROTECTED]>
> Cc: discuss-gnuradio@gnu.org
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, Oct 21, 2005 at 05:22:23PM -0400, Weber,
> Michael J. (US SSA) wrote:
> > Has anyone done any work on creating some
> intelligent behaviors based on
> > the FFT outputs? I'm thinking of things like
> autotuning to new strong
> > signals, autoconfiguring demodulator bandwidths
> (wide or narrow FM, for
> > example), drawing a vertical indicator line in the
> plot to indicate
> > various things, etc. If nothing's been done, I'll
> plow ahead slowly...
> > but no since recreating the wheel.
>
> Please dive in.
> In truth, I think the right answer is to completely
> revisit the guts
> of the plot widget we're currently using. It would
> be most
> appreciated.
>
> > On a related note, is there a way to calm the
> auto-scaling behavior of
> > the FFT plots?
>
> Use the code in CVS, or wait a bit for 2.6. It's
> doesn't autoscale
> (It was driving us crazy too!). With the new code,
> right clicking
> gets you a menu that controls dB/div, ref level,
> averaging, etc.
>
> > I've created a narrow-band version of the usrp_wfm
> demo,
> > but the frequency increment is 5KHz instead of
> 100Khz, and the plot
> > moves from left to right across the graph before
> the automatic scaling
> > switches ranges. Sometimes the total range of X
> values shifts as well,
> > from 4 to 5 MHz and back. I suppose what I'm
> looking for is more control
> > of the scale/range of the plots, the grid lines,
> everything. What's the
> > best way to proceed?
>
> You probably want to look at the usrp_wfm_rcv.py
> code in CVS. It's
> quite a bit different from the code in 2.5.
>
> The biggest contribution to the project would be to
> rewrite the
> underlying plotting widget. I suggest something
> simple and
> deterministic like a grid with fixed X & Y
> divisions. Don't try to
> autoscale, etc., just provide controls to scale X &
> Y. FWIW, the
> usrp_oscope manually manages the X axis, but
> autoscales Y. It was
> done by kludging around some of the underlying
> widget behavior.
>
> > I'm working with a TVRX board at the moment, but I
> suspect that doesn't
> > matter.
>
> Shouldn't matter.
>
> > Thanks for any hints and tips!
> >
> > Best,
> > Mike
>
> Eric
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 21 Oct 2005 14:42:16 -0700
> From: Eric Blossom <[EMAIL PROTECTED]>
> Subject: Re: [Discuss-gnuradio] TVRX flatness + USRP
> gain setting?
> To: "Weber, Michael J. (US SSA)"
> <[EMAIL PROTECTED]>
> Cc: discuss-gnuradio@gnu.org
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, Oct 21, 2005 at 05:33:22PM -0400, Weber,
> Michael J. (US SSA) wrote:
> > What is the recommended position of the USRP gain
> setting when using the
> > TVRX daughtercard?
>
> Hi Mike,
>
> First off, I strongly suggest you use CVS. Things
> are a lot different
> with that code. Sooo, for the code currently in
> CVS, when using a
> simple dipole, I typically set the gain to about 35.
>
> > Looking at the FFT plots, if the gain is maxed out
> it appears that the
> > signal drops about 13dB from center to edge,
> regardless of the bandwidth
> > of the decimated signal. I.E, if the signal is
> 640KHz wide, the edges
> > are 13dB down from the center, and if the signal
> is 4MHz wide, the edges
> > are still 13dB down from the center. At minimum
> gain, the edges seems to
> > drop about 6dB, but the input from the TVRX goes
> deaf at that setting.
>
> The rolloff is caused by the 4 stage CIC filter in
> the FPGA. There's a
> half-band filter in progress that will flatten this
> out. We'll use the
> half-band as the last stage decimator.
>
> > Is there a way to have a flatter signal response
> across the bandwidth
> > and still have gain?
>
> Gain and bandwidth are pretty much orthogonal.
> In the meanwhile the quick fix is to sample at twice
> the rate you
> really need, then filter and decimate by 2 in
> software. Use a
> combination of optfir.low_pass and gr.fir_filter_ccf
>
> We do this in usrp_wfm_rcv.py that's in CVS.
>
> Eric
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 21 Oct 2005 14:54:12 -0700
> From: Eric Blossom <[EMAIL PROTECTED]>
> Subject: [Discuss-gnuradio] 2.6 release coming RSN
> To: discuss-gnuradio@gnu.org
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=us-ascii
>
> Yes, I know it's *really* time for a new release.
> [I can tell because I keep telling everyone to use
> CVS!]
>
> Anyhow, there are a few things still left to finish
> off.
>
> In no particular order:
>
> * Finish refactoring *all* examples so that they use
> the best practices
> with regard to GUI organization, hierarchical
> blocks, unified handling of
> usrp daughterboards, command line arguments,
> control-C handling, etc.
>
> usrp_fft.py, usrp_wfm_rcv.py and the stuff in the
> audio directory are
> currently done. Take a look at them to see where
> we're headed.
>
> * Rework usrp_nbfm_ptt (basic narrow band FM
> tranceiver) so that it
> works with all daughterboards.
>
> * FPGA half-band filter.
>
> * Integrate the native python documentation (pydoc
> stuff)
>
> * Add support to query and control IF bandwidth to
> the generic usrp
> daughterboard code [Needed for dbs_rx].
>
> There a ton of other things on the list, but I think
> these are the
> critical items.
>
> Eric
>
>
>
>
> ------------------------------
>
> Message: 7
> Date: Fri, 21 Oct 2005 15:02:02 -0700 (MST)
> From: [EMAIL PROTECTED]
> Subject: Re: [Discuss-gnuradio] 2.6 release coming
> RSN
> Cc: Discuss GNU Radio <discuss-gnuradio@gnu.org>
> Message-ID:
>
>
<[EMAIL PROTECTED]>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> Yes, yes, half-band filter!
>
>
>
> On Fri, 21 Oct 2005, Eric Blossom wrote:
>
> > Yes, I know it's *really* time for a new release.
>
> > [I can tell because I keep telling everyone to use
> CVS!]
> >
> > Anyhow, there are a few things still left to
> finish off.
> >
> > In no particular order:
> >
> > * Finish refactoring *all* examples so that they
> use the best practices
> > with regard to GUI organization, hierarchical
> blocks, unified handling of
> > usrp daughterboards, command line arguments,
> control-C handling, etc.
> >
> > usrp_fft.py, usrp_wfm_rcv.py and the stuff in
> the audio directory are
> > currently done. Take a look at them to see
> where we're headed.
> >
> > * Rework usrp_nbfm_ptt (basic narrow band FM
> tranceiver) so that it
> > works with all daughterboards.
> >
> > * FPGA half-band filter.
> >
> > * Integrate the native python documentation (pydoc
> stuff)
> >
> > * Add support to query and control IF bandwidth to
> the generic usrp
> > daughterboard code [Needed for dbs_rx].
> >
> > There a ton of other things on the list, but I
> think these are the
> > critical items.
> >
> > Eric
> >
> >
> > _______________________________________________
> > Discuss-gnuradio mailing list
> > Discuss-gnuradio@gnu.org
> >
>
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> >
>
>
>
>
>
> ------------------------------
>
> Message: 8
> Date: Sat, 22 Oct 2005 12:25:50 +0300
> From: "Gituma Nturibi" <[EMAIL PROTECTED]>
> Subject: [Discuss-gnuradio] N1Bt software board and
> front end design
> To: discuss-gnuradio@gnu.org
> Message-ID:
> <[EMAIL PROTECTED]>
> Content-Type: text/plain; format=flowed
>
> Greetings to all GNU radio enthusiasts. I'm an
> electronics and computer
> engineering student currently undertaking a sofware
> radio project for my
> final year. I would like to receive broadcast FM but
> the task seems to be
> quite daunting as I don't have the resources to use
> the USRP or the PCI card
> for reception. Is there anybody out there who has
> created an FM or even AM
> front end from components? I would really like to
> get some info on that.
>
> I would also like to find out more information on
> the N1BT software radio
> board as the info at the gnu radio site is
> insufficient. I would
> particularly like to find out about the cabapilities
> of the board and
> whether there is any design documentation.
> Particularly I want to know
> whether it can receive FM and whether anothe module
> such as the cable modem
> module is required.
>
> Thanks for the support and keep up the good work on
> the open source front
>
> Gituma Nturibi,
> Aspiring Engineer
>
>
_________________________________________________________________
> Express yourself instantly with MSN Messenger!
> Download today it's FREE!
>
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>
>
>
>
> ------------------------------
>
> Message: 9
> Date: Sat, 22 Oct 2005 10:31:46 -0600
> From: "Robitaille, Michael"
> <[EMAIL PROTECTED]>
> Subject: [Discuss-gnuradio] (no subject)
> To: discuss-gnuradio@gnu.org
> Message-ID:
> <[EMAIL PROTECTED]>
> Content-Type: text/plain
>
> >On Fri, 21 Oct 2005 14:26:23 -0700, Eric Blossom
> wrote:
>
>
>
> >>On Fri, Oct 21, 2005 at 03:09:21PM -0600,
> Robitaille, Michael wrote:
> >> Hello all and thanks for your.
> >>
> >> I finally got all the baseline and gnuradio
> software installed per
> >> KD7LMO.net with some modification and still some
> question, for instance:
> >>
> >> 1- In the install_baseline.sh there
> is the installation of
> >> xerces-c-src-2_6_0 but not in the baseline build
> shell or in the list of
> >> items needed. I did not install this package, is
> this ok?
>
>
>
> >You don't need xerces. This is OK
>
> It would be good to change the install script at
> KD7LM0 web site.
>
> >> 2- Is the Octave/Octave-forge package
> needed? I did build
> and
> >> installed these packages.
>
>
>
> >Not required for GNU Radio, but nice to have.
>
>
>
> It would be good to to mention that this is optional
> at KD7LM0 web site.
>
>
>
> >> 3- Should any of these packages,
> including gnuradio, be
>
> >> installed with sudo?
>
>
>
> > Depends on your setup. I don't install with sudo
> (being generally
> > paranoid), and have arranged things so that I'm in
> a group that has
> > write access to everything under /usr/local.
> Judicious use of
>
> > chmod g+s on directories under there is useful.
>
>
>
> I like the idea of not having to use sudo. I will
> try to change the
> permission on the appropriate directory.
>
> Does anyone have a list of what those directories
> are?
>
>
>
> >> I then tried to do install my brand new USRP, =),
> based on the wiki
> >> UsrpInstall. Here are the problems I have
> encountered and need help
> with:
>
>
> >> 1- The directory /usr/local/share/usrp/rev2
> was not created with
> the
> >> required files (firmware). I created the
> directory and added the files
> as
> >> root manually. Running the program
> test_usrp_standard_tx does not seem
> to
> >> install the firmware file in the directory. Most
> likely related to #3
> above
> >> but not I did try to do gnuradio install with
> sudo and it did not put the
> >> fillies. I did use CVS and per the instruction,
> I manually copied the
> file
> >> usrp_fpga.rbf to the directory.
>
>
>
> > I think this was a permissions problem. Unless
> you're setup to write
>
> > /usr/local and below, you will want to "sudo make
> install".
>
>
>
> >> 2- When I run test_usrp_standard_tx I get
> the error - can't find
> >> usrp_fpga.rbf. The LED on the USRP does change
> from 2Hz to 1Hz, so the
>
> >> firmware did get loaded.
>
>
>
> > If you're building from CVS, you need to install
> the .rbf file manually.
> > Grab
> http://comsec.com/usrp/usrp_fpga_rev2_2005_10_20.rbf
>
<http://comsec.com/usrp/usrp_fpga_rev2_2005_10_20.rbf>
> and install
> > it as /usr/local/share/usrp/rev2/usrp_fpga.rbf
>
> I did that (see last sentence in #1) and I still got
> the error that it could
> not find usrp_fpga.rbf.
> Is this file supposed to be somewhere else to?
>
> Isn't' there a better method to set this up with the
> CVS release?
>
> >> 3- I do have hotplug running and seem to
> have permission to access
> the
> >> USRP device (when I had a camera to the USB port,
> it loaded
> automatically).
> >> When I check the /etc/hotplup/usb, I do not see
> usrp or usrp.usremap.
>
> > We don't use the hotplug stuff. Our library loads
> the firmware and fpga
>
> > bitstream when you first open the device.
>
>
>
> Why the the UsrpInstall wiki mention that you need
> hotplug for setting up
> USB device permission?
>
>
>
> I am on FC4, how can I make sure that I have
> permission for the USB?
>
>
>
> I do not see any usrp or usrp.usremap in the
> /etc/hotplug/usb directory but
> I do see some for the USB camera that I connected.
>
>
>
> Can I get more information about the scrip that set
> the device permission
> mention in the UsrpInstall wiki?
>
>
>
> > There's lots of variation on usb device
> permissions depending on your
> > distribution. Under SuSE 9.3 it "just works".
> Not sure why!
> > Under Mandrake 10.1 I made myself a member of
> group usb, which is the
> > group that owns everything under /proc/bus/usb/*
> > FWIW, the gid and perms used by usbfs can be set
> with a mount command
> > option. E.g.,
>
> > [EMAIL PROTECTED] ~]$ grep usbfs
> /etc/rc.d/init.d/usb
> > action "Mount USB filesystem" mount -t
> usbfs -o
> devmode=0664,devgid=43
>
> > none /proc/bus/usb
>
>
>
> I am running on FC4, any help with those that have
> experience or have USRP
> running on FC4 would be appreciated.
>
>
>
> >>
> >> 4- When I run the example usrp_oscope.py I
> get the error No module
> >> named gnuradio.
>
> > Did you make install? Did it work?
> > You might try "sudo ldconfig"
> > Is your PYTHONPATH set? Should be something like:
>
> > /usr/local/lib/python2.3/site-packages
>
>
>
> I did install and will do it again making sure that
> there are absolutely no
> errors. Somehow I must have missed an error message
> about not being able to
> create the /usr/local/share/usrp directories. I
> will try it with setting
> write permission for the share directory.
>
>
>
> Thanks for the help.
>
>
> ------------------------------
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
>
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
> End of Discuss-gnuradio Digest, Vol 35, Issue 19
> ************************************************
>
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
