I am offering advice without looking at the flowgraph, so take this with a
grain of salt, but sps usually stands for samples per *symbol*, not seconds.
On Sat, Aug 26, 2017 at 4:04 AM Marcus Müller wrote:
> Hi Mehtap,
>
> huh, if increasing sps = 100 is all that it takes to trigger this, then
>
Hi Mehtap,
huh, if increasing sps = 100 is all that it takes to trigger this, then
this is probably¹ a bug. And as such, we should fix it. Just to confirm:
If you take a totally unmodified packet_loopback_hier.grc and **only**
change sps=100, then you get this?
Generally, sps=100 seems… unintuiti
Thanks to Marcus Müller I became aware of the Packet TX and RX blocks.
I use the Packet_loopback_hier.grc example. However the example is set to
2 samples per seconds=sps. When I try to increase sps=100, the number of
taps of the RRC filter becomes( 5*sps*nfilts) exceeds its limit.
I get
../.grc_
