Re: [USRP-users] How to find and link OOT module with gnuradio 3.8?

[EJ Kreinar]

Ron,

Yes, that looks right on target with my results... A little baffling to me
though... linking against OOTs seems like a fairly standard use case but
maybe it's less common than I thought. It's definitely needed for rfnoc
though.


Mohamed Yaaseen,

The change that worked for me was to update GR_CMAKE_DIR in gr-ettus to
${CMAKE_MODULES_DIR)/gnuradio-ettus. Then I rebuilt and installed gr-ettus,
and my OOT could then call find_package(gnuradio-ettus) and link against
gnuradio-ettus.

But I'm really not a cmake expert in any way, so I don't know if this is
the "right" answer. Personally I'm satisfied with the GR_CMAKE_DIR change,
but it does change the package name for downstream users...

I guess the broader question is then... What is "desired" behavior provided
by default from gr_modtool for finding and linking OOTs?

EJ

On Tue, Jun 30, 2020, 10:53 AM Mohamed Yaaseen 
wrote:

> Hello EJ Kreinar,
>
> I just came across this situation. I was trying to create a rfnoc gain
> tutorial oot module using rfnomodtools. But, when I was doing cmake I got
> some errors with respect to find_package(ettus).
> I was just fiddling around with cmakefiles as I am not familiar with cmake
> and stuff.
>
> But, I found a problem with the gr-ettus module itself. In the gr-ettus
> module ettutsConfig.cmake file, there is a line
> *include("${CMAKE_CURRENT_LIST_DIR}/ettusTarget.cmake"). *
> This is the file that rfnoc OOT searches in order to find the
> package ettus. But, while make && make install gr-ettus module installs 
> *gnuradio-ettusTargets.cmake
> *file at the location. Hence, rfnoc OOT module throws an error message
> during cmake.
>
> When I corrected the line in gr-ettus and reinstalled it, my OOT module
> was able to compile  successfully.
>
> But, I am now facing errors during the make process.
>
> I believe the rfnocmodtools template code present inside gr-ettus has not
> been migrated for 3.8 even though gr-ettus is migrated.
>
> In the meantime I will also try to fix the error which is thrown during
> make process. And update you in this thread if I have any success
>
> If you are able to get past the make process also and install it in gr
> 3.8. It would be really great...!!!
>
> Regards,
> Mohamed Yaaseen
>
> On Tue, 30 Jun 2020 at 16:01, EJ Kreinar via USRP-users <
> usrp-us...@lists.ettus.com> wrote:
>
>> Hi gnuradio and usrp-users,
>>
>> I'm trying to update rfnoc OOT modules for gnuradio 3.8 (gasp).
>>
>> But I'm having trouble finding and linking to gr-ettus specifically, and
>> I wonder how we're supposed to call find_package() and then link to
>> OOT modules in general with the updated cmake workflow... Trying to find
>> and link gr-ettus, I've tried a few things...
>>
>> 1) find_package(ettus)
>>
>> I believe this worked against gnuradio-3.7. Now, I get the following
>> error during cmake configure...
>>
>> ```
>> --   No package 'ettus' found
>> CMake Error at /usr/local/lib/cmake/ettus/ettusConfig.cmake:41 (include):
>>   include could not find load file:
>> /usr/local/lib/cmake/ettus/ettusTarget.cmake
>> ```
>>
>> 2) find_package(gnuradio-ettus)
>>
>> This seems more promising, since GR_LIBRARY_FOO seems to
>> install gnuradio-ettus cmake files into the lib/cmake/ettus install
>> location. This fails in cmake configure with the following error:
>>
>> ```
>> CMake Error at gr-theseus/CMakeLists.txt:84 (find_package):
>>   By not providing "Findgnuradio-ettus.cmake" in CMAKE_MODULE_PATH this
>>   project has asked CMake to find a package configuration file provided by
>>   "gnuradio-ettus", but CMake did not find one.
>>
>>   Could not find a package configuration file provided by "gnuradio-ettus"
>>   with any of the following names:
>>
>> gnuradio-ettusConfig.cmake
>> gnuradio-ettus-config.cmake
>>
>>   Add the installation prefix of "gnuradio-ettus" to CMAKE_PREFIX_PATH or
>> set
>>   "gnuradio-ettus_DIR" to a directory containing one of the above files.
>> If
>>   "gnuradio-ettus" provides a separate development package or SDK, be
>> sure it
>>   has been installed.
>> ```
>>
>>
>> Interestingly, if I change the GR_CMAKE_DIR *inside gr-ettus* to point to
>> ${CMAKE_MODULES_DIR)/gnuradio-ettus (
>> https://github.com/EttusResearch/gr-ettus/blob/b69260655e974786ea6e611bd91ab578b13ec72a/CMakeLists.txt#L69),
>> then the gnuradio-ettus cmake modules get installed to
>> lib/cmake/gnuradio-ettus. Then, in my OOT module, calling
>> find_package(gnuradio-ettus) finds gr-ettus, and
>> target_link_libraries( gnuradio-ettus) links successfully.
>>
>> So: Is this right? Am I missing something obvious here? Should gnuradio
>> OOT modules set their GR_CMAKE_DIR to gnuradio-?
>>
>> Thanks for the help!
>> EJ
>>
>> ___
>> USRP-users mailing list
>> usrp-us...@lists.ettus.com
>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>
>

Re: Making C++ OOT module and wish to set up a parameter with different choices!

[Ron Economos]

It's done in the .yml file in gr-foo/grc. Here's a simple example:

https://github.com/gnuradio/gnuradio/blob/master/gr-analog/grc/analog_sig_source_x.block.yml#L6

And a more complex example:

https://github.com/gnuradio/gnuradio/blob/master/gr-dtv/grc/dtv_dvb_ldpc_bb.block.yml

If you use a definition from an additional project .h file, that .h file 
must be included in gr-foo/swig/foo_swig.i.


Ron

On 6/30/20 10:05, George Edwards wrote:

Hello,

I am making a C++ OOT module and wish to have an input parameter 
"frame_length" with different choices. I would like to provide short, 
medium and long frames with a value attached to each. Based on the OOT 
syntax, I can enter "frame_length" as an input argument to the model. 
Now, how can I set  up the inners of the *.cc file so that when the 
module is built into a Gnuradio block, I can simply click on 
'frame_length' to see the choices and select one?


Thanks for the help.

Regards,
George

Re: How to add Documentation description in C++ OOT module

[Ron Economos]

You put it in the .h file(s) in gr-foo/include/foo (where foo is the 
name of your OOT). Here's an example:


https://github.com/gnuradio/gnuradio/blob/master/gr-dtv/include/gnuradio/dtv/dvb_ldpc_bb.h

Ron

On 6/30/20 09:44, George Edwards wrote:

Hello,

I am making a C++ OOT module and would like to add Documentation 
description similar to if I were to open a Gnuradio block, I can go to 
the Documentation and read the description of how the block works.


Thanks for any help you can provide.

Regards,
George

Re: GSoC 2020: gr-dpd - New BlogPost for Week 6

[Cinaed Simson]

Hi Alekh - does gr-dpd play nicely with gnuradio 3.8?

-- Cinaed

On 6/30/20 11:17 AM, Alekh wrote:


Hello community!!

I have updated my new blogpost 
 
for last week updates regarding the gr-dpd 
 module on my blog 
.


Major week highlights are:

- Addition of 'cmd' port to the signal_source block in GNU Radio 
source tree.


- Updation of gain_phase_calibrate and stream_to_gmp_vector block to 
fix bugs and improve performance.


- Addition of gain_phase_test flowgraphs.

- Updation of copyright lines of all the code files of the gr-dpd 
 repository.


Upcoming Week tasks are:

  * Updation of the GRC IO port labels of /gr-dpd/ blocks to improve
their understanding and use while using in flowgraphs.
  * Addition of the functionality for runtime updation of MP and GMP
model PA coefficients as block parameters.
  * Bug fixes in the gr-dpd to improve its performance and work on
synchronisation.

Regards,

Alekh Gupta,

NIT Hamirpur

GSoC 2020: gr-dpd - New BlogPost for Week 6

[Alekh]

Hello community!!

I have updated my new blogpost 
 
for last week updates regarding the gr-dpd 
 module on my blog 
.


Major week highlights are:

- Addition of 'cmd' port to the signal_source block in GNU Radio source 
tree.


- Updation of gain_phase_calibrate and stream_to_gmp_vector block to fix 
bugs and improve performance.


- Addition of gain_phase_test flowgraphs.

- Updation of copyright lines of all the code files of the gr-dpd 
 repository.


Upcoming Week tasks are:

 * Updation of the GRC IO port labels of /gr-dpd/ blocks to improve
   their understanding and use while using in flowgraphs.
 * Addition of the functionality for runtime updation of MP and GMP
   model PA coefficients as block parameters.
 * Bug fixes in the gr-dpd to improve its performance and work on
   synchronisation.

Regards,

Alekh Gupta,

NIT Hamirpur

Re: Making C++ OOT module and wish to set up a parameter with different choices!

[Glen Langston]

Very nice document.
Thanks
Glen


> On Jun 30, 2020, at 1:17 PM, jean-michel.fri...@femto-st.fr wrote:
> 
> I do not claim to cover all aspect of OOT blocks but I tried to document the 
> basics of 
> passing parameters and public/private variables at 
> http://jmfriedt.free.fr/gr_oscilloscope_eng.pdf
> 
> Unfortunately this document only covers GNU Radio 3.7: while the French 
> version was extended to
> GNU Radio 3.8, the English version was not extended accordingly but I'd be 
> happy to do so if there
> is any interest.
> 
> JM
> 
> --
> JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe,
> 25000 Besancon, France
> 
> June 30, 2020 7:06 PM, "George Edwards"  wrote:
> 
>> Hello,
>> 
>> I am making a C++ OOT module and wish to have an input parameter 
>> "frame_length" with different
>> choices. I would like to provide short, medium and long frames with a value 
>> attached to each. Based
>> on the OOT syntax, I can enter "frame_length" as an input argument to the 
>> model. Now, how can I set
>> up the inners of the *.cc file so that when the module is built into a 
>> Gnuradio block, I can simply
>> click on 'frame_length' to see the choices and select one?
>> 
>> Thanks for the help.
>> 
>> Regards,
>> George
> 

Re: Making C++ OOT module and wish to set up a parameter with different choices!

[jean-michel.fri...@femto-st.fr]

I do not claim to cover all aspect of OOT blocks but I tried to document the 
basics of 
passing parameters and public/private variables at 
http://jmfriedt.free.fr/gr_oscilloscope_eng.pdf

Unfortunately this document only covers GNU Radio 3.7: while the French version 
was extended to
GNU Radio 3.8, the English version was not extended accordingly but I'd be 
happy to do so if there
is any interest.

JM

--
JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe,
25000 Besancon, France

June 30, 2020 7:06 PM, "George Edwards"  wrote:

> Hello,
> 
> I am making a C++ OOT module and wish to have an input parameter 
> "frame_length" with different
> choices. I would like to provide short, medium and long frames with a value 
> attached to each. Based
> on the OOT syntax, I can enter "frame_length" as an input argument to the 
> model. Now, how can I set
> up the inners of the *.cc file so that when the module is built into a 
> Gnuradio block, I can simply
> click on 'frame_length' to see the choices and select one?
> 
> Thanks for the help.
> 
> Regards,
> George

Making C++ OOT module and wish to set up a parameter with different choices!

[George Edwards]

Hello,

I am making a C++ OOT module and wish to have an input parameter
"frame_length" with different choices. I would like to provide short,
medium and long frames with a value attached to each. Based on the OOT
syntax, I can enter "frame_length" as an input argument to the model. Now,
how can I set  up the inners of the *.cc file so that when the module is
built into a Gnuradio block, I can simply click on 'frame_length' to see
the choices and select one?

Thanks for the help.

Regards,
George

Re: Where in OOT C++ code to write a boolean variable that is set at startup

[Glen Langston]

Hi George,

This kind of parameter goes in the .h file that defines the classes.

in our event detection software we have a similar issue (If I understand you 
correctly).
in our detect_impl.h

namespace gr {
  namespace radio_astro {

class detect_impl : public detect
{
 private:
  // values computed in this block
...
 bool initialized = 0;   // flag initializing output
…

Then somewhere in the code (detect_impl.cc)

...skipping...
  if (! initialized) {
for (int iii = 0; iii <  d_vec_length; iii++)
  { samples[iii] = input[iii];
  }
initialized = 1; // no need to re-initialize the event
  }

Best regards,

Glen


> On Jun 30, 2020, at 12:35 PM, George Edwards  wrote:
> 
> Hello,
> 
> I am writing my Gnuradio OOT in C++ and wish to add a boolean variable that 
> at startup is set to "true". Then, in Gnuradio "work" method, this variable 
> is tested and if true will cause an initialization method to run and 
> initialize parameters for the signal processing. The initialization method 
> would in turn set this variable to "false" so that Gnuradio "work method" can 
> only call it once (the first time the work method is entered". Which of the 
> methods in the OOT *.cc file do I put this variable in so that it is in scope 
> in the work method and the initialization method?
> 
> Thanks,
> George

How to add Documentation description in C++ OOT module

[George Edwards]

Hello,

I am making a C++ OOT module and would like to add Documentation
description similar to if I were to open a Gnuradio block, I can go to the
Documentation and read the description of how the block works.

Thanks for any help you can provide.

Regards,
George

Where in OOT C++ code to write a boolean variable that is set at startup

[George Edwards]

Hello,

I am writing my Gnuradio OOT in C++ and wish to add a boolean variable that
at startup is set to "true". Then, in Gnuradio "work" method, this variable
is tested and if true will cause an initialization method to run and
initialize parameters for the signal processing. The initialization method
would in turn set this variable to "false" so that Gnuradio "work method"
can only call it once (the first time the work method is entered". Which of
the methods in the OOT *.cc file do I put this variable in so that it is in
scope in the work method and the initialization method?

Thanks,
George

Re: [USRP-users] How to find and link OOT module with gnuradio 3.8?

[Mohamed Yaaseen]

Hello EJ Kreinar,

I just came across this situation. I was trying to create a rfnoc gain
tutorial oot module using rfnomodtools. But, when I was doing cmake I got
some errors with respect to find_package(ettus).
I was just fiddling around with cmakefiles as I am not familiar with cmake
and stuff.

But, I found a problem with the gr-ettus module itself. In the gr-ettus
module ettutsConfig.cmake file, there is a line
*include("${CMAKE_CURRENT_LIST_DIR}/ettusTarget.cmake"). *
This is the file that rfnoc OOT searches in order to find the
package ettus. But, while make && make install gr-ettus module
installs *gnuradio-ettusTargets.cmake
*file at the location. Hence, rfnoc OOT module throws an error message
during cmake.

When I corrected the line in gr-ettus and reinstalled it, my OOT module was
able to compile  successfully.

But, I am now facing errors during the make process.

I believe the rfnocmodtools template code present inside gr-ettus has not
been migrated for 3.8 even though gr-ettus is migrated.

In the meantime I will also try to fix the error which is thrown during
make process. And update you in this thread if I have any success

If you are able to get past the make process also and install it in gr 3.8.
It would be really great...!!!

Regards,
Mohamed Yaaseen

On Tue, 30 Jun 2020 at 16:01, EJ Kreinar via USRP-users <
usrp-us...@lists.ettus.com> wrote:

> Hi gnuradio and usrp-users,
>
> I'm trying to update rfnoc OOT modules for gnuradio 3.8 (gasp).
>
> But I'm having trouble finding and linking to gr-ettus specifically, and I
> wonder how we're supposed to call find_package() and then link to OOT
> modules in general with the updated cmake workflow... Trying to find and
> link gr-ettus, I've tried a few things...
>
> 1) find_package(ettus)
>
> I believe this worked against gnuradio-3.7. Now, I get the following error
> during cmake configure...
>
> ```
> --   No package 'ettus' found
> CMake Error at /usr/local/lib/cmake/ettus/ettusConfig.cmake:41 (include):
>   include could not find load file:
> /usr/local/lib/cmake/ettus/ettusTarget.cmake
> ```
>
> 2) find_package(gnuradio-ettus)
>
> This seems more promising, since GR_LIBRARY_FOO seems to
> install gnuradio-ettus cmake files into the lib/cmake/ettus install
> location. This fails in cmake configure with the following error:
>
> ```
> CMake Error at gr-theseus/CMakeLists.txt:84 (find_package):
>   By not providing "Findgnuradio-ettus.cmake" in CMAKE_MODULE_PATH this
>   project has asked CMake to find a package configuration file provided by
>   "gnuradio-ettus", but CMake did not find one.
>
>   Could not find a package configuration file provided by "gnuradio-ettus"
>   with any of the following names:
>
> gnuradio-ettusConfig.cmake
> gnuradio-ettus-config.cmake
>
>   Add the installation prefix of "gnuradio-ettus" to CMAKE_PREFIX_PATH or
> set
>   "gnuradio-ettus_DIR" to a directory containing one of the above files.
> If
>   "gnuradio-ettus" provides a separate development package or SDK, be sure
> it
>   has been installed.
> ```
>
>
> Interestingly, if I change the GR_CMAKE_DIR *inside gr-ettus* to point to
> ${CMAKE_MODULES_DIR)/gnuradio-ettus (
> https://github.com/EttusResearch/gr-ettus/blob/b69260655e974786ea6e611bd91ab578b13ec72a/CMakeLists.txt#L69),
> then the gnuradio-ettus cmake modules get installed to
> lib/cmake/gnuradio-ettus. Then, in my OOT module, calling
> find_package(gnuradio-ettus) finds gr-ettus, and
> target_link_libraries( gnuradio-ettus) links successfully.
>
> So: Is this right? Am I missing something obvious here? Should gnuradio
> OOT modules set their GR_CMAKE_DIR to gnuradio-?
>
> Thanks for the help!
> EJ
>
> ___
> USRP-users mailing list
> usrp-us...@lists.ettus.com
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>

Re: How to find and link OOT module with gnuradio 3.8?

[Ron Economos]

I filed an issue on this over a year ago. I'm not sure if it was ever 
fully resolved.


https://github.com/gnuradio/gnuradio/issues/2429

Ron

On 6/30/20 07:00, EJ Kreinar wrote:

Hi gnuradio and usrp-users,

I'm trying to update rfnoc OOT modules for gnuradio 3.8 (gasp).

But I'm having trouble finding and linking to gr-ettus specifically, 
and I wonder how we're supposed to call find_package() and then 
link to OOT modules in general with the updated cmake workflow... 
Trying to find and link gr-ettus, I've tried a few things...


1) find_package(ettus)

I believe this worked against gnuradio-3.7. Now, I get the following 
error during cmake configure...


```
--   No package 'ettus' found
CMake Error at /usr/local/lib/cmake/ettus/ettusConfig.cmake:41 (include):
  include could not find load file:
    /usr/local/lib/cmake/ettus/ettusTarget.cmake
```

2) find_package(gnuradio-ettus)

This seems more promising, since GR_LIBRARY_FOO seems to 
install gnuradio-ettus cmake files into the lib/cmake/ettus install 
location. This fails in cmake configure with the following error:


```
CMake Error at gr-theseus/CMakeLists.txt:84 (find_package):
  By not providing "Findgnuradio-ettus.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "gnuradio-ettus", but CMake did not find one.

  Could not find a package configuration file provided by "gnuradio-ettus"
  with any of the following names:

    gnuradio-ettusConfig.cmake
    gnuradio-ettus-config.cmake

  Add the installation prefix of "gnuradio-ettus" to CMAKE_PREFIX_PATH 
or set
  "gnuradio-ettus_DIR" to a directory containing one of the above 
files.  If
  "gnuradio-ettus" provides a separate development package or SDK, be 
sure it

  has been installed.
```


Interestingly, if I change the GR_CMAKE_DIR *inside gr-ettus* to 
point to 
${CMAKE_MODULES_DIR)/gnuradio-ettus (https://github.com/EttusResearch/gr-ettus/blob/b69260655e974786ea6e611bd91ab578b13ec72a/CMakeLists.txt#L69), 
then the gnuradio-ettus cmake modules get installed to 
lib/cmake/gnuradio-ettus. Then, in my OOT module, calling 
find_package(gnuradio-ettus) finds gr-ettus, and 
target_link_libraries( gnuradio-ettus) links successfully.


So: Is this right? Am I missing something obvious here? Should 
gnuradio OOT modules set their GR_CMAKE_DIR to gnuradio-?


Thanks for the help!
EJ

How to find and link OOT module with gnuradio 3.8?

[EJ Kreinar]

Hi gnuradio and usrp-users,

I'm trying to update rfnoc OOT modules for gnuradio 3.8 (gasp).

But I'm having trouble finding and linking to gr-ettus specifically, and I
wonder how we're supposed to call find_package() and then link to OOT
modules in general with the updated cmake workflow... Trying to find and
link gr-ettus, I've tried a few things...

1) find_package(ettus)

I believe this worked against gnuradio-3.7. Now, I get the following error
during cmake configure...

```
--   No package 'ettus' found
CMake Error at /usr/local/lib/cmake/ettus/ettusConfig.cmake:41 (include):
  include could not find load file:
/usr/local/lib/cmake/ettus/ettusTarget.cmake
```

2) find_package(gnuradio-ettus)

This seems more promising, since GR_LIBRARY_FOO seems to
install gnuradio-ettus cmake files into the lib/cmake/ettus install
location. This fails in cmake configure with the following error:

```
CMake Error at gr-theseus/CMakeLists.txt:84 (find_package):
  By not providing "Findgnuradio-ettus.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "gnuradio-ettus", but CMake did not find one.

  Could not find a package configuration file provided by "gnuradio-ettus"
  with any of the following names:

gnuradio-ettusConfig.cmake
gnuradio-ettus-config.cmake

  Add the installation prefix of "gnuradio-ettus" to CMAKE_PREFIX_PATH or
set
  "gnuradio-ettus_DIR" to a directory containing one of the above files.  If
  "gnuradio-ettus" provides a separate development package or SDK, be sure
it
  has been installed.
```


Interestingly, if I change the GR_CMAKE_DIR *inside gr-ettus* to point to
${CMAKE_MODULES_DIR)/gnuradio-ettus (
https://github.com/EttusResearch/gr-ettus/blob/b69260655e974786ea6e611bd91ab578b13ec72a/CMakeLists.txt#L69),
then the gnuradio-ettus cmake modules get installed to
lib/cmake/gnuradio-ettus. Then, in my OOT module, calling
find_package(gnuradio-ettus) finds gr-ettus, and
target_link_libraries( gnuradio-ettus) links successfully.

So: Is this right? Am I missing something obvious here? Should gnuradio OOT
modules set their GR_CMAKE_DIR to gnuradio-?

Thanks for the help!
EJ

Re: GPIO lines on RPi4

[jean-michel.fri...@femto-st.fr]

Thanks to this comment, I ended up finding a solution to call a thread
running a TCP/IP server able to control the variables from the main
processing flowchart, without modifying manually the generated Python for a Qt
application.
A screenshot, which I hope is self-explanatory, illustrating this process is at
http://jmfriedt.org/2020-06-30-083722_2704x1050_scrot.png

However I am facing a surprising result.
I initially (see above) created a signal source, set its frequency to a 
variable flo, 
checked with a slider that changing flo did change the output frequency, 
removed the 
slider and set the signal source flo from my server. No change in the frequency 
output.

So I went back to my initial setup in which I change not only the source signal
frequency but also the receiver hardware LO frequency of the B210, keeping the 
TX LO
fixed. And surely enough both a spectrum analyzer and the coupled output from 
the
B210 TX to the RX show the signal shifting.

Screenshots at
http://jmfriedt.org/2020-06-30-095336_2704x1050_scrot.png show that the 
callback function
for the source frequency or LO frequency are exactly the same and so are the 
server handling
functions, while
http://jmfriedt.org/2020-06-30-095712_2704x1050_scrot.png shows that the B210 
TX frequency
only changes when tuning the hardware LO, not the signal source LO.

Is there some signal that needs to be sent to the signal source beyond
self.analog_sig_source_x_0.set_frequency(self.flo)
to tell it to change frequency ?

Thanks, JM

--
JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe,
25000 Besancon, France

June 22, 2020 1:25 PM, "Marcus Müller"  wrote:

> It gets even better:
> 
> We've launched a feature in 3.8.1.0 (and on master before that, as we do 
> with any feature that ends up in a maintenance release) that we hope 
> doesn't come back to bite us due to enabling unclean design. But, we 
> must build best practices so that it doesn't go unused, either, so:
> 
> Assuming you're using GNU Radio 3.8.1.0 (or later, once we release 
> something), you can make use of the "Python Snippets" in GRC.
> 
> Cheers,
> Marcus
> 
> On 18/06/2020 23.17, Marcus D. Leech wrote:
> 
>> On 06/18/2020 03:54 PM, jean-michel.fri...@femto-st.fr wrote:
>>> My approach:
>>> * build your grc chart from GNU Radio Companion and generate the .py file
>>> * edit the py file and import pygpio
>>> * play with the RPi4 GPIO in your python script.
>>> 
>>> See attached script, with a python server included in the Python script
>>> to control an RF switch from a GNU Octave TCP/IP client talking to the
>>> Python
>>> TCP/IP server.
>>> 
>>> I am presenting this approach to hardware control at
>>> http://jmfriedt.free.fr/sdra_radar.pdf
>>> 
>>> JM
>> 
>> If you use "Python Module" block, you can write a lot of
>> non-GnuRadio-esque python, import anything you want, etc, etc.  No editing
>> of the output python required, necessarily.
>> 
>>> --
>>> JM Friedt, FEMTO-ST Time & Frequency/SENSeOR, 26 rue de l'Epitaphe,
>>> 25000 Besancon, France
>>> 
>>> June 18, 2020 9:40 PM, "Da Fy"  wrote:
>> 
>> Hi All, does anyone have an example of how to control GOIO lines on
>> the RPi4 from within a GRC
>> flowgraph. I’m guessing it’s an OOT module.
>> 
>> I need to generate a signal of a few 100Hz & control GPIO lines at
>> various points though the cycle.
>> 
>> Alternatively, I could generate the signal & lines with external
>> hardware & read them with
>> GnuRadio.
>> 
>> Tnx, Dave

Possibility of transmitting files with packet_tx

[Grace Huang]

Hi all,

I'm aiming to transmit csv and jpg files with an SDR and BPSK modulation.
Previously I've built a flowgraph (attached as demodulation_copy.grc) with
packet encoder block which is deprecated and the flowgraph can't seem to
work.

I'm exploring the example flowgraph(attached as packet_tx.grc) for
packet_tx to perform encoding and modulation. From what I understand, it
breaks up the header and the packet to modulate them individually before
combining them afterwards. May I know if this can be modified to transmit
files such as using the file source block at the very start? Or how can I
incorporate it to replace the deprecated packet encoder in my previously
built flowgraph?

If not, please advise on a possible approach to do so.

Thank you

Regards,
Grace


packet_tx.grc
Description: Binary data


demodulation_copy.grc
Description: Binary data

Re: gr-foo , gr-Bluetooth

[Cinaed Simson]

Bluetooth is using fast frequency hopping spread spectrum where only 
synchronized receivers are receiving the data.


There are wireshark plugins for bluetooth.

And you might want to post your question on the ubertooth mailing list 
regarding gr-bluetooth. Some of the people there developed gr-bluetooth 
then released a bluetooth capture device known as ubertooth - although 
the original people may not still be there.


-- Cinaed



On 6/29/20 7:14 AM, Martin Spears wrote:


I have been working with gr-bluetooth and things have been working out 
fine. I was wondering if there is a wireshark connector similar to the 
gr-foo ZigBee/wifi case. I can see a lot of the hex data but since I 
cannot format it correctly as a pcap file wireshark cannot provide me 
with any further information except that of a malformed eth


Martin Spears

Re: ALSAPulseAudio procedure

[Cinaed Simson]

What does

  aplay -l

indicate?

When using

  hw:CARD=Generic,DEV=0

in gnuradio, try using numbers, for example,

  hw:0,0

or

 plughw:0,0

and see if it makes a difference.

Or try switching between sampling rates of 48000 and 44100.

-- CInaed

On 6/29/20 3:00 PM, Barry Duggan wrote:
I have been having problems with audio underruns on some of my 
flowgraphs, so I decided to try the procedure in 
https://wiki.gnuradio.org/index.php/ALSAPulseAudio#Solution_2


I found one entry (other than HDMI) for my speakers and created the 
following for ~/.asoundrc :

pcm.pulse_monitor {
    type pulse
    device alsa_output.pci-_0f_00.4.analog-stereo.monitor
}

ctl.pulse_monitor {
    type pulse
    device alsa_output.pci-_0f_00.4.analog-stereo.monitor
}

I changed my Audio Sink device name to 'pulse_monitor' and got the 
following error:
ALSA lib pcm_pulse.c:752:(pulse_prepare) PulseAudio: Unable to create 
stream: No such entity


gr::log :ERROR: audio_alsa_sink0 - [pulse_monitor]: snd_pcm_hw_params 
failed: Input/output error

Traceback (most recent call last):
  File "/home/barry/GRdev/Pluto_NFM.py", line 216, in 
    main()
  File "/home/barry/GRdev/Pluto_NFM.py", line 194, in main
    tb.start()
  File 
"/usr/local/lib/python3/dist-packages/gnuradio/gr/top_block.py", line 
111, in start

    top_block_start_unlocked(self._impl, max_noutput_items)
  File 
"/usr/local/lib/python3/dist-packages/gnuradio/gr/runtime_swig.py", 
line 5828, in top_block_start_unlocked

    return _runtime_swig.top_block_start_unlocked(r, max_noutput_items)
RuntimeError: check topology failed on audio_alsa_sink(9) using 
ninputs=1, noutputs=0


Using the device name "hw:CARD=Generic,DEV=0" works, but gives the 
underruns. I'm using Ubuntu 19.10.


Any ideas?
Thanks.