|
From: | OG LESS |
Subject: | Re: [Discuss-gnuradio] create-gnuradio-out-of-tree-project |
Date: | Wed, 17 Aug 2011 14:06:41 +0100 |
> Did you link against libgruel? Try that. > From: address@hidden > Subject: Discuss-gnuradio Digest, Vol 105, Issue 16 > To: address@hidden > Date: Tue, 16 Aug 2011 12:01:07 -0400 > > Send Discuss-gnuradio mailing list submissions to > address@hidden > > To subscribe or unsubscribe via the World Wide Web, visit > https://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. Re: The format of I/Q sample (xi yang) > 2. Re: The format of I/Q sample (Marcus D. Leech) > 3. Re: The format of I/Q sample (yooxi) > 4. Re: The format of I/Q sample (Marcus D. Leech) > 5. Re: The format of I/Q sample (yooxi) > 6. Re: Configuring the slave for MIMO cable (wes.rumble) > 7. Re: Configuring the slave for MIMO cable (Josh Blum) > 8. Re: Configuring the slave for MIMO cable (wes.rumble) > 9. Re: xlating filter will introduce phase shift (Page Jack) > 10. doubt about linking library to gnuradio (patiljagdish154) > 11. Re: doubt about linking library to gnuradio (Martin Braun) > 12. Re: doubt about linking library to gnuradio (patiljagdish154) > 13. Re: doubt about linking library to gnuradio (Marcus M?ller) > 14. Re: benchmark OFDM Question (waqasme) > 15. Problem with N200 and waterfall display in grc (Isaac Gerg) > 16. create-gnuradio-out-of-tree-project (OG LESS) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 15 Aug 2011 13:22:24 -0400 > From: xi yang <address@hidden> > To: Tom Rondeau <address@hidden> > Cc: address@hidden > Subject: Re: [Discuss-gnuradio] The format of I/Q sample > Message-ID: > <address@hidden> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, Tom, > > Thanks a lot for your prompt reply! > Do you mean on the Transmitting side? > I want to know how 32-bit floating point number is converted to 16bits or > from 16bits to 32bits. > Where can I find the file that performs this conversion? > > We are actually working on the Receiving side. > Before we move I/Q samples from rx_buffer to USB, we want to do FFT and > deliver the FFT results instead of the raw I/Q samples to the host. > For my FPGA FFT module, I use 32bits floating point numbers as input. > So I want to know how the I/Q samples are represented by 16bits so that I > can convert them to 32bits. > In 32bits representation, bits 0 through 22 form the mantissa, bits 23 > through 30 form the exponent, and bit 31 is the sign bit. > In 16bits, do we simply cut 16bits of the mantissa? > Then bits 0 through 6 form the mantissa, bits7 through 14 form the > exponent,and bit 15 is the sign bit. Is that right? > It's better if we can have a look at the conversion file. > > Thanks, > Yooxi > > > 2011/8/15 Tom Rondeau <address@hidden> > > > On Mon, Aug 15, 2011 at 12:48 AM, xi yang <address@hidden> wrote: > > > Hi, all > > > > > > I want to use fpga to do FFT before the data are transmitted to usb. > > > > > > In FFT module, I used float point numbers to be its input. According to > > the > > > IEEE Floating-Point Standard, a float point number is represented by 32 > > bits > > > (bits 0 through 22 form the mantissa, bits 23 through 30 form the > > exponent, > > > and bit 31 is the sign bit). However, in GNU Radio, the UHD drive sends > > > 16bits I, and 16bits Q. > > > > > > Are I and Q float point numbers? How do the 16bits represent a float > > number? > > > Any suggestion about the I/Q's format is appreciated! > > > > > > Thanks, > > > Yooxi > > > > The interface to the USRP is defined to take floating point numbers. > > It will perform the conversion to the 16-bit shorts that are sent over > > the wire for you. Also remember that the output of the FFT is a > > vector, so you'll want to use the gr_vector_to_stream block to convert > > it back to a stream of floating point samples. > > > > Tom > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: </archive/html/discuss-gnuradio/attachments/20110815/5be07760/attachment.html> > > ------------------------------ > > Message: 2 > Date: Mon, 15 Aug 2011 13:27:11 -0400 > From: "Marcus D. Leech" <address@hidden> > To: address@hidden > Subject: Re: [Discuss-gnuradio] The format of I/Q sample > Message-ID: <address@hidden> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 08/15/2011 01:22 PM, xi yang wrote: > > Hi, Tom, > > > > Thanks a lot for your prompt reply! > > Do you mean on the Transmitting side? > > I want to know how 32-bit floating point number is converted to 16bits > > or from 16bits to 32bits. > > Where can I find the file that performs this conversion? > > > > We are actually working on the Receiving side. > > Before we move I/Q samples from rx_buffer to USB, we want to do FFT > > and deliver the FFT results instead of the raw I/Q samples to the host. > > For my FPGA FFT module, I use 32bits floating point numbers as input. > > So I want to know how the I/Q samples are represented by 16bits so > > that I can convert them to 32bits. > > In 32bits representation, bits 0 through 22 form the mantissa, bits 23 > > through 30 form the exponent, and bit 31 is the sign bit. > > In 16bits, do we simply cut 16bits of the mantissa? > > Then bits 0 through 6 form the mantissa, bits7 through 14 form the > > exponent,and bit 15 is the sign bit. Is that right? > > It's better if we can have a look at the conversion file. > > Thanks, > > Yooxi > > > The host interface uses 16-bit integers for I and Q. They're only > represented as floating-point numbers within a Gnu Radio flow-graph. > > Internally in the FPGA, everything is integers, starting with 12-bit > integers from the ADC (on the USRP1), then through the CIC decimators > and DDC, they become larger, but what is finally injected into the > host is 16-bit (integer) I and 16-bit (integer) Q. > Standard twos-complement representation for the integers, I don't > happen to recall off the top of my head whether they're "big endian" > or "little endian". > > > > > > > -- > Marcus Leech > Principal Investigator > Shirleys Bay Radio Astronomy Consortium > http://www.sbrac.org > > > > > > ------------------------------ > > Message: 3 > Date: Mon, 15 Aug 2011 10:38:44 -0700 (PDT) > From: yooxi <address@hidden> > To: address@hidden > Subject: Re: [Discuss-gnuradio] The format of I/Q sample > Message-ID: <address@hidden> > Content-Type: text/plain; charset=us-ascii > > > Hi, Marcus, > > Thanks a lot for your quick reply! > Then start from where, the integers become floating point numbers? > I'd like to see how they are converted. > > Thanks, > Yooxi > > > Marcus D. Leech wrote: > > > > On 08/15/2011 01:22 PM, xi yang wrote: > >> Hi, Tom, > >> > >> Thanks a lot for your prompt reply! > >> Do you mean on the Transmitting side? > >> I want to know how 32-bit floating point number is converted to 16bits > >> or from 16bits to 32bits. > >> Where can I find the file that performs this conversion? > >> > >> We are actually working on the Receiving side. > >> Before we move I/Q samples from rx_buffer to USB, we want to do FFT > >> and deliver the FFT results instead of the raw I/Q samples to the host. > >> For my FPGA FFT module, I use 32bits floating point numbers as input. > >> So I want to know how the I/Q samples are represented by 16bits so > >> that I can convert them to 32bits. > >> In 32bits representation, bits 0 through 22 form the mantissa, bits 23 > >> through 30 form the exponent, and bit 31 is the sign bit. > >> In 16bits, do we simply cut 16bits of the mantissa? > >> Then bits 0 through 6 form the mantissa, bits7 through 14 form the > >> exponent,and bit 15 is the sign bit. Is that right? > >> It's better if we can have a look at the conversion file. > >> Thanks, > >> Yooxi > >> > > The host interface uses 16-bit integers for I and Q. They're only > > represented as floating-point numbers within a Gnu Radio flow-graph. > > > > Internally in the FPGA, everything is integers, starting with 12-bit > > integers from the ADC (on the USRP1), then through the CIC decimators > > and DDC, they become larger, but what is finally injected into the > > host is 16-bit (integer) I and 16-bit (integer) Q. > > Standard twos-complement representation for the integers, I don't > > happen to recall off the top of my head whether they're "big endian" > > or "little endian". > > > > > > > > > > > > > > -- > > Marcus Leech > > Principal Investigator > > Shirleys Bay Radio Astronomy Consortium > > http://www.sbrac.org > > > > > > > > _______________________________________________ > > Discuss-gnuradio mailing list > > address@hidden > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > > > > -- > View this message in context: http://old.nabble.com/The-format-of-I-Q-sample-tp32262153p32266070.html > Sent from the GnuRadio mailing list archive at Nabble.com. > > > > > ------------------------------ > > Message: 4 > Date: Mon, 15 Aug 2011 13:45:12 -0400 > From: "Marcus D. Leech" <address@hidden> > To: address@hidden > Subject: Re: [Discuss-gnuradio] The format of I/Q sample > Message-ID: <address@hidden> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > Hi, Marcus, > > > > Thanks a lot for your quick reply! > > Then start from where, the integers become floating point numbers? > > I'd like to see how they are converted. > > > > Thanks, > > Yooxi > > > They are never floating-point numbers inside the FPGA or on the host > interface. For UHD, they get scaled and converted > inside the appropriate files. I can't tell you which specific file, > but the UHD source code is available, and I'm sure Josh > could tell you where the conversion between host-transport-format and > gnuradio-format happens with UHD/gr-uhd. > > -- > Marcus Leech > Principal Investigator > Shirleys Bay Radio Astronomy Consortium > http://www.sbrac.org > > > > > > ------------------------------ > > Message: 5 > Date: Mon, 15 Aug 2011 10:50:01 -0700 (PDT) > From: yooxi <address@hidden> > To: address@hidden > Subject: Re: [Discuss-gnuradio] The format of I/Q sample > Message-ID: <address@hidden> > Content-Type: text/plain; charset=us-ascii > > > Hi, Marcus, > > Thanks a lot! > We will look into the UHD source code. > > Best regards, > Yooxi > > > > Marcus D. Leech wrote: > > > >> Hi, Marcus, > >> > >> Thanks a lot for your quick reply! > >> Then start from where, the integers become floating point numbers? > >> I'd like to see how they are converted. > >> > >> Thanks, > >> Yooxi > >> > > They are never floating-point numbers inside the FPGA or on the host > > interface. For UHD, they get scaled and converted > > inside the appropriate files. I can't tell you which specific file, > > but the UHD source code is available, and I'm sure Josh > > could tell you where the conversion between host-transport-format and > > gnuradio-format happens with UHD/gr-uhd. > > > > -- > > Marcus Leech > > Principal Investigator > > Shirleys Bay Radio Astronomy Consortium > > http://www.sbrac.org > > > > > > > > _______________________________________________ > > Discuss-gnuradio mailing list > > address@hidden > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > > > > -- > View this message in context: http://old.nabble.com/The-format-of-I-Q-sample-tp32262153p32266153.html > Sent from the GnuRadio mailing list archive at Nabble.com. > > > > > ------------------------------ > > Message: 6 > Date: Mon, 15 Aug 2011 12:07:17 -0700 (PDT) > From: "wes.rumble" <address@hidden> > To: address@hidden > Subject: Re: [Discuss-gnuradio] Configuring the slave for MIMO cable > Message-ID: <address@hidden> > Content-Type: text/plain; charset=us-ascii > > > I see what you meant Josh, thanks for your help. One more quick question, as > simple as it seems I still have to make sure. In the flowgraph in GRC I > will need 2 UHD sources right? One with the default ref source and one with > the MIMO cable as its source. Assuming that's correct, is there a way I can > add the 2 streams in order to decode the incoming data, (in my case > streaming video)? > -- > View this message in context: http://old.nabble.com/Configuring-the-slave-for-MIMO-cable-tp32235863p32266652.html > Sent from the GnuRadio mailing list archive at Nabble.com. > > > > > ------------------------------ > > Message: 7 > Date: Mon, 15 Aug 2011 12:12:09 -0700 > From: Josh Blum <address@hidden> > To: address@hidden > Subject: Re: [Discuss-gnuradio] Configuring the slave for MIMO cable > Message-ID: <address@hidden> > Content-Type: text/plain; charset=ISO-8859-1 > > > > On 08/15/2011 12:07 PM, wes.rumble wrote: > > > > I see what you meant Josh, thanks for your help. One more quick question, as > > simple as it seems I still have to make sure. In the flowgraph in GRC I > > will need 2 UHD sources right? One with the default ref source and one with > > Use exactly one source block w/ 2 channels. That way, uhd performs the > time-alignment of the streams. > > Example of the device addressing for multiple mboards: > http://www.ettus.com/uhd_docs/manual/html/usrp2.html#multiple-device-configuration > > -josh > > > > ------------------------------ > > Message: 8 > Date: Mon, 15 Aug 2011 12:25:41 -0700 (PDT) > From: "wes.rumble" <address@hidden> > To: address@hidden > Subject: Re: [Discuss-gnuradio] Configuring the slave for MIMO cable > Message-ID: <address@hidden> > Content-Type: text/plain; charset=us-ascii > > > That makes perfect sense now, thanks. Now that there are 2 channels I have 2 > outputs which I can't directly feed into my demodulator/decoder. Is there a > way in GRC to combine the 2 streams in order to only have 1 demod/decoder > with the hopes of observing the array gain from the 2nd USRP at my output? > > > Josh Blum-3 wrote: > > > > > > > > > > Use exactly one source block w/ 2 channels. That way, uhd performs the > > time-alignment of the streams. > > > > Example of the device addressing for multiple mboards: > > http://www.ettus.com/uhd_docs/manual/html/usrp2.html#multiple-device-configuration > > > > -josh > > > > _______________________________________________ > > Discuss-gnuradio mailing list > > address@hidden > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > > > > -- > View this message in context: http://old.nabble.com/Configuring-the-slave-for-MIMO-cable-tp32235863p32266765.html > Sent from the GnuRadio mailing list archive at Nabble.com. > > > > > ------------------------------ > > Message: 9 > Date: Tue, 16 Aug 2011 09:33:49 +0800 > From: Page Jack <address@hidden> > To: Tom Rondeau <address@hidden> > Cc: address@hidden > Subject: Re: [Discuss-gnuradio] xlating filter will introduce phase > shift > Message-ID: > <address@hidden> > Content-Type: text/plain; charset="iso-8859-1" > > Hi Tom, > the xlating filter work fine, the phase shift is cause by another factor. > Thanks for your > reply. > > On Sun, Aug 14, 2011 at 4:17 AM, Tom Rondeau <address@hidden> wrote: > > > On Fri, Aug 12, 2011 at 3:50 AM, Page Jack <address@hidden> wrote: > > > I use xlating filter to down convert signal. after I down convert signal > > it > > > I decode it. > > > however the data decoded is still the signal in 0 frequency before down > > > convert. > > > I check the xlating filter code it will change the signal phase to avoid > > > aliasing, yeah > > > it avoid aliasing but it is not the data I want how can I recover the > > data's > > > phase after > > > xlating filter? > > > > > > Regards! > > > > Those filters are implemented as FIRs, which means they will have > > linear phase in the passband and constant (and known) group delay. > > > > In general, though, you will never know the phase of the incoming > > signal received over the air. If you have a signal where you require > > the phase, you'll have to figure out a way to recover it, anyways. > > > > Tom > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: </archive/html/discuss-gnuradio/attachments/20110816/563de0fa/attachment.html> > > ------------------------------ > > Message: 10 > Date: Tue, 16 Aug 2011 01:57:19 -0700 (PDT) > From: patiljagdish154 <address@hidden> > To: address@hidden > Subject: [Discuss-gnuradio] doubt about linking library to gnuradio > Message-ID: <address@hidden> > Content-Type: text/plain; charset=us-ascii > > > hi all, > i want to know while installing block in gnuradio , if i didn't get error > it's that means i had linked the library. > actually i am working on comedi-gnuradio. while installing the block(for > comedi) i didn't get any error. > > comedi is collection of drivers for a variety of common data acquisition > plug-in boards . comedilib is a user-space library that provides a > developer-friendly interface to Comedi devices. > > to compile comedi code in C language i used > gcc -filename.c -lcomedi -lm > > can any one tell me how include comedi library in gnuradio. > what i did is i made modification in Makefile.common in main folder . check > for attachment (Makefile.common) . i made changes in line 26 > http://old.nabble.com/file/p32270282/Makefile.common Makefile.common > AM_CXXFLAGS = @autoconf_default_CXXFLAGS@ \ > -lcomedi -lm -I/usr/include -L/usr/lib > > > i am using ubuntu 10.10 and gnuradio 3.3.0 > > > thanks > > -- > View this message in context: http://old.nabble.com/doubt-about-linking-library-to-gnuradio-tp32270282p32270282.html > Sent from the GnuRadio mailing list archive at Nabble.com. > > > > > ------------------------------ > > Message: 11 > Date: Tue, 16 Aug 2011 11:13:26 +0200 > From: Martin Braun <address@hidden> > To: address@hidden > Subject: Re: [Discuss-gnuradio] doubt about linking library to > gnuradio > Message-ID: <address@hidden> > Content-Type: text/plain; charset="utf-8" > > On Tue, Aug 16, 2011 at 01:57:19AM -0700, patiljagdish154 wrote: > > hi all, > > i want to know while installing block in gnuradio , if i didn't get error > > it's that means i had linked the library. > > actually i am working on comedi-gnuradio. while installing the block(for > > comedi) i didn't get any error. > > > > comedi is collection of drivers for a variety of common data acquisition > > plug-in boards . comedilib is a user-space library that provides a > > developer-friendly interface to Comedi devices. > > > > to compile comedi code in C language i used > > gcc -filename.c -lcomedi -lm > > > > can any one tell me how include comedi library in gnuradio. > > what i did is i made modification in Makefile.common in main folder . check > > for attachment (Makefile.common) . i made changes in line 26 > > http://old.nabble.com/file/p32270282/Makefile.common Makefile.common > > AM_CXXFLAGS = @autoconf_default_CXXFLAGS@ \ > > -lcomedi -lm -I/usr/include -L/usr/lib > > Hi patiljagdish154, > > libcomedi support for GNU Radio was deprecated a few versions ago. I > think the last version with comedi support was 3.2.2--you should check > out old versions of GNU Radio to see how this works. There's no need to > do all the work yourself, much has been done already. > > MB > > -- > Karlsruhe Institute of Technology (KIT) > Communications Engineering Lab (CEL) > > Dipl.-Ing. Martin Braun > Research Associate > > Kaiserstra?e 12 > Building 05.01 > 76131 Karlsruhe > > Phone: +49 721 608-43790 > Fax: +49 721 608-46071 > www.cel.kit.edu > > KIT -- University of the State of Baden-W?rttemberg and > National Laboratory of the Helmholtz Association > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 198 bytes > Desc: not available > URL: </archive/html/discuss-gnuradio/attachments/20110816/76a619b0/attachment.pgp> > > ------------------------------ > > Message: 12 > Date: Tue, 16 Aug 2011 04:19:26 -0700 (PDT) > From: patiljagdish154 <address@hidden> > To: address@hidden > Subject: Re: [Discuss-gnuradio] doubt about linking library to > gnuradio > Message-ID: <address@hidden> > Content-Type: text/plain; charset=UTF-8 > > > thanks. > i am close to finished it. in my synaptic manager gnuradio 3.2.2 is not > available. > i had gone through those files also , some files are missing . > > > Martin Braun-4 wrote: > > > > On Tue, Aug 16, 2011 at 01:57:19AM -0700, patiljagdish154 wrote: > >> hi all, > >> i want to know while installing block in gnuradio , if i didn't get > >> error > >> it's that means i had linked the library. > >> actually i am working on comedi-gnuradio. while installing the block(for > >> comedi) i didn't get any error. > >> > >> comedi is collection of drivers for a variety of common data acquisition > >> plug-in boards . comedilib is a user-space library that provides a > >> developer-friendly interface to Comedi devices. > >> > >> to compile comedi code in C language i used > >> gcc -filename.c -lcomedi -lm > >> > >> can any one tell me how include comedi library in gnuradio. > >> what i did is i made modification in Makefile.common in main folder . > >> check > >> for attachment (Makefile.common) . i made changes in line 26 > >> http://old.nabble.com/file/p32270282/Makefile.common Makefile.common > >> AM_CXXFLAGS = @autoconf_default_CXXFLAGS@ \ > >> -lcomedi -lm -I/usr/include -L/usr/lib > > > > Hi patiljagdish154, > > > > libcomedi support for GNU Radio was deprecated a few versions ago. I > > think the last version with comedi support was 3.2.2--you should check > > out old versions of GNU Radio to see how this works. There's no need to > > do all the work yourself, much has been done already. > > > > MB > > > > -- > > Karlsruhe Institute of Technology (KIT) > > Communications Engineering Lab (CEL) > > > > Dipl.-Ing. Martin Braun > > Research Associate > > > > Kaiserstra?e 12 > > Building 05.01 > > 76131 Karlsruhe > > > > Phone: +49 721 608-43790 > > Fax: +49 721 608-46071 > > www.cel.kit.edu > > > > KIT -- University of the State of Baden-W?rttemberg and > > National Laboratory of the Helmholtz Association > > > > > > > > _______________________________________________ > > Discuss-gnuradio mailing list > > address@hidden > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > > > > -- > View this message in context: http://old.nabble.com/doubt-about-linking-library-to-gnuradio-tp32270282p32270720.html > Sent from the GnuRadio mailing list archive at Nabble.com. > > > > > ------------------------------ > > Message: 13 > Date: Tue, 16 Aug 2011 13:44:07 +0200 > From: Marcus M?ller <address@hidden> > To: address@hidden > Subject: Re: [Discuss-gnuradio] doubt about linking library to > gnuradio > Message-ID: <address@hidden> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi Jagdish Patil, > Archives of old Versions can be found at > http://ftp.gnu.org/gnu/gnuradio/ > Since you'll have to compile things anyway, installing from source won't > hurt you. > > Version 3.2.2 is included in debian sid as well as in Ubuntu since lucid, > so I guess you either run an outdated system or a rather obscure one, > meaning that installing most libraries from source might be good advice > anyway. > > Greetings > Marcus M?ller > > Am 16.08.2011 13:19, schrieb patiljagdish154: > > thanks. > > i am close to finished it. in my synaptic manager gnuradio 3.2.2 is not > > available. > > i had gone through those files also , some files are missing . > > > > > > Martin Braun-4 wrote: > >> On Tue, Aug 16, 2011 at 01:57:19AM -0700, patiljagdish154 wrote: > >>> hi all, > >>> i want to know while installing block in gnuradio , if i didn't get > >>> error > >>> it's that means i had linked the library. > >>> actually i am working on comedi-gnuradio. while installing the block(for > >>> comedi) i didn't get any error. > >>> > >>> comedi is collection of drivers for a variety of common data acquisition > >>> plug-in boards . comedilib is a user-space library that provides a > >>> developer-friendly interface to Comedi devices. > >>> > >>> to compile comedi code in C language i used > >>> gcc -filename.c -lcomedi -lm > >>> > >>> can any one tell me how include comedi library in gnuradio. > >>> what i did is i made modification in Makefile.common in main folder . > >>> check > >>> for attachment (Makefile.common) . i made changes in line 26 > >>> http://old.nabble.com/file/p32270282/Makefile.common Makefile.common > >>> AM_CXXFLAGS = @autoconf_default_CXXFLAGS@ \ > >>> -lcomedi -lm -I/usr/include -L/usr/lib > >> Hi patiljagdish154, > >> > >> libcomedi support for GNU Radio was deprecated a few versions ago. I > >> think the last version with comedi support was 3.2.2--you should check > >> out old versions of GNU Radio to see how this works. There's no need to > >> do all the work yourself, much has been done already. > >> > >> MB > >> > >> -- > >> Karlsruhe Institute of Technology (KIT) > >> Communications Engineering Lab (CEL) > >> > >> Dipl.-Ing. Martin Braun > >> Research Associate > >> > >> Kaiserstra?e 12 > >> Building 05.01 > >> 76131 Karlsruhe > >> > >> Phone: +49 721 608-43790 > >> Fax: +49 721 608-46071 > >> www.cel.kit.edu > >> > >> KIT -- University of the State of Baden-W?rttemberg and > >> National Laboratory of the Helmholtz Association > >> > >> > >> > >> _______________________________________________ > >> Discuss-gnuradio mailing list > >> address@hidden > >> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > >> > >> > > > > > ------------------------------ > > Message: 14 > Date: Tue, 16 Aug 2011 04:45:18 -0700 (PDT) > From: waqasme <address@hidden> > To: address@hidden > Subject: Re: [Discuss-gnuradio] benchmark OFDM Question > Message-ID: <address@hidden> > Content-Type: text/plain; charset=us-ascii > > > Thank you so much Tom for your quick response.. yes i have found the code > scripts in gnurdio-examples/python/ofdm. > But iam not sure how to implement this code to make simulation in GNU radio. > could you please explain in bit detail how to use this code to make the > tranmission and reception blocks in GNU Radio. I will really appriciate if > you kindly guide me how to make this simulation work. Thanks for your help > and for your valuable information. looking forward to hear from you. > Anyone is welcome to answer ... > > Regards, > > Waqas. > address@hidden > > -- > View this message in context: http://old.nabble.com/benchmark-OFDM-Question-tp31765422p32271118.html > Sent from the GnuRadio mailing list archive at Nabble.com. > > > > > ------------------------------ > > Message: 15 > Date: Tue, 16 Aug 2011 11:33:08 -0400 > From: Isaac Gerg <address@hidden> > To: address@hidden > Subject: [Discuss-gnuradio] Problem with N200 and waterfall display in > grc > Message-ID: > <address@hidden> > Content-Type: text/plain; charset="iso-8859-1" > > Hi Everyone, > > I have a USRP N200 rev 2. I created a simple graph using the gnu radio > companion (grc) which is composed of three blocks, a UHD source, a variable > slider, and a WX FFT Waterfall display. When I run this graph, i quickly > see the waterfall display fill up with the color blue and then the > application becomes unresponsive. How can I fix this? > > When I run the uhd_fft tool, it appears to work correctly -- it shows me a > spectrum and allows me to adjust the fc and the gain. > > Also, where can i find a guide to the N200 debug lights? Lights C, E, and F > seem to be on all the time. Is this okay? > > Thanks in advance, > Isaac > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: </archive/html/discuss-gnuradio/attachments/20110816/3fbd51fd/attachment.html> > > ------------------------------ > > Message: 16 > Date: Tue, 16 Aug 2011 16:42:38 +0100 > From: OG LESS <address@hidden> > To: <address@hidden> > Subject: [Discuss-gnuradio] create-gnuradio-out-of-tree-project > Message-ID: <address@hidden> > Content-Type: text/plain; charset="iso-8859-1" > > > What file do I need to link to, to get rid of the following error (make)?: > > undefined reference to `gr_msg_accepter::post(boost::intrusive_ptr<pmt::pmt_base>)' > > Alot of similar errors are removed when linking the file /usr/lib/libgnuradio-core.la, however, I don't know why this one isn't going anyway? > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: </archive/html/discuss-gnuradio/attachments/20110816/143aff37/attachment.html> > > ------------------------------ > > _______________________________________________ > Discuss-gnuradio mailing list > address@hidden > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > > End of Discuss-gnuradio Digest, Vol 105, Issue 16 > ************************************************* |
[Prev in Thread] | Current Thread | [Next in Thread] |