GNU Radio, One Step at a Time: August 2016

Wednesday, August 31, 2016

Re: [Discuss-gnuradio] USRP B200 Not Transmitting

Hello Hasini,

The USRP-users mailing list is an excellent place to ask such questions.
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

I do not have experience with the dpsk flowgraphs. Have you verified that you can see a simple sinewave from one B200 to another? uhd_fft and uhd_siggen_gui are excellent tools for testing that. When transmitting with the B200, do you see the TX LED come on and the RX LED on the other one?

Thanks,

Derek

On Wed, Aug 31, 2016 at 10:31 PM, Hasini Abeywickrama <hvabey@gmail.com> wrote:

Hi,

I have a USRP B200 set to transmit a signal (using uhd_tx_dpsk.grc in the GNURadio examples) and another USRP B200 receive the signal (using uhd_rx_dpsk.grc in the GNURadio examples). But the receiving USRP does not receive the signal that is being transmitted by the other USRP, even though they are placed very close to each other.

If I user a USRP2 as the transmitter the receiver can receive the signal without any issue.

Can someone please suggest what might be the problem with this. (Please excuse if this is not directly related to GNU Radio)

Cheers
Hasini

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

[Discuss-gnuradio] USRP B200 Not Transmitting

Hi,

I have a USRP B200 set to transmit a signal (using uhd_tx_dpsk.grc in the GNURadio examples) and another USRP B200 receive the signal (using uhd_rx_dpsk.grc in the GNURadio examples). But the receiving USRP does not receive the signal that is being transmitted by the other USRP, even though they are placed very close to each other.

If I user a USRP2 as the transmitter the receiver can receive the signal without any issue.

Can someone please suggest what might be the problem with this. (Please excuse if this is not directly related to GNU Radio)

Cheers

Hasini

[Discuss-gnuradio] The correct way to use FEC encoder/decoder in a flowgraph

Hi,

I have a working flowgraph which reads from a file, encodes it, modulates using PSK and transmits it via USRP. The receiving USRP can demodulate, decode and properly write the file at the other end. Now I am trying to add forward error correction to the flowgraph. I am using FEC encoder and decoder.

When I run it in the simulation mode ("fec_flowgraph.png") I was able to recover the file correctly at the other end. However, when I run it using USRP(as shown in fec_tx.png and fec_rx.png flowgraphs), it receives a lot of garbage and part of the file once in a while. I do not understand why that is happening. (I did not have any problem when running it without FEC encoder and decoder). I appreciate if you could help me to solve this issue.

Thank you,

Damindra

Damindra Savithri Bandara,

Ph.D. in Information Technology (Candidate)
George Mason University,
Fairfax,
Virginia

Re: [Discuss-gnuradio] Thrift bulding make Issus

On Wed, Aug 31, 2016 at 10:05 AM, Marcus Müller <marcus.mueller@ettus.com> wrote:

Whether the configure line is correct: yes, the options I'd expect are there. However, typically, thrift is a nightmare to configure, and analyzing the ./configure output most of the time lead me to disable further things (demos/tutorials/ruby bindings/...) explicitly.

After long trial and error this is what we've come up with as a configure line for thrift:

https://github.com/gnuradio/gr-recipes/blob/master/apache-thrift.lwr#L21

-Johnathan

Re: [Discuss-gnuradio] Thrift bulding make Issus

Hi Ihab,

You should *never* use sudo to run make; `sudo make install` might be appropriate. I don't see an error in your compile log, so maybe you'd need to explain the problem you're encountering in more detail?

I'd recommend deleting the source folder and cloning it again; it's now riddled with files that belong to root, and it'll be impossible for a non-root user to build it again.

Whether the configure line is correct: yes, the options I'd expect are there. However, typically, thrift is a nightmare to configure, and analyzing the ./configure output most of the time lead me to disable further things (demos/tutorials/ruby bindings/...) explicitly.

Best regards,
Marcus

On 08/31/2016 05:02 PM, Ihab Zine wrote:

Hi all,

after cloning the Apache Thrift and configured, i ran to a problem when ii tried to build it.

using the command : make ,

i got the following output :

/sdr/thrift$ sudo make

make all-recursive

make[1]: Entering directory '/home/compliance/sdr/thrift'

Making all in compiler/cpp

make[2]: Entering directory '/home/compliance/sdr/thrift/compiler/cpp'

make all-am

make[3]: Entering directory '/home/compliance/sdr/thrift/compiler/cpp'

make[3]: Nothing to be done for 'all-am'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/compiler/cpp'

make[2]: Leaving directory '/home/compliance/sdr/thrift/compiler/cpp'

Making all in lib

make[2]: Entering directory '/home/compliance/sdr/thrift/lib'

Making all in cpp

make[3]: Entering directory '/home/compliance/sdr/thrift/lib/cpp'

Making all in .

make[4]: Entering directory '/home/compliance/sdr/thrift/lib/cpp'

make[4]: Nothing to be done for 'all-am'.

make[4]: Leaving directory '/home/compliance/sdr/thrift/lib/cpp'

Making all in test

make[4]: Entering directory '/home/compliance/sdr/thrift/lib/cpp/test'

make[4]: Nothing to be done for 'all'.

make[4]: Leaving directory '/home/compliance/sdr/thrift/lib/cpp/test'

make[3]: Leaving directory '/home/compliance/sdr/thrift/lib/cpp'

Making all in py

make[3]: Entering directory '/home/compliance/sdr/thrift/lib/py'

/usr/bin/python setup.py build

/usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'use_2to3'

warnings.warn(msg)

running build

running build_py

running build_ext

make[3]: Leaving directory '/home/compliance/sdr/thrift/lib/py'

Making all in perl

make[3]: Entering directory '/home/compliance/sdr/thrift/lib/perl'

Making all in test

make[4]: Entering directory '/home/compliance/sdr/thrift/lib/perl/test'

make[4]: Nothing to be done for 'all'.

make[4]: Leaving directory '/home/compliance/sdr/thrift/lib/perl/test'

make[4]: Entering directory '/home/compliance/sdr/thrift/lib/perl'

make -f Makefile-perl.mk

make[5]: Entering directory '/home/compliance/sdr/thrift/lib/perl'

make[5]: Leaving directory '/home/compliance/sdr/thrift/lib/perl'

find blib -name 'Makefile*' -exec rm -f {} \;

make[4]: Leaving directory '/home/compliance/sdr/thrift/lib/perl'

make[3]: Leaving directory '/home/compliance/sdr/thrift/lib/perl'

make[3]: Entering directory '/home/compliance/sdr/thrift/lib'

make[3]: Nothing to be done for 'all-am'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/lib'

make[2]: Leaving directory '/home/compliance/sdr/thrift/lib'

Making all in test

make[2]: Entering directory '/home/compliance/sdr/thrift/test'

Making all in cpp

make[3]: Entering directory '/home/compliance/sdr/thrift/test/cpp'

make[3]: Nothing to be done for 'all'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/test/cpp'

Making all in perl

make[3]: Entering directory '/home/compliance/sdr/thrift/test/perl'

make[3]: Nothing to be done for 'all'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/test/perl'

Making all in py

make[3]: Entering directory '/home/compliance/sdr/thrift/test/py'

make[3]: Nothing to be done for 'all'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/test/py'

Making all in py.twisted

make[3]: Entering directory '/home/compliance/sdr/thrift/test/py.twisted'

make[3]: Nothing to be done for 'all'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/test/py.twisted'

Making all in py.tornado

make[3]: Entering directory '/home/compliance/sdr/thrift/test/py.tornado'

make[3]: Nothing to be done for 'all'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/test/py.tornado'

make[3]: Entering directory '/home/compliance/sdr/thrift/test'

make[3]: Nothing to be done for 'all-am'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/test'

make[2]: Leaving directory '/home/compliance/sdr/thrift/test'

Making all in tutorial

make[2]: Entering directory '/home/compliance/sdr/thrift/tutorial'

Making all in cpp

make[3]: Entering directory '/home/compliance/sdr/thrift/tutorial/cpp'

make[3]: Nothing to be done for 'all'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/tutorial/cpp'

Making all in py

make[3]: Entering directory '/home/compliance/sdr/thrift/tutorial/py'

make[3]: Nothing to be done for 'all'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/tutorial/py'

Making all in py.twisted

make[3]: Entering directory '/home/compliance/sdr/thrift/tutorial/py.twisted'

../../compiler/cpp/thrift --gen py:twisted -r ../../tutorial/tutorial.thrift

make[3]: Leaving directory '/home/compliance/sdr/thrift/tutorial/py.twisted'

Making all in py.tornado

make[3]: Entering directory '/home/compliance/sdr/thrift/tutorial/py.tornado'

make[3]: Nothing to be done for 'all'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/tutorial/py.tornado'

make[3]: Entering directory '/home/compliance/sdr/thrift/tutorial'

../compiler/cpp/thrift --gen html -r ../tutorial/tutorial.thrift

make[3]: Leaving directory '/home/compliance/sdr/thrift/tutorial'

make[2]: Leaving directory '/home/compliance/sdr/thrift/tutorial'

make[2]: Entering directory '/home/compliance/sdr/thrift'

make[2]: Leaving directory '/home/compliance/sdr/thrift'

make[1]: Leaving directory '/home/compliance/sdr/thrift'

what is the problem?

no indication for missing package, or error.

is it ok to configure it like this :

./configure --prefix=/usr/local. PY_PREFIX=$prefix --with-cpp --with-python CXXFLAGS="-DNDEBUG"

or it is wrong.

Regards

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

[Discuss-gnuradio] [SOCIS] Summary

Hi Everyone,

This is the final week of SOCIS, so I have written a brief summary of the

work I undertook and the outcomes:

https://signalsintelligence.wordpress.com/2016/08/31/socis-summary/

Cheers

Chris

Re: [Discuss-gnuradio] Updating SD Card Image on E310

On 08/31/2016 11:30 AM, Philip Balister wrote:
> GNURadio is installed in the usual place in /usr/.....
>
> Philip
Thanks, Philip! I didn't realize that a lot of those directories in
/home/root get created the first time you run GRC (including amending
PATH so you can launch GRC from the home directory).

--
__ __ ______ __ John Wood
/ |\ / /\ / ____ \ / /\ Code 5520
/ | ||/ / / / /\__/ /| / / / U.S. Naval Research Lab
/ /| |/ / / / /_/_/ / / / / / 4555 Overlook Avenue, SW
/ / | / / / ___ / / / / / Washington, DC 20375-5337
/ / /| / / / /\_| |\_/ / /_/_ (202) 767-2608
/_/ / |_/ / /_/ / |_|| /_____/\ (202) 767-1191 (FAX)
\_\/ \_\/ \_\/ \_\| \_____\/ e-mail: john.wood@nrl.navy.mil
WWW: http://www.itd.nrl.navy.mil

Hear and you forget; see and you remember; do and you understand.
Confucius

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

Re: [Discuss-gnuradio] Updating SD Card Image on E310

On 08/31/2016 10:40 AM, John B. Wood wrote:
> Hello, all. From the Ettus website I recently downloaded and extracted
> the "sdimage-gnuradio-demo.direct" file from the "ettus-e3xx-sg1" folder
> (appropriate for my E310 SN). I used dd to copy the image to a micro SD
> card without incident and installed it in the E310. The E310 boots fine
> and I have no trouble logging in via SSH. This release 4 image is
> supposed to have UHD 3.9.2 and GNU radio 3.7.9 but the only entries in
> my /home/root directory on the E310 are ".volk", ".bash-history" and
> .viminfo. All the other GNU radio and GRC stuff that was present in
> /home/root in my previous SD card image is absent. What have I
> forgotten? Thanks for any assistance you can provide.
>
>

GNURadio is installed in the usual place in /usr/.....

Philip

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

Re: [Discuss-gnuradio] Attribute error: and support with external class and header files

Hi Dave,

I don't know and am not sure if it is safe to use c++11 flag. But I needed it, and so far I don't see any problems.

Regards,

Pranav Padalkar

Fraunhofer-Institut für Eingebettete Systeme und Kommunikationstechnik ESK

From: Dave NotTelling <dmp250net@gmail.com>
Sent: Wednesday, August 31, 2016 1:59 PM
To: Pranav Padalkar
Cc: discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Attribute error: and support with external class and header files

Is it safe to add the c++11 flag? I was under the impression that the GNU Radio build system didn't use c++11 for a reason. If that's not the case then I'll start using c++11 too :D

On Tue, Aug 30, 2016 at 4:25 AM, Pranav Padalkar <pranav.padalkar@esk.fraunhofer.de> wrote:

Good Morning everyone,

I figured out how to add my own source files in GNURadio and also how to add support for external libraries, in my case it was for Protobuf. I will just write a note here, hoping that it will help someone in the future.

1. I placed all of my own .h and .cpp files in the "lib" folder of my module, along with the "impl.cc" files.

2. I edited "CMakeLists.txt" of the "lib" folder; in that I added all of my own .cpp file names in "Setup library" section in the statement " list(APPEND ...) ".

To add C++11 flag -

1. I edited "CMakeLists.txt" in the home folder of my module (i.e. gnuradio/gr-modulename/CMakeLists.txt); in that I added a command set(CMAKE_CXX_FLAGS "-std=c++11") in "Compiler specific setup" section after add_definitions().

To add external libraries, in my case Protobuf -

1. I edited "CMakeLists.txt" in the "lib" folder of my module.

2. In "Setup library" section, i added some commands to find the library I am looking for and then added them in "include_directories()" and in "link_directories()".

include(FindProtobuf)
find_package(Protobuf REQUIRED)

include_directories(${Boost_INCLUDE_DIR} ${Protobuf_INCLUDE_DIRS})
link_directories(${Boost_LIBRARY_DIRS} ${Protobuf_LIBRARIES})

target_link_libraries(gnuradio-modulename ${Boost_LIBRARIES} ${GNURADIO_ALL_LIBRARIES} ${Protobuf_LIBRARIES})

After doing this it works for me now and I don't get attribute error which was happening because of my source files and libraries not being linked.

Regards,

Pranav Padalkar
Fraunhofer-Institut für Eingebettete Systeme und Kommunikationstechnik ESK

From: Discuss-gnuradio <discuss-gnuradio-bounces+pranav.padalkar=esk.fraunhofer.de@gnu.org> on behalf of Pranav Padalkar <pranav.padalkar@esk.fraunhofer.de>
Sent: Wednesday, August 24, 2016 9:19 AM
To: Dave NotTelling
Cc: discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Attribute error: and support with external class and header files

Hi Dave,

Thanks for your reply. Actually I figured out the problem. After going through the files of the already existing blocks, especially the CMakeLists.txt, I figured out where I need to add my own header files. I added entries of all the class files in the CMakeLists.txt inside "lib" folder. I am not sure if this has solved the problem, but at least it is compiling now. Currently I am facing the problem of how to make the GnuRadio compiler to get the C++11 flag. I know it has to be added to the CMake file, but I am not sure where exactly. If anyone knows about this, then kindly let me know. I also need to include other libraries like pthread, libboost_filesystem, etc.

Thanks and Regards,

Pranav

Von: Dave NotTelling [mailto:dmp250net@gmail.com]
Gesendet: Dienstag, 23. August 2016 18:50
An: Pranav Padalkar
Cc: discuss-gnuradio@gnu.org
Betreff: Re: [Discuss-gnuradio] Attribute error: and support with external class and header files

I've had bad luck just putting my own headers in OOT modules. The way I do things now is to use gr_modtool add and select 'noblock'. Then just remove the grc XML file created. Seems that YourModuleName_API is needed before structs and classes or it doesn't get seen by Swig. Could be wrong about that. Might just work for me on a fluke =\

On Tue, Aug 23, 2016 at 6:47 AM, Pranav Padalkar <pranav.padalkar@esk.fraunhofer.de> wrote:

Hello all,

I have written a c++ code and I wish to implement as a block in GNURadio. I created a module (named "newblocks") and a block (named "my_client) and made appropriate changes. The thing is, I have many class and header files for my c++ code, for eg. Protobuf. I put those files in a folder called "client" inside "include" folder of my module (gr-newblocks/include/newblocks/client). It showed no error during cmake, make, make install and ldconfig. But when I put the block in the flowgraph and run it, it gives me following error.

File "/home/sdr/workspace/develop/Pranav/USRP_client/usrp_client.py", line 115, in __init__
self.newblocks_my_client_0 = newblocks.my_client("123", "8080")
AttributeError: 'module' object has no attribute 'my_client'

I already had a working block in the same module, which I had created earlier. And now even that block gives me same error. If I don't use any of the two blocks, the flowgraph works fine.

I, then, also added a CMakeLists.txt file in that "client" folder and entered all the .h and .c files in the text file. I added the entry for "client" folder in the "Add subdirectories" part of the CMakeLists.txt in (gr-newblocks/ ). Is there anything else I need to do in order to use my own class and header files? Do I also need to put the .o files along with the header and class files? I tried with both, putting the .o files and not putting them, it still shows the same error.

I even created a new module and a new block and copy pasted my code and header and class files. I still get the same error. I kindly ask for help in this regard. I am using Ubuntu 14.04 LTS, GnuRadio 3.7.9.2, I am using a lot of Boost 1.61.

Thank you in advance.

Best Regards,

Pranav Padalkar

Fraunhofer-Institut für Eingebettete Systeme und Kommunikationstechnik ESK

_______________________________________________
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] Updating SD Card Image on E310

Hello, all. From the Ettus website I recently downloaded and extracted
the "sdimage-gnuradio-demo.direct" file from the "ettus-e3xx-sg1" folder
(appropriate for my E310 SN). I used dd to copy the image to a micro SD
card without incident and installed it in the E310. The E310 boots fine
and I have no trouble logging in via SSH. This release 4 image is
supposed to have UHD 3.9.2 and GNU radio 3.7.9 but the only entries in
my /home/root directory on the E310 are ".volk", ".bash-history" and
.viminfo. All the other GNU radio and GRC stuff that was present in
/home/root in my previous SD card image is absent. What have I
forgotten? Thanks for any assistance you can provide.

--
__ __ ______ __ John Wood
/ |\ / /\ / ____ \ / /\ Code 5520
/ | ||/ / / / /\__/ /| / / / U.S. Naval Research Lab
/ /| |/ / / / /_/_/ / / / / / 4555 Overlook Avenue, SW
/ / | / / / ___ / / / / / Washington, DC 20375-5337
/ / /| / / / /\_| |\_/ / /_/_ (202) 767-2608
/_/ / |_/ / /_/ / |_|| /_____/\ (202) 767-1191 (FAX)
\_\/ \_\/ \_\/ \_\| \_____\/ e-mail: john.wood@nrl.navy.mil
WWW: http://www.itd.nrl.navy.mil

Hear and you forget; see and you remember; do and you understand.
Confucius

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

[Discuss-gnuradio] Thrift bulding make Issus

Hi all,

after cloning the Apache Thrift and configured, i ran to a problem when ii tried to build it.

using the command : make ,

i got the following output :

/sdr/thrift$ sudo make

make all-recursive

make[1]: Entering directory '/home/compliance/sdr/thrift'

Making all in compiler/cpp

make[2]: Entering directory '/home/compliance/sdr/thrift/compiler/cpp'

make all-am

make[3]: Entering directory '/home/compliance/sdr/thrift/compiler/cpp'

make[3]: Nothing to be done for 'all-am'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/compiler/cpp'

make[2]: Leaving directory '/home/compliance/sdr/thrift/compiler/cpp'

Making all in lib

make[2]: Entering directory '/home/compliance/sdr/thrift/lib'

Making all in cpp

make[3]: Entering directory '/home/compliance/sdr/thrift/lib/cpp'

Making all in .

make[4]: Entering directory '/home/compliance/sdr/thrift/lib/cpp'

make[4]: Nothing to be done for 'all-am'.

make[4]: Leaving directory '/home/compliance/sdr/thrift/lib/cpp'

Making all in test

make[4]: Entering directory '/home/compliance/sdr/thrift/lib/cpp/test'

make[4]: Nothing to be done for 'all'.

make[4]: Leaving directory '/home/compliance/sdr/thrift/lib/cpp/test'

make[3]: Leaving directory '/home/compliance/sdr/thrift/lib/cpp'

Making all in py

make[3]: Entering directory '/home/compliance/sdr/thrift/lib/py'

/usr/bin/python setup.py build

/usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'use_2to3'

warnings.warn(msg)

running build

running build_py

running build_ext

make[3]: Leaving directory '/home/compliance/sdr/thrift/lib/py'

Making all in perl

make[3]: Entering directory '/home/compliance/sdr/thrift/lib/perl'

Making all in test

make[4]: Entering directory '/home/compliance/sdr/thrift/lib/perl/test'

make[4]: Nothing to be done for 'all'.

make[4]: Leaving directory '/home/compliance/sdr/thrift/lib/perl/test'

make[4]: Entering directory '/home/compliance/sdr/thrift/lib/perl'

make -f Makefile-perl.mk

make[5]: Entering directory '/home/compliance/sdr/thrift/lib/perl'

make[5]: Leaving directory '/home/compliance/sdr/thrift/lib/perl'

find blib -name 'Makefile*' -exec rm -f {} \;

make[4]: Leaving directory '/home/compliance/sdr/thrift/lib/perl'

make[3]: Leaving directory '/home/compliance/sdr/thrift/lib/perl'

make[3]: Entering directory '/home/compliance/sdr/thrift/lib'

make[3]: Nothing to be done for 'all-am'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/lib'

make[2]: Leaving directory '/home/compliance/sdr/thrift/lib'

Making all in test

make[2]: Entering directory '/home/compliance/sdr/thrift/test'

Making all in cpp

make[3]: Entering directory '/home/compliance/sdr/thrift/test/cpp'

make[3]: Nothing to be done for 'all'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/test/cpp'

Making all in perl

make[3]: Entering directory '/home/compliance/sdr/thrift/test/perl'

make[3]: Nothing to be done for 'all'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/test/perl'

Making all in py

make[3]: Entering directory '/home/compliance/sdr/thrift/test/py'

make[3]: Nothing to be done for 'all'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/test/py'

Making all in py.twisted

make[3]: Entering directory '/home/compliance/sdr/thrift/test/py.twisted'

make[3]: Nothing to be done for 'all'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/test/py.twisted'

Making all in py.tornado

make[3]: Entering directory '/home/compliance/sdr/thrift/test/py.tornado'

make[3]: Nothing to be done for 'all'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/test/py.tornado'

make[3]: Entering directory '/home/compliance/sdr/thrift/test'

make[3]: Nothing to be done for 'all-am'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/test'

make[2]: Leaving directory '/home/compliance/sdr/thrift/test'

Making all in tutorial

make[2]: Entering directory '/home/compliance/sdr/thrift/tutorial'

Making all in cpp

make[3]: Entering directory '/home/compliance/sdr/thrift/tutorial/cpp'

make[3]: Nothing to be done for 'all'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/tutorial/cpp'

Making all in py

make[3]: Entering directory '/home/compliance/sdr/thrift/tutorial/py'

make[3]: Nothing to be done for 'all'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/tutorial/py'

Making all in py.twisted

make[3]: Entering directory '/home/compliance/sdr/thrift/tutorial/py.twisted'

../../compiler/cpp/thrift --gen py:twisted -r ../../tutorial/tutorial.thrift

make[3]: Leaving directory '/home/compliance/sdr/thrift/tutorial/py.twisted'

Making all in py.tornado

make[3]: Entering directory '/home/compliance/sdr/thrift/tutorial/py.tornado'

make[3]: Nothing to be done for 'all'.

make[3]: Leaving directory '/home/compliance/sdr/thrift/tutorial/py.tornado'

make[3]: Entering directory '/home/compliance/sdr/thrift/tutorial'

../compiler/cpp/thrift --gen html -r ../tutorial/tutorial.thrift

make[3]: Leaving directory '/home/compliance/sdr/thrift/tutorial'

make[2]: Leaving directory '/home/compliance/sdr/thrift/tutorial'

make[2]: Entering directory '/home/compliance/sdr/thrift'

make[2]: Leaving directory '/home/compliance/sdr/thrift'

make[1]: Leaving directory '/home/compliance/sdr/thrift'

what is the problem?

no indication for missing package, or error.

is it ok to configure it like this :

./configure --prefix=/usr/local. PY_PREFIX=$prefix --with-cpp --with-python CXXFLAGS="-DNDEBUG"

or it is wrong.

Regards

Ihab

[Discuss-gnuradio] Updating SD Card Image on E310

Re: [Discuss-gnuradio] Attribute error: and support with external class and header files

Is it safe to add the c++11 flag? I was under the impression that the GNU Radio build system didn't use c++11 for a reason. If that's not the case then I'll start using c++11 too :D

On Tue, Aug 30, 2016 at 4:25 AM, Pranav Padalkar <pranav.padalkar@esk.fraunhofer.de> wrote:

Good Morning everyone,

I figured out how to add my own source files in GNURadio and also how to add support for external libraries, in my case it was for Protobuf. I will just write a note here, hoping that it will help someone in the future.

1. I placed all of my own .h and .cpp files in the "lib" folder of my module, along with the "impl.cc" files.

2. I edited "CMakeLists.txt" of the "lib" folder; in that I added all of my own .cpp file names in "Setup library" section in the statement " list(APPEND ...) ".

To add C++11 flag -

1. I edited "CMakeLists.txt" in the home folder of my module (i.e. gnuradio/gr-modulename/CMakeLists.txt); in that I added a command set(CMAKE_CXX_FLAGS "-std=c++11") in "Compiler specific setup" section after add_definitions().

To add external libraries, in my case Protobuf -

1. I edited "CMakeLists.txt" in the "lib" folder of my module.

2. In "Setup library" section, i added some commands to find the library I am looking for and then added them in "include_directories()" and in "link_directories()".

include(FindProtobuf)
find_package(Protobuf REQUIRED)

include_directories(${Boost_INCLUDE_DIR} ${Protobuf_INCLUDE_DIRS})
link_directories(${Boost_LIBRARY_DIRS} ${Protobuf_LIBRARIES})

target_link_libraries(gnuradio-modulename ${Boost_LIBRARIES} ${GNURADIO_ALL_LIBRARIES} ${Protobuf_LIBRARIES})

After doing this it works for me now and I don't get attribute error which was happening because of my source files and libraries not being linked.

Regards,

Pranav Padalkar
Fraunhofer-Institut für Eingebettete Systeme und Kommunikationstechnik ESK

From: Discuss-gnuradio <discuss-gnuradio-bounces+pranav.padalkar=esk.fraunhofer.de@gnu.org> on behalf of Pranav Padalkar <pranav.padalkar@esk.fraunhofer.de>
Sent: Wednesday, August 24, 2016 9:19 AM
To: Dave NotTelling
Cc: discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Attribute error: and support with external class and header files

Hi Dave,

Thanks for your reply. Actually I figured out the problem. After going through the files of the already existing blocks, especially the CMakeLists.txt, I figured out where I need to add my own header files. I added entries of all the class files in the CMakeLists.txt inside "lib" folder. I am not sure if this has solved the problem, but at least it is compiling now. Currently I am facing the problem of how to make the GnuRadio compiler to get the C++11 flag. I know it has to be added to the CMake file, but I am not sure where exactly. If anyone knows about this, then kindly let me know. I also need to include other libraries like pthread, libboost_filesystem, etc.

Thanks and Regards,

Pranav

Von: Dave NotTelling [mailto:dmp250net@gmail.com]
Gesendet: Dienstag, 23. August 2016 18:50
An: Pranav Padalkar
Cc: discuss-gnuradio@gnu.org
Betreff: Re: [Discuss-gnuradio] Attribute error: and support with external class and header files

I've had bad luck just putting my own headers in OOT modules. The way I do things now is to use gr_modtool add and select 'noblock'. Then just remove the grc XML file created. Seems that YourModuleName_API is needed before structs and classes or it doesn't get seen by Swig. Could be wrong about that. Might just work for me on a fluke =\

On Tue, Aug 23, 2016 at 6:47 AM, Pranav Padalkar <pranav.padalkar@esk.fraunhofer.de> wrote:

Hello all,

I have written a c++ code and I wish to implement as a block in GNURadio. I created a module (named "newblocks") and a block (named "my_client) and made appropriate changes. The thing is, I have many class and header files for my c++ code, for eg. Protobuf. I put those files in a folder called "client" inside "include" folder of my module (gr-newblocks/include/newblocks/client). It showed no error during cmake, make, make install and ldconfig. But when I put the block in the flowgraph and run it, it gives me following error.

File "/home/sdr/workspace/develop/Pranav/USRP_client/usrp_client.py", line 115, in __init__
self.newblocks_my_client_0 = newblocks.my_client("123", "8080")
AttributeError: 'module' object has no attribute 'my_client'

I already had a working block in the same module, which I had created earlier. And now even that block gives me same error. If I don't use any of the two blocks, the flowgraph works fine.

I, then, also added a CMakeLists.txt file in that "client" folder and entered all the .h and .c files in the text file. I added the entry for "client" folder in the "Add subdirectories" part of the CMakeLists.txt in (gr-newblocks/ ). Is there anything else I need to do in order to use my own class and header files? Do I also need to put the .o files along with the header and class files? I tried with both, putting the .o files and not putting them, it still shows the same error.

I even created a new module and a new block and copy pasted my code and header and class files. I still get the same error. I kindly ask for help in this regard. I am using Ubuntu 14.04 LTS, GnuRadio 3.7.9.2, I am using a lot of Boost 1.61.

Thank you in advance.

Best Regards,

Pranav Padalkar

Fraunhofer-Institut für Eingebettete Systeme und Kommunikationstechnik ESK

_______________________________________________
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

Tuesday, August 30, 2016

[Discuss-gnuradio] Duplicate GRC documentation

Hi,

I'm just wondering if anyone might have any idea why I would be getting duplicate GRC documentation for my vis3d block @ https://github.com/chrisruk/gr-inspector/tree/dev_amc

You can see how the repeated documentation looks in GRC, at the bottom of this e-mail.

I've removed any other doxygen style comments in my .cc/.h files as far as I can tell, so can't really understand what's causing this.

Cheers

Chris

----

vis3d_vf
make(int vlen, int width, int height, int gwidth, int gheight, double maxz, int fps, char * xaxis, char * yaxis, char * zaxis, QWidget * parent=None) -> vis3d_vf_sptr
        3D visualisation for the inspector toolkit
        This GUI uses QwtPlot3D to visualise data in 3D, for instance data from the gr-specest FAM block.
        Controls: Hold left mouse button and move cursor to rotate. Dragging using two fingers, zooms in or out
        Constructor Specific Documentation:
        Build a 3D visualisation.
        Args:
            vlen : The size of the input vector containing the data to be displayed
            width : The 1D vector will be reshaped with this width
            height : The 1D vector will be reshaped with this height
            gwidth : The graph will be stretched to this width
            gheight : The graph will be stretched to this height
            maxz : You can set the graph to have a maximum Z value, so that the graph boundaries remain fixed, or if you set to 0, the Z axis of the graph, will grow according to the data.
            fps : You can set the framerate of the graph, so that if a higher number vectors are received than the frame rate, they can be discarded.
            xaxis : Label for X axis
            yaxis : Label for Y axis
            zaxis : Label for Z axis
            parent : QWidget parent

vis3d_vf_make
vis3d_vf_make(int vlen, int width, int height, int gwidth, int gheight, double maxz, int fps, char * xaxis, char * yaxis, char * zaxis, QWidget * parent=None) -> vis3d_vf_sptr
    3D visualisation for the inspector toolkit
    This GUI uses QwtPlot3D to visualise data in 3D, for instance data from the gr-specest FAM block.
    Controls: Hold left mouse button and move cursor to rotate. Dragging using two fingers, zooms in or out
    Constructor Specific Documentation:
    Build a 3D visualisation.
    Args:
        vlen : The size of the input vector containing the data to be displayed
        width : The 1D vector will be reshaped with this width
        height : The 1D vector will be reshaped with this height
        gwidth : The graph will be stretched to this width
        gheight : The graph will be stretched to this height
        maxz : You can set the graph to have a maximum Z value, so that the graph boundaries remain fixed, or if you set to 0, the Z axis of the graph, will grow according to the data.
        fps : You can set the framerate of the graph, so that if a higher number vectors are received than the frame rate, they can be discarded.
        xaxis : Label for X axis
        yaxis : Label for Y axis
        zaxis : Label for Z axis
        parent : QWidget parent

Re: [Discuss-gnuradio] Microwave Link Demodulation

Hi all,

Thanks for the tips. ill go through them and come back to you soon.

Best Regards

Ihab

On 29 August 2016 at 20:53, Ben Hilburn <bhilburn@gnuradio.org> wrote:

Hi Ihab -

I recommend checking out this paper on performance counters & ctrlport. The dependency on `thrift` can be a bit painful, but these are great tools in GNU Radio for instrumenting your application and optimizing performance.

http://conferences.sigcomm.org/sigcomm/2013/papers/srif/p65.pdf

Cheers,
Ben

On Mon, Aug 29, 2016 at 12:38 PM, Dave NotTelling <dmp250net@gmail.com> wrote:
One way I check for bottlenecks it to run 'top -H' and watch the various threads. If you see any one thread pegged at 100% then it needs to be optimized. At least that's my method :)

On Mon, Aug 29, 2016 at 9:46 AM, Ihab Zine <ihab.zine13@gmail.com> wrote:
Hi Marcus,

I have been through the GNU RADIO tutorials , I also dived into adapting gr-dvbt, and it worked for me. But how can i find out where my transceiver BER bottlenecks and where my computational bottlenecks come from? Is the a method or steps i can follow? I need some hints on this.

Best Regards
Ihab

On 24 August 2016 at 15:12, Ihab Zine <ihab.zine13@gmail.com> wrote:
Hi Ron and Marcus,

For frequency higher than 6 Ghz, a down converter can be used to over come this problem.

for the data rate and bandwidth, the PC i'm using has the following specifications:

Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 20
On-line CPU(s) list: 0-19
Thread(s) per core: 2
Core(s) per socket: 10
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 63
Model name: Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz
Stepping: 2
CPU MHz: 1553.804
CPU max MHz: 3300.0000
CPU min MHz: 1200.0000
BogoMIPS: 5197.32
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 25600K
NUMA node0 CPU(s): 0-19

I think it can handle this rate. Please correct me if i'm Wrong.

i have other questions:

There are (synchronizers, equalizers, channel codes etc) blocks in the gr-dvbt project why I cant use them?
when you mentioned channel coding do you mean that i need to create a new one? and Why would I need it?
If i need BCH performance Why is difficult to achieve?
if the data requirement is fine (CPU and etc), what is the best way to start building the receiver? How can I figure out the blocks That i need for this receiver?

Regards
Ihab

On 23 August 2016 at 14:34, Ihab Zine <ihab.zine13@gmail.com> wrote:
Hi Ron,

1) Frequency range: 1.5 - 38 GHz

2) Bandwidth range : 2 - 56 MHz

3) Modulation : Qpsk - 256 QAM

4) Data rate range : 150Mbit/s - 326Mbit/s.

5) Error correction method : i thinks it is FEC.

Ihab

On 22 August 2016 at 12:33, Ihab Zine <ihab.zine13@gmail.com> wrote:
Hi All,

I'm working on a project using GnuRadio And USRP 205 mini, i'm at the stage where i need to demodulate a microwave link signal.

Anyone has an experience with Microwave link or tried to do something similar? Is it possiable to do it in gnuradio? or is there another approaches to do it?

I'd appreciate any information you could give me.

Thanks
Ihab

_______________________________________________
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] Using GRC generated python code inside a C++ code

Hi, thanks for your help.

I managed to do it by creating an OOT module. I implemented my client C++ code in the block impl.cc file and also added my other source files. I had some problems in that area, but then I managed to solve it, as I discussed in another thread. I implemented messaging passing, created a message output port in my block and used the control port of the UHD:USRP sink block. It works like a charm. With just a couple of commands from my server, I can now control the USRP which is at the client side, using TCP.

Thanks a lot again.

Regards,

Pranav Padalkar

Fraunhofer-Institut für Eingebettete Systeme und Kommunikationstechnik ESK

From: Discuss-gnuradio <discuss-gnuradio-bounces+pranav.padalkar=esk.fraunhofer.de@gnu.org> on behalf of Pranav Padalkar <pranav.padalkar@esk.fraunhofer.de>
Sent: Monday, August 22, 2016 9:48 AM
To: Marcus Müller; discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Using GRC generated python code inside a C++ code

Thanks a lot Marcus,

Thanks for pointing me towards feval and message passing. We have decided to implement an OOT module, which will then control some of the blocks from the flowgraph. Message passing will definitely come handy. I will let you know how it works.

Regards,

Pranav.

From: Discuss-gnuradio <discuss-gnuradio-bounces+pranav.padalkar=esk.fraunhofer.de@gnu.org> on behalf of Marcus Müller <marcus.mueller@ettus.com>
Sent: Friday, August 19, 2016 3:21 PM
To: discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Using GRC generated python code inside a C++ code

have a look at the feval class [1]; it's a way to call python code from C++ land, and vice versa.

Be very careful about multithreading – all the GNU Radio blocks run in their own thread, so does the GNU Radio scheduler, and just executing python while python is executing might have interesting effects!

My approach would probably be to write a Python sync block with 0 in and 0 stream outputs, and connect that to the blocks you want to control with message passing as far as possible (UHD source has a command message interface, so this would work nicely), and call the python top_block's set_variable() methods only when impossible to avoid. In fact, things can be pretty easy: The ZeroMQ message sources can accept zeromq messages, and you could directly connect them to the message control ports of the blocks, so no need to write your own GNU Radio blocks at all; just use #include <pmt/pmt.h>/pmt::pmt_t and ZeroMQ in your C++ code to send messages directly across network/IPC/intra-process queues to your Flow graph.

Best regards,

Marcus

[1] http://gnuradio.org/doc/doxygen/classgr_1_1feval.html

On 19.08.2016 14:07, Pranav Padalkar wrote:

Hi Sebastian,

Thanks for your reply. In the meanwhile I was going through some documents on embedding Python in C++. I liked the idea of having a python code embedded in my client c++ code. But I think access data variables from the gnuradio code (for eg centre freq, bw, gain, etc) will be difficult. Because I want to set them from my client c++ code. I am still searching for other options, but so far python embedding seems good. Will let you know how it works.

If others have any other options, please let me know.

Thanks!

Pranav
From: Koslowski, Sebastian (CEL) <sebastian.koslowski@kit.edu>
Sent: Friday, August 19, 2016 1:15 PM
To: Pranav Padalkar; discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Using GRC generated python code inside a C++ code
Well, there a number of options. Given your description its hard to say which one is best.
Aside from maintainability and flexibility of the system, it really depends on the required interaction between the components.
You could
    - re-implement the fg in C++.
    - create Python bindings for your C++ client (e.g. with swig) and do the integration/coupling in Python (outside of the fg)
    - embed Python in your C++ client (https://docs.python.org/2/extending/embedding.html)
    - simply run the Python interpreter as a sub-process if the C++ client

If you choose 2, 3 or anything not the list let me know how it worked out =)

Sebastian

On 08/19/2016 10:02 AM, Pranav Padalkar wrote:
Hello,

I have a GRC generated python code. I also wrote a server-client code in C++. I want to implement the client-code along with the GNU python code. The essence is that I want to a run a client C++ code, which will call the python code in a thread and start the USRP to receive/transmit data, and continue performing it's own process in another thread. I am not sure how I could go about this. I also considered implementing the client C++ code as module in GNU radio and use it in the flow graph. But I think that's not how a client background code should run.

Any thoughts on this matter would be helpful. Thanks in advance.

Best Regards,

Pranav Padalkar
Fraunhofer-Institut für Eingebettete Systeme und Kommunikationstechnik ESK

Hansastraße 32 | 80686 München

Telefon, Fax: +49 89 547088-0 | +49 89 547088-220

E-Mail: pranav.padalkar@esk.fraunhofer.de

Internet:

http://www.esk.fraunhofer.de

http://www.twitter.com/FraunhoferESK

http://www.facebook.com/FraunhoferESK
_______________________________________________ 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 