Hi Shalom - Something to check / verify: In the top-level CMakeLists.txt
file, when searching for GNU Radio, make sure to include the FFT module,
not just RUNTIME. From the look of the error, libgnuradio-fft is not
being linked into your OOT anywhere. This small tweak should do the
trick if this
Glad I could help out with the plumbing part of the problem, but I think
you'll need someone who knows how the wifi code works to help you out now.
On 04/30/2018 12:55 PM, Sumit Kumar wrote:
Hi Jeff,
Ok Now I did some experiments. I modified the long_sync block where it
outputs same items on
Michael,
That seems to have done it, thanks! Much appreciated.
On Mon, Apr 30, 2018 at 11:06 PM Michael Dickens
wrote:
> Hi Shalom - Something to check / verify: In the top-level CMakeLists.txt
> file, when searching for GNU Radio, make sure to include the FFT
Hi Jordan,
nice! But: what exactly do you need help with? What's that source?
Best regards,
Marcus
On Tue, 2018-04-10 at 10:53 -0400, Jordan Nnabugwu wrote:
>
> I want to be able to create a block that will sent a message to change my
> source once it senses a certain amount of power coming
Hi Snehasish,
since this is defitnitely not your complete code, there's nothing we
can do to help you :(
Best regards,
Marcus
On Mon, 2018-04-02 at 19:13 +, Snehasish Kar wrote:
> Hello
>
> I was trying to generate a flow graph using file source descriptor and a file
> sink. But after
Hi Marvin,
sorry to have been so late to react:
Don't use the Packet Decoder. It has a bug and doesn't work reliably!
That's why it's in the "deprecated" category.
Best regards,
Marcus
On Thu, 2018-04-05 at 19:28 +, Marvin Biedermann wrote:
> Hello,
>
> I am new to Gnuradio and I have a
Hi Jacob,
sorry, I wasn't around to react to this:
Wow! Thank you for sharing this.
Would this be functionality that you'd like to see upstreamed into
mainline GNU Radio? That might ease future usage for you, as then "GNU
Radio" as a whole project would notice if something we do breaks the
unit
Dear Kailash,
there's very much that can go wrong for over-the-air transmissions, and
you'll simply have to apply your digital wireless communications
knowledge to narrow this down.
Furthermore, the Packet encoder and decoder blocks are *heavily*
deprecated, and you mustn't use them. Use the
Ah, by the way, the function names where that error occurs are mangled
C++ names; I'll try to show what is what (using `c++filt` to demangle
the names)
> /lib64/libc.so.6(+0x7dd4d)[0x7fa14f448d4d]
> /lib64/libc.so.6(__libc_malloc+0x4c)[0x7fa14f44afbc]
OK, that's malloc; are we certain that this
Huh, no, barring great undiscovered bugs, the delay involved shouldn't
have anything to do with the data, and the error pretty certainly has
something to do with invalid input data.
Are you sure the data is always the same?
Best regards,
Marcus
On Thu, 2018-04-12 at 11:03 -0400, Brad Hein wrote:
Hi Brad,
Sorry that I missed your mail for so long!
So, I'm pretty certain I've fixed a potential race condition when
accessing the data vector in vector sink lately:
https://github.com/gnuradio/gnuradio/pull/1445
But that should be included in the 3.7.11.1 release you're using... hm.
We
Hi,
I'm not very experienced with c++ or with swig, so perhaps I'm missing
something here, but I've got a problem and I can't figure it out.
I'm trying to replicate the signal_detector block in gr-inspector, and I
can't seem to include the fft header so that swig detects it. I can't find
the
12 matches
Mail list logo