Supporting 100Msps rates on an ordinary PC is exceedingly challenging for any
but the most trivial signal processing.
Even the most simple mathematical operation uses 10s or 100s of instructions
once you factor all the overhead of moving samples around, etc.
Sent from my iPhone
> On Jul 9,
Thank you Marcus!
I am not using a Raspberry Pi, I use a PC directly connecting to the USRP
(sorry I confused you saying embedded python block).
So I suppose I can try C instead of python to speed it up, or maybe FPGA,
then I need time learn
Best regards,
Wei
Marcus Müller 于2021年7月9日周五 下午5:
It might be faster, and it will not compete with the rest of Python for the
single Python
global interpreter lock.
Important point: you usually do *not* develop your software directly on the
embedded
platform (ie. your pi); you'd normally start on a PC, develop, figure out how
fast it runs
ther
Thank you for the quick reply, so if I write the block in C++ or C, it may
work at a higher rate?
Regards,
Wei
Marcus D. Leech 于2021年7月9日周五 下午5:29写道：
> On 07/09/2021 12:05 PM, Huang Wei wrote:
>
> Sorry, I mean it's the underrun problem
>
> Huang Wei 于2021年7月9日周五 下午5:02写道：
>
>> Hello everyone,
On 07/09/2021 12:05 PM, Huang Wei wrote:
Sorry, I mean it's the underrun problem
Huang Wei mailto:weizar...@gmail.com>> 于2021年7
月9日周五 下午5:02写道：
Hello everyone,
I am using the embedded python block in GRC to realize some simple
functions. All works fine in the GRC local set-up. Ho
Sorry, I mean it's the underrun problem
Huang Wei 于2021年7月9日周五 下午5:02写道：
> Hello everyone,
>
> I am using the embedded python block in GRC to realize some simple
> functions. All works fine in the GRC local set-up. However, if I connect a
> USRP sink to the flowgraph which includes that python b
