RE: Rust-lang

Also, for PlutoSDR, there is an official RUST Crate: https://crates.io/crates/industrial-io https://docs.rs/industrial-io/0.2.0/industrial_io/ On Friday, April 23, 2021 6:02 PM, Derek Kozel wrote: Subject: Re: Rust-lang [External] Hi Sam, I started looking at using the CXX library for

Re: gr 3.9 OOT execution error: unknown base type gr::block

HI Josh - here is the entire file ./python/bindings/python_bindings.cc: /* * Copyright 2020 Free Software Foundation, Inc. * * This file is part of GNU Radio * * SPDX-License-Identifier: GPL-3.0-or-later * */ #include #define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION #include

Re: GNUradio alsa audio

hi Marcus problem solved! thanks for information: I immediately localize the conf file and I can easily tune numbers of period. Best Regards, David Martini Il giorno mer 5 mag 2021 alle ore 14:27 Marcus Müller ha scritto: > How did you install GNU Radio? This usually defines where things are

Re: gr 3.9 OOT execution error: unknown base type gr::block

That looks right. And in python_bindings.cc, do you see the import of base block methods like: PYBIND11_MODULE(blocks_python, m) { // Initialize the numpy C API // (otherwise we will see segmentation faults) init_numpy(); // Allow access to base block methods

Re: Block not found in module although it is there

Hello Vasil, thank you very much, this seems to solve the problem and I now know where to look the next time :-) Kind regards, Ralf Am 05.05.2021 um 17:08 schrieb Vasil Velichkov: Hi Ralf, On 05/05/2021 17.38, Ralf Gorholt wrote: AttributeError: module 'dl5eu' has no attribute

Re: gr 3.9 OOT execution error: unknown base type gr::block

Hi Josh - thanks for your help. from ./python/bindings/hermesNB_python.cc: void bind_hermesNB(py::module& m) { using hermesNB= ::gr::hpsdr::hermesNB; py::class_>(m, "hermesNB", D(hermesNB)) .def(py::init(::make), py::arg("RxFreq0"), ... long list of

Re: Block not found in module although it is there

Hi Ralf, On 05/05/2021 17.38, Ralf Gorholt wrote: > AttributeError: module 'dl5eu' has no attribute 'dvbt_ofdm_synchronization' > Can anybody give me a hint what is happening here? You most probably need to link the gnuradio's fft component to your OOT block. In your CMakeLists.txt find the

Block not found in module although it is there

Dear all, my problem concerns GNU Radio version 3.8 from the maintenance branch but it is probably not limited to this version. I would like to try to adapt the block "ofdm_synchronization" that Federico Larrocca and others have developed for ISDB-T so that it can be used for DVB-T. For this

Re: gr 3.9 OOT execution error: unknown base type gr::block

Tom, What does your hermesNB_python.cc look like? There should be a declaration for the binding in there that looks like: py::class_ wrote: > I'm working on porting my OOT to gr 3.9 The 3.7 and 3.8 versions work > fine. > The ported code is compiled and make installed. My OOT is visible

gr 3.9 OOT execution error: unknown base type gr::block

I'm working on porting my OOT to gr 3.9 The 3.7 and 3.8 versions work fine. The ported code is compiled and make installed. My OOT is visible in GRC, and I've added to a new flowgraph. My OOT is in category HPSDR and the module is hermesNB (of several). When I try to execute a simple

Re: GNU Radio 3.9 gr_modtool problem

I have installed GNU Radio from the master branch, so I have got version 3.10 now. The install prefix is /usr. I don't have a ~/.gnuradio/config.conf file, only ~/.gnuradio/grc.conf exists after I have started gnuradio-companion. The directory /etc/gnuradio/conf.d exists. The files in there are

Re: GNUradio alsa audio

How did you install GNU Radio? This usually defines where things are looked for. You can check where your GNU Radio looks by running gnuradio-config-info --prefsdir , gnuradio-config-info --userprefsdir and gnuradio-config-info --sysconfdir . In fact, that tool can be used to check whether

GNUradio alsa audio

in order to reduce Ua warning I try to adjust (according to GNUradio WiKi ) the jumper of periods. In my case I found this setting in /etc/gnuradio/conf.d alsa audio directorybut seem to be no effect. Can be that the configuration file is located in other directory. Thank you for your help.

Re: GNU Radio gr-osmosdr on Ubuntu Installation Error; Kali Successfully Installs but Can’t Run

In my case gr-osmosdr on ubuntu 20.04 Work just in gnuradio 3.8.1. I'm not able to run it on ubuntu 3.9.. at least unit 10 days ago. David Martini Il Mer 5 Mag 2021, 12:49 Jeff Long ha scritto: > On Ubuntu 20.04, apt install gr-osmosdr works. > > It sounds like you've gone through quite a bit

Re: GNU Radio 3.9 gr_modtool problem

I think it may be more insidious. The ~/.gnuradio/config.conf file doesn't necessarily exist, and the default config.conf is in /etc/gnuradio/conf.d But if the install prefix is /usr, then there's some trickery in the top level CMakeLists.txt file. See:

Re: GNU Radio gr-osmosdr on Ubuntu Installation Error; Kali Successfully Installs but Can’t Run

On Ubuntu 20.04, apt install gr-osmosdr works. It sounds like you've gone through quite a bit here. What is the HackRF1 RF Receiver you mention? On Wed, May 5, 2021 at 4:28 AM Jessica Chen wrote: > Dear all, > > My main goal is to simply get the HackRF One FM receiver to work on GRC. > In

Re: GNU Radio 3.9 gr_modtool problem

Check your ~/.gnuradio/config.conf file. In there is a section [modtool] and a "newmod_path=..." Verify that matches the value of your installed path. On mine it says: [modtool] newmod_path = /share/gnuradio/gr39/share/gnuradio/modtool/templates/gr-newmod For 3.9, there was a slight change in the

GNU Radio gr-osmosdr on Ubuntu Installation Error; Kali Successfully Installs but Can’t Run

Dear all, My main goal is to simply get the HackRF One FM receiver to work on GRC. In short, I’ve tried: - GNU Radio installation on Ubuntu 20.04 via PPAs, PyBOMBS, and source. Unfortunately, no variation yields the osmocom source I need. Additional attempts to install gr-osmosdr, via default