Re: [Discuss-gnuradio] Still problems building gr 3.4.2 / Debian

[Ralph A. Schmid, dk5ras]

Hi,

Without gr-usrp everything builds and installs just fine - but when trying
to compile OpenBTS, I get the message "No package usrp found".

So I assume this one is needed...

Ralph.

> -Original Message-
> From: Tom Tsou [mailto:t...@tsou.cc]
> Sent: Friday, 02 August, 2013 22:39
> To: Ralph A. Schmid, dk5ras
> Cc: discuss-gnuradio@gnu.org
> Subject: Re: [Discuss-gnuradio] Still problems building gr 3.4.2 / Debian
> 
> On Fri, Aug 2, 2013 at 10:19 PM, Ralph A. Schmid, dk5ras

> wrote:
> > OK, pulled fresh copy frokm git, no errors with bootstrap, but still
> > this
> > one:
> >
> > /usr/bin/ld: usrp_rx_cfile.o: undefined reference to symbol
> > '_ZN5boost6system15system_categoryEv'
> > /usr/bin/ld: note: '_ZN5boost6system15system_categoryEv' is defined in
> > DSO
> > /usr/lib/libboost_system.so.1.53.0 so try adding it to the linker
> > command line
> > /usr/lib/libboost_system.so.1.53.0: could not read symbols: Invalid
> > operation
> > collect2: error: ld returned 1 exit status
> > make[5]: *** [usrp_rx_cfile] Error 1
> > make[5]: Leaving directory `/home/ras/gnuradio-3.4.2/gr-usrp/apps'
> > make[4]: *** [all] Error 2
> > make[4]: Leaving directory `/home/ras/gnuradio-3.4.2/gr-usrp/apps'
> > make[3]: *** [all-recursive] Error 1
> > make[3]: Leaving directory `/home/ras/gnuradio-3.4.2/gr-usrp'
> > make[2]: *** [all] Error 2
> > make[2]: Leaving directory `/home/ras/gnuradio-3.4.2/gr-usrp'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/home/ras/gnuradio-3.4.2'
> > make: *** [all] Error 2
> > ras@dk5ras:~/gnuradio-3.4.2$
> 
> If I'm not mistaken, that means the driver is built. Anyhow, the gr-usrp
> module isn't needed so you can add that to the disable list too
'--disable-gr-
> usrp'.
> 
> Or, since you *only* care about the usrp driver, just go into the 'usrp'
> subdirectory and run make and make install from there and ignore
> everything else.
> 
>  -TT


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Still problems building gr 3.4.2 / Debian

[Ralph A. Schmid, dk5ras]

Hi,

Without gr-usrp everything builds and installs just fine - but when trying
to compile OpenBTS, I get the message "No package usrp found".

So I assume this one is needed...

Ralph.

> -Original Message-
> From: Tom Tsou [mailto:t...@tsou.cc]
> Sent: Friday, 02 August, 2013 22:39
> To: Ralph A. Schmid, dk5ras
> Cc: discuss-gnuradio@gnu.org
> Subject: Re: [Discuss-gnuradio] Still problems building gr 3.4.2 / Debian
> 
> On Fri, Aug 2, 2013 at 10:19 PM, Ralph A. Schmid, dk5ras

> wrote:
> > OK, pulled fresh copy frokm git, no errors with bootstrap, but still
> > this
> > one:
> >
> > /usr/bin/ld: usrp_rx_cfile.o: undefined reference to symbol
> > '_ZN5boost6system15system_categoryEv'
> > /usr/bin/ld: note: '_ZN5boost6system15system_categoryEv' is defined in
> > DSO
> > /usr/lib/libboost_system.so.1.53.0 so try adding it to the linker
> > command line
> > /usr/lib/libboost_system.so.1.53.0: could not read symbols: Invalid
> > operation
> > collect2: error: ld returned 1 exit status
> > make[5]: *** [usrp_rx_cfile] Error 1
> > make[5]: Leaving directory `/home/ras/gnuradio-3.4.2/gr-usrp/apps'
> > make[4]: *** [all] Error 2
> > make[4]: Leaving directory `/home/ras/gnuradio-3.4.2/gr-usrp/apps'
> > make[3]: *** [all-recursive] Error 1
> > make[3]: Leaving directory `/home/ras/gnuradio-3.4.2/gr-usrp'
> > make[2]: *** [all] Error 2
> > make[2]: Leaving directory `/home/ras/gnuradio-3.4.2/gr-usrp'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/home/ras/gnuradio-3.4.2'
> > make: *** [all] Error 2
> > ras@dk5ras:~/gnuradio-3.4.2$
> 
> If I'm not mistaken, that means the driver is built. Anyhow, the gr-usrp
> module isn't needed so you can add that to the disable list too
'--disable-gr-
> usrp'.
> 
> Or, since you *only* care about the usrp driver, just go into the 'usrp'
> subdirectory and run make and make install from there and ignore
> everything else.
> 
>  -TT


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Still problems building gr 3.4.2 / Debian

[Ralph A. Schmid, dk5ras]

Hi,

Without gr-usrp everything builds and installs just fine - but when trying
to compile OpenBTS, I get the message "No package usrp found".

So I assume this one is needed...

Ralph.

> -Original Message-
> From: Tom Tsou [mailto:t...@tsou.cc]
> Sent: Friday, 02 August, 2013 22:39
> To: Ralph A. Schmid, dk5ras
> Cc: discuss-gnuradio@gnu.org
> Subject: Re: [Discuss-gnuradio] Still problems building gr 3.4.2 / Debian
> 
> On Fri, Aug 2, 2013 at 10:19 PM, Ralph A. Schmid, dk5ras

> wrote:
> > OK, pulled fresh copy frokm git, no errors with bootstrap, but still
> > this
> > one:
> >
> > /usr/bin/ld: usrp_rx_cfile.o: undefined reference to symbol
> > '_ZN5boost6system15system_categoryEv'
> > /usr/bin/ld: note: '_ZN5boost6system15system_categoryEv' is defined in
> > DSO
> > /usr/lib/libboost_system.so.1.53.0 so try adding it to the linker
> > command line
> > /usr/lib/libboost_system.so.1.53.0: could not read symbols: Invalid
> > operation
> > collect2: error: ld returned 1 exit status
> > make[5]: *** [usrp_rx_cfile] Error 1
> > make[5]: Leaving directory `/home/ras/gnuradio-3.4.2/gr-usrp/apps'
> > make[4]: *** [all] Error 2
> > make[4]: Leaving directory `/home/ras/gnuradio-3.4.2/gr-usrp/apps'
> > make[3]: *** [all-recursive] Error 1
> > make[3]: Leaving directory `/home/ras/gnuradio-3.4.2/gr-usrp'
> > make[2]: *** [all] Error 2
> > make[2]: Leaving directory `/home/ras/gnuradio-3.4.2/gr-usrp'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/home/ras/gnuradio-3.4.2'
> > make: *** [all] Error 2
> > ras@dk5ras:~/gnuradio-3.4.2$
> 
> If I'm not mistaken, that means the driver is built. Anyhow, the gr-usrp
> module isn't needed so you can add that to the disable list too
'--disable-gr-
> usrp'.
> 
> Or, since you *only* care about the usrp driver, just go into the 'usrp'
> subdirectory and run make and make install from there and ignore
> everything else.
> 
>  -TT


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Still problems building gr 3.4.2 / Debian

[Tom Tsou]

On Aug 3, 2013 9:18 AM, "Ralph A. Schmid, dk5ras"  wrote:
> Without gr-usrp everything builds and installs just fine - but when trying
> to compile OpenBTS, I get the message "No package usrp found".
>
> So I assume this one is needed...

It's not.

What are the contents of the following directories?

/usr/local/lib/pkgconfig
/usr/local/lib64/pkgconfig

  -TT
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Still problems building gr 3.4.2 / Debian

[Ralph A. Schmid, dk5ras]

In the lib filder only stuff of latest build, in the lib64 the 342 stuff...

Ralph.

Tom Tsou  wrote:

>On Aug 3, 2013 9:18 AM, "Ralph A. Schmid, dk5ras"  wrote:
>> Without gr-usrp everything builds and installs just fine - but when trying
>> to compile OpenBTS, I get the message "No package usrp found".
>>
>> So I assume this one is needed...
>
>It's not.
>
>What are the contents of the following directories?
>
>/usr/local/lib/pkgconfig
>/usr/local/lib64/pkgconfig
>
>  -TT
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Still problems building gr 3.4.2 / Debian

[Tom Tsou]

On Aug 3, 2013 11:39 AM, "Ralph A. Schmid, dk5ras"  wrote:
>
> In the lib filder only stuff of latest build, in the lib64 the 342
stuff...

You need to be more specific. Does the file 'ursp.pc' exist in the
pkgconfig directory or does it not?

  -TT
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Pybombs install gnuradio failing on gr-fcd.

[Alexandru Csete]

On Sat, Aug 3, 2013 at 8:52 AM, Andrew Back  wrote:
> Hello,
>
> I'm trying to install GNU Radio using pybombs on a Debian 6.0/amd64
> system and it gets as far as:
>
> [ 93%] Building CXX object 
> gr-atsc/lib/CMakeFiles/test_atsci.dir/test_atsci.cc.o
> Linking CXX executable test_atsci
> [ 93%] Built target test_atsci
> make: *** [all] Error 2
> bash return val = 2
> Traceback (most recent call last):
>
> If I then run make -j4 from src/gnuradio/build I get:
>
> [ 87%] Built target gnuradio-atsc
> ../../lib/libgnuradio-fcd-3.7.1git.so.0.0.0: undefined reference to
> `libusb_handle_events_completed'
> collect2: ld returned 1 exit status
> make[2]: *** [gr-fcd/examples/c++/fcd_nfm_rx] Error 1
> make[1]: *** [gr-fcd/examples/c++/CMakeFiles/fcd_nfm_rx.dir/all] Error 2
> make[1]: *** Waiting for unfinished jobs
> [ 88%] Built target test_atsci
> [ 88%] Built target _qtgui_swig
> [ 93%] Built target gnuradio-digital
> make: *** [all] Error 2
>
> So I tried setting -DENABLE_GR_FCD=OFF in the recipe and running
> pybombs install again, but it still fails at the same point, so I
> guess it's not being reconfigured. How would I do this? Alternatively,
> any idea what I should do to get gr-fcd to build? libusb-1.0-0-dev is
> installed.

There is a rebuild option:
./pybombs rb gnuradio
but I don't know if it will clean the cache and everything.

You can also just run:
./pybombs uninstall gnuradio
and maybe also
./pybombs clean gnuradio
to start from fresh

Alex

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Still problems building gr 3.4.2 / Debian

[Ralph A. Schmid, dk5ras]

I will check later, am on a train now :)

Ralph.

Tom Tsou  wrote:

>On Aug 3, 2013 11:39 AM, "Ralph A. Schmid, dk5ras"  wrote:
>>
>> In the lib filder only stuff of latest build, in the lib64 the 342
>stuff...
>
>You need to be more specific. Does the file 'ursp.pc' exist in the
>pkgconfig directory or does it not?
>
>  -TT
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] channel estimation

[Martin Braun (CEL)]

Hi Eslam,

On Fri, Aug 02, 2013 at 04:55:04PM +0200, Eslam Ahmed wrote:
> I have been working on channel estimation in ofdm. I used the ofdm mod and 
> ofdm
> demod blocks in gnuradio. I edited the ofdm frame acquistion block to print 
> the

I'm assuming you're using the old blocks? Have you tried the new stuff?

> equalizer taps. but the problem is that i only connected ofdm mod and demod
> together without channel model, and equalizer give me incorrect channel rather
> than one. Any suggestion with this problem?

Your "problem" is not clear from this email.
Please read
http://gnuradio.org/redmine/projects/gnuradio/wiki/ReportingErrors
before re-posting.

Also, http://gnuradio.org/doc/doxygen/page_ofdm.html might help.

Cheers,
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


pgpb9PeY62bnD.pgp
Description: PGP signature
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Still problems building gr 3.4.2 / Debian

[Ralph A. Schmid]

Hi

> You need to be more specific. Does the file 'ursp.pc' exist in the
> pkgconfig directory or does it not?

Here the non-64-bit-contents:

gnuradio-analog.pc
gnuradio-atsc.pc
gnuradio-audio.pc
gnuradio-blocks.pc
gnuradio-channels.pc
gnuradio-comedi.pc
gnuradio-digital.pc
gnuradio-fcd.pc
gnuradio-fec.pc
gnuradio-fft.pc
gnuradio-filter.pc
gnuradio-noaa.pc
gnuradio-pager.pc
gnuradio-qtgui.pc
gnuradio-runtime.pc
gnuradio-trellis.pc
gnuradio-uhd.pc
gnuradio-video-sdl.pc
gnuradio-vocoder.pc
gnuradio-wavelet.pc
gr-wxgui.pc
uhd.pc
volk.pc
yate.pc

And here the 64-bit-folder:

gnuradio-core.pc
gruel.pc
usrp.pc

Here the content of usrp.pc:

prefix=/usr/local
exec_prefix=${prefix}
libdir=${exec_prefix}/lib64
includedir=${prefix}/include

Name: usrp
Description: USRP Client Side C++ interface
Requires: libusb
Version: 3.4.2
Libs: -L${libdir} -lusrp
Cflags: -I${includedir}


With best regards

Ralph.






___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Still problems building gr 3.4.2 / Debian

[Tom Tsou]

On Sat, Aug 3, 2013 at 6:55 PM, Ralph A. Schmid  wrote:
> And here the 64-bit-folder:
>
> gnuradio-core.pc
> gruel.pc
> usrp.pc

The gnuradio-libusrp install is fine. You just need to specifiy the
PKG_CONFIG_PATH before running configure with OpenBTS.

'export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig'

  -TT

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Simple WBFM Transmitter - How to configure the USRP1 block to transmit ?

[Tom Rondeau]

On Fri, Aug 2, 2013 at 7:10 AM, Bruno Cardoso  wrote:
> Hi Tom,
>
> I did the modifications and now I have the  WBFM_transmitter_Bruno3.grc
> 
> It's working. Thank you a lot. I could do an FM broadcast for the first time
> from one USRP1 to another USRP1.
>
> But I have too much noise and I couldn't listen to it so clear. Could you
> listen to it clear ?
>
> Another thing curious was I could listen to the sound with another USRP1 but
> I couldn't listen with a normal FM receiver (for instance, a normal FM
> radio). What's the diference between the USRP1 and normal FM receiver?
>
> Thanks a lot!!
>
> Bruno

Bruno,

There's a lot that can happen and a ton of differences between a USRP
and a standard FM receiver. You're just going to have to play around
with filters, amplitudes, gains, and frequency settings to figure it
out.

-- 
Tom
Visit us at GRCon13 Oct. 1 - 4
http://www.trondeau.com/grcon13

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] BER Curve of DQPSK Demodulator

[Tom Rondeau]

On Thu, Aug 1, 2013 at 11:08 AM, Abid Ullah  wrote:
> Hi
>I am using the GNU Radio DQPSK Modulator and Demodulator for low rate
> data transfer. I know that GNU Radio blocks are already tested. So is there
> any BER curve available for the DQPSK Mod/Demod.
>
> Did any one characterized the BER curve of this block.
>
>
> Regards
>
> Abid
>
> Graduate Student
> Virginia Tech

Abid,

My PhD dissertation (from VT) or my book (Artificial Intelligence in
Wireless Communications) has BER curves in appendix A for various GNU
Radio demodulators.

-- 
Tom
Visit us at GRCon13 Oct. 1 - 4
http://www.trondeau.com/grcon13

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Build problems on mac os 10.8

[Tom Rondeau]

On Fri, Aug 2, 2013 at 12:57 PM, Ching  wrote:
> Hi,
>
> I try to build gnuradio on mac os 10.8 using macports. But failed to build
> "py27-wxpython-devel".
>
> Here is the detail the log:
>
> cports.org/release/tarballs/ports/x11/xorg-libpthread-stubs
> :debug:main OS darwin/12.4.0 (Mac OS X 10.8) arch i386
>   N   RO main.log   unix │ utf-8 │ no ft   22%  LN 415 C
> 54
>
> :info:build Exit code: 1
> :error:build org.macports.build for port py27-wxpython-devel returned:
> command execution failed
> :debug:build Error code: CHILDSTATUS 30849 1
> :debug:build Backtrace: command execution failed
> while executing
> "system -nice 0 $fullcmdstring"
> ("eval" body line 1)
> invoked from within
> "eval system $notty $nice \$fullcmdstring"
> invoked from within
> "command_exec build"
> (procedure "portbuild::build_main" line 8)
> invoked from within
> "$procedure $targetname"
> :info:build Warning: targets not executed for py27-wxpython-devel:
> org.macports.activate org.macports.build org.macports.destroot
> org.macports.install
> :notice:build Please see the log file for port py27-wxpython-devel for
> details:
>
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py27-wxpython-devel/py27-wxpython-devel/main.log
>
>
> Anyone know how to resolve this build problem? Thanks.
>
> Best regards,
> Cheng Chi


Unfortunately, our OSX guru Michael Dickens is on vacation right now,
and I'm not able to help with OSX issues too much. I know Dickens has
posted a lot of his work on this mailing list for how to use Mac ports
to install GNU Radio. Have you been following his instructions?

-- 
Tom
Visit us at GRCon13 Oct. 1 - 4
http://www.trondeau.com/grcon13

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Spectrogram plot on ControlPort

[Tom Rondeau]

On Thu, Aug 1, 2013 at 4:02 PM, Nowlan, Sean
 wrote:
> Does anybody know how to get gr-ctrlport-monitor to do spectrogram plots? I
> set up a ctrlport_probe2_c block with the DISPSPEC DisplayType but all I see
> are Time, PSD, and Constellation plot options in gr-ctrlport-monitor.
>
>
> Thanks,
>
> Sean

I hadn't actually enabled the spectrogram plots through our
ControlPort monitor app. It's due to the way the data is handled that
makes it a slight pain to set up. It's not impossible, but I just
hadn't spent the time to do it. You can look in
gnuradio-runtime/python/gnuradio/ctrlport/GrDataPlotter.py and see
what you can do about adding it in.

I'll likely get to it at some point, but not for the next few weeks at least.

-- 
Tom
Visit us at GRCon13 Oct. 1 - 4
http://www.trondeau.com/grcon13

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Problem compiling gnuradio 3.7.0 on CentOS 6.2

[Tom Rondeau]

On Thu, Aug 1, 2013 at 10:12 AM, Robert Lucas  wrote:
> My system:
> CentOS 6.2, x86_64
> Python 2.6.6
> Cmake version 2.6-patch 4
> gnuradio 3.7.0
>
> I created a "build" folder in the gnuradio soure directory and attempted to 
> compile using "cmake ../".  The error I keep getting is this:
>
> START 
> LOG-
> -- Build type not specified: defaulting to release.
> -- NO PERF COUNTERS
> -- Minimum SWIG version required is 1.3.31
> --
> -- The build system will automatically enable all components.
> -- Use -DENABLE_DEFAULT=OFF to disable components by default.
> --
> -- Configuring python-support support...
> --   Dependency PYTHONLIBS_FOUND = TRUE
> --   Dependency SWIG_FOUND = 1
> --   Dependency SWIG_VERSION_CHECK = TRUE
> --   Enabling python-support support.
> --   Override with -DENABLE_PYTHON=ON/OFF
> --
> -- Configuring testing-support support...
> --   Dependency CPPUNIT_FOUND = TRUE
> --   Enabling testing-support support.
> --   Override with -DENABLE_TESTING=ON/OFF
> --
> -- Configuring volk support...
> --   Enabling volk support.
> --   Override with -DENABLE_VOLK=ON/OFF
>   File "", line 1
>
>
> ^
> SyntaxError: invalid syntax
> CMake Error at volk/cmake/GrPython.cmake:105 (file):
>   file FILE(SYSTEM_PATH ENV result) must be called with only three arguments.
> Call Stack (most recent call first):
>   volk/CMakeLists.txt:53 (include)
>
>
> --
> -- Python checking for python >= 2.5
>   File "", line 1
>
>
> ^
> SyntaxError: invalid syntax
> -- Python checking for python >= 2.5 - not found
> --
> ---END 
> LOG-
>
> It seems as if cmake is inserting a "CR" character at the beginning of each 
> string that is passed to python.
>
> I found that I was able to resolve the problem by editing 
> volk/cmake/GrPython.cmake to put all the python code on one line as follows:
>
> --ORIGINAL CODE--
> 
> # Sets the python installation directory GR_PYTHON_DIR
> 
> execute_process(COMMAND ${PYTHON_EXECUTABLE} -c "
> from distutils import sysconfig
> print sysconfig.get_python_lib(plat_specific=True, prefix='')
> " OUTPUT_VARIABLE GR_PYTHON_DIR OUTPUT_STRIP_TRAILING_WHITESPACE
> )
> file(TO_CMAKE_PATH ${GR_PYTHON_DIR} GR_PYTHON_DIR)
>
> EDITED CODE--
> 
> # Sets the python installation directory GR_PYTHON_DIR
> 
> execute_process(COMMAND ${PYTHON_EXECUTABLE} -c "from distutils import 
> sysconfig; print sysconfig.get_python_lib(plat_specific=True, prefix='');" 
> OUTPUT_VARIABLE GR_PYTHON_DIR OUTPUT_STRIP_TRAILING_WHITESPACE
> )
> file(TO_CMAKE_PATH ${GR_PYTHON_DIR} GR_PYTHON_DIR)
>
> --END 
> CODE---
>
> Note that trying to put "from distutils import sysconfig" on the same line as 
> the open quotemark does not resolve the problem either (it also seems to 
> append a CR to the end of the line and python barks at me).
>
> However, this process is very tedious, and it seems like there should be a 
> better way of fixing it, and it does not work for the sections of python code 
> in the cmake files where there are if/else blocks.  Is there a better way of 
> resolving this problem, or has anyone else had this problem?



Robert,
Give PyBOMBS a shot (gnuradio.org/pybombs). CentOS ships with packages
that are too old for building GNU Radio out of the box, but PyBOMBS
should install them all as necessary. I was able to use it to build
GNU Radio on a CentOS 5.(something) a while ago.

-- 
Tom
Visit us at GRCon13 Oct. 1 - 4
http://www.trondeau.com/grcon13

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] A new SDR on Kickstarter

[Michael Ossmann]

The maximum output power varies by frequency.  See:

https://github.com/mossmann/hackrf/wiki/Jawbreaker#transmit-power


On Fri, Aug 02, 2013 at 08:06:49AM +0200, Ralph A. Schmid, dk5ras wrote:
>
> Do not expect more than a few mW, but MMICs are cheaply available, no
> problem to boost it a bit :)
> 
>  
> 
> Ralph.
> 
>  
> 
>  
> 
> From: nyxxena...@gmail.com [mailto:nyxxena...@gmail.com] On Behalf Of James
> Hall
> Sent: Thursday, August 01, 2013 5:35 PM
> To: Ralph A. Schmid, dk5ras
> Subject: Re: [Discuss-gnuradio] A new SDR on Kickstarter
> 
>  
> 
> I'm wondering what the power output is on this? I haven't seen it anywhere.
> I wouldn't imagine it's very much. 100mw?
> 
> On Thu, Aug 1, 2013 at 4:53 AM, Ralph A. Schmid, dk5ras 
> wrote:
> 
> I love the 6 GHz capability, but I really miss full duplex, this locks out
> stuff like OpenBTS or the open source LTE system everyone is hoping for :)
> For the moment I will go with the BladeRF, also a small design, nice for
> travel. Still I am tempted to order a hackrf :)
> 
> Ralph.
> 
> 
> 
> > -Original Message-
> > From: discuss-gnuradio-bounces+ralph=schmid@gnu.org
> > [mailto:discuss-gnuradio-bounces+ralph
>  =schmid@gnu.org] On Behalf Of
> > Michael Ossmann
> > Sent: Wednesday, July 31, 2013 11:36 PM
> > To: Farhad Abdolian
> > Cc: discuss-gnuradio@gnu.org
> > Subject: Re: [Discuss-gnuradio] A new SDR on Kickstarter
> >
> > Thanks, Farhad.  I designed HackRF for 20 MHz with 8 bit quadrature
> samples
> > because it is at the maximum rate that can be transferred over USB 2.0
> (Hi-
> > Speed).  It's enough bandwidth for most SDR applications I've seen.  What
> > applications do you have in mind?
> >
> >
> > On Wed, Jul 31, 2013 at 10:32:07PM +0200, Farhad Abdolian wrote:
> > >
> > > Hi Guys,
> > > Just saw this project on Kickstarter.
> > > http://www.kickstarter.com/projects/mossmann/hackrf-an-open-source-
> > sdr
> > > -platform
> > >
> > > It is an interesting low cost SDR with 20MHz bandwidth.
> > >
> > > It seems like SDR is becoming more popular every day and the number of
> > > low cost SDR devices are on the rise.
> > >
> > > I am thinking about backing it up, but I am not sure of 20MHz is
> > > enough for the applications I have in mind.
> > >
> > > What do you think?
> > >
> > > BR,
> > > Farhad
> >
> > > ___
> > > Discuss-gnuradio mailing list
> > > Discuss-gnuradio@gnu.org
> > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> >
> >
> > ___
> > Discuss-gnuradio mailing list
> > Discuss-gnuradio@gnu.org
> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
> 
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 
>  
> 

> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] QPSK in benchmark

[yeran]

Hi everyone,
I'm using gnu radio benchmark to do experiment. I want to test under different 
modulation, BPSK, DBPSK, DQPSK all works well, but there seems to be some 
problem in QPSK. I also asked some lab mates, they also face this problem. 
Anyone come across this problem, how did you deal with it?
Thanks in advance!
Ada   ___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Build problems on mac os 10.8

[Ian Buckley]

First step, follow the instructions in the error message, in my experience 
there's lots of useful information in the log file:

On Aug 3, 2013, at 9:16 AM, Tom Rondeau  wrote:

>> Please see the log file for port py27-wxpython-devel for
>> details:
>> 
>> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py27-wxpython-devel/py27-wxpython-devel/main.log

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] ATSC Magic coupling constant

[Andrew Davis]

Hello All,

Just an update for those following along, I have ( somewhat ) finished the
ATSC transmitter, most of the blocks needed were all ready made, but they
stopped right before pilot insertion and VSB modulation ( my guess is since
the hardware back then was receive only they stopped there ), so I added
the needed blocks, and transmitted with my USRP1 to a television. It is
much faster than real time and so i'm trying to encode and transmit my
webcam live but i'm still working on getting gstreamer to output the
correct stream :)

Also the receiver is coming along but i'm still stuck with the magic
constant. I have a nice sample data recording from my USRP of my local TV
station, it is just above the threshold for decent recovery and so should
be good for testing improvements the the receiver. Would anyone like this
sample for testing?

Thank you all
Andrew


On Wed, Jul 31, 2013 at 5:00 PM, Andrew Davis wrote:

> Ok, I tried the off by sqrt(2) and it put me close but now the bit_timing
> _loop is running short on data again, which as a disseminator means it
> probably cant find a good sync for timing and just eats all its input
> samples. So I pushed my changes to where i'm at now to github, could you
> see if that compiles for you, then I could walk you though whats all going
> on with this and where i'm at.
>
> Thank you
> Andrew
>
>
> On Tue, Jul 30, 2013 at 8:12 PM, Johnathan Corgan <
> johnat...@corganlabs.com> wrote:
>
>> On 07/30/2013 04:28 PM, Andrew Davis wrote:
>>
>> > Thanks for the idea, I will try it tomorrow when I get back to the test
>> > machine ( which is powerful enough to be within reach of real-time
>> > decoding if I get this figured out :)
>>
>> If you don't get this straightened out, I'd be happy to work with you by
>> phone or chat.
>>
>> --
>> Johnathan Corgan, Corgan Labs
>> SDR Training and Development Services
>> http://corganlabs.com
>> Visit us at GRCON13 Oct. 1-4 http://ow.ly/ntmpL
>>
>>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] PMT blobs in Python

[Peter Horvath]

Hi,

can I convert a blob created by my C++ code (unsigned chars) to a Python
list or NumPy array?

pmt.blob_data() returns a 'SwigPyObject' with which I can't do anything.
Passing it to a NumPy array constructor doesn't seem to do the job.

The blobs are in a tuple:
pmt::pmt_t b1 = pmt::make_blob(a, a_length);
pmt::pmt_t b2 = pmt::make_blob(b, b_length);
return pmt::make_tuple(b1, b2);

And I try to check the contents of b1 in QA code like this:
res = my_test_function()
b1 = pmt.blob_data(pmt.tuple_ref(res, 0))
b1_len = pmt.blob_length(pmt.tuple_ref(res, 0))

Thanks,
Peter

___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] A new SDR on Kickstarter

[Vanush Vaswani]

When can you ship to Australia?
We are interested in purchasing for university SATCOM project.

Regards,
Vanush

On Sun, Aug 4, 2013 at 4:57 AM, Michael Ossmann  wrote:

> The maximum output power varies by frequency.  See:
>
> https://github.com/mossmann/hackrf/wiki/Jawbreaker#transmit-power
>
>
> On Fri, Aug 02, 2013 at 08:06:49AM +0200, Ralph A. Schmid, dk5ras wrote:
> >
> > Do not expect more than a few mW, but MMICs are cheaply available, no
> > problem to boost it a bit :)
> >
> >
> >
> > Ralph.
> >
> >
> >
> >
> >
> > From: nyxxena...@gmail.com [mailto:nyxxena...@gmail.com] On Behalf Of
> James
> > Hall
> > Sent: Thursday, August 01, 2013 5:35 PM
> > To: Ralph A. Schmid, dk5ras
> > Subject: Re: [Discuss-gnuradio] A new SDR on Kickstarter
> >
> >
> >
> > I'm wondering what the power output is on this? I haven't seen it
> anywhere.
> > I wouldn't imagine it's very much. 100mw?
> >
> > On Thu, Aug 1, 2013 at 4:53 AM, Ralph A. Schmid, dk5ras  >
> > wrote:
> >
> > I love the 6 GHz capability, but I really miss full duplex, this locks
> out
> > stuff like OpenBTS or the open source LTE system everyone is hoping for
> :)
> > For the moment I will go with the BladeRF, also a small design, nice for
> > travel. Still I am tempted to order a hackrf :)
> >
> > Ralph.
> >
> >
> >
> > > -Original Message-
> > > From: discuss-gnuradio-bounces+ralph=schmid@gnu.org
> > > [mailto:discuss-gnuradio-bounces+ralph
> >  =schmid@gnu.org] On
> Behalf Of
> > > Michael Ossmann
> > > Sent: Wednesday, July 31, 2013 11:36 PM
> > > To: Farhad Abdolian
> > > Cc: discuss-gnuradio@gnu.org
> > > Subject: Re: [Discuss-gnuradio] A new SDR on Kickstarter
> > >
> > > Thanks, Farhad.  I designed HackRF for 20 MHz with 8 bit quadrature
> > samples
> > > because it is at the maximum rate that can be transferred over USB 2.0
> > (Hi-
> > > Speed).  It's enough bandwidth for most SDR applications I've seen.
>  What
> > > applications do you have in mind?
> > >
> > >
> > > On Wed, Jul 31, 2013 at 10:32:07PM +0200, Farhad Abdolian wrote:
> > > >
> > > > Hi Guys,
> > > > Just saw this project on Kickstarter.
> > > > http://www.kickstarter.com/projects/mossmann/hackrf-an-open-source-
> > > sdr
> > > > -platform
> > > >
> > > > It is an interesting low cost SDR with 20MHz bandwidth.
> > > >
> > > > It seems like SDR is becoming more popular every day and the number
> of
> > > > low cost SDR devices are on the rise.
> > > >
> > > > I am thinking about backing it up, but I am not sure of 20MHz is
> > > > enough for the applications I have in mind.
> > > >
> > > > What do you think?
> > > >
> > > > BR,
> > > > Farhad
> > >
> > > > ___
> > > > Discuss-gnuradio mailing list
> > > > Discuss-gnuradio@gnu.org
> > > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> > >
> > >
> > > ___
> > > Discuss-gnuradio mailing list
> > > Discuss-gnuradio@gnu.org
> > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> >
> >
> > ___
> > Discuss-gnuradio mailing list
> > Discuss-gnuradio@gnu.org
> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> >
> >
> >
>
> > ___
> > Discuss-gnuradio mailing list
> > Discuss-gnuradio@gnu.org
> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Still problems building gr 3.4.2 / Debian

[Ralph A. Schmid, dk5ras]

Hi,

> The gnuradio-libusrp install is fine. You just need to specifiy the
> PKG_CONFIG_PATH before running configure with OpenBTS.
> 
> 'export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig'

That made it! Yeah! Then still some standard.ihx file was missing, I do not
remember how it came in its place when I did the other installation, but
copying it from the other machine did the trick.

How should one be able to find this out without deepest knowledge?! Thank
you very much!

Now I have to get OpenBTS interoperate with yate, but this is another topic,
the phones see the BTS, can log in, everything else should be easy to find
out.
 
>   -TT

Ralph.




___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Still problems building gr 3.4.2 / Debian

[Ralph A. Schmid, dk5ras]

Hi,

> The gnuradio-libusrp install is fine. You just need to specifiy the
> PKG_CONFIG_PATH before running configure with OpenBTS.
> 
> 'export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig'

That made it! Yeah! Then still some standard.ihx file was missing, I do not
remember how it came in its place when I did the other installation, but
copying it from the other machine did the trick.

How should one be able to find this out without deepest knowledge?! Thank
you very much!

Now I have to get OpenBTS interoperate with yate, but this is another topic,
the phones see the BTS, can log in, everything else should be easy to find
out.
 
>   -TT

Ralph.




___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Still problems building gr 3.4.2 / Debian

[Ralph A. Schmid, dk5ras]

Hi,

> The gnuradio-libusrp install is fine. You just need to specifiy the
> PKG_CONFIG_PATH before running configure with OpenBTS.
> 
> 'export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig'

That made it! Yeah! Then still some standard.ihx file was missing, I do not
remember how it came in its place when I did the other installation, but
copying it from the other machine did the trick.

How should one be able to find this out without deepest knowledge?! Thank
you very much!

Now I have to get OpenBTS interoperate with yate, but this is another topic,
the phones see the BTS, can log in, everything else should be easy to find
out.
 
>   -TT

Ralph.




___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio