Re: Jamming the WiFi channel

On 1/16/21 10:58 PM, paulles...@mailo.com wrote:

Jamming the WiFi channel

1 fichier disponible au téléchargement - hackrf2.png (35 Ko) Vous pouvez télécharger ce fichier en cliquant sur ce lien ou en le copiant dans la barre d'adresse de votre navigateur

Re: stop making unneeded improvements

On 01/16/2021 09:00 PM, Glen Langston wrote: Dear Marcus and all, Thanks for all your efforts. I really to appreciate all you’ve done. Best regards, Glen We know you do, Glen. Sometimes when you haven't been "inside the sausage factory" it can be a bit hard to understand why things are

Re: stop making unneeded improvements

Dear Marcus and all, Thanks for all your efforts. I really to appreciate all you’ve done. Best regards, Glen > On Jan 16, 2021, at 8:30 PM, Marcus Müller wrote: > > Hi! > > On 17.01.21 00:56, KB3CS - Chris wrote: > >> why does not in my mind figure just as prominently as GSoC: other >>

Re: stop making unneeded improvements

Hi! On 17.01.21 00:56, KB3CS - Chris wrote: > why does not in my mind figure just as prominently as GSoC: other > campaigns like GSoD or GSoGUI ? (does anyone actually need me to fill in > the definitions for those abbreviations?) Well, the G in GSoC is "Google", not "GNU Radio": Google

Re: How to debug python blocks.

Python includes a debugger (pdb) and IDEs like VSCode have decent Python debugging. This should work fine for Python scripts like those generated by GRC. Internally, GNU Radio is highly parallel, which creates additional challenges not related to language ... how do you stop one block when that

Re: Is it time?

What's wrong is that GNN != GNU. Ron W6RZ On 1/16/21 15:57, KB3CS - Chris wrote: you know? the top result of a web search "gnuradio donation" provides: *Donations* - GNN Radio https://gnnradio.org

Is it time?

you know? the top result of a web search "gnuradio donation" provides: *Donations* - GNN Radio https://gnnradio.org /Donations/ *Donations* GNNradio is a non-profit ministry, funded

Re: stop making unneeded improvements

On Fri, 08 Jan 2021 22:16:22 -0500, "Marcus D. Leech" < patchvonbr...@gmail.com> wrote a great many things, and then this excerpt: > I "get" the whole "oh, but it's so very close to what I need". But GR > really is just a specialized programming environment, and GRC >has the unfortunate (in

How to debug python blocks.

So this is a relatively generic question about what people's processes for writing and debugging python blocks are. In C++ I use VScode and just run the gdb debugger - I can place breakpoints, look at variables, and step through the program super easily. Ideally I would like to be able to do the

Re: Problem with Log Power FFT block

Not all blocks support C++ code generation. I haven't tried generating C++, actually. Do you need that? I changed Output Language option to Python and the error is gone. Thanks for help Wojciech Kazubski

Re: Problem with Log Power FFT block

Not all blocks support C++ code generation. I haven't tried generating C++, actually. Do you need that? On Sat, Jan 16, 2021 at 5:52 PM wrote: > Cytowanie Jeff Long : > > > On the 3.8.2 installation, could you try creating a new flowgraph from > > scratch that is just > > Signal Source ->

Re: Problem with Log Power FFT block

Cytowanie Jeff Long : On the 3.8.2 installation, could you try creating a new flowgraph from scratch that is just Signal Source -> Throttle -> FFT Log Power -> Null Sink and see what happens? Between 3.8.1 and 3.8.2, the line of code where you're seeing the error was removed. It was part of

Re: Problem with Log Power FFT block

Hi Jeff - hmm, it appears the FFT block on 3.8.2 appears it doesn't like vectors? -- Cinaed On 1/16/21 1:24 PM, Jeff Long wrote: On the 3.8.2 installation, could you try creating a new flowgraph from scratch that is just   Signal Source -> Throttle -> FFT Log Power -> Null Sink and see what

Hiw to install binaries for GNURADIO 3.7 using MacPorts for MAC

Hi all, this email is intended primarily for Michael Dickens who maintains GNURADIO for MAC, but if anyone else knows feel free to chime in. I am teaching a class where some of the students have MAC and want to install a version of GNURADIO/GRC locally. The class is using GNURADIO 3.7 in the Lab

Re: Problem with Log Power FFT block

On the 3.8.2 installation, could you try creating a new flowgraph from scratch that is just Signal Source -> Throttle -> FFT Log Power -> Null Sink and see what happens? Between 3.8.1 and 3.8.2, the line of code where you're seeing the error was removed. It was part of the yml file for that

Re: Problem with Log Power FFT block

Try deleting the block, saving, and adding the block back in. I tried source -> log power fft -> max ... with no problems. Deleting and inserting again the block does not help. I can see the problem even on flowchart created from scratch in GR 3.8 The problem exists on openSUSE Tumbleweed

Re: Version info

Thanks for the info. I see the wrong version info depends on git describe which depends on a correct tagging. As every branch has it's own version info, why don't we use git rev-parse --short HEAD instead of git describe to get the commit hash ? So we would be independent of missing tags. --