Re: [Discuss-gnuradio] Delay locked loop for the two-clock problem

2016-10-29 Thread Biju Ravindran
Hi, How to calculate how much is the ppm from the error value, which is actually the drift. If suppose my sample rate is 48KHz and the accumulated error after 1M samples (20.833 sec) is 'n' samples, then ppm = n, Is that correct calculation ? On Thu, Oct 27, 2016 at 3:24 AM, Marcus Müller wr

Re: [Discuss-gnuradio] Delay locked loop for the two-clock problem

2016-10-27 Thread Fons Adriaensen
On Thu, Oct 27, 2016 at 10:35:32PM +, Fons Adriaensen wrote: > time constant of around 10 / B, i.e. one second. So the relativei Correction : of around 1 / (10 * B), i.e. one second. -- FA A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-

Re: [Discuss-gnuradio] Delay locked loop for the two-clock problem

2016-10-27 Thread Fons Adriaensen
On Wed, Oct 26, 2016 at 11:54:17PM +0200, Marcus Müller wrote: > > The actual frequency of the clock used to measure time doesn't > > matter as long as it has reasonable short term stability (and both sides > > use the same clock of course). > Exactly; that what was I was worried about. I don't ha

Re: [Discuss-gnuradio] Delay locked loop for the two-clock problem

2016-10-26 Thread Marcus Müller
Hi Fons, On 10/26/2016 10:26 PM, Fons Adriaensen wrote: > On Wed, Oct 26, 2016 at 01:30:19PM +0200, Marcus Müller wrote: > >> Now, these microsecond timestamps >> will introduce a /third/ clock into our problems. I can see how the >> control loop converges in case of that clock being both faster t

Re: [Discuss-gnuradio] Delay locked loop for the two-clock problem (was: simple mod-demod combinations doesn't work)

2016-10-26 Thread Fons Adriaensen
On Wed, Oct 26, 2016 at 01:30:19PM +0200, Marcus Müller wrote: > Now, these microsecond timestamps > will introduce a /third/ clock into our problems. I can see how the > control loop converges in case of that clock being both faster than your > sampling clock and relatively well-behaved, but: is