[Discuss-gnuradio] Regarding USRP examples
Hi all, 1) We are running the USRP examples on USRP board fsk_tx.py and fsk_rx.py on one PC. During execution we are receiving too much of noise, what might be the reason?.any solution? 2) Can we run both fsk_tx.py and fsk_rx.py simultaneously on the same PC or do we need to run them on two different PCs ? 3) While running nbfm_ptt_quick_and_dirty.py we are receiving lot of noise. Please provide some solution? 4) As suggested in the USRP document , We are using the antenna with following specifications 1. Electrical Characteristics: Operating Frequency 2.4~2.5 & 4.9 & 5.15~5.35 & 5.725~5.85 GHz Antenna Type: Dipole Polarization Type : Linear Type of Radiation: Toroidal Peak Gain 2.0 dBi Typical For 2 G 4.0 dBi Typical For 5 G Impedance: 50 Ohm nominal V.S.W.R. 2.0:1 Max. 2 . Mechanical Characteristics Swivel : 90 degrees Connector: SMA(M) Core : N/A ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] gnuradio make error
hi I face problem when “make”ing the gnuradio 2.5 tarball version. FYI, I’m using Redhat Fedora 2. Followings are the error message displayed. make all-recursive make[1]: Entering directory `/root/SDRLinux/Program/gnuradio-core-2.5' Making all in config make[2]: Entering directory `/root/SDRLinux/Program/gnuradio-core-2.5/config' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/SDRLinux/Program/gnuradio-core-2.5/config' Making all in src make[2]: Entering directory `/root/SDRLinux/Program/gnuradio-core-2.5/src' Making all in gen_interpolator_taps make[3]: Entering directory `/root/SDRLinux/Program/gnuradio-core-2.5/src/gen_interpolator_taps' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/root/SDRLinux/Program/gnuradio-core-2.5/src/gen_interpolator_taps' Making all in lib make[3]: Entering directory `/root/SDRLinux/Program/gnuradio-core-2.5/src/lib' Making all in missing make[4]: Entering directory `/root/SDRLinux/Program/gnuradio-core-2.5/src/lib/missing' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/root/SDRLinux/Program/gnuradio-core-2.5/src/lib/missing' Making all in runtime make[4]: Entering directory `/root/SDRLinux/Program/gnuradio-core-2.5/src/lib/runtime' if /bin/sh ../../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/lib/runtime -I../../../src/lib/general -I../../../src/lib/filter -I../../../src/lib/io -I../../../src/lib/g72x -I../../../src/lib/atsc -I../../../src/lib/omnithread -I../../../src/lib/general -I../../../src/lib/filter -I/usr/local/include -I/usr/local/include -g -O2 -Wall -Woverloaded-virtual -pthread -MT gr_block.lo -MD -MP -MF ".deps/gr_block.Tpo" -c -o gr_block.lo gr_block.cc; \ then mv -f ".deps/gr_block.Tpo" ".deps/gr_block.Plo"; else rm -f ".deps/gr_block.Tpo"; exit 1; fi g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/lib/runtime -I../../../src/lib/general -I../../../src/lib/filter -I../../../src/lib/io -I../../../src/lib/g72x -I../../../src/lib/atsc -I../../../src/lib/omnithread -I../../../src/lib/general -I../../../src/lib/filter -I/usr/local/include -I/usr/local/include -g -O2 -Wall -Woverloaded-virtual -pthread -MT gr_block.lo -MD -MP -MF .deps/gr_block.Tpo -c gr_block.cc -fPIC -DPIC -o .libs/gr_block.o make[4]: Leaving directory `/root/SDRLinux/Program/gnuradio-core-2.5/src/lib/runtime' make[3]: Leaving directory `/root/SDRLinux/Program/gnuradio-core-2.5/src/lib' make[2]: Leaving directory `/root/SDRLinux/Program/gnuradio-core-2.5/src' make[1]: Leaving directory `/root/SDRLinux/Program/gnuradio-core-2.5' Please help! Thanks Jimmy ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] binary installer gnuradio-2.5cvs.win32.exe for windows
Hi guys, Any updates to the mingw usrp gnuradio binary installation files to allow for the examples to work with the usrp on windows? Stephane mentioned previously that gnuradio-core/usrp/gr-usrp needs to be updated in the installer. If not, how can i go about doing it manually? many thanks, mike http://m0mik.org/gnuradio On 28/07/05, Stephane Fillod <[EMAIL PROTECTED]> wrote: > Hi Mike, > > Selon mjam01 <[EMAIL PROTECTED]>: > > thanks eric, that solved that bit... now here's the next one. i've > > tried running various sample codes and this error happens everytime. > > > > > [...] > > src = usrp.source_c (0, decim, 1, gru.hexint(0xf0f0f0f2), 0) > > File "C:\Python24\lib\site-packages\gnuradio\usrp.py", line 86, in > > source_c > > return ((usrp0.source_c, > > usrp1.source_c)[look_for_usrp(which)])(which, *args, **kwargs) > > File "C:\Python24\lib\site-packages\gnuradio\usrp1.py", line 1263, in > > source_c > > return _usrp1.source_c(*args) > > RuntimeError: std::runtime_error > > -- > > Are you using the snapshot from Martin? > This binary installer needs an update (gnuradio-core/usrp/gr-usrp) > to work with the examples. If thing goes well, we might generate > a new one soon.. > > -- > Stephane > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
RE: [Discuss-gnuradio] grnudadio-core test code
Title: RE: [Discuss-gnuradio] grnudadio-core test code that's fine, I will just have to work it out. I've noticed that there is some problem with shared libraries using gcc-3.4. I reverted to 3.3.3 & the behaviour changed - still doesn't work though. Using the audio-windows stuff, I've found there is a stack corruption when I call methods of a class in a shared library. I'm sure this is compiler related & perhaps related to the test stuff Anyway, my question is this. Has the gnuradio stuff ever fully worked under cygwin? I thought the answer was yes, but it is now broken. Is this right? Perhaps I can just roll stuff back until it works again & then see what changed. cheers, andrew ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] debugging C code called from python
Title: debugging C code called from python Hi, what is the best way to debug C++ code called from python? Is it possible to use gdb? Or is the idea to get everything working through test-cases first & hence avoid the issue? cheers, andrew ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] tv-reception
Hi all, Prateek Dayal wrote: have u had any success with tv reception on gnuradio I am all caught up in a new job here and still fighting out to take out some time to work on this .. even my net connection has not been installed yet at home :( John Gilmore wrote: > Thanks for your ongoing work on this. Television, here we come! The > next part, I think, will be looking for the sync pulse, throwing away > the samples before it. Eric has written such code before for HDTV, he > can suggest where to look or what to do. (He's improved the core > buffer/sched code since then too, and may recommend using a new > capability.) Eric, can you give a hint? > > Copyright notice on the new code should be 2005, e.g. in gr_float_to_uchar. > (There's always *some* nit that could be improved!) I will patch this nasty bug ;-) I am working on it right now. There is a preliminary tv-reception example in cvs now. gnuradio-examples\python\usrp\tvrx_tv_rcv.py I got some images that way. I am working on improved code right now. (Got some better images) First thing was to convert to unsigned char in stead of char. Next thing is an agc (I have a somewhat working version of an agc, using standard blocks in python which is quite computationally intensive) I also made an gr_agc_ff block based on gr_agc.h which should work better/faster. Using an agc you can get rid of the scale and offset parameter in the tvrx_tv_rcv.py example. What I am doing now is building a block which does am detection using a synchronous am_detector in stead of complex_to_mag (this block contains agc, pll and complex multiplier. This is all in one block because the different signals for phase-detection and agc are re-used and interact with each-other) This is mainly based on the FPLL which is in the old atsc code. This block is also quite computationally intensive but should give us a cleaner video signal. I haven't decoded video with it yet, but is seams to lock to a generated sinus if the initial frequency is close enough. I want to have a clean and stable videosignal before we try to detect the sync-pulses. I found that the right setting for rfgain and ifgain in the tvrx frontend is quite important. This should be included in the agc loop but I don't know yet how. Is there a way to send and get signals to other blocks in the flow-graph? (This will probably be usrp tvrx specific so this code probably can't go into gnuradio-core) Greetings, Martin ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] binary installer gnuradio-2.5cvs.win32.exe for windows
mjam01 wrote: Hi guys, Any updates to the mingw usrp gnuradio binary installation files to allow for the examples to work with the usrp on windows? Stephane mentioned previously that gnuradio-core/usrp/gr-usrp needs to be updated in the installer. Haven't made a new binary installer yet. I am trying to cleanup the installer (separate libusb files from usrp files) and currently it is broken (usrp dlls are not copied anywhere). It will be there soon. If not, how can i go about doing it manually? METHOD 1: I dumped all latest versions of gnuradio related files in http://www.olifantasia.com/pub/projects/gnuradio/mdvh/mingw/binary/latest/ Remove all *.pyo and *.pyc files (or all files) in your site-packages/gnuradio dir and copy the files in sitepackages_latest_bin.zip over them copy the files in msys_1.0_local_share_usrp.zip to somewhere on your filesystem set environment variable USRP_PATH to this directory (it will also find it if you have the files in your mingw /usr/local/share/usrp directory) (use forward slashed, for example c:/usrp) copy the files in msys_1.0_local_bin.zip to somewhere on your path. (I don't remember if I already put this files somewhere in the site-packages dir) METHOD 2: get latest cvs version of usrp, gr-usrp and gnuradio-core. build and install them with mingw see http://comsec.com/wiki?MinGW (I am not sure if all latest versions are checked in yet, must check as soon as I reboot into windows) Greetings, Martin many thanks, mike http://m0mik.org/gnuradio On 28/07/05, Stephane Fillod <[EMAIL PROTECTED]> wrote: Hi Mike, Selon mjam01 <[EMAIL PROTECTED]>: thanks eric, that solved that bit... now here's the next one. i've tried running various sample codes and this error happens everytime. [...] src = usrp.source_c (0, decim, 1, gru.hexint(0xf0f0f0f2), 0) File "C:\Python24\lib\site-packages\gnuradio\usrp.py", line 86, in source_c return ((usrp0.source_c, usrp1.source_c)[look_for_usrp(which)])(which, *args, **kwargs) File "C:\Python24\lib\site-packages\gnuradio\usrp1.py", line 1263, in source_c return _usrp1.source_c(*args) RuntimeError: std::runtime_error -- Are you using the snapshot from Martin? This binary installer needs an update (gnuradio-core/usrp/gr-usrp) to work with the examples. If thing goes well, we might generate a new one soon.. -- Stephane ___ 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] debugging C code called from python
Hi Andrew,
Hi, what is the best way to debug C++ code called
from python? Is it possible to use gdb? Or is the
idea to get everything working through test-cases
first & hence avoid the issue?
from the how-to-write-a-block documentation/wiki
Debugging with gdb
If your block isn't working, and you can't sort it out through python test cases or a few printfs in the code, you may want to use gdb to debug
it. The trick of course is that all of GNU Radio, including your new block, is dynamically loaded into python for execution.
Try this: In your python test code, after the relevant imports, print out the process id and wait for a keystroke. In another window run gdb and
tell it to attach to the python process with the given process id. At this point you can set breakpoints or whatever in your code. Go back to
the python window and hit Enter so it'll continue.
#!/usr/bin/env python
from gnuradio import gr
from gnuradio import my_buggy_module
# insert this in your test code...
import os
print 'Blocked waiting for GDB attach (pid = %d)' % (os.getpid(),)
raw_input ('Press Enter to continue: ')
# remainder of your test code follows...
Another SNAFU you might run into is that gdb 6.2 isn't able to set breakpoints in the constructors or destructors generated by g++ 3.4. In this
case, insert a call to the nop function gri_debugger_hook in the constructor and recompile. Load the code as before and set a break point on
gri_debugger_hook.
This even works on windows although you have to use the cygwin version of gdb
(or insight)
The cygwin gdb also works with the version of gnuradio built with mingw.
(the mingw gdb doesn't seem to work for me)
greetings,
Martin
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] binary installer gnuradio-2.5cvs.win32.exe for windows
thanks, i'll give it a go. much appreciated! :) mike On 09/08/05, Martin Dvh <[EMAIL PROTECTED]> wrote: > mjam01 wrote: > > Hi guys, > > > > Any updates to the mingw usrp gnuradio binary installation files to > > allow for the examples to work with the usrp on windows? Stephane > > mentioned previously that gnuradio-core/usrp/gr-usrp needs to be > > updated in the installer. > Haven't made a new binary installer yet. > I am trying to cleanup the installer (separate libusb files from usrp files) > and currently it is broken (usrp dlls are not copied anywhere). > It will be there soon. > > > > If not, how can i go about doing it manually? > METHOD 1: > I dumped all latest versions of gnuradio related files in > http://www.olifantasia.com/pub/projects/gnuradio/mdvh/mingw/binary/latest/ > > Remove all *.pyo and *.pyc files (or all files) in your > site-packages/gnuradio dir and copy the files in > sitepackages_latest_bin.zip over them > > copy the files in msys_1.0_local_share_usrp.zip to somewhere on your > filesystem > set environment variable USRP_PATH to this directory (it will also find it if > you have the files in your mingw /usr/local/share/usrp directory) > (use forward slashed, for example c:/usrp) > > copy the files in msys_1.0_local_bin.zip to somewhere on your path. (I don't > remember if I already put this files somewhere in the site-packages > dir) > > METHOD 2: > get latest cvs version of usrp, gr-usrp and gnuradio-core. > build and install them with mingw > see http://comsec.com/wiki?MinGW > > (I am not sure if all latest versions are checked in yet, must check as soon > as I reboot into windows) > > Greetings, > Martin > > > > many thanks, > > > > mike > > http://m0mik.org/gnuradio > > > > On 28/07/05, Stephane Fillod <[EMAIL PROTECTED]> wrote: > > > >>Hi Mike, > >> > >>Selon mjam01 <[EMAIL PROTECTED]>: > >> > >>>thanks eric, that solved that bit... now here's the next one. i've > >>>tried running various sample codes and this error happens everytime. > >>> > >>> > >> > >>[...] > >> > >>>src = usrp.source_c (0, decim, 1, gru.hexint(0xf0f0f0f2), 0) > >>> File "C:\Python24\lib\site-packages\gnuradio\usrp.py", line 86, in > >>> source_c > >>>return ((usrp0.source_c, > >>>usrp1.source_c)[look_for_usrp(which)])(which, *args, **kwargs) > >>> File "C:\Python24\lib\site-packages\gnuradio\usrp1.py", line 1263, in > >>>source_c > >>>return _usrp1.source_c(*args) > >>>RuntimeError: std::runtime_error > >>>-- > >> > >>Are you using the snapshot from Martin? > >>This binary installer needs an update (gnuradio-core/usrp/gr-usrp) > >>to work with the examples. If thing goes well, we might generate > >>a new one soon.. > >> > >>-- > >>Stephane > >> > > > > > > > > ___ > > 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] NTSC decoding
Just wondering if there's been any leaps or bounds in progress of NTSC decoding. We are still working on decoding the NTSC video signal in python. Has there been any progress in converting the MATLAB code to python? thom rainwater [EMAIL PROTECTED] http://www-personal.umich.edu/~trainwat ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] gnuradio make error
On Tue, Aug 09, 2005 at 04:01:53PM +0800, Jimmy Wong (DiGi - Central) wrote: > hi > > > > I face problem when "make"ing the gnuradio 2.5 tarball version. > FYI, I'm using Redhat Fedora 2. > > Followings are the error message displayed. I didn't see any error indicated in the messages listed. Try capturing both stdout and stderr: $ make 2>&1 | tee make.log Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] debugging C code called from python
On Tue, Aug 09, 2005 at 09:21:31PM +0930, Beck, Andrew Thomas - BECAT001 wrote: > Hi, what is the best way to debug C++ code called > from python? Is it possible to use gdb? Yes. See http://www.gnu.org/software/gnuradio/doc/howto-write-a-block.html#debugging > Or is the idea to get everything working through test-cases > first & hence avoid the issue? Test cases are a good idea ;-) > cheers, > andrew Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] tv-reception, some example captured images
captured tv images: http://www.olifantasia.com/pub/projects/gnuradio/mdvh/examples/tv/ greetings, Martin ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] tv-reception, some example captured images
On Tue, Aug 09, 2005 at 07:05:17PM +0200, Martin Dvh wrote: > captured tv images: > http://www.olifantasia.com/pub/projects/gnuradio/mdvh/examples/tv/ > Very nice! Great progress since What the Hack. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] tv-reception
FYI, I've fiddled with NTSC a bit. One big help is to work on Cable instead of OTA. Cable has a hundred channels that the tvrx can tune to with high snr and little multipath. I also determined that a 2 MSPS data rate seems to be enough for a basic black and white image, although its best to interpolate back up by 4x to get good horizontal resolution in the image. - Original Message - From: Martin Dvh <[EMAIL PROTECTED]> Date: Tuesday, August 9, 2005 9:38 am Subject: [Discuss-gnuradio] tv-reception > Hi all, > Prateek Dayal wrote: > > have u had any success with tv reception on gnuradio I am all > > caught up in a new job here and still fighting out to take out some > > time to work on this .. even my net connection has not been > installed> yet at home :( > John Gilmore wrote: > > Thanks for your ongoing work on this. Television, here we > come! The > > next part, I think, will be looking for the sync pulse, > throwing away > > the samples before it. Eric has written such code before for > HDTV, he > > can suggest where to look or what to do. (He's improved the core > > buffer/sched code since then too, and may recommend using a new > > capability.) > Eric, can you give a hint? > > > > Copyright notice on the new code should be 2005, e.g. in > gr_float_to_uchar. > (There's always *some* nit that could be > improved!)I will patch this nasty bug ;-) > > > I am working on it right now. > There is a preliminary tv-reception example in cvs now. > gnuradio-examples\python\usrp\tvrx_tv_rcv.py > I got some images that way. > > I am working on improved code right now. > (Got some better images) > First thing was to convert to unsigned char in stead of char. > > Next thing is an agc (I have a somewhat working version of an agc, > using standard blocks in python which is quite computationally > intensive)I also made an gr_agc_ff block based on gr_agc.h which > should work better/faster. > > Using an agc you can get rid of the scale and offset parameter in > the tvrx_tv_rcv.py example. > > What I am doing now is building a block which does am detection > using a synchronous am_detector in stead of complex_to_mag > (this block contains agc, pll and complex multiplier. This is all > in one block because the different signals for phase-detection and > agc are > re-used and interact with each-other) > This is mainly based on the FPLL which is in the old atsc code. > > This block is also quite computationally intensive but should give > us a cleaner video signal. > I haven't decoded video with it yet, but is seams to lock to a > generated sinus if the initial frequency is close enough. > > I want to have a clean and stable videosignal before we try to > detect the sync-pulses. > > I found that the right setting for rfgain and ifgain in the tvrx > frontend is quite important. > This should be included in the agc loop but I don't know yet how. > Is there a way to send and get signals to other blocks in the flow- > graph?(This will probably be usrp tvrx specific so this code > probably can't go into gnuradio-core) > > Greetings, > Martin > > > ___ > 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] copyright
Hi all, I'm trying to get other people's perspective/experiences on using GPL while working for a company. Upon employment I've signed an IP agreement that has the clause "Agrees [employee] that the copyright to any copyrightable material generated by the Employee during the course of employment shall be owned by the Company in accordance with established legal precedents in respect of "Works Made for Hire"." It appears I cannot work on GPL projects unless I get written exemption by employer (not likely) although I will try. Is anybody else in this type of agreement, do you know if you are? Am I misinterpreting and gnuradio work would not count under some precedent in "Works Made for Hire"? This is potentially a big problem for me since I create what I thought I could release under the FDL (free document license) on PlanetPhysics. [Disclaimer: Don't worry I'm not taking anyone's advise as legal council] Thanks. Ben ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] copyright
Ben Loftin wrote: Hi all, I'm trying to get other people's perspective/experiences on using GPL while working for a company. Upon employment I've signed an IP agreement that has the clause "Agrees [employee] that the copyright to any copyrightable material generated by the Employee during the course of employment shall be owned by the Company in accordance with established legal precedents in respect of "Works Made for Hire"." It appears I cannot work on GPL projects unless I get written exemption by employer (not likely) although I will try. Is anybody else in this type of agreement, do you know if you are? Am I misinterpreting and gnuradio work would not count under some precedent in "Works Made for Hire"? Technically, if you 'use' GPL'd items in your 'company's product, that may make the company liable for the GPL. Hence, some companies disallow their empolyees to use GPL'd software in company products. There's the BSD license, and Net/Free-BSD which does not have the GPL requirements of 'open source'... however, even there, packages acquired which go beyond the core BSD set, may get you into GPL country. (* There have been a number of companies in the linux kernel world which have not re-released their soruces, all the while using the GPL software for their company gain. I have never heard of any company being sued over this, and who would take up the suite... perhaps someone has, but I don't recall such.) Also, I believe, and this is where a lawyer may be needed, is that the 'work for hire' covers only what you do 'at work', 'on behalf, under the direction' of the employer, or for which equipment or services owned/paided for by the employer, were used by you. If you have your home PC using your own paid for DSL/Cable connection, etc, your own sofware, your own e-mail account, etc.etc.etc... Then it is yours. Real muddy areas are if what you do 'at work' matches very closely to what you do at home, such as signal processing implementations, the only difference being that at home you used FORTRAN and punch cards, whereas at work you used APL and a modern Cathode Ray Tube with fancy upper and lower case character keyboard... Less muddy is if you're a grocerystore clerk, and you develop yet-another-basic-interpreter-that-becomes-the-next-best-thing-since-sliced-bread... John Clark ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Boost Library
I am trying to install the Boost library and get the following error at the beginning skipping Boost.Python library build due to missing or incorrect configuration couldn't find Python.h in "/usr/local/include/python2.2" You can configure the location of your python installation by setting: PYTHON_ROOT- currently "/usr/local" PYTHON_VERSION - The 2-part python Major.Minor version number (e.g. "2.2", NOT "2.2.1") - currently "2.2" The following are automatically configured from PYTHON_ROOT if not otherwise set: PYTHON_LIB_PATH - path to Python library object; currently "/usr/local/lib/python2.2/config" PYTHON_INCLUDES- path to Python #include directories; currently "/usr/local/include/python2.2" - Yet the rest seems to compile after half an hour or so! Does this mean the installation has failed? I cannot seem to find the problem ..Python is installed in my machine and when I try the comman PYTHON_ROOT it does not recognise it? Excuse me but I am not a Unix expert! regards Tom ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] anything changed in usrp interface?
Hi - has anything changed in the usrp interface since what-the-hack ? I just updated to the latest cvs and suddenly all my radios are broken. Actually they work but frequencies go haywire in half the band: My rig sets the src to complex, decim 100, the ddc to -3.9e6 and mux to 0xf0f0f0f0, and then tunes a freq-xlating-fir-filter over +- 100khz to get 3.8 to 4.0Mhz. However things start going crazy over 3916khz. The software ddc is decimating to a bw of 32khz so that probably explains why the boundary is 16khz above the usrp ddc. It was working so well untill I did the update ;) if PLAY_FROM_USRP: src = usrp.source_c(0,usrp_decim) mux = gru.hexint(0xf0f0f0f0) src.set_pga(0,0) src.set_mux(mux) src.set_rx_freq(0,-usrp_center) tune_offset = -usrp_center - src.rx_freq(0) rf_LO_L = usrp_center - ( freq - tune_offset ) + 1.8e3 xlate_taps = gr.firdes.low_pass ( \ 1.0, rf_sample_rate, 20e3, 10e3, gr.firdes.WIN_HAMMING ) xlate_L = gr.freq_xlating_fir_filter_ccf ( \ fir_decimation, xlate_taps, rf_LO_L, rf_sample_rate ) If usrp_center is 3900e3, xlate_L is ok for freq < 3916e3 but is broken above that, stations at 3957k turn up around 3837 etc. --Chuck ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
RE: [Discuss-gnuradio] Boost Library
Sorry I got around that problem. WHich of these do I use... Invoke the build system, specifying the toolset(s) you wish to use, to build and install. For example for GNU/GCC. bjam "-sTOOLS=gcc" install Or if you are interested only in the built libraries you can have them built and collected to a common directory without installation. bjam "-sTOOLS=gcc" stage or do I need both? --- I got around the first problem by doing export PYTHON_ROOT= "/usr" regards Tom -Original Message- From: [EMAIL PROTECTED] on behalf of Moir, Tom Sent: Wed 8/10/2005 12:29 PM To: discuss-gnuradio@gnu.org Cc: Subject:[Discuss-gnuradio] Boost Library I am trying to install the Boost library and get the following error at the beginning skipping Boost.Python library build due to missing or incorrect configuration couldn't find Python.h in "/usr/local/include/python2.2" You can configure the location of your python installation by setting: PYTHON_ROOT- currently "/usr/local" PYTHON_VERSION - The 2-part python Major.Minor version number (e.g. "2.2", NOT "2.2.1") - currently "2.2" The following are automatically configured from PYTHON_ROOT if not otherwise set: PYTHON_LIB_PATH - path to Python library object; currently "/usr/local/lib/python2.2/config" PYTHON_INCLUDES- path to Python #include directories; currently "/usr/local/include/python2.2" - Yet the rest seems to compile after half an hour or so! Does this mean the installation has failed? I cannot seem to find the problem ..Python is installed in my machine and when I try the comman PYTHON_ROOT it does not recognise it? Excuse me but I am not a Unix expert! regards Tom ___ 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] anything changed in usrp interface?
On Tue, 9 Aug 2005, cswiger wrote: > Hi - has anything changed in the usrp interface since > what-the-hack ? I just updated to the latest cvs and > suddenly all my radios are broken. Actually they work > but frequencies go haywire in half the band: > Yeah, just verified with an older disk, the gnuradio-core/Makefile is dated June 20 - exact same python script works fine, just on the disk with the latest update things go crazy. I'll try to be more specific tomorrow. --Chuck ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] anything changed in usrp interface?
On Tue, Aug 09, 2005 at 09:59:17PM -0400, cswiger wrote: > Hi - has anything changed in the usrp interface since > what-the-hack ? I just updated to the latest cvs and > suddenly all my radios are broken. Actually they work > but frequencies go haywire in half the band: Shouldn't have, but we did renumber some FPGA registers a month or so ago. You might want to try using the latest .rbf file available at http://comsec.com/usrp/usrp_fpga_rev2_2005_07_30.rbf Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] Boost Library
On Wed, Aug 10, 2005 at 12:29:04PM +1200, Moir, Tom wrote: > I am trying to install the Boost library and get the following error at the > beginning > > skipping Boost.Python library build due to missing or incorrect configuration > > couldn't find Python.h in "/usr/local/include/python2.2" This is OK. We don't use Boost.Python. It's just reporting that it didn't build that optional part of the library. > Yet the rest seems to compile after half an hour or so! Does this > mean the installation has failed? I cannot seem to find the problem > ..Python is installed in my machine and when I try the comman > PYTHON_ROOT it does not recognise it? Excuse me but I am not a Unix > expert! As a side note, I was unable to compile boost 1.32 under OS/X on a machine with 768M of RAM. I gave up after a couple of hours. The first phase of g++ grew to 2.7 GB while compiling some XML serializer or some such.Boost 1.31 compiled OK, and took something on the order of 10 - 20 minutes. Haven't tried compiling 1.32 under x86 GNU/Linux. Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] copyright
On Tue, Aug 09, 2005 at 04:26:55PM -0600, Ben Loftin wrote: > Hi all, > > I'm trying to get other people's perspective/experiences on using GPL > while working for a company. Upon employment I've signed an IP > agreement that has the clause > >"Agrees [employee] that the copyright to any copyrightable material > generated by the Employee during the course of employment shall be owned > by the Company in accordance with established legal precedents in > respect of "Works Made for Hire"." IANAL... A lot of this stuff depends on the juristiction you live in. If you signed something that says the company owns everything you think or create while you work for them (including stuff done on your own time, on your own equipment), you might want to ask yourself why you agreed to those terms... [Contrary to what the HR people would have you believe, these things *are* negotiable. Sometimes just never getting around to signing that piece of paper works. "I'll have to run this by my lawyer, I'll get back to you on this."] With regard to contributing code to GNU Radio, we require a copyright assignment from the author to FSF, and if there appears to be any possibility that an employer might have an interest, then we require that the employer declaim or assign copyright to FSF. That said, this isn't the right forum for this thread. (Not sure where to point you.) Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Re: Noise while executing USRP examples
On Wed, Aug 10, 2005 at 10:34:32AM +0530, Arora_Amit wrote: > > 1) We are running the USRP examples on USRP board fsk_tx.py > and fsk_rx.py on one PC. During execution we are receiving too much of > noise, what might be the reason?.any solution? > > 2) Can we run both fsk_tx.py and fsk_rx.py simultaneously > on the same PC or do we need to run them on two different PC's ? > > 3) While running nbfm_ptt_quick_and_dirty.py we are > receiving lot of noise. Please provide some solution? Matt and I will be sorting out the Tx/Rx example sometime before we release 2.6. > 4) As suggested in the USRP document, we are using the > antenna with following specifications: An antenna tuned for 5 GHz is not going to work well for Tx and Rx taking place at 29 MHz... Eric ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Noise while executing USRP examples
Hi All, 1) We are running the USRP examples on USRP board fsk_tx.py and fsk_rx.py on one PC. During execution we are receiving too much of noise, what might be the reason?.any solution? 2) Can we run both fsk_tx.py and fsk_rx.py simultaneously on the same PC or do we need to run them on two different PC’s ? 3) While running nbfm_ptt_quick_and_dirty.py we are receiving lot of noise. Please provide some solution? 4) As suggested in the USRP document, we are using the antenna with following specifications: 1. Electrical Characteristics: Operating Frequency 2.4~2.5 & 4.9 & 5.15~5.35 & 5.725~5.85 GHz Antenna Type: Dipole Polarization Type : Linear Type of Radiation: Toroidal Peak Gain 2.0 dBi Typical For 2 G 4.0 dBi Typical For 5 G Impedance: 50 Ohm nominal V.S.W.R. 2.0:1 Max. 2. Mechanical Characteristics Swivel : 90 degrees Connector: SMA(M) Core: N/A Thanks and Regards, Amit Arora DISCLAIMER:This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated.. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
