Re: [Discuss-gnuradio] make install failure---- subscribe m3by38xr
The problem was fixed by reinstall ubuntu system. .:-/ -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio -- View this message in context: http://www.nabble.com/make-install-failure-subscribe-m3by38xr-tp22060002p22095739.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
[Discuss-gnuradio] from a function generator into the LF-RX (maximum load)
Hi All, as i read in the documentation, http://gnuradio.org/trac/attachment/wiki/UsrpFAQ/USRP_Documentation.pdf Page 44, there is only a statement about maximum load at the Basic-RX. (From a function generator directly into the input of the Basic-RX) So i ask you, is there a built-in safety to save the LF-RX from being damaged too? Regards Markus ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Re: change variables in the FFT Plot
Josh Blum schrieb: Are you using GRC? -josh Yes, i compiled gnuradio with support and under Suse 11.1. Nearby if you want to get a spec file to create a RPM Package for Suse 11.1 i would send you mine. :-) My Requirements are nearly complete. Regards Markus ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Re: USRP2 and external clock (from GPS receiver)
Matt Ettus wrote: > The easiest way to check for lock is to put the following line in your > firmware: > > clocks_enable_test_clk(true,10); > > This will output a test clock on the middle 2 pins of the 4 pin > connector right near the VCXO on the motherboard. Look at one of those > 2 pins on an oscilloscope at the same time as the 10 MHz reference. You > should see the two clocks don't drift relative to each other. I tried as you suggested but it still drifts. I also added the following line in the firmware to make sure. clocks_mimo_config(MC_WE_LOCK_TO_SMA); I tried on several different USRP2s and I got same results. Any more suggestions? -- Posted via http://www.ruby-forum.com/. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Problem with "How-to-write-a-block"-tutorial
2009/2/18 Eric Blossom > On Wed, Feb 18, 2009 at 03:39:52PM +0100, Emil Molin wrote: > > Hi and thanks for the help, yes ive run it (and ive renamed the block to > > 'test' instead of 'howto_2' but i still get something wrong obviously > > because when running the test script i get this error: > > > > File "./qa_test.py", line 6, in > > from gnuradio import gr, gr_unittest, test > > File "/Library/Python/2.5/site-packages/gnuradio/test.py", line 21, in > > > > import _test > > ImportError: dlopen(/Library/Python/2.5/site-packages/gnuradio/_test.so, > 2): > > Symbol not found: __ZTV14test_double_ff > > Referenced from: /Library/Python/2.5/site-packages/gnuradio/_test.so > > Expected in: dynamic lookup > > > > it seems like there is something wrong in the swig-generated _test.so > file > > but how to fix that i have no idea? > > > > > $ c++filt _ZTV14test_double_ff > vtable for test_double_ff > > Are you sure you've got code for the class named test_double_ff linked > into the shared library you're building? > > Eric > Ive linked everythin in the same way as in the howto_square_ff example, what files could i have missed something in to not get the test_double_ff class linked? And well if its any reason to the problem this is how my makefile looks: # # Copyright 2004,2005,2006,2008 Free Software Foundation, Inc. # # This file is part of GNU Radio # # GNU Radio is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 3, or (at your option) # any later version. # # GNU Radio is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with GNU Radio; see the file COPYING. If not, write to # the Free Software Foundation, Inc., 51 Franklin Street, # Boston, MA 02110-1301, USA. # include $(top_srcdir)/Makefile.common # Install this stuff so that it ends up as the gnuradio.test module # This usually ends up at: # ${prefix}/lib/python${python_version}/site-packages/gnuradio ourpythondir = $(grpythondir) ourlibdir= $(grpyexecdir) AM_CPPFLAGS = $(STD_DEFINES_AND_INCLUDES) $(PYTHON_CPPFLAGS) SWIGPYTHONARGS = $(SWIGPYTHONFLAGS) $(SWIGGRFLAGS) ALL_IFILES = \ $(LOCAL_IFILES)\ $(NON_LOCAL_IFILES) NON_LOCAL_IFILES =\ $(GNURADIO_CORE_INCLUDEDIR)/swig/gnuradio.i LOCAL_IFILES = \ $(top_srcdir)/src/lib/test.i # These files are built by SWIG. The first is the C++ glue. # The second is the python wrapper that loads the _test shared library # and knows how to call our extensions. BUILT_SOURCES = \ test.cc\ test.py # This gets howto.py installed in the right place ourpython_PYTHON =\ test.py ourlib_LTLIBRARIES = _test.la # These are the source files that go into the shared library _test_la_SOURCES = \ test.cc\ test_double_ff.cc # magic flags _test_la_LDFLAGS = $(NO_UNDEFINED) -module -avoid-version # link the library against some comon swig runtime code and the # c++ standard library _test_la_LIBADD = \ $(PYTHON_LDFLAGS)\ -lstdc++ test.cc test.py: $(LOCAL_IFILES) $(ALL_IFILES) $(SWIG) $(SWIGPYTHONARGS) -module test -o test.cc $(LOCAL_IFILES) # These headers get installed in ${prefix}/include/gnuradio grinclude_HEADERS =\ test_double_ff.h # These swig headers get installed in ${prefix}/include/gnuradio/swig swiginclude_HEADERS = \ $(LOCAL_IFILES) MOSTLYCLEANFILES = $(BUILT_SOURCES) *.pyc # Don't distribute output of swig dist-hook: @for file in $(BUILT_SOURCES); do echo $(RM) $(distdir)/$$file; done @for file in $(BUILT_SOURCES); do $(RM) $(distdir)/$$file; done ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Re: No package 'usrp' found[SOLVED]
Hi, The problem is fixed. After doing "export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig", I can compile without any problem. Thanks alot. Woody On Thu, Feb 19, 2009 at 11:36 AM, Woody Dickson wrote: > Hi, > > While installing openbts, I am getting the following error: > > checking for USRP... configure: error: Package requirements (usrp > > 3.1) were not met: > > No package 'usrp' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables USRP_CFLAGS > and USRP_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > > Does anyone know how to fix it? > > Thanks, > Woody > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] USRP 2 Daughter Cards
I am trying to use the USRP 2 radio. I have been using the rx_streaming_sample script to collect data. If I use the rfx1800 daughtercard the results from the set_center_freq command seem correct but the output looks as if the receive channel is not connected (changing gain does not affect output levels). If I try the lfrx or dbs daughter cards the set_center_freq response appears incorrect. The baseband frequency is 0 and the ddc frequency is the negative of the commanded frequency. Any suggestions? == Jim Graham Black River Systems Company, Inc. 162 Genesee Street, Utica, NY 13502 e-mail : gra...@brsc.com voice : (315) 732-7385 x146 fax : (315) 732-5837 == ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP2 and external clock (from GPS receiver)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matt Ettus wrote: > Changkyu Seol wrote: >> Hi! >> >> I am planning to implement multiple synchronized transmitters using >> USRP2 and GPS receiver. Before that I checked whether the USRP2 is >> locked to external clock through following experiment. > > > The easiest way to check for lock is to put the following line in your > firmware: > > clocks_enable_test_clk(true,10); > > This will output a test clock on the middle 2 pins of the 4 pin > connector right near the VCXO on the motherboard. Look at one of those > 2 pins on an oscilloscope at the same time as the 10 MHz reference. You > should see the two clocks don't drift relative to each other. > > Matt > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio Is the test clock supposed to be running at 5kHz? I've just tested this on one of my USRP2 - it does appear to be locked with my external clock - - i.e. the 5kHz signal on the pin doesn't drift w.r.t my 10Mhz external source. Thanks, Doug - -- Doug Geiger Research Assistant Communications and Signal Processing Lab Oklahoma State University http://cspl.okstate.edu douglas.gei...@okstate.edu doug.gei...@ieee.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJnZtMgfOzzR5bXIgRAlD2AJ4358ZGT8PbPAfp3S6F5LKBEBFG1QCeKy6+ WEBFDTXjvLgtogJazqwQWjE= =bvvj -END PGP SIGNATURE- ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP 2 Daughter Cards
On Thu, Feb 19, 2009 at 10:15:29AM -0500, jim graham wrote: > I am trying to use the USRP 2 radio. I have been using the > rx_streaming_sample script to collect data. > > If I use the rfx1800 daughtercard the results from the set_center_freq > command seem correct but the output > > looks as if the receive channel is not connected (changing gain does not > affect output levels). What OS, version, distribution, architecture? Which version of the GNU Radio code? Are you feeding this with a signal generator? What's your input signal level? Which antenna port are you connected to? Have you tried running usrp2_fft.py? > If I try the lfrx or dbs daughter cards the set_center_freq response > appears incorrect. The baseband frequency is 0 and the ddc frequency > is the negative of the commanded frequency. Those values are correct. Have you tried injecting a signal into the board and looking at it using usrp2_fft.py? Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Can BBN 802.11 , Fedora 9, and Gnuradio 3.03 work well?
Hi all, I searched on the [Discuss-gnuradio] and got some information that BBN 802.11 can only be used with the earlier version of gnuradio.. About one and a half years ago (2007), I ran the BBN 802.11 with GNURadio 3.03 in Fedora 7. It worked well. I have not used the USRP for a long time. Now, I need to run the BBN 802.11 again; however, I am using Fedora 9 ( upgraded Fedora from 7 to 9). Does anyone know if BBN 802.11 , Fedora 9, and Gnuradio 3.03 can work well? I really don't want to break the USRP. Thank you, Jane ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Re: USRP2 and external clock (from GPS receiver)
Changkyu Seol wrote: Matt Ettus wrote: I tried as you suggested but it still drifts. I also added the following line in the firmware to make sure. clocks_mimo_config(MC_WE_LOCK_TO_SMA); I tried on several different USRP2s and I got same results. Any more suggestions? Are you sure you have a 10 MHz reference and not some other frequency? Matt ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP2 and external clock (from GPS receiver)
Douglas Geiger wrote: Is the test clock supposed to be running at 5kHz? I've just tested this on one of my USRP2 - it does appear to be locked with my external clock - - i.e. the 5kHz signal on the pin doesn't drift w.r.t my 10Mhz external No, the test clock runs as 100MHz/div where div is the 2nd argument to the function. The maximum value of div is 32. I think you are using a digital oscilloscope to view this, and you are seeing it alias because you turned the time per division up way too high. Change it to 100ns per division. Matt ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] USRP2 Gnuradio 3.1.3 and BBN 802.11 Code Working?
Hello, I'm working on a project that involves the USRP2. I've downloaded the lastest version of Gnuradio and the BBN 802.11 code. I've come to realize that the newest release of Gnuradio is not compatible with the BBN code. Is there an earlier version of gnuradio that will work with the USRP2 and the BBN code? Thanks, Miklos Christine ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP 2 Daughter Cards
On Thu, Feb 19, 2009 at 01:21:37PM -0500, jim graham wrote: > Eric > > We are using Fedora Linux version 7 on an x86 machine. OK. [Please be sure to hit Reply-All to reply to the writer and the list.] > The GNU radio software is Revision 10211 (jcorgan) > Last change date 1/12/2009 > > We have the USRP 2 connected to a directional antenna. I have used the > dbs daughtercard hooked to the same antenna with a USRP 1 to verify > a signal is present. > > For the dbs and lfrx daughtercards are the set_center_freq outputs of 0 for > Baseband freq and -commanded freq for ddc freq correct? > The output of the call using a flex1800 daughtercard is different. What rx_daughterboard_id() does the USRP2 report for your RFX 1800? With regard to RFX boards, the USRP2 only supports the MIMO_B version. Any board that the firmware doesn't recognize is treated as a Basic Rx or Basic Tx. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP2 Gnuradio 3.1.3 and BBN 802.11 Code Working?
On Thu, Feb 19, 2009 at 10:40:42AM -0800, Miklos Christine wrote: > Hello, > > I'm working on a project that involves the USRP2. I've downloaded the > lastest version of Gnuradio and the BBN 802.11 code. I've come to realize > that the newest release of Gnuradio is not compatible with the BBN code. > Is there an earlier version of gnuradio that will work with the USRP2 and > the BBN code? > > Thanks, > Miklos Christine The USRP2 is new. No early version of GNU Radio supports it. A bit of googling will find you several discussions about people updating the BBN code to work with the latest GR code. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
RE: [Discuss-gnuradio] USRP 2 Daughter Cards
Eric, rx_daughterboard_id() returns id 0x0034 for the RFX 1800 daughtercard? For the comment on the RFX boards; does this mean we are unable to use the dbs daughtercard on the USRP 2 unit? -- thanks jim == Jim Graham Black River Systems Company, Inc. 162 Genesee Street, Utica, NY 13502 e-mail : gra...@brsc.com voice : (315) 732-7385 x146 fax : (315) 732-5837 == -Original Message- From: 'Eric Blossom' [mailto:e...@comsec.com] Sent: Thursday, February 19, 2009 2:24 PM To: jim graham Cc: discuss-gnuradio@gnu.org Subject: Re: [Discuss-gnuradio] USRP 2 Daughter Cards On Thu, Feb 19, 2009 at 01:21:37PM -0500, jim graham wrote: > Eric > > We are using Fedora Linux version 7 on an x86 machine. OK. [Please be sure to hit Reply-All to reply to the writer and the list.] > The GNU radio software is Revision 10211 (jcorgan) > Last change date 1/12/2009 > > We have the USRP 2 connected to a directional antenna. I have used the > dbs daughtercard hooked to the same antenna with a USRP 1 to verify > a signal is present. > > For the dbs and lfrx daughtercards are the set_center_freq outputs of 0 for > Baseband freq and -commanded freq for ddc freq correct? > The output of the call using a flex1800 daughtercard is different. What rx_daughterboard_id() does the USRP2 report for your RFX 1800? With regard to RFX boards, the USRP2 only supports the MIMO_B version. Any board that the firmware doesn't recognize is treated as a Basic Rx or Basic Tx. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP 2 Daughter Cards
On Thu, Feb 19, 2009 at 02:52:41PM -0500, jim graham wrote: > Eric, > > rx_daughterboard_id() returns id 0x0034 for the RFX 1800 daughtercard? That's a MIMO B board, so you should be fine. > For the comment on the RFX boards; does this mean we are unable to use the > dbs daughtercard on the USRP 2 unit? No, the DBS RX is supported. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP2 Gnuradio 3.1.3 and BBN 802.11 Code Working?
If I revert to an old version of Gnuradio, would the USRP2 work with that? The Gnuradio code and BBN code that worked on the USRP, would it work on the USRP2? Is it backwards compatible? Thanks, Miklos Christine On Thu, Feb 19, 2009 at 11:26 AM, Eric Blossom wrote: > On Thu, Feb 19, 2009 at 10:40:42AM -0800, Miklos Christine wrote: > > Hello, > > > > I'm working on a project that involves the USRP2. I've downloaded the > > lastest version of Gnuradio and the BBN 802.11 code. I've come to realize > > that the newest release of Gnuradio is not compatible with the BBN code. > > Is there an earlier version of gnuradio that will work with the USRP2 and > > the BBN code? > > > > Thanks, > > Miklos Christine > > The USRP2 is new. No early version of GNU Radio supports it. > A bit of googling will find you several discussions about people > updating the BBN code to work with the latest GR code. > > Eric > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP2 and external clock (from GPS receiver)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matt Ettus wrote: > Douglas Geiger wrote: >> >> Is the test clock supposed to be running at 5kHz? I've just tested this >> on one of my USRP2 - it does appear to be locked with my external clock >> - - i.e. the 5kHz signal on the pin doesn't drift w.r.t my 10Mhz external > > > No, the test clock runs as 100MHz/div where div is the 2nd argument to > the function. The maximum value of div is 32. > > I think you are using a digital oscilloscope to view this, and you are > seeing it alias because you turned the time per division up way too > high. Change it to 100ns per division. > > Matt Ah - that's was the problem. Unfortunately my scope can only handle a single channel at 100MHz, so setting the divisor >2 helps. Unfortunately it appears the clock is not synchronized with my external 10MHz clock - any suggestions on further steps to debug why I'm having trouble? Thanks, Doug - -- Doug Geiger Research Assistant Communications and Signal Processing Lab Oklahoma State University http://cspl.okstate.edu douglas.gei...@okstate.edu doug.gei...@ieee.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJndsRgfOzzR5bXIgRAlZzAJ4wjTzE05MUZPXn2CfUFbnIJPRDqgCfcPKJ iSyctrCGAqKnewNpclJmwls= =+lqY -END PGP SIGNATURE- ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP2 and external clock (from GPS receiver)
Ah - that's was the problem. Unfortunately my scope can only handle a single channel at 100MHz, so setting the divisor >2 helps. Unfortunately it appears the clock is not synchronized with my external 10MHz clock - any suggestions on further steps to debug why I'm having trouble? I don't understand this. It works 100% of the time here. What code are you using? Matt ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP2 and external clock (from GPS receiver)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matt Ettus wrote: >> >> Ah - that's was the problem. Unfortunately my scope can only handle a >> single channel at 100MHz, so setting the divisor >2 helps. >> Unfortunately it appears the clock is not synchronized with my external >> 10MHz clock - any suggestions on further steps to debug why I'm having >> trouble? > > > I don't understand this. It works 100% of the time here. What code are > you using? > > Matt I'm at svn revision 10441 - with both the firmware and fpga code built from that (using Xilinx ISE 10.1 to make the fpga). I've just modified the txrx.c code - adding: clocks_enable_test_clk(true, 2); clocks_mimo_config(MC_WE_LOCK_TO_SMA); just before the while(1) loop My rx_mimo.cc code also calls ->config_mimo(MC_WE_LOCK_TO_SMA), but right now I've stepped back to just getting one USRP2 synchronized to my external source - which in this case is a function generator with a 10MHz sine with 2V P-P. Is it possible some of the hardware on my USRP2's isn't working? Thanks, Doug - -- Doug Geiger Research Assistant Communications and Signal Processing Lab Oklahoma State University http://cspl.okstate.edu douglas.gei...@okstate.edu doug.gei...@ieee.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJnd3vgfOzzR5bXIgRArCiAJ94oanfG0zxukks37qgQnImsqV90ACgqTku kEdLWYUjrAfR0ZrGhohxUIY= =kdz8 -END PGP SIGNATURE- ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP2 and external clock (from GPS receiver)
Douglas Geiger wrote: I'm at svn revision 10441 - with both the firmware and fpga code built from that (using Xilinx ISE 10.1 to make the fpga). I've just modified the txrx.c code - adding: clocks_enable_test_clk(true, 2); clocks_mimo_config(MC_WE_LOCK_TO_SMA); just before the while(1) loop My rx_mimo.cc code also calls ->config_mimo(MC_WE_LOCK_TO_SMA), but right now I've stepped back to just getting one USRP2 synchronized to my external source - which in this case is a function generator with a 10MHz sine with 2V P-P. Is it possible some of the hardware on my USRP2's isn't working? Unlikely, since it was tested before shipping. I will send you code to run in a separate email. Matt ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] There is no ./configure in gr-bbn?
Hi all, I got the code through cvs -d anon...@acert.ir.bbn.com:/cvs/adroitgrdevel co adroitgrdevel ,but there is no ./configure in gr-bbn. I ran autoconf, but got errors as follows: # autoconf configure.ac:25: error: possibly undefined macro: AM_CONFIG_HEADER If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:27: error: possibly undefined macro: AM_INIT_AUTOMAKE configure.ac:40: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL configure.ac:41: error: possibly undefined macro: AC_ENABLE_SHARED configure.ac:42: error: possibly undefined macro: AC_DISABLE_STATIC configure.ac:43: error: possibly undefined macro: AC_PROG_LIBTOOL How can I install the BBN? Thank you, Jane ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Re: Re: USRP2 and external clock (from GPS receiver)
Matt Ettus wrote: > Are you sure you have a 10 MHz reference and not some other frequency? > > Matt Yes. I also have tested with a function generator. Changkyu Seol -- Posted via http://www.ruby-forum.com/. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Re: Re: USRP2 and external clock (from GPS receiver)
Changkyu Seol wrote: Matt Ettus wrote: Are you sure you have a 10 MHz reference and not some other frequency? Matt Yes. I also have tested with a function generator. Changkyu Seol If you had a real email address, I would send you some code to try. Matt ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Installing Gnuradio in Fedora Core 6
Hi! I am installing the latest Gnuradio core in Fedora Core 6, I install all the requirements that you mention in the wiki and execute the installation of the gnuradio core. First I use the following secuence: svn co http://gnuradio.org/svn/gnuradio/branches/releases/3.1 gnuradio ./bootstrap ./configure make make check make install and when the proccess finishes I cant execute gnuradio ussing the grc command in terminal. then I explore the configure help and use the following secuence: BOOST_PREFIX=/opt/boost_1_37_0 export LD_LIBRARY_PATH=/opt/boost_1_37_0/lib ./bootstrap ./configure --with-boost=/opt/boost_1_37_0 --prefix=/usr/gnuradio --with-boost-include-dir=/opt/boost_1_37_0/include/boost-1_37 --enable-omnithread --enable-gnuradio-core --enable-usrp --enable-gr-usrp --enable-gr-atsc --enable-gr-gpio --enable-gr-gsm-fr-vocoder --enable-gr-pager --enable-gr-radar-mono --enable-gr-radio-astronomy --enable-gr-trellis --enable-gr-video-sdl --enable-gr-wxgui --enable-gr-sounder --enable-gr-utils --enable-gnuradio-examples and at the end of it I obtain the output: * The following GNU Radio components have been successfully configured: config gruel omnithread gnuradio-core pmt mblock usrp usrp2 gr-usrp gr-usrp2 gr-msdd6000 gr-audio-oss gr-atsc gr-cvsd-vocoder gr-gpio gr-gsm-fr-vocoder gr-pager gr-radar-mono gr-radio-astronomy gr-trellis gr-video-sdl gr-wxgui gr-sounder gr-utils gnuradio-examples You my now run the make command to build these components. * The following components were skipped either because you asked not to build them or they didn't pass configuration checks: gcell gr-gcell gr-audio-alsa gr-audio-jack gr-audio-osx gr-audio-portaudio gr-audio-windows gr-comedi gr-qtgui grc These components will not be built. I continue with the secuence to install gnuradio: make make check make install and again I can not execute gnuradio ussing grc or ussing one of the examples. Thanks sdjflkasf como soy yo -- Imagination is more important than knowledge - Albert Einstein ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Installing Gnuradio in Fedora Core 6
You are missing a dependency for GRC. If you read through the configure verbose, it will say what is missing (or version is too old). Also, make sure to install all the packages listed in http://gnuradio.org/trac/wiki/FedoraInstall See the following: http://gnuradio.org/trac/wiki/GNURadioCompanion#Requirements http://gnuradio.org/trac/wiki/GNURadioCompanion#Installation -Josh Pablo Mendoza wrote: Hi! I am installing the latest Gnuradio core in Fedora Core 6, I install all the requirements that you mention in the wiki and execute the installation of the gnuradio core. First I use the following secuence: svn co http://gnuradio.org/svn/gnuradio/branches/releases/3.1 gnuradio ./bootstrap ./configure make make check make install and when the proccess finishes I cant execute gnuradio ussing the grc command in terminal. then I explore the configure help and use the following secuence: BOOST_PREFIX=/opt/boost_1_37_0 export LD_LIBRARY_PATH=/opt/boost_1_37_0/lib ./bootstrap ./configure --with-boost=/opt/boost_1_37_0 --prefix=/usr/gnuradio --with-boost-include-dir=/opt/boost_1_37_0/include/boost-1_37 --enable-omnithread --enable-gnuradio-core --enable-usrp --enable-gr-usrp --enable-gr-atsc --enable-gr-gpio --enable-gr-gsm-fr-vocoder --enable-gr-pager --enable-gr-radar-mono --enable-gr-radio-astronomy --enable-gr-trellis --enable-gr-video-sdl --enable-gr-wxgui --enable-gr-sounder --enable-gr-utils --enable-gnuradio-examples and at the end of it I obtain the output: * The following GNU Radio components have been successfully configured: config gruel omnithread gnuradio-core pmt mblock usrp usrp2 gr-usrp gr-usrp2 gr-msdd6000 gr-audio-oss gr-atsc gr-cvsd-vocoder gr-gpio gr-gsm-fr-vocoder gr-pager gr-radar-mono gr-radio-astronomy gr-trellis gr-video-sdl gr-wxgui gr-sounder gr-utils gnuradio-examples You my now run the make command to build these components. * The following components were skipped either because you asked not to build them or they didn't pass configuration checks: gcell gr-gcell gr-audio-alsa gr-audio-jack gr-audio-osx gr-audio-portaudio gr-audio-windows gr-comedi gr-qtgui grc These components will not be built. I continue with the secuence to install gnuradio: make make check make install and again I can not execute gnuradio ussing grc or ussing one of the examples. Thanks sdjflkasf como soy yo ___ 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] There is no ./configure in gr-bbn?
On Thu, Feb 19, 2009 at 03:56:30PM -0800, Jane Chen wrote: > Hi all, > > I got the code through cvs -d anon...@acert.ir.bbn.com:/cvs/adroitgrdevel co > adroitgrdevel ,but there is no ./configure in gr-bbn. > > I ran autoconf, but got errors as follows: > > # autoconf > configure.ac:25: error: possibly undefined macro: AM_CONFIG_HEADER > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > configure.ac:27: error: possibly undefined macro: AM_INIT_AUTOMAKE > configure.ac:40: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL > configure.ac:41: error: possibly undefined macro: AC_ENABLE_SHARED > configure.ac:42: error: possibly undefined macro: AC_DISABLE_STATIC > configure.ac:43: error: possibly undefined macro: AC_PROG_LIBTOOL > > How can I install the BBN? > > Thank you, > Jane > Did you ./bootstrap before trying to configure? Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Re: Re: USRP2 and external clock (from GPS receiver)
I've tested this here in my lab, using a signal generator for the SMA reference input. With firmware modified to automatically set the clock source to the external reference, and to generate a test 10 MHz output waveform, I get a good lock when the external reference is anywhere between -13dBm and 10 dBm (142mV p-p to 2V p-p). This is using revision 10467 for both the FPGA and the firmware. Johnathan Corgan Corgan Enterprises LLC ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Re: Re: Re: USRP2 and external clock (from GPS receiver)
Matt Ettus wrote: > Changkyu Seol wrote: > > If you had a real email address, I would send you some code to try. > > Matt I sent you an email in order to let you know my email address. Changkyu Seol -- Posted via http://www.ruby-forum.com/. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Intel ATOM WHOOAAAAA Nellie
Many of us have and love the Intel ATOM 330 boards we have. I have 3 of them! I want to ask those who do not see an immediate need for them but are thinking about getting one for SDR purposes, I want to tell you that "better things are arriving" as always. The Nvidia ION will address almost 100% of the few gripes with the D945GCLF2 and D945GCLF (Intel Mobo) computers. The intel graphics chip, 3D/2D acceleration, is okay, but it is not great. The D945GCLF2 addressed the desire for 64 bit OS, but we still had pretty slow memory supporting slow DDR2. Unhappy with the PC VGA connector on the Intel? The Nvidia ION has HDMI output and 7.1 audio! The Nvidia ION address both of these shortcomings. The Nvidia ION has a memory of Nvidia's very impressive GPU's with the GEO Force (9300/9400) family. It is also supports DDR3 memory. Both of these factors will represent MAJOR improvements in the performance. Please, if you have not already purchased the Intel ATOM motherboards, hold up a bit. There is nothing wrong with the $80-$90 motherboards you currently have but these new ones will represent bit steps in the right direction. HOWEVER, for those folks who want to build an small board computer for supporting the Flex family of firewire devices, the Intel motherboards are your only choice. You need the PCI slot to get the firewire support. For those of us who want to support USB 2.0 or better yet, GigE, the Nvidia ION will provide more IO ports than the Intel motherboard and has the other advantages already mentioned here. You will need an external drive case to hold the drives as the eSata ports are on the back of the motherboard for Nvidia ION. So, no firewire needed? better memory and graphics needed? HDMI needed or desired? Wait for the Nvidia ION motherboards to become available to you in the second quarter of this year in desktops and motherboards. The ASUS N10Jc notebook are, or soon will be available. Bob -- (Co)Author: DttSP, Quiktrak, PowerSDR, GnuRadio Member: ARRL, AMSAT, AMSAT-DL, TAPR, Packrats, NJQRP, QRP ARCI, QCWA, FRC. "It is human nature to think wisely and act in an absurd fashion.", Anatole France. Twitter:rwmcgwier Active: Facebook,Myspace,LinkedIn ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Re: Re: Re: USRP2 and external clock (from GPS receiver)
Matt Ettus wrote: > Changkyu Seol wrote: > > If you had a real email address, I would send you some code to try. > > Matt Thank you for the files. I tested as you suggested with firmware and fpga files you sent me and it is locked!! I used it other USRP2s and all worked fine. I modified and compiled "txrx.c" in gnuradio (revision 10464, fedora 9) trunk to generate "txrx.bin". What was the problem? Changkyu Seol -- Posted via http://www.ruby-forum.com/. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] added new method to gr_file_sink.cc, but python can't see it.
I updated the appropriate .h and .i files, and re-built, but still python can't see the new method. How do you get new "stuff" in .i files included in the python environment? -- Marcus Leech Principal Investigator, Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Re: [dttsp-linux] Intel ATOM WHOOAAAAA Nellie
On Thu, Feb 19, 2009 at 11:17 PM, Bob McGwier wrote: ...HOWEVER, for those folks who want to build an small board computer for > supporting the Flex family of firewire devices, the Intel motherboards > are your only choice. You need the PCI slot to get the firewire support... For DttSP apps it's not a real choice. You will need a PCI slot, either for FireWire audio like the Edirol FA-66 or the PreSonus FireBox, or merely for some other halfway decent soundcard like the M-Audio Delta 44. This is a required configuration for effectively using sdr-shell, sdr-core, and the sdrTEC board, for example. A reference Linux implementation for this combination, with a cost of around $800US total for the RF front end + computer, is about ready to go up on CGRAN. The FireWire+Flex option is moot for dttsp-linux and vrk, but the other FireWire/PCI addons are critical. DttSP apps using the USRP1+GNU Radio are fine. USRP2 is an open question, for now. Short form: for dttsp-linux and general RF hardware, the Atom 330 is unquestionably the more utilitarian alternative. This is especially so when, given Nvidia's history regarding Open drivers, Linux support for ION is very uncertain in the near term (6-9 months). 73 Frank AB2KT -- Some people are like slinkies...not really good for anything, but they still bring a smile to your face when you push them down a flight of stairs. -- Anon. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Re: [dttsp-linux] Intel ATOM WHOOAAAAA Nellie
On Fri, Feb 20, 2009 at 12:36 AM, Frank Brickle wrote: [snip] > Short form: for dttsp-linux and general RF hardware, the Atom 330 is > unquestionably the more utilitarian alternative. This is especially so when, > given Nvidia's history regarding Open drivers, Linux support for ION is very > uncertain in the near term (6-9 months). Nvidia video is a pretty poor choice for Linux too— you're tied to their proprietary drivers which often cause weird bugs (usually the #1 cause of kernel panics on the kernelopps data collection project, right ahead of a proprietary wifi driver), and that driver ties you to whatever kernel and xorg versions they are willing to support. I'm not sure why the Intel video would be a problem for SDR apps. The Intel video in my laptop is great, though perhaps the atom has something more limited. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Re: Re: Re: USRP2 and external clock (from GPS receiver)
Changkyu Seol wrote: > Matt Ettus wrote: > Thank you for the files. > I tested as you suggested with firmware and fpga files you sent me and > it is locked!! I used it other USRP2s and all worked fine. > > I modified and compiled "txrx.c" in gnuradio (revision 10464, fedora 9) > trunk to generate "txrx.bin". What was the problem? > > Changkyu Seol I downloaded GNU radio by following command. (I am not used to linux.) $ svn co http://gnuradio.org/svn/gnuradio/trunk gnuradio "txrx.c" included seems to be very old version. Where can I get the latest firmware/fpga source codes? -- Posted via http://www.ruby-forum.com/. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] added new method to gr_file_sink.cc, but python can't see it.
try making from the gnuradio-core/src directory Marcus D. Leech wrote: I updated the appropriate .h and .i files, and re-built, but still python can't see the new method. How do you get new "stuff" in .i files included in the python environment? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio