Hi again,
Apologies, this is what you get from not using copy/paste...
On 06/03/2020 14:06, Paul Boven wrote:
Create a 'Variable' block, with Id 'Sine', and Value:
np.sin(np.linrange(0, 2*np.pi, samp_rate, endpoint=False)
This needs to be 'linspace', not 'linrange'.
Regards, Paul Boven.
Hi Lukas,
On 03/03/2020 16:52, Lukas Haase wrote:
3.) What would you do if you would want to create precise timing signals? Is a
custom block really the only way? And then, how would you implement it?
This is a problem that I've run into as well in the past. You don't have
to create a custom
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
On 03/02/2020 04:45 PM, Lukas Haase wrote:
Hi Marcus,
How can (or better: *should*) a fully digital signal source have phase noise?
Also, for 1Hz at 5MSps I always get either 5005789 or 5005790 samples (instead
of 500) ... this is fairly deterministic.
Experimenting a bit, I see the weird
Hi Marcus,
How can (or better: *should*) a fully digital signal source have phase noise?
Also, for 1Hz at 5MSps I always get either 5005789 or 5005790 samples (instead
of 500) ... this is fairly deterministic.
Experimenting a bit, I see the weirdest behaviour of the analog signal source.
In
