Morton:
We built GNU Radio 3.7.11 with some blocks, (including the Pluto/IIO ones, but
missing some others), and put it here:
https://github.com/tfcollins/GNURadio_Windows_Build_Scripts/releases/tag/1.5.0
This doesn’t include the drivers (which need to be installed on windows
separately):
https
Glad to help!
NB: the null source-to-sink trick might consume up to two CPU cores
completely and thus contribute to global warming as much as about 1.5
ppb of the total bitcoin infrastructure ;)
Cheers,
Marcus
On Fri, 2019-12-06 at 05:21 +0100, Lukas Haase wrote:
> Dear Marcus, Dear Kevin,
>
Hi,
I am using GRC 3.7.11 on Ubuntu (WSL). When I use the M&M Clock Recovery block
GRC crashes randomly with this message:
clock_recovery_mm_cc: ii > ninput_items[0] (3168 > 3167
python:
/build/gnuradio-BBYmSv/gnuradio-3.7.11/gr-digital/lib/clock_recovery_mm_cc_impl.cc:214:
virtual int gr::di
> Marcus Mueller wrote:
>
> NB: the null source-to-sink trick might consume up to two CPU cores
> completely and thus contribute to global warming as much as about 1.5
> ppb of the total bitcoin infrastructure ;)
Thank you, also good point. Adding a Throttle block with sample_rate=10m should
all
> Date: Fri, 6 Dec 2019 07:22:11 +0100
> From: "Lukas Haase"
> Hi,
>
> I am using GRC 3.7.11 on Ubuntu (WSL). When I use the M&M Clock
> Recovery block GRC crashes randomly with this message:
>
>
> clock_recovery_mm_cc: ii > ninput_items[0] (3168 > 3167
> python: /build/gnuradio-BBYmSv/gnuradi
Hi Andy,
On 2019-12-06 14:28, Andy Walls wrote:
> [...]
>
> The M&M clock recovery block is obsolete. Use the Symbol Synchronizer
> block instead, if you must use the M&M TED.
Thank you.
You do not mean "Polyphase Clock Sync" but "Symbol Synchronizer"? Is this part
of the standard blocks in GR
