06.02.2015 14:56, Georg Chini wrote: > One more thing: There is a systematic error in the adjust_time I could > not work around without > introducing too much overhead. The latency snapshot varies widely in the > execution time, I > measured values between 50 us and more than 60 ms. So if the extreme > values follow each other > you will have one adjust time that is around 60 ms too long and another > one which is 60 ms too > short. Maybe this also contributes significantly to the (in)stability of > regulation. Thanks for this observation. I will look into it, too. -- Alexander E. Patrakov
