[Discuss-gnuradio] --disable-all-components --enable-gr-usrp doesn't built
G'day, ./configure --sysconfdir=/usr/pkg/share/examples --disable-all-components --without-libintl-prefix --prefix=/usr/pkg --host=i386--netbsdelf --mandi r=/usr/pkg/man doesn't build due to usrp not being build. To reproduce, on a system with the usrp-module already installed, install a fresh tarball and try to build gr-usrp only. The following comment was found inside the configure script: # Don't do gr-usrp if usrp skipped # There *has* to be a better way to check if a value is in a string I consider this to be a bug since configure should check for availability of the usrp-module system wide and not just inside the tarball package. I successfully built gr-usrp after bypassing this limitation. Whilst most users will build usrp and gr-usrp together, IMHO, a fix is desirable in order to be consistent and enable modular packaging of gnuradio. cheerio Berndt ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Sampling rate mismatch in Fedora Core 5
Hi,After a long wait I recieved the hardware. I was trying to run FM Reciever but there is some problem related to the sampling rate of my computer. I received following error message: [EMAIL PROTECTED] usrp]# ./usrp_wfm_rcv.pyUsing RX d'board A: Basic Rx gr_fir_ccf: using SSE gr_fir_fff: using SSEaudio_alsa_sink[hw:0,0]: unable to support sampling rate 32000 card requested 44100 instead.** (python:16205): WARNING **: IPP request failed with status 1030 ** (python:16205): WARNING **: IPP request failed with status 1030 FYI: No Powermate or Contour Knob foundThe GUI is opening very well, and I can see the frequency spectrum. After getting this error, I wen to the control centre of Fedora Core 5, and changed the default sampling rate to 32000 Hz, but the problem was not resolved. Can somebody tell me how to deal with this problem? And, what does the IPP Request error tell exactly?Thank youTarun ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] discuss-gnuradio archive search not working
Hi,Just few hours back, the discuss-gnuradio archive search stopped working. Can somebody resolve the issue.Thank you,TarunPS: my local time is US Central, and writing this mail at 03:22 AM on 11/11/2006. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] gr-howto-write-a-block
G'day, are there any compelling reasons why this module isn't part of the main tree like the other modules? cheerio Berndt ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] hier_block
HiIm trying to implement a hier_block, but when do a sudo make install I get the following error:Byte-compiling python modules...qam_corr_demod.py File /usr/local/lib/python2.4/site-packages/python/qam_corr_demod.py, line 28 gr.hier_block.__init__(self, fg, self.qam_corr , self.qam_corr) ^SyntaxError: invalid syntaxdoes anyone know why this happend?best regardserlend ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Sampling rate mismatch in Fedora Core 5
2006/11/11, Tarun Tiwari [EMAIL PROTECTED]: The GUI is opening very well, and I can see the frequency spectrum. After getting this error, I wen to the control centre of Fedora Core 5, and changed the default sampling rate to 32000 Hz, but the problem was not resolved. Copy'n'pasted from the archives: The solution is to add -O plughw:0,0 to the end of your command line (without the quotes), which causes ALSA to resample the output to be at a compatible sample rate. -- Trond Danielsen ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] digital noise input
On Fri, Nov 10, 2006 at 07:23:07PM -0800, Oussama Sekkat wrote: On 11/10/06, Eric Blossom [EMAIL PROTECTED] wrote: Yes, I could enable the output pins from the host and just connect the rx_a_a to one of the debug inputs in the master_control module. I thaught it wouldn't make a difference if I just connect it directly to the DEBUG pins. Or does it? It depends on whether or not you need to be able to control the attached daughterboard too. I then load the .rbf file to the FPGA, connect the io_rx_a outputs of the LFRX daughter board to the logic analyzer and observe what I get. I make sure that no antenna is connected to the RX-A port. To my surprise, some of the upper bits toggle. For example, bit 11, 10, 9, 8, 5 ,4 , 3 ,2 ,1 0, toggle. Since I should only be getting noise, I was expecting to get a very low signal where only the least significant bit would be switiching between low and high values. Are they being driven or are they just floating? No antenna is connected to the RX-A and RX-B ports , so those are floating. But the debug pins are connected to the logic analyzer. (I am not sure if I answered you're question, when you say they are you referring to the DEBUG pins or the input ports? ) No, not the antenna, the i/o pins. My guess is that you haven't output enabled them. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Avoiding plug-n-fry design
It's beginning to look like future daughterboards should include an attenuator or fuse or something. This would avoid the idiotic result that you plug 'transmit' into 'receive', as any sane computer-oriented person would do, and (invisibly) fry your board. Having the same connector on the tx and rx ports makes it that much more likely to happen. (I'm not arguing that we should enter connector hell by making them different!) Prominently selling a loopback cable that includes an appropriate attenuator would also be a positive step. Perhaps each amplified transmiter should come with one, in a nice ethernet-orange color. John ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] --disable-all-components --enable-gr-usrp doesn't built
On Sat, Nov 11, 2006 at 07:39:37PM +1030, Berndt Josef Wulf wrote: G'day, ./configure --sysconfdir=/usr/pkg/share/examples --disable-all-components --without-libintl-prefix --prefix=/usr/pkg --host=i386--netbsdelf --mandi r=/usr/pkg/man doesn't build due to usrp not being build. Whilst most users will build usrp and gr-usrp together, IMHO, a fix is desirable in order to be consistent and enable modular packaging of gnuradio. Please create a new ticket for this issue in Trac. Login in as user: guest, password: gnuradio, then select New Ticket. There was some discussion of this a while ago, but it apparently didn't result in an ticket being created. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] hier_block
On Sat, Nov 11, 2006 at 12:43:01PM +0100, Erlend Barstad Strand wrote: Hi Im trying to implement a hier_block, but when do a sudo make install I get the following error: Byte-compiling python modules... qam_corr_demod.py File /usr/local/lib/python2.4/site-packages/python/qam_corr_demod.py, line 28 gr.hier_block.__init__(self, fg, self.qam_corr , self.qam_corr) ^ SyntaxError: invalid syntax does anyone know why this happend? best regards erlend Erlend, that's not much of a hint. It is a file that you wrote, right? Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] gr-howto-write-a-block
On Sat, Nov 11, 2006 at 10:42:09PM +1030, Berndt Josef Wulf wrote: G'day, are there any compelling reasons why this module isn't part of the main tree like the other modules? cheerio Berndt It is part of the tree from the svn point of view. It is designed to be built _outside_ of the tree so that folks can generate their own extensions without be constantly stomped on when we update the main tree. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
