Re: [Discuss-gnuradio] Another question about making a signal processing block
Eric, Thanks so much! I will try them first time tomorrow morning. Zhenghao On Mon, May 19, 2008 at 11:30 PM, Eric Blossom <[EMAIL PROTECTED]> wrote: > On Mon, May 19, 2008 at 10:45:41PM -0400, Zhenghao Zhang wrote: >> Thanks for helping me on this! >> >> autoconf (GNU Autoconf) 2.61 >> automake (GNU automake) 1.10 >> > > OK, those look fine. > > Try this: > >rm -fr config.cache autom4te*.cache > >aclocal -I config >autoconf >autoheader >libtoolize --automake >automake --add-missing -c -f -Wno-portability > >./configure >make && make check > > > [I realized that we're not distributing the "bootstrap" script with > the tarballs. I'll fix that in a minute.] > > Eric > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Another question about making a signal processing block
On Mon, May 19, 2008 at 10:45:41PM -0400, Zhenghao Zhang wrote: > Thanks for helping me on this! > > autoconf (GNU Autoconf) 2.61 > automake (GNU automake) 1.10 > OK, those look fine. Try this: rm -fr config.cache autom4te*.cache aclocal -I config autoconf autoheader libtoolize --automake automake --add-missing -c -f -Wno-portability ./configure make && make check [I realized that we're not distributing the "bootstrap" script with the tarballs. I'll fix that in a minute.] Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Another question about making a signal processing block
Thanks for helping me on this! autoconf (GNU Autoconf) 2.61 automake (GNU automake) 1.10 On Mon, May 19, 2008 at 10:40 PM, Eric Blossom <[EMAIL PROTECTED]> wrote: > On Mon, May 19, 2008 at 09:46:03PM -0400, Zhenghao Zhang wrote: >> Thanks for the help! I will check it. >> >> automake has been complaining about not being able tofind PYTHON variable: >> >> src/lib/Makefile.am:55: Python sources seen but `PYTHON' is undefined >> >> After adding `AM_PATH_PYTHON' micro to Makefile.am, automake does not >> complain any more. I actually don't think I should be doing this >> because it should be automatically done, I guess. The missing of the >> CC variable may due to the same problem. >> >> Thanks again for the help! >> >> Zhenghao > > What versions of automake and autoconf do you have? > > $ autoconf --version > $ automake --version > > Eric > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Another question about making a signal processing block
On Mon, May 19, 2008 at 09:46:03PM -0400, Zhenghao Zhang wrote: > Thanks for the help! I will check it. > > automake has been complaining about not being able tofind PYTHON variable: > > src/lib/Makefile.am:55: Python sources seen but `PYTHON' is undefined > > After adding `AM_PATH_PYTHON' micro to Makefile.am, automake does not > complain any more. I actually don't think I should be doing this > because it should be automatically done, I guess. The missing of the > CC variable may due to the same problem. > > Thanks again for the help! > > Zhenghao What versions of automake and autoconf do you have? $ autoconf --version $ automake --version Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Another question about making a signal processing block
Thanks for the help! I will check it. automake has been complaining about not being able tofind PYTHON variable: src/lib/Makefile.am:55: Python sources seen but `PYTHON' is undefined After adding `AM_PATH_PYTHON' micro to Makefile.am, automake does not complain any more. I actually don't think I should be doing this because it should be automatically done, I guess. The missing of the CC variable may due to the same problem. Thanks again for the help! Zhenghao On Mon, May 19, 2008 at 9:25 PM, Michael Dickens <[EMAIL PROTECTED]> wrote: > > On May 19, 2008, at 9:08 PM, Zhenghao Zhang wrote: >> >> But make is giving me problems. It seemed to be complaining about not >> being able to find "fvirtual", therefore the no zzblk.cc is produced >> and g++ cannot find the source file to compile. The detailed messages >> are the follows. Any hint is greatly appreciated. Thanks! > > The shell environment variable CC isn't getting picked up properly by > configure, or it is not correctly defined in your shell environment. > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Another question about making a signal processing block
On May 19, 2008, at 9:08 PM, Zhenghao Zhang wrote: But make is giving me problems. It seemed to be complaining about not being able to find "fvirtual", therefore the no zzblk.cc is produced and g++ cannot find the source file to compile. The detailed messages are the follows. Any hint is greatly appreciated. Thanks! The shell environment variable CC isn't getting picked up properly by configure, or it is not correctly defined in your shell environment. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Another question about making a signal processing block
Hi, I was trying to make a signal processing block. I basically did nothing but copied the ``how-to-write-a-block'' package and modified the name of the block in files according to the Shen tutorial.With the help from Philip, I got around several make problems I asked earlier. The automake passes with two messages that do not seem to be bad: [EMAIL PROTECTED] trytry]# automake doc/Makefile.am:77: `%'-style pattern rules are a GNU make extension doc/Makefile.am:80: `%'-style pattern rules are a GNU make extension But make is giving me problems. It seemed to be complaining about not being able to find "fvirtual", therefore the no zzblk.cc is produced and g++ cannot find the source file to compile. The detailed messages are the follows. Any hint is greatly appreciated. Thanks! Zhenghao [EMAIL PROTECTED] trytry]# make make all-recursive make[1]: Entering directory `/root/USRP/USRP_try/zztryblock/trytry' Making all in config make[2]: Entering directory `/root/USRP/USRP_try/zztryblock/trytry/config' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/USRP/USRP_try/zztryblock/trytry/config' Making all in src make[2]: Entering directory `/root/USRP/USRP_try/zztryblock/trytry/src' Making all in lib make[3]: Entering directory `/root/USRP/USRP_try/zztryblock/trytry/src/lib' fvirtual -python -modern -I/root/gnuradio-3.1.2/gnuradio-core/src/lib/swig -I/root/gnuradio-3.1.2/gnuradio-core/src/lib -module zzblk -o zzblk.cc ../../src/lib/zzblk.i make[3]: fvirtual: Command not found make[3]: [zzblk.cc] Error 127 (ignored) fvirtual -python -modern -I/root/gnuradio-3.1.2/gnuradio-core/src/lib/swig -I/root/gnuradio-3.1.2/gnuradio-core/src/lib -module zzblk -o zzblk.cc ../../src/lib/zzblk.i make[3]: fvirtual: Command not found make[3]: [zzblk.py] Error 127 (ignored) make all-am make[4]: Entering directory `/root/USRP/USRP_try/zztryblock/trytry/src/lib' fvirtual -python -modern -I/root/gnuradio-3.1.2/gnuradio-core/src/lib/swig -I/root/gnuradio-3.1.2/gnuradio-core/src/lib -module zzblk -o zzblk.cc ../../src/lib/zzblk.i make[4]: fvirtual: Command not found make[4]: [zzblk.cc] Error 127 (ignored) /bin/sh ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../.. -DOMNITHREAD_POSIX=1 -pthread -I/usr/local/include/gnuradio-g -O2 -MT zzblk.lo -MD -MP -MF .deps/zzblk.Tpo -c -o zzblk.lo zzblk.cc g++ -DHAVE_CONFIG_H -I. -I../.. -DOMNITHREAD_POSIX=1 -pthread -I/usr/local/include/gnuradio -g -O2 -MT zzblk.lo -MD -MP -MF .deps/zzblk.Tpo -c zzblk.cc -fPIC -DPIC -o .libs/zzblk.o g++: zzblk.cc: No such file or directory g++: no input files make[4]: *** [zzblk.lo] Error 1 make[4]: Leaving directory `/root/USRP/USRP_try/zztryblock/trytry/src/lib' make[3]: *** [all] Error 2 make[3]: Leaving directory `/root/USRP/USRP_try/zztryblock/trytry/src/lib' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/root/USRP/USRP_try/zztryblock/trytry/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/USRP/USRP_try/zztryblock/trytry' make: *** [all] Error 2 ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Packets and m-blocks
Greetings. Some time ago created a number of GNURadio signal processing blocks for audio codecs, and have recently gotten around to finishing them up for public release (Speex and CELT, along with the speex acoustic echo canceler). Constant bitrate support was a piece of cake (and wow does Speex sound better than GSM FR, I forgot how bad GSM was... ;) ) However, I'm stuck on supporting variable bitrate mode. I basically want to present a variable sized packet interface for the coded side. It seems that the m-block code is what I want to use for that ... but I can't find any examples of m-block code that I could emulate. Can someone kick me in the right direction? ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Problem with Installation of GNU radio
Hi Prasanna, I tried installing GNU radio in windows using cygwin. I did it as it was given on the gnuradio.org website. I initially built a minimal GNU radio system, with just omnithread, gnuradio-core and gr-audio-oss modules enabled and it worked fine. Then I when I tried to build a full GNU radio system, it gave me the following error in the usrp module- mkdir -p html xmlto html-nochunks ../../usrp/doc/usrp_guide.xml xmlto: input does not validate http://www.oasis-open.org/docbook/xml/4.2/1:parser error : Content error in the external subset I have not been able to make xmlto work with the GNU Radio xml files on Cygwin. Since this is just the documentation that is failing, you can build GNU Radio without it. One way is to get rid of xmlto (uninstall it with Cygwin setup, remove it from /usr/bin, or rename it), then rerun configure and try it again. Another solution is to edit usrp/doc/Makefile to remove usrp_guide.html from the DOCBOOK_HTML_FILES line, but you will need to do this every time you run configure. The best solution (aside from making xmlto work) would be to figure out how to tell configure to ignore xmlto. If anyone knows why xmlto doesn't work (on Cygwin), please let us know. -- Don W. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Modulation problem ?
Eric Blossom wrote: On Mon, May 19, 2008 at 05:15:12AM -0700, irene159 wrote: Hello, I am testing QPSK modulation. To do so, I have created a text file that I modulate and demodulate with blks2impl dqpsk.py. The problem is the resulting demodulated file, which I can not open: "Could not open the file Resultat.txt. gedit has not been able to detect the character coding. Please check that you are not trying to open a binary file. Select a character coding from the menu and try again." Help would be appreciated. Please find code files below. Regards, Irene http://www.nabble.com/file/p17316660/Modulation.py Modulation.py http://www.nabble.com/file/p17316660/Demodulation.py Demodulation.py -- How about: $ cat Resultat.txt or $ less Resultat.txt Or : od -tx1 Resultat.txt | less to get hex bytes to see what's going on at a binary level. @(^.^)@ Ed ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] make question about building a signal processing block
Hi, I was trying to see if I could build a signal processing block. I basically did nothing but copied the ``how-to-write-a-block'' package and modified the name of the block in files according to the Shen tutorial. I ran aclocal, autoconf, ./configure, all seemed to be fine. Then I ran automake, which gave me these mesages: [EMAIL PROTECTED] trytry]# automake doc/Makefile.am:77: `%'-style pattern rules are a GNU make extension doc/Makefile.am:80: `%'-style pattern rules are a GNU make extension src/lib/Makefile.am:55: Python sources seen but `PYTHON' is undefined src/lib/Makefile.am:55: The usual way to define `PYTHON' is to add `AM_PATH_PYTHON' src/lib/Makefile.am:55: to `configure.ac' and run `aclocal' and `autoconf' again. src/python/Makefile.am:31: Python sources seen but `PYTHON' is undefined src/python/Makefile.am:31: The usual way to define `PYTHON' is to add `AM_PATH_PYTHON' src/python/Makefile.am:31: to `configure.ac' and run `aclocal' and `autoconf' again. I don't think PYTHON is defined. Any hints will be greatly appreciated. Thanks. Zhenghao ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Problem with Installation of GNU radio
Hello, I tried installing GNU radio in windows using cygwin. I did it as it was given on the gnuradio.org website. I initially built a minimal GNU radio system, with just omnithread, gnuradio-core and gr-audio-oss modules enabled and it worked fine. Then I when I tried to build a full GNU radio system, it gave me the following error in the usrp module- mkdir -p html xmlto html-nochunks ../../usrp/doc/usrp_guide.xml xmlto: input does not validate http://www.oasis-open.org/docbook/xml/4.2/1:parser error : Content error in the external subset http://www.oasis-open.org/docbook/xml/4.2/1:parser error : Content error in the external subset http://www.nabble.com/Problem-with-Installation-of-GNU--radio-tp17310699p17310699.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] Basic Unix help
It seems like there are a lot of people coming to GNU radio without a Unix background. This is prompting a lot of newbie type questions that are covered in basic Unix/Linux intros. Does anyone have a good list of Unix intro resources (that are especially good for GNU Radio users) that could help answer new user questions and hopefully reduce the number of beginner Unix questions? Philip ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Modulation problem ?
On Mon, May 19, 2008 at 05:15:12AM -0700, irene159 wrote: > > Hello, > > I am testing QPSK modulation. To do so, I have created a text file that I > modulate and demodulate with blks2impl dqpsk.py. The problem is the > resulting demodulated file, which I can not open: > > "Could not open the file Resultat.txt. > gedit has not been able to detect the character coding. > Please check that you are not trying to open a binary file. > Select a character coding from the menu and try again." > > Help would be appreciated. Please find code files below. > > Regards, > Irene > > http://www.nabble.com/file/p17316660/Modulation.py Modulation.py > http://www.nabble.com/file/p17316660/Demodulation.py Demodulation.py > -- How about: $ cat Resultat.txt or $ less Resultat.txt ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Modulation problem ?
On May 19, 2008, at 8:15 AM, irene159 <[EMAIL PROTECTED]> wrote: Hello, I am testing QPSK modulation. To do so, I have created a text file that I modulate and demodulate with blks2impl dqpsk.py. The problem is the resulting demodulated file, which I can not open: "Could not open the file Resultat.txt. gedit has not been able to detect the character coding. Please check that you are not trying to open a binary file. Select a character coding from the menu and try again." Help would be appreciated. Please find code files below. I'm on a mobile so I can't look at the files. But look at the file sink type of your final output and the block that feeds it. My guess is that its of type float or something where each float represents a bit in "unpacked" binary format Not the bit packed ASCII you are expecting. - George ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Differential QPSK modulation resampling
On May 19, 2008, at 5:42 AM, irene159 <[EMAIL PROTECTED]> wrote:
Hello,
Just another question concerning the file "gr_mpsk_receiver_cc.cc".
In the extract of code below, why are phase_error_detector_generic and
decision_generic used for all BPSK, QPSK and other modulations?
Have optimized algorithms for BPSK and QPSK already been implemented?
// Select a phase detector and a decision maker for the modulation
order
switch(d_M) {
case 2: // optimized algorithms for BPSK
d_phase_error_detector =
&gr_mpsk_receiver_cc::phase_error_detector_generic; //bpsk;
d_decision = &gr_mpsk_receiver_cc::decision_generic; //bpsk;
break;
case 4: // optimized algorithms for QPSK
d_phase_error_detector =
&gr_mpsk_receiver_cc::phase_error_detector_generic; //qpsk;
d_decision = &gr_mpsk_receiver_cc::decision_generic; //qpsk;
break;
default: // generic algorithms for any M (power of 2?) but not pretty
d_phase_error_detector =
&gr_mpsk_receiver_cc::phase_error_detector_generic;
d_decision = &gr_mpsk_receiver_cc::decision_generic;
break;
This is just a guess based on the block names... But given that the
block names have "generic" in them, I'd guess they are generic enough
to work with psk modulations given some configuration.
- George
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Modulation problem ?
This is not surprising. It is likely that you are getting some initial
garbage (non-standard-ascii characters) coming out, or that you have
some bit errors.
Don't open it in gedit. Try:
python
f = open('Resultat.txt')
d = f.read()
f.close()
print(len(d))
print(d)
(or if d is really long, print(d[:50]))
On Mon, May 19, 2008 at 8:15 AM, irene159 <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I am testing QPSK modulation. To do so, I have created a text file that I
> modulate and demodulate with blks2impl dqpsk.py. The problem is the
> resulting demodulated file, which I can not open:
>
> "Could not open the file Resultat.txt.
> gedit has not been able to detect the character coding.
> Please check that you are not trying to open a binary file.
> Select a character coding from the menu and try again."
>
> Help would be appreciated. Please find code files below.
>
> Regards,
> Irene
>
> http://www.nabble.com/file/p17316660/Modulation.py Modulation.py
> http://www.nabble.com/file/p17316660/Demodulation.py Demodulation.py
> --
> View this message in context:
> http://www.nabble.com/Modulation-problem---tp17316660p17316660.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 mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Modulation problem ?
Hello, I am testing QPSK modulation. To do so, I have created a text file that I modulate and demodulate with blks2impl dqpsk.py. The problem is the resulting demodulated file, which I can not open: "Could not open the file Resultat.txt. gedit has not been able to detect the character coding. Please check that you are not trying to open a binary file. Select a character coding from the menu and try again." Help would be appreciated. Please find code files below. Regards, Irene http://www.nabble.com/file/p17316660/Modulation.py Modulation.py http://www.nabble.com/file/p17316660/Demodulation.py Demodulation.py -- View this message in context: http://www.nabble.com/Modulation-problem---tp17316660p17316660.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
Re: [Discuss-gnuradio] Differential QPSK modulation resampling
Hello,
Just another question concerning the file "gr_mpsk_receiver_cc.cc".
In the extract of code below, why are phase_error_detector_generic and
decision_generic used for all BPSK, QPSK and other modulations?
Have optimized algorithms for BPSK and QPSK already been implemented?
// Select a phase detector and a decision maker for the modulation order
switch(d_M) {
case 2: // optimized algorithms for BPSK
d_phase_error_detector =
&gr_mpsk_receiver_cc::phase_error_detector_generic; //bpsk;
d_decision = &gr_mpsk_receiver_cc::decision_generic; //bpsk;
break;
case 4: // optimized algorithms for QPSK
d_phase_error_detector =
&gr_mpsk_receiver_cc::phase_error_detector_generic; //qpsk;
d_decision = &gr_mpsk_receiver_cc::decision_generic; //qpsk;
break;
default: // generic algorithms for any M (power of 2?) but not pretty
d_phase_error_detector =
&gr_mpsk_receiver_cc::phase_error_detector_generic;
d_decision = &gr_mpsk_receiver_cc::decision_generic;
break;
}
Regards,
Irene
--
View this message in context:
http://www.nabble.com/Differential-QPSK-modulation-resampling-tp17276806p17314530.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
