Hi,
> I am by no means an expert on this but just for my understanding I would be
> curious:
>
> 1.) I still do not understand why for 1 Hz at 5MSps I can get a period that's
> "500578.5" on average. The frequency error is a whopping 0.1158%!
> ((5005789.5-500)/500*100). Huge.
That's b
Hi Sylvain,
Thank you very much for your answer. Much appreciated!
> Von: "Sylvain Munaut" <246...@gmail.com>
>
> Hi,
>
> > How can (or better: *should*) a fully digital signal source have phase
> > noise?
>
> Limited precision arithmetic
>
>
> > Also, for 1Hz at 5MSps I always get either 500578
Hi,
> How can (or better: *should*) a fully digital signal source have phase noise?
Limited precision arithmetic
> Also, for 1Hz at 5MSps I always get either 5005789 or 5005790 samples
> (instead of 500) ... this is fairly deterministic.
That's because the signal source works with phase i
appreciated.
Thanks,
Lukas
> Gesendet: Mittwoch, 26. Februar 2020 um 16:39 Uhr
> Von: "Marcus D. Leech"
> An: "Lukas Haase"
> Cc: "discuss-gnuradio@gnu.org"
> Betreff: Re: How ensure consistency with timing signals
>
> On 02/26/2020 04:11 PM, Lukas Haa
On 02/26/2020 04:11 PM, Lukas Haase wrote:
Hi Marcus,
Good point; but this is just for demonstration purposes here. I can tie it to
USRP Source/Sink.
The delta (measured in samples) should still be consistent, no matter what.
Best, Lukas
Looking at the siggen code, this is probably equivale
t; An: "Lukas Haase"
> Cc: "discuss-gnuradio@gnu.org"
> Betreff: Re: How ensure consistency with timing signals
>
> Something to understand about the throttle block is that it doesn’t guarantee
> a precise sample rate. Just that the long term average rate is what
Something to understand about the throttle block is that it doesn’t guarantee a
precise sample rate. Just that the long term average rate is what you expect.
Sent from my iPhone
> On Feb 26, 2020, at 12:09 PM, Lukas Haase wrote:
>
> Hello,
>
> I use a square wave to generate control/clockin
