Re: [Discuss-gnuradio] Pay You $$$ to Mentor Me - Tx OFDM 64 QAM and Rx Measure Error Vector Magnitude

[Ifly88]

I want to create a spread of 15khz sub carriers ( like LTE ) that fills up 
bandwidth of 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, and 20 MHz ( like LTE 
bandwidths ).  In the 1.4 MHz block there are 72 15 khz subcarriers, 180 in a 3 
MHz block, 300 in a 5 MHz, 600 in a 10 MHz, 900 in a 15 MHz, and 1200 in a 20 
MHz bandwidth.

The subcarriers are to be modulated with a constant QPSK, or 16 QAM or 64 QAM.  
A BladeRF or HackRF One will be used to measure and generate these signals.  
Preferably the HackRF because the BladeRF seems to be more unstable (locks up) 
in my experience.  May be bad code or hardware, not sure which one.

The goal is to test RF components to see if they are causing signal distortion. 
 In the past I had access to a LTE signal generator that would key up all 
sub-carriers with 64 quam and a LTE signal analyser that would measure EVM and 
that was a great way to see if a system could transmit 64 QAM without issue.  
If the EVM was over a certain X for 64 QAM, 16 QAM or QPSK then the components 
needed to be addressed.

Below is the chart that shows Bandwidth and Subcarriers in an LTE signal.

Thanks,
Andrew

Sent with [ProtonMail](https://protonmail.com) Secure Email.

>  Original Message 
> Subject: Re: [Discuss-gnuradio] Pay You $$$ to Mentor Me - Tx OFDM 64 QAM and 
> Rx Measure Error Vector Magnitude
> Local Time: September 24, 2017 3:54 PM
> UTC Time: September 24, 2017 8:54 PM
> From: marcus.muel...@ettus.com
> To: discuss-gnuradio@gnu.org
>
> HI IFly88,
>
> I don't fully understand your requirements – on one hand, you just say "I 
> just want OFDM with 15 kHz subcarrier spacing and QAM/QPSK inside", on the 
> other hand you mention LTE: an arbitrary OFDM signal with the right 
> subcarrier spacing and constellation mapping does not constitute a validly 
> measurable LTE signal. Your LTE receiver needs a lot of specific structure in 
> the frames to be able to synchronize, and equalize, to an LTE transmission.
>
> So, what exactly are you using to measure EVM? What is the higher level goal 
> of this? Your transmit hardware will always also play a part in the signal 
> quality you receive, so it's usually better to first sit down and contemplate 
> what you want to measure, then design a system.
>
> Best regards,
> Marcus
>
> On 09/23/2017 10:30 PM, Ifly88 wrote:
>
>> Name your price to give me pointers and help me kick start this project.  I 
>> want to emulate a 64qam, 16qam, and qpsk LTEs signal to test for signal 
>> impairments.  Basically take 15khz sub carriers over channel bandwidths of 
>> 1.4mhz to 20 mhz and modulate them with 64qam, 16qam, and qpsk.  I want to 
>> use another receiver to Rx the signal and calculate error vector magnitude 
>> for each of those three modulations.  I'll be using HackRF One radios or 
>> will use BladeRF if necessary.
>>
>> I'be been spinning my wheels for a few days trying to get this to work on 
>> GRC and need some guidance.
>>
>> Please help.
>> ifly88 at protonmail dot com
>>
>> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>>
>> ___
>> 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] [SOCIS '17] GRC C++ Output: Week 9

[Håkon Vågsether]

Hi all,

I have updated my blog for my next to last week, providing a demonstration
of my recent additions. The most important changes are the build options,
my yaml_blocks_python branch and last but not least, the ability to
generate QT flowgraphs in C++ with GRC! :)

You can read more at:

https://grccpp.wordpress.com

Best regards,
Håkon Vågsether
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] [SOCIS '17] GRC C++ Output: Week 8

[Håkon Vågsether]

Hello Piotr,

hmm, that certainly doesn't look like code I have touched, and I can't say
I have seen that error before either. I'm running Arch Linux (Python
3.6.2), hope that helps! :)

Best regards,
Håkon Vågsether

On Sun, Sep 24, 2017 at 4:27 PM, Piotr Krysik  wrote:

> W dniu 18.09.2017 o 11:10, Håkon Vågsether pisze:
> > Hi all,
> >
> > The focus for this week has been the QT blocks. You can read more at:
> >
> > https://grccpp.wordpress.com
> >
> > Best regards,
> > Håkon Vågsether
> Hi Håkon,
>
> I'm trying to compile and run according to the description but I got an
> error when trying to do "from gnuradio import gr". Gnuradio-companion
> also doesn't run because of this.
> Below is the full error message. My OS is Ubuntu 16.04. I don't want you
> to loose focus to debug this particular problem, but can you tell me
> what is your setup (mainly distro), where your version of GRC works fine?
>
>
> Python 3.5.2 (default, Aug 18 2017, 17:48:00)
> [GCC 5.4.0 20160609] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> from gnuradio import gr
> Traceback (most recent call last):
>   File "/usr/local/lib/python3.5/dist-packages/gnuradio/gr/__init__.py",
> line 39, in 
> from .runtime_swig import *
>   File
> "/usr/local/lib/python3.5/dist-packages/gnuradio/gr/runtime_swig.py",
> line 28, in 
> _runtime_swig = swig_import_helper()
>   File
> "/usr/local/lib/python3.5/dist-packages/gnuradio/gr/runtime_swig.py",
> line 24, in swig_import_helper
> _mod = imp.load_module('_runtime_swig', fp, pathname, description)
>   File "/usr/lib/python3.5/imp.py", line 242, in load_module
> return load_dynamic(name, filename, file)
>   File "/usr/lib/python3.5/imp.py", line 342, in load_dynamic
> return _load(spec)
> ImportError: dynamic module does not define module export function
> (PyInit__runtime_swig)
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "", line 1, in 
>   File "/usr/local/lib/python3.5/dist-packages/gnuradio/gr/__init__.py",
> line 43, in 
> from .runtime_swig import *
>   File
> "/usr/local/lib/python3.5/dist-packages/gnuradio/gr/runtime_swig.py",
> line 28, in 
> _runtime_swig = swig_import_helper()
>   File
> "/usr/local/lib/python3.5/dist-packages/gnuradio/gr/runtime_swig.py",
> line 24, in swig_import_helper
> _mod = imp.load_module('_runtime_swig', fp, pathname, description)
>   File "/usr/lib/python3.5/imp.py", line 242, in load_module
> return load_dynamic(name, filename, file)
>   File "/usr/lib/python3.5/imp.py", line 342, in load_dynamic
> return _load(spec)
> ImportError: dynamic module does not define module export function
> (PyInit__runtime_swig)
>
> Best Regards,
> Piotr Krysik
>
> ___
> 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] Pay You $$$ to Mentor Me - Tx OFDM 64 QAM and Rx Measure Error Vector Magnitude

[Marcus Müller]

HI IFly88,

I don't fully understand your requirements – on one hand, you just say
"I just want OFDM with 15 kHz subcarrier spacing and QAM/QPSK inside",
on the other hand you mention LTE: an arbitrary OFDM signal with the
right subcarrier spacing and constellation mapping does not constitute a
validly measurable LTE signal. Your LTE receiver needs a lot of specific
structure in the frames to be able to synchronize, and equalize, to an
LTE transmission.

So, what exactly are you using to measure EVM? What is the higher level
goal of this? Your transmit hardware will always also play a part in the
signal quality you receive, so it's usually better to first sit down and
contemplate what you want to measure, then design a system.

Best regards,
Marcus


On 09/23/2017 10:30 PM, Ifly88 wrote:
> Name your price to give me pointers and help me kick start this
> project.  I want to emulate a 64qam, 16qam, and qpsk LTEs signal to
> test for signal impairments.  Basically take 15khz sub carriers over
> channel bandwidths of 1.4mhz to 20 mhz and modulate them with 64qam,
> 16qam, and qpsk.  I want to use another receiver to Rx the signal and
> calculate error vector magnitude for each of those three modulations.
>  I'll be using HackRF One radios or will use BladeRF if necessary.
>
> I'be been spinning my wheels for a few days trying to get this to work
> on GRC and need some guidance.
>
> Please help.
> ifly88 at protonmail dot com
>
>
> Sent with ProtonMail  Secure Email.
>
>
>
> ___
> 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] osmocom_fft

[Hans Van Ingelgom]

Hello,

It's been a while since I was able to use gnuradio due to getting a son,
but I've finally found some time to reinstall everything using Pybombs.

I got almost everything to work, even fosphor. The only thing that gives me
issues is osmocom_fft.
Here is the traceback:


Traceback (most recent call last):
  File "/opt/gnuradio/bin/osmocom_fft", line 850, in 
main ()
  File "/opt/gnuradio/bin/osmocom_fft", line 846, in main
app = stdgui2.stdapp(app_top_block, "osmocom Spectrum Browser",
nstatus=1)
  File
"/opt/gnuradio/lib/python2.7/dist-packages/gnuradio/wxgui/stdgui2.py", line
46, in __init__
wx.App.__init__ (self, redirect=False)
  File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_core.py", line
8628, in __init__
self._BootstrapApp()
  File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_core.py", line
8196, in _BootstrapApp
return _core_.PyApp__BootstrapApp(*args, **kwargs)
  File
"/opt/gnuradio/lib/python2.7/dist-packages/gnuradio/wxgui/stdgui2.py", line
49, in OnInit
frame = stdframe (self.top_block_maker, self.title, self._nstatus)
  File
"/opt/gnuradio/lib/python2.7/dist-packages/gnuradio/wxgui/stdgui2.py", line
76, in __init__
self.panel = stdpanel (self, self, top_block_maker)
  File
"/opt/gnuradio/lib/python2.7/dist-packages/gnuradio/wxgui/stdgui2.py", line
98, in __init__
self.top_block = top_block_maker (frame, self, vbox, sys.argv)
  File "/opt/gnuradio/bin/osmocom_fft", line 255, in __init__
fft_rate=options.fft_rate)
  File
"/opt/gnuradio/lib/python2.7/dist-packages/gnuradio/wxgui/fftsink_nongl.py",
line 198, in __init__
self.win = fft_window(self, parent, size=size)
  File
"/opt/gnuradio/lib/python2.7/dist-packages/gnuradio/wxgui/fftsink_nongl.py",
line 331, in __init__
self.control_panel = control_panel(self)
  File
"/opt/gnuradio/lib/python2.7/dist-packages/gnuradio/wxgui/fftsink_nongl.py",
line 256, in __init__
wx.Panel.__init__(self, parent, -1, style=wx.SIMPLE_BORDER)
  File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_windows.py", line
68, in __init__
_windows_.Panel_swiginit(self,_windows_.new_Panel(*args, **kwargs))
wx._core.PyAssertionError: C++ assertion "m_window" failed at
../src/gtk/dcclient.cpp(2043) in DoGetSize(): GetSize() doesn't work
without window


My system is running kubuntu 17.04, that is a kde distribution. So I
suspect that some gui library package is not installed. Does anyone have a
idea on what is going wrong here?

Thanks in advance,
Hans Van Ingelgom.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Python Tutorial for MAC OS 10.12

[Michael Dickens]

Hi Luis Felipe - So section 3.1.5 is meant to show you some of the
functionality of GRC and Python scripting. GRC is used as the primary
means to create the flowgraph visually, and then to generate a Python
script that can be executed. In this specific case, the tutorial is
asking you to also edit the generated Python to show alternative
functionality -- editing lines 74-80 roughly. The resulting lines should
read like those found after the text "Thus we can go back and modify our
probe function with the if-else statement to give power to our friend.".
Note that the tutorial authors also made a copy of the generated Python
script ... original is "if_else.py", and they copy it to
"if_else_mod.py". I'd recommend doing so, to avoid overwriting from
within GRC.
Yet another item to notice is that if your file "if_else_mod.py" reads
like that found immediately after the text "Full code copied below:",
then it will rarely execute cleanly (when running via "python
if_else_mod.py" or the like; I'd actually recommend using "python2.7
if_else_mod.py" on Mac OS X, just to be clear). The error will read
something like:{{{
% python2.7 /tmp/if_else_mod.py
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib-
  /python2.7/threading.py", line 801, in __bootstrap_innerself.run()
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib-
  /python2.7/threading.py", line 754, in runself.__target(*self.__args, 
**self.__kwargs)
  File "/tmp/if_else_mod.py", line 81, in
  _variable_function_probe_0_probeself.set_ampl(.3)
  File "/tmp/if_else_mod.py", line 177, in set_ampl
self.analog_sig_source_x_1.set_amplitude(self.ampl)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib-
  /python2.7/site-packages/gnuradio/gr/hier_block2.py", line 92, in
  __getattr__return getattr(self._impl, name)
AttributeError: 'top_block_sptr' object has no attribute 
'analog_sig_source_x_1'}}}

The reason for the error is the changes made for this tutorial result in
a variable (self.analog_sig_source_x_1) being accessed before it is
created. A fix is to move the section of code with:{{{
def _variable_function_probe_0_probe():
[snip]
 _variable_function_probe_0_thread =
 threading.Thread(target=_variable_function_probe_0_probe) 
_variable_function_probe_0_thread.daemon = True
 _variable_function_probe_0_thread.start()
}}}
to just before the text "# QT sink close method reimplementation" and at
the same indentation level. The error comes about because the thread is
started (the last line), and the thread starts executing & then calls
"set_ampl" which in turn references the variable
"self.analog_sig_source_x_1" which won't be created until later in the
Python script from when this thread is started.
Hope this is useful (to you & others trying this tutorial). - MLD

On Sun, Sep 24, 2017, at 02:26 PM, Luis Felipe Albarracin Sanchez wrote:> I get 
o tried to do that "python  file" manually, but It did not work.
> Maybe I am doing it wrong. I opened opened a terminal in the folder
> where the python file is and I placed the manual commands that are on
> the tutorial, but the console shows an error. Do you know how to do
> this the rigth way?
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Python Tutorial for MAC OS 10.12

[Luis Felipe Albarracin Sanchez]

Hello everyone,

Thanks for the responses, they are helpful.

Michael, I get o tried to do that "python  file" manually, but It did not
work. Maybe I am doing it wrong. I opened opened a terminal in the folder
where the python file is and I placed the manual commands that are on the
tutorial, but the console shows an error. Do you know how to do this the
rigth way?

Thanks again.

El sept. 24, 2017 12:20 PM, "Michael Dickens" 
escribió:

> Hi Luis Felipe - OK; thanks for clarifying. When you click the button
> "generate the flowgraph", GRC creates the Python file -- overwriting
> anything that might be there already. So, any changes to the Python file
> are lost when you have GRC generate the flowgraph. Note that, at the very
> end of 3.1.5, you execute the (new) Python script by hand: "python
> if_else_mod.py". So, do the file edits, save the Python script, but -do
> not- click the button "generate the flowgraph". Hope this helps! - MLD
>
> On Sun, Sep 24, 2017, at 01:00 PM, Luis Felipe Albarracin Sanchez wrote:
>
> Thank you for the quick response,
>
> I think you are rigth,  i need to clarify better my problem,  i started
> from scratch the  Tutorial,  and i placed all blocks according to the
> Tutorial. After that i clicked on "generate the flowgraph". Once i did this
> in the folder where the GRC is saved Python file was created. I opened this
> file to edit it as proposed in the section 3.1.5 of the Tutorial and wrote
> the lines that in the tutorial said should be added to make Flowgraph work
> taking into account the two signals.  I did this, i wrote the new code i
> saved it on python (the same file), and then i clicked again on "Generate
> the flowgraph" hoping that the "flowgraph" will take the changes on the
> python files, but it did not happend; what it happend is that it created
> again a Python file overwritting the one the one that i did changes on. i
> am kind of lost. How can i make the flowgraphs to take Python script once
> it have change it?
>
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] New GR-SQL Module

[Ghost Op]

Hi everyone,

Back from GRCon2017 (one of the best conferences I've been to) and had
some time for some more module development.  During the conference in
one of the working sessions there was a suggestion for a module that
would allow you to query really large IQ files with a SQL-like syntax.

Made sense, 500 GB file but you only want a minute or two of the
sample rather than having to go through the whole thing.  So I put one
together and posted up on github
(https://github.com/ghostop14/gr-sql).

Basic to start.  Has a command-line tool called grsql (the readme has
some examples) to extract portions to a new file, and a flowgraph
block to play excerpt directly.

Basic syntax:

Get the total time length of a file:
grsql "select TIMELENGTH FROM '/tmp/myrecording_593MHz_6.2MSPS.raw'
ASDATATYPE complex SAMPLERATE 6.2M"

Extracting data from 45.2 seconds to 80 seconds into the save to a new file:
grsql "SELECT * FROM '/tmp/myrecording_593MHz_6.2MSPS.raw' ASDATATYPE
complex SAMPLERATE 6.2M STARTTIME 45.2 ENDTIME 80.0 SAVEAS
'/tmp/extracted.raw'"

In the flowgraph block, saveas doesn't apply but you can play specific
time ranges back directly from the flowgraph without needing to
extract from the file (if you're looking for a signal in the
recording).

If you're working on some blind analysis, if you extract a sample to a
new file, you may want to use the gr-filerepeater block up on my
github too.  It'll let you put delays between replays so that any
blocks looking for signal continuity won't get too "confused" by going
directly from the end of a sample immediately to the first sample
creating a weird signal discontinuity as it "jumps".  gr-filerepeater
will let it go "quiet" for a specified period of time so the blocks
can settle before trying to decode / demod again.

Anyway it's alpha/beta but it works.  If you run into any bugs or are
working with some big files and want any particular features, drop me
a note.  If all looks pretty solid and there's interest I can set up a
pull to integrate it into pybombs for an easier install.

Mike

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

Re: [Discuss-gnuradio] Python Tutorial for MAC OS 10.12

[Michael Dickens]

Hi Luis Felipe - OK; thanks for clarifying. When you click the button
"generate the flowgraph", GRC creates the Python file -- overwriting
anything that might be there already. So, any changes to the Python file
are lost when you have GRC generate the flowgraph. Note that, at the
very end of 3.1.5, you execute the (new) Python script by hand: "python
if_else_mod.py". So, do the file edits, save the Python script, but -do
not- click the button "generate the flowgraph". Hope this helps! - MLD
On Sun, Sep 24, 2017, at 01:00 PM, Luis Felipe Albarracin Sanchez wrote:> Thank 
you for the quick response,
> 
> I think you are rigth,  i need to clarify better my problem,  i
> started from scratch the  Tutorial,  and i placed all blocks according
> to the Tutorial. After that i clicked on "generate the flowgraph".
> Once i did this in the folder where the GRC is saved Python file was
> created. I opened this file to edit it as proposed in the section
> 3.1.5 of the Tutorial and wrote the lines that in the tutorial said
> should be added to make Flowgraph work taking into account the two
> signals.  I did this, i wrote the new code i saved it on python (the
> same file), and then i clicked again on "Generate the flowgraph"
> hoping that the "flowgraph" will take the changes on the python files,
> but it did not happend; what it happend is that it created again a
> Python file overwritting the one the one that i did changes on. i am
> kind of lost. How can i make the flowgraphs to take Python script once
> it have change it?
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Python Tutorial for MAC OS 10.12

[Kevin Reid]

On Sun, Sep 24, 2017 at 10:00 AM, Luis Felipe Albarracin Sanchez <
lfasanc...@gmail.com> wrote:

>  i started from scratch the  Tutorial,  and i placed all blocks according
> to the Tutorial. After that i clicked on "generate the flowgraph". Once i
> did this in the folder where the GRC is saved Python file was created. I
> opened this file to edit it as proposed in the section 3.1.5 of the
> Tutorial and wrote the lines that in the tutorial said should be added to
> make Flowgraph work taking into account the two signals.  I did this, i
> wrote the new code i saved it on python (the same file), and then i clicked
> again on "Generate the flowgraph" hoping that the "flowgraph" will take the
> changes on the python files, but it did not happend; what it happend is
> that it created again a Python file overwritting the one the one that i did
> changes on. i am kind of lost. How can i make the flowgraphs to take Python
> script once it have change it?
>

GNU Radio Companion does not ever read the Python file. The point of
modifying the Python file is to accomplish things that you *cannot* put
into GRC. Once you have modified it you need to keep it separately from GRC
and edit it by hand for any further changes you want to make.

One way to make this easier to deal with is to use hierarchical blocks so
that the parts that GRC can do are done in GRC, and the amount of
hand-maintained Python code is smaller. You can either have GRC make a
hierarchical block instead of a top block and use that from Python, or you
can write a hierarchical block containing your custom code and use that
from GRC.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Python Tutorial for MAC OS 10.12

[Luis Felipe Albarracin Sanchez]

Hello Michael,

Thank you for the quick response,

I think you are rigth,  i need to clarify better my problem,  i started
from scratch the  Tutorial,  and i placed all blocks according to the
Tutorial. After that i clicked on "generate the flowgraph". Once i did this
in the folder where the GRC is saved Python file was created. I opened this
file to edit it as proposed in the section 3.1.5 of the Tutorial and wrote
the lines that in the tutorial said should be added to make Flowgraph work
taking into account the two signals.  I did this, i wrote the new code i
saved it on python (the same file), and then i clicked again on "Generate
the flowgraph" hoping that the "flowgraph" will take the changes on the
python files, but it did not happend; what it happend is that it created
again a Python file overwritting the one the one that i did changes on. i
am kind of lost. How can i make the flowgraphs to take Python script once
it have change it?

Thanks again.

Kind regards.



On Sun, Sep 24, 2017 at 11:48 AM, Michael Dickens  wrote:

> Hi Luis Felipe - Nice to hear from another MacOS X user of GNU Radio;
> there are actually quite a few of us "out there"...
>
> Maybe you can clarify what you mean by "goes back to the original". Step
> 3.1.5 has you modify the GRC flowgraph, which will in turn generate an
> updated Python script; you view the changes in the Python script to get an
> idea of the connection between the GRC representation of a flowgraph and
> the Python version (among other connections). If you succeed in the GRC
> flowgraph changes, when you click the button "Generate the flow graph" then
> the flowgraph's Python script will be updated.
>
> I hope this is useful! If not, ask more questions! - MLD
>
> On Sun, Sep 24, 2017, at 12:00 PM, Luis Felipe Albarracin Sanchez wrote:
>
> Is mi first time here, and i am just learning about how to work  with
> GNURadio on MAC OS.
>
> I am following this tutorial:
>
> https://wiki.gnuradio.org/index.php/Guided_Tutorial_GNU_Radio_in_Python
>
> And when i reach the section 3.1.5,  i  rewrite the code and save it on
> Python, but once  i hit "Execute the flowgraph"  the code goes back to the
> original.
>
> Would anyone please tell me how can i execute the flowgraph and make the
> new code in python be accepted for the flowgraph.
>
>
>


-- 
Eng. Luis Felipe Albarracin
PMP
CCNA/CCDA/CCNP/CCDP/CCIP
ITIL v3 Foundation
Msc. Telematics / MBA
"Die Grenzen meiner Sprache bedeuten die Grenzen meiner Welt"
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Re: [Discuss-gnuradio] Python Tutorial for MAC OS 10.12

[Michael Dickens]

Hi Luis Felipe - Nice to hear from another MacOS X user of GNU Radio;
there are actually quite a few of us "out there"...
Maybe you can clarify what you mean by "goes back to the original". Step
3.1.5 has you modify the GRC flowgraph, which will in turn generate an
updated Python script; you view the changes in the Python script to get
an idea of the connection between the GRC representation of a flowgraph
and the Python version (among other connections). If you succeed in the
GRC flowgraph changes, when you click the button "Generate the flow
graph" then the flowgraph's Python script will be updated.
I hope this is useful! If not, ask more questions! - MLD

On Sun, Sep 24, 2017, at 12:00 PM, Luis Felipe Albarracin Sanchez wrote:> Is mi 
first time here, and i am just learning about how to work  with
> GNURadio on MAC OS.> 
> I am following this tutorial:
> 
> https://wiki.gnuradio.org/index.php/Guided_Tutorial_GNU_Radio_in_Python> 
> And when i reach the section 3.1.5,  i  rewrite the code and save it
> on Python, but once  i hit "Execute the flowgraph"  the code goes back
> to the original.> 
> Would anyone please tell me how can i execute the flowgraph and make
> the new code in python be accepted for the flowgraph.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

[Discuss-gnuradio] Python Tutorial for MAC OS 10.12

[Luis Felipe Albarracin Sanchez]

Hello everyone,

Is mi first time here, and i am just learning about how to work  with
GNURadio on MAC OS.

I am following this tutorial:

https://wiki.gnuradio.org/index.php/Guided_Tutorial_GNU_Radio_in_Python

And when i reach the section 3.1.5,  i  rewrite the code and save it on
Python, but once  i hit "Execute the flowgraph"  the code goes back to the
original.

Would anyone please tell me how can i execute the flowgraph and make the
new code in python be accepted for the flowgraph.

thanks in advance.

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

Re: [Discuss-gnuradio] [SOCIS '17] GRC C++ Output: Week 8

[Piotr Krysik]

W dniu 18.09.2017 o 11:10, Håkon Vågsether pisze:
> Hi all,
>
> The focus for this week has been the QT blocks. You can read more at:
>
> https://grccpp.wordpress.com
>
> Best regards,
> Håkon Vågsether
Hi Håkon,

I'm trying to compile and run according to the description but I got an
error when trying to do "from gnuradio import gr". Gnuradio-companion
also doesn't run because of this.
Below is the full error message. My OS is Ubuntu 16.04. I don't want you
to loose focus to debug this particular problem, but can you tell me
what is your setup (mainly distro), where your version of GRC works fine?


Python 3.5.2 (default, Aug 18 2017, 17:48:00)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from gnuradio import gr
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/gnuradio/gr/__init__.py",
line 39, in 
    from .runtime_swig import *
  File
"/usr/local/lib/python3.5/dist-packages/gnuradio/gr/runtime_swig.py",
line 28, in 
    _runtime_swig = swig_import_helper()
  File
"/usr/local/lib/python3.5/dist-packages/gnuradio/gr/runtime_swig.py",
line 24, in swig_import_helper
    _mod = imp.load_module('_runtime_swig', fp, pathname, description)
  File "/usr/lib/python3.5/imp.py", line 242, in load_module
    return load_dynamic(name, filename, file)
  File "/usr/lib/python3.5/imp.py", line 342, in load_dynamic
    return _load(spec)
ImportError: dynamic module does not define module export function
(PyInit__runtime_swig)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/local/lib/python3.5/dist-packages/gnuradio/gr/__init__.py",
line 43, in 
    from .runtime_swig import *
  File
"/usr/local/lib/python3.5/dist-packages/gnuradio/gr/runtime_swig.py",
line 28, in 
    _runtime_swig = swig_import_helper()
  File
"/usr/local/lib/python3.5/dist-packages/gnuradio/gr/runtime_swig.py",
line 24, in swig_import_helper
    _mod = imp.load_module('_runtime_swig', fp, pathname, description)
  File "/usr/lib/python3.5/imp.py", line 242, in load_module
    return load_dynamic(name, filename, file)
  File "/usr/lib/python3.5/imp.py", line 342, in load_dynamic
    return _load(spec)
ImportError: dynamic module does not define module export function
(PyInit__runtime_swig)

Best Regards,
Piotr Krysik

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