Re: GRC version 3.9.0.0 git master (python 3.8.2) + OOT blocks

[Josh]

David,

As far as I know, 3.15 is the long term support UHD release, and should be
considered the most stable.  4.0 has not been officially released yet
(looks like release candidate went out last week).  If your research does
not involve the newest features of GNU Radio, but you need a stable
version, I'd recommend sticking with 3.8.2 - which it it sounds like you
have successfully done from source.  It looks like there are two variables
in play here - how GR is installed, and the version of GR.  You can also
install GR 3.8 from the PPA (gnuradio-releases), and of course 3.9 from
source.  But if having installed 3.8 from source is working for you, that
seems like a good path to go down.  For gr-uhd to be installed, you have to
install uhd (either from the package manager - 20.04 has 3.15.0.0-1build5,
or from source) before compiling GR.  Take a look at the CMake stdout for
GR to see if there are any other dependencies or issues that would prevent
gr-uhd from being installed.

Josh

On Sun, Aug 30, 2020 at 1:26 PM David Taylor (manx.net) 
wrote:

> Josh,
>
> Many thanks for your questions and apologies for the delay in replying.
>
> From a clean 20.04 Ubuntu, I installed 3.9 using the package installer
> from the master branch.
> $ sudo add-apt-repository ppa:gnuradio/gnuradio -master
>
> There were no major issues with the GRC install, transfer of old 3.7 OOT
> blocks, their new python binding, libraries linkage or block import for
> that matter.
> The 3.9 OOT porting guide proved, helpful with some additional and
> relevant information to be found in the 3.8 porting guide particularly on
> external libraries inclusion.
> UHD 3.15.0.0-2build5 from a package manager install works fine.
>
> PYTHONPATH =/usr/local/lib/python3/dist-packages.
> The OOT blocks are being installed to:
> /usr/local/lib/python3/dist-packages/test and the blocks to:
> /usr/local/share/gnuradio/grc/blocks
> In all other respects the GRC works fine..
>
> -
> Noting this release last weekend, on a separate drive, with a clean 20.04
> Ubuntu, I have installed and built GRC 3.8.2.0 from gnuradio-3.8.2.0.tar.gz
> OOT blocks import without issue as per 3.7.11 using the older SWIG
> bindings. VOLKGNSSSDR as an external library is both visible and useable.
>
> I noticed that during the build the UHD interface was disabled and
> consequently the GRC source and sink blocks are both missing. These are
> available for build under ~/gr-uhd.
> Is there a reason for this please?
> Is 3.15 compatible and stable as a UHD interface, noting the very recent
> emergence of 4.0 RC?
>
> My research in the first instance, is to investigate the intrinsic carrier
> phase stability of an SDR system in RF loop-back and then through a
> geo-stationary satellite.
> The OOT blocks in development are of flexible direct spread spectrum
> coding and reception type.
> It’s therefore important that I settle on stable GRC/UHD variants for the
> next twelve months or so.
>
> Best regards,
> David GD4FMB
>
>
>
>
> *From:* Josh
> *Sent:* Monday, August 24, 2020 8:09 PM
> *To:* David Taylor (manx.net)
> *Cc:* GNURadio Discussion List
> *Subject:* Re: GRC version 3.9.0.0 git master (python 3.8.2) + OOT blocks
>
> David,
>
> 1) How is your GNU Radio installed in this system?
> 2) It sounds a lot like PYTHONPATH is misconfigured for OOT - where are
> your OOT files being installed to?
>
> Thanks,
> Josh
>
> On Fri, Aug 21, 2020 at 12:23 PM David Taylor (manx.net) <
> drtay...@manx.net> wrote:
>
>> Josh,
>>
>> Sorry to go over old ground yet again.
>>
>> In order to remove any additional problems caused by the use of external
>> libraries, I have created a separate OOT branch that is void of external
>> libraries.
>> Stripped to the bone python and C++ blocks have been created using
>> gr_modtool. Test codes validate the blocks code content as functional and
>> they import correctly into the GRC with simple .yml.
>> The top level CMakeLists.txt and others are unmodified from a clean new
>> module.
>>
>> The current issue has been traced so far to the __init__.py file and its
>> inability to resolve ‘__path__’
>> Consequently the pybind11 link fails to find my ‘test’ directory and the
>> subsequent imported python block fails with no known parent package.
>> I am unclear how and where this is initialised under python3? I have
>> attended to the usual library and path ~./bashrc changes to no avail.
>>
>> The GRC outputs the AttributeError: message for the python and C++ OOT
>> block.
>>
>> Once resolved, I can move forward again with the external library
>> inclusion.
>>
>> Many thanks,
>> David GD4FMB
>>
>>
>>
>> *From:* Josh
>> *Sent:* Monday, August 17, 2020 11:45 AM
>> *To:* David Taylor (manx.net)
>> *Cc:* GNURadio Discussion List
>> *Subject:* Re: GRC version 3.9.0.0 git master (python 3.8.2) + OOT blocks
>>
>> David,
>>
>> I've found most of the time I get the "No module named ..." error it is
>> due to C++ linkage issues in setting up the CMake.  There was a big 

Re: Ho to use Limesdr and rtl dongles with GNURadio 3.8.2

[Christophe Seguinot]

  
  
Thanks Paul
This in fact is an important information. 

To resume I found that following packages installed from source
  under Ubuntu 20.04 (compiling some of them is tricky) are fully
  functionnal with GNURadio 3.8.2: 


  librtlsdr 
  
  gr-osmosdr
  gr-limesdr (LimeSuite can be installed from ubuntu repository)
  gqrx (if you want both GNU Radio AND gqrx)
  
  gr-rds

For all these packages, installing from existing PPA (ubuntu and
  myriadrf repositories) breaks GNU Radio.
Regards

On 27/08/2020 12:44, Paul Boven wrote:

Hi
  Christophe,
  
  
  This is unfortunately a known problem. The way GNU Radio was
  packaged in Ubuntu 20.04 is (to me) a bit odd, with the version
  number as part of the package name for most of the libraries.
  
  
  If you install GR from the PPA, you will now get version 3.8.2,
  which is great. This will also include all the libraries. But if
  you then try to install a package from the regular Ubuntu
  repository, e.g. gr-osmosdr, this will pull in gnuradio-3.8.1
  libraries. So now you end up with two versions of the gnuradio
  libraries installed on your system. Your gr-osmosdr (from the
  Ubuntu repositories) is linked against the 3.8.1 versions of the
  libraries, whereas the gnuradio on your system links against the
  3.8.2 version of the libraries. Then, when you try to use the two
  together, mayhem ensues.
  
  
  The result of this, is that the 3.8.2 on the PPA only works with
  itself, but not with the other packages from the regular Ubuntu
  LTS release. Unfortunately, the PPA is simply broken at this time.
  
  
  Fixing this is not easy, because to solve the root cause, we'd
  have to figure out how to properly package GR for Ubuntu, and then
  convince Ubuntu to upgrade the version of GNU Radio (and all
  dependent packages!) that are part of the stable release.
  
  
  Regards, Paul Boven.
  
  
  On 8/27/20 12:25 PM, Christophe Seguinot wrote:
  
  Hi


I recently switched my computer to Ubuntu 20.04 and installed
GNURadio 3.8.2.0 from ppa
(http://ppa.launchpad.net/gnuradio/gnuradio-releases/ubuntu).
Version 3.8.2 is the latest in this PPA and is installed by
default.


I also installed gr-osmosdr gr-limesdr and gr-rds using sudo apt
install.


Gnuradio is running fine in most cases. However, each time I run
a flowgraph involving  SDR or LimeSDR Dongle I get the classical
error:


 File "/home/-/rds_rx.py", line 571, in __init__

 self.audio_sink_1 = audio.sink(audio_rate, '', True)

 AttributeError: 'int' object has no attribute 'sink'


Looking into library folder /usr/lib/x86_64-linux-gnu I found
that some 3.8.1.1 and 3.8.0 libraries are installed and probably
conflicting with 3.8.2.0 libraries. For example, command/ll
libgnuradio-runtime*/ gives


 lrwxrwxrwx 1 root root  28 aug.  22 14:29
libgnuradio-runtime.so -> libgnuradio-runtime.so.3.8.2

 lrwxrwxrwx 1 root root  30 juil. 31 15:23
libgnuradio-runtime.so.3.8.1 ->
libgnuradio-runtime.so.3.8.1.0

 -rw-r--r-- 1 root root 1077632 juil. 31 15:23
libgnuradio-runtime.so.3.8.1.0

 lrwxrwxrwx 1 root root  30 aug.  22 14:29
libgnuradio-runtime.so.3.8.2 ->
libgnuradio-runtime.so.3.8.2.0

 -rw-r--r-- 1 root root 1077632 aug.  22 14:29
libgnuradio-runtime.so.3.8.2.0


It looks like 3.8.1 and 3.8.0 libraries have been installed when
installing gr-osmosdr gr-limesdr and gr-rds


 installed libraries during gr-osmosdr install


 libgnuradio-audio.so.3.8.1


 libgnuradio-blocks.so.3.8.1


 libgnuradio-pmt.so.3.8.1


 libgnuradio-runtime.so.3.8.1


 libgnuradio-fcdproplus.so.3.8.0


 libgnuradio-iqbalance.so.3.8.0


 ilbgnuradio-uhd.so.3.8.0


 ibgnuradio-fosphor.so.3.8.0


 installed libraries during gr-rds install


 libgnuradio-analog.so.3.8.1


 libgnuradio-digital.so.3.8.1


 libgnuradio-filter.so.3.8.1



I also notice that gr-osmosdr and gr-limesdr depend on
libgnuradio-xxx  >

Using forgotten id breaks gnuradio-companion

[Christophe Seguinot]

Hi

One of my flowgraph was generating the error:

    self.audio_sink_0 = audio.sink(audio_rate, '', True)
    AttributeError: 'int' object has no attribute 'sink'

This error was not easy to debug since the error message sounds like 
there was a library error (which was not the case here).


My mistake was a "QT GUI Chooser" whose id was (incorrectly) set to 
audio; "audio" being also the name of a gnuradio python module.


Now that I found my mistake, it's obvious that no ID should be set to 
some python module name.


May be it could be interesting that gnuradio-companion tests block ids 
and rejects forbidden ones when compiling flowgraph.


Regards

Re: Using forgotten id breaks gnuradio-companion

[Jeff Long]

Since there is no way of knowing what global names will conflict in the
future, it could be useful for GRC to prefix ids (id_audio), make them part
of another structure (ids.audio), or something similar. This adds
complexity to manual coding in Python, so it's a tradeoff.

On Mon, Aug 31, 2020 at 10:53 AM Christophe Seguinot <
christophe.segui...@orange.fr> wrote:

> Hi
>
> One of my flowgraph was generating the error:
>
>  self.audio_sink_0 = audio.sink(audio_rate, '', True)
>  AttributeError: 'int' object has no attribute 'sink'
>
> This error was not easy to debug since the error message sounds like
> there was a library error (which was not the case here).
>
> My mistake was a "QT GUI Chooser" whose id was (incorrectly) set to
> audio; "audio" being also the name of a gnuradio python module.
>
> Now that I found my mistake, it's obvious that no ID should be set to
> some python module name.
>
> May be it could be interesting that gnuradio-companion tests block ids
> and rejects forbidden ones when compiling flowgraph.
>
> Regards
>
>
>

Funcube Dongle Pro Plus help

[Vincenzo Mone]

Hello

Please I am trying to install the FCDPROPLUS which is the Funcube Dongle Pro
Plus.

This is what I've done following the instructions on the author page:

 

git clone  
https://github.com/dl1ksv/gr-fcdproplus

 

cd ~/gr-fcdproplus

mkdir build

cd build

cmake -DCMAKE_INSTALL_PREFIX="/usr" -DCMAKE_BUILD_TYPE=Release ../

make

sudo make install

sudo ldconfig

 

then I have created a file named '99-usb-serial.rules'  with the following
content:

 

SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8" ATTRS{idProduct}=="fb56"
MODE:="0666"

SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8" ATTRS{idProduct}=="fb31"
MODE:="0666"

KERNEL=="hidraw*", ATTRS{busnum}=="1", ATTRS{idVendor}=="04d8",
ATTRS{idProduct}=="fb56", MODE="0666"

KERNEL=="hidraw*", ATTRS{busnum}=="1", ATTRS{idVendor}=="04d8",
ATTRS{idProduct}=="fb

 

 

Then:

 

cd /etc/udev/rules.d

sudo cp -v ~//99-usb-serial.rules ./

sudo udevadm trigger

 

After that executing grc  I sould find in Fcd  

 

Funcube Dongle   

Funcube Dongle control

Funcube Dongle Pro+

Funcube Dongle Pro+ control

 

But I do not find any FCD group.

Please anybody can tell me if I am doing something wrong?

Thanks

 

73's de Enzo IK8OZV
EasyLog 5 BetaTester
EasyLog PDA BetaTester
WinBollet BetaTester
D.C.I. CheckPoint Regione Campania
Skype: ik8ozv8520




  *

  **   GSM  +39 328 7110193  **

  * SMS  +39 328 7110193*

  *

 

Re: Using forgotten id breaks gnuradio-companion

[Kevin Reid]

On Mon, Aug 31, 2020 at 8:11 AM Jeff Long  wrote:

> Since there is no way of knowing what global names will conflict in the
> future, it could be useful for GRC to prefix ids (id_audio), make them part
> of another structure (ids.audio), or something similar. This adds
> complexity to manual coding in Python, so it's a tradeoff.
>

It would be sufficient to modify the constructor code generation so that
variables aren't used — to use a non-conflicting example from a random
generated .py file I have,
  self.samp_rate = samp_rate = 44100
  ...
  self.audio_sink_0 = audio.sink(samp_rate, "", True)
would be instead generated without a local variable as
  self.samp_rate = 44100
  ...
  self.audio_sink_0 = audio.sink(self.samp_rate, "", True)

If another case arises where that's not sufficient, I think it would still
be a better idea to have GRC detect and alter Python variable names (or,
possibly preferably, the names of module imports) on a case-by-case basis
to avoid worsening readability (and edit distance from hand-maintained GR
code).

Re: Funcube Dongle Pro Plus help

[Marcus Müller]

Vincenzo,

please don't open a new thread for every other email you have sent. You 
have gotten easily confused in the past, and we can avoid that if you 
can try to focus on staying on a single email thread, and it was a big 
problem for you. Please don't open a new thread before having solved 
this issue, and instead reply to the things here, keeping 
discuss-gnuradio@gnu.org in CC:.


Something went wrong during your software build or installation. We 
can't tell you what that was - have you checked whether the cmake, the 
make, the make install commands were successful?


Best regards,

Marcus

On 8/31/20 5:09 PM, Vincenzo Mone wrote:


Hello

Please I am trying to install the FCDPROPLUS which is the Funcube 
Dongle Pro Plus.


This is what I’ve done following the instructions on the author page:

git clone https://github.com/dl1ksv/gr-fcdproplus

cd ~/gr-fcdproplus

mkdir build

cd build

cmake -DCMAKE_INSTALL_PREFIX="/usr" -DCMAKE_BUILD_TYPE=Release ../

make

sudo make install

sudo ldconfig

then I have created a file named '99-usb-serial.rules'  with the 
following content:


SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8" ATTRS{idProduct}=="fb56" 
MODE:="0666"


SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8" ATTRS{idProduct}=="fb31" 
MODE:="0666"


KERNEL=="hidraw*", ATTRS{busnum}=="1", ATTRS{idVendor}=="04d8", 
ATTRS{idProduct}=="fb56", MODE="0666"


KERNEL=="hidraw*", ATTRS{busnum}=="1", ATTRS{idVendor}=="04d8", 
ATTRS{idProduct}=="fb


Then:

cd /etc/udev/rules.d

sudo cp -v ~//99-usb-serial.rules ./

sudo udevadm trigger

After that executing grc  I sould find in Fcd

Funcube Dongle

Funcube Dongle control

Funcube Dongle Pro+

Funcube Dongle Pro+ control

But I do not find any FCD group.

Please anybody can tell me if I am doing something wrong?

Thanks

73’s de Enzo IK8OZV
EasyLog 5 BetaTester
EasyLog PDA BetaTester
WinBollet BetaTester
D.C.I. CheckPoint Regione Campania
Skype: ik8ozv8520




*

** GSM  +39 328 7110193  **

  * SMS  +39 328 7110193 *

  *

Re: Using forgotten id breaks gnuradio-companion

[Marcus Müller]

I'd categorize this somewhere between feature request and bug report.

Could you raise this as an issue on github.com/gnuradio/gnuradio/issues 
, please?


Generally, tracking could be possible, but is rather complicated, 
because we have different namespaces in which parts of the flow graph 
generation happen. Hence, I'd like this to be tracked in the issue 
tracker. Thanks!


Best,

Marcus

On 8/31/20 4:52 PM, Christophe Seguinot wrote:

Hi

One of my flowgraph was generating the error:

    self.audio_sink_0 = audio.sink(audio_rate, '', True)
    AttributeError: 'int' object has no attribute 'sink'

This error was not easy to debug since the error message sounds like 
there was a library error (which was not the case here).


My mistake was a "QT GUI Chooser" whose id was (incorrectly) set to 
audio; "audio" being also the name of a gnuradio python module.


Now that I found my mistake, it's obvious that no ID should be set to 
some python module name.


May be it could be interesting that gnuradio-companion tests block ids 
and rejects forbidden ones when compiling flowgraph.


Regards

R: Funcube Dongle Pro Plus help

[Vincenzo Mone]

Sorry Marcus,
I thought it was closed as I did not get any reply from a long time.
Please what I need to check as I still did not understood  how to know The
gnuradio path for the correct command:

cmake -DCMAKE_INSTALL_PREFIX= "path to gnuradio installation" ../

Thanks

73’s de Enzo IK8OZV
EasyLog 5 BetaTester
EasyLog PDA BetaTester
WinBollet BetaTester
D.C.I. CheckPoint Regione Campania
Skype: ik8ozv8520




  *
  **   GSM  +39 328 7110193  **
  * SMS  +39 328 7110193    *
  *

> -Messaggio originale-
> Da: Marcus Müller 
> Inviato: lunedì 31 agosto 2020 18:11
> A: Vincenzo Mone ; Gnuradio Mailing List  gnura...@gnu.org>
> Oggetto: Re: Funcube Dongle Pro Plus help
> 
> Vincenzo,
> 
> please don't open a new thread for every other email you have sent. You
> have gotten easily confused in the past, and we can avoid that if you can
try
> to focus on staying on a single email thread, and it was a big problem for
you.
> Please don't open a new thread before having solved this issue, and
instead
> reply to the things here, keeping discuss-gnuradio@gnu.org in CC:.
> 
> Something went wrong during your software build or installation. We can't
> tell you what that was - have you checked whether the cmake, the make,
> the make install commands were successful?
> 
> Best regards,
> 
> Marcus
> 
> On 8/31/20 5:09 PM, Vincenzo Mone wrote:
> >
> > Hello
> >
> > Please I am trying to install the FCDPROPLUS which is the Funcube
> > Dongle Pro Plus.
> >
> > This is what I’ve done following the instructions on the author page:
> >
> > git clone https://github.com/dl1ksv/gr-fcdproplus
> >
> > cd ~/gr-fcdproplus
> >
> > mkdir build
> >
> > cd build
> >
> > cmake -DCMAKE_INSTALL_PREFIX="/usr" -DCMAKE_BUILD_TYPE=Release
> ../
> >
> > make
> >
> > sudo make install
> >
> > sudo ldconfig
> >
> > then I have created a file named '99-usb-serial.rules'  with the
> > following content:
> >
> > SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8"
> ATTRS{idProduct}=="fb56"
> > MODE:="0666"
> >
> > SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8"
> ATTRS{idProduct}=="fb31"
> > MODE:="0666"
> >
> > KERNEL=="hidraw*", ATTRS{busnum}=="1", ATTRS{idVendor}=="04d8",
> > ATTRS{idProduct}=="fb56", MODE="0666"
> >
> > KERNEL=="hidraw*", ATTRS{busnum}=="1", ATTRS{idVendor}=="04d8",
> > ATTRS{idProduct}=="fb
> >
> > Then:
> >
> > cd /etc/udev/rules.d
> >
> > sudo cp -v ~//99-usb-serial.rules ./
> >
> > sudo udevadm trigger
> >
> > After that executing grc  I sould find in Fcd
> >
> > Funcube Dongle
> >
> > Funcube Dongle control
> >
> > Funcube Dongle Pro+
> >
> > Funcube Dongle Pro+ control
> >
> > But I do not find any FCD group.
> >
> > Please anybody can tell me if I am doing something wrong?
> >
> > Thanks
> >
> > 73’s de Enzo IK8OZV
> > EasyLog 5 BetaTester
> > EasyLog PDA BetaTester
> > WinBollet BetaTester
> > D.C.I. CheckPoint Regione Campania
> > Skype: ik8ozv8520
> >
> >
> >
> >
> > *
> >
> > ** GSM  +39 328 7110193  **
> >
> >   * SMS  +39 328 7110193 *
> >
> >   *
> >

Re: R: Funcube Dongle Pro Plus help

[Marcus Müller]

Hi Vincenzo,

no such thing as "closed" :)

Well, that path is where your GNU Radio is installed to. You should be 
able to check it through `gnuradio-config-info --prefix`.


To repeat my questions:

1. Did `cmake...` run through successfully? Or did it end with an error?

2. Did `make` run through successfully? Or did it end with an error?

3. Did `sudo make install` run through successfully? Or did it end with 
an error?


Best regards,
Marcus

On 8/31/20 7:25 PM, Vincenzo Mone wrote:

Sorry Marcus,
I thought it was closed as I did not get any reply from a long time.
Please what I need to check as I still did not understood  how to know The
gnuradio path for the correct command:

cmake -DCMAKE_INSTALL_PREFIX= "path to gnuradio installation" ../

Thanks

73's de Enzo IK8OZV
EasyLog 5 BetaTester
EasyLog PDA BetaTester
WinBollet BetaTester
D.C.I. CheckPoint Regione Campania
Skype: ik8ozv8520




   *
   **   GSM  +39 328 7110193  **
   * SMS  +39 328 7110193    *
   *


-Messaggio originale-
Da: Marcus Müller 
Inviato: lunedì 31 agosto 2020 18:11
A: Vincenzo Mone ; Gnuradio Mailing List 
Oggetto: Re: Funcube Dongle Pro Plus help

Vincenzo,

please don't open a new thread for every other email you have sent. You
have gotten easily confused in the past, and we can avoid that if you can

try

to focus on staying on a single email thread, and it was a big problem for

you.

Please don't open a new thread before having solved this issue, and

instead

reply to the things here, keeping discuss-gnuradio@gnu.org in CC:.

Something went wrong during your software build or installation. We can't
tell you what that was - have you checked whether the cmake, the make,
the make install commands were successful?

Best regards,

Marcus

On 8/31/20 5:09 PM, Vincenzo Mone wrote:

Hello

Please I am trying to install the FCDPROPLUS which is the Funcube
Dongle Pro Plus.

This is what I've done following the instructions on the author page:

git clone https://github.com/dl1ksv/gr-fcdproplus

cd ~/gr-fcdproplus

mkdir build

cd build

cmake -DCMAKE_INSTALL_PREFIX="/usr" -DCMAKE_BUILD_TYPE=Release

../

make

sudo make install

sudo ldconfig

then I have created a file named '99-usb-serial.rules'  with the
following content:

SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8"

ATTRS{idProduct}=="fb56"

MODE:="0666"

SUBSYSTEMS=="usb" ATTRS{idVendor}=="04d8"

ATTRS{idProduct}=="fb31"

MODE:="0666"

KERNEL=="hidraw*", ATTRS{busnum}=="1", ATTRS{idVendor}=="04d8",
ATTRS{idProduct}=="fb56", MODE="0666"

KERNEL=="hidraw*", ATTRS{busnum}=="1", ATTRS{idVendor}=="04d8",
ATTRS{idProduct}=="fb

Then:

cd /etc/udev/rules.d

sudo cp -v ~//99-usb-serial.rules ./

sudo udevadm trigger

After that executing grc  I sould find in Fcd

Funcube Dongle

Funcube Dongle control

Funcube Dongle Pro+

Funcube Dongle Pro+ control

But I do not find any FCD group.

Please anybody can tell me if I am doing something wrong?

Thanks

73's de Enzo IK8OZV
EasyLog 5 BetaTester
EasyLog PDA BetaTester
WinBollet BetaTester
D.C.I. CheckPoint Regione Campania
Skype: ik8ozv8520




*

** GSM  +39 328 7110193  **

   * SMS  +39 328 7110193 *

   *

R: R: Funcube Dongle Pro Plus help

[Vincenzo Mone]

Hi Marcus,
thanks for your reply.
I gave the command:

gnuradio-config-info --prefix

and got :

/usr/local

So I have tried to give the command:

cmake -DCMAKE_INSTALL_PREFIX= "/usr/local/" ../

- Checking for module 'mpir >= 3.0'
--   No package 'mpir' found
-- Could NOT find MPIR (missing: MPIRXX_LIBRARY MPIR_LIBRARY MPIR_INCLUDE_DIR) 
-- User set python executable /usr/bin/python3
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found suitable 
exact version "3.8.2") 
-- Found ALSA 1.2.2
-- Found jack: /usr/lib/x86_64-linux-gnu/libjack.so
-- Extracting version information from git describe...
-- System Hidapi will be used
-- 
-- Checking for module SWIG
-- Found SWIG version 4.0.1.
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found version 
"3.8.2") 
-- Doxxyfile found in 
/usr/share/gnuradio/modtool/templates/gr-newmod/docs/doxygen
--  Build Summary =
-- Building gr-fcdproplus  : 3.8.0 for Linux 
-- Building for gnuradio   : 3.8.1.0
-- Using CMAKE Module path : 
/home/enzo/gr-fcdproplus/cmake/Modules;/usr/local/lib/cmake/gnuradio
-- CMake Modules Dir   : lib/cmake
-- fcdproplus INCLUDES : include/fcdproplus
-- Using install prefix: 
-- Installing grc files to : /share/gnuradio/grc/blocks
-- System Hidapi Lib /usr/lib/x86_64-linux-gnu/libhidapi-libusb.so is used
-- 
-- Configuring done
-- Generating done
-- Build files have been written to: /home/enzo/gr-fcdproplus/build

Then I gave the other commands:

make
sudo make install
sudo ldconfig

Did not get any errors on the above commands

Went again in gnuradio but still get the missing block fcdproplus_fcdproplus
Thanks


73’s de Enzo IK8OZV
EasyLog 5 BetaTester
EasyLog PDA BetaTester
WinBollet BetaTester
D.C.I. CheckPoint Regione Campania
Skype: ik8ozv8520




  *
  **   GSM  +39 328 7110193  **
  * SMS  +39 328 7110193*
  *

> -Messaggio originale-
> Da: Marcus Müller 
> Inviato: lunedì 31 agosto 2020 19:37
> A: Vincenzo Mone 
> Cc: Gnuradio Mailing List 
> Oggetto: Re: R: Funcube Dongle Pro Plus help
> 
> Hi Vincenzo,
> 
> no such thing as "closed" :)
> 
> Well, that path is where your GNU Radio is installed to. You should be able to
> check it through `gnuradio-config-info --prefix`.
> 
> To repeat my questions:
> 
> 1. Did `cmake...` run through successfully? Or did it end with an error?
> 
> 2. Did `make` run through successfully? Or did it end with an error?
> 
> 3. Did `sudo make install` run through successfully? Or did it end with an
> error?
> 
> Best regards,
> Marcus
> 
> On 8/31/20 7:25 PM, Vincenzo Mone wrote:
> > Sorry Marcus,
> > I thought it was closed as I did not get any reply from a long time.
> > Please what I need to check as I still did not understood  how to know
> > The gnuradio path for the correct command:
> >
> > cmake -DCMAKE_INSTALL_PREFIX= "path to gnuradio installation" ../
> >
> > Thanks
> >
> > 73's de Enzo IK8OZV
> > EasyLog 5 BetaTester
> > EasyLog PDA BetaTester
> > WinBollet BetaTester
> > D.C.I. CheckPoint Regione Campania
> > Skype: ik8ozv8520
> >
> >
> >
> >
> >*
> >**   GSM  +39 328 7110193  **
> >* SMS  +39 328 7110193*
> >*
> >
> >> -Messaggio originale-
> >> Da: Marcus Müller 
> >> Inviato: lunedì 31 agosto 2020 18:11
> >> A: Vincenzo Mone ; Gnuradio Mailing List  >> gnura...@gnu.org>
> >> Oggetto: Re: Funcube Dongle Pro Plus help
> >>
> >> Vincenzo,
> >>
> >> please don't open a new thread for every other email you have sent.
> >> You have gotten easily confused in the past, and we can avoid that if
> >> you can
> > try
> >> to focus on staying on a single email thread, and it was a big
> >> problem for
> > you.
> >> Please don't open a new thread before having solved this issue, and
> > instead
> >> reply to the things here, keeping discuss-gnuradio@gnu.org in CC:.
> >>
> >> Something went wrong during your software build or installation. We
> >> can't tell you what that was - have you checked whether the cmake,
> >> the make, the make install commands were successful?
> >>
> >> Best regards,
> >>
> >> Marcus
> >>
> >> On 8/31/20 5:09 PM, Vincenzo Mone wrote:
> >>> Hello
> >>>
> >>> Please I am trying to install the FCDPROPLUS which is the Funcube
> >>> Dongle Pro Plus.
> >>>
> >>> This is what I've done following the instructions on the author page:
> >>>
> >>> git clone https://github.com/dl1ksv/gr-fcdproplus
> >>>
> >>> cd ~/gr-fcdproplus
> >>>
> >>> mkdir build
> >>>
> >>> cd build
> >>>
> >>> cmake -DCMAKE_INSTALL_PREFIX="/usr" -
> DCMAKE_BUILD_TYPE=Release
> >> ../
> >>> make
> >>>
> >>> sudo make install
> >>>
> >>> sudo ldconfig
> >>>
> >>> then I have created a file named '99-usb-serial.rules'  with the
> >>> following con

Re: R: R: Funcube Dongle Pro Plus help

[Marcus Müller]

You need to be more careful, Vincenzo. The space between = and " is 
wrong. There mustn't be any space. It should be:


cmake -DCMAKE_INSTALL_PREFIX="/usr/local/" ../

Best regards,
Marcus

On 31/08/2020 20.18, Vincenzo Mone wrote:

Hi Marcus,
thanks for your reply.
I gave the command:

gnuradio-config-info --prefix

and got :

/usr/local

So I have tried to give the command:

cmake -DCMAKE_INSTALL_PREFIX= "/usr/local/" ../

- Checking for module 'mpir >= 3.0'
--   No package 'mpir' found
-- Could NOT find MPIR (missing: MPIRXX_LIBRARY MPIR_LIBRARY MPIR_INCLUDE_DIR)
-- User set python executable /usr/bin/python3
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found suitable exact 
version "3.8.2")
-- Found ALSA 1.2.2
-- Found jack: /usr/lib/x86_64-linux-gnu/libjack.so
-- Extracting version information from git describe...
-- System Hidapi will be used

how to run gdb with gnuradio 3.8 ?

[Tom McDermott]

I am trying to debug an OOT in gnuradio 3.8 using gdb.  It's a problem with
double free()
that seems to have popped up with 3.8.2

I rebuilt my OOT with debug symbols.  WIthout gdb, it all runs, but of
course tells me about the double free() when it shuts down.

1. I've altered the top_block.py to stop and wait after printing the
process id before continuing,
then enter to continue.  This starts up the flowgraph GUI.

2. In a different terminal window:
$ sudo gdb -p the_process_id
This makes the gui disappear, and   'System Problem Detected' window
appears asking
if I want to report the problem.

I still have the gdb window, but because I was not able to shut down my
GUI, the
backtrace does not let me look at the shutdown error I am getting.

-- Tom, N5EG

Re: how to run gdb with gnuradio 3.8 ?

[Jeff Long]

You can run the python interpreter under gdb, outside GRC, and that should
capture library errors. Another stranger idea would be to change the
"interpreter" under GRC options/advanced to run your program under GDB. I
got this to work using something along the lines of:

  gdb {python} -ex "run -u {filename}"

but didn't figure out how to interact with GDB afterward if that were to be
necessary.

On Mon, Aug 31, 2020 at 4:30 PM Tom McDermott  wrote:

> I am trying to debug an OOT in gnuradio 3.8 using gdb.  It's a problem
> with double free()
> that seems to have popped up with 3.8.2
>
> I rebuilt my OOT with debug symbols.  WIthout gdb, it all runs, but of
> course tells me about the double free() when it shuts down.
>
> 1. I've altered the top_block.py to stop and wait after printing the
> process id before continuing,
> then enter to continue.  This starts up the flowgraph GUI.
>
> 2. In a different terminal window:
> $ sudo gdb -p the_process_id
> This makes the gui disappear, and   'System Problem Detected' window
> appears asking
> if I want to report the problem.
>
> I still have the gdb window, but because I was not able to shut down my
> GUI, the
> backtrace does not let me look at the shutdown error I am getting.
>
> -- Tom, N5EG
>
>
>
>
>
>
>

R: R: R: R: Funcube Dongle Pro Plus help

[Vincenzo Mone]

Thanks Marcus,
it worked no Missing blocks now but when I go to run the Funcube grc file I get 
tis on the bottom:

Generating: '/media/enzo/243A-C1DB/BY70-2/BY70-2/frontend_by702_rx_fcdpp.py'

Executing: /usr/bin/python3 -u 
/media/enzo/243A-C1DB/BY70-2/BY70-2/frontend_by702_rx_fcdpp.py

Traceback (most recent call last):
  File "/media/enzo/243A-C1DB/BY70-2/BY70-2/frontend_by702_rx_fcdpp.py", line 
366, in 
main()
  File "/media/enzo/243A-C1DB/BY70-2/BY70-2/frontend_by702_rx_fcdpp.py", line 
342, in main
tb = top_block_cls()
  File "/media/enzo/243A-C1DB/BY70-2/BY70-2/frontend_by702_rx_fcdpp.py", line 
266, in __init__
self.fcdproplus_fcdproplus_0 = fcdproplus.fcdproplus('',1)
  File "/usr/local/lib/python3/dist-packages/fcdproplus/fcdproplus_swig.py", 
line 121, in make
return _fcdproplus_swig.fcdproplus_make(*args, **kwargs)
RuntimeError: Alsa not found.

>>> Done (return code 1)


And it does not run.
Any advice please?
Thanks

73’s de Enzo IK8OZV
EasyLog 5 BetaTester
EasyLog PDA BetaTester
WinBollet BetaTester
D.C.I. CheckPoint Regione Campania
Skype: ik8ozv8520




  *
  **   GSM  +39 328 7110193  **
  * SMS  +39 328 7110193*
  *

> -Messaggio originale-
> Da: Marcus Müller 
> Inviato: lunedì 31 agosto 2020 20:44
> A: Vincenzo Mone 
> Oggetto: Re: R: R: R: Funcube Dongle Pro Plus help
> 
> Vincenzo,
> 
> CC. gnuradio-disc...@gnu.org.
> 
> Respectfully,
> Marcus
> 
> On 31/08/2020 20.42, Vincenzo Mone wrote:
> > Marcus,
> > i have retried againd with the command you said deleting the gr-fcdproplus
> folder and restarting.
> > When I run make I have noticed at the end this:
> >
> > warning: Tag 'PERL_PATH' at line 1686 of file '/home/enzo/gr-
> fcdproplus/build/docs/doxygen/Doxyfile' has become obsolete.
> >   To avoid this warning please remove this line from your 
> > configuration
> file or upgrade it using "doxygen -u"
> > warning: Tag 'MSCGEN_PATH' at line 1707 of file '/home/enzo/gr-
> fcdproplus/build/docs/doxygen/Doxyfile' has become obsolete.
> >   To avoid this warning please remove this line from your 
> > configuration
> file or upgrade it using "doxygen -u"
> > [100%] Built target doxygen_target
> >
> > Is it normal?
> >
> > 73’s de Enzo IK8OZV
> > EasyLog 5 BetaTester
> > EasyLog PDA BetaTester
> > WinBollet BetaTester
> > D.C.I. CheckPoint Regione Campania
> > Skype: ik8ozv8520
> >
> >
> >
> >
> >*
> >**   GSM  +39 328 7110193  **
> >* SMS  +39 328 7110193*
> >*
> >
> >> -Messaggio originale-
> >> Da: Marcus Müller 
> >> Inviato: lunedì 31 agosto 2020 20:26
> >> A: Vincenzo Mone 
> >> Cc: Gnuradio Mailing List 
> >> Oggetto: Re: R: R: Funcube Dongle Pro Plus help
> >>
> >> You need to be more careful, Vincenzo. The space between = and " is
> wrong.
> >> There mustn't be any space. It should be:
> >>
> >> cmake -DCMAKE_INSTALL_PREFIX="/usr/local/" ../
> >>
> >> Best regards,
> >> Marcus
> >>
> >> On 31/08/2020 20.18, Vincenzo Mone wrote:
> >>> Hi Marcus,
> >>> thanks for your reply.
> >>> I gave the command:
> >>>
> >>> gnuradio-config-info --prefix
> >>>
> >>> and got :
> >>>
> >>> /usr/local
> >>>
> >>> So I have tried to give the command:
> >>>
> >>> cmake -DCMAKE_INSTALL_PREFIX= "/usr/local/" ../
> >>>
> >>> - Checking for module 'mpir >= 3.0'
> >>> --   No package 'mpir' found
> >>> -- Could NOT find MPIR (missing: MPIRXX_LIBRARY MPIR_LIBRARY
> >>> MPIR_INCLUDE_DIR)
> >>> -- User set python executable /usr/bin/python3
> >>> -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so
> >>> (found suitable exact version "3.8.2")
> >>> -- Found ALSA 1.2.2
> >>> -- Found jack: /usr/lib/x86_64-linux-gnu/libjack.so
> >>> -- Extracting version information from git describe...
> >>> -- System Hidapi will be used
> >>>
> >

Re: how to run gdb with gnuradio 3.8 ?

[Marcus Müller]

Interact in which way, enabling what? Maybe I / we have some hints :)

On 31.08.20 22:52, Jeff Long wrote:
> You can run the python interpreter under gdb, outside GRC, and that should
> capture library errors. Another stranger idea would be to change the
> "interpreter" under GRC options/advanced to run your program under GDB. I
> got this to work using something along the lines of:
> 
>   gdb {python} -ex "run -u {filename}"
> 
> but didn't figure out how to interact with GDB afterward if that were to be
> necessary.
> 
> On Mon, Aug 31, 2020 at 4:30 PM Tom McDermott  wrote:
> 
>> I am trying to debug an OOT in gnuradio 3.8 using gdb.  It's a problem
>> with double free()
>> that seems to have popped up with 3.8.2
>>
>> I rebuilt my OOT with debug symbols.  WIthout gdb, it all runs, but of
>> course tells me about the double free() when it shuts down.
>>
>> 1. I've altered the top_block.py to stop and wait after printing the
>> process id before continuing,
>> then enter to continue.  This starts up the flowgraph GUI.
>>
>> 2. In a different terminal window:
>> $ sudo gdb -p the_process_id
>> This makes the gui disappear, and   'System Problem Detected' window
>> appears asking
>> if I want to report the problem.
>>
>> I still have the gdb window, but because I was not able to shut down my
>> GUI, the
>> backtrace does not let me look at the shutdown error I am getting.
>>
>> -- Tom, N5EG
>>
>>
>>
>>
>>
>>
>>
> 

Re: how to run gdb with gnuradio 3.8 ?

[Jeff Long]

If the console window in GRC were interactive, then you could debug right
there, using gdb as the interpreter. I spent a grand total of 5 minutes
looking into this, so maybe this is already possible. There's no particular
advantage to doing it this way, though, since we assume that the user is
fairly advanced if they're debugging an OOT ... the usual reason for not
wanting to leave the GRC environment doesn't apply.

On Mon, Aug 31, 2020 at 7:20 PM Marcus Müller  wrote:

> Interact in which way, enabling what? Maybe I / we have some hints :)
>
> On 31.08.20 22:52, Jeff Long wrote:
> > You can run the python interpreter under gdb, outside GRC, and that
> should
> > capture library errors. Another stranger idea would be to change the
> > "interpreter" under GRC options/advanced to run your program under GDB. I
> > got this to work using something along the lines of:
> >
> >   gdb {python} -ex "run -u {filename}"
> >
> > but didn't figure out how to interact with GDB afterward if that were to
> be
> > necessary.
> >
> > On Mon, Aug 31, 2020 at 4:30 PM Tom McDermott 
> wrote:
> >
> >> I am trying to debug an OOT in gnuradio 3.8 using gdb.  It's a problem
> >> with double free()
> >> that seems to have popped up with 3.8.2
> >>
> >> I rebuilt my OOT with debug symbols.  WIthout gdb, it all runs, but of
> >> course tells me about the double free() when it shuts down.
> >>
> >> 1. I've altered the top_block.py to stop and wait after printing the
> >> process id before continuing,
> >> then enter to continue.  This starts up the flowgraph GUI.
> >>
> >> 2. In a different terminal window:
> >> $ sudo gdb -p the_process_id
> >> This makes the gui disappear, and   'System Problem Detected' window
> >> appears asking
> >> if I want to report the problem.
> >>
> >> I still have the gdb window, but because I was not able to shut down my
> >> GUI, the
> >> backtrace does not let me look at the shutdown error I am getting.
> >>
> >> -- Tom, N5EG
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >
>
>

Re: how to run gdb with gnuradio 3.8 ?

[Marcus D. Leech]

On 08/31/2020 07:34 PM, Jeff Long wrote:
If the console window in GRC were interactive, then you could debug 
right there, using gdb as the interpreter. I spent a grand total of 5 
minutes looking into this, so maybe this is already possible. There's 
no particular advantage to doing it this way, though, since we assume 
that the user is fairly advanced if they're debugging an OOT ... the 
usual reason for not wanting to leave the GRC environment doesn't apply.


If you're a developer and the thought of popping out to an ordinary 
command-line frightens you, you must be a Visual Studio user :) :)


[I'll, ahem, go back to my troll cave].