Hi Verónica,
in your long/short_sync_block's __init__, you set the in_sig to [np.complex64], which is
of a complex number composed of two 32 bit floats.
You can change that to other types!
But: your wifi_phy block outputs something specific, it needs to match that.
Best regards,
Marcus
On 25.11.21 17:47, Verónica Toro Betancur wrote:
Hi Martin,
Yes, that could definitely be the case. I don't have my radios right now with me, but
I'll try it tomorrow. And sorry for the silly question, but how should I define it in
Python to be fixpoint?
On Thu, Nov 25, 2021 at 6:25 PM Martin Braun <[email protected]> wrote:
Verónica,
have you maybe mismatched data types? Like, the real signals are fixpoint,
but your
Python is doing floating point?
--M
On Thu, Nov 25, 2021 at 2:59 PM Verónica Toro Betancur <[email protected]>
wrote:
Hi,
I am trying to detect and decode WiFi and ZigBee signals in GNURadio.
For the
detection, I have implemented my own blocks in Python. It all works
well with
simulated signals but the problem comes when I use radios to acquire
real
signals. I'm using Pluto SDR and it works perfectly when I use it in
workflow
examples but not in my own implementation. I mean, I plot the data that
comes
directly from the radio and it looks good in the given examples but, in
mine, it
looks like noise.
I am using the exact same parameters in both cases. The only difference
I see is
that the blocks in the example are all in C++ while mine are in Python.
Could
this be the problem? If so, is there a way to solve it other than
writing the
blocks in C++?
Thanks in advance.
Best regards,
Verónica
