> From:
> devin kelly
> Subject:
> Re: [Discuss-gnuradio] PFB Clock
> Sync stops producing samples
> Date:
> Thu, 8 Ju
now for Filter Size
> > PFB MF Taps: whatever prototype filter taps you're using now
> >
> >
> > Properly fixing the tag propagation in the PFB_clock_sync block is a
> > major change, which is one reason I wrote the new Symbol Synchronizer
> > blocks.
> &
s a
> major change, which is one reason I wrote the new Symbol Synchronizer
> blocks.
>
> FWIW, I also do think get_tags_in_range() could stand to perform a
> sanity check, but that won't fix the underlying problem.
>
> -Andy
>
>
> >
x27;t fix the underlying problem.
-Andy
> From:
> devin kelly
> Subject:
> [Discuss-gnuradio] PFB Clock Sync
> stops producing samples
> Date:
> Thu, 8 Jun 2017 12:08:12 -0400
>
> ___
I'm having a problem with the Polyphase Clock Sync block. I believe what's
happening is that the block is calling get_tags_in_range improperly and
then causing an infiite loop in gnuradio-runtime/lib/buffer.cc, at this
point the PFB Clock Sync block stops emitting samples.
The problem occurs in t
On Mon, Feb 13, 2012 at 9:39 PM, Nick Foster wrote:
> Hi all,
>
> I've been doing some stuff with the pfb clock sync for GMSK (my AIS app
> again) and had a couple questions. First, a sanity check so you can tell me
> if I'm just nuts:
>
> BT = 0.35
> self.filtersections = 32
> self.tapspersectio
Hi all,
I've been doing some stuff with the pfb clock sync for GMSK (my AIS app
again) and had a couple questions. First, a sanity check so you can tell me
if I'm just nuts:
BT = 0.35
self.filtersections = 32
self.tapspersection = 20
self.clockrec_sps = 1
gain_mu = 0.03
self._samples_per_symbol =
