discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Discuss-gnuradio Digest, Vol 183, Issue 29


From: Rick Spanbauer
Subject: Re: [Discuss-gnuradio] Discuss-gnuradio Digest, Vol 183, Issue 29
Date: Sun, 3 Jun 2018 12:23:35 -0400

K

On Wed, Jan 31, 2018, 12:02 PM <address@hidden> wrote:
Send Discuss-gnuradio mailing list submissions to
        address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
or, via email, send a message with subject or body 'help' to
        address@hidden

You can reach the person managing the list at
        address@hidden

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Discuss-gnuradio digest..."


Today's Topics:

   1. Re: How to extract part of a vector in GNURadio Companion?
      (M?ller)
   2. 802.15 Zigbee transceiver (Zhiwu Guo)
   3. Software Design Engineer Opening at DeepSig (Ben Hilburn)
   4. Re: Import Error running companion after upgrade to Fedora 27
      (Mike Gilmer)
   5. Re: Import Error running companion after upgrade to Fedora 27
      (M?ller)
   6. gr-bluetooth installation issue (Suman Bhunia)
   7. Re: 802.15 Zigbee transceiver (Bastian Bloessl)
   8. Re: gnu radio installation on Mac via MacPorts (Vipin Sharma)
   9. Re: gr-bluetooth installation issue (Cinaed Simson)
  10. Re: gnu radio installation on Mac via MacPorts (Vipin Sharma)
  11. How to use IQ Bal Optimize/Fix? (kokosz)
  12. Re: How to use IQ Bal Optimize/Fix? (Jeff Long)
  13. Re: gnu radio installation on Mac via MacPorts (Michael Dickens)
  14. Re:  How to use IQ Bal Optimize/Fix? (kokosz)
  15. Re: How to use IQ Bal Optimize/Fix? (Jeff Long)


----------------------------------------------------------------------

Message: 1
Date: Tue, 30 Jan 2018 17:15:28 +0000
From: M?ller, Marcus (CEL) <address@hidden>
To: "address@hidden" <address@hidden>,
        "address@hidden" <address@hidden>
Subject: Re: [Discuss-gnuradio] How to extract part of a vector in
        GNURadio Companion?
Message-ID: <address@hidden>
Content-Type: text/plain; charset="utf-8"

Hi Kokosz, Hi Jeff!

I really like Jeff's approach, as it's very "GNU Radio stylish"!

Another flexible way of doing this would be to simply write a  python
block ? and that's super easy if you just use the "Python Block" in
GRC; you just set the "in_sig" in the file that opens when you click on
"Open in Editor" to something like [(np.complex,1024)], and the out_sig
to something that makes sense to your application, like [np.float32] if
you just want to output one mean power value per input vector, or
[(np.float32, 100)] when you want to produce one output vector of 100
real values per input vector.

Then, you write your "math" in the work method below; notice that you
need to write to the *elements* of the first output, so
"output_items[0][:]" is the right thing to assign to.

I'm including a simple "give me the mean of element 113 through 250"
block below.

Best regards,
Marcus

class blk(gr.sync_block):
    def __init__(self, scale = 1.0):  # only default arguments here
        gr.sync_block.__init__(
            self,
            name='Vector partial mean',
            in_sig=[(np.complex64, 1024)],
            out_sig=[np.complex64]
        )
        self.scale = scale

    def work(self, input_items, output_items):
        output_items[0][0] = input_items[0][0][112:250].mean() *
self.scale
        return 1 #we've produced exactly one item of output,so return 1


On Tue, 2018-01-30 at 11:23 -0500, Jeff Long wrote:
> Reading this again, you're probably looking to continuously extract a
> slice from a vector type, not a vector sink as I first read it.
>
> Ah, there is an efficient way. Convert vector-to-stream, use keep-m-in-n
> with an offset, and convert back to a vector. Hope that works.
>
>
> On 01/30/2018 11:06 AM, Jeff Long wrote:
> > Flowgraphs aren't procedural, so you can't say "run, then extract". But
> > you can build a flowgraph in GRC, import/run it from a small Python
> > program, and then extract a slice of the vector.
> >
> > On 01/30/2018 10:44 AM, kokosz wrote:
> > > Dear all,
> > >
> > > Is there any way to extract just some part of a vector in GNURadio
> > > Companion for further processing?
> > >
> > > For example, FFT block returns a vector of, say, 1024 complex points
> > > in frequency domain, but I want to extract just some of them (e.g.
> > > points no. 113-250) and then process them (e.g. convert to stream and
> > > calculate their average value etc).
> > >
> > >
> > > _______________________________________________
> > > Discuss-gnuradio mailing list
> > > address@hidden
> > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> > >
>
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6582 bytes
Desc: not available
URL: <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20180130/8e4b4483/attachment.bin>

------------------------------

Message: 2
Date: Tue, 30 Jan 2018 12:04:38 -0700
From: Zhiwu Guo <address@hidden>
To: address@hidden
Subject: [Discuss-gnuradio] 802.15 Zigbee transceiver
Message-ID:
        <CA+A5_F0gx16==FMZ+iLRLLVw_swvA5wMLQ=address@hidden>
Content-Type: text/plain; charset="utf-8"

Dear all,

I am working on the gnuradio project of 802.15 Zigbee transceiver which I
downloaded from link below:

https://github.com/bastibl/gr-ieee802-15-4

I am looking the mac.cc file which is located in the lib files. As we all
know know, there are two types of MAC mechanism in 802.15, one is the CSMA
based, another one is TDMA based. I am wondering which mechanism is this
mac.cc written for? I could not find any hints on this file. Thank you.

Best regards.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20180130/ae57a5dc/attachment.html>

------------------------------

Message: 3
Date: Tue, 30 Jan 2018 15:29:28 -0500
From: Ben Hilburn <address@hidden>
To: GNU Radio Mailing List <address@hidden>
Subject: [Discuss-gnuradio] Software Design Engineer Opening at
        DeepSig
Message-ID:
        <CA+F3bHisw+vUv=address@hidden>
Content-Type: text/plain; charset="utf-8"

Hi all!

I'm sending this e-mail wearing a different hat than I normally do when
sending messages to the list.

We are hiring at DeepSig, and we're (obviously) very interested in people
with GNU Radio experience. If you're in the market for a software
engineering position, check out the below description and get in touch!

Cheers,
Ben

------------
/*
 * Job Posting: Software Design Engineer
 *
 * Keywords: C/C++, Python, Linux, Embedded, Open-Source, Software Radio,
Machine Learning
 * Type: Full-Time (W2) On-Site
 * Location: Arlington, VA
 */

/*
 * About the Position
 */
DeepSig Inc. is looking for a full-time software developer to join our R&D
team in Arlington, Virginia, for an immediate opening. The primary
responsibility of this position is contributing to the design and
implementation of DeepSig?s software products, which are principally
written with C/C++ and Python using common Linux-based open-source tools &
workflows. Important aspects of this role include writing clean &
maintainable code, designing user-friendly interfaces, creating great
documentation, and architecting a robust & re-usable software
infrastructure. Our products commonly interface with software-defined radio
hardware and are built around our machine learning algorithms, so
experience (or an interest) in working close to hardware, embedded systems,
and/or with machine learning is valuable.

Previous experience working with open-source projects & communities is a
big plus. Candidates should be able to communicate clearly, both internal
and external to the company, be self-driven, and know when to ask for help!
We hire engineers that empathize with the users of their code, develop good
relationships with customers, and love to learn.

Travel expectations are light, mostly consisting of conferences and
occasional customer visits. Candidates must be authorized to work in the
United States by US citizenship or permanent residency. This position is
located on-site with our engineering team in Arlington, Virginia. We are
not currently able to sponsor visa applications or support remote hires.

/*
 * Engineering at DeepSig
 */
DeepSig is growing its technical team while cultivating a collaborative,
agile, and fun small-team culture. We value creativity, knowledge sharing,
and employee growth, and we encourage participation in scientific
publications, conferences, and open-source software. We strive to offer
competitive salaries, compelling benefits (including health, dental,
retirement, and equity), a welcoming environment, a flexible schedule, and
a great work / life balance.

/*
 * About Us
 */
DeepSig is a venture-backed startup focused on wireless communications and
machine learning. We are creating software products and algorithms for the
commercial telecommunications market that enable the first generation of
true machine learning-based communications and sensing systems. More
information can be found on our website:  https://www.deepsig.io/.

/*
 * How to Apply
 */
Send an e-mail to address@hidden with your r?sum? / CV. Cover letters are
encouraged, but not required. You may also use this e-mail address for
questions about the position.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20180130/006b8a6f/attachment.html>

------------------------------

Message: 4
Date: Tue, 30 Jan 2018 15:45:53 -0500
From: Mike Gilmer <address@hidden>
To: Jeff Long <address@hidden>
Cc: discuss-gnuradio <address@hidden>
Subject: Re: [Discuss-gnuradio] Import Error running companion after
        upgrade to Fedora 27
Message-ID:
        <address@hidden>
Content-Type: text/plain; charset="utf-8"

Yes, thanks - I figured out I needed to have been doing that. ;-)

What a drudgery - I had to make changes to many files to get as far as I've
gotten (now up to 87% finished) and now I'm getting the errors:

/usr/bin/ld: warning: libboost_date_time.so.1.58.0, needed by
/usr/local/lib64/libuhd.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libboost_filesystem.so.1.58.0, needed by
/usr/local/lib64/libuhd.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libboost_program_options.so.1.58.0, needed by
/usr/local/lib64/libuhd.so, not found (try using -rpath or -rpath-link)
.
.
.

Any ideas?

Thanks.
Mike

On Tue, Jan 30, 2018 at 11:29 AM, Jeff Long <address@hidden> wrote:

> Import errors can happen for a variety of reasons, even if the packages
> are still in the right place. A common reason is that libraries provided by
> rpms, and that gnuradio depends on, have changed. Since Boost has changed
> to version 1.64 in Fedora 27, you'll have to rebuild gnuradio.
>
>
> On 01/30/2018 11:17 AM, Mike Gilmer wrote:
>
>> I recently upgraded my Fedora 23 laptop (on which gnuradio companion
>> worked fine) to Fedora 27
>>
>> Now when I try to run gnuradio-companion I get an error window.
>>
>> ++++++++++++++++++++++++++++++++++++++++++++
>>                    ImportError
>> Cannot import gnuradio.
>>
>> Is the python path environment variable set correctly?
>>      All OS: PYTHONPATH
>>
>> Is the library path environment variable set correctly?
>>      Linux: LD_LIBRARY_PATH
>>      Windows: PATH
>>      MacOSX: DYLD_LIBRARY_PATH
>> ++++++++++++++++++++++++++++++++++++++++++++
>>
>> (libboost_date_time.so.1.58.0: cannot open shared object file: No such
>> file or directory)
>>
>> I've checked the two env variables and they are set properly AFAIK.
>>
>> $ echo $PYTHONPATH
>> /usr/local/lib64/python2.7/site-packages
>>
>>
>> $ echo $LD_LIBRARY_PATH
>> /usr/lib64
>>
>> Any advice would be appreciated.
>>
>> -Mike
>>
>>
>> _______________________________________________
>> Discuss-gnuradio mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>>
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20180130/7a9b0212/attachment.html>

------------------------------

Message: 5
Date: Tue, 30 Jan 2018 21:09:50 +0000
From: M?ller, Marcus (CEL) <address@hidden>
To: "address@hidden" <address@hidden>,
        "address@hidden"   <address@hidden>
Cc: "address@hidden" <address@hidden>
Subject: Re: [Discuss-gnuradio] Import Error running companion after
        upgrade to Fedora 27
Message-ID: <address@hidden>
Content-Type: text/plain; charset="utf-8"

Hi Mike,

yep, whenever you update libraries (which changes their ABI), you'll
have to rebuild *all* software that depends on it. In your case, this
includes not only GNU Radio, but seemingly also UHD.

Question: Did you make any modifications to either GNU Radio or UHD?
Otherwise, I'd just say: uninstall both the GNU Radio and UHD you have
now, and install both via DNF ? in Fedora 27, you'll get UHD 3.10.1.0
and GNU Radio 3.7.11, both pretty recent. So unless you really need a
specific version of UHD, no reason to build from source; unless you
need a specific or modified version of GNU Radio, no reason to build
that either :)

Best regards,
Marcus

On Tue, 2018-01-30 at 15:45 -0500, Mike Gilmer wrote:
> Yes, thanks - I figured out I needed to have been doing that. ;-)
>
> What a drudgery - I had to make changes to many files to get as far as I've gotten (now up to 87% finished) and now I'm getting the errors:
>
> /usr/bin/ld: warning: libboost_date_time.so.1.58.0, needed by /usr/local/lib64/libuhd.so, not found (try using -rpath or -rpath-link)
> /usr/bin/ld: warning: libboost_filesystem.so.1.58.0, needed by /usr/local/lib64/libuhd.so, not found (try using -rpath or -rpath-link)
> /usr/bin/ld: warning: libboost_program_options.so.1.58.0, needed by /usr/local/lib64/libuhd.so, not found (try using -rpath or -rpath-link)
> .
> .
> .
>
> Any ideas?
>
> Thanks.
> Mike
>
> On Tue, Jan 30, 2018 at 11:29 AM, Jeff Long <address@hidden> wrote:
> > Import errors can happen for a variety of reasons, even if the packages are still in the right place. A common reason is that libraries provided by rpms, and that gnuradio depends on, have changed. Since Boost has changed to version 1.64 in Fedora 27, you'll have to rebuild gnuradio.
> >
> >
> > On 01/30/2018 11:17 AM, Mike Gilmer wrote:
> > > I recently upgraded my Fedora 23 laptop (on which gnuradio companion worked fine) to Fedora 27
> > >
> > > Now when I try to run gnuradio-companion I get an error window.
> > >
> > > ++++++++++++++++++++++++++++++++++++++++++++
> > >                    ImportError
> > > Cannot import gnuradio.
> > >
> > > Is the python path environment variable set correctly?
> > >      All OS: PYTHONPATH
> > >
> > > Is the library path environment variable set correctly?
> > >      Linux: LD_LIBRARY_PATH
> > >      Windows: PATH
> > >      MacOSX: DYLD_LIBRARY_PATH
> > > ++++++++++++++++++++++++++++++++++++++++++++
> > >
> > > (libboost_date_time.so.1.58.0: cannot open shared object file: No such file or directory)
> > >
> > > I've checked the two env variables and they are set properly AFAIK.
> > >
> > > $ echo $PYTHONPATH
> > > /usr/local/lib64/python2.7/site-packages
> > >
> > >
> > > $ echo $LD_LIBRARY_PATH
> > > /usr/lib64
> > >
> > > Any advice would be appreciated.
> > >
> > > -Mike
> > >
> > >
> > > _______________________________________________
> > > Discuss-gnuradio mailing list
> > > address@hidden
> > > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> > >
> > >
> > 
> > _______________________________________________
> > Discuss-gnuradio mailing list
> > address@hidden
> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6582 bytes
Desc: not available
URL: <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20180130/3c6e290c/attachment.bin>

------------------------------

Message: 6
Date: Tue, 30 Jan 2018 17:03:58 -0800
From: Suman Bhunia <address@hidden>
To: "discuss-gnuradio" <address@hidden>
Subject: [Discuss-gnuradio] gr-bluetooth installation issue
Message-ID:
        <address@hidden>
Content-Type: text/plain; charset="utf-8"

Hi,



I want to use gr-bluetooth to sniff packets. I have installed gnuradio3.7.9, uhd on Ubuntu 16.04. I am encountering some error installing gr-bluetooth it. When I use the cmake command, I obtain the following output:


-- The CXX compiler identification is GNU 5.4.0

-- The C compiler identification is GNU 5.4.0

-- Check for working CXX compiler: /usr/bin/c++

-- Check for working CXX compiler: /usr/bin/c++ -- works

-- Detecting CXX compiler ABI info

-- Detecting CXX compiler ABI info - done

-- Detecting CXX compile features

-- Detecting CXX compile features - done

-- Check for working C compiler: /usr/bin/cc

-- Check for working C compiler: /usr/bin/cc -- works

-- Detecting C compiler ABI info

-- Detecting C compiler ABI info - done

-- Detecting C compile features

-- Detecting C compile features - done

-- Build type not specified: defaulting to release.

-- Boost version: 1.58.0

-- Found the following Boost libraries:

--   filesystem

--   system

-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")

Checking for GNU Radio Module: RUNTIME

-- Checking for module 'gnuradio-runtime'

--   Found gnuradio-runtime, version 3.7.9

 * INCLUDES=/usr/include

 * LIBS=/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so

-- Found GNURADIO_RUNTIME: /usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so 

GNURADIO_RUNTIME_FOUND = TRUE

Checking for GNU Radio Module: BLOCKS

-- Checking for module 'gnuradio-blocks'

--   Found gnuradio-blocks, version 3.7.9

 * INCLUDES=/usr/include

 * LIBS=/usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so;/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so

-- Found GNURADIO_BLOCKS: /usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so;/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so 

GNURADIO_BLOCKS_FOUND = TRUE

Checking for GNU Radio Module: FILTER

-- Checking for module 'gnuradio-filter'

--   Found gnuradio-filter, version 3.7.9

 * INCLUDES=/usr/include

 * LIBS=/usr/lib/x86_64-linux-gnu/libgnuradio-filter.so;/usr/lib/x86_64-linux-gnu/libgnuradio-fft.so;/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so

-- Found GNURADIO_FILTER: /usr/lib/x86_64-linux-gnu/libgnuradio-filter.so;/usr/lib/x86_64-linux-gnu/libgnuradio-fft.so;/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so 

GNURADIO_FILTER_FOUND = TRUE

-- Checking for module 'cppunit'

--   Found cppunit, version 1.13.2

-- Found CPPUNIT: /usr/lib/x86_64-linux-gnu/libcppunit.so;dl 

-- Found LIBBTBB: /usr/lib/x86_64-linux-gnu/libbtbb.so 

--

-- Checking for module SWIG

-- Found SWIG version 3.0.8.

-- Found SWIG: /usr/bin/swig3.0 

-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found suitable version "2.7.12", minimum required is "2")

-- Found PythonInterp: /usr/bin/python2 (found suitable version "2.7.12", minimum required is "2")

-- Performing Test HAVE_WNO_UNUSED_BUT_SET_VARIABLE

-- Performing Test HAVE_WNO_UNUSED_BUT_SET_VARIABLE - Success

CMake Warning (dev) at /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GrTest.cmake:45 (get_target_property):

  Policy CMP0026 is not set: Disallow use of the LOCATION target property.

  Run "cmake --help-policy CMP0026" for policy details.  Use the cmake_policy

  command to set the policy and suppress this warning.



  The LOCATION property should not be read from target "gnuradio-bluetooth".

  Use the target name directly with add_custom_command, or use the generator

  _expression_ $&lt;TARGET_FILE&gt;, as appropriate.



Call Stack (most recent call first):

  python/CMakeLists.txt:44 (GR_ADD_TEST)

This warning is for project developers.  Use -Wno-dev to suppress it.



CMake Warning (dev) at /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GrTest.cmake:45 (get_target_property):

  Policy CMP0045 is not set: Error on non-existent target in

  get_target_property.  Run "cmake --help-policy CMP0045" for policy details.

  Use the cmake_policy command to set the policy and suppress this warning.



  get_target_property() called with non-existent target "/usr/bin/python2".

Call Stack (most recent call first):

  python/CMakeLists.txt:44 (GR_ADD_TEST)

This warning is for project developers.  Use -Wno-dev to suppress it.



CMake Warning (dev) at /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GrTest.cmake:45 (get_target_property):

  Policy CMP0045 is not set: Error on non-existent target in

  get_target_property.  Run "cmake --help-policy CMP0045" for policy details.

  Use the cmake_policy command to set the policy and suppress this warning.



  get_target_property() called with non-existent target

  "/home/iot3/gr-bluetooth/python/qa_gr_bluetooth_multi_sniffer.py".

Call Stack (most recent call first):

  python/CMakeLists.txt:44 (GR_ADD_TEST)

This warning is for project developers.  Use -Wno-dev to suppress it.



-- Found Doxygen: /usr/bin/doxygen (found version "1.8.11")

-- Configuring done

-- Generating done

-- Build files have been written to: /home/iot3/gr-bluetooth/build





Output of 'make' command:



[  4%] Building CXX object lib/CMakeFiles/gnuradio-bluetooth.dir/tun.cc.o

[  8%] Building CXX object lib/CMakeFiles/gnuradio-bluetooth.dir/multi_block.cc.o

[ 12%] Building CXX object lib/CMakeFiles/gnuradio-bluetooth.dir/multi_hopper_impl.cc.o

[ 16%] Building CXX object lib/CMakeFiles/gnuradio-bluetooth.dir/multi_LAP_impl.cc.o

[ 20%] Building CXX object lib/CMakeFiles/gnuradio-bluetooth.dir/multi_sniffer_impl.cc.o

[ 25%] Building CXX object lib/CMakeFiles/gnuradio-bluetooth.dir/multi_UAP_impl.cc.o

[ 29%] Building CXX object lib/CMakeFiles/gnuradio-bluetooth.dir/packet_impl.cc.o

[ 33%] Building CXX object lib/CMakeFiles/gnuradio-bluetooth.dir/piconet_impl.cc.o

[ 37%] Linking CXX shared library libgnuradio-bluetooth.so

[ 37%] Built target gnuradio-bluetooth

Scanning dependencies of target gr_bluetooth_swig_doc

[ 37%] Built target gr_bluetooth_swig_doc

Scanning dependencies of target _gr_bluetooth_swig_tag

[ 41%] Building CXX object swig/CMakeFiles/_gr_bluetooth_swig_tag.dir/_gr_bluetooth_swig_tag.cpp.o

[ 45%] Linking CXX executable _gr_bluetooth_swig_tag

[ 45%] Built target _gr_bluetooth_swig_tag

[ 50%] Generating gr_bluetooth.tag

Scanning dependencies of target gr_bluetooth_swig_2d0df

[ 54%] Building CXX object swig/CMakeFiles/gr_bluetooth_swig_2d0df.dir/gr_bluetooth_swig_2d0df.cpp.o

[ 58%] Linking CXX executable gr_bluetooth_swig_2d0df

Swig source

/home/iot3/gr-bluetooth/include/gr_bluetooth/packet.h:148: Warning 314: 'print' is a python keyword, renaming to '_print'

/home/iot3/gr-bluetooth/include/gr_bluetooth/packet.h:241: Warning 314: 'print' is a python keyword, renaming to '_print'

/home/iot3/gr-bluetooth/include/gr_bluetooth/packet.h:332: Warning 314: 'print' is a python keyword, renaming to '_print'

[ 58%] Built target gr_bluetooth_swig_2d0df

Scanning dependencies of target _gr_bluetooth

[ 62%] Building CXX object swig/CMakeFiles/_gr_bluetooth.dir/gr_bluetoothPYTHON_wrap.cxx.o

[ 66%] Linking CXX shared module _gr_bluetooth.so

[ 75%] Built target _gr_bluetooth

Scanning dependencies of target pygen_swig_d9cb6

[ 79%] Generating gr_bluetooth.pyc

[ 83%] Generating gr_bluetooth.pyo

[ 87%] Built target pygen_swig_d9cb6

Scanning dependencies of target pygen_python_b3a7c

[ 91%] Generating __init__.pyc

[ 95%] Generating __init__.pyo

[ 95%] Built target pygen_python_b3a7c

Scanning dependencies of target pygen_apps_89140

[100%] Shebangin btrx

[100%] Built target pygen_apps_89140





When I used make test command, I got the following output:



Test project /home/iot3/gr-bluetooth/build

    Start 1: qa_gr_bluetooth_multi_sniffer

1/1 Test #1: qa_gr_bluetooth_multi_sniffer ....***Failed    0.07 sec



0% tests passed, 1 tests failed out of 1



Total Test time (real) =   0.07 sec



The following tests FAILED:

      1 - qa_gr_bluetooth_multi_sniffer (Failed)

Errors while running CTest

Makefile:127: recipe for target 'test' failed

make: *** [test] Error 8



I was wondering if anyone could help me what would be a probable solution might be.



Thanks,

Suman


















-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20180130/e538ac60/attachment.html>

------------------------------

Message: 7
Date: Wed, 31 Jan 2018 01:52:37 +0000
From: Bastian Bloessl <address@hidden>
To: Zhiwu Guo <address@hidden>, address@hidden
Subject: Re: [Discuss-gnuradio] 802.15 Zigbee transceiver
Message-ID: <address@hidden>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi,

On 01/30/2018 07:04 PM, Zhiwu Guo wrote:
> Dear all,
>
> I am working on the gnuradio project of 802.15 Zigbee transceiver which
> I downloaded from link below:
>
> https://github.com/bastibl/gr-ieee802-15-4
>
> I am looking the mac.cc file which is located in the lib files. As we
> all know know, there are two types of MAC mechanism in 802.15, one is
> the CSMA based, another one is TDMA based. I am wondering which
> mechanism is this mac.cc written for? I could not find any hints on this
> file. Thank you.

The MAC block just adds the MAC header. It doesn't implement any channel
access procedure, it's just a PHY implementation.

Best,
Bastian



------------------------------

Message: 8
Date: Tue, 30 Jan 2018 19:42:46 -0800
From: Vipin Sharma <address@hidden>
To: Michael Dickens <address@hidden>
Cc: GNURadio Discussion List <address@hidden>
Subject: Re: [Discuss-gnuradio] gnu radio installation on Mac via
        MacPorts
Message-ID:
        <CAJQb1zsZyNM-b15=Q+vpm2PKCU_CUa=address@hidden>
Content-Type: text/plain; charset="utf-8"

Alright, I gave it a try after your fix just now. Still not successful.
Here is what I do/get. At first it seemed uhd installation went successful
but while building gnuradio something goes wrong. I also tried collecting
the uhd_rev.txt file from your earlier comment. I will send that file
directly to you in the next email.

mac01:~ emwaves$ sudo port selfupdate

Password:

--->  Updating MacPorts base sources using rsync

MacPorts base version 2.4.2 installed,

MacPorts base version 2.4.2 downloaded.

--->  Updating the ports tree

--->  MacPorts base is already the latest version


The ports tree has been updated. To upgrade your installed ports, you
should run

  port upgrade outdated

mac01:~ emwaves$ sudo port uninstall gnuradio

--->  Deactivating gnuradio
@3.7.11_6+docs+grc+jack+log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq

--->  Cleaning gnuradio

--->  Uninstalling gnuradio
@3.7.11_6+docs+grc+jack+log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq

--->  Cleaning gnuradio

mac01:~ emwaves$ sudo port uninstall uhd

--->  Deactivating uhd
@3.10.2.0_1+docs+examples+gpsd+libusb+manpages+manual+python27+test

--->  Cleaning uhd

--->  Uninstalling uhd
@3.10.2.0_1+docs+examples+gpsd+libusb+manpages+manual+python27+test

--->  Cleaning uhd

mac01:~ emwaves$ sudo port install gnuradio

--->  Computing dependencies for gtk2

--->  Fetching archive for gtk2

--->  Attempting to fetch gtk2-2.24.32_0+x11.darwin_16.x86_64.tbz2 from
https://packages.macports.org/gtk2

--->  Attempting to fetch gtk2-2.24.32_0+x11.darwin_16.x86_64.tbz2.rmd160
from https://packages.macports.org/gtk2

--->  Installing gtk2 @2.24.32_0+x11

--->  Cleaning gtk2

--->  Computing dependencies for gtk2

--->  Deactivating gtk2 @2.24.31_0+x11

--->  Cleaning gtk2

--->  Activating gtk2 @2.24.32_0+x11

--->  Cleaning gtk2

--->  Computing dependencies for py27-zmq

--->  Fetching archive for py27-zmq

--->  Attempting to fetch py27-zmq-16.0.4_0.darwin_16.x86_64.tbz2 from
https://packages.macports.org/py27-zmq

--->  Attempting to fetch py27-zmq-16.0.4_0.darwin_16.x86_64.tbz2.rmd160
from https://packages.macports.org/py27-zmq

--->  Installing py27-zmq @16.0.4_0

--->  Cleaning py27-zmq

--->  Computing dependencies for py27-zmq

--->  Deactivating py27-zmq @16.0.3_0

--->  Cleaning py27-zmq

--->  Activating py27-zmq @16.0.4_0

--->  Cleaning py27-zmq

--->  Computing dependencies for gnuradio

The following dependencies will be installed:  uhd

Continue? [Y/n]: Y

--->  Fetching archive for uhd

--->  Attempting to fetch
uhd-3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test.darwin_16.x86_64.tbz2
from https://packages.macports.org/uhd

--->  Attempting to fetch
uhd-3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test.darwin_16.x86_64.tbz2
from http://sea.us.packages.macports.org/macports/packages/uhd

--->  Attempting to fetch
uhd-3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test.darwin_16.x86_64.tbz2
from http://ywg.ca.packages.macports.org/mirror/macports/packages/uhd

--->  Fetching distfiles for uhd

--->  Verifying checksums for uhd

--->  Extracting uhd

--->  Applying patches to uhd

--->  Configuring uhd

--->  Building uhd

--->  Staging uhd into destroot

--->  Installing uhd
@3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test

--->  Activating uhd
@3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test

--->  Cleaning uhd

--->  Fetching archive for gnuradio

--->  Attempting to fetch
gnuradio-3.7.11_6+docs+grc+jack+log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq.darwin_16.x86_64.tbz2
from https://packages.macports.org/gnuradio

--->  Attempting to fetch
gnuradio-3.7.11_6+docs+grc+jack+log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq.darwin_16.x86_64.tbz2
from http://sea.us.packages.macports.org/macports/packages/gnuradio

--->  Attempting to fetch
gnuradio-3.7.11_6+docs+grc+jack+log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq.darwin_16.x86_64.tbz2
from http://ywg.ca.packages.macports.org/mirror/macports/packages/gnuradio

--->  Fetching distfiles for gnuradio

--->  Verifying checksums for gnuradio

--->  Extracting gnuradio

--->  Applying patches to gnuradio

--->  Configuring gnuradio

--->  Building gnuradio

--->  Staging gnuradio into destroot

--->  Installing gnuradio
@3.7.11_6+docs+grc+jack+log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq

--->  Activating gnuradio
@3.7.11_6+docs+grc+jack+log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq

--->  Cleaning gnuradio

--->  Updating database of binaries

--->  Scanning binaries for linking errors

--->  Found 76 broken files, matching files to ports

--->  Found 1 broken port, determining rebuild order

You can always run 'port rev-upgrade' again to fix errors.

The following ports will be rebuilt: uhd @3.10.2.0
+docs+examples+gpsd+libusb+manpages+manual+python27+test

Continue? [Y/n]: Y

--->  Computing dependencies for gpsd

--->  Fetching archive for gpsd

--->  Attempting to fetch gpsd-3.17_1.darwin_16.x86_64.tbz2 from
https://packages.macports.org/gpsd

--->  Attempting to fetch gpsd-3.17_1.darwin_16.x86_64.tbz2.rmd160 from
https://packages.macports.org/gpsd

--->  Installing gpsd @3.17_1

--->  Cleaning gpsd

--->  Computing dependencies for gpsd

--->  Deactivating gpsd @3.17_0

--->  Cleaning gpsd

--->  Activating gpsd @3.17_1

--->  Cleaning gpsd

--->  Computing dependencies for uhd

--->  Cleaning uhd

--->  Updating database of binaries

--->  Scanning binaries for linking errors

--->  Found 76 broken files, matching files to ports

--->  Found 1 broken port, determining rebuild order

--->  Rebuilding in order

     uhd @3.10.2.0 +docs+examples+gpsd+libusb+manpages+manual+python27+test

--->  Computing dependencies for uhd

--->  Fetching distfiles for uhd

--->  Verifying checksums for uhd

--->  Extracting uhd

--->  Applying patches to uhd

--->  Configuring uhd

--->  Building uhd

--->  Staging uhd into destroot

--->  Unable to uninstall uhd
@3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test, the
following ports depend on it:

--->  gnuradio
@3.7.11_6+docs+grc+jack+log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq

Warning: Uninstall forced.  Proceeding despite dependencies.

--->  Deactivating uhd
@3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test

--->  Cleaning uhd

--->  Uninstalling uhd
@3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test

--->  Cleaning uhd

--->  Computing dependencies for uhd

--->  Installing uhd
@3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test

--->  Activating uhd
@3.10.2.0_2+docs+examples+gpsd+libusb+manpages+manual+python27+test

--->  Cleaning uhd

--->  Updating database of binaries

--->  Scanning binaries for linking errors

--->  No broken files found.

--->  Some of the ports you installed have notes:

  gpsd has the following notes:

    The xgps variant is now needed to get the xgps and xgpsspeed programs.

mac01:~ emwaves$


On Tue, Jan 30, 2018 at 6:02 AM, Michael Dickens <address@hidden>
wrote:

> I pushed fixes into MacPorts this morning. Will be live by around 9:30 AM
> US/Eastern (about 30 minutes from now). You will need to "selfupdate" or
> "sync" to get the changes. Please let me know (here or off list) success or
> failure. Cheers! - MLD
>
> On Mon, Jan 29, 2018, at 8:54 PM, Vipin Sharma wrote:
>
> Great; thank you. I will just wait for your fix.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20180130/38345ad3/attachment.html>

------------------------------

Message: 9
Date: Tue, 30 Jan 2018 20:41:58 -0800
From: Cinaed Simson <address@hidden>
To: address@hidden
Subject: Re: [Discuss-gnuradio] gr-bluetooth installation issue
Message-ID: <address@hidden>
Content-Type: text/plain; charset=utf-8

In the directory

  ./gr-bluetooth/python

try changing the line

  import bluetooth.swig as bluetooth

to

  import _gr_bluetooth as bluetooth

in the file

  qa_gr_bluetooth_multi_sniffer.py


-- Cinaed

On 01/30/2018 05:03 PM, Suman Bhunia wrote:
> Hi,
>
> I want to use gr-bluetooth to sniff packets. I have installed
> gnuradio3.7.9, uhd on Ubuntu 16.04. I am encountering some error
> installing gr-bluetooth it. When I use the cmake command, I obtain the
> following output:
>
>
>     -- The CXX compiler identification is GNU 5.4.0
>     -- The C compiler identification is GNU 5.4.0
>     -- Check for working CXX compiler: /usr/bin/c++
>     -- Check for working CXX compiler: /usr/bin/c++ -- works
>     -- Detecting CXX compiler ABI info
>     -- Detecting CXX compiler ABI info - done
>     -- Detecting CXX compile features
>     -- Detecting CXX compile features - done
>     -- Check for working C compiler: /usr/bin/cc
>     -- Check for working C compiler: /usr/bin/cc -- works
>     -- Detecting C compiler ABI info
>     -- Detecting C compiler ABI info - done
>     -- Detecting C compile features
>     -- Detecting C compile features - done
>     -- Build type not specified: defaulting to release.
>     -- Boost version: 1.58.0
>     -- Found the following Boost libraries:
>     --?? filesystem
>     --?? system
>     -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
>     Checking for GNU Radio Module: RUNTIME
>     -- Checking for module 'gnuradio-runtime'
>     --?? Found gnuradio-runtime, version 3.7.9
>     ?* INCLUDES=/usr/include
>     ?*
>     LIBS=/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
>     -- Found GNURADIO_RUNTIME:
>     /usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
>     ?
>     GNURADIO_RUNTIME_FOUND = TRUE
>     Checking for GNU Radio Module: BLOCKS
>     -- Checking for module 'gnuradio-blocks'
>     --?? Found gnuradio-blocks, version 3.7.9
>     ?* INCLUDES=/usr/include
>     ?*
>     LIBS=/usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so;/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
>     -- Found GNURADIO_BLOCKS:
>     /usr/lib/x86_64-linux-gnu/libgnuradio-blocks.so;/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
>     ?
>     GNURADIO_BLOCKS_FOUND = TRUE
>     Checking for GNU Radio Module: FILTER
>     -- Checking for module 'gnuradio-filter'
>     --?? Found gnuradio-filter, version 3.7.9
>     ?* INCLUDES=/usr/include
>     ?*
>     LIBS=/usr/lib/x86_64-linux-gnu/libgnuradio-filter.so;/usr/lib/x86_64-linux-gnu/libgnuradio-fft.so;/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
>     -- Found GNURADIO_FILTER:
>     /usr/lib/x86_64-linux-gnu/libgnuradio-filter.so;/usr/lib/x86_64-linux-gnu/libgnuradio-fft.so;/usr/lib/x86_64-linux-gnu/libgnuradio-runtime.so;/usr/lib/x86_64-linux-gnu/libgnuradio-pmt.so
>     ?
>     GNURADIO_FILTER_FOUND = TRUE
>     -- Checking for module 'cppunit'
>     --?? Found cppunit, version 1.13.2
>     -- Found CPPUNIT: /usr/lib/x86_64-linux-gnu/libcppunit.so;dl ?
>     -- Found LIBBTBB: /usr/lib/x86_64-linux-gnu/libbtbb.so ?
>     --
>     -- Checking for module SWIG
>     -- Found SWIG version 3.0.8.
>     -- Found SWIG: /usr/bin/swig3.0 ?
>     -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so
>     (found suitable version "2.7.12", minimum required is "2")
>     -- Found PythonInterp: /usr/bin/python2 (found suitable version
>     "2.7.12", minimum required is "2")
>     -- Performing Test HAVE_WNO_UNUSED_BUT_SET_VARIABLE
>     -- Performing Test HAVE_WNO_UNUSED_BUT_SET_VARIABLE - Success
>     CMake Warning (dev) at
>     /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GrTest.cmake:45
>     (get_target_property):
>     ? Policy CMP0026 is not set: Disallow use of the LOCATION target
>     property.
>     ? Run "cmake --help-policy CMP0026" for policy details.? Use the
>     cmake_policy
>     ? command to set the policy and suppress this warning.
>
>     ? The LOCATION property should not be read from target
>     "gnuradio-bluetooth".
>     ? Use the target name directly with add_custom_command, or use the
>     generator
>     ? _expression_ $<TARGET_FILE>, as appropriate.
>
>     Call Stack (most recent call first):
>     ? python/CMakeLists.txt:44 (GR_ADD_TEST)
>     This warning is for project developers.? Use -Wno-dev to suppress it.
>
>     CMake Warning (dev) at
>     /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GrTest.cmake:45
>     (get_target_property):
>     ? Policy CMP0045 is not set: Error on non-existent target in
>     ? get_target_property.? Run "cmake --help-policy CMP0045" for policy
>     details.
>     ? Use the cmake_policy command to set the policy and suppress this
>     warning.
>
>     ? get_target_property() called with non-existent target
>     "/usr/bin/python2".
>     Call Stack (most recent call first):
>     ? python/CMakeLists.txt:44 (GR_ADD_TEST)
>     This warning is for project developers.? Use -Wno-dev to suppress it.
>
>     CMake Warning (dev) at
>     /usr/lib/x86_64-linux-gnu/cmake/gnuradio/GrTest.cmake:45
>     (get_target_property):
>     ? Policy CMP0045 is not set: Error on non-existent target in
>     ? get_target_property.? Run "cmake --help-policy CMP0045" for policy
>     details.
>     ? Use the cmake_policy command to set the policy and suppress this
>     warning.
>
>     ? get_target_property() called with non-existent target
>     ? "/home/iot3/gr-bluetooth/python/qa_gr_bluetooth_multi_sniffer.py".
>     Call Stack (most recent call first):
>     ? python/CMakeLists.txt:44 (GR_ADD_TEST)
>     This warning is for project developers.? Use -Wno-dev to suppress it.
>
>     -- Found Doxygen: /usr/bin/doxygen (found version "1.8.11")
>     -- Configuring done
>     -- Generating done
>     -- Build files have been written to: /home/iot3/gr-bluetooth/build
>
>
>
> Output of 'make' command:
>
>
>     [? 4%] Building CXX object
>     lib/CMakeFiles/gnuradio-bluetooth.dir/tun.cc.o
>     <http://gnuradio-bluetooth.dir/tun.cc.o>
>     [? 8%] Building CXX object
>     lib/CMakeFiles/gnuradio-bluetooth.dir/multi_block.cc.o
>     <http://gnuradio-bluetooth.dir/multi_block.cc.o>
>     [ 12%] Building CXX object
>     lib/CMakeFiles/gnuradio-bluetooth.dir/multi_hopper_impl.cc.o
>     <http://gnuradio-bluetooth.dir/multi_hopper_impl.cc.o>
>     [ 16%] Building CXX object
>     lib/CMakeFiles/gnuradio-bluetooth.dir/multi_LAP_impl.cc.o
>     <http://gnuradio-bluetooth.dir/multi_LAP_impl.cc.o>
>     [ 20%] Building CXX object
>     lib/CMakeFiles/gnuradio-bluetooth.dir/multi_sniffer_impl.cc.o
>     <http://gnuradio-bluetooth.dir/multi_sniffer_impl.cc.o>
>     [ 25%] Building CXX object
>     lib/CMakeFiles/gnuradio-bluetooth.dir/multi_UAP_impl.cc.o
>     <http://gnuradio-bluetooth.dir/multi_UAP_impl.cc.o>
>     [ 29%] Building CXX object
>     lib/CMakeFiles/gnuradio-bluetooth.dir/packet_impl.cc.o
>     <http://gnuradio-bluetooth.dir/packet_impl.cc.o>
>     [ 33%] Building CXX object
>     lib/CMakeFiles/gnuradio-bluetooth.dir/piconet_impl.cc.o
>     <http://gnuradio-bluetooth.dir/piconet_impl.cc.o>
>     [ 37%] Linking CXX shared library libgnuradio-bluetooth.so
>     [ 37%] Built target gnuradio-bluetooth
>     Scanning dependencies of target gr_bluetooth_swig_doc
>     [ 37%] Built target gr_bluetooth_swig_doc
>     Scanning dependencies of target _gr_bluetooth_swig_tag
>     [ 41%] Building CXX object
>     swig/CMakeFiles/_gr_bluetooth_swig_tag.dir/_gr_bluetooth_swig_tag.cpp.o
>     [ 45%] Linking CXX executable _gr_bluetooth_swig_tag
>     [ 45%] Built target _gr_bluetooth_swig_tag
>     [ 50%] Generating gr_bluetooth.tag
>     Scanning dependencies of target gr_bluetooth_swig_2d0df
>     [ 54%] Building CXX object
>     swig/CMakeFiles/gr_bluetooth_swig_2d0df.dir/gr_bluetooth_swig_2d0df.cpp.o
>     [ 58%] Linking CXX executable gr_bluetooth_swig_2d0df
>     Swig source
>     /home/iot3/gr-bluetooth/include/gr_bluetooth/packet.h:148: Warning
>     314: 'print' is a python keyword, renaming to '_print'
>     /home/iot3/gr-bluetooth/include/gr_bluetooth/packet.h:241: Warning
>     314: 'print' is a python keyword, renaming to '_print'
>     /home/iot3/gr-bluetooth/include/gr_bluetooth/packet.h:332: Warning
>     314: 'print' is a python keyword, renaming to '_print'
>     [ 58%] Built target gr_bluetooth_swig_2d0df
>     Scanning dependencies of target _gr_bluetooth
>     [ 62%] Building CXX object
>     swig/CMakeFiles/_gr_bluetooth.dir/gr_bluetoothPYTHON_wrap.cxx.o
>     [ 66%] Linking CXX shared module _gr_bluetooth.so
>     [ 75%] Built target _gr_bluetooth
>     Scanning dependencies of target pygen_swig_d9cb6
>     [ 79%] Generating gr_bluetooth.pyc
>     [ 83%] Generating gr_bluetooth.pyo
>     [ 87%] Built target pygen_swig_d9cb6
>     Scanning dependencies of target pygen_python_b3a7c
>     [ 91%] Generating __init__.pyc
>     [ 95%] Generating __init__.pyo
>     [ 95%] Built target pygen_python_b3a7c
>     Scanning dependencies of target pygen_apps_89140
>     [100%] Shebangin btrx
>     [100%] Built target pygen_apps_89140
>
>
>
> When I used make test command, I got the following output:
>
>     Test project /home/iot3/gr-bluetooth/build
>     ??? Start 1: qa_gr_bluetooth_multi_sniffer
>     1/1 Test #1: qa_gr_bluetooth_multi_sniffer ....***Failed??? 0.07 sec
>
>     0% tests passed, 1 tests failed out of 1
>
>     Total Test time (real) =?? 0.07 sec
>
>     The following tests FAILED:
>     ?? ?? 1 - qa_gr_bluetooth_multi_sniffer (Failed)
>     Errors while running CTest
>     Makefile:127: recipe for target 'test' failed
>     make: *** [test] Error 8
>
>
> I was wondering if anyone could help me what would be a probable
> solution might be.
>
> Thanks,
> Suman
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>




------------------------------

Message: 10
Date: Tue, 30 Jan 2018 23:28:14 -0800
From: Vipin Sharma <address@hidden>
To: Michael Dickens <address@hidden>
Cc: GNURadio Discussion List <address@hidden>
Subject: Re: [Discuss-gnuradio] gnu radio installation on Mac via
        MacPorts
Message-ID:
        <CAJQb1zsGW6d8YJ4A2y3zHf160WY3VtBBqSm1G3VF=address@hidden>
Content-Type: text/plain; charset="utf-8"

Ok, I tried another attempt by completely removing the MacPorts and
restarting. This time it worked!
sudo port -fp uninstall installed

sudo rm -rf         /opt/local         /Applications/DarwinPorts
/Applications/MacPorts         /Library/LaunchDaemons/org.macports.*
  /Library/Receipts/DarwinPorts*.pkg
/Library/Receipts/MacPorts*.pkg
/Library/StartupItems/DarwinPortsStartup
/Library/Tcl/darwinports1.0         /Library/Tcl/macports1.0
~/.macports

sudo port selfupdate

sudo port install gnuradio


I got segmentation fault when I tried this:

uhd_fft -f 868M -s 10M


but then after trying

sudo port select --set python python27

uhd_fft works fine.

Thanks for your support!


Vipin

On Tue, Jan 30, 2018 at 7:42 PM, Vipin Sharma <address@hidden>
wrote:

> Alright, I gave it a try after your fix just now. Still not successful.
> Here is what I do/get. At first it seemed uhd installation went successful
> but while building gnuradio something goes wrong. I also tried collecting
> the uhd_rev.txt file from your earlier comment. I will send that file
> directly to you in the next email.
>
> mac01:~ emwaves$ sudo port selfupdate
>
> Password:
>
> --->  Updating MacPorts base sources using rsync
>
> MacPorts base version 2.4.2 installed,
>
> MacPorts base version 2.4.2 downloaded.
>
> --->  Updating the ports tree
>
> --->  MacPorts base is already the latest version
>
>
> The ports tree has been updated. To upgrade your installed ports, you
> should run
>
>   port upgrade outdated
>
> mac01:~ emwaves$ sudo port uninstall gnuradio
>
> --->  Deactivating gnuradio @3.7.11_6+docs+grc+jack+
> log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq
>
> --->  Cleaning gnuradio
>
> --->  Uninstalling gnuradio @3.7.11_6+docs+grc+jack+
> log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq
>
> --->  Cleaning gnuradio
>
> mac01:~ emwaves$ sudo port uninstall uhd
>
> --->  Deactivating uhd @3.10.2.0_1+docs+examples+
> gpsd+libusb+manpages+manual+python27+test
>
> --->  Cleaning uhd
>
> --->  Uninstalling uhd @3.10.2.0_1+docs+examples+
> gpsd+libusb+manpages+manual+python27+test
>
> --->  Cleaning uhd
>
> mac01:~ emwaves$ sudo port install gnuradio
>
> --->  Computing dependencies for gtk2
>
> --->  Fetching archive for gtk2
>
> --->  Attempting to fetch gtk2-2.24.32_0+x11.darwin_16.x86_64.tbz2 from
> https://packages.macports.org/gtk2
>
> --->  Attempting to fetch gtk2-2.24.32_0+x11.darwin_16.x86_64.tbz2.rmd160
> from https://packages.macports.org/gtk2
>
> --->  Installing gtk2 @2.24.32_0+x11
>
> --->  Cleaning gtk2
>
> --->  Computing dependencies for gtk2
>
> --->  Deactivating gtk2 @2.24.31_0+x11
>
> --->  Cleaning gtk2
>
> --->  Activating gtk2 @2.24.32_0+x11
>
> --->  Cleaning gtk2
>
> --->  Computing dependencies for py27-zmq
>
> --->  Fetching archive for py27-zmq
>
> --->  Attempting to fetch py27-zmq-16.0.4_0.darwin_16.x86_64.tbz2 from
> https://packages.macports.org/py27-zmq
>
> --->  Attempting to fetch py27-zmq-16.0.4_0.darwin_16.x86_64.tbz2.rmd160
> from https://packages.macports.org/py27-zmq
>
> --->  Installing py27-zmq @16.0.4_0
>
> --->  Cleaning py27-zmq
>
> --->  Computing dependencies for py27-zmq
>
> --->  Deactivating py27-zmq @16.0.3_0
>
> --->  Cleaning py27-zmq
>
> --->  Activating py27-zmq @16.0.4_0
>
> --->  Cleaning py27-zmq
>
> --->  Computing dependencies for gnuradio
>
> The following dependencies will be installed:  uhd
>
> Continue? [Y/n]: Y
>
> --->  Fetching archive for uhd
>
> --->  Attempting to fetch uhd-3.10.2.0_2+docs+examples+
> gpsd+libusb+manpages+manual+python27+test.darwin_16.x86_64.tbz2 from
> https://packages.macports.org/uhd
>
> --->  Attempting to fetch uhd-3.10.2.0_2+docs+examples+
> gpsd+libusb+manpages+manual+python27+test.darwin_16.x86_64.tbz2 from
> http://sea.us.packages.macports.org/macports/packages/uhd
>
> --->  Attempting to fetch uhd-3.10.2.0_2+docs+examples+
> gpsd+libusb+manpages+manual+python27+test.darwin_16.x86_64.tbz2 from
> http://ywg.ca.packages.macports.org/mirror/macports/packages/uhd
>
> --->  Fetching distfiles for uhd
>
> --->  Verifying checksums for uhd
>
> --->  Extracting uhd
>
> --->  Applying patches to uhd
>
> --->  Configuring uhd
>
> --->  Building uhd
>
> --->  Staging uhd into destroot
>
> --->  Installing uhd @3.10.2.0_2+docs+examples+
> gpsd+libusb+manpages+manual+python27+test
>
> --->  Activating uhd @3.10.2.0_2+docs+examples+
> gpsd+libusb+manpages+manual+python27+test
>
> --->  Cleaning uhd
>
> --->  Fetching archive for gnuradio
>
> --->  Attempting to fetch gnuradio-3.7.11_6+docs+grc+jack+log4cpp+logging+
> portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq.darwin_16.x86_64.tbz2 from
> https://packages.macports.org/gnuradio
>
> --->  Attempting to fetch gnuradio-3.7.11_6+docs+grc+jack+log4cpp+logging+
> portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq.darwin_16.x86_64.tbz2 from
> http://sea.us.packages.macports.org/macports/packages/gnuradio
>
> --->  Attempting to fetch gnuradio-3.7.11_6+docs+grc+jack+log4cpp+logging+
> portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq.darwin_16.x86_64.tbz2 from
> http://ywg.ca.packages.macports.org/mirror/macports/packages/gnuradio
>
> --->  Fetching distfiles for gnuradio
>
> --->  Verifying checksums for gnuradio
>
> --->  Extracting gnuradio
>
> --->  Applying patches to gnuradio
>
> --->  Configuring gnuradio
>
> --->  Building gnuradio
>
> --->  Staging gnuradio into destroot
>
> --->  Installing gnuradio @3.7.11_6+docs+grc+jack+
> log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq
>
> --->  Activating gnuradio @3.7.11_6+docs+grc+jack+
> log4cpp+logging+portaudio+qtgui+sdl+swig+uhd+wavelet+zeromq
>
> --->  Cleaning gnuradio
>
> --->  Updating database of binaries
>
> --->  Scanning binaries for linking errors
>
> --->  Found 76 broken files, matching files to ports
>
> --->  Found 1 broken port, determining rebuild order
>
> You can always run 'port rev-upgrade' again to fix errors.
>
> The following ports will be rebuilt: uhd @3.10.2.0+docs+examples+gpsd+
> libusb+manpages+manual+python27+test
>
> Continue? [Y/n]: Y
>
> --->  Computing dependencies for gpsd
>
> --->  Fetching archive for gpsd
>
> --->  Attempting to fetch gpsd-3.17_1.darwin_16.x86_64.tbz2 from
> https://packages.macports.org/gpsd
>
> --->  Attempting to fetch gpsd-3.17_1.darwin_16.x86_64.tbz2.rmd160 from
> https://packages.macports.org/gpsd
>
> --->  Installing gpsd @3.17_1
>
> --->  Cleaning gpsd
>
> --->  Computing dependencies for gpsd
>
> --->  Deactivating gpsd @3.17_0
>
> --->  Cleaning gpsd
>
> --->  Activating gpsd @3.17_1
>
> --->  Cleaning gpsd
>
> --->  Computing dependencies for uhd
>
> --->  Cleaning uhd
>
> --->  Updating database of binaries
>
> --->  Scanning binaries for linking errors
>
> --->  Found 76 broken files, matching files to ports
>
> --->  Found 1 broken port, determining rebuild order
>
> --->  Rebuilding in order
>
>      uhd @3.10.2.0 +docs+examples+gpsd+libusb+
> manpages+manual+python27+test
>
> --->  Computing dependencies for uhd
>
> --->  Fetching distfiles for uhd
>
> --->  Verifying checksums for uhd
>
> --->  Extracting uhd
>
> --->  Applying patches to uhd
>
> --->  Configuring uhd
>
> --->  Building uhd
>
> --->  Staging uhd into destroot
>
> --->  Unable to uninstall uhd @3.10.2.0_2+docs+examples+
> gpsd+libusb+manpages+manual+python27+test, the following ports depend on
> it:
>
> --->  gnuradio @3.7.11_6+docs+grc+jack+log4cpp+logging+portaudio+
> qtgui+sdl+swig+uhd+wavelet+zeromq
>
> Warning: Uninstall forced.  Proceeding despite dependencies.
>
> --->  Deactivating uhd @3.10.2.0_2+docs+examples+
> gpsd+libusb+manpages+manual+python27+test
>
> --->  Cleaning uhd
>
> --->  Uninstalling uhd @3.10.2.0_2+docs+examples+
> gpsd+libusb+manpages+manual+python27+test
>
> --->  Cleaning uhd
>
> --->  Computing dependencies for uhd
>
> --->  Installing uhd @3.10.2.0_2+docs+examples+
> gpsd+libusb+manpages+manual+python27+test
>
> --->  Activating uhd @3.10.2.0_2+docs+examples+
> gpsd+libusb+manpages+manual+python27+test
>
> --->  Cleaning uhd
>
> --->  Updating database of binaries
>
> --->  Scanning binaries for linking errors
>
> --->  No broken files found.
>
> --->  Some of the ports you installed have notes:
>
>   gpsd has the following notes:
>
>     The xgps variant is now needed to get the xgps and xgpsspeed programs.
>
> mac01:~ emwaves$
>
>
> On Tue, Jan 30, 2018 at 6:02 AM, Michael Dickens <
> address@hidden> wrote:
>
>> I pushed fixes into MacPorts this morning. Will be live by around 9:30 AM
>> US/Eastern (about 30 minutes from now). You will need to "selfupdate" or
>> "sync" to get the changes. Please let me know (here or off list) success or
>> failure. Cheers! - MLD
>>
>> On Mon, Jan 29, 2018, at 8:54 PM, Vipin Sharma wrote:
>>
>> Great; thank you. I will just wait for your fix.
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20180130/75d95fad/attachment.html>

------------------------------

Message: 11
Date: Wed, 31 Jan 2018 11:54:27 +0100
From: kokosz <address@hidden>
To: address@hidden <address@hidden>
Subject: [Discuss-gnuradio] How to use IQ Bal Optimize/Fix?
Message-ID: <address@hidden>
Content-Type: text/plain; charset="utf-8"

Dear all,   It looks like IQ imbalance is causing problems in my application, as I was able to simulate real-world-like problems after adding &#34;IQ Imbalance Generator&#34; to my GRC flowgraph. So, after simulating this imbalance, I wanted to get rid of it with the help of &#34;IQ Bal Optimize&#34; and &#34;IQ Bal Fix&#34; combo. Unfortunately, I can&#39;t get it work.   As far as I understand, &#34;IQ Bal Optimize&#34; is automatically detecting settings (i.e. magnitude and phase correction values) for &#34;IQ Bal Fix&#34; and pass it to the latter block via message connection called &#34;iqbal_corr&#34;. Is this is true, I don&#39;t understand why I have to manually set &#34;Magnitude&#34; and &#34;Phase&#34; in &#34;IQ Bal Fix&#34; (otherwise I cannot run the flowgraph because of empty fields). I think that these fields were meant for making manual fix possible, but when using &#34;IQ Bal Optimize&#34;/&#34;IQ Bal Fix&#34; combo, message connection should be all what is necessary, right? Also, because of lack of detailed documentation, I am not sure how to interpret &#34;Period&#34; field in IQ Bal Optimize - what units are expected here?   I am using GRC v3.7.11, compiled from source files few days ago.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20180131/4415ba00/attachment.html>

------------------------------

Message: 12
Date: Wed, 31 Jan 2018 06:34:07 -0500
From: Jeff Long <address@hidden>
To: address@hidden
Subject: Re: [Discuss-gnuradio] How to use IQ Bal Optimize/Fix?
Message-ID: <address@hidden>
Content-Type: text/plain; charset=utf-8; format=flowed

If you put 0 in the manual fields and wire

   src->optimize->iqbal

and

   src->iqbal

it seems to work fine. Do you have a GRC file?

"period" is some sort of time constant, in samples. If you set it to
samp_rate, optimization will happen within a second. Smaller values for
faster response up to a point.

On 01/31/2018 05:54 AM, kokosz wrote:
> Dear all,
>
> It looks like IQ imbalance is causing problems in my application, as I
> was able to simulate real-world-like problems after adding "IQ Imbalance
> Generator" to my GRC flowgraph. So, after simulating this imbalance, I
> wanted to get rid of it with the help of "IQ Bal Optimize" and "IQ Bal
> Fix" combo. Unfortunately, I can't get it work.
>
> As far as I understand, "IQ Bal Optimize" is automatically detecting
> settings (i.e. magnitude and phase correction values) for "IQ Bal Fix"
> and pass it to the latter block via message connection called
> "iqbal_corr". Is this is true, I don't understand why I have to manually
> set "Magnitude" and "Phase" in "IQ Bal Fix" (otherwise I cannot run the
> flowgraph because of empty fields). I think that these fields were meant
> for making manual fix possible, but when using "IQ Bal Optimize"/"IQ Bal
> Fix" combo, message connection should be all what is necessary, right?
> Also, because of lack of detailed documentation, I am not sure how to
> interpret "Period" field in IQ Bal Optimize - what units are expected here?
>
> I am using GRC v3.7.11, compiled from source files few days ago.
>
>
>
>
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>



------------------------------

Message: 13
Date: Wed, 31 Jan 2018 08:59:01 -0500
From: Michael Dickens <address@hidden>
To: Vipin Sharma <address@hidden>
Cc: GNURadio Discussion List <address@hidden>
Subject: Re: [Discuss-gnuradio] gnu radio installation on Mac via
        MacPorts
Message-ID:
        <address@hidden>
Content-Type: text/plain; charset="utf-8"

Thanks for reporting back, Vipin, and your creative solution. Sometimes
starting over is the way to go ;)
A strange note: the "rev-upgrade" logfile was clean; no errors or issues
found beyond the usual innocuous ones. I've no idea why port thought uhd
was broken the final run-through.
Anyway: Good catch on the gpsd issue; I'm glad we got it fixed quickly! You're very welcome for the support! - MLD
On Wed, Jan 31, 2018, at 2:28 AM, Vipin Sharma wrote:
> Ok, I tried another attempt by completely removing the MacPorts and
> restarting. This time it worked!> sudo port -fp uninstall installed
> sudo rm -rf         /opt/local         /Applications/DarwinPorts
> /Applications/MacPorts         /Library/LaunchDaemons/org.macports.*
> /Library/Receipts/DarwinPorts*.pkg
> /Library/Receipts/MacPorts*.pkg
> /Library/StartupItems/DarwinPortsStartup
> /Library/Tcl/darwinports1.0         /Library/Tcl/macports1.0
> ~/.macports>
> sudo port selfupdate


>


> sudo port install gnuradio 


>


>


> I got segmentation fault when I tried this:


> uhd_fft -f 868M -s 10M


>


> but then after trying


>


> sudo port select --set python python27


>
> uhd_fft works fine.
>
> Thanks for your support!



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20180131/93ccd1a0/attachment.html>

------------------------------

Message: 14
Date: Wed, 31 Jan 2018 15:21:35 +0100
From: kokosz <address@hidden>
To: Jeff Long <address@hidden>, discuss gnuradio
        <address@hidden>
Subject: Re: [Discuss-gnuradio]  How to use IQ Bal Optimize/Fix?
Message-ID: <address@hidden>
Content-Type: text/plain; charset="utf-8"

This is exactly what I am doing, but restored signal looks very weird
(its real part is close to zero). I have attached example *grc file
showing the problem. 




                  Dnia 31 stycznia 2018 12:34 Jeff Long &lt;address@hidden&gt; napisa?(a):


                   If you put 0 in the manual fields and wire

  ?src-&gt;optimize-&gt;iqbal

 and

  ?src-&gt;iqbal

 it seems to work fine. Do you have a GRC file?

 &#34;period&#34; is some sort of time constant, in samples. If you set it to 
 samp_rate, optimization will happen within a second. Smaller values for 
 faster response up to a point.

 On 01/31/2018 05:54 AM, kokosz wrote:

 Dear all,

 It looks like IQ imbalance is causing problems in my application, as I 
 was able to simulate real-world-like problems after adding &#34;IQ Imbalance 
 Generator&#34; to my GRC flowgraph. So, after simulating this imbalance, I 
 wanted to get rid of it with the help of &#34;IQ Bal Optimize&#34; and &#34;IQ Bal 
 Fix&#34; combo. Unfortunately, I can&#39;t get it work.

 As far as I understand, &#34;IQ Bal Optimize&#34; is automatically detecting 
 settings (i.e. magnitude and phase correction values) for &#34;IQ Bal Fix&#34; 
 and pass it to the latter block via message connection called 
 &#34;iqbal_corr&#34;. Is this is true, I don&#39;t understand why I have to manually 
 set &#34;Magnitude&#34; and &#34;Phase&#34; in &#34;IQ Bal Fix&#34; (otherwise I cannot run the 
 flowgraph because of empty fields). I think that these fields were meant 
 for making manual fix possible, but when using &#34;IQ Bal Optimize&#34;/&#34;IQ Bal 
 Fix&#34; combo, message connection should be all what is necessary, right? 
 Also, because of lack of detailed documentation, I am not sure how to 
 interpret &#34;Period&#34; field in IQ Bal Optimize - what units are expected here?

 I am using GRC v3.7.11, compiled from source files few days ago.




 ______________________________
 Discuss-gnuradio mailing list
  address@hidden
 lists.gnu.org lists.gnu.org



 ______________________________
 Discuss-gnuradio mailing list
  address@hidden
 lists.gnu.org lists.gnu.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20180131/a504b75e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: iqbal_test.grc
Type: application/gnuradio-grc
Size: 40628 bytes
Desc: not available
URL: <http://lists.gnu.org/archive/html/discuss-gnuradio/attachments/20180131/a504b75e/attachment.bin>

------------------------------

Message: 15
Date: Wed, 31 Jan 2018 10:11:15 -0500
From: Jeff Long <address@hidden>
To: discuss gnuradio <address@hidden>
Subject: Re: [Discuss-gnuradio] How to use IQ Bal Optimize/Fix?
Message-ID: <address@hidden>
Content-Type: text/plain; charset=utf-8; format=flowed

1. Add a throttle after the source.

2. You are feeding the optimizer and the balancer from the original
signal. They need to be connected to the output of the imbalance generator.

3. Whatever the scale of magnitude is in the imbalance generator, 1.0 is
too small to see on the time plot.

4. The time plots will look different if the phase is rotated, so
different is not necessarily wrong.

5. Add a slider to control magnitude, and you can see the optimizer adjust.



On 01/31/2018 09:21 AM, kokosz wrote:
> This is exactly what I am doing, but restored signal looks very weird
> (its real part is close to zero). I have attached example *grc file
> showing the problem.
>
> Dnia 31 stycznia 2018 12:34 Jeff Long <address@hidden> napisa?(a):
>
>     If you put 0 in the manual fields and wire
>
>      ?src->optimize->iqbal
>
>     and
>
>      ?src->iqbal
>
>     it seems to work fine. Do you have a GRC file?
>
>     "period" is some sort of time constant, in samples. If you set it to
>     samp_rate, optimization will happen within a second. Smaller values for
>     faster response up to a point.
>
>     On 01/31/2018 05:54 AM, kokosz wrote:
>
>         Dear all,
>
>         It looks like IQ imbalance is causing problems in my
>         application, as I
>         was able to simulate real-world-like problems after adding "IQ
>         Imbalance
>         Generator" to my GRC flowgraph. So, after simulating this
>         imbalance, I
>         wanted to get rid of it with the help of "IQ Bal Optimize" and
>         "IQ Bal
>         Fix" combo. Unfortunately, I can't get it work.
>
>         As far as I understand, "IQ Bal Optimize" is automatically
>         detecting
>         settings (i.e. magnitude and phase correction values) for "IQ
>         Bal Fix"
>         and pass it to the latter block via message connection called
>         "iqbal_corr". Is this is true, I don't understand why I have to
>         manually
>     

reply via email to

[Prev in Thread] Current Thread [Next in Thread]